Support for the e-Biz Impact Open Transport-XML alert consists three applications:
ims54alertg (UNIX, Windows)
ims54alertd (UNIX, Windows)
ims54alertdsvc ( Windows only)
To simulate and generate OT-XML alerts, e-Biz Impact uses the ims54cluster binary and the ims54alertg binary.
Both ims54cluster and ims54alertg can publish OT-XML alerts. After an alert is published, an external handler is required to manage the alert, and take some user-defined action such as issuing e-mail or logging the event. The external handler used depends on the type of alert published.
To use the alert information from ims54cluster or ims54alertg, an OT-XML message on the alert transport, such as an item in the PENDING queue, must be turned into a user-defined action using the utility program.
ims54alertd reads alert messages from the alert transport, such as a queue or file device, and invokes a user-maintained shell script or binary. Use ims54alertdsvc to run as a Windows service. On UNIX systems, run ims54alertd either in the foreground or in the background, for example, as a daemon.
Before invoking the user script or binary, ims54alertd places the relevant information from the alert message in environment variables. While the user script or binary is executing, you can query the environment variables to control the execution flow in a script or binary.After successfully processing the alert message from the transport device using the script or binary, ims54alertd can, optionally, copy the alert message to another transport device, such as a log device, for auditing or history purposes. Alert messages that cannot be processed are moved to an error transport device.
To configure and implement alert notification and response, see Chapter 5, “Configuring and Using Alerts.”
To view possible alert messages, see Appendix A, “Alert IDs.”
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
