Sample alertd configuration file

The following sample is the alertd configuration file (alertd.cfg) supplied with e-Biz Impact and is located in x:\Sybase\ImpactServer-5_4\samples\alerts\ on Windows and in ~/Sybase/ImpactServer-5_4/Samples/alerts\ on UNIX, where “x” and “~” represent the install location of the e-Biz Impact server.

#

# Sample configuration file for alert handler

#   ims54alertd (and ims54alertdsvc on windows).

###################################################### The "Alerts" stanza is specific to ims54alertd.

#

# Default below indicates default values built into

#application (e.g. key can be omitted in cfg). 

#

# Verbose 

#     Use: Controls how much info is sent to

#           console/screen. FALSE=min, TRUE=max 

#     Default: FALSE

#

# Context #     Use: References an OT context stanza ID (see

           "OTContext.OTI_Context" stanza below). 

#     Default: OTI_Context

#

# In

#     Use: References the OT "input" transport stanza

#          ID (see "Transport.AlertsIn" stanza below).

#          This defines the alert message input

#          transport.

#     Default: AlertsIn

#

# PollRate 

#     Use: Time (in milliseconds) to pause between read

#          attempts again the "In" transport.

#          Not all OT drivers support blocking timeouts

#          (e.g. file driver does not, but IBM Websphere

#          MQ (formerly MQSeries) does, etc). If

#          blocking is supported, it is by far preferred

#          to polling. Use 0 to indicate blocking. If

#          blocking does not work, use a "reasonable"

#          polling interval such as 5 seconds. 

#     Default: INFINITE

#

# Log 

#     Use: References the OT "log" transport stanza ID

#          (see "Transport.AlertLog" stanza below)

#          where processed alerts msgs are logged.

#          Usage is optional - if Log is not specified

#          then processed alerts are not saved.

#     Default: none

#

# Error

#     Use: References the OT "error" transport stanza

#          ID (see "Transport.AlertError" stanza

#          below). Defines transport where

#          unprocessable alerts msgs are sent. 

#     Default: AlertError

#

# Command

#     Use: The name of script/binary. Can include path. 

#     Default: myalert

#

# IsScript 

#     Use: Indicates whether Command is a script or

#          binary. If TRUE, script must be processable

#          by cmd.exe (Windows) or /usr/bin/sh (Bourne

#          shell) on UNIX

#     Default: TRUE

#

# ExecDir

#     Use: Sets the working directory for the

#          script/binary. 

#     Default: .

#

# Visible (Windows Only) 

#     Use: Spawn a new console window to run

#          script/binary in. 

#     Default: FALSE

#

#####################################################Alerts

     Verbose = FALSE

     Context = OTI_Context

     In = AlertsIn

     PollRate = 3

     Log = AlertLog

     Error = AlertError

     Command = myalert

     IsScript = TRUE

     ExecDir = .

     Visible = TRUE

# Open Transport (OT) configuration can occur here or

# in nnsyreg.dat in the working directory or in the

# directory specified by the NNSY_ROOT environment

# variable. See sample OT configuration files

# nnsyreg_mqs.dat and nnsyreg_file.dat

# for example configurations for Websphere MQ and the

# OT file driver respectively.

Copyright © 2005. Sybase Inc. All rights reserved.

View this book as PDF