At Base22
, we've been working on a content migration utility using the IBM Web Content Integrator (WCI) for WebSphere Portal. The Web Content Integrator is a tool in WebSphere Portal that allows you to use RSS feeds to add, update, and delete content into the Portal's Lotus Web Content Management (LWCM) system. This can be useful for migrating content or publishing content from some other source system besides LWCM. The documentation is a bit sparse, so here's some things I've learned about using WCI to delete items in LWCM. These lessons were learned using IBM WebSphere Portal 6.1.5.
In order for the Web Content Integrator to process a delete action, the ibmwcm:element block must be present in the item. The ibmwcm:element must contain both an ibmwcm:type and ibmwcm:source node. In the case of a delete action, the ibmwcm:source node can be empty, but it must be present. Note also that it is not necessary for the pubDate of the item to match the original pubDate that was used by the item when the original feed was used to add it.
Example Item Node for Deleting a Library Image Component
The rules are similar for a Library File Component. In the following working example, which I tested successfully, you can see that the link and description nodes may also be empty - though the nodes themselves must be present in the item.
Example Item Node for Deleting a Library File Component
Deleting a Library HTML Component is also similar. Notice that in the successfully tested example below, the link, description, and pubDate nodes must be present, but they can be empty. The ibmwcm:element node must be present with a child ibmwcm:value node. Again, the ibmwcm:value node can be empty.
| Traces, Logs, and Debugging To enable tracing for WCI, navigate to Portal admin console > Portal Analysis > Enable Tracing. Then append the following trace settings: com.ibm.workplace.feed.*=finest Also, note the feed service configuration file at: |