IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Mapping xs:any on an input or output message

You can use the Cast function to redefine parts of the input or output model in a graphical data map.

In your integration solution, you can create a generic message model, which you can later redefine to a specific model, by using a wildcard, defined as xs:any.

You can redefine an xs:any element in any of the following ways:

Using the Cast function. You can redefine an xs:any element by specifying the specific complex or global type defined in a particular schema file.
Using a transform. You can define a transform, such as the Submap transform, and define the input and output xs:any elements within the nested map of the transform.

For example, in IBM® Integration Bus, a SOAP message is a common example of a generic model in which you are required to define the business data being exchanged through the SOAP protocol. The predefined SOAP message format defines only the structure of the SOAP envelope and allows you to redefine the Header and Body content.

Note: The xs:any input element cannot be involved in a transformation when it is contained within a cast item group. You can either create transformations on the cast elements or remove all associated cast elements to directly transform the xs:any.

Qualify `xs:any` parts of a schema-based message model by using the Cast function

You can define a wildcard in a schema-based message model as an xs:any element to create a flexible message model that can be redefined later.

You use the Cast function to redefine parts of the input or output model in a message map.

For example, you might have a base type of AddressType, and two derived types of USAddressType and CanadianAddressType. Using the Cast function in the Graphical Data Mapping editor, you can cast AddressType to CanadianAddressType.

For more information, see Casting wildcards in a map.

Qualify `xs:any` parts by using a transform

You can specify any of the following transforms between an xs:any element defined on the input message assembly, the output message assembly, or both:

Move transform
If transform
Submap transform
Custom XPATH transform
Custom Java transform

Then, you must specify the input element type and the output element type as a global type in the associated nested map of the transform. You qualify the xs:any elements in the nested map by defining the input and output elements.

cm28855_.htm |

Last updated Friday, 21 July 2017

Mapping xs:any on an input or output message

Qualify xs:any parts of a schema-based message model by using the Cast function

Qualify xs:any parts by using a transform

Qualify `xs:any` parts of a schema-based message model by using the Cast function

Qualify `xs:any` parts by using a transform