Verifying the Content Platform Engine server status

You can verify that the Content Platform Engine server is up and running by accessing the Content Platform Engine Startup Context (Ping Page) or the Content Cortex System Health page.

com.filenet.MinimalPingPage=true

1. Verify the Content Platform Engine server status by using the Content Platform Engine Startup Context (Ping Page).
   1. Browse to the Content Platform Engine Startup Context (Ping Page):

      http://server:port/FileNet/Engine

      where:

      server is the host name of the server where Content Platform Engine is deployed. In a load-balanced environment, server is the name of one of the servers in the farm, not the virtual address of a load balancer.

      port is the HTTP port that is used by the application server where Content Platform Engine is deployed.

      The following table lists examples of addresses with default port numbers for supported application servers:

      Table 1. Examples of Content Platform Engine Startup Context (Ping Page) addresses

      Application server type	Web page address
      IBM® WebSphere® Application Server	http://myserver:9080/FileNet/Engine
      Oracle WebLogic Server	http://myserver:7001/FileNet/Engine

   2. 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 must match the build and version in the content_platform_engine_install_path/ce_version.txt file, where content_platform_engine_install_path is the location where the Content Platform Engine software is installed.
      • Verify that the values for the JDBC driver, the server instance, the operating system, and other properties match the values that are configured for Content Platform Engine.
2. Verify the Content Platform Engine server status by using the Content Cortex System Health page:
   1. Browse to the Content Cortex System Health page:

      http://server:port/P8CE/Health

      where:

      server is the host name of the server where Content Platform Engine is deployed. In a load-balanced environment, server is the name of one of the servers in the farm, not the virtual address of a load balancer.

      port is the HTTP port that is used by the application server where Content Platform Engine is deployed.

      The following table lists examples of addresses with default port numbers for supported application servers:

      Table 2. Examples of Content Cortex System Health page addresses

      Application server type	Web page address
      IBM WebSphere Application Server	http://myserver:9080/P8CE/Health
      Oracle WebLogic Server	http://myserver:7001/P8CE/Health

   2. Verify that the Content Cortex 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: Red icons are displayed on the page at the left of those entries that do not yet exist.

      Table 3. FileNet P8 System Health page contents

      Section	Description
      Domain	Displays the Content Cortex domain name if a domain was found.
      Global Configuration Database	Verifies that the global configuration database contains a valid domain object, that the XA and non-XA data sources are defined and have unique names, and that the Content Engine system 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 workflow system connection points.
      PE Isolated Regions	Displays the number of workflow system isolated regions.
      Fixed Content Devices	Lists the number of fixed content devices For each fixed content device that is 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.