This section describes new Data Integration Service features in version 10.0.
Architecture
Effective in version 10.0, the Data Integration Service includes the following types of components:
Service components
Service components include modules that manage requests from client tools, the logical Data Transformation Manager (LDTM) that optimizes and compiles jobs, and managers that manage application deployment and caches. The service components run within the Data Integration Service process. The Data Integration Service process must run on a node with the service role.
Compute component
The compute component of the Data Integration Service is the execution Data Transformation Manager (DTM). The DTM extracts, transforms, and loads data to complete a data transformation job. The DTM must run on a node with the compute role.
When the Data Integration Service runs on a single node, the service and compute components of the Data Integration Service run on the same node. The node must have both the service and compute roles.
When the Data Integration Service runs on a grid, the service and compute components of the Data Integration Service can run on the same node or on different nodes, based on how you configure the grid and the node roles. When you configure a Data Integration Service grid to run jobs in separate remote processes, the nodes in the grid can have a combination of the service only role, the compute only role, and both the service and compute roles. Some nodes in the grid are dedicated to running the service processes while other nodes are dedicated to running mappings.
For more information about Data Integration Service components, see the "Data Integration Service Architecture" chapter in the
Informatica 10.0 Application Service Guide
.
DTM Resource Allocation Policy
Effective in version 10.0, the Data Transformation Manager resource allocation policy determines how to allocate the CPU resources for tasks. The DTM uses an on-demand resource allocation policy to allocate CPU resources.
For more information about the DTM resource allocation policy, see the "Data Integration Service Architecture" chapter in the
Informatica 10.0 Application Service Guide
.
ASCII Data Movement Mode
Effective in version 10.0, the logical Data Transformation Manager (LDTM) component of the Data Integration Service determines whether to use the ASCII or Unicode data movement mode for mappings that read from a flat file or relational source. The LDTM determines the data movement mode based on the character sets that the mapping processes. When a mapping processes all ASCII data, the LDTM selects the ASCII mode. In ASCII mode, the Data Integration Service uses use one byte to store each character, which can optimize mapping performance. In Unicode mode, the service uses two bytes for each character.
For more information about the data movement mode, see the "Data Integration Service Architecture" chapter in the
Informatica 10.0 Application Service Guide
.
Maximize Parallelism for Profiles
Effective in version 10.0, you can enable the Data Integration Service to maximize parallelism when it runs a column profile and performs data domain discovery if you have the partitioning option. When you maximize parallelism, the Data Integration Service dynamically divides the profiling data into partitions and uses multiple threads to concurrently process the partitions. When the Data Integration Service uses additional threads, the service can optimize profiling performance.
For more information about how to maximize parallelism, see the "Data Integration Service Management" chapter in the
Informatica 10.0 Application Service Guide
.
Multiple Cache, Target, and Temporary Directories
Effective in version 10.0, you can configure multiple directories for the following Data Integration Service properties:
Cache Directory
Configure multiple cache directories to optimize performance during cache partitioning for Aggregator, Joiner, or Rank transformations.
Target Directory
Configure multiple target directories to optimize performance when multiple partitions write to a flat file target.
Temporary Directories
Configure multiple temporary directories to optimize performance during cache partitioning for Sorter transformations.
For more information about optimizing cache and target directories for partitioning, see the "Data Integration Service Management" chapter in the
