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 Transaction Boundaries

Working with Transaction Boundaries

The Integration Service handles transaction boundaries entering and leaving Custom transformations based on the mapping configuration and the Custom transformation properties.
The following table describes how the Integration Service handles transaction boundaries at Custom transformations:
Transformation Scope
Generate Transactions Enabled
Generate Transactions Disabled
Row
Integration Service drops incoming transaction boundaries and does not call the data boundary notification function.
It outputs transaction rows according to the procedure logic across all output groups.
When the incoming data for all input groups comes from the same transaction control point, the Integration Service preserves incoming transaction boundaries and outputs them across all output groups. However, it does not call the data boundary notification function.
When the incoming data for the input groups comes from different transaction control points, the Integration Service drops incoming transaction boundaries. It does not call the data boundary notification function. The Integration Service outputs all rows in one open transaction.
Transaction
Integration Service preserves incoming transaction boundaries and calls the data boundary notification function.
However, it outputs transaction rows according to the procedure logic across all output groups.
Integration Service preserves incoming transaction boundaries and calls the data boundary notification function.
It outputs the transaction rows across all output groups.
All Input
Integration Service drops incoming transaction boundaries and does not call the data boundary notification function. The Integration Service outputs transaction rows according to the procedure logic across all output groups.
Integration Service drops incoming transaction boundaries and does not call the data boundary notification function. It outputs all rows in one open transaction.

0 COMMENTS

We’d like to hear from you!