The WebSphere® Cooperative Portal architecture allows you to synchronize multiple portlet views in a single request-response cycle.
You can do this by using the Output
inputs. The technique involves sending data to one portlet and in turn causing that portlet to send data to another portlet which can, in turn send data to another portlet. Think of this concept as the chaining together of portlet events.
A typical example of the usefulness of this technique provided by IBM® is as follows: Transferring the order ID to an Order Details portlet also triggers the transfer of the tracking ID for the order to a tracking details portlet, which in turn triggers the transfer of the customer name associated with the order to a customer details portlet. Thus a single event in the Order Details portlet can cause all three portlets to display information pertaining to the same order.
If you have existing models that are using the C2A menu functionality, and you want to support wiring, you must open the Cooperative Portlet Source builder call in your model, and fill in the following new inputs: Output Name
, Output Type
, and Caption
Before creating a cross-page wire, the target page must have receiving actions defined as global on its portlets. This is located in the Portlet Wiring Tool when you click Manage Actions
If you have existing models that are using the C2A functionality, you must open the model in IBM WebSphere Portlet Factory Designer and perform a regeneration, then save the model. Therefore, the caption values are now stored as external model properties, which an Ant task saves when the WAR is rebuilt. Formerly, the caption property files were written by the builder.
Parent topic: Cooperative Portlet Target builder