Provision an Oracle SOA Cloud Service Instance with Stack Manager

Only Oracle Cloud Infrastructure Classic This topic applies only to Oracle Cloud Infrastructure Classic.

Use Oracle Cloud Stack to provision instances of both Oracle SOA Cloud Service and Oracle Database Classic Cloud Service as a single operation.

Oracle Cloud Stack is a component of Oracle Cloud that enables you to create multiple cloud resources as a single unit called a stack. You create, delete and manage these resources together as a unit, but you can also access, configure, and manage them through their service-specific interfaces. Stacks also define the dependencies between your stack resources, so that Oracle Cloud Stack creates and destroys the resources in a logical sequence.

Stacks are created from templates. The Quick Start feature of Oracle SOA Cloud Service uses stack templates so that you can quickly create service instances based on standard configurations.

Oracle Cloud Stack also includes a certified Oracle stack template named Oracle-SOACS-DBCS-Template. This template creates a stack that’s comprised of these resources:

  • A database deployment in Oracle Database Classic Cloud Service

  • A service instance in Oracle SOA Cloud Service that is connected to the database deployment

  • A storage container in Oracle Cloud Infrastructure Object Storage Classic to support cloud backups for the Oracle SOA Cloud Service instance and the database deployment

Get Started

Create a stack using the Oracle-SOACS-DBCS-Template template. Refer to these topics in Using Oracle Cloud Stack Manager:

A video and a tutorial are also available.

Tutorial icon Tutorial

Template Parameters

In the Oracle-SOACS-DBCS-Template template, the values of these input parameters can be customized for each stack creation:

  • Oracle WebLogic Server and Oracle Database versions

  • Oracle WebLogic Server and Oracle Database VM compute shapes (CPU, memory, storage)

  • Oracle WebLogic Server user name

  • Oracle WebLogic Server and Oracle Database system passwords

  • Oracle Database name (SID)

  • Oracle Database usable storage in Gigabytes

  • SSH public key for all nodes

  • Name of the Oracle Cloud Infrastructure Object Storage Classic container to create

  • Storage user name and password

The stack name (the predefined parameter serviceName) is used to name the new services. This stack name is joined with the text SOACS and DBCS.

Create a Stack with the CLI

In addition to the web console, Oracle Cloud Stack supports the same command line interface (CLI) that you can use to create and manage an Oracle SOA Cloud Service instance. Execute the stack create command and specify the template’s name, Oracle-SOACS-DBCS-Template. Provide values for the template parameters, and be sure to properly enclose any values that contain white space or other special characters. For example:

psm stack create -n MyStack -t Oracle-SOACS-DBCS-Template -p commonPwd:"password" backupDestination:"BOTH" backupStorageContainer:"https://acme.storage.oraclecloud.com/v1/MyService-acme/MyContainer" backupStorageUser:"john@example.com" backupStoragePassword:"password" publicKeyText:"key_text"

To identify the parameter names to use with the CLI, view or export the template. See Viewing a Template in Using Oracle Cloud Stack Manager.

Customize the Template

Use Oracle Cloud Stack to copy and update the Oracle-SOACS-DBCS-Template template in order to customize your stack’s behavior. Modify the template’s name and contents, such as adding a template parameter or changing the parameters used to provision the Oracle SOA Cloud Service instance. Refer to these topics in Using Oracle Cloud Stack Manager:

Tip:

While editing a resource in a stack template, place you mouse over a parameter name to view its description.

See below for some examples of customizing this stack template.

Enable Access to the Administration Console

By default, network access to the WebLogic Server Administration Console in an Oracle SOA Cloud Service instance is disabled for security reasons. To enable access to the console after creating a stack, see Access WebLogic Server Administration and OTD Consoles in Oracle Cloud Infrastructure Classic. Alternatively, you can update the template and enable access to the console at the time the service instance is provisioned. Edit the Oracle SOA Cloud Service resource and set enableAdminConsole to true.

Set the WebLogic Server Cluster Size

By default, the Oracle WebLogic Server domain in an Oracle SOA Cloud Service instance contains a single Managed Server to host your Java Enterprise applications. This is appropriate for a development environment, but test or production systems may require a larger cluster of Managed Servers. Oracle SOA Cloud Service allows users to scale out an existing service instance after creating it, but alternatively you can update the stack template. Edit the Oracle SOA Cloud Service resource, expand components and WLS, and then set managedServerCount.

 components: 
   WLS:
     ...
     managedServerCount: 3

Create a Separate Application Database

An Oracle SOA Cloud Service instance requires at least one Oracle Database Classic Cloud Service deployment in order to host the required Oracle schemas. But a new Oracle SOA Cloud Service instance can also connect to a second database deployment (or a second Pluggable Database in the same database deployment) to separate the Oracle schemas from your application schemas. Create a second database resource in your template and associate it with the Oracle SOA Cloud Service instance.

  1. Add a second Oracle Database Classic Cloud Service resource to your template named dbcs2. See Creating Resources in Using Oracle Cloud Stack Manager.

  2. For the database deployment’s serviceName parameter, use the Join function to give the resource a unique name. For example:

    'Fn::Join':
      - ''
      - - 'Fn::GetParam': serviceName
        - DBCSAPP
  3. Edit the Oracle SOA Cloud Service resource, expand components and WLS, and then set appDBs to the following value:

    - dbServiceName:
        'Fn::GetAtt':
          - dbcs2
          - serviceName
      dbaName: sys
      dbaPassword:
        'Fn::GetParam': commonPwd