Skip navigation FileNet logo
  Open Client Developer's Guide
  Search  |  Index  |  Glossary   |  
Open menu Overview
Open menu Open Client Architecture
Close menu Developing for Process
  Open menu Process Overview
  Close menu Preparing for Development
    Setup Checklist
    PJAC
    PJAC Files
    Close menu Installing the PDE
      Configuring the JRE
      Starting a Local Process Router
      Close menu Setting Up for JiGlue
        JiGlueand ASP.NET Issues
        Configuring the JiGlue COM Bridge
        JiGlue Java-COM Data Types
        JiGlue Programming Guidelines
  Open menu HTML Step and Launch Processors
  Java Processors
  Component-Integrator Work Performer
  Open menu Deploying Process Applications
Open menu Error and Exception Handling
Open menu Customizing the Framework
Globalization / Localization
Open menu General Information
   

Starting a Local Process Router

A Process router is a Java Remote Method Invocation (RMI) communication bridge. You need not start a local router if a Process Router is running on either the Open Client Web server or the Primary Process Engine. You can pass the host name, port number, and router name as part of the VWSession.logon() router_URL parameter. Starting a local router allows you to observe the RMI communication between a development system and a workflow server more closely.

This procedure assumes you have already installed and configured the Java SDK (see above) to use the Process APIs. This procedure also assumes you are using the appropriate JDK — in the example shown, the Sun Microsystems JDK 1.3.1 on a Windows platform.

The following procedure uses the Task Manager to start a local router (treat all entries as case-sensitive; for information on using the Task Manager, see Help for Task Manager on the Process Documentation for FileNet Image Manager CD):

  1. Open a command prompt and enter the following command (modify for the appropriate JDK):

    C:\jdk1.3.1\bin\javaw.exe -classpath filenet.vw.router.VWRouterAdminApp

  1. Once the Router Administration window displays, click Start.
  2. In the router dialog box, enter a name for the local instance of the router; for example, myrouter.
  3. Enter the name of the workflow server running the Process Engine; for example, if the name of the Process Engine server is "myserver", enter myserver.
  4. Enter a valid administrative user name. (When running the samples, for example, you should be a Process Services administrative user.)
  5. Enter the password for the specified user.
  6. Enter an isolated region number. This number can be from 1 to 999 and should correspond to the initialized isolated region you are using for development. While it is possible to do so, you should not run the samples (or other Process applications in development) in an isolated region used for either production or other development work.
  7. Click OK.

    Once the message appears stating that the local router has started, you can use it to communicate with a Process Engine server.

    Tip: On Windows 2000 systems, you may want to create a short-cut to launch the Process Router. In the short-cut properties dialog box, enter the command shown in the first step in the target field. Specify the directory containing the Process API samples as the start directory. (Specifying the directory containing the API samples creates and updates the router trace files in that directory, which can be useful for debugging when you start modifying the sample code.)

The first time you attempt to connect to a session, a vwapi.txt file is created in the root directory of the disk on which the application is being run. The file contains a complete list of all session transactions handled by the router. Be aware that if you don't start the Process router, the vwapi.txt file will grow rapidly (as duplicate error messages are appended to it) until you terminate the sample application.