solmandiag guide sp15

8/2/2019 SolManDiag Guide SP15

1/60


2/60

Copyright 2004 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP AG. The

information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain

proprietary software components of other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered trademarks

of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA,

AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries,

z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix

are trademarks or registered trademarks of IBM Corporation in the

United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open

Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,

VideoFrame, and MultiWin are trademarks or registered trademarks of

Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered

trademarks of W3C, World Wide Web Consortium, Massachusetts

Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used

under license for technology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and

other SAP products and services mentioned herein as well as their

respective logos are trademarks or registered trademarks of SAP AG in

Germany and in several other countries all over the world. All other

product and service names mentioned are the trademarks of their

respective companies. Data contained in this document

serves informational purposes only. National product

specifications may vary.

These materials are subject to change without notice.

These materials are provided by SAP AG and its affiliated

companies ("SAP Group") for informational purposes

only, without representation or warranty of any kind, and

SAP Group shall not be liable for errors or omissions with

respect to the materials. The only warranties for SAP

Group products and services are those that are set forth in

the express warranty statements accompanying such

products and services, if any. Nothing herein should be

construed as constituting an additional warranty.

SAP Library document classification: PUBLIC

Disclaimer

Some components of this product are based on Java.

Any code change in these components may cause

unpredictable and severe malfunctions and is therefore

expressively prohibited, as is any decompilation of these

components.

Any Java Source Code delivered with this product is

only to be used by SAPs Support Services and may not

be modified or altered in any way.

Documentation in the SAP Service Marketplace

You can find this documentation at the following Internet

address:service.sap.com/solutionmanager

Neurottstrae 1669190 WalldorfGermanyT +49/18 05/34 34 24F +49/18 05/34 34 20!!!"#"$!!!"#"$!!!"#"$!!!"#"$


3/60

%##&'(

Type Style Represents

Example Text Words or characters that appearon the screen. These includefield names, screen titles,pushbuttons as well as menunames, paths and options.

Cross-references to other

documentation

Example text Emphasized words or phrases inbody text, titles of graphics andtables

EXAMPLE TEXT Names of elements in thesystem. These include reportnames, program names,transaction codes, table names,and individual key words of aprogramming language, whensurrounded by body text, forexample, SELECT andINCLUDE.

Example text Screen output. This includes fileand directory names and theirpaths, messages, names ofvariables and parameters,source code as well as names ofinstallation, upgrade anddatabase tools.

Example text Exact user entry. These arewords or characters that youenter in the system exactly asthey appear in thedocumentation.

Variable user entry. Pointedbrackets indicate that youreplace these words andcharacters with appropriateentries.

EXAMPLE TEXT Keys on the keyboard, forexample, function keys (such asF2) or the ENTER key.

)

Icon Meaning

Caution

Example

Note

Recommendation

Syntax


4/60

Solution Manager Diagnostics..............................................................5Solution Manager Diagnostics: Navigation ..............................................7

ACTIVITY.................................................................................................9Thread Dump Analysis................................................................................ 9

ALERTS.................................................................................................12Alert Monitoring.........................................................................................12

Remote Database Monitoring...................................................................13

SAP J2EE SQL Monitoring........................................................................ 14

SQL Command Console............................................................................ 15

LOGS AND TRACES.............................................................................17Log Display ................................................................................................17

Log Configuration Area............................................................................. 17

File Navigation Area ..................................................................................18

Log Viewer.................................................................................................. 19

OPERATING SYSTEM ..........................................................................23File System Browser .................................................................................23

OS Command.............................................................................................26

Remote OS Monitoring..............................................................................28

J2EE Command Console ..........................................................................30

PERFORMANCE ...................................................................................31HTTP Analysis............................................................................................ 31

J2EE Server Analysis................................................................................34Java Web DynPro Monitoring................................................................... 35

STATUS.................................................................................................36J2EE System Information .........................................................................36

Systems Landscape Directory .................................................................37

USAGE STATISTICS.............................................................................38Portal Activity Report................................................................................38

CONFIGURATION AND FILE MANAGEMENT ....................................39Configuration and File Reporting............................................................. 39


5/60

Comparing Multiple Instances.................................................................. 46

SOFTWARE CHANGE REPORTING....................................................50Software Change Reporting ..................................................................... 50

J2EE SYSTEMS ....................................................................................52Key Storage / SSL......................................................................................52

LDAP Browser............................................................................................ 54

TASKS ...................................................................................................55Abap Connectivity ..................................................................................... 55

Scheduler ...................................................................................................56

Self Check ..................................................................................................60

Solution Manager Diagnostics

Introduction

The Solution Manager Diagnostics (SMD) is a Java-based tool running on SAP Web ApplicationServer 6.40 that provides essential functions and tools to centrally monitor and analyze a completeNetWeaver solution landscape. It provides functionality to support Java-based components. Thedisplayed information is gathered by various agents like SMD agent, saposcol, sapccmsr, IntroscopeAgent and Component Analyzer.

Integration

Solution Manager Diagnostics is integrated with various monitoring tools and capabilities to facilitatebetter and easier supportability. To troubleshoot problems on the J2EE Engine and applicationsrunning on it, Wily Introscope tool is integrated with SMD. Mercury Interactive load generator tool isalso integrated to SMD and allows SAP Support to produce some defined load on the SAP NetWeaversolution remotely in order to detect performance bottlenecks.

Prerequisites

Solution Manager Diagnostics primarily provides functionality to support Java based components,therefore at least an active J2EE installation is required to run on the central Solution ManagerDiagnostics setup.

It is critical to install Solution Manager Diagnostics within SAP NetWeaver solution landscapes. OneSolution Manager Diagnostics system can monitor many SAP NetWeaver solutions but allcomponents within one SAP NetWeaver solution should be attached to the same Solution ManagerDiagnostics system.

Features

Solution Manager Diagnostics is a consolidated tool for monitoring, troubleshooting, and analysis ofcomplex Java-based solutions. It enables simple access and navigation to a suite of valuable tools.SMD provides transparency to end-users in terms of platform and requires no OS / filesystem accessfollowing installation and configuration. Some other advantages of using Solution Manager Diagnosticstools are:

1. Ease of use, all functionality of SMD is accessible via a standard Web browser through acommon GUI

2. OS level access is not necessary to monitor solution landscape


6/60

3. Cluster wide comparison of settings is possible

4. Remote load test integration is also possible

5. Historical information can be collected and maintained in SMD

Results

Various monitoring tools and functionalities to monitor Java based components with a landscape areincorporated in SMD. These tools and features are either links to existing tools or have been customdesigned for better troubleshooting and customer support. For SMD navigation and functionalityoverview refer SMD Navigation


7/60

Solution Manager Diagnostics: Navigation

Use

Navigation through Solution Manager Diagnostics application is fairly easy and intuitive. Solution

Manager Diagnostics has the capability to consolidate information from disparate landscapes withdifferent environments and make it available to the end user through a single User Interface. It offers avery rich collection of monitoring tools and troubleshooting capabilities that will reduce the turnaroundtime from both the customer as well as SAP to solve issues.

Structure

The structure of SMD has been organized in such a way that the end user is capable of selecting thelandscape and environment to be reviewed and later choose among the various tools/featuresprovided by SMD. The User Interface can be divided into three major areas:

1. First Level of navigation: Here the user has a choice to select the appropriate

a. Solution

b. Landscape

c. Product

d. Host

This information is obtained from Component Analyzer.

2. Second Level of Navigation: From here the user starts the navigation to choose between type ofinformation to be obtained.

a. Monitoring: The monitoring tools are structured under this tab.

b. Reporting: Various reporting capabilities have been categorized under this tab.

c. Configuration: This tab provides configuration options for SMD through the interface.

3. Detailed Navigation: This is the main navigational area within SMD. The tools and reportingfunctionality have been grouped under broader areas of troubleshooting and reporting.

Features

