Consuming WSRP services in a Consumer portal

After creating a Producer definition, we can proceed to consuming the WSRP services that are provided bthat Producers that is, integrating them into the Consumer portal as remote portlets.

To consume a WSRP service as a remote portlet in your Consumer portal, we can use either of the following tools:

• The Manage Web Modules portlet.

• The portal xmlaccess.sh. For more information about xmlaccess.sh refer to the appropriate topics.

1. On the Consumer side, all WSRP services that you consume as remote portlets behave like standard API compliant portlets, independent of their implementation on the Producer side.

2. When a Producer provides a portlet, the portlet itself is provided, not an instance of it. Therefore 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 only be modified on the Consumer and is not visible on the Producer portal.

3. Customization of the consumed portlets by Consumer portal users can be exported using xmlaccess.sh.

Proceed by selecting the appropriate topic from the following links:

• Use the Manage Web Modules portlet to consume WSRP services from a Producer portal
  To consume WSRP services from a Producer portal, we use the Manage Web Modules portlet and consume a Web module.
• Use xmlaccess.sh to consume WSRP services from a Producer portal
  We can use xmlaccess.sh to consume WSRP services from a Producer portal.

Parent: Use the portal as a WSRP Consumer
Previous: Work with Producer definitions
Next: Customize the WSRP configuration of the Consumer portal
Related:
xmlaccess.sh