SAP Enterprise Point-of-Sale 3.1 SP07

Transcription

1 PUBLIC Upgrade Guide SAP Enterprise Point-of-Sale 3.1 SP07 Target Audience System administrators Technology consultants Document version: February, 2012

2 SAP AG Dietmar-Hopp-Allee Walldorf Germany T +49/18 05/ F +49/18 05/ Copyright Copyright 2012 SAP AG. All rights reserved. SAP Library document classification: PUBLIC No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iseries, pseries, xseries, zseries, eserver, z/vm, z/os, i5/os, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, Clear Enterprise, SAP BusinessObjects Explorer, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP France in the United States and in other countries. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty Disclaimer Some components of this product are based on Java. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components. Any Java Source Code delivered with this product is only to be used by SAP s Support Services and may not be modified or altered in any way Documentation in the SAP Service Marketplace You can find this documentation at the following address:

3 Typographic Conventions Icons Type Style Example Text Example text EXAMPLE TEXT Example text Example text <Example text> EXAMPLE TEXT Description Words or characters quoted from the screen. These include field names, screen titles, pushbutton labels, menu names, menu paths, and menu options. Cross-references to other documentation Emphasized words or phrases in body text, graphic titles, and table titles 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. Keys on the keyboard, for example, F2 or ENTER. Icon Meaning Caution Example Note Recommendation Syntax Additional icons are used in SAP Library documentation to help you identify different types of information at a glance. For more information, see Help on Help General Information Classes and Information Classes for Business Information Warehouse on the first page of any version of SAP Library.

4 Contents 1 Introduction Document History About this Document Overview Guiding Principles Levels of Upgrades Upgrade Context Procedures Preparing for the Upgrade System Requirements Preparing Installation Image Repository Performing a Pre-Upgrade Upgrade Upgrading the Head Office Upgrading the Store Upgrading the POS Registers Post-Upgrade Operations Troubleshooting Reference February 2012

5 1 Introduction This section provides introductory information that you need to know before you begin upgrading SAP Enterprise Point-of-Sale (SAP Enterprise POS). 1.1 Document History The following table provides an overview of the most important document changes. Version Description 1.00 First version no changes 1.01 SAP Enterprise POS 3.1 SP01 (note the guide was neither changed nor released for SP02) 1.02 SAP Enterprise POS 3.1 SP SAP Enterprise POS 3.1 SP SAP Enterprise POS 3.1 SP SAP Enterprise POS 3.1 SP SAP Enterprise POS 3.1 SP About this Document Purpose This guide provides step-by-step instructions for upgrading SAP Enterprise POS. It is intended for SAP or SAP-Approved system administrators and technology consultants. 2 Overview 2.1 Guiding Principles The following are the core principles of the SAP Enterprise POS upgrade process Phased Upgrading for Multiple Stores An upgrade can be performed selectively. For example, you may not want to upgrade all of the stores but only a group of stores at the same time in a staged approach External Systems Decoupled from Upgrades There is minimal impact if there are changes to the interface specification between an external system and SAP Enterprise POS Complete and Unattended Upgrade at Stores For a normal upgrade, store or corporate administrative personnel must provide minimal manual intervention. February

6 2.1.4 Best Practice The store upgrade must be performed after a successful head office upgrade. Before the upgrade, the middleware (IBM DB2, IBM MQ, and IBM WebSphere application server) must work properly on the server to be upgraded. The system time of the servers involved in the upgrade process must be synchronized. 2.2 Levels of Upgrades Upgrades come with three levels of significance, and one approach is not suitable for all three levels. The following levels of upgrades are possible: Patches Involve minimal changes for a simple upgrade and involve no data loss. A patch is applied to an existing installation and it updates the code without breaking any interfaces. Also, the data can be updated in place, without having to be moved. Standard upgrades Involve significant changes that may require adjustments and data conversion and involve no data loss. Exceptional upgrades Involve significant changes that you cannot handle as a standard upgrade. An exceptional upgrade requires greater effort to convert from one version to another. You must perform an exceptional upgrade when one of the following conditions exists: There is no established upgrade between the two versions. Either the prior version is an older version than what is supported by upgrades to the current version, or the prior version is a customer-specific version for which a standard upgrade has not been implemented. The interfaces (for example, JMS, RMI, database, or configuration) between the prior version and the new version cannot be made compatible. This incompatibility must prevent interaction between systems running the two versions. Data loss would be encountered when using a standard upgrade approach. Data loss can occur when the prior version contains data that has no equivalent storage possibility in the new version, or for which there is no consistent way of converting the data. In general, this must be avoided if possible, but there could be situations where it is unavoidable. There are significant changes in the middleware or the whole operating system needs to be changed or upgraded. The terms patch, standard upgrade, and exceptional upgrade are not correlated with the patch, minor and major software version levels, or releases. The terms reflect the level of effort required to create and apply the upgrade, and the impact that the upgrade has on the system. A patch release may be applied by either a patch upgrade or standard upgrade, and a major or minor version release may be applied by a patch, standard, or exceptional upgrade. 6 February 2012

