Cisco IT has already started reaping the benefits of Application Centric Infrastructure (ACI) from our early internal deployments. Cost savings rank high, in decreased operating expenditures through automation enabled by ACI and the sharp reduction of manual processes that introduce human errors and operational risk. Read More »
It’s All About The Applications. But Do You Speak Developer? Do Your Developers Speak Infrastructure?
Infrastructure matters. It’s the foundation on which everything else in IT is built. The purpose of data center infrastructure is to run applications, yet the relationship between infrastructure admins and application developers is often dismal.
Are you an infrastructure admin? When’s the last time Read More »
The faster internal applications can be developed and deployed, the sooner they will deliver benefits for the business. That’s an easy statement to understand, but not so easy to bring to reality. Read More »
One of the great challenges of SDN – that many in my view underplay – is the change in paradigm from having a vendor deliver your network (hardware + software), to having (potentially) an ecosystem deliver your network – and this ecosystem may require you to develop software to perform network tasks or to integrate various SDN components together. This was recognized quite astutely by consultant Jim Metzler, which I discussed in one of my earlier blogs. “Applications can dynamically request services from the network” is what the SDN evangelists will tell you. Jim astutely asked “How exactly do they do that?”. Well ….. the true answer is that either (i) you need to buy [new] apps that do this off the shelf, as it were, or [more likely today] (ii) you need to modify your apps or develop new apps to do this.
So are you ready for procuring apps and/or developing software in your network design team now? Don’t worry if you say “no”. Let me first tell you a few customer reactions to this topic, and then let me update you on Cisco Services can help you develop new SDN apps that solve your specific network challenges.
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 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: API, App, app developer, application, application developer, application development, code, Development, engineer, location, location based services, map, mobility, mobility services, mobility services engine, MS API, mse, network, REST, SOAP/XML, technical, technology, wifi, wireless