UnifiedPOS (UPOS) Controls Combined JavaPOS and OPOS Controls. Programmer s Guide

Transcription

1 UnifiedPOS (UPOS) Controls Combined JavaPOS and OPOS Controls Programmer s Guide

2 Disclaimer Hand Held Products, Inc. d/b/a Hand Held Products ( Hand Held Products ) reserves the right to make changes in specifications and other information contained in this document without prior notice, and the reader should in all cases consult Hand Held Products to determine whether any such changes have been made. The information in this publication does not represent a commitment on the part of Hand Held Products. Hand Held Products shall not be liable for technical or editorial errors or omissions contained herein; nor for incidental or consequential damages resulting from the furnishing, performance, or use of this material. This document contains proprietary information which is protected by copyright. All rights are reserved. No part of this document may be photocopied, reproduced, or translated into another language without the prior written consent of Hand Held Products Hand Held Products, Inc. All rights reserved. Web Address: Microsoft Visual C/C++, Windows 95, Windows 98, Windows 2000, and Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Other product names mentioned in this document may be trademarks or registered trademarks of other companies and are the property of their respective owners.

3 Table of Contents Chapter 1 - Introduction Supported Java Versions Chapter 2 - Hand Held Products UPOS Installation and System Configuration Installation Procedures Installing Java Runtime v1.4.2_04 (optional) System Configuration Configuring Windows 2000 and XP PATH Environment Variable (required) Configuring Windows NT PATH Environment Variable (required) Configuring Windows 98 PATH Environment Variable (required) Installation and System Configuration Complete Updating Windows CLASSPATH Environment Variable (optional) Running Third Party (non-hand Held Products) Applications with Hand Held Products Devices Uninstall Instructions Chapter 3 - Hand Held Products UnifiedPOS Configuration Application Configuration Application Overview Configuration Settings Configuration Functions Add New En Save to XML Chapter 4 - Configuring Devices Bar Code Scanner (RS-232) Bar Code Scanner (USB) Bar Code Scanner (USB Serial Emulation) Transaction Terminal (RS-232) Transaction Terminal (USB) Transaction Terminal (RS-485) Chapter 5 - Hand Held Products JavaPOS and OPOS Controls Tester (UltraTester) Applications Hand Held Products JavaPOS Ultra Tester Hand Held Products OPOS Ultra Tester Running the UltraTester Chapter 6 - Hand Held Products JavaPOS Host Sample Application Running JavaPOS Host Sample Chapter 7 - Overview of UnifiedPOS DirectIO DirectIO Method DirectIO Event i

4 Chapter 8 - DirectIO Command Details for Scanner Controls JavaPOS Usage OPOS Usage Chapter 9 - DirectIO Command Details for Transaction Terminal Controls Supported DirectIO Commands for Interfacing to Transaction Terminals JavaPOS DirectIO Commands DISPLAY_Bitmap DISPLAY_Box DISPLAY_Clear DISPLAY_Logo DISPLAY_ResetLogo DISPLAY_SetFont DISPLAY_SetLogoFile DISPLAY_Text MEM_DeleteObj MEM_DeleteVar MEM_FindObj MEM_FindVar MEM_GetFree MEM_GetVar MEM_SetVar PINIO_SetMasterKeyID PINIO_SetSessionKey PROMPT_Number SCRIPT_Goto SCRIPT_GotoVar SCRIPT_IsPaused SCRIPT_IsRunning SCRIPT_IsScript SCRIPT_IsVar SCRIPT_Reset SCRIPT_Run SCRIPT_Set SCRIPT_Stop SYS_DownloadFirmware SYS_GetError SYS_GetModel SYS_GetName SYS_GetVersion SYS_IsAvailable SYS_IsError SYS_Reboot SYS_Reset SYS_SetDebug Text_GetVar Text_IsVar Text_SetVar OPOS DirectIO Commands PW_CLEARSCREEN PW_DISPLAYBITMAPFILE PW_DISPLAYBOX PW_DISPLAYLOGO ii

