Provisioning Oracle BPM Suite on Oracle Java Cloud Service


Options



Before You Begin

Purpose

This tutorial describes the process for extending an Oracle WebLogic Server domain on an Oracle Java Cloud Service instance with Oracle Business Process Management Suite (Oracle BPM Suite).

Time to Complete

8 hours

Background

Oracle BPM Suite provides a complete set of tools that you can use to create, execute, and optimize business processes. Oracle Java Cloud Service enables you to use an Oracle WebLogic Server domain and set up your Oracle BPM Suite environment without worrying about the infrastructure or platform components. All Oracle Java Cloud Service instances are preconfigured to use your database deployment in Oracle Database Cloud Service 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.

What Do You Need?

To create a storage container, an Oracle Database Cloud Service database deployment 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 (as described in Setting Up Your Environment).

  • Local host: Oracle Linux 6.4
  • 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'll see three 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:

    • VM1: 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 BPM Suite version: 11.1.1.7.0. You select the Oracle SOA Suite and Oracle BPM Suite version when you run the configuration wizard to extend your Oracle Java Cloud Service domain.

Process Overview

The following are the high-level steps required to install, configure, and verify the Oracle BPM Suite on an Oracle Java Cloud Service instance:

  1. Set up your environment.
  2. Perform preinstallation tasks on your Oracle Java Cloud Service instance.
  3. Download and copy the installation files to your Oracle Java Cloud Service instance.
  4. Run the Oracle Fusion MiddleWare Repository Creation Utility.
  5. Install Oracle BPM Suite.
  6. Perform configuration tasks.
  7. Verify Oracle BPM Suite installation.

Setting Up Your Environment

To set up your Oracle Java Cloud Service and Oracle Database Cloud Service instances:

  • Create an Object Storage Container
  • Generate an SSH Key Pair
  • Create an Oracle Database Cloud Service Instance
  • Create an Oracle Java Cloud Service Instance

Creating an Object Storage Container

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 got your Oracle Cloud account, you received an email telling you how to sign in to My Services. Follow the link and use the credentials provided 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. Find out your REST endpoint.

    Go to the Oracle Storage Cloud Service section of the dashboard, click Menu 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.

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

    From the output of this command, make a note of the X-Auth-Token value.

  3. Create a container.
    curl -v -H 'X-Auth-Token: your_auth_token ' -X PUT https://storage.data-region-code.oraclecloud.com/v1/Storage-IdentityDomain/container_name
  4. 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/

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 and go to the My Services Dashboard.
  2. In the Oracle Database Cloud Service section, click Open Service Console. The Oracle Database Cloud Service Console appears.
  3. Click Create Instance. The Create Database Cloud Service Wizard starts and the Subscription Type page appears.
  4. Select Oracle Database Cloud Service and a billing frequency. Click Next.

    Create Database Cloud Service Instance - Subscription screen

  5. On the Release page, select Oracle Database 11g Release 2. Click Next.

    Create Database Cloud Service Instance - Release screen

  6. On the Software Edition page, select Enterprise Edition. Click Next. The Service Details page appears.

    Create Database Cloud Service Instance - Edition screen

  7. In the Instance Configuration section, enter the following:
    • Instance name
    • Description
    • Compute shape: This allows you to specify the number of OCPUs and RAM that 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 and go to the folder where you saved the SSH public key.
      3. Select the SSH public key and then click Enter.
  8. In the Database Configuration section, enter following:
    • Usable Database Storage
    • Administrator Password: The administrator password that you provide is used for the SYS and SYSTEM database users, and for the Oracle GlassFish Server and Oracle Application Express administrator users.
    • DB Name: Make a note of the SID. You'll need it later.
  9. In the Backup and Recovery Configuration section, enter the following:
    • Backup Destination: Select Both Cloud Storage and Block Storage.
    • Cloud Storage Container: The container name should be of the format storageservicename-id_domain/container, where storage service name is the name of the Oracle Storage Cloud Service (Storage), id_domain is the name of your identity domain, and container is the name of your container.
    • Cloud Storage User Name
    • Cloud Storage Password

    Create Database Cloud Service Instance - Details screen

  10. Click Next.
  11. On the Confirmation page, review the information and then click Create to create the database instance.

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 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 a billing frequency. 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.

    Create Java Cloud Service Instance - Edition screen

  7. On the Instance Details page, in the Instance Configuration section, enter the following:
    • 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 and go 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.
  9. In the Database Configuration section, enter the following:
    • 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, and then click Next:
    • Provision Load Balancer: Select Yes.
    • Load Balancer Policy: Select the appropriate policy.
    • Compute Shape: Select OC3 – 1 OCPU, 7.5 GB RAM.

    Create Java Cloud Service Instance - Details screen

  11. On the Confirmation page, review the information and then click Create to create your Oracle Java Cloud Service instance.

Performing Preinstallation Tasks on Your Oracle Java Cloud Service Instance

