SAP POS 2.3 Installation Guide

Transcription

1 Guide SAP Point-of-Sale Document Version: Covering the application formerly known as SAP Transactionware General Merchandise, version 10.3 and its components: Store Configurator, Xpress Server, Point-of-Sale Client, Mobile Point-of-Sale client, and Store Manager.

2 Typographic Conventions Type Style Example Description Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Textual cross-references to other documents. Example EXAMPLE Example Example <Example> Emphasized words or expressions. Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE. Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools. Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. EXAM PLE Keys on the keyboard, for example, F2 or EN TER SAP SE or an SAP affiliate company. All rights reserved. Typographic Conventions

3 Document History Version Date Change Updated the document template. Updated disk space requirements. Added Windows 2012R2 and Microsoft SQL server 2012 (32 Bit) support. Updated the special instructions for Installing Microsoft SQL 2008 Express 2008 R2 Edition or SQL 2012 Express and Standard Edition. Document History 2016 SAP SE or an SAP affiliate company. All rights reserved. 3

4 Table of Contents 1 Introduction About this Document New Features SAP Notes for the Additional Information Naming Conventions Planning Determining What Components to Install Determining Your Store Architecture (Sample Environments) Preparation System Requirements Hardware Certification Prerequisites Starting the Installing Database Tools Installing Databases: Xpress Server and Electronic Journal Viewer Databases Installing Xpress Server Installing Electronic Journal Viewer Installing Store Manager Installing Point-of-Sale Installing Mobile Point-of-Sale Client Installing Store Configurator Installing Software Development Kit Installing AppSight Service Black Box Installing Diagnostic Agents Installing SAP SMD Agents Performing Follow-On Activities After SAP POS Automated Installer Configuring Automated Installer Installing SAP POS with the Automated Installer Sample AUTOINST.INI and <store number>.ini Files Pre- and Post Special Instructions for Installing Databases Installing Microsoft SQL 2008 Express 2008 R2 Edition or SQL 2012 Express and Standard Edition: Special Instructions Setting up a Backup Server Obtaining the Database Server Name Changing the Display of POS Locations when Running Multiple POS Units on a Single Machine SAP SE or an SAP affiliate company. All rights reserved. Table of Contents

5 5.5 Localization and Language Support Language-Check Message During Translating Parameter Texts Configuring Mobile POS Devices Setting up the Wireless Network Connecting Handheld Devices to the Wireless Network Connecting a Printer to the Wireless Network Troubleshooting the Mobile POS Configuration Running Mobile POS Accessing Help Documentation and Changing the Default Location Performing the in MSI Silent Mode Integrating SAP POS with File and Message Transfer Functions Activating Client Software in SAP POS Changing Configuration File Settings Using the Security Key File Additional Information Removing POS Appendix Legal Software Terms Table of Contents 2016 SAP SE or an SAP affiliate company. All rights reserved. 5

6 1 Introduction This section provides introductory information that you need to know before you install SAP Point-of-Sale (SAP POS) About this Document This guide provides step-by-step instructions for installing SAP POS 10.3 as well as prerequisites and postinstallation information. This guide is intended for SAP, partner, and customer system administrators and technology consultants. Functions and Components SAP POS is the leading transaction management and point-of-sale (POS) application for general merchandise retailers running client-server environments. SAP POS consists of the following: Store software (Store Manager, Xpress Server) running in a store s back office to serve connective, operative, and administrative needs, such as reporting, payroll entry, file maintenance, cash management, and inventory control POS client software to process POS transactions Head office software (Store Configurator) for central configuration that enables you to control all POS terminal functions and processes by maintaining parameter definitions for tender and transaction types, tax settings, promotions, keyboard layouts, terminal menus, cashier prompts, customer records, and many more. You set most parameters only once, or infrequently, to reflect core aspects of your business model, such as tender types or terminal display settings. Other parameters, such as price lookup (PLU) definitions and promotion settings, can be modified more frequently for maximum flexibility. In addition, you can translate parameter definitions, menus, and other user-interface objects into languages other than English. Integration SAP POS can be integrated with the following software: SAP POS Store Data Transfer for Retail application1 (for more information, see section 5.10 Integrating SAP POS with File and Message Transfer Functions) SAP Returns Authorization application 1 Formerly called SAP Centralized Electronic Funds Transfer (SAP CEFT), which was known previously as Transnet SAP SE or an SAP affiliate company. All rights reserved. Introduction

7 SAP Stored Value Program application. For more information about these applications, see the appropriate installation and upgrade guides. Constraints SAP POS does not rely on a central user-management system for user management and authentication, since SAP POS users are valid only within the SAP POS application. This, however, does not minimize the level of security the application provides. 1.2 New Features For a list of new functions in SAP POS, see What's New available at help.sap.com (registration may be required). The following new features have been added to SAP POS 10.3: Area Tools 64-bit (X64) Operating System Database Servers Mobile Point-of-Sale Description of AppSight Black Box software is now included in the installation procedure. As of service pack 09 SAP POS 2.3 supports Microsoft Windows: System Type - 32-bit (x86) or 64-bit (x64) operating systems. As of SP 11, support was added for Windows 2012R2. Additional database servers SAP Sybase 16 (32-bit) database and Microsoft SQL server 2008 R2 (32-bit) are supported. As of SP 11, support was added for Microsoft SQL 2012 (32 bit) On 64-bit (X64) Operating System Mobile Point-of- Sale, user exits (UE) are supported. Full functional use is available only on a 32-bit (X86) operating system. 1.3 SAP Notes for the You must read any SAP Notes before you start the installation. SAP Notes contain the most recent information on the installation, as well as corrections to the installation documentation. Make sure that you have the up-to-date version of each SAP Note, which you can find at: Introduction 2016 SAP SE or an SAP affiliate company. All rights reserved. 7

8 1.4 Additional Information More information is available as follows: Documentation Description Internet Address Title Diagnostics RCA Wiki End-to-End Root Cause Analysis General Quick Links Description SAP Help Portal SAP Notes Released platforms and operating systems System sizing Security Front-End installation Internet Address help.sap.com sap notes platforms sizing security help.sap.com 1.5 Naming Conventions Throughout this document the following naming conventions apply. Terminology The term SAP system refers to Point-of-Sale. Variables Variable <SAPSID> <sapsid> <DBSID> <dbsid> <INSTDIR> Description SAP system ID in uppercase letters SAP system ID in lowercase letters Database ID in uppercase letters Database ID in lowercase letters directory for the SAP system SAP SE or an SAP affiliate company. All rights reserved. Introduction

9 Variable <DVD_DIR> <OS> <PROGRAM_FILES> <SYSTEM> Description Directory on which a DVD is mounted Operating system name within a path On a 32-bit (x86) operating system it is C:\Program Files\ or for a 32-bit (x86) application on a 64-bit (x64) operating system it is C:\ Program Files(X86)\ System folder of the operating system. It is usually C:\Windows\System32 or on a 64-bit operating system for 32-bit applications it is usually C:\Windows\SysWOW64 The following examples show how the variables are used: Example C:\<OS>\system32 Introduction 2016 SAP SE or an SAP affiliate company. All rights reserved. 9

10 2 Planning Process Flow Determining What Components to Install Determining Your Store Architecture (Sample Environments). 2.1 Determining What Components to Install There are two types of installations: head office and store solution. The following table lists the required and optional components for each type of installation: Type Required Component Optional Component Head office Store Store Configurator Database Tools (required for database maintenance and upgrades) Xpress Server Xpress Server database Store Manager Database Tools (required for database maintenance and upgrades) Point-of-Sale (POS) Client Software Development Kit Electronic Journal Viewer Electronic Journal Viewer database (required if you install Electronic Journal Viewer) Mobile POS Client (required only if you want to run mobile applications) 2.2 Determining Your Store Architecture (Sample Environments) The following examples show various combinations of store installation components that can be installed on the same or on different pieces of hardware. Compare your requirements and model your store installation accordingly. Example Store Install on Server System Install on POS System Install on Store Manager System Store A DBMS server Xpress Server Xpress Server database POS Client SAP SE or an SAP affiliate company. All rights reserved. Planning

11 Example Store Install on Server System Install on POS System Install on Store Manager System A server with Store Manager and several separate POS terminals Database Tools Store Manager Store B DBMS server POS Client A server with Store Manager, Electronic Journal Viewer, several separate POS terminals, and handheld mobile devices Xpress Server Xpress Server database Electronic Journal Viewer database Electronic Journal Viewer Mobile POS Client Database Tools Store Manager Store C A server, several separate POS terminals, handheld mobile devices, and a separate Store Manager and Electronic Journal Viewer DBMS server Xpress Server Xpress Server database Database Tools POS Client Mobile POS Client SQL client/connectivity software from the corresponding DBMS vendor Store Manager Electronic Journal Viewer Electronic Journal Viewer database Store D DBMS server A server, POS terminal, Store Manager, and Electronic Journal Viewer all on one system Xpress Server Xpress Server database Electronic Journal Viewer database Electronic Journal Viewer Database Tools POS Client Store Manager Planning 2016 SAP SE or an SAP affiliate company. All rights reserved. 11

12 3 Preparation Process Flow System Requirements Hardware Certification Prerequisites. 3.1 System Requirements This section outlines the system requirements for SAP POS components. For an up-to-date list of supported operating systems and databases for each component, see support.sap.com/pam, other minimum and optimum requirements are provided below. The specifications given below are based on a typical implementation. However, you can install components in different configuration combinations. Use these specifications as a guideline since the requirements of each retail environment can be different. For each configuration, you should perform usability testing to determine if the system performance is acceptable. Note It is vital for retail activity to be uninterrupted should a main server fail. To ensure uninterrupted activity, you can set up a backup server to support the main server s functions. For information about how to set up a backup server, see section 5.2 Setting up a Backup Server. POS Client Minimum System Requirements Optimum System Requirements 10 SAPS2 10 SAPS 1 GB RAM above OS memory 2 GB RAM above OS memory 5 GB disk space available after installation of software 10 GB disk space available after installation of software 2 SAPS (SAP application performance standard) is a unit of performance measurement. To determine the SAPS of your hardware, contact your vendor. For more information about system sizing, go to service.sap.com/sizing and then choose Sizing Guidelines Solutions & Platforms New Structure Industry Solutions SAP POS Sizing and then click on POS Sizing Questionnaire SAP SE or an SAP affiliate company. All rights reserved. Preparation

13 Xpress Server with Store Manager Minimum System Requirements Optimum System Requirements 50 SAPS 350 SAPS 4 GB RAM 4 GB RAM 30 GB disk space available after installation of software and database 60 GB disk space available after installation of software and database Store Configurator Minimum System Requirements Optimum System Requirements 5 SAPS 5 SAPS 1 GB RAM above OS memory 2 GB RAM above OS memory 10 GB disk space available after installation of software and database 15 GB disk space available after installation of software and database Mobile POS Client The Mobile POS Client is composed of a networking module, a simple GUI, and hardware components for a scanner and magnetic stripe reading (MSR) device. The printer is a TCP/IP printer. The following devices are supported: System Requirements Specification 64 MB RAM 64 MB flash Wireless Infrastructure g invoking WPA2 encryption is recommended for secure network transmission Disk Space Requirements The following table lists the disk space requirements for each product installation: System Requirements Product SQL Server Xpress Server (including Database Tools and back office or journal databases) Specification Disk Space Required 2GB Minimum (MS SQL2012) 300 MB Preparation 2016 SAP SE or an SAP affiliate company. All rights reserved. 13

14 System Requirements Store Manager Specification 100 MB Electronic Journal Viewer POS Client Store Configurator Software Development Kit 20 MB 100 MB 100 MB 10 MB 3.2 Hardware Certification SAP maintains a list of certified hardware devices that are supported by SAP POS. For more information about certified hardware, talk to your SAP representative. 3.3 Prerequisites Ensure that your hardware and software meet the following prerequisites. Stop all previously installed retail applications such as SAP POS Store Data Transfer for Retail or SAP Returns Authorization as they may be using some files in folders that the installer needs to update, which can interfere with the installation. Files, Drivers, and Other Software All computers must be loaded with the TCP/IP protocol. The NetBEUI protocol may also be loaded, but is optional. The protocols must be installed and configured before any SAP applications or required support components are installed. All OPOS hardware drivers for required peripheral equipment must be installed on machines where the POS Client is installed. You can download them from their respective vendors. The OPOS drivers should be installed in the mode in which the POS Client is run; for example, at an administrator security level. If the OPOS drivers are installed in administrator mode, then the POS Client should always be run in the same mode; otherwise some setup configurations may not be maintained. Note 1. Powershell is required to start the main installer. If it was not installed as part of the operating system deployment, you may get an error during the installation. Install Powershell using the following steps: 2. Open the Start menu, choose All Programs Administrative Tools, and then choose Server Manager. Click Features, choose Add Features Administrative Tools, and then choose Server Manager. The Add Features Wizard appears. Select the Windows PowerShell check box, and then choose Next to install it. 3. When installing SAP POS on terminals running the Windows Embedded POSReady 2009 operating system, the operating system requires that the Command Line Utilities component is installed. The SAP SE or an SAP affiliate company. All rights reserved. Preparation

15 Command Line Utilities component can be selected for installation during the initial installation of the operating system on the POS terminal, or you can add this component later via the Control Panel. Choose Start Control Panel Add or Remove Programs. Select the Add/Remove Windows Components icon and then select Accessories and Utilities and Command Line Utilities checkboxes. You must have the most up-to-date version of the ole32.dll file. If the installation program does not detect the correct file, a warning message appears. When this occurs, you must cancel the installation process, install ole32.dll, and then restart the installation process. You must have the most current version of the msvcp60.dll file. This file is typically located under C:\Windows\<SYSTEM>. If you do not find a copy of this file on your system, you can perform a search for it on the Internet using msvcp60.dll download as the search term. After you download this file, copy it to the relevant directory as described above, for example, C:\Windows\System32. You must download the MSXML 4.0 installer from the following location: c5d7485f2b42&displaylang=en. This installs all files required for the installation to their required locations. You must have the most up-to-date version of the Microsoft Visual C Redistributable Package (x86) files. If the installation program does not detect the correct file, an error message appears when it tries to register the XRules.DLL. When this occurs, you must cancel the installation process, install Microsoft Visual C Redistributable Package (x86), and then restart the installation process. The latest version of Microsoft Visual C Redistributable Package (x86) can be obtained at Microsoft s Download Center site. Before installing Store Manager, Store Configurator, Database Tools, or Electronic Journal Viewer on Microsoft Windows Server, you must ensure that the following DLL files exist in the C:\<OS>\<SYSTEM> directory: Atl71.dll, Msvcp71.dll, and Msvcr71.dll. If these files do not exist, you can download them from the third-party resource at (site recommended by Microsoft). Note SAP provides third-party information to help customers find technical support. This information may change without notice. SAP does not guarantee the accuracy of this third-party information. To install encryption, you need the security key file keyfile.txt and its password. These should be available from your head office. Note Before beginning the installation, place the keyfile.txt in a known folder and note the password. When running Windows 2008 and/or Windows 7, administrative privileges are required by the installer. If necessary, use the Run As Administrator command to elevate your privileges. Refer to Microsoft documentation for more information on elevating privileges. Note After running the installer using elevated permissions, additional permissions might be required for the user account that will be used to run the application. At a minimum, full-access permissions are required for the application folder. Note The installation and configuration of an FTP server may be required for some Integration Landscapes. Please verify your requirements for integration with SAP PI. Preparation 2016 SAP SE or an SAP affiliate company. All rights reserved. 15

16 4 Before starting the installation of SAP POS, review the first three sections of this guide. There are two types of installations: store solution and head office. When you select a store solution installation, the following components are installed in the order listed: Database Tools (required) is utilized for regular maintenance of the Store database for functions such as purging and upgrading. Databases maintained include Xpress Server database and Electronic Journal Viewer database Xpress Server database (required) is where all data is stored and is accessed by the Xpress Server Electronic Journal Viewer database (optional, but required if you choose to install Electronic Journal Viewer) is where all journal data is stored and is accessed by the Electronic Journal Viewer Xpress Server (required) component is the service that processes requests from the POS Clients and the Store Manager Electronic Journal Viewer (optional) component provides searching and viewing of journal records at the store level Store Manager (required) component provides store administration activities such as merchandising, file maintenance, reporting and cash management. Xpress Server and Xpress Server database must be installed for Store Manager to work Point-of-Sale (POS) Client (required) is used to perform retail sales transactions in a B2C brick and mortar scenario. Xpress Server and Xpress Server database must be installed for the POS Client to work Mobile POS Client (optional) is used to perform retail sales transactions in a B2C brick and mortar scenario where mobility is needed to move throughout the store. Xpress Server and Xpress Server database must be installed for the POS Client to work. When you select a head office installation, the following components are installed in the order listed: Database Tools (required) is utilized for upgrading the Configurator database Store Configurator (required) component is utilized to define the business rules that are then transmitted to the Xpress Server, Store Manager and POS Client Software Development Kit (optional) provides extension points/user exits to expand the capabilities of the application through coding. The Xpress Server, Xpress Server database, and POS Client are required if the Software Development Kit is used. Ensure that you have met the requirements outlined in the following sections for the components that you will be installing. Process Flow The following provides installation procedures for the SAP POS components Starting the Installing Database Tools Installing Databases: Xpress Server and Electronic Journal Viewer DatabasesInstalling Databases: Xpress Server and Electronic Journal Viewer SAP SE or an SAP affiliate company. All rights reserved.

17 Installing Xpress Server Installing Electronic Journal Viewer Installing Store Manager Installing Point-of-Sale Installing Mobile Point-of-Sale Client Installing Store Configurator Installing Software Development Kit Installing AppSight Service Black Box Installing Diagnostic Agents Automated Installer. 4.1 Starting the Procedure 1. The SAP POS installation is available. To download the application: o Go to support.sap.com/swdc. o Choose Software Downloads Software Download Center s and Upgrades Browse our Download Catalog Industry-Specific Components SAP POS. o Select the appropriate version that you want to install and then choose. o In the SAP POS 10.3 window that lists what is available in this installation package, select the appropriate checkbox. o Choose Add to Download Basket and then Download Basket. 2. When the application has finished downloading: Note o As of service pack 09 SAP POS 2.3 supports Microsoft Windows: System Type - 32-bit (x86) or 64-bit (x64) operating systems. As of SP 11, Windows 2012R2 is supported o Additional database servers SAP Sybase 16 (32-bit) database, Microsoft SQL server 2008 R2 (32-bit) and Microsoft SQL server 2012 (32 Bit) are supported o Sybase SQL Anywhere 11, Sybase SQL Anywhere 12 or Microsoft SQL server 2008 are not supported on a 64-bit (x64) operating system. Folders used for 32-bit (x86) or 64-bit (x64) Operating System AppSight Mobile Point-of-Sale Point-of-Sale SDK Utils UU 2016 SAP SE or an SAP affiliate company. All rights reserved. 17

18 Folders used for 32-bit (x86) or 64-bit (x64) Operating System Also, the root folder with files INSTALL.bat, main.ms_, and version.ini. Folders used for 32-bit (x86) Operating System DBTools Electronic Journal Store Configurator Store Manager Xpress Server Folders used for 64-bit (x64) Operating System DBToolsX64 Electronic JournalX64 Store ConfiguratorX64 Store ManagerX64 Xpress ServerX64 o Start the installation: o For Windows 2008, Windows 7 or Windows 2012R2, right click on INSTALL.BAT and choose Run as Administrator o For all other supported operating systems, double-click on INSTALL.BAT. o Or, to use the Automated Installer to install the store solution, see 4.13 Automated Installer. Note On Windows 7, the INSTALL.BAT will not launch if the directory path where the batch file is located contains parenthesis characters. This can be resolved by adding a space into the directory name containing the parenthesis characters. For example, SAP(POS)Installer can be changed to SAP (POS)Installer. Caution On Windows 2008 or Windows 7, do not run setup.exe or the MSI to install the software manually. 3. On the SAP POS welcome screen, choose either the head office or the store installation path. Depending on the installation type you choose, either the store solution or head office installation path shows the required and optional components. By default, all components are selected. Deselect the components that you do not want to install. 4. To install the selected components, select Install. The SAP POS installation begins. Note o As of the SAP POS 2.2 release, SAP provides you with an option to install the support utility AppSight Service Black Box 4.2 Installing Database Tools Use Database Tools is a required helper component for proper database maintenance and upgrade of both the head office and store installations SAP SE or an SAP affiliate company. All rights reserved.

19 Note On a 64-bit operating system, SAP Sybase 16 (32-bit) database, Microsoft SQL server 2008 R2 (32-bit) and Microsoft SQL Server 2012R2 (32 bit) are supported. Sybase SQL Anywhere 11, Sybase SQL Anywhere 12 or Microsoft SQL server 2008 are not supported on a 64-bit operating system. Prerequisites You have installed Microsoft SQL Server 2005 Backward Compatibility Pack for SQL 2008 (x86 on 32-bit) or (x64 on 64-bit). Please note that the backward compatibility pack is not needed for SQL 2012R2 You have installed Microsoft Visual C SP1 Redistributable Package (x86 on 32-bit) or (x64 on 64-bit). Procedure Note If the above prerequisites are not installed, the Database Tools InstallShield Wizard lists the missing requirements and prompt you to install them at this time. If you do not have SAP SQL Anywhere installed, uncheck the option Use DBTools for CONFIGURATOR Database. 1. On the Welcome screen for the Database Tools installation, select Next. 2. On the Destination Folder screen, do the following: o Specify the store language o Identify the folder where Database Tools is to be installed o In the Please Select Your Store Language dialog box, choose the appropriate language o To install to the folder displayed, select Next. To install to another folder, select Change. In the Change Current Destination Folder dialog box, navigate to the appropriate folder and select OK. Click Next to continue. 3. Choose the database type used for a back office database. Select Use DBTools for BACKOFF and select the type of database used from the list under BACKOFF Database Parameters. Proceed as follows and repeat this step for a journal database: 4. If the database is Sybase SQL Anywhere, proceed as follows: o Enter the server name o To change the backup folder, select Change o Navigate to the appropriate folder o Select OK. 5. If the database is Microsoft SQL Server, proceed as follows: o Enter the server name. The default is the current server name o Choose Connect o On the Database Server screen, to select another server choose Browse and then OK o Select Logon. 6. For a Store Configurator database (for head office installation, Sybase SQL Anywhere only): o Enter the directory path where the Store Configurator database is to be located 2016 SAP SE or an SAP affiliate company. All rights reserved. 19

