Install the Web Interface

The web interface provides the user interface to manage your inventory and license position. Continue this process as administrator (fnms-admin) on either your:

• application server (for a single server installation); or
• web application server (in a multi-server installation).

Tip: The web interface transfers high volumes of HTML data, which may have noticeable performance impacts for operators with slow links (such as across a WAN) between their web browsers and the web application server. To maximize performance, the web.config file installed on this web application server turns on both static and dynamic content compression, with a setting of this form:

<urlCompression doStaticCompression="true" doDynamicCompression="true" />

These settings turn on compression settings for IIS, where these are available on the web application server:

• Static compression is installed by default for IIS.
• Dynamic compression requires a standard Microsoft installation to enable it. (Without this setup, the dynamic compression setting in the web.config file remains latent, having no possible effect.)

If you have operators on slow (WAN) links, check whether dynamic compression is already available on your web application server by examining the Server Manager, using the Add Roles and Features wizard. If it is not yet configured, see https://docs.microsoft.com/en-us/iis/configuration/system.webServer/urlCompression#setup for installation details.

The instructions provided here show how to install the web interface for FlexNet Manager Suite. Additionally, FlexNet Manager Suite can be installed using a scripted installation. For more information, refer to Managing Scripted Installation.

To install the web interface for FlexNet Manager Suite:

1. On the (web) application server, open Windows Explorer.
2. Copy the downloaded archive FlexNet Manager Suite 2024 R2 Installer.zip from your staging location to a convenient location on this server (such as C:\temp), and unzip it.
   Tip: Unzipping the archive locally on each of your servers simplifies running the configuration scripts later in the process. After running the installers, PowerShell scripts need to be Run as Administrator. Notice that the entire archive must be present, as scripts reference other elements from the archive.
3. Navigate in the unzipped archive to the FlexNet Manager Suite\Installers\FlexNet Manager Suite folder.
4. Start (double-click) setup.exe.
   Tip: You must start the installation by running setup.exe, rather than running the MSI by any other means. The setup file also installs Visual C++ 2010 Redistributable (if it is not already present), which is a prerequisite for integration with FlexNet Manager for SAP Applications.
5. Step through the installer until asked for the Setup Type, and do one of the following:
   • For a small, single server installation combining the web application, the inventory collection, and the batch processing functionality in one server, select the Complete option, and follow the instructions in the installation wizard to complete the standard installation.
     Tip: In the page where you are asked for the batch process credentials, for Server type, choose either Production for your main server installation, or Failover if this is a stand-by or testing server. On your Production server, the batch scheduler and batch processor are automatically started as part of the installation process, while on a Failover server, both are disabled by default. If you need to switch between your production and stand-by servers, you must manually:

     • Disable the batch scheduler and processor on the product batch server
     • Enable the batch scheduler and processor on the standby batch server.

     These adjustments are made in the Microsoft Services control panel.
   • For a multi-server installation, select the Custom installation path, and select the Web application server for this installation. (If this is the only functionality on this server, also ensure that Inventory server, Batch scheduling server, and Batch server are all deselected; but in fact you can combine most servers in the way that best suits your enterprise, so make the selection that matches your server plan.)
   Take note of the installation location for future reference.
6. If this is a separate installation of the web application server in a multi-server implementation, ensure that from this server you can access the network shares that you configured in Configure Network Shares for Multi-Server.
7. If this server includes the batch server functionality, you are prompted for the credentials used for batch processes. Be sure that the account you enter already has Logon as a service permission (see Authorize the Service Account).
8. When successful, close the installation wizard.
9. If you have decided to configure on-demand scanning for every uploaded document, you need to turn on the capability. The setup process so far has create the two required registry keys, but has not set the values required to turn on scanning.
   if you have not already done so, see details in the section Preventing Uploads of Malicious Files in the FlexNet Manager Suite System Reference (on-premises edition for release 2020 R2 or later), available through http:/docs.flexera.com in either PDF or HTML format. If you wish to configure the registry settings now, continue as below (if not, you may defer these changes until later, as part of other changes needed to configure the on-demand scanning).
   1. Open your preferred registry editor on your web application server.
      For example, in the Windows search bar, enter Registry and then open Registry Editor.
   2. Navigate in the registry editor to HKLM\Software\WOW6432Node\Flexera Software\FlexNet Manager Platform\Security\CurrentVersion.
   3. Scroll to, and double-click the value FileUploadScannerPath.
   4. Edit the Value data field to be the path and file name for your PowerShell integration script.
      For example, the default suggested path for the ClamAV tool is

      C:\ClamAV\Filescanner_ClamAV.ps1

      However, ensure that your value is correct for your environment and file name. When done, click OK.
   5. Scroll back to, and double-click the value EnableFileUploadScan.
   6. Edit the Value data field to true, and click OK.
   7. Exit the registry editor.
   The registry settings have no effect until an operator attempts to upload a document.