SAP
In this SAP note, I would like to describe how a developer can catch different types of exceptions for the API to prevent it from failing or making unnecessary calls that will fail with an error. SAP BTP API Management has various standard tools that will allow me to achieve
SAP
Hey, everyone! I won’t take much of your time today. I want to share a useful tip that could save you time, especially if you’ve just started developing with SAP BTP. Before we dive in, I’d like to remind you about several posts I published earlier. You
event type
SAP BTP provides an important service that allows you to monitor iFlows activity within the BTP tenant. The service I am referring to is SAP Alert Notification Service for SAP BTP. What Is SAP Alert Notification Service for SAP BTP? SAP Alert Notification service offers a common API for providers
SAP
Have you ever encountered challenges while monitoring processed iFlow messages to identify errors and track their custom status with specific values? See Overwriting standard BTP iFlow header parameters If so, I'd like to share information that can simplify the developer's life during investigation and analysis. Scenario
SAP
Regardless of your area of expertise within SAP, whether it's HCM or PM (Plant Maintenance), you may encounter IDOCs used for various business needs. The steps outlined below can help you understand what is required to process an IDOC developed in the SAP on-premise system and consume it
SAP
I would like to describe a peculiar behavior of SAP BTP regarding iFlows with HTTP requests inside. Let me provide further details. Initial set up I have an iFlow that triggers an API and returns a JSON containing the request data. For some reason, I decided not to expose the
SAP
In this post, I would like to consider a sequence of steps required for restricting access to iFlows within the BTP instance. Preface As you probably know, an Integration Flow could be triggered via the generated endpoint URL that you can find in the corresponding tile on the Monitoring dashboard.
SAP
I would like to present an example of the iFlow containing the PGP Encryption step, followed by further message storage in the DataStore. Requirement Develop an iFlow to process the sent data, encrypt it with the PGP public key, and save it in the DataStore. Step #1. PGP Keys Before
SAP
This post addresses a common challenge encountered when working with SAP BTP Integration Suite — specifically, passing parameters to iFlows using the 'Header' section of the message. Let's walk through an example to illustrate the issue. Step #1. Create the simple iFlow Begin by creating a straightforward
SAP
This note delves into the capabilities of an essential API Management engine that empowers developers to extend their API's functionality. Specifically, it focuses on policies. I may explore the most commonly used policies in future posts. See Policy Types Scenario Imagine you need to append specific values to
SAP BTP
If you utilize API Management within your SAP BTP instance, you may encounter or have already experienced a lack of API monitoring data on the Integration Suite dashboard. When navigating to Monitor -> API section within Integration Suite, you might observe a display similar to the screenshots provided below:
SAP
Let's dive into deploying a simple REST Controller to the BTP Cloud Foundry Instance. If you have a trial BTP account, this will be a great opportunity to follow along and understand the process. Hopefully, by the end of this tutorial, not only will I have a clearer