Installation of FileNet CPE

1. Installing Content Platform Engine and IBM Case Foundation
   You must install the Content Platform Engine software to place the binary files for its components on the server. If you purchased IBM Case Foundation or will be installing IBM Case Manager, you must also install IBM Case Foundation.
2. Configuring Content Platform Engine
   You can configure and deploy all of your Content Platform Engine instances with Configuration Manager. Configuration Manager prepares the Content Platform Engine application for deployment on the application server. A single Content Platform Engine application instance equates to one deployed application on your application server.
3. Configuring WebSphere with Security Directory Server federated repositories
   You must complete some additional steps when configuring Content Platform Engine to run on WebSphere® with Security Directory Server federated repositories. If you are not using federated repositories, or if Security Directory Server is configured to use inetOrgPerson for logins, skip these steps.
4. Deploying Content Platform Engine instances
   Depending on your environment, you can use the Configuration Manager graphical user interface, or the command line, to deploy Content Platform Engine instances.
5. Installing storage device source files
   If your FileNet P8 system includes Spectrum Protect or EMC Centera devices, you must install files on the Content Platform Engine server.
6. Configuring file stores for high availability
   File store content is managed from the Content Platform Engine application.
7. Completing Content Platform Engine post-deployment steps
   You must complete the post-deployment web application server configuration before you can put a FileNet P8 system into production.
8. Verifying the Content Platform Engine deployment
   You can verify that the Content Platform Engine deployment was successful by accessing the FileNet P8 System Health page and the Content Platform Engine Startup Context (Ping Page).
9. Enabling Java applet support for Administration Console for Content Platform Engine on WebSphere Application Server 8
   If you need to use workflow-related applets in Administration Console for Content Platform Engine with version 8 (or higher) of WebSphere Application Server, you must disable HttpOnly session cookies. Because Administration Console for Content Platform Engine is collocated with Content Platform Engine, you must disable the cookies in the WebSphere profile that hosts Content Platform Engine. You can disable the cookies globally or just for your deployed application.
10. Creating the FileNet P8 domain
    You need to create a FileNet P8 domain to contain the object stores, storage areas, index areas, and other entities that you create.
11. Creating a database connection
    You must create a database connection so that Content Platform Engine can connect to the database that is used by object stores and isolated regions.
12. Creating the initial object store
    Object stores are used to store documents, workflows and other objects. The New Object Store wizard leads you through the steps required to create an object store.
13. Creating a workflow system
    To create a workflow system, you define an isolated region and its connection point. In addition, you can optionally customize the database storage parameters and configure email notification.
14. Connecting to a highly available Content Platform Engine
    The configuration of the Content Platform Engine connection in a highly available environment depends on the type of application you want to connect to the Content Platform Engine. You can configure administrative applications or user applications to connect to Content Platform Engine.
15. Verifying the Content Platform Engine system
    You can verify the Content Platform Engine system by using Administration Console for Content Platform Engine to create a folder in each object store.

Source: https://www.ibm.com/docs/en/filenet-p8-platform/5.5.x?topic=system-installing-configuring-content-platform-engine