PUBLIC Upgrade Guide

Upgrade Guide

SAP® Enterprise

Point-of-Sale 3.1SP05

Target Audience

System administrators

Technology consultants

Document version: 1.04 – April 30, 2010

PUBLIC

© Copyright 2010 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in anyform or for any purpose without the express permission of SAP AG.The information contained herein may be changed without priornotice.

Some software products marketed by SAP AG and its distributorscontain proprietary software components of other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registeredtrademarks of Microsoft Corporation.IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex,MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries,xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity,Tivoli, Informix, i5/OS, POWER, POWER5, OpenPower andPowerPC are trademarks or registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are eithertrademarks or registered trademarks of Adobe Systems Incorporated inthe 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 theOpen Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,VideoFrame, and MultiWin are trademarks or registered trademarks ofCitrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registeredtrademarks of W3C®, World Wide Web Consortium, MassachusettsInstitute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., usedunder license for technology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, andother SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AGin Germany and in several other countries all over the world. All otherproduct and service names mentioned are the trademarks of theirrespective companies. Data contained in this document servesinformational purposes only. National product specifications mayvary.

These materials are subject to change without notice. These materialsare provided by SAP AG and its affiliated companies ("SAP Group")for informational purposes only, without representation or warranty ofany kind, and SAP Group shall not be liable for errors or omissionswith respect to the materials. The only warranties for SAP Groupproducts and services are those that are set forth in the expresswarranty statements accompanying such products and services, if any.Nothing herein should be construed as constituting an additionalwarranty.

DisclaimerSome components of this product are based on Java™. Any codechange in these components may cause unpredictable and severemalfunctions and is therefore expressively prohibited, as is anydecompilation of these components.

Any Java™ Source Code delivered with this product is only to be usedby SAP’s Support Services and may not be modified or altered in anyway.

Documentation in the SAP Service MarketplaceYou can find this documentation at the following address:http://service.sap.com/instguides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 24F +49/18 05/34 34 20www.sap.com

http://service.sap.com/instguides

Typographic Conventions

Type Style Description

Example Text Words or characters quotedfrom the screen. These includefield names, screen titles,pushbutton labels, menunames, menu paths, and menuoptions.

Cross-references to otherdocumentation

Example text Emphasized words or phrasesin body text, graphic titles, andtable titles

EXAMPLE TEXT Technical names of systemobjects. These include reportnames, program names,transaction codes, tablenames, and key concepts of aprogramming language whenthey are surrounded by bodytext, for example, SELECT andINCLUDE.

Example text Output on the screen. Thisincludes file and directorynames and their paths,messages, names of variablesand parameters, source text,and names of installation,upgrade and database tools.

Example text Exact user entry. These arewords or characters that youenter in the system exactly asthey appear in thedocumentation.

<Exampletext>

Variable user entry. Anglebrackets indicate that youreplace these words andcharacters with appropriateentries to make entries in thesystem.

EXAMPLE TEXT Keys on the keyboard, forexample, F2 or ENTER.

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Additional icons are used in SAP Librarydocumentation to help you identify differenttypes of information at a glance. For moreinformation, see Help on Help GeneralInformation Classes and Information Classesfor Business Information Warehouse on thefirst page of any version of SAP Library.

Security Guide: SAP Transactionware Enterprise

4 April 2010

Contents1 Introduction ............................................................................................. 51.1 Document History ....................................................................................... 51.2 About this Document .................................................................................. 5

2 Overview .................................................................................................. 52.1Guiding Principles........................................................................................ 52.2Levels of Upgrades ...................................................................................... 62.3Upgrade Context .......................................................................................... 72.4Procedures ................................................................................................... 7

3 Preparing for Upgrade ............................................................................ 93.1 System Requirements ................................................................................. 93.2 Preparing Installation Image Repository ................................................. 103.4 Performing Pre-Upgrade ........................................................................... 13

4. Upgrade ................................................................................................. 154.1 Publishing or Distributing Store and POS/OLC Client Software ........... 154.2 Upgrading Head Office.............................................................................. 174.3 Upgrading Store ........................................................................................ 184.4 Upgrade OLC Client .................................................................................. 194.5 Upgrade POS Client .................................................................................. 20

5. Post-Upgrade Operations .................................................................... 215.1 Post-Upgrade Operations at Head Office ................................................ 215.2 Post-Upgrade Operations at Store ........................................................... 215.3 TPMfSW Server .......................................................................................... 22

6. Troubleshooting ................................................................................... 227. Reference .............................................................................................. 25

Upgrade Guide: SAP Enterprise Point-of-Sale

April 2010 5

1 IntroductionThis section provides introductory information that you need to know before you beginupgrading SAP Enterprise Point-of-Sale (SAP Enterprise POS), Transactionware Enterprise(TE).

1.1 Document HistoryThe 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 wasneither changed nor released for SP02)

1.02 SAP Enterprise POS 3.1 SP03



1.2 About this DocumentPurposeThis guide provides step-by-step instructions for upgrading SAP Enterprise POS. It isintended for SAP or SAP-approved system administrators and technology consultants.

2 Overview2.1 Guiding PrinciplesThe following are the core principles of the SAP Enterprise POS upgrade process.

