Get Started with Meridian
From the Meridian Editor to Beacons hardware, there are many things to keep track of while you get your Meridian-powered app up off the ground. This article describes all of the steps you'll need to get started with Meridian.
Meridian subscriptions come in different types: trials, demos, proofs of concept (POC), and paid.
If you don't know what type of subscription you have, please contact your sales representative.
If you're reading this article, you already have an account in the Meridian Editor.
Once you have a Meridian Editor account, you have access to everything you'll need to start deploying Beacons hardware, adding placemarks and routing to your maps, and preparing for the release of your Meridian-powered apps.
If you have a Meridian Editor account, you can create accounts for other users for your location.
Before you can use Meridian's location services, you'll need at least one for your location in the Meridian Editor. To do this, send us a map image file for each map you want in your Meridian-powered app. The Meridian Maps team will convert your map file into a format that works well in both the Meridian Editor and your Meridian-powered app.
Please send your map as a high resolution PNG, PDF, or JPEG image file to email@example.com.
Only one map is granted for each Proof of Concept (POC) or Not for Resale (NFR) kit. If you need to order more map conversions (SKU = PS-MER-MAP), please contact your HPE/Aruba sales manager.
Placemarks are points of interest on your map that your visitors might like to find.
Routing describes the legal pathways your visitors can take through you location. Once our Maps team has uploaded a map the Editor for you, you can begin adding routing lines to your map.
Aruba Beacons send Bluetooth signals with a unique identifier. They don't connect to Wi-Fi networks.
The Meridian Editor and Meridian-powered apps use the Beacon Bluetooth signals to enable location and friend finding, directions, and push notifications.
Beacons have a maximum range of 25 meters (80 feet) in an unobstructed area.
Battery-powered Beacons (BT-100) can be placed throughout a venue. Beacon batteries have at least 1 year of life.
USB Beacons are plugged into Aruba access points (APs) to enable them to monitor battery-powered Beacons. Along with an Aruba controller, this enables the Meridian Editor's Beacons Management feature.
USB Beacons can be deployed as either location or proximity.
Aruba Sensors are Beacons that can function as either location or proximity. Not only that, the Aruba Sensor can monitor battery-powered Beacons in range and report that data to the Meridian Editor, using a location's Wi-Fi internet connection.
The Aruba Beacons App
The Aruba Beacons app is the only way to deploy Beacon hardware. At the moment, it is only available as an iOS app. It is usable on iPhones, iPads, and iPod Touches.
The Meridian Editor's Beacons Management provides greater control over the Beacons deployed to your location.
With Beacons Management you can review your deployed Beacons, track Beacon battery levels, and edit Beacon values.
Remote Beacons Management is supported on both Aruba and non-Aruba wireless local area networks (WLAN). If you're using a non-Aruba WLAN, you'll need Aruba Sensors to enable Beacons Management.
If you're using Aruba hardware to manage your WLAN, a controller is a key piece of that. The controller is crucial for Beacons Management, because it reports the Beacon status it receives from a location's access points (APs).
The controller also stages Beacon changesets to be pushed out to APs.
Beacons Management requires 7xxx controllers.
Access Point (AP)
The AP 215 and AP 225 running Aruba OS 126.96.36.199 don't natively support Beacons Management. However, when a USB Beacon is plugged into an AP, it enables that AP to monitor Beacons and report that Beacon status to its controller.
When an AP receives a Beacon changeset from a controller, it pushes that changeset down to the appropriate Beacon and then reports that it has been done.
Upcoming AP hardware will support Beacon monitoring natively.
The Aruba Sensor functions as an AP that can monitor Beacons and, using a Wi-Fi network, report Beacon status to the Meridian Editor.
The Sensor can function in place of a controller and APs for the purposes of Beacons Management.
Meridian-powered iOS and Android apps are what your visitors will use to navigate around your location, find placemarks of interest, be notified of events or location-specific information, and provide other features relevant to your location.
There are two kinds of Meridian-powered apps.
White-label apps are standard, out-of-the-box apps that can be customized to match your location's branding and colors.
Alternatively, you can use the Meridian SDK to add the Meridian features to your own app. Using the Meridian SDK, you have complete control over how the final iOS and Android Meridian-powered apps turn out.
To learn more about the Meridian SDK, please go to the Meridian SDK Introduction.