Use an Oracle Database Exadata Cloud Service Database Deployment

Not Oracle Cloud Infrastructure This topic does not apply to Oracle Cloud Infrastructure.

You can create an Oracle SOA Cloud Service instance that uses an Oracle Database Exadata Cloud Service database deployment. A manual IP reservation procedure is required before you can create your instance.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 your instance.

Note:

If regions are enabled for your account and you select a region name on the service instance creation wizard, you can use reserved IP addresses for your VMs without using this procedure. Otherwise, you must use this procedure.

If you are not familiar with Oracle Database Exadata Cloud Service, see Creating a Database Deployment in Using Oracle Database Exadata Cloud Service.

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.
  1. Create an Oracle Database Exadata Cloud Service database deployment if you have not done already.
  2. Determine the initial size for the Oracle WebLogic Server cluster you will define when you create your Oracle SOA Cloud Service instance.
  3. Log in to support.oracle.com (My Oracle Support).
  4. File a Service Request to obtain authorized IP addresses for your Oracle SOA Cloud Service instance.
    Oracle will provide IP addresses and open up the firewall at these addresses on the Oracle Database Exadata Cloud Service.
    In the Service Request, specify the following information:
    • Your identity domain

    • Oracle Required Schema database name, which must be the name of the Oracle Database Exadata Cloud Service database deployment if you are not specifying a database deployment for the Application Schema

    • (Optional) Application Schema database deployment name

    • Desired number of servers in your WebLogic Server cluster