2.1.1 Phased Upgrading for Multiple StoresAllows you to apply a selective upgrade. For example, you may not want to upgrade all thestores but only a group of stores at the same time in a staged approach.

2.1.2 External Systems Decoupled from UpgradesThere is minimal impact there are changes to the interface specification between an externalsystem and SAP Enterprise POS.

2.1.3 Complete and Unattended Upgrade at StoresFor a normal upgrade, store or corporate administrative personnel have to provide minimalmanual intervention.

2.1.4 Best PracticeThe store upgrade has to be performed after a successful head office upgrade.

Before the upgrade, the middleware (that is, IBM DB2, IBM MQ, and IBM WebSphereapplication server) has to work properly on the server to be upgraded.


6 April 2010

The system time of the servers involved in the upgrade process has to be synchronized.

2.2 Levels of UpgradesUpgrades come with three levels of significance, and one approach is not suitable for allthree levels.

The following levels of upgrades are possible:

Patches

Involve minimal changes for a simple upgrade and involve no data loss. A patch isapplied to an existing installation and it updates the code without breaking anyinterfaces. 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 andinvolve no data loss.

Exceptional upgrades

Involve significant changes that you cannot handle as a standard upgrade. Anexceptional upgrade requires greater effort to convert from one version to another.

You need to perform an exceptional upgrade when one of the following conditionsexists:

There is no established upgrade between the two versions. Either the priorversion is an older version than what is supported by upgrades to the currentversion, or the prior version is a customer-specific version for which astandard upgrade has not been implemented.

The interfaces (for example, JMS, RMI, database or configuration) betweenthe prior version and the new version cannot be made compatible. Thisincompatibility must prevent interaction between systems running the twoversions.

Data loss would be encountered when using a standard upgrade approach.Data loss can occur when the prior version contains data that has noequivalent storage possibility in the new version or for which there is noconsistent way of converting the data. In general, this must be avoided ifpossible, but there could be situations where it is unavoidable.

The terms patch, standard upgrade, and exceptional upgrade are not correlated with thepatch, minor and major software version levels, or releases. The terms reflect the level ofeffort required to create and apply the upgrade, and the impact that the upgrade has on thesystem. A patch release may be applied by either a patch upgrade or standard upgrade, anda major or minor version release may be applied by a patch, standard, or exceptionalupgrade.

2.2.1 PatchesGenerally, to apply a patch upgrade, you perform an in-place data upgrade and replace theexisting 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 compatiblewith any other system with which it interacts, including internal (head office or store) systemsand external systems.


April 2010 7

2.2.2 Standard UpgradeFor a standard upgrade, there may be interface changes that you need to handle, but youcan do so using a standard approach. While the data upgrade might take some time andeffort, it can be accomplished in a standard manner.

Generally, 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 anymiddleware changes that are required, and deploy the new enterprise application.

2.2.3 Exceptional UpgradeAn exceptional upgrade may be handled in part using a standard upgrade, but it could havesome aspects requiring customization (at least when it is created). It may require acompletely different approach if the differences are too significant.

You can accomplish an exceptional upgrade in many ways. The simplest is a customizedform 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 convertedto run the newer version. You can use an extensible standard upgrade to support anexceptional upgrade. This method is described here.

2.3 Upgrade ContextThe context in which upgrades need to operate can vary for each retailer. For some retailers,SAP Enterprise POS owns the store and POS client systems, and needs to manage thewhole 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, and so the SAPEnterprise POS upgrade needs to be coordinated with upgrades to other systems, which caninclude distribution, scheduling, and application by these other upgrades.

SAP Enterprise POS 3.1 runs on IBM’s WRS, and the technical context for upgrades is aWRS environment. The upgrades are managed using Tivoli Provisioning Manager forSoftware (TPMfSW). If SAP Enterprise POS is one of many of the retailer’s storeapplications, it is expected that the coordination with these other systems will be managedusing TPMfSW.

2.4 ProceduresThere are many views and levels of process flow to be considered for an upgrade. Thefollowing provides an explanation of the context in which upgrades are expected to operate,and the expected flow of the processing from different perspectives.

2.4.1 Logistics ViewFrom a logistics perspective, updates are typically applied to a retailer’s enterprise in asequence resembling the one below:

1. Upgrade all enterprise systems that need to handle new versions of interfaces for datareceived from SAP Enterprise POS (for example, TLogs and services). This step is notrequired by the 3.1 upgrade.

2. Upgrade the POS head office system. This upgrade can be done in isolation to allow fordetection of any issues that it might cause, or it can be done during the next step.


8 April 2010

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 determinewhether the new version is working successfully or not. Sometimes, you repeat this typeof upgrade for different stores, or groups of stores, that may have differentcharacteristics.

4. Upgrade a large group of stores. This is the beginning of what is often 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 feedsnew data to the POS that was not handled by the previous version. This strategy allowsthe retailer to detect any critical issues as soon as possible and, if needed, roll back theupdate for the affected systems.

2.4.2 Head Office Level ProceduresAt the retailer’s head office (the location, not just the server), perform the following tasks:

1. Prepare the TPMfSW server for upgrades:

a. Place the SAP Enterprise POS 3.1 SP05 software distribution and requiredthird-party libraries on the TPMfSW server (for more information, see theRequired Software section).

b. Customize the SAP Enterprise POS 3.1 SP05 distribution with the securitysetting from the previous installation, repackage it, generate new softwareinstallable - Software Package Blocks (SPBs), and install them on theTPMfSW server.

2. Load enterprise deployment and configuration data in the TPMfSW database.

3. Apply the head office system upgrade: Trigger the TE Head Office Upgrade SPBinstallation using the TPMfSW scalable infrastructure.

4. Distribute the store system upgrade(s): Distribute TE Store Upgrade SPB to the storeservers using the TPMfSW scalable infrastructure.

5. Distribute the POS, or OLC client, or both system installation(s): Distribute the SPBs tothe client servers using the TPMfSW scalable infrastructure.

6. Schedule the store system upgrade(s): This is required to synchronize business activitieswith upgrade steps that need to be performed.

7. Schedule the client system installation(s): This is required to synchronize businessactivities with upgrade steps that need to be performed.

2.4.3 Store Level ProceduresPerform the following activities at the stores (the location, not just the server):

1. Obtain the upgrade (TE Store Upgrade SPB).

2. Apply the store system upgrade: At the head office, trigger the TE Store Upgrade SPBinstallation using the TPMfSW scalable infrastructure.

2.4.4 Register Level ProceduresPerform the following activities at the stores (the location, not just the server):

1. If you plan to reuse the physical register for the new POS or OLC client installation, youmust perform this step before running the software distribution from the head office. If theregister is configured as an OLC client running the previous SAP Enterprise POS version,then the database replication process must be stopped and cleaned up. The terminalmust be closed. The register must be discovered and registered with the TPMfSW server.


April 2010 9

After that, the Tivoli Common Agent (TCA) must be installed on the register. For moreinformation, see the SAP Enterprise Installation Guide.

2. The register must have the upgrade (TE POS Client or TE OLC Client SPB).

3. Apply the register system installation: At the head office, trigger the TE POS Client orTE OLC Client installation using the TPMfSW scalable infrastructure.

3 Preparing for UpgradeThis section provides information about how to prepare for a successful upgrade of SAPEnterprise POS from version 3.1 SP03 or SP04 to 3.1 SP05

The software can be acquired by DVD or from SAP Service Marketplace.

3.1 System Requirements3.1.1 EnvironmentTivoli TPMfSW version 5.1.1 must be available to deploy SAP Enterprise POS. This servercannot be used to run SAP Enterprise POS, only to deploy it.

The previous SAP Enterprise POS 3.1 SP03 or SP04 build custom directory should beavailable on the TPMfSW server. If this directory does not exist on the server, it can becopied from the head office server.

The previous SAP Enterprise POS 3.1 SP03 or SP04 is installed and running.

3.1.2 Required SoftwareThe following table lists the software required for the SAP Enterprise POS 3.1 SP03 or SP04upgrade. If, after the upgrade, you are planning to carry out new SAP Enterprise POS 3.1SP05 application installations, see the SAP Enterprise Installation Guide for more informationabout the software required for the new installation.

Miscellaneous Java API for XML WebServices (JAX-WS)Reference ImplementationVersion 2.1.7 https://jax-ws.dev.java.net/2.1.7/

Open source JAVA codeused by the application.Must be downloaded andinstalled as a prerequisitefor deploying SAPEnterprise POS.

https://jax-ws.dev.java.net/2.1.7/

https://jax-ws.dev.java.net/2.1.7/


10 April 2010

3.2 Preparing Installation Image RepositoryUseTo prepare installation image repository.

PrerequisitesYou have installed a Tivoli TPMfSW product and it is functioning correctly.

Procedure for Linux EnvironmentAs root user, perform the following steps on the TPMfSW server:1. As root user and using the assigned password, log on to the Linux machine on which the

Tivoli TPM server is running.

2. Create the TE Installation Root Directory (later referred to as TE_INSTALL_ROOT) andmake the TPMfSW administrator user the owner of that directory. TE_INSTALL_ROOT isthe directory where all software required by SAP Enterprise POS 3.1 SP05 is located.The default directory is /opt/sap/te. If the directory already exists as a result of anSAP Enterprise POS 3.1 SP03 or SP04 installation, skip this step. Assuming that theTPMfSW user name and group are tioadmin execute the following commands (ifrequired):

mkdir –p /opt/sap/techown –R tioadmin:tioadmin /opt/sap/te

You must execute all other steps as the TPMfSW administrator user.

3. If the TE_INSTALL_ROOT directory contains the previous SAP Enterprise POS 3.1 SP03or SP04 release in the /opt/sap/te/build directory, rename it using the followingcommand to prevent a directory name collision with the new build:

mv /opt/sap/te/build /opt/sap/te/build-31-old

4. Copy the TE zip archive from the provided upgrade media to the TE_INSTALL_ROOTdirectory and extract the new build from the archive. The archive file name isTESERVER00_0.sca. Execute the following commands to extract the build:

cd /opt/sap/te

