---
title: AbsInt
description: Configure OpenLM Broker in OpenLM Version 26 to monitor the token usage of the AbsInt License Manager (ALM) through its web interface, then approve it in OpenLM SLM.
product: OpenLM Version 26 (legacy)
---

> **OpenLM Version 26 (legacy).** This page documents the legacy product, not OpenLM Platform.

OpenLM can monitor the AbsInt License Manager (ALM), which serves the license tokens of AbsInt tools such as Astrée and RuleChecker, through OpenLM Broker. Broker supports it with the **AbsInt** LM Type and reports it to OpenLM SLM in the **OpenLM Generic** format.

Broker reads the token usage and the connected users from the ALM web interface, and reports each token type as a feature, with the users who hold its tokens, to OpenLM SLM.

## Requirements

1. **OpenLM SLM** or [Software License Management Cloud (SLMC)](https://www.openlm.com/documentation/legacy/slmc/index) environment with permissions to approve new **OpenLM Generic** license managers.
2. **OpenLM Broker v24.11.11.806 or higher** installed on a machine that reaches the ALM web interface over HTTP. In Broker versions earlier than v25.2.6.1326, the default address of the data inquiry is `http://localhost:8080/?xml` instead of your ALM, and you correct it in [OpenLM Broker configuration](#openlm-broker-configuration).
3. Network access from the Broker to OpenLM SLM (default port **5015**).
4. The host name of the machine that runs the ALM, and the HTTP port of its web interface: `42425` by default. Don't use the ports that AbsInt tools use to request tokens, `42426` (TLS) and `42424` (legacy tools). See the [Astrée and RuleChecker 23.10 release notes](https://www.absint.com/releasenotes/astree/23.10/) for the default ports.
5. The HTTP web interface of the ALM turned on. It is on by default. An ALM started with `--http-port 0` serves no HTTP web interface.
6. A firewall rule that lets the Broker machine reach the ALM host on the web interface port.

## Monitoring capabilities

| LM type | Commands | Logs | Quantity | Expiration date | Denied | Borrowing | Allocations | Report resolution |
|----------------|-----------|------|-----------|------------------|---------|------------|--------------|-------------------|
| AbsInt | Yes       | No   | Yes       | Yes              | No      | No         | No           | Minutes           |

For each token type that the ALM serves, Broker reports:

- **Feature name**: the program name and the token name, joined with a dot, for example `a3c.astree` or `a3c.rulechecker-connections`. OpenLM SLM shows the same name as the product.
- **License total** and **licenses in use**: the total and the assigned tokens of the type, as the **Token usage** tab of the ALM web interface shows them.
- **Expiration date**: the expiration date of the license installed in the ALM. The same date applies to every token type.
- **License type**: Broker reports every token type as **Floating**.
- **Vendor**: `AbsInt`, unless you add a vendor on the **Vendors** tab.

For each client connection that holds tokens, Broker reports the user and the computer that the ALM lists for the connection, and the number of tokens that it holds of each type. A connection that holds no tokens doesn't appear in OpenLM SLM.

The ALM doesn't report when a session started. In OpenLM SLM, a session starts at the first query that finds it.

Broker does not report denials, borrowed licenses, or license allocations. It runs no commands that start or stop the ALM.

## How OpenLM interfaces with AbsInt

The following diagram shows how OpenLM Broker collects AbsInt usage and sends it to OpenLM SLM.

*How OpenLM Broker collects AbsInt usage.*

Broker queries the ALM web interface every 55 seconds by default. Broker reads no ALM log file and no license file.

Each query reads the current state of the ALM. A session that starts and ends between two queries doesn't reach OpenLM SLM, and Broker does not upload the usage history from before you add the license manager.

The pending entry in EasyAdmin gets the time zone of the Broker machine.

## OpenLM Broker configuration

:::note
Install OpenLM Broker and confirm that it reports to OpenLM SLM before starting these steps.
:::

1. Open a browser on the Broker machine and go to the Broker web UI at [http://localhost:5090/](http://localhost:5090/).

2. On the **License Managers** page, check that **Host** shows the host name of the ALM machine.

    OpenLM SLM lists the license server under this host name. The field holds the host for every license manager on the page, not for AbsInt alone.

    - If the field is empty, enter the host name of the ALM machine and select the save icon next to the field.
    - If it names a different machine, leave it as it is, and enter the ALM host name in the data inquiry address in step 5.

3. Select **Add License Manager** and select **AbsInt** as the **LM Type**.

4. In **Port**, enter the HTTP port of the ALM web interface, for example **42425**. Then select **Add**.

    OpenLM SLM names the license server after this port, as `42425@<host>`.

    *Add AbsInt as the license type.*

5. On the **Commands** tab, check the address in the **Data Inquiry** box.

    **Data Inquiry** is the only command for **AbsInt**. It runs every 55 seconds by default, set in **Watch interval (sec)**. Its address holds the **Host** and the port that you entered, for example `http://absint01.example.com:42425/?xml`.

    - If the ALM runs on the machine in **Host**, keep the address.
    - If the ALM runs on another machine, replace the host name and the port in the address with those of the ALM, for example `http://alm01.example.com:42425/?xml`.
    - If the Broker is earlier than v25.2.6.1326, the address is `http://localhost:8080/?xml`. Replace it with the ALM host name and port. **Restore Default** brings back the wrong address in these versions.

    Keep `/?xml` at the end of the address. Without it, the ALM returns its web page, and Broker cannot read the token usage.

    *Check the Data Inquiry address.*

6. Leave **Use the operating system start/stop commands** off and the **Log Files** tab empty.

7. (Optional) On the **Vendors** tab, add a vendor to show a vendor name other than `AbsInt` in OpenLM SLM.

8. Select **Save**.

To test the address, open the AbsInt license manager again, select **Data Inquiry** on the **Commands** tab, and select **Execute**. A working address returns each token type with its total and the users who hold tokens. If you never saved the license manager, Broker answers "Need to save first in order to execute command".

*Test the address with Execute.*

**Detect** doesn't find the ALM. Add the license manager by hand.

To read the ALM over HTTPS, use `https://` and the HTTPS port of the web interface, `42427` by default, in the **Data Inquiry** address, for example `https://alm01.example.com:42427/?xml`. On a Windows Broker machine, Broker trusts the certificates in **Trusted Root Certification Authorities** of the local computer. Import the ALM certificate there, or the certificate of the authority that issued it, and restart the OpenLM Broker service. Otherwise **Execute** answers with an error that starts with `PKIX path building failed`.

## OpenLM SLM configuration

### Automatic configuration through EasyAdmin

When the Broker reports AbsInt, approve the license server in EasyAdmin:

1. Open EasyAdmin (`http://<Server IP>:5015`) and go to **Start → Widgets → License Manager - Servers**.
2. Select the **There are N servers pending approval** link at the top of the widget.

    *Pending approval message.*

    The **Administration - License Manager Servers** window opens, with the pending entries at the top of the list.

3. Find the pending AbsInt entry, with the host name and the port as configured in Broker, and select the edit icon at the end of its row.

    The entry has the **Status** **Pending** and the **Display Name** `<port>@<host>`. OpenLM SLM has no plugin for the AbsInt type, so its **Type** is **OpenLM Generic**, the protocol that Broker reports it with. The edit icon appears when you hover over the row.

    *Approve the pending license server.*

4. Update the **Display name** to something meaningful, confirm the **Host Name** and **Port**, and select **APPROVE**.

    **Use Broker** is on, and **Time Zone** is the time zone of the Broker machine.

    *Update the display name and approve.*

### Manual configuration through EasyAdmin

If automatic configuration fails:

1. Go to **Start → Administration → License Manager Servers**.
2. Select **Add LM**.
3. In **Display name**, enter a name for the connection, for example `AbsInt`.
4. From **Type**, select **OpenLM Generic**.

    **Use Broker** turns on.

5. In the row under **Host Name**, **Port**, and **Time Zone**, enter the host name and the port exactly as configured in Broker for AbsInt, and select the time zone of the Broker machine.
6. Select **SAVE**.

The **Time Zone** of the entry must match the time zone of the Broker machine. When the two differ, the license server doesn't show as **Up to date**.

## Verify your configuration

1. Open EasyAdmin in your browser.
2. Go to **Start → Widgets → License Manager - Servers**.
3. Find the AbsInt license server and confirm that its **Status** is **Up to date**.

    After approval, the license manager appears with the **Type** **OpenLM Generic**. **Quantity** is the sum of the totals of all token types, and **Used** is the number of tokens in use.

    *The license manager appears as OpenLM Generic.*

4. In the row of the AbsInt license server, select the number in **Quantity**.

    The **Licenses** window opens with 1 row for each token type, with **Vendor** **AbsInt**, **License Type** **Floating**, its total in **Total**, and the tokens in use in **Used**. Compare them with the **Token usage** tab of the ALM web interface.

    *AbsInt token types in the Licenses window.*

5. Select a token type's number in **Used** to confirm that sessions arrived.

    The **Currently Consumed Licenses** window opens. It lists the open sessions of all license servers, so the AbsInt sessions can be on a later page. Each client connection that holds tokens appears with its username, **Workstation**, and **Start Time**, and **Consumed Tokens** shows how many tokens of the type it holds. Compare them with the **Connected clients** tab of the ALM web interface.

    *AbsInt sessions in Currently Consumed Licenses.*

## Troubleshooting

The Broker log holds the detail for each of these problems, in the `logs` folder of the Broker installation. The periodic data inquiry writes to `port-<port>-AbsInt.log`, and **Execute** writes to `broker-service.log`.

If AbsInt never appears as pending in EasyAdmin, confirm that the Broker reports to OpenLM SLM: other license managers on the same Broker update in EasyAdmin.

If the license server shows **Data error** with the message **Parsing failed. Data format is wrong. Can't convert xml.**, check whether a client is connected to the ALM. When no client is connected, OpenLM SLM shows **Data error** and **Used** drops to 0. The status returns at the first query after a client connects.

If the license server keeps old data, Broker cannot read the ALM and sends no data. To see the cause, open the AbsInt license manager in the Broker UI, select **Data Inquiry** on the **Commands** tab, and select **Execute**. Then check the following:

- The address ends in `/?xml`. Without it, the ALM returns its web page.
- The address opens in a browser on the Broker machine. If it doesn't, check the host name, the port (`42425` by default, not `42424` or `42426`), the firewall between Broker and the ALM host, and that the ALM runs and was not started with `--http-port 0`.
- For an `https://` address, the Broker machine trusts the ALM certificate.

## Known limitations

- Broker does not report denials, borrowed licenses, or license allocations, and does not upload usage history. Broker doesn't import the past token usage that the ALM web interface shows.
- Broker reads the current state of the ALM, so it can miss a session shorter than the watch interval. A session in OpenLM SLM starts at the first query that finds it, not when the user started the AbsInt tool.
- When no client is connected to the ALM, OpenLM SLM shows **Data error** for the license server, and **Used** drops to 0.
- When Broker cannot read the ALM, OpenLM SLM keeps showing the last status and counts of the license server.
- ALM user accounts, which the **Manage users** tab of the ALM defines for password-protected access, are not reported.
- Broker runs no commands for the ALM. It cannot start or stop the ALM.