5 PW_MEMDELETEOBJ PW_MEMDELETEVAR PW_MEMFINDOBJ PW_MEMFINDVAR PW_MEMGETFREE PW_MEMGETVAR PW_MEMSETVAR PW_NUMBERPAD PW_PUTTEXT PW_RESETLOGO PW_SCRIPTGOTO PW_SCRIPTGOTOVAR PW_SCRIPTISPAUSED PW_SCRIPTISRUNNING PW_SCRIPTISSCRIPT PW_SCRIPTISVAR PW_SCRIPTRESET PW_SCRIPTRUN PW_SCRIPTFILELOAD PW_SCRIPTSTOPLOAD PW_SETFONT PW_SETLOGO PW_SETMKEY PW_SETSKEY PW_SYSDOWNLOAD PW_SYSGETERROR PW_SYSGETMODEL PW_SYSGETNAME PW_SYSGETVERSION PW_SYSISAVAILABLE PW_SYSISERROR PW_SYSREBOOT PW_SYSRESET PW_SYSSETDEBUG PW_TEXTGETVAR PW_TEXTISVAR PW_TEXTSETVAR Chapter 10 - Technical Assistance iii

6 iv

7 1 Introduction Hand Held Products provides a set of Java for Point of Service (JavaPOS or JPOS) and OLE for Retail Point of Sale (OPOS) controls that can be used to interface to a specified group of Hand Held Products products when writing JavaPOS or OPOS applications for retail environments. The Hand Held Products JavaPOS and Hand Held Products OPOS controls support RS- 232, USB, and RS-485 interfaces to the connected device in Windows XP, 2000, 98, and NT environments. These JavaPOS and OPOS controls are compliant with the UnifiedPOS Retail Peripheral Architecture specification v1.9 dated 1/16/2005. UnifiedPOS is an architectural specification for application interfaces to point-of-service devices that are used in the retail environment. The Hand Held Products JavaPOS and Hand Held Products OPOS Controls (from here on referred to as the Hand Held Products UnifiedPOS or UPOS controls) are two implementations of the UnifiedPOS specification. The UnifiedPOS specification can be found at: The Hand Held Products UPOS controls provide an application interface to the Hand Held Products Transaction Team 8000 Series Terminals and the following Hand Held Products scanners: 3800, 4600g, 4620, 4800i, 3800r, 3820, and 3800i. In the case of the Transaction Team 8000 Series Terminal, multiple device categories are supported within the one physical device. That is, the Transaction Team 8000 Series Terminal supports the following device categories: Line Display, MSR, PIN Pad, POS Keyboard, Signature Capture, and Tone Indicator. Hand Held Products provides a JavaPOS and OPOS control for each of those device categories along with a control for the Scanner device category. The following table shows the relationship between the Hand Held Products product and the Hand Held Products UPOS control that provides an application interface to that product. Device Category Line Display POS Keyboard PIN Pad MSR - Magnetic Stripe Reader Signature Capture Tone Indicator Scanner (Bar Code Reader) Hand Held Products Physical Device TT8000 Series Transaction Terminal TT8000 Series Transaction Terminal TT8000 Series Transaction Terminal TT8000 Series Transaction Terminal TT8000 Series Transaction Terminal TT8000 Series Transaction Terminal 2020, 3800, 4010, 4080, 4200, 4600g ( 1 IT4600), 4620, 4800i ( 1 IT4800), 3800r ( 1 IT5600), 3820 ( 1 IT5620), 3800i ( 1 IT5800) 1. Former model number Note: Hand Held Products UPOS controls do not work with the Transaction Team 3100 terminal. This programmer s guide details the following: Installation and system configuration of Hand Held Products JavaPOS and OPOS controls Hand Held Products UnifiedPOS Configuration Application Hand Held Products JavaPOS Controls Tester application (JPOS UltraTester) Hand Held Products OPOS Controls Tester application (OPOS UltraTester) Hand Held Products JavaPOS Sample Host application DirectIO methods that are specific to the Hand Held Products JavaPOS and OPOS controls For further detailed information (methods, properties, events) about the application interfaces to the Hand Held Products supported devices, refer to the UnifiedPOS v1.9 specification with which the Hand Held Products JavaPOS and OPOS supported controls were developed to be in compliance. Supported Java Versions The Hand Held Products JavaPOS and OPOS controls both share common source code at the service layer that is used to communicate directly to the Hand Held Products supported products. This common source code requires the Java Runtime Environment (JRE) and above to be installed and running on your environment prior to using the Hand Held Products UPOS controls. In order to develop JavaPOS or OPOS applications using the Hand Held Products UPOS controls, the JRE must either already exist on your system, or be selected during installation to be installed onto your system. JavaPOS applications written using the Hand Held Products JavaPOS controls must be developed using the Java SDK version (which includes the JRE 1.3.1) and above. UnifiedPOS (UPOS) Controls Programmer s Guide 1-1

8 1-2 UnifiedPOS (UPOS) Controls Programmer s Guide

9 2 Hand Held Products UPOS Installation and System Configuration To set up the Hand Held Products JavaPOS and/or OPOS controls to run in your environment, you must: 1. Run the Hand Held Products UnifiedPOS Installation program 2. Configure your Windows system environmental path variable 3. Run the Hand Held Products UnifiedPOS Configuration Application This chapter details steps 1 and 2 above. See Hand Held Products UnifiedPOS Configuration Application beginning on page 3-1 for information about running the Hand Held Products UnifiedPOS Configuration Application. The Hand Held Products UnifiedPOS Installation program allows you to install either the Hand Held Products JavaPOS and/or Hand Held Products OPOS controls, along with optional items, such as test programs, a sample program, and Java Runtime 1.4.2_04. The following are the components that can be selected during installation: Hand Held Products JavaPOS Controls (required, when OPOS Controls are selected) The Hand Held Products JavaPOS controls, which let you develop JavaPOS applications to interface to the supported Hand Held Products devices. This component also includes the Hand Held Products UnifiedPOS Configuration Application that lets you configure your communication parameters along with other miscellaneous items. See Hand Held Products UnifiedPOS Configuration Application beginning on page 3-1 for further details. Hand Held Products OPOS Controls (optional, depend on JavaPOS Controls) The Hand Held Products OPOS controls, which let you develop OPOS applications to interface to the supported Hand Held Products devices. This component also includes the Hand Held Products UnifiedPOS Configuration Application that lets you configure your communication parameters along with other miscellaneous items. See Hand Held Products UnifiedPOS Configuration Application beginning on page 3-1 for further details. Hand Held Products JavaPOS and OPOS UltraTester Applications (optional, depend on JavaPOS Controls) These applications test each of the supported Hand Held Products JavaPOS or OPOS controls. See Hand Held Products JavaPOS and OPOS Controls Tester (UltraTester) Applications beginning on page 5-1 for further details. Hand Held Products JavaPOS Sample Host Application (optional, depend on JavaPOS Controls) A sample retail point-of-sale application that uses all the Hand Held Products JavaPOS controls to interface to a Transaction Terminal and scanner. The Java source code for this sample host is installed so you may reference it when writing your own JavaPOS application. The Transaction Terminal binary script file is also installed and can be downloaded to the Transaction Terminal via the Hand Held Products JavaPOS or Hand Held Products OPOS UltraTester Application. See Hand Held Products JavaPOS Host Sample Application beginning on page 6-1 for further details. Java Runtime Environment (JRE) 1.4.2_04 (optional) Optional if JRE or above is already resident on the system. Otherwise this is required to use either the Hand Held Products JavaPOS or Hand Held Products OPOS controls. Installation Procedures The following steps describe the Hand Held Products UPOS installation process: 1. Download the UPOS installation program, HandHeldUPOSInstall.exe, into a temporary folder on your hard drive (for example: C:\temp\handheld\upos). 2. Within Windows Explorer, locate the installation program, HandHeldUPOSInstall.exe. Begin the installation and follow the instructions on the screens that appear. 3. If installing OPOS controls, restart your system when prompted. Once your system is restarted, the UPOS installation program automatically starts up again to finish the installation. If you have selected not to install the JRE, your installation is now complete. Otherwise, the Java Runtime v1.4.2_04 installation begins. Installing Java Runtime v1.4.2_04 (optional) Before utilizing the Hand Held Products UPOS controls, you must have JRE or above installed on your PC. This installation is automatically launched when the Java Runtime 1.4.2_04 option is selected. The Typical installation installed the Java Runtime Environment by default in the C:\Program Files\Java\j2re1.4.2_04 folder. If you want to install the Java Runtime in another folder, perform a Custom installation. System Configuration After completing and verifying the installation, you must perform the following system configuration before utilizing the installed components. This will ensure that the JRE is in your Windows system environmental PATH variable. The following steps describe this process. UnifiedPOS (UPOS) Controls Programmer s Guide 2-1

