Access Control Software

Documentation

Installation of Local Ticket Server

  1. Install VirtualBox on the machine that will be running the Local Ticket Server. Unless you will be using many scanners basically any modern desktop or notebook computer running Windows/Mac/Linux/Solaris will do (see details). For best stability a Linux operating system is recommended.
  2. Download the Local Ticket Server software (a virtual machine) from your license page and unpack the download .7z file (using 7-Zip) into the folder where VirtualBox stores the machines.
  3. Start VirtualBox and add the machine (go to the menu Machine -> Add).
  4. If the machine has lots of physical RAM you can increase the amount you delegate to the virtual machine, eg. half of your memory. It will improve the performance of the server.
  5. Check in the machine settings that the network adapter is attached to a "Bridged adapter" and that the correct adapter is selected below. Sometimes it's also required to set Promiscuous Mode to Allow All - in case the server does not receive an IP address or complains about the network on startup. Also be aware of these issues.
  6. Start the virtual machine and let it boot up.
  7. In a browser anywhere on your network and go to the address written on the virtual machine console.
  8. Login with the username and password noted on the license page/e-mail.
  9. Go to Options and first enter your configuration details, then run an update of the software at which point you will need to enter the license code from your license page/e-mail.
  10. Once you have set everything up you can monitor the scanning process from the dashboard page.
  11. Also, please go through this checklist regarding the server.

Installation and configuration of Android app

  1. Install the app on your device by searching for "SeatAdvisor" on Google Play.
  2. Start up the app and go to the Settings tab and set each one of the options. Here is a description of the ones that are not self-explanatory:
    • Server IP address: enter the IP address of the Local Ticket Server (it's shown on the console of the virtual machine). If you are not going to use the Local Ticket Server (LTS) and instead communicate directly with SABO you should enter the word "ONLINE" instead of an IP address. Just remember that either all devices must scan against SABO or against LTS. If using a mixed setup the same ticket will be valid two times.
    • Portal: if the desired portal is not found in the list you need to manually enter the portal ID (a number) that this device is used at. To locate the portal ID do the following:
      1. Log into the SABO website with your operator login.
      2. Go to Event Tools -> Portals.
      3. Right-click on the desired portal and choose "Inspect element". A window will come up where you see something like this:
        <option value="1005562">...</option>
      4. The number you see there is the portal ID.
      Selecting "- No portal -" or entering "0" means that you don't use portals for this event/performance.
    • Performance ID: if the desired performance is not found in the list you need to manually enter the performance ID (a number) of the event that you will be scanning barcodes for. If you want to select multiple performances you can enter the performance IDs in the manual entry field, separated by a comma.
      1. Log into the SABO website with your operator login.
      2. Go to Events -> Manage Performances
      3. Select the desired event and click "Go".
      4. Right-click on the desired performance and choose "Inspect element". A window will come up where you see something like this:
        <option value="1952524">...</option>
      5. The number you see there is the performance ID.
    • Organization name, short: enter the short name of your organization as it is defined in SABO. You can see your short name (all upper case within parenthesis) in the top right dropdown box when you log into SABO.
    • API Key: This is optional, but if you need to enter it and don't know it, please contact SeatAdvisor.
    • API Secret Key: This is optional, but if you need to enter it and don't know it, please contact SeatAdvisor.

Using the Local Ticket Server

  1. After each time you are done using the server first shutdown the virtual machine, then the computer itself. Don't just hibernate or sleep the computer with the virtual machine running.
  2. Before starting to use the server ensure the UTC time shown in the console of the virtual machine is correct. If not you can either login to the administration interface and resync the clock under Options, or you can reboot the virtual machine. Verify that the clock has been adjusted.
Terms & Conditions
 
Contact Info: