Zum Inhalt springen
  • Blog
  • Cookie Policy (EU)
  • Datenschutzerklärung
  • EBF Docs
  • EBF Onboarder 3.0
  • Onboarder Source and Target
  • Test
  • Diese Website durchsuchen

    EBF product documentation

    Find help using and administering EBF applications

    EBF MIDA

    • Release Notes
    • 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
    View Categories
    • Home
    • EBF Docs
    • EBF MIDA

    12. MIDA Configuration Parameter

    8 min read

    0:00 / 8:46
    • View as Markdown Open this page as plain Markdown (opens in a new tab)
    • Open in ChatGPT Ask questions about this page (opens in a new tab)
    • Open in Claude Ask questions about this page (opens in a new tab)
    • Open in Google AI Studio Ask questions about this page (Google account required) (opens in a new tab)

    Note:

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

    General configuration

    Name Type Example ( default in ms) Description
    db.crypt.key mandatory, string password encryption secret key
    token.ttl number 28800000 auth token time to live
    token.secret mandatory, string jwt token verification secret
    spring.http.multipart.location string temporary location for uploaded files
    server.port number 80 Specify the TCP-Port for the MIDA Website
    spring.profiles.active string spring profile (default: prod)
    spring.datasource.driverClassName mandatory,string jdbc driver class name
    spring.datasource.url mandatory, string MIDA database link / URL
    spring.datasource.username mandatory, string MIDA database username
    spring.datasource.password mandatory, string MIDA database password
    spring.jpa.database-platform mandatory, string sql dialect of the database

    Example: org.hibernate.dialect.SQLServer2012Dialect

    mail.protocol string Email Server Protocol
    mail.host string Email Server Host
    mail.port string Email Server Port
    mail.smtpAuth boolean Is SMTP Auth used? true or false
    mail.smtpStartlse boolean Should Starttlse be used? true or false
    mail.from string Email address with which MIDA sends emails
    mail.username string Email Server Username
    mail.password string Email Server Password

     

    Mida Configuration

    Name Type Default value Description
    mida.superAdmin.username mandatory, string Superadmin username
    mida.superAdmin.password mandatory, string bcrypt password hash with “Number of rounds” set to 10
    mida.superAdmin.labelName mandatory, string super admin label, usually: All-Smartphones
    mida.fi.instituteMarkerAttributeName string FI specific, if set it will turn on the post device registration action for setting device custom attributes
    mida.compliance.worker.hound.interval number 60000 interval for hound executions in milliseconds
    mida.compliance.worker.hound.delay number 30000 delay for hound executions in milliseconds
    mida.compliance.worker.policeman.interval number 10000 interval for policeman executions in milliseconds
    mida.compliance.worker.policeman.delay number 5000 delay for hound executions in milliseconds
    mida.coredata.label.import.interval number 5000 interval for labels import executions in milliseconds
    mida.coredata.label.import.delay number 10000 delay for labels import executions in milliseconds
    mida.coredata.label.sync.interval number 1000 interval for labels sync executions in milliseconds
    mida.coredata.label.sync.delay number 60000 delay for labels sync vpp in milliseconds
    mida.coredata.app.import.interval number 30000 interval for apps import executions in milliseconds
    mida.coredata.app.import.delay number 10000 dealy for apps import executions in milliseconds
    mida.coredata.app.sync.delay number 11000 delay for apps import executions in milliseconds
    mida.coredata.app.sync.interval number 15000 interval for apps import executions in milliseconds
    mida.coredata.app.vpp.sync.delay number 12000 delay for app vpp sync executions in milliseconds
    mida.coredata.app.vpp.sync.interval number 10000 interval for app vpp sync executions in milliseconds
    mida.coredata.app.label.sync.delay number 13000 delay for app label sync executions in milliseconds
    mida.coredata.app.label.sync.interval number 5000 interval for app lable sync executions in milliseconds
    mida.coredata.policy.match.delay number 0 delay for policy match executions in milliseconds
    mida.coredata.policy.match.interval number 1000 interval for polocy match executions in milliseconds
    mida.coredata.policy.sync.delay number 10000 delay for polocy sync executions in milliseconds
    mida.coredata.policy.sync.interval number 10000 interval for polocy sync executions in milliseconds
    mida.coredata.device.import.delay number 10000 delay for devices import executions in milliseconds
    mida.coredata.device.import.interval number 9000000 interval for devices import executions in milliseconds
    mida.coredata.device.sync.delay number 11000 delay for devices sync executions in milliseconds
    mida.coredata.device.sync.interval number 15000 interval for devices sync executions in milliseconds
    mida.coredata.device.label.sync.delay number 13000 delay for device label sync executions in milliseconds
    mida.coredata.device.label.sync.interval number 5000 interval for device label sync executions in milliseconds
    mida.coredata.applist.inhouse.updater.worker.delay number 30000 interval executions in milliseconds
    mida.coredata.applist.inhouse.updater.worker.interval number 1200000 interval executions in milliseconds
    mida.devices.registration.countriesList string DE,US coma 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.delay number 15000 delay for device custom attributes sync executions in milliseconds
    mida.coredata.device.customAttributes.sync.interval number 5000 interval for device custom attributes sync executions in milliseconds
    mida.fi.instituteMarkerAttributeLength number 4 FI specific, the length the mida.fi.instituteMarkerAttributeName custom attribute value in the Core
    mida.devices.reports.last.days number 30 It 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.delay number 15000 delay for iBook sync in milliseconds
    mida.coredata.ibooks.sync.interval number 15000 interval for iBooks sync in milliseconds
    mida.coredata.ibooks.import.delay number 15000 delay for iBook label import in milliseconds
    mida.coredata.ibooks.import.interval number 15000 interval for iBooks import in milliseconds
    mida.coredata.ibooks.label.sync.delay number 15000 delay for iBook label sync in milliseconds
    mida.coredata.ibooks.label.sync.interval number 15000 interval for iBook labels sync in milliseconds
    mida.general-info.version string Ebf MIDA version Overwrite the MIDA version.

    Example: 2.7.0No
    quotes

    mida.coredata.device.resync.minutesAgo number 10
    (Minutes)
    Fetch devices that were created before X minutes ago for performing resync. Time in minutes
    mida.coredata.device.resync.delay number 30000 How long after MIDA startup should the first run of the device resync task be. Time in milliseconds
    mida.coredata.device.resync.interval number 30000 How often should this device resync task run
    mida.coredata.logs.cleanUpHours number 168
    (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.delay number 15000 How long after MIDA startup should the first run be?
    mida.coredata.logs.interval number 86400000 How 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.interval number 3600000 How 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.delay number 20000 Delay for starting the task after MIDA service start/restart?
    mida.event.retention.time number 10800000 How long should events be stored?
    Default 3 hours
    mida.event.janitor.clearEvents string PROCESSED Which processing statuses are automatically removed by the janitor. Comma separated list.

    Possible values:

    PROCESSED, PROCESSING,

    FAILED, UNPROCESSED

    mida.cluster.nodeName string Here 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.interval number 60000 How often is a new ENS Leader is selected?
    mida.cluster.reelection.delay number 5000 Delay for starting the tasl after MIDA service start/restart?
    mida.ens.reelectionConnection.interval number 3000 Each 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.delay number 5000 Delay for starting the tasl after MIDA service start/restart?
    mida.ens.eventCleanup.interval number 1800000 ENS events older than 3 hours and events with the status PROCESSING are converted to UNPROCESSED and processed again later on.
    mida.ens.eventCleanup.delay number 5000 Delay for starting the task after MIDA service started/restarted?
    mida.ens.compliantHandler.delay number 60000 Delay for the Non Compliant / Compliant devices check on the MI Core.

    mida.ens.eventsPriority

    mida.ens.eventsPriority map Adjustment 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.interval number 5000 How often does a MIDA server search for a new event (the oldest event) in the MIDA event table?
    mida.event.monitor.delay number 1000 Delay for starting the ENS Event Handling task after MIDA service start/restart?
    mida.coredata.sync.maxRetries number 1
    Number of retires
    Sets the max number of retries to perform API sync actions.
    Handle with care.
    mida.coredata.sync.retryDelay number 5000 Sets the max duration to perform retries for, else the execution will be failed. It is a number in milliseconds

     

    Parameter for a custom plugin Type Default value Description
    mida.plugins.lostDevices.active boolean false Activate lost devices custom plugin
    mida.events.lostDevices.triggerWord string lost The 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
    Linkedin-in Phone
    Workplace Management
    • UEM Solutions
    • Migrations
    • Services
    Modern Work Tools
    • Sync Contacts
    • Hybrid Data Management
    • Secure Mobile Printing
    • eSIM Management
    • App Management
    IT Security
    • IAM
    • Modern Threat Defense
    • Cyber Risk Management
    • Secure Development
    • Zero Trust
    • Security Check
    AI Solutions
    • AI Adoption
    • Copilot Consulting
    • EBF Insight
    • EBF Flow
    Company
    • About Us
    • References
    • Partners
    • Sustainability
    • Careers
    • Trends
    © 2026 EBF-EDV Beratung Föllmer GmbH
    • Privacy Policy
    • GTC
    • EULA
    • Imprint
    EBF Status Check