SAP Solution Manager 7.

0 EhP1

End-to-End Diagnostics
Troubleshooting Guide
Configuration Validation
Version 2.0, December 2008
END-TO-END DIAGNOSTICS
TROUBLESHOOTING GUIDE
CONFIGURATION VALIDATION

Typographic Conventions Icons

Type Style Represents Icon Meaning
Example Words or characters quoted Caution
Text from the screen. These
include field names, screen Example
titles, pushbuttons labels,
menu names, menu paths,
and menu options. Note
Cross-references to other
documentation. Recommendation
Example Emphasized words or
text phrases in body text, graphic Syntax
titles, and table titles.
EXAMPLE Technical names of system
TEXT
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 Output on the screen. This
text 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 Exact user entry. These are
text words or characters that you
enter in the system exactly
as they appear in the
documentation.
<Example Variable user entry. Angle
text> brackets indicate that you
replace these words and
characters with appropriate
entries to make entries in the
system.
EXAMPLE Keys on the keyboard, for
TEXT example, F2 or ENTER.
 END-TO-END DIAGNOSTICS
TROUBLESHOOTING GUIDE
CONFIGURATION VALIDATION

Contents

1 Frequently asked questions ............................................................................................................... 4

1.1 Configuration Validation - detail analysis .................................................................................. 4
1.2 Configuration Validation - reference value ................................................................................ 5
1.3 Configuration Validation - Performance..................................................................................... 6
End-to-End Diagnostics 4
Troubleshooting Guide - Configuration Validation

1 Frequently asked questions

In this part you can find some solutions to potential issues and answers to frequently asked questions.

1.1 Configuration Validation - detail analysis

Q: The result area of the REFERENCE VALIDATION or the CUSTOM VALIDATION shows initially the
compliance information per system. One can expand the hierarchy nodes to see the configuration item value. Is
it possible to expand all nodes of the hierarchy in one step?
A: For this kind of report it was expected to have only few non compliant items and systems. If many non compliant
items are reported, it is helpful to expand all nodes of a hierarchy to the selected level defined in the query properties
dialog. After a right mouse click in the result area of the report the user can select the menu entry 'Query Properties' of
the context menu

to get the dialog:

SAP AG 2008
End-to-End Diagnostics 5
Troubleshooting Guide - Configuration Validation

Select 'Config. Item Value' as shown in the screen shot and get the hierarchy drilled down to this level after
confirming the dialog with 'Transfer'.

1.2 Configuration Validation - reference value

Q: In the Configuration Validation REFERENCE VALIDATION or the CUSTOM VALIDATION the
reference system and the reference values are not displayed. How can I get these values
A: In default, only data of the Comparison Systems is displayed as defined in the BI query. Data of the Reference
System is suppressed. The Reference System is displayed in addition after the suppression is removed by pressing the
trash icon for 'Compliance System' highlighted in the screen shot:

Alternatively the filter icon (cone) can be clicked and 'Reference System' selected instead or in addition of
'Comparison System'.

Q: In the Configuration Validation I use a target system as reference system, but the reports 'SOFTWARE
VALIDATION', 'SECURITY VALIDATION' 'DATA BASE VALIDATION' or 'BI VALIDATION' display 'No
Applicable Data Found.' for some categories, e.g. for the Profile Parameters.
How can I get the configuration items which are defined in the target system?
A: The mentioned reports show in some categories, e.g. Profile Parameters only the default values defined in the
queries. In fact also others items of the comparison systems are read, but most of them are suppressed. On the detail
tab page, e.g. for Profile Parameters this suppression is removed by pressing the trash icon for 'Compliance System'
highlighted in the screen shot:

SAP AG 2008
End-to-End Diagnostics 6
Troubleshooting Guide - Configuration Validation

Additionally the restriction on 'No' for 'Compliance' can be replaced by 'Yes' and 'No', if also the compliant values
should be displayed.

