To start the Component Manager from a script or command window, execute the following procedure:
From a command window on the Application Engine, enter the following, as a single command. (Note that line breaks have been inserted for readability.)
java -D<InitialContextFactory for use with JMS Adapters>
-Djava.security.auth.login.config=<FileNet Installation Directory>\Router\taskman.login.config
-Djava.security.policy=<FileNet Installation Directory>\Router\taskman.policy
-classpath "<FileNet Installation Directory>\Workplace\WEB-INF\lib\eprocess.jar;
<FileNet Installation Directory>\Workplace\download\wcm.jar;
<FileNet Installation Directory>\Workplace\WEB-INF\lib\jaas.jar;
<FileNet Installation Directory>\Workplace\WEB-INF\lib\p8ciops.jar;
<FileNet Installation Directory>\Workplace\WEB-INF;
[your component's jar file];
[application server jar files for JMS]"
filenet.vw.integrator.base.VWComponentManager
<routerURL><username> <password>
[registryPort][eventPort]
To stop the Component Manager from a script or command window on the Application Engine, enter the following :
java -classpath "<FileNet Installation Directory>\Workplace\WEB-INF\lib\eprocess.jar" filenet.vw.integrator.base.VWComponentManager
/named /registryPort=<registryPort> unbind
Notes
"-D<InitialContextFactory for use with JMS Adapters>"
is required only if you use a JMS queue. Using JMS with the Component Integrator
is described in the topic, Building a Component Integrator-based Work Performer,
in the Help for Process Development document. The InitialContextFactory
file that applies to your application server is shown in the table of JNDI
Initial Context Factories in that topic. -Djava.security.auth.login.config=<FileNet
Installation Directory>\Router\taskman.login.config"
, the taskman.login.config
file is described in the topic, Component Authentication Example, in the Help
for Process Development document. "-Djava.security.policy=<FileNet Installation
Directory>\Router\taskman.policy"
is required by the Component
Manager to define file access security policy. For information about file
security, see the topic, Security Overview, in the Help for Security
document.<FileNet Installation Directory>\Workplace\WEB-INF\lib\eprocess.jar
classpath, the Component Manager module accesses the Process Engine API. <FileNet Installation Directory>\Workplace\download\wcm.jar
classpath file, the Component Manager module accesses the Content Engine
API and required XML parser. <FileNet Installation Directory>\Workplace\WEB-INF\lib\jaas.jar
classpath file, the Component Manager module accesses files used for authentication.
<FileNet Installation Directory>\Workplace\WEB-INF\lib\p8ciops.jar
classpath file, the Component Manager module accesses the CEOperations class.
Reference information for the CEOperations class is provided on the Filenet
P8 Platform Documentation CD, in the file .../developer_help/component_integrator_ce_ops/javadocs/index.html.
<FileNet Installation Directory>\Workplace\WEB-INF
classpath directory, the Component Manager module accesses properties that
are provided to the CEOperations module. [your component's jar file]
classpath file, the Component
Manager module accesses a JAR file containing your customized modules, for
inclusion in a workflow with the Component Integrator.
[application server jar files for JMS]
classpath
files, the Component Manager module accesses the files that apply to your
application server, as shown in the table of JNDI Initial Context Factories
in the topic, Building a Component Integrator-based Work Performer, in the
Help for Process Development document.
routerURL
" entry must match the Process Router
specified as your router site preference on the Application Engine. For details,
see the topic, Router, in the Help for Site Preferences document. [registryPort]
and [eventPort]
entries, see the topic, Component Manager general properties, in the Help
for Process Task Manager document. From a command window on your Web Server, enter the following, as a single command. (Note that line breaks have been inserted for readability.)
java -Djava.security.auth.login.config=<FileNet Installation Directory>\IDM\PWBin\taskman.login.config
-Djava.security.policy=<FileNet Installation Directory>\IDM\PWBin\taskman.policy
-classpath "<FileNet Installation Directory>\IDM\Web\IDMWS\Redist\WF_Extras\pw.jar;
<FileNet Installation Directory>\IDM\PWBin\jaas.jar;
[your component's jar file]"
filenet.vw.integrator.base.VWComponentManager
<routerURL><username> <password>
[registryPort][eventPort]
To stop the Component Manager from a script or command window on your Web Server, enter the following :
java -classpath "<FileNet Installation Directory>\IDM\Web\IDMWS\Redist\WF_Extras\pw.jar" filenet.vw.integrator.base.VWComponentManager
/named /registryPort=<registryPort> unbind
Notes
-Djava.security.auth.login.config=<FileNet
Installation Directory>\IDM\PWBin\taskman.login.config"
, the
taskman.login.config file is described in the topic, Component Authentication
Example, in the Help for Process Development document. "-Djava.security.policy=<FileNet Installation
Directory>\IDM\PWBin\taskman.policy"
is required by the Component
Manager to define file access security policy. For information about file
security, see the topic, Security Overview, in the Help for Security
document.<FileNet Installation Directory>\IDM\Web\IDMWS\Redist\WF_Extras\pw.jar
classpath, the Component Manager module accesses the Process Engine API. <FileNet Installation Directory>\IDM\PWBin\jaas.jar
classpath file, the Component Manager module accesses files used for authentication.
[your component's jar file]
classpath file, the Component
Manager module accesses a JAR file containing your customized modules, for
inclusion in a workflow with the Component Integrator.routerURL
" entry must match the Process Router
specified as your router site preference. For details, see the topic, Router,
in the Help for Site Preferences document. [registryPort]
and [eventPort]
entries, see the topic, Component Manager general properties, in the Help
for Process Task Manager document.