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

12. MIDA Configuration Parameter

Table of Contents
  • General configuration
  • Mida Configuration
  • Calculation of parameters

Note:

The configuration parameters are stored in the file /etc/sysconfig/mida on each individual MIDA server.

General configuration

NameTypeExample ( default in ms)Description
db.crypt.keymandatory, stringpassword encryption secret key
token.ttlnumber28800000auth token time to live
token.secretmandatory, stringjwt token verification secret
spring.http.multipart.locationstringtemporary location for uploaded files
server.portnumber80Specify the TCP-Port for the MIDA Website
spring.profiles.activestringspring profile (default: prod)
spring.datasource.driverClassNamemandatory,stringjdbc driver class name
spring.datasource.urlmandatory, stringMIDA database link / URL
spring.datasource.usernamemandatory, stringMIDA database username
spring.datasource.passwordmandatory, stringMIDA database password
spring.jpa.database-platformmandatory, stringsql dialect of the database

Example: org.hibernate.dialect.SQLServer2012Dialect

mail.protocolstringEmail Server Protocol
mail.hoststringEmail Server Host
mail.portstringEmail Server Port
mail.smtpAuthbooleanIs SMTP Auth used? true or false
mail.smtpStartlsebooleanShould Starttlse be used? true or false
mail.fromstringEmail address with which MIDA sends emails
mail.usernamestringEmail Server Username
mail.passwordstringEmail Server Password

 

Mida Configuration

NameTypeDefault valueDescription
mida.superAdmin.usernamemandatory, stringSuperadmin username
mida.superAdmin.passwordmandatory, stringbcrypt password hash with “Number of rounds” set to 10
mida.superAdmin.labelNamemandatory, stringsuper admin label, usually: All-Smartphones
mida.fi.instituteMarkerAttributeNamestringFI specific, if set it will turn on the post device registration action for setting device custom attributes
mida.compliance.worker.hound.intervalnumber60000interval for hound executions in milliseconds
mida.compliance.worker.hound.delaynumber30000delay for hound executions in milliseconds
mida.compliance.worker.policeman.intervalnumber10000interval for policeman executions in milliseconds
mida.compliance.worker.policeman.delaynumber5000delay for hound executions in milliseconds
mida.coredata.label.import.intervalnumber5000interval for labels import executions in milliseconds
mida.coredata.label.import.delaynumber10000delay for labels import executions in milliseconds
mida.coredata.label.sync.intervalnumber1000interval for labels sync executions in milliseconds
mida.coredata.label.sync.delaynumber60000delay for labels sync vpp in milliseconds
mida.coredata.app.import.intervalnumber30000interval for apps import executions in milliseconds
mida.coredata.app.import.delaynumber10000dealy for apps import executions in milliseconds
mida.coredata.app.sync.delaynumber11000delay for apps import executions in milliseconds
mida.coredata.app.sync.intervalnumber15000interval for apps import executions in milliseconds
mida.coredata.app.vpp.sync.delaynumber12000delay for app vpp sync executions in milliseconds
mida.coredata.app.vpp.sync.intervalnumber10000interval for app vpp sync executions in milliseconds
mida.coredata.app.label.sync.delaynumber13000delay for app label sync executions in milliseconds
mida.coredata.app.label.sync.intervalnumber5000interval for app lable sync executions in milliseconds
mida.coredata.policy.match.delaynumber0delay for policy match executions in milliseconds
mida.coredata.policy.match.intervalnumber1000interval for polocy match executions in milliseconds
mida.coredata.policy.sync.delaynumber10000delay for polocy sync executions in milliseconds
mida.coredata.policy.sync.intervalnumber10000interval for polocy sync executions in milliseconds
mida.coredata.device.import.delaynumber10000delay for devices import executions in milliseconds
mida.coredata.device.import.intervalnumber9000000interval for devices import executions in milliseconds
mida.coredata.device.sync.delaynumber11000delay for devices sync executions in milliseconds
mida.coredata.device.sync.intervalnumber15000interval for devices sync executions in milliseconds
mida.coredata.device.label.sync.delaynumber13000delay for device label sync executions in milliseconds
mida.coredata.device.label.sync.intervalnumber5000interval for device label sync executions in milliseconds
mida.coredata.applist.inhouse.updater.worker.delaynumber30000interval executions in milliseconds
mida.coredata.applist.inhouse.updater.worker.intervalnumber1200000interval executions in milliseconds
mida.devices.registration.countriesListstringDE,UScoma separated list of countries that should be available for the registration of a new device. If the list is empty all countries from the core will be available
mida.coredata.device.customAttributes.sync.delaynumber15000delay for device custom attributes sync executions in milliseconds
mida.coredata.device.customAttributes.sync.intervalnumber5000interval for device custom attributes sync executions in milliseconds
mida.fi.instituteMarkerAttributeLengthnumber4FI specific, the length the mida.fi.instituteMarkerAttributeName custom attribute value in the Core
mida.devices.reports.last.daysnumber30It is used in all time based report and represent the time frame of the last x days since the report creation. The time based report will contain the records of the specific time frame
mida.coredata.ibooks.sync.delaynumber15000delay for iBook sync in milliseconds
mida.coredata.ibooks.sync.intervalnumber15000interval for iBooks sync in milliseconds
mida.coredata.ibooks.import.delaynumber15000delay for iBook label import in milliseconds
mida.coredata.ibooks.import.intervalnumber15000interval for iBooks import in milliseconds
mida.coredata.ibooks.label.sync.delaynumber15000delay for iBook label sync in milliseconds
mida.coredata.ibooks.label.sync.intervalnumber15000interval for iBook labels sync in milliseconds
mida.general-info.versionstringEbf MIDA versionOverwrite the MIDA version.

