Hexagon Geospatial
MENU

Licensing Knowledge Base

Easily license Hexagon Geospatial desktop products using the License Manager .
Showing results for 
Search instead for 
Do you mean 

Configuring TCP PORTS for Geospatial Licensing 2018

by psmith 4 weeks ago - edited 3 weeks ago (107 Views)

After installing Geospatial Licensing 2018 and activating a license using License Administrator, the License Administrator will try to start the service on TCP PORT 27000. If that port is not available (closed or already in use) the service may fail to start. In such cases we can either create or edit the empty license file in C:\Users\Public\Intergraph\Licenses\Server folder which can be manually edited to specify specific server and vendor ports.

There are two executables installed by Geospatial Licensing that are used to host a license service. One is the FlexNet Licensing Service, LMGRD.exe (server daemon), the other is the Intergraph Licensing Service, INGRTS.exe (vendor daemon). Both of these require an open port of communication even if you are running the application and the service on the same machine.

The LMGRD.exe server daemon uses a port to receive client requests for a license (even if it's from your own machine). After receiving a request for a license, the LMGRD.exe (Flexnet Service) talks to the INGRTS.exe vendor daemon via the port assigned for vendor. The default port assigned to INGRTS.exe vendor daemon is controlled by the operating system (the vendor just gets a default handed to it by the OS).

If you want to control which ports are used (which is often the case in today's high security environments) you will need to review these suggestions to edit the "empty" .lic fie in the C:\Users\Public\Intergraph\Licenses\Server folder.

Your windows firewall (run WF.msc) can be used to open / declare user defined TCP PORTS. You can assign a user defined name of your choosing for the 2 TCP PORTS.


HINT: Do not build any rules on the ports that you open. Open and use the ports first then if rules are needed, modify and test again by stopping and restarting the Licensing Service using Licensing Administrator, Server > Stop and Start commands. In the example below we have used WF.msc to ensure that TCP PORTS 27010 and 27011 are open.

 

Example:
Suppose your license server nodename is called BIGDOG and has a composite id 9503D56FFEF5. You have already used windows firewall to open ports 27010 and 27011 on the server. Now you want to define 27010 as the server port, and 27011 as the vendor port.

 

Overview:

  • You can use notepad or notepad++ to edit the "empty" .lic fie in the C:\Users\Public\Intergraph\Licenses\Server folder.
  • Append the server port number to the end of the first (SERVER) line.
  • Define the vendor port number by adding PORT=<TCP PORT VALE> to the end of the second (VENDOR) line.

Specific Example:

In the example below, notice how the server port is simply appended to the first line (the server line) of the "empty" .lic fie in the C:\Users\Public\Intergraph\Licenses\Server folder. The vendor port is defined on the second line by appending PORT=27011. Notice how you must enter "PORT=<PORT_VALUE> for the vendor port. If you do not specify a vendor port then one will be provided by your operating system.

 

SERVER BIGDOG 9503D56FFEF5 27010
VENDOR INGRTS PORT=27011
USE_SERVER

 

After specifying the ports in the empty .lic file, you can now use the GeoSpatial License Administrator, Server menu option to stop and restart the service.

 

Configure the client systems applications by running the application configuration wizard and specify the SERVER_NAME and enter the PORT value corresponding to the .lic file server line port value (27010 in our example).

 

The configuration process will add the entry 27010@BIGDOG as a license source to the INGRTS_LICENSE_PATH file found in the C:\ProgramData\Intergraph\Licensing folder. The INGRTS_LICENSE_PATH keeps a semi-colon <;> separated list of license sources.

 

Note: If a client does not specify any port, then when attempting to obtain a license from the service on server, the client will try ports 27000 -> 27009; so in our case the client user MUST define the specific port value.

 

If you should encounter problems or have further questions, don't hestate contacting support by logging a support ticket:

https://www.hexagongeospatial.com/resources/support

 

 

Contributors