SAP NetWeaver How-To Guide How-To Transport Gateway services to Newer Trial Version

Transcription

1 SAP NetWeaver How-To Guide How-To Transport Gateway services to Newer Trial Version Applicable Releases: SAP NetWeaver Gateway Trial Version SP4 and up Version 1.0 December 2012

2 Copyright 2012 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, PowerPoint, Silverlight, and Visual Studio 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, z10, z/vm, z/os, OS/390, zenterprise, PowerVM, Power Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, purescale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the United States and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countries. Oracle and Java are registered trademarks of Oracle and its affiliates. 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. Apple, App Store, ibooks, ipad, iphone, iphoto, ipod, itunes, Multi- Touch, Objective-C, Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc. IOS is a registered trademark of Cisco Systems Inc. RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App World are trademarks or registered trademarks of Research in Motion Limited. Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android are trademarks or registered trademarks of Google Inc. INTERMEC is a registered trademark of Intermec Technologies Corporation. Wi-Fi is a registered trademark of Wi-Fi Alliance. Bluetooth is a registered trademark of Bluetooth SIG Inc. Motorola is a registered trademark of Motorola Trademark Holdings LLC. Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, 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 Software Ltd. Business Objects is an SAP company. Sybase and Adaptive Server, ianywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc. Sybase is an SAP company. Crossgate, m@gic EDDY, B2B 360, and B2B 360 Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate 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. These materials are provided as is without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these materials. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third party web pages nor provide any warranty whatsoever relating to third party web pages. SAP NetWeaver How-to Guides are intended to simplify the product implementation. While specific product features and procedures typically are explained in a practical business context, it is not implied that those features and procedures are the only approach in solving a specific business problem using SAP NetWeaver. Should you wish to receive additional information, clarification or support, please refer to SAP Consulting. Any software coding and/or code lines / strings ( Code ) included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or grossly negligent. 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. i

3 Document History Document Version Description 1.00 First official release of this guide ii

4 Typographic Conventions Icons Type Style Description Icon Description Example Text Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Cross-references to other documentation Caution Important Note Recommendation or Tip Example Example text Emphasized words or phrases in body text, graphic titles, and table titles Example text File and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools. Example text User entry texts. These are words or characters that you enter in the system exactly as they appear in the documentation. <Example text> Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER. iii

5 Table of Contents 1. Business Scenario Background Information Prerequisites Step-by-Step Procedure Saving the Objects to a transport Rebuilding Generated Service Create Final Transport In the SP5 System iv

