Friday, May 31, 2013

Exalogic Managing Machine - Part 3

Dear Readers,

My name is Franz Devantier, creator of this blog.  I am an Oracle Certified Professional (OCP DBA 11g) Security DBA.  I will be sharing with you the basic duties of an Oracle DBA, and also some of the undocumented, and not so well known tasks. 

I will make a deal with you:  If you refer me to a company that needs database support, from a few hours per week to full time, and I am able to sign a contract with them.
Then I will give you 10% of the monthly contract or deal price every month.  When the contract ends, and we re-sign the contract, I will again give you 10% of the monthly contract price.  This will go on until the company no longer employs or contracts me or my agents to look after their databases.
I can do this, because that 10% is my marketing budget.  When we re-sign the contract, in the future, it may depend on you giving the thumbs up again, and that is worth 10% of the monthly contract price, to be given to you as commission.


Exalogic Managing Machine  -  Part 3
Viewing Exalogic System Information
We have navigated to the Exalogic systems view, and from that pane in the center of the page we are now going to click on the Details tab.

On the details tab, you will be able to view the following information about your Exalogic System:
. Machine Name
. Description
. Model
. Number of Racks
. Number of compute nodes
. Number of storage nodes
. Number switches
. Number of power distribution units
. Number of fabrics

You may also see information about the Master Subnet Manager.





In the Tags pane on the right hand side, you will see details on the Tags, with their respective values.  There is also a facility to search for a specific Tag.

Viewing Exalogic Control Information
To view the Controls information in Exalogic Control, you can click on the Controls Tab on the center pane.  You will see information there about:
. Software name of Exalogic software components.
. Version of these software components.
. Description of these software components.
. Names of the virtual machines that are hosting the Exalogic components.
. Names of the Oracle VM (OVM) servers that are hosting these virtual machines.


  
You can double click on any of the Exalogic components in the table to view the dashboard for that component.  This table is useful in helping to identify where the Exalogic Control Software components are running in your Exalogic machine.  There is a refresh icon, above the list on the right hand side, if required.

Viewing Infrastructure Networks
You can also click on the Networks tab to view information abut the infrastructure networks and about Network connectivity.  There is a lot of information provided.  At the top is a table containing the data for the Infrastructure Networks.  At the bottom is the table for Network connectivity, which also provides a lot of information.


Franz Devantier,
Need a database health check, or a security audit?
devantierf@gmail.com

Thursday, May 30, 2013

Exalogic Managing Machine - Part 2

Dear Readers,

My name is Franz Devantier, creator of this blog.  I am an Oracle Certified Professional (OCP DBA 11g) Security DBA.  I will be sharing with you the basic duties of an Oracle DBA, and also some of the undocumented, and not so well known tasks. 

I will make a deal with you:  If you refer me to a company that needs database support, from a few hours per week to full time, and I am able to sign a contract with them.
Then I will give you 10% of the monthly contract or deal price every month.  When the contract ends, and we re-sign the contract, I will again give you 10% of the monthly contract price.  This will go on until the company no longer employs or contracts me or my agents to look after their databases.
I can do this, because that 10% is my marketing budget.  When we re-sign the contract, in the future, it may depend on you giving the thumbs up again, and that is worth 10% of the monthly contract price, to be given to you as commission.


Exalogic Managing Machine  -  Part 2
Viewing System Summary, Membership Graph, and Status
Ok, so you have clicked on the Dashboard tab on the center pane, and you can see the following information about your Exalogic machine.
-> System Summary
-> Membership Graph
-> System Status




System Summary Section
The summary section is also the top section, or at the top of the page.  You will see the name of the Exalogic machine.  Also in this section you will see the description of name of the system identifier.  The number of racks that are part of the system.  On the right hand side is a summary of the number of unassigned incidents.  There are three unassigned incident icons which represent: Critical incidents(Red), Warning incidents(Amber), and information incidents(Blue).  These incidents originate from all the assets that belong to the Exalogic racks.

