Components within a composite application can be wired to 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.

Using the Property Broker Editor

WSDL files that are used in composite applications are created and edited in IBMR LotusR Domino(TM) Designer 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.

This feature lets you do the following:

• Define wiring properties for composite applications
• Set data types for values that are being shared by applications
• Create actions for composite applications

Defining wiring properties for composite applications

With composite applications, you need to define the properties that portlets will use to exchange information using the IBMR WebSphereR Portal property broker. The property broker transfers instances of these properties and their values to and from portlets to initiate actions.

The property broker is a WebSphere Portal interface that negotiates the relationship between cooperative source and target portlets and delivers data to the target in the form of the corresponding portlet action. To define properties and their corresponding property details with the Domino Designer Property Broker Editor, do the following:

1. Start Domino Designer

2. Open the composite application that contains the WSDL file that you wish to open.

3. Click Composite Applications-Wiring Properties. The WSDL files for the composite application are displayed in the Composite Applications-Wiring Properties view. You can also click the New Wiring Property button to create a new file to start with and automatically launch the Editor.

4. If the file already exists, select and double click the file that you wish to open for editing. The Property Broker Editor is launched so that you can edit your WSDL file.

5. Click the Properties tab in the canvas. A form titled Wiring Properties is displayed.

6. In the Wiring Properties form, do the following:

• Click Add to add a new property to the Properties box. A default property named Property is created with a default data type of String.
• In the Name field of the Property Details box, type the name you wish to give the property. You reference the names of properties in scripts that you write for the composite application, for example, action scripts.
• In the Type field of the Property Details box, select the data type of the property you are defining. Options include String, Integer, Double, Boolean, Date, and Date/Time as well as any types that you have created earlier for the component.
• In the Title field of the Property Details box, type the title of the property. Titles do not replace names. Titles are exposed on WebSphere Portal but do not appear in script code.

  Note Optional: In the Description field of the Property Details box, type a description of the property. Your administrator uses this description when wiring the portlets after deployment.

• Enable or disable the Allow publishing option. Since a property is a typed exchangeable data item which components can produce, enabling this option means that you wish to publish this property to the property broker. NSF components can publish and consume properties. Publishing involves sending a value to the property broker, for it to pass on to other components.
• Add the desired namespace to the Namespace field of the Target Namespace section. As part of creating a new types, default namespaces for the property type are needed in this Namespace field. The namespace provides a unique identifier in the file that contains the property definitions. This value is automatically set to a value based on the name of your component, and you do not need to modify it unless you have custom requirements.
• To remove a property, select the property you wish to remove from the property list. Click Remove to remove the property.

Note In most cases, the property type is string. Normally, you only set new property types for properties that contain multiple types, for example, string, integer, and date/time.

As a result, Domino Designer creates a Web Services Description Language (WSDL) file so that your component can reference the properties. This file will be deployed to WebSphere Portal along with the rest of the component files.

If you are editing an existing WSDL file, you need to refresh the existing Wiring Properties design element to update it with your changes. Refer to the topic "Updating or refreshing an edited WSDL file in Domino Designer" for more information on refreshing and updating your Wiring Properties design element.

Defining property data types for composite applications

With composite applications, properties are used to exchange information between application components using the IBMR WebSphereR Portal property broker. The property broker transfers instances of these properties and their values to and from portlets to initiate actions.

The property broker is a WebSphereR Portal interface that negotiates the relationship between cooperative source and target portlets and delivers data to the target in the form of the corresponding portlet action. For more information about the WebSphere Portal property broker, go to http://www.ibm.com/websphere/portal/library.

Use the following steps to set data types for these properties:

1. Start Domino Designer

2. Open the composite application that contains the WSDL file that you wish to open.

3. Click Composite Applications-Wiring Properties. The WSDL files for the composite application are displayed in the Composite Applications-Wiring Properties view. You can also click the New Wiring Property button to create a new file to start with and automatically launch the Editor.

4. If the file already exists, select and double click the file that you wish to open for editing. The Property Broker Editor is launched so that you can edit your WSDL file.

5. Click the Types tab in the editor. Any new types that you create on the Types page appear in the Type list on the Properties page.

Note In most cases, the property type is string. Normally, you only set new property types for properties that contain multiple types, for example, string, integer, and date/time.

6. To create a new property type, do either of the following steps:

• To create a single new property type, click New Type. Type a name for the property type in the Name field, and select a type from the list in the Type field.
• To create a complex new type, click New Complex Type and type a name for the property type in the Name field. For each child type in a complex property type, provide a name in the Name field and select a type from the list in the Type field.
• As part of still creating a new type, type the default namespace for the property type in the Namespace field. The namespace provides a unique identifier in the file that contains the property definitions. This value is automatically set to a value based on the name of your component, and you do not need to modify it unless you have custom requirements.

