Merge pull request #23419 from danielva/master

jmmargo · web-flow · commit 55f4b2be8b3d · 2024-01-31T08:01:43.000-07:00
Updates to HC clients, alerts, and getting started tutorials
diff --git a/tutorials/hana-clients-x509/hana-clients-x509.md b/tutorials/hana-clients-x509/hana-clients-x509.md
@@ -44,7 +44,7 @@ The SAP HANA Client can use different [cryptographic service providers](https://
 
 As a first step, we will ensure that basic connectivity is working with a user name and password.  The steps below check the version of the SAP HANA Client, create a test user, and attempt to connect using basic authentication with mscrypto or OpenSSL.  The SQL commands can be run by an admin user such as DBADMIN in the SQL console or hdbsql.
 
-1. Check the version of SAP HANA Client on your machine.  
+1. Check the version of SAP HANA Client on your machine and ensure it is a recent release.  
 
     ```Shell
     hdbsql -v 
diff --git a/tutorials/hana-clients-x509/hdbsql-version.png b/tutorials/hana-clients-x509/hdbsql-version.png
diff --git a/tutorials/hana-cloud-alerts-custom/hana-cloud-alerts-custom.md b/tutorials/hana-cloud-alerts-custom/hana-cloud-alerts-custom.md
@@ -156,8 +156,10 @@ This step will create a catalog, an input, and a command in the SAP Automation P
 
     ![edit output](edit-output.png)
 
-    Set the value to be `$(.QueryDB.output.output[0])`.
-
+    | Label | Value |
+    | -------- | ----- |
+    | checkResult | `$(.QueryDB.output.output[0])` |
+    
     This will take the result printed in the `QueryDB` executor and set it to the output of the command.
 
     > For additional details on the use of the `$(...)` used above, see [Dynamic Expression](https://help.sap.com/viewer/de3900c419f5492a8802274c17e07049/Cloud/en-US/22621f87e7574f9e9fd1b1b95fe7a61d.html).
@@ -258,9 +260,9 @@ This step will add an additional executor to the command that can connect to a S
     print(rows)
     ```
 
-    Under STDIN, specify `$(.scriptInput.password)` so that the output of the previous step can be accessed in the Python code.
+    Under STDIN, specify `$(.SQLStatement.output.result)` so that the output of the previous step can be accessed in the Python code.
 
-    ![STDIN](stdin.png)
+    ![STDIN](stdin1.png)
 
 
 7. Trigger the execution.  Additional inputs are not needed.
diff --git a/tutorials/hana-cloud-alerts-custom/stdin1.png b/tutorials/hana-cloud-alerts-custom/stdin1.png
diff --git a/tutorials/hana-cloud-alerts-rest-api/hana-cloud-alerts-rest-api.md b/tutorials/hana-cloud-alerts-rest-api/hana-cloud-alerts-rest-api.md
@@ -80,7 +80,7 @@ There are multiple tools that enable making calls to a REST API such as Postman,
 
 
 ### Request a bearer token to enable access to the REST APIs
-The following steps are required to create a bearer token that will be used in subsequent steps that make REST API calls to access alerts and metrics.  The bearer token is generated by a login request and can be understood as "give access to the bearer of this token".  Additional details can be found at [User Account and Authorization Service](https://docs.cloudfoundry.org/api/uaa/version/75.7.0/index.html#token) for Cloud Foundry.  The instructions below enable a specfic SAP HANA Cloud instance to be queried.  It is also possible to query alerts and metrics for all instances in a subaccount or Cloud Foundry space using the admin-api-access service plan.  This is demonstrated in Step 5.
+The following steps are required to create a bearer token that will be used in subsequent steps that make REST API calls to access alerts for a single SAP HANA Cloud, SAP HANA database or data lake Relational Engine instance.  It can also be used to access metrics for a SAP HANA Cloud, SAP HANA Database  instance.  The bearer token is generated by a login request and can be understood as "give access to the bearer of this token".  Additional details can be found at [User Account and Authorization Service](https://docs.cloudfoundry.org/api/uaa/version/75.7.0/index.html#token) for Cloud Foundry.  It is also possible to query alerts and metrics for all instances in a subaccount using the admin-api-access service plan.  This is demonstrated in Step 5 and also enables the ability to access metrics for data lake Relational Engine instances.
 
 1. In the SAP BTP Cockpit, navigate to the **Instances** section, select your SAP HANA Cloud, SAP HANA database instance.
 
@@ -287,7 +287,7 @@ The following instructions will show a few examples of how to view metrics throu
     For additional details on the metrics REST API, see [APIs for Metrics](https://help.sap.com/docs/hana-cloud-database/sap-hana-cloud-sap-hana-database-administration-guide/apis-for-metrics), [Overview of Available Metrics](https://help.sap.com/docs/hana-cloud-database/sap-hana-cloud-sap-hana-database-administration-guide/overview-of-available-metrics), and [Metrics Service on the Business Accelerator Hub](https://api.sap.com/api/MetricsAPI/overview).
 
 ### Access alerts and metrics for multiple instances
-If you wish to access alerts and metrics for multiple instances with one API call, the service plan admin-api-access can be used as shown below.
+If you wish to access alerts and metrics for multiple instances with one API call, the service plan admin-api-access can be used as shown below.  In addition, metrics for data lake Relational instances can be accessed using this service plan.
 
 1. Ensure the service plan **admin-api-access** appears under the service **SAP HANA Cloud**.  If required, select **Add Service Plans** and enable the entitlement.
 
diff --git a/tutorials/hana-cloud-mission-trial-1/hana-cloud-mission-trial-1.md b/tutorials/hana-cloud-mission-trial-1/hana-cloud-mission-trial-1.md
@@ -39,7 +39,7 @@ This tutorial is part of a mission, in which you will learn in a hands-on, end-t
 
 -	If you do not restart your instance within **30 days**, it will be **deleted**. Your trial account, however, will continue to exist and you can easily provision an instance again, if you wish to do so.
 
--	The configuration of your trial instance of SAP HANA Cloud, SAP HANA database is **16 GB of memory, 1 vCPUs, and 80 GB of storage**.
+-	The configuration of your trial instance of SAP HANA Cloud, SAP HANA database is **16 GB of memory, 1 vCPU, and 80 GB of storage**.
 
 -   Features such as JSON document store, Script Server, PAL/APL etc. require larger HANA Cloud configurations (3 vCPUs, 45G memory) and are therefore *not supported* in a trial account.
 
