Skip to Content

IoT Message Processing - Message Forwarding (HTTP)


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, 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

but there is nothing for

Thank you!

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Jul 10, 2017 at 06:59 AM

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

    Add comment
    10|10000 characters needed characters exceeded

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