sap user interface (ui) logging logging of web service and ...€¦ · pursue any course of...
TRANSCRIPT
SAP User Interface (UI) LoggingLogging of Web Service and RFC/BAPISAP Custom DevelopmentOctober 2014
© 2014 SAP SE. All rights reserved. 2
Disclaimer
The information in this presentation is confidential and proprietary to SAP and may not bedisclosed without the permission of SAP. This presentation is not subject to your licenseagreement or any other service or subscription agreement with SAP. SAP has no obligation topursue any course of business outlined in this document or any related presentation, or todevelop or release any functionality mentioned therein. This document, or any relatedpresentation about SAP’s strategy and possible future developments, directions, andfunctionality of products and/or platforms, are all subject to change and may be changed bySAP at any time for any reason without notice. The information in this document is not acommitment, promise, or legal obligation to deliver any material, code, or functionality. Thisdocument is provided without a warranty of any kind, either express or implied, including butnot limited to, the implied warranties of merchantability, fitness for a particular purpose, ornon-infringement. This document is for informational purposes and may not be incorporatedinto a contract. SAP assumes no responsibility for errors or omissions in this document,except if such damages were caused by SAP intentionally or grossly negligent.All forward-looking statements are subject to various risks and uncertainties that could causeactual results to differ materially from expectations. Readers are cautioned not to place unduereliance on these forward-looking statements, which speak only as of their dates, and theyshould not be relied upon in making purchasing decisions.
© 2014 SAP SE. All rights reserved. 3
RCS UI LoggingData leakage: the insider threat
© 2014 SAP SE. All rights reserved. 4
AGENDA
1. General Processing
2. Web Service Logging
3. RFC/BAPI Logging
© 2014 SAP SE. All rights reserved. 5
Architecture Overview
Straightforward high-performance solution, tailored to SAP applicationsServer-side logging - log entry is written with each client-server roundtripLog records are written to provided log service
© 2014 SAP SE. All rights reserved. 6
AGENDA
1. General Processing
2. Web Service Logging
3. RFC/BAPI Logging
© 2014 SAP SE. All rights reserved. 7
WS
Laye
r
Web Service Logging Processing
Enhancing the methods which are used from the different types of Web Services(RFC, Web Services, XI)
Frontend Tools
Call ofWeb Service
ExternalRepository
SAP BackendWS Framework
Request
Response
Business Engine
Legend New Enhancement
Import / Exportdata traffic
Temporary Log(Asynchronous)transfer toExternal Repository
OLA
PP
roce
ssor
WS
Laye
r
© 2014 SAP SE. All rights reserved. 8
Web Service Logging can be enabled on service definition level
Web Service Logging
Web Service Input (admin, parameter…)Web Service Output
What is logged?
Name-Value Pairs (with XML as value)
Output Format
No additional field mapping or filtering (only BAdI during logging)
Mapping and Filter (Transfer to External Repository)
Web Service Logging
© 2014 SAP SE. All rights reserved. 9
Web Service Demo - Configuration
Use IMG (“uniform configuration”) in order to maintain the customizing tableEnable logging functionality :
For Service Definition
© 2014 SAP SE. All rights reserved. 10
Web Service Demo - Input data logging
Input logging while executing the services
© 2014 SAP SE. All rights reserved. 11
Web Service Demo - Output data logging
Output result
© 2014 SAP SE. All rights reserved. 12
AGENDA
1. General Processing
2. Web Service Logging
3. RFC/BAPI Logging
© 2014 SAP SE. All rights reserved. 13
WS
Laye
r
RFC/BAPI Logging Processing
Enhancing the each RFC function module with a logging hook
Frontend/Backend Tools
Call of RFC
ExternalRepository
SAP Backend
Request
Response
Business Engine
Legend New Enhancement
Import / Exportdata traffic
Temporary Log(Asynchronous)transfer toExternal Repository
OLA
PP
roce
ssor
© 2014 SAP SE. All rights reserved. 14
RFC/BAPI Logging can be enabled on Function Module level
Web Service Logging
RFC/BAPI Input (admin, parameter…)RFC/BAPI Output
What is logged?
Name-Value Pairs (with XML as value)
Output Format
No additional field mapping or filtering (only BAdI during logging)
Mapping and Filter (Transfer to External Repository)
RFC/BAPI Logging
© 2014 SAP SE. All rights reserved. 15
RFC/BAPI Demo - Configuration
Use IMG (“uniform configuration”) in order to maintain the customizing tableEnable logging functionality :
For function module (remote-enabled)For single parameters
© 2014 SAP SE. All rights reserved. 16
RFC/BAPI Demo – Logging Hooks
Generated implicit enhancements with coding individual to the function module
© 2014 SAP SE. All rights reserved. 17
RFC/BAPI Demo - Input data logging
Input parameter
© 2014 SAP SE. All rights reserved. 18
RFC/BAPI Demo - Output data logging
Output result
© 2014 SAP SE. All rights reserved. 19
Tobias KellerProduct Owner
SAP SE, Custom Development
T +49 6227-7-74995
Your Contact – RCS UI Logging
Martin LoitzTechnical Product Owner
SAP SE, Custom Development
T +49 6227-7-48810
Visit our SAP UI Logging channel on SCN:http://scn.sap.com/community/ui-logging…your one-shop-stop for product information,release news, Q&A, and more
© 2014 SAP SE. All rights reserved. 20
No part of this publication may be reproduced or transmitted in any form or for anypurpose without the express permission of SAP SE. The information containedherein may be changed without prior notice.Some software products marketed by SAP SE and its distributors containproprietary software components of other software vendors.Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks ofMicrosoft 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/390Parallel 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 IBMCorporation.Linux is the registered trademark of Linus Torvalds in the U.S. and othercountries.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks orregistered trademarks of Adobe Systems Incorporated in the United States and/orother countries.Oracle and Java are registered trademarks of Oracle and/or its affiliates.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, andMultiWin 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.
© 2014 SAP SE. All rights reserved.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjectsExplorer, StreamWork, and other SAP products and services mentioned herein aswell as their respective logos are trademarks or registered trademarks of SAP SEin Germany and other countries.
Business Objects and the Business Objects logo, BusinessObjects, CrystalReports, Crystal Decisions, Web Intelligence, Xcelsius, and other BusinessObjects products and services mentioned herein as well as their respective logosare trademarks or registered trademarks of Business Objects Software Ltd.Business Objects is anSAP company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and otherSybase products and services mentioned herein as well as their respective logosare trademarks or registered trademarks of Sybase, Inc. Sybase is an SAPcompany.
All other product and service names mentioned are the trademarks of theirrespective companies. Data contained in this document serves informationalpurposes only. National product specifications may vary.
The information in this document is proprietary to SAP. No part of this documentmay be reproduced, copied, or transmitted in any form or for any purpose withoutthe express prior written permission of SAP SE.