4.0.0 HP Polyserve Matrix Server Administration Guide (T5392-96052, March 2010)

• Event details, formatted in XML, are passed to the standard input (stdin) of the
script or program.
Script requirements
For the script to work properly, the following requirements must be met:
• The script or program must be accessible from each node in the matrix. It is re-
commended that an identical copy of the script or program be placed on local
storage on each node to ensure that it will always be available.
• The script must be able to be executed on each node. For example, if perl is used,
the appropriate interpreter must be installed on each node and the appropriate
extension must be associated with the interpreter on each node.
• The script or program must either use full path names to any external commands
or set a PATH variable appropriate to each language. (A system PATH variable
is not passed to the script.)
Script variables
Variables are accessed in a manner consistent with the language. For example, the
VAR variable is accessed in Batch as %VAR%; Powershell uses $env:VAR; C uses
getenv("VAR"); perl uses $ENV{VAR}; and so on.
The following variables can be set for an event. (All of the variables are not required
for each event).
MxS-event-severity-nameMxS-event-cluster-description
MxS-event-categoryMxS-event-cluster-id
MxS-event-sourceMxS-event-epoch
MxS-event-event-timeMxS-event-serial
MxS-event-locationMxS-event-event-id
MxS-event-process-idMxS-event-catalog-version
MxS-event-messageMxS-event-severity
MxS-event-user
Following is an example of the input XML (as with the above, not all elements are
required for each event):
HP PolyServe Matrix Server administration guide 177