How to Restrict System Agent To One Managers Which is Already In agentparm.txt File?
search cancel

How to Restrict System Agent To One Managers Which is Already In agentparm.txt File?

book

Article ID: 49150

calendar_today

Updated On:

Products

CA Workload Automation AE - Business Agents (AutoSys) Workload Automation Agent CA Workload Automation AE - System Agent (AutoSys) CA Workload Automation DE - Business Agents (dSeries) CA Workload Automation DE - System Agent (dSeries)

Issue/Introduction

If you wish to stop new scheduling manager instances (AutoSys, dSeries, ESP, etc.) from registering with a System Agent the procedure is as follows.

Environment

Release: All Supported Versions
Component: CA System Agent

Resolution

  1. Modify the agentparm.txt file

  2. In the agentparm.txt file locate this parameter:

    communication.manager.dynamic.modifications.lock=

  3. If is set to "false" then any instance can register with the System Agent

  4. If set to "true" then dynamic registration will be disallowed

  5. Any changes made in agentparm.txt will require a restart of the System Agent to take effect

Additional Information

https://techdocs.broadcom.com/us/en/ca-enterprise-software/intelligent-automation/workload-automation-system-agent/12-0/troubleshooting/troubleshoot-ca-wa-system-agent-for-unix-linux-windows-iseries-or-hpe-integrity-nonstop.html

Powered by Wolken Software