There is no global license for Player. Regional licenses are not permitted to ‘float’ outside of a region or follow the sun. 

The GIS-PAX licensing regions are:

  • North America (Canada/USA/Mexico)
  • South/Central Americas
  • Europe (including eastern Europe)
  • Russia
  • FSU ex Russia
  • N Asia (China, Koreas, Japan)
  • South East Asia
  • Indian sub-continent (Bangladesh, India, Sri Lanka, Pakistan)
  • ANZ (Australia, NZ, Pacific, PNG)
  • Middle East
  • Africa


Our larger customers manage their licenses locally within the office/region. For example they may have license servers in: Houston, Singapore and Perth; or Aberdeen, Stavanger and Kuala Lumpur. One customer manages regional licenses centrally across a WAN. The Player software has an internal license check every couple of minutes so a slow network could cause the licenses to dropout. 

We can work with your IT license management folks to get the best arrangement. IT prefer to manage the licenses centrally, we would supply one license file per region. You could either use separate license servers to host each gispax ISV and license file; or use a single license server with one gispax ISV and multiple license files. We would expect you configure RLM appropriately to comply with our regional license model and not globally pool the licenses, not allow global floating or ‘follow the sun’ licenses.

Reprise has a number of options for controlling how users/regions access Player licenses. You can partition licenses for separate groups on a single license server. 

Below are two simple scenarios. There are 6 Player licenses and two groups. Reprise allows defining of groups by username, hostname or IP address. The most generic regional approach is to use an INTERNET_GROUP. This is a list of IP addresses separated by spaces. IP addresses can contain the wildcard (‘*’) character. The options are specified in a file on the server. 

One approach is to define the Player licenses in a single license file and pool them together.

Use the option file to control access across the groups.

This restricts region1 to a single Player license. Region2 will always have 2 licenses available and could use all 6. If a user from region1 tries to access Player when their license is already in use, they get an error:

Alternatively the 6 Player licenses could be split into different license files, each with 3 licenses. Your license administrators can then use the _id option in the license file to separate the Player licenses into two pools: 100 and 200.


Below the Player licenses appear as two separate pools. This would allow you to manage the different groups at this level. This feature is available in the latest version of RLM: v11.2BL2.

In this scenario, the options file restricts the region1 users to a maximum of 1 license from pool 1. 2 Player licenses are reserved for region2 from pool 5, but they can use as many as they need.

There are other ways to configure RLM to restrict access to specific groups of users. If you have a specific scenario contact the GIS-PAX Helpdesk. For more information you can also read the Reprise License Administration Guide: