Skip Headers
Oracle® WebCenter Content Deployment Guide for Content Portlet Suite
11g Release 1 (11.1.1)

Part Number E10637-02
Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Go to current chapter
Go to next page
PDF · Mobi · ePub

1 General Information

This chapter provides general information on Content Portlet Suite (CPS) including a list of supported servers, descriptions of the portlets, recommended access settings, and information on the portlet interface language. It covers the following topics:

1.1 What's New

CPS 11g Release 1 (11.1.1) includes the following new features and enhancements:

Additional WSRP Support

IBM Websphere Portal 6.1 is now supported as both a WSRP Producer and WSRP Consumer. See Section 3.3, "IBM WebSphere Portal as Producer" for more information.

CPS Architecture

CPS now uses the Remote Intradoc Client (RIDC) API to communicate with Oracle WebCenter Content Server. CPS portlet actions are mapped to a custom MVC framework that uses the RIDC API to perform tasks. This architecture enables CPS portlets to call RIDC methods and execute the requested content server service. See Appendix A, "CPS Software Development Kit" for more information.

1.2 Servers Supported in this Release

This version of CPS provides Web Services for Remote Portlets (WSRP) support. CPS is deployed as a WSRP producer and can be consumed from other WSRP-enabled consumers.

Supported WSRP Producers and Consumers

Oracle WebCenter Portal 11g Release 1 ( or higher) (as producer)

Oracle WebLogic Portal 10g Release 3 (as producer)

IBM WebSphere Portal Version 6.1 (as producer)

1.3 Portlets Provided with this Release

CPS enables you to manage content creation and the distribution process through a set of easy-to-use portlets. By providing access to Oracle WebCenter Content Server, CPS enables users to update, search, and view content in an easy, efficient way.

These are the available portlets for this release:

1.4 Recommended Access Settings

This section provides the recommended access settings for the portlets. By default, portlet security is set to allow access by only the system administrator. You must also configure security to allow other users to access the portlets and assign permissions based on the access requirements you establish for users. However, some security settings are recommended for authenticated users and for anonymous users.

Authenticated Users

These security settings are recommended for authenticated users:

Anonymous Users

These security settings are recommended for anonymous users:

1.5 Portlet Interface Language

The portlet interface language is set to the client's locale. That is, if the client is using, say, a German language version of an operating system (assuming support by the JVM running the portal server), the CPS portlets will display a German interface.