Execution Agent is a secure connection between Serviceaide Enterprise Service Automation (ESA) and the integrated Application. The Agent is used to deploy apps and execute the discrete operations on the Mule runtime on the target system.
A SaaS implementation of Serviceaide Automation ESA comes with an in-built Cloud Agent that can be used to connect to the apps that are available over the internet. However, the systems that are internal to the organization and do not have public connectivity cannot be accessed via the default Cloud Agent. In such cases, a tenant-specific Execution Agent is deployed. This is called a Hybrid Implementation where the Automation Server is available on Cloud (as a SaaS implementation) and the Automation Execution Agent is configured on the customer's On-premise server or Private cloud. The On-Premise Automation Execution Agent facilitates integration with systems that are available only within the Customer network and cannot be accessed over the internet.
...
Before implementing the Automation Execution Agent on-premise, the tenant administrator should create an Agent in the Serviceaide Automation portal. The This generates agent details such as Agent External ID and Secret Key, which are configured in the properties files to enable the Agent.
...
Navigate to the Execution Agents workspace on the Serviceaide Automation portal.
All the configured Agents and their current status are listed on the page.
Click on Create agent.
Add the following details:
Add the Agent Name and Description.
Add the Server Address where the Execution Agent is implemented.
Provide the Port number used to establish the connection.
Click on Create.
The Execution agent is created. A pop-up appears with Agent Access Key. The Key is used in the agent deployment process. Copy and keep the key on the clipboard or on a text editor to be used later.
...
Refer to the ESA On-premise Agent v2.0.0 Runbook for detailed instructions on implementing the Execution Agent on the On-Premise servercustomer’s environment.
Once the Execution Agent is deployed on the server with the above details, the Execution Agent is moved to the ‘Running’ state and can now be used for operations execution.
...