Em12c Dbaas Cookbook 1432364
Transcript of Em12c Dbaas Cookbook 1432364
An Oracle Technical White Paper
December 2011
Database as a Service using Oracle Enterprise Manager
12c Cookbook
Table of Contents PREFACE ........................................................................................................................................................ 1
ABOUT ORACLE ENTERPRISE MANAGER DATABASE CLOUD ........................................................................ 2
Oracle Enterprise Manager ....................................................................................................................... 2
Database as a Service (DBaaS) .................................................................................................................. 2
Cloud Management Self Service Portal .................................................................................................... 3
Database Self Service Portal for End-User .................................................................................................... 3
SETTING UP THE DATABASE CLOUD SELF SERVICE PORTAL ......................................................................... 4
Preparing the Database Servers for Privilege Delegation ......................................................................... 4
Preparing Enterprise Manager for Privilege Delegation ........................................................................... 4
Configure Privilege Delegation for Database Servers ........................................................................... 4
Define a Named Credential for Database Cloud Self Service................................................................ 6
Configuring the Software Library .......................................................................................................... 8
Defining Roles and Assigning Users ........................................................................................................ 11
Creating a Cloud User Role ................................................................................................................. 11
Creating an end-user with Cloud User role ......................................................................................... 12
Creating a Database Zone ....................................................................................................................... 15
Configure Request Settings ..................................................................................................................... 19
Configure Quotas .................................................................................................................................... 20
Create Service Templates ....................................................................................................................... 22
Customizing a Create Database Deployment Procedure .................................................................... 22
Creating a Service Template ............................................................................................................... 33
Configuring Chargeback .......................................................................................................................... 35
Chargeback and Database Cloud Self Service Portal .......................................................................... 36
Defining a Universal Charge Plan ........................................................................................................ 36
Create an Extended Charge Plan......................................................................................................... 38
Create a Business Hierarchy of Cost Centers ...................................................................................... 42
Turn Data Gathering on for Targets .................................................................................................... 44
Assign a Charge Plan to a Target ......................................................................................................... 46
Assign a Cost Center to a Target ......................................................................................................... 48
PROVISIONING A DATABASE USING SELF SERVICE PORTAL ....................................................................... 50
Using the Self Service Portal for the First Time ...................................................................................... 50
Provisioning a Database .......................................................................................................................... 52
Shutting Down or Starting Up the Newly Created Database .............................................................. 56
Connecting to the Newly Created Database ....................................................................................... 57
Deleting a Provisioned Database ........................................................................................................ 57
Scheduled Database Retirement ........................................................................................................ 58
CHARGEBACK MONITORING ....................................................................................................................... 59
Chargeback Monitoring for Cloud Users ................................................................................................. 59
Chargeback Monitoring for Cloud Administrators .................................................................................. 60
Page 1
PREFACE
This document explains the steps in provisioning a database using Oracle Enterprise Manager’s
Database Cloud feature. These steps include:
Security Configuration for Named Credentials, Roles and Accounts for Cloud
Management
Customizing database creation procedures to your environment and business
requirements
Setting up the Database Zones
Setting quota limits for each cloud management roles
Definition of Service Templates to be used for database instance creation
Configuring chargeback policies for your database cloud infrastructure
Pre-requisites
This document assumes that, the following pre-requisites have been met:
1. An Oracle Management Server (OMS) is already in place, and the database servers are
configured as EM Hosts with the appropriate OMS Agents. The agent software for
required platforms can be downloaded using Setup->Extensibility->Self Update.
2. The mandatory patch (13031985) has been applied to the Oracle Management Server
(OMS).
3. This feature supports database versions 10.2.0.4 and greater. So install media or
software for all database components has been download and staged for provisioning
use. For example, Grid Infrastructure to setup Clusterware and Automatic Storage
Management (ASM), and Oracle database software to setup Oracle Homes.
4. Adequate storage space has been made available on the OMS for configuration of
Software Library location. Typically, a minimum 50 GB for test environments and well in
excess of 100 GB for production.
For more details on OMS installation and configuration, please see Oracle Enterprise Manager
Cloud Control Documentation from http://download.oracle.com/docs/cd/E24628_01/index.htm
Page 2
ABOUT ORACLE ENTERPRISE MANAGER DATABASE CLOUD
Oracle Enterprise Manager
Oracle Enterprise Manager is Oracle’s premiere cloud management solution. It is the industry’s
first complete solution including self-service provisioning balanced against centralized, policy-
based resource management, integrated chargeback and capacity planning and complete
visibility of the physical and virtual environment from applications to disk.
More information about Enterprise Manager’s Cloud Solution can be found on OTN:
http://www.oracle.com/technetwork/oem/cloud-mgmt-496758.html
Database as a Service (DBaaS)
Oracle Cloud Management Pack for Oracle Database delivers capabilities spanning the entire
Database cloud lifecycle. It lets Cloud administrators identify pooled resources, configure role-
based access, define the service catalog, and the related chargeback plans. It allows Cloud
users to request database services, and consume them on-demand. It also allows for users to
scale-up and down their platforms to adapt to changes in workload. Finally, it lets both parties to
understand the costs of the service delivered, and establish accountability for consumption of
resources.
The key benefit of a database cloud is to enable faster deployment of typical platforms by
moving away from admin driven provisioning to end user driven. Enterprise Manager allows
administrators to:
Pool resources
Standardize and automate deployment processes
Publish established templates to service catalog
Setup role-based access and privileges
Set quotas to limit over-consumption
Establish policies for scale-up and scale-down, and retirement
Enable metering and optional chargeback on consumed resources.
Page 3
Cloud Management Self Service Portal
As for the end-users, Oracle Cloud Management Pack for Oracle Database provides an out-of-
the-box Self Service Portal. Cloud users are presented with a Graphical User Interface to
provision database services without the need for deep technical knowledge on the Hardware
and Software Infrastructure. Self Service Portal enables cloud users to:
Monitor resource allocation
Request and Provision Database Services
Monitor performance of provisioned database
Control availability of provisioned database through simple STARTUP / SHUTDOWN
push buttons
Push Button Retirement of database services that will no longer be used
Database Self Service Portal for End-User
Page 4
SETTING UP THE DATABASE CLOUD SELF SERVICE PORTAL
The Self Service Portal allows administrators to configure the cloud and define policies for the
cloud, expose it to certain users and decide the total amount of resources each user can
reserve, and so on. Users can login to the Self Service Portal and provision the database they
need, without the need for deep technical knowledge on the inner working of the database
management system. The user can even define the time when the database will be retired
automatically.
Before the Self Service Portal can be used, the user privileges, user quota, roles for zone
access, and chargeback mechanism must be defined. Follow this process to set up and
configure the Self Service Portal.
Please refer to the URL below for more detailed documentation in setting up Database as a
Service (DBaaS):
http://download.oracle.com/docs/cd/E24628_01/doc.121/e25179/cloud_part3.htm#sthref164
Preparing the Database Servers for Privilege Delegation
Privilege delegation allows a logged-in user to perform an activity with the privileges of another
user. Sudo and PowerBroker are privilege delegation tools that allow a logged-in user to be
assigned these privileges. Typically, the privileges that are granted to a specific user are
administered centrally.
For example, the sudo command can be used to run a script that requires root access:
sudo root root.sh
The Operating System (OS) Account to be used by Oracle Enterprise Manager (i.e. oracle)
must be configured either for Sudo or PowerBroker.
Please see your Sudo or PowerBroker documentation for detailed setup and configuration
information.
Preparing Enterprise Manager for Privilege Delegation
Enterprise Manager preferred credentials allow you to use two types of privilege delegation
tools: Sudo and PowerBroker.
To configure Privilege Delegation, login as a Super Administrator (i.e. Sysman) in Enterprise
Manager
Configure Privilege Delegation for Database Servers
1. From the Setup menu, choose Security and then Privilege Delegation.
Page 5
2. For any host target appearing in the table, click Edit. Enterprise Manager takes you to
the Host Privilege Delegation Setting page.
3. Select a privilege delegation type (Sudo or PowerBroker).
4. Enter the privilege delegation command to be used and, in the case of PowerBroker, the
optional Password Prompt.
5. Click Update to apply the settings to the host.
Page 6
Define a Named Credential for Database Cloud Self Service
1. From the Setup menu, choose Security and then Named Credentials
2. Click Create button
3. Fill up the form with the appropriate details.
Note that Global Credentials are only applicable to Host with identical credential
properties (i.e. OS username and password). Otherwise, you will have to create a
separate Target Credential for each Host with distinct credential properties.
Page 7
The example below assumes that (most of) your database servers uses “oracle” service
account, identical password, and with sudo run privilege to run as root.
4. Click Test and Save button.
5. You will then be prompted for a Test Target Host. Select a database server from the list
and click Test and Save.
6. After the confirmation, click Manage Access button.
Page 8
7. Click Add Grant
8. Assign to the appropriate users, then click Select button.
9. Once all appropriate users and/or roles are granted access, click Save Button
10. This complete the process of Named Credential configuration
Configuring the Software Library
Oracle Software Library (Software Library) is a repository that stores software patches, virtual
appliance images, reference gold images, application software and their associated directive
scripts. It allows maintaining versions, maturity levels, and states of entities. The software
entities can be automatically mass-deployed to provision software, software updates, and
servers using Enterprise Manger Cloud Control in a reliable and repeatable manner. These
provisioning operations, which are unattended and can be scheduled, lead to substantial cost
savings.
Besides acting as a repository for certified software entities, the Software Library is a logical
interface between the deployment models and the automation framework required to perform a
large number of patching and provisioning tasks. To configure the storage location for the
Software Library, follow these steps:
Page 9
1. Log into Enterprise Manager as an EM_CLOUD_ADMINISTRATOR user or as a Super
Administrator.
2. Click Setup > Provisioning and Patching > Software Library.
3. Select OMS Shared File System in the Storage Type drop down box and click Add
4. Specify a Name and Location that is accessible to all Oracle Management Servers
(OMSes) and click OK.
Page 10
Note:
As the storage location for the Software Library must be accessible to all OMSes as
local directories, in a multi-OMS scenario, you must set up a clustered file system using
OCFS2 or NFS. For single OMS systems, any local directory is sufficient.
5. A job is executed to upload all the out-of-box content.
This may take 15 to 30 minutes depending on your disk speed.
Page 11
Defining Roles and Assigning Users
Roles are named groups of related system and object privileges. You can create roles and then
assign them to users and to other roles. You can assign any of the existing roles to a new role
and the associated privileges
When creating Database Zones and Service Templates, selective access can only be granted
to custom roles. You will not find any pre-defined roles from the list.
Creating a Cloud User Role
Cloud Management Self Service Portal is intended for end-users to be able to provision and
manage their own cloud services. As such, end-users need only access to the Self Service
Portals and the resources they are assigned to. Such capabilities are inherent in the pre-defined
EM_SSA_USER role. However, pre-defined roles cannot be assigned to Database Zones and
Service Templates. Hence, you will need to create a custom Cloud User role based on the
standard EM_SSA_ROLE role.
Log into Enterprise Manager as a Super Administrator
1. Click Setup > Security > Roles
2. Click Create to launch the Create Role wizard
3. Provide a meaningful Name and Description to the custom role, and click Next
4. From the list of Available Roles, select the EM_SSA_USER role, Move it to the
Selected Roles table and click Next
Page 12
5. Accept the default target privileges and click Next.
6. Accept the default resource privileges and click Next.
7. Skip the Create Role: Administrators step and click Next.
8. Review all the changes and click Finish to create the Cloud User Role
(i.e. DBAAS_CLOUD_USERS)
Creating an end-user with Cloud User role
It is highly recommended for each end-user to have its own Cloud User credentials. This is for
effective monitoring of services and resource utilization.
Log into Enterprise Manager as a Super Administrator user (i.e. SYSMAN)
1. Click Setup > Security > Administrators.
2. Click Create in the Administrators page to launch the Create Administrator wizard.
Page 13
3. Enter the name and password for the role and create Next.
4. From the list of Available Roles, select the custom cloud user role you’ve created
earlier (i.e. DBAAS_CLOUD_USERS) and Move it to the Selected Roles table. Click
Next. For Self Service Portal’s end-users, it is prudent to revoke any other roles.
5. Accept the default target privileges and click Next.
Page 14
6. Accept the default resource privileges and click Next.
7. Review all the changes and click Finish to create the end-user account.
8. Create additional end-user accounts as necessary.
Page 15
Creating a Database Zone
A database zone is a collection of servers or clusters with pre-installed database software. Each
servers in a database zone have identical platform and database version. For servers that
support multiple Oracle Homes with different versions, a separate database zone must be
created for each database version.
To create a Database Zone, you must login using any account with
EM_SSA_ADMINISTRATOR role (or SYSMAN).
1. Click Setup > Cloud > Database
2. Click Database Zones
3. Click Create
4. In the Create New Database Zone: Name page, enter a name and description for the
zone, and specify appropriate values for placement policy constraints based on the
resources available to the members. The EM_SSA_ADMINISTRATOR can use the
placement policy constraints to set maximum ceilings for any host in the zone.
Placement policy values are used during deployment to filter out hosts that are
overburdened. You can define the following placement policy constraints for each host:
Page 16
Maximum CPU Utilization: The average CPU utilization percentage over a
specified period.
Maximum Memory Allocation: The average memory allocation over a specified
period.
Maximum Number of Database Instances: The maximum number of database
instances that can be running on the host.
Select the Target Type as Oracle Home. Select the Platform, Configuration (Single
Instance Database or Real Application Cluster), and Version. Select the Named
Credentials for all Oracle Homes in the zone. This Named Credential is used during
database creation in the zone. Click Add to add more targets to the zone. Click Next
5. Select the Target Type as Oracle Home. Select the Platform, Configuration (Single
Instance Database or Real Application Cluster), and Version.
6. Select the Named Credentials for all Oracle Homes in the zone. This Named Credential
is used during database creation in the zone.
7. Click Add to add more targets to the zone.
8. Click Next.
Page 17
Note: For a RAC database, you need to enumerate all the participating nodes in the cluster.
9. A database zone can be made available to a restricted set of users through the use of
roles. Click Add to add the roles that can access this database zone.
Page 18
10. Note that only custom roles are available for selection. Select the appropriate roles and
click Next.
11. Click Submit to create the zone and return to the Database Cloud Self Service Setup
page.
Page 19
Configure Request Settings
1. Click Setup > Cloud > Database
2. Click the Request Settings tab. Review the defaults for Future Reservation and Request
Duration, set appropriate values, if required, and click Apply.
Page 20
Configure Quotas
Quota is the aggregate amount of resources that can be granted to each self service user
belonging to a certain role. This quota applies only to the database provisioned through the Self
Service Application
1. Click Setup > Cloud > Database
2. Click Quotas
3. Click Create
4. In the Create New Quota window, select the Role Name for which the quota is to be
granted. Note that only roles with EM_SSA_USERS privilege can be selected. In our
example, EM_SSA_USERS privilege was assigned to custom EM_CLOUD_USERS
role.
Page 21
Quotas can be based on the following:
Total allocated memory that can be assigned for all the databases owned by a
specific user.
Total allocated storage that can be assigned for all the databases owned by a
user.
The number of databases that can be owned by a user at any point in time.
5. Assign Quotas for each Roles that will be given access to Database Zones
Page 22
Create Service Templates
A service template is a standardized service definition that can be used self service users. You
can create service templates that can be used to provision databases in a set of selected zones.
Before you create a service template, you must have saved a copy of a Create Database
Deployment Procedure with appropriate values.
Customizing a Create Database Deployment Procedure
Login as an Enterprise Manager Administrator (i.e. Sysman)
1. Click > Enterprise > Provisioning and Patching > Database Provisioning
2. From the list of Deployment Procedures, select “Create Oracle Database” and click
Launch
Page 23
3. Make sure that the Database Version and Database Type will match the Version and
Configuration defined during Database Zone creation.
4. Add at least one Host
Page 24
5. Lockdown the Database Version and Type by clicking the PADLOCK ( ) button.
Page 25
Note: For a RAC Database, you need to identify the cluster and the reference node:
6. Click Next
7. Select a Database Template, lockdown your selection and click Next
Page 26
8. Specify any valid Database Name. Note that when you provision a database via Self
Service Portal, the database name will be automatically derived, overriding whatever you
specify here.
9. Specify Database Credentials, take note of the password, and lockdown selection
Page 27
Note: For a RAC Database, you will need to select the configuration type and cluster nodes
10. Click Next
11. Specify Storage Type and lockdown values
12. Specify Storage Location
13. Specify Recovery Files Location and lockdown values
Page 28
Page 29
Note: For a RAC database, you will need to specify a common location for database files
14. Specify Memory Management Settings and lockdown values
15. Specify block size, processes parameters and lockdown values
16. Specify the number of CPU to be allocated for each database, and lockdown values
17. Specify Character Set and lockdown values
18. Specify Database Connection Mode and lockdown values
19. Click Next
Page 30
20. Click Next
21. Specify Listener configuration and lockdown values
22. Lockdown custom scripts
23. Click Next
Page 31
24. On the Schedule screen, click Next
25. On the Review screen, DO NOT SUBMIT the job. Click Save Button Instead
Page 32
26. Specify name for your Deployment Procedure and click Save
27. After saving your Deployment Configuration, click Cancel
Page 33
28. Create additional Custom Deployment Procedures as necessary
(i.e. for TINY, SMALL, MEDIUM, LARGE database deployments)
Creating a Service Template
Now that you have customized your own Create Database Deployment Procedure, you may
now assign this to a service template. Login as an Enterprise Manager Administrator (i.e.
Sysman)
1. Click > Setup > Cloud > Database
2. Click Service Templates
3. Click Create
4. Provide an appropriate name, select your custom deployment procedure, provide a
detailed description and click Next
Page 34
5. Add one or more database zone that will make use of this template, and click Next
6. Add one or more roles that will have access to this template, and click Submit
Page 35
7. Create as many service templates as necessary
Configuring Chargeback
Chargeback, as the name implies, is a tool of accountability. The application's primary uses can
generally be described as follows:
Provide resource usage metering by aggregating and normalizing the enormous amount
of metric data Enterprise Manager collects.
Provide IT a means to "charge" a dollar amount to internal organizations that use
resources.
Provide internal organizations and users with reports detailing their consumption and
charges.
Chargeback has three universal metrics against which to compute resource consumption: CPU
usage, and memory and storage allocation. These three comprise the universal charge plan that
can be applied to any target type signed up for Chargeback services. Given the variety of
processor architecture, the universal plan can bill different rates based on CPU model.
In addition, you can create extended charge plans that apply target-specific charges. Extended
charge plans provide flexibility in how you bill for services, allowing you to:
Override or adjust universal plan rates
Establish different rates based on target configuration
Charge flat and usage-based rates
Chargeback can be configured by a Super Administrator (i.e. SYSMAN) or any user with an
EM_CLOUD_ADMINISTRATOR Role.
Page 36
Chargeback and Database Cloud Self Service Portal
A database zone set up for chargeback automatically includes all of its contained database
instances and RACs as nested targets. Database zones appear under the Databases target
type category on the Chargeback Targets tab. New members added to a zone are automatically
recognized by Chargeback at the next data collection cycle. Note, however, that if a member
target was already set up for chargeback, it must be removed before it can be included as part
of a zone.
When assigning charge plans, a plan assigned to a zone applies to all members within the zone
that do not otherwise have a plan assigned. A cost center can be automatically associated with
a zone as part of SSA setup by setting the cost center target property to an appropriate value.
For resource consumption by internal users, you create a business hierarchy against which to
allocate charges. A business hierarchy consists of cost centers that typically correspond to
business units such as sales, engineering, human resources, and so forth. Cost centers in turn
consist of individual consumers of services within the organization. Use cost centers for rollup
purposes when reporting on usage and charges.
Defining a Universal Charge Plan
1. Click Enterprise > Chargeback
2. Click the Charge Plans Tab
3. Set the rates and charge frequency for the three universal metrics.
Page 37
Note: The rates set here are effective from the beginning of the current month, and have
no impact on any previous month.
a. Select the default CPU row and click Edit.
b. In the dialog that opens, set the rate and charge frequency and then click OK.
c. Set rates and charge frequency for memory and storage allocation in similar
fashion.
d. Make additional entries for different CPU architectures, as required. Click the
Add button.
In the dialog that opens, select the architecture from the drop-down list, set the
rate and charge frequency, and then click OK.
4. You can change the default currency (USD) by clicking the currency symbol and
entering the desired currency symbol in the popup dialog. The new selection becomes
the default currency across all charge plans; that is, the universal plan and all extended
charge plans. All reports, including historical reports, reflect the new currency. No rate
conversion occurs when you change the currency; that is, the numbers stay the same.
Change from dollars to euros and a one dollar charge becomes a one euro charge.
5. Update the rates for existing charge plans as necessary
Page 38
Create an Extended Charge Plan
An extended charge plan allows you to customize how charges accrue.
1. From the Enterprise menu, select Chargeback.
2. Select the Charge Plans tab.
3. In the Extended Charge Plan region, click Create, type a name for the new charge
plan, and then click OK.
4. On the Edit Extended Charge Plan page, click Add. Complete the dialog that opens as
follows:
Page 39
a. Select Database Instance as target type from the drop-down list.
b. Indicate whether it is shared or not
c. Select whether to apply a condition. Default means apply unconditionally.
Conditions give you flexibility. For example, you may want to create many charge
plans with no conditions and assign individually to targets. Or, you can create a
single charge plan with many conditions, and assign to all targets.
The target type selected drives the list of conditions available. Select from the
list, choose an operator, and set the condition value. You can select the condition
value from a list, or choose Specify Value to enter a value.
5. Add Charge Items based on target type for billing purposes. In the Charge Items tab,
click Add. Complete the dialog that opens as follows:
Page 40
a. Select a charge item from the drop-down list. The list of items derives from the
target type. The unit of measure to which the charge applies appears as well,
where applicable (MB, GB, and so forth).
For a shared database, charges are per service.
b. Select the charge type; that is, whether the charge is usage-based, config-based,
or a flat rate. These choices vary, depending on the charge item selected.
c. Specify the rate at which to charge for the item.
d. Select from the drop-down list the frequency at which to apply the charges. It's
not unusual to have different frequencies for charge items within the same target
type, depending on whether the item is a config or metric, and the charge is a flat
rate or usage-based.
e. Click OK.
Page 41
A charge item might effectively be stated in a sentence as: Charge on a weekly
basis a flat rate of a n dollars for every n Hours of CPU Utilization
Repeat this step to include additional charge items.
6. Click Save to create the new extended charge plan.
You can now assign the extended charge plan to a target instance of the appropriate target
type. Remember that extended charge plans are automatically effective from the beginning of
the month.
Page 42
Create a Business Hierarchy of Cost Centers
You can create a business hierarchy by setting up cost centers and assigning users to the
business units.
1. From the Enterprise menu, select Chargeback.
2. Select the Cost Centers tab and then click the Add button.
3. Enter the appropriate information in the New Cost Center dialog:
a. The cost center takes a unique name by which it is known internally in the
system.
b. The cost center also takes a meaningful name that appears in the user interface
and generated reports.
c. Indicate the cost center's position in the tree hierarchy; that is, whether it should
be a top level or a nested level. You can subsequently change its position in the
hierarchy.
Page 43
d. When you click OK. The new cost center appears in the table.
4. With the new cost center row selected in the table, click the Assign to Cost Center
button on the right of the bottom region to add users to the cost center. Provide the
required information in the dialog that opens.
5. Users who are unassigned are designated to a Default Cost Center to which their
charges accrue.
Page 44
6. As the cost centers list grows, you may find that you want to combine cost centers, sales
under marketing, for example.
To do so, drag the Sales cost center over the Marketing cost center and release the
mouse button. Alternatively, select a cost center and click the Move button.In the dialog
that opens, confirm the move operation, or choose another option, such as changing the
parent group.
7. At some point, you may decide to deactivate the cost center. To do so, select the cost
center row and click the Remove button. Indicate whether to deactivate nested cost
centers as well.
Deactivation means the cost center can no longer be assigned to a target, but it remains
active for target assignments in previous report cycles.
Turn Data Gathering on for Targets
Select the targets whose resources you want to manage within Chargeback. You have to add
targets to start collecting metrics against which to calculate charges.
1. From the Enterprise menu, select Chargeback.
2. Select the Targets tab and click the Add Targets button.
3. In the Add Targets dialog, select the targets to manage, and then click OK. If there are
no targets in the list, click the Target Selector button to search for targets to include.
Select the targets in the search results list and click Select.
Page 45
4. In the Add Targets dialog, indicate whether the targets are to be shared across different
cost centers. In particular, databases and WebLogic Servers can be shared. The check
box is disabled if a target is ineligible for sharing. Click OK.
Page 46
5. Selected targets appear in the Target Name column, nested under the major target type
categories (Databases, Middleware, and so forth). Selecting a zone automatically
includes all targets within the zone.
Assign a Charge Plan to a Target
An extended charge plan includes parameters for how to apply universal charge rates to an
assigned target. You also can replace an extended plan by reassigning the universal plan to a
target. A charge plan assigned to a zone applies to all members within the zone that do not
otherwise have a plan assigned.
1. From the Enterprise menu, select Chargeback.
Page 47
2. Select the Targets tab. A hierarchical list of targets appears showing assigned cost
centers and extended charge plans.
3. Select a target in the list and click the Assign Plan button on the right.
4. A dialog opens displaying a list of plans that apply only to the target type selected.
Choose the plan you want to assign and click OK.
5. The table of target assignments refreshes to reflect the assignment. Note that assigning
a charge plan to a composite target (system or group) maps directly to target members.
Page 48
Assign a Cost Center to a Target
Cost centers are a way of distributing charges for resource usage. A cost center target property
automatically assigns a cost center to an SSA target.
1. From the Enterprise menu, select Chargeback.
2. Select the Targets tab. Targets without an explicitly assigned cost center should appear
at the top. When charges are calculated, unassigned targets are assigned to the default
cost center.
3. Select the target to assign (or reassign) to a cost center and click the Assign Cost
Center button on the right.
4. A dialog opens displaying a list of cost centers. Choose the cost center for the target and
click OK. The table of target assignments refreshes to reflect the assignment.
Page 49
5. Note that assigning a cost center to a composite target (system or group) maps directly
to target members. For a composite target other than a system or group, the cost center
assignment is directly to the composite target, and to any children that otherwise have
no direct cost center assignment.
Page 50
PROVISIONING A DATABASE USING SELF SERVICE PORTAL Now that the environment setup is complete, you may now use the Self Service Portal to
provision your database. With the Self Service Portal, cloud users can request a database
through a simple interview process, monitor resource consumptions, and manage the
database through an intuitive graphical user interface.
Using the Self Service Portal for the First Time
1. Logon to Enterprise manager using any of the Cloud User Accounts created earlier.
2. By default, this will take you to the Infrastructure Cloud Self Service Portal, click
Databases on the upper right side to go to the Database Cloud Self Service Portal
Page 51
3. You will now be presented with the Database Self Service Portal Dashboard.
Page 52
Provisioning a Database
1. From the Self Service Portal, click Request Database
2. Select a Service Template from the list, and click OK
Page 53
3. Select a Destination Zone and click Next
4. Enter the Username to be created for this database, provide the default password and
click Next.
Page 54
5. If applicable, indicate when will the Database be created, and the date the database will
be retired. Click Next
6. Review your selections. If satisfied, click Submit
7. You will then be directed back to the Database Self Service Portal where you can
monitor the progress of your request. The process can take a couple of minutes,
depending on the performance and load profile of the Cloud Infrastructure.
The resource utilization chart will also be updated while the database is being created.
Page 55
8. Upon completion of the database request, the portal will list the newly created database.
Click on the database service name to get more details.
Page 56
9. You will then be presented with a single screen to control and monitor the newly create
database, Take note of the connection details which will be required by your database
client software. Use the user credentials provided during database creation.
Shutting Down or Starting Up the Newly Created Database
The cloud user can shutdown or startup the newly created database through the same database
monitoring screen. Just click on the Shutdown button to startup a “Down” database, or bring it
“Up” using the Startup button.
For safety, cloud user will be prompted whether to continue with the startup or shutdown
operation.
Note: Shutting down or starting up a database could take some time.
Page 57
Connecting to the Newly Created Database
The cloud user database monitoring screen also contains important connection details for your
database.
In this particular example, the cloud user is presented with the following details:
Hostname => oraem12c.localdomain
Listener Port => 1521
Database SID => DB29911a
Regardless of database client software to be used, this information, plus the username and
password specified during database creation, is all you need to connect to the new database.
Deleting a Provisioned Database
During database creation, cloud users have an option to provide a retirement schedule, or keep
the provisioned database indefinitely. Either way, cloud users can immediately retire his/her own
database using the Delete button in the Self Service Portal.
As a safety precaution, cloud user will be prompted whether to continue or cancel Manual
Database Deletion.
Page 58
Scheduled Database Retirement
Enterprise Manager will automatically retire a database upon reaching its expiration date.
In the example below, the Self Service Portal indicates that the a database was retired
successfully and is appropriately removed against the Cloud User’s quota.
Page 59
CHARGEBACK MONITORING
Chargeback Monitoring for Cloud Users
Cloud users can monitor the status of their own cloud resource consumption by clicking the
Chargeback Tab from their own Database Cloud Self Service Portal
This particular example also indicates that the user is to be charged $3.53.
Page 60
Chargeback Monitoring for Cloud Administrators
Cloud Administrators can monitor Usage Trend and Charge Trend through the integrated
Chargeback application (Click Enterprise > Chargeback).
Cloud Administrators can also click on the Reports tab for further details on cloud resource
utilization.
Database as a Service using Oracle
Enterprise Manager 12c Cookbook
December 2011
Author: Norman Radan
Contributing Author: Adeesh Fulay
Copyright © 2011, Oracle and/or its affiliates. All rights reserved.
This document is provided for information purposes only and the contents hereof are
subject to change without notice. This document is not warranted to be error-free, nor
subject to any other warranties or conditions, whether expressed orally or implied in law,
including implied warranties and conditions of merchantability or fitness for a particular
purpose. We specifically disclaim any liability with respect to this document and no
contractual obligations are formed either directly or indirectly by this document. This
document may not be reproduced or transmitted in any form or by any means, electronic
or mechanical, for any purpose, without our prior written permission.
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores, CA 94065
U.S.A.
Worldwide Inquiries:
Phone: +1.650.506.7000
Fax: +1.650.506.7200
oracle.com