Quantcast
Channel: SCN : All Content - SAP HANA Cloud Platform Developer Center
Viewing all 3285 articles
Browse latest View live

Cloud Connector Access Back-end System via VPN?

$
0
0

Hi all,

I am new to SAP HANA and investigating a solution for our html5 applications.


My question is it is possible for us to deploy SAP HANA Cloud Connector in Internet while it accessing our back-end systems via VPN? 


If yes, any tips or note, especially for "Mapping Virtual To Internal System".


Thanks a lot.





How can I add a role to my user

$
0
0

Hello.

 

I am doing the tutorial Creating an SAP HANA XS Application. In step 8 it says:

Productive SAP HANA instance

    1. In the Systems view, expand Start of the navigation pathSecurityNext navigation stepUsersEnd of the navigation path and then double-click your user ID.
    2. On the Granted Roles tab, choose the + (Add)  button.
    3. Select the model_access role in the list and choose OK. The role is now listed on the  Granted Roles tab.

 

I have done so, but everything in my user is greyed out:

 

screenshot1.jpeg

There is also no such role in the list, especially not a model_access role.

How do I get the rights to add a role to my own user?

 

Thank you in advance,

 

Robin

 

State-of-the-art Authentication Mechanisms in the Cloud with SAP Cloud Identity Service

$
0
0

How can you ensure secure operations while offering easy cloud access to business data?

Delegate Authentication.png

The SAP Cloud Identity service simplifies and secures access to your business data, allowing you to control user access based on proven security standards. This comprehensive cloud service provides state-of-the-art authentication mechanisms, secure single sign-on functionality, and on-premise integration.

The SAP Cloud Identity service empowers users to log in just once — from anywhere, on any device — and gain access to all authorized applications.

Spend less time on operations and more on innovation by relying on the SAP Cloud Identity service.

For more information, see SAP Cloud Identity Service



Release Notes for SAP HANA Cloud Platform

$
0
0
Release Notes for SAP HANA Cloud Platform - 20 November 2014
FunctionType of ChangeDescription
CockpitNew

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

Eclipse ToolsNew

If you have changed logger levels, for example for application debugging  purposes, you can now reset these loggers to their initial state. For more information, see Using Logs in the Eclipse IDE -> Resetting Loggers section.

Eclipse ToolsEnhancement

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.

SAP HANA, Console ClientEnhancement

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, see restart-hana.

SAPUI5

Enhancement

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

 

 

Release Notes for SAP HANA Cloud Platform - 6 November 2014
FunctionType of ChangeDescription
Cockpit, DeployNew

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

Cockpit, FavoritesNew

You can now tag Java applications as favorite. All favorite applications appear with key information in the new Favorite Applications panel on the Account dashboard.

Java Web Tomcat 7Enhancement

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

Java Applications, DeployEnhancement

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

Enhancement

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.

 

 

Release Notes for SAP HANA Cloud Platform - 23 October 2014

 

FunctionType of ChangeDescription
Console Client, Java ApplicationsEnhancement

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.

Java Applications, DeployEnhancement

The REST API for lifecycle management operations with applications running on SAP HANA Cloud Platform is now generally available.

For information about using the API, seehttps://api.hana.ondemand.com/lifecycle/v1/documentation.

CockpitEnhancement

Subscribed Java applications will now show their run state in the subscription dashboard.

SAPUI5Enhancement

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

HTML5 Applications

Enhancement

The documentation now includes instructions for:

 

 

Release Notes for SAP HANA Cloud Platform - 9 October 2014
FunctionType of ChangeDescription
Data SynchronizationNew

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.

CockpitNew

SAP HANA Cloud Platform offers a new role - Support User.Designed for technical support engineers, this role allows you to read almost all data related to an account, including metadata, configuration settings, and log files. Note that to be able to read database content, you need to be assigned the appropriate database permissions by a database administrator. For more information, seeAssigning Members to Accounts.

Eclipse ToolsEnhancement

Eclipse Tools have the following enhancements:

  • The autocomplete feature is now enabled for the Account name, User name and Database user fields in plugin SAP HANA Cloud Platform Tools for Connecting to SAP HANA Systems.
  • TheServersview in Eclipse Tools now provides direct links to the application dashboard in the cockpit and the application URLs. For more information, seeServer Endpoints in the Eclipse Tools.
Console ClientEnhancement

You can choose where the logs from a command output will be displayed - in log files or in the console client. For more information, seeVerbose Mode of the Console Commands Output.

SAP Development Tools for Eclipse (Download Site)Enhancement

The home page and the menu titles of the Download Site have been optimized to become more concise and clear.

SAPUI5Enhancement

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

SAP River Rapid Development Environment

Renaming

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

 

 

Release Notes for SAP HANA Cloud Platform - 25 September 2014
FunctionType of ChangeDescription
Eclipse ToolsEnhancement

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.
SAPUI5Enhancement

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

Eclipse ToolsBugfix

Sharing an XS project on the Trial landscape, when a system is added via Add Cloud System, is now possible.

SAP HANA Cloud Connector

Bugfix

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.

 

 

Release Notes for SAP HANA Cloud Platform - 11 September 2014
FunctionType of ChangeDescription
Connectivity Service, Java Web Tomcat 7Enhancement

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

Eclipse ToolsEnhancement

Eclipse Tools have the following enhancements:

  • The SHINE SP6 sample is added to the list of SAP HANA samples for import. For more information on importing samples, seeSamples. A new GitHub repository holds the SHINE SP6 content:https://github.com/SAP/cloud-hana-shine-opensap.
  • The runtimes and local server names in the Eclipse IDE are adjusted so that each server now complies with a particular runtime type.  For more information, seeSetting Up the Runtime Environment
  • Java Web Tomcat 7 is now shown when adding a new runtime in the Eclipse IDE.

SAPUI5

Enhancement

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

 

 


Release Notes for SAP HANA Cloud Platform: Security Bugfix - 29 August 2014
FunctionType of ChangeDescription
SAP HANA Cloud ConnectorBugfix

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.

 

 

 

Release Notes for SAP HANA Cloud Platform - 28 August 2014
FunctionType of ChangeDescription
Java Applications, DeployNew

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.

HTML5 Applications
New

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 EnvironmentNew

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)

EnhancementYou can change deploy parameters without redeploying the whole application via the console client command set-application-property. For more information, seeset-application-property (beta).

SAP Development Tools for Eclipse

(Download Site)

Enhancement

A new section about SAP River RDE is now available in theSAPUI5 Toolstab of the Download Site. For more information, seehttps://tools.hana.ondemand.com/#sapui5.

Persistence ServiceEnhancement

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.

SAPUI5Enhancement

SAPUI5 distribution 1.22.5 (including runtime 1.22.6 & documentation) has been released. The distribution is also available as a service for HTML5 applications. For more information, seeAccessing SAPUI5 Resources.

Eclipse ToolsEnhancementAn option to add a cloud system in the Add System toolbar dropdown is now available.

Eclipse Tools

Bugfix
  • 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>)

 

 

 

Release Notes for SAP HANA Cloud Platform - 14 August 2014

FunctionType of ChangeDescription
SAP HANA Cloud ConnectorEnhancement

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.
SDK, Database Tunnel
EnhancementThe SDK sample projects persistence-with-jpa and persistence-with-ejbdemonstrate how JPA entities can be tested against SAP HANA database using the database tunnel.

