Wikis use the template libraries provided by IBM® Web Content Manager. Wikis use the Web Resources v70 library and the Wiki v70 library. The page hierarchy that is provided for wikis is the common one defined by the Web Content Manager template libraries.

Blogs and blog libraries use the template libraries provided by IBM® Web Content Manager. Blog libraries use Web Resources v70 library and Blog v70 library. Blogs use the Web Resources v70 and Blog Solo v70 library. The page hierarchy that is provided for these components is the common one defined ...

Use blogs and blog libraries to provide news and commentary on a variety of subjects pertinent to your intranet and extranet sites. Blogs and blog libraries typically combine text with graphics and links to other blogs and web sites. Entries that you create and post are arranged in ...

Your web content system can contain multiple libraries. The number of libraries required is determined by the type of website you are creating, and the types of users who require access to each library.

The roles you assign each library on your authoring system will determine what views and features in an authoring portlet are accessible to your users.

You define the access of a user or group for a library to determine who has access to a library, and to define access to the different views within the authoring portlet.

You can export the contents of a web content library to disk and import this data into another web content server. This feature enables you to make a backup copy of a web content library, and can also be used to move data between servers. This function cannot be used to send updates, deletes, and ...

You can export the contents of a web content library to disk by creating a copy of the web content library. By working with an exported copy, you can import the copied library into the same web content server multiple times, resulting in a new library after each import without affecting previous ...

IBM® Web Content Manager provides two methods for exporting and importing web content libraries: an export or import that operates on one library, and an export or import that enables you to work with a separate copy of a library. With either method, you can export the contents of a web content ...

You can export the contents of a web content library to disk and import this data into another web content server. This feature enables you to make a backup copy of a web content library, and can also be used to move data between servers. This function cannot be used to send updates, deletes and ...

To set up syndication between libraries on two IBM® Web Content Manager applications, establish a relationship between a syndicator and a subscriber. The syndicating server contains the data to be replicated, and the subscribing server receives the replicated data.

You can restrict access to selected users and groups to the views within an authoring portlet, the items managed by the authoring portlet, and to elements and pages displayed within a website.

Blogs and blog libraries use the template libraries provided by IBM® Web Content Manager. Blog libraries use Web Resources v70 library and Blog v70 library. Blogs use the Web Resources v70 and Blog Solo v70 library. The page hierarchy that is provided for these components is the common one defined ...

Use blogs and blog libraries to provide news and commentary on a variety of subjects pertinent to your intranet and extranet sites. Blogs and blog libraries typically combine text with graphics and links to other blogs and web sites. Entries that you create and post are arranged in ...

Wikis use the template libraries provided by IBM® Web Content Manager. Wikis use the Web Resources v70 library and the Wiki v70 library. The page hierarchy that is provided for wikis is the common one defined by the Web Content Manager template libraries.

To set up syndication between libraries on two IBM® Web Content Manager applications, establish a relationship between a syndicator and a subscriber. The syndicating server contains the data to be replicated, and the subscribing server receives the replicated data.

Use blogs and blog libraries to provide news and commentary on a variety of subjects pertinent to your intranet and extranet sites. Blogs and blog libraries typically combine text with graphics and links to other blogs and web sites. Entries that you create and post are arranged in ...

Blogs and blog libraries use the template libraries provided by IBM® Web Content Manager. Blog libraries use Web Resources v70 library and Blog v70 library. Blogs use the Web Resources v70 and Blog Solo v70 library. The page hierarchy that is provided for these components is the common one defined ...

Wikis use the template libraries provided by IBM® Web Content Manager. Wikis use the Web Resources v70 library and the Wiki v70 library. The page hierarchy that is provided for wikis is the common one defined by the Web Content Manager template libraries.

To set up syndication between libraries on two IBM® Web Content Manager applications, establish a relationship between a syndicator and a subscriber. The syndicating server contains the data to be replicated, and the subscribing server receives the replicated data.

This article details about how to configure Lotus Quickr server to delete the libraries permanently from Lotus Quickr. This can be done by setting the CAI scheduler to run by cron. When quickr places are deleted in the Lotus Quickr via the 'Manage Places' place, they are not deleted ...

Test Infrastructure: Web Content Management z/OS End to End: Authoring, Rendering, API and Syndication Abstract The purpose of this document is to outline the steps by which the Web Content Managem

Working with libraries Libraries are used in order to separate items, whether to separate between the contents and components, or separate based on projects or for any other design purposes. A library and its security settings are to be created before starting the work on the site. This section ...

Introduction In version 6.1 a new method was introduced to the Web Content Management API that allows customers to export a list with information about all documents and web content artefacts in a we