1. Using Oracle SOA Suite on Marketplace in Oracle Cloud Infrastructure
  2. Create and View Oracle SOA Suite on Marketplace Instances
  3. Provision an Oracle SOA Suite on Marketplace Instance
  4. Provision an Oracle SOA Suite on Marketplace Instance in the Oracle Cloud Infrastructure Console

Provision an Oracle SOA Suite on Marketplace Instance in the Oracle Cloud Infrastructure Console

You can provision an Oracle SOA Suite on Marketplace instance in a selected compartment in Oracle Cloud Infrastructure. The database and Oracle SOA Suite on Marketplace instance can be in the same or different compartment.

Notes:

  • Before you begin these steps, make sure that you have met the necessary Prerequisites.

  • When you provision an Oracle SOA Suite on Marketplace instance with a private subnet, you must select either an existing Private Endpoint or a Bastion VM, or create a new Bastion VM (see Understand Oracle SOA Suite on Marketplace Topologies). The newly created Bastion VM will use an Oracle Linux 7.x image, which is free to use (only the instance's OCPU and memory usage will be billed). The Bastion VM is associated with the Oracle SOA Suite on Marketplace instance stack and will be deleted when the stack is deleted (Terraform Actions > Destroy). You can delete just the Bastion VM once the provisioning process is completed. If you provision another instance in the same subnet, you will need to choose another Bastion VM that is associated to second stack. Note that scale out and scale in operations will create a new Bastion VM if it does not exist. You can delete this Bastion VM after scale out and scale in operations.

  • With administration privileges in Oracle Cloud Infrastructure, you can deprovision compute instances from an Oracle SOA Suite on Marketplace cluster. To delete nodes from a cluster when you no longer need the cluster, it is recommended that you use Terraform Actions > Destroy (see Deprovision an Oracle SOA Suite on Marketplace Instance). As a best practice, use a dedicated compartment for provisioning Oracle SOA Suite on Marketplace compute instances, and restrict administrator access to this compartment. This will ensure that Oracle Cloud Infrastructure Console users cannot delete the instances and administrators will use Terraform Actions > Destroy to terminate instances.

  • If provisioning of an Oracle SOA Suite on Marketplace instance fails, check for the following common causes of failure:

    • Before provisioning in an existing subnet, verify that port 1521 is open for database connectivity in the ingress rules. See Configure Security Lists.

    • If you select a Database Strategy of Database System in the provisioning screens, verify that the following values are correct:
      • the name of the pluggable database (PDB)
      • the Database Administrator Password
    • Verify that the user who submitted the provisioning request is part of the Oracle Cloud Infrastructure IAM Administrator group or part of a group that is authorized to manage network and compute resources.
    • If you select Enable SOA DB Schema Partitioning, verify that the Oracle Database software edition edition is Enterprise Edition High Performance or Enterprise Edition Extreme Performance.
    • If you use a custom DNS resolver and provisioning times out for a cluster with more than 4 nodes, verify that the custom DNS resolver is configured correctly.

    • If provisioning continues to fail, file a service request (SR) at My Oracle Support (click the Service Requests tab, and click Create Technical SR):

      • Use the ssh command to connect to the Administration Server VM that failed to provision the Oracle SOA Suite on Marketplace instance and provide /u01/logs/*.log from all the nodes for analysis.

To provision an Oracle SOA Suite on Marketplace instance:

  1. Navigate to the SOA Suite 12.2.1.4 listing on Marketplace by direct URL or by browsing in Oracle Cloud Infrastructure:
  2. Accept the terms and restrictions, then click Launch Stack.

    Description of soamp-launch-stack.png follows
    Description of the illustration soamp-launch-stack.png

    The Create Stack wizard is displayed.

  3. Provide information about the stack for the instance as described in the following table.
    Field Label Description
    Name Optionally, modify the default name for the stack after it's deployed.

    The name must be unique within the identity domain and must meet the following conditions: start with a letter, not longer than 30 characters, not contain non-alphanumeric character (including spaces).
    Description Optionally, enter a description of the stack. For example, you can specify the name of the application that will run on the stack after it is deployed.
    Create in compartment Automatically populated with the compartment you selected on the landing page. This is the compartment where the stack will be created in the tenancy. (Stacks are attached to a specific region. However, where necessary, the resources on a given stack can be deployed across multiple regions.)

    Note:

    If not already granted, you will need to ask your administrator to grant the following manage and use permissions in the compartment:

    • allow group groupName to manage instance-family in compartment compartmentName
    • allow group groupName to manage virtual-network-family in compartment compartmentName
    • allow group groupName to manage volume-family in compartment compartmentName
    • allow group groupName to use database-family in compartment compartmentName
    • allow group groupName to use autonomous-database-family in compartment compartmentName

    where groupName is the name of the group to which you belong and compartmentName is the name of the compartment where Oracle SOA Suite on Marketplace instances will be created.

    Terraform version Automatically populated with the Terraform version used for the Marketplace offering.
    Tags

    Optionally, select existing tags or add tags to associate with the stack. For more information about tagging, see Resource Tags.

    If you do not assign tags during provisioning, you can create and manage tags after the stack is created.

  4. Click Next and configure the instance as described in the following table.
    Field Label Description
    Server Instance
    Instance Name Prefix Enter the prefix you wish to use for the instance name, up to 15 characters.
    Service Type Select the service type you are provisioning:
    • SOA with SB & B2B Cluster
    • MFT Cluster
    • BAM Cluster

    Note: In this guide, Oracle SOA Suite refers to any of the three service types.

    Enable SOA DB Schema Partitioning

    If you selected a Service Type of SOA with SB & B2B Cluster, select this check box to enable SOAINFRA schema partitioning.

    Default: not selected.

    Note: If you enable SOAINFRA schema partitioning for your database, be sure to choose Enterprise Edition High Performance or Enterprise Edition Extreme Performance for the Oracle Database software edition when you create the database.

    Compute Shape

    Select a compute shape with at least 15GB of memory. For information about compute shapes, see:

    The available compute shapes (VM.Standard3.Flex, VM.Standard.E4.Flex, and VM.Optimized3.Flex) allow you to customize the following values for Oracle SOA Suite on Marketplace instances:

    • OCPU count:
      • Minimum: 2
      • Miximum: 18
    • Memory size:
      • Minimum: 15GB
      • Miximum: 256GB

    Note: Flexible compute shapes are not supported for a Bastion instance.

    You can change the compute shape post-provisioning by scaling up the Oracle SOA Suite on Marketplace instance. See Scale an Oracle SOA Suite on Marketplace Instance Up or Down.

    Enable Secure Boot

    Select to prevent unauthorized boot loaders and operating systems from booting.

    For more information, see Shielded Instances in the Oracle Cloud Infrastructure documentation.

    Enable Measured Boot

    Select to enhance boot security by taking and storing measurements of boot components, such as bootloaders, drivers, and operating systems. The Trusted Platform Module (TPM) securely stores boot measurements.

    Note: Bare metal instances do not support Measured Boot.

    For more information, see Shielded Instances in the Oracle Cloud Infrastructure documentation.

    SSH Public Key

    Enter the public key for the secure shell (SSH), either by providing an SSH key file or pasting the SSH key. This key is used for authentication when connecting to the Oracle SOA Suite on Marketplace instance using an SSH client. See Generate a Secure Shell (SSH) Public/Private Key Pair.

    Cluster Node Count Enter the initial number of SOA Server compute instances. This is also the number of Managed Servers in the cluster.

    During provisioning, the maximum allowable cluster size is 8 nodes. If you want to create a cluster of a larger size, you can create a 8-node cluster during provisioning and then post-provisioning you can scale out the cluster to a maximum size of 16 nodes. See Scale Out an Oracle SOA Suite on Marketplace Instance Cluster.

    Administration Username Enter the name of the SOA Server domain administrator.
    Administration Password Enter a password that meets the specifications shown below the field. Enter the password again for confirmation.
    WebLogic Server Admin Secret Compartment

    Validated Secrets OCID for Administration password

    		 If you selected Use KMS Vault Secrets for passwords:
    • Select the compartment for the WebLogic Server administration secret.
    • Select the OCID of the secret that contains the WebLogic Server administration password.
    Domain Volume Size (GB) Enter a custom domain block volume size for the instance. Default (minimum): 50GB

    You can increase the domain volume size post-provisioning by editing the stack.You cannot decrease the domain volume size. See Edit an Oracle SOA Suite on Marketplace Instance.

    Key Management Service Configuration
    Use KMS Vault Secrets for passwords Select this check box to enable KMS vault secrets for passwords. The KMS secrets must be created prior to provisioning an Oracle SOA Suite on Marketplace instance. On selection, fields in the provisioning UI support selections for KMS secrets for passwords:
    • For WebLogic Server administration: WebLogic Server Admin Secret Compartment and Validated Secrets OCID for Nodemanager password
    • For WebLogic Server nodemanager: WebLogic Server Nodemanager Secret Compartment and Validated Secrets OCID for Nodemanager password
    • For OCI database: OCI DB Secret Compartment and Validated Secrets OCID for Database Administrator Password
    • For ATP database: ATP DB Secret Compartment and Validated Secrets OCID for Autonomous Database ADMIN password
    • For Exadata database: Exadata DB Secret Compartment and Validated Secrets OCID for Database Administrator Password
    • For database connection string: External DB Secret Compartment and Validated Secrets OCID for Database Administrator Password
    • For RCU schema: RCU Schema Secret Compartment and Validated Secrets OCID for Custom RCU Schema Password
    • For ATP DB wallet: ATP DB Wallet Secret Compartment and Validated Secrets OCID for ATP DB Wallet Password

    Selecting this checkbox also exposes the Backup/Restore Configuration section (see below).

    OCI Policies Select this check box to create required OCI policies to access the KMS secrets from the vault during provisioning.
    Instance Network
    Network Compartment Automatically populated with the compartment you selected on the landing page. This is the compartment where the instance will be created in the tenancy.
    Virtual Cloud Network Strategy Select either Create New VCN or Use Existing VCN in which to create the instance, network resources, and load balancer.
    SOA Server Network If you selected a Virtual Cloud Network Strategy of Create New VCN, enter the name of the new VCN.
    SOA Server Network CIDR If you selected a Virtual Cloud Network Strategy of Create New VCN, enter the unique CIDR to assign to the new VCN.
    Existing Network If you selected a Virtual Cloud Network Strategy of Use Existing VCN, select the name of the VCN.
    Use Network Security Group for SOA Instance

    Note: You can also edit an Oracle SOA Suite on Marketplace instance post-provisiong to disable and enable this option.

    If you selected a Virtual Cloud Network Strategy of Use Existing VCN, select this check box to use a network security group (NSG) for controlling traffic to the Oracle SOA Suite on Marketplace compute instances.

    If you do not select this option, the compute instance uses the security list of the respective subnet.

    NSG Compartment

    If you selected Use Network Security Group for SOA Instance, select the NSG's compartment.

    SOA Network Security Group

    If you selected Use Network Security Group for SOA Instance, select the NSG to be used for controlling traffic to the Oracle SOA Suite on Marketplace compute instance.

    Subnet Strategy

    Select either Create New Subnet or Use Existing Subnet.

    If you use an existing subnet, note that the provisioning process will not create any security lists to open ports in the subnets. You must open the ports explicitly before provisioning. See Configure Security Lists.

    Subnet Compartment Select the compartment in which to create the new or existing subnet.
    Subnet Type Select either a public or private subnet.
    Subnet Span Select either a region or AD Specific Subnet to create the instance in an availability domain.
    Availability Domain If you selected a Subnet Strategy of Create New Subnet and a Subnet Span of AD Specific Subnet, select the name of the availability domain in which to create the instance.

    Note: For a regional subnet, the nodes in an Oracle SOA Suite on Marketplace cluster are distributed evenly across all available availability domains.

    Existing Subnet

    If you selected a Subnet Strategy of Use Existing Subnet, select an existing subnet to use for the instance. This subnet must already be present in the chosen VCN.

    If you use an existing subnet, note that the provisioning process will not create any security lists to open ports in the subnets. You must open the ports explicitly before provisioning. See Prerequisites.

    Subnet CIDR If you selected a Subnet Strategy of Create New Subnet, enter the unique CIDR of the new subnet to create for the instance.
    Bastion Strategy If you selected a Subnet Strategy of Use Existing Subnet, and a Subnet Type of Use Private Subnet, select a Bastion strategy:
    • (Default) Use Private Endpoint to use a private endpoint instead of a Bastion host for provisioning and scale out operations. A private endpoint enables private SSH access to compute instances created during provisioning of Oracle SOA Suite on Marketplace instances on a private subnet.

      Note: To use this feature, you must add security policies to your tenancy. See Manage Private Endpoints in the Oracle Cloud Infrastructure documentation.

    • Create New Bastion Instance to create a new Bastion host for every SOA cluster
    • Use Existing Bastion Instance to use an existing Bastion host for every SOA cluster
    Private Endpoint Strategy If you selected a Bastion Strategy of Use Private Endpoint, select either Create New Private Endpoint or Use Existing Private Endpoint.
    Private Endpoint Compartment Select the compartment in which to create the new private endpoint, or find the existing private endpoint.

    This field is shown when you select:

    • a Subnet Strategy of Create New Subnet and a Subnet Type of Use Private Subnet
    • or, a Subnet Strategy of Using Existing Subnet, a Subnet Type of Use Private Subnet, and a Bastion Strategy of Use Private Endpoint
    Private Subnet Compartment Select the compartment for the new private endpoint subnet.

    This field is shown when you select:

    • a Subnet Strategy of Create New Subnet and a Subnet Type of Use Private Subnet
    • or, a Subnet Strategy of Using Existing Subnet, a Subnet Type of Use Private Subnet, a Bastion Strategy of Use Private Endpoint, and a Private Endpoint Strategy of Create New Private Endpoint
    Private Endpoint Subnet If you selected a Bastion Strategy of Use Private Endpoint and a Private Endpoint Strategy of Create New Private Endpoint, select a private subnet for creating the private endpoint.
    Private Endpoint Subnet CIDR If you selected a Subnet Strategy of Create New Subnet, and a Subnet Type of Use Private Subnet, enter the unique CIDR of the new subnet to create for the private endpoint. The new subnet's CIDR should not overlap with any other subnet CIDRs.
    Use Network Security Group for Private Endpoint select this check box to use a network security group (NSG) for controlling traffic to the private endpoint.

    This check box is shown when you select:

    • a Subnet Strategy of Create New Subnet and a Subnet Type of Use Private Subnet
    • or, a Subnet Strategy of Using Existing Subnet, a Subnet Type of Use Private Subnet, a Bastion Strategy of Use Private Endpoint, and a Private Endpoint Strategy of Create New Private Endpoint
    Network Security Group Compartment

    If you selected Use Network Security Group for Private Endpoint , select the NSG's compartment.

    Private Endpoint Network Security Group

    If you selected Use Network Security Group for Private Endpoint , select the NSG to be used for controlling traffic to the private endpoint.

    Private Endpoint Display Name If you selected a Bastion Strategy of Use Private Endpoint and a Private Endpoint Strategy of Create New Private Endpoint, enter a display name for the private endpoint.
    Existing Private Endpoint If you selected a Bastion Strategy of Use Private Endpoint and a Private Endpoint Strategy of Use Existing Private Endpoint, select the private endpoint to be used during provisioning of the instance.
    Bastion Host Subnet Compartment If you selected a Bastion Strategy of Create New Bastion Instance, select the compartment in which to create the new Bastion host subnet.
    Existing Subnet for Bastion Host If you selected a Bastion Strategy of Create New Bastion Instance, select an existing public subnet to use for a Bastion compute instance. This subnet must already be present in the chosen VCN. This field is required only if you did not assign public IP addresses to WebLogic Server.
    Bastion Host Shape

    If you selected a Bastion Strategy of Create New Bastion Instance, select the shape of the Bastion instance.

    Note: Flexible compute shapes are not supported for a Bastion instance.

    Public IP of Bastion Instance If you selected a Bastion Strategy of Use Existing Bastion Instance, enter the public IP address of the existing Bastion instance.
    SSH Private Key Bastion Instance If you selected a Bastion Strategy of Use Existing Bastion Instance, enter the SSH private key of the existing Bastion instance. Note: the SSH private key must not be passphrase-protected.
    Bastion Host Subnet CIDR If you selected a Virtual Cloud Network Strategy of Create New VCN a Subnet Strategy of Create New Subnet and a Subnet Type of Use Private Subnet, enter the unique CIDR of the new subnet to create for a Bastion compute instance. This is required only if you did not assign a public IP address to SOA Server.
    Use Network Security Group for Bastion Host

    If you selected a Bastion Strategy of Create New Bastion Instance, select this check box to use a network security group (NSG) for controlling traffic to the Bastion host.

    NSG Compartment

    If you selected Use Network Security Group for Bastion Host, select the NSG's compartment.

    Bastion Network Security Group

    If you selected Use Network Security Group for Bastion Host, select the NSG to be used for controlling traffic to the Bastion host.

    Provision Load Balancer

    Note: You can also edit an Oracle SOA Suite on Marketplace instance post-provisiong to disable and enable this option.

    		Select this check box to enable the Oracle Cloud Infrastructure load balancer to distribute traffic. For more information, see Overview of Load Balancing in the Oracle Cloud Infrastructure documentation.

    Enabling a load balancer is optional. If you decide you want to add one later, see Add or Delete a Load Balancer Post-Provisioning.

    Load Balancer Strategy If you selected Provision Load Balancer, select whether to create a new load balancer or use an existing load balancer.
    Load Balancer Compartment If you selected Provision Load Balancer, select the compartment to create a new load balancer or use an existing load balancer.
    Existing Load Balancer If you selected Provision Load Balancer and Use Existing Load Balancer, select the existing load balancer to use.
    Load Balancer Subnet Compartment If you selected Provision Load Balancer, select the compartment in which to create the new or existing load balancer subnet.

    You can change the load balancer subnet compartment post-provisioning by editing the stack. See Edit an Oracle SOA Suite on Marketplace Instance.

    Load Balancer Subnet Type If you selected a Subnet Type of Use Private Subnet and Provision Load Balancer, select to use either a private or a public subnet for the load balancer.
    Load Balancer Subnet CIDR If you selected a Subnet Strategy of Create New Subnet and Provision Load Balancer, enter the CIDR of the new subnet to create for the load balancer. The new subnet's CIDR should not overlap with any other subnet CIDRs.
    Existing Subnet for Load Balancer If you selected a Subnet Strategy of Use Existing Subnet and Provision Load Balancer, select an existing subnet to use for the load balancer. This subnet must already be present in the chosen VCN.

    You can change the load balancer subnet post-provisioning by editing the stack. See Edit an Oracle SOA Suite on Marketplace Instance.

    Load Balancer Shape If you selected Provision Load Balancer, select the load balancer shape: 100Mbps, 400Mbps, 8000Mbps, or Flexible.
    If you select Flexible, the provisioning wizard exposes two fields to specify the minimum and maximum bandwidth for the load balancer:
    • Minimum size of Flexible Shape (Mbps)
    • Maximum size of Flexible Shape (Mbps)
    Enter a minimum bandwidth value greater than or equal to 10, and a maximum bandwidth value less than or equal to 8000. To set a fixed load balancer shape, set both the minimum and maximum bandwidth value to the same required load balancer shape.

    You can change the load balancer shape post-provisioning by editing the stack. See Edit an Oracle SOA Suite on Marketplace Instance.

    Use Network Security Group for Load Balancer

    If you selected Provision Load Balancer, select this check box to use a network security group (NSG) for controlling traffic to the load balancer.

    NSG Compartment

    If you selected Use Network Security Group for Load Balancer, select the NSG's compartment.

    Load Balancer Network Security Group

    If you selected Use Network Security Group for Load Balancer, select the NSG to be used for controlling traffic to the load balancer.

    Database
    Database Strategy Select the database strategy for WebLogic Server:
    • Database System (the Oracle Cloud Infrastructure database), supported for any service type.
    • Autonomous Transaction Processing Database, supported for the SOA with SB & B2B Cluster and MFT Cluster service types.
    • Exadata Database, supported for any service type.
    • Database Connection String. This option is only for advanced users, and not recommended.

      If selected, enter a value in Database Connection String using syntax host:port/serviceName. For example:

      demodb-scan.demodb.demovcn.oraclevcn.com:1521/PDB1.demodb.demovcn.oracle.vcn.com
    DB System Compartment

    Autonomous DB System Compartment

    		 Select the compartment for the database. This can be the same compartment as the Oracle SOA Suite on Marketplace instance, or a different compartment.
    DB System

    Autonomous Database

    		 Select the DB system to use for this WebLogic Server domain. This should be in the same VCN as WebLogic instances.
    Database home in the DB System If you selected a Database Strategy of Database System, select the database home within the DB system.
    Database in the DB System If you selected a Database Strategy of Database System, select the database in which to provision the schemas for a JRF-enabled WebLogic Server domain.
    PDB If you selected a Database Strategy of Database System, enter the name of the pluggable database (PDB) in which to provision the schemas for a JRF-enabled WebLogic Server domain.
    Exadata SCAN DNS Name If you selected a Database Strategy of Exadata Database, enter the SCAN DNS name of the Exadata VM cluster. Refer to the Exadata VM cluster details page in the Oracle Cloud Infrastructure Console for the SCAN DNS name..
    PDB Service name If you selected a Database Strategy of Database System or Exadata Database, enter the full service name of the pluggable database (PDB) in which to provision the schemas for a JRF-enabled WebLogic Server domain.
    Database Administrator If you selected a Database Strategy of Database System or Exadata Database, enter the name of a database user with DBA privileges.
    Database Administrator Password

    Autonomous Database Admin Password

    		 Enter a password for the database administrator.
    OCI DB Secret Compartment

    Validated Secrets OCID for Database Administrator Password

    		 If you selected a Database Strategy of Database System and you selected Use KMS Vault Secrets for passwords:
    • Select the compartment for the OCI database secret.
    • Select the OCID of the secret that contains the password for the OCI database administrator.
    Exadata DB Secret Compartment

    Validated Secrets OCID for Database Administrator Password

    		 If you selected a Database Strategy of Exadata Database and you selected Use KMS Vault Secrets for passwords:
    • Select the compartment for the Exadata database secret.
    • Select the OCID of the secret that contains the password for the Exadata database administrator.
    ATP DB Secret Compartment

    Validated Secrets OCID for Autonomous Database ADMIN password

    		 If you selected a Database Strategy of Autonomous Transaction Processing Database and you selected Use KMS Vault Secrets for passwords:
    • Select the compartment for the ATP database secret.
    • Select the OCID of the secret that contains the password for the ADMIN user in the ATP database.
    External DB Secret Compartment

    Validated Secrets OCID for Database Administrator Password

    		 If you selected a Database Strategy of Database Connection String and you selected Use KMS Vault Secrets for passwords:
    • Select the compartment for the external database secret.
    • Select the OCID of the secret that contains the password for the external database administrator.
    Autonomous Database Service Level If you selected a Database Strategy of Autonomous Transaction Processing Database, select the service level that the WebLogic Server domain should use to connect to the ATP database.

    Select Custom Service Level to add your custom ATP service level.

    Default: low.

    Custom Autonomous Database Service Level This field is exposed when you select Custom Service Level as your Autonomous Database Service Level. It allows you to add the custom ATP service level name.
    Database Listener Port If you selected a Database Strategy of Database System or Exadata Database, enter the listener port for the database. Default: 1521.
    Specify custom RCU Schema Prefix Select this check box to specify a custom RCU schema prefix name.

    If selected, enter an RCU schema prefix in Specify custom RCU Schema Prefix Note that it is your responsibility to make sure that the prefix name is unique in the selected database.

    Specify RCU Schema custom Password Select this check box to specify a custom password for the RCU schema. The password must start with a letter, be 12 to 30 characters long, contain at least one number and two or more uppercase characters. Optionally, it can include the following characters: ( ) $ # _ .

    If this option is not selected, the provisioning process generates a random password for the RCU schema.

    RCU Schema Secret Compartment

    Validated Secrets OCID for Custom RCU Schema Password

    		 If you selected Specify RCU Schema custom Password and Use KMS Vault Secrets for passwords:
    • Select the compartment for the RCU schema secret.
    • Select the OCID of the secret that contains the password for the RCU schema.
    File Storage
    This section is shown in the provisioning wizard when:
    • the Service Type is MFT Cluster and the Database Strategy is Autonomous Transaction Processing Database. This configuration is mandatory for the MFT Cluster service type on an Autonomous Transaction Processing (ATP) database.
    • the Service Type is SOA with SB & B2B Cluster, the Database Strategy is Autonomous Transaction Processing Database, and you select the optional check box labeled Configure File Storage for shared location in cluster nodes.

    The configuration settings here create a new file system, mounted on all the nodes of the cluster. Subsequent scale out operations handle mounting the file system on the newly added node. When configured, FSS will be used as an alternative to DBFS.
    File System Compartment Select the compartment in which to create the file system.
    File Storage Availability Domain Select the name of the availability domain in which to create the file system and the mount target.
    Mount Target Strategy If you selected a Virtual Cloud Network Strategy of Use Existing VCN and a Subnet Strategy of Use Existing Subnet, select:
    • Create New Mount Target to create a new mount target to mount the file system.
    • Use Existing Mount Target to use an existing mount target to mount the file system.
    Mount Target Compartment Select the compartment in which to create the new or existing mount target.
    Mount Target Subnet If you selected a Virtual Cloud Network Strategy of Use Existing VCN, a Subnet Strategy of Use Existing Subnet, and a Mount Target Strategy of Create New Mount Target, select the subnet in which to create the new or existing mount target.
    Mount Target Subnet CIDR If you selected a Subnet Strategy of Create New Subnet, enter the unique CIDR of the new mount target subnet.
    Existing Mount Target OCID

    Enter the OCID of the mount target to be used for mounting the file system.

    This field is shown when you select:

    • a VCN Strategy of Use Existing VCN, a Subnet Strategy of Using Existing Subnet, a Subnet Type of either Use Private Subnet or Use Public Subnet, and a Mount Target Strategy of Use Existing Mount Target
    • or, VCN Strategy of Create New VCN, a Subnet Strategy of Create New Subnet, and a Subnet Type of Use Public Subnet
    Use Network Security Group for Mount Target

    Select this check box to use a network security group (NSG) for controlling traffic to the mount target.

    This check box is shown when you select:

    • a VCN Strategy of Use Existing VCN and a Subnet Strategy of Create New Subnet
    • or, a VCN Strategy of Use Existing VCN, a Subnet Strategy of Use Existing Subnet, and a Mount Target Strategy of Create New Mount Target
    • or, VCN Strategy of Create New VCN, a Subnet Strategy of Create New Subnet, and a Subnet Type of Use Private Subnet
    Network Security Group for Compartment

    If you selected Use Network Security Group for Mount Target, select the NSG's compartment.

    Mount Target Network Security Group

    If you selected Use Network Security Group for Mount Target, select the NSG to be used for controlling traffic to the mount target.

    Service Instance Advanced
    Service Instance Advanced Configuration Select this check box to specify port configuration properties. Refer to the descriptions below each field:
    • Specify custom WLS Nodemanager Password

      If you select this check box and also selected Use KMS Vault Secrets for passwords, the following fields display:

      • WebLogic Server Nodemanager Secret Compartment
      • Validated Secrets OCID for Nodemanager Password
    • Node Manager Port
    • Admin Console Port
    • Admin Console SSL Port
    • External Admin Port
    • External Admin SSL Port
    • Managed Server Port
    • Managed Server SSL Port
    • Coherence Cluster Port
    • Custom Cluster Name
    • Custom Domain Name
    • Custom Admin Server Name
    • Custom Managed Server Name Prefix
    • Custom Machine Name Prefix
    • Deploy Sample Application
    • Specify custom ATP wallet Password

      If you select this check box and also selected Use KMS Vault Secrets for passwords, the following fields display:

      • ATP DB Wallet Secret Compartment
      • Validated Secrets OCID for ATP DB Wallet Password

    Note: If you choose not to provide custom values, the default naming convention will be followed during provisioning.

    Backup/Restore Configuration (enabled with KMS Configuration)

    This section is exposed only when you select Use KMS Vault Secrets for Passwords.

    Enable Backup/Restore configuration

    Note: You can also edit an Oracle SOA Suite on Marketplace instance post-provisiong to disable and enable this option.

    		Select this check box to enable Oracle SOA Suite on Marketplace domain home backup and restore. Backup and restore requires KMS to be configured in the following fields:
    • KMS Vault Compartment. Select the compartment where you have the KMS vault.
    • KMS Vault. Select the OCID of the KMS vault used to encrypt the backup files.
    • KMS Encryption Key. Select the OCID of the KMS encryption key used to encrypt the backup files.
    • Object Storage Bucket Name. Enter the name of the object storage bucket used for storing the backup files.
    Email Notification

    When enabled, Oracle SOA Suite on Marketplace uses the OCI Notification Service (ONS) and OCI Events Service to send out email notifications upon completion of the Terraform job in the stack.

    Enable Email notifications Select this check box to send an email notification upon completion of the Terraform job in the stack, containing information about the job.

    Example email:
    Email notification
    ONS Topic Strategy Select:
    • Use Existing ONS Topic to reuse an existing ONS topic with an email subscription.
    • Create New ONS Topic to create a new ONS topic.
    Existing ONS Topic OCID If you selected an ONS Topic Strategy of Use Existing ONS Topic, enter the OCID of the existing ONS topic to be used for configuring the email notification.
    Notification Email ID If you selected an ONS Topic Strategy of Create New ONS Topic, enter the email address to which the email notification should be sent.

    Note: A confirmation email will be sent to the provided email address. The email recipient must click the link provided in the email to confirm the subscription and enable email notifications.


    Email subscription notification
    Tags

    For more information, see Resource Tags.

    Tag namespace Select free-form or defined tags for the instance.
    Tag key Optionally, enter a tag key for the instance.
    Tag value Enter the value for the specified tag key.
  5. Click Next.
  6. See Complete Post-Provisioning Tasks.