Configure Component Manager for WebLogic control

You can configure the WebLogic application server to automatically start and stop Component Manager on an Application Engine server using WebLogic. Alternatively, you can configure Process Task Manager to automatically start and stop Component Manager.

NOTES 

Before starting the procedures below, do the following:

To add and configure a Component Manager Servlet

  1. Deploy the Component Manager servlet by adding the following text to the web.xml file, located in <INSTALL_HOME>/FileNet/Workplace/WEB-INF.

    <servlet>
        <servlet-name>VWComponentManagerServlet</servlet-name>
        <servlet-class>filenet.vw.integrator.base.VWComponentManagerServlet</servlet-class>
        <load-on-startup>1</load-on-startup>
    </servlet>

  2. Add the Java™ Authentication and Authorization Service (JAAS) login information for JAAS Component Integrator adaptors to the /jaas/login.config.weblogic file. 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;
    };

  3. To set the proper security permissions for Component Manager adaptors, you must add security information to the weblogic.policy file. Consult your application server documentation to determine the location of this configuration file. For sample code, see Sample weblogic.policy file (Windows) or Sample weblogic.policy file (UNIX).
  4. Stop Component Manager if it is currently running, then restart the WebLogic application for the changes to take effect.