SAP HANA Cloud Platform now supports JSR 356 Java API for WebSocket. The support of WebSocket API is in beta state.

For more information, see Java EE 6 Web Profile.

The SAP HANA Cloud Platform SDK and API are now also available as Maven artifacts in the central Maven repository.

You can find them for all supported Java runtimes under the group ID "com.sap.cloud".

You can now reset loggers level for a specific application to its initial value.

For more information, see reset-log-levels.

SAP HANA Cloud connector 1.x is planned to go end-of-maintenance by the end of March 2014. We would like to ask you to migrate to SAP HANA Cloud connector 2.x by then.

For more information about deprecating 1.x and migrating to 2.x, see this blog.

SAP HANA Cloud Platform will remove Internet Explorer 8 from the supported browsers list as of February 2014 and will stop testing of user interfaces against IE8.

The reason for this is that IE8, which was released back in March 2009, supports very limited subset of HTML5 features. This results in functional restrictions in the cockpit UIs.

We recommend that all users of the UIs of the platform migrate to a more modern browser.

For more information about browser support, see Product Restrictions.

You can now use the following features in the Destinations editor in the cockpit:

• For HTTP and RFC destinations, there is an additional parameter CloudConnectorVersion that allows you to select values 1 or 2 from a dropdown box, according to the version of your Cloud connector. Default value is 2.
• Besides destination files with no extension, you are now allowed to import files with the following extensions: .props, .properties, .jks, and .txt.
• Fix is provided for destination configuration values and you can now use backslashes in destination configuration values, such as destination name and URL

Support of OAuth 2.0 is now generally available, which enables applications to easily integrate with a platform-provided OAuth 2.0 authorization server to protect their web APIs according to IETF RFC 6749.

• The cockpit now shows a busy indicator when loading for the first time so that first time users connected via a low bandwidth connection get visual feedback that it is loading.
• You can now resize the space which the navigation on the left-hand side uses on your screen.
• The welcome e-mail that new developer account owners receive now lists all trial services with their corresponding access URLs.

You can now use HANA catalog objects from development schema that is not defined in the HANA Repository when building HANA analytic views. Note that this feature is in beta version and is available on the trial landscape only.

You can now delete a HANA package and all its content from the cockpit. Note that this feature is in beta version and is available on the trial landscape only.

You can now profile your applications that run on SAP HANA Cloud Platform inside the Eclipse IDE.

For more information, see Profiling Applications on the Cloud.

A confusing message issued by the subscribe command when a wrong application name was passed as an argument has been fixed.

The console client now provides helpful error messages for the following cases, respectively:

• When you enter a wrong command name - "Command <name> not found"
• When you enter "neo" only - "No arguments specified. For help, type: neo help"
• When you enter a command without specifying parameters - the tool prompts you to enter the missing parameters

A problem with insufficient info in case an application is bound to the default data source has been fixed.

The persistence samples for default DBMS have been fixed.

Error messages for monitoring and logging commands in the console client for SDK 2.0 have been improved to match the ones in SDK 1.0.

It is not possible anymore to zoom to infinity in the charting component of the monitoring metrics history.

The displayed timeline in the metrics history chart now corresponds to the selected period even if there is no data for the full period.

A problem with the display-application-properties command showing empty values for vm-arguments property has been fixed.

A problem resulting in Internal Server Error when you press Enter without specifying any values in the User or Groups or Roles tabs has been fixed.

Java Applications

When an application is stopped, the shutdown relevant methods of the Servlet API are called before the application process is stopped. These are servlet destroy() methods or servlet context listener events.

You can now view a history of the monitoring metrics for your application processes in addition to the current metrics status in the cockpit. You can do that from the Monitoring tab of application processes. For more information, see Monitoring Applications.

You can now use the SAP JVM Tools to profile your applications deployed on the cloud. For more information, see Profiling Applications in the Cloud.

Eclipse Tools

You can profile your application that runs on SAP HANA Cloud Platform local runtime inside the Eclipse IDE.

For more information, see Profiling Applications Locally.

Feedback Service

The Аnalysis page now offers analysis of the data collected for the rating questions. The analytics report shows average rating score, ratings distribution and history of the ratings data. For more information, see Feedback Analysis.