10 Configuring Windows 2000 and XP PATH Environment Variable (required) 1. Right click on the My Computer icon and select Properties, then click on the Advanced tab. 2. Click on Environment Variables to set the path system variable. Select Path under System Variables. 3. Note: <install_dir> stands for the directory where you installed the files. Click on Edit and enter <install_dir>\bin;<java_runtime_dir>\bin\client, where <install_dir>\bin indicates where the installation file is stored and <java_runtime_dir>\bin\client indicates where the Java Runtime Environment resides. For example: C:\Program Files\ Hand Held Products\UPOS\bin; C:\Program Files\Java\j2re1.4.2_04\bin\client. Click OK. 2-2 UnifiedPOS (UPOS) Controls Programmer s Guide

11 Configuring Windows NT PATH Environment Variable (required) 1. Right click on the My Computer icon and select Environment. 2. Select Path under System Variables. 3. Enter <install_dir>\bin and <java_runtime_dir>\bin\client at the end of the variable value string to indicate where the Java Runtime Environment resides. For example: C:\Program Files\Java\j2re1.4.2_04\bin; C:\Program Files\Java\j2re1.4.2_04\bin\client. Click OK. Configuring Windows 98 PATH Environment Variable (required) 1. On the Start Menu, select Run, enter msconfig, and click on OK. 2. Click on the Autoexec.bat tab. 3. Enter <install_dir>\bin and <java_runtime_dir>\bin\client at the end of the variable value string to indicate where the Java Runtime Environment resides. For example: C:\Program Files\Java\j2re1.4.2_04\bin; C:\Program Files\Java\j2re1.4.2_04\bin\client. Click OK. UnifiedPOS (UPOS) Controls Programmer s Guide 2-3

12 Installation and System Configuration Complete The setting of the Windows system environmental path variable completes the installation and system configuration for the Hand Held Products JavaPOS and/or OPOS controls. To utilize the installed controls, you must next configure them to fit your needs (communication parameters, special parameters to interface to a Transaction Terminal script, log files, etc.) by running the UnifiedPOS Configuration Application (see Hand Held Products UnifiedPOS Configuration Application beginning on page 3-1). Updating Windows CLASSPATH Environment Variable (optional) The install adds several JAR files to your Windows system environmental CLASSPATH variable. By default, these JAR files are located under the <install_dir>/bin directory. If you are running other Java based applications on the same system, you may wish to modify the locations of the following 3 rd party JAR files to reflect your environment: comm.jar jcl.jar jposxx-controls.jar (where XX denotes the version, for example jpos19-controls.jar) xerces.jar When any of these locations are modified, you should also update the following BAT files to reflect the changes: RunJposSampleHostApp.bat RunJposUltraTester.bat RunUposConfig.bat Running Third Party (non-hand Held Products) Applications with Hand Held Products Devices Running a third party Java application requires the location of jpos.xml, which resides in <install_dir>\res. You must update the jpos.config.populatorfile attribute located within the jcl.jar file s jpos.properties file. The following is an example of the new jpos.properties en: # # Use this property for the JCL to load a specific file (cfg or XML) # when not using multiple populators via the jpos.config.populator.class. # multi-property # jpos.config.populatorfile=c://handheldproducts/upos/res/jpos.xml You must verify that your third party application s classpath includes the path to the device specific jar, hhpjpos.jar, as well as any dependent files such as comm.jar. The updated classpath will be similar to the following: set classpath=%classpath%;c:\hand Held Products\UPOS\bin\comm.jar;c:\<install.dir> Uninstall Instructions To uninstall the Hand Held Products JavaPOS Controls, OPOS Controls, JavaPOS UltraTester, OPOS UltraTester, and JavaPOS Sample Host Application components, use Add or Remove Programs from the Control Panel. Remove the Hand Held Products UPOS Controls software. To uninstall the Java Runtime component, remove the Java 2 Runtime Environment, SE v1.4.2_04 software. 2-4 UnifiedPOS (UPOS) Controls Programmer s Guide

13 3 Hand Held Products UnifiedPOS Configuration Application Once the installation and system configuration are complete, you must configure the Hand Held Products JavaPOS and/or OPOS Controls. The installation of the Hand Held Products JavaPOS and/or OPOS Controls component includes the installation of the Hand Held Products UnifiedPOS Configuration Application. This application sets up your system for proper operation with the connected Hand Held Products device. The Hand Held Products UnifiedPOS Configuration Application allows you to configure parameters for your communication interface to the devices (RS-232, USB, or RS-485), and also configure special parameters to be used when interfacing to a Transaction Terminal script (custom script forms and signature formats). To run the Hand Held Products UnifiedPOS Configuration Application, launch the <install_dir>\runuposconfig.bat batch file in a Windows Explorer window. This file is in C:\<install_dir>\RunUposConfig.bat. Configuration Application Overview The configuration application comes with 7 default en names corresponding to 7 UnifiedPOS controls (device categories) that were installed by the UnifiedPOS controls component. En Name Device Category Hand Held Products Physical Device L1 Line Display Transaction Team 8000 Series Terminal SCAN1 Scanner 2020, 3800, 4010, 4080, 4200, 4600g ( 1 IT4600), 4620, 4800i ( 1 IT4800), 3800r ( 1 IT5600), 3820 ( 1 IT5620), 3800i ( 1 IT5800) K1 POSKeyboard Transaction Team 8000 Series Terminal P1 PinPad Transaction Team 8000 Series Terminal M1 MSR Transaction Team 8000 Series Terminal S1 SignatureCapture Transaction Team 8000 Series Terminal T1 ToneIndicator Transaction Team 8000 Series Terminal 1. Former model number The following is an example of the screen that is displayed when the UPOS Configuration Application is executed: UnifiedPOS (UPOS) Controls Programmer s Guide 3-1

14 Configuration Settings Setting Device Bus Port Name, Baud Rate, Parity Data Bits Stop Bits, Flow Control USB Device, USB Device Serial # Connection Port, Connection Slot, Device ID, Initialize POS Subsystem Log File Text Rows, Column Rows Custom Script Form Signature Format Each device category supports three types of Device Bus values: RS-232, USB, and RS-485. When you select the device bus, the corresponding properties selections for that interface are enabled. RS-232 properties are only selectable if Device Bus is set to RS-232. These values must match the values that are set for the PC communications port and for the Hand Held Products device. Note: If the scanner is connected to a USB port, but configured as USB COM port emulation, then you must select RS-232 as the device bus, and select the correct virtual COM port. All other RS- 232 parameters (baud rate, parity, data bits, stop bits, and flow control) can be ignored for USB COM port emulation. USB Properties are only selectable if Device Bus is set to USB. RS-485 properties are only selectable if Device Bus is set to RS-485. These values must match the values that are set for the Hand Held Products device. Connection Port:: Use the default value. Connection Slot:: Use the default value. Device ID: Refer to Transaction Terminal (RS-485) on page 4-2 to configure the Device ID. Initialize POS Subsystem: Check this box if your application is the first to initialize the POS subsystem. Otherwise, leave the box unchecked. If a Log File name is specified, a log file will be kept for those UPOS controls activities in the <install_dir> folder. Note: The OPOS Service Object always creates a log file, <device>so.log, and stores it in the install directory by default (<install_dir>) or in the location specified by the regis key: HKLM\SW\OLEforRetail\ServiceInfo\Hand Held Products\Logpath These parameters may only be set for a Line Display Device category. This parameter may only be set for PinPad and POSKeyboard Device categories. This parameter is used only when interfacing to a corresponding script residing on a Transaction Terminal. This value represents the name of the form in the script to which the PinPad and/or POS Keyboard UPOS control will interface. For the PinPad control, this parameter must match the name of the Pinpad form in the script. For the POS Keyboard control, this parameter must match the name of the form in the script that will be sending data via the POS Keyboard control. When this parameter is specified, the UPOS control goes to the specified script form on the Transaction Terminal upon the beginning of an EFT Transaction (PinPad control), and/or upon the device being enabled (POS Keyboard control). This parameter may only be set for the SignatureCapture Device category and has valid values of: Packet, CMP, and CMP_Base64. This value represents the type of signature data returned by Transaction Terminal to SignatureCapture UPOS control. This is used only in conjunction with a corresponding script residing on a Transaction Terminal. This parameter must match the format of the signature output from the script. 3-2 UnifiedPOS (UPOS) Controls Programmer s Guide

