Skip to end of metadata
Go to start of metadata

Overview

This page describes how alerts based on configuration items are integrated into the Alert Inbox. These kind of alerts are available with SAP Solution Manager 7.1.

The following alerts based on configuration items available in CCDB

  • Number of Transports
  • Number of ICF Service changes
  • Number of changed ABAP RFC destinations
  • Number of installed SAP notes

Those alerts would meet the term Change Analysis Alerting (shipped inactive, using the CCDB-Store-Change-Alert Provider), since it’s based only on the number of changes detected with Change Analysis.

  • Number of non-compliant items

This is the bridge to Configuration Validation, it basically allows to raised alerts based on a target system and its rule for compliance for configuration items

Starting with  SAP Solution Manager 7.1 SP6 the following alerts were added:

  • Expiring ABAP certificates
  • Failed ABAP transports
  • Global changes allowed
  • Users with critical profiles

Those are now based again Configuration Validation; A target system is shipped containing the rules for the config items.

Content

Alerts for systems of type ABAP based on preconfigured target systems

With SAP Solution Manager 7.1 SP06 four metrics are shipped which are active in the standard template. To avoid lots of alerts only the alert for ConfigStore PSE_CERT is active. That means that 4 metrics for configuration validation are collect by default but only the alert ‘Expiring ABAP certificates’ might be displayed in the Alert inbox. The alerts using the definitions defined in the SAP target system 0ALERT which is shipped with SP06. This target system has 4 ConfigStores. Each of the metric definitions restricts additional on one of these 4 ConfigStores. 0ALERT is defined like this:

The ConfigStores contain the rules for the compliant / non-compliant items:


ABAP_TRANSPORTS

AUTH_PROFILE_USER

GLOBAL

PSE_CERT

Remark: The operator ‘>(today + x)’ checks whether the VALID_TO of the managed system item is larger than (today + 30 days).
If the value is greater the item is compliant.

If the value is smaller or equal the item is non-compliant and an alert is raised.
(More details in method IS_PARA_VAL_GT_TODAY_X (CL_DIAGCV_VAL_TAB_STORE)

The Alert inbox restricted on Configuration should look like shown in the screen shot below. The marked lines are related to Configuration Validation:

Expiring ABAP certificates

Details (Mark the line and choose Show Details in screen above)

This screen shows that the information is created per instance. The Text Value provides the information about which target system has been used and the number of Items and the figures of validation.
Reference:0ALERT;VIRTUAL; #Items (NonCompliant/Compliant/NotFound/NotValuated/All): 3/32/0/0/35

Mark one instance line and get the option for more details in the ‘Configuration Validation BW Report’ or in transaction STRUST:


 Remark: To get rid of ‘empty’ PSEs please apply the correction of SAP note 1757010.

Definition in Template:


Defined as ‘Metric Group’ to get the alerts per instance!

The URL is inserted in this special in the Metric Definition tool (http(s)://<solman_host>:<port>/sap/bc/webdynpro/sap/wdc_definition_hier?sap-client=<solman client>&sap-language=EN)

Insert URL ‘DIAGCV_BW_REP’ (which had been created in url app framework), the default configstore is PSE_CERT and should (has to) be adjusted for the other metrics:



Back to template. The ‘Data Collection’ is defined to collect alerts for PSE_CERT once a day.

 0ALERT is the ‘Reference System’:

Store name ‘Expiring Certificates’ will be replaced by PSE_CERT during assignment:

Failed ABAP transports

The current status is green which means that the last extraction did not find a failed transport. Overall 5 Alerts had been generated before. The ‘Start Date and Time’ and ‘End Date and Time’ is related to the time when the alert was triggered. Mark one line and ‘Show Details’ to get more information, The Value Text provides the time range (UTC) when the failed transport has been imported:

In the example 3 transports have been imported with a return code greater 4 in the red marked time range (above).

Mark the line and get the link to the reporting

The Configuration Validation Report runs a validation restricted on the current day and the day before.

Remark: We do not have the alert generation time frame available for the link and the reporting offers only restriction on day. For alerts that are not in this date range, the report will not be able to find the transport requests responsible for the alert. In this case the URL of the Text Value can be used or the restriction of the report adjusted using the context menu, …, variable screen:


Execute and get

Add characteristics ‘Return Code’ and ‘Target Client’ (Navigation Block):

 and get

Click on a request name and get the Change Reporting:
Remark: Change Reporting displays the time stamp according to the SAP Solution manager time setting.

Mouse click on a request will display the object list, if the user is authorized in the managed system and the web service cts_objectlist_browser is available and active.

Definition in Template:

Extraction is done hourly.

The configuration validation is done for the alerting time range – 1 hour. The alerting time range goes from last alert extraction to current alert extraction.

Global changes allowed

Show Details provides a link to the transaction SE03 of the managed system and a link to the Configuration Validation BW Report:



Definition in Template:

Users with critical profiles

Show Details (example)

In Client 200 configuration validation has identified 244 users with a critical profile assigned (in default SAP_ALL is searched only), in client 001 182 users found.

Mark a line to get the link to the Configuration Validation BW Report:

Remark: The report is not restricted to a client. It displays the users with critical profiles assigned of all clients of the managed system. However, you could drill down the client info.

Definition in Template:

It is defined as Metric Group to get alerts per Client.

Data Collection – Store name

Defined as Parameter in the DataProvider UI

http(s)://<solman_host>:<port>/sap/bc/webdynpro/sap/wd_mai_dpc_main

RFC (Pull)

How to adjust the definition

The reference system (target system) 0ALERT is defined in a way that it should be valid for most of the alerts. However, customer may want to adjust the definition to use e.g. exceptions or other values. This example uses for the expiring certificates alert 20 instead of 30 days.

Here is how this can be achieved:

Step1

Step 1 is to create a target system, copy 0ALERT. Start Configuration Validation in RCA workcenter:

Press Edit

Enter 0ALERT, check ‘SAP Target System’, Press ‘Display selection’ and get:

Create a copy

Enter a name and save:

Next action is to select your system

Click on PSE_CERT, Click on the Valid_TO entry or any other content and get

Adjust the value, e.g. to 20, Apply changes, Save:

Step 2

Assign your target system to an Alerting Template and assign it to the managed system.

Run Solution Manager Configuration (SOLMAN_SETUP) -> Technical Monitoring -> 4 Template Maintenance:

Expand ‘Technical System’. Select e.g. ‘SAP ABAP 7.00 – 7.03 and press Edit

Press ‘Create Custom Template

Enter or adjust Name, save it. Afterwards press ‘Expert Mode’:

Select the Metrics Tab strip, in the table mark the metric ‘Expiring PSE certificates per instance’. Press ‘Change Setting. Select the Data Collection Tab strip in the Details view:

Adjust the content of the ‘SID…’: Replace 0ALERT by the name of your target system e.g. BP_ALERT and save it.

Press Next (next to the save button) and select the scope:

Press Next. In the Setup Monitoring screen, press ‘Assign Templates’, select your template.

Finally ‘Apply and Activate’ to get it used.

How to get an Alert for ‘Failed ABAP Transports’, ‘Global changes allowed’ or ‘Users with critical profiles’

The alert is defined in the ‘SAP ABAP …’ Templates not as active:

Create a copy of the template or use the copied template that is already assigned to the managed system for which you would to get the alerts. Set the Active flag and save the template.
Next steps are: Define Scope, Setup Monitoring and assign it to the managed system.

Alert on "number of non-compliant items"

The metric ‘number of non-compliant items’ is (including the alert) is not active by default. It could be used to add a target system including rules on configuration items and to get an alert if non-compliant items are identified.

Copy the SAP standard template and set it active AND assigned a target system (Data Collection, Add Variant in Expert Mode!).

Setup

Transaction SOLMAN_SETUP, Technical Monitoring, Option System Monitoring
(or Workcenter Solution Manager Administration -> Link Configuration -> 

Solution Manager Configuration; then Technical Monitoring ->  System Monitoring)

Define Scope

Define Scope, select a system.
Next

On higher SP versions the template handling is in step 4 and step Define scope is then step 5 and so on.

.
Template: Select basis setting and Create ‘Custom Template’. Adjust name, e.g.  if needed deselect active

(Attention: In 5 only one template can be assigned. ‘Change Setting, switch on ‘Expert Mode’, Add variant (Adjust Time restriction, deactivate all others)

Check, if ACTIVE flag is set (below Alerts tab)

Save it.

Assign the template to the system

This template can be assigned and activated via “Assign Template” & “Apply and Activate”

Flag MO-specific controls if the template is applied only to the assigned system. It would be possible to assign different target system to different systems

Alerts for techncial systems of type J2EE / missing metric goup

With SAP Solution Manager 7.1 SP05 a metric, but not a metric group related definition for J2EE is shipped.

This means that the figures (Non-compliant, compliant etc.) are combined which are created per ConfigStore of the target system assigned to the metric. The figure ‘All’ may not fit to the sum of the other figures. As long as only one ConfigStore is used in the target system no issue would be visible. With SP06 the configuration validation metric is shipped as metric group.

The approach described below can be used also for all other technical system types like ABAP. The SID for the Reference System for Configuration Validation in Data collection is the important setting.

Starting with SP05 a Custom Template can be created and then a custom metric of type Metric group can be created supporting to display the non-compliant information per ConfigStore.

The text below describes how to create the metric group and the alert.

The first step is to create ‘Custom Template’. This option is available in Edit mode only. Press the Edit button in Technical Monitoring of the Solution Manager Configuration:

After that select the ‘Technical System’ -> SAP J2EE 7.00 – 7.02  (e.g.)

Enter a name for the Custom Template and save it.

Now change the Custom Template.

Start with the alert. Select the Custom Template, press ‘Expert Mode’, in Edit Mode (button has the text ‘Read Only’) to get the ‘Create’ button active:

Now select the ‘Alerts’ tab strip. Create -> Alert

Enter a Name and Select the Category ‘Configuration’:

Remark: Do not Group Individual occurrences controls whether an Alert Entry is created per Config Store used in the target system or only one Alert for the target system.

Activate the ‘Others’ tab strip and enter a Technical Name

Press ‘Next’ and ‘Finish’. After that ‘Save’:

Depending of the system setting there may a dialog asking for a package. Select Local object, except the template should be transported:

Define the Metric as in the screen shot, Enter a Name and Description:

Remark: Raise Alert per Variant is only relevant, if more than one variant (Target System is assigned)

For ‘Data Collection’ define the Collection Interval, Data Collector and Data Provider ‘Configuration Validation’ to get the Collector Input Parameters:

Now ‘Add Variant’. Enter ‘VIRTUAL’ for Installation Number and the name of the target system of Configuration Validation (MA_JAVAL in the example):

Data Usage:

As threshold select Threshold Type ‘Numeric Threshold (Green/Red)’:

In Others tab strip enter a technical Name e.g. CUST_CONVAL:

And press ‘Next’.

Select the Assignment and Finish:

Finally ‘Save’.

Assign this template to the J2EE system for which the alert should generated.

Alert for ABAP Transports with SAP Solution Manager 7.1 SP08

There have been complains about a situation that the metric ‘Number of Transports’ shows 0 and is green, but ‘Failed ABAP Transports’ is grey at the same time, like in screen shot:

The metrics using different time frames.

Number of ABAP Transports

Number of ABAP transports uses the time frame between the second last und last config store extraction time stamp (second last timestamp is managed by the extractor). The alert runs every 4 to 6 hours.

Failed ABAP Transports

Failed ABAP Transports uses the time frame between last alert execution time and current alert execution time (no time frame management by extractor). However, a safety buffer of on hour is used to avoid that failed transports may overlooked. That means, the time frame which is used is exactly:

From “last alert execution – 3600s” To “current alert exection – 3601s”

Avoiding grey alerts

With SP08 the alert on failed ABAP transports gets green when no transports are found AND the last config store extraction is newer then the used alerting time frame for failed transports.

Prerequisites

Authorizations

The user of the extraction framework resource manager batch job (select in SM37 on ABAP program name:   E2E_EFWK_RESOURCE_MGR; if more jobs with different names are running, delete one or assign the user SOLMAN_BTC to both jobs or SM_EFWK starting with SP05; mark one job and display step list (CTRL+SHIFT+F9) to find the users name) has to have authorizations for Configuration target systems and secured ConfigStores.

  • AI_DIAGE2E and AI_LMDB_OB are normally already assigned;
  • ACTVT=03 needed, other fields *.

For Configuration Validation SM_CV_TASM and AI_CCDB_SC are needed:

  • SM_CV_TASM
          ACTVT             03
          CV_TARSYS    *
          CV_TUSER       *
  • AI_CCDB_SC
          ACTVT             03
          CONT_AUTH     SECURITY

The role SAP_SM_CV_EXTRACTOR with this authorization is shipped starting with SP06.

DPC PULL CORE extractor

The ST extractor has to be running, otherwise release it:
It’s in Workcenter Solution Manager Administration -> Infrastructure -> Alerting Framework

If the DPC PULL CORE extractor for ST does not exist, please install it, see appendix.

The other job that has to run is normally called SAP_ALERT_CALCULATION_ENGINE is related to the ABAP Program ACE_CALCULATION_CONTROLLER.

SP03: Check whether Note 1671723 Missing Component "Period" in Structure E2E_RESULT is needed.
Additionally for SP03-SP05 apply note 1710702

Appendix

How to check whether it is working from framework pint of view?

Function Module E2E_CONFIG_VAL is called from the alerting extraction. It calls DIAGCPL_CV_ALERT_1 which calls DIAGCPL_COMPARE_ALERTING.

Report E2E_DPC_GET_DATA_CHECK

    SID                                 SQ7          (enter the extended SID)
    RFC Destination               NONE
    Collector Source               ST
    Dataprovider Implementation     E2E_CONFIG_VAL

Breakpoint  at

  r_dpc_read->get_data_check( IMPORTING return_status = return_status

In Method GET_DATA_CHECK (CL_E2E_DPC_READ)


me->retrieve_data( EXPORTING it_directory_input = lt_directory_input
                   IMPORTING et_metric_result   = lt_metric_result   ).

internal table lt_metric_result is filled properly ?

(it is visible in debugging mode that finally the fm E2E_CONFIG_VAL is called)

What is to be checked: Extractor Log:
Alerting-Framework (Workcenter Solution Manager Administration -> Infrastructure -> Alerting Framework), restrict extended context on ST:

DPC PULL CORE extractor for ST does not exist.

How to get it?

1. Solution manager is (was) not defined as "Diagnostic Relevant"

Please call the Solution Manager Configuration -> Managed Systems

Configuration -> Select the extrended system <SolMan> -> Choose ‘System Operations’, ‘Maintain System’
-->

Afterwards please call the Solution Manager Configuration -> Basis Configuration -> Configure Automatically
Choose the step "Basic DPC Configuration" and press the button "Execute Selected":

  • No labels