MMS Integration Overview
Remote integration with the Media Manager System (MMS) is provided through web services.
Web Services
The current version of the MMS integration interface supports a set of operational Web Services that provide the ability for integrators to manage delivery of content to their fleet.
Web Services in Production
The production web services can be categorized as follows:
Migration to Omnitracs Web services Endpoint
The web services: Delivery Management and Group Management are now available on omnitracs.com domain and the services currently on myqualcomm.com domain will be retired in sometime in future. So, we encourage migrating your programs to use the newer WSDL. There are no functional changes to the web services.
Endpoint https://mm.omnitracs.com/mms-ws/mms.wsdl support will end in future.
https://mm.omnitracs.com/mms-webservice/mms.wsdl Available for use from 02/27/2016.
Endpoint https://qgsws.omnitracs.com/qgs-ws/qgs.wsdl support will end in future.
https://qgsws.omnitracs.com/qgs-webservice/qgs.wsdl Available for use from 02/27/2016.
Event Subscription Service
MMS is integrated with the Event Subscription Service (ESS) provided by the Omnitracs Services Portal (QSP) which includes access to event-based data. ESS is built upon the publish/subscribe model. Applications that are hosted on the QSP Server may use ESS to make transactions available for publication. In turn, ESS provides a common interface (accessible through web services) that allows interested remote applications to subscribe to, and subsequently consume, various transactions. These transactions are primarily event-based. The ESS transaction interface provides the means to receive these event feeds in near real time.
Asynchronous Events
It is important to note that some of the web services provided by the integration interface result in the generation, and subsequent publishing, of events to ESS. The integrator must subscribe to specific ESS events in order to retrieve or monitor the request in these cases. For example, the sendDelivery API initiates content to be delivered to a mobile device. The web services do not block the caller. They generate the request and return to the caller immediately. The response from the mobile will wind up being published to ESS. The caller must consume the ESS event if it is interested in the response.
Specifically, MMS events are published to ESS using Transaction T.8.01.0. This transaction encapsulates events that can happen for different reasons.
- Content is available on the vehicle
- Content has been viewed.
- Content has been deleted.