Reference for using WSRP with the portal

Reference information about using WSRP with the portal includes WSRP markup caching and Known limitations.

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. You can disable this feature if required.
WSRP two-phase rendering
The WSRP Consumer and the WSRP Producer in the portal support two-phase rendering for JSR 286 portlets. This allows a remote portlet to set headers and cookies and to modify the HTML head section. The WSRP Producer determines whether a JSR 286 portlet requires two-phase rendering and, if it does, the Producer invokes the render method in two phases.
Hints and tips for using WSRP with the portal
These are some hints and tips for using WSRP with the portal.
Troubleshooting WSRP
You can troubleshoot WSRP using different methods such as logging and tracing, debugging, and monitoring.

Parent topic: Using WSRP services