Provisioning Oracle SOA Suite on Oracle Java Cloud Service


Options



Before You Begin

Purpose

This tutorial provides instructions for extending an existing Oracle Java Cloud Service domain with Oracle SOA Suite.

The topology of the domain that you create can vary, depending upon how many virtual machines and how many Managed Servers that you provision as part of your Oracle Java Cloud Service subscription.

Time to Complete

Approximately 8 hours

Background

Oracle SOA Suite is an integrated suite of products that helps you rapidly design, assemble, deploy, and manage highly agile business applications. Oracle Java Cloud Service enables you to use an Oracle WebLogic Server domain and set up your Oracle SOA Suite environment without worrying about the infrastructure or platform components. All Oracle Java Cloud Service instances are preconfigured to use your Oracle Database Cloud Service instance and an object storage container that you create in Oracle Storage Cloud Service.

Oracle Java Cloud Service provides a platform to develop and deploy business applications in the cloud. Oracle Java Cloud Service provides instant access to a cloud environment with Oracle WebLogic Server, integrated security, and database access.

It is assumed that you created a domain that contains an Administration Server and a cluster of two Managed Servers. The cluster is deployed across two Oracle Java Cloud Service virtual machines. A similar topology is shown in a diagram and described in detail in About the Deployment Topology of Virtual Machines in Using Oracle Java Cloud Service. Your actual topology may vary.

What Do You Need?

To create a storage container, an Oracle Database Cloud Service instance and an Oracle Java Cloud Service instances, ensure that you have a subscription to each of the following:

  • Oracle Storage Cloud Service
  • Oracle Database Cloud Service
  • Oracle Java Cloud Service

See Getting Started with Oracle Cloud in the Oracle Help Center.

This tutorial assumes that your environment is set up as follows, and as described in Setting Up Your Environment.

  • Operating System: Oracle Linux 6.4
  • Secure Shell (SSH) key: You need an SSH key to create your Oracle Database Cloud Service and Oracle Java Cloud Service instances. Ensure that your SSH key has a bit size of 2048 or higher.
  • Database version: 11g Release 2 (Enterprise Edition). You select the database version when you create your Oracle Database Cloud Service instance.
  • Oracle WebLogic Server version: 11.1.1.7. You select the Oracle WebLogic Server version when you create your Oracle Java Cloud Service instance.
  • Oracle WebLogic Server edition: Enterprise with Oracle Coherence. You select the Oracle WebLogic Server edition when you create your Oracle Java Cloud Service instance.
  • Oracle Java Cloud Service cluster size: 2 nodes, plus load balancer. You select the cluster size when you create your Oracle Java Cloud Service instance. For this tutorial, ensure that you select the Virtual Image service level. You must also select the load balancer option. When your Oracle Java Cloud Service instance is created, you will see three Oracle Compute Units (OCPUs) in the service console. These OCPUs include the nodes on the cluster as well as the load balancer.

    This tutorial refers to the three OCPUs as follows:

    • Virtual Machine (VM)1: The OCPU that hosts the Administration Server and one Managed Server
    • VM2: The OCPU that hosts the second Managed Server
    • VM3: The OCPU that hosts the load balancer
  • Compute Shape: You select a compute shape while creating Oracle Database Cloud Service and Oracle Java Cloud Service instances. Select the compute shape: OC3 – 1 OCPU, 7.5 GB RAM
  • Oracle SOA Suite version: 11.1.1.7.0. You select the Oracle SOA Suite version when you run the configuration wizard to extend your Oracle Java Cloud Service domain.

Note:

While performing these tasks, keep a record of all the user names and passwords that you enter because you'll need them later while performing provisioning or administration tasks.

Setting Up Your Environment

Creating Cloud Storage Containers

Use the Oracle Storage Cloud Service to create an object storage container. This container will be used by the database when you create your Oracle Database Cloud Service instance.

When you subscribe for an Oracle Cloud account, you will receive an email with the details for signing in to My Services. Follow the link and use the credentials in that email to access your My Services Dashboard.

Note: Remember to bookmark your My Services page, so that you can access it easily in future.

To create a container:

  1. Sign in to the My Services application.
  2. On the My Services Dashboard, click View Details for Oracle Storage Cloud Service.

    View Details menu item

  3. Find out your REST endpoint.

    Go to the Oracle Storage Cloud Service section of the dashboard, click the menu icon and select View Details. The Oracle Storage Cloud Service details page provides the REST endpoint.

    Note: Alternatively, you can click the Oracle Storage Cloud Service link on the dashboard to go to the Oracle Storage Cloud Service details page.

  4. Enter the following command in the command shell to get an authentication token:
    curl -v -X GET -H 'X-Storage-User: Storage-domain:username ' -H 'X-Storage-Pass: your_password ' https://storage.data-region-code.oraclecloud.com/auth/v1.0

    In the preceding command:

    • Storage-domain: Domain name of the subscribed Oracle Storage Cloud service
    • storage.data-region-code: The full web address of the Oracle Storage Cloud data region
    • username: Your Oracle Public Cloud Services username (typically the email address associated with your Oracle Cloud account)
    • your_password: Your Oracle Public Cloud Services password

    For example:

    $<curl –k -v -X GET -H 'X-Storage-User:
    Storage-MYDOMAIN:aaa@xyz.com' 
    -H 'X-Storage-Pass:Oracle@1' https://storage.dc1.oraclecloud.com/auth/v1.0
  5. From the response, note the X-Storage-Url and X-Auth-Token values.

    For example:

    • X-Storage-Url: https://storage.dc1.oraclecloud.com/v1/ Storage-MYDOMAIN
    • X-Auth-Token: AUTH_tk209f7f2ea1265a0d3f29d28a2dc8ced6
  6. Enter the following command to create the storage container:
    curl -v -H 'X-Auth-Token: your_auth_token ' -X PUT https://storage.data-region-code.oraclecloud.com/v1/Storage-IdentityDomain/container_name

    You'll get the following response:

    HTTP/1.1 201 Created
  7. Get a list of containers to verify that your container is created.
    curl -v -H 'X-Auth-Token: your_auth_token' https://storage.data-region-code.oraclecloud.com/v1/Storage-IdentityDomain/

    The value of the storage container would be:

    Storage-IdentityDomain/wcpcontainer

Generating an SSH Key Pair

When you create an Oracle Database Cloud Service instance and an Oracle Java Cloud Service instance, you'll have to provide an SSH public key that will be used for authentication when you log in to an instance. You can either specify an SSH key that was uploaded earlier or upload a new SSH public key.

To generate an SSH key pair:

  1. Run the ssh-keygen command.
    ssh-keygen -b 2048 -t rsa
  2. The command prompts you to enter the path to the file in which you want to save the key. A default path and file name are suggested in parentheses. For example: /home/user_name/.ssh/id_rsa. To accept the default path and file name, press Enter. Otherwise, enter the required path and file name, and then press Enter.
  3. The command prompts you to enter a passphrase, which is used for encrypting your private key. A null entry is strongly discouraged. Note that the passphrase isn't displayed when you type it in.
  4. When prompted, enter the passphrase again to confirm it.
  5. The command generates an SSH key pair consisting of a public key and a private key, and saves them in the specified path. The file name of the public key is created automatically by appending the string .pub to the name of the private key file. For example, if the file name of the SSH private key is id_rsa, then the file name of the public key would be id_rsa.pub.

    Note: Make a note of the passphrase and the path where you've saved the SSH key pair. When you create Oracle Database Cloud Service and Oracle Java Cloud Service instances, you'll have to enter the SSH public key. When you log in to an instance, you'll have to provide the path to the corresponding SSH private key and you'll have to enter the passphrase when prompted.