7 2.2.1 Patches Generally, to apply a patch upgrade, you perform an in-place data upgrade and replace the existing JAR files with ones containing the new version, regardless of the type of system (head office or store). A patch upgrade requires the patched system to be fully compatible with any other system with which it interacts, including internal (head office or store) systems and external systems Standard Upgrade For a standard upgrade, there may be interface changes that you need to handle, which you can do using a standard approach. While the data upgrade might take some time and effort, it can be accomplished in a standard manner. To perform a standard upgrade, you perform a data and configuration upgrade. This can include schema as well as content conversion. Rather than inserting the complete, new set of code for both the enterprise application and the standalone utilities, you apply any middleware changes that are required, and deploy the new enterprise application Exceptional Upgrade An exceptional upgrade can be handled in part using a standard upgrade, but it could have some aspects that require customization (at least when it is created). It may require a completely different approach if the differences are too significant. You can accomplish an exceptional upgrade in many ways. The simplest is a customized form of a standard upgrade. Another, more complex, method is the migration approach, where the old and new versions are run in parallel and in isolation, while stores are converted to run the newer version. 2.3 Upgrade Context The context in which upgrades must operate can vary for each retailer. For some retailers, SAP Enterprise POS owns the store and POS client systems, and must manage the whole process of distribution, scheduling, and application of the updates. For other retailers, SAP Enterprise POS is one of a set of applications used by the stores, so the SAP Enterprise POS upgrade must be coordinated with upgrades to other systems, which can include distribution, scheduling, and application, by these other upgrades. SAP Enterprise POS 3.1 runs on IBM s WebSphere Remote Server (WRS), and the technical context for upgrades is a WRS environment. The upgrades are managed using Tivoli Provisioning Manager (TPM). If SAP Enterprise POS is one of many of the retailer s store applications, it is expected that the coordination with these other systems is managed using TPM. 2.4 Procedures The SAP Enterprise POS SP07 release runs on a new software stack based on the IBM WebSphere Remote Server product as well as new operating systems that were not previously supported by the SAP Enterprise POS SP06 release (see the SAP Enterprise Point-of-Sale 3.1 SP07 Installation Guide for more information on the supported operating systems). That makes upgrading to the SAP Enterprise POS SP07 an exceptional upgrade type. Because of the new system requirements, an existing installation of SAP Enterprise POS SP06 can not be upgraded and instead must be replaced by new SAP Enterprise POS SP07 servers and clients. Migration utilities are provided to move data from an old installation to a new installation where necessary. February

8 There are many views and levels of process flow to be considered for an upgrade. The following provides an explanation of the context in which upgrades are expected to operate, and the expected flow of the processing from different perspectives Logistics View From a logistics perspective, updates are applied to a retailer s enterprise in a sequence resembling the one below: 1. Upgrade all enterprise systems that must handle new versions of interfaces for data received from SAP Enterprise POS (for example, TLogs and services). This step is not required by the 3.1 SP07 upgrade. 2. Upgrade the POS head office system. This upgrade can be done in isolation to allow for detection of any issues that it might cause, or it can be done during the next step. 3. Upgrade the POS store system and terminals at a single store or a small set of stores. This is often called a pilot, and is typically followed by an assessment period to determine whether the new version is working successfully or not. Sometimes, you repeat this type of upgrade for different stores, or groups of stores, that have different characteristics. 4. Upgrade a large group of stores. This is the beginning of what is called the rollout, and is repeated until all stores are updated. 5. Any time after or during step two above, you can update any enterprise system that feeds new data to the POS that was not handled by the previous version. This strategy allows the retailer to detect any critical issues as soon as possible and, if needed, roll back the update for the affected systems Head Office Level Procedures At the retailer s head office (the location, not just the server), perform the following tasks: 1. Prepare the TPM server for upgrades: a. Place the SAP Enterprise POS 3.1 SP07 software distribution and all other required software on the TPM server (for more information, see the SAP Enterprise Point-of-Sale 3.1 SP07 Installation Guide). b. Customize the SAP Enterprise POS 3.1 SP07 distribution with the security setting from the previous installation, repackage it, generate new software installable - Software Package Blocks (SPBs), and install them on the TPM server. 2. Load enterprise deployment and configuration data in the TPM database. 3. Apply the head office system upgrade: a. Install the SAP Enterprise POS 3.1 SP07 Head Office on the new head office server following the SAP Enterprise Point-of-Sale 3.1 SP07 Installation Guide. b. Configure all required external services on the SAP Enterprise POS 3.1 SP07 Head Office. c. Backup the SAP Enterprise POS 3.1 SP06 Head Office database. d. Restore SP06 database backup in the SAP Enterprise POS 3.1 SP07 Head Office database. e. Configure WebSphere Application Server at the SAP Enterprise POS 3.1 SP06 Head Office to connect to the SAP Enterprise POS 3.1 SP07 Head Office database. Steps a and b can be performed in advance and do not require the SAP Enterprise POS 3.1 SP06 Head Office server outage. Steps c, d, and e must be performed as 8 February 2012

9 one unit of work and require the SAP Enterprise POS 3.1 SP06 Head Office to be stoped until all steps are complete. At the end of the upgrade the WebSphere Application Server at the SAP Enterprise POS 3.1 SP06 Head Office is connected to the SAP Enterprise POS 3.1 SP07 Head Office databse and all transactions from SP06 stores are posted to the new SP07 database. The SAP Enterprise POS 3.1 SP06 Head Office database is only used for data replication to the SP06 stores. 4. Schedule the store system upgrade(s). This is required to synchronize business activities with upgrade steps that must be performed. 5. Schedule the register system installation(s). This is required to synchronize business activities with upgrade steps that must be performed. Apply the register system upgrade Store-Level Procedures Perform the following activities at the stores (the location, not just the server): a. Backup the SAP Enterprise POS 3.1 SP06 Store database. b. Install the SAP SAP Enterprise POS 3.1 SP07 Store on the new or reimaged store server following the SAP Enterprise Point-of-Sale 3.1 SP07 Installation Guide. c. Restore the SP06 database backup in the SAP Enterprise POS 3.1 SP07 Store database. All steps must be completed as one unit of work Register-Level Procedures Perform the following activities at the stores (the location, not just the server): a. Backup the POS Client snapshot from the SAP Enterprise POS 3.1 SP06 register. b. Install the SAP Enterprise POS 3.1 SP07 register on the new or reimaged register following the SAP Enterprise Point-of-Sale 3.1 SP07 Installation Guide. c. Copy the backed up SAP Enterprise POS 3.1 SP06 POS Client snapshots to the SAP Enterprise POS 3.1 SP07 register. 3 Preparing for the Upgrade This section provides information about how to prepare for a successful upgrade of SAP Enterprise POS from version 3.1 SP06 to 3.1 SP07. The software can be acquired by DVD or from the SAP Service Marketplace. 3.1 SAP Notes for the Upgrade and Installation You must read the EPOS Upgrade Troubleshooting SAP Note and the Installation Troubleshooting SAP Note before you start the upgrade. SAP Notes contain the most recent information on the upgrade and installation troubleshooting, as well as corrections to the upgrade and installation documentation. Make sure that you have the upto-date version of the SAP Notes, which you can find on the SAP Service Marketplace at service.sap.com/notes. February

