Skip to main content

Seisware

To monitor Seisware licenses in OpenLM Platform, configure OpenLM Broker. The Seisware license server writes every license checkout and check-in to a CSV log. OpenLM Broker reads that log on the license server machine and reports each session to OpenLM Platform.

Before you begin​

Confirm these prerequisites:

  • An OpenLM Platform account.
  • OpenLM Broker v22.4.15.656 or higher, installed on the Seisware license server machine.
  • The Broker approved in Broker Hub. OpenLM Platform accepts license manager data only from approved Brokers, so the Seisware entry does not reach Pending Servers until you approve the Broker.
  • The path of the Seisware license log on that machine. See How OpenLM Broker collects Seisware data for how to recognize the file.

What you can monitor​

OpenLM Broker monitors the following for Seisware:

LM Type in the BrokerCommandsLogsQuantityExpiration dateDeniedBorrowingAllocationsReport resolution
SeiswareNoYesNoNoNoNoNoStart time to the second, end time to the minute

For each checkout and check-in, Broker reports:

  • Feature name: always SeisWare. Broker reports all Seisware usage as one feature, whichever module the log names.
  • Username: the User column.
  • Workstation: the Machine column.
  • Start and end time: the Time column of the OUT row and of the IN row.
  • License type: Broker reports the feature as Floating.
  • Vendor: always SeisWare.

The Seisware license log holds no license totals or expiration dates. OpenLM Platform therefore reports Seisware usage without a license total. The log can hold DENIED rows, but Broker does not read them, so it does not report denials. Broker also does not report borrowed licenses or license allocations.

How OpenLM Broker collects Seisware data​

The following diagram shows how OpenLM Broker collects Seisware usage and sends it to OpenLM Platform.

Diagram: OpenLM Broker on the license server reads its log files and sends license data to OpenLM Platform over HTTPS on port 443. You see the data in the OpenLM Platform apps in a web browser. How OpenLM Broker collects Seisware usage

Broker runs on the Seisware license server machine and reads the license log there. It sends the license data to OpenLM Platform over HTTPS, on outbound port 443. Broker collects data in the following ways:

  • Log file: the Seisware license log is a CSV file, for example LicenseLog.csv, whose first row names the columns. Seisware writes one of two layouts. The later layout adds a Component column with the module name, for example Core or Geophysics:

    Status,User,Machine,MacID,Time,Elapsed,ID,InUse,Version,Description,Note1,Note2,Note3,Component
    OUT,jdoe,WS-1001,00-11-22-33-44-55,2026-10-19 08:12:40,0:00:00,10452,1,9.02,,,,,Core
    IN,jdoe,WS-1001,00-11-22-33-44-55,2026-10-19 11:47:05,3:34:25,10452,0,9.02,,,,,Core

    Broker reads the OUT and IN rows, and from them only the User, Machine, Time, and ID columns. It ignores every other row, including STARTUP and DENIED, and every other column, including Component, InUse, and Version.

  • Sessions: Broker matches each IN row to its OUT row by the ID column. In the later layout, a user who opens several modules gets one OUT row per module, all with the same ID. Broker reports them as one license in use, and ends the session at the first IN row with that ID.

  • First read: when Broker starts, it reads the whole log file to find the licenses that are checked out at that moment. From then on it reports each new OUT and IN row. Broker does not upload earlier usage history.

  • Commands: None run on a schedule. Broker does not connect to the Seisware license server, so the port that you enter in Broker only identifies the license server in OpenLM Platform.

Configure OpenLM Broker​

To configure OpenLM Broker for Seisware:

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

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

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

    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 Seisware alone.

  3. If the field is empty, enter the host name of the license server machine and select the save icon next to the field.

  4. Select License Managers, then Add License Manager.

  5. From LM Type, select Seisware.

  6. In Port, enter a port that no other license manager on this Broker uses, for example 30433, and select Add.

    Broker does not connect to this port. It only identifies the license server in OpenLM Platform. Broker refuses a port that another license manager already uses.

    The Add License Manager dialog with LM Type set to Seisware and port 30433 Add Seisware as a license manager

  7. On the Vendors tab, select Add Vendor, enter SeisWare, and select Continue.

    Broker reports every Seisware session with the vendor SeisWare, so use that name. The vendor appears in the list after you switch to another tab and back.

  8. On the Log Files tab, select Add Log File, then enter the following settings:

    • Log Type: Seisware Log, the only type for Seisware, which Broker selects for you.
    • Log Name: a name for the log, for example Seisware license log, in place of the suggested log.
    • Log Path: the full path of the Seisware license log. Select the search icon next to the field to browse to it.
    • Vendor: SeisWare, the vendor that you added on the Vendors tab. Broker selects it when it is the only vendor.

    The Add Log File dialog with Log Type Seisware Log, the log name Seisware license log, the path C:\Logs\LicenseLog.csv, and the vendor SeisWare Point Broker at the Seisware license log

  9. Select Continue, then select Save.

  10. Wait for Broker to read the log, every 10 seconds by default.

    Broker then reports Seisware to OpenLM Platform, and the license server reaches Pending Servers.

Approve Seisware in OpenLM Platform​

Broker reports Seisware with the OpenLM Generic protocol and names the license server after the Host that you set in the Broker UI. The pending entry is listed by that host name and the port that you entered, with License Manager Type shown as Seisware.

  1. Sign in to OpenLM Platform with the URL your administrator gave you.

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

  3. Select Pending Servers.

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

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

  5. Select that row, then select Approve And Merge.

  6. On the Approve License Server page, check the settings, then select Approve.

Verify the integration​

To verify that OpenLM Platform receives data from Seisware:

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

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

    Confirm that RSQT (Recent Successful Query Time), the last time OpenLM Platform received data from the license server, is recent.

  3. Open Licenses (Navigation, then Licenses and Features, then Licenses) and select Live Statistics.

    The feature SeisWare appears with License Type Floating and the number of licenses in use.

  4. Select the Used count to confirm that sessions arrived.

    The count opens the Usage page 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 connection.

Troubleshooting​

This section covers common problems when you monitor Seisware in OpenLM Platform.

Why does Seisware not reach 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.

Why does the approved license server show no usage?​

Confirm the following:

  • Log Path points at the Seisware license log, the CSV file whose rows start with OUT and IN.
  • The license manager type in the Broker is Seisware, and the log file type is Seisware Log.

What does "No session found for" mean in the Broker log?​

If the Broker log shows No session found for followed by a number, an IN row arrived for an ID whose session had already ended. That is expected for the later layout, where each module on the same ID writes its own IN row. The Broker log is in the logs folder of the Broker installation.

Known limitations​

These limits apply to Seisware monitoring:

  • Broker does not report license totals, expiration dates, denied requests, borrowed licenses, or license allocations, and does not upload usage history. Usage in OpenLM Platform starts when you configure the license manager.
  • All Seisware modules arrive as one feature, SeisWare. OpenLM Platform does not show which module a user opened.
  • Broker reports rows that share an ID as one license in use, and ends the session at the first IN row with that ID, even while other modules on that ID are still checked out.
  • An OUT row that never gets a matching IN row keeps its session in use in OpenLM Platform, also after Broker or the license server restarts. Broker ignores the STARTUP rows and rebuilds the open sessions from the whole log file each time it starts.
  • Broker does not check whether the Seisware license server is running. OpenLM Platform shows the license server as up while Broker reports it.

The documentation team might draft this page using a large language model. A technical writer reviews every page and verifies it against the product before publishing it. A human makes the final decision.