• Add all Role Collections starting with KymaRuntimeNamespace... to your user.
Follow the steps below to complete the exercise.
Steps and Instructions Additional Information
1 On your BTP free trial,select the trial tile. New BTP trial accounts are setup with Kyma Runtime already added. You will see an Enable Kyma button if it is. If you do not see that button, you will need to select Entitlements on the left, choose Configure Entitlements to set it up. This exercise assumes you already have it.
3 Accept the default Cluster Name, enter a
Description if you wish to, and select the Create button.
The enablement process begins. As the notice on the previous dialog stated, the process can take between 30 and 60 minutes to complete. Please be patient.
The process will continue, even if you close the BTP window.
You can use the BTP for other tasks while the setup process runs.
4 Select Role Collections. The list of current Role Collections is displayed on the right.
5 Scroll down to, and select the
KymaRuntimNamespaceAdmin item.
6 Select the Edit button in the upper right. The Role Collection is now editable.
7 In the Users area, enter the email address you used to create your BTP trial into the ID field and then select the appropriate user from the list.
9 Select the Save button in the upper right. Your user is now assigned the Role Collection. You can use the Trust Configuration tool to confirm the assignment.
10 Select trial from the breadcrumb trail.
12 Scroll down to the Kyma Environment area and select the Link to dashboard link.
Your Kyma console opens. This is your area for managing and deploying applications or services on the Kyma runtime. With the dashboard you can not only deploy or delete deployments, but also manage them for scale, expose them over self-defined API Rules and more.
What is Kyma?
Tell me what Kyma is in simple words
Kyma /kee-ma/ is a platform for extending applications with serverless functions and microservices. It provides a selection of cloud-native projects glued together to simplify the creation and management of extensions.
These cloud native projects are:
• Asset management and storing tool (Rafter, MinIO) • Backup of Kyma clusters (Kyma Backup)
The entire solution is containerized and runs on a Kubernetes cluster. Kubernetes, also known as K8s, is an open-source system for automating deployment, scaling, and management of containerized applications.
What are my advantages to use this platform?
The extensions and customizations you create are decoupled from the core applications, which means that: • Deployments are quick.
• Scaling is independent from the core applications.
• The changes you make can be easily reverted without causing downtime of the production system. • Highly cost-efficient.
Read more :
https://kyma-project.io/docs https://open.sap.com/courses/kyma1/items/7G43vPkYRT0xwLOj3AlCEk https://kubernetes.io/ https://www.docker.com/Explain the main components of KYMA
Kyma is built of numerous components but the following three are the most important ones:
• Registers external Events and APIs in the Service Catalog and simplifies the API usage
• Provides asynchronous communication with services and Functions deployed in Kyma through Events • Manages secure access to external systems
• Provides monitoring and tracing capabilities to facilitate operational aspects
In our scenario, the self-deployed SAP Commerce Cloud mock app is registered via the Application Connector. Usually, the SAP application to be connected is outside the Kyma cluster. In our case, however, it is in the same Kyma cluster and also in the same namespace.
Serverless:
• Ensures quick deployments following a Function approach • Enables scaling independent of the core applications
• Gives a possibility to revert changes without causing production system downtime • Supports the complete asynchronous programming model
• Offers loose coupling of Event providers and consumers • Enables flexible application scalability and availability
Service Catalog:
• Connects services from external sources
• Unifies the consumption of internal and external services thanks to compliance with the Open Service Broker standard
• Provides a standardized approach to managing the API consumption and access
• Eases the development effort by providing a catalog of API and Event documentation to support automatic client code generation
In our scenario we use a Redis store to store the data from the event. This data is then read out again by the second serverless function, get-order .
https://community.sap.com/search/?ct=blog&q=Kyma
© 2021 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see
http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.
National product specifications may vary.
These materials may have been machine translated and may contain grammatical errors or inaccuracies. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without
representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