Creating an Oracle Database Cloud Service Instance

  1. Sign in to the My Services application.
  2. On the My Services Dashboard page, click Consoles and select Oracle Database Cloud Service.

    selecting the Database console

    The Oracle Database Cloud Service Console appears.

  3. On the Oracle Database Cloud Service Console, click Create Instance.

    clicking Create Instance button

  4. On the Subscription Type page, select Oracle Database Cloud Service, the billing frequency, and then click Next.

    Selecting Oracle Database Cloud Service

  5. On the Software Release page, select Oracle Database 11g Release 2, and click Next.

    Selecting Oracle Database 11g Release 2

  6. On the Software Edition page, select Enterprise Edition, and click Next.

    Selecting the Enterprise Edition

  7. On the Service Details page, configure the settings for your instance, and click Next.

    configuring instance settings

  8. On the Confirmation page, review the information listed. If you're satisfied with the information, then click Create.

    Confirmation page

    The Oracle Database Cloud Service instance is created.

    database instance created

Creating an Oracle Java Cloud Service Instance

  1. Sign in to the My Services application and go to the My Services Dashboard.
  2. In the Oracle Java Cloud Service section, click Open Service Console. The Oracle Java Cloud Service Console page appears.
  3. Click Create Instance. The Create New Oracle Java Cloud Service Instance wizard starts and the Subscription Type page appears.

    Create Java Cloud Service Instance - Subscription screen

  4. Select the Oracle Java Cloud Service – Virtual Image option and the billing frequency that you require. Click Next.
  5. On the Software Release page, select Oracle WebLogic Server 11g (11.1.1.7). Click Next.

    Create Java Cloud Service Instance - Release screen

  6. On the Software Edition page, select Enterprise Edition with Coherence. Click Next. The Instance Details page appears.

    Create Java Cloud Service Instance - Edition screen

  7. In the Instance Configuration section, enter the following information:
    • Instance name
    • Description
    • Compute shape – This allows you to specify the number of OCPUs and RAM that each node on your instance should have. Select OC3 – 1 OCPU, 7.5 GB RAM.
    • VM public key – To add the SSH key that you generated earlier:
      1. Click Edit and select the Key file name option.
      2. Click Browse to navigate to the folder where you saved the SSH public key.
      3. Select the SSH public key and then click Enter.
  8. In the WebLogic Administrator section, enter the user name and password that you want to use.

    Note: Please note that your password conforms to the Oracle password policy.

  9. In the Database Configuration section, enter the following information:
    • Name – Select the name of the Oracle Database Cloud Service instance that you created earlier.
    • Database Administration User Name – Enter the user name SYSTEM.
    • Password – Enter the Administrator password that you specified while creating the Oracle Database Cloud Service instance.
  10. In the Load Balancer section, enter the following information:
    • Provision Load Balancer – Select Yes.
    • Load Balancer Policy – Select the appropriate policy.
    • Compute Shape – Select OC3 – 1 OCPU, 7.5 GB RAM.
    JCS configuration
  11. Click Next.
  12. On the Confirmation page, review the information and then click Create to create your Oracle Java Cloud Service instance.

Performing Preinstallation Steps

When you created your Oracle Java Cloud Service instance, you were provided with details about the required database. To extend the Oracle Java Cloud Service domain for Oracle SOA Suite or Oracle Service Bus, you must connect to the same database and install the required SOA schemas.

To verify the details of the database, see Accessing the Oracle Database Cloud Service Console in Using Oracle Database Cloud Service.

Oracle Java Cloud Service creates schemas for Oracle Metadata Services (MDS) and Oracle Platform Security Services (OPSS) when it provisions the domain. The password for these schemas is the same as the Oracle WebLogic Server Administration User password that you specified when you created your Oracle Java Cloud Service instance.

Next, complete the following preinstallation tasks:

  • Connect to the Oracle Java Cloud Service environment using a secure shell (SSH)
  • Verify that the TMP directory exists and is writable
  • Configuring the X Window system and starting a Virtual Network Computing (VNC) session
  • Downloading the Oracle software and copying It to the virtual machines (VMs)
  • Backing up your domain

Connecting to the Oracle Java Cloud Service Environment Using SSH

When you create an instance of the Oracle Java Cloud Service, all the Oracle Compute Cloud Service VMs required to support the service are provisioned and configured for you. You can access the services and resources provided by the VMs by logging in to the machine through an SSH. You'll access the VMs from your local machine by using the ssh command in a UNIX command shell.

  1. To create an SSH tunnel, you must find the IP address of the VM hosting your Oracle Java Cloud Service instance.
    1. Sign in to the My Services application at http://cloud.oracle.com.
    2. On the My Services Dashboard, click Consoles and select Oracle Java Cloud Service.
    3. On the Oracle Java Cloud Service Console, click the instance.
    4. The public IP address of the Administration Server is available under the Virtual Machines section. Make a note of the IP address.
  2. In a command shell, run the ssh utility:
    $> ssh -i path_to_SSH_private_key opc@IP_address_of_VM1

    In the preceding command:

    • path_to_SSH_private_key is the path to the SSH private key file that matches the public key used when your instance was created.
    • IP_address_of_VM1 is the public IP address of the Admin Server VM in n.n.n.n format.
    • opc is the user account.

    For example:

    $> ssh -i keys/id_rsa opc@192.0.2.100
  3. If this is the first time that you're connecting to the VM, then the ssh utility prompts you to confirm the public key. In response to the prompt, enter yes.

    At the prompt, enter the passphrase for the SSH key, if one was created.

Verifying That the TMP Directory Exists and Is Writable

When you created your Oracle Java Cloud Service, the /tmp directory was created automatically. Ensure that the opc user has the correct tmp variables defined, and verify the /tmp directory has the correct permissions by running the following commands on VM1:

  1. Edit the .bashrc file:
    vi ~opc/.bashrc
  2. Change the value of the following files to =/tmp:
    • export TMPDIR=/tmp
    • export TEMPDIR=/tmp
    • export TMP=/tmp
    • export TEMP=/tmp
  3. Rerun:. ~opc/.bashrc
  4. Check the permission of the /tmp directory:
    cd /
    ls –l 
  5. If the permission is not currently 777, change the permission of the /tmp directory:
    sudo chmod 777 /tmp 

Configuring the X Window System and Starting a VNC Session

The installation and configuration tools that you use to install and configure Oracle SOA Suite and Oracle Service Bus require the X Window System. The X Window System is installed on the virtual machines that you procured when you registered for Oracle Java Cloud Service.

