Skip Headers
Oracle® Enterprise Manager Cloud Administration Guide
12c Release 3 (12.1.0.3)

E28814-10
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

28 Rapid Start Cloud Setup

This chapter describes the rapid start cloud setup kit. It contains the following sections:

28.1 Introduction

Setting up the DBaaS cloud involves a series of steps. The user with the CLOUD_ADMINISTRATOR role has to go through many wizards and clicks to complete the setup. This requires a considerable amount of effort and time before the DBaaS is ready to use.

The Rapid Start Kit provides a single command solution to setup Cloud for Database as a Service (DBaaS) and Pluggable Database as a Service (PDBaaS). One command creates all the Cloud artifacts like Roles, Administrators, Credentials, PaaS Infrastructure Zone, Database Pools and Service Templates. Once the Rapid Start Kit has been successfully executed, requests can be made to provision databases, schemas, and PDBs.

28.2 Installing the Kit

The Rapid Start Kit is shipped along with Oracle Cloud Application 12.1.0.7.0. The kit is available on the Oracle Management Server host with the Oracle Cloud Application 12.1.0.7.0 deployed in plug-in home directory.The Rapid Start Kit can be used from the host on which the Oracle Management Server (OMS) is installed or from any other host that can access Oracle Management Server host using Enterprise Manager Command Line Interface (emcli).

28.2.1 OMS Host

The Rapid Start Kit can be used directly from the host on which the OMS has been installed. No separate installation of the kit is required. The kit is available in the following directory:

EM_BASE/oracle/MW/plugins/oracle.sysman.ssa.oms.plugin_12.1.0.7.0/dbaas/setup

28.2.2 Other Hosts

The kit can also be used from any other host. To install the kit on any other machine, copy the setup directory to the desired location on the target machine.

28.3 Contents of the Kit

The Rapid Start Kit contains the following files:

  • Cloud Setup Script: dbaas/setup/exadata_cloud_setup.py

    This script contains the code for the one command cloud setup. The script uses the input files or the cloud artifacts as defined in the configuration file.

  • Database as a Service Input XML: dbaas/setup/config/dbaas_cloud_input.xml

    The Cloud Setup for Database as a Service uses the dbaas_cloud_input.xml as the input file. The script reads this configuration file and sets up the cloud artifacts as defined in the file.

  • Pluggable Database as a Service Input XML: dbaas/setup/config/pdbaas_cloud_input.xml

    The Cloud Setup for Pluggable Database as a Service uses the pdbaas_cloud_input.xml as the input file. The script reads this configuration file and sets up the cloud artifacts as defined in the file.

28.4 Prerequisites

Certain prerequisites must be fulfilled before running the Rapid Start Kit. This includes OMS setup with correct plug-in versions. Cloud setup can be done on Real application cluster machines with Database instance or Oracle Homes installed. The prerequisites are described in the following sections:

28.4.1 Oracle Management Server

  • The Oracle Management Server must have the Oracle Cloud Application 12.1.0.7 deployed.

  • The Software Library must have been configured.

28.4.2 EMCLI Setup

EMCLI with scripting option must be set up on the host from which the kit is going to be executed. To set up EMCLI on the host, follow these steps:

  1. Download the emcliadvancedkit.jar from the OMS using URL https://<omshost>:<omsport>/em/public_lib_download/emcli/kit/emcliadvancedkit.jar

  2. Set your JAVA_HOME environment variable and ensure that it is part of your PATH. You must be running Java 1.6.0_43 or greater. For example:

    • setenv JAVA_HOME /usr/local/packages/j2sdk

    • setenv PATH $JAVA_HOME/bin:$PATH

  3. You can install the EMCLI with scripting option in any directory either on the same machine on which the OMS is running or on any machine on your network (download the emcliadvancedkit.jar to that machine)

    java -jar emcliadvancedkit.jar client -install_dir=<emcli client dir>

  4. Run emcli help sync from the EMCLI Home (the directory where you have installed emcli) for instructions on how to use the "sync" verb to configure the client for a particular OMS.

  5. Navigate to the Setup menu then the Command Line Interface. See the Enterprise Manager Command Line Tools Download page for details on setting EMCLI.

28.4.3 Infrastructure Setup

To prepare the infrastructure for cloud setup, make sure that the Real Application Cluster machines are available and the required databases and oracle homes have been setup on them. Targets must have been discovered in Oracle Management Server. The following sections describe the setup requirement for PDbaaS and DBaaS.

