You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Magic Collaboration Studio requires a FlexNet license server to operate. It can be installed on the same system, or on a separate machine. This chapter explains how to use the install_flex_<operating_system>.sh automated deployment script which downloads all required components, deploys the server, creates the systemctl service entry to control it, and creates the necessary firewall rules to allow the required traffic. The firewall rules are created for both the internal and public zones. The script may require modification depending on the zone where the interface is located. However, if the firewall is not running when the installation script is executed, the rules are not be created. In addition, the script creates the lmadmin user which runs the lmadmin service.

Prerequisites

  • The FlexNet server requires the Redhat LSB core files and the ld-linux library in order to execute.

  • The install_flex_<operating_system>.sh script is configured for CentOS (Red Hat) 7 or Red Hat 8 , but can be modified for a different OS version as well.


To identify which LSB Core library is required, execute the following command:  

sudo yum provides /lib/ld-lsb.so.3


To install the FlexNet server

  1. Run the install_flex_<operating_system>.sh script to start the installation and follow the installer instructions.

    All the default values presented by the installer should be accepted except for the installation directory which should be changed when prompted (see step 2).

  2. When you are prompted to choose the installation directory, change the default directory to /opt/local/FNPLicenseServerManager.

  3. After the lmadmin service is installed, start it by executing the following command:

    sudo systemctl start lmadmin

  4. To check if the service is running, execute the following command:

    sudo systemctl status lmadmin

Troubleshooting

If the Imadmin service failed to start, it is often because the built-in web server cannot resolve the hostname.

To check if this is the case, execute the following commands:

cd /opt/local/FNPLicenseServerManager/logs
tail web.log

You will see output similar to the following where yourhostname is the name of the host:

[Tue May 02 18:43:27 2017] [alert] (EAI 2)Name or service not known:
mod_unique_id: unable to find IPv4 address of "yourhostname"
Configuration Failed

If this is the case, edit the /etc/hosts file and add the following entry so the webserver could resolve the host:

192.168.130.10  yourhostname