Question & Answer
Content Platform Engine (CPE) has two transport layers: Web Services and EJB. All client requests enter CPE through one of these two transport layers.
• Web Services
- The listener exposes the full functionality of the CPE server through a standard Web services API and uses a load balancer for high availability.
- The Java EE session beans reside in the EJB tier of the application server. All clients of this layer must perform a JAAS login prior to sending a request to one of the EJBs. The recommended approach when using the EJB transport for high availability is to use application server clusters. A hardware load balancer cannot be used between application servers that are using the EJB transport because EJB uses long lived sessions and only the first EJB lookup call from an application actually goes through the hardware load balancer. All subsequent EJB calls circumvent the hardware load balancer.
With the EJB transport, the recommended approach to creating highly available ECM applications is by creating clusters of application servers that use technology such as WebSphere ND because this approach provides the simplest and most effective method of balancing workloads, session replication and achieving transparent failover.
If using a server cluster technology such as WebSphere ND is not possible, then high availability can be achieved using a “Stovepipe” configuration in which each server in the application tier is directed to a specific CPE instance.
The purpose of this document is to provide the high-level steps for configuring a stovepipe environment for use by IBM FileNet Content Platform Engine (CPE) and IBM Content Navigator (ICN). This document does not provide details on how to configure hardware load balancers for distributing load or for monitoring the availability of components in the stovepipe configuration.
The high availability approach described above has inherent limitations and drawbacks. To provide a comprehensive and transparent highly available solution, IBM strongly recommends the use of an application server clustering solution such as WebSphere Application Server Network Deployment.
17 September 2019