Q: Configuration Validation displays non compliant items for the ConfigStores 'GW_SECINFO',
'GW_REGINFO' or 'STANDARD_USERS'.
Where can I find more information about the content of these ConfigStores?
A: The meaning of the content of these ConfigStores is described in the SAP note 1234799.

1.3 Configuration Validation - Performance

Q: A report of the Configuration Validation ends in '500 Connection timed out', see screen shot. What can be
done to avoid this situation?

SAP AG 2008
End-to-End Diagnostics 7
Troubleshooting Guide - Configuration Validation

A: The time gap till a report is canceled because of a long runtime (Time out) is influenced
by the settings of the system (a). The overall runtime of the Configuration Validation is dependent on the number of
comparison systems selected by the query and the number of ConfigStores used for validation (b).
a) Check the Time Out parameters
Refer to the SAP Note 192658 and setup the parameters icm/server_port_<xx> and icm/keep_alive_timeout as
recommended per this note.

b) The number of comparison system can be easily influenced in the variable screen by selecting fewer systems. The
number von ConfigStores however can be influenced only for the REFERENCE VALIDATION or the CUSTOM
VALIDATION. The other reports use already only one ConfigStore for each query.
The CUSTOM VALIDATION report offers a free selection on ConfigStores. None, one or several ConfigStores can be
selected. If no ConfigStore is selected all ConfigStores of the Reference System will be read as no restriction is in
place. As default selection of ConfigStore 'SAP_KERNEL' is proposed. Another ConfigStore can be selected using the
'Selection' button.

For the ConfigStores 'ABAP_TRANSPORTS' and 'J2EE_TRANSPORTS' a Date Range should be entered, see screen
shot. Otherwise all transport requests applied or created in the system would be read and used for comparison.

The REFERENCE VALIDATION however reads all ConfigStores of the reference system. If a real existing system is
used as reference system normally lots of ConfigStores are involved. A report with real system as reference system is
only expected to have a short runtime, if a restricted number of comparison systems is used.
This report was designed however to use a target system. A target system is supposed to be defined to have a
restricted number of ConfigStores and items.
As we had expected that at least in some phases the definition of the target system is changed quite often, we did not
allow the relevant query 0SMD_VCA1/0SMD_VCA1_REF_CONFSTORES to use the OLAP cache. So the query is
forced to read of the most recent data.
You can enable the query for OLAP cache usage by changing the Cache Mode '0 Cache is Inactive' to another Cache
mode in the 'Property' dialog in Transaction RSRT. See also the documentation 'Cache Mode'
http://help.sap.com/saphelp_nw04/helpdata/en/d9/31363dc992752de10000000a114084/frameset.htm

For OLAP cache enabled queries the user can repeat the execution of the report with the same restrictions for the
variables 'Reference System', 'Comparison Systems', 'Config Store' and 'Transport Requests in Date Range' offered in

SAP AG 2008
End-to-End Diagnostics 8
Troubleshooting Guide - Configuration Validation

the variable screen. Other restrictions are not relevant for the usage of the OLAP cache as these are used as default
values.
For these queries the OLAP cache can be filled in background after the ConfigStores have been updated, e.g. at 5 a.m.
More information can be found in SAP Note 998680, attachment Automate-with-RSTT-Trace-Tool.pdf.

Q: How can I precalculate the data and fill the OLAP Cache ?

A: The SAP note 998680, attachment Automate-with-RSTT-Trace-Tool.pdf, gives some hints. For the Configuration
Validation the following steps give an example. Please consider that the queries are OLAP cache enabled.

Step1: Activate the trace user using transaction RSTT in BI backend and execute the Configuration Validation Report
after that.

Step 2: Deactivate the tracing and find the trace id in BI backend

SAP AG 2008
End-to-End Diagnostics 9
Troubleshooting Guide - Configuration Validation

Step 3: Define a test package

Step 4: Define a new background job and schedule it

SAP AG 2008
End-to-End Diagnostics 10
Troubleshooting Guide - Configuration Validation

SAP AG 2008