Release Notes for SAP HANA Cloud Platform

Note that it cannot be used for productive applications and does not support SQL Trace, connectivity service integration, OAuth, and keystore service.

For more information, see Java Web Tomcat 7 .

The hot-update command is now generally available. It enables you to redeploy and update the binaries of an application faster than when using deploy and restart. The update happens directly on the already running application process.

You can now debug server-side JavaScript with SAP HANA XS Web-based Development Workbench. For more information, see Debugging Server-Side JavaScript with SAP HANA Web-based Development Workbench.

Two new blog posts give more information:

• Building Java Web Applications with Mavenexplains how to compile against the SAP HANA Cloud Platform API for Java.
• Working with the "Neo" Maven Pluginintroduces the official Maven plugin for SAP HANA Cloud Platform.

You can view the overall monitoring status of SAP HANA instances on the Account Dashboard and in the HANA instances list. For more information, seeViewing Monitoring Metrics of a Productive SAP HANA Instance.

The Destinations editor is now available in the cockpit on subscription level and allows you to maintain destination configurations for subscribed applications. For more information, seeAccessing the Destinations Editor.

Existing account members have both roles assigned to them (some exceptions might exist). Newly added account members receive only the Developer role by default from now on. For more information, seeAssigning Members to Accounts.

You can view history of metrics of SAP HANA instances in the cockpit. For more information, seeViewing Monitoring Metrics of a Productive SAP HANA Instance.

The command is enhanced as follows:

• It supports a background mode, which allows you to open a DB tunnel as part of automated scripts. For more information, seeUsing a Database Tunnel in Scripts.
• It can generate json output instead of plain text. For more information on json output, seeMachine-Readable Command Output.

This feature is in beta and is available on the trial landscape only. For more information, seeHTML5 Applications Development.

You can create custom roles via the cockpit from the new Application Subscription view. These custom roles are created per application subscription.

For more information, seeManaging Roles.

Features:

• A new Application Whitelist enables you to limit the applications that are allowed to use the tunnel for accessing on-premise applications. For more information, see Setting Up Trust.
• Principal propagation support has been extended to the RFC protocol. Principal propagation X.509 certificate subject can be configured in the Cloud connector. For more information, seeConfiguring Principal Propagation to an ABAP system for RFC.
• You can import and export access control configurations.

Bugfixes:

• Refreshing of audit logs now works properly and does no longer jump always to the first page.
• If connectivity to the cloud is lost, when an administrator opens the Cloud connector, the re-connection mechanism works and is no longer cancelled by the UI.
• A file descriptor leak has been fixed in the re-connection procedure. This leak could prevent the mechanism from working at all if certain limits were reached and thus cause downtime for the tunnel.

You can use on-premise connectivity via SAP HANA Cloud connector through a standard HTTP proxy from Java Web applications. The proxy is provisioned on your application compute unit and is accessible at localhost:20003 via HTTP. For more information, seeHTTP Proxy for On-Premise Connectivity.

You can restart SAP HANA services on productive SAP HANA instances from the console client. For more information, seerestart-hana.

You can evaluate and work with SAP HANA Predictive Analytic Library (PAL) functions on SAP HANA Cloud Platform Trial landscape. For more information, seeUsing Predictive Analysis Library.

• Unclear error message appeared if password for connecting to a SAP HANA system was wrong
• The "Add Cloud System..." action was missing from the menu when the selection was on a system that is logged off.

An API for storing, updating and deleting passwords is now available to applications. For more information, seeStoring Passwords.

SSL 3.0 is no longer supported as a communication protocol.

In case you have connection problems, make sure your HTTP client (e.g. browser) supports TLS 1.0, TLS 1.1, or TLS 1.2.

Deployment with SAP HANA Cloud Platform Tools with version older than 1.17.0 or SDK with version older than 1.16.0 is no longer supported.

• "Landscape host" in the preference page is renamed to "Server's host name" to match the New Server wizard
• Trailing white spaces are now ignored in the Cloud Server wizard
• Starting a local server in an external directory which exists in the workspace is now possible
• Stopping a local server from the Debug view is now possible
• The Users editor does not throw an exception when you open it right after a server is created.

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, see Creating SAP HANA Packages.

For more information, see Configuring 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, see Configuring 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.