100FF51A MyAMC - fa-messeng100FF51A - myAMC - FA-Messenger - Installation - and - Administration - Pdfer - Installation and Administration

FA Suite V9.
0
myAMC.FA-Messenger
myAMC.FA-Messenger V9.0
Stand: 05.04.2012
General section
Page 1 of 148
myAMC.Messenger
Contents
Contents ...........................................................................................................................................................3
1 Preface ......................................................................................................................................................5
1.1
Introduction ........................................................................................................................................5
1.2
Target group .......................................................................................................................................5
1.3
Summary of contents .........................................................................................................................5
1.4
Notational conventions .......................................................................................................................5
1.5
Features in this version ......................................................................................................................6
1.6
Basic and extended Versions of Messenger/Robot ..........................................................................6
2 Getting Started ..........................................................................................................................................9
2.1
Introduction ........................................................................................................................................9
2.2
Requirements ...................................................................................................................................10
2.3
Installation ........................................................................................................................................11
2.3.1
Install myAMC.Messenger on the management host ...............................................................11
2.3.2
Start the myAMC.Messenger Server ........................................................................................15
2.3.3
myAMC.Messenger configuration.............................................................................................15
2.4
Examples .........................................................................................................................................16
2.4.1
Forwarding of messages in a FlexFrame environment .........................................................16
2.4.2
Alerting with myAMC.Messenger and myAMC.Printer .............................................................17
2.4.3
Alerting with myAMC.Messenger and myAMC.Network ..........................................................17
3 Introduction ..............................................................................................................................................19
3.1
Architecture ......................................................................................................................................19
3.1.1
Components..............................................................................................................................20
3.1.2
Operating modes ......................................................................................................................20
3.1.3
Input interfaces .........................................................................................................................21
3.2
Message History ..............................................................................................................................22
3.3
Filters ...............................................................................................................................................23
3.4
Reactions .........................................................................................................................................25
3.4.1
Reaction types ..........................................................................................................................25
3.4.2
Receiver groups ........................................................................................................................26
3.5
Output interface................................................................................................................................27
3.6
Master/Slave Messenger .................................................................................................................27
3.7
Repository ........................................................................................................................................28
3.7.1
Fault-resistant Message Repository .........................................................................................28
4 myAMC.Messenger Usage .....................................................................................................................29
4.1
Introduction ......................................................................................................................................29
4.2
Examples .........................................................................................................................................30
4.2.1
Example: Input formulas ...........................................................................................................30
4.2.2
Example: Receiver types ..........................................................................................................33
4.2.3
Example: Receiver Groups .......................................................................................................53
4.2.4
Example: Filter ..........................................................................................................................55
4.2.5
Example: Output .......................................................................................................................67
4.3
Funtional description ........................................................................................................................70
4.3.1
Input interfaces .........................................................................................................................70
4.3.2
Message structure ....................................................................................................................71
4.3.3
Filter Learn mode ......................................................................................................................71
4.3.4
Dynamic processing .................................................................................................................71
4.3.5
Message group .........................................................................................................................72
4.3.6
Log File .....................................................................................................................................72
5 myAMC.Messenger: Configuration .........................................................................................................73
5.1
Introduction ......................................................................................................................................73
5.2
Functional description ......................................................................................................................74
5.2.1
Program handling .....................................................................................................................74
5.2.2
Messenger ................................................................................................................................82
5.3
Master-Slave Repository ................................................................................................................142
6 Troubleshooting.....................................................................................................................................145
General section
Page 3 of 148
Stand: 05.04.2012
6.1
Debugging ..................................................................................................................................... 145
6.1.1
Introduction ............................................................................................................................ 145
6.1.2
myAMC.Messenger Service .................................................................................................. 145
Index ............................................................................................................................................................ 146
Figures ......................................................................................................................................................... 147
Stand: 05.04.2012
General section
Page 4 of 148
1 Preface
1.1 Introduction
myAMC.Messenger/Robot is an enterprise solution for the distributed management of
heterogenous applications and systems.
myAMC.Messenger receives events and alerts from applications, network components,
printers, storage systems and other managements systems. In response to incoming events
there is a wide range of automated or manual reactions possible.
myAMC.Messenger is a general component of myAMC to receive and distribute alarms and
events. This component is the central point for analysis, benchmarking, visualization and
forwarding alerts. Alerting and forwarding can happen as SNMP-trap, as file or email..
myAMC.Messenger includes an event viewer, which can be used to monitor all incoming
alerts. Additionally, the graphical configuration tool allows fine-grained control over filters,
reactions and predefined rulesets to handle incoming events and alerts.
myAMC.Robot is an addon component for the myAMC.Messenger for IT Automation. The
myAMC.Robot component has an own manual in addition to the myAMC.Messenger manual.
The interfaces and APIs exposed by myAMC allow other management products to integrate
and to connect with myAMC management solutions.
1.2 Target group

This manual describes the components and functions of myAMC.Messenger.
It is intended for all users of myAMC.Messenger as well as for administrators who wish to
integrate this application into an Enterprise IT Management System.
1.3 Summary of contents

This document describes installation, configuration and handling of myAMC.Messenger as well
as additional information for usage in a Fujitsu FlexFrame environment.
1.4 Notational conventions

To highlight important items in the text, the following conventions are used in this manual:
Italics
Italics are used for the names of files and windows, parameter descriptions, menu titles, and
entries as well as for commands and variables in word-wrapping texts.
<pointed brackets>
Entries between pointed brackets stand for variables, to which values are to be assigned.
Stand: 05.04.2012
General section
Page 5 of 148
Preface
1.5 Features in this version

The following list gives an overview of the powerful features. A comprehensive description can
be found in the following chapters.
myAMC.Messenger
An event and message management system
Easy configuration and parametrization
Priority-controlled alerts
Definition of alert groups and escalation level
Easy integration with other myAMC components
Reduces the costs of the IT operation
Information via email, SNMP Trap, HTTP webservices or execution of arbitrary

external programs
API to connect to other management products
Master/Slave Repository
Master/Slaver Mesenger Service
Message History as Receivertype
1.6 Basic and extended Versions of Messenger/Robot

myAMC.Messenger comes in three versions, Basic and Expert. myAMC.Messenger Expert
myAMC.Messenger/Robot. The use of the expert and robot funcitionality needs extended
licenses.
The main differences between myAMC.Messenger Basic and Expert are listed below:
myAMC.Messenger Basic
Reception of SNMP traps from myAMC applications and some other pre-defined
components like network devices
Simple, unfiltered forwarding of all incoming messages to a single email address and
SNMP trap destination
Message history can be browsed in Message View of the Config Viewer or any
myAMC GUI.
myAMC.Messenger Expert
All features of myAMC.Messenger Basic
Fine-grained filtering using Standard and Precision Filters
Creation of arbitrary receivers and receiver groups
Time-based forwarding of messages to selected receivers and receiver groups
Stand: 05.04.2012
General section
Page 6 of 148
Getting Started
Creation of customized formulas to parse incoming SNMP traps or email messages
myAMC.Messenger/ Robot
All features of myAMC.Messenger Basic and Expert
Taskautomation
Reaction Tasks
Stand: 05.04.2012
General section
Page 7 of 148
2 Getting Started
2.1 Introduction
This chapter describes how to start your Enterprise IT application management with
myAMC.Messenger in some easy steps from installation to using the myAMC.Messenger.
This chapter does NOT describe all capabilities of myAMC.Messenger. This will be done in
following chapters.
Stand: 05.04.2012
General section
Page 9 of 148
Getting Started
2.2 Requirements
myAMC.Messenger runs on both Microsoft Windows and Linux platforms.
Requirements for Microsoft Windows
Microsoft SQL Server 2000 or newer or MySQL 4.1 or newer
ODBC drivers for Microsoft SQL Server or MySQL
Java JRE 1.4.2 or newer
Requirements for Linux
Novell SLES8 or newer
MySQL server 4.1 or newer
MySQL ODBC driver 3.5.1 or newer
unixODBC 2.2.2 or newer
Java JRE 1.4.2 or newer
Stand: 05.04.2012
General section
Page 10 of 148
Getting Started
2.3 Installation
2.3.1
Install myAMC.Messenger on the management host
2.3.1.1 Creating the database on an remote Server

Note: This step is only necessary if you dont want to use a local MySQL database server.
Run the myAMC Setup Manager located in your CD Drive as SetupMgr.exe. Proceed to the
component selection and select only SQL Scriptfiles. If you already have installed myAMC
components the installation location is already set, otherwise you can select the folder where
your want to install the myAMC.Messenger. In both cases you will find the script
CreateAmcMsg.sql in <BASEDIR>\repository\Create
<BASEDIR> is the folder of your myAMC.Messenger installation.
If you use Linux just copy the sql script from the following folder of the installation CD:
/<path to cd>/Linux/myAMC.Messenger and choose the sql script for your database.
Running the script for MySQL Server

You can execute the script by typing the following command in the shell:
shell> mysql u<user> p<password> db_name < /source/to/CreateAmcMsg.sql
Or you can type it directly into mysql by typing this:
mysql > source /path/to/CreateAmcMsg.sql
Note: Please use the MySQL Server version 4.1
Running the Script for MS SQL Server
Open the script with the SQL Query Analyzer and press F5 to start the script.
Stand: 05.04.2012
General section
Page 11 of 148
Getting Started
2.3.1.2 Installation on Windows

By default the installation of the myAMC.Messenger uses a local MS SQL Server as repository
but you can also use MySQL.
Select myAMC.Messenger in the myAMC setup from the myAMC-CD, start the installation
program by clicking the green arrow and the component will be installed.
Follow the instructions specified below:
Start the myAMC.Messenger setup
Enter the MS SQL Server password

If you use a remote database leave this field blank and accept the warnings.
Choose the components you want to install
Follow the instructions on the screen
You will be asked to start the configuration tool
At the end of the installation the myAMC.Messenger Server will be started.
2.3.1.2.1 Installation of myODBC on an Windows Host

Note: This step is only necessary if you using MySQL.
Unzip myodbc-3.51.14-nt.zip and start Setup.exe (you can also get the latest myODBC
driver from www.mysql.com)
Open the ODBC Administrator from the Windows Control Panel
Press <add> in the tab System DSN
Choose MySQL driver
As Windows DSN name use AMCMSG_V10
Under MySQL, enter the IP address or hostname of the MySQL server into the host field
The database name is messenger
2.3.1.2.2 Installation of MySQL GUI on an Windows Host

Note: This step is only necessary if you want to execute SQL statements.
Unzip MySQLgui-win32-static-1.7.5-2.zip
Copy the created folder to C:\Program files\MySQL GUI (or another folder)
Create start menu entry respectivly create an shortcut of MySQLgui.exe
Start, and press the Options button
On tab Server:
Host name:
Default database:
On tab Client:
User name:
Host name or IP address of the MySQL server

messenger
root
Press Save to permanently store the configuration
Stand: 05.04.2012
General section
Page 12 of 148
Getting Started
2.3.1.3 Installation on Linux

2.3.1.3.1 Creating a myAMC.Messenger database
Install the MySQL database server and client software:
su root
rpm -i MySQL-server-4.1.13-0.i386.rpm
rpm -i MySQL-client-4.1.13-0.i386.rpm
In /etc/rc.config you have to set the variable START_MYSQL=<yes> .

For starting MySQL directly you have to call '/etc/init.d/mysql' with the parameter start.
Set permission for user root:
su root
cd/usr/bin
mysql
grant all on *.* to <user>@<Host> identified by <password>;

for example: grant all on *.* to root@111.111.111.111 identified by "3pxcf6_1";
flush privileges;
quit
In the future and with root as database user you have to type in mysql -u root p instead of
<mysql>. You will be asked for the password (as an alternative you can use
/usr/bin/mysqladmin u root p password <new password> )
mysql -u <user> -p < <sqlscript>

for example: mysql -u root -p < ./CreateAmcMsgmySQL.sql
Warning: This command will delete an existing messenger database!
2.3.1.3.2 Installation of myODBC on Linux
su root
rpm i MySQL-shared-compat-4.0.13-0.i386.rpm
rpm i MyODBC-3.51.14-1.i386.rpm
2.3.1.3.3 Installation of unixODBC on Linux
su root
rpm i unixODBC-2.2.2-94.i386.rpm
Please execute /sbin/ldconfig, so that myAMCMessenger can find the required shjared
libraries.
General section
Page 13 of 148
Stand: 05.04.2012
Getting Started
2.3.1.3.4 Installation of the Messenger Server

su root
rpm i myAmcMessenger-server-*.rpm
Execute /etc/init.d/myAMC.MessengerSrv connect <user> <password>. User and password

have to be the same as you used for the GRANT in MySQL (see above). If the Messenger
Server should have remote access to the MySQL database, you have to change server
entry of section [AMCMSG_V10] of /etc/odbc.ini and /root/.odbc.ini.
Start Messenger by executing /etc/init.d/myAMC.MessengerSrv start
Ensure that Messnger is running by executing ps ef | grep i amcmsgsrv
If the Messenger Server is not running, you have to check the Messenger log file which you
will find in /opt/myAMC/Messenger/log/ . There are four main reasons which have to be
considered:
User and password wrong. Solution: /etc/init.d/myAMC.MessengerSrv connect <user>
<password>.
The name of the myODBC driver slightly differs, because you installed a different version of
it. In this case you have to correct the entry Driver in the files /etc/odbc.ini and
/root/.odbc.ini.
The SNMP port (default: 162) is blocked. In this case you either have to quit the program
blocking the port ( netstat -a -p udp ), or you have to configure the Messenger so that it
does not use the default SNMP port. As an alternative you can switch to another port. The
SQL command update CNF_CONFIGGLOBAL set STRINGS='-1' where TYPES=
'SNMPRCVPORT' and APPLICATION=9 switches off the SNMP port. To use another port,
replace STRINGS=-1 with STRINGS=8162 in the statement above.
Stand: 05.04.2012
General section
Page 14 of 148
Getting Started
2.3.2
Start the myAMC.Messenger Server
Start the myAMC.Messenger Server via Service menu

The product can be started as all other services by the Service Control Manager:
Windows
Start Menu Settings Control Panel Administrative Tools Services
Linux
/etc/init.d/myAMC.MessengerSrv start
2.3.3
myAMC.Messenger configuration
The myAMC.Messenger configuration can be started via
Windows
Start Menu Programs Siemens myAMC WebGui FaConfigGui
Linux
/opt/myAMC/FA_ConfigGui/configgui.sh
Stand: 05.04.2012
General section
Page 15 of 148
Getting Started
2.4 Examples
2.4.1
Forwarding of messages in a FlexFrame environment

Task
Configuring myAMC.Messenger Basic so that all messages in a FlexFrame
environment are forwarded both to a central management station via SNMP traps as
well as sending email messages to an administrator.
Procedure
1. Set up outgoing email functionality by configuring MailServer and MailSender in the
FlexFrame / Basic forwarding menu.
2. Enter the administrators email address in the field MailReceiver of the FlexFrame /
Basic forwarding menu.
3. Enter hostname or IP address of your external management console in the fields
TrapTarget and TrapCommunity of the FlexFrame / Basic forwarding menu.
Result
Whenever myAMC.Messenger receives a message, it is automatically forwarded to your
administors email address and to the central management station. Additionally, all
messages can be browsed in the MessageView of the myAMC.ConfigViewer or any
other myAMC GUI.
Stand: 05.04.2012
General section
Page 16 of 148
Getting Started
2.4.2
Alerting with myAMC.Messenger and myAMC.Printer

Task
Sending an email to a person named admin if a printer goes offline or paper is empty. If
toner cartridge is empty the admin should get a mail and in addition a person called
service should get an email too.
Procedure
4. Set <MailServer>, <MailServerPort> and <MailReceiverPort>, <MailSender> in the
Messenger / Messages / Mail Settings menu.
5. Create two new receivers. (Admin, Service) Therefore press the Add button at the
Messenger / Targets / Message Receivers menu.
6. Select each of the receivers and press the Physical receivers button. Now select the
Physical Receivers by pressing the Add button.
7. Select the Physical Receiver type Email. In the Address field there should be placed
the email address of the according receiver.
8. Create two new groups. (AdminGroup, ServiceGroup). Therefore press the Add
button of the Messenger / Targets / Receiver Groups page.
9. The new receivers have to be assigned to the new groups. Therefore select a
Receivers Group and press Timed receivers. Choose the receiver which you will
add to the group and press the Save button.
10. Last but not least the different reactions have to be specified. Press the Add button
in the Messenger / Filter & Reactions / Reactions dialog.
11. printer is offline therefore select Application==myAMC.Printer, set the tick
ShortMessage in the Message contens menu and fill in the textfield printer is offline.
The receiver group has to be changed into one of the new groups (AdminGroup)
created above.
12. paper is empty therefore select Application==myAMC.Printer, set the tick
ShortMessage in the Message contens menu and fill in the textfield paper is empty.
The ReceiverGroup in the Message source menu has to be changed to one of the
new groups (AdminGroup) created above.
13. toner cartridge is empty therefore select Application==myAMC.Printer, set the tick
ShortMessage in the Message contens menu and fill in the textfiled toner cartrige is
empty. The ReceiverGroup in the Message source menu has to be changed to one
of the new groups (AdminGroup) created above.
14. toner cartridge is empty not only the AdminGroup but also the ServiceGroup should
be notified. So create a new reaction fill in the same parameters as above but now
the receiver group should be ServiceGroup.
Result
If printer is offline or paper is empty a person (Admin) will get an email. If toner cartrige
is empty a person (Admin) and also a person (Service) will get an email
2.4.3
Alerting with myAMC.Messenger and myAMC.Network

Task
Stand: 05.04.2012
General section
Page 17 of 148
Getting Started
Sending an email and a SMS to a network admin and an admin for a SAP R/3 system if
the interface of the SAP applicationserver is not available.
Procedure
1. Set MailServer, MailServerPort and MailReceiverPort, MailSender in the Messenger
/ Messages / Mail Settings menu.
2. Set in the Messenger / Messages / Pager Settings menu the Use Pagers hook and
select a modem.
3. Create two new receivers. (Admin, NetAdmin) Therefore press the Add button on
the Messenger / Targets / Message receiver page.
4. Select each of the receivers and press the Physical receivers button. Now select the
Physical Receivers by pressing the button Add button.
5. Select The Physical Receiver Type Email. In the address field shold be placed the
email address of the according receiver.
6. Select The Physical Receiver Syub type Pager and the correct Pager Center and fill
in the Address field the mobile number you want send a SMS.
7. Create a group. (NetGroup) Therefore press the Add button in the Messenger /
Targets / Receiver Groups page.
8. The new receivers have to be assigned to the new groups. Therefore select a
Receivers Group and press the Timed receivers button. Press the Add button and
choose the receiver which you will add to the group and press the Save button.
9. Last but not least the reaction has to be specified. Press the Add button in the
Messenger / Filter & Recations / Reactions dialog. Set the tick Host and fill in the
textfield the <hostname>.Then select Application==myAMC.Net, set the tick
ShortMessage in the Message contens menu and fill in the textfield interface not
available. The ReceiverGroup in the Message source menu has to be changed to
the new group (NetGroup) created above.
Result
If the network interface of the SAP applicationserver host isn't available two persons
(Admin, NetAdmin) will get an email and a SMS.
Note: SMS works only with a myAMC.Messenger running on Windows.
Stand: 05.04.2012
General section
Page 18 of 148
3 Introduction
3.1 Architecture
myAMC.Messenger is the component of the myAMC application management center
responsible for the management of alerts, events und reactions. This chapter tells you how this
component can be integrated into an enterprise management solution.
myAMC.Messenger is a modular component which consists of the following components:
Messenger Service
Graphical configuration tool
Repository
Message viewer integrated with myAMC and FlexFrame graphical user interface
Enterprise
event console
myAMC.Messenger
myAMC.MessageViewer
Email, SNMP Trap, External programs
myAMC.Messenger
Application-specific messages, alerts, events
Server, Network,
Storage
myAMC
FA Agents
Master
Repository
Slave
Repository
myAMC
LogAgent
Log
files
Figure 1
myAMC.Messenger: Structure
Stand: 05.04.2012
General section
Page 19 of 148
myAMC.Messenger: Configuration
3.1.1
Components
3.1.1.1 myAMC.Messenger Server

The service myAMC.Messenger Server is one of the core services of the myAMC.Messenger
solution. It receives alerts over the SNMP trap or database interface, filters it and dispatches it
according to user defined rules. MyAMC.Messenger is started over the system control panel
resp. the run level script. Der myAMC. Messenger Server verbindet sich ber eine ODBC
Schnittstelle mit seinem Repository.
Processing logic, input interface and output component are integrated in the Messenger
service daemon. It can be configured to run stand alone on a separate machine if necessary.
3.1.1.2 myAMC.Messenger GUI

The myAMC Messenger has a GUI component to configure the myAMC.Messenger
Parameters. The viewing of the Events can be done with FA_WebGUI, or with a version
compatible myAMC.GUI
3.1.1.3 myAM.Messenger Repository
The myAMC.Messenger Repository is he database with the configuration and the eventdata.
The myAMC.Messenger Repository can be realiced as MS-SQL and mySWL database.
3.1.2
Operating modes
The myAMC.Messenger server can work in two different operating modes.
Learn Mode
In Learn Mode myAMC.Messenger automatically recognizes new, so far unknown message

categories and stores them into its library. The administrator can now easily define new action
filters and reactions for the newly learned alerts and events.
Work Mode
In Work Mode myAMC.Messenger rejects all messages which are not currently part of the
message definition library. If you select this mode you can reduce the load of
myAMC.Messenger which is caused by learning new message categories. Therefore, new
alerts can be filtered, e.g., by the assignment of a special category in spite of switched off
Learn Mode. Configuration of the work mode is described in chapter Configuration.
Stand: 05.04.2012
General section
Page 20 of 148
3.1.3
Input interfaces
myAMC.Messenger provides several input interfaces for messages.
The Receiving Interfaces are responsible for receiving and identifying incoming alerts and
messages. Functionality and configurating differ between different interface types.
3.1.3.1 SNMP Trap interface

myAMC.Messenger can receive messages from any applications and devices using SNMP
traps.
By default myAMC.Messenger recognizes and interprets messages only from components of
the myAMC product family. Messages of other applications and devices are processed using a
pre-defined default handling.
With Messenger Expert the user may specify application specific formulas, which map
incoming SNMP traps to the common myAMC message schema. The formulas analyses the
incoming traps and passes them to the trap processing interface of myAMC.Messenger.
The formula module and some example rules are described in the chapter 4
myAMC.Messenger Usage. The creation and implementation of rulesets are described in
chapter 5 myAMC.Messenger: Configuration.
3.1.3.2 Database interface

Direct input into the database is a very powerful interface to integrate and connect applications
with myAMC.Messenger.
myAMC.Messenger maintains a table for incoming messages where messages can directly be
inserted with conventional SQL commands. To use this interface you have to connect to the
myAMC. Messenger Repository over an ODBC or JDBC connection. After insertion into the
input table, myAMC.Messenger starts processing all newly found messages.
3.1.3.3 Email interface

myAMC.Messenger can receive messages using a builtin mail server.
By default myAMC.Messenger obtaines some meta-data attached to an email message such
as sender and stores the email body as message text. The handling of incoming email
messages can be customized using formulas.
Note: This feature is only available with myAMC.Messenger Expert.
3.1.3.4 Messenger to Messenger Email communication
The myAMC.Messenger Email interface can be used for the communication between several
myAMC.Messenger components. In all situation when no direct communication is available or
not allowend in case of security requests.
A myAMC.Messenger in site A can send a Email to the Mailexchange proxy in site A. The
Mailserver in Site A transfers the message to a definid Email Adress for site B. The mailserver
Stand: 05.04.2012
General section
Page 21 of 148
on site B makes an forward to the local emailservice of messenger in site B. the message can
be tsendes with the format MailTrans2Messenger.
3.1.3.5 Messenger TicketID
The myAMC.Messenger can create a unique Ticket ID send with every SNMP Trap or email.
The TicketID has to be definied with myAMC.Messenger Configuration GUI global variables
Serialnumber.
3.2 Message History

The message history is a table in the repository of the messenger database with all incoming
events. In the standard operation mode all events are strored in the same table.The
myAMC.Messenger starting at Version 8.0 allows the change of the standard mode to
reactionmode.The global variable ALWAYS2HISTORY must be changed to false.
The reactionmode defines the message history as receivertyp like email or snmp Trap.The
difference to the standard mode is that every message is stored in the history. The
reactionmode stores only the message which can pass the filterrule for the message history.
The standard filter definition for the reactionmode has a all match filter rule, that means the
same result as the standard mode. To use the reactionmode for special tasks the reaction rule
has to be adapted.
An other feature of the new reactionmode is to split the incoming events in dependency of
message typ to different history tables. Such a table must have the same datastructure as the
standard history table. In the default repository of the messenger are tables
DYN_HISTORY_1
DYN_HISTORY_2
DYN_HISTORY_3
are predefined.
Stand: 05.04.2012
General section
Page 22 of 148
3.3 Filters
Extensive support for filtering is one of the most important features of myAMC.Messenger.
Input interface
No reaction
Receive and identification rule
sets
Standard and
Precision filter
Filter
rules
No reaction
Reactions
Standard message
history
Receiver groups
Group x
Group y
Group z
Alternative
message
history
Output interface
Physical receiver
Repositor
y
Email, SNMP Trap, external program
Figure 2
myAMC.Messenger:Filter: Workflow
myAMC.Messenger provides both Standard filters and Precision filters, which can be used to
specify, which actions to perform whenever an important event occurs.
The Standard filter decides whether to react on an alert and whether to forward the incoming
alert to the Precision filter.
This mechanism allows easy activation or deactivation of groups of alerts while leaving the
possibility for special treatment of specific alerts.
A simpe example is to deactivate the Toner empty alert, sent by myAMC.Printer using the
Standard filter. The Precision filter can now be used to activate this alert for specific printers,
while the alert is ignored for other printers.
Filters can be applied for a number of attributes for each alert using wildcards which gives the
administrator a powerful tool to react on specific events and scenarios.
The filtering component also provides time-based filtering. Alerts of similar type, which arrive
within a specified time span, can be filtered so that only one alert is allowed to pass. The time
filter specifies the time range, for which alerts of similar type are blocked. As long as the time
filter is active for a specific alert the number of similar incoming alerts is displayed together
with the current alert.
The parameter Discard first controls whether to forward the first or last <count> messages.
Stand: 05.04.2012
General section
Page 23 of 148
Discard first is not set: The first <count> messages in the time range will be processed; the
following messages will be discarded.
Discard first is set: The first <count> messages will be discarded, the following messages will
be processed.
The filter mechanism, in conjunction with the configured reactions for all alerts are a base
requirement for the reasonable use of Notification via SMS and/or email.
No reaction
Standard filter
Standard filter active,
no precision filter
Standard filter active,

Precision filter enabled
No reaction
Precision filter
Message matches
filter perform
reactions
Standard
message history
Reactions
Repository
Reactions
Figure 3
Alternative
message
history
myAMC.Messenger: Filter
Stand: 05.04.2012
General section
Page 24 of 148
3.4 Reactions
Essential parts of the myAMC.Messenger are the many possibilities to react on received,
identified and filtered messages. You can define reactions in order to notify administrators or
operators. After a message passes the filters, it can be routed to different receivers using
several types of reactions.
3.4.1
Reaction types
myAMC.Messenger offers a wide range of reaction types.
The following services are available:
Sending emails to several receivers
Sending SMS to several receivers (currently only on Microsoft Windows)
Sending user defined messages to an Web service
Sending a SNMP trap to other management consoles or another myAMC.Messenger
Execution of an arbitrary external program, e.g. to establish a link to a Job Control System
Write message information to a log file
Store messages in alternative message history tables
Stand: 05.04.2012
General section
Page 25 of 148
3.4.2
Receiver groups
Receiver groups are an easy way to define reactions targeted at a group of message
receivers. Each receiver group consists of one or more receivers. Each receiver may specify
individual reactions and a scheduling plan for time-based message delivery. For example you
can send alerts to an administrator by email during the day and by SMS in the evening. In
addition a receiver group may specify a follow-up reveiver group, which is activated when the
receivers of the previous group are not available.
3.4.2.1 Predefined Receiver groups

Predefined receivergroups available fort he user :
Default
Example
History
Heartbeat
Robot
The receivergroups RobotIntern and FLEXFrame are internal groups and should not be
changed. Die Receivergroups RobotIntern und FLEXFrame sind interne Receivergruppen und
sollten nicht verndert warden.
Messages are always forwarded to a receiver group. Each member of the group is notified. A
receiver may be a member of several groups at once.
Each receiver may specify one or more physical receivers, which basically comprises one of
the available output method and method-specific configuration data, e.g. an email address.
The Receiver Heartbeat has table DYN_HISTROY_1 as destination, the Receicertyp History
has destination DYN_MSGHistory. The receiver robot hast the destionation robot.txt.
Example and Forwarder are empty receivers.
Stand: 05.04.2012
General section
Page 26 of 148
3.5 Output interface

The output interface defines style and structure of the outgoing messages. You can define
several output styles for each reaction type. As an example is you can specify which
parameters of a message should appear in the subject of an outgoing email and which parts
are contained in the email body.
For the dispatching of SMS notification, a short, concise message style can be chosen which
is needed to depict the message as easily and shortly as possible on the display of a mobile
phone.
This is also very important for the transfer of parameters to an external program which shall
be started as a reaction after an alert.
Youll find the configuration of the output interface in detail in chapter myAMC.Messenger:
Configuration.
3.6 Master/Slave Messenger

The myAMC.Messenger has starting with version 8.0 an master/slave mode for high
availability requirements.
A master/slave installation needs an second myAMC.Messenger service on an other node.
The second messenger service works as slave messenger.
The myAMC.Messenger slaves receive the same traps as the master but dont transfer the
events to the repository or to the receivertyps.
The myAMC.Messenger slave monitors the livetraps from myAMC.Messenger master, if the
myAMC.Messenger Master fails the myAMC.Messenger slave takeover the master rule.
To start the myAMC.Messenger in a defined rule use the fooling startparameter
/mode: MASTERSLAVE for the master

The myAMC.Messenger starts in mode Master, if an other myAMC.Messenger exists in the
Master rule the mode of the running myAMC.Messenger is changed to slave.
/mode:SLAVEMASTER for the slave
The myAMC.Messenger is started in slave mode, if no other myAMC.Messenger exist the
starting myAMC.Messenger service changes to the master ruel.
Requirements :
All messages have to be send to all myAMC.Messenger services.
All myAMC.Messenger services can receive multicast messages from each other. In case
of problems the routing like this have to added (route add net 224.0.0.0 netmask 240.0.0.0 dev
lo).
To activate the master/slave mode the global variable ABC must be true. In other cases the
myAMC.Messenger works as Master..
Stand: 05.04.2012
General section
Page 27 of 148
3.7 Repository
All myAMC components use a relational repository based on a MySQL or MS-SQL Server
database. The repository is devided into several parts of configuration data, currently
processed messages, message history, as well as basic data for the creation of filter functions
and reactions.
The repository from myAMC can be integrated with the main repository of other myAMC
components or can be used seperately to monitor and distribute events to serveral workplaces
and sites. Each instance of myAMC.Messenger can send SNMP traps, so you can build
hierachical, distributed and redundant structures very easily.
3.7.1
Fault-resistant Message Repository

In order to ensure message processing and throughput, myAMC.Messenger is designed to
continue operation even if the underlying message repository is temporarily unavailable.
Repository failures are handled gracefully so messages are always processed and forwarded
by myAMC.Messenger even if the database is not available or blocks read and/or write
access.
3.7.1.1 Repository failure

