ACSYS

IBM FileNet Content Federation Services for Content Manager OnDemand

Version 4.5

Configuration Guide

SC19-2711-01

IBM FileNet Content Federation Services for Content Manager OnDemand

Version 4.5

Configuration Guide

SC19-2711-01

Note Before using this information and the product it supports, read the information in “Notices” on page 19.

This edition applies to version 4.5 of IBM FileNet Content Manager (program number 5724-R81), and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright International Business Machines Corporation 2008, 2009.

US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Table of Contents

Table of Contents CFS-CMOD configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Content federation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Configuring Content Manager for CFS-CMOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Installing the OnDemand Web Enablement Kit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Configuring JDBC data sources for the CMOD fixed content device . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Creating the CMOD fixed content device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Configuring CFS-CMOD for use with CMOD on Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Creating the CMOD fixed storage area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Configuring the CMOD viewer in Workplace XT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Enabling Application Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Creating a custom document class in the Content Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Adding properties to the new custom document class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Mapping Content Engine properties to OD application group fields . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Configuring the CFSOD Export utility for document federation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Requirements and background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Usage information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

The export and import process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Export batch mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Export unscheduled mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Records Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Declaring a record. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Declaring a record during the export and import process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Declaring a federated document as a record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Destroying a record. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

16 16 17 17

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 U.S. Patents Disclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

CONTENT FEDERATION SERVICES FOR CONTENT MANAGER ONDEMAND CONFIGURATION GUIDE

5

Table of Contents

CONTENT FEDERATION SERVICES FOR CONTENT MANAGER ONDEMAND CONFIGURATION GUIDE

6

CFS-CMOD configuration

CFS-CMOD configuration Overview This document provides technical details and configuration steps for the three main integration areas between IBM® Content Manager OnDemand (CMOD) and IBM FileNet® Content Federation Services (CFS): Federation of CMOD documents into the CFS system, Records Management control of these federated documents, and Viewer integration into Workplace XT.

Content federation Content federation is a method of providing access to business content stored on multiple computer systems. The content on each system can be generated by different applications and can be stored in different databases. The content stored on one system can be retrieved from another system using a different application than the one used to originally store the content.

Content that is accessible in this way is referred to as federated content.

CFS-CMOD provides a mechanism by which content contained in an IBM Content Manager OnDemand (CMOD) system becomes accessible to an IBM FileNet P8 system. This mechanism consists of two steps: •

Exporting the metadata (CMOD fields and their values), and a document reference identifier as XML

•

Importing this XML into a document object residing in the IBM FileNet P8 system

Configuring Content Manager for CFS-CMOD Follow the procedures in this document to configure the federation of the CMOD documents to IBM FileNet Content Manager.

Installing the OnDemand Web Enablement Kit The Content Engine uses OnDemand Web Enablement Kit (ODWEK) to access the CMOD repositories. ODWEK must be installed on each Content Engine that is used for CFS-CMOD. The minimum ODWEK version required for CFS-CMOD is 8.4.1.0.

See the IBM Content Manager OnDemand Version 8.4.1 Information Center for more information on how install ODWEK. http://publib.boulder.ibm.com/infocenter/cmod/v8r4m1/index.jsp After ODWEK is installed, the application server that runs the Content Engine must be configured to support ODWEK. Follow the steps below for configuring ODWEK in the Content Engine application server.

CONTENT FEDERATION SERVICES FOR CONTENT MANAGER ONDEMAND CONFIGURATION GUIDE

7

Configuring JDBC data sources for the CMOD fixed content device

NOTE: This example shows you how to configure ODWEK using WebSphere on Windows servers.

However, both ODWEK and IBM FileNet Content Manager support various operating systems and application servers.

For ODWEK hardware and software requirements, see: http://www-01.ibm.com/support/docview.wss?rs=129&uid=swg27012104 For IBM FileNet Content Manager hardware and software requirements, see: http://www-01.ibm.com/support/docview.wss?rs=3273&uid=swg27010422 If you are planning to use or if you are already using a different application server and operating system, verify that: •

The appropriate application server startup script is modified to include the full path of the ODWEK installation folder to the operating system PATH and LIBPATH (or the equivalent for your operating system) environment variables.

•

Add the CLASSPATH to include the ODApi.jar file.

1. Log in to the WebSphere Admin Console.

2. Go to Application Server > server1 > Process Definition > Java Virtual Machine 3. Enter the full path of the ODApi.jar file in the Java classpath. Typically, the ODApi.jar file is in following location: UNIX®: /usr/lpp/ars/www/api/ODApi.jar Windows®: C:\Program Files\IBM\OnDemand Web Enablement Kit\api\ODApi.jar 4. Save to the master configuration.

5. Restart WebSphere.

6. Add the full path of the ODWEK installation folder to the operating system PATH environment variables.

Configuring JDBC data sources for the CMOD fixed content device Before the CMOD fixed content device can be created, two JDBC data sources must be configured in the Content Engine. These two data sources must point to the database where the CFS importer tables will be created. The importer tables are created when you create a CMOD fixed content device in the next section.

NOTE: The CFS importer database can be created on either the Content Engine server or the OnDemand server. However, you should create the CFS importer database on the same database server where the GCD and object store databases reside.

CONTENT FEDERATION SERVICES FOR CONTENT MANAGER ONDEMAND CONFIGURATION GUIDE

8

Creating the CMOD fixed content device

See the IBM FileNet Content Manager product documentation for more information about how to create JDBC data sources. http://www-1.ibm.com/support/docview.wss?rs=3278&uid=swg27010422

Creating the CMOD fixed content device The CMOD fixed content device is a Content Engine object that points to a CMOD repository.

Follow the steps below to create the CMOD fixed content device.

1. Start the Enterprise Manager and log in as the administrator user.

2. Right-click Fixed Content Device and select New Fixed Content Device.

3. Click Next in the Welcome screen.

4. Enter a name for the fixed content device and click Next.

5. Enter the following settings for your fixed content device. a. Type: IBM Content Manager OnDemand b. Federation JNDI Data: Name of the data source name created in, “Configure JDBC datasources for the CMOD fixed content device” c. Federation JNDI XA Data: Name of the XA data source name created in, “Configure JDBC datasources for the CMOD fixed content device” d. CMOD Server Name: The OnDemand server name shown in the OnDemand Configurator. e. CMOD User Name: The CMOD administrator user f.

CMOD Password: The CMOD administrator user password

6. Click Test Connection to verify the connection to the OnDemand server.

7. Click Next.

8. Click Finish.

Configuring CFS-CMOD for use with CMOD on Oracle If you are using Content Manager OnDemand with an Oracle database, complete the following steps before you set up a fixed content storage device for use with CFS-CMOD. These steps are needed because CMOD uses integrated Oracle security.

1. On the CMOD Oracle server, do the following: a. Use a tool such as SQLPlus to create an additional Oracle user (also known as the proxy_user). b. Issue this command: ALTER USER cmod_user GRANT CONNECT THROUGH proxy_user;

CONTENT FEDERATION SERVICES FOR CONTENT MANAGER ONDEMAND CONFIGURATION GUIDE

9

Creating the CMOD fixed storage area

2. On the Content Engine application server, use the application server administration console to set up the JDBC data source, and enter the Oracle user name (from Step 1) as follows: proxy_user[cmod_user]/password

Creating the CMOD fixed storage area A fixed storage area is required for importing federated CMOD documents. Follow the steps in this section to create a fixed storage area.

1. Create a shared directory for the storage area. This directory can be either local or remote to the Content Engine.

2. Start Enterprise Manager and expand Object Store > <Object Store Name> > Storage Areas.

3. Right click Storage Areas and select New Storage Area.

4. Click Next in the Welcome screen.

5. Select Initial Site and click Next.

6. Enter a name for the new storage area and click Next.

7. Select Fixed Storage Area and click Next.