10 3.2 System Requirements Environment Tivoli TPM version 7.2 must be available to deploy SAP Enterprise POS. This server cannot be used to run SAP Enterprise POS, only to deploy it. The previous SAP Enterprise POS 3.1 SP06 build custom directory must be available on the TPM server. If this directory does not exist on the server, it can be copied from the head office server. The previous SAP Enterprise POS 3.1 SP06 must be installed and running. 3.3 Preparing Installation Image Repository Use To prepare the installation image repository. Prerequisites Tivoli TPMfSW is installed and is functioning correctly. Procedure for Linux Environment 1. Perform the steps described in the Preparing Installation Image Repository (Linux TPM) section of the SAP Enterprise Point-of-Sale 3.1 SP07 Installation Guide. 2. As the tioadmin user, copy the custom directory from the SAP Enterprise POS SP06 Head Office server to the TE_INSTALL_ROOT directory on the TPM server. If the custom directory contains the file deployment.properties.orig, it should be deleted. Procedure for Windows Environment 1. Perform the steps described in the Preparing Installation Image Repository (Windows TPM) section of the SAP Enterprise Point-of-Sale 3.1 SP07 Installation Guide. 2. While logged in as the tioadmin user, copy the custom directory from the SAP Enterprise POS SP06 Head Office server to the TE_INSTALL_ROOT directory on the TPM server. If the custom directory contains the file deployment.properties.orig,delete it. 3.4 Performing a Pre-Upgrade Use To generate the installation software packages and install them to the TPM server, perform the appropriate procedure depending on your operating system. Prerequisites The previous steps are complete The environment variable JAVA_HOME must be set to the location of a Java 1.5 Development Kit installation or Java Runtime Environment installation. 10 February 2012

11 Procedure As the TPM tioadmin user, perform the following steps on the TPM server. 1. Navigate to the deployment\upgradebase\upgradecheck directory of the new SAP Enterprise POS 3.1 SP07 build and edit the preconditioncheck.properties file. Check the properties if necessary. The default preconditions are: pos.check=true pos.allowopenterminals=false pos.allowunpostedtransactions=false pos.allowunreconciledtills=false pos.allowmissingbankdeposit=false store.check=true store.allowopen=false Change the setting to true or false to enable or disable the precondition check. 2. Using a command prompt, navigate to the deployment directory of the new SAP Enterprise POS 3.1 SP07 build and execute the preupgrade script. The script requires, as arguments, the path to the previous 3.1 SP06 installation custom directory as a parameter. If default values were used in the previous installation steps the paths are /opt/sap/te/custom and \sap\te\custom on Linux and Windows systems respectively. To start the utility, execute the following command: Linux cd /opt/sap/te/build/deployment sh preupgrade.sh /opt/sap/te/custom Windows cd \sap\te\build\deployment preupgrade.bat \sap\te\custom a. Select the type of topology to use for this installation. b. Choose whether you are deploying the IBM middleware to Windows, Linux sites, or both. Make the selection based on the operating system that is used on the SAP Enterprise POS servers. c. Select if you plan OLC register installations. d. Select if you plan POS register installations. e. Select the operating system types to support for SMD agent installations. Make the selection based on the operating system that is used on the SAP Enterprise POS servers. f. Select the operating system types to support for Wily agent installations. Make the selection based on the operating system that is used on the SAP Enterprise POS servers. g. The preinstall script runs without any further user input. Ensure that the script terminates successfully. h. The preupgrade utility creates a folder named dist in the TE_INSTALL_ROOT directory containg software installable for the SAP Enterprise POS 3.1 SP07 release. After the preupgrade script terminates, make sure that the dist folder contains the files migration.tar and migration.zip which are required for the system upgrade. The migration.tar is used for the Linux servers and the migration.zip is used for the Windows servers. February

