You must complete the post-deployment web application server
configuration before you can put a FileNet® P8 system into production.
Procedure
To complete the post-deployment configuration:
- Log in to the WebSphere® Application
Server administrative
console.
- Navigate to .
- If you configured Content Platform Engine to
use federated user repositories, complete the following substeps:
- Click Configure.
- Specify a unique user for the Primary administrative
user name. Use the short name. The user name
must exist in one of the realms and must be unique.
- Specify the Server user identity.
You can select Automatically generated server identity or
specify a name that exists in one of the repositories. The
user name must be unique.
- Save your changes to the master configuration.
- Configure security settings:
Important: Enabling the security settings must be done manually.
Deploying Content Platform Engine does
not enable or check these settings.
- Enable WebSphere administrative
security to secure the WebSphere administration
console.
- Disable Java™ 2
security. Otherwise, Content Platform Engine cannot start or process
requests.
- Complete the following substeps to verify that the HTTP
port used by the Content Platform Engine is
defined in the default_host host aliases table. By default
the host alias is defined only for HTTP port 9080. If you are using
any other HTTP port (common in network deployments) you must add that
port to the list of host aliases for default_host.
- Navigate to .
- Add your HTTP port in the host aliases table.
- Click OK, and then click Save.
- Restart the WebSphere application
server instance where Content Platform Engine is
deployed, as shown in the following table. .
Option |
Description |
Stand-alone server |
Stop and start the application server instance. |
Network Deployment |
Stop and start the application server instance
where Content Platform Engine is deployed,
including the Deployment Manager and all managed nodes. |
Cluster |
Stop and start the cluster, as well as the deployment manager
and all of its managed nodes. |