For more information, seeAutomating the Use of Database Tunnels.

Eclipse Tools

Enhancement

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>).

 

 

 

Release Notes for SAP HANA Cloud Platform - 31 July 2014
FunctionType of ChangeDescription
Authentication Configuration UINew

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 ToolsEnhancement

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.
SDK
Enhancement
To avoid maintaining clear-text passwords when using the Maven Plugin, you can now store your SAP HANA Cloud Platform user name and password in the settings.xml file. For more information,seehttp://maven.apache.org/guides/mini/guide-encryption.html.
HTML5 ApplicationsEnhancementYou can now use permissions to protect HTML5 applications. The application developer defines the permissions in the application descriptor file, and you use the cockpit to define roles and map the permissions to the roles. For more information, seeManaging Roles and Permissions.
SAPUI5EnhancementNew version 1.22.3 of SAPUI5 runtime and documentation has been released.

Connectivity Service

Bugfix

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.

 

 

 

Release Notes for SAP HANA Cloud Platform - 17 July 2014
FunctionType of ChangeDescription
SAP HANA Cloud ConnectorNew

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.

Persistence Service
Enhancement
For the purposes of Java development on productive SAP HANA instances, the persistence service now allows you to bind productive SAP HANA instances to Java applications with custom logons. By using custom logons, you can determine which schemas a Java application is able to access. For more information, seeBinding Productive SAP HANA Instances to Java Applications.
Eclipse ToolsEnhancementSAP HANA Cloud Platform Tools for Java now support the latest Eclipse Luna release (in addition to Kepler). The support for Juno has entered end of maintenance. For more information, seeInstalling SAP Development Tools for Eclipse.
CockpitEnhancementTables in the cockpit now use up the remaining screen real estate on the page if necessary or show exactly the number of rows for which data is available and no empty rows anymore.
SAPUI5EnhancementNew version 1.20.11 of SAPUI5 runtime and documentation has been released.

Eclipse Tools

Bugfix

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.

 

 

 

Release Notes for SAP HANA Cloud Platform - 3 July 2014
FunctionType of ChangeDescription
Connectivity ServiceEnhancement
HTTP destinations are extended by a new OAuthSAMLBearerAssertion authentication type. For more information, seeSAML Bearer Assertion Authentication.
Cockpit
Enhancement
If you try to log on to a landscape on which you do not have an account, the cockpit now presents a page that allows you to select the correct landscape and gives you additional guidance.
SDKEnhancementThe SDK samples can now be built with Maven whether or not you are executing the build behind a proxy. If you have a proxy, the build takes the Java default properties for proxy definition (no longer environment variables that fit Windows only). If you have no proxy, nothing must be done anymore.
Console Client, DeploymentEnhancementThe console commands in the deploy group show an improved message in case of an authentication error.
SAPUI5EnhancementNew version 1.20.9 of SAPUI5 runtime and documentation has been released.

SAP HANA

Enhancement

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

 

 

 

Release Notes for SAP HANA Cloud Platform - 19 June 2014
FunctionType of ChangeDescription
Java Web Tomcat 7New
Java Web Tomcat 7 is now available as a Beta on Trial. This new simplified edition of the Java Web application runtime container provides optimized performance (startup time and memory footprint).

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, seeJava Web Tomcat 7 .

New Data Center in AustraliaNew

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.

JMX ConsoleNew
An MBean web console is available as a Beta feature on the Trial landscape. It exposes all MBeans available in the SAP HANA Cloud Platform runtime including custom ones registered by your applications. You can view the values of their attributes and execute their operations. For more information, seeUsing the JMX Console.
Console Client, Java ApplicationsEnhancement

Thehot-updatecommand 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.

SAP HANA XSEnhancement

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

User Management
Enhancement
SAP HANA Cloud Platform can use an on-premise AS Java system to check user credentials, search, and retrieve user information. For more information, seeConfiguring a Connection with an On-Premise User Store.
Eclipse ToolsEnhancement

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.
Document ServiceEnhancementThe document service XS consumption library now supports serialization/deserialization of a CMIS session to improve performance.
Connectivity ServiceEnhancementJCoRecord offers toJSON() methods that allow the results of a function module invocation to be transformed easily into a JSON representation. Such a document can be consumed immediately by a SAP UI5 widget data model.
SAPUI5EnhancementNew version 1.20.8 of SAPUI5 runtime and documentation has been released.

Persistence Service, Roles and Permissions

Enhancement

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.

 

 

 

Release Notes for SAP HANA Cloud Platform - 5 June 2014
FunctionType of ChangeDescription
SAP River RDE (Beta)New
SAP River Rapid Development Environment (RDE) is beta-released as part of SAP HANA Cloud Platform. This development environment provisioned in the web offers wizards, templates, editors and preview functionality for creating new or extending existing SAP Fiori applications. River RDE aims to bring simplification and productivity in the collaborative design, development and deployment of HTML5 applications. For more information, seeSetting Up SAP River RDE.
SDKEnhancement
The SDK samples are reworked to demonstrate and use theSAP HANA Cloud Platform Maven Plugin. The plugin is also published on theMaven Centralrepository, which eases the consumption of the plugin in Maven-based development projects.

Two new blog posts give more information:

Cockpit, MonitoringEnhancement

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.

Cockpit, Destinations EditorEnhancement

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.

Cockpit
Enhancement
The visual appearance and the usability of the integrated cockpit help is improved.
Document ServiceEnhancementApache Chemistry OpenCMIS libraries are updated to version 0.11.0.
SAPUI5EnhancementNew version 1.20.7 of SAPUI5 runtime and documentation has been released.

 

 

 

Release Notes for SAP HANA Cloud Platform - 22 May 2014
FunctionType of ChangeDescription
Cockpit, Role ManagementNew
Account administrators can manage roles in the Members panel of the cockpit. The first two supported roles are Administrator and Developer. For more information, seeAccount Member Roles.

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.

Client Certificate AuthenticationNew
You can enable client certificate authentication to SAP HANA Cloud applications. For more information, seeEnabling Client Certificate Authentication.
Cockpit, MonitoringEnhancement

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.

Database TunnelEnhancement

The command is enhanced as follows:

SDK
Enhancement
A Maven plugin is now available in Maven Central Repository for the different Java runtimes of the SAP HANA Cloud Platform. This allows you to conveniently call the SAP HANA Cloud Platform console client and its commands from the Maven environment. A dedicated goal in the plugin maps to each console client command, which makes writing automated integration tests and deployment much easier than before. For example, command deploy:restart maps to goal neo-java-web:restart. For more information, seeMaven Plugin.
Eclipse ToolsEnhancementServer Adapter now provides helpful UI messages and server logs in case your application is in non-working state.
SAPUI5EnhancementNew version 1.20.6 of SAPUI5 runtime and documentation has been released.
MultitenancyBugfixTenant subscriptions are taken into account automatically when the application is in maintenance or downtime mode. It is no longer needed to subscribe the consumer account separately to the application or downtime page.
SAP HANABugfixProductive SAP HANA instances are now provisioned with debugging and developer mode switched off (that represents the SAP HANA default). Account administrators are granted permissions to switch the settings on and off when needed.

 

 

 

