|
|
not logged in
|
|
Automate your operations and start saving immediately!
|
|
|
|
Integrating PageAlert and HP OpenView Operations for Windows
The PageAlert / OvOW integration is accomplished through the installation of a PageAlert
policy in OvOW. The PageAlert policy type is WMI and a PageAlert policy group is
created. The default rules for this policy are to forward major and critical messages,
regardless of application, to the PageAlert integration script.
The default installation directory for PageAlert Server or Client is C:\Program
Files\PageAlert. If PageAlert is installed in another directory, then some adjustments
to the paths shown in this document may need to be made.
After installing PageAlert, review the script file:
C:\Program Files\PageAlert\Etc\OvOW\InstallPageAlertPolicy.vbs
This script installs the policy in the policy group PageAlert, as well as the automatic
command (the integration script) that the policy utilizes. The PageAlert installation
directory is determined through the registry key:
\HKLM\Software\Nobix\PageAlert\InstallDir
After a successful installation of the policy, open the HP OvOW console, expand
the policy groups, select the PageAlert policy, and right-click on the policy and
deploy it to your node.
The integration script,
is run when OvOW forwards a message to PageAlert. This script supplies four text
values to the script notifyPA.vbs, which then calls the PageAlert server directly.
These text values are intended to trigger a notification. The four values are:
|
|
Text1 |
the value “HPOVOW” |
|
|
Text2 |
the value “matchval2” |
|
|
Text3 |
the value “matchval3” |
|
|
Other Msg |
the text of the message from OvOW |
Note that Other Msg is not used for notification event matching purposes
and does not appear on the Notification Master Entry dialog. We suggest that OvOW
forwarded messages match on the hostname and Text 1 values only. It is this
scenario that is described below when creating a Notification Master Entry.
The actual message from OvOW, known as Other Msg, may be passed along to
the notification device as the PageAlert variable {otherMsg}.
The hostname of the OvOW server is in the variable {triggerHost}.
These variables may be used when creating a Device Profile in PageAlert. See the
Device Profile Dialog in the PageAlert Configuration program. The Help button
on that dialog will give you the details.
Update the PageAlert.ini File
There is no requirement that the PageAlert Server be installed in the same machine
as the HP OvOW server. If the PageAlert Server is installed on a different machine,
then the PageAlert Client must be installed on the HP OvOW server.
Regardless of whether the PageAlert Server or Client software is installed on the
HP OvOW server, edit the file pagealert.ini, which resides in the PageAlert
installation directory. Ensure that the line PA_SERVER contains the hostname
or IP address value that matches the location of the PageAlert Server. Do not use
127.0.0.1 to resolve to localhost. The nofityPA.vbs script uses the pagealert.ini
file to determine which PageAlert Server to use.
The directory structure of the PageAlert Server and Client installations is the
same. Note that when the PageAlert Server is installed, the installation automatically
includes one PageAlert Client for use on that machine, and no separate activation
key is required for the Client software.
Creating a Notification Master Entry in PageAlert for OvOW
Start the PageAlert Configuration program. Navigate to the Notification Master tab
and click Add.
Create a new Notification Master entry that looks similar to Screen 1 below. The
fields From Hostname, Text 2 and Text 3 should each contain
a single asterisk. The field Text 1 should contain only the text value HPOVOW.
Select Must Match All Three Text Fields.
Change the Minutes Between Entry Activations to 1. This value is intended
to suppress duplicate or repetitive messages. You can change this later to a higher
number.
Associate the desired Device Profiles and then clickAdd.
Note: Ensure that there are no other matching Notification Master entries that are
above the OpenView entry that was just added. Pay special note to test entries that
may contain all asterisks and may match any incoming message.
The Message from OpenView is available through the use of the Device Profile message
variable {otherMsg}. The Device Profile dialog is not
shown here.
Screen 1 – Notification Master Entry Example
|
|
|
How It Works
The integration script eventually calls the notifyPA.vbs script. There are
four values passed to notifyPA.vbs, three of which are the Text 1
thru 3 values used to match a notification master pattern in PageAlert. The
fourth value is the message to be displayed on the device itself (you can also display
the first three text values on the device as well). notifyPA
is intended to be used as a command line interface. notifyPA
looks up the PageAlert Server’s hostname from the pagealert.ini file and then runs
the npage.exe program directly. npage.exe is the actual
program used to communicate with the PageAlert Server.
If you run npage.exe directly, then you will have to resolve the PageAlert
server machine’s hostname, as well as the installation directory, etc. notifyPA.vbs
is simply a wrapper script that isolates npage.exe for you. Make sure the
pagealert.ini file is up to date. pagealert.ini is used
to determine the hostname of the PageAlert Server. The registry isn’t used for this
value. The registry is used to determine the installation directory
of the PageAlert Server or Client software.
 Back to previous page
|
|
|
|
|
|