Perform the following tasks to be able to open an xterm (standard terminal emulator for the X Window System) or the configuration wizard GUI on your monitor:

  1. As an opc user, edit the sshd_config file (the configuration file for the secure shell daemon program) on VM1:
    sudo vi /etc/ssh/sshd_config

    Ensure that all instances of the X11Forwarding parameter are set to yes:

    X11Forwarding yes
  2. Restart sshd by running the following command on VM1:
    sudo /etc/init.d/sshd restart
  3. Run the following command to prevent the Window Manager from displaying a lock screen:
    gconftool-2 -s -t bool /apps/gnome-screensaver/lock_enabled false
  4. Start the VNC server by running the following command on VM1:
    vncserver :1 -depth 16 -alwaysshared -geometry 1200x750 -s off

    Note: You must provide a password for the VNC server. If you're not prompted for a password, use the vncpasswd command to specify a password.

  5. On your local machine, create an SSH tunnel for the VNC server:

    ssh -4 -L 6905:127.0.0.1:5901 -N -f -i path_to_SSH_private_key -l opc IP_address_of_VM1

    In the preceding command:

    • path_to_SSH_private_key is the complete path of the VM private key
    • IP_address_of_VM1 is the public IP address of the Oracle Java Cloud Service instance
    • 5901 is the vncserver listening port defined in /usr/bin/vncserver
      $vncPort = 5900 + $displayNumber;

    Because the $displayNumber is set to 1 in the previous command, the listening port for vnc session :1 is 5901.

    Tip: This tutorial uses the local port 6905. If you get an error while setting up the SSH tunnel using this local port, check if this port is available or is already being used on your local host. Use netstat –ntpl to check the status of ports on your local host. Use any available port.

  6. On your local machine, if you have not already done so, set the DISPLAY environment variable:

    If you're using a Bash shell:

    export DISPLAY=IP_address_of_local_machine:1

    If you're using a C shell:

    setenv DISPLAY "IP_address_of_local_machine:1"
  7. Use a VNC viewer application to access the VNC session that a tunnel was created for:

    vncviewer 127.0.0.1:6905
  8. From the VNC viewer application, you will have access as an opc user and can switch to the oracle user to use the configuration wizard and other features.
    xhost +
    sudo su - oracle
    ### For example:
    /u01/app/oracle/middleware/oracle_common/common/bin/config.sh

    Note: Use this VNC window to run the installation and configuration files.

Downloading the Oracle Software and Copying It to the Virtual Machines

The following table lists the products that you must download depending on the topology that you're creating. Download the required zip files by referring to the Oracle Fusion Middleware Download, Installation, and Configuration ReadMe Files page.

Topology Files to Download and Install
SOA cluster
  • Oracle SOA Suite 11g (11.1.1.7.0)
  • Latest Patch Set release of Oracle SOA Suite 11g (11.1.1.7.0)

