Release Notes for SAP HANA Cloud Platform

A new dashboard serves as an entry page of the cockpit. The dashboard provides an overview of and access to the SAP HANA XS and Java applications available in the account and shows other key information about the account.

For more information, seeCreating SAP HANA Packages.

For more information, seeConfiguring OAuth Authorizations.

• You are now properly requested to enter your password for the console client commands (before there was an error with HTTP code: 401)
• Тhe --application parameter in console client commands for managing connectivity destinations for subscribed applications now works with the format --application <provider_account>:<provider_application>. For more information, seeConfiguring Destinations from the Console Client.

• When only modifying jco.client.cloud_connector_version, a JCoDestination was not recognized to be changed so that the old cached instance was still used.
• Depending on the defined DDIC (Data Dictionary) types and structures and on the defined RFM (Remote Function Module) interfaces at SAP AS ABAP system side, a java.lang.StackOverflowError could have been thrown when a JCoRepository instance was storing the queried RFC meta data into its internal MetaDataStorage instance.
• A java.lang.NullPointerException was thrown when saving a JCoRepository instance, which contained a remote function module template with an empty import parameter list.
• The meta data information that specifies whether a parameter is optional or not was lost after loading a JCoRepository instance from a Java I/O character stream. Calling method JCoListMetaData.isOptional(<name|index>) on any parameter meta data that was loaded by a JCoRepository always returned false in this case.
• A java.lang.NullPointerException was always thrown when trying to log on to a non-Unicode ABAP system using one of the new logon languages that are available in Unicode SAP systems only. Now an appropriate JCoException with error group RFC_ERROR_LOGON_FAILURE will be thrown in this case.

• rolling-update - to run an update of an application without downtime in one run. Prerequisite is that the new version is compatible with the old one.
• enable - to switch a previously disabled application process(es) to started state in the load balancer.

For more information, see rolling-updateandenable.

The status icons are improved, in particular the OK status icon which was sometimes confused with an action.

There is now a new cloud environment variable HC_PROCESS_ID that contains the process id of the current application process.

For more information, seeUsing Cloud Environment Variables.

For more information, see the release notes.

For more information, see Getting Feedback for Applications.

• Support of multiple accounts within a single installation. Account administration allows you to add/delete connections to several accounts. For more information, see Managing Accounts.
• Redesigned UI experience, similar to the cockpit
• Support for Principal Propagation has been added. By configuring trusted SAML IdPs, the identity, which is  logged on to the cloud, will also be logged on in the on-premise systems, if the prerequisites are fulfilled. For more information, see Setting Up Trust.
• Audit logs can be checked for integrity so that it can be verified that no one has modified them. For more information, seeAudit Logging in the Cloud Connector.
• Payload traces for the communication traffic can be activated for problem analysis. For more information, seeTroubleshooting.

For more information, seeChecking the Application Status.

• You can navigate to the metrics details from the Status Summary in the Process Dashboard
• Current metrics are now shown in compact view in the Monitoring tab
• You can now select a custom period when viewing history of metrics for whole applications.

For more information, see Viewing Monitoring Metrics.

Using Internet Services in Cloud Applications

Using On-Premise Back-End Services in Cloud Applications

• A user could not start a cloud server in debug mode if the Server Adapter was attached to an existing running application.
• The profiling session name was incorrectly generated.
• Servers used to hang if running with an older SAP JVM.
• Applications created with migrated runtime and running on a cloud server, were deployed with wrong runtime version
• Migration failed imperceptibly if SDK had been deleted.
• Accessibility fixes in the Connectivity and Users editors in the Eclipse IDE.