Failover Considerations

In order to configure failover for BPEL Service Engines, you must adhere to the following guidelines:

• Persistence must be enabled for both load balancing and failover.

• To run persistence, all BPEL Service Engines must be restarted.

• Service assemblies must be deployed manually across all clustered JBI environments.

• Failover is implemented consistently for the specific protocol and binding components involved in a given business process.

• Only a single database can be used for all BPEL Service Engines when implementing failover.

• The database must be highly available; should the database fail, failover will fail.

• When a BPEL Service Engine fails, a single BPEL Service Engine picks up those instances without distributing them across the balanced system. Consequently, a large number of failed over instances can overload an entire system, one service engine at a time, as a sort of domino effect.

• All BPEL Service Engines in a load balanced system must reside in the same time zone.