20 o To change the location of the folder, select Change o Navigate to the appropriate folder o Select OK. 7. To continue, select Next. 8. To begin the Database Tools installation, on the Ready to Install screen select Install. 4.3 Installing Databases: Xpress Server and Electronic Journal Viewer Databases Use Xpress Server and Electronic Journal Viewer databases are relevant only for the store installation. The Xpress Server database is a required component; the Electronic Journal Viewer database is optional, unless you are installing Electronic Journal Viewer, in which case the database is also required. Note On a 64-bit operating system, SAP Sybase 16 (32-bit) database, Microsoft SQL server 2008 R2 (32-bit) and Microsoft SQL server 2012R2 (32 bit) are supported. Sybase SQL Anywhere 11, Sybase SQL Anywhere 12, and Microsoft SQL server 2008 are not supported on a 64-bit operating system. Procedure This procedure is the same for both databases: Xpress Server and Electronic Journal Viewer. If you selected both databases when starting the installation, first install the Xpress Server database and then the Electronic Journal Viewer database. 1. On the Welcome screen for the database installation (either Xpress Server database or Electronic Journal Viewer database), select Next. 2. On the Destination Folder screen, do the following: o Specify the store language o Identify the folder where the database is to be installed. 3. In the Please Select Your Store Language dialog box, choose the appropriate language. 4. To install to the folder displayed, select Next. To install to another folder, select Change. In the Change Current Destination Folder dialog box, navigate to the appropriate folder and select OK. 5. On the Database Type screen, choose the appropriate database driver. The database server displayed is based on one of the following choices: o If you choose Sybase SQL Anywhere, enter the database server name and choose Next o If you choose the MS SQL Server, enter the database server name and choose Next o Enter or browse to locate the database server. The default is the current server name. Provide the server logon ID and password. To continue, choose Next SAP SE or an SAP affiliate company. All rights reserved.

21 6. On the Database Server Backup Option screen, choose the database backup option required for your recovery model. o If you choose Full Recovery Model, the log file can grow significantly but database recovery capabilities will be higher. To continue, choose Next o If you choose Simple Recovery Model with Auto Shrink On, the log file is smaller and reduces recovery capabilities. To continue, choose Next. 7. To begin the database installation, on the Ready to Install screen select Install. 8. Repeat the procedure if you are installing the Electronic Journal Viewer database. Result After the Xpress Server Database is installed, you must restart the server. For more information, see Performing Follow-On Activities After SAP POS. 4.4 Installing Xpress Server Use Xpress Server is a required component and relevant only for the store installation. Note XPS Server must be started as an Administrator to allow the option to stop/start Xpress Server from the SAP Transactionware GM interface. Right click the XPS server icon and choose Run as Administrator or change the compatibility by selecting Properties Compatibility Run this program as an administrator. Prerequisites You have installed the Xpress Server database (see sections 4.4 Installing Xpress Server and 4.5, Installing Electronic Journal Viewer) If you use encryption (security key), make sure that you have placed the keyfile.txt in a known folder and have the password. Both are required for this installation step. Procedure 1. On the Welcome screen for the Xpress Server installation, select Next. 2. On the Destination Folder screen, do the following: o Specify the store language o Indicate that you are installing or using a security key container o Identify the folder where the Xpress Server is to be installed. 3. In the Please Select Your Store Language dialog box, select the appropriate language SAP SE or an SAP affiliate company. All rights reserved. 21

22 4. To install a new security key container, or if you are using an existing security key container, ensure that the Install Security Key Container checkbox is selected. Caution Access rights for working with the security key container (for example, deleting, importing, or exporting it) are limited to the user who initially created this file. This is a security feature that prevents other users from manipulating the file after it has been installed. When installing the security key container, you must log on to the machine using the same logon ID and password used by the person who initially created the security key file. (This user requires administrator rights.) Failure to do this results in an error. 5. To install to the folder displayed, select Next. To install to another folder, select Change. In the Change Current Destination Folder dialog box, navigate to the appropriate folder and select OK. 6. On the Database Type screen, choose the appropriate database driver. The database server displayed is based on one of the following choices: o If you choose Sybase SQL Anywhere enter the database server name and select Next o If you choose the MS SQL Server, enter the database server name or select Browse to locate it. The default value is the current server name. Select Next. 7. On the Database Credentials screen, enter the logon ID and password used by the Xpress Server to connect to the back office database and select Next. Note Logon ID and password should be provided by the database administrator. The database account specified by the logon ID must have sufficient permissions for the back office database. 8. On the Install Security Key Container screen, in Select Location of the Keyfile.txt enter the location of the keyfile.txt. If installing a new key, enter the security container password. If the security key already exists, specify the folder where the keyfile.txt resides, the key file password and the security key container password. Select Next. Note Passwords are case-sensitive. 9. To begin the Xpress Server installation, on the Ready to Install screen select Install. Result After the Xpress Server is installed, you must restart the server. For more information, see Performing Follow-On Activities After SAP POS SAP SE or an SAP affiliate company. All rights reserved.

23 4.5 Installing Electronic Journal Viewer Use Electronic Journal Viewer is an optional component and relevant only for the store installation. Prerequisites You have installed the Electronic Journal Viewer database. For more information, see 4.3 Installing Databases: Xpress Server and Electronic Journal Viewer Databases If you use encryption (security key), make sure that you placed the keyfile.txt in a known folder and have the password. Both are required for this installation step. Note The Electronic Journal Viewer component requires the Windows operating system date format set to MM/DD/YYYY; the display resolution must be 1280 x 1024 or higher. Procedure 1. On the Welcome screen for the Electronic Journal Viewer installation, select Next. 2. On the Destination Folder screen, do the following: o Specify the store language o Indicate that you are installing or using a security key container o Identify the folder where the Electronic Journal Viewer is to be installed. 3. In the Please Select Your Store Language box, select the appropriate language. 4. To install a new security key container, or if you are using an existing security key container, ensure that the Security Key Container checkbox is selected. Caution Access rights for working with the security key container (for example, deleting, importing, or exporting it) are limited to the user who initially created this file. This is a security feature that prevents other users from manipulating the file after it has been installed. When installing the security key container, you must log on to the machine using the same logon ID and password used by the person who initially created the security key file. (This user requires administrator rights.) Failure to do this results in an error. 5. To install to the folder displayed, select Next. To install to another folder, select Change. In the Change Current Destination Folder dialog box, navigate to the appropriate folder and select OK. 6. On the Database Type screen, choose the appropriate database driver. The database server displayed is based on one of the following choices: o If you choose the Sybase SQL Anywhere option, enter the database server name and select Next. o If you choose the MS SQL Server, enter the database server name or select Browse to locate it. The default value is the current server name. Select Next SAP SE or an SAP affiliate company. All rights reserved. 23

24 7. On the Database Credentials screen, enter the logon ID and password and select Next. 8. On the Install Security Key Container screen, in Select Location of the Keyfile.txt enter the location of the keyfile.txt. If installing a new key, enter the security container password. If the security key already exists, specify the folder where the keyfile.txt resides, the key file password and the security container password. Select Next. Note Passwords are case-sensitive. 9. On the Xpress Server Local Path screen, enter a complete directory path for the location of the Xpress Server and select Next. 10. To begin the Electronic Journal Viewer installation, on the Ready to Install screen select Install. 4.6 Installing Store Manager Use Store Manager is a required component and relevant only for the store installation. Prerequisites The appropriate database is installed If you use encryption (security key), make sure that you placed the keyfile.txt in a known folder and have the password. Both are required for this installation step. Note The Store Manager component requires the Windows operating system date format set to MM/DD/YYYY; the display resolution must be 1280 x 1024 or higher. Procedure 1. On the Store Manager installation Welcome screen, select Next. 2. On the Destination Folder screen, do the following: o Specify the store language o Indicate that you are installing or using a security key container o Identify the folder where the Store Manager is to be installed. 3. In the Please Select Your Store Language dialog box, choose the appropriate language. 4. To install a new security key container, or if you are using an existing security key container, ensure that the Security Key Container checkbox is selected SAP SE or an SAP affiliate company. All rights reserved.

25 Caution Access rights for working with the security key container (for example, deleting, importing, or exporting it) are limited to the user who initially created this file. This is a security feature that prevents other users from manipulating the file after it has been installed. When installing the security key container, you must log on to the machine using the same logon ID and password used by the person who initially created the security key file. (This user requires administrator rights.) Failure to do this results in an error. 5. To install to the folder displayed, select Next. To install to another folder, select Change. In the Change Current Destination Folder dialog box, navigate to the appropriate folder and select OK. 6. On the Install Security Key Container screen, in Select Location of the Keyfile.txt enter the location of the keyfile.txt. If installing a new key, enter the security container password. If the security key already exists, specify the folder where the keyfile.txt resides, the key file password and the security container password. Select Next. Note Passwords are case-sensitive. 7. On the Database Type screen, choose the appropriate database driver. Enter the database server and the database server IP address. Select Next. 8. On the Database Credentials screen, enter the logon ID and password used by the Store Manager to connect to the back office database and select Next. Note Logon ID and password should be provided by the database administrator. The database account specified by the logon ID must have sufficient permissions for the back office database. 9. On the Xpress Server Local Path screen, enter a complete directory path for the location of the Xpress Server and then choose Next. 10. To begin the Store Manager installation, on the Ready to Install the Program screen select Install. 4.7 Installing Point-of-Sale Use The Point-of-Sale (POS) Client is a required component and relevant only for the store installation. Prerequisites If you use encryption (security key), make sure that you have placed the keyfile.txt in a known folder and have the password. Both are required for this installation step SAP SE or an SAP affiliate company. All rights reserved. 25

26 Note The POS Client component requires the Windows operating system date format set to MM/DD/YYYY; the display resolution must be 800 x 600 or higher. If you are planning to use COM, the screen resolution should be set to 1024 x 768 or higher. Procedure 1. On the Point-of-Sale installation Welcome screen, select Next. 2. On the Destination Folder screen, do the following: o Specify the store language o Indicate that you are installing or using a security key container o Identify the folder where the POS Client is to be installed. 3. In the Please Select Your Store Language box, select the appropriate language. 4. To install a new security key container, or if you are using an existing security key container, ensure that the Security Key Container checkbox is selected. Caution Access rights for working with the security key container (for example, deleting, importing, or exporting it) are limited to the user who initially created this file. This is a security feature that prevents other users from manipulating the file after it has been installed. When installing the security key container, you must log on to the machine using the same logon ID and password as the person who initially created the security key file. (This user requires administrator rights.) Failure to do this results in an error. 5. To install to the folder displayed, select Next. To install to another folder, select Change. In the Change Current Destination Folder dialog box, navigate to the appropriate folder and select OK. 6. On the Install Security Key Container screen, in the Select Location of the Keyfile.txt field enter the location of the keyfile.txt. If installing a new key, enter the security container password. If the security key already exists, specify the folder where the keyfile.txt resides, the key file password and the security container password. Select Next. Note Passwords are case-sensitive. 7. To begin the POS Client installation, on the Ready to Install screen, select Install SAP SE or an SAP affiliate company. All rights reserved.

27 4.8 Installing Mobile Point-of-Sale Client Use The Mobile POS Client is an optional component and is relevant only for the store solution installation. The Mobile POS Client is composed of a networking module, a simple GUI, and hardware components for a scanner and magnetic stripe reading (MSR) device. Prerequisites Ensure that the following prerequisites are met before installing the Mobile POS Client: Before installing the Mobile POS Client, make sure that Xpress Server database, Xpress Server, and POS Client are all installed on the same machine to which the mobile device is connected Microsoft Winsock control DLL file MSWINSCK.OCX is installed to the following location: C:\<OS>\<SYSTEM>\MSWINSCK.OCX Note Mobile POS support is available only on a 32-bit (X86) operating system. On a 64-bit (X64) operating system Mobile Point-of-Sale user exits (UE) are supported. To obtain this file, download MSWINSCK.CAB from the following location: The file copied to the appropriate system folder is registered. To register the file, enter the following command at the command prompt: regsvr32\<os>\<system>\mswinsck.ocx Or on a 64-bit operating system enter the following command at the command prompt: regsvr32\<os>\syswow64\mswinsck.ocx Microsoft Windows Mobile Device Center Version or later is installed on the system and running. If it is not running, a pop-up window asks you to connect during installation. If this is the case, a quick way to start the ActiveSync is to remove the mobile device from its cradle and put it back in. This starts the Microsoft Windows Mobile Device Center. Note The mobile handheld device must be placed in its cradle before beginning the installation. Failure to do this can prevent some necessary files from being copied to the handheld device. Configuring a Retailer-Specific Mobile POS A user exit is incorporated into the SAP POS Mobile Point-of-Sale installation to allow the launching of a customized Retailer-Specific installation from within the SAP POS Mobile Point-of-Sale installation session. The configuration file RSIMBL.INI is used to configure a command line Retailer-Specific Mobile POS installation application. If the RSIMBL.INI configuration file is present in the SAP POS Mobile Point-of-Sale installation directory msiinstall\mobile Point of Sale\ Retailer Specific Installers a new type of Mobile POS application (Other) is enabled on the Hand Held Device screen to allow you to install a Retailer-Specific Mobile POS application. If the Other option is selected, then during the installation session of the SAP POS Mobile 2016 SAP SE or an SAP affiliate company. All rights reserved. 27

28 Point-of-Sale, the command line executable and associated command line arguments for the Retailer-Specific Mobile POS installation are extracted from the RSIMBL.INI configuration file and used to launch the Retailer- Specific Mobile POS installation application. RSIMBL.INI Section Key Key Mandatory DEVICE INSTALL Name of Retailer-Specific installation application including the location of where the installation application resides. YES INSTALL_ARGUMENTS UNINSTALL UNINSTALL_ARGUMENTS List of Retailer-Specific installation application arguments (if required). Name of Retailer-Specific uninstallation application including the location of where the installation application resides. The list of installation application parameters (if any) are to be separated from the program name by a single space. List of Retailer-Specific uninstallation application arguments (if required). NO NO NO DIALOG FINISH Description of the InstallShield Wizard Completed! dialog to be displayed in the top portion of the dialog just below the title. NO If a Retailer-Specific Mobile POS uninstallation application is configured in the RSIMBL.INI configuration file, the command line executable and associated command line arguments are updated in the SAP POS Mobile Point-of- Sale registry. At the time the SAP POS Mobile Point-of-Sale application is uninstalled, the Retailer-Specific Mobile POS uninstallation application is launched during the uninstallation session. Note The creation, configuration, and maintenance of the RSIMBL.INI configuration file to install a customized Retailer-Specific installation is the responsibility of the customer. By default, the RSIMBL.INI configuration file is not present in the SAP POS Mobile Point-of-Sale installation directory. This is to ensure that the new Other option on the Hand Held Device screen is disabled so that users are prevented from choosing to install a Retailer-Specific application unless it is configured in a RSIMBL.INI configuration file. Customers are responsible for developing, maintaining, and testing their own customized Retailer-Specific installation applications. Installing the Mobile POS Client Software 1. On the Welcome screen for Mobile POS Client installation, select Next. 2. On the Destination Folder screen, to install to the folder displayed select Next. To install to another folder, select Change. In the Change Current Destination Folder dialog box, navigate to the appropriate folder and select OK. 3. On the Hand Held Device screen, enter values for Store Number and Terminal Number. The first terminal number you enter must be 51. You can increment the terminal number by one for each additional POS register that you want to configure as a Mobile POS Client up to number SAP SE or an SAP affiliate company. All rights reserved.

29 4. Choose one, or both, of the following: o The Xpress POS Thin Server option requires that you enter the unique IP address assigned to the printer that you want to connect to the Mobile POS device. The Unique IP address is the IP address of the printer with which the POS Thin Server communicates over the WAN o The Xpress Server option requires that you choose the appropriate handheld device from the provided list. Enter a socket number and an IP address for the handheld device. The value required in the Socket field is the one that the POS Thin Server listens to for requests from the handheld device. Listening port numbers must start at 4000 for terminal number 51 and increment by one for each additional POS register configured as a Mobile POS Client. Enter the unique IP Address assigned to the machine where the POS Thin Server resides. This IP Address is used by the Mobile POS device to communicate with the POS Thin Server over the WAN. Finally, make sure to specify the type of Mobile POS device to install. There are four types of devices available to choose from: 1. MC MC MC MC9090. The Other option to install a customized Retailer-Specific Mobile POS application is only enabled if a RSIMBL.INI configuration file is present in the SAP POS Mobile Point-of-Sale installation directory. Note The option to install MC75 and MC3190 is available on MS Windows 7 or higher. These options are not visible in lower (older) versions of Windows. The socket number is directly linked to the terminal ID number. The second terminal ID must, therefore, be 52 and it must be linked to socket number 4001, the next one must be 53 and it must be linked to socket number 4002, and so on. Selecting the Xpress Server option results in the installation injecting on to the mobile device all of the application files associated with the specified type. The settings entered in the Xpress Server are updated in the m_pos.ini file that is also injected on to the mobile device. There is a sample configuration file named m_pos_sample.ini that is installed at the installation location for reference. 5. Verify your settings and then select Next. 6. On the Ready to Install screen, verify that the handheld device is in its cradle. This ensures that all required files can be transferred successfully to the device during the installation process. 7. To begin the Mobile POS Client installation, select Install. Note The following steps are only required if upgrading a mobile POS device that is already installed with the SAP POS 2.3 Mobile POS software. o The installation informs you that the SAP <specified device> is already installed. Do you want to proceed with the re-install\upgrade? Respond Yes to inject the application software package on the Mobile POS device o After the application software package has been injected on the device, an additional prompt is displayed by the installation to allow you to follow any additional steps (if any) being displayed on the device. Complete all steps presented on the device and then click OK to complete the installation of the Mobile POS device SAP SE or an SAP affiliate company. All rights reserved. 29

30 8. At the end of the SAP POS Mobile Point-of-Sale installation, if you select Other as the type of Mobile POS device to install, selecting Finish in the InstallShield Wizard Completed! dialog box completes the current installation session and launches the installation of the configured Retailer-Specific installation application. After the Mobile POS Client installation process is completed, you must perform additional configuration tasks on the host machine to support this installation, as described in the following section. Configuring the Host Machine 1. On the host machine, create a shortcut for Mobile POS Client: o In the <PROGRAM_FILES>\SAP\Retail Systems folder, create a folder called MPOS51. o In the <PROGRAM_FILES>\SAP\Retail Systems\Point of Sale folder, locate posw.exe. Highlight this file and create a shortcut for it. o Make a copy of this file and place it in the <PROGRAM_FILES>\SAP\Retail Systems\MPOS51 folder. 2. Modify the properties file of this shortcut as follows: o Edit Target to show C:\<PROGRAM_FILES>\SAP\Retail Systems\Point of Sale\POSW.exe 1=c:\<PROGRAM_FILES>\SAP\Retail Systems\mpos51\parm\layout.ui0 o Edit Start In the path to show C:\<PROGRAM_FILES>\SAP\Retail Systems\mpos Place a copy of the same shortcut on the desktop and rename the shortcut to Mobile POS. 4. In the <PROGRAM_FILES>\SAP\Retail Systems\MPOS51 folder, create a folder called temp. 5. Update the m_pos.ini file with a parameter to handle the credit card management DLL file. This file is located in the C:\<PROGRAM_FILES>\SAP\Retail Systems\Mobile Point of Sale folder. To do this, in the m_pos.ini file, add the following line: MsrDLLName=Msr3000MCx.dll. Note The requirement for this *.DLL along with its name may vary depending on the requirements of any peripheral or service-supporting software in use at the retail location. For example, the MC75 and MC3190 devices do not use the MsrDLLName setting because all of the logic to support the MSR and the Scanner is contained within the specified Hardware DLL. For the MC3090 device, the setting MsrDLLName is used and should be set with the value of Msr3000MCx.dll. For the MC9090 device, the setting MsrDLLName is used and should be set with the value of Msr3000.dll.Copy m_pos.ini from C:\<PROGRAM_FILES>\SAP\Retail Systems\Mobile Point of Sale\<Specified type of Mobile POS device> to the Mobile POS repository folder created for the device type (for example, MC3090). There is a sample configuration file named m_pos_sample.ini that is installed at the installation location for reference. 6. By default, the Mobile POS Server will run a window for each mobile client that is configured. It is also possible to run the Mobile POS Server as a Windows OS service. This can be done as follows: o Copy the POSW.EXE from C:\<PROGRAM_FILES>\SAP\Retail Systems\Point of Sale to a designated directory. For example, from C:\<PROGRAM_FILES>\SAP\Retail Systems\mpos51 o Rename the POSW.EXE in the destination folder to a distinct filename such as MPOS R<xx> S<ss>.EXE, where <xx> and <ss> denote the register and store number respectively. Having unique names helps to identify an individual Mobile POS Client in Task Manager for performance tracking o Add the service instance for the specific Mobile POS service by running the following command from the command prompt: MPOS_R51_S01.EXE /I SAP SE or an SAP affiliate company. All rights reserved.

