Release Notes for SAP HANA Cloud Platform

The Services section of the cockpit is redesigned to list all platform services and to provide direct links to service administration and documentation. For more information, seeAccessing Services.

You can now register an SAP Cloud Identity tenant as an identity provider for your SAP HANA Cloud Platform applications. If the SAP Cloud Identity tenant is registered for your current SAP HANA Cloud Platform user, the trust configuration between SAP HANA Cloud Platform and the SAP Cloud Identity tenant is created automatically. For more information, see ID Federation with a SAP Cloud Identity Tenant.

SAP HANA Cloud connector, version 2.5.0, is released. It now supports:

• Service channels, which offer access to cloud services in local networks. The currently supported type of channels is HANA Database. For more information, see Configuring Service Channels.
• Kerberos tokens for principal propagation to servers that do not support authentication with X.509 certificate. For more information, see Configuring Kerberos in the Cloud Connector.
• Configuration of local user store as a cloud user base. It requires corresponding settings in the cockpit.

• A restriction is removed: You can now configure a single Cloud connector to connect to several accounts with the same name in different landscapes. For example, connection to account fiori in hana.ondemand.com, us1.hana.ondemand.com, and  ap1.hana.ondemand.com.
• The reconnection behavior is improved in the case when a connection through the Cloud connector breaks without returning a response code.

Cockpit, Monitoring

The JMX console is now available for productive use. For more information, see Using the JMX Console.

You can change the cockpit UI theme to high-contrast black. The change is persisted as user preference and can be switched back to the default theme. For more information, seeCockpit → section Accessibility.

The following plugins can now be used with SAP Web IDE: 

• Visualization Extension (Vizpacker) - creates chart extension packages in SAP Lumira and other products.
• SAP HANA Cloud Portal - creates different types of OpenSocial widgets in SAP HANA Cloud Portal sites.

You can create new projects based on reference applications (such as SAP Fiori applications). For more information, seeSAP Web IDE 1.6

Тhe SDK for Java Web Tomcat 7 contains а new connectivity sample. Find it at: <Tomcat7_SDK_location>/samples/connectivity.

The documentation offers two new tutorials relevant to the sample:Consuming Internet Services (Java Web Tomcat 7)andConsuming Back-End Systems (Java Web Tomcat 7)

Тhe ConnectivityConfiguration API offers two additional methods: getConfiguration(account, name) and listConfigurations(account). For more information, seeInterface ConnectivityConfiguration.

Eclipse Tools

You can now easily recognize SAP HANA systems inside the Systems view in the Eclipse IDE. The name of each SAP HANA system has the following name pattern:  <account>-<schema name>(<DB user name>).

SAPUI5

SAPUI5 distribution 1.24.5 for Java and HTML5 applications (including runtime 1.24.4 & documentation) has been released.

You can now set a display name and a description for Java applications. For more information, seeDefining Application Details.

When in the Eclipse IDE you delete a server with an application running on it, a dialog appears allowing you to choose whether to only undeploy the application, or to completely delete it together with its configuration.

Using the restart-hana command, you can now restart an entire productive SAP HANA system, or  a specific SAP HANA service running on the specified SAP HANA system. Before, it was possible to restart a specific SAP HANA service only. For more information, seerestart-hana.

SAPUI5

SAPUI5 distribution 1.24.4 for Java and HTML5 applications (including runtime 1.24.3 & documentation) has been released.

You can now deploy and update Java applications via the cockpit. For more information, seeDeploying on the Cloud with the Cockpit.

The Java Web Tomcat 7 runtime is generally available and can be used on productive landscapes. For more information, seeJava Web Tomcat 7.

During deployment, if compute unit size is not explicitly specified, by default, the smallest compute unit size from the account quota is assigned to the application. For more information, seedeploy.

Java Applications, Console Client

You can now set the Tomcat connector attributes max-threads and connection-timeout during application deployment. Alternatively, you can execute the set-application-property command for each property without the need to redeploy the application. For more information, seedeployandset-application-property.

Theset-application-propertycommand, which allows you to change the deploy parameters without redeploying the whole application, is now generally available. For more information, see the blog postUpdating Application Properties Without Redeploy.

HTML5 Applications

The documentation now includes instructions for:

• Working with the Git service. For more information, seeWorking with Git.
• Consuming the document service from HTML5 applications. For more information, seeUsing the Document Service in HTML5 Applications.

SAP SQL Anywhere MobiLink as-a-Service (Beta) is available on SAP HANA Cloud Platform. MobiLink is a session-based synchronization technology for exchanging data among relational databases and other non-relational data sources. Customers can request MobiLink server in their accounts via an IT/IBC ticket in component BC-NEO-CON.

SAP River Rapid Development Environment

SAP River Rapid Development Environment (SAP River RDE) has been renamed to SAP Web IDE.

Eclipse Tools have the following enhancements:

• Autocomplete feature is now enabled for the Account name and User name fields inside Eclipse Tools. For more information, seeSetting Up SDK Location and Landscape Host.
• Local servers now automatically use proxy if the current Eclipse environment uses proxy server.
• SAP HANA Tools for HANA Server rev. 82 or earlier now supports also Eclipse Luna. For more information, seeInstalling SAP HANA Tools for Eclipse.

