Consuming WSRP services in a Consumer portal
After you have created a Producer definition, you can proceed to consuming the WSRP services that are provided by that Producer, that is, integrating them into Consumer portal as remote portlets.
To consume a WSRP service as a remote portlet in Consumer portal, you can use either of the following tools:
- The Manage Web Modules portlet.
- The portal XML configuration interface. For more information about xmlaccess.sh refer to the appropriate topics.
Notes:Proceed by selecting the appropriate topic from the links below.
- 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.
- 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.
- Customization of the consumed portlets by Consumer portal users can be exported by using xmlaccess.sh.
- Use the Manage Web Modules portlet to consume WSRP services from a Producer portal
- 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 topic
Customize the WSRP configuration of Consumer portal
xmlaccess.sh