# AGI32

# Introduction

Open iT supports AGI32 usage reporting 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 every night, 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.

# Requirements

# Updating AGI32 Configuration with the AGI32 License Portal Credentials

These steps configure AGI32 to use your credentials.

  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
     genlicutil AGI32 /config
  4. Type in the username when prompted,

    Example: Entering Username
     Enter username to use: Sample-UsersName

    then press Enter.

  5. Type in the password when prompted,

    Example: Entering Password
     Enter password: **********

    then press Enter.

# Configuring Data Collection

These are the required steps to activate and configure collection of AGI32 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. Activate the collection of AGI32 data, run the command:

    Command Syntax
     openit_confinit -c "licpoll.license-types.genericlicense-agi32-sample.active=true"
  5. Update the configuration file, run the command:

    Command Syntax
     openit_confbuilder --client

    Make sure no errors are encountered.

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

Object Name Accepted Value Description
active Boolean (true or false) Setting this to true activates AGI32 usage data collection.
type String (e.g., GenericLicense) The license manager type.
interval Timespan (e.g., P30S, P5M, P1H) The span of time between each polling round (it is recommended to set a value no less than P1M).
offset Timespan (e.g., P30S, P5M, P1H) The span of time the aligned poll time decided by interval is shifted.
product-name String (e.g., server;daemon) This object is defined if a vendor license name other than the default GenericLicense=%hosttype% will be used.
license-server String (e.g., hou105win) The License Server name.
status-command FileName (i.e., ${OpeniT.directories.bin}/genlicutil) The binary used to obtain status from the license manager.
status-command.arguments String (i.e., agi32) The arguments used for the status command.
AGI32 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 -# 12
  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.

# Sample Reports

# Historical Reports

# Max Available vs Max in Use

This sample report compares max in-use licenses against max available licenses.
It offers several key benefits:

  • 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.

Max Available vs Max in Use Licenses per Feature

Max Available vs Max in Use Licenses per Feature

# Feature Elapsed Time per User

This sample report gives you helpful insights into software use, performance trends, and user behavior.
It offers several key benefits:

  • User Efficiency Analysis – tracks how much time users spend on specific features to help assess productivity.
  • Identifying Workflow Issues – highlights any delays or inefficiencies in processes that could be improved.
  • Usability & UX Insights – points out features that take longer to use, which could indicate design or functionality improvements.
  • Training & Support Guidance – helps identify users who might need extra training to use a feature more effectively.
  • Compliance Tracking – makes sure users are spending the right amount of time on regulated tasks.
  • Resource & License Optimization – finds underused features or areas where too much time is spent, helping with better resource allocation.

Feature Elapsed Time per User

Feature Elapsed Time per User

# Real-time Report

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

Drilled Down Feature View

Drilled Down Feature View

# Next Steps?

   Renaming Vendor License    Renaming Features    Create and Add Report    License Monitor

We value your feedback!

Please take a few minutes to complete our survey and share your thoughts on your recent experience with our documentation.

Take survey

Close