Table of Contents

Search

  1. Preface
  2. Working with Transformations
  3. Aggregator Transformation
  4. Custom Transformation
  5. Custom Transformation Functions
  6. Data Masking Transformation
  7. Data Masking Examples
  8. Expression Transformation
  9. External Procedure Transformation
  10. Filter Transformation
  11. HTTP Transformation
  12. Identity Resolution Transformation
  13. Java Transformation
  14. Java Transformation API Reference
  15. Java Expressions
  16. Java Transformation Example
  17. Joiner Transformation
  18. Lookup Transformation
  19. Lookup Caches
  20. Dynamic Lookup Cache
  21. Normalizer Transformation
  22. Rank Transformation
  23. Router Transformation
  24. Sequence Generator Transformation
  25. Sorter Transformation
  26. Source Qualifier Transformation
  27. SQL Transformation
  28. Using the SQL Transformation in a Mapping
  29. Stored Procedure Transformation
  30. Transaction Control Transformation
  31. Union Transformation
  32. Unstructured Data Transformation
  33. Update Strategy Transformation
  34. XML Transformations

Transformation Guide

Transformation Guide

Working with Transactions

Working with Transactions

When the Integration Service processes a Joiner transformation, it can apply transformation logic to all data in a transaction, all incoming data, or one row of data at a time. The Integration Service can drop or preserve transaction boundaries depending on the mapping configuration and the transformation scope. You configure how the Integration Service applies transformation logic and handles transaction boundaries using the transformation scope property.
You configure transformation scope values based on the mapping configuration and whether you want to preserve or drop transaction boundaries.
You can preserve transaction boundaries when you join the following sources:
  • You join two branches of the same source pipeline.
    Use the Transaction transformation scope to preserve transaction boundaries.
  • You join two sources, and you want to preserve transaction boundaries for the detail source.
    Use the Row transformation scope to preserve transaction boundaries in the detail pipeline.
You can drop transaction boundaries when you join the following sources:
  • You join two sources or two branches and you want to drop transaction boundaries
    . Use the All Input transformation scope to apply the transformation logic to all incoming data and drop transaction boundaries for both pipelines.
The following table summarizes how to preserve transaction boundaries using transformation scopes with the Joiner transformation:
Transformation Scope
Input Type
Integration Service Behavior
Row
Unsorted
Preserves transaction boundaries in the detail pipeline.
Row
Sorted
Session fails.
Transaction
Sorted
Preserves transaction boundaries when master and detail originate from the same transaction generator. Session fails when master and detail do not originate from the same transaction generator
Transaction
Unsorted
Session fails.
All Input
Sorted, Unsorted
Drops transaction boundaries.
Sessions fail if you use real-time data with All Input or Transaction transformation scopes.

0 COMMENTS

We’d like to hear from you!