Release Notes for SAP HANA Cloud Platform

SAP JVM 8 is generally available for productive use as a deployment option for the Java Web Tomcat 7 runtime. For more information, seeChoosing JRE Version.

Faster log viewer for Java applications. The speed of the viewer has increased 9 times for 15 MB files. It is even higher for larger files and repeat executions.

SAP HANA revision 102.05 is supported. For more information seeSAP Note 2021789 - SAP HANA Revision and Maintenance Strategy.

SAP HANA Interactive Education (SHINE) can be installed as an SAP HANA component via the cockpit. This application is for demo purposes only and is used as a self-service. For more information, seeSAP HANA Interactive Education (SHINE) and SAP Note 1934114.

SAPUI5 distribution 1.28.31 is supported. For more information, seeWhat's New in SAPUI5 or Change Log.

SAP ASE 16 SP2 is supported. For more information, seeWhat’s new in SAP Adaptive Server Enterprise 16.0 SP02.

Restarting a whole SAP HANA database system is now possible using the SAP HANA Cloud Platform cockpit. Previously, it was possible only by using the console client command restart-hana.

For more information, see Managing Databases.

SAP HANA Cloud connector 2.7.2 is released.

• Performance improvement for high-latency communication with small data amounts when using RFC via JCo on the SAP HANA Cloud Platform side.
• Support for Java 8.
• Support for Windows 10.

Fixes in 2.7.2

• Error message for logon failure for an RFC system was swallowed when connecting via message server.
• Pooling of HTTP connections works with Principal Propagation.
• Eliminated ConcurrentModificationException occurring when closing a connection to a backend. The exception could lead to delayed release of sockets on operating system level.
• UI certificate chain import works when the CA response provides the chain in reverse order.
• Improved robustness when loading corrupt configurations.
• In high availability setups, when the failover instance (shadow) is down, it is still possible to add an account or import host mappings. 
• Redirects to servers not known to the Cloud Connector do not lead to Access Denied responses when the SAP HANA Cloud Platform application wants to take care of the redirect itself.

New runtime for Java releases with important security improvements is available.

We recommend that you update your runtime for Java by following the procedure in Updating Applications with Zero Downtime.

There is a new section FAQ with a collection of frequently asked questions and provided solutions. For more details, see FAQ.

The Push, OData and Processing APIs of MMS are also used with OAuth. The OData interface supports batch processing as defined in the OData V2 specification. For more information, refer to sections Push Service API Authentication, Message Consumption and Message Processing.

A new --updates parameter allows the version command to check whether the SDK version is still supported and to suggest updates and hot fixes. For more information, see Version.

The selection of tables in the app data UI in the MMS cockpit has been simplified.

The Members list shows the names of members in addition to their user IDs. The name of a member becomes available after the first time the member visits the account.

Administrators can send emails to account members.

JCo runtime for SAP HANA Cloud Platform:

• Fixed connection pool recovery problems when property jco.destination.max_get_client_time not set to 0.
• Improved tracing for metadata and data content.
• Added clone() method to the JCoFunction interface.

The API offers two new methods:

• adjustPointsForPlayer for adjusting player points as TenantOperator,
• withdrawPointsFromPlayer "rule only” for withdrawing points.

The new GamificationReviewer role provides read-access to game mechanics.

Multiple SAP HANA databases can be hosted on a single SAP HANA system when the support for multitenant database container (MDC) is enabled for the SAP HANA databases (beta). Creating a tenant database is available on the trial landscape too.

A tenant database runs for 12 hours and shuts down at the end of the period to free resources. A tenant database that is not used for 30 days is automatically deleted.

A blog post describes the procedure for creating and testing a tenant database by using the SAP HANA Interactive Education example on a trial landscape. For more information, see SAP HANA Multitenant Database Containers (MDC) Scenarios Now on Trial Landscape.

In addition, the OData entity properties are typed according to the respective database table column. For RDMS, a device supports up to 32 custom attributes. For example, you can use a custom attribute to store things like serial number, MAC or IP address of a device. For more information, see Device.

Fixes:

• When a shadow is upgraded from an older version, the system certificate stays correctly available. The system certificate used to get lost during the upgrade when connecting to the master instance, which was not yet upgraded. As a result, the system certificate could be restored only with a workaround.
• The restart mechanism works properly in all environments. On some Linux systems, the restart used to not work as expected.
• Changes needed to support the correct E2E destination check.