28.4.3.1 Pluggable Database as a Service

You must ensure that the Real Application Cluster machine is available and has a 12.1.0.1 Container Database version running on it. All the hosts from Real Application Cluster have the Management Agents installed on it. The following targets must be discovered using the guided discovery process:

  • Oracle Cluster

  • Cluster ASM

  • Oracle RAC Database

  • Oracle Database Listerners

28.4.3.1.1 Database as a Service

You must ensure that the Real Application Cluster machine with Oracle home version 12.1.0.1 or 11.2.0.3 installed on it is available.All the hosts in the Real Application Cluster must have the Management Agents installed on it. The following targets must be discovered using guided discovery process:

  • Oracle Cluster

  • Cluster ASM

  • Oracle RAC Database

  • Database Instance

  • Oracle Database Listener

28.5 Artifacts Created by the Rapid Start Kit

The Rapid Start Kit uses cloud input files to create cloud entities. Cloud Input files define the list of entities and input values for each of the entity. See Section 28.3, "Contents of the Kit" for more details on input files. This section explains the Cloud artifacts created as part of cloud setup.

The following actions occur when the Cloud script is executed:

  1. The following roles are created:

    Role Associated System Role
    CLOUD_ADMIN_ROLE EM_CLOUD_ADMINISTRATOR
    SSA_ADMIN_ROLE EM_SSA_ADMINISTRATOR
    SSA_QA_ROLE EM_SSA_USER

  2. The following users are created:

    Administrator / User Associated Role
    CLOUD_ADMIN CLOUD_ADMIN_ROLE
    SSA_ADMIN SSA_ADMIN_ROLE
    SSA_QA1 SSA_QA_ROLE
    SSA_QA2 SSA_QA_ROLE
    SSA_QA3 SSA_QA_ROLE

  3. The following Named Credentials are created:

    Credentials Description
    HOST_CRED Host credentials with host user name and password.
    HOST_CRED_ROOT Host credentials with root access.
    DB_CRED Database access credentials.
    GI_CRED Grid infrastructure owner user.

  4. The quota is set for the SSA_QA_ROLE.

  5. The PaaS Infrastructure Zone is created and the hosts that are part of the Oracle Cluster are added as members of the zone.

  6. The SSA_ADMIN_ROLE creates the following:

    • DBaaS Pool: The DBaaS Pool contains the Oracle Homes from the hosts that are part of the selected zone. The DBaaS Pool is used for Database as a Service.

    • PDBaaS Pool: The PDbaaS Pool has the container database instances from the hosts that are part of the selected zone. The PDBaaS Pool is used for Pluggable Database as a Service.

  7. The SSA_ADMIN_ROLE creates the following:

    • Default Database Service Template: This service template can be used to submit a request for a Database.

    • Default Pluggable Database Service Template: This service template can be used to submit a request for a Pluggable Database.

28.6 Cloud Setup Inputs

The cloud setup requires many user inputs specific to the RAC environment and the cloud artifacts. The Rapid Start Kit has two configuration files that define the cloud input. The following cloud input files are under the configuration directory.

  • dbaas_cloud_input.xml: Defines the cloud artifacts and the input values for Database as a Service.

  • pdbaas_cloud_input.xml: Defines the cloud artifacts and the input values for Pluggable Database as a Service.

Review the cloud input files and map the artifacts with the ones defined in Section 28.5, "Artifacts Created by the Rapid Start Kit". The user marked with cloudadmin="True" is used as the Cloud Administrator to create the PaaS Zone and the user marked as ssaadmin="True" is used to create the Database Pools. All default passwords used by the kit are welcome1.

28.6.1 Pluggable Database as a Service

There is no environment specific value in pdbaas_cloud_input.xml. Pluggable Database as a Service can be run with out of box input xml without any change.

28.6.2 Database as a Service

Database as a service has few environment specific values. User must set them to suite the Real Application Cluster used.

XML Input Edit Guide Line
Pool Filters:

<platform>226</platform>

<version>12.1.0.1.0</version>

Edit the platform value to ARU id of Real Application Cluster machine platform. Use 226 for Linux x86-64 and 267 for Solaris x86.

Edit the database version to the correct value from the database installed on Real Application Cluster machine.

Service Template:<REDO_FILE_LOCATION>RECOSLC16</REDO_FILE_LOCATION>

