At the moment onetap.mobile server runs as a web application in Windows Internet Information Services (IIS). This may change in the future, but for now, this is the case. It requires IIS to be installed on the Windows machine, along with various add ons to allow for ASP processing, and .NET functionality, then for the application to be added to IIS.
This must be run on a Windows based server. It has been successfully installed on Windows 7, 8 and Windows Server 2012, and should run on any newer versions of Windows, including Windows 10.
IIS (Internet Information Services)
IIS must first be installed. This is usually shipped as part of Windows, and can be added using the Add Windows Features tool.
Go the the Internet Information Services Tab, then Web Management Tools. Turn on the IIS Management Console.
Next down to the World Wide Web Services, then Application Development Features. Turn on ASP.NET 4.5. This will also select a bunch of other features that are required.
Click OK, and it will install the features, required, then probably restart.
See this example of a setup running on Windows 8.
This is probably installed already as part of Windows 8 and newer. But may not be. If it’s not then the onetap.mobile server app will not run. Windows 7 may not have it by default, so is needed to be installed manually.
If it needs to be installed, then do a google for .net 4.5 download, or try following this link https://www.microsoft.com/en-nz/download/details.aspx?id=30653
Our application needs to be installed manually. Follow the following steps.
- There are three different version of onetap.mobile servers.
- OnetapMobileRESTIIS: IIS version.
- OnetapMobileRESTSA: Windows application version.
- OnetapMobileRESTService: Windows Service version.
- IIS version installation below:
- Copy the OnetapMobileRESTIIS folder so it becomes C:\inetpub\OnetapMobileRESTIIS.
- Start IIS Manager.
- Add a Website.
- Call it OnetapMobileRESTIIS.
- Set the physical path to C:\inetpub\OnetapMobileRESTIIS.
- Binding should be http, All Unassigned, and port 2080.
- Edit the OnetapMobileRESTIIS Application Pool
- Ensure .NET CLR version is set to v4.0.30319
- Managed pipeline mode is Integrated
- Create another directory line. c:\Logs\OnetapMobile
- This is the folder that log files generated by the onetap.mobile server will be created in. It can prove itself very valuable in debugging any errors within the system.
- You may need to give the IIS_IUSRS user, permissions to access this folder. Give them permission to do everything.
- Please check if the log file is created successfully after all mobile devices setup are done. a Internal Server Error may be caused if the server fails to create a log file.
- Using Notepad or similar, edit the Web.config file found in C:\inetpub\OnetapMobileRESTIIS.
- Mark the server is hosted on the local <add key=”Registration.ServerHost” value=”localhost” />
- Check that the connectionString says something similar to<add name=”OTData” connectionString=”DataSource=localhost;Database=otdata” /> Where the datasource is the IP of the server, and Database is the name of the DB in that machine. You could replace it with something similar to<add name=”OTData” connectionString=”DataSource=IBSERVER;Database=C:\Program Files\WizBang\Waiter\OTData.fdb” />
- Check the ApplicationLog.LogDir matches the directory mentioned above. Leave the other ApplicationLog setting alone, unless they need to be changed. The default is for up to 64 log files to be created, of up to 8MB in size. This shouldn’t be an issue for most circumstances.
- Ensure the Registration.ServerHost points to the server running OTServer. Usually localhost or IBServer.
- Only Brazil clients needs to worry about Fiscal. Leave it off in all other circumstances. If enabled, you will need to provide a path to the auxiliary file.
- The other setting relate to behaviour within the onetap.mobile application. Hopefully they are obvious enough to not need an explanation
- Active payment method tab before finalizing sale when OK button is pressed in Quick Sale.<add key=”QuickSale.ConfirmPaymentMethod” value=”true” />
- Menu item filter (Temporary solution)
- onetap.mobile provides a way to hide items that no need to be shown in onetap.mobile.
- Set a comma-separated list of super item group ID in ItemFilter.ExcludeSuperItemGroupIDs value in config file.
- Set a comma-separated list of item group ID in ItemFilter.ExcludeItemGroupIDs value in config file.
- Keep value empty if there is exclude IDs.
- Example: <add key=”ItemFilter.ExcludeItemGroupIDs” value=”5,6,12,122″ /> <add key=”ItemFilter.ExcludeSuperItemGroupIDs” value=”1,2″ />
- Disable/enable quick sale
- To disable, set both TILLID and QSSALECATEGORYID to NULL in TERMINAL of OTData
- To enable, set TILLID to a exciting TILLID, and set QSSALECATEGORYID to 1 (SALECATEGORY is ‘Eat In’)
- Make sure the terminal and the till are NOT marked as deleted (value of WHENDELETED is not null), when enable quick sale
Local Server Testing
Open up a browser, and go to
You should see a screen similar to the image on the right.
This confirms that IIS has been installed correctly and is running, that .NET 4.5 is installed, and that IIS is hosting the onetap.mobile server correctly.
It doesn’t confirm that the database has been linked correctly, or that the system is licensed to use handhelds.
The mobile server application version is shown in gray after the name onetap.mobile in onetap.mobile page.
Assuming that the onetap.mobile application has been correctly installed. (The method for doing this will very likely be via google play, but this could be a manual method).
If the application starts and shows the login screen, then it’s installed.
You can now try testing from a onetap.mobile device.
The mobile APP version is shown at the bottom-left corner of login page in onetap.mobile APP.
Ensure the settings point to the correct local URL, and to a valid mobile Terminal ID.
Terminal ID: 5
Try to log on.
If there is an error message, then try to fix the issue, referencing the table to the right here.
If you can log in, then you will see the list of current tabs. Try to print a summary, or place a test order.
Pat yourself on the back for a job well done.
|Common Errors||Potential Solution|
|Database connection error||Ensure the connectionstring in web.config is valid|
You may be out of range
|Try again, as the web app may still be starting in IIS.If this message continues, then check the network settings of the device, and check the URL in the onetap.mobile settings.You can try connecting to http://192.168.0.203:2080 in a browser. You should see a similar screen as the image above.|
|System not licensed
Please speak to your Onetap reseller
|First check that OTServer is running, and is licensed for using handhelds.
Then check that the Registration.ServerHost in web.config is valid
|Incorrect login combination
Please try again
|You’re actually very close, as everything is working properly. You just need to enter a current Staff No and PIN.|
|Invalid Terminal ID in settings||Check that the terminal ID in onetap.mobile settings matches an active handheld Terminal ID in the database.|