Installing the Process Development Environment - FileNet Workplace

The FileNet Process Engine includes a Process Development Environment for developers. The Process Development Environment for the FileNet Workplace web application consists of a set of JAR files that contain the Java API runtime classes, Process API samples, sample HTML and Java Step Processor applets/applications (available for customization), and library and toolkit files.

Subtopics include:

Process Development Environment Overview

The Process Development Environment for FileNet Workplace consists of (for further details, see Process Development Environment Contents below):

Process Development Environment Installation Procedure

To install the Process Development Environment on your development system, use the following procedure:

  1. Insert the FileNet P8 Platform Installation CD into the CD-ROM drive on your system.
  2. On the installation CD, locate the ...\ProcessEngine\Developer Files folder.

Note The locations listed in this topic may vary from the actual location on the FileNet P8 Platform Installation CD. If you have difficulty locating the ...\Developer Files folder, search for the MainSample.java file on the Installation CD. This should help you find the ...\Developer Files\Samples\API folder location on the CD.

  1. Copy the ...\ProcessEngine\Developer Files folder, and all its subdirectories, to your local drive. Maintain the relative directory structure of the directories.
  2. If you are developing a COM application and plan to use the JiGlue COM Bridge to instantiate COM objects (allows you to make Win32 calls that are equivalent to native Java statements), configure the JiGlue COM Bridge on your development system; for information, see Configuring the JiGlue COM Bridge.
  3. Locate the eProcess.jar, wcm.jar, p8ciops.jar, jaas.jar, and xerces.jar files on your Application Engine server, and put copies into the directory structure you created on your development system. (See Process Development Environment Contents below for information on locating these JAR files.)
  4. Change the file attributes for all of the files in the newly created directory structure from Read-only to Read/Write.
  5. If you have not already done so, install and configure the Sun Microsystems JDK on your development system, being sure to configure the CLASSPATH to specify the eProcess.jar, pw.jar, and wcm.jar locations (typically either by creating a batch file to include eProcess.jar, wcm.jar, and pw.jar in the CLASSPATH, or if you are developing using an IDE — such as IntelliJ IDEA, JBuilder, etc. — by adding eProcess.jar, etc. to your global or project setting). For details on installation, configuration, and which JDK to use, see Configuring the Java Runtime Environment (JRE). If you are developing on multiple Process Engine servers and/or if you are implementing the (optional) Process Analyzer and the (optional) Process Simulator on other machines, be sure that you have installed and configured the JRE and copied the pw.jar file on each of these machines.
  6. Verify that your local drive now contains the following files with Read/Write properties in your ...\ProcessEngine\Developer Files directory:

    pw.jar
    eProcess.jar
    wcm.jar
    vwpanel.jar
    jiglue.dll (if you plan to use the JiGlue COM Bridge for a COM application)
    jiglue.tlb (if you plan to use the JiGlue COM Bridge for RAD development)
    The contents of the ...\ProcessEngine\Developer Files\Samples directory

Note In order for JiGlue to work correctly, the pw.jar, wcm.jar, and eProcess.jar files and the JiGlue library files (jiglue.dll and jiglue.tlb) must be in the same directory.

Process Development Environment Contents

If you followed the installation procedure above, the Process Development Environment files should be located on your Application Engine server in the ...\Workplace\download directory and on your development system in a directory structure contained in the ...\Developer Files directory.

The default Process Development Environment directory structure for Workplace consists of the following directories and files:

Directory Description of Contents

On the Application Engine Server:

...\Workplace\download

Contains the following Process development files:

eProcess.jar: Includes the Process Engine Java API runtime classes. You must install this file on the Application Engine server in order to develop a custom Process application, such as a Step Processor, or to work with the Step Processor and API samples shipped with your system.

wcm.jar: Includes the Content Engine Java API runtime classes. This file must also be installed on the Application Engine server in order to develop a Process application or to work with the Step Processor and API samples shipped with your system.

p8ciops.jar — contains API classes for Content Engine operations used with the Component Manager.

jaas.jar — contains the the Java Authentication and Authorization Service classes, used to provide user authentication.

xerces.jar — contains the Xerces Java XML parser files.

These files are located in the <application server>...\Workplace\download directory, where <application server> is the name of the Application Server software you are using with FileNet P8 Platform and must be deployed on the Application Engine. If you install the Web Application Toolkit Source Code option, the default locations are <application server>...\Workplace\download\eProcess.jar, <application server>...\Workplace\download\wcm.jar, etc.

On the FileNet P8 Platform Installation CD under the \ProcessEngine directory:

\Developer Files

Contains the following development files:

pw.jar: Contains the Process Engine Java API runtime classes, plus client classes, Task Manager classes, third party classes [e.g., for Xerces], etc. The pw.jar file should reside on the Process Engine (if there are multiple Process Engines, pw.jar should be on each Process Engine) and also, if used, on the Process Analyzer and the Process Simulator.

vwpanel.jar: Contains the Java Step Processor UI Toolkit beans, interface, and information classes which may be used for Rapid Application Development (RAD), drag-and-drop functionality in an Integrated Development Environment (IDE), such as JBuilder. To use drag-and-drop RAD programming in your IDE to customize the user interface with these Swing-based Process controls used for the Java Step Processor and Launch Step Processor sample applets/applications provided with the Process Development Environment, add vwpanel.jar to your IDE.

jiglue.dll: The dynamic link library used to enable Java - COM communication (also called the JiGlue COM Bridge).

jiglue.tlb: The JiGlue type library.

Developer Files
\Samples

Includes the following directories:

\API: Contains sample Java API files that may be used to create, launch, complete, and display and save log information for a workflow.

\vwpanel: Contains the sample Java Step Processor application files (in the \samplestep sub-directory) and Java Launch Step Processor sample files (in the \samplelaunch sub-directory) along with the image files needed for the default user interface.

\Utils: Contains a Java class that allows you to view or remove entries from the Java (Remote Method Invocation) RMI registry.