HTTP/HTTPS-based Communications

Iotellect provides a versatile suite of tools for integrating with external systems and devices using standard HTTP and HTTPS protocols. These tools leverage different aspects of HTTP communication to provide rich functionality. The following table gives a brief overview of how each tool can be used.

HTTP/HTTPS Device Driver

HTTP Server

REST/HTTP API

SOAP Device Driver

SOAP Web Service

Purpose

Monitor web servers and interact with HTTP resources

Expose Iotellect functionality via custom HTTP endpoints

Provide programmatic access to Iotellect context via RESTful interface

Interact with external SOAP web services

Expose Iotellect functionality as a SOAP web service

Architecture

Client-server; Driver sends requests, receives responses

Server-client; Server listens for and handles requests

Client-server; Clients send RESTful requests, receive JSON responses

Client-server; Driver acts as both client (to external services) and server (exposing its own operations)

Server-client; Server listens for SOAP requests and responds accordingly

Protocol

HTTP/HTTPS

HTTP/HTTPS

HTTP/HTTPS

SOAP over HTTP/HTTPS

SOAP over HTTP/HTTPS

Mode

Client

Server

Server

Both Client and Server

Server

Use Cases

  • Monitoring website availability

  • Retrieving data from web APIs

  • Controlling devices with HTTP interfaces

  • Hosting custom web applications built using Iotellect

  • Building integrations with modern systems leveraging REST APIs

  • Automating Iotellect tasks from external scripts or applications

  • Integrating with legacy systems using SOAP

  • Accessing external data and functionality exposed via SOAP web services

  • Integrating with enterprise systems (ERPs, CRMs)

  • Allowing external applications to manage Iotellect server and devices

Was this page helpful?