Browser Real-time Debugger for SAP (Configure)

⚙️ Configure Browser-Side JavaScript Diagnostics for SAP

Use the GermainUX JS Profiler to collect advanced browser-side diagnostic information from supported SAP web applications.

This capability helps investigate JavaScript errors, browser freezes, long-running operations, slow user interactions, and network problems affecting SAP users.

It does not debug or profile ABAP code.

📋 Prerequisites

Before enabling browser-side diagnostics:

👥 Supported SAP interfaces

The JS Profiler can analyze browser-side activity in compatible:

Coverage depends on where the profiling component executes, browser support, same-origin restrictions, frames, and application security policies.

The JS Profiler does not monitor native SAP GUI desktop activity.

🔍 What the JS Profiler analyzes

The JS Profiler can collect supported information about:

The exact detail depends on the browser, profiling method, duration, sampling configuration, and application architecture.

🚫 What it does not analyze

The JS Profiler does not directly analyze:

Use the GermainUX Engine to collect supported server-side logs, HTTP telemetry, database metrics, or custom SAP telemetry.

🚀 Enable JavaScript profiling

Go to:

Germain Workspace > Analytics > UX Monitoring Profiles

💡 Steps

1. Select the SAP monitoring profile.

2. Open the configuration editor.

3. Select JavaScript Profiling Monitoring.

4. Enable profiling.

5. Select the profiling method supported by the environment.

6. Restrict profiling to the required users or pages.

7. Save the profile.

Depending on the GermainUX version, UX Monitoring Profiles may appear under Settings > Analytics.

✅ Select a profiling method

🔧 JS Profiler browser extension

Use the supported GermainUX JS Profiler extension when browser-side profiling cannot be enabled directly through the application.

Deploy the extension to:

The browser may display a notification while profiling is active. If the user dismisses that notification, profiling may stop for the current page or tab.

⚡ JavaScript Self-Profiling API

Where supported, profiling can use the browser’s JavaScript Self-Profiling API.

The monitored page must return:

Document-Policy: js-profiling

The header must be present in the page response. It cannot be granted by client-side JavaScript after the document loads.

Browser and policy support must be validated before using this method.

🎯 Target profiling

Avoid enabling continuous profiling for every SAP user unless its overhead, volume, security, and privacy implications have been reviewed.

👤 Include selected users

settings.plugins.jsProfiling.includedUsernames = [
    "sap-diagnostic-user"
];

❌ Exclude selected users

settings.plugins.jsProfiling.excludedUsernames = [
    "restricted-user"
];

An undefined or empty list means that the corresponding restriction is not applied.

Only use identifiers approved by the organization’s privacy policy.

💻 Target selected applications

Restrict profiling by:

Use the smallest scope that can reproduce the problem.

⚙️ Configure profiling

Available settings include:

Example:

settings.plugins.jsProfiling.maxProfileDuration = 30;
settings.plugins.jsProfiling.sampleIntervalMillis = 20;
settings.plugins.jsProfiling.maxSampleBufferSize = 1000;
settings.plugins.jsProfiling.profileOnPageReady = true;
settings.plugins.jsProfiling.useSelfProfilingAPI = true;
settings.plugins.jsProfiling.includedUsernames = [
    "sap-diagnostic-user"
];

Apply these settings before starting RUM JS:

germainApm.start(settings);

Longer profiling durations, shorter sampling intervals, and broader user coverage can increase browser overhead and data volume.

🔁 Reproduce an SAP browser problem

1. Enable profiling for the selected diagnostic user.

2. Start a new browser session.

3. Open the monitored SAP application.

4. Perform only the actions required to reproduce the issue.

5. Record the approximate reproduction time.

6. Close the diagnostic session or disable profiling.

7. Open the corresponding session in GermainUX.

8. Review the browser and JavaScript telemetry.

Analyze:

Profiling samples can help identify expensive browser-side functions. They should not be described as guaranteed line-by-line execution tracing.

🔗 Correlate with other telemetry

Where compatible identifiers and data are available, correlate browser diagnostics with:

This correlation must be configured and validated. It does not provide automatic browser-to-ABAP distributed tracing.

🔒 Privacy and security

Configure:

Do not collect:

Browser profiling must not be used to bypass SAP, browser, or organizational security controls.

✅ Validate the configuration

Confirm that:

🛑 Disable profiling

When the investigation is complete:

1. Open the SAP UX monitoring profile.

2. Select JavaScript Profiling Monitoring.

3. Disable profiling or remove the included users.

4. Save the profile.

5. Remove the extension or response header if it is no longer required.

6. Confirm that new profiling data is no longer collected.

🔧 Troubleshooting

❔ No profiler data appears

Verify:

⛔ The browser reports a policy violation

Confirm that the document response includes:

Document-Policy: js-profiling

If the header cannot be added, use the supported JS Profiler extension instead.

🐢 Profiling increases browser overhead

Reduce:

You can also increase the sampling interval.

ℹ️ ABAP information does not appear

This is expected. The JS Profiler collects browser-side JavaScript and network telemetry only.

📖 Related documentation

ℹ️ Get More Information

GermainUX can help determine which monitoring, analytics and automation capabilities are appropriate for your SAP environment.

Contact GermainUX Support.