Running the Application

Once you have deployed your application or applet, the final step is to run the application/applet to verify that it is working correctly. You run the application/applet on the Application Engine (for FileNet Workplace) or on the web/application server (for FileNet Web Services and Open Client) in a manner comparable to the way you run the sample Java Step Processor applications and applets supplied with the Process Development Environment.

To run a custom or default Java application/applet, use the following procedure (as an example, this procedure uses the unmodified sample Java Step and Launch Step Processor applications):

  1. If you have not already done so, using the Process Designer, create a workflow definition.
  2. If you have not already done so, still in Designer, validate and run the workflow.
  3. If you have not already done so, if appropriate (for example, for a Step Processor application/applet) add the application to the workflow.
  4. If you have not already done so, using the Process Administrator, retrieve a valid workflow object number (wobNumber) for an object in a queue from your workflow.
  5. Run the sample Java Step Processor application by entering a command similar to the following:

    javaw -classpath .;<sample.jar>;C:\<your directory >\eProcess.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 JAR file, the <package name > is the period-separated (".") directory structure in which the sample files reside, VWSampleStepApplication is the application name — in this case, the name of the sample Java Step Processor, <host name > is the name of the Application Engine server (for Workplace) or web server (for FileNet Web Services or Open Client) or Process Engine host, <local router > is the name of the router on the Application Engine or the web server or the Process Engine server, the FileNet default RMI port for the router (also for the PPM and IDM port) is 32771, <WEB APP NAME > is the FileNet web application (see Note), <queue name > is the name of the queue being accessed, and <object number > is the work object number (GUID) assigned to the work object by the Process Engine.

    Note Specify the <WEB APP NAME > according to the FileNet web application, as follows:

    For example, you might enter a command similar to the following for the sample Java Step Processor for FileNet Workplace:

    javaw -classpath .;C:\Developer Files\samples\vwpanel\sample.jar;C:\<your directory>
    \eProcess.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

    Note The FileNet default RMI port for the router (also for the Process Engine PPM and IDM port) is 32771.

  6. Similarly, you can run the sample Java Launch Step Processor application, for example for FileNet Workplace, by entering a command similar to:

    javaw -classpath .;<sample.jar>;C:\<your directory >\eProcess.jar;C:\<your directory >
    \wcm.jar;C:\<your directory>\pw.jar;%CLASSPATH%;<package name>\VWSampleLaunchApplication 
    /hostName=<host name> /routerNames=<local router > /routerPorts=32771 /idmPort=32771 
    /webApp=WORKPLACE /workflowDefinitionDocID=<>/mainAttachmentDocID=<> /subject=<subject>

    where <sample.jar> is the application JAR file, the <package name> is the period-separated (".") directory structure in which the sample files reside, <VWSampleLaunchApplication> is the application name — in this case, the name of the sample Java Launch Step Processor, <host name > is the name of the Application Engine server (for Workplace) or web server (for FileNet Web Services or Open Client) or Process Engine server host, <local router> is the name of the router on the Application Engine or the web server or the Process Engine server, WORKPLACE is the FileNet web application (modify according to which web application you are using), <> is the workflow definition ID, <> is the library ID assigned to the attachment, and <subject> is the subject specified for the step that launches the workflow.

    Note The FileNet default RMI port for the router (also for the Process Engine PPM and IDM port) is 32771.