SAP Point-of-Sale 2.3 Application Operations Guide

Application Operations Guide

SAP Point-of-Sale 23

Document Version 109 ndash 2015-11-30

CUSTOMER

SAP Point-of-Sale 23 Application Operations Guide

2

CUSTOMER

copy 2015 SAP AG All rights reserved

SAP Point-of-Sale 23 Application Operations Guide Application Operations Guide

Typographic Conventions


Type Style Description

Example Words or characters quoted from the screen These include field names screen titles

pushbuttons labels menu names menu paths and menu options

Textual cross-references to other documents

Example Emphasized words or expressions

EXAMPLE Technical names of system objects These include report names program names

transaction codes table names and key concepts of a programming language when they

are surrounded by body text for example SELECT and INCLUDE

Example Output on the screen This includes file and directory names and their paths messages

names of variables and parameters source text and names of installation upgrade and

database tools

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

appear in the documentation

ltExamplegt Variable user entry Angle brackets indicate that you replace these words and characters

with appropriate entries to make entries in the system

EXAMPLE Keys on the keyboard for example F2 or ENTER


Document History

CUSTOMER

copy 2015 SAP AG All rights reserved 3

Document History

Caution

Make sure you use the current version of the Application Operations Guide

The current version of the Application Operations Guide is at httpservicesapcominstguides on SAP Service

Marketplace

The following table provides an overview of the most important changes in prior versions

Version Change

10 First version for SAP POS 23

101 Updated for SAP POS 23 SP01


Changed document version to match SP07

Added a reference to SAP Note 1916385

Reorganized document sections to a new logical order

108 Updated for SAP POS 23 SP08 Modifiedadded the following sections

363 Backup and Restore

421 Enable CA Introscope for Transnet Server

422 Enable CA Introscope for Transnet Client

109 Moved content to the updated template

4

CUSTOMER



Table of Contents

Table of Contents

1 Getting Started 7 11 About this Guide 7 12 Global Definitions 7 13 Important SAP Notes 8

2 Technical System Landscape 9 21 ScenarioComponent Matrix 9 22 Related Documentation 10

3 Store Components of SAP POS 12 31 Analysis Tools 12 32 Trace Files and Log Files 13

321 File Handler Configuration Section 13 322 Log Feature Configuration 14 323 Log File Format 15 324 POS Client Logging 15 325 Xpress Server Logging 17

33 Root Cause Analysis 20 331 Problem Analysis Using AppSight Troubleshooting Tool 20

34 Integration with CA Introscope 23 341 INTROSCPASC Turn ONOFF Data Collection 24 342 Interpreting Performance Nodes Displayed by Introscope 27

35 Technical Monitoring 27 36 Management of SAP POS 27

361 Administration Tools of Software Components 27 362 Starting and Stopping 29 363 Backup and Restore 31 364 Periodic Tasks 33 365 Load Balancing 34 366 Management of Logon Data 34

37 High Availability 35 38 Software Change Management 36

381 Transport and Change Management 36 382 Development Requests and Development Release Management 37 383 Support Packages and Patch Implementation 37

39 Troubleshooting 37

4 SAP POS STORE DATA TRANSFER FOR RETAIL 39 41 Technical System Landscape 39

411 Graphic Landscape Description 39 412 Language Support 39 413 JVM Memory Settings 40 414 Database Monitoring 41 415 Extracting Data via HTTP URLs with Internet Explorer 5 and Later 46


Table of Contents

CUSTOMER


416 Extracting Data via Template Queries with Internet Explorer 5 and Later 47 42 Integration with CA Introscope 47

421 Enable CA Introscope for Transnet Server 48 422 Enable CA Introscope for Transnet Client 50 423 Interpreting Performance Nodes Displayed by Introscope 53

43 Technical Monitoring 53 44 Management 53

441 Administration Tools of Software Components 53 442 Disable Sample NTM Modules 54 443 Increase Minimum Thread Count for SAP POS STORE DATA TRANSFER FOR RETAIL54 444 Disable NTM Transaction Logging 55 445 Increase Preserved NTM Server Logs 55 446 Disable Client Reverse DNS Lookups 55 447 Page File 55 448 SQL Server Memory56 449 Logging to DB 58 4410 Starting and Stopping 58 4411 Backup and Restore 58 4412 Periodic Tasks 59 4413 Logging On and Load Balancing 59 4414 User Management62 4415 Printing 62


461 Transport and Change Management64 462 Development Request and Development Release Management 64

47 Troubleshooting64 471 Works Cited 64

5 SAP RETURNS AUTHORIZATION 65 51 Technical System Landscape 65

511 System Landscape65 512 Language Support 65 513 Proposed Components 66 514 System Requirements for SAP RETURNS AUTHORIZATION 66

52 Monitoring and Tools for Problem and Performance Analysis 66 521 Trace and Log Files 66 522 Database Monitors 68 523 Operating System Monitors68 524 Workload Monitors68 525 Other Important Problem Analysis Tools 68 526 Interface Monitors 69 527 Data Growth and Data Archiving Monitors 69 528 Software Component Monitors 69

53 Integration with CA Introscope 69 531 CA Introscope - Enabling IBM WebSphere 70 532 CA Introscope - Enabling Batch Load Process 72 533 Interpreting Performance Nodes Displayed by Introscope 73

54 Technical Monitoring 73 55 Management of SAP RETURNS AUTHORIZATION 74

6

CUSTOMER



Table of Contents

551 Administration Tools of Software Components 74 552 Starting and Stopping 74

56 Backup and Restore 75 57 Classification 75 58 Backup and Restore 75 59 Periodic Tasks 76

591 Scheduled Periodic Tasks 76 592 Required Manual Periodic Tasks 77

510 Logging On and Load Balancing 77 511 User Management 78

5111 User Management Tools 78 512 Printing 80 513 High Availability 80

5131 High Availability at Application Level 80 5132 SAP RETURNS AUTHORIZATION Load Balancing 82 5133 High Availability at a Database Level 84

514 Transport and Change Management 85 515 Troubleshooting 85 516 Categories of System Components for Backup and Restore 86

6 Support Desk Management 89 61 Remote Support Setup 89 62 Problem Message Handover 89

7 Appendix 90 71 Related Guides 90


Getting Started

CUSTOMER


1 Getting Started

Caution

This guide does not replace the daily operations handbook that we recommend customers to create for

their specific production operations

11 About this Guide

This guide provides operations-related information for SAP POINT-OF-SALE (SAP POS) SAP POS STORE DATA

TRANSFER FOR RETAIL1 (SDTR) and SAP RETURNS AUTHORIZATION

The design implementation and optimized operation of your SAP POS application 24 hours a day has never been

more vital for your business success

This guide provides a starting point for managing your SAP POS application and maintaining and running it to its

full potential It contains specific information for various tasks and lists the tools that you can use to implement

the application

You can find documentation for SAP POS SAP POS STORE DATA TRANSFER FOR RETAIL and SAP RETURNS

AUTHORIZATION along with this guide in the SAP Library under Customer Relationship Mgmt rarr SAP Point-of-

Sale

Target Groups

Technical Consultants

System Administrators

Solution Consultants

Business Process Owner

Support Specialist

12 Global Definitions

SAP POS Application

SAP POS represents a market view of groups of related business scenarios This delivery contains SAP POS

components that are essential for implementing all solution-related business scenarios processes and functions

Implementation knowledge is included with each solution

1 Formerly called SAP CENTRALIZED ELECTRONIC FUNDS TRANSFER (SAP CEFT) which was known previously

as TRANSNET

8

CUSTOMER



Getting Started

Business Scenario

From a microeconomic perspective a business scenario is a cycle which consists of several different

interconnected logical processes in time Typically a business scenario includes several company departments

and involves with other business partners From a technical point of view a business scenario needs at lea st one

SAP application (SAP ERP SAP SCM or others) for each cycle and possibly other third-party systems A business

scenario is a unit which can be implemented separately and reflects the customerrsquos prospective course of

business

Component

A component is the smallest individual unit considered within the Solution Development Lifecycle components

are separately produced delivered installed and maintained

13 Important SAP Notes

Caution

Check regularly for updates available for the Application Operations Guide

Important SAP Notes

SAP Note

Number

Title Comment

1916385 SAP POS 23 RCA and Monitoring Guide Solution Manager Diagnostics and System

Monitoring


Technical System Landscape

CUSTOMER


2 Technical System Landscape

21 ScenarioComponent Matrix

1 SAP POS

o Instance Mobile POS Device

i Software Component Mobile POS Client v103

o Instance POS Terminal

i Software Component POS Client v103

o Instance Store Server

i Software Component POS Server v103 (Xpress Server)

ii Software Component Store Manager V103 (optional)

iii Software Component POS Client v103 (optional)

iv Software Component Mobile POS Server v103 (optional)

10

CUSTOMER




v Software Component SAP POS STORE DATA TRANSFER FOR RETAIL 110 (optional)

vi Software Component Electronic Journal Viewer v103 (optional)

vii Software Component Database Tools v103

viii Software Component Store Configurator v103 (optional)

o Instance Store Configurator Server

i Software Component Store Configurator v103

ii Software Component Database Tools v103

o Instance SAP POS STORE DATA TRANSFER FOR RETAIL Server

i Software Component SAP POS STORE DATA TRANSFER FOR RETAIL 110

o Instance SAP POS STORE DATA TRANSFER FOR RETAIL 110

i [Third- party SW Component] TPS NFM v22

o Instance Stored Value Server

i Software Component Stored Value Service 10

o Instance SAP RETURNS AUTHORIZATION Server

i Software Component SAP RETURNS AUTHORIZATION Service 27

ii Software Component Common Data Load 29

2 SAP POS Base






i Software Component POS Server v103






vii Software Component Database Tools v103 (optional)

viii Software Component Store Configurator v103

Instance Store Configurator Server



For information on how various combinations of components can be installed toget her or on different pieces of

equipment see Determining Your Store Installation Architecture (Sample Installation Environments) in the SAP

Point-of-Sale Installation Guide

22 Related Documentation

The following table lists where you can find more information about the technical system landscape



CUSTOMER


Topic GuideTool Quick Link on SAP Service

Marketplace (servicesapcom)

Application- and Industry-specific

Components such as SAP Financials and

SAP Retail

Master Guide servicesapcominstguides

Technology Components such as SAP Web

Application Server


Sizing Quick Sizer Tool servicesapcomsizing

Technical Configuration Master Guide servicesapcominstguides

Scalability Master Guide servicesapcominstguides

High Availability Master Guide servicesapcominstguides

Security Security Map

Application Security Guide

servicesapcomsecurity

servicesapcominstguides

12

CUSTOMER



Store Components of SAP POS

3 Store Components of SAP POS

This section is for components that are installed at the store and the components directly related to the

configuration of these components These are

POS Server (Xpress Server)

Store Manager

POS Client

Mobile POS Client

Electronic Journal Viewer

Database Tools

Head Office Component Store Configurator

31 Analysis Tools

The following table provides information on the tools

Monitor (Transaction Tool) StartPath Description Error Condition

POS Client (Register

Application)

Desktop icon or from

the Windows Start

menu

There is a Status window

that is normally blank A

short code appears if

there is an error

Manager code 6 Runs

communication

diagnostics at the

register

Manager code 900

Runs peripheral

diagnostics

Manager code 999

Shows the current

version and build

The NODB error code (no

database) appears in the

Status window if the

register is offline to the

POS Server The server

or the network is having

problems

POS ServerXpress Server Started by the

service when the PC

starts up

Can run a console

from the desktop to

monitor the server

At the bottom of the

console there is a

connection box that

shows the number of

registers currently

connected

If the server is not

running properly there

are errors reported in

The console application

can be used to identify a

number of problems with

the server



CUSTOMER



the Log window

(xpslog)

LSN REPORT and

STATUS REPORT on the

console identify

technical problems

POS ManagerStore Manager

component

Started from the

desktop icon or from

the Windows Start

menu

At the bottom of this

application there are two

status flags Database

Connected and Server

Connected

If green the connections

are successful

If red the connections

have failed

Dbcheckexe Started in a

command line

window

This is a standalone

program that allows for

the integrity of b-tree

files to be validated

If POS is reporting a

corrupted b-tree

database this program

can be run to validate

the files

32 Trace Files and Log Files

Trace files and log files are essential for analyzing problems

Logging is configured via an ini file with a separate configuration file for each application (posLogini for POS

Client and xpsLogini for POS ServerXpress Server) These configuration files are located in the parm

directory and in the case of the POS application is handled in the same manner as other POS configuration files

(for example automatically copied and loaded from the Xpress Server as updates to the file are made)

The configuration file consists of two sections one section to configure log file attributes (FileHandler) and the

other to configure logging features (Logger) as described in the following sections

321 File Handler Configuration Section

The file handler configuration settings consist of

FileHandlerltIDgtltKeywordgt=ltSettinggt

FileHandler Constant Indicating a FileHandler Configuration Setting

ID An ID associated with the file handler used to associate logger features to file

handlers

Keyword One of pattern archive limit or count where

Pattern = log file name

Archive = truefalse flag indicating whether log files should be archived into

uploadlogs directory

14

CUSTOMER





Limit = number of log files to maintain (historical log files are appended with a

sequence number)

Setting Setting appropriate for keyword

A sample file handler to write log content to a xpslog file is as follows

FileHandlerFH1pattern=logsxpslog

FileHandlerFH1archive=true

FileHandlerFH1limit=500000

FileHandlerFH1count=5

Note

If archiving of a log file is enabled (Archive=true) then historical log files (up to a maximum of lsquoLimitrsquo) are

maintained in the uploadkeep0logs directory Additionally as part of POS terminal close processing

archived log files are transferred from the POS to the Xpress Serverrsquos uploadkeep0logs directory as

well When transferred to the Xpress Server the store number and terminal number is pre-pended to the

log file name

ltssssssgtltrrgtlogFileName

Where ltssssssgt is the store number (between 4 to 6 digits depending on configuration) and ltrrgt is the

register number Xpress Server logs use p5 as the value of ltrrgt

Example

If Store 3 (4 digit store numbers) is configured to archive the posclient log file then the log file from

terminal 3 will be transferred to the Xpress Server and given the name 000301posclientlog

322 Log Feature Configuration

Logging is based on features Each feature has its own log level and is associated with a file handler (to control

which log file the feature writes its log entries to) The logger feature configuration settings consist of

LoggerltFeatureNamegtltKeywordgt=ltSettinggt

Where

Logger Is a constant indicating a Logger configuration setting

FeatureName Is a well-known feature ID for which logging is to be generated

Keyword Is one of fileHandler displayToConsole or level where

fileHandler = a FileHandler ID used to associate a Logger to a File

Handler

displayToConsole = truefalse flag indicating whether log lines should be

displayed to a console (currently only valid for Xpress Server logging)

Level = log level associated with a feature one of SEVERE WARNING INFO

CONFIG FINE FINER or FINEST with FINEST generating the most detailed

logging



CUSTOMER


Where

Setting Is the setting appropriate for a keyword

A sample xcpt log logger to write content to the xpslog file handler defined above is as follows

LoggerXCPTfileHandler=FH1

LoggerXCPTdisplayToConsole=true

LoggerXCPTlevel=INFO

323 Log File Format

All log lines written to log files have the same format They consist of

ltDategt ltSAP Thread IDWindows Thread IDgt ltLog Levelgt ltFeature NamegtltLog Entrygt

A sample EVENT log feature generated at an INFO level is as follows

Sep 16 103401 [14228c] [INFO] [EVENT] STARTUP

324 POS Client Logging

The following table provides information on the log files generated by the POS with the default PosLogini file

Logger Feature Path Description Error Condition

XCPT

EVENT

SAPTXNOBJ

TXNCOMP

BROWSER

Program Files rarr SAP

rarr Retail Systems rarr

Point of Sale rarr logs

rarr posclientlog

XCPT ndash exception errors

and diagnostic logging

EVENT ndash for logging of

major store and terminal

state events

SAPTXNOBJ ndash SAP

Transaction Object

logging

TXNCOMP ndash SAP

Transaction Object

implementation logging

BROWSER ndash POS browser

logging

Level-based logging

from error (ERROR) to

diagnostic (FINEST)

PRINTER

DRAWER

MICR

MSR

KEYBOARD

DISPLAY

LOCK




rarr OPOSlog

POS OPOS device

logging with specific

feature name for each

device

Errors logged at ERROR

level

16

CUSTOMER





SCALE

SCANNER

FISCAL_PTR

PROMO

SERVICES




rarr UElog

User exit logging PROMO

feature for Promotion

Engine User Exit logging

and SERVICES for

Services User Exit

logging

EFT_UE

EFT_IMP

PINPAD_UE

PINPAD_IMP




rarr EFTlog

EFT User Exit logging

POS generated log

entries under _UE and

user exit implementation

generated log lines

under _IMP


level



Point of Sale rarr

rdatararr alleglog

To turn ON Allegiance

Message Logging use

regedit and navigate to

the following entry

HKEY_LOCAL_MACHINE

|SOFTWARE|SAPrarr

Retail Systems rarr Point

of Sale

Create a new STRING

key called

AllegianceLogWindow

and set the string value

to 1 With this option set

the register application

creates a window that is

accessible on the

register and shows

Allegiance messages to

and from SAP POS

STORE DATA

TRANSFER FOR RETAIL

Restart the POS

application after setting

this option In addition

this option creates a file

called alleglog that

contains these

messages This file

wraps like other

standard log files and

message text is not


and from SAP POS

STORE DATA

TRANSFER FOR RETAIL



CUSTOMER



truncated

At End Of Day this file is

copied to the

cXpress

Serveruploadkeep0

logs directory

ltsssssgtltrrgtalleglo

g

where ltssssssgt is the

store number and ltrrgt

is the register number

TWSecurity Logging Event Viewer under

Application

Errors that occur in the

TWSecurity module

325 Xpress Server Logging

The following table provides information on the log files generated by the Xpress Server with the default

XpsLogini file


XCPT

EVENT

APPLY

XPS

APPLICATION

TRICKLE

COMMUNICATION

TLOG_UPLOADER



Xpress Server rarr logs

rarr xpslog





state events

APPLY ndash reports the

files that have been

applied to the Xpress

Server It also includes

logging of files that are

applied at the register

Only primary download

files are logged

XPS ndash Xpress Server

diagnostic logging

APPLICATION ndash XPS

messaging related

diagnostic logging

TRICKLE ndash Tlog posting

from POS to Xpress

Server diagnostic

logging

COMMUNICATION ndash

Any errors that occur in

SAP POS appear here

18

CUSTOMER





POSXPS Server

communication

diagnostic logging

TLOG_UPLOADER ndash real

time trickle to head

office diagnostic logging

CRSRV Program Files rarr SAP



rarr crsrvlog

The purpose of this log

file is to log credit debit

and some SAP POS

STORE DATA

TRANSFER FOR RETAIL

messages for debug

purposes

This file contains

information about credit

debit and store value

card authorizations

Any credit or SAP POS

STORE DATA

TRANSFER FOR RETAIL

communication errors

are reported here

SQL Program Files rarr SAP



rarr sqllog

SQL diagnostic logging

Apply Master Data log file Program Files rarr SAP


Xpress Server rarr

sdata rarr

ApplyBPMLog

A corresponding

trigger file

ApplyBPMTrg is

created after the

Apply process

finishes writing to

the log file

After master data is

transferred to a store it

is detected and applied

by the Xpress Server

This file logs the result

(SUCCESS or FAILURE)

of the Apply process for

each of the master data

files

A POSINI option

BPMAPPLYLOGFOLDER

allows you to specify the

folder where the

ApplyBPMlog file is

created No file is

generated if the setting

does not exist

Success and failure

statuses are logged

Reports the following

about the apply process

date and time stamp

store number filename

file size (bytes) result

(DONE or FAIL)

duration number of

records appliedrecord

number that caused the

failure

In case of failure the

following are logged

operation code

(addmodifydelete) of

the record that caused

the failure the PLUSKU

number (if present) of


the failure

EOD log file Program Files rarr SAP


Xpress Server rarr

This log file reports any

problems detected

during the EOD

Success and failure

statuses are logged




CUSTOMER



sdata rarr

EodBPMLog

(A corresponding

trigger file

EodBPMTrg is

created after the

EOD process finishes

writing to the log

file)

procedure

A POSINI option

BPMEODLOGFOLDER


folder where the

EodBPMLog file is

created No file is


does not exist

about the EOD process

date and time stamp

store number EOD state

(STARTED

COMPLETED or

FAILED) duration of

EOD process (in

seconds)

Logging of Real Time Trickled

TLog



Xpress Server rarr

sdata rarr

CLOGYYYYMMDDT

XT

This file is created daily

and contains TLog trickle

messages to SAP POS

STORE DATA

TRANSFER FOR RETAIL

Turn on logging in the

Store Configurator rarr

Register Parameters rarr

Polling Options rarr Log

Messages checkbox

Contains TLog trickle

messages to SAP POS

STORE DATA

TRANSFER FOR RETAIL

Logging of Credit Messages to

Transnet



Xpress Server rarr

sdata

Rltgtltsssssgtxml ndash

Credit Authorization

Responses from SAP

POS STORE DATA

TRANSFER FOR RETAIL

Sltgtltsssssgtxml -

Credit Request sent to

SAP POS STORE DATA

TRANSFER FOR RETAIL

ltgt = register number

ltsssssgt = credit

sequence number

Credit Messages

tofrom SAP POS

STORE DATA

TRANSFER FOR RETAIL

Note

Not all

messages are

logged

Logging of Messages to SAP

RETURNS AUTHORIZATION



Xpress Server rarr

sdata rarr

CRltgtxml and

rdataCCltgtxml

(Xpress Server PC)



Point of Sale rarr rdata

(Register PC)

CRltgtxml - Response

XML from SAP

RETURNS

AUTHORIZATION

CCltgtxml - XML

request transmitted to

SAP RETURNS

AUTHORIZATION

ltgt = the register

number

SAP RETURNS

AUTHORIZATION

messages to and from

SAP POS STORE DATA

TRANSFER FOR RETAIL

Only the last message

and response exists in

the directory


Application


TWSecurity module

20

CUSTOMER





Store Manager Error Log Program Files rarr SAP


Store Manager rarr

bkofferr

Any Store Manager

component crashes are

logged here

At EOD this file is copied

to the cXpress

Serveruploadkeep0

logs directory as

SSSSRRBKOFFERR

This is only copied if the

Store Manager

component resides on

the Xpress Server

33 Root Cause Analysis

331 Problem Analysis Using AppSight Troubleshooting Tool

Use Appsight for SAP Client Diagnostics to identify the root cause of poor client performance SAP POS setup

includes the optional installation of AppSight Service Black Box AppSight is a third-party monitoring tool used to

troubleshoot generic Windows applications

How AppSight Works

AppSight has two main parts The first part monitors all or particular applications running on a PC recording all

the details into a log file (asl) including screen shots user input program stack and other technical

information that help detect a problem You can install the recording part either as a regular application or as a

service To make the recording efficient and capture only the required application activity special recording

profiles are used (rpr)

The second part is a playback application that allows developers to play back the log file offline They can see the

details and the state of the program right before the critical error In addition to the log file debug files (such as

pdb and map) are required to obtain detailed information on an applicationrsquos internals AppSight playback

application requires an additional license and is typically only used by the SAP Support team

AppSight Installation Along with SAP POS

SAP POS installs only AppSight Service Black Box ndash an AppSight Windows service that does not require an

additional license The installation can be found with the SAP POS 103 installation package available at

servicesapcomswdc rarr Software Downloads rarr Software Download Center rarr Installations and Upgrades rarr

Browse our Download Catalog rarr Industry-specific Components rarr SAP POS



CUSTOMER


Once installed the service is configured to manually launch which ensures that it does not run at all times

thereby avoiding degrading system performance or bringing unnecessary overhead that is not immediately

required

SAP POS also installs recording profiles and helper batch files used for starting and stopping the service

For more information about AppSight Service Black Box installation along with SAP POS see the SAP Point-of-

Sale Installation Guide

AppSight Typical Use Case Scenario

The following is a scenario on how AppSight is used to troubleshoot a problem

The SAP POS application is installed on a target PC along with AppSight Service Black Box The application is

used on a daily basis while the service is stopped by default

At some point a user notices a critical error in the application performing a particular operation and contacts

the SAP support team

The support team uses the appropriate batch file to start the service with the corresponding recording profile

The support team advises the user to reproduce the issue or to continue normal operations until the error

reoccurs When the problem occurs again the user contacts the support team

The user stops the service using the batch file SAP provides and collects the recording log file for further

investigation along with additional binary and debug files from the application in question

The SAP customer representative uses the SAP Box service to transfer any large log files

Starting and Stopping of the AppSight Service

Along with each SAP POS application installed there is a shared component installed that includes SAP POS-

specific recording profiles as well as start and stop batch files

AppSight SAP POS specific files are installed to a fixed location ProgramFilesSAPRetail

SystemsAppSight

There are subfolders

Bin ndash contains StartAppSight batch files and util subfolder

Logs ndash recording log files folder where asl files are kept

RPR ndash AppSight profiles folder with rpr files

Recommendation

Do not start AppSight Service Black Box directly from the Control Panel Instead use the batch files from

the Bin folder This ensures that the service is started with the appropriate recording profile and that the

corresponding log file is stored in the Log folder so it can be easily located The Bin folder location is

added to the PATH environment variable so the batch files can be called from any location (including from

Windows Start rarr Run and command line windows)

The SAP support representative advises you on what batch file to use for each particular case

Use the StopAppSight batch file to stop the service and finalize the recording (You can start batch files by name

with or without specifying the bat extension)

The following table provides information on the batch files for AppSight

22

CUSTOMER




Batch File Name Profile Used and

Applications Monitored

Created Log File Prefix

StartAppSight_POSGeneric POSGenericrpr

bkoffexe

journalexe

poswexe

xpsexe

POSGeneric

StartAppSight_POSStoreAdministrat

ion

POSStoreAdministratio

nrpr

bkoffexe

journalexe

xpsctrlexe

POSStoreAdministration

StartAppSight_POSStoreStore

Configurator

POSStoreStore

Configuratorrpr

poscfgwexe

POSStoreStore

Configurator

StartAppSight_POSStoreOperations POSStoreOperationsrp

r

transnetexe

xpsexe

POSStoreOperations

StartAppSight_POSTerminal POSTerminalrpr

algexe

poswexe

TrvLPointsexe

POSTerminal

StopAppSight Stops the service

Log files Naming Convention

Recording rpr log files are named as follows

ltProfilePrefixgt_ltcomputernamegt_ltdategt_lttimegt_SEQltsequencenumbergtasl

where

ltProfilePrefixgt - prefix defined by profile used (see the table above)

ltcomputernamegt - PC name the service is running on

ltdategt - service launch date in format DDMMYY

lttimegt - service launch time in format HHMMSS

ltsequencenumbergt - number of the log file in the rotation sequence

Recommendation

There is a mechanism to rotate log files A maximum of 10 files is kept in a shared sequence produced

from all profiles A recording log file is overwritten once it becomes the 11th in the sequence of log files



CUSTOMER


created on a given PC If you need to keep previous version of the log files rename them before starting

the service

Starting the AppSight Service Remotely

To start the service remotely use the sc utility You need to specify the full path to a profile to be used and to an

output recording log file on the target PC as shown in the example below

sc computername start bbxservice rpr CProgram

FilesAppsightDataRPRSAPPOSrpr asl CProgram

FilesAppsightLogsPOSRecordingasl

where

bbxservice ndash AppSight Black Box service name in the system

computername -target PC name

rpr ltpathgt - a switch and path to a profile to be used by the service

asl ltpathgt - a switch and path to a log file to be created

Use quotes for long path names as shown in the example

Stopping the AppSight Service Remotely

sc ltcomputernamegt stop bbxservice

Sending Log Files to SAP Support

Once an issue is reproduced stop AppSight service using StopAppSight Locate the appropriate recording log file

in the ProgramFilesSAPRetail SystemsAppSightLogs folder

AppSight Service Best Practices

When the service is running ensure that users do not press RESET on the PC once the issue is encountered The

service has to first be stopped to allow putting all the recorded information safely into the log file

If AppSight service is running to monitor an issue on a PC and a user reboots the PC the service has to be started

again manually

34 Integration with CA Introscope

Integration with CA Introscope is part of the End-to-End Root Cause Analysis Solution The current

implementation is with Solution Manager 71

Note

For more information on this tool see httpservicesapcomdiagnostics

24

CUSTOMER




To provide this monitoring the following is required

1 Install the SMD agents as described in the SAP Point-of-Sale Installation Guide on the Xpress Server machine

These agents must be running

They are started by using the All Programs rarr SAP Management Console (select Console Root rarr SAP Systems

rarr DAA right mouse click and select Start)

2 Register with SLD (System Landscape Directory) using the Data Supplier Refer to SAP Note 1916385

3 Run managed system setup in the Solution Manager Refer to SAP Note 1916385

4 Configure the introscpasc file with your monitoring options This configuration file will turn ONOFF data

collection for the components

5 At the registers specify the SMD Agent IP by running manager code 6 If no IP is provided the application

uses the IP address of the Xpress Server

341 INTROSCPASC Turn ONOFF Data Collection

To turn ONOFF data collection create or update the introscpasc according to the instructions in the file and

send this file to the store or stores along with the newparmtrg file Once this file is applied data collection is

active or inactive depending on the settings in the introscpasc file

To obtain the default copy of introscpasc copy the introscpirs file in the cProgram

FilesSAPRetail SystemsXpress Serverparm directory The irs file provides the current active

settings The irs file is provided in the default parameter set

The default parameters installed for Introscope have all reporting turned OFF

The default contents of introscpasc are as follows

Syntax

Control file for the Introscope instrumentation of SAP POS

(Xpress Server and POS applications)

Level of Instrumentation for metric collection and trace

collection

0 = NONE (no instrumentation)

- NCS_CONF setting threshold_level_threshold=0

1 = LOW (minimal instrumentation - recommended)

- Internal instrument levels 0-9


2 = MEDIUM (medium level of instrumentation)


- NCS_CONF threshold_level_threshold=20

3 = HIGH (maximum instrumentation)



Note that this file is renamed to introscpirs



CUSTOMER


For minimal performance impact recommended settings are

XPRESS SERVER=1

BACKUP SERVER=0

R=0

XPRESS SERVER=0 set to levels 0 1 2 or 3

XPRESS SERVER SMD IP can be

XPRESS SERVER SMD IP=localHost or

XPRESS SERVER SMD IP=ip address specify ip address

of the SMD agent

Note that a change of SMD address requires this parm file

to be applied and an application restarted

XPRESS SERVER SMD IP=localHost

BACKUP SERVER=0 set to levels 0 1 2 or 3

BACKUP SERVER SMD IP can be

BACKUP SERVER SMD IP=localHost or

BACKUP SERVER SMD IP=primaryServer or

BACKUP SERVER SMD IP=ip address specify ip address

of the SMD agent



BACKUP SERVER SMD IP=primaryServer

Register Specification

R=default level of instrumentation

(used if no register is specified)

R(register number)=level of instrumentation

R=0 sets the default level for register

R1=0 Register 1

R2=0 Register 2

To view Introscope status

Introscope Status can be displayed at the store as follows

26

CUSTOMER




Xpress Server

Press Status Report on the Xpress Server console

The status message appears on the console

INTROSCOPE STATUS ON

INTROSCOPE LEVEL 10

INTROSCOPE SMD IP 106217199

POS - Register

Run manger code 8 or manager code 902 Communication Diagnostics then choose Introscope Status

This status indicates the status from instroscpasc It does not indicate whether or not the SMD agents are

running

Log Files

Log files written by the NCS library agent are given the same name as the system name plus _ncstrc and exist

in the POS or Xpress Servers program directories

Example

Cprogram filessapretail systemsXpress Server

STORE000003_ncstrc or

Cprogram filessapretail systemspoint of salerdata

STORE000003REG7_ncstrc

SMD Troubleshooting log files can be found in the following directories

CusrsapDAASMDA97SMDAgentlog

Look at most recent log file (for example SMDAgentApplicationltgtlog) The message Metric limit

exceeded stops collection Restart the agent

CusrsapDAASMDA97work

Metric Limits to Consider

Metric limits at a store have a default limit of 1000 metrics at one time Maximum instrumentation generates

about 50 metrics for the Xpress Server and 80 metrics for each register In addition the Enterprise Manager has a

limited total number of metrics across a chain The number 500000 is suggested for this implementation It is

not expected that all registers and all stores are instrumented at the same time

Functionality is instrumented according to an instrumentation level

NONE Not instrumented

LOW Minimal instrumentation (Recommended)

MEDIUM Medium instrumentation

HIGH Full instrumentation

Note

The LOW level provides all the necessary metrics to support Technical Monitoring

For minimal impact to performance the following setting for monitoring is recommended

XPRESS SERVER=1 lowest level

BACKUP SERVER=0 off

Commented [F1] I have asked Robins team for new limits



CUSTOMER


R=0 no register monitoring

342 Interpreting Performance Nodes Displayed by Introscope

For additional information on the individual nodes reported by the workstation see

httpservicesapcominstguidesrarr Industry Solutionsrarr Industry Solution Guidesrarr SAP for Retailrarr SAP Point

of-Sale rarr SAP POS 23rarrSAP POS 23 Introscope Technical Reference on the SAP Service Marketplace

35 Technical Monitoring

For Alert Event and Exception monitoring see


of-Sale rarr SAP POS 23rarr SAP POS 23 Introscope Technical Reference on the SAP Service Marketplace

36 Management of SAP POS

SAP provides you with an infrastructure to help your technical support consultants and system administrators

effectively manage all SAP components and complete all tasks related to technical administration and operation

361 Administration Tools of Software Components

The following table lists available administration tools

TransactionTool Detailed Description

In the SAP Library select Customer Relationship Mgmt rarr SAP Point-of-Sale


Store Configurator Then select Head Office Functions rarr Store Configurator

POSINI Then select Technical Product Reference rarr POSini File

Directories and Parameters Then select Technical Product Reference rarr Rdata Sdata and Parameter

subdirectories

TLog Data Capture Formats

Then select Technical Product Reference rarr TLOG Data Capture Formats

Download File Formats

(Parameter File Download

Formats)

Then select Technical Product Reference rarr Download File Formats

28

CUSTOMER







Manager Code Reference Then select Head Office Functions rarr Store Configurator rarr Additional POS

Configuration Procedures Information rarr Manager Code Reference

SDK Reference

(Software Development Kit)

Then select Technical Product Reference rarr SDK Reference

See also the httpservicesapcominstguidesrarr Industry Solutionsrarr

Industry Solution Guidesrarr SAP for Retailrarr SAP Point of-Sale rarr SAP POS

23rarrSAP Point-of-Sale 23 SDK Technical Reference Guide

This Software Development Kit provides a programming level interface to

some aspects of the application (for example SKU and employee tables)

Backup Server Then select Technical Product Reference rarr Xpress Server and Backup Server

rarr The Backup Server

Log Files

POS ServerXpress Server Log

This log file is a low level log file for the Xpress Server application

Program Files rarr SAP rarr Retail Systems rarr Xpress Server rarr logs rarr xpslog

This log file is in the log window of the POS Server console

Credit Log

These log files are low level log files

Program Files rarr SAP rarr Retail Systems rarr Point of Sale rarr logs rarr

crsrvlog

Program Files rarr SAP rarr Retail Systems rarr Xpress Server rarr logs rarr

crsrvlog

These logs contain data for credit transactions to an outside service

POS Client and Server Exception

and Event logs


Program Files rarr SAP rarr Retail Systems rarr Point of Sale rarr logs rarr xcptlog

and eventlog


xcptlog and eventlog

Log Files Viewable from the POS

Store Manager application

The following log files can be viewed from the POS Store Manager application

Applylog (log file for base parameter applies)

Xcptlog

Eventlog

(Main Menu rarr Administration rarr Log File)

Store Configurator

Program Files rarr SAP rarr Retail Systems rarr Store Configurator rarr convertlog

This file contains information about the conversion of parameter files If the

conversion fails this log file contains details about the conversion error



CUSTOMER


362 Starting and Stopping

Start and Stop Sequences and Tools

Software Component Start and Stop Sequences and Tools

Sequence Tool Detailed Description

Store Applications

Back Office Database 1 The back office

database can either

be Sybase or

Microsoft SQL

Standard database

processes apply

The back office

database must be

running for Xpress

Server or POS Store

Manager

applications to

work

Standard database

POS ServerXpress

Server

2 Xpress Server is

normally configured

as a Windows

service and can be

started or stopped

automatically or

using administrative

tools for Windows

The Xpress Server

application can also

be stopped by using

the Xpress Server

Console application

as well as

subsequently be

restarted This

console application

for the Xpress

Server can be run

from the desktop or

from the Windows

start menu Closing

the console

application does not

stop the POS Server

from running

See httphelpsapcomrarr Customer

Relationship Mgmt rarr SAP Point-of-Sale

rarr select the appropriate release of

SAP POS rarrTechnical Product

Reference rarr Xpress Server and Backup

Server rarr The Backup Server See also

the SAP Point-of-Sale Installation

Guide

Although this application is generally

run before the register application it

does not have to be

30

CUSTOMER





