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

Configuring Java Transformation Properties

Configuring Java Transformation Properties

The Java transformation includes properties for both the transformation code and the transformation. If you create a Java transformation in the Transformation Developer, you can override the transformation properties when you use it in a mapping.
The following table describes the Java transformation properties:
Property
Description
Language
Language used for the transformation code. You cannot change this value.
Class Name
Name of the Java class for the transformation. You cannot change this value.
Tracing Level
Amount of detail displayed in the session log for this transformation. Use the following tracing levels:
  • Terse
  • Normal
  • Verbose Initialization
  • Verbose Data
Default is Normal.
Is Partitionable
Multiple partitions in a pipeline can use this transformation. Use the following options:
  • No. The transformation cannot be partitioned. The transformation and other transformations in the same pipeline are limited to one partition. You might choose No if the transformation processes all the input data together, such as data cleansing.
  • Locally. The transformation can be partitioned, but the Integration Service must run all partitions in the pipeline on the same node. Choose Locally when different partitions of the transformation must share objects in memory.
  • Across Grid. The transformation can be partitioned, and the Integration Service can distribute each partition to different nodes.
Default is No.
Inputs Must Block
The procedure associated with the transformation must be able to block incoming data. Default is enabled.
Is Active
The transformation can generate more than one output row for each input row.
You cannot change this property after you create the Java transformation. If you need to change this property, create a new Java transformation.
Update Strategy Transformation
The transformation defines the update strategy for output rows. You can enable this property for active Java transformations.
Default is disabled.
Transformation Scope
The method in which the Integration Service applies the transformation logic to incoming data. Use the following options:
  • Row
  • Transaction
  • All Input
This property is always Row for passive transformations. Default is All Input for active transformations.
Generate Transaction
The transformation generates transaction rows. You can enable this property for active Java transformations.
Default is disabled.
Output Is Repeatable
The order of the output data is consistent between session runs.
  • Never. The order of the output data is inconsistent between session runs.
  • Based On Input Order. The output order is consistent between session runs when the input data order is consistent between session runs.
  • Always. The order of the output data is consistent between session runs even if the order of the input data is inconsistent between session runs.
Default is Never for active transformations. Default is Based On Input Order for passive transformations.
Requires Single Thread Per Partition
A single thread processes the data for each partition.
You cannot change this value.
Output Is Deterministic
The transformation generates consistent output data between session runs. Enable this property to perform recovery on sessions that use this transformation.
Default is enabled.
If you configure a transformation as repeatable and deterministic, it is your responsibility to ensure that the data is repeatable and deterministic. If you try to recover a session with transformations that do not produce the same data between the session and the recovery, the recovery process can result in corrupted data.

0 COMMENTS

We’d like to hear from you!