 |
 |
|
|
|
Configuring the JiGlue COM Bridge
This topic describes how to configure the JiGlue COM Bridge on a development
system. Configuring the JiGlue COM Bridge consists of three basic steps:
- Configure the Java Runtime Environment (JRE)
and CLASSPATH.
- Register the JiGlue Library (jiglue.dll).
- 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 Runtime Environment (JRE) 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 Configuring the Java Runtime Environment
(JRE). 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.
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:
- 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 (<drive>...\jdk1.4.0).
If you run the PJAC installer for Open Client on this machine, 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.
- Create a local directory (in any location) called \process.
You will use this directory to hold the Process Developer files, including
pw.jar and the JiGlue library files (jiglue.dll and jiglue.tlb).
- Locate the following files in your FileNet filesystem setup:
- pw.jar file from the PJAC and Toolkit Installation
CD ...\Developer Files directory.
- The JiGlue jiglue.dll and jiglue.tlb library files
also in the ...\Developer Files directory.
For additional information on these files and where to find them,
see Installing the Process Development
Environment.
- Copy the jiglue.dll, jiglue.tlb, and pw.jar files
to the \process directory.
- 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 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. If JiGlue does not find
pw.jar in the CLASSPATH:
- The JiGlue library (jiglue.dll) attempts to find the registry
key:
HLM\Software\FileNet\Panagon eProcess
Services - Web WorkFlo\Extras + "pw.jar" .
For example: [HKEY_LOCAL_MACHINE\SOFTWARE\FileNet\eProcess\classpath.WS]
-PE@="C:\\FNSW\\BIN\\pw.jar" .
- If the library cannot find this registry key (see previous bullet),
jiglue.dll will then concatenate the subkeys of
HLM\Software\FileNet\eProcess ;
these subkeys are assumed to contain file names to a .jar file.
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 Open Client, this step is not required (the PJAC installer has already
registered the jiglue.dll).
To register JiGlue:
- Open a command prompt, and cd to the newly-created
\process subdirectory.
- Register jiglue.dll by entering
the following at the command prompt:
regsvr32.exe jiglue.dll/p>
Tip: You can unregister the library
by entering the following command:
regsvr32.exe /u jiglue.dll
Deploy the Client Application
If you are developing a new ASPX-based application or extending the default
ASPX application and you plan to deploy them on client systems, your installer
must perform the following steps:
- Install or check for an existing installation of the JRE (currently
for the client, JRE 1.4.0).
- Create a new directory to contain the Process components.
- Copy the jiglue.dll, jiglue.tlb, and pw.jar files
to the new directory (all three of these files must be in the same directory).
- Register the jiglue.dll (see Register
the JiGlue Library (jiglue.dll) above).
|