Portal Server content management system (CMS) provides a hierarchical content store that supports structured and unstructured content, images, content templates, and versions. The content management system uses the JSR 170: Content Repository for Java Technology API specification, which provides a standard way for server-based applications to interact with content repositories.
How Portal Server users can use the content management system is based on their roles.
Portal Server administrators can use content management to create, edit, delete, and lock the following:
Content categories
Content versions
Organize content into different categories for ease of management
Portal Server developers can use content management to do the following:
Use CMS tag libraries and API to interactive with the content management system
Use Portal Pack for NetBeansTM IDE
Portal Server end users can use content management to perform the following tasks:
Create and edit content
Lock content versions
Create, based on their roles, and assign templates to content
Publish content by completing user tasks that are predefined in workflow definitions (Simple API for Workflow and Sun Java Composite Application Platform Suite must be available)
Search for content
The content management systems provides portlets that do the following:
Manage categories and content types with templates
Manage contents for a content type
Portal Server provides sample CMS portlets that illustrate the use of OCM (object content mapping) functions for managing unstructured content, for managing structured content with predefined metadata, and for creating custom content types and contents. The samples available include the following portlets:
Document Management Portlet that showcases how unstructured content is managed
Article Management Portlet that showcases how structured content is managed
The sample CMS portlets use the Apache JackRabbit implementation of the JSR 170 specification.