31 The Mobile POS services are configured so that the service runs under the Local System account. Set the Startup type: to be Automatic on the General tab of the selected service (Control Panel System and Security Administrative Tools) and enable the Allow service to interact with the desktop checkbox on the Log On tab. Additional services parameters are stored under the Parameters registry key associated with the services instance. These will include layout options for the GUI. The POS application supports a number of layouts such as /L2. As the service is started via SVCHOST, you must assign a working directory in the service options. The working directory is stored under the Parameters folder of the service registry entry. When the service is started, it will invoke the Windows API function SetCurrentDirectory ( ) that forces the service to start in a specific folder. Note For more information about how to configure the peripheral devices that support the Mobile POS Client component, see 5.6 Configuring Mobile POS Devices. Note If installing software on the MC75 or MC3190 Mobile POS device, the Motorola DataWedge Version or better must be installed on the Mobile POS device. This datawedge provides support for both the MSR and the Scanner by allowing data received from the MSR and Scanner to be processed by the Mobile POS application as data received through the keyboard buffer. For the Mobile POS application to distinguish MSR data/scanner data received through the keyboard buffer, the Motorola Datawedge must be configured to prefix and postfix the data received from the MSR and the Scanner. Make sure to: o Prefix MSR and Scanner data with different character sets to be able to distinguish data received from each peripheral o Postfix the MSR and Scanner data with the En ter key (ASCII 13) so that the Mobile POS application can consume the data received from the keyboard buffer. The following entries found under the [MAIN] section in the m_pos.ini file allow the Mobile POS application to be configured with prefix/postfix character sets for both the MSR and Scanner that match the prefix/postfix character set configured for the MSR and Scanner through the datawedge: m_pos.ini Entry Definition Characters Maximum Characters Per Set SCNPrefix Define a prefix character set for Scanner Any combination of visible and nonvisible ASCII characters between 0 and 255. For non-visible characters (for example, characters that cannot be typed through the keyboard) use ASCII Code value separated by a ; ASCII (59) 25 SCNPostfix Define a postfix character set for Scanner Any combination of visible and nonvisible ASCII characters between 0 and 255. For non-visible characters (for example, characters that cannot be typed through the keyboard) use ASCII Code value separated by a ; ASCII (59) SAP SE or an SAP affiliate company. All rights reserved. 31

32 m_pos.ini Entry Definition Characters Maximum Characters Per Set SCNPfxFilter Define unwanted characters included in the Scanner prefix/postfix character set received from datawedge that are to be filtered before prefix/postfix character set is processed by the Mobile POS application Any combination of visible and nonvisible ASCII characters between 0 and 255. For non-visible characters (for example, characters that cannot be typed through the keyboard) use ASCII Code value separated by a ; ASCII (59) 25 SCNDtaFilter Define unwanted characters included in the Scanner data received from the datawedge that are to be filtered before the data is processed by the Mobile POS application Any combination of visible and nonvisible ASCII characters between 0 and 255. For non-visible characters (for example, characters that cannot be typed through the keyboard) use ASCII Code value separated by a ; ASCII (59) 25 MSRPrefix Define a prefix character set for MSR Any combination of visible and nonvisible ASCII characters between 0 and 255. For non-visible characters (for example, characters that cannot be typed through the keyboard) use ASCII Code value separated by a ; ASCII (59) 25 MSRPostfix Define a postfix character set for MSR Any combination of visible and nonvisible ASCII characters between 0 and 255. For non-visible characters (for example, characters that cannot be typed through the keyboard) use ASCII Code value separated by a ; ASCII (59) 25 MSRPfxFilter Define unwanted characters included in the MSR prefix/postfix character set received from datawedge that are to be filtered before prefix/postfix character set is processed by the Mobile POS application Any combination of visible and nonvisible ASCII characters between 0 and 255. For non-visible characters (for example, characters that cannot be typed through the keyboard) use ASCII Code value separated by a ; ASCII (59) 25 MSRDtaFilter Define unwanted characters included in the MSR data received from datawedge that are to be filtered before the data is processed by the Mobile POS application Any combination of visible and nonvisible ASCII characters between 0 and 255. For non-visible characters (for example, characters that cannot be typed through the keyboard) use ASCII Code value separated by a ; ASCII (59) SAP SE or an SAP affiliate company. All rights reserved.

33 The following is a sample setting for the MSR and Scanner prefix/postfix and filters: SCNPrefix = 01 # <CTRL-A> (non visible character) SCNPostfix = 13 # <CR> (non visible character) SCNPfxFilter=16 # <SHIFT> (non visible character) SCNDtaFilter=16 # <SHIFT> (non visible character) MSRPrefix = M;83;R # 77;83;82 or MSR (visible characters) MSRPostfix = 13 <CR> (non visible character) MSRPfxFilter=16 # <SHIFT> (non-visible character) MSRDtaFilter=16 # <SHIFT> (non-visible character) Validation is performed on the character sets comprising prefixes, postfixes and filters to ensure they have been defined correctly. Strings comprised entirely of visible characters (do not contain digits between 0 9) are valid. Strings comprised of visible characters and non-visible characters must be separated by a ; semi-colon. In the event that digits 0 9 are needed for the mask, use ASCII Code values In the event that the ; character is needed for the mask, use ASCII Code value 59. If validation of a prefix or postfix fails for a specific device, data for this device will not be processed by the Mobile POS application. 4.9 Installing Store Configurator Use The Store Configurator is a required component and relevant for only the head office installation. Prerequisites The appropriate database must be installed. If you use encryption (security key), make sure that you have placed the keyfile.txt in a known folder and have the password. Both are required for this installation step. Note The Store Configurator component requires the Windows operating system date format set to MM/DD/YYYY; the display resolution must be 1280 x 1024 or higher. Procedure 1. On the Welcome screen for the Store Configurator installation, choose Next. 2. On the Destination Folder screen, do the following: o Specify the store language o Indicate that you are installing or using a security key container o Identify the folder where the POS Client is to be installed SAP SE or an SAP affiliate company. All rights reserved. 33

34 3. In the Please Select Your Store Language dialog box, choose the appropriate language. 4. To install a new security key container or if you are using an existing security key container, ensure that the Security Key Container checkbox is selected. Note Access rights for working with the security key container (for example, deleting, importing, or exporting it) are limited to the user who initially created this file. This is a security feature that prevents other users from manipulating the file after it has been installed. When installing the security key container, you must log on to the machine using the same logon ID and password used by the person who initially created the security key file. (This user requires administrator rights.) Failure to do this results in an error. 5. To install to the folder displayed, select Next. To install to another folder, choose Change. In the Change Current Destination Folder dialog box, navigate to the appropriate folder and select OK. Choose the database version if you are using a 32-bit operating system and click Next 6. On the Install Security Key Container screen, in the Select Location of the Keyfile.txt field, enter the location of the keyfile.txt. If installing a new key, enter the security container password. If the security key already exists, specify the folder location where the keyfile.txt resides, key file password and the security container password. Select Next. Note Passwords are case-sensitive. 7. To begin the Store Configurator installation, on the Ready to Install screen select Install. Result After the Store Configurator is installed, you must restart the server. For more information, see Performing Follow-On Activities After SAP POS. Note As of SAP POS 2.3 SP06, to provide a more secure password, a Security Key Container is required to support the hashing of a Store Configurator application user s password. If a Security Key Container already exists on the machine where the Store Configurator is to reside, it will be utilized by the Store Configurator application. However, if a Security Key Container does not exist, a Security Key Container is required to either be a) installed with a brand new Configurator application or b) manually created on the machine where an existing Store Configurator application resides. Refer to the SAP Point-of-Sale 2.3 Security Guide for instructions on how to manually create a Security Key Container. If creating a new Security Key Container, make sure to also set up the Security Key Container to support the Xpress Server, Store Manager and Journal Viewer if these applications reside on the same machine where the Configurator application is being installed. The Store Configurator installation will create a Security Key Container with a default key if the option to install a Security Key Container is selected. A security key does not need to be added to the Security Key Container; the presence of the Security Key Container is all that is required to support the hashing feature for the Store Configurator application. If the Security Key Container has not been created when attempting to logon to the Store Configurator application, the following error message is displayed Login failed, a Security Container has not been created preventing the user from logging on to the application SAP SE or an SAP affiliate company. All rights reserved.

35 Versions of the Security Key Container older than 2.0 must be upgraded to match the version of the Store Configurator being installed. A new Password Initialization Utility command line executable (CFGPwIni.exe) has been developed for the Store Configurator to initialize (hash) all application user passwords in a corresponding Configurator database. The utility searches through all of the Configurator databases listed in the UserDatabase table of the USERDB.DB database and then lists these Configurator databases, indicating whether all application user passwords in the database are initialized (hashed). Any, or all, of the Configurator databases can be selected for password initialization. This utility is required to run after the upgrade of the Store Configurator application. If the passwords for a selected Configurator database have not been initialized (hashed), when attempting to logon to the Store Configurator application, the following error message is displayed Login failed, the password for this user has not been initialized preventing the user from logging on to the application. The new Password Security feature in the Store Configurator application cannot be disabled. Therefore, if these two requirements are not met, a user will not be able to a) logon to the Store Configurator, b) create new Configurator databases, and c) delete existing Configurator databases after an upgrade Installing Software Development Kit Use The SDK is optional and relevant only for the head office installation. Prerequisites You must know the IP address for your database server. Procedure 1. On the Welcome screen for SDK installation, select Next. 2. On the Destination Folder screen, in the Database Server IP dialog box enter the IP address for the database server. 3. To install to the folder displayed, select Next. To install to another folder, select Change. On the Change Current Destination Folder screen, navigate to the appropriate folder and select OK. 4. On the Ready to Install screen, to begin the SDK installation select Install SAP SE or an SAP affiliate company. All rights reserved. 35

36 4.11 Installing AppSight Service Black Box Use Available as of SAP POS 2.2, AppSight Service Black Box is an optional component and relevant for both the head office and store installation. It is an additional component used for technical support purposes. Procedure 1. Navigate to the installation root folder or the msiinstall directory and locate the subfolder AppSight. 2. Run InstallAppSight.bat. This launches the standard AppSight Service Black Box installer; an additional configuration is made. 3. Continue the AppSight installation with the default settings. Deselect HTTP during installation, ensure that DCOM is checked, and ensure that the server name is blank. 4. To complete the main installation, choose Finish. If the application prompts you to continue with the installation, leaving the server name empty, choose Yes. 5. To close the batch file window, choose any key. Note For more information about how to use AppSight Service Black Box and obtain technical support, see the SAP POS Application Operations Guide Installing Diagnostic Agents Use The SAP Solution Manager Diagnostics (SMD) Agent and SAP Host Agent are used as part of the end-to-end root cause analysis and monitoring solution. The SAP SMD agent, also called a diagnostics agent, is the remote component of the end-to-end root cause analysis. It allows a connection between SAP Solution Manager, the managing application, and SAP POS, the managed application. Information is gathered from SAP POS and reported to SAP Solution Manager. For more information about root cause analysis, see the various documents available on the End-to-End Root Cause Analysis page on the SAP Service Marketplace at (logon may be required). SAP Notes Review the following notes before planning the installation of the Diagnostics Agents in your systems SAP SE or an SAP affiliate company. All rights reserved.

37 SAP Note Title of Diagnostics Agents Diagnostics Agent installation with SWPM Installing SAP SMD Agents For the installation of the SAP SMD Agents SAP recommends to use the latest support pack of the SL Toolset 1.0 (SAP Software Logistics Toolset). You can find the relevant information and guides under The Diagnostic Agent installation is covered in the System Provisioning area Performing Follow-On Activities After SAP POS You must perform the following activities after the installation of SAP POS components is completed. This lets you test whether the installation was successful. After Xpress Server, Xpress Server Database, and Store Configurator are installed, you must reboot the PCs and place all the parameter files exported by the Store Configurator in the following directory: C:\<PROGRAM_FILES>\SAP\Retail Systems\Xpress Server\Parm. This is required for a new installation, a reinstallation, or an upgrade on Xpress Server For the POS Client component, you must run Manager Code 6 (Define Terminal) to define aspects of the register (register number of Xpress Server and so on). For information about starting and stopping the Store Configurator and Store Manager, see Customer Relationship Mgmt SAP Point-of-Sale select the appropriate release of SAP POS Automated Installer Use The Automated Installer allows you to predefine the responses required to install the POS applications, databases and/or Retailer-Specific applications so that the automated installation process requires little interaction with the personnel running the installation at the store. Note The Automated Installer does not install head office applications such as the Store Configurator, the Software Development Tool Kit, AppSight Service Black Box or the Diagnostic Agents. Responses and configuration values required by each POS application installation are predefined in three types of INI files (AUTOINST.INI, <store number>.ini, and <language>.ini) which are used to: 2016 SAP SE or an SAP affiliate company. All rights reserved. 37

38 Define the Title, Labels, Button Text and Message Text that display in the GUI Define the type of installation: Register or Xpress Server Define which applications are to be installed per store Define responses/configurations used to install each application/database per store Configuring Automated Installer Note On a 64-bit operating system copy the installation files from X64 folders. Example If you are installing Xpress Server, copy the files from the Xpress ServerX64 folder to the SAP POS Installers\XPS folder. Follow the same process by copying files from relevant X64 folders for the files being copied to the following folders under the SAP POS Installers folder: XPS, XPD, SMG, EJV, EJD, DBT, and DBT\SQLScript. Procedure 1. In the directory where the Automated Installer resides, create all the sub-directories listed in the table below. This serves as the staging area for the installation, configuration, and application files needed to install the applications and/or databases at a specified store: Automated Installer Directory Automated Installer Directory Automated Installer Directory Sub- Directory Retailer-Specific Installers SAP POS Installers File Name AUTOINST.INI FRENCH.INI SPANISH.INI GERMAN.INI ITALIAN.INI POSTINST.BAT **name of installation application is extracted from [RETAILER SPECIFIC INSTALLER] section of the application INI file depending on whether Automated Installer is configured to install on a Register or Xpress Server. VERSION.INI SAP SE or an SAP affiliate company. All rights reserved.

39 Automated Installer Directory Automated Installer Directory Sub- Directory SAP POS Installers\POS SAP POS Installers\XPS SAP POS Installers\XPD SAP POS Installers\SMG SAP POS Installers\EJV SAP POS Installers\EJD SAP POS Installers\DBT File Name **file is specific to the installation from the installation directory. Point of Sale.msi setup.exe Setup.ini 0x0409.ini Xpress Server.msi setup.exe Setup.ini 0x0409.ini Xpress Server Database.msi setup.exe Setup.ini 0x0409.ini Store Manager.msi setup.exe Setup.ini 0x0409.ini Electronic Journal Viewer.msi setup.exe Setup.ini 0x0409.ini Electronic Journal Database.msi setup.exe Setup.ini 0x0409.ini Database Tools.msi setup.exe Setup.ini 0x0409.ini 2016 SAP SE or an SAP affiliate company. All rights reserved. 39

40 Automated Installer Directory Automated Installer Directory Sub- Directory SAP POS Installers\DBT\SQLScript Store INI Files Store Parameter Files\<store number>\pos\parm ** <store number> is the eight-digit store number Store Parameter Files\<store number>\xps\parm ** <store number> is the eight-digit store number Transnet Installer Transnet Installer\jcserv Transnet Installer\jcserv\win32 Transnet Installer\jtmt Transnet Installer\nfmctemp File Name tmx_db_<software version>.cab ** Actual name of Database Tools Upgrade file is specific to the version of the SAP POS installation. ** Sub-directory containing store specific INI files (<store number>.ini) ** Customer-specific POS Client parameter files ** Customer-specific Xpress Server parameter files The SAP Store Data Transfer for Retail application has a folder named Include. Copy the file named tn_aa.zip from this folder to the Automated Installer directory. Extract the tn_aa.zip file preserving the folder structure. When you extract it while preserving the folder structure, a folder named Transnet Installer is created under the Automated Installer folder. Delete the file tn_aa.zip after extracting these files. Replace the file transnet.xml with a customer-specific configuration. cserv.zip jcserv.zip NTMJavaClient.jar _INST32I.EX ISDEL.EXE _SETUP.DLL _sys1.cab _user1.cab data1.cab DATA.TAG SAP SE or an SAP affiliate company. All rights reserved.

41 Automated Installer Directory Automated Installer Directory Sub- Directory Transnet Installer\Transnet Transnet Installer\bin Transnet Installer\lib File Name lang.dat layout.bin os.dat readme.txt setup.bmp SETUP.EXE SETUP.INI setup.ins setup.iss setup.lid TPSServer.dll tnrun.bat tnsetpwd.bat Transnet.exe twactivate.bat twaddkey.bat twaddproperty.bat twchgproperty.bat twcmd.bat twcreatecontainer.bat twdelkey.bat twdelproperty.bat twexportkeys.bat twimportkeys.bat twlistkeys.bat twmark4del.bat UpgradePaymentDetail.bat UpgradeTNUser.bat a1to1.jar jdom.jar log4j.jar 2016 SAP SE or an SAP affiliate company. All rights reserved. 41

42 Automated Installer Directory Automated Installer Directory Sub- Directory Transnet Installer\config File Name logging.jar tncore.jar tnextension.jar tw-security.jar xerces.jar FinancialHandler.xml logging.properties Merchant.xml ModemProfiles.xml TLOGHandler.xml transnet.xml. Replace this file with a customer-specific configuration file. transnetjms.xsl transnetsample.xml transnettpsclient.xsl transnettpsserver.xsl transnettransientclient.xsl transnetxmlsocketserver.xsl 2. Copy the files listed above from the msiinstall directory of the TWGM installation and the extracted tn_aa.zip file from SAP Store Data Transfer for Retail installation to your staging area. 3. Open AUTOINST.INI with Notepad or any other text editor. Note This is the application INI file and is used to maintain: o The default set of English translatable text (Title, Labels, Button Text, and Message Text) that will be displayed by the Automated Installer o The applications/databases to install o The type of machine to be installed: Register or Xpress Server. (The type of machine determines which data entry fields will be available in the GUI for the user to interact with). 4. Create and configure the keys in AUTOINST.INI using the table below as well as section , Sample AUTOINST.INI and <store number>.ini Files as a guide SAP SE or an SAP affiliate company. All rights reserved.

43 AUTOINST.INI Section Key Description [APPLICATION GUI] TYPE LANGUAGE WORKINGDIRECTORY LOGLEVEL BATCHLAUNCHDELAY Configures the GUI for type of installation: Register or Xpress Server Language to display literals, text, and messages. **Only supports languages currently supported by SAP POS 10.3 (English, French, Spanish, German and Italian). Unless configured for another language, English is the default language displayed in the GUI. Location of working directory for the Automated Installer application. **The Automated Installer application creates this folder if it does not exist and copies all required files from the directory, where the GUI resides, to the location of the Automated Installer application installation directory before installing an application/database. IMPORTANT: The Working Directory and the directory where the GUI application resides cannot be the same directory. Level of logging captured in AUTOINST.LOG log file. 0 = lowest 1 = highest. Unless configured, default logging is set to the lowest level. Number of seconds to delay before launching post installation batch file. The default is 15 seconds. [ENGLISH TRANSLATIONS] 1 Unable to open file: %s Default English Error / Warning 2 Unable to close file: %s Message Literal unless a language other than English is specified. 3 Unable to read from file: %s 4 Unable to write to file: %s 6 Unable to copy file: %s 9 Unable to truncate file: %s **To be used for translation into French, Spanish, German and Italian. See the section on the Translation INI file SAP SE or an SAP affiliate company. All rights reserved. 43

44 Section Key Description 11 Unable to initialize file search 12 Unable to continue file search 16 Unable to start program launch listener thread 17 Unable to stop program launch listener thread 18 Unable to launch program: %s 19 Invalid program return code: (%d) %s 20 Unable to instantiate application window 21 Unable to start install process listener thread 22 Unable to stop install process listener thread 23 Unable to create the application working directory: %s 24 Application working directory cannot be defined as the application directory: %s 25 Mandatory setting(s) not defined in the application INI file: %s 26 Application working directory is not defined in the application INI file: %s 27 Invalid type of installation defined in the application INI file: %s 28 Unable to locate build version in %s 29 Unable to locate application INI file: %s 30 Unable to open the application log file: %s SAP SE or an SAP affiliate company. All rights reserved.

45 Section Key Description 31 Applications / databases have not been configured for installation 32 Unable to locate the store specific INI file; %s 33 Mandatory field in GUI is required: %s 34 Invalid value entered in GUI, %s must be between %d and %d 35 Mandatory setting(s) not defined in the store specific INI file: %s 36 Unable to locate Language INI file: %s 37 Unable to initialize directory search 38 Unable to continue directory search 39 Unable to create directory: %s 40 Unable to copy directory: %s 42 Unable to delete registry value: %s - %s 43 Unable to update registry value %s - %s 44 Unable to create registry key: %s 45 Unable to retrieve registry value %s - %s 46 Unable to determine the application/database installation path 47 Unable to locate Post batch log file: %s 48 Unable to open service manager 49 Unable to close service manager 2016 SAP SE or an SAP affiliate company. All rights reserved. 45

46 Section Key Description 50 Unable to create service: %s 51 Unable to delete service: %s 52 Unable to open service: %s 53 Unable to close service %s 54 Unable to stop service: %s 55 Unable to query service: %s 56 Unable to control service: %s 57 Unable to retrieve XML file: %s 58 Unable to update XML file: %s 59 Unable to access XML root node: %s 60 Unable to get XML node list: %s 61 Unable to get XML node item: %s 63 session has been completed successfully 64 session has generated an error 65 session has been cancelled 66 Mandatory file(s) not found in the application Staging Area directory 67 Unable to validate application Staging Area directory 68 Unable to locate Post batch log file: %s [ENGLISH TRANSLATIONS] INFORMATION Information Default English Literals that are WARNING Warning displayed in the GUI unless a language other than English is specified. ERROR Error **To be used for translation into French, Spanish, German and Italian. STORENUMBER STORE NUMBER REGISTERNUMBER REGISTER NUMBER SAP SE or an SAP affiliate company. All rights reserved.

47 Section Key Description REGISTERTYPE PARMGROUP PRIMARYSERVERIP ADDRESS BACKUPSERVERIPA DDRESS SCANNER BANAMEXPORT INSTALLER SAPPOSCUSTOMIZA TION SCREENREGISTER SCREENSERVER XPRESSSERVER PRIMARY BACKUP CANCEL OK STATUS INSTALLING OF INSTALLATIONS REGISTER TYPE PARAMETER GROUP PRIMARY SERVER IP ADDRESS PRIMARY SERVER IP ADDRESS SCANNER PRESENT (Y or N) BANAMEX SERVER PORT INSTALLER SAP POS CUSTOMIZATION SCREEN: REGISTER SCREEN: SERVER XPRESS SERVER PRIMARY BACKUP CANCEL OK STATUS: Installing OF INSTALLATIONS [REGISTER APPLICATIONS] POS XPS XPD SMG (Y=Yes / N=No) install POS Client application on the register (Y=Yes / N=No) install Xpress Server application on the register (Y=Yes / N=No) install Xpress Server Database on the register (Y=Yes / N=No) install Store Manager application on the register 2016 SAP SE or an SAP affiliate company. All rights reserved. 47

