Infrastructure minimal hardware requirements

• Dual-core CPU
• 4 GB memory (Recommended – 8 GB)
• Microsoft Desktop Runtime 3.1.3 or higher and ASP.NET Core Runtime 3.1.3 or higher (official download links)
• .NET Framework 4.7.2 Runtime to run the Server installer (official download links)
• Static MAC address (Cloud-based servers must use ENI)

We also recommend consulting the optimal configuration guide for more in-depth information.

The following ports should be open (both inbound and outbound) on the OpenLM Server:

 

• 5000 (to be opened on license servers with the Brokers as well)
• 5015 (to be opened on license servers with the Brokers as well)
• 5005 (if using ServiceNow integration)
• 7026 (if using DSS for AD Sync)
• 8081 (if using DSA for AD Sync)
• 53555 (used by Personal Dashboard)
• 27080 (if using Application Manager)
• 8888 (for Report Scheduler)
• 1433 (if using MS SQL – to be opened on the database server as well)
• 3306 (if using MySQL – to be opened on the database server as well)

 

HTTP SERVER
OpenLM is provided with an integrated HTTP Server – LightTPD
OpenLM can also be configured to work with most standard HTTP servers. We tested the system with:
Apache HTTP Server version 2* – Fully supported
Microsoft IIS 6, 7, 7.5, 10 – Fully Supported.
Other HTTP servers should also work.

 

OpenLM Server Supported Operating Systems
OpenLM can monitor both Windows’ and Unix / Linux resident license server systems.
The OpenLM Server can be installed on a Windows’ machine only.

OS VERSION	OPENLM SERVER
Windows 7 SP1 32 bit	Tested, Fully Supported
Windows 7 SP1 64 bit	Tested, Fully Supported
Windows 8.1	Tested, Fully Supported
Windows 8 32 bit	Not Supported
Windows 8 64 bit	Not Supported
Windows 10	Tested, Fully Supported
Windows Server 2008 R2 32 bit	Not Supported, deprecated by Microsoft.
Windows Server 2008 R2 SP1 64 bit	Not Supported, deprecated by Microsoft.
Windows Server 2008 SP2 32 bit	Not Supported, deprecated by Microsoft.
Windows Server 2008 SP2 64 bit	Not Supported, deprecated by Microsoft.
Windows Server 2012 64 bit	Tested, Fully Supported
Windows Server 2012 R2 64 bit	Tested, Fully Supported
Windows Server 2016 64 bit	Tested, Fully Supported
Windows Server 2016 R2 64 bit	Tested, Fully Supported
Windows Server 2019	Tested, Fully Supported

Supported Databases
OpenLM is provided with an embedded Firebird DB, which is installed as part of the OpenLM Server installation. OpenLM also supports external databases. The following database types are supported:

MS SQL Server:
Versions 2012, 2014, 2016, 2017, 2019 are tested and supported.
Version 2005 support has been discontinued in OpenLM Server version 3.1 due to Microsoft’s deprecation.

Additionally:

• Set the collation to case-sensitive (CS)
• It is recommended to connect using an SQL Server Authenticated user
• Make sure the user is permitted to read, write and change the database (db_owner)

Firebird Server:
Version 2.5.5 is tested and supported.

MySQL Server:
Version 5.7 is tested and supported. OpenLM Server v4.4+ supports MySQL 8.

1. Use this creation script:

CREATE SCHEMA `openlm_database_name` DEFAULT CHARACTER SET utf8mb4;

2. On the blank database, run the script

SET SQL_SAFE_UPDATES = 0

Oracle DB
Not supported.

 

OpenLM EasyAdmin
OpenLM EasyAdmin is the OpenLM management interface. It is applicable to any standard browser. We tested it on the following browser types:

Mozilla Firefox
It is recommended to use the latest version.

Microsoft Edge
It is recommended to use the latest version.

Google Chrome
It is recommended to use the latest version.

 

The OpenLM Router is implemented as a Java application. As such it can run on any operating system that supports Java; e.g. Windows or Unix / Linux. The required Java version is 8.

Will be discontinued on December 31st, 2021.