Release Notes for SAP HANA Cloud Platform - 8 May 2014
FunctionType of ChangeDescription
HTML5 Applications (Beta)New
SAP HANA Cloud Platform enables you to develop lightweight HTML5 applications in a cloud environment. HTML5 applications consist of static resources and can connect to an existing on-premise or on-demand REST service. The static content of the HTML5 applications is stored and versioned in Git repositories.

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

Cockpit, MonitoringEnhancement
You can view the current metrics of productive SAP HANA instances in the cockpit. For more information, seeViewing Monitoring Metrics of a Productive SAP HANA Instance.
Cockpit, Application RolesEnhancement

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.

Java Applications, WebSocket
Bugfix
The WebSocket protocol now works correctly with Internet Explorer 10 and 11.

 

 

 

Release Notes for SAP HANA Cloud Platform - 24 April 2014
FunctionType of ChangeDescription
SAP HANA XS, Document ServiceNew
You can now consume the document service from SAP HANA XS applications. This feature is currently in beta state. For more information, seeConsuming the Document Service.
Connectivity ServiceNew
A new interface com.sap.core.connectivity.api.authentication.
AuthenticationHeaderProvider has been introduced. It provides methods for application-to-application and on-premise SSO authentication and can be used to initialize arbitrary HTTP clients on application level. For more information, seeAuthenticationHeaderProvider API.
SAP HANA Cloud ConnectorNew
SAP HANA Cloud connector 2.3.0 is released on thedownload sitewith the following features and fixes:

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.
Document ServiceEnhancement
The document service now supports roles and groups in Access Control Lists (ACLs). For more information, seeACLs in the Document Service.
Document Service, DocumentationEnhancement
Best practices documentation about repository and folder handling is available. For more information, seeDocuments and Folders.
Console ClientEnhancement
Commands can return structured (machine readable) json output through the optional parameter: --output json. For more information, seeMachine-Readable Command Output.
Cockpit, SAP HANA XS MonitoringEnhancement
You can configure availability checks and view the status of SAP HANA XS applications running on a productive SAP HANA instance via the cockpit. For more information, seeConfiguring Availability Checks for SAP HANA XS Applications from the Cockpit.
Cockpit, Destinations EditorEnhancement
In the cockpit you can configure destinations on account level. Account-level destinations are globally visible to all applications and platform services in the account. For more information, seeConfiguring Destinations from the Cockpit.
TenantContext APIEnhancement
The com.sap.cloud.account.TenantContext interface has been extended by a new method – getAccountName().  For more information, seeAPI Documentation.
Connectivity ServiceEnhancement

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.

Connectivity ServiceEnhancement
The JCo runtime in SAP HANA Cloud Platform now supports principal propagation to on-premise systems. The on-premise side must use Cloud connector version 2.3.0.
SAP HANAEnhancement
The trial SAP HANA instances have been upgraded to revision 73.
SAPUI5
Enhancement
New version 1.20.5 of SAPUI5 runtime and documentation has been released. For more information, see therelease notes.

 

 

 

Release Notes for SAP HANA Cloud Platform - 10 April 2014
FunctionType of ChangeDescription
Security, Identity and Access ManagementNew
You can manage your custom SAML 2.0 identity providers with productive HANA XS instances. For more information, seeConfiguring SAML 2.0 Authentication.
SAP HANA Web-based Development WorkbenchEnhancement
You can use the SAP HANA Web-based Development Workbench also on the trial landscape. For more information, seeDeveloping with SAP HANA Web-based Development Workbench.
Console Client, SAP HANA ServicesEnhancement

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

Console Client, DeployEnhancement
You can start an application process from the console client in disabled mode so that it is not available for new connections. For more information, seestart.
SAP HANA XS, MonitoringEnhancement

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.

Cockpit, Destinations EditorEnhancement
The Destinations editor has been re-designed for easier navigation and extended with new features, such as cloning existing destinations and deleting configured certificates. For more information, seeConfiguring Destinations from the Cockpit.
SAPUI5
Enhancement
New version 1.18.10 of SAPUI5 runtime and documentation has been released. For more information, see therelease notes.

 

 

 

Release Notes for SAP HANA Cloud Platform - 27 March 2014
FunctionType of ChangeDescription
Document ServiceNew
The Document Service features console client commands for managing document repositories.  For more information seeConsole Client Commands-> Document Service section.
SAP HANA Predictive Analytic LibraryNew

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.

SecurityNew
A set of new commands in the console client allows the account administrator to modify the keystore of productive SAP HANA XS systems to upload, delete and list certificates. For more information, seeupload-hanaxs-certificates, list-hanaxs-certificatesanddelete-hanaxs-certificates.
Console Client, DeployEnhancement

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

CockpitEnhancement
You can disable (and enable) Java application processes from the cockpit. Disabled Java application processes don't accept new session requests. For more information, seeStarting and Stopping Applications.
CockpitEnhancement

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.

Connectivity Service, SecurityEnhancement
The list of certificate authorities that SAP HANA Cloud Platform trusts by default is now available. For more information, seeTrusted Certificate Authorities.
SAPUI5Enhancement
New version 1.18.9 of SAPUI5 runtime and documentation has been released. For more information, see therelease notes.
SAP HANA Cloud ConnectorDeprecation

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.

MonitoringBugfix
An issue with custom monitoring metrics not reported correctly in case you have registered many custom metrics is fixed.
SAP HANA Cloud Platform Tools for Connecting to SAP HANA Systems
Bugfix
The following issues are fixed:
  • 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.

 

 

 

Release Notes for SAP HANA Cloud Platform - 13 March 2014
FunctionType of ChangeDescription
LicensingNew
SAP HANA Cloud Platform has enlarged its scope and now encompasses SAP HANA Infrastructure Services, SAP HANA DB Services and SAP HANA Application Services. The new package offering comes with a new pricing model. For more information, seeSAP HANA Marketplaceand the blogpostThe full package.
Password Storage APINew

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

Console Client, Java ApplicationsNew
A new command hot-update (beta) enables you to redeploy and update the binaries of an application faster than the normal deploy and restart. The update happens directly on the already running application process. For more information, seehot-update.
SAP Development Tools for Eclipse (Download Site)New

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.

MultitenancyEnhancement
The existingtenant APIhas been extended by a new execute() method to run background threads on behalf of a given tenant.
Cockpit, LogsEnhancement

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.

Cockpit, MonitoringEnhancement
You can now register availability checks for your Java applications also from the cockpit and check the application availability status from the Java Application Dashboard. For more information, seeConfiguring Availability Checks from the Cockpit.
SAP Development Tools for Eclipse (Download Site)Enhancement
The download site now uses geolocation-based load balancing for SAP Development Tools for Eclipse (tools.hana.ondemand.com). When installing tools, you are routed to the nearest data center. The response time and the download times are significantly improved for users in the US region.
Eclipse ToolsEnhancement
SAPUI5Enhancement
New version 1.18.8 of SAPUI5 runtime and documentation has been released. For more information, see therelease notes.
HTTPSDeprecation

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.

Eclipse Tools, SDKDeprecation

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.

Eclipse Tools
Bugfix
The following issues are now fixed in Eclipse tools:
  • "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.

 

 

 

