Table of Contents

Search

  1. Preface
  2. Analyst Service
  3. Catalog Service
  4. Content Management Service
  5. Data Integration Service
  6. Data Integration Service Architecture
  7. Data Integration Service Management
  8. Data Integration Service Grid
  9. Data Integration Service Applications
  10. Interactive Data Preparation Service
  11. Enterprise Data Preparation Service
  12. Informatica Cluster Service
  13. Mass Ingestion Service
  14. Metadata Access Service
  15. Metadata Manager Service
  16. Model Repository Service
  17. PowerCenter Integration Service
  18. PowerCenter Integration Service Architecture
  19. High Availability for the PowerCenter Integration Service
  20. PowerCenter Repository Service
  21. PowerCenter Repository Management
  22. PowerExchange Listener Service
  23. PowerExchange Logger Service
  24. SAP BW Service
  25. Search Service
  26. System Services
  27. Test Data Manager Service
  28. Test Data Warehouse Service
  29. Web Services Hub
  30. Application Service Upgrade
  31. Appendix A: Application Service Databases
  32. Appendix B: Connecting to Databases from Windows
  33. Appendix C: Connecting to Databases
  34. Appendix D: Updating the DynamicSections Parameter of a DB2 Database

Process Where DTM Instances Run

Process Where DTM Instances Run

Based on how you configure the Data Integration Service, DTM instances can run in the Data Integration Service process, in a separate DTM process on the local node, or in a separate DTM process on a remote node.
A DTM process is an operating system process that the Data Integration Service starts to run DTM instances. Multiple DTM instances can run within the Data Integration Service process or within the same DTM process.
The
Launch Job Options
property on the Data Integration Service determines where the service starts DTM instances. Configure the property based on whether the Data Integration Service runs on a single node or a grid and based on the types of jobs that the service runs.
The following table lists each process where DTM instances can run:
Process Where DTM Instances Run
Data Integration Service Configuration
Types of Jobs
In the Data Integration Service process
Single node or grid
Any job that runs on a single node or on a grid where each node has both the service and compute roles.
Jobs that run in the service process achieve better performance, but stability decreases.
Recommendation:
Run SQL data service and web service jobs in the service process to increase performance.
In separate DTM processes on the local node
Single node or grid
Any job that runs on a single node or on a grid where each node has both the service and compute roles.
Run jobs in separate local processes to increase stability. Stability increases because an unexpected interruption to one job does not affect all other jobs.
Recommendation:
Run mapping, profile, and workflow jobs in separate processes. You can run SQL data service and web service jobs in separate local processes, but performance might decrease.
In separate DTM processes on remote nodes
Grid
Mapping, profile, and workflow jobs on a grid where nodes have a different combination of roles.
Run jobs in separate remote processes to increase stability. Stability increases because an unexpected interruption to one job does not affect all other jobs. In addition, you can better use the resources available on each node in the grid. When a node has the compute role only, the node does not have to run the service process. The machine uses all available processing power to run mappings.
You cannot run SQL data service and web service jobs in separate DTM processes on remote nodes.
Ad hoc jobs, with the exception of profiles, can run in the Data Integration Service process or in separate DTM processes on the local node. Ad hoc jobs include mappings run from the Developer tool or previews, scorecards, or drill downs on profile results run from the Developer tool or Analyst tool. If you configure a Data Integration Service grid to run jobs in separate remote processes, the service runs ad hoc jobs in separate local processes.