This document describes how to deploy custom scripts to be used for Actions and/or MIB Extensions to managed SystemEDGE agents.
How to Deploy Scripts for Actions and Extension to managed SystemEDGE Agents?
Virtual Assurance for IM with Managed SystemEDGE agents
- On the Domain Server machine create the following directories:
- Add any scripts and binaries required be deployed directly into the "windows" or "unix" directories accordingly - note that sub-directories beneath these are ignored.
Use the "sysedge_scripts\windows" directory for any scripts to be deployed to Windows hosts, and used the "sysedge_scripts\unix" directory for any scripts to be deployed to UNIX/Linux hosts.
- Recycle the "CA SM Domain Server" service.
- Once the Domain server is running again, recycle the "CA SM Distribution Server" on all Distribution servers.
Note: Recycling of these services will be required anytime any additions or updates are made to the sysedge_scripts directories.
Whenever a policy is pushed to an agent the contents of either sysedge_scripts\windows or sysedge_scripts\unix (depending on the target platform) will also be pushed to the agent. The pushed scripts will be created in the following directory on the target agent host:
Windows - <sysedge install dir>\bin\managedscripts\
Example: C:\Program Files\CA\SystemEDGE\bin\managedscripts\
UNIX - <sysedge install dir>/bin/managedscripts/
When creating policies that need to use these scripts, be sure to include the proper full path in the Action or MIB Extension configuration.