You can verify that the Content Engine deployment was successful by accessing the IBM® FileNet® P8 System Health page.
http://server:port/P8CE/Health
where:
server is the host name of the machine where Content Engine is deployed.In a highly available environment, server is the name of one of the servers in the farm.
port is the WSI port used by the Web application server on the machine where Content Engine is deployed.
The following table lists an example address for your application server:
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 |
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. |
http://server:port/FileNet/Engine
where:
server is the host name of the machine where Content Engine is deployed. In a highly available environment, server is the name of one of the servers in the farm.
port is the HTTP port used by the application server where Content Engine is deployed.
The following table lists an example address for your application server:
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 |
http://ce_load_balancer:port/FileNet/Enginewhere 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 Engine on the load balancer or server running Content Engine.