Broker System Requirements
OpenLM Broker is designed to run on any platform supported by the license server.
OpenLM Broker requires Java to run.  It is recommended to use the latest release of Java 8 or 11.  OpenJDK is supported.
.NET Framework 4.5.2 or higher is required to run the installer on Windows machines.
Memory: 4 GB of RAM (recommended 8GB)

 

OpenLM Broker supported platforms

 

 

The OpenLM Applications Manager should be installed on the same machine as the License Server (e.g. FLEXlm), adjacent the OpenLM Broker. It is implemented as a Java application, and as such it can run on any operating system that supports Java; e.g. Windows or Unix / Linux.

.NET Framework 4.5.2 or higher is required to run the installer on Windows machines.

We recommend consulting the optimal configuration guide for Applications Manager for a more in-depth answer as to system requirements.

 

 

OpenLM Reporting Hub System Requirements

The OpenLM Reporting Hub generally requires a Windows or Linux operating system, with the following minimal hardware requirements:

For small databases (under 100Gb):

• RAM – 8GB
• CPU – 2.1 Ghz+ Dual-Core
• Storage – At least twice the size of your current OpenLM database, with room for growth.

For large databases (over 100Gb):

• RAM – 16GB
• CPU – 2.1 Ghz or higher Quad-Core
• Storage – At least twice the size of your current OpenLM database, with room for growth.

 

Supported source database types:

• Firebird (OpenLM embedded database)
• SQL Server
• MySQL

Supported destination database types:

• PostgreSQL (Reporting Hub embedded database)
• SQL Server
• MySQL

 

Component Requirements

Data Integration 

Firebird Server (optional) 

Jave JDK 11 

Postgres Server 

Power BI Desktop

 

Infrastructure requirements
Minimum hardware requirements:
– a dual-core CPU
– 2 GB of RAM

Windows:
.NET Framework 4.7.2 Runtime to run the installer
Tested on Windows 10, Ubuntu 18, Ubuntu 20, CentOS 8.

End-User Services is a self-contained .NET Core app – no runtimes are required to run the actual software since all files and libraries are bundled with the installers.
End-User Services needs to be able to connect to these TCP ports: 5015 (default for OpenLM Server), 5020 (OpenLM Identity, if used) and listen to TCP 53555 (can be changed in appsettings.json).
Outbound connections are required for Browser notifications.

 

 

Infrastructure requirements
Minimum hardware requirements:
– a dual-core CPU
– 2 GB of RAM

Windows: .NET Framework 4.7.2 Runtime is required to run the installer.
Linux Agent requires pre-installed libXScrnSaver library when installing on CentOS, when using the tar.gz.
Tested on Windows 10, Ubuntu 18, Ubuntu 20, CentOS 8.

The agent is a self-contained .NET Core app – no runtimes are required to run the actual software since all files and libraries are bundled with the installers.
The agent needs to be able to connect to these TCP ports: 5015 (default for OpenLM Server), 27080 (Applications Manager), 53555 (OpenLM End-User Services), 5020 (OpenLM Identity, if used)

 

 

Infrastructure requirements
• .NET Framework 4.6.2 or higher;
• .NET Framework 3.5 for ArcGIS, versions older than 10.4.

OS VERSION	OPENLM AGENT
Windows 7 32 bit	Tested, Fully Supported
Windows 7 64 bit	Tested, Fully Supported
Windows 8.1	Tested, Fully Supported
Windows 8 32 bit	Not Supported
Windows 8 64 bit	Not Supported
Windows 10	Tested, Fully Supported
Windows Server 2008 R2 32 bit	Tested, Fully Supported
Windows Server 2008 R2 SP1 64 bit	Tested, Fully Supported
Windows Server 2008 SP2 32 bit	Not Supported.
Windows Server 2008 SP2 64 bit	Not Supported.
Windows Server 2012 64 bit	Tested, Fully Supported
Windows Server 2012 R2 64 bit	Tested, Fully Supported
Windows Server 2016 64 bit	Tested, Fully Supported
Windows Server 2016 R2 64 bit	Tested, Fully Supported

 

 

OpenLM Agent support for terminal servers
OpenLM Agent is built to work on any terminal server software (e.g. Microsoft Terminal Server, Citrix). If you have installed the OpenLM Agent on a terminal server software other than the ones elaborated below – please update us.

