Supporting

1

• Supporting Troubleshooting MobilePOS

2
MobilePOS First Principles

• Allow wait staff to take orders from customers
  using mobile devices
• Provide a subset of WTA functionality
• Allow user to complete full check lifecycle
• Create check
• Save Check
• Recall Check
• Tender Check
• Be simple, reliable and intuitive to use

3
MobilePOS Components

• SQL Database
• Web Services
• Mpos Sync Application
• Mpos Config Application
• Mpos Transaction Processing Service
• Order Monitor
• Mpos Client
• Mpos Client Database

4
SQL Database

• Store for all information relating to Mpos
• Mpos Configuration Data
• IG Configuration Data
• Screens
• Users
• Menu Items
• Modifiers
• Choice Groups
• Etc
• Data for checks created in Mpos

5
SQL Database

• Stored Procedures
• No Mpos application contains hard coded SQL
  Statements
• Mostly contains transient information
• All IG data is pulled back periodically
• Only data that is not stored anywhere else is
• Service Area data
• Mpos check data
• Backups?

6
SQL Database

• Can exist on a clustered environment
• However SQL Components still need to be
  installed on Mpos server for the SDF creation
• Database is called OrderManager
• See history for Mpos for explanation of that!
• Under the hood

7
Web Services

• What are Web Services?
• Re-usable chunks of code stored on a server
• Called by a client application
• Accessed via HTTP
• Why are they used ?
• Just like stored procedures
• Centralization
• Reusability
• Distributed Workload
• Abstraction

8
Web Services

• Mpos Web Services
• All communication between HHT and Server
• Download config database
• Create check
• Recall Check
• Save Check
• Tender Check
• Everything!

9
Web Services

• Two types of Mpos web service
• Batch
• Save Check
• Interactive
• Save Print
• Recall Check
• Tender Check
• A look at Mpos Web Services
• Can be used for testing fundamentals if issues
  occur

10
MobilePOS Sync Application

• What it does
• Pulls configuration data from IG
• Manipulates simplifies it for Mpos
• Stores it in Mpos Database
• Refines it further and creates the SDF file for
  the HHT

11
MobilePOS Sync Application

• In more detail
• It is a console app no UI
• It is intended to be run on schedule or as
  necessary
• It should be run after any changes are made to IG
  config that affects the Mpos devices
• Users
• Screens
• Menu items
• Meal periods

12
MobilePOS Sync Application

• In more detail
• It pulls data directly from the IG database
  tables
• SQL Queries are stored in config files, not hard
  coded
• Data is stored in HOLDING tables and the live
  data is only replaced if the entire process is
  successful
• Final step is to generate a new SDF file ready
  for download to HHT
• New in V2.6
• The IG is parsed to only take the data that is
  needed
• Starts at Primary Screen for each meal period and
  trawls

13
MobilePOS Sync Application

• Sync Application Logs
• Stored in \Sync Logs folder on the server
• Each execution has its own log
• Take a look

14
Transaction Processing Service

• Takes transactions from the database and
  processes them in batch mode
• Passes them to the TPG
• Waits for a response
• Updates Mpos status accordingly
• Windows Service no UI
• Logs stored in \Order Processing Logs folder
• New log started at either
• Service start-up
• File size is aprox 1mb

15
Transaction Processing Service

• Runs on a 10 second cycle
• Will classify processing errors in two ways
• Fatal Error
• Invalid Employee
• Check already closed
• Invalid Profit Centre
• User will be notified
• Non-Fatal Error
• General comms errors with TPG
• KP Problems
• Will be re-queued for next pass

16
Order Monitor Utility

• Allows admins to view mPos activity
• Shows processing queues
• Allows you to get a high level overview of a
  check, or general status of Mpos environment

17
Mpos Configuration App

• Set the key data for the mPos environment
• General Info
• Server Addresses
• Usernames
• Passwords
• Service Area Info
• Terminal IDs
• Profit Centres
• Mpos Characteristics
• License Info
• Par Levels

18
Mpos Configuration App

• Global Data is stored in CONFIG.XML in the Mpos
  install directory
• Much of the data is encrypted for security
• Everything else is stored in DB tables
• - If any changes are made to config, run Sync
  Application and restart Windows Service so that
  changes are picked up

19
What do all the options mean?

• Options tab
• Use Seat Numbers
• Use Course Numbers
• Use Infogenesis Table Layout
• Allow Auto Numbering of checks
• Tender Only Mode
• Re-Stock Mode

20
What do all the options mean?

• Tenders tab
• Prompt for Gratuity
• Use Digital Signatures
• Allowed Tenders

21
What do all the options mean?

• Check Types tab
• Check type checkboxes

22
What do all the options mean?

• Stadium Seating tab
• Use stadium seating
• Sections
• Rows
• Seats

23
What can go wrong?

• HHT Issues
• Device lockups crashes
• Device reboot (1 9 red button)
• Hardware failures
• Warranty repair
• Loss of network connectivity
• No network coverage / inability to connect
• Device connected to network, but HTTP connections
  fail

24
Mpos Client App

• Runs on HHT
• The end users interaction with Mpos
• Consists of
• Exe
• DLLs
• Config .xml
• Images stored in \IMG folder
• SDF file (SQL Compact database)
• Communicates with Mpos server via Web Services

25
Other files on the server

• Config.XML
• Configuration data (back this up!)
• Query_config_vx.xml
• Contains the SQL queries used to retrieve data
  from IG
• Can be modified
• Be very very careful!
• Tender_query_config_vx.xml
• Contains info about how each tender verification
  code should be handled
• Colour_map.xml
• Translates IG button colours into XHTML standard
  colours

26
What can go wrong?

• Loss of network connectivity
• Go back to basics
• Exit Mpos
• Check network connections
• Check Internet Explorer can browse Mpos Server
• Check that Mpos client config has correct address
  for Mpos Server
• Check that a PC on same network can web browse
  Mpos server
• Check IIS is running on Mpos server
• Check that Web Services are running correctly

27
What can go wrong?

• Checks can be submitted to Mpos server, but do
  not get processed
• Ensure that Transaction Processing service is
  running
• Start Order Monitor application and look in the
  processing queue
• Is check pending or failed?
• Look in Transaction Processing logs for error
  messages
• Any unsuccessful response from TPG will be logged
• Look at TPG logs
• 99 times out of 100 it will be
• Comms related
• IG configuration related

28
What can go wrong?

• Common issues
• Menu Item / Employee not found
• Check already closed
• Check locked by WTA
• Invalid Profit Centre
• No response from TPG
• Unable to connect to SQL database
• Timeout issues between
• HHT Mpos Server
• Mpos Server and TPG

29
What Mpos doesnt do

• Assign check numbers
• Kitchen printing
• Generate receipt / sales draft texts
• Communicate with 3rd party systems
• PMS
• Shift4
• Etc
• Write any data into IG database tables

30
Limitations

• All the TPG limitations we know and love
• Cant split checks
• No part payments
• Cant cancel authorizations
• Only a subset of tender verification codes
  supported
• Cant assign course numbers properly
• Etc

31
Limitations

• Cannot tender offline
• Cannot do hold fire ordering

32
Process Walk Through

• Create a new check
• Recall an existing check and add items to it
• Tender a check
• Cash
• Credit Card
• GA
• Room
• Folio