The OEM Server Connectors allow device data to be 'switched' to different end points. The end points are usually front end servers that aggregate the device data. The connectors can send data in raw form over TCP (as the devices send it) or convert it to JSON and send it over HTTP.
This connector model also allows for the "multi-connector". This allows multiple connectors to be assigned to the device. The OEM Server will send data to each of the end points. This allows platforms to compliment each other. For example, Telematics Guru may provide the mapping and fleet management, but a partner may want to add some value in a unique way by consuming the data themselves.
- The multi connector can specify 2 or more connectors.
- BOTH connectors must allow data to be successfully committed, otherwise the device upload will fail. The device will disconnect and retry. It will resend the same data until it gets a successful commit response. This implies that if one connector is broken, neither system will work.
- You can specify HTTP/JSON and TCP/Raw connectors in a multi-connector group.
- There is an additional charge per multi-connector. Contact your local sales channel to understand this.
How to setup a multi-connector:
- First, the individual connectors need to be setup:
- Provide DM support with the URL:port and format (raw/JSON) requirements. Support will create the connector.
- Test the connectors individually, to isolate any problems. Use the Device Details page, with the 'Server Logs' button and the 'Debug Terminal' feed to identify the issues.
- Ask DM support to create the Multi-Connector. Specify which connectors should be combined.
- Assign the multi-connector to devices.
Other interesting notes:
- It is often useful for the 2 end-points to share some common data. For example, "what is the name of the asset linked to serial 123456?". This has been done previously using the Telematics Guru Web API.