8. Select the CMOD fixed content device that you created in â&#x20AC;&#x153;Creating the CMOD fixed content deviceâ&#x20AC;? on page 9 and enter the full path of the staging area that you created in step 1.

9. Click Next in the Select the Size Parameters of the Storage Area screen.

10. Click Finish.

Configuring the CMOD viewer in Workplace XT CMOD Documents that have been federated are accessible through the IBM FileNet Workplace XT client, which supports browser-based viewing of CMOD documents in the same way as WEBi or a custom client built with ODWEK. NOTE: You can view OnDemand documents from Workplace XT, but not from Workplace. In Workplace XT, access to OnDemand content is limited to viewing and the Download action menu is disabled. In Workplace, there is no support for viewing OnDemand documents. The Download option in Workplace is enabled for OnDemand documents, but the download will not contain a fully formatted OnDemand document.

To support viewing of federated AFP and Line Data documents in a Content Manager OnDemand repository, complete these steps: 1. Install the ODWEK Toolkit on each Workplace XT server.

2. Configure the Line Data viewer so that it can be used through Workplace XT. 3. Run the AFP plug-in on all client machines that will be used to view AFP documents.

4. In the Workplace XT General Settings, specify the name and password of the user account used to authenticate with a Content Manager OnDemand server.

CONTENT FEDERATION SERVICES FOR CONTENT MANAGER ONDEMAND CONFIGURATION GUIDE

10

Enabling Application Groups

For details about these steps, see the following FileNet P8 Documentation help topics: •

Install AFP and Line Data viewers, located under System Administration > Application Engine and Workplace XT Administration > Workplace XT administration.

•

General Settings for IBM Content Manager OnDemand (Workplace XT), located under User help > Actions, preferences, and tools > Site preferences > General Preferences > IBM Content Manager OnDemand.

Enabling Application Groups Enable Application Groups through the OnDemand Administrator client to allow document federation.

1. To modify an existing Application Group, click on the Application Groups object, right-click on the desired Application Group, and then select Update from the menu.

2. To allow document federation for a new Application Group, right-click on the Application Group object and select New Application Group from the pop-up menu.

3. Click on the Advanced button on the General tab 4. In the Interoperate with FileNet P8 section of the resulting dialog box, check Yes to the question Use Content Federation Services (CFS-OD)?

The Federate Documents Automatically option causes the OnDemand server to generate metadata information for each existing document as well as any new documents loaded to the application group. If this option is not checked, you must manually specify which documents to federate through an OnDemand client. See “Export unscheduled mode” on page 16 for more details.

If the Enable FileNet Records Manager to records declare automatically is checked, the OnDemand server assumes that any documents that are federated into FileNet P8 are declared as records to FileNet Records Manager. If you do not select this check box, then the documents that are federated into FileNet are not declared as records in FileNet P8 Records Manager.

5. Click on the Field Definition tab and add a new database field. Enter a name for the database field and click Add. 6. Click on the Field Information tab and select the newly created filed from the Name drop-down.

7. Leave the Type as Filter and change the Data Type to Small Int (2).

8. Select the CFS-OD box.

9. Continue updating or creating the Application Group and click OK.

Creating a custom document class in the Content Engine Create a custom document class that corresponds to an CFS enabled application group. Although this procedure is optional, it is the best practice.

CONTENT FEDERATION SERVICES FOR CONTENT MANAGER ONDEMAND CONFIGURATION GUIDE

11

Adding properties to the new custom document class

For example, the SAMPLE01 application group is an CFS enabled application group and you can create a custom document class that corresponds to this application group.

Follow these steps to create a custom document class in the Content Engine.

1. Start Enterprise Manager and log in as the administrator user.

2. Right-click the Document Class node and select New Class.

3. Enter the name OD-Sample01 and click Next.

4. Click Next in the Select Property Attributes screen.

5. Click Next in the Specify Content Storage Parameters screen.

6. Click Next in the Configure Auditing screen.

7. Click Finish.

Adding properties to the new custom document class The new custom document class that you created in â&#x20AC;&#x153;Creating a custom document class in the Content Engineâ&#x20AC;? on page 11 does not have any custom properties. You must add new properties to this document class that correspond to the application group fields.

