Cisco Cisco 3310 Mobility Services Engine Release Notes
35
Release Notes for Cisco Mobility Services Engine, Release 8.0.110.0
OL-32458-01
Operational Notes for Mobility Services Engine
•
For Google Chrome, follow the instructions given for WebGL and 3D Graphics in the Google
Chrome support website.
Chrome support website.
•
For Firefox, follow these steps to enable WebGL:
–
Download the latest build of Firefox browser and launch Firefox on your computer.
–
In the browser address line, enter about:config
–
In the Search text box, enter webgl to filter the settings
–
Double click webgl.enabled_for_all_sites
–
Set the webgl.enabled_for_all_sites=true
•
For Safari, follow these steps to enable WebGL:
–
Choose Safari > Preferences.
–
Click the Advanced tab.
–
Select the Show Develop menu in menu bar check box.
–
Choose Enable WebGL from the Develop menu.
Jboss Issue
Sometimes CMX Analytics service does not start up because of a stray Jboss process that runs as a root
user. If Analytics engine does not start and if you notice a stray Jboss process with root permissions
running, then you must to do the following:
user. If Analytics engine does not start and if you notice a stray Jboss process with root permissions
running, then you must to do the following:
•
Stop CMX Analytics service from the Prime Infrastructure.
•
Kill the Jboss process. command
•
Run the
chown -R nobody:nobody /opt/mse/analytics
command.
•
Start CMX Analytics service from the Prime Infrastructure.
Operational Notes for Facebook Wi-Fi
http://developers.facebook.com/status/
Operational Notes for CMX Connect and Engage
While upgrading the Prime Infrastructure server, the map IDs and the information also gets updated. This
results in the new identifiers for maps. The new identifiers are not automatically synchronized with the
CMX Connect and Engage. This causes the location updates to use the new identifiers but the CMX
Connect and Engage will not be aware of the new identifiers and cause the location updates to get
ignored. To resolve this issue, you must update maps in the CMX Connect and Engage user interface. To
update maps, login to CMX Connect and Engage user interface and choose Maps from left sidebar menu
and click Update Maps from PI.
results in the new identifiers for maps. The new identifiers are not automatically synchronized with the
CMX Connect and Engage. This causes the location updates to use the new identifiers but the CMX
Connect and Engage will not be aware of the new identifiers and cause the location updates to get
ignored. To resolve this issue, you must update maps in the CMX Connect and Engage user interface. To
update maps, login to CMX Connect and Engage user interface and choose Maps from left sidebar menu
and click Update Maps from PI.