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

Deploy Monitoring for SAP

Cover SAP end to end

Deploy RUM JS for SAP

Browser-side SAP experience

Deploy the Engine for SAP

Connect APIs, logs, databases

Deploy the RPA Bot Recorder

Record Selenium SAP scenarios

​
Overview

Deploy GermainUX across the appropriate SAP access points to monitor real-user experience, business processes, browser performance, APIs, logs, infrastructure, databases, and synthetic user journeys. The required components depend on the SAP products, interfaces, and monitoring objectives in scope.

​
Supported monitoring layers

GermainUX can be used with supported browser-based SAP applications, including SAP Fiori and SAPUI5 interfaces, when the required monitoring component can be deployed.

​
Important JS Profiler limitation

The JS Profiler analyzes JavaScript and network activity within the user’s browser. It does not execute or directly profile server-side ABAP code. Use the Engine, SAP APIs, logs, traces, or other server-side telemetry to monitor ABAP execution and backend processing. Browser and server-side data can then be correlated when compatible identifiers are available.

​
Plan the deployment

Before installing components, identify:
  • SAP products and versions
  • Browser-based applications and URLs
  • Production and non-production environments
  • SAP application servers
  • REST, OData, RFC, SOAP, and other integrations
  • Log and file locations
  • Database technologies and access requirements
  • Critical business processes
  • Expected user population and transaction volume
  • Network zones and firewall restrictions
  • Authentication and proxy requirements
  • Privacy, masking, and data-retention requirements
  • High-availability requirements for GermainUX components

​
Select the required components

​
Prerequisites

​
GermainUX environment

Confirm that:
  • GermainUX Cloud or on-premise is available.
  • The Workspace is accessible.
  • The required licenses and components are enabled.
  • The monitored environment can reach the GermainUX ingestion endpoints.
  • Appropriate users have access to configuration and dashboards.

​
SAP access

Obtain the access required for the selected monitoring layers:
  • Permission to modify or extend browser-based SAP pages, when using direct RUM deployment
  • Administrative access for supported browser extensions, when required
  • API credentials
  • Read access to approved log directories
  • Database monitoring credentials
  • Network access between the Engine and monitored resources
  • Dedicated synthetic user credentials
  • Approval for production data collection
Use dedicated service accounts and minimum required permissions.

​
Network requirements

Allow the required traffic between:
  • User browsers and GermainUX
  • GermainUX Engine and SAP APIs
  • GermainUX Engine and SAP hosts
  • GermainUX Engine and databases
  • Synthetic execution nodes and SAP applications
  • GermainUX components and the GermainUX platform
Review:
  • Firewalls
  • Proxies
  • TLS certificates
  • DNS
  • Load balancers
  • VPN requirements
  • Authentication gateways
  • Content Security Policy

​
Deploy RUM JS for SAP

RUM JS provides browser-side real-user monitoring for supported SAP web interfaces.

​
Capabilities

RUM JS can capture:
  • User sessions
  • Session Replay
  • Page and logical-view navigation
  • Clicks and user interactions
  • Browser errors
  • Unhandled promise rejections
  • Network and resource requests
  • Customer-perceived response time
  • Browser and device context
  • User feedback
  • Business-process steps
  • Heatmaps
  • Rage clicks and dead clicks
Session Replay reconstructs the browser experience from captured events. It is not a video recording.

​
Create the SAP profile

Go to: Germain Workspace > Settings > Wizards
1

Select SAP

2

Enter the application name

3

Enter the SAP application URL

4

Select or enter the environment

5

Configure the available privacy and monitoring options

6

Review the wizard summary

7

Complete the generated installation steps

Use a distinct application or environment value when production, test, development, or separate SAP applications must be analyzed independently.

​
Return to the installation instructions

You can reopen the generated deployment instructions:
1

Go to Germain Workspace > Analytics > UX Monitoring Profiles

2

Select the SAP monitoring profile

3

Open Installation in the configuration editor

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

​
Choose a RUM JS deployment method

The available method depends on how the SAP interface is hosted and controlled. Potential methods include:
  • Directly adding the generated RUM JS loader to the application
  • Using an SAP-supported application extension or shell integration
  • Deploying through an approved tag-management mechanism
  • Injecting through an authorized reverse proxy
  • Using a managed GermainUX browser extension when the SAP root page cannot be modified
Use the installation method generated by the SAP wizard or approved by GermainUX Support. Do not assume that code added inside an isolated component can monitor the entire SAP shell. The monitoring script must execute in a context with access to the required application activity.

​
Configure URL and application matching

Include:
  • Primary SAP application URL
  • Alternate hostnames
  • Load-balanced URLs
  • Launchpad paths
  • Locale-specific paths
  • Authentication redirects
  • Relevant embedded applications
Normalize dynamic routes and identifiers so the same logical SAP page does not appear as thousands of separate pages.

​
Configure user identification

Where approved, configure stable non-sensitive identifiers such as:
  • SAP username
  • User role
  • Department
  • Business unit
  • Location
  • Application role
Do not collect passwords, authentication tokens, or unnecessary personal data.

​
Configure privacy

Before production deployment, configure:
  • Text masking
  • Input masking
  • Element exclusion
  • Page exclusion
  • Request and response capture
  • URL and query-string sanitization
  • Session Replay sampling
  • Consent requirements
  • Data retention
  • Role-based access
Pay particular attention to employee, customer, financial, human-resources, healthcare, and procurement data displayed by SAP applications.

​
Validate RUM JS

1

Open the monitored SAP application

2

Sign in with an approved test account

3

Navigate through several pages or Fiori applications

4

Perform representative actions

5

Generate a safe validation message or test error when possible

6

Open GermainUX

7

Confirm that the session appears under the correct application

8

Verify pages, clicks, requests, errors, and replay

9

Confirm that sensitive values are protected

​
Deploy the Engine for SAP

The GermainUX Engine monitors SAP through supported APIs, logs, files, databases, and connected infrastructure.

​
Select the Engine location

Deploy the Engine on a host that:
  • Can reach the monitored SAP resources
  • Can reach the GermainUX platform
  • Meets the supported operating-system and runtime requirements
  • Has sufficient CPU, memory, and disk capacity
  • Uses synchronized time
  • Is monitored and maintained
  • Complies with network-segmentation requirements
For high-volume or segmented SAP environments, use multiple Engines based on location, workload, security boundary, or availability requirements.

​
Configure credentials

Create credentials for the required resources:
  • SAP APIs
  • Operating-system access
  • Log and file access
  • Databases
  • Integration endpoints
  • Proxies
Store credentials in the GermainUX credential configuration. Do not place passwords or secrets directly in scripts, URLs, or documentation. Apply least privilege and rotate credentials according to organizational policy.

​
Configure API monitoring

The Engine can monitor supported SAP endpoints for:
  • Availability
  • Response time
  • Status codes
  • Functional success
  • Error messages
  • Throughput
  • Authentication failures
  • Integration health
Potential interfaces include REST and OData endpoints and other supported integration services. For each endpoint, configure:
  • Name
  • URL
  • Method
  • Authentication
  • Schedule
  • Timeout
  • Success criteria
  • Response validation
  • Privacy rules
  • Alert thresholds

​
Configure SAP log monitoring

Identify the approved files and logs required for operational monitoring. Configure:
  • Host
  • File path or pattern
  • File encoding
  • Rotation behavior
  • Multiline-event rules
  • Timestamp extraction
  • Severity extraction
  • Error and warning patterns
  • Application and environment
  • Sensitive-data masking
  • Collection frequency
  • Retention
The Engine account should have read-only access whenever possible. Validate log rotation so events are neither missed nor collected more than once.

​
Configure database monitoring

The database configuration depends on the database used by the SAP environment. Monitor supported:
  • Availability
  • Connection success
  • Response time
  • Capacity
  • Sessions and connections
  • Locking and blocking
  • Long-running queries
  • Errors
  • Resource consumption
Use a dedicated read-only monitoring account and avoid executing expensive diagnostic queries at high frequency.

​
Validate the Engine

Confirm that:
  • The Engine is running.
  • It appears with the intended Engine name.
  • API checks complete successfully.
  • Log events are collected once.
  • Timestamps and severity values are parsed correctly.
  • Database connections work.
  • Credentials have only the required permissions.
  • Collected data appears under the correct SAP application and environment.
  • Alerts are not generated by test or setup noise.
For detailed instructions, see Engine Deployment for SAP.

​
Deploy the JS Profiler for SAP

Use the JS Profiler when RUM JS identifies a browser-side problem but additional JavaScript or network evidence is required. Deploy the JS Profiler to:
  • QA engineers
  • Application support
  • Selected diagnostic users
  • Test workstations
  • Controlled production users affected by a difficult issue
It is not required for standard SAP RUM or Session Replay.

​
Capabilities

The JS Profiler can provide deeper browser-side information about:
  • JavaScript execution
  • Long-running browser operations
  • Browser freezes
  • Network activity
  • Client-side errors
  • Browser objects and resources
  • Performance bottlenecks visible in the browser
It does not directly profile ABAP, SAP application-server processing, or database execution.

​
Deployment

1

Open the JS Profiler deployment instructions

2

Install the supported extension or profiling mechanism

3

Apply the SAP application and user targeting rules

4

Configure profiling duration and sampling

5

Restart or reopen the browser if required

6

Reproduce the problem

7

Confirm that profiler data appears in GermainUX

Browser security policies may display a profiling notification or require administrative browser policies. Validate the deployment with the organization’s security team. For detailed instructions, see JS Profiler Deployment for SAP.

​
Deploy the RPA Bot Recorder

The RPA Bot Recorder helps record Selenium-based synthetic SAP user scenarios. Record critical processes such as:
  • Open the SAP launchpad
  • Sign in
  • Open a Fiori application
  • Search for a customer, order, material, or document
  • Create or update an approved test record
  • Submit a workflow step
  • Validate that expected data is displayed
  • Sign out

​
Record a scenario

1

Install the RPA Bot Recorder extension

2

Open the target SAP application

3

Start recording

4

Perform the scenario using a dedicated test account

5

Add explicit validations

6

Replace unstable selectors where necessary

7

Remove sensitive test data

8

Save the Selenium scenario

9

Deploy it to the required synthetic execution node

10

Configure its schedule, timeout, and alert rules

​
Synthetic-account safety

Use:
  • Dedicated test accounts
  • Minimum required permissions
  • Reversible test data
  • A defined cleanup process
  • Non-production environments when possible
Do not automate destructive production actions unless the scenario has been explicitly reviewed and approved.

​
Validate synthetic monitoring

Confirm that:
  • The scenario runs unattended.
  • Authentication works.
  • Selectors remain stable.
  • Each step has an appropriate timeout.
  • Functional validations detect incorrect application behavior.
  • Screenshots and diagnostics exclude sensitive data.
  • Synthetic traffic is distinguishable from real users.
  • Failures generate the intended alert.
For detailed instructions, see RPA Bot Recorder Deployment for SAP.

​
Correlate frontend and backend monitoring

For end-to-end analysis, deploy both RUM JS and the Engine. Where supported and approved, correlate data using:
  • Session identifier
  • Request or correlation identifier
  • User identifier
  • Transaction identifier
  • Business document identifier
  • Application and environment
  • Timestamp
This can connect:
1

A user action in the browser

2

The resulting network request

3

SAP API or integration activity

4

Log events

5

Database activity

6

The final user-visible outcome

Do not use sensitive business-document identifiers for correlation unless necessary and approved.

​
Deploy business-process monitoring

Configure the SAP workflows that matter to the organization. Examples include:
  • Purchase requisition to approval
  • Purchase order creation
  • Sales order creation
  • Customer or vendor onboarding
  • Invoice processing
  • Expense approval
  • Inventory transfer
  • Material lookup
  • Service-ticket handling
  • Employee self-service
For each process, define:
  • Start condition
  • Completion condition
  • Required and optional steps
  • Failure conditions
  • Abandonment timeout
  • Expected duration
  • Application and environment
  • Correlation identifiers
  • Relevant user or business dimensions
Business-process monitoring can identify:
  • Lost productivity
  • Process overruns
  • Repeated steps
  • Abandonment
  • Errors
  • Slow system response
  • Ineffective workflows
  • Users or segments requiring assistance

​
Configure alerts and automation

After establishing a representative baseline, configure alerts for:
  • SAP application unavailable
  • Synthetic scenario failure
  • API failure
  • Log error increase
  • Database capacity or performance issue
  • User-facing application error
  • Silent application error
  • Business-process failure
  • Response-time degradation
  • Increase in affected users
Keep expected user validation separate from software failures. Automation can:
  • Send notifications
  • Create incidents or tickets
  • Run diagnostic scripts
  • Call approved APIs or webhooks
  • Generate recurring reports
  • Perform authorized corrective actions
Apply access controls, safeguards, auditability, and approval requirements before enabling automated remediation.

​
Production rollout checklist

Before completing the deployment, verify that:
  • Each SAP application and environment has a clear name.
  • RUM JS loads only once.
  • Real-user sessions appear in GermainUX.
  • Logical pages and SAP applications are identified correctly.
  • Session Replay captures the intended scope.
  • Sensitive values are masked or excluded.
  • User identification complies with privacy requirements.
  • API checks use minimum required permissions.
  • Log monitoring handles file rotation.
  • Database monitoring uses a read-only account.
  • JS Profiler deployment is limited to intended users.
  • Synthetic scenarios use safe accounts and data.
  • Synthetic traffic is excluded from real-user KPIs.
  • Frontend and backend data correlate where intended.
  • Alert thresholds use representative baseline data.
  • Test telemetry is distinguishable from production activity.

​
Troubleshooting

​
No browser data appears

Confirm that:
  • The RUM loader is installed.
  • The SAP URL matches the UX monitoring profile.
  • The browser can reach GermainUX.
  • Content Security Policy permits the required endpoints.
  • Consent allows collection.
  • The script executes in the correct application context.
  • The monitored SAP page is not isolated inside an inaccessible cross-origin frame.

​
Sessions appear but navigation is missing

SAP applications can update views without full page loads. Configure logical navigation and route detection for the SAP interface rather than relying only on browser page-load events.

​
Engine data does not appear

Verify:
  • Engine status
  • Network connectivity
  • Credentials
  • Proxy configuration
  • File permissions
  • Database permissions
  • API authentication
  • Application and environment mapping
  • Collection schedules

​
JS Profiler does not capture ABAP

This is expected. The JS Profiler collects browser-side JavaScript and network information. Use Engine-based server telemetry, SAP logs, APIs, or traces for ABAP and backend analysis.

​
Synthetic scenarios are unstable

Review:
  • Dynamic element identifiers
  • Frame and window transitions
  • Explicit waits
  • Authentication redirects
  • SAP UI changes
  • Test-data dependencies
  • Session timeout
  • Network latency
Prefer stable semantic selectors and explicit functional validations.

​
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.