Membership Graph Section
The membership graph section or the middle section displays the Exalogic system as a hierarchy of its components.  It shows the relationship between the Oracle Virtual Machine (OVM) Manager, the physical InfiniBand fabric, and the hardware that is stored in the rack.  InfiniBand is a switched fabric communications link that is used in high performance computing and enterprise data centers, and also in the Exalogic Elastic Cloud System.  You can navigate to any asset by double clicking on the asset in the membership graph.

With the controls on the top right of the graph pane, you can change the view of the graph to either a horizontal or a vertical orientation.  You can refresh the view by clicking on the refresh Icon for the web page.  There is also a control to change the depth of the graph or the size of the images, ie either bigger or smaller.

System Status Section
The bottom section or pane is the System Status Section.   Here is a display of the total unassigned incidents in chart format on the left hand side.  On the right hand side is a listing of the recent incidents encountered by the Exalogic system.  This is listed in table format, with the following columns:
->Severity:  The severity column displays the severity of the incident, with Blue, amber, and red icons.
-> State:  This column displays the state of the incident.
-> ID: This column displays the incident ID, for example ‘13003’.
-> Description: This will give you a description of the incident.
-> Source: This will display the source of the incident
-> Owner: This displays the name of the owner, who reported the incident.
-> Creation Date: This column displays the date on which the incident was created.

Franz Devantier,
Need a database health check, or a security audit?
devantierf@gmail.com

Wednesday, May 29, 2013

Exalogic Managing Machine - Part 1

Dear Readers,

My name is Franz Devantier, creator of this blog.  I am an Oracle Certified Professional (OCP DBA 11g) Security DBA.  I will be sharing with you the basic duties of an Oracle DBA, and also some of the undocumented, and not so well known tasks. 

I will make a deal with you:  If you refer me to a company that needs database support, from a few hours per week to full time, and I am able to sign a contract with them.
Then I will give you 10% of the monthly contract or deal price every month.  When the contract ends, and we re-sign the contract, I will again give you 10% of the monthly contract price.  This will go on until the company no longer employs or contracts me or my agents to look after their databases.
I can do this, because that 10% is my marketing budget.  When we re-sign the contract, in the future, it may depend on you giving the thumbs up again, and that is worth 10% of the monthly contract price, to be given to you as commission.


Exalogic Managing Machine  -  Part 1
The Exalogic Control, enables you to view your Exalogic machine as an appliance.  You can monitor and actively manage the Exalogic hardware and fault management cycle.
The broad categories under Exalogic Management are:
-> Launching the Exalogic Control BUI
-> Navigating to Exalogic Systems
-> Viewing the Exalogic System
-> Viewing the Exalogic Machine Rack
-> Viewing the Photorealistic Representation of the Exalogic Machine
-> Creating and Viewing Exalogic Reports

Launching Exalogic Control BUI
After the Exalogic Control is started, you can access the Exalogic Control Browser User Interface (BUI), using this URL:  http://<EMOC_IP>
-> <EMOC_IP> is the EoIB IP address of the Ops Center Enterprise Controller VM.  This VM is a software component of Exalogic Control.  For more information log into the Exalogic Control BUI as the Exalogic Systems Admin.  You can also find information in the file.  /opt/Exalogic/ecu/config/oc_ec.json.

http://<EMOC_IP> redirects to https://<EMOC_IP>/emoc

Navigating to Exalogic Systems
Once you are in the Exalogic BUI, go to the navigation pane. Under “Assets” select “Exalogic Systems” from the drop down list.



Viewing the Exalogic System
In Exalogic Control BUI there are four tabs on the Center pane.
. Dashboard
. Details
. Controls
. Networks

On the right hand side is the Actions pane.  The actions in the Actions pane are context sensitive to the selected assets on the Navigation pane.  The actions are also based on Roles, to prevent users from carryout actions that they are not authorized to do.

To view a specific Exalogic system in Exalogic Control BUI, you will follow this process.  In the Navigation pane in the Center, move down to Assets, and select “Exalogic Systems” from the drop-down list.   Then you will see a list of the specific Exalogic systems and you can select one of them:
  


After making your selection, there will be five tabs displayed in the Center pane.
. Dashboard
. Details
. Controls
. Networks
. Incidents



