You are on page 1of 64

SAP Solution Manager 7.

0 EhP1

End-to-End Diagnostics
User Guide Configuration Validation
Version 1.0, December 2008
END-TO-END DIAGNOSTICS
USER 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,
Note
and menu options.
Cross-references to other Recommendation
documentation.
Example Syntax
Emphasized words or
text phrases in body text, graphic
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
USER GUIDE CONFIGURATION
VALIDATION

Contents

1 Introduction ......................................................................................................................................... 4
1.1 How to Use this document .......................................................................................................... 4
1.2 Required Software Components................................................................................................. 4
2 Architectural overview ........................................................................................................................ 4
2.1 Goal and Concept ........................................................................................................................ 4
Extractor Framework............................................................................................................................... 5
3 Architecture of Configuration and Change Database (CCDB) ......................................................... 7
3.1 Overview....................................................................................................................................... 7
3.2 Architecture of the Configuration Validation ............................................................................. 7
3.3 Prerequisites for Configuration Validation setup .................................................................... 10
3.4 Determination of the Configuration Compliance ..................................................................... 11
Stores and Groups ................................................................................................................................ 11
4 Application in Details ........................................................................................................................ 13
4.1 Tools Overview .......................................................................................................................... 13
4.2 Starting the Configuration Validation Tools ............................................................................ 13
4.3 Configuration Validation Procedure ......................................................................................... 15
4.3.1 Creating Target System ....................................................................................................... 17
4.3.2 . Editing Target System ........................................................................................................ 25
4.3.3 Create Comparison List........................................................................................................ 36
4.3.4 Execution of Validation reports............................................................................................. 41
4.3.5 Validation Report Output (BI User Interaction) ..................................................................... 50
5 Appendix............................................................................................................................................ 58
5.1 Involved BI reporting objects.................................................................................................... 58
5.2 OLAP Cache ............................................................................................................................... 61
5.3 BI Queries................................................................................................................................... 62
End-to-End Diagnostics 4
User Guide - Configuration Validation

1 Introduction

1.1 How to Use this document


The purpose of this document is to describe the architecture of the Configuration Validation, describe functionality of
Configuration Validation tools and provides practical recommendations on using these tools.

1.2 Required Software Components


The Configuration Validation application is running on top of End-to-End Diagnostics SP18 functionality delivered with
SAP Solution Manager 7.0 EhP1. This way the required software components can be divided into two parts:
1. E2E Diagnostics SP18
The latest mandatory Software Components for E2E Diagnostics SP18 are described in note 1274287.
This note mentions also the 'Prerequisites for Managed systems' and all required Support Packages and SAP
notes that have to be applied. If those prerequisites are not fulfilled completely the E2E application might not work
properly.
2. Configuration Validation
Improvements and corrections for the Configuration Validation are described in the SAP Notes 1263306 and
1263256.

2 Architectural overview
This chapter provides a technical overview of Configuration Validation application.

2.1 Goal and Concept


The main goal of the Configuration Validation application is to compare and validate current values of configuration
items of many systems against a defined target or standard configuration.
The validation results are displayed in the browser using Business Intelligence (BI) reporting capabilities. It allows
performing an interactive cross-system configuration audit as well as configuration reporting for a large number of
compared systems.
To minimize efforts required for the implementation of Configuration Validation a number of predefined validation
reports delivered for different validation areas. Those are: software validation, security validation, database validation,
SAP BI validation and customer-defined validation.
Validation of the configuration items is based on the data stored in the Configuration and Change Database (CCDB)
which is a part of the E2E Diagnostics Infrastructure.

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

In the diagram below a general overview of the E2E Diagnostics Infrastructure is provided.

The configuration data is collected from different sources of differing system types. On the diagram those are displayed
as Managed Systems at the left side.
The data is collected on a Product Instance Perspective, which means that an access is provided to data specific to the
component in question, e.g. CRM or XI, ABAP or Java based systems.
The technical infrastructure to collect the data into the Solution Manager Diagnostics and into the BI is the Extractor
Framework (EFWK). The Extractor Framework guarantees that the strong emphasis on the Product Instance
Perspective is available for the E2E applications displaying the data by enriching the data with additional information.
The extracted configuration data is stored in the Configuration and Change Database (CCDB). The Configuration
Validation and the Change Reporting are using the data of the CCDB. However, for the E2E Change Analysis the
CCDB data is aggregated and saved in an InfoProvider of Business Intelligence (BI) which allows using BI reporting
capabilities by E2E Diagnostics applications. The Configuration Validation is reading the CCDB data via a 'Virtual
InfoProvider' to provide BI reporting capabilities. The validated data is not stored in BI.
The further information on E2E Diagnostics can be found under the page http://service.sap.com/diagnostics

Extractor Framework
The Extractor Framework (EFWK) collects data of different data sources, and performs an enrichment of the collected
data based on the data maintained in transaction SMSY (landscape model). All data transported by the EFWK has to
incorporate core dimensions of a data model based on the landscape model in order to ensure that the data can be
stored in a self-contained manner. All E2E applications run in the same context of the landscape model, which allows
direct access to the data transported and enriched by the EFWK.

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

Technically, the data enrichment comprises of a set of IDs (the so called PPMS-IDs), which uniquely identify any SAP
Product Instance delivered to customers. All data extraction and status tracking is also based on these IDs.
For the collected data, a central status tracking is available in order to control data retrieval and storage in the
persistence layer (BI, CCDB, etc). This avoids data gaps and that identical data records are written to the persistence
layer more than once.
The smallest technical entity collecting the data is an extractor, which will gather the data either directly from the
managed system by means of a RFC call (ABAP extractor) or indirectly by retrieving the data from an intermediate
layer such as the Wily Introscope Enterprise Manager or retrieving the data from Configuration and Change Database
(CCDB) for the Change Analysis.
The EFWK offers an API for the Setup Wizard of E2E Diagnostics in the SAP Solution Manager which will activate all
relevant extractors based on how a system was modeled in transaction SMSY. Thus, for a CRM system, only the
extractors relevant for CRM will be activated.
Furthermore, a batch process will be created in the ABAP-stack of the Solution Manager. This batch process will only
start one extractor for the given system at a time, preventing that more than one extractor can run on a managed
system at any time.

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

3 Architecture of Configuration and Change Database


(CCDB)

3.1 Overview
Configuration items, values and history are stored in the Configuration and Change Database (CCDB) which is part of
the E2E Root Cause Analysis in SAP Solution Manager.
The details of a single configuration item are stored in containers of a defined type called ConfigStore. Based on this
ConfigStore information, the numbers of changes of each ConfigStore are determined using CCDB and are uploaded
daily into BI by the Extractor Framework.
Thus two layers of configuration and change data exist:
The detailed configuration data and the history as basic layer in the CCDB.
The aggregated number of changes in the BI to provide a top-down reporting (in the diagram below it is
represented via InfoProvider 0SMD_CA02)

Solution Manager Change Analysis Change Reporting


I nfoCube
0SMD_CA02 (CA) (CR)

Landscape-API CCDB Read-API


(Store-API)
Configuration Validation
(CV)

Upload-API Other s Log Viewer

The CCDB is connected to the Landscape-API of the Solution Manager which provides landscape information of the
managed systems. The Upload-API detects the changes per ConfigStore and stores the data in the CCDB. The Read-
API is the central point of entry for all applications reading configuration data from the CCDB. The InfoProvider
0SMD_CA02 contains aggregated changes of the configuration data. The Store-API is the interface to access the
configuration data via object model.
The Configuration Validation is reading the CCDB via Read-API.

3.2 Architecture of the Configuration Validation


The main components of Configuration Validation are:
Configuration and Change Database (CCDB)
Virtual InfoProvider 0SMD_VCA1 using function module (RS_BW_BTC_SMD_CA2_COMPLIANCE1)
Configuration Validation Reporting application
Target System Maintenance application

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

The diagram below describes the architecture and data flow of the Configuration Validation and the functions of the
components belonging to it.

As first step the single configuration items of existing systems are collected and stored by the Extractor Framework
(EFWK) in the ConfigStores of the Configuration and Change Database (CCDB).
To make this configuration data available for BI reporting, the data from CCDB is read and valuated by the function
module RS_BW_BTC_SMD_CA2_COMPLIANCE1 and passed to the Virtual InfoProvider 0SMD_VCA1 and queries
defined on it. The data is not stored in the Virtual InfoProvider 0SMD_VCA1; the validation reports use the appropriate
BI structures and reporting features to display the results in the browser.