Release Notes for SAP HANA Cloud Platform - 27 February 2014
FunctionType of ChangeDescription
Java ApplicationsNew
SAP HANA Cloud Platform now supports JSR 356 Java API for WebSocket in productive state.
For more information, seeJava EE 6 Web Profile.
CockpitEnhancement
The cockpit now has integrated help. You can click the Help link next to a panel title in a cockpit page to access the contextual help for the respective panel and further links to the documentation.
CockpitEnhancement

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.

Cockpit, SAP HANA XSEnhancement
The use of packages in developer accounts on the trial landscape is simplified: a developer account can have only one  SAP HANA package, and you can create that package easily with one button click.

For more information, see Creating SAP HANA Packages.

Cockpit, LogsEnhancement
  • 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.

Cockpit, Logs, MonitoringEnhancement
The cockpit has now completely adopted the process ID as an identifier of application processes in logs and monitoring charts.
SDKEnhancement
  • 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.
TenancyEnhancement
Application logs now include tenant names in each log entry, which allows you to filter and explore relevant logs for a particular tenant.
For more information, seeViewing the Default Trace.
Cockpit, OAuthEnhancement
The UI for registering OAuth clients is now available for cross-account subscribed applications.

For more information, see Configuring OAuth Authorizations.

SAP UI5Enhancement
New version 1.18.6 of UI Development Toolkit has been released.
CockpitDeprecation
The cockpit no longer supports Internet Explorer 8. For more information about supported browsers, seeProduct Prerequisites and Restrictions.
SDK, DestinationsBugfix
The following bugfixes are provided for SDK 2.x:
  • 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.
Connectivity Service
Bugfix
The JCo runtime for SAP HANA Cloud Platform is upgraded and includes the following bugfixes:
  • 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.

 

 

 

Release Notes for SAP HANA Cloud Platform - 13 February 2014
FunctionType of ChangeDescription
Console Client, DeployEnhancement
You can now use the following two new commands:
  • 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.

CockpitEnhancement
In the cockpit, you can now clearly differentiate infrastructure from application error states for Java applications which makes it easier for you to detect and fix application issues.

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

Cloud Environment VariablesEnhancement

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.

SDKEnhancement
The SDK samples will now demonstrate and make use of the SAP HANA Cloud Platform API which is now also published to Maven Central for easier consumption in Maven-based development projects.
SAP UI5Enhancement
New version 1.18.5 of UI Development Toolkit has been released.

For more information, see the release notes.

Feedback ServiceEnhancement
You can now provide feedback for the feedback service and its UIs.

For more information, see Getting Feedback for Applications.

Cockpit, DestinationsEnhancement
The Destinations editor in the cockpit is extended to support the new authentication type PrincipalPropagation. This new authentication type works for on-premise destinations (proxyType=OnPremise) and requires Cloud Connector version 2 (CloudConnectorVersion=2).
SAP HANA Cloud Connector
Enhancement
SAP HANA Cloud Connector 2.2 has been released with the following features:
  • 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.

 

 

 

Release Notes for SAP HANA Cloud Platform - 30 January 2014
FunctionType of ChangeDescription
Cockpit, HANA XSEnhancement
Users of productive HANA XS systems are now able to create their SAP HANA database users within the cockpit.
For more information, seeCreating Your Database User.
CockpitEnhancement
You can now see the runtime type, for example Java Web or Java EE 6 Web Profile, together with the runtime version.
CockpitEnhancement
You can now see the process ID for Java application processes in the UI. The process ID for processes that are still running is also shown with each log file, so that you can match a certain log file to a running process. 
CockpitEnhancement
In the process list of the application dashboard, you can now see the aggregated status of processes including run state, runtime version and metrics. This makes spotting problems with individual processes much easier.

For more information, seeChecking the Application Status.

Cockpit, MonitoringEnhancement
The following usability improvements are now available:
  • 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.

SDK, Connectivity ServiceEnhancement
The existing SDK sample application “connectivity-outbound-internet” is renamed to "connectivity" and is also extended to cover an example for on-demand to on-premise connectivity. The tutorials below are adopted accordingly to describe both connectivity scenarios, fitting to the extended sample application:

Using Internet Services in Cloud Applications

Using On-Premise Back-End Services in Cloud Applications

SAP UI5Enhancement
New version 1.16.9 of UI Development Toolkit has been released.
DocumentationEnhancement
SAP HANA Cloud Platform now uses geolocation-based load balancing for SAP HANA Cloud Platform documentation (help.hana.ondemand.com). When opening the documentation, users are routed to the nearest data center. The response time for opening and browsing the documentation is significantly improved for users in the US region.
Connectivity Service: Destination ConfigurationIncompatibility
To support SAP HANA Cloud Platform service JNDI resource lookups in EJBs with the release of neo-sdk-javaee6-wp-2.25.7, an incompatible behavior had to be introduced concerning the time destinations need to be configured. For more information, seeIncompatibility announcement for neo-sdk-javaee6-wp-2.25.7 affecting destination configuration time.
Eclipse ToolsBugfix
The following issues are now fixed:
  • 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.
Java EE 6 Web Profile
Bugfix
SAP HANA Cloud Platform services can be injected as JNDI resources in EJBs.

 

 

 

Release Notes for SAP HANA Cloud Platform - 16 January 2014

 

FunctionType of ChangeDescription
Cockpit, MonitoringEnhancement
You can now choose a custom time period when viewing history of metrics for a single process.
You can also compare the metrics history of different processes within an application.
For more information, see Viewing Monitoring Metrics.
ID Service, Authorization ManagementEnhancement
You can now directly assign users to groups.
Cloud ConnectorEnhancement
Version 1.3.2 improves the security of SCC traffic tracing by introducing a 4-eyes principle for the activation of HTTP and RFC protocol traces: activating a trace level that dumps traffic data requires the approval of two separate users.
SAP UI5Enhancement
New version 1.16.7 of UI Development Toolkit has been released.
Console ClientEnhancement
The disabled status for applications processes, as well as maintenance status for applications are now shown in the console client.
Console Client, DeployDeprecation
The parameter --severity for setting log severity during deploy has been deprecated.
Eclipse ToolsBugfix
An issue with applications deployed on a newly created cloud server (via Run → Run on Server) sporadically not being published on the server has been fixed.
Console Client, DeployBugfix
The deploy command now shows improved output in case you are trying to select a non-existing runtime version.
Console Client
Bugfix
It is no longer possible to start maintenance for an application that is used as a maintenance page.

For more information about older release notes, see:

HCC to ECC (HTTP)

$
0
0

Hi,

 

Trying to setup HCC to connect to ECC for some Fiori trials. Connector state is all green in HCC and below are my settings. But when trying to connect to a service-catalog I get the following error in Web- IDE. Appreciate all help on what's missing

 

Capture3.PNG

 

Fig1 is the settings in HANA cloud connector - 'access control'

Capture1.PNG

 

Fig2 is the settings on HANA Cockpit platform - 'destinations'

Capture2.PNG

cheers,

Ram

cross origin issue for hana cloud portal

$
0
0

Hi Everyone,

 

     Currently i have one issue when add Hana cloud portal for my SF extension module,  when I try to  access portal through SF instance. It will have cross origin issue.

 

     Does anyone know how to solve this cross origin issue?  I already config the SSO etc.

 

 

Error message like below:

 

Refused to display 'https://cloudportaltrial-xxxxx.hanatrial.ondemand.com/portal/index.h…cMcvc8y8yMcvcSKbCJbiQSKbC0%2B0%2B1px%2B0!1!Y1WvH!%2F.dcss%3Bmod%3D152a71e1' in a frame because it set 'X-Frame-Options' to 'SAMEORIGIN'.

 

 

Best Regards,

 

Chris.Bai

Question about destinations in HCP

$
0
0

I posted a question a few days ago and got no response but I've continued to research it and have learned a little more but it raises a fundamental question.

 

I'm attempting to create a destination in HCP but have run into some issues and I'm having trouble understanding how this works.  I'm hoping someone can clear it up for me.  I've created services on our HANA system and in NWG.  I can access both successfully using a REST client through the internet.  When I create a destination in the HCP Cockpit or connection in SMP cloud I configure it using Internet as opposed to OnPremise because I'm able to access via the Internet.  However, when I test it, I get a 403 or Target Service Not Allowed error.  According to the SMP documentation, this means that the service should be configured as OnPremise.  This is confusing.  What is the criteria for requiring an OnPremise connection?  My understanding was that it was required when a service could not be accessed directly via the Internet.

 

If anyone can clear it up for me, I would greatly appreciate it.

 

Ross

RaspberryPi on SAP HCP - IoT blog series part 3: Sending sensor data from Raspberry Pi to your cloud-app

$
0
0

In the second blog post of this blog post series around Raspberry Pi and the SAP HANA Cloud Platform we've taken care of the receiving part in the cloud. If you've followed the instructions in the blog post you have now an app running on your free developer account which can receive sensor data and persist it and provide some output in JSON format for the user interface.

 

In this blog post we'll now look into the code for the Raspberry Pi and will connect an external temperature sensor to our Raspberry Pi. That code will be sending the temperature data from the CPU inside the Raspberry Pi as well as the temperature from the external temperature sensor.

 

Screen+Shot+2014-11-12+at+14.20.26.png

 

Table of Contents

 

 

But first thing first. Let's first tackle some hardware challenges.

 

Connecting the external sensor

This is the part where you need to have solding skills (or know somebody who has). Follow the instructions on this blog under the section "

Step Two: Connecting the Temperature Sensor" and connect your sensor to your Raspberry Pi.

 

CAUTION:

Please be aware that this is hardware-stuff which actually can react in a physical way like getting hot, explode, burn you, etc.. So you either know what you are doing, find someone who can do it, buy it somewhere ready-made or just leave it. You do this at your own risk (which you've probably know before anyways, but just mentioning it here, so you don't forget while reading :-)

 

 

The Java app for the Raspberry Pi

You can find the code for your Raspberry Pi in the file I've attached to this blog post.

Just unzip it on your machine and open a console to connect to your Raspberry Pi like I've described in my first blog post of this series.

 

After logging-in to your Raspberry Pi change the current directory to the folder you've created for your scripts. If you did it, like I've done it, you'll switch to your myscripts folder.

 

cd /home/pi/myscripts

 

The next thing we do is to create the app on the Rasperry Pi. To create the corresponding Java file we create a file called Temperature.java with the text editor nano.

 

nano Temperature.java

 

Your window should look more or less like this:

Screen Shot 2014-11-21 at 17.07.11.png

 

Now copy the content of the file you've extracted before on your machine into your clipboard. Switch back to the console with the opened nano editor and paste the clipboard into the window.

 

Screen Shot 2014-11-21 at 17.08.44.png

 

Now press the command and X key and the editor will ask you to either press Y to save the file or N for not doing it. Press Y and hit the return key to save the file.

Screen Shot 2014-11-21 at 17.11.17.png

Before you can move forward you need to adapt the code so it works with your account. So let's open the Temperature.java file again in nano

nano Temperature.java

 

Check proxy

First thing you need to do is adapt the USEPROXY variable in the Temperature.java file. Set it to false if you are working from home, as most probable you don't use a proxy server at home. If you do have a proxy server for accessing the internet, set it to true.

 

Adapt URL of Java app on your SAP HANA Cloud Platform account

Now look into the variable called SERVLET_URL_cloud and change it to the URL of your application that you've deployed in the second blog post of this series.

 

Get Hardware ID of the external temperature sensor (optional)

In case you want to use the values of the external temperature sensor, you need to find out it's ID before. To do that you should ensure you've added the modules for the sensors as described in the first blog post and also connect the sensor to the Raspberry Pi as described above.

 

Now move to the folder /sys/bus/w1/devices/ and search for a subfolder there called 28-xxxxxxxxxxx. That folder name is the id of your sensor.

 

ls /sys/bus/w1/devices/

If you don't get any results or an error message saying "No such file or directory" you've either not connected the external sensor, or you've connected it wrongly to your Raspberry Pi.

 

Once you have the id of your sensor you need to assign it to the variable called SENSOR_HARDWARE_ID in your Temperature.java file.

 

Assign DB id's of sensors to the ones on your Raspberry Pi

In the past blog post you've already created at least one sensor in your database. What you need to do now is to get the database ids for 2 sensors. So if you haven't done, yet, create at least two sensors in your app like described in the past blog post.

If you call your app you should see something like this

Screen Shot 2014-11-21 at 17.44.25.png

Take the number after the "id" field and assign them in your code to the variables SENSOR_DB_ID_CPU_TEMP and SENSOR_DB_ID_TEMP_SENSOR.

 

Compile the Temperature.java file

After doing all the changes you need to save the file in nano. Now you need to compile the file. To do that enter this command in your myscript folder:

javac Temperature.java

 

Should you get an error message you might have messed-up the code. Try again :-)

If there are no errormessages a new file was created called Temperature.class. Check it by listing up the files in your myscript folder:

ls -l

 

Send your sensor data to your app on SAP HANA Cloud Platform

 

The last thing missing now is to actually run the app. To do it simply we call the Java app like this

java Temperature 10

The 10 at the end tells the app that it should iterate through the app 10 times.

 

Screen Shot 2014-11-21 at 17.58.22.png

 

If everything worked fine you should now be able to see the sent sensor data in your Java app on your account.

 

Screen Shot 2014-11-21 at 17.59.32.png

Next Steps

Now that we have worked on the hardware side of this, we'll work on the user interface to provide a nice looking dashboard for Rui's Fish Import/Export Inc..

 

Screen+Shot+2014-11-12+at+14.20.26-1.png

 

That's what we'll do in the next blog post.

 

Have fun.

 

Best,

Rui


RaspberryPi on SAP HANA Cloud Platform

$
0
0

When thinking about the SAP HANA Cloud Platform there are some things you'd not immediately connect to it. One is certainly a Raspberry Pi.

 

The Raspberry Pi is a low-cost credit-card-size computer with an ARM-processor that has a huge community and since today more than . It costs around 35 Euro and runs on special Linux versions like e.g. Raspian (adapted Debian Linux). Produced for the first time in 2012 by the end of 2013 already more than 2 million devices were sold!

 

Along with one HDMI, one Ethernet, and two USB ports the RaspberryPi has also digital input pins. Meanwhile there is even a new revision B+ available providing 4 USB ports and some more improvements. Meaning you can connect digital sensors to it or, via an analog-to-digital convert, or analog sensors. With the low price and these connectivity features it's the ideal candidate to run internet-of-things scenarios on it.

 

