Plan for WSRP
IBM WebSphere Portal v8.0 supports both WSRP Version 1.0 and 2.0.
How WSRP is implemented in the portal
The WSRP implementation in WebSphere Portal v8.0 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 (IBM legacy portlets) are provided via both WSRP V 1.0 and V 2.0. JSR 286 portlets can be provided via WSRP V 2.0 only.
API to which the portlet complies Provided by WSRP V 1.0 Provided by WSRP V 2.0 JSR 168 standard API X X JSR 286 standard API JSR 286 portlets cannot be provided by WSRP V 1.0. X IBM portlet API (legacy portlets) X X
- For Consumer portals:
- A WSRP Consumer portal can integrate WSRP services 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 V 6.1 can integrate WSRP services provided by WSRP V 1.0 or WSRP V 2.0 Producer portals. Consumer portals V 6.1 support WRSP V 2.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, you must have the appropriate level of IBM WAS installed. Refer to System requirements to determine the WAS version required by the 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, including 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 we use WSRP with the portal, we can configure security and provide authentication using different authentication mechanisms.- 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 we use the portal as a Producer or Consumer portal.- Communication between 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: Use WSRP services
Related: