FileNet Open Client Architecture

FileNet Open Client is a Web application that provides a Web services automation layer between an ASP.NET-based Process application (via PJAC for FileNet Open Client) and a client (via the Web server).

Note: Refer to your FileNet Open Client documentation for complete information about FileNet Open Client.

FileNet Open Client automatically downloads the Process Java™ APIs, the Process applets, the client-side Java™Script API (to open popup windows), and the Java™ Runtime Environment to the client the first time the client accesses FileNet Open Client services on the Web server.

To access an ASPX-hosted application from a client browser, a user logs into the Web server and either launches a workflow or participates in an existing workflow (for example, by opening an Open Client HTML or Java Step Processor application). Client HTTP requests that do not require interaction with the Process Engine via a Java applet/application are passed to the FileNet Open Client services and the PJAC for FileNet Open Client components, which send them via the Process Java APIs and the JiGlue COM Bridge to the ASPX-hosted application.

If a Process applet/application on the client requests IDM objects from FileNet Image or Content Services (such as, attachments needed for a step in a workflow), FileNet Open Client services retrieve them via RPCs to the FileNet Image Services server and/or the FileNet Content Services server, and provides the services to make them available to the client.

Open Client enables you to use the ASP.NET-based User Inbox, Step Processor, and Launch Step Processor supplied with the Open Client installation. You can also customize these applets as required (source code is provided with the Open Client installation). The ASPX top-level pages host the Process modules, enabling you to launch these modules either from the FileNet Open Client Web application or via email notification messages.

The following figure illustrates the Process Engine architecture and its interfaces within the context of the .NET framework:

Additional Components

The following additional components are also necessary to use FileNet Open Client:

JiGlue COM Bridge

The JiGlue COM Bridge acts as a translation layer between the Process Java APIs and COM. The JiGlue COM Bridge provides the ability to instantiate COM objects using the Process Java APIs. Using the JiGlue COM Bridge you can make COM calls that are equivalent to native Java statements. For additional information, see Developing with the JiGlue COM Bridge.

PJAC for FileNet Open Client

The Process Java Applets Connectivity (PJAC) component combines Java and an interface to the ASPX-hosted application and the automation layer of FileNet Web Services. PJAC provides the Process integration services and connectivity (client-side Javascript API and Process applets) between FileNet Open Client and the Process Engine. PJAC is installed by running the PJAC installer on the Web server. See the topic Install Process Java Applets Connectivity in the IBM FileNet Image Manager Process Installation Guide. To download this guide from the IBM support page, see Accessing IBM FileNet Documentation. See also Process Java Applets Connectivity (PJAC).