At program start, myAMC.Messenger retrieves configuration information from the database.
Afterwards, myAMC.Messenger can gracefully cope with database failures without missing or
delaying messages.
If the repository is unavailable, messages will be processed correctly, but they wont be written
to the message history. This means they are unavailable for later analysis using the Message
View in myAMC GUI applications. Another drawback is, that the configuration cannot be
changed, as it is kept in the database as well.
When the database becomes available again, myAMC.Messenger reconnects and stores
messages again.
3.7.1.2 Master-Slave Database
In order to guarantee that all messages are available in the message history even in case of
database failure myAMC.Messenger can use a slave database.
At program start, myAMC.Messenger retrieves configuration information from the master
database and stores a copy in the slave database. If the master database is not available at
program start, myAMC.Messenger is still able to start and operate correctly, as it reads
configuration data from the slave database.
If the master database fails, myAMC.Messenger stores all incoming messages in the slave
database. When the master database becomes available again, myAMC.Messenger
reconnects and transfers all messages from the slave database back to the master database
and resumes normal operation.
Note: In order to use this feature MySQL ODBC Driver V3.51.14 or newer is required.
See chapter 5.3 on how to configure master-slave mode.
Stand: 05.04.2012
General section
Page 28 of 148
4 myAMC.Messenger Usage
4.1 Introduction
The myAMC.Messenger has a wide range of use. In the following chapters areas of use of
myAMC.Messenger are presented. The description of the corresponding configuration dialogs
can be found in chapter 5.
Enterprise
event console
myAMC.Messenger
myAMC.MessageViewer
Email, SNMP Trap, External programs
myAMC.Messenger
Server, Network,
Storage
myAMC
FA Agents
Master
Repository
Slave
Repository
myAMC
LogAgent
Log
files
Figure 4
myAMC.Messenger: Structure
Stand: 05.04.2012
General section
Page 29 of 148
4.2 Examples
4.2.1
Example: Input formulas

The following examples demonstrate the use of formulas for message input. Comments are
initiated with //.
Note: There is no support for comments in real formulas. They are used to annotate the
formua in this manual only.
4.2.1.1 Example 1
//Initialize output fields TYPESTRG, CATEGORY, HOST, SHORTMSG and SEVERITY
OutSType='Alarm';
OutSCat='AlCl';
OutSHost='';
OutSShortMsg=;
OutLSeverity=50;
//Copy the value of variable binding with OID .1.3.6.1.4.1.4321.1.1.1.2 to HOST field
IF(SnmpSGetByOid(VarS01,'.1.3.6.1.4.1.4321.1.1.1.2'))THEN OutSHost=VarS01 FI;
//If HOST field is empty then copy IP adress of sending host into
IF(OutSHost=='')AND(InSSendHostIp<>'')THEN OutSHost=InSSendHostIp FI;
//Copy the value of variable binding with OID .1.3.6.1.4.1.4321.1.1.1.3 to SHORTMSG field
//If this character string contains the word CRITICAL, the SEVERITY field is set to critical. If it
//otherwise begins with the word WARNING, the SEVERITY field is set to warning
IF(SnmpSGetByOid(VarS01,'.1.3.6.1.4.1.4321.1.1.1.3'))THEN
OutSShortMsg=VarS01;
ChrSUpper(VarS01);
IF(ChrSFind(VarS01,'CRITICAL')THEN OutLSeverity=250
ELSE IF(ChrSCmp(VarS01,'WARNING')THEN OutLSeverity=150;
FI FI;
FI;
Stand: 05.04.2012
General section
Page 30 of 148
4.2.1.2 Example 2
//Initialize output fields TYPESTRG, CATEGORY, HOST, SHORTMSG, SEVERITY
//and GROUP
OutSType='Alarm';
OutSCat='AlCl';
OutSHost='';
OutSShortMsg=;
OutLSeverity=50;
OutSGroup='None'
//Copy the value of the 1st variable binding to HOST field

IF(SnmpSGetOidByIdx(VarS01,1))THEN
ChrSExpression(OutSHost,VarS01,'(.*?)','($1)');
FI;
//If HOST field is empty then copy IP adress of sending host to HOST field. If sending
//hostname is TestHost or IP address is 0.255.255.17 then setting GROUP field to Test
IF(OutSHost=='')AND(NOT(InSSendHostIp==''))THEN OutSHost=InSSendHostIp FI;
IF(OutSHost=='TestHost')OR(InSSendHostIp=='0.255.255.17')THEN OutSGroup='Test' FI;
//Read the 1st bit of the numeric value of the 2nd variable binding to VarL01.
//If the bit is set then set SEVERITY field to critical, otherwise set it to warning
//If the SnmpSGetOidByIdx function fails failes, the trap will be discarded
IF(SnmpSGetOidByIdx(VarS01,2))THEN
VarL01=KvtS2L(VarS02) & 7;
IF(VarL01>0)THEN
OutLSeverity=250;
ELSE
OutLSeverity=150;
FI;
ELSE
OutLValid=0;
FI;
//Get current timestamp (in GMT) and copy date and time as character string to
//the SHORTMSG field
VarL00=DateLGetAktSec();
IF(DateLSecToDateGm(VarS01,VarS02,VarL00))THEN
Stand: 05.04.2012
General section
Page 31 of 148
OutSShortMsg='Date: ';
ChrSAdd(OutSShortMsg,VarS01);
ChrSAdd(OutSShortMsg,', Time: ');
FI;
//Read all variable bindings starting from the 3rd and append the value to the SHORTMSG
//field
VarL00=SnmpLGetCount();
FOR VarL01=2,VarL01<VarL00,VarL01=VarL01+1 DO
IF(SnmpSGetByIdx(VarS01,VarL01+1))THEN
IF(VarL01==0)THEN
ChrSAdd(OutSShortMsg,'; ')
ELSE
ChrSAdd(OutSShortMsg,', ')
FI;
ChrSNoControl(VarS01,' ');
FI;
ROF;
//Replace all # in SHORTMSG by underlines

//Notice: ChrSReplace(OutSShortMsg,#,_) will do the same
VarL01=0;
VarS04='';
VarL02=ChrLGetLen(OutSShortMsg);
WHILE(VarL01<VarL02)DO
ChrSGetChar(VarS03,OutSShortMsg,VarL01);
IF(VarS03=='#')THEN VarS03='_' FI;
ChrSAdd(VarS04,VarS03);
VarL01=VarL01+1;
ELIHW;
IF(VarS04<>'')THEN OutSShortMsg=VarS04;FI;
Stand: 05.04.2012
General section
Page 32 of 148
4.2.2
Example: Receiver types

4.2.2.1 Example: Alerting with myAMC.Messenger and myAMC.Network

Prerequisites
Installed and configured myAMC.Network.
Task
If a network connection to a monitored server is going down, myAMC.Messenger should
send a email to the network administrator. The trap from myAMC.Net contains the key
word ping and is critical.
Procedure
The following instructions explain all required steps in detail.
4.2.2.1.1 Configure the email connection
Figure 5
Configuration: Example: Email connection
Open the myAMC.ConfigViewer tool and open the property page Messenger / Settings /
MailSettings. Enter the host name of your mail server, the address of the email sender, the
mail server port, and the mail receiver port.
Stand: 05.04.2012
General section
Page 33 of 148
4.2.2.1.2 Configure the user Administrator as receiver
Figure 6
Configuration: Example: Receiver
Open the myAMC.ConfigViewer tool and open the property page Messenger / Targets /
Message Receivers. Press the Add-button. Enter the contact details of your network
administrator.
Stand: 05.04.2012
General section
Page 34 of 148
4.2.2.1.3 Configure the physical receiver of receiver Administrator
Figure 7
Configuration: Example: Physical Receiver
Open the myAMC.ConfigViewer tool and open the property page Messages / Tagets /
Message Receivers. Select your network administrator and press the button Physical
Receivers. In this dialog you press the Add-button and select you physical receiver. The
physical receiver should be Email, the address is the email address of your network
administrator. Save every change by clicking the Save button.
Stand: 05.04.2012
General section
Page 35 of 148
4.2.2.1.4 Create a new group Network_Group
Figure 8
Configuration: Example: Receiver Group
Receiver Groups. Press the Add-button. Type the name of the new group: Network_Group. In
the field Comment you can type a comment you like. The field Next could be left empty.
Press the Save button
Stand: 05.04.2012
General section
Page 36 of 148
4.2.2.1.5 Add your network administrator to the receiver group Network_Group
Figure 9
Configuration: Example: Members of the Receiver Group
Receiver Groups. Select the receiver group Network_Group and press the Timed receiversbutton. Press the Add button at the bottom of the property page. Select your network
administrator and press Save.
Stand: 05.04.2012
General section
Page 37 of 148
4.2.2.1.6 Configure a suitable Standard filter
Figure 10
Configuration: Example: myAMC Standard Filter
Open the myAMC.ConfigViewer tool and open the property page Messenger / Filters &
Reactions / Standard filters. Select the Add-button. Select as application myAMC.Net and as
severity Critical. Select the tick ApplyPrecisionFilter and ForwardMessage to deactivate the
filter. Press Save.
Stand: 05.04.2012
General section
Page 38 of 148
4.2.2.1.7 Configure a suitable Precision filter
Figure 11
Configuration: Example: myAMC Precision Filter
4.2.2.1.8 Summary
Open the myAMC.ConfigViewer tool and open the property page Messenger / Filter &
Reaction / Precision filter. Select the Add-button. Select application myAMC.Net with operation
<==> (equal). Select severity Critical together with the operation <==> (equal) in the Message
contents panel. Activate the field ShortMessage and type *ping*. Go back to the Message
source panel; enable the precision filter and press Save.
In the last chapter and in this chapter a standard filter and a precision filter were defined.
These two filters work together as described below:
The standard filter makes sure that only selected critical alerts from myAMC.Network will be
processed by delegating to a precision filter to restrict the messages being forwarded to the
user Administrator.
The precision filter takes the alerts from the newly configured but deactivated standard filter
and makes sure that all critical alerts from myAMC.Network which contain (!) the word ping in
the short message will be processed by the reaction.
This behavior of the two filters is also described in chapter 0 and corresponds with the 2
in the table of the chapter.
Stand: 05.04.2012
General section
nd
row
Page 39 of 148
4.2.2.1.9 Test your example
Now you can test your example. The best way to do this is if you configure a non critical PC in
myAMC.Network and unplug the LAN connection from this PC. With the next poll of this PC
the necessary trap will be sent to the myAMC.Messenger and then sent as email to your
network administrator.
Stand: 05.04.2012
General section
Page 40 of 148
4.2.2.2 Example: Physical Receivers

Task
This example teaches how to create receivers as well as assigning these receivers real
physical receivers like email, SMS, file, external programs and so on.
Procedure
4.2.2.2.1 Configure the email connection
Figure 12
Configuration: Example: Email connection
Open the myAMC.ConfigViewer tool and open the property page Messenger / Settings /
MailSettings. Enter the host name of your mail server, the address of the email sender, the
mail server port, and the mail receiver port.
4.2.2.2.2 Create a receiver

First you have to create a receiver. Open the myAMC.ConfigViewer tool and open the property
page Messenger / Targets / Message Receivers. Choose an existing receiver or press the
Add-button to create one. Please type in the contact informations of the new receiver (e.g.
Administrator). Press the Save button.
Stand: 05.04.2012
General section
Page 41 of 148
Figure 13
Configuration: Example: Receiver
Now you can specify the real physical receivers.

4.2.2.2.3 Physical receiver: Email
Press the Physical Receivers button and choose the desired physical receiver type. The
receiver type should be Email, the address is the email address of your network administrator.
Stand: 05.04.2012
General section
Page 42 of 148
This email address is used to send the mail to. The Summary message is sent as email
subject, while the Detailed message is used as email body.
Note: The email address specified in the dialog Message Receivers is not used for this
purpose.
Figure 14
Configuration: Example: Physical Receiver: Email
Stand: 05.04.2012
General section
Page 43 of 148
4.2.2.2.4 Physical receiver: Pager
Message Receivers. Choose an existing receiver or press the Add-button to create one. Press
the Physical receivers button. Press the Add button and choose the desired physical receiver
type. The receiver type should be Pager along with the target mobile service operator. The
address is the mobile phone number of the administrator. This phone number is used to send
a SMS.
Note: The phone number specified in the dialog Message Receivers is not used for this
purpose.
Note: This feature is only supported for a myAMC.Messenger running on Windows.
Figure 15
Configuration: Example: Physical Receiver: Pager
Stand: 05.04.2012
General section
Page 44 of 148
4.2.2.2.5 Physical receiver: File
First open the myAMC.ConfigViewer tool and open the property page Messenger / Message
output / Files. Press the Add button set the logfilename (e.g.printer alter file) type in the
physical file name (e.g. C:\var\log\printer_alerts.out) and if desired set the file size restrictions.
Figure 16
Configuration: Example: File definition
Next open the myAMC.ConfigViewer tool and open the property page Messenger / Targets /
Message Receivers. Choose an existing receiver or press the Add-button to create one. Press
Physical receivers, than the Add button and configure your physical receiver. The physical
receiver type should be File, the sub type should be the one defined in the File dialog in the
section above.
Stand: 05.04.2012
General section
Page 45 of 148
Figure 17
Configuration: Example: Physical Receiver: File
4.2.2.2.6 Physical receiver: External commands

output / External command. Press the Add button and specify the description of the external
program (e.g. Send a Ping). Enter the command line of the external program (e.g.
C:\WINNT\system32\ping.exe).
Note: The program must exist.
Note: If running on Windows make sure to set the tick Allow service to interact with desktop in
the properties of the service myAMC.Messenger Server if you want to start a GUI based
program.
Stand: 05.04.2012
General section
Page 46 of 148
Figure 18
Configuration: Example: External command definition
Switch to the property page Messenger / Targets / Message Receivers. Choose an existing
receiver or press the Add-button to create one. Press the Physical Receiver button, than Add
button and select your physical receiver. The physical receiver type should be External, the
Sub type should be the one defined in the external command dialog in the section above.
Stand: 05.04.2012
General section
Page 47 of 148
4.2.2.2.7 Physical receiver: Tables

output / Tables. Press the Add button and specify the description of the Table.
Figure 19
Configuration: Example: Physical Reciever External commands
Next open the property page Messenger / Targets / Message Receivers. Choose an existing
receiver or press the Add-button to create one. Press the Physical Receiver button, than the
Add button and select your physical receiver. The physical receiver type should be Table, the
sub type should be the one defined in the Tables dialog in the section above.
Stand: 05.04.2012
General section
Page 48 of 148
4.2.2.2.8 Physical receiver: WebServices

Open the myAMC.ConfigViewer and open the property page Messenger / Targets / Message
Receivers. Choose an existing receiver or press the Add-button to create one. Press the
Physical receivers button and create a physical receiver with the Add button. The physical
receiver type should be Http, as sub type choose Http FlexFrame, the address can be
e.g. http://127.0.0.1:8080/FAwebgui/FlexServlet, as Summary message you can choose the
output style HTTPFlexFrame. The rest you can leave blank.
Note: The output style of the Summary message must be understood by the receiving
WebService. In case of a FlexFrame system, the pre-defined style HTTPFlexFrame is
used to forward incoming messages to the FA WebGui.
Figure 20
Configuration: Example: Physical Receiver WebService
Stand: 05.04.2012
General section
Page 49 of 148
4.2.2.3 Example: Time tables

Task
In order to learn how to work with time tables we construct a simple scenario which can
happen in nearly all large companies with shift work. We have two persons (<Person1>,
<Person2>). >Person1> should be alerted from Monday to Friday in the time range from
8:00 am untill 12:00 pm. <Person2> should be alerted from Monday to Friday in the time
range from 12:00 pm untill 4:00 pm.
Result
from Monday to Friday <person1> will be alerted in the time from 8:00am to 12:00 pm.
<Person2> will be alerted on these days from 12:00 pm to 04:00 pm.
Note
Procedure
4.2.2.3.1 Create the two receivers

First we have to create the two receivers (<Person1>, <Person2>). To do so look in the
examples above on how to create physical receivers
Figure 21
Configuration: Example: Create the two receivers
Stand: 05.04.2012
General section
Page 50 of 148
4.2.2.3.2 Create a group
Now we have to create a group. (e.g. Shiftplan1) Change to the Receiver Groups dialog
and press the "Add" button. Fill in the name of the new group. (e.g. shiftplan1) and press the
Save button. After pressing the Timed receivers button, press the Add button and select
the receivers Person1 resp. Person2 and press the Save button.
Figure 22
Configuration: Example: Create a group
Stand: 05.04.2012
General section
Page 51 of 148
4.2.2.3.3 Select the group created before
Now select the group created before (Shiftplan1), press the Timed receivers button and select
the receiver (<Person1>) for whom you want to specify a time range. Now press the Receiver
schedules button, a new dialog appears. Press the Add button and select the new time range
where <Person1> will be alerted. Do these steps as often as you want to specify different time
ranges you want to define for this person. At last press the Save button. Do this also for
receiver <Person2>.
Figure 23
Configuration: Example: Select the group create before
Stand: 05.04.2012
General section
Page 52 of 148
4.2.3
Example: Receiver Groups

4.2.3.1 Example: Receiver Groups

Task
Receiver groups form one or more receivers into a group. For each group more than
one reaction may be dfined, which allows to meet almost any requirement..
Procedure
4.2.3.1.1 Define some receivers

Define some receivers. Please see the examples above on how to perform this step
4.2.3.1.2 Create groups

This example explains the creation of groups. (e.g. <Office1>, <Office2>). Change to the
Receiver Groups dialog and press the Add button. Enter the name of the new group. (e.g.
<Office1>). After you have done this, press the Save button and proceed in the same way with
the other group.
Figure 24
Configuration: Example: Create groups
Stand: 05.04.2012
General section
Page 53 of 148
4.2.3.1.3 Assign receivers
Now you have to assign the receivers to the groups. Select the new group (<Office1>) and
press the Timed receivers button. Press the Add button and select the receiver you want to
add to the group. Do this with all recievers you want to add to this group and press Save. Do
these steps in a similar way for the other group.
Figure 25
Configuration: Example: Assign receivers
Stand: 05.04.2012
General section
Page 54 of 148
4.2.4
Example: Filter
4.2.4.1 Example: Standardfilter

Task
All events and alerts from each printer should be logged in a separate file.
Result
All alarms, events and so on of each printer will be logged in a file.
Note: -
Procedure
4.2.4.1.1 Switch to Filter Learn Mode

First be sure that the tick Enable Filter Learn Mode in the Messenger / Settings / Message
Settings menu is switched on.
4.2.4.1.2 Filter dialog

Change to the Messenger / Filter & Reactions / Standard Filter dialog and look that all
Standard filters with Application myAMC.Printer are active.
Stand: 05.04.2012
General section
Page 55 of 148
Figure 26
Configuration: Example: Filter dialog
Stand: 05.04.2012
General section
Page 56 of 148
4.2.4.1.3 Select the file
Now you have to select the file in which you want to log all messages. Switch to the
Messenger / Message output / Files dialog and press the Add button. Now you can select the
name (description) of the file and the physical filename. If you want to restrict maximum file
size or age you can do this as well
Figure 27
Configuration: Example: Select the file
Stand: 05.04.2012
General section
Page 57 of 148
4.2.4.1.4 Create a receiver
Next you have to create a receiver, to do so change to the Messenger / Targets / Message
Receivers dialog. Press the Add button and fill in the parameters for this receiver. If you have
done this you have to assign the file specified above to a physical receiver of the new receiver.
Press the Physical receivers button, so a new dialog pops up. Now press Add and change the
sub type of the physical receiver to File and choose the file where you want to log the events.
Figure 28
Configuration: Example: Assign a file to a receiver
Stand: 05.04.2012
General section
Page 58 of 148
4.2.4.1.5 Create a group
Now it is time to create a group. Open the property page Messenger / Targets / Receiver
Groups.Press the Add button. Enter the name of the new group. (e.g. printer-admins). After
that select the new group and press the Timed receivers button and add the receiver created
in the section above. After that press the Save button.
Figure 29
Configuration: Example: Create a group
Stand: 05.04.2012
General section
Page 59 of 148
4.2.4.1.6 Specify a reaction
Last but not least the reaction has to be specified. Open the property page Messenger / Filters
& Reactions / Reactions. Create a new reaction with the Add button. Select the Application
<myAMC.Printer>, the ApplicationOperator should be <==> (equal). The receiving group
should be the one defined in the section above.
Figure 30
Configuration: Example: Specify a reaction
Stand: 05.04.2012
General section
Page 60 of 148
4.2.4.2 Example: Precisionfilter

Task
In this example alerts should be logged only, if a special printer sends an TRAY EMPTY
message. All other alerts and events of other printers should not be logged. This
example requires the configuration of the previous example.
Result
Only the alert TRAY EMPTY of the printer HP5SI-TD3 will be logged in a file.
Note
Procedure
4.2.4.2.1 Deactivate the filter

The alert TRAY EMPTY belongs to the category AlClGlobal of the application myAMC.Printer
and it is a critical alert. Open the Messenger / Filter & Reactions / Standard filters dialog.
Select the filter matching these criteria. Deactivate the filter and enable the precision filter
(ApplyPrecisionFilter). This setting specifies that no alert of this category will be handled
unless a precision filter matches.
Figure 31
Configuration: Example: Deactivate the filter
Stand: 05.04.2012
General section
Page 61 of 148
4.2.4.2.2 Create a precision filter
To create a precision filter press the Add button in the Messenger / Filter & Reactions /
Precision filter section. One criterion to log an alert is that the alert comes from a special host.
So enable the field Host and write in the hostname you want to filter. Dont set the ticks for
negation and case-sensitive. Another criterion is the message text. Only the text TRAY
EMPTY is part of the wanted message. So switch to the page Message contents and enable
the field ShortMessage. Dont set the ticks for the negation and case-sensitive. Go back to the
page Message source and set the application equal (<==>) to myAMC.Printer.
Figure 32
Configuration: Example: Create a precision filter
Stand: 05.04.2012
General section
Page 62 of 148
4.2.4.3 Example: Reaction filter

Task
In this example, alerts of type TRAY EMPTY should be sent to user printer-admin and
alerts of type CLOSE PRINTER COVER will be forwarded to user printer-service. Both
users can be reached by email.
Result
If the tray is empty the printer-admin will get an email. If the printer cover is open the
printer-service will get an email.
Note
Procedure
4.2.4.3.1 Activate the fllter

Both alerts (TRAY EMPTY and CLOSE PRINTER COVER) belong to the category AlClGlobal
of the application myAMC.Printer and they are critical alerts. Change to the Messenger / Filter
& Reactions / Standard filter dialog. Select the filter matching these criteria. Activate the filter
and disable the precision filters which match the standard filter. All the alerts of the category
will be handled unless a precision filter matches.
Figure 33
Configuration: Example: Activate the filter
Stand: 05.04.2012
General section
Page 63 of 148
4.2.4.3.2 Create two receivers
Next step is to create two receivers (printer-admin, printer-service) as well as two receiver
groups (printer-admins, printer-services). The receiver printer-admin should belong to the
group printer-admins and the receiver printer-service is member of the group printer-services.
Please have a look at the examples above on how to perform these steps.
Figure 34
Configuration: Example: Create two receivers
Stand: 05.04.2012
General section
Page 64 of 148
4.2.4.3.3 Create two reaction filters
Now we have to create two reaction filters. Press the Add button in Messenger / Filter &
Reactions / Reactions dialog. The first filter should specify the TRAY EMPTY reaction. To do
so set the Application to myAMC.Printer, switch to the Message contents panel and set the
severity to Critical. Also activate the ShortMessage field and set the text to *TRAY EMPTY*.
Go back to the Message source panel and set the Receiver Group to "printer-admins".
Figure 35
Configuration: Example: Create two receiver filters 1
The second filter should specify the CLOSE PRINTER COVER reaction. To do so set the
Application to myAMC.Printer, switch to the Message contents panel and set the severity to
Critical. Also activate the ShortMessage field and set the text to *CLOSE PRINTER COVER*.
Go back to the Message source panel and set the Receiver Group to printer-services.
Stand: 05.04.2012
General section
Page 65 of 148
Figure 36
Configuration: Example: Create two receiver filters 2
Stand: 05.04.2012
General section
Page 66 of 148
4.2.5
Example: Output
4.2.5.1 Example: Output

Task
You can also define a customized output format for a message. For example your
output message should only print out Error on <host>. Only a subset of receivers should
get this message.
Result
If the receiver administrator gets an email from myAMC.Messenger the message text
will be: Error on <host>.
Note
Procedure
4.2.5.1.1 Design your output style
First you have to define the output style. Change to the Messenger / Message output / Output
styles dialog and press the Add button. Define the name of your own new style in the field
Description (e.g. myCompanyStyle1). In the field Text you can design your own style. Write
your own text mixed with parameters from the myAMC applications by selecting the
parameters you want (e.g. Error on @host@). The drop-down box provides all available
message fields. After you have defined your style press the "Save" button to finish.
Stand: 05.04.2012
General section
Page 67 of 148
Figure 37
Configuration: Example: Design your output style
4.2.5.1.2 Assign to a physical receiver

Now you have to assign the new output style to the physical receiver. Open the Messenger /
Targets / Message Receivers dialog and select a receiver (e.g. administrator) and press the
button Physical receivers. In the receiver dialog select or create a physical receiver (e.g.
Email). To assign your own output style, choose your defined output style for the fields
Summary message field and Detailed message.Finish by pressing the Save button.
Stand: 05.04.2012
General section
Page 68 of 148
Figure 38
Configuration: Example: Assign ouput style to a physical receiver
Stand: 05.04.2012
General section
Page 69 of 148
4.3 Funtional description
4.3.1
Input interfaces
4.3.1.1 Trap Input interface

myAMC.Messenger provides a SNMP Trap Input interface, which can receive arbitrary SNMP
traps. A parser analyses incoming messages, applies trap-specific formulas to normalize it into
the common myAMC message format and processes them according to the configured rules.
4.3.1.2 Database Input interface

myAMC.Messenger maintains a database table for incoming messages . Messages can
directly be inserted with conventional SQL commands.
4.3.1.3 EMail Input interface
myAMC.Messenger provides an email server, which can receive simple text emails. A parser
analyses incoming messages, applies formulas to normalize it into the common myAMC
message format and processes them according to the configured rules.
Stand: 05.04.2012
General section
Page 70 of 148
4.3.2
Message structure
All messages received by other myAMC components through the SNMP interface have a welldefined structure.
These structures contain the following elements:

Application ID: specifies which component generated the alert, e.g. SAP Collector or
myAMC.Network component
Logical Group: elements monitored by myAMC components are usually members of one or
more logical groups. Grouping criteria may comprise organizational unit, physical
location or grouping into production or test environments. Messages can be processed
using different rule sets for specific groups.
Severity: all alerts of myAMC components contain a value that defines whether it is a warning,
a critical message or just some simple information..
Category: as an additional feature, categories such as performance alert are given to alerts
Message: a message text no longer than 250 characters
4.3.3
Filter Learn mode

If the flag for the Filter learning mode is set in the Messenger / Settings / Message Settings
dialog, all messages coming through an input interface are stored in the message library.
Individual messages can selectively be deactivated from a group.
4.3.4
Dynamic processing
For each message, all filter conditions are to be checked. In a filter condition, it is decided
whether a message corresponds to a criterion. Afterwards, it is checked in which group this
filter condition is configured.
Stand: 05.04.2012
General section
Page 71 of 148
4.3.5
Message group
A message group consists of receivers to receive the message. Each receiver may specify
one or more of the following message transport actions:
EMail
SMS (Windows only)
SNMP Trap
HTTP
External command
File
Table
Each transport method has a priority attached. A priority value of 0 disabled the corresponding
transport method. Methods with higher priority (i.e. lower numeric value) are tried before
transport methods with lower priority (i.e. higher numeric value). Only if no transport methods
of a priority level succeeded, the next level will be tried.
Additionaly each member of a group can be bound to one or more time ranges, e.g. to reflect a
service schedule..
4.3.6
Log File
For administrative use the myAMC.Messenger uses a log file to write errors, warnings or
program operations.
On a Windows installation it is located in <BASEDIR>\Messenger\AMCMsgServer.log.
And on a Linux system you can find it in <BASEDIR>/Messenger/log/AMCMsgServer.log.
<BASEDIR> is the folder of your myAMC.Messenger installation.
Stand: 05.04.2012
General section
Page 72 of 148
5 myAMC.Messenger: Configuration
5.1 Introduction
Generally the messenger can be used with the default configuration settings. Usually though,
not all messages are treated the same way. Therefore, you can limit the transmissions by
configuring filter rules and user groups.
The following elements belong to the data set:
Configuration of pager parameters for individual SMS Providers
Configuration of a mail server used for sending emails
Configuration of user data
Library with messages
The data sets can be adjusted using the myAMC.ConfigViewer. Also, myAMC.Messenger has
been a built in learning mode to learn filters for unknown message types automatically.
Stand: 05.04.2012
General section
Page 73 of 148
5.2 Functional description
5.2.1
Program handling
5.2.1.1 Menu bar

With the menu bar you can control program-wide settings
Figure 39
myAMC.Messenger: Config: Menu bar
File
Exit
Closes the myAMC.ConfigViewer.
Config
Described in chapter 0 Tool Bar.
Settings
Here you can choose between the following options.
Connectors
Shows the registered connections, described in chapter 0.
Stand: 05.04.2012
General section
Page 74 of 148
Switch to Normal/Expert mode

Here you can switch to Normal/Expert mode. In normal mode some advanced
and rarely used configuration dialogs are hidden. If they are needed for
configuration purposes switch to the expert mode using this menu option or by
pressing ctrl + m.
5.2.1.2 Controls
This panel is the main control view, here you can add, edit, copy and delete data, close the
menu or refresh the view. The chosen action will be shown in the main panel. You can edit
existing data by clicking the item in the instances list of the main panel and modify the data.
Figure 40
myAMC.Messenger: Config: Controls
Controls menu
Some menus will not support all of those options listed below, this is an overview of all
possible options you will have in the controls menu.
Close
Closes the current view.
Refresh
Refreshes the current view.
Delete
Deletes all selected setting configuration items in the table on the lower right.
General section
Page 75 of 148
Stand: 05.04.2012
Copy
Copies the selected configuration items in the table on the lower right.
Add
Creates a new configuration item.
Discard
Discards all unsaved changes of this view.
Save
Saves all changed settings of this view.
Note: Some settings will only be valid after a restart of myAMC.Messenger.
Stand: 05.04.2012
General section
Page 76 of 148
5.2.1.3 Main panel

In this window the selected configuration view will appear. It is the main window to alter the
configuration of the selected configuration menu.
Figure 41
myAMC.Messenger: Main panel
Main panel
The main Panel is the view where you can see and change all data wich can be
configured by the myAMC.ConfigViewer. You can also see the instances of already
configured items and their values.
Stand: 05.04.2012
General section
Page 77 of 148
5.2.1.4 Tool Bar

The toolbar provides quick access to often used actions and controls like setting up the
location of the myAMC component or choosing the configuration view.
The toolbar can be placed freely. It is possible to stick it at any border of the
myAMC.ConfigViewer, so you can adjust it to your needs.
Figure 42
myAMC.Messenger: Config: Tool Bar
Exit
This button closes the myAMC.ConfigViewer. The user will be prompted whether
to save any unsaved data.
Connectors
Shows the registered connections and their connection states (described in
chapter 0).
Configuration
This button provides access to all available configuration actions . By rolling over
the desired component you will see a list of the menus of the component. Clicking
them will display it in the main panel.
Stand: 05.04.2012
General section
Page 78 of 148
5.2.1.5 Connectors
myAMC.ConfigViewer needs to connect to the data source(s) containing the configuration
data. Data sources may comprise databases or web services. On this property page you can
setup connections to the configuration data sources. The connection can be stored
permanently, so the connections need to be set up only once.
Figure 43
myAMC.Messenger: Config: Connectors
Add
Here you can add a new connection.
Remove
Removes the selected entries
Save
Saves the currently configured connectors. This configuration will be restored upon
program (re)start.
Reload
Reloads the connectors file
Edit
Edit the selected connector
Stand: 05.04.2012
General section
Page 79 of 148
Tools
Test
Test availability of the connection. This can be used to ensure, that the
connection is configured correctly, e.g. with correct user name and password.
Import
Import previously configured connectors from a file.
Export
Export the connectors to a file. Only the selected connectors will be exported. You
can select multiple connectors by pressing Shift and/or Ctrl key.
Add a connector
Database
Creates a new connection with a database.
Here you can setup the database settings which will allow you to connect. In this
version it is possible to use a MySQL or a MS-SQL database.
Stand: 05.04.2012
General section
Page 80 of 148
Web
Http connections are currently not supported.
Import
Import a connectors file with previously configured connectors.
Note: If more than one connector provides access to a configuration data set,
myAMC.ConfigViewer will connect to the first one in the list, or the one with the
highest priority.
Stand: 05.04.2012
General section
Page 81 of 148
5.2.2
Messenger
5.2.2.1 Settings
5.2.2.1.1 Message Settings
This page contains basic settings for the configuration of myAMC.Messenger. All changed
data is stored by clicking the Save Button. They only take effect after a restart of
myAMC.Messenger (except Filter Learn Mode).
Figure 44
myAMC.Messenger: Config: Message Settings
Max Message Hours

This value specifies the maximum age of messages in hours processed by
myAMC.Messenger. If a message is older, it will be moved to the history and marked as
failed. You can disable this feature by setting this value to zero.
You shouldnt set this value to one hour, because changing between daylight saving
time during runtime of myAMC.Messenger may delete new but so far unprocessed
messages.
Max Message History Hours

This value specifies the maximum age of processed messages in hours.
MyAMC.Messenger will regulary delete older messages. The messages contained in
Stand: 05.04.2012
General section
Page 82 of 148
the message history can be browsed using the Message View of myAMC.ConfigViewer
or other myAMC GUIs.
Max Logfile Size (KB)

This value specifies the maximum size of the myAMC.Messenger logfile in KB. If the
logfile has reached the specified size it is renamed automatically to the logfile name
completed with the extension .old. This will be done every time the maximum log file
size is reached.
Cycletime schedules reload (secs)

Specifies how often to check for new schedules in database. This configuration setting
is related to the TaskScheduler feature.
Cycletime config reload (secs)

myAMC.Messenger automatically reloads its configuration, if it detects changes. This
setting specifies how often to check for changed configuration data.
Enable Filter Learn Mode

If the Filter Learn Mode is switched on, each unknown message will create a new
standard filter, which is active by default. Each Standard filter has an entry date. So it
is possible to check for Standard filters inserted automatically by Filter Learn Mode. If
the Filter Learn Mode is switched off, unknown messages wont cause the creation of
new standard filters.
Note: If Filter Learn Mode is enabled, it could be that during the configuration with
the myAMC.ConfigViewer, new filters will be learned. These filters wont be shown in the
property page Standard filter. To show them, you have to refresh the content of the
propery page Standard filter in myAMC.ConfigViewer.
Log level
This option defines the myAMC.Messenger logfile loglevel.
Normal
This is the standard setting, you will see all important log information of
myAMC.Messenger. Normal messages include: ERR, FAT, WRN and MSG.
Warning
Using this setting you will see warnings and critical log information of
myAMC.Messenger. Warning messages include: ERR, FAT and WRN.
Critical
Using this setting you will only see critical log information of myAMC.Messenger.
Critical messages include: ERR and FAT.
Debug
This setting is not recommended, it is only for debugging purposes.
Stand: 05.04.2012
General section
Page 83 of 148
5.2.2.1.2 Mail settings

This view provides settings for regarding transmission of emails. All data is stored by clicking
the Save button. They only take effect after a restart of myAMC.Messenger.
Figure 45
myAMC.Messenger: Config: Mail Settings
MailServer
Host name or IP address of your SMTP server. If this field is empty, the transmission of
emails is disabled.
MailSender
Email address of the sender (i.e. myAMC.Messenger). This address is used as sender
and reply-to address.
MailServerPort
Port number on which your SMTP server accepts incoming connects. Default port is 25.
MailReceiverPort
Port number on which myAMC.Messenger will listen for incoming email messages.
Default port is 25.
Stand: 05.04.2012
General section
Page 84 of 148
5.2.2.1.3 Basic message forwarding

myAMC.Messenger Basic provides basic message forwarding capabilities via SNMP traps and
emails. All required parameters can be set on this property page.
A trap target might be another instance of myAMC.Messenger or a central network or system
management console such as IBM Tivoli or HP OpenView.
All data is stored by clicking the Save button. They only take effect after a restart of
myAMC.Messenger.
Figure 46
myAMC.Messenger: Config: Basic message forwarding
MailServer
Host name or IP address of your SMTP server. If this field is empty, the transmission of
emails is disabled.
MailSender
Email address of the sender. This address is used as sender and reply-to address.
MailTarget
Email address of the receiver.
TrapTarget
IP address or host name of the trap target.
Stand: 05.04.2012
General section
Page 85 of 148
TrapCommunity
SNMP community string of the trap target.
5.2.2.1.4 Pager Settings

This page contains settings required in order to send messages to mobile phones via short
message service (SMS). All changed data will be stored by clicking the Save button. They
only take effect after a restart of myAMC.Messenger
Note: This feature is only supported for a myAMC.Messenger running on Windows.
Figure 47
myAMC.Messenger: Config: Pager Settings
Use Pager
Switch on to enable pager messages. Otherwise all pager messages will fail.
Max Pager Retries
Pager centers can be busy (state of line) or may not answer your outgoing call. In this
case myAMC.Messenger retries to connect to the pager immediately. With this
parameter you can specify how often myAMC.Messenger tries to send a message to a
pager before setting its state to Failed.
Max Pager Messages Per Call
This setting limits the amount of messages sent during a single connection to the pager
center. This setting may limit the individual amount configured for each pager center too.
The value affects memory usage and therefore the scalability of the server
Modem
Here you can select the modem that should be used for connecting pager centers. If this
Stand: 05.04.2012
General section
Page 86 of 148
is an ISDN device it must be able to establish a connection using X.75 or V.110. See the
manual of your ISDN device on how to configure outgoing calls. Make sure that there is
a configured modem connected to the selected device of your server.
Stand: 05.04.2012
General section
Page 87 of 148
5.2.2.2 Messages
5.2.2.2.1 Messages
The message view allows easy brwosiung of all messages contained in the message history.
Figure 48
myAMC.Messenger: Config: Messages
The time range of messages to display can be controlled using the following elements:
Here you can set up the start of the time range. If the time span is set to a value
other than <None>, the end of the displayed time range will be adjusted
accordingly.
Please press
to update the message display.
Goes back for the amount of time specified by the span field
Refreshes the list

Stand: 05.04.2012
General section
Page 88 of 148
Stops the current query
Goes forward for the amount of time specified by the span field
Sets the end of the display time range to the current time and the begin of the
display time range to the current time minus the the amount of time specified by
the span field
Here you can set up the time span to display. If set to <none> the time span can
be specified freely by editing the from and/or end field. Otherwise the time
range start is always adjusted, when time range end has been changed and vice
versa.
Here you clear the message cache and set up the cache size.
Note: The cache wil be cleared as a result!
Here you can setup the end of the displayed time range. If the time span is set to
a value other than <None>, the start of the displayed time range will be adjusted
accordingly.
Please press
to update the message display.
The message views is refreshed periodically with the end of the displayed time
range being set to the current time. This allows a live update of all new
messages. Messages older than twice the time span will drop out off the message
view.
Stand: 05.04.2012
General section
Page 89 of 148
5.2.2.2.2 Alternative Message History 1-3

As the result of a reaction, selected messages can be moved to an alternative message
history. These views show messages contained in Alternative Message History 1 3.
these section 0 on how to configure alternative message histories.
Figure 49
myAMC.Messenger: Config: Aletrnative Message History 1-3
Handling and controls are identical to the Message View described in section 5.2.2.2.1.
Stand: 05.04.2012
General section
Page 90 of 148
5.2.2.3 Targets
5.2.2.3.1 Message Receiver
On this page you can setup message receivers. A receiver might be an existing person or
reflect a role within your organization. Each receiver should state a meaningful name and may
have on or more physical receivers. The receiver name is used in log files of the server to
name a receiver.
Actions on receivers are stored in database at once. They take affect at program start and
whenever the configuration is reloaded (see Cycletime config reload (secs) in section
5.2.2.1.1).
Note: Deleting a receiver which has physical receivers or which is referenced by a timed
receiver is not possible. All references to a receiver must be deleted before it can be deleted.
Figure 50
myAMC.Messenger: Config: Message Rceiver
Message Receiver
List of configured receivers with his postal address, phone number and Email address.
Stand: 05.04.2012
General section
Page 91 of 148
5.2.2.3.2 Physical Receivers

The receiver type specifies both method and target of a message. For some receiver types
you need to define the address and format of Summary and Detailed messages.
Figure 51
myAMC.Messenger: Config: Physical Receiver
The following table decribes all combinations of available methods and the corresponding
address and message format.
Receiver
Type
Receiver
Subtype
Email
Stand: 05.04.2012
Address
Output style summary

message
Output style - detailed

message
Email address
of receiver
Subject of the mail.

Take Const Text
if you are not shure
Body of the mail. Take

MailTrans2Messenger
General section
Page 92 of 148
External
A configured
external
application
(see chapter 0)
Parameter list for

the external
programm. Take
Standard Small if
you are not shure
File
A configured
output file (see
chapter 0)
Configured output
style for the output
file
Http
A configured
http receiver
Take
HTTPFlexFrame
Pager
The Pager
center of the
receiver
The phone
number of the
receiver
You should select

Standard Small
SNMP
myAMC
Format,
Hostname or
IP address of
the receiver
and SNMP
community
string,
separated by a
comma. If you
dont enter a
community it is
set to public
automatically.
Format of the
SNMP trap.
SrvrView
Format
Unicenter
Format
Take
SrvrView
Format if you
are not shure
For Unicenter Format this value is

ignored
For myAMC Format, the format of
the LongMessage
field can be set
For SrvrView Format, the format of
the field
DisplayString can
be set. You should
select SrvrView
Format.
Table
Alternative
tables
Take ShortMsg if
you are not shure
History
Plan
Testplan name
Start or Stop
Stand: 05.04.2012
General section
Page 93 of 148
Receiver Groups
On this page you can set up receiver groups and their timed receivers. They take affect at
program start and whenever the configuration is reloaded (see Cycletime config reload
(secs) in section 5.2.2.1.1).
Note: Deleting a receiver group which has receivers or which is referenced by another group
is not possible. All references to a receiver group must be deleted before it can be deleted.
Figure 52
myAMC.Messenger: Config: Receiver Groups
Receiver Groups
A receiver group may contain one or more timed receivers. The timed receivers of the
selected receiver group are displayed by clicking the Timed receivers Button.
Name
Enter a unique name for this receiver group.
Comment
This is the place for a user comment and has no other affect.
NextGroupId
Here you can enter the next Receiver Group. If timed receivers of a receiver
group fail, messages will be sent to the next receiver group specified. You may
leave this field unset. In this case message processing will end with this receiver
group.
Timed receivers
Here you can add, edit and delete Timed receivers for the selected Receiver
Group.
Stand: 05.04.2012
General section
Page 94 of 148
5.2.2.3.2.1 Timed receiver

A timed receiver references a receiver with one or more physical receivers. A timed receiver
may have multiple schedules which specify at which times messages should be sent to the
receiver. The specified time ranges are only checked on the beginning of processing of a
message. If a timed receiver has no schedules, messages will be sent without a time
restriction. The list of timed receivers shows only timed receivers of the selected group.
Note: Deleting a timed receiver which has schedules is not possible. All references to a timed
receiver must be deleted before it can be deleted.
Figure 53
myAMC.Messenger: Config: Timed receiver
Each transport method has a priority attached. A priority value of 0 disabled the corresponding
transport method. Methods with higher priority (i.e. lower numeric value) are tried before
transport methods with lower priority (i.e. higher numeric value). If one of these messages
fails, all messages with the next priority level will be sent. If one message with the lowest
priority fails, the whole timed receiver will fail and the next receiver group will be used if there
is one configured.
Stand: 05.04.2012
General section
Page 95 of 148
5.2.2.3.2.2 Receiver Schedules

In this dialog you can configure the timer of a receiver. You have two possibilities to configure
time ranges:
Figure 54
myAMC.Messenger: Config: Receiver Schedules (date)
You can define a time range between two dates, e. g. 01.04.2007, 00:00:00 untill 01.05.2007,
00:00:00, as shown in Figure 54. This is only possible if you set Use date and time.
Figure 55
myAMC.Messenger: Config: Receiver Schedules (weekday)
Stand: 05.04.2012
General section
Page 96 of 148
You can define a time range between two weekdays, e. g. Monday, 00:00:00 untill Friday,
23:59:59, as shown in Figure 55. This is only possible if you set Use weekday and time.
Stand: 05.04.2012
General section
Page 97 of 148
5.2.2.4 Filter & Reactions

5.2.2.4.1 Standard filter
On this page you can set up the Standard Filters. A filter can be used to determine whether to
forward or discard messages. Standard Filters work together with Precision Filter, which can
be used to reverse the decision of the Standard Filter. The working relationship of these two
filters is described in section 0.
Figure 56
myAMC.Messenger: Config: Standard Filter
Standard filter
The list of Standard filters. Each myAMC input message should only have one matching
filter. If there are more matching filters the first matching filter as returned by the
database will be used.
Application
Here you can specify which Application should be filtered.
Severity
Here you can specify which severity should be filtered.
Stand: 05.04.2012
General section
Page 98 of 148
Category
Here you can specify which Category should be filtered.
ForwardMessage
The tick ForwardMessage specifies whether a matching message should be
further processed or simply be discarded. This field is always used together with
ApplyPrecisionFilter. See section 0 for details.
ApplyPrecisionFilter
This tick activates the processing of the myAMC precision filter. How the precision
filter works together with the Standard filter is described in chapter 0.
SuspendMode
If you click Suspend, only a configured maximum <count> of similar messages
will be sent within the configured time range.
DiscardFirst
If the tick is set only the first <count> messages in the configured time range will
be discarded. If the tick is not set the first <count> messages will be processed
and the rest will be discarded. The message <count> can be set in field
SuspendCount.
SuspendTime
Here you set up the tmespan for the suspending resp. discarding.
SuspendCount
Here you set up the number of messages to keep or wait for when in
SuspendMode.
Note: If Filter Learn Mode is switched on, new filters might be added to the database
while configuring filters with myAMC.ConfigViewer tool. These filters wont be
shown in the view Messenger / Filters & Reactions / Standard filters unless the
filters are reloaded using Refresh.
Stand: 05.04.2012
General section
Page 99 of 148
5.2.2.4.2 Precision filter

On this page you can setup Precision Filters. A precesion filter can process or discard
messages on a fine grained level. The Precision Filter always reverses the result of the
previously passed Standard Filter. The working relationship of these two filters is described in
chapter 0.
For a better overview this property page is subdivides into logical groups which are described
in the following sections.
5.2.2.4.2.1 General usage
On this page you find general information about the usage of this configuration view.
Note: A message might contain contain only a subset of the fields described below!
Numeric comparison
The following table gives an overview over possible numeric comparisons.
Off
Turns this precision filter criterion off. This criterion is not evaluated.
<
All values which are less than the selected value.
<=
All values which are less than or equal to the selected value.
==
All values which are equal to the selected value.
<>
All values which are not equal to the selected value.
>=
All values which are greater than or equal to the selected value.
>
All values which are greater than the selected value.
Textual comparison
This section defines the filter semantics for textual field values. The text expression may
contain wildcards, i.e. an asterisk <*> (zero or more characters) and question mark <?>
(one single character) as placeholder for variable text.
Active
Activates the current filter criterion.
Negate
Negates the result of the text matching process.
Case
Specifies whether the text comparison should be case-sensitive () or caseinsensitive ().
Stand: 05.04.2012
General section
Page 100 of 148
5.2.2.4.2.2 Message source

This property page provides filters regarding the message source.Only filters, which are
enabled, are used to process incoming messages.
Figure 57
myAMC.Messenger: Config: Precision Filter: Message source
Enabled
Activates or deactivates this precision filter.
Poolname
Name of the pool the message originates from.
Role
Here you can specify which role should be filtered, (for future use).
Group
Name of the group the message originates from.
System
Name of the system the message originates from.
Host
Name of the host the message originates from.
Stand: 05.04.2012
General section
Page 101 of 148
Instance
Name of the instance of service the message originates from. (for future use).
Application
Application, which sent the message.Here you can enter all applications defined in the
property page Messenger / Advanced / Applications (see chapter 5.2.2.7.1). When using
a compare-parameter other than <==>, you need to know the numeric application ID,
which is shown in the property page Application, too.
InstanceNumber
Numeric id of the instance of service the message originates from.
Stand: 05.04.2012
General section
Page 102 of 148
5.2.2.4.2.3 Message contents

This property page provides filters regarding the message contents.
Figure 58
myAMC.Messenger: Config: precision Filter: Message contents
Severity
Possible values for the field Severity are configured in the property page Severity (see
chapter 0). When using a compare-parameter other than <==>, you need to know the
numeric severity value, which is shown in the property page Severity, too.
Priority
Here you can specify which priority should be filtered.
Category
Here you can specify which category should be filtered.
ServiceClass
Here you can specify which service class should be filtered.
ShortMessage
Here you can specify which short message should be filtered.
Stand: 05.04.2012
General section
Page 103 of 148
5.2.2.4.2.4 Message activation

This property page contains settings to control the amount of similar messages.
Figure 59
myAMC.Messenger: Config: precision Filter: Message activation
UseDate
Here you can can choose if you want to use the filter during a specific date, or you use it
recurring at specific weekdays.
Begin
Defines the start weekday of the scope.
Begin
Defines the start date of the scope and the time.
End
Defines the end weekday of the scope.
End
Defines the end date of the scope and the time.
Stand: 05.04.2012
General section
Page 104 of 148
SuspendMode
If you tick Suspend, only a configured maximum <count> of similar messages will be
sent within the configured time range.
DiscardFirst
If the tick is set only the first <count> messages in the configured time range will be
discarded. If the tick is not set the first <count> messages will be processed and the rest
will be discarded. The message <count> can be set in field SuspendCount.
SuspendTime
Here you set up the tmespan for the suspending resp. discarding.
SuspendCount
Here you set up the number of messages to keep or wait for when in SuspendMode.
Stand: 05.04.2012
General section
Page 105 of 148
5.2.2.4.2.5 Other
This page contains severy rarely used filter fields.
Figure 60
myAMC.Messanger: Config: Precision Filter: Other
SymbolicRole
Here you can specify which symbolic role should be filtered.
SymbolicGroup
Here you can specify which symbolic group should be filtered.
SymbolicSystem
Here you can specify which symbolic system should be filtered.
SymbolicHost
Here you can specify which symbolic host should be filtered.
SymbolicInstance
Here you can specify which symbolic instance should be filtered.
Class
Here you can specify which class should be filtered. The alert classes of the
myAMC.R/3 Agent resp. myAMC.LNI SNMP manager are:
General section
Page 106 of 148
Stand: 05.04.2012
Class-Number
Stand: 05.04.2012
Description
State Change
SAP System Up
SAP System Down
10
Syslog Entry (ID)
11
Frequent write to Syslog
12
Buffer
13
Enqueue
14
Rollpage
15
Trace
16
Dispatcher Queue
20
Performance Dialog
21
Performance Update
22
Performance Batch
23
Performance Spool
30
Abap Update
31
Abap Error
32
Abap Sql
41
DB Indices
42
DB Freespace
43
DB Archiver Stuck
44
DB Backup
51
Spool
52
Archive
53
General Purpose 3
54
General Purpose 4
55
General Purpose 5
56
General Purpose 6
57
General Purpose 7
58
General Purpose 8
59
General Purpose 9
60
General Purpose 10
61
General Purpose 11
62
General Purpose 12
63
General Purpose 13
64
General Purpose 14
General section
Page 107 of 148
65
Stand: 05.04.2012
General Purpose 15
General section
Page 108 of 148
5.2.2.4.2.6 The relationship of Standard Filter and Precision Filter

This section explains how the two filter types work together. For the possible combination of
the filters, the fields ForwardMessage and ApplyPrecisionFilter in the Standard filter are
responsible (see Figure 61).
Figure 61
myAMC.Messenger: Config: Relevant settings for filtering
The precision filter is only used if ApplyPrecisionFilter is enabled in the matching Standard
Filter. Otherwise the precision filter is not used for further processing of the current message
and the result of the standard filter defines whether the message is forwarded to the reaction
st
rd
or not (see 1 and 3 row in the table below).
Note: The Precision Filter always reverses the result of the previously passed Standard Filter.
ForwardMessage
field in
Standard Filter
ApplyPrecisionFilter field in
Standard Filter
or not defined or not defined
Stand: 05.04.2012
Standard Filter
is matching
No (no further
processing in
precision filter)
General section
Precision
Filter is
matching
Forward to
reaction
No
Page 109 of 148
Yes
Yes (no further

processing in
precision filter)
Yes
Stand: 05.04.2012
General section
Yes (inverts the

previous result)
Yes
No
No
Yes
Yes (inverts the

previous result)
No
No
Yes
Page 110 of 148
5.2.2.4.3 Reactions
On this page you can setup the reaction on successfully filtered messages.
For a better overview this property page is subdivided into logical groups which are described
in the following sections.
5.2.2.4.3.1 General usage

On this page you find general information about the usage of this configuration view.
Note: A message might contain contain only a subset of the fields described below!
Numeric comparison
The following table gives an overview over possible numeric comparisons.
Off
Turns this precision filter criterion off. This criterion is not evaluated.
<
All values which are less than the selected value.
<=
All values which are less than or equal to the selected value.
==
All values which are equal to the selected value.
<>
All values which are not equal to the selected value.
>=
All values which are greater than or equal to the selected value.
>
All values which are greater than the selected value.
Textual comparison
This section defines the filter semantics for textual field values. The text expression may
contain wildcards, i.e. an asterisk <*> (zero or more characters) and question mark <?>
(one single character) as placeholder for variable text.
Active
Activates the current filter criterion.
Negate
Negates the result of the text matching process.
Case
Specifies whether the text comparison should be case-sensitive () or caseinsensitive ().
Stand: 05.04.2012
General section
Page 111 of 148
5.2.2.4.3.2 Message source

This property page provides filters regarding the message source.Only filters, which are
enabled, are used to process incoming messages.
Figure 62
myAMC.Messenger: Config: Reactions: Message source
Enabled
Activates or deactivates the message reaction. A deactivated message reaction has the
same effect as if you delete the message reaction.
Enabled
Disabled
The reaction definition is enabled. If a message matches the

reaction definition it will be sent to the specified receiver group. If a
message matches more than one reaction definition, the message
will be sent to the configured receiver groups of all matching
reactions.
The reaction definition is disabled. This reaction doesnt cause
messages to be processed. This has the same effect as if you
delete the message reaction
Group
Specifies the receiver group where the message should be sent. How to configure a
receiver group is described in chapter 0.
Poolname
Name of the pool the message originates from.
Stand: 05.04.2012
General section
Page 112 of 148
Role
Here you can specify which role should be filtered, (for future use).
Group
Name of the group the message originates from.
System
Name of the system the message originates from.
Host
Name of the host the message originates from.
Instance
Name of the instance of service the message originates from. (for future use).
Application
Application, which sent the message.Here you can enter all applications defined in the
property page Messenger / Advanced / Applications (see chapter 5.2.2.7.1). When using
a compare-parameter other than <==>, you need to know the numeric application ID,
which is shown in the property page Application, too.
InstanceNumber
Numeric id of the instance of service the message originates from.
Stand: 05.04.2012
General section
Page 113 of 148
5.2.2.4.3.3 Message contents

This property page provides filters regarding the message contents.
Figure 63
myAMC.Messenger: Config: Reactions: Message contents
Severity
The possible values of this field are all severities that are configured in the property
page Messenger / Advanced / Severity, (see chapter 0). To use a compare-parameter
you must know the numeric value of the severity.
Priority
The priority of the message you want to react on.
Category
The category of the message you want to react on.
ServiceClass
The service class of the message you want to react on.
ShortMessage
The short description of the message you want to react on.
Stand: 05.04.2012
General section
Page 114 of 148
5.2.2.5 Message output
5.2.2.5.1 File
This property page contains settings required to write messages into a specified file. Changed
settings are stored by pressing the Save button of the property page. They take effect after a
restart of myAMC.Messenger.
Figure 64
myAMC.Messenger: Config: File
File
List of all configured output files. These output files can be referenced from the Physical
Receiver property page Messenger / Targets / Message Receiver (see chapter
5.2.2.3.1).
Name
Symbolic name of the output file definition. This symbolic name is used referenced from
the Physical Receiver property page Messenger / Targets / Message Receiver (see
chapter 5.2.2.3.1).
Stand: 05.04.2012
General section
Page 115 of 148
MaximumMessages
This value specifies the maximum number of messages stored in the output file. If the
number of messages stored in the output file has reached the maximum value, it is
automatically renamed to the output file name with additional extension .old. This
procedure will be repeated every time the maximum number of messages will be
reached. This feature is disabled if the maximum number of messages is set to 0.
MaximumSize
This value specifies the maximum file size in KB. If the output file has reached the
maximum file size, it is automatically renamed to the output file name with additional
extension .old. This procedure will be repeated every time the maximum file size will be
reached. This feature is disabled if the maximum file size is set to 0.
MaximumAge
This value specifies the maximum age of the output file in seconds. If the output file is
older than this value it is automatically renamed to the output file name with additional
extension .old. This procedure will be repeated every time the maximum age of the
output file will be reached. This feature is disabled if the maximum age of the output file
is set to 0.
Filename
In this field you must configure the filename of the output file. You should ensure that
there is enough space on the specified disk device.
Note: The file name is interpreted by myAMC.Messenger on its host which is not
necessarily the same as the local host. So please make sure, that the directory actually
exists and is writable.
If you use a combination of these three output file restrictions the first occurrence of one
restriction causes a new output file. Any previously created .old files are discarded, when a
new one is created.
Stand: 05.04.2012
General section
Page 116 of 148
5.2.2.5.2 Pagers
This page contains settings required in order to send messages to mobile phones via short
message service (SMS). Changed settings are stored by pressing the Save button. They only
take effect after a restart of myAMC.Messenger.
Note: Deleting a pager center which is referenced by a physical receiver is not possible. All
references to a pager center must be deleted before it can be deleted.
Note: This feature is currently only supported on Microsoft Windows platforms.
Figure 65
myAMC.Messenger: Config: Pager
A page center is the gateway for sending SMS messages into a mobile network. There should
be one pager center for each network you want to send messages to. Individual mobile
phones are addressed using the Address field in the corresponding physical receiver. See
section 0 for details.
Please ask the mobile operator of the target wireless service for the required values. Examples
are provided for several German mobile networks.
Enabled
By turning this switch on the pager center will be usable.
Name
Name of the Pager Center
Stand: 05.04.2012
General section
Page 117 of 148
Address
Phone number of the Pager Center
SenderAddress
Phone number of the sender; must be valid if you use UCP.
MaximumMessageLength
Specifies the maximum number of characters in a messages. If the message being sent
is longer than this parameter specifies, additional characters are cut off.
MaximumMessagePerCall
This setting limits the amount of messages sent during a single connection to the pager
center. This setting may limit the individual amount configured for each pager center,
too. This value affects memory usage and therefore the scalability of the server.
Pager properties
You must enter a unique name for a pager center. The phone number will be translated
using the settings of your modem configuration and must not be empty. You have to
specify the maximum number of messages the pager center accepts during one call.
Zero is used to specify an unrestricted number of messages. A GSM SMS can contain
up to 160 characters. If you use other pager systems you must enter their limits. But 160
is the maximum number of characters in this release. The short message string of a
received message can contain up to 160 characters. This message string will be sent to
the pager. If the pager system doesnt support 160 characters, the message may be cut
by the server. In this case a warning will be appended to the log file. Currently, TAP and
UCP pager centers are supported by the server. If you use a UCP pager center, you
must enter a sender address. This should be the number of your mobile phone.
Pager Center
Analogue Phone
Number
ISDN Phone Number
D1-TELEKOM
+49 (171) 2092522
+49 (171) 2521001
+49 (172) 2278020
+49 (172) 2278000
+49 (177) 1167
+49 (177) 1167
+49 (179) 7673425
+49 (179) 7673425
(T-Mobile, GSM 262-01)

D2 PRIVAT
(Vodafone, GSM 262-02)
E-Plus
(GSM 262-03)
Interkom
(O2, GSM 262-07)
Stand: 05.04.2012
General section
Page 118 of 148
5.2.2.5.3 External commands

On this property page you can set up external applications as physical receivers to forward
messages. These applications are executed by the server and should return as soon as
possible. Additionally they should not provide a graphical user interface, as this migt not be
available.
Changed settings are stored by pressing the Save button. They only take effect after a restart
of myAMC.Messenger.
Figure 66
myAMC.Messenger: Config: External commands
External command
List of defined external applications. These external applications can be used for the
configuration in the Receiver property page (see chapter 5.2.2.3.1).
Name
You must enter a unique symbolic name for an external application.
Command
Enter the complete path and executable of your external programm. The external
application will be executed by myAMC.Messenger using the shell.
Note: The command line is interpreted by myAMC.Messenger on its host which is not
necessarily the same as the local host. So please make sure, that the command actually
exists and is executable.
Stand: 05.04.2012
General section
Page 119 of 148
Check Returncode
If enabled, myAMC.Messenger expects a return code of 0 as success, any other return
code will be interpreted as failed command.
Stand: 05.04.2012
General section
Page 120 of 148
5.2.2.5.4 Tables
This property page contains settings required to write messages into an alternative history
table. Changed settings are stored by pressing the Save button. They take effect only after a
restart of myAMC.Messenger.
Figure 67
myAMC.Messenger: Config: Tables
Here you can set up your table. This is for storing your messages in the tables specified below.
Name
Symbolic name of the table. This name is referenced by Physica Receivers.
TableName
Name of the table in the database
MaximumKeepTime
Maximum time the messages are kept in the table in hours.
Note: The pre-defined tables are available by default, additional tables wont be created
automatically, but must be created manually using external tools! Additionally, there is
currently no message view for manually created tables.
Stand: 05.04.2012
General section
Page 121 of 148
5.2.2.5.5 WebServices (HTTP)

This property page contains settings required to send messages using HTTP POST request.
Changed settings are stored by pressing the Save button. They take effect only after a restart
of myAMC.Messenger.
Note: The forwarded message must be understood by the receiving WebService, so its
usually necessary to create a corresponding output style (see section 0). In case of a
FlexFrame system, the pre-defined style HTTPFlexFrame is used to forward incoming
messages to the FA WebGui.
Figure 68
myAMC.Messenger: Config: WebServices (Http)
Name
Symbolic name for this WebService. This name is referenced by Physica Receivers.
Username
Username for the HTTP connection.
Password
Password for the HTTP connection.
ProxyHost
Hostname or ip address of the proxy server.
Stand: 05.04.2012
General section
Page 122 of 148
ProxyPort
Port of the proxy server
Stand: 05.04.2012
General section
Page 123 of 148
5.2.2.5.6 Output style

In this property page you can define output styles being used by several receiver types.
Changed settings are stored by pressing the Save button.
Figure 69
myAMC.Messenger: Config: Output style
Output Styles
An output styles consists of a name and a text template, which may contain variable
parts,. It can be used for the configuration in the Receiver property page (see chapter
5.2.2.3.1).
Description
Symbolic name for the output style.
Text
Text template, which may contain variables in the form @varname@. A list of available
variables allows easy insertaion at the current cursor position.
The following table provides a list of available variables. Please note, that some fields might be
empty.
Field
Description
Address
The address of the message
Stand: 05.04.2012
General section
Page 124 of 148
Application
The Application ID as defined in Application

property page (chapter 5.2.2.7.1).
Application Name
The name of the application as defined in

Application property page (chapter 5.2.2.7.1).
Category
The category of the message.
Class
The alert class of the message.
Date
The date when myAMC.Messenger received the

message.
Group
The group of the message.
Host
The host of the message.
Instance
The instance of the message.
Instance-Number
The instance number of the message.
Numeric Info 0 9
The numeric info field 0 9 of the message.
Message Id
The unique ID of the message as shown in the

Message view.
Priority
The priority of the message.
Role
The role of the message.
Severity
The severity of the message as number.
Severity-Name
The severity of the message as text.
Short-Message
The short message of the alert.
Text Info 00 .. 09
The text info field 0 9 of the message.
Symbol Group
The symbolic group name of the message.
Symbol Host
The symbolic host name of the message.
Symbol Instance
The symbolic instance name of the message.
Symbol Role
The symbolic role name of the message.
Symbol System
The symbolic system name of the message.
System
The system of the message.
Time
The time when myAMC.Messenger received the

message.
Type
The alert type of the message as number.
Type-Name
The alert type of the message as text.
Stand: 05.04.2012
General section
Page 125 of 148
5.2.2.6 Message input

5.2.2.6.1 Trap types
In this property page you can add, edit or delete settings to interpret all types of traps from
different producers. If the messenger server receives traps which are not defined in this view
these traps are automatically added. Changed settings are stored by pressing the Save button.
Figure 70
myAMC.Messenger: Config: Trap types
TrapTypes
List of all Trap types
EnterpriseOid
The Enterprise OID defines the object id of a trap. There is no need to declare it
completely. For example to include the two trap OIDs .1.3.6.1.4.1.231.694.1 and
.1.3.6.1.4.1.231.694.2 you need only one entry with .1.3.6.1.4.1.231.694
Generic Trap number
EnterpriseOId, MajorTrapnumber and MinorTrapNumber are specifying a trap.
Setting the generic trap number to -1 includes all possible numbers of a given OId
and MinorNumber.
Specific Trap number
EnterpriseOId, MajorTrapNumber and and MinorTrapNumber are specifying a
Stand: 05.04.2012
General section
Page 126 of 148
trap. Setting the specific trap number to -1 includes all possible numbers of a
given OID und generic trap number.
ApplicationId
The application id of the incoming trap.
TrapName
This short TrapName is only used by myAMC components. May not be changed
for myAMC traps.
Display Name
This is a short comment and has no other affect.
Comment
This is a place for long user comment and has no other affect.
ProcessingMode
ProcessingMode specifies how to handle an incoming trap. The available modes
are:
Default handling: some message fields are generated automatically
Formula: a formula is used to parse the trap and create a message
Discard: the message is simply discarded
Default handling is the standard handling for new incoming traps. All variable
bindings of a trap are added as message text. All other fields are empty or
standard settings.
Applying a formula has the advantage that you can extract, interpret and modify
trap components and map them to different input fields, e.g. hostname, severity,
message and so on.
Note: Formulas are only enabled for pre-defined traps originating rom myAMC
components or with myAMC.Messenger Expert.
Formula
This field contains the input formula to be used if the trap is to be parsed using a
formula. Formulas are described in detail in in chapter 0.
Stand: 05.04.2012
General section
Page 127 of 148
5.2.2.6.2 Mail types

On this property page you can set up the incoming alerts received as emails. Similar to
incoming SNMP traps incoming mail messages can be parsed in order to extract useful
information.
Figure 71
myAMC.Messenger: Config: Mail types
DisplayName
Here you can type in a symbolic unique name.
SendHost
The sender host of an incoming email.
Sender
The sender address of an incoming email.
Receiver
The receiver address of an incoming email.
Mode
ProcessingMode defines the manner to handle a trap. The available modes are:
Default handling: some message fields are generated automatically
General section
Page 128 of 148
Stand: 05.04.2012
Formula: a formula is used to parse the trap and create a message
Discard: the message is simply discarded
Default handling is the standard handling for new incoming emails. The message body
is used as message text. All other fields are empty or standard settings.
Applying a formula has the advantage that you can extract, interpret and modify
message parts and map them to different input fields, e.g. hostname, severity, message
and so on.
Note: Formulas are only enabled for pre-defined traps originating rom myAMC
components or with myAMC.Messenger Expert.
Comment
Here you can enter a comment.
Formula
This field contains the input formula to be used if the email is to be parsed using a
formula. Formulas are described in detail in in chapter 0.
Stand: 05.04.2012
General section
Page 129 of 148
5.2.2.6.3 Patch types

On this property page you can set up how an incoming trap will modify incoming alert to show
another Application id.
Usually there is no need to extend or change the pre-configured patch types. This procedure is
usually only necessary for very specific use cases.
Figure 72
myAMC.Messenger: Config: Patch types
PatchId
Enter the application by its applicationId you want to recurve.
Formula
Here you can type in the formula needed to mofiy the application ids.
Note: Currently there is only one valid PatchId (ApplicationIds), so there is no way to create
new patch types. The one and only formula can be extended to modify additional application
ids.
Stand: 05.04.2012
General section
Page 130 of 148
5.2.2.6.4 Formulas
The myAMC.Messenger provides an universal message interface, which can be used. to
integrate SNMP Traps or emails, which are not originated by a myAMC component.
With the aid of formulas the variable bindings of a SNMP trap or email messages can be read
into myAMC.Messenger variables, processed and mapped to the common fields of a
message, such as Severity or LongMessage.
Formulas can contain loops (FOR, DO, WHILE), conditions (IF .. THEN .. ELSE .. FI),
assignments and boolean operations (NOT, AND, OR, XOR).
See chapter 4.2.1 for some example formulas.
5.2.2.6.4.1 Common Functions

Note: L usually stands for numbers of type long (32 bits, i.e. a range of -2.147.483.648 to
2.147.483.647), while S stands for string, i.e. a simple text.
The following functions can be used in myAMC.Messenger formulas to process incoming
SNMP traps:
5.2.2.6.4.1.1 Convert functions
KvtL2S(Buffer,Number) converts a number to a character string and copies it into

Buffer.
Example: KvtL2S(VarS01,VarL01);
KvtS2L(String) converts the character string specified with String and returns a
number.
Example: VarL01=KvtS2L(VarS01);
5.2.2.6.4.1.2 Character functions
ChrLGetLen(String) returns the number of characters in String.

Example: VarL01=ChrLGetLen(testtext);
ChrSUpper(Buffer) converts all characters from Buffer to uppercase.

Example: ChrSUpper(VarS01);
ChrSLower(Buffer) converts all characters from Buffer to lowercase.

Example: ChrSLower(VarS01);
ChrSCmp(String1,String2) compares String1 and String2. If they are identical the

function returns TRUE, otherwise it returns FALSE.
Example: IF(ChrSCmp(text,test))THEN FI;
ChrSICmp(String1,String2) performs a case insensitive comparison of String1 and

String2. If the strings are identical the function returns TRUE, otherwise it returns
FALSE.
Example: IF(ChrSICmp(VarS01,VarS02))THEN FI;
ChrSNCmp(String1,String2,n) compares the first <n> characters of String1 and

String2. If they are identical the function returns TRUE, otherwise it returns FALSE.
Example: IF(ChrSNCmp(VarS01,VarS02,5))THEN FI;
ChrSNICmp(String1,String2,n) performs a case insensitive comparision of the first <n>

characters of String1 and String2. If they are identical the function returns TRUE,
Stand: 05.04.2012
General section
Page 131 of 148
otherwise it returns FALSE.
Example: IF(ChrSNICmp(VarS01,VarS02,VarL01))THEN FI;
ChrSFind(String1,String2) returns TRUE, if String2 is contained in in String1,

otherwise the function returns FALSE.
Example: IF(ChrSFind (VarS01,test))THEN FI;
ChrSAdd(Buffer,String) appends String to Buffer.

Example: ChrSAdd(VarS01,bla);
ChrSReplace(Buffer, String1,String2) replaces String1 in Buffer with String2.

Example: IF(ChrSReplace(VarS01,test,text))THEN FI;
ChrSNoControl(Buffer,Character) replaces all non-printable characters with Character.

Example: ChrSNoControl(VarS01,_);
ChrSGetChar(Buffer,String,n) copies the character on position <n> from String to

Buffer. The position starts beginning with 0.
Example: ChrSGetChar(VarS01,testtext,5);
ChrSCopyArea(Buffer,String,Start,n) copies <n> characters on position Start from

String to Buffer.
Example: ChrSCopyArea(VarS01,bla bla,0,2);
5.2.2.6.4.1.3 Date and time functions
DateLGetAktSec() returns the number of seconds elapsed since midnight

(00:00:00), January 1, 1970, coordinated universal time, according to the
system clock.
Example: VarL01=DateLGetAktSec();
DateLSecToDateLoc(DateBuffer,TimeBuffer,Seconds) copies the local date to

DateBuffer and local time to TimeBuffer. Seconds is the output from
DateLGetAktSec(). On error the function returns FALSE, otherwise TRUE.
Example: IF(DateLSecToDateLoc (VarS01,VarS02,VarL01))THEN FI;
DateLSecToDateGm (DateBuffer,TimeBuffer,Seconds) copies the date (in UTC) to

DateBuffer and the time (in UTC) to TimeBuffer. Seconds is the output from
DateLGetAktSec(). On error the function returns FALSE, otherwise TRUE.
Example: IF(DateLSecToDateGm(VarS01,VarS02,VarL01))THEN FI;
5.2.2.6.4.1.4 Regular expression function
ChrSExpression(Buffer,Input,Expression,Formatstring) provides the possibility of

executing regular expressions. The result will be copied to Buffer. On error the function
returns FALSE, otherwise TRUE.
Example: IF(ChrSExpression (VarS01,bla bla,(.*),($1)))THEN FI; Regular
5.2.2.6.4.1.5 Test functions
PrnLogS(String) writes a character string to the myAMC.Messenger log file.

Example: PrnLogS(testtext);
PrnLogL(Number) writes the number to the myAMC.Messenger log file.

Example: PrnLogL(1);
5.2.2.6.4.2 Functions in formuals for SNMP Trap type parsing

Stand: 05.04.2012
General section
Page 132 of 148
5.2.2.6.4.2.1 Object ID functions
DotLGetCount(Buffer,OID) returns the count of dots of a OID. On error the function

returns 0.
Example: VarL01= DotLGetCount(.1.3.6.1.4.1.4567.1.1.1.1);
DotSAdd(Buffer,OID) appends OID to Buffer. Missing dots are complemented.

Example: DotSAdd(VarS01,.1.1.3.1);
DotSGetArea(Buffer,OID,Start,n) copies <n> elements beginning with position Start of

OID to Buffer. A leading dot will be complemented. Start applies to poistion of an OID.
It allways starts with 0. On error the function returns FALSE, otherwise TRUE.
Example: IF(DotSGetArea(VarS01,.1.3.6.1.4.1,1,2))THEN . FI;
DotSPreDotDel(Buffer,OID) removes leading and succeeding dots of an OID and

copies the result to Buffer. On error the function returns FALSE, otherwise TRUE.
Example: IF(DotSPreDotDel(VarS01,VarS02))THEN VarS02=VarS01 FI;
DotSCmp(OID1,OID2) compares OID1 and OID2. If they are identical the function
returns TRUE, otherwise FALSE.
Example: IF(DotSCmp(VarS01,VarS02))THEN FI;
DotSNCmp(OID1,OID2,Count) compares the first Count elements of OID1 and OID2.

If they are identical the function returns TRUE, otherwise FALSE.
Example: IF(DotSNCmp(VarS01,VarS02,5))THEN FI;
5.2.2.6.4.2.2 SNMP functions
SnmpLGetCount() returns the number of variabel bindings of the incoming trap.

Example: VarL01=SnmpLGetCount();
SnmpSGetOidByIdx(Buffer,Index) copies the object id (OID) of a variable binding

specified with Index to Buffer. Index starts with 1. On error the function returns FALSE,
otherwise TRUE.
Example: IF(SnmpSGetOidByIdx(VarS01,1))THEN . FI;
SnmpLGetIdxByOid (OID) returns the index of a variable binding specified with OID.
On error the function returns FALSE, otherwise TRUE.
Example: VarL01=SnmpLGetIdxByOid (.1.3.6.1.4.1.4567.1.1.1.1);
SnmpSGetByIdx(Buffer,Index) copies the value of a variable binding specified with

Index to Buffer. Index starts with 1. On error the function returns FALSE, otherwise
TRUE.
Example: IF(SnmpSGetByIdx (VarS01,1))THEN . FI;
SnmpSGetByOid(Buffer,OID) copies the value of a variable binding specified with OID

to Buffer. On error the function returns FALSE, otherwise TRUE.
Example: IF(SnmpSGetByOid(VarS01,.1.3.6.1.4.1.4567.1.1.1.2))THEN . FI
SnmpLGetTypeByIdx(L) returns the type of a variable binding specified by index

beginning with 1, resp. -1 in case of an failure.
SnmpLGetTypeByOid(S) returns the type of an variable binding specified by OID,

resp. -1 in case of an failure
SnmpSGet2Oid(SSS) copies the value of two with . linked variable bindings specified
by OIDs to the buffer and returns it (in case of ASN_COUNTER64 only the part
containing the lower 32 bit is used). In case of a failure you will receive NULL.
SnmpSGetHigh64ByIdx(SL) this function complements CBSnmpSGetDataByIdx() and

can be used to retrieve the upper 32 bit of a variable bindings of type
ASN_COUNTER64.In case of an failure it will return NULL.
Stand: 05.04.2012
General section
Page 133 of 148
SnmpSGetHigh64ByOid(SS) this function complements SnmpSGetDataByOid can be

used to retrieve the upper 32 bit of a variable bindings of type ASN_COUNTER64. In
case of an failure it will return NULL.
5.2.2.6.4.3 Variables
The formula module provides 3 kinds of variables:
Variables for temporary use
Output variables
Special variables
Variables for temporary use are required for temporarily storing function results or results of
mathematical operations. They always start with the fixed string Var. The next character
specifies the variable type. L specifies a numerical variable and S a character string variable.
Valid variables are VarL00, VarL01, VarL02, VarL03, .. , VarL19 and VarS00, VarS01, VarS02,
VarS03, .. , VarS19.
th
Output variables always start with the fixed string Out. As aforementioned the 4 letter is
likewise L or S. Each output variable specifies a field of the current message.
Variable
Field name
OutLSeverity
SEVERITY
OutSSeverity
SEVERITYSTRG
OutSSymInst
SYM_INST
OutLInstNum
INSTNUM
OutSInst
INST
OutLApp
APPLICATION
OutSApp
APPSTRG
OutSSymHost
SYM_HOST
OutSHost
HOST
OutSSymSystem
SYM_SYSTEM
OutSSystem
SYSTEM
OutLType
TYPEID
OutSType
TYPESTRG
OutLClass
CLASS
OutSCat
CATEGORY
OutSSymGroup
SYM_GROUPS
OutSGroup
GROUPS
OutSSymRole
SYM_ROLE
OutSRole
Stand: 05.04.2012
ROLE
General section
Page 134 of 148
OutSShortMsg
SHORTMSG
OutSLongMsg
LONGMSG
OutLLong00
INFOLONG00
OutLLong01
INFOLONG01
OutLLong02
INFOLONG02
OutLLong03
INFOLONG03
OutLLong04
INFOLONG04
OutLLong05
INFOLONG05
OutLLong06
INFOLONG06
OutLLong07
INFOLONG07
OutLLong08
INFOLONG08
OutLLong09
INFOLONG09
OutSStrg00
INFOSTRG00
OutSStrg01
INFOSTRG01
OutSStrg02
INFOSTRG02
OutSStrg03
INFOSTRG03
OutSStrg04
INFOSTRG04
OutSStrg05
INFOSTRG05
OutSStrg06
INFOSTRG06
OutSStrg07
INFOSTRG07
OutSStrg08
INFOSTRG08
OutSStrg09
INFOSTRG09
OutSRecvType
RECVTYPE
OutSRecvSubType
RECVSUBTYPE
OutSRecvAddress
RECVADDRESS
Special variables are:
InSOid which contains the enterprise OID of the incoming trap
InLGenTrapNr which contains the generic trap number of the incoming trap
InLSpecTrapNr which holds the specific trap number of the incoming trap
InSSendHostIp which embodies the IP address of the trap sending device
OutLValid is set to 1 by default. If you want to discard a trap from within a formula you
have to set this variable to 0.
Stand: 05.04.2012
General section
Page 135 of 148
5.2.2.7 Advanced
5.2.2.7.1 Applications
In this property page you can add, edit or delete user defined applications. The application ids
from -1 to 1000 are reserved for myAMC applications.
Application ids can be used for customized trap definitions (see chapter 5.2.2.6.1 for details).
Note: This menu will only be shown if you switch to the expert mode, you can do this by
pressing the key combination ctrl + m.
Figure 73
myAMC.Messenger: Config: Application
Applications
List of defined applications which can be used for the configuration of filters.
ApplicationId
The identifier of the application.
Name
The name of the application.
Stand: 05.04.2012
General section
Page 136 of 148
5.2.2.7.2 Weekdays
Some filters accept time ranges not only as fixed time stamps but allow the specification of
weekdays. This property page allows to edit the values.
Usually there is no need to extend or change the pre-configured week days. The only
exception is localization of week day names into another language.
Figure 74
myAMC.Messenger: Config: Weekdays
Stand: 05.04.2012
General section
Page 137 of 148
5.2.2.7.3 Severities
In this property page you can add, edit or delete severities for the incoming alerts for different
applications. myAMC comes with often used severities pre-configured. Usually there is no
need to extend or change the pre-configured severites.
Figure 75
myAMC.Messenger: Config: Severities
Severity
List of all configured severities.
Severity
The numeric severity value (depends on the application which sends the
severity). The value of severity can be between -1 and 300. By convention,
severities in the range 0 to 99 are considered Normal, 100 to 199 are considered
Warning and 200 to 300 are considered Critical.
ApplicationId
The application specifying the severity.
Stand: 05.04.2012
General section
Page 138 of 148
Name
The name of the severity as it is shown in the message history view.
Stand: 05.04.2012
General section
Page 139 of 148
5.2.2.7.4 Alert types

This property page allows the configuration of Alert Types. A alert type consists of a numeric
id, a textual description and optionally a short name used in SNMP traps.
Usually there is no need to extend or change the pre-configured alert types.
Figure 76
myAMC.Messenger: Config: Alert type
Alert Type
List of configured alert types.
AlertTypeId
The identifier of the alert type (for internal use only).
Typename
The name of the alert type. For myAMC messages the alert types Command,
Alarm, Event and Log are used. If you use other trap sending applications that
use different alert types, you can configure them in this property page.
Trapname
The short name of the alert type as it is used in SNMP traps (category).
Stand: 05.04.2012
General section
Page 140 of 148
Stand: 05.04.2012
General section
Page 141 of 148
5.2.2.7.5 General Configuration

This page contains common settings for the myAMC.Messenger service. Changed settings are
stored by pressing the Save button. They only take effect after a restart of myAMC.Messenger.
This page provides a raw view of all configuration variables. Commonly used settings are
changeable from the Message Settings, Mail Settings, and Pager Settings views. Take care
when changing configuration parameters!
Figure 77
myAMC.Messenger: Config: General Configuration
5.3 Master-Slave Repository

In order to guarantee that all messages are available in the message history even in case of
database failure myAMC.Messenger can use a slave database. See chapter Fehler!
Verweisquelle konnte nicht gefunden werden. for details regarding a fault-resistant
message repository.
To use the myAMC.Messenger in master-slave mode the following steps have to be
performed:
Stand: 05.04.2012
General section
Page 142 of 148
1. The mySQL database directory should be on a local disk (e.g. /var/lib/mysql as opposed to
a network mount, e.g. /opt/myAMC/mySQLDBs on FlexFrame systems)
2. MySQL keeps data of all databases in a single directory, with one sub-directory per
database. If the master database resides on a remote file system (e.g. on a NFS mount), it
should be linked to the local database directory using a symbolic link.
Example: the master database resides on a network volume mounted on
/opt/myAMC/mySQLDBs, the local (slave) database resides in /var/lib/mysql. MySQL server is
configured to use /var/lib/mysql as base directory.
shell> ln s /opt/myAMC/mySQLDBs/messenger /var/lib/mysql/
3. Make a copy of the messenger database creation script and change the following 3 lines in
the copied sql script
drop database if exists messenger;
create database messenger;
use messenger;
to
drop database if exists messengermirror;
create database messengermirror;
use messengermirror;
4. Create the slave database
mysql u<user> p<password> < /source/to/CopyOfCreateAmcMsg.sql
5. Copy section [AMCMSG_V10] of file /root/.odbc.ini and change the following parts of the
copied section from
[AMCMSG_V10]
DSN
= AMCMSG_V10
Database
= messenger
to
[AMCMSGSLAVE_V10]
DSN
= AMCMSGSLAVE_V10
Database
= messengermirror
Note: in order to use master-slave mode, the following requirements must be met:
myAMC.Messenger and the MySQL server must run on the same node and be accessible
by MySQL tools (mysql, mysqldump) without special addressing or parameters
The database names may not be changed. The master database is called messenger,
the slave database messengermirror.
The name of the master ODBC DSN must be AMCMSG_V10.
The name of the slave ODBC DSN must be AMCMSGSLAVE_V10.
Stand: 05.04.2012
General section
Page 143 of 148
6 Troubleshooting
6.1 Debugging
6.1.1
Introduction
myAMC.Messenger writes debug information to a logfile.
The amount of information can be adjusted with the parameter LogLevel.
This debug information is needed for our developers in case of problems.
6.1.2
myAMC.Messenger Service
The parameters of the myAMC.Messenger service are described in the document General
section: Getting Started.
How to get log- and debug-information is described in the document General section: Getting
Started.
Stand: 05.04.2012
General section
Page 145 of 148
Index
Components
myAMC.Messenger Server ........................... 20
Receive interfaces
Command line ........................................... 21
Database ................................................... 21
Receive interfaces ......................................... 21
Repository ............................................... 22, 28
Configuration
Functional description
Advanced
Alert type .............................................. 140
Application ........................................... 136
General Configuration .......................... 142
Severities ............................................. 138
Weekdays ............................................ 137
Filter
Combination of myAMC Standard Filter
and myAMC Precision Filter ............. 109
Precision filter ...................................... 100
Standard filter ......................................... 98
Formulas .................................................. 131
Functions.............................................. 131
Variables .............................................. 134
Message input
Mail types ............................................. 128
Patch types .......................................... 130
Trap types ............................................ 126
Message output
External commands ............................. 119
File ....................................................... 115
Output style .......................................... 124
Pagers .................................................. 117
Tables .................................................. 121
WebServices (HTTP) ........................... 122
Messages
Alternative Message History 1-3 ............ 90
Messages ............................................... 88
Program handling ...................................... 74
Connectors ............................................. 79
Main panel ............................................. 77
Menu bar ................................................ 74
Stand: 05.04.2012
Tool Bar .................................................. 78

Reactions ................................................. 111
Settings
Mail Settings ........................................... 84
Message Settings ................................... 82
Pager Settings ........................................ 86
Targets
Message Receiver ................................. 91
Physical Receiver ............................... 92
Receiver Groups .................................... 94
Timed receiver .................................... 95
Receiver Schedules ........................ 96
Introduction .................................................... 73
Getting Started
Installation ..................................................... 11
Linux .......................................................... 13
Windows .................................................... 12
myAMC.Messenger configuration ................. 15
Starting Service ............................................. 15
Reactions
Output interface ............................................. 27
Reaction types ............................................... 25
Receiver groups ............................................ 26
Structure .................................................................. 19
Troubleshooting ..................................................... 145
Usage
Example
Input formulas ............................................ 30
Output ........................................................ 67
Receiver Groups ........................................ 53
Receivertypes ............................................ 33
Funtional description
Dynamic course ......................................... 71
Filter Learn mode....................................... 71
Message group .......................................... 72
Message structure ..................................... 71
Receive interfaces
Database interface ................................. 70
Trap Receive interface ........................... 70
Receive interfaces ..................................... 70
Introduction .................................................... 29
General section
Page 146 of 148
Figures
Figure 1 myAMC.Messenger: Structure .....................................................................................................19
Figure 2 myAMC.Messenger:Filter: Workflow ............................................................................................23
Figure 3 myAMC.Messenger: Filter ............................................................................................................24
Figure 4 myAMC.Messenger: Structure .....................................................................................................29
Figure 5 Configuration: Example: Email connection ..................................................................................33
Figure 6 Configuration: Example: Receiver ................................................................................................34
Figure 7 Configuration: Example: Physical Receiver .................................................................................35
Figure 8 Configuration: Example: Receiver Group .....................................................................................36
Figure 9 Configuration: Example: Members of the Receiver Group ..........................................................37
Figure 10
Configuration: Example: myAMC Standard Filter .....................................................................38
Figure 11
Configuration: Example: myAMC Precision Filter .....................................................................39
Figure 12
Configuration: Example: Email connection ...............................................................................41
Figure 13
Configuration: Example: Receiver ............................................................................................42
Figure 14
Configuration: Example: Physical Receiver: Email...................................................................43
Figure 15
Configuration: Example: Physical Receiver: Pager ..................................................................44
Figure 16
Configuration: Example: File definition .....................................................................................45
Figure 17
Configuration: Example: Physical Receiver: File ......................................................................46
Figure 18
Configuration: Example: External command definition .............................................................47
Figure 19
Configuration: Example: Physical Reciever External commands .............................................48
Figure 20
Configuration: Example: Physical Receiver WebService .........................................................49
Figure 21
Configuration: Example: Create the two receivers ...................................................................50
Figure 22
Configuration: Example: Create a group ..................................................................................51
Figure 23
Configuration: Example: Select the group create before ..........................................................52
Figure 24
Configuration: Example: Create groups ...................................................................................53
Figure 25
Configuration: Example: Assign receivers ................................................................................54
Figure 26
Configuration: Example: Filter dialog ........................................................................................56
Figure 27
Configuration: Example: Select the file .....................................................................................57
Figure 28
Configuration: Example: Assign a file to a receiver ..................................................................58
Figure 29
Configuration: Example: Create a group ..................................................................................59
Figure 30
Configuration: Example: Specify a reaction ..............................................................................60
Figure 31
Configuration: Example: Deactivate the filter ...........................................................................61
Figure 32
Configuration: Example: Create a precision filter .....................................................................62
Figure 33
Configuration: Example: Activate the filter ................................................................................63
Figure 34
Configuration: Example: Create two receivers .........................................................................64
Figure 35
Configuration: Example: Create two receiver filters 1 ..............................................................65
Figure 36
Configuration: Example: Create two receiver filters 2 ..............................................................66
Figure 37
Configuration: Example: Design your output style....................................................................68
Figure 38
Configuration: Example: Assign ouput style to a physical receiver ..........................................69
Figure 39
myAMC.Messenger: Config: Menu bar ....................................................................................74
Figure 40
myAMC.Messenger: Config: Controls ......................................................................................75
Figure 41
myAMC.Messenger: Main panel...............................................................................................77
Figure 42
myAMC.Messenger: Config: Tool Bar ......................................................................................78
Figure 43
myAMC.Messenger: Config: Connectors .................................................................................79
Figure 44
myAMC.Messenger: Config: Message Settings .......................................................................82
Figure 45
myAMC.Messenger: Config: Mail Settings ...............................................................................84
Figure 46
myAMC.Messenger: Config: Basic message forwarding .........................................................85
Figure 47
myAMC.Messenger: Config: Pager Settings ............................................................................86
Figure 48
myAMC.Messenger: Config: Messages ...................................................................................88
Figure 49
myAMC.Messenger: Config: Aletrnative Message History 1-3 ................................................90
Figure 50
myAMC.Messenger: Config: Message Rceiver ........................................................................91
Figure 51
myAMC.Messenger: Config: Physical Receiver .......................................................................92
Figure 52
myAMC.Messenger: Config: Receiver Groups .........................................................................94
Figure 53
myAMC.Messenger: Config: Timed receiver ............................................................................95
Figure 54
myAMC.Messenger: Config: Receiver Schedules (date) .........................................................96
Figure 55
myAMC.Messenger: Config: Receiver Schedules (weekday) ..................................................96
Figure 56
myAMC.Messenger: Config: Standard Filter ............................................................................98
Figure 57
myAMC.Messenger: Config: Precision Filter: Message source .............................................101
Figure 58
myAMC.Messenger: Config: precision Filter: Message contents ...........................................103
Figure 59
myAMC.Messenger: Config: precision Filter: Message activation .........................................104
General section
Page 147 of 148
Stand: 05.04.2012
Figures
Figure 60
Figure 61
Figure 62
Figure 63
Figure 64
Figure 65
Figure 66
Figure 67
Figure 68
Figure 69
Figure 70
Figure 71
Figure 72
Figure 73
Figure 74
Figure 75
Figure 76
Figure 77
myAMC.Messanger: Config: Precision Filter: Other .............................................................. 106

myAMC.Messenger: Config: Relevant settings for filtering ................................................... 109
myAMC.Messenger: Config: Reactions: Message source .................................................... 112
myAMC.Messenger: Config: Reactions: Message contents ................................................. 114
myAMC.Messenger: Config: File ........................................................................................... 115
myAMC.Messenger: Config: Pager ....................................................................................... 117
myAMC.Messenger: Config: External commands ................................................................. 119
myAMC.Messenger: Config: Tables ...................................................................................... 121
myAMC.Messenger: Config: WebServices (Http) .................................................................. 122
myAMC.Messenger: Config: Output style .............................................................................. 124
myAMC.Messenger: Config: Trap types ................................................................................ 126
myAMC.Messenger: Config: Mail types ................................................................................. 128
myAMC.Messenger: Config: Patch types .............................................................................. 130
myAMC.Messenger: Config: Application ............................................................................... 136
myAMC.Messenger: Config: Weekdays ................................................................................ 137
myAMC.Messenger: Config: Severities ................................................................................. 138
myAMC.Messenger: Config: Alert type .................................................................................. 140
myAMC.Messenger: Config: General Configuration .............................................................. 142
Stand: 05.04.2012
General section
Page 148 of 148

100FF51A MyAMC - fa-messeng100FF51A - myAMC - FA-Messenger - Installation - and - Administration - Pdfer - Installation and Administration

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

100FF51A MyAMC - fa-messeng100FF51A - myAMC - FA-Messenger - Installation - and - Administration - Pdfer - Installation and Administration

Uploaded by

Copyright:

Available Formats

FA Suite V9.

1.2 Target group

1.3 Summary of contents

1.4 Notational conventions

1.5 Features in this version

An event and message management system

Easy configuration and parametrization

Definition of alert groups and escalation level

Easy integration with other myAMC components

Reduces the costs of the IT operation

Information via email, SNMP Trap, HTTP webservices or execution of arbitrary

API to connect to other management products

Master/Slaver Mesenger Service

Message History as Receivertype

1.6 Basic and extended Versions of Messenger/Robot

All features of myAMC.Messenger Basic

Fine-grained filtering using Standard and Precision Filters

Creation of arbitrary receivers and receiver groups

Time-based forwarding of messages to selected receivers and receiver groups

Creation of customized formulas to parse incoming SNMP traps or email messages

All features of myAMC.Messenger Basic and Expert

Requirements for Microsoft Windows

Microsoft SQL Server 2000 or newer or MySQL 4.1 or newer

ODBC drivers for Microsoft SQL Server or MySQL

Java JRE 1.4.2 or newer

Requirements for Linux

Novell SLES8 or newer

MySQL server 4.1 or newer

MySQL ODBC driver 3.5.1 or newer

unixODBC 2.2.2 or newer

Java JRE 1.4.2 or newer

Install myAMC.Messenger on the management host

2.3.1.1 Creating the database on an remote Server

Running the script for MySQL Server

2.3.1.2 Installation on Windows

Start the myAMC.Messenger setup

Enter the MS SQL Server password

Choose the components you want to install

Follow the instructions on the screen

You will be asked to start the configuration tool

At the end of the installation the myAMC.Messenger Server will be started.

2.3.1.2.1 Installation of myODBC on an Windows Host

Open the ODBC Administrator from the Windows Control Panel

Press <add> in the tab System DSN

Choose MySQL driver

As Windows DSN name use AMCMSG_V10

The database name is messenger

2.3.1.2.2 Installation of MySQL GUI on an Windows Host

Create start menu entry respectivly create an shortcut of MySQLgui.exe

Start, and press the Options button

Host name or IP address of the MySQL server

Press Save to permanently store the configuration

2.3.1.3 Installation on Linux

In /etc/rc.config you have to set the variable START_MYSQL=<yes> .

Set permission for user root:

grant all on *.* to <user>@<Host> identified by <password>;

mysql -u <user> -p < <sqlscript>

Warning: This command will delete an existing messenger database!

2.3.1.3.2 Installation of myODBC on Linux

2.3.1.3.3 Installation of unixODBC on Linux

2.3.1.3.4 Installation of the Messenger Server

Execute /etc/init.d/myAMC.MessengerSrv connect <user> <password>. User and password

Start Messenger by executing /etc/init.d/myAMC.MessengerSrv start

grant all on . to <user>@<Host> identified by <password>;