In order to run a Process application or applet for FileNet Web Services, you must deploy it on your FileNet Web Services server.
Caution If you upgrade to a new FileNet
Web Services, PJAC, or Process Engine version, you must redeploy all
existing custom applications and applets. Existing applications/applets, including
all Java Step Processors and Launch Step Processors, should be recompiled and
then redeployed using the procedure below. If you get compiling errors, correct
your Processor applications/applets, for example, by comparing them to the new
version's sample Java Processors (see Java
Step Processor Sample Files and Java
Launch Step Processor Sample Files).
To deploy a Java application/applet, such as a custom Java Step or Launch Step Processor, on the Application Engine server, use the following procedure (for details, click on the step):
Note This procedure assumes that you have already installed the Process Development Environment (for information, see Installing the Process Development Environment and click on the appropriate link according to which FileNet web application you are using), have installed and configured the Java Runtime Environment (JRE), have compiled your application files, and have created and signed (with a Netscape Object Signing Certificate) a JAR file for your application/applet.
This procedure describes how to create an ASP page as part of the process of providing a customized Java Step Processor (or other Java application/applet) to the FileNet Web Services server, which in turn makes it available to the Process Engine server. Creating an ASP page for a Launch Step Processor is a similar process, although the locations and file names are different (as indicated in the procedure below). Unless you are creating your own ASP page from scratch, the simplest approach may be to copy, rename, and modify the sample step_main.asp file provided with your Process Development Environment.
To create an ASP page for a custom Java Step Processor or Launch Step Processor Processor, use the following procedure:
<PARAM NAME=CODE VALUE="filenet.vw.apps.steps.tabbed.VWTabbedStepApplet">
<PARAM NAME=CODE VALUE="newstep.newStepApplet">
Modify the globalInfo.asp file in the ...\Redist\WF_Extras directory to specify the new (or updated) Step Processor and JAR files, as follows:
's_jarArchiveTag=s_jarArchiveTag + ", " + "samplestep.jar"'
s_jarArchiveTag=s_jarArchiveTag + ", " + "<my_JAR_file>.jar"
Note: You can also, if you wish, place your JAR file in another directory. However, since the JAR file path is relative to ...\IDMWS\Redist\WF_Extras, you must specify the path. If you do this and use unified logon, the folder must have Anonymous Access enabled. Remember, as previously indicated, the JAR file must be signed (for details, see Signing a Jar File).
At this point, you are ready to configure the server for the web application and add the new or updated Step Processor to the workflow.