29 Configuring External Oracle BPEL Process Manager with Oracle Beehive

If you have an existing instance of Oracle BPEL Process Manager, you may configure Oracle Beehive to use it instead of the one that is included with Oracle Beehive.

Note:

It is recommended that you configure an external Oracle BPEL process manager immediately after installing Oracle Beehive.

It is not recommended that you switch from using the Oracle BPEL Process Manager that comes installed with Oracle Beehive to an external one in an Oracle Beehive currently in production.

Configuring an external Oracle BPEL Process Manager involves the following steps:

Step A: Configure Oracle Beehive
Step B: Configure External Oracle BPEL Process Manager

After performing these steps, refer to "Deploying Custom Workflows with External Oracle BPEL Process Manager" to deploy custom workflows.

Step A: Configure Oracle Beehive

Create an external Oracle BPEL Process Manager component to represent your Oracle BPEL Process Manager. Use the beectl add_external_bpel_pm command:

beectl add_external_bpel_pm
  --oc4j_instance_name oc4j_soa
  --oc4j_admin_password my_obfuscated_OC4J_admin_password
  --domain default
  --domain_password my_obfuscated_domain_password
  --bpel_application_name orabpel
  --bpel_admin_password my_obfuscated_BPEL_password
  --host_name example.com
  --opmn_port 6003

Successfully created a BpelCluster with following identifier.
BPEL_CLUSTER_ID=ec542d17-0a13-4974-b6a4-f61526d09215
Successfully created a ExternalBpelProcessManager with the following id.
EXT_BPEL_PROCESS_MANAGER_ID=cb5d934a-fe61-44e0-906a-bf2d0b1c80e1
Workflow service exists with the id 79af98cb-81d1-4318-9f22-84d36e268e86
Changes to configuration repository are not activated.

This command will create a BpelCluster component. Note the IDs of this component for the next step.

The following table describes the properties of this command:

Table 29-1 beectl add_external_bpel_pm Properties

Property	Description
oc4j_instance_name	Name of the OC4J instance in which your Oracle BPEL Process Manager is deployed. Typically, this is `oc4j_soa`.
oc4j_admin_password	Administrator's password of OC4J in which your Oracle BPEL Process Manager is deployed. Use `beectl obfuscate` to obfuscate the password.
domain	If you have not created any additional domains in your Oracle BPEL Process Manager, typically, the name of the default domain is `default`. Refer to Chapter 19, "BPEL Process Deployment and Domain Management" in Oracle BPEL Process Manager Developer's Guide.
domain_password	The password to access the specified domain. By default, this is the same as the OC4J administrator's password. Use `beectl obfuscate` to obfuscate the password.
bpel_application_name	Name used by OC4J to refer to the Oracle BPEL Process Manager Web application. Typically, this is `orabpel`. Refer to the OC4J configuration files of the OC4J instance in which your Oracle BPEL process is deployed to determine this name.
bpel_admin_password	Oracle BPEL Process Manager administrator's password. Use `beectl obfuscate` to obfuscate the password.
host_name	The name of the server in which Oracle BPEL Process is running.
opmn_port	OPMN request port number of the Oracle BPEL server. This is typically `6003`. If you installed Oracle Application Sever SOA Suite, this port number is defined by the property `opmn.requestport` in `<Installation directory>/bpel/utilities/and-orabpel.properties`.

Set the property BpelCluster in the component _WorkflowService with the BpelCluster component you just created in the previous step:
```
beectl modify_property
  --component _WorkflowService
  --name BpelCluster
  --value ec542d17-0a13-4974-b6a4-f61526d09215
```

Activate the configuration and commit changes:

beectl activate_configuration
beectl modify_local_configuration_files

Step B: Configure External Oracle BPEL Process Manager

Create a synonym in the ORABPEL repository for the Oracle Beehive Workflow PL/SQL schema. Typically, ORABPEL and the Oracle Beehive schema are located in the same database instance. If this is the case, run the following SQL*Plus command:

CREATE OR REPLACE SYNONYM ORABPEL.BEE_CODE_WF_BPEL_PKG FOR BEE_CODE.WF_BPEL_PKG

If ORABPEL and the Oracle Beehive schema are in different database instances, use a database link. Refer to "CREATE DATABASE LINK" in Oracle Database SQL Language Reference for more information.
Follow these steps to deploy Oracle Beehive Identify Provider.

Note:
If you have configured your Oracle BPEL Process Manager for a particular LDAP directory, and you have synchronized Oracle Beehive to work with the same LDAP directory (as described in "Integrating and Synchronizing LDAP with Oracle Beehive"), do not perform the steps described here.
1. Extract the contents of <Oracle Beehive home>/beehive/seed/bpel/isprovider.jar into the <Oracle BPEL Process Manager home>/bpel/system/classes directory. The command jar is the Java archive tool:
```
cd <Oracle BPEL Process Manager home>/bpel/system/classes
jar xvf <Oracle Beehive home>/beehive/seed/bpel/isprovider.jar
```
2. Create a backup of the file <Oracle BPEL Process Manager home>/bpel/system/config/is_config.xml. Replace this file with <Oracle Beehive home>/beehive/seed/bpel/is_config.xml
After performing these steps, any identity services you have configured for your Oracle BPEL Process Manager will no longer work.

If you want Oracle Beehive Identity Provider and another identity service you have already configured to co-exist in your Oracle BPEL Process Manager, you may merge the details of your identity service configuration and those of Oracle Beehive Identity Provider in the same is_config.xml file. Refer to "Configuring the Identity Service" in Chapter 2, "Service Configuration" in Oracle BPEL Process Manager Administrator's Guide.
Deploy Oracle Beehive workflows. The Workflow service deploys two BPEL processes, ParallelVoteWorkflow and SerialWorkflow, when you install Oracle Beehive. These BPEL process suitcases (or archives) are located in <Oracle Beehive home>/beehive/seed/workflows. Deploy these processes with the Oracle BPEL Admin Console or auto-deploy mode of Oracle BPEL Process Manager. To use auto-deploy mode, copy the BPEL process jar files into <Oracle BPEL Process Manager home>/bpel/domains/default/deploy.

Deploying Custom Workflows with External Oracle BPEL Process Manager

To deploy a custom workflow with an external Oracle BPEL Process Manager, you must both register it in Oracle Beehive and deploy it through your Oracle BPEL Process Manager:

Use the beectl add_workflow_schema command to register your custom workflow:

beectl add_workflow_schema
  --file <Absolute path of the suitcase (the jar file) of your BPEL process>

Manually deploy the custom workflow suitcase into your Oracle BPEL Process Manager with the Oracle BPEL Admin Console or auto-deploy mode.