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.
Configuration is a multiple step process. You must provide information about your Content Platform Engine application environment, apply the settings by running the configuration tasks, and deploy the application. You can configure multiple instances before you deploy any of them, or you can configure and deploy one instance at a time.
You use Configuration Manager to define the
following information for the Content Platform Engine instance:
- Application server properties
Licensing for your installed products, including IBM® FileNet® Content Manager or IBM Content
Foundation, IBM Case
Foundation, and IBM Case
Manager 
- Java™ Database Connectivity (JDBC) data source properties for the global configuration database (GCD) database
- Java Database Connectivity (JDBC) data source properties for each object store database
- Directory service (LDAP) provider properties
- Content Platform Engine application login modules
- Content Platform Engine bootstrap properties
Remember the following
points when you prepare to configure Content Platform Engine:
- You can use Configuration Manager to configure and deploy the Content Platform Engine software that you installed on an application server only if Configuration Manager is running with the same application server.
- (WebSphere® Application Server only) For best results, configure no more than one Content Platform Engine application instance in a WebSphere profile.
- (WebSphere Application Server only) Configuration Manager can connect to a remote WebSphere Application Server stand-alone server or Network Deployment Manager if a matching WebSphere Application Server installation is available where Configuration Manager runs.
- If you need an accessible software version of Configuration Manager for people with disabilities, use the command-line version of Configuration Manager.
- If your system is HP-RISC, use the command-line version of Configuration Manager.
- You
must run the Configure Bootstrap and Text Extraction task and the
Deploy Application task after running the Choose Licenses task so
that the running application has the correct licensing information.
- If your FileNet P8 domain uses multiple non-managed application servers, then you must repeat all Configuration Manager tasks, except the Configure Bootstrap and Text Extraction task, on each non-managed application server. For the Configure Bootstrap and Text Extraction task, copy a single EAR file with the bootstrap settings to the Configuration Manager profiles that configure the other Content Platform Engine servers in the environment.
- Granting directory permissions to the Configuration Manager user
You must grant file and directory permissions to config_mgr_user, which is the user who runs Configuration Manager, to allow this user to run the program and create files in the ce_install_path/tools/configure directory. - Enabling Configuration Manager to connect to WebSphere Application Server 8.0 when FIPS is enabled
If you installed Content Platform Engine on WebSphere Application Server 8.0, and the application server is configured to adhere to Federal Information Processing Standards, you must enable Configuration Manager to connect to the application server. - Configuring Content Platform Engine instances
You can configure and deploy all of your Content Platform Engine application instances with Configuration Manager. A single Content Platform Engine application instance equates to one deployed application on your application server. You can use the graphical user interface or the command-line interface for Configuration Manager.