FileNet P8 Application Engine, Version 5.2

Starting and Stopping a Component Manager Instance

Note: Component Manager is configured to use the web services transport by default. The following instructions assume the web services transport. See Configuring Component Manager for the Enterprise JavaBeans (EJB) Transport for this configuration information.

To start or stop an instance of Component Manager from a script or command line (using the web services transport):

Ensure that your system is properly configured for your Java™ Runtime Environment (JRE). See Installing the JDK.
Ensure the appropriate connection point is configured. See Connection Points.
Edit the classpath that you use for Component Manager to include the WcmApiConfig.properties located in the filenet_installation_directory\AE\Router\lib directory.

Use one of the following commands (line breaks inserted for readability) to start or stop Component Manager. The only distinction between the stop and start commands are the switches specified for Component Manager (filenet.vw.integrator.base.VWComponentManager).

Note: Entries must be in the order indicated.

To start a Component Manager instance:

java "-Dinitial_context_factory"
      "-Djava.security.auth.login.config=filenet_installation_directory/AE/Router/taskman.login.config"
      "-Djava.security.policy=filenet_installation_directory/AE/Router/taskman.policy"
      -Dorg.apache.axis.components.net.SecureSocketFactory=filenet.ws.utils.jsse.FnJSSESocketFactory 
      -Dfilenet.vw.base.logging.ServiceName=VWServicesAE 
      -Xrs 
      -cp 
      "filenet_installation_directory/AE/Router/lib/pe.jar;
       filenet_installation_directory/AE/Router/lib/peResources.jar;
       filenet_installation_directory/AE/CE_API/lib/Jace.jar;
       filenet_installation_directory/AE/Router/lib/xml-apis.jar;
       filenet_installation_directory/AE/Router/lib/xercesImpl.jar;
       filenet_installation_directory/AE/Router/lib/saaj.jar;
       filenet_installation_directory/AE/Router/lib/mailapi.jar;
       filenet_installation_directory/AE/Router/lib/axis.jar;
       filenet_installation_directory/AE/Router/lib/axis-schema.jar;
       filenet_installation_directory/AE/Router/lib/wsdl4j.jar;
       filenet_installation_directory/AE/Router/lib/commons-discovery.jar;
       filenet_installation_directory/AE/Router/lib/commons-logging.jar;
       filenet_installation_directory/AE/Router/lib/jaxrpc.jar;
       filenet_installation_directory/AE/Router/lib/juddi.jar;
       filenet_installation_directory/AE/Router/lib/addressing.jar;
       filenet_installation_directory/AE/Router/lib/Sandesha.jar;
       filenet_installation_directory/Workplace/WEB-INF/lib/p8ciops.jar;
       filenet_installation_directory/Workplace/download/wcm.jar;
       filenet_installation_directory/AE/Router/lib;
       filenet_installation_directory/Workplace/WEB-INF;
       your_custom_component_jar;
       appserver_jars_for_jms;"
       filenet.vw.integrator.base.VWComponentManager 
        /named
        /routerURL connectionPoint 
        /userName username 
        /password password 
        /registryPort registryPort 
        /eventPort eventPort 
        /registryName componentManagerName 
        /queues componentQueues

To stop a Component Manager instance:

java "-Dinitial_context_factory"
      "-Dwasp.location=filenet_installation_directory/AE/Router/../CE_API/wsi"
      "-Djava.security.auth.login.config=filenet_installation_directory/AE/Router/taskman.login.config"
      "-Djava.security.policy=filenet_installation_directory/AE/Router/taskman.policy"
      -Dorg.apache.axis.components.net.SecureSocketFactory=filenet.ws.utils.jsse.FnJSSESocketFactory 
      -Dfilenet.vw.base.logging.ServiceName=VWServicesAE 
      -Xrs 
      -cp "filenet_installation_directory/AE/Router/lib/pe.jar;
          filenet_installation_directory/AE/Router/lib/peResources.jar;
          filenet_installation_directory/AE/CE_API/lib/Jace.jar;
          filenet_installation_directory/AE/Router/lib/xml-apis.jar;
          filenet_installation_directory/AE/Router/lib/xercesImpl.jar;
          filenet_installation_directory/AE/Router/lib/saaj.jar;
          filenet_installation_directory/AE/Router/lib/mailapi.jar;
          filenet_installation_directory/AE/Router/lib/axis.jar;
          filenet_installation_directory/AE/Router/lib/axis-schema.jar;
          filenet_installation_directory/AE/Router/lib/wsdl4j.jar;
          filenet_installation_directory/AE/Router/lib/commons-discovery.jar;
          filenet_installation_directory/AE/Router/lib/commons-logging.jar;
          filenet_installation_directory/AE/Router/lib/jaxrpc.jar;
          filenet_installation_directory/AE/Router/lib/juddi.jar;
          filenet_installation_directory/AE/Router/lib/addressing.jar;
          filenet_installation_directory/AE/Router/lib/Sandesha.jar;
          filenet_installation_directory/Workplace/WEB-INF/lib/p8ciops.jar;
          filenet_installation_directory/Workplace/download/wcm.jar;
          filenet_installation_directory/AE/Router/lib;
          filenet_installation_directory/Workplace/WEB-INF;
          your_custom_component_jar;
          appserver_jars_for_jms;"
       filenet.vw.integrator.base.VWComponentManager 
        /named 
        /unbind
        /registryPort registryPort 
        /registryName componentManagerName

