Portal Federation with WebLogic Portal WRSP: The Basics, Page 2
Although the most basic of WSRP producers require 60+ lines of XML to define the WSDL, even the most complicated WLP applications will generate a WSDL for you. The only hand editing you may need to do is with simpler files such as wsrp-producer-config.xml and wsrp-producer-registry.xml.
Remote portlets are consumed in the producer with a proxy portlet, and WLP provides two ways to create a proxy portlet. One method is through the WebLogic Workshop IDE at design time. Defining a proxy portlet at design time requires providing an address to the producer in a .portlet file; this cannot be changed at runtime. Due to this drawback, this approach is not recommended in this article. If you want to see how it works in detail, you can follow the tutorial included in the WLP documentation.
The other method to define a proxy portlet is through the WLP Portal Administration Tool (PAT). To define proxy portlets in the PAT, you first must create a streaming portal. Streaming portals are database-driven rather than file-based (where users access the portal through a .portal file defined in Workshop). There are many considerations outside of WSRP in choosing between a file-based versus a streaming portal and are beyond the scope of this article.
To quickly illustrate the steps of creating a streaming portal and consuming a WSRP portlet, you will use the naming conventions from your example applications as well as the existing assets in the example. For simplicity, you will have both portal applications deployed to the same domain. With this in mind, here is the process to create a streaming portal and consuming a simple remote portlet:
With the portal server running, navigate to http://localhost:7001/wsrpConsumerAdmin for your consumer portal's administration console (or, with the Portal perspective open in Workshop, select Run\Open Portal Administration Console) and log in with the admin credentials. From the Portal Management page, create a streaming portal and a desktop based on the .portal file you created in Workshop. In Figure 2, you've created a portal named "wsrp" with desktop named "default".
Figure 2: Streaming Portal Created in Portal Admin Tool
Next, add your producer portal to your library by expanding Library and Remote Producers, and then click the Add Producer button. In the wizard, enter
and click Search. Click the Remote Producer in the search results, and then follow the self-explanatory prompts to complete registration.
Figure 3: Remote Producer Configuration Wizard
With your remote producer registered, click the producer's name, and then Selected Portlets to access the Add Portlets button. The Add Portlets button will start a straightforward wizard to add your remote portlets.
Figure 4: Adding Remote Portlets to Consumer
Page 2 of 3