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 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 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.
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. Additional licenses can be easily added when access needs grow.
Easy to set up and administer
Setup of the IATA FL solution can often be completed quickly and easily. Once installed and configured, little intervention is typically needed. End users or IT staff aren’t required to activate individual applications. Review usage over time to assist with budgeting for future needs.
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.
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.
Select a publication to show/hide details
Setup involves the installation of a license server service on a Windows Server computer within an organization's IT infrastructure. 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.
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 computer (typically Windows Server) and runs as a service. The license server manages license lease requests from the end user applications. The client application 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 a combination of those.
For IATA publication products released 2017 and later, 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 client computers, and the publication document is installed and opened in the Reader. Multiple different IATA publication documents may be opened in the same IATA Reader application.
- Select a Windows Server to act as license server host
- Select a TCP port for client-server communication
- Activate and install the license server
The license server requires product activation and periodic validation (internet connectivity required)
Note: Installing the license server in a VM hosted in a large hypervisor group requires special considerations
- Install the IATA Reader end user 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)
- 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
- 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)
- Apply the configuration settings file
The file is stored with the publication content, PER USER in user profile folders
- Adjust communication layers between the client and server
Security and network layers must permit communication on the chosen port
About the License Server
- Install on a Windows computer (typically Windows Server), minimum Windows Server 2008. 32 and 64 bit OS supported
- 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
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 5 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.
The license server must remain activated in order to manage license leases. The license server relies on a stable underlying hardware ID for persistent activation. 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.
- Options to mitigate the deactivation risks on a VM:
- Anchor the VM to one specific host
- Bind the VM to a set of hypervisors of identical hardware
- Set the hypervisor group to propagate the same hardware ID (if applicable to the hypervisor technology in use)
- Install the license server on a physical machine instead
- Deactivate the license server whenever the VM may potentially move to a different host, then reactivate once it is on a new host
About the Client Application
System Requirements - IATA Reader for Windows
- Windows 10, 8.1, 8, 7, Vista
- Microsoft .NET Framework 4.x
- 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.
Floating License Server: The license server component in an FL setup must undergo product activation. The activation is bound to a hardware ID. The hardware ID must remain constant for the license to remain activated. On a physical machine the hardware ID can be expected to remain constant (barring significant changes to the system). On a virtual machine, steps may need to be taken to stabilize the underlying hardware ID.
For example, with a license server installed on a VM hosted in a large cloud hosting environment, or 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 ID may change on each host, and the license server may become deactivated. In such a case anchoring the VM to a specific host, or otherwise stabilizing the VM’s hardware ID will be necessary.
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.