How do I integrate AppManager with Vytek Wireless' Telalert? (NETIQKB15883)

  • 7715883
  • 02-Feb-2007
  • 07-Jan-2011


NetIQ AppManager 6.x
NetIQ AppManager 7.0.x


How do I integrate AppManager with Vytek Wireless' Telalert?


Use the Action_Page Knowledge Script to send a paging call with AppManager event information to one or more recipients. Paging systems and target recipients (individuals or groups) are defined in the \winnt\netiqpage.ini file. Before using this Knowledge Script, review and edit the netiqpage.ini file to reflect the groups, phone numbers, and other parameters appropriate for your specific paging system.

By default, the paging message is the detail message associated with the event that raised the page. To override the default message, enter a custom message in the Message property.

Because each paging system has its own command line syntax or API requirements, you need to define some information about the paging system(s) you are using in the netiqpage.ini file before using this Knowledge Script. The netiqpage.ini file specifies:

  • Path to the paging server interface (for example, the path to the command line program used to send the page).
  • Command line parameters or API syntax used to construct the page (for example, a specific paging interface may require a pager number, sender ID, or start time as command line arguments).
  • Target group or profile names that contain the rules for contacting groups or individuals (for example, some paging systems allow an administrator to set up templates that define contact flow to control when specific groups can be reached via pager).

This information is defined in the netiqpage.ini file in two sections:

  • The [system] section, which defines the paging system, the path to the interface, and the command line parameters to be passed in from the [group_name] section depending on the Name of the group to page you enter in the Knowledge Script.
  • The [group_name] sections, which define the details for target groups.

The following in an example of a netiqpage.ini file with definitions for three paging systems and two target groups, QA and Sales:

 ;;   ;; sample netiqpage.ini file   ;;    [system]  ;; For the command line syntax for these paging systems:   ;; first %s maps to the target_name [target]  ;; second %s maps additional parameters [param]  ;; third %s is the message passed in from the Knowledge Script   ;;   attention=c:\AttnClient\attn -t %s %s %s   telalert=c:\usr\telalert\telalertc -c %s %s -m %s  <.
hiplink=c:\hiplink\cms\hlclp -r:%s %s -m:'%s' ;; msg in quotes [QA] pageco1=hiplink target1=M param1= start_time1=00/00/00 00:00:00 stop_time1=00/00/00 23:59:59 [Sales] pageco1=telalert target1=Pager param1= -n 4083031937 start_time1=00/00/00 00:00:00 stop_time1=00/00/00 23:59:59 pageco2=telalert target2=Pager param2= -n 4083031937 start_time2=5/12/98 00:00:00 stop_time2=6/30/98 00:00:00

The Action_Page Knowledge Script uses the information defined in this file and the Action properties entered to construct the required command line to send the page. For example, if you set the Name of the group to page to Sales, AppManager will send a page to the Sales pager number (4083031937) using the telalert paging system.

Defining a paging schedule

Within the netiqpaqe.ini file, you can set a paging start time and end time for each person or group. This allows you to define specific periods when the individuals in a group can be paged. For example, if you have a TechSupport group with two employees who can be paged any day of the week between the hours of midnight and 8:00 a.m. and one employee who can be paged at any hour during specific dates, you might create entries similar to the following in the netiqpaqe.ini file:

 [TechSupport]      pageco1=telalert	       target1=Blake                    // Blake can be paged       param1= -n 4083031937            // between 12:00 a.m.       start_time1=00/00/00 24:00:00    // and 8:00 a.m.       stop_time1=00/00/00 08:00:00     // (no start date or                                        // end date)       pageco2=telalert       target2=Andy                   // Andy has the same        param2= -n 4084551037          // schedule as Blake       start_time2=00/00/00 24:00:00       stop_time2=00/00/00 08:00:00        pageco3=telalert       target3=Alex                   // Alex can be paged any       param3= -n 4156542200          // hour from midnight       start_time3=7/12/98 00:00:00   // July 12, 1998 until       stop_time3=7/30/98 10:30:00    // 10:30a.m. July 30  

Both the start_time and stop_time parameters consist of two parts-the date and time. If you don't want to specify a start date or an end date, set the first part of the appropriate parameter to 00/00/00 (as illustrated with Blake and Andy in the example). If you don't want to specify a start time or an end time, set the second part of the appropriate parameter to 00:00:00 (as illustrated with Alex in the example).

Note   You cannot use the start_time and stop_time parameters to set up weekly scheduling. You can only define scheduling profiles or templates using parameters associated with your paging system. For example, if your paging system supports a -s schedule_profile command line parameter, you can include this in the netiqpaqe.ini file as you do other parameters. For example:

 [system]  page_app=c:\PageSysClient\sendpage -t %s -n %s %s -m %s   .
[WeekdayCrew] pageco1=page_app target1=scott param1= -n 4083031937 -s weekday_profile

Additional Information

Formerly known as NETIQKB15883