Table of Contents

Search

  1. Preface
  2. Transformations
  3. Source transformation
  4. Target transformation
  5. Access Policy transformation
  6. Aggregator transformation
  7. B2B transformation
  8. Chunking transformation
  9. Cleanse transformation
  10. Data Masking transformation
  11. Data Services transformation
  12. Deduplicate transformation
  13. Expression transformation
  14. Filter transformation
  15. Hierarchy Builder transformation
  16. Hierarchy Parser transformation
  17. Hierarchy Processor transformation
  18. Input transformation
  19. Java transformation
  20. Java transformation API reference
  21. Joiner transformation
  22. Labeler transformation
  23. Lookup transformation
  24. Machine Learning transformation
  25. Mapplet transformation
  26. Normalizer transformation
  27. Output transformation
  28. Parse transformation
  29. Python transformation
  30. Rank transformation
  31. Router transformation
  32. Rule Specification transformation
  33. Sequence transformation
  34. Sorter transformation
  35. SQL transformation
  36. Structure Parser transformation
  37. Transaction Control transformation
  38. Union transformation
  39. Vector Embedding transformation
  40. Velocity transformation
  41. Verifier transformation
  42. Web Services transformation

Transformations

Transformations

Sample transaction control mappings with multiple targets

Sample transaction control mappings with multiple targets

In a mapping with multiple targets, a Transaction Control transformation can be effective for one target and ineffective for another target. If each target is connected to an effective Transaction Control transformation, the mapping is valid. If one target in the mapping is not connected to an effective Transaction Control transformation, the mapping is invalid.
The following image shows a valid mapping with both an ineffective and an effective Transaction Control transformation:
The mapping contains two pipelines. The first pipeline contains the following transformations: Source, TransactionControl_1, Expression_1, Target_1. The second pipeline contains the following transformations: Source, TransactionControl_1, Aggregator, Expression_2, TransactionControl_2, Target_2.
Data Integration
processes TransactionControl_1, evaluates the transaction control expression, and creates transaction boundaries. The mapping does not include a transformation that drops transaction boundaries between TransactionControl_1 and Target_1, making TransactionControl_1 effective for Target_1.
Data Integration
uses the transaction boundaries defined by TransactionControl_1 for Target_1.
However, the mapping includes a transformation that drops transaction boundaries between TransactionControl_1 and Target_2, which makes TransactionControl_1 ineffective for Target_2. When
Data Integration
processes the Aggregator transformation, with transformation scope set to All Input, it drops the transaction boundaries defined by TransactionControl_1 and outputs all rows in an open transaction. Then
Data Integration
evaluates TransactionControl_2, creates transaction boundaries, and uses them for Target_2.
If a roll back occurs in TransactionControl_1,
Data Integration
rolls back only rows from Target_1. It does not roll back any rows from Target_2.
The following image shows an invalid mapping with both an ineffective and an effective Transaction Control transformation:
The mapping contains two pipelines. The first pipeline contains the following transformations: Source, mapplet "mplt_TransactionControl," Aggregator_1, Target_1. The second pipeline contains the following transformations: Source, mapplet "mplt_TransactionControl," Aggregator_2, Expression, TransactionControl_2, Target_2.
The mapplet, mplt_TransactionControl, contains a Transaction Control transformation. It is ineffective for Target_1 and Target_2. The transformation scope for Aggregator_1 is All Input. It is an active source for Target_1. The transformation scope for Aggregator_2 is All Input. It is an active source for Target_2. TransactionControl_2 is effective for Target_2.
The mapping is invalid because Target_1 is not connected to an effective Transaction Control transformation.

0 COMMENTS

We’d like to hear from you!