Workload Automation Agent not communicating with DE Server after hostname/IP address change

Document ID:  TEC1026912
Last Modified Date:  07/13/2017
{{active ? 'Hide' : 'Show'}} Technical Document Details


  • CA Workload Automation DE


  • CA Workload Automation DE:Release:11.3
  • CA Workload Automation DE:Release:11.3 SP1
  • CA Workload Automation DE:Release:11.3 SP2
  • CA Workload Automation DE:Release:11.3 SP3


  • CA Workload Automation System Agent:SYSAGD

We have a server running CA Workload Automation Agent. The Server hostname and IP address changed. We updated the agentparm.txt file and restarted the agent. However, the agent is still not communicating with DE Server. Is there any other configuration we need to change?

UNIX, Linux and Windows

If Agent's server hostname and IP address changed, you need to modify the agent's agentparm.txt file and agent definition in the Topology on the Desktop Client to reflect the change so that the agent and DE Server can communicate;

Agent's agentparm.txt file;

DE Desktop Client Topology Agent definition:
Port number

And, restart the agent for the change to take effect.

Please help us improve!

Will this information enable you to resolve your issue?

Please tell us what we can do better.

{{feedbackText.length ? feedbackText.length : '0'}}/255


Not what you were looking for?

Search Again >

Product Information

Support by Product >


Join a Community >