Home > Articles > Web Services > WebSphere

  • Print
  • + Share This
This chapter is from the book

Important Points

  • WPF portlets can communicate with each other using the WebSphere Property Broker, shared variables, or the WPF event model. Each approach has its own strengths and weaknesses.
  • Communication via the WebSphere Property Broker is facilitated by publishing properties to a WebSphere Portal Server mechanism known as the Property Broker, which then routes these properties off to other portlets. Implementing communication using the Property Broker offers considerable flexibility, because it means that your portlets can communicate with portlets in other WARs, or even portlets built using environments other than WPF. Also, because WPF provides builders to automate the communication configuration, you don't need to write any code to implement the communication. However, configuration in the portal is required before this mode of communication will work.
  • Shared variables can be configured to use a number of different stores and are perhaps the quickest and easiest way to implement inter-portlet communication in WPF. However, unless your portlets are all in the same WAR file, you need to write code to retrieve the variable values. This approach is best suited to storing one or two small pieces of information used across an entire WPF application.
  • The WPF event model also offers a quick and easy approach to inter-portlet communication, and gives you the added benefit of a prepackaged WPF builder to handle communication events without regenerating the entire portal page. This approach has limited extensibility because all communicating portlets need to be contained in the same WAR file to be used effectively, and they need to be developed in WPF; however, it is well suited to WPF applications where events in one portlet trigger events in another.
  • + Share This
  • 🔖 Save To Your Account