To set up a node-locked license of the product:

See "Configuring a Node-Locked License of InstallAnywhere" on page 9 of the Flexera Product Download and License Guide for InstallAnywhere 2011 and Later (PDF).

To set up a new or existing license server:

See Setting Up Your License Server for Concurrent Licenses.

To connect a machine that has the product to the license server:

See Connecting Machines to Your License Server.

• Can I evaluate or use InstallAnywhere without configuring the licensing?
• What is the difference between the node-locked and concurrent licensing models for InstallAnywhere?
• How can I obtain an activation code for my product?
• How do I determine the host ID of my machine?

• What is the Product and License Center?
• How do I create a new user account for myself in the Product and License Center?
• I'm having trouble downloading installations from the Product and License Center. What can I do?
• How do I add users, modify users, or remove access for users in the Product and License Center?
• How do I figure out who in my organization generated our license files?
• What Flexera technology does the Product and License Center use?

• What's the best way to download my license file?
• What node locked–related parameters are available for build.exe, the InstallAnywhere command-line build tool? For example, can I set up node-locked licensing for build.exe through the command line?
• What do I do if I obtain a new machine? Can I move InstallAnywhere and my license file to that machine?
• I generated the license file but I entered the wrong host ID. How do I regenerate the correct license file?
• I installed InstallAnywhere on a Linux box. When I try to use the licensing wizard to set up my node-locked licensing, the value of the host ID on the Host ID dialog in the wizard is blank. How do I determine my machine's host ID in this case?

• What are the system requirements for the FlexNet Licensing Server?
• What is the difference between lmadmin and lmgrd?
• What's the best way to download my license file?
• I have concurrent licenses for an earlier version of InstallAnywhere, and I just bought upgrades for the latest version of the product. How can I generate an upgrade concurrent license that I can use on my FlexNet Licensing Server to manage concurrent licenses for those multiple versions of InstallAnywhere?
• How do I resolve an error that I encounter when trying to specify a license file on a 64-bit Linux machine?
• I have a concurrent license of InstallAnywhere and I am using build.exe, the InstallAnywhere command-line build tool, to build my installation. What build.exe command-line parameters are available to connect to the FlexNet Licensing Server?
• How do I start the FlexNet Licensing Server service on a Windows machine?
• How do I get reports that show usage information for my organization?
• I've purchased concurrent licensing for more than one Flexera product. Can I use the same machine to manage concurrent licenses for all of these products?
• I have a FlexNet Licensing Server machine to manage concurrent licenses of an old version of a Flexera product. That machine uses lmgrd, the command-line tool. Do I need to switch to lmadmin for my new Flexera concurrent licenses?
• What do I do if I obtain a new licensing server machine? Can I move the FlexNet Licensing Server software and my license file to that machine?
• What do I need to know about installing lmadmin, the local Web-based user interface for managing concurrent license files, on my Linux-based FlexNet Licensing Server system?

The following licensing models are available for InstallAnywhere:

• Node-locked licensing—With this model, the product license is tied to a specific user and machine. This model is the traditional option and the one that is most often purchased.
  • A node-locked license for InstallAnywhere requires a Flexera–generated license file for the machine on which you install InstallAnywhere.
  • If you are using the node-locked type of license, it is your responsibility to maintain your license on your machine. Sharing this type of license between multiple users does not comply with Flexera products' end-user license agreements (EULAs).
• Concurrent licensing—This model enables sharing or floating of InstallAnywhere licenses among multiple users; it is also sometimes called floating licensing. Concurrent licensing can provide you with greater flexibility and cost efficiency than the traditional node-locked licensing.
  • If your organization purchased concurrent licenses for a Flexera product, you need to connect your product to the licensing server that you are using. Subsequently, every time that you start a Flexera product on your machine, the server is queried to verify that the required license is available. If the license is available, you are granted access to a Flexera product.

Neither licensing model for InstallAnywhere uses activation.

To learn more about these different licensing models and determine which option best fits your requirements, contact your a Flexera sales representative or your preferred reseller.

The host ID that the Flexera Product and License Center requires you to enter when you are acquiring a license file is the machine's MAC address, which is also called the physical address or Ethernet address.

You can download the following tool and launch it on any Windows-based system to determine its host ID:

FlexNetHostIDExe.exe

Launching that tool displays a window that shows the host ID and lets you copy it to the Clipboard:

To manually determine the host ID of a specific machine:

1. Open a Command Prompt window.
2. At the command prompt, enter the following command:

ipconfig /all

Configuration information is displayed in the Command Prompt window.



3. In the Ethernet adapter Local Area Connection section, look at the Physical Address value.

This physical address value is the host ID of your machine. Use this value (without the dashes) when you are obtaining a license file from the Product and License Center.

The Flexera Product and License Center is where you perform InstallAnywhere-related tasks such as the following:

• Download the InstallAnywhere installations.
• Generate and download new node-locked or concurrent license files for InstallAnywhere.
• Generate and download new concurrent license files for the FlexNet Licensing Server.
• View and reacquire existing license files.
• View history such as which users in your organization have generated license files and which machines in your organization have license files.

The Product and License Center offers several methods for downloading products. Examples include:

• Browser FTP—The file is transferred using FTP via a Web browser. This is the default method.
• HTTPS—The file is transferred using encrypted HTTP via a Web browser.
• Command-Line FTP—The file is transferred using FTP via a DOS prompt or UNIX shell.
• Download Manager—This applet-based download lets you select multiple or individual files for download via the Download Manager. All files are saved to a single location on your machine.

If you are having trouble using one method to download the product, you may want to try a different method. For example, if the browser FTP method does not work because your organization's firewall blocks FTP, you may want to try the HTTPS method.

To change the available download options for all download links and buttons that are displayed for your user account in the Product and License Center:

1. In the left navigation under Administration, click Download Preferences.
2. Select the check boxes for the download methods that you want to be displayed whenever you are presented with a download link or button in the Product and License Center.

To change the available download options for a specific download in the Product and License Center:

1. In the left navigation under Entitlements, click Product List. The Product List page shows all of the product lines to which your account is entitled. If you do not have access to multiple products, clicking the Product List link opens the Product Information page directly.
2. If the Product List page shows multiple products, click the InstallAnywhere link. The Product Information page opens.
3. Find the item that you want to download, and then in the Description column, click the license link for that item. The Product Download page opens.
4. Find the item that you want to download, and click the Advanced Download Options link for that item. The Advanced Download Options page opens.
5. Select the appropriate option.

To look up who generated license files and see details about those license files:

1. In the left navigation under Entitlements, click View Licenses by Member. The View Licenses by Member page opens. It shows a table that lists all of the users at your organization who generated license files.
2. Click the email address of a member to see details about the license files that the member generated.

If you try to use build.exe to build installations without configuring the licensing for either the full InstallAnywhere product or build.exe, build.exe runs in evaluation mode for a limited number of days, and it creates evaluation installations.

At any time when you launch build.exe from the command line, you can configure node-locked licensing information by passing the -registerNodeLocked parameter to build.exe as follows:

build.exe -registerNodeLocked LicenseFilePathAndName

LicenseFilePathAndName represents the path and file name of the license file (.lic).

Whenever you run a build with the same user account that was used to specify the node-locked license information, you can build installations. Specifying the license information is required only once—either through the licensing wizard for the full InstallAnywhere product, or through the command line for build.exe.

To determine the host ID of the machine, use the following command:

build.exe -generateHostID

To clear license information from your machine—for example, if you are moving the license to a different machine—use the following command:

build.exe -unregister

Note that the -register parameter—which was used to specify the activation code in InstallAnywhere 2010 and earlier—is now obsolete.

If you obtain a replacement machine, you can move your license from your old machine to your new machine. In order to move your license to your new machine, you must first return your license to your account in the Product and License Center. Returning the license makes it available again so that you can obtain a new license file for a different machine.

Note that there is a limit to the number of times that you can return a license: you can return a license only one time per entitlement per year. An entitlement is the purchase of the InstallAnywhere product.

To return a license in the Product and License Center:

1. In the left navigation under Entitlements, click Product List. The Product List page shows all of the product lines to which your account is entitled. If you do not have access to multiple products, clicking the Product List link opens the Product Information page directly.
2. If the Product List page shows multiple products, click the InstallAnywhere link. The Product Information page opens.
3. Find the item that you want to return, and then in the Description column, click the license link for that item. The Product Download page opens.
4. Click the License Keys link. The License Information page opens. It shows the licenses that have been generated for the selected license.
5. Find the license that you want to return, and click its Return button. Note that if you or someone in your organization has already returned a license for the entitlement that is associated with the selected license, the Return button is not displayed.

The Product and License Center processes your return request and refreshes the License Information page so that the license you returned is no longer displayed. Now you can generate a new license for the new machine. You can also install InstallAnywhere and the new license file on your new machine.

You can follow the same return-the-license procedure that is described in the previous question.

Note that there is a limit to the number of times that you can return a license: you can return a license only one time per entitlement per year.