You can now assign a predefined trust store to HTTP destinations created for SAP HANA XS applications. For more information, see Assigning Trust Stores to HTTP Destinations.

Enhancement

The database tunnel now allows you to connect to your SAP HANA and SAP MaxDB instances in the cloud. It is available as a beta version on the trial landscape only. For more information, seeDatabase Tunnel.

The tunnel replaces the existing remote database access tool and provides greater flexibility and ease of use.  The remote access servlet remains functional but has been removed from the 2.x SDK.

New version 1.16.6 of SAPUI5 runtime and documentation has been released.

SAP HANA Cloud Platform feedback service (currently in beta) provides you with the ability to collect end user feedback for your applications. The feedback service leverages the SAP HANA text analysis capabilities to deliver detailed text analysis of user feedback sentiment (positive, negative, or neutral). The feedback service consists of a client API exposed through the HTTPS REST protocol and of administration and analysis user interface.

For more information, see Feedback Service.

With SAP HANA Cloud Platform you can develop and run multitenant applications, that is, applications running on a shared compute unit that can be used by multiple tenants (consumers). Each tenant’s data is isolated from the data of other tenants, and each tenant accesses the application through a dedicated URL.

For more information, see Multitenant-Aware Applications.

To test how multitenancy works, see Tutorials: Multitenant Applications.

Document Service

Type mutability as defined in CMIS 1.1 is now supported and you can create and remove new object types.

For more information, see Object Type Mutability.

SAPUI5

New version 1.14.6 of SAPUI5 runtime and documentation has been released.

When establishing a connection to SAP HANA Cloud Platform using the Cloud connector 2.1.1, you can now select the landscape host from a dropdown box instead of typing it.

The following issues have been fixed in SAP HANA Cloud connector 2.1.1:

• NullPointerException that could occur when reading the SNC library configuration
• When switching the Cloud connector to a different account, the previous tunnel connection is now closed.

As a customer or partner, you can now have multiple accounts and create them yourself from the cockpit or the console client. You can also allocate compute unit quota to your accounts. For more information, see Account Management.

Multiple accounts allow you to maintain different environments for different purposes, such as development, testing, and productive use. For more information, see Using Multiple Accounts for Staged Application Development.

You can now debug your Java applications that run on SAP HANA Cloud Platform using the debugger inside the Eclipse IDE. The SAP JVM debugger is integrated within SAP HANA Cloud Server Adapter. The debugging experiences for the local and the cloud scenarios are analogical. For more information, see Debugging Applications in SAP HANA Cloud.

Connectivity Service

The console client commands upload, download and delete used for managing connectivity destinations for subscribed applications have been changed. They now conform to the syntax used for the other console client commands. The --application parameter is extended to the format:  --application <provider_account>:<provider_application>. The parameters --provider-account and --provider-application are deprecated but will continue to work. For more information, see Configuring Destinations from the Console Client.

• The import of destinations is now supported in Internet Explorer 9.
• While editing destinations or creating new ones, the Edit buttons of the other destinations on the screen are disabled.

New version 1.14.5 of SAPUI5 runtime and documentation has been released.

Connectivity service 2.x is now released for productive use. For more information, see Using Connectivity Service 2.x.

The API of SAP HANA Cloud connectivity service 2.x is fully backward compatible to version 1.x.

This release includes a new version 2.1.0 of SAP HANA Cloud connector, which provides the following additional features:

• RFC destinations can be configured for version 2.x. For more information, see Using Connectivity Service 2.x.
• Microsoft Windows 64-bit MSI installer, Linux 64-bit ZIP installer and MacOS X 64-bit ZIP installer for productive and development scenarios. For more information, see Installing Cloud Connector 2.x.

If you start freshly with the connectivity service, we strongly recommend that you use the latest version. Version 1.x will be deprecated in the future.

Migration from version 1.x to 2.x is possible without application downtime, in a fully backward compatible way. For more information about how to migrate, see Upgrading the Cloud Connector from 1.x to 2.x.

You can now start additional processes for an application right from the cockpit.

Cockpit, Persistence Service

