WE CLAIM
1. A method of implementing a software application for an Internet of things (IoT) device, the method comprising:
defining, by an IoT implementation framework, a set of events and a set of actions for the IT implementation based on a process flow and configuration metadata;
creating, by the implementation framework, a set of custom actions, for the IT implementation, based on the set of events, the set of actions, and the configuration metadata; and
processing, by the implementation framework, a set of messages received from the IoT device based on the process flow, the set of custom actions, and a set of pre-built actions.

2. The method of claim 1, further comprising storing transaction metadata for each of a plurality of interfaces and for each of a plurality of IoT devices in an operational data store, wherein, for each of the plurality of IoT devices, the transaction metadata comprises at least one of a transaction ID, an application name, an application version, a device ID of the IoT device, an event ID, a location of the IoT device, an event name, an action name, a present state, a date, a time, a status code, a status message of the IoT device, a plurality of events for the IT implementation, or a plurality of actions for the IT implementation.

3. The method of claim 2, further comprising generating insights by analyzing the transaction metadata.

4. The method of claim 1, further comprising storing the configuration metadata for each of a plurality of IoT applications in a configuration database, wherein the configuration metadata comprises at least one of an application name, an application version, an interface name, an interface ID, a source protocol, a target protocol, an end point, a security scheme, a plurality of credentials, a process flow, an event name, an event ID, an action name, a debug level, a correlation flag, a persistency flag, or a priority.

5. The method of claim 1, further comprising creating a plurality of pre-built actions for a plurality of generic tasks to be employed across a plurality of interfaces in the IT implementation for the IoT device, wherein, upon completion of a corresponding generic task, each pre-built action is configured to create an event message based on the configuration metadata and to update transaction metadata.

6. The method of claim 1, wherein the plurality of custom action corresponds to specific business logic and requirement of the IT implementation, wherein, upon completion of a corresponding specific task, each custom action is configured to create an event message based on the configuration metadata and to update transaction metadata.

7. The method of claim 1, wherein each of the set of messages comprises at least one of a topic, a location of the IoT device, or an address of the IoT device.

8. The method of claim 1, wherein processing comprises processing the set of messages as per queue by calling appropriate pre-built actions from the set of pre-built actions and appropriate custom actions from the set of custom actions.

9. A system for implementing a software application for an Internet of things (IoT) device, the system comprising:
an IoT implementation framework comprising at least one processor and a computer-readable medium storing instructions that, when executed by the at least one processor, cause the at least one processor to perform operations comprising:
defining a set of events and a set of actions for the IT implementation based on a process flow and configuration metadata;
creating a set of custom actions, for the IT implementation, based on the set of events, the set of actions, and the configuration metadata; and
processing a set of messages received from the IoT device based on the process flow, the set of custom actions, and a set of pre-built actions.

10. The system of claim 9, wherein the operations further comprise storing transaction metadata for each of a plurality of interfaces and for each of a plurality of IoT devices in an operational data store, and wherein, for each of the plurality of IoT devices, the transaction metadata comprises at least one of a transaction ID, an application name, an application version, a device ID of the IoT device, an event ID, a location of the IoT device, an event name, an action name, a present state, a date, a time, a status code, a status message of the IoT device, a plurality of events for the IT implementation, or a plurality of actions for the IT implementation.

11. The system of claim 10, wherein the operations further comprise generating insights by analyzing the transaction metadata.

12. The system of claim 9, wherein the operations further comprise storing the configuration metadata for each of a plurality of IoT applications in a configuration database, and wherein the configuration metadata comprises at least one of an application name, an application version, an interface name, an interface ID, a source protocol, a target protocol, an end point, a security scheme, a plurality of credentials, a process flow, an event name, an event ID, an action name, a debug level, a correlation flag, a persistency flag, or a priority.

13. The system of claim 9, wherein the operations further comprise creating a plurality of pre-built actions for a plurality of generic tasks to be employed across a plurality of interfaces in the IT implementation for the IoT device, and wherein, upon completion of a corresponding generic task, each pre-built action is configured to create an event message based on the configuration metadata and to update transaction metadata.

14. The system of claim 9, wherein the plurality of custom action corresponds to specific business logic and requirement of the IT implementation, and wherein, upon completion of a corresponding specific task, each custom action is configured to create an event message based on the configuration metadata and to update transaction metadata.

15. The system of claim 9, wherein each of the set of messages comprises at least one of a topic, a location of the IoT device, or an address of the IoT device.

16. The system of claim 9, wherein processing comprises processing the set of messages as per queue by calling appropriate pre-built actions from the set of pre-built actions and appropriate custom actions from the set of custom actions.