Verifying the Content Platform Engine deployment

You can verify that the Content Platform Engine deployment was successful by accessing the FileNet® P8 System Health page.

To verify the Content Platform Engine deployment:

1. Browse to the FileNet P8 System Health page:

   http://server:port/P8CE/Health

   where:

   server is the host name of the machine where Content Platform Engine is deployed.

   port is the WSI port used by the web application server on the machine 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/P8CE/Health.

   The following table lists an example address for your application server:

   Table 1. Example FileNet P8 System Health page address

   Application Server Type	Web Page Address
   IBM® WebSphere® Application Server	http://server:9080/P8CE/Health
   Oracle WebLogic Server	http://server:7001/P8CE/Health
   JBoss Application Server	http://server:8080/P8CE/Health

2. Verify that the FileNet P8 System Health page contains the Content Platform Engine instance host name and port number. The FileNet P8 System Health page provides status for the items in the following table.
   Tip: At this point, red icons appear on the page at the left of those entries that do not yet exist.

   Table 2. FileNet P8 System Health page contents

   Section	Description
   Domain	Displays the FileNet P8 domain name if a domain was found.
   Global Configuration Database	Verifies that the GCD contains a valid domain object, that the XA and non-XA data sources are defined and have unique names, and that the bootstrap user name and password are defined. If any of these verification tests fail, then the failed icon is displayed.
   Directory Configurations	Verifies that at least one directory service is configured and lists the number of configured directory service providers.
   PE Connection Points	Displays the number of Process Engine connection points.
   PE Isolated Regions	Displays the number of Process Engine isolated regions.
   Fixed Content Devices	Lists the number of fixed content devices (FCDs) For each FCD listed, there is at least one associated fixed storage area that is in the open state.
   Object Stores	Verifies that at least one object store exists and lists the number of object stores.
   Storage Areas	Verifies that at least one storage area is defined, lists the number of storage areas, and the status for each storage area, such as online or offline.
   Content Cache Areas	Displays the number of content cache areas.
   Sites	Verifies that at least one site is defined and lists the number of sites. For each site listed, at least one virtual server or server instance exists.

3. Optional: Bookmark the FileNet P8 System Health page web page address in your browser for later use.
4. 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 3. Example Content Platform Engine Startup Context (Ping Page) address

   Application 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

5. 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.
6. Optional: Bookmark the Content Platform Engine Startup Context (Ping Page) in your browser for later use.
7. (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.
8. (Highly available environments): Verify Content Platform Engine access through the load balancer.
   1. 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.
   2. Load the Content Platform Engine Startup Context page and verify that Content Platform Engine is accessed correctly by using the load balancer.
   3. 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.