You can now see the size of a schema from the cockpit.

You can use the --connections parameter in the deploy command  to specify the number of connections to be used during deployment. Use the parameter to speed up the deployment of application archives bigger than 5 MB in slow networks.

For more information, see deploy.

The SAP JVM Debugger has been released for productive use. For more information, see Debugging Applications in the Cloud.

It is now possible to build and run SAP HANA native XS applications on SAP HANA Cloud platform. For more information, see Creating an SAP HANA XS Application.

Note that this is a Beta functionality available only on TRIAL landscape (hanatrial.ondemand.com).

You can now give feedback about the cockpit using the Feedback link in the top menu. Your comments, ideas and suggestions reach directly our development teams.

Persistence Service, HANA

The persistence service automatically uses an SPS6 version (i.e. revision 61) of the SAP HANA JDBC driver when accessing SAP HANA databases with version SPS6 or later. SAP HANA databases with version SPS5 or earlier remain with the SAP HANA JDBC driver revision 49.

You need to carefully test on the new database applications that use EclipseLink and plan to migrate to SAP HANA database version SPS6. Individual applications observed issues with EclipseLink 2.3 and 2.4 in combination with a SAP HANA JDBC driver revision >= 50, which could be solved if you switch to EclipseLink 2.5 or later. Note that you have to bring EclipseLink 2.5 as part of your application as this version is not yet included into the SAP HANA Cloud platform.

You can now change the default database of an account.

For more information, see Changing the Default Database.

Apache Chemistry OpenCMIS has been updated to 0.10.0.

A read-only mode to the proxy bridge allows anonymous exposure of content and at the same time prevents anonymous users from modifying or adding content.

For more information, see Building a Proxy Bridge.

A new --uri-encoding parameter is available for the deploy command. If set, the specified encoding will be used for parsing the application URI.

For more information, see deploy.

• The Welcome page has been redesigned to ensure better navigation to important topics.
• In the Tutorials page, you can find a link to the Cross-Technology End-to-End Scenario tutorials, which are available in the Developer Center.

Client applications can now consume OAuth-protected Web APIs in your SAP HANA Cloud applications. To protect your applications with OAuth, you use a customizable OAuth 2.0 Authorization Server, new interfaces in the cockpit and the SDK.

For more information, see Protecting Applications with OAuth 2.0.

Debugging (Beta)

You can now use the SAP JVM debugger (Beta) to inspect the runtime behavior and state of your applications deployed on the cloud.

For more information, see Debugging Applications in the Cloud.

A new --loggers parameter in the set-log-level command allows you to simultaneously change the log level of multiple loggers in the console client.

For more information, see Managing Application Logs Using the Console Client.

You can now configure a custom maintenance page that is displayed during planned downtime of an application. For more information, see Using an Application Maintenance Page.

It is now possible to update an application to a compatible version without downtime. For more information, see Updating Applications with Zero Downtime.

You can perform a soft shutdown of an application or application process by executing shutdown in two steps - first disable opening of new connections and then stop the application or application process. For more information, see Soft Shutdown.

A new Operator's Guide has been added in the official SAP HANA Cloud documentation. The guide describes how you can perform the most common operator tasks, such as configuring and updating applications. For more information, see Operator’s Guide.

You can restart a single application process by ID using the restart command in SAP HANA Cloud console client. For more information, see Start and Stop.

An application process can now be identified with a short process ID. By default, the status command is showing only the first 7 characters of the process ID and the full process ID can be listed by using the --show-full-process-id option.  For more information, see Status; Start and Stop.

