Here are few basic points which you should know while dealing with IBM Workplace Webcontent Management(IWWCM) Library or wcm library.
Webcontent Library or wcm library:
Libraries are (new) data-partitioning feature in wcm (6.0). The web content management library contains your website structure. This repository includes all of the components that make up the website, such as: authoring and presentation templates, and menu and link components that take the advantage of the dynamic structure web content management offers. These components help you easily manage the content and avoid broken links on the website.
There are 2 methods to assign roles to whole library and the item types within it:
- Additive: You apply the User or Privileged User role to the entire library and deselect the propagation check box. It will give it access to the library and any authoring portlets configured to use the library. The Administrator then applies Contributor, Editor, Manager, or Administrator roles to specific item types to grant additional access to specified users or groups.
- Subtractive: The administrator applies the Manager or Administrator role to the entire library, then applies Contributor, Editor, Privileged User, or User roles to specific item types, and deselects the inheritance check box. This reduces the access to different item types for specified users or groups.
The difference between Manager and Administrator roles within Web Content Management: if you assign an Administrator role to an entire library, you cannot then remove this role from any item type views. This is not true for a Manager role.
Advantages of library:
- By using libraries, you can split up large sites and manage them separately.
- Separate presentation storage from content storage. It means one library would only contain Sites and Content and another library would contain Presentation Templates and Components.
N.B:If a library is no longer required, it can be deleted or disabled. Deleting a library means also deleting all objects within that library. Disabling a library prevents a user from accessing it from an authoring portlet or updating any items stored in the library. Any items referenced from this library will still be rendered by the rendering portlet.
The following conditions may prevent a library from being deleted:
- A library cannot be deleted if it contains any draft or locked items.
- A library containing items with complex relationships may not be able to be deleted due to referential integrity issues. You will need to delete these items before deleting the library.
- Libraries containing a large number of items may not be able to be deleted. You will need to reduce the number of items in the library.
If a library cannot be deleted after addressing the previous issues, you may need to delete all items from the library before it can be deleted.
