| Installing Upgrading Designing Configuring Deploying Monitoring Administering Troubleshooting Reference JBI Components | |
| Close Print View | |
| Using JBI Components: Failover |
|
Configuring WSDL Extensibility Elements
HTTP WSDL Extensibility Elements
SOAP WSDL Extensibility Elements
Configuring JBI Runtime Properties
Configuring the BPEL Service Engine Runtime Properties
Starting the Application Server
Viewing Service Engine Properties
HTTP Binding Component Runtime Properties
Configuring BPEL Service Engine Clustering and Failover
Clustering/Failover Considerations
Configuring the HTTP Binding Component for Clustering
Administering JBI Components for Java CAPS
Using the Java EE Service Engine in a Project
Using the Java EE Service Engine to Create a Composite Application
Using the BPEL Designer and Service Engine
Using the HTTP Binding Component
Processing an Order in a Purchase Order System
XSLT Designer: Simple Transformation Tutorial
Using the File Binding Component
Using the File Binding Component in a Project
Using the JMS Binding Component
Understanding the FTP Binding Component
Using the FTP Binding Component in a Project
Understanding the LDAP Binding Component
Using the LDAP Binding Component in a Project
Using the JAXB Wizard and Code-Seeder Pallete
Understanding the Database Binding Component
Using the Database Binding Component
Migrating From eTL to Sun Data Integrator
Designing Intelligent Event Processor (IEP) Projects
When your business process is configured for clustering, the BPEL Service Engine's failover capabilities ensure throughput of running business process instances. When business process instances encounter an engine failure, any suspended instances are picked up by all available BPEL Service Engines.
To configure failover, in the BPEL Service Engine properties, set the EngineExpiryInterval
property so that it registers itself as alive frequently enough to meet the
demands of your system. Optimizing this property setting might require some testing. The
default setting is 15.