• Click Import Types. The Import Types dialog box appears.
• Browse to and select the WSDL file that contains the type you wish to import. The available types from that WSDL file are displayed.
• Select the checkbox for the type(s) you wish to import. Click OK to import the type(s) into your current WSDL file.

9. Click File > Save to save your all your new types and changes.

Below the Types section of the form, there is the Type Namespaces section. By default, this section is collapsed. It can be opened by clicking on the Type Namespaces text. This section is provided to help eliminate namespace typing errors when adding namespaces and it also lets you assign a prefix to that type since the Namespace field in the Type Details section is non-editable and only lets you choose from valid namespaces understood by the component.

Within the Type Namespaces section, you can add a namespace with a prefix to refer to types, perhaps from another component, or another external standard. Click Add to add a new namespace. Enter the new prefix in the Prefix field and the desired namespace in the Namespace field. To remove a type namespace, select the one you wish to remove from the list on the left and click Remove.

If you are editing an existing WSDL file, you need to refresh the existing Wiring Properties design element to update it with your changes. Refer to the topic "Updating or refreshing an edited WSDL file in Domino Designer" for more information on refreshing and updating your Wiring Properties design element.

Creating actions and action parameters for composite applications

With composite applications, you need to define the actions that are triggered when portlets publish properties that get received by another portlet. Examples of actions include changing or refreshing component pages and redirecting the current page to a Web site.

In composite applications, the following steps must take place before an action can occur.

• The user interacts with a portlet in some way, for example, inputting a value and then clicking a submit button.
• A script runs and publishes the property value to the IBMR WebSphereR Portal property broker.
• The property broker finds the portlets that are listening for the property value and tells them to perform the requested action.

1. Start Domino Designer

2. Open the composite application that contains the WSDL file that you wish to open.

3. Click Composite Applications-Wiring Properties. The WSDL files for the composite application are displayed in the Composite Applications-Wiring Properties view. You can also click the New Wiring Property button to create a new file to start with and automatically launch the Editor.

4. If the file already exists, select and double click the file that you wish to open for editing. The Property Broker Editor is launched so that you can edit your WSDL file.

5. Click the Actions tab in the canvas. A form titled Wiring Actions is displayed.

6. In the Wiring Actions form, do the following:

• Click Add to add a new action to the Actions box. A default action named Action is created. The default settings for this action have the following option(s):
  • Default action if multiple actions match the property - If multiple actions match the incoming property, make this action the default action if you have defined other actions that are configured to receive the same property.
  Note If you have more than one action that is using the same Action Input Parameter property, then you need to determine which Action is the default action. To specify the action that is the default for that property, you put a checkmark in the box next to Default action if multiple actions match the property. Be sure that you only have one action checked for with the same property as other actions. Again, if you have more than one action selected as the default for that input property, it will cause errors when you are running the composite application.

  If you wish to change these options, de-select the option to disable it.

• In the Name field of the Action details box, type the name you wish to give the property. You reference the names of properties in scripts that you write for the composite application, for example, action scripts.
• In the Title field of the Action details box, type the title of the action. Titles do not replace names. Titles are exposed on WebSphere Portal but do not appear in script code.

  Note Optional: In the Description field of the Action details box, type a description of the action. Your administrator uses this description when wiring the portlets after deployment.

• To remove an action, select the action you wish to remove from the action list. Click Remove to remove the action.

You must now define the following for your action(s):

• Action input parameter
• Action output parameter

Action Input Parameter

An Action Input Parameter is used to identify that an action is associated with an input property. This action is triggered when the input property is published - provided it is active. You would then use the value in a script to update whatever information on the page is dependent on the value.

You set the Action input Parameter by specifying the associated input property in the Property field of the Action Input Parameter section of the Wiring Actions form. Your action is then triggered in response to this property being published, and when this action is invoked, the value of this property can be requested by script.

Action Output Parameter

If an action publishes a property, you need to define an action output parameter. You can do this by using the Available Properties and Selected Properties boxes in the Action Output Parameter section of the Wiring Actions form .

The Available Properties box lists all the properties in the current WSDL file - that have not already been chosen as output properties. You can select one or more properties and click Add to set them as output parameters for the current action.

The Selected Properties box lists the properties that have been chosen as output parameters for the current action.

You can then use the Add and Remove buttons to set and unset output parameters from the Available Properties list.

Be sure to click File > Save to save all your Action Input and Output Parameter changes.

If you are editing an existing WSDL file, you need to refresh the existing Wiring Properties design element to update it with your changes. Refer to the topic "Updating or refreshing an edited WSDL file in Domino Designer" for more information on refreshing and updating your Wiring Properties design element.

See Also

WSDL file syntax
Using data types in composite applications
Importing WSDL files in Domino Designer
Exporting WSDL files from Domino Designer
Refreshing a WSDL file in Domino Designer
Specifying an alternate default property editor in Domino Designer

Glossary