This article discusses how you would integrate a device into your own platform via the OEM Server. Please contact your local DM branch and get the integration protocol documents if you do not have them already.

OEM Server acts as a 'router' of the device data. To do this it uses a data 'Connector'. The data connector can be set for each device. 

Note that the connector for a device is loaded when it connects in to OEM - so if you change a connector for a device then it will only be reloaded when the device next connects. Consider using the "Disconnect Device" button on the device details page.

There are generally two types of connector that OEM offers. Other custom connectors have been developed in special circumstances. 

1. TCP Connector

Our recommended connector type is the TCP protocol connector, that will forward the 'raw' TCP data messages from the device to your server.

This is the best way to access all of the features and data fields in the device protocol. The protocol documents describe the various messages and data fields that are sent.

2. HTTP JSON Connector

We also support a "HTTP JSON" connector. This connector will forward data records in a JSON format, via a HTTP connection.

We do not recommend this for high volumes of data, so it is more suitable for devices such as the Remora and the Flexi1, or devices that are setup to connect to the server occasionally.


In order for us to setup a connector for you we will need a server host name or IP address, and the port that you want to use.

Upload Server on the Device

Do not change the upload server setting in Admin parameters or by texting the device, unless you want the device to bypass OEM Server and connect directly to your server.

This should only be done if you do not require any of OEM Server's functionality.