Untitled Document
Table of contents | Next | Previous
Integration with other Systems
The following document describes the integration options with Portal
Document Manager, as well as how third party Enterprise Content Management
(ECM) systems can be integrated with WCM.
Portal Document Manager
As of version 6.1, Document Manager is no longer available in WebSphere
Portal. After migrating your primary data, you must replace Web content
previously stored as documents in a document library with either file resource
components or file resource elements stored in authoring templates, content
items, sites, or site areas.
For more information, see the "Document migration, version 5.1 to
6.1" topic in the Lotus Web Content Management information center at the
following address:
http://publib.boulder.ibm.com/infocenter/wcmdoc/v6r0/index.jsp?topic=/com.ibm.lo
tus.wcm.doc/wcm/wcm_migration_pdm_51.html
Migration to IBM WebSphere Portal version 6.1 is being delivered in two
phases. The first phase, available today, is migration from version 5.1 to 6.1.
Migration from version 6.0 to 6.1, and of the Document Manager content, will be
available in the near future. For more Information, refer to "Migration
Limitations in WebSphere Portal version 6.1" at the following address:
http://www-1.ibm.com/support/docview.wss?rs=899&uid=swg21312856
ECM Integration
In this section we describe an overview of how third party Enterprise
Content Management (ECM) systems can be integrated with WCM.
Organizations around the world use different types of ECM solutions and rely
on WebSphere Portal to aggregate content and applications from different
sources.
It is common for third party ECM software to provide a standard JSR 168
portlet that can be used with the WebSphere Portal environment. However, this
solution does not make use of the key WebSphere Portal capabilities such as
search, security and personalized content delivery.
To overcome this limitation, the IBM Software Services of Lotus (ISSL) team
has developed an asset called the IBM Web Content Integrator (WCI).
WCI allows content created in third party ECM systems to be published in WCM
and thus making it available to the WebSphere Portal environment. WCM is part
of WebSphere Portal and can very easily make use of the security features,
search capability and deliver personalized content.
WCI uses the WCM API to consume content from the ECM system. It requires a
RSS/ATOM feed that stores the META data and data and adheres to the IBM WCI
specification.
The working of the IBM WCI can be best explained by describing the various
entities involved.
Feed Producer
This is a custom application that is built at the third party ECM level that
uses the IBM WCI specification to produce the RSS/ATOM feed.
RSS/ATOM Feed
This is the RSS/ATOM Feed that is generated by the third party ECM custom
application and contains the META data and data required by WCM.
WCI
IBM WCI is deployed on the WebSphere Portal environment and consumes the
RSS/ATOM feed and uses the META data information from the feed to create new,
update existing or delete WCM content.
Figure: IBM Web Content Integrator