48 Section Key Description [PRIMARY SERVER APPLICATIONS] EJV EJD XPS XPD SMG EJV EJD DBT TNT RSI POS POS XPS XPD SMG EJV EJD (Y=Yes / N=No) install Electronic Journal Viewer application on the register (Y=Yes / N=No) install Electronic Journal Viewer database on the register (Y=Yes / N=No) install Xpress Server application on the register (Y=Yes / N=No) install Xpress Server Database on the register (Y=Yes / N=No) install Store Manager application on the register (Y=Yes / N=No) install Electronic Journal Viewer application on the register (Y=Yes / N=No) install Electronic Journal Viewer database on the register (Y=Yes / N=No) install Database Tools application on the register (Y=Yes / N=No) install Transnet Client application on the register (Y=Yes / N=No) install Retailer-Specific on the register (Y=Yes / N=No) install POS Client application on the Xpress Server (Y=Yes / N=No) install POS Client application on the Xpress Server (Y=Yes / N=No) install Xpress Server application on the Xpress Server (Y=Yes / N=No) install Xpress Server Database on the Xpress Server (Y=Yes / N=No) install Store Manager application on the Xpress Server (Y=Yes / N=No) install Electronic Journal Viewer application on the Xpress Server (Y=Yes / N=No) install Electronic Journal Viewer database on the Xpress Server SAP SE or an SAP affiliate company. All rights reserved.

49 Section Key Description [BACKUP SERVER APPLICATIONS] DBT TNT RSI POS XPS XPD SMG EJV EJD DBT TNT RSI (Y=Yes / N=No) install Database Tools application on the Xpress Server (Y=Yes / N=No) install Transnet Client application on the Xpress Server (Y=Yes / N=No) install Retailer-Specific on the Xpress Server (Y=Yes / N=No) install POS Client application on the backup Xpress Server (Y=Yes / N=No) install Xpress Server application on the backup Xpress Server (Y=Yes / N=No) install Xpress Server Database on the backup Xpress Server (Y=Yes / N=No) install Store Manager application on the backup Xpress Server (Y=Yes / N=No) install Electronic Journal Viewer application on the backup Xpress Server (Y=Yes / N=No) install Electronic Journal Viewer database on the backup Xpress Server (Y=Yes / N=No) install Database Tools application on the backup Xpress Server (Y=Yes / N=No) install Transnet Client application on the backup Xpress Server (Y=Yes / N=No) install Retailer-Specific on the backup Xpress Server The value of the LANGUAGE key in the [APPLICATION GUI] section of AUTOINST.INI denotes which <language>.ini file to use to translate the Automated Installer GUI text. Each <language>.ini file contains the set of default English literals/messages displayed through the Automated Installer GUI translated into the specified language. If translated text cannot be located in the <language>.ini file, the text is defaulted to English. Default English translations are extracted from the [ENGLISH TRANSLATION] section in the AUTOINST.INI file SAP SE or an SAP affiliate company. All rights reserved. 49

50 <LANGUAGE>.INI Section Key Description [<language> TRANSLATIONS ] 1 Unable to open file: %s Default English Error / Warning 2 Unable to close file: %s Message Literal translated into French, Spanish, German and Italian. 3 Unable to read from file: %s 4 Unable to write to file: %s 6 Unable to copy file: %s 9 Unable to truncate file: %s 11 Unable to initialize file search 12 Unable to continue file search 16 Unable to start program launch listener thread 17 Unable to stop program launch listener thread 18 Unable to launch program: %s 19 Invalid program return code: (%d) %s 20 Unable to instantiate application window 21 Unable to start install process listener thread 22 Unable to stop install process listener thread 23 Unable to create the application working directory: %s 24 Application working directory cannot be defined as the application directory: %s 25 Mandatory setting(s) not defined in the application INI file: %s 26 Application working directory is not defined in the application INI file: %s SAP SE or an SAP affiliate company. All rights reserved.

51 Section Key Description 27 Invalid type of installation defined in the application INI file: %s 28 Unable to locate build version in %s 29 Unable to locate application INI file: %s 30 Unable to open the application log file: %s 31 Applications / databases have not been configured for installation 32 Unable to locate the store specific INI file; %s 33 Mandatory field in GUI is required: %s 34 Invalid value entered in GUI, %s must be between %d and %d 35 Mandatory setting(s) not defined in the store specific INI file: %s 36 Unable to locate Language INI file: %s 37 Unable to initialize directory search 38 Unable to continue directory search 39 Unable to create directory: %s 40 Unable to copy directory: %s 42 Unable to delete registry value: %s - %s 43 Unable to update registry value %s - %s 44 Unable to create registry key: %s 45 Unable to retrieve registry value %s - %s 2016 SAP SE or an SAP affiliate company. All rights reserved. 51

52 Section Key Description 46 Unable to determine the application/database installation path 47 Unable to locate Post batch log file: %s 48 Unable to open service manager 49 Unable to close service manager 50 Unable to create service: %s 51 Unable to delete service: %s 52 Unable to open service: %s 53 Unable to close service %s 54 Unable to stop service: %s 55 Unable to query service: %s 56 Unable to control service: %s 57 Unable to retrieve XML file: %s 58 Unable to update XML file: %s 59 Unable to access XML root node: %s 60 Unable to get XML node list: %s 61 Unable to get XML node item: %s 63 session has been completed successfully 64 session has generated an error 65 session has been cancelled 66 Mandatory file(s) not found in the application Staging Area directory SAP SE or an SAP affiliate company. All rights reserved.

53 Section Key Description 67 Unable to validate application Staging Area directory 68 Unable to locate Post batch log file: %s INFORMATION Information Default English Literals that are WARNING Warning displayed in the GUI translated into French, Spanish, German and Italian. ERROR Error STORENUMBER REGISTERNUMBER REGISTERTYPE PARMGROUP PRIMARYSERVERIP ADDRESS BACKUPSERVERIPA DDRESS SCANNER BANAMEXPORT INSTALLER SAPPOSCUSTOMIZA TION SCREENREGISTER SCREENSERVER XPRESSSERVER PRIMARY BACKUP CANCEL OK STATUS INSTALLING OF STORE NUMBER REGISTER NUMBER REGISTER TYPE PARAMETER GROUP PRIMARY SERVER IP ADDRESS PRIMARY SERVER IP ADDRESS SCANNER PRESENT (Y or N) BANAMEX SERVER PORT INSTALLER SAP POS CUSTOMIZATION SCREEN: REGISTER SCREEN: SERVER XPRESS SERVER PRIMARY BACKUP CANCEL OK STATUS: Installing OF 2016 SAP SE or an SAP affiliate company. All rights reserved. 53

54 Section Key Description INSTALLATIONS INSTALLATIONS 5. Save AUTOINST.INI in the location specified in Step Close AUTOINST.INI. 7. Open INI, which is a sample <store number>.ini file with Notepad or any other text editor. Note The store-specific INI file is used to maintain the predefined responses and configurations for each application and database to be installed at a specified store. The store number is incorporated into the name of the store-specific INI file formatted as an 8-digit store number, right justified and zero filled. There is one store specific INI file for each store that will be installed with the SAP POS applications and/or databases. The Automated Installer determines the name of the store specific INI file from the store number entered by the user. 8. Create and configure the keys of INI using the table below as well as section , Sample AUTOINST.INI and <store number>.ini Files as a guide. <store number>.ini (Store-Specific INI File) Section Key Description [APPLICATION GUI] STORENUMBER Number of the store entered through the GUI. ** Value for this key is entered by the user through the GUI and the Automated Installer application will update this key. This is recognized for both the Register and Xpress Server installation. REGISTERNUMBER Number of store. ** Value for this key is entered by the user through the GUI and the Automated Installer application will update this key. This is only recognized for the Register installation. PRIMARYXPRESSSERVER (Y=Yes / N=No) Install applications on primary server. ** Value for this key is entered by the user through the GUI and the Automated Installer application will update this key. This is only recognized for the Xpress Server installation. BACKUPXPRESSSERVER (Y=Yes / N=No) Install applications on backup server. ** Value for this key is entered by the user through the GUI and the Automated Installer application will SAP SE or an SAP affiliate company. All rights reserved.

55 Section Key Description update this key. This is only recognized for the Xpress Server installation. REGISTERTYPE Type of register (1 9). ** Value for this key is entered by the user through the GUI and the Automated Installer application will update this key. This is only recognized for the Register installation. PARMGROUP Parameter group of register (1 9). ** Value for this key is entered by the user through the GUI and the Automated Installer application will update this key. This is only recognized for the Register installation. PRIMARYSERVERIPADDRESS IP Address of Primary Xpress Server. ** Value for this key is entered by the user through the GUI and the Automated Installer application will update this key. This is recognized for both the Register and Xpress Server installation. BACKUPSERVERIPADDRESS IP Address of Backup Xpress Server. ** Value for this key is entered by the user through the GUI and the Automated Installer application will update this key. This is recognized for both the Register and Xpress Server installation. [REGISTER DEFAULT] MC2_OPOS_PRINTER Name of peripheral configured POS Client for OPOS printer. MC2_OPOS_PRINTER_KNIFE (Y=Yes / N=No) Configure POS Client for OPOS printer knife. ** Is only recognized if the OPOS printer is configured. MC2_OPOS_PRINTER_CHEQUE_ FLIP 0=NONE 1=IBM TI4 2=EPSON TM-H6000 ** Is only recognized if OPOS printer configured. MC2_ OPOS_LINEDISPLAY Name of peripheral configured POS Client for the OPOS line display SAP SE or an SAP affiliate company. All rights reserved. 55

56 Section Key Description MC2_ OPOS_CASHDRAWER_1 MC2_ OPOS_CASHDRAWER_2 Name of peripheral configured POS Client for the OPOS cash drawer 1. Name of peripheral configured POS Client for the OPOS cash drawer 2. ** Is only recognized if OPOS cash drawer 1 is configured. MC2_ OPOS_MSR MC2_OPOS_SCANNER MC2_OPOS_SCANNER_EXPAND_ UPCE MC2_OPOS_MICR MC2- _OPOS_MICR_CHEQUE_FACE_U P MC2_OPOS_KEYLOCK MC2_OPOS_SCALE MC2_OPOS_KEYBOARD MC2_SIGNATURE_CAPTURE MC2_OPOS_CASHDRAWER_1_CA SHBOXES Name of peripheral configured POS Client for the OPOS MSR. Name of peripheral configured POS Client for the OPOS scanner. (Y=Yes / N=No) Configure POS Client for OPOS scanner expanded UPCE. Name of peripheral configured POS Client for the OPOS MICR. (Y=Yes / N=No) Configure POS Client for OPOS MICR check face up. ** Is only recognized if OPOS Printer Check Flip is configured. Name of peripheral configured POS Client for the OPOS key lock. Name of peripheral configured POS Client for the OPOS scale. Name of peripheral configured POS Client for the OPOS keyboard. Name of peripheral configured POS Client for signature capture device. Number of cash boxes configured for cash drawer 1 (1-4). ** Is only recognized if OPOS cash drawer 1 is configured. MC2_OPOS_CASHDRAWER_2_CA SHBOXES Number of cash boxes configured for cash drawer 2 (1-4). ** Is only recognized if OPOS cash drawer 1 is configured. MC6_REGISTER_TYPE Register Type (1 99) MC6_ REPORT_GROUP Register Report Group (1 10) MC6_PARM_GROUP Register Parm Group SAP SE or an SAP affiliate company. All rights reserved.

57 Section Key Description (1 10) MC6_STATE_PROVINCE MC6_LOCAL_PLU MC6_BACKUP_SERVER MC6_BACKUP_CREDIT_SERVER Register State/Province (Y=Yes / N=No) Maintain local PLU on register. (Y=Yes / N=No) Register uses backup server for PLU lookups. (Y=Yes / N=No) Register uses backup credit server for credit authorizations. ** Is only recognized if the register is configured to use a backup server. MC6_PRIMARY_SERVER_IP MC6_BACKUP_SERVER_IP Primary server IP address used by the register to connect to the primary Xpress Server Backup server IP address used by the register to connect to the backup Xpress Server. ** Is only recognized if the register is configured to use the backup server. [REGISTER <NUMBER>] MC2_OPOS_PRINTER Name of peripheral configured POS Client for the OPOS printer MC2_OPOS_PRINTER_KNIFE (Y=Yes / N=No) Configure POS Client for OPOS printer knife. ** Is only recognized if the OPOS printer configured. MC2_OPOS_PRINTER_CHEQUE_ FLIP 0=NONE 1=IBM TI4 2=EPSON TM-H6000. ** Is only recognized if the OPOS printer configured. MC2_ OPOS_LINEDISPLAY MC2_ OPOS_CASHDRAWER_1 MC2_ OPOS_CASHDRAWER_2 Name of peripheral configured POS Client for OPOS line display. Name of peripheral configured POS Client for OPOS cash drawer 1. Name of peripheral configured POS Client for OPOS cash drawer 2. ** Is only recognized if the OPOS cash drawer 1 configured. MC2_ OPOS_MSR Name of peripheral configured POS Client for OPOS MSR SAP SE or an SAP affiliate company. All rights reserved. 57

58 Section Key Description MC2_OPOS_SCANNER MC2_OPOS_SCANNER_EXPAND_ UPCE MC2_OPOS_MICR MC2- _OPOS_MICR_CHEQUE_FACE_U P MC2_OPOS_KEYLOCK MC2_OPOS_SCALE MC2_OPOS_KEYBOARD MC2_SIGNATURE_CAPTURE MC2_OPOS_CASHDRAWER_1_CA SHBOXES Name of peripheral configured POS Client for OPOS scanner (Y=Yes / N=No) Configure POS Client for OPOS scanner expanded UPCE. Name of peripheral configured POS Client for the OPOS MICR. (Y=Yes / N=No) Configure POS Client for OPOS MICR check face up. ** Is only recognized if OPOS Printer Check Flip is configured. Name of peripheral configured POS Client for OPOS key lock. Name of peripheral configured POS Client for the OPOS scale. Name of peripheral configured POS Client for the OPOS keyboard. Name of peripheral configured POS Client for signature capture device. Number of cash boxes configured for cash drawer 1 (1-4). ** Is only recognized if OPOS cash drawer 1 is configured. MC2_OPOS_CASHDRAWER_2_CA SHBOXES Number of cash boxes configured for cash drawer 2 (1-4). ** Is only recognized if OPOS cash drawer 1 is configured. MC6_REGISTER_TYPE Register Type (1 99) MC6_ REPORT_GROUP Register Report Group (1 10) MC6_PARM_GROUP Register Parm Group (1 10) MC6_STATE_PROVINCE MC6_LOCAL_PLU MC6_BACKUP_SERVER MC6_BACKUP_CREDIT_SERVER Register State/Province (Y=Yes / N=No) Maintain local PLU on register. (Y=Yes / N=No) Register uses backup server for PLU lookups. (Y=Yes / N=No) Register uses backup credit server for credit authorizations SAP SE or an SAP affiliate company. All rights reserved.

59 Section Key Description ** Is only recognized if the register is configured to use a backup server. MC6_PRIMARY_SERVER_IP MC6_BACKUP_SERVER_IP Primary server IP address used by the register to connect to the primary Xpress Server Backup server IP address used by the register to connect to the backup Xpress Server. ** Is only recognized if the register is configured to use the backup server. [REGISTER <NUMBER>] MC2_OPOS_PRINTER Name of peripheral configured POS Client for the OPOS printer MC2_OPOS_PRINTER_KNIFE (Y=Yes / N=No) Configure POS Client for OPOS printer knife. ** Is only recognized if the OPOS printer configured. MC2_OPOS_PRINTER_CHEQUE_ FLIP 0=NONE 1=IBM TI4 2=EPSON TM-H6000. ** Is only recognized if the OPOS printer configured. MC2_ OPOS_LINEDISPLAY MC2_ OPOS_CASHDRAWER_1 MC2_ OPOS_CASHDRAWER_2 Name of peripheral configured POS Client for OPOS line display. Name of peripheral configured POS Client for OPOS cash drawer 1. Name of peripheral configured POS Client for OPOS cash drawer 2. ** Is only recognized if the OPOS cash drawer 1 configured. MC2_ OPOS_MSR MC2_OPOS_SCANNER MC2_OPOS_SCANNER_EXPAND_ UPCE MC2_OPOS_MICR MC2- _OPOS_MICR_CHEQUE_FACE_U P Name of peripheral configured POS Client for OPOS MSR. Name of peripheral configured POS Client for OPOS scanner (Y=Yes / N=No) Configure POS Client for OPOS scanner expanded UPCE. Name of peripheral configured POS Client for the OPOS MICR. (Y=Yes / N=No) Configure POS Client for OPOS MICR check face up SAP SE or an SAP affiliate company. All rights reserved. 59

60 Section Key Description ** Is only recognized if OPOS Printer Check Flip is configured. MC2_OPOS_KEYLOCK MC2_OPOS_SCALE MC2_OPOS_KEYBOARD MC2_SIGNATURE_CAPTURE MC2_OPOS_CASHDRAWER_1_CA SHBOXES Name of peripheral configured POS Client for OPOS key lock. Name of peripheral configured POS Client for the OPOS scale. Name of peripheral configured POS Client for the OPOS keyboard. Name of peripheral configured POS Client for the signature capture device. Number of cash boxes configured for cash drawer 1 (1-4). ** Is only recognized if OPOS cash drawer 1 is configured. MC2_OPOS_CASHDRAWER_2_CA SHBOXES Number of cash boxes configured for cash drawer 2 (1-4). ** Is only recognized if OPOS cash drawer 1 is configured. MC6_REGISTER_TYPE Register Type (1 99). MC6_ REPORT_GROUP Register Report Group (1 10). MC6_PARM_GROUP Register Parm Group (1 10). MC6_STATE_PROVINCE MC6_LOCAL_PLU MC6_BACKUP_SERVER MC6_BACKUP_CREDIT_SERVER Register State/Province. (Y=Yes / N=No) Maintain local PLU on register. (Y=Yes / N=No) Register uses a backup server for PLU lookups. (Y=Yes / N=No) Register uses a backup credit server for credit authorizations. ** Is only recognized if register configured to use backup server. MC6_PRIMARY_SERVER_IP MC6_BACKUP_SERVER_IP Primary server IP address used by register to connect to primary Xpress Server. Backup server IP address used by the register to connect to a backup Xpress Server SAP SE or an SAP affiliate company. All rights reserved.

61 Section Key Description ** Is only recognized if register is configured to use a backup server. [PRIMARY XPRESS SERVER] PRIMARY_XPS_PLUCACHE PRIMARY_XPS_PARMPROC PRIMARY_XPS_EODPROC PRIMARY_XPS_NEWPARMINT PRIMARY_XPS_SHOWEODPROC PRIMARY_XPS_LOGFILE PRIMARY_XPS_SHOWDATE PRIMARY_XPS_LOGSIZE Size of PLU cache supported by Xpress Server ( ). Parameter File Update Batch file. Location and file name of End Of Day Batch file. Attempt to apply parameter files every (X) number of seconds ( ). (Y=Yes / N=No) Run End Of Day in foreground. Location and file name of the Xpress Server Log File. (Y=Yes / N=No) Capture date and time in the Xpress Server Log File. Maximum size (in Bytes) of the Xpress Server Log File ( ). [BACKUP XPRESS SERVER] BACKUP_XPS_PLUCACHE BACKUP_XPS_PARMPROC BACKUP_XPS_EODPROC BACKUP_XPS_NEWPARMINT BACKUP_XPS_SHOWEODPROC BACKUP_XPS_LOGFILE BACKUP_XPS_SHOWDATE BACKUP_XPS_LOGSIZE BACKUP_XPS_BKSRV Size of PLU cache supported by the Xpress Server ( ). Parameter File Update Batch file. Location and file name of End Of Day Batch file. Attempt to apply parameter files every (X) number of seconds ( ). (Y=Yes / N=No) Run End Of Day in the foreground. Location and file name of the Xpress Server Log File. (Y=Yes / N=No) Capture date and time in Xpress Server Log File. Maximum size (in Bytes) of the Xpress Server Log File ( ). Indicates that the server is a backup Xpress Server. ** Is only recognized for backup Xpress Server (Default to 1) SAP SE or an SAP affiliate company. All rights reserved. 61

62 Section Key Description BACKUP_XPS_SERVERNAME IP Address of primary Xpress Server. ** Is only recognized for backup Xpress Server. [POS UPGRADE] INSTALL_BROWSER (Y=Yes / N=No) POS Browser will be installed. INSTALL_DEMO_PARMS CREDIT INSTALL_DIRECTORY UTIL_DIRECTORY SERVER_IP (Y=Yes / N=No) Demonstration parameters will be installed. Type of credit to be installed (EF = EFT Service). directory for application files. directory for application utilities. IP Address of primary Xpress Server. ** Used for information only. BACKUP_SERVER_IP IP Address of backup Xpress Server. ** Used for information only. LANGUAGE Default application language. ** only supports the following language codes: ENG = English FRE = French SPA = Spanish GER = German ITA = Italian CISP_MODULE ** not defined by user: defaulted to: 0 CISP_KEYFILE CISP_MULTIKEY_PASSWORD CISP_SINGLEKEY_PASSWORD CISP_KEYFILE_PASSWORD ** not defined by user: defaulted to empty string ** not defined by user: defaulted to empty string ** not defined by user: defaulted to empty string ** not defined by user: defaulted to empty string [XPS UPGRADE] INSTALL_API (Y=Yes / N=No) Application Programming Interface is to be installed SAP SE or an SAP affiliate company. All rights reserved.

63 Section Key Description DB_TYPE Type of Database Management System. MS = Microsoft SQL Server S11 = SQL Anywhere 11 S12 = SQL Anywhere 12 S16 = SQL Anywhere 16 CREDIT DATABASE_APP_PATH DATABASE_SERVER INSTALL_DIRECTORY INSTALL_DEMO_PARMS UTIL_DIRECTORY DB_USER DB_PASS Type of credit to be installed (EF = EFT Service) Database Management System installation directory. Database Server Name. directory for application files. (Y=Yes / N=No) Demonstration parameters will be installed. directory for application utilities. User name of database account used by the Xpress Server application to access the database. Password of database account used by the Xpress Server application to access the database. ** Password must be encrypted using the default NON-PCI encryption algorithm. LANGUAGE Default application language. ** only supports the following language codes: ENG = English FRE = French SPA = Spanish GER = German ITA = Italian CISP_MODULE ** not defined by user: defaulted to: 0 CISP_KEYFILE CISP_MULTIKEY_PASSWORD ** not defined by user: defaulted to empty string ** not defined by user: defaulted to empty string 2016 SAP SE or an SAP affiliate company. All rights reserved. 63

64 Section Key Description CISP_SINGLEKEY_PASSWORD CISP_KEYFILE_PASSWORD ** not defined by user: defaulted to empty string ** not defined by user: defaulted to empty string [BACKUP XPS UPGRADE] INSTALL_API (Y=Yes / N=No) Application Programming Interface is to be installed. DB_TYPE Type of Database Management System. MS = Microsoft SQL Server S11 = SQL Anywhere 11 S12 = SQL Anywhere 12 S16 = SQL Anywhere 16 CREDIT DATABASE_APP_PATH DATABASE_SERVER INSTALL_DIRECTORY INSTALL_DEMO_PARMS UTIL_DIRECTORY DB_USER DB_PASS Type of credit to be installed (EF = EFT Service) Database Management System installation directory. Database Server Name. directory for application files. (Y=Yes / N=No) Demonstration parameters will be installed. directory for application utilities. User name of database account used by the Xpress Server application to access the database. Password of database account used by the Xpress Server application to access the database. ** Password must be encrypted using the default NON-PCI encryption algorithm. LANGUAGE Default application language. ** only supports the following language codes: ENG = English FRE = French SPA = Spanish SAP SE or an SAP affiliate company. All rights reserved.

65 Section Key Description GER = German ITA = Italian CISP_MODULE ** not defined by user: defaulted to: 0 CISP_KEYFILE CISP_MULTIKEY_PASSWORD CISP_SINGLEKEY_PASSWORD CISP_KEYFILE_PASSWORD ** not defined by user: defaulted to empty string ** not defined by user: defaulted to empty string ** not defined by user: defaulted to empty string ** not defined by user: defaulted to empty string [EJV UPGRADE] DB_TYPE Type of Database Management System MS = Microsoft SQL Server S11 = SQL Anywhere 11 S12 = SQL Anywhere 12 S16 = SQL Anywhere 16 INSTALL_DIRECTORY DATABASE_APP_PATH DATABASE_SERVER DB_USER DB_PASS directory for application files. Database Management System installation directory. Database Server Name. User name of database account used by the Journal Viewer application to access the database. Password of database account used by the Journal Viewer application to access the database. ** Password must be encrypted using the default NON-PCI encryption algorithm. XPRESS_SERVER_PATH LANGUAGE Location of the Xpress Server. Used by the Journal Viewer to define the location of the current day directory under the Xpress Server. Default application language. ** only supports the following language codes: ENG = English FRE = French 2016 SAP SE or an SAP affiliate company. All rights reserved. 65

66 Section Key Description SPA = Spanish GER = German ITA = Italian CISP_MODULE ** not defined by user defaulted to: 0 [STORE MANAGER UPGRADE] CISP_KEYFILE CISP_MULTIKEY_PASSWORD CISP_SINGLEKEY_PASSWORD CISP_KEYFILE_PASSWORD DB_TYPE SERVER_IP INSTALL_DIRECTORY DATABASE_APP_PATH DATABASE_SERVER XPRESS_SERVER_PATH DB_USER DB_PASS LANGUAGE ** not defined by user: defaulted to empty string ** not defined by user: defaulted to empty string ** not defined by user: defaulted to empty string ** not defined by user: defaulted to empty string Type of Database Management System: MS = Microsoft SQL Server S11 = SQL Anywhere 11 S12 = SQL Anywhere 12 S16 = SQL Anywhere 16 IP Address of the primary Xpress Server. directory for application files. Database Management System installation directory. Database Server Name. directory for the Xpress Server application files. User name of database account used by the Store Manager application to access the database. Password of the database account used by the Store Manager application to access database. ** Password must be encrypted using the default NON-PCI encryption algorithm. Default application language. ** only supports the following language codes: SAP SE or an SAP affiliate company. All rights reserved.

67 Section Key Description ENG = English FRE = French SPA = Spanish GER = German ITA = Italian [BACKOFF DB UPGRADE] DB_TYPE Type of Database Management System: MS = Microsoft SQL Server S11 = SQL Anywhere 11 S12 = SQL Anywhere 12 S16 = SQL Anywhere 16 DB_PATH LOG_PATH BACKUP_DIR DATABASE_APP_PATH DATABASE_SERVER DB_USER DB_PASS directory for the Xpress Server database file. directory for the Xpress Server database log file. Location of the database backup directory. Database Management System installation directory. Database Server Name. Database Administrator User Name. Database Administrator Password. ** Password must be encrypted using the default NON-PCI encryption algorithm. LANGUAGE Default application language. [BACKUP BACKOFF DB UPGRADE] DB_TYPE ** only supports the following language codes: ENG = English FRE = French SPA = Spanish GER = German ITA = Italian Type of Database Management System: MS = Microsoft SQL Server S11 = SQL Anywhere 11 S12 = SQL Anywhere SAP SE or an SAP affiliate company. All rights reserved. 67

68 Section Key Description S16 = SQL Anywhere 16 DB_PATH LOG_PATH BACKUP_DIR DATABASE_APP_PATH DATABASE_SERVER DB_USER directory for the Xpress Server database file. directory for the Xpress Server database log file. Location of the database backup directory. Database Management System installation directory. Database Server Name. Database Administrator User Name. ** Password must be encrypted using the default NON-PCI encryption algorithm. DB_PASS Database Administrator Password. ** Password must be encrypted using the default NON-PCI encryption algorithm. LANGUAGE Default application language. ** only supports the following language codes: ENG = English FRE = French SPA = Spanish GER = German ITA = Italian [EJV DB UPGRADE] DB_TYPE Type of Database Management System: MS = Microsoft SQL Server S11 = SQL Anywhere 11 S12 = SQL Anywhere 12 S16 = SQL Anywhere 16 DB_PATH LOG_PATH BACKUP_DIR directory for the Xpress Server database file. directory for the Xpress Server database log file. Location of the database backup directory SAP SE or an SAP affiliate company. All rights reserved.

69 Section Key Description DATABASE_APP_PATH DATABASE_SERVER DB_USER DB_PASS Database Management System installation directory. Database Server Name. Database Administrator User Name. Database Administrator Password. ** Password must be encrypted using the default NON-PCI encryption algorithm. LANGUAGE Default application language. ** only supports the following language codes: ENG = English FRE = French SPA = Spanish GER = German ITA = Italian [DB TOOLS UPGRADE] INSTALL_DIRECTORY directory for application files. UPGRADE_BACKOFF UPGRADE_JOURNAL XPS_DB_TYPE (Y=Yes / N=No) Configure the Xpress Server database to be upgraded using Database Tools. (Y=Yes / N=No) Configure the Journal Viewer database to be upgraded using Database Tools. Type of Database Management System for the Xpress Server database. MS = Microsoft SQL Server S11 = SQL Anywhere 11 S12 = SQL Anywhere 12 S16 = SQL Anywhere 16 XPS_BACKUP_DIR XPS_DATABASE_SERVER XPS_DB_USER Location of the Xpress Server database backup directory. Database Server Name used to host the Xpress Server database. User name of the database account used by the Database Tools application to access the Xpress Server database SAP SE or an SAP affiliate company. All rights reserved. 69

70 Section Key Description XPS_DB_PASS Password of database account used by the Database Tools application to access the Xpress Server database. ** Password must be encrypted using the default NON-PCI encryption algorithm. EJD_DB_TYPE Type of Database Management System for the Xpress Server database: MS = Microsoft SQL Server S11 = SQL Anywhere 11 S12 = SQL Anywhere 12 S16 = SQL Anywhere 16 EJD _BACKUP_DIR EJD _DATABASE_SERVER EJD _DB_USER EJD _DB_PASS Location of the Journal Viewer database backup directory. Database Server Name used to host the Journal Viewer database. User name of database account used by the Database Tools application to access the Journal Viewer database. Password of database account used by the Database Tools application to access the Journal Viewer database. ** Password must be encrypted using the default NON-PCI encryption algorithm. LANGUAGE Default application language. [BACKUP DB TOOLS UPGRADE] INSTALL_DIRECTORY UPGRADE_BACKOFF ** only supports the following language codes: ENG = English FRE = French SPA = Spanish GER = German ITA = Italian directory for application files. (Y=Yes / N=No) Configure the Xpress Server database to be upgraded using the Database Tools SAP SE or an SAP affiliate company. All rights reserved.

71 Section Key Description UPGRADE_JOURNAL XPS_DB_TYPE (Y=Yes / N=No) Configure the Journal Viewer database to be upgraded using the Database Tools. Type of Database Management System for the Xpress Server database: MS = Microsoft SQL Server S11 = SQL Anywhere 11 S12 = SQL Anywhere 12 S16 = SQL Anywhere 16 XPS_BACKUP_DIR XPS_DATABASE_SERVER XPS_DB_USER XPS_DB_PASS Location of the Xpress Server database backup directory. Database Server Name used to host the Xpress Server database. User name of database account used by the Database Tools application to access the Xpress Server database. Password of database account used by the Database Tools application to access the Xpress Server database. ** Password must be encrypted using the default NON-PCI encryption algorithm. EJD_DB_TYPE Type of Database Management System for the Xpress Server database: MS = Microsoft SQL Server S11 = SQL Anywhere 11 S12 = SQL Anywhere 12 S16 = SQL Anywhere 16 EJD _BACKUP_DIR EJD _DATABASE_SERVER EJD _DB_USER EJD _DB_PASS Location of the Journal Viewer database backup directory. Database Server Name used to host the Journal Viewer database. User name of database account used by the Database Tools application to access the Journal Viewer database. Password of database account used by the Database Tools application to access the Journal Viewer database SAP SE or an SAP affiliate company. All rights reserved. 71

72 Section Key Description ** Password must to be encrypted using the default NON-PCI encryption algorithm. LANGUAGE Default application language. ** only supports the following language codes: ENG = English FRE = French SPA = Spanish GER = German ITA = Italian [TRANSNET UPDATE] SERVERPORT Port number assigned to the Transnet Client to connect to the credit provider. SERVERADDR CLASSPATH_ADDITIONS INSTALL_DIRECTORY CHAIN_ID IP Address assigned to the Transnet Client to connect to the credit provider. Defines additional jar files to be appended to the end of the Transnet application class path. directory for application and configuration files. Identifier of store chain. [RETAILER SPECIFIC INSTALLER] SERVERSSLTYPE ICONNECT LANINACTIVITYTO KEEPALIVE KEEPALIVETIME KEEPALIVEINTERVAL PING PINGCOUNT PINGWAIT TIMEOUT RSI_LOGFILE RSI_CMDLINE_REGISTER Location and file name of the log file generated by Retailer Specific. Command line that is used by the Automated Installer application to SAP SE or an SAP affiliate company. All rights reserved.

73 Section Key Description launch the Retailer Specific on the register. **Command line includes the name of the executable and command line parameters. RSI_CMDLINE_SERVER Command line that is used by the Automated Installer application to launch the Retailer Specific on the Xpress Server/Backup Xpress Server. **Command line includes the name of the executable and command line parameters. *** All other keys and values for Retailer-Specific installation to be defined by the developer of Retailer-Specific. Entries appearing in this section are not used by the Automated Installer application other than: RSI_CMDLINE_REGISTER, RSI_CMDLINE_SERVER, and RSI_LOGFILE *** [MERCHANT_XML] [GENERICMERCHANT_XML] [< SPECIFIC>MERCHANT_XML] ** See Installing Transnet Client for an explanation of each key available under the [MERCHANT_XML] section. ** See Installing Transnet Client for an explanation of each key available under the [GENERICMERCHANT_XML] section. You can create your own [< SPECIFIC>MERCHANT_XML] based on the [MERCHANT_XML] or [GENERICMERCHANT_XML] sections. o Configure a [< SPECIFIC>MERCHANT_XML] section to update Transnet XML configuration files. Separate sections must be created in <store number>.ini for each type of customer-specific merchant XML file that must be supported by the Transnet Client application. A customer-specific section must start with [and end with MERCHANT_XML] for the Automated Installer to extract a value for each entry found in the section and update the corresponding setting in the customer-specific XML configuration file. A customer specific section can contain settings for multiple registers. The value of RegisterId denotes which register number the register settings CreditName and DebitName apply to. The register settings must appear at the end of the section SAP SE or an SAP affiliate company. All rights reserved. 73

74 Note Entries in the [< SPECIFIC>MERCHANT_XML] section of <store number>.ini are not mandatory. Store- Specific INI Section Store-Specific INI Key Transnet Configuration File Updated Transnet Configuration Setting [TRANSNET UPDATE] CHAIN_ID config\transnet.xml Transnet SystemID=<chain_store_instance > [AUTOMATED INSTALLER APPLICATIO N] STORENUMBER ** Chain is set to the value of chain ID extracted from key CHAIN_ID under section [TRANSNET UPDATE] in <store number>.ini. Transnet SystemID=<chain_store_instance > ** Store is set to the value of store number entered through the GUI. Transnet SystemID=<chain_store_instance > ** Instance is set to 1 for primary and 2 for backup. [TRANSNET UPDATE] CHAIN_ID config\merchant.xml <Merchants> <Chain> <ChainId></ChainId> [AUTOMATED INSTALLER APPLICATIO N] STORENUMBER <Store> </Store> ** Chain is set to the value of chain ID extracted from key CHAIN_ID under section [TRANSNET UPDATE] in store specific INI file. <Merchants> <Chain> <Store> <StoreId></StoreId> </Store> ** Store is set to a value of store number entered through the GUI. [MERCHANT_ XML] ExtStoreId config\merchant.xml <Merchants> <Chain> SAP SE or an SAP affiliate company. All rights reserved.

75 Store- Specific INI Section Store-Specific INI Key Transnet Configuration File Updated Transnet Configuration Setting <Store> <ExtStoreId><ExtStoreId> </Store> ServiceType <Merchants> <Chain> <Store> <ServiceType><ServiceType> </Store> Name <Merchants> <Chain> <Store> <Name><Name> </Store> City <Merchants> <Chain> <Store> <City><City> </Store> State <Merchants> <Chain> <Store> <State><State> </Store> Account <Merchants> <Chain> <Store> <Account><Account> </Store> SecurityCod e <Merchants> <Chain> <Store> <SecurityCode><SecurityCode> </Store> 2016 SAP SE or an SAP affiliate company. All rights reserved. 75

76 Store- Specific INI Section Store-Specific INI Key Transnet Configuration File Updated Transnet Configuration Setting ClearingCod e <Merchants> <Chain> <Store> <ClearingCode><ClearingCode> </Store> ExtAccount <Merchants> ExtAccount <Chain> <Store> <ExtAccount><ExtAccoun t> </Store> BINNumber <Merchants> BINNumber <Chain> <Store> <BINNumber><BINNumber> </Store> ICANumber <Merchants> ICANumber <Chain> <Store> <ICANumber><ICANumber> </Store> CategoryCo de <Merchants> <Chain> CategoryCode <Store> <CategoryCode><Categor ycode> </Store> CheckProce ssor <Merchants> <Chain> CheckProcessor <Store> <CheckProcessor><Check Processor> SAP SE or an SAP affiliate company. All rights reserved.

77 Store- Specific INI Section Store-Specific INI Key Transnet Configuration File Updated Transnet Configuration Setting </Store> Contact <Merchants> Contact <Chain> <Store> <Contact><Contact> </Store> BusinessCu tovertime <Merchants> <Chain> BusinessCutoverTime <Store> <BusinessCutoverTime>< BusinessCutoverTime> </Store> RegisterId <Merchants> RegisterId <Chain> <Store> <Register> <RegisterId><RegisterI d> </Register> CreditName <Merchants> CreditName <Chain> <Store> <Register> <CreditName><CreditNam e> </Register> DebitName <Merchants> DebitName <Chain> <Store> <Register> <DeditName><DeditName> </Register> 2016 SAP SE or an SAP affiliate company. All rights reserved. 77

78 Store- Specific INI Section Store-Specific INI Key Transnet Configuration File Updated Transnet Configuration Setting [< SPECIFIC> MERCHANT_X ML] Refer to the section [MERCHANT_X ML] for an explanation of supported fields. config\<customer Specific>Merchant.xml Refer to the section [MERCHANT_XML] for an explanation of supported fields. o To configure the Automated Installer to launch the Retailer Specific, use the command line executables listed below. Depending on the type of installation configured (Register or Xpress Server); the Automated Installer will launch the appropriate executable. Automated Installer Configuration Register Xpress Server Retailer Specific Installer Application Value of RSI_CMDLINE_REGISTER Value of RSI_CMDLINE_SERVER Ensure that the command line contains the name of the Retailer-Specific installation executable and any necessary command line parameters. Parameters must be separated from the executable by a blank space (ASCII 32) for the Automated Installer to launch the Retailer-Specific. 9. Save INI using the store number in the location specified in Step 1. Example Store number has the corresponding INI file: INI. 10. Close <store number>.ini. 11. Repeat from Step 7 for each store and installation type (Xpress Server or Register) Installing SAP POS with the Automated Installer Note Before you start the installation make sure that you follow the steps below: 1. Make sure the computer is clean of any residual POS installations. Remove the folders under SAP\Retail systems in Program Files and Program Data. Also, remove all registry entries under SAP\Retail systems. 2. Delete the folder named Working Folder in %temp%. 3. Install the latest Windows support pack. 4. Select the Database Tools to be installed on every computer with a database. It must be the first product being installed. 5. In the STORE INI files, the option INSTALL_DEMO_PARMS = Y is not used. PARM files are always installed regardless of this setting SAP SE or an SAP affiliate company. All rights reserved.

79 Procedure Launch the Automated Installer from the directory where the Automated Installer AUTOINST.EXE resides. Right click on AUTOINST.EXE and choose Run as Administrator. 1. The Automated Installer will extract the working directory from the [APPLICATION GUI] section in AUTOINST.INI and compare this with the directory from where the Automated Installer is launched. o If these are different, (for example, if the Automated Installer is launched from a DVD and the working directory is on the local hard drive of the machine where the installation takes place), the Automated Installer extracts from the set of applications and/or databases configured for installation and copies these from the DVD to predetermined subdirectories under the working directory o If a working directory is not specified in the [APPLICATION GUI] section of AUTOINST.INI or the working directory is the same as the directory where the Automated Installer is launched, an error is generated by the Automated Installer and the installation session is aborted. The working directory can be defined with the macro %TEMP%. The Automated Installer replaces this macro with the value of the Windows TEMP environment variable o The Automated Installer ensures that all configurations are defined for each section of AUTOINST.INI. An error message appears due to a missing key or value and the installation session is aborted o The Automated Installer creates the ASCII text log file AUTOINST.LOG in the working directory. 2. Depending on the Type key in the [APPLICATION GUI] section of AUTOINST.INI, you are presented with a GUI that allows you to enter a predefined set of register attributes. o If the type is not configured or cannot be determined as being either Register or Xpress Server, you are presented with a GUI void of any data entry fields, text labels, and button controls. An error message displays indicating that the type of installation has not been specified and the installation session is aborted. Enter the information prompted in the GUI. Once the installation begins, you are not able to alter any of the responses. 3. For register installations: o Store number o Register number o Register type o Parameter group o Primary Xpress Server IP address o Backup Xpress Server IP address o Your name. 4. For primary and backup Xpress Server installations: o Store number o Option for primary or backup Xpress Server o Primary Xpress Server IP address o Backup Xpress Server IP address o Your name. Select OK. 5. The Automated Installer validates that all fields in the GUI are defined and an error message displays if you leave any of them blank 2016 SAP SE or an SAP affiliate company. All rights reserved. 79

80 6. If the <store number>.ini cannot be located, an error message displays and you cannot proceed with the installation until a valid store number is entered 7. The Automated Installer validates that all required installation, configuration and application files residing in the staging area are available. If the required files are missing, an error message displays and the installation session is aborted 8. The Automated Installer copies the <store number>.ini in the working directory and updates it with the values entered in the GUI 9. The Automated Installer copies the required installation, configuration, and application files from the staging area to the working directory 10. ***The Automated Installer sequentially triggers the installation of each application and/or database configured in AUTOINST.INI in the following order: Order Description Internal Identifier Successful Registry Entry 0 Xpress Server Database 1 Backup Xpress Server Database 2 Journal Viewer Database XPD BXD EJD Backoff Database Backoff Database Journal Database 3 Database Tools DBT Database Tools 4 Backup Database Tools BDT Database Tools 5 Xpress Server XPS Xpress Server 6 Backup Xpress Server XPS Xpress Server 7 Store Manager SMG Store Manager 8 Journal Viewer EJV Journal Viewer 9 POS Client POS POS Client 10 Transnet Client TNT Transnet Client 11 Retailer Specific Installer 11. **For each application and/or database configured: o Prior to each installation, the Automated Installer: RSI Retailer Specific Installer o Validates each value in the <store number>.ini as each application and/or database is prepared for installation. If an error occurs due to a missing key or value, a message displays and the installation session is aborted. Any applications and/or databases successfully installed by the Automated Installer during the current installation session are not affected if the installation session is aborted due to missing values. Validation of a preconfigured value is strictly based on the values being mandatory. No attempt is made to validate the integrity of a preconfigured value. The only exclusion to this rule is the type of installation to perform o Validates the registry and if the application or database is already installed, it bypasses that installation. This ensures that subsequent installations through the Automated Installer result in the SAP SE or an SAP affiliate company. All rights reserved.

