Distributing an Integrated Application

This section discusses considerations related to integrating an application with FileNet Workplace and installing an integrated application:

Enable FileNet Workplace User Tokens

In order to integrate a third-party client application with FileNet Workplace, user tokens must be enabled. The User Token Settings are contained in the Site Bootstrap Preferences and can be manually configured through FileNet Workplace as follows:

  1. Login into FileNet Workplace as a user that has sufficient access rights to modify the Site Bootstrap Preferences.
  2. Select the Admin tab.
  3. Select Site Preferences.
  4. Select Bootstrap.
  5. Set the value of Generate user tokens to "Yes".
  6. Set the value of Accept user tokens to "Yes".
  7. Set the value of Token timeout interval to any value between one and 15 minutes.

Compatibility Requirements

Information about the minimum platform requirements for integrating third-party client applications with FileNet Workplace can be found in FileNet P8 Hardware and Software Requirements. To download this document from the IBM support page, see Accessing IBM FileNet documentation.

Merge Module Support for Custom Application Installation

Third-party client applications must install the Workplace Application Integration Toolkit during installation of their application. In order to support this installation requirement, the Toolkit is provided as an InstallShield merge module (.msm file) which can be built into the installer for a custom application. The FnAppIntCore.msm merge module is located in the Application Engine Source\client directory, which is provided with a custom Application Engine installation that includes the Workplace Source Code option.

The following steps provide a general overview of how to use the FnAppIntCore.msm merge module within an InstallShield project:

  1. Launch InstallShield.
  2. Create a project with various features and components.
  3. Click Redistributables in the left-hand pane.
    The list of merge modules located on the client will appear in the upper-middle pane.
  4. Select the FileNet P8 Workplace Application Integration Client Toolkit 4.0.0 merge module (FnAppIntCore.msm).
    As a result, all other dependent merge modules will automatically become selected (that is, the merge modules which contain the MFC dlls).
  5. Choose the feature(s) with which to associate the files contained within the merge module.
    For example, FileNet associates the Workplace Application Integration API Toolkit with the Toolkit feature contained in the Workplace Application Integration installer. As a result, when the user installs the Toolkit feature, all of the core components necessary for running and utilizing Application Integration with Workplace are installed.

When the project is built, a series of COM extraction calls are displayed in the output window indicating that the merge module is being incorporated into the product. All of the core DLLs contained in the merge module will either be placed in the Disk output directory of the install project, or included in the setup package (that is, Setup.exe) if the install project is configured to behave as a single executable.

For more information regarding how to use a merge module within an InstallShield project, see the InstallShield Help. When using a product other than InstallShield to develop the installer for a client application, refer to the Help documentation for that product for information about working with merge modules.