onedevatlasBeta
Browse the atlas
AllBTPCAPUI5ABAP
SampleSampletypeA worked example you read or clone. Evidence: it demonstrates, it never provides.See every one →What this type is →by SAPby SAPoriginPublished by SAP itself. A visible facet, never an input to a reading — a dormant official plugin reads exactly like a dormant independent one.See every one →Reference

SAP-samples/cloud-sample-webhooks

A pair of Java servlets that relay alerts from SAP BTP's Neo environment to an on-premise system through the Cloud Connector.

An alert raised for an application on SAP BTP's Neo environment stays in the cloud unless something forwards it. The project contains two servlets, one used for the webhook functionality that is uploaded on the cloud and another for the on-premise processing of the received alerts; for the connection between the Neo environment and the on-premise backend system you configure a Cloud Connector and a destination. It is tied to a step-by-step tutorial for Java Web Tomcat 9, and expects Maven, an Eclipse IDE set up with the SAP BTP Tools for Java and the SDK, and active resources to receive alerts for. It is offered as-is: the project states that no support is provided and that no changes will be made.

GitHub3 ★

Facts

Last pushLicenceApache-2.0

Where it sits

Lives in
BTP/BAIP
Demonstrates
Operations automationBTPOperations automationcapabilityActing on a running landscape without someone at the console: an alert routed to where a person or a system will pick it up, and a command that troubleshoots or remediates when it arrives. [Logging](capability:logging), [telemetry](capability:telemetry) and [health checks](capability:health-checks) observe; this acts on what they report. Running an application's own recurring work is [job scheduling](capability:job-scheduling).
Requires
Cloud ConnectorCloud Connectorartifactthe connection that carries the forwarded alert from the Neo environment to the on-premise backend system

Who is behind it

SAP SamplesSAP SamplesOrganisationMaintains this
In the atlas: maintains 222@SAP-samplesmaintainerAjinkya PatilPersonContributes to this
In the atlas: contributes to 112@ajinkyapatil8190Brian BernardPersonContributes to this
In the atlas: contributes to 64@btbernardJonathan BakerPersonContributes to this
In the atlas: contributes to 9@jonathanbaker7kdayradzhievPersonContributes to this
In the atlas: contributes to 1@kdayradzhievNikola SimeonovPersonContributes to this
In the atlas: contributes to 1@nikolasimeonov77Yavor MladenovPersonContributes to this
In the atlas: contributes to 1@yamladenov6 contributors

What it declares

Every artifact

Type
Sample
Origin
By SAP
Use as
A reference

As a sample

Form
A tutorial's companion code

Connections2

README

quoted from SAP-samples/cloud-sample-webhooks under Apache-2.0, read
SAP-samples/cloud-sample-webhooks/README.mdOn GitHub

Use Alert Webhooks from Cloud to On-Premise Monitoring

REUSE status

Description

The cloud to on-premise project helps you configure a connection so that you can receive your alerts locally. This project contains two servlets, one used for the webhook functionality that is uploaded on the cloud, and another for the on-premise processing of the received alerts. For the connection between SAP BTP, Neo environment and the on-premise backend system, you need to configure a cloud connector and a destination.

Requirements

  • You have a global account and a subaccount. See Getting Started.
  • You have active resources (applications) to receive alerts for.
  • You have installed Maven.
  • You have downloaded and set up your Eclipse IDE, SAP BTP Tools for Java, and SDK. See Setting Up the Development Environment.
  • You have set up Java Web Tomcat 9 as a runtime environment. See Java Web Tomcat 9.
  • You have downloaded and initially configured the Cloud Connector. For this tutorial, you can use the portable version. See Cloud Connector.

Download and Installation

Download the project as a ZIP file and then extract it into a local folder. Finally, import the folder into Eclipse as a Maven project. See Tutorial: Receive Alerts in Your On-Premise System Using Java Web Tomcat 9.

Configuration

Build a WAR file from Eclipse and deploy it on SAP BTP, Neo environment. You also need to deploy the WAR locally on your on-premise system. Furthermore, you need to configure the cloud connector and the destination. See Tutorial: Receive Alerts in Your On-Premise System Using Java Web Tomcat 9.

Support

This project is 'as-is'. We do not provide support and will not make changes. You are welcome to make changes to improve the project but we are not available for questions or support of any kind.

License

Copyright (c) 2026 SAP SE or an SAP affiliate company. All rights reserved. This project is licensed under the Apache Software License, v. 2 except as noted otherwise in the LICENSE file. See LICENSE.

Apache-2.0, read

Details

Sources3
Added by handdiscovered herechecked
github.com/SAP-samples/cloud-sample-webhookstree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
discovered viaAdded by hand
first seen in the atlas
ecosystem and domainbtp, operations-and-runtime
Contributors6
Ajinkya PatilBrian BernardJonathan BakerkdayradzhievNikola SimeonovYavor Mladenov

From the repository’s contributor list, .

History in the atlas1
  1. First seen.
For your agent
Ref
artifact:sap-samples-cloud-sample-webhooks
JSON
/artifacts/sap-samples-cloud-sample-webhooks.json
MCP
Connecting an agent