Secure Agent services are pluggable microservices that the Secure Agent uses for data processing. For example, the Secure Agent uses the Data Integration Server to run data integration jobs. Each Secure Agent service runs independently of the other services that run on the agent.
The independent services architecture provides the following benefits:
•The Secure Agent does not restart when you add a connector or package.
•Services are not impacted when another service restarts.
•Downtime during upgrades is minimized. The upgrade process installs a new version of the Secure Agent, updates connector packages, and applies configuration changes for the Data Integration Server . To minimize downtime, the old agent remains available and continues to run data integration jobs during the upgrade. The new version of the Secure Agent runs jobs that start after the upgrade process completes.
The following table describes the Secure Agent services that can run on an agent:
Secure Agent service
Description
Common Integration Components
Runs the shell scripts or batch commands in a Command Task step of a taskflow.
Data Integration Server
Runs data integration jobs such as mapping, task, and taskflow instances.
Each Secure Agent service has a unique set of configuration properties, such as Tomcat and Tomcat JRE settings. You might need to configure a service or change the service properties to optimize performance or if you are instructed to do so by Informatica Global Customer Support. You configure a Secure Agent service independently from other services that run on the agent.