12 4 Upgrade The SAP Enterprise POS 3.1 SP07 upgrade consists of the following steps in sequence: Setup a new EPOS SP7 Head Office Server and migrate the data from the EPOS SP06 Head Office Server. For each existing EPOS SP06 Store Server: Setup a new EPOS SP7 Store Server configured to replace the existing EPOS SP06 Store Server. For each existing POS and OLC register configured to use the store server, setup a new POS or OLC register using EPOS SP07. Perform the upgrade in the following sequence: Head Office, Stores, and POS and OLC registers. 4.1 Upgrading the Head Office Use To upgrade the head office server to the new SAP Enterprise POS 3.1 SP07 version. Prerequisites The previous steps are complete TCA agent is running on the server There are no failed transactions to post in the WebSphere Application Server log directory. Procedure 1. Install SAP Enterprise POS 3.1 SP07 Head Office on the new server following the SAP Enterprise Point-of-Sale 3.1 SP07 Installation Guide. It is not necessary to discover and define store and register computers in this step. This step can be performed in advance, prior to taking the SAP Enterprise POS 3.1 SP06 Head Office server off the production environment for upgrade. 2. Configure external services. This step can be performed in advance, prior to taking the SAP Enterprise POS 3.1 SP06 Head Office server off the production environment for upgrade. a. On the Enterprise POS 3.1 SP07 server: Configure the same external services such as MDI, customer service, and TLog posting that are also used by the SAP Enterprise POS 3.1 SP06 Head Office. The configuration procedure is not covered in this Upgrade Guide and should be performed following the service configuration documentation. 3. Restore the database from the SAP Enterprise POS 3.1 SP06 server to the SAP Enterprise POS 3.1 SP07 server and configure SAP Enterprise POS 3.1 SP06 WebSphere Application Server to connect to the SAP Enterprise POS 3.1 SP07 database. On the Linux system the restore steps must be performed by the root user and on the Windows system by a member of the Administrators group. Perform the following steps as one unit of work. Notice that some steps are executed on the Enterprise POS 3.1 SP06 server and some of them are performed on the Enterprise POS 3.1 SP07 server. a. On the Enterprise POS 3.1 SP06 and Enterprise POS 3.1 SP07 servers: 12 February 2012

13 Depending on the operating systems installed on the Enterprise POS 3.1 SP06 and Enterprise POS 3.1 SP07 Head Office servers, extract the content of the migration.tar or migration.zip archive file located in the dist folder of the TE_INSTALL_ROOT directory of the TPM server to any directory on the SAP Enterprise POS 3.1 SP06 and Enterprise POS 3.1 SP07 Head Office servers. On both servers the SP6 folder is in the directory where it was extracted. b. On the Enterprise POS 3.1 SP06 server: Navigate to the SP6 directory and run the migrate script to backup the database and stop all Enterprise POS 3.1 SP06 processes. Provide two command line parameters: backupdb indicating that a database backup is required and the absolute path to the directory where database backup files should be created. For example: Linux sh migrate.sh backupdb /opt/db-backup Windows migrate.bat backupdb \sap\db-backup c. On the Enterprise POS 3.1 SP06 and Enterprise POS 3.1 SP07 servers: Copy database backup files from the SAP Enterprise POS 3.1 SP06 server to the SAP Enterprise POS 3.1 SP07 server to the directory of your choice. d. On the Enterprise POS 3.1 SP07 server: Navigate to the SP6 directory and run the migrate script to restore the database from the backup. Provide three command line parameters: restoredb indicating that a database restore is required, the absolute path to the directory where the SAP Enterprise POS 3.1 SP06 database backup files were copied, and the hostname of the Enterprise POS 3.1 SP06 server. For example: Linux sh migrate.sh restoredb /opt/db-backup SP06-server-hostname Windows migrate.bat restoredb \sap\db-backup SP06-server-hostname e. On the Enterprise POS 3.1 SP06 server: Navigate to the SP6 directory and run the migrate script. Provide two command line parameters: configdb indicating that a WebSphere Application Server database connectivity change is required and the hostname of the Enterprise POS 3.1 SP07 server. For example: Linux sh migrate.sh configdb SP07-server-hostname Windows migrate.bat configdb SP07-server-hostname The migrate script also starts all SAP Enterprise POS 3.1 SP06 processes to make the server available in the production environment. If running the migrate script is not successful, check for errors in the migration.log file located in the same directory. February

