Solution Manager Integration

Transcription

1 Valid for GWPAM SAP AG 1

2 Table of Contents Overview... 3 Prerequisites... 3 Integrating Solution Manager for GWPAM Applications... 3 Checking Logs Copyright SAP AG 2

3 Overview GWPAM provides capabilities to applications to enable end-to-end logging and tracing for easy troubleshooting. These features work seamlessly within the context of SAP Solution Manager and enables the IT admin to easily troubleshoot issues. The GWPAM project enables enterprise supportability via. This scenario typically happens when an end user reports an issue with the existing GWPAM project. The system administrator will install the SAP Client plugin tool on the client machine and trace the service call end to end. Prerequisites GWPAM installed in user machine A VSTO application installed in Microsoft Outlook SAP Client Plugin tool for end to end tracing (32-bit or 64-bit based on user machine). Copy to local folder structure. o o For 32 bit machine use SAP note to download SAP Client Plugin tool. For 64 bit machine use SAP note to download SAP Client Plugin tool. Integrating Solution Manager for GWPAM Applications To integrate Solution Manager for a GWPAM application follow the steps outlined below: 1. Navigate to the folder where SAP client plugin is copied and double click on plugin-starter-gui.exe. The End to End Trace Analysis Client Plug-In application opens 2. Select Microsoft Office Excel from the Application drop-down list. 3. Click Launch 2014 SAP AG 3

4 The Microsoft Excel application opens with the client plugin tool. 4. Enter the name for the folder where the Business Transaction XML is to be created 5. Enter the Solution Manager Host name in the field SMD Host (Optional) 6. Enter the Solution Manager Http Port in the field SMD HTTP Port (Optional) 7. Click on the Start Transaction button to begin the trace 2014 SAP AG 4

5 8. Start the normal GWPAM Excel operations, for example Bind Microsoft Excel with records from the SAP system. 9. As soon as the Bind operation is invoked, the SAP Client Plugin Tool will recognize the request 10. Once the Odata service call has completed a response will be recognized by the SAP Client Plugin Tool 2014 SAP AG 5

6 11. After receiving the Query response the SAP Client Plugin will update the recording 12. Select the Stop Transaction button o If the Solution Manager Host and Port were not maintained a dialog pop-up will appear asking the user to manually upload the transaction xml 2014 SAP AG 6

7 13. Click on Exit to close the SAP Client Tool 14. To locate the log folder, navigate to the folder where the SAP Client Plugin was started. 15. Open the Log folder 16. Open the folder with the name of Business Scenario specified while creating the template 2014 SAP AG 7

8 17. Open the Business Transaction xml in Internet Explorer, and search for the Request ID for the particular web service call 18. Logon to the Solution Manager Work Center and navigate to Root Cause Analysis End to End Analysis 2014 SAP AG 8

9 19. Highlight the appropriate system and select the Trace Analysis button 20. If the SMD Host and Port were not maintained when the SAP Client Plug-in GUI was started you can manually upload the Business Transaction xml by selecting the Browse button and navigating to the folder where the SAP Client Plug-in GUI was started. 21. Open the Log folder and select the Business Transaction xml and then select the select Open' 2014 SAP AG 9

10 22. Select the Upload button to complete the process 23. Once the upload is successful, select the Trace Analysis tab to display the list. 24. Select your Business Transaction xml from the list. 25. The screen at the bottom shows various steps that were carried out (typically each request) 2014 SAP AG 10

11 26. Click on Display button 27. Monitor the HTTP tabs and get detailed information on trace analysis o A summary screen would come up detailing how the request and response took place o Navigate to HTTP Message Table for more information 2014 SAP AG 11

12 Checking Logs Checking logs in the client machine and the Gateway system can be achieved by using the same Request ID found in the Business Transaction xml 1. From the client machine navigate to the folder where the GWPAM Logs are located (the path will be provided in the GWPAM configuration file 2014 SAP AG 12

13 2. Open the log file and search for the Request ID in the log and check the logs below the line for analysis 3. The log analysis of both the client and NW Gateway server can be achieved via the Request ID 4. Log on to the NW Gateway system and go to transaction SLG1 and paste the Request ID into the External ID field and execute 2014 SAP AG 13

14 Copyright Copyright 2014 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 Oracle Corporation. JavaScript is a registered trademark of Oracle Corporation, 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 SAP AG 14