Mapping node syntax

In a Mapping node, the source message, if present, is identified in the Message Mapping editor by $source.

The message tree is represented in XPath format. For example, if you have an element called Body within a source message called Envelope, this is represented in the Mapping node as:
  $source/soap11:Envelope/soap11:Body
Where soap11 is a namespace prefix.

The first target message is identified by $target; additional target messages are identified by $target_1, $target_2, etc.

The first source database is identified by $db:select; additional source databases are identified by $db:select_1, $db:select_2, etc.

The database element is represented in the following format:
  $db:select.DB.SCH.TAB.COL1
where: You can also use the Mapping node to: The comparison operators are: The arithmetic operators are: Conditional operators ‘or’ and ‘and’ are supported (these are case-sensitive).
The following objects can be mapped:
Start of change

Naming restrictions for database objects

The names of objects in Oracle databases can contain certain characters, such as the dollar sign ($) and number sign (#), which the Mapping node cannot process correctly. Database table names, table column names, stored procedure parameter names, and column names in stored procedure result sets, must not contain any of the following characters:
~ ! @ # $ % ^ & * ( ) + = - ` { } | \ ] [ " 
: ' ; ? > < , . /
End of change
Related concepts
Mapping node functions
Mapping node casts
Message Mapping editor
Mapping node
Start of changeLocal environment tree structureEnd of change
Related tasks
Developing message mappings
Configuring the LocalEnvironment
Related reference
Mapping node
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009.
Last updated : 2009-01-07 15:22:59

ar00900_