This article shows how content architects can coordinate the publishing or transfer of all portal content artifacts from a staging or development environment to a production server. Portal content artifacts include those stored in IBM® Workplace® Web Content Management, Portal Document Manager and WebSphere Portal Personalization.

The scenario assumes you are publishing content that references personalization rules which, when executed, return documents from a known folder in a document library. You see how to publish all content stored in the portal content repository.

Filed in:
0 Comments To ' Implementing a content publishing pattern '

Post a Comment