midas inventory webapp integration - bes-worldline.com inventory/midas_4.9_inventory...2. legal...

MIDAS Inventory Web Application Integration

Version 4.9

Installation and User Guide

BLUE ELEPHANT SYSTEMS GmbH

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 shall Blue Elephant Systems GmbH 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

Zettachring 2

70567 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.

Date of Issue: 11/2014.

© BLUE ELEPHANT SYSTEMS GmbH, 2009-2014.

Software Included

MIDAS 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

2

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.

All license files can be found in the installation directory (./docs/licenses). Furthermore, a full overview of all external dependencies and license conditions is also accessible via the Web interface: HELP button -> About menu -> External Dependencies. This includes links to all projects.

This product includes software developed by the ActiveMQ project (http://activemq.org/)

This product includes software developed by the Ant project (http://ant.apache.org)

This product includes software developed by the Ant-Contrib project (http://ant-contrib.sourceforge.net)

This product includes software developed by the Antlr project (http://www.antlr2.org)

This product includes software developed by the Baekmuk project (http://kldp.net/projects/baekmuk/)

This product includes software developed by the BCEL project (http://jakarta.apache.org/bcel)

This product includes software developed by the BSF project (http://jakarta.apache.org/bsf/)

This product includes software developed by the Cocoon project (http://cocoon.apache.org)

This product includes software developed by the Commons project (http://jakarta.apache.org/commons)

This product includes software developed by the Derby project (http://db.apache.org/derby)

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.com/editarea/)

This product includes software developed by the Ehcache project (http://ehcache.org)

3

This product includes software developed by the Excalibur project (http://avalon.apache.org/excalibur)

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)

This product also includes software developed by the Firebird project (http://www.firebirdsql.org)

This product also includes software developed by the Fireflysung project (http://www.study-area.org/apt/firefly-font/)

This product includes software developed by the FOP project (http://xml.apache.org/fop)

This product includes software developed by the Forrest project (http://xml.apache.org/forrest)

This product includes software developed by the FTPserver project (http://mina.apache.org/ftpserver)

This product includes software developed by the Fugue Icons project (http://pinvoke.com)

This product includes software developed by the Gradle project (http://gradle.org)

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 includes software developed by the H2 project (http://www.h2database.com)

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.codehaus.org/)

4

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 includes software developed by the Log4j project (http://logging.apache.org/log4j)

This product includes software developed by the Lucene project (http://jakarta.apache.org/lucene)

This product includes software developed by the Mondrian project (http://mondrian.pentaho.com)

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)

This product also includes software developed by the openadaptor project (http://www.openadaptor.org)

This product includes software developed by the opencsv project (http://opencsv.sourceforge.net)

This product also includes software developed by the Oracle JDBC project (http://www.oracle.com)

This product includes software developed by the ORO project (http://jakarta.apache.org/oro)

This product includes software developed by the POI project (http://jakarta.apache.org/poi)

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)

5

This product also includes software developed by the ServiceMix project (http://servicemix.apache.org)

This product also includes software developed by the ServingXml project (http://servingxml.sourceforge.net)

This product includes software developed by the Snmp4j project (http://www.snmp4j.org)

This product includes software developed by the Smart-GWT project (http://smartclient.com/smartgwt)

This product also includes software developed by the Solr project (http://lucene.apache.org/solr)

This product also includes software developed by the Spring project (http://www.springframework.org)

This product also includes software developed by the Spring Security project (http://projects.spring.io/spring-security)

This product also includes software developed by the StaX project (https://sjsxp.dev.java.net)

This product also includes software developed by the Tuscany project (http://tuscany.apache.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 Velocity project (http://velocity.apache.org)

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 Xalan project (http://xml.apache.org/xalan-j)

This product also includes software developed by the XBean project (http://xbean.org)

This product also includes software developed by the Xerces project (http://xml.apache.org/xerces2-j)

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 RPC project (http://wa.apache.org/xmlrpc)

This product also includes software developed by the XML-Security project (http://santuario.apache.org/Java/index.html)

This product also includes software developed by the XML Ant Task project (http://www.oopsconsultancy.com/software/xmltask/)

6

7

ContentsConventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

1 Information Road Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Useful Links & Contact Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Contacting Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Communication and Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

3 Installing MIDAS Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Technical Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

MIDAS Inventory Web-Service Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

MIDAS Inventory Web Application Add-on. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Adding MIDAS Inventory to MIDAS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16New Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Post Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Enabling HTTPS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Registering the Inventory Server in the MIDAS GUI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

4 Configuring MIDAS Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Listening Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

HTTPS Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Enabling HTTPS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Certificate Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Updating MIDAS Inventory Registration Setting in MIDAS GUI. . . . . . . . . . . . . . . . . . . . . . 24

5 Using MIDAS Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Direct Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Access from within HPOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Corresponding Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Node Comparison Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Trigger Node Comparison Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Node Comparison Report Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Triggering a new Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

11

Conventions

The following typographical conventions are used in this book.

It is recommended to install MIDAS in the default home directory /opt/midas. However, you can choose to install MIDAS in an alternative directory, too. For this reason, in all examples the following default installation path is displayed for MIDAS on HP-UX, Sun Solaris, and Linux:

# /<MIDAS_HOME>/

Furthermore, throughout this manual the HP-UX, Sun Solaris, or Linux syntax is used for the central MIDAS command:

# /<MIDAS_HOME>/midas.sh {sub-command}

Font Style Explanation

Boldface Boldface words highlight important information or the first time a term is used.

Capitalization Capitalized first letters represent company or product names.

Computer font Words in computer font represent file or path names, command syntax statements, prompts or messages that appear on your screen.

Bold Computer font Words in bold computer font represent text that the user is required to input, for example, a command, the response to a command-line prompt, or in a dialog box.

Italics Words in italics represent variables in syntax statements or words that are emphasized in the text. Italics are also used to represent the title of a book.

{ } 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.

1 Information Road Map

In addition to the online help available in the Web browser during a MIDAS session, the MIDAS Product Family includes the following core user information:

• MIDAS Installation Guide

Information concerning the installation process and initial setup tasks

• MIDAS Administration & Configuration Guide

Information concerning advanced configuration, maintenance or troubleshooting

• MIDAS User Guide

Information and instructions to help you use the MIDAS software

• MIDAS Release Notes

Information about all the new features included with the current version of the MIDAS software and, in addition, a list of known problems that have been fixed

Information is also available for the following add-on products that enable you to extend the features and functionality of the MIDAS Product Family:

• MIDAS Automator

Automates the compilation and updating of your IT management configuration.

• MIDAS Analyzer

Identifies and reduces message problems with analyzing end-to-end views and views.

• API Toolkit

Extends access to APIs beyond the native HPOM capabilities by supporting various additional programming languages.

• MIDAS Debugger

Reduces the number of tools and actions required for testing policy changes.

• MIDAS Inventory

Enables the rapid identification of new or changed systems to ensure up-to-date infrastructure information.

• MIDAS Outage Manager

Simplifies the usage and management of outages with HPOM.

• MIDAS Service Builder

Provides an easy-to-use graphical interface for creating new services trees and modifying and exporting existing service trees.

• MIDAS Synchronizer

Provides ready-to-use functionality that enables you to replicate changes across multiple HPOM servers.

• boom

Monitors your entire enterprise environment with platform-independent technology.

Chapter 1: Information Road Map 12

For more information about which add-on products are available and the features and functionality they include, see the Blue Elephant Systems Web site in Useful Links & Contact Information on page 13.

As a result of regular program updates, some information in the printed manuals may differ from that found in the online help. For the same reason, there may be minor differences in the presentation of the program's interface. Most screenshots in this manual have been taken during development and may not reflect final content.

The information in this manual applies to MIDAS for HP OMU, HP OMS and HP OML and any reference throughout this manual to HPOM includes all three versions. System specific specialities are highlighted accordingly. For a general overview of the features provided with HP OMU, HP OMS and HP OML, refer to the HP Operations Manager Concepts Guide, which is available in PDF format on the HP product manual Web site (see below).

Useful Links & Contact Information

Check our home page (downloads section) for the latest version of the MIDAS manuals, whitepapers, documents, and software:

http://www.blue-elephant-systems.com

HPOM patches and documentation can be downloaded from the following Web site:

http://support.openview.hp.com/selfsolve/manuals

http://support.openview.hp.com/patches/patch_index.jsp

Contacting Customer Support

You can contact the support team from Blue Elephant Systems via:

• e-mail: [email protected]

• phone: ( +49 | 0 ) 711 400 425 55

Support Times: Mo.-Fr. from 9.00-17.00 CET (except German public holidays)

Chapter 1: Information Road Map 13

http://support.openview.hp.com/patches/patch_index.jsp


2 Architecture

MIDAS Inventory is a stand-alone product, which is installed on a Windows server. On the server itself, a “fat client” is used to access the Administrative GUI of MIDAS Inventory. By default, no interaction exists between the MIDAS Inventory server and the standard MIDAS GUI. Separate manuals exist for the stand-alone product.

This manual discusses the add-on for MIDAS Inventory which can be installed on a MIDAS Web Application server. This will create a GUI integration of MIDAS Inventory into the standard MIDAS Web interface which you are using to administrate HPOM (see Figure 1 on page 11).

The following interfaces exist for MIDAS Inventory:

• Operations interface (via the add-on for the MIDAS GUI)

This interface provides read-only access and all user views are based on the existing and extensive MIDAS user model. Users can fetch in-depth information for any node object (for example, Applications or Memory Modules Reports) but also use the information collected by MIDAS Inventory to add new nodes, etc. An integration into the HPOM Java GUI allows users to access detailed system information directly from a message.

• Administration interface

This is a native Windows application providing full access to all features of MIDAS Inventory, which also includes custom reporting and exporting of reports to Excel.

Figure 1: Architecture Overview

MIDASConfigurator

NETWORK

HPOM

MIDASInventory

DB

HPJava GUI

AdministrativeGUI

HP OM server

Inventory Server(Windows platform)HP OM server

MIDASWeb GUIServer

GUIintegration

GUIintegration

Chapter 2: Architecture 11

Communication and Ports

This section will discuss only MIDAS Inventory specifics. For a general overview on the general communication setup in MIDAS, see the MIDAS Administration and Configuration Guide.

The Windows MIDAS Inventory server has to be registered on the MIDAS Web Application system as a MIDAS Backend server, similar when you register any other HPOM server.

Therefore, the MIDAS Web Application system needs to be able to talk to the Windows MIDAS Inventory server directly.

By default the MIDAS Inventory server listens on port 9000 to incoming connections from any MIDAS Web Application system.

If there is a firewall the corresponding ports have to be opened. The blue arrow shows the direction from where the communication is initiated.

Figure 2:

Windows Server with

MIDAS Inventory

9000Browser 9662/9663

MIDAS web application

system

Firewall Firewall

HTTP or HTTPS

Communication and Ports

12 Chapter 2: Architecture

3 Installing MIDAS Inventory

This section will discuss the system requirements and installation of MIDAS Inventory:

• Overview on page 13

• System Requirements on page 13

• Technical Requirements on page 14

• MIDAS Inventory Web-Service Module on page 14

• MIDAS Inventory Web Application Add-on on page 16

• Post Installation Tasks on page 18

Overview

To enable the integration between MIDAS and the Windows-based MIDAS Inventory server, you must perform two high-level installation steps.

• Windows based MIDAS Inventory Server

Install the Inventory Web-Service module - a small Windows MSI executable. For more details, see MIDAS Inventory Web-Service Module on page 14.

• MIDAS Web Application systems

Install the MIDAS Inventory add-on. This add-on is included in the common MIDAS installation package. For more details, see MIDAS Inventory Web Application Add-on on page 16.

System Requirements

Before you start the installation process, check the following system prerequisites:

• Windows MIDAS Inventory server

Requires patch level v4.2 or higher. For the system requirements of the Windows MIDAS Inventory, see the corresponding Installation Guide.

• The MIDAS Inventory add-on

Requires v4.2 or higher. All system requirements of MIDAS 4.2 must be met. See the MIDAS Installation Guide for more details.

A separate installer is required for each installation step.

Chapter 3: Installing MIDAS Inventory 13

If the MIDAS Inventory add-on is installed on a system where MIDAS is already existing you have to use the same version of the installer. For example, if MIDAS v4.2 is installed, you have to use the v4.2 installer to install the MIDAS Inventory add-on.

Technical Requirements

Before you start the installation process, check the following disk-space requirements:

• Permanent Disk Space:

— On the Windows MIDAS Inventory server some additional diskspace of 20MB on top of an existing MIDAS Inventory installation

— On the MIDAS Web Application system some additional diskspace of 10MB on top of an existing MIDAS installation is required

• Temporary Disk Space:

~2000MB temporary disk space in /tmp or some other location (needed temporarily during the installation for unpacking the installer itself)

MIDAS Inventory Web-Service Module

Out of the box MIDAS Inventory does not provide a connector to which the MIDAS Web Application could talk to. In order to enable the MIDAS Web Application system connect to the MIDAS Inventory server it is required to install a SOAP Web service.

The following points should be taken into account:

• This module has to be installed on the Windows MIDAS Inventory server.

• For that purpose we offer a stand-alone installer: “InventoryWebService.msi”.

• The version of the MSI installer should match the version of MIDAS Inventory.

The installation is straight forward. Simply execute the installer on the Windows machine on which the MIDAS Inventory application is installed. The installer will not query the user for any configuration input (see the next page).

Please note, that the fully automatic configuration will include:

• SOAP Web service port: 9000.

• Communication method: HTTP.

These settings can be changed after the installation is complete. If you want to do so, please refer to Chapter 4, Configuring MIDAS Inventory.

When launching the SOAP Web service installer you will receive the screen illustrated in Figure 3 on page 15.

14 Chapter 3: Installing MIDAS Inventory

Figure 3: SOAP Web Service Welcome Screen

The subsequent screen asks you to accept the license agreement, as illustrated in Figure 4 on page 15.

Figure 4: SOAP Web Service - License Agreement

The installer automatically installs the SOAP Web service and creates a Windows service called “MIDAS Inventory Web Service” which you can use to control (or example, stop, start, restart) the SOAP Web service.

When the installation is complete click Finish, as illustrated in Figure 5 on page 16.


Figure 5: SOAP Web Service - Completion

MIDAS Inventory Web Application Add-on

On the MIDAS Web Application system1, it is necessary to install the MIDAS Inventory add-on. This section covers two scenarios:

• Adding MIDAS Inventory to MIDAS on page 16

• New Installation on page 18

Adding MIDAS Inventory to MIDAS

If you want to add MIDAS Inventory to an existing installation of MIDAS, perform the following steps:

It is important to use the same installer version of the current MIDAS version installed on the system!

1 Export the DISPLAY of the HPOM 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.

1 Define the directory to which the installer will unpack itself temporarily, please run:

# export IATEMPDIR=/directory/with/enough/spaceExample: # export IATEMPDIR=/tmp

2 Start the installer with the following command:

# ./install.bin

1. If the MIDAS Web Application and MIDAS Web Application server modules are split across two servers, MIDAS Inventory has to be installed on BOTH systems.


If there is not enough free disk space inside /tmp or the other directory you defined, you will receive the following message:

bash-2.05b# ./install.bin Preparing to install...WARNING: /tmp does not have enough disk space!

If you see the message indicated above, set the IATEMPDIR variable to an alternative location that has the required disk space and restart the installer, for example:

# export IATEMPDIR=/directory/with/enough/space# ./install.bin

3 The installer will detect the existing MIDAS 4x installation and offer you the chance to perform an upgrade, which installs additional components. Select Upgrade, as illustrated in Figure 6 on page 17.

Figure 6: Upgrade

• The existing version of MIDAS 4x will be temporarily stopped.

• Inside the product selection window the Web Application and Web Application Server modules should be listed as “installed” (Figure 7 on page 17).

— Installable add-on products: [X] Enable the checkbox for MIDAS Inventory.

Figure 7: Add MIDAS Inventory

• After that finish the installation.


New Installation

See the MIDAS Installation Guide for a description of all the installation steps required on an empty system where MIDAS has not been installed.

The MIDAS Inventory add-on must be installed on the same server as the MIDAS Web Application. If the MIDAS Web Application and MIDAS Web Application Server modules are split across two servers, MIDAS Inventory has to be installed on both systems.

In the product selection window it (see Figure 8 on page 18) please enable the following settings:

— Installable add-on products: [X] Enable the checkbox for MIDAS Inventory.

Figure 8: Add MIDAS Inventory

• Finish the installation according to the MIDAS installation guide.

Post Installation Tasks

Currently there are maximal two post installation task to perform, after the SOAP Web service was installed and the MIDAS Inventory add-on on the MIDAS Web Application system.

• Enabling HTTPS on page 18

• Registering the Inventory Server in the MIDAS GUI on page 19

Enabling HTTPS

By default, the communication between the MIDAS GUI (MIDAS Web Application) and the Windows based MIDAS Inventory server is unencrypted (HTTP).

The configuration setup has to be done in two steps:

1 Enabling HTTPS


2 Exchanging the corresponding certificates between the servers

For a detailed explanation please see chapter: HTTPS Usage on page 22.

Registering the Inventory Server in the MIDAS GUI

In order to be able to connect to MIDAS Inventory server, you have to register it on the MIDAS Web Application system.

In order to do so perform the following tasks in the MIDAS Web Application GUI:

1 From the administrative menu select: “Servers” -> “List All”

2 From the List Menu at the bottom select: “Add Server”

3 Inside the Add Server editor you have to provide the correct settings. These are:

— Server Type: select “Inventory Server” here.

— Hostname: usage of the full DNS is recommended. The hostname must be resolvable on the MIDAS Web Application system.

— Server Identifier: You have to enter a unique server identifier, which is otherwise not used in your MIDAS environment. You can for example use: <hostname>_server, or “inventory_server”. Please note, this identifier is not defined on the Windows MIDAS Inventory server, as it is otherwise the case with MIDAS Backend servers.

— User Name, Password: You have to enter a Windows user which is allowed to access the Windows MIDAS Inventory server.

— Protocol: SOAP protocol has to be used.

— SSL: is not enabled by default. This requires a certificate exchange between a separate MIDAS Web Application and MIDAS Backend(s). For more details see HTTPS Usage on page 22.

— Port: default port 9000

Figure 9: Add Inventory Server Dialog

If all settings are correct, the result should be similar to the window illustrated in Figure 10 on page 20, where the MIDAS Inventory server is shown as green.


Figure 10:Successful Registration of an Inventory Server


4 Configuring MIDAS Inventory

There are currently two areas where the MIDAS Inventory integration into the MIDAS GUI can be adapted:

• Listening Port on page 21

It is possible to modify the listening port of the Windows MIDAS Inventory server to which the MIDAS GUI connects to.

• HTTPS Usage on page 22

Communications between the MIDAS GUI and the Windows MIDAS Inventory server can be switched between HTTPS and HTTP.

Listening Port

By default MIDAS Inventory listens on port 9000 for connections from any MIDAS Web Application server. You can change this port setting in the file WebServiceConfig.xml, which can be found in the directory:

C:\Program Files\blue elephant systems\MIDAS Inventory 4.2\config

The configuration block for the MIDAS Web Application server port setting is:

[...] <WebServicePort>9000</WebServicePort>

If you change the default port setting for the MIDAS Web Application server, you must restart the MIDAS Inventory Web service.

Figure 11:SOAP Web Service Restart

Chapter 4: Configuring MIDAS Inventory 21

HTTPS Usage

By default, the communication between the MIDAS GUI (MIDAS Web Application) and the Windows based MIDAS Inventory server is unencrypted (HTTP) as illustrated in Figure 12 on page 22.

Figure 12:

Browser WebApp ModuleBackEnd Module

here: MIDAS Inventory

HTTP or HTTPS

The configuration setup must be performed in the following order:

1 Enable HTTPS

2 Exchange the corresponding certificates between the servers

3 Update the MIDAS Inventory Backend settings inside the MIDAS GUI.

The details of each step will be explained below.

Enabling HTTPS

The central configuration file for enabling HTTPS/SSL usage is

WebServiceConfig.xml:

It can be found inside the following directory:

C:\Program Files\blue elephant systems\MIDAS Inventory 4.2\config

The protocol can be changed inside the block:

[...] <WebServiceProtocol>http</WebServiceProtocol>

If you want to switch your communication from HTTP to HTPS simply enter: https

Please note, that you have to restart the MIDAS Inventory Web Service. You can use the Windows Computer Management for that purpose.

22 Chapter 4: Configuring MIDAS Inventory

Figure 13:SOAP Web Service Restart

Certificate Exchange

To enable HTTPS, the corresponding certificates have to be exchanged between the MIDAS Web Application system (server A) and the MIDAS Inventory server (server B). After that each certificate has to be imported into the local trust-/keystore.

Figure 14:

Browser WebApp ModuleBackEnd Module

here: MIDAS Inventory

HTTPS

<MIDAS_HOME>/conf/B_server.cerA B

<MIDAS_HOME>/conf/A_server.cer /tmp/tmp

Import certificate Bto keystore on A

Import certificate Ato keystore on B

On the MIDAS Inventory server two batch files exist, which will help you with the export and import of the certificates. Their file location is:

C:\Program Files\blue elephant systems\MIDAS Inventory 4.2\bin

• ExportKey.bat to export the JDisc key from the JDisc's keystore

Syntax: ExportKey.bat {target-filename}

• ImportKey.bat to import the MIDAS key into the JDisc truststore

Syntax: ImportKey.bat {source-filename} {backend_identifier}

The individual truststore and keystore are located in:

C:\Program Files\blue elephant systems\MIDAS Inventory 4.2\

• On the MIDAS Inventory server export the local certificate:

Open a shell window and go into the following directory



Run the export command like this:

exportkey.bat C:\temp\midas_inventory.cer

• Transfer the file midas_inventory.cer to the MIDAS Web Application system, preferably into /tmp.

• Import the certificate midas_inventory.cer on the MIDAS Web Application by:

# /opt/midas<version>/midas.sh ant -f run.xml https_import_backend\ -Dfile=/tmp/midas_inventory.cer -Dbackend=inventory_server

• Next transfer the certificate of the MIDAS Web Application to the MIDAS Inventory server. The certificate is located in:

# /opt/midas<version>/conf/<hostname>_server.cer

• On the MIDAS Inventory server import the MIDAS Web Application certificate. Go to


and run the import from a shell window:

ImportKey.bat C:\temp\<hostname>_server.cer <hostname>_server

Updating MIDAS Inventory Registration Setting in MIDAS GUI

The 3rd and last step is required when the MIDAS Inventory server is already registered on the MIDAS Web Application.

In order to change the registration information for this server from HTTP to HTTPS, it is necessary to run through the following steps:

1 From the administrative menu select: “Servers” -> “List All”

2 Select: “Edit” from the Actions menu of your MIDAS Inventory server.

3 Enable the (X) SSL(HTTPS) checkbox and press “Save”.

Figure 15:Enabling HTTPS/SSL


If the certificate exchange was successful, the result should be similar to the screenshot illustrated in Figure 16 on page 25, where the MIDAS Inventory server is shown with the status green.

Figure 16:Successful Registration of an Inventory Server


This page is intentionally left blank.


5 Using MIDAS Inventory

Introduction

If you are new to MIDAS, its menus and functions, have a look at the section “First Steps” in the main MIDAS User Guide before starting to explore the features provided with the MIDAS Inventory. MIDAS User Guide explains in detail how to operate the MIDAS GUI.

Figure 17 on page 27 illustrates the menu names in the MIDAS GUI.

Figure 17:Menu Names

• Toolbar menu

Icons that enable you to set the data context, for example, OMU, Server, or Admin.

• Administrative menu

Context-sensitive drop-down menus that differ according to the data context (OMU, Server, Admin)

• Global Browse and Actions menus

Context-sensitive drop-down menus that enable you to display additional information about (or perform specific actions on) all objects in the currently active screen, for example, the Policy Bank.

• Context-sensitive Browse and Actions menus

Context-sensitive drop-down menus that enable you to display additional information about (or perform specific actions on) individual objects in the currently active screen, for example, a policy in the Policy Bank.

Chapter 5: Using MIDAS Inventory 27

• List menu

Context-sensitive drop-down menu that enables you to perform an action on selected objects in the currently active screen, for example, on one of more specific policies in the Policy Bank.

Overview

This chapter provides an overview of the functions available as a result of the integration of MIDAS Inventory with the MIDAS Web interface.

The integration of MIDAS Inventory with the MIDAS Web interfaceis as follows:

• You can directly access & browse the MIDAS Inventory data via the MIDAS Web interface. See section: Direct Access on page 28.

• Or you can indirectly access that data provided by MIDAS Inventory from within the context of a node in HPOM. See section: Access from within HPOM on page 32.

Direct Access

In order to directly access and browse the available MIDAS Inventory data, perform the following steps:

1 In the administrative menu, click “Servers” and select the MIDAS Inventory server.

2 In the top right hand corner you will see, that you are now connected to your MIDAS Inventory server (Figure 18 on page 28). In this example the MIDAS Inventory server is on the host “Narwal”.

Figure 18:

3 From the Toolbar Menu select the “Server” icon.

4 Either select the direct link “All Discovered Devices” or use: “Browse” -> “All Discovered Devices” (Figure 19 on page 29).

28 Chapter 5: Using MIDAS Inventory

Figure 19:Direct Access

This displays a list of all detected devices (Figure 20 on page 29). The presentation is identical to any other listing in MIDAS, with 20 results shown on each page. If there are more that 20 results, you can page forwards and backwards. You can use a filter (for example, a letter of the alphabet) to narrow down the results.

Figure 20:All Discovered Devices Listing

5 If you receive an error such as the one displayed in Figure 21 on page 29, it might be that the MIDAS Inventory Windows part is not running.

Figure 21:Communication Error

6 To check if the MIDAS Inventory Windows server is running, log on to the MIDAS Inventory Windows server using the Administration GUI. You can restart the application using “Administration” -> “Start Application”.


Figure 22:

7 The Browse and Actions menus offer context based information on all items. They are explained below.

Via the Browse Menu various object details can be displayed (Figure 23 on page 30):

— General Report (listing for example: hostname, discovery date, manufacturer, model, uptime)

— Networking Report (Interfaces, Networks, SNMP System Group)

— Hardware (Processors, Memory Modules, Disks, Video Controller, etc.)

— Firmware details

— Software (Operating System, Applications, Appl.Instances, Patches, Services)

— User (Logged on Users, Local Users, Logged on User History)

— Virtual Computers installed on the server

— Roles & Groups

— Protocols lists the protocol status (e.g. for DNS, HTTP, SSH)

MIDAS provides expandable sub-menus, as illustrated in Figure 23 on page 30.

Figure 23:Browse Menu

8 When selecting a report, the result could for example look like this (Processors Report for the node “jever”, Figure 24 on page 30:

Figure 24:Report Details Example


When viewing a report, as illustrated in Figure 24 on page 30, it is also possible to use the Global Browse and Actions menus. You do not have to go back to the previous listing, as illustrated in Figure 25 on page 31.

Figure 25:Report Details - Global Browse and Actions Menu

9 From the context-sensitive Actions menu you can select “Add Node”, as illustrated in Figure 30 on page 32. This enables you to quickly add a node to HPOM if it is not monitored yet.

Figure 26: Actions Menu

When selecting “Add Node” a yellow selector box will pop up. Here you have to define the HPOM server on which the node will be added (Figure 27 on page 31).

Figure 27: Add Node Selector

10 Next, the standard MIDAS node editor will be opened, where you can define any node details. If necessary you can also manually select the machine type here (Figure 28 on page 31).

Figure 28: Node Editor

Please note, that the List Menu at the bottom is currently not used in MIDAS Inventory (Figure 29 on page 32).

MIDAS tries to detect the machine type automatically. The type “other other” is also always offered. If the automatic detection fails, continue with “other other” and manually set the type in the subsequent Node Editor screen.


Figure 29: List Menu is not used

Access from within HPOM

The following functions are available:

• Corresponding Device on page 32

Listing the MIDAS Inventory data for a particular node. Here you can quickly list all relevant data collected by MIDAS Inventory for a particular node.

• Node Comparison Report on page 33

Node Comparison Report. This will compare your HPOM environment against the findings of MIDAS Inventory.

Corresponding Device

Inside your standard MIDAS interface, you now have the possibility to access the MIDAS Inventory features within the context of an existing node in HPOM. Select from the Browse Menu of a node “Corresponding Device”, as illustrated in Figure 30 on page 32.

Figure 30:Context Node Browse Menu

You will be asked to select the MIDAS Inventory server from which the data is collected (Figure 31 on page 32).

Figure 31: Selection of MIDAS Inventory Server

Via the Browse Menu (as it was explained in the previous section) you can access the various system specific reports (Figure 32 on page 33).


Figure 32:

Node Comparison Report

The Node Comparison Report is extremely helpful when you want to compare your existing HPOM environment against the findings of MIDAS Inventory. This will give you a live report which is displayed in the MIDAS Web interface. The results will be displayed side by side (see below for details).

This can, for example help you in finding and identifying servers which exist in your environment, but which are not monitored via HPOM. Therefore, you might not be alerted by a sudden downtime of this system.

The details can be found here:

• Trigger Node Comparison Report on page 33

• Node Comparison Report Results on page 34

Trigger Node Comparison Report

This report can be triggered from various locations.

• While you are connected to a HPOM server in MIDAS you can run the “Node Comparison Report” from the Global Browse Menu, as illustrated in Figure 33 on page 33.

Figure 33: Node Comparison Report - HPOM Context

• The two other possibilities are to launch the report from within the “Servers” -> “List All” window. Here you can either select to display the report via the Browse Menu of the HPOM server (see Figure 34 on page 34) or the MIDAS Inventory server (see Figure 35 on page 34).


Figure 34: Node Comparison Report - List All Servers Context

Figure 35: Node Comparison Report - List All Servers Context

Node Comparison Report Results

After the Node Comparison Report was triggered, it will be displayed after a few moments inside the Web browser.

The results will be listed similar to other HPOM objects listings in MIDAS, as illustrated in Figure 36 on page 35. There are some differences which will be discussed in this section. The first result page could look like this for example:


Figure 36: Node Comparison Report Result

Nodes/devices are grouped into one of following categories:

• Nodes/Devices in Conflict

Generally these are hostname shortname, FQDN differences (shown in red).

• Devices Missing in OM

These devices were discovery by MIDAS Inventory but are not present inside HPOM (shown in orange).

• Nodes Missing in the MIDAS Inventory Environment

Devices which were not discovered by MIDAS Inventory (shown in yellow).

• Identical Nodes/Devices

(Shown in green).

It is possible to limit the items displayed to one of these blocks. This can be done via the Global Browse Menu, as illustrated in Figure 37 on page 35.

Figure 37: Categories Filter

There are 20 results displayed per page. In order to go forward or backwards please use the according buttons or the jump to page x function, as illustrated in Figure 38 on page 36.


Figure 38: Jump to, Go Forward, Go Backward

In order to allow you direct access to all MIDAS and MIDAS Inventory functions the corresponding context-sensitive Browse and Actions menus are also included in the Node Comparison Report, as illustrated in Figure 39 on page 36.

Figure 39: Browse and Actions Menus

Therefore, it is possible to directly add from within the Node Comparison Report a device which is missing in HPOM by using the MIDAS Inventory Actions menu, as illustrated in Figure 40 on page 36.

Figure 40: Add Missing Device


Triggering a new Discovery

It is also possible to initiate a new discovery run via the MIDAS GUI in order to detect any new nodes/devices. This task can be initiated from various locations within the MIDAS GUI.

• “List All Servers “ screen

From the administrative menu select “Servers” -> “List All”. In the Actions menu of the MIDAS Inventory server, select “Execute Discovery Job”.

Figure 41: Execute Discovery Job

• MIDAS Inventory as a Backend:

a In the administrative menu go to: “Servers” -> and the select the MIDAS Inventory server.

b In the top right hand corner you will see, that you are now connected to your MIDAS Inventory server.

c From the Toolbar Menu click on the “Server” icon.

d Either select the direct link “All Discovery Jobs” or use: “Browse” -> “All Discovery Jobs” (Figure 42 on page 37).


e In the Actions menu, select “Execute Discovery Job”, as illustrated in Figure 43 on page 38.


Elevate your IT Management


midas inventory webapp integration - bes-worldline.com inventory/midas_4.9_inventory...2. legal...

Documents