Zum Inhalt springen
EBF Logo

EBF product documentation

Find help using and administering EBF applications

EBF MIDA

  • Changelog
  • 01. Getting Started
  • 02. Initial Setup
  • 03. MIDA Overview
  • 04. Apps
  • 05. Policies
  • 06. iBooks
  • 07. App lists
  • 08. Compliance Actions
  • 09. Audit Logs
  • 10. ENS Events
  • 11. MIDA Installation Guide
  • 12. MIDA Configuration Parameter
  • 13. Import & Sync Workers
  • 14. About the Event Notification Service (ENS)
  • 15. Troubleshooting
  • 16. Browser Support
  • 17. Contact

10. ENS Events

Table of Contents
  • Event types

In ENS Events the current ENS events are displayed.

The following information is displayed for each event:

  • Event type
  • Processing status
  • Data
  • Info
  • Added on
  • Processed by
  • Actions

Event types

Event type:DescriptionAction
MIDA Internal
ENS_ENABLEDENS_was activated in MIDA and the MI Core settings for ENS were savedNone
ENS_DISABLEDENS has been deactivated in MIDANone
ENS_RECONNECTTry to connect to the MI Core again on port 8883None
ENS_SUBSCRIBEEvent type was subscribedNone
ENS_UNSUBSCRIBEEvent type was disabledNone
ENS_CHECK_CONNECTION„Check“ was executed in the ENS settingsNone
DEVICE_ENROLLEDDevice has been registered and activatedGet information (details, labels/ apps) of this device from MI Core and create device in MIDA
DEVICE_CHECK_INDevices check inGeneral devices Query data from MI
DEVICE_NOT_COMPLIANTDevice not compliantMI Core has received a „Not compliant“ message for a device. The device is marked accordingly in MIDA.

With delay the data of the device is read from the MI Core, because MIDA receives the event before it becomes visible in the MI Admin Portal.( mida.ens.compliantHandler.delay)

DEVICE_COMPLIANTDevices is compliant againA non-complaint device was detected as compliant again by the Mi Core and marked in MIDA. With delay the data of the device is read from the MI Core, because MIDA receives the event before it becomes visible in the MI Admin Portal.( mida.ens.compliantHandler.delay)
DEVICE_RETIREDDevice deregisteredRemove device from MIDA
DEVICE_APP_INVENTORYChange to the App Inventory of a deviceChanging the app inventory of an app. MIDA queries the MI Core for the installed apps on the device
DEVICE_CERT_INVENTORYChange of certificates
DEVICE_PROFILE_INVENTORYProfile change
DEVICE_WIPEDDevice Deleted
DEVICE_REPORT_INITIALIZEDReporting
Processing status
UNPROCESSED:Event was received from MIDA and stored in MIDA table
PROCESSINGEvent is being processed. As a rule, data is requested from the MI Core
PROCESSEDEvents have been processed. Normally, these successful events are removed from the ENS event table after 3 hours. Therefore, there should be no events in the table that are older than 3 hours
FAILEDFailed

Data

More detailed information is displayed. For example, for device events the device UUID.

Info

Other information, primarily for error analysis.

Examples:

  1. not authorized to connect ENS user / password is not correct.
  2. MqttException (0) – java.net.UnknownHostException: emm-dev2.ebf.deXX
  3. Unknown MI Core

Added on

Event was entered into the MIDA database.

Actions

Event with status Failed can be executed again.

Existing events can be deleted (individually).

 

Was this article useful?
Still stuck? How can we help?

How can we help?

Updated on 3. Februar 2022
09. Audit Logs11. MIDA Installation Guide
Table of Contents
  • Event types
Subscribe for EBF Newsletter
©2020 EBF-EDV Beratung Föllmer GmbH, All Rights Reserved
Imprint Terms and Conditions Privacy Statement Contact
Facebook-square Twitter-square Linkedin Xing-square Instagram
EBF Status Check