Using the HTTP Binding Component

Contents

• Using the HTTP Binding Component
• About the HTTP Binding Component
• HTTP/SOAP Binding Architecture
• HTTP Binding Component Features
• HTTP Binding Component Example Scenario
• SOAP Processing
• HTTP Processing
• HTTP GET and POST Processing
• HTTP Binding Component Runtime Properties
• HTTP Binding Component Client Endpoint Properties
• Using Normalized Message Properties to Propagate Binding Context Information
  • Using Normalized Message Properties in a BPEL Process
  • BPEL Code Generation Using NM Properties
  • Normalized Message Properties
• Configuring Quality of Service (QOS) Features
• Using the Tango Web Service Attributes with the HTTP Binding Component
• Configuring Web Service Attributes
• HTTP Binding Component Security
• Using Application Variables to Define Name/Value Pairs
• Using Application Configuration to Configure Connectivity Parameters
• Logging and Statistics Monitoring
• Using WS-Atomic Transaction
• Clustering Support for the HTTP Binding Component
• Common User Scenarios

Using Normalized Message Properties to Propagate Binding Context Information

Normalized Message properties are commonly used to specify metadata that is associated with message content. javax.jbi.security.subject and javax.jbi.message.protocol.type are two examples of standard normalized Message properties defined in the JBI Specification.

Normalized Message properties are used to provide additional capabilities in Open ESB, such as:

• Getting and Setting transport context properties. For example, HTTP headers in the incoming HTTP request, or file names read by the File Binding Component
  
• Getting and Setting protocol specific headers or context properties (SOAP headers)
  
• Getting and Setting additional message metadata. For example. a unique message identifier, or an endpoint name associated with a message
  
• Dynamic configurations. For example, to dynamically overwrite the statically configured destination file name at runtime
  

Some of the use cases mentioned above require protocol/binding specific properties, typically used by a particular binding component. Other properties are considered common or general purpose properties that all participating JBI components make use of, for example, the message ID property, which can be utilized to uniquely identify or track a given message in the integration.

Using Normalized Message Properties in a BPEL Process

The Normalized Message properties are accessed from the BPEL Designer Mapper view. When you expand a variable's Properties folder it exposes the variable's predefined NM properties, as well as the regular BPEL specific WSDL properties used in correlation sets, assigns, and to build expressions . If the specific NM property you need is not currently listed, additional NM properties can be added.

Using predefined Normalized Message Properties in a BPEL process

Predefined Normalized Message properties are ready for use, from a variable's Properties file.

To use predefined normalized message properties in a BPEL process:

1. From the Design View diagram, select the activity with the process you want to edit.
2. Click Mapper to switch to the Mapper view of the BPEL process.
3. From the Output pane, expand the Variable you want to edit and its Properties file. The Properties file contains the predefined Normalized Message (NM) properties.
4. To use a predefined NM Property, select the property and use it to build an expression or an assign.

Adding additional Normalized Message Properties to a BPEL process

If the specific NM Property you want is not listed, you can add additional NM properties.

There are two options available when adding NM Properties:

• Add NM Property Shortcut: This option typically supports simple type properties, in that it does not grant access to some data within the NM Property.
  
• Add NM Property: This option provides access to data within the NM property used to build expressions.
  

To add a Normalized Message Property Shortcut to a BPEL process:

1. From the Output or Input panes of the BPEL Mapper, expand the node for the variable to which you want to add an NM property. Right-click that variables Properties directory node and select Add NM Property Shortcut from the pop-up menu.
   The Add NM Property Shortcut dialog box appears.
2. Enter the information for the new NM property into the the Add NM Property Shortcut dialog box, as follows:
3. Property Name: The NM property name (see each binding component's documentation for available NM properties).
4. Display Name:The display name for the NM property. This is a user-defined name that appears in the Mapper tree. The display name is optional.
5. Click OK. The new NM property is added to the Mapper tree under the variables Properties directory. The property can now be used in assigns and to build expressions.

To edit an NM Property shortcut

1. To edit an existing NM property shortcut, right-click the NM property shortcut in the BPEL Mapper tree and choose Edit NM Property Shortcut in the pop-up menu. The Add NM Property Shortcut dialog box appears.
2. Edit the NM Property Name or Display Name, and click OK.

To delete an NM Property shortcut

1. To delete an NM property shortcut, right-click the property in the Mapper tree.
2. Choose Delete NM Property Shortcut in the pop-up menu. The NM Property Shortcut is deleted.

To add a Normalized Message Property to a BPEL process

1. From the Output or Input panes of the BPEL Mapper, expand the node for the variable to which you want to add an NM property. Right-click that variables Properties directory node and select Add NM Property from the pop-up menu. The Add NM Property dialog box appears.
2. Enter the information for the new NM property in the the Add NM Property dialog box, as follows:
3. Property Name: User-defined property name. This name is displayed in mapper tree and stored in WSDL file.
4. Type or Element:Displays the property type or element associated with the selected node in the Map Property To tree.
5. Associate property with message: Specifies with which message type the property is associated.
   • A checkmark indicates that the new NM property is associated with all variables of the specified message type. For example, in the image below, the new NM property will be associated with the requestMessage type.
     
   • Unchecked indicates that the new NM property is associated with all variables of any message type.
     
6. Map Property To: The Map Property To tree displays all of the predefined NM properties. This is used to build a query or choose a property type. When you select a node within the property tree the Type or Element and Query fields are populated automatically. Valid endpoint nodes are displayed in bold.
7. New NM Property: Select the New NM Property checkbox to add a specific NM property, and enter the name of the property in the New NM Property field. The new NM property is added to the Map Property To tree.
8. Sync with tree:When this checkbox is selected, the Query field is automatically synchronized with the selected node in the Map Property To tree.
9. Query: Displays the query type associated with the selected node in the
10. Click OK. The new NM property name is added to the tree in the BPEL Mapper, and the NM property is stored in nmPropertiesDefinitions.wsdl as a pair of elements: <vprop:property> and <vprop:propertyAlias>.
    The new NM property can now be used in assigns and to build expressions.

To delete an NM Property

1. To delete a new NM property, right-click the property in the Mapper tree.
2. Choose Delete NM Property in the pop-up menu.
   The property is deleted.

BPEL Code Generation Using NM Properties

Data copied from an NM property or an NM property shortcut generates code that is similar to the following:

<from variable="inputVar" sxnmp:nmProperty="org.glassfish.openesb.file
.outbound.dcom.username"/>

Data copied from WSDL properties based on NM property generates code that is similar to the following:

<from variable="inputVar" property="ns3:DemoNMProperty"/>

When properties and NM properties are used to build an expression, code similar to the following code is generated:

<from>concat(bpws:getVariableProperty('inputVar', 'ns3:DemoNMProperty'), 
sxnmp:getVariableNMProperty('inputVar','org.glassfish.openesb.file.outbound.dcom.
username'))</from>

An NM property used in a condition generates code that is similar to the following:

<condition>sxnmp:getVariableNMProperty('inputVar', 'my.nmProperty.boolean')</condition>

Normalized Message Properties

Normalized Message properties are either General, available to all participating JBI components, or protocol/binding specific, used by a particular binding component.

Table 19 General Normalized Message Properties

SOAP HTTP Binding Component specific Normalized Message Properties

The following properties are specific to the HTTP (SOAP) Binding Component.

Table 20 SOAP HTTP Binding Component NM Properties

Previous
Next

This page (revision-9) was last changed on 15-Jul-09 15:36 PM, -0700 by rjacobus.
This page was created on 05-Dec-08 08:47 AM, -0800 by rjacobus.

More info...