Page History
...
- Agents are assigned a Job in a Workflow by use their Agent Name.
- Agent Names frequently are specified from the host name for which the Agent is operated, such as
drx6834. Such practice should be reconsidered as it forces to modify Agent assignment of a Job when the Workflow is rolled out across environments. - Instead, during During registration with a Controller in addition to the Agent Name Agents can be assigned one or more Alias Names.
- It is good practice to use generic Alias Names, such as
accountingAgent, During rollout the Job's Agent assignment can remain unchanged provided that for each environment we find an Agent with the same Alias Name. - This includes that in a dev environment we might find fewer Agent instances than in a prod environment. Using more Alias Names for the same Agents in the dev environment maps to use of more Agents in the prod environment.
- It is good practice to use generic Alias Names, such as
...
Overview
Content Tools