That's the reason why I thought: why not letting the Raspberry Pi send sensor data to an account on the SAP HANA Cloud Platform? And that's why I've setup this blog post series around this topic.

 

In the next weeks and months I'll keep on adding additional blog posts to this series so that you can see you to use your Raspberry Pi for internet-of-things scenarios.

And maybe you get inspired and think of other scenarios where you need sensor data in your SAP HANA Cloud Platform account to bring the internet-of-things into the products and services of your company.

 

Currently these are the blog posts I'm planning to release in a monthly or bi-weekly cycle:

 

 

Best,

Rui

oData Authorization Error

$
0
0

Hi All,

 

I've created a trial account and I'm trying to expose a table using an oData service (xsodata file).

 

The service is created correctly, since when running https://...myhanaxs/tweet.xsodata and https://...myhanaxs/tweet.xsodata/$metadata I'm able to see the corresponding pages.

 

The problem is that, when I try to GET from the service, I receive the following error message:

 

<exception>

exception  1: no.71000258  (ptime/query/checker/query_check.cc:2547)    Not authorizedNO exception throw location recorded. Stack generation suppressed.

</exception>

 

I've tried to create my table in both schemas (the one starting with DEV_ and the other starting with NEO_) but both tables, when referenced by the xsodata file result in the same error.

 

Do you know what is missing?

 

Thanks and regards,

Roberto Falk

SAPUI5, ODATA and anonymous database access in the HCP: How to do it

$
0
0

The HANA Cloud Platform trial account is free of charge. This is possible because multiple developers work on the same databases in parallel. For that reason, additional safety measures have been implemented. This makes the application development quite tricky sometimes. A couple of weeks ago I developed an SAPUI5 application using my HANA Cloud Platform trial account. When I wanted to receive data from the database, it was not working. The process of figuring out the problem and solving it took quite some time but I came up with a solution. Jamie Wiseman from the SAP HANA Academy team encouraged me to explain my solution in the SCN, so that’s what I am going to do

 

The issue

My SAPUI5 Application accesses a database table containing Geodata. The standard way of doing this in SAP HANA is creating and using an ODATA service. Creating an ODATA service in SAP HANA is very easy: You simply need to create another file (file extension .odata) in your XS or SAPUI5 package and insert something like:

service {
"SCHEMA"."TABLE" as "Geodata" keys generate local "GENERATED_ID";
}

At first you of course should test the ODATA interface. You can do this by just calling it in your browser. The URL is like:

 

https://s1hanaxs.hanatrial.ondemand.com/path/to/your/package/odataservice.xsodata/servicename?json&$select=COLUMN,COLUMN,…


Be careful when you test your service. When I did it on my laptop, I had no problems. My SAPUI5 app however seemed to be unable to access data. Using a different browser, I finally understood the issue: Normally, I have to logon with my S-User first.

Logon.png

    ODATA access will trigger S-USER Logon process

 

The other browser had the SAP Certificates for automated logon installed, so testing with it had always worked. This by the way also applies to the SAPUI5 application itself. If you want to be able to access it without logging on with your S-User, it does not work out of the box.

 

First problems

At first, I looked at the settings for authentication in the SAP HANA Cloud Platform Cockpit (Trust). Unfortunately, your only alternative to the authentication via S-User is setting up a connection to another trusted identity provider. I am no expert on this, but I guess it would be a lot of work and at the end also require some sort of authentication which is not supported by a standard SAPUI5 application. So this approach is a dead end.

My second try was using SQLCC which is described very well in a video from the SAP HANA Academy. For this approach, your database user needs certain privileges (role sap.hana.xs.admin.roles::SQLCCAdministrator). These privileges could be used to basically become administrator if you use them right. As the trial instances (just the trial instances) of the HANA Cloud Platform are used by multiple developers in parallel, they don’t have these privileges. Another dead end.

 

Anonymous access to SAPUI5 application

My first step to success was a thread on saphana.com with a solution for anonymous access very similar to the full SQLCC approach. It uses the .xsaccess file in the project. HANA development projects including ODATA services or SAPUI5 applications always need two files to work: “.xsapp” and “.xsaccess”

.xsaccess – as the name says – can contain options for the accessing the application. To enable anonymous access, you have to adjust your file like this:

{
"anonymous_connection": "path.to.your.package::anonuser",
"authentication" : null,
"exposed": true
}

Then you have to create a database user using XS development. You can this by creating a file with the name “username.xssqlcc”. I used the name “anonuser” in .xsaccess, so the filename has to be “anonuser.xssqlcc”. There is not a lot of content, but you can insert a description. Just remember To have brackets in the file:

{
"description" : "Anon SQL connection"
}

Now you can access your development projects in this package without having to authenticate with your S-User. It works fine for the SAPUI5 applications. However, access to the database is still not possible. If you try to access the ODATA service like I described, you will no longer see a logon screen. Instead you won’t see anything. By using the development tools of your browser, you can examine the response from the server and see something like this:

Development Tools.PNG

   Accessing with an anonymous database user does not work for ODATA

 

Error 500 makes it clear: Using ODATA services anonymously does not work in the HANA Cloud Platform. So I found a different solution. (However: If someone knows a solution for ODATA, please tell me in the comments )

 

Anonymous access to SAP HANA

My next idea was to develop a database interface like odata on my own. As I was already using an XS application project in the HANA Cloud Platform, I tried to do it with XS. Remember that you have to enable anonymous access to the XS application itself before an SAPUI5 application would be able to use it. If you want to access the database out of XS, you do something like:

var conn = $.db.getConnection();
var pstmt = conn.prepareStatement( "select * from NEO_ET72UJMG1CL4IUODE1NJVKJ1O.ADACALL" );
var rs = pstmt.executeQuery();

The problem with that is the first statement. It will not work if you call it using anonymous access. Instead you will get an error code 500 like you did with ODATA. The only way around this is using SQLCC, which is not possible with an SAP HANA Cloud Platform trial account (see “First problems”).

The key to success is the JAVA development in the SAP HANA Cloud Platform. If you access the database out of a JAVA application, it does not require any authentication. This is even the default setting. Using JAVA, you can easily write a little webservice that transfers the data you need to the SAPUI5 application.

A little issue remains: I wanted to be able to create HANA Views on top of my tables. It is important to understand that the standard database schemas of JAVA and XS applications are fundamentally different. The first sign for that are different database versions:

Schemas.PNG

   XS and JAVA Schemas are located on different databases

 

That means you not only have different schemas but actually different databases. Therefore it is not possible to access a table in a JAVA schema out of an XS application using a XS schema. Also, you have far more privileges in the XS schema. The most important one is the privilege to create packages and develop XS and SAPUI5 applications as well as HANA Views in them.

To combine the benefits of anonymous database access and HANA Views as well as XS development, I simply changed the schema binding of my JAVA webservice to the XS schema.

Schemawechsel.PNG

   Changing the schema binding combines the benefit of JAVA and XS in the HCP

 

You can change the schema binding of your JAVA application in the HANA Cloud Platform Cockpit. In the menu on the left side, select "JAVA Applications" and then select your application. On the left side, click on "Schmema Bindings". Now delete the old schema binding and create a new binding to your XS schema.

 