The various monitoring, reporting and configuration tools for the end user are structured as follows:

Monitoring: Monitoring tab has several tools for troubleshooting which have been categorized underdifferent components based on the type of activity and troubleshooting areas. These components andcorresponding tools are:

Activity

o Thread Dump Analysis

Alerts

o Alert Monitoring

Database

o Remote Database Monitoring

o J2EE SQL Monitoring

o SQL Command Console

Logs and Traces

o Log Display

o Log Viewer

Operating System


8/60

o Remote OS Monitoring

o OS CommandConsole

o File System Browser

o J2EE Command Console

Performance

o HTTP Analysis

o J2EE Server Analysis

o Java Web Dynpro Monitoring

Status

o SAP J2EE Systems Information

o Systems Landscape Directory

Reporting: Reporting tab has several reporting capabilities for detailed analysis; these have beencategorized under different components based on the type of reporting and functionality desired.

These components and corresponding reporting tools are: Usage Statistics

o Portal Activity Report

Configuration and File Management

o Configuration and File Reporting

o Comparing Multiple Instances

Software Change Management

o Software Change Reporting

J2EE System

o KeyStorage / SSL

o LDAP Browser

Configuration: Configuration tab has several configuration capabilities for detailed analysis; thesehave been categorized under different components based on the type of configuration and componentin use.

Tasks

o Scheduler

o ABAP Connectivity

o Self Check


9/60

ACTIVITY

Thread Dump Analysis

UseThread Dump Analysis component of SMD can be used for central triggering and scheduling of JVMbased thread dumps for certain or all J2EE node(s), gathering and transfer generated thread dumpsand analysis of the thread dump data via appropriate user interface. A thread dump is a snapshot ofthe state of all the Java threads.

The JVM is in charge of allocating and de allocating memory to Java Applications. It manages thememory using a special agent, Garbage Collections, which is part of the JVM. There are two types ofGCs that occur, Regular and Full GCs. These collect the memory that is no longer being used byJava applications returns it to the heap.

Prerequisites

Make sure that the -Xrs option is not used in the instance.properties file of the JVM. To trigger or analyze thread dump for the selected hosts or all hosts, the relative hosts have to

be registered in the database through ABAP System Setup.

To analyze thread dump from an uploaded file, you need to generate the thread dump on thesource system manually.

Features

Using SMDs Thread Dump Analysis you are able to count the threads used, see to which methodthey belong to and what task they were performing. A full thread dump is a request to the Java VirtualMachine to dump its current state.

Activity

1. To Trigger Full Thread Dumps for All Nodes

1. Select Thread Dump Analysis in the Detailed Navigation under Activity.2. In the section of Select J2EE Nodes, select all the nodes listed and select Trigger Dump

2. To Trigger Full Thread Dumps for Selected Nodes

1. Select Thread Dump Analysis in the Detailed Navigation under Activity.2. In the section of Select J2EE Nodes, choose the desired nodes.3. Select Trigger Dump button.

3. Trigger Full Thread Dumps at Intervals

1. Select Thread Dump Analysis in the Detailed Navigation under Activity.2. In the section of Trigger a series of Full Thread Dumps, Define an interval and number of

dumps to repeat triggering thread dumps.3. Select the Start now

4. Analyze Full Thread Dumps for Selected Nodes

1. Select Thread Dump Analysis in the Detailed Navigation under Activity.


10/60

2. In the section of Select J2ee Nodes, choose the nodes.3. Select the trigger Dumps, Then select the Analyze button.

5. Analyze Full Thread Dumps for Uploaded File

1. Select Thread Dump Analysis in the Detailed Navigation under Activity.

2. In the section of Upload files, select the Browse button to choose a thread dump file.3. Select the Analyze file button.4. Then you can follow the step 2 3 of Analyze Full Thread Dumps for All Nodes.

Structure

Title Description And Usage

Select J2EE Nodes -Select which nodes you want to create a thread dump

-Trigger dump button-Analyze dump button

Trigger a Series ofFull Thread Dumps

-Interval [seconds]

-Number of dumps you wish to analyze

-Start analyze button

-Prepare a Scheduler Template

Upload File -Browse to dump file

-Upload button

ResultsAfter a thread dump has been triggered, click on Analyze in order to view the contents and result ofthe dump. A new screen will appear with a table shown containing several tabs and options to choose:

Tab Title Description And Usage

Summary This tab is useful for comparing differences between thread dumps. Foreach cluster node, their log file will be displayed if any thread dumpsoccurred.The summary analysis reads the console logs from the selected

components and shows it in a tab. The summary table structure isindependent of the chosen J2EE Node ID. If a dump contains adeadlock it would be shown in summary as well.Click on one of the thread dumps to view the Single Dump TableThese columns are contained in the table:

Timestamp Dispatcher

Server

All Dumps This tab displays all the thread dumps for the selected J2EE node id.You are able to compare a large number of thread dumps at the sametime in order to compare any changes. You are also given the option todownload the thread dumps for offline analysis.These columns are contained in the table:

Filter Threads by Application, KM, Anonymous or System Group Prefix

Thread State (Java state knowledge is required)


11/60

First non-java.* stack line

Total Count

1 N However many threads there are (Click here to displaythread details)

Single Dump This tab is useful for finding out what the state of JVM threads is and

identifying any type of deadlocks. You can view the thread dumpsgrouped by name, total number of threads, thread conditions and alsothe state of the threads.These options are available to filter the table contents:

Dump Number

Filter ThreadsThese columns are contained in the table:

Group Name Total (Click here to display thread details)

Waiting on Condition Runnable In Object.wait()

Threads Detail This tab displays the details of the selected thread dump such as NativeThread Id, the condition of each thread and also a complete stack traceof a thread.

Memory GarbageCollection

This tab displays an analysis of the Garbage Collections taken duringthe thread dump. A general understanding of JVM memory managementis required here.With this tool you can view the garbage collection behavior in graphicalform.There are three tables displayed on this page, and these columns arecontained in the table:Time Frame

Time Frame

GC Type

Statistics Start time End time

Up Time % GC Time

VM Parameters

GC Type Count

Total Duration Average Duration

Total Recycled Bytes

Average Recycled Bytes

Customer Code All threads from the dump are scanned for any type of non SAPstandard packages. If any customer threads are found, they aredisplayed here. Clicking on any of the threads will display them in theThread Details report.


12/60

ALERTS

Alert Monitoring

UseMonitoring which uses Alerts to alarm a critical situation. Alerts can be treated as an error report or aservice request. These alerts are generated based on some threshold values set for the monitoredsystems, processes or behaviors.

Integration

Integration of analysis transaction RZ20 to display Alerts is received by SAP Monitoring Infrastructure.(E.g. availability of a certain component, error pattern in log files, certain threshold, if reached). SMDuses the Alert monitor (transaction RZ20) to facilitate Alert Monitoring.

More information on this topic can be referred from http://help.sap.com,under topic SAPNetWeaver Technical Operations Manual Administration of SAP Web Application Server (ABAP)

Monitoring

Prerequisites

