![]() ![]() |
|
Open Client Developer's Guide | |
Search | Index | Glossary | | |
![]() |
|
![]() |
![]() |
![]() |
Starting a Local Process RouterA 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):
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. |
![]() |
|