Following on from my earlier blog post on setting up Pluggable Database as a Service (PDBaaS) in EM 18.104.22.168, this post will cover how you actually use the Self Service Portal to create on demand an empty pluggable database within the container database I created for that earlier post. You’ll no doubt be pleased to know that this post is much shorter! 🙂
The main reason we want to do this, of course, is to automate the more mundane database administration tasks associated with creating a database. If we can leave these sorts of tasks more to the end user, while importantly ensuring they do not have free reign to just go about willy nilly creating databases, it removes these boring tasks from our hands, and at the same time, automates the tasks to ensure correct configuration, performance and so on.
The first step is to login as a Self Service user. You may recall from my earlier post that I created a user called DBaaS, so I’m going to login as that user. I provide the username and password and click “Login”:
This will take me to the bog standard Welcome screen. The first thing I want to do from here is make it easier for this user to get to the right place. Enterprise Manager 12c allows you to define home pages on a per user basis, so I need to get to the Self Service Portal first, by following the path Enterprise → Cloud → Self Service Portal:
Now I can select “Set Current Page as My Home” from the user menu on the top right of the screen next to “Setup” so that next time I login I see this page immediately:
You will see a confirmation message that the Home Page has been updated. Note that the default item to manage on this Infrastructure Cloud Self Service Portal is still set to “Infrastructure – Oracle VM”, so we need to swap that to “Databases” from the Manage dropdown list (unfortunately this can’t be set as a default):
Now I am on the Database Cloud Self Service Portal page, which is where I can see all the information about requests that have already been made. In this case, of course, there are none, so the first thing I need to do is request a pluggable database from the Request dropdown list. Note this is the only request I have available to me at this stage due to the way we defined the DBAAS user in the setup:
I am asked to select a service template from a list of those that have already been defined. Again, the user has only been granted access to one, so I choose that and click “Select”:
Next, I am presented with the “Create Pluggable Database” screen. There are a number of options I need to populate here:
- Request Name – the name given to the Self Service request. This is populated with a default value, but you can of course change that to something more meaningful if you like.
- Zone – The PaaS Infrastructure Zone where the PDB’s for this request will reside. Again, this will be populated by default, based on the zones the user has been given access to. In this case, the user can only use the East Coast Zone I created in my earlier post.
- PDB Name – obviously, the name for the PDB that will be created. Make this something recognizable, rather than something generic like PDB6.
- Database Service Name – Again, use a meaningful service name. This will be used as the service name part of the connect string.
- Workload Size – Defines the resources allocated to the database service name, and is also used to derive the database resource management plan. Again, in this example only one workload is defined.
- Schedule request – The date and time that the request will be scheduled to be created (if not being created immediately), as well as the duration for its lifespan.
- Administrator credentials – The Pluggable Database administrator account which will be created by the request for this PDB.
- Tablespace name – The name of the tablespace to be created as part of this request.
I can enter values for all these fields (or accept the defaults) and then click “Submit”:
Now I am returned to the “Database Cloud Self Service Portal” page, and I can see the request I just created is running:
The default for this page is manual refresh, so I can change that by clicking the “View Data” dropdwon list on the right hand side of the page:
After a few minutes, I’ll see the new service instance listed in the “Database Service Instances” region of the Self Service Portal page:
Notice on the left hand part of the screen, there is additional information pertaining to notification, as well as usage values that will now have changed. Enterprise Manager uses green, yellow and red to indicate usage that is at normal, warning or critical levels. The notification section is designed to alert and notify the Self Service users of pending expirations, as well as any new service templates that have been recently published and available for use. The Usage section provides information regarding current utilization in relationship to the quotas (seen on the right end of each bar) defined by the Cloud Administrator.
If I click on the service instance name, it takes me to the pluggable database page where I can see the connection details that can be used to connect to the database to perform application development tasks:
And that’s it! It’s dead easy, right? Now you can concentrate on the more interesting parts of database administration life, like performance management, configuring high availaiblity, eating donuts – OK, so maybe not eating donuts. 🙂