As an administrator, you must perform several steps to set up a fully operational Kyma environment to which you can connect the chosen SAP solutions.
-
To perform administrative and development tasks, you need a global account and one or several subaccounts for which you can provision the Kyma environment. For details, see Create the Kyma Environment Instance.
-
Additionally, the subaccount admin must assign the Kyma environment as an entitlement to the subaccount. For details, see Configure Entitlements and Quotas for Subaccounts.
-
Set up a Kubernetes cluster with the project "Kyma" to connect and extend SAP systems: Create the Kyma Environment Instance
-
Assign the roles to users to allow the administrators to manage Kyma and the developers to create Functions: Assign Roles in the Kyma Environment
Assign the roles before the users start using the Kyma Dashboard. Not granting the roles results in an error.
-
Use the Kyma environment to integrate external systems: Register an SAP Customer Experience System
Your options are as follows:
-
Integrate a CX system and the Kyma environment so that the Functions you develop can use the system's API and receive business events.
-
Integrate an SAP S/4 HANA Cloud system to use the services it provides to extend your applications.
After you've integrated externals systems, the developers can start working on their Functions.
-
-
Extend SAP S/4HANA Cloud by developing event-driven extensions and applications: Extending SAP S/4HANA Cloud in the Cloud Foundry and Kyma Environment
-
Group several solutions into one formation to meet the requirements of your business scenario: Including SAP Systems in a Formation
You have set up the Kyma environment and connected it as required.
Once the administrator sets up the environment, the developers can access the Kyma environment through the Kyma Dashboard. Upon logging, developers can start creating extensions for the SAP systems either from the Kyma Dashboard or from the terminal after downloading the kubeconfig file with the cluster configuration. For details, see Development in the Kyma Environment.