Management Instrumentation, Documentation and Automation System (MIDAS)

v4.4.0 Debugger Installation & Administration Guide

(Document version 1.3 - 01/18/10)

(intentionally blank page)

Table of Contents
Table of Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . III Legal Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .V Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IX

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 About This Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

2 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Information Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Routing (Hopping) Server . . . . . . . . . . . . . . . . . . . . . . . Communication Layout with HP OM Administration UI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. .. .. .. .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 .4 .5 .5 .6

3 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Technical Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 MIDAS Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 HP OM Administration UI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Permanent Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Supported HP OM Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Upgrade Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Installation Details Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Installation Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding MIDAS Debugger on the MIDAS Web Application system . . . . . . . . . . . . . . . Adding MIDAS Debugger on a MIDAS HP OM BackEnd. . . . . . . . . . . . . . . . . . . . . . . Installing MIDAS Debugger on the HP OM Test Agent System. . . . . . . . . . . . . . . . . . Adding MIDAS Debugger to Administration UI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Post Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . Registration of HP OM Test Agent System . . . . . . . . Add HP OM Test Agent to Node Group midas_debug Edit opc_adm Responsibility Matrix. . . . . . . . . . . . . . Enable Server MSI . . . . . . . . . . . . . . . . . . . . . . . . . . . MIDAS v4.4.0 and OM 9 - Problem . . . . . . . . . . . . . . HTTPS Certificates Exchange . . . . . . . . . . . . . . . . . . MIDAS Configurator . . . . . . . . . . . . . . . . . . . . . . . HP OM 9 Administration UI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. .. .. .. .. .. .. .. .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. .. .. .. .. .. .. .. .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 . 14 . 15 . 16 . 17 . 20 . 21 . 22 . 23 . 24 . 24 . 25 . 25 . 25

4 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Cleanup of MIDAS Policy Debugger Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Routing (Hopping) Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Configuration Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 MIDAS User Role Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

5 Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Launch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Interface . . . . . . . . . . . . . . . . . . Menu Details . . . . . . . . . . Test Data Browser . . . . . . Message Browser . . . . . . Message Details Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 . 34 . 35 . 36 . 36 . 37 . 37 . 37 . 37 . 37

Troubleshooting MIDAS Policy Debugger . . . . . . . . . . . . . . . . . . Before you begin: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . No Data Displayed in the Test Data Pane: . . . . . . . . . . . No Messages Displayed in the Message Browser Pane: . Tests Generate Wrong or Unexpected Messages:. . . . . .

6 About blue elephant systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Legal Notices
blue elephant systems GmbH shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material. The information herein is subject to change without notice and is provided "as is" without warranty of any kind. The entire risk arising out of the use of this information remains with recipient. In no event blue elephant systems GmbH shall be liable for any direct, consequential, incidental, special, punitive, or other damages whatsoever (including without limitation, damages for loss of business profits, business interruption or loss of business information), even if blue elephant systems GmbH has been advised of the possibility of such damages. The foregoing shall apply regardless of the negligence or other fault of either party and regardless of whether such liability sounds in contract, negligence, tort, or any other theory of legal liability, and notwithstanding any failure of essential purpose of any limited remedy. The limited warranties for blue elephant systems GmbH products are exclusively set forth in the documentation accompanying such products. Nothing herein should be construed as constituting a further or additional warranty. blue elephant systems GmbH may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: blue elephant systems GmbH Wollgrasweg 49 D-70559 Stuttgart Germany This document is protected by copyright. All rights are reserved. No part of this document may be photocopied, reproduced, or translated to another language without prior written consent of blue elephant systems GmbH. blue elephant systems is a registered trademark of blue elephant systems GmbH in Germany, other countries, or both. All other registered trademarks belong to their respective companies. Copyright blue elephant systems GmbH, 2010-2011.

