AutoSys Workload Automation

  • Private Community
 View Only

  • 1.  CAWADE upgrade - Need recommendations on agent modification

    Posted May 15, 2020 03:00 PM
    We are currently planning to upgrade our CAWADE to 12.2 using the migration method , and the below set up is mentioned in docs to be done on all agent servers . 

    Is this set up required , if we provide the same manager ID for the new scheduler server  as well as use a DNS alias pointing the old server name to new migration server . Any suggestions please 

    Modify an Agent to Work with the New Server:
    Modify the following parameters to match the values for the new server:
    – communication.managerid
    – communication.manageraddress
    – communication.managerport

    ------------------------------
    Thanks,
    Ramesh.
    ------------------------------


  • 2.  RE: CAWADE upgrade - Need recommendations on agent modification

    Broadcom Employee
    Posted May 27, 2020 01:10 PM
    When the agent is added to the topology map, the server will contact the agent by default and register causing these entries to be retained by the agent. In other words, the entries do have to be there but dSeries will request the agent add them so you don't have to manually add them.

    ------------------------------
    Broadcom - CA Technologies
    ------------------------------

    Original Message


  • 3.  RE: CAWADE upgrade - Need recommendations on agent modification

    Posted May 27, 2020 01:19 PM
    Hi Daniel,

    Thanks for the response, but you mean to say that post using migration method no need to edit the old server name from agent paramater file . Will simply adding the agent name to topology in the new DE 12.2 will automatically establish the connection to all the existing agents.
    Original Message


  • 4.  RE: CAWADE upgrade - Need recommendations on agent modification
    Best Answer

    Broadcom Employee
    Posted May 27, 2020 01:40 PM
    Adding the agent to the topology map with "Remember Manager address changes between restarts" set to "true" (default), will cause dSeries to connect to the agent and have it retain the manager connect data in the agentparm.txt file. Something to consider though is when you decommission the old server, the agentparm.txt files that contained the old server info should be cleaned up. If the old information is retained you may find the agent trying to contact the old manager wasting resources for something that will never be there.

    ------------------------------
    Broadcom - CA Technologies
    ------------------------------

    Original Message