Runtime Environments

Back Next

Stopping and starting services on a Secure Agent

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:

<Secure Agent installation directory>/apps/Data_Integration_Server/64.0.38.1

When you stop and restart the Data Integration Server, the Secure Agent creates the following directory:

<Secure Agent installation directory>/apps/Data_Integration_Server/64.0.38.2

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.

Secure Agents

Guidelines for stopping and starting Secure Agent services

Stopping a Secure Agent service

Starting a Secure Agent service

Download Guide

Watch

Comments

Communities

Knowledge Base

Success Portal