Step 4 – IoT application: Create Java application to integrate all these services and Python code to send the sensor data from the device .(check part 2.2 for details).

Since I will be covering the configuration in detail for the first scenario, I have decided to split Part 2 of the series into two. I will keep it brief for the next 2 scenarios as the steps are almost the same.

Steps 1 & 2 will be covered in this blog and Steps 3 & 4 in the next blog.

Make sure that the following services are enabled in SAP Cloud Platform Neo environment under your trial account.

Internet of Things

Business Rules

Workflow

Web IDE full stack

Step 1: Device Management

The device management steps shown below covers the configuration of all three scenarios of the prototype

THSensorData: This message type will be used to send temperature and humidity data from device to SCP.

LowStockSensorData: This message type will be used to send the material type of the material with low stock.

ThicknessSensorData: This message type will be used to get the thickness information from the device for scenario 3.

AdjustThicknessSensor: This message type will be used to send the corrected thickness data to the device.

Go to Device Management -> Device Types

Create one device type with all the above four message types. Three of the message types will be configured with direction ‘From Device’ and one with direction ‘To Device’.

Go to Device Management -> All Registered Devices

Register a device with the device type configured above. Note the device ID and the authentication token which the system generates during the device registration. These will be used in the Python script which runs in the device to send and receive sensor data.

Configure Processing Service Mappings

For all four message types, configure processing service mappings so that the messages received from the device are stored in our own set of tables instead of the auto generated T_IOT_<message type id> tables.

I got the url (first part) from the URL mentioned under connectivity services -> destination ->bpmrulesruntime . If you notice closely the term ‘rules’ appear twice once before the runtime and once after. I guess you can try with the same URL or check and confirm once in your destinations.