6 1. Business Scenario The SAP NetWeaver Trial versions that are available on SCN are only licensed as is. Meaning that due to their license restrictions they cannot be upgraded or enhanced with new features of SAP NetWeaver Gateway 2.0 that are continually being enhanced. 2. Background Information Given that a SAP NetWeaver gateway service was created on one trial version, it might still be relevant when the new features of the next trial version is released. Rather than going about and recreating the service, this How-to guide will show you how to move what you have created to a newer release of the SAP NetWeaver Trial versions. 3. Prerequisites Although the procedures of this guide can be applied to practically any SAP NetWeaver instance, it is written explicitly for upgrading from the SAP NetWeaver Gateway 2.0 SP4 release on Linux to SAP NetWeaver Gateway 2.0 SP5 release. A running instance of the SP4 release with access to the file system with user npladm (This user was created when you installed the Trial version and is the user that starts and stops the SAP NetWeaver instance. A running instance of the SP5 release with access to the file system with user npladm. You will be creating files that you need to move from the older system and placing on the newer system, so access from the machine to either a web based system, or installing VMware tools to share USB drives for example. December

7 ... How-To Transport Gateway services to Newer Trial Version 4. Step-by-Step Procedure For the first step, you will be moving all your objects that you require to a Transport, creating a Transport of Copies to be released that contains all the objects necessary to import the working service into the upgraded system. Then finally, importing that transports into the newer system and testing the service. 4.1 Saving the Objects to a transport 1. Logon to the SP4 NPL system as user developer and go to transaction se80 2. Create a customer friendly package December

8 3. Press enter and you will be prompted to create the package if it does not exist already. 4. Fill in the required Short Description field and press the ok button 5. When the Prompt for Workbench request appears, create a new request, so only your objects that you want to move are separated out. December

9 6. Enter a Short Description and press Save 7. Your Package should be put to this new request number. December

10 8. Once saved, go to the Gateway Service Builder transaction segw. December

11 9. Open the project that you wish to upgrade 10. Making sure you are in Edit mode, select the project and from the top menu bar select Goto -> Object Directory Entry 11. Replace $TMP package with your newly created one. December

12 12. Put this on the same transport as the Package that you created earlier 13. Expand the node Generated Objects 14. The classes are what we will be concerned with now and must be moved from $TMP December

13 15. Go back to the SAP ABAP workbench, transaction se80, select Local Objects for the user that created this service. 16. Expand the Class Library node and Classes December

14 ... How-To Transport Gateway services to Newer Trial Version 17. Right click on each of the classes that you need to reassign to the new package. From the right click menu, go to Other Function -> Change Package Assignment 18. Save these to the same transport as previously. Do this for each Class that was listed in the Generated Objects list from the Service Builder 4.2 Rebuilding Generated Service 1. For the model and service that were created with when you generated the project from the service builder, we have to manual delete then rebuild to put them on the new transport. We first delete everything, then rebuild in the reverse order. 2. Go to transaction /iwnfd/maint_service December

15 3. Find your service and select it so that it shows up in the ICF Nodes and System Alias windows 4. Delete the System Alias 5. Then high light and delete the ICF Node December

16 6. Then delete the service itself 7. Saying yes to the warning, as we will be creating this again. December

17 8. To reassign the service and the model you need to manually delete then re-create them. Using the IMG from transaction spro or directly via the corresponding transaction codes. 9. Using transaction /iwbep/reg_service find the Technical Service Name and Service Version using F4 help and delete the service, the Model will be automatically be unassigned December

18 10. Next delete the model. Go to transaction /iwbep/reg_model 11. Delete the Technical Model name 12. Now that everything is clean we being re-creating it again, still in the Maintain Model transaction Enter the exact same Technical Model name and version that you just deleted and click Create December

19 13. Enter the Model Provider Class of the extension class that you previously moved to the transport. Description (when generated) is the same as the class. 14. Pressing the Save button you will be prompted to enter a package name, use the newly created one that you started with. 15. Press save and keep everything to the same transport. December

20 16. Next go to create the service and assign the model to that service. Via transaction /iwbep/reg_service 17. Enter in the Data Provider Class similar to the Model provider class as the previous step December

21 18. You must save before you can assign the Model to this service. 19. You can then assign the model December

22 20. Go back to transaction /iwfnd/maint_service to re-create and reactivate the service. Press the add service button 21. Enter the System Alias, in this case LOCAL and press enter to get a list of services. December

23 22. Click on the service that you want to transport and add it to the package December

24 ... How-To Transport Gateway services to Newer Trial Version 4.3 Create Final Transport 1. Now that everything that is needed is on transports, go to transaction se10 you can see your request should have similar objects as below December

25 2. From the Transport Organizer main screen click the create button 3. Select Transport of Copies and press ok December

26 4. Put in a Short Description and in the Target field enter NPL as the target system 5. Right click on the newly created transport of copies and select Include Objects. From the Object List from Request open up the possible entries 6. Leave the defaults and press the execute button December

27 7. Select the task that contains all the objects you want to move to the newer system. This is usually one number higher than the request that you have been saving too December

28 8. Your transport of copies should now also contain all of the objects that you have saved. 9. When you are finished adding objects to this transport, select it and press the release directly button. 10. If you get the warning that the objects cannot be locked, just continue. December

29 11. You are only creating a file that you will transport to the newer system. 12. Click refresh until the transport has finished. December

30 13. Log onto the Linux machine as user npladm, the files you need to save are located in the /usr/sap/trans/cofiles directory and /usr/sap/trans/data directory with files K9000<xx>.NPL and R9000<xx>.NPL respectively. 14. The simplest way to move these files is ing these two files to you using a web mail client e.g. using the installed Firefox browser. December

31 4.4 In the SP5 System 1. Logon to this system as npladm and retrieve the two files that you previously ed to yourself. 2. Make sure you place the K9000<xx>.NPL file in the /usr/sap/trans/cofiles directory and the R9000<xx>.NPL in the /usr/sap/trans/data directory. 3. Logon to the SAP GUI for this SP5 NPL system and go to transaction stms 4. This is the Transport Management System, click on the Import Overview button. 5. Double Click on the System NPL line December

32 6. In the top menu select Extras -> Other Request -> Add, a popup should appear choose the possible entries button 7. The transport that you put in the file system should be the only one that appears. 8. Select it, it doesn t hurt to check the Import Again option (in case the number has been previously used in the new system and there is some overlap). December

33 9. Click yes to attach to import queue 10. Select the line and click the import Request button. Ignore the short text if anything is written there. 11. Use 001 as the Target Client. December

34 12. The transport should be small enough to run Synchronously, otherwise you can leave it as Asynchronous. December

35 13. All options can be selected, since this is a new request it s probably overkill 14. Click yes to start the import December

36 15. Once transport is finished you can check the Transport Logs, warning are ok. December

37 16. You will need to activate the service again, go to transaction iwfnd/maint_service December

38 17. Find and select the service 18. From here you can also add the System Alias back to the system. December

39 19. Once saved, you can verify that everything is back using transaction segw and view the project in the service builder. December

40