In composite applications, Web Services Description Language (WSDL) files (XML files) containing name spaces, properties, actions, and types are used by components for component interaction in a composite application.
Components within a composite application can be wired together so a user-initiated action in one component can trigger a programmed action in another component. This functionality is supported by the use of properties, actions, types, and the property broker. The composite application components use a model for declaring, publishing, and sharing this information with each other via the WebSphere® Portal property broker.
Components subscribe to the broker by publishing typed data items - properties and actions - that they can share. Components can act either as a provider or as a recipient of these properties and actions.
These components may be developed and deployed separately or together and can exchange information and react in a coordinated manner, thus improving the end-user experience. Conversely, as components are removed, the remaining components will still be able to function correctly and in a coordinated manner. The property broker is used to facilitate development of components that may be dynamically integrated, without requiring previous coordination at development time. Composite applications can simply be an assembly of multiple components with on-the-glass aggregation that keep the application user focused on the business process, eliminating the need for the application user to switch between applications or switch between open windows.
To derive additional value and further increase organizational productivity, you can have components form causal relationships with other components through properties and actions. A property broadcasts a value and an action consumes a value. In order to make sure that both sides are communicating consistently, both properties and actions need to describe the type of value they broadcast or consume. This ensures that sensible connections are made when the components are wired together.
WSDL files that are used in composite applications are created and edited using the Property Broker Editor. This feature provides an easy way for you to describe property broker properties, actions, and types without having to understand the WSDL format. You define the properties, actions, and types through a simple interface which then generates the WSDL file required by property broker implementations when you save the editor settings. The editor can be launched using either of the following methods:
- To create a new Property Broker WSDL file using the New File wizard, selecting File > New > Client Services > Wiring Properties.
- To edit an existing file, select it in the Navigator and then launch the editor using Open With > Wiring Properties.
Refer to the Property Broker Editor help menu for instructions on how to:
- Define wiring properties
- Define property data types
- Define wiring actions and action parameters
Parent topic: Portlet intercommunication: XPD621