|Oracle® Exalogic Elastic Cloud Enterprise Deployment Guide for Oracle SOA Suite
Release EL X2-2 and EL X3-2
|PDF · Mobi · ePub|
This chapter describes the procedures for extending the domain to include Oracle BPM.
This chapter contains the following section:
You can install and configure Oracle BPM in a Fusion Middleware installation in the following two ways:
Extend an existing domain that contains an Administration Server (and optionally other non-SOA servers) to include SOA and BPM (in one single Configuration Wizard session). For configuration steps, see Section 10.2, "Option 1: Extending a Domain to Include SOA and BPM."
Extend a domain that already contains SOA (and optionally other non-SOA servers) to BPM. For configuration steps, see Section 10.3, "Option 2: Extending a SOA Domain to Include Oracle BPM."
Before you extend the current domain, ensure that your existing deployment meets the following prerequisites:
Back up the installation - If you have not yet backed up the existing Fusion Middleware Home and domain, Oracle recommends backing it up now. For more information, see Section 14.8, "Backing Up the Oracle SOA Enterprise Deployment."
There is an existing WL_HOME and ORACLE_HOME installed in previous chapters on a shared storage.
It is assumed that a SOA ORACLE_HOME (binaries) has already been installed, patched to latest patch set (if applicable), and is available from SOAHOST1 and SOAHOST2. it is also assumed that a domain with an Administration Server has been created. This is the domain that is extended in this chapter to support SOA and BPM components.
To extend a domain with SOA and BPM components using the Configuration Wizard, follow the exact same steps in Chapter 9, "Extending the Domain for SOA Components" and make the following modifications:
In the Select Extension Source screen, select Oracle BPM Suite - 126.96.36.199 [soa] beside the products indicated in Chapter 9, "Extending the Domain for SOA Components."
In the Target Deployments to Clusters screen, besides the appropriate targets indicated in Chapter 9, "Extending the Domain for SOA Components,", ensure that
oracle.BPM.* deployments target
/bpm/workspace URIs to the Oracle Traffic Director (OTD) route properties created for SOA.
Update the appropriate persistent stores for the BPM JMS Servers
In this step, you extend the domain created to include Oracle BPM.
Before extending the current domain, ensure that your existing deployment meets the following prerequisites:
Back up the installation - If you have not yet backed up the existing Fusion Middleware Home and domain, Oracle recommends backing it up now.
To back up the existing Fusion Middleware Home and domain:
tar -cvpf fmwhomeback.tar ORACLE_BASE/product/fmw tar -cvpf domainhomeback.tar ORACLE_BASE/config/domain_name
These commands create a backup of the installation files for both Oracle WebLogic Server and Oracle Fusion Middleware, as well as the domain configuration.
There is an existing WL_HOME and SOA ORACLE_HOME (binaries) are installed in previous chapters on a shared storage and are available from SOAHOST1 and SOAHOST2 (this is required before the WebLogic Configuration Wizard steps are performed to extend the domain).
Node Manager, Admin Server, SOA Servers and WSM Servers exist and have been configured as described in previous chapters to run a SOA system. Server migration, transaction logs, coherence, and all other configuration steps for the SOA System have already been performed and will be used by BPM. BPM is added as a superset of the existing configuration.
This section contains the following topics:
Run the Configuration Wizard from the
ORACLE_COMMON_HOME directory to extend a domain containing an Administration Server and Oracle Web Services Manager to support SOA and BPM components.
Change the directory to the location of the Configuration Wizard. This is within the SOA home directory. Domain extensions are run from the node where the Administration Server resides.
Start the Oracle Fusion Middleware Configuration Wizard:
In the Welcome screen, select Extend an Existing WebLogic Domain, and click Next.
In the WebLogic Domain Directory screen, select the WebLogic domain directory ASERVER_HOME, and click Next.
In the Select Extension Source screen, do the following:
Select Extend my domain automatically to support the following added products. Select the following products:
Select the following product:
Oracle BPM Suite - 188.8.131.52 [soa]
In the Configure JDBC Component Schema screen, accept existing values (schemas created in the existing SOA system) and click Next.
Oracle BPM uses the same Data Sources as the existing soa-infra system.
In the Optional Configuration screen, select the following:
JMS Distributed Destinations
Deployments and Services
JMS File Store
Target WSM-PM only to WSM-PM_Cluster.
Target usermessagingserver and usermessagingdriver-email only to SOA_Cluster. (The usermessaging-xmpp, usermessaging-smpp, and usermessaging-voicexml applications are optional.)
Target the oracle.sdp.*, oracle.bpm.*, and oracle.soa.* libraries only to SOA_Cluster.
Target the oracle.rules.* library to SOA_Cluster and Admin Server.
In the Target Services to Clusters or Servers screen, target the mds-owsm datasource to the WSM-PM_Cluster and the AdminServer and click Next.
In the Configure JMS File Stores screen, enter the shared directory location specified for your JMS stores as recommended in Section 4.4, "Recommended Directory Locations for an Oracle Exalogic Enterprise Deployment." For example:
Select Direct-write policy for all stores.
In the Configuration Summary screen click Extend.
In the Creating Domain screen, click Done.
You must restart the Administration Server for this configuration to take effect; see Section 8.5.3, "Starting the Administration Server on SOAHOST1."
Oracle BPM Suite requires some updates to the WebLogic Server start scripts. Propagate these changes using the pack and unpack commands.
To propagate the start scripts and classpath configuration from the Administration Server's domain directory to the managed server domain directory:
Create a backup copy of the managed server domain directory and the managed server applications directory.
pack command on SOAHOST1 to create a template pack:
cd ORACLE_COMMON_HOME/common/bin ./pack.sh -managed=true -domain=ASERVER_HOME -template=soadomaintemplateExtSOABPM.jar -template_name=soa_domain_templateExtSOABPM
Run the unpack command on SOAHOST1 to unpack the propagated template to the domain directory of the managed server:
./unpack.sh -domain= MSERVER_HOME -overwrite_domain=true -template=soadomaintemplateExtSOABPM.jar -app_dir=APP_DIR
-overwrite_domain option in the unpack command, allows unpacking a managed server template into an existing domain and existing applications directories. For any file that is overwritten, a backup copy of the original is created. If any modifications had been applied to the start scripts and ear files in the managed server domain directory they must be restored after this unpack operation.
Run the unpack command on SOAHOST2 to unpack the propagated template:
cd ORACLE_COMMON_HOME/common/bin ./unpack.sh -domain=MSERVER_HOME/ -overwrite_domain=true -template=soadomaintemplateExtBPM.jar -app_dir=APP_DIR
The configuration steps provided in this Exalogic enterprise deployment topology are documented with the assumption that a private (per node) domain directory is used for each managed server.
For configuration changes and start scripts to be effective, you must restart the WLS_SOAn server to which BPM has been added. Since BPM extends an already existing SOA system, the Administration Server and respective Node Managers are already running in SOAHOST1 and SOAHOST2.
To start the added BPM components:
Restart the WLS_SOA1 managed server:
Log into the Oracle WebLogic Server Administration Console at:
In the Domain Structure window, expand the Environment node, then select Servers.
The Summary of Servers page appears.
Click the Control tab.
Select WLS_SOA1 from the Servers column of the table.
Click Shutdown. Wait for the shutdown to complete (refresh the WebLogic Server Console page to verify shutdown status).
Repeat steps a-f for WLS_SOA2.
To enable Oracle Traffic Director (OTD) to route to the appropriate BPM URIs, add the following to the route rules for both the
soainternal.mycompany.com and the
soa.mycompany.com virtual servers:
Verify URLs to ensure that appropriate routing and failover is working from the OTD Server to the BPM Suite Components.
For information on configuring system access through the load balancer, see Section 3.7, "Configuring the Load Balancer."
To verify the URLs:
While WLS_SOA is running, stop WLS_SOA1 using the Oracle WebLogic Server Administration Console.
http://webhostN-priv-v1:7777/bpm/workspace to verify the appropriate functionality for BPM project Composer.
Start WLS_SOA1 from the Oracle WebLogic Server Administration Console.
Stop WLS_SOA2 from the Oracle WebLogic Server Administration Console.
http://webhostN-priv-v1:7777/bpm/workspace to verify the appropriate functionality for BPM Workspace.
You can also verify these URLs using your load balancer address:
Back up the Oracle BPM configuration. For more information, see Section 14.8, "Backing Up the Oracle SOA Enterprise Deployment."