POS Client 3 Each register can be

started at any time

The register uses

the Xpress Server to

provide information

The POS cannot

receive information

from the Xpress

Server unless the

Xpress Server is

running POS can be

started using the

desktop icon or by

using the Start

menu It can be

stopped by running

manager code 499

(Exit POS)

POS ManagerStore

Manager Application

3 The POS Store

Manager application

run after the back

office database and

Xpress Server

applications are

running

This application

does not run if the

database is not

running Several

functions do not run

if the POS Server is

not running If the

POS Server is

stopped while this

application is still

running this

application can be

reconnected using

the Main Menu rarr

Server State rarr

Attach function

otherwise this

application needs to

be stopped and

restarted




SAP POS rarr Store and Back Office

Functions rarr Store Manager



CUSTOMER



Head Office Applications

Store Configurator 1 A Store

Configurator

database must be

installed

Start this

application from the

desktop icon or

from the Start

menu




SAP POS rarr Head Office Functions rarr

Store Configurator


Database

1 The database runs

as part of a

database server It

starts and stops

from a service

Standard Sybase database


Application

2 This application

starts from the

desktop icon of the

Start menu The

journaldb

database must be

running when this is

started





Functions rarr Store Manager rarr Store

Operations rarr Working with Journal

Files


You must back up your system landscape regularly to ensure that you can restore and recover it in case of failure

The backup and restore strategy for SAP POS consists of

Backup and restore coverage for each component (see the table below)

Cross-system data dependencies and handling

The backup and restore strategy for your system landscape should not only consider SAP systems but should

also be embedded in overall business requirements and incorporate your companyrsquos entire process flow

In addition the backup and restore strategy must cover disaster recovery processes such as the loss of a data

center through fire It is most important in this context that you ensure that backup devices are not lost together

with normal data storage (separation of storage locations)

Based on the type of application data contained in a component we have introduced a categorization scheme for

system components that can be used to analyze the backup requirements of any system component and to easily

determine an appropriate backup method for this component The following table contains a component list for

your application and the appropriate Categories

32

CUSTOMER




Component Application Data Type Backup Method for

Application Data

Restore

POS ServerXpress Server Transaction files

(txn)

Journals (jrn)

Daily totals data

Back Office database

Parameter files

Back up database

daily after the end of

the day process

Back up Xpress

Server directories

sdata rdata and

parm

Keep all current

parameter downloads

available

Make available all

parameter file

updates done during

the day

SAP recommends

using a backup server

to ensure continued

service at the store if

the POS Server

machine has a hard

drive failure

Alternatively the

LOCAL PLU feature

can be used instead

of a backup server

With the LOCAL PLU

feature product data

and pricing is kept on

each register

In the event of a hard

drive failure

Install a new hard drive

containing the Xpress

Server image

Reset the store number

Copy saved sdata

rdata and parm

directories

Restore previous

eveningrsquos back office

database

Reapply any parameters

downloaded since the

previous backup

Start the POS Server

The application populates

all journal and transaction

files and rebuilds totals

data for the day

Store Configurator Store Configurator

database

Back up database or

keep a copy of the

database when

configuration

changes


drive failure reinstall

Store Configurator and

copy the backed up Store

Configurator database

Electronic Journal Viewer Journal database

Transaction files

(txn)

Journals (jrn)

Back up database

Back up all

transaction files and

journal files


drive failure reinstall the


restore the backed up

database and copy in all

of the journal and

transaction files

POS Client In the event of a hard

drive failure on a register

install a new hard drive



CUSTOMER



Application Data

Restore

containing the POS

image Start the register

run the Terminal Define

function (manager code

6) and the Peripheral

Setup function (manager

code 2) You can either

start a new register and

new daily transactions or

use the same original

register number If using

the same register

number run manager

code 420 (import

transaction files txn

and jrn from POS

Server) andor manager

code 422 (rebuild totals)

After setup this

application will download

parameters from the POS

Server and the register

Totals files will be rebuilt

364 Periodic Tasks

3641 Scheduled Periodic Tasks

This chapter describes all automatable tasks required to run periodically in order to keep the application running

smoothly over time Such tasks may be required on component level and are therefore relevant in each scenario

that uses the component You can find the mapping in 21 ScenarioComponent Matrix Other tasks may be

relevant for certain business scenarios only It is important that you monitor the successful execution of these

tasks on a regular basis

The EODPROCBAT file is a file that is executed on the Xpress Server to perform a number of tasks related to the

End Of Day process The retailer must create this file

Implement the following tasks

Back up the back office database after the end of the day This is usually done as part of the EODPROCBAT

Shut down the Xpress Server at the end of the day with a restart afterwards This is usually done as part of the

EODPROCBAT

Download daily parameters using the transport utility (for example SAP POS STORE DATA TRANSFER FOR

RETAIL)

34

CUSTOMER




Use the EODPROCBAT to copy files for the transport function andor use this batch file to perform a file clean-

up

Run the Tmxpurge utility to remove old data from the database This will ensure that the database will not get

too big See httphelpsapcomrarr Customer Relationship Mgmt rarr SAP Point-of-Sale rarr select the

appropriate release of SAP POS rarrTechnical Product Reference rarr Operating the Databases and Utilities rarr

Viewing and Validating Databases rarr Tmxpurge Utility for details

Upload all daily sales transaction files (txn) journal files (jrn) and total files This is the record of what

happened at the store during the day Copy all log files generated and keep them for future reference

Shut down the POS at the end of the day and then restart afterwards

Implement the database purge program to keep the database an acceptable size

Run scandisk and defragmentation on a regular basis

Run antivirus software

3642 Required Manual Periodic Tasks

There are no required manual periodic tasks

365 Load Balancing

One POS ServerXpress Server can handle all registers at a store

366 Management of Logon Data

User Management Tools

Tool Detailed Description

Head Office Applications Carry out user management at the head office by creating an

empxtxnasc file containing all updates to employee

information at the store See httphelpsapcomrarr Customer

Relationship Mgmt rarr SAP Point-of-Sale rarr select the

appropriate release of SAP POS rarr Head Office Functions rarr

Store Configurator rarr Administration rarr Employee

POS ManagerStore Manager Application See httphelpsapcomrarr Customer Relationship Mgmt rarr SAP

Point-of-Sale rarr select the appropriate release of SAP POS rarr

Store and Back Office Functions rarr Store Manager rarr Store

Operations rarr Employee Management



CUSTOMER


37 High Availability

SAP POS is a Point-Of-Sale suite of products that runs in a retail store setting There are no centralized

components requiring high availability and the resiliency concept for the store components is built into the

product itself While you may opt not to use these high availability options in a typical deployment these are

employed in a manner that does not cause a single point of failure within the application

If you choose not to use the availability options included with the application t he following components could be

single points of failure

POS Server ndash This application is the store-level server for the POS terminals and POS ManagerStore

Manager Applications

Store Manager ndash This provides store reporting and other store back office support

Mobile POS Server ndash This provides business logic and data support for hand held mobile POS devices

Electronic Journal Viewer ndash This provides a view of the store transactions

All of these components run together on the store server The availability concept for the suite is covered by using

a backup store server For information on setting up a backup server see Setting Up a Backup Server in the SAP

Point-of-Sale Installation Guide Additionally the POS terminals which run the component POS Client may also

be fitted with their own local operational database to allow the selling activity to continue even if both store

servers or the store LAN fail

Components with single point of failure

Component Result Level of Impact

POS ServerXpress Server All selling activities are

blocked

Severe

Store Manager Store administrative

functions and reports are

blocked

Moderate to low

Mobile POS Server All mobile selling and

inventory management

functions are blocked

Low impact - tasks can be

performed at workstations

Electronic Journal Viewer Viewing transaction data or

receipts are blocked

Low

Each of the above components can be a single point of failure in this scenario In order to achieve high availability

(HA) for the complete scenario it is required that all components with single point of failures are setup with HA

All of the described functions can be distributed to a local backup store server In addition loss of the POS Server

can be mitigated by using a local database on each POS terminal

SAP POS provides this high availability option because these are mission-critical store systems Since load

balancing or other such data center oriented techniques do not apply to store systems support is built into and

delivered with the application

The following is an example of how users who are logged on and running transactions are affected in the event of a

system crash

36

CUSTOMER




Crash of a POS Terminal

All the POS transactions are trickled to the SAP POS Server

If the POS terminal crashes (without a hard drive failure) it can continue working without any data loss once

the POS is restarted POS can reload the last transaction that was running during the crash from the POS

Server with the power failure mechanism

If the POS terminal crashes (with a hard drive failure) the POS can be reinstalled

Once the POS is started the transaction log can be restored with the RESTORE TERMINAL TLog function

Refer to the Technical Product Reference section of the SAP Library for a detailed description

Using the transaction log at the SAP POS Server the totals can be rebuilt with the REBUILD TOTALS function


With the exception of an incomplete transaction that was running during the crash the POS can continue

running transactions without any data loss

Crash of Store Server Machine

After a crash (without a hard drive failure) once the SAP POS Server is started it will start trickling

transaction data from POS registers from the point of failure

If the store server crashes (with a hard drive failure) the set of applications installed must be reinstalled After

the POS Server is started it can receive trickle data (including data generated from before the crash) from

the POS registers

Additional required actions after a crash

Component Business Impact if Unavailable

POS Server Critical - employ backup store server option andor local POS

database on POS terminals

Store Manager Moderate

Mobile POS Server Low impact - employ backup store server option

Electronic Journal Viewer Low impact - employ backup store server option

38 Software Change Management

381 Transport and Change Management

There are no transport processes for SAP POS Change management requires a commitment to a SAP custom

development project and a consulting engagement resulting in a customer-specific code branch



CUSTOMER


382 Development Requests and Development Release Management

Once a support package is released the standard practice is for the client to install the new rele ase or upgrade in

a head office lab environment for configuration and testing In addition back -end processes need to be developed

to produce product files for the store system (for example SKU and Promotion files) Once parameters are

configured hardware peripherals set up network configuration completed and back-end processes put into

place you need to complete testing to ensure successful configuration and integration For instructions on

installing SAP POS see the SAP Point-of-Sale Installation Guide

SAP POS is released as a whole This is true for general releases and support packages Each release contains

builds of all SAP POS executables and components Many enhancements involve software changes to the

following and therefore need to be installed and upgraded

Store Configurator

Store Configurator database

POS Server

Back office database

POS

New installations can be done manually on each machine that requires the software Another common practice is

to create images of the POS Server PC and the point of sale device (register) PC These images are then copied to

the target machines at the store

Upgrades are done manually using the installation CD for each component (POS POS Server Databases

Database Tools Electronic Journal Viewer and Store Configurator) Another method of doing an upgrade is to

use the Unattended Upgrade feature For more information about the silent upgrade see Running an Unattended

Upgrade Process in the SAP Point-of-Sale Upgrade Guide

383 Support Packages and Patch Implementation

Support Packages contain a collection of error corrections They are released whole

39 Troubleshooting

POS Loses Communication with POS Server

If the POS loses communication to the POS Server you no longer have access to the transactions (for example

credit layaway lookup customer lookup)

Determine why the communication has failed Is the POS Server still running Are errors reported in the

xpslog Check the network Reboot the POS and POS Server

38

CUSTOMER




Peripheral Failures

Run manager code 900 and test peripheral functions Use the peripheral vendorrsquos diagnostic tools to determine

the problem Reconfigure the vendorrsquos hardware if necessary Install new hardware if the peripheral is faulty Run

manager code 2 to configure peripheral

Register Hard Drive Failure

Replace the hard drive If the end of the day report is run before the problem is fixed you have to bypass the

register at the end of the-day

Parameter Files Do Not Become Active

Run manager code 414 to ensure that the parameters are moved to the register Stop the POS and the POS

Server and restart them

Download the parameter files again ensuring that the newparmtrg file is in the parm directory last

Xpress Server Hard Drive Failure

Replace the hard drive and follow the recovery instructions by your company


SAP POS STORE DATA TRANSFER FOR RETAIL

CUSTOMER


4 SAP POS STORE DATA TRANSFER FOR RETAIL


411 Graphic Landscape Description

text

Tware GMXP5

TWare Enterprise

texttextXML

Socket

JMS

Connection

Java

Client

Connection

JMS

Connection

Message

ManagerXML

ISO

JMS

Connection

ISO SocketIP-

Based

IP-BasedIP-

Based

IP-

Based

Message Handler

TPS NTM

Java Client

text text

APM

APM

JMS

Connection

TPS server

connection

Message

Manager

APM

TPS NTM

Server

JMS Server

OR

OR

POS SystemSAP POS Store Data Transfer for Retail Client

(Store level)

SAP POS Store Data Transfer for Retail Server

(Head office or ASP)

412 Language Support

SAP POS STORE DATA TRANSFER FOR RETAIL does not support Unicode Support is only available in English in

North America

Problem

A problem related to TLog trickle store_1_TLogTrickleRouteERROR due to

javalangNullPointerException [2009-03-03

161916 CST]

A connection to the SAP RETURNS

AUTHORIZATION TLog trickle could not be

Connection start ERROR for

40

CUSTOMER




Problem

established (could be that SAP RETURNS

AUTHORIZATION is not running or

something else causing a connection error)

comtriversitytransnetcoretmsconnection

TNMessageConsumerConnection due to

comtriversitytransnetcoreTNException

to initialize adapter

comtriversitytransnetxtensionxreturn

ExpressReturnsTLogUploader [2009-03-05 110050

CST]

Problem log thread allocation warning Thread allocation WARNING multiple attempts(3)

needed for handler

comtriversitytransnetcoretmsmessage

TNXMLMessageHandlerd41f3 [2009-03-03 162143

CST]

Problem log thread allocation failure Thread allocation ERROR no thread allocated for

handler comtriversitytransnetcoretmsmessage

TNXMLMessageHandler8b3bb3 [2009-03-03 162402

CST]

413 JVM Memory Settings

The following directly affects how JAVA (and subsequently SAP POS STORE DATA TRANSFER FOR RETAIL)

handles memory on the server By default JAVA uses up to a maximum of 64MB of memory Once that 64MB of

memory limit is reached (usually under high transaction volume) SAP POS STORE DATA TRANSFER FOR RETAIL

may slow down considerably or stop responding all together

To adjust the JAVA memory setting edit the registry as follows

Note

These values may already have been set by an SAP Retail consultant It is possible that they may differ

from those below If they do we recommended that you consult with an SAP Retail consultant before you

change any values

HKLMSystemCurrentControlSetServicesTransnetParameters

JVM Library REG_SZ DProgram

Filestransnetjrebinse

rverjvmdll

JVM Option Count REG_DWORD 0x00000005(5)

JVM Number 0 REG_SZ -Dsunnetinetaddttl=0

JVM Number 1 REG_SZ -

Djavaclasspath=libt

ncorejartwsecurityjar

li



CUSTOMER




XX+ForceTimeHighResoluti

on

JVM Number 3 REG_SZ -Xms256M

JVM Number 4 REG_SZ -Xmx1024M

Path REG_SZ DProgram

Filestransnetbin

The most important settings are

Xms256M denotes the minimum amount of memory allocated to JAVA The 256 denotes 256MB of memory

Xmx1024M denotes the maximum amount of memory allocated to JAVA The 1024 denotes 1024MB of

memory

Note

Make sure that the JVM Option Count and the JVM Option

Numbers added to the registry match that is if you have 5 JVM Option entries then the JVM Option

Count must be set to 5

414 Database Monitoring

4141 Database Table Layout

The following sections describe the database table layout

41411 SAP POS STORE DATA TRANSFER FOR RETAIL Meter Table

The SAP POS STORE DATA TRANSFER FOR RETAIL meter table contains data on all transactions that SAP POS

STORE DATA TRANSFER FOR RETAIL processes regardless of whether or not the transaction had a successful

delivery

The following are column headings with a description from the SAP POS STORE DATA TRANSFER FOR RETAIL

meter table

Id - contains a unique identifier assigned by the SAP POS STORE DATA TRANSFER FOR RETAIL server to

every transaction handled by SAP POS STORE DATA TRANSFER FOR RETAIL

serverId - contains the unique number assigned to each production SAP POS STORE DATA TRANSFER

FOR RETAIL server This number identifies which SAP POS STORE DATA TRANSFER FOR RETAIL server

processed the transaction

42

CUSTOMER




addedTime - contains the date and time stamp of when SAP POS STORE DATA TRANSFER FOR RETAIL

received a transaction

Chain - contains the clientrsquos chain ID

Store - contains the store number that initiated the transaction

clientInstanceId - not populated

txnType - numeric value identifying the transaction type

txnState - numeric value identifying the state of the transaction

externalProcessor - numeric value pulled from the EXTPROCESSORDESC table indicating which third-

party processor handled the transaction

clientRequestTime - not populated

requestTime - time value indicating when SAP POS STORE DATA TRANSFER FOR RETAIL received the

transaction from the store

externalRequestTime - time value indicating when SAP POS STORE DATA TRANSFER FOR RETAIL sent

out the transaction to the third-party provider

externalResponseTime - time value indicating when SAP POS STORE DATA TRANSFER FOR RETAIL

received the transaction back from the third party provider

responseTime - time value indicating when SAP POS STORE DATA TRANSFER FOR RETAIL sent the

transaction back to the store

clientResponseTime - not populated

linkedId - not populated

41412 Payment Detail Table

The PAYMENT DETAIL table contains data on all successful transactions that SAP POS STORE DATA TRANSFER

FOR RETAIL processes The PAYMENT DETAIL table only contains information on financial transactions that were

successfully processed by SAP POS STORE DATA TRANSFER FOR RETAIL The following are column headings

with the description from the payment detail table

meter_id - contains a unique identifier assigned by the SAP POS STORE DATA TRANSFER FOR RETAIL

server to every transaction handled by SAP POS STORE DATA TRANSFER FOR RETAIL



Register - contains the store register number that initiated the transaction

Service - contains information on the processor that handled the transaction

tender_type - contains a numeric code for the tender type

card_type - contains information on the type of credit card used for the transaction

txn_ref_num - numeric value assigned by a third-party provider

txn_time - time the transaction occurred in SAP POS STORE DATA TRANSFER FOR RETAIL

txn_num - not populated

txn_type - contains a numeric code for the transaction type

txn_modifier - not populated

card_input_mode - not populated



CUSTOMER


card_holder_presence - not populated

card_holder_auth_method - not populated

card_holder_auth_entity card_num - not populated

card_num - contains encrypted card number data

card_expiry - contains encrypted card expiration data

Amount - dollar amount of the transaction

Cashback - not populated

action_code approval_code - numeric code passed from third party

Status - not populated

txn_timeUTC - transaction time value

Supplemental - not populated

4142 Sample SQL Queries to Monitor SAP POS STORE DATA TRANSFER FOR RETAIL

Example

Envision SAP POS STORE DATA TRANSFER FOR RETAIL is like a square where every corner represents a

time stamp from a transaction

Corner 1 Transaction from the store to SAP POS STORE DATA TRANSFER FOR RETAIL Column name

requesttime

Corner 2 Transaction leaving SAP POS STORE DATA TRANSFER FOR RETAIL and going to a third-party

provider Column name externalrequesttime

Corner 3 Transaction response coming back from a third-party provider Column name

externalresponsetime

Corner 4 Transaction response going back to the store level POS Column name responsetime

With each time stamp we can calculate total round trip times of a transaction or find the amount of time a

transaction took at a specific stage inside SAP POS STORE DATA TRANSFER FOR RETAIL

Note

If a transaction is not passed along the path in SAP POS STORE DATA TRANSFER FOR RETAIL a 0 (zero)

appears in the portion of the database indicating the phase (as shown below) that was expecting to

receive a transaction hand-off That is if a transaction is not sent out to the third-party a (0) zero

appears under the requesttime column

44

CUSTOMER




Phase1 rarr TXN into SAP POS STORE

DATA TRANSFER FOR RETAIL

Phase2 TXN out to Provider rarr

Store POS

1 2

SAP POS STORE

DATA TRANSFER

FOR RETAIL

4 3

Third Party Provider

Phase4 TXN out to Store ltmdash Phase 3 TXN in from Provider ltmdash

With basic SQL knowledge we can then execute queries against the SAP POS STORE DATA TRANSFER FOR

RETAIL database that assist in troubleshooting if any slowdowns occur

Example

Calculating Transaction Times

----- Total TXNs ------

select count () from transnet_meter

where addedtime gt 2006-01-04 060000000 and addedtime lt 2006-01-04

130000000

----Total Round Trip ----


where responsetime - requesttime gt 2500

and addedtime gt 2006-01-04 060000000 and addedtime lt 2006-01-04

130000000

----Total Time in Transnet Phase I ----


where externalrequesttime - requesttime gt 2500


130000000

---- Total Time in Transnet Phase II ----


where externalresponsetime - externalrequesttime gt 2500


130000000

----Total Time in Transnet Phase III ----


where responsetime - externalresponsetime gt 2500



CUSTOMER



130000000

Note

The items in italics are configurable and time in SAP POS STORE DATA TRANSFER FOR RETAIL is always

expressed in milliseconds

Example

Calculating Failed Txns

----Failures in Transnet Phase I ----


where externalrequesttime = 0


130000000

The following code indicates that Transnet did not send the transaction to a third-party



where externalresponsetime = 0


130000000

The following code indicates that the third-party did not send a response back in the allotted time frame



where responsetime = 0


130000000

Note



4143 Automating SAP POS STORE DATA TRANSFER FOR RETAIL Database Monitoring

Since SAP POS STORE DATA TRANSFER FOR RETAIL uses a Microsoft SQL 2008 database it can be easily

incorporated into third-party monitoring systems that allow for monitoring of applications via SQL queries

One of the methods for the monitoring of SQL databases in real time is through the use of SQL XML services for

IIS This is a reference to assist in the configuration of SQL XML via IIS

46

CUSTOMER




You gain access to MS SQL Server (2005 +) XML data via IIS (5 +) Virtual Directories The following steps show

you how to set up a Virtual Directory via the Microsoft Management Console (MMC) snap-in IIS Virtual Directory

Management for SQL Server

1 Open the IIS Virtual Directory Management for SQL Server MMC span-in

2 Right-click on the Default Web Site (or the Web Site name) for the IIS computer then choose NewVirtual

Directory

3 In the General tab set the Virtual Directory Name and Local Path to the Virtual Directorys IIS root folder (this

can remain the default wwwroot folder)

4 Set security options in the Security tab

Note

If you set up security so that the local IIS IUSR_COMPUTERNAME account is used for MS SQL Server

access first make sure that the COMPUTERNAMEIUSR_COMPUTERNAME account is set up for access to

the specified database in MS SQL Server This type of security configuration is necessary if you want an

ASPNET Web Form to have access to the Virtual Directory (as the ASPNET Web Form typically runs

under the context of the local IUSR_COMPUTERNAME account)

5 In the Data Source tab set the name of the MS SQL Server containing the data you want to extract Then set

the Database field to the name of the database containing the data you want to extract

6 In the Settings tab make appropriate settings

7 Choose OK to save your changes

The Virtual Directory in the MMC console is visible

415 Extracting Data via HTTP URLs with Internet Explorer 5 and Later

If you have setup a Virtual Directorys Settings tab to allow for URL queries below is the general syntax for

constructing such a URL

Syntax

Without XSLT transformation

httpltIISComputerNamegt[port]ltVirtualDirectoryNamegtsql=ltSelectQuerygtampRoot=ltXM

LRootNodeNamegt

With XSLT transformation

httpltIISComputerNamegt[port]ltVirtualDirectoryNamegtsql=ltSelectQuerygtampRoot=ltX

MLRootNodeNamegtampxsl=ltXSLTFileNamegt

Example of an XSLT formatted URL

httplocalhostMSSQLNorthwindsql=SELECT2020FROM20Employees20FOR20XML20

AUTOampRoot=Employeesampxsl=MSSQLNorthwindEmployeesxsl

Where

[ ] Brackets indicate the value is optional

ltIISComputerNamegt - is the name of the server where the Virtual Directory was

set up



CUSTOMER


ltVirtualDirectoryNamegt - is the name of the Virtual Directory setup on the IIS

server

ltSelectQuerygt - is any T-SQL formatted SELECT statement with the appended FOR

XML AUTO clause

For example SELECT FROM Employees FOR XML AUTO

o ltXMLRootNodegt - is the parentroot node of the XML document extracted

o ltXSLTFileNamegt - is the URL path to an XSLT transformation file to be applied

to the extracted XML data

416 Extracting Data via Template Queries with Internet Explorer 5 and Later

If you have set up Settings on the Virtual Directory tab to allow for template queries you can use XML-based

template files instead of URLs to extract data from MS SQL Server

Note

This is useful if you want to hide the details of a SELECT statement and other elements


2 Select the Default Web Site (or the Web Site name) for the IIS computer and then choose NewVirtual

Directory

3 Select the Virtual Directory that you want to set up a Virtual Template Directory for

4 Select the Virtual Names tab

5 Create a Virtual Name of Type template and set the Path to where the template files are located

6 Choose Save


If you have a Virtual Directory named MSSQLNorthwind and created a Virtual Template Directory named

template that is hosted on the same machine as the MS SQL Server instance then you would extract the MS SQL

Server data from a template XML file with the following URL

httpltlocalhostgtltMSSQLNorthwindgttemplateAllEmployeesxml

Where

ltlocalhostgt is the name of the server where the Virtual Directory was set up

ltMSSQLNorthwindgt is the name of the Virtual Directory setup on the IIS server

lttemplategt is the name of the Virtual Template Directory setup via the Virtual Names tab on the IIS server


Integration with CA Introscope is part of the End-to-End Root Cause Analysis solution The current


48

CUSTOMER




Note

For more information about this tool see httpservicesapcomdiagnostics

To provide this monitoring the following are required

1 Install the SMD agents as described in the SAP POS Store Data Transfer for Retail Installation Guide These

agents must be running

2 They are started by using the All Programs rarr SAP Management Console (select Console Root rarr SAP Systems



4 Run Managed System Setup in the Solution Manager Refer to SAP Note 1916385

5 Enable CA Introscope


1 Locate the Introscope agent files directory

For example for Introscope 82xx

CusrsapDAASMDA97SMDAgentapplicationscomsapsmdagentapplicationwily4java

_8240xxwily

For example for Introscope 91x

CusrsapDAASMDA97SMDAgentapplicationscomsapsmdagentapplicationwilybcaj5

_9150xxWily

2 Unzip ISAGENT8240-xxzip(for 824x) or ISAGENT9150-xxzip(for 915x)

This creates another Wily subdirectory


_8240xxwilyISAGENT8240-xxwily

or

CusrsapDAASMDA97SMDAgentapplicationscomsapsmdagentapplication

wilybcaj5_915xxwilyISAGENT915xxwily

3 In the rest of the setup instructions the above path is referred to as ltAGENT_HOMEgt In case of manual

installation of CA Introscope ltAGENT_HOMEgt is the folder where CA Introscope is installed Typically it is

usrsapccmswily and in the current landscape it is Cwily_transnet

4 Set Introscope agent connection properties

o Open the agentrsquos profile IntroscopeAgentprofile

o For IS agent 9 ltAGENT_HOMEgtcoreconfig

o For IS agent 8 ltAGENT_HOMEgt

o Locate the property introscopeagententerprisemanagertransporttcphostDEFAULT

o Set the value to the host name (or IP address) of the machine where Enterprise Manager resides

o dewdfgwd00537wdfsapcorp

o Locate the property introscopeagententerprisemanagertransporttcpportDEFAULT

o Set the value to the port on which the Enterprise Manager listens for Agent connections

o The default value for that property is 6001



CUSTOMER


o If the host name is not in lower case letters locate and set the property introscopeagenthostName

to the host name in lower case letters

o cayyztnsbpos23

o SAP Solution Manager requires all host names to be reported in lower case letters

o Choose the right Instrumentation packages Locate property

introscopeautoprobedirectivesFile and append the POS-Specific jar file (sap_retailjar)

to the end of the property values

o introscopeautoprobedirectivesFile=sap_typicaljar sap_retailjar

o Set these entries for Transnet locate and enable the following properties

o introscopeagentcustomProcessName=SAP Transnet Server

o introscopeagentdefaultProcessName=SAP Transnet Server

o Save the changes to the agentrsquos profile

5 Activate Introscope agent by setting Java VM parameters To activate the Introscope agent for a Transnet

process add the following additional Java VM parameters to the registry

o Open your registry and locate the following directory

o HKEY_LOCAL_MACHINESOFTWARETriversityJavaStartupTransnet

o Modify the property VirtualMachineArgs to add the following parameters

On Java 5 and Introscope agent 8

o javaagentltAGENT_HOMEgtAgentjar

o DcomwilyintroscopeagentProfileltAGENT_HOMEgtIntroscopeAgentprofile

o DcomwilyintroscopeagentagentName=ltAGENT_NAMEgt For more information refer to the

details below

Note

Once the Introscope agent is upgraded the configuration store path is changed as given below


o Javaagent ltAGENT_HOMEgtAgentjar

o DcomlwilyintroscopeagentProfileltAGENT_HOMEgtcoreconfigIntroscopeAgentpr

ofile

o Dcomwily introscopeagentagentName=ltAGENT_NAMEgt

Example

Java VM parameters

DcomwilyintroscopeagentProfile=Cwily_transnetIntroscopeAgentprofile -

javaagentCwily_transnetAgentjar -

DcomwilyintroscopeagentagentName=Transnet

6 Update SAP POS Introscope instrumentation

o Extract the SAP_Retail_Instrumenationzip attached to SAP Note 1916385 copy the extracted file

sap_retailjar and replace it with the one under ltAGENT_HOMEgtcoreconfig

o Copy sap_ext_eposjar attached to SAP Note 1916385 and replace it with the one under

ltAGENT_HOMEgtcoreext

7 Restart Transnet Service

8 Validate the activation of Introscope agent

50

CUSTOMER




o Go to the log folder under ltAGENT_HOMEgtlogs

o Make sure that a log file for the configured Introscope Agent exists The name of the log files are

o IntroscopeAgent_ltAGENT_NAMEgtlog

o AutoProbe_ltAGENT_NAMEgtlog For example AutoProbeTransnetlog

Each Java Agent running in your Introscope environment has a name whether you assigned one explicitly

configured a method of automatically assigning a name or simply started up an instrumented application that

the Java Agent monitors

The Java Agent name is important because it is central to many views and presentations in the Introscope

clients and it is the key to the process of associating monitoring logic with target applications You should

assign a unique name to each Introscope Agent running in your landscape The agent name is set by the

ltAGENT_NAMEgt Java VM parameter (see above) Follow the instructions and naming conventions precisely

Note

It is important to follow the agent naming conventions otherwise the associated monitoring logic will not

work

Note

To disable CA Introscope Transnet Server

Remove the following options from the JVM arguments (Java Virtual Machine Arguments) to disable the

CA Introscope agent


o DcomwilyintroscopeagentProfile=ltAGENT_HOMEgtIntroscopeAgentprofile

o DcomwilyintroscopeagentagentName=ltAGENT_NAMEgt


1 Extract the introscope-transnet-setupzip file attached to SAP Note 1916385 This zip file is included in the

attachment named SAP_Note_1916385-CA_Introscope_Contentrar

2 Edit the batch file introscope_transnet_setupbat for the following properties These setup parameter

variables must be configured correctly before the batch is executed The following values are just examples

o SET SOL_MAN_HOST=DEWDFGWD00537WDFSAPCORP

o SET SOL_MAN_PORT=6001

o SET JAVA_HOME=Program FilesJavajdk170_25

o SET INTROSCOPE_TRANSNET_DRIVE_LETTER=C

3 Execute the batch program introscope_transnet_setupbat which will execute the steps below from

Step 4 to Step 7 Once this batch process is successfully executed go to Step 8 ndash update SAP POS Introscope

instrumentation

Locate the Introscope agent files directory For example



4 Copy the file wilybcaj5_915xxzip to a temporary directory and unzip it to a directory named

introscope_transnet under drive property value set above in the batch file For example

Cintroscope_transnet



CUSTOMER


5 In the rest of the setup instructions the above path is referred as ltAGENT_HOMEgt In case of manual


usrsapccmswily











o If the host name is not in lower case letters locate and set the property introscopeagenthostName to

the host name in lower case letters

o cayyzssbpos23


o Choose the correct instrumentation packages for SAP POS Locate property




o Set the following properties for Transnet Client For example locate and enable the following properties

o introscopeagentcustomProcessName=SAP Transnet Client

o introscopeagentdefaultProcessName=SAP Transnet Client










o DcomwilyintroscopeagentagentName=ltAGENT_NAME

Note



o javaagent ltAGENT_HOMEgtAgentjar

o DcomwilyintroscopeagentProfileltAGENT_HOMEgtcoreconfigIntroscopeAgentpro

file

o Dcom wilyintroscopeagentagentName=ltAGENT_NAMEgt

52

CUSTOMER




Example

Java VM parameters





o Extract the SAP_Retail_Instrumenationzip attached to SAP Note 1916385 This zip file is included

in the attachment named SAP_Note_1916385-CA_Introscope_Contentrar copy the extracted file


o Copy the sap_ext_eposjar file attached to SAP Note 1916385 This jar file is included in the

attachment named SAP_Note_1916385-CA_Introscope_Contentrar and replace it with the one

under ltAGENT_HOMEgtcoreext











clients and it is the key to the process of associating monitoring logic with target applications

You should assign a unique name to each Introscope Agent running in your landscape The agent name is set

by the ltAGENT_NAMEgt Java VM parameter (see above) Follow the instructions and naming conventions

precisely

Note


work

Note

To disable CA Introscope Transnet Client


CA Introscope agent






CUSTOMER




servicesapcominstguidesrarr Industry Solutionsrarr Industry Solution Guidesrarr SAP for Retailrarr SAP Point of-Sale

rarr SAP POS 23rarrSAP POS 23 Introscope Technical Reference on the SAP Service Marketplace




rarr SAP POS 23rarrSAP POS 23 Technical Monitoring and Introscope Technical Reference on the SAP Service

Marketplace

44 Management


Store Server

HOStore Server

POS

SAP POS Store Data

Transfer for Retail

SA

P P

OS

Sto

re D

ata

Tra

nsfe

r fo

r R

eta

il

(Co

re)

NT

M C

lien

t A

PI (J

ava

)

NTM

Server

NT

M S

erv

er

AP

I (J

NI)

SAP POS Store Data

Transfer for Retail

SA

P P

OS

Sto

re D

ata

Tra

nsfe

r fo

r R

eta

il

(Co

re) Service

Provider

DB

Frontend (Web container)

RRRR

TCPIPTCPIP

Windows

Named Pipes

The optimal topology for SAP POS STORE DATA TRANSFER FOR RETAIL services dedicates a server for the data

load and SAP POS STORE DATA TRANSFER FOR RETAIL Administration module (for reporting) to ensure that

data intensive operations do not interfere with online transaction processing (being done by the primary and

secondary servers) For more information see the SAP POS Store Data Transfer for Retail Installation Guide

The SAP POS STORE DATA TRANSFER FOR RETAIL interface is a Web-based application that serves as a system

administration center You perform administrative tasks such as how to set up users task definitions and audit

schedules

54

CUSTOMER




442 Disable Sample NTM Modules

Disable any sample APMs that run on the SAP POS STORE DATA TRANSFER FOR RETAIL server These APMs are

installed by default and can be disabled without adverse However leaving these APMs running takes away

resources from SAP POS STORE DATA TRANSFER FOR RETAIL

Note

This may already have been taken care of by an SAP Retail consultant

To do this in SAP POS STORE DATA TRANSFER FOR RETAIL

1 Choose System rarrModule rarrModule Properties

2 Remove auto start from all modules except SAP POS STORE DATA TRANSFER FOR RETAIL

Note

SAP POS STORE DATA TRANSFER FOR RETAIL may not have auto-start enabled Depending on the

version of SAP POS STORE DATA TRANSFER FOR RETAIL it may be defined as a windows service rather

than a module

443 Increase Minimum Thread Count for SAP POS STORE DATA TRANSFER FOR RETAIL

In the config directory of the SAP POS STORE DATA TRANSFER FOR RETAIL install there is a file called

transnetxml This file contains the configuration information that controls how SAP POS STORE DATA

TRANSFER FOR RETAIL operates when starting up and routing messages

The configuration for minimum thread count is at the bottom of this file

ltThreadPool

Name=TransnetThreadPool

Debug=false

CleaningIntervalSeconds=60

MinimumThreads=30 gt

Depending on the volume of traffic and connections made by stores you may want to increase the minimum

thread count from its initial default value (5) to at least 30 for servers that handle more than 100 stores with

volumes that could exceed 10 tps at peak

Note

You can monitor thread count using Windows Task Manager and viewing the SAP POS STORE DATA

TRANSFER FOR RETAIL process (make sure you have selected thread count in the Task Manager under

View rarr Select Column)



CUSTOMER


444 Disable NTM Transaction Logging

Verify that the NTM Transaction Logging option is disabled on all servers To do this open the NTM module and

choose System rarr Server rarr Server Properties

From the menu select Transnet Once selected ensure that the following are not checked

Diagnostic Logging

Verbose Output

Disable Routing Messages

445 Increase Preserved NTM Server Logs

To troubleshoot a SAP POS STORE DATA TRANSFER FOR RETAIL server effectively there are circumstances in

which SAP needs to involve TPS Systems TPS Systems is the group that developed the low-level messaging

engine used in SAP POS STORE DATA TRANSFER FOR RETAIL If they become involved in resolving a SAP POS

STORE DATA TRANSFER FOR RETAIL issue they require NTM server logs By default when SAP POS STORE

DATA TRANSFER FOR RETAIL is installed the NTM server logging is set to capture a maximum of two log files

with a maximum log size of 1024 MB This setting is too low when trying to determine the cause of an issue that

arose several days ago

To change this setting from the NTM Manager screens choose System rarr NTM Manager

Select Log Daemon and change the log size to 10 MB and the number of backups also to 10 This enables TPS to

look at issues that have occurred in the past several days

446 Disable Client Reverse DNS Lookups

Add a G to the Additional Parameters field in the server configuration This disables Client DNS reverse lookups

upon connecting to the server Currently these lookups cause an approximate two-second delay on each initial

store connection each time the server is reset

Note

Only the first connection per store is affected

447 Page File

Ensure that the paging file size is set correctly in Windows

The page file is a special file used by windows for holding temporary data that is swapped in and out of physical

memory to provide a larger virtual memory set

The file name is pagefilesys and it is created during setup in the root of the boot drive as a hidden file It does

not show up on an Explorer file listing unless you toggle off the Hide System Files option In its default state the

page file should be approximately 15 times the system RAM

56

CUSTOMER




A page file can be individually set for each drive by the following

1 On the desktop right click My Computer

2 Choose Properties

3 Select the Advanced tab

4 Choose Performance Options

5 Choose Change

The Virtual Memory screen appears

You can now select the drive from the provided list and then type in the amount of memory you want dedicated to

the swap file in the provided text boxes A box is provided for the initial size and the maximum size Enter the

amount and choose Set

Note

Using the same value for the initial and maximum size improves performance and reduces fragmentation

448 SQL Server Memory

4481 Systems Configured on Windows 2000Windows NT 40Windows 2008 Servers

SQL by default is set to use all available memory dynamically This can cause problems for high volume as SQL

could contend for resources that SAP POS STORE DATA TRANSFER FOR RETAIL needs

To change the memory in SQL

1 Go to SQL Enterprise Manager

2 Right-click on the SQL server that stores the SAP POS STORE DATA TRANSFER FOR RETAIL database

3 Under Dynamic Memory Settings select Properties and adjust the settings accordingly

Note

In MS SQL Server 2008 Dynamic Memory is referred to as Other Memory

Note

For most SAP POS STORE DATA TRANSFER FOR RETAIL systems SAP recommends that you set the

minimum value to 350MB and the maximum value to be 1024MB

If you are using any of the following then the Advanced Windowing Extensions AWE enabled option should always

be left to the default value of 0 which means that the AWE memory is not being used

SQL Server 2005 Standard Edition under Windows NT 40 or Windows 2000 (any version) or

SQL Server 2005 Enterprise Edition under Windows NT 40 or Windows 2000 Server or

if your server has 4GB or less of RAM



CUSTOMER


4482 Systems Configured on Windows 2000 Advanced Server

The AWE Application Programming Interface (API) allows applications (that are written to use the AWE API) to

run under Windows 2000 Advanced Server or Windows 2000 Datacenter Server to access more than 4GB of

RAM SQL Server 2005 Enterprise Edition (not SQL Server 2005 Standard Edition) is AWE-enabled and can take

advantage of RAM in a server over 4GB If the operating system is Windows 2000 Advanced Server SQL Server

2005 Enterprise Edition can use up to 8GB of RAM If the operating system is Windows 2000 Datacenter Server

SQL Server 2005 Enterprise can use up to 64GB of RAM

By default if a physical server has more than 4GB of RAM Windows 2000 (Advanced and Datacenter) along with

SQL Server 2005 Enterprise Edition cannot access any RAM greater than 4GB Exactly how you configure AWE

memory support depends on how much RAM your server has To configure Windows 2000 (Advanced or

Datacenter) you must enter one of the following switches in the boot line of the bootini file and reboot the server

4GB RAM 3GB (AWE support is not used)

8GB RAM 3GB PAE

16GB RAM 3GB PAE

16GB + RAM PAE

The 3GB switch is used to tell the SQL Server to consume 3GB out of the 4GB of RAM available natively If you do

not specify this option then SQL Server takes advantage of only the 2GB of the first 4GB of RAM in the server not

effectively utilizing 1GB of RAM

Once this step is done the next step is to set the AWE enabled option to 1 within SQL Server Enterprise Edition

and then restart the SQL Server service Now SQL Server is able to use the additional RAM in the server

Using a query window pointed to the SQL server you are working with execute the following

Syntax

SP_CONFIGURE show advanced options 1

RECONFIGURE

GO

SP_CONFIGURE awe enabled 1

RECONFIGURE

GO

Caution

When using the AWE enabled setting after it is turned on the SQL Server no longer dynamically manages

memory and takes the entire available RAM (except for 128MB that is left for the operating system)

instead If you want to prevent SQL Server from taking the entire RAM you must set the Max Server

Memory option

Syntax

SP_CONFIGURE max server memory 4096 (Note 4096 is just an example)

RECONFIGURE

GO

58

CUSTOMER




449 Logging to DB

In the transnetxml file you will find the following setting

ltDatabase type=rdbms

Driver =cominettdsTdsDriver

Url=jdbcinetdae710100861433transnet15gt

ltConnectionPool

Debug=false

Name = TransnetJDBCPool


MinimumConnections=1

MaximumConnections=10

ConnectionLifeSeconds=1800

MaximumUseCount=25 gt

ltDatabasegt

Ensure that the correct IP address the port that SQL is listening to and the database that SAP POS STORE DATA

TRANSFER FOR RETAIL uses is set correctly

To validate if SAP POS STORE DATA TRANSFER FOR RETAIL is logging to SQL run a POS transaction against

SAP POS STORE DATA TRANSFER FOR RETAIL and then run the following query against the SAP POS STORE

DATA TRANSFER FOR RETAIL database

Select from transnet_meter

where addedtime gtlt07142005 111651 AMgt

Adjust the time and data parameters to correspond with the transaction that just ran

If logging is not successful check logtxt from the log directory for errors related to SQL connectivity

Following the above steps can eliminate potential issues that may cause slowdowns or unresponsiveness in SAP

POS STORE DATA TRANSFER FOR RETAIL during times of peak activity


There are specific instructions for starting programs and resources such as clients APIs and servers Similarly

there are specific instructions for stopping resources For more information see the SAP POS Store Data Transfer

for Retail Installation Guide


The backup and restore procedures can be applied to the system with the working windows registry for SAP POS

STORE DATA TRANSFER FOR RETAIL If the windows registry entries for SAP POS STORE DATA TRANSFER FOR

RETAIL are broken the user should reinstall the software and then follow the restore steps



CUSTOMER


Note

There is no online backup available for SAP POS STORE DATA TRANSFER FOR RETAIL The user is

expected to stop all SAP POS STORE DATA TRANSFER FOR RETAIL services before backup The steps

do not cover the backup and restore for any third-party components used by SAP POS STORE DATA

TRANSFER FOR RETAIL such as JAVA Environment MS SQL Server BouncyCastle JDBC driver

Backup

1 Stop all SAP POS STORE DATA TRANSFER FOR RETAIL services

2 Copy the CProgram FilesSAPTransnet directory or the directory where the application was initially

installed to a backup location

3 Detach the SAP POS STORE DATA TRANSFER FOR RETAIL database and copy the SAP POS STORE DATA

TRANSFER FOR RETAIL database from the installed location to a backup location

4 Attach the SAP POS STORE DATA TRANSFER FOR RETAIL database

5 Start all SAP POS STORE DATA TRANSFER FOR RETAIL services

Restore


2 Copy the backup from the backup directory to the CProgram FilesSAPTransnet directory or the

directory where the application is initially installed

3 Detach the SAP POS STORE DATA TRANSFER FOR RETAIL database copy the backup SAP POS STORE

DATA TRANSFER FOR RETAIL database into the location it is installed and overwrite the existing files



4412 Periodic Tasks

There are no periodic tasks that are defined for all customers

Each electronic funds transfer (EFT) providerclient implementation has its own way of doing reconciliation and

settlement This involves comparing TLogs from SAP POS with the EFT providersrsquo equivalent of TLogs but this is

done outside of SAP POS STORE DATA TRANSFER FOR RETAIL While SAP POS STORE DATA TRANSFER FOR

RETAIL does have the ability to load TLogs and EFT providersrsquo TLogs so they can be compared it is up to the

customer to decide how frequently the load process is done

4413 Logging On and Load Balancing

44131 Logging On

To access the SAP POS STORE DATA TRANSFER FOR RETAIL interface

1 On the SAP POS STORE DATA TRANSFER FOR RETAIL server (or any computer with Internet access) start

your Internet browser program (for example Microsoft Internet Explorer)

60

CUSTOMER




2 Go to the Internet address of the computer on which you have installed SAP POS STORE DATA TRANSFER

FOR RETAIL (ask your system administrator for the IP address or bookmark)

The SAP POS STORE DATA TRANSFER FOR RETAIL sign-in page appears

3 Enter your user logon information To do this

o In User ID type your unique SAP POS STORE DATA TRANSFER FOR RETAIL user name

Note

If you do not know or have forgotten your user identifier contact your system administrator This field is

case sensitive

o In Password type your unique SAP POS STORE DATA TRANSFER FOR RETAIL password

Note


case sensitive

Caution

SAP POS STORE DATA TRANSFER FOR RETAIL comes with a single default user called Administrator

which uses the accompanying password admin This allows initial access to the system When you first

set up your system administrator should assign unique user identifiers and passwords to each person

who uses the system Users should change their password the first time they log into the system

4 Choose Login

SAP POS STORE DATA TRANSFER FOR RETAIL main menu page appears From this page you can access all

of the administrative reporting and configuration subsystems available

You can access the configuration interfaces for both File Transfer and the Centralized Electronic Funds

Transfer components depending on which services you have installed by choosing the relevant menu

buttons on the main menu page

Note

When accessed from this interface the File Transfer and Centralized Electronic Funds Transfer

Configuration Interfaces appear in a secondary browser window following the logon process To run them

you must keep both the original and the secondary browser windows running

44132 Load Balancing

To service greater transaction throughput than can be handled by a single server SAP POS STORE DATA

TRANSFER FOR RETAIL can use multiple servers linked to a load balancer at the front end A load balancer is a

server that allocates requests among multiple servers to equalize the loads handled by each server



CUSTOMER


In-store POS System

R

Xpress Server

SAP POS Store Data Transfer for Retail

TPS Client

In-store POS System

R

Xpress Server


TPS Client

In-store POS System

R

Xpress Server


TPS Client

SAP POS Store Data

Transfer for Retail Server

TPS Server TPS Server

Load Balancer

SAP POS Store Data Transfer

for Retail Server

SAP POS Store Data



Load Balancer


for Retail Server

MS SQL Server

Database

R

R

R

R

R

R

R

R

R

TCPIP (SSL)TCPIP (SSL)TCPIP (SSL)

Primary HO System Secondary HO System

Although each SAP POS STORE DATA TRANSFER FOR RETAIL server can write to its own database this presents

a problem for features such as transaction reporting that require that all transactions for a given query be within

the same database For example if a reversal is not in the same database as the transaction it is reversing the

query would have to run against both databases and then be merged for an accurate report SAP POS STORE

DATA TRANSFER FOR RETAIL servers connected to a given load balancer can alleviate this extra work by writing

to the appropriate database



data intensive operations do not interfere with online transaction processing being done by the primary and

secondary servers Information is written to the database asynchronously with respect to transaction processing

in the SAP POS STORE DATA TRANSFER FOR RETAIL Adapter Module Therefore even if the database server

becomes busy with a report transaction processing is not affected and all data is eventually written into the

repository

The use of a Storage Area Network (SAN) provides the greatest data input output (IO) rates the most significant

physical redundancy (leveraging a RAID configuration) and the flexibility to expand storage as the need arises

The SAN should be configured with RAID level 5 for data and RAID level 1 for MS SQL logs

The minimal topology for the SAP POS STORE DATA TRANSFER FOR RETAIL Service involves two servers a

primary and secondary

62

CUSTOMER




Reporting and data loading should not be executed during periods of high volume and preferably not at all during

store operating hours

4414 User Management

The user management feature provides a central space in which you can maintain detailed informat ion and

security profiles for each of your users You can

Create new user profiles

Assign user names

Assign and modify passwords

Enter and modify personal information (for example contact information)

Define and modify user scope privileges (that is specify the chains stores and registers for which data is

available to this user)

Define and modify security clearance information

4415 Printing

Logging in to the user interface opens the SAP Centralized EFT Welcome window from which you can access the

print options via the File menu The options are

Print Report ndash generate a report for the screen you are currently in Not all windows allow you to print a report

Print Screen ndash print the current screen (only the viewable area shown)


The SAP POS Store Data Transfer for Retail Adapter modules are stateless the architecture of the SAP POS

STORE DATA TRANSFER FOR RETAIL Service can be characterized as a service-oriented architecture (SOA)

This allows for a relatively simple yet robust application-level high availability implementation (see also the

diagram in 510 Logging On and Load Balancing The SAP POS STORE DATA TRANSFER FOR RETAIL site client is

responsible for directing requests to the primary server unless the primary server fails to accept a connection or

respond within a configurable amount of time If there is a service interruption on the primary server the client

reverts to the secondary server until the primary comes back online Comprehensive internal design ensures that

there are no missed or duplicate transactions when these server redirections happen The failover and failback is

invisible to the POS operator and completely automated

Most service providers support multiple access points and most of the APMs in the library incorporate support for

multiple service provider access points ensuring that even failures at the service provider do not interrupt service

at the registers

The following diagram depicts a possible technicallogical system landscape which addresses the SAP POS

STORE DATA TRANSFER FOR RETAIL high-availability and scalability aspects (illustrating these concepts at all

tiers of the system deployment)



CUSTOMER


64

CUSTOMER






There are no transport processes for SAP POS STORE DATA TRANSFER FOR RETAIL changes This requires

commitment to an SAP custom development project and a consulting engagement and results in a customer -

specific code branch

462 Development Request and Development Release Management

There is an installation image created with every software build which is considered as a one entity component

There is no facility to modify code at the customer site

47 Troubleshooting

For more information see the Troubleshooting section in the SAP POS Store Data Transfer for Retail Installation

Guide

471 Works Cited

1) Microsoft Corporation (1997) MS Cluster Server Administrators Guide

Retrieved January 5 2006 from

httpwwwmicrosoftcomtechnetarchivewinntasproddocsdefaultmspx

2) SQL Server Performance (2001) Setting Up SQL in a Clustered Environment

Retrieved January 5 2006 from httpwwwsql-server-performancecom

3) Microsoft Corporation (2000) Server Cluster Troubleshooting


httpwwwmicrosoftcomtechnetprodtechnolwindowsserver2003libraryServerHelp549145e

4-4f5d-4545-a9b5-53ebd86d7591mspx

4) Michael G (2005) Adding Microsoft SQL Server 2000 (and later) XML Support via IIS 5


SAP RETURNS AUTHORIZATION

CUSTOMER


5 SAP RETURNS AUTHORIZATION


511 System Landscape

SAP RETURNS AUTHORIZATION is a centralized transaction service that authorizes item returns and refund

transactions requested from the SAP POS SAP RETURNS AUTHORIZATION is typically deployed at the head

office of the retailer and provides service to SAP POS across all stores SAP POS STORE DATA TRANSFER FOR

RETAIL is required to connect SAP RETURNS AUTHORIZATION and SAP POS

SAP RETURNS AUTHORIZATION is a Java EE application that is currently running on IBM WebSphere The

following diagram shows integration of all involved SAP components

SAP POS Store Data

Transfer for Retail Client

Register

Register

Express Server

JEE Engine

WebSphere

Head Office

Returns Authorization

SAP SAP POS Store Data

Transfer for Retail

SAP POS

StoreSAP SAP POS Store

Data Transfer for Retail

SAP POS Store Data


CDL

DBSQL

ServerWeb Client

R

R

R

R

R

R


SAP RETURNS AUTHORIZATION does not support Unicode Support is only available in English in North America

66

CUSTOMER




513 Proposed Components

Proper versions of applications are required to ensure successful system integration Check with your SAP

consultant regarding the supported versions of the following applications


SAP POS


514 System Requirements for SAP RETURNS AUTHORIZATION

See the SAP Returns Authorization Installation Guide

52 Monitoring and Tools for Problem and Performance Analysis

521 Trace and Log Files


Trace and Log files Path Description Major Content

WebSphere

SystemErrlog

ltWebSphere

Homegtprofilesltpro

filenamegtlogsltSer

ver

NamegtSystemErrlog

WebSphere system error

log


message and description

WebSphere

SystemOutlog

ltWebSphere

Homegtprofilesltpro

filenamegtlogsltSer

ver

NamegtSystemOutlog

WebSphere System

Output Log

WebSphere Log

Enginelogxx ltRA Install

rootgtExpressReturn

sCorelogsengine

logxx

SAP RETURNS

AUTHORIZATION engine

log

Important message or

error description for

engine and trickle

LoadLoglogxx ltRA Install

rootgtExpressReturn

sCorelogsloadLog

logxx

Or

SAP RETURNS

AUTHORIZATION batch

data loading log



batch data loading



CUSTOMER



ltCDL install

rootgtlogsloadLog

log

Important Log and Trace Files

Content File

TIMINGAUTHORIZEREQUESTxx milliseconds

Return service performance

Enginelogxx

- Parsing transaction completed successfully

- Time elapsed for parsing (sec) xxx

Trickle service performance

Enginelogxx

- SEVERE comtriversitytefcoretlogparserInfoSetHandler -

Invalid format hellip

This generally indicates TLog parsing configuration is not correct You need to verify

the TLog format with SAP RETURNS AUTHORIZATION TLog parsing configuration

core2-5xml

Enginelogxx

Any TWSecurity related error message for example bad padding mode

This indicates that the encryption key does not match between SAP POS and SAP


Another possibility is an incorrect parsing configuration SAP RETURNS

AUTHORIZATION is trying to decrypt a message that is not encrypted

Enginelogxx

- LoadFiles executing task LoadSkuFile

- LoadFiles successfully executed task LoadSkuFile

Time between above two messages is used to measure SKU loading performance

Loadloglogxx

- LoadFiles executing task LoadStoreFile

- LoadFiles successfully executed task LoadStoreFile

Time between above two messages is used to measure STORE loading

performance

Loadloglogxx

- Parse executing task ParseTLog

- Parsing TLog file completed successfully

Time between above two messages is used to measure TLog parsing (one major

step of data loading) performance

Loadloglogxx

- pipeline executing stage BulkLoad

- pipeline successfully executed stage BulkLoad

Time between above two messages is used to measure bulk load (one major step of

data loading) performance

Loadloglogxx

- Process executing task ProcessTLog

- Process successfully executed task ProcessTLog

Time between above two messages is used to measure post bulk load (one major

Loadloglogxx

68

CUSTOMER




Content File


- pipeline executing stage DataPurge

- pipeline successfully executed stage DataPurge

Time between above two messages is used to measure db purge (one major step of


Loadloglogxx

- pipeline executing stage LowPriceLoad

- pipeline successfully executed stage LowPriceLoad

Time between above two messages is used to measure low price load (one major


Loadloglogxx

522 Database Monitors

SAP RETURNS AUTHORIZATION does not provide specific tools for database monitoring In addition to the

logging support available within the application you can use Microsoft tools to troubleshoot other vendor-specific

database monitoring problems

523 Operating System Monitors

SAP RETURNS AUTHORIZATION does not provide specific tools for Operating System monitoring In addition to

the logging support available within the application you can use Microsoft tools to troubleshoot other vendor -

specific operating system problems

524 Workload Monitors

SAP RETURNS AUTHORIZATION does not provide workload monitoring

525 Other Important Problem Analysis Tools

In general SAP RETURNS AUTHORIZATION relies on monitor or analysis tools provided by platforms such as

the operating system the application server and the database It does not provide a monitoring or analysis tool



CUSTOMER


526 Interface Monitors

Interface monitors are essential for analyzing problems with interfaces such as RFC IDoc and HTTP

SAP RETURNS AUTHORIZATION interfaces with other components via RMI or JMS It relies on monitoring or

analysis tools provided by platforms such as operating system application server and database It does not

provide monitoring or analysis tools

527 Data Growth and Data Archiving Monitors

SAP RETURNS AUTHORIZATION does not provide a tool to monitor data growth It relies on the database server

to monitor data growth Inside of the SAP RETURNS AUTHORIZATION database TLog is the fastest growth data

It is fed into the database through the TLog trickle service or batch data loading process

However SAP RETURNS AUTHORIZATION internally has a process to purge data automatically including TLog

data Database purge is one step of nightly batch data loading process It purges data that is out of date This is a

step automatically completed every night

For periodic tasks required to contain data growth (that is to reorganize temporary data) refer to 59 Periodic

Tasks

528 Software Component Monitors

Monitors for the technical components are essential for analyzing problems

SAP RETURNS AUTHORIZATION does not run on SAP standard platform and does not utilize CCMS as a

monitoring tool It relies on tools provided by the operating system application server and database to monitor


Integration with CA Introscope is part of the End-to-End Root Cause Analysis solution

Note



1 Install the SMD agents as described in the SAP Returns Authorization 27 Installation Guide These agents

must be running


rarr DAA right mouse click and choose Start)




CA Introscope-Enabling IBM WebSphere

70

CUSTOMER




CA Introscope-Enabling Batch Load Process

531 CA Introscope - Enabling IBM WebSphere

1 Locate the CA Introscope agent files directory

for Introscope 82xx version


_8240xxwily

for Introscope 91x version


_9150xxWily

2 Unzip ISAGENT8240-xxzip (for 824x) or ISAGENT9150-xxzip(for 915x) This creates

another Wily subdirectory



OR



This directory is referred to as the Introscope agent files directory In the remaining instructions

ltAGENT_HOMEgt refers to this directory Substitute the actual directory accordingly

3 Set Agent connection properties

For IBM WebSphere Application Server SAP delivers the default Agent profile in the

IntroscopeAgent_websphereprofile file This file contains some SAP-Specific settings required for

IBM WebSphere Application Server The agent profile file contains different properties You have to specify

the connections properties to the Enterprise Manager All other settings can usually remain to the default

values

Open the agentrsquos profile IntroscopeAgent_websphereprofile



To configure the CA Introscope Agent update the following properties to

IntroscopeAgent_websphereprofile

Property Value

introscopeagententerprisemanagertran

sporttcphostDEFAULT=

Fully qualified host name of the Wily Enterprise Manager

server (for example usphlags06phlsapcorp)


sporttcpportDEFAULT=

Port number on which the Wily Enterprise Manager

listens for Agent connections The default value is 6001

introscopeagenthostName= SAP Solution Manager requires all host names of the

Introscope Agent to be reported in small letters

If the host name is not in small letters locate and set

this property to the host name in small letters

introscopeagentcustomProcessName= Set these entries for WebSphere



CUSTOMER


Property Value

introscopeagentdefaultProcessName=

introscopeautoprobedirectivesFile= Choose the Right Instrumentation Packages following

package is used for IBM WebSphere by default

introscopeautoprobedirectivesFile =

sap_typicaljarsap_websphere_typicaljar

This instrumentation package covers standard J2EE

functionalities (eg Servlets databaseJDBC web

services threads etc) Another instrumentation

package for WebSphere is the sap_websphere_fulljar

file It covers the same functionality but more in detail

Please use this file only if detailed analysis is needed Do

not specify both typical and full together

4 Activate CA Introscope Agent

Set Java VM parameters

To activate the CA Introscope Agent for a WebSphere application server you have to add the following additional

Java VM options

On CA Introscope agent 8

javaagent ltAGENT_HOMEgtAgentjar

DcomwilyintroscopeagentProfile=ltAGENT_HOMEgtIntroscopeAgent_websphereprofile

DcomwilyintroscopeagentagentName=ltAGENT_NAMEgt Refer to the note below for details



DcomwilyintroscopeagentProfile=ltAGENT_HOMEgtcoreconfigIntroscopeAgent_webspher

eprofile

DcomwilyintroscopeagentagentName=ltAGENT_NAMEgt Refer note below for details

You can use WebSphere Administratorrsquos UI Integration Solutions Console to specify Java VM parameters for IBM

WebSphere application server as follows

1 Go to Servers rarr Server Types rarr WebSphere Application servers and select the server that you want to

modify For example Server1

2 From the menu on the right side choose Server Infrastructure rarr Java and Process Management rarr Process

Definition rarr Additional Properties rarr Java Virtual Machine

3 Specify new Java VM parameters in the Generic JVM Arguments field

Example

DcomwilyintroscopeagentProfile=CusrsapDAASMDA97SMDAgentapplicationsco

msapsmdagentapplicationwily4java_824020120626135042wilyISAGENT824

0-2012-06-26wilyIntroscopeAgent_ websphereprofile ndash

javaagentCusrsapDAASMDA97SMDAgentapplicationscomsapsmdagentapplicat

ionwily4java_824020120626135042wilyISAGENT8240-2012-06-

26wilyAgentjar ndashDcomwilyintroscopeagentagentName= RASERVERNode01Cell

_RASERVERNode01_server1

72

CUSTOMER




Note


CA Introscope agent

-javaagentltAGENT_HOMEgtAgentjar

DcomwilyintroscopeagentProfile=ltAGENT_HOMEgtcoreconfigIntroscopeAgent_websp

hereprofile

-DcomwilyintroscopeagentagentName=ltAGENT_NAMEgt

4 Restart WebSphere

5 Validate the activation

o Go to the logs folder under ltAGENT_HOMEgtlogs

o Make sure that a log file for configured Introscope Agent exists The name of the log files are

o IntroscopeAgent_sap_WebSphereltAGENT_NAMEgtlog

o AutoProbe_WebSphereltAGENT_NAMEgtlog

The Agent Name


configured a method of automatically assigning a name or simply started up an instrumented application that the

Java Agent monitors

The Java Agent name is important because it is central to many views and presentations in the Introscope clients

and it is the key to the process of associating monitoring logic with target applications

You should assign a unique name to each Introscope Agent running in your landscape The agent name is set by

the ltAGENT_NAMEgt Java VM parameter (see above) SAP Solution Manager requires following agent naming

convention to be applied to WebSphere Application Server systems

ltAGENT_NAMEgt=ltCELL _NAMEgt_ltNODE_NAMEgt_ltAPP_SERVER_NAMEgt

ltCELL_NAMEgt - the name of the WebSphere CELL for example RASERVERNode01Cell

lt NODE_NAMEgt - the name of WebSphere Node of the application server like RASERVERNode01

ltAPP_SERVER_NAMEgt - name of WebSphere application server like server1

AGENT_NAME = RASERVERNode01Cell _RASERVERNode01_server1

Note


work

532 CA Introscope - Enabling Batch Load Process

1 Update CA Introscope Agent Profile

o Go to ltAGENT_HOMEgt

o Open the agentrsquos profile IntroscopeAgent_websphereprofile

o Locate property introscopeautoprobedirectivesFile and append the POS-specific jar file

(sap_retailjar) to the end of the property values

2 Edit the CDL batch file



CUSTOMER


o Go to ltCDL_HOMEgt

For example CProgram FilesSAPReturnsAuthorizationDataloadSAP_POS

o Open the batch file pipelinebat

o Append CA Introscope parameters to the java command


javaagent =ltAGENT_HOMEgtAgentjar

DcomwilyintroscopeagentagentName=ltAGENT_NAMEgt

o ltAGENT_HOMEgt=CusrsapDAASMDA97SMDAgentapplicationscomsapsmdagentap

plicationwily4java_824020120626135042wilyISAGENT8240-2012-06-

26wily [for Introscope version 82x]

o ltAGENT_NAMEgt= A unique name to associate the CDL batch process CDL_Batch

Note

It is important to follow the agent naming convention for agents otherwise the associated monitoring

logic will not work

o Save the file

Note

Disable CA Introscope in Batch Load Process


CA Introscope agent

javaagentltAGENT_HOMEgtAgentjar





servicesapcominstguides rarr Industry Solutionsrarr Industry Solution Guides rarr SAP for Retail rarr SAP Point-of-

Sale rarr SAP POS 23 rarr Technical Monitoring and Introscope Technical Reference Guide on the SAP Service

Marketplace





Marketplace

74

CUSTOMER




55 Management of SAP RETURNS AUTHORIZATION


effectively manage all SAP components and complete all tasks related to middleware technology


The management of the system falls into four categories

Operating system (OS0 - Windows Server)

Database (MS SQL Server 2008)

Application server (IBM WebSphere V7)

SAP applications

The OS database and application server have their own management consoles or tools to manage those parts of

the system For administration of these parts refer to the product related guides from their respective vendors


IBM WebSphere admin console

and command line tools

To start stop and monitor WebSphere application server

MS SQL Server Enterprise

Manager and related tools

To start stop and monitor MS SQL Server


The following commands outline various administration-level processes that can be performed

Command Detailed Description

startServercmd ltserver

namegt

This is an IBM WebSphere tool to start the IBM WebSphere server SAP

RETURNS AUTHORIZATION is automatically launched upon starting the

WebSphere server

Run this command from the command window under directory

ltWebSphereRootgtbin

stopServercmd ltserver

namegt

This is an IBM WebSphere tool to stop the IBM WebSphere server SAP

RETURNS AUTHORIZATION is automatically stopped with the stopping of

the WebSphere server



Pipelinebat This is the tool to start the batch data loading of SAP RETURNS

AUTHORIZATION


ltRA rootgtExpressReturnsCoreDataload



CUSTOMER



Once the process is complete the application exits automatically

Start admin UI To start admin UI of SAP RETURNS AUTHORIZATION perform these steps

1 Open the Web browser and type the URL httpltRA server

namegt9080ExpressReturnsWebRefundLoginjsp

2 Enter the user name and password If you do not know your user name or

forgot the password contact your system administrator or SAP customer

support

3 Select Login

The main menu appears

4 To stop the admin UI

a) Choose Connect from the main menu

b) Choose LoginLogout



system components You can use this schema to analyze the backup requirements of any system component and

to easily determine an appropriate backup method for this component

57 Classification

SAP RETURNS AUTHORIZATION contains application data There are several types of application data in the

system

Application configurations - either residing directly on the file system or some configurations are packaged

inside the JEE installable package

TLog archives passed from SAP POS every night

Application logs

Application data in database (MS SQL Server 2008)


SAP RETURNS AUTHORIZATION backup and restore strategy fails over to category VII from 516 Categories of

System Components for Backup and Restore as follows

76

CUSTOMER




VII Original application data standalone system data

managed by a DBMS not based on SAP WebAS

Data

Database and log backup

Backup of software

Configuration

Log files

Below are some backup and restore recommendations regarding the above data types

Application configurations

Since some configurations are included inside the JEE installable package you may want to back up the entire

returns authorization installation directory each time the installation or configuration changes

Backup and restore is file system based See the MS Windows 2003 Administrator Guide for detailed steps

Archive TLog from SAP POS every night

SAP POS pass the TLog archive to SAP RETURNS AUTHORIZATION every night for batch data loading The

archive is on the file system and after batch data load it is normally left under the directory ltdata loading

rootgtstorage

It is suggested to back up these archives daily For either troubleshooting or in case database restore is not

possible the backup can be used to restore TLog data

Application Logs

Application logs can be found under the directory ltRA installation rootgtlogs Logs can be useful for

trouble shooting Backup and restore can be performed directly on file system level

The application serverrsquos log can be considered in this scope as well The application serverrsquos log can be found

under the directory ltApplication server rootgtAppServerprofilesltprofile

namegtlogsltserver namegt

This type of data is not critical which means that data loss does not impact the functioning of the business but

may create difficulty in troubleshooting Customers can define their own backuprestore strategy for application

logs

Application Data in the Database

Application data in the database is critical for SAP RETURNS AUTHORIZATION Minimum data loss and quick

data restoration is highly desired

Therefore we recommend that you do a full database backup each week In addition we recommend that you do

a transaction log backup every night after batch data loading You may also want to consider full backups plus

differential backups based on your management strategy

59 Periodic Tasks


We recommend that you schedule the batch data loading process according to your needs Batch data loading

can be started by a command line tool This batch download looks into the data directory to pick up the TLog and

then follows the preconfigured steps to process TLogs and other tasks (based on configuration)



CUSTOMER


Recommendation

As this process creates a heavy load on the database we suggest that you run the batch data loading

process outside of your normal business hours

StandardHousekeeping Jobs

Program name Task Program name Task Program name Task

Batch data loading process

pipelinebat

Once per day SAP recommends that you

schedule this task once per day

and after normal business hours


There is no manual periodic task


The following describes the return and trickle services

Services Detailed Description Prerequisites

Return service Return service is deployed on the

JEE engine as a stateless session

bean This service can be load

balanced but ensure that

configuration files on all load

balancing nodes are the same

All load balancing nodes have to

access the same database

instance This means that the

database should be centralized


is a centralized service All data

is kept in a centralized

transaction database no

replication exists

Not applicable

Trickle service Trickle service is deployed on the

JEE engine as a message driven

bean (MDB) It is an

asynchronous service and

processes JMS messages

This service can be load

balanced but you need to ensure

Not applicable

78

CUSTOMER





that configuration files on all load










replication exists

511 User Management

5111 User Management Tools

SAP RETURNS AUTHORIZATION does not run on the standard SAP platform so it does not utilize any SAP user

management tools However SAP RETURNS AUTHORIZATION has a built-in user management tool which is

accessible from its Web Admin UI and can be used to manage any UI users



CUSTOMER


The SAP RETURNS AUTHORIZATION user management tool is only open to the administrator

Tool Detailed Description Prerequisites


Admin UI

You can use this tool to manage

all users that access the SAP


Admin UI Customer can perform

the functions user search add

edit and delete via this tool

This tool is only accessible to the

administrator

To access this tool

Open the Web browser and enter

the URL

httplthostnamegtltportgt

ExpressReturnsWebRefundL

oginjsp

Choose Administration rarr User

Maintenance

There are three levels of

permissions that can be granted

to users

Cashier - users with this

permission can only access store

functions such as transaction

search and customer

maintenance

Manager - users with this

permission can access Store

Functions and Reports but have

no access to administrative

tasks such as user maintenance

and other system parameters

maintenance

Administrator - users with this

permission can access all

functions from the Admin UI

User data is kept in the SAP


database SAP RETURNS

AUTHORIZATION is not a

distributed system and no data

replication exists


is installed and running

User

User Detailed Description Single Sign-On

Admin User admin is the default user Not applicable

80

CUSTOMER





with the SAP RETURNS

AUTHORIZATION installation

and has Administrator

permissions

Single sign-on is not supported in

SAP RETURNS

AUTHORIZATION

512 Printing

There is no printing in SAP RETURNS AUTHORIZATION Typically SAP RETURNS AUTHORIZATION is a backend

service that has no printing requirement However it is possible to print while using the administrator user

interface This printing is dependent on the browser


While implementing high availability for SAP RETURNS AUTHORIZATION you must consider high availability for

both the application and its database This approach gives you the flexibility to choose from different high

availability strategies for the application and database and eventually build a complete solution for the entire

system

Currently application high availability is supported by the application itself and the application server High

availability of the database is fully supported by the vendor

5131 High Availability at Application Level

SAP RETURNS AUTHORIZATION has two proven high availability implementations namely failover and load

balancing

SAP RETURNS AUTHORIZATION Failover

The following diagram shows the high availability implementation of SAP RETURNS AUTHORIZATION failover In

this case high availability is supported by the SAP POS STORE DATA TRANSFER FOR RETAIL server which is

located at the head office

In this approach there are two SAP RETURNS AUTHORIZATION servers or instances set up in head office

Primary instance

Backup instance

Both servers (instances) are configured identically and connect to the same database

SAP POS STORE DATA TRANSFER FOR RETAIL can be configured to deal with two SAP RETURNS

AUTHORIZATION instances It normally directs all requests to the primary instance However whenever any

problem occurs SAP POS STORE DATA TRANSFER FOR RETAIL has the capability to redirect all requests to the

backup instance for failover



CUSTOMER


MS SOL

Server


Primary Server


Backup Server

POS SAP Store Data


POS SAP Store Data


Express Server

RegisterRegister

POS SAP Store Data


Express Server

RegisterRegister

Head Office

Store 1 Store N

SAP POSSAP POS

SAP SAP POS Store



R

R

R

R

R

R

R

R

R

R

In the failover model SAP POS STORE DATA TRANSFER FOR RETAIL is configured to support high availability as

well as to improve reliability of the entire system

However there are two disadvantages in this model that need to be considered while choosing proper high

availability implementation for a customer

There is no load balancing in this configuration which means that though there are two SAP RETURNS

AUTHORIZATION servers or instances configured it cannot handle a higher load than one server can The

reason for this is that there is only one server or instance used at any given time The backup server or

instance is on standby and only becomes active when the primary server or instance encounters a problem

Trickle service is not covered by this high availability implementation This means that when control switches

from a primary to a backup server or instance trickle service is not switched on The reason for this is that

