INIs
Sales32c.INI
There is an optional setting that can be used to allow Ticket Inquiry searches by WTP number on salespoints that do not have an Axess Smart Printer installed:
[Preferences]
AxessInquiry=TRUE
If the media needs to be encoded for Siriusware salespoint validation programs, the following setting also needs to be added:
[Preferences]
AxessEncodeSwipe=TRUE
It is possible to prompt a Sales operator with the guest name and photo when performing a %E (swipe discount) or %A (auto-sale) auto-validation using a pass number encoded within the Siriusware segment. Although this setting is not specific to Axess, it can be helpful when using the small black and white guest photos printed on Axess media.
[Preferences]
GuestPhotoVerify=TRUE
GuestPhotoVerifyTimeout=3
• GuestPhotoVerify=TRUE activates the functionality
• GuestPhotoVerifyTimeout determines the number of seconds before auto-closing the dialog. Setting this to 0 forces the operator to click OK to close the GuestPhotoVerify dialog.
Ports.INI
The following settings are required for AXCoding:
[SmartPrinter]
Port=Number (comport used by the Axess smart printer)
POS=Number (number that uniquely identifies the physical computer and salespoint ID; can be a value of 1 to 199)
Project=Number (site number – is the same on every computer)
Type=2 (this is the default value used for the SmartPrinter; if encoding with a SmartReader, set this to 6).
For the Sales Host or any other salespoint where only WTP records are generated and cards are never encoded (for example, call center salespoints that do not have Axess Smart Printers installed), it is still necessary to add the POS= and the Project= setting, but do not include a Port= setting as it causes the salespoint to continually fail when attempting to initialize the (nonexistent) printer. Also, remember to add the full list of POS numbers to Axess! Any transaction performed in Siriusware containing a POS number that does not exist in Axess is rejected by the Axess interface.
Scanned input using the Axess gate keys off the presence of a % at the beginning and is processed just like input to GateKeeper module directly. GateKeeper module has the ability to connect to piicom.ocx and piicom.dll. In order to connect to a Team Axess gate, these two components must be registered somewhere on the system. In addition, the proper .INI settings must be in place:
[PiiCom]
Enabled=TRUE
IP=192.168.0.99
Side=1
OpenTime=1
RFPrefix=Y
ScanPrefix=P
OpenTime is the number of seconds to flash the gate to allow someone to go through if a valid scan is received. Side is 1 or 2 for a double-sided gate. RFPrefix is used to validate the chip ID of the pass read before it is sent to SalesEZ application. The RF chip ID is an eight-digit hex number that is converted to decimal. Similarly, ScanPrefix is used for scanned content, but the raw number is passed with the prefix to SalesEZ application.