Specifications

Configuration 2- 1
C HAPTER 2
CONFIGURATION
This chapter covers options for configuring Point-of-Sale normally carried out by an administrator before
the system goes into general use. It covers the following topics:
• “Modifying Parameters”
• “Defining Security with Roles”
• “Reason Codes”
• “Configuring Transaction ID Lengths”
• “Configuring RMI Time-outs”
• “Configuring Third-party Tender Authorization”
• “System Settings”
• “Adding or Changing Language Bundles”
• “Configuring Logging “
Modifying Parameters
Point-of-Sale includes many configurable parameters; these parameters are used to control flow, set
minimums and maximums for data, and to allow flexibility without recompiling code. Most parameters
can be modified through the Point-of-Sale user interface. This section describes those parameters, which
are stored in XML files.
Note: The Point-of-Sale system can also be configured through system settings and reason codes.
System settings are values, set in the database, that control application behavior in a manner
similar to parameters. For more information, see “System Settings” on page 2-16. Reason codes
enable administrators to configure lists of options that are offered to the application’s users; see
“Reason Codes” on page 2-10.
The XML parameters are stored in a set of related parameter XML files, and editing those files is another
way to change parameters. Parameters not visible in the Point-of-Sale interface can be modified in the
XML files. For parameters that establish company policies, you can create files for corporate and store-
level defaults; see “Parameter File Hierarchy” on page 2-3.