Target Systems
The configuration items stored in the CCDB are providing information of the technical configuration and the applied
software versions of existing systems. This includes also system specific configuration items like host name, IP
address and so on. However, no other system corresponds with all configuration items to another system. In addition
only some specific configuration items but not the complete system configuration might be relevant for validation.
Thus in many cases instead of performing a validation against an existing system configuration, a validation against a
defined target configuration is required, e.g. to validate settings according to corporate security baselines or
performance settings across a large number of systems. These target configurations are created based on existing
system configurations, and stored in the Solution Manager as "Target Systems".

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

To ensure the independency from existing configuration data stored in CCDB the target configuration data is copied
into the Database table DIAGCPL_VS. The copied configuration data can be edited via the Target System
Maintenance application.

The configuration data of existing systems as well as the customer defined configurations, represented by target
systems, are read by the function module RS_BW_BTC_SMD_CA2_COMPLIANCE1 and are transferred to the Virtual
InfoProvider 0SMD_VCA1 to make it available for Configuration Validation Reporting application.
From a technical perspective a validation report is a BI WebTemplate that starts a number of queries as soon as it is
executed. The queries are selecting data from the Virtual InfoProvider 0SMD_VCA1 which is dynamically filled with the
existing system configuration data from the CCDB and the customer defined configuration from the database table
DIAGCPL_VS. The Virtual InfoProvider 0SMD_VCA1 does not store the data; its only preparing it at runtime of the
query for displaying it in the WebTemplate.

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

Reference and Comparison Systems


As a reference system for Configuration Validation both the configuration items of an existing system and the
configuration items of a target system can be used. As comparison systems only the existing system configurations
stored in the CCDB can be used.
Reference Systems
o Configuration of an existing system
Data stored in Configuration and Change Database (CCDB)
Latest available snapshot used (its not possible to choose a date in the past).
Exception: for the 'event type ConfigStores' ABAP_TRANSPORTS and J2EE_TRANSPORTS
a time range selection is possible. Remark: 'Event type ConfigStores' do not store a snapshot.
No changes of configuration is allowed
o Target Systems (Customer defined configuration / baseline configuration)
Content of existing ConfigStore is copied into a separate database table
Existing configuration items could be modified manually and restricted to only those
configuration items which really necessary for a specific audit task
Snapshots of existing system configurations could be saved at regular intervals for further
reference
Comparison Systems
o Existing systems only
Data stored in Configuration and Change Database (CCDB)
Latest available snapshot used (its not possible to choose a date in the past).
Exception: for the 'event type ConfigStores' ABAP_TRANSPORTS and J2EE_TRANSPORTS
a time range selection is possible and expected.

3.3 Prerequisites for Configuration Validation setup


Configuration Validation and Change Reporting are using the same data which is also the basis of the E2E Change
Analysis application. This part of End-to-End Diagnostics EHP1.
As soon as diagnostics setup was performed and the E2E Change Analysis application is available, configuration data
is collected and written into CCDB. Thus the Configuration Validation application can be used without further
implementation activities.
E2E Change Analysis is a part of standard E2E Diagnostics setup that among other includes the following steps that
need to be done for E2E Change Analysis and for Configuration Validation implementation:
Installation of End-to-End Diagnostics SPS18
o BI Content 704, Level 1
o Solution Manager EHP 1
Configuration of E2E Diagnostics
o Connecting of Managed Systems with E2E Diagnostics
o Installation of Diagnostics Agents
o Configuration of Extractor Framework

SAP AG 2008
End-to-End Diagnostics 11
User Guide - Configuration Validation

o Filling the Configuration and Change Database (CCDB) with the Configuration Data
After the E2E Diagnostics setup is completed and the configuration data is available in the CCDB it is necessary to
assign the role for Change Management Work center to the end-user profile to access the application. Additionally the
roles SAP_BI_E2E and SAP_SOLMANDIAG_E2E or the corresponding authorizations have to be assigned to the end-
user. The Change Management Work center offers the URL links to the Configuration Validation.

3.4 Determination of the Configuration Compliance

Validation Process
The configuration items of comparison systems are validated in accordance to the corresponding items of the reference
system.
The validation is done for each configuration item. If the item value string of the comparison system is exactly the same
as in the reference system, the configuration item is valuated as compliant (Compliance = 'Yes').
The items of the 'Security' related ConfigStores STANDARD_USERS, GW_SECINFO and GW_REGINFO, however,
are not valuated against the items of the reference system, but according to the rules described in SAP note 1234799.
Each ConfigStore like 'ABAP_COMP_SPLEVEL', 'J2EE_COMP_SPLEVEL' or 'SAP_KERNEL' gets valuated as not-
compliant as soon as one item is not-compliant. A system is also valuated as not-compliant as soon as one item of the
selected ConfigStores and items is not-compliant.

Stores and Groups


As it has been mentioned before the configuration items of existing systems are stored regularly in corresponding
ConfigStores. There are different types of ConfigStores depending on the type of data stored in it. The most important
types are xml, txt, ini, properties (two column based container: parameter, value), table (more than two column based
container: key1, key2, value1, value2 ) and event (as table but event-based).
The following table contains a list (not complete at all) of Change Groups and their ConfigStores which are currently
relevant for Configuration Validation.

SAP AG 2008
End-to-End Diagnostics 12
User Guide - Configuration Validation

Group ConfigStore
ABAP-SOFTWARE ABAP_COMP_RELEASE
ABAP_COMP_SPLEVEL
ABAP_NOTES
ABAP_TRANSPORTS
SAP_KERNEL
ABAP-PARAMETER ABAP_INSTANCE_PAHI
ABAP-DATABASE DB6_CONFIG
DB6_DBMCONFIG
DB6_LEVEL
DB6_REGISTRY
MAXDB_LEVEL
MAXDB_PARAMETER
MSSQL_LEVEL
MSSQL_PARAMETER
ORA_LEVEL
ORA_PARAMETER
BI RSADMIN
RSADMINA
RSADMINC
RSADMINS
RSDDTREXADMIN
ROIDOCPRMS
RSFRONTENDINIT
J2EE-SOFTWARE J2EE_COMP_SPLEVEL
J2EE-TRANSPORTS J2EE_TRANSPORTS
PROFILE ABAP_DEFAULT_PROFILE
ABAP_INSTANCE_PROFILE
ABAP_START_PROFILE
OS ENVIRONMENT_VAR_${SID}ADM
(stands for Operating System) saposcol
SECURITY GW_REGINFO
GW_SECINFO
STANDARD_USERS
Table: Selected Groups and Stores
To get a complete list of all the defined ConfigStores the application 'e2e_ca_store_list' can be used to. To start the
application use the URL: http://<server>:<port>/sap/bc/webdynpro/sap/e2e_ca_store_list

Limitations
In the CCDB approx. 25 ConfigStores created for an ABAP based system per instance. Not all of these ConfigStores
are relevant for the Configuration Validation. The practical usage of the Configuration Validation is limited to the
ConfigStores of the following types:
Property
Table
WIN_INI
The ConfigStores of types TEXT and XML are not generally supported because these ConfigStores are not structured
in a way which allows identifying the configuration items and their values from a general perspective.

SAP AG 2008
End-to-End Diagnostics 13
User Guide - Configuration Validation

An exception is done for the ConfigStore saposcol whose content is parsed to identify the configuration items. Please
refer to the SAP Note 1253963 for further details on supported ConfigStores.

4 Application in Details

4.1 Tools Overview


With Configuration Validation two tools are delivered:
Target System Maintenance
Configuration Validation Reporting

Target System Maintenance is aimed to create and maintain target system configurations, create templates for target
system configurations and create comparison lists.
Configuration Validation Reporting is aimed to execute validation reports for selected systems.

4.2 Starting the Configuration Validation Tools


Both tools are part of the SAP Solution Manager 7.0 EhP1 and can be accessed in two ways:
Via Solution Manager Work center
Via SAP GUI

SAP AG 2008
End-to-End Diagnostics 14
User Guide - Configuration Validation

1. Via Change Management Work Center


The first option accesses the Configuration Validation tool
from the Change Management Work center of the SAP
Solution Manager.
To do so please start Solution Manager Work center in the
browser via URL:
Error! Hyperlink reference not valid.
And navigate to the Change Management tab. At the left side
you see the section "Related Links".
In this section you will find the links "Maintenance" and
"Reporting" to start applications for Target System
Maintenance and Configuration Validation Reporting.

2. Via SAP GUI


Another way to access Configuration Application is using SAP
GUI.

In the SAP easy access menu navigate to the Change


Management item and then open the Configuration Validation
section.
There are two links below Configuration validation
"Maintenance" and "Reporting".
The link Maintenance starts the Target System Maintenance
tool.
The link Reporting starts the Configuration Validation
Reporting tool. The application configuration validation starts
in a separate browser window

SAP AG 2008
End-to-End Diagnostics 15
User Guide - Configuration Validation

4.3 Configuration Validation Procedure


In the diagram below an overview of the configuration validation procedure is displayed.

In this procedure the values of configuration items of many systems will be validated against a defined target or
standard configuration. The procedure can be separated in four general steps:
1. Define and edit the target system
At the first step it is offered to define the target or baseline configuration. It could either be based on a current
configuration of an existing system or on a template. After the creation of the target system the selection of the
configuration items and their values can be adjusted in accordance with the requirements. If an existing system
is supposed to be used as reference system in the reporting step 1 can be skipped.
2. Define the comparison list of systems for comparison
At this step it is offered to define which systems are to be compared with the reference system. During this step
its possible to create a comparison list. This step and the usage of the comparison list avoids that the user has
to select the same comparison systems every time a report is executed.
3. Choose and execute validation report matching the validation area
After defining a target system and a comparison list everything is ready to execute configuration validation
reports in accordance to the validation area easily.
4. Customize the report output
If necessary, the output of the BI report can be adapted or saved offline.

SAP AG 2008
End-to-End Diagnostics 16
User Guide - Configuration Validation
Start Target System Maintenance

1. Navigate to the Change Management Work center


Creating and editing of target systems is done via Target System
Maintenance tool the can be started from the Change Management
Work center in the SAP Solution Manager.

2. Click the link Maintenance


In section "Related Links", click the link Maintenance at the left side
of the Change Management Work center.

.
3. The "Target System Maintenance" tool is started in the separate
browser window.

Tip:
Alternatively the Target System Maintenance tool can be started via direct URL:
Error! Hyperlink reference not valid.

SAP AG 2008
End-to-End Diagnostics 17
User Guide - Configuration Validation

4.3.1 Creating Target System


This chapter provides step by step procedure to create a target system (customer defined configuration).

A target system could be created based on an existing system configuration. From a technical point of view the
configuration items of an existing system are copied from the Configuration and Change Database (CCDB) and then
the configuration could be customized. To do so it is necessary first to select an appropriate existing system.
As it has been mentioned before not all Configuration Items (CIs) are relevant for Configuration Validation (e.g. IP
Address, host names, DIR paths etc.). By creation of target system the user can decide:
Which ConfigStores are relevant and need to be copied?
Which parameters and Configuration Items (CIs) are relevant and need to be left in the ConfigStore?
Which Configuration Items need to be removed?
There are two variants to create a target system:
Variant 1: Creation from manually selected ConfigStores
This option should be used to create a target system in case configuration items which have to be validated are
not contained in the predefined validation templates.
Variant 2: Creation in accordance to predefined templates.
ConfigStores and configuration items are defined here based on the delivered templates that correspond to
one of the predefined validation areas. Those are security validation, software validation, database validation,
BI validation.
A new target system is created for both of the variants as displayed in the diagram below:

SAP AG 2008
End-to-End Diagnostics 18
User Guide - Configuration Validation

Variant 1: Target System creation from manually selected ConfigStores


The diagram below provides an overview of the functions and steps required to create a new target system from the
manually selected ConfigStores (Variant 1).

SAP AG 2008
End-to-End Diagnostics 19
User Guide - Configuration Validation

1. Start the tool Target System Maintenance


Start the tool Target System Maintenance as it is described in
the chapter Start Target System Maintenance

2. Choose option Create Target System


After the tool is started click on the link Create Target System
at the left side to start application for target system creation.

3. Find source system


All source systems available for Configuration Validation can
be displayed by clicking on the link Display all in the section
"Source System List". Alternatively filtering is possible by
entering the required system ID into the corresponding input
field. In the table below all source systems relevant for
Configuration Validation are displayed. In this list you see
system ID, product name, and the Installation Number.

4. Use filter to restrict display


There is a filter option available at the top of the table to restrict
the displayed systems. Its possible to filter the system list by
system ID, product name, or installation number. Using
Wildcards is supported. E.g. using *NETWEAVER* as product
filter will only display then SAP Netweaver systems

SAP AG 2008
End-to-End Diagnostics 20
User Guide - Configuration Validation

5. Select source system


Choosing a source system via system ID link will display the details.
As soon as the source system is selected the ConfigStores of the chosen system are displayed in the table at the
right side. Here the ConfigStore name and ConfigStore attributes are displayed.

6. Select required stores


6.1. Use filter
Similar to the source system selection a filter option is available for all attributes to restrict the displayed stores.
Wildcards such as Asterisks (*), <, ! and +are supported.
To display all stores without host assignment insert "<!" in the filter field in column "Host"

To display all stores with host assignment use "!" as a filter option:

In order to display ConfigStores relevant for a ABAP Stack choose "ABAP" as filter in column System

Filter can be removed via the icon at the top of the screen.

6.2. Display ConfigStore content


Content of a ConfigStore is displayed by clicking on the link in column name. In this example all current ABAP
instance parameters are shown. For that the ConfigStore ABAP_INSTANCE_PAHI is selected.

SAP AG 2008
End-to-End Diagnostics 21
User Guide - Configuration Validation

Current kernel version information available via the ConfigStore "SAP_KERNEL"

Select the ConfigStores to be saved in the Database.

Warning
It is not possible to store in a target system several ConfigStores with the same name. For
example a system with several instances has the ConfigStores ABAP_INSTANCE_PAHI for

SAP AG 2008
End-to-End Diagnostics 22
User Guide - Configuration Validation

each instance. In case all these ConfigStores are selected for saving in the target system only
the first ConfigStore will be saved and all the others will be ignored. The reason for this is that a
target system as the reference it must not have several values for single configuration item.

7. Create target system from the selected ConfigStores


After the required ConfigStores are selected click the button at the bottom of the screen

8. Provide Target System Name and Description


In the popup window the name for target system and a
description must be provided. The name could be maximum 8
characters long and must not start with 0 which is a reserved
for SAP objects.

9. Save the Target System


After the system id and the description are provided, button
"Save" will finally store the content of the selected
ConfigStores. Feedback regarding the results of the creation of
the selected ConfigStores is provided

SAP AG 2008
End-to-End Diagnostics 23
User Guide - Configuration Validation
Variant 2: Target System creation from Template

Use case:
In many cases the available configuration items need to be restricted to ensure transparency of Configuration
Validation. The reasons are as following:
Not all the available configuration items are relevant for Compliance Reporting from a general perspective. For
example configuration items including IP Address, host names, system ID are always different in the compared
systems and normally excluded from validation.
For different validation areas only specific configuration items are relevant. For example for a Security
Validation only security relevant parameters and configuration items need to be validated. For a Software
Validation some other configuration items might be necessary

To minimize efforts by selecting necessary ConfigStores for a specific validation area the predefined templates can be
used for creating target systems.
From a technical point of view a template consists of ConfigStores including configuration items which are pre-selected
for specific validation area. The values of configuration items are not stored in the templates, only the configuration
item names. During target system creation only those configuration items from the source system are copied that exist
in the template.
Templates can be considered as a filter with two layers. At the first layer the ConfigStore are filtered. At the second
layer only configuration items relevant to the validation area are left in the ConfigStores. All the irrelevant configuration
items are deleted.
In the diagram below an overview of the functions and steps to create a new target system from a template (Variant 2)
is provided.

SAP AG 2008
End-to-End Diagnostics 24
User Guide - Configuration Validation

1-5 For this variant the steps 1-5 are the same as for the variant 1. Please refer to the previous chapter for
detailed description. Manual selection of the ConfigStores is not required since the necessary ConfigStores
will be selected via template automatically

6. Create Target System from Template


After the source system is selected its possible to
create a target system based on a template via the
button at the bottom part of the screen.
In this example a target system is created from the
source system C60.

7. Provide Target System Name and Description


In the popup window the name for target system
and a description must be provided. The name
could be maximum 8 characters long and must not
start with 0 which is a reserved for SAP objects.
8. Select Template
After the target system ID and the description are
provided; the required template from the template
list is selected. The templates for the different
validation areas such as validation of BI, database,
software or security are available.
In this example a target system for software
configuration validation is to be created. To do this
the template 0SW can be used. This template
contains pre-selected configuration items for the
areas: ABAP and Java Software Level, ABAP
Kernel Level, OS Level, SAP Notes, Transport
Requests, ABAP Profile parameters and for ABAP
Memory configuration
9. Click the button Create
At this step the ConfigStores matching the template
will be copied from the selected source system. The
Configuration Items within these stores will be
filtered in accordance to the configuration items
defined in the ConfigStores of the template.
To store all the configuration items from the source
ConfigStore without filtering, the option Keep all
parameters from source system needs to be
selected at the bottom of the screen. In that case
the template determines only the ConfigStores

SAP AG 2008
End-to-End Diagnostics 25
User Guide - Configuration Validation

