360Store Point-of-Sale Administrator Guide Release 7.2.
Confidential ©2005 360Commerce. All rights reserved. 360Commerce and third-party specifications are subject to change without notice. Although every precaution has been taken in the preparation of this paper, 360Commerce assumes no responsibility for errors or omissions, and no warranty or fitness is implied. 360Commerce shall have neither liability nor responsibility to any person or entity with respect to any loss or damages arising from the use of the information contained in this paper.
TABLE OF CONTENTS Preface ix Chapter 1: Installation Installation Requirements 1-1 Supported Software for Clients (Registers) 1-1 Supported Software for Store Servers 1-2 Basic Computer Specifications 1-2 Peripheral Devices for Clients 1-3 Supported Hardware for Clients 1-3 Supported Hardware for Store Servers 1-3 Installing with the Install Script 1-4 Determining Server Tier 1-4 Installing the Database 1-5 Installing JMS 1-5 Installing JavaPOS 1-6 Installing Point-of-Sale on Machines 1-6 Populating the Dat
Setting the RMI Time-out for All Manager and Technician Calls 2-14 Setting the RMI Time-out for a Specific Technician 2-14 Configuring Third-party Tender Authorization 2-15 Enabling the Financial Network Technician 2-15 Setting the Merchant Number 2-16 System Settings 2-16 Adding or Changing Language Bundles 2-16 Naming Convention for Language Bundles 2-16 Creating a New Language Bundle 2-17 Configuring the System to Use a New Language Bundle 2-17 Configuring Logging 2-17 Chapter 3: Troubleshooting Viewing
LIST OF FIGURES Figure 2-1 Figure 2-2 Figure 2-3 Figure 2-4 Figure 2-5 Figure 2-6 Figure 2-7 Figure 3-1 Figure 3-2 Figure 3-3 Parameter Groups and Parameter List Screens 2-5 Set Access Screen 2-6 Add Role Screen 2-7 Set Access Screen 2-7 Reason Code Group Screen 2-10 Reason Code List Screen 2-11 Edit Reason Code Screen 2-12 Find Transaction Screen 3-2 Journal Display Screen 3-2 Del Queue Conf Screen 3-4 List of Figures v
vi Point-of-Sale Administrator Guide
LIST OF TABLES Table P-1 Table 1-1 Table 1-2 Table 1-3 Table 1-4 Table 1-5 Table 1-6 Table 1-7 Table 1-8 Table 1-9 Table 2-1 Table 2-2 Table 2-3 Table 2-4 Table 2-5 Text Conventions x Supported Software for Clients 1-1 Supported Software for Store Servers 1-2 Hardware Minimum Recommendations 1-2 Supported Hardware for Clients 1-3 Supported Hardware for Store Servers 1-3 Server Tier Logical Components 1-4 Point-of-Sale Install Script Information 1-7 360Store Subdirectories 1-9 360Store\pos Subdirectories 1-
viii Point-of-Sale Administrator Guide
PREFACE Audience The audience for this document is administrators and developers who install and configure the 360Store® Point-of-Sale application. Goals An administrator or developer who reads this document will be able to: • Install Point-of-Sale • Configure Point-of-Sale Feedback Please e-mail feedback about this document to 360University@360Commerce.com.
Text Conventions The following table shows the text conventions used in this document. Table P-1 Text Conventions Sample Description Italic text This is used for emphasis. It calls attention to crucial information and important terms defined in the text, for example, quantity on hand is .... This is used for text (in an application window or on a keyboard) that is acted upon by the user, for example, Click Next.
C H A P T E R 1 INSTALLATION This chapter provides information about the installation procedures for 360Store Point-of-Sale. 360Commerce provides an installation script for Point-of-Sale, but customer installations typically develop custom procedures which build on the existing scripts. Use procedures in this chapter to install a demonstration or initial register system and as a source of information for modifying installations.
Supported Software for Store Servers Table 1-2 Supported Software for Store Servers Required Item Supported Products Operating System IRES V 2 (SUSE Linux Enterprise Server 9) Windows 2003 Server Java 2 Platform, Enterprise Edition (J2EE), Version 1.4.2 DB2 v.8.2 MySQL 4.1.14 JBoss JMS 4.0.2 Websphere MQ Series 5.
Peripheral Devices for Clients JavaPOS is the industry standard for Java compatibility for retail-oriented devices. A committee of prominent retail vendors and end users maintains the standard. Some of the more common devices used with point-of-sale applications include bar code scanners, cash drawers, printers, keyboards, magnetic stripe readers (MSR), wedge keyboards, hard totals, and magnetic ink check readers (MICR).
Installing with the Install Script To establish an initial Point-of-Sale installation or to create a demonstration system, use the Point-of-Sale installation script as described in this section. Note that the installation script is not appropriate for all installations: • 360Commerce expects implementation teams to develop custom procedures for actual register installations, which may or may not be based on the script described here. See “Creating a Custom Installation” on page 1-12 for guidelines.
Installing the Database 360Store products such as Point-of-Sale and Back Office use the 360Store database. One 360Store database is typically installed in each store. Data stored in the 360Store database includes employee names, logon information, transaction data, and the inventory database. The database can be located on the store server or on a separate machine acting as the database server. The database must be installed before Point-of-Sale can be installed.
java.naming.provider.url=jnp://: Example: java.naming.provider.url=jnp://eqa4:1099 To install JMS on the client: 1. Edit the posenv.bat file by removing rem from rem call jboss.bat. This enables setting up the classpath for JBoss. 2. Check jboss.bat to make certain it points to the store server where JBoss is installed. 3. Remove the comm.properties file the pos/config directory.
The installation script asks some or all of the following questions. (Some questions do not apply to all Server Tier types.
Table 1-7 Point-of-Sale Install Script Information Item Default Description Tender Authorization Details Host name www.isdwhq.co m Host port - 15713 Merchant number - 0001 Swing For the ISD Tender Authorizer, provide details. User Interface Option Choose from Swing (a standard swing interface) or Image (custom images for buttons and other graphics are provided). Populating the Database The 360Store database needs to be built with tables, fields, and initialized data.
Results of a Point-of-Sale Installation The default root directory for 360Store applications on Windows is c:\360Store. The default root directory for 360Store applications on Linux is /opt/360store.
2. If you are not running a collapsed implementation, start the store server: StoreServerConduit.bat When the message TierManager Started appears, the server has started. The server component does not have a user interface. Collapsed implementations do not need to launch a separate store server. 3. Start the registers. For each of the Point-of-Sale registers, execute the conduit script that starts the Point-of-Sale client component. For collapsed implementations, the command is: CollapsedConduitFF.
Installing Point-of-Sale Install Point-of-Sale as described in “Installing with the Install Script” on page 1-4, then return to this section. Replacing Security Files in the Alternative JRE Use the security and policy files from the Point-of-Sale installation with your alternative JRE. Copy the java.security and java.policy files from the \jre\lib\security directory to the corresponding directory in your alternative JRE, such as c:\wsdk_v51\appserver\java\jre\lib\ security.
Creating a Custom Installation A custom installation of Point-of-Sale can use one of several approaches: • Install Point-of-Sale using the install script on a reference machine, and copy the resulting installation to other machines. - With this method, you can change the configuration settings of the installation as described in Chapter 2, “Configuration,” until the installation works as desired, then propagate those configurations to other machines.
C H A P T E R 2 CONFIGURATION This chapter covers options for configuring Point-of-Sale normally carried out by an administrator before the system goes into general use.
Each parameter belongs to one and only one group, and there is a security role for each group, so parameter access can be restricted to particular groups if desired. See “Defining Security with Roles” on page 2-6. Your choice of how to change a parameter matters: if you change a parameter with the Point-of-Sale interface, the value of that parameter is not loaded on other registers.
This example shows some standard properties: Table 2-1 Standard Parameter Properties Property Description type final The type of parameter value. Can be Y or N; if Y, it reverses the normal file precedence for the parameter. See the next section, “Parameter File Hierarchy,” for more information. If Y, the parameter does not appear in the Point-of-Sale interface. A structure that defines valid values for the parameter. In the example, the tags define a range of floating-point currency values, from 0.
The following table shows two examples of competing parameter files, along with the actual value that Point-of-Sale ends up using. Table 2-3 Sample Parameter Values and Results Parameter File corporate.xml store.xml workstation.x ml Value used by Point-of-Sale Maximum Travelers Check Amount Value 100 75 50 Final property Parameter File final="N" corporate.xml final="N" store.xml final="N" workstation.
Within Point-of-Sale, there is no indication of the source of the value of a parameter. The value you see displayed on screen could come from a variety of XML files. See “Parameter File Hierarchy” on page 23 for more information. To use the Point-of-Sale application to change a parameter: 1. From the Main Options screen, choose F4/Administration. 2. When prompted, enter your username and password. 3. From the Admin. Options screen, choose F4/Security. 4.
Defining Security with Roles In Point-of-Sale, you specify users’ access to the application by assigning a role to each user. Each role contains a list of the security access points of the application, specifying which access points that role is allowed to use. You can create as many roles as you need. Roles are typically named for job titles; by creating a manager role and a clerk role, for example, you define two classes of employees with different access to the Point-of-Sale functions.
Adding a Role To add a role: 1. From the Main Options screen, choose F4/Administration, F4/Security, F3/Roles, and F3/Add. The Add Role screen appears. 2. From the Main Options screen, choose F4/Administration, F4/Security, F3/Roles, and F3/Add. The Add Role screen appears. Figure 2-3 Add Role Screen 3. Enter the new role name and choose Enter/Next. The Set Access screen appears. Initially, access for all functions is set to No. Figure 2-4 Set Access Screen 4.
2-8 5. Select the function(s) that need to be enabled/disabled for the role and choose F2/Yes/No to toggle to between Yes and No. 6. Continue selecting all functions that need to be changed. When finished, choose F3/Done to save the settings. 7. Choose Esc/Undo or F12/Cancel to return to the Security Options screen.
Secured Features The following table lists all of the functions within Point-of-Sale for which security access points exist. When a user attempts to use a function protected by one of these security access points, the system checks whether the user’s role allows that function.
Reason Codes Reason codes are items offered to the end user as choices in lists, for example, the set of possible reasons for a price override. These choices normally vary for each corporation, and they must be configured to suit your local requirements and policies. The system comes with a predetermined set of reason code groups; within each group, you can add, remove, and modify the list of codes, all from within the Pointof-Sale interface.
Figure 2-6 4. Reason Code List Screen Select one of the following: • To delete a code, select it, then choose F5/Delete. • To change the position of a code in the list, select it, then choose F6/Move Up or F7/Move Down. • To add a code, choose F4/Add. The Add Reason Code screen appears. Enter a name and database ID, then choose Enter/Next. • To change the name or database ID of a code, select the code in the list and choose F3/Edit. The system displays the Edit Reason Code screen.
Figure 2-7 Edit Reason Code Screen Configuring Transaction ID Lengths You can change the lengths of some of the most common data values associated with transactions. These changes affect every aspect of the software and should not be undertaken lightly. Changes should only be performed before Point-of-Sale is installed. Changes to these settings can require substantial testing to establish that no problems result from the change.
• Dates can be used in transaction IDs to help ensure unique IDs. If they are used, they are expressed as an 8-digit number; this is set by the TransactionIDBarcodeDateFormat property in the domain.properties file. The only valid values for this property are no value and yyyyMMdd. The date format does not vary from one locale to another. • You can set the transaction sequence start number in the database. • When you enter a transaction ID manually, the trailing date is optional.
Setting the RMI Time-out for the JVM Under Linux 360Commerce has found it useful to change the RMI time-out for the JVM under Linux. To do this, change the command that launches the JVM, adding the JVM flag Dsun.rmi.transport.connectionTimeout= where represents the time-out period in milliseconds. This tells the JVM to time out socket connections used by RMI after X milliseconds of inactivity. Linux quickly notifies the JVM when a socket connection cannot be established.
Configuring Third-party Tender Authorization Initially, the Point-of-Sale system simulates tender authorization. You can connect Point-of-Sale to a third-party tender authorization service to verify tenders.
Setting the Merchant Number Set the Merchant Number parameter to the appropriate value for the authorization service you are using. Merchant Number is an XML parameter in the Tender Authorization group. See “Modifying Parameters” on page 2-1. System Settings System settings are values set in the 360Store database. Changes to these settings must be made in the database by a database administrator or an application developer.
Creating a New Language Bundle To create a new language bundle: 1. Create a new source code directory in \360store\pos\locales for the language bundle, starting with a copy of the en_US directory. 2. Replace the English text in the properties files and help files in your new directory with translated text. 3. Generate a .jar file using the naming convention described in the preceding section. Configuring the System to Use a New Language Bundle To add a new language and change the default language: 1.
2-18 Point-of-Sale Administrator Guide
C H A P T E R 3 TROUBLESHOOTING This chapter describes Point-of-Sale functions used by administrators to maintain and troubleshoot the system. It includes the following sections: • “Viewing the Electronic Journal” • “Resetting Totals” • “Managing the Transaction Queue” Viewing the Electronic Journal Use the electronic journal to view register transactions. Registers produce clean receipts which do not include corrections made during a transaction.
To view the electronic journal: From the Admin Options screen, choose F2/E.Journal. The Find Transaction screen opens. Figure 3-1 Find Transaction Screen 1. • To search by Transaction ID, date, time, cashier ID, or Sales Associate ID, enter the search criteria and choose Enter/Next. • To search for all transactions for the current business day, choose Enter/Next without entering any data in the search criteria fields. If there is a single match, the transaction journal appears in the window.
3. 4. View or print the transaction detail. • Choose F2/Previous, F3/Next, F4/First, F5/Last to view the journal. • Choose F7/Print to print the journal entry. When you are finished, choose F6/Done to exit. The Admin Options screen opens. Resetting Totals Note: Typical register installations have hard totals turned off. If they are turned on, resetting totals clears the financial information stored in hard totals.
Deleting an Entry To delete the first entry in the queue: 1. From the Main Options screen, choose F4/Administration. From the Admin Options screen, choose F5/Queue. The Queue Options screen appears. 2. Choose F2/Delete Entry. 3. The Delete Confirmation screen appears. • Choose Yes to delete the first entry in the queue. A confirmation message appears. Choose Enter to continue. • Choose No to return to the Queue Options screen.
• If you select Yes, all transactions in the queue are deleted and a confirmation message appears. Choose Enter/Next to continue. • If you select No, the system displays the Queue Options screen.
3-6 Point-of-Sale Administrator Guide
