| Installing Upgrading Designing Configuring Deploying Monitoring Administering Troubleshooting Reference JBI Components | |
| Close Print View | |
| Using JBI Components: Clustering |
|
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 a business process needs to be scaled to meet heavier processing needs, you can distribute it across multiple service engines to increase throughput. The BPEL Service Engine's clustering algorithm automatically distributes processing across multiple engines. To configure clustering, deploy your composite applications across multiple BPEL Service Engines running on multiple processors or systems.
For details about setting up a cluster of application servers with BPEL Service Engines, see the documentation for Sun Java System Application Server.