Follow these steps to add new properties to the document class that corresponds to the SAMPLE01 application group fields.

1. Right-click the new custom document class. (OD-Sample01, for example) and select Add Properties to Class.

2. Click Next in the Welcome screen.

3. Click New. 4. Click Next in the Create a Property Template welcome screen.

5. Enter a name and select an appropriate data type. Table 1 lists properties and their data types.

Table 1: Add properties to class CE Property Name

Data Type

OD-P8ID

Integer

OD-doc_descr

String

OD-time_created

DateTime

OD-file_path

String

6. Click Next in the Select a Choice List screen.

7. Select Single and click Next in the Single or Multi-value screen.

8. Click Finish.

9. Repeat steps 4 - 8 for each property.

CONTENT FEDERATION SERVICES FOR CONTENT MANAGER ONDEMAND CONFIGURATION GUIDE

12

Mapping Content Engine properties to OD application group fields

Mapping Content Engine properties to OD application group fields Mapping the application group fields to the Content Engine properties allows you to federate the metadata to the Content Engine. A Content Engine property can be mapped to only one application group field.

Follow these steps to map the Content Engine properties to the OD application group fields.

1. Start Enterprise Manager and login as the administrator user.

2. Right-click the object store and select Properties.

3. Select the Configuration tab.

4. Click Add/Edit.

5. In the Fixed Content Device drop-down menu, select the CMOD fixed content device that you created in “Creating the CMOD fixed content device” on page 9“.

6. After a fixed content device is selected, you will see a list of CFS enabled application group in the Document Class panel. Select a CFS enabled application group. For example, select the SAMPLE01 application group.

7. In the Content Engine document class panel, select the custom document class that you created in “Creating a custom document class in the Content Engine” on page 11. For example, select the OD-Sample01 document class.

8. After you choose the application group and the Content Engine document class, click Add. 9. Map the application group fields to the Content Engine properties.

Select an application group field from the External Repository Available Properties list and select a matching Content Engine property from the Content Engine Available Properties list.

After choosing a field and a property, click Add. Repeat this for all the properties. Click OK when you are finished.

External Property Name

Data Type

CE Property Name

Data Type

doc_descr

String

OD-doc_descr

String

file_path

String

OD-file_path

String

P8ID

Integer

OD-P8ID

Integer

time_created

DateTime

OD-time_created

DateTime

Figure 1 - Mapping application group fields to Content Engine Properties

For example, Figure 1 shows the current property mappings.

NOTE: Map an application group field to the DocumentTitle system property in the Content Engine. This mapping helps when you query for the federated CMOD documents in Workplace XT.

CONTENT FEDERATION SERVICES FOR CONTENT MANAGER ONDEMAND CONFIGURATION GUIDE

13

Configuring the CFSOD Export utility for document federation Requirements and background

Configuring the CFSOD Export utility for document federation The CFSOD exporter is a Java application that uses JDBC drivers to connect to the OD database tables and CFS importer tables. The CFSOD exporter is designed to run anywhere, but the best practice is to run it on the Content Engine.

The CFSOD exporter is included with ODWEK.

Requirements and background •

•

The CFSOD Export utility is a Java application that uses jdbc drivers to connect to the OnDemand database.

–

You must install the correct Type 4 jdbc driver for your OnDemand database type (DB2, Oracle or MSSQL Server).

–

The jdbc driver must be in the classpath for the CFSOD Exporter utility

The OnDemand database instance contains all of the tables necessary for the CFSOD Export utility to function: –

ARSCFSODWORK, CFS_IMP_QUEUE, CFS_IMP_QUEUE_ERROR, CFS_IMP_SESSION, CFS_REPOSITORY_MAP, FDB_VERSION_SERIES.

•

The utility was designed to be scheduled as a cron job (for UNIX systems) or via Windows Scheduler. A typical schedule would run the utility once a day typically when other system utilization is low.

•

