You will need one license per scanning device (eg. an Android phone or tablet) that you will be using simultaneously. Besides that we recommend buying at least one extra license per server for being able to put in a backup device in case of a hardware failure.
Client licenses are not tied to the specific device but are only counted by the server. It calculates the number of used licenses by counting how many unique devices have scanned barcodes within the last 24 hours. As long as that number never exceeds the number of purchased licenses you can swap around devices as you please.
In case you are using multiple Local Ticket Servers at different venues you need to buy separate client licenses for each server, since the client licenses are linked to the server license.
If you are not using the Local Ticket Server but instead validating directly against SABO you still need to buy the same number of licenses as if you were using a Local Ticket Server.
Yes, for Android clients you can use the app directly against SABO and hence not need the Local Ticket Server. For best connectivity and full-featured operation we do recommend using a Local Ticket Server though.
Turnstile access control systems (that are not based on Android) do require a Local Ticket Server though.
The Local Ticket Server (LTS) runs as a VirtualBox virtual machine on your own computer running Windows/Mac/Linux/Solaris (see details). For most locations any modern desktop or notebook will do. Recommended minimum hardware requirements for the host machine is 300 MHz x86 processor and 1 Gb RAM. Lower speed processor and somewhat also less RAM will of course affect how many bar codes can be processed per hour so depending on your needs a computer with higher performance might be required. Also be aware that the filesystem may not be FAT32, it must be at least NTFS (Windows) or Ext3 (Linux) in order to handle the large file sizes.
If LTS will be processing more than 70,000 ticket scans per hour (~1,200 per minute) high-end hardware is recommended - on which the LTS can handle up to 360,000 ticket scans per hour (~6,000 per minute).
The more memory that can be allocated to the virtual machine the better. In a benchmark test an increase from the default 512Mb up to 4Gb of RAM on the virtual machine resulted in a performance increase of 20%.
The LTS must be connected to a LAN which all the clients must connect to as well. There are no special requirements for the network but we highly recommend using industrial grade routers and switches. If you are using Wifi for the clients (we recommend ALWAYS connecting LTS via cable - and because of driver issues it might not always work on Wifi either) make sure you use a WPA wireless network to protect against intrusion.
In case you run multiple LTS servers it is critical that only one server is connected to a given network at any time. Otherwise conflicts will arise.
Make sure you follow the instructions in the documentation by going to the machine settings of the virtual machine and under the network settings selecting "Bridged adapter" and select the correct adapter below.
Also check these issues.
Make sure you follow the instructions in the documentation by going to Settings -> Security (or Applications on older Android versions) and put a checkmark in "Unknown sources" to allow installation of non-Market applicatons.
Yes. A portal/gate can be set to only allow exit scans - where a preceeding entry scan is required for allowing person to exit. Portals/gates can also be set to only allow first-time validations, only allow re-entry, or allow both. People can therefore enter, exit and re-enter as many times as they like.
1. The host computer (the one running VirtualBox) is not connected to a network with a DHCP server and therefore is not getting an IP address.
2. The host computer is connected to a network via wireless instead of via an ethernet cable. The server is only guaranteed to work with an ethernet cable since wireless is not natively supported by VirtualBox.
3. The MAC address of the network adapter has been changed in the network configuration of the virtual machine. Ensure it is set to 08002715BD18.