Cisco Cisco 3350 Mobility Services Engine Developer's Guide
C
ISCO
MSE
API
S
PECI FICATI ON
G
UI DE
–
C
ONTEXT
A
W ARE
S
ERVICE OF
MSE,
R
ELEASE
7.4
.
P
A G E
27
O F
2 27
Any application like WCS or other partner application or devices which wants to use the one or
more services provided by MSE can communicate to MSE through unified APIs over various
protocols supported by MSE - HTTP/SOAP.
more services provided by MSE can communicate to MSE through unified APIs over various
protocols supported by MSE - HTTP/SOAP.
Figure 1 Mobility Service Engine – System Level
1.4 Salient API features
MSE exposes the following HTTP/SOAP endpoints:
Note: The service engine specific endpoints are present if the service exists on a MSE box. It is
licensed and enabled.
Table 1
Note: The service engine specific endpoints are present if the service exists on a MSE box. It is
licensed and enabled.
Table 1
Endpoint URL
Target Service/Module
Login and Logout Module
Design and Location Module
From MSE, there will be two WSDL, common Login/Logout to the engine and location as a
seperate service.
seperate service.
mse-aaa.wsdl - which contains calls for Login/Logout with endpoint https://mseip/aaa/
mse-location.wsdl - which contains all location calls with endpoint
Note the trailing slash in the URI
Indoor
APs
Controllers
Location
SOAP
MSE
Wireless
Control
System
Third Party
Applications
Applications