SAP Solution Manager 7.

1 SP01

Outside Discovery
User Guide
Troubleshooting Guide
Version 1.0 - February 2011

OUTSIDE DISCOVERY
USER GUIDE

Typographic Conventions

Icons

Type Style

Icon

Example
Text

Represents

Meaning

Words or characters quoted

from the screen. These
include field names, screen
titles, pushbuttons labels,
menu names, menu paths,
and menu options.

Caution

Cross-references to
documentation.

Recommendation

other

Example
text

Emphasized
words
or
phrases in body text, graphic
titles, and table titles.

EXAMPLE
TEXT

Technical names of system

objects. These include report
names, program names,
transaction codes, table
names, and key concepts of
a programming language
when they are surrounded
by body text, for example,
SELECT and INCLUDE.

Example
text

Output on the screen. This

includes file and directory
names and their paths,
messages,
names
of
variables and parameters,
source text, and names of
installation, upgrade and
database tools.

Example
text

Exact user entry. These are

words or characters that you
enter in the system exactly
as they appear in the
documentation.

<Example
text>

Variable user entry. Angle

brackets indicate that you
replace these words and
characters with appropriate
entries to make entries in the
system.

EXAMPLE
TEXT

Keys on the keyboard, for

example, F2 or ENTER.

Example
Note

Syntax

OUTSIDE DISCOVERY
USER GUIDE

Contents
1

Overview .............................................................................................................................................. 5

Pre-requisites ...................................................................................................................................... 6
2.1

2.1.1

SAPHostAgent Version ............................................................................................................ 6

2.1.2

SAPHostAgent Porttype ........................................................................................................... 7

2.1.3

SAPHostAgent Trusted Connection ......................................................................................... 8

2.2
3

SAPHostAgent............................................................................................................................... 6

Diagnostics Agent......................................................................................................................... 8

User Guide ........................................................................................................................................... 9

3.1

Host Discovery .............................................................................................................................. 9

3.1.1

Landscape Browser / Technical System Editor View ................................................................ 9

3.1.2

Host Discovery Process Status .............................................................................................. 11

3.1.3

Physical Host Data ................................................................................................................. 11

3.1.4

Logical Host Data ................................................................................................................... 12

3.2

Database Discovery .................................................................................................................... 13

3.2.1
3.3

Microsoft IIS Discovery ............................................................................................................... 14

3.3.1
4

Landscape Browser ............................................................................................................... 13

Landscape Browser / Technical System Editor View .............................................................. 14

Advanced Configuration ................................................................................................................... 16

4.1

Switching On/Off Outside Discovery ......................................................................................... 16

4.2

Internal Cache ............................................................................................................................. 16

4.3

Force Push Flag .......................................................................................................................... 17

4.4

Jobs scheduling .......................................................................................................................... 17

4.5

Customizing Physical Host FQDN and IP address ................................................................... 18

Support Tools .................................................................................................................................... 19

5.1

Landscape browser..................................................................................................................... 19

5.1.1

Landscape Tab

5.1.2

Administration Tab

5.2

Hosts View ............................................................................................... 19

Logs and Traces View ......................................................................... 19

Diagnostics Agent Administration ............................................................................................. 21

5.2.1

Agent Error Monitoring Tab .................................................................................................... 21

Outside Discovery
User Guide SolMan 7.1 SP01

5.2.2
5.3

Agent Log Viewer ................................................................................................................... 21

Diagnostics Agent Support ........................................................................................................ 23

5.3.1

SMD Server Analysis View..................................................................................................... 23

5.3.2

Diagnostics Agent Runtime View ........................................................................................... 24

Troubleshooting Guide ..................................................................................................................... 25

6.1

Troubleshooting Roadmap ......................................................................................................... 25

6.2

Common Issues .......................................................................................................................... 26

6.2.1

Diagnostics agent is not connected to solution manager server ............................................. 26

6.2.2
An exception occurred during the execution of the function
'FM_DIAGLS_PUSH_PHYSICAL_HOST' ............................................................................................ 26

6.2.3

Exception while parsing SapOsCol DataNo data allowed here ........................................... 27

6.2.4

Exception while parsing SapOsCol DataParsing an empty source ..................................... 27

6.2.5

Failed to open HW file ............................................................................................................ 27

6.2.6

CIM Request EnumerateInstances for classes Application failed: : Provider load failure .... 28

6.2.7

GetObject ADSi Object IIS://localhost/W3SVC failed: Error : Access is denied ...................... 28

6.2.8

java.net.SocketTimeoutException: Read timed out ................................................................ 28

6.2.9

Timeout waiting for saposcol answer...................................................................................... 29

6.2.10

Error to perform http request cause Socket output stream shutdown by peer .................... 29

6.2.11

Unable to open connection to host "localhost:1128". The host is down or unavailable ........... 29

6.2.12

Cannot established a trusted connection to SAP host agent webservice ................................ 29

6.2.13

Webservice port type not enabled .......................................................................................... 30

6.2.14

Webservice invocation error occurred Generic error .......................................................... 30

Technical Implementation ................................................................................................................. 31

7.1

Host Discovery ............................................................................................................................ 31

7.1.1

Physical host .......................................................................................................................... 31

7.1.2

Operating System .................................................................................................................. 31

7.1.3

Virtualization Information ........................................................................................................ 32

7.1.4

Logical hosts .......................................................................................................................... 32

7.2

Database Discovery .................................................................................................................... 33

7.2.1

Installed Database List ........................................................................................................... 33

7.2.2

Database Properties .............................................................................................................. 33

7.3

IIS Discovery ............................................................................................................................... 34

7.3.1

Identifying IIS instance ........................................................................................................... 34

7.3.2

Installed .Net Version ............................................................................................................. 34

7.3.3

Discovering IIS Version 7.x .................................................................................................... 35

7.3.4

Discovering IIS Version 6.x .................................................................................................... 36

SAP AG 2008

Outside Discovery
User Guide SolMan 7.1 SP01

Overview

The purpose of the Outside Discovery is to automatically discover, collect and send information related the monitored
system to Solution Manager.
As of Solution Manager 7.1 SP01, Outside Discovery is able to collect following information:
Host: data related to Physical Host and Virtual Host (like Operating System type, version, cpu, memory
)
Database: data related to installed database (like database type, version, )
Microsoft Internet Information Service: data related to installed instance of Microsoft IIS (like .Net
version, IIS Applications, IIS Sites)
The Outside Discovery is packaged inside the Diagnostics Agent within the Agelet called DCC (agelet archive:
sap.com~tc~smd~agent~application~e2edcc.ear).
The Outside Discovery process relies on the SAPHostAgent Web Service process for collecting all raw technical
data related to monitored system.
The process is ready to push as soon as the running Diagnostics Agent gets connected to a Solution Manager
system. Data are:
o Collected from the SAPHostAgent Web Service.
o Filtered and cached on Agelet side.
o Sent to JAVA Bean Controller (SMD_DataEnrichment_Registrator) through P4 Connection.
o Stored in LMDB database (AI_DIAGSNOTICS_DATA_ENRICHMENT package).

SAP AG 2008

Outside Discovery
User Guide SolMan 7.1 SP01

Pre-requisites

Even if the Outside Discovery process itself do not require any specific setup in order to run some pre-requisites are
necessary.
Pre-requisites for the SAPHostAgent and Diagnostic Agent are detailed in the Solution Manager Guided Procedure:
SAP Solution Manager Configuration

System Preparation

Step 6.3: Prepare Outside Discovery

Implementation Guides (IMG) are available in Solution Manager.

Topic

IMG ID

Diagnostics Agent Installation Guide

SMCONF_LSC_DIAGAGT (SIMG)

SAP Host Agent Installation Guide

SMCONF_LSC_HOSTAGT (SIMG)

SAP Host Agent Trusted Connection

SMCONF_LSC_CREDENT (SIMG)

2.1

SAPHostAgent

All data discovered by the Outside Discovery process are collected from the SAPHostAgent installed on the physical
host.

2.1.1

SAPHostAgent Version

The SAPHostAgent should have the correct version the minimum required version is:
Version field

Required version

Kernel Version

720

Patch Number

54

How to check the version of SAPHostAgent:

Using Self-Check Application:
A specific self-check for the SAPHostAgent version is implemented in within the Self-Check Framework. This
check verify that the current SAPHostAgent Patch Number is higher than the required Path Number defined in
following configuration:

SAP AG 2008

Outside Discovery
User Guide SolMan 7.1 SP01

Using Operating System command:

o

Open directory where SAPHostAgent is installed (example: on Windows system C:\Program

Files\SAP\hostctrl\exe).

Run following shell command:

saphostctrl.exe -function ExecuteOperation -name versioninfo

2.1.2

Here is the output from the above command:

SAPHostAgent Porttype

The SAPHostAgent provides a Web Service access to some sub-services also called Porttype. The SAPHostAgent
should be configured in order expose those Porttype to the Web Service.
The configuration of those available services is defined in the following file host_profile located under of the binary
directory of the SAPHostAgent.
Following porttypes are mandatory for the Outside Discovery process:
o

SAPHostControl

SAPOscol

Example of host_profile file on Windows system:

SAP AG 2008

Outside Discovery
User Guide SolMan 7.1 SP01

2.1.3

SAPHostAgent Trusted Connection

Some methods within the SAPHostAgent are restricted. In order to allow the Diagnostics Agent to access protected
Web Service from the SAPHostAgent a trusted connection is necessary between the 2 parties.
Trusted connection is defined in the following file host_profile.
The Diagnostics Agent user should be entered in the specific field service/admin_users.

Example of host_profile file on Windows system:

2.2

Diagnostics Agent

In order to start the Outside Discovery process, the Diagnostics Agent should be connected to the Solution Manager
System:
o

Either during the Diagnostics Agent installation procedure.

Either using the following step in the System Preparation Guided Procedure:
SAP Solution Manager Configuration

SAP AG 2008

System Preparation

Step 6.4: Connect Diagnostics Agents

Outside Discovery
User Guide SolMan 7.1 SP01

User Guide

As soon as the Diagnostics Agent gets connected to a Solution Manager system, the Outside discovery agelet
starts running.
The Outside Discovery Agelet contains 3 different jobs:
Host Discovery:

this job is retrieving data from physical and virtual host on the monitored system.

Database Discovery: this job is retrieving data for all installed database on the monitored host.
IIS Discovery:

this job is retrieving data for installed Microsoft IIS on monitored host.

The Host Discovery process is the master process of the Outside Discovery Agelet. Database
Discovery and IIS Discovery processes are only started if Host Discovery has been able to
successfully push and create host entity on Solution Manager.

3.1

Host Discovery

The Host Discovery (aka PhysicalHostPushJob) is the master process and gets started first.
The Host Discovery is retrieving following data from the monitored system:
Physical Host this includes:
o

Operating System Information

Virtualized Solution used.

All Logical hosts defined on the monitored Physical Host.

3.1.1

Landscape Browser / Technical System Editor View

All hosts created by the Outside Discovery process are available in the Landscape Browser and the Technical
System Editor.

In the following example, Outside Discovery retrieved following information from a Diagnostics Agent installed
on physical host vml2262:
Landscape browser:

SAP AG 2008

Outside Discovery
User Guide SolMan 7.1 SP01
Physical Host vml2262 is using a Virtualization solution.
o

Its Operating System is SUSE Linux Enterprise Server 10 (x86_64)

its Full Qualify Domain Name is vml2262.wdf.sap.corp and its IP Address is 10.66.51.11

Logical Host ldai1sd7 is defined within this physical Host:

o

Its Operating System is SUSE Linux Enterprise Server 10 (x86_64)

its Full Qualify Domain Name is ldai1sd7.wdf.sap.corp and its IP Address is 10.66.51.53

More detailed data are available in the Technical System Editor like Alternative Hostnames, CPU Type.

Complete list of data is available using the Details button:

SAP AG 2008

10

Outside Discovery
User Guide SolMan 7.1 SP01

3.1.2

11

Host Discovery Process Status

The status of the Host Discovery Process is displayed within the Landscape Browser (column Host Status).

Here is a view of the Host Discovery Process running on Physical Host vml2262

Host Discovery run successfully for physical host vml2262

Version of the SAPHostAgent is Kernel version 720 and Patch Number 80.

3.1.3

Physical Host Data

Following data are retrieved for the Physical Host:

Physical Host fields

Description

Name

Short name of the physical host

Full Host Name

Full Host name of the physical host

IP Address

IP Address

Virtualized Solution

Identify if the physical host is running inside a virtualized

solution.

List of fields retrieved from the monitored host:

Operating System data

Example

OpSysUname

Windows NT

OpSys

WINDOWS_X86_32

OpSysRelease

5.2

SAP AG 2008

Outside Discovery
User Guide SolMan 7.1 SP01

12

OsSysBits

32

OpSysCategory

Windows NT

OpSysReleaseName

Windows NT 5.2

Manufacturer

PC Vendor

PhysicalRAMinMB

3904

VirtualRAMinMB

12276

NumberofCPUs

CPURate

2799

CPUCache
CPUType

3.1.4

Intel 801586 (Mod 2 Step 9)

Logical Host Data

The Outside Discovery process is retrieving all Logical Hosts from the installed SAP Product Instance: SAP J2EE
Engine, Diagnostics Agent, etc
Logical Host fields

Description

Name

Short name of the logical host

Full Host Name

Full Host name of the logical host

IP Address

IP Address

The Logical Host inherit from the same Operating System data as its Physical Host.
Logical Hosts are retrieved from the SAPHostAgent which reads the SAP Profile. If the Full Qualified Domain
Name is not reported correctly then the property SAPLOCALHOSTFULL=<FQDN> in the SAP Profile should be
modified manually in order to match your network configuration.

SAP AG 2008

Outside Discovery
User Guide SolMan 7.1 SP01

3.2

Database Discovery

Database Discovery (aka IISInfoPushJob) is started only after a successful push of the Host Discovery process.
Database Discovery is retrieving following data from the monitored system:
Database List installed on the monitored system.
Database Type, Name and additional properties like vendor, version.

3.2.1

Landscape Browser

All Database instances created by the Outside Discovery process are available in the Landscape Browser.

Database in Landscape Browser

SAP AG 2008

13

Outside Discovery
User Guide SolMan 7.1 SP01

3.3

14

Microsoft IIS Discovery

IIS Discovery (aka IISInfoPushJob) is started only after a successful push of the Host Discovery process.
IIS Discovery is only running on Windows Operating System. The process is stopped if no IIS instance is found on
the monitored system.
IIS Discovery is retrieving following data from the monitored system:
IIS instance automatically created in LMDB
IIS version (supported version are IIS 6 and IIS 7)
All Installed .Net versions
All IIS Applications and IIS Pools

3.3.1

Landscape Browser / Technical System Editor View

All IIS instances created by the Outside Discovery process are available in the Landscape Browser and the
Technical System Editor.

In the Landscape Browser you can search for all IIS instances

SAP AG 2008

Outside Discovery
User Guide SolMan 7.1 SP01
IIS Instance overview in the Technical System Editor

MSIIS Application view:

SAP AG 2008

15

Outside Discovery
User Guide SolMan 7.1 SP01

16

Advanced Configuration

The Outside Discovery Agelet can run out of the box without any additional configuration. However, some properties
are available in the Agelet configuration in order to control the process.
The configuration of the Outside Discovery Agelet is possible using the SMD Agent Administration UI.
The technical name for the Outside Discovery Agelet is: com.sap.smd.agent.application.e2edcc.

Here are default parameters for the Outside Discovery Agelet

4.1

Switching On/Off Outside Discovery

If necessary the whole Outside Discovery process can be switched off. This may happen if multiple Diagnostics
Agents are installed on the same physical host (example: End-user Experience Monitoring Agents).
Parameter name

Default value

e2edcc.enabled

true

Description
true the Outside discovery process is running.
false all Outside discovery jobs are stopped.

4.2

Internal Cache

In order to avoid unnecessary network traffic between Outside Discovery Agelet and Solution Manager as well as
unnecessary database update in LMDB, each job implements an internal cache.
When collecting data from the SAPHostAgent Web Service, job is checking that collected data are different from the
previous successfully collect.
Following cache implementations are available:
Memory cache: the cache is only valid while the Diagnostics Agent is running. If the Diagnostics Agent gets
re-started, then each job will push discovered data to Solution Manager.
File cache: the cache is physically persisted on the file system, within the Agelet directory (filename:
dcc.cache). If the Diagnostics Agent gets restarted, the previous cache is loaded.

SAP AG 2008

Outside Discovery
User Guide SolMan 7.1 SP01

17

Parameter name

Default value

cache.type

memory

Description
memory use memory cache.
file use file cache.

4.3

Force Push Flag

This property is used only on test systems in order to check that information is pushed correctly on Solution
Manager. If activated, the relevant job will push the data without checking the cache.
This option will increase network traffic and database update and should not be used on Production or
Quality Systems.
Parameter name

Default value

job.physical.force.push

Description
false Host Discovery job use cache.

false

true Host Discovery ignore cache.

job.dbinfo.force.push

false Database Discovery job use cache.

false

true Database Discovery job ignore cache.

job.iisinfo.force.push

false IIS Discovery job use cache.

false

true IIS Discovery job ignore cache.

4.4

Jobs scheduling

By default, all Outside Discovery jobs are scheduled to run each 5 minutes. This means, each job is querying the
SAPHostAgent Web Service in order to get latest up to date information at a frequency of 5 minutes.
In some cases, we may need to adjust the scheduling on the monitored system in order to reduce SAPHostAgent
access frequency.
The schedule can be adjusted using following property:
Parameter name

Default value

Description

job.physical.scedule.period.m

Define frequency in minutes of the Host discovery job

job.dbinfo.scedule.period.m

Define frequency in minutes of the Database discovery job

job.iisinfo.scedule.period.m

Define frequency in minutes of the IIS discovery job

SAP AG 2008

Outside Discovery
User Guide SolMan 7.1 SP01

4.5

18

Customizing Physical Host FQDN and IP address

In some cases, the Full Qualified Domain Name and IP address of the Physical Host returned by the
SAPHostAgent is not accessible from Solution Manager. This situation is due to multiple network configuration on the
host.
In order to force a specific value for FQDN and IP address, following properties can be used:
Parameter name

Default value

Description

job.physicalhost.fqdn

none

Force the Full Qualified Domain Name of the physical host

job.physicalhost.ip

None

Force the IP Address of the physical host.

SAP AG 2008

Outside Discovery
User Guide SolMan 7.1 SP01

19

Support Tools

Different tools are available in Solution Manager in order to identify problems during the Outside Discovery process.

5.1

Landscape browser

5.1.1

Landscape Tab

Hosts View

As already seen in section 3.1.2, Landscape Browser is showing the status of the Host Discovery process.
Any error during the host discovery process is reported in the Host Status
under the Application area Data Enrichment.

Technical System Status section

Example of error occurring during Host discovery process of Physical Host nced60165205a:
SAPHostAgent is too old Upgrade is necessary.

5.1.2

Administration Tab

Logs and Traces View

Additional logs are available in the Logs and Traces view of the Landscape Browser. Logs are available for each
discovery jobs using following Search pattern:
Discovery job

Search Pattern

Description

Host Discovery

Push Host <hostname>

Search pattern for Host Discovery job on specific

hostname.

Database Discovery

Push Database <SID> at <hostname> of

type <database type>

Search pattern for Database discovery job on specific

hostname.

IIS Discovery

Push MSIIS IIS.SystemHome.<hostname>

Search pattern for IIS discovery job on specific

hostname.

SAP AG 2008

Outside Discovery
User Guide SolMan 7.1 SP01

20

Example of Logs and Traces view for all discovery jobs:

Enter Search query according to pattern table here all discovery jobs PUSH*
Make sure current users is switch off

Additional details are available in the Log Details view:

The level of details (Error, Warning, Info and Debug) is managed in Administration Tab
Configuration.

SAP AG 2008

Configuration

Log

Outside Discovery
User Guide SolMan 7.1 SP01

5.2

21

Diagnostics Agent Administration

All logs written by the Outside Discovery Agelet are available through the SMD Agent Administration UI.

5.2.1

Agent Error Monitoring Tab

This view shows only exceptions reported by all SMD Agents.

Following locations are available for filtering the Outside Discovery jobs:
Discovery job

Location

Host Discovery

com.sap.smd.e2edcc.host

Database Discovery

com.sap.smd.e2edcc.db

IIS Discovery

com.sap.smd.e2edcc.iis

5.2.2

Agent Log Viewer

The Agent Log Viewer can be used to check raw data retrieved from the SAPHostAgent by the Discovery job.
Each discovery job has its own log file. In order to get the most detailed report of extracted data, the Log Level should
be switched to debug.

SAP AG 2008

Outside Discovery
User Guide SolMan 7.1 SP01

22

Available log files for Outside Discovery Jobs:

Discovery job

Log file

Host Discovery

e2edcc_host.*.log

Database Discovery

e2edcc_db.*.log

IIS Discovery

e2edcc_iis.*.log

Example of e2edcc_host.*.log file which contains detailed process information

SAP AG 2008

Outside Discovery
User Guide SolMan 7.1 SP01

5.3

23

Diagnostics Agent Support

The Diagnostics Agent Support Tool is available to check:

JAVA Bean Controller registration - SMD_DataEnrichment_Registrator.
Discovery jobs statistics.

5.3.1

SMD Server Analysis View

In this view section SMD JNDI objects auto-registered we can check that the JAVA Bean Controller is registered
correctly.

The JAVA Bean Controller is used to controlled callback performed by each Outside Discovery Agelet.

If the object is not registered correctly, use the objects Reinitialization button to re-create all objects.

SAP AG 2008

Outside Discovery
User Guide SolMan 7.1 SP01

5.3.2

Diagnostics Agent Runtime View

The Diagnostics Agent Runtime view is used to get statistics about the Outside Discovery Jobs.
You have to select the Diagnostics Agent and use the Agent Monitoring Tab.

This view shows:

Outside Discovery jobs running on the Diagnostics Agent
Average execution time per jobs
Total number of execution
Last execution date
Number of Exceptions
Number of Timeouts exceptions.

SAP AG 2008

24

Outside Discovery
User Guide SolMan 7.1 SP01

25

Troubleshooting Guide

6.1

Troubleshooting Roadmap

In order to troubleshoot a specific Outside Discovery process, following roadmap may be used this applies to any
discovery job running on a specific host.
Tool

Check

Section
reference

Check Host status for the Application Area Data

Enrichment.
Landscape Browser / Host View

5.1.1
The status should be green as the Host
Discovery process is the master process.

Landscape Browser / Logs and

Trace view

Diagnostics Agent Administration /

Agent Error Monitoring Tab

Diagnostics Agent Administration /

Agent Log Viewer

Use following search string push*<hostname>

to check logs for each discovery job.
5.1.2
If Exception is found then the problem is located
in the persist process.
Select relevant Diagnostics Agent
If an exception is found then the problem is
located in the discovery process.

5.2.1

Select relevant Diagnostics Agent set relevant

log file to debug
5.2.2
The log file should display all actions related to
the discovery process:

Once the problem has been identified, please check in the Common Issues (section 6.2) for detailed description of the
root cause and possible solution.
If the problem is not listed in the Common Issues section, please create a Message attaching the logs file from the
Diagnostics Agent.

SAP AG 2008

Outside Discovery
User Guide SolMan 7.1 SP01

6.2
6.2.1

26

Common Issues
Diagnostics agent is not connected to solution manager server

Diagnostics agent is not connected to solution manager server, connection status: CONNECTING
Diagnostics agent is not connected to solution manager server, connection status:
LAST_REGISTRATION_ON_ERROR
Description

this message is displayed if:

Diagnostics Agent is not yet connected to the Solution Manager system.
o Please make sure the Agent is starting correctly and is connected to a Solution
Manager.
JAVA Bean controller SMD_DataEnrichment_Registrator is not available.
o It may happen during deployment of new LM_SERVICE that the JAVA Bean
Controller SMD_DataEnrichment_Registrator is not correctly registered
please refer to section 5.3.1 for instruction on how to reinitialize JAVA Bean
Controller.

6.2.2

An exception occurred during the execution of the function

'FM_DIAGLS_PUSH_PHYSICAL_HOST'

java.rmi.RemoteException:RfcExecutionException; nested exception is:

