> ## Documentation Index
> Fetch the complete documentation index at: https://docs.germainux.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Application Monitoring for SAP (Configure)

> SAP Commerce Cloud—formerly SAP Hybris—can be monitored through its available browser, HTTP, Java, log, infrastructure, and synthetic access points.

Components
[`Engine`](https://docs.germainux.com/main/germain-ux-engine)
[`JS Profiler`](https://docs.germainux.com/main/germain-ux-js-profiler)
[`Mobile App`](https://docs.germainux.com/main/germain-ux-mobile-app)
[`RPA Bot Recorder`](https://docs.germainux.com/main/germain-ux-rpa-bot-recorder)
[`RUM JS`](https://docs.germainux.com/main/germain-ux-rum-js)

Availability
2022.1 or later

> [card] [SAP Commerce Cloud Monitoring](#sap-commerce-cloud-monitoring)
>
> Browser, HTTP and Java coverage

> [card] [Configure storefront monitoring](#configure-storefront-monitoring)
>
> Deploy RUM JS on storefront

> [card] [Configure OCC API monitoring](#configure-occ-api-monitoring)
>
> Endpoint checks, not internal visibility

> [card] [Configure Java monitoring](#configure-java-monitoring)
>
> When Java profiling applies

## SAP Commerce Cloud Monitoring

SAP Commerce Cloud—formerly SAP Hybris—can be monitored through its available browser, HTTP, Java, log, infrastructure, and synthetic access points.

### Environment coverage

The available coverage depends on whether the environment is:

| Environment | Notes |
| - | - |
| SAP-managed Commerce Cloud | Managed cloud environments may restrict access to servers, JVMs, logs, and databases. |
| Privately hosted |   |
| On-premise |   |
| A customer-controlled legacy SAP Hybris deployment |   |

### Supported monitoring capabilities

| SAP Commerce Cloud layer | GermainUX component | Capabilities |
| - | - | - |
| Storefront | RUM JS | Real-user monitoring, Session Replay, pages, clicks, errors, requests, heatmaps, feedback, and conversion journeys |
| Browser-side JavaScript | JS Profiler | Advanced JavaScript, browser, and network diagnostics |
| Storefront journeys | RPA Bot Recorder | Synthetic product search, cart, checkout, login, and account scenarios |
| HTTP and OCC APIs | Engine | Availability, response time, status, and configured functional validation |
| Accessible logs | Engine | Generic or custom log parsing |
| Customer-controlled servers | Engine | Supported host, process, service, and capacity monitoring |
| Customer-controlled database | Engine | Monitoring when the database technology is supported and access is available |
| Customer-controlled Java runtime | Code Profiler | Java method and transaction profiling when the runtime is supported and agent installation is permitted |

## Configure storefront monitoring

Deploy RUM JS on the SAP Commerce Cloud storefront to monitor:

* User sessions
* Session Replay
* Product and category views
* Product searches
* Add-to-cart and remove-from-cart actions
* Cart and checkout journeys

> [accordion] Show all 12
>
> * User-perceived performance
> * JavaScript errors
> * Failed browser requests
> * Rage clicks and dead clicks
> * Customer feedback
> * Conversion and abandonment

The exact events available depend on the storefront implementation and configuration.

For headless storefronts, deploy RUM JS in the customer-facing frontend application. The frontend may use Spartacus, another JavaScript framework, or a custom implementation.

## Configure conversion events

Potential commerce events include:

* Product Viewed
* Category Viewed
* Search Submitted
* Search with No Results
* Product Added to Cart
* Product Removed from Cart

> [accordion] Show all 11
>
> * Cart Viewed
> * Checkout Started
> * Checkout Step Completed
> * Checkout Failed
> * Order Completed

These events may require custom extraction or instrumentation. GermainUX does not automatically recognize every SAP Commerce Cloud event.

Use them to build funnels such as:

**1. Landing Page**

**2. Category Viewed**

**3. Product Viewed**

**4. Product Added to Cart**

**5. Cart Viewed**

**6. Checkout Started**

**7. Order Completed**

## Configure OCC API monitoring

The GermainUX Engine can execute HTTP checks against reachable SAP Commerce Cloud OCC or other supported endpoints.

Configure:

* Endpoint URL
* HTTP method
* Authentication
* Request headers
* Approved request body
* Timeout

> [accordion] Show all 10
>
> * Schedule
> * Expected status
> * Functional response validation
> * Privacy rules

This provides endpoint monitoring—not automatic visibility into the internal execution of every Commerce Cloud service.

## Configure Java monitoring

SAP Commerce Cloud and legacy SAP Hybris use Java-based server components. The GermainUX Code Profiler may monitor those components only when:

* The JVM and application server are supported.
* The organization controls the runtime.
* The profiler agent can be installed.
* The deployment is approved.
* The environment permits the required network communication.

Potential capabilities include:

* Java transaction tracing
* Method-level performance
* Errors and exceptions
* Outbound calls
* Database-call correlation
* Time spent in supported Java components

Do not claim Java profiling for SAP-managed Commerce Cloud environments unless SAP permits agent installation in that specific environment.

This Java capability applies to SAP Commerce Cloud or Hybris components—not ABAP.

## Configure log and infrastructure monitoring

For customer-controlled environments, the Engine may monitor:

* Accessible Commerce Cloud logs
* Web-server logs
* Application-server logs
* Integration logs
* Java process availability
* CPU, memory, and disk
* Supported databases
* HTTP endpoints

For SAP-managed cloud environments, monitoring is limited to the logs, APIs, metrics, and access points SAP makes available to the customer.

## Configure synthetic commerce monitoring

Use the RPA Bot Recorder to create scenarios such as:

* Open the storefront
* Search for a product
* Open a product page
* Add a product to the cart
* Start checkout
* Validate pricing or availability
* Sign in to a customer account
* Confirm that a critical page works

Use dedicated test accounts and safe test data. Avoid creating real orders unless the scenario includes an approved cancellation or cleanup process.

### Get More Information

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

[Contact GermainUX Support](https://docs.germainux.com/main/support.md).

## Get Help

> [card] [Contact GermainUX Support](https://docs.germainux.com/main/support.md)
>
> 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.

> [card] 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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.