You should click on each of the Tabs on the center pane to view information that is contained there.
-> Dashboard:  The Dashboard displays the summary of the Exalogic system, membership graph, as well as the status of the System.
-> Details: the details Tab will display the name of the Exalogic system, the description of the system, the master subnet manager address, the number of racks, the computer nodes, the storage nodes, switches, and the Power Distribution Units (PDU) present in the system.
-> Controls:  The controls tab displays the Exalogic Control Software details such as the name of the software, version number, description, name of the virtual machine, and the server name.
-> Networks: The networks tab will display the infrastructure network table as well as the network connectivity table.
-> Incidents:  The incidents tab displays all the incidents and alerts that have been reported in the Exalogic System.

Franz Devantier,
Need a database health check, or a security audit?
devantierf@gmail.com

Tuesday, May 28, 2013

Exalogic Task Overview Concepts - Part 3

Dear Readers,

My name is Franz Devantier, creator of this blog.  I am an Oracle Certified Professional (OCP DBA 11g) Security DBA.  I will be sharing with you the basic duties of an Oracle DBA, and also some of the undocumented, and not so well known tasks. 

I will make a deal with you:  If you refer me to a company that needs database support, from a few hours per week to full time, and I am able to sign a contract with them.
Then I will give you 10% of the monthly contract or deal price every month.  When the contract ends, and we re-sign the contract, I will again give you 10% of the monthly contract price.  This will go on until the company no longer employs or contracts me or my agents to look after their databases.
I can do this, because that 10% is my marketing budget.  When we re-sign the contract, in the future, it may depend on you giving the thumbs up again, and that is worth 10% of the monthly contract price, to be given to you as commission.
Contact: Franz

Exalogic Task Overview Concepts -  Part 3
Virtual Storage Resources
There are three types of storage resources visible to Cloud Users in the Exalogic vDC.
-> vServer Root Disks
vServer root disks are created at vServer creation time, and are based on the server template.  This is the disk where the vServer OS operates.  Root disks are available after a vServer reboot, and a root disk is deleted only when a vServer is deleted.
There are four attributes of the vServer root disk that are visible to Cloud Users:
. vServer
. Size GB
. Status
. Created by

-> Volumes
A volume is a virtual block storage device that can be attached or detached from vServers.  Cloud Users can attach one or more volumes to a vServer, either at vServer creation time or at a later time to a stopped vServer.  The storage space for volumes is limited by the Account’s quota.
Cloud users can create an empty volume, or create a volume from a snapshot, or import a volume from an HtTP server.
When you create a volume you can share it.  Shared volumes can be attached to multiple vServers.  If a volume is not attached to any vServer, then you can delete it.
There aretwelve attributes about the volumes that are visible to Cloud Users.
. Name
. Description
. Max Size GB
. Usage Size GB
. Attached to
. Share Status
. Use Status
. Root Volume
. R/W
. Created By
. Status
. Tags

-> Snapshots
A snapshot is a clone of a volume at a specific point in time.  The snapshot captures the current state of the volume and is immutable.
Cloud Users can create a snapshot from an existing volume.  Cloud Users can create a volume from a snapshot and attaché those volumes to vServers at vServer creation time.  They can also attach those volumes at a later time to a stopped vServer.  Deleting a volume does not influence any snapshot that had been created based on that volume.  Snapshots exist independently of the volume.
A Snapshot has 12 attributes associated with it, that are visible to Cloud Users:
. Name
. Description
. Max Size GB
. Usage Size GB
. Attached to
. Share Status
. Use Status
. Root Volume
. R/W
. Created By
. Status
. Tags

Distribution Groups
Distribution Groups is a concept that is specific to Exalogic Virtual Data Centers (vDCs).  You place your vServers in a distribution group.  This mechanism can help you to ensure that no two vServers run on the same Oracle VM Server.  Distribution groups are bound to a specific Account.  vServers can be assigned to a distribution group when you create a vServer.  Cloud users have the authority to create, update, or delete their distributions groups.  Naturally you can only delete distribution groups that don’t have any vServers assigned to them.  Cloud Users can check the number of vServers that have been assigned to a specific Distribution group.

There are six Distribution Group attributes that are visible to Cloud Users:
. Name
. Description
. vServer Assigned
. Size
. Status
. Tags

vServers
A vServer is an entity that looks like an Operating System.  It provides the outward interface of a Standalone Operating System.  A vServer consumes CPU and memory resources.  A vServer can be a member of one or multiple vNets.  It has its own identity, its own local storage, its own interfaces, and its own configuration that exists for the full lifetime of the vServer.

As a Cloud User you can create one or multiple vServers at a time.  When you create a single vServer a static IP address.  A suffix is not added to the name of the vServer.  When you create multiple vServers, only automatic IP address assignment is possible.  Also when creating multiple vServers a suffix is added to the vServer name for each vserver.

Before creating a single vServer, a Cloud User should make sure that the following resources exist, and if they don’t exist, then the Cloud User should first define them:
. A Server Template
. A vServer Type
Only Cloud Administrators can create new vServer types, However a Cloud user can choose from the list of defined vServer types, including the three default vServer types.  During the vServer creation process, the vServer types are visible to Cloud Users.  So all a Cloud User can do is to select a vServer Type from the existing vServer Types that are allocated to the Account.
. One or more virtual networks

During the planning stage, the Cloud User can define the requirements anddefine the following resources to be used during the vServer creation.
. Reserved IP addresses
. Distribution Groups
. Volumes
. Public Key

There are nine attributes about the vServer that are visible to Cloud Users:
. Name
. Description
. Created By
. Creation date
. Memory Size GB
. Number of CPUs
. OS
. Status
. Tags

Cloud user can manage the full life cycle of vServers. They can create them, start them, stop them, and destroy them. 

Franz Devantier,
Need a database health check, or a security audit?
devantierf@gmail.com

Monday, May 27, 2013

Exalogic Task Overview Concepts - Part 2

Dear Readers,

My name is Franz Devantier, creator of this blog.  I am an Oracle Certified Professional (OCP DBA 11g) Security DBA.  I will be sharing with you the basic duties of an Oracle DBA, and also some of the undocumented, and not so well known tasks. 

I will make a deal with you:  If you refer me to a company that needs database support, from a few hours per week to full time, and I am able to sign a contract with them.
Then I will give you 10% of the monthly contract or deal price every month.  When the contract ends, and we re-sign the contract, I will again give you 10% of the monthly contract price.  This will go on until the company no longer employs or contracts me or my agents to look after their databases.
I can do this, because that 10% is my marketing budget.  When we re-sign the contract, in the future, it may depend on you giving the thumbs up again, and that is worth 10% of the monthly contract price, to be given to you as commission.
Contact: Franz

Exalogic Task Overview Concepts -  Part 2
Cloud User Tasks
A Cloud User who has been granted access to an Account has all the privileges needed to manage and use the Computing, Network, and storage resources in an Exalogic vDC.  This would be within the limitations of the quotas that were granted to the Account that the Cloud User is working in.

Cloud Users can create vServers, and manage the entire life cycle of the vServer , which they may be doing for their applications.   These are the resources that a Cloud User can manage:
-> Virtual Network resources
-> Server templates
-> Virtual Storage Resources
-> Distribution Groups
-> vServers

Virtual Network Resources
A Virtual Network will restrict the network connectivity of a vServer.  Virtual network management will involve connecting and restricting the network access to vServers.  A Cloud User can see the following types of virtual networks:
-> Public External Networks
These are defined by Cloud Administrators.  Cloud users can’t create, update, or delete this type of vNet.  This type of virtual network can be shared among many Accounts in an Exalogic vDC.  If a vServer is a member of a Public External vNet, then it will also have external communication beyond the Exalogic vDC.  Such vServers can be used to host public services.  A separate IP address is allocated for this type of virtual network.

-> Private vNets
These Private vNets are defined by Cloud Users, according to their requirements, and within the limits of the Account quota.  A private vNet is created based on the private network of the network domain of the Exalogic vDC.  Private vNets are only accessible within an Account.  All vServers that have membership of a private vNet in common with other vServers, can communicate freely throughout that subnet.

The Cloud User defines the private vNets to which vServers are assigned.  Membership of a vServer to one or more vNets can only be specified at the vServer creation time.  Cloud Users can also reserve a number of IP addresses from any existing virtual network.  Reserved IP addresses can be used later on for static allocation to vServers.

When creating vServers, a Cloud User can choose different methods to allocate IP addresses to a vServer.
-> Static Method
With the static method you require a reserved IP address, from each selected virtual network to the vServer.  You can only use this method, when you are creating a dingle vServer at a time.

-> Automatic Method
This method of doing it will dynamically allocate an IP address from each selected virtual network.  This method is good if you are creating multiple vServers at a time.

A Cloud User can when required release a reserved IP address that is not allocated to a vServer.  On the other hand IP addresses that are dynamically allocated to vServers are released automatically when the vServers are deleted.

A vNet has a number of attributes that are visible to Cloud Users:
-> Name:  An identifier in the system for the vNet.
-> Description: This is descriptive test for the vNet.
-> Type:  This can be a Private vNet, or a Public External vNet.
-> Subnet: This attribute defines the IP address range for a vNet.
-> Allocatable Addresses: This is the maximum number of IP addresses that can be allocated to vServers from a vNet.
-> Reserved Addresses: This is the number of reserved IP addresses.
-> Status: This is the current status of the vNet.
Tags:  This is the available tags for a vNet.  Tags can be used for better identification and classification of the vNet.

Server Templates
A Server Template is an OS image that can be used to create a vServer.  The OS image needs to be in a certain format.  Server templates are specific to the processor architecture of the server pool and virtualization type.  You need to have a server template for creating vServers.

Server templates are loaded into the central software library associated with the Exalogic vDC, and they can’t be changed later on.  Server templates are bound to a specific Account by default.  Inside the Exalogic vDC, you can register a server template for public use within any Acccount.

You can also upload a new server template, to be used for creating vServers.  There are a number of attributes of a server template that are visible to Cloud Users.
-> Name: This is an identifier within the system for the server template.
-> Description: This is descriptive text for the server template.
-> Size: This refers to the size of the server template in GB.
-> Memory: Memory that has been defined for the server template in GB
-> OS: This is the type of operating system that is defined for the server template.
-> CPUs: This is the number of CPUs defined for the server template.
-> Assembly: This is the name of the assembly of the server template.  This field is empty because you are uploading the server template using a template sub-type file.
-> Public: This filed indicates if the server template is shared with other Accounts in the Exalogic vDC.
-> Tags: All the available tags for a server template.  Tags can be used for better identification and classification of the server template.

Franz Devantier,
Need a database health check, or a security audit?
devantierf@gmail.com

Sunday, May 26, 2013

Exalogic Task Overview Concepts - Part 1


Dear Readers,

My name is Franz Devantier, creator of this blog.  I am an Oracle Certified Professional (OCP DBA 11g) Security DBA.  I will be sharing with you the basic duties of an Oracle DBA, and also some of the undocumented, and not so well known tasks. 

I will make a deal with you:  If you refer me to a company that needs database support, from a few hours per week to full time, and I am able to sign a contract with them.
Then I will give you 10% of the monthly contract or deal price every month.  When the contract ends, and we re-sign the contract, I will again give you 10% of the monthly contract price.  This will go on until the company no longer employs or contracts me or my agents to look after their databases.
I can do this, because that 10% is my marketing budget.  When we re-sign the contract, in the future, it may depend on you giving the thumbs up again, and that is worth 10% of the monthly contract price, to be given to you as commission.
Contact: Franz

Exalogic Task Overview Concepts -  Part 1
Task Overviews and Basic Concepts
There are various tasks that are split between the users:
. Exalogic Systems Administrator
. Cloud Administrator
. Cloud User

Cloud Administrator Tasks
Account Creation
The Account will enable and entitle the Cloud Users the authorization to use the computing, network, and storage resources of the Exalogic vDC.  The Account provides the required capabilities to manage all of these resources.

Before you create an account:
   -> Estimate the resource quotas to be allocated for the account
   -> Identify the Cloud users to be assigned to the new Account

You define the quota for vCPU, memory, and storage resources during the Account creation process.  In the Account Creation Wizard, the Resource Quota information is displayed, and indicates how much of the corresponding vDC resources can be used or allocated.  You will also be able to see if the vDC resources are oversubscribed or undersubscribed.

You will continue by setting the Account to be able to create a certain number of private vNets.  The maximum number is 4096 private vNets.  Then you will go on to look at defining your private networks.  The maximum number of allowable defined private networks, is a function of the server pool configuration that is defined in the Exalogic vDC.  Within each server pool, you can create a maximum number of 64 private networks.  Some of the number up to 64 are already defined for use by the Exalogic control, so you will have to settle for a few less than 64.

When you create an Account, the public networks that are available in the vDC are listed.  From this listing you can set the number of public IP addresses allocated to the Account.  The public IP addresses can be used by the Cloud User to assign to the vServer, as required.  You have the option to decide which defined public networks will be available to a specific Account.

The virtual resources for an Account are controlled by means of an Entitlement that you will set up during Account creation.  To allocate resources to an Account, you allocate them from the vDC.  You can oversubscribe the total allocation of resources for all the accounts in a vDC, which means that there are more resources allocated than the actual resources in the vDC.  You need to plan the allocation of resources properly, in order to avoid oversubscribing the vDC.  You will need a carefully worked out resource plan, and update the resource configuration when the need arises.  If an Account user does not have sufficient resources, then that Cloud User will get notifications that they cannot create vServers, for example, because there are not enough resources available.

As the Cloud Administrator, you need to monitor the resource usage and re-configure resources when required.  You will need to create as many Accounts as your business requires.  You can partition the Exalogic vDC by Account.  The separation of the Accounts is based on resource allocation.

 Account Management
The Cloud Administrator has a lot of power.  The Cloud Administrator can update the resource configuration for an account.  He can assign Cloud Users to the Account.  He can delete an Account.

The Cloud Users can be assigned to the Account during the account creation or done separately afterwards.  A Cloud User only has access to the Accounts that the Cloud Administrator has added them to.  The Cloud Administrator can manage the access of all the Cloud Users, to all of the Accounts in the Exalogic vDC.

 vServer Type Creation
vServer Types are profiles of virtual machines that define the computing resources, for example the CPU, memory, and storage size.  A Cloud User is restricted to using these definitions in order to implement and create vServers.  A vServer Type that has been created, is available for all the Accounts in the Exalogic vDC.

The Cloud Administrator, can capture the user requirements and create different vServer Types.  There are also some default system-defined vServer Types that are available in the Exalogic vDC.
-> EXTRA_LARGE vServer:  This has 16GB of memory, and 4 vCPUs.
-> LARGE vServer:   This vServer has 8GB of memory, and 2 vCPUs.
-> SMALL vServer:  This vServer has 4GB of memory and 1 vCPU

The Cloud Administrator can create and delete vServer Types.  However the Cloud administrator, can delete the system-defined vServer Types.  These three system defined vServer Types are always present.  When you create a vServer Type in the wizard, the VM hosting details display some information that is based on the resources defined in the vDC.
-> The number of Oracle VM Servers that are in the Exalogic vDC, and that they will have sufficient resources to host the vServer that has been defined with a set of resources.
-> There is an estimation of the number of vServers that can be hosted with the total number of physical resources of the vDC.
-> A warning message will display, when the defined value for the memory size of the vServer, exceeds the available storage in the vDC.

Franz Devantier,
Need a database health check, or a security audit?
devantierf@gmail.com

Saturday, May 25, 2013

Exalogic Creating Users and Roles - Part 3

Dear Readers,

My name is Franz Devantier, creator of this blog.  I am an Oracle Certified Professional (OCP DBA 11g) Security DBA.  I will be sharing with you the basic duties of an Oracle DBA, and also some of the undocumented, and not so well known tasks. 

