Browse Prior Art Database

Integration development with the Internet of things

IP.com Disclosure Number: IPCOM000239027D
Publication Date: 2014-Oct-02
Document File: 2 page(s) / 38K

Publishing Venue

The IP.com Prior Art Database

Abstract

This article describes the methods for enabling ESB / IoT development environments to integrate with API management repositories to enable connected device interfaces to be seamlessly imported into the development palette for use in integrations.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 54% of the total text.

Page 01 of 2

Integration development with the Internet of things

The Internet of Things (IoT) is bringing together multiple platforms, products and protocols. And one of the challenges of the Internet of Things is to make it as easy as possible to allow developers to make things.

    However, applications such as integration products and more traditional ESB solutions fall short of enabling devices to automatically integrate with the development environments to make it much easier to allow developers to make things.

    This article describes how devices connecting to a developer's network can publish a description of their interfaces / APIs to enable automatic integration into development palettes of integration applications / ESBs.

    The method herein uses API management solutions to enable IoT / ESB development environments to automatically create dynamic nodes associated with devices connecting to the network.

1. When a new device connects to a developer's network it locates an API management repository (this can be achieved in a number of ways initiated by the device or API management repository).
2a. If the device is enabled as such it can publish details of its API.
2b. An alternative embodiment can request device details on network connection (make, model #, etc.) and look-up in interface details in a database.

3. When the API repository is modified (or at predefined intervals) the ESB will query the API management repository.

4. As new devices are added new nodes will be created and added to the development palette in the form of a standard node template with options relating the different ways of integrating with the device.
4a. There are different node templates dependant on the transport as defined for communication (i.e. HTTP, SOAP, REST, JMS, MQ etc.)

5. The developer is now able to use the device node in integr...