OpenLM Platform architecture

To plan a deployment, see which OpenLM Platform components you install, where they send data, and how you read the results. If you're setting up OpenLM Platform for the first time, start with Prerequisites for OpenLM Platform.

Components you install

Each component runs close to the data it collects and sends what it collects to OpenLM Platform:

Component	Where it runs	What it collects
Workstation Agent	End-user workstations	Application and executable usage on each machine
OpenLM Broker	Your license servers	License manager data. You manage Brokers from Broker Hub.
SaaS Agent	A Windows machine	Subscription and allocation data from your SaaS accounts
Directory Synchronization Agent (DSA)	A Windows machine	Users, groups, and computers from your directory, for Directory Sync

For SaaS platforms, Cloud Broker also collects licensing data. It's an OpenLM Platform service, so you don't install anything for it.

Where the data goes

Each component sends its data to your organization's OpenLM Platform address, its fully qualified domain name (FQDN), over outbound HTTPS on port 443. Allow that traffic through your firewalls and proxies, as Prerequisites for OpenLM Platform describes. The OpenLM Broker also needs network access to your license manager servers.

What OpenLM Platform does with the data

OpenLM Platform combines what the components send, so each license session carries its user, project, and license server details. It keeps the results for your reports, dashboards, and alerts.

Where you read the results

Read the results in OpenLM Platform or in your own tools:

• BI reports and the reports in each app show usage, denials, and license utilization.
• The Reporting Data API lets your own applications read the same reporting data.

Running OpenLM Platform yourself

If you run OpenLM Platform on your own infrastructure, Architecture and components describes what you deploy and operate.