<RECOVERY_FILE_LOCATION>RECOSLC16</RECOVERY_FILE_LOCATION><DATA_FILE_LOCATION>DATASLC16</DATA_FILE_LOCATION>

Cloud Setup Supports Real Application Cluster with ASM.Specify the disk group names used for Redo files, Recovery files and Data files.

28.6.3 Input Customization

The Rapid Setup Kit supports logical customization of input values. The customer can make a copy of the out-of-the-box input file. Customize the input values logically and pass the modified file to the Rapid Setup Kit.

For example:The user wants to change the Role name from SSA_QA_ROLE to SSA_USER_ROLE. Change should be done as follows:

Original xml tag:

    <role name="SSA_QA_ROLE" description="SSA QA role">
            <systemRoles>
                <systemRole>EM_SSA_USER</systemRole>
            </systemRoles>
            <users></users>
      </role>

Changed tag:

     <role name="SSA_USER_ROLE" description="SSA QA role">
            <systemRoles>
                <systemRole>EM_SSA_USER</systemRole>
            </systemRoles>
            <users></users>
      </role>

The user must look at all the usages of above Role name and change them accordingly. Due to the change in Role name, the following user tag:

<user>        <userName>SSA_QA1</userName>        <passWord>welcome1</passWord>        <email></email>        <contact></contact>        <location></location>        <isSuperAdmin>0</isSuperAdmin>        <lineOfBiz></lineOfBiz>        <costCenter></costCenter>        <description>Cloud user</description>        <!-- system roles or above created role -->        <systemRole>SSA_QA_ROLE</systemRole>    </user>

Must change to use the new role name

<user>
        <userName>SSA_QA1</userName>
        <passWord>welcome1</passWord>
        <email></email>
        <contact></contact>
        <location></location>
        <isSuperAdmin>0</isSuperAdmin>
        <lineOfBiz></lineOfBiz>
        <costCenter></costCenter>
        <description>Cloud user</description>
        <!-- system roles or above created role -->
        <systemRole> SSA_USER_ROLE</systemRole>
    </user>

The user can edit the names and descriptions of Roles, Users, Credential Names, Pool Names and Service template names and their properties defined in the input XML.For example:The user may want to customize the work load to suit the environment for PDBaaS. The user can customize the database SID name and Domain name as follows:Change these tags from dbaas_cloud_input.xml

<COMMON_DB_SID>dbsid</COMMON_DB_SID><COMMON_DOMAIN_NAME>mycompany.com</COMMON_DOMAIN_NAME>

To

<COMMON_DB_SID>hrdb</COMMON_DB_SID>

<COMMON_DOMAIN_NAME>companyname.com</COMMON_DOMAIN_NAME>

Similarly the init parameters for DbaaS can be changed for sga_target and the pga_aggregate_target by editing their values in the dbaas_cloud_input.xml.Some of the values cannot be edited.

For example

<DB_STORAGE_TYPE>ASM</DB_STORAGE_TYPE>

The Rapid Start Kit supports only ASM as the storage type. Hence this cannot be edited.

28.7 Command Line Interface

This section describes step by step instructions for setting up the Cloud using Rapid Start Kit.Make sure all the targets are discovered in Enterprise Manager before starting with Cloud Setup Script.

28.7.1 Usage

-help option describes all the supported options.

Usage: emcli @ exadata_cloud_setup.py
                    -pdbaas
                        This flag is used to setup Cloud for Pluggable Database 
                    -dbaas 
                        This flag is used to setup Cloud for Database as service 
                    -db_list 
Comma separated list of 'Target Name'(s) for 'Cluster Database' targets discovered in Enterprise Manager. 
                        Choose Container Databases for PDbaaS.
Make sure all the Container Databases have same Database credentials and same Host Credentials and are on same platform 
                        e.g -db_list=CDB1,CDB2,CDB3 
                    -host_list 
Comma separated list of 'Target Name'(s) for 'Host' targets discovered in Enterprise Manager. 
                    -db_home_location 
                        Database Home location 
                        e.g -db_home_location=/u01/app/oracle/11.2.0/dbhome1 
                    -cloud_input=<path to custom cloud input xml> 
Cloud input XML defines Enterprise Manager entities created as part of Cloud Setup. 
                        Default file config/dbaas_cloud_input.xml will be used for database setup 
