sap enterprise point-of-sale 3.1 sp07 · pdf filesap enterprise point-of-sale (sap enterprise...

‘

Installation Guide

SAP

®

Enterprise

Point-of-Sale 3.1

SP07

Target Audience

System administrators

Technology consultants

February 15, 2012

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.

Typographic Conventions

Type Style Description

Example Text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons, labels as well as menu names, paths, and options.

Cross-references to other documentation

Example text Emphasized words or phrases in body text, titles of graphics and tables

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and key words of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, names of variables and parameters, source code as well as names of installation, upgrade and database tools.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.

EXAMPLE TEXT Keys on the keyboard, for

example, F2 or ENTER key.

Icons

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 window of any version of SAP Library.

Installation Guide

4 February 2012

Contents

Introduction ......................................................................................................... 6

About this Document ................................................................................... 6

Before you Start ........................................................................................... 6

SAP Notes for the Installation ..................................................................... 6

Information Available on SAP Enterprise POS .......................................... 7

Naming Conventions ................................................................................... 7

Planning .............................................................................................................. 9

Distributing SAP Enterprise POS over a Retailer’s Network .................... 9

Guiding Principles ....................................................................................... 9

High Level Architecture ............................................................................... 9

Install Stack .................................................................................................. 9

Application Stack ....................................................................................... 10

Support and Monitoring Stack .................................................................. 11

The System Landscapes for SAP Enterprise POS .................................. 12

Preparation ........................................................................................................ 13

System Requirements ............................................................................... 13

Operating System Requirements ............................................................. 13

Processor Speed and Memory Requirements ......................................... 14

Disk Space .................................................................................................. 14

Name Resolution ........................................................................................ 14

Group Policies for Windows Users .......................................................... 15

Software ...................................................................................................... 16

Port Settings ............................................................................................... 17

Tivoli Provisioning Manager Node ........................................................... 18

Tivoli Provisioning Manager Depot Node ................................................ 18

Security and Technical User IDs .............................................................. 18

Configuration Checklist............................................................................. 19

Preparing the Installation Image Repository (Linux TPM)...................... 20

Preparing the Installation Image Repository (Windows TPM) ............... 22

Customizing the SAP Enterprise POS Installation ........................................ 26

Cloning Customizable Files ...................................................................... 26

Integrating with a Loyalty Provider .......................................................... 26

Updating the device.properties File ......................................................... 27

Preinstallation ................................................................................................... 28

SAP Enterprise Point-of-Sale

February 2012 5

Running the Preinstallation Script ........................................................... 28

Prepare Tivoli Provisioning Manager ....................................................... 30

Installation ......................................................................................................... 40

Overview ..................................................................................................... 40

Installing Head Office Server .................................................................... 40

Installing Store Server ............................................................................... 41

Installing Wily Agent (Optional) ................................................................ 42

Installing SMD Agent (Optional) ............................................................... 43

Installing the POS Register ....................................................................... 44

Installation Verification .................................................................................... 46

Head Office ................................................................................................. 46

Store Server ............................................................................................... 47

Head Office and Store Server ................................................................... 49

Installing the Mobile Point-of-Sale .................................................................. 52

Configuring the Mobile Point-of-Sale Components ................................ 53

Post Installation ................................................................................................ 57

Applying Support Packages and Patches ............................................... 57

Configuration ............................................................................................. 57

Configuring Organization ID ..................................................................... 57

Hosted Sites ............................................................................................... 57

Configuring Business Logic ..................................................................... 59

Configuring Operational Data ................................................................... 62

Troubleshooting ................................................................................................ 67

Installation Guide

6 February 2012

Introduction This section provides introductory information that you need to know before you begin installing SAP Enterprise Point-of-Sale (SAP Enterprise POS).

This guide is regularly updated in SAP Service Marketplace at

http://service.sap.com/instguides under Industry Solutions → Industry Solution

Guides → SAP for Retail → SAP Enterprise Point-of-Sale.

Make sure you have the latest version of this guide by checking SAP Service Marketplace immediately before starting the installation.

About this Document

Purpose

This guide provides step-by-step instructions for installing SAP Enterprise POS. It also includes prerequisite and post-installation steps required to successfully install the application. It is intended for SAP or SAP-Approved system administrators and technology consultants.

SAP Enterprise POS is a market-leading, distributed Point-of-Sale (POS) system. It is a multi-tier system that supports nodes running in a retailer’s head office (HO), stores, and on POS terminals.

Integration

SAP Enterprise POS uses Tivoli Provisioning Manager (TPM) to enable management aspects of the application and support automated installations and upgrades. A server running TPM must be configured and run before installation.

Constraints

This guide does not include information about installing the IBM TPM server.

Refer to the IBM installation documentation.

Before you Start The following sections provide information about:

SAP Notes for the installation

Information available in SAP Service Marketplace

Naming conventions

SAP Notes for the Installation You must read the1655003 SAP Note before you start the installation. It contains the most recent information on the installation troubleshooting, as well as corrections to the installation documentation. Make sure that you have the up-to-date version of the SAP Note, which you can

find in the SAP Service Marketplace at the Internet address: service.sap.com/notes.


February 2012 7

Information Available on SAP Enterprise POS

Reference

For a complete list of available documents, see the SAP Enterprise POS Master Guide in SAP

Service Marketplace at http://service.sap.com/instguides under Industry Solutions

→ Industry Solution Guides → SAP for Retail → SAP Enterprise Point-of-Sale.

General Quick Links

Description Internet Address Title

SAP Notes service.sap.com/notes –

Released platforms

service.sap.com/platforms –

System sizing service.sap.com/sizing Sizing Guide

Installation and upgrade

service.sap.com/instguides Installation Guide, Upgrade Guide

Security service.sap.com/security –

Naming Conventions

In this documentation, the following naming conventions apply:

Terminology

Term Description

HO Head Office. Traditionally, a computer kept at a physical location (office) that is placed at the logical top (head) of the enterprise hierarchy. It is remotely networked to all of the ISPs.

ISP In-Store Processor. Traditionally, a computer kept at the physical retail location (store), and locally networked to point-of-sale terminals in the same location. It is remotely networked to the HO. It is also known as a store server.

POS Point-of-Sale terminal. Traditionally, a specialized computer configured with peripherals used to facilitate sales transactions.

OLC POS Offline Capable Point-of-Sale. Controller that keeps the POS operational when the ISP is not available.

SMD Solution Manager Diagnostics. SAP standard monitoring tool allowing SAP support personnel read-only access on remote systems.

Wily Introscope Wily. SAP standard monitoring tool to capture performance and other status data on remote systems.

TPM The Tivoli Provisioning Manager server.

TPM Depot The Tivoli Provisioning Manager depot server.

Installation Guide

8 February 2012

Variables

Variables Description

<SAPSID> SAP system ID in uppercase letters.

<sapsid> SAP system ID in lowercase letters.

<DBSID> Database system ID in uppercase letters.

<dbsid> Database system ID in lowercase letters.

<INSTDIR> Installation directory for the SAP system.

<CD-DIR> Directory on which a CD is mounted.

<DVD-DIR> Directory on which a DVD is mounted.

<OS> Operating system name within a path.


February 2012 9

Planning This section provides information about how to plan the SAP Enterprise POS installation and describes what you need to know before you begin preparing the installation.

Distributing SAP Enterprise POS over a Retailer’s Network This section explains how to automate SAP Enterprise POS installations across a retailer’s enterprise.

Guiding Principles Minimal configuration – The amount of configuration for an installation is minimal. In other

words, SAP Enterprise POS installs silently with most defaults.

Configurable – While minimal configuration is desirable, if you want to change default values, you can, for example, change user names or install paths.

Middleware – The application server, JMS server, and database that SAP Enterprise POS is dependent on are included within this installation process, but the operating system is not.

IBM Middleware – The installation process installs and configures only IBM WebSphere Remote Server middleware (WebSphere Application Server, WebSphere MQ, DB2 UDB).

IBM Installation Tools – Tivoli Provisioning Manager provides a robust and scalable way to manage software and hardware in a large network. It is part of the WebSphere Remote Server eAssembly.

High Level Architecture

SAP Enterprise POS

WAS - IBM WebSphere Application Server

MQ - IBM WebSphere MQ messaging

DB2 - IBM DB2 Universal Database

NLPOS - Novell Linux for Point-of-Sale

OLC - Offline Capable Client

WASCE - IBM WebSphere Application Server Community Edition, used on the OLC

DB2 Express - IBM DB2 Express, used on the OLC

JavaPOS - NRF ARTS JavaPOS device driver layer.

Install Stack SAP Enterprise POS leverages the capabilities of IBM Tivoli Provisioning Manager (TPM) to provide a scalable distribution infrastructure that can be used for large scale deployments of new software, software updates, and software auditing. Tivoli Provisioning Manager is included in the license for IBM WebSphere Remote Server 7.1.

Use the following TPM components to distribute and deploy SAP Enterprise POS:

TPM V7.2 – The TPM server should be a server dedicated to running only TPM. The product consists of a main application that runs on WebSphere Application Server ND 7.0, IBM DB2 UDB Enterprise Edition, IBM LDAP Server, and some stand-alone applications such as the agent manager and content delivery service.

Depot – A depot is any machine that has the content delivery service depot subagent installed. A depot server is required for the distribution of software using the software distribution infrastructure (SDI). All Enterprise POS servers act as depot servers.

Installation Guide

10 February 2012

Endpoint – An endpoint is the primary interface for system management. In the case of SAP Enterprise POS, the POS registers are considered endpoints. The Tivoli Common Agent software runs on the endpoint, and manages software delivery and installation for the machine it is running on.

Application Stack The application stack is the heart of SAP Enterprise POS. It consists of the middleware (WebSphere, MQ, DB2) and the application itself. Other processes included within the application stack are:

SAP POS Store Data Transfer for Retail (formerly referred to as Transnet) site client for EFT transactions

Transaction services for customer service access

Apply/capture servers for DB2 replication

MDI controller for master data import control

The following figure illustrates the application stack:

Head Office Server

OLC POS Client

Standard POS ClientStore Server

WAS

(TE EAR)

TE POS Client

(runs on WAS App

Client)

Hardware Stack

(JavaPOS)

Hardware Stack

(JavaPOS)

WAS CE

(TE OLC EAR)

WAN

LAN

LAN

MDI

Controller

POS

Store

Data

Transfer

for Retail

MQ

DB2

DB2

Capture

Server

WAS

(TE EAR)

POS

Store

Data

Transfer

for Retail

MQ

DB2

DB2

Apply

Server

DB2

Capture

Server

EPOS Client

(runs on WAS App

Client)

DB2 Express

DB2 Apply Server


February 2012 11

Support and Monitoring Stack The support and monitoring stack consists of the following SAP standard monitoring tools:

Introscope Wily: primarily used for J2EE-Based products. It captures the JVM status, performance status, and other status data for predefined services. The Wily agent collects this information on the Enterprise POS server and sends it to the Wily Enterprise Manager server

SAP Solution Manager Diagnostics (SMD): provides read-only access on remote systems, allowing support personnel to track changes on predefined file sets and to view files from a remote server. The SMD agent collects this information on the Enterprise POS server and sends it to the SMD server.

Only the Wily agents and SMD agents are included as part of the SAP Enterprise POS installation. The SMD and Wily agents are installed and integrated with SAP Enterprise POS on the store server and head office node only.

While installation of the agents is optional, it is highly recommended that these agents are installed on the SAP Enterprise POS servers to allow SAP support personnel to provide prompt and extensive support.

The following diagram illustrates the support and monitoring stack:

Installation Guide

12 February 2012

The System Landscapes for SAP Enterprise POS SAP Enterprise POS can be deployed flexibly based on your requirements. The primary configuration is shown below. Variations of this are possible, discuss them with SAP.

SAP Enterprise POS’s centralized configuration consists of the POS Client and the store server running at the store location, and the HO server running at a retailer’s headquarters.

1

Supported OS

EPOS POS Server EPOS POS Manager

EPOS Configurator

EPOS Pending Txn Service EPOS Returns Service

EPOS Centralized Txn DB

EPOS Customer DB Service

EPOS Central. Receipt Archive

EPOS POS Client

Supported OS Supported OS DB2

WAS

WebSphere MQ

EPOS POS Server (Primary)

Supported OS

EPOS Client

IBM WRS

x2

(min)

EPOS OLC Server

DB2

WAS WAS MQ IBM WRS

x2

(min)

Supported OS

DB2

WAS WebSphere MQ

EPOS Server (Primary) Supported OS

EPOS Client

IBM WRS

x2

(min)

Head Office

Store B

Store A

Online (Normal Operations) Offline (Fail - Over)

Client to Server Connection (RMI)

IBM DB2 Express IBM WebSphere CE

EPOS POS Client

Supported OS

EPOS OLC Server

DB2 Express IBM WebSphere CE

x2

(min)

NOTE: The operating system on all devices is not included in the SAP EPOS application bundle so it must be externally delivered.

2nd level failover

1st level failover

NOTE: In this example, the offline capable POS is configured as the first level failover target in Store A, but as the second level target in Store B. A POS client may employ any number of failover targets in any order


February 2012 13

Preparation This section provides information about how to prepare for a successful installation of SAP Enterprise POS.

The software can be acquired from the SAP Service Marketplace.

Ensure that all Enterprise POS servers:

Have a unique host name, and that the hosts are all navigable via host name

Are planned to have a unique store number

System Requirements There are a number of software and hardware requirements for using SAP Enterprise POS. These requirements include a standard mouse attached to the POS client for user interface editing, application servers, Web servers, databases, and operating systems.

All system requirements listed are minimum requirements. To maximize system efficiency, we recommend that you run your system above these levels, using the best available equipment and software.

Operating System Requirements The following operating systems are supported based on the node type:

Node(s) Version Edition Update Level

HO, TPM Depot*

SUSE Linux

Enterprise Server 11

HO, ISP, TPM Depot*

Windows Server 2008 Standard Edition SP2

HO, ISP, TPM Depot*

Windows Server 2008 R2 Standard Edition SP2

POS, OLC Windows 7 Professional Edition SP1

TPM Windows Server 2008 Standard Edition SP2

TPM Windows Server 2008 R2 Enterprise Edition R2 SP2

*For more information regarding TPM requirements, see the Tivoli Provisioning Manager InfoCenter at the following URL:

http://publib.boulder.ibm.com/infocenter/tivihelp/v45r1/topic/com.ibm.tivoli.tpm.doc/welcome/ic-homepage.html



Installation Guide

14 February 2012

Processor Speed and Memory Requirements The following are processor speed and memory requirements based on the node type:

Node Machine Type RAM

HO x86_64 4096MB

ISP x86

x86_64

2048BM

4096MB

OLC x86 1024MB

TPM* x86_64 8192MB



Disk Space The following are the recommended disk space requirements based on the node type. For more detailed disk sizing information, see the SAP Enterprise POS Sizing Guide in the SAP Service Marketplace.

Node Disk Space Requirements

HO 80GB

ISP 80GB

POS 5GB

OLC 40GB

TPM* 80GB



Name Resolution For all nodes, ensure that a form of name resolution is used. Either a DNS server or a static host file must resolve the name. If you are unfamiliar with the configuration of name resolution and networking concepts, consult your network administrator.

Ensure the following points are understood and accounted for:

For all nodes configure a fully qualified domain name.

If the host name is linux and the domain name is site.com, the fully qualified domain

name is linux.site.com. Some computers might be configured to return a short host

name only, such as linux.

A static IP address must be used for the HO, ISP, TPM, or TPM depot nodes

A dynamic or static IP can be used for an offline client (OLC) or standard client (POS) node






February 2012 15

If you are using a DNS server for name resolution, ensure that the host name configured in the operating system of the node matches the host name configured for that node on the DNS server

If you are using a hosts file to resolve IP addresses, the hosts file must be properly configured with the host name of the computer. The file must include:

1. The IP address, fully qualified domain name, and the host name of the computer as the first entry in the file.

2. The IP address 127.0.0.1, the fully qualified domain name localhost.localdomain,

the host name localhost, and the alias loopback.

3. The IP address, fully qualified domain name, and the host name of the other servers on the network.

The following example shows settings for a computer using a static hosts file:

#IP address Fully Qualified Domain Name Short Name

10.0.0.12 tpm.site.com tpm

127.0.0.1 localhost.localdomain localhost loopback

10.0.0.13 tpmdepot.site.com tpmdepot

10.0.0.14 ho.site.com ho

10.0.0.15 isp.site.com isp

Group Policies for Windows Users The silent installation of SMD agent on the Windows platform requires that the user account performing the installation has specific group policies set. Failure to configure the group policies will result in the failure of SMD agent installation. Installing the SMD agent is not mandatory. It is available to be installed on the following nodes: HO and ISP.

To add the required group policy settings on an individual machine:

1. Start the Group Policy Editor from the Windows Run dialog box: gpedit.msc

2. Navigate to the User Rights Assignment: computer configuration->windows setting->security settings->local

policies->user rights assignment.

3. Add the user that will perform the installation to the following policies: a. Act as part of the operating system. b. Adjust memory quotas for a process. c. Replace a process level token.

4. Exit the Group Policy Editor. 5. Restart the machine.

Installation Guide

16 February 2012

Software The following is a list of the required software:

Category Product Description

Deployment Tivoli Provisioning Manager V7.2 (including all TPM prerequisites)

TPM is used to deploy Enterprise POS software to servers and clients. This is in the Enterprise POS package.

Middleware WebSphere Remote Server 7.1.1 Solution Installer

This is the primary middleware for server installations, such as the HO and ISP. Installs the following:

IBM WebSphere Network Deployment 7.0.0.17 with JDK 1.6 SR9 FixPack 1

IBM DB2 Universal Database Workgroup Edition 9.7.0.4

IBM WebSphere MQ 7.0.1.6

Middleware

IBM WebSphere Application Server Community Edition 2.1.1.6

https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?lang=en_US&source=wsced_archive&S_PKG=dl

*You must have an IBM ID to download

A license-free lightweight JEE application server based on open standards.

Required for OLC POS terminals.

This software is not provided and must be downloaded if you intend on using OLC POS terminals.

Middleware

IBM DB2 Express V9.7.0.4 Required for OLC POS terminals. This is in the Enterprise POS package.

Web Browser

Internet Explorer Version 8.x Required to use Configurator, POS Manager, TPM, and other software.

Miscellaneous

Java API for XML Web Services(JAX-WS) Reference Implementation Version 2.1.7

https://jax-ws.dev.java.net/2.1.7/JAXWS2.1.7-20090419.jar

Open source JAVA code used by the application. Must be downloaded and installed as a prerequisite to deploying SAP Enterprise POS.









February 2012 17

Support tool Introscope Wily Agent SAP standard root cause analysis tool primarily for J2EE-Based products. Monitors performance, JVM status, and other status of pre-defined services. This tool is included in the Enterprise POS package.

Support tool SAP Solution Manager Diagnostics (SMD) Agent

SAP standard root cause analysis tool. Provides read-only access on remote system. Allows support personnel to view and track changes on files. This tool is included in the Enterprise POS package.

Miscellaneous SAPCAR SAP archive utility required to extract the contents of SAR archive files.

Miscellaneous N/A Any other third-party applications that integrate with SAP Enterprise POS must already be in place before installation. This includes software for functions like postal code lookup service, or customer service.

Port Settings The following ports are the default communication ports that must be available for SAP Enterprise POS. It is possible, but not recommended, to customize these values:

Protocol Source Port Destination Port

From To

WebSphere MQ TCP 1414 Any HO ISP

TCP Any 1414 ISP HO

WebSphere Application Server

TCP Any 2809 POS ISP

TCP 9060 Any ISP Any

TCP 9080 Any ISP Any

TCP 80 Any ISP Any

DB2 TCP 51000 Any ISP HO

Installation Guide

18 February 2012

TCP Any 51000 HO ISP

Wily Agent TCP 6001 6001 HO/ISP Wily EM server

SMD Agent TCP 50004 50004 HO/ISP SMD server

Tivoli Provisioning Manager Node A Tivoli Provisioning Manager (TPM) V7.2 server must be available to deploy SAP Enterprise POS. This server cannot be used to run SAP Enterprise POS, it can be used only to deploy it. Installation instructions are available from IBM Publication Tivoli Provisioning Manager Version 7.2 Installation Guide for Windows and Tivoli Provisioning Manager Version 7.2 Installation Guide for SUSE Linux.

Tivoli Provisioning Manager Depot Node As the TPM instructions state, there must be at least one server configured to act as a depot server if you want to distribute software using the scalable distribution infrastructure (SDI). You must, at a minimum, configure the EPOS HO node as a TPM Depot Server. SAP recommends that in addition to the HO node, all ISP nodes be configured as a TPM Depot Server also.

Security and Technical User IDs

During the installation, you are prompted to enter security information, including a user ID and password. The user ID is the primary operating system user for the application and middleware. This user is not a business user, and is not able to log on to the Configurator or POS Manager.

Recommendations for security settings:

Currently, SAP Enterprise POS does not have a centralized key management utility. This means that to ensure that encryption/decryption works in both directions, each store must import the head office key, and the head office must import the store key. Any changes to keys (rotation) must also be imported into the proper key container. This is currently a manual process.

We recommend that you use only one set of encryption keys. This dramatically simplifies the maintenance, and is compliant with PCI DSS. SAP installation scripts do this. For information about creating additional keys, see the SAP Enterprise POS Security Guide in the SAP Service Marketplace.

When prompted for a password, ensure that it meets your security guidelines. For example, if your security policy says that your passwords must be 8 characters long or include some special characters, then the default password,

trivers, does not work.

Be aware of password expiration. If your security policy automatically terminates passwords, this must be addressed before expiration.

For further information about security and technical user IDs, see the SAP Enterprise POS Security Guide in the SAP Service Marketplace.


February 2012 19

Configuration Checklist Use the following checklist to gather the configuration settings needed to perform a successful installation of SAP Enterprise POS:

Setting Values Comment

TE.TOPOLOGY.TYPE HO-POSM

HO-POSM-FO

The topology governs which software components run where. Currently, the two options are HO-POSM (Head Office POS Manager) and HO-POSM-FO (Head Office POS Manager with failover). The difference between the two is that with HO-POSM-FO, the POS Manager component is available at the head office to be used as a failover target for store servers.

TE.NODE.TYPE HO or ST The node type determines the overall purpose of the SAP Enterprise POS server. HO implies the server is installed at a central location and handles centralized services such as POS Manager, transaction log aggregation, or customer database. ST implies the server is installed for the purpose of operating an actual store. This setting is determined during the TPM installation, and you do not need to set it.

ORG. ID Text, 32 alphanumeric characters or less

The organization name is used to group data and configuration parameters.

SITE ID Text, 32 numeric characters or less

The site identifier uniquely identifies an instance of a SAP Enterprise POS server.

Use MDI True or false MDI is a feature that allows master data to be delivered across the enterprise using DB2 UDB replication. If MDI is not used, master data is delivered using JMS messaging.

Is OLC True or false OLC is a feature that allows the clients (registers) to operate in situations where the primary or secondary servers are unavailable.

Installation Guide

20 February 2012

Preparing the Installation Image Repository (Linux TPM) The installation image location is referred to in this document by the label TE_INSTALL_ROOT.

Label Default Linux Path Default Windows Path

TE_INSTALL_ROOT /opt/sap/te C:\sap\te

Perform this step on the TPM server running on the Linux platform as the root user.

1. Create the TE_INSTALL_ROOT directory.

host name~#> mkdir -p /opt/sap/te

host name~#> chown -R tioadmin:tioadmin /opt/sap

host name~#> logout

Perform these steps on the TPM server as the tioadmin user:

2. Copy and extract the SAP Enterprise POS software image to the directory created in the first step.

Assuming the installation media is a DVD and mounted at /media/dvd, execute the

following commands:

tioadmin@host name:~> cd /opt/sap/te

tioadmin@host name:/opt/sap/te> cp /media/dvd/TESERVER07_0.sca

.

tioadmin@host name:/opt/sap/te> unzip -j TESERVER07_0.sca

DEPLOYARCHIVES/is~isr~epos~te_deliver.sda

tioadmin@host name:/opt/sap/te> unzip

is~isr~epos~te_deliver.sda build/*

Verify that a directory build now exists in the /opt/sap/te directory.

3. Copy the middleware installer images from the installation media to the

TE_INSTALL_ROOT directory. The middleware required varies depending on the OS

platform being used for the SAP Enterprise POS installation. For the target OS platform copy the whole folder shown in the following table:

Windows Installer Linux Installer

IBM_WRS_V7.1.1_SolutionInstaller_Win_x6

4 IBM_WRS_V7.1.1_SolutionInstaller_

Lnx_x64


6

If the installation media is a CD, the files are on separate CDs and you must switch CDs between the file copy steps listed above.

4. Pre-Installation steps require Java Virtual Machine version 1.5.0. The TPM 7.2 installation includes the IBM WebSphere Application Server 6.x containing the required Java Virtual Machine. That Java Virtual Machine can be used for performing pre-

installation steps. Open a command prompt and set the JAVA_HOME and PATH

environment variables based on the location of the JRE installed with TPM 7.2 server. This example uses the default TPM 7.2 installation:


February 2012 21

tioadmin@host name:/opt/sap/te> export

JAVA_HOME=/opt/IBM/WebSphere/AppServer/java


PATH=$JAVA_HOME/bin:$PATH

5. Copy the JAXWS 2.1 reference implementation to the TE_INSTALL_ROOT directory. For

more information, see Software.

6. Extract the contents of the JAXWS 2.1 reference implementation using the following commands:

tioadmin@host name:/opt/sap/te> export LANG=en_US.ISO-8859-1

tioadmin@host name:/opt/sap/te> java –jar JAXWS2.1.7-

20090419.jar

The license acceptance window appears. Read and accept the license agreement to complete the extraction.

7. Set the value of the JAXWS21_HOME environment variable.


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

8. Create an EXTERNAL directory under TE_INSTALL_ROOT.

tioadmin@host name:/opt/sap/te> mkdir EXTERNAL

9. Put all relevant middleware required for POS and OLC images in the EXTERNAL

directory. The middleware required varies depending on the OS platform being used for the SAP Enterprise POS installation. The preinstall script fails if required middleware is missing.

File Required By Description Installation Media Location

AppClient70-FP17-SDKSR9FP1.zip

Windows POS, Windows OLC

WebSphere Application Client and JRE for Windows

OLC_REGISTER

wasce_setup-2.1.1.6-win.exe Windows OLC WebSphere CE Installation Image for Windows

Third-party download. See Software for known download sites.

DB2Exp-97FP4-Win-x86.zip Windows OLC DB2 Express Installation Image for Windows

OLC_REGISTER

When you download WASCE, you are accepting the license for and downloading open-source software from IBM. This software is distributed automatically, within SAP's installation process, to all POS terminals that you designate as offline capable clients.

10. Place all relevant software required for Wily agent and SMD agent in the EXTERNAL

directory. The preinstall script fails if Wily and SMD agents are chosen for installation but

Installation Guide

22 February 2012

required software is missing. See SAP Note 797147 for more details on Wily agent software download and configuration instructions and troubleshooting.

File Required By Description

SAPCAR.exe Windows SMD Agent Windows Wily Agent

SAPCAR archive utility for Windows

SAPCAR_0-10003688 Linux SMD Agent Linux Wily Agent

SAPCAR archive utility for Linux

ISAGENTSTD02_4-10007435.SAR Linux Wily Agent Windows Wily Agent

Wily Agent for Linux and Windows

j2sdk-1_4_2_19-linux-i586.bin Linux SMD Agent JDK 1.4.2 required for SMD Agent Linux installation

j2sdk-1_4_2_19-windows-i586-p.exe Windows SMD Agent

JDK 1.4.2 required for SMD Agent Windows installation

51033511_4.zip Linux SMD Agent SAP Installation master for Linux

51033511_11.zip Windows SMD Agent

SAP Installation master for Windows

51033507_9.zip Linux SMD Agent NW7.0 SR3 Kernel for Linux


NW7.0 SR3 Kernel for Windows

SMDAGENT15_0-20003546.SAR Linux SMD Agent Windows SMD Agent

SMD Agent for Linux and Windows

11. Execute the command to configure building in a Linux environment.

tioadmin@host name:~> cd /opt/sap/te/build/utils

tioadmin@host name:/opt/sap/te/build/utils> sh

setupPlatform.sh

Preparing the Installation Image Repository (Windows TPM) During the preparation tasks, note that the environment variables required to be set in the following steps are not persistent in the Windows command prompt. If you log out or exit the command prompt before the completion of the preparatory steps, the environment variables must be set again before the preparation tasks of the Installation Image Repository can be resumed. Similarly, you can set the environment variables permanently on Windows through the System Properties dialog box (Advanced tab). For more information about the System Properties dialog box on Windows, refer to the Windows OS documentation.

The installation image location is referred to in this document as TE_INSTALL_ROOT.

Label Default Windows Path

TE_INSTALL_ROOT C:\sap\te

1. Log on to Windows as the tioadmin user.

2. Create the TE_INSTALL_ROOT directory.

3. Copy the build archive named TESERVER07_0.sca to the TE_INSTALL_ROOT directory.


February 2012 23

4. Extract the file is~isr~epos~te_deliver.sda from the build archive to the directory

created in above. A utility such as unzip, winzip, or winrar can be used to extract from

the .sca or .sda files.

5. Extract the directory named build and all of its contents from the file in the above step

to the directory created in step 2. At this point you should have extracted the SAP

Enterprise POS build and have the directory c:\sap\te\build.

6. Copy the middleware installer images from the installation media to the

TE_INSTALL_ROOT directory. The middleware required varies depending on the OS

platform being used for the SAP Enterprise POS installation. For the target OS platform copy the whole folder shown in the following table:

Windows Installer Linux Installer


4 IBM_WRS_V7.1.1_SolutionInstall

er_Lnx_x64


6

If the installation media is CD, the files are on separate CDs and you must switch CDs between the file copy steps listed above.

7. Pre-Installation steps require Java Virtual Machine version 1.5.0. The TPM 7.2 installation includes the IBM WebSphere Application Server 6.x containing the required Java Virtual Machine. That Java Virtual Machine can be used for performing pre-installation steps. Open a command prompt and set the JAVA_HOME and PATH environment variables based on the location of the JRE installed with TPM 7.2 server. This example uses the default TPM 7.2 installation.

C:\sap\te>set JAVA_HOME=C:\Program

Files\IBM\WebSphere\AppServer\java

C:\sap\te>set PATH=%JAVA_HOME%\bin;%PATH%

8. Verify that the JAVA_HOME and PATH are set correctly by entering java –version.

Ensure that the command returns java version 1.5.0.

9. Copy the JAXWS 2.1 reference implementation (as noted in the software section above)

to the TE_INSTALL_ROOT directory.

10. Extract the contents of the JAXWS 2.1 reference:

C:\sap\te>java -jar JAXWS2.1.7-20090419.jar

The license acceptance window appears. Read the agreement from the top to the bottom and accept the license agreement to complete the extraction.

11. Set the value of the JAXWS21_HOME Environment Variable:

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

Installation Guide

24 February 2012

12. Create the EXTERNAL directory under TE_INSTALL_ROOT:

C:\sap\te>mkdir EXTERNAL

13. Put all relevant middleware required for POS and OLC images in the EXTERNAL

directory. The middleware required varies depending on the OS platform being used for the SAP Enterprise POS installation. The preinstall script fails if required middleware is missing.

File Required By Description Installation Media Location

AppClient70-FP17-SDKSR9FP1.zip

Windows POS, Windows OLC

WebSphere Application Client and JRE for Windows

OLC_REGISTER

wasce_setup-2.1.1.6-win.exe Windows OLC WebSphere CE Installation Image for Windows

Third-party download. See Software for known download sites.

DB2Exp-97FP4-Win-x86.zip Windows OLC DB2 Express Installation Image for Windows

OLC_REGISTER

When you download WASCE, you are accepting the license for and downloading open-source software from IBM. This software is distributed automatically, within SAP's installation process, to all POS terminals that you designate as offline capable clients.

14. Put all relevant software required for Wily agent and SMD agent in the EXTERNAL

directory. The preinstall script fails if Wily and SMD agents are chosen for installation but required software is missing. See SAP Note 797147 for more details on Wily agent software download and configuration instructions and troubleshooting.

File Required By Description

SAPCAR.exe Windows SMD Agent Windows Wily Agent

SAPCAR archive utility for Windows

SAPCAR_0-10003688 Linux SMD Agent Linux Wily Agent

SAPCAR archive utility for Linux

ISAGENTSTD02_4-10007435.SAR Linux Wily Agent Windows Wily Agent

Wily Agent for Linux and Windows

j2sdk-1_4_2_19-linux-i586.bin Linux SMD Agent JDK 1.4.2 required for SMD Agent Linux installation

j2sdk-1_4_2_19-windows-i586-p.exe Windows SMD Agent

JDK 1.4.2 required for SMD Agent Windows installation

51033511_4.zip Linux SMD Agent SAP Installation master for Linux


SAP Installation master for Windows

51033507_9.zip Linux SMD Agent NW7.0 SR3 Kernel for Linux


NW7.0 SR3 Kernel for Windows


February 2012 25

SMDAGENT15_0-20003546.SAR Linux SMD Agent Windows SMD Agent

SMD Agent for Linux and Windows

15. Execute the command to configure building in a Windows environment. Assuming that

TE_INSTALL_ROOT is C:\sap\te\, open a command prompt and execute the

following commands from the command line:

C:\>cd c:\sap\te\build\utils

C:\sap\te\build\utils\>setupPlatform.bat

Installation Guide

26 February 2012

Customizing the SAP Enterprise POS Installation Certain files in SAP Enterprise POS are customizable. The look and feel of the POS Client and the configuration profiles are some examples. Other examples are listed in the SAP Enterprise POS User Exit Guide In the SAP Expert Knowledge Corner.

Cloning Customizable Files The files shipped with SAP Enterprise POS are the default installation files. During installation, each retailer is expected to customize these files as necessary. Rather than modifying the supplied default configuration files, follow the steps below to make a clone of the customizable files.

The primary benefit of this approach is that when a new build or patch is received from SAP, the customer’s customized files are not overwritten. The preinstall script ensures that the customized files are delivered to the necessary Enterprise POS nodes for installation.

Use

To create a clone of SAP Enterprise POS customizable configuration files.

Prerequisites

You have read through and completed the tasks listed in Preparation.

Ensure that the following environment variables are set to their respective paths before running

the clone_custom script: JAVA_HOME, JAXWS21_HOME, and PATH. Refer to the steps outlined

in Preparing Installation Image Repository (Linux or Windows depending on the chosen OS platform) with regard to setting/exporting the environment variables.

Procedure

Execute the clone_custom (.bat for Windows, .sh for Linux) script to clone the customizable

SAP-Delivered files to a customer-specific folder.

Linux

sh /opt/sap/te/build/deployment/clone_custom.sh

Windows

C:\sap\te\build\deployment\clone_custom.bat

The customizable files are in the config directory of TE_INSTALL_ROOT. The retailer can

customize these files as needed.

Integrating with a Loyalty Provider Before running the SAP Enterprise POS installation, if you are integrating with a loyalty provider (for example, with SAP Loyalty Solution), you must configure the address of the loyalty provider

machine in the file called services.properties. Furthermore, the machine name for the SAP

Loyalty Solutions machine must be present in the /etc/hosts file on the head office server.

Use

To customize SAP Enterprise POS to integrate with SAP Loyalty Solution.

Prerequisites


You have identified the IP address of the SAP Loyalty Solutions machine. You have also identified the naming lookup string for the real-time service. This can be found on the SAP Loyalty


February 2012 27

Solutions machine under C:\Program Files\SAP\Analytics\Realtime in the file

a1to1.props.

Procedure

In the example below, the IP address of the SAP Loyalty Solution is 12.345.67.8, its name is

LOYSOLN, and the naming lookup string is a1to1XML.Replace these values with the correct

ones for your system.

1. Using a text editor of your choice, open the services.properties file from the

CUSTOM_DIR/custom/ear/framework directory. The <custom dir> is the directory

you created during the Customizing the SAP Enterprise POS Installation.

2. The following requires editing within the services.properties file:

loyaltyProviderFactory.namingLookup=//12.345.67.8/a1to1XML

3. Ensure that the host name LOYSOLN can be resolved either by DNS or through the hosts

file. To resolve using the hosts, edit the file:

Linux

/etc/hosts

Windows

C:\windows\system32\etc\drivers\hosts

4. The following requires editing within the hosts file:

12.345.67.8 LOYSOLN

Updating the device.properties File Before running the SAP Enterprise POS installation, you can change the default settings in the

device.properties file to further customize your installation. For example, if your registers

are equipped with MICR readers, the claim timeout and the begin removal timeout settings in the

device.properties file might need to be adjusted.

Use

To customize SAP Enterprise POS using the settings in the device.properties file.

Prerequisites


Procedure

1. Using a text editor of your choice, open the device.properties file from the following

directory:

Linux

/opt/sap/te/config/client

Windows

C:\sap\te\config\client\

2. Change the required settings in the device.properties file. The functionality of each

setting is described in the comments.

Installation Guide

28 February 2012

Preinstallation Before installation can begin, SAP Enterprise POS must be integrated with third-party software that was downloaded as part of preparation in the previous section. The preinstallation steps also work with Tivoli Provisioning Manager(TPM) to create a solution that can be installed from the TPM administration console. At the end of this section you should be ready to install SAP Enterprise POS to servers in the enterprise.

Running the Preinstallation Script

Use

Run the preinstall script to prepare for a TPM installation. Perform the appropriate procedure

depending on your operating system. A log file (Pre_Install.log) is generated for the

preinstallation process and can be found in:

Linux

/opt/sap/te/build/deployment

Windows

C:\sap\te\build\deployment

Prerequisites

You have read and completed the previous sections.

The TPM server must be started before commencing the preinstallation script. For more information about starting, stopping, and verifying the status of the TPM server, see IBM’s TPM Version 7.2 Installation Guide.

In a Windows environment, each machine where EPOS is installed must already have a user that has administrative privileges. This user must be used when defining the various users and passwords for servers running Windows.

Procedure

Perform the following steps on the TPM server as the tioadmin user.

1. Navigate to the SAP Enterprise POS deployment directory and execute the preinstall script using the following commands:

Linux

tioadmin@host name:~/> cd /opt/sap/te/build/deployment

tioadmin@host

name:/opt/sap/te/build/deployment>./preinstall.sh

Windows

C:\>cd \sap\te\build\deployment

C:\sap\te\build\deployment>preinstall.bat

2. Perform the security configuration.

a. Set up the key storage file password and the key export password.

The key storage password is used to protect the key store. A user or application must provide the correct key storage file password to access any key from the key store.


February 2012 29

After the key is created in the key store, it is exported to an export file for exchange in the future, for example, to import this key into another key store. This export file is protected by the export password. Whenever a user wants to access the export file, this password is verified.

A root user cannot be used. The installation fails if a root user is used.

b. Set up the user names and passwords listed below. The default value is

enclosed in brackets ([ ]) and is used if you press ENTER without any input.

The user names and passwords must conform to the IBM DB2 user name and password requirements.

i. [inputsequence] te.jdbc.admin.password [trivers]

This password is used for the DB2 user account which gets created during the installation of WebSphere Remote Server. The DB2 user account modified on Windows installations is db2admin, and db2inst1 on Linux installations. It is

referred to as JDBC_ADMIN_USER in the SAP Enterprise POS Installation

Guide.

On Windows, the password requirement is set by the domain policy and thus might be stronger (or weaker). The Windows administrator should be consulted for the password policy. There is no such limitation on Linux.

ii. [inputsequence] te.user.name [trivers]

This is the user that the SAP Enterprise POS application runs under. A local operating system user account is created during installation with this name. It is

referred to as TE_USER in the SAP Enterprise POS Installation Guide.

As dictated by DB2, the te.user.name should be limited to 8

characters on Linux. If you plan to run any server on Linux (head office server, store server or OLC server) in your landscape, you must limit

te.user.name to 8 characters. The te.user.name password should

be limited to 20 characters on Windows.

iii. [inputsequence] te.user.password [trivers]

The password for the te.user.name account is set to this value.

On Windows, the password requirement is set by the domain policy and thus might be stronger (or weaker). The Windows administrator should be consulted for the password policy. There is no such limitation on Linux.

3. Select the type of topology to use for this installation.

a. Choose whether you are deploying the IBM middleware to Windows, to Linux sites, or both. Make the selection based on the operating system that is used on the SAP Enterprise POS servers.

b. Indicate if you plan OLC register installations.

c. Indicate if you plan POS register installations.

d. 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.

e. Select the operating system types to support for Wily agent installations. Make the selection based on the operating system that are used on the SAP Enterprise POS servers.

Installation Guide

30 February 2012

f. The preinstall script runs without any further input. Ensure that the script terminates successfully.

Prepare Tivoli Provisioning Manager This section serves as a tutorial for deploying SAP Enterprise POS using Tivoli Provisioning Manager (TPM). Techniques shown here should be adapted to your unique situation. Only features relevant to a simple deployment scenario are discussed.

Overview

1. Discover computers.

2. Install depot agents on discovered computers.

3. Install Tivoli common agents on discovered computers.

4. Modify TPM workflow Local_Execute_Command (optional).

5. Define Head Office Computers.

6. Define Store Server Computers.

7. Define Registers.

Discovering Computers

TPM provides an easy and efficient means for discovering devices that are accessible over the network from the TPM server. There are various discovery methods depending on the device you are trying to discover.

Use

To discover the computers that TPM uses to deploy SAP Enterprise POS.

Prerequisites

You have completed the previous section

Linux machines to be discovered are running and are accessible via the network and have the default umask set to 0022

Windows machines to be discovered are running and have Windows networking running

All machines must meet the Tivoli Provisioning Manager discovery requirements. The requirements are documented by IBM and available on the Internet at the following URL:

http://publib.boulder.ibm.com/infocenter/tivihelp/v45r1/topic/com.ibm.tivoli.tpm.scenario.doc/discovery/rcom_checklist.html

Procedure

1. Using a Web browser, open the Tivoli Web Console logon at the URL shown, where

<tpm_host> is the fully qualified host name of the server where TPM is installed. IBM

recommends Firefox as the preferred Web browser.

https://<tpm_host>:9443/maximo

2. The Web browser’s security error dialog box appears, indicating an issue with the security certificate. To proceed to Tivoli Web Console, click OK or YES, depending on the Web browser.

3. On the Logon popup window, enter a valid user ID and password. The initial user ID and password were set during the TPM 7.2 installation using installation media. By default, the

TPM installation uses maxadmin as the user ID.




February 2012 31

4. After logging on, using navigation links at the right top corner, choose Go To Discovery Provisioning Discovery Discovery Configuration.

5. The Discovery Configurations window appears. Search for the discovery configuration called Initial Discovery and click on it in the search result list. The Discovery Configuration Details screen under the Discovery tab appears.

6. Click the IP Address Ranges tab and then New Row. In the Details section, enter the Start and End of an IP address range that contains EPOS servers and POS registers. Click Save at the top of the screen to save your changes. For a single IP, enter the same IP for the start and end. Repeat for multiple address ranges.

7. Click the Credentials tab and then New Row. In the Password Credentials section enter the user ID and password. After each set of credentials, click New Row.

a. For Linux servers: enter the User Name and Password for the root user from the machine. Ensure the Protocol is set to SSH mechanism.

b. For Windows servers: enter the User Name and Password for the user with administrator privileges from the machine. Ensure the Protocol is set to SMB mechanism.

8. Click Save.

9. Repeat steps 6 and 7 for any other EPOS servers or clients that were not in the original configuration. For example, if adding servers or clients after the initial configuration or for servers or clients that were forgotten originally.

10. Click Run Discovery.

11. In the Run Discovery popup window enter the name for the discovery task in the Provisioning Task field. You can set scheduling and notification options as desired. Click Submit to initiate the discovery.

12. The Provisioning Task Tracking window displays the new discovery task. You can display detailed information by clicking the icon on the right of the line item. Click Refresh to update the task until it is finished.

13. A successful result displays a green bar with a 100 percent success and Workflow Status is set to Succeeded. If there is a failure, click View Details next to the provisioning workflow Discovery. Discover and check the error. Refer to the following TPM documentation to help troubleshoot discovery problems: http://publib.boulder.ibm.com/infocenter/tivihelp/v45r1/topic/com.ibm.tivoli.tpm.scenario.doc/discovery_troubleshooting/tcom_troubleshooting.html.

14. To display the discovered servers: Click the icon next to the Known Resources field. The Provisioning Computers screen appears. Ensure that all of the computers you intend to find are displayed. Note the host name of each computer. From this point, any SAP Enterprise POS installation-related tasks in the Tivoli Web Console that require the host name of the computer must match the host name of the computers found here. To go back to the Provisioning Task Tracking window click the Return link in the right top corner.

15. Proceed to Install Depot Agent.

Occasionally, situations will arise when servers discovered by TPM have to be reimaged. As the servers were already registered with TPM and have software installed, certain precautionary steps must be taken on the TPM server side to ensure proper cleanup. In addition to re-installing software, the servers must also be re-discovered by TPM. To do so, perform the following steps after server

reimaging: 1) If the TPM server is running in the Linux environment, clean the SSH cache.

To clean the cache, logon to the TPM server as the TPM Administrator user

(default name is tioadmin). Navigate to the .ssh directory located under

the TPM Administrator user home directory:

http://publib.boulder.ibm.com/infocenter/tivihelp/v45r1/topic/com.ibm.tivoli.tpm.scenario.doc/discovery_troubleshooting/tcom_troubleshooting.html

http://publib.boulder.ibm.com/infocenter/tivihelp/v45r1/topic/com.ibm.tivoli.tpm.scenario.doc/discovery_troubleshooting/tcom_troubleshooting.html

Installation Guide

32 February 2012

tioadmin@host name:~/> cd ~/.ssh

Use the editor of your choice to remove the entry of the reimaged server IP

address from the known_hosts file.

2) Log on to the TPM Web Console, and navigate to Go To Deployment Provisioning Computers. The Provisioning Computers window appears.

3) Find the reimaged computers and delete them by clicking Delete Computer on the right side of each row.

4) Start the computer discovery process as it is described in this section.

TPM does not allow software products, including TCA agents and depot agents, to be installed on discovered computers if the clock of the TPM server and the clocks of the discovered computers are desynchronized by more than two hours. Ensure that the clocks on the computers discovered by TPM are synchronized with the clock on the TPM server.

Installing Depot Agent

TPM uses a depot server as part of its scalable distribution architecture. There can be many depots as part of the infrastructure, and these can be grouped into regions, depending on your particular needs. You must plan your placement of depot servers carefully. For more information, see Tivoli Provisioning Manager Node and the TPM information center for a full discussion on planning for scalable distribution. You must configure at least one depot server.

If you intend to install and distribute the SAP Enterprise POS register software using TPM, we recommend you install the Depot Agent at the head office and on every store server. As a minimum requirement, the Depot Agent must be installed at the head office.

Use

To set up a TPM region and depot server by creating a region and installing the Depot Agent to the computers discovered in the Discovering Computers section.

Prerequisites

You have completed the previous section.

Procedure

Perform these procedures as the maxadmin user on the TPM server.

1. If necessary, open the Tivoli Web Console logon at the URL shown. <tpm_host> is the

fully qualified host name of the server where TPM is installed.


2. Choose Go To Administration Provisioning Dynamic Content Delivery Configuration. The Dynamic Content Delivery Configuration window displays. Select the Regions tab window and click New Row.

3. Choose Edit and then select Add Region.

4. Enter values for the Name and Description fields. In this scenario, use the following values:

a. Name – Test Region

b. Description – SAP EPOS Test Lab

5. Click Save to continue, and then select the Depots tab window.

6. On the Depots tab window, click New Row.


February 2012 33

7. Complete the Depot details section:

a. In the Depot field enter a name for the depot server. It can be any name to identify that server, for example HO Depot or ST 1 Depot.

b. In the Region field, select the region. This is the region the new depot server will be assigned to. It must be set to the value created previously.

c. To use a computer that has already been discovered, click the Detail Menu icon next to the Computer filed. In the Select Value popup window perform a computer search and click on it.

d. After selecting the computer, most fields are filled.

e. In the Credentials section, select the Install the depot agent services checkbox and provide a User Name and Password for the depot server. On Linux servers, specify the root user and password. On Windows servers, specify the predefined install user and password that is a member of the Administrators group.

f. In the Distribution Configuration section select the Preferred upload server checkbox and specify a Data Directory Limit. The default value for the data directory limit of 2000MB is not sufficient. 8000MB is the preferred value to use for this scenario.

g. Leave the rest of the fields at their default values.

h. Click Save.

8. A task is added to the Provisioning Task Tracking window that shows the completion status of the Depot Agent installation. Ensure that the Depot Agent is installed by refreshing the results until the results are shown as successful for the task.

9. Repeat steps 2 to 9 for each EPOS server until the Depot Agent is installed on all of the configured EPOS servers. If you use only one region, then you can omit steps 3 and 4.

10. Proceed to Installing Tivoli Common Agent.

Installing Tivoli Common Agent

You must install the Tivoli Common Agent (TCA):

On any computer that is managed by TPM except for the previously defined depot servers. Depot servers already have the common agent installed as part of the Depot Agent installation

On any SAP Enterprise POS server that does not have the Depot Agent installed

On any POS register that is installed using Tivoli Provisioning Manager.

Use

To install the TCA on the required SAP Enterprise POS servers and registers.

Prerequisites

The servers and registers have been discovered using TPM.

Procedure

1. Using a supported Web browser, open the Tivoli Web Console logon at the URL shown,

where <tpm_host> is the fully qualified host name of the server where TPM is installed.


2. Choose Go To Deployment Software Management Common Agent Installation. The Install Common Agent window displays. In the Common Agent Stacks section click the Tivoli Common Agent Stack for the task. Choose Select Computers and in the Select Computers popup window find and select one or more target computers for the task, then click OK. You cannot install the TCA on the TPM server itself (the host name of the TPM server appears on the list of computers).

Installation Guide

34 February 2012

3. Configure Install Options.

a. Ensure that the root (Linux) or administrators group (Windows) credentials are supplied for the servers and registers on which the agent is installed. By default, the TPM uses credentials provided for the initial computer’s discovery. If the credentials differ from those required, new credentials must be created by clicking on the Credentials checkbox and filling in the User Name, Password and Confirm Password fields.

b. Choose the required scheduling and notification options.

c. Click Submit when you are finished.

4. A task is created and the progress is shown on the Provisioning Task Tracking window. Refresh the window and wait for the completion results to show 100 percent success. The Tivoli Web Console allows you to set the time interval to refresh itself automatically. On the top left corner of the window, choose the time interval from the drop-down list. It can be set to off, 5 seconds, 10 seconds, 20 seconds, 30 seconds, 60 seconds, or 90 seconds. By default, it is set to off. Alternatively, you can manually refresh the Web Console window by clicking the refresh link. If agent installation fails for any computer, troubleshoot the problem before continuing.

TPM does not allow software products, including TCA agents and depot agents, to be installed on computers if the clock of the TPM server and the clocks of the computers are desynchronized by more than two hours. Ensure that the clocks on the computers on which you plan to install the TCA are synchronized with the clock on the TPM server.

Modifying TPM Workflow Local_Execute_Command

If the TPM server is installed on a virtual machine or slower hardware, you might run into a known problem with a built-in Tivoli workflow that is used by SAP Enterprise POS installation. For more information, see Troubleshooting at the end of this guide to implement a workaround.

Defining the Head Office

Define the head office installation-specific properties for a specific server.

Use

To define the SAP Enterprise POS installation properties for a head office server. Settings for the SMD agent and Wily agent are optional.

Prerequisites

The head office server has been discovered using TPM.

Procedure

1. Using a Web browser, log on to the Tivoli Web Console logon at the URL shown, where

<tpm_host> is the fully qualified host name of the server where TPM is installed:


2. Choose Go To Administration Provisioning Provisioning Workflows. On the

Provisioning Workflows window search for the TE_DefineHeadOffice workflow.

3. When the workflow is found, click Run on the right side of the workflow row. The Run Workflow popup window displays.

4. Enter the appropriate values in the fields:

a. HeadOfficeHost name – Enter the fully qualified host name of the server where the head office is installed. Do not use the server’s IP address. Use the host name of the server as shown in the TPM discovered computers list (Go To Deployment Provisioning Computers).


February 2012 35

b. TopologyType – Enter the code for the topology type that this server and all store

servers connected to it use. Valid values are HO-POSM and HO-POSM-FO. Use the

same topology provided in Running the Preinstallation Script. See Configuration Checklist for topology features.

c. OrgID – The organization ID that is used for this server and all store servers

connected to it. The alphanumeric field default value is Triversity.

d. SiteID – The unique numeric identifier for this EPOS head office server.

e. UseMDI – Can be either true or false. Enables or disables the MDI feature. If deploying Centralized Store Servers, then the UseMDI option must be enabled. For more information about the MDI process, see Configuring Operational Data in the Post Installation section.

f. WilyEMServerIP – Enter the IP address of the Wily Enterprise Manager server. This allows the installation of the Wily agent on the EPOS head office server. To skip the Wily agent installation process, leave this field blank.

g. WilyEMServerPort – Enter the port number the Wily agent uses to communicate with the Wily Enterprise Manager server. Leaving this field blank defaults the port number to 6001.

h. SMDServerIP – Enter the host name of the Solution Manager Diagnostics server. This allows installation of the SMD agent on the EPOS head office server. To skip the SMD agent installation process, leave this field blank.

i. SMDServerPort – Enter the port number used by the SMD agent to communicate with the SMD server. Leaving this field blank defaults the port number to 50004.

j. SMDUserName – Enter the username logon required for the SMD agent to log on to the SMD server.

k. SMDUserPassword – Enter the password required for the SMD agent to log on to the SMD server.

5. Click Run to execute the workflow.

A workflow deployment task is generated and the workflow request is in the queue to start. Tivoli Web Console prompts you if you want to go to the Provisioning Task Tracking application to monitor the task. Click Yes to go to the Provisioning Task Tracking window where you can monitor the task execution status. Click Refresh to update the status and ensure that the workflow is successful. If it fails, click View Details on the workflow row next to the workflow name and then click Log in the opened Details section under the Targets tab. To go back to the Provisioning Workflows window click Return.

You can rerun the workflow if an incorrect setting was used to define the server. Run the workflow and specify the same head office host name you previously used.

You can define more than one head office by running the workflow and specifying a different head office host name.

Defining the Store

Define the store installation-specific properties for a specific server.

Use

To specify the SAP Enterprise POS installation settings for a store server. Settings for the SMD agent and the Wily agent are optional.

Prerequisites

The store server has been discovered using TPM

The head office server has been defined in TPM.

Installation Guide

36 February 2012

Procedure




2. Choose Go To Administration Provisioning Provisioning Workflows. In the Provisioning

Workflows window search for the TE_DefineStore workflow.



a. HeadOfficeHost name – Enter the fully qualified host name of the server that acts as the head office for this store. Do not use the server’s IP address. Use the host name of the server as shown in the TPM discovered computers list (Go To Deployment Provisioning Computers).

b. StoreHost name – Enter the fully qualified host name of the store server being configured. Do not use the server’s IP address. Use the host name of the server as shown in the TPM discovered computers list (Go To Deployment Provisioning Computers).

c. SiteID – The unique numeric identifier for this EPOS store server.

d. OLCServer – Can be either true or false. Enables or disables the replication support for OLC clients. You must set this to true if you want to set up OLC clients for this store.

e. WilyEMServerIP – Enter the IP address of the Wily Enterprise Manager server. This allows the installation of the Wily agent on the EPOS store server. To skip the Wily agent installation process, leave this field blank.

f. WilyEMServerPort – Enter the port number that the Wily agent uses to communicate with the Wily Enterprise Manager server. Leaving this field blank defaults the port number to 6001.

g. SMDServerIP – Enter the host name of the Solution Manager Diagnostics server. This allows installation of the SMD agent on the EPOS store server. To skip the SMD agent installation process, leave this field blank.

h. SMDServerPort – Enter the port number that the SMD agent uses to communicate with the SMD server. Leaving this field blank defaults the port number to 50004.

i. SMDUserName – Enter the user name logon required for the SMD agent to log on to the SMD server.

j. SMDUserPassword – Enter the password required for the SMD agent to log on to the SMD server.


A workflow deployment task is generated and the workflow request is in the queue to start. Tivoli Web Console prompts you if you want to go to the Provisioning Task Tracking application to monitor the task. Click Yes to go to the Provisioning Task Tracking window where you can monitor the task execution status. Click Refresh to update the status to ensure that the workflow is successful. If it failed, click View Details on the workflow row next to the workflow name and then click Log in the opened Details section under the Targets tab. To go back to the Provisioning Workflows window click Return.

6. Repeat the procedure for all store servers in the Enterprise.

You can rerun the workflow if an incorrect setting was used to define the server.

Defining the POS OLC Client

Define the client installation-specific properties for a specific server.


February 2012 37

Use

To specify the SAP Enterprise POS installation settings for a client.

Prerequisites

The POS client machine has been discovered in TPM

The store server to be used by the client has been defined in TPM

If a client fails over to a head office server, it has been defined in TPM.

Procedure





Workflows window search for the TE_DefineClient workflow.



a. Client_DeviceID – Enter either the host name of the client or its TPM device ID. Do not use the machine’s IP address. Use the host name of the machine as shown in the TPM discovered computers list (Go To Deployment Provisioning Computers).

b. isOLC – Can be either false or true. If the value is true the register configures for the OLC client installation.

c. Primary Server – Required. Enter the host name of the first server that the client attempts to connect to. Typically, the primary server is a store server, but it can be a head office, local host, or any other server configured for processing the

register transactions. The value, localhost, assumes that the server is a

WASCE server and that it can be used only if the register is offline-capable.

d. Primary Server JNDI Port – Optional. Enter the WebSphere JNDI port number of the primary server. If this field is left blank and the primary server is not

localhost, the WebSphere JNDI port number defaults to 2809. If this field is

left blank and the primary server is localhost, the WebSphere JNDI port

number defaults to 4201.

Define the primary server carefully as a mistake can result in a register connecting to a store server of another store. Although all registers in a store should ONLY connect to the primary store server, this is not restricted in the current installation process.

e. Secondary Server – Optional. The client uses this server only when the primary server is unavailable. Typically, the secondary server is a head office server but it can be a store, local host, or any other server configured for processing the register transactions. The way in which the local host value is used is the same as for the primary server.

f. SecondaryServerJNDIport – Optional. Follow the instructions for the primary server JNDI port.

g. ExtraServer – Optional. This server is used only when both the primary and the secondary servers are unavailable. Typically, this server is a local host but it can be a head office, a store, or any other server configured for processing the register transactions. The way in which a local host value is used is the same as for the primary server.

Installation Guide

38 February 2012

h. ExtraServerJNDIport – Optional. Follow the instructions for the primary server JNDI port.

i. StoreSiteID – Required. The numeric identifier of the store that this register uses to process transactions.

j. ClientID – Optional. The numeric identifier that determines the unique identity of the POS Client. If left blank, an automatically generated value is used.


6. A workflow deployment task is generated and the workflow request is in the queue to start. Tivoli Web Console prompts you if you want to go to the Provisioning Task Tracking application to monitor the task. Click Yes to go to the Provisioning Task Tracking window where you can monitor the task execution status. Click Refresh to update the status to ensure that the workflow was successful. If it failed, click View Details on the workflow row next to the workflow name and then click Log in the Details section under the Targets tab. To go back to the Provisioning Workflows window click Return.

7. Repeat the procedure for all registers that you install.

Defining Wily Agent (Optional)

Define the Wily agent installation-specific properties for a specific server.

Use

To specify the Wily agent installation settings for an SAP Enterprise POS server. Execute only if the Wily agent installation settings were omitted during the Defining Head Office or Defining Store tasks.

Prerequisites

SAP Enterprise POS head office or store server is installed on the target server

The targeted head office or store server for Wily agent installation is defined in TPM

The targeted head office or store server does not have Wily agent installed.

Procedure





Workflows window search for the TE_DefineWilyAgent workflow.

3. After the workflow is found, click Run on the right side of the workflow row. The Run Workflow popup window displays.


a. TEServerHost name – Enter the host name or DeviceID of the SAP Enterprise POS server targeted for Wily agent installation.

b. WilyEMServerIP – Enter the IP address of the Wily Enterprise Manager server. This allows the installation of the Wily agent on the SAP Enterprise POS store server.

c. WilyEMServerPort – Enter the port number that the Wily agent uses to communicate with the Wily Enterprise Manager server. Leaving this field blank defaults the port number to 6001.


6. A workflow deployment task is generated and the workflow request is in the queue to start. Tivoli Web Console prompts you if you want to go to the Provisioning Task Tracking application to monitor the task. Click Yes to go to the Provisioning Task Tracking window


February 2012 39

where you can monitor the task execution status. Click Refresh to update the status to ensure that the workflow is successful. If it failed, click View Details on the workflow row next to the workflow name and then click Log in the Details section under the Targets tab. To go back to the Provisioning Workflows window click Return.

7. Repeat the procedure for all SAP Enterprise POS servers where Wily agents are installed.

Defining SMD Agent (Optional)

Define the Solution Manager Diagnostics (SMD) agent installation-specific properties for a specific server.

Use

To specify the SMD agent installation settings for an SAP Enterprise POS server. Execute only if SMD agent installation settings were omitted during the Defining Head Office or Defining Store tasks.

Prerequisites

The SAP Enterprise POS head office or store server is installed on the target server

The targeted head office or store server for SMD agent installation is defined in TPM

The targeted head office or store server does not have the SMD agent installed.

Procedure





Workflows window search for the TE_DefineSMDAgent workflow.


4. Enter the appropriate value in the fields:

a. TEServerHost name – Enter the host name or DeviceID of the SAP Enterprise POS server targeted for SMD agent installation.

b. SMDServerIP – Enter the host name of the SMD server. This allows for installation of the SMD agent on the EPOS store server.

c. SMDServerPort – Enter the port number used by the SMD agent to communicate with the SMD server. Leaving the field blank defaults the port number to 50004.

d. SMDUserName – Enter the username logon required for the SMD agent to log on to the SMD server.

e. SMDUserPassword – Enter the password required for the SMD agent to log on to the SMD server.


6. A workflow deployment task is generated and the workflow request is in the queue to start. Tivoli Web Console prompts you if you want to go to the Provisioning Task Tracking application to monitor the task. Click Yes to go to the Provisioning Task Tracking window where you can monitor the task execution status. Click Refresh to update the status to ensure that the workflow is successful. If it failed, click View Details on the workflow row next to the workflow name and then click Log in the Details section under the Targets tab. To go back to the Provisioning Workflows window click Return

7. Repeat the procedure for all SAP Enterprise POS servers where SMD agents are installed.

Installation Guide

40 February 2012

Installation This section provides information, including step-by-step instructions, about how to install SAP Enterprise POS.

The SAP Enterprise POS installation process is a fully functional three-tier installation with minimal configuration.

Overview 1. Head office server installation.

2. Store server installation.

3. Wily agent installation (optional).

4. SMD agent installation (optional).

5. POS client installation.

Installing Head Office Server A SAP Enterprise POS head office server is required in all deployment models except the collapsed deployment model. The head office server aggregates all transaction data and runs the Configurator and POS Manager applications. If you define the Wily agent and SMD agent settings on the head office server, the head office server installation also includes the installation of the Wily and SMD agents.

Use

To install a head office server.

Prerequisites

All hardware and software requirements described in the previous sections are in place and functioning

Preinstallation steps are complete, including the head office server definition

The Depot Agent is installed on the server and acts as the head office server.

Procedure




2. Choose Go To Deployment Software Management Software Product Installation. The Software Product Installation window displays.

3. Install the head office server application:

a. Click Select Software. In the Select Software popup window use SAP Enterprise Software Module as the name for the product search. Select the software name SAP Enterprise POS Head Office 3.1.7 in the search result and click OK.

b. On the Software Product Installation window click the Select dropdown list and choose Computers. In the Select Computers popup window select the computer where the software is installed and click OK. The Software Product Installation window displays.

c. Configure the Scheduling or Notification options and click Submit.

4. An installation task is generated in the Provisioning Task Tracking window. Verify that the task complete before installing any store servers.

5. Reboot the server after a successful installation. This must be done before beginning EPOS Store Server installations.


February 2012 41

It can take up to 90 minutes or more for the installation to complete if the IBM WebSphere middleware must be installed.

If the Wily or SMD is part of the installation and their installation fails, see the Troubleshooting section for the required steps to take.

6. Perform the EPOS Head Office installation verification as it is described in the Install Verification part of this guide. The Verify MQ Channel Startup step can be omitted because there are no installed stores.

Installing Store Server A SAP Enterprise POS store server is used by POS Clients to process transactions. It is where all business logic is processed and store-specific data is kept. It also posts transactions to other store servers and head office servers. In some deployment models it also runs the POS Manager application. If you define the Wily agent and SMD agent settings on the store server, then the store server installation also includes the installation of the Wily and SMD agents.

Use

To install a store server.

Prerequisites

All hardware and software requirements outlined in the previous sections are in place and functioning

Preinstallation steps are complete

The store servers to be installed are defined

Tivoli Common Agent or Depot Agent is installed on the store server

A head office server is installed using TPM.

Procedure



https:// <tpm_host>:9443/maximo


3. Install the store server application:

a. Click Select Software. In the Select Software popup window use the SAP Enterprise Software Module name for the product search. Select SAP Enterprise POS Store 3.1.7 in the search result and click OK. The Software Product Installation window displays.

b. Click the Select dropdown list and choose Computers. In the Select Computers popup window select the computer where the software is installed and click OK. The Software Product Installation window displays.

c. Configure the Scheduling or Notification options and click Submit.

4. An install task is generated in the Provisioning Task Tracking window. Verify that the task is complete before installing any store servers.

5. Once the software is successfully installed, restart the EPOS Store Server.

It can take up to 90 minutes or more for the installation to complete if the IBM WebSphere middleware has to be installed.

Installation Guide

42 February 2012

If the Wily or SMD is a part of the installation and their installation fails, see Troubleshooting for steps that may be required.

6. Perform the EPOS Store Server installation verification as it is described in the Install Verification part of this guide. Also perform the Verify MQ Channel Startup at the EPOS Head Office.

Installing Wily Agent (Optional) The installation of Wily agents on the SAP Enterprise POS servers is optional. Typically, the Wily agent is installed as part of the SAP Enterprise POS head office or store server installation process. However, if the Wily agent was omitted during the head office or store server installation, it is possible to install the Wily agent as a separate installation task. The steps below describe this process.

Use

To install a Wily agent as a separate task.

Prerequisites

All hardware and software requirements in the previous sections are in place and functioning


The Tivoli Common Agent or Depot Agent is installed on the server targeted for Wily agent installation

Enterprise POS is installed using TPM on the targeted head office or store server

Wily agent installation settings are defined for the targeted head office or store server.

Procedure





3. Install the Wily agent application:

a. Click Select Software. In the Select Software popup window use the SAP Enterprise Software Module name for the product search. Select the software name SAP Enterprise POS Wily Agent Install 3.1.7 in the search result and click OK. The Software Product Installation window displays.


c. Configure Scheduling or Notification options and choose Submit.

4. An installation task is generated in the Provisioning Task Tracking window. Verify that the task is complete before installing any store servers.

To view details of the installation either while in progress or after a success or failure click Install Software Products from the Track Tasks window. This opens the Task Details window. Click Request ID to see the workflow execution log. The log file is useful for troubleshooting a failed installation.


February 2012 43

5. Perform Wily Agent installation verification as it is described in the Install Verification part of this guide.

Installing SMD Agent (Optional) Installation of SMD agents on SAP Enterprise POS servers is optional. Typically, the SMD agent is installed as part of the SAP Enterprise POS head office or store server installation process. However, if the SMD agent was omitted during the head office or store server installation, it is possible to install the SMD agent as a separate installation task. The steps below describe this process.

Use

To install a SMD agent as a separate task.

Prerequisites

All hardware and software requirements in the previous sections are in place and functioning


The Tivoli Common Agent or Depot Agent are installed on the server targeted for SMD agent installation

Enterprise POS is installed using TPM on the targeted head office or store server

SMD agent installation settings are defined for the targeted head office or store server.

Procedure





3. Install the SMD agent application:

a. Click Select Software. In the Select Software popup window use the SAP Enterprise Software Module name for the product search. Select the software name SAP Enterprise POS SMD Agent Install 3.1.7 in the search result and click OK. The Software Product Installation window displays.


c. Configure Scheduling or Notification options and click Submit.

4. An installation task is generated in the Provisioning Task Tracking window. Verify that the task is complete before installing any store servers.

To view details of the installation either while in progress or after a success or failure click Install Software Products from the Track Tasks window. This opens the Task Details window. Click Request ID to see the workflow execution log. The log file is useful for troubleshooting a failed installation.

5. Perform SMD Agent installation verification as it is described in the Install Verification part of this guide.

Installation Guide

44 February 2012

Installing the POS Register Tivoli Software Provisioning installs the SAP Enterprise POS Client software using the Tivoli Common Agent. The main advantage of this installation approach is the ability of Tivoli Provisioning Manager to reliably distribute and install the software across a wide area network. One drawback of this approach is that the register must already be staged with an operating system and have the Tivoli Common Agent installed and running. The client is the user interface for the cashier and runs on a cash register. There are two forms of the client; standard and offline capable (OLC). The standard client cannot continue processing transactions when the head office or store server is not available due to network outages or downtime.

An offline capable POS has greater hardware requirements to operate properly and ensure the cash register meets the minimum requirements for OLC operation.

Use

To install a POS Client on a computer.

Prerequisites

All hardware and software requirements described in the previous sections are in place and functioning

Javapos is installed on the POS registers. Contact your POS register vendor for more information on the specific requirements of javapos for the register


The client to be installed is defined

Tivoli Common Agent is installed on the client computer.

Procedure





3. Install the Client application:

a. Click Select Software. In the Select Software popup window use the SAP Enterprise Software Module name for the product search. Select the software name SAP Enterprise POS OLC Client 3.1.7 or SAP Enterprise POS Client 3.1.7.in the search result and click OK. The Software Product Installation window displays.


c. Configure Scheduling or Notification options and click Submit.

4. An installation task is generated in the Provisioning Task Tracking window.

5. Verify that the installation task is complete and restart the computer.

6. To start an OLC register, log out and log on as the install user.

7. To start a POS register, run the following script:

Linux

startpos.sh

Windows

startpos.cmd


February 2012 45

If you have a large number of registers you can benefit from using the TPM Scalable Distribution Infrastructure (SDI). It allows you to distribute software installable to the target computers prior to installation. See the TPM documentation for more details on SDI usage.

Installation Guide

46 February 2012

Installation Verification

Head Office Perform the steps described in the sections below to verify that a head office server is installed and running properly.

Verify WebSphere Application Server Log

As the TE_USER, check the log files for server errors:

Linux

$WAS_PROFILE_HOME/logs/server1/SystemOut.log

Windows

%WAS_PROFILE_HOME%\logs\server1\SystemOut.log

For information about possible errors that could be in the log files, see Troubleshooting.

Verify MQ Communication

1. Start the WebSphere MQ tool runmqsc.

Linux

Log on as the TE_USER and start runmqsc.

Windows

Log on as the predefined install user and start runmqsc from a command prompt window.

2. From the runmqsc tool, issue the command to check the channel status:

display chstatus(HEAD_OFF.*)

The output looks as follows:

AMQ8417: Display Channel Status details.

CHANNEL(HEAD_OFF.ST1_1) CHLTYPE(SDR)

CONNAME(CAYYZONONF3(1414)) CURRENT

RQMNAME(ST1_1) STATUS(RUNNING)

SUBSTATE(MQGET) XMITQ(ST1_1)


CHANNEL(HEAD_OFF.ST2_1) CHLTYPE(SDR)

CONNAME(10.6.214.31(1414)) CURRENT

RQMNAME(ST2_1) STATUS(RUNNING)

SUBSTATE(MQGET) XMITQ(ST2_1)

where HEAD_OFF.ST1_1 is the channel going from the head office server to the store server

deployed with site1.

HEAD_OFF.ST2_1 is the channel going from the head office server to the store server

deployed with site2. Only one head office-to-store channel is required for each store (site) server.

A channel with the status running appears after issuing the display command.

3. From the runmqsc tool, issue the command to check the publish/subscribe status:

display pubsub status



February 2012 47

AMQ8723: Display pub/sub status details.

QNAME(HEAD_OFF) STATUS(ACTIVE)


QNAME(ST1_1) STATUS(ACTIVE)


QNAME(ST2_1) STATUS(ACTIVE).

4. To exit the utility, enter END.

Verify Replication Startup

If MDI is enabled, verify that the replication process has started on the head office server.

1. On Linux servers, log on as the JDBC_ADMIN_USER. On Windows servers, log on as the predefined install user.

2. Verify the status of the replication process by running the following command from the

TE_HOME/deployment/replication directory:

Linux

./replication.sh status

Windows

replication.bat status

Location Output Meaning

Head office server

2009-11-25-12.31.58.740635 ASN0506E "AsnCcmd" : "MDI" : "Initial" : The command was not processed. The "Capture" program is presumed down.

The capture server is not started.

Store server 2009-11-25-15.32.11.635669 ASN0506E "AsnAcmd" : "MD1_1QLF" : "Initial" : The command was not processed. The "Apply" program is presumed down.

The apply server is not started.

Store server [exec] 2009-11-25-15.36.34.129441 ASN0506E "AsnCcmd" : "OLC" : "Initial" : The command was not processed. The "Capture" program is presumed down.

The capture server is not started.

3. If any of the replication processes are not running you can start them from the

TE_HOME/deployment/replication directory.

Linux

./launchReplication.sh

Windows

launchReplication.bat

where <TE_HOME> is the installation directory of SAP Enterprise POS software;

/opt/sap/te/product.

Store Server Complete the steps in the following sections to verify that a store server is installed and running correctly.

Verify WebSphere Application Server Log

As the TE_USER, check the log files for server errors:

Installation Guide

48 February 2012

Linux

$WAS_PROFILE_HOME/logs/server1/SystemOut.log

Windows

%WAS_PROFILE_HOME%\logs\server1\SystemOut.log

For information on some possible errors that may be in the log files, see Troubleshooting.

Verify MQ Communication

The MQ communication channel for sending messages from the store to the head office is configured to start once the first message arrives; after installation it is not running because there are no messages to process. To verify MQ communication at the store, that channel must be started first. Perform the following verification steps:

1. Start the WebSphere MQ tool runmqsc.

Windows

Log on as the predefined install user and start runmqsc from a command prompt window.

2. From the runmqsc tool, issue the command to start the channel:

start channel(STx_1.HEAD_OFF)

For centralized store servers that have multiple sites, each site must have a separate communication channel to the HO server. When a centralized store server has multiple sites, it is initially deployed with the site ID set in the define store process. This is the ID of the physical store server. Then, all individual sites are imported to the store during the hosted sites configuration steps described in the Post Installation section. Each of these sites must have its own channel connecting it to the HO server. The naming convention of the store-to-head office mq channel is:

STx_1.HEAD_OFF where x is the site ID used during the deployment of the store.

3. From the runmqsc tool, issue the command to check the channel status:

dis chstatus(ST*)



CHANNEL(ST1_1. HEAD_OFF) CHLTYPE(SDR)

CONNAME(CAYYZONONF3(1414)) CURRENT

RQMNAME(HEAD_OFF) STATUS(RUNNING)

SUBSTATE(MQGET) XMITQ(HEAD_OFF)

A channel with the status running appears after issuing the display command.

4. From the runmqsc tool, issue the command to check the publish/subscribe status:

Display pubsub status



QNAME(ST1_1) STATUS(ACTIVE)


February 2012 49


QNAME(HEAD_OFF) STATUS(ACTIVE)

If publish/subscribe status of the head office MQ manager called HEAD_OFF is not ACTIVE, the parent–child relation between head office and store MQ managers must be reset following the procedure described in the Installation Troubleshooting SAP Note (see SAP Notes for the Installation section for details).

5. To exit the utility, enter END.

Verify Replication Startup (Optional)

If MDI is enabled, verify that the replication process has started on the store node.

1. On Linux servers, log on as the JDBC_ADMIN_USER. On Windows servers, log on as the predefined install user.

2. Verify that the replication process is running by running the following command from the

TE_HOME/deployment/replication directory.

Linux

./replication.sh status

Windows

replication.bat status

3. If it is not running, launch the replication process from the directory

TE_HOME/deployment/replication.

Linux

./launchReplication.sh

Windows

launchReplication.bat

where <TE_HOME> is the installation directory of SAP Enterprise POS software;

/opt/sap/te/product.

The replication process must be running at the HO node before replication at store node can be launched.

Head Office and Store Server The following verification steps must be done on both head office and store servers.

Verify Wily Agent Installation (Optional)

If Wily agent installation is selected, verify that it is installed on the head office node.

1. On Linux servers, log on as the TE_USER. On Windows servers, log on as the predefined install user.

2. Verify that the Wily agent directory exists:

Linux

/usr/sap/wily

Windows

C:\usr\sap\wily

3. Verify the contents in the Wily agent directory. Ensure that the Agent.jar file and

IntroscopeAgent.profile file are in the directory.

4. By default, the Wily agent is off upon installation. To start the Wily agent, run the following

command from the directory TE_HOME/utils:

Installation Guide

50 February 2012

Linux

./startWily.sh

Windows

startWily.bat

5. We recommend that the Wily agent is on only when required. To shut down the Wily agent,

run the following command from the directory TE_HOME/utils:

Linux

./stopWily.sh

Windows

stopWily.bat

6. Where <TE_HOME> is the installation directory of SAP Enterprise POS software;

Linux

/opt/sap/te/product

Windows

C:\sap\te\product

For more information about the startWily and stopWily scripts, refer to the SAP Enterprise

POS Application Operation Guide .

Verify SMD Agent Installation (Optional)

If SMD agent installation is selected, verify that it is installed on the head office node.

1. On Linux servers, log on as the smdadm user. The password for the smdadm user is the same as the password for the TE_USER that was prompted in the preinstallation script during the security configuration process. On Windows servers, log on as the predefined install user.

2. Verify that the SMD agent directory exists:

Linux

/usr/sap/SMD

Windows

C:\usr\sap\smd

3. Verify the contents in the SMD agent directory. There should be three subdirectories: exe,

J98, and SYS.

4. By default, the SMD agent is off upon installation. To start the SMD agent, run the following

command from the directory /usr/sap/SMD/J98/script (Linux) or

C:\usr\sap\smd\.J98\script (Windows):

Linux

./smdstart.sh

Windows

smdstart.bat

5. We recommend that the SMD agent is on only when required. To shut down the SMD agent,

run the following command from the directory /usr/sap/SMD/J98/script (Linux) or

C:\usr\sap\smd\.J98\script (Windows):

Linux

./smdstop.sh


February 2012 51

Windows

smdstop.bat

For more information about the SMD scripts, refer to the SAP Enterprise POS Application Operation Guide.

Installation Guide

52 February 2012

Installing the Mobile Point-of-Sale Use

To install the SAP Enterprise Mobile Point-of-Sale component of the SAP POS suite for your implementation of SAP Enterprise POS.

SAP Enterprise POS supports one mobile device at a time. Using this installation process, you can either install a new Mobile POS or modify existing parameters already loaded on the Mobile POS. The installer detects whether an installation for Mobile POS has occurred and automatically guides you through the correct installation or modification process.

Prerequisites

Mobile POS prerequisites:

You must install and be running the SAP Enterprise POS server and database on the store server running SAP Enterprise POS

Microsoft ActiveSync 4.2 must be installed on the system and running. If it is not running, a dialog box asking you to connect appears during installation. If this is the case, a quick way to start the Microsoft ActiveSync is to remove and then replace the mobile device from or to its cradle. This starts Microsoft ActiveSync.

The mobile 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.

Procedure

1. Access the SAP Enterprise Mobile Point of Sale installation file Enterprise Mobile

Point of Sale.msi.

The Welcome screen for the Enterprise Mobile Point of Sales installation appears.

2. Select Next. The Destination Folder screen appears.

3. Choose the location where you want to install SAP Enterprise Mobile POS.

To install to the folder displayed in the default path (where you previously installed SAP Enterprise POS), select Next.

To install to another folder, select Change. From the Change Current Destination Folder screen, navigate to the appropriate folder and select OK.

The Hand Held Device screen appears.

4. Enter the following values:

Organization ID

Store Number – once entered this becomes the default value

Server IP Address – the SAP Enterprise POS store server, this can also be the HO server

Server Port – typically 9080 to support the default Linux WebSphere environment

Device Type – choose MC3090 or MC9090

Terminal ID – the ID of the Mobile POS device; each device must have a unique ID

Terminal Port – the range should be around 4000

Terminal Printer – the printer name must match the printer logical name defined

in the JPOS.xml file


February 2012 53

If entries are missing, the installation program prompts you to enter the required fields.

5. Verify your settings and select Next to continue.

The Ready to Install screen appears.

6. Verify that the handheld device is returned to its cradle. This ensures that all required files are successfully transferred to the device during the installation process.

7. To begin the Mobile POS installation, select Install.

8. After the Mobile POS installation process is complete, you must perform additional configuration tasks on the host machine to support this installation.

For more information about how to configure the peripheral components that support the Mobile POS application, see Configuring the Mobile Point of Sale Components.

Configuring the Mobile Point-of-Sale Components The Mobile Point-of-Sale application is a mobile thin client POS application supported by an infrastructure that consists of a wireless handheld or mobile device, an access point, and a wireless printer. Your environment can also include a magnetic stripe reading device (MSR). In addition to installing the application files that set up and link the Mobile POS as a recognized terminal in your store, you must also configure additional components that support the Mobile POS terminal. This section describes how to install and configure these components.

The following diagram is an illustration of how the POS components are set up in relation to the access point:

The following section describes how to set up and configure the Mobile Point-of-Sale application.

Mobile POS Application Technical Notes The current version of Mobile POS is developed using Microsoft's embedded Visual C++ 4.0. The executables are built using the recommended Symbol SDK libraries for each type of supported device. The target platform for development is WinCE 5.0.

Installation Guide

54 February 2012

Supported Devices The Mobile POS thin client is composed of a networking module, a simple GUI, and hardware components for the scanner and MSR. The printer is a wireless TCP/IP printer. SAP Enterprise POS Mobile POS supports the following devices:

Device Specification

Symbol MC3090Up - Mobile Handheld Device with support for detachable MSR3000-100

Microsoft Windows CE 5 Professional Edition

Symbol MC9090Up - Mobile Handheld Device with support for detachable MSR9000-100

Microsoft Windows CE 5 Professional Edition

28, 38, or 48 key emulation

28, 37, or 47 key emulation

Symbol AP 5131 - Wireless Access Point 802.11b 11 Mbps

Zebra QL320plus mobile belt printer with WPA/WPA2 support

Configuring the Mobile POS Wireless Components After installing the Mobile POS files, you must configure the supporting wireless components and devices that run the Mobile POS network and link it to the store server running the SAP Enterprise POS. You must define specific settings for each of the following devices:

Wireless Access Point (controls the Mobile POS wireless network)

Handheld device

Printer.

The following sections provide basic information about the settings that you configure to get your Mobile POS network up and running. Additional information about each device referenced should be obtained from the vendor’s website.

Setting up the Wireless Network Refer to the manufacturer’s User Guide for assistance with setting up your wireless network.

We recommend the use of WPA2, which is more secure than WPA.

To make the key truly secure, use a complex encryption key that contains letters, numbers, and special characters

We recommend you assign a static IP address rather than DHCP.

Connecting a Handheld Device to a Wireless Network

Mobile POS supports the Symbol MC3090 and Symbol MC9090 handheld device models. These devices include the Wireless Fusion Enterprise Mobility Suite application, which allows you to set up the wireless configuration.

1. To access this utility from the mobile device, select Programs Fusion WCLAUNCH.

2. Once you start the utility, locate the fusion icon at the bottom of the mobile display in the task bar.

For more information about this utility, refer to the Wireless Fusion Enterprise Mobility Suite User Guide. The Wireless Fusion Enterprise Mobility Suite User


February 2012 55

Guide is available at https://docs.symbol.com/manuals/10717001a.pdf during the publication of this guide

3. Click Fusion and select either Find WLAN or Manage WLAN to set up your wireless configuration.

The values used to set up your wireless configuration depend on the parameter values set up on the access point.

Connecting a Printer to the Wireless Network

For instructions on connecting a printer to the wireless network, refer to your hardware manufacturer’s user guide.

Test your wireless infrastructure by pinging the printer from the Mobile POS server system.

If you encounter problems communicating with the devices using the ping utility, contact your hardware vendor for assistance.

Running the Mobile POS

After the mobile device is connected to the store server that is running the SAP Enterprise POS application, you can begin to operate it. Start the Mobile POS by double-clicking the icon on the desktop.

To prevent a reset of the configurations following a cold reboot, export the settings in the WLAN profile manager. Go to Options Export. Choose both export options: Export Options and Export All Profiles.

To start the Mobile POS application:

1. Click the TE MPOS icon.

2. The Mobile POS application appears.

3. Select OK at the Connect to Server message.

4. You can now use the Mobile POS.

Troubleshooting the Mobile POS

The following section provides answers to some frequently asked questions that may arise as you configure the Mobile POS device.

How do I warm boot the mobile device?

Response:

For the MC9090, press and hold the power button for about 5 seconds or until the display becomes black. This warm boots the MC9090 mobile device

For the MC3090, press and hold down sequence keys 7, 9 and the red power button at the same time. This warm boots the MC3090 mobile device.

What can I do if the device displays Not Connected?

Response: Check the following:

The mobile device is able to ping the server on which the Mobile POS application is installed

All the settings in M_pos.ini are correctly set.

The device is not printing.


The printer is turned on

https://docs.symbol.com/manuals/10717001a.pdf

Installation Guide

56 February 2012

The m_pos.ini contains the printer logicalname (for example,

CPOSPRINTER1) that is defined in the jpos.xml. Check that this link to the IP

address is defined in the structure of the printer.

The device has an MSR device attached but nothing happens when a card is swiped.


In the Main section of M_pos.ini, check that the MsrDLLName is correctly

defined

Confirm that the MSR device was attached to the mobile device before launching the thin server and thin client.

When the MSR is attached to the device, a warm boot is recommended to make sure the device is recognized by the mobile device.


February 2012 57

Post Installation This section describes what activities should be performed after the SAP Enterprise POS installation is complete and verified.

Applying Support Packages and Patches There are no additional software support packages or patches available for the current release of SAP Enterprise POS.

Configuration This section is a brief tutorial on how to configure SAP Enterprise POS so that it is ready for transaction processing in an imaginary retail environment using a Demonstration configuration. For detailed information about configuring SAP Enterprise POS, see the Configurator and POS Manager sections in the SAP Enterprise POS Application Help at help.sap.com.

There are two phases to configuration: configuring business logic and adding operational data.

Business logic is defined by the application in a Profile. Default profiles are included with the application and are used for this tutorial. There are currently four different profile types. They are: POS, POS manager, EFT manager, and ASYNC services.

The POS profile defines business logic related to the Point-of-Sale

The POS manager profile defines business logic related to the back-end management application

The EFT manager profile defines business logic related to electronic funds transfer.

The ASYNC services profile defines business logic that is related to non-transaction-specific functions such as when to purge the database of old records.

Operational data includes, but is not limited to:

Merchandise records

Non-Merchandise records

Employee records

Department records

Store information, such as address and hours of operation.

Configuring Organization ID Enterprise POS is designed so that the primary identifier for a retailer is the Organization ID, or OrgID. The default configuration creates an OrgID of Triversity, but it is likely that you will change this to a more appropriate value.

To do so, choose the OrgID when you install the SAP Enterprise POS head office. This Organization ID must be consistently used throughout all subsequent steps of SAP Enterprise POS configuration. This includes hosted sites, hierarchy import, and all master data imports. The Organization ID is in the header of most SAP Enterprise POS xml files, as well as in the body of several other files, which is another reason to maintain its consistency.

Hosted Sites Site hosting is a critical concept in SAP Enterprise POS. It is how the database replication knows which master data to load onto which stores, and it is how the messaging layer of SAP Enterprise POS knows which messages apply to which servers.

Every server, whether HO or store, is assigned a site ID. The site ID is the identifier of the server, and in some cases, the store number. A server can host more than one store, where hosting means that the server responds to messages and retains master data for a given store. Therefore, setting up hosted sites properly is important for ensuring correct data movement.

Hosted sites are defined using a HostedSites.xml file, a sample of which is shown below:

Installation Guide

58 February 2012

<?xml version="1.0" encoding="UTF-8"?>

<HostSiteMaintenance Version="1.0"

xmlns="http://www.triversity.com/TE/integration/"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xsi:schemaLocation="http://www.triversity.com/TE/integration/

C:\TBSFeature\Te\twinterfaceschema\supported\HostSiteMaintenance.xsd">

<Header>

<OrganizationID>Triversity</OrganizationID>

<ApplyToStores>

<RetailStoreID>0</RetailStoreID>

</ApplyToStores>

<MessageId>76W9264C89</MessageId>

<Timestamp>2006-02-15T16:23:58</Timestamp>

<Originator>Triversity</Originator>

<AckType>Always</AckType>

</Header>

<Body>

<HostedSite Action="Add">

<Organization>Triversity</Organization>

<Site>0</Site>

</HostedSite>



<Site>1</Site>

</HostedSite>

</Body>

</HostSiteMaintenance>

In the example above, the organization is set to Triversity. Site 0, in the <ApplyToStores>

section of the HostedSites.xml file, is the hosting site. The sites that it hosts are defined in the

<Body> section. Triversity/0 is the first hosted site and Triversity/1 is the second.

Each hosted site import must be for only one hosting site.

If you want your hosting site to host itself, it must be explicitly added. In the example above, site 0 does not host site 0 unless you specify it in the

<Body> section of the HostedSites.xml file.

The RetailStoreID in the <Header> section is a server identifier, while the

sites listed in the <Body> are store numbers.

A hosted site import must be created for every server that is defined, and it must specify which stores it hosts. Typically, the head office site (by default, site 0), should host every store. A store server in the local store server topology hosts itself and the other hosted stores.

The HostedSites.xml below is an example of a store server which is set to use the centralized

store server topology. The store server is deployed as site 1. Along with hosting itself (site 1), it also hosts two stores (site 2 and site3).

<?xml version="1.0" encoding="UTF-8"?>

<HostSiteMaintenance Version="1.0"

xmlns="http://www.triversity.com/TE/integration/"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xsi:schemaLocation="http://www.triversity.com/TE/integration/

C:\TBSFeature\Te\twinterfaceschema\supported\HostSiteMaintenance.xsd">

<Header>


February 2012 59

<OrganizationID>Triversity</OrganizationID>

<ApplyToStores>

<RetailStoreID>1</RetailStoreID>

</ApplyToStores>

<MessageId>76W9264C89</MessageId>

<Timestamp>2006-02-15T16:23:58</Timestamp>

<Originator>Triversity</Originator>

<AckType>Always</AckType>

</Header>

<Body>



<Site>1</Site>

</HostedSite>



<Site>2</Site>

</HostedSite>



<Site>3</Site>

</HostedSite>

</Body>

</HostSiteMaintenance>

Each of these XML files should be imported to the head office. The resulting data is replicated down to the proper servers.

Configuring Business Logic This section describes the activities required to configure SAP Enterprise POS with the supplied Demonstration business logic. There are three stages to this process:

1. Creating the business logic configuration.

2. Creating the enterprise hierarchy.

3. Deploying the configuration to the enterprise.

Creating Business Logic Configuration The business logic configuration is created based on specific business requirements.

The Demonstration configuration is provided as xml files that you can import into the system using a supplied sample application. It is also possible to import the configuration using the JMS API, but this is not covered in this guide. By default the OrgID for the Demonstration configuration is Triversity.

Use

To import the Demonstration business logic configuration into the system using the supplied tools.

Prerequisites

HO node must be installed and running.

Installation Guide

60 February 2012

Procedure

1. Log on to a terminal on the HO node as the TE_USER.

2. Navigate to the custom directory containing the xml data files for the profiles:

Linux

trivers@host:~/>cd

/opt/sap/te/product/custom/standalone/dataimport

Windows

C:\> cd \sap\te\product\custom\standalone\dataimport

3. Open all of the profile xml files. The default profile file name pattern is Profile*.xml.

Take note of the value of the <RetailStoreId> element. The value should be asterisk *

indicating that the profile is applicable to all sites.

4. Prepare HostedSites XML files, one per server. For more information, see Hosted Sites.

5. Navigate to the directory containing the Data Import scripts:

Linux

trivers@host:~/>cd /opt/sap/te/product/bin/DataImport

Windows

C:\> cd \sap\te\product\bin\DataImport

6. Upload hosted sites information in the system. Execute the batch script dataimport.sh/

dataimport.sh for each HostedSites file that you created. For example:

Linux

trivers@host:~/opt/sap/te/product/bin/DataImport>./dataimport.sh was

../../custom/standalone/dataimport/HostedSitesHO.xml

trivers@host:~/opt/sap/te/product/bin/DataImport>./dataimport.sh was

../../custom/standalone/dataimport/HostedSitesN.xml

Windows

C:\sap\te\product\bin\DataImport>dataimport.bat was

..\..\custom\standalone\dataimport\HostedSitesHO.xml

C:\sap\te\product\bin\DataImport>dataimport.bat was

..\..\custom\standalone\dataimport\HostedSitesN.xml

7. Once the hosted sites are imported, the default configuration, including the configuration profiles for POS, POS manager, EFT, and Async Site services, can be imported. You can import these individually using data import, or you can use the

rundataimportprofiles.sh/rundataimportprofiles.bat script to automate the

import:

Linux

trivers@host:~/opt/sap/te/product/bin/DataImport>./rundataimportprofi

les.sh

Windows

C:\sap\te\product\bin\DataImport> rundataimportprofiles.bat

was

8. Verify that the configuration profile imported successfully. In the terminal there is one response for each imported profile, for a total of four responses. Each response indicates that one of one files was imported successfully.

mailto:trivers@host:~/opt/sap/te/product/bin/DataImport%3e./dataimport.sh%20was%20../../custom/standalone/dataimport/HostedSitesHO.xml

mailto:trivers@host:~/opt/sap/te/product/bin/DataImport%3e./dataimport.sh%20was%20../../custom/standalone/dataimport/HostedSitesHO.xml

mailto:trivers@host:~/opt/sap/te/product/bin/DataImport%3e./dataimport.sh%20was%20../../custom/standalone/dataimport/HostedSitesN.xml

mailto:trivers@host:~/opt/sap/te/product/bin/DataImport%3e./dataimport.sh%20was%20../../custom/standalone/dataimport/HostedSitesN.xml


February 2012 61

The system can import the older configuration profiles, by either running the

dataimport.sh/dataimport.bat utility, or using the profile import feature that is

available in configurator.

However, you must specify the product version of the imported profile in the input file. You must make this change manually.

To make the change and import the updated profile:

1. Before attempting to import the 3.0 profiles, edit each profile xml file by

adding the version attribute to the ConfigurationProfileMaintenance

root element: <ConfigurationProfileMaintenance xmlns=http://www.triversity.com/TE/integration

Version=3.0>.

2. Import the updated profile, by either running the

dataimport.sh/dataimport.bat utility or using the Manage

Configuration Import Profile feature in the Configurator. The profile is then available in the Configurator under the next sequential version number. You can then maintain, release, and deploy it to your stores. The profile is automatically upgraded when you select it for maintenance and update. When the profile is deployed to a store, it is automatically upgraded (or downgraded) to match the SAP Enterprise POS version that the target store is using.

Creating the Enterprise Hierarchy Similar to the profiles described in the previous section, you can create the enterprise hierarchy through the configurator Web-Based tool or by importing a properly formatted xml text file using

the data import utility. The supplied HierarchyImport.xml, found in the

<TE_HOME>/product/custom/standalone/dataimport directory, is configured for a

Demonstration configuration. <TE_HOME> is the install directory of SAP Enterprise POS software:

Linux

/opt/sap/te/product

Windows

C:\sap\te\product

The Demonstration configuration consists of one head office server (site ID=0) and two store servers (site ID=1 and site ID=2). For each store server, ten POS/OLC clients (Device ID=1 to Device ID=10) have been defined. To create the hierarchy using the supplied xml file that is configured for a Demonstration configuration, follow these steps:

Use

To import the enterprise hierarchy into the system using the supplied tools.

Prerequisites

The head office server as well as the store server(s) must be installed and running.

Procedure

1. Modify the HierarchyImport.xml file based on the desired landscape. The

<RetailStoreID> tag must be set to the site ID value of the server that the data import

runs on, meaning the head office server. For example, if the head office is set to site ID=0,

then the <RetailStoreID> tag is 0. Depending on the landscape setup, define the

appropriate number of site IDs and device IDs.

2. Continue from where you left off in the last procedure. Execute the data import script and

supply the HeirarchyImport.xml file as the file to import:

Installation Guide

62 February 2012

Linux

trivers@host:~/opt/sap/te/product/bin/DataImport>./dataimport.sh

was

/opt/sap/te/product/custom/standalone/dataimport/HierarchyImport.

xml

Windows

C:\sap\te\product\bin\DataImport>dataimport was

..\..\custom\standalone\dataimport\HierarchyImport.xml

3. Verify that the response message indicates success.

Deploying the Configuration

Use

To log on to the configurator and deploy profiles.

Prerequisites

The head office server as well as the store server(s) must be installed and running.

Procedure

1. Using a supported Web browser, logon to the configurator. The default URL is

http://<host name>:9080/saptrv/te/configurator.

The default configurator user uses 1111 as the logon ID and 11111111 as the logon password. The default configurator is only a temporary user account. Once the employee profiles are successfully imported during the operational data configuration steps, the default configurator user account is deleted.

2. As mentioned earlier, the Demonstration configuration supports only one store server by default. If more than one store server is defined in the Creating Business Logic Configuration section, add all additional sites and devices in the Sites and Devices section of the configurator.

3. Assign the profiles to the appropriate nodes in the hierarchy configuration.

4. Release and deploy the Demonstration profiles one at a time. Ensure that the timestamp used for deploying the profiles is set with regard to the current date and time on the nodes where the profiles are being deployed. Release and deploy the following:

a. POS profile

b. POS manager profile

c. EFT manager profile

d. ASYNC services site profile

5. Verify that the profiles are deployed successfully. There may be a delay while the profiles are applied. If any profile verification result is still in a yellow or red state, wait up to 5 minutes.

Configuring Operational Data This section describes what activities should be performed to import data into SAP Enterprise POS. You can use one of two ways to import data:

Using JMS (Java Messaging Services API)

Using database replication (Master Data Import). To import data using database replication, you must have planned for it and installed the application appropriately.


February 2012 63

Importing Data via Java Message Service (JMS)

When operational data is delivered to the stores using Java Message Service, xml formatted messages are submitted to a JMS queue at the HO node. The message is processed internally and then forwarded to the ISP nodes.

Since the messaging server being used is WebSphere MQ there are multiple ways to place the xml formatted messages onto the appropriate QUEUE:

Using the sample application provided with SAP Enterprise POS. This sample application is only suitable for testing

Using the WebSphere MQ Native API or JMS API develop a C or Java application that places messages on the QUEUE and reads the responses for further processing. This is more efficient than using the sample application provided with SAP Enterprise POS.

In the steps below, you use the sample application provided with SAP Enterprise POS to read xml formatted text files from the file system and place them on the JMS QUEUE. Responses are displayed in xml format to STDOUT.

Use

To import the supplied Demonstration operational data using the provided sample Java application.

The Demonstration operational data is intended to be used with the Demonstration business logic configuration only

The Demonstration operational data is applicable only to the ISP with the SITE ID value

of 1. Modification of the supplied xml formatted text files is required to support additional ISPs other than site ID 1 or an Organization ID other than Triversity. Creation and modification of xml formatted operational data is not covered in this document.

Prerequisites

SAP Enterprise POS HO is installed and running

SAP Enterprise POS ISP is installed and running

All SAP Enterprise POS nodes have business logic configured successfully.

Procedure

The procedure involves executing the rundataimport shell script. Follow these steps to import

the operational data. The steps below are for Linux. For Windows, use .bat instead of .sh.

1. Log on to the server on the HO node as the TE_USER.

2. Navigate to the directory containing the supplied script:

trivers@host name:~/> cd /opt/sap/te/product/bin/DataImport

3. Execute the command rundataimport.sh:

trivers@host name:~/> ./rundataimport.sh

4. Verify that the xml response message denotes the successful addition of operational data to

the system. For each file imported, scan the response for the text X records of a

total X records were imported successfully. Verify that all records imported

successfully. You may see some errors when the utility processes files HostedSitesHO.xml and HostedSites1.xml. This is because they were already processed when Business Logic Configuration was performed.

Installation Guide

64 February 2012

Importing Data using Database Replication (MDI) MDI takes advantage of the replication capabilities of IBM DB2 UDB. It is only possible to use MDI when the application is configured to use IBM DB2 for its database engine and the application is deployed with MDI enabled. For information about enabling MDI, see Preparation..

Prerequisites

SAP Enterprise POS head office server is running

SAP Enterprise POS store servers are running

Database replication at the head office server is running

Database replication at the store servers is running

A set of data import files to import. The xml files must conform to the SAP-Defined schemas for each type:

Hosted Sites (Required) Item Hierarchy (Required) Departments (Required) Employee (Required) Item Maintenance (Required) Mix Match Pricing (Optional) Promotions (Optional) Site Parameters (Optional) Validation Data (Optional)

An instruction (or trigger) file describing the data import file is set. The file name is not restricted in any way, only the contents. The contents of the instruction file must conform to the BulkImportRequest schema (BulkImportRequest.xsd). An example instruction is shown below, with descriptions of the various elements:


February 2012 65

The data import files specified in the instruction file are copied to the head office server in the location described in the instruction file. The above example shows files placed on a

Linux server in the /var/importdata directory

Verify that the database is up and running.

Procedure

1. Log on to the HO server. In Linux, log in as JDBC_ADMIN_USER or switch to this user

account. On Windows, log on as TE_USER.

2. Launch the MDI controller.

Linux

cd /opt/sap/te/product/bin/MDI

sh mdiStart.sh

You launch the MDI controller from a batch shell.

Windows

c:\>cd c:\sap\te\product\bin\MDI

c:\sap\te\product\bin\MDI\>mdiStart.bat

3. Copy the instruction file to the DM controller commands directory. For example, assuming an

instruction file name of loadAll.xml and a data path of /var/sap/te, the command

would be:

Installation Guide

66 February 2012

Linux

Assuming the instruction file name of loadAll.xml and a data path of

/var/sap/te, the command would be:

cp loadAll.xml /var/sap/te/mdi/commands

Windows

Assuming the instruction file name of loadAll.xml and a data path of

C:\sap\te\, the command would be: C:\>copy loadAll.xml C:\sap\te\mdi\commands

4. Monitor the progress by reviewing the log files in:

Linux

/var/sap/te/mdi/applog

Windows

C:\sap\te\mdi\applog


February 2012 67

Troubleshooting Additional Information

Additional troubleshooting information can be also found in the SAP Note 1655003.

Middleware Installation

TPM Log Files:

The TPM log files are located in the following directory:

Linux

/tmp/wrs711_install/logs

Windows

$(temp_dir)\WRSTEMP\logs

where $(temp_dir) is the temporary directory of the user under which the agent is running.

Log File System Description

chmod.out Linux x64 Result of command to set LinuxSetup

command to execute

wrs711_Lnx_x64_install.log Linux x64 Result of Launching the WRS Installer

and the result of the SolutionValidator script wrs711_win_x64_install.log Windows x64

wrs711_win_x86_install.log Windows x86

WRS711Linuxx64Part1.7.1.1.log Linux x64 Log of SPB file extraction and commands

WRS711Winx64Part1.7.1.1.log Windows x64








WRS Solution Installer Log Files:

The WRS Solution Installer log files are only present after the installation routine has finished execution (successfully or not), and are located in the following directory:

Linux

/opt/SolutionFiles/logs

Windows x86

C:\Program Files\SolutionFiles\logs

Windows x64

C:\Program Files (x86)\SolutionFiles\logs

The IRU_DeploymentWizard.log is the master installation log file. Other log files in the

directory are specific to each program that is installed.

Installation Guide

68 February 2012

SAP Enterprise POS Store and Head Office Installation

The Head Office and Store installation log file temaster.out is located in the

$TE_HOME/deployment directory on the Linux system; teamster.log is located in the

%TE_HOME%/deployment/logs directory on the Windows system, where TE_HOME is the home

directory where SAP Enterprise POS is installed.

Cannot extract the contents from the tar.gz files when executing the tar command

Make sure that the ownership of the /opt/sap directory and the tar.gz/tgz files belong to

tioadmin. For more information, see Preparing Installation Image Repository.

java.lang.UnsupportedClassVersionError (Unsupported major.minor version 49.0) error when you run the preinstallation script

Make sure that the environment variable JAVA_HOME points to the path of the Java JDK 5.0

directory. The current release of SAP Enterprise POS does not support java versions prior to JDK 5.0.

Channel verification fails

After executing the MQ channel creation task, the channel status for the store server to the HO is retrying when verifying the MQ channel startup on the ISP server. For more information, see Verify MQ .

Log on to the ISP server as the JMS_USER.Run the following commands:

1. runmqsc

2. start channel(STx_1.HEAD_OFF)

3. end

Where x is the site ID of the ISP server. For example, if the site ID is 1, then the command is start channel (ST1_1.HEAD_OFF).

COPCOM123E A shell command error occurred: Exit code=3, Error stream="Timeout - login on localhost failed. Command: ‘su – tioadmin’

The response wait time setting in the built-in TPM workflow Local_Execute_Command is the cause. If you experience this problem you can edit the workflow to increase the response wait time by performing the following steps:

1. Make the workflow editable:

a. Log on to the TPM server as the Tivoli administrator.

b. Start a DB2 command prompt.

c. Set the DB2INSTANCE variable to ctginst1:

C:\>set DB2INSTANCE=ctginst1

d. Connect to the maxdb71 database:

C:\>db2 connect to maxdb71 user <Tivoli administrator> using

<Password>

e. Update the database to make the workflow editable:

C:\>db2 update workflow4 set is_editable=’Y’ where

workflow_name=’Local_Execute_Command’

f. Exit the DB2 command prompt:

C:\>db2 terminate

2. Edit the workflow:

a. Using a Web browser, log on to the Tivoli Web Console at the following URL:


b. Navigate to the workflow window using the admin console:


February 2012 69

Go To Administration Provisioning Provisioning Workflows

c. Find the workflow to edit by searching for the workflow with the name

Local_Execute_Command. Select the workflow to go to the workflow source code

screen.

d. In the text of the source code editor locate the line that begins with

sleep .1.

e. Increase the wait response timeout by one second by replacing the 1 with a 2.

f. Compile the workflow by choosing Compile Workflow in the Select Action dropdown list.

3. Test the workflow:

a. Repeat the action that caused the error message. If it reoccurs perform step 2 again and increase the wait response by another second.

b. Repeat step 3.

4. Make the workflow immutable (Optional):

a. Repeat step 1a through step 1d.

b. Update the database to make the workflow immutable.

C:\>db2 update workflow4 set is_editable=’N’ where

workflow_name=’Local_Execute_Command’

c. Exit the DB2 command prompt:

C:\>db2 terminate

SAP Enterprise POS Installation

TPM Installation Log Files


Windows x86

%TEMP%\POSInstall

where %User_Home% is the home folder of the user under which the installation is

running.


POSInstall.log Windows POS installation log file generated by POSMaster.bat

POSInstall.err Windows Lists the names of erroneous sections

of the POSInstall.log

SAP Enterprise OLC Client Installation



Windows x86

C:\Temp\OLCInstall


OLCInstall.log Windows OLC installation log file generated by OLCMaster.bat

OLCInstall.err Linux, Windows Lists the names of erroneous sections

of the OLCInstall.log

Installation Guide

70 February 2012

Fail to redefine OLC or POS Client in Tivoli

You must rerun the TE_DefineClient workflows due to incorrect input parameters.

Before rerunning the workflow, you must clean up the previous variables by executing the

TE_RemoveVariables workflow. For the deviceID and Prefix parameters, the deviceID is

the TPM computer name and the prefix should be set to CL_.

Install Error: “setTEClientEnv.bat not found”

If an installation of OLC server is attempted on a computer that has been defined as a POS Client or has not been defined at all, the error setTEClientEnv.bat not found will be listed in the Tivoli installation task logs. Ensure that the computer is defined as an OLC register as specified in the installation guide. The same error can happen when the installation of the POS Client is attempted on a computer that is defined as an OLC server.

Wily Installation



Linux

/tmp/WILYInstall/logs/

Windows

%TEMP%\WILYInstall\logs\

where User_Home is the home folder of the user under which the installation is running.


error.log Linux, Windows Standard error log file of the Wily Software Package Block installation process.

out.log

Linux, Windows Standard output log file of the Wily Software Package Block installation process.

TE_Wily_Agent_Linux^3.1.7.log

Linux Log file of the TPM managing the Wily Software Package Block installation process.

TE_Wily_Agent_Windows^3.1.7.log Windows Log file of the TPM managing

the Wily Software Package

Block installation process.

Wily installation failed when installing the Head Office or Store

If the Wily Agent is installed with the other products as a part of the Head Office installation process, but not as a separate product and the Wily Agent installation fails, the TPM does not create a record indicating that the SAP Enterprise POS Head Office or Store was installed. This is true even if the WebSphere Remote Server and SAP Enterprise POS application were installed successfully as part of the Head Office installation process. In this case, validate if WebSphere Remote Server and SAP Enterprise POS were successfully installed and manually add a record in the TPM Data Center Model. After that the Wily Agent can be installed as a separate product. For more information, see Installing Wily Agent (optional).

To add a record in the TPM Data Center Model, perform the following steps:

1. Navigate to the Tivoli Web Console logon at the URL shown, where <tpm_host> is the fully

qualified host name or IP address of the server where TPM is installed, and logon to the TPM Web Console:


February 2012 71


2. Choose Go To Deployment Provisioning Computers. The Provisioning Computers window displays. Select the Computer where the installation failed. The computer details screen (Computer tab) displays.

3. Add Software Installation record.

a. Click Add Software and then select Add Software Installation.

b. Enter values for the Name and Software Definition fields:

Name – SAP Enterprise POS Head Office 3.1.7 or SAP

Enterprise POS Store 3.1.7 (depending on which server you are

working with)

Software Definition – Click Software Definition next to the Software

Definition text field. In the popup window search for SAP Enterprise

POS Head Office 3.1.7 or SAP Enterprise POS Store

3.1.7 (depending on which server you are working with). Click the

selected item.

c. Click Save Computer at the top of the screen. The SAP Enterprise POS Head

Office 3.1.7 or SAP Enterprise POS Store 3.1.7 record displays in the

software list.

SMD Installation



Linux

/tmp/SMDInstall/

Windows

%TEMP%\SMDInstall\

where User_Home is the home folder of the user under which the installation is running.


logs/ error.out

Linux, Windows Standard error log file of the SMD Software Package Block installation process.

logs/ out.log

Linux, Windows Standard output log file of the SMD Software Package Block installation process.

logs/ TE_SMD_Agent_Linux^3.1.7.log

Linux Log file of the TPM managing the SMD Software Package Block installation process.

logs/TE_SMD_Agent_Windows^3.1.7.log Windows Log file of the TPM managing

the SMD Software Package

Block installation process.

SMDInstall.log Linux, Windows Generated by SMDInstall script

SMD Installation failed when installing the Head Office or Store

Perform the steps listed in Wily installation failed when installing the Head Office or Store. Adapt the steps for the SMD product.

sap enterprise point-of-sale 3.1 sp07 · pdf filesap enterprise point-of-sale (sap enterprise...

Documents