SAP POS STORE DATA TRANSFER FOR RETAIL only supports one destination for trickle and does not

provide failover

However trickle can be corrected by CDL which loads all TLogs during the storersquos nightly process thus

preventing data loss The following impact on business should be noted

82

CUSTOMER




SAP RETURNS AUTHORIZATION rejects same day returns since it cannot find the TLog from its database

The TLog goes to the database by CDL during the stores nightly process SAP RETURNS AUTHORIZATION

processes the return request the following day

Though same day return is not supported by SAP RETURNS AUTHORIZATION in this case SAP POS has the

capability to override and perform a manual return by the store manager

Web UI of SAP RETURNS AUTHORIZATION does not support automatic switchover which means that when

switchover happens the user has to manually switch to point to the backup server to user Web UI

Note

Though there are drawbacks listed above in the failover model it is still a valid and acceptable solution as

it provides high availability to return service It is also easy to set up and manage

5132 SAP RETURNS AUTHORIZATION Load Balancing

The following diagram shows how the SAP RETURNS AUTHORIZATION load balancing model works In this

configuration SAP POS STORE DATA TRANSFER FOR RETAIL does not connect to SAP RETURNS

AUTHORIZATION directly Instead it sends all requests to the load balancer and the load balancer redirects the

requests to different SAP RETURNS AUTHORIZATION servers based on their load level and availability

To avoid single point of failure in this model SAP POS STORE DATA TRANSFER FOR RETAIL should be configured

to support high availability The database should also be configured to support high availability as described later

in this guide



CUSTOMER


This approach provides some benefits as compared to the failover model

Full high availability is supported Not only for return service but it is also supported by the Web UI and trickle

service

Increased capability to handle more requests Both SAP RETURNS AUTHORIZATION servers are running

concurrently and share the load which means higher loads can be handled

Note

Although Web UI is covered in this high availability approach the UI session is not synchronized between

multiple SAP RETURNS AUTHORIZATION servers So when the load balancer switches servers the user

may have to log in again to set up a session

84

CUSTOMER




5133 High Availability at a Database Level

Database high availability is critical to the entire system Failover clustering is a solution provided by Microsoft to

ensure high availability of the database system Failover clustering is a process in which the operating system and

SQL Server 2008 work together to provide availability in the event of

Application failure

Hardware failure

Operating system error

Failover clustering provides hardware redundancy through a configuration in which mission critical resources are

automatically transferred from a failing machine to an identically configured server The following diagram shows

the high level overview of failover clustering

Below are high level descriptions about how it works

Virtual Server Virtual server is how a client views the cluster No matter how a cluster is implemented it hides

all details from the client What the client sees is a single server with its own unique server name and IP

address that is called virtual server The client works only with virtual server and does not need to identify

which node in the cluster it connects to

The client always accesses the virtual server through an external or public network

Heartbeat Heartbeat works in a private network which is set up only between the nodes The purpose of

Heartbeat is to check whether a server is up and running This occurs at regular intervals If the Heartbeat is

not functioning a failover is initiated and another node in the cluster takes over the services

Shared Disk Array The shared disk array is a collection of physical disks that is accessed by the cluster

However there is only one node in the clusterrsquos disk array at any given moment All other nodes are denied

access until they own the resource This protects the data from being overwritten when two computers have

access to the same drives simultaneously



CUSTOMER




commitment to an SAP custom development project and a consulting engagement which results in a customer-


515 Troubleshooting

SAP RETURNS AUTHORIZATION troubleshooting majorly falls into three areas authorization engine trickle

service and batch data loading

Note

Trickle is always covered by the batch data loading process The advantage of trickle is that the TLog

posting is in real time However if trickle stops working it does not cause any data loss The TLog is

loaded by batch data loading typically after business hours

All troubleshooting activities rely on application logs Below are some typical problems found from our ramp -up

customers

EncryptionDecryption Problem SAP RETURNS AUTHORIZATION is a centralized service in the SAP POS

landscape Some information exchanged between SAP RETURNS AUTHORIZATION and SAP POS are

encrypted for example credit card numbers To make sure the communication is successful both SAP

RETURNS AUTHORIZATION and SAP POS must share the same encryption key

If you see any code GeneralTWSecurityException in enginelog this most likely indicates an encryption

key mismatch between two systems To solve this problem export the encryption key from SAP POS and

import it to SAP RETURNS AUTHORIZATION

Another possibility for this error is that the parsing configuration for either trickle or CDL is incorrect It is

trying to parse and decrypt some information that is not encrypted To solve this problem we need to verify

the TLog format definition from SAP POS and compare it with the parsing configuration

Connection pool issue The connection pool sometimes exhausts during peak load In this case there should

be a message in the enginelog to state No Connection If this happens we recommend increasing the

connection pool size This can be done through the WebSphere admin console

Repeating trickle message or incomplete trickle message The trickle service repeatedly processes same

message and throw exception There are factors that can cause this problem

o WebSphere JMS retry times

o Need to check settings of WebSphere JMS retry times We recommend that you limit retry to three times

o SAP POS STORE DATA TRANSFER FOR RETAIL translates TLog (trickle request) into a wrong format in

certain instances

The following scenarios should no longer occur as they have been fixed in the system

o The TLog message has a leading 0 (zero) and it create difficulty for SAP RETURNS AUTHORIZATION to

process

SAP POS repeatedly sends a trickle message to SAP RETURNS AUTHORIZATION in certain condition

Check the SAP POS log to make sure it is not repeating the trickle message

JMS Monitoring Monitor the trickle JMS queue and system exception queue (dead letter queue) periodically

as this is the only way to identify any issues at an early stage

86

CUSTOMER




This monitoring can be done via the WebSphere administrative console The most important thing to check is

the number of messages in the trickle JMS queue and system exception queue

If you see messages accumulating in the trickle message queue refer to the above Repeating trickle message

or incomplete trickle message section above You need to regularly monitor the system exception queue

Ideally there should be no messages in this queue However it may always have messages (a few failure

messages are acceptable) It does not cause data loss since all TLogs are eventually recovered by batch data

loading process However it needs attention if the number of messages grows suddenly in this queue This

may indicate a larger problem You are required to check the application log and server log to identify the

reason for this problem

Performance monitoring There are performance related messages in the application log They need to be

checked regularly to make sure performance is stable especially when the customer is gradually migrating

stores to the SAP RETURNS AUTHORIZATION system During this period of time the load on SAP RETURNS

AUTHORIZATION is gradually growing If the log shows a downgrade in performance that is potentially

unexpected while new stores are being added it might be an early alert that needs more investigation

The performance of the authorization engine trickle service and batch loading need to be monitored

516 Categories of System Components for Backup and Restore

Categories of System

Components

Category Properties Suggested Methods for

Backup and Restore

Examples

I Only software no

configuration or

application data

- No backup new

installation in case of a

recovery or

- Initial software backup

after installation and

upgrade

- Backup of log files

BDOC Modeler

II Only software and

configuration

information no

application data

- Backup after changes

have been applied or

- No backup new

installation and

configuration in case of a

recovery


SAP Gateway

Comm Station

SAP Business

Connector

SAP IPC (20C)

III Only replicated

application data

Replication time is

sufficiently small for a

recovery

Data

- No data backup needed

- Backup of software

configuration and log

files

SAP IMSSearch

Engine

SAP IPC (20B)

Webserver

SAP ITS

IV Only replicated

application data Backup

recommended as

Data

- Application specific file

system backup or

SAP IMSSearch

Engine

Webserver



CUSTOMER



Components


Backup and Restore

Examples

replication time is too

long data not managed

by a DBMS

- Multiple instances


configuration log files

V Only replicated


recommended because


long data managed by a

DBMS

Data

- Database and log

backup or




SAP IPC (20B)

Catalog Server

VI Original application data

standalone system data

not managed by a DBMS

Data


system backup



Webserver

VII Original application data


managed by a DBMS not

based on SAP NetWeaver

AS

Data

- Database and log

backup


- Configuration

- log files

VIII Original application data

standalone system


AS

Data

- Database and log

backup application log

backup (such as job logs

in file system)



Standalone SAP

SAP System

IX Original application data

data exchange with other

systems data not

managed by a DBMS

Data


system backup data

consistency with other

systems must be

considered



X Original application data


systems data managed

by a DBMS not based on

SAP NetWeaver AS

Data

- Database and log

backup data consistency

with other systems must

be considered

SAP liveCache

SAP Mobile

Workbench

88

CUSTOMER





Components


Backup and Restore

Examples



XI Original application data


systems based on SAP

NetWeaver AS

Data

- Database and log



in file system) data


systems must be

considered



SAP System

SAP CRM

SAP APO

SAP NetWeaver Business

Warehouse


Support Desk Management

CUSTOMER


6 Support Desk Management

Support Desk Management enables you to set up an efficient internal support desk for your support organization

that seamlessly integrates your end users internal support employees partners and SAP Active Global Support

specialists with an efficient problem resolution procedure

For support desk management you need the methodology management procedures and tools infrastructure to

run your internal support organization efficiently

The following topics are covered

Remote Support

References to problem-solving solutions

Responsibility for monitoring interfaces

Responsibility for analyzing interface problems

Responsibility for solving interface problems

Typical problems

Component hierarchy relevant for this application

61 Remote Support Setup

SAP support needs to be able to work remotely for highest efficiency and availability Therefore all required

support tools must be remotely accessible for SAP support

62 Problem Message Handover

Describe the SAP component hierarchy names to be used for sending problem messagestickets to SAP

Which additional information shall be provided in a problem message per related component

90

CUSTOMER



Appendix

7 Appendix

71 Related Guides

You can find more information about installation and configuration in the Master Guide

wwwsapcomcontactsap


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 ads System i5 System

p System p5 System x System z System z10 System z9 z10 z9

iSeries pSeries xSeries zSeries eServer zVM zOS i5OS

S390 OS390 OS400 AS400 S390 Parallel Enterprise

Server PowerVM Power Architecture POWER6+ POWER6

POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes

BladeCenter System Storage GPFS HACMP RETAIN DB2

Connect RACF Redbooks OS2 Parallel Sysplex MVSESA 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 US 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 andor other countries

Oracle is a registered trademark of Oracle Corporation

UNIX XOpen OSF1 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 W3Creg 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 R3 xApps xApp SAP NetWeaver Duet PartnerEdge

ByDesign SAP Business ByDesign 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 in

several other countries all over the world 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

2

CUSTOMER





Type Style Description

Example Words or characters quoted from the screen These include field names screen titles

pushbuttons labels menu names menu paths and menu options

Textual cross-references to other documents

Example Emphasized words or expressions

EXAMPLE Technical names of system objects These include report names program names

transaction codes table names and key concepts of a programming language when they

are surrounded by body text for example SELECT and INCLUDE

Example Output on the screen This includes file and directory names and their paths messages

names of variables and parameters source text and names of installation upgrade and

database tools

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

appear in the documentation

ltExamplegt Variable user entry Angle brackets indicate that you replace these words and characters

with appropriate entries to make entries in the system

EXAMPLE Keys on the keyboard for example F2 or ENTER


Document History

CUSTOMER


Document History

Caution



Marketplace


Version Change












4

CUSTOMER



Table of Contents

Table of Contents















Table of Contents

CUSTOMER














6

CUSTOMER



Table of Contents











Getting Started

CUSTOMER


1 Getting Started

Caution



11 About this Guide







the application



Sale

Target Groups





Support Specialist


SAP POS Application





as TRANSNET

8

CUSTOMER



Getting Started

Business Scenario






business

Component




Caution


Important SAP Notes

SAP Note

Number

Title Comment


Monitoring



CUSTOMER




1 SAP POS










10

CUSTOMER




















2 SAP POS Base
























CUSTOMER






SAP Retail



Application Server










12

CUSTOMER








Store Manager

POS Client

Mobile POS Client


Database Tools


31 Analysis Tools




Application)


the Windows Start

menu




there is an error

Manager code 6 Runs

communication

diagnostics at the

register

Manager code 900

Runs peripheral

diagnostics

Manager code 999

Shows the current

version and build







problems


service when the PC

starts up

Can run a console

from the desktop to

monitor the server


console there is a

connection box that

shows the number of

registers currently

connected







the server



CUSTOMER



the Log window

(xpslog)

LSN REPORT and


console identify

technical problems


component

Started from the


the Windows Start

menu





Connected


are successful


have failed


command line

window






corrupted b-tree



the files














handlers





14

CUSTOMER






sequence number)







Note





log file name




Example







Where





Handler





logging



CUSTOMER


Where






323 Log File Format








XCPT

EVENT

SAPTXNOBJ

TXNCOMP

BROWSER




rarr posclientlog





state events

SAPTXNOBJ ndash SAP

Transaction Object

logging

TXNCOMP ndash SAP

Transaction Object



logging

Level-based logging


diagnostic (FINEST)

PRINTER

DRAWER

MICR

MSR

KEYBOARD

DISPLAY

LOCK




rarr OPOSlog

POS OPOS device



device


level

16

CUSTOMER





SCALE

SCANNER

FISCAL_PTR

PROMO

SERVICES




rarr UElog




and SERVICES for

Services User Exit

logging

EFT_UE

EFT_IMP

PINPAD_UE

PINPAD_IMP




rarr EFTlog


POS generated log



generated log lines

under _IMP


level



Point of Sale rarr

rdatararr alleglog


Message Logging use


the following entry

HKEY_LOCAL_MACHINE

|SOFTWARE|SAPrarr


of Sale

Create a new STRING

key called

AllegianceLogWindow





accessible on the

register and shows


and from SAP POS

STORE DATA

TRANSFER FOR RETAIL

Restart the POS





contains these

messages This file

wraps like other


message text is not


and from SAP POS

STORE DATA

TRANSFER FOR RETAIL



CUSTOMER



truncated


copied to the

cXpress

Serveruploadkeep0

logs directory


g





Application


TWSecurity module



XpsLogini file


XCPT

EVENT

APPLY

XPS

APPLICATION

TRICKLE

COMMUNICATION

TLOG_UPLOADER




rarr xpslog





state events








files are logged


diagnostic logging


messaging related

diagnostic logging


from POS to Xpress

Server diagnostic

logging

COMMUNICATION ndash


SAP POS appear here

18

CUSTOMER





POSXPS Server

communication

diagnostic logging







rarr crsrvlog



and some SAP POS

STORE DATA

TRANSFER FOR RETAIL

messages for debug

purposes

This file contains



card authorizations


STORE DATA

TRANSFER FOR RETAIL


are reported here




rarr sqllog




Xpress Server rarr

sdata rarr

ApplyBPMLog

A corresponding

trigger file

ApplyBPMTrg is

created after the

Apply process

finishes writing to

the log file









files

A POSINI option

BPMAPPLYLOGFOLDER


folder where the

ApplyBPMlog file is

created No file is


does not exist

Success and failure

statuses are logged



date and time stamp



(DONE or FAIL)

duration number of



failure



operation code






the failure



Xpress Server rarr


problems detected

during the EOD

Success and failure

statuses are logged




CUSTOMER



sdata rarr

EodBPMLog

(A corresponding

trigger file

EodBPMTrg is

created after the


writing to the log

file)

procedure

A POSINI option

BPMEODLOGFOLDER


folder where the

EodBPMLog file is

created No file is


does not exist


date and time stamp


(STARTED

COMPLETED or

FAILED) duration of

EOD process (in

seconds)


TLog



Xpress Server rarr

sdata rarr

CLOGYYYYMMDDT

XT



messages to SAP POS

STORE DATA

TRANSFER FOR RETAIL





Messages checkbox


messages to SAP POS

STORE DATA

TRANSFER FOR RETAIL


Transnet



Xpress Server rarr

sdata



Responses from SAP

POS STORE DATA

TRANSFER FOR RETAIL

Sltgtltsssssgtxml -


SAP POS STORE DATA

TRANSFER FOR RETAIL


ltsssssgt = credit

sequence number

Credit Messages

tofrom SAP POS

STORE DATA

TRANSFER FOR RETAIL

Note

Not all

messages are

logged





Xpress Server rarr

sdata rarr

CRltgtxml and

rdataCCltgtxml

(Xpress Server PC)




(Register PC)


XML from SAP

RETURNS

AUTHORIZATION

CCltgtxml - XML


SAP RETURNS

AUTHORIZATION

ltgt = the register

number

SAP RETURNS

AUTHORIZATION


SAP POS STORE DATA

TRANSFER FOR RETAIL



the directory


Application


TWSecurity module

20

CUSTOMER







Store Manager rarr

bkofferr

Any Store Manager


logged here


to the cXpress

Serveruploadkeep0

logs directory as

SSSSRRBKOFFERR


Store Manager


the Xpress Server






How AppSight Works

















CUSTOMER




required




















SystemsAppSight





Recommendation










22

CUSTOMER








bkoffexe

journalexe

poswexe

xpsexe

POSGeneric


ion


nrpr

bkoffexe

journalexe

xpsctrlexe



Configurator

POSStoreStore

Configuratorrpr

poscfgwexe

POSStoreStore

Configurator


r

transnetexe

xpsexe

POSStoreOperations


algexe

poswexe

TrvLPointsexe

POSTerminal





where






Recommendation





CUSTOMER



the service







where















again manually




Note


24

CUSTOMER
























Syntax




collection















CUSTOMER



XPRESS SERVER=1

BACKUP SERVER=0

R=0





of the SMD agent









of the SMD agent









R1=0 Register 1

R2=0 Register 2



26

CUSTOMER




Xpress Server




INTROSCOPE LEVEL 10


POS - Register



running

Log Files



Example




















Note




BACKUP SERVER=0 off




CUSTOMER






















subdirectories





Formats)


28

CUSTOMER









SDK Reference










Log Files





Credit Log



crsrvlog


crsrvlog



and Event logs



and eventlog







Xcptlog

Eventlog


Store Configurator






CUSTOMER






Store Applications


database can either

be Sybase or

Microsoft SQL

Standard database

processes apply

The back office

database must be

running for Xpress

Server or POS Store

Manager

applications to

work

Standard database

POS ServerXpress

Server

2 Xpress Server is

normally configured

as a Windows

service and can be

started or stopped

automatically or


tools for Windows

The Xpress Server


be stopped by using

the Xpress Server

Console application

as well as

subsequently be

restarted This

console application

for the Xpress

Server can be run

from the desktop or

from the Windows

start menu Closing

the console


stop the POS Server

from running








Guide



does not have to be

30

CUSTOMER






started at any time

The register uses


provide information

The POS cannot

receive information

from the Xpress

Server unless the

Xpress Server is

running POS can be

started using the

desktop icon or by

using the Start

menu It can be

stopped by running

manager code 499

(Exit POS)

POS ManagerStore

Manager Application

3 The POS Store

Manager application

run after the back

office database and

Xpress Server

applications are

running

This application

does not run if the

database is not

running Several



not running If the

POS Server is

stopped while this


running this

application can be

reconnected using

the Main Menu rarr

Server State rarr

Attach function

otherwise this


be stopped and

restarted








CUSTOMER





Configurator

database must be

installed

Start this


desktop icon or

from the Start

menu





Store Configurator


Database

1 The database runs

as part of a

database server It

starts and stops

from a service



Application

2 This application

starts from the

desktop icon of the

Start menu The

journaldb

database must be


started







Files















32

CUSTOMER





Application Data

Restore


(txn)

Journals (jrn)

Daily totals data


Parameter files

Back up database


the day process

Back up Xpress

Server directories

sdata rdata and

parm

Keep all current

parameter downloads

available

Make available all

parameter file

updates done during

the day

SAP recommends


to ensure continued


the POS Server

machine has a hard

drive failure

Alternatively the

LOCAL PLU feature

can be used instead

of a backup server

With the LOCAL PLU



each register


drive failure



Server image


Copy saved sdata

rdata and parm

directories

Restore previous


database



previous backup





data for the day


database

Back up database or

keep a copy of the

database when

configuration

changes







Transaction files

(txn)

Journals (jrn)

Back up database

Back up all


journal files






of the journal and

transaction files






CUSTOMER



Application Data

Restore

containing the POS











the same register

number run manager

code 420 (import


and jrn from POS



After setup this





364 Periodic Tasks












EODPROCBAT


RETAIL)

34

CUSTOMER





up













365 Load Balancing

















CUSTOMER






















blocked

Severe



blocked

Moderate to low








Low









system crash

36

CUSTOMER





















the POS registers














CUSTOMER












Store Configurator


POS Server


POS










39 Troubleshooting






38

CUSTOMER




Peripheral Failures















CUSTOMER





text

Tware GMXP5

TWare Enterprise

texttextXML

Socket

JMS

Connection

Java

Client

Connection

JMS

Connection

Message

ManagerXML

ISO

JMS

Connection

ISO SocketIP-

Based

IP-BasedIP-

Based

IP-

Based

Message Handler

TPS NTM

Java Client

text text

APM

APM

JMS

Connection

TPS server

connection

Message

Manager

APM

TPS NTM

Server

JMS Server

OR

OR


(Store level)





North America

Problem



161916 CST]




40

CUSTOMER




Problem










CST]


needed for handler



CST]




CST]







Note



change any values




rverjvmdll




Djavaclasspath=libt


li



CUSTOMER





on




Filestransnetbin




memory

Note










delivery


meter table






42

CUSTOMER













































CUSTOMER














Example




requesttime








Note





44

CUSTOMER







Store POS

1 2

SAP POS STORE

DATA TRANSFER

FOR RETAIL

4 3





Example


----- Total TXNs ------



130000000





130000000





130000000





130000000






CUSTOMER



130000000

Note



Example






130000000






130000000






130000000

Note








46

CUSTOMER









Directory




Note














Syntax



LRootNodeNamegt







Where



set up



CUSTOMER



server


XML AUTO clause








Note




Directory




6 Choose Save






Where







48

CUSTOMER




Note














_8240xxwily



_9150xxWily





or


















CUSTOMER




o cayyztnsbpos23



















details below

Note





ofile


Example

Java VM parameters











50

CUSTOMER















Note


work

Note



CA Introscope agent















instrumentation









CUSTOMER




usrsapccmswily













o cayyzssbpos23



















Note





file


52

CUSTOMER




Example

Java VM parameters
























precisely

Note


work

Note



CA Introscope agent






CUSTOMER










Marketplace

44 Management


Store Server

HOStore Server

POS

SAP POS Store Data

Transfer for Retail

SA

P P

OS

Sto

re D

ata

Tra

nsfe

r fo

r R

eta

il

(Co

re)

NT

M C

lien

t A

PI (J

ava

)

NTM

Server

NT

M S

erv

er

AP

I (J

NI)

SAP POS Store Data

Transfer for Retail

SA

P P

OS

Sto

re D

ata

Tra

nsfe

r fo

r R

eta

il

(Co

re) Service

Provider

DB


RRRR

TCPIPTCPIP

Windows

Named Pipes







schedules

54

CUSTOMER








Note





Note



than a module






ltThreadPool


Debug=false






Note






CUSTOMER






Diagnostic Logging

Verbose Output

















Note


447 Page File







56

CUSTOMER






2 Choose Properties



5 Choose Change





Note










Note


Note










CUSTOMER














8GB RAM 3GB PAE

16GB RAM 3GB PAE

16GB + RAM PAE







Syntax


RECONFIGURE

GO


RECONFIGURE

GO

Caution




Memory option

Syntax


RECONFIGURE

GO

58

CUSTOMER




449 Logging to DB





ltConnectionPool

Debug=false







ltDatabasegt






















CUSTOMER


Note





Backup








Restore








4412 Periodic Tasks








44131 Logging On




60

CUSTOMER









Note


case sensitive


Note


case sensitive

Caution





4 Choose Login






Note










CUSTOMER


In-store POS System

R

Xpress Server


TPS Client

In-store POS System

R

Xpress Server


TPS Client

In-store POS System

R

Xpress Server


TPS Client

SAP POS Store Data



Load Balancer


for Retail Server

SAP POS Store Data



Load Balancer


for Retail Server

MS SQL Server

Database

R

R

R

R

R

R

R

R

R















repository






62

CUSTOMER










Assign user names






4415 Printing

















at the registers






CUSTOMER


64

CUSTOMER












47 Troubleshooting


Guide

471 Works Cited









4-4f5d-4545-a9b5-53ebd86d7591mspx




CUSTOMER











SAP POS Store Data


Register

Register

Express Server

JEE Engine

WebSphere

Head Office



Transfer for Retail

SAP POS



SAP POS Store Data


CDL

DBSQL

ServerWeb Client

R

R

R

R

R

R



66

CUSTOMER








SAP POS








WebSphere

SystemErrlog

ltWebSphere

Homegtprofilesltpro

filenamegtlogsltSer

ver

NamegtSystemErrlog


log



WebSphere

SystemOutlog

ltWebSphere

Homegtprofilesltpro

filenamegtlogsltSer

ver

NamegtSystemOutlog

WebSphere System

Output Log

WebSphere Log


rootgtExpressReturn

sCorelogsengine

logxx

SAP RETURNS


log



engine and trickle


rootgtExpressReturn

sCorelogsloadLog

logxx

Or

SAP RETURNS

AUTHORIZATION batch

data loading log



batch data loading



CUSTOMER



ltCDL install

rootgtlogsloadLog

log


Content File



Enginelogxx




Enginelogxx





core2-5xml

Enginelogxx






Enginelogxx




Loadloglogxx




performance

Loadloglogxx





Loadloglogxx





Loadloglogxx




Loadloglogxx

68

CUSTOMER




Content File






Loadloglogxx





Loadloglogxx
















CUSTOMER















Tasks







Note




must be running







70

CUSTOMER









_8240xxwily



_9150xxWily





OR










values






Property Value
















CUSTOMER


Property Value
















Java VM options








eprofile









Example








72

CUSTOMER




Note


CA Introscope agent



hereprofile


4 Restart WebSphere






The Agent Name



Java Agent monitors











Note


work










CUSTOMER













Note


logic will not work

o Save the file

Note



CA Introscope agent








Marketplace





Marketplace

74

CUSTOMER












SAP applications














namegt



WebSphere server




namegt







AUTHORIZATION





CUSTOMER









support

3 Select Login









57 Classification


system




Application logs





76

CUSTOMER






Data


Backup of software

Configuration

Log files









rootgtstorage



Application Logs








logs







59 Periodic Tasks







CUSTOMER


Recommendation






pipelinebat























replication exists

Not applicable



bean (MDB) It is an





Not applicable

78

CUSTOMER















replication exists

511 User Management







CUSTOMER





Admin UI








administrator

To access this tool


the URL



oginjsp


Maintenance



to users




search and customer

maintenance







maintenance









replication exists



User



80

CUSTOMER








permissions


SAP RETURNS

AUTHORIZATION

512 Printing








system





balancing






Primary instance

Backup instance








CUSTOMER


MS SOL

Server


Primary Server


Backup Server

POS SAP Store Data


POS SAP Store Data


Express Server

RegisterRegister

POS SAP Store Data


Express Server

RegisterRegister

Head Office

Store 1 Store N

SAP POSSAP POS

SAP SAP POS Store



R

R

R

R

R

R

R

R

R

R












provide failover



82

CUSTOMER











Note










in this guide



CUSTOMER




service



Note




84

CUSTOMER








Application failure

Hardware failure




















CUSTOMER






515 Troubleshooting



Note





customers



















certain instances



process





86

CUSTOMER





















Components


Backup and Restore

Examples

I Only software no

configuration or

application data

- No backup new


recovery or



upgrade


BDOC Modeler


configuration

information no

application data



- No backup new

installation and


recovery


SAP Gateway

Comm Station

SAP Business

Connector

SAP IPC (20C)

III Only replicated

application data

Replication time is


recovery

Data




files

SAP IMSSearch

Engine

SAP IPC (20B)

Webserver

SAP ITS

IV Only replicated


recommended as

Data


system backup or

SAP IMSSearch

Engine

Webserver



CUSTOMER



Components


Backup and Restore

Examples



by a DBMS




V Only replicated


recommended because



DBMS

Data

- Database and log

backup or




SAP IPC (20B)

Catalog Server




Data


system backup



Webserver





AS

Data

- Database and log

backup


- Configuration

- log files


standalone system


AS

Data

- Database and log



in file system)



Standalone SAP

SAP System



systems data not

managed by a DBMS

Data


system backup data


systems must be

considered







SAP NetWeaver AS

Data

- Database and log



be considered

SAP liveCache

SAP Mobile

Workbench

88

CUSTOMER





Components


Backup and Restore

Examples






NetWeaver AS

Data

- Database and log





systems must be

considered



SAP System

SAP CRM

SAP APO


Warehouse



CUSTOMER









Remote Support





Typical problems








90

CUSTOMER



Appendix

7 Appendix

71 Related Guides


wwwsapcomcontactsap





notice



vendors














other countries






Open Group










Netscape



















Document History

CUSTOMER


Document History

Caution



Marketplace


Version Change












4

CUSTOMER



Table of Contents

Table of Contents















Table of Contents

CUSTOMER














6

CUSTOMER



Table of Contents











Getting Started

CUSTOMER


1 Getting Started

Caution



11 About this Guide







the application



Sale

Target Groups





Support Specialist


SAP POS Application





as TRANSNET

8

CUSTOMER



Getting Started

Business Scenario






business

Component




Caution


Important SAP Notes

SAP Note

Number

Title Comment


Monitoring



CUSTOMER




1 SAP POS










10

CUSTOMER




















2 SAP POS Base
























CUSTOMER






SAP Retail



Application Server










12

CUSTOMER








Store Manager

POS Client

Mobile POS Client


Database Tools


31 Analysis Tools




Application)


the Windows Start

menu




there is an error

Manager code 6 Runs

communication

diagnostics at the

register

Manager code 900

Runs peripheral

diagnostics

Manager code 999

Shows the current

version and build







problems


service when the PC

starts up

Can run a console

from the desktop to

monitor the server


console there is a

connection box that

shows the number of

registers currently

connected







the server



CUSTOMER



the Log window

(xpslog)

LSN REPORT and


console identify

technical problems


component

Started from the


the Windows Start

menu





Connected


are successful


have failed


command line

window






corrupted b-tree



the files














handlers





14

CUSTOMER






sequence number)







Note





log file name




Example







Where





Handler





logging



CUSTOMER


Where






323 Log File Format








XCPT

EVENT

SAPTXNOBJ

TXNCOMP

BROWSER




rarr posclientlog





state events

SAPTXNOBJ ndash SAP

Transaction Object

logging

TXNCOMP ndash SAP

Transaction Object



logging

Level-based logging


diagnostic (FINEST)

PRINTER

DRAWER

MICR

MSR

KEYBOARD

DISPLAY

LOCK




rarr OPOSlog

POS OPOS device



device


level

16

CUSTOMER





SCALE

SCANNER

FISCAL_PTR

PROMO

SERVICES




rarr UElog




and SERVICES for

Services User Exit

logging

EFT_UE

EFT_IMP

PINPAD_UE

PINPAD_IMP




rarr EFTlog


POS generated log



generated log lines

under _IMP


level



Point of Sale rarr

rdatararr alleglog


Message Logging use


the following entry

HKEY_LOCAL_MACHINE

|SOFTWARE|SAPrarr


of Sale

Create a new STRING

key called

AllegianceLogWindow





accessible on the

register and shows


and from SAP POS

STORE DATA

TRANSFER FOR RETAIL

Restart the POS





contains these

messages This file

wraps like other


message text is not


and from SAP POS

STORE DATA

TRANSFER FOR RETAIL



CUSTOMER



truncated


copied to the

cXpress

Serveruploadkeep0

logs directory


g





Application


TWSecurity module



XpsLogini file


XCPT

EVENT

APPLY

XPS

APPLICATION

TRICKLE

COMMUNICATION

TLOG_UPLOADER




rarr xpslog





state events








files are logged


diagnostic logging


messaging related

diagnostic logging


from POS to Xpress

Server diagnostic

logging

COMMUNICATION ndash


SAP POS appear here

18

CUSTOMER





POSXPS Server

communication

diagnostic logging







rarr crsrvlog



and some SAP POS

STORE DATA

TRANSFER FOR RETAIL

messages for debug

purposes

This file contains



card authorizations


STORE DATA

TRANSFER FOR RETAIL


are reported here




rarr sqllog




Xpress Server rarr

sdata rarr

ApplyBPMLog

A corresponding

trigger file

ApplyBPMTrg is

created after the

Apply process

finishes writing to

the log file









files

A POSINI option

BPMAPPLYLOGFOLDER


folder where the

ApplyBPMlog file is

created No file is


does not exist

Success and failure

statuses are logged



date and time stamp



(DONE or FAIL)

duration number of



failure



operation code






the failure



Xpress Server rarr


problems detected

during the EOD

Success and failure

statuses are logged




CUSTOMER



sdata rarr

EodBPMLog

(A corresponding

trigger file

EodBPMTrg is

created after the


writing to the log

file)

procedure

A POSINI option

BPMEODLOGFOLDER


folder where the

EodBPMLog file is

created No file is


does not exist


date and time stamp


(STARTED

COMPLETED or

FAILED) duration of

EOD process (in

seconds)


TLog



Xpress Server rarr

sdata rarr

CLOGYYYYMMDDT

XT



messages to SAP POS

STORE DATA

TRANSFER FOR RETAIL





Messages checkbox


messages to SAP POS

STORE DATA

TRANSFER FOR RETAIL


Transnet



Xpress Server rarr

sdata



Responses from SAP

POS STORE DATA

TRANSFER FOR RETAIL

Sltgtltsssssgtxml -


SAP POS STORE DATA

TRANSFER FOR RETAIL


ltsssssgt = credit

sequence number

Credit Messages

tofrom SAP POS

STORE DATA

TRANSFER FOR RETAIL

Note

Not all

messages are

logged





Xpress Server rarr

sdata rarr

CRltgtxml and

rdataCCltgtxml

(Xpress Server PC)




(Register PC)


XML from SAP

RETURNS

AUTHORIZATION

CCltgtxml - XML


SAP RETURNS

AUTHORIZATION

ltgt = the register

number

SAP RETURNS

AUTHORIZATION


SAP POS STORE DATA

TRANSFER FOR RETAIL



the directory


Application


TWSecurity module

20

CUSTOMER







Store Manager rarr

bkofferr

Any Store Manager


logged here


to the cXpress

Serveruploadkeep0

logs directory as

SSSSRRBKOFFERR


Store Manager


the Xpress Server






How AppSight Works

















CUSTOMER




required




















SystemsAppSight





Recommendation










22

CUSTOMER








bkoffexe

journalexe

poswexe

xpsexe

POSGeneric


ion


nrpr

bkoffexe

journalexe

xpsctrlexe



Configurator

POSStoreStore

Configuratorrpr

poscfgwexe

POSStoreStore

Configurator


r

transnetexe

xpsexe

POSStoreOperations


algexe

poswexe

TrvLPointsexe

POSTerminal





where






Recommendation





CUSTOMER



the service







where















again manually




Note


24

CUSTOMER
























Syntax




collection















CUSTOMER



XPRESS SERVER=1

BACKUP SERVER=0

R=0





of the SMD agent









of the SMD agent









R1=0 Register 1

R2=0 Register 2



26

CUSTOMER




Xpress Server




INTROSCOPE LEVEL 10


POS - Register



running

Log Files



Example




















Note




BACKUP SERVER=0 off




CUSTOMER






















subdirectories





Formats)


28

CUSTOMER









SDK Reference










Log Files





Credit Log



crsrvlog


crsrvlog



and Event logs



and eventlog







Xcptlog

Eventlog


Store Configurator






CUSTOMER






Store Applications


database can either

be Sybase or

Microsoft SQL

Standard database

processes apply

The back office

database must be

running for Xpress

Server or POS Store

Manager

applications to

work

Standard database

POS ServerXpress

Server

2 Xpress Server is

normally configured

as a Windows

service and can be

started or stopped

automatically or


tools for Windows

The Xpress Server


be stopped by using

the Xpress Server

Console application

as well as

subsequently be

restarted This

console application

for the Xpress

Server can be run

from the desktop or

from the Windows

start menu Closing

the console


stop the POS Server

from running








Guide



does not have to be

30

CUSTOMER






started at any time

The register uses


provide information

The POS cannot

receive information

from the Xpress

Server unless the

Xpress Server is

running POS can be

started using the

desktop icon or by

using the Start

menu It can be

stopped by running

manager code 499

(Exit POS)

POS ManagerStore

Manager Application

3 The POS Store

Manager application

run after the back

office database and

Xpress Server

applications are

running

This application

does not run if the

database is not

running Several



not running If the

POS Server is

stopped while this


running this

application can be

reconnected using

the Main Menu rarr

Server State rarr

Attach function

otherwise this


be stopped and

restarted








CUSTOMER





Configurator

database must be

installed

Start this


desktop icon or

from the Start

menu





Store Configurator


Database

1 The database runs

as part of a

database server It

starts and stops

from a service



Application

2 This application

starts from the

desktop icon of the

Start menu The

journaldb

database must be


started







Files















32

CUSTOMER





Application Data

Restore


(txn)

Journals (jrn)

Daily totals data


Parameter files

Back up database


the day process

Back up Xpress

Server directories

sdata rdata and

parm

Keep all current

parameter downloads

available

Make available all

parameter file

updates done during

the day

SAP recommends


