StoreLine Product Overview &

Architecture
 StoreLine application &
services
 All retail business logic runs in windows Services
 Sales processing & management
 Activation of price changes and database updates
 Synchronization & integrity
 Automatic tasks: batches, reporting, etc.

 User interface after logging –on

 Menus
 Reports
 User alerts
 StoreLine Components
POS
MFS1

QDX

SQL
MFS2

QDX
MFS1: The Primary Server
Tasks that involve
User
User-Interface are
Application
loaded as a program.
The OS must be

After OS Login
Task Runner
(EOD) logged on for these to
run.
System Viewer
and Monitor
However, the user
application does not
have to be running.
Alert Server

Q-dex
database Batch Server
Tasks that do not need

Service Mode
SQL Transaction User-Interface are
database
Process Server loaded as a service.
As such, these
SQL Server RSMSRV services run even if
there is no user
Operating Q-Dex
logged on to the OS.
System Server All the services are
started by
POS_Srv_Manager.
 POS_Srv_Manager
 Deploy one OS-Service
 POS_Srv.exe invokes child processes:
SrvStart.bat loads all StoreLine services
SrvStop.bat unloads all StoreLine services
MFS1: The Primary Server
User
Application

Login
After OS
Task Runner Monitors services are loaded.
(EOD) Monitors disk space. Shows major
logs.
System Viewer
and Monitor
Handles screen pop-ups,
email, and pagers. Treat both
Alert Server
POS and MFS alerts.
Q-dex
database
Executes both time activated
Batch Server
and manual activated batches.

Mode
Service
SQL Transaction Processes both SQL and
Process Server
database Q-dex transactions

SQL Server RSMSRV Handles all communications

and business logic with POSs
Operating Q-Dex
System Server
Upload QDXs to the memory
MFS1: The Primary Server

User
Application

Login
After OS
Task Runner
(EOD)

System Viewer
and Monitor

Alert Server

Q-dex database
Batch Server
A Closer look
…at RSMSRV

Mode
Service
SQL database Transaction
Process Server

SQL Server RSMSRV

Operating
Q-Dex Server
System
 StoreLine MFS-POS Connection

MFS1
POS

RSM SRV
QDX
RS
M
SR
V
SQL

MFS2
V
SR
M
RS
RSM SRV
QDX
 StoreLine MFS-POS Connection

MFS1
 MFS1 & MFS2 connecting to the
sql on MFS1 (Frontoff DB exist
only on MFS1)
QDX  The POS transaction are been
written on MFS1 and MFS2
transact.qdx
SQL  Every EOD MFS2 will sync with
MFS1 (according to the DB)
 When MFS1 services is down,
MFS2 MFS2 can be sync with the POS
 When MFS1 computer is down
the transaction will be transfer
to MFS2 until the DB on MFS1
QDX will be up (no GUI will be
available).
 The Database

SQL Database QDX Database

 DB Name: FrontOff  Subset of FrontOff

 Holds full set of StoreLine data  Exist as DB on the Till and
 Includes (e.g.): MFS2
 Settings (parameters)  Only holds data relevant to the
 Retail data (items, POSs ability to trade (e.g. some
promotions) parameters, some retail data)
 Sales (item and cashier sales)  Also holds daily download and
 History data (item sales, upload data:
reports)  Transactions (POS to servers) –
 Master of the Data Using Transcli and Transexe
 Maintenance (servers to POS)
 HOSTS File

 Mandatory lines:
 IP of MFS1:
192.22.33.1 MFS1
 IP of POS1:
192.22.33.11 POS1
 Subnetmask:
255.255.255.0 SUBNETMASK
 Optional lines:
 IP of MFS2 and W/S:
192.22.33.2 MFS2
 IP of POS (may be non-contiguous)
192.22.33.7 POS2
 Located under C:\WINDOWS\system32\drivers\etc