This topic summarizes the changes made between P8 Process Release 2.0 and Release 2.0.1 and their implications for developers, including changes to the Process APIs and other miscellaneous developer-related changes. Bug fixes are not included unless they required a modification to the Process APIs.
Topics covered in this section include:
The following table summarizes the changes for this Process release. The table also describes the impact (if any) of these changes on the Process APIs or on how Process development is done.
Change | Description | Process API or Other Developer Impact |
---|---|---|
Oracle 9i support. | Supports Oracle 9i across the P8 platform, including the Process Engine, Content Engine, Rendition Engine, and the Web Content Manager. Oracle 8x is no longer supported for the Process Engine database. | No direct API or other developer impact. For information on Oracle installation and configuration, see Help for Installation. |
Support additional LDAP server. |
Previously, the Process Engine supported only Active Directory services for user authentication via LDAP. Support for the Sun iPlanet (SunONE) LDAP server (in addition to Active Directory, which is still supported) has been added. |
No direct API or other developer impact. When the Process Engine is installed and configured, the Process Task Manager is used to specify the LDAP directory service to be used (Active Directory or SunONE) and the LDAP properties for the Login and Display name. One-way SSL, to provide a secure connection between the Process Engine and the LDAP directory service, is available (see next item). |
Support SSL (one-way) between the Process Engine and the LDAP directory service. | Supports one-way SSL connections between the Process Engine and the LDAP directory service server (Active Directory or SunONE) to provide user credential security. LDAP calls initialize the SSL connection to the Process Engine using the SSL certificate location and port number. | No direct API or other developer
impact. The Process Task Manager
is used to specify the SSL certificate database location and the SSL port
number (default port is 636). |
Process Analyzer upgrade. | Provides an upgrade utility to upgrade the Process Analyzer from Release 2.0 to 2.0.1. | No direct API or other developer impact. For information, see Help for Installation. |
Process Simulator upgrade. | Provides an upgrade utility to upgrade the Process Simulator from Release 2.0 to 2.0.1. | No direct API or other developer impact. For information, see Help for Installation. |
Process Engine upgrade. | Provides an upgrade utility to upgrade the Process Engine from Release 2.0 to 2.0.1. | No direct API or other developer impact. For information, see Help for Installation. |
Rules Engine integration. | Provides Process Engine integration with the iLog Rules Engine via a VWRules shared library on the Process Engine and a FileNet-supplied Rules daemon on the iLog Rules Engine (the iLog Rules Engine must be purchased separately). Rules Engine implementation can be enabled/disabled via a system-wide flag specified via the Process Configuration Console. Business rules are specified via the client iLog Rules Editor. The Process Designer may be used to specify the rule sets to be applied to workflow steps. The Process Task Manager is used to specify setup (e.g., specify the Rules repository path in vwserver.ini) and configuration (e.g., start/stop/configure the Rules daemon). | New create, set, and get ruleset API methods and a system-wide flag were added to determine if Rules functionality is enabled on the Process Engine server. For additional information, see Modified API Classes/New Methods. |
Default index tablespace location for Oracle. | The Process Engine installer was enhanced to allow a user to be prompted for a default index tablespace (for Oracle on a Unix platform only). The tablespace name is passed to the Image Services mini-installer via an Environment variable. | No direct API or other developer impact. For information, see Help for Installation. |
SQL script to automate execution of three IS 4.0.0 SQL scripts. | The Process Engine installer was enhanced to automatically launch a single SQL script to execute three SQL scripts required by IS 4.0.0 for remote site-controlled Oracle 9i systems. These three SQL scripts (Filenet_site.sql, fn_CreateStoredProcedures. sql, fn_GrantSPPermissions.sql) are used respectively, to add FileNet database users, add a set of Oracle stored procedures required by IS, and set database permissions on the stored procedures. Alternatively, this single SQL script may also be run manually by the Oracle system administrator at the beginning of Process Engine Installation, prior to database initialization (assumes the Oracle 9i client is already installed and connected to the Oracle database server). | No direct API or other developer impact. For information, see Help for Installation. |
Event-driven mechanism for the Component Integrator. | Provides an event-driven mechanism for filtering events into Component queues and forwarding them to the Component Manager, so that a Component Integrator-based Work Performer can be event-driven as well as polling queues for work items (both mechanisms are provided). | No direct API or other developer impact. For information, see Developing Component Integrator-Based Workflow Applications and Help for Task Manager > Component Manager. |
Process Analyzer database support enhancement. | Provides Process Analyzer capabilities to support and configure remote database server (MS SQL Server) names, named database instance, and support a case-sensitive character set. | No direct API or other developer impact. For information, see Help for Process Analyzer Configuration and Administration. |
Default port number for the Process Analyzer. | The default port number provided by the Process Analyzer installer has been changed to 32772. | No direct API or other developer impact. |
Database system instruction. | Provides the ability to invoke a stored procedure call on a local or remote Oracle or MS SQL Server database. The Process Designer is used to specify the database system instruction and parameters for execution by the Process Engine. The vwtool utility has been modified to configure the database name and the Oracle or SQL Server user name and password (using the vwtool Dbconfig command). | A new getDatabaseType() API method with constants for database types to return the Process Engine database configuration (Oracle or MS SQL Server 2000) were added to the VWSession class. A static integer constant was added to the VWActionType API for the database execute system instruction. For additional information, see Modified API Classes/New Methods. |
Multiple Process Engine servers with remote database and Process Analyzer support. | Supports multiple Process Engine servers (with a "Primary Process Engine" and "Additional Process Engines"). The Process Analyzer installation has been modified to enable the user to configure the Process Analyzer for a Process Engine multi-server configuration. The Process Configuration Console has been modified to allow the user to configure the Process Analyzer for a Process Engine single-server or multi-server configuration. | No direct API or other developer impact. |
Support the JiGlue COM Bridge for P8 Baseline Process Engine. | Provides the JiGlue COM Bridge for Process Engine use with the Workplace web application for COM-based applications (previously, the JiGlue COM Bridge was only available with FileNet Image Manager using FileNet Web Services and Open Client web applications). | For developers creating/modifying COM applications, the JiGlue COM Bridge provides a translation layer between the Process Java APIs and COM. Using the JiGlue COM Bridge enables developers to make Win32 calls that are equivalent to native Java statements; i.e., the JiGlue COM Bridge enables you to instantiate COM objects using the Process Java APIs. For information, see the section, Developing for COM, elsewhere in this guide. |
One new public API class, VWRuleSetDefinition, has been added to the Process API to support Rules Engine integration.
Class | Method Included | Class or Method Description |
---|---|---|
VWRuleSetDefinition | ------- | This class encapsulates a ruleset object for Rules Engine integration. |
String getValue() |
Gets the value of this rule set; i.e., the rule set name. | |
void setValue(String) |
Sets the value for the rule set; i.e., the rule set name. | |
void toXML(StringBuffer) |
Appends an XML String that represents this VWRuleSetDefinition object to the buffer specified by the input parameter. | |
void validate(VWSession, |
Validates this VWRuleSetDefinition object, by updating the specified Vector with any validation errors found. | |
String toString() |
Returns a string value (i.e., the rule set name.) of the rule set. | |
VWStepHistory |
boolean isCompoundStep() |
Indicates whether the step type of the current history object is a compound step. Compound steps are used to access timers, to make calls to submaps, and to perform complex workflow map instruction functions (e.g., Delay, etc.). |
The following table summarizes the API classes modified for this release. New methods and class members added or modified are also shown.
Class | Members Added | Description | Reason for Change |
---|---|---|---|
VWMapNode (parent virtual class) VWCompoundStepDefinition VWStepDefinition |
PRE_RULESETS = 0 |
For use with getRuleSets(int) and setRuleSets(int, VWRuleSetDefinition []). |
Support for design-time use of rulesets. |
VWMapNode (parent virtual class) VWCompoundStepDefinition VWStepDefinition |
UPDATE_RULESETS = 1 |
For use with getRuleSets(int) and setRuleSets(int, VWRuleSetDefinition []). |
Support for design-time use of rulesets. |
VWMapNode (parent virtual class) VWCompoundStepDefinition VWStepDefinition |
POST_RULESETS = 2 |
For use with getRuleSets(int) and setRuleSets(int, VWRuleSetDefinition []). |
Support for design-time use of rulesets. |
VWMapNode (parent virtual class) VWCompoundStepDefinition VWStepDefinition |
getRuleSets(int ruleSetSelector) |
Retrieves the array of VWRuleSetDefinition objects for this step definition of the type, specified by the ruleSetSelector parameter. |
Support for design-time use of rulesets. |
VWMapNode (parent virtual class) VWCompoundStepDefinition VWStepDefinition |
setRuleSets(int ruleSetSelector, VWRuleSetDefinition[] theRules) |
Sets the VWRuleSetDefinitions for this step definition. |
Support for design-time use of rulesets. |
VWSession | getDatabaseType() | Returns an integer associated with the database configuration type. | Support for a Database System Instruction feature. |
VWSession | DATABASE_ORACLE = 1 | Oracle Database type. | Support for a Database System Instruction feature. |
VWSession | DATABASE_SQL2000 = 2 | SQL2000 Database type. | Support for a Database System Instruction feature. |
No changes for this release.
The following table summarizes API class members that have been deprecated between P8 Process Releases 2.0 and 2.0.1.
Note For additional information about any specific deprecation, refer to the "Deprecated Methods" section of the Process API JavaDoc documentation.
Class | Member deprecated | Replacement | Reason for Change |
---|---|---|---|
VWNewWorkObject |
VWNewWorkObject class |
VWSession.createLiveWorkObject() |
The VWSession.createNewWorkObject() method that created and instantiated this object was deprecated (as of the P8 Process 2.0 release, because of its limitation in only allowing a single work class per roster). Consequently, the VWNewWorkObject class has also been deprecated and functionally replaced by the VWSession.createLiveWorkObject() method, which is now used to provide a work object (this method allows multiple work classes on a roster by returning an array of VWCreateLiveWOResult objects; these objects contain the F_WobNum and RosterNames for the new work items, allowing convenient access to the new item). |
VWInjectSessionInfo |
VWInjectSessionInfo class |
VWSession.createLiveWorkObject(), VWSession.createLiveWOResult() |
This class used the now-deprecated VWNewWorkObject class to get inject session information. Consequently, this class is also now deprecated and replaced by the indicated VWSession methods. |
VWQueueQuery | QUERY_GET_TRANSLATED_ SYSTEM_FIELD field |
Deprecated; not replaced. | Query items returned already include translated system field values as the default. This flag is deprecated consistent with the deprecation of the same flag for the VWQueue and VWRoster classes (also see VWRosterQuery below). |
VWRoster |
VWRoster.getInjectSessionInfo()
|
VWSession.createLiveWorkObject(), VWSession.createLiveWOResult() |
This method creates and instantiates the now deprecated VWInjectSessionInfo object. Consequently, this method is also now deprecated and replaced by the indicated VWSession methods. |
VWRosterQuery | QUERY_GET_TRANSLATED_ SYSTEM_FIELD field |
Deprecated; not replaced. | Query items returned already include translated system field values as the default. This flag is deprecated consistent with the deprecation of the same flag for the VWQueue and VWRoster classes (also see VWQueueQuery above). |
The following documentation changes have been made since the last release: