After you have deployed and registered your application or applet, and, for Processors, added it to a workflow, the final development step is to run the application/applet to verify it is working correctly.
To run a Java™ application/applet, do the following:
javaw -classpath .;sample.jar;C:\your_directory\pe.jar; C:\your_directory\wcm.jar;C:\your_directory\pw.jar; %CLASSPATH% package_name.VWSampleStepApplication/hostName=host_name /routerNames=local_router/routerPorts=32771 /webApp=WEB_APP_NAME /queueName=queue_name /wobNumber=object_number
where sample.jar is the application/applet Java™ Archive (JAR) file, package_name is the package (directory structure in which the sample files reside), VWSampleStepApplication is the application name (in this case, the sample Java Step Processor), host_name is the name of the Application Engine or Process Engine host, local_router is the connection point name of the router on the Content Engine host, the FileNet default Java™ Remote Method Invocation (RMI) port for the router is 32771, WEB_APP_NAME is the FileNet web application (see the Note below), queue_name is the name of the workflow queue being accessed, and object_numberis the Work Object number (wobNumber) you retrieved in the preceding step.
Note: WEB_APP_NAME can be one of the following:
An example of a command statement to run a Java Step Processor for FileNet Workplace is as follows:
javaw -classpath .;C:\Developer Files\samples\vwpanel\sample.jar; C:\your_directory\pe.jar;C:\your_directory\wcm.jar; C:\your_directory\pw.jar; %CLASSPATH% samples\vwpanel\samplestep\VWSampleStepApplication /hostName=myhost /routerNames=vwrouter /routerPorts=32771 /webApp=WORKPLACE /queueName=InBox /wobNumber=B8D270F79636E1489BA9EC2DD9F7E950