Ucmdb8.01 DDM Cp5

HP Universal CMDB
for the Windows operating system Software Version: CP5.0, 8.01 or later
Discovery and Dependency Mapping Content Guide
Document Release Date: January 2010 Software Release Date: January 2010
Legal Notices
Warranty The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice. Restricted Rights Legend Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Copyright Notices Copyright 2005 - 2010 Hewlett-Packard Development Company, L.P. Trademark Notices Adobe and Acrobat are trademarks of Adobe Systems Incorporated. Intel, Pentium, and Intel XeonTM are trademarks of Intel Corporation in the U.S. and other countries. JavaTM is a US trademark of Sun Microsystems, Inc. Microsoft, Windows, Windows NT, and Windows XP are U.S registered trademarks of Microsoft Corporation. Oracle is a registered US trademark of Oracle Corporation, Redwood City, California. Unix is a registered trademark of The Open Group.
Documentation Updates
The title page of this document contains the following identifying information: Software Version number, which indicates the software version. Document Release Date, which changes each time the document is updated. Software Release Date, which indicates the release date of this version of the software.
To check for recent updates, or to verify that you are using the most recent edition of a document, go to: http://h20230.www2.hp.com/selfsolve/manuals This site requires that you register for an HP Passport and sign-in. To register for an HP Passport ID, go to: http://h20229.www2.hp.com/passport-registration.html Or click the New users - please register link on the HP Passport login page. You will also receive updated or new editions if you subscribe to the appropriate product support service. Contact your HP sales representative for details.
Support
Visit the HP Software Support web site at: http://www.hp.com/go/hpsoftwaresupport This web site provides contact information and details about the products, services, and support that HP Software offers. HP Software online support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your business. As a valued support customer, you can benefit by using the support web site to: Search for knowledge documents of interest Submit and track support cases and enhancement requests Download software patches Manage support contracts Look up HP support contacts Review information about available services Enter into discussions with other software customers Research and register for software training
Most of the support areas require that you register as an HP Passport user and sign in. Many also require a support contract. To register for an HP Passport ID, go to: http://h20229.www2.hp.com/passport-registration.html To find more information about access levels, go to: http://h20230.www2.hp.com/new_access_levels.jsp
Table of Contents
Welcome to This Guide .......................................................................11 How This Guide Is Organized .............................................................11 Who Should Read This Guide .............................................................13 Getting More Information ..................................................................13 PART I: INTRODUCTION Chapter 1: General Information for Discovery and Dependency Mapping Content ...........................................................................17 Delete Files Copied to Remote Machine .............................................17 Files Copied to a Remote Machine......................................................18 PART II: THE APPLICATION MODULES Chapter 2: Active Directory.................................................................25 Overview..............................................................................................25 Discover Active Directory Domain Controllers and Topology...........26 Chapter 3: Microsoft Exchange...........................................................33 Overview..............................................................................................33 Discover Microsoft Exchange Server 2003 ..........................................34 Discover Microsoft Exchange Server 2007 ..........................................39 Discover Microsoft Exchange Server Topology with Active Directory .........................................................................................43 Chapter 4: SAP.....................................................................................51 Overview..............................................................................................51 Discover SAP ABAP ..............................................................................52 Discover SAP Java ................................................................................56 Discover SAP Solution Manager ..........................................................58 Chapter 5: Siebel .................................................................................61 Overview..............................................................................................61 Discover Siebel Topology ....................................................................62
Table of Contents
Chapter 6: UDDI Registry....................................................................69 Overview..............................................................................................69 Discover UDDI Processes.....................................................................69 P A R T I I I: TH E C L U ST E R M O D U L E S Chapter 7: Microsoft Cluster...............................................................75 Discover Microsoft Cluster Servers......................................................75 Chapter 8: Veritas................................................................................77 Discover Veritas Cluster Servers ..........................................................77 P A R T I V : T H E D A T AB A S E M O D U L E S Chapter 9: DB2 ....................................................................................83 Discover IBM DB2 Databases ..............................................................83 Chapter 10: MS-SQL ............................................................................87 Discovery by OS Credentials ...............................................................87 Discover Microsoft SQL Server Database Application.........................88 Discover SQL Server by OS Credentials...............................................90 Chapter 11: MySQL Replication Between Databases .........................93 Overview..............................................................................................93 Discover MySQL Configuration and Replication Jobs........................94 Chapter 12: Oracle ............................................................................103 Discover Oracle Databases.................................................................103 Discover Oracle Real Application Cluster (RAC)...............................106 P A R T V : D I S C OV E RY T O O L S Chapter 13: Discovery Tools .............................................................119 Overview............................................................................................119 Troubleshooting and Limitations .....................................................119 Chapter 14: Importing Data from External Sources.........................121 Importing Data from External Sources Overview ..........................122 The External_source_import Package................................................124 The Import from CSV File Job...........................................................125 The Import from Properties File Job .................................................129 The Import from Database Job..........................................................130 The External Source Mapping Files ...................................................135 Converters .........................................................................................135 Import CSV Data from an External Source Scenario......................138 Troubleshooting and Limitations .....................................................142
Table of Contents
P A R T V I : I N T E G R A T I O N B Y D IS C O V E R Y Chapter 15: Network Node Manager i (NNMi) Integration with HP Universal CMDB .............................................................147 NNMi Integration Overview...........................................................148 NNMi - UCMDB Integration Architecture ........................................149 Set Up HP NNMiHP UCMDB Integration .......................................150 Run HP NNMiUCMDB Integration .................................................151 Use the HP NNMiHP UCMDB Integration .....................................159 Change the HP NNMiHP UCMDB Integration Configuration ......162 Disable HP NNMiHP UCMDB Integration Configuration .............162 Perform Impact Analysis ...................................................................163 HP NNMiHP UCMDB Integration Configuration Form Reference 163 NNMi Protocol Connection Parameters ...........................................167 Troubleshooting and Limitations .....................................................168 Chapter 16: Storage Essentials (SE) Integration with HP Universal CMDB ..............................................................171 SE Integration Overview .................................................................172 Discover the SE Oracle Database .......................................................173 The Storage Essentials Integration Packages .....................................175 Discovered CITs .................................................................................176 Views..................................................................................................181 Correlation Rules ...............................................................................185 Reports ...............................................................................................187 Chapter 17: EMC Control Center (ECC) Integration with HP Universal CMDB ..............................................................191 ECC Integration Overview..............................................................192 Discover the ECC Storage Topology .................................................193 ECC Job SQL Queries.........................................................................199 Views..................................................................................................202 Correlation Rules ...............................................................................206 Reports ...............................................................................................209 PART VII: THE J2EE MODULES Chapter 18: JBoss...............................................................................215 Discover JBoss by Shell ......................................................................215 Chapter 19: WebLogic ......................................................................221 Discover WebLogic ............................................................................221 Discover WebLogic by Shell ..............................................................223
Table of Contents
Chapter 20: WebSphere....................................................................227 Discover WebSphere by Shell............................................................227 Troubleshooting and Limitations .....................................................231 PART VIII: THE NETWORK MODULES Chapter 21: Host Resources and Applications..................................235 Host Resources and Applications Overview ...................................235 Host Resources and Applications Workflow ..................................237 Revert to Previous Method of Discovering Installed Software .........244 Changes to DDM Modules ................................................................245 Troubleshooting and Limitations .....................................................248 Chapter 22: Network Basic................................................................249 Overview............................................................................................249 Host Connection by Shell: Discover Windows Running F-Secure .........................................................................................250 Chapter 23: Layer 2 ..........................................................................251 Overview............................................................................................251 Discover Layer 2 Objects ...................................................................252 Chapter 24: Network Advanced........................................................267 Overview............................................................................................267 Discover DNS Zones ..........................................................................267 Chapter 25: Credential-less...............................................................271 Overview............................................................................................271 Discover Host Fingerprint with Nmap..............................................271 Chapter 26: Active and Passive Discovery Network Connections .................................................................................279 Overview............................................................................................279 Discover Processes .............................................................................280 Chapter 27: Load Balancer................................................................287 Overview............................................................................................287 Discover Load Balancers....................................................................288 PART IX: THE VIRTUAL MACHINES MODULE Chapter 28: VMware .........................................................................299 Discover VMware Infrastructure Topology .......................................299 Discover VMware VMotion ..............................................................321
Table of Contents
PART X: THE WEB SERVER MODULES Chapter 29: Apache Tomcat .............................................................327 Overview............................................................................................328 Discover Apache Tomcat...................................................................329 Discover Bugzilla, Wordpress, and MediaWiki .................................333 Chapter 30: Microsoft Internet Information Services (IIS) ..............335 Discover Microsoft Internet Information Services (IIS) Previous Topology.........................................................................335 Discover Microsoft Internet Information Services (IIS) Current Topology..........................................................................339 Index ..................................................................................................345
Table of Contents
10
Welcome to This Guide

This guide describes the procedures for discovering components in your environment. This chapter includes:

How This Guide Is Organized on page 11 Who Should Read This Guide on page 13 Getting More Information on page 13
How This Guide Is Organized

The guide contains the following chapters:
Part I
Introduction
Provides general information for Discovery and Dependency Mapping Content.
Part II
The Application Modules

Explains how to discover enterprise applications such as Active Directory, Microsoft Exchange, SAP, and Siebel, and the UDDI registry.
Part III
The Cluster Modules

Explains how to properly configure discovery of cluster solutions such as Microsoft Cluster and Veritas Cluster.
11
Part IV
The Database Modules

Explains how to discover Database Management Systems (DBMS) such as DB2, MS-SQL, and Oracle databases.
Part V
Discovery Tools
Discovery Tools provide guidance on how to perform frequent discovery tasks, such as importing data from databases or properties files.
Part VI
Integration by Discovery
Describes integration solutions that are based on DDM capabilities.
Part VII The J2EE Modules

Explains how to perform J2EE discovery, for example, to discover JBoss, WebLogic and WebSphere J2EE components.
Part VIII The Network Modules

Provides documentation on performing Network discovery that discovers what is generally running in your environment. Also explains how to discover resources that exist on a host (for example, Disk, CPU, Users) as well as applications that run on that host.
Part IX
The Virtual Machines Module

Describes how to discover the connection between the physical infrastructure and the Virtual Machines that run on it.
Part X
The Web Server Modules

Describes how to discover and model Web Server solutions such as Apache Tomcat and Microsoft IIS.
12
Who Should Read This Guide

This guide is intended for the following users of HP Universal CMDB:

HP Universal CMDB administrators HP Universal CMDB platform administrators HP Universal CMDB application administrators HP Universal CMDB data collector administrators Readers of this guide should be knowledgeable about enterprise system administration, have familiarity with ITIL concepts, and be knowledgeable about HP Universal CMDB.
Getting More Information

For a complete list of all online documentation included with HP Universal CMDB, additional online resources, information on acquiring documentation updates, and typographical conventions used in this guide, see the HP Universal CMDB Deployment Guide PDF.
13
14
Part I
Introduction
16
1
General Information for Discovery and Dependency Mapping Content
This chapter includes: Tasks
Delete Files Copied to Remote Machine on page 17 Reference
Tasks
Files Copied to a Remote Machine on page 18
Delete Files Copied to Remote Machine

During discovery, DDM copies files to a remove Windows machine. For details, see Files Copied to a Remote Machine on page 18. To configure DDM to delete files copied to the destination machine, once discovery is finished: 1 Access the globalSettings.xml file: Manage Discovery Resources > AutoDiscoveryContent > Configuration Files. 2 Locate the removeCopiedFiles parameter.

true. The files are deleted. false. The files are not deleted.
3 Save the file. To control xCmd behavior: 1 In the globalSettings.xml file, locate the NtcmdAgentRetention parameter.
17
Chapter 1 General Information for Discovery and Dependency Mapping Content
2 Enter one of the following:
0. (The default) Unregister the service and delete the remote executable file. (Unregister: stop the service and remove it from the remote machine, so that it is no longer listed in the list of services.) 1. Unregister the service, but leave the executable file on the file system. 2. Leave the service running, and leave the executable file on the file system.
Reference
Files Copied to a Remote Machine

This section lists the files that the DDM Probe copies to a remote Windows machine, to enable discovery of the machines components. DDM copies the files to the %SystemRoot%\system32\drivers\etc\ folder on the remote machine.
Note:
DDM runs xCmdSvc.exe to connect to and retrieve the Shell on the remote machine. When the wmic command is launched on the remote Windows machine, by the Host Connection by Shell or Host Resources and Applications by Shell jobs, an empty TempWmicBatchFile.bat file is created.
This section includes the following topics:

adsutil.vbs on page 19 getfilever.vbs on page 19 reg_mam.exe on page 19 meminfo.exe on page 20 diskinfo.exe on page 20
18

processlist.exe on page 20 Exchange_Server_2007_Discovery.ps1 on page 21 GetFileModificationDate.vbs on page 21 junction.exe on page 22
adsutil.vbs
The Visual Basic script used for discovery of Microsoft IIS applications. DDM copies this Visual Basic script to the remote machine to discover IIS. Relevant DDM Job: IIS Applications by NTCMD Content Pack Version: All
getfilever.vbs
The Visual Basic script is used to identify the version of the running software. The script retrieves the executable or DLL file version on Windows machines. This Visual Basic script is used by Shell-based application signature plug-ins to retrieve the version of a particular software on the remote machine. Relevant DDM Job: Host Resources and Applications by Shell Content Pack Version: All
reg_mam.exe
The copy of the Microsoft reg.exe file that enables querying the registry. If DDM does not discover a native reg.exe file, this executable is copied to the remote Windows machine. This situation occurs with some previous Windows versions (for example, Windows 2000) where the tool is not included by default but can still function there correctly. Relevant DDM Job: Host Resources and Applications by Shell Content Pack Version: All
19
meminfo.exe
The executable that enables the retrieval of memory information. DDM discovers memory information with the wmic query. However, if the wmic query fails to execute, DDM copies the meminfo.exe file to the remote machine. This failure can occur if, for example, wmic.exe is not included in the PATH system variable or is completely absent on the remote machine, as is the case on Windows 2000. Relevant DDM Job: Host Resources and Applications by Shell Content Pack Version: All
diskinfo.exe
The executable that enables the retrieval of disk information when it is not available to be retrieved by wmic. DDM discovers default disk information with the wmic query. However, if the wmic query fails to execute, DDM copies the diskinfo.exe file to the remote machine. This failure can occur if, for example wmic.exe is not included in the PATH system variable or is completely absent on the remote machine, as is the case on Windows 2000. Relevant DDM Job: Host Resources and Applications by Shell Content Pack Version: All
processlist.exe
The executable that enables the retrieval of process information together with command line, PID and other relevant information. DDM discovers default process information with the wmic query. However, if the wmic query fails to execute, DDM copies the processlist.exe file to the remote machine. This failure can occur if, for example wmic.exe is not included in the PATH system variable or is completely absent on the remote machine, as is the case on Windows 2000. Relevant DDM Job: Host Resources and Applications by Shell Content Pack Version: All
20
Exchange_Server_2007_Discovery.ps1
The PowerShell script for MS Exchange 2007 discovery. DDM uses a PowerShell scenario to discover Microsoft Exchange 2007 by NTCMD. This file, therefore, must be copied to the remote machine. Relevant DDM Jobs:

Microsoft Exchange Connection by NTCMD Microsoft Exchange Topology by NTCMD
Content Pack Version: CP4
GetFileModificationDate.vbs
The Visual Basic script for retrieving the file modification date (disregarding locale). The most common use case is when DDM must retrieve the last modification date of a configuration file of a discovered application. Relevant DDM Jobs:

Apache Tomcat by Shell File Monitor by Shell IIS Applications by NTCMD IHS Websphere Plugin by Shell J2EE Weblogic by Shell J2EE WebSphere by Shell or JMX J2EE WebSphere by Shell Oracle TNSName by Shell SAP Profiles by Shell SAP System By Shell Service Guard Cluster Topology by TTY Siebel Application Server Configuration
21

Software Element CF by Shell Veritas Cluster by Shell Webserver by Shell
junction.exe
This executable file, part of the Sysinternals Suite (http://technet.microsoft.com/en-us/sysinternals/bb842062.aspx), enables the creation of a junction point. DDM uses this file if the linkd.exe and mklink.exe tools are absent on the remote machine. When DDM runs discovery on a Windows x64 machine, DDM needs to bypass the Windows redirect feature running on that machine. DDM does this by creating a link to the %SystemRoot%\System32 folder with either the linkd.exe or mklink.exe tool. However, if these tools are missing on the remote machine, DDM transfers junction.exe to the remote machine. DDM is then able to launch the 64-bit version of the system executable files. (Without this 64-bit version, DDM would be locked into an isolated 32-bit world.)
Note: This junction point is automatically removed once discovery is complete.
Relevant DDM Jobs:

Host Resources and Applications by Shell Microsoft Exchange Connection by NTCMD Microsoft Exchange Topology by NTCMD
22
Part II
The Application Modules
24
2
Active Directory
Note: This functionality is available as part of Content Pack 5.00 or later.
This chapter includes: Concepts
Overview on page 25 Tasks
Concepts
Discover Active Directory Domain Controllers and Topology on page 26
Overview
Active Directory (AD) provides an extensible and scalable directory service that enables efficient managing of network resources. DDM discovers Active Directory topology through the LDAP Directory Service Interface that communicates with the AD domain controllers. DDM uses JNDI to provide the API that interacts with the LDAP Directory Service Interface.
Tasks
25
Chapter 2 Active Directory
Discover Active Directory Domain Controllers and Topology

This task explains how to discover Active Directory. This task includes the following steps:

Supported Servers on page 26 Prerequisites on page 26 Network and Protocols on page 27 Discover AD Domain Controllers on page 28 Discover AD Topology on page 29 Active Directory Topology on page 32 Troubleshooting and Limitations on page 32
1 Supported Servers

Windows Server 2000 Windows Server 2003 Windows Server 2008
2 Prerequisites
a Discover the host of each AD domain controller: activate one of the following jobs (depending on the protocol you are using) in the Network Basic module:

Host Connection by Shell Host Connection by SNMP Host Connection by WMI
b Verify that the portNumberToPortName.xml configuration file includes all possible AD ports. For example, if AD is running on LDAP port 389, locate the following row in the file:
<portInfo portProtocol="tcp" portNumber="389" portName="ldap" discover="0" />
26
Change the discover="0" attribute value to discover="1". For details, see Define a New Port and The portNumberToPortName.xml File in Discovery and Dependency Mapping Guide. c Open the LDAP port of the destination IP for each domain controller server, by activating the following job in the Network Advanced module:
TCP Ports This job includes the TCP_NET_Dis_Port pattern.
3 Network and Protocols

a To discover hosts, you must set up the SNMP, Shell (NTCMD, SSH, Telnet), and WMI protocols:
SNMP. For credentials information, see SNMP Protocol in Discovery and Dependency Mapping Guide. Prepare the following information for the SNMP protocol: community name (for v2 protocol), user name (for v3 protocol), and password (for v3 protocol).
NTCMD. For credentials information, see NTCMD Protocol in Discovery and Dependency Mapping Guide. SSH. For credentials information, see SSH Protocol in Discovery and Dependency Mapping Guide. Telnet. For credentials information, see Telnet Protocol in Discovery and Dependency Mapping Guide. Prepare the following information for the Shell protocols: user name, password, and domain name (optional for NTCMD).
WMI. For credentials information, see WMI Protocol in Discovery and Dependency Mapping Guide. Prepare the following information for the WMI protocol: user name, password, and domain name (optional).
27
b To discovery all AD patterns, you must set up the LDAP protocol. There are two versions of the protocol available: 2 and 3. As version 2 has never been standardized in any formal specification, DDM uses the version 3 protocol. Prepare the following information for the LDAP protocol: user name (if a domain is present: username@domain), password, Authentication type. Answer the question, Should SSL be used (the default is no).
4 Discover AD Domain Controllers

In the Run Discovery window, activate the Active Directory Connection by LDAP job (in the Application Active Directory module). This job discovers the existence of AD domain controllers through LDAP.
Trigger CI
IP
Trigger TQL
CI Attributes
CI Source Service Address Attribute Value NOT IP Probe Name Is null Name Equal ignore case "ldap"
28
Triggered CI Data
Name hostId ip_address port_number Value ${HOST.root_id} ${SOURCE.ip_address} ${Service_Address. ipport_number} Description The ID of the host on which the domain controller resides. The IP address, retrieved from the service address. The LDAP port number, retrieved from the service address.
Discovered CITs

DomainController Container link
5 Discover AD Topology
In the Run Discovery window, activate the Active Directory Topology by LDAP job (in the Application Active Directory module). This job connects to the AD domain controller servers and discovers their topology.
Trigger CI
DomainController
Trigger TQL
29
CI Attributes
CI IP Source Attribute Value NOT IP Probe Name is null
NOT Reference to the credentials dictionary entry Is
null
NOT Application IP is null
Service Address
Name Equal ignore case "ldap"
Triggered CI Data
Name application_ port credentialsId hostId ip_address port Value ${SOURCE.application _port:NA} ${SOURCE.credentials _id} ${HOST.root_id} ${SOURCE.ip_address} ${SERVICE_ADDRESS. ipport_number} Description The port retrieved from the service address. The credentials ID of the protocol saved in the domain controllers attribute. The ID of the host on which the domain controller resides. The IP address of the server. The LDAP port number.
Discovery Pattern Parameters
tryToDiscoverGlobalCatalog. If this parameter is set to true, DDM attempts to discover the entire topology by connecting to the domain controller designated as a global catalog server. The connection is made through the port defined in the globalCatalogPort parameter. By default, the global catalog is not used for discovery, so the default is false. globalCatalogPort. The port number through which DDM accesses the domain controller designated as the global catalog. The default value is 3268. This parameter is needed only when tryToDiscoverGlobalCatalog is set to true.
30
Discovered CITs

Active Directory Domain. Domains in the AD Forest. Active Directory Forest. Information about functionality level and contiguous names. Active Directory Site. Available site objects that are configured in the AD Forest. Active Directory Site Link Active Directory System Container link Document DomainController DomainControllerRole Host. Member. Relationships between sites and subnets. Network. Available subnet objects.
31
6 Active Directory Topology
7 Troubleshooting and Limitations

SSL authentication is not supported by the LDAP protocol.
32
3
Microsoft Exchange
Discover Microsoft Exchange Server 2003 on page 34 Discover Microsoft Exchange Server 2007 on page 39 Discover Microsoft Exchange Server Topology with Active Directory on page 43
Concepts
Overview
DDM discovers the following components of Microsoft Exchange Server (Exchange) software, versions 2003 and 2007: Microsoft Exchange System, Server, Administrative and Routing groups, and Public folders and Folder trees. Currently, all information about Exchange is retrieved by the WMI protocol from the root\MicrosoftExchangeV2 namespace. There are two jobs responsible for Exchange discovery:

Tasks
Microsoft Exchange connection by WMI Microsoft Exchange topology by WMI
33
Chapter 3 Microsoft Exchange
Discover Microsoft Exchange Server 2003

This task explains how to discover Exchange 2003. This task includes the following steps:

Supported Versions on page 34 Prerequisites on page 34 Network and Protocols on page 34 Discovery Workflow on page 35 Configuration Item Types on page 36 Discovered CITs on page 37 The Microsoft Exchange Server Package on page 37 TQLs on page 37 Views on page 38 Topology Map on page 38 Troubleshooting and Limitations on page 39
1 Supported Versions
Microsoft Exchange Server 2003 is supported.
2 Prerequisites
You must enable read-only permissions for the root\MicrosoftExchangeV2 WMI namespace. In some cases the root\cimv2 namespace is also needed (with read-only permissions). For details, see Troubleshooting and Limitations on page 39.

WMI. For credentials information, see WMI Protocol in Discovery and Dependency Mapping Guide.Information about Exchange is taken from the root\MicrosoftExchangeV2 namespace.
34
4 Discovery Workflow
In the Run Discovery window, activate the following jobs:

Network Basic (Host Connection by WMI) to discover WMI CITs. Run any of the Host Resources and Applications jobs that gather information about processes running on a host. If a process named emsmta.exe is discovered on a host, the Microsoft Exchange Connection by WMI job is triggered. Application Microsoft Exchange (Microsoft Exchange Connection by WMI). The job reports the server that is actually running on this host. To discover other Exchange servers, you must run this job on each host where Exchange is running. The job creates Exchange CITs. This job connects to the remote host by WMI to the root\MicrosoftExchangeV2 namespace. The following WMI queries are executed:
SELECT AdministrativeNote, CreationTime, ExchangeVersion, FQDN, GUID, MTADataPath, MessageTrackingEnabled, MessageTrackingLogFileLifetime, MessageTrackingLogFilePath, MonitoringEnabled, Type FROM Exchange_Server
This query returns all Exchange servers present in the Exchange organization.
Microsoft Exchange Topology by WMI. The Exchange CI created by the Microsoft Exchange Connection by WMI job acts as a trigger for this job. The Trigger CI connects to the host where Exchange is running and retrieves the complete topology. (For details on troubleshooting error messages, see Troubleshooting and Limitations on page 39.) This job connects to the remote host by WMI to the root\MicrosoftExchangeV2 namespace. The following WMI queries are executed (order is preserved):
SELECT AdministrativeGroup, DN, FQDN, Name, RoutingGroup FROM Exchange_Server SELECT AdministrativeGroup, AdministrativeNote, CreationTime, Description, GUID, Name, RootFolderURL FROM Exchange_FolderTree SELECT AddressBookName, AdministrativeNote, Comment, ContactCount, FolderTree, FriendlyUrl, IsMailEnabled, Path, Url FROM Exchange_PublicFolder
35
5 Configuration Item Types

The following CIs are created for Exchange components:
Exchange
This CIT is located in the Application System folder. It is an abstract CIT that is the parent of the following CITs:
Administrative group This CIT represents the administrative group in the Exchange organization.
Exchange Organization This CIT represents the top-level of the Exchange organization. For example, if an organization uses the Exchange solution, then all the Exchange components are linked to a single Exchange Organization CI.
Routing group This CIT represents routing groups existing in the Exchange organization.
Microsoft Exchange Server

This CIT is located in the Software Element folder. The CIT represents Exchange software installed on a host.
Microsoft Exchange Resource

This CIT is located in the Application Resource folder. It is an abstract CIT that is the parent of the following CITs:
Exchange folder This CIT represents the public folders available in the Exchange organization. A public folder may be organized in an hierarchical structure, that is, one public folder may contain another public folder.
Exchange folder tree This CIT provides information about public and private folder trees on Exchange servers.
36
6 Discovered CITs MS_Exchange_Connection_by_WMI
MS_Exchange_Topology_by_WMI
7 The Microsoft Exchange Server Package

All components responsible for Exchange in DDM are bundled in the Microsoft_Exchange_Server package.
8 TQLs
Name ms_exchange_process_and _wmi ms_exchange_server_and_ host_and_wmi Microsoft Exchange topology Category Trigger Trigger View Used by... Microsoft Exchange connection by WMI job Microsoft Exchange topology by WMI job Microsoft Exchange topology view
37
9 Views
The following view displays Exchange components: Microsoft Exchange topology.
10 Topology Map MS_Exchange_Connection_by_WMI
MS Exchange 2003 Topology by WMI

DDM connects to the remote host and retrieves the topology for MS Exchange 2003:
38
11 Troubleshooting and Limitations Administrative Group Limitation

If an Administrative group does not contain any Exchange servers or folder trees, the Administrative group is not discovered.
Error Messages
Error message Failed to obtain host name Reason Solution
Run any job that will retrieve the
To model Exchange topology correctly, the Microsoft Exchange Connection by WMI job should know the name of the host to which it is connected. DDM tries to retrieve the host_hostname attribute of the host, matched by the input TQL. If the attribute is not set, DDM runs the following WMI query to obtain the domain name of the host: SELECT Name FROM Win32_ComputerSystem If this query fails for any reason, the job also fails with this error message.
correct host name.

Set the host name manually. Refer to the log files for more
information as to why the WMI query for host name failed.
Failed to discover folder trees and public folders
Check if the credentials you use for connection match those described in Prerequisites on page 34.
Discover Microsoft Exchange Server 2007

DDM discovers the following CIs for Microsoft Exchange Server 2007: Exchange System, Microsoft Exchange Server, and Exchange role. DDM discovers Exchange by executing a PowerShell script on a remote machine with Exchange installed.
39
This task includes the following steps:

Prerequisites on page 40 Supported Versions on page 40 Network and Protocols on page 40 Discovery Workflow on page 40 The Microsoft Exchange Server Package on page 41 Discovered CITs on page 41 Topology Maps on page 42
1 Prerequisites

Set the script execution policy either to Unrestricted or Remote Signed. Verify that the account used for discovery has the permissions of the Exchange View-Only Administrator role.
Microsoft Exchange Server 2007.

NTCmd. For credentials information, see NTCMD Protocol in the Discovery and Dependency Mapping Guide.
a Define NTCmd credentials. The account must have Exchange View-Only Administrator permissions. b Run the Host Connection by Shell job. c Run the Host Resources and Applications by Shell job to discover the Exchange process. d Run the Microsoft Exchange Connection by NTCMD job to discover Exchange Server CIs.
40
e Run the Microsoft Exchange Topology by NTCMD job to discover the rest of the topology.

All components responsible for Exchange in DDM are bundled in the Microsoft_Exchange_Server package. For details on the package, click the Readme link in the Package Manager.
6 Discovered CITs
The following CITs are used to create CIs for Exchange components:
Exchange Organization
This CIT represents the top-level Exchange system. For example, if an organization uses the Exchange solution, all the Exchange components are linked to a single Exchange Organization CI.
Microsoft Exchange Server

This CIT is located in the Software Element folder. The CIT represents Exchange software installed on a host.
Exchange Role
This CIT is located in the Application Resource > Microsoft Exchange Resource folder. It is an abstract CIT that is the parent of the following CITs:

Exchange Client Access Server. Represents the Client Access Server role. Exchange Mail Server. Represents the Mail Server role. Exchange Edge Server. Represents Edge Server role. Exchange Hub Server. Represents Hub Server role. Exchange Unified Messaging server. Represents Unified Messaging server role.
41
7 Topology Maps
The following maps illustrate Microsoft Exchange Server 2007 topology.
MS Exchange Connection by NTCMD
MS Exchange 2007 Topology

DDM runs the NTCMD protocol to retrieve the topology for MS Exchange 2007:
42
Discover Microsoft Exchange Server Topology with Active Directory

This section explains how DDM discovers Exchange by utilizing the tight integration between Exchange and AD. DDM runs jobs to discover Exchange elements in the topology that are available only through AD. This task includes the following steps:

Overview on page 44 Prerequisites Set Permissions on page 45 Prerequisites Discover a Domain Controller on page 46 Supported Versions on page 46 Network and Protocols on page 46 Discovery Workflow on page 46 The Microsoft Exchange Server Package on page 47 Additional CITs on page 47 Deprecated CITs on page 47 Modified CITs on page 47 Discovered CITs on page 48 Trigger TQL on page 48 Trigger CI on page 49 CI Attributes on page 49 Patterns on page 49 Topology Maps on page 49 Troubleshooting and Limitations on page 49
43
1 Overview
With the addition of LDAP protocol support in Content Pack 5, DDM can discover the Exchange topology using AD. Since Exchange is tightly integrated with AD and stores most of its configuration there, DDM connects to the AD Domain Controller and extracts information from it. The Exchange configuration is stored in a specific node under Services:
The Base Distinguished Name of this node is: "CN=Microsoft Exchange, CN=Services, CN=Configuration,DC=ucmdb-ex, DC=dot" where ucmdb-ex.dot is the name of the domain in this example. If this node exists, DDM drills down and discovers all remaining information that includes: Exchange organization, Exchange servers, administrative and routing groups, connectors, roles, and so on. Multiple Domain Controllers can serve the same domain, in which case the information is replicated between them (multi-master replication). The controllers contain the same data, so DDM needs to run only against one of them.
44
Note: The job for AD discovery triggers on, and runs against, all discovered domain controllers. However, as only updates are sent to the CMDB by the DDM Probes result processing mechanism, the information is reported only once.
AD machines in the domain are registered in DNS as being configured for AD. DDM retrieves the FQDN (fully qualified domain name) from every Exchange discovery. This is the name of Exchange within AD. To report such an Exchange, DDM tries to resolve the FQDN to an IP address, as follows:

DDM uses the default Probes DNS to resolve the Exchange FQDN. If this fails, DDM uses the target Domain Controller as the DNS. This is because in many cases the DNS server runs on the same machine as the Domain Controller. DDM runs the command "netstat <FQDN> <targetDC>" in the Probe's local Shell. If this fails, DDM skips this Exchange instance.
Note: A message is displayed by the job if the FQDN cannot be resolved either by a local DNS or by using the target Domain Controller as the DNS: Cannot resolve IP address for host '<host>', Exchange Server won't be reported
2 Prerequisites Set Permissions

Define at least one set of LDAP protocol credential. These credentials should enable connecting to a Domain Controller through the LDAP protocol and performing searches. DDM does not modify information in AD. The queried nodes reside in the Configuration partition under the following nodes:

CN=Services,CN=Microsoft Exchange node CN=Sites node
45
The LDAP protocol credentials should include:
User name and password. Use the user account from the target domain. For all nodes that are to be queried, give List Contents and Read all properties permissions. Authentication type. Simple. For credentials information, see LDAP Protocol in the Discovery and Dependency Mapping Guide..
3 Prerequisites Discover a Domain Controller

To discover the Exchange topology with AD, DDM must first find a Domain Controller with an available LDAP connection. a Activate the Range IPs by ICMP job, to ping the target host on which the Domain Controller runs (Discovery Modules > Network Basic). b Activate the TCP Ports job against the target host, to discover open LDAP ports (Discovery Modules > Network Advanced). c Activate the Active Directory Connection by LDAP job, to discover the Domain Controller on the target host (Discovery Modules > Application Active Directory).
DDM discovers both Microsoft Exchange Server 2003 and Microsoft Exchange Server 2007 with the LDAP protocol.

LDAP. For an explanation, see Prerequisites Set Permissions on page 45.
Activate the Microsoft Exchange Topology by LDAP job (Discovery Modules > Application Microsoft Exchange). This job discovers both 2003 and 2007 versions of Exchange.
46

All components responsible for Exchange in DDM are bundled in the Microsoft_Exchange_Server package. For details on the package, click the Readme link in the Package Manager.
8 Additional CITs
The following CITs have been added to the Microsoft Exchange Server Package:

Routing Group Connector SMTP Connector Exchange Routing Connector Send Connector Receive Connector Exchange Storage Group Exchange Mailbox Database Routing group
9 Deprecated CITs
The following CITs are deprecated; they remain in the package but are no longer reported:

Directory Service Access DC Exchange Message queue Exchange link Exchange Routing Group
10 Modified CITs
The following CITs are modified:

Exchange System is now Exchange Organization Microsoft Exchange Server includes a new attribute: is_master.
47
11 Discovered CITs

Active Directory Forest Active Directory Site Active Directory System Administrative Group Contained Container link Exchange Folder Exchange Folder Tree Exchange Organization Exchange Routing Connector Exchange role Host IP Member Microsoft Exchange Server Routing Group Connector Routing group SMTP Connector
12 Trigger TQL
The Trigger TQL (trigger_domainctl_ldap) is part of the Active Directory package.
48
13 Trigger CI
DomainController
14 CI Attributes
CI IP DomainController Attribute Value NOT IP Probe Name Is null NOT Reference to the credentials entry dictionary Is null AND NOT Application IP Is null Service Address Name Equal ignore case ldap
15 Patterns
ms_exchange_topology_by_ldap. This pattern discovers Microsoft Exchange Server, versions 2003 and 2007.
16 Topology Maps
For the Microsoft Exchange Server 2007 topology view, see Topology Maps on page 42. For the Microsoft Exchange Server 2003 topology view, see Topology Map on page 38.

Currently Exchange Folders are not reported through the Microsoft Exchange Topology by LDAP job.
49
50
4
SAP

Concepts
Discover SAP ABAP on page 52 Discover SAP Java on page 56 Discover SAP Solution Manager on page 58
Overview
The SAP tasks discover either SAP ABAP or SAP Java. The Application Server ABAP provides the complete technology and infrastructure to run ABAP applications. The Application Server Java provides a Java 2 Enterprise Edition (Java EE) environment for developing and running Java EE programs.
Note: To discover more than one SAP system, it is recommended to create a SAP Protocol credential with a different user and password for each SAP system. For details on the SAP protocol and required user permissions, see SAP Protocol in Discovery and Dependency Mapping Guide.
Tasks
51
Chapter 4 SAP
Discover SAP ABAP

This task discovers SAP ABAP architecture, SAP application components, SAP transactions, and SAP Solution Manager business process definitions. This task includes the following steps:

Supported Versions on page 52 Prerequisites Install Java Connectors on page 52 Network and Protocols on page 53 Discovery Workflow on page 53 Configure Pattern Parameters on page 55
SAP BASIS and SAP AS (Architecture layer). Versions 3.x to 6.x. SAP JCo. Version 3.0 (recommended). Note that DDM can discover SAP as long as the default SAP JCo provided with DDM is the correct version. If you are running an older version of SAP JCo, DDM may not be able to connect to SAP version 6.x. SAP J2EE client. The version should match the relevant SAP system version.
2 Prerequisites Install Java Connectors

a Download the SAP JCo package from the Tools & Services window of SAP JCo in SAP Service Marketplace: https://websmp101.sap-ag.de/~form/ sapnet?_SHORTKEY=01100035870000463649 b Extract sapjco-ntintel-2.0.8.zip to a temporary directory (for example: C:\temp) on the HP Universal CMDB machine. c Create a sap directory (in lowercase) in the C:\hp\DDM\DiscoveryProbe \root\ext\ directory on the machine where the Probe is installed. d Copy sapjco.jar from the temporary directory to the C:\hp\DDM \DiscoveryProbe\root\ext\sap\ directory on the machine where the Probe is installed.
52
Chapter 4 SAP
e Copy sapjcorfc.dll from the temporary directory to the %winnt%\system32 directory on the machine where the Probe is installed. Also copy the file to the C:\hp\DDM\DiscoveryProbe\ root\ext\dll folder. f Copy librfc32.dll from the temporary directory to the %winnt%\system32 directory. Also copy the file to the C:\hp\DDM\ DiscoveryProbe\root\ext\dll folder. g Verify that the MSVCR71.dll and MSVCP71.dll files are located in the %winnt%\system32 directory.

The following protocols enable connection to a machine to verify whether a SAP system is installed on it:
NTCmd. For credentials information, see NTCMD Protocol in Discovery and Dependency Mapping Guide. SSH. For credentials information, see SSH Protocol in Discovery and Dependency Mapping Guide. Telnet. For credentials information, see Telnet Protocol in Discovery and Dependency Mapping Guide. SAP. For credentials information, see SAP Protocol in Discovery and Dependency Mapping Guide.
a In the Run Discovery window, activate the modules in the following order:

Network Basic (Range IPs by ICMP, Host Connection By Shell). Host Resources and Applications (Host Resources and Applications by Shell). This job discovers SAP software elements and processes. Network Advanced (TCP Ports). Also, activate the SAP System by Shell job. This job discovers SAP J2EE Central Services and a SAP system without SAP J2EE credentials.
53
Chapter 4 SAP
Web Servers Basic (WebServer Detection using TCP Ports). If the SAP system has an ITS configuration, to discover the ITS entities of the SAP system, run this job as a prerequisite to the SAP discovery that discovers ITS entities. Application SAP
SAP System By Shell. This job searches for a SAP system by referring to the file system and process list. The SAP CI that is created is used as a trigger for the SAP ABAP Connection by SAP JCO job. This job needs Shell credentials and not SAP credentials. SAP ABAP Connection by SAP JCO. This job connects to the SAP system and creates a SAP System CI with a credentials ID. Subsequently, the other ABAP jobs use these credentials to connect to SAP. SAP ABAP Topology by SAP JCO. Discovers infrastructure entities in the SAP system: hosts, application servers, work processes, databases, SAP clients, configuration files, software components (discovered as configuration files), and support packages (discovered as configuration files). SAP Applications by SAP JCO. You run this job to discover the application components of this system. The result of this job may be many CIs. To omit unnecessary CIs, you can configure the pattern parameters. For details, see Configure Pattern Parameters on page 55. SAP ITS by NTCMD. Discovers Internet Transaction Server (ITS) entities (Application Gateway and Web Gateway). SAP Solution Manager by SAP JCO. Discovers SAP Solution Manager components. SAP Solution Manager discovery enables you to discover the business process hierarchy. For details, see Discover SAP Solution Manager on page 58.
b For details on the CIs that are discovered, see the Statistics table in the Details tab, or click the View CIs in Map button. For details, see Discovery Job Details Pane in Discovery and Dependency Mapping Guide. c Verify that DDM discovered the appropriate components. Access the SAP_ABAP_Topology view in View Manager and verify that the map displays all components.
54
Chapter 4 SAP
d To view the CIs discovered by the SAP discovery, access the Statistics Results pane, select a CI, and click the View Instances button, to open the Discovered by window. For details, see Statistics Results Pane and Discovered CIs Dialog Box in Discovery and Dependency Mapping Guide.
5 Configure Pattern Parameters

To omit unnecessary CIs, you can configure the pattern parameters, as follows: a Access the SAP pattern: Manage Discovery Resources > SAP_Discovery package > Patterns > SAP_Dis_Applications. b Select the Pattern Signature tab and locate the Discovery Pattern Parameters pane.
c Set one of the following parameters, and click OK to save the changes:

To discover all SAP transactions: Set getAllTransactions to false. To discover active SAP transactions: Set getActiveTransactions to true. To discover SAP transactions that have been changed by discovered transports:

Set getTransChanges to true. Set the from date (transChangesFromDate) and the to date (transChangesToDate). The date format is YYYYMMDD. Set the from time (transChangesFromTime) and the to time (transChangesToTime). The time format is HHMMSS.
55
Chapter 4 SAP
Discover SAP Java

The SAP for Java discovery process enables you to discover SAP JAVA architecture and J2EE applications on the SAP JAVA server. This task includes the following steps:

Prerequisites on page 56 Network and Protocols on page 57 Discovery Workflow on page 57
1 Prerequisites
a Add the following *.jar files to the C:\hp\DDM\DiscoveryProbe\root\ lib\collectors\probeManager\discoveryResources\j2ee\sap directory on the Probe machine:

sapj2eeclient.jar logging.jar exception.jar sapxmltoolkit.jar
The files reside in the \usr\sap\<SID>\<instance name>\j2ee\j2eeclient directory on the SAP system machine. b Add the com_sap_pj_jmx.jar file to the C:\hp\DDM\DiscoveryProbe\ root\lib\collectors\probeManager\discoveryResources\j2ee\sap directory on the Probe machine: The file resides in the \usr\sap\<SID>\<instance name>\j2ee\admin\lib directory on the SAP system machine.
56
Chapter 4 SAP
Note: If you create version folders under the \j2ee\sap directory on the Probe machine, you can connect to several SAP versions, by adding *.jar files to each folder. For example, to connect to versions 7.0 and 6.4:

Create two folders under the sap folder. Name the folders 6.x and 7.x. Place the relevant *.jar files in these folders.

The following protocol enables connection to a machine and verification whether a SAP system is installed on it:
SAP JMX. For credentials information, see SAP JMX Protocol in Discovery and Dependency Mapping Guide.
In the Run Discovery window, activate the modules in the following order:

Network Basic (Range IPs by ICMP, Host Connection By Shell). Host Resources and Applications (Host Resources and Applications by Shell). This job discovers SAP software elements and processes. Network Advanced (TCP Ports). Also, activate the SAP System by Shell job. This job discovers SAP J2EE Central Services and a SAP system without SAP J2EE credentials. Application SAP (SAP Java Topology by SAP JMX). This job discovers infrastructure entities in the SAP J2EE system: hosts, application servers, databases. Interfaces, Libraries, and Services are discovered as configuration files.
57
Chapter 4 SAP
Discover SAP Solution Manager

Often, an environment includes several SAP systems, each one using a different set of credentials (for instance, user name, password, system number, or client number). To prevent the need to create a set of credentials for each SAP system, you register all the SAP systems with the SAP Solution Manager, and DDM discovers all systems (and their topology) with this one set. This task includes the following steps:

Prerequisites on page 58 Supported Versions on page 59 Network and Protocols on page 59 Discovery Workflow on page 59 Discovered CITs on page 60 Topology Map on page 60
1 Prerequisites
a Run the SAP ABAP Connection by JCO job. This job triggers the SAP Solution Manager Topology by SAP JCO job on a specific, discovered SAP system (if it is signed by the SAP Solution Manager). b To run SAP Solution Manager, ask the SAP Solution Manager admin to give you permissions on the following objects for the given profile:
For the S_RFC object, obtain privileges: RFC1, SALX, SBDC, SDIF, SDIFRUNTIME, SDTX, SLST, SRFC, STUB, SUTL, SXMB, SXMI, SYST, SYSU, SEU_COMPONENT. For the S_XMI_PROD object, obtain:
EXTCOMPANY=MERCURY;EXTPRODUCT=DARM;INTERFACE=XAL
58
Chapter 4 SAP
For the S_TABU_DIS object, obtain:

DICBERCLS=SS; DICBERCLS=SC; DICBERCLS=&NC& ACTVT=03
SAP Solution Manager versions 6.x, 7.x.

SAP. For credentials information, see SAP Protocol in the Discovery and Dependency Mapping Guide.
Method 1:

Run the SAP TCP Ports job to discover SAP ports. Run the SAP ABAP Connection by JCO job. Run the SAP Solution Manager Topology by SAP JCO job. Method 2:
Run the Host Resources by ... jobs to discover SAP (ABAP or J2EE) Application Server and/or SAP (ABAP or J2EE) Central Services. Run the SAP System by Shell job to create a SAP system CI (but without defining whether it is the SAP Solution Manager). Run the SAP ABAP Connection by JCO job. Run the SAP Solution Manager Topology by SAP JCO job. All SAP systems that are defined as SAP Solution Manager (by the SAP ABAP Connection by JCO job) are triggers for the SAP Solution Manager Topology by SAP JCO job.
59
Chapter 4 SAP
5 Discovered CITs
The following CITs are discovered by the SAP Solution Manager Topology by SAP JCO job:
6 Topology Map
To view the SAP Solution Manager Topology by SAP JCO map: Run Discovery > select Application SAP > SAP Solution Manager Topology by SAP JCO > Details pane. Click the View CIs in Map button.
60
5
Siebel
Concepts
Discover Siebel Topology on page 62
Overview
Using the Siebel patterns, you can run an automatic Siebel discovery to create the Siebel world, together with its components, inside HP Universal CMDB. During discovery:
All Siebel-related IT entities that reside in the organization are discovered and configuration items (CIs) are written to the CMDB. The relationships between the elements are created and saved in the CMDB. The newly generated CIs are displayed when the Siebel Enterprises view is selected in View Explorer under the Siebel Enterprises root CI.
Note: Verify that all Siebel server IP addresses are included in the range. If not all servers can be covered with one IP range, you can split the range into several ranges.
Tasks
61
Chapter 5 Siebel
Discover Siebel Topology

This task describes how to discover Siebel topology. This task includes the following steps:

Prerequisites Copy the driver Tool to the Probe Server on page 62 Network and Protocols on page 63 Discovery Workflow on page 63 Discovered CITs on page 64 Topology Map on page 66 Troubleshooting and Limitations on page 67
1 Prerequisites Copy the driver Tool to the Probe Server

The driver tool is used to extract data about the enterprise structure from Siebel.
Note: If you are working with different versions of Siebel in your organization, make sure you use a driver tool with a version that is appropriate for the Siebel server.
To copy the driver tool to the Probe server: a Copy the driver Command Line Interface (CLI) tool from the Siebel server to any folder on the Probe server. b It is recommended to run the Siebel connection test to validate the driver installation. To run the connection test, open the command line on the Probe server and change directory to the location of the driver.exe file. c Run from the command line:
>driver /e [site_name] /g [gateway_host] /u [username] /p [password]
If the connection is established successfully, the Command Prompt window displays the driver prompt and a status message about the number of connected servers.
62
Chapter 5 Siebel

Set up the following protocols for the Windows platform:
WMI. For credentials information, see WMI Protocol in Discovery and Dependency Mapping Guide. NTCmd. For credentials information, see NTCMD Protocol in Discovery and Dependency Mapping Guide. Siebel Gateway. For credentials information, see Siebel Gateway Protocol in Discovery and Dependency Mapping Guide. Set up the following protocols for the UNIX platform:
SSH. For credentials information, see SSH Protocol in Discovery and Dependency Mapping Guide. Telnet. For credentials information, see Telnet Protocol in Discovery and Dependency Mapping Guide. Siebel Gateway. For credentials information, see Siebel Gateway Protocol in Discovery and Dependency Mapping Guide.
a For Siebel discovery to run, you must copy the driver tool to the Probe server. For details, see Prerequisites Copy the driver Tool to the Probe Server on page 62. b To trigger the discovery of Siebel networking features, add a Network CI to the CMDB. For details, see New CI Dialog Box in Model Management. c In the Run Discovery window, activate the modules in the following order:

Network Basic (Class C IPs by ICMP, Host Connection by WMI) Application Siebel (Siebel DB by TTY)
d To discover the Web tier, activate the following modules:

Network Advanced (TCP Ports) Application Siebel (Siebel Web Applications by NTCMD, Siebel Web Applications by TTY, Siebel DB by WMI and NTCMD) Web Server Basic (WebServer Detection using TCP Ports)
63
Chapter 5 Siebel
e To discover Siebel, activate all the jobs in the Application Siebel module.
Note: The following enrichment patterns automatically run in the background during discovery: Siebel_Route_WebApp_To_Component. Builds the route between Siebel Web Application CIs and Siebel Component CIs. Siebel_Web_To_Middle_Tier. Builds the route between the Web tier and the middle tier when the Siebel enterprise uses a Resonate server for load balancing.
f For details on the CIs that are discovered, see the Statistics table in the Details tab.
4 Discovered CITs SIEBEL_DIS_APP_SERVERS
SIEBEL_DIS_APP_SERVER_CONFIG
64
Chapter 5 Siebel
SIEBEL_DIS_GATEWAY_CONNECTION_(GTWY)
SIEBEL_DIS_WEBAPPS_UNIX
SIEBEL_DIS_DB_UNIX
SIEBEL_DIS_DB_NT
65
Chapter 5 Siebel
SIEBEL_DIS_WEBAPPS_NT
5 Topology Map
66
Chapter 5 Siebel

The Siebel DB by TTY job cannot discover virtual Siebel application servers (with a different name and configuration to the actual Siebel application server) running on UNIX machines.
67
Chapter 5 Siebel
68
6
UDDI Registry
Concepts
Discover UDDI Processes on page 69
Overview
The UDDI discovery process enables you to discover Web services from a UDDI registry. DDM queries the UDDI registry for its Web services, including non-SOAP services, or for a specific publisher service (if defined in the UDDI Registry protocol). The Web services found in the UDDI registry are represented by a webservice CI in the CMDB and the registry is created as a uddiregistry CI.
Tasks
Discover UDDI Processes


Supported Versions on page 70 Network and Protocols on page 70 Discovery Workflow Optional on page 70 Topology Map on page 71 Troubleshooting and Limitations on page 71
69
Chapter 6 UDDI Registry
DDM supports UDDI versions 2 and 3.

Set up the UDDI protocol. For credentials information, see UDDI Registry Protocol in Discovery and Dependency Mapping Guide.
In the Run Discovery window, locate the Application UDDI Registry module. Activate the WebServices by URL job. For details on the CIs that are discovered, see the Statistics table in the Details tab.
4 Discovery Workflow Optional

To enter the name of the service publisher whose services must be published: a Access the Manage Discovery Resources window. b In the Discovery Resources pane, locate the Webservices package and select the UDDI_Registry pattern. c In the Pattern Signature tab, in the Discovery Pattern Parameters pane, select the organization parameter and click the Edit button. d In the Parameter Editor:

In the Value box, enter the name of the service publisher. In the Description box, enter the required description of the organization.
e Save the changes.
70
5 Topology Map
The following depicts the topology of the SOA_UDDI_View:

When activating the WebServices by URL job, the Web services being discovered should be authentication-less, that is, they can be accessed without credentials (user name/password).
71
72
Part III
The Cluster Modules
74
7
Microsoft Cluster
Tasks
Discover Microsoft Cluster Servers on page 75
Discover Microsoft Cluster Servers

The MS Cluster discovery process enables you to discover the topology of a Microsoft Cluster Server on the network. This task includes the following steps:

Network and Protocols on page 75 Discovery Workflow on page 76 Topology Map on page 76
WMI. For credentials information, see WMI Protocol in Discovery and Dependency Mapping Guide. NTCmd. For credentials information, see NTCMD Protocol in Discovery and Dependency Mapping Guide.
75
Chapter 7 Microsoft Cluster
In the Run Discovery window, activate the modules in the following order:

Network Basic (Host Connection by Shell) Network Host Resources and Applications Cluster Microsoft Cluster (MS Cluster by NTCMD) For details on the CIs that are discovered, see the Statistics table in the Details tab.
3 Topology Map
The Microsoft Cluster Server View shows the MS Cluster and the cluster software (the agents running on the actual host) as its members. The cluster is composed of several Clustered Servers that are the virtual hosts or servers providing the platform for the virtual service used by the cluster clients (through the virtual IPs). The cluster contains Microsoft Cluster Groups. Each of the groups contains Microsoft Cluster Resources. For each Cluster Resource Group, it is assumed that different, dedicated, virtual IPs are being assigned; these IPs are configured for the use of the cluster clients.
76
8
Veritas
Tasks
Discover Veritas Cluster Servers on page 77
Discover Veritas Cluster Servers

The Veritas Cluster discovery process enables you to discover Veritas Cluster Servers (VCS), and their member machines (also referred to as nodes), that activate the discovered resources provided by the cluster. This task includes the following steps:

Overview on page 77 Network and Protocols on page 78 Discovery Workflow on page 78 Discovered CITs on page 78 Topology Map on page 79
1 Overview
A Veritas Cluster group is a collection of dependent or related resources that is managed as a single unit. Each Veritas Cluster group is linked to a designated node, which is responsible for activating the resources contained in the group. If a failure occurs in the designated node, the responsibility for activating the resources is switched over to a different node.
77
Chapter 8 Veritas
Veritas Clusters are composed of several clustered servers. Each server is responsible for running certain services and applications. The servers are used as backups for one another. When a system components fails, another server takes over to provide the necessary service.
SSH. For credentials information, see SSH Protocol in Discovery and Dependency Mapping Guide. Telnet. For credentials information, see Telnet Protocol in Discovery and Dependency Mapping Guide.
In the Run Discovery window, activate the Veritas Cluster by Shell job.
4 Discovered CITs
For details on the CIs that are discovered, see the Statistics Results table in the Details tab. For details, see Statistics Results Pane in Discovery and Dependency Mapping Guide.
78
Chapter 8 Veritas
5 Topology Map
This view shows the top layer of the Veritas Cluster topology. It displays the discovered Veritas Cluster and the clustered software resources that are members of that cluster. Each software resource is linked by a member relationship to the Veritas Cluster.
79
Chapter 8 Veritas
Double-click the required node to drill down to the CIs folded underneath.
80
Part IV
The Database Modules
82
9
DB2
Tasks
Discover IBM DB2 Databases on page 83
Discover IBM DB2 Databases

This module discovers IBM DB2 Server databases and their components on the network. This task includes the following steps:

Prerequisites on page 83 Network and Protocols on page 84 Discovery Workflow on page 84 Discovered CITs on page 84 Topology Map on page 84 Troubleshooting and Limitations on page 85
1 Prerequisites
Verify the user name, password, and port used by IBM DB2 Server.
83
Chapter 9 DB2

IBM DB2 Server uses the SQL protocol. For credentials information, see SQL Protocol in Discovery and Dependency Mapping Guide. In the Database Type box, choose db2.
In the Run Discovery window, activate the jobs in the Database DB2 module in the following order:

DB2 Connection by SQL DB2 Topology by SQL Databases TCP Ports
4 Discovered CITs
For details on the CIs that are discovered, see the Statistics table in the Details tab. For details, see Statistics Results Pane in Discovery and Dependency Mapping Guide.
5 Topology Map
The following image depicts the topology of the IBM DB2 Server view:
This view shows a host on which an IBM DB2 Server and DB2 Schema are installed, the processes that communicate with the server (connected by DB Client links), and the DB tablespaces.
84
Chapter 9 DB2

To perform an IBM DB2 discovery, copy the following files from the installation folder on the IBM DB2 machine to the DDM Probe machine:

db2java.zip db2jcc.jar db2jcc_license_cisuz.jar db2jcc_license.jar Place the files in the following folder: C:\hp\DDM\DiscoveryProbe\root\ lib\collectors\probeManager\discoveryResources\db\db2. Restart the Probe.
85
Chapter 9 DB2
86
10
MS-SQL
Discovery by OS Credentials on page 87 Tasks

Concepts
Discover Microsoft SQL Server Database Application on page 88 Discover SQL Server by OS Credentials on page 90
Discovery by OS Credentials
There are two approaches to identifying MS SQL Server instance names by OS credentials. The changes appear in the Host_Resources_Basic package:
By Process Command Line. The SQL Server process usually includes the MS SQL Server instance name in its command line. DDM extracts this instance name to a CI.
Note: A process command line cannot be retrieved by the SNMP protocol. Therefore, SNMP cannot be used to discover the MS SQL Server instance name, and DDM reports the generic software element instead.
Using Windows Services. DDM checks existing services for those that include sqlservr.exe in the command line and extracts the instance name from the service name (since the service name reflects the instance name).
Tasks
87
Chapter 10 MS-SQL
Discover Microsoft SQL Server Database Application

This task describes how to discover the Microsoft SQL Server database application. This task includes the following steps:

Supported Versions on page 88 Prerequisites on page 88 Network and Protocols on page 88 Discovery Workflow on page 88 Discovered CITs on page 89 Topology Map on page 89
Microsoft SQL Server 2000, 2005.
2 Prerequisites
Verify the user name, password, and port used by Microsoft SQL Server.

Microsoft SQL Server uses the SQL protocol. For credentials information, see SQL Protocol in Discovery and Dependency Mapping Guide.
In the Run Discovery window, activate the jobs in the Database MS-SQL module in the following order:

Databases TCP Ports MSSQL Connection by SQL MSSQL Topology by SQL
88
Chapter 10 MS-SQL
5 Discovered CITs
For details on the CIs that are discovered, see the Statistics table in the Details tab. For details, see Statistics Results Pane in Discovery and Dependency Mapping Guide.
6 Topology Map
This view shows the hosts on which Microsoft SQL Server is installed. Microsoft SQL Server contains the databases, users, SQL jobs, and configuration files of this database, and maintenance plans.
89
Chapter 10 MS-SQL
Discover SQL Server by OS Credentials


Overview on page 90 Discovery Jobs on page 91 Discovery Changes on page 91 Discovery When Host Information Is Available on page 91 Discovery When Host Information Is Not Available on page 91
1 Overview
This section describes how DDM discovers MS SQL Server CIs, using operating system (OS) credentials. DDM creates an identifiable SQL Server CI, rather than a generic Software Element CI. Previously, SQL Server discovery assumed the existence of a process with the name of sqlservr.exe. Once DDM found this process, generic software elements with a MSSQL DB value in the data_name attribute were reported to UCMDB. The changes rectify the following issues:
DDM did not discover instance name information, so identifiable CIs could not be reported. When several instances of SQL Server existed in the environment, DDM reported only one software element to UCMDB.
90
Chapter 10 MS-SQL
2 Discovery Jobs
The following jobs discover MS SQL Server components by OS credentials:

Host Resources and Applications by Shell Host Resources and Applications by WMI
3 Discovery Changes
The following changes have been made:
When running discovery with OS credentials, an identifiable SQL Server CI is reported, instead of the generic Software Element CI. DDM can now resolve the SQL Server instance name. The Probe can report multiple SQL Server instances, each of them linked by a depend link to its own sqlservr.exe process. DDM now supports SQL Server named instances. DDM supports discovery of the following SQL Server versions: MSSQL 2000, 2005, 2008.
4 Discovery When Host Information Is Available

DDM runs the following SQL command:
select SERVERPROPERTY ('InstanceName')
5 Discovery When Host Information Is Not Available

DDM runs the following SQL command:
select @@servername
91
Chapter 10 MS-SQL
92
11
MySQL Replication Between Databases
Concepts
Discover MySQL Configuration and Replication Jobs on page 94
Overview
This chapter explains how to discover MySQL database servers that replicate data in a master-slave relationship. Replication enables data from one MySQL database server (the master) to be replicated to one or more MySQL database servers (the slaves). For details on replication, see the MySQL manual on the MySQL Web site: http://dev.mysql.com/doc/refman/5.0/en/replication-howto.html. Currently all information about databases is retrieved through Shell protocols from the MySQL configuration file. The job responsible for MySQL discovery is MySQL by Shell (Database MySQL module).
Tasks
93
Chapter 11 MySQL Replication Between Databases
Discover MySQL Configuration and Replication Jobs

This task describes how to discover the MySQL configuration and replication jobs. This task includes the following steps:

Supported Versions on page 94 Prerequisites User Permissions on page 95 Required Protocols on page 95 Discovery Workflow on page 95 The MySQL by Shell Job on page 96 Trigger TQL on page 97 Configuration Item Types on page 97 CIT Attributes on page 97 Links on page 98 Discovered CITs on page 99 The MySQL Package on page 99 Input TQL on page 100 Triggered CI Data on page 100 Views MySQL Replication Topology on page 100 Limitation on page 101

MySQL versions 4.x and 5.x are supported. The following operating systems are supported: Windows, Solaris, and Linux.
94
2 Prerequisites User Permissions

To retrieve all relevant information, DDM must have read permissions for the $MYSQL_HOME directory and for executing mysqld (mysqld.exe or mysqld-nt.exe for Windows) with the following parameters:
mysqld --verbose --help
mysqld --version
If the my.cnf (my.ini) file is located outside the $MYSQL_HOME directory, you must add permissions for reading to it.
3 Required Protocols
Verify that the following protocols are configured:
SSH. For credentials information, see SSH Protocol in Discovery and Dependency Mapping Guide. Telnet. For credentials information, see Telnet Protocol in Discovery and Dependency Mapping Guide. NTCmd. For credentials information, see NTCMD Protocol in Discovery and Dependency Mapping Guide.
a Run the Host Connection by Shell job to create Shell CITs. b Run any of host resources jobs to gather information about processes running on the host. c Run the MySQL by Shell job to retrieve information about MySQL configuration and replication jobs. For details, see the following step.
95
5 The MySQL by Shell Job

This section explains how DDM discovers the MySQL server:

The MySQL by Shell job connects to the remote host using Shell credentials. The job checks for the existence of the path of the MySQL configuration file by executing the following command:
mysqld --verbose --help
If the job cannot find the configuration file with this command, it assumes the file is located in the default configuration file path:

UNIX or Linux: /etc/my.cnf Windows: ../my.ini
The job tries to retrieve the attribute values from the configuration file. The job either reads the attribute values from the command line, or reads the configuration file to find the values of the attributes that were not found in the command line. Example of command line with attribute values:
mysqld-nt.exe --defaults-file=C:\hp\DDM\DiscoveryProbe\MySQL\my.ini DDM_Probe_DB
If the job does not find any attribute values, it takes the default values from the MySQL documentation. For details of the MySQL attributes, see CIT Attributes on page 97.
The job creates the MySQL CIs with appropriate attribute values and links. The job now checks if this MySQL instance is a replica. If it is a replica, the job attempts to discover a master host and master user. The version of the MySQL engine is taken from the mysqld --version command output. The job creates the MySQL replication CI with appropriate attribute values and links.
96
6 Trigger TQL
7 Configuration Item Types

Name Parent CIT Uses Existing Attributes database_dbsid Uses New Attributes server_id, database_datadir, database_max_ connections master_user, master_connect_ retry Description
MySQL
Database
CIT represents the MySQL database
MySQL Replication
DB Scheduler Job
CIT represents the MySQL Replication job
8 CIT Attributes MySQL

server_id. The unique ID for each slave and master node. database_datadir. Path to the database root (datadir in the configuration file). database_max_connections. The maximum number of concurrent sessions allowed by the MySQL server (max_connections in the my.ini file). database_dbsid. The unique identifier for running the MySQL instance-process port. The format is MySQL on port ####.
97
MySQL Replication

master_user. A user name used when connecting to the master server. master_connect_retry. The number of seconds that the slave thread sleeps before trying to reconnect to the master, if the master goes down or the connection is lost.
9 Links
Source mysql mysql mysql_replication Destination configfile mysql_replication service_address Link Type Container link Container link Client-Server Cardinality 1..1 1..1 1..1
98
10 Discovered CITs
11 The MySQL Package

All components responsible for MySQL discovery by Shell in DDM are bundled in the MySQL package (in the Database category in the Package Manager). For details, see Chapter 15, Package Manager in Model Management.
99
12 Input TQL
13 Triggered CI Data
14 Views MySQL Replication Topology
100
15 Limitation
There are two main approaches to running several active MySQL instances on one host:
Two MySQL instances are each run on a different port, for example, one on 134.44.1.1:3306 and the second on 134.44.1.1:3307. A host has several IPs, and each MySQL process is bound to its own IP, for example, 134.44.1.1:3306 and 134.44.1.2:3306. In the second case, as the key identifier that differentiates one MySQL CI from another is a port number (without an IP), the job cannot differentiate between the two MySQL instances and merges them into one CI.
101
102
12
Oracle

Tasks
Discover Oracle Databases on page 103 Discover Oracle Real Application Cluster (RAC) on page 106
Discover Oracle Databases

This task describes how to discover Oracle databases. This discovery adds a valid credentials ID to the CMDB. You can then use this CI to fully discover the database. This task includes the following steps:

Supported Versions on page 103 Prerequisites on page 104 Network and Protocols on page 104 Discovered CITs on page 104 Topology Map on page 105
Oracle 8, 9, 10.
103
Chapter 12 Oracle
2 Prerequisites
Run Databases TCP Ports. (The ports that are discovered are those open TCP\UDP ports running on a host with known server ports.)

To discover Oracle databases, use the following protocol: SQL. For credentials information, see SQL Protocol in Discovery and Dependency Mapping Guide.
4 Discovered CITs
owner, dbjob, dbuser, process, dbclient, dblinkobj, dbsnapshot, dbdatafile, dbtablespace, db_controlfile, db_redofile, db_redofilegroup, db_archivefile, oracle, dbschedulerjob, service, rac The following attributes are updated:

database_dbversion database_dbtype database_dbsid database_dbport
104
Chapter 12 Oracle
5 Topology Map
105
Chapter 12 Oracle
Discover Oracle Real Application Cluster (RAC)

This section explains how to run the Oracles Listeners by Shell and the Oracle RAC Topology by Shell jobs. This section includes the following topics:

Overview on page 106 Supported Versions on page 107 Prerequisites on page 107 Required Protocols on page 107 Discovery Workflow on page 108 The Oracle Listeners by Shell Job on page 108 The Oracle RAC Topology by Shell Job on page 110 Topology on page 113 Configuration Items on page 113 The Oracle Package on page 114 Oracle View on page 115 Troubleshooting and Limitations on page 115
1 Overview
DDM discovers information about Oracle RAC through the Shell protocols from the Oracle configuration files listener.ora and tnsnames.ora, and through the lsnrct utility.
106
Chapter 12 Oracle
The following jobs are responsible for Oracle RAC discovery (in the Database Oracle module):

Oracle Listeners by Shell Oracle RAC Topology by Shell
Oracle RAC over Oracle DB 10 and 11 is supported.
3 Prerequisites
a To retrieve all relevant information, verify that DDM has:

Read permissions for the $ORACLE_HOME\network\admin directory The correct execute permissions for $ORACLE_HOME\bin\lsnrctl and for the corresponding library (lib) and message files.
b The Oracle Listeners by Shell job. Verify that the RAC relative processes are running on the Oracle database. The file names begin with ora_lms, ora_lmd, ora_lck, and oracm. c The Oracle RAC Topology by Shell job. The Listened IPs of the Listener CIT must be not NULL. d Run the Host Connection by Shell job, to activate Shell CITs.
4 Required Protocols
Verify that the following protocols are configured:
NTCmd. For credentials information, see NTCMD Protocol in the Discovery and Dependency Mapping Guide. SSH. For credentials information, see SSH Protocol in the Discovery and Dependency Mapping Guide. Telnet. For credentials information, see Telnet Protocol in the Discovery and Dependency Mapping Guide.
107
Chapter 12 Oracle
a Run any of the host resources jobs that gather information about processes running on the host. If DDM discovers TNS Listener processes, the job creates Oracle TNS Listener CIs and an Oracle DB CI together with its connected processes. b To discover Oracle TNS Listener CIs with full data, run the Oracle Listeners by Shell job. This job connects to the host and retrieves the required data for the Oracle TNS Listener CI. For details, see The Oracle Listeners by Shell Job on page 108. c To discover Oracle RAC topology, run the Oracle RAC Topology by Shell job. This job connects to the hosts with full listeners and discovers RAC. For details, see The Oracle RAC Topology by Shell Job on page 110. For details on undiscovered elements, see Troubleshooting and Limitations on page 115.
6 The Oracle Listeners by Shell Job

This job triggers on Oracle databases that have RAC related processes. The job:

Connects to the remote host by Shell. Checks for the ORACLE_HOME environment variable. If the variable is not defined, the job takes the ORACLE_HOME value from the job pattern (if defined).
Reads the Oracle TNS listener configuration file, stored in $ORACLE_HOME/network/admin/listener.ora, and performs further parsing. Retrieves a full list of IP addresses to which this particular listener is listening. Checks for listener status using the $ORACLE_HOME/bin/lsnrctl status. Retrieves known services and listener status from the output.
108
Chapter 12 Oracle
Trigger TQL
The pattern used by the job is Oracle_Listeners_by_Shell. To access: Manage Discovery Resources > Discovery Resources pane > Oracle > Patterns > Oracle _Listeners_by_Shell.
Input TQL
Used Scripts. oracle_listeners_by_shell.py
Triggered CI Data
109
Chapter 12 Oracle
Discovered CITs
OracleHomes. Used when no ORACLE_HOME environment variable is defined. This value must be the same as the parameter in the Oracle RAC Topology by Shell job.
7 The Oracle RAC Topology by Shell Job

This job:

Connects to the remote host by Shell. Checks for the ORACLE_HOME environment variable. If it is not defined, the job uses the OracleHome value from the job pattern.
Retrieves RAC parameters such as Service Name and Nodes from the $ORACLE_HOME/network/admin/tnsnames.ora file. Checks if this RAC instance is running, by parsing the lsnrctl status output.
Note: Nodes are cited in the tnsnames.ora file by their internal IP or by their internal domain name. If the domain name appears, DDM resolves it.
Retrieves the full list of Listened IPs from the input TQL, for all listeners matching the TQL. Parses this attribute's values from the list of listened IPs, to retrieve the Host Primary Domain name that corresponds to the MAC address. This is needed since the RAC CI's data_name key attribute must consist of a list of all the node domain names separated by the colon symbol (:).
110
Chapter 12 Oracle
Looks up the full node name in the build table sorted by IP address. The result is the Host Primary Domain name for each node. At this stage, the following information is available: the RAC Service Name, the fully qualified domain names of all the RAC nodes, and a RAC instances count.
Creates the RAC CI. The pattern used by the job is Oracle_RAC_Topology_by_Shell.
Trigger TQL
Input TQL
111
Chapter 12 Oracle
Triggered CI Data
Discovered CITs

OracleHomes. Used when no ORACLE_HOME environment variable is defined. This value must be the same as the parameter in the Oracle Listeners by Shell Job job.
112
Chapter 12 Oracle
8 Topology
9 Configuration Items

Oracle TNS Listener. This CIT represents the Oracle TNS Listener. CIT name. oracle_listener Parent CIT name. application Key attributes:

data_name (displayed as Name). The TNS Listener constant. root_container (displayed as Container). The Container CI. listener_name (displayed as Name of the Listener). The real TNS Listener name.
113
Chapter 12 Oracle
Additional Attributes
listened_ips (displayed as Listened IPs). Listened to IP addresses and machine domain name. Listened IPs are IP addresses that are listened to by the Oracle TNS Listener. Format: <host_name>:<host_primary_ip>@<listened_ip>:<mac>; <listened_ip>:<mac>
Note: MAC addresses are not currently discovered. The marker acts as a placeholder for future enhancements.
Links
CIT Host RAC Process Link Type Container link Member Depend Cardinality 1.* 1.* 1.*
10 The Oracle Package

All components responsible for Oracle RAC discovery are bundled in the Oracle package (Admin > Universal CMDB > Settings > Package Manager > Oracle), under the Database category.
114
Chapter 12 Oracle
11 Oracle View
To access: Modeling > View Manager > Views > Root > Database > Oracle > Oracle.

Error Message Failed to lookup host name. No RAC CI will be created. Description For one or more nodes, the job failed to retrieve the FQDN (fully qualified domain name) from the listeners listened_ips attribute information.
Check the logs to retrieve the IP and destination. Make sure that the FQDN for that IP can be
obtained either from the DNS or from the host file. No RAC CI are retrieved. Not all nodes were discovered with the correct listener information.
115
Chapter 12 Oracle
116
Part V
Discovery Tools
118
13
Discovery Tools

Concepts
Overview on page 119 Troubleshooting and Limitations on page 119
Overview
This module holds the jobs necessary to:

Discover document files and directories. Discover hosts using the Nslookup command on the Shell of every DNS server in the scope. Serve as an example of dynamically creating and using credentials for connecting to remote machines. Import data from external sources, for example, CSV files, properties files, and databases. For details, see Chapter 14, Importing Data from External Sources.
Troubleshooting and Limitations

Problem: The File Monitor by Shell does not trigger automatically. This is because there is no trigger TQL for this particular job: an automatic trigger on all destinations may cause an out-of-memory error on the Probe. Solution: Add the triggered CI manually.
119
Chapter 13 Discovery Tools
120
14
Importing Data from External Sources

Importing Data from External Sources Overview on page 122 The External_source_import Package on page 124 The Import from CSV File Job on page 125 The Import from Properties File Job on page 129 The Import from Database Job on page 130 The External Source Mapping Files on page 135 Converters on page 135 Tasks

Concepts
Import CSV Data from an External Source Scenario on page 138 Troubleshooting and Limitations on page 142
121
Chapter 14 Importing Data from External Sources
Importing Data from External Sources Overview

Your data is probably stored in several formats, for example, in spreadsheets, databases, XML documents, properties files, and so on. You can import this information into HP Universal CMDB and use the functionality to model the data and work with it. External data are mapped to CIs in the CMDB. The following external data sources are currently supported:

Comma Separated Value (CSV) Files on page 122 Properties Files on page 123 Databases on page 124
Comma Separated Value (CSV) Files

A *.csv file has a format that stores tabular data. Each row in a CSV file represents a set of values delimited with a particular delimiter. All rows are homogeneous, that is, each row has the same number of values. Values from all rows with the same index create a column. Values in a single column represent the same type of data. Therefore a CSV file represents a table of data (with rows and columns). The default delimiter for CSV files is the comma, but any symbol can be used as a CSV delimiter, for example, a horizontal tab.
Note: Microsoft Office Excel includes native support for the CSV format: Excel spreadsheets can be saved to a CSV file and their data can then be imported into UCMDB. CSV files can be opened in an Excel spreadsheet.
122
Example of a CSV file
CSV Files with Column Titles in First Row

CSV files often include column headings in the first row. When data is imported from these files, the titles are considered data and a CI is created for this row. To prevent a CI being created, you can define which row DDM should start at when importing data from a CSV file: 1 Select Manage Discovery Resources > Discovery Resources pane > Discovery Packages > External_source_import package > Patterns > Import_CSV. 2 In the Pattern Signature tab, locate the Discovery Pattern Parameters pane. 3 Locate the rowToStartIndex parameter. By default, the value is 1, that is, DDM retrieves data from the first row. 4 Replace 1 with the number of the row at which to start retrieving data. For example, to skip the first row and start with the second row, replace 1 with 2.
Properties Files
A properties file is a file that stores data in the key = value format. Each row in a properties file contains one key-to-value association. In code terms, a properties file represents an associative array and each element of this array (key) is associated with a value. A properties file is commonly used by an application to hold its configuration. If your application uses a configuration file, you can model the application in UCMDB.
123
Example of a properties file
Databases
A database is a widely used enterprise approach to storing data. Relational databases consist of tables and relations between these tables. Data is retrieved from a database by running queries against it. The following databases are supported: Oracle, Microsoft SQL Server, MySQL, and DB2.
The External_source_import Package

The External_source_import package consists of three jobs and three patterns. There is one job and one pattern for each external source (CSV file, properties file, database):
External Source CSV file Properties file Database Job Import from CSV file Import from Properties file Import from Database Pattern Import_CSV Import_Properties_file Import_DB
124
The jobs are located under the Discovery Tools module:
The patterns are located in the External_source_import package:
The Import from CSV File Job


Job Details on page 126 Discovery Pattern Parameters on page 126 Delimiters, Quotes, and Escaping Characters on page 128
125
Job Details
The job details are as follows:
This job has no Trigger TQLs associated with it. That is, this job is not triggered automatically (nor are the Import from Properties file and the Import from Database jobs). After you activate the job, you must manually add input CIs to the job so that it runs against a particular destination. For details, see Add the Discovered Shell CI to the Job on page 142.

The following parameters are included by default:
csvFile. The full path to the CSV file on the remote machine. The job uses the Shell CI Type as input to reach this path on the remote machine. delimiter. The delimiter used in the CSV file. The comma (,) delimiter is the default but other delimiters are supported. For details, see Delimiters on page 128. mappingFile. For details of the mapping file, see The External Source Mapping Files on page 135. rowToStartIndex. For details on setting the row at which DDM starts collecting data, see CSV Files with Column Titles in First Row on page 123. ciType. The CIT name. This job creates and reports CIs of this type to UCMDB, based on data in the CSV file. For example, if the CSV file contains records for UNIX hosts, you must set the ciType parameter to unix.
126
mappingString. The string containing mapping information used to map the columns in the CSV file to the CIs attributes. You define this mapping in the following format:

mapping elements should be separated by commas each mapping element should be specified in a <column number>:<attribute name> format, for example: The string 0:host_key,1:host_hostname defines the mapping of two attributes of a host CI, where the hosts host_key attribute is taken from the value in the first column (0) and the host_hostname attribute is taken from the value in the second column (1).
For details on overriding a pattern parameter, see Override Pattern Parameters in Discovery and Dependency Mapping Guide.
Mapping Information for the Import from CSV File Job

You can specify mapping information for the Import from CSV File job with one of the following methods:
In an external XML file. You must specify the mappingFile parameter. For details, see The External Source Mapping Files on page 135. Directly in a jobs ciType and mappingString parameters, without using an external file.
Note: When using this mapping method, you cannot specify attribute types or converters.
If the mappingFile parameter is specified, the job tries to retrieve mapping information from the XML file. If it is not specified, the job uses the mapping information specified in the ciType and mappingString parameters.
127
Delimiters, Quotes, and Escaping Characters

Delimiters
The delimiter divides values in the same row of a CSV file. Supported delimiters are:
Single symbol. Any symbol can be used as a delimiter, for example, the pipe sign (|), the letter O. Delimiters are case sensitive. ASCII code. If an integer number is used as the value for a delimiter parameter, this value is treated as ASCII code, and the related symbol is used as the delimiter. For example, 9 is a valid delimiter because 9 is the ASCII code for the horizontal tab. Known character sequence. A sequence of characters can be used to represent special characters. For example, \t represents the horizontal tab.
Quotation Marks
You can use double or single quotes in values, that is, all values residing between the two quotes are treated as a single value.
If a delimiter symbol is used in a value, the value must be surrounded with quotation marks. For example, the following row includes a comma inside a value, so the value must be quoted:
Morganfield, "25 Hope Road, Kingston", Jamaica
If a quote character is used in a value, the character must be escaped by inserting a backslash before it:
McKinley \"Muddy Waters\" Morganfield, "April 4, 1915"
This row contains two values: 1) McKinley "Muddy Waters" Morganfield 2) April 4, 1915.
128
Escaping Symbols
The following symbols must always be quoted or escaped:

Backslash Single quote Double quote Delimiter, that is, the delimiter used in the same CSV file.
The Import from Properties File Job

This job imports information from a properties file, maps the information to one CI, and imports that CI into UCMDB. This section includes the following topics:

Job Details on page 129 Discovery Pattern Parameters on page 130 Keys and Values on page 130 Comments in Properties Files on page 130
Job Details
This job has no Trigger TQLs associated with it.
129

mappingFile. For details of the mapping file, see The External Source Mapping Files on page 135. propertyFile. The full path to the properties file located on a remote machine. The Input CI runs the Shell discovery that is used to access this file on the remote machine. For details on overriding a pattern parameter, see Override Pattern Parameters in Discovery and Dependency Mapping Guide.
Keys and Values

Keys cannot contain the equals symbol (=). Each value must be set out in a single line. Use backslash+n (\n) to specify a new line. Values can contain anything, including \n for a new line, quotes, tabs, and so on.
Comments in Properties Files

To create a commented line in a properties file, add the pound sign (#) as the first character in a line. The job ignores commented lines.
The Import from Database Job

This job uses a database table or database query as the source of the information, maps the information to CIs, and imports the CIs into UCMDB. This section includes the following topics:

Job Details on page 131 Discovery Pattern Parameters on page 131 Tables and Queries on page 132 Database, Schema, and Table Names on page 132
130

Importing Data with a SQL Query on page 133 Column Types on page 133
Job Details
This job has no Trigger TQLs associated with it.

mappingFile. The name of the table column or query result column is used as a value for the column attribute in the mapping file. For details of the mapping file, see The External Source Mapping Files on page 135. schemaName. The name of the database schema. sqlQuery. If a SQL query is specified, mapping is performed against its result. This parameter is ignored if tableName is defined. tableName. If a table name is specified, mapping is performed against the tables columns. For details on overriding a pattern parameter, see Override Pattern Parameters in Discovery and Dependency Mapping Guide.
131
Tables and Queries

The following use cases are supported by the Import from Database job (a single SQL query is performed):
Import data using the schema name and table name parameters:
The SQL query is generated from these parameters.
Import data specifying an arbitrary SQL query as the source of the data:
The SQL query is generated from the defined query. For more details, see Importing Data with a SQL Query on page 133.
Database, Schema, and Table Names

SQL naming conventions suggest a usage of a <database.schema.table> syntax for the fully qualified name of a table. Note, however, that each vendor treats the specification in a different way. DDM uses the following notation:

The schemaName parameter specifies the name of a database. The tableName parameter specifies the name of a table. A schema name cannot be specified in a parameter but can be included in a SQL query.
132
For Oracle, the SQL query is:

SELECT * FROM <schemaName.tableName>
For Microsoft SQL Server, the SQL query is:

SELECT * FROM dbo.tableName
Note: The default dbo schema is used for Microsoft SQL Server.
Importing Data with a SQL Query

You can use arbitrarily-complex SQL query expressions, for example, joins, sub-selects and other options, as long as the query is valid and complies with the database usage. Currently, you must use a fully-qualified table name in the query according to the specific database.
Column Types
Types enable you to specify, in the mapping file, the type of column that exists in the external source. For example, a database includes information about column types, and the value of this type needs to be included in the CIs attributes. This is done by adding a type element to the map element (in mapping_[your mapping file name].xml):
<column type="int"></column>
Supported type attributes are:

string Boolean date int long
133

double float timestamp
Note:

You use the type attribute for database mapping only. If the column element does not include a type attribute, the element is mapped as a string.
Example of adding a type attribute A database column has an integer type and can be either 0 or 1. This integer must be mapped to a Boolean attribute of a CIT in UCMDB. Use the binaryIntToBoolean converter, as follows:
<map> <attribute>cluster_is_active</attribute> <column type="int">cluster_is_active</column> <converter module="import_converters">binaryIntToBoolean</converter> </map>
type="int". This attribute specifies that the value of cluster_is_active should be retrieved as an integer, and that the value passed to the converter method should be an integer. If the cluster_is_active attribute of the CIT is of type integer, the converter is not needed here, and the mapping file should say:
<map> <attribute>cluster_is_active</attribute> <column type="int">cluster_is_active</column> </map>
134
The External Source Mapping Files

The data in the external source is mapped to a CIs attributes in UCMDB by means of a mapping file. The mapping files are located in the Discovery Resources pane > External_source_import package > Configuration Files folder:
mapping_template.xml. A template that serves as a source for creating the mapping file. mapping_schema.xsd. The XML schema used to validate the XML mapping file. The XML mapping file must be compliant with this schema. mapping_doc.xml. A file that contains Help on creating a mapping file, including all valid elements. The mapping file describes the mapping only and does not include information about how data should be obtained. In this way, you can use one mapping file across different jobs. All the pattern files in the External_source_import package include a mappingFile parameter, for example:
<parameter name="mappingFile" type="string" description="Mapping file located in "Configuration Files" folder of this package" />
name="mappingFile". The value of this parameter is the mapping XML file. The mapping file is always located on the server and is downloaded to the Probe machine upon job execution.
Converters
Converters enable you to specify the way data should be converted between the external source and a CIs attributes. A CSV file contains records of type string. However, some of the record values need to be handled as numbers. This is done by adding a converter element to the map element (in [your mapping file name].xml):
<converter module="import_converters"></converter>
135
The import_converters.py file contains a set of the most commonly needed converters and types:

toString stringToInt stringToLong stringToFloat stringToBoolean stringToDate stringToDouble skipSpaces binaryIntToBoolean stringToBytesArray stringToZippedBytesArray To access the file: Discovery Resources pane > External_source_import package > Scripts. Example of a Converter A CSV file contains the following row:
Usain, 21, Male
This row must be mapped to the Person CIT that includes name (Usain), age (21), and gender (Male) attributes. The age attribute should be of type integer. Therefore, the string in the CSV file must be converted to an integer in the CIT to make it compliant with the CIT attribute type, before the Person CIs can retrieve the age values.
136
This is done by adding a converter element to the map element:

<map> <attribute>age</attribute> <column>2</column> <converter module="import_converters">stringToInt</converter> </map>
module="import_converters". This attribute specifies from which module the converter is to be retrieved. A module is a Jython script file that contains a set of converter methods, in this case, import_converters.py. stringToInt. The name of the converter. In the import_converters.py file, the method is written as follows:
def stringToInt(value): if value is not None: return int(value.strip()) else: return 0
Custom Converters
You can write your own custom converters: Add a new method to the import_converters.py file or create your own script and add a set of converter methods to it. Call the method with the name of the script, for example:
<converter module="your_converter_script">[your_converter_method] </converter>
Tasks
137
Import CSV Data from an External Source Scenario

The UCMDB administrator must model a vehicle catalog that is stored in a CSV file. This task includes the following steps:

Prerequisites on page 138 Create a CIT on page 139 Create a Mapping File on page 139 Activate the Import from CSV File Job on page 141 Add the Discovered Shell CI to the Job on page 142 Result on page 142
1 Prerequisites
The admin opens the CSV file and analyzes the data:
The file includes the name, model, year of manufacture, and the date when the car was purchased, that is, there are four columns of data:
1 2 3 4 Name Model Year of manufacture Date of purchase string string integer date
There are three rows to the file, which means that the admin expects three CIs to be created in UCMDB.
138
2 Create a CIT
The admin creates a CIT. a The admin creates a CIT named Car to hold the attributes that are to be mapped to the data in the CSV file (name, model, and so on):
For details, see Create a CI Type in Model Management. b During the creation of the CIT, the admin adds these attributes as follows:
For details, see Attributes Page in Model Management.
3 Create a Mapping File

The admin uses the template (mapping_template.xml) to create a mapping file that makes the information available to the Import_CSV pattern. The mapping file is located in the following folder: Manage Discovery Resources > Discovery Resources > External_source_import > Configuration Files.
139
a For each attribute, the admin adds a <map> marker:

<?xml version="1.0" encoding="UTF-8"?> <mappings xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation=".\mapping_schema.xsd" parserClassName="com.hp.ucmdb.discovery.library.communication.downloader.cfg files.CiMappingConfigFile"> <ci type="car"> <map> <attribute>name</attribute> <column>1</column> </map> <map> <attribute>model</attribute> <column>2</column> </map> <map> <attribute>year_of_manufacture</attribute> <column>3</column> </map> <map> <attribute>date_of_purchase</attribute> <column>4</column> </map> </ci> </mappings>
140
b The admin then adds information about the attribute type:

<?xml version="1.0" encoding="UTF-8"?> <mappings xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation=".\mapping_schema.xsd" parserClassName="com.hp.ucmdb.discovery.library.communication.downloader.cfg files.CiMappingConfigFile"> <ci type=""> <map> <attribute>name</attribute> <column>1</column> </map> <map> <attribute>model</attribute> <column>2</column> </map> <map> <attribute>year_of_manufacture</attribute> <column>3</column> <converter module="import_converters">stringToInteger</converter> </map> <map> <attribute>date_of_purchase</attribute> <column>4</column> <converter module="import_converters">stringToDate</converter> </map> </mappings>
All conversions between the values in the CSV file and the CI attributes are done by a converter. Several converter types are included in the package by default. For details, see Converters on page 135.
4 Activate the Import from CSV File Job

This job uses the Shell Trigger CIT to discover the CSV file on a remote machine. The Input CI Type is Shell and the Discovered CIs are the IT Universe. The admin activates the following job: Advanced Mode > Discovery Modules > Discovery Tools > Import from CSV file. For details on activating jobs, see Discovery Modules Pane in Discovery and Dependency Mapping Guide.
141
5 Add the Discovered Shell CI to the Job

After activation, the admin locates the Shell CI (of the machine where the cars.csv file is located) and adds it to the job. For details, see Choose CIs to Add Dialog Box in Discovery and Dependency Mapping Guide.
6 Result
The admin accesses the CIT Manager and searches for instances of the Car CIT. UCMDB finds the three instances of the CIT:


DDM Adds Extra CI When Importing from CSV File on page 142 Timeout Issues When Importing from CSV and Properties Files on page 143
DDM Adds Extra CI When Importing from CSV File

Problem. When CIs imported from a CSV file are displayed in the Statistics Results pane, one more CI than expected is included in the results. This is because the first row of the CSV file contains column headings that are considered as CIs. Solution. For details on defining from which row DDM should read the CSV file, see CSV Files with Column Titles in First Row on page 123.
142
Timeout Issues When Importing from CSV and Properties Files

Problem. When importing large CSV or properties files on the network, there may be time-out issues. Solution. Make sure the files are not large.
143
144
Part VI
Integration by Discovery
146
15
Network Node Manager i (NNMi) Integration with HP Universal CMDB
This chapter explains how to integrate Network Node Manager (NNMi) with HP Universal CMDB. This chapter includes: Concepts

NNMi Integration Overview on page 148 NNMi - UCMDB Integration Architecture on page 149 Tasks
Set Up HP NNMiHP UCMDB Integration on page 150 Run HP NNMiUCMDB Integration on page 151 Use the HP NNMiHP UCMDB Integration on page 159 Change the HP NNMiHP UCMDB Integration Configuration on page 162 Disable HP NNMiHP UCMDB Integration Configuration on page 162 Perform Impact Analysis on page 163 Reference
HP NNMiHP UCMDB Integration Configuration Form Reference on page 163 NNMi Protocol Connection Parameters on page 167 Troubleshooting and Limitations on page 168
Concepts
147
Chapter 15 Network Node Manager i (NNMi) Integration with HP Universal CMDB
NNMi Integration Overview

You integrate NNMi with UCMDB using the Discovery and Dependency Mapping (DDM) application. When you activate the Integration NNM Layer2 module, DDM retrieves Layer 2 network topology data from NNMi and saves the data to the Universal CMDB database. Users can then perform change management and impact analysis through the UCMDB correlation engine.
Note: DDM version 8.00 or later includes a module for discovering NNMi. No additional deployment is necessary.

Use Cases on page 148 Supported Versions on page 148
Use Cases
This document is based on the following use cases:
Use Case 1: A UCMDB user wants to view the Layer 2 network topology supporting servers and applications. The requirement is to use NNMi as the authoritative source for that information with access through the Universal CMDB application. Use Case 2: An NNMi operator wants to view the impact of a network access switch infrastructure failure where the impact data is available in UCMDB. The NNMi operator selects an incident or a node in NNMi and then enters a request for impacted CIs.
Supported Versions
Out of the box, the following software versions are supported:
Discovery and Dependency Mapping (DDM) Probe version 8.03 (with Content Pack 4) and later
148
HP NNMi version 8.11 and later The following versions are supported after certain updates have been made (as per technical article KM629927 on the HP Support Web site at http://support.openview.hp.com).
Discovery and Dependency Mapping (DDM) Probe, versions 8.0, 8.01 and 8.02. HP NNMi version 8.10. To use these versions, you must first update the nnm_sdk.jar file as directed by HP Software support.
NNMi - UCMDB Integration Architecture
Tasks
149
Set Up HP NNMiHP UCMDB Integration

The following steps describe how to configure NNMi to communicate with UCMDB:

Configure the Connection between NNMi and UCMDB on page 150 Customize the Integration on page 150
Configure the Connection between NNMi and UCMDB

On the NNMi management server, do the following: 1 In the NNMi console, open the HP NNMiHP UCMDB Integration Configuration form (Integration Module Configuration > HP UCMDB). 2 Select the Enable Integration check box to activate the remaining fields on the form. 3 Enter the information for connecting to the NNMi management server. For information about these fields, see NNMi Management Server Connection on page 164. 4 Enter the information for connecting to the UCMDB server. For information about these fields, see UCMDB Server Connection on page 165. 5 Click Submit at the bottom of the form. A new window displays a status message. If the message indicates a problem with connecting to the UCMDB server, re-open the HP NNMiHP UCMDB Integration Configuration form (or press ALT+LEFT ARROW in the message window), and then adjust the values for connecting to the UCMDB server as suggested by the text of the error message.
Customize the Integration

On the NNMi management server, do the following: 1 In the NNMi console, open the HP NNMiHP UCMDB Integration Configuration form (Integration Module Configuration > HP UCMDB).
150
2 Enter values for the following fields:

HP UCMDB Correlation Rule Prefix HP UCMDB Impact Severity Level (19)
For details on these fields, see Integration Behavior on page 166. 3 Click Submit at the bottom of the form.
Run HP NNMiUCMDB Integration

This task includes the steps to run the NNMi/Universal CMDB integration jobs.
Important: To avoid conflict, do not run the UCMDB Layer 2 discovery jobs when running the NNMi Layer 2 integration discovery.

Prerequisites on page 152 Set Up the NNMi Protocol on page 154 Activate the Discovery Jobs on page 155 Check Messages for Successful Job Execution on page 157 Topology Map and Validation of Results on page 158
151
1 Prerequisites
Ensure that the DDM Discovery Probe has been installed, as detailed in the Discovery and Dependency Mapping Guide. NNMi integration jobs are triggered against the IP CI of the NNMi server. This IP CI must be present in UCMDB. This IP CI may be discovered in one of the following ways:

Discover the IP CI of the NNMi Server in UCMDB on page 152 Manually Add the IP CI of the NNMi Server on page 153
After the IP CI has been discovered, perform the step Verify CI Discovery on page 154.
Note: If you installed HP Business Availability Center or HP Operations Manager i, you may have installed a bundled UCMDB that uses a Foundation license. If your UCMDB installation has a Foundation license deployed, it is not possible to discover the IP CI automatically. Therefore, you should create this CI manually in the CMDB, as described in Manually Add the IP CI of the NNMi Server.
Discover the IP CI of the NNMi Server in UCMDB

To add the IP of the NNMi server to the DDM Probe range: 1 Navigate to Admin > Discovery > Setup Discovery Probes. 2 Select the Probe that is to be used for the NNMi integration, and add the IP address of the NNMi server to its range. To discover the IP CI of the NNMi server: 1 Navigate to Admin > Discovery > Run Discovery. 2 In the Network - Basic discovery module, select the job Range IPs by ICMP and click the Properties tab. 3 In the Range parameter line, select the Override check box and add the IP address of the NNMi server.
152
4 Click OK to save the job, and then activate it to discover the IP CI of the NNMi server.
Manually Add the IP CI of the NNMi Server
Note: When you installed HP Business Availability Center or HP Operations Manager i, you may have installed a bundled UCMDB that uses a Foundation license. If your UCMDB installation has a Foundation license deployed, use the steps in this section to manually add an IP CI. If any other license (Basic or Advanced) is deployed on the UCMDB server, use the Discover the IP CI of the NNMi Server in UCMDB procedure.
To manually add the IP CI of the NNMi server 1 Verify that the DDM Probe is correctly installed and connected to the UCMDB server. 2 Add the IP of the NNMi server to the DDM Probe range: a Navigate to Admin > Discovery > Setup Discovery Probes. b Select the Probe that is to be used for the NNMi integration, and add the IP address of the NNMi server to its range. 3 Insert the IP CI of the NNMi server in the CMDB: a Navigate to Admin > Modeling > IT Universe Manager. b In the View drop-down menu of the CI Selectors View Browser, select Network Topology. c Click the New CI button. d In the New CI dialog box, select the IP CIT from the tree and enter the following values:
Field IP Address Description
The IP address of the NNMi server.
153
Field IP Domain Name
Description
The UCMDB domain name (for example, DefaultDomain). The name of the DDM Probe (for example, DefaultProbe).
IP Probe Name
e Click Save to save the IP CI.
Verify CI Discovery
Note: Verification of CI discovery is relevant only when the IP CI of the NNMi server is discovered (as described in Discover the IP CI of the NNMi Server in UCMDB on page 152), not when it is added manually.
In HP Universal CMDB, verify that the following CIs have been discovered before running the NNMi discovery:

The IP CI of the NNMi server (through the ICMP jobs) The Host CI of the NNMi server (through the Host Connection jobs) The Process CI of the NNMi Host (through the Host Resource jobs) To activate a job, select it and click the Activate button. For an explanation of a discovery job, see Jobs in Discovery and Dependency Mapping Guide.
2 Set Up the NNMi Protocol

In this step, you configure an NNMi protocol entry. This enables the UCMDB server to access information on the NNMi server. a Click Admin > Discovery > Set Up Discovery Probes to open the Setup Discovery Probes window. b If no Probe exists, select Domains and Probes and click the Add Domain or Probe button to open the Add New Domain dialog box. c Enter a name for the new domain and click OK.
154
d In the Domains and Probes tree, navigate to the Probe for which you want to set up the NNMi protocol, and click Credentials. e Select NNM Protocol and click .
f Set the protocol attributes, as detailed in NNMi Protocol Connection Parameters on page 167, and click OK. For further information about setting up protocols, see Domain Credential References in Discovery and Dependency Mapping Guide.
3 Activate the Discovery Jobs

The NNMi jobs are included in UCMDBs Integration NNM Layer 2 module.
Layer 2 by NNM job This job connects to the NNMi Web service and retrieves NNMi discovered nodes, IPs, networks, interfaces, and Layer 2 connection information to create a Layer 2 topology in UCMDB. The job is activated against the IP CI of the NNMi server (discovered in the Verify CI Discovery step above).
Note: Due to the large volume of data discovered by this DDM job, it may take a while for the Probe to send the data back to the server. If there are more than 20,000 CIs, the Probe returns data in chunks of 20,000 objects at a time.
To activate the Layer 2 by NNM job: a Navigate to Admin > Discovery > Run Discovery. b In the Integration - NNM Layer2 discovery module, select the job Layer2 by NNM and click the Properties tab. c Right-click the job name and select Activate.
155
Note: Steps d through f are necessary only if the NNMi server's IP address CI was added manually, as described in Manually Add the IP CI of the NNMi Server on page 153. If the server's IP address was discovered by DDM (as described in Discover the IP CI of the NNMi Server in UCMDB on page 152), skip steps d through f.
d When the job has been activated, click the Add CI button. e Search for the IP CI of the NNMi server and click Add to add the IP CI of the NNMi server to the triggered CIs section. f Click Close to close the Choose CIs to Add dialog box. This causes the job to be activated against the selected IP CI of the NNMi server.
Update Ids in NNM job This job updates the nodes in the NNMi topology with the UCMDB IDs of the corresponding nodes in UCMDB. This job retrieves the UCMDB IDs of the NNMi hosts from the UCMDB server using the UCMDB Web Services API. The job then updates the UCMDB_ID custom attribute on the corresponding node object on the NNMi server using the NNMi Web service. Because the NNMi Web service enables updating of only one node at a time, this process might take a while, depending on the number of nodes involved. Check probeMgr-patternsDebug.log for the update status.
To activate the Update Ids in NNM job: a Navigate to Admin > Discovery > Run Discovery. b In the Integration - NNM Layer2 discovery module, select the job Update Ids in NNM. c Right-click the job name and select Activate. Note: Steps d through f are necessary only if the NNMi server's IP address CI was added manually, as described in Manually Add the IP CI of the NNMi Server on page 153. If the server's IP address was discovered by DDM (as described in Discover the IP CI of the NNMi Server in UCMDB on page 152), skip steps d through f.
156
d When the job has been activated, click the Add CI button. e Search for the IP CI of the NNMi server and click Add to add the IP CI of the NNMi server to the triggered CIs section. f Click Close to close the Choose CIs to Add dialog box. This causes the job to be activated against the selected IP CI of the NNMi server.
4 Check Messages for Successful Job Execution

You can monitor the wrapperProbeGw.log file for job invocation, execution (and possible error) messages. For further debugging information, check the probeMgr-patternsDebug.log file, located in C:\hp\DDM\DiscoveryProbe \root\logs\. The following example shows typical successful job execution messages for the Layer 2 by NNM job:
- The Job 'NNM Layer 2' started invocation (on 1 destinations) - Starting NNM_Integration_Utils:mainFunction - Server: it2tst10.cnd.hp.com, Port: 80, Username: system, MaxPerCall: 2500, MaxObjects: 50000 - Service URL: http://it2tst10.cnd.hp.com:80/IPv4AddressBeanService/IPv4AddressBean - Service URL: http://it2tst10.cnd.hp.com:80/NodeBeanService/NodeBean - Service URL: http://it2tst10.cnd.hp.com:80/IPv4SubnetBeanService/IPv4SubnetBean - Service URL: http://it2tst10.cnd.hp.com:80/InterfaceBeanService/InterfaceBean - Service URL: http://it2tst10.cnd.hp.com:80/L2ConnectionBeanService/L2ConnectionBean - OSHVector contains 45426 objects. - The probe is now going to send back 45426 objects. - This transfer may take more time than normal due to the large amount of data being sent to the server.
157
The following example shows typical successful job execution messages for the Update Ids in NNM job:
- The Job 'NNM Update IDs' started invocation (on 1 destinations) - UCMDB Server: ucmdb75.fkam.cup.hp.com, UCMDB Port: 8080, UCMDB Username: admin, UCMDB Protocol: http, UCMDB Context: /axis2/services/UcmdbService - NNM Server: it2tst10.cnd.hp.com, NNM Port: 80, NNM Username: system - Getting ready to update Custom Attribute UCMDB_ID on 8161 NNM nodes in NNM - This process may take a while since the UCMDB_ID custom attribute in NNM can only be updated one node at a time. Check probeMgr-patternsDebug.log for status update.
5 Topology Map and Validation of Results

Verify that data was discovered using the NNMI integration jobs. a For a Layer 2 by NNM job:

In UCMDB, navigate to Admin > Modeling > IT Universe Manager. In the View drop-down menu of the CI Selectors View Browser, select Layer 2. This view displays the CIs and relationships discovered by the integration job.
b For an Update Ids in an NNM job:
In NNMi, open an NNMi node that was discovered in UCMDB.
158
On the Custom Attributes tab, look for the UCMDB_ID custom attribute, which should contain the UCMDB ID of the corresponding host in UCMDB.
Use the HP NNMiHP UCMDB Integration

When you have set up the HP NNMiHP UCMDB integration, the following URL actions are added to the NNMi console:
The Find UCMDB Impacted CIs action, which is described in View Impacted CIs on page 159. The Open CI in UCMDB action, which is described in View the UCMDB CI on page 161. For information about using the integration from the UCMDB user interface, see Run HP NNMiUCMDB Integration on page 151.
View Impacted CIs

Testing for impacted configuration items in UCMDB involves firing a test event of the designated severity and then evaluating the specified correlation rules to determine if the event impacts any other configuration items. For example:
Correlation rule 1 might specify the following impacts:
If Router A experiences a management event of severity 8, Router B and Router C are impacted. If Router A experiences a management event of severity 9, Router B, Router C, and Router D are impacted.
Correlation rule 2 might specify the following impact:
If Router A experiences a management event of any severity, Service E is impacted.
159
The results of impact analysis on Router A are as follows:

For a management event of severity 17, Service E would be impacted. For a management event of severity 8, Router B, Router C, and Service E would be impacted. For a management event of severity 8, Router B, Router C, Router D, and Service E would be impacted. For more information about correlation rules, see Correlation Manager in Model Management. For the HP NNMiHP UCMDB integration, the parameters described in Integration Behavior on page 166 specify the severity of the test event and the group of UCMDB correlation rules to evaluate. The Find UCMDB Impacted CIs action displays a list of the UCMDB configuration items that would be impacted for the selected node or interface according to the values of the HP UCMDB Correlation Rule Prefix and HP UCMDB Impact Severity Level (19) parameters. The Find UCMDB Impacted CIs action is available from the following NNMi console locations:
Any node inventory view Any interface inventory view Any map view (with a node or interface selected) Any incident browser
Note: The Find UCMDB Impacted CIs action is available for all nodes and interfaces in the NNMi topology, regardless of whether these objects are modeled in the UCMDB database.
160
View the UCMDB CI

To launch the UCMDB information for a specific CI, select that CI in the HP UCMDB Impacted CIs window (the results of the Find UCMDB Impacted CIs action), and then click Actions > Open CI in UCMDB.
Note: Since UCMDB is not supported on FireFox, this cross launch works only if NNMi is running in Internet Explorer.
161
Change the HP NNMiHP UCMDB Integration Configuration

To update the HP NNMiHP UCMDB Integration Configuration, perform the following steps: 1 In the NNMi console, open the HP NNMiHP UCMDB Integration Configuration form (Integration Module Configuration > HP UCMDB). 2 Modify the values as appropriate. For information about the fields on this form, see HP NNMiHP UCMDB Integration Configuration Form Reference on page 163. 3 Verify that the Enable Integration check box at the top of the form is selected, and then click Submit at the bottom of the form.
Note: The changes take effect immediately. You do not need to restart ovjboss.
Disable HP NNMiHP UCMDB Integration Configuration

To disable the HP NNMiHP UCMDB Integration Configuration, perform the following steps: 1 In the NNMi console, open the HP NNMiHP UCMDB Integration Configuration form (Integration Module Configuration > HP UCMDB). 2 Clear the Enable Integration check box at the top of the form, and then click Submit at the bottom of the form. The integration URL actions are no longer available.
Note: The changes take effect immediately. You do not need to restart ovjboss.
162
Perform Impact Analysis

You run impact analysis on a node in NNMi. Use the Universal CMDB Web Services API to call the NNMi correlations in the NNM_Integration.zip package:

NNM_Application_impacts_Application NNM_Host_impacts_Application NNM_Switch_Router_impacts_Host For details on running impact analysis, refer to the NNMi documentation. For details on the Universal CMDB Web Services API, see The HP Universal CMDB Web Service API in HP Universal CMDB Integrations. For details on correlation, see Correlation Manager in Model Management.
Reference
HP NNMiHP UCMDB Integration Configuration Form Reference

The HP NNMiHP UCMDB Integration Configuration form contains the parameters for configuring communications between NNMi and UCMDB. This form is available from the Integration Module Configuration workspace.
Note: Only NNMi users with the Administrator role can access the HP NNMiHP UCMDB Integration Configuration form.
The HP NNMiHP UCMDB Integration Configuration form collects information for the following general areas:

NNMi Management Server Connection on page 164 UCMDB Server Connection on page 165 Integration Behavior on page 166
163
To apply changes to the integration configuration, update the values on the HP NNMiHP UCMDB Integration Configuration form, and then click Submit. This section also includes the following topics:

NNMi Management Server Connection on page 164 UCMDB Server Connection on page 165 Integration Behavior on page 166
NNMi Management Server Connection

The following table lists the parameters for connecting to the NNMi management server. This is the same information that you use to open the NNMi console. You can determine many of these values by examining the URL that invokes an NNMi console session. Coordinate with the NNMi administrator to determine the appropriate values for this section of the configuration form. The default NNMi configuration uses http for connecting to the NNMi console. For information about configuring this connection to use https, see the chapter about enabling https for NNMi in the HP Network Node Manager i-series Software Deployment Guide.
Field HP NNMi SSL Enabled Description The connection protocol specification.
If the NNMi console is configured to use https, select the
NNMi SSL Enabled check box.

If the NNMi console is configured to use http, clear the
NNMi SSL Enabled check box. This is the default configuration. HP NNMi Host The fully-qualified domain name of the NNMi management server. This field is pre-filled with host name that was used to access the NNMi console. Verify that this value is the name that is returned by the nnmofficialfqdn.ovpl -t command run on the NNMi management server.
164
Field HP NNMi Port
Description The port for connecting to the NNMi console. This field is pre-filled with the port that the jboss application server uses for communicating with the NNMi console, as specified in the following file:
Windows:
%NnmDataDir%\shared\nnm\conf\nnm.ports.properties
UNIX:
$NnmDataDir/shared/nnm/conf/nnm.ports.properties For non-SSL connections, use the value of jboss.http.port, which is 80 or 8004 by default (depending on the presence of another Web server when NNMi was installed). For SSL connections, use the value of jboss.https.port, which is 443 by default. HP NNMi User The user name for connecting to the NNMi console. This user must have the NNMi Administrator or Web Service Client role. The password for the specified NNMi user.
HP NNMi Password
UCMDB Server Connection

The following table lists the parameters for connecting to the Web services on the UCMDB server. Coordinate with the UCMDB administrator to determine the appropriate values for this section of the configuration.
Field HP UCMDB SSL Enabled Description The connection protocol specification for connecting to the UCMDB Web services.
If the UCMDB Web services are configured to use https,
select the HP UCMDB SSL Enabled check box.

If the UCMDB Web services are configured to use http,
clear the HP UCMDB SSL Enabled check box. This is the default configuration. HP UCMDB Host The fully-qualified domain name of the UCMDB server.
165
Field HP UCMDB Port
Description The port for connecting to the UCMDB Web services. If you are using the default UCMDB configuration, use port 8080 (for non-SSL connections to UCMDB).
HP UCMDB User HP UCMDB Password
A valid UCMDB user account name with the UCMDB Administrator role. The password for the specified UCMDB user.
Integration Behavior
The following table lists the parameters that describe the integration behavior. Coordinate with the UCMDB administrator to determine the appropriate values for this section of the configuration.
Field HP UCMDB Correlation Rule Prefix Description The prefix of the UCMDB correlation rules that the Find UCMDB Impacted CIs action runs to calculate impact. The default prefix of NNM_ corresponds to the default UCMDB impact correlation rules in the integration package provided by UCMDB (the NNM_Integration.zip file). The severity level at which to apply the UCMDB impact correlation rules. HP recommends using the highest severity, 9, to include all rules that start with the specified HP UCMDB Correlation Rule Prefix in the calculation of possible impact.
HP UCMDB Impact Severity Level (19)
166
NNMi Protocol Connection Parameters

The following table lists the connection parameters from DDM to NNMi.
Field Connection Timeout NNM Password NNM Username Description The timeout (in milliseconds) after which the DDM Probe stops trying to connect to the NNMi server. The password for the specified NNMi Web service (for example, Openview). The user name for connecting to the NNMi console. This user must have the NNMi Administrator or Web Service Client role. The port for connecting to the NNMi console. This field is pre-filled with the port that the JBoss application server uses for communicating with the NNMi console, as specified in the following file:
Windows:
NNM Webservice Port
%NnmDataDir%\shared\nnm\conf\nnm.ports.properties
UNIX:
$NnmDataDir/shared/nnm/conf/nnm.ports.properties For non-SSL connections, use the value of jboss.http.port, which is 80 or 8004 by default (depending on the presence of another Web server when NNMi was installed). For SSL connections, use the value of jboss.https.port, which is 443 by default. NNM Webservice Protocol UCMDB Password UCMDB Username The protocol for the NNMi Web service (the default is http). The password for the UCMDB Web service (the default is admin). A valid UCMDB Web service account name with the UCMDB Administrator role (the default is admin).
167
Field UCMDB Webservice Port
Description The port for connecting to the UCMDB Web service. If you are using the default UCMDB configuration, use port 8080 (for non-SSL connections to UCMDB). The connection protocol specification for connecting to the UCMDB Web services.
If the UCMDB Web services are configured to use https,
UCMDB Webservice Protocol
select the HP UCMDB SSL Enabled check box.

If the UCMDB Web services are configured to use http,
clear the HP UCMDB SSL Enabled check box. This is the default configuration.
Problem. The NNMi Web service responds with a cannot interrogate model message. Solution. This message usually indicates that the Web services request made to the NNMi server is incorrect or too complex to process. Check the NNMi JBoss logs for details.
Problem. If an excessive number of nodes are to be updated with the same UCMDB ID, it may take a while for the update pattern to complete. Solution. The volume of data retrieved from the NNMi server might be large. The recommended memory requirements for the DDM Probe process is 1024 MB. Since the NNMi Web service enables updating the individual nodes one at a time, the time to update the nodes may take a while.
Problem. You have verified the values in the HP NNMiHP UCMDB Integration Configuration form, but the status message still indicates a problem with connecting to the UCMDB server. Solution. a Clear the Web browser cache. b Clear all saved form or password data from the Web browser.
168
c Close the Web browser window completely, and then re-open it. d Re-enter the values in the HP NNMiHP UCMDB Integration Configuration form.
Problem. The Layer 2 by NNM job finishes with the following warning: Failed to get any Layer 2 links from NNM. Solution. Refer to technical article KM629927 on the HP support Web site at http://support.openview.hp.com.
Problem. Either of the NNMi integration jobs fails with the following error in the DDM log files: com.hp.ov.nms.sdk.node.NmsNodeFault: Cannot interrogate model. Solution. This error typically means that the NNMi server failed to process the Web services call. Check the following two logs on the NNMi server for exceptions when the integration was activated:

jbossServer.log sdk.0.0.log
Problem. Either of the NNMi integration jobs fail with the following error: Could not find Discovery Probe 'DefaultProbe'. Task for TriggerCI will not be created. Solution. a Right-click the job and select Go To Pattern. b Click the Pattern Management tab. c Select the Override default Probe selection check box, and enter the name of the Probe used for the NNMi integration in the Probe field. d Click Save to save the pattern, then reactivate the job against the IP CI of the NNMi server.
169
170
16
Storage Essentials (SE) Integration with HP Universal CMDB
This chapter explains how to integrate Storage Essentials (SE) with HP Universal CMDB. This chapter includes: Concepts
SE Integration Overview on page 172 Tasks
Discover the SE Oracle Database on page 173 Reference

Concepts
The Storage Essentials Integration Packages on page 175 Discovered CITs on page 176 Views on page 181 Correlation Rules on page 185 Reports on page 187
171
Chapter 16 Storage Essentials (SE) Integration with HP Universal CMDB
SE Integration Overview
Integration involves synchronizing devices, topology, and the hierarchy of a customer storage infrastructure in the Universal CMDB database (CMDB). This enables Change Management and Impact Analysis across all business services mapped in UCMDB from a storage point of view. You integrate SE with UCMDB using the Discovery and Dependency Mapping (DDM) application. When you activate the Integration Storage Essentials module, DDM retrieves data from the SE Oracle database and saves CIs to the Universal CMDB database. Users can then view SE storage infrastructure in UCMDB. The data includes information on storage arrays, fiber channel switches, hosts (servers), storage fabrics, logical volumes, host bus adapters, storage controllers, and fiber channel ports. Integration also synchronizes physical relationships between the hardware, and logical relationships between logical volumes, storage zones, storage fabrics, and hardware devices.
Note: DDM version 8.00 or later includes a module for discovering SE. No additional deployment is necessary.
Supported Versions
The integration procedure supports DDM version 8.00 or later and SE version 6.x.
SE Installation Requirements
The minimum VM installation requirements for SE integration are:

Tasks
4 GB memory 50 GB hard drive space
172
Discover the SE Oracle Database

This task includes the steps to run the SE/UCMDB integration jobs. This task includes the following steps:

Prerequisites on page 173 Network and Protocols on page 174 Activate the Discovery Job on page 174 Topology Map on page 175
1 Prerequisites
In DDM, in the Run Discovery window, verify that the following CIs have been discovered before running the SE discovery:
Network Basic > Class C IPs by ICMP or Range IPs by ICMP: discovers the IP address of the Oracle database server Database Oracle > Database TCP Ports: discovers TCP ports on the IP address discovered previously Database Oracle > Oracle Connection by SQL: discovers Oracle server instances Network Storage > SE Integration by SQL: discovers storage infrastructure For details on activating a job, see Discovery Modules Pane in Discovery and Dependency Mapping Guide. For an explanation of a discovery job, see Jobs in Discovery and Dependency Mapping Guide.
173
Note:
For the Oracle Connection by SQL job, it is recommended to use the REPORT_USER Oracle user name, since this user has privileges necessary to run SQL queries on the APPIQ_SYSTEM tables. This DDM job queries Oracle Materialized Views, and the views may be in the process of being refreshed when the DDM job is executed. This could result in an error message identifying the problem and a request to run the job later.

SE uses the SQL protocol. For details, see SQL Protocol in Discovery and Dependency Mapping Guide.
3 Activate the Discovery Job

The SE Integration by SQL job is included in the Integration Storage Essentials module. The SE Integration by SQL job runs queries against Oracle materialized views, installed and maintained by Storage Essentials in the Oracle database. The job uses a database CI as the trigger. For details on activating a job, see Discovery Modules Pane in Discovery and Dependency Mapping Guide.
174
4 Topology Map
The following diagram illustrates the CITs discovered by the SE Integration by SQL job:
Reference
The Storage Essentials Integration Packages

The integration includes two UCMDB packages:
SE_Discovery.zip. Contains the trigger TQL for SE discovery, discovery script, discovery pattern, and discovery job. The discovery pattern has no parameters and requires no configuration. Storage_Basic.zip. Contains the new CI Type definitions, views, reports, and correlation rules. This package is common to all Storage Management integration solutions.
175
Tip: You can include the SE job in the DDM schedule. For details, see Discovery Scheduler Dialog Box in Discovery and Dependency Mapping Guide.
Discovered CITs
The following CITs represent SE storage entities in UCMDB:
Fiber Channel Connect. This CIT represents a fiber channel connection between fiber channel ports. Fiber Channel HBA. This CIT has change monitoring enabled on parameters such as state, status, version, firmware version, driver version, WWN, and serial number. A Fiber Channel HBA inherits from the Host Resource CIT. Fiber Channel Port. This CIT has change monitoring enabled on parameters such as state, status, WWN, and trunked state. Since a Fiber Channel Port is a physical port on a switch, it inherits from the Physical Port CIT under the Network Resource CIT. Fiber Channel Switch. A switch falls under the Host CIT since SE maintains an IP address for each switch. Parameters such as status, state, total/free/available ports, and version are change monitored. This CIT retrieves Fiber Channel Switch details from the mvc_switchsummaryvw and mvc_switchconfigvw views. DDM retrieves detailed information about Fiber Channel Ports on each switch from the mvc_portsummaryvw view. A switch inherits from a Host CIT in UCMDB. Since DDM uses the IP address of a host as part of its primary key, this DDM job attempts to use an IP address from SE for this purpose. If an IP address is not available, the job attempts to resolve the switchs IP address using a DNS name (also maintained by SE). If neither an IP address nor a DNS name is available, the switch is discarded.
176
Logical Volume. This CIT represents volumes on Storage Arrays and hosts with change monitoring on availability, total/free/available space, and storage capabilities. Storage Array. This CIT represents a Storage Array with change monitoring on details such as serial number, version, and status. Since a storage array may not have a discoverable IP address, it inherits from the Network Resource CIT. This package retrieves Storage Array details from the mvc_storagesystemsummaryvw view. DDM retrieves detailed information on Storage Processors and HBAs from the mvc_storageprocessorsummaryvw and mvc_cardsummaryvw tables respectively. The SE database may possibly not be able to obtain IP address information on Storage Arrays for a variety of technical and policy related reasons. Since a Storage Array is a host as far as DDM is concerned, DDM assumes that the serial number of a Storage Array is unique and uses this as the primary key. The CI is then manually set as a complete host. If the serial number of a Storage Array is not available, the array is discarded. Since Fiber Channel Ports may be present on a Storage Array, Storage Processor, or HBA, DDM uses three separate queries to retrieve Fiber Channel Ports for each Storage Array. Detailed information about Fiber Channel Ports on each array are retrieved from the mvc_portsummaryvw view. Since this view uses a container ID as the key, DDM queries the view by container ID for each Storage Array, each Storage Processor on a Storage Array, and each HBA on a Storage Array. DDM retrieves detailed information about Logical Volumes on each Storage Array from the mvc_storagevolumesummaryvw view.
177
Results from these queries populate a map as shown below:
Storage Fabric. This CIT inherits from the Network Resource CIT and represents a storage fabric. This CIT has no change monitoring enabled. Storage Processor. This CIT represents other storage devices such as SCSI controllers, and inherits from the Host Resource CIT. A Storage Processor CIT monitors change on parameters such as state, status, version, WWN, roles, power management, and serial number. Storage Pool. Storage Pool information is also collected from each Storage Array using the query below. Results from this query populate a map as shown below:
Host Details
DDM retrieves Host details from the mvc_hostsummaryvw view and detailed information on HBAs from the mvc_cardsummaryvw view.
178
SE maintains information on Operating Systems, CPUs, Memory, IP address, and DNS name on each host. DDM uses this information to create Host CIs of type UNIX or Windows, and adds CPU and Memory CIs for each host as available. Since UCMDB uses the IP address of a host as part of its primary key, DDM attempts to use the IP address from SE for this purpose. If an IP address is not available, DDM then attempts to resolve the hosts IP address using a DNS name. If neither an IP address nor a DNS name is available, DDM ignores the host. Similar to Storage Arrays, a host may have Fiber Channel Ports directly associated with itself or on HBAs on the host. The DDM job uses three separate queries to retrieve Fiber Channel Ports for each host. The job retrieves detailed information about Fiber Channel Ports on each host from the mvc_portsummaryvw view. Since this view uses a ContainerID attribute as the key, the job queries the view by containerID for each host, and each HBA on a host. Finally, DDM retrieves detailed information about Logical Volumes on each host from the mvc_hostvolumesummaryvw and mvc_hostcapacityvw views. The mvc_hostcapacityvw view maintains capacity information for each volume over multiple instances in time, and the job uses only the latest available information. Results from these queries populate a map as shown below:
179
SAN Topology
SAN Topology consists of the Fiber Channel network topology and includes (fiber channel) connections between Fiber Channel Switches, Hosts, and Storage Arrays. SE maintains a list of WWNs that each Fiber Channel Port connects to, and this package uses this list of WWNs to establish Fiber Channel Connection links. Results from these queries populate a map as shown below:
Storage Topology
Storage topology consists of relationships between Logical Volumes on a host and Logical Volumes on a Storage Array. DDM uses multiple tables to identify this relationship as shown in the query below. This view is a summary of all of the above information.
180
Results from these queries populate a map as shown below:
Views
The SE package contains views that display common storage topologies. These are basic views that can be customized to suit the integrated SE applications.
Storage Array Details

This view shows a Storage Array and its components including Logical Volumes, HBAs, Storage Processors, and Fiber Channel Ports. The view shows each component under its container Storage Array and groups Logical Volumes by CI Type.
181
Storage Array does not require all components in this view to be functional. Container links stemming from the Storage Array have a cardinality of zeroto-many. The view may show Storage Arrays even when there are no Logical Volumes or Storage Processors.
FC Switch Details
This view shows a Fiber Channel Switch and all connected Fiber Channel Ports.
182
Storage Pool Details

This view shows Storage Pools with associated Storage Arrays and Logical Volumes.
Host Storage Details

This view shows only Hosts that contain a Fiber Channel HBA or a Logical Volume. This keeps the view storage-specific and prevents hosts discovered by other DDM jobs from being included in the view.
183
SAN Topology
This view maps physical connections between Storage Arrays, Fiber Channel Switches, and Hosts. The view shows Fiber Channel Ports below their containers. The view groups the Fiber Channel Connect relationship CIT to prevent multiple relationships between the same nodes from appearing in the top layer.
Storage Topology
This view maps logical dependencies between Logical Volumes on Hosts and Logical Volumes on Storage Arrays. There is no folding in this view.
184
Correlation Rules
The SE package contains basic correlation rules to enable impact analysis and root cause analysis in UCMDB. These correlation rules are templates for more complex rules that you can define based on business needs. All correlation rules fully propagate both Change and Operation events. For details on impact analysis, see Correlation Manager Window and Correlation Manager Overview in Model Management.
Note: Correlation events are not propagated to Fiber Channel Ports for performance reasons.
Storage Array Devices to Storage Array

This correlation rule propagates events between Logical Volumes, Storage Processors, Fiber Channel HBAs, and Storage Arrays.
Host Devices to Host

This correlation rule propagates events between Fiber Channel HBAs and Hosts, and Logical Volumes on the Host.
185
Logical Volume to Logical Volume

This correlation rule propagates events on a Logical Volume contained in a Storage Array to the dependent Logical Volume on the Host.
FC Switch Devices to FC Switch

This correlation rule propagates events from a Fiber Channel Port to and from a Switch. The event is also propagated to the associated Storage Fabric.
FC Port to FC Port
This rule propagates events on a Fiber Channel Port to another connected Channel Port.
186
Example Scenario of HBA Going Down on a Storage Array
The event propagates from the HBA to the Storage Array and the Logical Volumes on the Array because of the Storage Devices to Storage Array rule. The correlation event on the Logical Volume then propagates to other dependent Logical Volumes through the Logical Volume to Logical Volume rule. Hosts using those dependent Logical volumes see the event next because of the Host Devices to Host rule. Depending on business needs, you define correlation rules to propagate events from these hosts to applications, business services, lines of business, and so on. This enables end-to-end mapping and impact analysis using UCMDB.
Reports
The SE package contains basic reports that can be customized to suit the integrated SE applications. In addition to the system reports, Change Monitoring and Asset Data parameters are set on each CIT in this package, to enable Change and Asset Reports in UCMDB. For details see Storage Array Configuration on page 187, Host Configuration on page 188, Storage Array Dependency on page 188, and Host Storage Dependency on page 189.
Storage Array Configuration

This report shows detailed information on Storage Arrays and its subcomponents including Fiber Channel Ports, Fiber Channel Arrays, and Storage Processors. The report lists Storage Arrays with sub-components as children of the Array.
187
Host Configuration
This report shows detailed information on hosts that contain one or more Fiber Channel HBAs, Fiber Channel Ports, or Logical volumes. The report lists hosts with sub-components as children of the host.
Storage Array Dependency

This report maps dependencies on a Storage Array. The report also displays information on switches connected to it.
188
Host Storage Dependency

This report shows detailed information on storage infrastructure dependencies of a Host. The report lists hosts and dependent components.
Storage Pool Configuration

This report shows detailed information on Storage Pool configuration.
189
190
17
EMC Control Center (ECC) Integration with HP Universal CMDB
This chapter explains how to integrate EMC Control Center (ECC) with HP Universal CMDB. This chapter includes: Concepts
ECC Integration Overview on page 192 Tasks
Discover the ECC Storage Topology on page 193 Reference

Concepts
ECC Job SQL Queries on page 199 Views on page 202 Correlation Rules on page 206 Reports on page 209
191
Chapter 17 EMC Control Center (ECC) Integration with HP Universal CMDB
ECC Integration Overview

Integration between ECC and DDM involves synchronizing devices, topology, and hierarchy of storage infrastructure in the UCMDB database (CMDB). This enables Change Management and Impact Analysis across all business services mapped in UCMDB from a storage point of view. DDM initiates discovery on the ECC database. Synchronized Configuration Items (CIs) include Storage Arrays, Fiber Channel Switches, Hosts (Servers), Storage Fabrics, Storage Zones, Logical Volumes, Host Bus Adapters, Storage Controllers, and Fiber Channel Ports. The integration also synchronizes physical relationships between hardware, and logical relationships between Logical Volumes and hardware devices, to enable end-to-end mapping of the storage infrastructure. You integrate ECC with UCMDB using the Discovery and Dependency Mapping (DDM) application.
Note: DDM Content Pack version 5.00 or later includes a module for discovering ECC. No additional deployment is necessary.
Tasks
192
Discover the ECC Storage Topology

This task includes the steps to run the ECC/UCMDB integration job. This task includes the following steps:

Supported Versions on page 193 Prerequisites on page 193 Network and Protocols on page 195 Discovery Workflow on page 196 Discovery Pattern Parameters on page 196 Discovered CIs on page 197 The ECC Integration Package on page 198 Topology Map on page 198
Target Platform EMC Control Center OS Platform All DDM Protocol SQL over JDBC, SSL optional ECC Version 6.x DDM Version DDM Content Pack 5.00 or later
2 Prerequisites
Deploy the ECC Integration package a If you are connecting to the ECC Oracle database with SSL communication, in DDM populate the SQL protocol or pattern parameters. For details, see SQL Protocol in Discovery and Dependency Mapping Guide. b Verify that the IP address of the ECC server is within scope of a DDM Probe. For details, see Add/Edit IP Range Dialog Box in Discovery and Dependency Mapping Guide.
193
Set up SSL communication with the ECC Oracle database
Important: Perform this procedure if SSL communication is enabled for the ECC database.
a Retrieve the following files from the Oracle server and copy them to C:\dbSafe (or another convenient location) on the DDM Probe file system:

cert.txt cwallet.sso ewallet.p12
b Populate the walletLocation DDM pattern parameter with the absolute location of cwallet.sso, for example, C:\dbSafe\cwallet.sso. For details on job parameters, see Discovery Pattern Parameters on page 196. c Open the WrapperEnv.conf file with a text editor. The file is located in C:\hp\DDM\DiscoveryProbe\scripts\install\conf\. d Add a new line after line ~82 that looks like:
set.ORACLE_SSL_CLASSES= %lib%/collectors/probeManager/discoveryResources/db/oracleSSL/oraclepki.jar; %lib%/collectors/probeManager/discoveryResources/db/oracleSSL/ojpse.jar; %lib%/collectors/probeManager/discoveryResources/db/oracleSSL/ojdbc14.jar
e Append the following code to the end of the line beginning with set.COMMON_CLASSPATH (line ~87):
;%ORACLE_SSL_CLASSES%
f Save and close the file. g Restart the DDM Probe.
194
Run the DDM jobs In DDM, in the Run Discovery window, run the following jobs needed to trigger ECC discovery:
Network Basic > Range IPs by ICMP. Discovers the IP address of the ECC server. Network Basic > Host Connection by Shell/WMI/SNMP. Discovers operating system information on the ECC server. Network Host Resources and Applications > Host Resources and Applications by Shell/SNMP/WMI. Discovers the Oracle database instance used by ECC. Database Oracle > Oracle Connection by SQL. Discovers Oracle databases using the SQL protocol.
For details on activating a job, see Discovery Modules Pane in Discovery and Dependency Mapping Guide. For an explanation of a discovery job, see Jobs in Discovery and Dependency Mapping Guide.
In DDM, set up the SQL protocol. Populate the parameters with the credentials to the ECC database. For details, see SQL Protocol in Discovery and Dependency Mapping Guide.
These credentials should have SELECT permissions on the following tables/views:

Fiber channel switches: STSSYS.STS_SWITCH_LIST Fiber channel ports on switches: STSSYS.STS_SWITCH_PORT Storage arrays: STSSYS.STS_ARRAY_LIST Fiber channel ports on arrays: STSSYS.STS_ARAY_PORT Logical volumes on arrays: STSSYS.STS_ARRAY_DEVICE Hosts/servers: STSSYS.STS_HOST_LIST Fiber channel ports and HBAs on hosts: STSSYS.STS_HOST_HBA Logical volumes on hosts: STSSYS.STS_HOST_DEVICE
195

Logical volume dependencies: STSSYS.STS_HOST_SHAREDDEVICE Port connections: STSSYS.STS_ARRAY_PORT_CONNECTION
Note: The ECC database instance has an out-of-the-box user account named STSVIEW that includes the necessary privileges. The default password for this account is sts.
Activate the Integration EMC Control Center > ECC Integration by SQL job. This job discovers the storage infrastructure of ECC. The ECC Integration by SQL job runs SQL queries on the ECC Oracle database using JDBC. This Oracle database instance is used as a trigger for the DDM job. For details of the SQL queries, see ECC Job SQL Queries on page 199.
Tip: You can include the ECC job in the DDM schedule. For details, see Discovery Scheduler Dialog Box in Discovery and Dependency Mapping Guide.
5 Discovery Pattern Parameters

Name useSSL Value false Description If SSL is required to connect to the ECC database, change to true.
196
Name walletLocation
Value C:\dbSafe\cwallet.sso
Description The location of the Oracle wallet. This parameter is required for SSL connections and defaults to C:\dbSafe\cwallet.sso. The Oracle wallet type. This parameter is required for SSL connections. The default for the ECC database is SSO.
walletType
SSO
6 Discovered CIs

CPU Contained (link) Container link (link) Depend (link) Fiber Channel Connect (link) Fiber Channel HBA Fiber Channel Port Fiber Channel Switch Host IP Logical Volume Member Memory Storage Array Storage Fabric Storage Processor Unix Windows
197
7 The ECC Integration Package

The integration includes the following package:
ECC_Integration.zip. Contains the trigger TQL, DDM script, pattern, and job for ECC discovery. The DDM job uses the ECC Oracle database CI as the trigger.
8 Topology Map
The following diagram illustrates the storage topology and shows the relationships between logical volumes on a storage array and those on servers:
198
The following diagram illustrates the SAN (Storage Area Networks) topology showing fiber channel paths between storage arrays, switches, and servers:
Reference
ECC Job SQL Queries

The following workflow explains how the ECC Integration by SQL job discovers the storage topology of ECC. The job: 1 Connects to the ECC Oracle database instance using credentials from the SQL protocol. For details, see Network and Protocols on page 195. 2 Queries for fiber channel switches and ports on each switch and creates Fiber Channel Switch CIs:
SELECT switch.st_id, switch.st_sn, switch.st_alias, switch.st_model, switch.st_version, switch.st_vendor, switch.sw_managementurl, switch.sw_domain, switch.sw_portcount, switch.sw_portcount_free FROM stssys.sts_switch_list switch WHERE LOWER(switch.sw_principal) = 'true'
199
3 Queries for fiber channel adapters and ports on each Fiber Channel Switch and creates Fiber Channel HBA and Fiber Channel Port CIs:
SELECT port.port_id, port.port_number, port.port_type, port.adport_alias, port.port_wwn, port.port_status, port.conn_port_wwn FROM stssys.sts_switch_port port WHERE port.st_id = switch.st_id from above query
4 Queries for storage arrays and creates Storage Array CIs:

SELECT array.st_id, array.st_sn, array.st_alias, array.st_type, array.st_model, array.st_vendor, array.st_microcode, array.sy_microcode_patch, array.sy_microcode_patchdate FROM stssys.sts_array_list array
5 Queries for Fiber Channel ports, Fiber Channel host bus adapters (HBA), and logical volumes on each storage array, and creates Fiber Channel Port, Fiber Channel Port HBA, and Logical Volume CIs:
SELECT port.port_id, port.port_number, port.port_type, port.adport_alias, port.port_wwn, port.port_status FROM stssys.sts_array_port port WHERE port.st_id = array.st_id from above query SELECT hba.port_id, hba.ad_id, hba.ad_name FROM stssys.sts_array_port hba WHERE hba.st_id = array.st_id from above query SELECT logicalVolume.sd_id, logicalVolume.sd_name, logicalVolume.sd_alias, logicalVolume.sd_size, logicalVolume.sd_type FROM stssys.sts_array_device logicalVolume WHERE logicalVolume.st_id = array.st_id from above query
6 Queries for hosts/servers and creates appropriate Computer, Windows, or Unix CIs. Results of this query are used to create host resource CIs such as Memory and CPU if this information is available:
SELECT host.host_id, host.host_name, host.host_alias, host.host_domain, host.host_model, host.host_ip, host.host_vendorname, host.host_cpucount, host.host_installedmemory, host.host_os, host.host_osversion, host.host_oslevel, host.host_osclass FROM stssys.sts_host_list host
200
7 Queries for Fiber Channel ports, Fiber Channel host bus adapters (HBA), and logical volumes on each host/server and creates Fiber Channel Port, Fiber Channel Port HBA, and Logical Volume CIs:
SELECT port.port_id, port.port_number, port.adport_alias, port.port_wwn FROM stssys.sts_host_hba port WHERE port.host_id = host.host_id from above query SELECT hba.ad_id, hba.ad_name, hba.fibread_nodewwn, hba.ad_vendor, hba.ad_revision, hba.ad_model, hba.port_id, hba.ad_driver_rev FROM stssys.sts_host_hba hba WHERE hba.host_id = host.host_id from above query SELECT logicalVolume.hd_id, logicalVolume.hd_name, logicalVolume.hd_type, logicalVolume.hd_total FROM stssys.sts_host_device logicalVolume WHERE logicalVolume.hd_id IS NOT NULL AND logicalvolume.arrayjbod_type = 'Array' AND logicalVolume.host_id = host.host_id from above query
8 Queries for logical volume mapping between logical volumes on hosts/servers and logical volumes on storage arrays, and adds Depend relationships between hosts/servers and storage arrays:
SELECT sd_id FROM stssys.sts_host_shareddevice WHERE hd_id = logicalvolume.hd_id from above query
9 Queries for paths between hosts/servers and storage arrays and adds Fiber Channel Connect relationships between respective hosts/servers, switches, and storage arrays:
SELECT port.port_wwn, port.conn_port_wwn FROM stssys.sts_array_port_connection port WHERE port.port_wwn IS NOT NULL AND port.conn_port_wwn IS NOT NULL SELECT port.port_wwn, port.conn_port_wwn FROM stssys.sts_switch_port port WHERE port.port_wwn IS NOT NULL AND port.conn_port_wwn IS NOT NULL
201
Views
The Storage_Basic package contains views that display common storage topologies. These are basic views that can be customized to suit the integrated ECC applications. To access the Storage_Basic package: Settings > Package Manager. For details, see Package Manager in Model Management. This section includes:

Storage Array Details on page 202 FC Switch Details on page 203 Storage Pool Details on page 204 Host Storage Details on page 204 SAN Topology on page 205 Storage Topology on page 205
Storage Array Details

This view shows a Storage Array and its components including Logical Volumes, HBAs, Storage Processors, and Fiber Channel Ports. The view shows each component under its container Storage Array and groups Logical Volumes by CI Type.
202
Storage Array does not require all components in this view to be functional. Container links stemming from the Storage Array have a cardinality of zeroto-many. The view may show Storage Arrays even when there are no Logical Volumes or Storage Processors.
FC Switch Details
This view shows a Fiber Channel Switch and all connected Fiber Channel Ports.
203
Storage Pool Details

This view shows Storage Pools with associated Storage Arrays and Logical Volumes.
Host Storage Details

This view shows only Hosts that contain a Fiber Channel HBA or a Logical Volume. This keeps the view storage-specific and prevents hosts discovered by other DDM jobs from being included in the view.
204
SAN Topology
This view maps physical connections between Storage Arrays, Fiber Channel Switches, and Hosts. The view shows Fiber Channel Ports below their containers. The view groups the Fiber Channel Connect relationship CIT to prevent multiple relationships between the same nodes from appearing in the top layer.
Storage Topology
This view maps logical dependencies between Logical Volumes on Hosts and Logical Volumes on Storage Arrays. There is no folding in this view.
205
Correlation Rules
The Storage_Basic package contains basic correlation rules to enable impact analysis and root cause analysis in UCMDB. These correlation rules are templates for more complex rules that you can define based on business needs. All correlation rules fully propagate both Change and Operation events. For details on impact analysis, see Correlation Manager Window and Correlation Manager Overview in Model Management. To access the Storage_Basic package: Settings > Package Manager. For details, see Package Manager in Model Management.
Note: Correlation events are not propagated to Fiber Channel Ports for performance reasons.
This section includes:

Storage Array Devices to Storage Array on page 207 Host Devices to Host on page 207 Logical Volume to Logical Volume on page 207 FC Switch Devices to FC Switch on page 208 FC Port to FC Port on page 208
206
Storage Array Devices to Storage Array

This correlation rule propagates events between Logical Volumes, Storage Processors, Fiber Channel HBAs, and Storage Arrays.
Host Devices to Host

This correlation rule propagates events between Fiber Channel HBAs and Hosts, and Logical Volumes on the Host.
Logical Volume to Logical Volume

This correlation rule propagates events on a Logical Volume contained in a Storage Array to the dependent Logical Volume on the Host.
207
FC Switch Devices to FC Switch

This correlation rule propagates events from a Fiber Channel Port to and from a Switch. The event is also propagated to the associated Storage Fabric.
FC Port to FC Port
This rule propagates events on a Fiber Channel Port to another connected Channel Port.
Example Scenario of HBA Going Down on a Storage Array
The event propagates from the HBA to the Storage Array and the Logical Volumes on the Array because of the Storage Devices to Storage Array rule. The correlation event on the Logical Volume then propagates to other dependent Logical Volumes through the Logical Volume to Logical Volume rule. Hosts using those dependent Logical volumes see the event next because of the Host Devices to Host rule. Depending on business needs, you define correlation rules to propagate events from these hosts to applications, business services, lines of business, and so on. This enables end-to-end mapping and impact analysis using UCMDB.
208
Reports
The Storage_Basic package contains basic reports that can be customized to suit the integrated ECC applications. In addition to the system reports, Change Monitoring and Asset Data parameters are set on each CIT in this package, to enable Change and Asset Reports in UCMDB. To access the Storage_Basic package: Settings > Package Manager. For details, see Package Manager in Model Management. This section includes:

Storage Array Configuration on page 209 Host Configuration on page 210 Storage Array Dependency on page 210 Host Storage Dependency on page 211 Storage Pool Configuration on page 211
Storage Array Configuration

This report shows detailed information on Storage Arrays and its subcomponents including Fiber Channel Ports, Fiber Channel Arrays, and Storage Processors. The report lists Storage Arrays with sub-components as children of the Array.
209
Host Configuration
This report shows detailed information on hosts that contain one or more Fiber Channel HBAs, Fiber Channel Ports, or Logical volumes. The report lists hosts with sub-components as children of the host.
Storage Array Dependency

This report maps dependencies on a Storage Array. The report also displays information on switches connected to it.
210
Host Storage Dependency

This report shows detailed information on storage infrastructure dependencies of a Host. The report lists hosts and dependent components.
Storage Pool Configuration

This report shows detailed information on Storage Pool configuration.
211
212
Part VII
The J2EE Modules
214
18
JBoss
Tasks
Discover JBoss by Shell on page 215
Discover JBoss by Shell

You can perform deep discovery of JBoss without having to enter JMX credentials for each server, and without having to define additional libraries (*.jar files). Instead, you use the regular Shell credentials. Deep discovery enables you to discover the topology of J2EE application systems, that is, the components of an application and not just the application itself. This task includes the following steps:

Prerequisites on page 216 Supported Versions on page 216 Network and Protocols on page 216 Discovery Workflow on page 216 Discovered CITs on page 219 Troubleshooting and Limitations on page 219
215
Chapter 18 JBoss
1 Prerequisites
Run Network Basic > Host Connection by Shell. DDM discovers hosts running NTCmd, Telnet, or SSH agents. Run Host Resources and Applications by Shell. DDM discovers software elements and processes relevant to JBoss. For details on the required *.jar files, see JBoss in Discovery and Dependency Mapping Guide.
JBoss versions 3.x ,4.x, and 5.x.
NTCmd. For credentials information, see NTCMD Protocol in the Discovery and Dependency Mapping Guide. SSH. For credentials information, see SSH Protocol in the Discovery and Dependency Mapping Guide. Telnet. For credentials information, see Telnet Protocol in the Discovery and Dependency Mapping Guide. Users do not need root permissions, but do need the appropriate credentials to enable connecting to the remote machines and running the relevant commands.
Run the J2EE JBoss > J2EE JBoss by Shell job. DDM discovers the following JBoss elements:
The Version Number. DDM discovers the version number of the JBoss application server by using the following regular expression in <JBoss base directory>\readme.html:
<title>.+?\s+(.+?)\s+.+
(That is, search for the string that follows the <title> string.)
216
Chapter 18 JBoss
If the version number is not found here, DDM discovers it by parsing the <JBoss base directory>\<server name>\config\standardjboss.xml file.
The Server Listening Port and Address. DDM retrieves this information from the <JBoss base directory>\server\<server name>\conf\jbossservice.xml file.
The listening port is retrieved from the RmiPort property. The port number is needed for the JBoss Connections by JMX job to choose the relevant JMX credentials. The listening address is retrieved from the rmibindaddress property; if this property does not exist or is set to jboss.bind.address, DDM uses the IP address of the Shell agent with which it connects to JBoss.
For JBoss version 5.x, DDM retrieves the listening port from the <JBoss base directory>\server\<server name>\bootstrap\bindings.xml file or the <JBoss base directory>\server\<server name>\conf\bindings.xml file.
The JMS Configuration.
DDM creates the jboss.mq JMS server CI according to the JBoss configuration. JMS destinations are parsed out from the <JBoss base directory>\ server\<server name>\deploy\jms\jbossmq-destinations-service.xml file. For JBoss version 5.x, DDM retrieves this information from the <JBoss base directory>\server\<server name>\deploy\messaging\ destinations-service.xml file.
The Database Configuration. DDM retrieves the database configuration from the <JBoss base directory>\server\<server name>*-ds.xml files where ds = data source. There can be several of these files. By default, JBoss includes the hsqldbds.xml file which configures the OOT Hypersonic database.
J2EE Applications. DDM discovers all folders with the .war or .ear suffix under the <JBoss base directory>\server\<server name>\tmp\deploy\ directory. For each of them, DDM finds the original .war or .ear file under the <JBoss base directory>\server\<server name>\deploy folder.
217
Chapter 18 JBoss
For each .war or .ear folder located under the <JBoss base directory>\ server\<server name>\tmp\deploy\ directory, DDM creates a J2EE Application CI with the following attributes:
data_name For an .ear file, DDM retrieves the application name from the <JBoss base directory>\server\<server name>\tmp\deploy\ filename.ear\META-INF\application.xml file. For a .war file, DDM uses the original .war file name (under the <JBoss base directory>\server\<server name>\deploy folder) for the application name, but without the .war suffix.
j2eeapplication_isear Set to true for .ear files.
j2eeapplication_fullpath DDM uses the original .war file full path under the <JBoss base directory>\server\<server name>\deploy folder. When discovering a JBoss server, DDM creates a J2EE Domain CI with the following name: <server name>@<ipaddress>. This action is performed also with JMX discovery. All J2EE objects use the J2EE Domain CIT as a container and are deployed on a J2EE server.
Configuration Files. DDM creates CIs for the following topology and resources configuration files:

jboss-service.xml (the principal configuration file) the xxx-ds.xml files (for data sources) jbossmq-destinations-service.xml or destinations-service.xml for the JMS configuration All these CIs are attached to the JBoss server CI since the JBoss server is used as a container for the J2EE Domain CI (even though DDM also creates the J2EE domain as a separate CI).
218
Chapter 18 JBoss
5 Discovered CITs
The following CITs are discovered by the J2EE JBoss by Shell job:

DDM can discover a J2EE application only when its .ear file is unzipped to a folder.
219
Chapter 18 JBoss
220
19
WebLogic

Tasks
Discover WebLogic on page 221 Discover WebLogic by Shell on page 223
Discover WebLogic
This task describes how to discover WebLogic applications. The WebLogic discovery process enables you to discover all the deployed Web services and operations deployed on a WebLogic server. DDM first finds WebLogic servers based on the JMX protocol, then discovers the WebLogic J2EE environment and components. This task includes the following steps:

Supported Versions on page 221 Prerequisites on page 222 Network and Protocols on page 222 Discovery Workflow on page 222
The following versions are supported: WebLogic 6.0, 6.1, 7.0, 8.1, 9.0, 9.1, 9.2, and 10.
221
Chapter 19 WebLogic
2 Prerequisites
If you are using WebLogic version 7, perform the following procedure to discover this Weblogic version:
Take the weblogic.jar file from the following location: <BEA Installation root folder>\<WebLogic version number>\server\lib. Place the file in the following location: C:\hp\DDM\DiscoveryProbe \root\lib\collectors\probeManager\discoveryResources. Rename the *.jar file by adding a suffix that includes the WebLogic version number, as follows: weblogic70.jar.
For details on the required *.jar files for all WebLogic versions, see WebLogic in Discovery and Dependency Mapping Guide.
WebLogic. For credentials information, see WebLogic Protocol in Discovery and Dependency Mapping Guide.
In the Run Discovery window, activate the job in the J2EE WebLogic module. For details on the CIs that are discovered, see the Statistics Results table in the Details tab. For details, see Statistics Results Pane in Discovery and Dependency Mapping Guide.
222
Chapter 19 WebLogic
Discover WebLogic by Shell

This task describes how to discover WebLogic applications by Shell. This task includes the following steps:

Prerequisites on page 223 Supported Versions on page 224 Network and Protocols on page 224 Discovery Workflow on page 224 Discovered CITs on page 226 Troubleshooting and Limitations on page 226
1 Prerequisites
a Run Network Basic > Host Connection by Shell. DDM discovers hosts running NTCmd, Telnet, or SSH agents. b Run Host Resources and Applications by Shell. DDM discovers software elements and processes relevant to WebLogic. c If you have created WebLogic configuration files manually, that is, you did not use the WebLogic Configuration Wizard, you must define the paths to these files:

Access Discovery Resources > J2EE > Patterns > WebLogic_By_Shell. In the Pattern Signature tab, locate the Discovery Pattern Parameters pane. Select the weblogic_config_root pattern parameter. Enter a comma-separated list of paths to the configuration files.
223
Chapter 19 WebLogic
WebLogic versions 8.x, 9.x, and 10.x.
Run the J2EE WebLogic by Shell job. DDM discovers the following elements:
The Version Number. DDM discovers the WebLogic application server version number by retrieving it from the domain config.xml file. The Server Listening Port and Address. DDM retrieves this information from the domain config.xml file. DDM identifies the admin server in one of the following ways:
WebLogic version 9 or later: from the config.xml file, using the <adminserver-name> tag. WebLogic version 8 or earlier: from the <WebLogic base directory>_cfgwiz_donotdelete\startscript.xml file, by searching for <setenv name="SERVER_NAME">.
If DDM does not identify the admin server, DDM stops the discovery for the current domain.
JMS Configurations. DDM retrieves the JMS configuration from the domain config.xml file. Database Configurations. DDM retrieves the JDBC configuration from the domain config.xml file.
224
Chapter 19 WebLogic
J2EE Applications. DDM retrieves application names and targets from the config.xml file:
For versions earlier than WebLogic 9, the EJB and Web components are obtained from this file. Web component related information (that is, servlets and their URLs) are obtained from the <WebLogic base directory>\<server_name>\stage\..\web.xml files. For WebLogic version 9 or later, the application EJB and Web components are retrieved from the <WebLogic base directory>\servers\<server_name>[stage or tmp\\_WL_user] \...\application.xml files.
Configuration Files. DDM creates CIs for the config.xml (the principal configuration file). DDM discovers WebLogic domain configurations with one of the following methods:
DDM uses the command line to search for platform.home that points to the WebLogic root folder. This folder holds the domain configurations created by the WebLogic Configuration Wizard. DDM uses the command line to search for -Dweblogic.RootDirectory= which points to non-default domain configurations. DDM retrieves the value of the weblogic_config_root pattern parameter, and checks for domain configurations in all the paths specified in this parameter. For details, see Prerequisites on page 223.
225
Chapter 19 WebLogic
5 Discovered CITs
The following CITs are discovered by the J2EE WebLogic by Shell job:
DDM discovers domains only when they are created by the WebLogic Configuration Wizard. For versions earlier than WebLogic 9, the J2EE WebLogic by Shell job can run only on admin server hosts. For WebLogic version 9 or later, the job can run also on hosts that contain managed nodes only. DDM can discover a J2EE application only when its .ear file is unzipped to a folder. The WebLogic installation includes an example that is filtered out by default. You can remove the filter in the weblogic_by_shell.py Jython script. Look for WL_EXAMPLE_DOMAINS = ['medrec']. If DDM finds two domains with the same name on the same host, only one domain configuration (j2eedomain topology) is reported.
226
20
WebSphere

Tasks
Discover WebSphere by Shell on page 227 Troubleshooting and Limitations on page 231
Discover WebSphere by Shell

This task describes how to discover WebSphere topology by Shell. This task includes the following steps:

Overview on page 228 Prerequisites on page 228 Jar Files on page 228 Supported Database Versions on page 228 Network and Protocols on page 229 Discovery Workflow on page 229 Discovered CITs on page 230 Troubleshooting and Limitations on page 230
227
Chapter 20 WebSphere
1 Overview
This task describes how to discover WebSphere applications. DDM first finds WebSphere servers based on either SOAP or RMI authentication, then discovers the WebSphere J2EE environment and components. WebSphere discovery discovers Web services that are deployed on an IBM WebSphere server. The discovered Web services are represented by the webservice CIT in the CMDB.
2 Prerequisites
Run Network Basic > Host Connection by Shell. DDM discovers hosts running NTCmd, Telnet, or SSH agents. Run Host Resources and Applications by Shell. DDM discovers software elements and processes relevant to WebSphere.
3 Jar Files
The *.jar files needed in discovery are located in the following folder: C:\hp\DDM\DiscoveryProbe\root\lib\collectors\probeManager\ discoveryResources/j2ee/websphere/
Note: These *.jar files must not be replaced.
For details on the required *.jar files for all WebSphere versions, see WebSphere in Discovery and Dependency Mapping Guide.
WebSphere versions 5.x, 6.x, and 7.x.
5 Supported Database Versions

WebSphere versions 5.x, 6.x, and 7.x.
228
NTCmd. For credentials information, see NTCMD Protocol in the Discovery and Dependency Mapping Guide. SSH. For credentials information, see SSH Protocol in the Discovery and Dependency Mapping Guide. Telnet. For credentials information, see Telnet Protocol in the Discovery and Dependency Mapping Guide. Users do not need root permissions, but do need the appropriate credentials to enable connecting to the remote machines and running the relevant commands.
Run the J2EE WebSphere by Shell job. DDM discovers the following elements:
The Version Number. DDM discovers the version number of the WebSphere application server from the WAS.product or BASE.product file (depending on the WebSphere version) under the <WebSphere base directory>\properties\version folder. The Server Listening Port and Address. DDM retrieves information about WebSphere servers by searching for the serverindex.xml file, located under the <WebSphere base directory>\profiles\<PROFILE>\config\ cells\<CELL>\nodes\<NODE> folder, or under the <WebSphere base directory>\config\cells\<CELL>\nodes\<NODE> folder. J2EE Applications. DDM searches for the deployment.xml file in each <WebSphere base directory>\profiles\<PROFILE>\config\cells\<CELL> \applications folder (or in the <WebSphere base directory>\config\cells \<CELL>\nodes\<NODE>\applications folder). The deployment.xml file is located in every installed application folder and contains information about application targets. Configuration Files. DDM creates CIs for the resources.xml resources configuration file. A CI is created for each cell, node, and server (with the relevant prefix); each CI is attached to the WebSphere server CI.
229
8 Discovered CITs
The following CITs are discovered by the J2EE WebSphere by Shell job:
For details on the CIs that are discovered, see the Statistics Results table in the Details tab. For details, see Statistics Results Pane in Discovery and Dependency Mapping Guide.

J2EE clusters are not discovered. EJB and Web Service CIs are not discovered. DDM can discover a J2EE application only when its .ear file is unzipped to a folder.
230

Troubleshooting
Problem: A client machine includes two key stores, each one needed for identification on a specific WebSphere server. If the client attempts to connect to one of the WebSphere servers with the wrong key store, the attempt fails. If the client then uses the second, correct key store to connect to the WebSphere server, that attempt also fails. Solution 1: Set up one key store on the client for all WebSphere servers. Solution 2: Set up one key store per IP address range, for all WebSphere servers that use the same user name and password. For a server that uses a different user name and password, set up a key store on another IP range. Key stores are defined in the WebSphere credentials. For details, see WebSphere Protocol and Credentials in Discovery and Dependency Mapping Guide.
Limitation
If DDM finds two cells with the same name on the same host, only one cell configuration (j2eedomain topology) is reported.
231
232
Part VIII
The Network Modules
234
21
Host Resources and Applications
Host Resources and Applications Overview on page 235 Tasks
Host Resources and Applications Workflow on page 237 Revert to Previous Method of Discovering Installed Software on page 244 Reference
Changes to DDM Modules on page 245 Troubleshooting and Limitations on page 248
Concepts
Host Resources and Applications Overview

The Network Host Resources and Applications module discovers resources that exist on a host (for example, Disk, CPU, Users) as well as applications that run on that host. The module also discovers the relationships between the application and the relevant processes, the appropriate services, and the relevant Service Address (port). The Host Resources and Applications by Shell/SNMP/WMI jobs:
Discover the TCP connections of the discovered machines, using Shell or SNMP. Store the information in the Probe-dedicated netflow database. Query the Probe database for TCP information.
235
Chapter 21 Host Resources and Applications
The Host Resources and Applications by Shell/SNMP/WMI jobs also gather connectivity information (either by running netstat commands or the lsof command). The relationships between processes and the relevant Service Address (server port) can be discovered on Windows 2003 and Windows XP, SunOS, Hewlett-Packard UniX (HP-UX), AIX, and Linux operating systems. For the HP-UX and AIX machines, you should install lsof software, which can be downloaded from the Internet from, for example, http://www.netadmintools.com/html/lsof.man.html. You can install lsof software also on SunOs. If you do not, the pfiles software that is installed on SunOS is used.
Note: Process to process (P2P) discovery is the name given to the discovery of processes running on hosts in the environment.
Job Threads
Each job is run using multiple threads. You can define a maximum number of threads that can be used concurrently when running a job. If you leave the box empty, the Probes default threading value is used (8). The default value is defined in DiscoveryProbe.properties in the defaultMaxJobThreads parameter.
regularPoolThreads. The maximum number of worker threads allocated to the multi-threaded activity (the default is 50). priorityPoolThreads. The maximum number of priority worker threads (the default is 20).
236
Note:
The number of actual threads should never be higher than regularPoolThreads + priorityPoolThreads. The jobs in the Network Host Resources and Applications module require a permanent connection to the Probes internal database. Therefore, these jobs are limited to a maximum number of 20 concurrent threads (which is the maximum number of concurrent connections permitted to the internal database). For details on the Max. Threads field, see Execution Options Pane in Discovery and Dependency Mapping Guide.
Tasks
Host Resources and Applications Workflow


Prerequisites on page 238 Network and Protocols on page 238 Pattern Parameters for the Host Resources and Applications by Shell Job on page 239 Pattern Parameters for the Host Resources and Applications by SNMP Job on page 240 Pattern Parameters for the Host Resources and Applications by WMI Job on page 240 Discovery Workflow for the Host Resources and Applications by Shell/SNMP/WMI Jobs on page 241 Discovery Workflow for the Software Element CF by Shell Job on page 241 TCP Discovery on page 241 Discovered CITs on page 242 Topology Map on page 244
237
1 Prerequisites
Verify that the CMDB already contains the Agent and Shell CITs: Modeling > CI Type Manager. Search for Software Element, and verify that Agent and Shell are present:
Note: The jobs in the Network Host Resources and Applications module require a permanent connection to the Probes internal database. Therefore, these jobs are limited to a maximum number of 20 concurrent threads (which is the maximum number of concurrent connections permitted to the internal database). For details on the Max. Threads field, see Execution Options Pane in Discovery and Dependency Mapping Guide.

To run this module, define the following protocols:
NTCmd. For credentials information, see NTCMD Protocol in Discovery and Dependency Mapping Guide. SNMP. For credentials information, see SNMP Protocol in Discovery and Dependency Mapping Guide.
238
SSH. For credentials information, see SSH Protocol in the Discovery and Dependency Mapping Guide. Telnet. For credentials information, see Telnet Protocol in the Discovery and Dependency Mapping Guide. WMI. For credentials information, see WMI Protocol in Discovery and Dependency Mapping Guide. Users do not need root permissions, but do need the appropriate credentials to enable connecting to the remote machines and running the relevant commands.
3 Pattern Parameters for the Host Resources and Applications by Shell Job
For details, see Discovery Pattern Parameters Pane in Discovery and Dependency Mapping Guide.
P2PServerPorts. The service address to be discovered. This parameter can include a number or a known name. You separate entries with commas. An asterisk (*) signifies all ports. The default value is *.
discoverProcesses. False: Only processes that are related to a specified software element are discovered. (The software element is specified in the applicationsSignature.xml file.) True: All processes are discovered. Previously, False signified that no processes are discovered.
discoverServices. False: Only those services that are related to a specified software element are discovered. True: All services are discovered.
239
filterP2PProcessesByName (formerly filterProcessesByName). The names of the processes that are not reported. The default value is system,svchost.exe, lsass.exe,System Idle Process,xCmd.exe. To prevent P2P running, enter an asterisk (*) as the value. ignoreP2PLocalConnections. False: P2P discovery does not ignore local connections. That is, when a client and server are installed on the same host and the client-server relationship connects between them, P2P discovery should report this relationship. lsofPath. The path to the lsof command that enables process communication discovery on UNIX machines. The default value is /usr/local/bin/lsof,lsof,/bin/lsof.
4 Pattern Parameters for the Host Resources and Applications by SNMP Job
For definitions of the parameters, see Pattern Parameters for the Host Resources and Applications by Shell Job on page 239.
5 Pattern Parameters for the Host Resources and Applications by WMI Job
For definitions of the parameters, see Pattern Parameters for the Host Resources and Applications by Shell Job on page 239.
240
6 Discovery Workflow for the Host Resources and Applications by Shell/SNMP/WMI Jobs
In the Run Discovery window, activate the job (Discovery Modules > Host Resources and Applications > Host Resources and Applications by Shell/SNMP/WMI). These jobs discover resources that exist on a host (for example, Disk, CPU, Users) as well as applications that run on that host. The jobs are scheduled to run every day.
7 Discovery Workflow for the Software Element CF by Shell Job

In the Run Discovery window, activate the job (Discovery Modules > Host Resources and Applications > Software Element CF by Shell). This job retrieves the software elements configuration file and maps the file to the correct application by referring to the applicationsSignature.xml file. The triggered CIs are software elements that have Shell running on their host and that include a configuration file definition that matches the definition in the applicationsSignature.xml file. For an example on discovering Oracle configuration files, see Discover Software Elements Scenario in Discovery and Dependency Mapping Guide.
8 TCP Discovery
The Client/server relationship. When checking connections between two destinations (IP and port pairs), DDM uses the following logic to decide which side is the server and which the client (descending, in order of importance):
If one of the ports is a listening port (that is, is marked as listening in the port_process table), then this port is a server port. If one of the ports is used by a process that is known to be a server process, then this port is the server port. If a local port is not listening and the remote side has not yet been processed (TCP discovery has not yet run on the remote side), it is assumed that the remote port is the server port. If neither port is listening and none of the processes is known to be a server process, DDM does not report P2P connectivity.
241
9 Discovered CITs
For details on discovered CITs, see Discovered CITs Pane in Discovery and Dependency Mapping Guide.
The following CITs are discovered by the Host Resources and Applications by Shell job:
The following CITs are discovered by the Host Resources and Applications by SNMP job:
242
The following CITs are discovered by the Host Resources and Applications by WMI job:
The following CITs are discovered by the Software Element CF by Shell job:
The attributes for the resource name and its root container (that is, its parent) are updated during the run.
243
10 Topology Map
Revert to Previous Method of Discovering Installed Software

The Host Resources and Applications by WMI job discovers installed software that is installed with the WMI Windows Installer Provider. Discovery is faster than previously. If the software is not installed with the Windows Installer, you must use the previous mechanism to discover the software. To revert to the previous discovery mechanism for this job: 1 Access the Host Resources and Applications by WMI pattern: Resource Configuration > Host_Resources_By_WMI > Patterns > WMI_HR_All. 2 In the Pattern Signature tab, locate the Discovery Pattern Parameters pane. 3 Double-click the discoverInstalledSoftwareByOldMechanism parameter to change the default value from false to true.
244
4 Save the change. A warning message is added to the communication log.

Reference
Changes to DDM Modules

The following changes have been made to the DDM modules:
High-Level Changes
The TCP Java code has been rewritten in Jython and refactored to enable end users to better understand its logic. The discoverProcess.xml configuration file is no longer supported and its code has been removed. You should move all process information that previously resided in this file to the application signature file (applicationsSignature.xml).
Changes to the Host Resources Module
The Network Host Resources module has been renamed to Network Host Resources and Applications. All Host Resources by xxx jobs have been renamed to Host Resources and Applications by xxx. For example, the Host Resources by Shell job is now the Host Resources and Applications by Shell job. TCP discovery (formerly used by the Collect Network Data by Shell/SNMP jobs) is now used by the Host Resources and Applications by Shell/SNMP jobs, because only Shell and SNMP agents are discovered. P2P discovery (formerly used by the Collect Network Data by Shell/SNMP jobs) is now used by the Host Resources and Applications by Shell job, because only Shell agents are discovered.
245
The following parameters have changed:
discoverProcesses. False: Only processes that are related to a specified software element are discovered. (The software element is specified in the applicationsSignature.xml file.) True: All processes are discovered. Previously, False signified that no processes are discovered. discoverServices. False: Only those services that are related to a specified software element are discovered. True: All services are discovered. Previously, False signified that no services are discovered.
The following parameters have been removed: filterByDiscoveredProcesses, noWMIcUsage.
TCP Discovery
The useLSOF parameter has been removed. Instead, the lsof command is used for operating systems that support it (HP-UX, AIX, SunOS). If this command fails, the standard netstat command is used. For SunOS, the pfiles command is also used.
P2P Discovery
P2P now runs on a single host destination together with process and TCP discovery. (This behavior differs from the previous version, when the Probe was the trigger for P2P and the discovery ran across the whole Probe range.)
Parameters. The following parameter name has changed: filterP2PProcessesByName (formerly filterProcessesByName). Reporting topology. The following topologies illustrate the results of running the Host Resources and Applications By Shell job to discover client/server relationships. The results depend on whether the remote side has already been discovered and whether P2P information is available on both the local and remote side.
246
Deployed Software View
P2P Information Available on Local and Remote Sides
Process Found on Client Side, Server Side Not Yet Discovered or Does Not Support P2P
247
P2P Information Not Available on Client Side, Available on Server Side
P2P Information Not Available on Local and Remote Sides
To discover processes and software running on a Solaris machine, verify that the /usr/ucb/ps utility is installed on the Solaris machine.
When DDM discovers installed software by WMI, and the software does not include a defined name, DDM does not report the software entity to the CMDB.
248
22
Network Basic
Concepts
Host Connection by Shell: Discover Windows Running F-Secure on page 250
Overview
You activate the jobs in the network modules to discover information about host components, for example, which hosts have open TCP/UDP ports, the ARP table of a router that is using the SNMP protocol, and so on. For details on using a wizard to discover the network, see Infrastructure Wizard in Discovery and Dependency Mapping Guide.
Tasks
249
Chapter 22 Network Basic
Host Connection by Shell: Discover Windows Running F-Secure

When running the Host Connection by Shell job to discover Windows machines, on which an SSH server running the F-Secure application is installed, you must make the following modifications to F-Secure:

Stop the F-Secure service completely. Verify that there are no F-Secure leftover processes still running (fssh* processes). Alter the following lines in the sshd2_config file. This is a F-Secure configuration file that resides in the F-Secure installation directory.
The DoubleBackspace setting should contain a no value, that is, DoubleBackspace no. The EmulationType setting should contain a raw value, that is, EmulationType raw. The EmulationTypeForCommands setting should contain a raw value, that is, EmulationTypeForCommands raw.
Save the altered sshd2_config file. Restart the F-Secure service.
Note:
The DDM Probe enables an SSH-based connection to remote Windows machines only if the remote SSH server providers are Open-SSH or F-Secure. For Open-SSH (that provides SSH servers for the Windows, UNIX, and Linux operating systems), DDM supports connections to Open-SSH only if the Open-SSH version is later than, or equal to, 3.7.1 (for any operating system).
250
23
Layer 2
Concepts
Discover Layer 2 Objects on page 252
Overview
The Layer 2 package discovers the Layer 2 topology that includes the switches tree topology (the backbone links between the switches) and also the end user connections to the switch-ports (the Layer 2 links between a switch and a host). The Layer 2 package is based on the SNMP protocol.
251
Chapter 23 Layer 2
The following image illustrates a router connecting overlapping VLANs/ELANs:
Tasks
Discover Layer 2 Objects

Note: Layer 2 discovery runs on Catalyst (Cisco Systems) network switches only.
This task describes how to discover Layer 2 objects. This task includes the following steps:

Prerequisites on page 253 Discovery Workflow on page 254 The Layer2 Enrichment Job on page 263 Discovered CITs on page 264 Layer 2 Relationships on page 265 Topology Map on page 266 Troubleshooting and Limitations on page 266
252
Chapter 23 Layer 2
1 Prerequisites
Important:
All network connection jobs should finish running before you activate the Layer 2 jobs. Make sure that there is SNMP access to all switches in the environment to be discovered, as that is a key requirement for fully discovering the Layer 2 topology. When defining the SNMP protocol credentials, have available the Port and Community authentication parameters.
In the Network Layer 2 module, run the Host Networking By SNMP job. As a result of this run, DDM saves SNMP CIs to the CMDB. You should run this job on all SNMP agents on the switches that were discovered in the environment. The to-be discovered Layer 2 link names are dependent on this discovery. (Layer 2 link names are the replica of the relevant interface index name and description that the host base pattern discovers.)
Note: Layer 2 discovery is based on the connection jobs for the following reasons:
The Layer 2 connectivity between the switch-port to the host is based on the host MAC address. These MAC addresses are discovered by the network connection jobs (Host Interfaces). The trigger of the Layer 2 job is dependent on the type of the discovered switch. The switch class and type is discovered by the SNMP connection job.
253
Chapter 23 Layer 2
Important: The Layer 2 package includes four jobs. Each job discovers a part of the Layer 2 architecture. You should activate these jobs in the following order.
a Activate the VLANS by SNMP job. The trigger for this job is the snmp_of_catalyst_switch TQL. The Switch CIT is either:

an SNMP object that holds a description containing the string atalyst an SNMP agent that is connected to a switch that holds an operating system or model attribute value containing the string atalyst
SNMP Description Like %atalyst%:
254
Chapter 23 Layer 2
Host Operating System Like %atalyst% OR Host Model Like %atalyst%:
The SNMP_Net_Dis_Catalyst_Vlans.py script retrieves the VLAN, ELAN name, and VLAN number per ELAN tables. b Activate the VLAN ports by SNMP job. The trigger for this job is the catalyst_vlan TQL. This is a VLAN object that has a connection to:
a switch with an SNMP object that holds a description containing the string atalyst a switch that holds an operating system or model attribute value containing the string atalyst
255
Chapter 23 Layer 2
The trigger is placed on the VLAN object instead of on the SNMP itself because the VLAN object must be authenticated with a special community string (and not with the regular community string that was discovered on the SNMP object on the discovered switch). This community string should hold the value <COMMUNITY>@<VLAN NUMBER>. For example, if the community string is public and the discovered VLAN number is 16, the community string is public@16. For details on the SNMP protocol parameters, see SNMP Protocol in Discovery and Dependency Mapping Guide. SNMP Description Like %atalyst%:
256
Chapter 23 Layer 2
The SNMP_Net_Dis_VMS_catalyst.py script retrieves the Base MAC table and Port number If Index table. c Activate the Layer2 Topology Bridge based by SNMP job. The trigger for this job is the catalyst_bridge_no_vlan TQL. This is a Bridge object that has a connection to:
a switch with an SNMP object that holds a description containing the string atalyst a switch that holds an operating system or model attribute value containing the string atalyst. the NOT VLAN Bridge MAC is null attribute
In both the first two cases, the switch should have zero connections to a VLAN.
257
Chapter 23 Layer 2
258
Chapter 23 Layer 2
259
Chapter 23 Layer 2
NOT VLAN Bridge MAC is null:
Both this job (Layer2 Topology Bridge based by SNMP) and the following job (Layer2 Topology VLAN based by SNMP) use the bridgePortDisc.py script. The difference between the jobs in this script is the way they retrieve the community string:
Layer2 Topology Bridge based by SNMP uses the regular SNMP community authentication. The job is triggered on the Bridge only when the discovered switch has no VLANS. Layer2 Topology VLAN based by SNMP is triggered on each one of the VLANs discovered on the switch. This job uses the relevant special community authentication, as explained in step b, based on the triggered VLAN number.
260
Chapter 23 Layer 2
Note:
When the VLANs by SNMP job runs, it discovers Layer 2 topology that is relevant to the discovered VLAN only. Bridge Layer 2 discovery. If a machine has no VLANs, discovery is triggered on the bridge of the switch. DDM retrieves the Layer 2 topology of all the switches. If you dispatch the Bridge Layer 2 job on the bridge of a switch that holds VLANs only, the default VLAN Layer 2 topology is discovered.
d Activate the Layer2 Topology VLAN based by SNMP job. The trigger for this job is the catalyst_vlan_with_bridge TQL. This is a VLAN object with a value in its bridge_mac attribute. It should also have a connection to either:
a switch with an SNMP object that holds a description containing the string atalyst a switch that holds an operating system or model attribute value containing the string atalyst
261
Chapter 23 Layer 2
262
Chapter 23 Layer 2
For details on the bridgePortDisc.py script, see step c. The Backbone and Layer 2 links are created by the enrichments of the Layer 2 package, based on the data that was discovered by these jobs. After these jobs have run, job statistics do not show any Layer 2 or Backbone links as parts of the results.
3 The Layer2 Enrichment Job

This job replaces a previous enrichment. Its purpose is to remove Layer 2 links between physical ports and an interface that has no matching MAC address. This job is not activated automatically as part of the installation, so you should manually activate it.
263
Chapter 23 Layer 2
4 Discovered CITs
264
Chapter 23 Layer 2
5 Layer 2 Relationships
A Layer 2 switch can be connected to its ports directly or through a VLAN. The Bridge CIT represents the basic MAC address (Network Interface Card) on which the ports are located. Each switch-port can be connected to a host or interface object (the end user machines) by a Layer 2 link, or to a port-switch by a Backbone link.
265
Chapter 23 Layer 2
6 Topology Map
If the results of the discovery return empty, verify that you have access to the discovered SNMP agent (or to the SNMP agent using the special community authentication) and that all the requested MIB tables are responding to SNMP requests from the Probe machine. For details on the MIB tables, refer to the appropriate script. In cases where the reported bridge MAC address is 000000000000, "", or null, the pattern does not report results. If the retrieved basic bridge MAC (retrieved from the 1.3.6.1.2.1.17.1.1 table) is not the same as the given bridgeId in the destination data, the pattern returns zero results. In the case of SNMP_Dis_L2_Bridge, bridgeId is set by bridge_basemacaddr. In the case of SNMP_Dis_L2_VLAN, bridgeId is set by vlan_bridgemac.
266
24
Network Advanced
Concepts
Discover DNS Zones on page 267
Overview
You can discover the Domain Name System (DNS) server topology, that is, the zones that each server manages, and the IPs in each zone.
The pattern is triggered on every DNS with WMI: DDM activates the registry query to retrieve all the zones that this DNS manages. DDM queries each zone by activating Nslookup on the Probe against the DNS servers.
Tasks
Discover DNS Zones

This task describes how to discover DNS zones. This task includes the following steps:

Network and Protocols on page 268 Discovery Workflow on page 268
267
Chapter 24 Network Advanced

Discovered CITs on page 268 Topology Map on page 269 Troubleshooting and Limitations on page 269

Nslookup (Zone transfer)
In the Run Discovery window, activate the DNS Zone by Nslookup job (Network Advanced module).
3 Discovered CITs
268
4 Topology Map

Check that Nslookup is permitted in the environment. In many environments, Nslookup is blocked by the network administrator, in which case DDM cannot retrieve data.
269
270
25
Credential-less
Concepts
Discover Host Fingerprint with Nmap on page 271
Overview
Nmap is a utility for network exploration that uses raw IP packets to determine which hosts are available on the network, which services those hosts are offering, which operating systems they are running on, and so on. Nmap also calculates to what extent the operating system result is accurate, for example, 80% accuracy. The Host Fingerprint using nmap job, which relies on the Nmap utility, reports the Nmap accuracy value on the host_osaccuracy attribute on the Host CI.
Tasks
Discover Host Fingerprint with Nmap

This task describes how to use the Host Fingerprint using nmap job to discover hosts, operating systems, network interfaces, applications, and running services.
271
Chapter 25 Credential-less

Prerequisites on page 272 Discovery Workflow on page 275 Pattern Parameters on page 275 Discovered CITs on page 276 Troubleshooting and Limitations on page 276
1 Prerequisites
Use the following procedure to install Nmap and WinPcap. Perform the following procedure on every Probe machine that is to run the Host Fingerprint using nmap job: a Run nmap-4.76-setup.exe from C:\hp\DDM\DiscoveryProbe\nmap_install. b Accept the terms of the license and click I agree. The Choose Components dialog box opens. c Select Nmap Core Files, Register Nmap Path, and WinPcap 4.02.
272
Click Next. The Choose Install Location dialog box opens.
d Accept the default location or enter another location. Click Install. Nmap is installed. The WinPcap installation dialog box opens immediately after the Nmap installation is complete. e Accept the terms of the license and click Next. The Choose Install Location dialog box opens.
273
f Accept the default location or enter another location. Click Install. The Finished dialog box opens.
Click Finish. The WinPcap Options dialog box opens.
g Clear the check boxes and click Next. h Click Finish.
274
The following software is added to the Probe machine:

Nmap 4.76 winpcap-nmap 4.02 Microsoft Visual C++ Redistributable - x86 9.0.21022
To verify, access the Add/Remove Programs window.
This job is triggered on any discovered IP address.
3 Pattern Parameters
To view the pattern parameters: Run Discovery > Network Credentialless Discovery > Host Fingerprint using nmap > Properties tab > Parameters pane. For details on overriding parameters, see Parameters Pane in Discovery and Dependency Mapping Guide.
Create_Application_CI. Creates an application CI based on the port fingerprint information. Perform_Port_Fingerprints. Tries to discover opened ports. discover_os_name. Discovers host OS, which may have some inaccuracy. nmap_host_timeout. The length of time Nmap is allowed to spend scanning a single host (in seconds). scan_known_ports_only. Scans for ports listed in the portNumberToPortName.xml file.
275
scan_these_ports_only. Limits the range of ports to be scanned, for example, T:1-10,42,U:1-30 (discover TCP ports 1 to 10 and 42 and UDP ports 1-30). If this parameter is left empty, the Nmap default is used.
4 Discovered CITs

Error Message Can't parse XML document with Nmap results. Skipped. Error nmap result file is missing Reason nmap.exe failed before it could create a valid XML file. nmap.exe failed before it could create an XML file. Solution
Try to restart the Nmap job. Try to reduce the number of threads for the
Nmap job.
Try to restart the Nmap job. Try to reduce the number of threads for the
Nmap job.
276
Error Message The system cannot execute the specified program (in the communication log file)
Reason The Windows system cannot launch the Nmap application.
Solution Verify that:

The correct Nmap version has been
downloaded and installed.

WinPcap has been installed.
For details on these installations, see Prerequisites on page 272. If you have installed Nmap and WinPcap, and the error message still appears in the communication log, install vcredist_x86.exe from C:\hp\DDM\DiscoveryProbe\root\lib\collec tors\probeManager\discoveryResources.
Nmap is not installed on Probe machine
Nmap is not installed on the Probe machine.
Try to launch Nmap from the command line. Make sure that Nmap is installed. For details on the installation, see Prerequisites on page 272.
277
278
26
Active and Passive Discovery Network Connections
Concepts
Discover Processes on page 280
Overview
All jobs in these modules run queries against the Probes MySQL database to retrieve data inserted by the Host Resources and Applications jobs. For details on Host Resource jobs, see Host Resources and Applications Overview on page 235. The DDM Probe includes a built-in MySQL database so there is no need to install a separate MySQL instance for NetFlow. Instead, data is saved to a dedicated scheme (called netflow for historical reasons).
Tasks
279
Chapter 26 Active and Passive Discovery Network Connections
Discover Processes
This task describes how to discover processes. This task includes the following steps:

Prerequisites on page 280 Job Order and Scheduling on page 280 Supported Versions on page 281 Discovery Pattern Parameters on page 281 Network and Protocols on page 281 Discovery Workflow on page 282 The IP Traffic by Network Data Job on page 283 The Potential Servers by Network Data Job on page 284 The Server Ports by Network Data Job on page 283 The Servers by Network Data Job on page 282 Discovered CITs on page 286
1 Prerequisites
a Run the following jobs in the Network Basic module:

Range IPs by ICMP job Host Connection by Shell/SNMP/WMI (NTCmd, SSH, Telnet, and WMI CIs are discovered)
b Run Host Resources and Applications by Shell/SNMP/WMI in the Host Resources and Applications module.
2 Job Order and Scheduling

By default, all queries are scheduled to be run on a relatively frequent basis (every hour). The queries themselves are not re-run unless the data set has changed since the last run, in order not to waste CPU cycles on the Probe.
280
Although you can activate the Host Resources and Applications job together with the relevant queries, you would probably not see any results until at least one hour has passed before the next scheduled invocation of the query. This is because by the time the first set of queries is run, no data has yet been gathered. So a best practice is to make sure data gathering is complete and only then launch the query and see the result it populates.
DDM supports NetFlow versions 5 and 7.

You can filter the list of processes to run only those processes that retrieve data that is of interest to you. The network connectivity of these processes is omitted. To override a process parameter value: a Select Run Discovery (Advanced Mode) > Network Connections Active Discovery. b Select the job, select the Properties tab, and locate the Parameters pane. For details on overriding a parameter, see Parameters Pane in Discovery and Dependency Mapping Guide.

To discover network connections, define the following protocols:
SNMP. For credentials information, see SNMP Protocol in Discovery and Dependency Mapping Guide. NTCmd. For credentials information, see NTCMD Protocol in Discovery and Dependency Mapping Guide. SSH. For credentials information, see SSH Protocol in Discovery and Dependency Mapping Guide. Telnet. For credentials information, see Telnet Protocol in Discovery and Dependency Mapping Guide. WMI. For credentials information, see WMI Protocol in Discovery and Dependency Mapping Guide.
281
Note: None of these protocols is mandatory, but WMI alone does not retrieve network data.
In the Run Discovery window, activate the jobs in the following order:

The Servers by Network Data Job on page 282 The IP Traffic by Network Data Job on page 283 The Server Ports by Network Data Job on page 283 The Potential Servers by Network Data Job on page 284
7 The Servers by Network Data Job

This job enables the discovery of specific service names (the services parameters). The service name to port numbers are still configurable through the portNumberToPortName.xml file. The links discovered by this job are clientserver links (between the client IP and the server port to which it connects) and dependency links between the related hosts. You can override the values of the following pattern parameters:
ignoreLocalConnections. DDM should ignore local connections. The default is false.
282
ignoreUnackedTcpConn. DDM does not report unacknowledged connections. ignoredIps. IPs that should be filtered. The values are comma separated (for example, 10.*.*.*,15.45.*.*). The default is none (that is, the value is empty). includeOutscopeClients/Servers. Prevents discovery of clients or servers on machines that are out of a Probes network scope. onlyHostDependLinks. Enables discovery of dependency links only (without the clientserver links). services. The following default services are discovered: http, https, telnet, ssh, rmi, websphere, weblogic, weblogicSSL, oracle, sql, netflow, siebel, and sap. This parameter can also include specific numbers and an asterisk to represent all known ports. updateUtilizationInfo. Relevant only for NetFlow and can be used to prevent reporting the packets and octets count information on the clientserver links.
8 The IP Traffic by Network Data Job

This job discovers traffic links between all communicating IPs. The traffic links are populated between any two IPs that are seen to communicate. An attribute is defined on these links with the value of the top ports (the most important TCP/UDP ports) that are found between those two IPs/hosts. The top ports are calculated according to the number of clients and the size of the network traffic between them. You can configure the maximum number of recognized ports (in which you are interested) through the maxPorts parameter.
9 The Server Ports by Network Data Job

This job discovers open server ports according to a list of specified services. This can be useful if you do not want to discover the TCP connections themselves but do want to know which ports are open, without performing any TCP port scanning (which may be dangerous in some organizations). This discovery job is not relevant for NetFlow data as there is no LISTEN flag in this case.
283
You can override the values of the following pattern parameters:
includeOutscopeServers. Prevents discovery of servers on machines that are out of a Probes network scope. services. The following default services are discovered: http, https, telnet, ssh, rmi, websphere, weblogic, weblogicSSL, oracle, sql, netflow, siebel, and sap. This parameter can also include specific numbers and an asterisk to represent all ports.
10 The Potential Servers by Network Data Job

This job can be used in situations where you need to find clientserver links but without defining the port numbers in advance. The server port is defined according to the criteria passed as job parameters: minClient (the minimum number of clients for the service), minPackets/minOctets (minimum packets and octets relevant only for NetFlow). You can override the values of the following pattern parameters:
284
disregardListenPorts. False: DDM checks whether the port is marked as a listening port. If it is, DDM does not check the minimal conditions (minOctets, minClients, and minPackets). True: DDM does not check if the port is a listening port and instead uses the minimal conditions (minOctets, minClients, and minPackets). The default is false. ignoreLocalConnections. Local connections should not be discovered. The default is false. ignoredIps. IPs that should be filtered. The values are comma separated (for example, 10.*.*.*,15.45.*.*). The default is none (that is, the value is empty). includeOutscopeClients/Servers. Prevents discovery of clients or servers on machines that are out of a Probes network scope. minClients. The number of connected clients that must be discovered to make this service a potential server. minOctets. The number of octets (bytes) to be sent by a client to a service, so that the client is included in the discovery. minPackets. The number of packets to be sent by a client to a service, so that the client is included in the discovery. protocols. Limit the query to these IP protocols. The values are comma separated. The default is TCP.
Important: This job does not come out-of-the-box with a Trigger TQL because it is not intended to be used on many triggers. Rather, you should activate the job manually against specific IP instances, to find unknown server ports. It is preferable to add the ports afterwards to the portNumberToPortName.xml file and continue discovery through the Servers by Network Data.
285
11 Discovered CITs
Client-Server. DDM determines which machine is the server and which the client:
If one end is discovered as a listening port, then this end is presumed to be a server. If one end has more than two connections on its ports, it is presumed to be the server. If both ends have just one connection to a port, DDM identifies whether the end is a server by checking the ports and the portNumberToPortName.xml file (Manage Discovery Resources > Discovery Resources > Network > Configuration Files). If the previous is not the case, the port is checked to see whether it equals, or is less than, 1024. In this case, DDM identifies it as a server.
Talk. This link is created between two processes only if DDM does not recognize the Client-Server link between the processes. The Talk link reports bidirectionally.
286
27
Load Balancer
Concepts
Discover Load Balancers on page 288
Overview
DDM discovers the following load balancers:

F5 BIG-IP Local Traffic Manager (LTM) Nortel Application Switches (formerly known as Alteon Application Switches) Cisco Content Services Switches (CSS)
Tasks
287
Chapter 27 Load Balancer
Discover Load Balancers

This task explains how to discover load balancers. This task includes the following steps:

Supported Versions on page 288 Prerequisites on page 289 Discovery Workflow on page 290 Load Balancer CITs on page 290 The Load_balancing Package on page 291 The Alteon_application_switch Package on page 292 The F5_BIGIP_LTM Package on page 293 The Cisco_CSS Package on page 294 Topology Map on page 295
The supported version for each load balancer is as follows:

F5 BIG-IP Local Traffic Manager, versions 9 and 4. Nortel Application Switches. No known limitations Cisco Content Services Switches. No known limitations.
288
2 Prerequisites
Run the Host Connection by SNMP job to discover and create SNMP CIs which answer the following requirements:
To be the trigger TQL for the Alteon application switch by SNMP job with the following condition:
SNMP OID Like 1.3.6.1.4.1.1872.2.5%
To be the trigger TQL for the F5 BIG-IP LTM by SNMP job with the following condition:
SNMP OID Like 1.3.6.1.4.1.3375%
289
To be the trigger TQL for the Cisco CSS by SNMP job with the following condition:
SNMP OID Like 1.3.6.1.4.1.9.9.368% OR 1.3.6.1.4.1.2467%
Host Connection by SNMP. For details on the prerequisites to running a load balancer job, see Prerequisites on page 289. Any of the following jobs:

F5 BIG-IP Local Traffic Manager (LTM) Nortel Application Switches (formerly known as Alteon Application Switches) Cisco Content Services Switches (CSS)
4 Load Balancer CITs

The following CITs model load balancer topology:
Load Balancer Software
This CIT represents software that provides load balancing solutions. For details on the supported load balancers, see Overview on page 287.
290
Clustered Server
A clustered server is a traffic-management object on the system that can balance traffic load across a pool of servers. Clustered servers increase the availability of resources for processing client requests. The primary function of a clustered server is to receive requests and distribute them to pool members according to criteria you specify.
Load Balancing Cluster
A load balancing cluster (or pool) is a logical set of devices that are grouped together to receive and process traffic. Instead of sending client traffic to the destination IP address specified in the client request, the virtual server sends the request to any of the servers that are members of that pool. This helps to efficiently distribute the load on your server resources.
5 The Load_balancing Package

This package contains data that is common to all load balancer solutions.
291
The Network Load balancer module contains the load balancing jobs:

Alteon application switch by SNMP Cisco CSS by SNMP F5BIG-IP LTM by SNMP The following view displays the topology (View Manager > Root > Application > Load balancer):
6 The Alteon_application_switch Package

This package contains a class model definition, a pattern, and a job used to discover Nortel application switches by SNMP. To run this package, activate the Alteon application switch by SNMP job. DDM discovers Nortel (Alteon) load balancers and all related CIs.
292
The following SNMP tables are queried:

Table Name Virtual servers Virtual services Real groups Real servers Port links Ports Name From MIB slbCurCfgVirtServerTable slbCurCfgVirtServicesTable slbCurCfgGroupEntry slbCurCfgRealServerTable slbCurCfgRealServPortTable slbCurCfgPortTable OID 1.3.6.1.4.1.1872.2.5.4.1.1.4.2.1 1.3.6.1.4.1.1872.2.5.4.1.1.4.5.1 1.3.6.1.4.1.1872.2.5.4.1.1.3.3.1 1.3.6.1.4.1.1872.2.5.4.1.1.2.2.1 1.3.6.1.4.1.1872.2.5.4.1.1.2.5.1 1.3.6.1.4.1.1872.2.5.4.1.1.5.2.1
7 The F5_BIGIP_LTM Package

This package contains a class model definition, a pattern, and a job used to discover the F5 BIG-IP Local Traffic Manager (LTM) by SNMP. This package supports F5 BIG-IP LTM, versions 4 and 9. To run this package, activate the F5 BIG-IP LTM by SNMP job. DDM chooses all SNMPs related to F5 and runs against them. The following SNMP tables are queried for version 9:
Table Name General information Virtual servers Pools Pools to server Pool members Rules to servers Rules Name From MIB sysProduct ltmVirtualServTable ltmPoolTable ltmVirtualServPoolTable ltmPoolMemberTable ltmVirtualServRuleTable ltmRuleTable OID 1.3.6.1.4.1.3375.2.1.4 1.3.6.1.4.1.3375.2.2.10.1.2.1 1.3.6.1.4.1.3375.2.2.5.1.2.1 1.3.6.1.4.1.3375.2.2.10.6.2.1 1.3.6.1.4.1.3375.2.2.5.3.2.1 1.3.6.1.4.1.3375.2.2.10.8.2.1 1.3.6.1.4.1.3375.2.2.8.1.2.1
293
The following SNMP tables are queried for version 4:

Table Name General information Virtual servers Pools Pool members Name From MIB globalAttributes virtualServerTable poolTable poolMemberTable OID 1.3.6.1.4.1.3375.1.1.1.1 1.3.6.1.4.1.3375.1.1.3.2.1 1.3.6.1.4.1.3375.1.1.7.2.1 1.3.6.1.4.1.3375.1.1.8.2.1
8 The Cisco_CSS Package

This package contains a class model definition, a pattern, and a job used to discover Cisco Content Services Switches by SNMP. This package supports all versions of Cisco CSS. To run this package, activate the Cisco CSS by SNMP job. DDM chooses all SNMPs related to Cisco CSS and runs against them.
Note: Some services may not be discovered by this package if no content rule is defined for them.
Discovery of CSS is based on three tables: apCntTable, apSvcTable, and apCntsvcTable (see the following table):
apCntTable provides information about virtual addresses, virtual services, and pools. apSvcTable provides information about physical hosts included in the pool. apCntsvcTable describes which host is included in which pool. apSvcTable can contain entries for which there is no corresponding row in apCntsvcTable. In this case, such hosts are skipped.
294
Table name CNT SVC CNT to SVC
Name from MIB apCntTable apSvcTable apCntsvcEntry
OID 1.3.6.1.4.1.2467.1.16.4.1 or 1.3.6.1.4.1.9.9.3681.16.4.1 1.3.6.1.4.1.2467.1.15.2.1 or 1.3.6.1.4.1.9.9.3681.15.2.1 1.3.6.1.4.1.2467.1.18.2.1 or 1.3.6.1.4.1.9.9.3681.18.2.1
9 Topology Map
295
296
Part IX
The Virtual Machines Module
298
28
VMware

Tasks
Discover VMware Infrastructure Topology on page 299 Discover VMware VMotion on page 321
Discover VMware Infrastructure Topology

This task describes how to discover the VMware Infrastructure Topology suite of applications. You can discover virtual machines (VM), processors, memory, storage, and network resources that are running on VMware. This task includes the following steps:

Supported Protocol Versions on page 300 Supported VMware Servers on page 300 SSL Support Details on page 301 Prerequisites Add *.jar Files on page 301 Prerequisites Run Host Discovery on page 302 Prerequisites Run WMI Discovery on page 302 Prerequisites Run Processes Discovery on page 302 Prerequisites VMware Infrastructure Permissions on page 302 Network and Protocols on page 303 Discovery Workflow Overview on page 304
299
Chapter 28 VMware
Discovery Workflow VMware VirtualCenter Connection by WMI and VIM on page 304 Discovery Workflow VMware VirtualCenter Topology by VIM on page 308 Discovery Workflow VMware ESX Connection by VIM on page 312 Discovery Workflow VMware ESX Topology by VIM on page 315 Virtual Topology Map on page 318 Licensing Topology Map on page 319 Troubleshooting and Limitations on page 319
1 Supported Protocol Versions

There are two protocol versions available: 2.0 and 2.5. The new versions of the ESX servers support the VMware Infrastructure SDK API, version 2.5 but transparently support connections using the old version of the protocol, providing backward compatibility. Older versions of the servers support the VMware Infrastructure SDK API, version 2.0 only. For details, see the next section. For details on the protocol, see VMware Infrastructure Management (VIM) Protocol in Discovery and Dependency Mapping Guide.
2 Supported VMware Servers

vCenter Server 4. ESX Server 4.0. Note that DDM does not report licensing information for ESX 4.0 servers. ESX Server 3.5, VirtualCenter Server 2.5, and ESX Server 3i support VMware Infrastructure SDK API 2.5. The servers can be connected using protocol version 2.5 or 2.0. ESX Server 3.0.x, VirtualCenter Server 2.0.x support VMware Infrastructure SDK API 2.0. The servers can be connected using protocol version 2.0 only.
300
Chapter 28 VMware
3 SSL Support Details

Web services use http transport which can also be transferred over SSL. The VMware Infrastructure Management (VIM) protocol uses SSL by default, but it is possible to configure it without SSL usage. Each server supporting the VIM protocol (VirtualCenter server or ESX server) has its own SSL certificated. Currently, DDM supports only one strategy (accept all certificates always). The following code is an example of how DDM sets the global property for the Axis engine:
System.setProperty('org.apache.axis.components.net.SecureSocketFactory', 'org.apache.axis.components.net.SunFakeTrustSocketFactory')
4 Prerequisites Add *.jar Files

To use the VMware Infrastructure Management protocol, add the following *.jar files from the SDK to the Probe:
vim.jar. Contains Java classes generated by Axis from WSDL for API version 2.0 vim25.jar. Contains Java classes generated by Axis from WSDL for API version 2.5 These *.jar files are used without any modification together with the Axis engine. All protocol interactions are performed by working with objects from these *.jar files (instantiating objects, calling methods, getting result objects, and so on).
Note: These *.jar files are not included by default with DDM due to licensing issues.
a Download the VMware Infrastructure SDK from http://www.vmware.com/support/developer/vc-sdk/, version 2.5.0. b Locate the vim.jar and vim25.jar files in the SDK\samples\Axis\java directory.
301
Chapter 28 VMware
c Copy the *.jar files to the C:\hp\DDM\DiscoveryProbe\root\ext\ vmware directory. d To load the *.jar files, restart the Probe.
5 Prerequisites Run Host Discovery

To connect to each potential VMware server (vCenter, VirtualCenter, or ESX), discover its Host CI by running one of the Host Connection by Shell/WMI/SNMP jobs (in the Network Basic module).
6 Prerequisites Run WMI Discovery

To connect to each potential vCenter or VirtualCenter server (this is not required for ESX), make the WMI connection available for the host by running the Host Connection by WMI job.
7 Prerequisites Run Processes Discovery

To connect to each potential VMware server (vCenter, VirtualCenter, or ESX), you must discover Process CIs that match certain criteria, by running one of the Host Resources and Applications by Shell/WMI/SNMP jobs (in the Network Basic module).
8 Prerequisites VMware Infrastructure Permissions

The VMware Infrastructure Management (VIM) protocol requires the following permissions:
System.Read permissions for users performing discovery. Users should have permissions for all entities being discovered, and must have been assigned at least a Read-Only role. Global.Licenses permissions to obtain the total and available number of licenses for each License Feature. If the user does not have these permissions, these attributes remain empty. The WMI protocol used in the vCenter or VirtualCenter connection pattern requires the following permissions:
Users should be able to perform remote queries for the root\default namespace (Remote Enable, Enable Account, and Execute Methods); administrators usually have these permissions.
302
Chapter 28 VMware

The WMI, Shell (Telnet, SSH, NTCmd), and SNMP protocols are required to discover hosts and host processes. The WMI protocol is required to discover the vCenter or VirtualCenter connectivity pattern. The VMware Infrastructure Management (VIM) protocol is required for all VMware jobs.
WMI. For credentials information, see WMI Protocol in Discovery and Dependency Mapping Guide. The protocol requires the user name and password and, optionally, the domain name. NTCmd. For credentials information, see NTCMD Protocol in Discovery and Dependency Mapping Guide. SSH. For credentials information, see SSH Protocol in Discovery and Dependency Mapping Guide. Telnet. For credentials information, see Telnet Protocol in Discovery and Dependency Mapping Guide. These protocols require the user name, password, and domain name (the domain name is optional for NTCmd).
SNMP. For credentials information, see SNMP Protocol in Discovery and Dependency Mapping Guide. This protocol requires the community name (for v2), the user name (for v3), and the password (for v3). VMware Infrastructure Management (VIM). For credentials information, see VMware Infrastructure Management (VIM) Protocol in Discovery and Dependency Mapping Guide. This protocol requires a user name and password. Port Number is optional. Use SSL. true: select if the VMware servers are configured to use SSL by default. false: select if the VMware servers are configured to use non-secured http.
303
Chapter 28 VMware
10 Discovery Workflow Overview

The Network VMware module includes two jobs for vCenter or VirtualCenter Server discovery and two for ESX Server discovery:
If the VMware Infrastructure environment is managed by vCenter or VirtualCenter Servers, run the VMware VirtualCenter Connection by WMI and VIM job, followed by the VMware VirtualCenter Topology by VIM job. If the VMware Infrastructure environment includes unmanaged ESX servers (standalone) or the entire environment is unmanaged, run the VMware ESX Connection by VIM job, followed by the VMware ESX Topology by VIM job.
Note:
The Manual VMware VIM Connection job is intended for use in those instances when the above four jobs cannot discover the VMware environment. You must, however, manually run this job, that is, you specify a URL (you need to know its format), you activate the job, and you choose the Probe. DDM models the Console Operating System (COS) as a Unix CI Type, and models the hardware running the ESX as a VMWare ESX Server CI Type. Once modeled, these two CITs have the same or similar display names, but represent different entities, each one identified by its own set of unique properties.
11 Discovery Workflow VMware VirtualCenter Connection by WMI and VIM

This job discovers vCenter or VirtualCenter Servers. Trigger CI. WMI.
304
Chapter 28 VMware
Trigger TQL and Node Conditions:
Triggered CI Data:

credentialsId. The credentials ID of the WMI agent CI. ip_address. The IP address, taken from the WMI agent CI. Discovery Pattern Parameters. None.
305
Chapter 28 VMware
DDM runs the following processes:
Runs through all defined credentials for the VMware Infrastructure Management (VIM) protocol. If the Use SSL parameter is set to true, the default prefix is HTTPS, otherwise the prefix is set to HTTP. If the user has entered a port number in the VIM protocol, this value is used for the port. If not, a WMI query is performed to extract the port number from the registry. DDM queries HKLM\SOFTWARE\VMware, Inc.\VMware VirtualCenter and searches for the HttpsProxyPort or HttpProxyPort attribute.
If the HttpsProxyPort attribute is found, DDM uses its value for the port and sets the prefix to HTTPS. If the HttpProxyPort attribute is found, DDM uses its value for the port and sets the prefix to HTTP.
Note: DDM performs a search for the WMI port once only. The retrieved value is cached so that the same query does not need to be run for each VMware Infrastructure Management (VIM) protocol entry.
Once the port is found, DDM generates the connection URL as follows: <prefix>://<ip_address>:<port>/sdk. DDM creates a VMware Infrastructure Client, passes the user name and password from the current VMware Infrastructure Management (VIM) protocol, passes the generated URL, and performs a connection. The connection is made using the version 2.5 protocol. If this connection fails, DDM tries to connect using the version 2.0 protocol.
If the connection is successful, DDM retrieves the product information and extracts the required values (these values are stored in the VMware VirtualCenter CI attributes). The values include build number, version, description, and so on. DDM uses the IP address to create a Host CI.
306
Chapter 28 VMware
DDM stores the generated URL used for this successful connection in the VirtualCenter CI's connection_url attribute. DDM stores the credentialsId of the current VIM protocol in the VirtualCenter CIs credentialsId attribute. If the connection is successful, DDM clears all errors and warnings that were generated in previous connection attempts and returns results. If the connection is unsuccessful, DDM continues with the next VIM protocol credentials entry, until all are tried. Output:
Troubleshooting:
Problem. The following error message is displayed when an operation cannot be performed due to lack of permissions:
User does not have required '<permission>' permission
Check that the user has permissions for all entities being discovered: In the VMware Infrastructure Client, access the Permissions tab of each entity (host, cluster, virtual machine, and so on). Verify that the user has been assigned at least a Read-Only role.
Note: You can view necessary permissions in the Discovery Job Details pane (Run Discovery > Details tab). For details, see Discovery Permissions Window in Discovery and Dependency Mapping Guide.
307
Chapter 28 VMware
Problem. The following error message is displayed when credentials are not correct:
Invalid user name or password
12 Discovery Workflow VMware VirtualCenter Topology by VIM

This job connects to vCenter or VirtualCenter Servers and discovers the full VMware Infrastructure topology. Trigger CI. WMI. Trigger TQL:
Node Conditions. None. Triggered CI Data:
credentialsId. The credentials ID of the VMware Infrastructure Management (VIM) protocol saved in the vCenter or VirtualCenter Servers attribute. server_url. The URL for connecting to VMware Infrastructure, taken from the vCenter or VirtualCenter Servers connection_url attribute. Discovery Pattern Parameters. reportPoweredOffVMs. Checks whether virtual machines that are powered off should be reported. Discovery and Dependency Mapping performs the following processes: a DDM extracts the connection URL and the VIM protocol credentials ID by using the VirtualCenter Trigger CI. DDM uses the credentials ID to retrieve the user name and password for the VIM protocol. DDM creates a VMware Infrastructure Client and connects to the server using these parameters. The connection is made using the version 2.5 protocol. If this connection fails, DDM tries to connect using the version 2.0 protocol. b DDM performs a query to retrieve information about Datacenters; the retrieved information is used to create Datacenter CIs.
308
Chapter 28 VMware
c DDM performs a query for the licensing information, including license availability and usage information, and information about license sources. The user used to retrieve availability information must have Global.Licenses permissions. If these permissions do not exist, DDM cannot add the licenses_total and licenses _available attributes for each License Feature CI, and a warning is reported. d For each Datacenter, DDM performs a query to retrieve ComputeResources data. ComputeResource can represent either a single ESX server or a cluster (in which case it is called ClusterComputeResource). DDM does not map the ComputeResource resource itself to any CI (it is considered an abstract element of the hierarchy) but does use its properties. e For each ComputeResource resource which is a ClusterComputeResource resource, DDM treats the resource as a cluster and creates a Cluster CI. DDM performs an additional query to retrieve its attributes. f For each ComputeResource resource, DDM performs queries to retrieve:
Information about its resource pools (the hierarchy of all the resource pools are retrieved in one query). Information about its ESX servers (all ESX servers are returned in one query; for a ComputeResource resource that is not a cluster, a single ESX is returned). Information about its VMs (all in one query).
g For each ESX server, DDM discovers its licensing information. For details, see step c on page 309. h When discovering VMs:
DDM retrieves the host key for the Network Node CI, representing the guest OS, which can be either the lowest MAC address or the IP address. To make this information available, the VM must have a VMware Tools component installed and running. If this component is not installed, DDM reports a warning and skips that VM. If the Tools component is installed, DDM tries to retrieve the host key. DDM searches for the lowest MAC address, or, if that is not available, for the IP. If that is also not available, DDM skips this VM and reports a warning.
309
Chapter 28 VMware
DDM determines the power status of the VM: If it is powered-off, the reportPoweredOffVms parameter determines whether DDM skips the machine or includes it in the results. (You may not want to report a powered-off VM because the information it containsfor example, the IP addressmay be outdated and may conflict with another VM that is powered-on. If reportPoweredOffVms is set to false, the powered-off VM is not reported. If reportPoweredOffVms is set to true, DDM tries to include the VM in the results (see the next step).
All discovered VMs undergo a filtering mechanism. Currently filtering is performed by host keys. If there are two machines with the same host key, DDM reports only one, as follows: If both machines are powered-on, DDM reports the first that is found. If both machines are powered-off, DDM reports the first that is found. If the machines have different power states, DDM reports the powered-on machine.
i All retrieved information is processed: DDM organizes the resource pools into a hierarchy and aligns each VM to its corresponding pool, then creates corresponding CIs and links, and returns the results.
310
Chapter 28 VMware
Output:
Troubleshooting:
Solution. Check that permissions are set as System.Read.
Problem. The following warning message is displayed and the CI is not reported:
Cannot determine the IP or MAC address of virtual machine '<vm_name>
311
Chapter 28 VMware
Problem. The following warning message is displayed, the status is <status> and the CI is not reported:
Virtual machine '<vm_name>' does not have a VMware Tools running
Problem. The following warning message is displayed when DDM cannot retrieve license availability (permissions, in most cases, is Global.Licenses):
User does not have required '<permission>' permission, features availability information won't be reported
Problem. The following warning message is displayed when DDM cannot retrieve the properties of clusters from VirtualCenter:
Failed to retrieve cluster properties, verify the connected user has sufficient permissions to query clusters information.
Solution. Users should have permissions for all clusters being discovered, and must have been assigned at least a Read-Only role.
13 Discovery Workflow VMware ESX Connection by VIM

This job discovers the connections to VMware ESX servers. Trigger CI. Unix. Trigger TQL and Node Conditions:
312
Chapter 28 VMware
Triggered CI Data. ip_address. The IP address is taken from the WMI agent CI. Discovery Pattern parameters. None. Discovery and Dependency Mapping performs the following procedure:

DDM checks the credentials for the VIM protocol. If the current credential includes a defined port, DDM uses this port. Otherwise, the port is not specified in the generated connection URL. The prefix is determined from the current credentials use SSL attribute.
DDM generates a connection URL: <prefix>://<ip_address>:<port>/sdk. DDM creates a VMware Infrastructure Client and connects using the generated URL and the user name and password from the credentials. The connection is made using the version 2.5 protocol. If this connection fails, DDM tries to connect using the version 2.0 protocol.
313
Chapter 28 VMware
If the connection is successful, DDM obtains the product details for the ESX server (version, build, and description), which will be used to populate the attributes of the Virtualization Layer Software CI. In addition, DDM retrieves the UUID and name of the ESX server. ESX UUID is stored in the host_key attribute of the VMware ESX Server CI, which is a key attribute.
DDM clears all errors or warnings and returns all discovered results. Otherwise, if the connection is unsuccessful, DDM tries the next VIM protocol credential, until all are tried. Output:
Troubleshooting and Limitations:
Solution. Check that permissions are set as System.Read.
Problem. The job completes with a time-out warning message:

<<Progress message, Severity: Error>> VMware VIM: Timeout trying to connect to remote agent, try increasing credential timeout value
Solution. You cannot set the connection timeout value for the job. The default 60 seconds timeout is always used.
314
Chapter 28 VMware
14 Discovery Workflow VMware ESX Topology by VIM

This job connects to ESX servers and discovers their topology. Trigger CI. Virtualization Layer Software. Trigger TQL and Node Conditions:
Triggered CI Data.
credentialsId. The credentials ID of the VMware Infrastructure (VIM) protocol, saved in the ESX server attribute. server_url. The URL for connection, taken from the ESX server connection_url attribute. Discovery Pattern Parameters. reportPoweredOffVMs. Checks whether VMs that are powered off should be reported. Discovery and Dependency Mapping performs the following procedure:
DDM uses the connection URL (extracted from the ESX server attribute) and the user name and password (obtained by the credentialsId Trigger CI from the ESX server attribute) to connect to the server. The connection is made using the version 2.5 protocol. If this connection fails, DDM tries to connect using the version 2.0 protocol.
DDM performs discovery of the ESX servers. DDM uses the same objects as the VMware VirtualCenter Topology by VIM job, so the flow is identical. (For details, see Discovery Workflow VMware VirtualCenter Topology by VIM on page 308.)
315
Chapter 28 VMware
DDM discovers:

All resource pools of the server All virtual machines of the server
DDM performs discovery of the licensing information (as in the VMware VirtualCenter Topology by VIM job). DDM processes and returns results. Output:
Troubleshooting for VMware ESX Topology by VIM:
Check that permissions are set as System.Read.
316
Chapter 28 VMware
Problem. The following warning message is displayed and the CI is not reported:
Cannot determine the IP or MAC address of virtual machine '<vm_name>
Problem. The following warning message is displayed, the status is <status> and the CI is not reported:
Virtual machine '<vm_name>' does not have a VMware Tools running
Problem. The following warning message is displayed when DDM cannot retrieve license availability (permissions, in most cases, is Global.Licenses):
User does not have required '<permission>' permission, features availability information won't be reported
317
Chapter 28 VMware
15 Virtual Topology Map
318
Chapter 28 VMware
16 Licensing Topology Map
Problem. The following error message is displayed:

Required class %s not found. Verify VMware SDK jar files (vim.jar, vim25.jar) are present in '<PROBE>\\root\\ext\\vmware' folder.
Cause. The SDK *.jar files are not copied to the Probe. Solution. Copy the *.jar files to the Probe, as described in Prerequisites Add *.jar Files on page 301.
Problem. The following error message is displayed:

User does not have required 'System.Read' permission
Cause. There is a lack of permissions from the user account when DDM connects to the ESX servers VirtualCenter.
319
Chapter 28 VMware
Solution.
Verify that credentials are defined for the VMware Infrastructure Management (VIM) protocol in the proper priority, so that credentials with full permissions have a lower index number than credentials with less permissions. For details, see Index in Discovery and Dependency Mapping Guide. If DDM previously discovered connections using credentials with less than full permissions, you must rerun the connection job (either VMware VirtualCenter Connection by WMI and VIM or VMware ESX Connection by VIM) to update the credentials ID attribute of VirtualCenter or ESX server, and then run the topology job (VMware VirtualCenter Topology by VIM or VMware ESX Topology by VIM).
Currently if VMware Tools are not running on a virtual machine, it is not possible to get its IP or MAC address; such virtual machines are ignored and are not reported to HP Universal CMDB. DDM can discover the total number of licenses and available licenses for each feature, but only when the user has Global.Licenses permission. If the user does not have such permissions, these attributes of the License Feature CI are not populated. Different versions of ESX Servers (versions 3.0 and 3.5) report the feature_is_edition flag differently for the esxFull feature: for the older version it is reported as false and for the newer version it is reported as true. Because of this discrepancy, DDM does not report this attribute. Different versions of ESX Servers (versions 3.0 and 3.5) report the total or available license counts differently for ESX-specific features (nas, iscsi, vsmp, san) that are included in the esxFull edition license. For these features, DDM does not report these attributes. There is a difference between VMware protocols 2.5 and earlier: certain attributes appear only in version 2.5 and do not appear in previous versions. As a result, when using an old protocol certain attributes are not discovered, especially for clusters and licenses.
320
Chapter 28 VMware
Discover VMware VMotion

VMware VMotion technology moves an entire running virtual machine instantaneously from one server to another. The VMware VirtualCenter server exposes a management interface that can be used by DDM to:
Connect to VirtualCenter using the VIM protocol, to discover its topology (Datacenters, Clusters, ESX Servers, Resource Pools, Virtual Machines, and so on). Connect to ESX Server and discover its full topology. This discovery is limited to the server itself. Listen for events that occur in the inventory structure. VMware provides an SDK describing this interface, which includes documentation, API reference, libraries, and examples. VMware Infrastructure SDK can be downloaded from http://www.vmware.com/support/developer/vc-sdk/. This task includes the following steps:
Supported VMware servers on page 322 Prerequisites on page 322 Discovery Workflow on page 322 DDM Package on page 322 Trigger CI on page 323 Trigger TQL on page 323 Triggered CI Data on page 323 Discovered CITs on page 323 Troubleshooting and Limitations on page 324
321
Chapter 28 VMware
1 Supported VMware servers
VI API 2.5 is supported by ESX Server 3.5, VirtualCenter Server 2.5, and ESX Server 3i (they can also be connected using protocol 2.0). VI API 2.0 is supported by ESX Server 3.0.x, VirtualCenter Server 2.0.x, ESX Server 3.5, VirtualCenter Server 2.5, and ESX Server 3i (protocol 2.5 is not supported).
2 Prerequisites
a To connect to any server using the VIM protocol, prepare the following:

A connection URL, for example, https://vcserver/sdk. Credentials (user name and password). A user account must be created for you on the VMware server.
For details on the protocol, see VMware Infrastructure Management (VIM) Protocol in Discovery and Dependency Mapping Guide. b Permissions. VMotion event-driven discovery requires special permissions for the protocol used:
System.Read permissions for the user performing the login, for all DDM actions. The user must be a member of the Read-Only user group.
c Discover the VMware inventory structure. For details, see Discover VMware Infrastructure Topology on page 299.
Activate the VMware VMotion Monitor by VIM job. The job includes the VMware_VMotion_discovery_by_VIM pattern that listens for virtual machine migration events collected by the VirtualCenter server.
4 DDM Package
To access the VMWare package: Settings > Package Manager. For details, see Package Manager in Model Management. For details on the contents of the package, click the link to the Readme file.
322
Chapter 28 VMware
5 Trigger CI
VMware VirtualCenter
6 Trigger TQL
7 Triggered CI Data
Name credentialsId Value ${SOURCE.credentials_id} Description The credentials ID of the VIM protocol saved in the VirtualCenter attribute. The IP address, taken from the VirtualCenter application_ip. The URL for connection, taken from the VirtualCenter connection_url attribute.
ip_address
server_url
${SOURCE.application_ip} ${SOURCE.connection_url}
8 Discovered CITs

Contained Container Link Host Hypervisor IP Run
323
Chapter 28 VMware
connectionRetryNumber. The maximum number of times that DDM attempts to restore the connection. The default is 0 (zero), that is, the number of attempts is unlimited. eventBasedDiscoveryEnabled. If this parameter is set to true (the default), every time the job is activated, it stays connected to the destination machine listening for VMotion events, until the job is stopped. historyHours. The period within which DDM checks for untracked VMotion events. DDM calculates the period from when the job is activated going backwards in time. The default value is 24 hours.
Currently you can stop the job only by restarting the Probe server.
324
Part X
The Web Server Modules
326
29
Apache Tomcat
This chapter describes how DDM discovers the Apache Tomcat application. This chapter includes: Concepts

Concepts
Discover Apache Tomcat on page 329 Discover Bugzilla, Wordpress, and MediaWiki on page 333
327
Chapter 29 Apache Tomcat
Overview
To discover Apache Tomcat, DDM parses the following configuration files:
server.xml. This is the main Apache Tomcat configuration file that describes the components of the Tomcat installation, its architecture, and its topology. The file also contains the configuration for global resources. The following script fragment appears in the server.xml file and is the part used by the Apache Tomcat by Shell job to retrieve information for building the CIs:
<Server port="8505" shutdown="SHUTDOWN"> <GlobalNamingResources> <Resource name="jdbc/GlobalDS" type="javax.sql.DataSource" driverClassName="com.inet.ora.OraDriver" url="jdbc:inetora:labm3mam13:1521:UCMDB" maxActive="20" /> </GlobalNamingResources> <Service name="Catalina"> <Connector port="8580" protocol="HTTP/1.1"/> <Connector port="8509" protocol="AJP/1.3" /> <Engine name="Catalina"> <Host name="localhost" appBase="webapps"> <Cluster"> <Membership mcastAddr="228.0.0.4" mcastPort="45564"/> </Cluster> </Host> <Host name="grabinovic01" appBase="genadiwebapps"> <Membership mcastAddr="228.0.0.4" mcastPort="45564"/> </Cluster> </Host> </Engine> </Service> </Server>
context.xml. This file defines the application context configuration. Each installed application has a unique URL prefix. This file contains resource configurations for different scopes, depending on the file location. web.xml. This file defines the application configuration, for example, the application display name and the servlets used to process HTTP requests. Currently, DDM uses this file to retrieve the application display name.
Tasks
328
Discover Apache Tomcat

This task describes how to discover the Apache Tomcat application. This task includes the following steps:

Supported Versions on page 329 Network and Protocols on page 329 Discovery Workflow on page 329 Apache Tomcat CITs on page 330 Apache Tomcat Links on page 330 Input TQL on page 331 Triggered CI Data on page 331 Topology View on page 332
Apache Tomcat versions 4.x, 5.x, and 6.x. DDM discovers Tomcat running on the following operating systems: Windows, UNIX, Linux.

Set up the following credentials:
a Run the Range IPs by ICMP job (in the Network Basic module) to discover IPs in the range where Tomcat is running.
329
b Run the Host Connection by Shell job (in the Network Basic module) to discover Shell agents. c Run the Host Resources and Applications by Shell job (in the Network Host Resources and Applications module) to verify that an Apache Tomcat is running on the system, and to discover Tomcat-specific processes. If these processes are discovered, the job creates Tomcat CIs. The job searches for the java.exe (or java) process name, then searches in the command line for either the -Dcatalina.home= or -Dcatalina.base= substring. This substring includes the path to the Tomcat home directory. If this substring is not found, the job searches for a process name starting with tomcat and from there acquires the path to the home directory. The job then finds the absolute path to the Tomcat configuration file and adds this path as an attribute (webserver_configfile) to the Tomcat CI. d Run the Apache Tomcat by Shell job. This job uses the Tomcat Trigger CI attribute to locate the configuration files that are discovered by the Host Resources and Applications by Shell job.
4 Apache Tomcat CITs
5 Apache Tomcat Links

Tomcat Service > USE > Service Address Tomcat Service > Container > Web Server Virtual Host
330

Web Application > USE > JDBC Data Source Tomcat > Container > Configuration File Tomcat > Container > Tomcat Service Tomcat Cluster > Member > Web Server Virtual Host Web Server Virtual Host > Container > Web Application Tomcat > Container > JDBC Data Source JDBC Data Source > Depend > Database
6 Input TQL
7 Triggered CI Data
331
8 Topology View
332
Discover Bugzilla, Wordpress, and MediaWiki

The following Web-based applications are discovered as part of the Apache and IIS discovery jobs. The following versions are supported:
Application Bugzilla Helpzilla MediaWiki Wordpress Supported Version 3.x 0.x 1.15.x 2.5.x
To activate discovery: 1 Run the Host Connection by Shell job to create Shell CITs. 2 Run any of the Host Resources and Applications jobs to gather information about processes running on the host. 3 Run the WebServer by Shell job to retrieve information about Apache and available Web applications deployed on the Apache server. The Web Application CIT:

ID. webapplication Parent CIT. application Usage of the existing attribute. name New attribute. type (the type of application, for example, blog engine, wiki)
333
334
30
Microsoft Internet Information Services (IIS)
Discover Microsoft Internet Information Services (IIS) Previous Topology on page 335 Discover Microsoft Internet Information Services (IIS) Current Topology on page 339
Tasks
Discover Microsoft Internet Information Services (IIS) Previous Topology

This task describes how to discover Internet Information Services (IIS). IIS is a set of Internet-based services for servers created by Microsoft for use with Microsoft Windows. This task includes the following steps:

Supported Versions on page 336 Network and Protocols on page 336 Discovery Workflow on page 336 Discovered CITs on page 336 Topology Map on page 338 Troubleshooting and Limitations on page 338
335
Chapter 30 Microsoft Internet Information Services (IIS)
IIS versions 5 and 6.

NTCmd. For credentials information, see NTCMD Protocol in Discovery and Dependency Mapping Guide.Verify that the target machine running IIS lies in the Probe range.
In the Run Discovery window, activate the jobs in the following order:
WebServices by URL. For a limitation, see Troubleshooting and Limitations on page 338. IIS Applications by NTCMD
4 Discovered CITs
336
The dependency list for the IIS Web Site node is defined as follows:
For details, see Subgraph Condition Definition Dialog Box in Model Management.
337
5 Topology Map

When activating the WebServices by URL job, the Web services being discovered should be authentication-less, that is, they can be accessed without credentials (user name/password).
338
Discover Microsoft Internet Information Services (IIS) Current Topology

This task describes how to discover Microsoft Internet Information Services (IIS). This task includes the following steps:

Supported Versions on page 339 Prerequisites on page 340 Network and Protocols on page 340 Discovery Workflow on page 340 Trigger TQL on page 341 Triggered CI Data on page 341 Parameters on page 341 Discovered CITs on page 342 IIS Package on page 342 Permissions on page 343 Topology Map on page 344 Troubleshooting and Limitations on page 344
IIS version 7.0 or earlier.
339
2 Prerequisites
To retrieve all relevant information, DDM should be able to execute Visual Basic scripts and have write permission to the %SytemRoot%/system32 /drivers/etc folder. Verify that the target machine running IIS lies in the Probe range.

NTCmd. For credentials information, see NTCMD Protocol in Discovery and Dependency Mapping Guide.
In the Run Discovery window, activate the jobs in the following order: a Run the Host Connection by Shell job to create Shell CITs. b Run the Host Resources and Applications by Shell job to discover IIS Web Server CIs and IIS Application Pool CIs with corresponding Depend links to the managing process. c Run the IIS Applications by NTCMD job to discover the detailed topology of IIS. After the connection is made, DDM copies the adsutil.vbs script on the remote machine. DDM retrieves IIS topology information from the output of this tool. Microsoft IIS version 7.0 enables you to create an IIS application from a Web directory, as well as from a virtual directory (as in prior versions). Therefore, when DDM discovers such an application, DDM creates an IIS Web Directory CI. To view required permissions: Run Discovery > Advanced Mode > Web Servers IIS > IIS Applications by NTCMD job. Details tab > Discovery Job Details pane. Click the View Permissions button. For details, see Permissions on page 343.
340
Note: The IIS Web Dir CI is created only if there is an IIS Virtual Dir CI or a web.config file underneath in the topology, otherwise it is not reported.
5 Trigger TQL
6 Triggered CI Data
7 Parameters
341
adsutil_path. Enter the path and name to the adsutil.vbs script. The adsutil.vbs script is a free script provided by Microsoft for IIS management tasks. do_web_service. true: The IIS Web Service CI is reported. Note that report_legacy_topology must also be set to true for DDM to report this CI. report_legacy_topology. true: For backwards compatibility, DDM continues, by default, to report the legacy IIS topology.
8 Discovered CITs
9 IIS Package
All components responsible for IIS discovery by Shell are bundled in the IIS package (in the Web Tier category).
342
10 Permissions
343
11 Topology Map
12 Bugzilla, Wordpress, and MediaWiki Discovery

For details see Discover Bugzilla, Wordpress, and MediaWiki on page 333.

An IIS Web server CI is created even if no Web service is running on the machine but the IIS FTP and IIS SMTP services are present.
344
Index
A
Active Directory discover 25 discover domain controllers, topology 26 Active Directory Connection by LDAP job 28 Active Directory Topology by LDAP job 29 adsutil.vbs 19 Alteon application switch by SNMP job 289 Apache Tomcat by Shell job 21, 328, 330 Application SAP Solution Manager module 58 architecture 149 discovery credential-less 271 IBM DB2 Server 83 IIS 335 JBoss 215 JBoss by Shell 215 Layer 2 251 load balancers 287 Microsoft Cluster Server 75 Microsoft Exchange Server 2007 39 Microsoft SQL Server 87 network - basic 249 Oracle 103 SAP 51 SAP Solution Manager 58 Siebel 61 Solaris zones 279 Veritas Cluster Server 77 VMware 299 WebLogic 221 WebLogic by Shell 223 WebSphere 227 WebSphere by Shell 227 Discovery Tools 119 diskinfo.exe 20 DNS Zone by Nslookup job 268
B
Bugzilla, Wordpress, MediaWiki 333
C
Cisco CSS by SNMP job 290 Class C IPs by ICMP job 63 credential-less discovery 271 CSV data importing from external source 138
D
Databases TCP Ports job 84, 88 DB2 Connection by SQL job 84 DB2 Topology by SQL job 84 DDM modules changes in 8.01 245 DDM Probe copying files to a remote Windows machine 18
E
ECC 191 discovering storage topology 193 overview 192 SQL queries for job 199 ECC Integration by SQL job 196 EMC Control Center overview 192
345
Index EMC Control Center integration 191 discovering storage topology 193 SQL queries for job 199 Exchange_Server_2007_Discovery.ps1 21 external sources importing data from 121 importing data, troubleshooting 142 Host Resources and Applications by WMI job 91, 241, 244, 280 Host Resources and Applications module 235
I
IBM DB2 Server discovery 83 IHS Websphere Plugin by Shell job 21 IIS discovery 335 IIS Applications by NTCMD job 19, 21, 336, 340 import data from external sources 125 Import from CSV File job 124, 125 Import from Database job 124 Import from Properties file job 124 importing data from external sources 121 troubleshooting 142 installed software reverting to previous discovery method 244 integrations with ECC 193 IP Traffic by Network Data job 283
F
F5 BIG-IP LTM by SNMP job 289 File Monitor by Shell job 21 F-Secure running on Windows for Host Connection by Shell job 250
G
general information 17 GetFileModificationDate.vbs 21 getfilever.vbs 19
H
Host Connection by Shell job 18, 40, 53, 95, 280, 330, 340 Windows running F-Secure 250 Host Connection by Shell/WMI/SNMP job in ECC 195 Host Connection by SNMP job 280, 289 Host Connection by WMI job 35, 63, 280 Host Fingerprint using nmap job 271 Host Networking By SNMP job 253 host resources and application dependency, overview 235 and applications discovery 235 troubleshooting and limitations 248 workflow 237 Host Resources and Applications by Shell job 18, 19, 40, 53, 57, 91, 235, 241, 280, 330, 340 Host Resources and Applications by Shell/WMI/SNMP job in ECC 195 Host Resources and Applications by SNMP job 241, 280 346
J
J2EE JBoss by Shell job 216 J2EE WebLogic by Shell job 224 J2EE Weblogic by Shell job 21 J2EE WebSphere by Shell job 21, 229 J2EE WebSphere by Shell or JMX job 21 JBoss discovery 215 discovery by Shell 215 jobs Alteon application switch by SNMP 289 Apache Tomcat by Shell 328, 330 Cisco CSS by SNMP 290 Class C IPs by ICMP 63 Databases TCP Ports 84, 88 DB2 Connection by SQL 84 DB2 Topology by SQL 84
Index DNS Zone by Nslookup 268 F5 BIG-IP LTM by SNMP 289 Host Connection by Shell 40, 53, 95, 280, 330, 340 Host Connection by SNMP 280, 289 Host Connection by WMI 35, 63, 280 Host Fingerprint using nmap 271 Host Networking By SNMP 253 Host Resources and Applications by Shell 40, 53, 57, 91, 235, 241, 280, 330, 340 Host Resources and Applications by SNMP 241, 280 Host Resources and Applications by WMI 91, 241, 280 IIS Applications by NTCMD 336, 340 Import from CSV File 124, 125 Import from Database 124 Import from Properties 124 IP Traffic by Network Data 283 J2EE JBoss by Shell 216 J2EE WebLogic by Shell 224 J2EE WebSphere by Shell 229 Layer2 Topology Bridge based by SNMP 257 Layer2 Topology VLAN based by SNMP 261 Microsoft Exchange Connection by NTCMD 40 Microsoft Exchange Connection by WMI 33, 35, 37 Microsoft Exchange Topology by NTCMD 41 Microsoft Exchange Topology by WMI 33, 35, 37 MS Cluster by NTCMD 76 MSSQL Connection by SQL 88 MSSQL Topology by SQL 88 MySQL by Shell 93, 95 Oracle Listeners by Shell 108 Oracle RAC Topology by Shell 108 Potential Servers by Network Data 284 Range IPs by ICMP 53, 280, 329 SAP ABAP Connection by JCO 58 SAP ABAP Connection by SAP JCO 54 SAP ABAP Topology by SAP JCO 54 SAP Applications by SAP JCO 54 SAP ITS by NTCMD 54 SAP Java Topology by SAP JMX 57 SAP Solution Manager by SAP JCO 54 SAP Solution Manager Topology by SAP JCO 58 SAP System by Shell 53, 57, 59 SAP TCP Ports 59 SE Integration by SQL 174 Server Ports by Network Data 283 Servers by Network Data 282 Siebel DB by TTY 63, 67 Siebel DB by WMI and NTCMD 63 Siebel Web Applications by NTCMD 63 Siebel Web Applications by TTY 63 Software Element CF by Shell 241 TCP Ports 63 Veritas Cluster by Shell 78 VLAN ports by SNMP 255 VLANS by SNMP 254 VMware ESX Connection by VIM 304 VMware ESX Topology by VIM 304 VMware VirtualCenter Connection by WMI and VIM 304 VMware VirtualCenter Topology by VIM 304 WebServer Detection using TCP Ports 54, 63 WebServices by URL 336 junction.exe 22
L
Layer 2 discovery 251 Layer2 Topology Bridge based by SNMP job 257 Layer2 Topology VLAN based by SNMP job 261 load balancers discovery 287
M
meminfo.exe 20
347
Index Microsoft Cluster Server discovery 75 Microsoft Exchange Connection by NTCMD job 21, 40 Microsoft Exchange Connection by WMI job 33, 35, 37 Microsoft Exchange Server discover 34 discover topology with Active Directory 43 overview 25, 33 Microsoft Exchange Server 2007 discovery 39 package 41, 47 Microsoft Exchange Topology by LDAP job 46 Microsoft Exchange Topology by NTCMD job 21, 41 Microsoft Exchange Topology by WMI job 33, 35, 37 Microsoft Internet Information Services (IIS) 335 Microsoft SQL Server discovery 87 MS Cluster by NTCMD job 76 MSSQL Connection by SQL job 88 MSSQL Topology by SQL job 88 MySQL by Shell job 93, 95 Oracle Listeners by Shell job 108 Oracle RAC Topology by Shell job 108 Oracle TNSName by Shell job 21 OS credentials discovery for MS SQL Server 87
P
Potential Servers by Network Data job 284 processlist.exe 20
R
Range IPs by ICMP job 53, 280, 329 in ECC 195 reg_mam.exe 19
S
SAP discover ABAP 52 discover Java 56 discovery 51 SAP ABAP Connection by JCO job 58 SAP ABAP Connection by SAP JCO job 54 SAP ABAP Topology by SAP JCO job 54 SAP Applications by SAP JCO job 54 SAP ITS by NTCMD job 54 SAP Java Topology by SAP JMX job 57 SAP Profiles by Shell job 21 SAP Solution Manager discovery 58 SAP Solution Manager by SAP JCO job 54 SAP Solution Manager Topology by SAP JCO job 58 SAP System By Shell job 21 SAP System by Shell job 53, 57, 59 SAP TCP Ports job 59 SE Integration by SQL job 174 Server Ports by Network Data job 283 Servers by Network Data job 282 Service Guard Cluster Topology by TTY job 21 Siebel discovery 61 Siebel Application Server Configuration job 21
N
network - basic 249 NNMi integration 147 change management and impact analysis 162, 163 connection protocol parameters 163, 167 overview 148 run 151 troubleshooting and limitations 168 NNMi-UCMDB Integration 159
O
Oracle discovery 103
348
Index Siebel DB by TTY job 63, 67 Siebel DB by WMI and NTCMD job 63 Siebel Web Applications by NTCMD job 63 Siebel Web Applications by TTY job 63 software reverting to previous discovery method 244 Software Element CF by Shell job 22, 241 Solaris zones discovery 279 SQL Server shallow discovery 90 shallow discovery overview 90, 93, 328 Storage Essentials (SE) integration with Universal CMDB 172
W
WebLogic discovery 221 discovery by Shell 223 Webserver by Shell job 22 WebServer Detection using TCP Ports job 54, 63 WebServices by URL job 336 WebSphere discovery 227 discovery by Shell 227 troubleshooting and limitations 231
X
xCmdSvc.exe connecting to remote Windows machine 18
T
TCP Ports job 63 TempWmicBatchFile.bat empty file created 18
U
UDDI discover processes 69
V
Veritas Cluster by Shell job 22, 78 Veritas Cluster Server discovery 77 VLAN ports by SNMP job 255 VLANS by SNMP job 254 VMware discovery 299 VMware ESX Connection by VIM job 304 VMware ESX Topology by VIM job 304 VMware VirtualCenter Connection by WMI and VIM job 304 VMware VirtualCenter Topology by VIM job 304 VMware VMotion discover 321 VMware VMotion Monitor by VIM job 322
349
Index
350

Ucmdb8.01 DDM Cp5

Uploaded by

Copyright:

Available Formats

Ucmdb8.01 DDM Cp5

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ucmdb8.01 DDM Cp5

Uploaded by

Copyright:

Available Formats

HP Universal CMDB

Discovery and Dependency Mapping Content Guide

Welcome to This Guide

How This Guide Is Organized

The Application Modules

The Cluster Modules

Welcome to This Guide

The Database Modules

Part VII The J2EE Modules

Part VIII The Network Modules

The Virtual Machines Module

The Web Server Modules

Welcome to This Guide

Who Should Read This Guide

Getting More Information

Welcome to This Guide

Delete Files Copied to Remote Machine on page 17 Reference

Files Copied to a Remote Machine on page 18

Delete Files Copied to Remote Machine

Chapter 1 General Information for Discovery and Dependency Mapping Content

2 Enter one of the following:

Files Copied to a Remote Machine

This section includes the following topics:

Chapter 1 General Information for Discovery and Dependency Mapping Content

processlist.exe on page 20 Exchange_Server_2007_Discovery.ps1 on page 21 GetFileModificationDate.vbs on page 21 junction.exe on page 22

Chapter 1 General Information for Discovery and Dependency Mapping Content

Chapter 1 General Information for Discovery and Dependency Mapping Content

Microsoft Exchange Connection by NTCMD Microsoft Exchange Topology by NTCMD

Content Pack Version: CP4

Chapter 1 General Information for Discovery and Dependency Mapping Content

Software Element CF by Shell Veritas Cluster by Shell Webserver by Shell

Content Pack Version: CP5

Note: This junction point is automatically removed once discovery is complete.

Relevant DDM Jobs:

Content Pack Version: CP5

This chapter includes: Concepts

Overview on page 25 Tasks

Discover Active Directory Domain Controllers and Topology on page 26

Chapter 2 Active Directory

Discover Active Directory Domain Controllers and Topology

Windows Server 2000 Windows Server 2003 Windows Server 2008

Host Connection by Shell Host Connection by SNMP Host Connection by WMI

Chapter 2 Active Directory

TCP Ports This job includes the TCP_NET_Dis_Port pattern.

3 Network and Protocols

Chapter 2 Active Directory

4 Discover AD Domain Controllers

Chapter 2 Active Directory

DomainController Container link

Chapter 2 Active Directory

Name Equal ignore case "ldap"

Discovery Pattern Parameters

Chapter 2 Active Directory

Chapter 2 Active Directory

6 Active Directory Topology

7 Troubleshooting and Limitations

Overview on page 33 Tasks

Microsoft Exchange connection by WMI Microsoft Exchange topology by WMI

Chapter 3 Microsoft Exchange