Table of Contents

Search

  1. Preface
  2. Introducing Administrator
  3. Organizations
  4. Licenses
  5. Ecosystem single sign-on
  6. SAML single sign-on
  7. Source control and service upgrade settings
  8. Users and user groups
  9. User roles
  10. Permissions
  11. Runtime environments
  12. Serverless runtime environments
  13. Secure Agent services
  14. Secure Agent installation
  15. Schedules
  16. Bundle management
  17. Event monitoring
  18. File transfer
  19. Troubleshooting

Administrator

Administrator

Guidelines for stopping and starting services

Guidelines for stopping and starting services

Use the following guidelines when you stop and start services on a Secure Agent:
  • Use caution when you stop services on a Secure Agent because stopping services can cause job failures.
    When you stop a service, any job that requires the service and is currently running on the agent stops. If there are no other agents in the group, the job can no longer run. If there are other agents in the group, you can restart the job and it will run on a different agent.
  • Do not stop the Data Integration Server on an agent if you store connection properties with the agent.
    If you store connection properties with a local Secure Agent and you stop the Data Integration Server on the agent, users will not be able to access any connections or run tasks in the organization. Any job that is currently running on the agent also fails.
  • Do not stop and start services to reserve a Secure Agent group for certain types of jobs.
    If you want to reserve a Secure Agent group for certain types of jobs, you can enable the required services for the Secure Agent group and disable other services. For more information about enabling and disabling services for a Secure Agent group, see Service assignment for Secure Agent groups.


Updated August 03, 2020