Using JiGlue with ASP.NET - Issues and Guidelines

When developing a FileNet Open Client application, you must use JiGlue to provide the COM Bridge between the data providers and the Process Engine services (accessed via the Process Java™ APIs). The JiGlue COM Bridge provides the ability to make COM-based VB.NET (or other .NET-compatible language) calls to the Process Java APIs equivalent to native Java statements for nearly all Windows programming tasks.

There are a number of known ASP.NET and JiGlue COM Bridge-related issues and guidelines to keep in mind when creating your Process Open Client ASPX pages and User Controls, including:

Using JiGlue Example

To use JiGlue to create and instantiate a Process VWSession object and log on, you might use VB.NET code similar to the following:

Imports Jiglue
Public Class FnJiglueSample
    Protected m_aJiglue As New JiglueUtil()
    Public Function Logon() As Boolean
    ...
      'Use JiGlue to create a VWSession object and logon
      Dim aVWSession As Object
      aVWSession  = m_aJiglue.newinstance("filenet.vw.api.VWSession")
      SetVWSession(aVWSession)
      aVWSession.logon(strUserName,strPassWord,strRouterURL)
    ...
    End Function
   ...
End Class

where strRouterURL is the URL of the Process Engine connection point.

Declaring Integer Arrays

If you want to declare an integer array, be aware that in Visual Basic or VB.NET, an integer is a 16-bit value, whereas in Java (and for the Process APIs), an integer is a 32-bit value. If, for example, you specify a 2-byte integer array in Visual Basic, it might be mapped in JiGlue to java.lang.Short, thereby causing the Process Java API to throw an exception.

Additional COM-related Issues

The following additional COM-related issues and guidelines should be kept in mind when developing a Process Open Client application:

For Additional Information

See also: