The IATA Reader is being decommissioned. Visit this page for more information.

As a result, the eLibrary Floating License is being replaced with the Enterprise Library. Visit this page for more information.

Shared multi-user ​access to IATA Standards

The Floating License (FL) solution is a great way to provide all your staff with access to IATA standards electronically.

The FL solution is an alternate license model for the ‘Windows’ version of IATA publications. The number of floating licenses acquired equals the number of "open sessions" to a publication that can be accessed by users at the same time. One floating license = one user at a time. 10 licenses = 10 users at a time.

It is strongly recommended that you consult your organization's IT department prior to purchase, as installing the product will require IT support. It is very important to read and understand the information in the ‘Product Overview’ and ‘VM Considerations’ sections of the TECH SPECS tab.

With the IATA Floating License solution, an IATA publication (for Windows®) can be made available to as many users within your organization as you want. With the IATA FL solution, licenses can be shared across large numbers of end users located in geographically dispersed offices.

An ideal solution for organizations with many end users requiring irregular or infrequent access to an IATA publication, the FL solution offers you greater flexibility and cost effectiveness.

Get flexible access

Make the IATA publication available to as many users within the organization as needed. Review usage over time to assist with budgeting for future needs. Additional licenses can be easily added when access needs grow.

Works on a wide range of IT infrastructures

Highly flexible, the FL solution is compatible with most organizations' software distribution strategies. While the single user license version an IATA publication has to be installed and activated on each end user’s Windows computer, with the Floating License solution only the license server needs to be activated. After that, deploy the end user component as a distributed/virtual application, include it in virtual desktops, host it on a Windows Server, install it on computers, or combinations of those.

Save money

With licenses that can be shared by hundreds of individuals, the cost per end user can potentially be much lower than the single user alternative.​​​

Product Overview

Important: Installing the FL solution will require an organization’s IT team(s).

The product has two parts: A license server, and a client application. The product is available for Microsoft Windows® systems only.

The license server is installed on a Windows system (typically Windows Server) within an organization's IT infrastructure. For best results, the license server should be installed on a physical Windows computer.

The end user component can be installed on as many Windows systems (physical or virtual) within an organization as needed. The end user component interacts with the license server for 'leases' of the floating licenses. The license server must have persistent internet access, in order to communicate with IATA's activation server. Client computers need persistent network access to the license server (over a unique, customizable TCP port).

More Information

License Server

The license server runs as a service on a Windows computer. The license server manages license lease requests from the end user applications. Multiple floating license servers (for different IATA publications) can be hosted on the same machine.

VM Considerations

The license server requires activation. Activation is bound to hardware IDs, on a specific host machine. The license server must remain activated in order to manage license leases from clients.

  • Recommended: Physical host
    For best results, the license server should be installed on a physical Windows computer.
  • On prem or private cloud virtual host
    The license server may be installed on a VM, but one must have control over the VM’s host. If the license server is installed on a VM, and the host hardware changes or is perceived to have changed, product deactivation is likely. This most commonly applies to hypervisor groups within which a VM may move from host to host.
    In an on prem hypervisor group, plan to bind/anchor the VM to a specific host.
  • Not recommended: Public cloud virtual host
    Large third party cloud hosting environments should be avoided as one is not likely to have control over the underlying hosting of the VM.
    Do not set up the license server in an environment where one does not have full control over the license server’s hosting conditions.

Client Software

The client component is made up of the IATA Reader for Windows® software, plus an IATA Reader publication document (for example the Dangerous Goods Regulations). IATA Reader is installed on physical or virtual Windows computers, in a virtual desktop solution, in a distributed/virtual application solution, hosted on a terminal server, or combination of those. The publication document is installed and opened in the IATA Reader software. Multiple different IATA publication documents may be opened in the same IATA Reader application.

Setup Overview

  1. Select a Windows computer to act as license server host.
    Note: For best results, the license server should be installed on a physical Windows computer.
  2. Select a TCP port for client-server communication.
  3. Activate and install the license server.
    The license server requires product activation and periodic validation (internet connectivity required).
  4. Install the IATA Reader software on client computers (or in your alternate software deployment technology).
    IATA Reader may be installed for Current User or for All Users (elevation required)
  5. Install the IATA publication '.mirdoc' document on client computers.
    The publication content (e.g. the DGR, AHM, LAR, etc.), opened within the IATA Reader, is always installed PER USER to user profile folders.
  6. Adjust the configuration settings file (e.g. DGRconfig.ini) to include information about the license server host ('FLSIP' for computer name or IP address, 'FLSPort' for the selected TCP port).
  7. Apply the configuration settings file.
    The file is stored with the publication content, PER USER in user profile folders.
  8. Adjust communication layers between the client and server.
    Security and network layers must permit communication on the chosen port.

About the License Server

System Requirements

  • Install on a Windows computer (typically Windows Server), minimum Windows Server 2008. 32 and 64 bit OS supported.
    Note: For best results, the license server should be installed on a physical Windows computer.
  • Administrator level permissions during installation.
  • Internet connection for product activation and periodic validation.
  • Persistent network connection (TCP/IP) for accepting and managing lease assignments.
  • Multiple license servers (for different IATA products and different editions) can be hosted on the same computer, as long as each one uses a unique TCP port.

Resource Usage

The license server manages license lease assignments to clients. All IATA publication content is stored on the end user computer, and all application functionality is performed by the end user application. The license server service has a small resource footprint. Processor & RAM usage are low, unless very large numbers of leases are being assigned and released constantly. The computer used to host the license server does not need to be powerful. The license server service can often be added to an existing Windows Server already performing light to moderate duties. The files making up the license server amount to about 10 MB in size.

As a general rule, powerful or multiple processors are not needed, large amounts of RAM are not needed, fast drives are not needed.

About the Client Application

System Requirements - IATA Reader for Windows

  • Windows 10, 8.1, 8, 7, Vista
  • Microsoft .NET Framework 4.5.2 or later
  • Microsoft Internet Explorer 8.0 or higher
  • About 150 MB for the IATA Reader software install
  • 25 to 350 MB for the publication content (depending on the publication)

Software and Publication Content Install Locations

The IATA Reader software may be installed for Current User (to a user's profile folder) or for All Users (to e.g. C:\Program Files (x86)). The IATA Reader software is compatible with common deployment strategies (physical end user computer, VM, VDI, distributed app, terminal server).

Important: The publication content (e.g. Dangerous Goods Regulations) viewed within the IATA Reader software is not installed to the same location. The content must always be installed for Current User, to a user's profile folder. IATA Reader always reads publication content from:


Publication content must therefore be replicated per user.

With the floating license solution, an IATA application may be installed on as many end user Windows computers as an organization wishes. The number of users who can open and use the IATA application at the same time will equal the number of floating licenses held. For example, an IATA application might be installed on 50 computers across several offices. With 5 licenses, 5 users will be able to open and use the IATA application at a time. A 6th user wishing to open the application will need to wait until one of the 5 users closes his/her copy of the application.

The floating license solution is highly flexible. It can be used in a variety of technology infrastructure environments, as long as a Microsoft Windows OS system is available to host the floating license server and end user application. The FL solution can be used in a terminal server setup (e.g. Microsoft Windows Server RDS with RDWeb), distributed to end users in a virtual/published application setup (e.g. with Citrix XenApp or Microsoft App-V), made available within a VDI environment, or installed in a virtual or physical computer.

One or more members of an organization’s IT team must perform the setup operations. Actions are needed on at least one Windows Server system for installation of the floating license server. Outbound communications from the license server host to IATA's activation server need to be enabled. Security devices/layers in between the FL license server and the end user IATA application(s) need to be configured to allow the communication traffic between client and server. Depending on the end user application distribution method used, system administrator permissions may be needed as well on the end user systems.

End User IATA Application: The IATA Reader application included in an FL solution is compatible with physical and virtual computers, terminal server hosting, and virtual application distribution. Note: Publication content (e.g. the Dangerous Goods Regulations) is installed separately from the IATA Reader software. Publication content must always be stored per user, at %userprofile%\AppData\Local\IATA\Reader\\Library.

Floating License Server: IATA recommends use of a physical Windows host computer for the license server. Or, a virtual machine may be used, IF one has control over the hosting conditions. IATA recommends against hosting a license server in a large third party cloud hosting environment.

The license server component in an FL setup must undergo product activation. The activation is bound to a series of hardware IDs. The hardware IDs must remain constant for the license server to remain activated. On a physical machine the hardware IDs can be expected to remain constant (barring significant changes to the system). On a virtual machine, steps will need to be taken to ensure the underlying hardware IDs remain consistent.

For example, with a license server installed on a VM hosted in a multi-member on premises hypervisor group, the VM may move to a different host each time it is restarted. The underlying hardware IDs reported to the VM may change on each host, and the license server will become deactivated. In such a case, binding/anchoring the VM to a specific host, or otherwise stabilizing the VM’s hardware IDs will be necessary.

Installing a license server on a VM hosted in a large third party cloud hosting environment should be avoided. Control over the underlying hosting of the VM and thus maintaining license server activation is very likely to be problematic. Unless one is certain to have control over VM hosting conditions, do not plan to host a license in a large third party cloud hosting environment.

The FL solution includes two components: A license server and an end user application. The license server must be hosted on a Windows OS, typically Windows Server. The end user application must be installed within a Windows OS. The end user application can be installed within a virtual Windows computer hosted on a Mac computer (e.g. in a solution such as Parallels). Support of the FL solution on the Mac platform is limited to such a scenario.

The floating license server requires persistent internet connectivity. At the time of license server activation an internet connection is needed, and the license server periodically communicates with IATA’s activation servers for continued activation validation.

Persistent TCP/IP network connectivity (over a customizable TCP port) between the end user application(s) and the license server is needed for lease management.

Yes. Multiple floating license servers can all be hosted on the same Windows Server. Each license server runs as a distinct Windows service. Each license server must be configured to use a unique TCP port for client-server communication.