Setup Database as a Service using EM12c Date: 20/11/12 Author: Rob Zoeteweij http://oemgc.wordpress.com This document will guide you through the steps necessary to allow your users to use Database as a Service using EM12c Cloud Control. The Setup of the Database Cloud Before we can start setting up the Database as a Service we need to create a PaaS Infrastructure Zone. For the administrative steps to do the PaaS Infrastructure setup, I have created an Administrator called CLOUD_ADMIN. This Administrator has granted the role EM_CLOUD_ADMINISTRATOR that allows him to setup and deploy the cloud infrastructure (servers, pools, zones) and to perform operations for performance and configuration management. Next we will connect to the EM12c Console as administrator CLOUD_ADMIN. From the Enterprise Menu select Cloud Middleware and Database Home.
Next from the Middleware and Database Cloud menu select Create PaaS Infrastructure Zone. Press [Next] Add those Targets to be included in the PaaS Infrastructure Zone (in this example I have included host myserver1.mycorpdomain.com). Press [Next]
By adding roles we can limit the access to this PaaS Infrastructure Zone. In this example I have add 3 Developer roles. NOTE As this step involves the authorization of users to servers, we might consider assigning this task to a Security Role! Press [Next] After a final review to make sure you have entered everything correctly, press [Submit] to create the Zone.
Next we will perform the same steps to create the PaaS Infrastructure Zone for Production Lifecycle Phase Targets. This Zone will be accessible only by Operation Support Engineers only, as they are the only authorized personnel to access the Production Environment.
Now we have finished setting up the Platform as a Service Infrastructure we can start with the setup of Database as a Service. For the administrative steps to do the DBaaS setup, I have created an Administrator called DBAAS_ADMIN. This Administrator has granted the role EM_SSA_ADMINISTRATOR that allows him to define quotas and constraints for self service users and grant them access privileges. Next we connect to the EM12c Console as the DBAAS_ADMIN administrator:
Next we will navigate Setup Cloud Database Here we need to start to setup our Database Pools. A Database Pool is a collection of Database Servers or Clusters that will participate in your Database As A Service setup. Each of these Servers or Clusters should have the Database Software installed. We will select [Create] to create some of our Database Pools
Note that we will only be able to find homes that are already present on one or more hosts. Press [Submit] to finalize the creation of the Software Pool The next thing to do is the setup of Request Settings
In this example we say that: There are no restrictions in the number of days a user can make any requests There are no restrictions in the number of days before an archived request will be deleted from the system There are no restrictions in the number of days a request can last Next we can set the quota for Memory, Storage and number of Databases per Role that we allow to use (create).
Next for specifying the Service Templates (this will actually give the Self Service Portal user the ability to choose from) we first need to create a specific procedure based on a copy of the Create Database Deployment Procedure: For this we will connect to the EM Console as CLOUD_ADMIN From the Enterprise menu navigate Provisioning and Patching Database Provisioning Select Create Oracle Database and press [Launch]
In this page we have selected database version 11.2.0.3.0 and Locked this field to avoid the Self Portal User to select a different version. By this we actually force 11.2.0.3 to be the standard available database release. We locked the filed by simply clicking the lock icon. We select Oracle Single Instance Database and Lock tis field as well. The Deployment Procedure forces us to select a Host, for the Database to be created on. This is a bit confusing as we want the end user (Self Service Portal user) to select the host to create a database on. Don t worry, the end user will not see this selected Host when he/she executes this procedure, so simply select a Host (does not matter which) and press [Next] to go to the next page.
In this page we will select a Database Template to be used. This would be a DBCA Template we have created before and should have uploaded to the Software Library. As we didn t create such a Template we have selected Select Template From Oracle Home and locked the field. Press [Next] In this page we need to enter a dummy Global Database Name and SID. We enter the Database Credentials and lock the entry of it next Press [Next]
We standardize on using the file system, as on my demo server there is no ASM setup. We will also standardize on the location for the Database Files and as to save resources on my demo environment I choose not to enable Archiving by default. As you notice all entries are locked. Press [Next] In the Initialization Parameters page I enter the desired parameters and lock all entry Press [Next]
As an additional configuration option we specify the name and port of the listener. The procedure assumes that we will create a Listener per OracleHome. Now we will press [Save] to save the Customized Deployment Procedure Press [Save] Press [Cancel] to exit the execution of the procedure
As you can see the Deployment Procedure we have just created is now available in the Software Library. Next we need to grant access to this procedure. Select the procedure and press the [Edit Permissions] button In this example we have granted View privilege to the three Developer administrators We now re- connect to the EM console as the DBAAS_ADMIN administrator to continue the Database as a Service setup Press the [Create] icon to create a Service Template Press [Next]
In this page we have used the [Edit Name and Description] button to provide a description for the Service to be provided through the Self Service Portal and pressed [Finish] to return to this page. Next we have entered the value master and the password to be used for this user and locked both options to enforce this standard. The user master is the name of the user that will be created in the Database and will serve as the primary administrator account for the database. For security reasons, users will not get access to the SYS and system account. Reference Oracle Enterprise Manager Cloud Administration Guide 12c Release 2 (12.1.0.2) Chapter 13 Setting Up and Using the Self Service Application for DBaaS Press [Next] Here we need to define in what Zone the Database Service can be provisioned. Using the [Add] icon we have selected the Development, Test and Acceptance PaaS Infrastructure Zone and using the magnifier icons we have selected the Software Pool to be used.
Using the [Add] icon we have selected the roles that need to be granted access to this service. Press [Next] After reviewing we press [Submit]
Reference Oracle Enterprise Manager Cloud Administration Guide 12c Release 2 (12.1.0.2) Chapter 4 Chargeback Administration Next we select Configure Charge Plan
By selecting a Metric and pressing the [Edit] icon we can set the rates for each of the resource metrics CPU, Memory and Storage In this example we will charge a dollar per day for usage of a CPU, 2 dollars per day for the usage of 2GB Memory and a dollar per day for the usage of 1GB Storage. The Date Range field shows that the Universal Plan settings we just did will be valid from 01- nov- 2012 and onward. Next we will create an Extended Chargeback Plan to charge for usage of Software Licenses and Datacentre facilities (cooling, racks etc.)
Press [Create] to create a new Extended Plan and enter a name for it In this example we have created an Extended Charge plan where we will charge $1 a day for usage of Oracle Database Licenses. In the same example we will charge $1.25 per day for using Oracle Weblogic Licenses. Next we will define Cost Centers to allow Chargeback being based on it In this example we have create a Cost Centre structure with THE BUSINESS as Top and FINANCE and IT underneath Please note that we are also able to base this structure on LDAP integration Next we will assign a Charge Back plan to our Targets
Accessing and using the Self Service Portal We will know connect to the Self Service Portal as user DEVELOPER_FINANCE1
Notice that this user as granted two Roles: EM_SSA_USER to allow access to the Self Service Portal US_FINANCE_DEV to allow access to the Development, Test and Acceptance Lifecycle phase targets owned sued by the FINANCE Line of Business After the Database Cloud has been set up we will now access the Self Service Portal as user DEVELOPER_FINANCE1 We have selected the My Databases option and see that this user has created no Databases yet. We will now request for the creation of a Database by pressing the [Request Database] button
From the Service Template overview we will select the Create Single Instance template and press [Select] We will leave the automatic generated Request Name and select the Development, Test and Acceptance Zone to deploy our database in Press [Next] We will accept the creation of the database administrative user master and press [Next]
As we can t wait to see what will happen, we will schedule for immediate execution Press [Submit] Notice that the creation of the database is In Progress When connected to the EM Console as Super Admin EMADMIN and navigating to Provisioning Procedure Activity, I see the following:
When selecting link DBAAS- CREATE- #3 (in this example) we will get an overview of the Procedure progress After completion of the procedure we re- connect to the Self Service Portal as user DEVELOPER_FINANCE1
Notice that from the Self Service Portal I am able to delete the Database as well. When selecting the database that was just created you will get a complete status overview page, allowing you to Stop / Start the Database.