After your Oracle Java Cloud Service instance is created, it's listed on your Oracle Java Cloud Service Console. You can use your SSH key to log in to the virtual machine, VM1, which hosts the Administration Server. You can log in to VM1 as the default opc user. To log in to VM1:

  1. On the Oracle Java Cloud Service Console, click the instance name to view details of your instance.
  2. Make a note of the IP addresses of VM1 displayed on the instance details page. The public IP address will be used throughout this tutorial to access VM1 from your local machine. The private IP address is used to access VM1 from VM2.

    Note: Make a note of the IP address and content endpoint of the load balancer as well. You'll need it when you verify the deployment later.

  3. On your local system, run the following command to log in to VM1:
    ssh –i path_to_SSH_private_key opc@IP_address_of_VM1

    Note: In this tutorial, italics are used in commands to indicate placeholders for variables. Substitute the italicized text with your actual values. For example, in this command, substitute path_to_SSH_private_key with the actual path to your SSH key, and substitute IP_address_of_VM1 with the actual public IP address of VM1.

Next, complete the following preinstallation tasks:

  • Verify that the TMP directory exists and is writable
  • Forward the X Window system
  • Start a VNC session

Verifying that the TMP Directory Exists and Is Writable

Run the following commands on VM1:

  1. Open the .bashrc file in a text editor.
    vi ~opc/.bashrc
  2. Search for lines beginning with:
    export TMPDIR=
  3. Change each line to:
    export TMPDIR=/tmp
  4. Save the file and exit the editor.
  5. Source the updated configuration file:
    source ~opc/.bashrc
  6. Check the permission of the /tmp directory:
    cd /
    ls –l 
  7. If the permission isn't currently 777, then change the permission of the /tmp directory:
    sudo chmod 777 /tmp 

Forwarding the X Window System

The installation and configuration tools that you use to install and configure Oracle BPM Suite require the X Window system. The X Window system is already installed on your Oracle Java Cloud Service Administration Server VM. You must forward the X Window system to be able to view and use an xterm or the configuration wizard on your display.

To forward the X Window system, run the following commands on VM1:

  1. Open the sshd_config file:
    sudo vi /etc/ssh/sshd_config
  2. Search for the following line:
    X11Forwarding no
  3. This line may occur more than once in this file. Change all occurrences to:
    X11Forwarding yes
  4. Save the file and exit the editor.
  5. Restart sshd.
    sudo /etc/init.d/sshd restart
  6. Optionally, to prevent the Window Manager from locking the page, run the following command:
    gconftool-2 -s -t bool /apps/gnome-pagesaver/lock_enabled false

Starting a VNC Session

  1. Start a VNC server on VM1:
    vncserver :1 -depth 16 -alwaysshared -geometry 1200x750 -s off

    You'll be prompted to provide a password for the VNC server.

    Note: Make a note of this password. You must provide this password when you access VM1 through VNC.

  2. To create an SSH tunnel, run the following command on your local machine:
    ssh -4 -L 6905:127.0.0.1:5901 -N -f -i path_to_SSH_private_key -l opc IP_address_of_VM1

    In this command, 5901 is the listen port of the VNC server, as defined in /usr/bin/vncserver:

    $vncPort = 5900 + $displayNumber;

    Note: Because $displayNumber is set to 1 in the previous step, the listen port for this VNC session :1 is 5901.

    Note: 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 view the status of ports on your local host. If the specified port is already being used, then use any available port.

  3. On your local machine, if you haven't already done so, set the DISPLAY environment variable:
    export DISPLAY=IP_address_of_local_machine:1
  4. On your local machine, use vncviewer to access VM1 via the SSH tunnel:
    vncviewer 127.0.0.1:6905

    This logs you in as the opc user.

Downloading the Installation Files and Copying Them to Your Oracle Java Cloud Service Nodes

