Configuring the JiGlue COM Bridge

The FileNet-supplied JiGlue COM Bridge is a requirement for web services whenever a COM-based application/applet, such as an ASP or ASP.NET-based application, must communicate with the Process Engine. Configuring the JiGlue COM Bridge consists of the following basic steps:

  1. Configure the Java Runtime Environment (JRE) and CLASSPATH.
  2. Configuring JiGlue (if not on a workflow server or Process Engine server).
  3. Register the JiGlue Library (jiglue.dll).
  4. Deploy the Client Application.

Procedures for these steps are provided below.

Configure the Java Runtime Environment (JRE) and CLASSPATH

To use the JiGlue COM Bridge, if you have not already done so, you must first install the appropriate Java SDK on your development system (the JDK version varies depending upon your OS). For information on which JDK to use and how to configure the JDK for Process development, see the Configuring the Java Runtime Environment (JRE) topic. Once you have installed and configured the JRE for Process development, you must configure your CLASSPATH for the location of the pw.jar file (contains the Process APIs) and register the jiglue.dll file on your system.

If you are planning to develop COM applications on your Process Engine server, typically you will have already installed your JDK and configured your JRE and CLASSPATH; skip to the Register the JiGlue Library (jiglue.dll) procedure.

Note When installing the JDK, be sure to use the default settings. If you change default settings and you are using JRE 1.3.1, the security settings will not be correctly installed by the JDK installer (this is not a problem with JRE 1.4.x). To correct for JRE 1.3.1, make sure that both the <JRE>\bin and the <JRE>\bin\hotspot directories have both Read and Execute privileges assigned for the Users group and that these directories are in your CLASSPATH.

Configuring JiGlue (if not on a Workflow server or Process Engine server)

If you are planning to develop an application on a system that is neither your workflow server or your Process Engine server, use the following procedure:

  1. If you have not already done so, install the appropriate Java SDK (or JDK) on your development system. In order to use the JiGlue COM Bridge, you should install the JDK in the default directory (for example, <drive>...\jdk1.4.0). If you run the PJAC installer for FileNet Web Services and/or Open Client or Stand-alone PJAC, PJAC installs the Sun JDK 1.3.1 to the default directory. For information on which JDK to use and how to install the JDK and configure your JRE for Process development, see the Configuring the Java Runtime Environment (JRE) topic elsewhere in this guide.
  2. Create a local directory (in any location) called \process. You will use this directory to hold the Process Developer files, including the JiGlue library files (jiglue.dll and jiglue.tlb).
  3. Locate the following files in your filesystem setup:
  4. For additional information on these files and where to find them, see Installing the Process Development Environment and select the Process Development Environment for your FileNet web application.

  5. For FileNet Web Services and Open Client, copy the jiglue.dll, jiglue.tlb, and pw.jar files to the \process directory. For Workplace, copy the jiglue.dll, jiglue.tlb, eProcess.jar and wcm.jar files to the \process directory (in order for JiGlue to work correctly with Workplace, all of these files must be in the same directory).
  6. If you have not already done so on this system, configure the CLASSPATH to specify the pw.jar location (typically either by creating a batch file to include pw.jar in the CLASSPATH, or if you are developing using an IDE (such as IDEA™, JBuilder™, etc.), by adding pw.jar to your global or project setting); for Workplace, include eProcess.jar and wcm.jar. For details, see the Configuring the Java Runtime Environment (JRE) topic.

Note The jiglue.dll parses the CLASSPATH for the location of the pw.jar file (for Workplace, also eProcess.jar and wcm.jar). If JiGlue does not find pw.jar, etc. in the CLASSPATH:

Note If you wish to use the Content Engine Java API runtime classes as well, you will need to also add the wcm.jar file to a subkey of the Process HLM\SOFTWARE\FileNet\eProcess registry key. For example: [HKEY_LOCAL_MACHINE\SOFTWARE\FileNet\eProcess\classpath.wcm] ="C:\\FNSW\\BIN\\wcm.jar".

Register the JiGlue Library (jiglue.dll)

Note If you have run the PJAC installer for FileNet Web Services, Open Client, or Stand-alone PJAC on this system, this step is not required (the PJAC installer has already registered the jiglue.dll).

  1. Open a command prompt, and cd to the newly-created \process directory.
  2. Register jiglue.dll by entering the following at the command prompt:

    regsvr32.exe jiglue.dll

    Tip You can unregister the library by entering:

    regsvr32.exe /u jiglue.dll

Deploy the Client Application

If you are developing a new ASP-based or ASPX-based application or extending the default ASP or ASPX application and you plan to deploy them on client systems, your installer must perform the following steps:

  1. Install or check for an existing installation of the JRE (currently JRE 1.4.0 for all Process application clients).
  2. Create a new directory to contain the Process components.
  3. Copy the jiglue.dll, jiglue.tlb, and pw.jar files to the new directory; for Workplace applications requiring JiGlue, copy the jiglue.dll, jiglue.tlb, eProcess.jar, and wcm.jar files (in order for JiGlue for Workplace to work properly, all of these files must be in the same directory).
  4. Register the jiglue.dll (see Register the JiGlue Library (jiglue.dll) above).