If Content Platform Engine does
not deploy, you must verify that you have set up your system correctly.
Symptoms
Content Platform Engine does
not deploy.
Diagnosing the problem
When
Content Platform Engine fails
to deploy, verify the state of the deployment as follows:
- Browse to the following web page: http://server:port/FileNet/Engine
where server is the host name of the machine where
Content Engine Server is deployed and port is the
HTTP port used by the application server where Content Platform Engine is deployed. Example
web page addresses are shown in the following table:
Table 1. Example
web page addressesApplication Server Type |
Web Page Address |
WebSphere |
http://server:9080/FileNet/Engine |
WebLogic |
http://server:7001/FileNet/Engine |
JBoss |
http://server:8080/FileNet/Engine |
Tip: Bookmark the web page address in your browser.
- Verify your installation by checking the following information
on the web page:
- The value for the Startup Message key, which shows the Content Platform Engine build and version (for
example, dap501.134), must match the build and version in the cpe_install_path/ContentEngine/ce_version.txt file.
- The values for JDBC driver, server instance, operating system,
and so on, must match the values you chose when planning the FileNet® P8 installation.