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
Request clarification before answering.
hello Anton - I'm getting the error below. This is in the iotmms default trace file.
2017 05 22 21:23:47#+00#ERROR#com.sap.iotservices.mms.processing.sds.connection.StreamingWebServiceHttpsConnection##anonymous#Delayed request processing for device '6115856b-7fec-4b94-b930-09704ecff342'#na#pXXXtrial#iotmms#web##SWS Token could not be retrieved. Response Code: 405|
Additional info:
FILE_TYPE:DAAA96DE-B0FB-4c6e-AF7B-A445F5BF9BE2 FILE_ID:1495477078755 ENCODING:[UTF8|NWCJS:ASCII] RECORD_SEPARATOR:124 COLUMN_SEPARATOR:35 ESC_CHARACTER:92
HEADER_END 2017 05 22 18:18:07#+00#ERROR#com.sap.iotservices.mms.processing.ProcessingServiceRegistry##anonymous#localhost-startStop-1#na#p296796trial#iotmms#web##Could not retrieve the service mappings from the data base.java.io.IOException: Failed to find a corresponding processing service named 'sds' for device type '3041ca0ef3a86a9c736e' and message type 'e1b0068faba1203f6661'.
21:23:47#+00#ERROR#com.sap.iotservices.mms.processing.sds.connection.StreamingWebServiceHttpsConnection##anonymous#Delayed request processing for device '6115856b-7fec-4b94-b930-09704ecff342'#na#p296796trial#iotmms#web##SWS Token could not be retrieved. Response Code: 405|
Any thoughts on how to resolve this.
Thx
Pandari
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
further update. i deleted all the previous registrations and registered the smart data streaming service, with "wss" protocol, then i got the message below in "iotmms"
2017 05 22 22:06:10#+00#ERROR#com.sap.iotservices.mms.processing.sds.connection.StreamingWebServiceWssConnection##anonymous#IoT MMS pool thread-2#na#pXXXtrial#iotmms#web##No websocket connection available.|
Registed to iotmms using: https://iotmmspXXXXtrial.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.166.240.XXX", "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" } } ] }
Dear Pandari, I still see that your iotmms instance is not able to connect to the underlying DB. Please, as stated above in my comment from May, 20th - bring iotmms to the operating state first. If it is not feasible with MDC instance, then I would suggest to switch back to shared HANA schema. Without underlying DB it is not possible for iotmms to operate with its processing services, since all configurations are stored there. Regards, Anton
i reconfigured to use shared instance, now i'm getting the error below, which is similar to what i received before. Any other thoughts.
FILE_TYPE:DAAA96DE-B0FB-4c6e-AF7B-A445F5BF9BE2 FILE_ID:1495670532241 ENCODING:[UTF8|NWCJS:ASCII] RECORD_SEPARATOR:124 COLUMN_SEPARATOR:35 ESC_CHARACTER:92 COLUMNS:Time|TZone|Severity|Logger|ACH|User|Thread|Bundle name|JPSpace|JPAppliance|JPComponent|Tenant Alias|Text| SEVERITY_MAP:FINEST|Information|FINER|Information|FINE|Information|CONFIG|Information|DEBUG|Information|PATH|Information|INFO|Information|WARNING|Warning|ERROR|Error|SEVERE|Error|FATAL|Error HEADER_END 2017 05 25 00:31:35#+00#ERROR#com.sap.iotservices.mms.processing.sds.connection.StreamingWebServiceHttpsConnection##anonymous#Delayed request processing for device '6115856b-7fec-4b94-b930-09704ecff342'#na#pXXXXXtrial#iotmms#web##SWS Token could not be retrieved. Response Code: 405|
i restarted the iot services, and deleted the previous registration, and registered the service as wss and https, still it failed.
+00#ERROR#com.sap.iotservices.mms.processing.sds.connection.StreamingWebServiceWssConnection##anonymous#IoT MMS pool thread-3#na#p296796trial#iotmms#web##No websocket connection available.| 2017 05 25 00:51:46#+00#ERROR#com.sap.iotservices.mms.processing.sds.connection.StreamingWebServiceWssConnection##anonymous#IoT MMS pool thread-3#na#p296796trial#iotmms#web##No websocket connection available.| 2017 05 25 00:52:03#+00#ERROR#com.sap.iotservices.mms.processing.sds.connection.StreamingWebServiceWssConnection##anonymous#IoT MMS pool thread-3#na#p296796trial#iotmms#web##No websocket connection available.| 2017 05 25 00:52:14#+00#ERROR#com.sap.iotservices.mms.processing.sds.connection.StreamingWebServiceWssConnection##anonymous#IoT MMS pool thread-3#na#p296796trial#iotmms#web##No websocket connection available.|
Hello Pandari, now monitoring tool indicates that the iotmms operates normally, thanks. But in the logs I see the following: "Failed to find a corresponding processing service named 'sds' for device type '304***36e' and message type 'e1b***661'". May you please post here a screenshot of your "T_IOT_PROCESSING_SERVICE_CONFIG" table? IoT MMS Cockpit -> Application Data (tile, top-left corner) -> T_IOT_PROCESSING_SERVICE_CONFIG table. (Please, mask user sensitive info if required). Regards, Anton
Please see attached. iot-processing-service.jpg
| User | Count |
|---|---|
| 5 | |
| 5 | |
| 4 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.