This article provides details the tasks necessary to migrate the PockeTracker RG v3 (also known as RapIDtrack Gateway) system to a new server. This includes the back-end Microsoft SQL database and the front-end Microsoft Internet Information Services (IIS) PockeTracker website. 

System Requirements

Note: While it may be possible to run the PockeTracker Gateway on systems below with the minimum specifications listed, those systems will not be supported by Vision Database Systems.

Web Server Requirements


Static IPv4 Network Address – The PockeTracker Gateway requires a static (non-changing) IPv4 network address. The client mobile devices will point to the IIS web server's network address. If the server's IPv4 network address changes the mobile devices must be reconfigured with the new IPv4 address to avoid network connectivity issues. This scenario can be avoided by assigning a static IPv4 address to the server.

Firewall exception - The PockeTracker Gateway will use HTTP port 80 and HTTPS port 443. HTTPS is optional and is not required for PockeTracker to operate. If using HTTPS you must keep HTTP port 80 open, although data will not be sent over HTTP.

HTTPS - If using the HTTPS option you must acquire a FQDN SSL certificate. Wildcard certs are not supported.

Hardware & Operating System

System Requirements

Operating SystemWindows 7 Pro, Server 2008 R2Windows 10 Pro, Server 2012 or later
HDD Space10GB Free50GB Free
ProcessorDual-Core Intel CPUQuad-core Intel CPU
NetworkWired LANWired LAN

Open Server Manager and install IIS with 4.5 .net extensibility.

Internet Information Services (IIS)

Server Roles

Web Server (IIS)


.NET Framework 4.5


Web Server Role (IIS) Services

Application Development

.NET Extensibility 4.5


ISAPI Extensions

ISAPI Filters

Migrate the MS-SQL Database

  1. Archive the database
  2. Restore the backup on the new database server
  3. Recreate SQL logins if necessary
    1. The pocketracker SQL login requires the db_datareader and db_datawriter permissions on the PockeTracker database.

Database Connection Setup

Create a 64-bit ODBC DSN on the web server to allow the PockeTracker Gateway to access the Microsoft SQL PockeTracker database.

  1. Open the 64-bit ODBC Data Source Administrator (c:\windows\system32\odbcad32.exe)
  2. Click Add > SQL Server > Finish
  3. Enter a Name for the connection and enter the server name. Click Next
  4. Choose "With SQL server authentication..." radio button
  5. Enter the pocketracker username and password
  6. Enable "Change the default database to.." and pick the PockeTracker database. Click next, Finish, then OK

PockeTracker Installation

  1. Execute PockeTrackerGateway_x64.exe on the Web Server.
  2. Choose to install PockeTracker onto the default website, port 80.

Migrate the PockeTracker App_Data folder that contains the license file, user database, and reports.

C:\Program Files (x86)\Vision Database Systems\PockeTrackerGateway\WebAPIGateway\App_Data

Migrate the Gateway Configuration

We recommend copying the Gateway configuration file to the new server.

Migrate the Gateway configuration

The Gateway configuration file is located in the Program Files (x86) directory.

C:\Program Files (x86)\Vision Database Systems\PockeTrackerGateway\OdbcGateway\GatewayConfig.xml  

Copy the file to the new server in the same path and then restart the ODBC Gateway service. If the new server's external IP is different from the original server IP you will need to visit Gateway Settings to select the new IP address and then restart the Gateway. 

(optional) Setup the Gateway service to access remote photo files

The PockeTracker Gateway is able to read cardholder photos located on the local disk of the web server or a remote shared folder. When reading photos on a remote shared folder, special consideration must be taken to allow the Gateway to access the files.

Add a Windows user to the remote photo share making sure the user is granted the read security permission.

Then, apply that Windows user account to the ODBC Gateway service.

PockeTracker can then access remote photos by using a UNC path such as \\remoteserver\photos.

Configure a Log On account for ODBC Gateway service

  1. Open Services on the IIS Web Server
  2. Start > Settings > Administrative Tools > Services
  3. Right click ODBC Gateway > Properties
  4. Click on the Log On tab
  5. Enter a valid Windows account and password
  6. Click OK
  7. Restart the ODBC Gateway Service

First Time Login

Use Google Chrome, Firefox, or Edge web browser to access the PockeTracker website at http://localhost/Gateway. Replace localhost with the name of the Web Server.

Log in using the following credentials:

username: administrator

password: sdiqpids

Upon successful logon you will see Welcome to PockeTracker!

If the Gateway is setup correctly browsing to Admin > Terminals or Admin > Profiles will return the Terminal and Profile lists.


PockeTracker requires a valid license key to operate the client PockeTracker software and perform mobile lookups. To request a license, or apply a license please follow the below steps.

Request a License

  1. Use Chrome web browser to open the PockeTracker Gateway then log in as Administrator
  2. Click Admin > System Configuration
  3. Click the Licensing tab
  4. Copy the Machine Code string to clipboard (select all, then Right Click > Copy)
  5. For best results, paste the license string into a notepad text file
  6. Email the license string file to

Apply a License

  1. Use Chrome web browser to open the PockeTracker Gateway then log in as Administrator
  2. Click Admin > System Configuration
  3.  Click the Licensing tab
  4. Select and erase the old license string found in the License String field
  5. Open the license file obtained from Vision Database Systems and copy the license string into clipboard (Edit > Select All, Edit > Copy)
  6. Paste the new license into the License String field (Right Click > Paste)
  7. Click Validate License
  8. The License Expiration Date will now display the new expiration date and the number of licenses will be displayed