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).
Before you begin
In a highly available
environment, verify that the
Content Platform Engine application
is running on the cluster or farm.
Procedure
To verify the Content Platform Engine deployment:
- Browse to the Content Platform Engine Startup Context (Ping
Page):
http://server:port/FileNet/Engine
where:
server is
the host name of the machine where Content Platform Engine is deployed.
port is
the HTTP port used by the application server where Content Platform Engine is deployed.
In a highly available environment, use the load
balanced virtual name for the server:port . For
example: http://virtual_server/FileNet/Engine.
The
following table lists an example address for your application server:
Table 1. Example Content Platform Engine Startup Context (Ping
Page) addressApplication Server Type |
Web Page Address |
IBM®
WebSphere® Application Server |
http://myserver:9080/FileNet/Engine |
Oracle WebLogic Server |
http://myserver:7001/FileNet/Engine |
JBoss Application Server |
http://myserver:8080/FileNet/Engine |
- Verify that the Content Platform Engine Startup Context (Ping
Page) contains the following information:
- Verify the value in the Startup Message key.
The Content Platform Engine build
and version (for example, dap511.097), must match the build and version
in the ce_install_path/ce_version.txt file,
where ce_install_path is the location where the Content Platform Engine software is installed.
- Verify that the values for JDBC driver, server instance, operating
system, and other properties match the values that you entered when
you configured Content Platform Engine.
- Optional: Bookmark the Content Platform Engine Startup
Context (Ping Page) in your browser for later use.
To
prevent unauthenticated users from accessing the Content Manager Ping
Page, see IBM
FileNet Content Manager Ping Page Authentication.
- (Highly available
environments) View the startup context name of the load-balancer or
proxy device to verify the functionality of the load-balanced environment,
or the name of the physical server to verify a single server.
- (Highly available
environments) Verify Content Platform Engine access
through the load balancer.
- Browse to:
http://ce_load_balancer:port/FileNet/Engine
where ce_load_balancer is
name of the load-balancer or proxy device to verify the functionality
of the load balanced environment and port is the
port used to access Content Platform Engine on
the load balancer or server running Content Platform Engine.
- Load the Content Platform Engine Startup
Context page and verify that Content Platform Engine is accessed correctly
by using the load balancer.
- View the startup context.name of the load-balancer or
proxy device to verify the functionality of the load-balanced environment,
or the name of the physical server to verify a single server.
Tip: - Depending on your configuration you can connect to the load balanced Content Platform Engine installation, and after
confirming that Content Platform Engine is
up and running, you can refresh your browser to have the load balancer
cycle through all managed nodes for verification.
- For JBoss Application Server,
this cyclic verification will not work because JBoss Application Server only reports the name
of the cluster and not the individual servers.