Default file config/pdbaas_cloud_input.xml will be used for pluggable database setup. 
                        Pass custom input xml file to override default input file.
                    -help 
                        Displays Cloud Setup help
    For example: 
       Setup Cloud on Exadata Machine: Run script on first node of Exadata Machine: 
emcli @exadata_cloud_setup.py : Sets up Cloud for PDBaaS if CDB is available in Enterprise Manager. Setups up DBaaS otherwise. 
emcli @exadata_cloud_setup.py -pdbaas : Sets up Cloud for PDBaaS
emcli @exadata_cloud_setup.py -dbaas  : Sets up Cloud for DBaaS
 
Setup Cloud on Non-Exadata Cluster Machine: Run script on cluster node or any standalone Machine. 
emcli @exadata_cloud_setup.py -pdbaas -db_list=CDB1,CDB2,CDB3   : Sets up Cloud for PDBaaS using  given list of Pluggable databases
emcli @exadata_cloud_setup.py -dbaas -host_list=host1,host2 -db_home_location=<oracle home location> : Sets up Cloud for DBaaS using  given list of hosts and oracle home.

28.7.2 Database as a Service (DBaaS)

The following command can be used to setup DBaaS.

ORACLE_HOME/bin/emcli @exadata_cloud_setup.py -dbaas -host_list=" clusterhost1.mycompany.com , clusterhost1.mycompany.com” -db_home_location="/u01/app/oracle/product/12.1.0/dbhome_1"

where the -dbaas flag indicates that this is used set up Database as a Service.

The script retrieves the list of hosts and the location of the Oracle Home. Enter the following input when prompted by the Rapid Start Kit.

User Input Description
Enterprise Manager Host Name Hostname
Enterprise Manager Port Number Port number for the secure port.
Enterprise Manager User Name Enter name of user with administration privileges (sysman).
Enterprise Manager User Password Enter the password for the sysman user.
Password for the CLOUD_ADMIN user This user is created by the kit. The default password is welcome1.
User name for host credentials The name of the user who can access the target host.
Password for host credentials The password required to access the target host.
Monitoring user name for DB_CRED sys
Monitoring password for DB_CRED sys password

If any of the cloud artifacts already exist in Enterprise Manager, the Rapid Setup Kit shows the message and does not create or modify it.The Cloud Setup script can be run again multiple times in case of any failure after fixing the issue. The kit creates the new artifacts and shows the message for already existing ones.

28.7.3 Pluggable Database as a Service (PDBaaS)

The following command can be used to set up PDBaaS.

ORACLE_HOME/bin/emcli @exadata_cloud_setup.py -pdbaas -db_list=pdb

where:

  • the -pdbaas flag indicates that this sets up for Pluggable Database as Service

  • the -db_list parameter passes the list of container databases discovered in Enterprise Manager.

Enter the following input when prompted by the Rapid Setup Kit.

User Input Description
Enterprise Manager Host Name Hostname
Enterprise Manager Port Number Port number for the secure port.
Enterprise Manager User Name Enter name of user with administration privileges (sysman).
Enterprise Manager User Password Enter the password for the sysman user.
Password for the CLOUD_ADMIN user This user is created by the kit. The default password is welcome1.
User name for host credentials The name of the user who can access the target host.
Password for host credentials The password required to access the target host.
Monitoring user name for DB_CRED sys
Monitoring password for DB_CRED sys password

If any of the cloud artifacts already exist in Enterprise Manager, the Rapid Setup Kit shows the message and does not create or modify it.The Cloud Setup script can be run again multiple times in case of any failure after fixing the issue. The kit creates the new artifacts and shows the message for already existing ones.

28.7.4 Securing the Cloud Setup

The Rapid Setup Kit creates the Administrators as part of Cloud Setup. The kit allows the user to secure the cloud setup so that only authorized users can be given access to the selected functionality. If the user opts to secure the Cloud Setup, the passwords for the users created by the kit will automatically expire. Enterprise Manager allows re-setting the password on first login by each user.

28.7.4.1 Expire Default Passwords

The Rapid Start Kit will ask for confirmation and will expire the passwords for all the users that are part of input xml.

28.7.5 Set New Passwords

Administrator should log in to Enterprise Manager as each user is created. Enterprise Manager will ask to set a new password on first login.

