Planning for WSRP

Before you work with WSRP, plan your configuration based on the following information.

WebSphere Portal v6.1.5 supports both WSRP Version 1.0 and 2.0.

How WSRP is implemented in the portal

The WSRP implementation in WebSphere Portal v6.1.5 enables you to do the following with the portal:

For Producer portals:

A WSRP Producer portal can provide portlets as WSRP services for remote invocation by Consumers. Depending on the API version of the provided portlet, the WSRP Producer provides the portlet in different WSRP protocol versions. JSR 168 portlets and IBM API portlets (also called IBM legacy portlets) are provided via both WSRP v1.0 and v2.0.    JSR 286 portlets can be provided via WSRP v2.0 only. The following table shows which provided portlets on a WSRP Producer are available in which WSRP version:

API to which the portlet complies	Provided by WSRP v1.0	Provided by WSRP v2.0
JSR 168 standard API	X	X
JSR 286 standard API	JSR 286 portlets cannot be provided by WSRP v1.0.	X
IBM portlet API (legacy portlets)	X	X

For Consumer portals:

A WSRP Consumer portal can integrate WSRP services that are provided by Producers as remote portlets. On the Consumer portal these portlets behave like local portlets that comply with the standard portlet API, independent of their implementation on the Producer side - by the standard portlet API, the IBM portlet API, .NET, or other implementations.

A WSRP Consumer portal v6.1 can integrate WSRP services that are provided by WSRP v1.0 or WSRP v2.0 Producer portals. Consumer portals v6.1 support WRSP v2.0 and can therefore consume all three types of portlets: JSR 168, JSR 286, and IBM portlet API.

At this time the WSRP Producer implementation in the portal does not support the Registration interface of the WSRP specification.

This interface is optional. However, the Consumer portal can handle Producers that support WSRP registration interfaces.

Prerequisites for WSRP in the portal

To use WSRP with the portal, have the appropriate level of IBM WAS installed. Refer to WebSphere Portal detailed system requirements to determine the WAS version that is required by your version of WebSphere Portal.

Exchanging the information required for WSRP

Before Producer and Consumer portals can communicate for using WSRP, the Producer needs to provide the information that the Consumer needs to consume the WSRP services from the Producer. This includes information about the following:

• The location where the Consumer can find the service description document of the Producer.

• The configuration of the Producer portal. This includes the security setup for WSRP on the Producer portal.

WSRP markup caching

The WSRP implementation in the portal uses expiry-based markup caching for remote portlets to improve performance. This reduces the number of interactions between the Consumer and the Producer and enables the use of remote caches for pages containing remote portlets.

For more information about markup caching refer to the topic about WSRP markup caching.

• Security considerations for WSRP services

  When you use WSRP with the portal, you can configure security and provide authentication by using different authentication mechanisms.

• How you work with WSRP in the portal

  To work with WSRP in the portal, you perform different administrative tasks. Some of these tasks depend on whether you use the portal as a Producer or Consumer portal.

• Communication between the Producer and Consumer portals

  The WSRP standard defines the communication interfaces between the Producer portal and the Consumer portal.

• Cookie support

  The WSRP Consumer stores cookies received from a Producer or from resources served by the WSRP Consumer as a proxy, and forwards the cookies appropriately in subsequent requests to a Producer or other resources.

Parent topic:

Use WSRP services

Related information

WebSphere Portal detailed system requirements

---