VastoLM

Follow these steps to monitor VastoLM licenses in OpenLM Platform. VastoLM is the license manager that VASTO.Lab uses to license its software, such as Vasto.FILL, from a license server on your network. OpenLM Broker runs vlmdiag, the diagnostic utility that ships with VastoLM, on a schedule and reports license totals, the licenses in use, and the users who hold them to OpenLM Platform. Broker runs on the license server machine and reads the VastoLM server on that machine.

Before you begin

Confirm these prerequisites:

• OpenLM Platform.
• OpenLM Broker v26.10.13.929 or higher, installed on the VastoLM license server machine. Earlier Broker versions do not list VastoLM as a license manager type.
• The Broker approved in Broker Hub. OpenLM Platform accepts license manager data only from approved Brokers, so the VastoLM entry does not reach Pending Servers until the Broker itself is approved.
• Access to the license server machine, to find the VastoLM port and the folder that holds vlmdiag.exe.

What you can monitor

OpenLM Broker monitors the following for VastoLM:

LM Type in the Broker	Commands	Logs	Quantity	Expiration date	Denied	Borrowing	Allocations	Report resolution
VastoLM	Yes (vlmdiag)	No	Yes	Yes	No	No	No	Seconds

On every data inquiry, the Broker reports the following:

• Feature name: the name of each licensed feature, for example Vasto.FILL.
• Total: the Total Licenses Issued of the feature.
• In use: the Total Licenses in Use of the feature.
• Expiration date: the Valid Until date of the feature, converted from the license server's local time to UTC.
• Username: the user of each checkout.
• Workstation: the Client Hostname of each checkout.
• Start time: the Checkout Time of each checkout, converted to UTC.
• License type: Broker reports every feature as Floating.
• Vendor: Broker reports VASTO.Lab unless you add a different vendor on the Vendors tab.

License denials, borrowed licenses, and license allocations are not available for VastoLM. vlmdiag does not report denied license requests.

How OpenLM Broker interfaces with VastoLM

When you configure a VastoLM port, Broker fills in only the settings in this list. The remaining license manager settings stay empty:

• Commands: status and data_inquiry, which the Broker UI shows as Status and Data Inquiry. Both run vlmdiag from the Executable path of the license manager, against the VastoLM port:

  "{$path}vlmdiag" {$port} -s
  "{$path}vlmdiag" {$port} -a

  • Status (-s): Broker reports the license server as up only while the output says lmgrd Status Running. A suspended VastoLM server grants no new licenses, so Broker reports it as down.
  • Data Inquiry (-a): lists the server, every licensed feature with its totals and expiration date, and a checkout record for each license in use.

  vlmdiag connects to the VastoLM server on the same machine, which is why Broker runs on the license server.

• License file: None. Broker does not read the VastoLM license configuration file.

• Log file: None. Broker does not read the VastoLM log (vastolicense.log), and the Log Files tab stays empty.

• Polling: The data inquiry runs every 55 seconds by default. Checkouts that start and end between two runs do not reach OpenLM Platform.

The data inquiry reads output like this example:

Assumed: server running on localhost

Server Hostname       vlm01
Server Port           26765
lmgrd Status          Running
lmgrd Version         VASTO.Lab LAN/NODELOCK License Manager (R55)

Feature Name          Vasto.FILL
Total Licenses Issued 10
Total Licenses in Use 1
Valid Until           08-mar-2027 23:59:59 (Server time)

Username              jdoe
Client Hostname       WS-1001
Application PID       4120
Checkout Time         30-sep-2026 08:59:22 (Server time)

Find the VastoLM port and vlmdiag

Broker needs the port that VastoLM listens on and the folder that holds vlmdiag.exe.

1. On the license server, open the VastoLM installation folder.

   vlmdiag.exe is in its intel_64 subfolder, next to vlm.exe, for example C:\Vasto.LM\intel_64\.

2. In the same folder, open the license configuration file in a text editor.

   The file is license.conf unless your VastoLM uses a different name, set as CONFIGFILE in vlm-service.cmd. The port is the PORT value:

   # Editable parameters
   PORT    26765

3. Open a command prompt in the intel_64 folder, and run vlmdiag with that port:

   vlmdiag 26765 -a

   The output lists the server and its features, as in the example in How OpenLM Broker interfaces with VastoLM.

   • There is no connection to 26765@127.0.0.1: VastoLM is not running on this machine, or it listens on a different port.
   • The vlmdiag usage text instead of a feature list: your VastoLM release does not support the -a option. Broker was built for VastoLM R55, so ask VASTO.Lab for a release that supports it.

Configure OpenLM Broker

To add VastoLM to the Broker:

1. Open the Broker UI for the Broker on the license server.

   On the license server itself, open http://localhost:5090/. Local access needs no credentials. From any other machine, open Broker Hub in OpenLM Platform and select the Broker UI icon of that Broker, which opens the interface with the remote access token handled for you.

2. On the License Managers page, check Host.

   OpenLM Platform lists the license server under this host name, and the field holds the host for every license manager on the page, not for VastoLM alone. If the field is empty, enter the license server's host name and select the save icon next to the field.