As far as I can tell, there is no benefit from using the JAVA schema over the XS schema (again, please correct me if I’m, wrong). Of course you can also establish multiple bindings for one application if you like.

 

I hope I could help some of you to understand how anonymous access works. Please keep in mind that this issue only exists in the trial account. And please give me some feedback if you like

JAX-RS the missing link between UI5 and HCP Java apps

$
0
0

Many of you may have noticed a gap in the documentation of Hana Cloud Platform development. There is a description of UI5 and how to build nice UIs with this HTML5 technology. And there is a description of how to build backend java based applications which starts with servlet technology?! Wouldn't it be nice to have UI5 and let it communicate with the Java backend and not to build servlets anymore?

 

In fact if HCP would support Java EE 7 Web Profile instead of version 6 you would get JAX-RS support out of the box and can use the JSONModel in UI5 to communicate with your HCP backend. With version 6 you can still use JAX-RS but you have to include it yourself in your application.

 

I want to describe here as an overview whats need to get this done. As normal you need a dynamic Web project in your Eclipse as a start point. I have successfully used Jersey/Jackson as the implementation of the JAX-RS 2.0 standard. If you have a maven project inlude the dependencies as described on Jersey project page. If you don't use maven just include the libs in WebContent/WEB-INF/lib as you would normally do.

 

So what do you need for JAX-RS to work for you? Lets assume you want to create one service class which responds to a HTTP GET on the relative path "/rest/ping" where "rest" shall be the path of all rest based calls and ping the specific part.

 

So you have to do some work in your web.xml first:

  <servlet>

    <servlet-name>com.sap.myapp.MyApplication</servlet-name>

    <init-param>

      <param-name>com.sun.jersey.api.json.POJOMappingFeature</param-name>

      <param-value>true</param-value>

    </init-param>

  </servlet>

  <servlet-mapping>

    <servlet-name>com.sap.myapp.MyApplication</servlet-name>

    <url-pattern>/rest/*</url-pattern>

  </servlet-mapping>

 

This defines a special servlet that you have to write later on and defines that all your REST based services are reachable under the path of "/rest/*" as we wanted to do.

So lets create the class com.sap.myapp.MyApplication which has to extend javax.ws.rs.core.Application, a standard class of JAX-RS. It should look like the following:

package com.sap.coe.hr.sf.par.rest;

 

import java.util.HashSet;

import java.util.Set;

 

import javax.ws.rs.core.Application;


/**

* JAX-RS Application

*/

public class PARApplication extends Application {


  public Set<Class<?>> getClasses() {


    Set<Class<?>> s = new HashSet<Class<?>>();

    s.add(PingService.class);

    return s;

  }

}

 

Here you have to add EVERY service class you write. Normally you would divide your services in several classes. We now have to write the PingService thats added there.

 

/**

* REST

*/

package com.sap.myapp;

 

import javax.servlet.ServletException;

import javax.ws.rs.GET;

import javax.ws.rs.Path;

import javax.ws.rs.Produces;

import javax.ws.rs.core.MediaType;

import javax.ws.rs.core.Response;

 

/**

* JAX-RS Service for ping

*/

@Path("/ping")

public class PingService {

  @GET

  @Path("/")

  @Produces(MediaType.TEXT_PLAIN)

  public Response ping() throws ServletException {

    return Response.ok().entity("pong").build();

  }

}

 

So this service listens on everything on the relative path "/ping". Together with the declaration in web.xml the relative path is now: /rest/ping/*

 

It has one method that is called on a HTTP GET request and it produces plain text. Normally you would produce JSON but thats something I will keep for part two. Just a hint in the return you can add any object in the entity call instead of a static string that gets transformed to JSON automatically!

 

Thats it you created your first REST service.

Unable to run SAP HANA Cloud Connector on windows 8.1

$
0
0

Hi Experts,

 

I am trying to run SAP HANA Cloud Connector on Windows 8.1 machine , i could see the go.bat command response as below:

 

          gobat.PNG

But when i run https://localhost:8443 URL in a browser, i don't see any response. Just a blank screen.

 

By looking at the logs:

 

#ERROR#com.sap.scc.jni#Start Level Event Dispatcher#  #Cannot load the Cloud Connector native library. (exception java.lang.UnsatisfiedLinkError: no sapscc20jni in java.library.path)

 

 

As per this reference https://help.hana.ondemand.com/help/frameset.htm?204aaad4270245f3baa0c57c8ab1dd60.htmlInstallation on Microsoft Windows OS it doesn't talk anything about support of HCC on Windows 8.1, just wondering if above error is because of it.

 

For more details, PFA log files.

 

Regards,

JK

XS to another Hana System

$
0
0

Hello everyone!

 

I have xs-application and 2 HANA systems, for example, hana1 and hana2.

XS-application based on hana1, but I want also use data from hana2.

Is it possible?

I was trying to call xsjs from hana2, but it was unsuccessful.

 

Thanks!

Jersey based REST with EJB and JPA

$
0
0

Hi,

 

has anyone managed to bring those pieces together?

 

What I have running are some REST based Services with Jersey 1.18 but no EJB Injection seems to work.

 

@Path("/user")

public class UserService {

  @EJB
  PDBInterface pdbBean;

  @POST
  @Produces("application/json")
  @Consumes("application/json")
  @Path("/json")
  public Response modifyJson(JsonBean input) {
    if (pdbBean != null) {
      input.setVal2(pdbBean.getUser("11"));
    }
    else {
      input.setVal2("pdb not injected");
    }
    return Response.ok().entity(input).build();
  }
}

This service I can call but the Bean "pdbBean" is always null, so nothing gets injected.

 

I also tried to use the EJB directly as Rest Service class:

@Stateless
@LocalBean
@Path("/ejb")
public class PDBInterface {

  @PersistenceContext
  EntityManager em;

  @GET
  @Path("/echo")
  @Produces("text/plain")
  public String getUser(String userId) {
    if (em != null) {
      return "em here";
    }
    else {
      return "em not here";
   }
  }
}

Again no em is injected...

 

Anyone managed to get something like this running?

 

Frank


SAPUI5 app on HANA CP with external json source

$
0
0

Hello.

 

Being a newbie, apologies if the question is naive.

 

I have been working locally on my laptop building a simple SAPUI5 app (simple master/detail app with a json feed coming from an external url).

 

The external url that provides the JSON feed is done through a php script. I can control because it is served from a site I own. I have been able to resolve the cross domain issues and locally (on my laptop) can run the app successfully without needing to be in - disabe security - mode.

 

I invoke the json feed in my app as below:

 

// Using a local model for offline development

  var oModel = new sap.ui.model.json.JSONModel("http://link.to.my domain/script.php");

  oView.setModel(oModel);

 

Using this php script, again locally it all works. However when I push it to the SAPHCP, it no longer works.

 

I have tried to replace the json feed with a local file, and that works OK.

 

Is there something I need to do to be able t consume that external feed?

 

Any information is greatly appreciated.

Thanks

Connectivity for SAP HANA XS (Trial)

$
0
0

Hi Guys,

 

I state that are very newbie on SAP HANA.

I'm using SAP HANA Trial and trying to connect from SAP HANA to googe maps as described on tutorial "https://help.hana.ondemand.com/help/frameset.htm?a238abbe7bb141f1a66143da94697b95.html" but I'm not able to launch the application. When I indicate the full path into the browser "https://s6hanaxs.hanatrial.ondemand.com/pxxxxxxxtrial/myinst/hello2/connectivity/google_test.xsjs"  I receive the message

"User is not authorized to use destination (package: connectivity.mapinfo, name: google)".

 

Can someone help me Please

 

Within the application I've create the subpackage "connectivity" that contains two files:


file: google.xshttpdest

host = "maps.googleapis.com";

port = 80;

pathPrefix = "/maps/api/distancematrix/json";

useProxy = true;

proxyHost = "proxy-trial";

proxyPort = 8080;

authType = none;

useSSL = false;

timeout = 30000;

 

File: google_test.xsjs:

var destination_package = "connectivity.mapinfo";

var destination_name = "google";

try {

  var dest = $.net.http.readDestination(destination_package, destination_name);

  var client = new $.net.http.Client();

  var req = new $.web.WebRequest($.net.http.GET, "?origins=Frankfurt&destinations=Cologne&mode=driving&language=en-US&sensor=false");

  client.request(req, dest);

  var response = client.getResponse();

  $.response.contentType = "application/json";

  $.response.setBody(response.body.asString());

  $.response.status = $.net.http.OK;

  }

catch (e) {

  $.response.contentType = "text/plain";

  $.response.setBody(e.message);

  }

How to install/configure Hana cockpit in Cloud Platform

$
0
0

Hi,

 

I'm new to HANA Mobile developments.

 

Through the SAP guides, i have learnt some basics of HANA mobile development and implemented few sample apps too.

 

Now, I just want to try the same in our own Landscape which is Cloud Platform.

 

But we dont have a clue, how to configure HANA cockpit?

 

In all sap samples we have used HANA cockpit to create instance and manage SAPUI5 apps etc. So it seems HANA cockpit is mandatory for mobile developments. But not sure.

 

Is Cockpit is Mandatory for Mobile developments ?

If not mandatory, how to create instances, create apps and view app url etc... ?

 

If its mandatory, then how to install or configure HANA cockpit in our Cloud Landscape ?

 

 

Thanks in Advance.

 

Regards

Yokesvaran Kumarasamy

JAX-RS the missing link between UI5 and HCP Java apps - adding EJB

$
0
0

This is part 2 of this blog and it assumes you have read Part 1.

 

In part 1 of this blog we have achieved a basic "ping" service that responds to a get request with just some static answer - "pong".

 

Normally you want to access a database and do some nice stuff. The best way to achieve a nice service layer is (in my opinion) to use EJB. You can control access rights, transactions etc. right by annotating your EJB in a nice and simple way. And you get your EntityManager or Datasource for JPA or JDBC directly injected without so much "boiler plate" code. So I want to show how to incopreate EJB in our setup. So the task I want to solve is adding an EJB with an entity manager injected and returning the result as a JSON object.

 

So first turn your project to a JPA project by adding this project facet in Eclipse.

 

Then we need a simple EJB:

/**

* EJB

*/

