The ABAP workbench has a set of examples to show you how to make the best coding with regards to performance.
You can reach the examples in SE38 transaction by selecting menu Environment, Examples, Performance Examples. You then reach the performance examples demos screen.
On the left hand side you can choose a topic and double click on it. You then see 2 examples of implementation. By clicking on the Measure Runtime button:
Now the two examples are evaluated at runtime. At the bottom you can see the documentation and explanation on what is best to use.
Health Monitoring provides a functionality called Availability Monitoring wherein we can monitor:
HTTP Availability: Monitoring availability of URLs.
TCP Availability: Monitoring the availability of a TCP port or the availability of a host.
RFC Availability: Monitoring availability of RFCs specifically for measuring availability of an application server instance of an SAP system or the availability of a message server port of an SAP system.
In this blog we will explain how you can configure a HTTP Availability monitor to monitor availability of a URL.
Setup of URL availability monitoring
Step1: Assign Agent for data collection
The HTTP availability is measured by making a URL http or https call by a designated Simple Diagnostic Agent from your specific customer network in the Focused Run system.
The first step is to assign a Simple Diagnostic agent as the collector for this metric.
For this open the Health Monitoring App from the Focused Run launchpad.
Navigate to Configuration area by clicking on the button.
Expand the Customer Networks node and click on the button.
In the next popup select the agent from the list of all connected agents to this customer network.
Step2: Configure HTTP Availability Metric
In the Configuration area expand the metric node and click on the button for Availability under Metrics node.
In the next pop-up screen click on the button to add a metric.
In the next pop-up screen select HTTP Availability
Enter the following details for a basic URL Availability check.
Field
Description
Metric Name
A descriptive name for the metric
Customer Network
Select the customer network for which you want to create the metric
Collection Frequency
Specify the collection frequency, how frequently the check should be performed.
URL
Enter the URL to be monitored
Proxy
Enter the proxy detail if the URL is reached via a proxy from the customer network. Else select None.
Authentication
Enter the authentication type None or Basic or oAuth and enter the details based on authentication type.
Timeout
Period in milliseconds (ms) before a call fails.
Number of Retries
Number of times the data collector calls a URL until it receives a response.
You can also further customize based on type of call you want to do to the URL for instance sending a POST request. For details you can refer to the SAP documentation here.
Optionally you can also enable alerting and notification in the Alert section of the configuration.
After entering all the details save your configuration to activate the metric.
URL availability monitoring usage
To navigate to the URL availability monitors you can click on the Availability button in the navigation panel.
Or you can also navigate from home screen.
Upon navigating to the Availability monitor metric list you will see the status of all URL availability metrics configured. The metric list view shows us the number of days and hours since the URL is available or unavailable. It also shows us the response time when accessing the URL.
This way you can not only monitor the URL availability but also the performance of an URL with regards to the response time while accessing the URL.
OS process monitoring
With OS Process Monitoring functionality we can monitor the availability of critical OS level processes on any host.
With System Monitoring templates you can also activate custom metric for monitoring OS processes however this will be applicable for all system/hosts for which you activate the template.
For monitoring critical OS processes for specific hosts you need to setup using Health Monitoring functionality.
To access Health Monitoring functionality you can navigate to Health Monitoring app in the Focused Run launch pad.
Prerequisite for OS process monitoring
The only prerequisite for configuring OS process monitor in Health Monitoring is that you should have registered the host and deployed Simple Diagnostic Agent (SDA) on the host where you want to monitor the critical process.
Setup of OS process monitoring
For setting up the OS process monitor you need to navigate to the settings page of the Health Monitoring App.
In the settings area expand the metrics node and click on the pencil button (Edit Metric) for OS Processes.
In the OS Process edit metric screen click on Add Metric button to start creating the OS Process Metric.
In the OS Process edit metric screen click on Add Metric button to start creating the OS Process Metric.
Field
Description
Process Name
Name of the OS process. This parameter needs to be maintained as a regular expression. SDA will use this expression for searching for the respective OS process at OS level.
User (Optional)
You can further restrict the search for processes running through a specific user. You need to enter the name as a regular expression
Command Line (Optional)
You can further restrict by the specific command line with which the process is running . This is specifically useful if there are multiple processes running with the same name but you want to monitor the process which is running with a specific argument or parameter. This also needs to be maintained as regular expression.
Hostname
Name of the host where the process to be monitored. You can select from a list of all hosts connected (also SDA deployed) to the Focused Run system.
In the General Settings tab you can also specify the data collection frequency and the threshold. By default 5 minutes frequency and Already Rated threshold is set.
Optionally you can update the alert settings for this metric in the Alert Settings tab. By default alerting is active with medium severity.
After entering all details, to activate the metric click on Save button.
You can monitor all you OS process metrics in the OS Processes tab of the Health Monitoring App.
SSL certificate monitoring
You can configure monitors to monitor the SSL certificate of a URL using Health Monitoring functionality in SAP Focused Run system. This monitor measures the remaining validity (in days) of a SSL certificate for a https call to a URL. The URL is called by Simple Diagnostics Agent of a designated host in your customer network.
The Health Monitoring app also provides a separate section called as URL Certificate Monitor where in you can centrally monitor expiry of SSL certificates of any https URL.
To navigate to URL Certificates monitor you can click on the URL Certificate button as shown below in the navigation panel of the app.
Setup of SSL certificate monitoring
To configure URL Certificate monitors , navigate to the Configuration area, expand the Metrics node and click on the change button.
In the popup window click on the Add Metric.
In the Metric Configuration window enter the following details in the General tab.
Field
Description
Metric Name
A meaningful name to the monitor
URL
URL whose certificate to be monitored.
Proxy URL (Optional)
The Proxy URL if the URL is accessible via a proxy URL
Customer Network
The Customer Network to which this URL belongs. The designated SDA from this customer network will be performing the check.
Technical System (Optional)
You can optionally link this monitor to a specific cloud service you have registered in your LMDB. This is the Cloud Service you would have created if you are using AIM scenario for Cloud Service Monitoring. Select from the drop down.
Collection Interval
Frequency of data collection. Select from available options.
Threshold
Threshold for remaining days for expiry. By default 200 Days for Yellow and 100 days for Red.
Additionally and optionally in the Alert Settings tab you can activate alerting and notification settings as shown below.
That’s it, now your monitor is active.
Using SSL certificate monitoring
To monitor navigate to the URL Certificate tab in the Health Monitoring App.
You can also refer to this SAP documentation to know more about various features available with Focused Run Health Monitoring.
<< This blog was originally posted on SAP Focused Run Guru by Manas Tripathy and Frank Umans. Repost done with permission. >>
manage the figures you need for service availability management:
Uptime of the system
Planned and unplanned downtime of the system
All service availability management functions are present using this Fiori tile:
On the left hand side there is the menu with all options:
Service availability management definitions
There are 2 definitions we need to configure:
The outage customization
Service availability definitions
First we start with the outage customizing:
Make the required settings for planned and unplanned downtime.
Now you add a new service management definition:
Provide a name and validity date for the definition and use the + symbol to add systems for which the definition is relevant.
In the tab availability set the SLA threshold for the availability percentage:
If relevant you can set specific contractual maintenance time in the last tab:
Example of use for this tab: you are running your SAP system hosted on for example AWS or Azure. Those platforms can have scheduled maintenance as well. That is not in your control.
Carefully check your entries and definition before saving. They cannot easily be changed later!
You cannot delete an active definition. To make it inactive you need to change the end date of the definition to today, and then delete it next day.
Each system can only be in one SLA definition!
Classifying the outages
On the Outages overview you can see the outages. The outages can be 0, or there can be open and/or confirmed outages:
Click on the open alert to classify it (click once for the line, click on the line for the details):
Classify the outage (planned/unplanned) and set the status. Fill out the text to clarify. And then save the update.
Outage reporting
There are 2 main reports. The uptime and outage reporting. The uptime reporting shows how long your system is up since the last reported planned or unplanned downtime. This overview is not so useful.
The useful overview is the outage reporting which shows you the downtime per system and per month:
In the example above 1 system had outage, but that was short enough to still meet the SLA target. Availability was 99.64% versus SLA target over 99.5%.
<< This blog was originally posted on SAP Focused Run Guru by Frank Umans. Repost done with permission. >>
There will be planned maintenance on SAP systems, databases, operating systems and the below infrastructure. During this planned maintenance, you don’t want any alerts and mails from SAP Focused Run, since the application is not available for a planned time.
Using the work mode management function you plan these maintenance events.
Questions that will be answered in this blog are:
How can I set up planned maintenance for systems monitored by SAP Focused Run to temporarily suppress the alerts during maintenance?
How can I see the current maintenance and planned upcoming maintenance?
Can I make a public page for the IT calendar?
Planning maintenance
Goto the IT calendar and workmode management tile:
Select the system (or select multiple systems in one go) and create the work mode for maintenance, and immediately switch to Expert Mode:
With expert mode you can simply set start and stop date and time.
You also should check the scope (the system will make a proposal) and extend if needed:
After saving, you can send notification via mail on the planned maintenance:
You can now see the planned maintenance in the calendar mode.
Overview of upcoming events
If you are in the calendar mode there can be a lot of systems. The overview screen for upcoming events will filter on the systems which have maintenance mode planned:
Can I select multiple systems for planned maintenance in one go? Yes you can, this will save you a lot of time to input.
Can I make a recurring maintenance? Yes you can, in the scheduling screen mark the maintenance as recurring.
IT Calendar access for Non-SAP Focused Run Users
During the maintenance the alerts are suppressed. The same information can also be made generally available to serve as a IT calendar for all interested persons. This can be people for the IT department and the business. These users are mainly interested in planned downtime of the IT systems.
Use of the IT calendar for non-SAP focused run users
Create a system user with copy of role SAP_FRN_APP_ITC role and update it with the UI5 application “itcal_external”(IWSG and IWSV).
Also add these 4 not documented authorizations:
Display for service availability management:
2. Display for work modes:
3. Add generic services:
4. Add filter bar rights:
Activate and save this role.
Activate these 2 SICF services:
/default_host/sap/bc/bsp/sap/itcal_external
/default_host/sap/bc/ui5_ui5/sap/itcal_external
On the Logon tab of these 2 services set the user ID and password of the newly created system user.
Do the same for the external system alias /sap/itcalnonsolman (also in SICF transaction): also here set the user ID and password for the newly created system user with the assignment of the newly created role.
After settings are done, execute testing. Most issues are coming from lack of auhtorizations.
OSS note for IT calendar function
Relevant OSS notes:
2926433 – IT Calendar access to Non-SAP Focused Run Users
3150979 – Number of systems in scope is limited, while using External IT Calendar
<< This blog was originally posted on SAP Focused Run Guru by Frank Umans. Repost done with permission. >>
The SAP* activation is required in some cases. Systems that are protected well have the parameter login/no_automatic_user_sapstar set to 1 which will forbid the logon with SAP* (see also blog on SAP standard users). To use SAP* this parameter has to be set to 0, followed by system restart to activate it (the parameter is not dynamic). Often after using SAP* it is forgotten to undo the SAP* activation or to set the parameter login/no_automatic_user_sapstar to the secure 1 status again.
The new way described is available as of kernel release 790 and a separate tool with a short lived password only.
ultiple systems. Items that are part of the tactical dashboard is database backup status, performance, logged on users, software maintenance status.
Questions that will be answered in this blog are:
How to use the Focused Run tactical dashboards?
How to fine tune the tactical dashboards?
How to setup your own tactical dashboard?
Tactical dashboards usage
To start the tactical dashboard, click the corresponding Fiori tile:
You now reach the tactical dashboard overview screen:
By clicking the Expand Group icon at the right you get first level of details:
By clicking the tile you are interested in you get the details.
Examples are hardware resources for current week and last month:
Dialog response times:
Amount of logged on users:
And software maintenance status for detailed components:
An alternative for manageming software components is via Security and Configuration management. More details be found in this detailed blog. The tactical dashboard is nice for 1 system. The configuration validation tool is useful for overview of components across multiple systems.
Configuration of the tactical dashboard
By clicking the personalization button top right:
you will reach the configuration screen. Here you can add and delete systems from the overview:
And you can set the view properties and thresholds for each of the categories:
This fine-tuning you do as per your companies needs. By clicking on the Visibility symbol, you can hide an aspect from your overview. Like above the Database backup was put to invisible.
Creating your own tactical dashboard
You can create your own tactical dashboard for your own specific needs. We will take the example here to make a dedicated dashboard for the backups. Since we want to check daily in the overview if the backups were successful.
Start by clicking top left on the big + symbol to add a new dashboard:
The personalization view screen will open:
Important here are a few things. Set the tick box Public if you want to share this dashboard. Find the keyword for the right SAP icon (use the SAP icons link and read this blog). Rename the dashboard by clicking the Rename button.
Now Save the page. Close the personalization. You are now in the empty screen. Open peronalization again to add the system(s):
Also hide the not needed views. On the left hand side you can immediately see the result updating.
Hint: start with one or two systems only when making a new dashboard. First fine tune what you want to see. When all is ok, add the systems later. If you have a lot of systems, the updating of the left hand screen will be slowing you down.
Don’t forget to save off course.
Using a dashboard created by a different user
If you want to use a dashboard created by a different user, go to the personalization option and select the add page option:
Now you can select any created dashboard, which has been set to public.
If you don’t see the correct dashboard, check with the owner that he made it public.
When using Focused Run you monitor systems. But how about the health and stability of the monitoring tool itself? Here is where self monitoring plays an important role.
Questions that will be answered are:
What to check in self monitoring?
How much metrics are collected and stored in my Focused Run installation?
Self monitoring
Self monitoring can be started with the Self Monitoring Fiori tile:
If you click the tile the overview page comes (this page will take time to load):
The interesting part is unfortunately hidden in the below screen (you need to scroll), which is the CPU utilisation.
The other interesting part is the amount of data collected and stored. This is not so interesting for yourself, but more interesting for your manager to show how much data HANA can handle, or to show how much work is really automated.
Simple diagnostics agent
On the top left icons, click on the Simple DA agent button to get the agent overview screen:
Important here:
Check that all agents are up
Check that all agent versions are not too old
Monitoring and Alerting Infrastructure
The next option is to check the MAI (monitoring and alerting infrastructure) data collection:
Important here is to fix the systems in error.
Wily Introscope
The Wily option will show if your Wily Introscope connected to Focused Run is ok. Wily is used for special use cases like JAVA and Business Objects products.
Managed system overview
The managed system overview gives the overview of the diverse systems and application status:
Any red or yellow item can mean a setup issue. But it can also be because of missing authorizations and privileges of the Focused Run technical user in the connected managed system.
Central component monitoring
The central component monitoring shows the overview of the central components:
<< This blog was originally posted on SAP Focused Run Guru by Frank Umans. Repost done with permission. >>
When you have performed Simple System Integration (SSI) for the connected managed system on the Focused Run system, by default SSI itself activates the SAP early watch (EWA) reporting for a managed system, provided the managed system has IT Admin Role defined as Production system. For more information on how to set IT Admin Role read this blog.
For non productive systems you can also manually activate EWA.
Additionally for all ABAP systems (Production and Non-production), you will need to configure SDCCN in managed system so that EWA data is sent to the Focused Run system.
Note: In an Focused Run environment, EWAs are not generated on the Focused Run system, but rather at SAP side. Only data is collected at the Focused Run side and the EWA is then available in Service Messages at SAP. For accessing the EWAs you can navigate from the launchpad using the EWA Workspace tile. For more details click here or here.
Steps for activating EWA for ABAP Systems
STEP 1: Activate EWA on Focused run System
Goto Launchpad and click on the SAP Early Watch Alert Status tile.
In the EWA Status Application first you need to select scope to include all ABAP systems as shown below.
To activate EWA, change under Active column from NO to YES for the respective system.
After Activation status changes as shown below. Refresh after 5 minutes to ensure that the first circle is Green.
For this first create a HTTP destination from the managed ABAP system to Focused Run system using report /BDL/CREATE_HTTP . Provide the following input and execute the report.
HTTP Destination: By default, it shows as SDCC_SID, you’d better change the SID to the real target system id. This is the suggestion, but you can specify any name if you want.
SSL Status(HTTPS): This checkbox means whether you want to use HTTPS for the communication. By default, it will only use HTTP.
Path Prefix: By default, the service used by SDCCN is /sap/bc/sdf/sdcc/. You cannot change this unless you mark the checkbox “Force Mode”.
User Name: FRN_EWA_<FRUN SID> which you have created during the initial setup of FRUN system
Run report /BDL/CONFIGURE_SDCCN_HTTP to activate SDCCN. Provide the HTTP destination that created in step 2 and change the job user. Only the first check box must be selected (only on FRUN 1.0 both check boxes must be selected).
The job user must have authorization SAP_SDCCN_ALL
After running this report with above parameters, the SDCC_OSS RFC will be removed from RFC destinations, and the new HTTP destination will be added to RFC destinations.
STEP 3: Create Maintenance Package on SDCCN in Managed System
Now you need to create a maintenance package in transaction SDCCN of managed system.
To Ensure the EWA activation is properly completed, goto transaction SDCCN on the managed system and ensure that the EWA sessions for the managed system is registered.
When EWA Data is sent to Focused Run and processed at the SAP side, you will see all circles in Green for the respective ABAP system as shown below.
Activating EWA for JAVA Systems
Goto Launchpad and click on the SAP Early Watch Alert Status tile.
In the EWA Status Application first you need to select scope to include all java systems as shown below.
To activate EWA, change under Active column from NO to YES for the respective system.
After Activation status changes as shown below. Refresh after 5 minutes to ensure that the first circle is Green.
To Ensure the EWA activation is properly completed, goto transaction SDCCN on the FRUN system and ensure that the EWA session for respective Java system is registered.
When EWA Data is sent to FRUN and processed, you will see all circles in Green for the respective JAVA system as shown below.
EWA troubleshooting
In case of issues you can follow the link to the troubleshooting guide of SAP:
The integration and cloud monitoring function of SAP Focused Run consists of 2 main functions:
Cloud monitoring between on premise and cloud SAP products
Interface monitoring between SAP systems (read more on interface monitoring in this blog)
This blog will give an overview of the Cloud monitoring between SAP on premises systems and SAP cloud solutions.
Questions that will be answered in this blog are:
How does the Cloud monitoring in SAP Focused Run look like?
How much details and history can I see in SAP Focused Run interface monitoring?
Can I link an Cloud monitoring event to and alert?
Which Cloud monitoring scenarios are supported?
How to monitor message to and from SAP CPI?
How to setup the monitoring towards SAP CPI?
How to monitor message to and from SAP Ariba?
How to setup the monitoring towards SAP Ariba?
Cloud monitoring
To start the cloud monitoring click on the Fiori tile:
Select the cloud scenarios:
You now reach the scenario overview screen:
Click on the tile for details (we will take Ariba as example):
Click on the red line between the on premise and the cloud system:
Click on the red errors number for the error overview:
Click on specific error:
Supported cloud scenarios
Not all cloud products and scenarios of SAP are supported via SAP Focused Run Cloud monitoring. On the SAP Focused Run Expert Portal the following scenarios are currently published:
Read the scenario details carefully! Inside the details there might be less monitored than you were expecting.
CPI message monitoring
SAP Focused Run Cloud Monitoring can be used to monitor messages to and from the SAP BTP CPI solution. CPI stands for Cloud Platform Integeration.
End result of CPI message monitoring
The configuration of the scenario is described in the next chapter. We start explaining the end result.
Select the scenario and the overview tile appears:
Validate in the SAP Focused Run ABAP stack that these two parameters are set in RZ11:
icm/HTTPS/client_sni_enabled = TRUE
ssl/client_sni_enabled = TRUE
If this is done, go to the cloud setup FIORI tile:
Add a new end point for CPI:
The application key, client ID and client secret will need to be provided by the basis person or functional consultant maintaining the CPI interface configurations on the BTP cloud. Depending on the security setup, a proxy is required as well.
After entering the details check the connection that connectivity is working as expected.
Now go to the configuration of the interface scenario and create a new cloud service for Cloud Platform Integration:
On the monitoring screen specify filters for specific IFlows if requiered:
On the alerting tab you can set up any alerting wanted:
Set the filter for alerting (in this case all failed flows):
Assign alert receivers and make sure everything is saved and activated.
Now you can model the scenario graphically as well:
Cloud monitoring: Ariba
SAP Focused Run Cloud Monitoring can be used to monitor messages to and from the Ariba solution.
End result of Ariba cloud monitoring
The configuration of the scenario is described in the next chapter. We start explaining the end result.
Select the scenario and the overview tile appears:
Click on the card to go to the scenario topology:
Click on the red line to zoom into the communication error details:
Validate in the SAP Focused Run ABAP stack that these two parameters are set in RZ11:
icm/HTTPS/client_sni_enabled = TRUE
ssl/client_sni_enabled = TRUE
If this is done, go to the cloud setup FIORI tile:
Add a new end point for Ariba:
The application key, client ID and client secret will need to be provided by the basis person or functional consultant maintaining the Ariba interface configurations on the Ariba cloud. Depending on the security setup, a proxy is required as well.
After entering the details check the connection:
Now go to the configuration of the interface scenario and create a new cloud service for Ariba Network Transaction:
On the Monitoring tab connect to the end point create above and set the wanted filters:
If you want, you can also set up alerting in the third tab.
Save and activate the setup.
Now you can model the scenario graphically as well:
<< This blog was originally posted on SAP Focused Run Guru by Frank Umans. Repost done with permission. >>