Downloading the Installation Files

  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 option 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. Ensure that the /u01 and /u01/zips directories on VM1 have write permission. If you logged out of VM1, log in as the opc user and run the following commands:

    sudo chmod 777 /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/bpm
    
    sudo chmod 777 /u01/zips/bpm
  4. Use scp on your local machine to copy the Oracle SOA Suite zip files to the /u01/zips/bpm directory on VM1.
    scp –i path_to_SSH_private_key path_to_downloaded_files/*soa*.zip opc@IP_address_of_VM1:/u01/zips/bpm
  5. Set the following permissions for the oracle user:
    cd /u01/zips/bpm
    
    sudo chown oracle:oracle *.zip
    
    sudo chmod 755 *.zip
  6. Confirm that the Oracle SOA Suite zip files have been copied:
    ls –lt

    This should list the Oracle SOA Suite zip files.

Copying the Installation Files to the Second Oracle Java Cloud Service Node

As the oracle user on VM1, use scp to copy the Oracle SOA Suite zip files to VM2.

  1. Sign in to the My Services application and go to the My Services Dashboard.

    Note: Bookmark your My Services application so that you can easily access the service consoles later.

  2. Click the Open Service Console link in the Oracle Compute Cloud Service section. The Oracle Compute Cloud Service Instances page appears.

    My Services dashboard

  3. Click domain_name wls 2. This is the second node of your two-node cluster.

    Oracle Compute Cloud Service console

  4. On the instance details page, make a note of the host name or private IP address of this instance.
  5. Use SSH to log in to VM1 as the opc user.
  6. Use scp to copy your private key from your local machine to VM1. You'll 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
  7. On VM1, restrict permissions on the private key file.
    sudo chmod 600 /home/opc/private_key_name

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

  8. Use SSH on VM1 to log in to VM2 as the opc user.
    ssh –i path_to_SSH_private_key opc@Private_IP_address_of_VM2
  9. Create the /u01/zips/bpm directory and ensure that the directories on VM2 have write permission.
    sudo chmod 777 /u01
    
    sudo chmod 777 /u01/zips
    
    mkdir /u01/zips/bpm
    
    sudo chmod 777 /u01/zips/bpm
    
  10. On VM1, use scp to quickly copy the SOA zip files to VM2.
    scp –i path_to_SSH_private_key /u01/zips/bpm/*soa*.zip opc@Private_IP_address_of_VM2:/u01/zips/bpm
  11. On VM2, set permissions for the oracle user.
    cd /u01/zips/bpm
    
    sudo chown oracle:oracle *.zip
    
    sudo chmod 755 *.zip
  12. On VM2, confirm that all the Oracle SOA Suite zip files have been copied.
    ls –lt

Running the Oracle Fusion MiddleWare Repository Creation Utility

Oracle WebLogic Server and Oracle Fusion Middleware Repository Creation Utility (RCU) are already installed on the Oracle Java Cloud Service instance that you created. The Oracle Metadata Services (MDS) and Oracle Platform Security Services (OPSS) schemas are already created. To create the Oracle BPM Suite schemas, SOAINFRA and ORASDPM:

  • Find out your schema prefix
  • Find out your Oracle Database Cloud Service host name, port, and service name
  • Start the RCU
  • Create the schemas

Finding Out Your Schema Prefix

When you run the RCU to create the Oracle BPM 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:

  1. Sign in to the My Services application that you had bookmarked earlier 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.

    Oracle Java Cloud Service console

  3. Click Menu Menu icon and select Open Fusion Middleware Control Console.
  4. Sign in to Oracle Enterprise Manager 11g Fusion Middleware Control using the Oracle WebLogic Server Administrator credentials that you provided while creating the Oracle Java Cloud Service instance.
  5. On the Home page, in the navigation panel on the left, expand Metadata Repositories and select mds-owsm.

    Enterprise Manager Home page

  6. On the mds-owsm page, from the Metadata Repository drop-down list at the top of the page, select General Information.

    Enterprise Manager mds-owsm screen

  7. Make a note of the Schema. The schema prefix is the string that appears before _MDS.

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

  1. Sign in to the My Services application and go to the My Services Dashboard.
  2. In the Oracle Database Cloud Service section, click Open Service Console. The Oracle Database Cloud Service Console appears.

    Oracle Database Cloud Service console

  3. Click your Oracle Database Cloud Service instance to view its details.
  4. On the instance details page, make a note of the following:
    • Host name: This is the name that you specified while creating your Oracle Database Cloud Service instance.
    • SQL *Net Port: This is usually 1521.
    • SID: This is the SID that you specified while creating your Oracle Database Cloud Service instance.
    • Identity Domain: This is the identity domain for your account, provided to you when your account was set up.
    • Connect Descriptor: This is of the format dbhost:port/SID.IdentityDomain.

Starting the RCU

  1. If you logged out of VM1, use SSH 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. Start the RCU to create the Oracle BPM Suite schemas that you require.
    /u01/app/oracle/middleware/rcuHome/bin/rcu

Creating the Schemas

When the RCU wizard starts, complete the following steps:

  1. On the Welcome page, click Next.
  2. On the Create Repository page, select Create Repository and then click Next.
  3. On the Database Connection Details page, enter the following, and then click Next:
    • Host Name: The name of your Oracle Database Cloud Service instance
    • Port: Usually 1521
    • Service Name: The SID followed by your fully qualified identity domain name, separated by a dot (.)
    • Username: The default user SYS
    • Password: The Administrator password that you specified for the Oracle Database Cloud Service instance while creating the Oracle Java Cloud Service instance

    Database Connection Details screen

  4. On the Checking Global Prerequisites page, click OK.
  5. On the Select Components page, select the following, and then click Next:
    1. Select Select an existing Prefix and then from the drop-down list, select the appropriate schema prefix. The schema prefix that you select should be the one used by the MDS schema, as identified in Step 7 of Finding Out Your Schema Prefix.
    2. From the listed components, under SOA and BPM Infrastructure, select SOA Infrastructure and User Messaging Service.

      RCU wizard Step 3 of 7

  6. On the Checking Component Prerequisites page, click OK.
  7. On the Schema Passwords page, select Use same passwords for all schemas. Enter your password in the Password and Confirm Password fields, and then click Next.

    Note: Make a note of this password. You'll need it later.

  8. On the Map Tablespaces page, you don't need to make any changes. Click Next. A confirmation message appears.
  9. Click OK.
  10. On the Validating and Creating Tablespaces page, when the validation is complete, click OK.
  11. On the Summary page, review the information and then click Create.

Installing Oracle BPM Suite

Oracle BPM Suite is installed as a component of Oracle SOA Suite. To install Oracle BPM Suite, ensure that you are logged in to VM1 as the oracle user. Complete the following steps:

Note: You must perform the following steps on VM2 as well.

  1. Unzip the installation files.
    cd /u01/zips/bpm
    
    unzip ofm_soa\*.zip
    

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

  2. Create the bpm.rsp file with the following content:
    [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 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/bpm
    
    #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]
    
  3. Create the jcs.invptr file with the following content:
    inventory_loc=/u01/app/oraInventory
    
    inst_group=pref
  4. Ensure that both the bpm.rsp file and the jcs.invptr file have permissions set to 775. If not, then to set the permissions, run the following commands as the opc user on VM1:
    sudo chmod 775 /u01/zips/bpm/bpm.rsp
    
    sudo chmod 775 /u01/zips/bpm/jcs.invptr
    
    sudo su - oracle
    
  5. Go to the Disk1 directory.
    cd /u01/zips/bpm/Disk1
  6. Run the installer.
    ./runInstaller –silent -ignoreDiskWarning -noValidation 
    -ignoreSysPrereqs -waitforcompletion -jreLoc /u01/jdk 
    -response full_path_to_bpm.rsp -invPtrLoc full_path_to_jcs.invptr
    

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

  7. From VM1, use SSH to connect to VM2 and repeat the steps to install Oracle SOA Suite on that node.

Configuring Your Data Source and DB Policy Store

  • Create an OPSS data source
  • Associate a policy store with an OPSS data source

Creating an OPSS Data Source

  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 Menu Menu icon and select Open WebLogic Server Console.
  4. Sign in to the Oracle WebLogic Server Administration Console using the Oracle WebLogic Server Administrator credentials that you provided while creating your Oracle Java Cloud Service instance.
  5. Expand the Services menu in the left pane and select Data Sources.

    Oracle WebLogic Admin console

  6. In the Summary of JDBC Data Sources page, verify that the opss-ds data source is displayed. If it is, then skip the remaining steps in this section and proceed to the section Associating a Policy Store with an OPSS Data Source. If the opss-ds data source isn't displayed in the list of data sources, then you must create it. Start a new edit session by clicking Lock & Edit.
  7. From the New drop-down list, select Generic Data Source.

    Summary of JDBC Data Sources screen

  8. Enter the following, and then click Next:
    • Name: OPSSDS
    • JNDI Name: jdbc/OPSSDS
    • Database Type: Oracle

    Create new JDBC Data Source screen

  9. In the Database Driver field, select Oracle's Driver (Thin) for Instance connections. Click Next.
  10. Deselect Supports Global Transactions. Click Next.
  11. Enter the following:
    • Database Name: your_database_SID
    • Host Name: your_database_instance_host_name
    • Port: your_database_port
    • Database User Name: SchemaPrefix_opss. Use the same schema prefix that you used for creating schemas while running the RCU earlier.
    • Password: your_WLS_Admin_password

    Note: You must specify the Oracle WebLogic Server Administrator password as the RCU password. This enables the new schemas that you create to connect to the schemas that were created by default when you created your Oracle Java Cloud Service instance.

    Create new JDBC Data Source screen

  12. Click Next.
  13. Verify that the URL syntax is correct. Some versions of Oracle SOA Suite separate the port and service with a colon (:) instead of a slash (/). If you see a colon (:) after the port, change it to a slash (/). Click Test Configuration to verify the connection. Click Next.
  14. Select the Administration Server and the cluster.
  15. Click Finish.
  16. Click Activate Changes.

Associating a Policy Store with an OPSS Data Source

  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 Menu Menu icon and select Open Fusion Middleware Control Console.
  4. Sign in to Oracle Enterprise Manager 11g Fusion Middleware Control using the Oracle WebLogic Server Administrator credentials that you provided while creating the Oracle Java Cloud Service instance.
  5. In the navigation pane on the left, expand Weblogic Domain and click your domain name. Your domain name consists of the first eight characters of your Oracle Java Cloud Service instance name, followed by _domain.

    Enterprise Manager WebLogic domain

  6. From the WebLogic Domain drop-down list under the domain name at the top of the page, select Security and then select Security Provider Configuration. The Configure Security Stores page appears.

    Security Provider Configuration in Enterprise Manager

  7. If the policy store association has already been created, then skip the remaining steps in this section and go to Extending the Oracle Java Cloud Service Domain. If the policy store doesn't show in the list, then create it now:
    • Store Type: Click Change Store Type and from the Store Type drop-down list, select Oracle Database.
    • Data Source JNDI Name: Enter the data source JNDI name for the OPSS data source that you created (jdbc/OPSSDS), or click Select and select it from the list.
    • User Name: Enter the user name that you provided while creating the OPSS data source. The user name is of the format SchemaPrefix_opss.
    • Password: Enter your RCU password, which is the same as your Oracle WebLogic Server Administrator password.
    • Root DN: Enter cn=jpsNode

      Note: You can enter any name in this field. This name is used for the node created in the database for the policy store.

    • Select Create New Domain.
    • Domain Name – Enter your domain name or accept the default.

    Configure Security Stores screen

  8. Click OK. A confirmation page appears.
  9. Click Yes. Security store configuration begins.
  10. When security store configuration completes, click Close.

    Configure Security Stores Completed Successfully

Extending the Oracle Java Cloud Service Domain

To extend the Oracle Java Cloud Service domain to include Oracle BPM Suite:

  • Prepare to extend the Oracle Java Cloud Service domain
  • Run the Fusion Middleware Configuration Wizard

Preparing to Extend the Oracle Java Cloud Service Domain

  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. Log in to VM1 and use sudo to become the oracle user.
  7. Back up your existing domain.
    cp –r /u01/data/domains /u01/data/domains.orig
  8. As the oracle user, start the Fusion MiddleWare Configuration Wizard to extend the domain.
    /u01/app/oracle/middleware/oracle_common/common/bin/config.sh

    If the soainfra or orasdpm schemas are locked, the command to run the configuration wizard will return an error. If this happens, then run the following commands to unlock the schemas:

    
    export ORACLE_HOME=/u01/app/oracle/middleware/rcuHome
    
    export LD_LIBRARY_PATH=${ORACLE_HOME}/lib
    
    export PATH=${PATH}:${ORACLE_HOME}/bin
    
    sqlplus sys/password@//database_connect_string as sysdba
    

    Note: Provide the password that you specified for the Database Administrator while creating the Oracle Java Cloud Service instance. The database_connect_string here should be of the format dbhost:dbport/SID.fully_qualified_identity_domain

    Note: If you're unable to connect to the database with the sys user name, use system instead.

    At the SQL prompt, run the following commands:

    Note: Provide the RCU password, which is the same as your Oracle WebLogic Server Administrator password, for these commands.

    
    ALTER USER SchemaPrefix_SOAINFRA IDENTIFIED BY password ACCOUNT UNLOCK;
    
    ALTER USER SchemaPrefix_ORASDPM IDENTIFIED BY password ACCOUNT UNLOCK;
    
    exit
    

    Now you should be able to start the Configuration Wizard to extend the domain.

    /u01/app/oracle/middleware/oracle_common/common/bin/config.sh

Running the Fusion Middleware Configuration Wizard

  1. In the Fusion Middleware Configuration Wizard Welcome page, select Extend an existing WebLogic domain, and then click Next.
  2. On the WebLogic Domain Directory page, select the following WebLogic Server domain directory, and then click Next:
    /u01/data/domains/your_domain_name
  3. On the Select Extension Source page:
    1. Select Extend my domain automatically to support the following added products.
    2. Select Oracle BPM Suite - 11.1.1.0. The prerequisite component Oracle SOA Suite 11.1.1.0 is selected automatically.
    3. Click Next.
  4. If you get a Conflict Detected message that Oracle JRF (Java Required Files) is already defined in the domain, select Keep Existing Component 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: SID.fully_qualified_identity_domain

      Note: Verify this against the details that you noted from the Oracle Database Cloud Service Console instance details page earlier. Note the dot (.) between the SID and the identity domain.

    • Host Name: dbhost or IP_address_of_your_database_instance.

      Configure JDBC Data Sources screen

  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 14 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

      Configure JDBC Component Schema scree

  8. In the Test JDBC Component Schema page, confirm that all connections are successful.

    The connections are tested automatically. If any connection fails, then click Previous to return to the previous page and correct your entries. If all connections are successful, then click Next.

  9. In the Select Optional Configuration page, select the following, and then click Next:
    • JMS Distributed Destination
    • Managed Servers, Clusters, and Machines
    • Deployments and Services
    • JMS File Store
  10. In the Select JMS Distributed Destination Type page, ensure that all JMS system resources are configured to uniform distributed destination (UDD). This should be configured by default. Click Next.
  11. In the Configure Managed Servers page, verify the settings for the Managed Servers.

    Note: A server called soa_server1 is created automatically. Delete this server by selecting it and clicking Delete.

    For the other two Managed Servers, enter the attributes listed in the following table, and then click Next:

    Name Listen Address Listen Port SSL Listen Port SSL Enabled
    BPM_WLS1 All Local Addresses 8001 N/A No
    BPM_WLS2 All Local Addresses 8001 N/A No

    Configure Managed Servers screen

  12. In the Configure Clusters page, you can rename the cluster to BPM_CLUSTER, if required. Don't change any of the other fields. Click Next.
  13. In the Assign Servers to Clusters page, verify that both Managed Servers, BPM_WLS1 and BPM_WLS2, are assigned to BPM_CLUSTER, and then click Next.

    Assign Servers to Clusters screen

  14. In the Configure Machines page, delete the LocalMachine that appears by default. In the Unix Machine tab, you can rename the machines to BPM_Machine1 and BPM_Machine2, if required. Don't change any of the other fields. Click Next.
  15. In the Assign Servers to Machines page, ensure that servers are assigned to machines as follows, and then click Next:
    • BPM_Machine1
      • AdminServer
      • BPM_WLS1
    • BPM_Machine2
      • BPM_WLS2

    Assign Servers to Machines screen

  16. In the Target Deployments to Clusters or Servers page, target deployments as follows, and then click Next:
    • Target oracle.soa.*, oracle.rules.*, oracle.sdpm.*, and oracle.bpm.* lib to BPM_CLUSTER.
    • Retain deployments that are by default targeted to BPM_CLUSTER.
    • Ensure that the oracle.rules library is targeted to both the Administration Server as well as to BPM_CLUSTER.

    For the complete list of deployments that must be targeted to BPM_CLUSTER, see Targeting Deployments to Clusters or Servers.

  17. In the Target Services to Clusters or Servers page target services as follows, and then click Next:
    • Ensure that all services are targeted to BPM_CLUSTER.
    • Ensure that mds-owsm and mds-soa are targeted to both the Administration Server and to BPM_CLUSTER.

    For the complete list of services that must be targeted to BPM_CLUSTER, see Targeting Services to Clusters or Servers.

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

    Note: You may see a warning about the domain configuration ports conflicting with the host ports. This warning appears because of the existing installation. Click OK to dismiss this warning.

  20. In the Extending Domain page, click Done.
  21. To start the Administration Server, log in to VM1 as the oracle user and run the following command:
    /u01/data/domains/your_domain/startWebLogic.sh

Configuring the Oracle BPM Suite Cluster

To configure the Oracle BPM Suite cluster:

  • Configure Oracle Coherence
  • Configure Java Object Cache
  • Create Java Database Connectivity (JDBC) stores for transaction logs and Java Message Service (JMS) servers

Note: Before starting the configuration steps, log in to VM1 and use sudo to become the oracle user. Run the following command:

export WLS_REDIRECT_LOG=/u01/data/domains/your_domain/servers/your_adminserver/logs/AdminServer.log

Configuring 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 to start an edit session.
  6. From the Environment menu in the left pane, select Servers.
  7. In the Summary of Servers page, click the Managed Server BPM_WLS1.
  8. In the Settings for BPM_WLS1 page, click the Server Start tab.
  9. In the Arguments field, enter the following:

    Note: There shouldn't be any line breaks in the following text. Enter the text in a single line; it will wrap automatically. Don't copy and paste text in this field, because it might introduce stray characters.

    -Dtangosol.coherence.wka1=listen_address_of_node_1
    -Dtangosol.coherence.wka2=listen_address_of_node_2
    -Dtangosol.coherence.localhost=listen_address_of_node_1
    -Dtangosol.coherence.localport=8089
    -Dtangosol.coherence.wka1.port=8089
    -Dtangosol.coherence.wka2.port=8089
    
  10. Click Save.
  11. Repeat Step 7 to Step 10 for the second Managed Server, BPM_WLS2. Specify the listen address for the local host as the listen address corresponding to the second node.
  12. Click Activate Changes to end the edit session.

Configuring Java Object Cache

You can optionally configure Java Object Cache (JOC) by using the configure-joc.py script:

  1. Run the wlst.sh script
    cd $MIDDLEWARE_HOME/bpm/common/bin
    
    ./wlst.sh
  2. At the wls prompt, run the following command:
    connect()
  3. Provide the following details when you are prompted:
    • Your Oracle WebLogic Server Administrator credentials
    • Your Administration 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 Configuring Oracle Coherence.

    Do you want to specify a cluster name (y/n) y
    
    Enter Cluster Name : BPM_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 BPM_WLS1 and BPM_WLS2.

Creating JDBC Stores for Transaction Logs and JMS Servers

By default, transaction logs and JMS servers are configured to use file stores for persistence. However, your Oracle Java Cloud Service nodes don't share a file system, so you must convert the file stores to JDBC stores, which are accessible from all nodes.

To create JDBC stores:

  • Check the data source
  • Configure transaction logs JDBC stores for Managed Servers
  • Configure JDBC Stores for JMS servers

Checking the Data Source

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

  1. Sign in to the Oracle WebLogic Server Administration Console.
  2. Expand the Services menu in the left pane and select Data Sources.
  3. Click Lock & Edit to start an edit session.
  4. Click SOALocalTxDataSource.
  5. Click the Transaction tab.
  6. Deselect Supports Global Transactions if it's currently selected.
  7. Click Save.
  8. Click Activate Changes.

Configuring JDBC Stores for Transaction Logs

  1. Sign in to the Oracle WebLogic Server Administration Console.
  2. Expand the Environment menu in the left pane and select Servers.
  3. In the Summary of Servers page, click the appropriate Managed Server.
  4. On the Settings page, click the Services tab.
  5. Click Lock & Edit to begin an edit session.
  6. In the Transaction Log Store section, from the Type drop-down list, select JDBC.
  7. From the Data Source drop-down list, select SOALocalTxDataSource. The Prefix Name defaults to the correct value.
  8. Click Save.
  9. Click Activate Changes.
  10. Repeat these steps for the second Managed Server.

Configuring JDBC Stores for JMS Servers

  1. Sign in to the Oracle WebLogic Server Administration Console.
  2. Click Lock & Edit to start an edit session.
  3. Expand the Services menu in the left pane and from the Messaging submenu, click JMS Servers.
  4. On the Summary of JMS Servers page, for each Persistent Store, note the name of the File Store.
  5. From the Services menu in the left pane, click Persistent Stores.
  6. On the Summary of Persistent Stores page, note the target for each store. It should be a Managed Server.
  7. Click New and select Create JDBC Store.
  8. Enter a name for the new JDBC Store that corresponds to the File Store being replaced. For example, if the File Store is named FileStore_auto_1, then use JDBCStore_auto_1 for the new JDBC Store.
  9. From the Target drop-down list, select a target that matches the target of the File Store that is being replaced.
  10. Select SOALocalTxDataSource.
  11. Set the prefix name to a value unique to this JDBC store. For example, if the JDBC store name is WseeJDBCStore_auto_1, then you could use WseeJDBC_1 as the prefix name.
  12. Click OK to create the JDBC store.
  13. From the Services menu in the left pane, expand the Messaging submenu and select JMS Servers.
  14. Click the JMS server that uses the file store that is being replaced.
  15. From the Persistent Store drop-down list, select the JDBC store that you just created.
  16. Click Save.
  17. 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
    AGJMSFileStore_auto_1 AGJMSJDBCStore_auto_1 JCS_SOA1 AGJMSJDBC_1
    AGJMSFileStore_auto_2 AGJMSJDBCStore_auto_2 JCS_SOA2 AGJMSJDBC_2
    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
  18. Click Activate Changes.

Packing the Configured Domain and Unpacking It on VM2

  1. Sign in to the Oracle WebLogic Server Administration 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 sudo 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 scp 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 SSH 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 time stamp.

Starting All Servers

You should now be able to start all servers in the domain.

  1. To start the Administration Server, use VNC 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 Oracle 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.

Configuring Access via Oracle Traffic Director

To configure access using Oracle Traffic Director:

  1. Set the front-end HTTP host and port
  2. Create an access rule
  3. Enable the HTTP listener

Setting the Front-End HTTP Host and Port

To set the front-end HTTP host and port for the Oracle WebLogic Server cluster:

  1. Sign in to the Oracle WebLogic Server Administration Console.
  2. Click Lock & Edit to start an edit session.
  3. Expand the Environment menu in the left pane and select Clusters.
  4. On the Summary of Clusters page, select your Oracle BPM Suite cluster.
  5. Select HTTP.
  6. Enter the following:
    • Frontend Host: Public_IP_address_of_VM3
    • Frontend HTTP Port: 8080
    • Frontend HTTPS Port: Do not enter a value. Leave this blank.

      Note: The Frontend HTTPS Port must be left blank because, due to the Oracle BPM Suite 11g security constraints, the front-end host can't be set with the SSL port enabled.

  7. Click Save.
  8. Click Activate Changes.

Creating an Access Rule

When an Oracle Java Cloud Service Instance is 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 Enterprise Manager 11g Fusion Middleware Control. The public IP address of VM3 is used by the Oracle Traffic Director load balancer. This IP address is used to access the cluster of Managed Servers by entering the following URL:

https://Public_IP_address_of_VM3:8081

The default value used by Oracle Java Cloud Service when configuring Oracle Traffic Director is 8081.

To open the Oracle Traffic Director HTTP listener port, 8080, you must add an access rule. This access rule enables access from the network group for Oracle WebLogic Server Managed Servers (ora_ms) to the network group for Oracle Traffic Director (ora_otd) on port 8080. You require this access rule because, in an Oracle SOA Suite cluster topology, all URLs constructed by the Oracle SOA Suite servers use this port.

To add an access rule:

  1. Sign in to the My Services application and go to the My Services Dashboard.
  2. In the Oracle Compute Cloud Service section, click Open Service Console. The Oracle Compute Cloud Service Console appears.
  3. Click the Network tab.
  4. Click the Protocols tile.
  5. On the Protocols page, click Create Protocol and enter the following:
    • Name: Enter the required name, such as OTD_HTTP_PORT
    • Port Type: tcp
    • Port Range Start: 8080
    • Port Range End: 8080
    • Create Protocol screen

  6. Click Create. The protocol is created.
  7. Click the Access Rule tile.
  8. Click Create Access Rule and enter the following:
    • Name: Enter the required name, such as ms2otd_http
    • Status: Enabled
    • Protocol: Select the OTD_HTTP_PORT protocol that you just created
    • Source: From the Network Groups drop-down list, select ora_ms.
    • Destination: Select ora_otd.

    Create Access Rule screen

  9. Click Create. The access rule is created.

Enabling the HTTP Listener

  1. Sign in to the Oracle Traffic Director Administration Console by entering the following URL:
    https://Public_IP_address_of_VM3:8989
  2. In the opc-config pane, click Listeners and then select http-listener-1.
  3. Check Enabled.
  4. Click Save.
  5. Click Deploy Changes.

Restarting the Administration Server and Managed Servers

Sign in to the Oracle WebLogic Server Administration Console and shut down both the Managed Servers and the Administration Server. After all the servers are shut down, start the Administration Server and the Managed Servers as described earlier.

Verifying Deployment

  1. Sign in to the Oracle WebLogic Server Administration Console.
  2. In the left pane, click Deployments.
  3. On the Summary of Deployments page, check all components with prefix OracleBPM and ensure that there is a check mark in the Health column.
  4. Find out the IP address and port of your load balancer, if you didn't 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 page 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 8081.
  5. On your local machine or on VM1, verify that you can access the following URLs:
    https://Public_IP_address_of_VM3:8081/soa-infra
    https://Public_IP_address_of_VM3:8081/integration/worklistapp
    https://Public_IP_address_of_VM3:8081/bpm/workspace
    https://Public_IP_address_of_VM3:8081/bpm/composer
    

    Note: Use your Oracle 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*
    

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 and Oracle BPM Suite extensions are installed:
    1. From the Help menu select About and then select Extensions.
    2. Look for an identifier with the prefix oracle.bpm.
  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 bpm-jdev-extension.zip file from here.

    Look for the section Details for Oracle BPM Studio 11g. In the table, look for the version 11.1.1.7.0.0.97. Download and install the bpm-jdev-extension.zip file.

  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 BPM Suite. See the tutorial Building Your First Process with Oracle BPM 11g.
  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.

Targeting Deployments and Services

The following is the complete list of deployments and services that must be targeted to BPM_CLUSTER while extending your Oracle Java Cloud Service domain.

Targeting Deployments to Clusters or Servers

In the Target Deployments to Clusters or Servers page, ensure that the following deployments are targeted to BPM_CLUSTER. Some of these deployments are already targeted to BPM_CLUSTER, while others are targeted to soa_server1. For each of the following deployments, if it's not already done, set the target to BPM_CLUSTER.

Note: Some deployments are also targeted to the Administration Server. Don't remove the Administration Server for these deployments. Retain the Administration Server deployments as-is.

Application


       DMS Application
       wsil-wls
       wsm-pm
       UMSAdapter
       frevvo
       Fileadapter
       DbAdapter
       JmsAdapter
       AqAdapter
       FtpAdapter
       SocketAdapter
       MQSeriesAdapter
       OracleAppsAdapter
       OracleBamAdapter
       usermessagingserver
       usermessagingdriver-email
       soa-infra
       worklistapp
       b2bui
       DefaultToDoTaskFlow
       composer
       OracleBPMProcessRolesApp
       OracleBPMComposerRolesApp
       OracleBPMWorkspace
       BPMComposer
       SimpleApprovalTaskFlow

Library


       oracle.bi.adf.model.slib
       oracle.bi.adf.view.slib
       oracle.bi.adf.webcenter.slib
       oracle.wsm.seedpolicies
       oracle.jsp.next
       oracle.dconfig-infra
       orai18n-adf
       oracle.adf.dconfigbeans
       oracle.pwdgen
       oracle.jrf.system.filter
       adf.oracle.domain
       adf.oracle.businesseditor
       oracle.adf.management
       adf.oracle.domain.webapp
       jsf
       jstl
       UIX
       ohw-rcf
       ohw-uix
       oracle.adf.desktopintegration.model
       oracle.adf.desktopintegration
       oracle.bi.jbips
       oracle.bi.composer
       oracle.rules 

Note: Ensure that oracle.rules is also targeted to the Administration Server.


       oracle.sdp.client
       oracle.soa.workflow.wc
       oracle.soa.worklist.webapp
       oracle.soa.rules_editor_dc.webapp
       oracle.soa.rules_dict_dc.webapp
       oracle.sdp.messaging
       oracle.soa.worklist
       oracle.soa.bpel
       oracle.soa.workflow
       oracle.soa.mediator
       oracle.soa.composer.webapp
       oracle.soa.ext
       oracle.bpm.client
       oracle.bpm.runtime
       oracle.bpm.projectlib
       oracle.bpm.webapp.common
       oracle.bpm.composerlib
       oracle.bpm.workspace

Targeting Services to Clusters or Servers

In the Target Services to Clusters or Servers page, ensure that the following services are targeted to BPM_CLUSTER.


Shutdown Class
       JOC-Shutdown
       DMSShutdown
Startup Class
       JRF Startup Class
       JPG Startup Class
       ODL-Startup
       AWT Application Context Startup Class
       JMX Framework Startup Class
       Web Services Startup Class
       JOC-Startup
       DMS-Startup
       SOAStartupClass
JMS
   JMS System Resource
       PS6SOAJMSModule
       UMSJMSSystemResource
       BPMJMSModule
       SOAJMSModule
       AGJMSModule
JDBC
   JDBC System Resource
       mds-owsm
       OPSSDS
       OraSDPMDataSource
       SOADataSource
       EDNDataSource
       EDNLocalTxDataSource
       SOALocalTxDataSource
       mds-soa
WLDF System Resource
       Module-FMWDFW
Self Tuning
   Work Manager
       wm/SOAWorkManager

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?