3. Select License Managers, then Add License Manager.

4. From LM Type, select VastoLM.

   Add VastoLM as a license manager

5. Enter the VastoLM port, the PORT value from the license configuration file, and select Add.

6. On the Commands tab, enter the folder that holds vlmdiag.exe in Executable path, for example C:\Vasto.LM\intel_64\, or select the search icon next to the field to browse to it. The command lines show this path after you save.

   The Executable path and the default Data Inquiry

7. Under Periodic commands, select Status and then Data Inquiry, and keep their default command lines.

8. Leave Watch interval (sec) at 55 seconds, or set the polling interval you want. Timeout (sec), 60 seconds by default, limits how long Broker waits for vlmdiag to answer.

9. Leave the Vendors and Log Files tabs empty. Add a vendor only if you want OpenLM Platform to show a vendor name other than VASTO.Lab.

10. Select Save.

11. Reopen the VastoLM license manager from the License Managers list, go to the Commands tab, select Data Inquiry, and select Execute to test it.

    A successful test returns the license server XML, with a feature for each VastoLM feature and a user entry for each checkout. Broker refuses Execute on a license manager that you have never saved, and answers Need to save first in order to execute command.

12. Wait for the next periodic data inquiry.

    Execute only tests the command inside the Broker UI and sends nothing to OpenLM Platform. Broker reports VastoLM to OpenLM Platform on the periodic data inquiry, so the license server reaches Pending Servers about a minute after you save.

Approve VastoLM in OpenLM Platform

To approve the VastoLM license server, find its row in Pending Servers. Broker reports VastoLM with the OpenLM Generic protocol and names the license server after the Host you set in the Broker UI, so the pending entry is listed by that host name and the port you entered, with License Manager Type set to VastoLM.

1. Sign in to OpenLM Platform.

2. Select Navigation (the grid icon in the OpenLM Platform header), then Licenses and Features, then License Servers.

3. Under Management, select Pending Servers.

4. Find the row whose Host Name and Port match the license manager you configured in Broker.

   Its License Manager Type is VastoLM, and Source names the Broker.

5. Select that row, then select Approve and merge.

Verify the integration

To confirm that OpenLM Platform receives VastoLM data:

1. In OpenLM Platform, open License Servers and, under Operational, select Live Servers Statistics.

2. Find the row for the host and port you configured, and confirm that Status is Up.

   Confirm that RSQT (Recent Successful Query Time), the last time OpenLM Platform read licenses and usage from the server, is recent, and that Quantity and Used carry numbers.

3. Select Navigation, then Licenses and Features, then Licenses, and select Live Statistics.

   Each VastoLM feature appears as its own row, with License Type Floating, the Total and Used counts, and the expiration date. Compare them with the output of vlmdiag <port> -a on the license server.

4. Select a feature's Used count to confirm that sessions arrived.

   The count opens the Usage app on Currently Consumed Licenses, where each checkout appears with its username, workstation, and start time.

Note

It can take up to 3 minutes for the status to update for a new connection.

Troubleshooting

If VastoLM never reaches Pending Servers, open Broker Hub and confirm that this Broker appears under Brokers with status Up, and not under Pending Brokers. OpenLM Platform accepts license manager data only from approved Brokers.

If the Broker is approved and up, or if VastoLM appears with no features, go back to the Commands tab in the Broker UI, select Data Inquiry, and select Execute. Compare the result with this list:

• There is no connection to <port>@127.0.0.1: VastoLM is not running on the Broker machine, or the license manager's port is not the PORT value of the license configuration file. Correct the port, or start VastoLM.
• An error that the system cannot find the file: Executable path does not point at the folder that holds vlmdiag.exe. Set it to the intel_64 folder of the VastoLM installation.
• The vlmdiag usage text: your VastoLM release does not support the -a option. See Find the VastoLM port and vlmdiag.

If features arrive but the license server shows as down, VastoLM is suspended. vlmdiag <port> -a then shows a lmgrd Status other than Running. Resume VastoLM as described in the VastoLM user guide (VLM_Local_for_Windows.pdf, section 4.3) that comes with VastoLM.

The Broker log holds the detail, in the logs folder of the Broker installation. A manual Execute writes to broker-service.log, and the periodic commands write to port-<port>-VastoLM.log.

Known limitations

These limits apply to VastoLM monitoring:

• Broker does not report license denials, borrowed licenses, or license allocations, and does not upload usage history. Usage in OpenLM Platform starts when you configure the license manager.
• Broker reads the VastoLM server on the machine where Broker runs. Install a Broker on each VastoLM license server that you want to monitor.
• Broker reads the current state of the license server, not a log, so it sees only the checkouts that are open when the data inquiry runs. Broker can miss a checkout shorter than the watch interval.
• Broker converts Valid Until and Checkout Time from the license server's local time with the time zone of the Broker machine, which is the license server itself.
• Broker was built for the vlmdiag output of VastoLM R55.
• Broker monitors VastoLM license servers on your network. VASTO.Lab's online licensing, served from VASTO.Lab's own servers, is not covered.
• Multiple server redundancy is not available for VastoLM.