Plan for WSRP
For Producer portals
A Web Services for Remote Portlets (WSRP) Producer portal can provide portlets as WSRP services for remote invocation by Consumers.
API WSRP V1.0 WSRP V2.0 JSR 168 X X JSR 286
X IBM portlet API 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
- 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 your portal, have the appropriate level of IBM WAS installed.
Exchanging the information required for WSRP
Before Producer and Consumer portals can communicate for using WSRP, the Producer needs to provide...
- Location where the Consumer can find the service description document of the Producer.
- Configuration of the Producer portal, including security setup.
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.
See also
- Security considerations for WSRP services
- How you work with WSRP in the portal
- Communication between the Producer and Consumer portals
- Cookie support
- Use WSRP services
- WebSphere Portal detailed system requirements