com.sap.sup.admin.abap.rfc.exception.RfcExecutionException:An exception occured during the execution of the
function 'FM_DIAGLS_PUSH_PHYSICAL_HOST': DBIF_RTAB_SQL_ERROR > com.sap.mw.jco.JCO$Exception:SQL error
-964 when accessing table VBMOD. <MiddlewareJRfc.java:516:g
Description

an error occurs during the communication between the Java Bean Controller and the
persistence Function Module in ABAP (package AI_DIAGNOSTICS_DATA_ENRICHMENT).
This is a global exception from the AI_DIAGNOSTICS_DATA_ENTICHMENT package and
should be resolved on Solution Manager ABAP stack.

Additional
Checks

SAP AG 2008

Check SOLMANDIAG destination between SAP J2EE Engine and ABAP stack.
Check ST22 dumps for additional information

Outside Discovery
User Guide SolMan 7.1 SP01

6.2.3

27

Exception while parsing SapOsCol DataNo data allowed here

com.sap.smd.agent.plugins.dcc.exc.SapOsColParsingException:Exception while parsing

SapOsCol Data. > com.sap.engine.lib.xml.parser.NestedSAXParseException:Fatal Error:
com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here(:main:,
row:951, col:1) > com.sap.engine.lib.xml.parser.ParserException:XMLParser: No data
allowed here (:main:, row:951, col:1) <XMLParser.java:2509:scanMisc()>
Description

This exception occurs when the Host Discovery process is trying to parse SAPosCol data
retrieved from the SAPHostAgent.
In some situation the SAPHostAgent is partially creating the SAPosCol.xml file before
sending it to Web Service.

Solution

6.2.4

Apply SAP Note 1574675 SAPOscol WS Returns malformed XML response.

Exception while parsing SapOsCol DataParsing an empty source

com.sap.smd.agent.plugins.dcc.exc.SapOsColParsingException:Exception while parsing

SapOsCol Data. > java.io.IOException:Parsing an empty source. Root element expected!
<XMLParser.java:2885:onEncodedDataReaderEOF()>
Description

SAPHostAgent Web Service is returning an empty SAPosCol.xml file.

Additional
Checks

SAPHostAgent log files should be analyzed in order to identify SAPHostAgent the issue.

6.2.5

Failed to open HW file

Failed to open HW file. <MimeHttpBinding.java:747:buildFaultException()>

Description

This exception occurs when the SAPHostAgent process (Porttype SAPosCol) is not able to
provide the SAPosCol.xml file

Additional
Check

SAPHostAgent log files should be analyzed in order to identify SAPHostAgent exception.

SAP AG 2008

Outside Discovery
User Guide SolMan 7.1 SP01

6.2.6

28

CIM Request EnumerateInstances for classes Application failed: : Provider load

failure

java.rmi.RemoteException:Webservice invocation error occured on stub

com.sap.smd.agent.wsclients.saphostcontrol.SAPHostControlStub@680a68e9; nested exception is:
javax.xml.rpc.soap.SOAPFaultException: CIM Request EnumerateInstances for classes Application failed:
EnumerateInstances for Application failed: Provider load failure >
Description

The issue is the restriction done by II 7.0 on Windows 2008 and higher while discovering IIS
Applications
in
WMI
namespace.
Additional
information
available
at
http://learn.iis.net/page.aspx/162/managing-sites-with-iis-7039s-wmi-provider/.
You must be an administrator to connect to the Web Administration WMI namespace. This
means that you are logged in as one of the following:

Solution

6.2.7

The built-in Administrator account on Windows Server 2008

A member of the Administrators group and you have disabled User Account Control
(UAC)

A member of the Administrators group and UAC is enabled.

Add the user sapadm to the Local Administrator Groups.

GetObject ADSi Object IIS://localhost/W3SVC failed: Error : Access is denied

java.rmi.RemoteException:Webservice invocation error occured on stub

com.sap.smd.agent.wsclients.saphostcontrol.SAPHostControlStub@16e3879; nested exception is:
javax.xml.rpc.soap.SOAPFaultException: GetObject ADSi Object IIS://localhost/W3SVC failed: Error :
Access is denied.
Description

SAPHostAgent user does not have authorization to access ADSi IIS object.

Solution

Add the user sapadm to the Local Administrator Groups.

6.2.8

java.net.SocketTimeoutException: Read timed out

java.rmi.RemoteException:Service call exception; nested exception is:

java.net.SocketTimeoutException: Read timed out > java.net.SocketTimeoutException:Read timed out
<SocketInputStream.java:-2:socketRead0()>
Description

A timeout exception occurred while accessing one of the SAPHostAgent Web Service
methods.

Additional

SAPHostAgent log files should be analyzed in order to identify SAPHostAgent performance or read

SAP AG 2008

Outside Discovery
User Guide SolMan 7.1 SP01
check

6.2.9

29

issue.

Timeout waiting for saposcol answer

Timeout waiting for saposcol answer. <MimeHttpBinding.java:747:buildFaultException()>

Description

A timeout exception occurred while accessing the SAPHostAgent Web Service (Porttype
SAPosCol)

