Difference between CommandExecute policy versus AutoSysCommandISponsorFilters.txt
Article ID: 126282
Updated On:
Products
EMBEDDED ENTITLEMENTS MGR
CA Workload Automation AE - Business Agents (AutoSys)
CA Workload Automation AE - Scheduler (AutoSys)
CA Workload Automation Agent
Issue/Introduction
What is the difference between CommandExecute policy in EEM versus usage of AutoSysCommandISponsorFilters.txt
Environment
Release: WAAGTA99000-11.4-Workload Automation-Agent AE-MSP
Component:
Component:
Resolution
The difference between the CommandExecute policy versus AutoSysCommandISponsorFilters.txt is that when you adapt the AutoSysCommandISponsorFilters.txt file that this counts for everyone.
When using CommandExecute policy you can restrict commands and also to certain users.
For example if you want to allow user 'user1' to execute 'autoflags -a' command and also 'autorep -J' but no other commands.
This can be done by specifying following resource in the CommandExecute policy.
Turn on the flag 'Treat resource names as regular expressions'.
If you specify
When using CommandExecute policy you can restrict commands and also to certain users.
For example if you want to allow user 'user1' to execute 'autoflags -a' command and also 'autorep -J' but no other commands.
This can be done by specifying following resource in the CommandExecute policy.
server/ACE/autoflags -a
server/ACE/autorep -J [^;]+$
Select 'Execute' as action'.server/ACE/autorep -J [^;]+$
Turn on the flag 'Treat resource names as regular expressions'.
If you specify
server/ACE/autorep [^;]+$
then all options of autorep are allowed.
Feedback
Powered by