package com.sap.myapp;

 

import javax.ejb.LocalBean;

import javax.ejb.Stateless;

import javax.persistence.EntityManager;

import javax.persistence.PersistenceContext;

 

/**

* Simple EJB

*/

@LocalBean

@Stateless

public class MyEJB {

 

  @PersistenceContext EntityManager em;

 

  public MyJSONResult doSomething() {

    MyJSONResult result = new MyJSONResult();

    result.setState(em != null ? "em is injected :-)" : " em not inject :-(");

    return result;

  }

}

It does nothing else as to give me the state of the injected entity manager. For the sake of completeness I have to add the MyJSONResult class, which is just a simple POJO:

/**

* JSON bean

*/

package com.sap.myapp;

 

/**

* Simple Bean as result of EJB call

*/

public class MyJSONResult {

  private String state;

 

  /**

   * @return the state

   */

  public String getState() {

    return state;

  }

 

  /**

   * @param state the state to set

   */

  public void setState(String state) {

    this.state = state;

  }

}

If we would have the Java Web Profile level 7 not 6 on HCP this would be very easy (and I could not write this blog) all you would have to do is add your EJB to your new service. So my service would look like:

 

/**

* REST

*/

package com.sap.myapp;

 

import javax.ejb.EJB;

import javax.servlet.ServletException;

import javax.ws.rs.GET;

import javax.ws.rs.Path;

import javax.ws.rs.Produces;

import javax.ws.rs.core.MediaType;

import javax.ws.rs.core.Response;

 

/**

* Simple REST Service

*/

@Path("/service")

public class MyService {

 

  @EJB MyEJB myEjb;

 

  @GET

  @Path("/")

  @Produces(MediaType.APPLICATION_JSON)

  public Response myService() throws ServletException {

    return Response.ok().entity(myEjb.doSomething()).build();

  }

}

 

This would result in a Nullpointer Exception as the EJB is not injected. So there is some more magic needed as long as we stay with Jave Web Profile 6. We have to do a JNDI lookup of the bean before we can use it. By doing JNDI we get a fully working container managed EJB and we have to do that in every service method that wants to use EJB.

 

So the extended service will look like the following:

/**

* REST

*/

package com.sap.myapp;

 

import javax.ejb.EJB;

import javax.naming.InitialContext;

import javax.naming.NamingException;

import javax.servlet.ServletException;

import javax.ws.rs.GET;

import javax.ws.rs.Path;

import javax.ws.rs.Produces;

import javax.ws.rs.core.MediaType;

import javax.ws.rs.core.Response;

 

/**

* Simple REST Service

*/

@Path("/service")

public class MyService {

 

  @EJB MyEJB myEjb;

 

  @GET

  @Path("/")

  @Produces(MediaType.APPLICATION_JSON)

  public Response ping() throws ServletException {

    lookupEJBs();

 

    return Response.ok().entity(myEjb.doSomething()).build();

  }

 

  private void lookupEJBs() throws ServletException {

    if (myEjb == null) {

      try {

        InitialContext ic = new InitialContext();

        myEjb = (MyEJB) ic.lookup("java:comp/env/ejb/MyEJB");

      }

      catch (NamingException e) {

        throw new ServletException(e);

      }

      catch (Exception e) {

        throw new ServletException(e);

      }

    }

  }

}

For the JNDI lookup to work you have to add your EJB to the web.xml:

  <ejb-local-ref>

    <ejb-ref-name>ejb/MyEJB</ejb-ref-name>

    <local>com.sap.myapp.MyEJB</local>

  </ejb-local-ref>

So you tried it all out and your ping-pong service works but your new service gives a 404? Then you forgot to add your new service class to "MyApplication" as we did with the PingService in Part 1

 

Thats it, if you call now your application with the relative path "/rest/service" you get a JSON response.

 

{"state":"em is injected :-)"}

 

Explore the power of Jersey, even stuff as file upload can be done with a few simple annotations. If someone is interested in that I may add a third part to this small blog series

Reading data from C4C

$
0
0

Hi all,

 

I am trying to get the list of accounts associated with particular sales person from c4c CRM. I am trying to sort it out using odata web service API's. The standard APIs bring back huge list of account(all of them) . I want to filter the result based on ownerId,but that property is not filter enabled. Can anybody suggest solution to my problem. Is it possible for us to enable filtering properties or is there any other way out?

 

Thanks,

Surya

Viewing all 3285 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>