CA Client Automation

supports the software delivery agents to move between scalability servers, connecting to the same domain manager. After collecting the outstanding job results, the records of SD agent on the previous scalability server are destroyed. As the targets do not change the domain manager, there is no need to move the job history.

A job is considered roaming as soon as the job has been ordered to scalability server A, and the software delivery (SD) agent registers through scalability server B.

The SD agent roams from scalability server A to scalability server B. The SD agent is automatically registered with scalability server A. A number of jobs have been set up to the agent and are staged in the file database on scalability server A. Then the agent is registered through scalability server B.

When scalability server B reports its new agent to its domain manager, the domain manager triggers the scalability server A. Scalability server A reports the job results for the agent, and the domain manager realizes that this agent has roamed to scalability server B. All jobs that have not yet executed are reset and scalability server B is triggered. Scalability server B picks up the reset jobs.

The software delivery function internally handles the name of the manager that receives the jobs, and ensures that the batch is not broken. The new SD manager does not pick up any job, unless the old manager reports the results or the administrator removes jobs, or timed out. During this time new jobs are not allowed to set up to the roaming agent.