SAP HANA Cloud Connector

SAP HANA Cloud connector 2.4.3 has the following bugs fixed:

• Short-running function modules started in a separate thread in a JCo application are no more blocked by long-running function modules executed via RFC.
• The sporadic hanging during execution of RFC function modules is fixed. RFC function modules now finish properly in every case.
• SNC configuration is now properly replicated in high availability setups.

Java Web Tomcat 7 (Beta) runtime now supports theConnectivityConfiguration API and the AuthenticationHeaderProvider API. For more information, seeConnectivityConfiguration APIandAuthenticationHeaderProvider API.

SAPUI5

SAPUI5 distribution 1.22.7 (including runtime 1.22.7 and documentation) has been released.

The new SAP HANA Cloud connector version 2.4.2 contains important bugfixes.

We strongly recommendthat customers and users upgrade to this version. For more information on upgrading, seeUpgrading the Cloud Connector.

There is a beta version of REST API for lifecycle management operations with applications running on SAP HANA Cloud Platform. For more information, seehttps://api.hana.ondemand.com/lifecycle/v1/documentation.

You can now develop and deploy HTML5 applications on productive landscapes. HTML5 applications consist of static resources and can connect to existing on-premise or on-demand REST services. The static content of the HTML5 applications is stored and versioned in Git repositories. For more information, seeHTML5 Applications Development.

SAP River Rapid Development Environment (SAP River RDE) provides a fully extensible and customizable experience. It accelerates the development lifecycle with interactive code editors, integrated developer assistance, and end-to-end application development lifecycle support. SAP River RDE prerequisites and set-up instructions are included in theHTML5 Getting Starteddocumentation. For more information, seeSAP River RDE Developer Guide.

Console Client, Java Applications (Beta)

SAP Development Tools for Eclipse

(Download Site)

The persistence service now provides thebind-hana-dbmsandunbind-hana-dbmscommands for handling bindings between productive SAP HANA instances and Java applications. These complement the bind-schema and unbind-schema commands, which continue to be used for binding database schemas to Java applications.

The newlist-application-datasourcescommand replaces the list-application-schemas command, which has been deprecated.

Eclipse Tools

• If a landscape is in maintenance mode, the server is now correctly marked as in maintenance.
• If you cancel a cloud server login dialog, it does not appear again.
• The problemHana Cloud - Unable to share project - REPO.MAINTAIN_IMPORTED_PACKAGESwas fixed. Please update your Eclipse Tools to receive the fix. Then, delete your erroneous SAP HANA systems in your Eclipse IDE and add them again. All SAP HANA systems, which can be found in the Systems view, now comply with the name pattern: <system ID>(<DB user name>)

New version 2.4.1 of SAP HANA Cloud connector has been released with the following enhancements and bugfixes:

Enhancements:

• It shows trusted entities for principal propagation on a shadow instance.
• It shows countdown on a shadow instance if failover is supposed to happen.

Bugfixes:

• When using a non-SAML2 authentication for a cloud application, the Cloud connector now interprets the identity properly.
• When configuring the subject for Principal Propagation, the single elements are now sent to the target system in the correct order.
• The SNC partner name for an RFC host mapping is now replicated to the shadow instance in high availability setup.
• When you add an account to a master instance, and immediately after that a failover situation occurs, the added account now properly establishes a connection to the SAP HANA Cloud Platform landscape.
• When the Windows service is stopped, the Cloud connector now shuts down cleanly.

Eclipse Tools

You can now easily recognize SAP HANA Cloud Platform-managed HANA systems in the Systems view in the Eclipse IDE. The name of each SAP HANA system has the following name pattern: <account>-<instance name>(<DB user name>).

You can now configure options for the authentication methods defined for your Java applications. Depending on the options you select/deselect, the authentication methods will perform differently, requiring different credentials on behalf of users.

You can access the Authentication Configuration UI using the Cockpit. For more information, seeConfiguring Authentication for Your Application.

Eclipse tools have the following enhancements:

• In Eclipse IDE, you can use autocomplete when entering landscape host names. This will help you avoid typos from manual entries.
• Publishing on the cloud from the Eclipse IDE now uses the faster hot-update operation if the application is running. (Not applicable to applications using the Java Web Tomcat 7 runtime.) For more information, see step 11 inDeploying on the Cloud from Eclipse IDE.
• Eclipse IDE now shows an improved message in case of an authentication error when deploying on the cloud.

Connectivity Service

SAP HANA Cloud connector used to use port 1 by default when an HTTP destination of type OnPremise had a URL that did not contain a port. After the fix, port 80 for HTTP and port 443 for HTTPS will be used by default.

To ensure smooth migration, you need to create an additional host mapping in the Cloud connector with the new default virtual port (either 80 or 443). Do not delete the old mapping as long as your application runs with runtime lower than 1.58.6 or 2.39.6.

SAP HANA Cloud connector 2.4 is released with the following features and fixes:

Features:

• Support for high availability setup - an administrator can decide to install a so-called "shadow instance", which takes over the processing of requests in case the productive "master instance" shuts down due to a (hardware) failure. For more information, seeInitial ConfigurationandInstalling a Failover Instance for High Availability.
• Principal propagation support has been extended to arbitrary authentication types for cloud applications. To achieve this, the Cloud connector allows trusting additional entities, such as Java applications or SAP HANA instances for that purpose. For more information, seeSetting Up Trust.
• When configuring LDAP authentication for the Cloud connector administration UI, you are now allowed to configure a secure connection with LDAPS.

Bugfix:

Support for ICF (Internet Communication Framework) session mangling in access check. This ABAP system feature allows you to include an encoded session ID within the path of a service. For example, for service /sap/bc/ping, the request could be /sap(abcdef==)/bc/ping. In previous versions, such a request would be denied, even if /sap/bc/ping was exposed as a resource.

Eclipse Tools

The following issues are fixed:

• It is now possible to create a new local Java Web Tomcat 7 server directly from the New Server Runtime Environment wizard by selecting the Create a new local server checkbox.
• The correct URL address is now open in the browser when selecting Run on Server for a Dynamic Web 3.0 project and Java Web Tomcat 7 server.

SAP HANA

SAP HANA revision 80 (SP8) is now available upon request for productive SAP HANA instances assigned to accounts on the production landscape.

SAP HANA Cloud Platform is now available in a new data center in Australia. The landscape host is ap1.hana.ondemand.com.

For more information, seeLandscape Hosts.

Eclipse Tools have the following enhancements:

• Support of Java Web Tomcat 7 runtime and SDK. For more information, seeSetting Up the Runtime Environment.
• A new common server type "SAP HANA Cloud Platform" now works with all available runtime types supported by SAP HANA Cloud Platform.
• No need to type the full landscape host when publishing. Eclipse remembers the landscape hosts you have used previously, and when you start typing, it presents the list of all valid landscape hosts for you to select.
• Maintenance notifications are now shown in Eclipse. If the platform is in maintenance, and you request to deploy, start or stop an application, you will get an appropriate message.

Persistence Service, Roles and Permissions

The following changes have been applied in the handling of account member roles by the persistence service:

• SAP HANA database users: Account members, who by default are assigned the developer role only, are no longer able to create their own users in the SAP HANA database. Account administrators can create their own SAP HANA database users as before, but now also need to set up user accounts in the SAP HANA database for the members of their development team. For more information, see theupdatedGuidelines for Creating Database Users.
• Restarting SAP HANA services on productive HANA instances: This feature requires the administrator role. For information about
  using this command line function, seerestart-hana.

You can register availability checks for multiple SAP HANA XS applications running on a productive SAP HANA instance from the console client. For more information, seeConfiguring an Availability Check to Monitor Your SAP HANA XS Application.

You can configure a custom downtime application to be used in case of unplanned downtime. For more information, seeHandling Unplanned Downtime.

You can put Java applications in and out of maintenance mode from the cockpit.  Java applications in maintenance mode redirect requests to a chosen target application until you put them again into normal operation. For more information, seePutting Applications into Maintenance Mode.

SAP HANA Cloud Connector 1.x has reached end-of-life. It is no longer accessible ontools.hana.ondemand.comand its documentation has been removed as well. UseSAP HANA Cloud Connector 2.xas the major version that will be extended and maintained in the future.

SAP HANA Tools Revision 72 are now delivered via the download site(https://tools.hana.ondemand.com/#hanatools). For more information, see

Setting Up the Tools.

The log viewer now opens in a new window, shows the log volume over time and supports you in finding time ranges of high activity. For more information, seeLog Viewers.

You can now configure loggers also via the Recent Logging panel in the Java Application Dashboard. For more information, seeUsing Logs in the Cockpit.

• The Connectivity editor in Eclipse IDE has been extended to support PrincipalPropagation authentication type.
• You can now connect to productive and trial SAP HANA Instances via the Eclipse IDE. For more information, see Connecting to a Productive SAP HANA Instance via the Eclipse IDEandConnecting to a Trial SAP HANA Instance via the Eclipse IDE.
• You can now import SAP HANA sample applications in a selected repository package via your Eclipse IDE so you can quickly get up to speed with SAP HANA development. For more information, seeSamples.

• A new log viewer in the cockpit allows you to view trace and HTTP access logs directly in the browser and to sort and filter the log entries.
• You can still download log files – for each file you can choose whether to open in the viewer or download to your machine.
• Log files are also grouped by type.

For more information, see Using Logs in the Cockpit.

• The console client commands for the local server inside the SDK (install-local, start-local, andstop-local) now have port parameters that help avoid port collisions, thus enabling you to set up parallel builds and test procedures. These parameters are now visible by default in the console help. 
• The install-local command now also supports setting non-proxy hosts for a local server (installed from the SDK for development purposes).
• A new command deploy-local that allows you to deploy WAR files on a local server instance is now available.