Business Object Map 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.)

Root root

An XPath 1.0 expression that specifies the root of the transformation. This property is used for both the input message and the transformed message.

Field detail	Value and notes
Required	Yes
Valid values	XPath You can specify: `/`, `/headers`, `/context` or `/body`. `/` 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.

Mapping File mappingFile

Specifies the name of the business object map that the mediation primitive uses. The business object map is used to transform data between the input and output business objects.

Field detail	Value and notes
Required	Yes
Valid values	String

containsRelationships

Specifies whether the Business Object Map mediation primitive uses a Business Object map that uses the relationship capability.

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

Considerations

If the Mapping File property is not valid it causes an exception at run time.
The order of transformations can be important.
The business object map associated with the Business Object Map mediation primitive can be stored in the mediation module, or in a library project that you declare as a dependency of the mediation module.
If you use dynamic relationships in the Business Object Map mediation primitive across request and response flows, the display name of the primitive in the response flow must match the corresponding primitive name in the request flow.

Sample XML code

<node name="BOMapper1" type="BOMapper>
  <property name="root" value="/"/>
  <property name="mappingFile" value="myBOMap.map"/>
  <inputTerminal type="myInterface:myRequestMsg"/>
  <outputTerminal type="myInterface:myRequestMsg"/>
  <failTerminal/>
</node>

Topic topic

Terms of use | Feedback

Timestamp icon

Last updated: Sunday, November 24, 2013

http://publib.boulder.ibm.com/infocenter/esbsoa/wesbv7r5/topic//com.ibm.wbit.help.medprim.doc/topics/wesb_bomapper.html
Indirection service link to this topic:: http://www14.software.ibm.com/webapp/wsbroker/redirect?version=wesb800&product=wesb-dist&topic=wesb_bomapper