After you install all components and connect a license manager, use this checklist to confirm that data flows through the system.
Verification checklist
Work through these checks in order:
Broker is approved and up Open Broker Hub . After you install a Broker, it first appears under Pending Brokers . Approve it, and it then appears under Brokers with status Up . If it does not appear at all, check that the authorization file was imported correctly and that the Broker machine has internet access on port 443.
License server is approved Open License Servers and, under Operational , select Live Servers Statistics . Your approved license server should appear with status Up . If the status is Down or Data error , verify the Broker configuration: the port, the license file path, and the vendor daemon name.
Workstation Agent is reporting Open Agent Activity (Navigation , then Agents , then Agent Activity ), which opens in Agents Hub. Installed agents should appear in the list with an online status. If an agent does not appear, verify the authorization file and confirm that the workstation has internet access on port 443.
DSA is syncing Open Directory Sync . Confirm the Directory Sync Agent (DSA) is approved under Agents and that user and group data from your directory is syncing. If the sync is not running, verify that the DSA machine can reach your directory source. For a DSA that doesn't appear or can't sync, see Install DSA and the Sync History in Directory Sync.
SaaS Agent is reporting Open Broker Hub and select the SaaS Agents tab. Your agent is in the list, and its host name opens the services it reports. If it is missing, see Troubleshoot SaaS Agent .
AI Proxy is reporting Open Broker Hub and select the AI Proxy tab. Your AI Proxy is in the list, with its Status and Last Update . Usage reaches the AI FinOps reports about 5 minutes after a client sends a request. See Confirm that data reaches AI FinOps .
OpenLM Router is connected Data appears in reports Open the Usage report (Navigation , then Licenses and Features , then Usage ). License usage data takes a few minutes to appear after the first collection cycle. If no data appears after 15 minutes, check Broker Hub for errors and confirm the license server is actively serving licenses.
Troubleshooting
The following table lists symptoms, their likely causes, and the actions to take:
Symptom Likely cause Action Broker not visible in Broker Hub Authorization file missing, deleted, or its secret was reset Re-generate the authorization file in Identity and re-import it. License server shows Down or Data error status Broker cannot reach the license server Check network connectivity and verify the port and host name in the Broker configuration. Agent not visible in Agent Activity Firewall blocking outbound HTTPS Verify that the workstation allows outbound traffic on port 443. No data in reports Collection cycle is not complete Wait 15 minutes. If data still does not appear, check Broker Hub and Agent Activity for error messages.
What's next
When the checklist passes, OpenLM Platform is collecting data. Explore these areas to get more value from the system:
Homepage : Tour the dashboard you land on after signing in.
BI Reports : Build dashboards and generate compliance reports.
License Access Control : Define access rules that control who can use which licenses.
Alerts : Get notified when custom licensing conditions are met.
Compliance : Monitor license compliance status.
Connectors catalog : Add more license managers to expand your coverage.
Install another Broker : Every additional license server needs its own Broker before its licenses appear in OpenLM Platform.
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.