Before You Begin with Oracle SOA Cloud Service

There are some prerequisites before you begin using Oracle SOA Cloud Service.

Before you begin using Oracle SOA Cloud Service to create a service instance, you must have access details to a database and a remote storage disk, and have obtained details for the following: a database network through which the service instance will access the database, and a public network that will be used to access the service instance. You are also required to have a secure shell (SSH) public/private key pair so you can provide the public key when you create the service instance.

  • Database

    Oracle SOA Cloud Service requires access to an existing relational database that contains the standard Oracle Fusion Middleware schemas. The schemas are required by Oracle Java Required Files (JRF).

    You can use an on-premises database or a database that is deployed through Oracle Database Cloud Service.

    Note:

    • To coordinate restoration of database backups with restoration of Oracle SOA Cloud Service instances, consider using a database for which Flashback and Database Point-in-Time-Recovery support is enabled.

    When you create an Oracle SOA Cloud Service instance, you have to provide the following information about the database:

    • Connection string to the database in one of these formats: host:port:SID or host:port/service_name

    • User name for the database administrator

    • Password for the database administrator, or the password that was specified when the Oracle Database Cloud Service database deployment was created

  • Networks

    When creating an Oracle SOA Cloud Service instance, you have to provide a public access network and a database network.

    Contact your Oracle Cloud Administrator for the following networks:
    • Public Access Network: The path to the network that will be used to access the service instance, in the format /tenant_name/public/EoIB_vNet_name. For example, /mytenant/public/vnet-EoIB-vlan3072.

    • Database Network: The path to the network through which the service instance will access the database that contains the Oracle Fusion Middleware component schemas. For example, /mytenant/public/IPoIB-dbaccess.

  • Remote Backup

    Oracle SOA Cloud Service uses a remote networked disk to store Oracle SOA Cloud Service instance backups.

    The remote networked disk is not permanently attached to the service instance’s WebLogic Server Administration Server virtual machine.

    A remote networked disk is not required for service instances created at the Oracle SOA Cloud Service—Virtual Image service level. Only service instances created at the service level of Oracle SOA Cloud Service require access to a remote backup disk.

    When creating an Oracle SOA Cloud Service instance, you specify the remote backup disk to use by providing the URI in one of the following formats:

    • host_name:absolute_path_to_remote_backup_disk

    • host_ip:absolute_path_to_remote_backup_disk

    Note:

    A remote backup disk share must be owned by oracle:oracle or uid=1101 and gid=1000, and the permissions rwxr-xr-x or rwx------ must be given.
  • Virtual Machine (VM) public key

    An SSH public/private key pair is used for authenticating access to a VM through an SSH client. You generate an SSH public/private key pair using a standard SSH key generation tool. See Accessing a VM Through a Secure Shell (SSH).

    You may use the same SSH public/private key pair that you used for creating a service instance in Oracle Database Cloud Service.

    When you’re ready to create an Oracle SOA Cloud Service instance, you’d be prompted to supply the VM public key.

    To connect to a VM in an Oracle SOA Cloud Service instance, you’d supply the paired private key when logging in to the machine using an SSH client.

  • JDeveloper

    The current release of Oracle SOA Cloud service works with versions 12.1.3 and 12.2.1.2 of Oracle JDeveloper. You can download the Oracle SOA Suite 12.1.3 QuickStart (which includes Oracle JDeveloper) from Oracle SOA Suite 12.1.3 QuickStart Download and the 12.2.1.2 version from Oracle SOA Suite 12.2.1.2.0 QuickStart Download.

Prior to using Oracle SOA Cloud Service, ensure also you’re familiar with the following:

  • Oracle Compute Cloud Service on Oracle Cloud Machine

    For information about Oracle Compute Cloud Service on Oracle Cloud Machine, see Using Oracle Compute Cloud Service on Oracle Cloud Machine.

  • Oracle Compute VMs

    Oracle SOA Cloud Service runs on Oracle Compute VMs.See Using Oracle Compute Cloud Service for information about disk images, compute shapes, storage volumes, public IP addresses, and SSH public/private key pairs.

  • Oracle WebLogic Server

    Applications are deployed to Oracle WebLogic Server. Oracle SOA Cloud Service supports Oracle WebLogic Server 12c (12.1.3 and 12.2.1.2).

  • Oracle Traffic Director

    To provide load balancing for applications, Oracle SOA Cloud Service uses Oracle Traffic Director Release 12c. Starting with Release 12c, Oacle Traffic Director administration tasks are performed from Oracle Enterprise Manager Fusion Middleware Control. When accessing Oracle Traffic Director from the Oracle SOA Cloud Service Console, you are directed to Oracle Enterprise Manager Fusion Middleware Control:

    https://hostname/em
    

    To use and configure Oracle Traffic Director, see Oracle Traffic Director Administrator’s Guide.