Skip to main content
Version: 10.3

MIDAS

Introduction​

Open iT supports MIDAS usage reporting starting Open iT version 10.3.

Open iT supports MIDAS usage by polling the license servers at regular intervals to get the current status of its license use and availability.

For this collection, the data source is through an API. The data collector/preprocessor initiates the license status utility every hour using a 5-minute sample interval, triggering the data collection process. The license status utility requests the current license usage data from the license manager portal. After the license manager portal provides the requested data, the license status utility passes this information to the data collector/preprocessor. The data collector/preprocessor processes the data, preparing it for transmission. Finally, the preprocessed data is sent to the Core Server at five minutes past every hour (HH:05), according to the client's timezone, for further storage, completing the license usage data collection and processing.

License Manager Utility Polling Workflow through API

License Manager Utility Polling Workflow through API

This will produce the following aggregated data types used for historical reporting:

The following sections will guide you in setting up the necessary configuration to collect and send the required data to the server.

warning

Apply the configurations shown in the Open iT Core Client.

Requirements​

Setting up MIDAS Account(s)​

These are the required steps to set up data collection from the MIDAS portal.

  1. Open a command prompt with Administrator level privileges.

  2. Go to the bin directory, which is by default in C:\Program Files\OpeniT\Core\bin, run the command:

    Command Syntax
    cd <bin_dir>
    Example
    cd C:\Program Files\OpeniT\Core\bin

  3. Set the username and password, run the command:

    Command Syntax
    genlicutil2 midas --config
    note

    If you need to collect data from more than one MIDAS account, use the --account parameter when running this command. This allows you to create separate credentials for each account.

    Command Syntax
    genlicutil2 midas --config --account <account_name>

    where <account_name> is the name of the account you want to use for data collection.

    Example
    genlicutil2 midas --config --account acct1

  4. Type in the username (or email) when prompted.

    Example: Entering Username
    Enter username to use: john_doe@example.com

    Then press Enter.

  5. Type in the password when prompted.

    Enter password: **********

    Then press Enter.

note

Open iT saves the hashed MIDAS credential file, MIDAS, in the OpeniT directory, which is by default in C:\ProgramData\OpeniT. When you use the --account parameter, Open iT appends the account name to the credential file (for example, MIDAS_acct1). This allows each MIDAS account to maintain its own credentials within the same directory.

Optional Parameters
ParameterDescription
--account <account_name>Use this to specify the account you want to use for data collection.
--debugUse this to turn on debug logging.
-h, --helpUse this to display help text.
Optional Parameters

Configuring Data Collection​

These are the required steps to activate the collection of usage data.

  1. Go to the Components directory, which is by default in C:\Program Files\OpeniT\Core\Configuration\Components, and back up the licpoll.xml configuration file.

  2. Open a command prompt with Administrator level privileges.

  3. Go to the bin directory, which is by default in C:\Program Files\OpeniT\Core\bin, run the command:

    Command Syntax
    cd <bin_dir>
    Example
    cd C:\Program Files\OpeniT\Core\bin

  4. Once in the directory, copy the object node genericlicense-sample and rename it to your desired name. In this example, we will use genericlicense-midas. Run the command:

    Command Syntax
    openit_confinit -c "licpoll.license-types.genericlicense-sample=>licpoll.license-types.genericlicense-midas"
    warning

    Element names cannot contain parentheses ( or ) because they are not valid for XML element names.

  5. Activate the collection of MIDAS data, run the command:

    Command Syntax
    openit_confinit -c "licpoll.license-types.genericlicense-midas.active=true"

  6. Set the status command, run the command:

    Command Syntax
    openit_confinit -c "licpoll.license-types.genericlicense-midas.status-command=<bin_dir>\genlicutil2.exe"

    where <bin_dir> is the path to the bin directory, which is by default in C:\Program Files\OpeniT\Core\bin.

    Example
    openit_confinit -c "licpoll.license-types.genericlicense-midas.status-command=C:\Program Files\OpeniT\Core\bin\genlicutil2.exe"

    Alternatively, you can use the ${OpeniT.directories.bin} variable to reference the bin directory dynamically:

    Alternative Command
    openit_confinit -c "licpoll.license-types.genericlicense-midas.status-command=${OpeniT.directories.bin}/genlicutil2.exe"

  7. Set the arguments to the status command, run the command:

    Command Syntax
    openit_confinit -c "licpoll.license-types.genericlicense-midas.status-command.arguments=midas"
    note

    If you have multiple MIDAS accounts, repeat the configuration steps to create additional object nodes for each account. Use a unique name for every node (for example, genericlicense-midas1, genericlicense-midas2, and so on) and specify the corresponding account in the status-command arguments.

    Example for acct1
    openit_confinit -c "licpoll.license-types.genericlicense-midas1.status-command.arguments=MIDAS --account acct1"

    This ensures that Open iT collects data separately for each configured MIDAS account.

  8. Run the following command to update the configuration files:

    Example
    openit_confbuilder --client

    Make sure no errors are encountered.

Advanced Configuration

Refer to the MIDAS Data Collection Configuration table to learn more about MIDAS configuration in licpoll.xml.

Object NameAccepted ValueDescription
activeBoolean (true or false)Setting this to true activates MIDAS usage data collection.
typeString (i.e., GenericLicense)The license manager type.
intervalTimespan (e.g., P30S, P5M, P1H)The span of time between each polling round (it is recommended to set a value no less than P1M).
offsetTimespan (e.g., P30S, P5M, P1H)The span of time the aligned poll time decided by interval is shifted.
product-nameString (e.g., %host%;midas)This object is defined if a vendor license name other than the default %host%;midas will be used.
license-serverString (e.g., WIN-HOST01)The license server name.
status-commandFileName (i.e., ${OpeniT.directories.bin}/genlicutil2.exe)The binary used to obtain status from the license manager.
status-command.argumentsString (e.g., midas)The arguments used for the status command.
MIDAS Data Collection Configuration

Verifying Data Collection​

After configuration, you can verify that the data is collected by following these steps:

  1. Open a command prompt with Administrator level privileges.

  2. Go to the bin directory, which is by default in C:\Program Files\OpeniT\Core\bin, run the command:

    Command Syntax
    cd <bin_dir>
    Example
    cd C:\Program Files\OpeniT\Core\bin

  3. Run the command:

    Command Syntax
    openit_licpoll -# 1

  4. Verify that the temp directory, which is by default in C:\ProgramData\OpeniT\Data\temp, contains a LicPoll directory containing .data and status-*.log files.

  5. Verify that the .token file exists in the OpeniT directory, which is by default in C:\ProgramData\OpeniT.

Sample Reports​

Historical Reports​

Utilization Trend​

This sample report provides a visual representation of license activity for the selected application. It helps users and administrators quickly understand how licenses are being used, when peak demand occurs, and whether any access issues (such as denials) are happening.
It offers several key benefits:

  • Centralized Visibility – provides a clear view of license usage, availability, and denials in a single interface.
  • Optimized License Allocation – helps ensure you are not over-purchasing licenses you don't need or under-provisioning.
  • Cost Savings – identifies opportunities to downgrade or redistribute licenses, reducing unnecessary expenses.
  • Usage Trends & Capacity Planning – shows peak usage patterns, allowing better forecasting for future needs.
  • Avoiding Service Disruptions – helps prevent situations where users cannot access software due to reaching the license limit.
  • Compliance & Audit Readiness – provides a usage record to ensure compliance with vendor agreements and avoid penalties.
  • Performance & Productivity Insights – helps assess whether certain teams or departments are under-utilizing or over-utilizing software.
  • Historical and Real-Time Analysis – combines near real-time monitoring with historical trend analysis, enabling both immediate decision-making and long-term planning.

Utilization Trend

Utilization Trend

Real-time Report​

This sample report shows a drilled-down feature view of the online licenses in use and the licenses available.

License Monitor Portal

License Monitor Portal

Next Steps?​

Renaming Vendor License
Renaming Features
Create and Add Report
License Monitor