IBM FileNet P8, Version 5.2.1            

Process Java API

This topic describes changes necessary to your 3.5.x Process Java API applications so they can run in a current release environment. If you have already modified your 3.5.x applications to run in a 4.0.x environment, there are no additional modifications needed to run your applications in a current release environment.

Process Router

The Process router used in releases prior to 4.0 was configured using the Process Task Manager, and the configuration information was stored in a local XML file. The Process Engine API referenced the router via the RMI registry. Beginning in the 4.0 release, the Process router has been replaced by Connection Points. The connection points are implemented in the Content Engine API classes PEConnectionPoint and IsolatedRegion, configured using IBM® Administration Console for Content Platform Engine, and stored in the GCD. When logging on to a Process Engine session, existing Process Engine applications will need to supply a connection point name (instead of a router name) and the Content Engine URI referencing the connection point.

Note that the Process Engine Web Service requires only the connection point name.

Directory Services and Authentication

In IBM FileNet® P8 3.5.x, LDAP directory lookups were done using a system-configured account. Beginning in the 4.0 release, the Process Engine uses JAAS and the Content Engine Java API to perform authentication and directory service lookups.

Content Engine API Files

Because the Process Engine uses the Content Engine API for authentication and directory service access, the 3.5.x applications that are being upgraded for the current release of IBM FileNet P8 must have the Content Engine API JAR files in their classpath. IBM recommends that you use the Web Services transport to connect your custom Process Engine applications to the Content Engine. However, for applications that use the J2EE framework with facilities specific to an application server (such as JMS), the EJB transport should be employed.

If your applications use the Web Services transport, follow the instructions below to configure 3.5.x applications to run in the current release environment. If your applications use the EJB transport, refer to the transport protocols information in the Getting Started section of the Content Engine Java and .NET API Developer's Guide, or to "Configuring Component Integrator" in the Configuring the Process Development Environment section of the Process Engine Developer's Guide.

To configure your 3.5.x applications for the current release environment (Web Services transport only):

  1. Using the Content Platform Engine client installer, install the Content Platform Engine client API. Select "Other applications" and specify the HTTP protocol for the URIs. During the installation process, the installation directory will be displayed in the summary. For example, C:\Program Files\IBM\FileNet\CEClient for Microsoft Windows and /opt/IBM/FileNet/CEClient for a non-Windows system:
    CEClient
    \config\samples
    \lib

    The other directories are not needed. The installation directory is referenced in the following instructions as CE_API.

  2. Add the following jar files to the classpath of the Process Engine applications: CE_API\lib\Jace.jar, CE_API\lib\pe.jar, CE_API\lib\pe3pt.jar, CE_API\lib\peResources.jar.
  3. Add the following JVM system properties to the command line of the Process Engine applications:
    -Djava.security.auth.login.config=<CE_API>\config\samples\jaas.conf.WSI
  4. Specify the Content Engine URI. The Content Engine server URI must be provided to the Process Engine API for the lookup of the connection points. Process Engine applications can use the VWSession methods to specify the URI or, for minimal code change, do one of the following:
    • Put the CE_API\WcmApiConfig.properties file in a directory that is in the classpath of the Process Engine application.
    • Add the JVM system property, filenet.pe.bootstrap.ceuri, and specify the Content Engine URI as follows:
      -Dfilenet.pe.bootstrap.ceuri=http://CEServerName:CEServerPort/wsi/FNCEWS40MTOM/


Last updated: October 2015
process_java_api.htm

© Copyright IBM Corporation 2015.