Index Changes

Difference between version and version     

Back to Jbi_cluster Standalone_p, or Jbi_cluster Standalone_p Info


At line 2 changed 1 line.
%%(color:red;)__Beta Document for v2.1__%%
\\
At line 4 changed 1 line.
__Table of Contents__
__Contents__
At line 10 changed 12 lines.
* [Implementing Business Processes in a Cluster|jbi_cluster-bpel_p]
* [Implementing the IEP Service Engine in a Cluster|jbi_cluster-iep_t]
* [Implementing the XSLT Service Engine in a Cluster|jbi_cluster-xslt_p]
* [Implementing the Java EE Service Engine in a Cluster|jbi_cluster-javaee_p]
* [Implementing the Data Mashup Service Engine in a Cluster|jbi_cluster-dm_p]
* [Implementing the Database Binding Component in a Cluster|jbi_cluster-db_p]
* [Implementing the File Binding Component in a Cluster|jbi_cluster-file_p]
* [Implementing the FTP Binding Component in a Cluster|jbi_cluster-ftp_p]
* [Implementing the HTTP Binding Component in a Cluster|jbi_cluster-http_p]
* [Implementing the JMS Binding Component in a Cluster|jbi_cluster-jms_p]
* [Implementing the LDAP Binding Component in a Cluster|jbi_cluster-ldap_p]
* [Implementing the Scheduler Binding Component in a Cluster|jbi_cluster-schedbc_p]
* [Configuring the BPEL Service Engine for Clustering|jbi_cluster-bpel_p]
* [Configuring the IEP Service Engine for Clustering|jbi_cluster-iep_t]
* [Configuring the XSLT Service Engine for Clustering|jbi_cluster-xslt_p]
* [Configuring the Java EE Service Engine for Clustering|jbi_cluster-javaee_p]
* [Configuring the Data Mashup Service Engine for Clustering|jbi_cluster-dm_p]
* [Configuring the Database Binding Component for Clustering|jbi_cluster-db_p]
* [Configuring the File Binding Component for Clustering|jbi_cluster-file_p]
* [Configuring the FTP Binding Component for Clustering|jbi_cluster-ftp_p]
* [Configuring the HTTP Binding Component for Clustering|jbi_cluster-http_p]
* [Configuring the JMS Binding Component for Clustering|jbi_cluster-jms_p]
* [Configuring the LDAP Binding Component for Clustering|jbi_cluster-ldap_p]
* [Configuring the Scheduler Binding Component for Clustering|jbi_cluster-schedbc_p]
At line 23 changed 1 line.
* %%(color:#3333ff;)__[Implementing Components for Standalone High Availability and Failover|jbi_cluster-standalone_p]__%%\\
* %%(color:#3333ff;)__[Configuring Components for Standalone High Availability and Failover|jbi_cluster-standalone_p]__%%
** Configuring the BPEL Service Engine for Multiple Standalone Instances
** Configuring the IEP Service Engine for Multiple Standalone Instances\\
At line 27 changed 1 line.
!!!Implementing Components for Standalone High Availability and Failover
!!!Configuring Components for Standalone High Availability and Failover
At line 29 changed 1 line.
The BPEL SE and IEP SE provide high availability and failover features without using GlassFish clustering. This is done by deploying service engines across multiple standalone GlassFish domains installed on multiple machines. In this implementation, if one instance fails, any running BPEL or IEP instances failover to the running instances.
All GlassFish ESB components provide high availability and failover features without using GlassFish clustering. Implementing the BPEL SE and IEP SE in this type of environment requires special configuration. The service engines are installed across multiple standalone GlassFish domains installed on multiple machines. In this implementation, if one engine fails, any running BPEL or IEP processes failover to the running engines. \\
At line 40 changed 1 line.
You can deploy the same application across multiple BPEL SEs that connect to the same database. For both clustering and failover, persistence must be enabled for the business processes. \\
You can deploy the same application across multiple BPEL SEs that connect to the same database. For both clustering and failover, BPEL SE persistence must be enabled. \\
At line 66 changed 1 line.
You can deploy the same application across multiple IEP SEs that connect to the same database. \\
You can deploy the same application across multiple IEP SEs that connect to the same database. In a standalone environment, an event processor is owned by the IEP instance on which it is deployed first. The rest of the processing is similar to that in a clustered environment. All instances can receive the incoming messages, and once a message is received it is inserted into the IEP database. The instance that owns the event processor picks up the event to complete processing and writes the output. If an IEP instance fails, any in-process transactions are taken over by one of the remaining IEP instances and the process is completed. When the failed engine recovers, it continues to process new requests. \\

JSPWiki v2.4.100
[RSS]
« Home Index Changes Prefs
This page (revision-13) was last changed on 09-Jun-09 11:57 AM, -0700 by CarolT