I will make a deal with you:  If you refer me to a company that needs database support, from a few hours per week to full time, and I am able to sign a contract with them.
Then I will give you 10% of the monthly contract or deal price every month.  When the contract ends, and we re-sign the contract, I will again give you 10% of the monthly contract price.  This will go on until the company no longer employs or contracts me or my agents to look after their databases.
I can do this, because that 10% is my marketing budget.  When we re-sign the contract, in the future, it may depend on you giving the thumbs up again, and that is worth 10% of the monthly contract price, to be given to you as commission.
Contact: Franz

Exalogic Creating Users and Roles -  Part 3
Creating Cloud Users
Now we should be connected as the Exalogic Systems Administrator, so that we can create Cloud Users.  To create the cloud users CloudUser1 and CloudUser2, you can follow these steps.

1. Use the ELAdmin user account to log into the BUI Exalogic Control.
http://<EMOC_IP>
<EMOC_IP> is the IP address that was assigned to the Enterprise Controller, when running ECU to configure and bring up the Exalogic Control.  Use the password “ovsroot”.  This URL is redirected to a more secure URL: https://<EMOC_IP>/emoc

2.  You should get to the home page, click on “Administration” on the left navigation pane.

3. Click on “Local Users”, under the Enterprise Controller.  The Local Users page is displayed.  Before you try to create a user in Exalogic control, make sure that the user exists on the virtual machine, where the Enterprise Manager Ops Center Enterprise Controller is running.

4. Click the “Add Users” icon, under “Users and Notification Profiles”.  You can also click on “Add User” on the “Operate pane”.  Either way the Add User screen is displayed.   

5. Do the following to add a cloud user.
   . In the user name (CloudUser1) in the User Name field.
   . From the list of Available Roles, and select the Cloud User role, and move it to the Selected Roles by clicking the right arrow.
   . Click on the “Add User” button.  The Cloud User CloudUser1 is created.  You will find the user CloudUser1 listed in the Users and Notification Profiles page.

6. Do the same to create Cloud User “CloudUser2”, with Cloud User permissions.

Adding Users from a Directory Server
It is possible to add a Directory Server to Exalogic control.  Then users and roles can be added to the Exalogic Control from the directory server.  When users are added from a Directory Server, they to start with will have a complete set of privileges, for each of the roles that have been assigned to them. 

Before you add the remote Directory Server to Oracle Exalogic Control, you must configure it:
1. Start by creating the following user groups on the Directory Server:
   . EXALOGIC_ADMIN
   . CLOUD_ADMIN
   . CLOUD_USER

2. Now you continue by adding users to these groups.  The users within each of the groups are given the corresponding role.

Adding a Directory Server
There are a few steps to add a directory in Exalogic Control.
1. Log into the BUI of Exalogic Control with the root user.  http://<EMOC_IP>.
<EMOC_IP> is the IP address that was assigned to the Enterprise Controller, when running ECU to configure and bring up Exalogic Control.  Use the password “ovsroot”.  The URL is redirected to:
https://<EMOC_IP>/emoc

2. Select “Administration” in the Navigation Pane.

3. Click on the “Directory Servers” entry.

4. Click on the “Add Directory Server” icon.  The Remote Directory Server Connection Settings page is displayed. 

5. You will need to enter the connection settings:
Name
This is the name of the Directory Server
Hostname
The Host Name of the Directory Server
Port
The port number that is going to be used to access the directory server
Use SSL
Select this option, if you want to use SSL to connect to the directory server
Username
The user name to be used to access the directory server
Password
The password to be used to access the directory server

6. Click on the Next button.  The Remote Directory Server Schema Settings page is displayed.

7. You need to enter the following schema settings:
Root suffix
This is the root node of the directory tree for the user search
User search DN
This is the subnode in which to search for users
User search scope
This is the scope for the user search.  Acceptable values are
base
one
subtree
baseObject
singleLevel
wholeSubtree
subordinateSubtree
User search filter
This is a LDAP search filter which users must meet for inclusion

8.  Click on the Next button.  The summary page is displayed.

9. Now you need to review the summary.  When you are finished you can click on “Add Directory Server”.

Synchronizing Remote Users and Roles
You can synchronize Exalogic Control with one of the directory servers, or with all of the directory servers.  This process will update the list of users and roles to match the directory server’s current information.

