Skip Navigation Links | |
Exit Print View | |
Configuring Oracle Java CAPS JBI Components for GlassFish Clustering Java CAPS Documentation |
Configuring Oracle Java CAPS JBI Components for Clustering
JBI Component Clustering Overview
Component Support for Clustering
Adding a Java CAPS JBI Component to a Cluster
To Add a Shared Library to a Cluster
To Add a Java CAPS JBI Component to a Cluster
Modifying Server Properties for Java CAPS JBI Components in a Cluster
To Modify Runtime Properties for a Component in a Cluster
To Create Application Configurations and Variables for a Component in a Cluster
To View the Descriptor for a Component in a Cluster
To Set Logging Properties for a Component in a Cluster
To Monitor a Component in a Cluster
Configuring the BPEL Service Engine for Clustering
Adding the BPEL Service Engine to the Cluster
To Add the BPEL Service Engine to the Cluster
Debugging a Business Process Deployed in a Cluster
To Debug a Business Process Deployed in a Cluster
Configuring the XSLT Service Engine for Clustering
To Add the XSLT Service Engine to the Cluster
Configuring the Java EE Service Engine for Clustering
To Enable the Java EE Service Engine on the Cluster
Configuring the Data Mashup Service Engine for Clustering
To Add the Data Mashup Service Engine to the Cluster
Configuring the Database Binding Component for Clustering
Creating the Clustering Database for the Database Binding Component
To Create the Clustering Database for the Database Binding Component
Adding the Database Binding Component to the Cluster
To Add the Database Binding Component to the Cluster
Configuring the File Binding Component for Clustering
Adding the File Binding Component to the Cluster
To Add the File Binding Component to the Cluster
Configuring the File BC WSDL File for Clustering
To Configure the File BC WSDL File for Clustering
Configuring the FTP Binding Component for Clustering
Adding the FTP Binding Component to the Cluster
To Add the FTP Binding Component to the Cluster
Configuring the FTP BC WSDL for Clustering
To Configure the FTP BC WSDL for Clustering
Configuring the HTTP Binding Component for Clustering
Enabling the HTTP Binding Component on the Cluster
To Enable the HTTP Binding Component on the Cluster
Configuring the HTTP BC Port Numbers for Clustering
To Configure the HTTP BC Port Numbers for Clustering
Configuring the JMS Binding Component for Clustering
To Add the JMS Binding Component to the Cluster
Configuring the LDAP Binding Component for Clustering
To Add the LDAP Binding Component to the Cluster
Configuring the Scheduler Binding Component for Clustering
To Add the Scheduler Binding Component to the Cluster
Deploying a Service Assembly to a Cluster
To Deploy a Service Assembly to a Cluster
Configuring Components for Standalone High Availability and Failover
Configuring the BPEL Service Engine for Multiple Standalone Instances
To Configure the BPEL Service Engine for Multiple Standalone Instances
Configuring the IEP Service Engine for Multiple Standalone Instances
To Configure the IEP Service Engine for Multiple Standalone Instances
You can configure the IEP SE to run in a GlassFish cluster on the same or different servers, You can also configure the SE for high availability and failover on a standalone GlassFish server. This topic describes configuring the IEP SE on a GlassFish cluster. For information on standalone configuration for high availability and failover, see Configuring Components for Standalone High Availability and Failover). The IEP SE can be implemented in a cluster on the same or different servers.
The IEP SE uses a database to maintain instance information in a cluster. In a clustered environment, an event processor belongs to any one of the live cluster instances at a given time. All instances can receive the incoming messages, and once a message is received it is inserted into the IEP database for further processing. The instance that owns the event processor picks up the event to complete processing. The output is only written by the instance that owns the event processor. If an instance fails, any in-process transactions are taken over by one of the remaining instances and the process is completed. When the failed engine recovers, it continues to process new requests.
The IEP SE is not dependent on any shared libraries.
Note - The servers in a cluster need to be on the same time zone in order to detect whether an instance has failed.
Default connection pools and JDBC resources are automatically created for an IEP Derby database, as are the Derby database and persistence tables once you enable the engine on the cluster. The tables are automatically created for an Oracle database, but you need to manually create the connection pools and JDBC resources for Oracle.
For Derby, you can customize the default connection pools and JDBC resources if necessary, or create new ones for the cluster. IEP uses both XA and non-XA transactions so two connection pools and JDBC resources are required, one for each type.
For more information about creating connection pools and JDBC resources, see Chapter 3, “JDBC Resources”, in Sun GlassFish Enterprise Server v2.1.1 High Availability Administration Guide.
http://wiki.open-esb.java.net/attach/HowToRunIEPOnOracle/create_iepse_user.sql
Note - For Derby, you can use the connection pools that are automatically created when IEP is installed.
Host (can be localhost)
PortNumber (1527 is the default Derby port)
DatabaseName
User
Password
connectionAttributes (set this to ;create=true to automatically create the Derby database)
URL (the format for the URL is jdbc:oracle:thin:@hostName:portNumber:databaseName)
user
password
This adds the resource to the cluster and enables the resource on the cluster.
The IEP SE is not dependent on any shared libraries; you only need to add the service engine to the cluster.
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.
This is the database that persists state data for business process instances for recovery.
For more information, see Oracle Java CAPS Intelligent Event Processor (IEP) User’s Guide.
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 IEP SE in order for the rows to appear.