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 CSV files
Comma-separated value (CSV) files for use in
impact analysis and data lineage.
You can export all mapping transformations from all Compute nodes in a specified application, library, or WebSphere® Message Broker project. You can also create extended data source documents for schemas in a message set project.
The resulting CSV files can be imported into products, such as IBM® InfoSphere® Metadata Workbench, that can
perform impact analysis and data lineage operations.
- Data lineage
- See where the information comes from, and what happens to it as it moves across data integration processes.
- Impact analysis
- Determine the effects of changing a field in the information flow.
The Data Lineage Documents wizard creates
the following artifact as CSV files:
- Extension Mapping Documents
- This artifact contains rows of mappings from WebSphere Message
Broker transformations between message
models in a message flow. One mapping document is created for each
flow, containing all mappings done by different Compute nodes in the flow.
Each transformation in a node is recorded on its own row:
The fields are as follows:Name,Source Columns,Target Columns,Rule,Function,Specification Description "Compute","WMBMessageModels.ShipOrderLibLibrary.shipPartRequest.shipPartRequest/partNo","WMBMessageModels.ShipOrderLibLibrary.shipPartResponse.shipPartResponse/partNo",,,"{}ProcessShipping_Compute.Main" "Compute","WMBMessageModels.ShipOrderLibLibrary.shipPartRequest.shipPartRequest/partQuantity","WMBMessageModels.ShipOrderLibLibrary.shipPartResponse.shipPartResponse/partQuantity",,,"{}ProcessShipping_Compute.Main"
- Name
- The name of the node in the message flow.
- Source Columns
- The source of the mappings.
- Target Columns
- The target of the mappings.
- Rule
- Not currently used.
- Function
- A list of user-defined or built-in functions that are being called in the mapping. If the list exceeds 255 characters, it is truncated.
- Specification Description
- The Compute node module
or ESQL procedure or function where the mapping takes place, that
is where the target is being mapped. If it is in a function or procedure
inside a compute module, it has this form:
If it is a procedure or function outside the module scope, the procedure or function name is shown, for example:{broker.schema1}MyMessageFlow2_Compute.Main, {}Compute2.CopyEntireMessage.
{broker.schema1}ExternalProcedure1
Not all ESQL transformations are supported; see Data Lineage restrictions.