You can configure the WebSphere application server to automatically start and stop Component Manager as a custom service on an Application Engine server using WebSphere. Alternatively, you can configure Process Task Manager to automatically start and stop Component Manager.
NOTE This configuration is not supported when Application Engine and Content Engine are collocated.
Before starting the procedures below, do the following steps:
To add and configure a Component Manager ExtensionMBean Provider
Classpath | Use the appropriate class path below, replacing all instances of <INSTALL_HOME> with the directory path where Application Engine is installed. In addition, add the jar files containing any custom adaptors for this Component Manager to the end. UNIX Windows |
Description | Enter a brief description, for example: Process Engine Component Manager MBean Provider |
Name | Enter a name, with no embedded spaces, to identify this provider, for example: ComponentManagerMBeanProvider |
To create the Component Manager Custom Service
Enable service at server startup |
Check this to automatically start the Component Manager custom service during application server startup. |
Classname | filenet.vw.integrator.base.VWComponentManagerCustomServiceMBean |
Display Name | Enter a unique descriptive name for the service, for example: Component Manager Service |
Description | Enter a description for the service, for example: Custom Service for Component Manager |
Classpath | Use the appropriate class path below, replacing all instances of <INSTALL_HOME> with the directory path where Application Engine is installed. (This is the same class path as used above, with the addition of the two "Router" jar files.) In addition, add the jar files containing any custom adaptors for this Component Manager to the end. UNIX Windows |
CELogin
{
filenet.vw.server.VWLoginModule required routerurl="ConnectionPoint";
com.filenet.wcm.toolkit.server.operations.util.CELoginModule required credTag=Clear;
};
PEWSLogin
{
com.filenet.wcm.toolkit.server.operations.util.CELoginModule required credTag=Clear;
};