FileNet P8 CFS CM OnDemand, Version 5.2.1              

Configuring the content federation exporter for document federation

Configure and run the content federation exporter to federate documents to Content Platform Engine. The exporter is included with ODWEK.

Before you begin

Ensure that you install the correct Type 4 JDBC driver for your Content Manager OnDemand database type and that the JDBC driver is in the class path for the content federation exporter.

For the documents that you plan to federate, ensure that you enabled their application groups for content federation and mapped their application group fields to Content Platform Engine document classes.

About this task

The content federation exporter is a Java™ application that uses JDBC drivers to connect to the Content Manager OnDemand database tables and the content federation importer tables. Typically, the exporter runs on the Content Platform Engine server.

You can export Content Manager OnDemand documents in either batch or unscheduled mode. Batch mode is used to export all Content Manager OnDemand documents in application groups that have the Federate Documents Automatically option enabled. In unscheduled mode, documents must be manually selected for federation by running a search from one of the Content Manager OnDemand client applications. After you select documents from the search results, you submit a federation request to trigger the export of the documents.

Restrictions:
  • A Content Manager OnDemand document can be exported only one time. Changes to Content Manager OnDemand document fields cannot be propagated to Content Platform Engine.
  • After you export documents from Content Manager OnDemand, do not modify the Application Group or the Application ID of the source documents in Content Manager OnDemand. If the Application Group or the Application ID of the source documents are modified, the content of the federated documents is no longer accessible from Content Platform Engine.

Procedure

To configure the content federation exporter for document federation:

  1. Generate a configuration file with all of the necessary information for the exporter to use. For example, enter the following command to generate the exporter_fcd.config configuration file:
    java –cp "C:\jdbc\db2jcc.jar";"C:\jdbc\db2jcc_license_cu.jar";"C:\Program
    Files\IBM\OnDemand Web Enablement Kit\exporter\CFSODExporter.jar" 
    com.ibm.cm.od.exporter.Exporter configure -u odadmin,ceadmin OD_DB_UserID,CE_DB_UserID -p
    oddb_password,cedb_password oduser,tester -e db2,db2 -I OD_DB_Instance,CFS_DB_Instance -h od_host,cfs_host
    -o 50000,50000 -d C:/CMODExporter/trace -n 200 -t 1 -f
    C:/CMODExporter/config/exporter_fcd.config
  2. Run the exporter to start federating documents to Content Platform Engine. For example, enter the following command to run the exporter with the exporter_fcd.config configuration file:
    java –cp "C:\jdbc\db2jcc.jar";"C:\jdbc\db2jcc_license_cu.jar";"C:\Program
    Files\IBM\OnDemand Web Enablement Kit\exporter\CFSODExporter.jar"
    com.ibm.cm.od.exporter.Exporter federate -f
    C:\CMODExporter\config\exporter_fcd.config

What to do next

Schedule the exporter to run as a cron job on UNIX systems or by using Windows Scheduler on Windows systems. In a typical schedule, the utility runs one time a day when the Content Manager OnDemand and Content Platform Engine systems are not active.


Last updated: October 2015
cfsod014.htm

© Copyright IBM Corporation 2015.