Hello experts,

I was wondering if it's possible to set up a real time data replication from, let's say, MSSQL Server 2012 database to HANA database in the cloud? The reason for this question is this: I have a trial developer's account on HCP and want to play around with data modelling in HANA, see how it works, learn etc. And I want to set up a real time data replication from my MSSQL sandbox database to HCP to have a real data and simulate the scenario when a customer has a transactional system based on non-SAP database but he wants a reporting to be done on HANA.

Best regards,

Vlad

Hi Experts,

I am following HCP IoT getting started videos series(https://www.youtube.com/watch?v=k0gyLHt7ioE&list=PLkzo92owKnVxzjoxwJdaa400E_UqkzE8J&index=9)  and I am currently on OData session where in I am not able to create a new package under my trial user. Earlier it was there(iotmmsxs, I deleted it by mistake)

Could you please help me how to create new package and proceed further? PFA the attachment with the error detail.

Thanks in advance,

Aman

Hello Experts,

could you please recommend the best way to implement communication between Java and XSJS applications hosted on HCP?

Java is our middleware which obtains data from SAP thru Cloud Connector and exposes manipulated data by REST services. Our XSJS application needs to receive set of data from Java and perform some PAL functions. Then results needs to go back to the Java app.

Our 1st approach was to expose a REST operation in XSJS and consume it by the Java app, but we have huge problems with oAuth2 - it seems to be not really a standard oAuth on the HCP side as none of Java libraries which we use is able to receive and use the token.

What is your recommended way of communicating those two applications?

thanks in advance!

Hello i have subscribed the new HTML5 subscription with below details.

Provider Account : sapmobile

application : hcpmsadmin.

It got subscribed but this not visible in subscription page. I could not able to add admin role.

Any one know why this not visible in subscription page?.

Regards,

Dhamodharan

Hi all,

our company has purchased "HANA Cloud Database Services" but I cannot access it no matter what I try. All we got from SAP was an email with an SAP ID User and the url https://account.hana.ondemand.com/cockpit , no password or anything. Using trial and error I've figured out that I can use the email of my boss to login to the cloud platform cockpit, but this is as far as I can get. I see one database system and one database. Clicking on Hana cockpit gets me a login page. When I use the SAP ID User, I get the message "

You are not authorized to open the SAP HANA Cockpit.

You're also not authorized to assign yourself the necessary role."

and that's the end. Clicking on Database user gets me "

You have already changed your initial password.

and nothing else. Clicking on Web IDE gets me the web IDE which I don't want to use for development. When I try to add the HCP Hana to my Studio, I'm not able to give it correct credentials, or at least it does not accept those that the web IDE accepts. I haven't found any docs about what to fill in there, what should be in the "Landscape host" field? It suggests hanatrial.ondemand.com, I've tried also hana.ondemand.com (for Europe), which does not work, either, it only tells me that after 5 attempts I will be locked out.

Clicking on New Database opens a popup where I can only click Cancel, cannot fill in anything.

How am I supposed to use this product? I've been working with Hana on AWS since a couple of years but this HCP stuff seems quite demanding.

-- Micha

Hi there,

I'm playing a bit with ETL processes on my free Hana Cloud Developer Account. I have upserted 140.000 dummy records, about 100 MB.

There seems to be a limit there as the upserts stopped at such a round number. This happened about an hour ago.

Now the Consumed Resources tab in the Cloud Cockpit still shows just a handful of kilobytes as network traffic and DB Space (HANA).

What can I expect? When will the real usage show up?

Best regards,

NAI

Introduction

Although there is no standardized definition of the term "Principal Propagation", it is commonly understood as the ability of a system to securely forward or propagate the authenticated user (principal) from a sender to a receiver in a way that the forwarded user information is kept confidential and - even more important - cannot be changed during transit. Based on a pre-established trust relationship to the sender, the receiver uses this information to logon the user without asking her again for their credentials.

Principal propagation plays an important role in many scenarios on SAP HANA Cloud Platform (HCP), e.g. when an application has to pass the logged-on user in the Cloud to an on-premise system via the SAP HANA Cloud Connector. More information on this scenario can be found here. The following picture illustrates another very common scenario for principal propagation, where an application on HCP consists of two components: The user interface (UI) is developed and deployed as an HTML5- or Java-application on HCP which consumes an API implemented as a RESTful service from an SAP HANA instance running on HCP. The API requires an authenticated user and exposes the user's data via SAP HANA Extended Application Services (XS).

On HCP, the user usually authenticates against an identity provider (IdP) which is configured for the account where the application is deployed to. In HCP trial accounts for example, this is the SAP ID Service by default, which is a free-of-charge public identity provider from SAP, managing the SAP Community Network users, SAP Service Marketplace users and the users of several other SAP sites. To delegate user authentication to the IdP, HCP uses the SAML 2.0 protocol. Upon successful authentication at the IdP, the HTML5 application on HCP receives a SAML Response from the IdP, which is a message digitally signed by the IdP. It must contain at least the unique logon name of the user, and may also include additional information about the user, such as the user's first and last name, e-mail address etc.

HTML5 applications usually rely on on-premise or on-demand RESTful services. When a RESTful service is called from an HTML5 application, a new connection is initiated by the central HTML5 dispatcher on HCP to the service that is defined in a corresponding HTTP destination. If this call requires the user to authenticate at the service, the HTML5 dispatcher should rather propagate the authenticated user or login context than prompting the user again for credentials to access the service.

There are two authentication mechanism available for an HTTP destination to propagate the logged-in user to a RESTful service running on SAP HANA XS: SAP Assertion SSO or Application-to-Application SSO (AppToAppSSO). The first one uses SAP Assertion Tickets to transfer the logged-on user information, the latter uses a SAML Assertion. Compared to SAP Assertion SSO, AppToAppSSO has the following advantages:

Compared to the alternative of using SAP Assertion Tickets for propagating the user, AppToAppSSO has two advantages:

• The propagated user information can contain more information than just the user's login name. Additional user attributes are also forwarded with the SAML Assertion. SAP Assertion Tickets only forward the user's login name.
• SAP HANA XS can dynamically create a new DB user based on the forwarded information. This user is required to successfully log on the user on the SAP HANA instance. With SAP Assertion Tickets, this mechanism, sometimes referred to as "Just-in-time (user) provisioning", is not supported, and the users have to be created in advance. However, this is sometimes not possible, e.g. if there is a large number of users accessing the service.

In this blog you will go step-by-step through a scenario using AppToAppSSO. Common for both mechanism is that the recipient (XS) must trust the sender (HTML5 dispatcher) to accept the propagated principal. For AppToAppSSO, this trust relationship is setup in XS similar to other SAML-based IdPs. Therefore, the SAP HANA instance must be properly setup for SAML-based authentication as one of the following prerequisites.

Note: Although an HTML5 application is used to implement the UI, a Java-based application could have been used as well for the scenario. AppToAppSSO works for both application runtimes to propagate the authenticated user to SAP HANA XS.

Prerequisites

The scenario in this blog is using an SAP HANA Multitenant Database Container (MDC) on the HCP trial landscape. Before getting started, please check that your meet the following prerequisites:

• You have an HCP trial account, which can be created at no charge from here.
• You have created a MDC in your trial account. Please followEkaterina Mitova's instructions in this blog to create one.
• You have setup the SAML Service Provider in the MDC. Please follow the sections Creating Your Service Provider Certificate and Complete the Service Provider Settings in the blog “Play It Again, SAML” from Oliver Goetz.
• You have installed Eclipse with the SAP HANA Cloud Platform Tools and SAP HANA Tools following the instructions on the SAP HANA Tools site
• You have installed OpenSSLwhich will be used in first step to generate the signing key pair and certificate for your HTML5 SAML Service Provider

Step 1: Configuring the Local Service Provider for HTML5 apps

AppToAppSSO uses a SAML Assertion as the security token format to propagate the logged-on user. Therefore, your HCP (trial) account must be setup with a custom SAML Service Provider key pair which is used to digitally sign the SAML Assertion. Based on this signature, XS will verify that the user information has been propagated from a trustworthy system, i.e. your HTML5 application, or even more precisely, your account's subscription to the central HTML5 dispatcher. Login to the Cloud Cockpit on the HCP trial landscape and open the Trust settings of your account. Click on the Edit button and switch the Configuration Type from "Default" to "Custom".

If you have never done this before, you will see empty text fields for the Signing Key and Signing Certificate. Those need to be filled in this step as they identify your HTML5 application to the service running on XS. Unfortunately, you cannot use the "Generate Key Pair" button in this scenario, as XS will not be able to import the certificate. This bug will be fixed in HANA in one of the next revisions. For now, you have to create the key pair using a tool like OpenSSL by issuing the following command:

openssl req -x509 -nodes -days 365 -sha256 -subj "/CN=https:\/\/hanatrial.ondemand.com\/<your account name>" -newkey rsa:2048 -keyout spkey.pem -out spcert.pem

Please replace "<your account name>" in the command with your trial account name, e.g. "p<some number>trial". As a result, two files are generated: spkey.pem and spcert.pem. You need to convert the private key file spkey.pem into the unencrypted PKCS#8 format before pasting it into the text field using the following command:

openssl pkcs8 -nocrypt -topk8 -inform PEM -outform PEM -in spkey.pem -out spkey.pk8

Now open the files spkey.pk8 and spcert.pem in a text editor and strip off the tags "-----BEGIN PRIVATE KEY-----", "-----END PRIVATE KEY-----", "-----BEGIN CERTIFICATE-----" and "-----END CERTIFICATE-----". Copy the remaining content from spkey.pk8 in the text field with the label Signing Key, and spcert.pem into Signing Certificate. After clicking on Save you should get a message that you can proceed with the configuring of your trusted identity provider settings, and see a Local Service Provider configuration like shown in the following screenshot:

Click on the Get Metadata link to export the Local Service Provider configuration in a standardized metadata format, which will be use in the next step to import the trust settings in XS.

With the Configuration Type "Custom" you are now able to configure your own trusted identity providers, e.g. a corporate IdP. For the scenario in this blog you will continue to use SAP ID Service as our IdP to authenticate the users. Therefore you have to switch back to Configuration Type "Default" by clicking on the Edit button and reverting Configuration Type "Custom" back to "Default". Click on Save.

Note: By switching back to "Default", your "Custom" settings are not lost, and will be used for signing the SAML Assertion sent by the HTTP destination using AppToAppSSO principal propagation.

Step 2: Setup Trust in XS to the HTML5 Local Service Provider

Open the SAML Identity Provider list of your trial MDC with the XS Admin tool using your account-specific URL https://<mdcname><account name>.hanatrial.ondemand.com/sap/hana/xs/admin, and login with the SYSTEM user. If the SYSTEM has not yet the required roles to access the XS Admin tool, add all roles in SAP HANA Studio containing "xs.admin" in the name as shown in the following screenshot:

On the SAML Identity Provider list, click on Add ("+") to create a new trust relationship to your HCP account's Local Service Provider which has been configured in the previous step. In the Metadata field, copy and paste the content of the SAML Metadata file you exported from the Cloud Cockpit using the Get Metadata link.

When you click on Save, the fields in the form will be updated based on the values from the metadata file. The only fields left blank are "SingleSignOn URL (RedirectBinding)" and "SingleSignOn URL (PostBinding)", because you've actually imported a metadata file of a service provider, and not of an identity provider. Therefore add some dummy values, e.g. "/saml2/sso". Also make sure that the checkbox "Dynamic User Creation" is activated. This ensures that for new users a corresponding HANA user is created. Click on Save again to store your settings.

With HANA SPS10, certificates are managed differently, and you need to issue a few SQL commands to store the Local Service Provider's certificate in HANA. First, verify that the destination for the new IdP was stored in HANA by checking in SAP HANA Studio the _SYS_XS.HTTP_DESTINATIONS table using the command

SELECT*FROM _SYS_XS.HTTP_DESTINATIONS

You should see the destination in the result list:

Next, store the certificate from file spcert.pem including the "-----BEGIN..." and "-----END..." tags with the following SQL command:

CREATE CERTIFICATE FROM'-----BEGIN CERTIFICATE-----

MIIDiDCCAnCgAwIBAgIJAM3+kppT633nMA0GCSqGSIb3DQEBCwUAMDYxNDAyBgNV

BAMTK2h0dHBzOi8vaGFuYXRyaWFsLm9uZGVtYW5kLmNvbS9kMDQ0NzI0dHJpYWww

...

hj65U8pdxfugQlhrnewfMrAYf6uqpe0Fbbz6e3Ig2o6lHdLRyLaZiffoVEc=

-----END CERTIFICATE-----';

Verify that the certificate has been successfully store using the following SQL command:

SELECT*FROM SYS.CERTIFICATES

The new certificate is shown at the end of the list:

Finally you need to add the new IdP certificate to the PSE container for SAML which has been created during the SAML configuration of your XS following the blog “Play It Again, SAML” (see steps Create a PSE Container and Assign the PSE Store For SAML Use). To add the certificate, issue the SQL command

ALTER PSE <your PSE name> ADD CERTIFICATE <your certificate id>

Note: You have to replace the PSE name and certificate id with your values, e.g. "SAMLTRUST" and 155581 (taken the generated certificate id from the screenshot above as an example).

This concludes the trust setup in HANA XS to your HTML5 application as a trustworthy system to propagate the authenticated user. Next you will configure the destination of your HTML5 application.

Step 3: Configure HTTP Destination for AppToAppSSO

The sample HTML5 application used in this blog is a project management application, which retrieves a user's project data from an REST service running on XS. The complete code of the HTML5 application can be downloaded from here and can imported in SAP WebIDE on HCP.

As a user, you login to the application via the IdP, and then see a list of projects where you are assigned to. Therefore the logged-on user must be propagated securely to XS which will use the propagated user id to query the database for the projects where the user is assigned to as the project lead. In addition, the user's attributes such as first- and last name are used to set the user's name in the list of projects returned from XS to HTML5.

The actual invocation of the service in XS is done in Project.controller.js of the HTML5 application:

In the JSON model, the data is loaded from the URL /api/projects, which is mapped in the HTML5 application's neo-app.json descriptor file to the HTTP destination with name "xsprojectdata" :

Let's have a look at the destination configuration in the Cloud Cockpit. The two most important settings are highlighted in the following screenshot:

• The Authentication method is set to AppToAppSSO
• An additional property with the name "saml2_audience" and the value "I1700" is set for the destination

The property sets an important value in the SAML Assertion which is used to propagate the user. This value, the SAML audience,

"contain[s] the unique identifier URI from a SAML name identifier that describes a system entity" and "evaluates to Valid if and only if the SAML relying party is a member of one or more of the audiences specified." (Assertions and Protocols for the OASIS Security Assertion Markup Language (SAML) V2.0, page 23)

In other words: XS would reject the SAML Assertion with the propagated user if the audience is not set correctly to its own SAML name identifier. By default, an HTTP destination configured for AppToAppSSO sets the audience to the name of the SAML local service provider (aka "relying party") configured in the Cloud Cockpit. For a trial account, this would be "https://hanatrial.ondemand.com/<your account name>" if you haven't changed it. However, your MDC container is configured to a different SAML service provider name. Mine got the name identifier "I1700" which can be looked up in the XS Admin Tool under "SAML Service Provider":

Last but not least, configure the URL of the destination according to your service location. You can download the XS code from here. I've deployed the service in a package sample.xproject in the HANA repository, so the resulting URL is https://<MDC_name><account_name>.hanatrial.ondemand.com/sample/xproject/xproject.xsjs.

Note: Please change the file data/projects.csv before you active it, and replace the two placeholders <your user id> in the file with your SAP ID Service user ID. This file will import some sample data into the PROJECT table which is used later for testing the scenario.

Step 5: Configure the default role of dynamically created users in XS Service

The xproject.xsjs file implements the XS service to retrieve the propagated user's projects from the database. The function getProject() retrieves the user's unique logon name and queries the database for projects where the user set as the project lead. The result is returned in JSON format. The PROJECT table can only be accessed by users with the role "projectmember" which is defined by the file projectmember.hdbrole. Therefore, new HANA DB users created dynamically according to the new IdP's setting should automatically be assigned to this role. To set this default role, you first need to create a run-time role by opening the Security folder of your system in the "Systems" view in SAP HANA Studio. There do a right-click on the Roles element and select New Role from the context menu. For the Role Name, enter a value such as "DEFAULT_ROLE_FOR_PROJECT_MEMBERS", and click on the "+" in tab Granted Roles to add your design-time role "sample.xproject::projectmember" to it. Press Ctrl+S to save you new run-time role.

Next, double-click on your system in SAP HANA Studio to open the Administration. Select the Configuration tab and filter for "saml". Right-click on the saml section in the search results and select Add Parameter from the context menu. The Add Parameter Wizard opens. Leave the default selection ("Database") for the scope and click Next. For the key name, enter "defaultrole", and for the value the name of the newly created run-time role ("DEFAULT_ROLE_FOR_PROJECT_MEMBERS"). Click Finish to save the new parameter.

Step 6: Configure SAML for the XS Service

Before you can test the scenario, the XS Service must also be protected with SAML. In the XS Admin Tool, select "XS Artifact Administration" from the menu. Go to package "sample.xproject" and click on Edit. In the Security & Authentication tab, activate SAML and select newly created IdP in the dropdown box, starting with "HTTPS__HANATRIAL_...". Deactivate any other authentication methods and click on Save.

Step 7: Testing the Scenario

Now it is time to test the scenario: Go back to Cloud Cockpit and open the Overview page of your xproject HTML5 application. Right-click on the Application URL and open the application in a new private/incognito browser window to obtain a new session.

You will see the landing page of the xproject application. Click on Login.

Based on your trial account's trust settings, you will be redirected to SAP ID Service as the default IdP. Upon successful logon with your SAP ID Service credentials, your browser is redirected back to the application. The project overview page retrieves its data from the XS service, which uses the AppToAppSSO destination to propagate your user. Based on the configuration settings from the previous steps, only the projects for the currently logged-in user are retrieved by getting the username from the XS session object with

var username = $.session.getUsername();

in line 20 of the xproject.xsjs file, and appending it to the SQL statement which queries the application's PROJECT table. In addition, the federated user attributes for first- and last name of the logged-in user are used to return the display name of the user. Those are accessed in XS under the same name as in HTML5 or Java. For SAP ID Service, they are accessed using firstname and lastname using the following API:

var displayName = $.session.samlUserInfo.firstname+" "+ $.session.samlUserInfo.lastname;

Depending on your table data and user name, the list may look like this in the web browser, only showing two out of three projects in total:

This step concludes the scenario and I hope this is of help if you are implementing a similar scenario on SAP HANA Cloud Platform.

Whenever I try to run my XS unit tests throughout the web browser I get error 404 that the page is not found, and when I try throughout the Web based Development Workbench to "Invoke tests" I get " Error when calling XS Unit. Check that you have installed HANA_TEST_TOOLS."

I was not able to login to the Lifecycle Management to do that with my credentials, nor was I able to download hana test tools package from the site where  Support Packages and Patches are. Since I like my code to be test-driven-developed and currently have only trail development account, is there a way to run my tests?

Hi,

   I'm trying to configure a destination in HCP cockpit using the following 6 fields using OAuth2 authentication :

url

client_id

client_secret

grant_type = 'client_credentials'

scopes

token url

However, I'm not sure where do I provide the client_id, grant_type,scope and what exactly needs to be filled in the 'audience' field. Could you please assist.

Thanks.

Hello !

I am just trying to do my first steps towards FIORI development. What I did so far is:

1. Get the HANA Trial accunt, and install the WEB IDE.
   This works fine, at least for the "Hello World" example.
2. Create an Account on ES4. This also works fine, as long as I try to Access it
   via WebGUI.

My next plan was to retrieve Data from ES4 and to use it in my next FIORI Application.

For this, I tried the following example:

http://scn.sap.com/community/developer-center/front-end/blog/2015/07/27/creating-and-deploying-sap-fiori-app--dc-exercise-part-1-of-3

And this is where I get stuck ... as in the example, I tried to create a new Destination:

However, when I try to Access it, I get the follwing message:

I am wondering what to do now ... I think it is a certificate Problem, since I have not installed the JDK. My understanding ist that the JDK Installation makes no sense for me, since I use the WEB IDE for development.

Does anyone know how to cope with this Situation ? Any help is appreciated !

Regards & thank you in advance,

Martin

Hi,

We are using the concept of multi-tenant in Hana Cloud Platform and the current challenge we are facing is scaling up and reducing the configuration time for the consumer accounts. Every consumer account needs to be configured to HCP, Fiori Landscape and Cloud Identity. We are looking at automating most of the steps in configuring the above mentioned services. But unfortunately could not find much except for create-account and subscribe account.

Is there any way we could set up the services and manage the accounts in a better way rather than manually performing steps in cockpit.

Thank you

Regards

Vidhya

Hello Experts,

I tried testing authorization management REST APIs through POSTMAN client as i have a requirement to get the roles assigned to a user in a webide code so that i can control the user access in a custom widget. I referred the documentation : https://help.hana.ondemand.com/help/frameset.htm?392af9d162694d6595499f1549978aa6.html and i want to test the API provided in documentation https://api.hana.ondemand.com/authorization/v1/documentation . As the API /accounts/{accountName}/users/roles which i want to access  is oAuth2.0  protected , i created a client with trial/portal subscription in my hana trial cockpit account and was able to get the oauthtoken using https://oauthasservices-<myTrailaccount>.hanatrial.ondemand.com/oauth2/api/v1/token?grant_type=client_credentials POST service. I am still not able to figure out how can i test roles api . I beleive i will have to create an http destination of type OAuth2SAMLBearerAssertion to access this api in my webide application. Could you please tell me what should i put for url, audience and token service url parameters while creating destination ?

Just to add , i am able to test the service with POSTMAN client now but i need to access this using webide application where i am getting error with getting token.

To test in Postman , i used frst the url

https://api.hanatrial.ondemand.com/oauth2/apitoken/v1?grant_type=client_credentials&scope=hcp.readAuthorizationSettings%20hcp.manageAuthorizationSettings

and passed the client key and client id which i generated from oAuth section of HCP, Platform API's tab .

i got the token which i passed to

https://api.hanatrial.ondemand.com/authorization/v1/accounts/<myTrailAccount>/users/roles/?userId=<myUserID>

so i got the response with user and Roles . I have  attached the screenshot of destination created, please guide me if i have missed any property in destination and how can i use it in a webide application.

Thanks ,

Rakesh

Hi,

I am trying to implement a people(user) search within an HCP Java Service. So essentially, I want to lookup user information such as first name, last name and email for a given user ID (not my own user, but others).

I tried using code like this:

  InitialContext ctx; 

ctx = new InitialContext(); 

  UserProvider userProvider = null; 

  userProvider = (UserProvider) ctx.lookup("java:comp/env/user/Provider"); 

  User user = userProvider.getUser(userId);

This works fine for my own user which is logged in, but other users are not found this way.

Is there any way one can implement a user lookup ? Is this even provided from a security perspective ?

Thanks,

Best regards,

Stefan

Hi Experts,

            I am trying to create calculation view in SAP Hana Web-based Development Workbench through HANA XS(Shared) Database System,but while i'm trying to add tables into projection node i cannot able to find tables its showing no result found. And also i cannot able to find default schema in search option. Please find below error screenshot..

Note: I'm using upgraded Hana Cloud Platform trial version

Regards,

Karthic S

Dear Colleagues,

I am using CMIS services for accessing a HCP document repository using JAVA. I would like to know, if there is a way in which I can change the capabilities of the repository? Example, I would like to change the Query Capabilities from "MetadataOnly" to "BothCombined". Is this supported? if yes, how is this possible programatically? There are no setters for these. There is only one getRepositoyCapabilities().

If a Client cannot change this capability, is this a restriction from HCP Document Service, that it supports only "metadataonly" as query capability?

Regards

Saif

What do you need to send data with an iOS device to the IoT Services?

• You have enabled the SAP HANA Cloud Platform, IoT Services (see: Try out the SAP HANA Cloud Platform Internet of Things (IoT) services).
• You own an Apple iPhone or Apple iPad (> iOS 9.x) to send data.

Optional:

• You own a Texas Instruments Sensor Tag Bluetooth Smart (CC2650).
• You own a ublox Sensor (OLP 425).

How to Send Data with the IoT Sensor App by itelligence AG?

Create a device model via IoT Services Cockpit

1. Open the Internet of Things services Cockpit.
2. Choose the Device Types tile.
3. Create a new Device Type by clicking ( + ).
4. Enter a name, e.g.: "iOSDevice", "TI CC2650" or "OLP 425" (depending on your available hardware).
5. Copy the displayed Device Type ID and Device Registration Token to your Clipboard.
   
6. Go back to the Internet of Things services Cockpit.
7. Choose the Message Types tile.
8. Create a new Message Type by clicking ( + ).
9. Enter a name, e.g. "iOS Data".
10. Select the Device Type that was previously created (here: "iOS Device").
11. Change the Data Type for timestamp to long.
    
12. Enter the following fields depending on the device you are targeting (all fields are optional):
    • iOS Device: timestamp (long) / accX (double) / accY (double) / accZ (double) / altitude (double) / locLat (double) / locLong (double) / pressure (double)
    • TI Sensor Tag: timestamp (long) / accX (double) / accY (double) / accZ (double) / rotX (double) / rotY (double) / locking (double) / pressure (double)
    • ublox OLP: timestamp (long) / sensorTemp (double) / sensorGyroX (double) / sensorGyroY (double) / sensorGyroZ (double)
13. Copy the displayed Message Type IDto your Clipboard.

You can now start sending data with a client using the created Device Type and Message Type.

Download and configure IoT Sensor App

1. Install on your mobile device: IoTSensor on the App Store (iOS only)
2. Configure the app with by calling the following custom URL on your device:
   • iot-create://&/accountName&/[Account ID]&/name&/[Connection Name]&/dataCenter&/[Data Center]&/deviceName&/[Device Name]&/deviceTypeID&/[Device Type ID]&/deviceReg&/[Device Registration Token]&/messageTypeID&/[Message Type ID]
   • Parameters:
     • [Account ID] => your account ID, e.g., "p1234567trail"
     • [Data Center] => your account data center, e.g., "hanatrial" / "hana" / "hana.us1" / "hana.us2" / "hana.ap1"
     • [Connection Name] => any name for a connection, e.g., "myConnection"
     • [Device Name] => any name for the device, e.g., "iPhone Michael" / "Sensor Tag 1"
     • [Device Type ID] => the Device Type ID you copied previously to your clipboard
     • [Device Registration Token] => the Device Registration Token you copied previously to your clipboard
     • [Message Type ID] => the Message Type ID you copied previously to your clipboard
   • Sample: iot-create://&/accountName&/p000000trial&/name&/myTrialConnection&/dataCenter&/hanatrial&/deviceName&/iPhoneMichael&/deviceTypeID&/f807b43597e44cf1fc4b&/deviceReg&/ce89c5cfe7fdb25b381eff51136b97&/messageTypeID&/9208dd4b8cc54bc1fb1b
3. Once the custom URL is launched the app starts and account will be configured.
4. Press on Register.
   
5. The "Device" gets registered and is ready to send Data. Press OK.
   
6. The "Connection" is now coloured red.
   

Select Device and Send Data

1. Press on Sensor.
   
2. Select a device (vor BLE device connection press refresh).
   
3. The device is not connect. Go back by pressing Select Source.
4. Press Back. (Sensor and Connection are coloured red.)
5. Press Record Button.
   
6. Data is sent according to sending interval (values that are not defined in the message type are ignored.)
   

How to write you own iOS App?

• The SAP IoT Starter Kit includes an iOS Sample how to write your own client: iot-starterkit/src/hardware/iOS at master · SAP/iot-starterkit · GitHub

Additional Material?

• Try out the SAP HANA Cloud Platform Internet of Things (IoT) services
• SAP IoT Starter Kit (code snippets how to use the SAP HANA Cloud Platform, IoT Services)
• SAP HANA Cloud Platform Internet of Things (IoT) Services (official documentation)

Questions and Feedback?

We highly appreciate your questions or feedback. Please add your comments below.

Hello All,

I am trying to connect HANA Cloud Connector to the on-premise ECC system. It keeps giving me error on Internal host cannot be reached. I am not sure if I am putting the right Host address and port. I found the host name using the FM /SDF/GET_ICM_Virtual_host_data.Can somebody tell me how to find the actual address and port # of the backend system if this not the correct way of doing it/
.

Thanks

Umang

Hi,

I have a problem regarding this OpenSAP course: https://open.sap.com/courses/hanacloud3-1/items/6XUMTXiXKcrGWmSptapuwz

I tried to deploy the example application from eclipse and it started up in the cockpit but when I try to go to the Link the answer from the server is 404 not found. I attached a Screenshot from the cockpit.

Do you know where my problem could be?

Are there any additional Information you need?

Thank you very much in advance!

Hi everyone,

I am trying to import csv files via SQL, and it doesn't work even though I am following the instructions on IMPORT FROM - SAP HANA SQL and System Views Reference - SAP Library

The steps I am following are:

I create a table mytable to store the imported data.

CREATE TABLE mytable ( A INT, B VARCHAR(10));

I create a CSV text file /data/data.csv and add the following contents.

1,"DATA1"
2,"DATA2"
3,"DATA3" 
4,"DATA4"

I then execute the following command to import the data.

IMPORT FROM CSV FILE 'C:/Users/cnumber/Desktop/TEST1.csv' INTO "MYTABLE" WITH RECORD DELIMITED BY '\n' FIELD DELIMITED BY ',';

Everything is done perfectly:

Statement 'CREATE TABLE mytable ( A INT, B VARCHAR(10))'

successfully executed in 160 ms 534 µs  (server processing time: 86 ms 711 µs) - Rows Affected: 0

But this is the error i get:

Could not execute 'IMPORT FROM CSV FILE 'C:Users/cnumber/Desktop/TEST1.csv' INTO "MYTABLE" WITH RECORD DELIMITED BY ...'

SAP DBTech JDBC: [258]: insufficient privilege: Not authorized

Any suggestions?

Best,

Christoforos