Provisioning Oracle SOA Suite on Oracle Java Cloud Service

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.

   

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

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.

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

   

   The Oracle Database Cloud Service Console appears.

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

   

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

   

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

   

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

   

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

   

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

   

   The Oracle Database Cloud Service instance is created.

   

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.

   

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.

   

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

   

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.
    
11. Click Next.
12. On the Confirmation page, review the information and then click Create to create your Oracle Java Cloud Service instance.

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.

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 

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.

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.

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

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

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).

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.

   

9. Click Next.
10. On the Checking Global Prerequisites page, click OK.
11. On the Select Components page:
    • Select Select an existing Prefix and then select the appropriate schema prefix from the drop-down list. The schema prefix that you select should be the one used by the MDS schema, as identified in the section Finding Out Your Schema Prefix, Oracle Database Cloud Service Host Name, Port, and Service Name.
    • From the listed components, under SOA and BPM Infrastructure, select SOA Infrastructure and User Messaging Service.

      

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.

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.

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.

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

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.

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()

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.

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

Configuring JDBC Stores for Transaction Logs

Configuring the JDBC Stores for JMS Servers

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.

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.

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.