Deploying a Custom Java Step or Launch Processor

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:

  1. On your Web WorkFlo server, navigate to the <drive>...\Program Files\FileNET\IDM\Web\IDMWS directory.
  2. Create a new directory under the \Redist\WF_Step directory (at the same level as the \Tabbed directory). For Launch Step Processors, create the directory under \Redist\WF_Launcher.
  3. Copy the step_main.asp file from the \Tabbed sub-directory, and put the copy into your newly created directory. For Launch Step Processors, copy the launcher_main.asp file.
  4. Rename the .ASP file (it is recommended that this name reflect the function of the custom processor). Change the file attribute from Read-only to Read/Write.
  5. Open the renamed file. Locate the <PARAM> attribute of the <OBJECT> tag that matches the following line:

<PARAM NAME=CODE VALUE="filenet.vw.apps.steps.tabbed.VWTabbedStepApplet">

  1. Modify the <PARAM> statement to reference the correct applet. For example, if your JAR file was created in the \newStep directory and the applet class is called newStepApplet, your parameter statement would be similar to the following:

<PARAM NAME=CODE VALUE="newstep.newStepApplet">

  1. Save the renamed file.
  2. Navigate to the \Redist\WF_Extras directory.
  3. Place your custom Processor Java archive (JAR) file in the \WF_Extras directory.
  4. Still in the \WF_Extras directory, locate the globalInfo.asp file. Change the file attribute from Read-only to Read/Write.
  5. Open the globalInfo.asp file, and locate the following commented statement:

's_jarArchiveTag=s_jarArchiveTag + ", " + "samplestep.jar"'

  1. Copy the statement, and paste a new instance of the line immediately below the first. Do not use or modify the statement that specifies the location for the pw.jar file.
  2. Remove the apostrophe (" ' ") from the beginning of the line to allow the server to parse the statement. (By default, the line is commented out using the VBScript comment convention.)
  3. Delete the "samplestep.jar" portion of the statement, and modify the statement to reflect the actual name and location of the JAR file you created and copied to the \WF_Extras directory.

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).

  1. Save the modified globalInfo.asp file.
  2. Add the processor to the workflow.

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.