unzip TESERVER00_0.sca DEPLOYARCHIVES/*

As the result the DEPLOYARCHIVES directory containingis~isr~epos~te_collapsed.sda and is~isr~epos~te_deliver.sda installablearchives should be created under TE_INSTALL_ROOT directory. Theis~isr~epos~te_collapsed.sda archive is not used by installation and upgradeprocesses and can be deleted to save disk space. Continue with the following steps:

cd DEPLOYARCHIVES unzip is~isr~epos~te_deliver.sda


April 2010 11

Once is~isr~epos~te_deliver.sda file has unzipped, the build directory shouldappear under the DEPLOYARCHIVES directory. Move it to the TE_INSTALL_ROOTdirectory.

mv build ..

5. Set the JAVA_HOME and PATH environment variables based on the location of theinstalled JRE. The upgrade process requires the same JRE 1.5 level as the previousSAP Enterprise POS 3.1 SP03 or SP04 installation process so the installed JRE can bereused. This example uses an IBM JRE.

export JAVA_HOME=/opt/sap/te/ibm-java2-i386-50/jre

export PATH=$JAVA_HOME/bin:$PATH

6. Download and copy the JAX-WS 2.1 reference implementation (as noted in the RequiredSoftware section) to the TE_INSTALL_ROOT directory.

7. Extract the contents of the JAX-WS 2.1 reference implementation using the followingcommands:

export LANG=en_US.ISO-8859-1

cd /opt/sap/te

unzip jaxws-ri.zip

java –jar JAXWS2.1.7-20090419.jar

The license acceptance window appears. Read the license agreement in its entirety andclick on the Accept button to complete the extraction.

8. Set the value of the JAXWS21_HOME Environment Variable pointing to the JAX-WS 2.1reference implementation on the TPM server, for example:

export JAXWS21_HOME=/opt/sap/te/jaxws-ri

9. Make shell scripts executable using the following commands:

cd /opt/sap/te/build/utils

chmod 775 setupPlatform.sh

sh setupPlatform.sh

Procedure for Windows EnvironmentAs a tioadmin user, perform the following steps on the TPMfSW server:1. Log on as tioadmin user to the Windows machine on which the Tivoli TPMfSW server is

running.

2. Create the TE Installation Root Directory (later referred to as TE_INSTALL_ROOT). TheTE_INSTALL_ROOT directory is where all software required by SAP Enterprise POS 3.1SP05 is located. The default directory is \sap\te. If that directory already exists as a


12 April 2010

result of an SAP Enterprise POS 3.1 SP03 or SP04 installation, skip this step. Executethe following commands (if required):

mkdir \sap\te

3. If the default TE_INSTALL_ROOT directory contains the previous SAP Enterprise POS3.1 SP03 or SP04 release in the /opt/sap/te/build directory, rename it using thefollowing command to prevent a directory name collision with the new build:

mv \sap\te\build \sap\te\build-31-old

4. Extract the content of the DEPLOYARCHIVES folder from the TE zip archive from theprovided installation media to the TE_INSTALL_ROOT directory. The archive file name isTESERVER00_0.sca. As the result the DEPLOYARCHIVES directory containingis~isr~epos~te_collapsed.sda and is~isr~epos~te_deliver.sda installablearchives should be created under TE_INSTALL_ROOT directory. Theis~isr~epos~te_collapsed.sda archive is not used by installation and upgradeprocesses and can be deleted to save disk space. Unzip content of theis~isr~epos~te_deliver.sda archive into the DEPLOYARCHIVES directory. Oncethis has been done, the build directory should appear under the DEPLOYARCHIVESdirectory. Move that directory to the TE_INSTALL_ROOT directory.

NoteIf you use cygwin to unzip the file you must set read and write permissions onall files and subdirectories.

5. Set the JAVA_HOME and PATH environment variables based on the location of theinstalled JRE. The upgrade process requires the same JRE 1.5 level as the previousSAP Enterprise POS 3.1 SP03 or SP04 installation process so the values can be reused.This example uses the publicly available Java Runtime Environment 1.5.0_16:

set JAVA_HOME=C:\Program Files\Java\jre1.5.0_16

set PATH=%JAVA_HOME%\bin;%PATH%

6. Download and copy the JAX-WS 2.1 reference implementation (as noted in the RequiredSoftware section) to the TE_INSTALL_ROOT directory.

7. Extract the contents of the JAX-WS 2.1 reference implementation zip archive to theTE_INSTALL_ROOT directory. The JAXWS2.1.7-20090419.jar file should appear inthe TE_INSTALL_ROOT directory.

8. Extract the contents of the JAX-WS 2.1 reference implementation using the followingcommands:

java –jar JAXWS2.1.7-20090419.jar

The license acceptance window appears. Read the license agreement in its entirety andclick the Accept button to complete the extraction.


April 2010 13

9. Set the value of the JAXWS21_HOME Environment Variable pointing to the JAX-WS 2.1reference implementation on the TPM server, for example:

set JAXWS21_HOME=C:\sap\te\jaxws-ri

set PATH=%JAXWS21_HOME%\bin;%PATH%

3.4 Performing Pre-UpgradeUseTo generate software packages, and to install them on the TPMfSW server. Perform theappropriate procedure depending on your operating system.

PrerequisitesYou have completed the previous steps.

ProcedureAs the TPMfSW administrator user, perform the following steps on the TPMfSW server. Thedefault TPMfSW administrator name is tioadmin.

1. Navigate to the deployment\upgradebase\upgradecheck directory of the newSAP Enterprise POS 3.1 SP05 build and edit the precondition Check.properties.Check the properties if necessary. The default preconditions are:pos.check=truepos.allowOpenTerminals=falsepos.allowUnpostedTransactions=falsepos.allowUnreconciledTills=falsepos.allowMissingBankDeposit=false

store.check=truestore.allowOpen=false

These settings require that POS terminals have to be closed with no unpostedtransactions, no unreconciled tills, and no missing bank deposit; you must close stores.

Change the setting to true or false to enable or disable the precondition check.

NoteThe condition at the target server must match the preconditions in order forupgrade to be performed. Otherwise, the process will fail with an error message inthe upgrade logs at the target server. See the Troubleshooting section for thelocation of the upgrade logs.

2. Navigate to the deployment directory of the new SAP Enterprise POS 3.1 SP05 buildand start the preupgrade utility. The command line requires the path to the previous 3.1SP03 or SP04 installation custom directory as a parameter. If that directory is notavailable on the TPMfSW server it can be copied from the head office server. By default,


14 April 2010

that directory is /opt/sap/te/config on the Linux and \sap\te\config on theWindows servers. To start the utility, execute the following command:

Linuxcd /opt/sap/te/build/deploymentsh preupgrade.sh /opt/sap/te/config

Windowscd \sap\te\build\deploymentpreupgrade.bat \sap\te\config

When the script starts:

1. The prompt for the new server installation types displays the possible choices. It can beskipped by entering 4 even if you are planning to install the new SAP Enterprise POS 3.1SP05 stores. The required software installable will be re-generated automatically bydefault.

2. The prompt for the new offline capable POS installation types displays the possiblechoices. If you are planning to install the new offline capable POS and you have copiedthe necessary files under the EXTERNAL directory (for more information, see the SAPEnterprise Installation Guide), enter the number matching the type you need. Otherwise,enter 4 to skip this step and continue.

3. The prompt for the new regular POS installation types displays the possible choices. Ifyou are planning to install the new regular POS and you have copied the necessary filesunder the EXTERNAL directory (for more information, see the SAP Enterprise InstallationGuide), enter the number matching the type you need. Otherwise, enter 4 to skip thisstep and continue.

4. The prompt for the SMD agent installation types displays the possible choices. It can beskipped by entering 4 if you already carried this out for the SAP Enterprise POS 3.1SP03 or SP04 installation or if you do not plan to install it. In any other case, enter thenumber matching the operating system, which is based on the operating system used bythe Enterprise POS servers. Make sure you copied the necessary files under theEXTERNAL directory (for more information, see the SAP Enterprise Installation Guide).

5. The prompt for the Wily agent installation types displays the possible choices. It can beskipped by entering 4 if you already carried this out for the SAP Enterprise POS 3.1SP03 or SP04 installation or if you do not plan to install it. In any other case, enter thenumber matching the operating system type which is based on the operating systemused by the Enterprise POS servers. Make sure you copied the necessary files under theEXTERNAL directory (for more information, see the SAP Enterprise Installation Guide).

6. The prompt for the TE server upgrade types displays the possible choices. Enter thenumber matching the type you need.

7. The prompt for the offline capable POS upgrade types displays the possible choices. Ifyou are using the offline capable POS enter the number matching the type you need.Otherwise, enter 4 to skip this step and continue.

8. The prompt for the regular POS upgrade types displays the possible choices. If you areusing the regular POS enter the number matching the type you need. Otherwise, enter 4to skip this step and continue.


April 2010 15

4. UpgradeAfter completing upgrade preparation, perform the following upgrade steps using theTPMfSW Web user interface (Web UI).

The SAP Enterprise POS 3.1 SP05 upgrade consists of the following steps: Publish store, and POS and OLC client software installable on the depot server(s). Distribute installable software to the target servers, if required. Perform head office upgrade. Perform store(s) upgrade. Perform POS and OLC client upgrades.

You can omit the Publishing or Distributing Store and POS/OLC Client Software steps in theenvironments when you perform the upgrade on the local area network and performance isnot an issue (for example, the lab environment upgrade). In the production environment, werecommend that you publish and distribute software before you start the stores upgrade andOLC and POS client installations.

Perform the upgrade in the following sequence: head office, stores, and POS and OLCregisters.

Stores and their registers must be upgraded together. If any register from the store was notupgraded for any reason when the store upgrade was performed that register must not beused until upgraded. Stores can be upgraded in the staged manner.

4.1 Publishing or Distributing Store andPOS/OLC Client SoftwareUseTo publish store and POS/OLC client software products on the depot server(s) and distributethem across the target servers using the TPMfSW scalable infrastructure.

Prerequisites You have completed the previous steps

You have set up the TPMfSW server

You have made sure that the depot server has enough space to store the files and theData Directory limit is set to 8000 or to a size that is capable of storing the packages tobe published on the depot. The following list estimates the sizes for various packages:

Package Description Size in Data Directory

Store or Head Office Upgrade – Linux 120MB

Store or Head Office Upgrade - Windows 120MB

POS Upgrade – Linux 20MB

POS Upgrade – Windows 20MB

OLC Upgrade – Linux 120MB

OLC Upgrade – Windows 120MB


16 April 2010

NoteIf the value is changed on the TPMfSW console, perform the following stepson the depot server:

1. Sign on as root for Linux or Administrator for Windows.

2. Check the DATA_DIRECTORY_SIZE property incdsserver.properties and make sure it matches the setting onthe console. The cdsserver.properties properties file is locatedin /opt/tivoli/ep/runtime/agent/subagents for Linux andin C:\ProgramFiles\tivoli\ep\runtime\agent\subagents for Windows.

3. Restart the endpoint: Linux

/opt/tivoli/ep/runtime/agent/endpoint.sh restart

WindowsStart->Control Panel->

Administrative Tools->Services

4. Restart the Tivoli Common Agent service.

Procedure1. Log on to the TPMfSW Web UI.

2. In the left navigation frame, choose Software Management -> Publish -> SoftwareProducts.

The Publish Software Products screen appears.

3. On the Publish Software Products screen, in the Select Installables section, type TE inthe search text field and click the Search button next to it.

4. In the search result, select the checkmark next to the Software Files that you need todistribute:

Linux

TE_HO_Upgrade_Linux_3.1.3-SP05 – for head office upgrade

TE_ST_Upgrade_Linux_3.1.3-SP05 – for store upgrade

TE_OLC_Upgrade_Linux_3.1.3-SP05 – for OLC register upgrade

TE_POS_Upgrade_Linux_3.1.3-Sp05 – for POS register upgrade

Windows

TE_HO_Upgrade_Windows_3.1.3-SP05 – for head office upgrade

TE_ST_Upgrade_Windows_3.1.3-SP05 – for store upgrade

TE_OLC_Upgrade_Windows_3.1.3-SP05 – for OLC register upgrade

TE_POS_Upgrade_Windows_3.1.3-SP05 – for POS register upgrade


April 2010 17

5. In the Select Depots section, select the checkbox(es) next to the depot server(s) onwhich you would like to publish Software Installable.

6. Specify scheduling and notification options in the Schedule and Notification sectionsrespectively and click the Submit button.

You are directed to the Track Tasks screen where you can monitor the publishingprogress. If publishing is not successful, troubleshoot the problem and re-publishSoftware Installable before you continue with the next step.

7. In the left navigation frame, choose Software Management -> Distribute -> SoftwareProducts.

You are directed to the Distribute Software Products screen.

8. On the Distribute Software Products screen, in the Select Software section, enter TE inthe search text field and choose the Search button next to it.

9. In the search result, select the checkbox next to the TE Store Upgrade 3.1.3-SP05 andTE OLC Client Upgrade 3.1.3-SP05 and/or TE POS Client Upgrade 3.1.3-SP05 SoftwareInstallable names.

10. In the Select Computers section, select the checkboxes next to the servers, or groups ofservers, to which you would like to distribute software products.

11. Specify scheduling and notification options in the Schedule and Notification sectionsrespectively and click the Submit button.

You are directed to the Track Tasks screen where you can monitor the distributionprogress. If distribution is not successful, troubleshoot the problem and re-distributeSoftware Product before going to the store upgrade.

4.2 Upgrading Head OfficeUseTo upgrade the head office server to the new SAP Enterprise POS 3.1 SP05 version.

Prerequisites You have completed the previous steps.

You have set up the TPMfSW server.

TCA agent is running on server.

If the head office server is installed on the Windows system, make sure that theTE_HOME directory (C:\sap\te\product by default) is not used by other users andapplications including Windows OS utilities such as Windows Explorer or command lineprompt, because they may lock the directory and cause the upgrade process to fail. Allusers must log off from the server before submitting the upgrade. As a best practice, aserver reboot can be performed before submitting the upgrade.


2. In the side navigation frame, choose Software Management -> Install -> SoftwareProducts.


18 April 2010

The system displays the Install Software Products screen

3. In the Select Software section of the Install Software Products screen, enter TE in thesearch text field and click Search.

4. In the search result, choose TE Head Office Upgrade 3.1.3-SP05 Name.

5. In the Select Computers section, in the Display dropdown list, choose By Computer.Select the head office server Name.

6. Specify scheduling and notification options in the Schedule and Notification sectionsrespectively.

7. Click the Submit button. You are directed to the Track Tasks screen where you canmonitor the installation progress. If the upgrade is not successful, troubleshoot theproblem before continuing with the next step.

NoteIt is recommended to reboot the Windows server and to ensure that the server isup and running before performing the upgrade procedure.

4.3 Upgrading StoreUseTo upgrade the store server to the new SAP Enterprise POS 3.1 SP05 version.

Prerequisites The previous steps have been completed.

TPMfSW server is up and running.


If the store server is installed on the Windows system, make sure that the TE_HOMEdirectory (C:\sap\te\product by default) is not used by other users and applicationsincluding Windows OS utilities such as Windows Explorer or command line prompt,because they may lock the directory and cause the upgrade process to fail. All usersmust log off from the server before submitting upgrade. As the best practice server rebootcan be performed before submitting upgrade.


2. In the left navigation frame, choose Software Management -> Install -> SoftwareProducts. The Install Software Products screen appears.

3. In the Select Software section on the Install Software Products screen, enter TE inthe search text field and click Search.

4. In the search result, select the TE Store Upgrade 3.1.3-SP05 Name.

5. In the Select Computers section, in the Display dropdown list, choose By Computer.Select the store server(s) or group(s) of server name(s).

6. Specify scheduling and notification options in the Schedule and Notification sectionsrespectively.


April 2010 19

7. Click the Submit button. The Track Tasks screen appears where you can monitorthe installation progress. If the publishing is not successful, troubleshoot theproblem before continuing to the next step.

NoteIt is recommended to reboot the Windows server and wait until it back to workingcondition before performing the upgrade procedure.

4.4 Upgrade OLC ClientUseTo upgrade OLC client on the target server.


You have closed the terminal running with the same client ID.

You have ended the Enterprise POS client application.




2. In the side navigation frame, choose Software Management -> Install -> SoftwareProducts. The Install Software Products screen appears.

3. In the Select Software section on the Install Software Products screen, enter TE inthe search text field and click Search.

4. In the search result, select the TE OLC Client Upgrade 3.1.3-SP05 Name.

5. In the Select Computers section, under the Display drop-down list, select ByComputer. Select the OLC client(s) or group(s) of OLC client Name(s).

6. Specify scheduling and notification options in the Schedule and Notification sectionsrespectively, and click the Advanced button. The Install Software - Advanced screenappears.

7. Edit the following TE OLC client upgrade 3.1.3-SP05 template parameter values:

%TE_USER – the name of the TE user

and click the Submit button.

8. The system displays the Track Tasks screen, where you can monitor the installationprogress.

9. Reboot the Windows OLC computer after upgrade.


20 April 2010

4.5 Upgrade POS ClientUseTo upgrade POS client on the target server.


You have closed the terminal running with the same client ID.

You have ended the Enterprise POS client application.




2. In the left navigation frame, choose Software Management -> Install -> SoftwareProducts. The Install Software Products screen appears.

3. In the Select Software section on the Install Software Products screen, enter TE inthe search text field and choose Search.

4. In the search result, select the TE POS Client Upgrade 3.1.3-SP05 Name.

5. In the Select Computers section, in the Display dropdown list, select By Computer.Select the POS client(s) or group(s) of POS client Name(s).

6. Specify scheduling and notification options in the Schedule and Notification sectionsrespectively, and click the Advanced button. The Install Software - Advanced screenappears.

7. Edit the following TE POS client upgrade 3.1.3-SP05 template parameter values:

%TE_USER – the name of the TE user

and click the Submit button.

8. The Track Tasks screen appears, where you can monitor the installation progress.

9. Reboot computer after upgrade.


April 2010 21

5. Post-Upgrade OperationsAfter the upgrade has been completed at the head office and stores, the previous SAPEnterprise POS build is backed up in the backup folder under the data directory. The defaultpath is:

Linux

/var/sap/te/backup and the file name is te-build-<previous-version-numer>.tar where <previous-version-numer> is the actual previous SAPEnterprise POS build number.

Windows

\sap\te\backup and the file name is te-build-<previous-version-numer>.zipwhere <previous-version-numer> is the actual previous SAP Enterprise POSbuild number.

5.1 Post-Upgrade Operations at Head OfficeUseTo clean up and free resources utilized during upgrade.


You have successfully upgraded all stores.

ProcedureDelete the previous SAP Enterprise POS build backed up in the location mentioned above.

5.2 Post-Upgrade Operations at StoreUseTo clean up and free resources utilized during upgrade.

Prerequisites Previous steps have been completed.

Stores have been upgraded successfully.

Procedure Delete the previous SAP Enterprise POS build backed up in the location mentioned above.


22 April 2010

5.3 TPMfSW ServerUseTo clean up and free resources.

Prerequisites The head office, store, and all required registers had been upgraded.


2. In the left navigation frame, choose Software Management -> Manage SoftwareCatalog -> Software Products. The Manage Software Products screen appears.

3. In the search section on the Manage Software Products screen, enter TE in theName search text field and click Search button.

4. In the search result, select the TE Head Office Upgrade 3.1.3, TE OLC ClientUpgrade 3.1.3, TE POS Client Upgrade 3.1.3, TE Store Upgrade 3.1.3, Names andclick Delete button.

NoteThe names of the deleted TE upgrade software modules do not have the SP05postfix and are used by the SAP Enterprise POS releases prior to SAP EnterprisePOS SP03.

6. TroubleshootingUpgrade Log FilesIn case of failure, evaluate the following log files:

Linux

/tmp/te/opt/sap/te/product/deployment/logs/upgrade.log,/tmp/te/opt/sap/te/product/deployment/logs/db2udbupgrade.log,opt/sap/te/product/deployment/logs/upgrade.log, andopt/sap/te/product/deployment/logs/db2udbupgrade.log – upgradeprocess log files on the target server

/tmp/te/opt/sap/te/product/deployment/logs/ and/opt/sap/te/product/deployment/logs/ – directories for the SAP EnterprisePOS head office, store, OLC client, and POS client installation and deployment logfiles on the target server

/tmp/te/te-upgrade-logs/ – directory for the TE Head Office Upgrade and TEStore Upgrade SPB installation log files on the target server

/opt/IBM/WebSphere/AppServer/profiles/<profile-name>/logs/server1/SystemOut.log – WebSphere application server log fileon the target server


April 2010 23

/opt/IBM/WebSphere/AppServer/profiles/<profile-name>/logs/server1/te_server.log – SAP Enterprise POS log file on thetarget server

/tmp/OLCInstall/OLCInstall.log – OLC client installation process log file onthe target server

/tmp/OLCInstall-logs/ – directory for the TE OLC Client SPB installation logfiles on the target server

/tmp/POSInstall/POSInstall.log – POS client installation process log file onthe target server

/tmp/POSInstall-logs/ – directory for the TE POS Client SPB installation logfiles on the target server

/opt/tivoli/ep/logs/rcp.log – Tivoli Common Agent log file on the targetserver

Windows%TEMP%\te\opt\sap\te\product\deployment\logs\upgrade.log,%TEMP%\te\opt\sap\te\product\deployment\logs\db2udbupgrade.log,\sap\te\product\deployment\logs\upgrade.log, andopt\sap\te\product\deployment\logs\db2udbupgrade.log – upgradeprocess log files on the target server

%TEMP%\te\opt\sap\te\product\deployment\logs\ and\sap\te\product\deployment\logs\ – directories for the SAP Enterprise POShead office, store, OLC client, and POS client installation and deployment log files onthe target server

%TEMP%\te\te-upgrade-logs\ – directory for the TE Head Office Upgrade andTE Store Upgrade SPB installation log files on the target server

%PROGRAMFILES%\IBM\WebSphere\AppServer\profiles\<profile-name>\logs\server1\SystemOut.log – WebSphere application server log fileon the target server

%PROGRAMFILES%\IBM\WebSphere\AppServer\profiles\<profile-name>\logs\server1\te_server.log – SAP Enterprise POS log file on thetarget server

C:\TEMP\OLCInstall\OLCInstall.log – OLC client installation process log fileon the target server

C:\TEMP\OLCInstall-logs\– directory for the TE OLC Client SPB installationlog files on the target server

TEMP%\POSInstall\POSInstall.log – POS client installation process log file onthe target server

TEMP%\POSInstall-logs\ – directory for the TE POS Client SPB installation logfiles on the target server

%PROGRAMFILES%\tivoli\ep\logs\rcp.log – Tivoli Common Agent log file onthe target server

If the upgrade process fails on the Windows system and the C:\sap\te\tmp\securitydirectory was created on the target server then that directory needs to be deleted.


24 April 2010

Tivoli TPMfSW error message: COPCOM123E A shell command erroroccurred: Exit code=3, Error stream="Timeout - login on localhostfailed. Command: ’su – tioadmin’

The response time setting in the built-in TPMfSW Local_Execute_Command workflow causesthis issue. In case of failure, it is safe to rerun the installation. To prevent this failure fromreoccurring, increase the response time from 1 to 3 seconds by executing the following steps:

1. Make Local_Execute_Command workflow editable. Follow the IBM procedure for doingthat: http://www-01.ibm.com/support/docview.wss?rs=0&dc=DB500&q1=make+workflow+editable&uid=swg21252830&loc=en_US&cs=utf-8&cc=us&lang=en

2. Using a Web browser, logon to the Tivoli Web Console logon at the URL shown, where<tpm_host> is the fully qualified hostname of the server where TPMfSW is installed:https://<tpm_host>:9045/tcWebUI

3. In the Find text field on the left side of the screen, type Local_Execute_Command. In thesearch result you should see the link to the workflow. Click the workflow link; theWorkflow Editor: Local_Execute_Command screen appears.

4. On the Workflow Editor: Local_Execute_Command screen in the text area find thesleep .1 line (there is dot in front of digit 1) and change it to the sleep 3 (no dot in front ofdigit 3), for example, or any other response time you want to set.

5. Click the Compile option at the top of the screen. You should see the compilation result:Compilation successful.

Make Local_Execute_Command workflow not editable again.

Tivoli TPMfSW error message: DISSE0005E Operation unsuccessful.;return code = 9

The error message may look like the following:

Installation of package TE_HO_Upgrade_Linux_3.1.3-SP05 failedwith return code [9],

and message: bash: line 1: temp_dir: command not found

DISSE0029I Current software package status is 'ICU--'.

DISSE0028E The requested operation is not allowed for thesoftware package

TE_HO_Upgrade_Linux_3.1.3-SP05.3.1.3 due to a validationfailure.

DISSE0005E Operation unsuccessful.; return code = 9

This problem can be resolved by removing the epsp.cat, that is where the local SoftwarePackage status is kept.

The epsp.cat can be found at /root/.swdis/work (Linux) or C:\swdis\work(Windows).


April 2010 25

7. ReferenceFor more information, see the SAP Enterprise POS Installation Guide.

Documents

PUBLIC Upgrade Guide