IBM FileNet P8, Version 5.2.1            

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.
JBoss
Missing JDBC jar file in the library directory of the JBoss profile.

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.
Create a WebLogic default authentication provider with the same name as directory server user or change the Provider Control Flag to Sufficient.
JBoss
Verify that the JDBC driver is copied to the lib directory of the JBoss profile. For example: jboss_installation_directory\server\server1 lib. Verify that JBoss is started.


Last updated: October 2015
p8pct025.htm

© Copyright IBM Corporation 2015.