to ensure continued


the POS Server

machine has a hard

drive failure

Alternatively the

LOCAL PLU feature

can be used instead

of a backup server

With the LOCAL PLU



each register


drive failure



Server image


Copy saved sdata

rdata and parm

directories

Restore previous


database



previous backup





data for the day


database

Back up database or

keep a copy of the

database when

configuration

changes







Transaction files

(txn)

Journals (jrn)

Back up database

Back up all


journal files






of the journal and

transaction files






CUSTOMER



Application Data

Restore

containing the POS











the same register

number run manager

code 420 (import


and jrn from POS



After setup this





364 Periodic Tasks












EODPROCBAT


RETAIL)

34

CUSTOMER





up













365 Load Balancing

















CUSTOMER






















blocked

Severe



blocked

Moderate to low








Low









system crash

36

CUSTOMER





















the POS registers














CUSTOMER












Store Configurator


POS Server


POS










39 Troubleshooting






38

CUSTOMER




Peripheral Failures















CUSTOMER





text

Tware GMXP5

TWare Enterprise

texttextXML

Socket

JMS

Connection

Java

Client

Connection

JMS

Connection

Message

ManagerXML

ISO

JMS

Connection

ISO SocketIP-

Based

IP-BasedIP-

Based

IP-

Based

Message Handler

TPS NTM

Java Client

text text

APM

APM

JMS

Connection

TPS server

connection

Message

Manager

APM

TPS NTM

Server

JMS Server

OR

OR


(Store level)





North America

Problem



161916 CST]




40

CUSTOMER




Problem










CST]


needed for handler



CST]




CST]







Note



change any values




rverjvmdll




Djavaclasspath=libt


li



CUSTOMER





on




Filestransnetbin




memory

Note










delivery


meter table






42

CUSTOMER













































CUSTOMER














Example




requesttime








Note





44

CUSTOMER







Store POS

1 2

SAP POS STORE

DATA TRANSFER

FOR RETAIL

4 3





Example


----- Total TXNs ------



130000000





130000000





130000000





130000000






CUSTOMER



130000000

Note



Example






130000000






130000000






130000000

Note








46

CUSTOMER









Directory




Note














Syntax



LRootNodeNamegt







Where



set up



CUSTOMER



server


XML AUTO clause








Note




Directory




6 Choose Save






Where







48

CUSTOMER




Note














_8240xxwily



_9150xxWily





or


















CUSTOMER




o cayyztnsbpos23



















details below

Note





ofile


Example

Java VM parameters











50

CUSTOMER















Note


work

Note



CA Introscope agent















instrumentation









CUSTOMER




usrsapccmswily













o cayyzssbpos23



















Note





file


52

CUSTOMER




Example

Java VM parameters
























precisely

Note


work

Note



CA Introscope agent






CUSTOMER










Marketplace

44 Management


Store Server

HOStore Server

POS

SAP POS Store Data

Transfer for Retail

SA

P P

OS

Sto

re D

ata

Tra

nsfe

r fo

r R

eta

il

(Co

re)

NT

M C

lien

t A

PI (J

ava

)

NTM

Server

NT

M S

erv

er

AP

I (J

NI)

SAP POS Store Data

Transfer for Retail

SA

P P

OS

Sto

re D

ata

Tra

nsfe

r fo

r R

eta

il

(Co

re) Service

Provider

DB


RRRR

TCPIPTCPIP

Windows

Named Pipes







schedules

54

CUSTOMER








Note





Note



than a module






ltThreadPool


Debug=false






Note






CUSTOMER






Diagnostic Logging

Verbose Output

















Note


447 Page File







56

CUSTOMER






2 Choose Properties



5 Choose Change





Note










Note


Note










CUSTOMER














8GB RAM 3GB PAE

16GB RAM 3GB PAE

16GB + RAM PAE







Syntax


RECONFIGURE

GO


RECONFIGURE

GO

Caution




Memory option

Syntax


RECONFIGURE

GO

58

CUSTOMER




449 Logging to DB





ltConnectionPool

Debug=false







ltDatabasegt






















CUSTOMER


Note





Backup








Restore








4412 Periodic Tasks








44131 Logging On




60

CUSTOMER









Note


case sensitive


Note


case sensitive

Caution





4 Choose Login






Note










CUSTOMER


In-store POS System

R

Xpress Server


TPS Client

In-store POS System

R

Xpress Server


TPS Client

In-store POS System

R

Xpress Server


TPS Client

SAP POS Store Data



Load Balancer


for Retail Server

SAP POS Store Data



Load Balancer


for Retail Server

MS SQL Server

Database

R

R

R

R

R

R

R

R

R















repository






62

CUSTOMER










Assign user names






4415 Printing

















at the registers






CUSTOMER


64

CUSTOMER












47 Troubleshooting


Guide

471 Works Cited









4-4f5d-4545-a9b5-53ebd86d7591mspx




CUSTOMER











SAP POS Store Data


Register

Register

Express Server

JEE Engine

WebSphere

Head Office



Transfer for Retail

SAP POS



SAP POS Store Data


CDL

DBSQL

ServerWeb Client

R

R

R

R

R

R



66

CUSTOMER








SAP POS








WebSphere

SystemErrlog

ltWebSphere

Homegtprofilesltpro

filenamegtlogsltSer

ver

NamegtSystemErrlog


log



WebSphere

SystemOutlog

ltWebSphere

Homegtprofilesltpro

filenamegtlogsltSer

ver

NamegtSystemOutlog

WebSphere System

Output Log

WebSphere Log


rootgtExpressReturn

sCorelogsengine

logxx

SAP RETURNS


log



engine and trickle


rootgtExpressReturn

sCorelogsloadLog

logxx

Or

SAP RETURNS

AUTHORIZATION batch

data loading log



batch data loading



CUSTOMER



ltCDL install

rootgtlogsloadLog

log


Content File



Enginelogxx




Enginelogxx





core2-5xml

Enginelogxx






Enginelogxx




Loadloglogxx




performance

Loadloglogxx





Loadloglogxx





Loadloglogxx




Loadloglogxx

68

CUSTOMER




Content File






Loadloglogxx





Loadloglogxx
















CUSTOMER















Tasks







Note




must be running







70

CUSTOMER









_8240xxwily



_9150xxWily





OR










values






Property Value
















CUSTOMER


Property Value
















Java VM options








eprofile









Example








72

CUSTOMER




Note


CA Introscope agent



hereprofile


4 Restart WebSphere






The Agent Name



Java Agent monitors











Note


work










CUSTOMER













Note


logic will not work

o Save the file

Note



CA Introscope agent








Marketplace





Marketplace

74

CUSTOMER












SAP applications














namegt



WebSphere server




namegt







AUTHORIZATION





CUSTOMER









support

3 Select Login









57 Classification


system




Application logs





76

CUSTOMER






Data


Backup of software

Configuration

Log files









rootgtstorage



Application Logs








logs







59 Periodic Tasks







CUSTOMER


Recommendation






pipelinebat























replication exists

Not applicable



bean (MDB) It is an





Not applicable

78

CUSTOMER















replication exists

511 User Management







CUSTOMER





Admin UI








administrator

To access this tool


the URL



oginjsp


Maintenance



to users




search and customer

maintenance







maintenance









replication exists



User



80

CUSTOMER








permissions


SAP RETURNS

AUTHORIZATION

512 Printing








system





balancing






Primary instance

Backup instance








CUSTOMER


MS SOL

Server


Primary Server


Backup Server

POS SAP Store Data


POS SAP Store Data


Express Server

RegisterRegister

POS SAP Store Data


Express Server

RegisterRegister

Head Office

Store 1 Store N

SAP POSSAP POS

SAP SAP POS Store



R

R

R

R

R

R

R

R

R

R












provide failover



82

CUSTOMER











Note










in this guide



CUSTOMER




service



Note




84

CUSTOMER








Application failure

Hardware failure




















CUSTOMER






515 Troubleshooting



Note





customers



















certain instances



process





86

CUSTOMER





















Components


Backup and Restore

Examples

I Only software no

configuration or

application data

- No backup new


recovery or



upgrade


BDOC Modeler


configuration

information no

application data



- No backup new

installation and


recovery


SAP Gateway

Comm Station

SAP Business

Connector

SAP IPC (20C)

III Only replicated

application data

Replication time is


recovery

Data




files

SAP IMSSearch

Engine

SAP IPC (20B)

Webserver

SAP ITS

IV Only replicated


recommended as

Data


system backup or

SAP IMSSearch

Engine

Webserver



CUSTOMER



Components


Backup and Restore

Examples



by a DBMS




V Only replicated


recommended because



DBMS

Data

- Database and log

backup or




SAP IPC (20B)

Catalog Server




Data


system backup



Webserver





AS

Data

- Database and log

backup


- Configuration

- log files


standalone system


AS

Data

- Database and log



in file system)



Standalone SAP

SAP System



systems data not

managed by a DBMS

Data


system backup data


systems must be

considered







SAP NetWeaver AS

Data

- Database and log



be considered

SAP liveCache

SAP Mobile

Workbench

88

CUSTOMER





Components


Backup and Restore

Examples






NetWeaver AS

Data

- Database and log





systems must be

considered



SAP System

SAP CRM

SAP APO


Warehouse



CUSTOMER









Remote Support





Typical problems








90

CUSTOMER



Appendix

7 Appendix

71 Related Guides


wwwsapcomcontactsap





notice



vendors














other countries






Open Group










Netscape


















4

CUSTOMER



Table of Contents

Table of Contents















Table of Contents

CUSTOMER














6

CUSTOMER



Table of Contents











Getting Started

CUSTOMER


1 Getting Started

Caution



11 About this Guide







the application



Sale

Target Groups





Support Specialist


SAP POS Application





as TRANSNET

8

CUSTOMER



Getting Started

Business Scenario






business

Component




Caution


Important SAP Notes

SAP Note

Number

Title Comment


Monitoring



CUSTOMER




1 SAP POS










10

CUSTOMER




















2 SAP POS Base
























CUSTOMER






SAP Retail



Application Server










12

CUSTOMER








Store Manager

POS Client

Mobile POS Client


Database Tools


31 Analysis Tools




Application)


the Windows Start

menu




there is an error

Manager code 6 Runs

communication

diagnostics at the

register

Manager code 900

Runs peripheral

diagnostics

Manager code 999

Shows the current

version and build







problems


service when the PC

starts up

Can run a console

from the desktop to

monitor the server


console there is a

connection box that

shows the number of

registers currently

connected







the server



CUSTOMER



the Log window

(xpslog)

LSN REPORT and


console identify

technical problems


component

Started from the


the Windows Start

menu





Connected


are successful


have failed


command line

window






corrupted b-tree



the files














handlers





14

CUSTOMER






sequence number)







Note





log file name




Example







Where





Handler





logging



CUSTOMER


Where






323 Log File Format








XCPT

EVENT

SAPTXNOBJ

TXNCOMP

BROWSER




rarr posclientlog





state events

SAPTXNOBJ ndash SAP

Transaction Object

logging

TXNCOMP ndash SAP

Transaction Object



logging

Level-based logging


diagnostic (FINEST)

PRINTER

DRAWER

MICR

MSR

KEYBOARD

DISPLAY

LOCK




rarr OPOSlog

POS OPOS device



device


level

16

CUSTOMER





SCALE

SCANNER

FISCAL_PTR

PROMO

SERVICES




rarr UElog




and SERVICES for

Services User Exit

logging

EFT_UE

EFT_IMP

PINPAD_UE

PINPAD_IMP




rarr EFTlog


POS generated log



generated log lines

under _IMP


level



Point of Sale rarr

rdatararr alleglog


Message Logging use


the following entry

HKEY_LOCAL_MACHINE

|SOFTWARE|SAPrarr


of Sale

Create a new STRING

key called

AllegianceLogWindow





accessible on the

register and shows


and from SAP POS

STORE DATA

TRANSFER FOR RETAIL

Restart the POS





contains these

messages This file

wraps like other


message text is not


and from SAP POS

STORE DATA

TRANSFER FOR RETAIL



CUSTOMER



truncated


copied to the

cXpress

Serveruploadkeep0

logs directory


g





Application


TWSecurity module



XpsLogini file


XCPT

EVENT

APPLY

XPS

APPLICATION

TRICKLE

COMMUNICATION

TLOG_UPLOADER




rarr xpslog





state events








files are logged


diagnostic logging


messaging related

diagnostic logging


from POS to Xpress

Server diagnostic

logging

COMMUNICATION ndash


SAP POS appear here

18

CUSTOMER





POSXPS Server

communication

diagnostic logging







rarr crsrvlog



and some SAP POS

STORE DATA

TRANSFER FOR RETAIL

messages for debug

purposes

This file contains



card authorizations


STORE DATA

TRANSFER FOR RETAIL


are reported here




rarr sqllog




Xpress Server rarr

sdata rarr

ApplyBPMLog

A corresponding

trigger file

ApplyBPMTrg is

created after the

Apply process

finishes writing to

the log file









files

A POSINI option

BPMAPPLYLOGFOLDER


folder where the

ApplyBPMlog file is

created No file is


does not exist

Success and failure

statuses are logged



date and time stamp



(DONE or FAIL)

duration number of



failure



operation code






the failure



Xpress Server rarr


problems detected

during the EOD

Success and failure

statuses are logged




CUSTOMER



sdata rarr

EodBPMLog

(A corresponding

trigger file

EodBPMTrg is

created after the


writing to the log

file)

procedure

A POSINI option

BPMEODLOGFOLDER


folder where the

EodBPMLog file is

created No file is


does not exist


date and time stamp


(STARTED

COMPLETED or

FAILED) duration of

EOD process (in

seconds)


TLog



Xpress Server rarr

sdata rarr

CLOGYYYYMMDDT

XT



messages to SAP POS

STORE DATA

TRANSFER FOR RETAIL





Messages checkbox


messages to SAP POS

STORE DATA

TRANSFER FOR RETAIL


Transnet



Xpress Server rarr

sdata



Responses from SAP

POS STORE DATA

TRANSFER FOR RETAIL

Sltgtltsssssgtxml -


SAP POS STORE DATA

TRANSFER FOR RETAIL


ltsssssgt = credit

sequence number

Credit Messages

tofrom SAP POS

STORE DATA

TRANSFER FOR RETAIL

Note

Not all

messages are

logged





Xpress Server rarr

sdata rarr

CRltgtxml and

rdataCCltgtxml

(Xpress Server PC)




(Register PC)


XML from SAP

RETURNS

AUTHORIZATION

CCltgtxml - XML


SAP RETURNS

AUTHORIZATION

ltgt = the register

number

SAP RETURNS

AUTHORIZATION


SAP POS STORE DATA

TRANSFER FOR RETAIL



the directory


Application


TWSecurity module

20

CUSTOMER







Store Manager rarr

bkofferr

Any Store Manager


logged here


to the cXpress

Serveruploadkeep0

logs directory as

SSSSRRBKOFFERR


Store Manager


the Xpress Server






How AppSight Works

















CUSTOMER




required




















SystemsAppSight





Recommendation










22

CUSTOMER








bkoffexe

journalexe

poswexe

xpsexe

POSGeneric


ion


nrpr

bkoffexe

journalexe

xpsctrlexe



Configurator

POSStoreStore

Configuratorrpr

poscfgwexe

POSStoreStore

Configurator


r

transnetexe

xpsexe

POSStoreOperations


algexe

poswexe

TrvLPointsexe

POSTerminal





where






Recommendation





CUSTOMER



the service







where















again manually




Note


24

CUSTOMER
























Syntax




collection















CUSTOMER



XPRESS SERVER=1

BACKUP SERVER=0

R=0





of the SMD agent









of the SMD agent









R1=0 Register 1

R2=0 Register 2



26

CUSTOMER




Xpress Server




INTROSCOPE LEVEL 10


POS - Register



running

Log Files



Example




















Note




BACKUP SERVER=0 off




CUSTOMER






















subdirectories





Formats)


28

CUSTOMER









SDK Reference










Log Files





Credit Log



crsrvlog


crsrvlog



and Event logs



and eventlog







Xcptlog

Eventlog


Store Configurator






CUSTOMER






Store Applications


database can either

be Sybase or

Microsoft SQL

Standard database

processes apply

The back office

database must be

running for Xpress

Server or POS Store

Manager

applications to

work

Standard database

POS ServerXpress

Server

2 Xpress Server is

normally configured

as a Windows

service and can be

started or stopped

automatically or


tools for Windows

The Xpress Server


be stopped by using

the Xpress Server

Console application

as well as

subsequently be

restarted This

console application

for the Xpress

Server can be run

from the desktop or

from the Windows

start menu Closing

the console


stop the POS Server

from running








Guide



does not have to be

30

CUSTOMER






started at any time

The register uses


provide information

The POS cannot

receive information

from the Xpress

Server unless the

Xpress Server is

running POS can be

started using the

desktop icon or by

using the Start

menu It can be

stopped by running

manager code 499

(Exit POS)

POS ManagerStore

Manager Application

3 The POS Store

Manager application

run after the back

office database and

Xpress Server

applications are

running

This application

does not run if the

database is not

running Several



not running If the

POS Server is

stopped while this


running this

application can be

reconnected using

the Main Menu rarr

Server State rarr

Attach function

otherwise this


be stopped and

restarted








CUSTOMER





Configurator

database must be

installed

Start this


desktop icon or

from the Start

menu





Store Configurator


Database

1 The database runs

as part of a

database server It

starts and stops

from a service



Application

2 This application

starts from the

desktop icon of the

Start menu The

journaldb

database must be


started







Files















32

CUSTOMER





Application Data

Restore


(txn)

Journals (jrn)

Daily totals data


Parameter files

Back up database


the day process

Back up Xpress

Server directories

sdata rdata and

parm

Keep all current

parameter downloads

available

Make available all

parameter file

updates done during

the day

SAP recommends


to ensure continued


the POS Server

machine has a hard

drive failure

Alternatively the

LOCAL PLU feature

can be used instead

of a backup server

With the LOCAL PLU



each register


drive failure



Server image


Copy saved sdata

rdata and parm

directories

Restore previous


database



previous backup





data for the day


database

Back up database or

keep a copy of the

database when

configuration

changes







Transaction files

(txn)

Journals (jrn)

Back up database

Back up all


journal files






of the journal and

transaction files






CUSTOMER



Application Data

Restore

containing the POS











the same register

number run manager

code 420 (import


and jrn from POS



After setup this





364 Periodic Tasks












EODPROCBAT


RETAIL)

34

CUSTOMER





up













365 Load Balancing

















CUSTOMER






















blocked

Severe



blocked

Moderate to low








Low









system crash

36

CUSTOMER





















the POS registers














CUSTOMER












Store Configurator


POS Server


POS










39 Troubleshooting






38

CUSTOMER




Peripheral Failures















CUSTOMER





text

Tware GMXP5

TWare Enterprise

texttextXML

Socket

JMS

Connection

Java

Client

Connection

JMS

Connection

Message

ManagerXML

ISO

JMS

Connection

ISO SocketIP-

Based

IP-BasedIP-

Based

IP-

Based

Message Handler

TPS NTM

Java Client

text text

APM

APM

JMS

Connection

TPS server

connection

Message

Manager

APM

TPS NTM

Server

JMS Server

OR

OR


(Store level)





North America

Problem



161916 CST]




40

CUSTOMER




Problem










CST]


needed for handler



CST]




CST]







Note



change any values




rverjvmdll




Djavaclasspath=libt


li



CUSTOMER





on




Filestransnetbin




memory

Note










delivery


meter table






42

CUSTOMER













































CUSTOMER














Example




requesttime








Note





44

CUSTOMER







Store POS

1 2

SAP POS STORE

DATA TRANSFER

FOR RETAIL

4 3





Example


----- Total TXNs ------



130000000





130000000





130000000





130000000






CUSTOMER



130000000

Note



Example






130000000






130000000






130000000

Note








46

CUSTOMER









Directory




Note














Syntax



LRootNodeNamegt







Where



set up



CUSTOMER



server


XML AUTO clause








Note




Directory




6 Choose Save






Where







48

CUSTOMER




Note














_8240xxwily



_9150xxWily





or


















CUSTOMER




o cayyztnsbpos23



















details below

Note





ofile


Example

Java VM parameters











50

CUSTOMER















Note


work

Note



CA Introscope agent















instrumentation









CUSTOMER




usrsapccmswily













o cayyzssbpos23



















Note





file


52

CUSTOMER




Example

Java VM parameters
























precisely

Note


work

Note



CA Introscope agent






CUSTOMER










Marketplace

44 Management


Store Server

HOStore Server

POS

SAP POS Store Data

Transfer for Retail

SA

P P

OS

Sto

re D

ata

Tra

nsfe

r fo

r R

eta

il

(Co

re)

NT

M C

lien

t A

PI (J

ava

)

NTM

Server

NT

M S

erv

er

AP

I (J

NI)

SAP POS Store Data

Transfer for Retail

SA

P P

OS

Sto

re D

ata

Tra

nsfe

r fo

r R

eta

il

(Co

re) Service

Provider

DB


RRRR

TCPIPTCPIP

Windows

Named Pipes







schedules

54

CUSTOMER








Note





Note



than a module






ltThreadPool


Debug=false






Note






CUSTOMER






Diagnostic Logging

Verbose Output

















Note


447 Page File







56

CUSTOMER






2 Choose Properties



5 Choose Change





Note










Note


Note










CUSTOMER














8GB RAM 3GB PAE

16GB RAM 3GB PAE

16GB + RAM PAE







Syntax


RECONFIGURE

GO


RECONFIGURE

GO

Caution




Memory option

Syntax


RECONFIGURE

GO

58

CUSTOMER




449 Logging to DB





ltConnectionPool

Debug=false







ltDatabasegt






















CUSTOMER


Note





Backup








Restore








4412 Periodic Tasks








44131 Logging On




60

CUSTOMER









Note


case sensitive


Note


case sensitive

Caution





4 Choose Login






Note










CUSTOMER


In-store POS System

R

Xpress Server


TPS Client

In-store POS System

R

Xpress Server


TPS Client

In-store POS System

R

Xpress Server


TPS Client

SAP POS Store Data



Load Balancer


for Retail Server

SAP POS Store Data



Load Balancer


for Retail Server

MS SQL Server

Database

R

R

R

R

R

R

R

R

R















repository






62

CUSTOMER










Assign user names






4415 Printing

















at the registers






CUSTOMER


64

CUSTOMER












47 Troubleshooting


Guide

471 Works Cited









4-4f5d-4545-a9b5-53ebd86d7591mspx




CUSTOMER











SAP POS Store Data


Register

Register

Express Server

JEE Engine

WebSphere

Head Office



Transfer for Retail

SAP POS



SAP POS Store Data


CDL

DBSQL

ServerWeb Client

R

R

R

R

R

R



66

CUSTOMER








SAP POS








WebSphere

SystemErrlog

ltWebSphere

Homegtprofilesltpro

filenamegtlogsltSer

ver

NamegtSystemErrlog


log



WebSphere

SystemOutlog

ltWebSphere

Homegtprofilesltpro

filenamegtlogsltSer

ver

NamegtSystemOutlog

WebSphere System

Output Log

WebSphere Log


rootgtExpressReturn

sCorelogsengine

logxx

SAP RETURNS


log



engine and trickle


rootgtExpressReturn

sCorelogsloadLog

logxx

Or

SAP RETURNS

AUTHORIZATION batch

data loading log



batch data loading



CUSTOMER



ltCDL install

rootgtlogsloadLog

log


Content File



Enginelogxx




Enginelogxx





core2-5xml

Enginelogxx






Enginelogxx




Loadloglogxx




performance

Loadloglogxx





Loadloglogxx





Loadloglogxx




Loadloglogxx

68

CUSTOMER




Content File






Loadloglogxx





Loadloglogxx
















CUSTOMER















Tasks







Note




must be running







70

CUSTOMER









_8240xxwily



_9150xxWily





OR










values






Property Value
















CUSTOMER


Property Value
















Java VM options








eprofile









Example








72

CUSTOMER




Note


CA Introscope agent



hereprofile


4 Restart WebSphere






The Agent Name



Java Agent monitors











Note


work










CUSTOMER













Note


logic will not work

o Save the file

Note



CA Introscope agent








Marketplace





Marketplace

74

CUSTOMER












SAP applications














namegt



WebSphere server




namegt







AUTHORIZATION





CUSTOMER









support

3 Select Login









57 Classification


system




Application logs





76

CUSTOMER






Data


Backup of software

Configuration

Log files









rootgtstorage



Application Logs








logs







59 Periodic Tasks







CUSTOMER


Recommendation






pipelinebat























replication exists

Not applicable



bean (MDB) It is an





Not applicable

78

CUSTOMER















replication exists

511 User Management







CUSTOMER





Admin UI








administrator

To access this tool


the URL



oginjsp


Maintenance



to users




search and customer

maintenance







maintenance









replication exists



User



80

CUSTOMER








permissions


SAP RETURNS

AUTHORIZATION

512 Printing








system





balancing






Primary instance

Backup instance








CUSTOMER


MS SOL

Server


Primary Server


Backup Server

POS SAP Store Data


POS SAP Store Data


Express Server

RegisterRegister

POS SAP Store Data


Express Server

RegisterRegister

Head Office

Store 1 Store N

SAP POSSAP POS

SAP SAP POS Store



R

R

R

R

R

R

R

R

R

R












provide failover



82

CUSTOMER











Note










in this guide



CUSTOMER




service



Note




84

CUSTOMER








Application failure

Hardware failure




















CUSTOMER






515 Troubleshooting



Note





customers



















certain instances



process





86

CUSTOMER





















Components


Backup and Restore

Examples

I Only software no

configuration or

application data

- No backup new


recovery or



upgrade


BDOC Modeler


configuration

information no

application data



- No backup new

installation and


recovery


SAP Gateway

Comm Station

SAP Business

Connector

SAP IPC (20C)

III Only replicated

application data

Replication time is


recovery

Data




files

SAP IMSSearch

Engine

SAP IPC (20B)

Webserver

SAP ITS

IV Only replicated


recommended as

Data


system backup or

SAP IMSSearch

Engine

Webserver



CUSTOMER



Components


Backup and Restore

Examples



by a DBMS




V Only replicated


recommended because



DBMS

Data

- Database and log

backup or




SAP IPC (20B)

Catalog Server




Data


system backup



Webserver





AS

Data

- Database and log

backup


- Configuration

- log files


standalone system


AS

Data

- Database and log



in file system)



Standalone SAP

SAP System



systems data not

managed by a DBMS

Data


system backup data


systems must be

considered







SAP NetWeaver AS

Data

- Database and log



be considered

SAP liveCache

SAP Mobile

Workbench

88

CUSTOMER





Components


Backup and Restore

Examples






NetWeaver AS

Data

- Database and log





systems must be

considered



SAP System

SAP CRM

SAP APO


Warehouse



CUSTOMER









Remote Support





Typical problems








90

CUSTOMER



Appendix

7 Appendix

71 Related Guides


wwwsapcomcontactsap





notice



vendors














other countries






Open Group










Netscape



















Table of Contents

CUSTOMER














6

CUSTOMER



Table of Contents











Getting Started

CUSTOMER


1 Getting Started

Caution



11 About this Guide







the application



Sale

Target Groups





Support Specialist


SAP POS Application





as TRANSNET

8

CUSTOMER



Getting Started

Business Scenario






business

Component




Caution


Important SAP Notes

SAP Note

Number

Title Comment


Monitoring



CUSTOMER




1 SAP POS










10

CUSTOMER




















2 SAP POS Base
























CUSTOMER






SAP Retail



Application Server










12

CUSTOMER








Store Manager

POS Client

Mobile POS Client


Database Tools


31 Analysis Tools




Application)


the Windows Start

menu




there is an error

Manager code 6 Runs

communication

diagnostics at the

register

Manager code 900

Runs peripheral

diagnostics

Manager code 999

Shows the current

version and build







problems


service when the PC

starts up

Can run a console

from the desktop to

monitor the server


console there is a

connection box that

shows the number of

registers currently

connected







the server



CUSTOMER



the Log window

(xpslog)

LSN REPORT and


console identify

technical problems


component

Started from the


the Windows Start

menu





Connected


are successful


have failed


command line

window






corrupted b-tree



the files














handlers





14

CUSTOMER






sequence number)







Note





log file name




Example







Where





Handler





logging



CUSTOMER


Where






323 Log File Format








XCPT

EVENT

SAPTXNOBJ

TXNCOMP

BROWSER




rarr posclientlog





state events

SAPTXNOBJ ndash SAP

Transaction Object

logging

TXNCOMP ndash SAP

Transaction Object



logging

Level-based logging


diagnostic (FINEST)

PRINTER

DRAWER

MICR

MSR

KEYBOARD

DISPLAY

LOCK




rarr OPOSlog

POS OPOS device



device


level

16

CUSTOMER





SCALE

SCANNER

FISCAL_PTR

PROMO

SERVICES




rarr UElog




and SERVICES for

Services User Exit

logging

EFT_UE

EFT_IMP

PINPAD_UE

PINPAD_IMP




rarr EFTlog


POS generated log



generated log lines

under _IMP


level



Point of Sale rarr

rdatararr alleglog


Message Logging use


the following entry

HKEY_LOCAL_MACHINE

|SOFTWARE|SAPrarr


of Sale

Create a new STRING

key called

AllegianceLogWindow





accessible on the

register and shows


and from SAP POS

STORE DATA

TRANSFER FOR RETAIL

Restart the POS





contains these

messages This file

wraps like other


message text is not


and from SAP POS

STORE DATA

TRANSFER FOR RETAIL



CUSTOMER



truncated


copied to the

cXpress

Serveruploadkeep0

logs directory


g





Application


TWSecurity module



XpsLogini file


XCPT

EVENT

APPLY

XPS

APPLICATION

TRICKLE

COMMUNICATION

TLOG_UPLOADER




rarr xpslog





state events








files are logged


diagnostic logging


messaging related

diagnostic logging


from POS to Xpress

Server diagnostic

logging

COMMUNICATION ndash


SAP POS appear here

18

CUSTOMER





POSXPS Server

communication

diagnostic logging







rarr crsrvlog



and some SAP POS

STORE DATA

TRANSFER FOR RETAIL

messages for debug

purposes

This file contains



card authorizations


STORE DATA

TRANSFER FOR RETAIL


are reported here




rarr sqllog




Xpress Server rarr

sdata rarr

ApplyBPMLog

A corresponding

trigger file

ApplyBPMTrg is

created after the

Apply process

finishes writing to

the log file









files

A POSINI option

BPMAPPLYLOGFOLDER


folder where the

ApplyBPMlog file is

created No file is


does not exist

Success and failure

statuses are logged



date and time stamp



(DONE or FAIL)

duration number of



failure



operation code






the failure



Xpress Server rarr


problems detected

during the EOD

Success and failure

statuses are logged




CUSTOMER



sdata rarr

EodBPMLog

(A corresponding

trigger file

EodBPMTrg is

created after the


writing to the log

file)

procedure

A POSINI option

BPMEODLOGFOLDER


folder where the

EodBPMLog file is

created No file is


does not exist


date and time stamp


(STARTED

COMPLETED or

FAILED) duration of

EOD process (in

seconds)


TLog



Xpress Server rarr

sdata rarr

CLOGYYYYMMDDT

XT



messages to SAP POS

STORE DATA

TRANSFER FOR RETAIL





Messages checkbox


messages to SAP POS

STORE DATA

TRANSFER FOR RETAIL


Transnet



Xpress Server rarr

sdata



Responses from SAP

POS STORE DATA

TRANSFER FOR RETAIL

Sltgtltsssssgtxml -


SAP POS STORE DATA

TRANSFER FOR RETAIL


ltsssssgt = credit

sequence number

Credit Messages

tofrom SAP POS

STORE DATA

TRANSFER FOR RETAIL

Note

Not all

messages are

logged





Xpress Server rarr

sdata rarr

CRltgtxml and

rdataCCltgtxml

(Xpress Server PC)




(Register PC)


XML from SAP

RETURNS

AUTHORIZATION

CCltgtxml - XML


SAP RETURNS

AUTHORIZATION

ltgt = the register

number

SAP RETURNS

AUTHORIZATION


SAP POS STORE DATA

TRANSFER FOR RETAIL



the directory


Application


TWSecurity module

20

CUSTOMER







Store Manager rarr

bkofferr

Any Store Manager


logged here


to the cXpress

Serveruploadkeep0

logs directory as

SSSSRRBKOFFERR


Store Manager


the Xpress Server






How AppSight Works

















CUSTOMER




required




















SystemsAppSight





Recommendation










22

CUSTOMER








bkoffexe

journalexe

poswexe

xpsexe

POSGeneric


ion


nrpr

bkoffexe

journalexe

xpsctrlexe



Configurator

POSStoreStore

Configuratorrpr

poscfgwexe

POSStoreStore

Configurator


r

transnetexe

xpsexe

POSStoreOperations


algexe

poswexe

TrvLPointsexe

POSTerminal





where






Recommendation





CUSTOMER



the service







where















again manually




Note


24

CUSTOMER
























Syntax




collection















CUSTOMER



XPRESS SERVER=1

BACKUP SERVER=0

R=0





of the SMD agent









of the SMD agent









R1=0 Register 1

R2=0 Register 2



26

CUSTOMER




Xpress Server




INTROSCOPE LEVEL 10


POS - Register



running

Log Files



Example




















Note




BACKUP SERVER=0 off




CUSTOMER






















subdirectories





Formats)


28

CUSTOMER









SDK Reference










Log Files





Credit Log



crsrvlog


crsrvlog



and Event logs



and eventlog







Xcptlog

Eventlog


Store Configurator






CUSTOMER






Store Applications


database can either

be Sybase or

Microsoft SQL

Standard database

processes apply

The back office

database must be

running for Xpress

Server or POS Store

Manager

applications to

work

Standard database

POS ServerXpress

Server

2 Xpress Server is

normally configured

as a Windows

service and can be

started or stopped

automatically or


tools for Windows

The Xpress Server


be stopped by using

the Xpress Server

Console application

as well as

subsequently be

restarted This

console application

for the Xpress

Server can be run

from the desktop or

from the Windows

start menu Closing

the console


stop the POS Server

from running








Guide



does not have to be

30

CUSTOMER






started at any time

The register uses


provide information

The POS cannot

receive information

from the Xpress

Server unless the

Xpress Server is

running POS can be

started using the

desktop icon or by

using the Start

menu It can be

stopped by running

manager code 499

(Exit POS)

POS ManagerStore

Manager Application

3 The POS Store

Manager application

run after the back

office database and

Xpress Server

applications are

running

This application

does not run if the

database is not

running Several



not running If the

POS Server is

stopped while this


running this

application can be

reconnected using

the Main Menu rarr

Server State rarr

Attach function

otherwise this


be stopped and

restarted








CUSTOMER





Configurator

database must be

installed

Start this


desktop icon or

from the Start

menu





Store Configurator


Database

1 The database runs

as part of a

database server It

starts and stops

from a service



Application

2 This application

starts from the

desktop icon of the

Start menu The

journaldb

database must be


started







Files















32

CUSTOMER





Application Data

Restore


(txn)

Journals (jrn)

Daily totals data


Parameter files

Back up database


the day process

Back up Xpress

Server directories

sdata rdata and

parm

Keep all current

parameter downloads

available

Make available all

parameter file

updates done during

the day

SAP recommends


to ensure continued


the POS Server

machine has a hard

drive failure

Alternatively the

LOCAL PLU feature

can be used instead

of a backup server

With the LOCAL PLU



each register


drive failure



Server image


Copy saved sdata

rdata and parm

directories

Restore previous


database



previous backup





data for the day


database

Back up database or

keep a copy of the

database when

configuration

changes







Transaction files

(txn)

Journals (jrn)

Back up database

Back up all


journal files






of the journal and

transaction files






CUSTOMER



Application Data

Restore

containing the POS











the same register

number run manager

code 420 (import


and jrn from POS



After setup this





364 Periodic Tasks












EODPROCBAT


RETAIL)

34

CUSTOMER





up













365 Load Balancing

















CUSTOMER






















blocked

Severe



blocked

Moderate to low








Low









system crash

36

CUSTOMER





















the POS registers














CUSTOMER












Store Configurator


POS Server


POS










39 Troubleshooting






38

CUSTOMER




Peripheral Failures















CUSTOMER





text

Tware GMXP5

TWare Enterprise

texttextXML

Socket

JMS

Connection

Java

Client

Connection

JMS

Connection

Message

ManagerXML

ISO

JMS

Connection

ISO SocketIP-

Based

IP-BasedIP-

Based

IP-

Based

Message Handler

TPS NTM

Java Client

text text

APM

APM

JMS

Connection

TPS server

connection

Message

Manager

APM

TPS NTM

Server

JMS Server

OR

OR


(Store level)





North America

Problem



161916 CST]




40

CUSTOMER




Problem










CST]


needed for handler



CST]




CST]







Note



change any values




rverjvmdll




Djavaclasspath=libt


li



CUSTOMER





on




Filestransnetbin




memory

Note










delivery


meter table






42

CUSTOMER













































CUSTOMER














Example




requesttime








Note





44

CUSTOMER







Store POS

1 2

SAP POS STORE

DATA TRANSFER

