This wiki does not contain official documentation and is currently deprecated and read only. Please try reading the documentation on the Liferay Developer Network, the new site dedicated to Liferay documentation. DISCOVER Build your web site, collaborate with your colleagues, manage your content, and more. DEVELOP Build applications that run inside Liferay, extend the features provided out of the box with Liferay's APIs. DISTRIBUTE Let the world know about your app by publishing it in Liferay's marketplace. PARTICIPATE Become a part of Liferay's community, meet other Liferay users, and get involved in the open source project. WSRP FAQ
Table of Contents [-]
- Introduction
- FAQ
- What versions of Liferay support WSRP?
- What is WSRP?
- How will embedded resources (like images, js, css) will be handled, can they be accessed still through a WSRP Consumer?
- How the user session is managed across portal servers
- How will I pass parameters (user info, parameter from browser, parameter from gtb portal) to and from between the two portal servers
- How will personalization be handled/stored/managed?
- Does Liferay support be producer and consumer at the same time?
- What versions of Liferay support WSRP?
Introduction #
This is a Frequently Asked Questions page for Liferay's WSRP feature.
FAQ #
What versions of Liferay support WSRP? #
All enterprise editions of Liferay will support WSRP 2.0. The community edition 6.0.x series supports WSRP as well.
What is WSRP? #
WSRP allows multiple portals to be setup as producers and consumers. If you have a Liferay instance with 200 portlets you will have extreme delays in updates and server reboots. WSRP will help mitigate this by giving each team their own portal from which they can serve their own portlets. This allows the main portal to consume all the portlets it needs without actually having to have them installed and deployed locally.
How will embedded resources (like images, js, css) will be handled, can they be accessed still through a WSRP Consumer? #
Resources, as long as they are using valid portlet URL's (resource URL's) will be properly proxied. If they are direct links they will remain that way.
How the user session is managed across portal servers #
One browser session equals one wsrp remote session. The sessions are synchronized between servers.
How will I pass parameters (user info, parameter from browser, parameter from gtb portal) to and from between the two portal servers #
As long as the portlet is Portlet 1.0 / 2.0 compliant all of this is handled transparently. Anything done outside of the portlet spec (ie accessing servlets directly) is not supported.
How will personalization be handled/stored/managed? #
This is handled by the remote server. If you have SSO properly set up then this should not be an issue. SSO between two portal servers needs to be customized for each portal server / SSO engine.
Does Liferay support be producer and consumer at the same time? #
Yes, it does. To accomplish that you should set the property auto.login.hooks=com.liferay.portal.security.auth.RequestHeaderAutoLogin in the portal-ext.properties.
