PUBLIC Upgrade Guide SAP Centralized Electronic Funds Transfer 1.8 Target Audience System administrators Technology consultants Document version: 1.1 May 26, 2008
SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 24 F +49/18 05/34 34 20 www.sap.com Copyright 2008 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, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iseries, pseries, xseries, zseries, z/os, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/os, POWER, POWER5, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. 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. SAP, R/3, mysap, mysap.com, xapps, xapp, SAP NetWeaver, 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. Disclaimer Some components of this product are based on Java. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components. Any Java Source Code delivered with this product is only to be used by SAP s Support Services and may not be modified or altered in any way. Documentation in the SAP Service Marketplace You can find this documentation at the following address: http://service.sap.com/instguides JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden.
Typographic Conventions Icons Type Style Example Text Example text EXAMPLE TEXT Example text Example text <Example text> EXAMPLE TEXT Description Words or characters quoted from the screen. These include field names, screen titles, pushbutton labels, menu names, menu paths, and menu options. Cross-references to other documentation Emphasized words or phrases in body text, graphic titles, and table titles Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE. Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools. Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. Keys on the keyboard, for example, F2 or ENTER. Icon Meaning Caution Example Note Recommendation Syntax Additional icons are used in SAP Library documentation to help you identify different types of information at a glance. For more information, see Help on Help General Information Classes and Information Classes for Business Information Warehouse on the first page of any version of SAP Library.
Upgrade Guide: SAP Centralized Electronic Funds Transfer Contents 1 Introduction...5 1.1 Document History... 6 1.2 About this Document... 7 1.3 Before You Start... 8 2 Upgrade Step by Step...9 3 Planning...10 4 Preparation...11 5 Upgrade Process...12 6 Follow-Up Activities...14 7 Troubleshooting...15 8 Upgrade Administration...16 9 Upgrade Tools...17 10 Reference...18 4 May 2008
1 Introduction This section provides introductory information you need to know before you begin upgrading the SAP Centralized Electronic Funds Transfer (SAP Centralized EFT) component. May 2008 5
1.1 Document History The following table provides an overview about the most important document changes: Version Date Description 1.0 June 2007 First version 6 May 2008
1.2 About this Document Purpose This document provides information on how to reinstall and upgrade POS Services 1.1 - Transnet 1.8 Integration This document should be used in conjunction with the SAP Centralized EFT Installation and Configuration Guide. Constraints This document does not apply if you are installing SAP Centralized EFT/File Transfer (Transnet) for the first time. If you are installing the component for the first time, refer to the SAP Centralized EFT Installation and Configuration Guide for more information. May 2008 7
1 Introduction 1.3 Before You Start Refer to the Before You Start section in the SAP Centralized EFT Installation and Configuration Guide. 1.3.1 Naming Conventions Refer to the Terminology section in the SAP Centralized EFT Installation and Configuration Guide 1.3.2 New Features There are no new installation upgrade features for this release. 1.3.3. SAP Notes for the Upgrade At this time there are no SAP notes for Transnet 1.8. 8 May 2008
2 Upgrade Step by Step 2 Upgrade Step by Step If a reinstallation is deemed necessary, ensure the database credentials, including: User, Schema, Security Logon and database instance that were created during the installation process are properly deleted before performing the reinstallation. Planning Activity Not applicable Preparation Activity Not applicable Upgrade Process Activity See Section 5 for instructions Follow-Up Activities Activity Not applicable May 2008 9
3 Planning 3 Planning An upgrade process requires time and planning. If you are planning an upgrade, you would need to schedule it in advance besides planning the upgrade sequence. When you first installed the application, you would have followed the Planning and Preparation sections in the SAP Centralized EFT Installation and Configuration Guide. Refer to this Guide for more information. 10 May 2008
4 Preparation 4 Preparation See the Preparation section in the SAP Centralized Electronic Funds Transfer Installation and Configuration Guide for more information. May 2008 11
5 Upgrade Process 5 Upgrade Process Upgrade from TN1.7 to TN1.8 This process is usually completed in one hour and thirty minutes. Upgrade Steps 1. Stop services: Tomcat, Transnet, TPS Command Service, NTM Manager and NTM Log Daemon. 2. In the Transnet directory, backup TPS license(.tpsntm.tps),config andlib directories. 3. Uninstall Transnet 1.7 from Add\Remove Programs in the Control Panel. 4. Transfer encryption key from twsecurity.jar into the new twsecurity 2.0 keystore(keydata.dat) a) Export the encryption key from the original tw-security.jar (1.0.6). b) Import the encryption key to the newtw-security.jar (2.0). c) Map the encryption key to the STORAGE Channel. d) Add the encryption key to thetw-security.jar. 5. Runupgradepaymentdetail.bat (batch not included to be supplied by SAP) file to rename the PAYMENTDETAIL TABLE to PAYMENTDETAIL.OLD. 6. Placejakarta-tomcat-4.1.31.zip in the root andc:\ directories and run Transnet 1.8 installer. 7. Runupgradetnuser.bat (batch not included to be supplied by SAP) file to convert the TNUSER TABLE (this process typically takes a couple of minutes). 8. Restore backed upconfig as below: a) config\transnet.xml b) config\*merchant.xml c) Replace anyjar file from the oldlib directory that is not in the newlib directory. 9. Add the following properties to TWSecurity keystore through TWInstall.bat (batch not included to be supplied by SAP) a) dbuser the user name to login to the database b) dbpassword the password to login to the database c) markallbutlastfour false d) defaulttoken the current activechanneled=storage token e) Any APM passwords 10. Start Transnet. 11. Transnet Realtime should be running fine at this point. No Store or EFT Provider TLog loading should be done until the conversion takes place; the Transnet reporting will be slower. (4500 transactions per second Pentium 4 1.5 GHz 512Meg SQL2000) (9000 transactions per second Pentium M 1.66 GHz 2Gig SQL2005) 12 May 2008
5 Upgrade Process 12. Run batch file to convert PAYMENTDETAIL.OLD in the background. 13. Run batch file to convert PAYMENTDETAIL_BANK in the background. 14. Run batch file to convert PAYMENTDETAIL_STORE in the background. 15. Store and EFT Provider TLog loading may resume. 16. Shut down Transnet. 17. Run batch file to append new PAYMENTDETAIL TABLE records to converted old PAYMENTDETAILTABLE. 18. Delete the new PAYMENTDETAIL TABLE. 19. Rename the converted PAYMENTDETAIL.OLD TABLE to PAYMENTDETAIL. The last four steps would typically take half an hour to complete. May 2008 13
6 Follow-Up Activities 6 Follow-Up Activities Refer to the Follow-Up Activities section in the SAP Centralized EFT Installation and Configuration Guide for more information 14 May 2008
7 Troubleshooting 7 Troubleshooting Refer to the Troubleshooting section in the SAP Centralized EFT Installation and Configuration Guide for more information May 2008 15
8 Upgrade Administration 8 Upgrade Administration Other than the tasks mentioned in the Planning and Upgrade Process sections in this Guide, no additional administrative tasks are required to reinstall or upgrade the application. 16 May 2008
9 Upgrade Tools 9 Upgrade Tools No additional tools are required to reinstall or upgrade the application. May 2008 17
10 Reference 10 Reference Related documentation: The SAP Centralized EFT Installation and Configuration Guide. 18 May 2008