10. Check the saving results. After a target system is created from a template a feedback is provided. The newly
created target systems might be found and maintained under the link "Edit Target System" which is described
in the chapter Editing Target System.

4.3.2 . Editing Target System

After a target system is created in many cases it is necessary to adjust it in accordance to customer requirements. For
example to perform a validation of security standards the existing ABAP instance parameters need to be restricted to
only those that are relevant for security validation.
In this chapter the steps to customize the ConfigStore ABAP_INSTANCE_PAHI will be described.

SAP AG 2008
End-to-End Diagnostics 26
User Guide - Configuration Validation

The diagram below describes the steps to edit a target system

1. Start the tool Target System Maintenance


Start the tool Target System Maintenance as it is described in
the chapter Start Target System Maintenance

2. Choose option Edit Target System


After the tool is started click on the link Create Target System
at the left side to start application for target system creation.

3. Find target system


All existing target systems can be displayed by clicking on the
link Display all in the section "Edit Target System".
Alternatively filtering is possible by entering the required
system ID into the corresponding input field. Table Select
Target Systems displays the system ID, product name, and
description of the target systems

SAP AG 2008
End-to-End Diagnostics 27
User Guide - Configuration Validation

4. Select Target System


Select a target system for editing by clicking on the system name. As soon as a target system is selected all
ConfigStores included into this system will be displayed at the right side in the table "ConfigStores of Target
System". The title of this table displays the currently selected target system

Editable Info only

5. Select Store to be edited


Clicking on the ConfigStore name will allow editing the content of ConfigStore.
In the diagram below the kernel level information is selected for editing by choosing the ConfigStore
SAP_KERNEL.
At the bottom part of the screen two tabs are displayed. In the Tab "Edit Store Content" at the left side a list of
configuration items from the selected ConfigStore is displayed. These entries could be modified. Here you can
change values, insert new entries or delete old entries.
In the table at the right side the configuration items from the corresponding source system are displayed. In this
table the current values of the configuration items are displayed
This view allows comparing the modifications done in the target store with the real configuration item values
stored in the source system.

SAP AG 2008
End-to-End Diagnostics 28
User Guide - Configuration Validation
Maintenance Options
The diagram below provides an overview of the maintenance options available for editing target systems.

With these options it is possible to select, delete and insert entries. In the example below the entries which are not
relevant for configuration validation are going to be deleted and only necessary configuration items will be left.

1. Select irrelevant entries


To do so, the irrelevant entries are selected. Those are KERN_COMP_ON, KERN_COMP_TIME and
KERN_DLIB
2. Delete irrelevant entries
After the irrelevant entries are selected they are deleted using the "waste container" icon:

SAP AG 2008
End-to-End Diagnostics 29
User Guide - Configuration Validation

1. Check the results


Now only two entries that are relevant for configuration validation are left in the ConfigStore.
In case a lot of entries need to be removed from the ConfigStore there is an easy way to do so: Select first
only the relevant entries and then invert the selection via the button . This way all the irrelevant entries
are selected for deletion in two steps.

2. Change the values


At the next step the values of these configuration items can be changed.
In the example below the Kernel Release is changed from 700 to 710 and the Kernel patch level from 183
to 200. To do that the values are changed directly in the table at the left side.

Please note that any free text can be inserted into this table. No accuracy check is done (neither for
configuration item names nor for the inserted values). At the right side table (displayed with green
background) the real values from the corresponding source system can be used as a reference to
compare edited values from the target ConfigStore.

Display Options

SAP AG 2008
End-to-End Diagnostics 30
User Guide - Configuration Validation

1. Display entries in source matching to target system entries


By default at the right side table (source system) only the entries matching the selected Target ConfigStore are
displayed. This view is activated via the button :

2. Display entries in source that exist in addition to target system entries

To display all parameters existing in the source systems and missing in the target system click the button in the
menu bar:
This view can be used if later some other configuration items need to be added from the source system. To add the
configuration items select the necessary configurations items and click the button . The parameters will be
added to the target system and removed from the table of source system configuration items.
Save ConfigStore
To save the changes done in the ConfigStore click the button at the bottom side of the screen.

At this step the ConfigStore is saved. Please note that an 'Undo' is not provided. After the save operation, the currently
displayed content snapshot of the selected ConfigStore is saved in the database

SAP AG 2008
End-to-End Diagnostics 31
User Guide - Configuration Validation
Store Details
In the second tab with the name "Store Details" the technical attributes of the selected target ConfigStore are
displayed.

Among other technical information the date of the last change and the user who has changed the target system last
time can be found.
Add / Remove ConfigStores

1. Click the link Add/Remove Stores


To add additional ConfigStores from the corresponding source system, use the link
in the toolbar of the table ConfigStore list of the target system

SAP AG 2008
End-to-End Diagnostics 32
User Guide - Configuration Validation

2. Display the ConfigStores from the source system


In the popup window at the right side the ConfigStores of the target system are displayed. At the left
side the available ConfigStores of the source system are displayed. The displayed source system was
used to create the target system. From the left table additional stores can be added to the target
system.

3. Filter the necessary ConfigStores


To find necessary ConfigStores filter options might be used. In the example below additional
ConfigStores are added to the target system. Those are ABAP_COMP_SPLEVEL, ABAP_NOTES and
ABAP_PACKAGES. To do that first all the existing ConfigStores are filtered to only those that have
ABAP string in their name.
4. Select the required ConfigStores
5. Add the required ConfigStores to the target system
After the necessary ConfigStores are selected the button adds the selected ConfigStores to the
target system. At this step the content of the selected ConfigStores will be copied to the target system

Save as Template

1. Click the button Save as Template


To minimize efforts in the future when creating a similar target systems, the target system configuration can be saved
as template using the button .

SAP AG 2008
End-to-End Diagnostics 33
User Guide - Configuration Validation

2. Provide Template ID and Description


In the following popup window the template ID and a
long description have to be provided in order to store the
template.
3. Save Results
The template is saved using the button . At this
step the configuration items of the selected target
system are stored under the name provided in the popup
window. The values of the configuration items are
deleted.

4. Check the save results


After saving the template a result screen is displayed.

Display Templates
A template contains information about ConfigStores and configuration items and is used to filter the configuration items
when a target system is created.
In the diagram below the steps to display content of templates are provided.

SAP AG 2008
End-to-End Diagnostics 34
User Guide - Configuration Validation

1. Choose option Display Template


Templates could be displayed in the Target System
Maintenance" application via the link Display Templates.

2. Find Template
All available templates can be displayed by clicking on
the link Display all in the section "Display Templates".
Alternatively filtering is possible by entering the required
template ID into the corresponding input field. Table
Templates displays the system ID, product name, and
description of displayed templates.
A template that starts with "0" is delivered by SAP and
cannot be modified. These templates are used to create
target systems for predefined validation areas such as
validation of BI, database or software configuration

SAP AG 2008
End-to-End Diagnostics 35
User Guide - Configuration Validation

3. Select Template
Select a template for displaying by clicking on the system name. As soon as a template is selected all the
ConfigStores included into this template will be displayed at the right side in the table "ConfigStores of Target
System" The title of this table displays the currently selected template

4. Select Store to be displayed


To display the content of a ConfigStore from a templates click on the ConfigStore name. In the example below the
content of ConfigStore SAP_KERNEL of the template CRM_TPL is displayed. In the bottom part of the screen the
content of template ConfigStore is displayed. As it can be seen from the diagram above the values of configuration
item are not part of the template

5. Select Source System


In the middle of the screen a list of the ConfigStores from source systems is displayed which have the same name.

SAP AG 2008
End-to-End Diagnostics 36
User Guide - Configuration Validation

The link in column store name displays the configuration matching the selected template.
As soon as a ConfigStore from the table ConfigStores (Source System) the content of this ConfigStore is
displayed at the right side.
At the right side only the entries matching template configuration items will be displayed. In the title of the table the
system id of the selected ConfigStore is shown.
The content displayed at the right side can be used as a preview of the target system as if its created from the
selected ConfigStore using the template

6. Display ConfigStores from all systems


By default the list in the middle of the screen contains only the ConfigStores from the systems matching the
product version of the displayed template. Its possible to display the ConfigStores with the same name from all
systems by removing the filter option in the top menu.

Its possible to match the content of any ConfigStore from the displayed systems with the template items.
In the example above at the right side the values of the kernel patch level of the system CXE are displayed. The
template items shown on the left side are matching item-wise.

4.3.3 Create Comparison List


After the reference configuration is prepared it is possible to define systems for comparison. That could be for example
all ABAP production systems or all SAP BI systems or all systems relevant for critical Business Process. It is not
necessary to have these lists defined, because the restriction on the systems can also be done in the variable screen
of the validation report. However, its more convenient to create comparison list having in mind using them regularly.
In order to avoid selecting single systems one by one each time a validation report is executed it is possible to create a
list of these systems only once and use it for configuration validation reporting. A list of systems to be compared is
named Comparison List". In this chapter it will be described how to create and maintain such a list.

SAP AG 2008
End-to-End Diagnostics 37
User Guide - Configuration Validation

The diagram below describes the steps to create a new comparison list.

SAP AG 2008
End-to-End Diagnostics 38
User Guide - Configuration Validation

1. Choose option Maintain Comparison Lists


The link "Maintain Comparison Lists" starts the
application

2. Create New
The link "Create new" opens a new popup window to
select systems and create a new comparison list.

3. Provide Name and Description


In the popup window the name for comparison list
and a description must be provided.
In this example a list including all systems having
ABAP-based components will be created. Lets name
it "ALL_ABAP"

4. Display systems available for Configuration


Validation
After the list name and the description are provided
the systems can be added to the list. The link
Display all" shows all available systems.
In the table all systems relevant for Configuration
Validation are displayed. For systems with a double
stack separate entries for ABAP- and Java-based
components are displayed

SAP AG 2008
End-to-End Diagnostics 39
User Guide - Configuration Validation

5. Filter Option
The filter option at the top of the table can be used to
filter systems by system ID, type, installation number
or product name.
In the example all systems that have ABAP- based
components have to be filtered. To do so the drop
down menu in column "Type" is used for filtering

6. Select Systems to be added


After ABAP-based systems are filtered the required
entries are select. It is possible to select all the
entries or one by one.
7. Create Comparison List
Adding the selected systems to the list via the button
. The results are displayed

8. Check the results


After the comparison list is created close the popup
window and return to the main screen

9. Refresh List
The button in the main screen updates
the display of the comparison lists

SAP AG 2008
End-to-End Diagnostics 40
User Guide - Configuration Validation
Options for Comparison Lists Maintenance

1. Display systems from the comparison


list
Clicking on the link in column name
displays the systems belonging to this list

At the left side the systems belonging to


the comparison list are displayed.
2. Remove systems from the
comparison list
The icon in the column Delete
removes systems from the list

3. Add systems to the comparison list


At the right side of the screen the list of
the source systems that do not belong to
the selected comparison list are shown.
These systems can be added to the
comparison list at any time
To add the systems to the comparison
list select the required systems and click
the button .

SAP AG 2008
End-to-End Diagnostics 41
User Guide - Configuration Validation

4.3.4 Execution of Validation reports

After the target and the comparison system lists have been defined a validation report can be executed easily.
SAP delivers a number of predefined validation reports for different validation areas such as security configuration
validation or software level validation.

As it has been described in the chapter Architecture of the Configuration Validation the validation reports are BI
WebTemplates with queries or views based on the Virtual InfoProvider 0SMD_VCA1 as data provider. BI
WebTemplates allow using of standard BI reporting capabilities such as user interaction, broadcasting and publishing.
In this chapter it will be described how to use "Configuration Validation Reporting" tool for execution of validation
reports. As example the security validation report will be used.

SAP AG 2008
End-to-End Diagnostics 42
User Guide - Configuration Validation

In the diagram below an overview of the functions and steps to execute a validation report is provided.

1. Start the tool Configuration Validation Reporting


Configuration Validation Reporting tool is started via the link
Reporting from the SAP Solution Manager WorkCenters as it
is described in the chapter Start Target System Maintenance.
Alternatively it can be started using the URL:
http://<host>:<port>//sap/bc/webdynpro/sap/
config_compliance_report

SAP AG 2008
End-to-End Diagnostics 43
User Guide - Configuration Validation

2. Select Configuration Validation Report


As the Configuration Validation Reporting tool is started at the top of the screen the predefined reports are
displayed.
Here the list of validation reports for different validation areas can be found.
There are two types of validation reports available:
Validation reports for predefined validation area
These reports have been developed for specific validation areas. Those are software validation, security
validation, database validation, SAP BI validation. For validation only those configuration items are
validated which correspond the predefined validation area. These configuration items are predefined in the
validation report.
Generic validation reports.
The last two reports (custom validation and reference validation) are generic reports and do not have any
predefinition of validated configuration items. Executing these reports only those configuration items will be
validated which exist in the reference system.

In the diagram below is an overview of the delivered validation reports and their scope is provided.

SAP AG 2008
End-to-End Diagnostics 44
User Guide - Configuration Validation

(*) The Configuration Compliance Comparison is not done versus the items of the reference system, but according
defined rules. See SAP note 1234799 for more information. The reference system can have non-compliant items
as well.

In current example the report "0TPL_0SMD_COMPL_SECURITY_START" is executed to perform a validation


against security relevant configuration items. The description of the report is "SECURITY VALIDATION- Using
ABAP software, kernel level and profile parameter, SAP Notes

3. Execute Configuration Validation Report


The link "Start configuration validation reporting" at the bottom part of the screen executes the selected validation
report

4. Provide input data (Variant 1: via Variable popup)


In the displayed variable popup the input data must be
provided.
Those are:
Reference system - This is the system which
configuration will be used as a reference for
comparison.
Comparison systems - These are the systems that
would be compared with the reference system
At the bottom part some further input fields such as ABAP
component, SAP notes, and ABAP kernel item and security
parameters are displayed. These input fields are already pre-
filled in accordance with security validation report and should
not be changed normally.
4.1. Navigate to the Reference System
To select a reference system from the list of available systems
a F4-help is available via the icon .

4.2. Select Reference System from the list


In the next popup window a list with the existing source systems
and the target systems are displayed.
Each system is represented by its system ID and installation
number. Target systems can be differentiated from existing
source systems via installation number. A target system has the
character string VIRTUAL" in capital letters as installation
number, instead of a numeric installation number.

Existing systems as well as target systems could be chosen as


a reference system.

In this example a target system with system ID


"SEC_VIRTUAL" is selected.

4.3. Navigate to the Comparison Systems


For the "Comparison Systems" also a F4-help is available.

SAP AG 2008
End-to-End Diagnostics 45
User Guide - Configuration Validation

4.4. Select Comparison Systems from the list


In the next popup window a list with the existing systems and
the target systems is displayed.
Each system is represented by its system ID and installation
number. Target systems can be differentiated from existing
source systems via installation number. A target system has the
character string VIRTUAL" in capital letters as installation
number, instead of a numeric installation number.

As comparison systems only the existing source systems can


be selected.

In this example several existing systems are selected. Those


are C60, P71 and WOP.
4.5. Transfer selection to the variable popup
The button "Transfer closes the F4-help and transfers the
selected system to the variable popup.

4.6. Check the selection


The currently selected reference and comparison systems can
be seen in the variable window.

4. Provide input data (Variant 2: via "Reference system and comparison systems" section in Reporting tool)
Alternatively to the selections via variable popup, its possible to perform the necessary selections using the tables
in section "Reference system and comparison systems". This minimizes the preparation efforts before a validation
report can be launched. To do so expand this section at the top of the screen.

SAP AG 2008
End-to-End Diagnostics 46
User Guide - Configuration Validation

4.1. Choose a reference system


In the section Choose a reference system the available
reference systems can be listed and filtered using the button
display. The reference system can be selected from the
displayed list. For each system the system ID, Installation
Number and a short description are displayed. In case of
existing systems in column "Description" the corresponding
product name is displayed. In case of a target system the
installation number is displayed as string "VIRTUAL". As in the
previous example the target system with the system ID-
SEC_VIRTUAL" is selected

4.2. Choose systems for comparison


Instead of selecting comparison systems one by one it is possible to use a comparison list which is maintained and
stored separately. The advantage is that a comparison lists could be maintained only once in accordance with the
customer requirements and then used for system selections many times. On the left side button "Display" shows
all available comparison lists.
In this example a comparison list containing all the ABAP-based systems is used.
4.3. Start configuration validation reporting
As next step configuration validation report is executed with the highlighted selections via the link "Start
configuration validation reporting" at the bottom of the screen.

SAP AG 2008
End-to-End Diagnostics 47
User Guide - Configuration Validation

4.4. Check the selection


In the variable popup the selected reference and comparison
systems are used as input for the configuration validation report
run.
5. Execute the report
The button "Execute" at the bottom of the variable popup
launches the validation configuration report.

Suppress query variables popup


Option Suppress query variable popup can be selected to avoid displaying the variable screen and to directly
execute a validation report. Of course a Reference System (section 'Choose a Reference System') has to be
selected before.

The screen below gives an overview of the result.

SAP AG 2008
End-to-End Diagnostics 48
User Guide - Configuration Validation

6. Report output
After the report is executed the validation results are displayed. In the diagram below an output of validation report
is shown
The information is separated into different tabs corresponding to the validated areas. The first tab is an overview
screen which comprises the results for all validated areas. The further tabs contain detailed information on the
corresponding area.

SAP AG 2008
End-to-End Diagnostics 49
User Guide - Configuration Validation

6.1. Tab Overview


At the top of the screen the system id of the reference system and the list of the comparison systems and their
installation numbers is displayed

At the middle of the screen an overview over all areas covered by the report is displayed. In this example the
following areas have been covered:
ABAP Software Level, ABAP Kernel Level, Profile Parameters, Gateway Secinfo, SAP Notes, IGS Level, Standard
Users and Gateway Reginfo.
For each validation category the number of compliant and non-compliant systems is displayed. In case there is at
least one system that is not compliant with the reference system the validation category is marked red. Only in
cases that all the systems are compliant the validation category is marked green.
Validation for Standard Users, Gateway Security and Gateway Reginfo is not done versus the configuration items
of the reference system but in accordance with the rules that are listed in the SAP Note 1234799. The content of
the ConfigStore of the Reference System is not taken into account here.

SAP AG 2008
End-to-End Diagnostics 50
User Guide - Configuration Validation

4.3.5 Validation Report Output (BI User Interaction)


In this chapter it will be shown how to use some important standard BI User Interaction functionalities.

SAP AG 2008
End-to-End Diagnostics 51
User Guide - Configuration Validation

1. Display Non compliant Items


In the example diagram the validation results of category ABAP Software Level are displayed.
At the left side the number of NOT compliant and compliant items is displayed per comparison system to rate the
compliance. At the right side a list of non-compliant configuration items is displayed. It shows exactly which items
and values are non-compliant.

2. Display Compliant values (reference values)


In the middle part a Navigation Block is provided aimed to restrict the displayed data. By default only the non-
compliant configuration items are displayed.

The filter option in the navigation block can be removed to display also the compliant values such as the values
from the reference system. Its possible to remove the filter via the "waste container" icon in the filter column of
characteristic Compliance.

SAP AG 2008
End-to-End Diagnostics 52
User Guide - Configuration Validation

2.1. Additionally the values for compliant


configuration items are displayed.
These added compliant configuration
items belong to the reference system.
Furthermore from other systems
specified in the comparison list
ALL_ABAP when having a corresponding
compliant configuration item.

3. Keep Filter Value


If a lot of the systems or configuration items
are used for comparison, a long list of
validated items is displayed. In this case its
useful to filter values only for one system and
hide all the other values.
In the example below the configuration items
for system CXE are filtered. This is possible
by clicking with the right mouse button on the
system name CXE and choosing the option
"Keep Filter Value" from the drop down
menu.

3.1. Then the values for the selected


system CXE are filtered while all the
other values are hidden.
Now the table Non compliant items
include only values for the CXE system

SAP AG 2008
End-to-End Diagnostics 53
User Guide - Configuration Validation

4. Drill down
In tab "ABAP Kernel Level" it is possible to check if ABAP kernel version used in the comparison systems is
compliant with the reference one.

In this diagram you can see that the system CXE has two different values for the ABAP kernel patch level.

4.1. The drill down options can be used to


check the kernel level used for
different ABAP Instances. Its possible
by clicking with the right mouse button
on system name and choosing
"Drilldown" Instance.

SAP AG 2008
End-to-End Diagnostics 54
User Guide - Configuration Validation

4.2. The same operation can be done for


the host names. The instance and
host names are added to the
displayed table.

Now it can be seen that the instance D26


on the host pwdf6365 has the ABAP
kernel level 15 while the other instances
have the level 9.

5. Display validity date of displayed


configuration data
In order to check when the configuration
items have been updated you can click on
the icon for the section: ConfigStore
Valid To

5.1. The column ConfigStore Valid To is


added to the table Non compliant
items
The displayed time stamps are in UTC
time zone and have the following format:
YYYYMMDDHHMMSS
<Year><Month><Day><Hour><Min><Sec>
For example the Configuration Item
700_COR for the system C60 with the
time stamp 20081110190336 has been
created at 10 November 2008 at
19:03:36.
From this table it can be seen that the
system E7U has several ConfigStores
KERN_REL which are updated at nearly
the same time. In the section it is
described how to display the instance
information as this ConfigStore exists per
each instance of a system.

6. Export to Excel (BI standard functionality)


6.1. Navigate to the Enhanced Menu of
the context menu. To do this perform
right mouse click in any place of the
table and choose Enhanced Menu

SAP AG 2008
End-to-End Diagnostics 55
User Guide - Configuration Validation

6.2. Export as CSV File or MS Excel


2000 File
Choose Export as CSV File or MS
Excel 2000 File from the dropdown
menu

7. Generic Validation Reports.

These reports (CUSTOM and REFERENCE VALIDATION) are not restricted to ConfigStores. For the REFERENCE
VALIDATION all ConfigStores and Configuration Items of the reference system are taken for the validation. The
CUSTOM VALIDATION offers additionally to restrict on 'Config Store', 'Configuration Items', 'Item Value' and a time
interval for 'Transport Requests in Date Range':

Both validations display a top down view starting with the system level and the information whether all items of the
reference system in case of the REFERENCE VALIDATION or the selected items in case of the CUSTOM
VALIDATION are found as compliant in the comparison system:

SAP AG 2008
End-to-End Diagnostics 56
User Guide - Configuration Validation

The REFERENCE VALIDATION is restricted on items whose compliance is Yes or No. It is expected that a target
system with a restricted number of items per ConfigStore is used. Thus the comparison systems will have more items
in their ConfigStores. These are found and valuated with compliance 'Additional in Comparison System'. Because of
the mentioned restriction on compliance Yes or No these items are not taken into account as long the restriction is
not removed. The CUSTOM VALIDATION on the other hand does not have this restriction in default.
Both reports offer the same drill down and navigational options. Unlike our example which shows all systems as not-
compliant it is expected that most of the systems or at least most categories are compliant and no further investigation
is necessary. The 'Expand Hierarchy Node' function by clicking on the triangle icon offers to drill down to the category
and finally the item values. The user decides for which system and configuration category and item the value should be
shown. In the screen shot the 'Expand Hierarchy Node' was done for the system 'C50 0020108503'. As the category
'ABAP-PARAMETER' was compliant it was not expanded. The category 'ABAP-SOFTWARE' however was expanded
as was valuated as not-compliant. The ConfigStore 'ABAP_COMP_SPLEVEL' and its item 'PI_BASIS' had been
expanded to display the not-compliant value 'Level 0012 Release 2005_1_700', see screen shot of the result area:

SAP AG 2008
End-to-End Diagnostics 57
User Guide - Configuration Validation

It might be helpful to expand all hierarchy nodes in one step or to display the result not hierarchical, but as flat list. Both
options are offered in the 'Local Properties of Query' dialog, which can be called using the context menu 'Query
Properties':

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'.
Or if the flat list should displayed remove the selection of 'Display Rows as Hierarchy and Expand to:

SAP AG 2008
End-to-End Diagnostics 58
User Guide - Configuration Validation

5 Appendix

5.1 Involved BI reporting objects


With BI Content 7.04 SP01 six WebTemplates and several objects used are delivered for this reporting:

The WebTemplates for predefined validation area use one WebTemplate per tab strip which uses two or more data
providers. The two WebTemplates for the generic reports use only one query as data provider.
The table lists the technical names of all WebTemplates, their data providers and ConfigStores used.
Area WebTemplate - technical name Query or Query View Selected ConfigStore