81 installation of only those applications and/or databases that were not previously installed successfully o Installs the application and/or database and updates the status field of the GUI with the name and number of the installation being performed. o After each installation, the Automated Installer: o Updates AUTOINST.LOG with a set of predefined responses for each installation and a set of post configurations for each register or Xpress Server. The Automated Installer consolidates the contents of AUTOINST.LOG so that the status of each installation can be reviewed after the installation process is complete. All messages captured in the ASCII text log file are in English regardless of the language specified in AUTOINST.INI. The Automated Installer captures the name of the user that performed the installation entered through the GUI o Adds an entry in the system registry denoting the successful installation. If the installation fails, the registry is not updated with the installation of the application. Example HKEY_LOCAL_MACHINE SOFTWARE SAP RETAIL SYSTEMS INSTALLED APPLICATIONS <installation description> <time of installation> <time of installation> is formatted as YYYY-MM-DD HH:MM:SS AM/PM Note The Retail Specific Installer must create its own entry to the registry when successfully installed, where the registry string name is Retailer-Specific Installer. The Automated Installer does not add this entry automatically as it does for the other applications/databases. o The Automated Installer looks for this specific register entry to make the determination pertaining to the success or failure of the Retailer-Specific o Invokes the batch file POSTINST.BAT, located in the same directory as the AUTOINST.EXE which copies store-specific customer parameter files from the Store Parameter Files subdirectory in the staging area to the parm subdirectory on the POS Client or Xpress Server, depending on the Type defined in <store number>.ini. Five parameters are passed from the Automated Installer to the batch file: - Store number as entered through the GUI - Register number as entered through the GUI (if installing a register) - Location from which the Automated Installer was launched - Type of application or database that is installed - Location of the application installation directory under the working directory. o The log file POSTINST.LOG is created and the contents consolidated to AUTOINST.LOG upon the successful completion of the batch, denoted by a 0 exit code (exit code 1 = error). If the post batch installation process returns an error, the Automated Installer displays a message and aborts the 2016 SAP SE or an SAP affiliate company. All rights reserved. 81

82 installation process. If the batch installation process is successful, the Automate Installer application continues with the next application or database installation. The batch file returns a successful result if there is no post batch processing required for the type of installation being performed by the Automated Installer. 12. The Automated Installer installs the next application or database listed in Step*** above and repeats Step**. When the Automated Installer gets to the Retailer-Specific application, if configured, an ASCII text log file is generated. The Automated Installer looks for the name of the log file as defined by the value of the RSI_LOGFILE under the [RETAILER SPECIFIC INSTALLER] section of <store number>.ini. o The installation proceeds as in Step**, with the content of the Retailer-Specific log file concatenated into the AUTOINST.LOG file after the installation of the Retailer-Specific is complete o Since <store number>.ini is specific to the store and the name of the Retailer-Specific log file is unknown at the time of launching the installation, the Automated Installer copies the corresponding <store number>.ini from the working directory to the Retailer Specific Installers subdirectory, renaming it to install_config.ini. The Retailer Specific looks for this file with this naming convention to obtain settings from <store number>.ini. 13. At the end of the installation process, the Automated Installer automatically exits if no error has occurred. Otherwise, an error message displays, requiring you to press any key to acknowledge the error and then the Automated Installer exits Sample AUTOINST.INI and <store number>.ini Files Sample AUTOINST.INI [APPLICATION GUI] Syntax ;To install applications on the register set TYPE = REGISTER ;To install applications on the primary/backup server set TYPE = XPRESS SERVER ;To set delay before launching post installation batch process set BATCHLAUNCHDELAY = <number of seconds> ;To set logging level: LOGLEVEL = 0 for minimal logging / set LOGLEVEL = 1 for maximum logging ;To set location of working directory to windows temporary directory set WORKINGDIRECTORY = %TEMP% TYPE = XPRESS SERVER LANGUAGE = ENGLISH WORKINGDIRECTORY = %TEMP%\Working Directory BATCHLAUNCHDELAY = 15 LOGLEVEL = SAP SE or an SAP affiliate company. All rights reserved.

83 ; List of translatable application literals and messages. If a translation ; has not been specified for a literal / message in a specified language the ; literal / message will be defaulted to English [ENGLISH TRANSLATION] ; List of translatable error messages 1 = Unable to open file: %s 2 = Unable to close file: %s 3 = Unable to read from file: %s 4 = Unable to write to file: %s 6 = Unable to copy file: %s 9 = Unable to truncate file: %s 11 = Unable to initialize file search 12 = Unable to continue file search 16 = Unable to start program launch listener thread 17 = Unable to stop program launch listener thread 18 = Unable to launch program: %s 19 = Invalid program return code: (%d) %s 20 = Unable to instantiate application window 21 = Unable to start install process listener thread 22 = Unable to stop install process listener thread 23 = Unable to create the application working directory: %s 24 = Application working directory cannot be defined as the application directory: %s 25 = Mandatory setting(s) not defined in the application INI file: %s 26 = Application working directory is not defined in the application INI file: %s 27 = Invalid type of installation defined in the application INI file: %s 28 = Unable to locate build version in %s 29 = Unable to locate application INI file: %s 30 = Unable to open the application log file: %s 31 = Applications / databases have not been configured for installation 32 = Unable to locate the store specific INI file; %s 33 = Mandatory field in GUI is required: %s 34 = Invalid value entered in GUI, %s must be between %d and %d 35 = Mandatory setting(s) not defined in the store specific INI file: %s 36 = Unable to locate Language INI file: %s 37 = Unable to initialize directory search 2016 SAP SE or an SAP affiliate company. All rights reserved. 83

84 38 = Unable to continue directory search 39 = Unable to create directory: %s 40 = Unable to copy directory: %s 42 = Unable to delete registry value: %s - %s 43 = Unable to update registry value %s - %s 44 = Unable to create registry key: %s 45 = Unable to retrieve registry value %s - %s 46 = Unable to determine the application/database installation path 47 = Unable to locate Post batch log file: %s 48 = Unable to open service manager 49 = Unable to close service manager 50 = Unable to create service: %s 51 = Unable to delete service: %s 52 = Unable to open service: %s 53 = Unable to close service %s 54 = Unable to stop service: %s 55 = Unable to query service: %s 56 = Unable to control service: %s 57 = Unable to retrieve XML file: %s 58 = Unable to update XML file: %s 59 = Unable to access XML root node: %s 60 = Unable to get XML node list: %s 61 = Unable to get XML node item: %s 63 = session has been completed successfully 64 = session has generated an error 65 = session has been cancelled 66 = Mandatory file(s) not found in the application Staging Area directory 67 = Unable to validate application Staging Area directory 68 = Unable to locate Post batch log file: %s ; List of translatable literals INFORMATION = Information WARNING = Warning ERROR = Error STORENUMBER = STORE NUMBER REGISTERNUMBER = REGISTER NUMBER REGISTERTYPE = REGISTER TYPE PARMGROUP = PARAMETER GROUP PRIMARYSERVERIPADDRESS = PRIMARY SERVER IP ADDRESS BACKUPSERVERIPADDRESS = BACKUP SERVER IP ADDRESS SAP SE or an SAP affiliate company. All rights reserved.

85 SCANNER = SCANNER PRESENT (Y or N) BANAMEXPORT = BANAMEX SERVER PORT INSTALLER = INSTALLER SAPPOSCUSTOMIZATION = SAP POS CUSTOMIZATION SCREENREGISTER = SCREEN: REGISTER SCREENSERVER = SCREEN: SERVER XPRESSSERVER = XPRESS SERVER PRIMARY = PRIMARY BACKUP = BACKUP CANCEL = CANCEL OK = OK STATUS = STATUS: INSTALLING = Installing OF = OF INSTALLATIONS = INSTALLATIONS [REGISTER APPLICATIONS] POS = Y XPS = N XPD = N SMG = N EJV = N EJD = N DBT = N TNT = N RSI = N [PRIMARY SERVER APPLICATIONS] POS = N XPS = Y XPD = Y SMG = Y EJV = Y EJD = Y DBT = Y TNT = Y RSI = N [BACKUP SERVER APPLICATIONS] 2016 SAP SE or an SAP affiliate company. All rights reserved. 85

86 POS = N XPS = Y XPD = Y SMG = N EJV = N EJD = N DBT = Y TNT = Y RSI = N Sample <store number>.ini [APPLICATION GUI] ; IMPORTANT: LEAVE THESE SETTINGS BLANK, VALUES WILL BE POPULATED WITH CORRESPONDING ; VALUES ENTERED THROUGH GUI AFTER PRESSING OK BUTTON TO START INSTALLATION STORENUMBER = REGISTERNUMBER = PRIMARYXPRESSSERVER = BACKUPXPRESSSERVER = REGISTERTYPE = PARMGROUP = PRIMARYSERVERIPADDRESS = BACKUPSERVERIPADDRESS = ; Manager Code 2 / Manager Code 6 Settings For Default Register [REGISTER DEFAULT] MC2_OPOS_PRINTER = Simulator MC2_OPOS_PRINTER_KNIFE = Y MC2_OPOS_PRINTER_CHEQUE_FLIP = N MC2_OPOS_LINEDISPLAY = NONE MC2_OPOS_CASHDRAWER_1 = NONE MC2_OPOS_CASHDRAWER_2 = NONE MC2_OPOS_MSR = NONE MC2_OPOS_SCANNER = NONE SAP SE or an SAP affiliate company. All rights reserved.

87 MC2_OPOS_SCANNER_EXPAND_UPCE = N MC2_OPOS_MICR = NONE MC2_OPOS_MICR_CHEQUE_FACE_UP = N MC2_OPOS_KEYLOCK = NONE MC2_OPOS_SCALE = NONE MC2_OPOS_KEYBOARD = NONE MC2_SIGNATURE_CAPTURE = NONE MC2_OPOS_CASHDRAWER_1_CASHBOXES = 0 MC2_OPOS_CASHDRAWER_2_CASHBOXES = 0 MC6_REGISTER_TYPE = 1 MC6_REPORT_GROUP = 1 MC6_PARM_GROUP = 1 MC6_STATE_PROVINCE = ON MC6_LOCAL_PLU = N MC6_BACKUP_SERVER = N MC6_BACKUP_CREDIT_SERVER = N MC6_PRIMARY_SERVER_IP = MC6_BACKUP_SERVER_IP = ; Primary/Backup Xpress Server Console Settings [PRIMARY XPRESS SERVER] PRIMARY_XPS_PLUCACHE = 1000 PRIMARY_XPS_PARMPROC = C:\<PROGRAM_FILES>\SAP\Retail Systems\Xpress Server\XPSPARM.BAT PRIMARY_XPS_EODPROC = C:\<PROGRAM_FILES>\SAP\Retail Systems\Xpress Server\EODPROC.BAT PRIMARY_XPS_NEWPARMINT = 30 PRIMARY_XPS_SHOWEODPROC = 1 PRIMARY_XPS_LOGFILE = C:\<PROGRAM_FILES>\SAP\Retail Systems\Xpress Server\XPS.LOG PRIMARY_XPS_SHOWDATE = 1 PRIMARY_XPS_LOGSIZE = [BACKUP XPRESS SERVER] BACKUP_XPS_PLUCACHE = 1000 BACKUP_XPS_PARMPROC = C:\<PROGRAM_FILES>\SAP\Retail Systems\Xpress Server\XPSPARM.BAT BACKUP_XPS_EODPROC = C:\<PROGRAM_FILES>\SAP\Retail Systems\Xpress Server\EODPROC.BAT 2016 SAP SE or an SAP affiliate company. All rights reserved. 87

88 BACKUP_XPS_NEWPARMINT = 30 BACKUP_XPS_SHOWEODPROC = 1 BACKUP_XPS_LOGFILE = C:\<PROGRAM_FILES>\SAP\Retail Systems\Xpress Server\XPS.LOG BACKUP_XPS_SHOWDATE = 1 BACKUP_XPS_LOGSIZE = BACKUP_XPS_BKSRV = 1 BACKUP_XPS_SERVERNAME = ; Application / Database Responses [POS UPGRADE] INSTALL_BROWSER = N INSTALL_DEMO_PARMS = Y CREDIT = EF INSTALL_DIRECTORY = C:\<PROGRAM_FILES>\SAP\Retail Systems\Point of Sale UTIL_DIRECTORY = C:\<PROGRAM_FILES>\SAP\Retail Systems\Utilities SERVER_IP = BACKUP_SERVER_IP = LANGUAGE = ENG [XPS UPGRADE] INSTALL_API = N DB_TYPE = MS CREDIT = EF DATABASE_APP_PATH = C:\<PROGRAM_FILES>\Microsoft SQL Server\90\Tools DATABASE_SERVER = <Database Server Name> INSTALL_DIRECTORY = C:\<PROGRAM_FILES>\SAP\Retail Systems\Xpress Server INSTALL_DEMO_PARMS = Y UTIL_DIRECTORY = C:\<PROGRAM_FILES>\SAP\Retail Systems\Utilities DB_USER = sa DB_PASS = <Encrypted Database User Password> LANGUAGE = ENG [BACKUP XPS UPGRADE] INSTALL_API = N DB_TYPE = MS CREDIT = EF DATABASE_APP_PATH = C:\<PROGRAM_FILES>\Microsoft SQL Server\90\Tools DATABASE_SERVER = <Database Server Name> SAP SE or an SAP affiliate company. All rights reserved.

89 INSTALL_DIRECTORY = C:\<PROGRAM_FILES>\SAP\Retail Systems\Xpress Server INSTALL_DEMO_PARMS = Y UTIL_DIRECTORY = C:\<PROGRAM_FILES>\SAP\Retail Systems\Utilities DB_USER = sa DB_PASS = <Encrypted Database User Password> LANGUAGE = ENG [EJV UPGRADE] DB_TYPE = MS INSTALL_DIRECTORY = C:\<PROGRAM_FILES>\SAP\Retail Systems\Sales Journal Viewer DATABASE_APP_PATH = C:\<PROGRAM_FILES>\Microsoft SQL Server\90\Tools DATABASE_SERVER = <Database Server Name> DB_USER = sa DB_PASS = <Encrypted Database User Password> XPRESS_SERVER_PATH = C:\<PROGRAM_FILES>\SAP\Retail Systems\Xpress Server LANGUAGE = ENG [STORE MANAGER UPGRADE] DB_TYPE = MS SERVER_IP = INSTALL_DIRECTORY = C:\<PROGRAM_FILES>\SAP\Retail Systems\Store Manager DATABASE_APP_PATH = C:\<PROGRAM_FILES>\Microsoft SQL Server\90\Tools DATABASE_SERVER = <Database Server Name> XPRESS_SERVER_PATH = C:\<PROGRAM_FILES>\SAP\Retail Systems\Xpress Server DB_USER = sa DB_PASS = <Encrypted Database User Password> LANGUAGE = ENG [BACKOFF DB UPGRADE] DB_TYPE = MS DB_PATH = C:\<PROGRAM_FILES>\SAP\Retail Systems\Databases LOG_PATH = C:\<PROGRAM_FILES>\SAP\Retail Systems\Databases BACKUP_DIR = C:\<PROGRAM_FILES>\SAP\Retail Systems\Databases\Backup DATABASE_APP_PATH = C:\<PROGRAM_FILES>\Microsoft SQL Server\90\Tools DATABASE_SERVER = <Database Server Name> DB_USER = sa DB_PASS = <Encrypted Database User Password> LANGUAGE = ENG 2016 SAP SE or an SAP affiliate company. All rights reserved. 89

90 [BACKUP BACKOFF DB UPGRADE] DB_TYPE = MS DB_PATH = C:\<PROGRAM_FILES>\SAP\Retail Systems\Databases LOG_PATH = C:\<PROGRAM_FILES>\SAP\Retail Systems\Databases BACKUP_DIR = C:\<PROGRAM_FILES>\SAP\Retail Systems\Databases\Backup DATABASE_APP_PATH = C:\<PROGRAM_FILES>\Microsoft SQL Server\90\Tools DATABASE_SERVER = <Database Server Name> DB_USER = sa DB_PASS = <Encrypted Database User Password> LANGUAGE = ENG [EJV DB UPGRADE] DB_TYPE = MS DB_PATH = C:\<PROGRAM_FILES>\SAP\Retail Systems\Databases LOG_PATH = C:\<PROGRAM_FILES>\SAP\Retail Systems\Databases BACKUP_DIR = C:\<PROGRAM_FILES>\SAP\Retail Systems\Databases\Backup DATABASE_APP_PATH = C:\<PROGRAM_FILES>\Microsoft SQL Server\90\Tools DATABASE_SERVER = <Database Server Name> DB_USER = sa DB_PASS = <Encrypted Database User Password> LANGUAGE = ENG [DB TOOLS UPGRADE] INSTALL_DIRECTORY = C:\<PROGRAM_FILES>\SAP\Retail Systems\DBTools UPGRADE_BACKOFF = Y UPGRADE_JOURNAL = Y XPD_DB_TYPE = MS XPD_BACKUP_DIR = C:\<PROGRAM_FILES>\SAP\Retail Systems\Databases\Backup XPD_DATABASE_SERVER = <Database Server Name> XPD_DB_USER = sa XPD_DB_PASS = <Encrypted Database User Password> EJD_DB_TYPE = MS EJD_BACKUP_DIR = C:\<PROGRAM_FILES>\SAP\Retail Systems\Databases\Backup EJD_DATABASE_SERVER = <Database Server Name> EJD_DB_USER = sa EJD_DB_PASS = <Encrypted Database User Password> LANGUAGE = ENG SAP SE or an SAP affiliate company. All rights reserved.

91 [BACKUP DB TOOLS UPGRADE] INSTALL_DIRECTORY = C:\<PROGRAM_FILES>\SAP\Retail Systems\DBTools UPGRADE_BACKOFF = Y UPGRADE_JOURNAL = Y XPD_DB_TYPE = MS XPD_BACKUP_DIR = C:\<PROGRAM_FILES>\SAP\Retail Systems\Databases\Backup XPD_DATABASE_SERVER = <Database Server Name> XPD_DB_USER = sa XPD_DB_PASS = <Encrypted Database User Password> EJD_DB_TYPE = MS EJD_BACKUP_DIR = C:\<PROGRAM_FILES>\SAP\Retail Systems\Databases\Backup EJD_DATABASE_SERVER = <Database Server Name> EJD_DB_USER = sa EJD_DB_PASS = <Encrypted Database User Password> LANGUAGE = ENG [TRANSNET UPDATE] SERVERPORT = 8400 SERVERADDR = CLASSPATH_ADDITIONS = INSTALL_DIRECTORY = C:\<PROGRAM_FILES>\SAP\Transnet CHAIN_ID = 1 SERVERSSLTYPE=1 ICONNECT = 1 LANINACTIVITYTO = 600 KEEPALIVE = TRUE KEEPALIVETIME = 60 KEEPALIVEINTERVAL = 60 PING = TRUE PINGCOUNT = 5 PINGWAIT = 3 TIMEOUT = 24 [RETAILER SPECIFIC INSTALLER] ; Please note that this is an example and would need to be customized for your specific command line executable(s). RSI_LOGFILE = install.log 2016 SAP SE or an SAP affiliate company. All rights reserved. 91

92 RSI_CMDLINE_REGISTER = installer_for_terminal.exe /r /x /y /z RSI_CMDLINE_SERVER = installer_for_server.exe /x ; Transnet Client Merchant XML settings (blank/empty values will not be updated in corresponding XML file) [MERCHANT_XML] ExtStoreId = ServiceType = Name = City = State = Account = SecurityCode = ClearingCode = ExtAccount = BINNumber = ICANumber = CategoryCode = CheckProcessor = Contact = BusinessCutoverTime = RegisterId = CreditName = DebitName = [GENERICMERCHANT_XML] StoreId = Account = BINNumber = ICANumber = StoreName = RegisterId = ; <<< AUTOMATED INSTALLER WILL COPY REGISTER DEFAULT SETTINGS FOR NEW REGISTERS BELOW >>> SAP SE or an SAP affiliate company. All rights reserved.

93 5 Pre- and Post- Process Flow Special Instructions for Installing Databases Setting up a Backup Server Obtaining the Database Server Name Changing the Display of POS Locations when Running Multiple POS Units on a Single Machine Localization and Language Support Configuring Mobile POS Devices Running Mobile POS Accessing Help Documentation and Changing the Default Location Performing the in MSI Silent Mode Integrating SAP POS with File and Message Transfer Functions Using the Security Key File. 5.1 Special Instructions for Installing Databases Installing Microsoft SQL 2008 Express 2008 R2 Edition or SQL 2012 Express and Standard Edition: Special Instructions Note SAP provides third-party information to help customers. This information may change without notice. SAP does not guarantee the accuracy of this third-party information. Note Microsoft SQL 2008 Express Edition or Microsoft SQL 2008 R2 is supported for Xpress Server, Store Manager, and Electronic Journal Viewer. Install the 32-bit SQL server on the 64-bit Windows. Microsoft SQL 2012 Express Edition or Microsoft SQL 2012 Express Professional is supported for Xpress Server, Store Manager, and Electronic Journal Viewer. Install the 32-bit SQL server on Windows 2012R2. Microsoft SQL2012 is only supported on Windows 2012 R2. Hint: To ensure a smooth installation of your SQL server, add the Dot net 3.5. Feature in Windows 2012R2 before running the SQL 2012 installation. Pre- and Post SAP SE or an SAP affiliate company. All rights reserved. 93

94 Installing 32-bit SQL Server on Windows 64-bit (x64) For POS 2.3 on a 64-bit (x64) Windows 7 operating system, install the 32-bit version of SQL Server. If you have installation media or an ISO image that contains both 32-bit and 64-bit versions of SQL Server 2008 or 2008 R2, follow these steps to install the 32-bit SQL Server on 64-bit Windows (x64): 1. When you insert the installation media, or mount the ISO image, in some cases you might need to doubleclick on the setup.exe. The SQL Server Center appears. 2. Select the Options link on the left. 3. Choose x86 to install the 32-bit (x86) version of the SQL Server. 4. To begin the 32-bit installation process, run the following command: setup.exe/action= install /x86=true. As an alternative, you can use the X86=true in the command line or answer file if you want an unattended installation of Microsoft SQL Server 2008 or 2008 R2. For SQL 2012 Standard and Express, choose the 32 bit distribution. To minimize update-related patching, it is suggested that you use the latest edition. As of this publication, the most recent version is SQL 2012 SP3 Standard Edition. Use Use this information to keep the installation consistent with Microsoft SQL Server 2008, 2008 Express Edition, 2008 R2 or SQL Server 2012 Standard or SQL Server Express 2012 SP3 or later. Procedure for SQL Start the installation of Microsoft SQL Server 2008, 2008 Express Edition, 2008 R2, SQL Server 2012 standard, Select Next. 2. When the installation starts, the SQL installer may need to install required components. To proceed, choose Install and then select Next. After the required components are installed, the SQL Server Wizard starts. 3. After the system checks run, select Next. 4. Do not select Hide Advanced Options. Select Next. 5. Under Client Components, enable all of the Connectivity Components, and then select Next. 6. Choose Default Instance and then select Next. 7. Under Use the Built in System Account, choose Local System and select Next. 8. Choose Mixed Mode Authentication and enter a password for the SA (system administrator) user. 9. Choose the Collation Designator and Sort Order options. Leave Latin1_General as the choice in the dropdown list. Select Next. 10. Do not select Enable User Instances. To add the user to the SQL Server Administrator role, select Add and then select Next. 11. In the Error Reporting dialog box, select Next. 12. Select Install. 13. Select Next and then Finish SAP SE or an SAP affiliate company. All rights reserved. Pre- and Post-

