Advanced ESM Administration Tasks¶
Disabling Windows Short Names to enable SASWORK Monitoring¶
If SASWORK is configured to point to a volume with short names enabled, and you wish to monitor SASWORK with ESM (recommended) you must change your SASWORK configuration to use a volume with short names disabled.
Determine the new location for SASWORK. This guide assumes a drive letter of E:
Query the short name status of drive E: by issuing the following command at a command prompt with elevated/Administrator privileges:
fsutil.exe 8dot3name query E:
C:\WINDOWS\system32>fsutil.exe 8dot3name query E: The volume state is: 0 (8dot3 name creation is enabled). The registry state is: 2 (Per volume setting - the default).
E:. If the status returns
8dot3 name creation is enabled on E:, issue the following command to disable it:
C:\WINDOWS\system32>fsutil 8dot3name set E: 1 Successfully disabled 8dot3name generation on E:
Now create a saswork directory (e.g
Now change the SAS Server configuration to set SASWORK to point to this location. It is recommended to change this setting in the Application Server root sasv9_usermods.cfg file. For example:add the following entry to this file:
Restart the SAS Object Spawners to pick up the new configuration
Start a new SAS Session and re-issue the saswork option query:
%put %sysfunc(getoption(work));If the change has taken effect, you should see output in the SAS log similar to the following:
Installing the ESM Agent as a systemd service on RHEL7¶
RHEL7 comes with
upstart from RHEL6. Systemd lets us configure control the ESM agent on machine startup and if the agent stops.
To configure the ESM agent as a
systemd service, create a file in
Remember to change the reference to ##ESMHOME## below to point to real install path (eg. /opt/esm/esm-agent).
[Unit] Description=ESM agent control After=network.target [Service] User=root ExecStart= ##ESMHOME##/bin/esm-agent-nonforking.sh start ExecStart= ##ESMHOME##/modules/esm-module-control.sh start Restart=on-failure Type=simple TimeoutStartSec=10 TimeoutStopSec=5 RestartSec=2 ExecStop= ##ESMHOME##/bin/esm-agent-nonforking.sh stop ExecStop= ##ESMHOME##/modules/esm-module-control.sh stop [Install] WantedBy=multi-user.target
After creating the file, you can run the following commands as root (or sudo):
systemctl daemon-reloadcommand to make systemd re-read the config
systemctl start esm-agentto have upstart run the agent for you
systemctl enable esm-agentto have the agent start as a service on every subsequent boot
systemctl status esm-agentto see the output of the last start