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

Enable, Disable, or Recycle the Data Integration Service

Enable, Disable, or Recycle the Data Integration Service

You can enable, disable, or recycle the Data Integration Service. You might disable the Data Integration Service if you need to perform maintenance or you need to temporarily restrict users from using the service. You might recycle the service if you changed a service property or if you updated the role for a node assigned to the service or to the grid on which the service runs.
The number of service processes that start when you enable the Data Integration Service depends on the following components which the service can run on:
Single node
When you enable a Data Integration Service that runs on a single node, a service process starts on the node.
Grid
When you enable a Data Integration Service that runs on a grid, a service process starts on each node in the grid that has the service role.
Primary and back-up nodes
When you enable a Data Integration Service configured to run on primary and back-up nodes, a service process is available to run on each node, but only the service process on the primary node starts. For example, you have the high availability option and you configure a Data Integration Service to run on a primary node and two back-up nodes. You enable the Data Integration Service, which enables a service process on each of the three nodes. A single process runs on the primary node, and the other processes on the back-up nodes maintain standby status.
The associated Model Repository Service must be started before you can enable the Data Integration Service.
When you disable the Data Integration Service, you shut down the Data Integration Service and disable all service processes. If you are running the Data Integration Service on a grid, you disable all service processes on the grid.
When you disable the Data Integration Service, you must choose the mode to disable it in. You can choose one of the following options:
  • Complete. Stops all applications and cancels all jobs within each application. Waits for all jobs to cancel before disabling the service.
  • Abort. Stops all applications and tries to cancel all jobs before aborting them and disabling the service.
If big data recovery is enabled on the Data Integration Service, run
infacmd ms abortAllJobs
before you disable or recycle the service.
When you recycle the Data Integration Service, the Service Manager restarts the service. When the Service Manager restarts the Data Integration Service, it also restores the state of each application associated with the Data Integration Service.
When you prepare to recycle or shut down a Data Integration Service running on a grid, verify that no jobs are running. If you recycle or shut down the service while jobs are running, a Data Integration Service node might recover the aborted jobs and re-run them. To ensure jobs are not recovered, use the
infacmd ms abortAllJobs
command before you issue the shut down request. The command gracefully aborts all running jobs and prevents them from being re-run.‭
Observe the following guidelines:
  • Choosing the option to abort all running jobs in the Administrator tool shut down dialog does not have the same effect as using the
    abortAllJobs
    command. To ensure all jobs on a Data Integration Service grid are stopped and not recovered, use the
    infacmd ms abortAIIJobs
    command before you issue the shutdown request.
  • When you shut down or recycle a Data Integration Service with a single node, or with a primary + backup node setup, the Data Integration Service aborts all jobs and does not recover them.