95 14. If the SQL Server is going to be used in the environment where another computer will access it, the user has to enable Named Pipes and TCP/IP connections by using the SQL Server Configuration Manager after the installation. Procedure for SQL 2012 SP3 1. Before installing, enable the Dot net 3.5 feature as mentioned in the previous section. 2. Install SQL 2012 Standard or SQL Express 2012 SP3 or later. 3. Select New SQL stand-alone installation or Add features to existing installation. Accept the license agreements. 4. On the Feature Selection screen, you only need to select database engine services. Choose the Unselect All button and select Database Services. 5. From a support perspective or for a lab environment, adding the SQL management tools may be helpful, but it s not necessary for the software to function. 6. Select the Instance Type as the default. 7. Leave the collation as is. It should display as SQL_Latin1_General_CP1_CI_AS. 8. Choose Mixed Mode for authentication. 9. Once the software is installed, use SQL Configuration Manager. o Enable TCP/IP support o Choose properties o Set TCP/IP to Enabled o Ensure that Listen All is selected o On the IP Properties tab, select IP Addresses o On the IPALL entry ensure that port 1433 is listed and that the TCP Dynamic port is blank. 10. Restart the SQL database service. 11. It is suggested that Netstat with the AN parameter be used to verify that 1433 is shown as listening. You will see at least two entries showing port 1433, one for the loopback and one showing the IP address or as depicted below: Result This installs the chosen version of Microsoft SQL Server with a single database instance with an SA user and password. Installing SAP Sybase SQL Anywhere 16 on a 64-bit Operating System: Special Instructions 1. During the installation, after the language selection and accepting the license agreement, choose Custom. 2. In the Custom installation options under Database choose not to install the SQL Anywhere (64-bit), but choose to install SQL Anywhere (32-bit) The 32 bit edition of the SQL Anywhere Server is required. The 32 bit database administration tools and other components are optional. Pre- and Post SAP SE or an SAP affiliate company. All rights reserved. 95

96 5.2 Setting up a Backup Server Use Retail activity must remain uninterrupted if a main server fails. To ensure this, you can set up a backup server that the POS terminals can revert to if a failure occurs. The backup server can support retail processes such as transactions, PLU, and customer information lookups. It can also receive trickles of transaction log and journal file information that provide additional sales data. The backup server can be a dedicated computer or any one of the regular POS terminals, provided it meets the minimum requirements to run the Xpress Server software. You must specify the terminals to copy information to the backup server. You can configure any, or all, of the terminals to work with the backup server. Prerequisites A compatible SQL database server application must be installed on your backup computer before you can configure the backup server. Procedure Installing Xpress Server on the Backup Server 1. Ensure that the primary Xpress Server is correctly installed and running. 2. On the backup server computer, install the Xpress Server and Xpress Server database software following the directions in the installation program and entering the appropriate information as required. 3. After installing the Xpress Server components on the backup server computer, close the installation program and reboot the computer. Configuring the Backup Server 1. When the computer restarts, the SQL program and Xpress Server start automatically. 2. On the server's Main tab, select Start. A series of line messages appear in the main Xpress Server window indicating that the system has read your license information and applied any default parameter settings. When it is finished processing all the necessary information, the messages Xpress Server Ready and Trickle Enabled appear. 3. Select the Properties tab. 4. In the Communications section of the screen, select Is Backup Server to indicate that this computer is used as the backup Xpress Server. 5. In the Primary Server Name field, enter the machine name or IP address of the primary server computer. 6. To save the information, select Apply. 7. Select the Main tab. 8. On this tab page, select Stop Server and wait for the server to stop. Select Start Server to restart the server. Watch for the line message indicating Backup Xpress Server Ready. The primary and backup servers synchronize. The system then performs a synchronization query every 5 minutes to ensure that the Xpress Server and backup server are working in tandem SAP SE or an SAP affiliate company. All rights reserved. Pre- and Post-

97 Configuring POS Terminals to Use the Backup Server Configure the POS terminals to revert to the backup server in case of an interruption to the main server. You can do this during the initial setup of the POS terminals or you can use Manager Code 6 at any time. 1. On each POS terminal, perform a Manager Code 6 (Define Terminal) function. 2. When prompted, indicate that you want to use a backup server and also indicate if you want to use a backup credit server (for backup credit authorization). 3. Enter the server names or IP addresses as prompted. The transaction files are then sent to both the primary and backup servers (but note that the transaction files are not posted to the database on the backup server). 5.3 Obtaining the Database Server Name Use To obtain the individual database server name at a store. Note You must be logged on to the system. Procedure Perform the following steps on the computer on which Xpress Server is installed: 1. On the Windows status bar, select Start. 2. Choose Programs SAP SQL Service Manager. 3. The SQL Anywhere Service Manager dialog box opens. The Service Name field contains the name of the database engine. 4. To exit select Close. 5.4 Changing the Display of POS Locations when Running Multiple POS Units on a Single Machine When more than one POS runs on the same machine, each active POS can look identical to the next one. This can cause the main screen to look cluttered and confusing. Since each POS has a distinct layout file, you can use the layout file to designate a specific location on the screen for each active POS. You can also define other distinctive display features such as the size of the window or the colors and style of the buttons, which can distinguish one POS from another. Pre- and Post SAP SE or an SAP affiliate company. All rights reserved. 97

98 Use You can use Manager Code 40 to create a layout file. This file is stored in the Parm directory. Note Currently only layout.ui0 is supported. Procedure To create a layout file: 1. Start the main POS. 2. Run Manager Code 40 and modify the layout for that POS as required. 3. When you are done select Save Changes. 4. At the Send File to Server Proceed prompt, select No. Caution Choosing Yes to this prompt sends a copy of the current layout file to the server. This results in the server sending the layout file to each additional POS installed on that machine and overwrites any distinguishing layout options that may have been set for the other POS'. 5. To copy the layout file to the parm directory for each POS: o Start each POS o Copy the new layout file into each additional POS parm directory o Customize the layout file for each POS by doing the following: o In the parm directory for each additional POS, double-click the layout file and open it using Notepad o Change the settings in the layout file as required to customize it for that specific POS. Example In the example below, the following settings are configured in the layout file: [General] NoResize=0 xsize=50 ysize=50 xoffset=0 (in increments of 10 depending on the POS) yoffset=0 (in increments of 10 depending on the POS) Result To apply the changes made to the layout file, restart each POS. To toggle between the various POS units use the ALT+TA B function in Windows. The terminal number and program name display in the status bar SAP SE or an SAP affiliate company. All rights reserved. Pre- and Post-

99 5.5 Localization and Language Support SAP POS supports several languages other than English. For up-to-date information and the countries and languages supported, see the support.sap.com/pam Language-Check Message During During the installation of the individual SAP POS components, you choose the language for your store. The installation software executes a check in the background to determine whether the current Windows code page supports the language you selected. If the check fails, the following message is displayed: Selected language ({1}) is not supported by this PC s Windows Code Page. Details: Current code page detected is {2}, expected code page is {3}. Please cancel the installation and set proper Windows Code Page to continue. Where: 1. {1} is the 3-character ISO code for the language you chose; such as ENG for English, ITA for Italian, and so on. 2. {2} is the detected system code page; for example, {3} is the expected code page for the chosen language; for example, Translating Parameter Texts To provide interface text in multiple languages, you must manually translate the text into the desired language using functionality in either the Store Configurator component or Store Manager component. When you complete the translation, the translated text is applied to the POS Client. Interface texts are then available in the desired language for the POS terminals and the Store Manager component. For more information, see Translating POS Parameter Texts in the Configurator Application in the SAP Library documentation. 5.6 Configuring Mobile POS Devices Mobile POS Client is a mobile thin client POS component supported by an infrastructure that consists of a wireless handheld or mobile device, an access point, and a wireless printer. Your environment may also include a magnetic stripe reading (MSR) device or a signature capture device. In addition to installing software that sets up and links Mobile POS Client as a recognized terminal in your store, you must also configure additional devices that support the Mobile POS terminal. For more information, see 4.8 Installing Mobile Point-of-Sale Client. The following diagram illustrates how Mobile POS devices are set up in relation to the access point: Pre- and Post SAP SE or an SAP affiliate company. All rights reserved. 99

100 Mobile POS Application Technical Notes The current version of Mobile POS Client is based on Windows CE thin-client architecture. The program is written using the Microsoft Pocket PC SDK, the Symbol 8100 SDK, and Microsoft Embedded VC The Symbol SDK handles the hardware elements of the program. Supported Devices The Mobile POS Client is composed of a networking module, a simple GUI, and hardware components for the scanner and MSR. The printer is a TCP/IP printer. After you install the Mobile POS Client, you must configure the supporting wireless devices that run the Mobile POS network and link it to the server. You must define specific settings for each of the following devices: Wireless switch (controls the Mobile POS wireless network) Handheld device Printer. The following sections provide basic information on the settings that you must configure to operate your Mobile POS network correctly. For additional or more specific information on each device referenced, see the vendor s Web site Setting up the Wireless Network Refer to the manufacturer s documentation for assistance with setting up your wireless network SAP SE or an SAP affiliate company. All rights reserved. Pre- and Post-

101 Recommendation We recommend the use of WPA2, which is more secure than WPA. To make the key truly secure, use an encryption key with a variety of letters, numbers, and special characters Connecting Handheld Devices to the Wireless Network Mobile POS supports the Symbol MC3000 and Symbol PDT 8146 XScale handheld device models. The following steps describe how to connect the Symbol MC3000 to your wireless network. Procedure 1. On the Mobile POS device, select the task bar. 2. Choose Menu settings. 3. Enable the Auto Hide option. 4. This hides the status bar at the bottom of the mobile device, thus providing you with more screen space. 5. Select the task bar again. 6. Select the Wireless Network icon and connect to the ESSID. The wireless switch name is ESSID, for example ESSID= Select the Authentication tab and choose WEP 128 as the encryption standard. 8. Enter the required secure encryption key. 9. In the IP Configuration field, make sure that DHCP is selected. 10. Test your wireless infrastructure by pinging the handheld device from the host PC Connecting a Printer to the Wireless Network For instructions on connecting a printer to the wireless network, refer to your hardware manufacturer s documentation. Recommendation We recommend the use of QL320+ printer that supports G. Test your wireless infrastructure by pinging the printer from the host PC. Note If you have problems communicating with the devices using the ping utility, call your hardware vendor for assistance. Pre- and Post SAP SE or an SAP affiliate company. All rights reserved. 101

102 5.6.4 Troubleshooting the Mobile POS Configuration The following section provides some frequently asked questions that may arise as you configure Mobile POS devices. How do I warm-boot the mobile device? Press and hold down sequence keys 7, 9 and the red powe r button at the same time. What can I do if the device says Not Connected? Check the following: Check that the thin client, which resides on the handheld device, is running Check that the handheld device is able to ping the server on which the Mobile POS Client is installed Check that all the settings in m_pos.ini are correct. The device is not printing. Check the following: The printer is on The IP address for the printer is properly defined in m_pos.ini. The device has an MSR device attached but nothing happens when a card is swiped. Check the following: In the main section of m_pos.ini, check that the MsrDLLName is correctly defined Confirm that the MSR device is attached to the handheld device before launching the thin server and thin client. 5.7 Running Mobile POS After configuring Mobile POS and connecting the handheld device to the host PC, you can begin to operate it. You start Mobile POS by double-clicking the icon on the desktop or by entering Start and then Run. Procedure 1. On the host version of the POS, set Manager Code 6 for the Thin Client CE using the following settings: o Terminal ID = 51. The current configuration supports a maximum of 4 terminal IDs. The remaining 3 can be set to 52, 53, and 54 respectively o Report Group: No change is required to this parameter o Parm Group: No change is required to this parameter unless you are running the POS and Mobile POS Client with different menus. Consult your technical analyst if you require any changes to a Parm Group o Is Thin Server = Yes o Enter Pacing MS = 10 o Display Popup = Yes o Thin Client Type = Mobile CE POS o Listen Socket Number = This value increases by 1 for each additional terminal ID. For example, this setting is 4001 for Terminal ID SAP SE or an SAP affiliate company. All rights reserved. Pre- and Post-

103 2. Double-click the Mobile POS icon on the handheld device. 3. Start Mobile POS Client: o On the Windows status bar of the host POS terminal, select Start and then select Run. The Run dialog box appears o Depending on the type of application that you want to run, enter one of the following in the Open field: o If you are installing the Mobile POS thin client on a system that already has the POS software installed, and you want to use multiple POS systems on one PC, then enter C:\<PROGRAM_FILES>\SAP\Retail Systems\mpos51\posw.exe. Otherwise enter C:\<PROGRAM_FILES>\SAP\ Retail Systems\Point of Sale\posw.exe. This displays a host version of the POS on your terminal. Or If you installed the emulator, enter C:\ProgramFiles\Windows CE Tools\wce300\MS Pocket PC\emulation\palm300\windows\shell32.exe. o On the host version of the POS, set Manager Code 6 for the Thin Client CE using the following settings: o Terminal ID = 51. The current configuration supports a maximum of 4 terminal IDs. The remaining 3 can be set to 52, 53, and 54 respectively o Report Group: No change is required to this parameter o Parm Group: No change is required to this parameter unless you are running the POS and Mobile POS with different menus. Consult your technical analyst if you require any changes to a Parm Group o Is Thin Server = Yes o Enter Pacing MS = 10 o Display Popup = Yes o Thin Client Type = Mobile CE POS o Listen Socket Number = This value increases by 1 for each additional terminal ID. For example, this setting is 4001 for Terminal ID 52. o Turn on the handheld device. o On the Welcome window, select OK o Double-Click EXIT o Double-Click CEMPOS TWGM to open the Mobile POS application o Select OK at the Connect to Server message. You can now use the Mobile POS. Note A cold boot of the mobile device may cause a reset of the configuration settings. To prevent this, you can export option settings in the WLAN profile manager. Go to Options Export. Choose both export options: Export Options and Export All Profiles. Pre- and Post SAP SE or an SAP affiliate company. All rights reserved. 103

104 5.8 Accessing Help Documentation and Changing the Default Location The Store Configurator component provides direct access to online documentation in the SAP Help Portal from within an application screen or a menu option when you press F1. By default, SAP POS is configured to access online help documentation on the SAP Help Portal. 5.9 Performing the in MSI Silent Mode MSI has the built-in feature to use a transform (.mst file) to customize and perform the installation silently. A transform (.mst file) is a simplified Windows Installer database that contains the differences between two.msi databases. Transforms enable an administrator to apply modified settings to a database when deploying an installation package. Note Applying a transform modifies the installation design and results. Only users with the relevant expertise and a good understanding of the application and environment should run this type of installation. Using the Upgrade.ini File SAP POS provides the capability to perform a silent installation of the upgrade files. This is done using a file called Upgrade.ini. Note The Upgrade.ini must be in the same folder as the MSI installation file. New or Upgrade To perform a new installation or to upgrade from any version from 8.0 to 9.5, run the following command: Msiexec.exe /I <PATH>\<MSI> /L*v <PATHTOLOG> /qn Example Msiexec.exe /I C:\GM\Point of Sale.msi /L*v C:\GM\POS.log /qn Upgrade/Repair from POS v10 Build-to-Build To perform an upgrade or repair from build to-build in version 10.3, run the following command: Msiexec.exe /I <PATH>\<MSI> /L*v <PATHTOLOG> REINSTALLMODE=VAMUS REINSTALL=<FEATURES> /qn The following is a list of parameters for this command: SAP SE or an SAP affiliate company. All rights reserved. Pre- and Post-

105 Component POS = POS Client MPOS = Mobile POS Client BACKOFF = Back office database CFG = Store Configurator POS = POS Client MPOS = Mobile POS Client BACKOFF = Back office database CFG = Store Configurator POS = POS Client MPOS = Mobile POS Client Parameter <FEATURES>= Core_Files, Utilities, Browser, EFT_SERVICE <FEATURES>= ALL <FEATURES>= Core_Files <FEATURES>= Core_Files,ODBC, DBRegistry <FEATURES>= Core_Files, Utilities, Browser, EFT_SERVICE <FEATURES>= ALL <FEATURES>= Core_Files <FEATURES>= Core_Files,ODBC, DBRegistry <FEATURES>= Core_Files, Utilities, Browser, EFT_SERVICE <FEATURES>= ALL Example Msiexec.exe /I C:\GM\Point of Sale.msi /L*v C:\GM\POS.log REINSTALLMODE=VAMUS REINSTALL=Core_Files, Utilities, Browser, EFT_SERVICE /qn 5.10 Integrating SAP POS with File and Message Transfer Functions Many SAP POS customers purchase the SAP POS Store Data Transfer for Retail application to provide the foundation for a secure and integrated retail communications network. To facilitate the integration between these two products, when you install SAP POS, the installation program silently installs the basic client software for file transfer and message transfer. To enable file and message transfer functionality, activate these clients and then configure the file settings to suit your needs as described in the following sections Activating Client Software in SAP POS Procedure 1. Install SAP POS at your head office, back office, and store POS terminal, as described in this guide. 2. Install the SAP POS Store Data Transfer for Retail application at your head office. For more information, see the SAP POS Store Data Transfer for Retail Guide. Pre- and Post SAP SE or an SAP affiliate company. All rights reserved. 105

106 Changing Configuration File Settings At the store level, on your Xpress Server and backup server, change the configuration file settings for two files: client.conf and clientapi.conf. Procedure 1. In the main Xpress Server directory (by default, located at C:\<PROGRAM_FILES>\SAP\Retail Systems\Xpress Server,) locate the NFM and NTM folders. These folders contain the client files. 2. In the NTM folder, locate the Conf folder and then locate the client.conf and clientapi.conf files. 3. Open the client.conf file in a text editor (such as Notepad) and perform the following configurations. Be careful not to add any additional spaces or tabs following the settings that you enter here or the configurations will not work. When you finish configuring the settings, save and close the file. Parameter LISTENADDR LISTENPORT SERVERADDR SERVERPORT ICONNECT Description Enter the IP address of your SAP POS Store Data Transfer for Retail client (application client). This is the same as that of your Xpress Server. This setting is necessary only if you have more than one network card installed. Enter the port used by your application client. This is the same as that of your Xpress Server (the default is port 8300). This setting is necessary only if you have more than one network card installed. Enter the IP address of your application message transfer server. Enter the port used by your application message transfer server (the default is port 8400). If ICONNECT is set to TRUE, when the client is started it immediately tries to make a connection with the server. This eliminates a connection startup delay when a transaction is received and must be sent to the server since the connection is already active. If you want the client to wait until it has a transaction before initiating a connection to the server, set this option to FALSE. ALERT There are different levels of severity when errors occur. Some are recoverable or expected; some are not and can cause a major failure. When a severe error occurs, if an alert command has been configured, the client executes that command. The command can contain a percent sign (%), which is replaced with an error message. This can be used to have the client submit an error message to the executable that starts. Example To execute a program called send with an address as the first parameter and an error message as the second parameter, set this option to ALERT=send [< SAP SE or an SAP affiliate company. All rights reserved. Pre- and Post-

107 Parameter Description address>]%, where the percent sign is replaced with an error message before the client executes the command. TACTIONLOG TACTIONLOGNAME DEBUGLOG Set to TRUE or FALSE, depending on whether or not you want to create a transaction log. If TACTIONLOG is set to TRUE, specify a name for the log (full path and file name). Set to TRUE or FALSE, depending on whether or not you want to create a log for debugging purposes. Recommendation Use this log for problem determination only; do not enable it by default as it decreases performance and uses large amounts of disk space. DEBUGLOGNAME EVENTLOGLEVEL EVENTLOGNAME RASPRI RASSEC INACTIVITYTO If DEBUGLOG is set to TRUE, specify a name for the log (full path and file name). Set the severity level up to which you want events to be logged. Specify a name for the event log (full path and file name). If the client is to access the server via a dial-up connection and you want the client to automatically initiate the RAS connection, set this option to the correct RAS configuration name. When started, the client initiates the RAS connection and waits for it to become active before trying to access the server. If the connection drops the client, it restarts the RAS connection. This is a secondary RAS configuration name. If the client fails to connect using the primary configuration (RASPRI), then it switches and tries to use this one. If this one fails, it switches to the primary. It switches back and forth until a connection is established or stopped. The inactivity time-out option is used to disconnect a RAS connection from the server when transactions are not being transmitted. By default, the client keeps the connection active continuously but in some cases (such as long-distance dial-up connections); this may not be the desired option. This option can be used to have the client drop the connection after a specified number of minutes with no transactions transmitted or received. Set this option to the number of minutes to wait before the time-out occurs. To turn off the inactivity time-out, set the value to 0 (zero). COMPRESSION The client has the ability to compress data to minimize the amount of bandwidth required for transactions. This is especially important for slower dial-up connections. Keep in mind that on fast connections, such as Ethernet, compressing small transactions may hinder instead of help. Set to TRUE or FALSE, depending on whether or not you want to use compression for the transfer. Although most transactions compress to Pre- and Post SAP SE or an SAP affiliate company. All rights reserved. 107

