|Skip Navigation Links|
|Exit Print View|
|Oracle Java CAPS BPEL Designer and Service Engine User's Guide Java CAPS Documentation|
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.
The Normalized Message properties are accessed from the BPEL Designer Mapper view. When you expand a variable's Properties folder it exposes the variables predefined NM properties. If the specific NM property you need is not currently listed, additional NM properties can be added.
Predefined Normalized Message properties are ready for use, from a variable's Properties file.
The Properties file contains the predefined Normalized Message (NM) properties.
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.
The Add NM Property Shortcut dialog box appears.
Property Name: The NM property name (see each binding component's documentation for available NM properties).
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.
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.
The Add NM Property Shortcut dialog box appears.
The NM Property Shortcut is deleted.
The Add NM Property dialog box appears.
Property Name: User-defined property name. This name is displayed in mapper tree and stored in WSDL file.
Type or Element:Displays the property type or element associated with the selected node in the Map Property To tree.
Associate property with message: To associate the new NM property with all variables of any message type select this checkbox.
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.
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.
Sync with tree:When this checkbox is selected, the Query field is automatically synchronized with the selected node in the Map Property To tree.
Query: Displays the query type associated with the selected node in the Map Property To tree.
The new NM property can now be used in assigns and to build expressions.
The property is deleted.
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:
Normalized Message properties are either General, available to all participating JBI components, or protocol/binding specific, used by a particular binding component. The following General NM properties are available to all binding components.
Table 1 General Normalized Message Properties
Binding components each have their own protocol specific Normalized Message properties. These include inbound and outbound specific, as well as general NM properties for each binding component.
For a list of binding component specific NM properties, refer to the following: