Configure Component Manager for WebSphere control

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:

To add and configure a Component Manager ExtensionMBean Provider

  1. In the WebSphere Administrative Console, navigate to the Extension MBean Providers tab for your server:
    1. In the left pane, navigate to Servers > Application Servers, then select the name of your server, for example, server1.
    2. Under Server Infrastucture, navigate to Administration > Administration Services.
    3. In the Configuration tab, under Additional Properties, select Extension MBean Providers.
  2. Create a new provider:
    1. Click New, and enter the following:

      Classpath

      Use the appropriate classpath below, replacing all instances of <INSTALL_HOME> with the directory path where Application Engine is installed. In addition, add the jar file(s) containing any custom adaptors for this Component Manager to the end.

      UNIX
      <INSTALL_HOME>/FileNet/AE/Workplace/WEB-INF/lib/pe.jar:
      <INSTALL_HOME>/FileNet/AE/Workplace/WEB-INF:
      <INSTALL_HOME>/FileNet/AE/Workplace/WEB-INF/lib/Jace.jar:
      <INSTALL_HOME>/FileNet/AE/Workplace/WEB-INF/lib/activation.jar:
      <INSTALL_HOME>/FileNet/AE/Workplace/WEB-INF/lib/p8ciops.jar:
      <INSTALL_HOME>/FileNet/AE/Workplace/WEB-INF/lib/javaapi.jar:
      <INSTALL_HOME>/FileNet/AE/Workplace/WEB-INF/lib/p8toolkit.jar:
      <INSTALL_HOME>/FileNet/AE/Workplace/WEB-INF/lib/p8workplace.jar:
      <INSTALL_HOME>/FileNet/AE/Workplace/WEB-INF/lib/log4j-1.2.13.jar:
      <INSTALL_HOME>/FileNet/AE/Workplace/WEB-INF/lib/axis.jar:
      <custom_adaptor_jar_files>

      Windows
      <INSTALL_HOME>/FileNet/AE/Workplace/WEB-INF/lib/pe.jar;
      <INSTALL_HOME>/FileNet/AE/Workplace/WEB-INF;
      <INSTALL_HOME>/FileNet/AE/Workplace/WEB-INF/lib/Jace.jar;
      <INSTALL_HOME>/FileNet/AE/Workplace/WEB-INF/lib/activation.jar;
      <INSTALL_HOME>/FileNet/AE/Workplace/WEB-INF/lib/p8ciops.jar;
      <INSTALL_HOME>/FileNet/AE/Workplace/WEB-INF/lib/javaapi.jar;
      <INSTALL_HOME>/FileNet/AE/Workplace/WEB-INF/lib/p8toolkit.jar;
      <INSTALL_HOME>/FileNet/AE/Workplace/WEB-INF/lib/p8workplace.jar;
      <INSTALL_HOME>/FileNet/AE/Workplace/WEB-INF/lib/log4j-1.2.13.jar;
      <INSTALL_HOME>/FileNet/AE/Workplace/WEB-INF/lib/axis.jar;
      <custom_adaptor_jar_files>

      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
    2. Click Apply to add the new provider to your local configuration.
  3. Define a new MBean for the Component Manager provider:
    1. Click the extensionMBeans link under Additional Properties. Click New and enter the following:
      • descriptorURIComponentManagerMBean.xml.
      • typeFnpeCM
    2. Click Apply to add the new provider to your local configuration. Click Save in the Messages pane, then click Save again to save your workspace changes to the master configuration.