In order to run the CFSOD Exporter utility, you need to have at least a 1.4.2 JVM installed.

Usage information A typical command line execution of the CFSOD Exporter utility might look like the following example: java -classpath <jdbc driver>;CFSODExporter.jar [configure] [options]

The [configure] action is used to save all the [options] specified to a configuration file.

The following options are supported: -u <userid> The user id needed to authenticate to the database instance.

-p <password> The user's password needed to authenticate to the database instance.

-o <port> The connection port number associated with the database instance.

-I <db instance> The database instance name.

-d <path> The directory in which trace files can be stored.

-t <export trace> Enable tracing for the utility. A value of 0 disables trace and a value of 1 enables trace.

CONTENT FEDERATION SERVICES FOR CONTENT MANAGER ONDEMAND CONFIGURATION GUIDE

14

The export and import process Usage information

-n <number> As mentioned in the Export and Import Process section, the number of documents exported per session entry (in the CFS_IMP_SESSION table) can be configured.

Provide a number between 1 and 250.

-f <path> If the 'configure' action is used as described above, this is the complete path and filename to write the configuration parameters file. Otherwise, this is the complete path and filename from which to read configuration parameters.

The export and import process The communication from the FileNet CFS system to an OnDemand server is accomplished through the OnDemand Web Enablement Kit Application Programming Interfaces (ODWEK API).

ODWEK configuration parameters are provided during the “Create a Fixed Content Device” wizard, and these parameters are necessary to initialize the ODWEK server interface.

After you identify the Fixed Content Device and Storage Area, you must create a mapping between FileNet Document Classes and OnDemand Application Groups. However, you must first enable OnDemand Application Groups for federation through the OnDemand Administrative Client. See “Enabling Application Groups” on page 11 for details on enabling an Application Group for federation.

After you enable an OnDemand Application Group for federation, the application becomes available in the FileNet Enterprise Manager’s Content Federation properties section. You need to map the Application Group fields to the correct type of Document Class property (For example, Integer, Date, and other properties).

When a mapping exists between the P8 Document Class and an OnDemand Application Group, document federation can begin. Federation is a two part process: import and export. The import process runs as part of CFS, and periodically polls database tables for new items to import. These items consist of XML, which describes the document's metadata.

The export process is handled by the CFSOD Exporter utility, which creates XML for each document which can be ingested by the importer process. You can schedule the CFSOD Exporter utility to run at times when the OnDemand and FileNet systems are not very active. See “Configuring the CFSOD Export utility for document federation” on page 14 for details on configuring the CFSOD Exporter utility. You can export OnDemand documents in two modes: batch and unscheduled. 0

Export batch mode Batch mode export will, based on a user-defined schedule, export OnDemand metadata for all documents within an Application Group. After you enable an Application Group for federation, OnDemand populates the ARSCFSODWORK database table with metadata for each document loaded in the Application Group.

Before the CFS-CMOD Exporter utility can export the metadata, the utility must first query the CFS_REPOSITORY_MAP database table to determine if the Application Group has been successfully mapped to FileNet Document Classes.

CONTENT FEDERATION SERVICES FOR CONTENT MANAGER ONDEMAND CONFIGURATION GUIDE

15

Export unscheduled mode Declaring a record during the export and import process

If the mapping is successful, the CFS-CMOD Exporter utility builds XML from the metadata for each related OnDemand document, and places XML into the CFS_IMP_QUEUE database table.

The utility validates the XML based on the CFS import XML schema, and then imports the XML into the FileNet P8 system. Each row in the CFS_IMP_QUEUE is given a session identifier. This session identifier is entered into the CFS_IMP_SESSION table. When the import process runs, it receives a session identifier from the CFS_IMP_SESSION table and processes all rows in the CFS_IMP_QUEUE table which match that session identifier. You can configure the number of CFS_IMP_QUEUE rows per session identifier, but the maximum of 250.

Export unscheduled mode Unscheduled mode export allows you to pick and choose OnDemand documents to federate. The OnDemand Application Group must be marked to allow federation through the OnDemand Administrator client. See “Enabling Application Groups” on page 11 for details on enabling an Application Group for federation.

