23901 Verix VeriVeriFone VX 520 Reference Manualx v Development Suite Getting Started Guide

Verix/Verix V DevelopmentSuite Getting Started Guide VeriFone Part Number 23901, Revision D Verix/Verix V Development Suite Getting Started Guide © 2007 VeriFone, Inc. All rights reserved. No part of the contents of this document may be reproduced or transmitted in any form without the written permission of VeriFone, Inc. The information contained in this document is subject to change without notice. Although VeriFone has attempted to ensure the accuracy of the contents of this document, this document may include errors or omissions. The examples and sample programs are for illustration only and may not be suited for your purpose. You should verify the applicability of any example or sample program before placing the software into productive use. This document, including without limitation the examples and software programs, is supplied “As-Is.” VeriFone, the VeriFone logo, Omni, VeriCentre, Verix, Vx, and VeriShield are registered trademarks of VeriFone. Other brand names or trademarks associated with VeriFone’s products and services are trademarks of VeriFone, Inc. All other brand names and trademarks appearing in this manual are the property of their respective holders. Comments? Please e-mail all comments on this document to your local VeriFone Support Team. VeriFone, Inc. 2099 Gateway Place, Suite 600 San Jose, CA, 95110 USA 1-800-VeriFone www.verifone.com VeriFone Part Number 23901, Revision D . . . . . . . . . . . . . . . . . . . . . . . . . 8 Minimum PC Requirements . . . . . . . . . . . . . . . . . . . . . . Installed Folders . Installed Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 For Verix V . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 15 15 16 16 16 17 17 17 17 18 18 19 19 19 19 19 19 19 20 20 21 21 21 22 22 22 22 Application Development Environment. . Installed Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installed Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tools available in both Verix and Verix V . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tools available in Verix . . . . . . . . . . . . . . . . . . . . . . . Installed Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Creating an Application for Verix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Document Organization . Debugging Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . VeriPrint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 VDTK Components. . . 10 Default Installation Directory. . . . . . . . . 7 Target Audience . . . . . . . . . . . . . . . . . . . . . . . . . . 23 VERIX/VERIX V DEVELOPMENT SUITE GETTING STARTED GUIDE 3 . . . . . . . . . . . . TMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installed Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installed Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Font Generation Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 CHAPTER 1 Development Suite Components CHAPTER 2 Developing Applications Verix SDK . . . . . . . . . . . . . . . . . . . . . . 9 For Verix . . . . . . . . . 11 Documentation . . . . . . . . . . . . . . Installed Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CardSlot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 What’s New . . . . . . . . . . . . . VeriShield FST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Debugging Tools. . . . . . . . . . . .CONTENTS PREFACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tools available in Verix V. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VeriFind . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installed Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Conventions and Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . Memory Calculator . . Verix V SDK . . . . . . . . . . . . . . . . . . ACT2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VMAC . . . . . . . . . . . . . . . . . . . . Messenger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installed Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Minimum Requirements for Developing Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Shared Libraries . . . . . . . . . . . . . . . . . . Generating Shared Libraries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 VERIX/VERIX V DEVELOPMENT SUITE GETTING STARTED GUIDE 24 24 24 25 . . . . . . . . . . . . . . .C ONTENTS Generating Static Libraries . . . . . . Creating an Application for Verix V. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Minimum Requirements for Verix V . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Acronyms and Definitions . . . 11 VERIX/VERIX V DEVELOPMENT SUITE GETTING STARTED GUIDE 5 . . . . . . . . . . . 7 Document Organization . . . . 8 Minimum PC Requirements . . .LIST OF TABLES Table 1 Table 2 Table 3 Table 4 Table 5 Table 6 Table 7 VDTK Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Minimum Requirements for Verix . . . . . . . . . . . . . . . . . . . . . . L IST OF TABLES 6 VERIX/VERIX V DEVELOPMENT SUITE GETTING STARTED GUIDE . utilities and libraries using which you can develop applications for Verix and Verix V terminals. Table 1 VDTK Components Development Suite ECL SDK Universal Communication Library ACT2000 TCPIP Library CardSlot IP Download Library Multi-App Conductor Communication Server Terminal Management Agent Simple Network Management Protocol Messenger Tools Memory Calculator Font Generation Tool VeriShield FST VeriFind VeriPrint This guide contains information on the Development Suite components.Development Suite and Enhanced Communication Libraries (ECL). VERIX/VERIX V DEVELOPMENT SUITE GETTING STARTED GUIDE 7 . Development Suite has the SDK and a set of libraries. tools and utilities that aid in application development.PREFACE The Verix/Verix V Development Tool Kit (VDTK) contains the Software Development Kit (SDK). Developers must have knowledge on C and C++ programming languages. Target Audience This guide is for developers who develop applications for VeriFone’s Verix and Verix V terminals using the Verix/Verix V Development Suite. ECL has a set of libraries and applications you can use to perform communication tasks in your applications. The Verix/Verix V Enhanced Communication Libraries Getting Started Guide. VDTK Components Table 1 lists the VDTK components in the two CDs. and various useful tools. The VDTK comprises two CDs . contains information on ECL components. filenames. NOTE Note points out interesting and useful information. The following are conventions used in this document. Table 3 8 Acronyms and Definitions Acronym Definition ACT Application Construction ToolKit CVLR Compressed Variable-Length Record ECL Enhanced Communication Libraries FST File Signing Tool ICC Integrated Chip Cards IMM Inter task Message Manager IP Internet Protocol ITP Integrated Thermal Printer MIID Monitored Item Identifier OS Operating System PIP Plural Interface Protocol SDK Software Development Kit SNMP Simple Network Management Protocol TCP/IP Transmission Control Protocol/Internet Protocol TMA Terminal Management Agent VERIX/VERIX V DEVELOPMENT SUITE GETTING STARTED GUIDE . Chapter 2. CAUTION Caution points out potential programming problems. Development Suite Components Provides an overview of the tools and libraries used in the Development Suite. • The italic typeface indicates book title or emphasis. and anything that might require typing at the DOS prompt or from the terminal keypad. When the pointer is placed over these references the pointer changes to the finger pointer.P REFACE Document Organization Document Organization Conventions and Acronyms The manual is organized as follows: Table 2 Document Organization Chapter Description Chapter 1. • The courier typeface is used for code entries. Table 3 presents acronyms and their definitions. Click on the link to view the topic. indicating a link. • Text in blue indicates terms that are cross-referenced. Developing Applications Explains how applications can be developed using the Development Suite components. • ~80 MB disk space for a typical installation of all components. VMAC • VFSDK • Wind River Systems (SDS) Cross Compiler.P REFACE Minimum PC Requirements Table 3 Minimum PC Requirements Acronyms and Definitions (continued) Acronym Definition TXO Transaction eXpress Option VCS Verix/Verix V Communication Server VDTK Verix/Verix V Development Tool Kit VLR Variable-Length Record VMAC Verix/Verix V Multi-App Conductor VTMA Verix/Verix V Terminal Management Agent Table 4 lists the software and hardware requirements for installing and using the DTK for application development. Minimum Requirements for Developing Applications For Verix Table 5 lists the minimum requirements for installing and using Development Suite components for developing applications. Table 4 Minimum PC Requirements Software • Any one of the following Operating Systems: • Microsoft Windows 2000 Service Pack 2 or later • Microsoft Windows XP Service Pack 1 or later • Internet Explorer 6. version 9. CardSlot.0 or later • Adobe Acrobat Reader.0 or later Hardware • Any PC supporting Windows 2000. • RS-232 download cable to connect Verix terminal to a PC running VeriPrint (VeriPrint is a PC-based application). • Microsoft Windows 2000 or XP VERIX/VERIX V DEVELOPMENT SUITE GETTING STARTED GUIDE 9 . • 128 MB RAM • 10 .15 MB free disk space on the system drive for temporary files created during installation. version 7.1 Tools • Microsoft Visual C++ Compiler VTMA • VMAC Messenger VeriPrint • VMAC • VTMA • An application that can print on the VeriFone printer connected to the terminal.0/ 7. Table 5 Minimum Requirements for Verix Tool Requirements ACT2000.0 or later • Microsoft Excel 2003. version 6. • RS-232 download cable to connect Verix V terminal to a PC running VeriPrint (VeriPrint is a PC-based application). • RS-232 download cable to connect Verix V terminal with a PC running VeriFind (VeriFind is a PC-based application).12. version 2 (for MakeFile Maker • VeriFone RVDS 2. CardSlot. DoxBox Part Number DO-415610-DG and CONEXANT SoftMAC. Covering UMAC Version 2. • Microsoft Windows 2000 or XP Font Generation Tool NOTE • Microsoft Windows 2000 or XP • Refer to the Verix (V) ReadMe for details on OS and firmware versions.1 and RVD 1. Refer to the VeriFind Online Help for more details. restart the terminal. 10 VERIX/VERIX V DEVELOPMENT SUITE GETTING STARTED GUIDE . VTMA • VMAC Messenger • VMAC • VTMA VeriPrint • An application that can print on the VeriFone printer connected to the terminal. VMAC • VRXSDK Tools • Java Runtime Environment.P REFACE Minimum Requirements for Developing Applications Table 5 Minimum Requirements for Verix (continued) Tool Requirements VeriFind • An application enabled for VeriFind. • Following are the commands for different modules to verify the firmware version: • Vx510 Ethernet: AT+iRP1 • Vx610 Wi-Fi: AT+iRP1 • Vx610 CDMA: AT+GMR • Vx610/Vx670 GPRS: AT+CGMR • Refer to the WPA Supplicant OIDs on NIC. UMAC Management Information Base Software Interface Manual.7 tool) and API converter tool. • RS-232 download cable to connect Verix terminal with a PC running VeriFind (VeriFind is a PC-based application).48.0.1 which includes RVCT 2. • To verify the terminal’s OS version number.0 to verify the firmware version of Vx670 Wi-Fi terminal. Refer to the VeriFind Online Help for more details. VeriFind • An application enabled for VeriFind. • Microsoft Windows 2000 or XP Font Generation Tool For Verix V Table 6 • Microsoft Windows 2000 or XP Minimum Requirements for Verix V Tool Requirements ACT2000. The OS version appears on the second line of the copyright screen during the start-up sequence. VPN 22940 • ConnectOne Interface Module AT Command Programming Guide. VPN 22412 SDK (Verix V) • WPA Supplicant OIDs on NIC. VPN 23902 SDK (Verix) • Aspen 144 Modem.12. the default installation path is: C:\VerixAps\<Project component> For Verix V. Related Documents Document Path • Verix/Verix V Enhanced Communication Library <Installation directory>\VerixVAps Getting Started Guide. VPN 19244 • Omni 37xx ISDN TA Module Programming Guide.P REFACE Default Installation Directory Default Installation Directory For Verix. UMAC Management Information Base Software Interface Manual. Table 7 lists the relevant documents and their paths.48. the default installation path is: C:\VerixVAps\<Project component> NOTE Documentation Table 7 The components are installed in the default path. DoxBox Part Number DO-415610-DG • CONEXANT SoftMAC. Covering UMAC Version 2. VPN E-102184 <Installation directory>\VerixAps\VFSDK\Doc • EMXXXX Development Kit AT Command Reference. VPN E-213039 • RIM OEM Radio Modem for GSM/GPRS Wireless Networks RIM 1902G™ and RIM 1802G™ AT Command Reference Guide. VPN PDF-04620-003 • Verix Operating System Programmers Manual. Omni Modem 144. the settings of the project workspace and associated files of the sample programs must be modified to reflect the new path. If you change the default path.0 VERIX/VERIX V DEVELOPMENT SUITE GETTING STARTED GUIDE 11 . Refer to these documents for more information on the individual components of the Development Suite. VPN 23304 • Conexant CX Modem AT Command Reference Manual. VPN 19733 • Verix Operating System Programming Reference Manual. and Santana 144 Acf Modem Command Reference Guide. 11 • Verix Applications to ARM Porting Guide. VPN 23231 • Integrated Thermal Printer Applet help (itp_app. VPN 22311 <Installation directory>Program Files\VeriShield File Signing Tool\Help Font Generation Tool • Font Generation Tool Help. VPN <Installation directory>\VerixVAps\ACT2000 23285 CardSlot Library • Verix/Verix V CardSlot Library Programmer’s Guide. VPN 24494 • Conexant CX86500 SCXV Modem AT Command Reference Manual. VPN 24291 <Installation directory>Program Files\FontGenerationTool ACT Library • Verix/Verix V ACT2000 Programmer’s Manual. VPN 23736 • Verix V Operating System Programmer’s Manual. VPN 22622 <Installation directory>\VerixAps\VeriFind VeriPrint • VeriPrint Online Help. VPN 23304 Tools • MakeFile Maker Tool User’s Guide.hlp VeriFind • VeriFind Online Help. VPN 2130394 • MC55 / MC56 Siemens Cellular Engine. Doc ID MC55 / MC56_ATC_V00. <Installation directory>\VerixVAps\VRXSDK\Doc VPN 23230 • Verix V Operating System Programming Tools Reference Manual.htm) • Silicon Labs AT Commands and Reponses Guide. VPN 22265 • VerixVWizard. VPN 22623 <Installation directory>\VerixAps\VeriPrint VeriShield FST • VeriShield Online Help. VPN E-102184 • EMXXXX Development Kit AT Command Reference.htm) • Understanding the Verix Error Log help (errlog.P REFACE Documentation Table 7 Related Documents (continued) Document Path • Conexant CX Modem AT Command Reference Manual. VPN E-102327 • ConnectOne Interface Module AT Command Programming Guide.htm) • Troubleshooting Debugger Installation Problems help (debughelp. VPN 23288 Multi-App Conductor 12 VERIX/VERIX V DEVELOPMENT SUITE GETTING STARTED GUIDE <Installation directory>\VerixVAps\CardSlot . P REFACE What’s New Table 7 Related Documents (continued) Document Path • Multi-App Conductor for Verix and Verix V <Installation directory>\VerixVAps\VMAC Programmer’s Guide. VERIX/VERIX V DEVELOPMENT SUITE GETTING STARTED GUIDE 13 . Following are the major enhancements in DTK: • DTK components support logging through USBD device of Vx810 terminals. • VTMA has been enhanced to communicate to VeriCentre over IP. VPN 23287 Messenger • Verix/Verix V Messenger Application User’s Guide. <Installation directory>\VerixVAps\Messenger VPN 23220 NOTE What’s New ReadMe files of the components are also in the respective paths mentioned in the Table 7. • VMAC has been enhanced to support new USBD device for arbitration. • DTK components have been enhanced to support Vx810 PINpad. VPN 23286 Terminal Management Agent • Verix/Verix V Terminal Management Agent <Installation directory>\VerixVAps\VTMA Programmer’s Guide. P REFACE What’s New 14 VERIX/VERIX V DEVELOPMENT SUITE GETTING STARTED GUIDE . shared libraries cannot have interfaces in C++. Verix SDK Verix SDK provides startup code. tools and libraries packaged in the Development Suite. ANSI C standard libraries and related tools required for the applications to run on Verix terminals.direct download utility for downloading files to the terminal. It also provides a standard Cinterface library for Verix V applications. It has sample make files for compiling and linking applications. Verix V SDK The VeriFone SDK provides startup code. • utility for changing executable file parameters such as stack and heap sizes. • DDL - • utility for converting text files into Variable-Length Record (VLR) and Compressed Variable-Length Record (CVLR) files. Verix SDK contains the following tools to create applications: • configuration files containing the standard compiler and linker options. Windows DLL that adds Verix-specific extensions to the SDS debugger. Refer to the Verix Operating System Programmers Manual for more details. • LIBGEN and LIBCHK - direct download utility for downloading files to the terminal. • DDL • VRXCC - tool for compiling and linking applications. NOTE Currently. VERIX/VERIX V DEVELOPMENT SUITE GETTING STARTED GUIDE 15 . ANSI C standard libraries and related tools for the applications to run on Verix V terminals. The Verix V SDK contains the following tools to create applications: . VLR - OUTHDR - tools for creating libraries. It also provides a standard C-interface library for Verix applications. The contents of the installed folders for each component are also explained in this chapter. Debugging Tools Debugging tools for Verix terminals are: • DBMON - • VFI2K - debug monitor program (runs on the terminal).CHAPTER 1 Development Suite Components This chapter provides an overview of the software applications. demonstrates the support for external 950 printer connected to COM1.contains the Verix/Verix V ACT2000 Programmer’s Manual. • Include . • Prn250 - demonstrates the support for external 250 printer connected to COM1. ACT installation folders contain: • Output . • DBMON - debug monitor program (runs on the terminal).contains following sample applications which demonstrate the usage of libraries: • AIETEST - • SHARE - • PRINTER - • FORMATER - • XModem - • PIPTEST - • DBFMTEST - • demonstrates the capabilities of idle engine. • Samples .contains header files required for developing applications based on the ACT2000 library.D EVELOPMENT S UITE C OMPONENTS ACT2000 Debugging Tools • VRXHDR - • VRXLIB - • VLR - utility for changing executable file parameters such as stack and heap sizes. demonstrates using ACT2000 as shared library. ACT2000 Installed Folders The Application Construction Toolkit (ACT) is a collection of C code modules. utility for converting text files into Verix Variable-Length Record (VLR) and Compressed Variable-Length Record (CVLR) files. Debugging tools for Verix V-based terminals are: • VRXDB - debug monitor program (runs on the PC). demonstrates modem functionality. utility for creating static and shared libraries. Prn950 - demonstrates printer functionality. This helps to control the size of the application by reusing code from the toolkit. • FmtrX50 - demonstrates formatter functionality using the P250 and P950 printers.contains ACT2000 library. 16 VERIX/VERIX V DEVELOPMENT SUITE GETTING STARTED GUIDE . You can develop additional specialized functions using the ACT modules as a base. • Docs . demonstrates formatter functionality. Refer to the Verix V Operating System Programmer’s Manual for more details. designed to reduce the effort required to design and develop applications for Verix/Verix V terminals. demonstrates database and file management functionality. demonstrates PIP engine functionality. • Include . If your applications are VMAC compliant. Varrec components. Verix/Verix V Multi-App Conductor (VMAC) is an application manager designed to manage application selection. In Vx670.D EVELOPMENT S UITE C OMPONENTS CardSlot CardSlot The Verix/Verix V CardSlot Library is a layer above the OS that communicates with ICCs (Integrated Chip Cards). and many other multi-application environment related requirements on the Verix/Verix V terminals. Installed Folders VMAC CardSlot installation folders contain: • Output . • Inter Task Message Manager is responsible for running all applications (executables) under the VMAC environment. COM6 and Wi-Fi LAN are connected over USB and can be used independently. VMAC is enhanced for managing the security requirement for USB devices.contains header files required for developing VMAC applications. they can run together seamlessly on the same Verix/Verix V terminal.contains the CardSlot Library which can be directly linked to any application.contains executables: • Device Manager is responsible for device (resource) management within the Verix/Verix V terminals. • Docs . This library provides a high-level interface designed to be independent of the protocol between the chip card slot and the ICC. • Include . the COM3. • FrontEnd provides an easy to use interface for selecting applications. device usage. VERIX/VERIX V DEVELOPMENT SUITE GETTING STARTED GUIDE 17 . COM3 and COM6 USB ports are not part of security architecture as they are externally pluggable.contains the Verix/Verix V CardSlot Library Programmer’s Guide. even if developed independently. LOGSYS.contains header files required for developing applications using CardSlot Library. inter-task synchronization and communications. Installed Folders VMAC installation folders contain: • Output . • ApLoader - • VMAC shared libraries - DevMan - FrontEnd - IMM - ApLoader utility facilitates clearing and defragmenting of the Flash before applications can be downloaded to the terminal. shared library consisting of EESL. Refer to the Multi-App Conductor for Verix and Verix V Programmer’s Guide for details on making applications VMAC compliant. VMAC is enhanced to support security on WLAN device. You can use the CardSlot Library to build Smart Card related transaction applications on Verix/Verix V terminals. This library ensures correct interaction between ICCs and terminals. contains TMA executable and signature file. • Tools . VC Simulator simulates the protocol and functionality of the remote diagnostics server of VeriCentre. VMACsdk - VeriFone terminals are monitored and managed by the Terminal Manager in VeriCentre. • Template .mmc mimic script for running the VC Simulator. • Docs .D EVELOPMENT S UITE C OMPONENTS TMA • Docs . • Demo3 . • Samples .contains template file for Device Mapping Resource Table. Remote Collection.ACT2000 sample to demonstrate the application maintained MIIDs. • Demo1 . The communication between TMA and VeriCentre can be over Dial or IP. Terminal Management Agent (TMA) facilitates the Terminal Manager to retrieve the required terminal information. • Template . • SCTEST - demonstrates the detection of insertion and removal of ICC1 and ICC2.SDK sample to demonstrate the application initiated TMA session.consists of mimic.demonstrates the display of COM data on the screen when it arrives in COM2. • demonstrates reading and printing of magnetic card data on DMLAB1 - swiping. • TMA Installed Folders 18 This application uses VMAC and is not based on ACT. • Tools . This is achieved by using VeriCentre components such as.contains sample applications to demonstrate TMA capabilities. • VMACEX2 - demonstrates background tasks (in this example background printing).exe and the tmahost.contains Verix/Verix V Terminal Management Agent Programmer’s Guide. TMA installation folders contain: • Output . It displays the current time on activation.contains header files for TMA application. printing and release of printer device.contains resource compiler tool and the associated utilities. Diagnostics and Message Management Module. • Samples . You can use this tool before testing your TMA-compliant applications with a test host of VeriCentre.contains Multi-App Conductor for Verix and Verix V Programmer’s Guide.contains sample applications to demonstrate VMAC capabilities: • VMACEX1 - demonstrates run time acquiring. • DMLAB2 . VERIX/VERIX V DEVELOPMENT SUITE GETTING STARTED GUIDE .contains template file for TMA Front End. • Include . contains ClientApp sample demonstrating Messenger interface. Tools available in Verix • utility to transform SDS compiler error messages to VC++ format. Tools installation folder contains the following tools and utilities: All tools are available in both Verix and Verix V unless otherwise specified in this section.contains header files required for Messenger application. FMTERR - Tools available in Verix V • FMTERRORARM - • MakeFileMaker - • API Converter - utility to transform ARM compiler error messages to VC++ format. This workspace contains template code for developing an application. VERIX/VERIX V DEVELOPMENT SUITE GETTING STARTED GUIDE 19 .contains Verix/Verix V Messenger Application User’s Guide. • Docs . • ACT2000 or SDK based application. • Application using static library or shared library. Tools available in both Verix and Verix V • . set of Java classes for converting Verix project make files to Verix V-based terminals. Messenger installation folders contain: • Output . • Single application or VMAC based application. so that double-clicking on the error/warning line takes the developer to the line of code containing the bug. which acts as an interface for sending and receiving messages between terminals and a computer running on VeriCentre composer application. Messages sent from VeriCentre can be viewed on the terminal display using the Messenger application. tool used for converting Verix programs to Verix V programs. • Samples . Tools comprises of various tools and utilities for developing applications for Verix/ Verix V terminals. The wizard guides you through a process of selecting the following options and helps to generate a template code: VERIXVWIZARD • Verix or Verix V is the target platform.contains executable and signature files of Messenger application.a custom application wizard to generate a sample application project workspace.D EVELOPMENT S UITE C OMPONENTS Messenger Messenger Installed Folders Tools Installed Folders NOTE Messenger is an application. • Include . so that double-clicking on the error/warning line takes the developer to the line of code containing the bug. for Verix V The Font Generation Tool is a GUI application which allows you to create. The Memory Calculator tool is an MS Excel spreadsheet which calculates memory requirement for deploying various combinations of the applications. 8x16 and 16x16 resolutions. VERIX/VERIX V DEVELOPMENT SUITE GETTING STARTED GUIDE . • GENDATA - • RCK2 utility for compiling printer template files. This tool also enables you to decide on the effective combination of files (compressed or non-compressed) for any particular download. edit.resource compiler to generate binary resource from ASCII templates and resources. The Font Generation Tool provides the following functionalities: 20 • Generate display font files (VFT and FON file formats): allows to edit and create display font files in VFT and FON formats. You can select between multiple download combinations. On entering the size of the application and the required terminal configuration. for Verix • VerixVAps folder. 24x24. 48x48 and 64x64 resolutions. • Generate printer fonts (PFT file format): allows to create printer font files in the PFT format in 5x8. and to download them to Verix and Verix V-based terminals. printer font files (PFT). 8x8 (supported by P950). TXOFILE - utility for compiling gendata resource files. The Memory Calculator. 32x32. 8x14 (32.and 42-column resolution). These can be of 6x8. MS Excel 2003 must be installed to use this tool. and manage display font files (VFT and FON). This enables you to decide on deploying applications based on the availability of memory.xls is installed under: Font Generation Tool • VerixAps folder.D EVELOPMENT S UITE C OMPONENTS Memory Calculator Memory Calculator • FORMCVT - • PC-based utility that allows you to quickly and easily generate TXO-compatible files. It also enables editing of existing PFT files. . 16x16. The tool supports the following printers: • Omni 33xx ITP (Integrated Thermal Printer) • Omni 3600 ITP • Omni 37xx ITP • Vx5xx ITP • Vx6xx ITP • P950 The main advantage of using Font Generation Tool is that you can generate font files without the knowledge of font file formats. and printer logo files (LGO). the tool calculates the memory requirement. and bitmap files. Also. printer font files. • Convert UNICODE fonts to VeriFone fonts. You can choose an area of 128x128 for Vx670 terminals and 128x64 for other terminals to convert a bitmap to VFT file.contains executables and batch files for Font Generation Tool. To convert a Windows bitmap file to display. The VeriShield FST is used for authenticating the files you download to the terminal. font or logo files. the bitmap file must be monochromatic. A wizard guides you through the steps required for merging the files. • Convert bitmap files to VFT and LGO files: supports the conversion of bitmaps to display font or logo files. Components installed in the Typical installation option are: • Bin . To convert a bitmap file to printer logo file. you can specify an offset value from where the input file characters need to be merged into the output file. which is the maximum resolution of printer.D EVELOPMENT S UITE C OMPONENTS VeriShield FST • Generate printer logo image files (LGO file format): allows to view printer logo files used to print graphics on printable receipts. NOTE Without authentication. Installed Folders VeriShield FST • Convert standard Windows® TTF fonts to VeriFone fonts. • HP Multi Card Access Enabler for PKCS#11. You can select characters by specifying the range from the input file to the output file. • Samples . select an area not exceeding 384x240 pixels. • Merging multiple VFT and FON font files: supports merging multiple VFT and FON files into a single VFT or FON file. • Help . Each file must be digitally signed using the smart card.contains the VeriShield Online Help file. VERIX/VERIX V DEVELOPMENT SUITE GETTING STARTED GUIDE 21 . • VeriShield FST.contains the default certificate and key files. • Smart Card reader drivers. Installed Folders VeriShield FST installation folder contains: • Certificate . applications do not execute on the terminals. logo files.contains display font files. • Microsoft Smart Card Base components. contains file listing the recent changes. • Hlp .contains samples demonstrating usage of VeriFind tool. Omni 33xx ITP. • Hlp . It provides a scripting utility. VeriPrint Printer Simulator is a generic printer simulator for various VeriFone printers (for example. screens on the terminal.contains a card data file.contains configuration files for VeriFone printers. VeriFind installation folder contains: • VeriFind tool. Vx5xx ITP and Vx6xx ITPs. file transfer utility.contains files pertaining to different terminals. such as key presses and magnetic card swipes. • Sample .contains utilities used by VeriFind. Vx5xx ITP. • Docs . RAM status. the P250. • 22 VFIPrinters . Installed Folders VeriFind installation folder contains: • VeriPrint tool and required . The main advantage of using VeriPrint is to save printer stationery that would otherwise be used while testing and debugging applications.dll files.D EVELOPMENT S UITE C OMPONENTS VeriFind VeriFind Installed Folders VeriPrint The VeriFind Test Automation Tool is an integrated testing tool that aids testing applications written for Verix/Verix V terminals. which help automate the execution of test suites. Omni 37xx ITPs. This is a Windows-based tool. or Omni 37xx ITP).contains samples that demonstrate how to use the VeriPrint tool to simulate Omni 33xx. • Utils .contains functions used for testing libraries and applications.contains VeriFind Online Help. This Windows-based tool simulates user actions. • SQAUtils . • Samples . • Target . VERIX/VERIX V DEVELOPMENT SUITE GETTING STARTED GUIDE . • Data .contains VeriFind Online Help. and records user actions to play back later. Vx6xx ITP. date and time as in the terminal. Omni 36xx. out (takes the name of the first file specified in the command). KCL is a batch file which is used to compile and link the source files. For example. DEVELOPMENT PC C SOURCE FILES VERIX AND VERIX V-BASED OMNI SERIES TERMINAL LIBRARIES RUN COMPILE AND LINK EXECUTABLE APPLICATION Figure 1 Creating an Application for Verix OPERATING SYSTEM DOWNLOAD SERVICE CALLS EXECUTABLE APPLICATION Application Development Environment To create Verix-based applications: Compile all the source files using SDS cross compiler.o and Test2.o respectively. VERIX/VERIX V DEVELOPMENT SUITE GETTING STARTED GUIDE 23 .CHAPTER 2 Developing Applications Application Development Environment Applications for Verix and Verix V terminals are written in C or C++ programming languages. The object files corresponding to Test1 and Test2 are Test1. compile the files Test1 and Test2 using the following command: $(VFSDK)\bin\KCL Test1 TEST2 You get the object files and Test1. These are compiled and linked on a PC. and then downloaded to the terminal for execution in Verix/Verix V Operating System environment. For example. use the command: $(VRXSDK)\bin\vrxcc -c test1.o object files by compiling the test1.c respectively.c files respectively. To create test.lib file. run the following command: $(SDS)\cmd\liber -cn test.o and test2. To generate a shared library.out Generating Static Libraries A static library can be created using the liber tool. you can use the following options with the vrxcc: • '-I' to add a directory which contains the .h files (if any) to the include search path.c test2. test1. use Outhdr command as follows: $(VFSDK)\bin\outhdr -t -s 15000 -h 5000 $(OutDir) test1.a test1.o are object files of test1.D EVELOPING A PPLICATIONS Creating an Application for Verix V To allocate sufficient memory required for the application. For example. generate a library file test.lid file before generating the shared library. the object files will be placed in the library. to generate the test1. run the following command: $(VFSDK)\bin\libgen test. $(VRXSDK)\bin\vrxcc -c test1.a This command reads the inputs from the test. 2 Create library .a and then use the following command to generate the test.o) using the Verix V Compiler's (vrxcc) '-c' option.c and test2.o test2.c In addition. Creating an Application for Verix V To create a Verix V-based application: 1 Compile all the source files (. Refer Verix Operating System Programmer’s Manual for more details.o and test2.lib 24 VERIX/VERIX V DEVELOPMENT SUITE GETTING STARTED GUIDE .If a library name is specified as an output file name in the above step using the -o option.cpp) to object files (.a. use the liber command as shown in the previous section. For example.o. Generating Shared Libraries A shared library can be created using the libgen tool. To generate object files. For example.c or .a is the destination static library file.o and test2. and test1.c and test2. use the KCL command as shown earlier in this section. • '-g' to generate debugging information.o where test.c $(VRXSDK)\bin\vrxcc -c test2.c -o test. The following command generates the output file: “$(VSFSTOOL)\filesignature” .out 5 VeriShield FST is used for signing the output file. $(VRXSDK)\bin\vrxcc test.a In addition to the standard compiler option. • ‘-h’ option . .fst file is present in the same directory where make file is present. Creating Shared Libraries A shared library can be created using the object files with vrxcc and vrxlib tools. It should contain library base name and library id number fields. the functions in test1.to create an absolute library.o.to set the heap size.o and test2.o -o testapp.fst file is present. to create a shared library test. For example.e. For example.c test. For example.to create a position independent library.out output file. The library description file describes the library name and its functions (i. $(VRXSDK)\bin\vrxlib test VERIX/VERIX V DEVELOPMENT SUITE GETTING STARTED GUIDE 25 . the following options can also be used: • shlabs • shpics .fst -nogui Here the -nogui option suppresses the user interface of the File Signing Tool. For example.c is the file containing the main() function. the object files generated in step 1 can be directly linked with the test.c and test2.lib using the object files test1..o test2.out can be generated as follows: $(VRXSDK)\bin\vrxcc test.to set the stack size.out 4 The vrxhdr tool can be used to set the stack and heap size of the output file: • ‘-s’ option .D EVELOPING A PPLICATIONS Creating an Application for Verix V Then . assuming that the testapp.lib -o testapp. the output file testapp. the stack size can be set to 15000 and heap size to 5000 using: $(VRXSDK)\bin\vrxhdr -s 15000 -h 5000 testapp. assuming that test. make sure that a library description file test.out generated in the previous steps.c to generate the testapp.c file containing the main() function.o test2.c). for the output file testapp.The shared library can be created using the command: $(VRXSDK)\bin\vrxcc test1.out 3 If the library is not created as mentioned in the step 2. Make sure that the outputfile.lid is present.c test1.out file can be generated by linking the library with the . For example.o -o test.\testapp. 26 VERIX/VERIX V DEVELOPMENT SUITE GETTING STARTED GUIDE .out Refer the documents and ReadMe files of the respective components listed in the Documentation section.D EVELOPING A PPLICATIONS Creating an Application for Verix V The above command creates the shared library test.lib=f:/ test.lib. To link the above shared library with your application.lib $(OutDir)\testapp. for more information on the Development Suite components. download the shared library to the flash drive in GID 15 and run the following command: $(VRXSDK)\bin\vrxhdr -s 15000 -h 5000 -l test. D EVELOPING A PPLICATIONS Creating an Application for Verix V VERIX/VERIX V DEVELOPMENT SUITE GETTING STARTED GUIDE 27 . com Verix/Verix V Development Suite Getting Started Guide VeriFone Part Number 23901.VeriFone. Inc. 95110 USA 1-800-VeriFone www. Revision D . 2099 Gateway Place. Suite 600 San Jose.verifone. CA.