# FlexNet Embedded license server setup

#### **Subtopics**

1. [Setting the hostname of a system controller](https://lhc.advantest.com/books/flexnet-embedded-licensing/page/setting-the-hostname-of-a-system-controller "The hostnamectl tool is provided for administering the three classes of hostnames that can be used on a system controller or license server running RHEL 7.")
2. [Single FNE License server installation, upgrades and updates](https://lhc.advantest.com/books/flexnet-embedded-licensing/page/single-fne-license-server-installation-upgrades-and-updates "Installation procedure for a single FlexNet Embedded license server to provide activated licenses. Applicable to fresh installations, and applying upgrades to add major functionality and patch updates installing the latest packages on an existing server.")
3. [Failover license server installation, upgrades and updates](https://lhc.advantest.com/books/flexnet-embedded-licensing/page/failover-license-server-installation-upgrades-and-updates "Installation procedure for a failover FlexNet Embedded license server arrangement to provide activated licenses. Applicable to fresh installations, and applying upgrades to add major functionality and patch updates installing the latest packages on an existing server.")
4. [Registering the license server](https://lhc.advantest.com/books/flexnet-embedded-licensing/page/registering-the-license-server "A new license server must be registered with the Advantest FNE Licensing Back-office before it can be used to host licenses.")

FlexNet Embedded license servers are implemented to provide activated licenses to SmarTest system controllers.

<section class="section" id="bkmrk-introduction-install">### Introduction

Installing a FlexNet Embedded license server able to provide the activated licenses requires three steps:

- Installation of the license server software on the host system
- License server registration
- License activation

The FNE license server, when installed in conjunction with the FNP2FNE proxy, can manage both FNE and FNP licenses for all supported SmarTest versions (SmarTest 5, 6, 7 and 8), and includes new features such as self-rehosting for SmarTest 5, 6 and 7 (FNP) license servers.

</section><section class="section" id="bkmrk-prerequisites-make-s">### **Prerequisites**

Make sure that the system hosting the FlexNet Embedded license server meets the following Prerequisites:

Hardware minimum configuration:

- Quad core CPU
- 8 GB RAM
- 12 GB free hard disc space FNE, plus 12GB for FNX/FNP if used.

Operating system configuration:

- Red Hat Linux ≥ 9.0, 7.2 - 7.9, Rocky Linux ≥ 9 or CentOS 7.2 - 7.9.
- Available user with unrestricted sudo access.
- Ports 7070 and 7077 may not be used by other applications. If FNX is installed, ports 27000, 27019, and 27020 must not be used by other applications.
- Java 8 - Oracle Java or OpenJDK
- License server must use fully qualified hostname (command `<var class="varname"><span class="keyword"><span class="filepath">hostname -f</span></span></var>` must not return `<var class="varname"><span class="keyword"><span class="filepath">localhost</span></span></var>`)

</section><section class="section" id="bkmrk-checking-the-availab">### **Checking the availability of ports 7070 and 7077**

Ports 7070 and 7077 must not be in use by other applications.

To check this, enter in the bash shell (if you use ksh, you can open a bash shell with enter /bin/bash on the command line):

`<var class="varname"><span class="keyword"><span class="filepath"><kbd class="userinput">&> /dev/null < /dev/tcp/localhost/7070 && echo INUSE</kbd></span></span></var>`

`<var class="varname"><span class="keyword"><span class="filepath"><kbd class="userinput">&> /dev/null < /dev/tcp/localhost/7077 && echo INUSE</kbd></span></span></var>`<kbd class="userinput"></kbd>

In addition, if FNX is used for FNP license management, ports 27000, 27019, and 27020 must not be in use by other applications.

To check this, enter in the bash shell (if you use ksh, you can open a bash shell with enter /bin/bash on the command line):

`<var class="varname"><span class="keyword"><span class="filepath"><kbd class="userinput">&> /dev/null < /dev/tcp/localhost/27000 && echo INUSE</kbd></span></span></var>`

`<var class="varname"><span class="keyword"><span class="filepath"><kbd class="userinput">&> /dev/null < /dev/tcp/localhost/27019 && echo INUSE</kbd></span></span></var>`

`<var class="varname"><span class="keyword"><span class="filepath"><kbd class="userinput">&> /dev/null < /dev/tcp/localhost/27020 && echo INUSE</kbd></span></span></var>`

If no response message is displayed, the port is not in use.

If the response `INUSE` is displayed, the port is in use.

If port any of these ports are in use, either use a different server to host the FNE license server or get in contact with your administrators (customer IT) to identify the application and remove it from the server to be used for the FNE license server.

The <span class="keyword">lsof `lsof`</span> command can be used to find processes using a particular port. For example, the following command returns information of the process using port 7070:  
  
<kbd class="userinput">`<kbd class="userinput">sudo lsof -i tcp:7070</kbd>`</kbd>

Example output:

```
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
java 11381 flexnetls 40u IPv6 56027 0t0 TCP *:arcp (LISTEN)
```

<p class="callout info"><span class="title">Note: The installation of an FNE license server opens all required ports in the firewall (7070, 7077, 27000, 27019 and 27020).</span></p>

</section><section class="section" id="bkmrk-checking-the-availab-2">### **Checking the availability of port 443**

If your FNE license server is to have an online connection to the Advantest Licensing Back-Office, you need a connection to the internet for outgoing connections (FROM the license server to the internet). To check if access is available before you install the FNE license server.

</section><p class="callout info"><span class="title">Note:</span> You do not need to check the availability of port 443 if you will only be communicating offline with the Advantest Licensing Back-Office (exchanging files as opposed to an Internet connection).</p>

<section class="section" id="bkmrk-do-the-following-to-">Do the following to check if port 443 is open on your FNE license server:

1. Open a browser.
2. Enter the URL: [https://license.advantest.com/](https://license.advantest.com/).  **If the port 443 is open**, the Advantest License Portal Welcome page is displayed:
    
    [![1.png](https://lhc.advantest.com/uploads/images/gallery/2025-10/scaled-1680-/1-png.png)](https://lhc.advantest.com/uploads/images/gallery/2025-10/scaled-1680-/1-png.png)
    
     **If port 443 is not open,** an error message page is displayed informing of a timeout or failure to connect to the requested page, for example:
    
    [![2.png](https://lhc.advantest.com/uploads/images/gallery/2025-10/scaled-1680-/eJp2-png.png)](https://lhc.advantest.com/uploads/images/gallery/2025-10/scaled-1680-/eJp2-png.png)
3. If you require an internet connection to the Advantest Licensing Back-Office, get in contact with your administrators (customer IT) and request that port 443 is opened.

</section><section class="section" id="bkmrk-checking-the-date-an">### **Checking the date and time settings**

It is important to have the correct date and time set on the workstations and license servers. The Network Time Protocol (NTP) can be used to synchronize the clocks of computers with a reference time source over a network. For details on how to synchronize the date and time settings using NTP, see [Network time protocol configuration](https://tdc.advantest.com/help/topic/com.verigy.itee.help.service.ui.8.7.6/150646.htm).

</section><section class="section" id="bkmrk-network-configuratio">### **Network configuration**

For a license server to start, the server workstation must be set up for networking.

For a local license server installed on the system controller that is not connected to a network, a few prerequisites must be considered. The system controller must have a Fully Qualified Domain Name (FQDN). As a result, the `<span class="filepath">/etc/hosts</span>` file must have an entry of the form:

`ip address hostname.domainname hostname`

For example: `192.168.0.15 server123.mycompany.com ws123`

For more details about setting hostnames, see [Setting the hostname of a system controller](https://lhc.advantest.com/books/flexnet-embedded-licensing/page/setting-the-hostname-of-a-system-controller "The hostnamectl tool is provided for administering the three classes of hostnames that can be used on a system controller or license server running RHEL 7.").

</section><section class="section" id="bkmrk-next-steps-if-the-pr">## Next steps

If the prerequisites are met, start the installation of the FNE license server as described in the appropriate topic:

- [Failover license server installation, upgrades and updates](https://lhc.advantest.com/books/flexnet-embedded-licensing/page/failover-license-server-installation-upgrades-and-updates "Installation procedure for a failover FlexNet Embedded license server arrangement to provide activated licenses. Applicable to fresh installations, and applying upgrades to add major functionality and patch updates installing the latest packages on an existing server.")
- [Single FNE License server installation, upgrades and updates](https://lhc.advantest.com/books/flexnet-embedded-licensing/page/single-fne-license-server-installation-upgrades-and-updates "Installation procedure for a single FlexNet Embedded license server to provide activated licenses. Applicable to fresh installations, and applying upgrades to add major functionality and patch updates installing the latest packages on an existing server.")

</section>