Release Notes for the Cisco Enterprise Mobility Services Platform Release 2.2
This document describes the system requirements, new features, enhancements, and known issues for the Cisco Enterprise Mobility Services Platform (EMSP). Use this document in conjunction with the documents listed in the “Support” section.
The EMSP is a mobile-application platform that enables rapid delivery of context-aware mobile experiences to meet the business requirements and customer expectations. The platform includes a cloud-based application server that combines the Cisco network infrastructure capabilities with the enterprise and open-cloud systems.
The EMSP comprises several applications that you can install and subscribe to, such as WiFi Engage, EMSP App Builder, EMSP Studio, EMSP SDK, and EMSP API. These applications enable you to access the various features of the EMSP.
This section lists the hardware requirements, operating systems, software requirements, and browsers for the EMSP.
The user interface of the EMSP home page and the EMSP dashboard are changed. The following links are added to the EMSP home page that appears when you access https://emsp.cisco.com :
A new icon, Add MAC Address to Do Not Track List, is added to the EMSP dashboard. This option enables you to specify the MAC addresses of the mobile devices that are not to be tracked. The end users can inform you through an e-mail if their actions in a portal are not be tracked. You can enter the MAC address of the mobile of such users whose actions are not to be tracked.
The Micello Wayfinding module is updated to provide multi-building and multi-floor support. This is applicable only for Cisco Unified Wireless Network (CUWN). Even though this functionality was available in the earlier version, it was not functioning as expected.
To use this feature, you need to create the Micello Wayfinding feed with the appropriate map details. You can obtain the map details from the Micello. You can use the Feed Editor icon in the EMSP dashboard to create the feed for the Micello Wayfinding.
If the feed details match with the EMSP API configuration, then the map of the floor where the user is currently presently is shown. If there is a mismatch, the default map is shown.
The WiFi-MX is now branded as WiFi Engage and the WiFi Engage user interface is redesigned. All of the modules related to the WiFi Engage are accordingly renamed.
The WiFi Engage is now merged with the EMSP. When you click the Go to WiFi Engage icon in the EMSP dashboard, the WiFi Engage dashboard appears as a part of the EMSP. The new URL that appears for the WiFi Engage is emsp.cisco.com/wifiengage.The incoming requests to cisco.wifi-mx.com are redirected to emsp.cisco.com/wifiengage.
The Switch Account button label is removed. When you click the icon for Settings, the Settings window appears with a Connect Account button.You can switch your account using this button.
The Microsite option that was available in the earlier version of the WiFi Engage (WiFi-MX) is removed.
The WiFi Engage now supports the SMS gateway of third-party vendors. You can configure the customized SMS gateway in the Settings option.
The WiFi Engage now supports the following third-party wireless network providers: Motorola, Xirrus, and Ruckus. The entire WiFi Engage functionality is extended for these networks.
The WiFi Engage now lets you configure either a custom password or an auto-generated password for an SMS Gateway. Additional fields such as Default Country Code, SMS Gateway, and Password Type are added to the SMS verification option under the Authentication module to support this feature.
The EMSP Live Studio, EMSP Sandbox Studio, and WiFi Engage Studio installers are unified, and a single EMSP Studio installer is provided for all of the environments. You can download the unified EMSP Studio installer from the EMSP main window that appears when you log in to https://emsp.cisco.com. During the initial launch of the EMSP Studio, all of the environments are installed on your computer. A single client icon appears on your desktop for the Cisco EMSP Studio. When you click this icon, an environment window appears from which you can choose the required environment to which you need to log in. The EMSP Studio icon in the EMSP main window always redirects you to the Live environment. The following environments are available:
The Cisco EMPS Studio is enhanced to work without the Adobe Flash Player. You do not have to install the Adobe Flash Player now to launch the EMSP Studio.The prerequisites for the EMSP Studio installation are Java and Adobe Air plug-in.
The EMSP Live App Builder and EMSP Sandbox App Builder installers are unified and a single EMSP App Builder installer is provided for both the environments. You can download the unified EMSP App Builder installer from the EMSP main window that appears when you log in to https://emsp.cisco.com. During the initial launch of the EMSP App Builder, both these environments are installed on your computer. A single client icon appears on your desktop for the Cisco EMSP App Builder. When you click this icon, an environment window appears from which you can choose the required environment to which you need to log in. The EMSP App Builder icon in the EMSP main window always redirects you to the Live environment. The following environments are available:
The Cisco EMPS App Builder is enhanced to work without the Adobe Flash Player. You do not have to install the Adobe Flash Player now to launch the EMSP Add Builder. The prerequisites for the EMSP App Builder installation are Java and Adobe Air plug-in.
In the Get Invite window, two new fields are added to specify the company name and designation of the user. This Get Invite window is used to send an invite to the users to enable them to access their WiFi Engage account.
The WiFi Engage now lets the customer configure their own social apps.
A new option, Settings, is available in the WiFi Engage. Click the Accounts icon in the WiFi Engage dashboard to view the Settings option. This option enables you to configure the customer-specific social apps and SMS gateway.You can configure the following in the Settings window:
If you need to use any social sign-in feature in your portal that requires authentication, then you need to configure the respective social app in the Settings option. You can configure the apps of Facebook, Google, Twitter, and Linked In.
To integrate the app with a captive portal, in the Authentication module in Create> Portals, specify the required app.
The WiFi Engage is enhanced to show whether a radius server from the EMSP or a captive portal created using the EMSP Studio is configured for an SSID. If either of these, or both of these are configured for an SSID, then an Advanced Configuration With Meraki message appears against that SSID in the Actions column of the SSID window.
In addition, for the radius server configuration, the Radius Server Configuration message appears in the Remarks column. Similarly, for an EMSP Studio portal configuration, the details of the EMSP Studio Portal configuration appear in the Remarks column of the SSID. A green indicator is shown for each of these configurations.
If the Radius server or captive portal configured is not of the EMSP, the sync option appears in red.
You can revert the advanced configurations for an SSID by clicking the corresponding Revert to Basic Config button. Then, the WiFi Engage captive portal gets configured for that SSID.
The support documentation is available at https://emsp.cisco.com