Chapter 7. Publishing Content Manager content 123
4. Click Add Files to Import.
5. Select a file (for instance, a text file with insurance information) and click OK.
6. Select Insurance Type in the Item Type field, and enter values for the
attributes fields.
7. Click Import.
8. Repeat the above steps to import more documents into the Content Manager
system.
7.3 Federated content component
There are three ways of retrieving data from Content Manager and publishing the
data to LWWCM Web sites. One way is to use the federated content component.
In this section, we discuss what it is, why we use it, how to set it up with sample
codes, and how to put it all together.
7.3.1 What is a federated content component?
A federated content component is a component used to retrieve and store
information from a federated data source, such as Content Manager. Working
with Content Manager data, a federated content component stores a reference to
a Content Manager document in LWWCM. From LWWCM, users can perform
searches for federated content and add the results of the search into the
LWWCM Web pages. These searches can be for content or for specific federated
attributes.
Using federated content components, you can:
򐂰 Search Content Manager objects using a federated search template and
select a reference to it to be stored in the content.
򐂰 Store federated content component searches as reusable library
components.
򐂰 Add federated content components to content templates.
򐂰 Clear Content Manager content reference from the component and select a
new reference.
򐂰 View attributes of the Content Manager content reference.
򐂰 Preview the Content Manager content.
124 Lotus Workplace Web Content Management and Content Manager Working Together
7.3.2 Why use federated content components?
Using federated content components enables users to have access to multiple
sources of information. This means that a user can use one query to search
against multiple sources to get a result set. There is no need for the user to
understand how and where the information is stored.
7.3.3 Setting up a federated content component
To use a federated content component, you need to configure the system to be
capable of performing federated searches. In addition, federated entity and
search templates must be defined in the Information Integrator for Content
Administration Client. Once they are defined, we need to create the federated
content component (either in a component library or within a content object) and
include it in the Web page content.
Prerequisites and configuration
The following is a list of tips and prerequisites for using the federated content
components:
򐂰 Information Integrator for Content V8.2 with Fix Pack 3 or greater must be
installed on your federated data server.
򐂰 Check your Information Integrator for Content configuration and make sure
that you have the
cmbds.ini file under the <CMGMT_HOME> directory. Refer
to Chapter 5, “Before you begin integration: pre-integration validation” on
page 63 for more detailed information on the setup.
򐂰 To link to a federated data source, the following parameters must be edited
within the
Connector section of the connect.cfg file.
DefaultServerAlias: alias name created when the Information Integrator for
Content is installed.
DefaultUsername: default user ID used to log on to the federated
database.
DefaultPassword: password for the user ID above.
MaxResultsReturned: maximum number of results returned by the search
query.
Example 7-1 shows a code snippet of the connect.cfg file with these
parameters.
Example 7-1 connect.cfg: code snippet
<FederatedConnector>
<DefaultServerAlias value = "ICMNLSDB" />
<DefaultUsername value = "icmadmin" />

Get IBM Workplace Web Content Management Java Edition V2 and IBM DB2 Content Manager V8 Working Together now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.