Skip to main content

RISA

Open iT supports RISA usage reporting starting Open iT version 10.2.580.

Introduction​

Open iT supports RISA 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.

warning

Apply the configurations shown in the Open iT Core Client.

Requirements​

Setting up RISA Account(s)​

These are the required steps to set up data collection from the RISA 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 risa --config
    note

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

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

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

    Example
    genlicutil2 risa --config --account acct1

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

    Example: Entering Username
    Enter username to use: sample-config@company.com

    then press Enter.

  5. Type in the password when prompted,

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

    then press Enter.

note

Open iT saves the hashed RISA credential file, Risa, 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, Risa_acct1). This allows each RISA account to maintain its own credentials within the same directory.

Configuring Data Collection​

These are the required steps to activate 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-risa. Run the command:

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

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

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

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

  6. Set the status command, run the command:

    Command Syntax
    openit_confinit -c "licpoll.license-types.genericlicense-risa.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-risa.status-command=C:\Program Files\OpeniT\Core\bin\genlicutil2.exe"

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

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

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

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

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

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

    Command Syntax
    openit_confbuilder --client

    Make sure no errors are encountered.

Advanced Configuration

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

Object NameAccepted ValueDescription
activeBoolean (true or false)Setting this to true activates RISA 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., server;daemon)This object is defined if a vendor license name other than the default GenericLicense=%hosttype% 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., risa)The arguments used for the status command.
RISA 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 Risa.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

License Efficiency​

This sample report gives you helpful insights on how much time a software license has been used. It shows whether licenses are being actively used or left idle, giving you a quick way to understand how efficiently your licenses are being managed.
It offers several key benefits:

  • License Utilization Tracking – monitors how long licenses are in use during a given period and see if any licenses are not being used so they can be reassigned.
  • 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.
  • Compliance & Audit Readiness – provides a usage record to ensure compliance with vendor agreements and avoid penalties.

License Efficiency

License Efficiency

Heatmap​

This sample report provides a visual representation of license usage by day of the week and hour of the day for the selected application.
It offers several key benefits:

  • Peak Usage Identification – highlights the specific days and hours with the highest demand for licenses.
  • Workload Distribution – helps balance activity by identifying underutilized periods where tasks can be scheduled.
  • Resource Planning – supports better allocation of licenses by anticipating peak and off-peak usage times.
  • User Behavior Insights – reveals patterns in how and when users access software, such as evening or weekday activity.
  • Avoiding Bottlenecks – reduces delays by planning critical tasks during low-usage hours.
  • Historical & Predictive Trends – combines weekly usage patterns with historical insights to inform long-term planning and decision-making.

Heatmap

Heatmap

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