High availability FileNet P8 Application Engine, FileNet P8 Content Engine, Version 5.0.+              

Content Engine in an application server cluster by using EJB transport

You can configure clients, such as Application Engine, that use EJB transport to communicate with the Content Engine in an application server cluster.

For clients such as Application Engine that use an EJB transport to communicate with Content Engine in an application server cluster configuration, you must use an URL with a format different from non-highly available configurations.
Restriction: In these examples, the "cemp" portion at the beginning of the URI is required by IBM® FileNet® P8 applications, such as Workplace and Workplace XT. If you are developing and using your own applications, the "cemp" prefix is not required.

When Content Engine is made highly available through an application server cluster configuration the Content Engine URL should have the following form:

WebSphere Application Server

SSL
cemp:corbalocs::node1_ hostname:WC_default_secure_port,:node2_hostname :WC_default_secure_port/cell/clusters/your_websphere_cluster_name/FileNet/Engine
Non-SSL
cemp:corbaloc::node1_ hostname:WC_default port,:node2_hostname:WC_default port/ cell/clusters/your_websphere_cluster_name/FileNet/Engine

This configuration requires the WebSphere® cluster name in addition to the node names as part of the URL. The default bootstrap port (for example, 9810) is different from the non-default (for example, 2809) on a non cluster configuration (that is, a standalone WebSphere installation).

Only one URL is used regardless of SSL use. When using WebSphere an SSL connection is automatically established by using this transport if the SSL port is enabled for the WebSphere application server instance.

Example: cemp:corbaloc::testnode1:9810,:testnode2:9810/cell/clusters/testwascluster/FileNet/Engine

Oracle WebLogic Server

SSL
cemp:t3S://node1 name:node1 SSL port , node2 name:node2 SSL port/FileNet/Engine
Non-SSL
cemp:t3://node1 name:node1 port ,node2 name:node2 port /FileNet/Engine
Even though the individual server names are shown, Oracle WebLogic Server will load-balance requests through the EJB transport to the Content Engine if the server instances are part of a Oracle WebLogic Server cluster.

Example: cemp:t3://testnode1:7001,testnode2:7001/FileNet/Engine

JBoss Application Server

SSL
For information, see JBoss Application Server documentation for SSL.
Non-SSL
cemp:jnp://node1_name:node1_port , node2_name:node2_port/FileNet/Engine

The behavior of JBoss Application Server is the opposite of Oracle WebLogic Server in the previous note; instead of load-balancing through the shown servers, JBoss Application Server tries the list in order and connects to the first server that responds.

Example: cemp:jnp://testnode1:1100,testnode2:1100/FileNet/Engine



Feedback

Last updated: November 2010


© Copyright IBM Corporation 2010.
This information center is powered by Eclipse technology. (http://www.eclipse.org)