Compiling a Java application or applet and adding it to a JAR file is required in order to deploy a Java application. For Process applications, compile a custom Java application or applet in a manner comparable to compiling the sample Java Step Processor and Launch Step Processor provided with the Process Development Environment (includes both application and applet versions of these Processors), as shown in the procedure below.
Note If you have not already done so, you must complete the following actions before you can compile these samples:
To compile the unmodified sample Java Step and Launch Step Processors, use the following procedure (your compile statements will vary according to which JDK and which FileNet web application you are using):
For applets for FileNet Workplace:
Enter a statement similar to:
C:\jdk1.4.0\bin\javac.exe -classpath .;"C:\<your directory>";"C:\<your directory>\eProcess.jar";"C:\<your directory>\wcm.jar";"C:\<your directory>\pw.jar";%CLASSPATH% VWSampleStepApplet.java
Note You should specify the location of the package as part of the compiler command, as shown here. Alternatively, if you have already created a batch file that includes the eProcess.jar, wcm.jar, and pw.jar locations in the CLASSPATH variable, you can specify setenv and need not specify the eProcess.jar, wcm.jar, and pw.jar locations; for details, see the Configure the Java Runtime Environment (JRE) topic).
Similarly, you compile the unmodified Launch Step Processor sample applet by entering a command similar to the following (from the directory containing the Launch Step Processor sample):
C:\jdk1.4.0\bin\javac.exe -classpath .;"C:\<your directory>";"C:\<your directory>\eProcess.jar";"C:\<your directory>\wcm.jar";"C:\<your directory>\pw.jar";%CLASSPATH% VWSampleLaunchApplet.java
For applications for FileNet Workplace:
Alternatively, if you want to use the sample Java applications, you can compile the unmodified Step Processor sample or Launch Step Processor sample applications by entering commands similar to the following (from the directory containing the appropriate sample):
C:\jdk1.4.0\bin\javac.exe -classpath .;"C:\<your directory>";"C:\<your directory>\eProcess.jar";"C:\<your directory>\wcm.jar";"C:\<your directory>\pw.jar";%CLASSPATH% VWSampleStepApplication.java
C:\jdk1.4.0\bin\javac.exe -classpath .;"C:\<your directory>";"C:\<your directory>\eProcess.jar";"C:\<your directory>\wcm.jar";"C:\<your directory>\pw.jar";%CLASSPATH% VWSampleLaunchApplication.java
For applets for FileNet Web Services or Open Client:
Enter a statement similar to (assumes using the JDK 1.3.1 installed by PJAC; modify for your JDK as appropriate):
C:\jdk1.3.1\bin\javac.exe -classpath .;"C:\<your directory>";"C:\<your directory>\pw.jar";%CLASSPATH% VWSampleStepApplet.java
Note You should specify the location of the package as part of the compiler command, as shown here. Alternatively, if you have already created a batch file that includes the pw.jar location in the CLASSPATH variable, you can specify setenv and need not specify the pw.jar location; for details, see the Configure the Java Runtime Environment (JRE) topic).
Similarly, you compile the unmodified Launch Step Processor sample applet by entering a command similar to the following (from the directory containing the Launch Step Processor sample):
C:\jdk1.3.1\bin\javac.exe -classpath .;"C:\<your directory>";"C:\<your directory>\pw.jar";%CLASSPATH% VWSampleLaunchApplet.java
Alternatively, if you want to use the sample Java applications, you can compile the unmodified Step Processor sample or Launch Step Processor sample applications by entering commands similar to the following (from the directory containing the appropriate sample assumes using the JDK 1.3.1 installed by PJAC; modify for your JDK as appropriate):
C:\jdk1.3.1\bin\javac.exe -classpath .;"C:\<your directory>";"C:\<your directory>\pw.jar";%CLASSPATH% VWSampleStepApplication.java
C:\jdk1.3.1\bin\javac.exe -classpath .;"C:\<your directory>";"C:\<your directory>\pw.jar";%CLASSPATH% VWSampleLaunchApplication.java
At this point, you are ready to create a JAR file to contain the compiled classes.