Skip navigation FileNet logo
  Open Client Developer's Guide
  Search  |  Index  |  Glossary   |  
Close menu Overview
  About This Guide
  What's New in 3.3
  Open menu Introduction to the Toolkit
  Close menu Programming Considerations
    View State Management
    Open Client and ActiveX
    Section 508 Compliance
    COM Objects and JiGlue in the .NET Environment
Open menu Open Client Architecture
Open menu Developing for Process
Open menu Error and Exception Handling
Open menu Customizing the Framework
Globalization / Localization
Open menu General Information
   

Developing in a Combined Open Client and ActiveX Environment

Open Client 3.3 supports both eProcess 5.0.0 and Process 2.0.1. eProcess 5.0.0 and Process 2.0.1 support ActiveX and Open Client coexistence on the same Web server and in the same isolated region. For more information about developing Process applications for ASP.NET-based Open Client, see the Developing for Process Open Client section of this guide.

Using eProcess 4.2.2 or Earlier

Coexistence is not available with eProcess 4.2.2 or earlier, because the workflows for the Open Client and ActiveX client are distinct. A workflow launched with ActiveX runs entirely within the ActiveX environment, while a workflow launched with the Open Client runs entirely within the Open Client environment. However, process integration is available when using Open Client 3.2 or a later Hot Fix Pack release, or the current ActiveX client with eProcess 4.2.2. In this configuration, the following integration functionality is supported:

  • Two, separately-configured Web servers where one server has an isolated region, router, and preferences that are configured for the ActiveX client, while the other Web server is configured for the Open Client.
  • A single Web server where the Open Client is installed in one isolated region and the ActiveX client is installed in another, separate region.

In either configuration, only one client can be used at a time; both clients cannot be run simultaneously.