Mapping mediation primitive properties

You can specify values for mediation primitive properties either by using the property fields in the IBM® Integration Designer user interface or by using an XML format. The property field names displayed in IBM Integration Designer are generally different from the property names used when building a mediation flow using XML code. In the following information, icons are used to identify each property name used in IBM Integration Designer and the corresponding XML name. (Where applicable, XML names that are required, but not shown in IBM Integration Designer, are also described.)

Parent topic: Mapping mediation primitive

Root root

An XPath 1.0 expression that specifies the root of the mapping. This property is used for both the input message and the transformed message. When you create a new XML map, you can specify the following message roots: /, /headers, /context or /body.

If you select /, /headers or /context as the root, you need to explicitly map all the SMO sections, using the XML mapping editor. Otherwise, you might get errors at run time. If you do not need to change any information in the headers or contexts sections of the SMO, you can use /body as the mapping starting point.
Field detail Value and notes
Required Yes
Valid values XPath
Note:

/ refers to the complete SMO, /headers refers to the headers of the SMO, /context refers to the context of the SMO and /body refers to the body section of the SMO.

Default /

XSLTransform

Specifies the XSLT stylesheet used during the transformation. This is required when the Target engine property in the XML Map is set to XSLT 1.0 or XSLT 2.0.

Field detail Value and notes
Required No
Valid values String
Note:

Mapping file XMXMap

Specifies the name of the XML mapping file, or the XSL stylesheet, that the mediation primitive uses. You can choose either an XML mapping file, with an associated XSL stylesheet or Business Object Map, or an XSL stylesheet on its own.

You can browse existing XML mapping files or create a new mapping file. An XML mapping file has a generated XSL stylesheet or Business Object Map that performs the transformation at run time.

You can browse existing XSL stylesheets, if they exist in the same project as the mediation module.

If you want to override the Mapping file value dynamically, at run time, you must promote the Mapping file property. (However, you must still provide a default value for the Mapping file property.) The override value must resolve to an XSL stylesheet. The stylesheet can be specified as a path to a resource in the project; for example, xslt/TransformCustomer.xsl. Alternatively, the stylesheet can be specified as a URL; for example, http://myserver.com/customerstylsheet.xsl or file://c:/customerstylesheet.xsl.
Note: The stylesheet must be available to the runtime system in order for the transformation to be successful.
Field detail Value and notes
Required No
Valid values String
Note:

Validate input validateInput

If true, the input message is validated at run time, before the mediation is performed.

Field detail Value and notes
Required Yes
Valid values Boolean
Note:
Default false

SMOVersion

This value is always defined as SMO61.

Field detail Value and notes
Required Yes
Valid values
SMO61 SMO61
SMO60 SMO60
Note:
Default SMO60

Considerations

  • If the Mapping file property is not valid, it causes an exception at run time.
  • If Validate input property is true, the input message is validated against its schema, at run time. If the input message does not match its schema, an exception occurs.

Sample XML code

<node name="Mapping1" type="XSLTransformation">
  <property name="root" value="/"/>
  <property name="XSLTransform" value="xslt/Mapping1_req_1.xsl"/>
  <property name="XMXMap" value="xslt/Mapping1_req_1.map"/>
  <property name="SMOVersion" value="SMO61"/>
  <inputTerminal type="XMLSchema:anyType"/>
  <outputTerminal type="XMLSchema:anyType">
    <wire targetNode="TypeFilter1"/>
  </outputTerminal>
  <failTerminal/>
</node>
Note: The node type attribute is XSL Transformation. The Mapping mediation primitive was named the XSL Transformation mediation primitive in WebSphere® ESB Version 7.5.1 and earlier versions.