+ All Categories
Home > Documents > RCS UI Logging - SAP UI Logging...RCS UI Logging Sample Screen Shots from SAP GUI (on SAP Test...

RCS UI Logging - SAP UI Logging...RCS UI Logging Sample Screen Shots from SAP GUI (on SAP Test...

Date post: 29-Mar-2020
Category:
Upload: others
View: 50 times
Download: 0 times
Share this document with a friend
10
RCS UI Logging Sample Screen Shots from SAP GUI (on SAP Test system) Tobias Keller, Product Owner, UI Logging and UI Masking (UI Field Security) September 2014 SAP SE
Transcript

RCS UI LoggingSample Screen Shots from SAP GUI(on SAP Test system)Tobias Keller, Product Owner, UI Logging and UI Masking (UI Field Security)September 2014SAP SE

© 2014 SAP SE. All rights reserved. 2Public

Overview: IMG structure for UIlogging

• Under node for SAP NetWeaver• One node for common settings

(relevant for all subscribed UILchannels)

• One node for each of thesubscribed (installed) UILchannels, with specific configoptions

• Node for BadIs to enable morecomplex business logic as towhat the logging functionalitydoes

[This slide deck covers merely thetwo main configuration tables]

RCS UI LoggingSample screen shots: Configuration

© 2014 SAP SE. All rights reserved. 3Public

Step 1: configure scope forlogging

• Separate tables per channel (UItechnology to log – SAP GUI,WebDynpro, CRM WebUI…)

• Either maintain transaction codesto be logged for a quick setup or

• Set up configuration on view/fieldlevel for a more granulardetermination of what is logged(option to determine whether theconfigured elements areexcluded or included)

RCS UI LoggingSample screen shots: Configuration

© 2014 SAP SE. All rights reserved. 4Public

Step 2: maintain which usersare to be logged (or not)

• Get and maintain a list of allusers that should be evaluated byUI Logging

• Maintain configuration whetherthese entries are “positive”(included and to be logged) or“negative” (excluded fromlogging)

RCS UI LoggingSample screen shots: Configuration

© 2014 SAP SE. All rights reserved. 5Public

UI Logging example

• If a user enters a protectedtransaction (e.g. PA20, PA30 forHR data, or SE16n), this isalready logged.

• Subsequently, the user requestsfor data to be displayed, e.g.salary data (infotype 8) for aparticular user.

• These moves are being logged –see the next page to understandhow.

RCS UI LoggingSample screen shots: normal system user steps

© 2014 SAP SE. All rights reserved. 6Public

Display the log

• In temporary log (for most recentdata) or in repository (the actual logfile).

• Each roundtrip from UI Server(database ) UI is logged as onedata file.

• Log Viewing options: structured ortext based (the actual log)

• The log contains multiple sections:general data, header, input, andoutput.

• header/input data: it is possible tounderstand the requests from agiven user (including UI functions,e.g. export, print)

• The output section is a snapshot ofthe exact data handed over to theuser

RCS UI LoggingSample screen shots: UIL admin tools

© 2014 SAP SE. All rights reserved. 7Public

Analyze the logged data• Powerful set of filters to narrow

down to the most relevantinformation

• Search the complete log over allchannels, or only specificchannels (and with varyingsettings/filters)

• User can set/get variants forcomplex filter settings

RCS UI LoggingSample screen shots: UIL admin tools

© 2014 SAP SE. All rights reserved. 8Public

Sample functionality: systemalert in case of critical dataaccess

• Sample only – not included instandard functionality

• Can be offered based on specificcustomer requirements

• Immediate system reaction forcritical fields or in case of othertriggering events (rules based)

• More complex rules could bevariants created with the LogAnalyser)

• Reports on a periodic base(grasp large scale access,uncommon accesses by a useretc.)

RCS UI LoggingSample screen shots: UIL admin tools

© 2014 SAP SE. All rights reserved. 9Public

Tobias KellerProduct Owner

SAP SE, Custom DevelopmentDietmar-Hopp-Allee 1669190 Walldorf

T +49 6227-7-74995

E [email protected]

Contact – RCS UI Logging

Martin LoitzTechnical Product Owner

SAP SE, Custom DevelopmentDietmar-Hopp-Allee 1669190 Walldorf

T +49 6227-7-48810

E [email protected]

Visit our SAP UI Logging channel on SCN:http://scn.sap.com/community/ui-loggingYour one-shop-stop for product information, release news, Q&A, and more

© 2014 SAP SE. All rights reserved. 10Public

© 2014 SAP SEAll 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 SE or anSAP affiliate company.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE(or an SAP affiliate company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additionaltrademark information and notices.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind,and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE orSAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products andservices, if any. Nothing herein should be construed as constituting an additional warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any relatedpresentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliatedcompanies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may bechanged by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment,promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertaintiesthat could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-lookingstatements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.


Recommended