Skip navigation FileNet logo
  Open Client Developer's Guide
  Search  |  Index  |  Glossary   |  
Open menu Overview
Open menu Open Client Architecture
Close menu Developing for Process
  Open menu Process Overview
  Close menu Preparing for Development
    Setup Checklist
    PJAC
    PJAC Files
    Close menu Installing the PDE
      Configuring the JRE
      Starting a Local Process Router
      Close menu Setting Up for JiGlue
        JiGlueand ASP.NET Issues
        Configuring the JiGlue COM Bridge
        JiGlue Java-COM Data Types
        JiGlue Programming Guidelines
  Open menu HTML Step and Launch Processors
  Java Processors
  Component-Integrator Work Performer
  Open menu Deploying Process Applications
Open menu Error and Exception Handling
Open menu Customizing the Framework
Globalization / Localization
Open menu General Information
   

Setting Up for JiGlue Development

The FileNet-supplied JiGlue COM Bridge provides a translation layer between the Process Java APIs and COM. JiGlue is required to use Web Services whenever a COM application, such as a .NET-based application, must communicate with the Process Engine. 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.

Before you can start using JiGlue, you must first configure the JiGlue COM Bridge on your development system. In addition, there are issues associated with using JiGlue and .NET, as well as some JiGlue-related programming guidelines you should be aware of before you set up JiGlue and start using it to develop Process Open Client applications.

Topics include: