Once you have created a new Java Step Processor or Launch Step Processor and have added the classes to a Java ARchive (JAR) file, you must deploy and configure the custom Processor on the eProcess server.
Note Your JAR file must be signed (with either a Netscape Object Signing Certificate or a Sun Java Object Signing Certificate). For additional information, see Sign a Jar File.
Caution If you upgrade to a new Panagon Web Services version, you must
redeploy all existing custom Step and Launch Processors. Existing custom Java
Step Processors and Launch Step Processors should be recompiled and then redeployed
using the procedure shown here. If you get compiling errors, correct your samples
by comparing them to the new version's sample Java Processors (see Java
Step Processor Sample Files).
To deploy a custom Java Step or Launch processor, use the following procedure:
<PARAM NAME=CODE VALUE="filenet.vw.apps.steps.tabbed.VWTabbedStepApplet">
<PARAM NAME=CODE VALUE="newstep.newStepApplet">
's_jarArchiveTag=s_jarArchiveTag + ", " + "samplestep.jar"'
For example, the statement should be similar to the following:
s_jarArchiveTag=s_jarArchiveTag + ", " + "<JAR file>.jar"
(where <JAR file>.jar is the name of the JAR file you created and copied to the \WF_Extra directory).
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 Sign a Jar File).
If you intend to use several .JAR files, you should add all of your class files into a single JAR file and reference only the one file. Alternatively, you can specify multiple JAR files using a comma (",") delimiter. Not all browsers support multiple JAR files.