14 After upgrading the head office, all SAP Enterprise POS 3.1 SP06 stores must be managed using the POS Manager application deployed on the SAP Enterprise POS 3.1 SP06 Head Office server, and master data must be managed using the MDI service running on that server. All stores upgraded to the SAP Enterprise POS 3.1 SP07 version must be managed using the POS Manager application deployed on the SAP Enterprise POS 3.1 SP07 server. There are no restrictions on the master data management process after the store upgrade. If the SAP Enterprise POS 3.1 SP06 server must be available in a production environment, before the database restore step (2d) is completed, step 2e can be omitted. In this case the SAP Enterprise POS 3.1 SP06 processes can be started by navigating to the SP6 directory on the Enterprise POS 3.1 SP06 server and running the migrate script: Linux sh migrate.sh startepos Windows migrate.bat startepos Steps 2b to 2e must be repeated as one unit of work the next time the SAP Enterprise POS 3.1 SP06 server is available again for upgrade. 4. Perform post upgrade validation of the SAP Enterprise POS 3.1 SP07 and SP06 servers: a. Make sure that all external services are running on both servers. b. If replication service is used, verify that it is running on both servers. See Verify Replication Startup in the SAP Enterprise Point-of-Sale 3.1 SP07 Installation Guide for details. The verification procedure is applicable to both servers. c. Make sure that all WebSphere MQ message channels are running on the Enterprise POS 3.1 SP06 server. See Verify MQ Communication in the SAP Enterprise Point-of- Sale 3.1 SP07 Installation Guide for details. The verification procedure is applicable to the SP06 server. d. Verify WebSphere application server log files for errors on both servers. See Verify WebSphere Application Server Log in the the SAP Enterprise Point-of-Sale 3.1 SP07 Installation Guide for details. The verification procedure is applicable to the both servers. e. Verify Enterprise POS 3.1 SP06 and Enterprise POS 3.1 SP07 application log files for errors. See Troubleshooting in this Upgrade Guide for the log file location. The file location is the same on both servers. 4.2 Upgrading the Store Use To upgrade the store server to the new SAP Enterprise POS 3.1 SP07 version. Prerequisites The previous steps are complete TCA agent is running on the server 14 February 2012

15 There are no failed transactions to post in the WebSphere Application Server log directory. Procedure 1. Backup the SAP Enterprise POS 3.1 SP06 database: a. On the Enterprise POS 3.1 SP06 server: Extract the content of the migration.zip archive file located in the dist folder of the TE_INSTALL_ROOT directory of the TPM server, to any directory on the SAP Enterprise POS 3.1 SP06 store server. The SP6 folder is in the directory where it was extracted. b. On the Enterprise POS 3.1 SP06 server: Navigate to the SP6 directory and run the migrate script to backup the database and stop all Enterprise POS 3.1 SP06 processes. Provide two command line parameters: backupdb indicating that a database backup is required and the absolute path to the directory where database backup files must be created. For example: Windows migrate.bat backupdb \sap\db-backup 2. Install the new SAP Enterprise POS 3.1 SP07 store and restore the database from the backup. a. On the Enterprise POS 3.1 SP07 server: Install the new SAP Enterprise POS 3.1 SP07 store on the server following the SAP Enterprise Point-of-Sale 3.1 SP07 Installation Guide. It is not necessary to descover and define register computers at this time. If you plan to use a new store server this step can be performed in advance, prior to step 1. b. On the Enterprise POS 3.1 SP07 server: Extract the content of the migration.zip archive file located in the dist folder in the TE_INSTALL_ROOT directory on the TPM server, to any directory on the SAP Enterprise POS 3.1 SP07 store server. The SP6 folder is in the directory where it was extracted. c. On the Enterprise POS 3.1 SP07 server: Copy SAP Enterprise POS 3.1 SP06 database backup files to the SAP Enterprise POS 3.1 SP07 server to the directory of your choice. d. On the Enterprise POS 3.1 SP07 server: Navigate to the SP6 directory and run the migrate script to restore the database from the backup. Provide two command line parameters: restoredb defining the action required and the absolute path to the directory where the SAP Enterprise POS 3.1 SP06 database backup files were copied. For example: Windows migrate.bat restoredb \sap\db-backup If running the migrate script is not successful, check for errors in the migration.log file located in the same directory. February