When you install InstallAnywhere on a Linux system, the installation attempts to create a symbolic link to the default Linux loader (/lib/ld-linux.so.2) if a link with the same name is not already present. The symbolic link is necessary for the host ID to be displayed on the Host ID dialog, and it is also necessary for successful node-locked licensing. The link is present on systems that are Linux Standard Base (LSB) 3 compliant, but it may not be present on systems that are not LSB compliant. If the installation cannot create the symbolic link because you do not have permission to do so, you can manually create it.

To manually create the symbolic link (and thus fix the host ID display issue, and be able to set up node-locked licensing):

1. Log in as root.
2. Execute the following command:
   ln -s /lib/ld-linux.so.2 /lib/ld-lsb.so.3

The FlexNet Licensing Server software manages license check-out and check-in requests from users who have concurrent licenses. If you have purchased concurrent licenses of a Flexera product, you need to install this FlexNet Licensing Server software on a machine in your environment.

When you are determining which machine to use as the FlexNet Licensing Server, note the following:

• The license file is locked to the specific FlexNet Licensing Server machine; the license file is based on the host ID (that is, the MAC address) of the network card on the license server. If you attempt to install the FlexNet Licensing Server software on another machine, it will not run.
• The FlexNet Licensing Server machine can be any machine in your network. Typically, the licensing server system components reside on a central machine in the network.
• The Flexnet Licensing Server software can be run on Windows-, Linux-, and Solaris-based systems. The FlexNet Licensing Server machine does not need to be an actual server operating system.
• The FlexNet Licensing Server machine must be able to communicate with the Flexera product through a TCP/IP port. A valid number is any unused port number between 0 and 64000. The default port range is 27000 through 27009. You may need to adjust your firewall settings to allow this communication.
• The FlexNet Licensing Server machine can have other applications running on it; it does not need to be dedicated to running only the FlexNet Licensing Server. However, for a high-traffic, high-license-count environment, and a more reliable system, it is better to have a dedicated machine.
• The FlexNet Licensing Server machine should remain on at all times so that users can access it at all times. The FlexNet Licensing Server machine must be accessible through the network by all of the machines that need to use InstallAnywhere.

If you want to be able to use the same FlexNet Licensing Server to manage concurrent licenses for multiple versions of InstallAnywhere, you need to obtain an upgrade concurrent license file in the Product and License Center. For instructions, see "Generating an Upgrade Concurrent License for an Existing FlexNet Licensing Server" on page 21 of the Flexera Product Download and License Guide for InstallAnywhere 2011 and Later (PDF)".

Once you have generated the upgrade concurrent license, you can add it the license server, as described in the "Adding Concurrent License Files to the FlexNet Licensing Server" section on page 22 of the Flexera Product Download and License Guide for InstallAnywhere 2011 and Later (PDF).

If you are using a 64-bit version of InstallAnywhere on a 64-bit Linux machine, you may encounter an error when specifying the correct path for the .lic file:

The following error is written to the debug log file (console.txt):

Trying to checkout IAEE version=12.0
Library for Native Hostid Couldn't Be Loaded (-521,7024)
Trying to checkout IAEB version=12.0
Library for Native Hostid Couldn't Be Loaded (-521,7024)
 

For instructions on how to resolve this issue, see Knowledge Base article Q214129: Unable To License 64 Bit Version Of InstallAnywhere 2011 or Later Using A Node Locked License File On 64 Bit Linux Operating Systems.

If you try to use build.exe to build installations without configuring the licensing for either the full InstallAnywhere product or build.exe, build.exe runs in evaluation mode for a limited number of days, and it creates evaluation installations.

At any time when you launch build.exe from the command line, you can connect to the license server by passing the -ls (license manager) parameter to build.exe as follows:

build.exe -ls Port@Host

Host represents the name of the machine that has the FlexNet Licensing Server software. Port is the HTTP port number. If the server is configured to use the default port, you do not need to specify the server port number.

For example, to connect build.exe with a license server that has an IP address of 192.168.0.1 and port number 27001, you would use the following command:

build.exe -ls 27001@192.168.0.1

To connect build.exe with a license server that has an IP address of 192.168.0.1 and the default port, you would use the following command:

build.exe -ls 192.168.0.1

Once you have specified the connection information, the licensing is established. Whenever you run a build with the same user account that was used to specify the connection information, you can build installations. Specifying the connection information is required only once—either through the licensing wizard for the full InstallAnywhere product, or through the command line for build.exe.

If you are using a triad server cluster, use colons or semicolons to separate each port and host combination to connect to the license servers, as follows:

build.exe -ls Port1@Host1:Port2@Host2:Port3@Host3

build.exe -ls Port1@Host1;Port2@Host2;Port3@Host3

