Skip to content

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
    To improve performance, the WSRP implementation in the portal can use expiry-based markup caching for remote portlets. This caching reduces the number of interactions between the Consumer and the Producer. The Consumer caches remote portlet content, based on the cache-control data structure that the Producer provides as part of its response. You can enable markup caching on the Consumer for all remote portlets or specifically for selected remote portlets.
  • Cookie support
    The WSRP Consumer stores cookies that it receives from a WSRP Producer or from resources that the Consumer serves as a proxy. It forwards the cookies appropriately in subsequent requests to a Producer or other resources.
  • WSRP two-phase rendering
    The WSRP Consumer and the WSRP Producer in the portal support two-phase rendering for JSR 286 portlets. Two-phase rendering allows a remote portlet to set headers and cookies and to modify the HTML head section.
  • Handling HTTP headers
    You can configure both the WSRP Producer and the Consumer to ignore headers.
  • Hints and tips for using WSRP with the portal
    Here are some hints and tips for using WSRP with HCL Digital Experience.
  • Troubleshooting WSRP
    You can troubleshoot WSRP by using different methods such as logging and tracing, debugging, and monitoring.