Data Integration
- Data Integration
- All Products
Property
| Description
|
---|---|
Behavior
| Transformation behavior, either active or passive. If active, the transformation can generate more than one output row for each input row. If passive, the transformation generates one output row for each input row.
Default is Active.
|
Tracing Level
| Detail level of error and status messages that
Data Integration writes in the session log. You can choose terse, normal, verbose initialization, or verbose data. Default is normal.
|
Transformation Scope
| The method in which the Secure Agent applies the transformation logic to incoming data. Use the following options:
For active transformations, default is All Input. For passive transformations, this property is always set to Row.
|
Defines Update Strategy
| Specifies whether the transformation defines the update strategy for output rows. When enabled, the Java code determines the update strategy for output rows. When disabled, the update strategy is determined by the operation set in the Target transformation.
You can configure this property for active Java transformations.
Default is disabled.
|
Enable High Precision
| Enables high precision to process decimal fields with the Java class BigDecimal. Enable this option to process decimal data types with a precision greater than 15 and less than 28.
Default is disabled.
In advanced mode, the Java transformation always uses high precision.
|
Use Nanoseconds in Date/Time
| Specifies whether the generated Java code converts the transformation date/time data type to the Java BigDecimal data type, which has nanosecond precision.
When enabled, the generated Java code converts the transformation date/time data type to the Java BigDecimal data type. When disabled, the code converts the date/time data type to the Java long data type, which has millisecond precision.
Default is disabled.
|
Optional
| Determines whether the transformation is optional. If a transformation is optional and there are no incoming fields, the
mapping task can run and the data can go through another branch in the data flow. If a transformation is required and there are no incoming fields, the task fails.
For example, you configure a parameter for the source connection. In one branch of the data flow, you add a transformation with a field rule so that only Date/Time data enters the transformation, and you specify that the transformation is optional. When you configure the
mapping task, you select a source that does not have Date/Time data. The
mapping task ignores the branch with the optional transformation, and the data flow continues through another branch of the mapping.
Default is enabled.
|
Design Time Classpath
| Classpath that the Secure Agent uses for custom or third-party packages when you design and validate the transformation and when you run the mapping from the Mapping Designer.
This classpath is not used when you run the mapping through a
mapping task.
Set the design-time classpath when you want to test the transformation and neither the JVMClassPath property for the Secure Agent nor the CLASSPATH environment variable on the Secure Agent machine contain the required packages. If you configured the JVMClassPath property or the CLASSPATH environment variable to include the required packages, then you do not need to configure this property.
|