How to Provision an Oracle SOA Cloud Service Environment – SOA

SOA Suite and API Manager Provisioning

Provisioning a SOA environment via SOA CS Console

You will realise very soon that provisioning a DB CS via the Cloud Service Console is almost identical than provisioning Java Cloud Service (JCS) environments, SOA/OSB Cloud Service environments, API Manager Cloud Service environments, etc. It will only change minor configurations that apply to each type of service cloud.

This section will guide you to create a SOA CS environment that will come with SOA and OSB.

• If not already open, Sign in to the My Services application at https://cloud.oracle.com/sign_in
  . The My Services Dashboard appears. Select your availability zone, e.g. US Commercial (us2), and click on Sign In to My Services

• Enter your Identity Domain and click Go

  

• Then enter your username and password and click Sign In.
  We strongly suggest that you use complex passwords and store them all in a secured place where you don’t have to remember them but you can retrieve them anytime/anywhere.
  Tools such as KeePass help those of us who have given up trying to remember our complex passwords.
  For more information about KeePass refer to this website: http://keepass.info/

1. In the Oracle My Service dashboard, locate the Oracle Oracle SOA Cloud Service and click on Service Console.

   

2. Click on Create Instance

   

3. In the Type step, select:
   1. Domain Types: SOA and OSB Cluster

   2. Billing Frequency: Monthly (that’s the only option as of now)

      

      Then click Next.

4. In the Image step, select Oracle SOA Suite and Service Bus 12.1.3 on Oracle Linux 6.4 (it’s the only supported version as of now).
   Then click Next.

   

5. The Details page is where you have to enter most of the environment configuration.
   1. Instance Configuration
      1. Instance Name: Enter a meaningful environment name.
      2. Description: Enter a meaningful description
      3. Cluster size: 2 – This means that the cluster will have 2 managed servers, each running on a separate VM. This will automatically enable the Load Balancer, as you will see below.
      4. Compute Shape: OC1M – 1 OCPU, 15 GB RAM – This means that each Managed Server VM, will have 1 OCPU and 15 GB of RAM.
      5. VM Public Key: Select the “public key” that you generated previously. If you have not created this key pair, refer to section How to create SSH key pair down in the Appendix of this document.

         For example:

         

   2. WebLogic Administrator
      1. User Name: weblogic (change it if you want)
      2. Password and Confirm Password: Do not choose welcome1, as this is going to be a public environment. Choose a stronger password

         For example:

         

   3. Database Configuration
      1. Use the drop down menu and select your DB CS instance.
      2. PDB Name: (which is PDB1, modify if you changed it)
      3. Administrator User Name: SYS

      4. Password: Enter the password that you chose when provisioning the DB

          

         
         

1. Load Balancer
   1. Provision Load Balancer: YesNote: Otherwise you will have to use your own way to balance traffic across your Weblogic cluster.

We recommend that you use the out of the box Load Balancer, which is Oracle Traffic Director (OTD), as the Oracle Cloud Platform will always keep it in sync with your cluster, whether you decide to scale out or in in the future. For more information about the Load Balancer, refer to section Load Balancer in this guide.

• Load Balancer Policy: Round Robin (set as you need)
• Compute Shape: OC3 – 1 OCPU, 7.5 GB RAM – This means that the Load balancer will run on its own VM with those specifications. If you select more than 1 OCPU, you can enable DR at the Load Balancer level.
  More information about this to come as a new section in this document. Contact the document owner for more information.
  

  

• Storage Container Configuration
  1. Storage Container Name: Enter the container name that you created previously.

     Storage-[identity domain]/[container name]
     

     For example: Storage-auoracle02747/dafwaContainer1
     

     Note: If you have not created one read this section in the document:
     

  2. Storage User Name: Enter your OPC account user name
  3. Password: Enter your OPC account password

     For example:

     

1. The overall configuration should look like this:

• Once you are comfortable with it, click on Next, review and click on Create
• It will take a while to create your SOA CS Environment. In the meantime you can check the status in the SOA CS Console

  

• Once it gets provisioned, click on the Environment name, in this case DAFWASOAEnv
  

1. Explore the different sections in this page. Especially take a note to the following information as you will need it in a minute:

1. Public VM IP Address: This will be the VM that you can SSH into in order to gain access to the Operating System where the WebLogic cluster runs. Also it is the VM that contains the WebLogic Admin console and EM Fusion Middleware Control, so you want to remember this IP Address.

• Load Balancer IP Address: This will be the external endpoint for any service or API interaction. You also want to remember this IP Address.
• Finally, click on the Burger icon on the top right corner and notice that you can get access to most of the consoles from here. You might want to access them and bookmark them in your browser, so that you don’t need to come through the SOA CS every time you need to get access to any of them.

Provisioning an API Manager environment via SOA CS Console

The process to provision an API Manager environment is almost the same to provision a SOA environment, the only difference is that you need to choose Domain Type as “API Manager”.
The rest of the steps will be identical as if creating a SOA environment. Obviously you might want to choose a different topology and size (compute shape) depending on your API Manager requirements.

Author: David Reid

Cloud Platform Architect View all posts by David Reid