Additional
check

SAPHostAgent log files should be analyzed in order to identify SAPHostAgent performance or read
issue.

6.2.10

Error to perform http request cause Socket output stream shutdown by peer

java.net.SocketException: Socket output stream shutdown by peer. >

java.net.SocketException:Socket output stream shutdown by peer. <Response.java:481:initialize()>
Description

The SAPHostAgent has closed the communication channel with Diagnostics Agent.

Additional
check

SAPHostAgent log files should be analyzed in order to identify SAPHostAgent performance or read
issue.

6.2.11

Unable to open connection to host "localhost:1128". The host is down or

unavailable

java.rmi.RemoteException:Error to perform http request cause by java.io.IOException: Unable to

open connection to host "localhost:1128". The host is down or unavailable...;
Description

The SAPHostAgent or port 1128 is not accessible.

Additional
check

Please check that SAPHostAgent is running correctly.

6.2.12

Cannot established a trusted connection to SAP host agent webservice

Cannot established a trusted connection to SAP host agent webservice. (SAP Host agent version
installed doesn't support trusted connection method)
<SAPHostAgentTrustedConnectionConfigurator.java:117:setupTrustedConnection()>
Description

SAP AG 2008

SAPHostAgent do not support trusted connection.

Outside Discovery
User Guide SolMan 7.1 SP01
Required
Action

30

Upgrade SAPHostAgent to latest version.

Cannot established a trusted connection to SAP host agent webservice. (Cannot find the file
/usr/sap/hostctrl/work/sapcontrol_logon/logon5.)
Cause: It means that the SMD Diagnostics agent does not have enough permissions to read the folder
"/usr/sap/hostctrl/work/sapcontrol_logon/logon5"
Description

The Diagnostics Agent does not have enough

"/usr/sap/hostctrl/work/sapcontrol_logon/logon5"

Required
Action

Change the agent OS user so that it can read the folder.

6.2.13

permissions

to

read

the

folder

Webservice port type not enabled

Webservice port type not enabled <MimeHttpBinding.java:747:buildFaultException()>

Description

One of the service Porttype of the SAPHostAgent is not available or not setup correctly.

Additional
Check

Check Porttype configuration (see section 2.1.2).

6.2.14

Webservice invocation error occurred Generic error

java.rmi.RemoteException:Webservice invocation error occured on stub

com.sap.smd.agent.wsclients.saphostcontrol.SAPHostControlStub@46b8c77f; nested exception is:
javax.xml.rpc.soap.SOAPFaultException: Generic error. Check the trace file C:\Program
Files\SAP\hostctrl\work\dev_sapdbctrl for more details. Increasing the trace level may provide further
details. > javax.xml.rpc.soap.SOAPFaultException:Generic error. Check the trace file C:\Program
Files\SAP\hostctrl\work\dev_sapdbctrl for more details. Increas
Description

Generic exception in SAPHostAgent process

Additional
Check

SAPHostAgent log files should be analyzed in order to identify SAPHostAgent performance or read
issue.

SAP AG 2008

Outside Discovery
User Guide SolMan 7.1 SP01

31

Technical Implementation

This section will detail the SAPHostAgent Web Service methods used to discover each element. This will help
understanding:

How a component is discovered.

Why a component is not discovered correctly.

The software soapUI (download available here http://www.soapui.org) can be used to access any Web Service
methods exposed by the SAPHostAgent.

Outside Discovery is using following 2 web services exposed by SAPHostAgent:

Porttype

Web Service WSDL

SAPHostControl

http://<hostname>:1128/SAPHostControl/?wsdl

SAPOscol

http://<hostname>:1128/SAPOscol/?wsdl

7.1

Host Discovery

7.1.1

Physical host

Porttype

Web Service method

Parameters

Description

SAPHostControl

GetComputerSystem

none

Get Physical host data

Field Name

Description

Name

Short name of the physical host

Hostnames

Full Qualified Domain Name list of host only one is returned localhost is filtered
out

IPAdresses

IP address list only one is returned (the one that is matching the FQDN) 127.0.0.1
is filtered out

7.1.2

Operating System

Porttype

Web Service method

Parameters

Description

SAPOscol

getHWConfXML

none

This method returns the saposcol.xml file

generated by the saposcol.exe binary. A parser
has been implemented in order to read OS data.

Field Name

Example

OpSysUname

Windows NT

OpSys

WINDOWS_X86_32

SAP AG 2008

Outside Discovery
User Guide SolMan 7.1 SP01

32

OpSysRelease

5.2

OsSysBits

32

OpSysCategory

Windows NT

OpSysReleaseName

Windows NT 5.2

Manufacturer

PC Vendor

PhysicalRAMinMB

3904

VirtualRAMinMB

12276

NumberofCPUs

CPURate

2799

CPUCache
CPUType

7.1.3

Intel 801586 (Mod 2 Step 9)

Virtualization Information

Porttype

Web Service method

Parameters

Description

SAPOscol

getOSData

none

This method contains information related to the

virtualization solution.

Field Name

Description

GeneralVirtCIM_SolutionName

This field is used to identify if the host is virtual of physical.

If this field contains Native Hardware or VIRT_METHOD_NONE then the host
is Physical Otherwise the host is Virtual.

GeneralVirtCIM_Type

Type of Virtualization - This field is optional.

GeneralVirtCIM_SolutionVersion

Version of Virtualization solution - This field is optional.

7.1.4

Logical hosts

Porttype

Web Service method

Parameters

Description

SAPHostControl

GetCIMObject

instances =
SAPInstance

This method returns all SAP Instances with SID,

short host name, FQDN and IP address of the
logical host.

Field Name

Description

Hostname

Short host name of the logical host

FullQualifiedHostname

FQDN of the logical host

IPAddress

IP address of the logical host

SAP AG 2008

Outside Discovery
User Guide SolMan 7.1 SP01

7.2

33

Database Discovery

7.2.1

Installed Database List

Porttype

Web Service method

Parameters

Description

SAPHostControl

listDatabases

none

Returns all databases installed on monitored

system.

Field Name

Description

Database/Name

Short name of the Database

Database/Type

Database type

Database/InstanceName

Database instance name

Database/Host

Host where the database is installed

7.2.2

Database Properties

Porttype

Web Service method

Parameters

Description

SAPHostControl

getDatabaseProperties

Database/Name

Returns properties for the selected database.

Database/Type

All properties returned by this Web Service are sent to Solution Manager.

SAP AG 2008

Outside Discovery
User Guide SolMan 7.1 SP01

7.3

34

IIS Discovery

7.3.1

Identifying IIS instance

Porttype

Web Service
method

Parameters

Description

SAPHostControl

getCimObject

EnumerateInstances
=WinRegistry?WinRegistryPath=HKLM
\Software\Microsoft\InetStp

Returns properties for the selected

database.

An IIS instance is found if the method returns elements If the entry is not found, the IIS Discovery Job is stopped.
Field Name

Description

VersionString

Version of the IIS Server

InstallPath

IIS Server installation path

MajorVersion
<MajorVersion>.<MinorVersion>
MinorVersion

7.3.2

Installed .Net Version

Porttype

Web Service
method

Parameters

Description

SAPHostControl

getCimObject

EnumerateInstances
=WinRegistry?WinRegistryPath
=HKLM\\Software\\Microsoft\\NE
T Framework Setup\\NDP

Installed .Net versions are visible in this

Registry path.
We used following Microsoft Note in order to
identify installed .Net Framework
http://msdn.microsoft.com/enus/kb/kbarticle.aspx?id=318785

SAP AG 2008

Outside Discovery
User Guide SolMan 7.1 SP01

7.3.3

35

Discovering IIS Version 7.x

Applications and Sites

Porttype

Web Service
method

Parameters

Description

SAPHostControl

getCimObject

EnumerateInstances
=root/WebAdministration/Application

Returns all IIS Applications

Field Name

Description

SiteName

IIS Site Name

ApplicationName

IIS Application Name

ApplicationPool

IIS Application Pool

Path

IIS Application Path

Application Physical Path

Additional query is needed in order to get the Physical Path for each discovered Application in previous step.
Porttype

Web Service
method

Parameters

Description

SAPHostControl

getCimObject

Associators =

Returns Application physical path

root/WebAdministration/Application?Pa
th=<ApplicationPath>&SiteName=<S
iteName>?AssocClass=ApplicationCo
ntainsVirtualDirectory

Field Name

Description

PhysicalPath

Application Physical Path

SAP AG 2008

Outside Discovery
User Guide SolMan 7.1 SP01

7.3.4

36

Discovering IIS Version 6.x

IIS ADS Objects

Porttype

Web Service
method

Parameters

Description

SAPHostControl

getCimObject

EnumerateInstances =

Get all Ads Path.

ADSi_Object?ADsPath=IIS://loc
alhost/W3SVC

Only ADS Objects where KeyType equals IISWEBSERVER are considered as Site.
Field Name

Description

ADsPath

ADS Path

KeyType

ADS Key Type

ServerComment

Site Name

IIS Application
Porttype

Web Service
method

Parameters

Description

SAPHostControl

getCimObject

EnumerateInstances =

We are using path from previous object to get

additional information on specific Site Object.

ADSi_Object?ADsPath=<ADsP
ath>

Only ADS Key Type of IISWEBVIRTUALDIR are considered as Application

Field Name

Description

ADsPath

ADS Path

KeyType

ADS Key Type

SAP AG 2008

Outside Discovery
User Guide SolMan 7.1 SP01

37

IIS Application details

Porttype

Web Service
method

Parameters

Description

SAPHostControl

getCimObject

EnumerateInstances =

We are using path from previous object to get

additional information on specific Application
Object.

ADSi_Object?ADsPath=<ADsP
ath>

Field Name

Description

AppFriendlyName

Application Name

Path

Application Path

AppPoolId

Application Pool

SAP AG 2008