Adding the BPEL Service Engine to the Cluster

Before you can add the BPEL SE to a cluster, you need to add a shared library. When you add the BPEL SE to a cluster, you need to configure certain properties. The SE must be configured for persistence and pointing to the correct data sources. All instances of the BPEL SE should point to a single persistence database (which you created earlier under To Set Up the BPEL Database).

To Add the BPEL Service Engine to the Cluster

1. Add the following shared library to the cluster as described in To Add a Shared Library to a Cluster:

   • sun-wsdl-ext-library

2. Add the BPEL SE (sun-bpel-engine) to the cluster as described in To Add a Java CAPS JBI Component to a Cluster. Configure the following properties on the Manage Targets page before you click OK:

   1. Under General – Configure Component, specify a value for the Lease Renewal Interval.

      ---

      Note –

      The Lease Renewal Interval is the time period in seconds that BPEL engines wait before renewing their lease to let the cluster know it is still running (also known as the heartbeat). If an engine does not update within the specified time period, it is considered to be unavailable.

      ---

   2. Under Persistence – Manage Persistence/Recovery, set Persistence Enabled to true.

   3. In the Non XA Data Source Name property, enter the JNDI name of the non-XA JDBC resource that you created earlier.

   4. In the XA Data Source Name property, enter the JNDI name of the XA JDBC resource that you created earlier.

      This is the database that persists state data for business process instances for recovery.

   5. Configure the remaining runtime properties as you typically would for the BPEL SE.

      For more information, see Configuring the BPEL Service Engine Runtime Properties in Using the BPEL Designer and Service Engine.

3. Verify that the engines table in the persistence database contains a row for each instance in the cluster.

   ---

   Tip –

   If the rows do not appear, check the following:

   • Both JDBC Resources are enabled on the target cluster.

   • The engine is enabled on the target cluster.

   If both of the above are enabled, you might need to stop and restart the BPEL SE in order for the rows to appear.

   You can also verify that the engines are renewing the lease within the specified interval by querying the engines table again after the interval has passed and verifying that the LASTUPDATETIME column is updated accordingly.

   ---