Software 0TPL_0SMD_COMPL_SW_START
Configuration
Overview 0SMD_VCA1_COMPL_Q001_V01_03 ABAP_COMP_SPLEVEL
0TPL_0SMD_COMPL_OVERV_V01_11 0SMD_VCA1_COMPL_Q005_V01_03 J2EE_COMP_SPLEVEL
0SMD_VCA1_COMPL_Q002_V01_03 SAP_KERNEL
0SMD_VCA1_COMPL_Q009_V01_03 saposcol
0SMD_VCA1_COMPL_Q011_V01_03 ABAP_NOTES
0SMD_VCA1_COMPL_Q010_V01_03 ABAP_TRANSPORTS
0SMD_VCA1_COMPL_Q003_V01_03 ABAP_INSTANCE_PAHI
ABAP Software Level 0SMD_VCA1_COMPL_Q001_V02
0TPL_0SMD_COMPL_ABAPSP_Q01_V02 0SMD_VCA1/0SMD_VCA1_COMPL_Q001 ABAP_COMP_SPLEVEL
JAVA Software Level 0SMD_VCA1_COMPL_Q005_V02
0TPL_0SMD_COMPL_JAVASP_Q05_V02 0SMD_VCA1/0SMD_VCA1_COMPL_Q005 J2EE_COMP_SPLEVEL
ABAP Kernel Level 0SMD_VCA1_COMPL_Q002_V02
0TPL_0SMD_COMPL_ABAPKR_Q02_V02 0SMD_VCA1/0SMD_VCA1_COMPL_Q002 SAP_KERNEL
Operating System 0SMD_VCA1_COMPL_Q009_V02
0TPL_0SMD_COMPL_OS_Q09_V02 0SMD_VCA1/0SMD_VCA1_COMPL_Q009 saposcol
SAP Notes 0SMD_VCA1_COMPL_Q011_V02
0TPL_0SMD_COMPL_SAP_NT_Q11_V02 0SMD_VCA1/0SMD_VCA1_COMPL_Q011 ABAP_NOTES
Transport Requests 0SMD_VCA1_COMPL_Q010_V02
0TPL_0SMD_COMPL_ABAPTR_Q10_V02 0SMD_VCA1/0SMD_VCA1_COMPL_Q010 ABAP_TRANSPORTS
ABAP Parameters 0SMD_VCA1_COMPL_Q003_V02
0TPL_0SMD_COMPL_ABAPPA_Q03_V02 0SMD_VCA1/0SMD_VCA1_COMPL_Q003 ABAP_INSTANCE_PAHI

SAP AG 2008
End-to-End Diagnostics 59
User Guide - Configuration Validation

Area WebTemplate - technical name Query or Query View Selected ConfigStore


Security 0TPL_0SMD_COMPL_SECURITY_START
Configuration
Overview 0SMD_VCA1_COMPL_Q001_V01_03 ABAP_COMP_SPLEVEL
0TPL_0SMD_COMPL_SEC_OVERV 0SMD_VCA1_COMPL_Q011_V01_03 ABAP_NOTES
0SMD_VCA1_COMPL_Q002_V01_03 SAP_KERNEL
0SMD_VCA1_COMPL_Q025_V01_03 IGS_LEVEL
0SMD_VCA1_COMPL_Q003S_V01_03 ABAP_INSTANCE_PAHI
0SMD_VCA1_COMPL_Q023_V01_03 STANDARD_USERS
0SMD_VCA1_COMPL_Q022_V01_03 GW_SECINFO
0SMD_VCA1_COMPL_Q024_V01_03 GW_REGINFO
ABAP Software Level 0SMD_VCA1_COMPL_Q001_V02
0TPL_0SMD_COMPL_ABAPSP_Q01_V02 0SMD_VCA1/0SMD_VCA1_COMPL_Q001 ABAP_COMP_SPLEVEL
SAP Notes 0SMD_VCA1_COMPL_Q011_V02
0TPL_0SMD_COMPL_SAP_NT_Q11_V02 0SMD_VCA1/0SMD_VCA1_COMPL_Q011 ABAP_NOTES
ABAP Kernel Level 0SMD_VCA1_COMPL_Q002_V02
0TPL_0SMD_COMPL_ABAPKR_Q02_V02 0SMD_VCA1/0SMD_VCA1_COMPL_Q002 SAP_KERNEL
IGS Level 0SMD_VCA1_COMPL_Q025_V02
0TPL_0SMD_COMPL_IGSSP_Q12_V02 0SMD_VCA1/0SMD_VCA1_COMPL_Q025 IGS_LEVEL
Profile Parameters 0SMD_VCA1_COMPL_Q003S_V02
0TPL_0SMD_COMPL_SECPA_Q03S_V02 0SMD_VCA1/0SMD_VCA1_COMPL_Q003S ABAP_INSTANCE_PAHI
Standard Users 0SMD_VCA1_COMPL_Q022_V02
0TPL_0SMD_COMPL_SUSER_Q15_V02 0SMD_VCA1/0SMD_VCA1_COMPL_Q022 STANDARD_USERS
Gateway Secinfo 0SMD_VCA1_COMPL_Q023_V02
0TPL_0SMD_COMPL_GWSEC_Q13_V02 0SMD_VCA1/0SMD_VCA1_COMPL_Q023 GW_SECINFO
Gateway Reginfo 0SMD_VCA1_COMPL_Q024_V02
0TPL_0SMD_COMPL_GWREG_Q14_V02 0SMD_VCA1/0SMD_VCA1_COMPL_Q024 GW_REGINFO
Database 0TPL_0SMD_COMPL_DB_START
Configuration
Overview 0SMD_VCA1_COMPL_Q008_V01_03 ORA_LEVEL
0TPL_0SMD_COMPL_DB_OVERV 0SMD_VCA1_COMPL_Q012_V01_03 ORA_PARAMETER
0SMD_VCA1_COMPL_Q013_V01_03 MSSQL_LEVEL
0SMD_VCA1_COMPL_Q014_V01_03 MSSQL_PARAMETER
0SMD_VCA1_COMPL_Q015_V01_03 DB6_LEVEL
0SMD_VCA1_COMPL_Q016_V01_03 DB6_CONFIG
0SMD_VCA1_COMPL_Q026_V01_03 DB6_REGISTRY
0SMD_VCA1_COMPL_Q027_V01_03 DB6_DBMCONFIG
0SMD_VCA1_COMPL_Q007_V01_03 MAXDB_PARAMETER
Oracle Level 0SMD_VCA1_COMPL_Q008_V02
0TPL_0SMD_COMPL_ORALEV_Q08_V02 0SMD_VCA1/0SMD_VCA1_COMPL_Q008 ORA_LEVEL
Oracle Configuration 0SMD_VCA1_COMPL_Q012_V02
0TPL_0SMD_COMPL_ORAPAR_Q12_V02 0SMD_VCA1/0SMD_VCA1_COMPL_Q012 ORA_PARAMETER
MS SQL Level 0SMD_VCA1_COMPL_Q013_V02
0TPL_0SMD_COMPL_MSSLEV_Q13_V02 0SMD_VCA1/0SMD_VCA1_COMPL_Q013 MSSQL_LEVEL
MS SQL Configuration 0SMD_VCA1_COMPL_Q014_V02
0TPL_0SMD_COMPL_MSSPAR_Q14_V02 0SMD_VCA1/0SMD_VCA1_COMPL_Q014 MSSQL_PARAMETER
DB6 Level 0SMD_VCA1_COMPL_Q015_V02
0TPL_0SMD_COMPL_DB6LEV_Q15_V02 0SMD_VCA1/0SMD_VCA1_COMPL_Q015 DB6_LEVEL
DB6 Configuration 0SMD_VCA1_COMPL_Q016_V02
0TPL_0SMD_COMPL_DB6PAR_Q16_V02 0SMD_VCA1/0SMD_VCA1_COMPL_Q016 DB6_CONFIG
DB6 Registry 0SMD_VCA1_COMPL_Q026_V02
0TPL_0SMD_COMPL_DB6REG_Q26_V02 0SMD_VCA1/0SMD_VCA1_COMPL_Q026 DB6_REGISTRY
DB6 DBM Configuration 0SMD_VCA1_COMPL_Q027_V02
0TPL_0SMD_COMPL_DB6DBM_Q27_V02 0SMD_VCA1/0SMD_VCA1_COMPL_Q027 DB6_DBMCONFIG
MAX DB Level/Conf. 0SMD_VCA1_COMPL_Q007_V02
0TPL_0SMD_COMPL_MDBPAR_Q07_V02 0SMD_VCA1/0SMD_VCA1_COMPL_Q007 MAXDB_PARAMETER

SAP AG 2008
End-to-End Diagnostics 60
User Guide - Configuration Validation

Area WebTemplate - technical name Query or Query View Selected ConfigStore


