Content Platform Engine failed to deploy
If Content Platform Engine does not deploy, you should verify your configuration settings and make the appropriate changes.
Symptoms
Content Platform Engine does not deploy.Causes
- WebSphere
- Incorrect environment variable setting to the JDBC driver path or the default authentication provider is set to the default value of Required. When this value is required, the directory server that you specified during installation must exist as a WebSphere default authentication provider.
- WebLogic
- Incorrect CLASSPATH setting in the startWebLogic.cmd/.sh startup script for the JDBC driver.
Resolving the problem
- WebSphere
- Verify the WebSphere environment variables for the JDBC drivers are at both the cell and node levels. Launch the application server console and test the data sources and the connection pools. Verify that you are using the latest supported JDBC drivers. For a list of the currently supported drivers, see the IBM® FileNet® P8 system requirements web page.
- WebLogic
- Launch the application server console and test the data sources and the connection pools. Verify that you are using the latest supported JDBC drivers. For a list of the currently supported drivers, see the IBM FileNet P8 system requirements web page.