15 Configuration Functions Add New En 1. On the initial Hand Held Products UnifiedPOS Configuration Application screen, select New En 2. Enter a meaningful Device ID (En Name) and select an appropriate Device Category (UPOS Control). If you utilize the UPOS control (by writing your own application or using the installed JavaPOS or OPOS UltraTester application), the Device ID must be passed to the JavaPOS or OPOS open( ) method to open communications with the desired device. 3. Click OK to add the new en. 4. Modify settings for new en as described on page 3-2. Save to XML The UnifiedPOS Configuration Application saves modified UPOS configuration information in the <install_dir>\res\jpos.xml file. This file should never be edited by any program other than the Hand Held Products UnifiedPOS Configuration Application. Updated UPOS configuration information can be saved by clicking Save To XML. UnifiedPOS (UPOS) Controls Programmer s Guide 3-3

16 3-4 UnifiedPOS (UPOS) Controls Programmer s Guide

17 4 Configuring Devices Bar Code Scanner (RS-232) 1. Connect the scanner to your computer/terminal according to the installation procedures in the scanner s user guide. 2. Once the scanner has been fully connected, power up the terminal/computer. 3. Log on to your computer. 4. Scan the RS-232 Interface bar code in your scanner s user guide. 5. Scan an appropriate baud rate bar code in your scanner s user guide. This baud rate must match what was specified for the device by the UnifiedPOS Configuration Application. 6. Scan an appropriate RS-232 Word Length bar code in your scanner s user guide. The parity - data bits - stop bits setting must match what was specified for the device by the UnifiedPOS Configuration Application. 7. Scan an appropriate RS-232 Handshaking RTS/CTS bar code in your scanner s user guide. The RTS/CTS setting must match what was specified for the device by the UnifiedPOS Configuration Application. Bar Code Scanner (USB) 1. Connect the USB interface cable to the scanner. 2. With the computer/terminal powered on, connect the USB connector to a target computer/terminal's USB port. 3. Immediately after the USB connection has been made, scan the USB HID bar code in your scanner s user guide. This sets the terminal ID for the scanner to Wait until the new device has been detected and recognized by the Windows operating system. 5. Right click on My Computer and select Properties, then click on the Hardware tab. 6. Click on Device Manager. 7. Expand the Human Interface Devices en. The following two entries should appear: HID-compliant device USB Human Interface Device Bar Code Scanner (USB Serial Emulation) 1. Download the Matrix USB Serial Emulation Driver from the Hand Held Products website ( Unzip the archive to a location of your choice. 2. Connect the USB interface cable to the scanner. 3. With the computer/terminal powered on, connect the USB connector to a target computer/terminal s USB port. 4. Immediately after the USB connection has been made, scan the USB COM Port Emulation bar code in your scanner s user guide. This sets the terminal ID for the scanner to Wait until the new device has been detected and recognized by the Windows operating system. The operating system will ask for the driver (the.inf file). Direct it to the location where you unzipped the driver files. 6. Right click on My Computer and select Properties, then click on the Hardware tab. 7. Click on Device Manager. 8. Expand the Ports en and verify the scanner appears, followed by the virtual COM port number. UnifiedPOS (UPOS) Controls Programmer s Guide 4-1

18 Transaction Terminal (RS-232) 1. Connect the Transaction Terminal to your computer/terminal according to the installation procedures in the startup guide. 2. Upon startup of the Transaction Terminal, the initial screen prompts you to Touch the pad now to enter setup mode. Touch the screen with the stylus to enter setup mode. 3. Touch the Host button. 4. Check/Uncheck the Enable CTS holdoff check box as specified for the Transaction Terminal by the UnifiedPOS Configuration Application. 5. Check the appropriate Baud Rate (bps): check box as specified for the Transaction Terminal device by the UnifiedPOS Configuration Application. 6. Select Accept on the Host configuration screen. 7. Select Accept on the Setup screen. Transaction Terminal (USB) 1. Connect the Transaction Terminal to your computer/terminal according to the installation procedures in the startup guide. 2. Wait until the new device has been detected and recognized by the Windows operating system. 3. Right click on My Computer and select Properties, then click on the Hardware tab. 4. Click on Device Manager. 5. Expand the Human Interface Devices en. The following two entries should appear: HID-compliant device USB Human Interface Device Transaction Terminal (RS-485) 1. Power down the IBM 46XX register. 2. Connect the cable to the Transaction Terminal and to port 9 in the back of the register. 3. Power up the IBM46XX register. 4. Upon startup of the Transaction Terminal, the initial screen prompts you to Touch the pad now to enter setup mode. Touch the screen with the stylus to enter setup mode. 5. Touch the Host button. 6. Check that the correct Device ID is specified for the Transaction Terminal by the UnifiedPOS Configuration Application. 7. Select Accept on the Host configuration screen. 8. Select Accept on the Setup screen. 9. Power down the register, then power it back up. 4-2 UnifiedPOS (UPOS) Controls Programmer s Guide