MIDAS Debugger includes software developed by various open-source projects and organizations as listed below. The corresponding files and components are copyright to the corresponding organization or vendor and all rights reserved. The software files and components distributed under the open-source licenses are distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the license of the corresponding project for specific rights and limitations under the license. Depending on the license, any product derived from the products may not be called with the name of the project nor may the name of the project appear in their name, without prior written permission. For written permission, please contact the corresponding project owner by visiting the corresponding project home page as listed below. We greatly appreciate the work of those projects and try to contribute as much as possible to some of those projects in order to compensate their contributions. This product includes software developed by the Acegi System for Spring Project (http://acegisecurity.org/) This product includes software developed by the ActiveMQ project (http://activemq.org/) This product includes software developed by the Ant-Contrib project (http://sourceforge.net/projects/ant-contrib) This product includes software developed by the Antlr project (http://www.antlr2.org) This product includes software developed by the Apache Software Foundation (http://www.apache.org/). These are Ant, Batik,BCEL, Cocoon, Commons, Derby, Excalibur, FOP, Forrest, FTPServer, Jasper, Log4j, Lucene, ORO, POI, Solr, Tuscany, Velocity, Xalan, Xerces and XML RPC, XML Security. This product includes software developed by the Baekmuk project (http://kldp.net/projects/baekmuk/) This product includes software developed by the BSF project (http://jakarta.apache.org/bsf/) This product includes software developed by the dnsjava project (http://www.dnsjava.org/) This product includes software developed by the Docbook project (http://www.docbook.org/) This product includes software developed by the dom4j project (http://dom4j.org/) This product includes software developed by the Drools project (http://drools.codehaus.org/) This product also includes software developed by the dsmltools project (http://www.dsmltools.org/) This product also includes software developed by the EditArea project (http://www.cdolivet.net/editarea/) This product also includes software developed by the Exist project (http://www.exist-db.org/) This product also includes software developed by the Fins project (http://cocoondev.org/main/117-cd/29-cd.html)

VI

This product also includes software developed by the Fireflysung project (http://www.study-area.org/apt/firefly-font/) This product also includes software developed by the Groovy project (http://groovy.codehaus.org/) This product also includes software developed by the GWT project (http://code.google.com/webtoolkit/) This product also includes software developed by the ICU4C project (http://www.ibm.com/software/globalization/icu/) This product also includes software developed by the ICU4J project (http://www.ibm.com/software/globalization/icu/) This product also includes software developed by the j2ssh project (http://sourceforge.net/projects/sshtools/) This product also includes software developed by the Janino project (http://www.janino.net/) This product also includes software developed by the Jasper project (http://tomcat.apache.org/) This product also includes software developed by the Jaxen project (http://jaxen.org/) This product also includes software developed by the Jaxup project (http://klomp.org/jaxup/) This product also includes software developed by the JDOM project (http://www.jdom.org/) This product also includes software developed by the Jencks project (http://jencks.org/) This product also includes software developed by the Jetty project (http://jetty.mortbay.org/jetty/) This product also includes software developed by the JFreeChart project (http://www.jfree.org/jfreechart/) This product also includes software developed by the JPam project (http://jpam.sourceforge.net/) This product also includes software developed by the mimeutil project (http://sourceforge.net/projects/mime-util/) This product also includes software developed by the jRegistryKey project (http://sourceforge.net/projects/jregistrykey/) This product also includes software developed by the Jsch project (http://www.jcraft.com/jsch/) This product also includes software developed by the Jsdifflib project (http://snowtide.com/jsdifflib) This product also includes software developed by the Jython project (http://www.jython.org) This product also includes software developed by the MX4J project (http://mx4j.sourceforge.net) This product also includes software developed by the Netbeans CVS project (http://javacvs.netbeans.org/library)

VII

This product also includes software developed by the openadaptor project (http://www.openadaptor.org) This product also includes software developed by the Oracle JDBC project (http://www.oracle.com) This product also includes software developed by the Prefuse project (http://prefuse.org) This product also includes software developed by the Quartz project (http://www.opensymphony.com/quartz) This product also includes software developed by the Rhino project (http://www.mozilla.org/rhino) This product also includes software developed by the Sazanami project (http://sourceforge.jp/projects/efont) This product also includes software developed by the ServiceMix project (http://www.servicemix.org) This product also includes software developed by the ServingXml project (http://servingxml.sourceforge.net) This product also includes software developed by the Spring project (http://www.springframework.org) This product also includes software developed by the StaX project (https://sjsxp.dev.java.net) This product also includes software developed by the TM4J project (http://www.tm4j.org) This product also includes software developed by the util.concurrent project (http://gee.cs.oswego.edu/dl/classes/EDU/oswego/cs/dl/util/concurrent/intro.html) This product also includes software developed by the VMTools project (http://www.vmsystems.net/vmtools) This product also includes software developed by the Wrapper project (http://wrapper.tanukisoftware.org) This product also includes software developed by the XBean project (http://xbean.org) This product also includes software developed by the XIA project (http://www.jeckle.de/freeStuff/xia/) This product also includes software developed by the XML Ant Task project (http://www.oopsconsultancy.com/software/xmltask/)

VIII

Conventions
Font Style Boldface Capitalization Computer font Explanation
Words in boldface type represent programs and commands. Capitalized first letters represent company or product names. Words in computer font represent file or path names, command syntax statements, prompts or messages that appear on your screen or text you should type on your workstation or terminal. Words in italics represent variables in syntax statements or words that are emphasized in the text. Represents required elements in a syntax statement. When several elements are separated by the | symbol you must select one of the elements. Represents optional elements in a syntax statement.

Italics
{}

[]

In all examples the default installation path of MIDAS Debugger on HP-UX, Sun Solaris, Linux is displayed. It is # /opt/midas44/Furthermore, throughout this manual the HP-UX, Sun Solaris or Linux syntax is used for the central MIDAS command: # /opt/midas44/midas.sh {sub-command}

IX

(intentionally blank page)

1 Introduction
Overview
Your company's business success relies on high-quality IT services and IT infrastructure agility. To keep your IT services available and well performing, you need a proven operations management solution that gives you control over your ever-changing IT infrastructure. That solution is HP Operations Manager for HP-UX (HP OMU), Sun Solaris (HP OMS) or LINUX (HP OML). HP Operations Manager discovers, monitors, controls and reports on the availability and performance of your heterogeneous, large-scale IT environment. It consolidates information for all IT components that control your business: network, systems, storage, databases, and applications. With its service-driven approach, it shows what IT problems affect your business processes, helping you to focus on what's most important for your company's business success. In order to monitor more and more complex applications and services, policies within HP Operations Manager have become highly complex as well, making policy testing an absolute necessity. Typical issues faced by HP OM Administrators: Ideally there should be separate development, test and production environments. Need for separate test agents & machines to develop HP OM policies & instrumentation. Complicated application software cannot be easily installed. No real testing facilities available.

MIDAS Debugger simplifying the process of testing and the subsequent modification of the policy. All required steps can be performed within a single GUI window, making this an easy, repeatable task. MIDAS Debugger is an Add-On software for: MIDAS Configurator v4.2 and above HP Operations Manager 9.1 Administration UI and above Full integration: within the policy editor MIDAS Debugger GUI window can be launched. This will trigger the assignment and deployment of the policy, in its actual state, to the selected test agent. No console access to the test agent system is required. Step-through conditions using test-data (logfiles, opcsmg). A message browser is integrated into the MIDAS Debugger GUI window as well, displaying all messages generated from the actual test run. Test data is needed, but the real application does not have to be installed. Covered by the MIDAS or HP OM Administration UI user model. The following policy types are currently supported: logfile, opcmsg.

MIDAS Debugger offers:

Chapter 1: Introduction

About This Document

This document provides information about the installation, basic configuration and usage of MIDAS Debugger. Check the following web site periodically for the latest versions of all manuals: http://www.blue-elephant-systems.com There is also a knowledgebase entry listing all available installers, patches, hotfixes and manuals for each MIDAS version: http://www.blue-elephant-systems.com/kb/?View=entry&EntryID=51

Chapter 1: Introduction

2 Architecture
Overview
The following considerations should be taken into account when installing MIDAS Debugger: MIDAS Debugger requires one or more test systems. A virtualized system is enough. The MIDAS Debugger test agent system(s) must not be production systems in any way. MIDAS Debugger does not bring its own agent. Therefore, MIDAS Debugger requires that a HP OM agent is installed on each of these test systems. The HP OM agent needs to be installed prior to MIDAS Debugger! You can have multiple agent test systems. They will be placed inside the node group midas_debug. MIDAS Debugger is an Add-On product to MIDAS Configurator/HP OM 9 Administration UI and requires a separate license. HP OM 9.1 Administration UI users should note the following: In order to install MIDAS Debugger you will require two (2) installer packages: MIDAS Debugger Add-On installer for installing the Add-On on the HP OM Administration UI server, Standard MIDAS Configurator installation package for installing the Add-On on the test agent system. MIDAS Debugger consists of several modules. By rule of thumb it has to be installed on each of your MIDAS/HP OM 9 Administration UI systems and on each test agent system(s).

All necessary details will be explained in Chapter 3, Installation.

Chapter 2: Architecture

Information Flow
The following diagram (Figure 1 on page 4) gives an overview of the general information flow with MIDAS installed on separate servers. Figure 2 on page 4 shows the basic architecture in a HP OM Administration UI environment. Please note, that when you use HP OM Administration UI, the MIDAS/Administration UI WebApp system is located also on the HP OM server. Figure 1 MIDAS Debugger Basic Architecture
MIDAS WebApp system
MIDAS er Debugger l GUI incl Message Browser owser

debug policy

OMU Debug Adaptor

HP OM server OMU Message Adaptor OMU DB OMU Agent OMU Agent Adaptor HP OM test agent system OMU Server OMU Configuration Adaptor

Figure 2 MIDAS Debugger in HP Administration UI Environment

MIDAS Debugger er GUI incl l Message Browser owser

debug policy HP OM Administration UI Server

OMU Debug Adaptor

OMU Message Adaptor OMU DB

OMU Server

OMU Configuration Adaptor

OMU Agent

OMU Agent Adaptor HP OM test agent system

Chapter 2: Architecture

Communication
If you run HP OM Administration UI, see Communication Layout with HP OM Administration UI on page 6. The MIDAS Web Application system will need to talk directly to the MIDAS HP OM Backend and also to the HP OM Test Agent. The default listening port is 9661. The communication is by default HTTP based. But it can also be switched to HTTPS, which will require the exchange of the necessary certificates. The MIDAS HP OM Test Agent system will be registered on the MIDAS Web Application Server as a normal MIDAS BackEnd (identical to registering a MIDAS HP OM BackEnd system), see Figure 3 on page 5. Figure 3 Communication Layout
MIDAS Web Application Server
A HTTP/ HTTPS

MIDAS Server e.g. HP OM

HTTP/ HTTPS

9661
B

9661 HP OM Test Agent System with MIDAS Debugger

Note: the HP OM communication is not displayed here

Routing (Hopping) Server

If it is not possible (due to network restraints) that the MIDAS Web Application system can talk directly to the MIDAS HP OM Test Agent, a workaround exists, where the MIDAS HP OM server can be used as a routing (hopping) server. This routing (hopping) server solution is introduced with MIDAS v4.2. Since a port opening has to exist between the MIDAS Web Application system and the MIDAS HP OM BackEnd, it is now possible to use this system also as a routing (hopping) server. The request will be routed via this system to the HP OM Test Agent system. Therefore, no additional firewall openings are required. The following diagram shows the basic principle behind this, see (see Figure 4 on page 5). The configuration details will be explained here: Routing (Hopping) Server on page 30. Figure 4 Routing (Hopping) Server Layout
MIDAS Web Application Server
A

MIDAS Server e.g. HP OM

HTTP/ HTTPS

9661
B

X X
Firewall
Note: the HP OM communication is not displayed here

HTTP/ HTTPS

9661 HP OM Test Agent System with MIDAS Debugger

Chapter 2: Architecture

Communication Layout with HP OM Administration UI

Since the Administration UI is installed on the HP OM management server the communication layout is simpler here. If you have a separate test agent, the Administration UI will talk to it via the default port 9661,see Figure 5 on page 6. The communication is by default HTTP based. But it can also be switched to HTTPS, which will require the exchange of the necessary certificates. The HTTPS certificate exchange is explained here: HTTPS Certificates Exchange on page 25. Figure 5 Administration UI Communication Layout
HP OM Administration UI Server
A HTTP/ HTTPS

9661 HP OM Test Agent System with MIDAS Debugger

Note: the HP OM communication is not displayed here

Chapter 2: Architecture

3 Installation
This chapter covers the following topics: - Technical Requirements on page 8 - Permanent Disk Space on page 9 - Supported HP OM Agents on page 9 - Installation Prerequisites on page 10 - Upgrade Paths on page 11 - Installation Details Overview on page 12 - Installation Details on page 13 After the installation has succeeded it is necessary to perform some post installation tasks. The details can be found here: - Post Installation Tasks on page 20

Chapter 3: Installation

Technical Requirements
Depending on your installed MIDAS or HP OM Administration UI version you can find the individual technical requirements here: - for MIDAS Configurator on page 8 - for HP OM Administration UI on page 9

MIDAS Configurator
MIDAS Debugger is an Add-On software which requires MIDAS Configurator v4.2 or higher. Therefore, all system requirements of MIDAS Configurator 4.2 also have to be met. Please see the main MIDAS Configurator 4.2 Installation Guide for details. MIDAS Configurator v3 is NOT supported. MIDAS Configurator v4.0, 4.1 are NOT supported. MIDAS Debugger requires an additional licence. It comes with a instant on license which is valid for 60 days. Installation of MIDAS Debugger has to be done on: If you use MIDAS Configurator v4.2: MIDAS Debugger is a optional component included within the MIDAS Configurator installer package. No stand-alone installer is available. It is important to use the installer version which matches your MIDAS version! You can check your existing version via the following command: # /opt/midas44/midas.sh version The following line lists your exact version: [...] [echo] MIDAS version = 4.2.0 If you use MIDAS Configurator 4.3.0 you need to use MIDAS Debugger 4.3.0. On the MIDAS WebApp system1. On the MIDAS HP OM BackEnd system. On the test agent system (HP OM agent must be installed first!).

1. If the Web Application and Web Application Server modules are split across two servers, MIDAS Debugger has to be installed on BOTH systems. Note, that this is a non default setup. Generally, customers have both WebApp modules installed on the same machine.

Chapter 3: Installation

HP OM Administration UI
MIDAS Debugger is an Add-On software which requires HP OM Administration UI 9.1 or higher. Therefore, all system requirements of HP OM Administration UI 9.1 also have to be met. Please see the main Administration UI 9.1 Installation Guide for details. Configuration and Value Pack (CVP) 3.x is NOT supported. Administration UI 9.0 is NOT supported. MIDAS Debugger requires an additional licence. It comes with a instant on license which is valid for 60 days. Installation of MIDAS Debugger has to be done on: On the HP OM server running Administration UI 9.1. For this purpose use the stand-alone MIDAS Debugger Add-On 9.1.0 installer. On the test agent system (HP OM agent must be installed first!). Here you have to use the MIDAS v4.3 Product Suite installer which matches the operating system of the HP test agent system. Download location for the installer packages is: http://www.blue-elephant-systems.com Register, login and navigate to the Downloads section.

Permanent Disk Space

The installation of the MIDAS Debugger on the HP OM Test Agent system requires in regard of diskspace 1100MB.

Supported HP OM Agents
Supported platforms for the HP OM Test Agent are those, which are also supported by MIDAS Configurator. Currently these are: HP-UX, Linux, Solaris & Windows. MIDAS Debugger does not require any special HP OM agent version. All agents v.8 and above should also work with MIDAS Debugger. Older agents are not supported. WARNING: Though it is possible to use the agent on the HP OM management server itself for policy debugging purposes, we strongly disadvise from doing this. A dedicated non-productive test system should be used. The reason is, that MIDAS Debugger more or less takes fully control of this agent, for example, continuously performing (de-)assigning, (un-)deploy operations.

Chapter 3: Installation

Installation Prerequisites
On the test agent system, the HP OM agent must be installed first and registered on an HP OM server. Remember to install a 64-bit agent on a 64-bit operating system. The HP OM agent installation can be done via: MIDAS Configurator or HP OM 9 Administration UI. For details on the HP OM agent installation, see chapter SSH Based Agent Installation in the main User Guide. HP OM 8 Motif GUI, or manually. For the two latter options please see the corresponding HP OM documentation.

10

Chapter 3: Installation

Upgrade Paths
Three scenarios exist: MIDAS Configurator is not installed yet. Simply enable the checkbox for the MIDAS Debugger Add-On. Remember, that you have to select the MIDAS Debugger Add-On on all the servers you are installing (i.e. MIDAS Web Application system, HP OM server). Otherwise, follow the main MIDAS Configurator Installation Guide. For the MIDAS Debugger details see this guide. MIDAS Configurator or HP OM 9 Administration UI is already installed. This guide assumes that this is the existing setup you have. If HP OM 9 Administration UI is not installed yet, you have to install Administration UI 9.1.0 or higher first and in a second step install the MIDAS Debugger Add-On on the HP OM server and on the HP test agent system(s).

Chapter 3: Installation

11

Installation Details Overview

This section will give an overview on the installation basics for MIDAS Debugger. In order to install MIDAS Debugger you have to copy the appropriate installation binary to all target systems. Make sure that the installer is matching the target operating system. The MIDAS Debugger version must be matching your MIDAS Configurator version. HP OM 9 Administration UI users please remember that you have to download the correct MIDAS installer binaries from our website at http://www.blue-elephant-systems.com Generally, you have to download two (2) installation packages: The stand-alone MIDAS Debugger Add-On 9.1.0 installer for your HP OM Administration UI 9.1.0 server. The HP OM 9 Administration UI installer does not include the MIDAS Debugger Add-On. For the HP test agent system you need the MIDAS Configurator 4.3.0 Product Suite installer for the target operating system. With Administration UI it is recommended to perform those installations in the following sequence: Please install the MIDAS Debugger on the HP OM test agent system first. Only then install the MIDAS Debugger Add-On on your HP OM Administration UI server. Therefore, Administration UI users should first consult section: - Installing MIDAS Debugger on the HP OM Test Agent System on page 16 After that go to section: Adding MIDAS Debugger to Administration UI on page 17

12

Chapter 3: Installation

Installation Details
The installation details for each setup scenario can be found in the following sub-sections: - Adding MIDAS Debugger on the MIDAS Web Application system on page 14 - Adding MIDAS Debugger on a MIDAS HP OM BackEnd on page 15 - Installing MIDAS Debugger on the HP OM Test Agent System on page 16 - Adding MIDAS Debugger to Administration UI on page 17

Chapter 3: Installation

13

Adding MIDAS Debugger on the MIDAS Web Application system

If you want to add MIDAS Debugger to an existing installation of MIDAS Configurator, simply run through the following steps: It is important to use the same installer version of the current MIDAS Configurator version installed on the system! Check with #/opt/midas44/midas.sh version Remember to export the DISPLAY of the MIDAS system to your workstation. If necessary allow access to it by using the xhost + command. The DISPLAY variable should be set before starting the Installer. To set the temporary directory for unpacking use: # export IATEMPDIR=/directory/with/enough/space Example: # export IATEMPDIR=/tmp Start the installer via: # ./install.bin The installer will detect the existing MIDAS 4 installation and offer you to upgrade it, i.e. installing additional components. Please select UPGRADE (Figure 6 on page 14). Upgrade

Figure 6

In the product selection window, simply select the MIDAS Debugger Add-On. Product Selection

Figure 7

Finish the installation.

14

Chapter 3: Installation

Adding MIDAS Debugger on a MIDAS HP OM BackEnd

Same procedure as before. In the product selection window, simply select the MIDAS Debugger Add-On. Product Selection Figure 8

Finish the installation.

Chapter 3: Installation

15

Installing MIDAS Debugger on the HP OM Test Agent System

Remember, that the HP OM Agent has to be installed first and also registered on the HP OM server, before you can install the MIDAS Debugger there. To install MIDAS Debugger here, run through the following steps: Export the DISPLAY of the HP OM test agent system to your workstation. If necessary allow access to it by using the xhost + command. The DISPLAY variable should be set before starting the Installer. To set the temporary directory for unpacking use: # export IATEMPDIR=/directory/with/enough/space Example: # export IATEMPDIR=/tmp Start the installer via: # ./install.bin Since there is no MIDAS installation existing on the HP OM test agent system, you have to answer several installation screens: After the Welcome Screen, License Agreement, Context Help information, you will be asked if HP OM/Oracle is running in a cluster. Since it is recommended to use a dedicated and separate test agent, you can generally select no. In the product selection window, select from the MIDAS Server Tiers section OMU Agent and also the Add-On MIDAS Debugger, see Figure 9 on page 16. Product Selection

Figure 9

The rest of the setup windows is identical to those with other MIDAS installations. If in doubt see the MIDAS Configurator Installation Guide.

16

Chapter 3: Installation

Adding MIDAS Debugger to Administration UI

If you want to add MIDAS Debugger to your HP OM Administration UI server, simply run through the following steps: It is important to use the same installer version of the current Administration UI version installed on the system! Check with #/opt/OV/OMU/adminUI/adminui version Export the DISPLAY of the HP OM Administration UI server to your workstation. If necessary allow access to it by using the xhost + command. The DISPLAY variable should be set before starting the Installer. To set the temporary directory for unpacking use: # export IATEMPDIR=/directory/with/enough/space Example: # export IATEMPDIR=/tmp Start the installer via: # ./install.bin After the Welcome Screen, License Agreement, Context Help information, you will be asked if HP OM/Oracle is running in a cluster. You will be offered two installation options (see Figure 10 on page 17): Debugger Standalone: Install the MIDAS Debugger Add-On on your HP OM Administration UI server. Please note, this requires a separate HP test agent. Debugger & Agent: This will use the HP Management Server agent as the test agent (not recommended!). Figure 10Product Selection

Chapter 3: Installation

17

The next installer panel will ask you to define the port of the Derby database and the administration password, see Figure 11 on page 18. MIDAS Debugger will use it to store its information here.

Figure 11Derby DB Port & Password Settings

The next installer panel summarizes the entered information (Figure 12 on page 18). Only when you press Install the installation will take place.

Figure 12 Pre-Installation Summary

18

Chapter 3: Installation

The installer will install and compile the necessary files. When this process has completed, the next panel will ask you to enter the registration data of the separate HP OM test agent system, which was previously installed (Figure 13 on page 19). If you do not remember which settings were used, you can run on the HP test agent the command: #/opt/midas44/midas.sh backend Hostname: This is the hostname of the HP test agent system. Server Identifier: Enter the server identifer of the test agent. Usually the syntax will be like this: <hostname>_server HTTP Serverport: Enter the default port 9661, unless another port is used. HTTPS/HTTP: Select HTTP or HTTPS. Remember that HTTPS requires the exchange of the corresponding certificates. See section HTTPS Certificates Exchange on page 25 for details. Server Password: Enter the password of the MIDAS/HP test agent here.

Figure 13 Debug Agent Registration

If you have more than one HP test agent you can add those as well via the next installer panel, see Figure 14 on page 19.

Figure 14 Register more HP Test Agents

When done, close the installer by pressing Done.

Chapter 3: Installation

19

Post Installation Tasks

The post installation tasks are as follows (details will be explained below): Register the MIDAS OMU test agent system as a BackEnd on the MIDAS Web Application server. Add the HP OM agent test system to the node group midas_debug. Put the node group midas_debug in the responsibility matrix of the opc_adm user. Assign all message groups and activate them for the node group midas_debug. Enable Server MSI on the HP OM management server. MIDAS v4.4.0 and OM 9 - Problem on page 24 If encrypted communication via HTTPS was enabled, it is necessary to exchange the corresponding certificates.

NOTE: MIDAS v4.4.0 on OM 9 system: after the release it was discovered that the category midas_debug is missing. Please add this category manually.

20

Chapter 3: Installation

Registration of HP OM Test Agent System

This sub-section does not apply to HP OM Administration UI users. Every HP OM Test Agent system has to be registered on the MIDAS Web Application system as a MIDAS BackEnd system. In the MIDAS GUI, select from the Administrative Menu Servers -> List All. From the List Menu at the bottom select Add Server. In the editor window you have to enter the MIDAS HP OM Test Agent server name & settings, see Figure 15 on page 21. Server Type: For the HP OM Test Agent select Standard Server. Hostname: Short or FQDN or IP of the HP OM Test Agent. Server Identifier: Enter the identifier which was used during the installation of the MIDAS Debugger agent. If unsure run the command # /opt/midas44/midas.sh backend This will display your hostname, server identifier, ports and whether HTTPS is used or not. Password: Enter the password which protects port 9661. Protocol: By default MIDAS uses HTTP The use of HTTPS(SSL) requires the . exchange of certificates between all involved servers. Port: The default BackEnd port is 9661. Figure 15 HP OM Test Agent Registration

Chapter 3: Installation

21

Add HP OM Test Agent to Node Group midas_debug

To add the HP OM Test Agent to the node group midas_debug it is quickest to use the Locate function. From the Administrative Menu select Find -> Locate. In the Locate field select Node and in the where name field enter the hostname or part of the hostname and press the return key on your keyboard. In the results window select from the Action Menu of that node Assign Node to Node Group. In the yellow select window which will pop up enter in the Name field midas_debug and press the return key on your keyboard. In the filtered node groups area the node group midas_debug will be listed. Click on it and press OK.

A policy group midas_debug also exists, but should not be modified in any other way! It is used internally.

22

Chapter 3: Installation

Edit opc_adm Responsibility Matrix

Now you have to edit the opc_adm users responsibility matrix in order to assign the midas_debug node group to him: From the Administrative Menu select Browse -> All Users. Locate the user opc_adm and select Edit Responsibilities from his Action Menu. Inside the editor click on the Edit View button. From Available Node Groups click on the midas_debug node group. Now move it to the right hand side to Visible Node Groups by pressing the > arrow, so it appears there. Now press the >> button for Available Message Groups. All message groups will appear inside Visible Message Groups. Close the edit matrix view window with OK. Back in the main responsibility matrix editor click on the header title midas_debug. This will select the whole column, see Figure 16 on page 23.

Figure 16

Close the responsibility matrix editor via the Save button. Now you can use the MIDAS Policy Debugger within the MIDAS policy editor. For details see Chapter 5, Usage.

Chapter 3: Installation

23

Enable Server MSI

The HP OM management server feature Server MSI has to be enabled. If it is not, you can use the following command to do so: # opcsrvconfig -msi -enable It is also possible to use the MIDAS GUI. While you are connected to your MIDAS HP OM BackEnd select Server Configuration ->Management Server Configuration from the Administrative Menu. This will list the current settings, see Figure 17 on page 24. If the Server MSI is not enabled, you can do so going through the Global Action Menu selecting Edit. Figure 17 Management Server Configuration

MIDAS v4.4.0 and OM 9 - Problem

NOTE: MIDAS v4.4.0 on OM 9 system: After the release of MIDAS 4.4.0 it was discovered that the category midas_debug is missing. Please add this category manually.

24

Chapter 3: Installation

HTTPS Certificates Exchange

If the communication via the default port 9661 should use HTTPS, it is required that the correct certificates are exchanged.

MIDAS Configurator
If you use the MIDAS Configurator Product Suite, please refer to chapter HTTP/ HTTPS in the MIDAS Configurator Administration and Configuration Guide.

HP OM 9 Administration UI
If you have enabled HTTPS on the MIDAS/HP test agent system, it is necessary to exchange the MIDAS/Administration UI certificates between the servers. Please note, that certifcates here does not mean the HP OM certificates, but those used within Administration UI and MIDAS. To do so please follow the steps below: In this example we use the following two systems: MIDAS/HP test agent: starbug HP OM Administration UI server: ios For convenience, a certificate file exists on each system in MIDAS /HP test agent: /opt/midas44/conf/<serverID>.cer HP OM Administration UI: /opt/OV/OMU/adminUI/conf/<serverID>.cer On the HP OM Administration UI server (here: ios): Transfer the file /opt/OV/OMU/adminUI/conf/ios_server.cer to your MIDAS/ HP test agent to /tmp (via scp, ftp, external media, ...). Please do not modify its contents in any way. On the MIDAS/HP test agent (here: starbug): Import the ios_server.cer CA certificate on starbug into its truststore. Use the following command to do so (please note this needs to be one single command line!):
starbug #/opt/midas44/midas.sh ant -f run.mxl https_import_backend \ -Dfile=/tmp/ios_server.cer -Dbackend=ios_server

Please restart MIDAS on the MIDAS/HP test agent (here: starbug), using the following command: starbug # /opt/midas44/midas.sh clean starbug # /opt/midas44/midas.sh start

Now perform the same steps on the other system. On the MIDAS/HP test agent (here: starbug): Transfer the file /opt/midas44/conf/starbug_server.cer to your HP OM Administration server (here: ios) to /tmp.

Chapter 3: Installation

25

On the HP OM Administration UI server (here: ios): Import the starbug_server.cer CA certificate on ios into its truststore. Use the following command to do so (please note this needs to be one single command line!):
ios #/opt/OV/OMU/adminUI/adminui ant -f run.mxl https_import_backend \ -Dfile=/tmp/starbug_server.cer -Dbackend=starbug_server

Please restart the HP OM Administration UI (here: ios), using the following command: ios # /opt/OV/OMU/adminUI/adminui clean ios # /opt/OV/OMU/adminUI/adminui start

Now the HTTPS connection will work.

26

Chapter 3: Installation

4 Configuration
This chapter currently has these sections: - Cleanup of MIDAS Policy Debugger Data on page 27 - Routing (Hopping) Server on page 30 - MIDAS User Role Rights on page 32

Cleanup of MIDAS Policy Debugger Data

It is possible that not each exit from the MIDAS Policy Debugger window is a clean one. Therefore, messages might be left over, causing an incorrect message count next time the debugger window is opened. In order to remove really all traces of previous debugging sessions, a cleanup tasks exists in MIDAS, see Figure 18 on page 27. It is recommended to enable and schedule it on a nightly or weekly basis. It should be run at night, because there must be no active debugging session open. Figure 18 Debugger Cleanup Task

The task exists on the MIDAS HP OM BackEnd system. In order to locate and schedule it please perform the following tasks: Select your MIDAS HP OM BackEnd system. Click the icon Server in the Toolbar Menu. Select the direct link All Tasks or via the Administrative Menu: Browse -> All Tasks, see Figure 19 on page 28.

Chapter 4: Configuration

27

Figure 19 All Server Tasks

In order to quickly locate the use the filter function and enter there debug (Figure 20 on page 28). From the Action Menu of the task Debug Cleanup select Schedule, see Figure 20 on page 28.

Figure 20 Schedule Debug Cleanup Task

see next page

28

Chapter 4: Configuration

Inside the schedule editor you have to fill in some required fields: Under the tab properties you have to a job name, for example: MIDAS Policy Debugger cleanup. It is recommend to enter the same information in the label field. Under the tab schedule set the time when the task should be executed. The task should be run on a weekend or at night (for example at 03:15 each night, Figure 21 on page 29), when there are generally no users using the debugger function. It should not be executed during daytime.

Figure 21 Schedule Task

Chapter 4: Configuration

29

Routing (Hopping) Server

Overview
As explained in Chapter 2, Architecture, the MIDAS Web Application system has to be able to talk directly to the MIDAS OMU Agent Adaptor (port 9661 TCP). Quite often the MIDAS Web Application system will be in another network, separated from the HP OM environment by a firewall. Getting a port opened requires a lot of hassle and paper work. To solve this problem a routing (hopping) server solution is introduced with MIDAS v4.2. Since a port opening has to exist between the MIDAS Web Application system and the MIDAS HP OM BackEnd, it is now possible to use this system also as a routing (hopping) server. The request will be routed via this system to the HP OM Test Agent system. Therefore, no additional firewall openings are required. Please note, that any MIDAS Server can be used. It is not necessary that it is always a MIDAS HP OM BackEnd. The following diagram shows the basic principle behind this, see (see Figure 22 on page 30). Figure 22Routing (Hopping) Server Layout

MIDAS Web Application Server

A

MIDAS Server e.g. HP OM

HTTP/ HTTPS

9661
B

X X
Firewall
Note: the HP OM communication is not displayed here

HTTP/ HTTPS

9661 HP OM Test Agent System with MIDAS Debugger

Please note, if you want to use HTTPS, it is absolutely necessary, that all communication connections A -> B -> C are set to HTTPS. The certificates have to be exchanged accordingly along the communication line. See the main MIDAS Configuration Administration and Configuration Guide for details.

30

Chapter 4: Configuration

Configuration Details
In order to setup a routing (hopping) server the following setup sequence is important: The MIDAS Server which should take over the routing role (for example the MIDAS HP OM Server) has to be registered first as a BackEnd in the MIDAS Web Application GUI. Please make sure that this connection is working correctly. The hostname of the HP OM Test Agent System must be resolvable on that MIDAS Server (for example the MIDAS HP OM Server). HTTPS only: If HTTPS is used for the communication it is absolutely necessary, that all communication connections A -> B -> C are set to HTTPS (see the diagram - Figure 22 on page 30). The certificates have to be exchanged accordingly along the communication line. See the main MIDAS Configuration Administration and Configuration Guide for details. Now register the HP OM Test Agent in the MIDAS GUI like this: Server Type: select Routing Server here. Hostname: Enter the hostname of the HP OM Test Agent where also the MIDAS Debugger module was installed. Server Identifier: Enter the identifier of the HP OM Test Agent. If unsure use the command: # /opt/midas44/midas.sh backend It will show the server identifier. Password: Please enter the MIDAS HP OM Test Agent server password which was supplied during the installation. Routing Server Identifier: Enter the server identifier of the MIDAS Server which should take over the role as routing (hopping) server. Use the command #/opt/midas44/midas.sh backend on the to-be routing server to show the used identifier there. Protocol: HTTP or enable (X)SSL when HTTPS should be used. Port: 9661 is the default MIDAS server port. Figure 23

Chapter 4: Configuration

31

MIDAS User Role Rights

In order to give the correct access rights so users can access the MIDAS Policy Debugger it is necessary to give the following rights. Create a new role or edit an existing one: On the MIDAS Web Server enable all rights (all checkboxes) for the line: dbg:data ovo:message On the HP OM BackEnd server you have to set: ovo:node - read right in order to list debug nodes ovo:policy - set read, create, modify, remove, exec This is required for the restore point creation and its removal, policy edit and exec for debug. If you want to disallow debug, deassign the exec right.

32

Chapter 4: Configuration

5 Usage
The Policy Debugger currently supports the following policy types: logfile, opcmsg.

Launch
From inside the policy editor the MIDAS Policy Debugger can be launched. It is located under the tab Conditions, see Figure 24 on page 33. Please allow your browser to open pop-up windows for the MIDAS Web Application system. Figure 24 Launch Debugger

When the debugger window opens, a restore point is saved in the background. Once the debugger window is open, a second click on the button Debugger will bring the already opened window into the foreground. Multiple debugging session, even with the same HP OM test agent are possible.

Chapter 5: Usage

33

Interface
The MIDAS Policy Debugger window has four main areas: Menu area: Start, step through, stop the debugging process, select the HP OM Test Agent and reload policy changes from the policy editor into the MIDAS Policy Debugger window. Test Data: The Test-data browser enables you to upload, browse, annotate, and modify the contents of the file that you want to use to test the effectiveness of the new policy you are developing. Click the pane's title bar to display or hide the contents of the pane. Messages: The Policy Debugger's built-in message browser enables you to browse the messages generated by the policy you are testing on the data in the uploaded file. Click the pane's title bar to display or hide the contents of the pane. Message Details: The Policy Debugger's message-details pane enables you to view detailed information about the individual messages generated by the policy you are testing on the data in the uploaded file. Click the pane's title bar to display or hide the contents of the pane.

Figure 25 MIDAS Policy Debugger - Interface

Menu Details
The main menu offers the following functions via buttons or drop down menus, see Figure 26 on page 35: Run Debugger: Start the debug process and run it from the designated point in the test log file to the next marker; you can set markers on any line in the test file. Note that the Run option is also available from the context-sensitive menu, for example, when you right-click a line in the test data file. Step Debugger: Run the debug process one line at a time through the test file. Stop Debugger: Stop the debugging process immediately, wherever it is in the current test-data file. Note that stopping the debugger in this way clears any pattern matching you have been using in the GUI and automatically acknowledges any messages generated during the debugging process. Select Evaluation Mode: Display/hide information in the Match and Candidates columns in the Test Data pane. The Match column indicates the line number in the test file where the policy you are testing has found the first match; the Candidates column indicates any other potential matches further down the test file. The current modes are: Full, Matches only, and Do not Show Matches. Full - all conditions are shown. Matches only - only the first matched condition is shown. Please note, the following current restriction:

34

Chapter 5: Usage

 This feature is disabled if you run an older version than HP OM 8.29. HP OM 8.29-8.35 - A HP OM API bug exists resulting in an out-of-memory error after bigger match operations. It will be fixed in HP OM 8.36. Toggle Agent Logging: Switch on/off logging on the test agent. Applies to opcmsg policies only. The default setting is "On". Toggle Forwarding of Unmatched Messages: Switch on/off automatic forwarding (from the agent) of unmatched messages. Applies to opcmsg policies only. The default setting is "On". When changing this setting, a redeploy is necessary. Please select a test agent here: Select the agent that you want to use to test the currently active policy and data file; the agent drop-down list displays all the managed nodes included in the midas_debug node group, which is a special node group intended only for use with the policy debugger. Note that the list of test agents is always up to date; the Policy Debugger checks the current contents of the midas_debug node group before displaying the list of test agents for selection. Deploy Policy: Manually redeploy to the test agent the latest version of the policy you are testing. Redeployment ensures that the latest version of the policy (with any changes made during the session) is available on the designated test node. Please note, that many parallel deployments in your environment can also slow down the deployment for the test agent. MIDAS Administrator users therefore, might find that this deployment task is listed under Pending Deployments. No instrumentation is deployed. Figure 26 MIDAS Policy Debugger - Main Menu

Test Data Browser

The Test Data pane in the Policy Debugger GUI enables you view, modify, and manage all aspects of the file that you upload to test the policy you are currently developing. You can perform the following actions on the test file: Upload a real log file to use as a test file for the policy you are developing. Please note, a file can only be uploaded from your workstation, not from the HP OM management server. Make changes to the uploaded log file and see how changes affect the matches found by the policy conditions. Note that you can upload the changes immediately. Deploy changes to the policy manually and immediately. Test all of the policy or selected parts. You can see exactly where in the test-data file the new policy finds a matching entry.

Chapter 5: Usage

35

Evaluate any strings that match the newly defined conditions; the Debugger displays the first match but lists as candidates all other matches in the test file, too. Please note, that test data cannot be saved or exported from the debugger window.

If you want to test an opcmsg policy, note that the opcmsg data you upload to the Policy Debugger must be in particular form, namely: a comma-separated list, whose content and order is important. The Debugger uses the values in the comma-separated list to populate the fields and columns in the test-data section of the Policy Debugger GUI.

Message Browser
The Message Browser pane in the Policy Debugger GUI enables you view and manage the messages generated by the policy you are currently testing on the uploaded log file or opcmsg call. You can perform the following actions on the messages displayed: Filter the contents of the message pane according to various criteria, for example: severity, node name, number of duplicate message, time received, unmatched status, and so on. Configure the browser to display the latest messages. Perform an action on one or more messages, for example, acknowledge the message or set a filter. Customize the way in which the messages are displayed. Monitor the number and severity status of messages generated by the test data.

Message Details Browser

The Message Details pane in the Policy Debugger GUI enables you to view and examine the contents of the individual messages generated by the policy you are currently testing on the uploaded log file or opcmsg call.

36

Chapter 5: Usage

Troubleshooting MIDAS Policy Debugger

Occasionally, it is possible that you will run into problems when using the Policy Debugger GUI. Sometimes, problems arise because the browser itself has run into difficulties; sometimes, your expectations might not match the scope of the functionality provided. The information provided on this page aims to help you solve some of the most common problems you are likely to encounter during every-day use of the Policy Debugger GUI. Before you begin: 1. Check that you have selected a test agent from the agent drop-down list. 2. Check that you have uploaded a test-data file (for example, a log file or opcmsg file). No Data Displayed in the Test Data Pane: 1. Check that a debugging run is not currently active. During a debugging run, the Test Data pane is greyed out. 2. Check that the Policy Editor browser session has not timed out after an extended period of inactivity. The Policy Debugger session is spawned from the Policy Editor session. If the Policy Editor session times out, you must log in to the session again before you can continue to work. 3. Check that the Test Data column is visible. Right click the title bar of the Test Data pane displays a settings menu that enables you to customize the appearance of the GUI, for example, by hiding or showing individual columns. 4. Check that the Test Data pane is visible. Right click the title bar of the Test Data pane displays a settings menu that enables you to customize the appearance of the GUI, for example, by hiding or showing individual columns. No Messages Displayed in the Message Browser Pane: 1. Check that a debugging run is not currently in progress. 2. Check that the Policy Editor browser which spawned the Policy Debugger session has not timed out, for example, after an extended period of inactivity. 3. Check that the Messages pane is visible Right click the title bar of the Test Data pane displays a settings menu that enables you to customize the appearance of the GUI, for example, by hiding or showing individual columns. Tests Generate Wrong or Unexpected Messages: 1. Make sure that no policies other than the currently active one are deployed to the midas_debug node group, which contains the agent you are using for testing purposes (or manually to the test agent itself). 2. Check that the previous debugging session did not close unexpectedly and leave temporary files lying around.
Chapter 5: Usage 37

3. Check that no background jobs are scheduled to automatically acknowledge all messages generated during the debugging session. 4. Check if the acknowledged messages were downloaded to a flat file as part of a scheduled clean up. Note that some cleanup tasks are performed automatically when the Policy Debugger session closes. For example, the temporary version of the tested policy is deleted, all temporary files on the agent are removed, and the policy (and any instrumentation) are undeployed from the test agent.

38

Chapter 5: Usage

6 About blue elephant systems

blue elephant systems GmbH is a software company from Germany. Having a strong background in IT management, blue elephant systems GmbH concentrates on the development and marketing of innovative software solutions for the monitoring and control of business applications. The focus is to integrate the traditional IT management and the management of business processes. To complement its software offerings, blue elephant systems also provides the following specialized services: consulting education support services

For more information, visit blue elephant systems on the web at http://www.blue-elephant-systems.com for more information.

Chapter 6: About blue elephant systems

39

(intentionally left blank)

40

Chapter 6: About blue elephant systems