FileNet P8 CFS CM OnDemand, Version 5.2.1              

Setting up Content Federation Services for Content Manager OnDemand

To set up Content Federation Services for Content Manager OnDemand, you must first configure the Content Manager OnDemand system to work with the content federation system. You then configure communication between Content Platform Engine and Content Manager OnDemand, map the Content Platform Engine properties to the Content Manager OnDemand application group fields, and configure the content federation exporter to federate documents to Content Platform Engine.

Before you begin

Ensure that the CFS-IS Extensions add-on is installed in the object store in which you plan to store the federated documents.

Procedure

To set up Content Federation Services for Content Manager OnDemand:

  1. Configure the Content Manager OnDemand system:
    1. Enable the Content Federation Services for Content Manager OnDemand feature.
    2. Enable application groups for content federation.
    3. If you use Content Manager OnDemand with an Oracle database, use a tool such as SQLPlus to create an additional Oracle user, who is known as the proxy user, Run the following command on the Oracle server: ALTER USER cmod_user GRANT CONNECT THROUGH proxy_user;.
  2. Configure Content Platform Engine.
    1. Install the Content Manager OnDemand Web Enablement Kit.
    2. Create JDBC data sources in the Content Platform Engine application server to connect to the federator database. Use the Configure Object Store JDBC Data Sources task in Configuration Manager to create the data sources. The federator database can be created on either the Content Platform Engine server or the Content Manager OnDemand server.
      Tip: If you use Content Manager OnDemand with an Oracle database, enter the Oracle user name as proxy_user[cmod_user]/password.
    3. Create a Content Manager OnDemand fixed storage device. In the domain navigation pane of the Content Platform Engine administration console, click Global Configuration > Administration > Fixed Content Devices and click New.
      Tip: Ensure that the specified user has access privileges to the Content Manager OnDemand application groups that are enabled for federation. Also, ensure that the user has a minimum timeout period of 30 minutes to prevent a timeout during a content retrieval operation. The timeout period for a Content Manager OnDemand user is defined in the Content Manager OnDemand Administrator utility.
    4. Create a Content Manager OnDemand fixed storage area. In the navigation pane of the object store in which you plan to store the federated documents, click Administrative > Storage > Storage Areas and click New. Select Fixed for the storage area type and complete the wizard.
    5. Create custom document classes and properties to correspond to the Content Manager OnDemand application groups and fields that are enabled for content federation.
    6. Map the Content Platform Engine properties to the Content Manager OnDemand application group fields.
  3. Configure the content federation exporter to federate documents to Content Platform Engine.
    Important: To support defensible disposition for Content Federation Services for Content Manager OnDemand documents, the documents must be locked down before export begins. Locking down the documents ensures that the documents are retained in the Content Manager OnDemand repository. Document operations such as deletions are initiated by Content Platform Engine.
  4. Optional: To support viewing of federated AFP and Line Data documents by using Workplace XT, configure the Content Manager OnDemand viewer in Workplace XT.
    Restriction: Content Manager OnDemand content can be viewed in Workplace XT but cannot be downloaded.


Last updated: October 2015
cfsod003.htm

© Copyright IBM Corporation 2015.