Integration Guide
Table Of Contents
- I
- Introduction
- Architecture Overview
- Hardware Requirements
- PSS Software Installation
- Install NT 4.0 Server
- Install the NT 4 Service Pack
- Install Internet Explorer 4.01 Service Pack 2
- NT Option Pack Install
- Install the Video Driver
- Create and Format the Database partition
- Desktop Cleanup (optional)
- Install Microsoft SQL Server 7
- Create and Configure the PSS Database
- Install Microsoft Access
- Internet Explorer 5.0 with Task Scheduler install
- Install WaveWorks
- Install PSS Runtime System
- Install Waveworks Development Studio
- Install PSS Development System
- TFTP Configuration
- DHCP Configuration
- Create an ODBC Data Source
- Load Initial Data
- MS IIS Configuration
- Obtaining Access to PSS System Administration Screens
- Configure Task Scheduler
- Configure Unit Management
- Configure Licensing
- Configure the NBQMAIN Service (IBM 4690 POS Only)
- Setup NT System Log
- Configuration of the PSS System
- Validation of System Operation
- Directory Listing of PSS Folders/Files
- Software Description
- _
- Hardware Overview
- Software Components
- Database Access
- Start of Shopping Trip Processing
- Shopping Trip Processing
- End of Shopping Trip Processing
- Shopping Trip Message Log Entries
- Fatal Messages:
- PSSTransactionFile Processing
- POS Transaction File Processing
- Item Record File Processing
- Customer Update File Processing
- PSS Services
- _
- Customizing the PSS System Software
- Custom DisplayServer Scripts
- Custom Services
- Custom Business Objects
- User Exit DLL
- Available User Exit Functions
- UE_PreProcessItemFile
- UE_PreProcessItemRecord
- UE_PostProcessItemRecord
- UE_PostProcessItemFile
- UE_PreProcessTaxFile
- UE_PostProcessTaxFile
- UE_PreProcessPOSTransFile
- UE_PreProcessPOSTransRecord
- UE_PostProcessPOSTransRecord
- UE_ProcessEODRecord
- UE_PostProcessPOSTransFile
- UE_PreProcessPSSTransFile
- UE_PreProcessPSSTransRecord
- UE_PostProcessPSSTransFile
- UE_CalculateItemPrice_Method10to20
- UE_RescanLevelCalculation
- UE_Pre-RescanDetermination
- UE_PostRescanDetermination
- UE_PreProcessMarketingMessage
- UE_LoginAuthorization
- System Administration Interface
- Specific Features
Customizing the PSS System Software
______________________________________________________________________________
WaveWorks PSS, Integration Guide, 1.10 Page 107
© 2000, Symbol Technologies, Inc. February 1, 2000
• Severityrepresents the severity of the condition being logged. A System setting
value, subname "Trace_Level", is maintained for the Facilities that log messages.
If the message severity value is less than the severity value specified in the
LogMessage call, the message is not written to the log. For instance, if the
Trace_Level is set to 2 (Warning), then messages with a severity value 1
(Informational) are not written to the log, but messages logged with the severity 3
(Error) are written to the log. The value 2 is the default Trace_Level value set for
most facilities by the PSS installation scripts. The Trace_Level values can be
modified using the System Settings Page on the PSS Administration terminal.
The allowable values for severity which can be specified in a LogMessage call are:
• PML_DEBUGlevel 0, used to log messages helpful in debugging code during
development. Examples are logging the values of parameters used or calculated by
software. The default Trace_Level settings suppress these messages.
• PML_INFOlevel 1, informational messages that typically log the operational status of
software. Examples are positive status about the completion of an operation (Function
XYX completed successfully). These are messages that would not normally be enabled in
the System Log because there would be many such messages cluttering the log and they
would obscure more severe messages. If there were a perceived system problem, then
troubleshooting procedures might suggest setting the Trace_Level to 1 so these messages
would be written to the log and could be reviewed to see if software functions were being
performed as expected.
• PML_WARNINGlevel 2, Error conditions which the PSS software is readily able to
recover from. The default Trace_Level settings write these messages to the log. These
messages may or may not indicate a system malfunction.
• PML_ERRORlevel 3, Error conditions that indicate a system malfunction that is causing
operational errors. The default Trace_Level settings write these messages to the log.
Some corrective action will normally need to be taken to reinstate proper system operation.
• PML_FATALlevel 4, Critical Error conditions that stop the operation of PSS system
components. These messages typically accompany other indications such as turning the
PSS Administration terminal's Main Menu traffic light red and the disabling of the ability
of PSS to perform shopping activities.
• PML_ALWAYSlevel 10, Status messages that do not indicate error conditions, but
which should always be written to the System Log. Examples are startup and shutdown
messages logged by PSS services or activation messages logged by scheduled tasks.
See the PssMsgLog.h header file for more programming details.