Descriptions

-Dinitial_context_factory
Required only if you use a Java Message Service (JMS) queue. Refer to the package pathname for the Java Naming and Directory Interface (JNDI) InitialContextFactory information.
-Djava.security.auth.login.config=filenet_installation_directoryAE/Router/taskman.login.config
The taskman.login.config file is the JAAS Login Configuration file for the custom component(s). See Component Authentication Requirements for more information.
-Djava.security.policy=filenet_installation_directoryAE/Router/taskman.policy
Required by the Component Manager to define the file access security policy.
-Dorg.apache.axis.components.net.SecureSocketFactory=filenet.ws.utils.jsse.FnJSSESocketFactory
SSL support for Apache Axis.
-Dfilenet.vw.base.logging.ServiceName=VWServicesAE
The FileNet® service to use for trace logging.
- cp
- filenet_installation_directory/AE/Router/lib/pe.jar
  Component Manager module access to the Process Engine API.
- filenet_installation_directory/AE/Router/lib/peResources.jar
  Component Manager module access to Process Engine resource files.
- filenet_installation_directory/AE/CE_API/lib/Jace.jar
  Component Manager module access to the Content Engine API.
- filenet_installation_directoryAE/Router/lib/xml-apis.jar
  (Required by Apache Axis.) Component Manager module access to the Java API for XML Processing (JAXP) classes.
- filenet_installation_directoryAE/Router/lib/xercesImpl.jar
  Component Manager module access to the Xerces XML parser.
- filenet_installation_directory/AE/Router/lib/saaj.jar
  (Required by Apache Axis.) Component Manager module access to the SAAJ (SOAP with Attachments API for Java) implementation.
- filenet_installation_directory/AE/Router/lib/mailapi.jar
  Component Manager module access to the Java mail API.
- filenet_installation_directory/AE/Router/lib/axis.jar
  (Required by Apache Axis.) Component Manager module access to the Apache Axis SOAP implementation.
- filenet_installation_directory/AE/Router/lib/axis-schema.jar
  (Required by Apache Axis.) Component Manager module access to the Apache Axis schema.
- filenet_installation_directory/AE/Router/lib/wsdl4j.jar
  (Required by Apache Axis.) Component Manager module access to the WSDL4J (Web Services Description Language for Java Toolkit) implementation.
- filenet_installation_directory/AE/Router/lib/commons-discovery.jar
  (Required by Apache Axis.) Component Manager module access to the classes that are part of the Apache Axis framework (used in invoking web services).
- filenet_installation_directory/AE/Router/lib/commons-logging.jar
  (Required by Apache Axis.) Component Manager module access to the classes that are part of the Apache Axis framework (used in invoking web services).
- filenet_installation_directory/AE/Router/lib/jaxrpc.jar
  (Required by Apache Axis.) Component Manager module access to the JAX-RPC (Java API for XML-based RPC) implementation.
- filenet_installation_directory/AE/Router/lib/juddi.jar
  (Required by Apache Axis.) Component Manager module access to the JUDDI implementation (Java class library for a UDDI registry).
- filenet_installation_directory/AE/Router/lib/addressing.jar
  (Used by Apache Axis.) Implements WS-Addressing protocol for Apache Axis.
- filenet_installation_directory/AE/Router/lib/Sandesha.jar
  (Used by Apache Axis.) Implements WS-ReliableMessaging protocol for Apache Axis.
- filenet_installation_directory/Workplace/download/wcm.jar
  Component Manager module access to the Content Engine Java API runtime classes.
- filenet_installation_directory/Workplace/WEB-INF/lib/p8ciops.jar
  Component Manager module access to the CEOperations class.
- filenet_installation_directory/Workplace/WEB-INF
  Component Manager module access to properties provided to the CEOperations module.
- filenet_installation_directory/AE/Router/lib
  Component Manager module access to properties provided to connection points.
- your_custom_component_jar
  Component Manager module access to the JAR file containing your customized component(s) for inclusion in a workflow (using Component Integrator).
- appserver_jars_for_jms
  Component Manager module access to the required libraries for your application server. See required libraries for the JNDI configuration.
```
filenet.vw.integrator.base.VWComponentManager 
    /named 
    /unbind
    /routerURL connectionPoint 
    /userName username 
    /password password 
    /registryPort registryPort 
    /eventPort eventPort 
    /registryName componentManagerName 
    /queues componentQueues
```
- /named
  Indicates the Component Manager parameters specified are indicated by the parameter names (for example, "/routerURL"), rather than positionally. This parameter has no value assignment.
- /unbind
  Stops the specified Component Manager.
- routerURL
  The name of the connection point to use.
- username
  The user must have Process Engine administrative permissions.
- password
  The password for the specified user.
- connectionPoint
  The name of the connection point to use.
- registryPort
  The port number assigned to the Process Engine Manager port (defaults to 32771).
- eventPort
  The port number on which the Component Manager listens for incoming events (defaults to 32773).
- componentManagerName
  Identifies the instance of the Component Manager. Note that the associated stop command will need to specify the same name used for the start command. This setting enables different Component Manager instances to use the same RMI port.
- componentQueues
  The component queue(s) for the Component Manager. This allows you to configure the Component Manager specifically for specified queue(s) (such as, for JAAS or JNDI). For example:
```
 
    /queues=CE_Operations,CustomQ1
```