To synchronize Exalogic Control with a single directory server you can follow the following steps:
1. Log into the BUI of Exalogic Control with the root user account.  http://<EMOC_IP>, and use the ovsroot password.

2. Select “Administration” from the Navigation pane.

3. Click on “Directory Servers”.  The list of directory servers is displayed.

4. From the list select a Directory Server and click on the “Sync Remote Users and Roles” icon.  A confirmation window is displayed.

5. Click on the OK button.

Synchronizing Exalogic Control with all Directory Servers
You should synchronize the Exalogic Control with all the directory servers as follows:
1. Log in to the BUI Exalogic Control with the root user account.  http://<EMOC_IP>
Use the password ovsroot.

2. Select “Administration” from the Navigation pane.

3.  Click on “Directory Servers”.  The list of directory servers is displayed.

4. In the Actions pane, click on “Sync All Remote Users and Roles”.  A confirmation windows will be displayed.

5. Click on the OK button and you are done.

Roles and Permissions
Exalogic Systems Administrator
Exalogic Systems Administrator has the following permissions:
READ
WRITE
ASSET_MGMT
CREDENTIAL_MGMT
DIRECTORY_SERVER_MGMT
JOB_MGMT
NETWORK_DOMAIN_CREATION
NETWORK_DOMAIN_DELETION
NETWORK_DOMAIN_MGMT
NETWORK_DOMAIN_USAGE
OVM_MANAGER_MGMT
OVM_MANAGER_USAGE
PDU_MGMT
PDU_USAGE
PROFILE_PLAN_MGMT
REPORT_MGMT
SERVER_DEPLOYMENT
STORAGE_MGMT
NETWORK_MGMT
NETWORK_CREATION
NETWORK_DELETION
NETWORK_USAGE
FABRIC_CREATION
FABRIC_DELETION
FABRIC_MGMT
FABRIC_USAGE
STORAGE_CREATION
STORAGE_DELETION
STORAGE_USAGE
PROXY_CONTROLLER_MGMT
USER_MGMT
ROLE_MGMT
SERVICE_REQUEST
STORAGE_SERVER_USAGE
STORAGE_SERVER_MGMT
SERVER_USAGE
SERVER_MGMT
OPERATING_SYSTEM_USAGE
OPERATING_SYSTEM_MGMT
SWITCH_USAGE
LINK_AGGREGATION
UPDATE_FIRMWARE
OPERATION_EXECUTION
EC_REGISTRATION
EC_HTTP_PROXY_MGMT
EC_ENERGY_COST_MGMT

Cloud Administrator
Cloud Administrator has the following permissions:
READ
SERVER_POOL_MGMT
SERVER_POOL_USAGE
VIRTUALIZATION_HOST_MGMT
VIRTUALIZATION_HOST_USAGE
VIRTUALIZATION_GUEST_CREATION
VIRTUALIZATION_GUEST_DELETION
VIRTUALIZAITON_GUEST_MGMT
VIRTUALIZATION_GUEST_USAGE
STORAGE_MGMT
STORAGE_USAGE
NETWORK_MGMT
NETWORK_USAGE
FABRIC_MGMT
FABRIC_USAGE
LINK_AGGREGATION
IPMP_GROUPS
SERVER_MGMT
SEVER_USAGE
OPERATING_SYSTEM_USAGE
OPERATING_SYSTEM_MGMT
STORAGE_SERVER_USAGE
SWITCH_MGMT
SWITCH_USAGE
CLOUD_MGMT
WRITE

Cloud User
Cloud User has the following permissions:
READ
VIRTUALIZATION_GUEST_MGMT
VIRTUALIZATION_GUEST_USAGE
STORAGE_USAGE
NETWORK_USAGE
FABRIC_USAGE
SERVER_USAGE
OPERATING_SYSTEM_USAGE
OPERATING_SYSTEM_MGMT
STORAGE_SERVER_MGMT
STORAGE_SERVER_USAGE
SWITCH_USAGE
CLOUD_USAGE
WRITE

Franz Devantier,
Need a database health check, or a security audit?
devantierf@gmail.com