FOR RETAIL

4 3





Example


----- Total TXNs ------



130000000





130000000





130000000





130000000






CUSTOMER



130000000

Note



Example






130000000






130000000






130000000

Note








46

CUSTOMER









Directory




Note














Syntax



LRootNodeNamegt







Where



set up



CUSTOMER



server


XML AUTO clause








Note




Directory




6 Choose Save






Where







48

CUSTOMER




Note














_8240xxwily



_9150xxWily





or


















CUSTOMER




o cayyztnsbpos23



















details below

Note





ofile


Example

Java VM parameters











50

CUSTOMER















Note


work

Note



CA Introscope agent















instrumentation









CUSTOMER




usrsapccmswily













o cayyzssbpos23



















Note





file


52

CUSTOMER




Example

Java VM parameters
























precisely

Note


work

Note



CA Introscope agent






CUSTOMER










Marketplace

44 Management


Store Server

HOStore Server

POS

SAP POS Store Data

Transfer for Retail

SA

P P

OS

Sto

re D

ata

Tra

nsfe

r fo

r R

eta

il

(Co

re)

NT

M C

lien

t A

PI (J

ava

)

NTM

Server

NT

M S

erv

er

AP

I (J

NI)

SAP POS Store Data

Transfer for Retail

SA

P P

OS

Sto

re D

ata

Tra

nsfe

r fo

r R

eta

il

(Co

re) Service

Provider

DB


RRRR

TCPIPTCPIP

Windows

Named Pipes







schedules

54

CUSTOMER








Note





Note



than a module






ltThreadPool


Debug=false






Note






CUSTOMER






Diagnostic Logging

Verbose Output

















Note


447 Page File







56

CUSTOMER






2 Choose Properties



5 Choose Change





Note










Note


Note










CUSTOMER














8GB RAM 3GB PAE

16GB RAM 3GB PAE

16GB + RAM PAE







Syntax


RECONFIGURE

GO


RECONFIGURE

GO

Caution




Memory option

Syntax


RECONFIGURE

GO

58

CUSTOMER




449 Logging to DB





ltConnectionPool

Debug=false







ltDatabasegt






















CUSTOMER


Note





Backup








Restore








4412 Periodic Tasks








44131 Logging On




60

CUSTOMER









Note


case sensitive


Note


case sensitive

Caution





4 Choose Login






Note










CUSTOMER


In-store POS System

R

Xpress Server


TPS Client

In-store POS System

R

Xpress Server


TPS Client

In-store POS System

R

Xpress Server


TPS Client

SAP POS Store Data



Load Balancer


for Retail Server

SAP POS Store Data



Load Balancer


for Retail Server

MS SQL Server

Database

R

R

R

R

R

R

R

R

R















repository






62

CUSTOMER










Assign user names






4415 Printing

















at the registers






CUSTOMER


64

CUSTOMER












47 Troubleshooting


Guide

471 Works Cited









4-4f5d-4545-a9b5-53ebd86d7591mspx




CUSTOMER











SAP POS Store Data


Register

Register

Express Server

JEE Engine

WebSphere

Head Office



Transfer for Retail

SAP POS



SAP POS Store Data


CDL

DBSQL

ServerWeb Client

R

R

R

R

R

R



66

CUSTOMER








SAP POS








WebSphere

SystemErrlog

ltWebSphere

Homegtprofilesltpro

filenamegtlogsltSer

ver

NamegtSystemErrlog


log



WebSphere

SystemOutlog

ltWebSphere

Homegtprofilesltpro

filenamegtlogsltSer

ver

NamegtSystemOutlog

WebSphere System

Output Log

WebSphere Log


rootgtExpressReturn

sCorelogsengine

logxx

SAP RETURNS


log



engine and trickle


rootgtExpressReturn

sCorelogsloadLog

logxx

Or

SAP RETURNS

AUTHORIZATION batch

data loading log



batch data loading



CUSTOMER



ltCDL install

rootgtlogsloadLog

log


Content File



Enginelogxx




Enginelogxx





core2-5xml

Enginelogxx






Enginelogxx




Loadloglogxx




performance

Loadloglogxx





Loadloglogxx





Loadloglogxx




Loadloglogxx

68

CUSTOMER




Content File






Loadloglogxx





Loadloglogxx
















CUSTOMER















Tasks







Note




must be running







70

CUSTOMER









_8240xxwily



_9150xxWily





OR










values






Property Value
















CUSTOMER


Property Value
















Java VM options








eprofile









Example








72

CUSTOMER




Note


CA Introscope agent



hereprofile


4 Restart WebSphere






The Agent Name



Java Agent monitors











Note


work










CUSTOMER













Note


logic will not work

o Save the file

Note



CA Introscope agent








Marketplace





Marketplace

74

CUSTOMER












SAP applications














namegt



WebSphere server




namegt







AUTHORIZATION





CUSTOMER









support

3 Select Login









57 Classification


system




Application logs





76

CUSTOMER






Data


Backup of software

Configuration

Log files









rootgtstorage



Application Logs








logs







59 Periodic Tasks







CUSTOMER


Recommendation






pipelinebat























replication exists

Not applicable



bean (MDB) It is an





Not applicable

78

CUSTOMER















replication exists

511 User Management







CUSTOMER





Admin UI








administrator

To access this tool


the URL



oginjsp


Maintenance



to users




search and customer

maintenance







maintenance









replication exists



User



80

CUSTOMER








permissions


SAP RETURNS

AUTHORIZATION

512 Printing








system





balancing






Primary instance

Backup instance








CUSTOMER


MS SOL

Server


Primary Server


Backup Server

POS SAP Store Data


POS SAP Store Data


Express Server

RegisterRegister

POS SAP Store Data


Express Server

RegisterRegister

Head Office

Store 1 Store N

SAP POSSAP POS

SAP SAP POS Store



R

R

R

R

R

R

R

R

R

R












provide failover



82

CUSTOMER











Note










in this guide



CUSTOMER




service



Note




84

CUSTOMER








Application failure

Hardware failure




















CUSTOMER






515 Troubleshooting



Note





customers



















certain instances



process





86

CUSTOMER





















Components


Backup and Restore

Examples

I Only software no

configuration or

application data

- No backup new


recovery or



upgrade


BDOC Modeler


configuration

information no

application data



- No backup new

installation and


recovery


SAP Gateway

Comm Station

SAP Business

Connector

SAP IPC (20C)

III Only replicated

application data

Replication time is


recovery

Data




files

SAP IMSSearch

Engine

SAP IPC (20B)

Webserver

SAP ITS

IV Only replicated


recommended as

Data


system backup or

SAP IMSSearch

Engine

Webserver



CUSTOMER



Components


Backup and Restore

Examples



by a DBMS




V Only replicated


recommended because



DBMS

Data

- Database and log

backup or




SAP IPC (20B)

Catalog Server




Data


system backup



Webserver





AS

Data

- Database and log

backup


- Configuration

- log files


standalone system


AS

Data

- Database and log



in file system)



Standalone SAP

SAP System



systems data not

managed by a DBMS

Data


system backup data


systems must be

considered







SAP NetWeaver AS

Data

- Database and log



be considered

SAP liveCache

SAP Mobile

Workbench

88

CUSTOMER





Components


Backup and Restore

Examples






NetWeaver AS

Data

- Database and log





systems must be

considered



SAP System

SAP CRM

SAP APO


Warehouse



CUSTOMER









Remote Support





Typical problems








90

CUSTOMER



Appendix

7 Appendix

71 Related Guides


wwwsapcomcontactsap





notice



vendors














other countries






Open Group










Netscape


















6

CUSTOMER



Table of Contents











Getting Started

CUSTOMER


1 Getting Started

Caution



11 About this Guide







the application



Sale

Target Groups





Support Specialist


SAP POS Application





as TRANSNET

8

CUSTOMER



Getting Started

Business Scenario






business

Component




Caution


Important SAP Notes

SAP Note

Number

Title Comment


Monitoring



CUSTOMER




1 SAP POS










10

CUSTOMER




















2 SAP POS Base
























CUSTOMER






SAP Retail



Application Server










12

CUSTOMER








Store Manager

POS Client

Mobile POS Client


Database Tools


31 Analysis Tools




Application)


the Windows Start

menu




there is an error

Manager code 6 Runs

communication

diagnostics at the

register

Manager code 900

Runs peripheral

diagnostics

Manager code 999

Shows the current

version and build







problems


service when the PC

starts up

Can run a console

from the desktop to

monitor the server


console there is a

connection box that

shows the number of

registers currently

connected







the server



CUSTOMER



the Log window

(xpslog)

LSN REPORT and


console identify

technical problems


component

Started from the


the Windows Start

menu





Connected


are successful


have failed


command line

window






corrupted b-tree



the files














handlers





14

CUSTOMER






sequence number)







Note





log file name




Example







Where





Handler





logging



CUSTOMER


Where






323 Log File Format








XCPT

EVENT

SAPTXNOBJ

TXNCOMP

BROWSER




rarr posclientlog





state events

SAPTXNOBJ ndash SAP

Transaction Object

logging

TXNCOMP ndash SAP

Transaction Object



logging

Level-based logging


diagnostic (FINEST)

PRINTER

DRAWER

MICR

MSR

KEYBOARD

DISPLAY

LOCK




rarr OPOSlog

POS OPOS device



device


level

16

CUSTOMER





SCALE

SCANNER

FISCAL_PTR

PROMO

SERVICES




rarr UElog




and SERVICES for

Services User Exit

logging

EFT_UE

EFT_IMP

PINPAD_UE

PINPAD_IMP




rarr EFTlog


POS generated log



generated log lines

under _IMP


level



Point of Sale rarr

rdatararr alleglog


Message Logging use


the following entry

HKEY_LOCAL_MACHINE

|SOFTWARE|SAPrarr


of Sale

Create a new STRING

key called

AllegianceLogWindow





accessible on the

register and shows


and from SAP POS

STORE DATA

TRANSFER FOR RETAIL

Restart the POS





contains these

messages This file

wraps like other


message text is not


and from SAP POS

STORE DATA

TRANSFER FOR RETAIL



CUSTOMER



truncated


copied to the

cXpress

Serveruploadkeep0

logs directory


g





Application


TWSecurity module



XpsLogini file


XCPT

EVENT

APPLY

XPS

APPLICATION

TRICKLE

COMMUNICATION

TLOG_UPLOADER




rarr xpslog





state events








files are logged


diagnostic logging


messaging related

diagnostic logging


from POS to Xpress

Server diagnostic

logging

COMMUNICATION ndash


SAP POS appear here

18

CUSTOMER





POSXPS Server

communication

diagnostic logging







rarr crsrvlog



and some SAP POS

STORE DATA

TRANSFER FOR RETAIL

messages for debug

purposes

This file contains



card authorizations


STORE DATA

TRANSFER FOR RETAIL


are reported here




rarr sqllog




Xpress Server rarr

sdata rarr

ApplyBPMLog

A corresponding

trigger file

ApplyBPMTrg is

created after the

Apply process

finishes writing to

the log file









files

A POSINI option

BPMAPPLYLOGFOLDER


folder where the

ApplyBPMlog file is

created No file is


does not exist

Success and failure

statuses are logged



date and time stamp



(DONE or FAIL)

duration number of



failure



operation code






the failure



Xpress Server rarr


problems detected

during the EOD

Success and failure

statuses are logged




CUSTOMER



sdata rarr

EodBPMLog

(A corresponding

trigger file

EodBPMTrg is

created after the


writing to the log

file)

procedure

A POSINI option

BPMEODLOGFOLDER


folder where the

EodBPMLog file is

created No file is


does not exist


date and time stamp


(STARTED

COMPLETED or

FAILED) duration of

EOD process (in

seconds)


TLog



Xpress Server rarr

sdata rarr

CLOGYYYYMMDDT

XT



messages to SAP POS

STORE DATA

TRANSFER FOR RETAIL





Messages checkbox


messages to SAP POS

STORE DATA

TRANSFER FOR RETAIL


Transnet



Xpress Server rarr

sdata



Responses from SAP

POS STORE DATA

TRANSFER FOR RETAIL

Sltgtltsssssgtxml -


SAP POS STORE DATA

TRANSFER FOR RETAIL


ltsssssgt = credit

sequence number

Credit Messages

tofrom SAP POS

STORE DATA

TRANSFER FOR RETAIL

Note

Not all

messages are

logged





Xpress Server rarr

sdata rarr

CRltgtxml and

rdataCCltgtxml

(Xpress Server PC)




(Register PC)


XML from SAP

RETURNS

AUTHORIZATION

CCltgtxml - XML


SAP RETURNS

AUTHORIZATION

ltgt = the register

number

SAP RETURNS

AUTHORIZATION


SAP POS STORE DATA

TRANSFER FOR RETAIL



the directory


Application


TWSecurity module

20

CUSTOMER







Store Manager rarr

bkofferr

Any Store Manager


logged here


to the cXpress

Serveruploadkeep0

logs directory as

SSSSRRBKOFFERR


Store Manager


the Xpress Server






How AppSight Works

















CUSTOMER




required




















SystemsAppSight





Recommendation










22

CUSTOMER








bkoffexe

journalexe

poswexe

xpsexe

POSGeneric


ion


nrpr

bkoffexe

journalexe

xpsctrlexe



Configurator

POSStoreStore

Configuratorrpr

poscfgwexe

POSStoreStore

Configurator


r

transnetexe

xpsexe

POSStoreOperations


algexe

poswexe

TrvLPointsexe

POSTerminal





where






Recommendation





CUSTOMER



the service







where















again manually




Note


24

CUSTOMER
























Syntax




collection















CUSTOMER



XPRESS SERVER=1

BACKUP SERVER=0

R=0





of the SMD agent









of the SMD agent









R1=0 Register 1

R2=0 Register 2



26

CUSTOMER




Xpress Server




INTROSCOPE LEVEL 10


POS - Register



running

Log Files



Example




















Note




BACKUP SERVER=0 off




CUSTOMER






















subdirectories





Formats)


28

CUSTOMER









SDK Reference










Log Files





Credit Log



crsrvlog


crsrvlog



and Event logs



and eventlog







Xcptlog

Eventlog


Store Configurator






CUSTOMER






Store Applications


database can either

be Sybase or

Microsoft SQL

Standard database

processes apply

The back office

database must be

running for Xpress

Server or POS Store

Manager

applications to

work

Standard database

POS ServerXpress

Server

2 Xpress Server is

normally configured

as a Windows

service and can be

started or stopped

automatically or


tools for Windows

The Xpress Server


be stopped by using

the Xpress Server

Console application

as well as

subsequently be

restarted This

console application

for the Xpress

Server can be run

from the desktop or

from the Windows

start menu Closing

the console


stop the POS Server

from running








Guide



does not have to be

30

CUSTOMER






started at any time

The register uses


provide information

The POS cannot

receive information

from the Xpress

Server unless the

Xpress Server is

running POS can be

started using the

desktop icon or by

using the Start

menu It can be

stopped by running

manager code 499

(Exit POS)

POS ManagerStore

Manager Application

3 The POS Store

Manager application

run after the back

office database and

Xpress Server

applications are

running

This application

does not run if the

database is not

running Several



not running If the

POS Server is

stopped while this


running this

application can be

reconnected using

the Main Menu rarr

Server State rarr

Attach function

otherwise this


be stopped and

restarted








CUSTOMER





Configurator

database must be

installed

Start this


desktop icon or

from the Start

menu





Store Configurator


Database

1 The database runs

as part of a

database server It

starts and stops

from a service



Application

2 This application

starts from the

desktop icon of the

Start menu The

journaldb

database must be


started







Files















32

CUSTOMER





Application Data

Restore


(txn)

Journals (jrn)

Daily totals data


Parameter files

Back up database


the day process

Back up Xpress

Server directories

sdata rdata and

parm

Keep all current

parameter downloads

available

Make available all

parameter file

updates done during

the day

SAP recommends


to ensure continued


the POS Server

machine has a hard

drive failure

Alternatively the

LOCAL PLU feature

can be used instead

of a backup server

With the LOCAL PLU



each register


drive failure



Server image


Copy saved sdata

rdata and parm

directories

Restore previous


database



previous backup





data for the day


database

Back up database or

keep a copy of the

database when

configuration

changes







Transaction files

(txn)

Journals (jrn)

Back up database

Back up all


journal files






of the journal and

transaction files






CUSTOMER



Application Data

Restore

containing the POS











the same register

number run manager

code 420 (import


and jrn from POS



After setup this





364 Periodic Tasks












EODPROCBAT


RETAIL)

34

CUSTOMER





up













365 Load Balancing

















CUSTOMER






















blocked

Severe



blocked

Moderate to low








Low









system crash

36

CUSTOMER





















the POS registers














CUSTOMER












Store Configurator


POS Server


POS










39 Troubleshooting






38

CUSTOMER




Peripheral Failures















CUSTOMER





text

Tware GMXP5

TWare Enterprise

texttextXML

Socket

JMS

Connection

Java

Client

Connection

JMS

Connection

Message

ManagerXML

ISO

JMS

Connection

ISO SocketIP-

Based

IP-BasedIP-

Based

IP-

Based

Message Handler

TPS NTM

Java Client

text text

APM

APM

JMS

Connection

TPS server

connection

Message

Manager

APM

TPS NTM

Server

JMS Server

OR

OR


(Store level)





North America

Problem



161916 CST]




40

CUSTOMER




Problem










CST]


needed for handler



CST]




CST]







Note



change any values




rverjvmdll




Djavaclasspath=libt


li



CUSTOMER





on




Filestransnetbin




memory

Note










delivery


meter table






42

CUSTOMER













































CUSTOMER














Example




requesttime








Note





44

CUSTOMER







Store POS

1 2

SAP POS STORE

DATA TRANSFER

FOR RETAIL

4 3





Example


----- Total TXNs ------



130000000





130000000





130000000





130000000






CUSTOMER



130000000

Note



Example






130000000






130000000






130000000

Note








46

CUSTOMER









Directory




Note














Syntax



LRootNodeNamegt







Where



set up



CUSTOMER



server


XML AUTO clause








Note




Directory




6 Choose Save






Where







48

CUSTOMER




Note














_8240xxwily



_9150xxWily





or


















CUSTOMER




o cayyztnsbpos23



















details below

Note





ofile


Example

Java VM parameters











50

CUSTOMER















Note


work

Note



CA Introscope agent















instrumentation









CUSTOMER




usrsapccmswily













o cayyzssbpos23



















Note





file


52

CUSTOMER




Example

Java VM parameters
























precisely

Note


work

Note



CA Introscope agent






CUSTOMER










Marketplace

44 Management


Store Server

HOStore Server

POS

SAP POS Store Data

Transfer for Retail

SA

P P

OS

Sto

re D

ata

Tra

nsfe

r fo

r R

eta

il

(Co

re)

NT

M C

lien

t A

PI (J

ava

)

NTM

Server

NT

M S

erv

er

AP

I (J

NI)

SAP POS Store Data

Transfer for Retail

SA

P P

OS

Sto

re D

ata

Tra

nsfe

r fo

r R

eta

il

(Co

re) Service

Provider

DB


RRRR

TCPIPTCPIP

Windows

Named Pipes







schedules

54

CUSTOMER








Note





Note



than a module






ltThreadPool


Debug=false






Note






CUSTOMER






Diagnostic Logging

Verbose Output

















Note


447 Page File







56

CUSTOMER






2 Choose Properties



5 Choose Change





Note










Note


Note










CUSTOMER














8GB RAM 3GB PAE

16GB RAM 3GB PAE

16GB + RAM PAE







Syntax


RECONFIGURE

GO


RECONFIGURE

GO

Caution




Memory option

Syntax


RECONFIGURE

GO

58

CUSTOMER




449 Logging to DB





ltConnectionPool

Debug=false







ltDatabasegt






















CUSTOMER


Note





Backup








Restore








4412 Periodic Tasks








44131 Logging On




60

CUSTOMER









Note


case sensitive


Note


case sensitive

Caution





4 Choose Login






Note










CUSTOMER


In-store POS System

R

Xpress Server


TPS Client

In-store POS System

R

Xpress Server


TPS Client

In-store POS System

R

Xpress Server


TPS Client

SAP POS Store Data



Load Balancer


for Retail Server

SAP POS Store Data



Load Balancer


for Retail Server

MS SQL Server

Database

R

R

R

R

R

R

R

R

R















repository






62

CUSTOMER










Assign user names






4415 Printing

















at the registers






CUSTOMER


64

CUSTOMER












47 Troubleshooting


Guide

471 Works Cited









4-4f5d-4545-a9b5-53ebd86d7591mspx




CUSTOMER











SAP POS Store Data


Register

Register

Express Server

JEE Engine

WebSphere

Head Office



Transfer for Retail

SAP POS



SAP POS Store Data


CDL

DBSQL

ServerWeb Client

R

R

R

R

R

R



66

CUSTOMER








SAP POS








WebSphere

SystemErrlog

ltWebSphere

Homegtprofilesltpro

filenamegtlogsltSer

ver

NamegtSystemErrlog


log



WebSphere

SystemOutlog

ltWebSphere

Homegtprofilesltpro

filenamegtlogsltSer

ver

NamegtSystemOutlog

WebSphere System

Output Log

WebSphere Log


rootgtExpressReturn

sCorelogsengine

logxx

SAP RETURNS


log



engine and trickle


rootgtExpressReturn

sCorelogsloadLog

logxx

Or

SAP RETURNS

AUTHORIZATION batch

data loading log



batch data loading



CUSTOMER



ltCDL install

rootgtlogsloadLog

log


Content File



Enginelogxx




Enginelogxx





core2-5xml

Enginelogxx






Enginelogxx




Loadloglogxx




performance

Loadloglogxx





Loadloglogxx





Loadloglogxx




Loadloglogxx

68

CUSTOMER




Content File






Loadloglogxx





Loadloglogxx
















CUSTOMER















Tasks







Note




must be running







70

CUSTOMER









_8240xxwily



_9150xxWily





OR










values






Property Value
















CUSTOMER


Property Value
















Java VM options








eprofile









Example








72

CUSTOMER




Note


CA Introscope agent



hereprofile


4 Restart WebSphere






The Agent Name



Java Agent monitors











Note


work










CUSTOMER













Note


logic will not work

o Save the file

Note



CA Introscope agent








Marketplace





Marketplace

74

CUSTOMER












SAP applications














namegt



WebSphere server




namegt







AUTHORIZATION





CUSTOMER









support

3 Select Login









57 Classification


system




Application logs





76

CUSTOMER






Data


Backup of software

Configuration

Log files









rootgtstorage



Application Logs








logs







59 Periodic Tasks







CUSTOMER


Recommendation






pipelinebat























replication exists

Not applicable



bean (MDB) It is an





Not applicable

78

CUSTOMER















replication exists

511 User Management







CUSTOMER





Admin UI








administrator

To access this tool


the URL



oginjsp


Maintenance



to users




search and customer

maintenance







maintenance









replication exists



User



80

CUSTOMER








permissions


SAP RETURNS

AUTHORIZATION

512 Printing








system





balancing






Primary instance

Backup instance








CUSTOMER


MS SOL

Server


Primary Server


Backup Server

POS SAP Store Data


POS SAP Store Data


Express Server

RegisterRegister

POS SAP Store Data


Express Server

RegisterRegister

Head Office

Store 1 Store N

SAP POSSAP POS

SAP SAP POS Store



R

R

R

R

R

R

R

R

R

R












provide failover



82

CUSTOMER











Note










in this guide



CUSTOMER




service



Note




84

CUSTOMER








Application failure

Hardware failure




















CUSTOMER






515 Troubleshooting



Note





customers



















certain instances



process





86

CUSTOMER





















Components


Backup and Restore

Examples

I Only software no

configuration or

application data

- No backup new


recovery or



upgrade


BDOC Modeler


configuration

information no

application data



- No backup new

installation and


recovery


SAP Gateway

Comm Station

SAP Business

Connector

SAP IPC (20C)

III Only replicated

application data

Replication time is


recovery

Data




files

SAP IMSSearch

Engine

SAP IPC (20B)

Webserver

SAP ITS

IV Only replicated


recommended as

Data


system backup or

SAP IMSSearch

Engine

Webserver



CUSTOMER



Components


Backup and Restore

Examples



by a DBMS




V Only replicated


recommended because



DBMS

Data

- Database and log

backup or




SAP IPC (20B)

Catalog Server




Data


system backup



Webserver





AS

Data

- Database and log

backup


- Configuration

- log files


standalone system


AS

Data

- Database and log



in file system)



Standalone SAP

SAP System



systems data not

managed by a DBMS

Data


system backup data


systems must be

considered







SAP NetWeaver AS

Data

- Database and log



be considered

SAP liveCache

SAP Mobile

Workbench

88

CUSTOMER





Components


Backup and Restore

Examples






NetWeaver AS

Data

- Database and log





systems must be

considered



SAP System

SAP CRM

SAP APO


Warehouse



CUSTOMER









Remote Support





Typical problems








90

CUSTOMER



Appendix

7 Appendix

71 Related Guides


wwwsapcomcontactsap





notice



vendors














other countries






Open Group










Netscape



















Getting Started

CUSTOMER


1 Getting Started

Caution



11 About this Guide







the application



Sale

Target Groups





Support Specialist


SAP POS Application





as TRANSNET

8

CUSTOMER



Getting Started

Business Scenario






business

Component




Caution


Important SAP Notes

SAP Note

Number

Title Comment


Monitoring



CUSTOMER




1 SAP POS










10

CUSTOMER




















2 SAP POS Base
























CUSTOMER






SAP Retail



Application Server










12

CUSTOMER








Store Manager

POS Client

Mobile POS Client


Database Tools


31 Analysis Tools




Application)


the Windows Start

menu




there is an error

Manager code 6 Runs

communication

diagnostics at the

register

Manager code 900

Runs peripheral

diagnostics

Manager code 999

Shows the current

version and build







problems


service when the PC

starts up

Can run a console

from the desktop to

monitor the server


console there is a

connection box that

shows the number of

registers currently

connected







the server



CUSTOMER



the Log window

(xpslog)

LSN REPORT and


console identify

technical problems


component

Started from the


the Windows Start

menu





Connected


are successful


have failed


command line

window






corrupted b-tree



the files














handlers





14

CUSTOMER






sequence number)







Note





log file name




Example







Where





Handler





logging



CUSTOMER


Where






323 Log File Format








XCPT

EVENT

SAPTXNOBJ

TXNCOMP

BROWSER




rarr posclientlog





state events

SAPTXNOBJ ndash SAP

Transaction Object

logging

TXNCOMP ndash SAP

Transaction Object



logging

Level-based logging


diagnostic (FINEST)

PRINTER

DRAWER

MICR

MSR

KEYBOARD

DISPLAY

LOCK




rarr OPOSlog

POS OPOS device



device


level

16

CUSTOMER





SCALE

SCANNER

FISCAL_PTR

PROMO

SERVICES




rarr UElog




and SERVICES for

Services User Exit

logging

EFT_UE

EFT_IMP

PINPAD_UE

PINPAD_IMP




rarr EFTlog


POS generated log



generated log lines

under _IMP


level



Point of Sale rarr

rdatararr alleglog


Message Logging use


the following entry

HKEY_LOCAL_MACHINE

|SOFTWARE|SAPrarr


of Sale

Create a new STRING

key called

AllegianceLogWindow





accessible on the

register and shows


and from SAP POS

STORE DATA

TRANSFER FOR RETAIL

Restart the POS





contains these

messages This file

wraps like other


message text is not


and from SAP POS

STORE DATA

TRANSFER FOR RETAIL



CUSTOMER



truncated


copied to the

cXpress

Serveruploadkeep0

logs directory


g





Application


TWSecurity module



XpsLogini file


XCPT

EVENT

APPLY

XPS

APPLICATION

TRICKLE

COMMUNICATION

TLOG_UPLOADER




rarr xpslog





state events








files are logged


diagnostic logging


messaging related

diagnostic logging


from POS to Xpress

Server diagnostic

logging

COMMUNICATION ndash


SAP POS appear here

18

CUSTOMER





POSXPS Server

communication

diagnostic logging







rarr crsrvlog



and some SAP POS

STORE DATA

TRANSFER FOR RETAIL

messages for debug

purposes

This file contains



card authorizations


STORE DATA

TRANSFER FOR RETAIL


are reported here




rarr sqllog




Xpress Server rarr

sdata rarr

ApplyBPMLog

A corresponding

trigger file

ApplyBPMTrg is

created after the

Apply process

finishes writing to

the log file









files

A POSINI option

BPMAPPLYLOGFOLDER


folder where the

ApplyBPMlog file is

created No file is


does not exist

Success and failure

statuses are logged



date and time stamp



(DONE or FAIL)

duration number of



failure



operation code






the failure



Xpress Server rarr


problems detected

during the EOD

Success and failure

statuses are logged




CUSTOMER



sdata rarr

EodBPMLog

(A corresponding

trigger file

EodBPMTrg is

created after the


writing to the log

file)

procedure

A POSINI option

BPMEODLOGFOLDER


folder where the

EodBPMLog file is

created No file is


does not exist


date and time stamp


(STARTED

COMPLETED or

FAILED) duration of

EOD process (in

seconds)


TLog



Xpress Server rarr

sdata rarr

CLOGYYYYMMDDT

XT



messages to SAP POS

STORE DATA

TRANSFER FOR RETAIL





Messages checkbox


messages to SAP POS

STORE DATA

TRANSFER FOR RETAIL


Transnet



Xpress Server rarr

sdata



Responses from SAP

POS STORE DATA

TRANSFER FOR RETAIL

Sltgtltsssssgtxml -


SAP POS STORE DATA

TRANSFER FOR RETAIL


ltsssssgt = credit

sequence number

Credit Messages

tofrom SAP POS

STORE DATA

TRANSFER FOR RETAIL

Note

Not all

messages are

logged





Xpress Server rarr

sdata rarr

CRltgtxml and

rdataCCltgtxml

(Xpress Server PC)




(Register PC)


XML from SAP

RETURNS

AUTHORIZATION

CCltgtxml - XML


SAP RETURNS

AUTHORIZATION

ltgt = the register

number

SAP RETURNS

AUTHORIZATION


SAP POS STORE DATA

TRANSFER FOR RETAIL



the directory


Application


TWSecurity module

20

CUSTOMER







Store Manager rarr

bkofferr

Any Store Manager


logged here


to the cXpress

Serveruploadkeep0

logs directory as

SSSSRRBKOFFERR


Store Manager


the Xpress Server






How AppSight Works

















CUSTOMER




required




















SystemsAppSight





Recommendation










22

CUSTOMER








bkoffexe

journalexe

poswexe

xpsexe

POSGeneric


ion


nrpr

bkoffexe

journalexe

xpsctrlexe



Configurator

POSStoreStore

Configuratorrpr

poscfgwexe

POSStoreStore

Configurator


r

transnetexe

xpsexe

POSStoreOperations


algexe

poswexe

TrvLPointsexe

POSTerminal





where






Recommendation





CUSTOMER



the service







where















again manually




Note


24

CUSTOMER
























Syntax




collection















CUSTOMER



XPRESS SERVER=1

BACKUP SERVER=0

R=0





of the SMD agent









of the SMD agent









R1=0 Register 1

R2=0 Register 2



26

CUSTOMER




Xpress Server




INTROSCOPE LEVEL 10


POS - Register



running

Log Files



Example




















Note




BACKUP SERVER=0 off




CUSTOMER






















subdirectories





Formats)


28

CUSTOMER









SDK Reference










Log Files





Credit Log



crsrvlog


crsrvlog



and Event logs



and eventlog







Xcptlog

Eventlog


Store Configurator






CUSTOMER






Store Applications


database can either

be Sybase or

Microsoft SQL

Standard database

processes apply

The back office

database must be

running for Xpress

Server or POS Store

Manager

applications to

work

Standard database

POS ServerXpress

Server

2 Xpress Server is

normally configured

as a Windows

service and can be

started or stopped

automatically or


tools for Windows

The Xpress Server


be stopped by using

the Xpress Server

Console application

as well as

subsequently be

restarted This

console application

for the Xpress

Server can be run

from the desktop or

from the Windows

start menu Closing

the console


stop the POS Server

from running








Guide



does not have to be

30

CUSTOMER






started at any time

The register uses


provide information

The POS cannot

receive information

from the Xpress

Server unless the

Xpress Server is

running POS can be

started using the

desktop icon or by

using the Start

menu It can be

stopped by running

manager code 499

(Exit POS)

POS ManagerStore

Manager Application

3 The POS Store

Manager application

run after the back

office database and

Xpress Server

applications are

running

This application

does not run if the

database is not

running Several



not running If the

POS Server is

stopped while this


running this

application can be

reconnected using

the Main Menu rarr

Server State rarr

Attach function

otherwise this


be stopped and

restarted








CUSTOMER





Configurator

database must be

installed

Start this


desktop icon or

from the Start

menu





Store Configurator


Database

1 The database runs

as part of a

database server It

starts and stops

from a service



Application

2 This application

starts from the

desktop icon of the

Start menu The

journaldb

database must be


started







Files















32

CUSTOMER





Application Data

Restore


(txn)

Journals (jrn)

Daily totals data


Parameter files

Back up database


the day process

Back up Xpress

Server directories

sdata rdata and

parm

Keep all current

parameter downloads

available

Make available all

parameter file

updates done during

the day

SAP recommends


to ensure continued


the POS Server

machine has a hard

drive failure

Alternatively the

LOCAL PLU feature

can be used instead

of a backup server

With the LOCAL PLU



each register


drive failure



Server image


Copy saved sdata

rdata and parm

directories

Restore previous


database



previous backup





data for the day


database

Back up database or

keep a copy of the

database when

configuration

changes







Transaction files

(txn)

Journals (jrn)

Back up database

Back up all


journal files






of the journal and

transaction files






CUSTOMER



Application Data

Restore

containing the POS











the same register

number run manager

code 420 (import


and jrn from POS



After setup this





364 Periodic Tasks












EODPROCBAT


RETAIL)

34

CUSTOMER





up













365 Load Balancing

















CUSTOMER






















blocked

Severe



blocked

Moderate to low








Low









system crash

36

CUSTOMER





















the POS registers














CUSTOMER












Store Configurator


POS Server


POS










39 Troubleshooting






38

CUSTOMER




Peripheral Failures















CUSTOMER





text

Tware GMXP5

TWare Enterprise

texttextXML

Socket

JMS

Connection

Java

Client

Connection

JMS

Connection

Message

ManagerXML

ISO

JMS

Connection

ISO SocketIP-

Based

IP-BasedIP-

Based

IP-

Based

Message Handler

TPS NTM

Java Client

text text

APM

APM

JMS

Connection

TPS server

connection

Message

Manager

APM

TPS NTM

Server

JMS Server

OR

OR


(Store level)





North America

Problem



161916 CST]




40

CUSTOMER




Problem










CST]


needed for handler



CST]




CST]







Note



change any values




rverjvmdll




Djavaclasspath=libt


li



CUSTOMER





on




Filestransnetbin




memory

Note










delivery


meter table






42

CUSTOMER













































CUSTOMER














Example




requesttime








Note





44

CUSTOMER







Store POS

1 2

SAP POS STORE

DATA TRANSFER

FOR RETAIL

4 3





Example


----- Total TXNs ------



130000000





130000000





130000000





130000000






CUSTOMER



130000000

Note



Example






130000000






130000000






130000000

Note








46

CUSTOMER









Directory




Note














Syntax



LRootNodeNamegt







Where



set up



CUSTOMER



server


XML AUTO clause








Note




Directory




6 Choose Save






Where







48

CUSTOMER




Note














_8240xxwily



_9150xxWily





or


















CUSTOMER




o cayyztnsbpos23



















details below

Note





ofile


Example

Java VM parameters











50

CUSTOMER















Note


work

Note



CA Introscope agent















instrumentation









CUSTOMER




usrsapccmswily













o cayyzssbpos23



















Note





file


52

CUSTOMER




Example

Java VM parameters
























precisely

Note


work

Note



CA Introscope agent






CUSTOMER










Marketplace

44 Management


Store Server

HOStore Server

POS

SAP POS Store Data

Transfer for Retail

SA

P P

OS

Sto

re D

ata

Tra

nsfe

r fo

r R

eta

il

(Co

re)

NT

M C

lien

t A

PI (J

ava

)

NTM

Server

NT

M S

erv

er

AP

I (J

NI)

SAP POS Store Data

Transfer for Retail

SA

P P

OS

Sto

re D

ata

Tra

nsfe

r fo

r R

eta

il

(Co

re) Service

Provider

DB


RRRR

TCPIPTCPIP

Windows

Named Pipes







schedules

54

CUSTOMER








Note





Note



than a module






ltThreadPool


Debug=false






Note






CUSTOMER






Diagnostic Logging

Verbose Output

















Note


447 Page File







56

CUSTOMER






2 Choose Properties



5 Choose Change





Note










Note


Note










CUSTOMER














8GB RAM 3GB PAE

16GB RAM 3GB PAE

16GB + RAM PAE







Syntax


RECONFIGURE

GO


RECONFIGURE

GO

Caution




Memory option

Syntax


RECONFIGURE

GO

58

CUSTOMER




449 Logging to DB





ltConnectionPool

Debug=false







ltDatabasegt






















