Summary

• Kyma Environment

• Cloud Foundry Environment

• ABAP Environment

  • Technically, the ABAP environment lives within the Cloud Foundry (CF) environment

  • Supports ABAP RESTful Application Programming Model (RAP)

  • Based on the latest ABAP platform cloud release

• Lets you structure your global account

• Subaccounts are independent of each other

• You can choose your own region

• Account model can be built on functional areas

  • Subaccount A – Sales and Marketing

  • Subaccount B - Development

• Easy scaling

• Reduced maintenance and governance efforts

• cds init

• 3 Ordner: app, db, srv

• 1 Datei: package.json

• Core Data Service Definition Language (CDL)

• Human readable syntax for defining data models

• Unicode based data serialization language

• YAML is a strict JSON superset – this means all valid JSON files are valid YAML files

• Support for serializing arbitrary native data structures

• Whitespaces and “#” for comments

• Drive UX consistency

• Speed up development

• No unique functionality

• Fast development

• List Report

• Worklist

• Object Page

• Analytical List Page

• Users need to find and act on items within a large set by searching, filtering, sorting and grouping

• Users need to work with multiple views of same content

• Drilldown is rarely used

• Users have numerous work items

• Users need to work with multiple views of same content

• Direct entry point for taking action on work items

• Users need to extract key information to understand current situation

• Users need to find and act on items within a large set by searching, filtering, sorting and grouping, drilling down, slicing and dicing

• Multiple event handlers can be registered for each event phase

• The are executed in the order in which they appear

• Single event handler can also handle multiple events

• All services are event emitters

• Events can be sent to them – READ, CREATE etc.

• Events can be emitted by them

• Register event handlers with services to react to any event

• High Availability Setup – Main and Shadow instance

• Secure trace data – Secure sensitive network trace data

• Monitoring – State and activities of Cloud Connector

• Alerting – Send email alerts

• Audit Logging – View and manage audit log

SAP Cloud Connector component is required to connect SAP BTP to On-Premise system. You access the SAP Cloud Connector at the Subaccount level.

• Connectivity Service – Connectivity proxy to access on-premise resource

• Destination Service – Retrieve and store technical info about target resource

• When you create a Subaccount and enable CF runtime – System automatically creates a Cloud Foundry org

• Subaccount and org have a 1:1 relationship

• You can create multiple spaces within Cloud Foundry org

• In Cloud Foundry environment, you deploy applications and consume services at the space level

• npm add passport

• Definition in service.cds

• Module xssec und xsenv benötigt

• In SAP BTP, CF environment, a single authorization is called Scope

• Scopes cannot be assigned to users directly – They are packaged into Roles

• Scopes are prefixed with xsappname to make them uniquely identifiable

• Role has many Scopes

• Role-Collections contain 1 or more Roles

• Role-Collections can be assigned to a User

• Platform Users: Meistens Entwickler und Admins die Apps deployen, administrieren und Fehlerbehandlung betreiben (Ident. mit SAP ID Service)

• Business Users: Nutzen Apps, die auf der BTP deployed wurde. Also z.B. Business Application Studio

  
  

• Nutzer mit email, userid, Vor- und Nachname identifizieren

• Nutzerrollen prüfen, um Aktionen erlauben oder verbieten zu können

File that defines the details of authentication method and authorization types to use for access to your application

• Auth Scopes

• Attributes (undefinierte Info wie z.B. Name der Kostenstelle)

• Role Templates

File contains configuration information used by the application router, z.B.

• welcome file path

• session timeout

• routes

• Routes request from browser to CAP Service

• Routes request from browser to provider of UI sources

• Ensures authenticated and authorized users get token from XSUAA Service and forwards it to CAP Service

• csd add pipeline

• neue Dateien: Jenkinsfile + .pipeline/config.yml

• Developers push code to main code line at least once a day

• Automated central build and tests are triggered upon each push

• Team ensures stable build and test quality all the time

• Software is ready for deployment to productive system all the time

• Deployment to productive system is triggered manually

• Feedback from productive system gets integrated to teams’ backlog

Deployment to productive system is triggered with each commit (automatic)

Rest wie Delivery