108 Parameter Description some extent, others do not. If compression does not produce a smaller transaction, then that transaction is sent uncompressed. COMPRESSION% If COMPRESSION is set to TRUE, specify the minimum percent of space (compression) that must be saved when a transaction is compressed. For example, if you set this option to 10 (10%) then a transaction that initially is 100 bytes long must compress to a length of 90 bytes or less. If not, it is sent uncompressed. Do not set this value to an unlikely percentage. To disable this option, set the value to 0 (zero). SERVERSSLTYPE Specify an SSL encryption type for your server (optional). Note If you specify an SSL type here, it must match the settings on your SAP POS Xpress Server. APISSLTYPE Specify an SSL encryption type for your client API (optional). This option specifies whether the client uses SSL when accepting connections from applications using the API. To turn off SSL, specify NONE. Note If you specify an SSL type here, it must match the APISSLTYPE setting in your clientapi.conf file (see the following table). 4. Open the clientapi.conf file in a text editor (such as Notepad) and perform the following configurations. Be careful not to add any additional spaces or tabs following the settings you enter here or the configurations will not work. When you have finished configuring the settings, save and close the file. Parameter APIID Description Set a unique API ID that is inserted into every transaction that is sent by the API. This ID can be used to locate and track transactions generated by a specific copy of an application. This ID should be unique throughout the entire network. Specify a numeric value from 1 to 232; for example, APIID=1. To indicate that no ID is to be used, set the value to 0 (zero). CLIENTADDR CLIENTPORT TIMEOUT Enter the IP address of your SAP POS Store Data Transfer for Retail client (application client). This is the same as that of your Xpress Server. Enter the port used by your application client. This is the same as that of your Xpress Server (the default is port 8300). When a transaction is sent, a response is generated and sent back to the application via the API. A response is expected to arrive at the API within a specified amount of time. The default time is 10 seconds. If the response is not received within the time-out period, then an alert is sent to the application. Use this parameter to change the time-out period from the default 10 seconds SAP SE or an SAP affiliate company. All rights reserved. Pre- and Post-

109 Parameter ALERT Description There are different levels of severity when errors occur. Some are recoverable or expected; some are not and can cause a major failure. When a severe error occurs, if an alert command has been configured, the client executes that command. The command can contain a percent sign (%), which is replaced with an error message. This can be used to have the client submit an error message to the executable that starts. Example To execute a program called send with an address as the first parameter and an error message as the second parameter, set this option to ALERT=send [< address>]%, where the percent sign is replaced with an error message before the client executes the command. AUTORECONNECT TACTIONLOG TACTIONLOGNAME DEBUGLOG This option allows the API to reconnect automatically to the client if the connection is lost. This prevents the application from having to stop and reestablish the connection via the API on its own. Set to TRUE or FALSE, depending on whether or not you want to create a transaction log. If TACTIONLOG is set to TRUE, specify a name for the log (full path and file name). Set to TRUE or FALSE, depending on whether not you want to create a log for debugging purposes. Recommendation Use this log for problem determination only; do not enable it by default as it decreases performance and uses large amounts of disk space. DEBUGLOGNAME EVENTLOGLEVEL EVENTLOGNAME APISSLTYPE If DEBUGLOG is set to TRUE, specify a name for the log (full path and file name). Set the severity level up to which you want events to be logged. Specify a name for the event log (full path and file name). Specify an SSL encryption type for your client API (optional). This option specifies whether or not the client uses SSL when accepting connections from applications using the API. To turn off SSL, specify NONE. Note If you specify an SSL type here, it must match the APISSLTYPE setting in your client.conf file (see the table in step 3). COMPRESSION The client has the ability to compress data to minimize the amount of bandwidth required for transactions. This is especially important for slower dial-up connections. Keep in mind that on fast connections, such as Ethernet, compressing small transactions may hinder instead of help. Pre- and Post SAP SE or an SAP affiliate company. All rights reserved. 109

110 Parameter Description Set to TRUE or FALSE, depending on whether or not you want to use compression in your API information transfer. Although most transactions compress to some extent, others will not. If compression does not produce a smaller transaction, then that transaction is sent uncompressed. COMPRESSION% If COMPRESSION is set to TRUE, specify the minimum percent of space (compression) that must be saved when a transaction is compressed. For example, if you set this option to 10 (10%) then a transaction that initially is 100 bytes long must compress to a length of 90 bytes or less. If not, it is sent uncompressed. Do not set this value to an unlikely percentage. To disable this option, set the value to 0 (zero) Using the Security Key File If security is enabled, during the head office installation, the user can choose to use the key that is previously generated or let the system to create the key. In order for the store applications to share the key, the user has to export the key from the key container at the head office server after the installation and transport it to the computer where the store applications are installed, then import to its key container. The export of the key can be completed by using the command-line: twsecurityinstall -export -appname TWGM -keyfile <keyfile> where <keyfile> is the full path name of keyfile name selected by the user. The import of the key can be completed by using the command-line: twsecurityinstall -import -appname TWGM -keyfile <keyfile> where <keyfile> is the full path name of keyfile name selected by the user. The import is done automatically if the user provides the keyfile and its corresponding password during the installation of the store applications. After the import of the key, the key is not active. The user has to perform the following procedure to activate the key. Procedure 1. Get the token ID of the key by using the command-line: twsecurityinstall -listkeys -appname TWGM The command lists the keys in the key container. The user can copy the security key token of the key from the output. 2. Map the key to the APPLICATION (APP) channel by using the command-line: twsecurityinstall -createmapping -appname TWGM channelid APP token <tokenid> where <tokenid> is the security key token of the key copied from the output of step Activate the key by using the command-line: twsecurityinstall -updatekey -appname TWGM token <tokenid> -status AC SAP SE or an SAP affiliate company. All rights reserved. Pre- and Post-

111 where <tokenid> is the security key token of the key copied from the output of step 1. Note that by making a key active (AC) will turn the current active key for the channel to expired state. 4. Confirm the key is active by using the command-line: twsecurityinstall -listkeys -appname TWGM The command lists the keys in the key container. The status corresponding to the security key token copied from step 1 should be ACTIVE. Pre- and Post SAP SE or an SAP affiliate company. All rights reserved. 111

112 6 Additional Information 6.1 Removing POS 2.3 When running Windows 2008 and/or Windows 7, administrative privileges are required by the installer. Use the Run As Administrator command to elevate your privileges. Refer to Microsoft documentation for more information on elevating privileges. There are two types of installations: store solution and head office. When you select a store solution installation, the following components are available to be removed: Database Tools Xpress Server database Electronic Journal Viewer database Xpress Server Electronic Journal Viewer Store Manager Point-of-Sale (POS) Client Mobile POS Client. When you select a head office installation, the following components are available to be removed: Database Tools Store Configurator Software Development Kit. Once you select a component to install, the Program Maintenance window appears. Select Remove to uninstall the component. Removing Folders not Removed by the Installer Note If you remove the entire product suite, some folders used for the backup and log files must be removed manually. If you decide to remove the entire product suite, remove the folder and the subfolders after removing all of the components: C:\Program Files\SAP\Retail Systems or on 64-bit system: C:\Program Files (x86)\sap\retail Systems And C:\ProgramData\sap\Retail Systems SAP SE or an SAP affiliate company. All rights reserved. Additional Information

113 Removing Registry Entries not Removed by the Installer This is required only if you are reinstalling POS 2.3 on the same system. Use the registry editor to remove the residual entries in Retail Systems if they were not removed after uninstalling POS 2.3. Note If the POS Store Data Transfer for Retail application is used, do not remove the entry Retail Systems\ Transnet. On a 32-bit operating system remove the registry entry and the sub keys and values: HKEY_LOCAL_MACHINE\SOFTWARE\SAP or on a 64-bit system remove the registry entry and the sub keys and values. The registry entries are in the following location: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SAP For more information, see the SAP Point-of-Sale Security Guide. Additional Information 2016 SAP SE or an SAP affiliate company. All rights reserved. 113

114 7 Appendix 7.1 Legal Software Terms Terms for Included Open Source Software This document contains information respecting free and open-source software (collectively, FOSS ) included in or provided with the product ( Product ) that this document accompanies. Any terms, conditions, and restrictions governing the use or distribution of FOSS that are offered or imposed by SAP and are not contained within the FOSS license(s) governing the use and distribution of the FOSS, are offered and imposed by SAP alone. The authors, licensors, and distributors of the FOSS have disclaimed all warranties relating to any liability arising from the use and distribution of the FOSS. While SAP has sought to provide a complete and accurate listing of the FOSS components included in or provided with the Product, SAP does not represent or warrant that the listing of FOSS components and associated notices and licensing information provided herein are complete or error-free. Recipients of the Product should investigate the listed FOSS components to confirm the accuracy of the notices and licensing information provided herein. Recipients are encouraged to notify SAP of any inaccurate information or errors found in this document. If you have any questions or concerns please contact SAP by at opensource@sap.com or via mail at Dietmar Hopp Allee 16, Walldorf, Germany, Attn: Global Legal. Mozilla SpiderMonkey Licensor: Mozilla Developer Network and individual contributorswebsite: developer.mozilla.org/en- US/docs/Mozilla/Projects/SpiderMonkeyLicense: Mozilla Public License version 2.0 Component: Mozilla SpiderMonkey Licensor: Mozilla Developer Network and individual contributors Website: License: Mozilla Public License version Definitions 1. Contributor means each individual or legal entity that creates, contributes to the creation of, or owns Covered Software. 2. Contributor Version means the combination of the Contributions of others (if any) used by a Contributor and that particular Contributor s Contribution. 3. Contribution means Covered Software of a particular Contributor. 4. Covered Software means Source Code Form to which the initial Contributor has attached the notice in Exhibit A, the Executable Form of such Source Code Form, and Modifications of such Source Code Form, in each case including portions thereof. 5. Incompatible With Secondary Licenses SAP SE or an SAP affiliate company. All rights reserved. Appendix

115 means 1. that the initial Contributor has attached the notice described in Exhibit B to the Covered Software; or 2. that the Covered Software was made available under the terms of version 1.1 or earlier of the License, but not also under the terms of a Secondary License. 6. Executable Form means any form of the work other than Source Code Form. 7. Larger Work means a work that combines Covered Software with other material, in a separate file or files, that is not Covered Software. 8. License means this document. 9. Licensable means having the right to grant, to the maximum extent possible, whether at the time of the initial grant or subsequently, any and all of the rights conveyed by this License. 10. Modifications means any of the following: 1. any file in Source Code Form that results from an addition to, deletion from, or modification of the contents of Covered Software; or 2. any new file in Source Code Form that contains any Covered Software. 11. Patent Claims of a Contributor means any patent claim(s), including without limitation, method, process, and apparatus claims, in any patent Licensable by such Contributor that would be infringed, but for the grant of the License, by the making, using, selling, offering for sale, having made, import, or transfer of either its Contributions or its Contributor Version. 12. Secondary License means either the GNU General Public License, Version 2.0, the GNU Lesser General Public License, Version 2.1, the GNU Affero General Public License, Version 3.0, or any later versions of those licenses. 13. Source Code Form means the form of the work preferred for making modifications. 14. You (or Your ) means an individual or a legal entity exercising rights under this License. For legal entities, You includes any entity that controls, is controlled by, or is under common control with You. For purposes of this definition, control means (a) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (b) ownership of more than fifty percent (50%) of the outstanding shares or beneficial ownership of such entity. 2. License Grants and Conditions 1. Grants Each Contributor hereby grants You a world-wide, royalty-free, non-exclusive license: 1. under intellectual property rights (other than patent or trademark) Licensable by such Contributor to use, reproduce, make available, modify, display, perform, distribute, and otherwise exploit its Contributions, either on an unmodified basis, with Modifications, or as part of a Larger Work; and 2. under Patent Claims of such Contributor to make, use, sell, offer for sale, have made, import, and otherwise transfer either its Contributions or its Contributor Version. 2. Effective Date Appendix 2016 SAP SE or an SAP affiliate company. All rights reserved. 115

116 The licenses granted in Section 2.1 with respect to any Contribution become effective for each Contribution on the date the Contributor first distributes such Contribution. 3. Limitations on Grant Scope The licenses granted in this Section 2 are the only rights granted under this License. No additional rights or licenses will be implied from the distribution or licensing of Covered Software under this License. Notwithstanding Section 2.1(b) above, no patent license is granted by a Contributor: 1. for any code that a Contributor has removed from Covered Software; or 2. for infringements caused by: (i) Your and any other third party s modifications of Covered Software, or (ii) the combination of its Contributions with other software (except as part of its Contributor Version); or 3. under Patent Claims infringed by Covered Software in the absence of its Contributions. This License does not grant any rights in the trademarks, service marks, or logos of any Contributor (except as may be necessary to comply with the notice requirements in Section 3.4). 4. Subsequent Licenses No Contributor makes additional grants as a result of Your choice to distribute the Covered Software under a subsequent version of this License (see Section 10.2) or under the terms of a Secondary License (if permitted under the terms of Section 3.3). 5. Representation Each Contributor represents that the Contributor believes its Contributions are its original creation(s) or it has sufficient rights to grant the rights to its Contributions conveyed by this License. 6. Fair Use This License is not intended to limit any rights You have under applicable copyright doctrines of fair use, fair dealing, or other equivalents. 7. Conditions Sections 3.1, 3.2, 3.3, and 3.4 are conditions of the licenses granted in Section Responsibilities 1. Distribution of Source Form All distribution of Covered Software in Source Code Form, including any Modifications that You create or to which You contribute, must be under the terms of this License. You must inform recipients that the Source Code Form of the Covered Software is governed by the terms of this License, and how they can obtain a copy of this License. You may not attempt to alter or restrict the recipients rights in the Source Code Form. 2. Distribution of Executable Form If You distribute Covered Software in Executable Form then: 1. such Covered Software must also be made available in Source Code Form, as described in Section 3.1, and You must inform recipients of the Executable Form how they can obtain a copy of such Source Code Form by reasonable means in a timely manner, at a charge no more than the cost of distribution to the recipient; and 2. You may distribute such Executable Form under the terms of this License, or sublicense it under different terms, provided that the license for the Executable Form does not attempt to limit or alter the recipients rights in the Source Code Form under this License. 3. Distribution of a Larger Work You may create and distribute a Larger Work under terms of Your choice, provided that You also comply with the requirements of this License for the Covered Software. If the Larger Work is a combination of Covered Software with a work governed by one or more Secondary Licenses, and the Covered Software is SAP SE or an SAP affiliate company. All rights reserved. Appendix

117 not Incompatible With Secondary Licenses, this License permits You to additionally distribute such Covered Software under the terms of such Secondary License(s), so that the recipient of the Larger Work may, at their option, further distribute the Covered Software under the terms of either this License or such Secondary License(s). 4. Notices You may not remove or alter the substance of any license notices (including copyright notices, patent notices, disclaimers of warranty, or limitations of liability) contained within the Source Code Form of the Covered Software, except that You may alter any license notices to the extent required to remedy known factual inaccuracies. 5. Application of Additional Terms You may choose to offer, and to charge a fee for, warranty, support, indemnity or liability obligations to one or more recipients of Covered Software. However, You may do so only on Your own behalf, and not on behalf of any Contributor. You must make it absolutely clear that any such warranty, support, indemnity, or liability obligation is offered by You alone, and You hereby agree to indemnify every Contributor for any liability incurred by such Contributor as a result of warranty, support, indemnity or liability terms You offer. You may include additional disclaimers of warranty and limitations of liability specific to any jurisdiction. 4. Inability to Comply Due to Statute or Regulation If it is impossible for You to comply with any of the terms of this License with respect to some or all of the Covered Software due to statute, judicial order, or regulation then You must: (a) comply with the terms of this License to the maximum extent possible; and (b) describe the limitations and the code they affect. Such description must be placed in a text file included with all distributions of the Covered Software under this License. Except to the extent prohibited by statute or regulation, such description must be sufficiently detailed for a recipient of ordinary skill to be able to understand it. 5. Termination 1. The rights granted under this License will terminate automatically if You fail to comply with any of its terms. However, if You become compliant, then the rights granted under this License from a particular Contributor are reinstated (a) provisionally, unless and until such Contributor explicitly and finally terminates Your grants, and (b) on an ongoing basis, if such Contributor fails to notify You of the noncompliance by some reasonable means prior to 60 days after You have come back into compliance. Moreover, Your grants from a particular Contributor are reinstated on an ongoing basis if such Contributor notifies You of the non-compliance by some reasonable means, this is the first time You have received notice of non-compliance with this License from such Contributor, and You become compliant prior to 30 days after Your receipt of the notice. 2. If You initiate litigation against any entity by asserting a patent infringement claim (excluding declaratory judgment actions, counter-claims, and cross-claims) alleging that a Contributor Version directly or indirectly infringes any patent, then the rights granted to You by any and all Contributors for the Covered Software under Section 2.1 of this License shall terminate. 3. In the event of termination under Sections 5.1 or 5.2 above, all end user license agreements (excluding distributors and resellers) which have been validly granted by You or Your distributors under this License prior to termination shall survive termination. 6. Disclaimer of Warranty Covered Software is provided under this License on an as is basis, without warranty of any kind, either expressed, implied, or statutory, including, without limitation, warranties that the Covered Software is free of defects, merchantable, fit for a particular purpose or non-infringing. The entire risk as to the quality and performance of the Covered Software is with You. Should any Covered Software prove defective in any respect, You (not any Contributor) assume the cost of any necessary servicing, repair, or correction. This Appendix 2016 SAP SE or an SAP affiliate company. All rights reserved. 117

118 disclaimer of warranty constitutes an essential part of this License. No use of any Covered Software is authorized under this License except under this disclaimer. 7. Limitation of Liability Under no circumstances and under no legal theory, whether tort (including negligence), contract, or otherwise, shall any Contributor, or anyone who distributes Covered Software as permitted above, be liable to You for any direct, indirect, special, incidental, or consequential damages of any character including, without limitation, damages for lost profits, loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses, even if such party shall have been informed of the possibility of such damages. This limitation of liability shall not apply to liability for death or personal injury resulting from such party s negligence to the extent applicable law prohibits such limitation. Some jurisdictions do not allow the exclusion or limitation of incidental or consequential damages, so this exclusion and limitation may not apply to You. 8. Litigation Any litigation relating to this License may be brought only in the courts of a jurisdiction where the defendant maintains its principal place of business and such litigation shall be governed by laws of that jurisdiction, without reference to its conflict-of-law provisions. Nothing in this Section shall prevent a party s ability to bring cross-claims or counter-claims. 9. Miscellaneous This License represents the complete agreement concerning the subject matter hereof. If any provision of this License is held to be unenforceable, such provision shall be reformed only to the extent necessary to make it enforceable. Any law or regulation which provides that the language of a contract shall be construed against the drafter shall not be used to construe this License against a Contributor. 10. Versions of the License 1. New Versions Mozilla Foundation is the license steward. Except as provided in Section 10.3, no one other than the license steward has the right to modify or publish new versions of this License. Each version will be given a distinguishing version number. 2. Effect of New Versions You may distribute the Covered Software under the terms of the version of the License under which You originally received the Covered Software, or under the terms of any subsequent version published by the license steward. 3. Modified Versions If you create software not governed by this License, and you want to create a new license for such software, you may create and use a modified version of this License if you rename the license and remove any references to the name of the license steward (except to note that such modified license differs from this License). 4. Distributing Source Code Form that is Incompatible With Secondary Licenses If You choose to distribute Source Code Form that is Incompatible With Secondary Licenses under the terms of this version of the License, the notice described in Exhibit B of this License must be attached. Exhibit A - Source Code Form License Notice This Source Code Form is subject to the terms of the Mozilla Public License, v If a copy of the MPL was not distributed with this file, You can obtain one at If it is not possible or desirable to put the notice in a particular file, then You may include the notice in a location (such as a LICENSE file in a relevant directory) where a recipient would be likely to look for such a notice SAP SE or an SAP affiliate company. All rights reserved. Appendix

119 You may add additional accurate notices of copyright ownership. Exhibit B - Incompatible With Secondary Licenses Notice This Source Code Form is Incompatible With Secondary Licenses, as defined by the Mozilla Public License, v Component: zlib Licensor: Jean-loup Gailly and Mark Adler Website: License: Copyright (C) Jean-loup Gailly and Mark Adler zlib.h -- interface of the 'zlib' general purpose compression library version 1.2.8, April 28th, 2013 Copyright (C) Jean-loup Gailly and Mark Adler This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software. Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions: 1. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required. 2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software. 3. This notice may not be removed or altered from any source distribution. Jean-loup Gailly Mark Adler jloup@gzip.org madler@alumni.caltech.edu Component: STLPort Licensor: Boris Fomitchev WebSite: License Agreement Boris Fomitchev grants Licensee a non-exclusive, non-transferable, royalty-free license to use STLportand its documentation without fee. By downloading, using, or copying STLport or any portion thereof, Licensee agrees to abide by the intellectual property laws and all other applicable laws of the United States of America, and to all of the terms and conditions of this Agreement. Licensee shall maintain the following copyright and permission notices on STLport sources and its documentation unchanged : Copyright 1999,2000 Boris Fomitchev Appendix 2016 SAP SE or an SAP affiliate company. All rights reserved. 119

120 This material is provided "as is", with absolutely no warranty expressed or implied. Any use is at your own risk. Permission to use or copy this software for any purpose is hereby granted without fee, provided the above notices are retained on all copies. Permission to modify the code and to distribute modified code is granted, provided the above notices are retained, and a notice that the code was modified is included with the above copyright notice. The Licensee may distribute binaries compiled with STLport (whether original or modified) without any royalties or restrictions. The Licensee may distribute original or modified STLport sources, provided that: The conditions indicated in the above permission notice are met; The following copyright notices are retained when present, and conditions provided in accompanying permission notices are met : Copyright 1994 Hewlett-Packard Company Copyright 1996,97 Silicon Graphics Computer Systems, Inc. Copyright 1997 Moscow Center for SPARC Technology. Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Hewlett-Packard Company makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty. Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Silicon Graphics makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty. Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Moscow Center for SPARC Technology makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty. Flexler 1.18 Copyright (c) 1993 The Regents of the University of California. All rights reserved. This code is derived from software contributed to Berkeley by Kent Williams and Tom Epperly. Redistribution and use in source and binary forms are permitted provided that: (1) source distributions retain this entire copyright notice and comment, and (2) distributions including binaries display the following acknowledgement: ``This product includes software developed by the University of California, Berkeley and its contributors'' in the documentation or other materials provided with the distribution and in all advertising materials mentioning features or use of this software. Neither the name of the University nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE SAP SE or an SAP affiliate company. All rights reserved. Appendix

121 Appendix 2016 SAP SE or an SAP affiliate company. All rights reserved. 121

122 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies. Please see for additional trademark information and notices.