# FlexNet Embedded licensing
1. [FlexNet Embedded license **server setup**](https://lhc.advantest.com/books/flexnet-embedded-licensing/chapter/flexnet-embedded-license-server-setup)
2. [FlexNet Embedded license **client setup**](https://lhc.advantest.com/books/flexnet-embedded-licensing/chapter/flexnet-embedded-license-client-setup)
3. [FlexNet Embedded license **administration**](https://lhc.advantest.com/books/flexnet-embedded-licensing/chapter/flexnet-embedded-license-administration)
4. [**Monitoring license** servers using the FNE Server Viewer](https://lhc.advantest.com/books/flexnet-embedded-licensing/page/monitoring-license-servers-using-the-fne-server-viewer)
5. [**Re-hosting** FlexNet Embedded licenses](https://lhc.advantest.com/books/flexnet-embedded-licensing/page/rehosting-flexnet-embedded-licenses)
6. [**Controlled re-hosting** for FNE](https://lhc.advantest.com/books/flexnet-embedded-licensing/page/controlled-rehosting-for-fne)
7. [**Troubleshooting** FlexNet Embedded licensing](https://lhc.advantest.com/books/flexnet-embedded-licensing/page/troubleshooting-flexnet-embedded-licensing)
# FlexNet Embedded licensing
FlexNet Embedded (FNE) is the licensing technology from Flexera adopted by Advantest. It is the replacement for the current FlexNet Publisher (FNP) technology.
FlexNet Embedded licensing is the default for SmarTest versions ≥ 8.1 and 7.10, and can be used with SmarTest versions ≥ 7.6.
- FNE architecture uses the same client-server concept as the earlier FNP technology.
- FNE offers more flexibility and ease of use.
- FNE does not need a permanent connection between the client and the license servers.
- FNE includes self re-hosting functionality (move licenses between license servers).
The main components of an FNE licensing setup is shown in the following graphic:
The FlexNet Licensing Back-office at Advantest is the license management infrastructure, incorporating the master database for licenses, and the location from which customer licenses are available for activation.
If, for example, a you remove licenses from one of your FNE license servers, this needs to be reflected in the FlexNet Licensing Back-office at Advantest before these licenses can be activated by another license server. Therefore, some data exchange is required between the your FNE license servers and the FlexNet Licensing Back-office at Advantest. This can be achieved over the Internet (online usage) or using file exchange (offline usage).
The FlexNet Licensing Back-office at Advantest is, however, transparent for customers. A license portal is available for managing licenses (for example, registering FNE license servers, exchanging data files, activating licenses), and takes over the tasks of communicating with the Advantest FlexNet Licensing Back-office.
### **Benefits of FlexNet Embedded**
- FNE provides a more stable production environment while clients only need to contact the license server every 20 minutes.
- Supports a renewal concept with less effort.
- Supports self-rehosting.
- Provides a device-specific licensing concept, including multi-dimensional locking.
- The host ID of the license server is not required for registration. Entering of host IDs is required by FNP and is error-prone.
### **Differences between FlexNet Embedded and FlexNet Publisher.**
- FNE does not use license files.
- Advantest FNP uses incremental licensing in license files. With every new license activation a new license file is created, which results in multiple license files. This makes license management difficult.
- Advantest FNE uses a license container. With each license activation all licenses of the license server are provided in a binary file. This eases license management. \- The license container is a binary file, which requires no manual editing. In FNP, editing the license container file is error-prone.
\- One file contains the complete license content. License management is simpler.
- License Portal interface is available for interaction with the FNE Licensing Back-office.
- The license server log files have different formats.
# FlexNet Embedded license server setup
# 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.
### 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.
### **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 `hostname -f` must not return `localhost`)
### **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):
`&> /dev/null < /dev/tcp/localhost/7070 && echo INUSE`
`&> /dev/null < /dev/tcp/localhost/7077 && echo INUSE`
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):
`&> /dev/null < /dev/tcp/localhost/27000 && echo INUSE`
`&> /dev/null < /dev/tcp/localhost/27019 && echo INUSE`
`&> /dev/null < /dev/tcp/localhost/27020 && echo INUSE`
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 lsof `lsof` command can be used to find processes using a particular port. For example, the following command returns information of the process using port 7070:
`sudo lsof -i tcp:7070`
Example output:
```
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
java 11381 flexnetls 40u IPv6 56027 0t0 TCP *:arcp (LISTEN)
```
Note: The installation of an FNE license server opens all required ports in the firewall (7070, 7077, 27000, 27019 and 27020).
### **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.
Note: 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).
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:
[](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:
[](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.
### **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).
### **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 `/etc/hosts` 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.").
## 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.")
# 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.
### **Scope**
***RHEL 7***
The following tips are applicable for RHEL 7. For more information about configuring host names, refer to the Red Hat documentation: [https://access.redhat.com/documentation/en-us/red\_hat\_enterprise\_linux/7/html/networking\_guide/ch-configure\_host\_names](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/networking_guide/ch-configure_host_names).
***RHEL 9***
For information about changing hostnames on RHEL 9 using the **nmcli** or **nmtui** tools, refer to the Red Hat documentation: [https://access.redhat.com/documentation/en-us/red\_hat\_enterprise\_linux/9/html/configuring\_and\_managing\_networking/assembly\_changing-a-hostname\_configuring-and-managing-networking#proc\_changing-a-hostname-using-nmcli\_assembly\_changing-a-hostname](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/configuring_and_managing_networking/assembly_changing-a-hostname_configuring-and-managing-networking#proc_changing-a-hostname-using-nmcli_assembly_changing-a-hostname)
### **View all hostnames**
To view all the current hostnames, enter the command:
`hostnamectl status `
The `status` option is implied by default if no option is given.
### **Set all hostnames**
To set all the hostnames on a system, as root, enter the command:
`hostnamectl set-hostname name `
This command changes the pretty, static, and transient hostnames to the name specified in *name*. The static and transient hostnames are simplified forms of the pretty hostname. Spaces are replaced with "-" and special characters are removed.
### **Set a particular hostname**
To set a particular hostname, as root, enter the command with the relevant option:
`hostnamectl set-hostname name [option...] `
Where option is one or more of: `--pretty`, `--static`, and `--transient`.
If either the `--static` or `--transient` options are used with the `--pretty` option, the static and transient hostnames are simplified forms of the pretty hostname. Spaces are replaced with "-" and special characters are removed. If the `--pretty` option is not specivied, no simplification takes place.
If the pretty hostname to be set contains spaces or a single quotation mark, use quotation marks around the name entry. For example:
`hostnamectl set-hostname "Advantest's SmarTest 8.2 system controller" --pretty`### **Check a hostname**
To check if the hostname is set correctly as a fully qualified domain name, as root, enter the command:
`hostname -f`
An example of a correct response is: `server123.mycompany.com`
Incorrect response example: `localhost.localdomain`
### **Clear a particular hostname**
To clear a particular hostname and revert to the default, as root, enter the command with the relevant option:
`hostnamectl set-hostname "" [option...] `
Where:
`""` is a quoted empty string.
option... is one or more of: `--pretty`, `--static`, and `--transient`.
# 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.
### About this task
The following procedure is applicable to installation, upgrades and updates. For failover arrangements, also refer to [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.").
Registering the server is only required for initial installation. This steps should be omitted for upgrades and updates. If you are upgrading an existing installation, a running license server is automatically stopped as part of the new software installation.
The license server install package can be downloaded from the Advantest Software Center server:
[https://softwarecenter.advantest.com/download/othersw/builds/licensing](https://softwarecenter.advantest.com/download/othersw/builds/licensing)
### **Before you begin**
Make sure that the system hosting the FlexNet Embedded license server host system meets the hardware and operating system prerequisites. For details, see [FlexNet Embedded license server setup](https://lhc.advantest.com/books/flexnet-embedded-licensing/page/flexnet-embedded-license-server-setup "FlexNet Embedded license servers are implemented to provide activated licenses to SmarTest system controllers.").
### **Procedure**
1. Open the Advantest Software Center in a browser: [https://softwarecenter.advantest.com/](https://softwarecenter.advantest.com/)Login with your credentials.
2. To get the list of all available Licensing products, from the left menu select: **Other > Licensing
**[](https://lhc.advantest.com/uploads/images/gallery/2025-10/scaled-1680-/IN13-png.png)
3. Scroll to and select the license type FNE and the version you want to install and expand to display the details.
4. Create an empty installation directory. For example:`/tmp/smartest_pakages ``mkdir /tmp/smartest_pakages `
Note: It is not recommended to use a separate partition for **/tmp**. Ensure that sufficient space is allocated to the **/tmp** folder. As **/tmp** is a shared directory and used by many applications, the required folder size is dependent on the actual use and so customer-specific. Therefore, Advantest cannot give a recommendation about the required size of this folder. Monitor the **/tmp** folder and make sure that sufficient space is always available.
5. Download the archive package by clicking the [](https://lhc.advantest.com/uploads/images/gallery/2025-10/scaled-1680-/WoC9-png.png) icon. The selected license (**tar.gz**) package is downloaded to your browser's download folder.
Example FNE packages include:
`fne_2024.01.0.0-24043_rhel9.tar.gz`
6. Move the downloaded archive packages to the installation directory: `/tmp/smartest_pakages`
7. Unpack the archive with the command: **`tar xvzf package-name.tar.gz`**
For example:
`tar xvzf fne_2024.01.0.0-24043_rhel9.tar.gz`
The installation script is extracted, for example:
`install-fne-2024.01.0.0-24043-rhel9.sh`
8. Check the downloaded archive package for integrity: `bash install-fne-date-version.sh test`
9. Start the installation or upgrade using the command appropriate for your licensing environment:
Note: During upgrading and updating, the installation script can be called without any options. All installed packages are detected automatically and updated if applicable.
##### **FNE license only**
**Installation with support for SmarTest 8 only (FNE licenses only):**
`sudo sh install-fne-date-version.sh server`
For example:
`sudo sh install-fne-2024.01.0.0-24043-rhel9.sh server`
**Upgrade (FNE software is installed and to be upgraded with newer software):** `sudo sh install-fne-date-version.sh`
For example:
`sudo sh install-fne-2024.01.0.0-24043-rhel9.sh`
##### **FNE and FNP licenses**
**Installation with support for SmarTest 8 and older SmarTest releases (FNE and FNP licenses):
**
`sudo sh install-fne-date-version.sh fnx`
For example:
`sudo sh install-fne-2024.01.0.0-24043-rhel9.sh fnx`
*The FNX front-end server that converts legacy **lmgrd** FNP license calls into FNE license call is also installed, providing support for SmarTest versions 5, 6 and 7.*
**Upgrade (FNE software is installed and to be upgraded with newer software):**
`sudo sh install-fne-date-version.sh`
For example:
`sudo sh install-fne-2024.01.0.0-24043-rhel9.sh`
***After installation, the FNE license server is automatically started.***
***This also installs the [FNE Server Viewer](https://lhc.advantest.com/books/flexnet-embedded-licensing/page/monitoring-license-servers-using-the-fne-server-viewer "The FNE Server Viewer is a web-based application that can be used to monitor Advantest license servers.").***
10. To display the readme file: `sh install-fne-date-version.sh readme`
11. **Optional:** Remove the installation directory. For example:`rm -rf /tmp/smartest_packages`### **Results**
The FNE license server and the FNE Server Viewer are installed.
To check if the FNE license server is running:
`/usr/bin/fne-status` or`/usr/local/bin/fne-status`
If the FNE license server is running, the following type of output is displayed:
```
* advantest-fne-server.service - Flex Net Embedded license server adapted for Advantest
Active: active (running) since Mon 2019-05-20 11:08:14 CEST; 3 days ago
* advantest-fne-server-viewer.service - Advantest Flex Net Embedded License Server Viewer
Active: active (running) since Mon 2019-05-20 11:06:48 CEST; 3 days ago
* advantest-fne-proxy.service - Advantest FNP2FNE proxy
Active: active (running) since Mon 2019-05-20 11:07:36 CEST; 3 days ago
```
To check if the FNE Server Viewer is running, enter the following URL in a browser:
`http://:7077`### **What to do next**
[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.")
# 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.
### About this task
Note: It is possible to set up an emergency FNE license server, listed at the end of the client.conf file. In an emergency where the normal license servers are inaccessible, install the emergency licenses on the emergency license server. All clients automatically connect to the emergency FNE license server.
Note: If you are upgrading an existing installation, a running license server is automatically stopped as part of the new software installation.
The following procedure is applicable to installation, upgrades and updates. However, associating the servers (step 2), registering the primary server (step 3), and synchronizing the servers (step 4) are only required for initial installation. These steps should be omitted for upgrades and updates.
Note: During updating, the installation script can be called without any options. All installed packages are detected automatically and updated if applicable.
### **Before you begin**
A redundant FNE failover setup consists of two servers; the primary production system and the failover standby system. If the primary system stops working, for example, due to a hardware defect, the failover system assumes the production workload and handles all requests. The period of each failover substitution is limited to a maximum of 5 days. During these 5 days, you must repair and recommission the primary server or set up a new server.
Note: If the failover system goes down while the primary system is handling the production workload, there is no mandatory time limit for getting it running again. However, during this period there is no redundancy backup.
For mixed FNE-FNP environments, also refer to [Mixed FlexNet Embedded and FlexNet Publisher licensing](https://lhc.advantest.com/books/licensing-reference/page/mixed-flexnet-embedded-and-flexnet-publisher-licensing "FlexNet Embedded (FNE) and FlexNet Publisher (FNP) license management can be handled from an FNE license server installation, using the FNP to FNE proxy solution, simplifying license management.") and [Set up a three-license-server redundancy configuration](https://lhc.advantest.com/link/84#bkmrk-set-up-a-three-licen-1 "In a redundancy configuration with three license servers, each of the three license servers runs on its own dedicated machine. Two servers are used to serve licenses and their license files must be kept synchronized. The third server is required to build the quorum, participating in monitoring the availability of at least one license server, but does not serve licenses. Licenses do not need to be installed on the third server.")
- Make sure that the system hosting the FlexNet Embedded license server host system meets the hardware and operating system prerequisites. For details and check procedures, see [FlexNet Embedded license server setup](https://lhc.advantest.com/books/flexnet-embedded-licensing/page/flexnet-embedded-license-server-setup "FlexNet Embedded license servers are implemented to provide activated licenses to SmarTest system controllers.").
- To be able to detect any license server problems early, we strongly recommend that you plan to include the FNE license servers in your availability monitoring setup. SmarTest cannot inform you about the failure of a license server.
### **Procedure**
1. Install the license server software on the primary server, the failover server, and for mixed FNE-FNP environments, on the FNP tertiary server.
Follow the instructions described in the appropriate topic linked below:
**FNE-only environments**
[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.")
**Mixed FNE-FNP environments**
[Single FNP 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 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.")
2. **❗ Not for upgrades or updates** : Associate the failover FNE license server with the primary FNE license server, using a user other than root, on the primary server execute the command:
`/opt/flexnetls/socbu/fne-failover-setup .`
3. **❗ Not for upgrades or updates** : Register the primary FNE license server with the Advantest Licensing Back-Office:
`register-fne-server `
For details see [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.").
4. **❗ Not for upgrades or updates** : Synchronize the FNE license servers:
For FlexNet Embedded license servers that are connected to the internet, an automatic synchronization should occur immediately. If this is not the case, you can perform a `sync-fne-server` action on the license server.
For FlexNet Embedded license servers not connected to the internet, registering the servers from the primary server (uploading the registration-request-file to the Advantest Licensing Back-Office) provides you with a downloadable license container file.
Unpack and apply the license container file to the primary AND the failover systems using the following command on each license server:
`register-fne-server `
For full details see [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.").
5. On the primary license server check the status of the failover system:
`/opt/flexnetls/socbu/fne-failover-status`
The following displays an example of the status output:
[](https://lhc.advantest.com/uploads/images/gallery/2025-10/scaled-1680-/Znx4-png.png)
6. Activate the licenses to the new FNE license server. For details, see [Activating licenses](https://lhc.advantest.com/books/activating-licenses/page/activating-licenses "After the successful license server installation and registration, you need to provide the licenses to the license server that it is to serve. Simple license activation is used to activate an entitlement on a license server.") or [Downloading licenses](https://lhc.advantest.com/books/licensing-reference/page/downloading-licenses "If the FNE license server is not connected to the internet you must manually download the license container from the Advantest License Portal and upload it to the FNE license server.") as appropriate for your environment.
### **Results**
The FNE primary and secondary license servers are installed, synchronized and licenses are activated.
To check if an FNE license server is running:
`/usr/bin/fne-status` or `/usr/local/bin/fne-status `
If the FNE license server is running, the following type of output is displayed:
```
* advantest-fne-server.service - Flex Net Embedded license server adapted for Advantest
Active: active (running) since Mon 2019-05-20 11:08:14 CEST; 3 days ago
* advantest-fne-server-viewer.service - Advantest Flex Net Embedded License Server Viewer
Active: active (running) since Mon 2019-05-20 11:06:48 CEST; 3 days ago
* advantest-fne-proxy.service - Advantest FNP2FNE proxy
Active: active (running) since Mon 2019-05-20 11:07:36 CEST; 3 days ago
```
To check that the installation is complete, open a browser to view the FNE Server Viewer from the primary FNE license server system:
`http://:7077`
Click on link **Features**.
You should see the licenses activated to your license server.
Check the connections of the primary and failover FNE license server systems with:
- `http://:7070/api/1.0/health`
- `http://:7070/api/1.0/health`
Note To uninstall the FNE License Server and FNE Server Viewer, execute the command:
`sudo yum remove advantest-fne-server advantest-fne-server-viewer `
# 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.
### About this task
Before you can install licenses onto the license server, the license server needs to be registered in the Advantest FNE Licensing Back-office. This is made over an online internet connection or by uploading and downloading files configuration files offline.
If your license server has access to the internet, only one **`register-fne-server`** tool command is required to complete the registration. If your license server host system does not have access to the internet, the **`register-fne-server`** tool provides you with a binary request file that you upload using the Advantest License Portal.
After registering your license server, activate your licenses using the license portal.
### **Before you begin**
Registration is executed by running the **`register-fne-server`** tool with a server activation ID from the Advantest License Portal. The server activation ID is available from the Advantest License Portal as an entitlement.
The activation ID takes the following form: ``
Your assigned server activation IDs are listed in the Advantest License Portal.
Note: Your entitlement certificate contains a representation of the registration key. Get the actual registration key from the License Portal.
### **Procedures**
##### **Online Registration**
If your license server has access to the internet, run the **`register-fne-server`**tool on the FlexNet Embedded license server for the initial registration of the FNE server at Advantest using the following command:
`register-fne-server `
The registration should complete automatically and the following message is displayed:
```
Successfully activated your server to
```
Server registration is complete.##### **Offline Registration**
1. If you do not have internet access to the Advantest back-office, from the primary server, generate the registration request file using the command:
`register-fne-server `
The registration request file is generated and the following message is displayed:
```
No connection to backoffice at license.advantest.com:80
Offline license server activation is successfully written to:
/tmp/srv_registration_request_.bin for 127.0.0.1 : 7070
```
2. Copy the request file generated in the previous step to a computer with internet access.
3. From the computer with internet access, log on to the Advantest License Portal: [https://license.advantest.com/](https://license.advantest.com/).
Note: If you do not have an account, click the **Register button**, create an account using an entitlement ID belonging to your organization for which the server should be registered. Provide a user name and a password for the account. On successful registration, an account is created and you are automatically logged in.
4. Open the tab License Management and click Register Server.
[](https://lhc.advantest.com/uploads/images/gallery/2025-10/scaled-1680-/l2K5-jpg.jpeg)
The **Register Server** page opens and lists the available registration keys.
5. Click on the registration key corresponding to the activation ID entry to be used to register the license server.
The command in the illustration below is adapted and you can use copy and paste to execute the **`register-fne-server `**tool on your FNE license server.
[](https://lhc.advantest.com/uploads/images/gallery/2025-10/scaled-1680-/3Pd6-png.png)
6. Click **Upload request file** and specify the location of the `srv_registration_request_.bin` file copied from the license server in step 2.
The license server is now registered.
### **Results**
Your license server is registered.
### **What to do next**
[Activating licenses](https://lhc.advantest.com/books/activating-licenses/page/activating-licenses "After the successful license server installation and registration, you need to provide the licenses to the license server that it is to serve. Simple license activation is used to activate an entitlement on a license server.")
# FlexNet Embedded license client setup
# FlexNet Embedded license client setup
#### Subtopics
1. [Installing the FNE license client](https://lhc.advantest.com/books/flexnet-embedded-licensing/page/installing-the-fne-license-client "Installing a FlexNet Embedded license client used to provide the activated licenses to a SmarTest installation on a system controller workstation requires two steps: the installation of the license client software itself on the SmarTest host system, and configuration of the license server configuration file to prioritized the order of server access.")
2. [Uninstalling the FNE license client](https://lhc.advantest.com/books/flexnet-embedded-licensing/page/uninstalling-the-fne-license-client "Uninstalling the FNE license client is done manually using yum.")
3. [Enabling license logging](https://lhc.advantest.com/books/flexnet-embedded-licensing/page/enabling-license-logging "Detailed information about license consumption and optimize license usage can be identified by License usage logging.")
The FlexNet Embedded license client is required to run on the system controller (installed as default).
The FlexNet Embedded license client is installed as the default license client.
Information required to install, configure and administer FlexNet Embedded license clients is divided into the following areas:
- License client installation - Installation of the license client software to manage the licensing of a SmarTest software installation.
- Switching the client between FlexNet Embedded and FlexNet Publisher servers.
- License client administration - Advantest FlexNet Embedded (FNE) license client tools and their usage.
### **System controller prerequisites**
- SmarTest 8.x
- The system controller fully-qualified hostname
### **Checking the connection to a customer-hosted FNE License Server**
After installing the FNE license server, check that the FNE license server is contactable from the SmarTest workstation before you start the installation of the FNE client subsystem on the SmarTest workstation.
`href="http://:7070/api/1.0/health `
Complete the following procedure to check the connection to the FNE license server:
1. Open a browser.
2. Enter the URL appropriate for your FNE server arrangement:
- `href="http://:7070/api/1.0/health `
``represents the hostname of the *FNE license server* to which you are testing the connection.
- **`href="http://:7070/api/1.0/health ` **represents the hostname of the *failover FNE* license server to which you are testing the connection.
If the FNE license server is contactable (port 7070 is open), the following type of output is displayed:
[](https://lhc.advantest.com/uploads/images/gallery/2025-10/scaled-1680-/L4R11-png.png)
3. **If port 7070 is not open**, you a page with a not available message is displayed. In this case, get in contact with your administrators (customer IT) and request that port 7070 is opened for the SmarTest client workstation.
# Installing the FNE license client
Installing a FlexNet Embedded license client used to provide the activated licenses to a SmarTest installation on a system controller workstation requires two steps: the installation of the license client software itself on the SmarTest host system, and configuration of the license server configuration file to prioritized the order of server access.
### About this task
Installing the FNE license client (installed as default license client) also installs the FNE Server Viewer. For more details, see [Monitoring license servers using the FNE Server Viewer](https://lhc.advantest.com/books/flexnet-embedded-licensing/page/monitoring-license-servers-using-the-fne-server-viewer "The FNE Server Viewer is a web-based application that can be used to monitor Advantest license servers.").
The following procedure explains how to install the FlexNet client.
### **Before you begin**
The license client is the SmarTest software. The FlexNet license server communicates with SmarTest using the FNE client.
The license client install package can be downloaded from the FNE section of the Advantest Software Center:
[https://softwarecenter.advantest.com/download/othersw/builds/licensing](https://softwarecenter.advantest.com/download/othersw/builds/licensing)
The following procedure is applicable to installation, upgrades and updates.
Note: During upgrading and updating, the installation script can be called without any option. All installed packages are detected automatically and updated if applicable.
`sudo sh install-fne-date-version.sh`
**Port 7070** must be open to the customer FNE license server and if needed to the cloud license server.
To check connection to your license servers, use the command:
If you are using the Advantest cloud license servers, check the connections by opening the following URLs:
- http://<license-server>:7070/ping
- https://<Device Owner FNE license server>.advantest.cloud:7070/ping
- https://<Device Owner FNE license server>-fo.advantest.cloud:7070/ping
If port 7070 is open, the following type of output is displayed:
[](https://lhc.advantest.com/uploads/images/gallery/2025-10/scaled-1680-/jtO44-png.png)
### **Procedure**
1. Open the Advantest Software Center in a browser: [https://softwarecenter.advantest.com/](https://softwarecenter.advantest.com/)
Login with your credentials.
2. To get the list of all available Licensing products, from the left menu select: **Other > Licensing
**[](https://lhc.advantest.com/uploads/images/gallery/2025-10/scaled-1680-/9IE55-png.png)
3. Scroll to and select the license type FNE and the version you want to install and expand to display the details.
4. Create an empty installation directory. For example:`/tmp/smartest_pakages`
5. Download the archive package by clicking the [](https://lhc.advantest.com/uploads/images/gallery/2025-10/scaled-1680-/WoC9-png.png) icon.
The selected license (`tar.gz`) package is downloaded to your browser's download folder.
Example FNE packages include:
`fne_2024.01.0.0-24043_rhel9.tar.gz`
6. Move the downloaded archive packages to the installation directory: `/tmp/smartest_pakages`
7. Unpack the archive with the command:
`tar xvzf package-name.tar.gz`
For example:
**`tar xvzf fne_2024.01.0.0-24043_rhel9.tar.gz`**
**The installation script is extracted**, for example:
**`install-fne-2024.01.0.0-24043-rhel9.sh`
**
8. Check the downloaded archive package for integrity:
`bash install-fne-date-version.sh test`
9. Shut down the **SmarTest Work Center**.
For details see [Shutting down SmarTest](https://tdc.advantest.com/help/topic/com.verigy.itee.help.smartest.ui.8.7.6/248729.htm "This task describes the procedure of shutting down SmarTest.").
10. Install the client package: `sudo sh install-fne-date-version.sh client`
For example:
`sudo sh install-fne-2024.01.0.0-24043-rhel9.sh client`
Note: During upgrading and updating, the installation script can be called without any option. All installed packages are detected automatically and updated if applicable.
11. **Optional:** Remove the installation directory. For example:
`rm -rf /tmp/smartest_packages`
12. After the installation has completed, configure the license server configuration file where the list of FlexNet Embedded license servers are listed in a prioritized order.
Open the **configuration file** in an editor: **`/etc/fne/client.conf`
**
Syntax of the **client.conf** file:
- **Local license server**
```
#Configuration of FNE servers to be used
# primary FNE server
server
{
name = "FNE on localhost"
url = "localhost"
}
```
- **Remote license server**
```
#Configuration of FNE servers to be used
# primary FNE server
server
{
name = "FNE central server"
url = "hostNameLicenseServer.domain"
}
#secondary FNE server
server
{
name = "FNE remote server"
url = "socbu158.advantest.com"
}
```
---
Keywords for the **client.conf** file:
**include**
Used to include another configuration file. **include** can be used multiple times in a file.
**server { }**
Used to specify a server description with brackets enclosing each description. **server { }** can be used multiple times in a file.
**name**
Free text used to add a description for a server.
**selector**
The client must comply with all listed selector conditions before the client can attempt to contact the server.
**selector** can be used multiple times in a file.
**url/primaryUrl**
**url** used to address for the server if only one server is configured. Use **primaryUrl** instead for the primary server when more than one server is configured.
**failoverUrl**
Used to address the failover servers.
**mute**
Used to suppresses connection-related error messages for the corresponding server.
Other error messages are displayed.
Some FNE servers listed in **client.conf** files may be unavailable by intent, for example, emergency servers or temporary servers. If these servers are not running or disconnected, associated error messages are normally displayed at each checkout request, which can be unhelpful if it is an expected situation.
Note: The mute keyword is not supported by older FNE subsystems and is ignored if specified. For FNE subsystem versions that do not support the mute keyword, a syntax warning might be displayed and can be ignored.
13. Enter the names and URLs for all FlexNet Embedded license servers that you want to use in their order of priority.
14. To verify the installation and license server configuration enter the command:
`/usr/local/bin/fne-list-licenses`
The tool iterates through the FlexNet Embedded servers defined in **`/etc/fne/client.conf`** and lists all licenses (used and available).
It also provides detailed information about the available licenses including:
- Content of the AssetScale tokens
- Locking of licenses
- Expiry information
Note: The fne-list-licenses tool does not show details from cloud license servers.
For details, see [fne-list-licenses](https://lhc.advantest.com/books/flexnet-embedded-licensing/page/advantest-flexnet-embedded-license-client-tools).
### **Results**
You have installed the license client software and configured the list of FlexNet Embedded license servers in a prioritized order.
The order in which clients attempt to check out licenses is the same order in which the licenses are referenced in the **client.conf** file.
### **Example**
#### Example of a client.conf file:
```
#Configuration of FNE servers to be used
# Emergency Server
include "/etc/fne/emergency.conf"
server
{
name = "Local cloud space"
url = "localcloud.company.com"
}
server
{
name = "My cloud"
selector = "DeviceOwner:MyCompany"
url = "https://MyCompany.advantest.cloud:7070"
}
server
{
name = "Local license server"
primaryUrl = "fne1.company.com"
failoverUrl = "fne2.company.com"
}
```
Minimum client.conf file configuration:
```
server
{
url = "localhost"
}
```
# Uninstalling the FNE license client
Uninstalling the FNE license client is done manually using yum.
### About this task
There are two options for uninstalling the FNE license client:
- Remove the FNE client only, which results in automatically switching back to using the FNP license client and FNP licensing.
- Completely remove the FNE client installation, which removes the license client, the FNE Server Viewer, and the `test_license_checkout` tool.
### **Procedures**
#### Uninstalling the FNE license client only
To remove the FNE client only, enter the command:
`yum remove v93000-fne-client`### **Completely uninstalling the FNE license client and tools**
To completely remove the FNE client installation, enter the command:
`yum remove v93000-fne-client advantest-fne-server-viewer advantest-test_license_checkout`### **Results**
FNE license client is no longer installed on the SmarTest system controller.
# Enabling license logging
##### **Subtopics**
- [**Reading log file data**](https://lhc.advantest.com/link/73#bkmrk-reading-log-file-dat-1)
- [**Example logfile parser**](https://lhc.advantest.com/link/73#bkmrk-example-logfile-pars)
Detailed information about license consumption and optimize license usage can be identified by License usage logging.
### **About this task**
To be able to get detailed information about license consumption and optimize license usage, it is necessary to analyze the licensing requirements for memory and speed for each measurement within a test program. From this information, it is then possible to isolate the main license requirements.
License usage logging (incremental over measurements and per measurement logging) provides the information required to establish the licensing dependencies. If the watermark increases in proportion to the measurement data, the test is independent, otherwise it shares data with other tests.
Log data is written to:
`/opt/hp93000/soc/system/log/licenseUsage_.log `
To read in the data you need to generate a parser based on protobuf library using the grammar in:
`/opt/hp93000/soc/system/include/xoc/profiling/licenseUsage.proto `
An existing file is not overwritten - only new data is appended to the existing content.
The most valuable data collected by license logging is when you have not previously executed an initial bind before executing the profile configuration. After an initial bind, only dynamic changes are recorded.
### **Before you begin**
Make sure the test program has been loaded.
License logging can only be enabled using a Profile launch configuration.
### **Procedure**
1. Select a test program or test flow in the **Package Explorer** view for which you want to enable license logging.
License logging is not available for encrypted testflows or test programs containing encrypted testflows.
2. Open the **Profile Configurations** dialog from the context menu:
**Profile As > Profile Configurations
**
3. Select **Test Program** from the objects pane on the left.
4. Click the New Launch Configuration [](https://lhc.advantest.com/uploads/images/gallery/2025-10/scaled-1680-/10-png.png) button.
5. Enter a name for the new profile configuration in the configuration pane on the right.
6. In the **Main** tab (default selection), select **Enable license logging**.
[](https://lhc.advantest.com/uploads/images/gallery/2025-10/scaled-1680-/kAy66-png.png)
7. Specify any other required configurations. For details, see [Creating a run configuration for running test programs or testflows](https://tdc.advantest.com/help/topic/com.verigy.itee.help.smartest.ui.8.7.6/256920.htm "You can specify, save and reuse customized configurations for starting test programs or testflows in execute or debug mode.").
8. Click **Apply** to save the profile configuration.
9. Click **Profile** to profile the test flow or **Close** to close the **Profile Configurations** dialog box.
##### **Results**
License logging is enabled.
Log data is written to `/opt/hp93000/soc/system/log/licenseUsage_.log.`
A license usage log file contains the memory contribution (in Bytes) for each signal for each measurement.
Note: License logging can also be enabled and disabled using the Test Cell API. For example:
`TestProgramConfig config;`
`config.enableLicenseLogging = true;``testProgram.loadWithConfig(config);`
For details about TestProgramConfig, see **[TestProgramConfig](https://tdc.advantest.com/help/topic/com.verigy.itee.help.smartest.ui.8.7.6/structxoc_1_1tcapi_1_1_test_program_config.html).**
##### **What to do next**
The generated log file is user-readable and it is possible to manually extract the licensing requirements for memory and speed for each measurement within a test program. It is not essential to parse this file.
However, for further processing, it can be beneficial to parse the file to arrange its content into a more readable format.
To read in the data you can generate a parser based on the **protobuf** library using the grammar in:
`/opt/hp93000/soc/system/include/xoc/profiling/licenseUsage.proto`
---
# Reading log file data
1) Log file data contains information, such as memory usage.
##### **About this task**
If license logging is enabled, the license log data is written to:
**`/opt/hp93000/soc/system/log/licenseUsage_.log.`**
The following log example shows the used memory (Pattern or PA = 1032 bytes) for the signal D04. The total accumulated value (`accDoubleValue`) is 3096 bytes which the total memory used by the complete program.
##### **LicenseUsage.log file example:**
```
measurementName: "Main.GlobalPAPattern.measurement"
measurementTimestamp: "Mon, 01 Jul 2019 15:30:08 -0700"
licensedFeatureLog {
featurePerSignal {
signalList: "D00 + D01 + D02 + D03 + D04"
feature {
feature: "speed"
accDoubleValue: 10000000
unit: "bps"
}
}
featurePerSignal {
signalList: "D04"
feature {
feature: "memory"
accDoubleValue: 3096
doubleValue: 1032
unit: "B"
}
feature {
feature: "sharedMemory"
doubleValue: 60352
unit: "B"
}
}
}
```
A license usage log file contains the memory contribution (in Bytes) for each signal for each measurement. The accumulated memory value is also recorded. In the example above:
This file is in the **protobuf** (ASCII) format and can be read using a simple parser. For more information, refer to: https://developers.google.com/protocol-buffers/
Note: If you only require the values for a specific measurement, you can read this from the ASCII text manually.
```
TestProgramConfig config;
config.enableLicenseLogging = true;
testProgram.loadWithConfig(config);
```
The protocol buffer compiler is installed under `/usr/bin/protoc`The protoc version can be found with the command:`/usr/bin/protoc --version`
Output example: **libprotoc 2.5.0**
To structure information, protocol buffer message types are defined in .proto files. The following protobuf file is used for license logging, which can be compiled with the protocol buffer compiler to Java, Python, Objective-C, or C++.
---
### **Before you begin**
Make sure that license logging is enabled. For details, see [Enabling license logging](https://lhc.advantest.com/books/flexnet-embedded-licensing/page/enabling-license-logging "Detailed information about license consumption and optimize license usage can be identified by License usage logging.").
### **Procedure**
1. Create a parser file, for an example, see [Example logfile parser](https://lhc.advantest.com/link/73#bkmrk-example-logfile-pars)**.**
2. For example, to compile to C++ with the protocol buffer compiler, run the following commands or a **make.sh** script containing the commands:
`protoc -I=/opt/hp93000/soc/system/include/xoc/profiling/ --cpp_out=.`` /opt/hp93000/soc/system/include/xoc/ profiling/licenseUsage.proto``c++ -std=c++11 -g -L/usr/local/lib -lprotobuf -o licenseLogger licenseUsage.pb.cc main.cpp`
The generated C++ class is used to simplify the parser implementation.
```
./licenseLogger licenseUsage.log memory D04
Analysing: licenseUsage.log memory D04
Top 20 measurement runs for feature "memory" at signal "D04"
Measurement Run | Value |Watermark Value
----------------------------------+----------+-----------------------
Main.GlobalPAPattern2.measurement | 1032.000 | 3096.000
```
### **Results**
After the above **protoc** call or **make.sh** script is run, the following files are created:
**licenseLogger**
Generated Parser Executable To execute the licenseLogger, use the command: `./licenseLogger `
For example:
`./licenseLogger licenseUsage.log memory D01`
**measurementLicense.pb.cc**
Generated after running protobuf compiler
**measurementLicense.pb.h**
Generated after running protobuf compiler
---
## Example logfile parser
1) The following code is an example parser for reading license log files and printing the top 10 measurement executions contributing to the specified feature and signal.
#### **Example parser (SmarTest ≥ 8.2.0)**
```
#include
#include
#include
#include
#include
#include