Enable JAVA SNC Certificate monitoring in FRUN

As part of many SAP landscapes, Secure Network Communication (SNC) is used to establish secure communication between ABAP and Java systems. If your environment is running with SNC-based communication between ABAP and ME/MII Java systems using SNC certificates stored in Java security directory.

While SAP Focused Run (FRUN) provides extensive monitoring capabilities, we identified a monitoring gap: there is no standard FRUN template available to monitor validity of Java SNC certificates. This means an expired certificate could go unnoticed until communication failures begin occurring between connected systems.

To address this gap, we developed a custom monitoring solution in SAP Focused Run that automatically tracks Java SNC certificate validity, calculates remaining days until expiration, and generates alerts before certificate expires.

Business Challenge

Communication between ABAP and Java systems relies on SNC certificates for secure authentication and encryption.

Java SNC certificate was deployed in the following location:
/usr/sap//J**/sec/SAPSNCS.pse

Although certificate is critical for secure communication, there was no proactive monitoring mechanism available in Focused Run to track its validity.

This created following risks:

Unplanned certificate expiration
ABAP to Java communication failures
Potential business process disruption
Manual monitoring effort
Lack of centralized visibility

Objective was therefore to provide proactive monitoring and alerting through SAP Focused Run.

Solution Overview

Implemented solution performs following functions:

Reads SNC certificate from Java PSE file.
Extracts certificate expiry date.
Calculates number of days remaining before expiration.
Generates output in JSON format.
Sends value to Focused Run through a custom metric.
Raises alerts when configured thresholds are reached.

Architecture Overview

SAPSNCS.pse
│
▼
sapgenpse export_own_cert
│
▼
OpenSSL Certificate Parsing
│
▼
Remaining Days Calculation
│
▼
JSON Output Generation
│
▼
FRUN Custom Metric
│
▼
Alerting & Notification

SNC Certificate Location

SNC certificate used by the Java system is stored in:
/usr/sap//J*/sec/SAPSNCS.pse

This PSE file contains the certificate information required for SNC communication.

Extracting Certificate Expiry Date

SAP utility sapgenpse can export certificate directly from PSE file.

sapgenpse export_own_cert -p SAPSNCS.pse | openssl x509 -noout -enddate

Example output: notAfter=Sep 29 15:45:21 2027

This date is then used to calculate remaining certificate validity.

Custom Monitoring Script

Following shell script was developed to calculate remaining days before certificate expiry.

#!/bin/bash
SAPGENPSE="sapgenpse"
PSE_FILE="SAPSNCS.pse"
expiry_date=$(
$SAPGENPSE export_own_cert -p "$PSE_FILE" 2>/dev/null |
openssl x509 -noout -enddate |
cut -d= -f2
)
 
expiry_epoch=$(date -d "$expiry_date" +%s)
current_epoch=$(date +%s)
 
diff_days=$(( (expiry_epoch - current_epoch) / 86400 ))
 
echo "{"type":"integer","name":"NumDays","value":$diff_days}" \

/tmp/NUMDAYS.json

Sample Output

generated JSON file contains the certificate validity in days.

JSON
{
"type":"integer",
"name":"NumDays",
"value":30
}

This output can be consumed directly by SAP Focused Run custom monitoring metrics.

Creating a Custom Metric in FRUN

Step 1: Create a Custom Monitoring Script

Deploy the script on the managed host where SAPSNCS.pse exists.

Example location:

Shell

/usr/sap/SID/J**/sec/calc_sapsnc_validity.sh

Step 2: Configure Simple Diagnostics Agent Script Metric

Create a new metric.

Example:

ParameterValue
Metric NameSNC Certificate Validity
Collection TypeScript
Scriptcalc_sapsnc_validity.sh
JSON AttributeNumDays
Metric TypeNumeric

Custom agent metric was configured in SAP Focused Run to collect generated JSON value.

Metric periodically collects remaining validity days and displays them centrally in FRUN monitoring dashboards.

This provides sufficient lead time for certificate renewal activities before the certificate reaches its expiration date.

Monitoring Benefits

This implementation delivers several operational benefits:

Closes a monitoring gap in SAP Focused Run Provides centralized certificate visibility

Closes a monitoring gap in SAP Focused Run
Provides centralized certificate visibility
Eliminates manual certificate validation checks
Enables proactive alerting
Reduces risk of ABAP-Java communication failures
Improves overall operational readiness
Prevents service disruptions caused by expired SNC certificates

Lessons Learned

During implementation, one challenge encountered was script compatibility after transferring files from Windows to Linux systems. Script initially contained Windows CRLF line endings, resulting in execution errors.

Converting script to UNIX format resolved the issue:
dos2unix calc_sapsnc_validity.sh

Conclusion

Java SNC communication is a critical component for secure integration between ABAP and Java systems. Since SAP Focused Run does not provide a standard monitoring template for Java SNC certificate validity, organizations may lack visibility into upcoming certificate expirations.

By implementing a lightweight custom monitoring solution using sapgenpse, OpenSSL, and SAP Focused Run custom metrics, we successfully introduced proactive monitoring and alerting for Java SNC certificates.

This approach is simple to implement, easy to maintain, and significantly reduces risk of communication outages caused by expired SNC certificates.

Have you implemented custom certificate monitoring in SAP Focused Run or SAP Solution Manager? Feel free to share your experience and monitoring approaches in the comments.

HANA Cleaner Monitoring Setup in FRUN

Introduction

Maintaining SAP HANA systems requires regular housekeeping activities, and one of the critical components is the HANA Cleaner. Monitoring its activity ensures that log cleanup and housekeeping jobs are running as expected.

In this blog, it is explained how we implemented HANA Cleaner monitoring in SAP Focused Run (FRUN) using custom metrics via template maintenance, without requiring custom scripts. This approach leverages standard FRUN capabilities and provides a scalable and maintainable monitoring solution.

Solution Overview

The objective of this monitoring setup is:

  • Track the execution of HANA Cleaner jobs
  • Detect inactivity or failure scenarios
  • Alert operations teams proactively

We achieved this using:

  • Custom Metric based on File Monitoring
  • FRUN Template Maintenance
  • Diagnostic Agent (push) data collection

How It Works

The monitoring logic is simple but effective:

  1. The system monitors the last modified timestamp of HANA Cleaner log files
  2. A custom metric evaluates this timestamp continuously
  3. If no update is detected beyond a defined threshold (e.g., 2 days), an alert is triggered

This ensures immediate visibility into any issues with the HANA Cleaner process.

Implementation Details

Step 1: Create Custom Metric in FRUN

Navigate to:

Advanced System Management → System Monitoring → Template Maintenance

Create or enhance a metric such as:

HANA Cleaner Run Status

Category:

Exceptions

Step 2: Configure Data Collection

From the screenshot setup, the following configuration is used:

Data Collector Type

Diagnostic Agent (push)

Data Collector Name

File Information

Collection Interval

5 Minutes

Step 3: Maintain Collector Input Parameters

Here are the key parameters used:

Parameter IDDescription
DATEPATTERNDate format used (yyyy-MM-dd)
FILEPATTERNHANA Cleaner log file pattern
FOLDERPath to log directory
KEY_FIGMetric to evaluate
RECURSIVEEnable/disable recursive search

Actual Values Used

Plain Text

DATEPATTERN = yyyy-MM-dd

FILEPATTERN = hanacleanerlog_*

FOLDER = /usr/sap/${SAP_HDBSystemID}/${SAPSystemName}/hanacleaner/output

KEY_FIG = Last Modified age in seconds

RECURSIVE = False
Show more lines

✅ This configuration ensures the system monitors the latest file modification time in the HANA Cleaner output directory.

Step 4: Define Metric Logic

The key figure:

Last Modified Age in Seconds

This indicates how long it has been since the log file was updated.

Step 5: Threshold Configuration

Define thresholds based on your operational requirements.

Example:

ConditionThreshold
Green< 24 hours
Yellow24–48 hours
Red> 48 hours

This ensures alerts are triggered if HANA Cleaner hasn’t executed in expected time.

Step 6: Assign Metric to Template

Assign the custom metric to:

  • Relevant HANA systems
  • Both Production and Non-Production landscapes

This ensures full coverage across your environment.

Monitoring Output

Once configured, FRUN displays:

  • Historical trend of HANA Cleaner activity
  • Status indicators (Green/Yellow/Red)
  • Alerts in case of inactivity

From your reference screenshot:

  • The metric appears under Exceptions
  • A graph shows activity progression
  • Alerts are triggered if thresholds are breached
  • System Monitoring
  • (Optional) Root Cause Analysis

Coverage

This setup can be implemented:

  • Across the entire HANA landscape
  • For all S/4HANA or standalone HANA systems
  • In both:
    • Production
    • Non-Production environments

Advantages of This Approach

No Custom Coding Required
Uses standard FRUN capabilities
Can be applied across multiple systems via templates
Frequent monitoring (every 5 minutes)
Detects failures before business impact
Simple file-based monitoring logic

Key Learnings & Best Practices

  • Always ensure correct file path and pattern
  • Validate that Diagnostic Agent has access to directory
  • Fine-tune thresholds based on:
    • HANA Cleaner job frequency
    • Business requirements
  • Use template-based rollout for consistency

Conclusion

Monitoring housekeeping activities like HANA Cleaner is critical for maintaining system health. By leveraging FRUN custom metrics and file monitoring, we can implement an efficient, scalable, and proactive monitoring solution.

This approach eliminates the need for custom scripts while fully utilizing standard SAP monitoring capabilities.

SAP Focused Run 5.0 OCC Dashboard – Build Powerful Performance Monitoring Dashboards

Introduction:

In today’s complex SAP landscapes, organizations need real-time visibility, proactive monitoring, and actionable insights to maintain system performance and availability. SAP Focused Run (FRUN) provides advanced monitoring capabilities, and one of its most powerful features is the OCC (Operation Control Center) Dashboard.

The OCC Dashboard enables SAP teams to visualize key metrics, monitor performance trends, and detect issues early—all through a flexible, customizable interface.

What is OCC Dashboard in SAP Focused Run?

The OCC Dashboard provides direct access to key technical and business metrics stored within SAP Focused Run. It is designed for SAP operations teams and business experts to create custom dashboards for deep analytics and monitoring.

Key characteristics:

  • Central web interface for dashboard configuration and visualization
  • Supports multiple data providers and monitoring sources
  • Ability to combine and filter multiple metrics in a single view
  • Flexible visualization using charts, tables, and trend analysis

Please find link attached for your reference-[support.sap.com]

How to Setup an OCC Dashboard (Step-by-Step)

Step 1: Launch Dashboard

  • Navigate to OCC Dashboard Fiori Tile
  • Open dashboard application

Step 2: Create Custom Page

  • Click “Add New Dashboard / Custom Page”
  • Rename with meaningful name (e.g., Performance Monitoring Dashboard)

Step 3: Define Layout

  • Choose layout (e.g., 2×2 grid or custom structure)

Step 4: Add Views / Widgets

  • Select visual components (charts, tables)
  • Drag and drop into layout

Step 5: Configure Metrics (Core Part)

  • Select Data Source (e.g., System Monitoring)
  • Choose:
  • System (SID)
  • Metric (CPU, Memory, Dumps, Response Time)

Step 6: Define Query

  • Add query using “+”
  • Assign legend name (e.g., Memory Utilization)
  • Configure filters & time range

Step 7: Choose Visualization

  • Line chart → Trends
  • Bar chart → Comparison
  • Table → Detailed analysis

Step 8: Save & Test

  • Validate data correctness

Step 9: Publish Dashboard

  • Make dashboard public for team usage.

Example: Performance Monitoring Dashboard

Dashboard Components:

  • CPU Utilization (Trend Chart)
  • Memory Usage
  • ABAP Dumps per Hour
  • Dialog Response Time
  • System Availability

How OCC Dashboard Helps in Performance Monitoring

1. Real-Time Monitoring

  • Quickly identify performance degradation
  • View metrics across systems in one place

2.Trend Analysis

  • Analyze historical performance trends
  • Detect recurring issues

3. Root Cause Analysis

  • Drill-down capability helps identify bottlenecks

4. Proactive Alerting & Insights

  • Predict issues before system failure
  • Improve system reliability

5. Custom KPI Tracking

  • Track business-relevant KPIs alongside technical metrics

Business Value of OCC Dashboard

  • Reduce downtime and performance issues
  • Improve SLA compliance
  • Faster issue resolution
  • Centralized monitoring for large SAP landscapes
  • Supports high-volume system monitoring environments [support.sap.com]

Key Differences

FRUN 4.0

  • Focus on enhancing OCC dashboard functionality
  • Introduction of new data providers (Events, KPI tracking)
  • Improved visualization and analytics configuration

FRUN 5.0

  • Supports large-scale hybrid monitoring scenarios
  • OCC dashboard becomes part of:
  • Unified monitoring
  • Automation
  • Alert management ecosystem
  • Supports large-scale hybrid monitoring scenarios

Conclusion

The evolution from SAP Focused Run 4.0 to 5.0 in OCC dashboards represents a shift from advanced visualization to intelligent operations

  • FRUN 4.0 enhanced the OCC dashboard with stronger analytics, new data providers, and KPI-driven monitoring, making it a powerful visualization tool.
  • FRUN 5.0, however, elevates this capability by embedding the OCC dashboard into a broader, unified monitoring ecosystem—enabling end-to-end visibility across hybrid landscapes, integrated alert management, and scalable operations.

SAP Cloud ALM memory estimator

If you are running SAP Solution manager and are planning to move to SAP Cloud ALM, you can estimate the expected memory usage on SAP Cloud ALM. The first 24 GB are for free in the standard SAP contract. If you need more, you might need to acquire extra licenses.

Installation of the SAP Cloud ALM memory estimator

Check that OSS note 3639977 – Collective corrections as of ST-PI 7.40 SP32 and ST-PI 7.58 SP00 for SAP Cloud ALM is installed (or a newer ST-PI).

Check if report /SDF/CALM_MEMORY_ESTIMATION is available in your solution manager system.

Running the memory estimator

In your solution manager system run in SE38 the program /SDF/CALM_MEMORY_ESTIMATION. Choose a representative day (take a busy weekday, and not a weekend day).

Let the program run.

Show the results:

You now can see the total and the highest impacted areas.

Wily Introscope tips & tricks

Wily Introscope is used in SAP JAVA and BO(DS) systems for diagnostics and analysis. This blog will give tips & tricks for the Wily Introscope tool.

General KBA OSS note for Wily Introscope: 3013495 – Central KBA for Introscope (SV-SMG-DIA-WLY and XX-PART-WILY). General public websites is on this link.

Landscape considerations and restrictions

OSS notes:

Installation and support

OSS notes:

Be aware that Wily Introscope is a 3rd party product with short lifecycle. Typically only 1 year support.

Other relevant OSS notes



SAP Focused Run LMDB and landscape management

SAP Focused Run LMDB is a great source of technical information. Especially with the new graphical view.

In SAP Focused Run LMDB is now part of Landscape Management.

LMDB administration (up to FRUN5.0)

With the LMDB administration page you can see the LMDB status:

Green is ok:

If not green, check the status for needed actions.

LMDB object maintenance

The LMDB Object Maintenance tile can be used to maintain a single LMDB entry:

Now select the system on the LMDB search screen:

And then push the button Display to go to the details:

On the left side you can choose a specific view on the system, like software, database, technical instances etc. If you click on the left side, the right side will show the details.

LMDB tools and graphical overview

The LMDB tools offer a graphical overview. First open the LDMB tools FIORI tile:

In Focused Run 5.0 there is a new tile for this:

Then select the technical system (in Focused Run 5.0 the main overview opens, and you need to select the technical systems on the left):

Now press the blue Hierarchy button to go to the graphical overview (in FRUN 5.0 simply click on the blue system name):

On the left is the graphical decomposition. On the right the details per object selected on the left side.

FRUN 5.0 landscape management

In Focused Run 5.0 there is a new tile replacing the LMDB and called Landscape Management:

The start page is an overview of all your systems and its status:

The other LMDB functions are still present on the left side of the screen.

API for LMDB

The SAP Focused Run LMDB has an API. For more details, read this blog.

LMDB updates

The LMDB updates are triggered automatically. This behavior can be changed in certain situations or even totally switched off. Read more on this SAP Focused Run export portal page. See also OSS note 3376303 – Support switch for disabling Agent deployments triggered by LMDB events for older versions.

Relevant OSS notes:

SAP Focused Run API’s

SAP Focused Run offers some nice API’s that you can use and re-use.

API’s available:

  • LMDB API
  • Work mode management API
  • Guided procedure API
  • Advanced analytics API
  • SSI API

LMDB API

The LMDB now has a REST API available to read data in structured way. You can search for hosts, technical systems, software components, installed product versions and instances.

The full specification for this API can be found on this link.

See also OSS note 3712330 – Enhance public landscape API for hosts by OPerating system name, release, software.

Ad hoc work mode creation via function module

Via function module FM_START_ADHOC_WORKMODE you can create an ad-hoc work mode to stop monitoring for a system. You can start monitoring again by stopping the work mode by calling function module FM_STOP_ADHOC_WORKMODE.

The full specification of all the work mode API’s can be found in the PDF attached to OSS note 2508346 – Work Mode Management API Documentation for Focused Run.

Triggering guided procedure via function module

Function module FM_EXTRN_GP_EXEC can be used to call a guided procedure. Unfortunately, you need to pass the GUID of the guided procedure to the function module.

The full guided procedure API can be found on this SAP page.

Advanced Analytics API

The specification for the Advanced Analytics API can be found here, and on this blog.

Service Availability Management API

The Service Availability Management has webservices available as API. The specifications can be found here.

SSI API

The SSI can be used to automated SSI activities. Explanation document of the API can be found by following this link. And example file; https://support.sap.com/content/dam/support/en_us/library/ssp/alm/sap-solution-manager/focused-solutions/demo-ssi-web-services.zip.

OSS notes:

SAP cases (incidents) overview

The me.sap.com has a nice overview for all your SAP cases (incidents).

Questions that will be answered in this blog are:

  • How can I get a nice KPI overview in PDF format on my SAP cases?
  • How can I get a list of all my SAP cases?
  • How can I get insights into aging SAP cases?
  • How can I get insights if the SAP cases are on our side, or at SAP side to solve?

Cases (incidents) overview

Go to https://me.sap.com/reporting/cases/ (part of the EWA workspace).

After opening you reach the dashboard you reach the KPI’s:

If you scroll down you get the easy list overview of all your cases:

From this list you can make an easy download to Excel.

KPI report in PDF format

Top right there is a button PDF report generator:

Follow the wizard and a nice PDF will be generated for you. Mock up of this PDF is so good that you can immediately share it with management.

EWA alert solutions

The SAP Early Watch Alert (EWA) report can contain valuable information on specific topics in your system that you must fix.

More information on the EWA workspace can be found in this blog.

General EWA tips and tricks can be found in this blog.

EWA alert solution finder

On the me.sap.com go to the specific page for EWA solution finder:

Action follow up is on the right hand side per alert:

You can choose:

  • Hide the alert (be very careful!)
  • Snooze the alert (see SAP blog)
  • Mail the alert

The snoozing is a very useful function. For example, you detect a red alert on HANA revision, but it will take you a month to implement (due to regression testing, process, etc), you can now snooze the alert for the implementation period:

After the implementation is done, the alert should be gone. If the implementation is delayed, you will be reminded again.