Content Engine Web Service Administration

The Content Engine Web Service is installed and enabled by default when you install the Content Engine.

Securing the Content Engine Web Service

If UsernameToken credentials are used, which require plaintext credentials for a user name and password, it is recommended that you configure your Content Engine server to use Secure Socket Layers (SSL) in order to protect user credentials. Once configured, the Content Engine Web Service will be able to send its XML SOAP messages using the secure HTTPS protocol. For more information, see the "Set Up Content Engine and Client Transport SSL Security" topic in the IBM® FileNet® P8 Platform Installation and Upgrade Guide for this release, available on the IBM web site Product Documentation for FileNet P8 Platform.

If Kerberos credentials are used with the Content Engine Web Service, it is not necessary to use SSL to protect user credentials. However, SSL might still be desirable if data privacy is required.

Systinet Server Console

Once you have installed the Content Engine Web Service, you should start the Systinet Server Console and change its default password. You can access the Systinet Server Console at the following URL: http://<hostname>:<port>/wsi/admin/console, where <hostname> is the name of the Content Engine host machine and <port> is the port number assigned to the Content Engine application server. For example: http://localhost:7001/wsi/admin/console.

The default user criteria for the Systinet Server Console are:

The default user criteria should be changed immediately after the initial login. The admin account can create additional accounts, and grant privileges to each web service that exists on the Systinet Server host. The user accounts are stored in the Systinet User Store located on each Systinet Server host. These accounts have no relationship to accounts that are defined in the enterprise directory service or on the local operating system. You can set up a Systinet Security Domain to create a logical grouping of Systinet servers that use the same user database. Refer to the Systinet Server for Java™ documentation for more information.

The Systinet Server is used internally by the Content Engine to support the Content Engine Web Service. Avoid making additional modifications to the Systinet Server's default settings.