1. Using Oracle SOA Suite on Marketplace in Oracle Cloud Infrastructure
  2. Get Started with Oracle SOA Suite on Marketplace
  3. About Managing Oracle SOA Suite on Marketplace Instances

About Managing Oracle SOA Suite on Marketplace Instances

Following best practices ensures that your Oracle SOA Suite on Marketplace instances are manageable.

Reliable management of Oracle SOA Suite on Marketplace instances requires a specific software environment that includes instances of an Oracle Cloud Infrastructure database and a secure shell (SSH) public key. For details on these features, see Before You Begin.

To keep your instances manageable, follow these guidelines:

  • To ensure that you can restore the database for an Oracle SOA Suite on Marketplace instance without risking data loss for other instances, do not use the same Oracle Cloud Infrastructure database with multiple Oracle SOA Suite on Marketplace instances. Backups of an Oracle Cloud Infrastructure database instance that are used with multiple Oracle SOA Suite on Marketplace instances contain data for all the instances. If you restore the database while restoring an Oracle SOA Suite on Marketplace instance, data for all the instances is restored.
  • Apply the latest software bundle patches. See About Managing Patches for Instances Provisioned With Earlier Releases.
  • Use only the default domain that was provisioned when an Oracle SOA Suite on Marketplace instance was created. Do not add any Oracle WebLogic Server domains to the instance.
  • If you plan to integrate multi-domain environments, ensure that the first eight characters of your Oracle SOA Suite on Marketplace instance name are unique so that all domains and associated resources have unique names.

    By default, the names of the domain and cluster in the Oracle SOA Suite on Marketplace instance are generated from the first eight characters of the instance name, and use the following formats, respectively:

    • first8charsOfServiceInstanceName_domain

    • first8charsOfServiceInstanceName_cluster

  • For any disk volume that an Oracle SOA Suite on Marketplace Managed Server attaches to an instance's VMs during creation of the instance:
    • Do not detach, change file access permissions for, or change the mount point of a disk volume.
    • Except for the DOMAIN_HOME volume, do not change the content of a disk volume.

    For details about these volumes, see About the Storage Volumes Attached to the WebLogic Server Nodes in Administering Oracle Java Cloud Service.

  • Do not change the egress and ingress network and security settings of any infrastructure resources that the instance uses.
  • If you close any ports or protocols post-provisioning, you may end up in blocking your server endpoint URLs. You must ensure that you have valid ingress rules allowing traffic from known sources only.

    You can open new ports and protocols, but closing existing ports and protocols may impair the functioning of an instance.

  • Do not detach NAT IP addresses from any of an instance's VMs.
  • Do not change the Oracle Fusion Middleware component schemas with which an instance was provisioned.
  • After provisioning, do not change the ports for the Oracle WebLogic Server Administration Server and the Oracle Cloud Infrastructure load balancer Administration Server.
  • Do not change OS users and SSH key settings that an Oracle SOA Suite on Marketplace Managed Server configured during creation of an instance.