1. Administering Oracle SOA Cloud Service
  2. Before You Begin
  3. About Oracle SOA Cloud Service Architecture
  4. About Oracle SOA Cloud Service Architecture in Oracle Cloud Infrastructure Classic

About Oracle SOA Cloud Service Architecture in Oracle Cloud Infrastructure Classic

The following figure illustrates an Oracle SOA Cloud Service instance on Oracle Cloud Infrastructure Classic.

Description of soa_architecture_diagram_oci__c.png follows
Description of the illustration soa_architecture_diagram_oci__c.png

Topics:

Region

If your identity domain is enabled for regions, you can select a region in which your Oracle SOA Cloud Service instance will reside.

For a list of available regions, see Data Regions for Platform and Infrastructure Services.

When you select an Oracle Cloud Infrastructure Classic region for a service instance, you can also select an IP Network and assign reserved IP addresses to your nodes. If you don’t explicitly select a region (No Preference), you cannot select an IP network or use reserved IPs.

IP Network

If you select a specific Oracle Cloud Infrastructure Classic region for your service instance, then you can also select an IP network in that region. Using an IP network gives you more control over the configuration of the network in which your service instance is placed.

By default, if you select an IP network, each underlying node is auto-assigned a public and private IP address. As a result, the IP address might change each time a service instance is started. To assign fixed public IP addresses to instances attached to the IP network, you can create and use IP reservations.

When you select an IP network during provisioning, you must also select a Oracle Database Classic Cloud Service instance that is on an IP network. If the Oracle SOA Cloud Service and Oracle Database Classic Cloud Service are attached to different IP networks, then the two IP networks must be connected to the same IP network exchange. The required access rules for the Oracle SOA Cloud Service instance and Oracle Database Classic Cloud Service database deployment to communicate are created automatically.

If you want to create a service instance that uses an IP network and also includes an Oracle-managed load balancer running on Oracle Cloud Infrastructure Load Balancing Classic, you must first attach an Internet-facing load balancer to the IP network. A service instance uses an Oracle-managed load balancer when you enable authentication with Oracle Identity Cloud Service.

See Creating an IP Network in Using Oracle Cloud Infrastructure Compute Classic (ignore information in this topic about the Compute API and orchestrations).

Software Release

You can select the following Oracle WebLogic Server releases.

With Oracle SOA Cloud Service, you can easily apply patches to an existing service instance.

Oracle has simplified the cloud provisioning policy to align with the WebLogic Server error correction support policy. Service instance provisioning will now end on the same day as the error correction end date for the corresponding WebLogic release.

This is specific to the provisioning of WebLogic instances through Oracle SOA Cloud Service and that this change has no impact on the use of these WebLogic releases within on-premises environments or within Oracle Cloud IaaS environments.

More information about this change can be found in the Oracle Fusion Middleware Lifetime Support Policy document and Error Correction Support Dates for Oracle WebLogic Server Support Note.

User Authentication

By default, the WebLogic Server domain in a service instance is configured to use the local WebLogic identity store to maintain administrators, application users, groups, and roles. These security elements are used to authenticate users and also to authorize access to tools like the WebLogic Server Administration Console.

Database

Every service instance must be associated with an existing relational database in Oracle Cloud. Oracle SOA Cloud Service provisions the required infrastructure schema on the selected database.

The supported database services in Oracle Cloud vary by region. For an Oracle Cloud Infrastructure Classic region, the infrastructure schema database options are shown in the following table.

Note:

If you specify No Preference for region, or if you have an older Oracle Cloud account that doesn't include regions, then you can also choose these same database options.

Database Supported Versions Additional Information
Oracle Database Classic Cloud Service, with or without Oracle Real Application Clusters (RAC)

Note: If you want to use RAC, you will need to create an Oracle Database Classic Cloud Service instance using the standard service level and Enterprise Edition Extreme Performance for the Oracle Database software edition.

  • Oracle Database 12c release 1 (12.1.0.2)

  • Oracle Database 12c release 2 (12.2.0.1)

See Oracle Database Classic Cloud Service Limitations and Usage Notes, below.

More Information:

Oracle Database Exadata Cloud Service

  • Oracle Database 12c Release 2

  • Oracle Database 12c Release 1

  • Oracle Database 11g Release 2

See Oracle Database Exadata Cloud Service Limitations and Usage Notes, below.

More Information:

General Usage Notes

  • All databases must be in an active state and not currently in the process of being provisioned. The WebLogic Server domain in a service instance uses Java Database Connectivity (JDBC) to access the databases.

  • To ensure that you can restore the database for an Oracle SOA Cloud Service instance without risking data loss for other service instances, Oracle recommends that you do not associate the same infrastructure schema database (or the same pluggable database) with multiple service instances. Backups of a database that is used with multiple Oracle SOA Cloud Service instances contain data for all the instances. Therefore, if you restore the database from a backup, data for all the service instances is restored, which might not be the intended result.

General Limitations

  • If you specify an IP network for a service instance, the infrastructure schema database for the Oracle SOA Cloud Service instance must also be attached to an IP network. If the service instance and the database are attached to different IP Networks, the two IP networks must be connected to the same IP network exchange. See Create an IP Network in Using Oracle Cloud Infrastructure Compute Classic.

