Phase2Phase
Follow these steps to monitor Phase2Phase licenses with OpenLM. Phase2Phase is the OpenLM name for the licensing service of Phase to Phase, the Dutch developer of the Vision Network Analysis, Vision Cable Analysis, and Gaia LV Network Design software for electricity networks. The licensing service runs on a server in your network and hands out Vision, Gaia, and Cable licenses to the clients. OpenLM Broker reads the log of the licensing service on that server and reports each license grant and release to OpenLM SLM.
Requirements
Before starting, make sure you have:
- OpenLM SLM installed on a machine in your organization, or a Software License Management Cloud (SLMC) account.
- OpenLM Broker v25.7.7.711 or higher, installed on the licensing service machine and reporting to OpenLM SLM. Broker lists Phase2Phase Server as a license manager type from v25.2.6.1326, but versions before v25.7.7.711 read the log only on a machine whose system language is English. On a Dutch or other non-English machine, they fail to parse the timestamp of every line and report no usage.
- Vision, Gaia, or Cable licenses served by the Phase to Phase licensing service,
LicensingService.exe, running as a Windows service. - Access to the licensing service machine, to find the folder that holds its log files.
Monitoring capabilities
The current monitoring capabilities for Phase2Phase through OpenLM Broker are:
| LM Type in the Broker | Commands | Logs | Quantity | Expiration date | Denied | Borrowing | Allocations | Report resolution |
|---|---|---|---|---|---|---|---|---|
| Phase2Phase Server | No | Yes | Yes | No | No | No | No | Seconds |
For each license grant and release, Broker reports:
- Feature name: the product name in the log line,
Vision,Gaia, orCable. The product version in the line, for exampleGaia 7.15, is not part of the feature name, so all versions of a product count against the same feature. - Username: the second value in the client identification of the line, for example
jdoeinWS-1001,jdoe,396258. Older client versions write no username. Broker reports their sessions under the usernameGeneralUser, so that the usage count stays right. - Workstation: the first value in the client identification, the computer name.
- Start and end time: the time of the grant and release lines, to the second.
- Vendor: the vendor that you select for the log file.
- Quantity: the total of each product, from the line that the licensing service writes when it starts, for example
maximaal 61 Vision-licenties.
The log holds no expiration dates for the licenses and no denied requests, so expiration dates, denials, borrowed licenses, and license allocations are not available.
How OpenLM interfaces with Phase2Phase
How OpenLM collects Phase2Phase usage
Broker runs on the licensing service machine, reads the licensing service log there, and sends the license data to OpenLM SLM.
-
Log file: The licensing service writes one log file per month, in the folder that holds
LicensingService.exe, for exampleLicensingService 2026-10.log. The lines are in Dutch. Broker reads 4 kinds of line:10/5/2026 8:02:11 AM: maximaal 20 Vision-licenties; maximaal 30 Gaia-licenties; maximaal 5 Cable-licenties.10/5/2026 8:14:37 AM: aanroep van WS-1001,jdoe,396258 voor Gaia 7.15: Gaia-licentie toegekend; 1 licenties in gebruik. (32177004,0,1,101 ms)10/5/2026 11:47:05 AM: aanroep van WS-1001,jdoe,396258 voor Gaia 7.15: Gaia-licentie vrijgegeven; nog 0 licenties in gebruik. (33934554,0,0,101 ms)10/5/2026 3:39:16 PM: Vision-licentie van WS-1002,asmith,197094 timed-out en vrijgegeven; nog 3 licenties in gebruik.The first line, which the licensing service writes when it starts, gives Broker the license totals. A
toegekendline is a license grant, and Broker opens a session for it. A re-grant,opnieuw toegekend, counts as a grant too. Avrijgegevenline is a release, and so is thetimed-out en vrijgegevenline that the licensing service writes when a client stops confirming its license. Broker ignores every other line, including thebevestigdlines with which clients confirm their license, thestand-bysummaries of licenses in use, and theservice gestart,service gestopt, andhoudbaar totlines about the service itself. -
Sessions: Broker matches each release to its grant by the computer name, the username, the session number, and the product. It compares the number of licenses in use in each line with its own count and writes a warning to the Broker log when they differ.
-
Service restart: When Broker reads a totals line, it closes every open session, because the licensing service freed all licenses when it stopped, and takes the new totals from the line.
-
First read: When you add the log file, Broker reads the current log file once, from the start, to find the licenses that are in use at that moment and the totals. From then on it reports each new grant and release. Broker does not upload earlier usage history.
-
Monthly files: With Watch files by pattern on, Broker moves to the next month's file after it has read the current file to its end. The new file name must differ from the old one only in its digits, which is the case for
LicensingService 2026-10.logandLicensingService 2026-11.log. -
Commands: None run on a schedule. Broker does not connect to the licensing service, so the port that you enter in Broker only identifies the license server in OpenLM.
Find the licensing service log
Broker sees only what the licensing service writes to its log, so find the log first.
-
On the licensing service machine, open the folder that holds
LicensingService.exe.Phase to Phase has no default folder for the service. The log files are in the folder that
LicensingService.exewas extracted to before it was installed withlicensingservice /install. Windows Services lists the service as Phase to Phase licensing service, and its properties show the path. -
Open the log file for the current month,
LicensingService <year>-<month>.log, and search fortoegekend.If no line matches, no client has taken a license from this licensing service since the start of the month.
-
Note the TCP port of the licensing service.
The Vision and Gaia clients name the server and this port in their options. Broker does not connect to the port, but OpenLM identifies the license server by it.
OpenLM Broker configuration
Install OpenLM Broker on the licensing service machine and confirm that it reports to OpenLM SLM before starting these steps.
-
Open a browser on the licensing service machine and go to the Broker web UI at http://localhost:5090/.
-
On the License Managers page, check Host.
OpenLM lists the license server under this host name, and the field holds the host for every license manager on the page, not for Phase2Phase alone. If the field is empty, enter the host name of the licensing service machine and select the save icon next to the field.
-
Go to License Managers → Add License Manager.
-
From LM Type, select Phase2Phase Server.
-
In Port, enter the TCP port of the licensing service, and select Add.
Broker does not connect to this port, so any port that no other license manager on this Broker uses works. Broker refuses a port that another license manager already uses.
Add Phase2Phase as a license manager -
On the Commands tab, leave every field empty.
Broker runs no commands for Phase2Phase, and Use the operating system start/stop commands is off.
-
On the Vendors tab, select Add Vendor, enter the vendor name that you want OpenLM to show, for example
Phase to Phase, and select Continue.The new vendor appears in the list after you switch to another tab and back.
-
On the Log Files tab, select Add Log File, and fill in the dialog:
- Log Type: Usage Log, the only type for Phase2Phase.
- Log Name: a name for the log, for example
Licensing service log. - Log Path: the full path of the current month's log file, for example
C:\PhaseToPhase\LicensingService\LicensingService 2026-10.log. Select the search icon next to the field to browse to it. - Vendor: the vendor that you added on the Vendors tab.
- Under Advanced, turn on Watch files by pattern, so that Broker moves to the next month's file. Leave Encoding and Read File Every (Sec) as suggested.
Point Broker at the current licensing service log -
Select Continue, then select Save.
OpenLM SLM configuration
Automatic configuration through EasyAdmin
If the preceding steps are complete, Broker reads the log every 10 seconds, by default, and reports Phase2Phase to OpenLM SLM. Approve the license server in EasyAdmin:
-
Open EasyAdmin (
http://<Server IP>:5015) and go to Start → Widgets → License Manager - Servers. -
Select the There are N servers pending approval link at the top of the widget.
The Administration - License Manager Servers window opens, with the pending entries at the top of the list.
-
Find the pending Phase2Phase entry, with the host name and the port that you configured in Broker, and select the edit icon at the end of its row.
Broker reports Phase2Phase with the OpenLM Generic protocol, so its Type is OpenLM Generic.
-
Optionally rename the connection in Display name, confirm the Host Name and Port, and select APPROVE.
Manual configuration through EasyAdmin
If automatic configuration fails:
-
Go to Start → Administration → License Manager Servers.
-
Select Add LM.
-
In Display name, enter a name for the connection, for example
Phase2Phase. -
From Type, select OpenLM Generic.
Use Broker turns on.
-
In the row under Host Name, Port, and Time Zone, enter the host name and the port exactly as configured in Broker for Phase2Phase, and select a time zone.
-
Select SAVE.
Verify your configuration
- Open EasyAdmin in your browser.
- Go to Start → Widgets → License Manager - Servers.
- Confirm that the Phase2Phase license server shows the Status Up to date.
- Go to Start → Widgets → Feature Usage Status and confirm that Vision, Gaia, and Cable appear with their totals in Quantity and the number of licenses in use in Used.
- Go to Start → Reports → License Activity, select Include Current Activity, and select Apply. Confirm that each license grant appears with its username and workstation.
Troubleshooting
If Phase2Phase 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 is approved but shows no usage, check these points:
- Log Path points at the current month's file, and Watch files by pattern is on. With the option off, Broker keeps reading the month's file that you selected after the licensing service has moved on to the next one.
- The log holds
toegekendlines. If it does not, the clients do not take their licenses from this licensing service. - The Broker version is v25.7.7.711 or higher. The Broker log of an earlier version on a non-English machine repeats
Phase2PhaseLogReader - Error parsing linewithDateTimeParseExceptionfor every line.
If a product shows usage but no total, the current month's file holds no totals line. The licensing service writes it only when it starts, so the total appears after the next restart of the service.
If the Broker log repeats There is a mismatch between inuse from log, Broker counts a different number of open sessions than the licensing service. The usual cause is a grant that happened before the current month's file started. See Known limitations.
The Broker log holds the detail, in the logs folder of the Broker installation.
Known limitations
- Broker does not report expiration dates, denied requests, borrowed licenses, or license allocations, and does not upload usage history. Usage in OpenLM starts when you configure the license manager.
- When Broker starts, it rebuilds the open sessions from the current month's log file only. Licenses granted before that file started are missing from OpenLM until they are released and granted again.
- Broker learns the license totals from the line that the licensing service writes when it starts. Until the current month's file holds such a line, OpenLM shows usage without a total.
- Sessions of older client versions, which write no username, are reported under the username
GeneralUser. - Broker does not check whether the licensing service is running. OpenLM shows the license server as up while Broker reports it.
- Broker reads the log on the machine where it runs. Install a Broker on each licensing service machine that you want to monitor.
- Multiple server redundancy is not available. Leave Is Triad Configuration unchecked in EasyAdmin.
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.