WebSphere Message Broker, Version 8.0.0.7
Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS
See information about the latest product version
See information about the latest product version
Data Lineage restrictions
The “New Data Lineage Documents” wizard does not support some types of ESQL transformation.
The following table lists these ESQL transformation types,
and states the corresponding output, if any, of the “New Data Lineage
Documents” wizard:
To work around these limitations, analyze the output files
and manually re-create your mappings in the IBM® InfoSphere® Metadata
workbench.
ESQL transformation type | Explanation | Output from wizard |
---|---|---|
Unmodeled content | ESQL paths for which schema definitions cannot be located in an application, library or message set. | Listed in .reject file |
Environment variable | Paths that are specified in an environment variable cannot include modeled content. | Listed in .reject file |
Mapping that uses literals | Both source and target must be modeled content that is defined in a referenced schema. | Ignored |
ESQL paths that contain one or more wildcards | No mapping
definition is created for the following examples:
|
Listed in .reject file |
User-defined message parser domains | Mapping definitions are generated only for the parser domains that are provided with WebSphere® Message Broker Version 7.0 or later. | Ignored |
Mapping definitions for any Headers, Properties, LocalEnvironment | Both source and target must be modeled content that is defined in a referenced schema. | Listed in .reject file |
Mapping path with an element or attribute that is xs:any type | Mapping definitions with xs:any type is not supported . | Listed in .reject file |
Data model with recursive structure | Recursive structures in data definitions are not supported. | The extended data source document is not created. |
Data model with nested attribute group reference | Nested attribute group references in data definitions are not supported. | Nested attribute group references in data models are not present in the extended data source document. |
Mapping that uses reference, and the value of the reference is changed by a MOVE statement | Mappings do not take account of any use of MOVE on a field reference. | The mapping created in the .csv file shows the initial value of the reference before the MOVE. |