| By Matt Silver | Article Rating: |
|
| July 17, 2008 06:00 PM EDT | Reads: |
10,636 |
A standard from OASIS called Web Services for Remote Portlets (WSRP) is used so portlets can be decoupled from a portal. In part one (JDJ, Volume. 13, issue 3) of this article, we introduced the relevant standards and specifications and then demonstrated WSRP’s capabilities by consuming a WebSphere Portal portlet in WebLogic Portal.
In this second article, we’ll explore the reverse scenario by illustrating WebSphere Portal acting as the portlet consumer and WebLogic operating as the portlet producer.
For WebSphere Portal to consume a WebLogic Portal portlet, several things have to happen:
WebLogic Portal
- Functions as a producer
- Offers (shares) the portlet
WebSphere Portal
- Functions as a consumer
- Adds a remote producer
- Creates a remote portlet
- Adds the remote portlet to a page
Once again, WebSphere Portal and WebLogic Portal both function as consumers and producers without requiring any special setup. However, the other steps still need to be taken.
WebLogic Portal – Offer a Portlet
WebLogic Portal automatically lets portlets created using WebLogic for Workshop be shared. There’s a property called Offer as Remote that’s set to true by default. Unfortunately, this property isn’t visible in the WebLogic Portal Administration Console. It’s only visible in WebLogic for Workshop.
Consequently, there’s nothing you have to do to share the portlet. This is different from the way WebSphere Portal behaves, since WebSphere Portal requires that you explicitly share the portlet using the administration console. Now it’s on to configuring the consumer.
WebSphere Portal - Add a Producer
Log onto WebSphere Portal (http://portalpc:10038/wps/portal). Click the Launch button and select Administration to navigate to the WebSphere Portal Administration Console.
Click the Web Services node underneath Portlet Management in the navigation bar.
Click the New Producer button in the Web Service Configuration administration portlet.
Unlike in WebLogic Portal, there’s only one step involved in adding a producer. Enter a Title for the producer, which serves as a label. In this case, input BEA WebLogic Portal Server v9.2. Next, input the URL to WSDL service definitions. This URL points to the WSDL document that contains information about the producer and how to connect to its services. Specifically, it contains the URLs of the WSRP interfaces supported by the provider. In the case of WebLogic Portal, the standard format for this URL is http://host:port/WebAppName/producer?wsdl
In our case, this URL translates to http://portalpc:7001/BEAPortalWeb/producer?wsdl. Enter this URL.
Published July 17, 2008 Reads 10,636
Copyright © 2008 SYS-CON Media, Inc. — All Rights Reserved.
Syndicated stories and blog feeds, all rights reserved by the author.
More Stories By Matt Silver
Matt Silver is a courseware developer and trainer, currently serving as a senior consultant for Web Age Solutions.
![]() |
agnelom 07/26/09 01:24:00 PM EDT | |||
Hi Matt This is a good starter example. But did you try access resources on the WebLogic producer using the Consumer resourceproxy Servlet on the WebSphere consumer. I am currently facing an issue with access a PDF file that is generated on the Producer which is access via the the ResourceProxy. In homogeneous environments both webSphere-to-WebSphere and WebLogic-to_WebLogic seems to be working fine but not in a heterogeneous environment I have tried with WebSphere-To-WebLogic (C-To-P) and the PDF file comes up blank. |
||||
- It's the Java vs. C++ Shootout Revisited!
- Patterns for Building High Performance Applications
- Asynchronous Logging Using Spring
- Java for Programmers (2nd Edition)
- Cross-Platform Mobile Website Development – a Tool Comparison
- Three Buzzwords That Every CIO Hears but One They Should Listen To
- Write Once Run Anywhere or Cross Platform Mobile Development Tools
- Immersing into JavaScript Frameworks
- Workday Reportedly Prepping to Go Public
- Cloud Expo New York: The Java EE 7 Platform - Developing for the Cloud
- Book Review: Sams Teach Yourself Java in 24 Hours
- OpenOffice.com Lives
- Book Excerpt: Introducing HTML5
- Adobe Sends Flex to the Apache Foundation
- Five Years Waiting for JRE 7: Is It Justified? (Part 1)
- Book Excerpt: Java Application Profiling Tips and Tricks
- i-Technology in 2012: Five Industry Predictions
- It's the Java vs. C++ Shootout Revisited!
- Patterns for Building High Performance Applications
- OpenXava 4.3: Rapid Java Web Development
- The Next Web Architecture
- Asynchronous Logging Using Spring
- Java for Programmers (2nd Edition)
- Is Write Once Run Anywhere Ever Going to Be a Reality?
- A Cup of AJAX? Nay, Just Regular Java Please
- Java Developer's Journal Exclusive: 2006 "JDJ Editors' Choice" Awards
- JavaServer Faces (JSF) vs Struts
- The i-Technology Right Stuff
- Rich Internet Applications with Adobe Flex 2 and Java
- Java vs C++ "Shootout" Revisited
- Bean-Managed Persistence Using a Proxy List
- Reporting Made Easy with JasperReports and Hibernate
- Creating a Pet Store Application with JavaServer Faces, Spring, and Hibernate
- Why Do 'Cool Kids' Choose Ruby or PHP to Build Websites Instead of Java?
- What's New in Eclipse?
- i-Technology Predictions for 2007: Where's It All Headed?





















