Guide - Setup For SAP NetWeaver 740 SP5
Guide - Setup For SAP NetWeaver 740 SP5
Overview
July 2014 Public
Disclaimer
This presentation outlines our general product direction and should not be relied on in making a
purchase decision. This presentation is not subject to your license agreement or any other agreement
with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or to
develop or release any functionality mentioned in this presentation. This presentation and SAP's
strategy and possible future developments are subject to change and may be changed by SAP at any
time for any reason without notice. This document is provided 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 assumes no responsibility for errors or omissions in this
document, except if such damages were caused by SAP intentionally or grossly negligent.
Basic Concepts
Summary
High-performing,
C for local high load scenarios,
across all ABAP Releases,
close integration into ABAP
RFC-Based Connectivity
Facts:
Most SAP ERP customers run just a limited number of the business
scenarios for which they need to expose some RFMs
A lot of RFMs are only used to parallelize within a system.
Solution
Find out which RFMs need to be exposed for the scenarios of a
customer.
Block the access to all other RFMs.
Expose only and exactly those RFMs a customer needs to run their business scenarios.
A typical SAP
38000 RFMs in customer only needs
to expose a few
SAP ERP (incl.
hundred RFMs for
SAP NetWeaver) their business
scenarios
…
R R R R R R R R R R R
F F F F F F F F F F F
M M M M M M M M M M M
1 2 3 4 5 6 7 8 9 .
10 11
RFM in no
CA?
No Access
yes
yes Access to
RFM
1. Set the UCON profile parameter UCON/RFC/ACTIVE to 1 to enable UCON runtime checks for RFMs in the
final phase.
2. Run the UCON setup to generate a default communication assembly (CA) and other required entities.
4. Schedule the batch job SAP_UCON_MANAGEMENT that selects and persists the RFC statistic records
required by the UCON phase tool on the database.
Logging of RFMs
Evaluation/ Runtime checks
called from
outside Simulation active
Logging of RFMs
Evaluation/ RuntimeChecks
Runtime check
called from
outside
Simulation active active
At the end of phase 1, choose the RFMs you need and assign them
to the Default CA:
•Based on the statistical records, you decide which RFMs
should be accessed from outside and assign them to the CA
Logging
Logging of ofRFMs
RFMs
called
Evaluation/ Runtimechecks
Runtime check
Checks
called from
from
outside
outside Simulation
simulation active active
Check whether you have protected the right RFMs and make
necessary corrections
Logging of
Logging ofRFMs
RFMs
called
Evaluation/ Runtimechecks
Runtime check
Checks
called from
from
outside
outside
Simulation
simulation active active
Access to RFMs
UCON
runtime
checks
S_RFC
checks
Access to RFMs
Access to RFMs
UCON
runtime
checks
S_RFC
checks
Access to RFMs
Check-Active Phase
100 ++
Default CA
SAP Business Suite
Check-active Phase
Protected/
Development blocked
RFMs
Default Communication
Assembly
Exposed RFMs
Check-active phase
Development
Check-active phase
Access blocked
UCON protection
Access allowed
Logging phase
Evaluation phase
Access blocked
UCON protection
Access allowed
Logging phase
Evaluation phase
Check-active phase
Access blocked
UCON protection
Access allowed
Blocked RFMs
Blocked RFMs from initial UCON set-up from other, new
transports or
installations
Default CA
SAP Business Suite
PROD
Authorizations and system change options in
Productive Systems are not sufficient for UCON Assignment of relevant RFMs
Operations to default CA and UCON
phases
Collection UCON
of RFC call Phase
statistics Tool
and UCON
protection
DEV PROD
Assignment of Delegate
UCON Collection
relevant RFMs
of RFC call
to default CA operations
statistics
and UCON to DEV and UCON
phases
protection
UCON UCON
Phase Phase
Tool Tool
Slide 32
DEV PROD
DEV PROD
DEV PROD
3 R3Trans
UCON Phase and CA assignment UCON
Phase Tool of RFMs Phase Tool
DEV PROD
Assignment of
Collection
relevant RFMs
of RFC call
to default CA
statistics
and UCON
and UCON
phases
protection
UCON UCON
Phase RFC call Phase
Tool statistics Tool
Phase and CA
assignment of RFMs
• The UCON framework offers a simple, straightforward approach for enhancing the security of
your RFCs. It allows you to minimize the number of RFMs on ABAP-based servers exposed
to other clients and systems, reducing the available attack surface in your RFC
communications.
• The UCON phase tool guides and supports the administrator in the three-step setup and the
three-phased process.
• UCON covers new function modules entering the system via Support Packages,
Enhancement Packages, transports, or new developments.
• UCON is fully enabled for life-cycle management to ensure consistent RFC security
across your system landscape.
Community Network
Get more information, videos and updates
Unified Connectivity (UCON)
http://scn.sap.com/docs/DOC-53844
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 an
SAP 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 additional trademark
information and notices.
Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.
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 or
SAP affiliate company 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.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or
release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future
developments, products, and/or platform directions and functionality are all subject to change and may be changed 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 uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue
reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.