Please refer to the Solution Manager Diagnostics setup guide for more information on prerequisites forsetting up Alert Monitoring through SMD. The setup guide can be downloaded from the SAP ServiceMarketplace (http://service.sap.com) under alias diagnostics.

Activities

1. Under the Monitoring Tab of the SMD application.

2. Select Alert Monitoring in the Detailed Navigation panel under Alerts.

3. The RZ20 transaction starts in the application window of SMD.4. Refer to the RZ20 User Documentation for further details.


13/60

Remote Database Monitoring

Use

As of SAP Web Application Server 6.40, you can administer not only your local SAP database, but

also remote SQL Servers and their databases from a central console. You can use the SAP databasemonitor transactions to point at remote SAP systems of a different release than the local SAP system.There are no restrictions with respect to the remote database. It can belong to an ABAP-based SAPsystem, a JAVA-based SAP system or a non-SAP application.

Integration

Remote DB Monitoring mainly uses the CCMS interfaces to display the data. SMD as a system isheavily integrated with CCMS for gathering such monitoring data. More information on this topic canbe referred from http://help.sap.com,under topic Database Administration in CCMS.

Prerequisites

For more information also refer to the Solution Manager Diagnostics setup guide. The setup guide canbe downloaded from the SAP Service Market place (http://service.sap.com/ ) under aliasdiagnostics.

Activity

1. Under the Monitoring tab, in the Detailed Navigation Panel

2. Select Remote Database Monitoring

3. On the display to the right, the DB SID and Monitored System details are displayed.Select the DB SID for which you wish to see the data for.


14/60

SAP J2EE SQL Monitoring

Use

SQL Monitoring is used to perform SQL Trace and view other monitoring boards for further SQL

analysis. This is meant only for 6.40 systems.

Activity

1. Select SAP J2EE SQL Monitoring from the Detailed Navigation Panel.

2. The display area to the right opens the SAP J2EE Engine Open SQL Monitors page

3. Follow the detailed procedure under heading Features of the topic Open SQL Monitoring toperform SQL Trace. The same section also has links to the SQL Monitors and their respectivedescriptions.

More information on this topic can be referred from http://help.sap.com,under topic Open SQLMonitoring.


15/60

SQL Command Console

Use

SQL Command Console is a monitoring tool for Solution Manager Diagnostics. Using this tool

database tables can be viewed through SMD interface without accessing the Database itself. It helpsto browse around Database installations and run selected read-only queries on the monitoredsystems.

Integration

The SQL Command Console uses the SMD Agent connection to retrieve data from remote database.It relies on the SMD Agent configuration to perform such actions. The steps needed for theconfiguration are described in the Solution Manager Diagnostics setup guide.

Prerequisites

For more information also refer to the Solution Manager Diagnostics setup guide. The setup guide can

be downloaded from the SAP Service Market place (http://service.sap.com/ ) under aliasdiagnostics.

Features

SQL Browser is a very efficient tool to access tables and run selected queries on the databasesrunning on a monitored system through a common interface. It has the following features:

1. View table details and its content

2. Run SQL queries, only select statements can be run

Activities

1. In the Solution Manager Diagnostics window select Monitoring Database SQL CommandConsole

2. Choose the appropriate Database Source from the drop down list to select the database that canbe viewed through SQL Command Console.

3. It pulls up information about the following Database properties, this information cannot be changed

JDBC Native URL

Product Name

Product Version

Driver Name

Driver Version

4. SQL Command Console provides two main functionalities

a. View Table Structure and records Selection

b. Execute SQL Query to get desired results SQL Query

Selection

Use

In SQL Browser Database tables for databases on monitored systems for SMD can be viewed directly.Both columns and records of the database sources can be returned through this interface


16/60

Structure: Selection


Table name Name of the Database Table to be browsed

Apply Verify the table name and populate the columns of that table

Columns Columns of the Table

Fields

Column Type

Selected

Page size The number of records to display for the table

Execute To retrieve data from selected columns for the table

Procedure

1. Once the appropriate Database source has been selected, the tables from that database can beviewed through SQL browser.

2. Select the table name to be browsed in the Table Name field and hit Apply.

3. The columns of the table are populated in table grid on this screen with information about fields,column type and selected from the database table directly

4. There is a possibility to filter the maximum number of displayed records.

5. On clicking Execute button the query results on this database table are displayed in a separate

table grid returning the number of columns desired with the fields selected to be browsed.

6. The Query Results from the table can be customized to select the columns to be displayed

7. The Query Results table grid also has a search functionality with which search can be performedon available columns using a regular pattern. On clicking at search a new dialog box opens upand searches can be done to find data especially if the table has a large number of records.

SQL Query

Use

In SQL Command console tables for databases on monitored systems for SMD can be vieweddirectly. Using SQL Query functionality of SQL Command Console SQL queries can be made directly

through SMD interface to the Database and the results can be viewed through the same interface.

Procedure

1. Once the appropriate Database source has been selected the SQL queries can be run to thatdatabase directly from SMD interface. Only Select statements can be executed.

2. Put the appropriate select statement in the SQL Query window.

3. There is a possibility to filter the maximum number of displayed records.

4. On clicking Execute button the query results by running this SQL query are displayed in aseparate table grid.

5. The Query Results from the table can be customized to select the columns to be displayed

6. The Query Results table grid also has a search functionality with which search can be performedon available columns using a regular pattern. On clicking at search a new dialog box opens upand searches can be done to find data especially if the table has a large number of records.


17/60

LOGS AND TRACES

Log Display

Use

A Consolidated display to check the status of logs and its levels. The Log Configuration Displayenables you to see the most important log configuration information of all server nodes of an entirecluster for the Portal Platform, SAP J2EE Engine, CM, Collaboration and TREX.

Provides an easy navigation capability of different entry points of the Log configuration. Also enablesanalysis of the files via the appropriate Viewer

Activities

1. Navigate under the Monitoring Tab of the SMD application.

2. Select Log Display in the Detailed Navigation panel under Logs and Traces.3. In the Display to the right the Log Display Interface is shown.

4. The Log Display interface is divided into two parts

Log Configuration Area

File Navigation Area

Log Configuration Area

Use

This area can be used to select the log files in different aspects for display. The different categoriesunder which the log files can be viewed are mentioned in the structure section.

Integration

Logs are normally written to categories and traces are normally written to locations. SAP J2EE loggingis structured around categories. The logging and tracing concept is divided into CategoriesandLocations. Categories contain log information for the system administrator and are used to check thesystem status. Locations contain trace information that is intended for the developer. They are used tohelp check the program flow and to detect program errors.

Information on this topic can be referred from the Administration Manual of SAP Web ApplicationServer. SAP J2EE Logging can be reached via Server AdministrationLogging

StructureTitle Description And Usage

Search Performs a search in the list of log files based on the search string.

Log-File-Names List of Logical Files Names based on J2EE-Destination Pattern.

Ex: defaultTrace.*.trc

Log-Directories List of known directories where the logs reside

Logical Logs J2EE Categories

Logical Traces J2EE Locations

Logical Destination J2EE Destination: Logical destinations of log files.

(Some entries are mapped to the SAP J2EE Visual Administration View of the Log ConfiguratorService)


18/60

Procedure

Perform Search in the Log Configuration Area

1. Select the tab strip where you want to search in "Log Configuration Area".

2. Enable the focus in the first row of the table.

3. Enter the String to be searched: letters (i.e. log) or a regular expression (i.e. l*)

4. If there is more than one row that contains the search string, a + sign is added to the icon

5. After a click on the icon, the focus is set to the next row that contains the text

6. Each time the focus is set on a row in "Log Configuration Area", the details of the selected row is

displayed in the "File Configuration Area" zone.

Difference in a 6.20 installed system

1. The first two tab strips have the same content as in a 6.40 system.

2. For the other tab strips: each component is displayed into a tab strip: only SAPJ2EE, Portal and

KM has dedicated tab strips.

3. For another component type (i.e. MDM), the log and trace files will be visible in the first two tabstrips.

4. If only the J2ee Engine is installed, only 3 tab strips are enabled. The third tab strip will contain the

loggers for the engine.

File Navigation Area

Use

This area is used to navigate to different files, based on the selection made in the Log ConfigurationArea. In this area the file can be viewed and downloaded in text format.

Structure


Landscape This column lists the directories and files based on the selection in LogConfiguration Area.

File Size Size of the files under a selected directory

Date Modified The Date on which the files were modified

Procedure

1. Select the file from the column Landscape (First Column).

2. The file will be opened in a new window for viewing and downloading.


19/60

Log Viewer

Use

The Log Viewer displays various log files of monitored solution landscapes.

Features

The Log Viewer can display structured and unstructured logs. Structured logs are created by the SAPWebAS with header information and delimiters. This allows the Log Viewer to recognize fields of thelog records, and thus allows filtering and searching of log records based on field content. Unstruc-tured logs do not contain header information and delimiters; each line is treated as a record.

The Log Viewer allows the user to filter which logs are displayed based on the log name and type.Optionally, multiple physical logs may be merged into a single, virtual log for display (for example, tomerge logs from all the nodes of a SAP J2EE cluster). Filters may be saved for reuse (a view).

If a log is structured, the user may choose which fields to display, and in which order. Logs may bedownloaded to the users desktop. Logs may be searched by field.

Prerequisites

The following configuration parameters may be set in Solution Manager Diagnostics Administration(Agent Administration Applications Configuration Agent Applications Configurationcom.sap.smd.agent.application.logviewer):

Name Description Default Value

Logviewer_NI_port the port of the Standalone LogViewer server

2600 (If this port is already used on themonitored machines, the agent willincrement this number to find a freeport.)

default.log.pattern registered log files, that is, thosewhich are recognized by theStandalone Log Viewer server

*.log,*.trc,*.out

Integration

An agent application named com.sap.smd.agent.application.logviewer packages the Standalone LogViewer server. When this agent is started by the SMD agent infrastructure, the SLV server isdeployed and started.

Structure

Connection Information

Example: One active connection on host name: napalepdev001, port: 26001

Purpose: Shows all connections to all hosts of monitored system.

Use selected host from navigation bar checkbox

Example: Use selected host from navigation bar

Purpose: If checked, only logs from the selected host will be available for display. If not checked,logs from all hosts in the cluster will be available for display.


20/60

View Type drop-down list

One of: Custom View, Predefined View, Recently Used View

Custom View: A view which has been created and saved using Open Filter. Note: Thecustom view Log and trace files is available by default.

Predefined View: Solution Manager built-in views. Note: The predefined view StandaloneLogViewer requires a connection to a running Standalone Log Viewer server on the monitoredhost.

Recently Used View: A shortcut to recently used Custom and Predefined views.

View Name drop-down list

Content: The name of the Custom, Predefined or Recently Used view. The view determines whichlogs will be available for display (by log name, type and/or content).

Open Filterbutton

Purpose: Allows the creation, change and deletion of views. A view is a filter which determineswhich logs and content of logs will be displayed. Views can be based on the name of the log, the type

of log (ListLog or TextFormat) or the content of the log.The following elements appear whenOpen Filter is selected:

Set as Default View button

Purpose: Sets this custom view as the default view when the Log Viewer application is started.

Save View button

Purpose: Saves changes for the current view.

Save View As ... button

Purpose: Saves changes as a new view.

Reset Viewbutton

Purpose: Resets view to last saved version.

Delete View button

Purpose: Deletes current view.

Refreshbutton

Purpose: Reloads the current view. Equivalent to Apply Logs plus Apply Filters.

Log Browser

Purpose: Determines which logs are available for display, based on the name of the log (file)and the type of the log file. The name of the log file may include the * wildcard (for example,DefaultTrace*). The type of the log file may be ListLog or TextFormat.

Note: The filter is not case-sensitive.

Apply Logs

Purpose: Applies changes made in the Log Browser section, thus making a new log (file) listavailable in the Display Log File drop-down.

Merge Logs If Possible checkbox

Purpose: If checked, the contents of logs from locations (i.e., Host and Path) will be merged,thus creating a single, virtual log.

Example: A Log Browser filter of Log file named as DefaultTrace* with Merge Logs IfPossible would display all default trace files on all nodes (dispatcher and server) of the cluster as

if they were a single log.Filter by Content

Purpose: Determines lines or records of the selected log is displayed.


21/60

Example: A Filter by Content filter of Message contains error would display only lines orrecords where the Message includes the string error.

Note: The filter is not case-sensitive.

Apply Filtersbutton

Purpose: Applies changes made in the Filter by Content section, thus refreshing the display oflines or records in the Display Log File section.

Close Filterbutton

Purpose: Closes the filter and its elements (above).

Display Log File drop-down list

Purpose: Allows the user to choose which log (file) is displayed. The logs available in the listdepends on the current view (see above).

Note: If Merge Logs If Possible is selected and logs can in fact be merged, then all the merged logswill appear as a single virtual log named * Merged SAP Logs.

From drop-down list

Purpose: If the same log is available in multiple locations, the user may choose among thelocations.

Example: defaultTrace.0.trc may be available on all dispatcher and server nodes.

Open Log Detailsbutton

Purpose: Displays the properties (such as location, modification time, etc.) of each log included inthe current view. You may then select a log and expand the More Details tray, or Close the dialog.

Open Column Customization button

Purpose: Determines which fields of the log are displayed, as well as the order in which they aredisplayed.

Note: Appears only if the log is structured (i.e., its field names are recognized).defaultTrace.*.trc is an example of a structured log. std_bootstrap.out is an example of anunstructured log.

Close Column Customization button

Purpose: Closes Column Customization dialog (above).

Open Record Details button

Purpose: Shows details of the selected record.

Note: Appears only if the log is structured (i.e., its field names are recognized).defaultTrace.*.trc is an example of a structured log. std_bootstrap.out is an example of anunstructured log.

Close Record Detailsbutton

Purpose: Close the record details (above).

Open Full Record Information button

Purpose: Shows full record (all fields).

Note: Appears only when Open Record Details is selected (above).

Close Full Record Information button

Purpose: Close the full record information (above).

Download Content button

Purpose: Downloads the log to a file on the users desktop.

Note: There are two steps to the download: (1) Extraction, which begins automatically, and (2)File Download, when the user may select Save and choose the target file location. If the log isstructured, the files records are comma-delimited.


22/60

Open Search button

Purpose: Searches the log for the next matching value.

The following elements appear whenOpen Search is selected:

Search By drop-down list

Purpose: If the log is structured, the Search By drop-down will show all the searchable fields. Ifthe log is unstructured, each line is treated as a record with a single field, Message.

Operator drop-down list

Purpose: Determines if the search will include (contains) or exclude (does not contain) allmatching records. The * wildcard may be used.

Go to Next Record button

Purpose: Display the next matching record.

Example: In a time-sorted log with the latest entries at the beginning, the display advances upto the next later record.

Go to Previous Record button

Example: In a time-sorted log with the latest entries at the beginning, the display advancesdown to the next earlier record.

Close Search button

Purpose: Closes the search dialog (above).

button

Purpose: Go to first page.

button

Purpose: Go to previous page.

button

Purpose: Go up one record.

button

Purpose: Go down one record.

button

Purpose: Go to next page.

button

Purpose: Go to last page.


23/60

OPERATING SYSTEM

File System Browser

UseThe File System Browser is used to browse, format and download files from the monitored NWinstance. The browser supports some predefined indexes for the Main Instance (J2EE/ABAP), LocalRoots and aliases. Hence, browsing can be performed extensively without the file system access.

Prerequisites

Solution Manager Diagnostics should be installed and configured. Please refer to the SolutionManager Diagnostics setup guide for more information on prerequisites. The setup guide can bedownloaded from the SAP Service Marketplace (http://service.sap.com) under alias diagnostics.

Features

1. Access to the file system of the monitored hosts.

2. View, format and download files from the monitored hosts.

3. Access the file system quickly and efficiently using Aliases and shortcuts depending on thetype of NetWeaver component installed in the monitored hosts.

Activities

5. In the Monitoring Tab of the SMD front application.

6. Select File System Browser in the Detailed Navigation panel under Operating System.

7. In the Display to the right the File System Browser is displayed.8. The File System Browser is divided into two parts

Entry Points

File System

Entry Points

Use

The Entry Points interface displays predefined indexes to important files system paths for browsing.These indexes can be selected to browse the displayed path.

Structure


Main Instances This tab lists indexes which are filled in directly from the database.These indexes depend upon the installation of the monitored system,i.e. an NW instance with Java Stack only, with ABAP Stack only, orboth. The tab displays the following columns

Name: Name of the instance, e.g. Enterprise Portal, dispatcher,server0 etc...

Type: The type of instance, e.g. Main Instance, Portal PlatformInstance etc

Path: The Path of the instance in the file system.


24/60

Local Roots This tab lists the local root directories which need to be browsed; thisinformation comes the SMD Agent application configuration asdescribed in the SMD setup guide.

Aliases This tab lists the aliases for all the important individual files and

directories. The aliases are predefined and come from the componentanalyzer files.

Procedure

1. In each of these tabs, select the Instance, Root Path or the Alias to view the files.

2. The selected path displayed below in the File System as a tree structure.

File System

Use

The File System console is used to browse, view, and format and download files based on theselection made in the Entry Points.

Structure


Selection The first column is used for selection

Landscape This column displays the paths based on the selection. It displays thealiases, files system paths to be browsed.

Opens the selected File in a new window

Enables Downloading the selected file.

Date Modified The date on which the file or directory was modified

Size Size of the files. Every directory is indicated with a zero value.

Procedure

1. Use the selection column to select a path. Once the required file is identified.

2. Use , to open the file in a separate window

You can use the window to Download the file using the icon or

Format the log file

3. Formatting depends on the source engine of the files,

On a 6.20 engine, log formatters cannot be automatically determined (There is noheader indicating the formatter in the log file); this is the reason why the formatterbutton and dropdown list appear. The options of formatters which appear in the dropdown are :

On a 6.40 engines, log formatter can be automatically identified from the header of thelog files.


25/60

If you download a log-file from the Display view, it will either formatted or not(depending on if you have pressed the format button or not).


26/60

OS Command

Use

OS and process level information is vital for troubleshooting and monitoring purposes. Hence, SAP

introduces an OS Command interface as a part of the Solution Manager Diagnostics. With thisapplication, support activities do not require access to the customer system.

This interface is used to issue OS level commands and maintain a history of those commands. TheOS Command interface is an embedded GUI which simulates the OS Command prompt.

Features

1. Access to OS level information without logging into the actual system.

2. Commands can be of both System and Network type.

3. Parameters can be passed with the command for more filtered data.

4. A history for the issued command can be maintained.

5. A command or the whole history of commands issued, can be downloaded as an excel file.

Activities

9. In the Monitoring Tab of the SMD front end.

10. Select OS Command in the Detailed Navigation panel under Operating System.

11. In the Display to the right the OS Command Interface is displayed.

12. The OS Command interface is divided into two parts

OS Command History

OS Command Prompt

OS Command History

Use

OS Command History interface is used for maintaining and recording command history.

Structure


OS CommandHistory

The grid is used to display all the previously issued commands. The gridis split into separate columns

Command: Lists issued commands in the order of most recent first.

Hostname: System name on which the command

was issued.

Group: Command belongs toSystem or Network

Parameters: Parameters for the command

Time: Time of issue

Total Time: Total time taken complete the execution

of the command

Remote Time: Total time taken for the command to execute in the remote

system. Code: Return Code of the command

green = successful, red = unsuccessful


27/60

Delete Command The button is used to delete the selected command

Clear History This button is used to clear the history of commands

Export Command The selected command can be exported as an excel file

Export History The history of commands can be exported as an excel file

OS Command Prompt

Use

The OS Command prompt interface enables us to issue OS level commands without any OS levelaccess. The results of the command can be viewed in the same display panel.

Structure

Title Description And UsageSend Command Equivalent of the Enter Command in an actual OS level command

prompt. Submitting the command for execution.

Hostname Select the host name on which the command needs to be executed.

Group Select the group to which the command belongs.

SYSTEM or NETWORK

Command Select the command.

The commands available in the drop down are System dependent.

For example, when the OS of the monitored host is Windows andthe group selected is NETWORK the commands in the drop down

are IPConfig, NetStat, Ping and Tracert.

If the group selected is SYSTEM the commands in the drop downis takslist

Parameters Specify additional parameters for the selected command. When thecommand does not need additional parameter, this field is noteditable.

Result View the result after executing the command or pressing the SendCommand button.


28/60

Remote OS Monitoring

Use

The operating system monitor can be used to monitor the system resources that the operating system

provides.

The collector SAPOSCOL collects these resources and are centralized by the CCMS monitoringinfrastructure in the ABAP stack. The OS07 transaction allows to display the monitoring information.

Integration

All CCMS agents can copy data from the SAPOSCOL shared memory segment to the CCMSmonitoring segment and transfer it to a central monitoring system. This means that the data is visiblein the CCMS monitoring architecture and is displayed both in the familiar transactions ST06 and OS07and in the Alert Monitor (transaction RZ20). In this way, you can monitor the operating system data forhosts without a running SAP Basis system

Related information can be referred from http://help.sap.comwebsite under topic OperatingSystem Monitor.

Prerequisites

SAPOSCOL must be running in monitoring and monitored systems so that the data is available. Formore information also refer to the Solution Manager Diagnostics setup guide. The setup guide can bedownloaded from the SAP Service Marketplace (http://service.sap.com/ ) under alias diagnostics.

Features

Using SMDs remote OS Monitoring (transaction ST06), you can monitor the following objects:

CPU Memory Swap Disk With Highest Response Time

LAN

Recommendations for an EP 6.0 System:

Total CPU time (User + system (kernel) time) 85%

User time related to System Time System time


29/60

Activity


2. Select Remote OS Monitoring

3. On the display to the right, OS Monitor is opened displaying the OS Parameters. (Transaction

Os07)


30/60

J2EE Command Console

Use

This feature enables the user to issue SAP J2EE commands and retrieve results without directly

accessing the operating system. The interface makes a telnet connection to the system which needsto be monitored.

Prerequisites

The monitored system has to be configured to list the available dispatchers, and should have thetelnet service enabled.

Structure


Available Dispatcher Lists the dispatcher on the selected system

Connect This button is used to make a telnet connection with the monitoredsystem. Select a dispatcher before using this button.

Disconnect Disconnects the existing session or the telnet connection with thedispatcher

Clear Console Clears the console (Session History)

Session History Maintains the history of all commands issued per session

Command This textbox is used to type a valid SAP J2EE Command. Refer to theSAP J2EEShell Administration Commands.

Execute Used to execute commands

Next Command, in the list of commands issued

Restores the last command executed

No Title Displays result of the current command executed.

Activity

1. In the Monitoring Tab of the SMD front end.

2. Select SAP J2EE Telnet Console in the Detailed Navigation panel under Operating System.

3. In the Display to the right the J2EE Console is displayed.


31/60

PERFORMANCE

HTTP Analysis

UseHTTP Analysis Monitor is used to monitor the HTTP requests sent by the client to the server and theHTTP responses returned from server to client, as well as client side rendering activities. The userinterface of HTTP Analysis displays detailed performance-related information graphically.

Prerequisites

User must have Microsoft Internet Explorer 6.0 or higher installed. In order to start the HTTP Analysis,the user must also download the HTTP Plug-in. SAP always recommends using HTTP 1.1 or HTTP1.0 with Keep-Alive if possible. SAP strongly recommends activating browser caching.

Features

Using SMDs HTTP Analysis, you can see all the requests triggered by a simple click.

You can also see from the requests the duration between sending the first byte of the requestuntil having received the last byte of the response.

For each request you can see how many bytes have been sent from the client to the serverand from the server to the client

For each transaction you can see the total number of bytes that have been sent and receivedby the client

o This feature can help to unmask requests that consume much network resources

o Check file sizes of CSS and Java Script files

o Check file size of images

o Check if heavy weight requests are (can be) cached

o If you know the bandwidth you can calculate the minimal possible response time foreach transaction

Activity


2. Select HTTP Analysis

3. On the first use of the HTTP Analysis, you need to install the analysis plugin

Please click on Download Plug-In.

Please choose Save in the File Download Pop Up.

Create a folder Analyzer on your local desktop, save the file HttpProxy.zip to thisfolder.

Unzip the HttpProxy.zip file to this folder

4. Run the IE gui program located in the installation folder of the HTTP plugin.

5. The program will open a new browser window with a deactivated Http Proxy plugin visible.

6. Navigate in the browser to the analyzing target (in case of a portal, enter your credentials),type a name for this specific Http test in the Plug In window and press Instrument

7. Perform any actions on this page that you would like analyzed.

8. When finished click De Instrument in the Plug In to stop the analysis.

9. Now type a name for the second Http Trace in the Plug In and click Instrument.


32/60

10. Navigate to the second page you would like analyzed and perform any actions needed.

11. When finished click De Instrument in the Plug In to stop the analysis.

12. To load the analysis results please navigate to the Http Analysis functionality of your SMDapplication and click on Browse of the Add a new transaction section.

13. Navigate to the folder where your Http Proxy installation is located and to the subdirectorylogs. Here you will find two folders with a time and date stamp in their name. Open the firstfolder and select the report.xml file, then click open to upload this file. Please upload thereport.xml file from your second trace in the same fashion.

14. Please analyze the transactions by selecting the transaction name and pressing the Displaybutton afterwards.

Structure


Transaction overview Choose a transaction to either show its statistics by clickingthe Display button or deleting an existing transaction bypressing the Delete button.

Add new transaction To add new transactions, upload a report.xml file.

Download PlugIn To download the browser plug-in.

Upload HTTPINFO.log/responses.X.trcfile

To load the http analysis server side log. Please refer to theSMD setup guide for more information

Results

When the analysis is completed a screen will be displayed with the following sections


Overview This tab contains some statistical data about the tracedtransaction. This helps determine which component isresponsible for poor performance.

There are several tables contained on this page:

TransactionDetails

Transaction name, start date, SAP J2EE Node ID, SAP J2EEHost, Transaction Duration

Times(accumulated)

Preprocessing time, Network time, Server time, Renderingtime

Http Status Codes Status Code type and occurrences

Request Summary Time to first request, Rendering time after last request,osBytes, scBytes, Number of requests

Request Table This tab provides you with detailed performance measurementdata for each single request. It is easy to identify themostexpensive request here.

These columns are contained in the table:

cPT ... Client Processing Time before request has been sent

cResT ... Client Response Time (Http Request)sRT ... Server Response Time (Web Container)


33/60

cRenT ... Client rendering timecsBytes ... Bytes sent from client to server

scBytes ... Bytes sent from server to client

Request Graphics This tab displays a graphical overview of each requests

Summary

An analysis of the HTTP protocol stream between client (browser) and server can help to reveal thefollowing information:

Number of requests that are sent when the user performs actions in the Web Application (e.g.the Enterprise Portal)

Number of physical connections that are established between client and server

Amount of data that is sent from the client and received from the server

Response times of each request

Type of content that is requested by the client (e.g. HTML, JavaScript, CSS, JPG, GIF etc.)

Return codes that are sent by the server


34/60

J2EE Server Analysis

Use

You want to analyze performance or memory problems in a Java application, SMDs J2EE Server

Analysis tool monitors J2EE applications on code level (e.g. average response time of a certainmethod), provide historical performance data, and correlate with OS performance counters (e.g. FileI/O, Socket I/O, GC runs).

Integration

This SMD functionality uses the Wily Introscope tool in order to monitor and analyze Java applicationsrunning on SAP NetWeaver installation.

Prerequisites You must have the Wily Introscope tool installed. Please refer to SAP Note 797147 for

download and detailed instructions.

o Note: Wilytech Introscope as shipped with SAP NetWeaver is only licensed for use bySAP employees. It will be used to analyze Java performance problems efficiently.Customers are not entitled to use this version of Introscope. If you are interested inusing it as a customer, please open a message on component XX-PART-WILY.

o Setup guide for Introscope 5.3 SAP End User Edition, available on the SAP ServiceMarketplace:

http://service.sap.com/swdc -> Download -> SAP Support Packages -> Entryby Application Group; navigate to SAP NetWeaver -> SAP NETWEAVER ->SAP NETWEAVER 04 -> Entry by component -> Central Admin -> WILYINTROSCOPE AGENT 5.3 -> #OS independent. The file SAPISDOC53.PDFcontains the setup guide.

FeaturesIntroscope is a system management application created to help manage Java Applicationperformance. Unlike development tools, Introscope is designed to scale with minimal performanceimpact. This allows you to monitor and manage your application performance in live productionenvironments.

Activities

1. Under Detailed Navigation and Performance please select J2EE Server Analysis. This willlaunch the Wily Introscope tool.

2. After logging into Introscope please refer to the End User document for Wily Introscope.


35/60

Java Web DynPro Monitoring

Use

Web DynPro Monitoring, monitors WebDynpro runtime including information like usage data (e.g.

users), deployed WebDynpro applications, JARM based performance data and WebDynproconfiguration data.

Integration

Java Web DynPro Monitoring mainly uses the WebDynPro Console to display the data. Information onthis topic can be referred from the Administration Manualof SAP Web Application Server.Administration/Configuration of Web Dynpro Runtime Environmentcan be reached via

Server AdministrationAdministration/Configuration of Web Dynpro Runtime Environment

Activity


2. Select Java Web DynPro Monitoring under Performance

3. The Web DynPro Console opens in a new window.


36/60

STATUS

J2EE System Information

UseSAP J2EE System information provides administrators with an overview of the system configurationand its state. It shows all of the system's instances and processes, their current state and importantparameters (such as ports) that may be required for support cases, as well as the versions of thecomponents installed.

Integration

SAP J2EE systems information is a part of Web application server and is directly integrated intoSolution Manager Diagnostics through the WebAS.

Features

SAP J2EE systems information can capture the following information from a single interface.

1. Message Server, Enqueue Server and Database this information is pulled from the SAP J2EEengine

2. The all components link pulls down information about your loaded packages. This informationcan be used to troubleshoot problems relating to outdated packages.

3. The Download system configuration link retrieves a series of files in zip format which containconfiguration data of your system.

Related information can be referred from http://help.sap.comwebsite under topic SAP J2EESystem Information.

Procedure


2. Select SAP J2EE Systems Information under Status group

3. A new window opens and the SAP J2EE System Information is pulled directly from theWebAS of the landscape that is currently monitored through SMD


37/60

Systems Landscape Directory

Use

In a complex landscape environment there are usually a large number of hardware and software

components that depend on each other with regard to installation, software updates, and demands oninterfaces. The SAP System Landscape Directory (SLD) simplifies the administration of a systemlandscape by providing information about all SAP software modules in landscape. SLD represents anexact model of actual system landscape.

Integration

System Landscape Directory is a part of Web application server and is directly integrated into SolutionManager Diagnostics through the WebAS.

Features

The system landscape directory provides information about the following:

1. Systems and system topology

2. Component structures

3. Component information of the installed software

Related information can be referred from http://help.sap.comwebsite under topic SystemsLandscape Directory.

Procedure


2. Select System Landscape Directory under Status group

3. A new window opens and the System Landscape Directory is pulled directly from the WebASof the landscape that is currently monitored through SMD


38/60

USAGE STATISTICS

Portal Activity Report

UseThe Portal Activity Report of Solution Manager Diagnostics displays information about Users activitiesin the Portal of the Monitored systems.

It displays display information, such as, the number of users that logged onto the portal in a givenperiod of time, and the number of times the logged on users requested a page, or an iView.

In addition, parameters can be defined to filter the report and produce precise details about the use ofa specific page, or iView.

Integration

Portal activity tracing for all or given users is also available in the Log Viewer section of the J2EEVisual Administrator. The Visual Administrator is available in GUI form whereas the SMD is available

via HTTP.

More information on this topic can be referred from http://help.sap.com,under topic Portal ActivityReporting.

Features

This is the SMD application that renders a report about the number of users that logged onto the portalin a given period of time, and the number of times the logged on users requested a page, or an iView.

Activities

1. Navigate to the Reporting Tab of the SMD front end

2. Select Portal Activity Report in the Detailed Navigation under Usage Statistics3. In the Display to the right, the reporting options will be displayed

4. Configure the report by defining values for the parameters:

Structure


Type User, iView, Page

- Defines whether to generate a report about logged on users, orabout the use of pages and iViews.

Aggregation Level Hour, Day, Month, Quarterly

- Defines the frequency period for the report.

From

To

(YYYYMMDD HH)

- Specifies the date on which to begin and end the statistics for thereport.

Result

You have created a portal activity report that provides the following:

Information about the number of users that are logged on to the portal Information about the number of pages and iViews used by the logged on users

The option to save the contents of the report in a comma separated values (*.csv) file.


39/60

CONFIGURATION AND FILE MANAGEMENT

Configuration and File Reporting

UseThe Solution Manager Diagnostic application provides with the Configuration and File Reporting acentral view of the configuration data for each component as well as the history of changes made. Theconfiguration reporting collects the configuration settings for all non-ABAP components in thecustomer solution and provides navigation via landscape trees to each configuration setting within theSolution Manager Diagnostics.

Features1. A history of changes is provided per single configuration setting (based on daily snapshots).

2. In addition it is possible to display the configuration as it existed for a given point in time.

3. It also allows comparing the configuration settings between two components within any landscape,each at any given point in time. As a result all the differences are highlighted.

Activities

1. In the Reporting Tab of the SMD front end.

2. Select Configuration and File Reporting in the Detailed Navigation panel underConfiguration and File Management.

3. In the Display to the right the Configuration and File Reporting Interface is displayed.

4. The Configuration and File Reporting interface is divided into two parts

Configuration Reporting

o Configuration Change Reporting

o View Configuration

File Version Reporting


View File Versions

Configuration Change Reporting

Use

This tab enables you to select options to report configuration changes within the same landscape orbetween two different landscapes based on respective timestamps. This tab is also used to selectoptions to load parameters of one of the landscapes of a point in time.

Structure


Timestamp Used to select a date and time for the current landscape as displayedabove. The date and time stamps stored are when the changes weremade.

Mark Changes in

History

Checkbox used to indicate the changes in the history, which will be

displayed in the View ConfigurationLoad Used to display the parameters of the current landscape

Landscape2 Used to select the same or different landscape for comparison.


40/60

Timestamp2 Used to select a date and time for the same or different landscape forcomparison. The date and time stamps stored are when the changes weremade.

Select For Compare Initiate Comparison, and display report in the Compare Landscapeswindow.

Procedure

1. To display configuration changes of a landscape.

Select a date and time from the Timestamp dropdown menu.

Check Mark Changes in History in case you wish to see the report indicating the changes.

Click the load button to generate the report.

The report is displayed in the View Configuration window

2. To compare changes between landscapes.

Select a date and time from the Timestamp dropdown menu for the current landscape

Select the same landscape or a different one from the Landscape2 dropdown menu.

Select a date and time from the Timestamp2 dropdown menu for the landscape inLandscape2.

Click the Select for Compare button to generate a report with the comparison.

The report is displayed in the Compare Landscapes window.

View Configuration

Use

This panel displays change configuration files and parameters based on the selection made in theConfiguration Change Reporting tab.

Structure


Filter Filter the displayed configuration stores. This button opens anotherwindow to fill in the filter options.

Search Searches for a String in the tree, from the starting node

Prepare Download Data Prepares download data either for the displayed tree or the entire tree,based on the Entire Tree checkbox selection.

Download The link is used to download the data as a file, use the PrepareDownload Data button before downloading.

Landscape Displays the tree and its child nodes below

Type The type of file or directory.E.g. Properties, Dispatcher etc

Date Date when the file or directory is viewed.

Alias Matching alias for a specific file. E.g. J2EE, Http Provider etc

This icon represents the fact that the particular config store has some

history, it has been changed earlier.


41/60

Structure for Filter in View Configuration Display


AliasFor easier recognition and search capabilities it is possible to define goodunderstandable alias names for single config store elements. The idea isthat the information structure known from visual administrator shall beused to define those alias names.

The suggestion for the alias naming convention is: : [:]. Hence

Option 1 : Type

Option 2 : Element

Name Name of the Configstore(s)

Type Search by the type of Configstore, options are properties, xml or txt.

History If history is required and available

Has History Since Date and Time since history required.


42/60


Use

This tab enables you to select options to report file version changes of the SAP NetWeaver Javacomponents within the same landscape or between two different landscapes based on respectivetimestamps. The version of the file is taken from the manifest file of the jar files of the components.

This tab is also used to select options to load file versions of one of the landscapes of a point in time.

Structure


Timestamp Used to select a date and time for the current landscape as displayedabove.

Mark Changes inHistory

Checkbox used to indicate the changes in the history, which will bedisplayed in the View File Versions

Load Used to display the parameters of the current landscape

Landscape2 Used to select the same or different landscape for comparison.

Timestamp2 Used to select a date and time for the same or different landscape forcomparison

Select For Compare Initiate Comparison, and display report.

Procedure

1. To display file version changes of a landscape.

o Select a date and time from the Timestamp dropdown menu.

o Check Mark Changes in History in case you wish to see the report indicating thechanges.

o Click the load button to generate the report.

o The report is displayed in the View File Versions window

2. To compare file version changes between landscapes.

Select a date and time from the Timestamp dropdown menu for the currentlandscape

Select the same landscape or a different one from the Landscape2 dropdown

menu. Select a date and time from the Timestamp2 dropdown menu for the landscape in

Landscape2.

Click the Select for Compare button to generate a report with the comparison.

The report is displayed in the Compare Landscapes window.

3. To display and compare configuration changes of a specific parameter or property file.

Select the row indicator in the first column of the display, of the row which contains theproperty file which needs to be compared.

The selection above will open another window below with some more options. The optionsare Attribute History, Compare Elements, Show Deleted Items and Hide

Unchanged Items.

1. Attribute History: This button displays the history on the property selected, if theproperty was changed or unchanged.


43/60

2. Compare Elements: More than one property can be selected using the Control key ofyour keyboard. This button enables you to compare the properties between differentinstances, i.e. Server, Dispatcher.

3. Show Deleted Items: Checkbox when selected also shows deleted values.

4. Hide Unchanged Items: Checkbox when selected hides unchanged values.

View File Versions

Use

This panel displays change versions of files and parameters based on the selection made in the FileVersions Reporting tab.

Structure


Filter Filter the displayed version stores. This button opens another windowto fill in the filter options.

Search Searches for a String in the tree, from the starting node

Prepare Download Data Prepares download data either for the displayed tree or the entire tree,based on the Entire Tree checkbox selection.

Download The link is used to download the data as a file, use the PrepareDownload Data button before downloading.

Landscape Displays the tree and its child nodes below

Type The type of file or directory. E.g. jardll, Dispatcher etc

Date Date when the file or directory is viewed.

Structure for Filter in View File Versions Display


Name Name of the Configstore(s)

History If history is required

Has History Since Date and Time since history required.

Procedure

1. To display and compare version changes of a specific parameter or property file.

o Select the row indicator in the first column of the display, of the row which contains theproperty file which needs to be compared.

o The selection above will open another window below with some more options. Theoptions are Attribute History, Show Deleted Items and Hide UnchangedItems.

1. Attribute History: This button displays the history on the property selected, ifthe property was changed or unchanged.

2. Show Deleted Items: Checkbox when selected also shows deleted values.3. Hide Unchanged Items: Checkbox when selected hides unchanged values.


44/60

Compare File Versions

UseThis interface is used to compare file versions between two components within any landscape, each atany given point in time. As a result all the differences are highlighted.

Structure


Reset Refreshes and resets the display of the file system tree

Prepare Download Data This is used to download the version information into an excel file

This icon indicates difference of valuesThis icon indicates an additional value attached

This icon indicates a missing value

Activity

1. Select the entry from the Solution pull down menu in the popup windows.

2. Select the appropriate entry for Landscape in the pull down menu.

3. Select the appropriate landscape in the pull down menu Landscape2.

4. Choose the desired timestamp for the landscape2.

5. Click on Select for Compare button.

6. Choose one snapshot for Landscape 1 on left side, choose another snapshot for Landscape 2on right side, and then click on Compare button.

7. Expand the configuration hierarchy to compare the attribute values.

8. Click Quick Compare button to get a short and fast comparison between landscapes. Thisdoes not give full tree comparison of the selected snapshots.

9. The procedure for comparing two snapshots of the same landscape is similar as above.


45/60

Compare Landscapes

Use

This interface is used to compare configuration settings between two components within anylandscape, each at any given point in time. As a result all the differences are highlighted.

Structure


Reset Refreshes and resets the display of the file system tree

Prepare Download Data This is used to download the version information into an excel file

This icon indicates difference of values

This icon indicates an additional value attached

This icon indicates a missing value

Activity

1. Select the entry from the Solution pull down menu in the popup windows.

2. Select the appropriate entry for Landscape in the pull down menu.

3. Select the appropriate landscape in the pull down menu Landscape2.

4. Choose the desired timestamp for the landscape2.

5. Click on Select for Compare button.

6. Choose one snapshot for Landscape 1 on left side, choose another snapshot for Landscape 2on right side, and then click on Compare button.

7. Expand the configuration hierarchy to compare the attribute values.

8. Click Quick Compare button to get a short and fast comparison between landscapes. Thisdoes not give full tree comparison of the selected snapshots.

9. The procedure for comparing two snapshots of the same landscape is similar as above.


46/60

Comparing Multiple Instances

Use

Comparing multiple instances is a reporting functionality that is a part of Configuration and FileManagement. It is very useful for complex landscapes with multiple instances of applications, J2EEinstances. It compares multiple instances one at a time and points out discrepancies. Very often it hasbeen noted that in large installations with various instances there is a need to comparison to makesure the configuration data is consistent.

Features

It is now possible to compare multiple instances of applications through the Solution ManagerDiagnostics interface. This functionality can trigger a comparison between two similar instances ofapplications and keep record of that comparison for detailed analysis of inconsistencies.

Activities1. Select the reporting tab in the Solution Manager Diagnostics interface

2. Select Compare Multiple Instances functionality which is a part of Configuration and FileManagement reporting

3. In the display to the right the comparison of the multiple instances can be triggered and analyzed

4. To trigger a compare on multiple instances select Trigger Compare tab

5. To compare results on an already triggered compare between multiple instances select CompareResults tab

Comparing Multiple Nodes: Trigger Compare

Use

With Comparing Multiple Nodes interface users can trigger comparison between multiple nodes toeasily find out inconsistencies across landscapes. By comparing similar applications consistentinformation can be maintained very easily.

Structure


Select Choose the appropriate nodes for comparison

Hostname Hostname on which the nodes resideInstance Id ID for each instance

Instance Type Type of instance in a cluster (dispatcher, server.)

Main Reference node for comparison. One main must beselected for a comparison.

Import Date Date and time when data from the system was importedinto Solution Manager Diagnostics system

Procedure

1. Select the instance that will be the reference for comparison to other nodes by checking thecheck-box Main for that instance


47/60

2. Choose the node (preferably similar) that needs to be compared and the reference node in theSelect column.

3. The nodes are ready to be compared. Click the Trigger Compare button to schedule the compare.

4. A pop up window appears with Scheduler Informationfor scheduling the comparison betweenmultiple nodes. In this window, the comparison task will be scheduled to be run by the SMD

scheduler. The frequency of the comparison execution can also be changed in this window.5. Save the scheduling information for the comparison

6. The comparison between nodes is triggered in the background and results can be analyzedthrough Compare Results functionality

Comparing Multiple Nodes: Compare Results

Use

With Comparing Multiple Nodes interface users can trigger comparison between multiple nodes toeasily find out inconsistencies across landscapes. With Compare Results functionality comparisonruns that have already been completed can be analyzed for discrepancies.

Prerequisites

A successful comparison between multiple nodes has already been triggered.

Structure: List of Comparison Runs

The Compare Results screen initially opens up with a list of triggered runs


Creation Date Date/Time the comparison run was created

Execution Date Date/Time the comparison run was executedExecution Status Status of the comparison

RunId System Generated Id for the comparison run. Used forinternal reason.

Procedure

1. The Compare Results screen initially opens up with a list of triggered runs

2. Select the Comparison Run, which you want to review and click on Display button.

3. A new grid opens in the screen below the results with a status of the comparison run betweenmultiple nodes. It will indicate the status of the comparison and also lists the details of the

compared nodes with the following structure.

Structure: Compared System of Run

The Compared system of Run gives the overall status of the comparison for each node.


Compare status Status of the compare- The system compared has differences

- The system compared do not have any differences

Hostname The host to which the node belongs

Instance Id The reference node

Instance Type The reference node type (for example dispatcher, server)


48/60

Import Date The time and date when data relevant to the nodes was

imported into SMD

Main To track which one is the main node for comparison

Status The status of compare

4. For each node involved in the comparison, a comparison status is displayed. It indicates ifdifferences have been identified for the selected node compared to the reference node. Select theappropriate node run to analyze the results and click on the Display button.

5. A new grid interface opens in the same screen with details of this compare run.

6. For details about the comparison see the structure for Compare Results below

Structure: Compare Results

The Compare Results screen lists out the results of the compared run between multiple nodes


Comparison The property on which the comparison was made

Instance Id The reference node

Instance Id The compared node

The icons used in the report for comparison


Difference due to changes made in this instance

The line has been deleted from this instance or exists in other instance only

An additional line is added in this instance or the line already exists

Comparing Multiple Nodes: Scheduler Information

Use

The Scheduler Information while comparing multiple nodes sets up a schedule based on which thecomparison run is executed in Solution Manager Diagnostics

Prerequisites

Setting up scheduler information is used for setting up a schedule for comparing multiple nodes. Thenodes should be selected through Solution Manager Diagnostics interface. At one point only twonodes can be compared.

Structure

A brief overview of the interface components:


Name Name of the comparison task that will be scheduled

Description Brief Description of the comparison task

Execution Date Scheduled Date for triggering the comparison

Execution Time Scheduled Time for triggering the comparison

Frequency The execution frequency of the task. Possible values are:


49/60

Execute Once, Daily, Weekly, Monthly, Yearly, Custom

Custom Frequency The frequency of the execution in minute.

Only available if frequency is set to custom.

Trial The number of trial in case of failure of the execution.

Procedure

1. The scheduler information is needed when the comparison of multiple nodes has been triggeredby the user.

2. Put the information about scheduling the comparison trigger.

3. Save the information

4. The comparison of multiple nodes functionality will be triggered based on the schedulerinformation


50/60

SOFTWARE CHANGE REPORTING

Software Change Reporting

Use

Software change reporting is one of the reporting functionality for Solution Manager Diagnostics and isvery useful in identifying the current software release on a system and also track changes as theyoccur. It is also a very useful reporting tool to gather and display transport logs for Enterprise Portalcontent and packages deployed through Software Deployment Manager (SDM).

Software Change Reporting is very useful in large installations as it is possible that versions of the fileare not correctly deployed across the landscape due to which software conflicts can occur due tomismatched components.

Integration

The software change reporting integrated uses the Design Time Repository (DTR) to provide versioninformation for JAVA components along with central reporting features. Integration to ChangeManagement Server (CMS) server for various deployments is also accessible.

Prerequisites

Solutio

solmandiag guide sp15

Documents