FileNet P8 Application Engine, Content Platform Engine, Version 5.2.1

Content Platform 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 Platform Engine in an application server cluster.

For clients such as Application Engine that use an EJB transport to communicate with Content Platform Engine in an application server cluster configuration, you must use a URI with a format different from non-highly available configurations.

Restriction: In the examples below, if the URI is intended for use by some older applications, such as FileNet® P8 applications Workplace or Workplace XT, the token cemp: must be prepended to the URI. For example, you would use the URI cemp:corbaloc::testnode1:9810,:testnode2:9810/cell/clusters/ testwascluster/FileNet/Engine instead of corbaloc::testnode1:9810,:testnode2:9810/cell/clusters/ testwascluster/FileNet/Engine.

When Content Platform Engine is made highly available through an application server cluster configuration the Content Platform Engine URI should have the following form (with no carriage returns):

WebSphere Application Server

corbaloc::node1_hostname:BOOTSTRAP_ADDRESS,
:node2_hostname:BOOTSTRAP_ADDRESS/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 URI. The bootstrap port for a cluster configuration (by default, port 9810) is usually different from the bootstrap port on a non-cluster (standalone) configuration (by default, port 2809).

Only one URI is used regardless of SSL use. WebSphere EJB over SSL is automatically established if EJB security is enabled.

Example:

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

If the EJB client is deployed into the same WebSphere Network Deployment cell as Content Platform Engine, you can use one of the following, simpler corbaloc URIs:

Example for IBM® Content Navigator:

corbaloc:rir:/cell/clusters/your_websphere_cluster_name/FileNet/Engine

Example for Workplace and Workplace XT:

cemp:corbaloc:rir:/cell/clusters/your_websphere_cluster_name/FileNet/Engine

Oracle WebLogic Server

SSL: t3s://node1_name:node1_SSL_port,node2 name:node2 SSL port/FileNet/Engine
Non-SSL: 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 Content Platform Engine if the server instances are part of a Oracle WebLogic Server cluster.

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

JBoss Application Server

SSL: For information, see JBoss Application Server documentation for SSL.
Non-SSL: 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: jnp://testnode1:1100,testnode2:1100/FileNet/Engine