Webcenter Portlet Configuration

There are 3 types of Producers we can configure into Webcenter.

1. WSRP Producer

2. Oracle PDK-Java Producer
3. Pagelet Producer

In order to register the above mentioned producers with webcenter following are configuration information needed

Following Table gives the configuration parameters in brief.

Configuration parameters marked in red are mandatory parameters. Other parameters depend on the parent parameter configuration detailed configuration in mentioned below.

WSRP Producer	Oracle PDK-Java Producer	Pagelet Producer
WSDL URL	End Point Url	Server Url
Proxy Host:port	Service Id
Token Profile	Proxy Host:port
Issuer Name	User Session
Default user	Subscriber Id
	Shared Key

Detailed information of the parameters mentioned above.

WSRP Producer :

           

WSDL URL:

WSDL URL for the WSRP Producer

Proxy Host :

Proxy Port :

                        host name ,Port for the proxy server

           

Note: Proxy Host and port are required if any proxy is configured

Token Profile :

                        Supported Profiles :

WSS 1.0 SAML Token

WSS 1.0 SAML Token with Message Integrity

WSS 1.0 SAML Token with Message Protection

WSS 1.0 Username Token with Password

WSS 1.0 Username Token without Password

WSS 1.0 Username Token without Password

WSS 1.1 SAML Token with Message Protection

 Issuer Name :

            name of the issuer of the SAML token

Default User :

user name to assert to the remote producer when the user is not authenticated with the WebCenter Portal application.

            Note: Token Profile can be selected as none. If any token profile is configured the above mentioned Issuer name and default user in needed.

Oracle PDK-Java Producer:

End Point Url:

 URL endpoint for the Oracle PDK-Java Producer

Service Id :g

            unique service ID for this producer

 Note: Provide if configured

Proxy Host :

Proxy Port :

host name ,Port for the proxy server

 Note: Proxy Host and port are required if any proxy is configured

User Session:

            enable a user session when executing portlets from this producer.

 Note: Provide if configured

Subscriber Id :

string to identify the consumer of the producer being registered. In this instance, the WebCenter Portal application is the consumer

Note: Provide if configured

Shared Key :

 The key is used for encrypting calls to the portlet producer.

Note: Provide if configured

Pagelet Producer:

Server Url :

URL of the server providing Pagelet Producer services. The URL should include fully qualified domain name.

Additional information which would help in optimizing the portet producer application.

External applications should published as portlet producers for webcenter portal application.

Portlets should support WSRP 2.0 Specs:

Portlets :

Portlet is a user-facing, interactive application component that renders markup fragments that can be aggregated and displayed by a portal.

WSRP :

Web Services for Remote Portlets (WSRP) are presentation-oriented, interactive web services. WSRP provides a standard that enables all content and application providers to provide their services in a manner where they can easily be discovered and plugged into all compliant portals without programming effort on the portal's side

Supported locale:

Portlet should support multiple locale as per the requirements.

Enable persistant store for application:

portlets store their state in file at OS level it is recommended for high availability and specially in a cluster environment to use database as a persistence store.

Contextual events propagation as portlet events:

Contextual events can be used for communication between the Portlet and the Portal

Portlets should support Edit Mode/Edit Defaults Mode:

A portlet uses Edit Defaults mode to enable administrators to customize the default behavior of a particular portlet instance. Edit Defaults mode provides a list of settings that the application developer can change. These settings may include the title, type of content, formatting, amount of information, defaults for form elements, and anything that affects the appearance or content of the portlet.

Validation-Based Caching support:

The portlet associates its content with a caching key and returns the key value along with the content. When the portlet content is requested, the portlet decides, based on the caching key, if the current content is valid. If the portlet content is valid, then it returns a response indicating that the cached content can be used (that is, the content is valid) or generates the new portlet content and returns it along with a new caching key for that content.