XYGATE Compliance PRO (XSW) Reference Manual

XYGATE
®
Compliance PRO
™
Reference Manual
Appendix B: The SWACL File
XYPRO Technology Corporation 239 Proprietary and Confidential
This example allows any userid or alias to connect to a NonStop server using the XSW
GUI and request a collection. Of course, Safeguard and/or XOS security on the
NonStop host software that constitutes the XSW application will ultimately limit who
can execute the collection software.
Example:
TASK COLLECTION ACL SEC.* TECH.*
In this example, any userid that is a member of the SEC or TECH groups can start the
collection, subject to Safeguard and X OS limits.
B5: NODE
The NODE keyword maps which nodes can be accessed through this node and where
the XSW software is located on that node. This keyword is repeated for each node that
this XSW connection can access.
Syntax:
NODE <nodename> <vol/subvol>
where <nodename> is the name of the node that XSW can collect information from
and <vol/subvol> is the volume and subvolume on that node where the XSW software
is installed.
Example: Contents of SWACL File
NODE \PROD1 $SEC.XYGATESW
NODE \PROD2 $SANDA.XYGATESW
NODE \DEV $WORK.XYGATESW
In this example, there are three nodes from which data will be collected. On \PROD1,
the XSW software is installed on $SEC.XYGATESW. On \PROD2, the XSW software is on
$SANDA.XYGATESW. On the third node, \DEV, the software is installed on
$WORK.XYGATESW.