16 After upgrading the store it must be managed using the POS Manager application deployed on the SAP Enterprise POS 3.1 SP07 Head Office. There are no restrictions on the master data management process after the store upgrade. 3. Perform post upgrade validation of the SAP Enterprise POS 3.1 SP07 server: a. If the replication service is used, verrify that it is running. See Verify Replication Startup in the the SAP Enterprise Point-of-Sale 3.1 SP07 Installation Guide for details. b. Make sure that all WebSphere MQ message channels are running. See Verify MQ Communication in the SAP Enterprise Point-of-Sale 3.1 SP07 Installation Guide for details. c. Verify the WebSphere application server log files for errors. See Verify WebSphere Application Server Log in the the SAP Enterprise Point-of-Sale 3.1 SP07 Installation Guide for details. d. Verify the Enterprise POS 3.1 SP07 application log file for errors. See Troubleshooting in this Upgrade Guide for the log file location. e. Wait until the replication service finishes data synchronization with the head office database and verify the EMPLOYEEPASSWORDHISTORY table integrity. Logon to the store server as a member of the Administrators group, start a Windows command prompt, and run the following. Windows db2cmd db2 connect to TE_DFLT db2 SELECT COUNT(*) from EPOS.EMPLOYEEPASSWORDHISTORY db2terminate If the SQL SELECT statement returns an error, see the EPOS Upgrade Troubleshooting SAP Note for details on how to correct the issue. 4.3 Upgrading the POS Registers Use To upgrade the OLC client on the target server. Prerequisites The previous steps are complete You closed the terminal running with the same client ID, and all collected offline transactions are posted to the head office You ended the Enterprise POS client application The TPM server is up and running The TCA agent is running on the register. 16 February 2012

17 Procedure 1. Backup the POS Client tni.snapshot.1 snapshot file located in the %TE_HOME%\posclient directory. The number in the file name can vary depending on the client ID of the register. 2. Install the new SAP Enterprise POS 3.1 SP07 POS or OLC client on the register following the SAP Enterprise Point-of-Sale 3.1 SP07 Installation Guide. 3. Copy the POS Client tni.snapshot.1 snapshot file from the backup to the %TE_HOME%\posclient directory on the new register. 4. Reboot the register. 5 Post-Upgrade Operations After the upgrade is complete at the head office and all stores, the SAP Enterprise POS SP6 Head Office server can be shutdown. All external services configured with the SAP Enterprise POS SP6 Head Office can also be shutdown. 6 Troubleshooting Upgrade Log Files If the head office, store, or register installation fails, see Troubleshooting in the SAP Enterprise Point-of-Sale 3.1 SP07 Installation Guide. If the migrate script fails, evaluate the migration.log file created in the SP6 directory. Linux $TE_HOME/deployment/logs/*.log SAP Enterprise POS SP7 Head Office installation log files on the target server. /opt/ibm/websphere/appserver/profiles/<profilename>/logs/server1/systemout.log WebSphere application server log file on the target server. /opt/ibm/websphere/appserver/profiles/<profilename>/logs/server1/te_server.log SAP Enterprise POS log file on the target server. /opt/tivoli/ep/logs/rcp.log - Tivoli Common Agent log file on the target server. Windows %TE_HOME%\deployment\logs\*.log SAP Enterprise POS SP7 Head Office and store installation log files on the target server. %PROGRAMFILES%\IBM\WebSphere\AppServer\profiles\<profilename>\logs\server1\SystemOut.log WebSphere application server log file on the target server. %PROGRAMFILES%\IBM\WebSphere\AppServer\profiles\<profilename>\logs\server1\te_server.log SAP Enterprise POS log file on the target server. C:\TEMP\OLCInstall\OLCInstall.log OLC client installation process log file on the target server. February

18 C:\TEMP\OLCInstall-logs\ OLC Client SPB installation log files on the target server. TEMP%\POSInstall\POSInstall.log POS client installation process log file on the target server. TEMP%\POSInstall-logs\ POS Client SPB installation log files on the target server. %PROGRAMFILES%\tivoli\ep\logs\rcp.log Tivoli Common Agent log file on the target server. 7 Reference For more information, see the SAP Enterprise Point-of-Sale 3.1 SP07 Installation Guide. 18 February 2012