Note that Oracle WebLogic Server and Oracle Fusion Middleware Repository Creation Utility (Oracle Fusion Middleware RCU) were installed when you created the Oracle Java Cloud Service instance. You'll also use the same database that you've used when you created the Oracle Java Cloud Service instance.

  1. Download the Oracle SOA Suite installation files to your local machine:
    1. Go to the Oracle SOA Suite 11g Downloads page.
    2. Click the radio button to accept the license agreement.
    3. From the Release 11gR1 (11.1.1.7.0) drop-down list, select Linux 64bit JVM.
    4. Expand the Prerequisites and Recommended Install Process section.
    5. Scroll to the Product Installation section and download the following packages:

      SOA Suite 11.1.1.7.0 Part 1 of 2

      SOA Suite 11.1.1.7.0 Part 2 of 2

      Note: You need to download only the Oracle SOA Suite installation packages. Other packages are preinstalled on your Oracle Java Cloud Service instance.

  2. If you're still an oracle user, then run the exit command to become an opc user again. Ensure that the u01/zips directory on the Administrator VM (VM1) has write permissions set by the opc user:
    sudo chmod 755 /u01
    sudo chmod 777 /u01/zips
  3. Create a directory for the Oracle SOA Suite zip files and set permissions for this directory.
    mkdir /u01/zips/soa
    
    sudo chmod 777 /u01/zips/soa
  4. On your local machine, use thescp command to copy the downloaded Oracle SOA Suite installation files to the /u01/zips/soa directory on the Administrator VM (VM1):
    scp -i path_to_SSH_private_key path_to_downloaded_files/*soa*.zip opc@IP_address_of_VM1:/u01/zips/soa

    In the preceding command:

    • path_to_SSH_private_key path is the complete path of the VM private key
    • IP_address_of_VM1 is the public IP address of the Oracle Java Cloud Service instance

    Note: It may take up to 1 hour to copy the installation files to VM1.

  5. After the files are in the Admininistrator VM (VM1), ensure that you own them and have the appropriate permissions set for the oracle user:
    ssh -i path_to_SSH_private_key opc@IP_address_of_VM1
    ..
    cd /u01/zips/soa
    sudo chown oracle:oracle *.zip
    sudo chmod 755 *.zip

    In the preceding command:

    • path_to_SSH_private_key path is the complete path of the VM private key
    • IP_address_of_VM1 is the public IP address of the Oracle Java Cloud Service instance

    Note: For multiple VMs, copy the zip files to all VMs. A quick method to do this is to use the scp command from the Administrator VM (VM1) to copy the files to the other VMs. When you use either the ssh or scp command to connect or copy files from the administrator VM to the other VMs, don't use their public IP addresses. Use the internal host name that can be found in the VM details page of the Oracle Java Cloud Service Console.

Copying the soa*.zip Files to the Second Oracle Java Cloud Service Node

  1. Get the private IP address of VM2:
    1. Sign in to the My Services application and go to the My Services Dashboard.
    2. In the Oracle Compute Cloud Service section, click the Open Service Console link .

      Opening Compute console

    3. Click <domain_name> wls 2. This is the second node of your two-node Oracle Java Cloud Service cluster.

      clicking the domain name

    4. On the instance details page, make a note of the private IP address of this instance.
  2. Use the ssh command to log in to VM1 as the opc user.
  3. Use the scp command to copy your private key from your local machine to VM1. You will need this private key on VM1 when you use scp to copy the zip files from VM1 to VM2. On your local machine, run the following command:
    scp -i path_to_SSH_private_key path_to_SSH_private_key opc@IP_address_of_VM1:/home/opc
  4. On VM1, restrict permissions on the private key file.
    sudo chmod 600 /home/opc/private_key_name

    Tip: Optionally, you can also move the private key to an appropriate directory on VM1, such as /home/opc/.ssh/authorized_keys.

  5. Use the ssh command on VM1 to log in to VM2 as the opc user.
    ssh –i path_to_SSH_private_key opc@Private_IP_address_of_VM2
  6. Create the /u01/zips/soa directory and ensure that the directories on VM2 have write permission.
    sudo chmod 777 /u01
    
    sudo chmod 777 /u01/zips
    
    mkdir /u01/zips/soa
    
    sudo chmod 777 /u01/zips/soa
    
  7. On VM1, use the scp command to quickly copy the SOA zip files to VM2.
    scp –i path_to_SSH_private_key /u01/zips/soa/*soa*.zip opc@Private_IP_address_of_VM2:/u01/zips/soa
  8. On VM2, set permissions for the oracle user.
    sudo chown oracle:oracle *.zip
    sudo chmod 755 *.zip

Backing Up Your Domain

Before you start any pre-provisioning and provisioning tasks, we recommend that you back up your existing domain.

For example:

Change to the oracle user to perform the task:

sudo su - oracle
cd /u01/data
cp -r domains domains.orig

Creating Oracle SOA Suite Schemas

This section describes how to use Oracle Fusion Middleware RCU to create the required Oracle SOA Suite schemas.

Note: You must change the user to oracle when provisioning Oracle SOA Suite on Oracle Java Cloud Service.

sudo su - oracle

Ensure that you use the same schema prefix that you used when you created the Oracle Metadata Services (MDS) schema that is already in use by the Oracle WebLogic Server domain. Oracle SOA Suite 11g requires the SOAINFRA and ORASDPM schemas. The MDS schema should already exist.

You can create Oracle SOA Suite schemas by using either of the following:

Finding Out Your Schema Prefix, Oracle Database Cloud Service Host Name, Port, and Service Name

When you run the Oracle Fusion Middleware RCU to create the Oracle SOA Suite schemas, you must use the same schema prefix that is used by the MDS schema. To find the schema prefix used by the MDS schema, review the Oracle Database Cloud Service instance properties, or run the following command:

more $DOMAIN_HOME/config/jdbc/mds-owsm-jdbc.xml

To get the database host name, database port, database service name and schemaPrefix details from the output of the preceding command:

  • database host name (dbhost), database port (dbport), database service name (dbservice) are available in the <url> parameter that follows the at sign (@)in the mds-owsm-jdbc.xml file. For example:
    jdbc:oracle:thin:@SOA11g:1521/ORCL.dbvmhost1.example.com

    In this example:

    • Database Host Name (dbhost): SOA11g
    • Database Port (dbport): 1521
    • Database Service Name (dbservice): ORCL.dbvmhost1.example.com
  • schemaPrefix is string that appears before _MDS. For example:
    SP169663410
    <property>    
       <name>user</name>    
       <value>SP169663410_MDS</value> 
    </property> 

    Note: To run Oracle Fusion Middleware RCU, Username (dbUser) should be a database user with the SYS or SYSDBA role (dbRole).

Running the Oracle Fusion Middleware RCU Wizard to Create Schemas

  1. If you logged out of VM1, use the ssh command to log in as the opc user.
  2. Set the DISPLAY variable:
    export DISPLAY=IP_address_of_VM1:1
  3. Disable access control.
    xhost +
  4. Use sudo to become the oracle user.
    sudo su – oracle
  5. Launch the Oracle Fusion Middleware RCU wizard to create the Oracle SOA Suite schemas that you require.
    /u01/app/oracle/middleware/rcuHome/bin/rcu
  6. When the Oracle Fusion Middleware RCU wizard launches, on the Welcome page, click Next.
  7. On the Create Repository page, select Create Repository and then click Next.
  8. On the Database Connection Details page, enter the following details that you've collected from Finding Out Your Schema Prefix, Oracle Database Cloud Service Host Name, Port, and Service Name:
    • Host Name – The name of your Oracle Database Cloud Service instance; for example, SOA11g.
    • Port – Usually 1521.
    • Service Name – The SID followed by your fully qualified Identity Domain name, separated by a dot (.); for example, ORCL.dbvmhost1.example.com.
    • Username –The default user SYS.
    • Password – The Administration password that you specified for the Oracle Database Cloud Service instance while creating the Oracle Java Cloud Service instance.

    Database Connection Details screen

  9. Click Next.
  10. On the Checking Global Prerequisites page, click OK.
  11. On the Select Components page:
  12. Click Next.
  13. On the Checking Component Prerequisites page, click OK.
  14. On the Schema Passwords page, select Use same passwords for all schemas. Enter your password in the Password and Confirm Password fields. Use the same password that was assigned by the Oracle Java Cloud Service when it created the MDS and OPSS schemas.

    Tip: Make a note of this password. You will need it later.

  15. Click Next.
  16. On the Map Tablespaces page, you do not need to make any changes. Click Next. A confirmation message appears.
  17. Click OK.
  18. On the Validating and Creating Tablespaces page, when the validation is complete, click OK.
  19. On the Summary page, review the information and then click Create.

Running the Oracle Fusion Middleware RCU in Silent Mode to Create Schemas

If you've created the schemas by running the Oracle Fusion Middleware RCU Wizard as described in Running the Oracle Fusion Middleware RCU Wizard to Create Schemas, then ignore this section.

Alternatively, to run the Oracle Fusion Middleware RCU in slient mode, run the following command as the oracle user on VM1 console:

/u01/app/oracle/middleware/rcuHome/bin/rcu -silent
   -createRepository 
   -connectString <dbhost:dbport/dbservice>
   -dbUser SYS
   -dbRole SYSDBA
   -schemaPrefix <schemaPrefix>
   -useSamePasswordForAllSchemaUsers true
   -databaseType ORACLE
   -lockSchemas false
   -component SOAINFRA 
   -component ORASDPM

Note: There shouldn't be breaks in the lines between the different parameters. Don't copy and paste the preceding command directly on the VM1 console. Doing that would cause the command to fail.

In the above command, specify the values of dbhost, dbport, dbservice, dbUser, and schemaPrefix that you have obtained from the section Finding Out Your Schema Prefix, Oracle Database Cloud Service Host Name, Port, and Service Name.

This command will prompt you for two passwords:

  • The password for the dbUser (SYS): The Administration password that you specified for the Oracle Database Cloud Service instance when you created the Oracle Java Cloud Service instance.
  • The password for the schemas: Use the same password as the one that was assigned by the Oracle Java Cloud Service when it created the MDS and OPSS schemas. That password is the same as the one specified for WebLogic Server Administrator in Step 8 of Creating an Oracle Java Cloud Service Instance.

Installing Oracle SOA Suite

You can install the Oracle SOA Suite software by following the instructions in Installing Oracle SOA Suite and Oracle Business Process Management Suite in Installation Guide for Oracle SOA Suite and Oracle Business Process Management Suite.

However, we recommend that you use the provided response file to perform a silent installation, without using the installer's graphical user interface:

  1. Extract the install files.
    cd /u01/zips/soa
    
    unzip ofm_soa\*.zip

    Note: Using the escape character \ allows you to extract the Oracle SOA Suite installer zip files with a single unzip command.

  2. To run the Oracle SOA Suite installer in silent mode, you require the Oracle SOA Suite response file (soa.rsp) and the Inventory Pointer file (jcs.invptr). Create the soa.rsp and jcs.invptr files with the following content and copy them to a directory, for example: /u01/zips/soa/Disk1/soa.rsp and /u01/zips/soa/Disk1/jcs.invptr.

    soa.rsp File

    [ENGINE]
     
    #DO NOT CHANGE THIS.
    Response File Version=1.0.0.0.0
     
    [GENERIC]
     
    #Set this to true if you wish to specify a directory where the latest updates are downloaded. This option would use the software updates from the specified directory
    SPECIFY_DOWNLOAD_LOCATION=false
     
    #
    SKIP_SOFTWARE_UPDATES=true
     
    #If the Software updates are already downloaded and available on your local system, then specify the path to the directory where these patches are available and set SPECIFY_DOWNLOAD_LOCATION to true
    SOFTWARE_UPDATES_DOWNLOAD_LOCATION=
     
    #Provide the Oracle Home location. The location has to be the immediate child under the specified Middleware Home location. The Oracle Home directory name may only contain alphanumeric , hyphen (-) , dot (.) and underscore (_) characters, and it must begin with an alphanumeric character. The total length has to be less than or equal to 128 characters. The location has to be an empty directory or a valid SOA Oracle Home.
    ORACLE_HOME=/u01/app/oracle/middleware/soa
     
    #Provide existing Middleware Home location.
    MIDDLEWARE_HOME=/u01/app/oracle/middleware
     
    #Application Server choices are WLS, WAS
    APPSERVER_TYPE=WLS
     
    #Provide the Application Server Location.
    APPSERVER_LOCATION=/u01/app/oracle/middleware
     
     
    [SYSTEM]
     
     
    [APPLICATIONS]
     
     
    [RELATIONSHIPS]

    jcs.invptr File

    inventory_loc=/u01/app/oraInventory
    inst_group=prefex
  3. Ensure that both the soa.rsp file and the jcs.invptr file have permissions set to 775. If not, to set the permissions run the following commands as the opc user on VM1:
    sudo chmod 775 /u01/zips/soa/Disk1/soa.rsp
    
    sudo chmod 775 /u01/zips/soa/Disk1/jcs.invptr
    
    sudo su - oracle
  4. Navigate to the Disk1 directory.
    cd /u01/zips/soa/Disk1
  5. Run the installer.
    ./runInstaller -silent -ignoreDiskWarning -noValidation -ignoreSysPrereqs -waitforcompletion -jreLoc /u01/jdk -response full_path_to_soa.rsp -invPtrLoc full_path_to_jcs.invptr

    Tip: After installation completes, you can reclaim the file system space by deleting the extracted files.

Note: For multiple VMs, you must install the software on each VM.

Installing Oracle SOA Suite on the Second Oracle Java Cloud Service Node

  1. Get the private IP address of VM2:
    1. Sign in to the My Services application and go to the My Services Dashboard.
    2. In the Oracle Compute Cloud Service section, click the Open Service Console link.

      Opening Compute console

    3. Click <domain_name> wls 2. This is the second node of your two-node Oracle Java Cloud Service cluster.

      clicking the domain name

    4. On the instance details page, make a note of the private IP address of this instance.
  2. Use the ssh command to log in to the second node as oracle user.
    $> ssh –X Private_IP_address_of_VM2
  3. Install Oracle SOA Suite software as shown in the Installing Oracle SOA Suite section.

Enabling DB Policy Stores

Oracle Java Cloud Service includes an embedded LDAP service, configured for the domain. As a result, you don't have to perform additional tasks or configure a remote directory service.

Oracle SOA Suite requires a database policy store.

Creating an OPSS Data Source

  1. Go to the Oracle WebLogic Server Console by entering the http://administration_server_host:administration_server_port/console URL.

    For example: https://<Admin_VM_IP> :7002/console

  2. Go to Services and then click DataSources.
  3. In the Summary of JDBC Data Sources page, check if the opss-ds data source appears. If it is, then skip the remaining steps in this section and proceed to the section Associating the Policy Store with OPSS Data Source. If the opss-ds data source is not displayed in the list of data sources, then you must create it. Start a new edit session by clicking Lock & Edit.
  4. Click Lock & Edit to start a new edit session.
  5. Click New and then Generic DataSource. Add the following:
    • Name: OPSSDS
    • JNDI Name: jdbc/OPSSDS
    • Database Type: Oracle
  6. Click Next and select Oracle's Driver (Thin) for Instance connections from the Database Driver drop-down list.
  7. Click Next and deselect Supports Global Transactions.
  8. Click Next and add the following:
    • Database Name: dbservice
    • Host Name: dbhost
    • Port: dbport
    • Database User Name: schemaPrefix_OPSS

      Specify the values of dbhost, dbport, dbservice, dbUser, and schemaPrefix that you have obtained from the section Finding Out Your Schema Prefix, Oracle Database Cloud Service Host Name, Port, and Service Name.

      Note that OPSS schemas were already provided with the Oracle Java Cloud Service environment.

    • Password: Schema password used with Oracle Fusion Middleware RCU

      Use the same password that was assigned by Oracle Java Cloud Service when it created the MDS and OPSS schemas. That password is the same as the one specified for Oracle WebLogic Server Administrator.

  9. Click Next and select Test Configuration to ensure that your changes have been made.
  10. Click Next and select Administration Server and OSB_Cluster.
  11. Click Finish and click Activate Changes.

Associating the Policy Store with an OPSS Data Source

  1. Log on to Oracle Enterprise Manager Fusion Middleware Control Console by entering the URL http://administration_server_host:administration_server_port/em.
  2. Under Weblogic Domain, right-click your domain name.
  3. From the drop-down list under the domain name, select Security and then click Security Provider Configuration.
  4. Click Change Store Type.
  5. From the Store Type drop-down list, select Oracle Database.
  6. Enter the data source JNDI name that you've created for the OPSS DataSource (jdbc/OPSSDS), or click Select and select the data source JNDI name from the list.
  7. Enter the user name that you provided while creating the OPSS data source. The user name is of the format schemaPrefix_opss.
  8. Enter your Oracle Fusion Middleware RCU password, which is the same as your Oracle WebLogic Server Administrator password.
  9. In the Root DN field, enter cn=jpsNode.

    Note:This jpsNode can be any name, and it is used to name the node created in the database for the policy store.

  10. Enter the domain name, select Create New Domain and click OK.
  11. After the confirmation message appears, click Yes.
  12. When security store configuration completes, click Close.
  13. Restart the servers:
    1. Sign in to the Oracle WebLogic Server Administration Console.
    2. From the Environment menu in the left pane, select Servers.
    3. In the Summary of Servers page, click the Control tab.
    4. Shut down both the Managed Servers if they are running.
    5. Shut down the Administration Server.
    6. Use the command line script to restart Administration Server:
      /u01/data/domains/<domain_name>/startWebLogic.sh
    7. After the Administration Server is in the RUNNING state, use the Oracle WebLogic Server Administration Console to restart the Managed Servers.
  14. Make a backup of the domain.

    For example:

    Change to the oracle user to perform the task:

    sudo su - oracle
    cd /u01/data
    cp -r domains domains.orig

Extending the Oracle Java Cloud Service Domain

Before you begin extending the Oracle Java Cloud Service domain, use the Oracle WebLogic Server Administration Console to shut down all Managed Servers and the Administration Server if they are up.

To extend your domain:

  1. Use the configuration wizard to extend the Oracle Java Cloud Service domain with Oracle SOA Suite.
    /u01/app/oracle/middleware/oracle_common/common/bin/config.sh
  2. In the Welcome page, select Extend an existing WebLogic domain, and click Next.
  3. In the WebLogic Domain Directory page, select the following WebLogic domain directory:
    u01/data/domains/domain_name

    Click Next.

  4. In the Select Extension Source page, do the following:
    1. Select Extend my domain automatically to support the following added products.
    2. Select Oracle SOA Suite - 11.1.1.0 [soa].
      The following products should already be selected, and grayed out. They were selected when you created the domain in your Oracle Java Cloud Service instance:
      • Basic WebLogic Server Domain
      • Oracle Enterprise Manager
      • Oracle Web Services Manager (WSM) Policy Manager
      • Oracle JRF (Java Required Files) WebServices Asynchronous Services
      • Oracle JRF

      Click Next.

      If you get a Conflict Detected message that Oracle JRF is already defined in the domain, then select the Keep Existing Component option and click OK.

  5. In the Configure JDBC Data Sources page, select the OPSS data source, verify the following, and then click Next:
    • User Name: schemaPrefix_opss
    • Password: WLS_Admin_password
    • DBMS/Service: dbservice
    • Host Name: dbhost or IP_address_of_your_database_instance.

    Refer to the values of dbhost, dbservice, and schemaPrefix that you have obtained from the section Finding Out Your Schema Prefix, Oracle Database Cloud Service Host Name, Port, and Service Name.

  6. In the Test JDBC Data Sources page, select the OPSS data source and click Test Connections. If the connection fails, then click Previous to return to the previous page and correct your entries. If the connection is successful, then click Next.
  7. In the Configure JDBC Components Schema page:
    1. Select SOA Infrastructure, User Messaging Service, and SOA MDS Schema.
    2. In the Schema Password, DBMS/Service and Host Name fields, enter the same details that you verified in Step 5 above.
    3. In the Schema Owner column, verify that the appropriate schema prefix is used for each schema. If required, enter the appropriate schema owner for each schema in the Schema Owner field, and then click Next.
      • SOA Infrastructure: schemaPrefix_SOAINFRA
      • User Messaging Service: schemaPrefix_ORASDPM
      • SOA MDS Schema: schemaPrefix_MDS
  8. In the Test JDBC Data Sources page, confirm that all connections that were made are successful.

    The connections are tested automatically. The Status column displays the results. If all connections aren't successful, then click Previous to return to the previous page and correct your entries.

    When all the connections are successful, click Next.

  9. In the Select Optional Configuration page, select the following:
    • JMS Distributed Destination
    • Managed Servers, Clusters and Machines
    • Deployments and Services
    • JMS File Store

    Click Next.

  10. In the Select Java Message Service (JMS) Distributed Destination Type page, ensure that all the JMS system resources are configured to be uniform distributed destination (UDD). This should be the default setup. Click Next.
  11. In the Configure Managed Servers page, add the required Managed Servers.
    1. By default, the Managed Servers will be populated already. You can either rename them or use them as they are.

      For this tutorial, the Managed Servers were renamed to JCS_SOA1 and JCS_SOA2, and they will be referenced with these names.

      To avoid targeting related libraries and applications to the default SOA server instead of to the SOA cluster, delete the default SOA server by:
      Select soa_server1 and click Delete.

    2. Give servers JCS_SOA1 and JCS_SOA2 the attributes listed in following table:

      Select soa_server1 and click Delete.

      Name Listen Address Listen Port SSL Listen Port SSL Enabled
      JCS_SOA1 All Local Addresses 8001 N/A No
      JCS_SOA2 All Local Addresses 8001 N/A No
  12. In the Configure Clusters page, rename the cluster to SOA_Cluster.

    Click Next.

    Note: For asynchronous request/response interactions over direct binding, the SOA composite applications must provide their JNDI provider URL for the invoked service to look up the beans for callback.

    If soa-infra configuration properties are not specified, but the Oracle WebLogic Server Cluster address is specified, the cluster address from the JNDI provider URL is used. This cluster address can be a single Domain Name System (DNS) name that maps to the clustered servers' IP addresses or a comma-separated list of server ip:port. Alternatively, the soa-infra configuration property JndiProviderURL/SecureJndiProviderURL can be used for the same purpose if explicitly set by users.

  13. In the Assign Servers to Clusters page, ensure that the servers are assigned to SOA_Cluster as shown:
    • JCS_SOA1
    • JCS_SOA2

    Click Next.

  14. In the Configure Machines page, delete LocalMachine that appears by default and click the Unix Machine tab to verify that it's populated. You can rename the machines to SOA_machine_1 and SOA_machine2, if required. Do not modify any of the other fields.

    Click Next.

  15. In the Assign Servers to Machines page, ensure that the servers are assigned to the machines as follows:
    • SOA_machine_1
      • Administration Server
      • JCS_SOA1
    • SOA_machine_2
      • JCS_SOA2

    Click Next.

  16. In the Target Deployments to Clusters or Servers page:
    1. Select SOA_Cluster and target the following to it:
      • Under Application:
        • DMS Application
        • wsil-wls
        • wsm-pm
        • FileAdapter
        • DbAdapter
        • JmsAdapter
        • AqAdapter
        • FtpAdapter
        • SocketAdapter
        • MQSeriesAdapter
        • OracleAppsAdapter
        • OracleBamAdapter
        • usermessagingserver
        • usermessagingdriver-email
        • UMSAdapter
        • soa-infra
        • worklistapp
        • b2bui
        • DefaultToDoTaskFlow
        • composer
      • Target all Libraries except the following:
        • emai
        • emas
        • emcore
        • oracle.webcenter.*
    2. Select Administration Server and target the following to it:
      • Under Application:
        • FMW Welcome Page Application
        • DMS Application
        • wsil-wls
        • em
        • OraJaaSmon

          Note: The wsm-pm application is not targeted to the Administration Server.

      • Target all Libraries to the Administration Server.

        For information, see "Targeting Applications and Resources to Servers" in Enterprise Deployment Guide for Oracle SOA Suite.

      Click Next.

  17. In the Target Services to Clusters or Servers page:
    • Ensure that the following are targeted to SOA_Cluster:
      • All shutdown classes
      • All startup classes
      • All JMS system resources except JRFWSAsyncJmsModule
      • All JDBC system resources
      • WLDF system resource
      • Work Manager
    • Ensure that the following are targeted to the Administration Server:
      • All shutdown classes
      • All startup classes except SOAStartupClass
      • mds-owsm, OPSS, and mds-soa JDBC system resources
      • WLDF system resource

    Click Next.

  18. In the Configure JMS File Stores page, click Next.
  19. In the Configuration Summary page, click Extend.

    Note: If you encounter any warning, click OK to dismiss the warning dialog box about the domain configuration ports that are conflicting with the host ports. This warning appears because of the existing Oracle Web Services Manager - Policy Manager (WSM-PM) installation.

  20. In the Extending Domain page, click Done.
  21. As the oracle user, start the Administration Server in VM1 by running the following command:
    /u01/data/domains/your_domain/startWebLogic.sh

    You can now access the WebLogic Server Administration Server Console by using the following link:

    http://administration_server_host:administration_server_port/console

Performing Postconfiguration Tasks

Configuring Oracle Coherence

Use the WebLogic Server Administration Console to specify a host name used by Oracle Coherence.

To configure Oracle Coherence:

  1. Sign in to the Oracle WebLogic Server Administration Console.
  2. From the Environment menu in the left pane, select Machines.
  3. In the Summary of Machines page, click the required machine.
  4. On the Settings page, click the Node Manager tab and make a note of the Listen Address. The listen address of each node is of the format instance_name-wls-1 and instance_name-wls-2.
  5. Click Lock & Edit start an edit session.
  6. From the Environment menu in the left pane, select Servers. The Summary of Servers page appears.
  7. In the Name column of the table, click the name of the server (JCS_SOA1 or JCS_SOA2, which are represented as links). The settings page for the selected server appears.
  8. Click the Server Start tab.
  9. Enter the following for JCS_SOA1 and JCS_SOA2 in the Arguments field without pressing the Enter key:
    • For JCS_SOA1:

      -Dtangosol.coherence.wka1=VM1
      -Dtangosol.coherence.wka2=VM2
      -Dtangosol.coherence.localhost=VM1
      -Dtangosol.coherence.localport=8089
      -Dtangosol.coherence.wka1.port=8089
      -Dtangosol.coherence.wka2.port=8089
    • For JCS_SOA2:

      -Dtangosol.coherence.wka1=VM1
      -Dtangosol.coherence.wka2=VM2
      -Dtangosol.coherence.localhost=VM2
      -Dtangosol.coherence.localport=8089
      -Dtangosol.coherence.wka1.port=8089
      -Dtangosol.coherence.wka2.port=8089

    In these examples, replace VM1 and VM2 with the actual listen address of each node as shown in Step 4.

    Note: There shouldn't be breaks in the lines between the different -D parameters. Don't copy and paste the text into your WebLogic Server Administration Console Arguments text field. Doing that could cause HTML tags to be inserted into the Java arguments. The text can't contain characters other than those include in the previous example.


    Note: The Oracle Coherence cluster used for deployment uses port 8088 by default. This port can be changed by specifying a different port (for example, 8089) with the -Dtangosol.coherence.wkan.port and -Dtangosol.coherence.localport startup parameters.


    To save the Arguments field values of each Managed Server, click Save.

  10. Click Activate Changes.
  11. Ensure that these variables are passed to the Managed Server correctly by reviewing the server's output log.

    If the Oracle Coherence framework fails, then the result caching might stop working.

    See Configuring Oracle Coherence for Deploying Composites in Oracle Fusion Middleware Enterprise Deployment Guide for Oracle SOA Suite.

Configuring Java Object Cache

Next, to improve the performance of OWSM, you can optionally configure Java Object Cache (JOC) by using the configure-joc.py script on VM1:

  1. Run the wlst.sh (Weblogic Scripting Tool) script:
    cd $MIDDLEWARE_HOME/soa/common/bin
    
    ./wlst.sh

    In the preceding command, $MIDDLEWARE_HOME is the path to your Oracle Weblogic Server install, which is typically u01/app/oracle/middleware.

  2. At the wls prompt, run the following command:
    connect()
  3. Provide the following details when you are prompted:
    • Your Oracle WebLogic Admin credentials
    • Your Admin server URL in the specified format: t3://IP_Address_of_VM1:7001
  4. Run the configure-joc.py script.
    execfile("/u01/app/oracle/middleware/oracle_common/bin/configure-joc.py")
  5. When prompted, enter the required information:
    Enter Hostnames (eg host1,host2) : listen_address_of_node_1,listen_address_of_node_2

    Note: This is the same listen address that you looked up in Step 4 of the section Configuring Coherence.

    Do you want to specify a cluster name (y/n) y
    
    Enter Cluster Name : SOA_CLUSTER
    
    Enter Discover Port : 9988
    
    Enter Distribute Mode (true|false)  : true
    
    Do you want to exclude any server(s) from JOC configuration (y/n) n
    

    The script runs and configures Java Object Cache for your Managed Servers JCS_SOA1 and JCS_SOA2.

  6. Run the following command to exit the Weblogic Scripting Tool:
    exit()

Configuring Oracle Adapters

Optionally, you can configure adapters. To configure Oracle Adapters, see Configuring Oracle Adapters in Oracle Fusion Middleware Enterprise Deployment Guide for Oracle SOA Suite.

Note: Adapters aren't supported with the High Availability feature because shared storage isn't available.

Creating a JDBC Store for Transaction Logs and JMS Servers

However, because the nodes in your Oracle Java Cloud Service cluster don't share the file system, convert the file stores to Java Database Connectivity (JDBC) stores. The JDBC stores are accessible from all nodes.

Checking the Data Source

The data source used by a JDBC store must not use global transactions. For SOA JDBC stores, use the SOALocalTxDataSource data source.

  1. Sign in to the WebLogic Server Administration Console.
  2. Go to Services and then click Data Sources.
  3. Click Lock & Edit to begin an edit session.
  4. Click SOALocalTxDataSource.
  5. From the Transactions tab, deselect Supports Global Transactions, if it is currently selected.
  6. Click Save and then Activate Changes.

Perform the same task for the OraSDPMDataSource data source.

Configuring JDBC Stores for Transaction Logs

  1. Sign in to the WebLogic Server Administration Console.
  2. Go to Environment and then click Servers.
  3. Complete the following tasks for all your Managed Servers:
    1. Click the Managed Server name. The Configuration tab opens.
    2. Select Services.
    3. Click Lock & Edit to begin an edit session.
    4. Under the Transaction Log Store section, from the Type drop-down list, select JDBC .
    5. From the Data Source drop-down list, select SOALocalTxDataSource. The prefix name will be automatically set to a correct value.

      Note that the prefix name can't be more than 20 characters and must be unique.

    6. Click Save and then click Activate Changes. Ensure that you repeat Step a through f for all of your Managed Servers.

Configuring the JDBC Stores for JMS Servers

  1. Sign in to the WebLogic Server Administration Console.
  2. Click Lock & Edit to begin an edit session.
  3. From Services, go to Messaging, and then select JMS Servers.
  4. A table of JMS servers with their respective persistent stores appears. For each persistent store that has a target defined:
    1. Select Services and then select Persistent Stores.
      You will see the name of your file store listed here. Note the Target for this store; it should be a Managed Server.
    2. Click New and select Create JDBC Store.
    3. Give the new JDBC store a name that corresponds to the file store that is getting replaced. For example, if the file store is named FileStore_auto_1, then use JDBCStore_auto_1 for this new JDBC store.
    4. From the Target drop-down list, select the target that matches the target of the file store that is getting replaced.
    5. Select the SOALocalTxDataSource option. Set the value of Prefix Name to a value unique to this JDBC store. For example, if the JDBC store name is WseeJDBCStore_auto_1, you could use WseeJDBC_1 as the Prefix Name.

      Note that the prefix name can't be more than 20 characters and it must be unique.

    6. Click OK to finish creating the JDBC store.
    7. From Services, select Messaging, and then select JMS Servers.
    8. Find the JMS server that uses the file store that was replaced and select it.
    9. Use the Persistent Store drop-down list to select the JDBC store that you just created.
    10. Click Save.
  5. Repeat these steps for each persistent store listed in the following table, and specify the data source as SOALocalTxDataSource for each persistent store.
    FileStore JDBCStore Target Prefix
    BPMJMSFileStore_auto_1 BPMJMSJDBCStore_auto_1 JCS_SOA1 BPMJMSJDBC_1
    BPMJMSFileStore_auto_2 BPMJMSJDBCStore_auto_2 JCS_SOA2 BPMJMSJDBC_2
    PS6SOAJMSFileStore_auto_1 PS6SOAJMSJDBCStore_auto_1 JCS_SOA1 PS6SOAJMSJDBC_1
    PS6SOAJMSFileStore_auto_2 PS6SOAJMSJDBCStore_auto_2 JCS_SOA2 PS6SOAJMSJDBC_2
    SOAJMSFileStore_auto_1 SOAJMSJDBCStore_auto_1 JCS_SOA1 SOAJMSJDBC_1
    SOAJMSFileStore_auto_2 SOAJMSJDBCStore_auto_2 JCS_SOA2 SOAJMSJDBC_2
    UMSJMSFileStore_auto_1 UMSJMSJDBCStore_auto_1 JCS_SOA1 UMSJMSJDBC_1
    UMSJMSFileStore_auto_2 UMSJMSJDBCStore_auto_2 JCS_SOA2 UMSJMSJDBC_2
  6. Click Activate Changes.

Running the Pack and Unpack Commands for Provisioning in Multiple VMs

If you're provisioning Oracle SOA Suite on multiple VMs of Oracle Java Cloud Service, then you must run the pack and unpack commands. Perform the following tasks only if you are provisioning on more than one VM.

  1. Sign in to the WebLogic Server Administrator Console and shut down the Administration Server and both the Managed Servers if they are running.
  2. Log in to VM1 as the opc user and use the sudo command to become the oracle user. Run the following commands to pack the domain:
    cd /u01/app/oracle/middleware/oracle_common/common/bin
    
    ./pack.sh -managed=true -domain=/u01/data/domains/your_domain -template=your_domain_name.jar -template_name=your_domain_name
  3. Use the scp command to copy the template to VM2:
    scp your_domain_name.jar Private_IP_address_of_VM2:/u01/app/oracle/middleware/oracle_common/common/bin/
  4. As the oracle user on VM1, use the ssh command to log in to VM2:
    ssh –X Private_IP_address_of_VM2
  5. To unpack the domain on VM2, run the following commands:
    cd /u01/app/oracle/middleware/oracle_common/common/bin
    
    ./unpack.sh -domain=/u01/data/domains/your_domain_name -overwrite_domain=true -template=your_domain_name.jar
  6. Verify that your domain on VM2 is updated:
    cd /u01/data/domains/your_domain_name
    ls –lt

    This should list the updated files in your domain with the current timestamp.

Starting the Servers

To get your deployments up and running, you must start the Administration Server and Managed Servers that you created when you extended the domain:

  1. To start the Administration Server, use a VNC viewer to log in to VM1 as the oracle user and run the following command:
    /u01/data/domains/your_domain/startWebLogic.sh
  2. Sign in to the WebLogic Server Administration Console.
  3. From the Environment menu in the left pane, select Servers.
  4. In the Summary of Servers page, click the Control tab.
  5. Select the Managed Servers and click Start.

    Note: If required, you can set specific performance tuning configurations before starting the managed servers. See Performance Tuning Guidelines.

Verifying Deployment

When an Oracle Java Cloud Service Instance was created, two public IP addresses are provided, one each for VM1 and VM3. The public IP address of VM1 is used for running SSH and transferring files to VM2, and to access the Oracle WebLogic Server Administration Console and the Oracle Enterprise Manager Fusion Middleware Control Console. The public IP address of VM3 is used by the Oracle Traffic Director load balancer, cluster of Managed Servers for Oracle SOA Composer, Oracle B2B, Oracle Worklist Application, and so on, by entering the following URL:

https://Public_IP_address_of_VM3:443

Note: When you configure Oracle Traffic Director, the default value used by Oracle Java Cloud Service is 443.

To verify whether Oracle SOA Suite has been properly deployed:

  1. Sign in to the WebLogic Server Administration Console.
  2. In the left pane, click Deployments.
  3. On the Summary of Deployments page, check all the Oracle SOA Suite components and ensure that there is a checkmark in the Health column.
  4. Find out the IP address and port of your load balancer, if you did not do so earlier:
    1. Sign in to the My Services application and go to the My Services Dashboard.
    2. In the Oracle Java Cloud Service section, click Open Service Console. The Oracle Java Cloud Service Console appears.
    3. Click your Oracle Java Cloud Service instance to view details of the nodes. Make a note of the content endpoint of the load balancer VM. The content endpoint is of the format Public_IP_address_of_VM3:port. By default, the port used by the load balancer for HTTPS is 443.
  5. On your local machine or on VM1, verify that you can access the following URLs:
    https://Public_IP_address_of_VM3:443/soa-infra
    https://Public_IP_address_of_VM3:443/integration/worklistapp
    https://Public_IP_address_of_VM3:443/soa/composer
    https://Public_IP_address_of_VM3:443/b2bconsole

    Note: Use your WebLogic Server Administrator user name and password to sign in.

    In case of errors, see the following log files for details:

    
    $DOMAIN_HOME/servers/your_adminserver/logs/your_adminserver-diagnostic.log
    $DOMAIN_HOME/servers/your_adminserver/logs/your_adminserver.log
    $DOMAIN_HOME/servers/your_managed_server_1/logs/your_managed_server_1-diagnostic.log
    $DOMAIN_HOME/servers/your_managed_server_1/logs/your_managed_server_1.log
    $DOMAIN_HOME/servers/your_managed_server_1/logs/your_managed_server_1.out*

    Note: You can continue to use HTTPS port 8081 to access an application running on an existing instance that was created by using the Create New Oracle Java Cloud Service Instance wizard.

Designing and Deploying SOA Composite Applications with Oracle JDeveloper

  1. To design SOA composite applications, install Oracle JDeveloper on your local host. See Fusion Middleware Installation Guide for Oracle JDeveloper.
  2. After you have installed Oracle JDeveloper, ensure that the Oracle SOA Suite extensions are installed:
    1. From the Help menu select About and then select Extensions.
    2. Look for an identifier with the prefix oracle.sca.
  3. If you see this identifier in the list, then go to the next step. If this identifier isn't listed, then download and install the soa-jdev-extension.zip file from here.

    Look for the section Details for Oracle SOA Composite Editor. In the table, look for the version 11.1.1.7.0.0.97, then click Download.

  4. Configure an application server connection from JDeveloper to the Oracle Java Cloud Service domain. See Creating an Application Server Connection in Developer's Guide for Oracle SOA Suite.
  5. Build a simple application using Oracle SOA Suite Suite.
  6. After you finish designing your composite application, deploy the project to a SOA archive (SAR) file. Use scp to copy the SAR file to VM1 and then deploy the SAR file from Oracle Enterprise Manager 11g Fusion Middleware Control or the Oracle WebLogic Scripting Tool (WLST) command-line interface.

    See Deployment Commands in WebLogic Scripting Tool Command Reference.

    See Deploying and Managing SOA Composite Applications in Administrator's Guide for Oracle SOA Suite and Oracle Business Management Suite.

Troubleshooting

Task Details Aren't Displayed Due to Untrusted Certificate

Problem Statement: When you go to task details in the integration or Worklistapp URL, you might see that the tasks are listed but task details aren't shown.

Workaround:

  1. Sign in to the Oracle Enterprise Manager Fusion Middleware Control Console.
  2. Go to the Composite home, and from the Administration tab, click the name of the task component.
  3. Specify the Oracle Traffic Director host and port, instead of the Managed Server and port.
  4. Click Save.
  5. Create the new instances and verify that the task details are displayed.

Error Message Displayed While Starting VNC Viewer

Problem Statement: When you start the VNC viewer, the following error message may be displayed:

There is a problem with the configuration server. (/usr/libexec/gconf-sanity-check-2 exited with status 256)

Workaround:

Create a VNC server by using the oracle user instead of the opc user.

Managed Server Fails to Start: Prefix Name Error

Problem Statement: If you don't change the default prefix name when you configure JMS and transaction logs, then the Managed Server will fail when you start it.

Workaround:

Log in to the WebLogic Server Administration Console. For every Managed Server, go to the Services tab and update the prefix name with a unique value. The value must be fewer than 20 characters.

Performance Tuning Guidelines

All other tuning should be similar to the tuning guidelines mentioned in Oracle Fusion Middleware Performance and Tuning Guide.

Want to Learn More?