To select documents for federation, initiate a search from one of the OnDemand clients (Windows client or WEBi). You can select a subset of the documents in the search results. After you select the documents, submit a federation request, which causes the OnDemand server to create entries in the ARSCFSODWORK database table with document metadata, and to notify the client that the request to federate documents has been completed. The CFS-CMOD Export utility proceeds to export the documents in a manner identical to the batch mode described above.

Records Management All of the features and controls from IBM FileNet Records Manager are applicable to federated CMOD documents. Document retention in a CMOD system is defined by the length of time the documents are maintained and the type of media on which the documents are stored. However, CMOD documents that have been declared as records under Records Manager control are locked down. CMOD will not apply document retention policy to these documents until Records Manager indicates that these documents can be destroyed.

Declaring a record You can declare federated CMOD documents as records by the following methods:

Declaring a record during the export and import process As part of the Batch Mode export and import process described previously, an Application Group configuration option is available to automatically declare documents as records. This option is accessed through the OnDemand Administrator Client as described in “Enabling Application Groups” on page 11. When you select this option, it causes the OnDemand server to internally mark all documents as records.

Similarly, if the Application Group is not set to automatically federate documents but is configured to automatically declare documents as records, documents which are federated in unscheduled

CONTENT FEDERATION SERVICES FOR CONTENT MANAGER ONDEMAND CONFIGURATION GUIDE

16

Destroying a record Declaring a federated document as a record

mode (as described in â&#x20AC;&#x153;Export unscheduled modeâ&#x20AC;? on page 16) causes the OnDemand server to internally mark these documents as records.

Although the exported documents are placed on hold in the CMOD server, they must still be manually declared as records through the IBM FileNet Records Manager client.

Declaring a federated document as a record You can place a document on hold by declaring the document as a record through IBM FileNet Records Manager. After you declare a federated document as a record, CFS communicates the declaration to the CMOD server through the OnDemand Web Enablement Kit (ODWEK). The CMOD server also declares the document as a record. If the Application Group has the option to automatically declare records enabled, the request from IBM FileNet Records Manager is ignored by the CMOD server, preventing unnecessary processing by the CMOD server.

Destroying a record The disposition of a record can take many forms. However, the only form relevant to federated CMOD documents declared as records is destroy. When a federated CMOD document record is eligible to be destroyed, CFS communicates this eligibility to the CMOD server through ODWEK. At this time, the CMOD document record is removed and the document is deleted.

CONTENT FEDERATION SERVICES FOR CONTENT MANAGER ONDEMAND CONFIGURATION GUIDE

17

Destroying a record Declaring a federated document as a record

CONTENT FEDERATION SERVICES FOR CONTENT MANAGER ONDEMAND CONFIGURATION GUIDE

18

Notices

Notices This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user’s responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan, Ltd. 3-2-12, Roppongi, Minato-ku, Tokyo 106-8711 Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs

CONTENT FEDERATION SERVICES FOR CONTENT MANAGER ONDEMAND CONFIGURATION GUIDE

19

Notices

(including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation J46A/G4 555 Bailey Avenue San Jose, CA 95141-1003 U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to nonIBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBMâ&#x20AC;&#x2122;s future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample programs.

CONTENT FEDERATION SERVICES FOR CONTENT MANAGER ONDEMAND CONFIGURATION GUIDE

20

Trademarks

Trademarks IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol (® or ™), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at “Copyright and trademark information” at www.ibm.com/legal/copytrade.shtml.

Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Other company, product, and service names may be trademarks or service marks of others.

U.S. Patents Disclosure This product incorporates technology covered by one or more of the following patents: U.S. Patent Numbers: 6,094,505; 5,768,416; 5,625,465; 5,369,508; 5,258,855.

CONTENT FEDERATION SERVICES FOR CONTENT MANAGER ONDEMAND CONFIGURATION GUIDE

21

Program Number: 5724-R81

Printed in USA

SC19-2711-01