This topic describes changes necessary to your 3.5.x Process Java API applications so they can run in a 4.5 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 4.5 environment.
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 Enterprise Manager, 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.
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.
Because the Process Engine uses the Content Engine API for authentication and directory service access, applications being upgraded for IBM FileNet P8 4.x will need to 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 the applications to run in a 4.x 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 Developer's Guide, or to "Configuring Component Integrator" in the Configuring the Process Development Environment section of the Process Engine Developer's Guide.
-Djava.security.auth.login.config=<CE_API>\config\jaas.conf.WSI
-Dwasp.location=<CE_API>\wsi
The Content Engine server URI needs to be provided to the Process Engine API for the lookup of the connection points. Process Engine applications can use the VWSession methods to specify this or, for minimal code change, do one of the following:
RemoteServerUrl = cemp:http://CEServerName:CEServerPort/wsi/FNCEWS40DIME/
-Dfilenet.pe.bootstrap.ceuri=http://CEServerName:CEServerPort/wsi/FNCEWS40DIME/