By default, each Secure Agent in an organization runs all microservices that are used for data processing in the organization. You can stop and start the microservices to perform troubleshooting, optimize resources on the agent machine, or make configuration changes. When you stop or start a Secure Agent microservice, other microservices that run on the agent are not affected.
The microservices that you stop and start on a Secure Agent are the Secure Agent services, which are different from the Informatica Intelligent Cloud Services. For example, if you want to stop the services associated with Operational Insights, you must stop the OI Data Collector service on the agent. For more information about Secure Agent services, see Secure Agent Services.
You might need to stop and restart a Secure Agent service in the following circumstances:
You need to troubleshoot issues with a specific Secure Agent service.
If a Secure Agent service shows an error state, you can stop the service, troubleshoot the problem, and then restart the service.
You are running memory or CPU intensive jobs, and you want to optimize computing resources on the Secure Agent machine.
For example, your organization runs Data Integration and Application Integration jobs. You want to optimize computing resources so that the Data Integration jobs run during the day and the Application Integration jobs run at night. To do this, stop Process Server during the day and restart it in the evening, and stop the Data Integration Server at night and restart it in the morning.
You update service configuration properties for the File Integration Service.
After you change configuration properties for the File Integration Service, you must restart the service. If the Secure Agent runs other services, you can stop and restart the File Integration Service without affecting the other services.
To start or stop a service on a Secure Agent, you must have update permission on the Secure Agent.
If you are the administrator of a sub-organization, you can start and stop services on the agents in the sub-organization. However, you cannot start and stop services on a Secure Agent that is in a shared Secure Agent group.
Each time you start and restart a service, the Secure Agent creates a new subdirectory for the service-related files. For example, if the Secure Agent uses version 64.0.38 of the Data Integration Server, the Secure Agent installation directory contains the following subdirectory:
The Secure Agent does not delete the .../64.0.38.1 directory.
Example
Your organization uses Data Integration and has licenses for Enterprise Data Catalog integration, file integration, and mass ingestion.
Your Secure Agent runs the following Secure Agent services:
•Data Integration Server
•EDC Search Agent
•File Integration Service
•Mass Ingestion
If you have issues with Enterprise Data Catalog search, you can stop the EDC Search Agent service while you perform troubleshooting. When you stop the EDC Search Agent service, you cannot perform data catalog discovery in Data Integration. However, jobs processed by the other services on this agent such as mappings, tasks, taskflows, and AS2 file transfers continue to run.
Guidelines for stopping and starting Secure Agent services
Use the following guidelines when you stop and start services on a Secure Agent:
•Use caution when you stop Secure Agent services because this can cause job failures.
When you stop a Secure Agent 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 and connector assignment for Secure Agent groups.
Stopping a Secure Agent service
You can stop a Secure Agent service that is in the "Up and Running" or "Error" state. Stopping a Secure Agent service stops all versions of the service that are running. After a service stops, you can start the latest version of the service.
Note: If you stop a Secure Agent service and then restart the Secure Agent, the service remains stopped until you start it.
1In Administrator, select Runtime Environments.
2On the Runtime Environments page, click the name of the Secure Agent.
Note: You might have to expand the Secure Agent group to see the list of Secure Agents within the group.
3Click the Details tab.
4In the Agent Service Start or Stop area, select the service that you want to stop.
5Click Stop.
The Secure Agent service stops, and Informatica Intelligent Cloud Services adds an entry in the audit log indicating that the service was stopped by a user.
Starting a Secure Agent service
You can start a Secure Agent service that is in the "Stopped" state. Starting a Secure Agent service starts the latest version of the service.
1In Administrator, select Runtime Environments.
2On the Runtime Environments page, click the name of the Secure Agent.
Note: You might have to expand the Secure Agent group to see the list of Secure Agents within the group.
3Click the Details tab.
4In the Agent Service Start or Stop area, select the service that you want to start.
5Click Start.
Informatica Intelligent Cloud Services attempts to start the Secure Agent service. After the service starts, the status changes to "Up and Running." If the Secure Agent service fails to start, check the audit log to find the cause of the error.