To create the Component Manager Custom Service

  1. In the WebSphere Administrative Console, navigate to the Extension MBean Providers tab for your server:
    1. In the left pane, navigate to Servers > Application Servers, then select the name of your server, for example, server1.
    2. Under Server Infrastucture, navigate to Administration > Custom Services.
  2. Create a Component Manager custom service definition:
    1. Click New, and enter the following:

      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 classpath below, replacing all instances of <INSTALL_HOME> with the directory path where Application Engine is installed. (This is the same classpath as used above, with the addition of the two "Router" jar files.) In addition, add the jar file(s) containing any custom adaptors for this Component Manager to the end.

      UNIX
      <INSTALL_HOME>/FileNet/AE/Workplace/WEB-INF/lib/pe.jar:
      <INSTALL_HOME>/FileNet/AE/Workplace/WEB-INF:
      <INSTALL_HOME>/FileNet/AE/Workplace/WEB-INF/lib/Jace.jar:
      <INSTALL_HOME>/FileNet/AE/Workplace/WEB-INF/lib/activation.jar:
      <INSTALL_HOME>/FileNet/AE/Workplace/WEB-INF/lib/p8ciops.jar:
      <INSTALL_HOME>/FileNet/AE/Workplace/WEB-INF/lib/javaapi.jar:
      <INSTALL_HOME>/FileNet/AE/Workplace/WEB-INF/lib/p8toolkit.jar:
      <INSTALL_HOME>/FileNet/AE/Workplace/WEB-INF/lib/p8workplace.jar:
      <INSTALL_HOME>/FileNet/AE/Workplace/WEB-INF/lib/log4j-1.2.13.jar:
      <INSTALL_HOME>/FileNet/AE/Workplace/WEB-INF/lib/axis.jar:
      <INSTALL_HOME>/FileNet/AE/Router/lib/addressing.jar:
      <INSTALL_HOME>/FileNet/AE/Router/lib/Sandesha.jar:
      <custom_adaptor_jar_files>

      Windows
      <INSTALL_HOME>/FileNet/AE/Workplace/WEB-INF/lib/pe.jar;
      <INSTALL_HOME>/FileNet/AE/Workplace/WEB-INF;
      <INSTALL_HOME>/FileNet/AE/Workplace/WEB-INF/lib/Jace.jar;
      <INSTALL_HOME>/FileNet/AE/Workplace/WEB-INF/lib/activation.jar;
      <INSTALL_HOME>/FileNet/AE/Workplace/WEB-INF/lib/p8ciops.jar;
      <INSTALL_HOME>/FileNet/AE/Workplace/WEB-INF/lib/javaapi.jar;
      <INSTALL_HOME>/FileNet/AE/Workplace/WEB-INF/lib/p8toolkit.jar;
      <INSTALL_HOME>/FileNet/AE/Workplace/WEB-INF/lib/p8workplace.jar;
      <INSTALL_HOME>/FileNet/AE/Workplace/WEB-INF/lib/log4j-1.2.13.jar;
      <INSTALL_HOME>/FileNet/AE/Workplace/WEB-INF/lib/axis.jar;
      <INSTALL_HOME>/FileNet/AE/Router/lib/addressing.jar;
      <INSTALL_HOME>/FileNet/AE/Router/lib/Sandesha.jar;
      <custom_adaptor_jar_files>

    2. Click Apply to add the new Component Manager Custom Service definition to the configuration. Click Save in the Messages pane, then click Save again to save your workspace changes to the master configuration.
  3. Create custom properties for the custom service.
    1. From the Custom Services page, select the custom service you just created by clicking on its Display Name. Under Additional Properties, click Custom Properties.
    2. Create a custom property to identify the Component Manager port:
      1. Click New, and enter the following:
        • NamepeCMPort
        • Value – The registry port you configured in Process Task Manager, for example:
          32771.
      2. Save your changes to the master configuration. (Click Apply. Then click Save in the Messages pane, then click Save again.)
    3. Create a custom property to identify the Component Manager connection point:
      1. Click New, and add the following:
        • NamepeRouterURL.
        • Value – The connection point you configured in Process Task Manager.
      2. Save your changes to the master configuration. (Click Apply. Then click Save in the Messages pane, then click Save again.)
    4. Create a custom property to identify the Component Manager location of the P8BPMWSBroker.properties file:
      1. Click New, and add the following:
        • Namep8BPMWSBroker
        • Value – The location of the P8BPMWSBroker.properties file. For example:
          c:/Program Files/FileNet/AE/Workplace/WEB-INF
      2. Save your changes to the master configuration. (Click Apply. Then click Save in the Messages pane, then click Save again.)
  4. Add the Java™ Authentication and Authorization Service (JAAS) login information for JAAS Component Integrator adaptors to the application server's authentication configuration file.
    1. Add the JAAS login information to the jaas.conf.WebSphere file installed during the Application Engine installation. You can use the sample code below, replacing the text ConnectionPoint with the name of the actual connection point used by Component Manager.

      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;
      };

    2. Copy the entire content of jaas.conf.WebSphere and append it to the authentication configuration file wsjaas.conf. Consult your application server documentation to determine the location of this configuration file.
  5. Stop Component Manager if it is currently running, then restart the WebSphere application for the changes to take effect.