A highly available FileNet® P8 system consists of components such as Content Platform Engine or Application Engine that are deployed as all-inclusive applications containing both presentation and business logic on multiple running instances.
An enterprise content management system typically consists of multiple tiers. For example, a system might have a web server tier, an application server tier for business logic, a content repository tier for managing content, and a data storage tier. A chain is only as strong as its weakest link, so a high availability solution requires a high availability configuration for every tier. The different tier types and server types require different technical solutions for high availability, primarily server farms with no sharing or server clusters with shared storage.
In a highly available FileNet P8 environment however, components such as Application Engine and Content Platform Engine are each installed and deployed as all-inclusive applications (presentation and business logic components) on multiple running instances.
The Application Engine architecture does not separate the images and static content of the Workplace application on separate server instance from the servlets and Java™ server pages of the Workplace application. Instead, all these components are deployed on one server instance.
Furthermore, neither Content Platform Engine nor Application Engine requires any applications or components be running on any server that is not intended to run the Content Platform Engine or Application Engine itself.
When you use a load-balancer or proxy server in a configuration of FileNet P8 components, you are not required to install and run the legacy Component Manager on the load balancer or proxy server.
Other essential high availability building blocks include: