Skip navigation FileNet logo
  Open Client Developer's Guide
  Search  |  Index  |  Glossary   |  
Open menu Overview
Open menu Open Client Architecture
Close menu Developing for Process
  Open menu Process Overview
  Open menu Preparing for Development
  Open menu HTML Step and Launch Processors
  Java Processors
  Component-Integrator Work Performer
  Close menu Deploying Process Applications
    HTML Step Processors
    Close menu Java Step Processors
      Compiling Java Files
      Creating the JAR File
      Signing the JAR File
      Deploying the Java Application/Applet
      Configuring the Server for the Web Application
    Adding Step Processors to Workflow
Open menu Error and Exception Handling
Open menu Customizing the Framework
Globalization / Localization
Open menu General Information
   

Deploying a Process Open Client Java Application/Applet

In order to run a Process application or applet for FileNet Open Client, you must deploy it on your Web server.

Caution: If you upgrade to a new Open Client, 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, for example for Step Processors, correct your old Processor applications/applets by comparing them to the new version's sample Java Step Processors.

Subtopics include:

Java Application/Applet Deployment Procedure


To deploy a Java application/applet, such as a custom Java Step or Launch Step Processor, on the Web server, use the following procedure (as an example, the out-of-the-box Java Step and Launch Step Processor applets, e.g., FnSPAppletPage.aspx and its ASPX code-behind file, are shown in the procedure):

Note: This procedure assumes that you have already installed the Process Development Environment (see Installing the Process Development Environment), have installed and configured the Java Runtime Environment (JRE) in its default directory — to avoid JiGlue problems — and that you have included both the JDK and the pw.jar file in your CLASSPATH, have compiled your application files, and have created and signed a JAR file (with a Netscape Object Signing Certificate) for your application/applet.

  1. On your Process Engine or Web server, navigate to the <drive>...\Program Files\FileNet\IDM\Web\FNOpenClient directory.
  2. Create a new directory under the ...\eProcess\StepProcs\Java directory (at the same level as the \OOTB directory).
  3. Copy the FnSPAppletPage.aspx and the FnSPAppletPage.aspx.vb files from the ...Program Files\FileNet\IDM\Web\FNOpenClient\eProcess\StepProcs\Java\OOTB subdirectory and put the copy into your newly created directory. For Launch Step Processors, copy the FnLSPAppletPage.aspx and the FnLSPAppletPage.aspx.vb files from the ...Program Files\FileNet\IDM\Web\FNOpenClient\eProcess\Launchers\Java\OOTB subdirectory. If you are using custom ASPX pages, use the custom ASPX files instead.
  4. Rename the ASPX files (if you are using the default ASPX files). Change the file attribute from Read-only to Read/Write.
  5. Open the ASPX Step Processor or Launch Step Processor code-behind file (FnSPAppletPage.aspx.vb or FnLSPAppletPage.aspx.vb). Locate the AppletClassName object that matches the following line:

    plugInCtrl.AppletClassName = "filenet.vw.apps.steps.tabbed.VWTabbedStepApplet"

  6. Modify this statement to reference the correct Java applet. For example, if your JAR file was created in the \newStep directory and the applet class is called FnSPApplet, your parameter statement would be similar to the following:

    plugInCtrl.AppletClassName = "newStep.FnSPApplet"

  7. Save the renamed file.
  8. Navigate to the ...\FNOpenClient\eProcess\DownLoad directory.
  9. Place your custom Java Processor JAR file in the \download directory.
  10. On your server, navigate to the Process Open Client User Control directory (the default is the <drive>...\Program Files\FileNet\IDM\Web\FNOpenClient\eProcess\UserControl directory)
  11. Open the FnPlugInHelperCC.vb file.
  12. Find the statement where you declare your JAR file variable for the default pw.jar file. Add your new JAR file to this statement. For example, if you created the new JAR file, mynewjar.jar, you would modify this statement as follows:
    From:

    Private m_jarArchiveValue As String = "pw.jar"

    To:

    Private m_jarArchiveValue As String = "pw.jar, mynewjar.jar"

    (Do not delete pw.jar; just add your JAR file.) Close and save the file.

    Note: You can also, if you wish, place your JAR file in another directory. However, since the JAR file path is relative to "\FNOpenClient\eProcess\download", 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).

Once you have deployed your Step Processor, you will need to create the workflow (if you have not already done so), configure the server for the Web application and add the new or updated Step Processor to the workflow. Once that is done, you can run the application.

Creating the Workflow

If you have not already done so, using the Process Designer, create a workflow. For details see Help for Process Designer on the Process Documentation for FileNet Image Manager CD.