Specify Basic Service Instance Information

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

On the Instance page of the Instance Creation Wizard, enter basic information for your service instance, including service name, service level, license type, software release, and software edition.
Service Type Components Installed

Service Name

Specify a name that you will use to identify the new service instance. The name must be unique within the identity domain and must meet the following conditions:

  • Must start with a letter

  • Cannot be longer than 30 characters

  • Cannot contain non-alphanumeric character — including spaces.

Service Description

You may add an optional description that can be used to help identify this new service. The description is only used during service list display and is not used internally.

Notification Email

(Optional) Specify an email address where you would like to receive a notification when the service instance provisioning has succeeded or failed.

Region

Select us-phoenix-1, us-ashburn-1, eu-frankfurt-1, or uk-london-1. If you select any other region, the instance will be created in Oracle Cloud Infrastructure Classic.

The Oracle Database Cloud Service deployment that you intend to associate with your Oracle SOA Cloud Service instance must be in the same region that you select in this field.

Availability Domain

Select an availability domain. A region can have multiple isolated availability domains, each with separate power and cooling. The availability domains within a region are interconnected using a low-latency network.

Note that the Oracle Database Cloud Service deployment that you intend to associate with your Oracle SOA Cloud Service instance can be in a different availability domain within the region.

Note:

You cannot distribute an Oracle SOA Cloud Service cluster within a region among multiple availability domains in that region.

Subnet

Select a subnet from a virtual cloud network (VCN) that you had created previously in Oracle Cloud Infrastructure. See Prerequisites for PaaS Services on Oracle Cloud Infrastructure in the Oracle Cloud Infrastructure documentation.

The Oracle Database Cloud Service deployment that you intend to associate with your Oracle SOA Cloud Service instance can be on a different subnet, but it must be in the same region and VCN.

Tags

(Optional) Select existing tags or add tags to associate with the service instance.

To select existing tags, select one or more check boxes from the list of tags that are displayed on the pull-down menu.

To create tags, click Click to create a tag to display the Create Tags dialog box. In the New Tags field, enter one or more comma-separated tags that can be a key or a key:value pair.

If you do not assign tags during provisioning, you can create and manage tags after the service instance is created. See Creating, Assigning, and Unassigning Tags.

SSH Public Key

Specify the value of the VM Public Key, or the name of the file that contains the public key value.

Define the public key for the secure shell (SSH). This key is used for authentication when connecting to the Oracle SOA Cloud Service instance using an SSH client.

Click Edit to display the public key input for VM access and specify the public key using one of the following methods:

  • Select Key File Name and click Browse to select a file that contains the public key for the secure shell (SSH).

  • Select Key Value and paste or type a key value in the text box.

  • Select Create a New Key and click Enter. The Provisioning Wizard generates a key for you. When prompted, save it as a file on your hard drive. Select Key File Name and click Browse to select the file.

License Type

Choose whether you want to leverage the Bring Your Own License (BYOL) option or use your Oracle SOA Cloud Service license.

  • The Bring Your Own License (BYOL) option enables you to bring your on-premises Oracle WebLogic Server licenses to Oracle Cloud. BYOL instances are billed at a lower rate than other instances. See Frequently Asked Questions: Oracle BYOL to PaaS.

    You must own a Universal Credits subscription or Government subscription in order to use BYOL.

    Before you scale out a BYOL instance, you must have enough WebLogic Server licenses for the additional OCPUs that will be allocated to the instance after it is scaled.

  • If you choose to use your Oracle SOA Cloud Service license, your account will be charged for the new service instance according to your Oracle SOA Cloud Service agreement.

If you have both BYOL and Oracle SOA Cloud Service entitlements, BYOL is selected by default, but you can change the license type. If you have BYOL entitlements only, BYOL is selected and you cannot change the license type. If you do not have BYOL entitlements, the Oracle SOA Cloud Service license option is selected and you cannot change the license type.

See Overview of Oracle Cloud Subscriptions.

Software Release

Version 12.2.1.3.0 of WebLogic Server and Fusion Middleware is supported.

Note:

  • You cannot upgrade from 12.2.1 to 12.2.1.2.0 or 12.2.1.3.0. Instead, provision a new instance of 12.2.1.3.0, which provides multinode support.

  • If you provisioned version 12.1.3 and later decided to use version 12.2.1.3.0, the upgrade from version 12.1.3 to 12.2.1.3.0 is not done automatically. You must follow the process described in Upgrading to SOA Suite and Business Process Management 12c (12.2.1).

.