Port1 and Host1 are the port number and name of the master license server, Port2 and Host2 are the port number and name of the secondary license server, and Port3 and Host3 are the port number and name of the tertiary license server. If the servers are configured to use the default ports, you do not need to specify the server port numbers.

To determine the host ID of the machine, use the following command:

build.exe -generateHostID

To clear license information from your machine—for example, if you want to connect InstallAnywhere to a different FlexNet Licensing Server—use the following command:

build.exe -unregister

Note that using the -ls Host:Port syntax—which was used in InstallAnywhere 2010 and earlier to specify the host and port—is now obsolete.

You can start the Windows service for the FlexNet Licensing Server by using Services in the Administrative Tools area of the Control Panel. The default name of the service is:

FlexNet Licensing Server Manager

(The name of the service is configurable when you are installing the FlexNet Licensing Server.)

The FlexNet Licensing Server can save a report log file that contains feature usage information. To create a report log file and view reports, you need to purchase Flexera's software license administration solution, FlexNet Manager. FlexNet Manager provides exceptional visibility into license usage data and helps you create insightful reports on critical information like license availability and usage.

For more information on FlexNet Manager, see the Flexera Web site:

https://www.flexera.com/products/flexnet-manager

No, you can continue using lmgrd; consider switching to lmadmin, since it has an easy-to-use graphical user interface.

If you want to switch from lmgrd to lmadmin, you must first uninstall the earlier version of the FlexNet Licensing Server. Then install the latest version, which has lmadmin. For instructions on how to obtain the latest version of the FlexNet Licensing Server software, see "Obtaining the FlexNet Licensing Server Software and Installing It on the Licensing Server" on page 17 of the Flexera Product Download and License Guide for InstallAnywhere 2011 and Later (PDF).

Once you have installed the latest version, you can import license files for earlier versions of InstallAnywhere into lmadmin, as described in the "Using the License Server Manager (lmadmin) on a FlexNet Licensing Server to Import Concurrent Licenses and Perform Related Tasks" section on page 22 of the Flexera Product Download and License Guide for InstallAnywhere 2011 and Later (PDF).

Note that lmgrd and lmadmin should not be installed on the same machine.

Avoid Installing lmadmin as Root

If you install lmadmin on a Linux-based system when logged on as root, you may encounter various issues. For example:

• When you try to launch the Web server (http://localhost:port) on the license server, you encounter an "Unable to connect" error.
• When you attempt to run the license server, you may encounter the following errors:

  14:28:12 (mvsn) Vendor daemon can't talk to lmgrd (Cannot read data from license
  server system. (-16,287))
  14:28:12 (mvsn) EXITING DUE TO SIGNAL 37 Exit reason 5

  In Web.log:
  

  [Wed Mar 18 14:28:01 2011] [warn] pid file /opt/FNPLicenseServerManager/logs/lmadmin.pid overwritten -- Unclean shutdown of previous Apache run?
  [Wed Mar 18 14:28:01 2011] [alert] getpwuid: couldn't determine user name from uid 4294967295, you probably need to modify the User directive

• A process listing for lmadmin ('ps aux | grep lmadmin') returns no results.
• A process listing for mvsn ('ps aux|grep mvsn') returns results if run right after lmadmin is started but then fails after a few seconds. If you view the mvsn.log file in the logs directory (the default location is /opt/FNPLicenseServerManager/logs), you see that the process failed with the following error messages:

  16:05:37 (mvsn) Report log started (mvsn/report.log).
  16:05:47 (mvsn) Vendor daemon can't talk to lmgrd (Cannot read data from license server system. (-16,287))
  16:05:47 (mvsn) EXITING DUE TO SIGNAL 37 Exit reason 5
  

Therefore, when you are installing lmadmin on a Linux-based system, it is recommended that you avoid installing as root. If you have already installed lmadmin when logged on as root and you do not want to reinstall lmadmin, change the ownership of all of the files in the installed folder from root to another user.

Setting up a 64-Bit Linux System for the FlexNet Licensing Server

If the LSB module is not present on a 64-bit Linux system, you may not be able to start the FlexNet Licensing Server. This is applicable for the Ubuntu distribution of Linux, and it may be applicable to other distributions of Linux. To install the LSB module, run the following command:

sudo apt-get install LSB

If libgcc_s.so.1 is incompatible with lmadmin or it is not present, you may not be able to start the FlexNet Licensing Server. To resolve this issue, copy a 32-bit version of this file from /lib/libgcc_s.so.1 on a 32-bit machine to the /lib32/ folder of the 64-bit machine.

If a loopback address is not configured, you may not be able to start the FlexNet Licensing Server. To resolve this issue, configure the loopback address in the /etc/hosts file on the system.