BI 0TPL_0SMD_COMPL_BI_START
Configuration
Overview 0SMD_VCA1_COMPL_Q006_V01_03 RSADMINC
0TPL_0SMD_COMPL_BI_OVERV 0SMD_VCA1_COMPL_Q017_V01_03 RSADMIN
0SMD_VCA1_COMPL_Q018_V01_03 RSADMINA
0SMD_VCA1_COMPL_Q019_V01_03 RSADMINS
0SMD_VCA1_COMPL_Q020_V01_03 ROIDOCPRMS
0SMD_VCA1_COMPL_Q021_V01_03 RSFRONTENDINIT
RSADMINC 0SMD_VCA1_COMPL_Q006_V02
0TPL_0SMD_COMPL_BI_PAR_Q06_V02 0SMD_VCA1/0SMD_VCA1_COMPL_Q006 RSADMINC
RSADMIN 0SMD_VCA1_COMPL_Q017_V02
0TPL_0SMD_COMPL_BI_PAR_Q17_V02 0SMD_VCA1/0SMD_VCA1_COMPL_Q017 RSADMIN
RSADMINA 0SMD_VCA1_COMPL_Q018_V02
0TPL_0SMD_COMPL_BI_PAR_Q18_V02 0SMD_VCA1/0SMD_VCA1_COMPL_Q018 RSADMINA
RSADMINS 0SMD_VCA1_COMPL_Q019_V02
0TPL_0SMD_COMPL_BI_PAR_Q19_V02 0SMD_VCA1/0SMD_VCA1_COMPL_Q019 RSADMINS
ROIDOCPRMS 0SMD_VCA1_COMPL_Q020_V02
0TPL_0SMD_COMPL_BI_ROI_Q20_V02 0SMD_VCA1/0SMD_VCA1_COMPL_Q020 ROIDOCPRMS
RSFRONTENDINIT 0SMD_VCA1_COMPL_Q021_V02
0TPL_0SMD_COMPL_BI_FRO_Q21_V02 0SMD_VCA1/0SMD_VCA1_COMPL_Q021 RSFRONTENDINIT
Area WebTemplate - technical name Query or Query View Selected ConfigStore
Generic
Custom Validation
0TPL_0SMD_COMPL_VAR_CONFSTORE 0SMD_VCA1/0SMD_VCA1_VAR_CONFST
S ORES Via variable
Reference Validation
0TPL_0SMD_COMPL_REF_CONFSTORE 0SMD_VCA1/0SMD_VCA1_REF_CONFST All of the reference
S ORES system
Table: WebTemplates and data providers of the Configuration Reporting.

SAP AG 2008
End-to-End Diagnostics 61
User Guide - Configuration Validation

5.2 OLAP Cache


The SAP Netweaver BI offers the functionality to store query raw data in the OLAP cache. A report can read the result
from this cache instead reading it from the database, if the query and the selections are fitting. SAP note 822302
provides information when the OLAP cache cannot be used.
The InfoProvider 0SMD_VCA1 used for the validation reporting is a virtual one that cannot use the OLAP cache by
default. The InfoProvider can be cache enabled using transaction RSDIPROP. The delivered settings are:

The Read Mode must be 'A Query to Read All Data At Once', because otherwise the Custom Validation and the
Reference Validation will not deliver a result. In this scenario there is no disadvantage using this Read Mode, because
the reading of the ConfigStore data via the function module takes most of the time, but is more or less independent of
the Read Mode. This Read Mode 'A Query to Read All Data At Once' avoids also additional reading accesses to the
function module, when the user does additional navigational steps like drill down of a characteristic or the selection of a
Configuration Item.
The Cache Validity should be less than 86400 seconds which means less than 1 day, because the ConfigStore data is
updated once a day. Please select the Cache Mode and Persistence Mode. The documentation about the Cache Mode
helps to decide this:
http://help.sap.com/saphelp_nw2004s/helpdata/en/d9/31363dc992752de10000000a114084/frameset.htm
If the setting as it is delivered is accepted, please transfer the InfoProvider 0SMD_VCA1 once more from BI Content,
but do not set the merge flag. Use transaction RSORBCT or RSA1 in BI client, select and transfer the InfoProvider. Set
the Install (I) flag and remove afterwards the merge (M) flag:

Press 'Install' to copy the delivered version of the InfoProvider.

SAP AG 2008
End-to-End Diagnostics 62
User Guide - Configuration Validation

The queries based on 0SMD_VCA1 are delivered cache enabled, because most of them use the InfoProvider setting.
Please read SAP note 1022589 about the relationship of the InfoProvider setting and the queries setting.
However the query 0SMD_VCA1/0SMD_VCA1_REF_CONFSTORES is not allowed to use the OLAP cache according
to its delivered settings, because it is supposed that the target system definition is changed quite often in the early test
phase. If the target systems definitions are not changed, the query can be adjusted to use the query cache, too. Please
use the transaction RSRT and select the query and use the menu 'Query, Properties'.
The cache and persistence mode of 0SMD_VCA1 and the queries is not the default mode used by BI. This makes the
administration, e.g. deletion of the cache entries easy. It is expected that only cache entries of the configuration
validation queries are found under the cross application 'Cluster' in the cache monitor (transaction RSRCACHE):

The validity of the cache entries is restricted by the cache validity setting of 0SMD_VCA1. As the OLAP does not have
the information about new updates of the ConfigStores or a change of the target used as system reference system in
the query, the relevant OLAP cache entry would be used and 'old' results displayed. This risk can be reduced by
defining a small value for the Cache Validity. The usage of the OLAP cache however offers to get a quick result.
A pre-filling of the OLAP cache can be done. The SAP note 998680 provides how-to information, see attachment
Automate-with-RSTT-Trace-Tool.pdf. Please check also the trouble shooting guide: 'SP18_CV_TbleShoot.pdf'.
Of course other options are possible. It is important however to do the pre-filling after the update of the ConfigStores.
The queries and the virtual InfoProvider Function Module are defined to read all Configuration Items of a ConfigStore.
This enables the user to run a report for some Configuration Items, get the result and display afterwards other or all
Configuration Items of a given ConfigStore.

5.3 BI Queries
The queries which are used by Configuration Validation are listed in the appendix, first section 'Involved BI reporting
objects'. The additional query 0SMD_VCA1/0SMD_VCA1_SINGL_CONFSTORE can be used in transaction RSRT or
in BEx Analyzer to check the data. This query has additionally the characteristics 'Cf. Item Value Info', which is only for
some ConfigStores filled, and 'ConfigStore Valid To', which should always be filled and provides the information about
the time stamp of the last successful update of the ConfigStore. Changes on Configuration Items done afterwards are
not available in our validation. All other queries do not have these two characteristics in the drill down, but as free
characteristics. So the user can drill down those characteristics to see the additional information.

SAP AG 2008
End-to-End Diagnostics 63
User Guide - Configuration Validation

The following screen shot shows a part of the result of the query 0SMD_VCA1/0SMD_VCA1_SINGL_CONFSTORE for
the ConfigStore ABAP_TRANSPORTS:

The displayed timestamps are in UTC time zone and have the following format:
YYYYMMDDHHMMSS
<Year><Month><Day><Hour><Min><Sec>
nd
For example the transport request B74005677 was imported at 20081002181007, which means October 2 2008 at
18:10:07 UTC. The text after the timestamp is the description of the transport request. The ConfigStore
ABAP_TRANSPORTS was updated for the last time at 20081009175959, which means October 9 th 2008 at 17:59:59
UTC. Only those transport request imported before this time stamp are available in the reporting.
If you would like to create your own queries based on the InfoProvider 0SMD_VCA1, it is important to know that these
queries must have some characteristics and restrictions via variables otherwise they will not work. Please see the
screen shot of the Filter of the query definition:

0SMD_CSPN (Configuration Item) can be used in the 'Default Values' area. This means that all Items are read, but
only the items inserted here are displayed. The other items can be displayed according to the user navigation. The
same mechanism works for 0SMD_CSX1 (Compliance).
A restriction on 0SMD_CSPN (Configuration Item) which means that 0SMD_CSPN is inserted in the 'Characteristic
Restriction' area of the 'Filter' is not handled in the combination ST 400 Sp 18 and BI_CONT 7.04 SP01 (EhP1). The
next Support Package combination ST 400 Sp 19 with BI_CONT 7.04 SP02 will be able to use this selection.

SAP AG 2008
End-to-End Diagnostics 64
User Guide - Configuration Validation

0SMD_CSNS (ConfigStore Name) can be restricted either via a variable or by a fixed restriction to one or more
ConfigStores. Patterns are no evaluated. If no ConfigStore restriction is given, the Items of all ConfigStores are read.
This may take several minutes or even longer per system depending on the throughput of the solution manager
database.
As the evaluation of the configuration compliance needs the Configuration Item and value information the query must
have additional the characteristics 0SMD_CSPN and 0SMD_CSPN and of course 0SMD_CSID for the System:

The compliance information of an item of a comparison system is available, if the characteristic 0SMD_CSX1 is
inserted in 'Rows'. You can get the number of compliant values by using a restricted key figure. Use the key figure
0SMD_COUN and restrict it on 0SMD_CSX1 equal 'Yes'. If 0SMD_COUN is restricted on 0SMD_CSX1 not equal 'Yes'
('Yes' excluded) the number of not compliant values is the result. Several options may be used to display the
compliance information.
Please verify that the query uses the Read Mode 'A Query to Read All Data At Once'. This can be done using the
transaction RSRT in BI client. Select the query and press 'Properties'. This is the same property dialog which also
offers to define, how a query should use the OLAP cache.

SAP AG 2008