Introduction & Architecture

This document provides support information for the Order builder App and includes supporting details for functionality developed in Kitchen iQ and Aztec to support Order Builder.

Order Builder App – Components

OrderBuilderApi Service

• Hosted on Aztec Site PC

  • Windows Service Name: OrderBuilderApiService

  • Directory: C:\Program Files\Zonal\OrderBuilderApi\

Features

• Customer Cache: Stores data in memory
  Must not be rebooted during operation

• Future Orders: Storage and handling of Future Orders (due >24h)

• Log files: Logs\OrderBuilderApi-20210421.log

Kept for 7 days but backed up by Zonal service

• Heartbeat API: http://localhost:50015/heartbeat 

• Customer Cache Status: http://localhost:50015/customers/status
  If allows one to check if there are delivery data in the Customer Cache or not. If the “max_time” > now, it means the service MUST NOT be rebooted

• Database: FutureOrders db – on SQL server instance 

 

OrderBuilderApp Serivce

• Hosted on Aztec Site PC

  • Windows Service Name: OrderBuilderAppService

  • Directory: C:\Program Files\Zonal\PizzaOrderApp\

• Acts as:

  • Web Server – hosts files from “wwwroot” (content of files served as web page to the till) - Displayed on tills, overlaying the EPOS program

• Proxy:

  • ZCF

  • PHDV Postcode Validation

• Log Files:

  • Logs\OrderBuilderApp20210421.log

  • iOrder - C:\Program Files (x86)\Zonal\Aztec\Log\iServe_Log_PB0_20210414_070834.log

Pizza Builder App (Client)

• Web application run in Chrome in Kiosk mode

  • Loads http and javascript files from: C:\Program Files\Zonal\PizzaOrderAppSetup\wwwroot on Site-PC (hosted by Pizza Builder App Server)

  • Run by EPOS

  • Invokes calls to:

    • ZCF - ▪    But only If “useProxy=false”

    • Pizza Builder App Server - If “useProxy=true” than ZCF calls are made through this service in