TERMINAL SERVER SOFTWARE	OPENLM AGENT
Microsoft Terminal Server	Home Tested, Fully Supported
All versions Citrix terminal server	Home Tested, Fully Supported

OPENLM for ESRI ArcGIS (Arcview, ArcEditor, ArcInfo)
OpenLM for ESRI ArcGIS provides dedicated functionality for ESRI’s ArcGIS Software. The OpenLM Agent supports ESRI ArcGIS Versions 9.3, 10, 10.1, 10.2.2, 10.3, 10.3.1, 10.4.1, 10.5, 10.6, 10.6.1, 10.7 as well as ArcGIS Pro 2.0 – 2.3.3 . For versions older than 10.4 of ArcGIS, it is necessary to install .NET Framework 3.5.

 

 

OPENLM for Autodesk
OpenLM provides dedicated functionality for Autodesk software. OpenLM supports Autodesk Versions 2007 through 2019.
OpenLM for Autodesk software supports any platform based on Autodesk Autocad. It is designed to provide full functionality with any other Autodesk software, e.g. Autodesk Inventor, Autodesk Architect, Autodesk Civil 3D, etc.

OpenLM Directory Synchronization Service & Synchronization Agent System Requirements

 

Hardware:

• Dual core CPU
• 4 GB memory (Recommended – 8 GB)

 

Platform: Windows.

Dependencies: .NET Framework 4.5.2 or higher is required to run the installer.

DSS & DSA are self-contained .NET Core applications – no runtimes are required to run the actual software as all files and libraries come bundled with the default installers.

Port configuration:
Port 8081 must be free when installing DSA. If it is occupied and you get an error during the installation stage, edit the kestrel.config file in the DSA installation folder (C:\Program Files (x86)\OpenLM\OpenLM Directory Synchronization Agent), change the port number and restart the Directory Synchronization Agent service.

Additionally, if installing DSS and DSA on separate machines from OpenLM Server, you will have to make sure that proper firewall rules are set for the application ports:

OpenLM Server machine: inbound for 5015, outbound for 7026
DSS machine: both inbound and outbound for 7026
DSA machine: outbound for 7026

Supported directory services:

OpenLM DSS synchronizes with the following LDAP directory services:

• Microsoft Active Directory
• NetIQ eDirectory
• ApacheDS

 

Supported databases:

An embedded Firebird DB is provided as part of the OpenLM DSS installation. DSS can also be configured to use external databases. The following database types are supported:

• MS SQL Server:
  Versions 2012, 2014, 2016, 2017, 2019 are tested and supported.
• Firebird Server:
  Version v2.5.5 is tested and supported.
• MySQL Server:
  MySQL v5.7 and 8 are supported.

 

If you choose to go with an external database, you must create a new empty database and upgrade the database schema following these instructions before you can use it.

Note that collation must be enabled. Both case-sensitive and case-insensitive databases are accepted.

To create an empty MS SQL database, use these scripts for a case sensitive/insensitive database respectively:

CREATE DATABASE DSS_Linux49 COLLATE Latin1_General_CI_AS

CREATE DATABASE DSS_Linux49 COLLATE Latin1_General_CS_AS

 

To create an empty MySQL 8 database, use these scripts for a case sensitive/insensitive database respectively:

CREATE DATABASE `DSS_Linux49 ` /*!40100 DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_as_ci */;

CREATE DATABASE `DSS_Linux49 ` /*!40100 DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_as_cs */;

OpenLM DSS UI
OpenLM DSS UI is the management interface. It is applicable to any standard browser. We tested it on the following browser types:

Mozilla Firefox
It is recommended to use the latest version.

Microsoft Edge
It is recommended to use the latest version.

Google Chrome
It is recommended to use the latest version.

Other considerations:

• If you previously used the integrated LDAP solution that came with OpenLM Server v4.x and you did not experience performance issues or processing hang-ups, you can install DSS & DSA on the same machine as OpenLM Server.
• For systems that anticipate a high load and a huge amount of synchronization data (tens of thousands of users), it is possible to install DSS on a separate machine to offset the load off the OpenLM Server machine.
• For systems where DSS & DSA will be deployed separately, it is recommended that DSA be placed on the same subnet as the directory service, as close as possible to the machine hosting it to reduce network latency.