Testing the B + MQTT Techedge Adapter for SAP PI

Try a new technology is always exciting, but when it comes to Internet of Things, it gets serious.

With investment in IoT up each year, and its many virtues, gradually it becomes an increasingly more attractive bet. In Techedge we have created an adapter (B + MQTT Adapter) that can integrate the IoT technology, with one of the most important and influential systems in the world, SAP.
To show the performance of the adapter, we have made a mockup with an ARM mbed IBM device, which we have placed in a small ambulance.

ARM mbed IoT Device

Toy ambulance

Assembled Solution

But before we start to work, let’s see a small outline of what we want to achieve …Our IoT device contains a simple MQTT client with the ability to post a message in MQTT a JSON message with data collected by the sensors available; accelerometer, two potentiometers, temperature and joystick. With a few lines you can specify the host and port where we hosted the Mosquitto Broker and the Topic on which we publish, “techedge/spain/madrid/iot/mockup/ambulance”.

To understand the structure of the Topic, you need to know that a topic in MQTT represents a hierarchy from general to specific. Thus, a client subscribed to our Broker, could access all hierarchy levels established in our Topic, through wildcards # and +.

• techedge/spain/madrid/iot/mockup/#.
• techedge/spain/+/iot/mockup/ambulance.

Once configured our device responsible for publishing the Broker, it is time to configure our client subscriber, we will use the MQTT adapter for SAP PI.As you can see in the picture above, we have chosen a simple configuration, in the Message Protocol field we are indicating that we will receive a JSON input, this suggests the adapter type of processing to be performed on the message, and offers additional options for working with JSON.

Then we specify connection parameters broker that we will use, and since it is a mockup, set a time of reconnection and Keep alive for 10 seconds.

That done, we set the Topic in the Subscribe tab, and set a Quality of Service of 2.As you can see, it is not necessary to configure any additional parameters for conversion to XML, since it is an automatic process, however, we must perform a mapping in the flow of PI, to adapt to the structure we need in our Proxy ABAP to communicate to SAP ECC. This mapping may map the received message to any interface and link with any functional SAP process.

After setting the channel, we can connect our device and check in SAP ECC that data has arrived, in our example, as a transaction. Within seconds we get the first 4 messages with the states of the sensors of our little ambulance.

And finally, here we can see the result, the UUID corresponds to a unique message identifier and the name identifies the device that sends the information.I hope you enjoyed as much as we, and you feel encouraged to do your own tests to see by yourselves the potential of this technology.

For further information about this adapter, you can check our documentation at the following URL:

[English] https://techedgespain.atlassian.net/wiki/display/IEN

[Spanish] https://techedgespain.atlassian.net/wiki/display/I/Integration+Tools