Before you can develop Java applications or applets, or compile and run the out-of-the-box Java samples shipped with Panagon eProcess, you must first install and configure the appropriate Java SDK on your development system.
For the current eProcess release:
Note Versions used may be updated. For the latest information on which versions of software (including JDKs) are supported for Panagon eProcess Web Services, Web WorkFlo and WorkFlo Services, see the eProcess Compatibility/Dependency/Server Matrix document, located at http://www.css.filenet.com web site (go to Product Info > Panagon > eProcess > Compatibility and Dependency).
The Java sample applications supplied with the product are provided in the pw.jar file. However, there are known issues associated with adding pw.jar to your system CLASSPATH. These issues and the recommended Java SDK configuration procedure are described in this topic as follows:
On your development system, perform the following steps to configure your system to use the eProcess APIs:
Note On Windows, the default installation directory is <drive>...\jdk1.3.1; on Solaris <drive>:/j2sdk1.4.0 (for JDK 1.4.0), etc. (The remainder of this procedure assumes a Windows platform.) As a reminder, remember to add the JDK to your PATH variable. If you are planning to use Panagon eProcess to develop Java applications with the JiGlue COM Bridge, you must install the Java SDK in the default directory (for information on configuring the JiGlue COM Bridge on a development system, see Configure the COM Bridge).
Refer to Install Panagon eProcess Toolkit for information on locating the \Developer Files directory on the CD (as well as additional information on its contents).
A known issue associated with adding the pw.jar file to the CLASSPATH is that this can cause security conflicts when attempting to run the out-of-the-box Java client applications on your development system. The conflict is caused when the Panagon eProcess Web WorkFlo server sends the correct pw.jar, but the CLASSPATH statement forces the client application to use the pw.jar file from the specified location.
If you run the Java Plug-in console on a system attempting to run the out-of-the-box Java client application with a pw.jar specified in the CLASSPATH, you will receive messages similar to the following:
java.security.AccessControlException: access denied (java.lang.RuntimePermission modifyThreadGroup) at java.security.AccessControlContext.checkPermission(Unknown Source) at java.security.AccessController.checkPermission(Unknown Source) at java.lang.SecurityManager.checkPermission(Unknown Source) . . .
There are three ways, any one of which will work, to get around this behavior:
javac.exe -classpath .;c:\jdk1.3.1\process\pw.jar MainSample.java
The disadvantage to this approach is that you have to specify the pw.jar
location each time you compile or run the application.
set CLASSPATH=.;C:\<your directory>\pw.jar;%CLASSPATH%where:
Note The only portion of the CLASSPATH statement specific to eProcess development is the location of the pw.jar file. If any of these assumptions are not correct for your development environment, refer to the Sun Microsystems Java Development Kit documentation (http://java.sun.com/) for additional information on setting up the CLASSPATH variable.
Note If you are using an IDE, and you want to use the eProcess UI
Toolkit Swing-based Java beans and interfaces to create user controls to
allow interaction with the API samples, add the vwpanel