-
Notifications
You must be signed in to change notification settings - Fork 82
rel hier mapping
Icon |
|
---|---|
Use When |
Data needs to be mapped from a relational model to a hierarchical one |
Samples |
|
Description |
The mapping component allows you to map relational messages to hierarchical messages |
Inbound Message Type |
Model Based Message |
Output Message Type |
Model Based Message |
Control Message Handling |
Input: As entity messages are received this component will process the data. Otherwise, when the input message is not an entity message and the 'Hierarchical Query Method' is 'BY QUERY' and the Unit of Work Boundary is received then the messages will be processed. Output: A single control message will be forwarded to downstream components once all messages have been processed through this step. |
Name | Description |
---|---|
Whether to forward failed messages and continue processing. This is the name of a linked component to forward the failed messages to. |
|
Set Unmapped Attributes To Null |
Whether attributes in the output model that don’t have a mapping specified from the input model should be set to null. |
Hierarchical Query Method |
Determines the method by which hierarchical relationships are formed from the relational data. Either BY_QUERY or BY_JOIN. Defaults to by join. Using the BY_JOIN method, relational data is sent to the relational / hierarchical mapper based on a single joined query from an rdbms reader. When the joined data comes in to the mapper, it completes control/break logic on the data to transform it into the hierarchical model. The control break logic is based on foreign key definitions in the relational model. Using the BY_QUERY method allows one or more queries to be run from one or more rdbms readers for each entity in the hierarchical model. |