Forward IoT data to smart data streaming

[#1]

hello - i'm setting up a scenario as below.

1. sensor sends data to iot services on HCP

2. configured service to forward sensor data to smart data streaming on cal.sap.com

3. Registered service from cal.sap.com to HCP - as mentioned in http://help-legacy.sap.com/saphelp_hana_options_sds_adapt/helpdata/en/68/df4e6a1cbd43f1890ce58e012f4...

4. Created project/workspace/etc and they are working fine

Issue - the sensor data doesn't seem flow to smart data streaming service.. not much useful info in the log file. Any suggestions.

Secondly - where do i see the data forwarded from iot service in cal (i configured HANA studio, but there is no data. i'm using SYSYEM schema) - any suggestion on which table holds the data.

thanks for your help

pandari

[JWootton]

I would suggest first making sure that you can connect to your SDS server via the SDS streaming web service (SWS). You say that you have deployed this from CAL, so I'm assuming that what you have deployed is the HANA 1.0 SPS12 Developer Edition in either AWS or Azure. I would suggest using this tutorial to ensure that you are able to publish to an SDS project via SWS:

https://www.sap.com/developer/tutorials/sds-rest-publish.html

- Be sure that SWS is running on your SDS cluster

- Use Postman or some other tool to try to connect to it. If successful, then see if you can configure MMS to publish to it.

But now a word of caution: we have never tried publishing from MMS to an SDS instance that's running outside of SAP Cloud Platform. I don't know if you will run into e.g. firewall issues, etc.

[Former Member]

yes, i deployed SDS on HANA developer edition on azure. i'm able to compile the project, webservice is enabled, http://13.81.0.52:9093/1/version - failed. i hv attached screen shots and trace file. please let me know if you have any other thoughts.

azure.jpg

get-service.jpg

trc-file-from-hana-admin.txt

trc-file-from-hana-admin.txt

[RobertWaywell]

The error you are getting strongly suggests that the SWS is not running. Have you worked through the 1st tutorial that Jeff mentioned which includes steps on configuring the SWS?

https://blogs.sap.com/2016/04/13/using-the-streaming-web-service-sp11/

[Former Member]

Hi Robert/Jeff,

My SWS is running, i also validated by invoking the url - /1/version, and 1/authorization. The issue i'm seeing now is HCP is throwing the authorization error below. I'm not sure, why HCP trial is using anonymous login.

This one when i used wss

2017 06 07 04:52:32#+00#ERROR#com.sap.iotservices.mms.processing.sds.connection.StreamingWebServiceWssConnection##anonymous#IoT MMS pool thread-25#na#p296796trial#iotmms#web#pXXXtrial#No websocket connection available.|

This error when i used https

2017 06 07 04:53:08#+00#ERROR#com.sap.iotservices.mms.processing.sds.connection.StreamingWebServiceHttpsConnection##anonymous#IoT MMS pool thread-25#na#p296796trial#iotmms#web#pXXXtrial#SWS Token could not be retrieved. Response Code: 405|

Service registration - tried it with both wss and https. (first i tried with wss, then deleted the registration, then re-registered with https)

https://iotmmsXXXXXXtrial.hanatrial.ondemand.com/com.sap.iotservices.mms/v1/api/http/processing

{ "deviceType":"3041ca0ef3a86a9c736e", "messageType":"e1b0068faba1203f6661", "processingServices":[ { "name":"sds", "properties":{ "mms.processing.sds.protocol":"wss", "mms.processing.sds.host":"52.174.242.241", "mms.processing.sds.port":30026, "mms.processing.sds.user":"SYSTEM", "mms.processing.sds.pwd":"XXXX", "mms.processing.sds.workspace":"default", "mms.processing.sds.project":"zstreamproj", "mms.processing.sds.input_stream":"ziotstream", "mms.processing.sds.proxy_enabled":"false" } } ] }

I also checked the HCP trial java application of iotmms, message forward configuration, i have entered the userid/password to the CAL streaming project.

Any thoughts?

Thanks

Pandari

[Former Member]

Hey Pandari,

as far as you leave the "trial" landscape of SAP Cloud Platform with your forward request, it could be possible to enter proxy settings in the SDS processing service.

Could you please try to set the mms.processing.sds.proxy_enabled to "true" and use the following settings:

Host: proxy-trial

Port: 8080

Kind regards,

Ralf

[Former Member]

still not working...pl see below error from default trace file in hanatrial.ondemand.com for iotmms application. pretty close to giving up 😞

2017 06 07 21:45:39#+00#ERROR#com.sap.iotservices.mms.auth.BasicAuthFilter##anonymous#http-nio-8041-exec-9#na#p296796trial#iotmms#web#p29XXXtrial#Unable to loginjavax.security.auth.login.CredentialNotFoundException: No user identifier is provided. at com.sap.security.auth.module.basic.PasswordLoginModule.handleUserName(PasswordLoginModule.java:320) at com.sap.security.auth.module.basic.PasswordLoginModule.login(PasswordLoginModule.java:105) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at javax.security.auth.login.LoginContext.invoke(LoginContext.java:755) at javax.security.auth.login.LoginContext.access$000(LoginContext.java:195) at javax.security.auth.login.LoginContext$4.run(LoginContext.java:682) at javax.security.auth.login.LoginContext$4.run(LoginContext.java:680) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680) at javax.security.auth.login.LoginContext.login(LoginContext.java:587) at com.sap.core.jpaas.security.auth.service.internal.LoginContext.login(LoginContext.java:101) at com.sap.iotservices.mms.auth.BasicAuthFilter.login(BasicAuthFilter.java:102) at com.sap.iotservices.mms.auth.BasicAuthFilter.doFilter(BasicAuthFilter.java:57) at com.sap.iotservices.mms.auth.BasicOAuthFilter.doFilter(BasicOAuthFilter.java:84) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:218) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:110) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:615) at com.sap.core.jpaas.security.auth.service.lib.AbstractAuthenticator.invoke(AbstractAuthenticator.java:170) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:169) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:962) at com.sap.core.tenant.valve.TenantValidationValve.invokeNextValve(TenantValidationValve.java:168) at com.sap.core.tenant.valve.TenantValidationValve.invoke(TenantValidationValve.java:94) at com.sap.js.statistics.tomcat.valve.RequestTracingValve.invoke(RequestTracingValve.java:45) at com.sap.core.js.monitoring.tomcat.valve.RequestTracingValve.invoke(RequestTracingValve.java:27) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:445) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1115) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:637) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1770) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1729) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:805)