IoT Message Processing - Message Forwarding (HTTP)

[Former Member]

Hi,

I would like to configure a HTTP handler to process the IoT Message sent from the device. I maintained the configuration as per the documentation here but I am not receiving any requests to my http endpoint. . Can you please help me with some guidance on how to troubleshoot this issue.

Here are few things I verified:

- My end point is an HCP url and I am able to successfully make POST requests to it.

- My message mode is synchronous "sync"

- Checked MMS logs for error, didn't see any errors.

- Turned on traces for component com.sap.iotservices.mms.processing, I don't see any attempt made by MMS to invoke my endpoint.

- Verified through Message Processing API if my handler is active, and I see the correct endpoint in the response.

Figure 1: Message Processing API showing the "http" processor is active for the device/message combination.

Figure 2: Request/Response of the Message request showing device-id, message-id and response.

On a separate note, why is that the logger has a separate component defined for each processing type like

com.sap.iotservices.mms.processing.sql

com.sap.iotservices.mms.processing.sds

but there is nothing for com.sap.iotservices.mms.processing.http?

Thank you!

[Former Member]

I restarted the MMS service and now I see an ERROR message in the log saying "Could not retrieve the service mappings from the data base".

But I see the service mapping active.

[anton_levin · Accepted solution]

Hello Ram, you have configured your mapping but used the device ID where device type ID was expected. Please, adapt. Regards, Anton

[Former Member · Accepted solution]

Thank you very much Anton, that solved the problem.

[Former Member · Accepted solution]

I was thinking why was there no validation on the device type when I created the service mapping? But then it came to me, the design decision at the core of IoT services is to keep services lean so that they can be scaled to millions of devices at a time.