Oracle Database Classic Cloud Service Limitations and Usage Notes

  • Oracle SOA Cloud Service uses Oracle Database Classic Cloud Service to host the Oracle Fusion Middleware component schemas required by Oracle Java Required Files (JRF). Make sure you have a subscription to Oracle Database Classic Cloud Service (Database as a Service).
  • You cannot use an Oracle Database Classic Cloud Service deployment running Oracle Database 18c.
  • You can use an Oracle Database Classic Cloud Service deployment running Oracle Database 12.2, but only for service instances running Oracle WebLogic Server 12.2.1 or later.
  • For information about subscribing to Oracle Database Classic Cloud Service and provisioning an Oracle Database Classic Cloud Service instance (standard service level), see Administering Oracle Database Classic Cloud Service.
  • When provisioning an Oracle Database with the Oracle Database Classic Cloud Service provisioning wizard, you must select an object storage container in Oracle Cloud Infrastructure Object Storage Classic even though this field is optional. If you do not select a storage container in Oracle Cloud Infrastructure Object Storage Classic, when you run the Oracle SOA Cloud Service provisioning wizard and select this Oracle Database Classic Cloud Service, instance provisioning fails. Always select an Oracle Database Classic Cloud Service that has a storage container in Oracle Cloud Infrastructure Object Storage Classic associated with it.
  • Create Oracle Database Classic Cloud Service deployments with a backup option other than NONE. This configuration enables Oracle SOA Cloud Service to coordinate backups across your service instance and the database. Coordinated backups are not supported for other database services.

  • Do not use the Virtual Image service level for Oracle Database Classic Cloud Service as it does not work correctly during backup and restore.

  • When creating an Oracle Database Classic Cloud Service instance (standard service level) to use with Oracle SOA Cloud Service, make sure you select either Cloud Storage Only or Both Cloud Storage and Local Storage as the backup option for the database. If you select None, the Oracle SOA Cloud Service provisioning wizard will not present that Oracle Database Classic Cloud Service instance as an available database in the Oracle SOA Cloud Service provisioning wizard.

  • If you are using Oracle Real Application Clusters (RAC) with Oracle Database Classic Cloud Service Enterprise Edition - Extreme Performance:

    • When you configure the compute shape during provisioning or scaling up a node, be sure to stay within the bounds of your available memory.

    • Note that Oracle SOA Cloud Service uses the GridLink data source to point to the RAC database.

    The following example shows a connect string used to connect to a RAC database:

    jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=vgad c01jjfrac1)(PORT=1522))(ADDRESS=(PROTOCOL=TCP)(HOST=DBHostRAC1)(PORT=1522))(LOAD_BALANCE=ON)(FAILOVER=ON))(CONNECT_DATA=(SERVICE_NAME=PDB1.sbcs.cloud.internal)))
    Name Type JNDI Name Targets

    EDNDataSource

    GridLink

    jdbc/EDNDataSource

    soaRACNo_cluster

    EDNLocalTxDataSource

    GridLink

    jdbc/EDNLocalTxDataSource

    soaRACNo_cluster

    LocalSvcTblDataSource

    GridLink

    jdbc/LocalSvcTblDataSource

    soaRACNo_adminserver

    mds-owsm

    GridLink

    jdbc/mds/owsm

    soaRACNo_cluster, soaRACNo_adminserver

    mds-soa

    GridLink

    jdbc/mds/MDS_LocalTxDataSource

    soaRACNo_cluster, soaRACNo_adminserver

    opss-audit-DBDS

    GridLink

    jdbc/AuditAppendDataSource

    soaRACNo_cluster, soaRACNo_adminserver

    opss-audit-viewDS

    GridLink

    jdbc/AuditViewDataSource

    soaRACNo_cluster, soaRACNo_adminserver

    opss-data-source

    GridLink

    jdbc/OpssDataSource

    soaRACNo_cluster, soaRACNo_adminserver

    OraSDPMDataSource

    GridLink

    jdbc/OraSDPMDataSource

    soaRACNo_cluster

    SOADataSource

    GridLink

    jdbc/SOADataSource

    soaRACNo_cluster

Oracle Database Exadata Cloud Service Limitations and Usage Notes

  • Oracle SOA Cloud Service supports Exadata database as a backend database to create SOAINFRA schemas. If you are not familiar with Oracle Database Exadata Cloud Service, see Creating a Database Deployment in Using Oracle Database Exadata Cloud Service.

  • An IP reservation is required for using Oracle Database Exadata Cloud Service as your database with Oracle SOA Cloud Service. See Create and Manage IP Reservations. Oracle Database Exadata Cloud Service requires the selection of an IP network during provisioning. You must then provision Oracle SOA Cloud Service in that same IP network. See Managing IP Networks in Using Oracle Cloud Infrastructure Compute Classic.

  • If you are provisioning the service instance in an identity domain that does not have regions enabled, a manual IP reservation procedure is required before you can create an Oracle SOA Cloud Service instance that uses an Oracle Database Exadata Cloud Service database deployment. See Reserve IP Addresses for Oracle Database Exadata Cloud Service When Region Not Enabled.
  • Your Oracle SOA Cloud Service instance can use an Oracle Database Exadata Cloud Service database deployment for either the Oracle Required Schema or Application Schema databases.

Backup Location

Backups are recorded to a specified object storage location in Oracle Cloud.

For a service instance in an Oracle Cloud Infrastructure Classic region, you can create this storage container manually, or Oracle SOA Cloud Service can create one automatically while you are provisioning the service instance.

See Create an Object Storage Container.

Load Balancer

A load balancer routes requests it receives from clients to the WebLogic Servers configured in a service instance.

Using a load balancer within your service instance is recommended if you are configuring more than one Managed Server or more than one cluster. A load balancer also gives you the ability to suspend access to a service instance temporarily to perform routine maintenance.

Oracle SOA Cloud Service in Oracle Cloud Infrastructure Classic supports a user-managed load balancer that runs within your service instance. This load balancer is an instance of Oracle Traffic Director (OTD) and is administered through the Load Balancer Console. A service instance can include zero or one nodes running OTD. Each load balancer node is assigned a separate public IP address.