Integration Guide

Software Description
______________________________________________________________________________
WaveWorks PSS, Integration Guide, 1.10 Page 99
© 2000, Symbol Technologies, Inc. February 1, 2000
8.8.4 PSSTransactionFile Processing
8.8.4.1 File-Based Interface
At the conclusion of a shopping trip (when a hand held terminal is returned to the dispenser or
the End of Trip barcode is scanned), a PSS transaction file is created and placed in the transfer
directory. Once the file is properly placed in the transfer directory, the processing for a PSS
transaction file is complete in the file-based interface. Custom code must be developed to
provide the transfer mechanism to the POS system.
8.8.4.2 4680/4690 Interface
The IBM SA Personality implementation of the POS API uses the IBM product RCO. The RCO
API provides access to the POS files on the POS controller over a LAN. It is described in the
IBM manuals:
• “Retail Connectivity OptionVersion 2.4.1 including OS/2 appendix - Product Reference”
dated September 15 1994.
• “Retail Connectivity OptionVersion 2.3 - User’s Guide” dated November 1996, which
covers both OS/2 and NT
The POS Interface consists of a service (PssPosService) that includes a modified version of the
POSAPI from Version 5.0 of the PSA. The POSAPI provides the interface between the PSS
Controller and the native 4680/90 POS. It provides the PSS Controller with file access to data on
the native POS controller.
When a hand held scanner is returned from a shopping trip, a PSSTransactionFile, according to
the format listed above, is created in the transfer directory. The PssPosService scans the transfer
directory at a regular interval. On detection of a file, the PssPosService handles transfer of the
information in the transaction file to the 4690 controller by writing the transaction information
into the Scan-In file on the POS. The frequency at which the PssPosService scans the directory
is specified by the system setting PSStransactionFile/MonitorInterval.
8.8.4.3 POS Emulation (Demo System)
Under normal conditions, the PSS shopping trip creates PssTransaction files and places them in
the transfer area for a POS to process. The PssFileMonitor process is configured to ignore these
files and not attempt to move them or process them, since the store POS (PssPosService) will be
processing them. For testing and demonstration purposes, when access to a POS system is
unavailable, the System Setting values for the PSSTransactionFile can be modified to cause the
PssFileMonitor to detect them and activate a POS emulation transaction. This transaction reads
PSSTransaction files (Scan-In) and creates corresponding POSTransaction files (ScanOut) which
are in turn detected and processed to complete the full shopping transaction cycle and unsuspend
the customer record (customers are suspended until trips are completed).