Book Image

Architecting Solutions with SAP Business Technology Platform

By : Serdar Simsekler, Eric Du
Book Image

Architecting Solutions with SAP Business Technology Platform

By: Serdar Simsekler, Eric Du

Overview of this book

SAP BTP is the foundation of SAP’s intelligent and sustainable enterprise vision for its customers. It’s efficient, agile, and an enabler of innovation. It’s technically robust, yet its superpower is its business centricity. If you’re involved in building IT and business strategies, it’s essential to familiarize yourself with SAP BTP to see the big picture for digitalization with SAP solutions. Similarly, if you have design responsibilities for enterprise solutions, learning SAP BTP is crucial to produce effective and complete architecture designs. This book teaches you about SAP BTP in five parts. First, you’ll see how SAP BTP is positioned in the intelligent enterprise. In the second part, you’ll learn the foundational elements of SAP BTP and find out how it operates. The next part covers integration architecture guidelines, integration strategy considerations, and integration styles with SAP’s integration technologies. Later, you’ll learn how to use application development capabilities to extend enterprise solutions for innovation and agility. This part also includes digital experience and process automation capabilities. The last part covers how SAP BTP can facilitate data-to-value use cases to produce actionable business insights. By the end of this SAP book, you’ll be able to architect solutions using SAP BTP to deliver high business value.
Table of Contents (22 chapters)
1
Part 1 Introduction – What is SAP Business Technology Platform?
4
Part 2 Foundations
8
Part 3 Integration
12
Part 4 Extensibility
16
Part 5 Data to Value

IAM in SAP BTP

Securing applications does not mean you deploy them and let them run on their own in a box that no one can access. Someone will have access to the applications, but can it be just anyone? Maybe, but you might need to control this by only letting certain people have access to your application. But then, among those who are allowed to access the application, should everyone be able to use every capability and see every piece of data? Alternatively, should there be a further control level that only lets a subset of these people use a specific feature?

It looks like we are establishing a control mechanism that revolves around the people, that is, the users, and their access levels to the application. Defining this mechanism through a framework of policies and implementing technologies for operating this mechanism is called IAM.

In order to let some people have access or not have access to an application, the first step is to distinguish one from another. For this,...