Note: If you want to re-run the kit after the passwords have been expired by Rapid Kit, new passwords must be set for CLOUD_ADMIN and SSA_ADMIN users before re-running the Rapid Kit and the new passwords must be used when prompted during the second run.

28.8 Rapid Start Kit Sample Run

This section shows a sample run for Pluggable Database as a Service

$ /scratch/emkitbase/oracle/MW/oms/bin/emcli @exadata_cloud_setup.py -pdbaas -db_list=pdb
===========================================================================
Cloud Setup Tool
===========================================================================
Log in to Enterprise Manager:
==============================
Enter Enterprise Manager Host Name: omshost.mycompany.com
Enter Enterprise Manager Port Number. Hit enter if using portless URL: 7802
Enter Enterprise Manager User Name: sysman
Connecting to Enterprise Manager 'https://omshost.mycompany.com:7802/em'...
  Login in as 'sysman'...
Enter password :  ********
  Login successful
Cloud Setup Inputs:
====================
Cloud Input XML: 'config/pdbaas_cloud_input.xml'
 
Fetching system information from Enterprise Manager...
  Setting up Pluggable Database as a Service (PDBaaS)...
  List of Container Databases for pool creation: pdb
 
+-------------------------------------+-------------------------------------------
|              Node                |               Oracle Home Location          |
+-------------------------------------+-------------------------------------------
| clusterhost1.mycompany.com       | /u01/app/oracle/product/12.1.0/dbhome_1     |
+--------------------------------------+------------------------------------------
| clusterhost2.mycompany.com       | /u01/app/oracle/product/12.1.0/dbhome_1     |
+--------------------------------------+------------------------------------------
Press Enter to continue: 
      Creating Roles...
          Creating Role "CLOUD_ADMIN_ROLE"...
         Role "CLOUD_ADMIN_ROLE" created successfully
          Creating Role "SSA_ADMIN_ROLE"...
         Role "SSA_ADMIN_ROLE" created successfully
          Creating Role "SSA_QA_ROLE"...
         Role "SSA_QA_ROLE" created successfully
      Creating Users...
         Creating User "SSA_ADMIN"...
         Created User "SSA_ADMIN" with Role(s):{SSA_ADMIN_ROLE}
         Creating User "CLOUD_ADMIN"...
         Created User "CLOUD_ADMIN" with Role(s):{CLOUD_ADMIN_ROLE}
         Creating User "SSA_QA1"...
         Created User "SSA_QA1" with Role(s):{SSA_QA_ROLE}
         Creating User "SSA_QA2"...
         Created User "SSA_QA2" with Role(s):{SSA_QA_ROLE}
         Creating User "SSA_QA3"...
         Created User "SSA_QA3" with Role(s):{SSA_QA_ROLE}
 
Connecting to Enterprise Manager 'https://omshost.mycompany.com:7802/em'...
  Login in as 'CLOUD_ADMIN'...
Enter password :  ********
  Login successful
      Creating Credentials...
Do you want to use same username and password for all credentials with 'Authenticating Target Type' as 'host'? (yes/no) [yes]: yes
         User selected same credential for 'Authenticating Target Type' as 'host'.
Enter User Name for Host Credentials: oracle
Enter Password for Host Credentials: 
Warning: Problem with getpass. Passwords may be echoed.
         Creating Credential "HOST_CRED"...
         Credential HOST_CRED created.
         Credentials "HOST_CRED:CLOUD_ADMIN" tested successfully
         Creating Credential "HOST_CRED_ROOT"...
         Credential HOST_CRED_ROOT created.
         Credentials "HOST_CRED_ROOT:CLOUD_ADMIN" tested successfully
         Creating Credential "GI_CRED"...
         Credential GI_CRED created.
         Credentials "GI_CRED:CLOUD_ADMIN" tested successfully
      Creating Quotas...
         Creating Quota for Role: SSA_QA_ROLE
         Quota for Role "SSA_QA_ROLE" setup successfully.
         Creating zone "DBaaS Zone"...
         PaaS Infrastructure Zone "DBaaS Zone" created successfully.
Connecting to Enterprise Manager 'https://omshost.mycompany.com:7802/em'...
  Login in as 'SSA_ADMIN'...
Enter password:  ********
  Login successful
      Creating Credentials...
Do you want to use same username and password for all credentials with 'Authenticating Target Type' as 'host'? (yes/no) [yes]: yes
         User selected same credential for 'Authenticating Target Type' as 'host'.
