To start or stop an instance of Component Manager from a script or command line (by using the web services transport):
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
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.
The taskman.login.config file is the JAAS Login Configuration file for the custom components. For more information, see Component Authentication Requirements.
Required by the Component Manager to define the file access security policy.
SSL support for Apache Axis.
The FileNet® service to use for trace logging.
Component Manager module access to the Process Java API.
Component Manager module access to the workflow system resource files.
Component Manager module access to the Content Engine API.
(Required by Apache Axis.) Component Manager module access to the Java API for XML Processing (JAXP) classes.
Component Manager module access to the Xerces XML parser.
(Required by Apache Axis.) Component Manager module access to the SAAJ (SOAP with Attachments API for Java) implementation.
Component Manager module access to the Java mail API.
(Required by Apache Axis.) Component Manager module access to the Apache Axis SOAP implementation.
(Required by Apache Axis.) Component Manager module access to the Apache Axis schema.
(Required by Apache Axis.) Component Manager module access to the WSDL4J (Web Services Description Language for Java Toolkit) implementation.
(Required by Apache Axis.) Component Manager module access to the classes that are part of the Apache Axis framework (used in invoking web services).
(Required by Apache Axis.) Component Manager module access to the classes that are part of the Apache Axis framework (used in invoking web services).
(Required by Apache Axis.) Component Manager module access to the JAX-RPC (Java API for XML-based RPC) implementation.
(Required by Apache Axis.) Component Manager module access to the JUDDI implementation (Java class library for a UDDI registry).
(Used by Apache Axis.) Implements WS-Addressing protocol for Apache Axis.
(Used by Apache Axis.) Implements WS-ReliableMessaging protocol for Apache Axis.
Component Manager module access to the Content Engine Java API runtime classes.
Component Manager module access to the CEOperations class.
Component Manager module access to properties provided to the CEOperations module.
Component Manager module access to properties provided to connection points.
Component Manager module access to the JAR file containing your customized components for inclusion in a workflow (by using Component Integrator).
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
Indicates the Component Manager parameters that are specified are indicated by the parameter names (for example, "/routerURL"), rather than positionally. This parameter has no value assignment.
Stops the specified Component Manager.
The name of the connection point to use.
The user must have Content Platform Engine administrative permissions.
The password for the specified user.
The name of the connection point to use.
The port number that is assigned to the Content Platform Engine Manager port (defaults to 32771).
The port number on which the Component Manager listens for incoming events (defaults to 32773).
Identifies the instance of the Component Manager. Note that the associated stop command must specify the same name that is used for the start command. This setting enables different Component Manager instances to use the same RMI port.
The component queues for the Component Manager. This setting allows you to configure the Component Manager specifically for specified queues (such as, for JAAS or JNDI). For example:
/queues=CE_Operations,CustomQ1