 |
 |
|
|
|
Issues Related to Using JiGlue and ASP.NET
When developing a Process Open Client application, you must use
JiGlue to provide the COM Bridge between the Data Providers and the Process
Engine services (which are accessed via the Process Java APIs). However,
there are a number of issues that arise when JiGlue is used with the ASP.NET
framework. Before you begin developing with JiGlue and .NET, review the
issues outlined in Developing
with IDM COM Objects and JiGlue in the .NET Environment, as well as
the following considerations:
- JiGlue and Java Runtime Environment (JRE) - Your JRE must
be installed in its default directory in order for JiGlue to work properly.
For additional information, see Configuring
the Java Runtime Environment (JRE).
- JiGlue and Data Providers - When you use the FileNet Process
Open Client out-of-the-box Step Processor and the FnProcessStepProcDP
Data Provider, the Data Provider provides the interface to JiGlue, thereby
insulating your ASPX page and the User Controls from JiGlue and the
Process Engine server. No references to JiGlue should be made outside
the Data Provider. If you are not going to use the out-of-the-box
Step Processor and the FnProcessStepProcDP Data Provider, you
will need to specify a Data Provider that will provide the JiGlue interface.
- JiGlue Date Format - When retrieving data via calls to JiGlue, be aware that dates are returned
in the UTC-ISO date format.
For Additional Information
For additional information on developing with JiGlue and FileNet Open
Client, also see:
|