The Correct Order of Thinking for a SAP BTP Admin

Posted by on

 “As an admin, what should I set up first?”

Environment? Entitlements? Marketplace? Spaces?

Most people have this confusion.

As an admin, your job is not to run an application.

Your job is to prepare the platform so that applications can run smoothly later.



Imagine this situation:

A project is starting.
Developers will build an application on SAP BTP.
You are the BTP admin.

Your responsibility is to set the stage, not to perform on it.


Step 1: Decide the structure



Where will this application live?

That means:

  • which Global Account 

  • which Subaccount (dev, test, prod)

  • which region


Step 2: Decide and enable the environment


What kind of environment does this application need?


  • cloud-native app → Cloud Foundry

  • ABAP extension → ABAP Environment

  • container-based app → Kyma



Step 3: Create spaces inside the environment


For Cloud Foundry:

  • spaces like dev, test, prod


Step 4: Assign entitlements


  • what services does this application need?

  • which plans?

  • how much quota?


Step 5: Check the service marketplace


Admins open the marketplace to:

  • verify entitlements

  • confirm service visibility

  • validate configuration

The marketplace is a mirror, not the starting point.



Step 6: Hand over to developers



After this:

  • developers create service instances

  • applications are deployed

  • services are consumed

Admins continue to:

  • manage access

  • monitor usage

  • adjust quotas when needed




Structure → Environment → Spaces → Entitlements → Marketplace → Applications

Comments

Post a Comment