The alertg application publishes OT-XML alerts and pushes them to a message queue. This functionality requires an alertg configuration file. e-Biz Impact provides a sample alertg configuration file (alertg.cfg) for reference, which you can use as a template to create a customize alertg configuration file.
Open the sample file x:\Sybase\ImpactServer-5_4\samples\alerts\alertg.cfg on Windows and ~/Sybase/ImpactServer-5_4/samples/alerts/alertg.cfg on UNIX, where “x” and “~” represent the drive, system, or directory where the e-Biz Impact server is installed.
Use the “Sample alertg configuration file” for reference.
The “keys” in alertg.cfg are
called “alert data” and represent the essential
information published in OT-XML alerts. The alert data
values for the various alerts generated by various e-Biz Impact entities,
for example, the SFM, the cluster, and the controller, are compiled
in the alert definition reference.
In the first key, PubType, specify the notification type. Choose Alert.
WARNING! The PubTypes Trap and Both are not currently supported.
Specify the ContextName (the
default value is OTI_Context)
and TransportName (the
default value is AlertsIn).
The value for ContextName must
correspond to a stanza in the nnsyreg.dat file
that uses the form OTContext.<ContextName>.
For this example, the stanza OTContext.OTI_Context must
exist locally or externally. For more information, see “Configuring alertd for OT-XML alerts”.
The value for TransportName must
also correspond to a stanza in the nnsyreg.dat file
that uses the form Transport.<TransportName>;
for example, Transport.AlertsIn.
Specify the remainder of the keys to configure information to publish as OT-XML alerts.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