CUSTOMER


Note





Backup








Restore








4412 Periodic Tasks








44131 Logging On




60

CUSTOMER









Note


case sensitive


Note


case sensitive

Caution





4 Choose Login






Note










CUSTOMER


In-store POS System

R

Xpress Server


TPS Client

In-store POS System

R

Xpress Server


TPS Client

In-store POS System

R

Xpress Server


TPS Client

SAP POS Store Data



Load Balancer


for Retail Server

SAP POS Store Data



Load Balancer


for Retail Server

MS SQL Server

Database

R

R

R

R

R

R

R

R

R















repository






62

CUSTOMER










Assign user names






4415 Printing

















at the registers






CUSTOMER


64

CUSTOMER












47 Troubleshooting


Guide

471 Works Cited









4-4f5d-4545-a9b5-53ebd86d7591mspx




CUSTOMER











SAP POS Store Data


Register

Register

Express Server

JEE Engine

WebSphere

Head Office



Transfer for Retail

SAP POS



SAP POS Store Data


CDL

DBSQL

ServerWeb Client

R

R

R

R

R

R



66

CUSTOMER








SAP POS








WebSphere

SystemErrlog

ltWebSphere

Homegtprofilesltpro

filenamegtlogsltSer

ver

NamegtSystemErrlog


log



WebSphere

SystemOutlog

ltWebSphere

Homegtprofilesltpro

filenamegtlogsltSer

ver

NamegtSystemOutlog

WebSphere System

Output Log

WebSphere Log


rootgtExpressReturn

sCorelogsengine

logxx

SAP RETURNS


log



engine and trickle


rootgtExpressReturn

sCorelogsloadLog

logxx

Or

SAP RETURNS

AUTHORIZATION batch

data loading log



batch data loading



CUSTOMER



ltCDL install

rootgtlogsloadLog

log


Content File



Enginelogxx




Enginelogxx





core2-5xml

Enginelogxx






Enginelogxx




Loadloglogxx




performance

Loadloglogxx





Loadloglogxx





Loadloglogxx




Loadloglogxx

68

CUSTOMER




Content File






Loadloglogxx





Loadloglogxx
















CUSTOMER















Tasks







Note




must be running







70

CUSTOMER









_8240xxwily



_9150xxWily





OR










values






Property Value
















CUSTOMER


Property Value
















Java VM options








eprofile









Example








72

CUSTOMER




Note


CA Introscope agent



hereprofile


4 Restart WebSphere






The Agent Name



Java Agent monitors











Note


work










CUSTOMER













Note


logic will not work

o Save the file

Note



CA Introscope agent








Marketplace





Marketplace

74

CUSTOMER












SAP applications














namegt



WebSphere server




namegt







AUTHORIZATION





CUSTOMER









support

3 Select Login









57 Classification


system




Application logs





76

CUSTOMER






Data


Backup of software

Configuration

Log files









rootgtstorage



Application Logs








logs







59 Periodic Tasks







CUSTOMER


Recommendation






pipelinebat























replication exists

Not applicable



bean (MDB) It is an





Not applicable

78

CUSTOMER















replication exists

511 User Management







CUSTOMER





Admin UI








administrator

To access this tool


the URL



oginjsp


Maintenance



to users




search and customer

maintenance







maintenance









replication exists



User



80

CUSTOMER








permissions


SAP RETURNS

AUTHORIZATION

512 Printing








system





balancing






Primary instance

Backup instance








CUSTOMER


MS SOL

Server


Primary Server


Backup Server

POS SAP Store Data


POS SAP Store Data


Express Server

RegisterRegister

POS SAP Store Data


Express Server

RegisterRegister

Head Office

Store 1 Store N

SAP POSSAP POS

SAP SAP POS Store



R

R

R

R

R

R

R

R

R

R












provide failover



82

CUSTOMER











Note










in this guide



CUSTOMER




service



Note




84

CUSTOMER








Application failure

Hardware failure




















CUSTOMER






515 Troubleshooting



Note





customers



















certain instances



process





86

CUSTOMER





















Components


Backup and Restore

Examples

I Only software no

configuration or

application data

- No backup new


recovery or



upgrade


BDOC Modeler


configuration

information no

application data



- No backup new

installation and


recovery


SAP Gateway

Comm Station

SAP Business

Connector

SAP IPC (20C)

III Only replicated

application data

Replication time is


recovery

Data




files

SAP IMSSearch

Engine

SAP IPC (20B)

Webserver

SAP ITS

IV Only replicated


recommended as

Data


system backup or

SAP IMSSearch

Engine

Webserver



CUSTOMER



Components


Backup and Restore

Examples



by a DBMS




V Only replicated


recommended because



DBMS

Data

- Database and log

backup or




SAP IPC (20B)

Catalog Server




Data


system backup



Webserver





AS

Data

- Database and log

backup


- Configuration

- log files


standalone system


AS

Data

- Database and log



in file system)



Standalone SAP

SAP System



systems data not

managed by a DBMS

Data


system backup data


systems must be

considered







SAP NetWeaver AS

Data

- Database and log



be considered

SAP liveCache

SAP Mobile

Workbench

88

CUSTOMER





Components


Backup and Restore

Examples






NetWeaver AS

Data

- Database and log





systems must be

considered



SAP System

SAP CRM

SAP APO


Warehouse



CUSTOMER









Remote Support





Typical problems








90

CUSTOMER



Appendix

7 Appendix

71 Related Guides


wwwsapcomcontactsap





notice



vendors














other countries






Open Group










Netscape


















8

CUSTOMER



Getting Started

Business Scenario






business

Component




Caution


Important SAP Notes

SAP Note

Number

Title Comment


Monitoring



CUSTOMER




1 SAP POS










10

CUSTOMER




















2 SAP POS Base
























CUSTOMER






SAP Retail



Application Server










12

CUSTOMER








Store Manager

POS Client

Mobile POS Client


Database Tools


31 Analysis Tools




Application)


the Windows Start

menu




there is an error

Manager code 6 Runs

communication

diagnostics at the

register

Manager code 900

Runs peripheral

diagnostics

Manager code 999

Shows the current

version and build







problems


service when the PC

starts up

Can run a console

from the desktop to

monitor the server


console there is a

connection box that

shows the number of

registers currently

connected







the server



CUSTOMER



the Log window

(xpslog)

LSN REPORT and


console identify

technical problems


component

Started from the


the Windows Start

menu





Connected


are successful


have failed


command line

window






corrupted b-tree



the files














handlers





14

CUSTOMER






sequence number)







Note





log file name




Example







Where





Handler





logging



CUSTOMER


Where






323 Log File Format








XCPT

EVENT

SAPTXNOBJ

TXNCOMP

BROWSER




rarr posclientlog





state events

SAPTXNOBJ ndash SAP

Transaction Object

logging

TXNCOMP ndash SAP

Transaction Object



logging

Level-based logging


diagnostic (FINEST)

PRINTER

DRAWER

MICR

MSR

KEYBOARD

DISPLAY

LOCK




rarr OPOSlog

POS OPOS device



device


level

16

CUSTOMER





SCALE

SCANNER

FISCAL_PTR

PROMO

SERVICES




rarr UElog




and SERVICES for

Services User Exit

logging

EFT_UE

EFT_IMP

PINPAD_UE

PINPAD_IMP




rarr EFTlog


POS generated log



generated log lines

under _IMP


level



Point of Sale rarr

rdatararr alleglog


Message Logging use


the following entry

HKEY_LOCAL_MACHINE

|SOFTWARE|SAPrarr


of Sale

Create a new STRING

key called

AllegianceLogWindow





accessible on the

register and shows


and from SAP POS

STORE DATA

TRANSFER FOR RETAIL

Restart the POS





contains these

messages This file

wraps like other


message text is not


and from SAP POS

STORE DATA

TRANSFER FOR RETAIL



CUSTOMER



truncated


copied to the

cXpress

Serveruploadkeep0

logs directory


g





Application


TWSecurity module



XpsLogini file


XCPT

EVENT

APPLY

XPS

APPLICATION

TRICKLE

COMMUNICATION

TLOG_UPLOADER




rarr xpslog





state events








files are logged


diagnostic logging


messaging related

diagnostic logging


from POS to Xpress

Server diagnostic

logging

COMMUNICATION ndash


SAP POS appear here

18

CUSTOMER





POSXPS Server

communication

diagnostic logging







rarr crsrvlog



and some SAP POS

STORE DATA

TRANSFER FOR RETAIL

messages for debug

purposes

This file contains



card authorizations


STORE DATA

TRANSFER FOR RETAIL


are reported here




rarr sqllog




Xpress Server rarr

sdata rarr

ApplyBPMLog

A corresponding

trigger file

ApplyBPMTrg is

created after the

Apply process

finishes writing to

the log file









files

A POSINI option

BPMAPPLYLOGFOLDER


folder where the

ApplyBPMlog file is

created No file is


does not exist

Success and failure

statuses are logged



date and time stamp



(DONE or FAIL)

duration number of



failure



operation code






the failure



Xpress Server rarr


problems detected

during the EOD

Success and failure

statuses are logged




CUSTOMER



sdata rarr

EodBPMLog

(A corresponding

trigger file

EodBPMTrg is

created after the


writing to the log

file)

procedure

A POSINI option

BPMEODLOGFOLDER


folder where the

EodBPMLog file is

created No file is


does not exist


date and time stamp


(STARTED

COMPLETED or

FAILED) duration of

EOD process (in

seconds)


TLog



Xpress Server rarr

sdata rarr

CLOGYYYYMMDDT

XT



messages to SAP POS

STORE DATA

TRANSFER FOR RETAIL





Messages checkbox


messages to SAP POS

STORE DATA

TRANSFER FOR RETAIL


Transnet



Xpress Server rarr

sdata



Responses from SAP

POS STORE DATA

TRANSFER FOR RETAIL

Sltgtltsssssgtxml -


SAP POS STORE DATA

TRANSFER FOR RETAIL


ltsssssgt = credit

sequence number

Credit Messages

tofrom SAP POS

STORE DATA

TRANSFER FOR RETAIL

Note

Not all

messages are

logged





Xpress Server rarr

sdata rarr

CRltgtxml and

rdataCCltgtxml

(Xpress Server PC)




(Register PC)


XML from SAP

RETURNS

AUTHORIZATION

CCltgtxml - XML


SAP RETURNS

AUTHORIZATION

ltgt = the register

number

SAP RETURNS

AUTHORIZATION


SAP POS STORE DATA

TRANSFER FOR RETAIL



the directory


Application


TWSecurity module

20

CUSTOMER







Store Manager rarr

bkofferr

Any Store Manager


logged here


to the cXpress

Serveruploadkeep0

logs directory as

SSSSRRBKOFFERR


Store Manager


the Xpress Server






How AppSight Works

















CUSTOMER




required




















SystemsAppSight





Recommendation










22

CUSTOMER








bkoffexe

journalexe

poswexe

xpsexe

POSGeneric


ion


nrpr

bkoffexe

journalexe

xpsctrlexe



Configurator

POSStoreStore

Configuratorrpr

poscfgwexe

POSStoreStore

Configurator


r

transnetexe

xpsexe

POSStoreOperations


algexe

poswexe

TrvLPointsexe

POSTerminal





where






Recommendation





CUSTOMER



the service







where















again manually




Note


24

CUSTOMER
























Syntax




collection















CUSTOMER



XPRESS SERVER=1

BACKUP SERVER=0

R=0





of the SMD agent









of the SMD agent









R1=0 Register 1

R2=0 Register 2



26

CUSTOMER




Xpress Server




INTROSCOPE LEVEL 10


POS - Register



running

Log Files



Example




















Note




BACKUP SERVER=0 off




CUSTOMER






















subdirectories





Formats)


28

CUSTOMER









SDK Reference










Log Files





Credit Log



crsrvlog


crsrvlog



and Event logs



and eventlog







Xcptlog

Eventlog


Store Configurator






CUSTOMER






Store Applications


database can either

be Sybase or

Microsoft SQL

Standard database

processes apply

The back office

database must be

running for Xpress

Server or POS Store

Manager

applications to

work

Standard database

POS ServerXpress

Server

2 Xpress Server is

normally configured

as a Windows

service and can be

started or stopped

automatically or


tools for Windows

The Xpress Server


be stopped by using

the Xpress Server

Console application

as well as

subsequently be

restarted This

console application

for the Xpress

Server can be run

from the desktop or

from the Windows

start menu Closing

the console


stop the POS Server

from running








Guide



does not have to be

30

CUSTOMER






started at any time

The register uses


provide information

The POS cannot

receive information

from the Xpress

Server unless the

Xpress Server is

running POS can be

started using the

desktop icon or by

using the Start

menu It can be

stopped by running

manager code 499

(Exit POS)

POS ManagerStore

Manager Application

3 The POS Store

Manager application

run after the back

office database and

Xpress Server

applications are

running

This application

does not run if the

database is not

running Several



not running If the

POS Server is

stopped while this


running this

application can be

reconnected using

the Main Menu rarr

Server State rarr

Attach function

otherwise this


be stopped and

restarted








CUSTOMER





Configurator

database must be

installed

Start this


desktop icon or

from the Start

menu





Store Configurator


Database

1 The database runs

as part of a

database server It

starts and stops

from a service



Application

2 This application

starts from the

desktop icon of the

Start menu The

journaldb

database must be


started







Files















32

CUSTOMER





Application Data

Restore


(txn)

Journals (jrn)

Daily totals data


Parameter files

Back up database


the day process

Back up Xpress

Server directories

sdata rdata and

parm

Keep all current

parameter downloads

available

Make available all

parameter file

updates done during

the day

SAP recommends


to ensure continued


the POS Server

machine has a hard

drive failure

Alternatively the

LOCAL PLU feature

can be used instead

of a backup server

With the LOCAL PLU



each register


drive failure



Server image


Copy saved sdata

rdata and parm

directories

Restore previous


database



previous backup





data for the day


database

Back up database or

keep a copy of the

database when

configuration

changes







Transaction files

(txn)

Journals (jrn)

Back up database

Back up all


journal files






of the journal and

transaction files






CUSTOMER



Application Data

Restore

containing the POS











the same register

number run manager

code 420 (import


and jrn from POS



After setup this





364 Periodic Tasks












EODPROCBAT


RETAIL)

34

CUSTOMER





up













365 Load Balancing

















CUSTOMER






















blocked

Severe



blocked

Moderate to low








Low









system crash

36

CUSTOMER





















the POS registers














CUSTOMER












Store Configurator


POS Server


POS










39 Troubleshooting






38

CUSTOMER




Peripheral Failures















CUSTOMER





text

Tware GMXP5

TWare Enterprise

texttextXML

Socket

JMS

Connection

Java

Client

Connection

JMS

Connection

Message

ManagerXML

ISO

JMS

Connection

ISO SocketIP-

Based

IP-BasedIP-

Based

IP-

Based

Message Handler

TPS NTM

Java Client

text text

APM

APM

JMS

Connection

TPS server

connection

Message

Manager

APM

TPS NTM

Server

JMS Server

OR

OR


(Store level)





North America

Problem



161916 CST]




40

CUSTOMER




Problem










CST]


needed for handler



CST]




CST]







Note



change any values




rverjvmdll




Djavaclasspath=libt


li



CUSTOMER





on




Filestransnetbin




memory

Note










delivery


meter table






42

CUSTOMER













































CUSTOMER














Example




requesttime








Note





44

CUSTOMER







Store POS

1 2

SAP POS STORE

DATA TRANSFER

FOR RETAIL

4 3





Example


----- Total TXNs ------



130000000





130000000





130000000





130000000






CUSTOMER



130000000

Note



Example






130000000






130000000






130000000

Note








46

CUSTOMER









Directory




Note














Syntax



LRootNodeNamegt







Where



set up



CUSTOMER



server


XML AUTO clause








Note




Directory




6 Choose Save






Where







48

CUSTOMER




Note














_8240xxwily



_9150xxWily





or


















CUSTOMER




o cayyztnsbpos23



















details below

Note





ofile


Example

Java VM parameters











50

CUSTOMER















Note


work

Note



CA Introscope agent















instrumentation









CUSTOMER




usrsapccmswily













o cayyzssbpos23



















Note





file


52

CUSTOMER




Example

Java VM parameters
























precisely

Note


work

Note



CA Introscope agent






CUSTOMER










Marketplace

44 Management


Store Server

HOStore Server

POS

SAP POS Store Data

Transfer for Retail

SA

P P

OS

Sto

re D

ata

Tra

nsfe

r fo

r R

eta

il

(Co

re)

NT

M C

lien

t A

PI (J

ava

)

NTM

Server

NT

M S

erv

er

AP

I (J

NI)

SAP POS Store Data

Transfer for Retail

SA

P P

OS

Sto

re D

ata

Tra

nsfe

r fo

r R

eta

il

(Co

re) Service

Provider

DB


RRRR

TCPIPTCPIP

Windows

Named Pipes







schedules

54

CUSTOMER








Note





Note



than a module






ltThreadPool


Debug=false






Note






CUSTOMER






Diagnostic Logging

Verbose Output

















Note


447 Page File







56

CUSTOMER






2 Choose Properties



5 Choose Change





Note










Note


Note










CUSTOMER














8GB RAM 3GB PAE

16GB RAM 3GB PAE

16GB + RAM PAE







Syntax


RECONFIGURE

GO


RECONFIGURE

GO

Caution




Memory option

Syntax


RECONFIGURE

GO

58

CUSTOMER




449 Logging to DB





ltConnectionPool

Debug=false







ltDatabasegt






















CUSTOMER


Note





Backup








Restore








4412 Periodic Tasks








44131 Logging On




60

CUSTOMER









Note


case sensitive


Note


case sensitive

Caution





4 Choose Login






Note










CUSTOMER


In-store POS System

R

Xpress Server


TPS Client

In-store POS System

R

Xpress Server


TPS Client

In-store POS System

R

Xpress Server


TPS Client

SAP POS Store Data



Load Balancer


for Retail Server

SAP POS Store Data



Load Balancer


for Retail Server

MS SQL Server

Database

R

R

R

R

R

R

R

R

R















repository






62

CUSTOMER










Assign user names






4415 Printing

















at the registers






CUSTOMER


64

CUSTOMER












47 Troubleshooting


Guide

471 Works Cited









4-4f5d-4545-a9b5-53ebd86d7591mspx




CUSTOMER











SAP POS Store Data


Register

Register

Express Server

JEE Engine

WebSphere

Head Office



Transfer for Retail

SAP POS



SAP POS Store Data


CDL

DBSQL

ServerWeb Client

R

R

R

R

R

R



66

CUSTOMER








SAP POS








WebSphere

SystemErrlog

ltWebSphere

Homegtprofilesltpro

filenamegtlogsltSer

ver

NamegtSystemErrlog


log



WebSphere

SystemOutlog

ltWebSphere

Homegtprofilesltpro

filenamegtlogsltSer

ver

NamegtSystemOutlog

WebSphere System

Output Log

WebSphere Log


rootgtExpressReturn

sCorelogsengine

logxx

SAP RETURNS


log



engine and trickle


rootgtExpressReturn

sCorelogsloadLog

logxx

Or

SAP RETURNS

AUTHORIZATION batch

data loading log



batch data loading



CUSTOMER



ltCDL install

rootgtlogsloadLog

log


Content File



Enginelogxx




Enginelogxx





core2-5xml

Enginelogxx






Enginelogxx




Loadloglogxx




performance

Loadloglogxx





Loadloglogxx





Loadloglogxx




Loadloglogxx

68

CUSTOMER




Content File






Loadloglogxx





Loadloglogxx
















CUSTOMER















Tasks







Note




must be running







70

CUSTOMER









_8240xxwily



_9150xxWily





OR










values






Property Value
















CUSTOMER


Property Value
















Java VM options








eprofile









Example








72

CUSTOMER




Note


CA Introscope agent



hereprofile


4 Restart WebSphere






The Agent Name



Java Agent monitors











Note


work










CUSTOMER













Note


logic will not work

o Save the file

Note



CA Introscope agent








Marketplace





Marketplace

74

CUSTOMER












SAP applications














namegt



WebSphere server




namegt







AUTHORIZATION





CUSTOMER









support

3 Select Login









57 Classification


system




Application logs





76

CUSTOMER






Data


Backup of software

Configuration

Log files









rootgtstorage



Application Logs








logs







59 Periodic Tasks







CUSTOMER


Recommendation






pipelinebat























replication exists

Not applicable



bean (MDB) It is an





Not applicable

78

CUSTOMER















replication exists

511 User Management







CUSTOMER





Admin UI








administrator

To access this tool


the URL



oginjsp


Maintenance



to users




search and customer

maintenance







maintenance









replication exists



User



80

CUSTOMER








permissions


SAP RETURNS

AUTHORIZATION

512 Printing








system





balancing






Primary instance

Backup instance








CUSTOMER


MS SOL

Server


Primary Server


Backup Server

POS SAP Store Data


POS SAP Store Data


Express Server

RegisterRegister

POS SAP Store Data


Express Server

RegisterRegister

Head Office

Store 1 Store N

SAP POSSAP POS

SAP SAP POS Store



R

R

R

R

R

R

R

R

R

R












provide failover



82

CUSTOMER











Note










in this guide



CUSTOMER




service



Note




84

CUSTOMER








Application failure

Hardware failure




















CUSTOMER






515 Troubleshooting



Note





customers



















certain instances



process





86

CUSTOMER





















Components


Backup and Restore

Examples

I Only software no

configuration or

application data

- No backup new


recovery or



upgrade


BDOC Modeler


configuration

information no

application data



- No backup new

installation and


recovery


SAP Gateway

Comm Station

SAP Business

Connector

SAP IPC (20C)

III Only replicated

application data

Replication time is


recovery

Data




files

SAP IMSSearch

Engine

SAP IPC (20B)

Webserver

SAP ITS

IV Only replicated


recommended as

Data


system backup or

SAP IMSSearch

Engine

Webserver



CUSTOMER



Components


Backup and Restore

Examples



by a DBMS




V Only replicated


recommended because



DBMS

Data

- Database and log

backup or




SAP IPC (20B)

Catalog Server




Data


system backup



Webserver





AS

Data

- Database and log

backup


- Configuration

- log files


standalone system


AS

Data

- Database and log



in file system)



Standalone SAP

SAP System



systems data not

managed by a DBMS

Data


system backup data


systems must be

considered







SAP NetWeaver AS

Data

- Database and log



be considered

SAP liveCache

SAP Mobile

Workbench

88

CUSTOMER





Components


Backup and Restore

Examples






NetWeaver AS

Data

- Database and log





systems must be

considered



SAP System

SAP CRM

SAP APO


Warehouse



CUSTOMER









Remote Support





Typical problems








90

CUSTOMER



Appendix

7 Appendix

71 Related Guides


wwwsapcomcontactsap





notice



vendors














other countries






Open Group










Netscape




















CUSTOMER




1 SAP POS










10

CUSTOMER




















2 SAP POS Base
























CUSTOMER






SAP Retail



Application Server










12

CUSTOMER








Store Manager

POS Client

Mobile POS Client


Database Tools


31 Analysis Tools




Application)


the Windows Start

menu




there is an error

Manager code 6 Runs

communication

diagnostics at the

register

Manager code 900

Runs peripheral

diagnostics

Manager code 999

Shows the current

version and build







problems


service when the PC

starts up

Can run a console

from the desktop to

monitor the server


console there is a

connection box that

shows the number of

registers currently

connected







the server



CUSTOMER



the Log window

(xpslog)

LSN REPORT and


console identify

technical problems


component

Started from the


the Windows Start

menu





Connected


are successful


have failed


command line

window






corrupted b-tree



the files














handlers





14

CUSTOMER






sequence number)







Note





log file name




Example







Where





Handler





logging



CUSTOMER


Where






323 Log File Format








XCPT

EVENT

SAPTXNOBJ

TXNCOMP

BROWSER




rarr posclientlog





state events

SAPTXNOBJ ndash SAP

Transaction Object

logging

TXNCOMP ndash SAP

Transaction Object



logging

Level-based logging


diagnostic (FINEST)

PRINTER

DRAWER

MICR

MSR

KEYBOARD

DISPLAY

LOCK




rarr OPOSlog

POS OPOS device



device


level

16

CUSTOMER





SCALE

SCANNER

FISCAL_PTR

PROMO

SERVICES




rarr UElog




and SERVICES for

Services User Exit

logging

EFT_UE

EFT_IMP

PINPAD_UE

PINPAD_IMP




rarr EFTlog


POS generated log



generated log lines

under _IMP


level



Point of Sale rarr

rdatararr alleglog


Message Logging use


the following entry

HKEY_LOCAL_MACHINE

|SOFTWARE|SAPrarr


of Sale

Create a new STRING

key called

AllegianceLogWindow





accessible on the

register and shows


and from SAP POS

STORE DATA

TRANSFER FOR RETAIL

Restart the POS





contains these

messages This file

wraps like other


message text is not


and from SAP POS

STORE DATA

TRANSFER FOR RETAIL



CUSTOMER



truncated


copied to the

cXpress

Serveruploadkeep0

logs directory


g





Application


TWSecurity module



XpsLogini file


XCPT

EVENT

APPLY

XPS

APPLICATION

TRICKLE

COMMUNICATION

TLOG_UPLOADER




rarr xpslog





state events








files are logged


diagnostic logging


messaging related

diagnostic logging


from POS to Xpress

Server diagnostic

logging

COMMUNICATION ndash


SAP POS appear here

18

CUSTOMER





POSXPS Server

communication

diagnostic logging







rarr crsrvlog



and some SAP POS

STORE DATA

TRANSFER FOR RETAIL

messages for debug

purposes

This file contains



card authorizations


STORE DATA

TRANSFER FOR RETAIL


are reported here




rarr sqllog




Xpress Server rarr

sdata rarr

ApplyBPMLog

A corresponding

trigger file

ApplyBPMTrg is

created after the

Apply process

finishes writing to

the log file









files

A POSINI option

BPMAPPLYLOGFOLDER


folder where the

ApplyBPMlog file is

created No file is


does not exist

Success and failure

statuses are logged



date and time stamp



(DONE or FAIL)

duration number of



failure



operation code






the failure



Xpress Server rarr


problems detected

during the EOD

Success and failure

statuses are logged




CUSTOMER



sdata rarr

EodBPMLog

(A corresponding

trigger file

EodBPMTrg is

created after the


writing to the log

file)

procedure

A POSINI option

BPMEODLOGFOLDER


folder where the

EodBPMLog file is

created No file is


does not exist


date and time stamp


(STARTED

COMPLETED or

FAILED) duration of

EOD process (in

seconds)


TLog



Xpress Server rarr

sdata rarr

CLOGYYYYMMDDT

XT



messages to SAP POS

STORE DATA

TRANSFER FOR RETAIL





Messages checkbox


messages to SAP POS

STORE DATA

TRANSFER FOR RETAIL


Transnet



Xpress Server rarr

sdata



Responses from SAP

POS STORE DATA

TRANSFER FOR RETAIL

Sltgtltsssssgtxml -


SAP POS STORE DATA

TRANSFER FOR RETAIL


ltsssssgt = credit

sequence number

Credit Messages

tofrom SAP POS

STORE DATA

TRANSFER FOR RETAIL

Note

Not all

messages are

logged





Xpress Server rarr

sdata rarr

CRltgtxml and

rdataCCltgtxml

(Xpress Server PC)




(Register PC)


XML from SAP

RETURNS

AUTHORIZATION

CCltgtxml - XML


SAP RETURNS

AUTHORIZATION

ltgt = the register

number

SAP RETURNS

AUTHORIZATION


SAP POS STORE DATA

TRANSFER FOR RETAIL



the directory


Application


TWSecurity module

20

CUSTOMER







Store Manager rarr

bkofferr

Any Store Manager


logged here


to the cXpress

Serveruploadkeep0

logs directory as

SSSSRRBKOFFERR


Store Manager


the Xpress Server






How AppSight Works

















CUSTOMER




required




















SystemsAppSight





Recommendation










22

CUSTOMER








bkoffexe

journalexe

poswexe

xpsexe

POSGeneric


ion


nrpr

bkoffexe

journalexe

xpsctrlexe



Configurator

POSStoreStore

Configuratorrpr

poscfgwexe

POSStoreStore

Configurator


r

transnetexe

xpsexe

POSStoreOperations


algexe

poswexe

TrvLPointsexe

POSTerminal





where






Recommendation





CUSTOMER



the service







where















again manually




Note


24

CUSTOMER
























Syntax




collection















CUSTOMER



XPRESS SERVER=1

BACKUP SERVER=0

R=0





of the SMD agent









of the SMD agent









R1=0 Register 1

R2=0 Register 2



26

CUSTOMER




Xpress Server




INTROSCOPE LEVEL 10


POS - Register



running

Log Files



Example




















Note




BACKUP SERVER=0 off




CUSTOMER






















subdirectories





Formats)


28

CUSTOMER









SDK Reference










Log Files





Credit Log



crsrvlog


crsrvlog



and Event logs



and eventlog







Xcptlog

Eventlog


Store Configurator






CUSTOMER






Store Applications


database can either

be Sybase or

Microsoft SQL

Standard database

processes apply

The back office

database must be

running for Xpress

Server or POS Store

Manager

applications to

work

Standard database

POS ServerXpress

Server

2 Xpress Server is

normally configured

as a Windows

service and can be

started or stopped

automatically or


tools for Windows

The Xpress Server


be stopped by using

the Xpress Server

Console application

as well as

subsequently be

restarted This

console application

for the Xpress

Server can be run

from the desktop or

from the Windows

start menu Closing

the console


stop the POS Server

from running








Guide



does not have to be

30

CUSTOMER






started at any time

The register uses


provide information

The POS cannot

receive information

from the Xpress

Server unless the

Xpress Server is

running POS can be

started using the

desktop icon or by

using the Start

menu It can be

stopped by running

manager code 499

(Exit POS)

POS ManagerStore

Manager Application

3 The POS Store

Manager application

run after the back

office database and

Xpress Server

applications are

running

This application

does not run if the

database is not

running Several



not running If the

POS Server is

stopped while this


running this

application can be

reconnected using

the Main Menu rarr

Server State rarr

Attach function

otherwise this


be stopped and

restarted








CUSTOMER





Configurator

database must be

installed

Start this


desktop icon or

from the Start

menu





Store Configurator


Database

1 The database runs

as part of a

database server It

starts and stops

from a service



Application

2 This application

starts from the

desktop icon of the

Start menu The

journaldb

database must be


started







Files















32

CUSTOMER





Application Data

Restore


(txn)

Journals (jrn)

Daily totals data


Parameter files

Back up database


the day process

Back up Xpress

Server directories

sdata rdata and

parm

Keep all current

parameter downloads

available

Make available all

parameter file

updates done during

the day

SAP recommends


to ensure continued


the POS Server

machine has a hard

drive failure

Alternatively the

LOCAL PLU feature

can be used instead

of a backup server

With the LOCAL PLU



each register


drive failure



Server image


Copy saved sdata

rdata and parm

directories

Restore previous


database



previous backup





data for the day


database

Back up database or

keep a copy of the

database when

configuration

changes







Transaction files

(txn)

Journals (jrn)

Back up database

Back up all


journal files






of the journal and

transaction files






CUSTOMER



Application Data

Restore

containing the POS











the same register

number run manager

code 420 (import


and jrn from POS



After setup this





364 Periodic Tasks












EODPROCBAT


RETAIL)

34

CUSTOMER





up













365 Load Balancing

















CUSTOMER






















blocked

Severe



blocked

Moderate to low








Low









system crash

36

CUSTOMER





















the POS registers














CUSTOMER












Store Configurator


POS Server


POS










39 Troubleshooting






38

CUSTOMER




Peripheral Failures















CUSTOMER





text

Tware GMXP5

TWare Enterprise

texttextXML

Socket

JMS

Connection

Java

Client

Connection

JMS

Connection

Message

ManagerXML

ISO

JMS

Connection

ISO SocketIP-

Based

IP-BasedIP-

Based

IP-

Based

Message Handler

TPS NTM

Java Client

text text

APM

APM

JMS

Connection

TPS server

connection

Message

Manager

APM

TPS NTM

Server

JMS Server

OR

OR


(Store level)





North America

Problem



161916 CST]




40

CUSTOMER




Problem










CST]


needed for handler



CST]




CST]







Note



change any values




rverjvmdll




Djavaclasspath=libt


li



CUSTOMER





on




Filestransnetbin




memory

Note










delivery


meter table






42

CUSTOMER













































CUSTOMER














Example




requesttime








Note





44

CUSTOMER







Store POS

1 2

SAP POS STORE

DATA TRANSFER

FOR RETAIL

4 3





Example


----- Total TXNs ------



130000000





130000000





130000000





130000000






CUSTOMER



130000000

Note



Example






130000000






130000000






130000000

Note








46

CUSTOMER









Directory




Note














Syntax



LRootNodeNamegt







Where



set up



CUSTOMER



server


XML AUTO clause








Note




Directory




6 Choose Save






Where







48

CUSTOMER




Note














_8240xxwily



_9150xxWily





or


















CUSTOMER




o cayyztnsbpos23



















details below

Note





ofile


Example

Java VM parameters











50

CUSTOMER















Note


work

Note



CA Introscope agent















instrumentation









CUSTOMER




usrsapccmswily













o cayyzssbpos23



















Note





file


52

CUSTOMER




Example

Java VM parameters
























precisely

Note


work

Note



CA Introscope agent






CUSTOMER










Marketplace

44 Management


Store Server

HOStore Server

POS

SAP POS Store Data

Transfer for Retail

SA

P P

OS

Sto

re D

ata

Tra

nsfe

r fo

r R

eta

il

(Co

re)

NT

M C

lien

t A

PI (J

ava

)

NTM

Server

NT

M S

erv

er

AP

I (J

NI)

SAP POS Store Data

Transfer for Retail

SA

P P

OS

Sto

re D

ata

Tra

nsfe

r fo

r R

eta

il

(Co

re) Service

Provider

DB


RRRR

TCPIPTCPIP

Windows

Named Pipes







schedules

54

CUSTOMER








Note





Note



than a module






ltThreadPool


Debug=false






Note






CUSTOMER






Diagnostic Logging

Verbose Output

















Note


447 Page File







56

CUSTOMER






2 Choose Properties



5 Choose Change





Note










Note


Note










CUSTOMER














8GB RAM 3GB PAE

16GB RAM 3GB PAE

16GB + RAM PAE







Syntax


RECONFIGURE

GO


RECONFIGURE

GO

Caution




Memory option

Syntax


RECONFIGURE

GO

58

CUSTOMER




449 Logging to DB





ltConnectionPool

Debug=false







ltDatabasegt






















CUSTOMER


Note





Backup








Restore








4412 Periodic Tasks








44131 Logging On




60

CUSTOMER









Note


case sensitive


Note


case sensitive

Caution





4 Choose Login






Note










CUSTOMER


In-store POS System

R

Xpress Server


TPS Client

In-store POS System

R

Xpress Server


TPS Client

In-store POS System

R

Xpress Server


TPS Client

SAP POS Store Data



Load Balancer


for Retail Server

SAP POS Store Data



Load Balancer


for Retail Server

MS SQL Server

Database

R

R

R

R

R

R

R

R

R















repository






62

CUSTOMER










Assign user names






4415 Printing

















at the registers






CUSTOMER


64

CUSTOMER












47 Troubleshooting


Guide

471 Works Cited









4-4f5d-4545-a9b5-53ebd86d7591mspx




CUSTOMER











SAP POS Store Data


Register

Register

Express Server

JEE Engine

WebSphere

Head Office



Transfer for Retail

SAP POS



SAP POS Store Data


CDL

DBSQL

ServerWeb Client

R

R

R

R

R

R



66

CUSTOMER








SAP POS








WebSphere

SystemErrlog

ltWebSphere

Homegtprofilesltpro

filenamegtlogsltSer

ver

NamegtSystemErrlog


log



WebSphere

SystemOutlog

ltWebSphere

Homegtprofilesltpro

filenamegtlogsltSer

ver

NamegtSystemOutlog

WebSphere System

Output Log

WebSphere Log


rootgtExpressReturn

sCorelogsengine

logxx

SAP RETURNS


log



engine and trickle


rootgtExpressReturn

sCorelogsloadLog

logxx

Or

SAP RETURNS

AUTHORIZATION batch

data loading log



batch data loading



CUSTOMER



ltCDL install

rootgtlogsloadLog

log


Content File



Enginelogxx




Enginelogxx





core2-5xml

Enginelogxx






Enginelogxx




Loadloglogxx




performance

Loadloglogxx





Loadloglogxx





Loadloglogxx




Loadloglogxx

68

CUSTOMER




Content File






Loadloglogxx





Loadloglogxx
















CUSTOMER















Tasks







Note




must be running







70

CUSTOMER









_8240xxwily



_9150xxWily





OR










values






Property Value
















CUSTOMER


Property Value
















Java VM options








eprofile









Example








72

CUSTOMER




Note


CA Introscope agent



hereprofile


4 Restart WebSphere






The Agent Name



Java Agent monitors











Note


work










CUSTOMER













Note


logic will not work

o Save the file

Note



CA Introscope agent








Marketplace





Marketplace

74

CUSTOMER












SAP applications