Enter User Name for Host Credentials: oracle
Enter Password for Host Credentials: 
Warning: Problem with getpass. Passwords may be echoed.
         Creating Credential "HOST_CRED"...
         Credential HOST_CRED created.
         Credentials "HOST_CRED:SSA_ADMIN" tested successfully
         Creating Credential "HOST_CRED_ROOT"...
         Credential HOST_CRED_ROOT created.
         Credentials "HOST_CRED_ROOT:SSA_ADMIN" tested successfully
         Creating Credential "GI_CRED"...
         Credential GI_CRED created.
         Credentials "GI_CRED:SSA_ADMIN" tested successfully
Enter Monitoring User Name for 'DB_CRED'[sys]: sys
Enter Monitoring Password for 'DB_CRED': 
Warning: Problem with getpass. Passwords may be echoed.
         Creating Credential "DB_CRED"...
         Credential DB_CRED created.
         Creating pool "PDBaaS Pool"...
         Software Pool "PDBaaS Pool" created successfully.
      Creating Pluggable Database Service Template...
         Creating PdbaaS Service Template...
         Service Template "Default Pluggable Database Service template" created successfully.
Securing Cloud setup...
Do you want to expire passwords for the users created by setup?(yes/no) [yes]: yes
Connecting to Enterprise Manager 'https://omshost.mycompany.com:7802/em'...
  Login in as 'sysman'...
Enter password :  ******** 
 
  Login successful
         Expiring Password for "SSA_ADMIN"...
         User "SSA_ADMIN" modified successfully
         Expiring Password for "CLOUD_ADMIN"...
         User "CLOUD_ADMIN" modified successfully
         Expiring Password for "SSA_QA1"...
         User "SSA_QA1" modified successfully
         Expiring Password for "SSA_QA2"...
         User "SSA_QA2" modified successfully
         Expiring Password for "SSA_QA3"...
         User "SSA_QA3" modified successfully
Cloud Setup Summary:

+--------------------------------+------------------------------------------+-----
|       Type               |     Cloud Entity        |         Status           |
+--------------------------------+------------------------------------------+-----
|      Role                |     SSA_ADMIN_ROLE      |  Created                 |
---------------------------------------------------------------------------------
|      Role                |     SSA_QA_ROLE         |   Created                |
----------------------------------------------------------------------------------
|      User                |     SSA_ADMIN           |Created with              |
|                          |                         |Role(s): SSA_ADMIN_ROLE   |
----------------------------------------------------------------------------------
|      User                |     CLOUD_ADMIN         |Created with              |
|                          |                         |Role(s): CLOUD_ADMIN_ROLE  |
----------------------------------------------------------------------------------
|      User                |     SSA_QA1             |Created with              |
|                          |                         |Role(s): SSA_QA_ROLE      |
----------------------------------------------------------------------------------
|      User                |     SSA_QA2             |Created with              |
|                          |                         |Role(s): SSA_QA_ROLE      |
----------------------------------------------------------------------------------
|      User                |     SSA_QA3             |Created with              |
|                          |                         |Role(s): SSA_QA_ROLE      |
----------------------------------------------------------------------------------
|      Credential          |     HOST_CRED           |     Created              |
----------------------------------------------------------------------------------
|      Credential          |     HOST_CRED_ROOT      |     Created              |
----------------------------------------------------------------------------------
|      Credential          |     GI_CRED             |     Created              |
----------------------------------------------------------------------------------
| PaaS Infrastructure Zone |     DBaaS Zone          |     Created              |
----------------------------------------------------------------------------------
|      Credential          |     HOST_CRED           |     Created              |
----------------------------------------------------------------------------------
|      Credential          |     HOST_CRED_ROOT      |     Created              |
----------------------------------------------------------------------------------
|      Credential          |     GI_CRED             |     Created              |
----------------------------------------------------------------------------------
|      Credential          |     DB_CRED             |     Created              |
----------------------------------------------------------------------------------
|      Software Pool       |     PDBaaS Pool         |     Created              |
----------------------------------------------------------------------------------| PDB Service Template     |     Default PDB Service |     Created              |
----------------------------------------------------------------------------------
Cloud Setup Completed Successfully for Pluggable Database as a Service (PDBaaS)Log in to Oracle Management Server url 'https://omshost.mycompany.com:7802/em' to submit the request for Pluggable Database.