Example: 2.7.0No
quotes

mida.coredata.device.resync.minutesAgonumber10
(Minutes)
Fetch devices that were created before X minutes ago for performing resync. Time in minutes
mida.coredata.device.resync.delaynumber30000How long after MIDA startup should the first run of the device resync task be. Time in milliseconds
mida.coredata.device.resync.intervalnumber30000How often should this device resync task run
mida.coredata.logs.cleanUpHoursnumber168
(Days)
Remove error logs older than X hours from the entity_error_log table. The default value is 168 hours (7 days).
This is NOT about the MIDA Audit logs.
Value in Days.
mida.coredata.logs.cleanup.delaynumber15000How long after MIDA startup should the first run be?
mida.coredata.logs.intervalnumber86400000How often should the cleanup worker run and remove old data from the entity_error_logs table. By default it runs every 24 hours
mida.event.janitor.intervalnumber3600000How often should the Janitor run and remove successful proccessed ENS events from the MIDA table? By default, the events are removed from the ens_events table that have the status PROCESSED and are older than 3 hours ( if not changed using the parameter mida.event.retention.time). Others are retained
mida.event.janitor.delaynumber20000Delay for starting the task after MIDA service start/restart?
mida.event.retention.timenumber10800000How long should events be stored?
Default 3 hours
mida.event.janitor.clearEventsstringPROCESSEDWhich processing statuses are automatically removed by the janitor. Comma separated list.

Possible values:

PROCESSED, PROCESSING,

FAILED, UNPROCESSED

mida.cluster.nodeNamestringHere you can define the name for a node (MIDA Server).

Without the parameter, a cryptic ID is used.

Recommended for multiple MIDA Servs.

mida.cluster.reelection.intervalnumber60000How often is a new ENS Leader is selected?
mida.cluster.reelection.delaynumber5000Delay for starting the tasl after MIDA service start/restart?
mida.ens.reelectionConnection.intervalnumber3000Each mida ENS node checks the entry lastUpdated and last_leader_updated in the table [dbo].[leader_election]. If the two values have a difference of more than 3 seconds, a new leader is determined.
mida.ens.reelectionConnection.delaynumber5000Delay for starting the tasl after MIDA service start/restart?
mida.ens.eventCleanup.intervalnumber1800000ENS events older than 3 hours and events with the status PROCESSING are converted to UNPROCESSED and processed again later on.
mida.ens.eventCleanup.delaynumber5000Delay for starting the task after MIDA service started/restarted?
mida.ens.compliantHandler.delaynumber60000Delay for the Non Compliant / Compliant devices check on the MI Core.

mida.ens.eventsPriority

mida.ens.eventsPrioritymapAdjustment of priorities of ENS event types.

 

The events ENS_ENABLED, ENS_DISABLED, ENS_RECONNECT, ENS_SUBSCRIBE must ALWAYS have the highest priority of all events, otherwise the ENS system can be blocked!

Possible values: (default priority):

ENS_ENABLED (100),ENS_DISABLED (100),ENS_RECONNECT (100),ENS_SUBSCRIBE (95),ENS_UNSUBSCRIBE (95),ENS_CHECK_CONNECTION (90),DEVICE_ENROLLED (0),DEVICE_CHECK_IN (0),DEVICE_NOT_COMPLIANT (0),DEVICE_COMPLIANT (0),DEVICE_RETIRED (0),DEVICE_APP_INVENTORY (0),DEVICE_CERT_INVENTORY (0),DEVICE_PROFILE_INVENTORY (0),DEVICE_WIPED (0),DEVICE_REPORT_INITIALIZED (0)

Example:

mida.ens.eventsPriority={DEVICE_ENROLLED:80,DEVICE_NOT_COMPLIANT:80,DEVICE_COMPLIANT:80,DEVICE_RETIRED:80}

This is used to process the events that are important for the administrators earlier.
Within the {} no spaces must be used.

The DEVICE_ events must not be given a priority higher than 89 in order not to endanger the operation.

Unlisted events retain their default priority.

mida.event.monitor.intervalnumber5000How often does a MIDA server search for a new event (the oldest event) in the MIDA event table?
mida.event.monitor.delaynumber1000Delay for starting the ENS Event Handling task after MIDA service start/restart?
mida.coredata.sync.maxRetriesnumber1
Number of retires
Sets the max number of retries to perform API sync actions.
Handle with care.
mida.coredata.sync.retryDelaynumber5000Sets the max duration to perform retries for, else the execution will be failed. It is a number in milliseconds

 

Parameter for a custom pluginTypeDefault valueDescription
mida.plugins.lostDevices.activebooleanfalseActivate lost devices custom plugin
mida.events.lostDevices.triggerWordstringlostThe word that should be used for triggering internal DEVICE_LOST MIDA events when admin retires or wipes devise. The reason must be equals this trigger word.

Calculation of parameters

MIDA synchronization parameters are always specified in milliseconds(ms).

Number / (ms/1000) = X seconds for one pass

  • X / 60 = Y minutes
  • Y / 24 = Z hours When using a MIDA server
  • Z / (number of MIDA servers)
Was this article useful?
Still stuck? How can we help?

How can we help?

Updated on 3. Februar 2022
11. MIDA Installation Guide13. Import & Sync Workers
Table of Contents
  • General configuration
  • Mida Configuration
  • Calculation of parameters
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