About the Original Author

Recent articles by this author

The Social Media Publisher for Web Content Manager is an extension to Web Content Manager that allows businesses to promote their web content on social networks, as well as provide some basic statistics about the promoted content.

The home page is an additional, simplified, UI for WCM. It is intended to be used by content authors who want to complete simple tasks through WCM, such as creating new content. For such users, the existing library explorer UI is unnecessarily complex and feature-rich.

Although all images and files can be created within Workplace Web Content Management, you might also want to consider using Document Manager in WebSphere Portal, depending on what you are trying to do.

The following table highlights feature differences between Workplace Web Content Management Resources and Document Manager to help you decide which approach you should take based on your specific requirements.

* The Document Manager API is provided under a Document of Understanding (DOU). Contact your IBM representative if this is required.

Handling syndication of Document Manager documents

Although syndication of content allows disparate server clusters to maintain the same level of content, it does not extend to documents that might be referenced with Document Manager components in Web Content Management. Ensure that these documents are transferred or published before syndicating the content.

Here is one way of ensuring that Document Manager documents are published first:

Create all Document Manager components in a separate library called an External Components library. Note: If you are already using All Live Items to syndicate the library that contains the rest of your components, then a separate library is not necessary.

Enable workflow on all components.

Use a Web Content Management workflow with a workflow stage that enables your components to be created in a Draft state initially.

If you need to change an existing Document Manager document and have it staged with other Web Content Management-related changes, create a new Document Manager document and update the Document Manager component in Web Content Management to use the new Document Manager document. Then use the process above to deploy the changes and finally remove the old Document Manager document after the changes are published.