Cisco Blogs


Cisco Blog > Mobility

Deep Dive: Mobility Services APIs (with Sample Code!)

Last week, my colleague Rajiv walked you through an overview of how our Mobility Services API now supports REST based APIs. As a developer for the Mobility Services Engine (MSE) team, I am very excited about this update because it means that it will be easier for developers to create apps using the MS-API, which hopefully means that more and more organizations will be able to take advantage of the location-based services and functionalities of the MSE. I’m going use this blog to walk you through some of the more technical aspects of the change.

The Basics

The REST API is now widely used in the field of API based web applications. The REST stands for REpresentational State Transfer. It is an architecture that is based on set of six rules, and APIs that support REST follow all those rules, making them RESTful.

Compared to SOAP, REST has better performance, scalability, simplicity, modifiability, visibility, portability, and reliability. For secured REST API transactions, HTTPS is recommended.

RESTful Mobility Services API

7.5 applications, including features from the Connected Mobile Experiences (CMX) solution such as Browser Engage and CMX Analytics, are now supporting REST APIs in addition to the existing SOAP APIs previous releases (backward compatibility).

CMX utilizes the basic authentication scheme to authenticate each REST API request. It utilizes the Authorization header in the HTTP packet. The Authorization header is composed as follows:

- Username and password are combined into a string “username:password”.
- The resulting string literal is then encoded using Base64.
- The authorization method, a space and the string “Basic” is then put before the encoded string.

The API credentials can be accessed from Prime Infrastructure (PI), which manages CMX (page is located under Mobility Services > Specific MSE > System > Users).

As Rajiv mentioned last week, the Mobility Services REST APIs can be grouped in the following way:

-          MAP APIs

-          Real time location APIs

-          Location history APIs

-          Notification APIs

Let’s break them down with use cases to get a better picture of when you’d use which. Read More »

Tags: , , , , , , , , , , , , , , , , , , , , , , ,

Get Your Network Ready For iOS7

September 13, 2013 at 5:30 pm PST

In their highly anticipated announcement this week, Apple introduced two new phones, the iPhone 5C and iPhone 5S, and confirmed that iOS 7 would be released on September 18th. Techies like myself took note that iOS 7 will include quite a number of new features. We at Cisco want to help you understand what iOS 7 means for your network, so here’s a quick blog to sum it up:

How does iOS 7 impact your wireless networks?

Soon your employees and guests will be upgrading to IOS 7. Did you know up to 20% of traffic to mobile devices is software upgrades, application updates and synchronizing your devices via the cloud? Cisco’s Application Visibility and Control technology can help you identify and tame these applications and is available on the routers, Wireless LAN and visible via Prime Infrastructure. In addition, Cisco’s ISR can cache these updates to reserve valuable and expensive WAN bandwidth. More details about protecting the WAN is available in another blog.

If you leverage a Captive Portal, you will experience a change in behavior. Apple has enhanced the Captive Network Assistant (CNA) functionality iOS 7 making it more robust. Cisco has proactively developed and tested a new version of wireless LAN controller code to interoperate with Apple’s new implementation while ensuring a seamless experience for all other clients.

Finally iOS 7 also has significant security and manageability enhancements to improve productivity for the enterprise.

What do you need to do in order to optimize for iOS 7? Read More »

Tags: , , , , , , , , , , , ,