The open hybrid-cloud and big data are at the center of the IT transformation that will enable every business, country, and city to become a digital and technology organization. Cisco and Red Hat share a common vision for the future of IT. That’s why Cisco is going big at the Red Hat Summit, which kicks off June 23rd in Boston. It’s going to be a great week of conversations with IT professionals who are harnessing open source innovation across their businesses and organizations to deliver new models of IT.
I’m especially looking forward to the opening general session with Red Hat CEO, Jim Whitehurst and Satinder Sethi Cisco VP of Data Center and Cloud Solutions. I’m sure these two industry luminaries will have keen insights into the market transitions and IT innovations that put the data center at the heart of digital transformation.
Of course, the Cisco team will be busy with an action packed agenda of sessions and demos. Plan to make the Cisco booth your hub in the Red Hat Summit Partner Pavilion. Our mini-theater will feature non-stop tech talks that span OpenStack, Group Based Policy, Big Data and Developer Programs. Every visitor to the Cisco booth will leave with an ultra-cool Cisco hat.
Read More »
Tags: ACI, ACI and Open Stack, app developer, Big Data, Cisco Developer Network, Cisco UCS, OpenStack, red hat, Red Hat Enterprise Linux OpenStack Platfrom
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