Consuming portlets in a Consumer portal
After creating a Producer definition, we can proceed to consume the portlets that are provided by that Producer. This way, you integrate them into the Consumer portal as remote portlets.
To consume a remote portlet in the Consumer portal, we can use either of the following tools:
On the Consumer side, all remote portlets behave like standard API-compliant portlets, independent of their implementation on the Producer side.
When a Producer provides a portlet, only settings made in the Configure mode of the portlet are available at the consumed remote portlet. Adding a remote portlet to a page on the Consumer side creates a new instance of the provided portlet on the Producer side. But this instance can be modified only on the Consumer and is not visible on the Producer portal.
Customization of the consumed portlets by Consumer portal users can be exported using xmlaccess.sh.
Parent topic: Use the portal as a consumerPrevious topic: Work with Producer definitions
Next topic: Customize the WSRP configuration of the Consumer portal
Related concepts:
xmlaccess.sh
Related information
Work with xmlaccess.sh