namegt



WebSphere server




namegt







AUTHORIZATION





CUSTOMER









support

3 Select Login









57 Classification


system




Application logs





76

CUSTOMER






Data


Backup of software

Configuration

Log files









rootgtstorage



Application Logs








logs







59 Periodic Tasks







CUSTOMER


Recommendation






pipelinebat























replication exists

Not applicable



bean (MDB) It is an





Not applicable

78

CUSTOMER















replication exists

511 User Management







CUSTOMER





Admin UI








administrator

To access this tool


the URL



oginjsp


Maintenance



to users




search and customer

maintenance







maintenance









replication exists



User



80

CUSTOMER








permissions


SAP RETURNS

AUTHORIZATION

512 Printing








system





balancing






Primary instance

Backup instance








CUSTOMER


MS SOL

Server


Primary Server


Backup Server

POS SAP Store Data


POS SAP Store Data


Express Server

RegisterRegister

POS SAP Store Data


Express Server

RegisterRegister

Head Office

Store 1 Store N

SAP POSSAP POS

SAP SAP POS Store



R

R

R

R

R

R

R

R

R

R












provide failover



82

CUSTOMER











Note










in this guide



CUSTOMER




service



Note




84

CUSTOMER








Application failure

Hardware failure




















CUSTOMER






515 Troubleshooting



Note





customers



















certain instances



process





86

CUSTOMER





















Components


Backup and Restore

Examples

I Only software no

configuration or

application data

- No backup new


recovery or



upgrade


BDOC Modeler


configuration

information no

application data



- No backup new

installation and


recovery


SAP Gateway

Comm Station

SAP Business

Connector

SAP IPC (20C)

III Only replicated

application data

Replication time is


recovery

Data




files

SAP IMSSearch

Engine

SAP IPC (20B)

Webserver

SAP ITS

IV Only replicated


recommended as

Data


system backup or

SAP IMSSearch

Engine

Webserver



CUSTOMER



Components


Backup and Restore

Examples



by a DBMS




V Only replicated


recommended because



DBMS

Data

- Database and log

backup or




SAP IPC (20B)

Catalog Server




Data


system backup



Webserver





AS

Data

- Database and log

backup


- Configuration

- log files


standalone system


AS

Data

- Database and log



in file system)



Standalone SAP

SAP System



systems data not

managed by a DBMS

Data


system backup data


systems must be

considered







SAP NetWeaver AS

Data

- Database and log



be considered

SAP liveCache

SAP Mobile

Workbench

88

CUSTOMER





Components


Backup and Restore

Examples






NetWeaver AS

Data

- Database and log





systems must be

considered



SAP System

SAP CRM

SAP APO


Warehouse



CUSTOMER









Remote Support





Typical problems








90

CUSTOMER



Appendix

7 Appendix

71 Related Guides


wwwsapcomcontactsap





notice



vendors














other countries






Open Group










Netscape


















10

CUSTOMER




















2 SAP POS Base
























CUSTOMER






SAP Retail



Application Server










12

CUSTOMER








Store Manager

POS Client

Mobile POS Client


Database Tools


31 Analysis Tools




Application)


the Windows Start

menu




there is an error

Manager code 6 Runs

communication

diagnostics at the

register

Manager code 900

Runs peripheral

diagnostics

Manager code 999

Shows the current

version and build







problems


service when the PC

starts up

Can run a console

from the desktop to

monitor the server


console there is a

connection box that

shows the number of

registers currently

connected







the server



CUSTOMER



the Log window

(xpslog)

LSN REPORT and


console identify

technical problems


component

Started from the


the Windows Start

menu





Connected


are successful


have failed


command line

window






corrupted b-tree



the files














handlers





14

CUSTOMER






sequence number)







Note





log file name




Example







Where





Handler





logging



CUSTOMER


Where






323 Log File Format








XCPT

EVENT

SAPTXNOBJ

TXNCOMP

BROWSER




rarr posclientlog





state events

SAPTXNOBJ ndash SAP

Transaction Object

logging

TXNCOMP ndash SAP

Transaction Object



logging

Level-based logging


diagnostic (FINEST)

PRINTER

DRAWER

MICR

MSR

KEYBOARD

DISPLAY

LOCK




rarr OPOSlog

POS OPOS device



device


level

16

CUSTOMER





SCALE

SCANNER

FISCAL_PTR

PROMO

SERVICES




rarr UElog




and SERVICES for

Services User Exit

logging

EFT_UE

EFT_IMP

PINPAD_UE

PINPAD_IMP




rarr EFTlog


POS generated log



generated log lines

under _IMP


level



Point of Sale rarr

rdatararr alleglog


Message Logging use


the following entry

HKEY_LOCAL_MACHINE

|SOFTWARE|SAPrarr


of Sale

Create a new STRING

key called

AllegianceLogWindow





accessible on the

register and shows


and from SAP POS

STORE DATA

TRANSFER FOR RETAIL

Restart the POS





contains these

messages This file

wraps like other


message text is not


and from SAP POS

STORE DATA

TRANSFER FOR RETAIL



CUSTOMER



truncated


copied to the

cXpress

Serveruploadkeep0

logs directory


g





Application


TWSecurity module



XpsLogini file


XCPT

EVENT

APPLY

XPS

APPLICATION

TRICKLE

COMMUNICATION

TLOG_UPLOADER




rarr xpslog





state events








files are logged


diagnostic logging


messaging related

diagnostic logging


from POS to Xpress

Server diagnostic

logging

COMMUNICATION ndash


SAP POS appear here

18

CUSTOMER





POSXPS Server

communication

diagnostic logging







rarr crsrvlog



and some SAP POS

STORE DATA

TRANSFER FOR RETAIL

messages for debug

purposes

This file contains



card authorizations


STORE DATA

TRANSFER FOR RETAIL


are reported here




rarr sqllog




Xpress Server rarr

sdata rarr

ApplyBPMLog

A corresponding

trigger file

ApplyBPMTrg is

created after the

Apply process

finishes writing to

the log file









files

A POSINI option

BPMAPPLYLOGFOLDER


folder where the

ApplyBPMlog file is

created No file is


does not exist

Success and failure

statuses are logged



date and time stamp



(DONE or FAIL)

duration number of



failure



operation code






the failure



Xpress Server rarr


problems detected

during the EOD

Success and failure

statuses are logged




CUSTOMER



sdata rarr

EodBPMLog

(A corresponding

trigger file

EodBPMTrg is

created after the


writing to the log

file)

procedure

A POSINI option

BPMEODLOGFOLDER


folder where the

EodBPMLog file is

created No file is


does not exist


date and time stamp


(STARTED

COMPLETED or

FAILED) duration of

EOD process (in

seconds)


TLog



Xpress Server rarr

sdata rarr

CLOGYYYYMMDDT

XT



messages to SAP POS

STORE DATA

TRANSFER FOR RETAIL





Messages checkbox


messages to SAP POS

STORE DATA

TRANSFER FOR RETAIL


Transnet



Xpress Server rarr

sdata



Responses from SAP

POS STORE DATA

TRANSFER FOR RETAIL

Sltgtltsssssgtxml -


SAP POS STORE DATA

TRANSFER FOR RETAIL


ltsssssgt = credit

sequence number

Credit Messages

tofrom SAP POS

STORE DATA

TRANSFER FOR RETAIL

Note

Not all

messages are

logged





Xpress Server rarr

sdata rarr

CRltgtxml and

rdataCCltgtxml

(Xpress Server PC)




(Register PC)


XML from SAP

RETURNS

AUTHORIZATION

CCltgtxml - XML


SAP RETURNS

AUTHORIZATION

ltgt = the register

number

SAP RETURNS

AUTHORIZATION


SAP POS STORE DATA

TRANSFER FOR RETAIL



the directory


Application


TWSecurity module

20

CUSTOMER







Store Manager rarr

bkofferr

Any Store Manager


logged here


to the cXpress

Serveruploadkeep0

logs directory as

SSSSRRBKOFFERR


Store Manager


the Xpress Server






How AppSight Works

















CUSTOMER




required




















SystemsAppSight





Recommendation










22

CUSTOMER








bkoffexe

journalexe

poswexe

xpsexe

POSGeneric


ion


nrpr

bkoffexe

journalexe

xpsctrlexe



Configurator

POSStoreStore

Configuratorrpr

poscfgwexe

POSStoreStore

Configurator


r

transnetexe

xpsexe

POSStoreOperations


algexe

poswexe

TrvLPointsexe

POSTerminal





where






Recommendation





CUSTOMER



the service







where















again manually




Note


24

CUSTOMER
























Syntax




collection















CUSTOMER



XPRESS SERVER=1

BACKUP SERVER=0

R=0





of the SMD agent









of the SMD agent









R1=0 Register 1

R2=0 Register 2



26

CUSTOMER




Xpress Server




INTROSCOPE LEVEL 10


POS - Register



running

Log Files



Example




















Note




BACKUP SERVER=0 off




CUSTOMER






















subdirectories





Formats)


28

CUSTOMER









SDK Reference










Log Files





Credit Log



crsrvlog


crsrvlog



and Event logs



and eventlog







Xcptlog

Eventlog


Store Configurator






CUSTOMER






Store Applications


database can either

be Sybase or

Microsoft SQL

Standard database

processes apply

The back office

database must be

running for Xpress

Server or POS Store

Manager

applications to

work

Standard database

POS ServerXpress

Server

2 Xpress Server is

normally configured

as a Windows

service and can be

started or stopped

automatically or


tools for Windows

The Xpress Server


be stopped by using

the Xpress Server

Console application

as well as

subsequently be

restarted This

console application

for the Xpress

Server can be run

from the desktop or

from the Windows

start menu Closing

the console


stop the POS Server

from running








Guide



does not have to be

30

CUSTOMER






started at any time

The register uses


provide information

The POS cannot

receive information

from the Xpress

Server unless the

Xpress Server is

running POS can be

started using the

desktop icon or by

using the Start

menu It can be

stopped by running

manager code 499

(Exit POS)

POS ManagerStore

Manager Application

3 The POS Store

Manager application

run after the back

office database and

Xpress Server

applications are

running

This application

does not run if the

database is not

running Several



not running If the

POS Server is

stopped while this


running this

application can be

reconnected using

the Main Menu rarr

Server State rarr

Attach function

otherwise this


be stopped and

restarted








CUSTOMER





Configurator

database must be

installed

Start this


desktop icon or

from the Start

menu





Store Configurator


Database

1 The database runs

as part of a

database server It

starts and stops

from a service



Application

2 This application

starts from the

desktop icon of the

Start menu The

journaldb

database must be


started







Files















32

CUSTOMER





Application Data

Restore


(txn)

Journals (jrn)

Daily totals data


Parameter files

Back up database


the day process

Back up Xpress

Server directories

sdata rdata and

parm

Keep all current

parameter downloads

available

Make available all

parameter file

updates done during

the day

SAP recommends


to ensure continued


the POS Server

machine has a hard

drive failure

Alternatively the

LOCAL PLU feature

can be used instead

of a backup server

With the LOCAL PLU



each register


drive failure



Server image


Copy saved sdata

rdata and parm

directories

Restore previous


database



previous backup





data for the day


database

Back up database or

keep a copy of the

database when

configuration

changes







Transaction files

(txn)

Journals (jrn)

Back up database

Back up all


journal files






of the journal and

transaction files






CUSTOMER



Application Data

Restore

containing the POS











the same register

number run manager

code 420 (import


and jrn from POS



After setup this





364 Periodic Tasks












EODPROCBAT


RETAIL)

34

CUSTOMER





up













365 Load Balancing

















CUSTOMER






















blocked

Severe



blocked

Moderate to low








Low









system crash

36

CUSTOMER





















the POS registers














CUSTOMER












Store Configurator


POS Server


POS










39 Troubleshooting






38

CUSTOMER




Peripheral Failures















CUSTOMER





text

Tware GMXP5

TWare Enterprise

texttextXML

Socket

JMS

Connection

Java

Client

Connection

JMS

Connection

Message

ManagerXML

ISO

JMS

Connection

ISO SocketIP-

Based

IP-BasedIP-

Based

IP-

Based

Message Handler

TPS NTM

Java Client

text text

APM

APM

JMS

Connection

TPS server

connection

Message

Manager

APM

TPS NTM

Server

JMS Server

OR

OR


(Store level)





North America

Problem



161916 CST]




40

CUSTOMER




Problem










CST]


needed for handler



CST]




CST]







Note



change any values




rverjvmdll




Djavaclasspath=libt


li



CUSTOMER





on




Filestransnetbin




memory

Note










delivery


meter table






42

CUSTOMER













































CUSTOMER














Example




requesttime








Note





44

CUSTOMER







Store POS

1 2

SAP POS STORE

DATA TRANSFER

FOR RETAIL

4 3





Example


----- Total TXNs ------



130000000





130000000





130000000





130000000






CUSTOMER



130000000

Note



Example






130000000






130000000






130000000

Note








46

CUSTOMER









Directory




Note














Syntax



LRootNodeNamegt







Where



set up



CUSTOMER



server


XML AUTO clause








Note




Directory




6 Choose Save






Where







48

CUSTOMER




Note














_8240xxwily



_9150xxWily





or


















CUSTOMER




o cayyztnsbpos23



















details below

Note





ofile


Example

Java VM parameters











50

CUSTOMER















Note


work

Note



CA Introscope agent















instrumentation









CUSTOMER




usrsapccmswily













o cayyzssbpos23



















Note





file


52

CUSTOMER




Example

Java VM parameters
























precisely

Note


work

Note



CA Introscope agent






CUSTOMER










Marketplace

44 Management


Store Server

HOStore Server

POS

SAP POS Store Data

Transfer for Retail

SA

P P

OS

Sto

re D

ata

Tra

nsfe

r fo

r R

eta

il

(Co

re)

NT

M C

lien

t A

PI (J

ava

)

NTM

Server

NT

M S

erv

er

AP

I (J

NI)

SAP POS Store Data

Transfer for Retail

SA

P P

OS

Sto

re D

ata

Tra

nsfe

r fo

r R

eta

il

(Co

re) Service

Provider

DB


RRRR

TCPIPTCPIP

Windows

Named Pipes







schedules

54

CUSTOMER








Note





Note



than a module






ltThreadPool


Debug=false






Note






CUSTOMER






Diagnostic Logging

Verbose Output

















Note


447 Page File







56

CUSTOMER






2 Choose Properties



5 Choose Change





Note










Note


Note










CUSTOMER














8GB RAM 3GB PAE

16GB RAM 3GB PAE

16GB + RAM PAE







Syntax


RECONFIGURE

GO


RECONFIGURE

GO

Caution




Memory option

Syntax


RECONFIGURE

GO

58

CUSTOMER




449 Logging to DB





ltConnectionPool

Debug=false







ltDatabasegt






















CUSTOMER


Note





Backup








Restore








4412 Periodic Tasks








44131 Logging On




60

CUSTOMER









Note


case sensitive


Note


case sensitive

Caution





4 Choose Login






Note










CUSTOMER


In-store POS System

R

Xpress Server


TPS Client

In-store POS System

R

Xpress Server


TPS Client

In-store POS System

R

Xpress Server


TPS Client

SAP POS Store Data



Load Balancer


for Retail Server

SAP POS Store Data



Load Balancer


for Retail Server

MS SQL Server

Database

R

R

R

R

R

R

R

R

R















repository






62

CUSTOMER










Assign user names






4415 Printing

















at the registers






CUSTOMER


64

CUSTOMER












47 Troubleshooting


Guide

471 Works Cited









4-4f5d-4545-a9b5-53ebd86d7591mspx




CUSTOMER











SAP POS Store Data


Register

Register

Express Server

JEE Engine

WebSphere

Head Office



Transfer for Retail

SAP POS



SAP POS Store Data


CDL

DBSQL

ServerWeb Client

R

R

R

R

R

R



66

CUSTOMER








SAP POS








WebSphere

SystemErrlog

ltWebSphere

Homegtprofilesltpro

filenamegtlogsltSer

ver

NamegtSystemErrlog


log



WebSphere

SystemOutlog

ltWebSphere

Homegtprofilesltpro

filenamegtlogsltSer

ver

NamegtSystemOutlog

WebSphere System

Output Log

WebSphere Log


rootgtExpressReturn

sCorelogsengine

logxx

SAP RETURNS


log



engine and trickle


rootgtExpressReturn

sCorelogsloadLog

logxx

Or

SAP RETURNS

AUTHORIZATION batch

data loading log



batch data loading



CUSTOMER



ltCDL install

rootgtlogsloadLog

log


Content File



Enginelogxx




Enginelogxx





core2-5xml

Enginelogxx






Enginelogxx




Loadloglogxx




performance

Loadloglogxx





Loadloglogxx





Loadloglogxx




Loadloglogxx

68

CUSTOMER




Content File






Loadloglogxx





Loadloglogxx
















CUSTOMER















Tasks







Note




must be running







70

CUSTOMER









_8240xxwily



_9150xxWily





OR










values






Property Value
















CUSTOMER


Property Value
















Java VM options








eprofile









Example








72

CUSTOMER




Note


CA Introscope agent



hereprofile


4 Restart WebSphere






The Agent Name



Java Agent monitors











Note


work










CUSTOMER













Note


logic will not work

o Save the file

Note



CA Introscope agent








Marketplace





Marketplace

74

CUSTOMER












SAP applications














namegt



WebSphere server




namegt







AUTHORIZATION





CUSTOMER









support

3 Select Login









57 Classification


system




Application logs





76

CUSTOMER






Data


Backup of software

Configuration

Log files









rootgtstorage



Application Logs








logs







59 Periodic Tasks







CUSTOMER


Recommendation






pipelinebat























replication exists

Not applicable



bean (MDB) It is an





Not applicable

78

CUSTOMER















replication exists

511 User Management







CUSTOMER





Admin UI








administrator

To access this tool


the URL



oginjsp


Maintenance



to users




search and customer

maintenance







maintenance









replication exists



User



80

CUSTOMER








permissions


SAP RETURNS

AUTHORIZATION

512 Printing








system





balancing






Primary instance

Backup instance








CUSTOMER


MS SOL

Server


Primary Server


Backup Server

POS SAP Store Data


POS SAP Store Data


Express Server

RegisterRegister

POS SAP Store Data


Express Server

RegisterRegister

Head Office

Store 1 Store N

SAP POSSAP POS

SAP SAP POS Store



R

R

R

R

R

R

R

R

R

R












provide failover



82

CUSTOMER











Note










in this guide



CUSTOMER




service



Note




84

CUSTOMER








Application failure

Hardware failure




















CUSTOMER






515 Troubleshooting



Note





customers



















certain instances



process





86

CUSTOMER





















Components


Backup and Restore

Examples

I Only software no

configuration or

application data

- No backup new


recovery or



upgrade


BDOC Modeler


configuration

information no

application data



- No backup new

installation and


recovery


SAP Gateway

Comm Station

SAP Business

Connector

SAP IPC (20C)

III Only replicated

application data

Replication time is


recovery

Data




files

SAP IMSSearch

Engine

SAP IPC (20B)

Webserver

SAP ITS

IV Only replicated


recommended as

Data


system backup or

SAP IMSSearch

Engine

Webserver



CUSTOMER



Components


Backup and Restore

Examples



by a DBMS




V Only replicated


recommended because



DBMS

Data

- Database and log

backup or




SAP IPC (20B)

Catalog Server




Data


system backup



Webserver





AS

Data

- Database and log

backup


- Configuration

- log files


standalone system


AS

Data

- Database and log



in file system)



Standalone SAP

SAP System



systems data not

managed by a DBMS

Data


system backup data


systems must be

considered







SAP NetWeaver AS

Data

- Database and log



be considered

SAP liveCache

SAP Mobile

Workbench

88

CUSTOMER





Components


Backup and Restore

Examples






NetWeaver AS

Data

- Database and log





systems must be

considered



SAP System

SAP CRM

SAP APO


Warehouse



CUSTOMER









Remote Support





Typical problems








90

CUSTOMER



Appendix

7 Appendix

71 Related Guides


wwwsapcomcontactsap





notice



vendors














other countries






Open Group










Netscape




















CUSTOMER






SAP Retail



Application Server










12

CUSTOMER








Store Manager

POS Client

Mobile POS Client


Database Tools


31 Analysis Tools




Application)


the Windows Start

menu




there is an error

Manager code 6 Runs

communication

diagnostics at the

register

Manager code 900

Runs peripheral

diagnostics

Manager code 999

Shows the current

version and build







problems


service when the PC

starts up

Can run a console

from the desktop to

monitor the server


console there is a

connection box that

shows the number of

registers currently

connected







the server



CUSTOMER



the Log window

(xpslog)

LSN REPORT and


console identify

technical problems


component

Started from the


the Windows Start

menu





Connected


are successful


have failed


command line

window






corrupted b-tree



the files














handlers





14

CUSTOMER






sequence number)







Note





log file name




Example







Where





Handler





logging



CUSTOMER


Where






323 Log File Format








XCPT

EVENT

SAPTXNOBJ

TXNCOMP

BROWSER




rarr posclientlog





state events

SAPTXNOBJ ndash SAP

Transaction Object

logging

TXNCOMP ndash SAP

Transaction Object



logging

Level-based logging


diagnostic (FINEST)

PRINTER

DRAWER

MICR

MSR

KEYBOARD

DISPLAY

LOCK




rarr OPOSlog

POS OPOS device



device


level

16

CUSTOMER





SCALE

SCANNER

FISCAL_PTR

PROMO

SERVICES




rarr UElog




and SERVICES for

Services User Exit

logging

EFT_UE

EFT_IMP

PINPAD_UE

PINPAD_IMP




rarr EFTlog


POS generated log



generated log lines

under _IMP


level



Point of Sale rarr

rdatararr alleglog


Message Logging use


the following entry

HKEY_LOCAL_MACHINE

|SOFTWARE|SAPrarr


of Sale

Create a new STRING

key called

AllegianceLogWindow





accessible on the

register and shows


and from SAP POS

STORE DATA

TRANSFER FOR RETAIL

Restart the POS





contains these

messages This file

wraps like other


message text is not


and from SAP POS

STORE DATA

TRANSFER FOR RETAIL



CUSTOMER



truncated


copied to the

cXpress

Serveruploadkeep0

logs directory


g





Application


TWSecurity module



XpsLogini file


XCPT

EVENT

APPLY

XPS

APPLICATION

TRICKLE

COMMUNICATION

TLOG_UPLOADER




rarr xpslog





state events








files are logged


diagnostic logging


messaging related

diagnostic logging


from POS to Xpress

Server diagnostic

logging

COMMUNICATION ndash


SAP POS appear here

18

CUSTOMER





POSXPS Server

communication

diagnostic logging







rarr crsrvlog



and some SAP POS

STORE DATA

TRANSFER FOR RETAIL

messages for debug

purposes

This file contains



card authorizations


STORE DATA

TRANSFER FOR RETAIL


are reported here




rarr sqllog




Xpress Server rarr

sdata rarr

ApplyBPMLog

A corresponding

trigger file

ApplyBPMTrg is

created after the

Apply process

finishes writing to

the log file









files

A POSINI option

BPMAPPLYLOGFOLDER


folder where the

ApplyBPMlog file is

created No file is


does not exist

Success and failure

statuses are logged



date and time stamp



(DONE or FAIL)

duration number of



failure



operation code






the failure



Xpress Server rarr


problems detected

during the EOD

Success and failure

statuses are logged




CUSTOMER



sdata rarr

EodBPMLog

(A corresponding

trigger file

EodBPMTrg is

created after the


writing to the log

file)

procedure

A POSINI option

BPMEODLOGFOLDER


folder where the

EodBPMLog file is

created No file is


does not exist


date and time stamp


(STARTED

COMPLETED or

FAILED) duration of

EOD process (in

seconds)


TLog



Xpress Server rarr

sdata rarr

CLOGYYYYMMDDT

XT



messages to SAP POS

STORE DATA

TRANSFER FOR RETAIL





Messages checkbox


messages to SAP POS

STORE DATA

TRANSFER FOR RETAIL


Transnet



Xpress Server rarr

sdata



Responses from SAP

POS STORE DATA

TRANSFER FOR RETAIL

Sltgtltsssssgtxml -


SAP POS STORE DATA

TRANSFER FOR RETAIL


ltsssssgt = credit

sequence number

Credit Messages

tofrom SAP POS

STORE DATA

TRANSFER FOR RETAIL

Note

Not all

messages are

logged





Xpress Server rarr

sdata rarr

CRltgtxml and

rdataCCltgtxml

(Xpress Server PC)




(Register PC)


XML from SAP

RETURNS

AUTHORIZATION

CCltgtxml - XML


SAP RETURNS

AUTHORIZATION

ltgt = the register

number

SAP RETURNS

AUTHORIZATION


SAP POS STORE DATA

TRANSFER FOR RETAIL



the directory


Application


TWSecurity module

20

CUSTOMER







Store Manager rarr

bkofferr

Any Store Manager


logged here


to the cXpress

Serveruploadkeep0

logs directory as

SSSSRRBKOFFERR


Store Manager


the Xpress Server






How AppSight Works

















CUSTOMER




required




















SystemsAppSight





Recommendation










22

CUSTOMER








bkoffexe

journalexe

poswexe

xpsexe

POSGeneric


ion


nrpr

bkoffexe

journalexe

xpsctrlexe



Configurator

POSStoreStore

Configuratorrpr

poscfgwexe

POSStoreStore

Configurator


r

transnetexe

xpsexe

POSStoreOperations


algexe

poswexe

TrvLPointsexe

POSTerminal





where






Recommendation





CUSTOMER



the service







where















again manually




Note


24

CUSTOMER
























Syntax




collection















CUSTOMER



XPRESS SERVER=1

BACKUP SERVER=0

R=0





of the SMD agent









of the SMD agent









R1=0 Register 1

R2=0 Register 2



26

CUSTOMER




Xpress Server




INTROSCOPE LEVEL 10


POS - Register



running

Log Files



Example




















Note




BACKUP SERVER=0 off




CUSTOMER






















subdirectories





Formats)


28

CUSTOMER









SDK Reference










Log Files





Credit Log



crsrvlog


crsrvlog



and Event logs



and eventlog







Xcptlog

Eventlog


Store Configurator






CUSTOMER






Store Applications


database can either

be Sybase or

Microsoft SQL

Standard database

processes apply

The back office

database must be

running for Xpress

Server or POS Store

Manager

applications to

work

Standard database

POS ServerXpress

Server

2 Xpress Server is

normally configured

as a Windows

service and can be

started or stopped

automatically or


tools for Windows

The Xpress Server


be stopped by using

the Xpress Server

Console application

as well as

subsequently be

restarted This

console application

for the Xpress

Server can be run

from the desktop or

from the Windows

start menu Closing

the console


stop the POS Server

from running








Guide



does not have to be

30

CUSTOMER






started at any time

The register uses


provide information

The POS cannot

receive information

from the Xpress

Server unless the

Xpress Server is

running POS can be

started using the

desktop icon or by

using the Start

menu It can be

stopped by running

manager code 499

(Exit POS)

POS ManagerStore

Manager Application

3 The POS Store

Manager application

run after the back

office database and

Xpress Server

applications are

running

This application

does not run if the

database is not

running Several



not running If the

POS Server is

stopped while this


running this

application can be

reconnected using

the Main Menu rarr

Server State rarr

Attach function

otherwise this


be stopped and

restarted








CUSTOMER





Configurator

database must be

installed

Start this


desktop icon or

from the Start

menu





Store Configurator


Database

1 The database runs

as part of a

database server It

starts and stops

from a service



Application

2 This application

starts from the

desktop icon of the

Start menu The

journaldb

database must be


started







Files















32

CUSTOMER





Application Data

Restore


(txn)

Journals (jrn)

Daily totals data


Parameter files

Back up database


the day process

Back up Xpress

Server directories

sdata rdata and

parm

Keep all current

parameter downloads

available

Make available all

parameter file

updates done during

the day

SAP recommends


to ensure continued


the POS Server

machine has a hard

drive failure

Alternatively the

LOCAL PLU feature

can be used instead

of a backup server

With the LOCAL PLU



each register


drive failure



Server image


Copy saved sdata

rdata and parm

directories

Restore previous


database



previous backup





data for the day


database

Back up database or

keep a copy of the

database when

configuration

changes







Transaction files

(txn)

Journals (jrn)

Back up database

Back up all


journal files






of the journal and

transaction files






CUSTOMER



Application Data

Restore

containing the POS











the same register

number run manager

code 420 (import


and jrn from POS



After setup this





364 Periodic Tasks












EODPROCBAT


RETAIL)

34

CUSTOMER





up













365 Load Balancing

















CUSTOMER






















blocked

Severe



blocked

Moderate to low








Low









system crash

36

CUSTOMER





















the POS registers














CUSTOMER












Store Configurator


POS Server


POS










39 Troubleshooting






38

CUSTOMER




Peripheral Failures















CUSTOMER





text

Tware GMXP5

TWare Enterprise

texttextXML

Socket

JMS

Connection

Java

Client

Connection

JMS

Connection

Message

ManagerXML

ISO

JMS

Connection

ISO SocketIP-

Based

IP-BasedIP-

Based

IP-

Based

Message Handler

TPS NTM

Java Client

text text

APM

APM

JMS

Connection

TPS server

connection

Message

Manager

APM

TPS NTM

Server

JMS Server

OR

OR


(Store level)





North America

Problem



161916 CST]




40

CUSTOMER




Problem










CST]


needed for handler



CST]




CST]







Note



change any values




rverjvmdll




Djavaclasspath=libt


li



CUSTOMER





on




Filestransnetbin




memory

Note










delivery


meter table






42

CUSTOMER













































CUSTOMER














Example




requesttime








Note





44

CUSTOMER







Store POS

1 2

SAP POS STORE

DATA TRANSFER

FOR RETAIL

4 3





Example


----- Total TXNs ------



130000000





130000000





130000000





130000000






CUSTOMER



130000000

Note



Example






130000000






130000000






130000000

Note








46

CUSTOMER









Directory




Note














Syntax



LRootNodeNamegt







Where



set up



CUSTOMER



server


XML AUTO clause








Note




Directory




6 Choose Save






Where







48

CUSTOMER




Note














_8240xxwily



_9150xxWily





or


















CUSTOMER




o cayyztnsbpos23



















details below

Note





ofile


Example

Java VM parameters











50

CUSTOMER















Note


work

Note



CA Introscope agent















instrumentation









CUSTOMER




usrsapccmswily













o cayyzssbpos23



















Note





file


52

CUSTOMER




Example

Java VM parameters
























precisely

Note


work

Note



CA Introscope agent






CUSTOMER










Marketplace

44 Management


Store Server

HOStore Server

POS

SAP POS Store Data

Transfer for Retail

SA

P P

OS

Sto

re D

ata

Tra

nsfe

r fo

r R

eta

il

(Co

re)

NT

M C

lien

t A

PI (J

ava

)

NTM

Server

NT

M S

erv

er

AP

I (J

NI)

SAP POS Store Data

Transfer for Retail

SA

P P

OS

Sto

re D

ata

Tra

nsfe

r fo

r R

eta

il

(Co

re) Service

Provider

DB


RRRR

TCPIPTCPIP

Windows

Named Pipes







schedules

54

CUSTOMER








Note





Note



than a module






ltThreadPool


Debug=false






Note






CUSTOMER






Diagnostic Logging

Verbose Output

















Note


447 Page File







56

CUSTOMER






2 Choose Properties



5 Choose Change





Note










Note


Note










CUSTOMER














8GB RAM 3GB PAE

16GB RAM 3GB PAE

16GB + RAM PAE







Syntax


RECONFIGURE

GO


RECONFIGURE

GO

Caution




Memory option

Syntax


RECONFIGURE

GO

58

CUSTOMER




449 Logging to DB





ltConnectionPool

Debug=false







ltDatabasegt






















CUSTOMER


Note





Backup








Restore








4412 Periodic Tasks








44131 Logging On




60

CUSTOMER









Note


case sensitive


Note


case sensitive

Caution





4 Choose Login






Note










CUSTOMER


In-store POS System

R

Xpress Server


TPS Client

In-store POS System

R

Xpress Server


TPS Client

In-store POS System

R

Xpress Server


TPS Client

SAP POS Store Data



Load Balancer


for Retail Server

SAP POS Store Data



Load Balancer


for Retail Server

MS SQL Server

Database

R

R

R

R

R

R

R

R

R















repository






62

CUSTOMER










Assign user names






4415 Printing

















at the registers






CUSTOMER


64

CUSTOMER












47 Troubleshooting


Guide

471 Works Cited









4-4f5d-4545-a9b5-53ebd86d7591mspx




CUSTOMER











SAP POS Store Data


Register

Register

Express Server

JEE Engine

WebSphere

Head Office



Transfer for Retail

SAP POS



SAP POS Store Data


CDL

DBSQL

ServerWeb Client

R

R

R

R

R

R



66

CUSTOMER








SAP POS








WebSphere

SystemErrlog

ltWebSphere

Homegtprofilesltpro

filenamegtlogsltSer

ver

NamegtSystemErrlog


log



WebSphere

SystemOutlog

ltWebSphere

Homegtprofilesltpro

filenamegtlogsltSer

ver

NamegtSystemOutlog

WebSphere System

Output Log

WebSphere Log


rootgtExpressReturn

sCorelogsengine

logxx

SAP RETURNS


log



engine and trickle


rootgtExpressReturn

sCorelogsloadLog

logxx

Or

SAP RETURNS

AUTHORIZATION batch

data loading log



batch data loading



CUSTOMER



ltCDL install

rootgtlogsloadLog

log


Content File



Enginelogxx




Enginelogxx





core2-5xml

Enginelogxx






Enginelogxx




Loadloglogxx




performance

Loadloglogxx





Loadloglogxx





Loadloglogxx




Loadloglogxx

68

CUSTOMER




Content File






Loadloglogxx





Loadloglogxx
















CUSTOMER















Tasks







Note




must be running







70

CUSTOMER









_8240xxwily



_9150xxWily





OR










values






Property Value
















CUSTOMER


Property Value
















Java VM options








eprofile









Example








72

CUSTOMER




Note


CA Introscope agent



hereprofile


4 Restart WebSphere






The Agent Name



Java Agent monitors











Note


work










CUSTOMER













Note


logic will not work

o Save the file

Note



CA Introscope agent








Marketplace





Marketplace

74

CUSTOMER












SAP applications














namegt



WebSphere server




namegt







AUTHORIZATION





CUSTOMER









support

3 Select Login









57 Classification


system




Application logs





76

CUSTOMER






Data


Backup of software

Configuration

Log files









rootgtstorage



Application Logs








logs







59 Periodic Tasks







CUSTOMER


Recommendation






pipelinebat























replication exists

Not applicable



bean (MDB) It is an





Not applicable

78

CUSTOMER















replication exists

511 User Management







CUSTOMER





Admin UI








administrator

To access this tool


the URL



oginjsp


Maintenance



to users




search and customer

maintenance







maintenance









replication exists



User



80

CUSTOMER








permissions


SAP RETURNS

AUTHORIZATION

512 Printing








system





balancing






Primary instance

Backup instance








CUSTOMER


MS SOL

Server


Primary Server


Backup Server

POS SAP Store Data


POS SAP Store Data


Express Server

RegisterRegister

POS SAP Store Data


Express Server

RegisterRegister

Head Office

Store 1 Store N

SAP POSSAP POS

SAP SAP POS Store



R

R

R

R

R

R

R

R

R

R












provide failover



82

CUSTOMER











Note










in this guide



CUSTOMER




service



Note




84

CUSTOMER








Application failure

Hardware failure




















CUSTOMER






515 Troubleshooting



Note





customers



















certain instances



process





86

CUSTOMER





















Components


Backup and Restore

Examples

I Only software no

configuration or

application data

- No backup new


recovery or



upgrade


BDOC Modeler


configuration

information no

application data



- No backup new

installation and


recovery


SAP Gateway

Comm Station

SAP Business

Connector

SAP IPC (20C)

III Only replicated

application data

Replication time is


recovery

Data




files

SAP IMSSearch

Engine

SAP IPC (20B)

Webserver

SAP ITS

IV Only replicated


recommended as

Data


system backup or

SAP IMSSearch

Engine

Webserver



CUSTOMER



Components


Backup and Restore

Examples



by a DBMS




V Only replicated


recommended because



DBMS

Data

- Database and log

backup or




SAP IPC (20B)

Catalog Server




Data


system backup



Webserver





AS

Data

- Database and log

backup


- Configuration

- log files


standalone system


AS

Data

- Database and log



in file system)



Standalone SAP

SAP System



systems data not

managed by a DBMS

Data


system backup data


systems must be

considered







SAP NetWeaver AS

Data

- Database and log



be considered

SAP liveCache

SAP Mobile

Workbench

88

CUSTOMER





Components


Backup and Restore

Examples






NetWeaver AS

Data

- Database and log





systems must be

considered



SAP System

SAP CRM

SAP APO


Warehouse



CUSTOMER









Remote Support





Typical problems








90

CUSTOMER



Appendix

7 Appendix

71 Related Guides


wwwsapcomcontactsap





notice



vendors














other countries






Open Group










Netscape


















Documents

SAP Point-of-Sale 2.3 Application Operations Guide