Zemona · zemona documentation pi informatik gmbh, brehmer 01.11.2007 3 5.4. supervising sap ® upgrades 29 5.5. supervising special servers 32 6. access through the w eb 33 6.1

Zemona

Zentrale Monitor-Applikation für SAP ®- und Baan-Systeme Central monitoring application for SAP ® and Baan systems

D o c u m e n t a t i o n – U s e r G u i d e

Zemona Documentation

PI Informatik GmbH, Brehmer 01.11.2007 2

Contents

1. WELCOME TO ZEMONA 4

2. INTRODUCTION TO ZEMONA 5

2.1. KEY FEATURES 5 2.2. SYSTEM REQUIREMENTS 6 2.3. BASICS OF ZEMONA 7 2.4. L ICENSING 9

3. HOW ZEMONA WORKS 10

3.1. OPERATING SYSTEM CHECKS 10 3.2. APPLICATION AND DATABASE 11 3.3. FILE SYSTEMS 12 3.4. BACKUPS 13 3.5. JOBS 13 3.6. SHORT DUMPS 13 3.7. UPDATE RECORDS 14 3.8. IDOC' S 14 3.9. USERS 14 3.10. ZEMONA LOG FILES 15

4. CONFIGURING ZEMONA 16

4.1. GLOBAL PARAMETERS 17 4.2. MESSAGE PARAMETERS 18 4.3. SERVER PARAMETERS 19 4.4. DEFINING NEW SERVERS 21 4.4.1. DEFINING SAP®

SERVERS 21 4.4.2. DEFINING BAAN SERVERS 22 4.4.3. DEFINING WEB SERVERS 22 4.4.4. DEFINING OTHER SERVERS 22 4.5. CONFIGURING A SAP® SERVER 23 4.6. CONFIGURING A BAAN SERVER 23 4.7. CONFIGURING SPECIAL SERVERS 25

5. USING ZEMONA 26

5.1. THE ZEMONA SCREEN 26 5.2. THE TOOLBAR (BUTTONS) 28 5.3. THE SERVER’S POPUP MENU 28 5.3.1. THE SCHEDULER 29



5.4. SUPERVISING SAP® UPGRADES 29 5.5. SUPERVISING SPECIAL SERVERS 32

6. ACCESS THROUGH THE WEB 33

6.1. INTERNET BROWSER ON THE PC 33 6.2. SMART PHONES 34 6.3. TEXT BASED MOBILE PHONES 36 6.4. EMAIL AND SMS* 37

7. SERVER REMOTE CONTROL 38

7.1. HOW IT WORKS ? 38 7.2. ABOUT THE SECURITY 38 7.3. INSTALLATION OF THE ZEMONA AGENT 39 7.4. WEB CLIENT REGISTRATION 39 7.5. REMOTE CONTROL 40

8. LIMITATIONS AND KNOW N PROBLEMS 42

8.1. MEMORY LIMITATIONS 42 8.2. DATABASE CHECK 42 8.3. PASSWORD PROBLEMS IN SAP SYSTEMS <= SAP R/3 4.7 43

9. SALES AND TECHNICAL SUPPORT 44

10. INDEX 45



1. Welcome to Zemona

Zemona is a monitor program to supervise SAP® servers under MS Windows.

It is even possible to guard Baan or SAP® servers under UNIX.



2. Introduction to Zemona

Usually you as a SAP® basic administrator check every morning your SAP® servers:

• Is the server running? (R/3, database)

• Is the last backup OK?

• Is there sufficient space on the disks?

• How many users are connected today?

• What about the performance?

These tasks take some time. Every day. For each server.

Zemona checks that for all your servers every minute, 24 hours a day. If a server is not available, it can send you an email (for example as SMS* onto your mobile phone), shows the problem on the monitor of your PC and writes it to the log file.

At a glance you can get an overview of the situation of all your servers

• on the PC where Zemona is running

• on each PC with an internet connection

• on a mobile phone or handheld PC with a WAP browser

*SMS: Text message

2.1. Key features

Zemona is a monitor program to supervise SAP ® servers under MS Windows.

Zemona checks in regular intervals

• the availability of the instance

• the availability of the database

• the file systems (free space)

• the last backup

• the number of active users



• the performance situation

• system parameters as swap file space, CPU load, paging, network errors

Zemona shows the results of these checks

• on the PC where Zemona is running

• on each PC with an internet connection

• on a mobile phone or handheld PC with a WAP browser

Zemona sends you an email (SMS*), if a server is no t reachable anymore.

Zemona observes an upgrade and sends an email (SMS) to you, if the upgrade program (R3up) waits for an input.

Zemona checks special servers

Zemona can check for you special servers of the SAP® environment as

• SAP®Router

• SAP®ITS

• SAP® Business Connector

• SAP® Content Server

*SMS: Text message

2.2. System Requirements

Zemona requires at least:

• MS Windows XP Professional SP2

• Pentium processor 300 MHz or faster

• 256 MB RAM or more

• At least 30 MB free disk space

Preconditions:

• read access to the file systems of the SAP® server

• Communication user account in the productive SAP client with profile SAP_ALL



Optional:

• write access to the file system of a WEB server

• availability of a SMTP server (Mail)

• an email account which sends a SMS (text message) in case of a new email

2.3. Basics of Zemona

Zemona checks in regular intervals

• the availability of the instance

• the availability of the database

• the file systems (free space)

• the last backup

• the number of active users

• the performance situation

• system parameters as swap file space, CPU load, paging, network errors

• special servers of the SAP® environment (SAPRouter, ITS etc.)

Before Zemona can regularly check your SAP ® servers, it is necessary to configure it:

• Global parameters (program language, HTML target path, URL)

• Messaging parameters (SMTP server, email addresses)

• SAPGUI parameters (path to SAPGUI.exe)

• Server parameter (server names, login data, database type, file systems)

You call the configuration dialog window by clicking the Button .

When Zemona is running, it will write all events as

• performance problems

• breakdown of a server

• problems with file systems

into

• the event list of the Zemona window

• the log file <application path>\Zemona.log

• the HTML pages for the PC (…statusPC.htm)



You can clear the event list in the program window at any time. The content of the log file is not touched with that function.

You get an overview at a glance from

• the program window

• the HTML pages for the PC (http://<your web server>/<your path>/statusPC.htm)

• the HTML pages for the handheld PC’s (http://<your web server>/<your path>/status.htm)

• the HTML pages for mobile phones (text only) (http://<your web server>/<your path>/statusTXT.htm)

Further information… …you will get in a simple list window, clicking on specified data fields in the program window as

• information about file systems

• user list

• list of performance data

• a short operating system analysis of the last few days

Logon to an server…

…by clicking on the field with the server name, then on the Button . This will start the SAPGUI and present the logon dialog window for the selected server.

You can pause Zemona

• complete

• writing of HTML

• messaging (email)

• logging

by clicking the button . With the arrow button on the right you can select, what you want to pause.

All buttons in the toolbar tell you which function they have, when you move the mouse cursor on them and wait for a second.

You can get help pressing the F1 key at any time.

Additionally Zemona can observe Baan systems (Triton) on HP-UX servers via rexecd. Using this feature completely you have to adapt an UNIX shell script and place it onto the server.

Without this script Zemona only observes UNIX (ping), file systems, users.



2.4. Licensing

After the Installation of Zemona you are running a demo version with an evaluation period of 40 days. During that time it is necessary to license the program, if you want to use it further.

You will see, that on each start of Zemona at first you will get the registration window. During the first 40 days you can decide each time, if you want to license the program now or later.

After the program is licensed, the registration window will not appear anymore.

For the licensing of the program please send us the serial number which is displayed in the registration window of Zemona (use copy and paste). You will get then your registration key from us, which contains the Zemona license for this computer where Zemona is installed and from which we got your serial number.



3. How Zemona works

Zemona is programmed with Visual Basic. It uses the ODBC interface (MS SQL Server) and functions of librfc32.dll to get data from inside the system.

Furthermore Zemona uses a remote command interface to communicate with UNIX servers.

Zemona checks all servers every time interval, e. g. 1 minute.

At first Zemona pings all servers.

Depending on the result of the ping, it performs these checks:

• Application and Database

• File systems

• Backups

• Users

• Operating System Checks

• Jobs

• Short Dumps

• Update Records

3.1. Operating System Checks

Operating System Check

At first Zemona pings all servers.

The ping function has a time out of 5 seconds.

If a server cannot be reached with the first attempt, it is pinged two times yet. That can take 15 seconds summary for the first time. Zemona remembers an unavailable Server. A server with known status unavailable is pinged only once the next times.

If it remains still unavailable, then the other system components are not checked anymore, until it will be reachable again.

The field OS is

• green, if the first ping succeeds,

• yellow, if Zemona must ping at least twice, or if the Operating System Analysis (see below!) detects any problems

• red, if the server isn't available.

Note:

A further OS check is related to the File systems which is performed later and separately.



Operating System Analysis

Every day once and after each restart of Zemona, looking back to the last three days , it analyses some parameters relating the operating system:

• CPU load

• free space in the SWAP file

• amount of paging of the system

• network errors

There is a specific database table of SAP®, which contains operating system analysis data, made by the SAP® system, and it's read by Zemona from inside the SAP® system via a SAP® login.

Zemona performs this short operating system analysis of the last three days once during each night. If values of these parameters - at least on one day - were suspect, the field OS is displayed with yellow colour. Also if the server had such problem only during one day, it is shown in the OS field during three days, because it occurred during the last three days. But if you correct a too small swap file, Zemona understands this correction, and shows the OS field green again from the next day.

Understand a yellow OS field as a hint to check the system with transaction st06!

3.2. Application and Database

Application Check

Zemona uses functions of the librfc32.dll to login into the SAP® system. This login is the first check of the application. The duration time for the login is noted and displayed graphically for the last 20 attempts.

If this check succeeds, you can be sure, that

• the SAP® system is available and working

• the server is connected to the network properly

• if users cannot connect to the server, the reason for that are problems with their front end systems and / or with the network between them and the server

The field Ap is

• green, if Zemona can login into SAP®, and the performance seems to be sufficient,

• yellow, if Zemona can login into SAP®, but the performance seems to be bad,

• red, if Zemona cannot login into SAP®.

The field Ap gets a yellow angle if the application is running with a good performance, but there is something to be checked, as

• errors in update records

• short dumps



• cancelled jobs

These checks are performed via a SAP® login from inside Zemona.

Database Check

In case you are running MS SQL Server, Zemona connects to the database via ODBC interface, and tries to read some data from a table.

In all other cases, the database check is performed via the SAP® system.

So the only difference between both methods is clear:

• the MS SQL Server database can be checked, although SAP® is not available

• other databases are valid as not available too, if SAP® is not available

3.3. File systems

Windows Systems

A standard Windows kernel function is used by Zemona to find out the actual space usage values of the file systems relating total and free space.

Therefore it is necessary that the user account, under which Zemona is running, has read access to the SAP® server file systems to be checked by Zemona.

UNIX Systems

Zemona calls via remote command shell the command df -k . The program expects the format given by HP-UX as answer.

For the remote command shell it is necessary to define the UNIX user account and password.

The field FS displays the value (in %) of the maximal used file system of the server. It is

• green, if there is enough space yet,

• yellow, if in a file system is little space

• red, if it is (nearly) full.



3.4. Backups

MS SQL Server Systems

Zemona connects via ODBC interface to the MSDB database, and reads the backup log table, to find out the status of the last backup.

The begin of the name of the backup job has to be defined in the configuration dialog of Zemona. If Zemona cannot find the word successfully in the backup log, the field Backup becomes red. This field contains the date of the checked backup.

In the case of a not properly finished backup, please check it with the Enterprise Manager of MS SQL Server!

Oracle Systems

Zemona connects via SAP® to the SAP® database and reads the log table of brarchive/brbackup.

If the return code in the backup log is greater than the defined one (default 0004), the field Backup becomes red.

In this case check the backup with transaction db12!

UNIX Systems

Zemona uses the remote command shell to perform a defined UNIX command (parameter: BackupLogCmd) to get the backup results. If the string, defined in the parameter BackupKey in the configuration dialog, cannot be found, then the field Backup becomes red. This field contains the date, found in the log file behind the string defined in the parameter BackupDatKey .

3.5. Jobs

Approximately every 20 minutes Zemona checks the status of the SAP® jobs of today. If there are jobs not properly ended, they are displayed, when you click on the Ap field in the main window. You will get a list with the status of the application. If all jobs are OK, no jobs will be displayed.

Zemona shows a yellow angle in the Ap field in case of not properly ended SAP® jobs.

Check such jobs with transaction sm37 !

3.6. Short Dumps



Approximately every 20 minutes Zemona checks if there are short dumps today. The result of this check is displayed, when you click on the Ap field in the main window. You will get a list with the status of the application.

Zemona shows a yellow angle in the Ap field in case of existing short dumps on this day.

Check the short dumps with transaction st22 !

3.7. Update Records

Approximately every 20 minutes Zemona checks if there are update records with errors. The result of this check is displayed, when you click on the Ap field in the main window. You will get a list with the status of the application. There will be displayed two values related to Update Records:

• Open update recs : Update Records of today not yet written to database

• Aborted upd.recs : Update Records with errors (date independent)

Zemona shows a yellow angle in the Ap field in case of existing update records with errors.

Check the Update Records with transaction sm13 !

3.8. IDOC's

Approximately every 20 minutes Zemona checks if there are IDOC's with status 51 today. The result of this check is displayed, when you click on the Ap field in the main window. You will get a list with the status of the application.

It is possible to configure Zemona so, that it sends an email to the defined user with the message subject, that there are IDOC's with errors. The message body contains data about the concerned IDOC's.

Zemona shows a yellow angle in the Ap field in case of existing IDoc’s with status=51 on this day.

Check the status of IDoc's with transaction bd87 !

3.9. Users

MS SQL Server Systems



Zemona connects via ODBC interface to the SAP® database, and reads the user table, to find out the number of the active users of all clients (Mandanten).

Other Database Systems

Zemona connects via SAP® to the SAP® database and reads the user table. This SAP® function delivers only the number of users of the login client.

UNIX Systems

Zemona uses the remote command shell to perform the UNIX command who to get the active users.

3.10. Zemona Log Files

The main log file of Zemona is in the program directory; the name of the current log file is Zemona.log.

You can display this file by pressing the button in the toolbar.

Note: If you define special servers, this button change to and get's an other function. Then use the arrow

key below, and select from the menu the Log File function.

Every month Zemona creates a new file. The old one is renamed to Zemona<month>.log, e. g. Zemona01.log for January. So you can check the log files of the last 12 months.

Additionally Zemona protocols the down times of the servers in a MS ACCESS database file, named Zemona.mdb in the program directory too.

The event list in the bottom of the program window is mirrored in the file events.lst. It's content is deleted by

pressing the button in the toolbar. The content of this file is only needed after a restart of Zemona to fill the list box.



4. Configuring Zemona

Before Zemona can regularly check your SAP ® servers, it is necessary to configure it:

• Global parameters (program language, HTML target path, URL)

• Messaging parameters (SMTP server, email addresses)

• SAPGUI parameters (path to SAPGUI.exe)

• Server parameters (server names, login data, database type, file systems)

You open the configuration dialog window by clicking the Button .

There select a parameter group (GLOBAL | MESSAGE | SAPGUI | Server <n>), after that select a parameter. In the field ‘Value’ you can edit the parameter value. You write the changed parameter value to the INI file by clicking on the OK button. The OK button is only active, if the displayed value was changed.

In the following chapters you will find the descriptions for the configuration of Zemona.



4.1. Global Parameters

Parameters as user name/password, login client, login language can be defined here globally. Additionally you can define these parameters for each server specifically if they are different from the global definitions. The server parameters have higher priority than global parameters, e. g. if you define these parameters for a server, the definitions in the global group are not used.

Passwords are stored encrypted but displayed decrypted.

PARAMETER CONTENT VALUES MEANING

Program language language of Zemona DE

EN

German

English

R/3 user name SAP® user account for all servers without an own account definition

<user> (service) user name in SAP®

R/3 user password Password for the user name <pswd>

R/3 login client SAP® client number <clnt>

R/3 login language SAP® login language

(depends on your installed languages)

D

E

…

German

English

…

HTML target path target path for the HTML pages on the WEB server (with finishing backslash \)

<path>\

URL URL of the HTML pages in the WEB

<url>

FileSystems File systems of the servers to be watched. You can define max. three file systems, for ex. CDE or Ccd. One letter stands for one file system, e. g. C for C$, D for D$…

CDE

Ccd

File systems C$, D$ and E$ of the SAP® server

File system C$ of the SAP® server, C$ and D$ of the database server

Backup job name MSSQL: Name or name prefix of the backup job(s)

ORA: command of brbackup, for example �

Backup%

svd

job names begin with ‘Backup’

command is ‘save and delete’

Backup RC Oracle max. return code of brbackup, which means backup=OK

<rc> for example ‘4’

Search Backups defines, if Zemona searches Oracle backups in the last month or year

Month

Year

Zemona performs once during each night a short operating system analysis of the last eight days. If values of these parameters at least on one day were suspect, the field OS is displayed with yellow colour. These parameter values you define here:

CPU Usage Yellow from %

if the CPU load was higher than this value, field OS becomes yellow

<percent cpu load>

for example '50'

SWAP FreeSpace if there is less free space in the <min free for example '250'



Yellow from MB swap file as defined here, field OS becomes yellow

MB>

Page In Yellow from Pages/h

if the system pages more than defined here, field OS becomes yellow

<max pages per hour>

for example '200000'

LAN Errors Yellow from # Errors

if occurred more network errors than defined here, field OS becomes yellow

<max LAN errors>

for example '5'

4.2. Message Parameters

In this section is described, how you configure the messaging functions of Zemona. Zemona makes differences between day and night. During the night the most enterprises are running backup and other jobs. So the network use is very intensive, and it can be, that Zemona doesn’t reach a SAP® server from time to time. Therefore you can define an email delay, which means, only if the server n-times wasn’t reachable, you will get an email/SMS.


Day definition from-to Day definition from-to <ff-tt> ff: hour when the day begins

tt: the day ends

example: 06-22

email delay day an email will be sent only if the server <n>-times wasn’t reachable during the day

<n>

email delay night as before, during the night <n>

SMTP Host Address IP address of your mail server <ip-addr> (or server address, e. g. smtp.web.com)

SMTP Login Required?

A few smtp servers require a login with username and password before sending email

0 = No

1 = Yes

In case of 1 you have to define SMTPusername and SMTPpassword

POP3 Login Required?

A few smtp servers require at first login into the pop3 server

0 = No

1 = Yes

SMTP username and password will be used

SMTP username username for smtp or pop3

SMTP password password for smtp or pop3

POP3 Host (IP-Addr) IP address of your pop3 server

<ip-addr> (or server address, e. g. pop3.web.com)

eMail Addr Admin email address of the administrator to be informed

<email>

senders email addr email address of Zemona

(the domain must exist on the SMTP server)

<email>

resp. time to log the minimal response time of a SAP® server from which Zemona writes it to the log.

<seconds> each response time greater than <seconds> will be logged by Zemona.

∅ resp. time yellow average response time, from which the server is displayed

<seconds> example: 0.5



yellow

File systems yellow %

usage of file systems, from which they are displayed yellow

<percent>

File systems red % usage of file systems, from which they are displayed red

<percent>

Defining SMTP server in Zemona configuration

If your SMTP server is in your intranet, it could be sufficient to define SMTP server address, senders email address and recipient (Email Addr Admin).

In the newer time mail servers often require a login into the SMTP server. In such case you have to define SMTP username and password, and set "SMTP Login required?" to 1.

Some mail servers additionally require a login into the pop3 server at first. In this case set "POP3 Login required?" to 1, and define the POP3 Host Address.

4.3. Server Parameters


Server Name The server name <server name>

(network name)

Name to display The displayed server name in Zemona.

<display name>

use it if you don’t want to display the real name

Use the Zemona’s Name to display for

- encrypting the server names (if you don’t want to display the real names in the WEB)

- effective using of the space of the small mobile phone displays

(the real server names (network names) may be too large…)


System name (SID) SAP® SID, SAP® system name

<SAPSID>

IP address SAP® server

IP address of the SAP® server <ip-addr>

Operating System WINNT HPUX HPUX-FTP

MS Windows 2000 HP UNIX log file via FTP

Application SAPR3 Baan

Database server Name or IP address of the database server

<ip-addr>

<srvname>

IP address

Server name

Database type database type MSSQL

ORA

OTHER

MS SQL Server

Oracle

other db servers

Database user name login account into the database

<user>



Database user passw password of the login account into the database

<pswd>

File Systems File systems of this server to be watched. You can define max. three file systems, for ex. CDE or Ccd. One letter stands for one file system, e. g. C for C$, D for D$…

see ’Global Parameters ‘

R/3 user name SAP® user account for this server

<user> (service) user name in SAP®

R/3 user password Password for the user name <pswd>

R/3 login client SAP® client number <clnt>

OS Username user name to login to UNIX system (OSTyp=HPUX)

OS User Password user password to login to UNIX system (OSTyp=HPUX)

eMail Addr Admin email address of the administrator to be informed, valid for this server

<email>

Backup job name MSSQL: Name or name prefix of the backup job

ORA: command of brbackup, for example �

HP-UX: OK-string in log file

Backup%

svd

job names begin with ‘Backup’

command is ‘save and delete’

BackupLogCmd UNIX command to get the Backup log file (OSTyp=HPUX)

e.g.: cat bck.log

lists the file bck.log

BackupDateKey string to find the date in the backup log file (OSTyp=HPUX)

e.g.: Backp from

UNIX Script path of a prepared script on the UNIX system to get complete information about application, file systems, backup, user (OSTyp=HPUX)

e.g.: ./tritest

Passwords are stored encrypted but they are displayed decrypted in Zemona.



4.4. Defining new servers

4.4.1. Defining SAP ® servers

Before defining a new SAP® server in Zemona, it would be a good idea to install the Zemona Agent on this server to be defined.

So Zemona can ask the Agent for the needed server details.

If you do not install the agent on the SAP® server, you have to define all parameter values manually.

Open the configuration dialog window by clicking the Button .

Then press the button [New Server] in the opened configuration window of Zemona. You will get a window like this (w/o data):

Please put in the second field the SAP® server name and press the [Query] button. If the Zemona Agent is installed on the server, Zemona will collect the needed data for you. If not, Zemona tries to get information w/o Zemona Agent. If it doesn't success, you have to configure the server definition by yourself.

Put in the name of the server under which it should be displayed by Zemona, into the first field “Name to Display”. If you let the field empty, the server name is used instead.



Note: Please put in the IP address additionally, if the server name cannot be resolved in your network. Then press the []Query] button again.

Press the [OK] button to save the data and close the window.

If necessary, select the newly created server in the group list box of the Zemona configuration window to define additional parameter values as user account and password. The new server is the last item in the list box.

Please create a communication user with profile SAP_ALL in your production client for Zemona.

4.4.2. Defining Baan servers

As “Application” select “Baan”.

As “Database” you can put in “TBASE” for documentation. You can let the field empty.

It is important to define the parameter „OSUser“ and „OS User Password“ after the basis definition.

Further you perform the steps described in the chapter 4.6.

4.4.3. Defining Web servers

As “Application” select “Web”.

The input fields „URL“ and „URL OK-String“ will be activated then. Please put in the URL to be guarded, e. g. “http://www.Zemona.de”. The “URL OK-String” is a string, which you attend in the respond data of the server, e. g. “Zemona gives an overview of all your servers at a glance.”

Only if this string is found on this web site, the web server is valid as “available”.

4.4.4. Defining other servers

As “Application” select “Other”.

Put in the TCP port, which has to be guarded by Zemona.

Only if Zemona successfully creates a connection over this port, the server is valid as “available”.



4.5. Configuring a SAP ® server

The following example shows you how to configure a SAP® server in Zemona.

The name of the server in this example may be SAPRO2, the OS is Windows 2000, the Database Oracle. The file systems to be observed may be C$, D$ and E$.

The minimal configuration (if there is no default configuration for username, password, client, File systems in [GLOBAL]):

Server name SAPRO2

IP address SAP® server 123.123.123.123

Operating System WINNT

Application SAPR3

Database server SAPro2

Database type ORA

SAP® System name (SID) C11

R/3 user name user1

R/3 user password 123456

R/3 login client 100

File Systems CDE

Backup job name qu%

Note:

Database user and password are only used for MS SQLServer. The access to other databases works through SAP®.

4.6. Configuring a Baan server

The following example shows you how to configure a Baan server in Zemona.

The name of the server in this example may be SBER1TR1, the OS HPUX. The method to gain the system information is Complete Script.

The minimal configuration:

Server name SBER1TR1

IP address Baan server 123.123.123.123

Operating System HPUX

Application Baan

Database type TBASE (Triton Base)

OS Username user1

OS User Password 123456

Backup job name backup successfully ended

a string to be in the log file, that indicates that the backup was OK.



BackupDateKey backup date: after that string has to be the date value

UNIX Script ./tritest This script is in the home directory of the OS user and collects all information.

Here is an example of the UNIX script:

At first we define the Baan environment:

BSE=/baan/bse

BSE_TMP=/baan/bse/tmp

PATH=/baan/bse/bin:$PATH

export BSE BSE_TMP PATH

. /etc/TIMEZONE

Then we ask Baan, how many companies exist in the system. The answer is always >0, i.e. Baan is running, otherwise not.

echo '#START BAANTEST'

qptool6.1 -q 'select count(*) from ttaad100' -c 000

echo '#END BAANTEST'

echo '#START FILESYSTEMS'

df -k

echo '#END FILESYSTEMS'

echo '#START USER'

who | wc -l

echo '#END USER'

Now we list the log file of the backup.

echo '#START BACKUP'

cat /TOOLS/bkup-sys.log

echo '#END BACKUP'

If Zemona gets in the result the first line beginning with «#START…», it decides that all necessary information is to be gained from this result set. It will not perform any further commands on the UNIX server.

Between #START BACKUP and #END BACKUP Zemona searches for the backup date (BackupDateKey) and the key for a successful backup (Backup job name).

Note:

It may be, that you have to install the tool qptool6.1 to your Baan system before. You can get this tool from your local Baan support.

In this described case Zemona gets all information with one script, e.g. with one execution of rexec.

If you don’t want to use such complete script, you can define a command to get only Baan information such as:

qptool6.1 -q 'select count(*) from ttaad100' -c 000

Zemona will get in this case information about file systems and active users by itself.



4.7. Configuring Special Servers

Under Special Servers we understand other servers than SAP® servers in the SAP® environment as

• SAP®Router

• SAP®ITS



etc.

You can define such servers to be supervised in the Zemona configuration dialog. Press the button to open

the configuration window. There press the button to get this dialog window:

Needed values are the name and the TCP port of the server. If the host name cannot be resolved (no name service in the network) put in the IP address additionally. The server type is displayed as information in the special server status window.

If you want to ping a server (or router or another active network component), type instead of a port number the word "PING".

You can select the TCP-Port via a predefined server type.



5. Using Zemona

After Zemona is configured and adapted to your environment, it works by itself.

To understand what Zemona is displaying, and If you want to see more than Zemona shows at the moment, please use the procedures described in the following chapters:

• The Zemona screen

• The Toolbar buttons_

• Supervising SAP® upgrades

• Supervising Special Servers

5.1. The Zemona screen

In this chapter you will find the descriptions of the content of the fields and the meanings of their able colours.

In the left column of the table the Name to display or - if not defined - the server name is displayed. You can

click on this field to login into this SAP® system with the button .

A right mouse click shows a popup menu with the most important functions for the selected server. This includes also the server remote control functions, if a Zemona agent is running on the server.

Zemona changes the font colour of the server names from black to dark blue, if it found a Zemona agent on the checked SAP® server.

The popup menu and Server Remote Control functions are described later in this document in separate chapter.

The OS column shows you the result of the performed ping. This result field can be green (=OK), yellow or red (=not reachable). The colour yellow can have two meanings:

• The OS is slow (Zemona tried at least twice to ping the server)

• You have to check the system relating page file, CPU usage or LAN errors (it indicates problems during the last eight days)*

Click on this filed to see a short system analysis.



* Zemona performs once during each night a short operating system analysis of the last eight days. If values of these parameters at least on one day were suspect, the field OS is displayed with yellow colour. Also if the server had such problem only during one day, it is shown in the OS field for eight days, because it occurred during the last eight days. But if you correct a too small swap file, Zemona understands this correction, and shows the OS field green again from the next day.

See a yellow OS field as a hint to check the system with transaction st06!

The Ap column shows the result of the application test. Zemona tries to login into SAP® and measures the duration time. The field can be green (=OK), yellow (=Performance problem) or red (=not available).

A reason for a yellow angle in the Ap field may be not properly ended SAP® jobs. Check such jobs with transaction sm37!

Just the same occurs if there are short dumps in the SAP® system on this day. Check this with transaction st22!

A further reason for a yellow angle in the AP field may be update records with errors. Check them with transaction sm13!

Move the mouse pointer on this field and wait, to see the average response time in the tooltip text. Click on it to see the status of the SAP® application, as jobs, short dumps etc.

The DB column shows the state of the database. It can be green or red. If you are running MS SQL Server, Zemona shows you the real state of the database, i.e. Zemona logs into the database and tries to read some data. Other databases such as Oracle are tested via the login.

The FS column displays the state of the file systems. The field can be green (=enough space), yellow (=too little space) and red (=[nearly] full). In the field is the percent value of the maximally used file system displayed. Move the mouse pointer on it and wait, to see the name of this file system in the tooltip text. Click on it to see a list of all checked file systems.

The Backup column shows you the result of the last performed backup. The field can be green (=OK), red (=backup finished with an error) or light blue (=backup is running currently). It displays the date (YYYYMMDD) of the last backup. Move the mouse pointer on it and wait, to see the name of the last backup in the tooltip text. If you are running MS SQL Server, Zemona searches for a Job with the name which is defined in the parameter BackupJobName. In case of other databases Zemona searches for a SAP® backup job with the key defined in the same parameter.

The Usr column shows the number of users logged into the system. Click on the field to see a list of the users.

The Performance column shows you a small performance graphic of the servers. The height of the marked line in the picture boxes stands for about 1 second. If you see red lines, the server wasn’t available during this time. Click on the graphic to see a list of all calculated performance values.

At the bottom of the Zemona form you see the event list . You can delete this event list when ever you want, without any effect to the log file.



5.2. The Toolbar (buttons)

With the STOP button you can halt Zemona to check the servers. The arrow button besides lets you select, what you want to halt (whole monitor, emailing, HTML creation, ...).

This button refreshes the display, between the intervals, manually.

With this button you can login into the SAP® system, on which you clicked before (the server field in the table below).

This button deletes the entries in the event list below. All entries remain in the log file.

Confirms the actual message in the title bar of the Zemona window.

Opens the option window of Zemona. See Configuring Zemona

Opens the protocol file in the notepad. The arrow key beside lets you select, what you want to see (release notes, log file, state of defined SAP® server upgrade, file systems of all servers, etc.)

This button changes its outfit and functionality if there are special servers defined. In this case use the arrow key beside to see the log file.

Opens a separate window with a list of the defined special servers and their status. If the screen of the computer symbol in the button is green, as shown, all defined special servers are available. If it is red, at least one of the servers is not working.

Opens the configuration window of Upgrade Guard. See Supervising SAP® upgrades

Shows the HTML page statusPC.htm in the Internet Explorer.

Opens this help file.

5.3. The Server’s Popup Menu

On each server field you can call a specific popup menu. The functions allow you to logon on a SAP® server, start and stop a SAP® instance, to schedule a shutdown of an instance or sending an email in case a defined time or user number 0 is reached. This is useful if you want to shutdown a SAP® instance, when no users are logged on anymore.

Other functions display reports: Down times of a server, some profile parameters or a list of the clients (Mandanten).

The remaining functions display the same overviews as a mouse click on the fields OS, Ap, FS etc.



5.3.1. The Scheduler

From the servers popup menu you can call the scheduler. This function enables you

- to shutdown a SAP® instance

- to send an email

when

- a specified time is reached

- no users are logged on anymore.

This can help you, if you want to shutdown a SAP® server because of any maintenance tasks to be performed, after all users are logged out from the system and / or after a specified time. You can select, if you want Zemona to shutdown SAP® and / or send an email.

Precondition for this feature is a properly installed and running Zemona Agent on the SAP® server.

In case of a successfully defined schedule, you see the symbol � in the Ap field of the SAP® server, so long as the schedule is active and valid.

5.4. Supervising SAP ® upgrades

Zemona observes an upgrade and sends an email (SMS*) to you, if the upgrade program (R3up) waits for an input.

Before you can use this function, you have to configure it.

Press this button to invoke the configuration window of Upgrade Guard.



Type in the required information as SAP® server and IP address. Clicking the both check boxes will fill in the path fields automatically, but you can modify the content manually.

Use the Check button to verify the field values. If there is an error, a message box will inform you about it. Otherwise (if the upgrade is already started) you get the target release of the upgrade in the upper right corner of the window.

Finally press the [OK] button.

In the Zemona main window you can check now the upgrade status with the function Display Upgrade in the

button menu of the arrow button beside the view log / special servers button.

In the Web pages for the PC you can use the Upgrade function in the menu bar to see the status of the defined upgrade.

In the status Web pages for mobile phones you will get now an additional icon ; click there to get details about the current upgrade:



The field Curr.Phase is a hyperlink. From there you can get a list of the most important upgrade phases. All successfully finished phases are displayed green, the remaining phases grey.

*SMS: Text message



5.5. Supervising Special Servers

Under Special Servers we understand other servers than SAP® servers in the SAP® environment as

• SAP®Router

• SAP®ITS



etc.

It is necessary to define some server details, before Zemona can supervise them.

If there are special servers defined, the log file button in the toolbar becomes the special server button .

If the screen of the computer symbol in the button is green, as shown, all defined special servers are available. If it is red, at least one of the servers is not working.

Press this button to see a window with the list of the special servers, as this:



6. Access through the Web

6.1. Internet Browser on the PC

If you configured a web server for Zemona, you can access the information, which produces Zemona, from any point with a standard web browser with access to the internet.

The URL is:

http://<your web server>/<your path>/statusPC.htm

You will get a screen like that:

You will get a detailed view of a server, if you click on the server name on the left hand. Here some examples of detail views (in the live web site you see some more information):



6.2. Smart Phones

To display the information on a mobile smart phone, use this URL:

http://<your web server>/<your path>/status.htm


From here you can switch to the FreeSpace (file systems) and the PerfGraf (performance graphic) view as following:



and

The link RemControl lets you jump to the remote control page, from where you can stop and start the servers, if these features are activated by you.

The link invokes the Service page, from where you can register a client (PC or Handy) to use the remote control functions.

The Help Site shows you the meanings of the remaining icons:



6.3. Text based mobile phones

Even for text based mobile phones it is possible to display the most important information of the SAP® servers. The text based views are less detailed than the other views for PC's and mobile (graphical) smart phones.

To display the information on such mobile phone, use this URL:

http://<your web server>/<your path>/statusTXT.htm


If a server has a problem (application or database), the server name becomes a hyperlink. Here you can get the details as described before. There is a detail view for all servers available, a FreeSpac (File systems) view and a PerfGraf (Performance graphic) view.

Besides the colon (:) you see the number of active users; besides the line (|) the average response time.

The date of the last backup is displayed without the year in the format MMDD.

AP means Application such as SAPR3, DB means database.

Text colours:

- green: OK - yellow: performance problems - red: error / not available

Detail View:



6.4. Email and SMS*

Zemona can send an email if

• a server is down (not reachable)

• a file system of a server is (nearly) full

• an SAP® upgrade waits for an input

• an arrived IDoc cannot be processed (status 51)

If you want to get the message as a SMS (Short Message Service) you need an email account which offers this feature. There you have to switch on the SMS notification in case of a new email.

You can define a global email address, which is valid for all (SAP®) servers and the Upgrade Guard:

- open the Zemona configuration dialog

- select the group MESSAGE

- select the Parameter eMail Addr Admin and change it’s value as desired

Additionally you can define a special address for each server which can be different from the global address. This is useful if you want to use another email address for test servers, i.e. if you don’t want to be informed via SMS about any error of a test server during the night.


- select the group SERVER <server name>

- select the Parameter eMail Addr Admin and change it’s value as desired

Relating IDoc’s it is possible to switch on or off e-mailing, and you can define a special email address, which will be used only in case of not processed IDoc’s:


- select the group SERVER <server name>

- select the Parameter CheckIDOCsEmailYes/No and change it’s value as desired

- select the Parameter CheckIDOCsEmailAdr and change it’s value as desired

Further you can completely switch off email sending in the menu of the arrow button beside the STOP button.

Defining SMTP server in Zemona configuration

If your SMTP server is in your intranet, it could be sufficient to define SMTP server address, senders email address and recipient (Email Addr Admin).

In the newer time mail servers often require a login into the SMTP server. In such case you have to define SMTP username and password, and set "SMTP Login required?" to 1.

Some mail servers additionally require a login into the pop3 server at first. In this case set "POP3 Login required?" to 1, and define the POP3 Host Address.

*SMS: Text message



7. Server Remote Control

7.1. How it works?

If you want to start and stop SAP® servers remotely with Zemona or over the internet, you have to install and run the Zemona Agent on each SAP® server.

Server Remote Control is an additional feature. All other functions of Zemona will work even if you don't install and use Zemona Agent on your SAP® servers.

The Zemona Agent is a small program (programmed in Visual Basic), which can accept specific commands from the Zemona main program over the company network via TCP. In the server popup menu in the Zemona main window you can find the functions to start and stop a server. This command is sent to the Agent, which compiles the needed command line and executes it.

If you do that over the internet, there is filled a request file. This file is read by Zemona, which generates the commands to be sent to the server agent.

7.2. About the security

What you have to do…

It is surely a high risk, to enable remote control functions over the internet, without sufficient sec urity rules.

Therefore I selected a way, which minimizes the risk, that anybody can control your servers from outside the way over Zemona. Of course the security concept of Zemona depends on the defined security options of

• your company network (firewall) - open only the needed TCP ports between Zemona and the agent: 3291 and 3292! - close these ports for internet access (from outside)

• your web server - disallow directory browsing - enable only reading files and executing scripts exception: write access for the file Auftrag.txt



(Not only) therefore the using of such functions is - as usually - at your own risk.

What Zemona does…

There are functions and algorithms integrated in Zemona and in the Zemona Agent, which should make sure, that it is unable to control the servers in any other way as defined by yourself:

• the Zemona agent knows only some Zemona-specific commands

• one part of the command line comes from Zemona, the other part is known by the agent

• the command line to stop or start a server is finally compiled by the agent

• the Zemona agent accepts only commands from the known Zemona's IP address

• the IP address is stored encrypted

using these features over the internet:

• a file Auftrag.txt collects the requests only passively on the web server (over the internet you don't get a reaction, if your client is registered or not!)

• this file has to be created manually by yourself, and you must set the write access for this file manually

• Zemona reads (and cleans) this file over the company network

• Zemona ignores requests from non-registered clients

• client registration consists of two parts, one on the web server, one in Zemona

• Zemona ignores requests older than 10 minutes

7.3. Installation of the Zemona Agent

Start the setup.exe of the installation set of Zemona Agent. Follow the instructions of the setup program.

Start the Zemona Agent from the Start - Programs - Startup folder.

After this first start of the agent it asks you for the IP address of the computer where Zemona is running. Please put in this IP address. It will be stored encrypted in the Zemona.ini file.

Now the Zemona Agent is installed and configured. It will accept commands only from the Zemona installation with the known IP address.

7.4. Web Client Registration

The client registration is necessary, if you want to use the remote control functions of Zemona over the internet. Zemona ignores all requests from non-registered Clients.



The registration consists of two parts:

1. Part one: In the internet

• In the status.htm (resp. statusPC.htm) invoke the (resp. Service) page

• There select: register client

• remember the displayed number after the step register client

2. Part two: In Zemona

• in the Zemona main window open the configuration dialog with

• There select the group CLIENTS

• Select a parameter Reg.WebClient<n>, which is not yet used

• In the value field type in the registration number, then a # and the name of the client

• press [OK] and close the configuration window

So only Zemona knows the registered clients. Over the internet the registration numbers are not available. They are only checked by Zemona. A request of a not registered client is simply ignored.

7.5. Remote Control On the SAP® server to be controlled remotely has to run the Zemona Agent.

Remote Control from the Zemona main program

In the server popup menu (right mouse click in the server name field) select the sub menu Server Control, there the function Start SAP® or Stop SAP®. If you select Stop SAP®, you will be asked, if you really want to stop the selected server.

Remote Control through the Web

Only registered web clients have the possibility to control SAP® servers remotely.

PC

In the web site menu (upper right part of the screen) select the function Control.

Smart phone

In the Web site menu (the first row on the web site) select the function (hyper link) RemCtl .



To start a server click on the field Start in the row of the server to be started. You will get a confirmation, that your request was accepted. That not means, that your request will be executed; that decides Zemona.



8. Limitations and known Problems

8.1. Memory limitations

Zemona is programmed with Visual Basic and uses Microsoft and SAP® standard libraries. Some of these library functions don’t release the allocated memory space completely. Usually this is not a problem in a dialog program because the not released memory areas are very small.

In a monitor program, which has to run over a long time without any administrator interactions, it can become a problem. This is because of the hundreds or thousands of calls of those functions during some days. The predefined memory segments for the program can become full – the program aborts.

Zemona captures these errors and tries to restart itself in the case of such error. The end of a program releases many of these system resources.

If this doesn’t succeed, you will get an error message, after it’s confirming the program aborts. The second variant is, that the program tries to run further. In the case of to small system resources such as memory segments, this cannot work. So the windows system gets into a chaotic state, until you stop the program manually.

To prevent this, Zemona restarts itself every night once. You can switch off this (and see how long Zemona will run without this help) by inserting/changing the parameter

Neustart=Nein

in the section [GLOBAL] .

Since Zemona uses directly the functions of the library librfc32.dll, and not anymore further libraries of the SAP® GUI, the releasing of RAM works better than before. But it is still recommended, to switch on this mechanism. Set the parameter to

Neustart=Ja

8.2. Database check

Zemona displays if the database is running. This works fine if your database server is the MS SQL Server. If the application is down, Zemona can check and display further the database state.

If you are running Oracle or another database server, Zemona doesn’t perform a real database check. It checks the database through the application. That means, in a situation when the application (SAP®) is down but the database is still running, Zemona will not display this, because it cannot check the database in this moment.

If you desire this function, you have to install the Zemona Agent on the SAP Server.

The number of active users which is shown by Zemona is for

MS SQL Server: users of all clients

other databases: users of the specified client

Therefore please specify your productive client in the case of Oracle and other databases, to see the active user number.



8.3. Password problems in SAP systems <= SAP R/3 4. 7

SAP systems with release SAP R/3 4.7 and earlier save passwords as capitals. SAP GUI and librfc32.dll convert therefore all passwords into capitals before sending them to the SAP system.

mySAP.ERP systems now allow passwords containing small letters too. The newest, with Zemona delivered librfc32.dll therefore don’t perform this conversion anymore.

If you let guard Zemona such older SAP systems, you must define the SAP R/3 passwords in Zemona in capital letters.



9. Sales and Technical Support

Software developer and vendor is

PI Informatik GmbH

Hertzstrasse 61, Geb. C4

D-13158 Berlin

Germany

Phone: +49 30 9177-4410

WEB addresses: www.Zemona.de

www.pi-informatik.de

Program Author:

Email address: [email protected]

http://www.sapmoni.de/

http://www.pi-informatik.de/

mailto:[email protected]



10. Index

Application Check 11

Backups 13

Basics 7

Configuration 16

Configuring a Baan server 23

Configuring a SAP server 23

Configuring Special Servers 26

Defining new SAP servers 21

Global Parameters 17

Message Parameters 18

Server Parameters 19

Database Check 12

Filesystems 12

IDOC's 14

Internet

Email and SMS 38

Internet Browser on the PC 34

Smart Phones 35

Text based mobile phones 37

Introduction 5

Jobs 13

Key features 5

Licensing 9

Limitations 43

Log Files 15

Operating System Analysis 11

Operating System Check 10

Remote Control 39

Remote Control, How to 41

Security 39

Web Client Registration 40

Zemona Agent Installation 40

Short Dumps 13

Special Servers, Supervising of 33

System Requirements 6

Update Records 14

Upgrades, Supervising SAP R/3 upgrades 30

Users 14

Zemona screen 27

Ap column 28

Backup column 28

DB column 28

event list 28

FS column 28

login 27

Number of Users column 28

OS column 27

Performance column 28

Toolbar 29

Documents

Zemona · zemona documentation pi informatik gmbh, brehmer 01.11.2007 3 5.4. supervising sap ® upgrades 29 5.5. supervising special servers 32 6. access through the w eb 33 6.1