19 5 Hand Held Products JavaPOS and OPOS Controls Tester (UltraTester) Applications The Hand Held Products JavaPOS and OPOS UltraTesters are optional components. These applications allow you to test all the Hand Held Products JavaPOS /OPOS controls individually. Before running the UltraTester, you must first configure your devices via the Hand Held Products UnifiedPOS Configuration Application. Refer to Hand Held Products UnifiedPOS Configuration Application beginning on page 3-1. Hand Held Products JavaPOS Ultra Tester To run the Hand Held Products JavaPOS UltraTester application, launch the <install_dir>\runuposultratester.bat batch file in a Windows Explorer window. When the Hand Held Products JavaPOS UltraTester is initially executed, the following screen displays: Hand Held Products OPOS Ultra Tester To run the Hand Held Products OPOS UltraTester application, launch the <install_dir>\oposultratester.exe file in a Windows Explorer window. UnifiedPOS (UPOS) Controls Programmer s Guide 5-1

20 When the Hand Held Products OPOS UltraTester is initially executed, the following screen displays: Running the UltraTester UltraTester allows you to perform the main functions provided by JavaPOS/OPOS. Using UltraTester, you can open the COM port, claim the device, enable data events, and then receive device data. It can also change supported JavaPOS/OPOS control properties and verify the new values. UltraTester also provides an interface for using and testing the various DirectIO functions available on the Hand Held Products JavaPOS/OPOS controls that interface to the Transaction Terminals. The GUI items on the tabs on the right side of the application apply to the control shown on the currently displayed tab on the left side of the main window. For example, to open the keyboard control, you must first display the keyboard control tab on the left side of the application. Then click the Open button on the tab on the right side window. This operation opens only the keyboard control. By selecting different left side tabs, multiple controls can be opened and tested simultaneously. 5-2 UnifiedPOS (UPOS) Controls Programmer s Guide

21 6 Hand Held Products JavaPOS Host Sample Application The Hand Held Products JavaPOS Host Sample application is an optional component that simulates a point-of-sale register interfacing to a Transaction Terminal along with an Hand Held Products scanner. JavaPOS Host Sample exercises all the JavaPOS controls for the Transaction Terminal (MSR, Sig, PinPad, LineDisplay, Keyboard, Toner) and also exercises the scanner control. The Transaction Terminal contains a script that has the typical point-of-sale functionality (line item display, credit, debit, signature, instant credit application, survey, etc.). There is a separate script for RS-232/RS-485 connectivity and USB connectivity. Before running JavaPOS Host Sample, the Transaction Terminal script must be downloaded to the Transaction Terminal. This can be done via a directio function using the Hand Held Products JavaPOS UltraTester, or can be done via an Hand Held Products supplied TT8000 Series Loader utility. The script files are in the following directories: C:\<install_dir>\bin\UPOS_Sample_Script_USB.bin C:\<install_dir>\bin\UPOS_Sample_Script_RS232_RS_485.bin Once the script is downloaded, the Hand Held Products UnifiedPOS Configuration Application must be run to configure the JavaPOS controls properly (see Hand Held Products UnifiedPOS Configuration Application beginning on page 3-1). Along with setting the proper communication parameters to accommodate the connections for your devices, the following special parameters must be configured before running JavaPOS Host Sample: Device Category Custom Script Form Signature Format PinPad padpin n/a POSKeyboard padinstantcredit_ssn n/a SignatureCapture n/a CMP Line Display padlinedisplay n/a To run JavaPOS Host Sample, launch the <install_dir> RunJposSampleHostApp.bat batch file in a Windows Explorer window. This file will be in a directory as follows: C:\<install_dir>\RunJposSampleHostApp.bat When JavaPOS Host Sample is initially executed, the following screen displays: Note: In order to use Debit, your system must be injected with a DUKPT key. For information on key injection, contact Technical Support (see Technical Assistance on page 10-1). Running JavaPOS Host Sample When JavaPOS Host Sample is in its idle state, the application status area indicates it is waiting for a bar code scan to initiate a transaction. The survey button is enabled at this time and, if selected, initiates a survey on the Transaction Terminal. UnifiedPOS (UPOS) Controls Programmer s Guide 6-1