How to use Alleantia IoT Connector with Boomi

Alleantia IoT Connector makes it easy to transform IoT data into new insights, revenue streams and digital innovations.

Introduction

Alleantia IoT Connector ensures a fast and easy connection between machines and applications, and it offers a complete monitoring and control system for industrial devices, single machines and sensors.

With the interoperability of the two software stacks, the customer can easily configure integration processes that bring raw data directly from the field (through Alleantia ISC software) to any business application, fully leveraging the capabilities of the Boomi platform and the ISC software.

You can personalize everything you want and select any available variable, custom alarms (they notify you, as soon as alert conditions are met, so you can act immediately) and events (when a condition occurs or the value of a variable has changed).

This solution has several advantages: it exploits the compute power of the gateway, which is often underutilized, it also reduces local network traffic, as well as making it extremely simple to build, deploy and govern complex integration patterns.

 

Free Connector trial

What you need to make Alleantia IoT Connector work:

In this way you can connect directly your industrial device (PLC, sensors or other available in the library) or use Alleantia's free simulators.

Alleantia - TPP - Build - Boomi AtomSphere - Google Chrome 2021-05-18 16-28-55

Configuration

Once your environment ISC and Atom are ready, go to Boomi Platform, select Alleantia IoT Connector from the Connect Catalogue and set up:

  • Alleantia IoT Connection : it contains the connection settings for the Alleantia ISC software (the host name and port) 
  • Alleantia IoT Operation : it defines what information about your devices you need to know
  • Alleantia IoT Parameters : you can use parameters to allow for dynamic configuration

Alleantia IoT Connector Connection

The Alleantia IoT Connector uses the following information to connect to Alleantia ISC Software:

  • Alleantia IP Address : the host for communication.
  • Port (80) : the port for communication (the default port is 80).

Alleantia IoT Connector Operation 

Actions

The Alleantia IoT Operation defines how to interact with the Alleantia ISC in the connection.

Certain operations require you to fill out additional fields necessary to complete the action.

  • Alleantia_System_Information:

Use this operation to return Alleantia system information.

  • All_Devices_Information:

Use this operation to return a data list to retrieve information on all devices configured in the IoT Server.

  • Single_Device_Information:

Use this operation to return the configuration information for device configured in the system.

  • All_Custom_Variables_Information:

Use this operation to return a list with the information on variables configuration of the plant configured in the IoT.

  • All_Variables_ Information:

Use this operation to return a list with the information on variables configuration of a device configured in the IoT Server.

  • Single_Variable_Information:

Use this operation to return the information on a variable configuration for a device configured on the IoT Server

  • All_Alarms_Information:

Use this operation to return the information on all alarms configured on the IoT Server.

  • Single_Alarm_Information:

Use this operation to return the information on an alarm configured on the IoT Server.

  • All_Events_Information:

Use this operation to return information relative to events that can be generated by the system.

  • Single_Event_Information:

Return information relative to the single event that can be generated by the system.

  • Get_Full_Telemetry:

Use this operation to return data lists to retrieve information on all devices configured in the IoT Server

  • Get_Single_Device_Telemetry:

Use this operation to return a list of actual values for the variables of a device configured in the IoT Server.

  • Get_Single_Variable_Telemetry:

Use this operation to return the actual variable value for a device configured in the IoT Server.

  • Get_Single_Custom_Variable_Telemetry:

Use this operation to return the actual variable value for the plant configured in the IoT Server.

  • Get_Custom_Variable_Historical_Telemetry_Data

Use this operation to return the historical values of a plant variable configured in the system for a specified time interval.

  • Get_Variable_Historical_Telemetry_Data

Use this operation to return the historical values of a variable of a device configured in the IoT Server for a specified time interval.

  • Get_Full_Active_Alarms:

Use this operation to return a list of active alarms in the IoT Server.

  • Get_Alarms_History:

Use this operation to return the historical list of the alarms in the IoT Server sorted by ascending time.

  • Get_Full_Active_Events:

Use this operation to return a list of active events in the IoT Server.

  • Get_Events_History:

Use this operation to return the historical events in the IoT Server for a specified time interval.

  • Get_Single_Event_History:

Use this operation to return a single historical event in the IoT Server for a specified time interval.

  • Set _Variable_Value:

Use this operation to set the value of a writable variable for a device configured in the IoT Server

Operation Tab

Options Tab

Configuration options enable you to define your Connector action.

Import

The Import Wizard helps you quickly configure an operation and automatically generate the request and response JSON profile that can include all required custom fields.

To import the response and request profile for the each operation:

• Click on Import button
• select the available Atom and click next

• Select the Object Type to create the specified action/operation type for that object type.The request and response JSON profiles are created.
• Click Next and Finish.

• Verify that the object Type selected in the previous steps is generated in the Response profile field as shown below

Object

An object defines the action to execute.

Request Profile

The Request Profile selects the profile definition that represents the data structure that is being sent by the connector. 

it is useful when the selected action requires the setting of specific parameters (like device identifier, variable identifier etc..) and the customers prefers to do it in dynamic way (Parametric tab).

Response Profile

The Response Profile selects the profile definition that represents the data structure that is being received by the connector.

You use this profile when mapping to another format or whenever you need to reference a specific field in a process shape configuration.

Parameters

You can create multiple filters and add multiple parameters. They can be static or dynamic values.

If customer doesn’t want defining the parameters in dynamic way, he can use the field within Operation tab to define them in static way.