How to restrict the use of Control-M/Agent utilities on Remote Hosts? - INCLUDES VIDEO
How to restrict the use of Control-M/Agent utilities on Remote Hosts?
Control-M/Agent for UNIX and Microsoft Windows
Control-M/Agent for UNIX and Microsoft Windows
Control-M/Agent for UNIX and Microsoft Windows
Control-M/Agent for UNIX and Microsoft Windows
Control-M/Agent for UNIX and Microsoft Windows
Control-M/Agent for UNIX and Microsoft Windows
How to restrict the use of Control-M/Agent utilities on Remote Hosts ?
Starting from Control-M/Agent 8.0.00, you can now invoke Control-M/Agent utilities on Remote Hosts.
Do the followings to enable the restriction of the utilities that allow to execute on Remote Host:
- Enabling the use of Control-M/Agent utilities on Remote Hosts by setting the value of UPLOAD_REMOTE_UTILS parameter to Y (default is N) - Improve performance by instructing the Control-M/Agent (RJX) to transfer utilities to Remote Hosts permanently. The utilities are transferred to the home directory of the job owner and are not deleted in order that they will be available for the next job and safe the time required to transfer all the utilities for each job invocation. Set the value of UPLOAD_REMOTE_UTILS_ONCE parameter to Y (default is N, if parameter is not included, needs to be added ) - The Control-M/Agent parameter 'REMOTE_UTILS_LIST' contains the list of Control-M/Agent utilities that can be invoked on Remote Hosts connected to the Control-M/Agent.
These parameters are located in CONFIG.dat file on Unix/Linux or HKEY_LOCAL_MACHINE\SOFTWARE\BMC Software\Control-M/Agent\CONFIG registry key on Windows.
Additional Information: - Before invoking the utility on Remote Host, the command is being passed to the Control-M/Agent from the Control-M Server. - Control-M Agent must be permitted to run the utility under 'AGPERMIT_UTILS' folder. Please reference KA#000128939 or "Authorizing Control-M/Server utilities for a Control-M/Agent" section at online documentation for more information.