Supporting SAP POS Best Practices Setting Log File Sizes and Retention Summary: This paper will serve as a primer in order to familiarize users of SAP POS with the log configuration and location of SAP POS. Also included in the document are supporting Operating System log files that can be provided to facilitate investigation by Primary Support, as well as helpful tips to assist the user in performing their own investigation prior to submitting a message to SAP. Author: Angelo Tauro Company: SAP Canada Created on: 16 December 2010 Author Bio Angelo Tauro is a Nexus Consultant in Toronto Canada working for SAP Active Global Support - Primary Support BST 2010 SAP AG 1
Table of Contents Setting log file sizes... 3 Set the number of Keep folders on the Xpress Server... 5 Data Retention... 5 Daily Log File backup... 5 Related Content... 6 Copyright... 7 2010 SAP AG 2
Setting log file sizes Setting up of the log file size and retention period in your retail environment will enable your organization to provide the necessary the requested files in one convenient location. Xpress Server Log Name: Xps.log Location: \xps or \program files\sap\retail systems\xpress server Contents: Credit processing, data posting, store administrative, file apply information 1. Open the Xpress Server console 2. Select the Properties Tab 3. Select the Maximum Logging Size base on volume and drive space 4. Confirm the radio button for "date and time" is set 5. Restart the service Credit Logging Name: Crsrv.log Location: \xps or \program files\sap\retail systems\xpress server Contents: Credit specific information Steps to complete via Configurator: 1. Open the SAP Configurator application 2. Select the Credit Tab 3. Select the Credit Parameter icon 4. Set the Credit Log Level to the value 5 (Level 5 is full-debugging which is generally sufficient) 5. Convert and apply the parm files Steps to complete via POS.ini: 1. Navigate to \xps\parm or \program files\sap\retail systems\xpress server\parm 2. Edit the pos.ini 3. If the Configurator method is used comment out the #CREDITLOG= option 4. If the above Configurator configuration is not used or needs to be overridden modify the following option CREDITLOG=X to 5 or level requested by Support Consultant Transnet Client Log Name: log.txt log.txt.2 log.txt.3 etc Location: \program files\transnet\logs or \program files\sap\transnet\logs Contents: Transnet Client messaging to Transnet Server. What is received from Xpress Server by the Transnet Client and sent to Transnet Server, and what is received from Transnet Server by the Transnet Client and sent to Xpress Server 1. Navigate to <transnet root>\config 2. Edit the logging.properties 3. Modify the line log4j.rootcategory=xxxxx, R to DEBUG (X's represent where DEBUG should be entered) 4. Modify the line log4j.appender.r.maxfilesize=####### to an appropriate size in bytes 5. Modify the line log4j.appender.r.maxbackupindex=xx. This will set the number of iterations before looping to the next log file 6. Stop and Start the Transnet Service 2010 SAP AG 3
Note: Debug logging generates larger files which will take more space on the server The MaxFileSize should be balanced with the number of log iterations to capture on day's worth of business without overwriting itself An ideal setting would be 10 files at 50000000 bytes (50MB) Dr Watson Logging Name: drwtsn32.log Location: As defined in drwtsn32.exe GUI Contents: When the application experiences crashes, the necessary information is logged to a Windows dump. This dump file can be configured to display the required information for Development to investigate the crash. 1. Select 'Start' 2. Select 'Run' 3. Type in 'drwtsn32' <ENTER> 4. A Dr. Watson GUI will be displayed 5. Adjust the 'Log File Path' and 'Dump File Path' (if necessary) 6. Set the number of instructions to "100" 7. Set the number of errors to "100" 8. Set the crash dump type to "Full" 9. Select "Dump Symbol Table" 10. Create "Crash dump File" 11. Remove OLD crash dumps and collect them regularly 2010 SAP AG 4
Set the number of Keep folders on the Xpress Server Data Retention The primary reason to set an appropriate number of Keep folders on the Xpress Server terminal is for increased data redundancy and log retention. 1. Confirm that there is appropriate drive space on the Server drive for the desired setting 2. Start the Store Configurator 3. Select the Transaction Functions tab 4. Select the Register Parameters icon 5. Open the default record 6. Select the Polling option 7. Set the Server Tlog Backup field to the desired number (max 99) The primary reason to set an appropriate number of Keep folders on the POS terminal is for increased data redundancy and log retention at a register level. 1. Start the Store Configurator 2. Select the correct Configurator database 3. Select the Transaction Functions tab 4. Select the Register Parameters icon 5. Open the default record 6. Select the Polling option 7. Confirm that there is appropriate drive space on the register drive for the desired setting 8. Set the 2nd POS Tlog Backup field to the desired number (max 99) Daily Log File backup Log file collection and archiving are generally done by the eodproc.bat. To achieve a nightly copies of a business day complete the following steps: Move *.log from \xps or \program files\sap\retail systems\xpress server to upload\keep1 Move *.txt * from \program files\transnet\logs or \program files\sap\transnet\logs to Keep1 Copy or move drwtsn32.log from \Microsoft\Dr Watson to Keep1 Compress all files to save drive space 2010 SAP AG 5
Related Content For more information, visit the Retail homepage. 2010 SAP AG 6
Copyright Copyright 2010 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iseries, pseries, xseries, zseries, eserver, z/vm, z/os, i5/os, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, 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 other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company. 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. 2010 SAP AG 7