Page tree
Skip to end of metadata
Go to start of metadata


This document describes the use of Configuration Validation in the context of J2EE Software validation. The Configuration and Change database (CCDB; setup via RCA setup) collects for each technical system of type Java the information about the software level and the deployed objects from SLD. The deployed objects are collected there only, if the parameter "IncludeJ2EEDeployedObjects" is set to "true", see SAP note 1172265.

For the software level the Config Store called ‘J2EE_COMP_SPLEVEL’ is used and the Config Store ‘SAP_J2EEDeployedSCService’ contains the notified objects. The example uses a Solution Manager 7.10 where a development System (SD7 as DEV) and an integration system (SI7 as PROD) are connected to as managed systems. More information and details about Configuration Validation are available at

Use Cases:

It is planned to harmonize the J2EE software level of the landscape. All Java stacks should work with 7.02 Support Package 4. This is the SP level requested by SAP note 1442700. So it is necessary to know which systems are not on this Support package level.

You would like to deploy a new version of an object, e.g. of the application ‘tc~kw_tc’. For this you would like to know on which version of this object is deployed in the landscape.

Where can I find Configuration Validation?

Configuration Validation can be found in the Work Center Change Management in Related Links

Where can I find the used Config Stores and have a look at the data?

 Work Center Root Cause Analysis (RCA) > System Analysis > Change Reporting

The extraction of the data is scheduled as soon as a “Root Cause Analysis Set Up” has been performed for a system. Both Config Stores relevant for the use cases are assigned to J2EE-SOFTWARE.

J2EE_COMP_SPLEVEL contains information about the component and its release, extrelase and patch level. For most of the requests this is sufficient. If more detailed information is required about a single object and its version, the config store ‘SAP_J2EEDeployedSCService’ can provide it:

Additionally this Config Store collects information about objects that are not assigned to components of SAP support packages. These are displayed related to the component Default:

Remark: In Configuration Validation the contents of the 3 Key fields COMPONENT, OBJNAME and OBJTYPE is concatenated using the ‘/’ as separator and at the end to the configuration item, e.g. Default/

Availability of Config Stores SAP_J2EEDeployedSCService

The content of those config stores is retrieved from SLD.
Starting with SLD Release >= 7.10 the default setting has been changed in a way that these data is no longer processed.

However, it's possible to turn on the processing of these data in newer releases!

Turn on with care

Description: „IncludeJ2EEDeployedObjects: If set to true, deployed objects will be included in the J2EE instances. Typically, the number of deployed objects on a J2EE engine is very high, so this may lead to a performance problem. Default value: false “
We expect that if you add not more than 100 J2EE engines you should not face such performance issues on SLD side.

Add parameter to SLD (>= 7.10)

It's necessary to add a parameter to SLD:
SLD UI SLD UI - Administration - Settings - Section „datasupplier“ auswählen -> „Add Parameter...“

Section: datasupplier
Name: IncludeJ2EEDeployedObjects
Type: boolean
Value: true


In order to perform all configuration validation examples it’s most convenient to create a target system upfront. If you have an existing system with the target configuration already, you can skip this step.

Configuration Validation > Target System Maintenance > Create

Create Target System from selected Stores, enter System ID and Description and Save.

Result: the target system BP_JS_1 is created.

Edit the target system BP_JS_1:

It is possible to reduce the number of configuration items and to adjust the content. If you like to use the target system as it is, skip this step.

Click on the store name J2EE_COMP_SPLEVEL

Mark some lines and delete all selected items at once .

Save it .

In the screen shot the PATCH_LEVEL is 0. This is also the patch level the SAP note 1442700 is requesting for the component SAP-JEECOR. Otherwise it would be possible to adjust the value.

Comparison of SAP-JEECOR level and reporting on object version

*Is the software level of the component SAP-JEECOR as requested by SAP note 1442700?
Config Store J2EE_COMP_SPLEVEL, Component SAP-JEECOR

*Which object versions are assigned to the deployed application tc~kw_tc?
Config Store SAP_J2EEDeployedSCService, Item Default/

SAP-JEECOR level Select your target system and the validation report

The report 0TPL_0SMD_VCA2_CITEMS_REF provides compliant and non compliant items.


As reference system the target system BP_JS_1 is used. As comparison systems select SD7 and SI7.
Select the ConfigStore J2EE_COMP_SPLEVEL and execute.

In the result select ‘Select filter values’ using the context menu (right mouse click) of Config.Item

In the ‘Select Filter Value…’ screen select all items that are related to COMPONENT:SAP-JEECOR e.g COMPONENT:SAP-JEECOR;RELEASE:7.02; and Transfer your selection.

Our example shows two items with ‘Yes’ in the column ‘Compliance’, the component is on the same level as in the target system:

Remark: Instead of filtering the result via ‘Select Filter Value…’ it is an option to enter the value COMPONENT:SAP-JEECOR;RELEASE:7.02; in the variable screen of the report, if you are sure that all selected systems are on the same release, in our example 7.02.

How to get more details

Use from the context menu ‘Goto’, Config.Validation – Items – Validation Details. Right mouse click n an item for which you would like to see more details opens the context menu:

The report displays the validation details:

The other report offered in the context menu ‘Goto, CA – Changes Last 28 days’ would display the information whether the config store has recorded changes the last 28 days.

The column ‘Goto’ offers instead to display the config store content. Left mouse click on an entry

opens a new window:

The change reporting is called using a restriction on items that had been changed the last 28 days. The result displayed in the screen shows that the items of the Config Store had not been changed.
Please ‘History filter’ to deactivate the restriction on changes to display the current content of the Config Store. The screen shows the deactivated ‘History filter’:

Object versions of application tc~kw_tc Select your target system and the report

This example describes a report without validation as an additional option. The report displays the object versions of deployed application tc~kw_tc. This is just an example. Instead of tc~kw_tc any other object that is available in the Config Store SAP_J2EEDeployedSCService can be used.

Select the report 0TPL_0SMD_VCA2_VAR_REP_FLAT in Report Excecution

In the variable screen select the comparsion systems, the Config Store ‘SAP_J2EEDeployedSCService’ and the Item ‘Default/’:


Adjust result area:

Remove Drilldown of ‘Cf. item Value Info’, ‘Host Name’ and ‘Instance’ via the context menu (right mouse on e.g. ‘Instance’).
Add Drill down of ‘Cf. Item Value Part2’:

Swap ‘System’ with ‘Cf. Item Value Part2’
Right mouse click on ‘System’, from context menu select ‘Enhanced Menu’, then ‘Swap System with’ -> ‘Cf. Item Value Part2’ and get the result:

The result shows that the object has a different version in the system ST7 compared to the other systems of the report.
Remark: The ‘Last Check [UTC]’ column displays the timestamp of the Config Store, except of our target system BP_JS_1 which we had created before. The Config Stores of the target systems do not have a timestamp.

This page is part of the Application Operations Wiki. Notice that Application Operations itself is a use-case of SAP Solution Manager

  • No labels

1 Comment

  1. How to create a Target System for Configuration Store J2EE_COMP_SPLEVEL

    The Configuration Store J2EE_COMP_SPLEVEL has only two key fields COMPONENT and RELEASE, but EXTRELEASE is not key field. All conditions need to look different concerning the key fields.

    Therefore we need a trick to enter multiple distinct key conditions for a specific combination of the software component and the release if we want to enter multiple conditions concerning patch levels.

    One possible solution is to use regular expressions which look different but address the same configuration items. The regular expressions (something)? match zero occurrences of something and can serve as an irrelevant distinct part of the key value.


    ( Regex ) LMCTC(7.50 18)?( = ) 7.50( = ) 18( >= ) 1( Ignore )
    ( Regex ) LMCTC(7.50 19)?( = ) 7.50( = ) 19( >= ) 0( Ignore )
    ( Regex ) LMCTC(7.50 20)?( = ) 7.50( >= ) 20( Ignore )( Ignore )