When you go to SAP HANA Cloud home page (http://hana.ondemand.com), it opens the Cloud Cockpit as a welcome page and does not redirect to the Developer Center any more.

The HTTPS port on localhost is not allowed anymore for loopback connections by the application (calls to https://localhost:8041 are not allowed). For loopback connections, a dedicated HTTP port bound to localhost shall be used. For more information, see Exchanging Data via HTTP Protocol.
The change is necessary for improving platform security.

Dynamic data source lookup allows you to dynamically bind new schemas to an application while it is running. Applications can use an arbitrary number of schemas, since the data sources are not predefined in the web.xml or persistence.xml file. For more information, see Using Dynamic Data Source Lookup.

Persistence Service

The JDBC driver for SAP HANA Database has been updated to version 1.00.49.373159.

The status of an application is now shown also with an icon, which makes it easier to view the current status of the application.

The application and process dashboard now shows your requested and respectively actual runtime versions and alerts you if the version is no longer recommended or expired.

All Cockpit pages that can be reached from the navigation now have stable links and can be bookmarked and shared. The URLs are human-readable and can be also entered manually or be pre-computed, for example for notifications. Browser back and forward also works and makes the interaction more fluent.

Increment for the Cloud Connector with version 2.0.1 containing first fixes has been released.

For more information how to use the Connectivity Service 2.0, see Using Connectivity Service 2.0 Beta.

SAP Cloud Connector 1.3.1 has been released with the following enhancements:

• A system certificate can now be deleted again
• An HTTPS server addressed by an internal host can now use wildcard certificates
• The system certificate is now immediately exchanged in the tunnel runtime after updating it
• Bugfix for the following issue: larger RFC request data streams could be interrupted and caused an exception in the JCo based cloud application.

New version 1.12.7 of SAPUI5 has been released.

The persistence service now provides a set of console client commands for handling database schemas. The commands allow you to create, bind, unbind, and delete schemas, and ultimately share schemas between applications and run applications on more than one database at the same time.

For more information, see Database Schemas.

Deploy Service

Using the console client you can list all application processes which are started for an application, get the status of a single application process and stop a single application process.

For more information, see Start and Stop.

The remote access servlet no longer needs to be deployed directly with the application in order to access the application’s database schema. Instead, simply bind the remote access servlet to the application’s schema using the new database schema functionality (beta) and then unbind it when remote access is no longer required.

For more information, see Enabling Remote Database Access.

The SAP HANA Cloud connectivity service is released in version 2.0 as Beta and can now be used on trial landscape hanatrial.ondemand.com. The new version of the service is now based on standards like Web Sockets and consists of the SAP HANA Cloud connector 2.0 which can be downloaded from the SAP HANA Cloud tools page.

For more information about how to use the Connectivity Service 2.0, see Using Connectivity Service 2.0 Beta.

You can now filter by ID in the member management of the cockpit.

You can also see all database schemas created within an account. Each schema is listed with its name and the database type and version.

The HTTPS port on localhost will not be allowed anymore for loopback connections by the application (i.e. calls to https://localhost:8041 will not be allowed). For loopback connections, a dedicated HTTP port bound to localhost shall be used.

For more information, see Exchanging Data via HTTP Protocol.

The change will be enabled with the SAP HANA Cloud release planned for August 29th, 2013.

Optimized deploy operations via console client when deploying applications with big sizes. The total deployment time may be reduced with up to 50% and varies depending on the archive size and client network.

SAP Development Tools for Eclipse Software Site

https://tools.hana.ondemand.com provides a new software site for the Eclipse Kepler release train. All Cloud Tools are available for Kepler.

Loggers configuration is now persisted on both local runtime and SAP HANA Cloud level. Logger level settings are kept and restored on a server restart, so you do not need to set them over again when restart or redeploy your application.

For more information, see Managing Application Logs from the Eclipse IDE.

The Java 6 runtime of the HANA Cloud Platform was updated from 1.6.026 to 1.6.043. The new Java Runtime will be provisioned for the applications after a restart. The update includes multiple corrections for bugs and security issues.

For more information, see the official Java SE 6 release notes page. The Java updates are cumulative and 1.6.043 includes all patches since 1.6.026.

SAP App Designer 0.9.3 is now in beta/trial shipment. SAP App Designer is available for selected Beta customers with restricted functionality (SAP Fiori extensibility scenario). Free trial access will be announced once available.

Remote Database Access

The Remote Database Access Tool (beta) now provides

a SAP HANA studio integration feature that allows you to remotely access the SAP HANA database. To use this feature, you require a local installation of the SAP HANA studio, available for download from https://hanadeveditionsapicl.hana.ondemand.com/hanadevedition/, and a SAP HANA studio remote access plugin, which is contained in the SDK 2.x add-ons directory. For more information, see Connecting to the Remote SAP HANA Database.

The Destinations editor in the cockpit, applicable on application level, is extended with the following features:

• You can upload custom 'key store' and 'trust store' (*.jks) files for HTTPS in the cases of client authentication;
• You can export destination files;
• You can import destination files in a more convenient way.

For more information, see Configuring Destinations from the Cockpit.

Applications are now able to make loopback requests to localhost on HTTP port 9001.

You can now unlock unlimited strength cryptography in SAP JVM for your SAP HANA Cloud application.

For more information, see Using Strong Encryption in Applications.

Cockpit: Monitoring

Average Response Time (for the last minute) and Used Memory Heap are now available as new metrics in the process dashboard of SAP HANA Cloud cockpit.

RFC (JCo) destinations can be created, edited and uploaded using the Destinations editor in the cockpit.

For more information, see Configuring Destinations from the Cockpit.

RFC (JCo) destinations can be created, edited and uploaded using the Eclipse Tools.

For more information, see Configuring Destinations from the Eclipse IDE.

You can now test Gateway as a Service (GWaaS) with your developer account on hanatrial.ondemand.com.

GWaaS is a solution that allows you to consume data from an SAP Business Suite backend system in SAP HANA Cloud. It establishes a connection between SAP Business Suite data and target clients, platforms, and programming framework. Gateway as a Service exposes business data and business logic as OData services on SAP HANA Cloud, thereby enabling customers to run user-centric applications on SAP HANA Cloud.

Keystore Service

The Keystore service, now available in Beta state, provides a repository for cryptographic keys and certificates to the applications hosted on SAP HANA Cloud platform. By using the Keystore service, the applications could easily retrieve keystores and use them in various cryptographic operations such as signing and verifying of digital signatures, encrypting and decrypting messages, and performing SSL communication.

For more information, see Keys and Certificates.

RFC protocol is now supported:

• A dedicated JCo version is now part of the SAP HANA Cloud runtime for Java and the latest corresponding SDK (1.29.18).

        A tutorial in the SAP HANA Cloud documentation describes how to   build   an application that accesses an on-premise ABAP system via RFC.

• SAP Cloud Connector 1.3.0 has been released with the following enhancements:
  • Configuration of host mappings for the RFC protocol
  • Configuration of function modules as resources in case of RFC
  • SNC configuration for secure communication with ABAP backends when using RFC
  • Support for Host-Header: Host-Header now contains the virtual host as used in the cloud. Thus, an on-premise HTTP application can create URLs pointing to other resources on the same server correctly.

By using SAP HANA Cloud SDK for Java EE 6 Web Profile, customers and partners can now develop applications that utilize the Java EE 6 WebProfile APIsand deploy such applications on the production landscape hana.ondemand.com.

Persistence Service

SAP HANA Cloud SDK for Java EE 6 Web Profile supports applications that bring their own JPA provider and use it instead of the one provided by the platform. For example, an application can bring in its WEB-INF/lib folder a particular version of EclipseLink and use it. In this case, the application will work with its own JPA provider standalone hence it cannot rely on JPA container logic.

https://tools.hana.ondemand.comhas grown from an “SAP HANA Cloud Tools” software site to a general “SAP Development Tools for Eclipse” software site. It now provides Eclipse tools for additional development scenarios like ABAP Development Tools for SAP NetWeaver and SAP NetWeaver Gateway Productivity Accelerator.

The representation of the SDK, SAP JVM and Cloud Connector downloads on the Cloud toolstab page has been improved as follows:

• old SDK versions are hidden
• file names describe runtime type
• file size is shown.

Document Service

The default protocol has been switched from AtomPub to JSON for better performance and less bandwidth consumption. No application changes are required.

The cockpit has a new look, new simplified navigation and offers more content at https://account.hana.ondemand.com/cockpitand

https://account.hanatrial.ondemand.com/cockpit.

For more information, see SAP HANA Cloud Cockpit.

Cockpit: Monitoring

It is possible to view the current state of the metrics for your applications.

For more information see Applications -> Application Dashboard section.

It is now possible to configure and import HTTP and Mail Destinations on application level from the cockpit.
For more information see Configuring Destinations from the Cockpit.

• The com.sap.core.connectivity.api.http.HttpDestination class has been extended by a new getURI() method.

        For more information, see Destination API.

• The documentation of the connectivity service has been restructured and improved.

        For more information, see Consuming SAP HANA Cloud Connectivity Service

Stronger password policy has been enforced for the platform management tools like the cockpit.

If your password is not complex enough or has not been changed in the last 6 months, you will be asked to change it at the first login via a browser.

The self-registration process for SAP HANA Cloud developer accounts has been simplified. Developers can now register via https://account.hana.ondemand.com.

• You can now configure Mail destinations in the Eclipse Connectivity Editor.

        For more information, see Configuring Destinations from the Eclipse IDE.

• Changes in the Eclipse Connectivity Editor on a SAP HANA Cloud local runtime do not require restart of the local runtime anymore.

The SAP JVM  7, a JDK 7 compatible Java Virtual Machine, is now available for the Mac OS X platform as a separate download from the Tools page -> Additional Software section. It can be used for running a local server for SAP HANA Cloud.

For more information see, Java Virtual Machine and Installing the SAP JVM.

Sending and fetching e-mail is now available for productive usage in customer and partner accounts.

For more information, see Sending and Fetching E-Mail.

Connectivity Service: E-Mail

Support for e-mail protocols has been merged into the connectivity service.

For more information see SAP HANA Cloud Connectivity Service.

You can now also install the SAP HANA Cloud Tools for Java directly from the Eclipse Marketplace.

For more information, see this blog.

Information about getting started with SAP HANA Cloud has been added to the Eclipse Welcome screen. This information is visible after the installation of SAP HANA Cloud Tools for Java.

SAP NetWeaver Cloud is now part of SAP HANA Cloud. All sites, documentation and tools have been rebranded.

For more information, see http://scn.sap.com/docs/DOC-39315.

Remote Database Access

The Remote Database Access Tool, available as a beta version, is delivered as part of the beta SDK 2.x in the new add-ons directory. It allows you to remotely access your application’s database schema and tables on the SAP HANA Cloud platform, investigate and repair application data, and create, drop, and modify database objects. It is currently available for SAP MaxDB only.

For more information, see Remote Database Access.

New version 1.10 of UI Development Toolkit for HTML5 (SAPUI5) has been released.

For more information, see SAPUI5 detailed release notes.

Downloading and installing SAP HANA Cloud Tools for Java from the Tools Update Site  does not require a log-in anymore. The license click-through for downloading the SDK has been simplified.

The support for Indigo version of Eclipse has entered the end of maintenance. The Indigo update site is still operational but no updates will be made. We recommend that you use Juno Service Release 2.

A new feature for testing the identity federation and single sign-on scenarios end-to-end has been introduced. With the test local identity provider (IdP), you can now establish trust to an easy-to-use test IdP running on your local machine.

For more information, see Using a Local Test Identity Provider.

Identity Federation

You can now upload your identity provider metadata as an XML file in the SAP NetWeaver Cloud Cockpit.

For more information, see Using a Custom Identity Provider.

SAP NetWeaver Cloud Mail Service now supports fetching mail via IMAP and POP3 protocols from an internet accessible mail provider.

For more information, see Using the Mail Service.

SAP NetWeaver Cloud Connectivity Service now supports destinations on account level. The destinations on account level are visible for all applications of a given account and thus it is possible to centrally create and maintain shared destinations.

For more information, see Connectivity Destinations Overview.

An application no longer needs an authenticated user for accessing the Document Service. This allows for public or unauthenticated use cases as well.

For more information, seeDocument Service Concepts-> User Management section.

Mail Service

Sending mail is no longer restricted to certain mail providers. The SMTP standard ports 465 (SMTPS) and 587 (SMTP+STARTTLS) are open for outgoing connections.

For more information, see Using the Mail Service.

When viewing logs in Eclipse, you can switch between the log files of different servers directly from the Server Logs view.

For more information, see Managing Application Logs from the Eclipse IDE.

Mail Service

The underlying javax.mail API has been upgraded from version 1.4.1 to 1.4.5 for the Beta SDK 2.x

For more information, see Mail Service API.

You can now change the log level of multiple loggers simultaneously.

For more information, see Viewing Logs and Setting Log Levels from the Eclipse IDE.

SAP Cloud Connector

SAP Cloud Connector (SCC) 1.2.0 has been released with the following enhancements:

• An automatic check for landscape host and proxy (if existing) that shows whether a connection to the Cloud is possible. The result appears on the Home tab.
• A manual connectivity check for all exposed systems, which shows whether the backend is reachable from SCC.
• A process monitor that shows the status of all SCC processes and provides a restart option for the different process groups.

You can download SAP Cloud Connector via the SAP NetWeaver Cloud update site -> Additional Software tab.

Sample Application “Paul the Octopus”

“Paul the Octopus” is a sample Web application that provides a complete example of all platform services of SAP NetWeaver Cloud, synchronously working together. The application code samples are provided and explained in details in a community blog.

For more information, see:

Community blog: Get Ready for Your Paul Position

Documentation: Running Sample Applications.

The SAP HANA database is now available for use on the nwtrial.ondemand.com landscape. The default database type to be used (the SAP HANA database or SAP MaxDB) can be selected when you register for a developer account. For more information, see Signing Up for an Account.

The issue with deploying to the Cloud when your IDE is behind a proxy requiring basic authentication has been resolved.

For more information, see this thread.

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, seeID 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, seeConfiguring Service Channels.
• Kerberos tokens for principal propagation to servers that do not support authentication with X.509 certificate. For more information, seeConfiguring 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, seeUsing 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.

Breadcrumbs show the full object hierarchy in the pattern:

Data Center> Account> application> process

The interface com.sap.core.connectivity.api.configuration.ConnectivityConfiguration is extended with a new clearCache() method. It allows each application to clear its local cache to ensure that the next configuration will be taken from a central storage. The method also clears the configuration cache used by HTTP destinations. For more information, see Connectivity Javadoc.

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

SAP HANA revision 90 (SP9) is now available.

• In a production environment or planned Go-live in less than 6 weeks,we recommend that you stay on the current SAP HANA SPS until the next SAP HANA Datacenter Service Point is reached.
• In a non-production environment or planned initial system setup, you can update to the new SP9 via request to SAP HANA Cloud Platform operators.

Virtual roles are now available for HTML5 applications.

• AccountAdministrator– account members with Administrator role.
• AccountDeveloper– account members with Developer or Administrator role.
• Everyone– all authenticated users of the configured identity provider.

You can map virtual roles to HTML5 application permissions. AccountAdministrator and AccountDeveloper require SAP IDP to be configured as identity provider. In case a custom IDP is configured, you can manually create these roles in the corresponding account.

By default, every permission required to access a protected resource of an application is granted to members of the AccountDeveloper role. As long as no other role is assigned to the permission, only account members with the Developer or Administrator role have access to the protected resource. This is also true for the default permission NonActiveApplicationPermission, which is required to access a non-active version of an HTML5 application.

• The Subscribed Java Applications table now has columns State and Start Time, so you can see the run state and start time of your subscribed Java applications.
• Every row in the log viewer has a View button that opens the respective log line in text-only format.

The rolling-update command is now available for productive use. For more information, seerolling-update.

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

New version of SAP JVM Tools is released. For more information about the new major features, seeWhat is New in SAP JVM Tools 2.2.

• JCoDestination.ping() times out after <rfc.client_connect_timeout>  seconds. It also throws a JCoException with error group JCO_ERROR_TIMEOUT if the system does not respond in that time.
• When using a destination with pooling, you can configure the destination to check the validity of a connection before using the connection for a function call. This way you can avoid zombie connections that may lead to error-prone situations.
• Traffic traces are added, which allows analyzing transferred data amounts.

Connectivity Service

• JCoRecord.isInitialized(name|index) no longer returns wrong "false" for nested tables or structures.
• Performance improvement is done for client calls that do not use AbapClassException.

Platform Infrastructure

The Safari browser no longer blocks iFrame-embedded applications.