Cloud-Connectors

A common use case occurs when available hardware is already connected to a 3rd party API and you wish to connect them to your Murano Application (Eg. ExoSense or ExoHome).

For that purpose, Murano supports a standard Cloud-To-Cloud integration. This integration is compatible with Murano applications provided as IoT-Connector templates. Those Cloud-Connectors can be managed and connected to Application the same ways as Standard IoT-Connectors.

Table of Contents


Existing Cloud-Connectors

On Exchange IoT-Marketplace under IoT-Connector you will find the IoT-Connector Templates section.

This section contains various connectivity templates including popular 3rd party APIs like AWS IoT or Sigfox. Those templates are already customized to provide is zero-development integration experience.

The element details will inform you about the required configuration steps unique for each integration.

Select your template and click Create IoT-Connector.

Notable Integration

Sigfox
AWS-IoT
RadioBridge
ElectricImp
Ewon
MachineQ
OpenWeatherMap

Configuration

Follow the steps documented on the IoT-Connector exchange element details page. It usually requires to setup your 3rd party API access credentials by navigating to your IoT-Connector page under the Services -> <3rd party api name>.

Data transformation

Your hardware model might have some unique data structure not compatible with ExoSense data model.

For this purpose, Cloud-To-Cloud templates provided a set of customizable scripting modules allowing you to apply the data transformation to & from the 3rd Party API.

You can directly update those modules' logic through Murano scripting Editor under your Cloud-Connector Modules->vendor.c2c.transform. While not mandatory, you probably want to have a look at the Murano Scripting reference to give you more context on the scripting.

Note: The vendor name-space is 'safe' and will not be updated if the Cloud-Connector is updated to a newer version of the template. However any modification made outside of the vendor name-space will be lost.


Create Your Own

If you cannot find your 3rd party API listed on the Exchange Marketplace, you might need to do the integration using Murano scripting & integration capabilities.

Thankfully you can re-use the same base template, used by all standard Cloud-Connectors, to make your integration easier and ensure compatibility with Murano applications.

The Cloud-Connector base template is a public Github repository published by Exosite. You will find all the necessary information there.

A highlight of the required steps:

  1. Define the remote API using OpenAPI v2 swagger and publish it as a Murano-Service on the Exchange Marketplace
  2. Fork & customize the Cloud-Connector base template to fit your integration need
  3. Publish your new template to Exchange
  4. If you want to share your integration make both the service and the template Public

You will also need to make yourself familiar with