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:
- DB is the database name
- SCH is the database schema name
- TAB is the table name
- COL1 is the column name
You can also use the
Mapping node to:
- make comparisons
- perform arithmetic
- create complex conditions
The comparison operators are:
- = equals
- != not equals
- > greater than
- >= greater than or equals
- < less than
- <= less than or equals
The arithmetic operators are:
- + plus
- - minus
- * multiply
- div divide
Conditional operators ‘or’ and ‘and’ are supported (these are case-sensitive).
The following objects can be mapped:
- Local Environment
- Message headers (optional)
- MQ Headers
- HTTP Headers
- JMSTransport
- Message elements
- Database columns

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:
~ ! @ # $ % ^ & * ( ) + = - ` { } | \ ] [ "
: ' ; ? > < , . /
