Agents are responsible for running all Automate MFT tasks such as file transfers, processes, and workflow orchestration. They provide the flexibility to execute operations either on your own infrastructure (self-hosted agents) or in the cloud (Progress-hosted agents), allowing organizations to align deployment with their security, compliance, and operational requirements.

There are two main types of agents:
  • Self-Hosted Agents: Installed and operated on your servers or virtual machines, giving you full control over the execution environment.
  • Progress-Hosted Agents: Hosted and managed by Progress, requiring no local installation.

Agent pools ensure task execution continues even if an individual agent becomes unresponsive or loses connectivity. When this occurs, other available agents in the pool automatically assume the workload.

Agent Pools allow you to group multiple self-hosted agents to support distributed task execution, load balancing, and simplified task management. Instead of assigning a task to a specific agent, you can assign it to a pool. Automate MFT will automatically choose the most suitable available agent in that pool when the task runs.

Centralized management

Agents and agent pools are centrally managed, monitored, and assigned to tasks during task creation or editing. An agent or agent pool can be assigned to multiple tasks.

Agent assignment

When you create a task, you must select which agent or agent pool will execute it.

Run multiple agents on the same machine

Automate MFT supports running multiple agents on a single machine. This capability allows administrators to reuse a single host for multiple environments, for example, separate agents for EU and US regions, removing the requirement to provision additional virtual or physical machines.

Each agent instance must be created independently in the Agents library and installed separately on the target machine.

Note: This configuration is generally recommended for testing or other specialized scenarios. When using agent pools for availability and failover, install each agent on a separate server or virtual machine to achieve full redundancy.

Multiple agent installation considerations

To run multiple agents on the same machine:
  • Install each agent in a separate directory.
  • Use the corresponding installation script to register and run each agent independently.

Running as a service

When installing agents as services, each instance must use a unique service name.

You can specify a custom service name by setting the following environment variable before running the installation script: MFT_SERVICE_NAME=<unique_service_name>
  • This variable applies to both Windows and Linux installations.
  • The value must be unique per agent instance to allow multiple services to run on the same system.

Quick view

The Details panel appears on the right side of the interface when an agent or agent pool is selected from the list. It provides a concise summary of the agent or agent pool details and task usage information.