Skip to main content
ComponentsEngineJS ProfilerMobile AppRPA Bot RecorderRUM JS
Availability2022.1 or later

Supported components

Native coverage and limits

Configure real-user monitoring

Browser profile for SAP app

Configure log and file monitoring

Custom parsers for SAP logs

Configure business-process monitoring

Build processes from events
Configure Monitoring for SAP Configure GermainUX to monitor supported SAP browser interfaces and the surrounding technical environment. Depending on the components deployed, GermainUX can monitor: This guide assumes that the required GermainUX components have already been deployed for SAP.

​
Supported components

GermainUX does not natively:
  • Instrument or profile ABAP code
  • Debug ABAP execution in real time
  • Automatically extract data from every SAP transaction or administration tool
  • Automatically collect SAT, ST12, ST05, ST03N, or ST22 data
  • Automatically trace browser activity through ABAP and database execution
  • Parse every SAP log, dump, or proprietary file format
  • Monitor every SAP database without an appropriate supported database monitor
These capabilities may require a custom API, file, log, script, or database integration. The GermainUX Code Profiler can be used only for supported runtimes associated with the SAP environment, such as a separate supported Java application. It does not profile ABAP.

​
Configure applications and environments

Create clear application and environment definitions for the SAP interfaces being monitored. Examples include:
Keep production, test, development, and separate SAP interfaces distinguishable. Do not imply that creating a data source automatically enables complete monitoring of that SAP layer. Each monitor still requires a supported collection method and valid configuration.

​
Configure real-user monitoring

Go to: Germain Workspace > Analytics > UX Monitoring Profiles Select the profile created for the SAP browser application. Configure:
  • Application
  • Environment
  • Monitored URLs
  • Session settings
  • User identification
  • Page and logical-view naming
  • Clicks and interactions
  • Network requests
  • Browser errors
  • Session Replay
  • Privacy
  • Sampling
  • Feedback
  • Business-process events

​
Browser coverage

RUM JS can monitor browser-accessible content in the context where the script executes. Coverage depends on:
  • Script placement
  • Same-origin restrictions
  • Frames
  • Content Security Policy
  • SAP application architecture
  • Browser security
  • User consent
A script deployed inside one SAP application does not necessarily monitor the complete Fiori launchpad or other applications. Applications inside inaccessible cross-origin frames normally require separate monitoring. Fiori and SAPUI5 applications can change views without full page loads. Configure logical page detection if the default browser navigation does not identify these transitions correctly. GermainUX should not be described as automatically recognizing every Fiori application, SAPUI5 control, route, or business object. SAP-specific naming may require custom extraction rules.

​
User identification

Where permitted, configure approved identifiers such as:
  • Username
  • Role
  • Department
  • Business unit
  • Location
The availability of these values depends on what the SAP page exposes to the browser and what the organization permits GermainUX to collect. Do not collect passwords, authentication tokens, session cookies, or unnecessary personal information.

​
Configure Session Replay

Configure:
  • Replay enablement
  • Sampling
  • Maximum duration
  • Input masking
  • Text masking
  • Element exclusion
  • Page exclusion
  • Consent
  • Retention
  • Access control
Session Replay reconstructs captured browser activity. It is not a video recording. Content inside protected cross-origin frames may not be available for replay.

​
Configure browser-side error monitoring

RUM JS can collect supported browser-side conditions such as: Use these classifications: Do not classify every SAP message, validation dialog, HTTP failure, or console entry as an application error.

​
Configure browser diagnostics

Use the JS Profiler when standard RUM data is insufficient to diagnose a browser-side issue. The JS Profiler can analyze: It cannot analyze: The page currently titled “ABAP & Browser Real-time Debugger for SAP” should be renamed:
Configure Browser-Side JavaScript Diagnostics for SAP
All references to Apex, eScript, or ABAP profiling should be removed from that page.

​
Configure HTTP endpoint monitoring

The Engine can execute generic HTTP checks against reachable SAP endpoints. For each supported endpoint, configure: This can monitor the availability or functional response of a known SAP HTTP, REST, OData, or SOAP endpoint. It should not be described as complete SAP API observability unless the required endpoints, authentication, response extraction, and data models have been configured.

​
Configure log and file monitoring

The Engine can monitor files that are: Configure: Do not claim that GermainUX automatically understands every SAP log format. A custom parser may be required to extract meaningful SAP-specific fields.

​
Remove incorrect Siebel configuration

The existing SAP Application Monitoring page contains configuration copied from Oracle Siebel documentation. Remove references to: These are not valid generic SAP monitoring concepts.

​
Configure crash and dump monitoring

The Engine can detect the creation of files in a monitored directory and collect approved metadata. This can be used to detect: Do not claim that GermainUX parses SAP binary core dumps or ABAP short dumps unless an appropriate parser or integration has been implemented. ST22 collection should be described as a potential custom integration, not a standard capability.

​
Configure database monitoring

Use an existing GermainUX database monitor only when the database technology and GermainUX version are supported. Potential capabilities depend on the database monitor and can include: Do not state that SAP HANA monitoring is included unless the available GermainUX release contains and supports a HANA-specific or compatible monitor. Use a dedicated read-only monitoring account.

​
Configure server monitoring

The Engine can monitor supported operating systems through available mechanisms such as WMI, SSH, or another supported collector. Potential metrics include: This is host monitoring around SAP. It should not be described as SAP application-server internals unless SAP-specific collection is configured.

​
Configure business-process monitoring

GermainUX can build business processes from events collected by RUM JS, Engine monitors, or custom integrations. Examples might include: However, these processes are not discovered automatically merely because SAP monitoring is enabled. For each process, configure: GermainUX can then measure:
  • Completion
  • Abandonment
  • Process duration
  • Step duration
  • Repetition
  • Errors
  • Overruns
  • Lost productivity
The accuracy of these KPIs depends on the quality and completeness of the configured events.

​
Configure synthetic monitoring

Use the RPA Bot Recorder to create Selenium scenarios for supported browser-based SAP applications. Examples include:
  • Open the login page
  • Sign in
  • Open the Fiori launchpad
  • Launch an application
  • Perform a read-only lookup
  • Validate an expected result
  • Sign out
Synthetic scenarios require:
  • Dedicated test credentials
  • Stable selectors
  • Safe test data
  • Functional validations
  • Execution infrastructure
  • Scheduling
  • Alert configuration
Do not describe synthetic monitoring as supporting native SAP GUI unless a separate supported automation mechanism exists.

​
Configure feedback

The RUM JS feedback feature can be enabled on browser-based SAP pages where RUM JS is running. Feedback can be correlated with:
  • Session
  • Page
  • Browser event
  • Error
  • Performance
  • Session Replay
Feedback availability depends on script placement, page access, privacy policy, and popup configuration.

​
Configure outlier detection

Outlier detection can be applied to SAP-related KPIs after sufficient data has been collected. Examples include:
  • User-interaction duration
  • Page duration
  • HTTP response time
  • Business-process duration
  • Error volume
  • Host or database metric
Outlier detection does not independently discover undocumented SAP internals. It operates on data already collected by configured monitors.

​
Configure correlation

GermainUX can correlate data when compatible identifiers are collected. Potential attributes include:
  • Timestamp
  • User
  • Session
  • Request ID
  • Correlation ID
  • Transaction ID
  • Application
  • Environment
Do not claim automatic end-to-end tracing from the browser through ABAP and the database. Such tracing requires:
  • Compatible identifiers
  • Instrumented or observable components
  • Collection of those identifiers
  • Correlation rules
  • Validation of clock synchronization
Without those elements, GermainUX can provide time-based and contextual analysis but not deterministic distributed tracing.

​
Configure dashboards and alerts

Use the KPIs produced by the configured data sources to build dashboards for:
  • User experience
  • Browser errors
  • Business processes
  • Synthetic availability
  • HTTP endpoints
  • Logs
  • Hosts
  • Supported databases
Configure alerts only after confirming:

​
Validation checklist

Confirm that:
  • Every claimed KPI has a real configured data source.
  • RUM JS runs in the intended browser context.
  • Cross-origin limitations are understood.
  • SAP navigation rules identify the required views.
  • Sensitive data is protected.
  • JS Profiler data is described only as browser-side telemetry.
  • No ABAP profiling is claimed.
  • No Siebel terminology remains in SAP documentation.
  • HTTP checks validate only configured endpoints.
  • Log parsing matches the actual file format.
  • Dump monitoring claims match the implemented parser.
  • Database monitoring is supported for the actual database.
  • Business processes use explicit event definitions.
  • Synthetic monitoring is limited to supported browser interfaces.
  • Correlation claims match the identifiers actually collected.
  • Alerts use verified KPIs.

​
Get More Information

GermainUX can help determine which monitoring, analytics and automation capabilities are appropriate for your Salesforce Experience Cloud environment. Contact GermainUX Support.

​
Get Help

Contact GermainUX Support

The GermainUX team helps you get up and running faster, empower your team, turn data into actionable insights, and optimize performance to deliver measurable business outcomes.

Can't find what you need?

Search all GermainUX docs with Ctrl + K, or use the feedback buttons at the bottom of this page to tell us what is missing.

The content of this document is proprietary to GERMAIN SOFTWARE.