Monitoring the XenMobile MDM Server

XenMobile MDM (also known as the XenMobile Device Manager (XDM)) is the MDM component within Citrix XenMobile, which runs on an Apache Tomcat web server configured as a Windows service and relies on Java software (Java virtual Machine). It provides role-based management, configuration and security of corporate and user-owned devices. Using this tool, IT can manage mobile devices, set mobile policies and compliance rules, gain visibility to the mobile network, provide control over mobile apps and data, and shield the network from mobile threats. IT can blacklist or whitelist apps, detect devices that are jailbroken or out of compliance and block their ActiveSync email access and do a full or selective wipe of a device that is lost, stolen or out of compliance. This implies that the non-availability of the XenMobile MDM, even for a few minutes, or a temporary slowdown in its operations, can have grave consequences! Without the XenMobile MDM, mobile devices will not be able to register with XenMobile; registered devices will not be able to download latest policies. This in turn can expose the environment to serious mobile threats – for instance, access by unauthorized devices and usage of blacklisted applications will go undetected; confidential information may travel beyond authorized boundaries increasing the possibilities of abuse. To keep such intrusions at bay and to ensure a secure mobile experience for users, administrators need to keep an eye on the availability and overall health of the XenMobile MDM, proactively detect potential problem conditions, and initiate measures to avert them.

To enable administrators to achieve this, eG Enterprise provides the XenMobile MDM monitoring model.

Figure 1 : The layer model of the XenMobile Device Manager

Each layer of this model is mapped to a wide variety of tests to pull out a wealth of performance information related to the XenMobile MDM. To enable the eG agent to access the API, the pre-requisites explained in Pre-requisites for Monitoring Citrix XenMobile MDM should be fulfilled. Using the metrics collected from the API, administrators can ascertain the following:

  • Is the XenMobile MDM server available over the network?
  • Is the Tomcat server hosting the XenMobile MDM operating at its peak capacity?
  • Are any JVM threads being blocked? Exactly, which thread is blocking and which line of code could have caused the block?
  • Is the XenMobile MDM server online?
  • Has the server experienced any error events recently? What type of errors are these?
  • Does the server have adequate user/device licenses?
  • Are scheduled jobs running as per schedule on the XenMobile MDM server?
  • What is the current device load on the server? Does the server’s thread pool have adequate threads to handle this load?
  • How many devices are currently managed by the server?
  • Which of these devices host blacklisted applications?
  • Do all managed devices contain all required applications? Which applications are missing on which devices?
  • Has the MDM server detected any jail-broken, perimeter-breaching, out-of-compliant, or passcode non-compliant devices? If so, which devices are they?
  • Has the MDM server triggered any automated actions on any device? Which of these actions are still pending on these devices and why?
  • Which devices are currently disconnected from the server?
  • Have any package deployments failed?

The sections that follow will take you on a layer-by-layer tour of the XenMobile MDM monitoring model. However, since the tests associated with the Operating System, Network, Application Processes, and Windows Service layers have been already dealt with in detail in the Unix and Windows Servers monitoring model, the documentation of this model will focus on the other layers only.