Getting Started with IBM Web Content Manager: Web Content Integrator

In my previous post, we reviewed the basics of IBM Web Content Manager (WCM). Using those fundamentals as background, let’s take a look at Web Content Integrator.

Web Content Integrator

Web Content Integrator (WCI) automates creation of web content from an external source. It does so by specifying an input format that maps to your WCM site. The input format is simply XML (RSS) and could be dynamically generated on schedule or created once to facilitate a batch import. The input-file separation is quite nice. The external system never needs to interface directly with WCM. It just needs to know how to create formatted files that WCM knows how to read. And once the file is created, WCM knows how to do the rest.

YouTube Example

In the previous post, we created an authoring and presentation template to showcase our company’s YouTube videos.  WCM doesn’t actually host the videos, it knows just enough information of how to render a YouTube player on our site. So rather than ask our team to manually create our many YouTube videos in WCM, we’ll create a simply feed that shows how we can import them automatically.

Feed Format

Our XML (RSS) feed supplies content that conforms to our existing authoring template. The authoring template will ask our users for just a few fields of information needed to build our YouTube player.


WCM Content

Our XML input file will essentially give WCM exactly this information. And by doing so, WCM will create our content at the defined location.  Let’s look at the XML.

<?xml version="1.0"?>
<rss version="2.0" xmlns:ibmwcm="" >
 <title>YouTube Feed</title>
 <description>An example RSS Feed for YouTube videos</description>
 <lastBuildDate>Tue, 21 Apr 2015 10:31:00 EST</lastBuildDate>
 <title>How Data Helped Bobby Jones Golf Swing</title>
 <description>Bobby Jones' golf swing was a subject worthy of study. He analyzed the pattern of his swing, producing results unmatched in his day. By focusing on the data that really counts, everyone can perform better and smarter every day.</description>
 <pubDate>Tue, 21 Apr 2015 10:31:00 EST</pubDate>
 <ibmwcm:authoringTemplate>Add YouTube Video</ibmwcm:authoringTemplate>
 <ibmwcm:workflow name="Express Workflow">
 <ibmwcm:workflowStage>Publish Stage</ibmwcm:workflowStage>
 Tue, 21 Apr 2015 10:31:00 EST
 <ibmwcm:element name="width">
 <ibmwcm:element name="height">
 <ibmwcm:element name="videoid">
 <ibmwcm:access type="user">[all users]</ibmwcm:access>

There’s one point worth making. In the previous post, we did not create the “Express Workflow” in the YouTube library. The “Express Workflow” was re-used from another library to make the post simpler. If you do not have a workflow, you can omit the <ibmwcm:workflow> node (and child node). Or you can create your own simple workflow.

The XML above is saved as a file and simply hosted on my HTTP server.

Importing the Feed

To begin importing the feed to create content, we begin with creating a credential vault slot. The slot will hold the ID that has permission to create content in WCM. You’ll find this option in Portal administration’s Access -> Credential Vault page.

WCM Vault Slot

Next we create a Web Content Integrator Feed. This is done from Portal administration’s Portal Content -> Feed Configurations.

Web Content Integrator Feed

Notice that my feed URL is pointing to the file we created – the one hosted on my HTTP server. You’ll also specify the vault slot created earlier. You can select the “Save and Consume” button to immediately import the content.  Or you can set up a Feed Job from Portal administration to consume a feed on a regular interval. The result should be a new content item in the Videos site area.

WCI Content

Next Steps

This was a basic example For more complete information, see the extension documentation on importing other artifacts like site areas, workflow, security, files, and images.

One thought on “Getting Started with IBM Web Content Manager: Web Content Integrator”

Leave a Reply

Your email address will not be published.