You can use load balancers to manage client requests across all of the nodes in a FileNet® P8 server farm.
Farming requires a mechanism to balance the load across all the nodes in a farm, and to redirect client connections to surviving nodes in case of failure. This section summarizes the available load balancing options.
A number of hardware and software load-balancing products are available for server farm configurations, including IBM®, Oracle, F5 Big IP, and JBoss.
Vendor | Notes® |
---|---|
Oracle WebLogic Server clusters | - |
F5 Big IP | - |
IBM WebSphere® Application Server Network Deployment clusters | Formerly called server group of clones. |
JBoss Application Server cluster | Also called High Availability partition. |
Content Platform Engine is hosted on a Java™ application server. Both the Oracle and IBM Java application servers have built-in capabilities for providing highly available web services. Each application server product is capable of configuring a collection of server instances that function as a single entity in order to provide an application to a user. Both Oracle WebLogic Server and IBM WebSphere Application Server calls this collection of server instances a Cluster. Both products function like a server farm.
JBoss Application Server clusters do not use a separate administrative server. In a JBoss cluster, all nodes grouped together in a partition are equivalent. Applications must be deployed on each node individually unless the optional JBoss farm service is used, and individual nodes are started and stopped independently. For details on the JBoss farm service, see the JBoss Application Server documentation.