Cisco Jasper Control Center is a cloud-based IoT services platform that enables you to view and control connectivity services for your IoT deployment, making it possible to quickly and efficiently launch, manage and monetize your IoT offering.
Reekoh has added 2 new plugins to its growing collection in the Plugin Store — the Jasper Events Gateway and Device Sync Plugins. The Jasper Events Gateway Plugin allows you to make use of Jasper’s Push API to send events to Reekoh for processing or integration. Jasper Events can be sent to a ticketing software, CRM or any other notification services (SMS, Mobile Push, Email etc.) for further processing and action. On the other hand, the Jasper Device Sync enables you to incorporate Control Center features and functionality into your Reekoh applications. This enables you to view and control connectivity service information along with other device information from within these applications.
Let’s go through the guide below to see how these plugins work.
First, we need to sync your Jasper Devices to Reekoh. To do this, install and configure the Jasper Device Sync plugin in your Reekoh instance. You may refer to our Plugin and Device Sync documents for more info.
Once configured, the Device Sync will run on the schedule you’ve set upon configuration. For example, if you’ve set the schedule to 10 minutes, it will sync devices from Jasper to Reekoh every 10 minutes. If you want to manually sync devices to Reekoh, navigate to Devices > Sync > All Device Syncs and then click the SYNC button of your Jasper device sync.
After your devices are synced, navigate to Pipeline Studio and then key-in the desired name for your pipeline. Locate the Gateways category on the right pane, and then drag & drop the Jasper plugin to the blank workspace.
To configure, double-click the plugin and then complete the wizard that follows. Click Save.
After you’ve configured your plugin, click Save & Deploy to run your pipeline.
Once your pipeline is set, you need to define an automation rule in the Jasper Control Center to determine the action to trigger when a certain event occurs. To do this, log in to your Jasper account and then navigate to Home > Automation Engine > Create New. Complete the wizard that comes next.
Based on the rule you’ve set, Jasper will send a Push API to Reekoh via the Jasper Gateway plugin for processing or integration. You may refer to the Push API/Rule Matrix for the list of different rules and Push APIs. Below is a sample data inside a Push API message.
{
"eventId":"SESSION_START-123",
"eventType":"SESSION_START",
"timestamp":"2010-01-07T01:20:55.685Z",
"signature":"8DYYAlzX5TbzChTK/qpMWdi8flA=",
"device":"8901311242888845458",
"data":{
"iccid":"8901311242888845458",
"ipAddress":"12.34.56.78",
"dateSessionStarted":"2010-01-07T01:20:55.200Z",
"dateSessionEnded":"2010-01-07T01:20:55.200Z"
}
}
The data to be sent will depend on the schema of each Push API. To see the schema for each API, navigate to Home > API Integration > XML Schema. Select your API from the list to view the corresponding schema.
For more info on how to customise your Reekoh pipeline, you can check out our Starter Guides in the Reekoh Help Center.