Upload
krishanu-ray
View
91
Download
21
Embed Size (px)
DESCRIPTION
Master Guide for SAP PI 7.1
Citation preview
Master GuideSAP NetWeaverreg Process Integration 71
Target Audience System administrators Technology consultants
PUBLICDocument version 17 ndash 2011-04-15Material number 50086539
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2011 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 noticeSome 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 CorporationIBM 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 zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer 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 countriesBusiness 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 in the United States and in other countriesSybase 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 companyAll 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 varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) 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
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
256 PUBLIC 2011-04-15
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2011-04-15 PUBLIC 356
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
456 PUBLIC 2011-04-15
Document History
CAUTION
Before you start the implementation make sure you have the latest version of this document
You can find the latest version on SAP Service Marketplace httpservicesapcom
instguides
The following table provides an overview on the most important document changes
Version Date Description
10 2007-12-07 First version
11 2008-02-05 Changes to System Landscape Directory section Minor changes
12 2008-04-22 Major revision of Shared Services section
13 2008-05-29 Information about dedicated PI system updated
14 2008-12-12 Restructuring of content according to use case concept Information about SAP enhancement package 1 for SAP NetWeaver PI 71 added
15 2009-03-19 Minor changes (mainly language corrections)
16 2009-03-20 Minor error corrections
17 2011-04-15 Section SAP Enhancement Package 1 for SAP NetWeaver PI 71 updated (Software Update Manager replaces SAP Enhancement Package Installer)
Section Process Sequence Installation of Enhancement Package 1 on an Existing SAP NetWeaver PI 71 system added
Section Maintaining System Landscape Information added Further minor changes
2011-04-15 PUBLIC 556
Table of Contents
Chapter 1 Introduction 9
Chapter 2 Before You Start 11
21 SAP Notes 11
22 More Information 11
23 Accessing the SAP Library 12
Chapter 3 SAP NetWeaver PI Overview 13
31 Installable Software Units 15
311 Systems with Usage Types 16
312 Standalone Engines 19
313 Clients 21
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration
71 23
Chapter 4 SOA-Based Integration Use Case 25
41 Overview 25
42 System Landscape 25
43 Implementation Sequence 27
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP
Netweaver PI 71 System 28
Chapter 5 System Landscape 33
51 Planning Your System Landscape 33
52 Shared Services 35
521 Use Cases 37
5211 End-to-End Solution Operations 37
5212 Support Infrastructure 38
5213 Collection of Landscape Data 39
5214 Authentication and Single Sign-On 39
5215 Integrated User and Access Management 39
522 Examples for the Overall System Landscape of Shared Services 40
656 PUBLIC 2011-04-15
523 Feature Details 42
5231 SAP Solution Manager 42
5232 Solution Manager Diagnostics 43
5233 System Landscape Directory 43
Chapter A Appendix 47
A1 Maintaining System Landscape Information 47
Chapter B Reference 51
B1 The Main SAP Documentation Types 51
B2 List of Documentation 51
2011-04-15 PUBLIC 756
This page is left blank for documents that are printed on both sides
1 Introduction
This Master Guide provides you with a central starting point for the technical implementation of SAP
NetWeaverreg Process Integration (SAP NetWeaver PI) It also contains information about enhancement
package 1 for SAP NetWeaver Process Integration 71
SAP NetWeaver PI 71 is based on an established architecture for realizing cross-system business processes
and supporting an service-oriented architecture (SOA) The focus is on the service-based integration
of applications
Structure of the Master Guide
The Master Guide consists of the following sections
Introduction
Contains an introduction to this guide
Before You Start
Contains information about this document important things which you need to know before you
start and information on how to access the SAP Library
SAP NetWeaver Overview
Describes the building blocks of SAP NetWeaver PI
SOA-Based Integration Use Case
Introduces the use case and explains how to install it
System Landscape
Contains information about how to install your system landscape
Reference
Contains information about the overall documentation concept for SAP systems
CAUTION
Make sure you have the latest version of the Master Guide by checking SAP Service Marketplace
immediately before starting the installation
The Master Guide is regularly updated on SAP Service Marketplace at http
servicesapcominstallnwpi71 Planning
Constraints
The business scenarios that are presented here serve as examples of how you can use SAP software in
your company The business scenarios are intended only as models and do not necessarily run the way
they are described here in your customer-specific system landscape Check your requirements and
systems to determine whether these scenarios can be used productively at your site Furthermore we
1 Introduction
2011-04-15 PUBLIC 956
recommend that you test these scenarios thoroughly in your test systems to ensure that they are
complete and free of errors before going live
1 Introduction
1056 PUBLIC 2011-04-15
2 Before You Start
21 SAP Notes
You must read the following SAP Notes before you use this Master Guide and implement SAP NetWeaver
Make sure that you have the up-to-date version of each SAP Note which you can find on SAP Service
Marketplace at httpservicesapcomnotes
NOTE
The SAP Notes related to SAP NetWeaver PI 71 are also listed on SAP Service Marketplace at
httpservicesapcomsapnotesnwpi71
List of Important SAP Notes
SAP Note Number Title Description
1004107 Release Restrictions for SAP NetWeaver PI 71
Some restrictions apply to the productive use of SAP NetWeaver PI 71 These are documented in this SAP Note
1247043 Release Restrictions for SAP EHP1 for SAP NetWeaver PI 71
Some restrictions apply to the productive use of enhancement package 1 for SAP NetWeaver PI 71 These are documented in this SAP Note
22 More Information
The following table contains links to information available on SAP Service Marketplace or in the SAP
Library which is important for implementing SAP NetWeaver
Content Location on SAP Service Marketplace or in SAP Library
The latest version of the installation and upgrade guides for SAP NetWeaver Process Integration
httpservicesapcominstguidesnwpi71
Information about supported platforms (operating systems databases browsers) for all SAP NetWeaver components
httpservicesapcomplatforms Product Availability Matrix
Sizing of SAP NetWeaver httpservicesapcomsizing
Information about security SAP Security Guide See the SAP Library [page 12] at Adminitstratoracutes Guide Security Guide
Information about the technical operation of SAP NetWeaver
Technical Operations Manual See the SAP Library [page 12] at Adminitstratoracutes Guide Technical Operations for SAP NetWeaver
2 Before You Start
21 SAP Notes
2011-04-15 PUBLIC 1156
Content Location on SAP Service Marketplace or in SAP Library
Information about SAP NetWeaver PI Support Package Stacks
httpservicesapcomnetweaver SAP NetWeaver PI 71- Release-Specific Information Support Package Stacks Information
Information about installing SAP NetWeaver Support Package Stacks
httpservicesapcomMaintenanceNWPI71
Support Package Stack Guide ndash SAP NetWeaver
23 Accessing the SAP Library
For more information about SAP NetWeaver Process Integration access the SAP Library from any of
the following
SAP Help Portal at httphelpsapcomNWPI71 SAP NetWeaver Process Integration 71 Library
ltLanguagegt SAP NetWeaver Process Integration Library
CAUTION
The SAP Help Portal contains the latest version of the SAP Library Therefore we recommend
that you use this channel to access the SAP Library
An SAP system if you have installed the online documentation Choose Help SAP Library
The browser starts
The help files on the online documentation CDs or DVDs
If you want to view the help files in HTMLHelp format from the online documentation CDs or
DVDs you need a PC running Microsoft Windows to install the HTMLHelp Viewer
2 Before You Start
23 Accessing the SAP Library
1256 PUBLIC 2011-04-15
3 SAP NetWeaver PI Overview
Introduction
SAP NetWeaver PI 71 is part of the SAP NetWeaver technology platform The complete offering of the
SAP NetWeaver technology platform is visualized in the SAP NetWeaver technology map which you
can access at httpsdnsapcomnetweaver SAP NetWeaver at a Glance The technology map
enables you to drill down from top-level technology areas (for example Lifecycle Management) to
individual capabilities (for example Administration Monitoring and so on)
SAP NetWeaver PI includes the following capabilities
Repository-based Modeling and Design
Service Bus-based Integration
SOA Management
A different view is introduced by the end-to-end use case concept This concept offers an
implementation view on SAP NetWeaver to structure and facilitate your implementation
A use cases is a process that typically involves several SAP NetWeaver capabilities It is not limited to a
single component or capability A use case guides you through the different phases of your
implementation project ndash from information through installation to the configuration phase This
implies that a uses case addresses several user roles administrator power user and end user
This document describes the SOA-based integration use case
Architecture Principals
The architecture of SAP NetWeaver Process Integration 71 (SAP NetWeaver PI 71) is based on an
established architecture for realizing cross-system business processes and is a further development of
lower releases (SAP NetWeaver 70 usage type Process Integration and SAP XI 30 as part of SAP
NetWeaver 2004) SAP NetWeaver PI 71 plays an important role in supporting an service-oriented
architecture (SOA) The focus is on the service-based integration of applications
SAP NetWeaver PI is based on general standards so as to enable 3rd-party systems to be integrated At
the center of SAP NetWeaver PI is an XML-based communication that uses HTTP (Hyper Text Transfer
Protocol) Irrespective of the scenario used the application-specific contents are transferred in messages
in user-defined XML (eXtensible Markup Language) from the sender to the receiver either via the
Integration Server or directly between the systems involved
The following figure gives an overview of the key capabilities of SAP NetWeaver Process Integration
3 SAP NetWeaver PI Overview
2011-04-15 PUBLIC 1356
Figure 1 SAP NetWeaver PI Key Capabilities Overview
SAP NetWeaver Process Integration 71 enables the integration of the applications of the following
communication parties
B2B Party Any business partners that want to integrate their application with other applications
outside their own system landscape Scenarios that require industry standards are supported as
well as any scenarios that do not adhere to a particular industry standard
SAP Applications that run on SAP systems This includes the processing of events by using the
Business Activity Monitoring (BAM) infrastructure
3rd-Party Application Applications from 3rd-party providers within one system landscape for
example database or file-system-based
3rd-Party Middleware Middleware systems from 3rd-party providers that are required for the
integration of applications within a company and across company boundaries
SAP NetWeaver PI also supports internal company scenarios and cross-company scenarios It enables
you to connect systems from different vendors (non-SAP and SAP) in different versions and
implemented in different programming languages (Java ABAP and so on) to each other Like the rest
of the SAP NetWeaver platform SAP NetWeaver PI is based on an open architecture uses open standards
(in particular those from the XML and Java environments) and offers those services that are essential
in a heterogeneous and complex system landscape
To enable end-to-end SOA development SAP NetWeaver Process Integration 71 offers a Universal
Description Discovery and Integration (UDDI) v3-based Services Registry where providers can publish
service endpoints definitions and associated metadata and consumers can discover the appropriate
services for their scenarios The Services Registry provides capabilities for classifying and browsing
3 SAP NetWeaver PI Overview
1456 PUBLIC 2011-04-15
services using semantic-rich classification systems The Services Registry is part of Application Server
Java (AS Java)
31 Installable Software Units
SAP NetWeaver comprises the following three types of installable software units
Systems that are configured for a specific purpose as indicated by one or more usage types
Standalone engines that provide one specific (server) function in combination with one or more
SAP NetWeaver PI systems
Clients used by (many) people from their local front-end PC to access functions offered by systems
of SAP NetWeaver PI or standalone engines in the system landscape
In the following sections you can find more details about the software units The figure below provides
and overview of the software units
Figure 2 Installable Software Units for SAP NetWeaver PI
For this and other figures in this guide the following legend applies
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1556
Figure 3 Legend
311 Systems with Usage Types
SAP systems are the main building blocks of SAP NetWeaver They are identified by unique SAP system
IDs (SAPSIDs) and configured for a certain purpose as indicated by usage types Usage types have the
following characteristics
They are a structuring element for SAP software on a technical level
Usage Types determine the intended purpose of a system and the role it plays in a given (distributed)
use case
They are realized by installing and configuring a collection of software components
They allow a logical view of the technology platform SAP NetWeaver PI
A usage type may require other usage types in the same system to operate
They can also be run in the same system together with other usage types that are not a prerequisite
How SAP NetWeaver Systems are Used
The following sections describe the usage types and their dependencies for SAP NetWeaver PI
Application Server ABAP (AS ABAP)
Purpose
AS ABAP is used to provide the ABAP foundation of SAP NetWeaver PI
Application Server ABAP provides a complete development and runtime environment for ABAP-based
applications It is optimized for the development of highly scalable business applications The ABAP
development and runtime environment makes it possible to develop complex business applications
3 SAP NetWeaver PI Overview
31 Installable Software Units
1656 PUBLIC 2011-04-15
without having to worry explicitly about technical details such as process or memory administration
multi-user capability database connections or similar issues These are provided in the basis services or
are integrated directly in the ABAP runtime The application development is similarly independent of
the underlying platform The application server decouples the application coding completely from the
operating system and database that are used
Dependencies
AS ABAP can be combined optionally with other usage types in one system
Application Server Java (AS Java)
Purpose
AS Java is used to provide the Java foundation of SAP NetWeaver PI using the Java Engine a Java EE-
compliant application server for running enterprise applications In addition to the pure Java EE
standard technologies the Java Engine implements complementary technologies such as Web Dynpro
or Web Services that are targeted at supporting large-scale real-business application development
projects
Dependencies
AS Java can be combined optionally with other usage types in one system
Process Integration (PI)
Purpose
PI consists of core components that model design automate and integrate processes in one or more
application systems For the integration of internal and cross-company processes PI is used to
incorporate all the functions of what was formerly known as Exchange Infrastructure (XI) In addition
PI contains core components for Business Process Management for application-embedded and
application-unbounded processes
The Advanced Adapter Engine is also part of usage type PI You use Advanced Adapter Engine to connect
to SAP systems (RFC adapter) and external systems You use the various adapters in Advanced Adapter
Engine to convert XML- and HTTP-based messages to the specific protocol and format required by
these systems and the other way around You can use the Advanced Adapter Engine that is part of
your PI system as a central Advanced Adapter Engine Optionally (for performance reasons) you can
install a non-central Advanced Adapter Engine [page 19] separately as a system with AS Java and parts of the
usage type PI on a separate host
Dependencies
PI requires AS ABAP and AS Java as prerequisites in the same system
For installing PI it is mandatory to have a dedicated PI system This applies to development quality
and production landscapes It is a prerequisite that no other system in your system landscape has a
higher release and enhancement package level than the PI system If you want to upgrade or install an
application in your system landscape you first have to make sure that the current release and
enhancement package level of the PI system is on the same level - if required you have to upgrade the
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1756
PI system first to the new or a higher release In a dedicated PI system this can be accomplished with a
minimum of downtime Also the PI system would not be affected by the downtime of other usage
types running in the same system
Configuration of Systems with Usage Types
Configuration information is available in the installation guides the configuration wizard and SAP
Solution Manager
In the Installation Guide ndash SAP NetWeaver PI 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt you find
initial technical configuration tasks This guide also informs you about how you can run the
configuration wizard and how you can access the configuration information in SAP Solution
Manager
For certain usage types configuration tasks can be applied by the configuration wizard after the
installation To do this you start the configuration wizard from SAP NetWeaver Administrator
The configuration steps for systems with usage types required for an use case are accessible through
SAP Solution Manager
To be able to use SAP Solution Manager for the configuration tasks you have to import the latest
SAP Solution Manager Implementation Content (Add-On ST-ICO) that is available for your SAP
Solution Manager release For more information see SAP Note 631042 (Release strategy for Implementation
Content (ST-ICO))
SAP Solution Manager Implementation Content is available on SAP Service Marketplace at
httpservicesapcomswdc Installations amp Upgrades Entry by Application Component SAP
Technology Components SAP Solution Manager ltReleasegt Content ST-ICO
In SAP Solution Manager you create a project and a project structure In the configuration phase
you select configuration structures with pre-delivered SAP content for your project You can find
the following different types of configuration tasks in SAP Solution Manager
Mandatory configuration tasks All configuration tasks that are mandatory for the standalone
engine or usage type
Optional configuration tasks Configuration tasks for areas where customers need to decide
if they want to use these functions (for example high availability or security settings)
Additional functions ndash configuration tasks Configuration tasks for functional units that are
used in certain use cases only
A marked checkbox in front of the configuration tasks indicates those configuration tasks that are
relevant for the use case you have chosen To configure ABAP systems SAP Solution Manager
offers executable configuration files (IMG activities)
For information about using SAP Solution Manager Content and creating a configuration guide
see the following documentation
httphelpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Implementing
and Upgrading SAP Solutions Configuration
3 SAP NetWeaver PI Overview
31 Installable Software Units
1856 PUBLIC 2011-04-15
How to Create a Configuration Guide using SAP Solution Manager available at http
servicesapcomsolutionmanager Media Library How-To Documents
Restrictions for Systems with Multiple Usage Types
If you have one system with multiple usage types be aware that we do not provide standard tools
to separate these usage types and distribute them to multiple systems at a later stage For example
if you have a system with usage types A and B you are not able to migrate it with SAP standard
tools into two systems one with usage type A only and the other with usage type B only
In addition we do not provide standard tools to merge multiple systems with different usage types
into one system with multiple usage types at a later stage
If you want to perform these tasks you require specific project support
The following figure shows that SAP standard system copy and migration tools do not support
you in separating or merging systems with usage types
Figure 4 No Support for Merging or Separating Systems with Usage Types
Although you can use one system for multiple usage types client restrictions apply for usage type
PI PI requires a dedicated client due to special PI requirements concerning the client pipeline
Whereas application client pipelines only send and receive messages the central PI pipeline can
also map messages to different formats before sending them
312 Standalone Engines
Standalone engines of SAP NetWeaver are additional installable software units They do not work as
full-blown systems of SAP NetWeaver but as standalone engines that provide a specific (server) function
in combination with one or more SAP NetWeaver systems
Standalone engines are not part of a usage type They do not run on AS ABAP or AS Java
The standalone engines that are available for SAP NetWeaver Process Integration are described in the
following
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1956
Gateway
It is possible to install an SAP instance of an SAP NetWeaver system based exclusively on a standalone
gateway This type of instance does not contain normal work process types (dialog background update
enqueue or spool) Only the gateway process (gwrd) is started If there is an SNA connection to an R
2 system gateway work processes (gwwp) are also started
SAP Conversion Agent by Informatica
SAP Conversion Agent by Informatica is a data conversion tool that enables you to create interfaces
between any data formats and XML-based systems SAP Conversion Agent can convert unstructured
semi-structured and structured formats to XML and the other way around The Conversion Agent
comprises the Conversion Agent Studio and the Conversion Agent Engine In the Conversion Agent
Studio you can develop and configure data conversions The Conversion Agent Engine executes the
data conversions
Search and Classification (TREX)
You can use Search and Classification with SAP NetWeaver PI to search for messages that were previously
indexed Message search using index provides additional methods of searching for specific messages In
addition to static header attributes you can also use adapter-specific message attributes and data from
the message payload for the search A requirement of this however is that the messages are indexed
first You can apply the index-based message search to one or all indexed components of an integration
landscape (domain) Integration Server Adapter Engines and ABAP business systems
For more information see the SAP Library [page 12] at Administratorrsquos Guide Technical Operations for SAP
NetWeaver Administration of SAP NetWeaver Systems Administering PI (Process Integration) Monitoring Index
Administration
Web Dispatcher
The Web Dispatcher lies between the Internet and your SAP system It is the entry point for HTTP(s)
requests into your system which consists of one or more SAP NetWeaver application servers As a
software web switch the Web dispatcher can reject connections or accept them When it accepts a
connection it balances the load to ensure an even distribution across the servers
You can use the Web dispatcher in ABAPJava systems and in pure Java systems as well as in pure ABAP
systems
It is also beneficial to use the Web Dispatcher if you do not need security functions (entry point in the
demilitarized zone (DMZ) SSL URL filtering) but you simply want to balance the load between
multiple SAP NetWeaver Application Server instances
Since Web Dispatcher is optional for every SAP system it is not contained in the system landscape and
the implementation sequence of the use case in this documentation
For more information see the SAP Library [page 12] at Function Oriented View Application Server Infrastructure
SAP Web Dispatcher
3 SAP NetWeaver PI Overview
31 Installable Software Units
2056 PUBLIC 2011-04-15
Advanced Adapter Engine
You use the Advanced Adapter Engine to connect to SAP systems (RFC adapter) and external systems
You use the various adapters in Advanced Adapter Engine to convert XML- and HTTP-based messages
to the specific protocol and format required by these systems and the other way around For specific
senderreceiver combinations messages can be processed without invoking the central Integration
Engine In principle you connect external systems using the adapters that are installed centrally or
non-centrally in Advanced Adapter Engine You can use the Advanced Adapter Engine that is part of
your PI system as a central Advanced Adapter Engine Optionally (for performance reasons) you can
install a non-central Advanced Adapter Engine separately as a system with AS Java and parts of the
usage type PI on a separate host
Adapter Engine (Java SE)
Adapter Engine (Java SE) is a separate software unit You can use it only if you have SAP NetWeaver
systems with usage type PI in your system landscape It has to be installed manually You use the Adapter
Engine (Java SE) to connect to external systems Using the various adapters in the Adapter Engine (Java
SE) XML and HTTP-based messages can be converted to the specific protocol and format required by
such systems and the other way around The Adapter Engine (Java SE) only provides some of these
adapters as a standalone version with restricted functions for operating systems that do not support
SAP NetWeaver PI 71 but that have at least a Java Runtime Environment 50 Therefore you should
use the Adapter Engine (Java SE) only if the platform prerequisites do not allow you to use the Advanced
Adapter Engine
SAP Partner Connectivity Kit
SAP Partner Connectivity Kit (PCK) runs on AS Java with parts of the usage type PI It enables a system
of a smaller company or subsidiary that does not run SAP NetWeaver PI to connect to your SAP
NetWeaver systems
313 Clients
Clients are additional installable programs or tools They reside either on local front-end PCs accessed
by users or on back-end systems where they act as client programs within an SAP NetWeaver system
landscape
The clients that you can use with SAP NetWeaver Process Integration are described in the following
sections
SAP GUI
NOTE
We recommend that you use the following versionsI
SAP GUI for Windows 710 (or higher) with the latest patch level
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 2156
SAP GUI for Java 710 (or higher) with the latest revision
The integrated SAP ITS 710
For more information about the SAP GUI family see SAP Service Marketplace at http
servicesapcomsapgui
SAP offers three different client applications for accessing ABAP applications in SAP systems (such as
SAP NetWeaver systems with usage type AS ABAP) This SAP GUI family consists of
SAP GUI for HTML
SAP GUI for HTML is based on the SAP integrated Internet Transaction Server (ITS) which is
included in the installation of SAP NetWeaver systems as of SAP NetWeaver 2004 On the client
side only a suitable browser (such as Internet Explorer 70 or Firefox 20) and a virtual machine are
required SAP ITS 620 is not compatible with SAP NetWeaver 71
SAP GUI for the Java environment (SAP GUI for Java)
SAP GUI for Java is a generic SAP GUI that covers a variety of platforms
For more information about the installation of SAP GUI for Java see the documentation Installation
Guide ndash SAP Front End
SAP GUI for the Windows environment (SAP GUI for Windows)
SAP GUI for Windows is SAPs universal client for accessing all SAP applications built on ABAP
technology It is available on the Microsoft Windows platform only and offers the broadest feature
set of all members of the SAP GUI family
For more information about the installation of SAP GUI for Windows see the Installation Guide ndash
SAP Front End
SAP NetWeaver Developer Studio
The SAP NetWeaver Developer Studio is SAPrsquos Integrated Development Environment (IDE) for Java
and is based on the open-source tools framework Eclipse 33 With the SAP NetWeaver Developer Studio
you can develop Java EE 5 applications from scratch using the built-in support for new technologies
such as EJB 30 and JSF 12
During the installation of the SAP NetWeaver Developer Studio several features are offered for
installation For SAP NetWeaver PI 71 only the following features are relevant
SAP NetWeaver Developer Studio Platform
SAP NetWeaver Developer Studio Java EE
NOTE
If you want to use one of the other features you need SAP NetWeaver Composition Environment
and a corresponding developers licence
For more information about the installation of SAP NetWeaver Developer Studio see the Installation
Guide ndash SAP NetWeaver Developer Studio 71 or Installation Guide ndash SAP NetWeaver Developer Studio 71 Including
Enhancement Package 1
3 SAP NetWeaver PI Overview
31 Installable Software Units
2256 PUBLIC 2011-04-15
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
SAP enhancement packages are a new way of delivering new functions for SAP NetWeaver This allows
a clear separation between the delivery of new functions on the one hand and corrections legal changes
and security updates on the other hand (in Support Package stacks) SAP enhancement packages are
cumulative an enhancement package always contains the functions of the corresponding predecessor
enhancement packages
Enhancement packages are maintained by their own Support Packages while the main release is in
maintenance
Benefits
SAP enhancement packages offer the following benefits
You have reduced effort for testing and no effort for training when applying Support Packages as
new features are only shipped with enhancement packages
Adding new functions between releases becomes predictable and controllable
New functions can be added successively in small steps There is no need to fully upgrade your
system to get new functions
You have minimal training effort when applying an enhancement package because existing
functions are not replaced
Implementation
There are the following ways to get an SAP NetWeaver system with the release level of SAP enhancement
package 1 for SAP NetWeaver Process Integration 71
New installation of SAP NetWeaver PI 71 including enhancement package 1 using the standard
installation tool SAPinst
Upgrade of an existing SAP NetWeaver system from a release lower than SAP NetWeaver PI 71 to
SAP NetWeaver PI 71 including enhancement package 1 For this you use the upgrade programs
SAPup (for ABAP) and SAPJup (for Java)
Installation of the enhancement package on an existing SAP NetWeaver PI 71 system
For this you use the Software Update Manager (SUM) The Software Update Manager evolved
from the previously used SAP Enhancement Package Installer The tool has been renamed to reflect
its broader use for example you can also use it for applying Support Package Stacks to your system
On the ABAP side the Software Update Manager uses a system cloning and switch procedure for
installing enhancement packages It installs a copy of the system the shadow system parallel to
the original system This shadow system is used to update the relevant software components and
to install the additional components while the original system is still in production operation At
a certain point during downtime the switch to the new system is made and afterwards any parts
of the original system that are no longer needed are deleted The enhancement package installation
in a Java system uses a deploy-based procedure that is no shadow system is used The Software
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2011-04-15 PUBLIC 2356
Update Manager requires a stack configuration file (xml file) as input file for the enhancement
package installation procedure This file lists all the packages that are to be installed in your systems
The stack configuration file is generated when you download the required packages
As the Software Update Manager is updated regularly we recommend to always use the latest
version It is delivered as part of the SL toolset For more information see http
servicesapcomsltoolset
For an overview of all required steps for the enhancement package installation process and
corresponding documents see Process Overview Installation of Enhancement Package 1 on an Existing SAP
Netweaver PI 71 System [page 28]
Content of SAP Enhancement Package 1 for SAP NetWeaver PI 71
With enhancement package 1 for SAP NetWeaver PI 71 new features are introduced and some existing
are changed The following is a selection of some of the most important enhancements
Enhanced design and modelling options in the Enterprise Services Repository
New services registry
Support for new Web services standard (Web Services Reliable Messaging)
New modules for the Advanced Adapter Engine
Use of shared memory of the ABAP Application Server for message processing
For more information about the changes see SAP Library [page 12] at Whatacutes new in SAP NetWeaver PI 71
ndash Release Notes
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2456 PUBLIC 2011-04-15
4 SOA-Based Integration Use Case
41 Overview
You can use SOA-based integration to set up the communication between service providers and service
consumers in both application-to-application and business-to-business scenarios and to execute
operate and monitor the communication at runtime SOA-based integration covers both direct (point-
to-point) as well as mediated (via an Integration Server) communication between service providers and
service consumers
The use case spans the whole life cycle of a SOA-based integration scenario including
Scenario modeling and service design in the Enterprise Services Repository
Implementation of the service provider and consumer in the back-end systems
Configuration and finally execution monitoring and operation of the integration scenario
For scenarios using Integration Server or broker-based communication the configuration of the
different connectivity options (for example SOAP RFC Web Services Industry standards and JDBC)
and their enhancements is covered
For more information see the following documents
Service-Enabling with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdnsoa-modeling
Getting Started
Service-Enabling a Legacy Application with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdn
soa-servicebus Getting Started
In the following you will find information about the installation of the involved software units
42 System Landscape
The following figure shows the system landscape for this use case
4 SOA-Based Integration Use Case
41 Overview
2011-04-15 PUBLIC 2556
Figure 5 SOA-Based Integration
It is mandatory to have a dedicated PI system This applies to development quality and production
landscapes
For PI it is a prerequisite that no other system in your system landscape has a higher release than
the PI system For exceptions to this rule see SAP Note 1043047 For example SAP XI 30 is compatible
with SAP NetWeaver 640 and 70 application systems since the same XI protocol is used Apart
from these exceptions if you want to upgrade or install an application in your system landscape
you first have to make sure that the PI system is on the same release level If required you have to
upgrade the PI system first to the new or a higher release
CAUTION
Although it should be technically possible to run an application system with a higher release
than your PI system in your system landscape this is not supported by SAP (apart from the
exceptions listed in SAP Note 1043047) Therefore you run such a landscape at your own risk
You can use the Advanced Adapter Engine that is part of your PI system as a central Advanced
Adapter Engine
Adapter Engine (Java SE) can be installed in a non-SAP Java environment However it only hosts
a subset of the adapter functionality is only supported for compatibility reasons and should be
used only if this is a precondition in your environment
Optionally you can use the Change Management Service (CMS) of an SAP NetWeaver 70 system
with usage type DI to transport design objects and repository objects For more information see
the SAP Library [page 12] at Administratoracutes Guide Technical Operations for SAP NetWeaver Administration
of SAP NetWeaver Systems PI (Process Integration) Software Logistics Transporting ESR Content and Objects
of Integration Directory PI Transports Using the Change Management Service (CMS)
Smaller business partners or subsidiaries that do not run SAP NetWeaver install SAP Partner
Connectivity Kit in their system landscape SAP Partner Connectivity Kit enables XML document
4 SOA-Based Integration Use Case
42 System Landscape
2656 PUBLIC 2011-04-15
exchange between your SAP NetWeaver systems and the partner systems Since SAP Partner
Connectivity Kit gets installed in their system landscape it is not shown in the system landscape
figure above
The AS ABAP system acts as an application and service provider For Java Web Services you also
require AS Java In addition you require SAP NetWeaver Developer Studio on the client side as a
development environment
The Web service client can be either an SAP or a non-SAP application For example an AS ABAP
system or a Web browser could act as application or service consumer
You can install SAP Conversion Agent by Informatica in the system with usage type PI or on a host
where SAP Partner Connectivity Kit is installed or on a host where neither usage type PI nor SAP
Partner Connectivity Kit is installed
43 Implementation Sequence
Procedure
To install this use case perform the steps listed in the following table
StepAction[Corresponding Documentation] Remarks
1 Make sure that you have performed the preparation steps You have planned your system landscape [page 33]
(that is you have decided how many systems you require how you want to use each of these systems and which standalone engines and clients you require)
With the help of your hardware partner you have mapped your systems and standalone engines to properly sized hosts
You have planned and installed shared services [page 35]
2 Installation of system with usage type PI (includes the installation of AS ABAP and AS Java)
NOTE
For usage type PI a Unicode installation is mandatory
[Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt]
If you want to use the features of enhancement package 1 use the direct installation of SAP NetWeaver PI 71 including enhancement package 1
Make sure that you perform the configuration steps as described in the installation guide For certain usage types configuration tasks can be applied by the configuration wizard These configuration tasks as well as any additional configuration steps for your use case are listed in SAP Solution Manager For more information
4 SOA-Based Integration Use Case
43 Implementation Sequence
2011-04-15 PUBLIC 2756
StepAction[Corresponding Documentation] Remarks
see the Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt
3 Install the Adapter Engine (Java SE) engines if required[Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
4 To integrate small business partners and subsidiaries the business partners or subsidiaries install SAP Partner Connectivity Kit running on AS Java with parts of usage type PI in the business partners or subsidiarys system landscape[Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
5 Install SAP Conversion Agent by Informatica if required[SAP Library [page 12] at Function-Oriented View Process Integration SAP Conversion Agent by Informatica Deploying and Using Conversion Agent ]
6 Installation of clients SAP GUI
[Installation Guide ndash SAP Front End]
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
The process sequences give a comprehensive overview of the steps relevant for the enhancement
package installation on an existing SAP NetWeaver PI 71 system
The process sequence is divided into a planning phase and an implementation phase Each step in both
phases contains references to the corresponding documentation to ensure that you can easily find the
information you need
Process
NOTE
To download the enhancement package files and required Support Packages you require the SAP
Solution Manager Maintenance Optimizer You have the following options
Manual Selection
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2856 PUBLIC 2011-04-15
You manually select the required files from SAP Service Marketplace at http
servicesapcomswdc using the SP Stack Application You use the Maintenance Optimize
only to approve the packages which is a prerequisite for the download
Automatic Calculation
The Maintenance Optimizer supports the download of a consistent queue that includes all
necessary Support Packages and enhancement packages In addition SAP Solution Manager
calculates a valid import queue for the selected SAP system and generates the enhancement
package stack configuration file that you require for the installation
As a prerequisite the system that you want to update needs to be maintained correctly in
SAP Solution Manager System Landscape As the Maintenance Optimizer uses this data for
the calculation it is crucial that the data is up-to-date In addition the SAP Solution Manager
system requires a Minimum Support Package level (see below)
Planing PhaseStep Description Documentation
Hardware amp Software Prerequisites
Check which platforms are supported for your target release (OSDB dependencies)
Product Availability Matrix (PAM) at httpservicesapcompam
Check which hardware sizing is required for your target release
Sizing information at httpservicesapcomsizing
Solution Manager Prerequisites
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of the required software packages you have to make sure that your SAP Solution Manager system has the required Support Package levelAt least SAP Solution Manager 70 EHP1 Support Package Stack 17 is required We recommend to use SAP Solution Manager 70 EHP1 Support Package Stack 23Check if you need to do an update or upgrade of your SAP Solution ManagerMake sure that you run the guided procedure SOLMAN_SETUP after every installation or update of SAP Solution Manager and that it completes successfully
For upgrades from source release SAP Solution Manager 31 and 32Upgrade Guide ndash SAP Solution Manager 70 incl Enhancement Package 1For updates from SAP Solution Manager 70Update Guide SAP Enhancement Package 1 for SAP Solution Manager 70Follow-up activities after an Support Package Stack update or enhancement package updateSolution Operations Guide ndash SAP Solution Manager 70 EHP1 section Software Change Management All guides are available at http
servicesapcom instguides SAP Components SAP Solution Manager -gt Release 70 EHP 1
Implementation PhaseStep Description Documentation
1Solution Manager Preparation
Configure the SAP Solution Manager Maintenance Optimizer
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of software packages make sure your
Configuration of Maintenance Optimizer http
helpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Change Request Management and Change ControlMaintenance Optimizer
Prerequisites
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 2956
Implementation PhaseStep Description Documentation
system landscape data in SAP Solution Manager is maintained correctlyLandscape Verification 10 which is an add-on to SAP Solution Manager can support you in maintaining your system landscape data The use of this tool is optional
Landscape Verification http
wwwsdnsapcom irj
sdn alm-update-
management link Landscape Verification under Related Areas on Upgrade and Update Management (in the right column)
SAP Note 1468605 (Installation of Landscape Verification)
Maintaining System Landscape Information [page 47]Note that the information provided in this section is based on SAP Solution Manager 70 EHP1 SP23
2System Preparation
Prepare your system as described in the documentation for example perform OS DB specific preparations and the PI-specific preparations
Update Guide ndash Update of SAP Systems with Software Update Manager sections Planning and Preparation
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
3Software Download
Select and download the software packages in either of the following ways Automatic calculation Create
a maintenance transaction in the Maintenance Optimizer and choose the Calculate Files Automatically option
Manual Selection Create a maintenance transaction in the Maintenance Optimizer and choose the Select Files Manually option You then can select the files manually using the SP Stack application in SAP Service Marketplace
NOTE
You have to download the stack configuration file manually after you have selected all files in the SP Stack
httphelpsapcom SAP Solutions SAP Solution Manager
SAP Solution Manager 70 EHP1 ltSPgtChange Request Management and
Change Control Maintenance Optimizer Maintenance Procedure Scenarios
For information about the automatic calculation see Maintenance Transaction with Installation of an Enhancement PackageFor information about the manual selection and approval process see section Approve and Download Files in Download Basket
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
3056 PUBLIC 2011-04-15
Implementation PhaseStep Description Documentation
application Choose Generate Stack XML and save the file
4Enhancement Package Installation
Run Software Update Manager to update your system with the selected software packages
Update Guide ndash Update of SAP Systems with Software Update Manager
5Follow-Up Steps
Perform technical and PI-specific follow-up activities after the enhancement package installation is done
Update Guide ndash Update of SAP Systems with Software Update Manager section Follow-Up Activities
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
6Configuration
Configure newly installed enhancement package functions using SAP Solution Manager content
See Systems with Usage Types [page 16] section Configuration of Systems with Usage Types
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 3156
This page is left blank for documents that are printed on both sides
5 System Landscape
51 Planning Your System Landscape
The installable software units that make up your system landscape depend on the functions that you
want to implement For information about the features see systems [page 16] standalone engines [page 19]
and clients [page 21]
In addition you have to determine the required shared services [page 35] (such as SAP Solution Manager
or SAP NetWeaver Administrator) that run on central systems in your system landscape and the
landscape aspects relevant for their implementation
In the following you will find general information that you should consider when planning your system
landscape
Sizing
You have to map systems and standalone engines to hosts after you have a clear picture of the following
Which systems and standalone engines you require
How many systems you require and how you want to use each of these systems
NOTE
No general guideline can be given for the sizing of your landscape since this relies heavily on your
requirements You should therefore perform this task together with your hardware partner and
your technical consultant
For information about sizing your systems you can use the following information sources
Your first point of reference is the Quick Sizer
SAP built the Quick Sizer as an online sizing questionnaire Internet application in close cooperation
with its hardware partners This tool delivers general sizing categories based on your volume load
estimates The results provide an objective basis for sizing independent of platform and
configuration
For more information see SAP Service Marketplace at
httpservicesapcomsizing for the SAP NetWeaver PI 71 sizing guide available under
Sizing Guidelines Business Suite amp Services
httpservicesapcomquicksizer for more information and access to the tool itself
Also consider the following important aspects concerning sizing
High availability
5 System Landscape
51 Planning Your System Landscape
2011-04-15 PUBLIC 3356
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Technical Infrastructure High Availability
Unicode
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Internationalization
Contact your hardware partner to find out the appropriate number of sized hosts
The platform-independent abstract results of the Quick Sizer can be used by any of our hardware
partners to create a concrete offer SAP itself does not make any hardware recommendations the
responsibility for sizing and detailed hardware configuration lies with the hardware partners
Figure 6 Example of Mapping of Systems and Standalone Engines to Three Hosts
NOTE
Optionally you could also distribute single systems to multiple hosts For example you could
decide to install the database instance of an SAP system on a separate host for performance
reasons or distribute other system instances to achieve high availability
To provide a mapping that fits your required functions and performance your hardware partner
and your technical consultant have to identify the number of required instances of SAP NetWeaver
find out how to distribute these instances to hosts and what functions will run on which instance
Therefore the hardware partner and the technical consultant have to consider many different
aspects such as
Number of required SAPS (SAP Application Benchmark Performance Standard) for each
system (provided by Quick Sizer)
Landscape-relevant aspects concerning security For more information see the SAP Security
Guide in the SAP Library [page 12] at Administratoracutes Guide Security Guide
Landscape-relevant aspects concerning scalability high availability operation and software
life-cycle management
5 System Landscape
51 Planning Your System Landscape
3456 PUBLIC 2011-04-15
For more information about relevant aspects for the mapping of systems to hosts see the document
Technical Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
Scaling and Distribution Options
You may need to design your system landscape for a large number of users SAP NetWeaver PI offers
you different means of scalability The following list provides you with some examples
You could install multiple systems of one type and use them for different purposes
You could scale every system by installing dialog instances or by distributing the database instance
For more information about distribution options on the instance level see the Technical
Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
For every SAP system you could additionally install Web Dispatcher For more information see
the SAP Library [page 12] at FunctionndashOriented View Application Server Infrastructure SAP Web
Dispatcher
You could further distribute certain standalone engines ndash for example Search and Classification
(TREX) is based on a flexible architecture that supports a distributed installation For more
information see the Technical Infrastructure Guide ndash SAP NetWeaver PI 71 available in SAP Service
Marketplace at httpservicesapcominstallNWPI71
52 Shared Services
You normally run shared services on central systems in your system landscape The following features
could be used for SAP NetWeaver Process Integration to realize shared services
SAP Solution Manager
Used to implement train test maintain monitor control change and manage incidents of your
SAP solution system landscape (open end-to-end application management)
As of SAP Solution Manager (70) 40 Support Package 15 SAP Solution Manager has become the
platform for SAPs end-to-end solution operations strategy Functions for complete application
management has been combined with administrative tools and has been merged in newly created
role based work centers
NOTE
Be aware that you require an SAP Solution Manager system to install or upgrade to SAP
NetWeaver 70 and higher An SAP Solution Manager system is required to generate the SAP
Solution Manager key needed during the installation or upgrade process Without this key
the installation or upgrade process cannot continue
For SAP NetWeaver Process Integration you require SAP Solution Manager 70
For more information see SAP Note 805390
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3556
Solution Manager Diagnostics
An integral part of SAP Solution Manager that is running as a Java application on the Java stack of
SAP Solution Manager 70 Solution Manager Diagnostics is used to analyze the root cause of
incidents in your landscape in an efficient and safe way Before Go-Live Solution Manager
Diagnostics has to be set up and made accessible remotely
SAP NetWeaver Administrator
SAP NetWeaver Administrator is the central administration component which is used for
monitoring and administering Java applications It is included in SAP NetWeaver systems with AS
Java
SAP NetWeaver Administrator exists in the following flavors
A local mode which runs out of the box and which focuses on administrating the underlying
SAP NetWeaver AS Java
NOTE
For a SAP NetWeaver PI 71 it has a special role which you need to activate using a
configuation wizard
A central mode which has to be configured before use and which deals with the system
landscape management
SAP has decided to merge the central mode of SAP NetWeaver Administrator into the new work
centers available as of SAP Solution Manager 70 SP 15 Thus it can be used in an administrative
context together with non-Java-based administration tools Although the central mode of SAP
NetWeaver Administrator will be still available for some time SAP will not develop this tool any
further SAP focuses on optimizing the administrative work centers of SAP Solution Manager
instead
The local mode of SAP NetWeaver Administrator stays untouched It is available for current and
future releases of SAP NetWeaver
SAP Central Process Scheduling by Redwood
SAP Central Process Scheduling application by Redwood enables central job scheduling and job
monitoring of current and old releases of AS ABAP systems (as of Basis Release 31) This application
is fully integrated in SAP NetWeaver Depending on the business needs SAP business applications
are the initial trigger for scheduled activities You can now manage jobs and job chains conveniently
using a graphical user interface
System Landscape Directory
The System Landscape Directory is the central directory of system landscape information relevant
for the management of your software life-cycle It contains a description of your system landscape
(that is software components that are currently installed) and a repository of software components
that can theoretically be installed in your landscape (such as the software components available
from SAP)
Adaptive Computing Controller
5 System Landscape
52 Shared Services
3656 PUBLIC 2011-04-15
The Adaptive Computing Controller enables users to control an adaptive computing landscape
from a single point through observation operation and dynamic resource distribution With
adaptive computing hardware software and system services are able to adapt to changing business
needs In the Adaptive Computing Controller the run-time data of logical and physical landscapes
can be monitored application services can be startedstoppedrelocated and hardware resources
can be assigned to application services The operation can also be mass executed and be planned as
tasks to be executed
For more information about the installation of the Adaptive Computing Controller tool see the
document Installation Guide ndash Adaptive Computing Controller in SAP NetWeaver 71 available on SAP Service
Marketplace at httpservicesapcominstallNWPI71
For more information about Adaptive Computing in general see httpsdnsapcomirj
sdnadaptive
521 Use Cases
You can use the applications and tools described above for use cases that are normally performed
centrally The following sections describe these use cases
5211 End-to-End Solution Operations
Running business applications through their complete life-cycle is a challenge Therefore SAP has
started the Run SAP methodology for implementing End-to-End Solution Operations Based on a set
of SAP standards a roadmap and a package for training and certification Run SAP helps customers to
facilitate End-to-End Solution Operations
You can download the SAP standards for Solution Operations from SAP Service Marketplace at http
servicesapcomsupportstandards They describe roles customers typically have in their IT
environment For optimal role support SAP has grouped existing and new functions in SAP Solution
Manager work centers as of SAP Solution Manager 70 Support Package 15 Operations aspects are fully
covered by adding administrative functions for SAP NetWeaver as well Work centers are ABAP Web
Dynpro-based applications They offer the following advantages
Easy to use similar look and feel
Context transfer while jumping from one work center into another
Logical grouping of tools for a certain area
Simple authorization concept
Easy to expand
Each IT role belongs to one or more work centers For instance the Technical Administrator IT role is
covered by the work centers for System Monitoring System Administration and Landscape Management
The following work centers are available
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3756
Business Process Operations
Change Management
Root Cause Analysis
Implementation Upgrade
Incident Management
Test Management
Job Management
System Landscape Management
Solution Documentation Assistant
SAP Engagement and Service Delivery
SAP Solution Manager Administration
System Administration
System Monitoring
My Home is the central point of access to all important data of almost all work centers in SAP Solution
Manager
5212 Support Infrastructure
A key requirement for effective support of IT solutions is the ability to perform root cause analysis with
speed and efficiency
With SAP Solution Manager SAP has long had an infrastructure in place for its ABAP applications that
efficiently supports SAP solutions This helps ensure the high availability and smooth running of
business processes For more information see the SAP Solution Manager section
With Solution Manager Diagnostics this knowledge has been extended to Java applications If for
example homegrown Java applications cause instability Solution Manager Diagnostics helps trace the
cause to eradicate the problem rapidly Solution Manager Diagnostics is fully integrated into SAP
Solution Manager 70 Solution Manager Diagnostics also contains two third-party tools CArsquos Wily
Introscopereg for measuring performance as well as troubleshooting problems of the Java EE Engine
and applications running on it and Mercury Loadrunnerreg which enables SAP Support to produce a
defined load in the SAP solution landscape remotely For more information see Solution Manager
Diagnostics [page 43]
The support infrastructure provides SAP Support with safe access to your productive landscape for safe
root cause analysis so ensuring that SAP Support does not change your landscape inadvertently You
require a support infrastructure to run SAP NetWeaver
The following figure shows the overall infrastructure including SAP NetWeaver administration tools
that are used by administrators or operators at the customer site
5 System Landscape
52 Shared Services
3856 PUBLIC 2011-04-15
Landscape Aspects
If you use SAP NetWeaver Process Integration 71 productively besides SAP Solution Manager (as a
central support platform) you have to set up Solution Manager Diagnostics for supportability reasons
Implementation Sequence
For information about the implementation of the support infrastructure see the document Master
Guide ndash SAP Solution Manager 70 available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution Manager ltReleasegt
5213 Collection of Landscape Data
Amongst other applications and services the support infrastructure and the SAP NetWeaver
administration tools rely on system landscape data
For SAP NetWeaver PI 71 you have to run non-ABAP components in your solution landscape
Therefore the System Landscape Directory is mandatory The landscape data that is automatically
gathered by the System Landscape Directory is replicated to SAP Solution Manager There are several
topology options for the System Landscape Directory They offer different grades of availability
administration and operation effort
For more information see the System Landscape Directory section
5214 Authentication and Single Sign-On
Before implementing your system landscape plan how to implement authentication and how to
integrate different systems into a Single Sign-On landscape Single Sign-On reduces complexity for end
users saving them valuable time while also reducing administration effort for resetting passwords
thereby contributing to TCO reduction
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
5215 Integrated User and Access Management
In a system landscape containing a combination of ABAP and Java components we recommend that
you integrate your user and access management so that you can use the same user data across different
systems administer this data centrally and control access to data SAPs mature fine-grained
authorization concept allows detailed control of access rights SAP NetWeaver provides both ABAP and
Java-based user management solutions The user management solution that you use to administer
your user data depends on factors such as the type of systems that are running in your landscape
If you want to use central user administration we recommend that you run it in a non-production
system If you do not have a central user administration yet you can for example realize it in the SAP
Solution Manager system
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3956
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
522 Examples for the Overall System Landscape of Shared Services
In this section we provide examples of how shared services can be set up depending on the system
landscape they are intended for The following examples aggregate the landscape aspects given in the
Use Cases section
NOTE
The following sections and the figure mostly do not show information about the life-cycle of
shared services For example you may also need a development and testquality assurance system
for SAP Solution Manager You should consider this aspect in addition to the information given
in this section based on your requirements
Small and MediumndashSized Customer Landscapes with Java
As you use Java productively for SAP NetWeaver PI 71 besides SAP Solution Manager you have to set
up additional components for optimal monitoring administration and support Solution Manager
Diagnostics and the central mode of SAP NetWeaver Administrator are already fully integrated into
SAP Solution Manager 70 as the central operations hub For SAP Process Integration you must also
set up SAP NetWeaver Administrator with a special role
We recommend that you do not install SAP Central Process Scheduling in the SAP Solution Manager
system You have to set up and operate the system which hosts your productive scheduler as a mission
critical system
In the SAP Solution Manager system you should set up a local System Landscape Directory in addition
to a central runtime System Landscape Directory This way you have a clear separation between your
management system (SAP Solution Manager) and managed systems in your landscape In addition
SAP Solution Manager then does not rely on a System Landscape Directory running in the production
environment For this setup configure the SLD data suppliers of your SAP Solution Manager system
to send data to the central runtime System Landscape Directory In addition configure automatic
bridge forwarding from your runtime System Landscape Directory to the local System Landscape
Directory For more information see the Planning Guide - System Landscape Directory
If you want to use a central system for Adobe Document Services we recommend that you install a
dedicated system for this purpose in your production environment For detailed information about
the sizing of the system for the different use cases see the Sizing Guide for Adobe Document Services at
SAP Service Marketplace at httpservicesapcomsizing Sizing Guidelines Solutions amp
Platform
We recommend that you start with this centralized SAP Solution Manager approach as depicted in the
following figure
5 System Landscape
52 Shared Services
4056 PUBLIC 2011-04-15
Figure 7 Single SAP Solution Manager Landscape
Large Customer Landscapes with Java
Large customers who have environments in their landscape that are large and distributed administered
by different groups or separated for security reasons can consider a distributed operations setup In
addition to the centralized setup described for small- and medium-sized customers above large
customers can put parts of the central management functions on extra hosts or systems for performance
or policy reasons You have the following options for a distributed setup
You may set up an extra system or client for Central User Administration (CUA)
The Change and Transport System (CTS) can run on an extra system However it is not
performance- or data-intensive
You may set up an extra system for central CCMS monitoring Depending on the customizing
and on the landscape size central CCMS may generate a lot of system load You can connect a
separate central CCMS to SAP Solution Manager for displaying alerts in the alert inbox of the System
Monitoring work center
You can use a separate SAP NetWeaver 70 system with usage type BI together with SAP Solution
Manager This may make sense with respect to the amount of landscape management data that is
stored for reporting purposes The amount of data strongly depends on the data granularity
storage time frame and landscape size
You can easily put Wily Introscope Enterprise Manager on an separate host
Other aspects described above for small- and medium-customers (such as the setup of the System
Landscape Directory) are also valid for large customers
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4156
523 Feature Details
This section provides further information about the features described above
5231 SAP Solution Manager
SAP provides you with SAP Solution Manager as the strategic application management platform and
to enable the collaboration between you and SAP You need to install at least one productive SAP
Solution Manager in your system landscape To ensure the availability of this application management
platform an SAP Solution Manager system is technically required to install or upgrade to SAP
NetWeaver 70 or higher If you are already using SAP Solution Manager you can also use it to manage
the solution you build with SAP NetWeaver In this case we highly recommend that you update SAP
Solution Manager to the latest version
As of SAP Solution Manager 70 SP15 you can use the newly created work centers
NOTE
During the SAP system installation or upgrade process you are prompted to enter the SAP
Solution Manager key An SAP Solution Manager system is required to generate this key Without
this key the installation or upgrade process cannot continue
You may generate all needed keys for your entire system landscape (development quality
assurance and production system) in one SAP Solution Manager system In case you plan to install
several solution landscapes (for example in different countries) one SAP Solution Manager
system is still sufficient
For more information see SAP Note 805390
It is possible to install multiple SAP Solution Managers If you do so they should host separate business
solutions
If you want to reduce the risk of unavailability you should not install SAP Solution Manager as a central
component Instead you can operate a 2-system-landscape with both a test and production
environment of SAP Solution Manager (especially if you are using time-critical functions like Support
Desk) If you also develop your own content a 3-system-landscape with a development test and
production environment is recommended
For more information about SAP Solution Manager see the following table
Topic Where to Find More Information
System infrastructure scenarios installation and configuration of SAP Solution Manager
Master Guide ndash SAP Solution Manager available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution ManagerltReleasegt
Benefits and usage scenarios SAP Solution Manager ndash Learning Maps available on SAP Service Marketplace at http
5 System Landscape
52 Shared Services
4256 PUBLIC 2011-04-15
Topic Where to Find More Informationservicesapcomrkt-solman or https
servicesapcomsolutionmanager
Additional information See SAP Service Marketplace at http
servicesapcomsolutionmanager
5232 Solution Manager Diagnostics
Solution Manager Diagnostics provides efficient and safe root-cause analysis of incidents in customer
solutions powered by SAP NetWeaver It can help monitor on operating systems databases Java
application activities performance and logs It also supports the reporting of software and
configuration changes that can lead to malfunctions and errors
You must run one Solution Manager Diagnostics within your SAP solution landscape if you run
applications based on SAP NetWeaver systems with usage type AS Java Agents are responsible for
delivering the data from all productive hosts within your system landscape to the Solution Manager
Diagnostics system
CAUTION
SAP Support performs root-cause analysis on incoming incidents with Solution Manager
Diagnostics Not installing and configuring this support infrastructure results in a dramatically
reduced service level
Solution Manager Diagnostics is fully integrated into SAP Solution Manager 70
Solution Manager Diagnostics also contains Wily Introscope (Display Server and Agent part) for
measuring performance as well as to troubleshoot problems of Non-ABAP applications Wily Introscope
is heavily used for troubleshooting applications running on AS Java
SAP has signed a distribution agreement for Wily Introscope SAP customers are allowed to use this
tool in a preconfigured way
For more information about Solution Manager Diagnostics and an FAQ list see SAP Service Marketplace
at httpservicesapcomdiagnostics
5233 System Landscape Directory
The System Landscape Directory (SLD) of SAP NetWeaver is the central directory of system landscape
information relevant for the management of your software life-cycle
NOTE
Note that the abbreviation SLD is not intended to define a product since the System Landscape
Directory is part of SAP NetWeaver This abbreviation is solely intended to improve readability
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4356
The System Landscape Directory contains a description of your system landscape (that is software
components that are currently installed) and a repository of software components that can
theoretically be installed in your landscape (such as the software components available from SAP)
Since this data gets updated automatically the System Landscape Directory provides reliable and up-
to-date system landscape information with as little effort for you as possible In this way the System
Landscape Directory acts as a central information provider for SAP and third-party tools that use this
data to deliver the services you need to keep your landscape up and running
For the System Landscape Directory as part of an SAP NetWeaver PI 71 landscape consider the following
aspects
Part of SAP NetWeaver PI 71 is a new version of the System Landscape Directory It is automatically
included in every SAP NetWeaver 71 system with usage type AS Java It offers enhanced functions
such as a full automatic synchronization mechanism for all data stored in it That is both data
delivered by data suppliers and data entered or changed manually in the System Landscape
Directory can be synchronized automatically This synchronization offers the following
A fully automated mechanism so no user interaction is required and conflicts are resolved
automatically
Asynchronous propagation of information so some nodes may be down temporarily
Communication over HTTP protocol
Uni- and bi-directional synchronization
Depending on your use case the full automatic synchronization could significantly reduce manual
synchronization effort
For SAP NetWeaver PI 71 the configuration of the system landscape directory and its data suppliers
is already included in the standard implementation procedure with SAPinst For existing systems
you only have to perform some quick and easy configuration actions to start operating the system
landscape directory server in an AS Java system
For SAP NetWeaver PI 71 you have the following options concerning SLD
Option 1
Run SAP NetWeaver PI 71 against an existing SLD running on SAP NetWeaver 70 We only
recommend this for upgrades from SAP NetWeaver 70 if you have a central SLD in operation
not running on one of your PI systems
Option 2
Use the SLD included in an SAP NetWeaver PI 71 system We recommend this option for new
installations and upgrades from older releases than SAP NetWeaver 70 due to the enhanced
functions and improved performance of SLD 71
NOTE
If you already have a central SLD running on SAP NetWeaver 70 in operation you could run
two SLD versions in parallel ndash SLD running on SAP NetWeaver 71 for your PI systems and
SLD running on SAP NetWeaver 70 for all other systemsuse cases This way your SAP
5 System Landscape
52 Shared Services
4456 PUBLIC 2011-04-15
NetWeaver PI 71 systems would benefit from the new features while it would be easy to set
up and operate such an SLD landscape For this purpose you could use the new fully
automatic synchronization This feature enables the automatic forwarding of all SLD data
from an SLD running on SAP NetWeaver 70 to an SLD running on SAP NetWeaver 71 As a
result there is no need to adapt most existing systems as their SLD data suppliers could still
send their data to the central SLD In brief the following steps would be required
1 Put SLD in a PI system into operation (part of standard implementation procedure)
2 Configure PI systems to use the new SLD (part of standard implementation procedure
for new PI systems)
3 Set up the fully automatic synchronization from your old SLD to your new SLD
As soon as an upgrade or an installation of a standalone AS Java 71 system is available you
could move your central SLD also to SAP NetWeaver 71 Then you could optionally shift
your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems
Figure 8
We recommend that you use a Domain Name System (DNS) alias so that you are able to switch to
another System Landscape Directory easily For example if customers build a new landscape they
normally start with a sandbox environment Over time more and more environments are set up
Once the production environment is in place move the System Landscape Directory there To do
this you can configure a new System Landscape Directory in the production environment
synchronize it with the old System Landscape directory and switch to the new one
Topology
Apart from the considerations above the System Landscape Directory offers several topology options
with different grades of availability at the expense of low administration and operation effort There is
no generic rule therefore on how to set up a System Landscape Directory in your system landscape
To find the topology and synchronization strategy for the System Landscape Directory that fits your
requirements concerning the System Landscape Directory availability (and hence the availability of
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4556
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2011 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 noticeSome 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 CorporationIBM 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 zVM zOS i5OS S390 OS390 OS400 AS400 S390 Parallel Enterprise Server PowerVM Power Architecture POWER6+ POWER6 POWER5+ POWER5 POWER OpenPower PowerPC BatchPipes BladeCenter System Storage GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 Parallel Sysplex MVSESA AIX Intelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the US and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States andor other countriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeSAP R3 SAP NetWeaver Duet PartnerEdge ByDesign SAP BusinessObjects Explorer 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 countriesBusiness 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 in the United States and in other countriesSybase 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 companyAll 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 varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) 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
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
256 PUBLIC 2011-04-15
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2011-04-15 PUBLIC 356
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
456 PUBLIC 2011-04-15
Document History
CAUTION
Before you start the implementation make sure you have the latest version of this document
You can find the latest version on SAP Service Marketplace httpservicesapcom
instguides
The following table provides an overview on the most important document changes
Version Date Description
10 2007-12-07 First version
11 2008-02-05 Changes to System Landscape Directory section Minor changes
12 2008-04-22 Major revision of Shared Services section
13 2008-05-29 Information about dedicated PI system updated
14 2008-12-12 Restructuring of content according to use case concept Information about SAP enhancement package 1 for SAP NetWeaver PI 71 added
15 2009-03-19 Minor changes (mainly language corrections)
16 2009-03-20 Minor error corrections
17 2011-04-15 Section SAP Enhancement Package 1 for SAP NetWeaver PI 71 updated (Software Update Manager replaces SAP Enhancement Package Installer)
Section Process Sequence Installation of Enhancement Package 1 on an Existing SAP NetWeaver PI 71 system added
Section Maintaining System Landscape Information added Further minor changes
2011-04-15 PUBLIC 556
Table of Contents
Chapter 1 Introduction 9
Chapter 2 Before You Start 11
21 SAP Notes 11
22 More Information 11
23 Accessing the SAP Library 12
Chapter 3 SAP NetWeaver PI Overview 13
31 Installable Software Units 15
311 Systems with Usage Types 16
312 Standalone Engines 19
313 Clients 21
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration
71 23
Chapter 4 SOA-Based Integration Use Case 25
41 Overview 25
42 System Landscape 25
43 Implementation Sequence 27
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP
Netweaver PI 71 System 28
Chapter 5 System Landscape 33
51 Planning Your System Landscape 33
52 Shared Services 35
521 Use Cases 37
5211 End-to-End Solution Operations 37
5212 Support Infrastructure 38
5213 Collection of Landscape Data 39
5214 Authentication and Single Sign-On 39
5215 Integrated User and Access Management 39
522 Examples for the Overall System Landscape of Shared Services 40
656 PUBLIC 2011-04-15
523 Feature Details 42
5231 SAP Solution Manager 42
5232 Solution Manager Diagnostics 43
5233 System Landscape Directory 43
Chapter A Appendix 47
A1 Maintaining System Landscape Information 47
Chapter B Reference 51
B1 The Main SAP Documentation Types 51
B2 List of Documentation 51
2011-04-15 PUBLIC 756
This page is left blank for documents that are printed on both sides
1 Introduction
This Master Guide provides you with a central starting point for the technical implementation of SAP
NetWeaverreg Process Integration (SAP NetWeaver PI) It also contains information about enhancement
package 1 for SAP NetWeaver Process Integration 71
SAP NetWeaver PI 71 is based on an established architecture for realizing cross-system business processes
and supporting an service-oriented architecture (SOA) The focus is on the service-based integration
of applications
Structure of the Master Guide
The Master Guide consists of the following sections
Introduction
Contains an introduction to this guide
Before You Start
Contains information about this document important things which you need to know before you
start and information on how to access the SAP Library
SAP NetWeaver Overview
Describes the building blocks of SAP NetWeaver PI
SOA-Based Integration Use Case
Introduces the use case and explains how to install it
System Landscape
Contains information about how to install your system landscape
Reference
Contains information about the overall documentation concept for SAP systems
CAUTION
Make sure you have the latest version of the Master Guide by checking SAP Service Marketplace
immediately before starting the installation
The Master Guide is regularly updated on SAP Service Marketplace at http
servicesapcominstallnwpi71 Planning
Constraints
The business scenarios that are presented here serve as examples of how you can use SAP software in
your company The business scenarios are intended only as models and do not necessarily run the way
they are described here in your customer-specific system landscape Check your requirements and
systems to determine whether these scenarios can be used productively at your site Furthermore we
1 Introduction
2011-04-15 PUBLIC 956
recommend that you test these scenarios thoroughly in your test systems to ensure that they are
complete and free of errors before going live
1 Introduction
1056 PUBLIC 2011-04-15
2 Before You Start
21 SAP Notes
You must read the following SAP Notes before you use this Master Guide and implement SAP NetWeaver
Make sure that you have the up-to-date version of each SAP Note which you can find on SAP Service
Marketplace at httpservicesapcomnotes
NOTE
The SAP Notes related to SAP NetWeaver PI 71 are also listed on SAP Service Marketplace at
httpservicesapcomsapnotesnwpi71
List of Important SAP Notes
SAP Note Number Title Description
1004107 Release Restrictions for SAP NetWeaver PI 71
Some restrictions apply to the productive use of SAP NetWeaver PI 71 These are documented in this SAP Note
1247043 Release Restrictions for SAP EHP1 for SAP NetWeaver PI 71
Some restrictions apply to the productive use of enhancement package 1 for SAP NetWeaver PI 71 These are documented in this SAP Note
22 More Information
The following table contains links to information available on SAP Service Marketplace or in the SAP
Library which is important for implementing SAP NetWeaver
Content Location on SAP Service Marketplace or in SAP Library
The latest version of the installation and upgrade guides for SAP NetWeaver Process Integration
httpservicesapcominstguidesnwpi71
Information about supported platforms (operating systems databases browsers) for all SAP NetWeaver components
httpservicesapcomplatforms Product Availability Matrix
Sizing of SAP NetWeaver httpservicesapcomsizing
Information about security SAP Security Guide See the SAP Library [page 12] at Adminitstratoracutes Guide Security Guide
Information about the technical operation of SAP NetWeaver
Technical Operations Manual See the SAP Library [page 12] at Adminitstratoracutes Guide Technical Operations for SAP NetWeaver
2 Before You Start
21 SAP Notes
2011-04-15 PUBLIC 1156
Content Location on SAP Service Marketplace or in SAP Library
Information about SAP NetWeaver PI Support Package Stacks
httpservicesapcomnetweaver SAP NetWeaver PI 71- Release-Specific Information Support Package Stacks Information
Information about installing SAP NetWeaver Support Package Stacks
httpservicesapcomMaintenanceNWPI71
Support Package Stack Guide ndash SAP NetWeaver
23 Accessing the SAP Library
For more information about SAP NetWeaver Process Integration access the SAP Library from any of
the following
SAP Help Portal at httphelpsapcomNWPI71 SAP NetWeaver Process Integration 71 Library
ltLanguagegt SAP NetWeaver Process Integration Library
CAUTION
The SAP Help Portal contains the latest version of the SAP Library Therefore we recommend
that you use this channel to access the SAP Library
An SAP system if you have installed the online documentation Choose Help SAP Library
The browser starts
The help files on the online documentation CDs or DVDs
If you want to view the help files in HTMLHelp format from the online documentation CDs or
DVDs you need a PC running Microsoft Windows to install the HTMLHelp Viewer
2 Before You Start
23 Accessing the SAP Library
1256 PUBLIC 2011-04-15
3 SAP NetWeaver PI Overview
Introduction
SAP NetWeaver PI 71 is part of the SAP NetWeaver technology platform The complete offering of the
SAP NetWeaver technology platform is visualized in the SAP NetWeaver technology map which you
can access at httpsdnsapcomnetweaver SAP NetWeaver at a Glance The technology map
enables you to drill down from top-level technology areas (for example Lifecycle Management) to
individual capabilities (for example Administration Monitoring and so on)
SAP NetWeaver PI includes the following capabilities
Repository-based Modeling and Design
Service Bus-based Integration
SOA Management
A different view is introduced by the end-to-end use case concept This concept offers an
implementation view on SAP NetWeaver to structure and facilitate your implementation
A use cases is a process that typically involves several SAP NetWeaver capabilities It is not limited to a
single component or capability A use case guides you through the different phases of your
implementation project ndash from information through installation to the configuration phase This
implies that a uses case addresses several user roles administrator power user and end user
This document describes the SOA-based integration use case
Architecture Principals
The architecture of SAP NetWeaver Process Integration 71 (SAP NetWeaver PI 71) is based on an
established architecture for realizing cross-system business processes and is a further development of
lower releases (SAP NetWeaver 70 usage type Process Integration and SAP XI 30 as part of SAP
NetWeaver 2004) SAP NetWeaver PI 71 plays an important role in supporting an service-oriented
architecture (SOA) The focus is on the service-based integration of applications
SAP NetWeaver PI is based on general standards so as to enable 3rd-party systems to be integrated At
the center of SAP NetWeaver PI is an XML-based communication that uses HTTP (Hyper Text Transfer
Protocol) Irrespective of the scenario used the application-specific contents are transferred in messages
in user-defined XML (eXtensible Markup Language) from the sender to the receiver either via the
Integration Server or directly between the systems involved
The following figure gives an overview of the key capabilities of SAP NetWeaver Process Integration
3 SAP NetWeaver PI Overview
2011-04-15 PUBLIC 1356
Figure 1 SAP NetWeaver PI Key Capabilities Overview
SAP NetWeaver Process Integration 71 enables the integration of the applications of the following
communication parties
B2B Party Any business partners that want to integrate their application with other applications
outside their own system landscape Scenarios that require industry standards are supported as
well as any scenarios that do not adhere to a particular industry standard
SAP Applications that run on SAP systems This includes the processing of events by using the
Business Activity Monitoring (BAM) infrastructure
3rd-Party Application Applications from 3rd-party providers within one system landscape for
example database or file-system-based
3rd-Party Middleware Middleware systems from 3rd-party providers that are required for the
integration of applications within a company and across company boundaries
SAP NetWeaver PI also supports internal company scenarios and cross-company scenarios It enables
you to connect systems from different vendors (non-SAP and SAP) in different versions and
implemented in different programming languages (Java ABAP and so on) to each other Like the rest
of the SAP NetWeaver platform SAP NetWeaver PI is based on an open architecture uses open standards
(in particular those from the XML and Java environments) and offers those services that are essential
in a heterogeneous and complex system landscape
To enable end-to-end SOA development SAP NetWeaver Process Integration 71 offers a Universal
Description Discovery and Integration (UDDI) v3-based Services Registry where providers can publish
service endpoints definitions and associated metadata and consumers can discover the appropriate
services for their scenarios The Services Registry provides capabilities for classifying and browsing
3 SAP NetWeaver PI Overview
1456 PUBLIC 2011-04-15
services using semantic-rich classification systems The Services Registry is part of Application Server
Java (AS Java)
31 Installable Software Units
SAP NetWeaver comprises the following three types of installable software units
Systems that are configured for a specific purpose as indicated by one or more usage types
Standalone engines that provide one specific (server) function in combination with one or more
SAP NetWeaver PI systems
Clients used by (many) people from their local front-end PC to access functions offered by systems
of SAP NetWeaver PI or standalone engines in the system landscape
In the following sections you can find more details about the software units The figure below provides
and overview of the software units
Figure 2 Installable Software Units for SAP NetWeaver PI
For this and other figures in this guide the following legend applies
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1556
Figure 3 Legend
311 Systems with Usage Types
SAP systems are the main building blocks of SAP NetWeaver They are identified by unique SAP system
IDs (SAPSIDs) and configured for a certain purpose as indicated by usage types Usage types have the
following characteristics
They are a structuring element for SAP software on a technical level
Usage Types determine the intended purpose of a system and the role it plays in a given (distributed)
use case
They are realized by installing and configuring a collection of software components
They allow a logical view of the technology platform SAP NetWeaver PI
A usage type may require other usage types in the same system to operate
They can also be run in the same system together with other usage types that are not a prerequisite
How SAP NetWeaver Systems are Used
The following sections describe the usage types and their dependencies for SAP NetWeaver PI
Application Server ABAP (AS ABAP)
Purpose
AS ABAP is used to provide the ABAP foundation of SAP NetWeaver PI
Application Server ABAP provides a complete development and runtime environment for ABAP-based
applications It is optimized for the development of highly scalable business applications The ABAP
development and runtime environment makes it possible to develop complex business applications
3 SAP NetWeaver PI Overview
31 Installable Software Units
1656 PUBLIC 2011-04-15
without having to worry explicitly about technical details such as process or memory administration
multi-user capability database connections or similar issues These are provided in the basis services or
are integrated directly in the ABAP runtime The application development is similarly independent of
the underlying platform The application server decouples the application coding completely from the
operating system and database that are used
Dependencies
AS ABAP can be combined optionally with other usage types in one system
Application Server Java (AS Java)
Purpose
AS Java is used to provide the Java foundation of SAP NetWeaver PI using the Java Engine a Java EE-
compliant application server for running enterprise applications In addition to the pure Java EE
standard technologies the Java Engine implements complementary technologies such as Web Dynpro
or Web Services that are targeted at supporting large-scale real-business application development
projects
Dependencies
AS Java can be combined optionally with other usage types in one system
Process Integration (PI)
Purpose
PI consists of core components that model design automate and integrate processes in one or more
application systems For the integration of internal and cross-company processes PI is used to
incorporate all the functions of what was formerly known as Exchange Infrastructure (XI) In addition
PI contains core components for Business Process Management for application-embedded and
application-unbounded processes
The Advanced Adapter Engine is also part of usage type PI You use Advanced Adapter Engine to connect
to SAP systems (RFC adapter) and external systems You use the various adapters in Advanced Adapter
Engine to convert XML- and HTTP-based messages to the specific protocol and format required by
these systems and the other way around You can use the Advanced Adapter Engine that is part of
your PI system as a central Advanced Adapter Engine Optionally (for performance reasons) you can
install a non-central Advanced Adapter Engine [page 19] separately as a system with AS Java and parts of the
usage type PI on a separate host
Dependencies
PI requires AS ABAP and AS Java as prerequisites in the same system
For installing PI it is mandatory to have a dedicated PI system This applies to development quality
and production landscapes It is a prerequisite that no other system in your system landscape has a
higher release and enhancement package level than the PI system If you want to upgrade or install an
application in your system landscape you first have to make sure that the current release and
enhancement package level of the PI system is on the same level - if required you have to upgrade the
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1756
PI system first to the new or a higher release In a dedicated PI system this can be accomplished with a
minimum of downtime Also the PI system would not be affected by the downtime of other usage
types running in the same system
Configuration of Systems with Usage Types
Configuration information is available in the installation guides the configuration wizard and SAP
Solution Manager
In the Installation Guide ndash SAP NetWeaver PI 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt you find
initial technical configuration tasks This guide also informs you about how you can run the
configuration wizard and how you can access the configuration information in SAP Solution
Manager
For certain usage types configuration tasks can be applied by the configuration wizard after the
installation To do this you start the configuration wizard from SAP NetWeaver Administrator
The configuration steps for systems with usage types required for an use case are accessible through
SAP Solution Manager
To be able to use SAP Solution Manager for the configuration tasks you have to import the latest
SAP Solution Manager Implementation Content (Add-On ST-ICO) that is available for your SAP
Solution Manager release For more information see SAP Note 631042 (Release strategy for Implementation
Content (ST-ICO))
SAP Solution Manager Implementation Content is available on SAP Service Marketplace at
httpservicesapcomswdc Installations amp Upgrades Entry by Application Component SAP
Technology Components SAP Solution Manager ltReleasegt Content ST-ICO
In SAP Solution Manager you create a project and a project structure In the configuration phase
you select configuration structures with pre-delivered SAP content for your project You can find
the following different types of configuration tasks in SAP Solution Manager
Mandatory configuration tasks All configuration tasks that are mandatory for the standalone
engine or usage type
Optional configuration tasks Configuration tasks for areas where customers need to decide
if they want to use these functions (for example high availability or security settings)
Additional functions ndash configuration tasks Configuration tasks for functional units that are
used in certain use cases only
A marked checkbox in front of the configuration tasks indicates those configuration tasks that are
relevant for the use case you have chosen To configure ABAP systems SAP Solution Manager
offers executable configuration files (IMG activities)
For information about using SAP Solution Manager Content and creating a configuration guide
see the following documentation
httphelpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Implementing
and Upgrading SAP Solutions Configuration
3 SAP NetWeaver PI Overview
31 Installable Software Units
1856 PUBLIC 2011-04-15
How to Create a Configuration Guide using SAP Solution Manager available at http
servicesapcomsolutionmanager Media Library How-To Documents
Restrictions for Systems with Multiple Usage Types
If you have one system with multiple usage types be aware that we do not provide standard tools
to separate these usage types and distribute them to multiple systems at a later stage For example
if you have a system with usage types A and B you are not able to migrate it with SAP standard
tools into two systems one with usage type A only and the other with usage type B only
In addition we do not provide standard tools to merge multiple systems with different usage types
into one system with multiple usage types at a later stage
If you want to perform these tasks you require specific project support
The following figure shows that SAP standard system copy and migration tools do not support
you in separating or merging systems with usage types
Figure 4 No Support for Merging or Separating Systems with Usage Types
Although you can use one system for multiple usage types client restrictions apply for usage type
PI PI requires a dedicated client due to special PI requirements concerning the client pipeline
Whereas application client pipelines only send and receive messages the central PI pipeline can
also map messages to different formats before sending them
312 Standalone Engines
Standalone engines of SAP NetWeaver are additional installable software units They do not work as
full-blown systems of SAP NetWeaver but as standalone engines that provide a specific (server) function
in combination with one or more SAP NetWeaver systems
Standalone engines are not part of a usage type They do not run on AS ABAP or AS Java
The standalone engines that are available for SAP NetWeaver Process Integration are described in the
following
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1956
Gateway
It is possible to install an SAP instance of an SAP NetWeaver system based exclusively on a standalone
gateway This type of instance does not contain normal work process types (dialog background update
enqueue or spool) Only the gateway process (gwrd) is started If there is an SNA connection to an R
2 system gateway work processes (gwwp) are also started
SAP Conversion Agent by Informatica
SAP Conversion Agent by Informatica is a data conversion tool that enables you to create interfaces
between any data formats and XML-based systems SAP Conversion Agent can convert unstructured
semi-structured and structured formats to XML and the other way around The Conversion Agent
comprises the Conversion Agent Studio and the Conversion Agent Engine In the Conversion Agent
Studio you can develop and configure data conversions The Conversion Agent Engine executes the
data conversions
Search and Classification (TREX)
You can use Search and Classification with SAP NetWeaver PI to search for messages that were previously
indexed Message search using index provides additional methods of searching for specific messages In
addition to static header attributes you can also use adapter-specific message attributes and data from
the message payload for the search A requirement of this however is that the messages are indexed
first You can apply the index-based message search to one or all indexed components of an integration
landscape (domain) Integration Server Adapter Engines and ABAP business systems
For more information see the SAP Library [page 12] at Administratorrsquos Guide Technical Operations for SAP
NetWeaver Administration of SAP NetWeaver Systems Administering PI (Process Integration) Monitoring Index
Administration
Web Dispatcher
The Web Dispatcher lies between the Internet and your SAP system It is the entry point for HTTP(s)
requests into your system which consists of one or more SAP NetWeaver application servers As a
software web switch the Web dispatcher can reject connections or accept them When it accepts a
connection it balances the load to ensure an even distribution across the servers
You can use the Web dispatcher in ABAPJava systems and in pure Java systems as well as in pure ABAP
systems
It is also beneficial to use the Web Dispatcher if you do not need security functions (entry point in the
demilitarized zone (DMZ) SSL URL filtering) but you simply want to balance the load between
multiple SAP NetWeaver Application Server instances
Since Web Dispatcher is optional for every SAP system it is not contained in the system landscape and
the implementation sequence of the use case in this documentation
For more information see the SAP Library [page 12] at Function Oriented View Application Server Infrastructure
SAP Web Dispatcher
3 SAP NetWeaver PI Overview
31 Installable Software Units
2056 PUBLIC 2011-04-15
Advanced Adapter Engine
You use the Advanced Adapter Engine to connect to SAP systems (RFC adapter) and external systems
You use the various adapters in Advanced Adapter Engine to convert XML- and HTTP-based messages
to the specific protocol and format required by these systems and the other way around For specific
senderreceiver combinations messages can be processed without invoking the central Integration
Engine In principle you connect external systems using the adapters that are installed centrally or
non-centrally in Advanced Adapter Engine You can use the Advanced Adapter Engine that is part of
your PI system as a central Advanced Adapter Engine Optionally (for performance reasons) you can
install a non-central Advanced Adapter Engine separately as a system with AS Java and parts of the
usage type PI on a separate host
Adapter Engine (Java SE)
Adapter Engine (Java SE) is a separate software unit You can use it only if you have SAP NetWeaver
systems with usage type PI in your system landscape It has to be installed manually You use the Adapter
Engine (Java SE) to connect to external systems Using the various adapters in the Adapter Engine (Java
SE) XML and HTTP-based messages can be converted to the specific protocol and format required by
such systems and the other way around The Adapter Engine (Java SE) only provides some of these
adapters as a standalone version with restricted functions for operating systems that do not support
SAP NetWeaver PI 71 but that have at least a Java Runtime Environment 50 Therefore you should
use the Adapter Engine (Java SE) only if the platform prerequisites do not allow you to use the Advanced
Adapter Engine
SAP Partner Connectivity Kit
SAP Partner Connectivity Kit (PCK) runs on AS Java with parts of the usage type PI It enables a system
of a smaller company or subsidiary that does not run SAP NetWeaver PI to connect to your SAP
NetWeaver systems
313 Clients
Clients are additional installable programs or tools They reside either on local front-end PCs accessed
by users or on back-end systems where they act as client programs within an SAP NetWeaver system
landscape
The clients that you can use with SAP NetWeaver Process Integration are described in the following
sections
SAP GUI
NOTE
We recommend that you use the following versionsI
SAP GUI for Windows 710 (or higher) with the latest patch level
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 2156
SAP GUI for Java 710 (or higher) with the latest revision
The integrated SAP ITS 710
For more information about the SAP GUI family see SAP Service Marketplace at http
servicesapcomsapgui
SAP offers three different client applications for accessing ABAP applications in SAP systems (such as
SAP NetWeaver systems with usage type AS ABAP) This SAP GUI family consists of
SAP GUI for HTML
SAP GUI for HTML is based on the SAP integrated Internet Transaction Server (ITS) which is
included in the installation of SAP NetWeaver systems as of SAP NetWeaver 2004 On the client
side only a suitable browser (such as Internet Explorer 70 or Firefox 20) and a virtual machine are
required SAP ITS 620 is not compatible with SAP NetWeaver 71
SAP GUI for the Java environment (SAP GUI for Java)
SAP GUI for Java is a generic SAP GUI that covers a variety of platforms
For more information about the installation of SAP GUI for Java see the documentation Installation
Guide ndash SAP Front End
SAP GUI for the Windows environment (SAP GUI for Windows)
SAP GUI for Windows is SAPs universal client for accessing all SAP applications built on ABAP
technology It is available on the Microsoft Windows platform only and offers the broadest feature
set of all members of the SAP GUI family
For more information about the installation of SAP GUI for Windows see the Installation Guide ndash
SAP Front End
SAP NetWeaver Developer Studio
The SAP NetWeaver Developer Studio is SAPrsquos Integrated Development Environment (IDE) for Java
and is based on the open-source tools framework Eclipse 33 With the SAP NetWeaver Developer Studio
you can develop Java EE 5 applications from scratch using the built-in support for new technologies
such as EJB 30 and JSF 12
During the installation of the SAP NetWeaver Developer Studio several features are offered for
installation For SAP NetWeaver PI 71 only the following features are relevant
SAP NetWeaver Developer Studio Platform
SAP NetWeaver Developer Studio Java EE
NOTE
If you want to use one of the other features you need SAP NetWeaver Composition Environment
and a corresponding developers licence
For more information about the installation of SAP NetWeaver Developer Studio see the Installation
Guide ndash SAP NetWeaver Developer Studio 71 or Installation Guide ndash SAP NetWeaver Developer Studio 71 Including
Enhancement Package 1
3 SAP NetWeaver PI Overview
31 Installable Software Units
2256 PUBLIC 2011-04-15
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
SAP enhancement packages are a new way of delivering new functions for SAP NetWeaver This allows
a clear separation between the delivery of new functions on the one hand and corrections legal changes
and security updates on the other hand (in Support Package stacks) SAP enhancement packages are
cumulative an enhancement package always contains the functions of the corresponding predecessor
enhancement packages
Enhancement packages are maintained by their own Support Packages while the main release is in
maintenance
Benefits
SAP enhancement packages offer the following benefits
You have reduced effort for testing and no effort for training when applying Support Packages as
new features are only shipped with enhancement packages
Adding new functions between releases becomes predictable and controllable
New functions can be added successively in small steps There is no need to fully upgrade your
system to get new functions
You have minimal training effort when applying an enhancement package because existing
functions are not replaced
Implementation
There are the following ways to get an SAP NetWeaver system with the release level of SAP enhancement
package 1 for SAP NetWeaver Process Integration 71
New installation of SAP NetWeaver PI 71 including enhancement package 1 using the standard
installation tool SAPinst
Upgrade of an existing SAP NetWeaver system from a release lower than SAP NetWeaver PI 71 to
SAP NetWeaver PI 71 including enhancement package 1 For this you use the upgrade programs
SAPup (for ABAP) and SAPJup (for Java)
Installation of the enhancement package on an existing SAP NetWeaver PI 71 system
For this you use the Software Update Manager (SUM) The Software Update Manager evolved
from the previously used SAP Enhancement Package Installer The tool has been renamed to reflect
its broader use for example you can also use it for applying Support Package Stacks to your system
On the ABAP side the Software Update Manager uses a system cloning and switch procedure for
installing enhancement packages It installs a copy of the system the shadow system parallel to
the original system This shadow system is used to update the relevant software components and
to install the additional components while the original system is still in production operation At
a certain point during downtime the switch to the new system is made and afterwards any parts
of the original system that are no longer needed are deleted The enhancement package installation
in a Java system uses a deploy-based procedure that is no shadow system is used The Software
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2011-04-15 PUBLIC 2356
Update Manager requires a stack configuration file (xml file) as input file for the enhancement
package installation procedure This file lists all the packages that are to be installed in your systems
The stack configuration file is generated when you download the required packages
As the Software Update Manager is updated regularly we recommend to always use the latest
version It is delivered as part of the SL toolset For more information see http
servicesapcomsltoolset
For an overview of all required steps for the enhancement package installation process and
corresponding documents see Process Overview Installation of Enhancement Package 1 on an Existing SAP
Netweaver PI 71 System [page 28]
Content of SAP Enhancement Package 1 for SAP NetWeaver PI 71
With enhancement package 1 for SAP NetWeaver PI 71 new features are introduced and some existing
are changed The following is a selection of some of the most important enhancements
Enhanced design and modelling options in the Enterprise Services Repository
New services registry
Support for new Web services standard (Web Services Reliable Messaging)
New modules for the Advanced Adapter Engine
Use of shared memory of the ABAP Application Server for message processing
For more information about the changes see SAP Library [page 12] at Whatacutes new in SAP NetWeaver PI 71
ndash Release Notes
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2456 PUBLIC 2011-04-15
4 SOA-Based Integration Use Case
41 Overview
You can use SOA-based integration to set up the communication between service providers and service
consumers in both application-to-application and business-to-business scenarios and to execute
operate and monitor the communication at runtime SOA-based integration covers both direct (point-
to-point) as well as mediated (via an Integration Server) communication between service providers and
service consumers
The use case spans the whole life cycle of a SOA-based integration scenario including
Scenario modeling and service design in the Enterprise Services Repository
Implementation of the service provider and consumer in the back-end systems
Configuration and finally execution monitoring and operation of the integration scenario
For scenarios using Integration Server or broker-based communication the configuration of the
different connectivity options (for example SOAP RFC Web Services Industry standards and JDBC)
and their enhancements is covered
For more information see the following documents
Service-Enabling with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdnsoa-modeling
Getting Started
Service-Enabling a Legacy Application with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdn
soa-servicebus Getting Started
In the following you will find information about the installation of the involved software units
42 System Landscape
The following figure shows the system landscape for this use case
4 SOA-Based Integration Use Case
41 Overview
2011-04-15 PUBLIC 2556
Figure 5 SOA-Based Integration
It is mandatory to have a dedicated PI system This applies to development quality and production
landscapes
For PI it is a prerequisite that no other system in your system landscape has a higher release than
the PI system For exceptions to this rule see SAP Note 1043047 For example SAP XI 30 is compatible
with SAP NetWeaver 640 and 70 application systems since the same XI protocol is used Apart
from these exceptions if you want to upgrade or install an application in your system landscape
you first have to make sure that the PI system is on the same release level If required you have to
upgrade the PI system first to the new or a higher release
CAUTION
Although it should be technically possible to run an application system with a higher release
than your PI system in your system landscape this is not supported by SAP (apart from the
exceptions listed in SAP Note 1043047) Therefore you run such a landscape at your own risk
You can use the Advanced Adapter Engine that is part of your PI system as a central Advanced
Adapter Engine
Adapter Engine (Java SE) can be installed in a non-SAP Java environment However it only hosts
a subset of the adapter functionality is only supported for compatibility reasons and should be
used only if this is a precondition in your environment
Optionally you can use the Change Management Service (CMS) of an SAP NetWeaver 70 system
with usage type DI to transport design objects and repository objects For more information see
the SAP Library [page 12] at Administratoracutes Guide Technical Operations for SAP NetWeaver Administration
of SAP NetWeaver Systems PI (Process Integration) Software Logistics Transporting ESR Content and Objects
of Integration Directory PI Transports Using the Change Management Service (CMS)
Smaller business partners or subsidiaries that do not run SAP NetWeaver install SAP Partner
Connectivity Kit in their system landscape SAP Partner Connectivity Kit enables XML document
4 SOA-Based Integration Use Case
42 System Landscape
2656 PUBLIC 2011-04-15
exchange between your SAP NetWeaver systems and the partner systems Since SAP Partner
Connectivity Kit gets installed in their system landscape it is not shown in the system landscape
figure above
The AS ABAP system acts as an application and service provider For Java Web Services you also
require AS Java In addition you require SAP NetWeaver Developer Studio on the client side as a
development environment
The Web service client can be either an SAP or a non-SAP application For example an AS ABAP
system or a Web browser could act as application or service consumer
You can install SAP Conversion Agent by Informatica in the system with usage type PI or on a host
where SAP Partner Connectivity Kit is installed or on a host where neither usage type PI nor SAP
Partner Connectivity Kit is installed
43 Implementation Sequence
Procedure
To install this use case perform the steps listed in the following table
StepAction[Corresponding Documentation] Remarks
1 Make sure that you have performed the preparation steps You have planned your system landscape [page 33]
(that is you have decided how many systems you require how you want to use each of these systems and which standalone engines and clients you require)
With the help of your hardware partner you have mapped your systems and standalone engines to properly sized hosts
You have planned and installed shared services [page 35]
2 Installation of system with usage type PI (includes the installation of AS ABAP and AS Java)
NOTE
For usage type PI a Unicode installation is mandatory
[Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt]
If you want to use the features of enhancement package 1 use the direct installation of SAP NetWeaver PI 71 including enhancement package 1
Make sure that you perform the configuration steps as described in the installation guide For certain usage types configuration tasks can be applied by the configuration wizard These configuration tasks as well as any additional configuration steps for your use case are listed in SAP Solution Manager For more information
4 SOA-Based Integration Use Case
43 Implementation Sequence
2011-04-15 PUBLIC 2756
StepAction[Corresponding Documentation] Remarks
see the Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt
3 Install the Adapter Engine (Java SE) engines if required[Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
4 To integrate small business partners and subsidiaries the business partners or subsidiaries install SAP Partner Connectivity Kit running on AS Java with parts of usage type PI in the business partners or subsidiarys system landscape[Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
5 Install SAP Conversion Agent by Informatica if required[SAP Library [page 12] at Function-Oriented View Process Integration SAP Conversion Agent by Informatica Deploying and Using Conversion Agent ]
6 Installation of clients SAP GUI
[Installation Guide ndash SAP Front End]
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
The process sequences give a comprehensive overview of the steps relevant for the enhancement
package installation on an existing SAP NetWeaver PI 71 system
The process sequence is divided into a planning phase and an implementation phase Each step in both
phases contains references to the corresponding documentation to ensure that you can easily find the
information you need
Process
NOTE
To download the enhancement package files and required Support Packages you require the SAP
Solution Manager Maintenance Optimizer You have the following options
Manual Selection
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2856 PUBLIC 2011-04-15
You manually select the required files from SAP Service Marketplace at http
servicesapcomswdc using the SP Stack Application You use the Maintenance Optimize
only to approve the packages which is a prerequisite for the download
Automatic Calculation
The Maintenance Optimizer supports the download of a consistent queue that includes all
necessary Support Packages and enhancement packages In addition SAP Solution Manager
calculates a valid import queue for the selected SAP system and generates the enhancement
package stack configuration file that you require for the installation
As a prerequisite the system that you want to update needs to be maintained correctly in
SAP Solution Manager System Landscape As the Maintenance Optimizer uses this data for
the calculation it is crucial that the data is up-to-date In addition the SAP Solution Manager
system requires a Minimum Support Package level (see below)
Planing PhaseStep Description Documentation
Hardware amp Software Prerequisites
Check which platforms are supported for your target release (OSDB dependencies)
Product Availability Matrix (PAM) at httpservicesapcompam
Check which hardware sizing is required for your target release
Sizing information at httpservicesapcomsizing
Solution Manager Prerequisites
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of the required software packages you have to make sure that your SAP Solution Manager system has the required Support Package levelAt least SAP Solution Manager 70 EHP1 Support Package Stack 17 is required We recommend to use SAP Solution Manager 70 EHP1 Support Package Stack 23Check if you need to do an update or upgrade of your SAP Solution ManagerMake sure that you run the guided procedure SOLMAN_SETUP after every installation or update of SAP Solution Manager and that it completes successfully
For upgrades from source release SAP Solution Manager 31 and 32Upgrade Guide ndash SAP Solution Manager 70 incl Enhancement Package 1For updates from SAP Solution Manager 70Update Guide SAP Enhancement Package 1 for SAP Solution Manager 70Follow-up activities after an Support Package Stack update or enhancement package updateSolution Operations Guide ndash SAP Solution Manager 70 EHP1 section Software Change Management All guides are available at http
servicesapcom instguides SAP Components SAP Solution Manager -gt Release 70 EHP 1
Implementation PhaseStep Description Documentation
1Solution Manager Preparation
Configure the SAP Solution Manager Maintenance Optimizer
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of software packages make sure your
Configuration of Maintenance Optimizer http
helpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Change Request Management and Change ControlMaintenance Optimizer
Prerequisites
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 2956
Implementation PhaseStep Description Documentation
system landscape data in SAP Solution Manager is maintained correctlyLandscape Verification 10 which is an add-on to SAP Solution Manager can support you in maintaining your system landscape data The use of this tool is optional
Landscape Verification http
wwwsdnsapcom irj
sdn alm-update-
management link Landscape Verification under Related Areas on Upgrade and Update Management (in the right column)
SAP Note 1468605 (Installation of Landscape Verification)
Maintaining System Landscape Information [page 47]Note that the information provided in this section is based on SAP Solution Manager 70 EHP1 SP23
2System Preparation
Prepare your system as described in the documentation for example perform OS DB specific preparations and the PI-specific preparations
Update Guide ndash Update of SAP Systems with Software Update Manager sections Planning and Preparation
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
3Software Download
Select and download the software packages in either of the following ways Automatic calculation Create
a maintenance transaction in the Maintenance Optimizer and choose the Calculate Files Automatically option
Manual Selection Create a maintenance transaction in the Maintenance Optimizer and choose the Select Files Manually option You then can select the files manually using the SP Stack application in SAP Service Marketplace
NOTE
You have to download the stack configuration file manually after you have selected all files in the SP Stack
httphelpsapcom SAP Solutions SAP Solution Manager
SAP Solution Manager 70 EHP1 ltSPgtChange Request Management and
Change Control Maintenance Optimizer Maintenance Procedure Scenarios
For information about the automatic calculation see Maintenance Transaction with Installation of an Enhancement PackageFor information about the manual selection and approval process see section Approve and Download Files in Download Basket
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
3056 PUBLIC 2011-04-15
Implementation PhaseStep Description Documentation
application Choose Generate Stack XML and save the file
4Enhancement Package Installation
Run Software Update Manager to update your system with the selected software packages
Update Guide ndash Update of SAP Systems with Software Update Manager
5Follow-Up Steps
Perform technical and PI-specific follow-up activities after the enhancement package installation is done
Update Guide ndash Update of SAP Systems with Software Update Manager section Follow-Up Activities
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
6Configuration
Configure newly installed enhancement package functions using SAP Solution Manager content
See Systems with Usage Types [page 16] section Configuration of Systems with Usage Types
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 3156
This page is left blank for documents that are printed on both sides
5 System Landscape
51 Planning Your System Landscape
The installable software units that make up your system landscape depend on the functions that you
want to implement For information about the features see systems [page 16] standalone engines [page 19]
and clients [page 21]
In addition you have to determine the required shared services [page 35] (such as SAP Solution Manager
or SAP NetWeaver Administrator) that run on central systems in your system landscape and the
landscape aspects relevant for their implementation
In the following you will find general information that you should consider when planning your system
landscape
Sizing
You have to map systems and standalone engines to hosts after you have a clear picture of the following
Which systems and standalone engines you require
How many systems you require and how you want to use each of these systems
NOTE
No general guideline can be given for the sizing of your landscape since this relies heavily on your
requirements You should therefore perform this task together with your hardware partner and
your technical consultant
For information about sizing your systems you can use the following information sources
Your first point of reference is the Quick Sizer
SAP built the Quick Sizer as an online sizing questionnaire Internet application in close cooperation
with its hardware partners This tool delivers general sizing categories based on your volume load
estimates The results provide an objective basis for sizing independent of platform and
configuration
For more information see SAP Service Marketplace at
httpservicesapcomsizing for the SAP NetWeaver PI 71 sizing guide available under
Sizing Guidelines Business Suite amp Services
httpservicesapcomquicksizer for more information and access to the tool itself
Also consider the following important aspects concerning sizing
High availability
5 System Landscape
51 Planning Your System Landscape
2011-04-15 PUBLIC 3356
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Technical Infrastructure High Availability
Unicode
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Internationalization
Contact your hardware partner to find out the appropriate number of sized hosts
The platform-independent abstract results of the Quick Sizer can be used by any of our hardware
partners to create a concrete offer SAP itself does not make any hardware recommendations the
responsibility for sizing and detailed hardware configuration lies with the hardware partners
Figure 6 Example of Mapping of Systems and Standalone Engines to Three Hosts
NOTE
Optionally you could also distribute single systems to multiple hosts For example you could
decide to install the database instance of an SAP system on a separate host for performance
reasons or distribute other system instances to achieve high availability
To provide a mapping that fits your required functions and performance your hardware partner
and your technical consultant have to identify the number of required instances of SAP NetWeaver
find out how to distribute these instances to hosts and what functions will run on which instance
Therefore the hardware partner and the technical consultant have to consider many different
aspects such as
Number of required SAPS (SAP Application Benchmark Performance Standard) for each
system (provided by Quick Sizer)
Landscape-relevant aspects concerning security For more information see the SAP Security
Guide in the SAP Library [page 12] at Administratoracutes Guide Security Guide
Landscape-relevant aspects concerning scalability high availability operation and software
life-cycle management
5 System Landscape
51 Planning Your System Landscape
3456 PUBLIC 2011-04-15
For more information about relevant aspects for the mapping of systems to hosts see the document
Technical Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
Scaling and Distribution Options
You may need to design your system landscape for a large number of users SAP NetWeaver PI offers
you different means of scalability The following list provides you with some examples
You could install multiple systems of one type and use them for different purposes
You could scale every system by installing dialog instances or by distributing the database instance
For more information about distribution options on the instance level see the Technical
Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
For every SAP system you could additionally install Web Dispatcher For more information see
the SAP Library [page 12] at FunctionndashOriented View Application Server Infrastructure SAP Web
Dispatcher
You could further distribute certain standalone engines ndash for example Search and Classification
(TREX) is based on a flexible architecture that supports a distributed installation For more
information see the Technical Infrastructure Guide ndash SAP NetWeaver PI 71 available in SAP Service
Marketplace at httpservicesapcominstallNWPI71
52 Shared Services
You normally run shared services on central systems in your system landscape The following features
could be used for SAP NetWeaver Process Integration to realize shared services
SAP Solution Manager
Used to implement train test maintain monitor control change and manage incidents of your
SAP solution system landscape (open end-to-end application management)
As of SAP Solution Manager (70) 40 Support Package 15 SAP Solution Manager has become the
platform for SAPs end-to-end solution operations strategy Functions for complete application
management has been combined with administrative tools and has been merged in newly created
role based work centers
NOTE
Be aware that you require an SAP Solution Manager system to install or upgrade to SAP
NetWeaver 70 and higher An SAP Solution Manager system is required to generate the SAP
Solution Manager key needed during the installation or upgrade process Without this key
the installation or upgrade process cannot continue
For SAP NetWeaver Process Integration you require SAP Solution Manager 70
For more information see SAP Note 805390
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3556
Solution Manager Diagnostics
An integral part of SAP Solution Manager that is running as a Java application on the Java stack of
SAP Solution Manager 70 Solution Manager Diagnostics is used to analyze the root cause of
incidents in your landscape in an efficient and safe way Before Go-Live Solution Manager
Diagnostics has to be set up and made accessible remotely
SAP NetWeaver Administrator
SAP NetWeaver Administrator is the central administration component which is used for
monitoring and administering Java applications It is included in SAP NetWeaver systems with AS
Java
SAP NetWeaver Administrator exists in the following flavors
A local mode which runs out of the box and which focuses on administrating the underlying
SAP NetWeaver AS Java
NOTE
For a SAP NetWeaver PI 71 it has a special role which you need to activate using a
configuation wizard
A central mode which has to be configured before use and which deals with the system
landscape management
SAP has decided to merge the central mode of SAP NetWeaver Administrator into the new work
centers available as of SAP Solution Manager 70 SP 15 Thus it can be used in an administrative
context together with non-Java-based administration tools Although the central mode of SAP
NetWeaver Administrator will be still available for some time SAP will not develop this tool any
further SAP focuses on optimizing the administrative work centers of SAP Solution Manager
instead
The local mode of SAP NetWeaver Administrator stays untouched It is available for current and
future releases of SAP NetWeaver
SAP Central Process Scheduling by Redwood
SAP Central Process Scheduling application by Redwood enables central job scheduling and job
monitoring of current and old releases of AS ABAP systems (as of Basis Release 31) This application
is fully integrated in SAP NetWeaver Depending on the business needs SAP business applications
are the initial trigger for scheduled activities You can now manage jobs and job chains conveniently
using a graphical user interface
System Landscape Directory
The System Landscape Directory is the central directory of system landscape information relevant
for the management of your software life-cycle It contains a description of your system landscape
(that is software components that are currently installed) and a repository of software components
that can theoretically be installed in your landscape (such as the software components available
from SAP)
Adaptive Computing Controller
5 System Landscape
52 Shared Services
3656 PUBLIC 2011-04-15
The Adaptive Computing Controller enables users to control an adaptive computing landscape
from a single point through observation operation and dynamic resource distribution With
adaptive computing hardware software and system services are able to adapt to changing business
needs In the Adaptive Computing Controller the run-time data of logical and physical landscapes
can be monitored application services can be startedstoppedrelocated and hardware resources
can be assigned to application services The operation can also be mass executed and be planned as
tasks to be executed
For more information about the installation of the Adaptive Computing Controller tool see the
document Installation Guide ndash Adaptive Computing Controller in SAP NetWeaver 71 available on SAP Service
Marketplace at httpservicesapcominstallNWPI71
For more information about Adaptive Computing in general see httpsdnsapcomirj
sdnadaptive
521 Use Cases
You can use the applications and tools described above for use cases that are normally performed
centrally The following sections describe these use cases
5211 End-to-End Solution Operations
Running business applications through their complete life-cycle is a challenge Therefore SAP has
started the Run SAP methodology for implementing End-to-End Solution Operations Based on a set
of SAP standards a roadmap and a package for training and certification Run SAP helps customers to
facilitate End-to-End Solution Operations
You can download the SAP standards for Solution Operations from SAP Service Marketplace at http
servicesapcomsupportstandards They describe roles customers typically have in their IT
environment For optimal role support SAP has grouped existing and new functions in SAP Solution
Manager work centers as of SAP Solution Manager 70 Support Package 15 Operations aspects are fully
covered by adding administrative functions for SAP NetWeaver as well Work centers are ABAP Web
Dynpro-based applications They offer the following advantages
Easy to use similar look and feel
Context transfer while jumping from one work center into another
Logical grouping of tools for a certain area
Simple authorization concept
Easy to expand
Each IT role belongs to one or more work centers For instance the Technical Administrator IT role is
covered by the work centers for System Monitoring System Administration and Landscape Management
The following work centers are available
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3756
Business Process Operations
Change Management
Root Cause Analysis
Implementation Upgrade
Incident Management
Test Management
Job Management
System Landscape Management
Solution Documentation Assistant
SAP Engagement and Service Delivery
SAP Solution Manager Administration
System Administration
System Monitoring
My Home is the central point of access to all important data of almost all work centers in SAP Solution
Manager
5212 Support Infrastructure
A key requirement for effective support of IT solutions is the ability to perform root cause analysis with
speed and efficiency
With SAP Solution Manager SAP has long had an infrastructure in place for its ABAP applications that
efficiently supports SAP solutions This helps ensure the high availability and smooth running of
business processes For more information see the SAP Solution Manager section
With Solution Manager Diagnostics this knowledge has been extended to Java applications If for
example homegrown Java applications cause instability Solution Manager Diagnostics helps trace the
cause to eradicate the problem rapidly Solution Manager Diagnostics is fully integrated into SAP
Solution Manager 70 Solution Manager Diagnostics also contains two third-party tools CArsquos Wily
Introscopereg for measuring performance as well as troubleshooting problems of the Java EE Engine
and applications running on it and Mercury Loadrunnerreg which enables SAP Support to produce a
defined load in the SAP solution landscape remotely For more information see Solution Manager
Diagnostics [page 43]
The support infrastructure provides SAP Support with safe access to your productive landscape for safe
root cause analysis so ensuring that SAP Support does not change your landscape inadvertently You
require a support infrastructure to run SAP NetWeaver
The following figure shows the overall infrastructure including SAP NetWeaver administration tools
that are used by administrators or operators at the customer site
5 System Landscape
52 Shared Services
3856 PUBLIC 2011-04-15
Landscape Aspects
If you use SAP NetWeaver Process Integration 71 productively besides SAP Solution Manager (as a
central support platform) you have to set up Solution Manager Diagnostics for supportability reasons
Implementation Sequence
For information about the implementation of the support infrastructure see the document Master
Guide ndash SAP Solution Manager 70 available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution Manager ltReleasegt
5213 Collection of Landscape Data
Amongst other applications and services the support infrastructure and the SAP NetWeaver
administration tools rely on system landscape data
For SAP NetWeaver PI 71 you have to run non-ABAP components in your solution landscape
Therefore the System Landscape Directory is mandatory The landscape data that is automatically
gathered by the System Landscape Directory is replicated to SAP Solution Manager There are several
topology options for the System Landscape Directory They offer different grades of availability
administration and operation effort
For more information see the System Landscape Directory section
5214 Authentication and Single Sign-On
Before implementing your system landscape plan how to implement authentication and how to
integrate different systems into a Single Sign-On landscape Single Sign-On reduces complexity for end
users saving them valuable time while also reducing administration effort for resetting passwords
thereby contributing to TCO reduction
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
5215 Integrated User and Access Management
In a system landscape containing a combination of ABAP and Java components we recommend that
you integrate your user and access management so that you can use the same user data across different
systems administer this data centrally and control access to data SAPs mature fine-grained
authorization concept allows detailed control of access rights SAP NetWeaver provides both ABAP and
Java-based user management solutions The user management solution that you use to administer
your user data depends on factors such as the type of systems that are running in your landscape
If you want to use central user administration we recommend that you run it in a non-production
system If you do not have a central user administration yet you can for example realize it in the SAP
Solution Manager system
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3956
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
522 Examples for the Overall System Landscape of Shared Services
In this section we provide examples of how shared services can be set up depending on the system
landscape they are intended for The following examples aggregate the landscape aspects given in the
Use Cases section
NOTE
The following sections and the figure mostly do not show information about the life-cycle of
shared services For example you may also need a development and testquality assurance system
for SAP Solution Manager You should consider this aspect in addition to the information given
in this section based on your requirements
Small and MediumndashSized Customer Landscapes with Java
As you use Java productively for SAP NetWeaver PI 71 besides SAP Solution Manager you have to set
up additional components for optimal monitoring administration and support Solution Manager
Diagnostics and the central mode of SAP NetWeaver Administrator are already fully integrated into
SAP Solution Manager 70 as the central operations hub For SAP Process Integration you must also
set up SAP NetWeaver Administrator with a special role
We recommend that you do not install SAP Central Process Scheduling in the SAP Solution Manager
system You have to set up and operate the system which hosts your productive scheduler as a mission
critical system
In the SAP Solution Manager system you should set up a local System Landscape Directory in addition
to a central runtime System Landscape Directory This way you have a clear separation between your
management system (SAP Solution Manager) and managed systems in your landscape In addition
SAP Solution Manager then does not rely on a System Landscape Directory running in the production
environment For this setup configure the SLD data suppliers of your SAP Solution Manager system
to send data to the central runtime System Landscape Directory In addition configure automatic
bridge forwarding from your runtime System Landscape Directory to the local System Landscape
Directory For more information see the Planning Guide - System Landscape Directory
If you want to use a central system for Adobe Document Services we recommend that you install a
dedicated system for this purpose in your production environment For detailed information about
the sizing of the system for the different use cases see the Sizing Guide for Adobe Document Services at
SAP Service Marketplace at httpservicesapcomsizing Sizing Guidelines Solutions amp
Platform
We recommend that you start with this centralized SAP Solution Manager approach as depicted in the
following figure
5 System Landscape
52 Shared Services
4056 PUBLIC 2011-04-15
Figure 7 Single SAP Solution Manager Landscape
Large Customer Landscapes with Java
Large customers who have environments in their landscape that are large and distributed administered
by different groups or separated for security reasons can consider a distributed operations setup In
addition to the centralized setup described for small- and medium-sized customers above large
customers can put parts of the central management functions on extra hosts or systems for performance
or policy reasons You have the following options for a distributed setup
You may set up an extra system or client for Central User Administration (CUA)
The Change and Transport System (CTS) can run on an extra system However it is not
performance- or data-intensive
You may set up an extra system for central CCMS monitoring Depending on the customizing
and on the landscape size central CCMS may generate a lot of system load You can connect a
separate central CCMS to SAP Solution Manager for displaying alerts in the alert inbox of the System
Monitoring work center
You can use a separate SAP NetWeaver 70 system with usage type BI together with SAP Solution
Manager This may make sense with respect to the amount of landscape management data that is
stored for reporting purposes The amount of data strongly depends on the data granularity
storage time frame and landscape size
You can easily put Wily Introscope Enterprise Manager on an separate host
Other aspects described above for small- and medium-customers (such as the setup of the System
Landscape Directory) are also valid for large customers
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4156
523 Feature Details
This section provides further information about the features described above
5231 SAP Solution Manager
SAP provides you with SAP Solution Manager as the strategic application management platform and
to enable the collaboration between you and SAP You need to install at least one productive SAP
Solution Manager in your system landscape To ensure the availability of this application management
platform an SAP Solution Manager system is technically required to install or upgrade to SAP
NetWeaver 70 or higher If you are already using SAP Solution Manager you can also use it to manage
the solution you build with SAP NetWeaver In this case we highly recommend that you update SAP
Solution Manager to the latest version
As of SAP Solution Manager 70 SP15 you can use the newly created work centers
NOTE
During the SAP system installation or upgrade process you are prompted to enter the SAP
Solution Manager key An SAP Solution Manager system is required to generate this key Without
this key the installation or upgrade process cannot continue
You may generate all needed keys for your entire system landscape (development quality
assurance and production system) in one SAP Solution Manager system In case you plan to install
several solution landscapes (for example in different countries) one SAP Solution Manager
system is still sufficient
For more information see SAP Note 805390
It is possible to install multiple SAP Solution Managers If you do so they should host separate business
solutions
If you want to reduce the risk of unavailability you should not install SAP Solution Manager as a central
component Instead you can operate a 2-system-landscape with both a test and production
environment of SAP Solution Manager (especially if you are using time-critical functions like Support
Desk) If you also develop your own content a 3-system-landscape with a development test and
production environment is recommended
For more information about SAP Solution Manager see the following table
Topic Where to Find More Information
System infrastructure scenarios installation and configuration of SAP Solution Manager
Master Guide ndash SAP Solution Manager available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution ManagerltReleasegt
Benefits and usage scenarios SAP Solution Manager ndash Learning Maps available on SAP Service Marketplace at http
5 System Landscape
52 Shared Services
4256 PUBLIC 2011-04-15
Topic Where to Find More Informationservicesapcomrkt-solman or https
servicesapcomsolutionmanager
Additional information See SAP Service Marketplace at http
servicesapcomsolutionmanager
5232 Solution Manager Diagnostics
Solution Manager Diagnostics provides efficient and safe root-cause analysis of incidents in customer
solutions powered by SAP NetWeaver It can help monitor on operating systems databases Java
application activities performance and logs It also supports the reporting of software and
configuration changes that can lead to malfunctions and errors
You must run one Solution Manager Diagnostics within your SAP solution landscape if you run
applications based on SAP NetWeaver systems with usage type AS Java Agents are responsible for
delivering the data from all productive hosts within your system landscape to the Solution Manager
Diagnostics system
CAUTION
SAP Support performs root-cause analysis on incoming incidents with Solution Manager
Diagnostics Not installing and configuring this support infrastructure results in a dramatically
reduced service level
Solution Manager Diagnostics is fully integrated into SAP Solution Manager 70
Solution Manager Diagnostics also contains Wily Introscope (Display Server and Agent part) for
measuring performance as well as to troubleshoot problems of Non-ABAP applications Wily Introscope
is heavily used for troubleshooting applications running on AS Java
SAP has signed a distribution agreement for Wily Introscope SAP customers are allowed to use this
tool in a preconfigured way
For more information about Solution Manager Diagnostics and an FAQ list see SAP Service Marketplace
at httpservicesapcomdiagnostics
5233 System Landscape Directory
The System Landscape Directory (SLD) of SAP NetWeaver is the central directory of system landscape
information relevant for the management of your software life-cycle
NOTE
Note that the abbreviation SLD is not intended to define a product since the System Landscape
Directory is part of SAP NetWeaver This abbreviation is solely intended to improve readability
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4356
The System Landscape Directory contains a description of your system landscape (that is software
components that are currently installed) and a repository of software components that can
theoretically be installed in your landscape (such as the software components available from SAP)
Since this data gets updated automatically the System Landscape Directory provides reliable and up-
to-date system landscape information with as little effort for you as possible In this way the System
Landscape Directory acts as a central information provider for SAP and third-party tools that use this
data to deliver the services you need to keep your landscape up and running
For the System Landscape Directory as part of an SAP NetWeaver PI 71 landscape consider the following
aspects
Part of SAP NetWeaver PI 71 is a new version of the System Landscape Directory It is automatically
included in every SAP NetWeaver 71 system with usage type AS Java It offers enhanced functions
such as a full automatic synchronization mechanism for all data stored in it That is both data
delivered by data suppliers and data entered or changed manually in the System Landscape
Directory can be synchronized automatically This synchronization offers the following
A fully automated mechanism so no user interaction is required and conflicts are resolved
automatically
Asynchronous propagation of information so some nodes may be down temporarily
Communication over HTTP protocol
Uni- and bi-directional synchronization
Depending on your use case the full automatic synchronization could significantly reduce manual
synchronization effort
For SAP NetWeaver PI 71 the configuration of the system landscape directory and its data suppliers
is already included in the standard implementation procedure with SAPinst For existing systems
you only have to perform some quick and easy configuration actions to start operating the system
landscape directory server in an AS Java system
For SAP NetWeaver PI 71 you have the following options concerning SLD
Option 1
Run SAP NetWeaver PI 71 against an existing SLD running on SAP NetWeaver 70 We only
recommend this for upgrades from SAP NetWeaver 70 if you have a central SLD in operation
not running on one of your PI systems
Option 2
Use the SLD included in an SAP NetWeaver PI 71 system We recommend this option for new
installations and upgrades from older releases than SAP NetWeaver 70 due to the enhanced
functions and improved performance of SLD 71
NOTE
If you already have a central SLD running on SAP NetWeaver 70 in operation you could run
two SLD versions in parallel ndash SLD running on SAP NetWeaver 71 for your PI systems and
SLD running on SAP NetWeaver 70 for all other systemsuse cases This way your SAP
5 System Landscape
52 Shared Services
4456 PUBLIC 2011-04-15
NetWeaver PI 71 systems would benefit from the new features while it would be easy to set
up and operate such an SLD landscape For this purpose you could use the new fully
automatic synchronization This feature enables the automatic forwarding of all SLD data
from an SLD running on SAP NetWeaver 70 to an SLD running on SAP NetWeaver 71 As a
result there is no need to adapt most existing systems as their SLD data suppliers could still
send their data to the central SLD In brief the following steps would be required
1 Put SLD in a PI system into operation (part of standard implementation procedure)
2 Configure PI systems to use the new SLD (part of standard implementation procedure
for new PI systems)
3 Set up the fully automatic synchronization from your old SLD to your new SLD
As soon as an upgrade or an installation of a standalone AS Java 71 system is available you
could move your central SLD also to SAP NetWeaver 71 Then you could optionally shift
your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems
Figure 8
We recommend that you use a Domain Name System (DNS) alias so that you are able to switch to
another System Landscape Directory easily For example if customers build a new landscape they
normally start with a sandbox environment Over time more and more environments are set up
Once the production environment is in place move the System Landscape Directory there To do
this you can configure a new System Landscape Directory in the production environment
synchronize it with the old System Landscape directory and switch to the new one
Topology
Apart from the considerations above the System Landscape Directory offers several topology options
with different grades of availability at the expense of low administration and operation effort There is
no generic rule therefore on how to set up a System Landscape Directory in your system landscape
To find the topology and synchronization strategy for the System Landscape Directory that fits your
requirements concerning the System Landscape Directory availability (and hence the availability of
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4556
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2011-04-15 PUBLIC 356
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
456 PUBLIC 2011-04-15
Document History
CAUTION
Before you start the implementation make sure you have the latest version of this document
You can find the latest version on SAP Service Marketplace httpservicesapcom
instguides
The following table provides an overview on the most important document changes
Version Date Description
10 2007-12-07 First version
11 2008-02-05 Changes to System Landscape Directory section Minor changes
12 2008-04-22 Major revision of Shared Services section
13 2008-05-29 Information about dedicated PI system updated
14 2008-12-12 Restructuring of content according to use case concept Information about SAP enhancement package 1 for SAP NetWeaver PI 71 added
15 2009-03-19 Minor changes (mainly language corrections)
16 2009-03-20 Minor error corrections
17 2011-04-15 Section SAP Enhancement Package 1 for SAP NetWeaver PI 71 updated (Software Update Manager replaces SAP Enhancement Package Installer)
Section Process Sequence Installation of Enhancement Package 1 on an Existing SAP NetWeaver PI 71 system added
Section Maintaining System Landscape Information added Further minor changes
2011-04-15 PUBLIC 556
Table of Contents
Chapter 1 Introduction 9
Chapter 2 Before You Start 11
21 SAP Notes 11
22 More Information 11
23 Accessing the SAP Library 12
Chapter 3 SAP NetWeaver PI Overview 13
31 Installable Software Units 15
311 Systems with Usage Types 16
312 Standalone Engines 19
313 Clients 21
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration
71 23
Chapter 4 SOA-Based Integration Use Case 25
41 Overview 25
42 System Landscape 25
43 Implementation Sequence 27
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP
Netweaver PI 71 System 28
Chapter 5 System Landscape 33
51 Planning Your System Landscape 33
52 Shared Services 35
521 Use Cases 37
5211 End-to-End Solution Operations 37
5212 Support Infrastructure 38
5213 Collection of Landscape Data 39
5214 Authentication and Single Sign-On 39
5215 Integrated User and Access Management 39
522 Examples for the Overall System Landscape of Shared Services 40
656 PUBLIC 2011-04-15
523 Feature Details 42
5231 SAP Solution Manager 42
5232 Solution Manager Diagnostics 43
5233 System Landscape Directory 43
Chapter A Appendix 47
A1 Maintaining System Landscape Information 47
Chapter B Reference 51
B1 The Main SAP Documentation Types 51
B2 List of Documentation 51
2011-04-15 PUBLIC 756
This page is left blank for documents that are printed on both sides
1 Introduction
This Master Guide provides you with a central starting point for the technical implementation of SAP
NetWeaverreg Process Integration (SAP NetWeaver PI) It also contains information about enhancement
package 1 for SAP NetWeaver Process Integration 71
SAP NetWeaver PI 71 is based on an established architecture for realizing cross-system business processes
and supporting an service-oriented architecture (SOA) The focus is on the service-based integration
of applications
Structure of the Master Guide
The Master Guide consists of the following sections
Introduction
Contains an introduction to this guide
Before You Start
Contains information about this document important things which you need to know before you
start and information on how to access the SAP Library
SAP NetWeaver Overview
Describes the building blocks of SAP NetWeaver PI
SOA-Based Integration Use Case
Introduces the use case and explains how to install it
System Landscape
Contains information about how to install your system landscape
Reference
Contains information about the overall documentation concept for SAP systems
CAUTION
Make sure you have the latest version of the Master Guide by checking SAP Service Marketplace
immediately before starting the installation
The Master Guide is regularly updated on SAP Service Marketplace at http
servicesapcominstallnwpi71 Planning
Constraints
The business scenarios that are presented here serve as examples of how you can use SAP software in
your company The business scenarios are intended only as models and do not necessarily run the way
they are described here in your customer-specific system landscape Check your requirements and
systems to determine whether these scenarios can be used productively at your site Furthermore we
1 Introduction
2011-04-15 PUBLIC 956
recommend that you test these scenarios thoroughly in your test systems to ensure that they are
complete and free of errors before going live
1 Introduction
1056 PUBLIC 2011-04-15
2 Before You Start
21 SAP Notes
You must read the following SAP Notes before you use this Master Guide and implement SAP NetWeaver
Make sure that you have the up-to-date version of each SAP Note which you can find on SAP Service
Marketplace at httpservicesapcomnotes
NOTE
The SAP Notes related to SAP NetWeaver PI 71 are also listed on SAP Service Marketplace at
httpservicesapcomsapnotesnwpi71
List of Important SAP Notes
SAP Note Number Title Description
1004107 Release Restrictions for SAP NetWeaver PI 71
Some restrictions apply to the productive use of SAP NetWeaver PI 71 These are documented in this SAP Note
1247043 Release Restrictions for SAP EHP1 for SAP NetWeaver PI 71
Some restrictions apply to the productive use of enhancement package 1 for SAP NetWeaver PI 71 These are documented in this SAP Note
22 More Information
The following table contains links to information available on SAP Service Marketplace or in the SAP
Library which is important for implementing SAP NetWeaver
Content Location on SAP Service Marketplace or in SAP Library
The latest version of the installation and upgrade guides for SAP NetWeaver Process Integration
httpservicesapcominstguidesnwpi71
Information about supported platforms (operating systems databases browsers) for all SAP NetWeaver components
httpservicesapcomplatforms Product Availability Matrix
Sizing of SAP NetWeaver httpservicesapcomsizing
Information about security SAP Security Guide See the SAP Library [page 12] at Adminitstratoracutes Guide Security Guide
Information about the technical operation of SAP NetWeaver
Technical Operations Manual See the SAP Library [page 12] at Adminitstratoracutes Guide Technical Operations for SAP NetWeaver
2 Before You Start
21 SAP Notes
2011-04-15 PUBLIC 1156
Content Location on SAP Service Marketplace or in SAP Library
Information about SAP NetWeaver PI Support Package Stacks
httpservicesapcomnetweaver SAP NetWeaver PI 71- Release-Specific Information Support Package Stacks Information
Information about installing SAP NetWeaver Support Package Stacks
httpservicesapcomMaintenanceNWPI71
Support Package Stack Guide ndash SAP NetWeaver
23 Accessing the SAP Library
For more information about SAP NetWeaver Process Integration access the SAP Library from any of
the following
SAP Help Portal at httphelpsapcomNWPI71 SAP NetWeaver Process Integration 71 Library
ltLanguagegt SAP NetWeaver Process Integration Library
CAUTION
The SAP Help Portal contains the latest version of the SAP Library Therefore we recommend
that you use this channel to access the SAP Library
An SAP system if you have installed the online documentation Choose Help SAP Library
The browser starts
The help files on the online documentation CDs or DVDs
If you want to view the help files in HTMLHelp format from the online documentation CDs or
DVDs you need a PC running Microsoft Windows to install the HTMLHelp Viewer
2 Before You Start
23 Accessing the SAP Library
1256 PUBLIC 2011-04-15
3 SAP NetWeaver PI Overview
Introduction
SAP NetWeaver PI 71 is part of the SAP NetWeaver technology platform The complete offering of the
SAP NetWeaver technology platform is visualized in the SAP NetWeaver technology map which you
can access at httpsdnsapcomnetweaver SAP NetWeaver at a Glance The technology map
enables you to drill down from top-level technology areas (for example Lifecycle Management) to
individual capabilities (for example Administration Monitoring and so on)
SAP NetWeaver PI includes the following capabilities
Repository-based Modeling and Design
Service Bus-based Integration
SOA Management
A different view is introduced by the end-to-end use case concept This concept offers an
implementation view on SAP NetWeaver to structure and facilitate your implementation
A use cases is a process that typically involves several SAP NetWeaver capabilities It is not limited to a
single component or capability A use case guides you through the different phases of your
implementation project ndash from information through installation to the configuration phase This
implies that a uses case addresses several user roles administrator power user and end user
This document describes the SOA-based integration use case
Architecture Principals
The architecture of SAP NetWeaver Process Integration 71 (SAP NetWeaver PI 71) is based on an
established architecture for realizing cross-system business processes and is a further development of
lower releases (SAP NetWeaver 70 usage type Process Integration and SAP XI 30 as part of SAP
NetWeaver 2004) SAP NetWeaver PI 71 plays an important role in supporting an service-oriented
architecture (SOA) The focus is on the service-based integration of applications
SAP NetWeaver PI is based on general standards so as to enable 3rd-party systems to be integrated At
the center of SAP NetWeaver PI is an XML-based communication that uses HTTP (Hyper Text Transfer
Protocol) Irrespective of the scenario used the application-specific contents are transferred in messages
in user-defined XML (eXtensible Markup Language) from the sender to the receiver either via the
Integration Server or directly between the systems involved
The following figure gives an overview of the key capabilities of SAP NetWeaver Process Integration
3 SAP NetWeaver PI Overview
2011-04-15 PUBLIC 1356
Figure 1 SAP NetWeaver PI Key Capabilities Overview
SAP NetWeaver Process Integration 71 enables the integration of the applications of the following
communication parties
B2B Party Any business partners that want to integrate their application with other applications
outside their own system landscape Scenarios that require industry standards are supported as
well as any scenarios that do not adhere to a particular industry standard
SAP Applications that run on SAP systems This includes the processing of events by using the
Business Activity Monitoring (BAM) infrastructure
3rd-Party Application Applications from 3rd-party providers within one system landscape for
example database or file-system-based
3rd-Party Middleware Middleware systems from 3rd-party providers that are required for the
integration of applications within a company and across company boundaries
SAP NetWeaver PI also supports internal company scenarios and cross-company scenarios It enables
you to connect systems from different vendors (non-SAP and SAP) in different versions and
implemented in different programming languages (Java ABAP and so on) to each other Like the rest
of the SAP NetWeaver platform SAP NetWeaver PI is based on an open architecture uses open standards
(in particular those from the XML and Java environments) and offers those services that are essential
in a heterogeneous and complex system landscape
To enable end-to-end SOA development SAP NetWeaver Process Integration 71 offers a Universal
Description Discovery and Integration (UDDI) v3-based Services Registry where providers can publish
service endpoints definitions and associated metadata and consumers can discover the appropriate
services for their scenarios The Services Registry provides capabilities for classifying and browsing
3 SAP NetWeaver PI Overview
1456 PUBLIC 2011-04-15
services using semantic-rich classification systems The Services Registry is part of Application Server
Java (AS Java)
31 Installable Software Units
SAP NetWeaver comprises the following three types of installable software units
Systems that are configured for a specific purpose as indicated by one or more usage types
Standalone engines that provide one specific (server) function in combination with one or more
SAP NetWeaver PI systems
Clients used by (many) people from their local front-end PC to access functions offered by systems
of SAP NetWeaver PI or standalone engines in the system landscape
In the following sections you can find more details about the software units The figure below provides
and overview of the software units
Figure 2 Installable Software Units for SAP NetWeaver PI
For this and other figures in this guide the following legend applies
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1556
Figure 3 Legend
311 Systems with Usage Types
SAP systems are the main building blocks of SAP NetWeaver They are identified by unique SAP system
IDs (SAPSIDs) and configured for a certain purpose as indicated by usage types Usage types have the
following characteristics
They are a structuring element for SAP software on a technical level
Usage Types determine the intended purpose of a system and the role it plays in a given (distributed)
use case
They are realized by installing and configuring a collection of software components
They allow a logical view of the technology platform SAP NetWeaver PI
A usage type may require other usage types in the same system to operate
They can also be run in the same system together with other usage types that are not a prerequisite
How SAP NetWeaver Systems are Used
The following sections describe the usage types and their dependencies for SAP NetWeaver PI
Application Server ABAP (AS ABAP)
Purpose
AS ABAP is used to provide the ABAP foundation of SAP NetWeaver PI
Application Server ABAP provides a complete development and runtime environment for ABAP-based
applications It is optimized for the development of highly scalable business applications The ABAP
development and runtime environment makes it possible to develop complex business applications
3 SAP NetWeaver PI Overview
31 Installable Software Units
1656 PUBLIC 2011-04-15
without having to worry explicitly about technical details such as process or memory administration
multi-user capability database connections or similar issues These are provided in the basis services or
are integrated directly in the ABAP runtime The application development is similarly independent of
the underlying platform The application server decouples the application coding completely from the
operating system and database that are used
Dependencies
AS ABAP can be combined optionally with other usage types in one system
Application Server Java (AS Java)
Purpose
AS Java is used to provide the Java foundation of SAP NetWeaver PI using the Java Engine a Java EE-
compliant application server for running enterprise applications In addition to the pure Java EE
standard technologies the Java Engine implements complementary technologies such as Web Dynpro
or Web Services that are targeted at supporting large-scale real-business application development
projects
Dependencies
AS Java can be combined optionally with other usage types in one system
Process Integration (PI)
Purpose
PI consists of core components that model design automate and integrate processes in one or more
application systems For the integration of internal and cross-company processes PI is used to
incorporate all the functions of what was formerly known as Exchange Infrastructure (XI) In addition
PI contains core components for Business Process Management for application-embedded and
application-unbounded processes
The Advanced Adapter Engine is also part of usage type PI You use Advanced Adapter Engine to connect
to SAP systems (RFC adapter) and external systems You use the various adapters in Advanced Adapter
Engine to convert XML- and HTTP-based messages to the specific protocol and format required by
these systems and the other way around You can use the Advanced Adapter Engine that is part of
your PI system as a central Advanced Adapter Engine Optionally (for performance reasons) you can
install a non-central Advanced Adapter Engine [page 19] separately as a system with AS Java and parts of the
usage type PI on a separate host
Dependencies
PI requires AS ABAP and AS Java as prerequisites in the same system
For installing PI it is mandatory to have a dedicated PI system This applies to development quality
and production landscapes It is a prerequisite that no other system in your system landscape has a
higher release and enhancement package level than the PI system If you want to upgrade or install an
application in your system landscape you first have to make sure that the current release and
enhancement package level of the PI system is on the same level - if required you have to upgrade the
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1756
PI system first to the new or a higher release In a dedicated PI system this can be accomplished with a
minimum of downtime Also the PI system would not be affected by the downtime of other usage
types running in the same system
Configuration of Systems with Usage Types
Configuration information is available in the installation guides the configuration wizard and SAP
Solution Manager
In the Installation Guide ndash SAP NetWeaver PI 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt you find
initial technical configuration tasks This guide also informs you about how you can run the
configuration wizard and how you can access the configuration information in SAP Solution
Manager
For certain usage types configuration tasks can be applied by the configuration wizard after the
installation To do this you start the configuration wizard from SAP NetWeaver Administrator
The configuration steps for systems with usage types required for an use case are accessible through
SAP Solution Manager
To be able to use SAP Solution Manager for the configuration tasks you have to import the latest
SAP Solution Manager Implementation Content (Add-On ST-ICO) that is available for your SAP
Solution Manager release For more information see SAP Note 631042 (Release strategy for Implementation
Content (ST-ICO))
SAP Solution Manager Implementation Content is available on SAP Service Marketplace at
httpservicesapcomswdc Installations amp Upgrades Entry by Application Component SAP
Technology Components SAP Solution Manager ltReleasegt Content ST-ICO
In SAP Solution Manager you create a project and a project structure In the configuration phase
you select configuration structures with pre-delivered SAP content for your project You can find
the following different types of configuration tasks in SAP Solution Manager
Mandatory configuration tasks All configuration tasks that are mandatory for the standalone
engine or usage type
Optional configuration tasks Configuration tasks for areas where customers need to decide
if they want to use these functions (for example high availability or security settings)
Additional functions ndash configuration tasks Configuration tasks for functional units that are
used in certain use cases only
A marked checkbox in front of the configuration tasks indicates those configuration tasks that are
relevant for the use case you have chosen To configure ABAP systems SAP Solution Manager
offers executable configuration files (IMG activities)
For information about using SAP Solution Manager Content and creating a configuration guide
see the following documentation
httphelpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Implementing
and Upgrading SAP Solutions Configuration
3 SAP NetWeaver PI Overview
31 Installable Software Units
1856 PUBLIC 2011-04-15
How to Create a Configuration Guide using SAP Solution Manager available at http
servicesapcomsolutionmanager Media Library How-To Documents
Restrictions for Systems with Multiple Usage Types
If you have one system with multiple usage types be aware that we do not provide standard tools
to separate these usage types and distribute them to multiple systems at a later stage For example
if you have a system with usage types A and B you are not able to migrate it with SAP standard
tools into two systems one with usage type A only and the other with usage type B only
In addition we do not provide standard tools to merge multiple systems with different usage types
into one system with multiple usage types at a later stage
If you want to perform these tasks you require specific project support
The following figure shows that SAP standard system copy and migration tools do not support
you in separating or merging systems with usage types
Figure 4 No Support for Merging or Separating Systems with Usage Types
Although you can use one system for multiple usage types client restrictions apply for usage type
PI PI requires a dedicated client due to special PI requirements concerning the client pipeline
Whereas application client pipelines only send and receive messages the central PI pipeline can
also map messages to different formats before sending them
312 Standalone Engines
Standalone engines of SAP NetWeaver are additional installable software units They do not work as
full-blown systems of SAP NetWeaver but as standalone engines that provide a specific (server) function
in combination with one or more SAP NetWeaver systems
Standalone engines are not part of a usage type They do not run on AS ABAP or AS Java
The standalone engines that are available for SAP NetWeaver Process Integration are described in the
following
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1956
Gateway
It is possible to install an SAP instance of an SAP NetWeaver system based exclusively on a standalone
gateway This type of instance does not contain normal work process types (dialog background update
enqueue or spool) Only the gateway process (gwrd) is started If there is an SNA connection to an R
2 system gateway work processes (gwwp) are also started
SAP Conversion Agent by Informatica
SAP Conversion Agent by Informatica is a data conversion tool that enables you to create interfaces
between any data formats and XML-based systems SAP Conversion Agent can convert unstructured
semi-structured and structured formats to XML and the other way around The Conversion Agent
comprises the Conversion Agent Studio and the Conversion Agent Engine In the Conversion Agent
Studio you can develop and configure data conversions The Conversion Agent Engine executes the
data conversions
Search and Classification (TREX)
You can use Search and Classification with SAP NetWeaver PI to search for messages that were previously
indexed Message search using index provides additional methods of searching for specific messages In
addition to static header attributes you can also use adapter-specific message attributes and data from
the message payload for the search A requirement of this however is that the messages are indexed
first You can apply the index-based message search to one or all indexed components of an integration
landscape (domain) Integration Server Adapter Engines and ABAP business systems
For more information see the SAP Library [page 12] at Administratorrsquos Guide Technical Operations for SAP
NetWeaver Administration of SAP NetWeaver Systems Administering PI (Process Integration) Monitoring Index
Administration
Web Dispatcher
The Web Dispatcher lies between the Internet and your SAP system It is the entry point for HTTP(s)
requests into your system which consists of one or more SAP NetWeaver application servers As a
software web switch the Web dispatcher can reject connections or accept them When it accepts a
connection it balances the load to ensure an even distribution across the servers
You can use the Web dispatcher in ABAPJava systems and in pure Java systems as well as in pure ABAP
systems
It is also beneficial to use the Web Dispatcher if you do not need security functions (entry point in the
demilitarized zone (DMZ) SSL URL filtering) but you simply want to balance the load between
multiple SAP NetWeaver Application Server instances
Since Web Dispatcher is optional for every SAP system it is not contained in the system landscape and
the implementation sequence of the use case in this documentation
For more information see the SAP Library [page 12] at Function Oriented View Application Server Infrastructure
SAP Web Dispatcher
3 SAP NetWeaver PI Overview
31 Installable Software Units
2056 PUBLIC 2011-04-15
Advanced Adapter Engine
You use the Advanced Adapter Engine to connect to SAP systems (RFC adapter) and external systems
You use the various adapters in Advanced Adapter Engine to convert XML- and HTTP-based messages
to the specific protocol and format required by these systems and the other way around For specific
senderreceiver combinations messages can be processed without invoking the central Integration
Engine In principle you connect external systems using the adapters that are installed centrally or
non-centrally in Advanced Adapter Engine You can use the Advanced Adapter Engine that is part of
your PI system as a central Advanced Adapter Engine Optionally (for performance reasons) you can
install a non-central Advanced Adapter Engine separately as a system with AS Java and parts of the
usage type PI on a separate host
Adapter Engine (Java SE)
Adapter Engine (Java SE) is a separate software unit You can use it only if you have SAP NetWeaver
systems with usage type PI in your system landscape It has to be installed manually You use the Adapter
Engine (Java SE) to connect to external systems Using the various adapters in the Adapter Engine (Java
SE) XML and HTTP-based messages can be converted to the specific protocol and format required by
such systems and the other way around The Adapter Engine (Java SE) only provides some of these
adapters as a standalone version with restricted functions for operating systems that do not support
SAP NetWeaver PI 71 but that have at least a Java Runtime Environment 50 Therefore you should
use the Adapter Engine (Java SE) only if the platform prerequisites do not allow you to use the Advanced
Adapter Engine
SAP Partner Connectivity Kit
SAP Partner Connectivity Kit (PCK) runs on AS Java with parts of the usage type PI It enables a system
of a smaller company or subsidiary that does not run SAP NetWeaver PI to connect to your SAP
NetWeaver systems
313 Clients
Clients are additional installable programs or tools They reside either on local front-end PCs accessed
by users or on back-end systems where they act as client programs within an SAP NetWeaver system
landscape
The clients that you can use with SAP NetWeaver Process Integration are described in the following
sections
SAP GUI
NOTE
We recommend that you use the following versionsI
SAP GUI for Windows 710 (or higher) with the latest patch level
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 2156
SAP GUI for Java 710 (or higher) with the latest revision
The integrated SAP ITS 710
For more information about the SAP GUI family see SAP Service Marketplace at http
servicesapcomsapgui
SAP offers three different client applications for accessing ABAP applications in SAP systems (such as
SAP NetWeaver systems with usage type AS ABAP) This SAP GUI family consists of
SAP GUI for HTML
SAP GUI for HTML is based on the SAP integrated Internet Transaction Server (ITS) which is
included in the installation of SAP NetWeaver systems as of SAP NetWeaver 2004 On the client
side only a suitable browser (such as Internet Explorer 70 or Firefox 20) and a virtual machine are
required SAP ITS 620 is not compatible with SAP NetWeaver 71
SAP GUI for the Java environment (SAP GUI for Java)
SAP GUI for Java is a generic SAP GUI that covers a variety of platforms
For more information about the installation of SAP GUI for Java see the documentation Installation
Guide ndash SAP Front End
SAP GUI for the Windows environment (SAP GUI for Windows)
SAP GUI for Windows is SAPs universal client for accessing all SAP applications built on ABAP
technology It is available on the Microsoft Windows platform only and offers the broadest feature
set of all members of the SAP GUI family
For more information about the installation of SAP GUI for Windows see the Installation Guide ndash
SAP Front End
SAP NetWeaver Developer Studio
The SAP NetWeaver Developer Studio is SAPrsquos Integrated Development Environment (IDE) for Java
and is based on the open-source tools framework Eclipse 33 With the SAP NetWeaver Developer Studio
you can develop Java EE 5 applications from scratch using the built-in support for new technologies
such as EJB 30 and JSF 12
During the installation of the SAP NetWeaver Developer Studio several features are offered for
installation For SAP NetWeaver PI 71 only the following features are relevant
SAP NetWeaver Developer Studio Platform
SAP NetWeaver Developer Studio Java EE
NOTE
If you want to use one of the other features you need SAP NetWeaver Composition Environment
and a corresponding developers licence
For more information about the installation of SAP NetWeaver Developer Studio see the Installation
Guide ndash SAP NetWeaver Developer Studio 71 or Installation Guide ndash SAP NetWeaver Developer Studio 71 Including
Enhancement Package 1
3 SAP NetWeaver PI Overview
31 Installable Software Units
2256 PUBLIC 2011-04-15
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
SAP enhancement packages are a new way of delivering new functions for SAP NetWeaver This allows
a clear separation between the delivery of new functions on the one hand and corrections legal changes
and security updates on the other hand (in Support Package stacks) SAP enhancement packages are
cumulative an enhancement package always contains the functions of the corresponding predecessor
enhancement packages
Enhancement packages are maintained by their own Support Packages while the main release is in
maintenance
Benefits
SAP enhancement packages offer the following benefits
You have reduced effort for testing and no effort for training when applying Support Packages as
new features are only shipped with enhancement packages
Adding new functions between releases becomes predictable and controllable
New functions can be added successively in small steps There is no need to fully upgrade your
system to get new functions
You have minimal training effort when applying an enhancement package because existing
functions are not replaced
Implementation
There are the following ways to get an SAP NetWeaver system with the release level of SAP enhancement
package 1 for SAP NetWeaver Process Integration 71
New installation of SAP NetWeaver PI 71 including enhancement package 1 using the standard
installation tool SAPinst
Upgrade of an existing SAP NetWeaver system from a release lower than SAP NetWeaver PI 71 to
SAP NetWeaver PI 71 including enhancement package 1 For this you use the upgrade programs
SAPup (for ABAP) and SAPJup (for Java)
Installation of the enhancement package on an existing SAP NetWeaver PI 71 system
For this you use the Software Update Manager (SUM) The Software Update Manager evolved
from the previously used SAP Enhancement Package Installer The tool has been renamed to reflect
its broader use for example you can also use it for applying Support Package Stacks to your system
On the ABAP side the Software Update Manager uses a system cloning and switch procedure for
installing enhancement packages It installs a copy of the system the shadow system parallel to
the original system This shadow system is used to update the relevant software components and
to install the additional components while the original system is still in production operation At
a certain point during downtime the switch to the new system is made and afterwards any parts
of the original system that are no longer needed are deleted The enhancement package installation
in a Java system uses a deploy-based procedure that is no shadow system is used The Software
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2011-04-15 PUBLIC 2356
Update Manager requires a stack configuration file (xml file) as input file for the enhancement
package installation procedure This file lists all the packages that are to be installed in your systems
The stack configuration file is generated when you download the required packages
As the Software Update Manager is updated regularly we recommend to always use the latest
version It is delivered as part of the SL toolset For more information see http
servicesapcomsltoolset
For an overview of all required steps for the enhancement package installation process and
corresponding documents see Process Overview Installation of Enhancement Package 1 on an Existing SAP
Netweaver PI 71 System [page 28]
Content of SAP Enhancement Package 1 for SAP NetWeaver PI 71
With enhancement package 1 for SAP NetWeaver PI 71 new features are introduced and some existing
are changed The following is a selection of some of the most important enhancements
Enhanced design and modelling options in the Enterprise Services Repository
New services registry
Support for new Web services standard (Web Services Reliable Messaging)
New modules for the Advanced Adapter Engine
Use of shared memory of the ABAP Application Server for message processing
For more information about the changes see SAP Library [page 12] at Whatacutes new in SAP NetWeaver PI 71
ndash Release Notes
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2456 PUBLIC 2011-04-15
4 SOA-Based Integration Use Case
41 Overview
You can use SOA-based integration to set up the communication between service providers and service
consumers in both application-to-application and business-to-business scenarios and to execute
operate and monitor the communication at runtime SOA-based integration covers both direct (point-
to-point) as well as mediated (via an Integration Server) communication between service providers and
service consumers
The use case spans the whole life cycle of a SOA-based integration scenario including
Scenario modeling and service design in the Enterprise Services Repository
Implementation of the service provider and consumer in the back-end systems
Configuration and finally execution monitoring and operation of the integration scenario
For scenarios using Integration Server or broker-based communication the configuration of the
different connectivity options (for example SOAP RFC Web Services Industry standards and JDBC)
and their enhancements is covered
For more information see the following documents
Service-Enabling with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdnsoa-modeling
Getting Started
Service-Enabling a Legacy Application with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdn
soa-servicebus Getting Started
In the following you will find information about the installation of the involved software units
42 System Landscape
The following figure shows the system landscape for this use case
4 SOA-Based Integration Use Case
41 Overview
2011-04-15 PUBLIC 2556
Figure 5 SOA-Based Integration
It is mandatory to have a dedicated PI system This applies to development quality and production
landscapes
For PI it is a prerequisite that no other system in your system landscape has a higher release than
the PI system For exceptions to this rule see SAP Note 1043047 For example SAP XI 30 is compatible
with SAP NetWeaver 640 and 70 application systems since the same XI protocol is used Apart
from these exceptions if you want to upgrade or install an application in your system landscape
you first have to make sure that the PI system is on the same release level If required you have to
upgrade the PI system first to the new or a higher release
CAUTION
Although it should be technically possible to run an application system with a higher release
than your PI system in your system landscape this is not supported by SAP (apart from the
exceptions listed in SAP Note 1043047) Therefore you run such a landscape at your own risk
You can use the Advanced Adapter Engine that is part of your PI system as a central Advanced
Adapter Engine
Adapter Engine (Java SE) can be installed in a non-SAP Java environment However it only hosts
a subset of the adapter functionality is only supported for compatibility reasons and should be
used only if this is a precondition in your environment
Optionally you can use the Change Management Service (CMS) of an SAP NetWeaver 70 system
with usage type DI to transport design objects and repository objects For more information see
the SAP Library [page 12] at Administratoracutes Guide Technical Operations for SAP NetWeaver Administration
of SAP NetWeaver Systems PI (Process Integration) Software Logistics Transporting ESR Content and Objects
of Integration Directory PI Transports Using the Change Management Service (CMS)
Smaller business partners or subsidiaries that do not run SAP NetWeaver install SAP Partner
Connectivity Kit in their system landscape SAP Partner Connectivity Kit enables XML document
4 SOA-Based Integration Use Case
42 System Landscape
2656 PUBLIC 2011-04-15
exchange between your SAP NetWeaver systems and the partner systems Since SAP Partner
Connectivity Kit gets installed in their system landscape it is not shown in the system landscape
figure above
The AS ABAP system acts as an application and service provider For Java Web Services you also
require AS Java In addition you require SAP NetWeaver Developer Studio on the client side as a
development environment
The Web service client can be either an SAP or a non-SAP application For example an AS ABAP
system or a Web browser could act as application or service consumer
You can install SAP Conversion Agent by Informatica in the system with usage type PI or on a host
where SAP Partner Connectivity Kit is installed or on a host where neither usage type PI nor SAP
Partner Connectivity Kit is installed
43 Implementation Sequence
Procedure
To install this use case perform the steps listed in the following table
StepAction[Corresponding Documentation] Remarks
1 Make sure that you have performed the preparation steps You have planned your system landscape [page 33]
(that is you have decided how many systems you require how you want to use each of these systems and which standalone engines and clients you require)
With the help of your hardware partner you have mapped your systems and standalone engines to properly sized hosts
You have planned and installed shared services [page 35]
2 Installation of system with usage type PI (includes the installation of AS ABAP and AS Java)
NOTE
For usage type PI a Unicode installation is mandatory
[Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt]
If you want to use the features of enhancement package 1 use the direct installation of SAP NetWeaver PI 71 including enhancement package 1
Make sure that you perform the configuration steps as described in the installation guide For certain usage types configuration tasks can be applied by the configuration wizard These configuration tasks as well as any additional configuration steps for your use case are listed in SAP Solution Manager For more information
4 SOA-Based Integration Use Case
43 Implementation Sequence
2011-04-15 PUBLIC 2756
StepAction[Corresponding Documentation] Remarks
see the Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt
3 Install the Adapter Engine (Java SE) engines if required[Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
4 To integrate small business partners and subsidiaries the business partners or subsidiaries install SAP Partner Connectivity Kit running on AS Java with parts of usage type PI in the business partners or subsidiarys system landscape[Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
5 Install SAP Conversion Agent by Informatica if required[SAP Library [page 12] at Function-Oriented View Process Integration SAP Conversion Agent by Informatica Deploying and Using Conversion Agent ]
6 Installation of clients SAP GUI
[Installation Guide ndash SAP Front End]
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
The process sequences give a comprehensive overview of the steps relevant for the enhancement
package installation on an existing SAP NetWeaver PI 71 system
The process sequence is divided into a planning phase and an implementation phase Each step in both
phases contains references to the corresponding documentation to ensure that you can easily find the
information you need
Process
NOTE
To download the enhancement package files and required Support Packages you require the SAP
Solution Manager Maintenance Optimizer You have the following options
Manual Selection
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2856 PUBLIC 2011-04-15
You manually select the required files from SAP Service Marketplace at http
servicesapcomswdc using the SP Stack Application You use the Maintenance Optimize
only to approve the packages which is a prerequisite for the download
Automatic Calculation
The Maintenance Optimizer supports the download of a consistent queue that includes all
necessary Support Packages and enhancement packages In addition SAP Solution Manager
calculates a valid import queue for the selected SAP system and generates the enhancement
package stack configuration file that you require for the installation
As a prerequisite the system that you want to update needs to be maintained correctly in
SAP Solution Manager System Landscape As the Maintenance Optimizer uses this data for
the calculation it is crucial that the data is up-to-date In addition the SAP Solution Manager
system requires a Minimum Support Package level (see below)
Planing PhaseStep Description Documentation
Hardware amp Software Prerequisites
Check which platforms are supported for your target release (OSDB dependencies)
Product Availability Matrix (PAM) at httpservicesapcompam
Check which hardware sizing is required for your target release
Sizing information at httpservicesapcomsizing
Solution Manager Prerequisites
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of the required software packages you have to make sure that your SAP Solution Manager system has the required Support Package levelAt least SAP Solution Manager 70 EHP1 Support Package Stack 17 is required We recommend to use SAP Solution Manager 70 EHP1 Support Package Stack 23Check if you need to do an update or upgrade of your SAP Solution ManagerMake sure that you run the guided procedure SOLMAN_SETUP after every installation or update of SAP Solution Manager and that it completes successfully
For upgrades from source release SAP Solution Manager 31 and 32Upgrade Guide ndash SAP Solution Manager 70 incl Enhancement Package 1For updates from SAP Solution Manager 70Update Guide SAP Enhancement Package 1 for SAP Solution Manager 70Follow-up activities after an Support Package Stack update or enhancement package updateSolution Operations Guide ndash SAP Solution Manager 70 EHP1 section Software Change Management All guides are available at http
servicesapcom instguides SAP Components SAP Solution Manager -gt Release 70 EHP 1
Implementation PhaseStep Description Documentation
1Solution Manager Preparation
Configure the SAP Solution Manager Maintenance Optimizer
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of software packages make sure your
Configuration of Maintenance Optimizer http
helpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Change Request Management and Change ControlMaintenance Optimizer
Prerequisites
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 2956
Implementation PhaseStep Description Documentation
system landscape data in SAP Solution Manager is maintained correctlyLandscape Verification 10 which is an add-on to SAP Solution Manager can support you in maintaining your system landscape data The use of this tool is optional
Landscape Verification http
wwwsdnsapcom irj
sdn alm-update-
management link Landscape Verification under Related Areas on Upgrade and Update Management (in the right column)
SAP Note 1468605 (Installation of Landscape Verification)
Maintaining System Landscape Information [page 47]Note that the information provided in this section is based on SAP Solution Manager 70 EHP1 SP23
2System Preparation
Prepare your system as described in the documentation for example perform OS DB specific preparations and the PI-specific preparations
Update Guide ndash Update of SAP Systems with Software Update Manager sections Planning and Preparation
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
3Software Download
Select and download the software packages in either of the following ways Automatic calculation Create
a maintenance transaction in the Maintenance Optimizer and choose the Calculate Files Automatically option
Manual Selection Create a maintenance transaction in the Maintenance Optimizer and choose the Select Files Manually option You then can select the files manually using the SP Stack application in SAP Service Marketplace
NOTE
You have to download the stack configuration file manually after you have selected all files in the SP Stack
httphelpsapcom SAP Solutions SAP Solution Manager
SAP Solution Manager 70 EHP1 ltSPgtChange Request Management and
Change Control Maintenance Optimizer Maintenance Procedure Scenarios
For information about the automatic calculation see Maintenance Transaction with Installation of an Enhancement PackageFor information about the manual selection and approval process see section Approve and Download Files in Download Basket
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
3056 PUBLIC 2011-04-15
Implementation PhaseStep Description Documentation
application Choose Generate Stack XML and save the file
4Enhancement Package Installation
Run Software Update Manager to update your system with the selected software packages
Update Guide ndash Update of SAP Systems with Software Update Manager
5Follow-Up Steps
Perform technical and PI-specific follow-up activities after the enhancement package installation is done
Update Guide ndash Update of SAP Systems with Software Update Manager section Follow-Up Activities
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
6Configuration
Configure newly installed enhancement package functions using SAP Solution Manager content
See Systems with Usage Types [page 16] section Configuration of Systems with Usage Types
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 3156
This page is left blank for documents that are printed on both sides
5 System Landscape
51 Planning Your System Landscape
The installable software units that make up your system landscape depend on the functions that you
want to implement For information about the features see systems [page 16] standalone engines [page 19]
and clients [page 21]
In addition you have to determine the required shared services [page 35] (such as SAP Solution Manager
or SAP NetWeaver Administrator) that run on central systems in your system landscape and the
landscape aspects relevant for their implementation
In the following you will find general information that you should consider when planning your system
landscape
Sizing
You have to map systems and standalone engines to hosts after you have a clear picture of the following
Which systems and standalone engines you require
How many systems you require and how you want to use each of these systems
NOTE
No general guideline can be given for the sizing of your landscape since this relies heavily on your
requirements You should therefore perform this task together with your hardware partner and
your technical consultant
For information about sizing your systems you can use the following information sources
Your first point of reference is the Quick Sizer
SAP built the Quick Sizer as an online sizing questionnaire Internet application in close cooperation
with its hardware partners This tool delivers general sizing categories based on your volume load
estimates The results provide an objective basis for sizing independent of platform and
configuration
For more information see SAP Service Marketplace at
httpservicesapcomsizing for the SAP NetWeaver PI 71 sizing guide available under
Sizing Guidelines Business Suite amp Services
httpservicesapcomquicksizer for more information and access to the tool itself
Also consider the following important aspects concerning sizing
High availability
5 System Landscape
51 Planning Your System Landscape
2011-04-15 PUBLIC 3356
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Technical Infrastructure High Availability
Unicode
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Internationalization
Contact your hardware partner to find out the appropriate number of sized hosts
The platform-independent abstract results of the Quick Sizer can be used by any of our hardware
partners to create a concrete offer SAP itself does not make any hardware recommendations the
responsibility for sizing and detailed hardware configuration lies with the hardware partners
Figure 6 Example of Mapping of Systems and Standalone Engines to Three Hosts
NOTE
Optionally you could also distribute single systems to multiple hosts For example you could
decide to install the database instance of an SAP system on a separate host for performance
reasons or distribute other system instances to achieve high availability
To provide a mapping that fits your required functions and performance your hardware partner
and your technical consultant have to identify the number of required instances of SAP NetWeaver
find out how to distribute these instances to hosts and what functions will run on which instance
Therefore the hardware partner and the technical consultant have to consider many different
aspects such as
Number of required SAPS (SAP Application Benchmark Performance Standard) for each
system (provided by Quick Sizer)
Landscape-relevant aspects concerning security For more information see the SAP Security
Guide in the SAP Library [page 12] at Administratoracutes Guide Security Guide
Landscape-relevant aspects concerning scalability high availability operation and software
life-cycle management
5 System Landscape
51 Planning Your System Landscape
3456 PUBLIC 2011-04-15
For more information about relevant aspects for the mapping of systems to hosts see the document
Technical Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
Scaling and Distribution Options
You may need to design your system landscape for a large number of users SAP NetWeaver PI offers
you different means of scalability The following list provides you with some examples
You could install multiple systems of one type and use them for different purposes
You could scale every system by installing dialog instances or by distributing the database instance
For more information about distribution options on the instance level see the Technical
Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
For every SAP system you could additionally install Web Dispatcher For more information see
the SAP Library [page 12] at FunctionndashOriented View Application Server Infrastructure SAP Web
Dispatcher
You could further distribute certain standalone engines ndash for example Search and Classification
(TREX) is based on a flexible architecture that supports a distributed installation For more
information see the Technical Infrastructure Guide ndash SAP NetWeaver PI 71 available in SAP Service
Marketplace at httpservicesapcominstallNWPI71
52 Shared Services
You normally run shared services on central systems in your system landscape The following features
could be used for SAP NetWeaver Process Integration to realize shared services
SAP Solution Manager
Used to implement train test maintain monitor control change and manage incidents of your
SAP solution system landscape (open end-to-end application management)
As of SAP Solution Manager (70) 40 Support Package 15 SAP Solution Manager has become the
platform for SAPs end-to-end solution operations strategy Functions for complete application
management has been combined with administrative tools and has been merged in newly created
role based work centers
NOTE
Be aware that you require an SAP Solution Manager system to install or upgrade to SAP
NetWeaver 70 and higher An SAP Solution Manager system is required to generate the SAP
Solution Manager key needed during the installation or upgrade process Without this key
the installation or upgrade process cannot continue
For SAP NetWeaver Process Integration you require SAP Solution Manager 70
For more information see SAP Note 805390
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3556
Solution Manager Diagnostics
An integral part of SAP Solution Manager that is running as a Java application on the Java stack of
SAP Solution Manager 70 Solution Manager Diagnostics is used to analyze the root cause of
incidents in your landscape in an efficient and safe way Before Go-Live Solution Manager
Diagnostics has to be set up and made accessible remotely
SAP NetWeaver Administrator
SAP NetWeaver Administrator is the central administration component which is used for
monitoring and administering Java applications It is included in SAP NetWeaver systems with AS
Java
SAP NetWeaver Administrator exists in the following flavors
A local mode which runs out of the box and which focuses on administrating the underlying
SAP NetWeaver AS Java
NOTE
For a SAP NetWeaver PI 71 it has a special role which you need to activate using a
configuation wizard
A central mode which has to be configured before use and which deals with the system
landscape management
SAP has decided to merge the central mode of SAP NetWeaver Administrator into the new work
centers available as of SAP Solution Manager 70 SP 15 Thus it can be used in an administrative
context together with non-Java-based administration tools Although the central mode of SAP
NetWeaver Administrator will be still available for some time SAP will not develop this tool any
further SAP focuses on optimizing the administrative work centers of SAP Solution Manager
instead
The local mode of SAP NetWeaver Administrator stays untouched It is available for current and
future releases of SAP NetWeaver
SAP Central Process Scheduling by Redwood
SAP Central Process Scheduling application by Redwood enables central job scheduling and job
monitoring of current and old releases of AS ABAP systems (as of Basis Release 31) This application
is fully integrated in SAP NetWeaver Depending on the business needs SAP business applications
are the initial trigger for scheduled activities You can now manage jobs and job chains conveniently
using a graphical user interface
System Landscape Directory
The System Landscape Directory is the central directory of system landscape information relevant
for the management of your software life-cycle It contains a description of your system landscape
(that is software components that are currently installed) and a repository of software components
that can theoretically be installed in your landscape (such as the software components available
from SAP)
Adaptive Computing Controller
5 System Landscape
52 Shared Services
3656 PUBLIC 2011-04-15
The Adaptive Computing Controller enables users to control an adaptive computing landscape
from a single point through observation operation and dynamic resource distribution With
adaptive computing hardware software and system services are able to adapt to changing business
needs In the Adaptive Computing Controller the run-time data of logical and physical landscapes
can be monitored application services can be startedstoppedrelocated and hardware resources
can be assigned to application services The operation can also be mass executed and be planned as
tasks to be executed
For more information about the installation of the Adaptive Computing Controller tool see the
document Installation Guide ndash Adaptive Computing Controller in SAP NetWeaver 71 available on SAP Service
Marketplace at httpservicesapcominstallNWPI71
For more information about Adaptive Computing in general see httpsdnsapcomirj
sdnadaptive
521 Use Cases
You can use the applications and tools described above for use cases that are normally performed
centrally The following sections describe these use cases
5211 End-to-End Solution Operations
Running business applications through their complete life-cycle is a challenge Therefore SAP has
started the Run SAP methodology for implementing End-to-End Solution Operations Based on a set
of SAP standards a roadmap and a package for training and certification Run SAP helps customers to
facilitate End-to-End Solution Operations
You can download the SAP standards for Solution Operations from SAP Service Marketplace at http
servicesapcomsupportstandards They describe roles customers typically have in their IT
environment For optimal role support SAP has grouped existing and new functions in SAP Solution
Manager work centers as of SAP Solution Manager 70 Support Package 15 Operations aspects are fully
covered by adding administrative functions for SAP NetWeaver as well Work centers are ABAP Web
Dynpro-based applications They offer the following advantages
Easy to use similar look and feel
Context transfer while jumping from one work center into another
Logical grouping of tools for a certain area
Simple authorization concept
Easy to expand
Each IT role belongs to one or more work centers For instance the Technical Administrator IT role is
covered by the work centers for System Monitoring System Administration and Landscape Management
The following work centers are available
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3756
Business Process Operations
Change Management
Root Cause Analysis
Implementation Upgrade
Incident Management
Test Management
Job Management
System Landscape Management
Solution Documentation Assistant
SAP Engagement and Service Delivery
SAP Solution Manager Administration
System Administration
System Monitoring
My Home is the central point of access to all important data of almost all work centers in SAP Solution
Manager
5212 Support Infrastructure
A key requirement for effective support of IT solutions is the ability to perform root cause analysis with
speed and efficiency
With SAP Solution Manager SAP has long had an infrastructure in place for its ABAP applications that
efficiently supports SAP solutions This helps ensure the high availability and smooth running of
business processes For more information see the SAP Solution Manager section
With Solution Manager Diagnostics this knowledge has been extended to Java applications If for
example homegrown Java applications cause instability Solution Manager Diagnostics helps trace the
cause to eradicate the problem rapidly Solution Manager Diagnostics is fully integrated into SAP
Solution Manager 70 Solution Manager Diagnostics also contains two third-party tools CArsquos Wily
Introscopereg for measuring performance as well as troubleshooting problems of the Java EE Engine
and applications running on it and Mercury Loadrunnerreg which enables SAP Support to produce a
defined load in the SAP solution landscape remotely For more information see Solution Manager
Diagnostics [page 43]
The support infrastructure provides SAP Support with safe access to your productive landscape for safe
root cause analysis so ensuring that SAP Support does not change your landscape inadvertently You
require a support infrastructure to run SAP NetWeaver
The following figure shows the overall infrastructure including SAP NetWeaver administration tools
that are used by administrators or operators at the customer site
5 System Landscape
52 Shared Services
3856 PUBLIC 2011-04-15
Landscape Aspects
If you use SAP NetWeaver Process Integration 71 productively besides SAP Solution Manager (as a
central support platform) you have to set up Solution Manager Diagnostics for supportability reasons
Implementation Sequence
For information about the implementation of the support infrastructure see the document Master
Guide ndash SAP Solution Manager 70 available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution Manager ltReleasegt
5213 Collection of Landscape Data
Amongst other applications and services the support infrastructure and the SAP NetWeaver
administration tools rely on system landscape data
For SAP NetWeaver PI 71 you have to run non-ABAP components in your solution landscape
Therefore the System Landscape Directory is mandatory The landscape data that is automatically
gathered by the System Landscape Directory is replicated to SAP Solution Manager There are several
topology options for the System Landscape Directory They offer different grades of availability
administration and operation effort
For more information see the System Landscape Directory section
5214 Authentication and Single Sign-On
Before implementing your system landscape plan how to implement authentication and how to
integrate different systems into a Single Sign-On landscape Single Sign-On reduces complexity for end
users saving them valuable time while also reducing administration effort for resetting passwords
thereby contributing to TCO reduction
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
5215 Integrated User and Access Management
In a system landscape containing a combination of ABAP and Java components we recommend that
you integrate your user and access management so that you can use the same user data across different
systems administer this data centrally and control access to data SAPs mature fine-grained
authorization concept allows detailed control of access rights SAP NetWeaver provides both ABAP and
Java-based user management solutions The user management solution that you use to administer
your user data depends on factors such as the type of systems that are running in your landscape
If you want to use central user administration we recommend that you run it in a non-production
system If you do not have a central user administration yet you can for example realize it in the SAP
Solution Manager system
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3956
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
522 Examples for the Overall System Landscape of Shared Services
In this section we provide examples of how shared services can be set up depending on the system
landscape they are intended for The following examples aggregate the landscape aspects given in the
Use Cases section
NOTE
The following sections and the figure mostly do not show information about the life-cycle of
shared services For example you may also need a development and testquality assurance system
for SAP Solution Manager You should consider this aspect in addition to the information given
in this section based on your requirements
Small and MediumndashSized Customer Landscapes with Java
As you use Java productively for SAP NetWeaver PI 71 besides SAP Solution Manager you have to set
up additional components for optimal monitoring administration and support Solution Manager
Diagnostics and the central mode of SAP NetWeaver Administrator are already fully integrated into
SAP Solution Manager 70 as the central operations hub For SAP Process Integration you must also
set up SAP NetWeaver Administrator with a special role
We recommend that you do not install SAP Central Process Scheduling in the SAP Solution Manager
system You have to set up and operate the system which hosts your productive scheduler as a mission
critical system
In the SAP Solution Manager system you should set up a local System Landscape Directory in addition
to a central runtime System Landscape Directory This way you have a clear separation between your
management system (SAP Solution Manager) and managed systems in your landscape In addition
SAP Solution Manager then does not rely on a System Landscape Directory running in the production
environment For this setup configure the SLD data suppliers of your SAP Solution Manager system
to send data to the central runtime System Landscape Directory In addition configure automatic
bridge forwarding from your runtime System Landscape Directory to the local System Landscape
Directory For more information see the Planning Guide - System Landscape Directory
If you want to use a central system for Adobe Document Services we recommend that you install a
dedicated system for this purpose in your production environment For detailed information about
the sizing of the system for the different use cases see the Sizing Guide for Adobe Document Services at
SAP Service Marketplace at httpservicesapcomsizing Sizing Guidelines Solutions amp
Platform
We recommend that you start with this centralized SAP Solution Manager approach as depicted in the
following figure
5 System Landscape
52 Shared Services
4056 PUBLIC 2011-04-15
Figure 7 Single SAP Solution Manager Landscape
Large Customer Landscapes with Java
Large customers who have environments in their landscape that are large and distributed administered
by different groups or separated for security reasons can consider a distributed operations setup In
addition to the centralized setup described for small- and medium-sized customers above large
customers can put parts of the central management functions on extra hosts or systems for performance
or policy reasons You have the following options for a distributed setup
You may set up an extra system or client for Central User Administration (CUA)
The Change and Transport System (CTS) can run on an extra system However it is not
performance- or data-intensive
You may set up an extra system for central CCMS monitoring Depending on the customizing
and on the landscape size central CCMS may generate a lot of system load You can connect a
separate central CCMS to SAP Solution Manager for displaying alerts in the alert inbox of the System
Monitoring work center
You can use a separate SAP NetWeaver 70 system with usage type BI together with SAP Solution
Manager This may make sense with respect to the amount of landscape management data that is
stored for reporting purposes The amount of data strongly depends on the data granularity
storage time frame and landscape size
You can easily put Wily Introscope Enterprise Manager on an separate host
Other aspects described above for small- and medium-customers (such as the setup of the System
Landscape Directory) are also valid for large customers
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4156
523 Feature Details
This section provides further information about the features described above
5231 SAP Solution Manager
SAP provides you with SAP Solution Manager as the strategic application management platform and
to enable the collaboration between you and SAP You need to install at least one productive SAP
Solution Manager in your system landscape To ensure the availability of this application management
platform an SAP Solution Manager system is technically required to install or upgrade to SAP
NetWeaver 70 or higher If you are already using SAP Solution Manager you can also use it to manage
the solution you build with SAP NetWeaver In this case we highly recommend that you update SAP
Solution Manager to the latest version
As of SAP Solution Manager 70 SP15 you can use the newly created work centers
NOTE
During the SAP system installation or upgrade process you are prompted to enter the SAP
Solution Manager key An SAP Solution Manager system is required to generate this key Without
this key the installation or upgrade process cannot continue
You may generate all needed keys for your entire system landscape (development quality
assurance and production system) in one SAP Solution Manager system In case you plan to install
several solution landscapes (for example in different countries) one SAP Solution Manager
system is still sufficient
For more information see SAP Note 805390
It is possible to install multiple SAP Solution Managers If you do so they should host separate business
solutions
If you want to reduce the risk of unavailability you should not install SAP Solution Manager as a central
component Instead you can operate a 2-system-landscape with both a test and production
environment of SAP Solution Manager (especially if you are using time-critical functions like Support
Desk) If you also develop your own content a 3-system-landscape with a development test and
production environment is recommended
For more information about SAP Solution Manager see the following table
Topic Where to Find More Information
System infrastructure scenarios installation and configuration of SAP Solution Manager
Master Guide ndash SAP Solution Manager available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution ManagerltReleasegt
Benefits and usage scenarios SAP Solution Manager ndash Learning Maps available on SAP Service Marketplace at http
5 System Landscape
52 Shared Services
4256 PUBLIC 2011-04-15
Topic Where to Find More Informationservicesapcomrkt-solman or https
servicesapcomsolutionmanager
Additional information See SAP Service Marketplace at http
servicesapcomsolutionmanager
5232 Solution Manager Diagnostics
Solution Manager Diagnostics provides efficient and safe root-cause analysis of incidents in customer
solutions powered by SAP NetWeaver It can help monitor on operating systems databases Java
application activities performance and logs It also supports the reporting of software and
configuration changes that can lead to malfunctions and errors
You must run one Solution Manager Diagnostics within your SAP solution landscape if you run
applications based on SAP NetWeaver systems with usage type AS Java Agents are responsible for
delivering the data from all productive hosts within your system landscape to the Solution Manager
Diagnostics system
CAUTION
SAP Support performs root-cause analysis on incoming incidents with Solution Manager
Diagnostics Not installing and configuring this support infrastructure results in a dramatically
reduced service level
Solution Manager Diagnostics is fully integrated into SAP Solution Manager 70
Solution Manager Diagnostics also contains Wily Introscope (Display Server and Agent part) for
measuring performance as well as to troubleshoot problems of Non-ABAP applications Wily Introscope
is heavily used for troubleshooting applications running on AS Java
SAP has signed a distribution agreement for Wily Introscope SAP customers are allowed to use this
tool in a preconfigured way
For more information about Solution Manager Diagnostics and an FAQ list see SAP Service Marketplace
at httpservicesapcomdiagnostics
5233 System Landscape Directory
The System Landscape Directory (SLD) of SAP NetWeaver is the central directory of system landscape
information relevant for the management of your software life-cycle
NOTE
Note that the abbreviation SLD is not intended to define a product since the System Landscape
Directory is part of SAP NetWeaver This abbreviation is solely intended to improve readability
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4356
The System Landscape Directory contains a description of your system landscape (that is software
components that are currently installed) and a repository of software components that can
theoretically be installed in your landscape (such as the software components available from SAP)
Since this data gets updated automatically the System Landscape Directory provides reliable and up-
to-date system landscape information with as little effort for you as possible In this way the System
Landscape Directory acts as a central information provider for SAP and third-party tools that use this
data to deliver the services you need to keep your landscape up and running
For the System Landscape Directory as part of an SAP NetWeaver PI 71 landscape consider the following
aspects
Part of SAP NetWeaver PI 71 is a new version of the System Landscape Directory It is automatically
included in every SAP NetWeaver 71 system with usage type AS Java It offers enhanced functions
such as a full automatic synchronization mechanism for all data stored in it That is both data
delivered by data suppliers and data entered or changed manually in the System Landscape
Directory can be synchronized automatically This synchronization offers the following
A fully automated mechanism so no user interaction is required and conflicts are resolved
automatically
Asynchronous propagation of information so some nodes may be down temporarily
Communication over HTTP protocol
Uni- and bi-directional synchronization
Depending on your use case the full automatic synchronization could significantly reduce manual
synchronization effort
For SAP NetWeaver PI 71 the configuration of the system landscape directory and its data suppliers
is already included in the standard implementation procedure with SAPinst For existing systems
you only have to perform some quick and easy configuration actions to start operating the system
landscape directory server in an AS Java system
For SAP NetWeaver PI 71 you have the following options concerning SLD
Option 1
Run SAP NetWeaver PI 71 against an existing SLD running on SAP NetWeaver 70 We only
recommend this for upgrades from SAP NetWeaver 70 if you have a central SLD in operation
not running on one of your PI systems
Option 2
Use the SLD included in an SAP NetWeaver PI 71 system We recommend this option for new
installations and upgrades from older releases than SAP NetWeaver 70 due to the enhanced
functions and improved performance of SLD 71
NOTE
If you already have a central SLD running on SAP NetWeaver 70 in operation you could run
two SLD versions in parallel ndash SLD running on SAP NetWeaver 71 for your PI systems and
SLD running on SAP NetWeaver 70 for all other systemsuse cases This way your SAP
5 System Landscape
52 Shared Services
4456 PUBLIC 2011-04-15
NetWeaver PI 71 systems would benefit from the new features while it would be easy to set
up and operate such an SLD landscape For this purpose you could use the new fully
automatic synchronization This feature enables the automatic forwarding of all SLD data
from an SLD running on SAP NetWeaver 70 to an SLD running on SAP NetWeaver 71 As a
result there is no need to adapt most existing systems as their SLD data suppliers could still
send their data to the central SLD In brief the following steps would be required
1 Put SLD in a PI system into operation (part of standard implementation procedure)
2 Configure PI systems to use the new SLD (part of standard implementation procedure
for new PI systems)
3 Set up the fully automatic synchronization from your old SLD to your new SLD
As soon as an upgrade or an installation of a standalone AS Java 71 system is available you
could move your central SLD also to SAP NetWeaver 71 Then you could optionally shift
your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems
Figure 8
We recommend that you use a Domain Name System (DNS) alias so that you are able to switch to
another System Landscape Directory easily For example if customers build a new landscape they
normally start with a sandbox environment Over time more and more environments are set up
Once the production environment is in place move the System Landscape Directory there To do
this you can configure a new System Landscape Directory in the production environment
synchronize it with the old System Landscape directory and switch to the new one
Topology
Apart from the considerations above the System Landscape Directory offers several topology options
with different grades of availability at the expense of low administration and operation effort There is
no generic rule therefore on how to set up a System Landscape Directory in your system landscape
To find the topology and synchronization strategy for the System Landscape Directory that fits your
requirements concerning the System Landscape Directory availability (and hence the availability of
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4556
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
456 PUBLIC 2011-04-15
Document History
CAUTION
Before you start the implementation make sure you have the latest version of this document
You can find the latest version on SAP Service Marketplace httpservicesapcom
instguides
The following table provides an overview on the most important document changes
Version Date Description
10 2007-12-07 First version
11 2008-02-05 Changes to System Landscape Directory section Minor changes
12 2008-04-22 Major revision of Shared Services section
13 2008-05-29 Information about dedicated PI system updated
14 2008-12-12 Restructuring of content according to use case concept Information about SAP enhancement package 1 for SAP NetWeaver PI 71 added
15 2009-03-19 Minor changes (mainly language corrections)
16 2009-03-20 Minor error corrections
17 2011-04-15 Section SAP Enhancement Package 1 for SAP NetWeaver PI 71 updated (Software Update Manager replaces SAP Enhancement Package Installer)
Section Process Sequence Installation of Enhancement Package 1 on an Existing SAP NetWeaver PI 71 system added
Section Maintaining System Landscape Information added Further minor changes
2011-04-15 PUBLIC 556
Table of Contents
Chapter 1 Introduction 9
Chapter 2 Before You Start 11
21 SAP Notes 11
22 More Information 11
23 Accessing the SAP Library 12
Chapter 3 SAP NetWeaver PI Overview 13
31 Installable Software Units 15
311 Systems with Usage Types 16
312 Standalone Engines 19
313 Clients 21
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration
71 23
Chapter 4 SOA-Based Integration Use Case 25
41 Overview 25
42 System Landscape 25
43 Implementation Sequence 27
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP
Netweaver PI 71 System 28
Chapter 5 System Landscape 33
51 Planning Your System Landscape 33
52 Shared Services 35
521 Use Cases 37
5211 End-to-End Solution Operations 37
5212 Support Infrastructure 38
5213 Collection of Landscape Data 39
5214 Authentication and Single Sign-On 39
5215 Integrated User and Access Management 39
522 Examples for the Overall System Landscape of Shared Services 40
656 PUBLIC 2011-04-15
523 Feature Details 42
5231 SAP Solution Manager 42
5232 Solution Manager Diagnostics 43
5233 System Landscape Directory 43
Chapter A Appendix 47
A1 Maintaining System Landscape Information 47
Chapter B Reference 51
B1 The Main SAP Documentation Types 51
B2 List of Documentation 51
2011-04-15 PUBLIC 756
This page is left blank for documents that are printed on both sides
1 Introduction
This Master Guide provides you with a central starting point for the technical implementation of SAP
NetWeaverreg Process Integration (SAP NetWeaver PI) It also contains information about enhancement
package 1 for SAP NetWeaver Process Integration 71
SAP NetWeaver PI 71 is based on an established architecture for realizing cross-system business processes
and supporting an service-oriented architecture (SOA) The focus is on the service-based integration
of applications
Structure of the Master Guide
The Master Guide consists of the following sections
Introduction
Contains an introduction to this guide
Before You Start
Contains information about this document important things which you need to know before you
start and information on how to access the SAP Library
SAP NetWeaver Overview
Describes the building blocks of SAP NetWeaver PI
SOA-Based Integration Use Case
Introduces the use case and explains how to install it
System Landscape
Contains information about how to install your system landscape
Reference
Contains information about the overall documentation concept for SAP systems
CAUTION
Make sure you have the latest version of the Master Guide by checking SAP Service Marketplace
immediately before starting the installation
The Master Guide is regularly updated on SAP Service Marketplace at http
servicesapcominstallnwpi71 Planning
Constraints
The business scenarios that are presented here serve as examples of how you can use SAP software in
your company The business scenarios are intended only as models and do not necessarily run the way
they are described here in your customer-specific system landscape Check your requirements and
systems to determine whether these scenarios can be used productively at your site Furthermore we
1 Introduction
2011-04-15 PUBLIC 956
recommend that you test these scenarios thoroughly in your test systems to ensure that they are
complete and free of errors before going live
1 Introduction
1056 PUBLIC 2011-04-15
2 Before You Start
21 SAP Notes
You must read the following SAP Notes before you use this Master Guide and implement SAP NetWeaver
Make sure that you have the up-to-date version of each SAP Note which you can find on SAP Service
Marketplace at httpservicesapcomnotes
NOTE
The SAP Notes related to SAP NetWeaver PI 71 are also listed on SAP Service Marketplace at
httpservicesapcomsapnotesnwpi71
List of Important SAP Notes
SAP Note Number Title Description
1004107 Release Restrictions for SAP NetWeaver PI 71
Some restrictions apply to the productive use of SAP NetWeaver PI 71 These are documented in this SAP Note
1247043 Release Restrictions for SAP EHP1 for SAP NetWeaver PI 71
Some restrictions apply to the productive use of enhancement package 1 for SAP NetWeaver PI 71 These are documented in this SAP Note
22 More Information
The following table contains links to information available on SAP Service Marketplace or in the SAP
Library which is important for implementing SAP NetWeaver
Content Location on SAP Service Marketplace or in SAP Library
The latest version of the installation and upgrade guides for SAP NetWeaver Process Integration
httpservicesapcominstguidesnwpi71
Information about supported platforms (operating systems databases browsers) for all SAP NetWeaver components
httpservicesapcomplatforms Product Availability Matrix
Sizing of SAP NetWeaver httpservicesapcomsizing
Information about security SAP Security Guide See the SAP Library [page 12] at Adminitstratoracutes Guide Security Guide
Information about the technical operation of SAP NetWeaver
Technical Operations Manual See the SAP Library [page 12] at Adminitstratoracutes Guide Technical Operations for SAP NetWeaver
2 Before You Start
21 SAP Notes
2011-04-15 PUBLIC 1156
Content Location on SAP Service Marketplace or in SAP Library
Information about SAP NetWeaver PI Support Package Stacks
httpservicesapcomnetweaver SAP NetWeaver PI 71- Release-Specific Information Support Package Stacks Information
Information about installing SAP NetWeaver Support Package Stacks
httpservicesapcomMaintenanceNWPI71
Support Package Stack Guide ndash SAP NetWeaver
23 Accessing the SAP Library
For more information about SAP NetWeaver Process Integration access the SAP Library from any of
the following
SAP Help Portal at httphelpsapcomNWPI71 SAP NetWeaver Process Integration 71 Library
ltLanguagegt SAP NetWeaver Process Integration Library
CAUTION
The SAP Help Portal contains the latest version of the SAP Library Therefore we recommend
that you use this channel to access the SAP Library
An SAP system if you have installed the online documentation Choose Help SAP Library
The browser starts
The help files on the online documentation CDs or DVDs
If you want to view the help files in HTMLHelp format from the online documentation CDs or
DVDs you need a PC running Microsoft Windows to install the HTMLHelp Viewer
2 Before You Start
23 Accessing the SAP Library
1256 PUBLIC 2011-04-15
3 SAP NetWeaver PI Overview
Introduction
SAP NetWeaver PI 71 is part of the SAP NetWeaver technology platform The complete offering of the
SAP NetWeaver technology platform is visualized in the SAP NetWeaver technology map which you
can access at httpsdnsapcomnetweaver SAP NetWeaver at a Glance The technology map
enables you to drill down from top-level technology areas (for example Lifecycle Management) to
individual capabilities (for example Administration Monitoring and so on)
SAP NetWeaver PI includes the following capabilities
Repository-based Modeling and Design
Service Bus-based Integration
SOA Management
A different view is introduced by the end-to-end use case concept This concept offers an
implementation view on SAP NetWeaver to structure and facilitate your implementation
A use cases is a process that typically involves several SAP NetWeaver capabilities It is not limited to a
single component or capability A use case guides you through the different phases of your
implementation project ndash from information through installation to the configuration phase This
implies that a uses case addresses several user roles administrator power user and end user
This document describes the SOA-based integration use case
Architecture Principals
The architecture of SAP NetWeaver Process Integration 71 (SAP NetWeaver PI 71) is based on an
established architecture for realizing cross-system business processes and is a further development of
lower releases (SAP NetWeaver 70 usage type Process Integration and SAP XI 30 as part of SAP
NetWeaver 2004) SAP NetWeaver PI 71 plays an important role in supporting an service-oriented
architecture (SOA) The focus is on the service-based integration of applications
SAP NetWeaver PI is based on general standards so as to enable 3rd-party systems to be integrated At
the center of SAP NetWeaver PI is an XML-based communication that uses HTTP (Hyper Text Transfer
Protocol) Irrespective of the scenario used the application-specific contents are transferred in messages
in user-defined XML (eXtensible Markup Language) from the sender to the receiver either via the
Integration Server or directly between the systems involved
The following figure gives an overview of the key capabilities of SAP NetWeaver Process Integration
3 SAP NetWeaver PI Overview
2011-04-15 PUBLIC 1356
Figure 1 SAP NetWeaver PI Key Capabilities Overview
SAP NetWeaver Process Integration 71 enables the integration of the applications of the following
communication parties
B2B Party Any business partners that want to integrate their application with other applications
outside their own system landscape Scenarios that require industry standards are supported as
well as any scenarios that do not adhere to a particular industry standard
SAP Applications that run on SAP systems This includes the processing of events by using the
Business Activity Monitoring (BAM) infrastructure
3rd-Party Application Applications from 3rd-party providers within one system landscape for
example database or file-system-based
3rd-Party Middleware Middleware systems from 3rd-party providers that are required for the
integration of applications within a company and across company boundaries
SAP NetWeaver PI also supports internal company scenarios and cross-company scenarios It enables
you to connect systems from different vendors (non-SAP and SAP) in different versions and
implemented in different programming languages (Java ABAP and so on) to each other Like the rest
of the SAP NetWeaver platform SAP NetWeaver PI is based on an open architecture uses open standards
(in particular those from the XML and Java environments) and offers those services that are essential
in a heterogeneous and complex system landscape
To enable end-to-end SOA development SAP NetWeaver Process Integration 71 offers a Universal
Description Discovery and Integration (UDDI) v3-based Services Registry where providers can publish
service endpoints definitions and associated metadata and consumers can discover the appropriate
services for their scenarios The Services Registry provides capabilities for classifying and browsing
3 SAP NetWeaver PI Overview
1456 PUBLIC 2011-04-15
services using semantic-rich classification systems The Services Registry is part of Application Server
Java (AS Java)
31 Installable Software Units
SAP NetWeaver comprises the following three types of installable software units
Systems that are configured for a specific purpose as indicated by one or more usage types
Standalone engines that provide one specific (server) function in combination with one or more
SAP NetWeaver PI systems
Clients used by (many) people from their local front-end PC to access functions offered by systems
of SAP NetWeaver PI or standalone engines in the system landscape
In the following sections you can find more details about the software units The figure below provides
and overview of the software units
Figure 2 Installable Software Units for SAP NetWeaver PI
For this and other figures in this guide the following legend applies
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1556
Figure 3 Legend
311 Systems with Usage Types
SAP systems are the main building blocks of SAP NetWeaver They are identified by unique SAP system
IDs (SAPSIDs) and configured for a certain purpose as indicated by usage types Usage types have the
following characteristics
They are a structuring element for SAP software on a technical level
Usage Types determine the intended purpose of a system and the role it plays in a given (distributed)
use case
They are realized by installing and configuring a collection of software components
They allow a logical view of the technology platform SAP NetWeaver PI
A usage type may require other usage types in the same system to operate
They can also be run in the same system together with other usage types that are not a prerequisite
How SAP NetWeaver Systems are Used
The following sections describe the usage types and their dependencies for SAP NetWeaver PI
Application Server ABAP (AS ABAP)
Purpose
AS ABAP is used to provide the ABAP foundation of SAP NetWeaver PI
Application Server ABAP provides a complete development and runtime environment for ABAP-based
applications It is optimized for the development of highly scalable business applications The ABAP
development and runtime environment makes it possible to develop complex business applications
3 SAP NetWeaver PI Overview
31 Installable Software Units
1656 PUBLIC 2011-04-15
without having to worry explicitly about technical details such as process or memory administration
multi-user capability database connections or similar issues These are provided in the basis services or
are integrated directly in the ABAP runtime The application development is similarly independent of
the underlying platform The application server decouples the application coding completely from the
operating system and database that are used
Dependencies
AS ABAP can be combined optionally with other usage types in one system
Application Server Java (AS Java)
Purpose
AS Java is used to provide the Java foundation of SAP NetWeaver PI using the Java Engine a Java EE-
compliant application server for running enterprise applications In addition to the pure Java EE
standard technologies the Java Engine implements complementary technologies such as Web Dynpro
or Web Services that are targeted at supporting large-scale real-business application development
projects
Dependencies
AS Java can be combined optionally with other usage types in one system
Process Integration (PI)
Purpose
PI consists of core components that model design automate and integrate processes in one or more
application systems For the integration of internal and cross-company processes PI is used to
incorporate all the functions of what was formerly known as Exchange Infrastructure (XI) In addition
PI contains core components for Business Process Management for application-embedded and
application-unbounded processes
The Advanced Adapter Engine is also part of usage type PI You use Advanced Adapter Engine to connect
to SAP systems (RFC adapter) and external systems You use the various adapters in Advanced Adapter
Engine to convert XML- and HTTP-based messages to the specific protocol and format required by
these systems and the other way around You can use the Advanced Adapter Engine that is part of
your PI system as a central Advanced Adapter Engine Optionally (for performance reasons) you can
install a non-central Advanced Adapter Engine [page 19] separately as a system with AS Java and parts of the
usage type PI on a separate host
Dependencies
PI requires AS ABAP and AS Java as prerequisites in the same system
For installing PI it is mandatory to have a dedicated PI system This applies to development quality
and production landscapes It is a prerequisite that no other system in your system landscape has a
higher release and enhancement package level than the PI system If you want to upgrade or install an
application in your system landscape you first have to make sure that the current release and
enhancement package level of the PI system is on the same level - if required you have to upgrade the
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1756
PI system first to the new or a higher release In a dedicated PI system this can be accomplished with a
minimum of downtime Also the PI system would not be affected by the downtime of other usage
types running in the same system
Configuration of Systems with Usage Types
Configuration information is available in the installation guides the configuration wizard and SAP
Solution Manager
In the Installation Guide ndash SAP NetWeaver PI 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt you find
initial technical configuration tasks This guide also informs you about how you can run the
configuration wizard and how you can access the configuration information in SAP Solution
Manager
For certain usage types configuration tasks can be applied by the configuration wizard after the
installation To do this you start the configuration wizard from SAP NetWeaver Administrator
The configuration steps for systems with usage types required for an use case are accessible through
SAP Solution Manager
To be able to use SAP Solution Manager for the configuration tasks you have to import the latest
SAP Solution Manager Implementation Content (Add-On ST-ICO) that is available for your SAP
Solution Manager release For more information see SAP Note 631042 (Release strategy for Implementation
Content (ST-ICO))
SAP Solution Manager Implementation Content is available on SAP Service Marketplace at
httpservicesapcomswdc Installations amp Upgrades Entry by Application Component SAP
Technology Components SAP Solution Manager ltReleasegt Content ST-ICO
In SAP Solution Manager you create a project and a project structure In the configuration phase
you select configuration structures with pre-delivered SAP content for your project You can find
the following different types of configuration tasks in SAP Solution Manager
Mandatory configuration tasks All configuration tasks that are mandatory for the standalone
engine or usage type
Optional configuration tasks Configuration tasks for areas where customers need to decide
if they want to use these functions (for example high availability or security settings)
Additional functions ndash configuration tasks Configuration tasks for functional units that are
used in certain use cases only
A marked checkbox in front of the configuration tasks indicates those configuration tasks that are
relevant for the use case you have chosen To configure ABAP systems SAP Solution Manager
offers executable configuration files (IMG activities)
For information about using SAP Solution Manager Content and creating a configuration guide
see the following documentation
httphelpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Implementing
and Upgrading SAP Solutions Configuration
3 SAP NetWeaver PI Overview
31 Installable Software Units
1856 PUBLIC 2011-04-15
How to Create a Configuration Guide using SAP Solution Manager available at http
servicesapcomsolutionmanager Media Library How-To Documents
Restrictions for Systems with Multiple Usage Types
If you have one system with multiple usage types be aware that we do not provide standard tools
to separate these usage types and distribute them to multiple systems at a later stage For example
if you have a system with usage types A and B you are not able to migrate it with SAP standard
tools into two systems one with usage type A only and the other with usage type B only
In addition we do not provide standard tools to merge multiple systems with different usage types
into one system with multiple usage types at a later stage
If you want to perform these tasks you require specific project support
The following figure shows that SAP standard system copy and migration tools do not support
you in separating or merging systems with usage types
Figure 4 No Support for Merging or Separating Systems with Usage Types
Although you can use one system for multiple usage types client restrictions apply for usage type
PI PI requires a dedicated client due to special PI requirements concerning the client pipeline
Whereas application client pipelines only send and receive messages the central PI pipeline can
also map messages to different formats before sending them
312 Standalone Engines
Standalone engines of SAP NetWeaver are additional installable software units They do not work as
full-blown systems of SAP NetWeaver but as standalone engines that provide a specific (server) function
in combination with one or more SAP NetWeaver systems
Standalone engines are not part of a usage type They do not run on AS ABAP or AS Java
The standalone engines that are available for SAP NetWeaver Process Integration are described in the
following
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1956
Gateway
It is possible to install an SAP instance of an SAP NetWeaver system based exclusively on a standalone
gateway This type of instance does not contain normal work process types (dialog background update
enqueue or spool) Only the gateway process (gwrd) is started If there is an SNA connection to an R
2 system gateway work processes (gwwp) are also started
SAP Conversion Agent by Informatica
SAP Conversion Agent by Informatica is a data conversion tool that enables you to create interfaces
between any data formats and XML-based systems SAP Conversion Agent can convert unstructured
semi-structured and structured formats to XML and the other way around The Conversion Agent
comprises the Conversion Agent Studio and the Conversion Agent Engine In the Conversion Agent
Studio you can develop and configure data conversions The Conversion Agent Engine executes the
data conversions
Search and Classification (TREX)
You can use Search and Classification with SAP NetWeaver PI to search for messages that were previously
indexed Message search using index provides additional methods of searching for specific messages In
addition to static header attributes you can also use adapter-specific message attributes and data from
the message payload for the search A requirement of this however is that the messages are indexed
first You can apply the index-based message search to one or all indexed components of an integration
landscape (domain) Integration Server Adapter Engines and ABAP business systems
For more information see the SAP Library [page 12] at Administratorrsquos Guide Technical Operations for SAP
NetWeaver Administration of SAP NetWeaver Systems Administering PI (Process Integration) Monitoring Index
Administration
Web Dispatcher
The Web Dispatcher lies between the Internet and your SAP system It is the entry point for HTTP(s)
requests into your system which consists of one or more SAP NetWeaver application servers As a
software web switch the Web dispatcher can reject connections or accept them When it accepts a
connection it balances the load to ensure an even distribution across the servers
You can use the Web dispatcher in ABAPJava systems and in pure Java systems as well as in pure ABAP
systems
It is also beneficial to use the Web Dispatcher if you do not need security functions (entry point in the
demilitarized zone (DMZ) SSL URL filtering) but you simply want to balance the load between
multiple SAP NetWeaver Application Server instances
Since Web Dispatcher is optional for every SAP system it is not contained in the system landscape and
the implementation sequence of the use case in this documentation
For more information see the SAP Library [page 12] at Function Oriented View Application Server Infrastructure
SAP Web Dispatcher
3 SAP NetWeaver PI Overview
31 Installable Software Units
2056 PUBLIC 2011-04-15
Advanced Adapter Engine
You use the Advanced Adapter Engine to connect to SAP systems (RFC adapter) and external systems
You use the various adapters in Advanced Adapter Engine to convert XML- and HTTP-based messages
to the specific protocol and format required by these systems and the other way around For specific
senderreceiver combinations messages can be processed without invoking the central Integration
Engine In principle you connect external systems using the adapters that are installed centrally or
non-centrally in Advanced Adapter Engine You can use the Advanced Adapter Engine that is part of
your PI system as a central Advanced Adapter Engine Optionally (for performance reasons) you can
install a non-central Advanced Adapter Engine separately as a system with AS Java and parts of the
usage type PI on a separate host
Adapter Engine (Java SE)
Adapter Engine (Java SE) is a separate software unit You can use it only if you have SAP NetWeaver
systems with usage type PI in your system landscape It has to be installed manually You use the Adapter
Engine (Java SE) to connect to external systems Using the various adapters in the Adapter Engine (Java
SE) XML and HTTP-based messages can be converted to the specific protocol and format required by
such systems and the other way around The Adapter Engine (Java SE) only provides some of these
adapters as a standalone version with restricted functions for operating systems that do not support
SAP NetWeaver PI 71 but that have at least a Java Runtime Environment 50 Therefore you should
use the Adapter Engine (Java SE) only if the platform prerequisites do not allow you to use the Advanced
Adapter Engine
SAP Partner Connectivity Kit
SAP Partner Connectivity Kit (PCK) runs on AS Java with parts of the usage type PI It enables a system
of a smaller company or subsidiary that does not run SAP NetWeaver PI to connect to your SAP
NetWeaver systems
313 Clients
Clients are additional installable programs or tools They reside either on local front-end PCs accessed
by users or on back-end systems where they act as client programs within an SAP NetWeaver system
landscape
The clients that you can use with SAP NetWeaver Process Integration are described in the following
sections
SAP GUI
NOTE
We recommend that you use the following versionsI
SAP GUI for Windows 710 (or higher) with the latest patch level
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 2156
SAP GUI for Java 710 (or higher) with the latest revision
The integrated SAP ITS 710
For more information about the SAP GUI family see SAP Service Marketplace at http
servicesapcomsapgui
SAP offers three different client applications for accessing ABAP applications in SAP systems (such as
SAP NetWeaver systems with usage type AS ABAP) This SAP GUI family consists of
SAP GUI for HTML
SAP GUI for HTML is based on the SAP integrated Internet Transaction Server (ITS) which is
included in the installation of SAP NetWeaver systems as of SAP NetWeaver 2004 On the client
side only a suitable browser (such as Internet Explorer 70 or Firefox 20) and a virtual machine are
required SAP ITS 620 is not compatible with SAP NetWeaver 71
SAP GUI for the Java environment (SAP GUI for Java)
SAP GUI for Java is a generic SAP GUI that covers a variety of platforms
For more information about the installation of SAP GUI for Java see the documentation Installation
Guide ndash SAP Front End
SAP GUI for the Windows environment (SAP GUI for Windows)
SAP GUI for Windows is SAPs universal client for accessing all SAP applications built on ABAP
technology It is available on the Microsoft Windows platform only and offers the broadest feature
set of all members of the SAP GUI family
For more information about the installation of SAP GUI for Windows see the Installation Guide ndash
SAP Front End
SAP NetWeaver Developer Studio
The SAP NetWeaver Developer Studio is SAPrsquos Integrated Development Environment (IDE) for Java
and is based on the open-source tools framework Eclipse 33 With the SAP NetWeaver Developer Studio
you can develop Java EE 5 applications from scratch using the built-in support for new technologies
such as EJB 30 and JSF 12
During the installation of the SAP NetWeaver Developer Studio several features are offered for
installation For SAP NetWeaver PI 71 only the following features are relevant
SAP NetWeaver Developer Studio Platform
SAP NetWeaver Developer Studio Java EE
NOTE
If you want to use one of the other features you need SAP NetWeaver Composition Environment
and a corresponding developers licence
For more information about the installation of SAP NetWeaver Developer Studio see the Installation
Guide ndash SAP NetWeaver Developer Studio 71 or Installation Guide ndash SAP NetWeaver Developer Studio 71 Including
Enhancement Package 1
3 SAP NetWeaver PI Overview
31 Installable Software Units
2256 PUBLIC 2011-04-15
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
SAP enhancement packages are a new way of delivering new functions for SAP NetWeaver This allows
a clear separation between the delivery of new functions on the one hand and corrections legal changes
and security updates on the other hand (in Support Package stacks) SAP enhancement packages are
cumulative an enhancement package always contains the functions of the corresponding predecessor
enhancement packages
Enhancement packages are maintained by their own Support Packages while the main release is in
maintenance
Benefits
SAP enhancement packages offer the following benefits
You have reduced effort for testing and no effort for training when applying Support Packages as
new features are only shipped with enhancement packages
Adding new functions between releases becomes predictable and controllable
New functions can be added successively in small steps There is no need to fully upgrade your
system to get new functions
You have minimal training effort when applying an enhancement package because existing
functions are not replaced
Implementation
There are the following ways to get an SAP NetWeaver system with the release level of SAP enhancement
package 1 for SAP NetWeaver Process Integration 71
New installation of SAP NetWeaver PI 71 including enhancement package 1 using the standard
installation tool SAPinst
Upgrade of an existing SAP NetWeaver system from a release lower than SAP NetWeaver PI 71 to
SAP NetWeaver PI 71 including enhancement package 1 For this you use the upgrade programs
SAPup (for ABAP) and SAPJup (for Java)
Installation of the enhancement package on an existing SAP NetWeaver PI 71 system
For this you use the Software Update Manager (SUM) The Software Update Manager evolved
from the previously used SAP Enhancement Package Installer The tool has been renamed to reflect
its broader use for example you can also use it for applying Support Package Stacks to your system
On the ABAP side the Software Update Manager uses a system cloning and switch procedure for
installing enhancement packages It installs a copy of the system the shadow system parallel to
the original system This shadow system is used to update the relevant software components and
to install the additional components while the original system is still in production operation At
a certain point during downtime the switch to the new system is made and afterwards any parts
of the original system that are no longer needed are deleted The enhancement package installation
in a Java system uses a deploy-based procedure that is no shadow system is used The Software
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2011-04-15 PUBLIC 2356
Update Manager requires a stack configuration file (xml file) as input file for the enhancement
package installation procedure This file lists all the packages that are to be installed in your systems
The stack configuration file is generated when you download the required packages
As the Software Update Manager is updated regularly we recommend to always use the latest
version It is delivered as part of the SL toolset For more information see http
servicesapcomsltoolset
For an overview of all required steps for the enhancement package installation process and
corresponding documents see Process Overview Installation of Enhancement Package 1 on an Existing SAP
Netweaver PI 71 System [page 28]
Content of SAP Enhancement Package 1 for SAP NetWeaver PI 71
With enhancement package 1 for SAP NetWeaver PI 71 new features are introduced and some existing
are changed The following is a selection of some of the most important enhancements
Enhanced design and modelling options in the Enterprise Services Repository
New services registry
Support for new Web services standard (Web Services Reliable Messaging)
New modules for the Advanced Adapter Engine
Use of shared memory of the ABAP Application Server for message processing
For more information about the changes see SAP Library [page 12] at Whatacutes new in SAP NetWeaver PI 71
ndash Release Notes
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2456 PUBLIC 2011-04-15
4 SOA-Based Integration Use Case
41 Overview
You can use SOA-based integration to set up the communication between service providers and service
consumers in both application-to-application and business-to-business scenarios and to execute
operate and monitor the communication at runtime SOA-based integration covers both direct (point-
to-point) as well as mediated (via an Integration Server) communication between service providers and
service consumers
The use case spans the whole life cycle of a SOA-based integration scenario including
Scenario modeling and service design in the Enterprise Services Repository
Implementation of the service provider and consumer in the back-end systems
Configuration and finally execution monitoring and operation of the integration scenario
For scenarios using Integration Server or broker-based communication the configuration of the
different connectivity options (for example SOAP RFC Web Services Industry standards and JDBC)
and their enhancements is covered
For more information see the following documents
Service-Enabling with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdnsoa-modeling
Getting Started
Service-Enabling a Legacy Application with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdn
soa-servicebus Getting Started
In the following you will find information about the installation of the involved software units
42 System Landscape
The following figure shows the system landscape for this use case
4 SOA-Based Integration Use Case
41 Overview
2011-04-15 PUBLIC 2556
Figure 5 SOA-Based Integration
It is mandatory to have a dedicated PI system This applies to development quality and production
landscapes
For PI it is a prerequisite that no other system in your system landscape has a higher release than
the PI system For exceptions to this rule see SAP Note 1043047 For example SAP XI 30 is compatible
with SAP NetWeaver 640 and 70 application systems since the same XI protocol is used Apart
from these exceptions if you want to upgrade or install an application in your system landscape
you first have to make sure that the PI system is on the same release level If required you have to
upgrade the PI system first to the new or a higher release
CAUTION
Although it should be technically possible to run an application system with a higher release
than your PI system in your system landscape this is not supported by SAP (apart from the
exceptions listed in SAP Note 1043047) Therefore you run such a landscape at your own risk
You can use the Advanced Adapter Engine that is part of your PI system as a central Advanced
Adapter Engine
Adapter Engine (Java SE) can be installed in a non-SAP Java environment However it only hosts
a subset of the adapter functionality is only supported for compatibility reasons and should be
used only if this is a precondition in your environment
Optionally you can use the Change Management Service (CMS) of an SAP NetWeaver 70 system
with usage type DI to transport design objects and repository objects For more information see
the SAP Library [page 12] at Administratoracutes Guide Technical Operations for SAP NetWeaver Administration
of SAP NetWeaver Systems PI (Process Integration) Software Logistics Transporting ESR Content and Objects
of Integration Directory PI Transports Using the Change Management Service (CMS)
Smaller business partners or subsidiaries that do not run SAP NetWeaver install SAP Partner
Connectivity Kit in their system landscape SAP Partner Connectivity Kit enables XML document
4 SOA-Based Integration Use Case
42 System Landscape
2656 PUBLIC 2011-04-15
exchange between your SAP NetWeaver systems and the partner systems Since SAP Partner
Connectivity Kit gets installed in their system landscape it is not shown in the system landscape
figure above
The AS ABAP system acts as an application and service provider For Java Web Services you also
require AS Java In addition you require SAP NetWeaver Developer Studio on the client side as a
development environment
The Web service client can be either an SAP or a non-SAP application For example an AS ABAP
system or a Web browser could act as application or service consumer
You can install SAP Conversion Agent by Informatica in the system with usage type PI or on a host
where SAP Partner Connectivity Kit is installed or on a host where neither usage type PI nor SAP
Partner Connectivity Kit is installed
43 Implementation Sequence
Procedure
To install this use case perform the steps listed in the following table
StepAction[Corresponding Documentation] Remarks
1 Make sure that you have performed the preparation steps You have planned your system landscape [page 33]
(that is you have decided how many systems you require how you want to use each of these systems and which standalone engines and clients you require)
With the help of your hardware partner you have mapped your systems and standalone engines to properly sized hosts
You have planned and installed shared services [page 35]
2 Installation of system with usage type PI (includes the installation of AS ABAP and AS Java)
NOTE
For usage type PI a Unicode installation is mandatory
[Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt]
If you want to use the features of enhancement package 1 use the direct installation of SAP NetWeaver PI 71 including enhancement package 1
Make sure that you perform the configuration steps as described in the installation guide For certain usage types configuration tasks can be applied by the configuration wizard These configuration tasks as well as any additional configuration steps for your use case are listed in SAP Solution Manager For more information
4 SOA-Based Integration Use Case
43 Implementation Sequence
2011-04-15 PUBLIC 2756
StepAction[Corresponding Documentation] Remarks
see the Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt
3 Install the Adapter Engine (Java SE) engines if required[Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
4 To integrate small business partners and subsidiaries the business partners or subsidiaries install SAP Partner Connectivity Kit running on AS Java with parts of usage type PI in the business partners or subsidiarys system landscape[Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
5 Install SAP Conversion Agent by Informatica if required[SAP Library [page 12] at Function-Oriented View Process Integration SAP Conversion Agent by Informatica Deploying and Using Conversion Agent ]
6 Installation of clients SAP GUI
[Installation Guide ndash SAP Front End]
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
The process sequences give a comprehensive overview of the steps relevant for the enhancement
package installation on an existing SAP NetWeaver PI 71 system
The process sequence is divided into a planning phase and an implementation phase Each step in both
phases contains references to the corresponding documentation to ensure that you can easily find the
information you need
Process
NOTE
To download the enhancement package files and required Support Packages you require the SAP
Solution Manager Maintenance Optimizer You have the following options
Manual Selection
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2856 PUBLIC 2011-04-15
You manually select the required files from SAP Service Marketplace at http
servicesapcomswdc using the SP Stack Application You use the Maintenance Optimize
only to approve the packages which is a prerequisite for the download
Automatic Calculation
The Maintenance Optimizer supports the download of a consistent queue that includes all
necessary Support Packages and enhancement packages In addition SAP Solution Manager
calculates a valid import queue for the selected SAP system and generates the enhancement
package stack configuration file that you require for the installation
As a prerequisite the system that you want to update needs to be maintained correctly in
SAP Solution Manager System Landscape As the Maintenance Optimizer uses this data for
the calculation it is crucial that the data is up-to-date In addition the SAP Solution Manager
system requires a Minimum Support Package level (see below)
Planing PhaseStep Description Documentation
Hardware amp Software Prerequisites
Check which platforms are supported for your target release (OSDB dependencies)
Product Availability Matrix (PAM) at httpservicesapcompam
Check which hardware sizing is required for your target release
Sizing information at httpservicesapcomsizing
Solution Manager Prerequisites
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of the required software packages you have to make sure that your SAP Solution Manager system has the required Support Package levelAt least SAP Solution Manager 70 EHP1 Support Package Stack 17 is required We recommend to use SAP Solution Manager 70 EHP1 Support Package Stack 23Check if you need to do an update or upgrade of your SAP Solution ManagerMake sure that you run the guided procedure SOLMAN_SETUP after every installation or update of SAP Solution Manager and that it completes successfully
For upgrades from source release SAP Solution Manager 31 and 32Upgrade Guide ndash SAP Solution Manager 70 incl Enhancement Package 1For updates from SAP Solution Manager 70Update Guide SAP Enhancement Package 1 for SAP Solution Manager 70Follow-up activities after an Support Package Stack update or enhancement package updateSolution Operations Guide ndash SAP Solution Manager 70 EHP1 section Software Change Management All guides are available at http
servicesapcom instguides SAP Components SAP Solution Manager -gt Release 70 EHP 1
Implementation PhaseStep Description Documentation
1Solution Manager Preparation
Configure the SAP Solution Manager Maintenance Optimizer
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of software packages make sure your
Configuration of Maintenance Optimizer http
helpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Change Request Management and Change ControlMaintenance Optimizer
Prerequisites
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 2956
Implementation PhaseStep Description Documentation
system landscape data in SAP Solution Manager is maintained correctlyLandscape Verification 10 which is an add-on to SAP Solution Manager can support you in maintaining your system landscape data The use of this tool is optional
Landscape Verification http
wwwsdnsapcom irj
sdn alm-update-
management link Landscape Verification under Related Areas on Upgrade and Update Management (in the right column)
SAP Note 1468605 (Installation of Landscape Verification)
Maintaining System Landscape Information [page 47]Note that the information provided in this section is based on SAP Solution Manager 70 EHP1 SP23
2System Preparation
Prepare your system as described in the documentation for example perform OS DB specific preparations and the PI-specific preparations
Update Guide ndash Update of SAP Systems with Software Update Manager sections Planning and Preparation
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
3Software Download
Select and download the software packages in either of the following ways Automatic calculation Create
a maintenance transaction in the Maintenance Optimizer and choose the Calculate Files Automatically option
Manual Selection Create a maintenance transaction in the Maintenance Optimizer and choose the Select Files Manually option You then can select the files manually using the SP Stack application in SAP Service Marketplace
NOTE
You have to download the stack configuration file manually after you have selected all files in the SP Stack
httphelpsapcom SAP Solutions SAP Solution Manager
SAP Solution Manager 70 EHP1 ltSPgtChange Request Management and
Change Control Maintenance Optimizer Maintenance Procedure Scenarios
For information about the automatic calculation see Maintenance Transaction with Installation of an Enhancement PackageFor information about the manual selection and approval process see section Approve and Download Files in Download Basket
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
3056 PUBLIC 2011-04-15
Implementation PhaseStep Description Documentation
application Choose Generate Stack XML and save the file
4Enhancement Package Installation
Run Software Update Manager to update your system with the selected software packages
Update Guide ndash Update of SAP Systems with Software Update Manager
5Follow-Up Steps
Perform technical and PI-specific follow-up activities after the enhancement package installation is done
Update Guide ndash Update of SAP Systems with Software Update Manager section Follow-Up Activities
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
6Configuration
Configure newly installed enhancement package functions using SAP Solution Manager content
See Systems with Usage Types [page 16] section Configuration of Systems with Usage Types
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 3156
This page is left blank for documents that are printed on both sides
5 System Landscape
51 Planning Your System Landscape
The installable software units that make up your system landscape depend on the functions that you
want to implement For information about the features see systems [page 16] standalone engines [page 19]
and clients [page 21]
In addition you have to determine the required shared services [page 35] (such as SAP Solution Manager
or SAP NetWeaver Administrator) that run on central systems in your system landscape and the
landscape aspects relevant for their implementation
In the following you will find general information that you should consider when planning your system
landscape
Sizing
You have to map systems and standalone engines to hosts after you have a clear picture of the following
Which systems and standalone engines you require
How many systems you require and how you want to use each of these systems
NOTE
No general guideline can be given for the sizing of your landscape since this relies heavily on your
requirements You should therefore perform this task together with your hardware partner and
your technical consultant
For information about sizing your systems you can use the following information sources
Your first point of reference is the Quick Sizer
SAP built the Quick Sizer as an online sizing questionnaire Internet application in close cooperation
with its hardware partners This tool delivers general sizing categories based on your volume load
estimates The results provide an objective basis for sizing independent of platform and
configuration
For more information see SAP Service Marketplace at
httpservicesapcomsizing for the SAP NetWeaver PI 71 sizing guide available under
Sizing Guidelines Business Suite amp Services
httpservicesapcomquicksizer for more information and access to the tool itself
Also consider the following important aspects concerning sizing
High availability
5 System Landscape
51 Planning Your System Landscape
2011-04-15 PUBLIC 3356
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Technical Infrastructure High Availability
Unicode
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Internationalization
Contact your hardware partner to find out the appropriate number of sized hosts
The platform-independent abstract results of the Quick Sizer can be used by any of our hardware
partners to create a concrete offer SAP itself does not make any hardware recommendations the
responsibility for sizing and detailed hardware configuration lies with the hardware partners
Figure 6 Example of Mapping of Systems and Standalone Engines to Three Hosts
NOTE
Optionally you could also distribute single systems to multiple hosts For example you could
decide to install the database instance of an SAP system on a separate host for performance
reasons or distribute other system instances to achieve high availability
To provide a mapping that fits your required functions and performance your hardware partner
and your technical consultant have to identify the number of required instances of SAP NetWeaver
find out how to distribute these instances to hosts and what functions will run on which instance
Therefore the hardware partner and the technical consultant have to consider many different
aspects such as
Number of required SAPS (SAP Application Benchmark Performance Standard) for each
system (provided by Quick Sizer)
Landscape-relevant aspects concerning security For more information see the SAP Security
Guide in the SAP Library [page 12] at Administratoracutes Guide Security Guide
Landscape-relevant aspects concerning scalability high availability operation and software
life-cycle management
5 System Landscape
51 Planning Your System Landscape
3456 PUBLIC 2011-04-15
For more information about relevant aspects for the mapping of systems to hosts see the document
Technical Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
Scaling and Distribution Options
You may need to design your system landscape for a large number of users SAP NetWeaver PI offers
you different means of scalability The following list provides you with some examples
You could install multiple systems of one type and use them for different purposes
You could scale every system by installing dialog instances or by distributing the database instance
For more information about distribution options on the instance level see the Technical
Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
For every SAP system you could additionally install Web Dispatcher For more information see
the SAP Library [page 12] at FunctionndashOriented View Application Server Infrastructure SAP Web
Dispatcher
You could further distribute certain standalone engines ndash for example Search and Classification
(TREX) is based on a flexible architecture that supports a distributed installation For more
information see the Technical Infrastructure Guide ndash SAP NetWeaver PI 71 available in SAP Service
Marketplace at httpservicesapcominstallNWPI71
52 Shared Services
You normally run shared services on central systems in your system landscape The following features
could be used for SAP NetWeaver Process Integration to realize shared services
SAP Solution Manager
Used to implement train test maintain monitor control change and manage incidents of your
SAP solution system landscape (open end-to-end application management)
As of SAP Solution Manager (70) 40 Support Package 15 SAP Solution Manager has become the
platform for SAPs end-to-end solution operations strategy Functions for complete application
management has been combined with administrative tools and has been merged in newly created
role based work centers
NOTE
Be aware that you require an SAP Solution Manager system to install or upgrade to SAP
NetWeaver 70 and higher An SAP Solution Manager system is required to generate the SAP
Solution Manager key needed during the installation or upgrade process Without this key
the installation or upgrade process cannot continue
For SAP NetWeaver Process Integration you require SAP Solution Manager 70
For more information see SAP Note 805390
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3556
Solution Manager Diagnostics
An integral part of SAP Solution Manager that is running as a Java application on the Java stack of
SAP Solution Manager 70 Solution Manager Diagnostics is used to analyze the root cause of
incidents in your landscape in an efficient and safe way Before Go-Live Solution Manager
Diagnostics has to be set up and made accessible remotely
SAP NetWeaver Administrator
SAP NetWeaver Administrator is the central administration component which is used for
monitoring and administering Java applications It is included in SAP NetWeaver systems with AS
Java
SAP NetWeaver Administrator exists in the following flavors
A local mode which runs out of the box and which focuses on administrating the underlying
SAP NetWeaver AS Java
NOTE
For a SAP NetWeaver PI 71 it has a special role which you need to activate using a
configuation wizard
A central mode which has to be configured before use and which deals with the system
landscape management
SAP has decided to merge the central mode of SAP NetWeaver Administrator into the new work
centers available as of SAP Solution Manager 70 SP 15 Thus it can be used in an administrative
context together with non-Java-based administration tools Although the central mode of SAP
NetWeaver Administrator will be still available for some time SAP will not develop this tool any
further SAP focuses on optimizing the administrative work centers of SAP Solution Manager
instead
The local mode of SAP NetWeaver Administrator stays untouched It is available for current and
future releases of SAP NetWeaver
SAP Central Process Scheduling by Redwood
SAP Central Process Scheduling application by Redwood enables central job scheduling and job
monitoring of current and old releases of AS ABAP systems (as of Basis Release 31) This application
is fully integrated in SAP NetWeaver Depending on the business needs SAP business applications
are the initial trigger for scheduled activities You can now manage jobs and job chains conveniently
using a graphical user interface
System Landscape Directory
The System Landscape Directory is the central directory of system landscape information relevant
for the management of your software life-cycle It contains a description of your system landscape
(that is software components that are currently installed) and a repository of software components
that can theoretically be installed in your landscape (such as the software components available
from SAP)
Adaptive Computing Controller
5 System Landscape
52 Shared Services
3656 PUBLIC 2011-04-15
The Adaptive Computing Controller enables users to control an adaptive computing landscape
from a single point through observation operation and dynamic resource distribution With
adaptive computing hardware software and system services are able to adapt to changing business
needs In the Adaptive Computing Controller the run-time data of logical and physical landscapes
can be monitored application services can be startedstoppedrelocated and hardware resources
can be assigned to application services The operation can also be mass executed and be planned as
tasks to be executed
For more information about the installation of the Adaptive Computing Controller tool see the
document Installation Guide ndash Adaptive Computing Controller in SAP NetWeaver 71 available on SAP Service
Marketplace at httpservicesapcominstallNWPI71
For more information about Adaptive Computing in general see httpsdnsapcomirj
sdnadaptive
521 Use Cases
You can use the applications and tools described above for use cases that are normally performed
centrally The following sections describe these use cases
5211 End-to-End Solution Operations
Running business applications through their complete life-cycle is a challenge Therefore SAP has
started the Run SAP methodology for implementing End-to-End Solution Operations Based on a set
of SAP standards a roadmap and a package for training and certification Run SAP helps customers to
facilitate End-to-End Solution Operations
You can download the SAP standards for Solution Operations from SAP Service Marketplace at http
servicesapcomsupportstandards They describe roles customers typically have in their IT
environment For optimal role support SAP has grouped existing and new functions in SAP Solution
Manager work centers as of SAP Solution Manager 70 Support Package 15 Operations aspects are fully
covered by adding administrative functions for SAP NetWeaver as well Work centers are ABAP Web
Dynpro-based applications They offer the following advantages
Easy to use similar look and feel
Context transfer while jumping from one work center into another
Logical grouping of tools for a certain area
Simple authorization concept
Easy to expand
Each IT role belongs to one or more work centers For instance the Technical Administrator IT role is
covered by the work centers for System Monitoring System Administration and Landscape Management
The following work centers are available
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3756
Business Process Operations
Change Management
Root Cause Analysis
Implementation Upgrade
Incident Management
Test Management
Job Management
System Landscape Management
Solution Documentation Assistant
SAP Engagement and Service Delivery
SAP Solution Manager Administration
System Administration
System Monitoring
My Home is the central point of access to all important data of almost all work centers in SAP Solution
Manager
5212 Support Infrastructure
A key requirement for effective support of IT solutions is the ability to perform root cause analysis with
speed and efficiency
With SAP Solution Manager SAP has long had an infrastructure in place for its ABAP applications that
efficiently supports SAP solutions This helps ensure the high availability and smooth running of
business processes For more information see the SAP Solution Manager section
With Solution Manager Diagnostics this knowledge has been extended to Java applications If for
example homegrown Java applications cause instability Solution Manager Diagnostics helps trace the
cause to eradicate the problem rapidly Solution Manager Diagnostics is fully integrated into SAP
Solution Manager 70 Solution Manager Diagnostics also contains two third-party tools CArsquos Wily
Introscopereg for measuring performance as well as troubleshooting problems of the Java EE Engine
and applications running on it and Mercury Loadrunnerreg which enables SAP Support to produce a
defined load in the SAP solution landscape remotely For more information see Solution Manager
Diagnostics [page 43]
The support infrastructure provides SAP Support with safe access to your productive landscape for safe
root cause analysis so ensuring that SAP Support does not change your landscape inadvertently You
require a support infrastructure to run SAP NetWeaver
The following figure shows the overall infrastructure including SAP NetWeaver administration tools
that are used by administrators or operators at the customer site
5 System Landscape
52 Shared Services
3856 PUBLIC 2011-04-15
Landscape Aspects
If you use SAP NetWeaver Process Integration 71 productively besides SAP Solution Manager (as a
central support platform) you have to set up Solution Manager Diagnostics for supportability reasons
Implementation Sequence
For information about the implementation of the support infrastructure see the document Master
Guide ndash SAP Solution Manager 70 available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution Manager ltReleasegt
5213 Collection of Landscape Data
Amongst other applications and services the support infrastructure and the SAP NetWeaver
administration tools rely on system landscape data
For SAP NetWeaver PI 71 you have to run non-ABAP components in your solution landscape
Therefore the System Landscape Directory is mandatory The landscape data that is automatically
gathered by the System Landscape Directory is replicated to SAP Solution Manager There are several
topology options for the System Landscape Directory They offer different grades of availability
administration and operation effort
For more information see the System Landscape Directory section
5214 Authentication and Single Sign-On
Before implementing your system landscape plan how to implement authentication and how to
integrate different systems into a Single Sign-On landscape Single Sign-On reduces complexity for end
users saving them valuable time while also reducing administration effort for resetting passwords
thereby contributing to TCO reduction
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
5215 Integrated User and Access Management
In a system landscape containing a combination of ABAP and Java components we recommend that
you integrate your user and access management so that you can use the same user data across different
systems administer this data centrally and control access to data SAPs mature fine-grained
authorization concept allows detailed control of access rights SAP NetWeaver provides both ABAP and
Java-based user management solutions The user management solution that you use to administer
your user data depends on factors such as the type of systems that are running in your landscape
If you want to use central user administration we recommend that you run it in a non-production
system If you do not have a central user administration yet you can for example realize it in the SAP
Solution Manager system
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3956
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
522 Examples for the Overall System Landscape of Shared Services
In this section we provide examples of how shared services can be set up depending on the system
landscape they are intended for The following examples aggregate the landscape aspects given in the
Use Cases section
NOTE
The following sections and the figure mostly do not show information about the life-cycle of
shared services For example you may also need a development and testquality assurance system
for SAP Solution Manager You should consider this aspect in addition to the information given
in this section based on your requirements
Small and MediumndashSized Customer Landscapes with Java
As you use Java productively for SAP NetWeaver PI 71 besides SAP Solution Manager you have to set
up additional components for optimal monitoring administration and support Solution Manager
Diagnostics and the central mode of SAP NetWeaver Administrator are already fully integrated into
SAP Solution Manager 70 as the central operations hub For SAP Process Integration you must also
set up SAP NetWeaver Administrator with a special role
We recommend that you do not install SAP Central Process Scheduling in the SAP Solution Manager
system You have to set up and operate the system which hosts your productive scheduler as a mission
critical system
In the SAP Solution Manager system you should set up a local System Landscape Directory in addition
to a central runtime System Landscape Directory This way you have a clear separation between your
management system (SAP Solution Manager) and managed systems in your landscape In addition
SAP Solution Manager then does not rely on a System Landscape Directory running in the production
environment For this setup configure the SLD data suppliers of your SAP Solution Manager system
to send data to the central runtime System Landscape Directory In addition configure automatic
bridge forwarding from your runtime System Landscape Directory to the local System Landscape
Directory For more information see the Planning Guide - System Landscape Directory
If you want to use a central system for Adobe Document Services we recommend that you install a
dedicated system for this purpose in your production environment For detailed information about
the sizing of the system for the different use cases see the Sizing Guide for Adobe Document Services at
SAP Service Marketplace at httpservicesapcomsizing Sizing Guidelines Solutions amp
Platform
We recommend that you start with this centralized SAP Solution Manager approach as depicted in the
following figure
5 System Landscape
52 Shared Services
4056 PUBLIC 2011-04-15
Figure 7 Single SAP Solution Manager Landscape
Large Customer Landscapes with Java
Large customers who have environments in their landscape that are large and distributed administered
by different groups or separated for security reasons can consider a distributed operations setup In
addition to the centralized setup described for small- and medium-sized customers above large
customers can put parts of the central management functions on extra hosts or systems for performance
or policy reasons You have the following options for a distributed setup
You may set up an extra system or client for Central User Administration (CUA)
The Change and Transport System (CTS) can run on an extra system However it is not
performance- or data-intensive
You may set up an extra system for central CCMS monitoring Depending on the customizing
and on the landscape size central CCMS may generate a lot of system load You can connect a
separate central CCMS to SAP Solution Manager for displaying alerts in the alert inbox of the System
Monitoring work center
You can use a separate SAP NetWeaver 70 system with usage type BI together with SAP Solution
Manager This may make sense with respect to the amount of landscape management data that is
stored for reporting purposes The amount of data strongly depends on the data granularity
storage time frame and landscape size
You can easily put Wily Introscope Enterprise Manager on an separate host
Other aspects described above for small- and medium-customers (such as the setup of the System
Landscape Directory) are also valid for large customers
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4156
523 Feature Details
This section provides further information about the features described above
5231 SAP Solution Manager
SAP provides you with SAP Solution Manager as the strategic application management platform and
to enable the collaboration between you and SAP You need to install at least one productive SAP
Solution Manager in your system landscape To ensure the availability of this application management
platform an SAP Solution Manager system is technically required to install or upgrade to SAP
NetWeaver 70 or higher If you are already using SAP Solution Manager you can also use it to manage
the solution you build with SAP NetWeaver In this case we highly recommend that you update SAP
Solution Manager to the latest version
As of SAP Solution Manager 70 SP15 you can use the newly created work centers
NOTE
During the SAP system installation or upgrade process you are prompted to enter the SAP
Solution Manager key An SAP Solution Manager system is required to generate this key Without
this key the installation or upgrade process cannot continue
You may generate all needed keys for your entire system landscape (development quality
assurance and production system) in one SAP Solution Manager system In case you plan to install
several solution landscapes (for example in different countries) one SAP Solution Manager
system is still sufficient
For more information see SAP Note 805390
It is possible to install multiple SAP Solution Managers If you do so they should host separate business
solutions
If you want to reduce the risk of unavailability you should not install SAP Solution Manager as a central
component Instead you can operate a 2-system-landscape with both a test and production
environment of SAP Solution Manager (especially if you are using time-critical functions like Support
Desk) If you also develop your own content a 3-system-landscape with a development test and
production environment is recommended
For more information about SAP Solution Manager see the following table
Topic Where to Find More Information
System infrastructure scenarios installation and configuration of SAP Solution Manager
Master Guide ndash SAP Solution Manager available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution ManagerltReleasegt
Benefits and usage scenarios SAP Solution Manager ndash Learning Maps available on SAP Service Marketplace at http
5 System Landscape
52 Shared Services
4256 PUBLIC 2011-04-15
Topic Where to Find More Informationservicesapcomrkt-solman or https
servicesapcomsolutionmanager
Additional information See SAP Service Marketplace at http
servicesapcomsolutionmanager
5232 Solution Manager Diagnostics
Solution Manager Diagnostics provides efficient and safe root-cause analysis of incidents in customer
solutions powered by SAP NetWeaver It can help monitor on operating systems databases Java
application activities performance and logs It also supports the reporting of software and
configuration changes that can lead to malfunctions and errors
You must run one Solution Manager Diagnostics within your SAP solution landscape if you run
applications based on SAP NetWeaver systems with usage type AS Java Agents are responsible for
delivering the data from all productive hosts within your system landscape to the Solution Manager
Diagnostics system
CAUTION
SAP Support performs root-cause analysis on incoming incidents with Solution Manager
Diagnostics Not installing and configuring this support infrastructure results in a dramatically
reduced service level
Solution Manager Diagnostics is fully integrated into SAP Solution Manager 70
Solution Manager Diagnostics also contains Wily Introscope (Display Server and Agent part) for
measuring performance as well as to troubleshoot problems of Non-ABAP applications Wily Introscope
is heavily used for troubleshooting applications running on AS Java
SAP has signed a distribution agreement for Wily Introscope SAP customers are allowed to use this
tool in a preconfigured way
For more information about Solution Manager Diagnostics and an FAQ list see SAP Service Marketplace
at httpservicesapcomdiagnostics
5233 System Landscape Directory
The System Landscape Directory (SLD) of SAP NetWeaver is the central directory of system landscape
information relevant for the management of your software life-cycle
NOTE
Note that the abbreviation SLD is not intended to define a product since the System Landscape
Directory is part of SAP NetWeaver This abbreviation is solely intended to improve readability
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4356
The System Landscape Directory contains a description of your system landscape (that is software
components that are currently installed) and a repository of software components that can
theoretically be installed in your landscape (such as the software components available from SAP)
Since this data gets updated automatically the System Landscape Directory provides reliable and up-
to-date system landscape information with as little effort for you as possible In this way the System
Landscape Directory acts as a central information provider for SAP and third-party tools that use this
data to deliver the services you need to keep your landscape up and running
For the System Landscape Directory as part of an SAP NetWeaver PI 71 landscape consider the following
aspects
Part of SAP NetWeaver PI 71 is a new version of the System Landscape Directory It is automatically
included in every SAP NetWeaver 71 system with usage type AS Java It offers enhanced functions
such as a full automatic synchronization mechanism for all data stored in it That is both data
delivered by data suppliers and data entered or changed manually in the System Landscape
Directory can be synchronized automatically This synchronization offers the following
A fully automated mechanism so no user interaction is required and conflicts are resolved
automatically
Asynchronous propagation of information so some nodes may be down temporarily
Communication over HTTP protocol
Uni- and bi-directional synchronization
Depending on your use case the full automatic synchronization could significantly reduce manual
synchronization effort
For SAP NetWeaver PI 71 the configuration of the system landscape directory and its data suppliers
is already included in the standard implementation procedure with SAPinst For existing systems
you only have to perform some quick and easy configuration actions to start operating the system
landscape directory server in an AS Java system
For SAP NetWeaver PI 71 you have the following options concerning SLD
Option 1
Run SAP NetWeaver PI 71 against an existing SLD running on SAP NetWeaver 70 We only
recommend this for upgrades from SAP NetWeaver 70 if you have a central SLD in operation
not running on one of your PI systems
Option 2
Use the SLD included in an SAP NetWeaver PI 71 system We recommend this option for new
installations and upgrades from older releases than SAP NetWeaver 70 due to the enhanced
functions and improved performance of SLD 71
NOTE
If you already have a central SLD running on SAP NetWeaver 70 in operation you could run
two SLD versions in parallel ndash SLD running on SAP NetWeaver 71 for your PI systems and
SLD running on SAP NetWeaver 70 for all other systemsuse cases This way your SAP
5 System Landscape
52 Shared Services
4456 PUBLIC 2011-04-15
NetWeaver PI 71 systems would benefit from the new features while it would be easy to set
up and operate such an SLD landscape For this purpose you could use the new fully
automatic synchronization This feature enables the automatic forwarding of all SLD data
from an SLD running on SAP NetWeaver 70 to an SLD running on SAP NetWeaver 71 As a
result there is no need to adapt most existing systems as their SLD data suppliers could still
send their data to the central SLD In brief the following steps would be required
1 Put SLD in a PI system into operation (part of standard implementation procedure)
2 Configure PI systems to use the new SLD (part of standard implementation procedure
for new PI systems)
3 Set up the fully automatic synchronization from your old SLD to your new SLD
As soon as an upgrade or an installation of a standalone AS Java 71 system is available you
could move your central SLD also to SAP NetWeaver 71 Then you could optionally shift
your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems
Figure 8
We recommend that you use a Domain Name System (DNS) alias so that you are able to switch to
another System Landscape Directory easily For example if customers build a new landscape they
normally start with a sandbox environment Over time more and more environments are set up
Once the production environment is in place move the System Landscape Directory there To do
this you can configure a new System Landscape Directory in the production environment
synchronize it with the old System Landscape directory and switch to the new one
Topology
Apart from the considerations above the System Landscape Directory offers several topology options
with different grades of availability at the expense of low administration and operation effort There is
no generic rule therefore on how to set up a System Landscape Directory in your system landscape
To find the topology and synchronization strategy for the System Landscape Directory that fits your
requirements concerning the System Landscape Directory availability (and hence the availability of
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4556
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
Document History
CAUTION
Before you start the implementation make sure you have the latest version of this document
You can find the latest version on SAP Service Marketplace httpservicesapcom
instguides
The following table provides an overview on the most important document changes
Version Date Description
10 2007-12-07 First version
11 2008-02-05 Changes to System Landscape Directory section Minor changes
12 2008-04-22 Major revision of Shared Services section
13 2008-05-29 Information about dedicated PI system updated
14 2008-12-12 Restructuring of content according to use case concept Information about SAP enhancement package 1 for SAP NetWeaver PI 71 added
15 2009-03-19 Minor changes (mainly language corrections)
16 2009-03-20 Minor error corrections
17 2011-04-15 Section SAP Enhancement Package 1 for SAP NetWeaver PI 71 updated (Software Update Manager replaces SAP Enhancement Package Installer)
Section Process Sequence Installation of Enhancement Package 1 on an Existing SAP NetWeaver PI 71 system added
Section Maintaining System Landscape Information added Further minor changes
2011-04-15 PUBLIC 556
Table of Contents
Chapter 1 Introduction 9
Chapter 2 Before You Start 11
21 SAP Notes 11
22 More Information 11
23 Accessing the SAP Library 12
Chapter 3 SAP NetWeaver PI Overview 13
31 Installable Software Units 15
311 Systems with Usage Types 16
312 Standalone Engines 19
313 Clients 21
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration
71 23
Chapter 4 SOA-Based Integration Use Case 25
41 Overview 25
42 System Landscape 25
43 Implementation Sequence 27
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP
Netweaver PI 71 System 28
Chapter 5 System Landscape 33
51 Planning Your System Landscape 33
52 Shared Services 35
521 Use Cases 37
5211 End-to-End Solution Operations 37
5212 Support Infrastructure 38
5213 Collection of Landscape Data 39
5214 Authentication and Single Sign-On 39
5215 Integrated User and Access Management 39
522 Examples for the Overall System Landscape of Shared Services 40
656 PUBLIC 2011-04-15
523 Feature Details 42
5231 SAP Solution Manager 42
5232 Solution Manager Diagnostics 43
5233 System Landscape Directory 43
Chapter A Appendix 47
A1 Maintaining System Landscape Information 47
Chapter B Reference 51
B1 The Main SAP Documentation Types 51
B2 List of Documentation 51
2011-04-15 PUBLIC 756
This page is left blank for documents that are printed on both sides
1 Introduction
This Master Guide provides you with a central starting point for the technical implementation of SAP
NetWeaverreg Process Integration (SAP NetWeaver PI) It also contains information about enhancement
package 1 for SAP NetWeaver Process Integration 71
SAP NetWeaver PI 71 is based on an established architecture for realizing cross-system business processes
and supporting an service-oriented architecture (SOA) The focus is on the service-based integration
of applications
Structure of the Master Guide
The Master Guide consists of the following sections
Introduction
Contains an introduction to this guide
Before You Start
Contains information about this document important things which you need to know before you
start and information on how to access the SAP Library
SAP NetWeaver Overview
Describes the building blocks of SAP NetWeaver PI
SOA-Based Integration Use Case
Introduces the use case and explains how to install it
System Landscape
Contains information about how to install your system landscape
Reference
Contains information about the overall documentation concept for SAP systems
CAUTION
Make sure you have the latest version of the Master Guide by checking SAP Service Marketplace
immediately before starting the installation
The Master Guide is regularly updated on SAP Service Marketplace at http
servicesapcominstallnwpi71 Planning
Constraints
The business scenarios that are presented here serve as examples of how you can use SAP software in
your company The business scenarios are intended only as models and do not necessarily run the way
they are described here in your customer-specific system landscape Check your requirements and
systems to determine whether these scenarios can be used productively at your site Furthermore we
1 Introduction
2011-04-15 PUBLIC 956
recommend that you test these scenarios thoroughly in your test systems to ensure that they are
complete and free of errors before going live
1 Introduction
1056 PUBLIC 2011-04-15
2 Before You Start
21 SAP Notes
You must read the following SAP Notes before you use this Master Guide and implement SAP NetWeaver
Make sure that you have the up-to-date version of each SAP Note which you can find on SAP Service
Marketplace at httpservicesapcomnotes
NOTE
The SAP Notes related to SAP NetWeaver PI 71 are also listed on SAP Service Marketplace at
httpservicesapcomsapnotesnwpi71
List of Important SAP Notes
SAP Note Number Title Description
1004107 Release Restrictions for SAP NetWeaver PI 71
Some restrictions apply to the productive use of SAP NetWeaver PI 71 These are documented in this SAP Note
1247043 Release Restrictions for SAP EHP1 for SAP NetWeaver PI 71
Some restrictions apply to the productive use of enhancement package 1 for SAP NetWeaver PI 71 These are documented in this SAP Note
22 More Information
The following table contains links to information available on SAP Service Marketplace or in the SAP
Library which is important for implementing SAP NetWeaver
Content Location on SAP Service Marketplace or in SAP Library
The latest version of the installation and upgrade guides for SAP NetWeaver Process Integration
httpservicesapcominstguidesnwpi71
Information about supported platforms (operating systems databases browsers) for all SAP NetWeaver components
httpservicesapcomplatforms Product Availability Matrix
Sizing of SAP NetWeaver httpservicesapcomsizing
Information about security SAP Security Guide See the SAP Library [page 12] at Adminitstratoracutes Guide Security Guide
Information about the technical operation of SAP NetWeaver
Technical Operations Manual See the SAP Library [page 12] at Adminitstratoracutes Guide Technical Operations for SAP NetWeaver
2 Before You Start
21 SAP Notes
2011-04-15 PUBLIC 1156
Content Location on SAP Service Marketplace or in SAP Library
Information about SAP NetWeaver PI Support Package Stacks
httpservicesapcomnetweaver SAP NetWeaver PI 71- Release-Specific Information Support Package Stacks Information
Information about installing SAP NetWeaver Support Package Stacks
httpservicesapcomMaintenanceNWPI71
Support Package Stack Guide ndash SAP NetWeaver
23 Accessing the SAP Library
For more information about SAP NetWeaver Process Integration access the SAP Library from any of
the following
SAP Help Portal at httphelpsapcomNWPI71 SAP NetWeaver Process Integration 71 Library
ltLanguagegt SAP NetWeaver Process Integration Library
CAUTION
The SAP Help Portal contains the latest version of the SAP Library Therefore we recommend
that you use this channel to access the SAP Library
An SAP system if you have installed the online documentation Choose Help SAP Library
The browser starts
The help files on the online documentation CDs or DVDs
If you want to view the help files in HTMLHelp format from the online documentation CDs or
DVDs you need a PC running Microsoft Windows to install the HTMLHelp Viewer
2 Before You Start
23 Accessing the SAP Library
1256 PUBLIC 2011-04-15
3 SAP NetWeaver PI Overview
Introduction
SAP NetWeaver PI 71 is part of the SAP NetWeaver technology platform The complete offering of the
SAP NetWeaver technology platform is visualized in the SAP NetWeaver technology map which you
can access at httpsdnsapcomnetweaver SAP NetWeaver at a Glance The technology map
enables you to drill down from top-level technology areas (for example Lifecycle Management) to
individual capabilities (for example Administration Monitoring and so on)
SAP NetWeaver PI includes the following capabilities
Repository-based Modeling and Design
Service Bus-based Integration
SOA Management
A different view is introduced by the end-to-end use case concept This concept offers an
implementation view on SAP NetWeaver to structure and facilitate your implementation
A use cases is a process that typically involves several SAP NetWeaver capabilities It is not limited to a
single component or capability A use case guides you through the different phases of your
implementation project ndash from information through installation to the configuration phase This
implies that a uses case addresses several user roles administrator power user and end user
This document describes the SOA-based integration use case
Architecture Principals
The architecture of SAP NetWeaver Process Integration 71 (SAP NetWeaver PI 71) is based on an
established architecture for realizing cross-system business processes and is a further development of
lower releases (SAP NetWeaver 70 usage type Process Integration and SAP XI 30 as part of SAP
NetWeaver 2004) SAP NetWeaver PI 71 plays an important role in supporting an service-oriented
architecture (SOA) The focus is on the service-based integration of applications
SAP NetWeaver PI is based on general standards so as to enable 3rd-party systems to be integrated At
the center of SAP NetWeaver PI is an XML-based communication that uses HTTP (Hyper Text Transfer
Protocol) Irrespective of the scenario used the application-specific contents are transferred in messages
in user-defined XML (eXtensible Markup Language) from the sender to the receiver either via the
Integration Server or directly between the systems involved
The following figure gives an overview of the key capabilities of SAP NetWeaver Process Integration
3 SAP NetWeaver PI Overview
2011-04-15 PUBLIC 1356
Figure 1 SAP NetWeaver PI Key Capabilities Overview
SAP NetWeaver Process Integration 71 enables the integration of the applications of the following
communication parties
B2B Party Any business partners that want to integrate their application with other applications
outside their own system landscape Scenarios that require industry standards are supported as
well as any scenarios that do not adhere to a particular industry standard
SAP Applications that run on SAP systems This includes the processing of events by using the
Business Activity Monitoring (BAM) infrastructure
3rd-Party Application Applications from 3rd-party providers within one system landscape for
example database or file-system-based
3rd-Party Middleware Middleware systems from 3rd-party providers that are required for the
integration of applications within a company and across company boundaries
SAP NetWeaver PI also supports internal company scenarios and cross-company scenarios It enables
you to connect systems from different vendors (non-SAP and SAP) in different versions and
implemented in different programming languages (Java ABAP and so on) to each other Like the rest
of the SAP NetWeaver platform SAP NetWeaver PI is based on an open architecture uses open standards
(in particular those from the XML and Java environments) and offers those services that are essential
in a heterogeneous and complex system landscape
To enable end-to-end SOA development SAP NetWeaver Process Integration 71 offers a Universal
Description Discovery and Integration (UDDI) v3-based Services Registry where providers can publish
service endpoints definitions and associated metadata and consumers can discover the appropriate
services for their scenarios The Services Registry provides capabilities for classifying and browsing
3 SAP NetWeaver PI Overview
1456 PUBLIC 2011-04-15
services using semantic-rich classification systems The Services Registry is part of Application Server
Java (AS Java)
31 Installable Software Units
SAP NetWeaver comprises the following three types of installable software units
Systems that are configured for a specific purpose as indicated by one or more usage types
Standalone engines that provide one specific (server) function in combination with one or more
SAP NetWeaver PI systems
Clients used by (many) people from their local front-end PC to access functions offered by systems
of SAP NetWeaver PI or standalone engines in the system landscape
In the following sections you can find more details about the software units The figure below provides
and overview of the software units
Figure 2 Installable Software Units for SAP NetWeaver PI
For this and other figures in this guide the following legend applies
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1556
Figure 3 Legend
311 Systems with Usage Types
SAP systems are the main building blocks of SAP NetWeaver They are identified by unique SAP system
IDs (SAPSIDs) and configured for a certain purpose as indicated by usage types Usage types have the
following characteristics
They are a structuring element for SAP software on a technical level
Usage Types determine the intended purpose of a system and the role it plays in a given (distributed)
use case
They are realized by installing and configuring a collection of software components
They allow a logical view of the technology platform SAP NetWeaver PI
A usage type may require other usage types in the same system to operate
They can also be run in the same system together with other usage types that are not a prerequisite
How SAP NetWeaver Systems are Used
The following sections describe the usage types and their dependencies for SAP NetWeaver PI
Application Server ABAP (AS ABAP)
Purpose
AS ABAP is used to provide the ABAP foundation of SAP NetWeaver PI
Application Server ABAP provides a complete development and runtime environment for ABAP-based
applications It is optimized for the development of highly scalable business applications The ABAP
development and runtime environment makes it possible to develop complex business applications
3 SAP NetWeaver PI Overview
31 Installable Software Units
1656 PUBLIC 2011-04-15
without having to worry explicitly about technical details such as process or memory administration
multi-user capability database connections or similar issues These are provided in the basis services or
are integrated directly in the ABAP runtime The application development is similarly independent of
the underlying platform The application server decouples the application coding completely from the
operating system and database that are used
Dependencies
AS ABAP can be combined optionally with other usage types in one system
Application Server Java (AS Java)
Purpose
AS Java is used to provide the Java foundation of SAP NetWeaver PI using the Java Engine a Java EE-
compliant application server for running enterprise applications In addition to the pure Java EE
standard technologies the Java Engine implements complementary technologies such as Web Dynpro
or Web Services that are targeted at supporting large-scale real-business application development
projects
Dependencies
AS Java can be combined optionally with other usage types in one system
Process Integration (PI)
Purpose
PI consists of core components that model design automate and integrate processes in one or more
application systems For the integration of internal and cross-company processes PI is used to
incorporate all the functions of what was formerly known as Exchange Infrastructure (XI) In addition
PI contains core components for Business Process Management for application-embedded and
application-unbounded processes
The Advanced Adapter Engine is also part of usage type PI You use Advanced Adapter Engine to connect
to SAP systems (RFC adapter) and external systems You use the various adapters in Advanced Adapter
Engine to convert XML- and HTTP-based messages to the specific protocol and format required by
these systems and the other way around You can use the Advanced Adapter Engine that is part of
your PI system as a central Advanced Adapter Engine Optionally (for performance reasons) you can
install a non-central Advanced Adapter Engine [page 19] separately as a system with AS Java and parts of the
usage type PI on a separate host
Dependencies
PI requires AS ABAP and AS Java as prerequisites in the same system
For installing PI it is mandatory to have a dedicated PI system This applies to development quality
and production landscapes It is a prerequisite that no other system in your system landscape has a
higher release and enhancement package level than the PI system If you want to upgrade or install an
application in your system landscape you first have to make sure that the current release and
enhancement package level of the PI system is on the same level - if required you have to upgrade the
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1756
PI system first to the new or a higher release In a dedicated PI system this can be accomplished with a
minimum of downtime Also the PI system would not be affected by the downtime of other usage
types running in the same system
Configuration of Systems with Usage Types
Configuration information is available in the installation guides the configuration wizard and SAP
Solution Manager
In the Installation Guide ndash SAP NetWeaver PI 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt you find
initial technical configuration tasks This guide also informs you about how you can run the
configuration wizard and how you can access the configuration information in SAP Solution
Manager
For certain usage types configuration tasks can be applied by the configuration wizard after the
installation To do this you start the configuration wizard from SAP NetWeaver Administrator
The configuration steps for systems with usage types required for an use case are accessible through
SAP Solution Manager
To be able to use SAP Solution Manager for the configuration tasks you have to import the latest
SAP Solution Manager Implementation Content (Add-On ST-ICO) that is available for your SAP
Solution Manager release For more information see SAP Note 631042 (Release strategy for Implementation
Content (ST-ICO))
SAP Solution Manager Implementation Content is available on SAP Service Marketplace at
httpservicesapcomswdc Installations amp Upgrades Entry by Application Component SAP
Technology Components SAP Solution Manager ltReleasegt Content ST-ICO
In SAP Solution Manager you create a project and a project structure In the configuration phase
you select configuration structures with pre-delivered SAP content for your project You can find
the following different types of configuration tasks in SAP Solution Manager
Mandatory configuration tasks All configuration tasks that are mandatory for the standalone
engine or usage type
Optional configuration tasks Configuration tasks for areas where customers need to decide
if they want to use these functions (for example high availability or security settings)
Additional functions ndash configuration tasks Configuration tasks for functional units that are
used in certain use cases only
A marked checkbox in front of the configuration tasks indicates those configuration tasks that are
relevant for the use case you have chosen To configure ABAP systems SAP Solution Manager
offers executable configuration files (IMG activities)
For information about using SAP Solution Manager Content and creating a configuration guide
see the following documentation
httphelpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Implementing
and Upgrading SAP Solutions Configuration
3 SAP NetWeaver PI Overview
31 Installable Software Units
1856 PUBLIC 2011-04-15
How to Create a Configuration Guide using SAP Solution Manager available at http
servicesapcomsolutionmanager Media Library How-To Documents
Restrictions for Systems with Multiple Usage Types
If you have one system with multiple usage types be aware that we do not provide standard tools
to separate these usage types and distribute them to multiple systems at a later stage For example
if you have a system with usage types A and B you are not able to migrate it with SAP standard
tools into two systems one with usage type A only and the other with usage type B only
In addition we do not provide standard tools to merge multiple systems with different usage types
into one system with multiple usage types at a later stage
If you want to perform these tasks you require specific project support
The following figure shows that SAP standard system copy and migration tools do not support
you in separating or merging systems with usage types
Figure 4 No Support for Merging or Separating Systems with Usage Types
Although you can use one system for multiple usage types client restrictions apply for usage type
PI PI requires a dedicated client due to special PI requirements concerning the client pipeline
Whereas application client pipelines only send and receive messages the central PI pipeline can
also map messages to different formats before sending them
312 Standalone Engines
Standalone engines of SAP NetWeaver are additional installable software units They do not work as
full-blown systems of SAP NetWeaver but as standalone engines that provide a specific (server) function
in combination with one or more SAP NetWeaver systems
Standalone engines are not part of a usage type They do not run on AS ABAP or AS Java
The standalone engines that are available for SAP NetWeaver Process Integration are described in the
following
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1956
Gateway
It is possible to install an SAP instance of an SAP NetWeaver system based exclusively on a standalone
gateway This type of instance does not contain normal work process types (dialog background update
enqueue or spool) Only the gateway process (gwrd) is started If there is an SNA connection to an R
2 system gateway work processes (gwwp) are also started
SAP Conversion Agent by Informatica
SAP Conversion Agent by Informatica is a data conversion tool that enables you to create interfaces
between any data formats and XML-based systems SAP Conversion Agent can convert unstructured
semi-structured and structured formats to XML and the other way around The Conversion Agent
comprises the Conversion Agent Studio and the Conversion Agent Engine In the Conversion Agent
Studio you can develop and configure data conversions The Conversion Agent Engine executes the
data conversions
Search and Classification (TREX)
You can use Search and Classification with SAP NetWeaver PI to search for messages that were previously
indexed Message search using index provides additional methods of searching for specific messages In
addition to static header attributes you can also use adapter-specific message attributes and data from
the message payload for the search A requirement of this however is that the messages are indexed
first You can apply the index-based message search to one or all indexed components of an integration
landscape (domain) Integration Server Adapter Engines and ABAP business systems
For more information see the SAP Library [page 12] at Administratorrsquos Guide Technical Operations for SAP
NetWeaver Administration of SAP NetWeaver Systems Administering PI (Process Integration) Monitoring Index
Administration
Web Dispatcher
The Web Dispatcher lies between the Internet and your SAP system It is the entry point for HTTP(s)
requests into your system which consists of one or more SAP NetWeaver application servers As a
software web switch the Web dispatcher can reject connections or accept them When it accepts a
connection it balances the load to ensure an even distribution across the servers
You can use the Web dispatcher in ABAPJava systems and in pure Java systems as well as in pure ABAP
systems
It is also beneficial to use the Web Dispatcher if you do not need security functions (entry point in the
demilitarized zone (DMZ) SSL URL filtering) but you simply want to balance the load between
multiple SAP NetWeaver Application Server instances
Since Web Dispatcher is optional for every SAP system it is not contained in the system landscape and
the implementation sequence of the use case in this documentation
For more information see the SAP Library [page 12] at Function Oriented View Application Server Infrastructure
SAP Web Dispatcher
3 SAP NetWeaver PI Overview
31 Installable Software Units
2056 PUBLIC 2011-04-15
Advanced Adapter Engine
You use the Advanced Adapter Engine to connect to SAP systems (RFC adapter) and external systems
You use the various adapters in Advanced Adapter Engine to convert XML- and HTTP-based messages
to the specific protocol and format required by these systems and the other way around For specific
senderreceiver combinations messages can be processed without invoking the central Integration
Engine In principle you connect external systems using the adapters that are installed centrally or
non-centrally in Advanced Adapter Engine You can use the Advanced Adapter Engine that is part of
your PI system as a central Advanced Adapter Engine Optionally (for performance reasons) you can
install a non-central Advanced Adapter Engine separately as a system with AS Java and parts of the
usage type PI on a separate host
Adapter Engine (Java SE)
Adapter Engine (Java SE) is a separate software unit You can use it only if you have SAP NetWeaver
systems with usage type PI in your system landscape It has to be installed manually You use the Adapter
Engine (Java SE) to connect to external systems Using the various adapters in the Adapter Engine (Java
SE) XML and HTTP-based messages can be converted to the specific protocol and format required by
such systems and the other way around The Adapter Engine (Java SE) only provides some of these
adapters as a standalone version with restricted functions for operating systems that do not support
SAP NetWeaver PI 71 but that have at least a Java Runtime Environment 50 Therefore you should
use the Adapter Engine (Java SE) only if the platform prerequisites do not allow you to use the Advanced
Adapter Engine
SAP Partner Connectivity Kit
SAP Partner Connectivity Kit (PCK) runs on AS Java with parts of the usage type PI It enables a system
of a smaller company or subsidiary that does not run SAP NetWeaver PI to connect to your SAP
NetWeaver systems
313 Clients
Clients are additional installable programs or tools They reside either on local front-end PCs accessed
by users or on back-end systems where they act as client programs within an SAP NetWeaver system
landscape
The clients that you can use with SAP NetWeaver Process Integration are described in the following
sections
SAP GUI
NOTE
We recommend that you use the following versionsI
SAP GUI for Windows 710 (or higher) with the latest patch level
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 2156
SAP GUI for Java 710 (or higher) with the latest revision
The integrated SAP ITS 710
For more information about the SAP GUI family see SAP Service Marketplace at http
servicesapcomsapgui
SAP offers three different client applications for accessing ABAP applications in SAP systems (such as
SAP NetWeaver systems with usage type AS ABAP) This SAP GUI family consists of
SAP GUI for HTML
SAP GUI for HTML is based on the SAP integrated Internet Transaction Server (ITS) which is
included in the installation of SAP NetWeaver systems as of SAP NetWeaver 2004 On the client
side only a suitable browser (such as Internet Explorer 70 or Firefox 20) and a virtual machine are
required SAP ITS 620 is not compatible with SAP NetWeaver 71
SAP GUI for the Java environment (SAP GUI for Java)
SAP GUI for Java is a generic SAP GUI that covers a variety of platforms
For more information about the installation of SAP GUI for Java see the documentation Installation
Guide ndash SAP Front End
SAP GUI for the Windows environment (SAP GUI for Windows)
SAP GUI for Windows is SAPs universal client for accessing all SAP applications built on ABAP
technology It is available on the Microsoft Windows platform only and offers the broadest feature
set of all members of the SAP GUI family
For more information about the installation of SAP GUI for Windows see the Installation Guide ndash
SAP Front End
SAP NetWeaver Developer Studio
The SAP NetWeaver Developer Studio is SAPrsquos Integrated Development Environment (IDE) for Java
and is based on the open-source tools framework Eclipse 33 With the SAP NetWeaver Developer Studio
you can develop Java EE 5 applications from scratch using the built-in support for new technologies
such as EJB 30 and JSF 12
During the installation of the SAP NetWeaver Developer Studio several features are offered for
installation For SAP NetWeaver PI 71 only the following features are relevant
SAP NetWeaver Developer Studio Platform
SAP NetWeaver Developer Studio Java EE
NOTE
If you want to use one of the other features you need SAP NetWeaver Composition Environment
and a corresponding developers licence
For more information about the installation of SAP NetWeaver Developer Studio see the Installation
Guide ndash SAP NetWeaver Developer Studio 71 or Installation Guide ndash SAP NetWeaver Developer Studio 71 Including
Enhancement Package 1
3 SAP NetWeaver PI Overview
31 Installable Software Units
2256 PUBLIC 2011-04-15
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
SAP enhancement packages are a new way of delivering new functions for SAP NetWeaver This allows
a clear separation between the delivery of new functions on the one hand and corrections legal changes
and security updates on the other hand (in Support Package stacks) SAP enhancement packages are
cumulative an enhancement package always contains the functions of the corresponding predecessor
enhancement packages
Enhancement packages are maintained by their own Support Packages while the main release is in
maintenance
Benefits
SAP enhancement packages offer the following benefits
You have reduced effort for testing and no effort for training when applying Support Packages as
new features are only shipped with enhancement packages
Adding new functions between releases becomes predictable and controllable
New functions can be added successively in small steps There is no need to fully upgrade your
system to get new functions
You have minimal training effort when applying an enhancement package because existing
functions are not replaced
Implementation
There are the following ways to get an SAP NetWeaver system with the release level of SAP enhancement
package 1 for SAP NetWeaver Process Integration 71
New installation of SAP NetWeaver PI 71 including enhancement package 1 using the standard
installation tool SAPinst
Upgrade of an existing SAP NetWeaver system from a release lower than SAP NetWeaver PI 71 to
SAP NetWeaver PI 71 including enhancement package 1 For this you use the upgrade programs
SAPup (for ABAP) and SAPJup (for Java)
Installation of the enhancement package on an existing SAP NetWeaver PI 71 system
For this you use the Software Update Manager (SUM) The Software Update Manager evolved
from the previously used SAP Enhancement Package Installer The tool has been renamed to reflect
its broader use for example you can also use it for applying Support Package Stacks to your system
On the ABAP side the Software Update Manager uses a system cloning and switch procedure for
installing enhancement packages It installs a copy of the system the shadow system parallel to
the original system This shadow system is used to update the relevant software components and
to install the additional components while the original system is still in production operation At
a certain point during downtime the switch to the new system is made and afterwards any parts
of the original system that are no longer needed are deleted The enhancement package installation
in a Java system uses a deploy-based procedure that is no shadow system is used The Software
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2011-04-15 PUBLIC 2356
Update Manager requires a stack configuration file (xml file) as input file for the enhancement
package installation procedure This file lists all the packages that are to be installed in your systems
The stack configuration file is generated when you download the required packages
As the Software Update Manager is updated regularly we recommend to always use the latest
version It is delivered as part of the SL toolset For more information see http
servicesapcomsltoolset
For an overview of all required steps for the enhancement package installation process and
corresponding documents see Process Overview Installation of Enhancement Package 1 on an Existing SAP
Netweaver PI 71 System [page 28]
Content of SAP Enhancement Package 1 for SAP NetWeaver PI 71
With enhancement package 1 for SAP NetWeaver PI 71 new features are introduced and some existing
are changed The following is a selection of some of the most important enhancements
Enhanced design and modelling options in the Enterprise Services Repository
New services registry
Support for new Web services standard (Web Services Reliable Messaging)
New modules for the Advanced Adapter Engine
Use of shared memory of the ABAP Application Server for message processing
For more information about the changes see SAP Library [page 12] at Whatacutes new in SAP NetWeaver PI 71
ndash Release Notes
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2456 PUBLIC 2011-04-15
4 SOA-Based Integration Use Case
41 Overview
You can use SOA-based integration to set up the communication between service providers and service
consumers in both application-to-application and business-to-business scenarios and to execute
operate and monitor the communication at runtime SOA-based integration covers both direct (point-
to-point) as well as mediated (via an Integration Server) communication between service providers and
service consumers
The use case spans the whole life cycle of a SOA-based integration scenario including
Scenario modeling and service design in the Enterprise Services Repository
Implementation of the service provider and consumer in the back-end systems
Configuration and finally execution monitoring and operation of the integration scenario
For scenarios using Integration Server or broker-based communication the configuration of the
different connectivity options (for example SOAP RFC Web Services Industry standards and JDBC)
and their enhancements is covered
For more information see the following documents
Service-Enabling with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdnsoa-modeling
Getting Started
Service-Enabling a Legacy Application with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdn
soa-servicebus Getting Started
In the following you will find information about the installation of the involved software units
42 System Landscape
The following figure shows the system landscape for this use case
4 SOA-Based Integration Use Case
41 Overview
2011-04-15 PUBLIC 2556
Figure 5 SOA-Based Integration
It is mandatory to have a dedicated PI system This applies to development quality and production
landscapes
For PI it is a prerequisite that no other system in your system landscape has a higher release than
the PI system For exceptions to this rule see SAP Note 1043047 For example SAP XI 30 is compatible
with SAP NetWeaver 640 and 70 application systems since the same XI protocol is used Apart
from these exceptions if you want to upgrade or install an application in your system landscape
you first have to make sure that the PI system is on the same release level If required you have to
upgrade the PI system first to the new or a higher release
CAUTION
Although it should be technically possible to run an application system with a higher release
than your PI system in your system landscape this is not supported by SAP (apart from the
exceptions listed in SAP Note 1043047) Therefore you run such a landscape at your own risk
You can use the Advanced Adapter Engine that is part of your PI system as a central Advanced
Adapter Engine
Adapter Engine (Java SE) can be installed in a non-SAP Java environment However it only hosts
a subset of the adapter functionality is only supported for compatibility reasons and should be
used only if this is a precondition in your environment
Optionally you can use the Change Management Service (CMS) of an SAP NetWeaver 70 system
with usage type DI to transport design objects and repository objects For more information see
the SAP Library [page 12] at Administratoracutes Guide Technical Operations for SAP NetWeaver Administration
of SAP NetWeaver Systems PI (Process Integration) Software Logistics Transporting ESR Content and Objects
of Integration Directory PI Transports Using the Change Management Service (CMS)
Smaller business partners or subsidiaries that do not run SAP NetWeaver install SAP Partner
Connectivity Kit in their system landscape SAP Partner Connectivity Kit enables XML document
4 SOA-Based Integration Use Case
42 System Landscape
2656 PUBLIC 2011-04-15
exchange between your SAP NetWeaver systems and the partner systems Since SAP Partner
Connectivity Kit gets installed in their system landscape it is not shown in the system landscape
figure above
The AS ABAP system acts as an application and service provider For Java Web Services you also
require AS Java In addition you require SAP NetWeaver Developer Studio on the client side as a
development environment
The Web service client can be either an SAP or a non-SAP application For example an AS ABAP
system or a Web browser could act as application or service consumer
You can install SAP Conversion Agent by Informatica in the system with usage type PI or on a host
where SAP Partner Connectivity Kit is installed or on a host where neither usage type PI nor SAP
Partner Connectivity Kit is installed
43 Implementation Sequence
Procedure
To install this use case perform the steps listed in the following table
StepAction[Corresponding Documentation] Remarks
1 Make sure that you have performed the preparation steps You have planned your system landscape [page 33]
(that is you have decided how many systems you require how you want to use each of these systems and which standalone engines and clients you require)
With the help of your hardware partner you have mapped your systems and standalone engines to properly sized hosts
You have planned and installed shared services [page 35]
2 Installation of system with usage type PI (includes the installation of AS ABAP and AS Java)
NOTE
For usage type PI a Unicode installation is mandatory
[Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt]
If you want to use the features of enhancement package 1 use the direct installation of SAP NetWeaver PI 71 including enhancement package 1
Make sure that you perform the configuration steps as described in the installation guide For certain usage types configuration tasks can be applied by the configuration wizard These configuration tasks as well as any additional configuration steps for your use case are listed in SAP Solution Manager For more information
4 SOA-Based Integration Use Case
43 Implementation Sequence
2011-04-15 PUBLIC 2756
StepAction[Corresponding Documentation] Remarks
see the Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt
3 Install the Adapter Engine (Java SE) engines if required[Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
4 To integrate small business partners and subsidiaries the business partners or subsidiaries install SAP Partner Connectivity Kit running on AS Java with parts of usage type PI in the business partners or subsidiarys system landscape[Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
5 Install SAP Conversion Agent by Informatica if required[SAP Library [page 12] at Function-Oriented View Process Integration SAP Conversion Agent by Informatica Deploying and Using Conversion Agent ]
6 Installation of clients SAP GUI
[Installation Guide ndash SAP Front End]
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
The process sequences give a comprehensive overview of the steps relevant for the enhancement
package installation on an existing SAP NetWeaver PI 71 system
The process sequence is divided into a planning phase and an implementation phase Each step in both
phases contains references to the corresponding documentation to ensure that you can easily find the
information you need
Process
NOTE
To download the enhancement package files and required Support Packages you require the SAP
Solution Manager Maintenance Optimizer You have the following options
Manual Selection
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2856 PUBLIC 2011-04-15
You manually select the required files from SAP Service Marketplace at http
servicesapcomswdc using the SP Stack Application You use the Maintenance Optimize
only to approve the packages which is a prerequisite for the download
Automatic Calculation
The Maintenance Optimizer supports the download of a consistent queue that includes all
necessary Support Packages and enhancement packages In addition SAP Solution Manager
calculates a valid import queue for the selected SAP system and generates the enhancement
package stack configuration file that you require for the installation
As a prerequisite the system that you want to update needs to be maintained correctly in
SAP Solution Manager System Landscape As the Maintenance Optimizer uses this data for
the calculation it is crucial that the data is up-to-date In addition the SAP Solution Manager
system requires a Minimum Support Package level (see below)
Planing PhaseStep Description Documentation
Hardware amp Software Prerequisites
Check which platforms are supported for your target release (OSDB dependencies)
Product Availability Matrix (PAM) at httpservicesapcompam
Check which hardware sizing is required for your target release
Sizing information at httpservicesapcomsizing
Solution Manager Prerequisites
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of the required software packages you have to make sure that your SAP Solution Manager system has the required Support Package levelAt least SAP Solution Manager 70 EHP1 Support Package Stack 17 is required We recommend to use SAP Solution Manager 70 EHP1 Support Package Stack 23Check if you need to do an update or upgrade of your SAP Solution ManagerMake sure that you run the guided procedure SOLMAN_SETUP after every installation or update of SAP Solution Manager and that it completes successfully
For upgrades from source release SAP Solution Manager 31 and 32Upgrade Guide ndash SAP Solution Manager 70 incl Enhancement Package 1For updates from SAP Solution Manager 70Update Guide SAP Enhancement Package 1 for SAP Solution Manager 70Follow-up activities after an Support Package Stack update or enhancement package updateSolution Operations Guide ndash SAP Solution Manager 70 EHP1 section Software Change Management All guides are available at http
servicesapcom instguides SAP Components SAP Solution Manager -gt Release 70 EHP 1
Implementation PhaseStep Description Documentation
1Solution Manager Preparation
Configure the SAP Solution Manager Maintenance Optimizer
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of software packages make sure your
Configuration of Maintenance Optimizer http
helpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Change Request Management and Change ControlMaintenance Optimizer
Prerequisites
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 2956
Implementation PhaseStep Description Documentation
system landscape data in SAP Solution Manager is maintained correctlyLandscape Verification 10 which is an add-on to SAP Solution Manager can support you in maintaining your system landscape data The use of this tool is optional
Landscape Verification http
wwwsdnsapcom irj
sdn alm-update-
management link Landscape Verification under Related Areas on Upgrade and Update Management (in the right column)
SAP Note 1468605 (Installation of Landscape Verification)
Maintaining System Landscape Information [page 47]Note that the information provided in this section is based on SAP Solution Manager 70 EHP1 SP23
2System Preparation
Prepare your system as described in the documentation for example perform OS DB specific preparations and the PI-specific preparations
Update Guide ndash Update of SAP Systems with Software Update Manager sections Planning and Preparation
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
3Software Download
Select and download the software packages in either of the following ways Automatic calculation Create
a maintenance transaction in the Maintenance Optimizer and choose the Calculate Files Automatically option
Manual Selection Create a maintenance transaction in the Maintenance Optimizer and choose the Select Files Manually option You then can select the files manually using the SP Stack application in SAP Service Marketplace
NOTE
You have to download the stack configuration file manually after you have selected all files in the SP Stack
httphelpsapcom SAP Solutions SAP Solution Manager
SAP Solution Manager 70 EHP1 ltSPgtChange Request Management and
Change Control Maintenance Optimizer Maintenance Procedure Scenarios
For information about the automatic calculation see Maintenance Transaction with Installation of an Enhancement PackageFor information about the manual selection and approval process see section Approve and Download Files in Download Basket
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
3056 PUBLIC 2011-04-15
Implementation PhaseStep Description Documentation
application Choose Generate Stack XML and save the file
4Enhancement Package Installation
Run Software Update Manager to update your system with the selected software packages
Update Guide ndash Update of SAP Systems with Software Update Manager
5Follow-Up Steps
Perform technical and PI-specific follow-up activities after the enhancement package installation is done
Update Guide ndash Update of SAP Systems with Software Update Manager section Follow-Up Activities
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
6Configuration
Configure newly installed enhancement package functions using SAP Solution Manager content
See Systems with Usage Types [page 16] section Configuration of Systems with Usage Types
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 3156
This page is left blank for documents that are printed on both sides
5 System Landscape
51 Planning Your System Landscape
The installable software units that make up your system landscape depend on the functions that you
want to implement For information about the features see systems [page 16] standalone engines [page 19]
and clients [page 21]
In addition you have to determine the required shared services [page 35] (such as SAP Solution Manager
or SAP NetWeaver Administrator) that run on central systems in your system landscape and the
landscape aspects relevant for their implementation
In the following you will find general information that you should consider when planning your system
landscape
Sizing
You have to map systems and standalone engines to hosts after you have a clear picture of the following
Which systems and standalone engines you require
How many systems you require and how you want to use each of these systems
NOTE
No general guideline can be given for the sizing of your landscape since this relies heavily on your
requirements You should therefore perform this task together with your hardware partner and
your technical consultant
For information about sizing your systems you can use the following information sources
Your first point of reference is the Quick Sizer
SAP built the Quick Sizer as an online sizing questionnaire Internet application in close cooperation
with its hardware partners This tool delivers general sizing categories based on your volume load
estimates The results provide an objective basis for sizing independent of platform and
configuration
For more information see SAP Service Marketplace at
httpservicesapcomsizing for the SAP NetWeaver PI 71 sizing guide available under
Sizing Guidelines Business Suite amp Services
httpservicesapcomquicksizer for more information and access to the tool itself
Also consider the following important aspects concerning sizing
High availability
5 System Landscape
51 Planning Your System Landscape
2011-04-15 PUBLIC 3356
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Technical Infrastructure High Availability
Unicode
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Internationalization
Contact your hardware partner to find out the appropriate number of sized hosts
The platform-independent abstract results of the Quick Sizer can be used by any of our hardware
partners to create a concrete offer SAP itself does not make any hardware recommendations the
responsibility for sizing and detailed hardware configuration lies with the hardware partners
Figure 6 Example of Mapping of Systems and Standalone Engines to Three Hosts
NOTE
Optionally you could also distribute single systems to multiple hosts For example you could
decide to install the database instance of an SAP system on a separate host for performance
reasons or distribute other system instances to achieve high availability
To provide a mapping that fits your required functions and performance your hardware partner
and your technical consultant have to identify the number of required instances of SAP NetWeaver
find out how to distribute these instances to hosts and what functions will run on which instance
Therefore the hardware partner and the technical consultant have to consider many different
aspects such as
Number of required SAPS (SAP Application Benchmark Performance Standard) for each
system (provided by Quick Sizer)
Landscape-relevant aspects concerning security For more information see the SAP Security
Guide in the SAP Library [page 12] at Administratoracutes Guide Security Guide
Landscape-relevant aspects concerning scalability high availability operation and software
life-cycle management
5 System Landscape
51 Planning Your System Landscape
3456 PUBLIC 2011-04-15
For more information about relevant aspects for the mapping of systems to hosts see the document
Technical Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
Scaling and Distribution Options
You may need to design your system landscape for a large number of users SAP NetWeaver PI offers
you different means of scalability The following list provides you with some examples
You could install multiple systems of one type and use them for different purposes
You could scale every system by installing dialog instances or by distributing the database instance
For more information about distribution options on the instance level see the Technical
Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
For every SAP system you could additionally install Web Dispatcher For more information see
the SAP Library [page 12] at FunctionndashOriented View Application Server Infrastructure SAP Web
Dispatcher
You could further distribute certain standalone engines ndash for example Search and Classification
(TREX) is based on a flexible architecture that supports a distributed installation For more
information see the Technical Infrastructure Guide ndash SAP NetWeaver PI 71 available in SAP Service
Marketplace at httpservicesapcominstallNWPI71
52 Shared Services
You normally run shared services on central systems in your system landscape The following features
could be used for SAP NetWeaver Process Integration to realize shared services
SAP Solution Manager
Used to implement train test maintain monitor control change and manage incidents of your
SAP solution system landscape (open end-to-end application management)
As of SAP Solution Manager (70) 40 Support Package 15 SAP Solution Manager has become the
platform for SAPs end-to-end solution operations strategy Functions for complete application
management has been combined with administrative tools and has been merged in newly created
role based work centers
NOTE
Be aware that you require an SAP Solution Manager system to install or upgrade to SAP
NetWeaver 70 and higher An SAP Solution Manager system is required to generate the SAP
Solution Manager key needed during the installation or upgrade process Without this key
the installation or upgrade process cannot continue
For SAP NetWeaver Process Integration you require SAP Solution Manager 70
For more information see SAP Note 805390
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3556
Solution Manager Diagnostics
An integral part of SAP Solution Manager that is running as a Java application on the Java stack of
SAP Solution Manager 70 Solution Manager Diagnostics is used to analyze the root cause of
incidents in your landscape in an efficient and safe way Before Go-Live Solution Manager
Diagnostics has to be set up and made accessible remotely
SAP NetWeaver Administrator
SAP NetWeaver Administrator is the central administration component which is used for
monitoring and administering Java applications It is included in SAP NetWeaver systems with AS
Java
SAP NetWeaver Administrator exists in the following flavors
A local mode which runs out of the box and which focuses on administrating the underlying
SAP NetWeaver AS Java
NOTE
For a SAP NetWeaver PI 71 it has a special role which you need to activate using a
configuation wizard
A central mode which has to be configured before use and which deals with the system
landscape management
SAP has decided to merge the central mode of SAP NetWeaver Administrator into the new work
centers available as of SAP Solution Manager 70 SP 15 Thus it can be used in an administrative
context together with non-Java-based administration tools Although the central mode of SAP
NetWeaver Administrator will be still available for some time SAP will not develop this tool any
further SAP focuses on optimizing the administrative work centers of SAP Solution Manager
instead
The local mode of SAP NetWeaver Administrator stays untouched It is available for current and
future releases of SAP NetWeaver
SAP Central Process Scheduling by Redwood
SAP Central Process Scheduling application by Redwood enables central job scheduling and job
monitoring of current and old releases of AS ABAP systems (as of Basis Release 31) This application
is fully integrated in SAP NetWeaver Depending on the business needs SAP business applications
are the initial trigger for scheduled activities You can now manage jobs and job chains conveniently
using a graphical user interface
System Landscape Directory
The System Landscape Directory is the central directory of system landscape information relevant
for the management of your software life-cycle It contains a description of your system landscape
(that is software components that are currently installed) and a repository of software components
that can theoretically be installed in your landscape (such as the software components available
from SAP)
Adaptive Computing Controller
5 System Landscape
52 Shared Services
3656 PUBLIC 2011-04-15
The Adaptive Computing Controller enables users to control an adaptive computing landscape
from a single point through observation operation and dynamic resource distribution With
adaptive computing hardware software and system services are able to adapt to changing business
needs In the Adaptive Computing Controller the run-time data of logical and physical landscapes
can be monitored application services can be startedstoppedrelocated and hardware resources
can be assigned to application services The operation can also be mass executed and be planned as
tasks to be executed
For more information about the installation of the Adaptive Computing Controller tool see the
document Installation Guide ndash Adaptive Computing Controller in SAP NetWeaver 71 available on SAP Service
Marketplace at httpservicesapcominstallNWPI71
For more information about Adaptive Computing in general see httpsdnsapcomirj
sdnadaptive
521 Use Cases
You can use the applications and tools described above for use cases that are normally performed
centrally The following sections describe these use cases
5211 End-to-End Solution Operations
Running business applications through their complete life-cycle is a challenge Therefore SAP has
started the Run SAP methodology for implementing End-to-End Solution Operations Based on a set
of SAP standards a roadmap and a package for training and certification Run SAP helps customers to
facilitate End-to-End Solution Operations
You can download the SAP standards for Solution Operations from SAP Service Marketplace at http
servicesapcomsupportstandards They describe roles customers typically have in their IT
environment For optimal role support SAP has grouped existing and new functions in SAP Solution
Manager work centers as of SAP Solution Manager 70 Support Package 15 Operations aspects are fully
covered by adding administrative functions for SAP NetWeaver as well Work centers are ABAP Web
Dynpro-based applications They offer the following advantages
Easy to use similar look and feel
Context transfer while jumping from one work center into another
Logical grouping of tools for a certain area
Simple authorization concept
Easy to expand
Each IT role belongs to one or more work centers For instance the Technical Administrator IT role is
covered by the work centers for System Monitoring System Administration and Landscape Management
The following work centers are available
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3756
Business Process Operations
Change Management
Root Cause Analysis
Implementation Upgrade
Incident Management
Test Management
Job Management
System Landscape Management
Solution Documentation Assistant
SAP Engagement and Service Delivery
SAP Solution Manager Administration
System Administration
System Monitoring
My Home is the central point of access to all important data of almost all work centers in SAP Solution
Manager
5212 Support Infrastructure
A key requirement for effective support of IT solutions is the ability to perform root cause analysis with
speed and efficiency
With SAP Solution Manager SAP has long had an infrastructure in place for its ABAP applications that
efficiently supports SAP solutions This helps ensure the high availability and smooth running of
business processes For more information see the SAP Solution Manager section
With Solution Manager Diagnostics this knowledge has been extended to Java applications If for
example homegrown Java applications cause instability Solution Manager Diagnostics helps trace the
cause to eradicate the problem rapidly Solution Manager Diagnostics is fully integrated into SAP
Solution Manager 70 Solution Manager Diagnostics also contains two third-party tools CArsquos Wily
Introscopereg for measuring performance as well as troubleshooting problems of the Java EE Engine
and applications running on it and Mercury Loadrunnerreg which enables SAP Support to produce a
defined load in the SAP solution landscape remotely For more information see Solution Manager
Diagnostics [page 43]
The support infrastructure provides SAP Support with safe access to your productive landscape for safe
root cause analysis so ensuring that SAP Support does not change your landscape inadvertently You
require a support infrastructure to run SAP NetWeaver
The following figure shows the overall infrastructure including SAP NetWeaver administration tools
that are used by administrators or operators at the customer site
5 System Landscape
52 Shared Services
3856 PUBLIC 2011-04-15
Landscape Aspects
If you use SAP NetWeaver Process Integration 71 productively besides SAP Solution Manager (as a
central support platform) you have to set up Solution Manager Diagnostics for supportability reasons
Implementation Sequence
For information about the implementation of the support infrastructure see the document Master
Guide ndash SAP Solution Manager 70 available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution Manager ltReleasegt
5213 Collection of Landscape Data
Amongst other applications and services the support infrastructure and the SAP NetWeaver
administration tools rely on system landscape data
For SAP NetWeaver PI 71 you have to run non-ABAP components in your solution landscape
Therefore the System Landscape Directory is mandatory The landscape data that is automatically
gathered by the System Landscape Directory is replicated to SAP Solution Manager There are several
topology options for the System Landscape Directory They offer different grades of availability
administration and operation effort
For more information see the System Landscape Directory section
5214 Authentication and Single Sign-On
Before implementing your system landscape plan how to implement authentication and how to
integrate different systems into a Single Sign-On landscape Single Sign-On reduces complexity for end
users saving them valuable time while also reducing administration effort for resetting passwords
thereby contributing to TCO reduction
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
5215 Integrated User and Access Management
In a system landscape containing a combination of ABAP and Java components we recommend that
you integrate your user and access management so that you can use the same user data across different
systems administer this data centrally and control access to data SAPs mature fine-grained
authorization concept allows detailed control of access rights SAP NetWeaver provides both ABAP and
Java-based user management solutions The user management solution that you use to administer
your user data depends on factors such as the type of systems that are running in your landscape
If you want to use central user administration we recommend that you run it in a non-production
system If you do not have a central user administration yet you can for example realize it in the SAP
Solution Manager system
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3956
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
522 Examples for the Overall System Landscape of Shared Services
In this section we provide examples of how shared services can be set up depending on the system
landscape they are intended for The following examples aggregate the landscape aspects given in the
Use Cases section
NOTE
The following sections and the figure mostly do not show information about the life-cycle of
shared services For example you may also need a development and testquality assurance system
for SAP Solution Manager You should consider this aspect in addition to the information given
in this section based on your requirements
Small and MediumndashSized Customer Landscapes with Java
As you use Java productively for SAP NetWeaver PI 71 besides SAP Solution Manager you have to set
up additional components for optimal monitoring administration and support Solution Manager
Diagnostics and the central mode of SAP NetWeaver Administrator are already fully integrated into
SAP Solution Manager 70 as the central operations hub For SAP Process Integration you must also
set up SAP NetWeaver Administrator with a special role
We recommend that you do not install SAP Central Process Scheduling in the SAP Solution Manager
system You have to set up and operate the system which hosts your productive scheduler as a mission
critical system
In the SAP Solution Manager system you should set up a local System Landscape Directory in addition
to a central runtime System Landscape Directory This way you have a clear separation between your
management system (SAP Solution Manager) and managed systems in your landscape In addition
SAP Solution Manager then does not rely on a System Landscape Directory running in the production
environment For this setup configure the SLD data suppliers of your SAP Solution Manager system
to send data to the central runtime System Landscape Directory In addition configure automatic
bridge forwarding from your runtime System Landscape Directory to the local System Landscape
Directory For more information see the Planning Guide - System Landscape Directory
If you want to use a central system for Adobe Document Services we recommend that you install a
dedicated system for this purpose in your production environment For detailed information about
the sizing of the system for the different use cases see the Sizing Guide for Adobe Document Services at
SAP Service Marketplace at httpservicesapcomsizing Sizing Guidelines Solutions amp
Platform
We recommend that you start with this centralized SAP Solution Manager approach as depicted in the
following figure
5 System Landscape
52 Shared Services
4056 PUBLIC 2011-04-15
Figure 7 Single SAP Solution Manager Landscape
Large Customer Landscapes with Java
Large customers who have environments in their landscape that are large and distributed administered
by different groups or separated for security reasons can consider a distributed operations setup In
addition to the centralized setup described for small- and medium-sized customers above large
customers can put parts of the central management functions on extra hosts or systems for performance
or policy reasons You have the following options for a distributed setup
You may set up an extra system or client for Central User Administration (CUA)
The Change and Transport System (CTS) can run on an extra system However it is not
performance- or data-intensive
You may set up an extra system for central CCMS monitoring Depending on the customizing
and on the landscape size central CCMS may generate a lot of system load You can connect a
separate central CCMS to SAP Solution Manager for displaying alerts in the alert inbox of the System
Monitoring work center
You can use a separate SAP NetWeaver 70 system with usage type BI together with SAP Solution
Manager This may make sense with respect to the amount of landscape management data that is
stored for reporting purposes The amount of data strongly depends on the data granularity
storage time frame and landscape size
You can easily put Wily Introscope Enterprise Manager on an separate host
Other aspects described above for small- and medium-customers (such as the setup of the System
Landscape Directory) are also valid for large customers
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4156
523 Feature Details
This section provides further information about the features described above
5231 SAP Solution Manager
SAP provides you with SAP Solution Manager as the strategic application management platform and
to enable the collaboration between you and SAP You need to install at least one productive SAP
Solution Manager in your system landscape To ensure the availability of this application management
platform an SAP Solution Manager system is technically required to install or upgrade to SAP
NetWeaver 70 or higher If you are already using SAP Solution Manager you can also use it to manage
the solution you build with SAP NetWeaver In this case we highly recommend that you update SAP
Solution Manager to the latest version
As of SAP Solution Manager 70 SP15 you can use the newly created work centers
NOTE
During the SAP system installation or upgrade process you are prompted to enter the SAP
Solution Manager key An SAP Solution Manager system is required to generate this key Without
this key the installation or upgrade process cannot continue
You may generate all needed keys for your entire system landscape (development quality
assurance and production system) in one SAP Solution Manager system In case you plan to install
several solution landscapes (for example in different countries) one SAP Solution Manager
system is still sufficient
For more information see SAP Note 805390
It is possible to install multiple SAP Solution Managers If you do so they should host separate business
solutions
If you want to reduce the risk of unavailability you should not install SAP Solution Manager as a central
component Instead you can operate a 2-system-landscape with both a test and production
environment of SAP Solution Manager (especially if you are using time-critical functions like Support
Desk) If you also develop your own content a 3-system-landscape with a development test and
production environment is recommended
For more information about SAP Solution Manager see the following table
Topic Where to Find More Information
System infrastructure scenarios installation and configuration of SAP Solution Manager
Master Guide ndash SAP Solution Manager available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution ManagerltReleasegt
Benefits and usage scenarios SAP Solution Manager ndash Learning Maps available on SAP Service Marketplace at http
5 System Landscape
52 Shared Services
4256 PUBLIC 2011-04-15
Topic Where to Find More Informationservicesapcomrkt-solman or https
servicesapcomsolutionmanager
Additional information See SAP Service Marketplace at http
servicesapcomsolutionmanager
5232 Solution Manager Diagnostics
Solution Manager Diagnostics provides efficient and safe root-cause analysis of incidents in customer
solutions powered by SAP NetWeaver It can help monitor on operating systems databases Java
application activities performance and logs It also supports the reporting of software and
configuration changes that can lead to malfunctions and errors
You must run one Solution Manager Diagnostics within your SAP solution landscape if you run
applications based on SAP NetWeaver systems with usage type AS Java Agents are responsible for
delivering the data from all productive hosts within your system landscape to the Solution Manager
Diagnostics system
CAUTION
SAP Support performs root-cause analysis on incoming incidents with Solution Manager
Diagnostics Not installing and configuring this support infrastructure results in a dramatically
reduced service level
Solution Manager Diagnostics is fully integrated into SAP Solution Manager 70
Solution Manager Diagnostics also contains Wily Introscope (Display Server and Agent part) for
measuring performance as well as to troubleshoot problems of Non-ABAP applications Wily Introscope
is heavily used for troubleshooting applications running on AS Java
SAP has signed a distribution agreement for Wily Introscope SAP customers are allowed to use this
tool in a preconfigured way
For more information about Solution Manager Diagnostics and an FAQ list see SAP Service Marketplace
at httpservicesapcomdiagnostics
5233 System Landscape Directory
The System Landscape Directory (SLD) of SAP NetWeaver is the central directory of system landscape
information relevant for the management of your software life-cycle
NOTE
Note that the abbreviation SLD is not intended to define a product since the System Landscape
Directory is part of SAP NetWeaver This abbreviation is solely intended to improve readability
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4356
The System Landscape Directory contains a description of your system landscape (that is software
components that are currently installed) and a repository of software components that can
theoretically be installed in your landscape (such as the software components available from SAP)
Since this data gets updated automatically the System Landscape Directory provides reliable and up-
to-date system landscape information with as little effort for you as possible In this way the System
Landscape Directory acts as a central information provider for SAP and third-party tools that use this
data to deliver the services you need to keep your landscape up and running
For the System Landscape Directory as part of an SAP NetWeaver PI 71 landscape consider the following
aspects
Part of SAP NetWeaver PI 71 is a new version of the System Landscape Directory It is automatically
included in every SAP NetWeaver 71 system with usage type AS Java It offers enhanced functions
such as a full automatic synchronization mechanism for all data stored in it That is both data
delivered by data suppliers and data entered or changed manually in the System Landscape
Directory can be synchronized automatically This synchronization offers the following
A fully automated mechanism so no user interaction is required and conflicts are resolved
automatically
Asynchronous propagation of information so some nodes may be down temporarily
Communication over HTTP protocol
Uni- and bi-directional synchronization
Depending on your use case the full automatic synchronization could significantly reduce manual
synchronization effort
For SAP NetWeaver PI 71 the configuration of the system landscape directory and its data suppliers
is already included in the standard implementation procedure with SAPinst For existing systems
you only have to perform some quick and easy configuration actions to start operating the system
landscape directory server in an AS Java system
For SAP NetWeaver PI 71 you have the following options concerning SLD
Option 1
Run SAP NetWeaver PI 71 against an existing SLD running on SAP NetWeaver 70 We only
recommend this for upgrades from SAP NetWeaver 70 if you have a central SLD in operation
not running on one of your PI systems
Option 2
Use the SLD included in an SAP NetWeaver PI 71 system We recommend this option for new
installations and upgrades from older releases than SAP NetWeaver 70 due to the enhanced
functions and improved performance of SLD 71
NOTE
If you already have a central SLD running on SAP NetWeaver 70 in operation you could run
two SLD versions in parallel ndash SLD running on SAP NetWeaver 71 for your PI systems and
SLD running on SAP NetWeaver 70 for all other systemsuse cases This way your SAP
5 System Landscape
52 Shared Services
4456 PUBLIC 2011-04-15
NetWeaver PI 71 systems would benefit from the new features while it would be easy to set
up and operate such an SLD landscape For this purpose you could use the new fully
automatic synchronization This feature enables the automatic forwarding of all SLD data
from an SLD running on SAP NetWeaver 70 to an SLD running on SAP NetWeaver 71 As a
result there is no need to adapt most existing systems as their SLD data suppliers could still
send their data to the central SLD In brief the following steps would be required
1 Put SLD in a PI system into operation (part of standard implementation procedure)
2 Configure PI systems to use the new SLD (part of standard implementation procedure
for new PI systems)
3 Set up the fully automatic synchronization from your old SLD to your new SLD
As soon as an upgrade or an installation of a standalone AS Java 71 system is available you
could move your central SLD also to SAP NetWeaver 71 Then you could optionally shift
your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems
Figure 8
We recommend that you use a Domain Name System (DNS) alias so that you are able to switch to
another System Landscape Directory easily For example if customers build a new landscape they
normally start with a sandbox environment Over time more and more environments are set up
Once the production environment is in place move the System Landscape Directory there To do
this you can configure a new System Landscape Directory in the production environment
synchronize it with the old System Landscape directory and switch to the new one
Topology
Apart from the considerations above the System Landscape Directory offers several topology options
with different grades of availability at the expense of low administration and operation effort There is
no generic rule therefore on how to set up a System Landscape Directory in your system landscape
To find the topology and synchronization strategy for the System Landscape Directory that fits your
requirements concerning the System Landscape Directory availability (and hence the availability of
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4556
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
Table of Contents
Chapter 1 Introduction 9
Chapter 2 Before You Start 11
21 SAP Notes 11
22 More Information 11
23 Accessing the SAP Library 12
Chapter 3 SAP NetWeaver PI Overview 13
31 Installable Software Units 15
311 Systems with Usage Types 16
312 Standalone Engines 19
313 Clients 21
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration
71 23
Chapter 4 SOA-Based Integration Use Case 25
41 Overview 25
42 System Landscape 25
43 Implementation Sequence 27
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP
Netweaver PI 71 System 28
Chapter 5 System Landscape 33
51 Planning Your System Landscape 33
52 Shared Services 35
521 Use Cases 37
5211 End-to-End Solution Operations 37
5212 Support Infrastructure 38
5213 Collection of Landscape Data 39
5214 Authentication and Single Sign-On 39
5215 Integrated User and Access Management 39
522 Examples for the Overall System Landscape of Shared Services 40
656 PUBLIC 2011-04-15
523 Feature Details 42
5231 SAP Solution Manager 42
5232 Solution Manager Diagnostics 43
5233 System Landscape Directory 43
Chapter A Appendix 47
A1 Maintaining System Landscape Information 47
Chapter B Reference 51
B1 The Main SAP Documentation Types 51
B2 List of Documentation 51
2011-04-15 PUBLIC 756
This page is left blank for documents that are printed on both sides
1 Introduction
This Master Guide provides you with a central starting point for the technical implementation of SAP
NetWeaverreg Process Integration (SAP NetWeaver PI) It also contains information about enhancement
package 1 for SAP NetWeaver Process Integration 71
SAP NetWeaver PI 71 is based on an established architecture for realizing cross-system business processes
and supporting an service-oriented architecture (SOA) The focus is on the service-based integration
of applications
Structure of the Master Guide
The Master Guide consists of the following sections
Introduction
Contains an introduction to this guide
Before You Start
Contains information about this document important things which you need to know before you
start and information on how to access the SAP Library
SAP NetWeaver Overview
Describes the building blocks of SAP NetWeaver PI
SOA-Based Integration Use Case
Introduces the use case and explains how to install it
System Landscape
Contains information about how to install your system landscape
Reference
Contains information about the overall documentation concept for SAP systems
CAUTION
Make sure you have the latest version of the Master Guide by checking SAP Service Marketplace
immediately before starting the installation
The Master Guide is regularly updated on SAP Service Marketplace at http
servicesapcominstallnwpi71 Planning
Constraints
The business scenarios that are presented here serve as examples of how you can use SAP software in
your company The business scenarios are intended only as models and do not necessarily run the way
they are described here in your customer-specific system landscape Check your requirements and
systems to determine whether these scenarios can be used productively at your site Furthermore we
1 Introduction
2011-04-15 PUBLIC 956
recommend that you test these scenarios thoroughly in your test systems to ensure that they are
complete and free of errors before going live
1 Introduction
1056 PUBLIC 2011-04-15
2 Before You Start
21 SAP Notes
You must read the following SAP Notes before you use this Master Guide and implement SAP NetWeaver
Make sure that you have the up-to-date version of each SAP Note which you can find on SAP Service
Marketplace at httpservicesapcomnotes
NOTE
The SAP Notes related to SAP NetWeaver PI 71 are also listed on SAP Service Marketplace at
httpservicesapcomsapnotesnwpi71
List of Important SAP Notes
SAP Note Number Title Description
1004107 Release Restrictions for SAP NetWeaver PI 71
Some restrictions apply to the productive use of SAP NetWeaver PI 71 These are documented in this SAP Note
1247043 Release Restrictions for SAP EHP1 for SAP NetWeaver PI 71
Some restrictions apply to the productive use of enhancement package 1 for SAP NetWeaver PI 71 These are documented in this SAP Note
22 More Information
The following table contains links to information available on SAP Service Marketplace or in the SAP
Library which is important for implementing SAP NetWeaver
Content Location on SAP Service Marketplace or in SAP Library
The latest version of the installation and upgrade guides for SAP NetWeaver Process Integration
httpservicesapcominstguidesnwpi71
Information about supported platforms (operating systems databases browsers) for all SAP NetWeaver components
httpservicesapcomplatforms Product Availability Matrix
Sizing of SAP NetWeaver httpservicesapcomsizing
Information about security SAP Security Guide See the SAP Library [page 12] at Adminitstratoracutes Guide Security Guide
Information about the technical operation of SAP NetWeaver
Technical Operations Manual See the SAP Library [page 12] at Adminitstratoracutes Guide Technical Operations for SAP NetWeaver
2 Before You Start
21 SAP Notes
2011-04-15 PUBLIC 1156
Content Location on SAP Service Marketplace or in SAP Library
Information about SAP NetWeaver PI Support Package Stacks
httpservicesapcomnetweaver SAP NetWeaver PI 71- Release-Specific Information Support Package Stacks Information
Information about installing SAP NetWeaver Support Package Stacks
httpservicesapcomMaintenanceNWPI71
Support Package Stack Guide ndash SAP NetWeaver
23 Accessing the SAP Library
For more information about SAP NetWeaver Process Integration access the SAP Library from any of
the following
SAP Help Portal at httphelpsapcomNWPI71 SAP NetWeaver Process Integration 71 Library
ltLanguagegt SAP NetWeaver Process Integration Library
CAUTION
The SAP Help Portal contains the latest version of the SAP Library Therefore we recommend
that you use this channel to access the SAP Library
An SAP system if you have installed the online documentation Choose Help SAP Library
The browser starts
The help files on the online documentation CDs or DVDs
If you want to view the help files in HTMLHelp format from the online documentation CDs or
DVDs you need a PC running Microsoft Windows to install the HTMLHelp Viewer
2 Before You Start
23 Accessing the SAP Library
1256 PUBLIC 2011-04-15
3 SAP NetWeaver PI Overview
Introduction
SAP NetWeaver PI 71 is part of the SAP NetWeaver technology platform The complete offering of the
SAP NetWeaver technology platform is visualized in the SAP NetWeaver technology map which you
can access at httpsdnsapcomnetweaver SAP NetWeaver at a Glance The technology map
enables you to drill down from top-level technology areas (for example Lifecycle Management) to
individual capabilities (for example Administration Monitoring and so on)
SAP NetWeaver PI includes the following capabilities
Repository-based Modeling and Design
Service Bus-based Integration
SOA Management
A different view is introduced by the end-to-end use case concept This concept offers an
implementation view on SAP NetWeaver to structure and facilitate your implementation
A use cases is a process that typically involves several SAP NetWeaver capabilities It is not limited to a
single component or capability A use case guides you through the different phases of your
implementation project ndash from information through installation to the configuration phase This
implies that a uses case addresses several user roles administrator power user and end user
This document describes the SOA-based integration use case
Architecture Principals
The architecture of SAP NetWeaver Process Integration 71 (SAP NetWeaver PI 71) is based on an
established architecture for realizing cross-system business processes and is a further development of
lower releases (SAP NetWeaver 70 usage type Process Integration and SAP XI 30 as part of SAP
NetWeaver 2004) SAP NetWeaver PI 71 plays an important role in supporting an service-oriented
architecture (SOA) The focus is on the service-based integration of applications
SAP NetWeaver PI is based on general standards so as to enable 3rd-party systems to be integrated At
the center of SAP NetWeaver PI is an XML-based communication that uses HTTP (Hyper Text Transfer
Protocol) Irrespective of the scenario used the application-specific contents are transferred in messages
in user-defined XML (eXtensible Markup Language) from the sender to the receiver either via the
Integration Server or directly between the systems involved
The following figure gives an overview of the key capabilities of SAP NetWeaver Process Integration
3 SAP NetWeaver PI Overview
2011-04-15 PUBLIC 1356
Figure 1 SAP NetWeaver PI Key Capabilities Overview
SAP NetWeaver Process Integration 71 enables the integration of the applications of the following
communication parties
B2B Party Any business partners that want to integrate their application with other applications
outside their own system landscape Scenarios that require industry standards are supported as
well as any scenarios that do not adhere to a particular industry standard
SAP Applications that run on SAP systems This includes the processing of events by using the
Business Activity Monitoring (BAM) infrastructure
3rd-Party Application Applications from 3rd-party providers within one system landscape for
example database or file-system-based
3rd-Party Middleware Middleware systems from 3rd-party providers that are required for the
integration of applications within a company and across company boundaries
SAP NetWeaver PI also supports internal company scenarios and cross-company scenarios It enables
you to connect systems from different vendors (non-SAP and SAP) in different versions and
implemented in different programming languages (Java ABAP and so on) to each other Like the rest
of the SAP NetWeaver platform SAP NetWeaver PI is based on an open architecture uses open standards
(in particular those from the XML and Java environments) and offers those services that are essential
in a heterogeneous and complex system landscape
To enable end-to-end SOA development SAP NetWeaver Process Integration 71 offers a Universal
Description Discovery and Integration (UDDI) v3-based Services Registry where providers can publish
service endpoints definitions and associated metadata and consumers can discover the appropriate
services for their scenarios The Services Registry provides capabilities for classifying and browsing
3 SAP NetWeaver PI Overview
1456 PUBLIC 2011-04-15
services using semantic-rich classification systems The Services Registry is part of Application Server
Java (AS Java)
31 Installable Software Units
SAP NetWeaver comprises the following three types of installable software units
Systems that are configured for a specific purpose as indicated by one or more usage types
Standalone engines that provide one specific (server) function in combination with one or more
SAP NetWeaver PI systems
Clients used by (many) people from their local front-end PC to access functions offered by systems
of SAP NetWeaver PI or standalone engines in the system landscape
In the following sections you can find more details about the software units The figure below provides
and overview of the software units
Figure 2 Installable Software Units for SAP NetWeaver PI
For this and other figures in this guide the following legend applies
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1556
Figure 3 Legend
311 Systems with Usage Types
SAP systems are the main building blocks of SAP NetWeaver They are identified by unique SAP system
IDs (SAPSIDs) and configured for a certain purpose as indicated by usage types Usage types have the
following characteristics
They are a structuring element for SAP software on a technical level
Usage Types determine the intended purpose of a system and the role it plays in a given (distributed)
use case
They are realized by installing and configuring a collection of software components
They allow a logical view of the technology platform SAP NetWeaver PI
A usage type may require other usage types in the same system to operate
They can also be run in the same system together with other usage types that are not a prerequisite
How SAP NetWeaver Systems are Used
The following sections describe the usage types and their dependencies for SAP NetWeaver PI
Application Server ABAP (AS ABAP)
Purpose
AS ABAP is used to provide the ABAP foundation of SAP NetWeaver PI
Application Server ABAP provides a complete development and runtime environment for ABAP-based
applications It is optimized for the development of highly scalable business applications The ABAP
development and runtime environment makes it possible to develop complex business applications
3 SAP NetWeaver PI Overview
31 Installable Software Units
1656 PUBLIC 2011-04-15
without having to worry explicitly about technical details such as process or memory administration
multi-user capability database connections or similar issues These are provided in the basis services or
are integrated directly in the ABAP runtime The application development is similarly independent of
the underlying platform The application server decouples the application coding completely from the
operating system and database that are used
Dependencies
AS ABAP can be combined optionally with other usage types in one system
Application Server Java (AS Java)
Purpose
AS Java is used to provide the Java foundation of SAP NetWeaver PI using the Java Engine a Java EE-
compliant application server for running enterprise applications In addition to the pure Java EE
standard technologies the Java Engine implements complementary technologies such as Web Dynpro
or Web Services that are targeted at supporting large-scale real-business application development
projects
Dependencies
AS Java can be combined optionally with other usage types in one system
Process Integration (PI)
Purpose
PI consists of core components that model design automate and integrate processes in one or more
application systems For the integration of internal and cross-company processes PI is used to
incorporate all the functions of what was formerly known as Exchange Infrastructure (XI) In addition
PI contains core components for Business Process Management for application-embedded and
application-unbounded processes
The Advanced Adapter Engine is also part of usage type PI You use Advanced Adapter Engine to connect
to SAP systems (RFC adapter) and external systems You use the various adapters in Advanced Adapter
Engine to convert XML- and HTTP-based messages to the specific protocol and format required by
these systems and the other way around You can use the Advanced Adapter Engine that is part of
your PI system as a central Advanced Adapter Engine Optionally (for performance reasons) you can
install a non-central Advanced Adapter Engine [page 19] separately as a system with AS Java and parts of the
usage type PI on a separate host
Dependencies
PI requires AS ABAP and AS Java as prerequisites in the same system
For installing PI it is mandatory to have a dedicated PI system This applies to development quality
and production landscapes It is a prerequisite that no other system in your system landscape has a
higher release and enhancement package level than the PI system If you want to upgrade or install an
application in your system landscape you first have to make sure that the current release and
enhancement package level of the PI system is on the same level - if required you have to upgrade the
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1756
PI system first to the new or a higher release In a dedicated PI system this can be accomplished with a
minimum of downtime Also the PI system would not be affected by the downtime of other usage
types running in the same system
Configuration of Systems with Usage Types
Configuration information is available in the installation guides the configuration wizard and SAP
Solution Manager
In the Installation Guide ndash SAP NetWeaver PI 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt you find
initial technical configuration tasks This guide also informs you about how you can run the
configuration wizard and how you can access the configuration information in SAP Solution
Manager
For certain usage types configuration tasks can be applied by the configuration wizard after the
installation To do this you start the configuration wizard from SAP NetWeaver Administrator
The configuration steps for systems with usage types required for an use case are accessible through
SAP Solution Manager
To be able to use SAP Solution Manager for the configuration tasks you have to import the latest
SAP Solution Manager Implementation Content (Add-On ST-ICO) that is available for your SAP
Solution Manager release For more information see SAP Note 631042 (Release strategy for Implementation
Content (ST-ICO))
SAP Solution Manager Implementation Content is available on SAP Service Marketplace at
httpservicesapcomswdc Installations amp Upgrades Entry by Application Component SAP
Technology Components SAP Solution Manager ltReleasegt Content ST-ICO
In SAP Solution Manager you create a project and a project structure In the configuration phase
you select configuration structures with pre-delivered SAP content for your project You can find
the following different types of configuration tasks in SAP Solution Manager
Mandatory configuration tasks All configuration tasks that are mandatory for the standalone
engine or usage type
Optional configuration tasks Configuration tasks for areas where customers need to decide
if they want to use these functions (for example high availability or security settings)
Additional functions ndash configuration tasks Configuration tasks for functional units that are
used in certain use cases only
A marked checkbox in front of the configuration tasks indicates those configuration tasks that are
relevant for the use case you have chosen To configure ABAP systems SAP Solution Manager
offers executable configuration files (IMG activities)
For information about using SAP Solution Manager Content and creating a configuration guide
see the following documentation
httphelpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Implementing
and Upgrading SAP Solutions Configuration
3 SAP NetWeaver PI Overview
31 Installable Software Units
1856 PUBLIC 2011-04-15
How to Create a Configuration Guide using SAP Solution Manager available at http
servicesapcomsolutionmanager Media Library How-To Documents
Restrictions for Systems with Multiple Usage Types
If you have one system with multiple usage types be aware that we do not provide standard tools
to separate these usage types and distribute them to multiple systems at a later stage For example
if you have a system with usage types A and B you are not able to migrate it with SAP standard
tools into two systems one with usage type A only and the other with usage type B only
In addition we do not provide standard tools to merge multiple systems with different usage types
into one system with multiple usage types at a later stage
If you want to perform these tasks you require specific project support
The following figure shows that SAP standard system copy and migration tools do not support
you in separating or merging systems with usage types
Figure 4 No Support for Merging or Separating Systems with Usage Types
Although you can use one system for multiple usage types client restrictions apply for usage type
PI PI requires a dedicated client due to special PI requirements concerning the client pipeline
Whereas application client pipelines only send and receive messages the central PI pipeline can
also map messages to different formats before sending them
312 Standalone Engines
Standalone engines of SAP NetWeaver are additional installable software units They do not work as
full-blown systems of SAP NetWeaver but as standalone engines that provide a specific (server) function
in combination with one or more SAP NetWeaver systems
Standalone engines are not part of a usage type They do not run on AS ABAP or AS Java
The standalone engines that are available for SAP NetWeaver Process Integration are described in the
following
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1956
Gateway
It is possible to install an SAP instance of an SAP NetWeaver system based exclusively on a standalone
gateway This type of instance does not contain normal work process types (dialog background update
enqueue or spool) Only the gateway process (gwrd) is started If there is an SNA connection to an R
2 system gateway work processes (gwwp) are also started
SAP Conversion Agent by Informatica
SAP Conversion Agent by Informatica is a data conversion tool that enables you to create interfaces
between any data formats and XML-based systems SAP Conversion Agent can convert unstructured
semi-structured and structured formats to XML and the other way around The Conversion Agent
comprises the Conversion Agent Studio and the Conversion Agent Engine In the Conversion Agent
Studio you can develop and configure data conversions The Conversion Agent Engine executes the
data conversions
Search and Classification (TREX)
You can use Search and Classification with SAP NetWeaver PI to search for messages that were previously
indexed Message search using index provides additional methods of searching for specific messages In
addition to static header attributes you can also use adapter-specific message attributes and data from
the message payload for the search A requirement of this however is that the messages are indexed
first You can apply the index-based message search to one or all indexed components of an integration
landscape (domain) Integration Server Adapter Engines and ABAP business systems
For more information see the SAP Library [page 12] at Administratorrsquos Guide Technical Operations for SAP
NetWeaver Administration of SAP NetWeaver Systems Administering PI (Process Integration) Monitoring Index
Administration
Web Dispatcher
The Web Dispatcher lies between the Internet and your SAP system It is the entry point for HTTP(s)
requests into your system which consists of one or more SAP NetWeaver application servers As a
software web switch the Web dispatcher can reject connections or accept them When it accepts a
connection it balances the load to ensure an even distribution across the servers
You can use the Web dispatcher in ABAPJava systems and in pure Java systems as well as in pure ABAP
systems
It is also beneficial to use the Web Dispatcher if you do not need security functions (entry point in the
demilitarized zone (DMZ) SSL URL filtering) but you simply want to balance the load between
multiple SAP NetWeaver Application Server instances
Since Web Dispatcher is optional for every SAP system it is not contained in the system landscape and
the implementation sequence of the use case in this documentation
For more information see the SAP Library [page 12] at Function Oriented View Application Server Infrastructure
SAP Web Dispatcher
3 SAP NetWeaver PI Overview
31 Installable Software Units
2056 PUBLIC 2011-04-15
Advanced Adapter Engine
You use the Advanced Adapter Engine to connect to SAP systems (RFC adapter) and external systems
You use the various adapters in Advanced Adapter Engine to convert XML- and HTTP-based messages
to the specific protocol and format required by these systems and the other way around For specific
senderreceiver combinations messages can be processed without invoking the central Integration
Engine In principle you connect external systems using the adapters that are installed centrally or
non-centrally in Advanced Adapter Engine You can use the Advanced Adapter Engine that is part of
your PI system as a central Advanced Adapter Engine Optionally (for performance reasons) you can
install a non-central Advanced Adapter Engine separately as a system with AS Java and parts of the
usage type PI on a separate host
Adapter Engine (Java SE)
Adapter Engine (Java SE) is a separate software unit You can use it only if you have SAP NetWeaver
systems with usage type PI in your system landscape It has to be installed manually You use the Adapter
Engine (Java SE) to connect to external systems Using the various adapters in the Adapter Engine (Java
SE) XML and HTTP-based messages can be converted to the specific protocol and format required by
such systems and the other way around The Adapter Engine (Java SE) only provides some of these
adapters as a standalone version with restricted functions for operating systems that do not support
SAP NetWeaver PI 71 but that have at least a Java Runtime Environment 50 Therefore you should
use the Adapter Engine (Java SE) only if the platform prerequisites do not allow you to use the Advanced
Adapter Engine
SAP Partner Connectivity Kit
SAP Partner Connectivity Kit (PCK) runs on AS Java with parts of the usage type PI It enables a system
of a smaller company or subsidiary that does not run SAP NetWeaver PI to connect to your SAP
NetWeaver systems
313 Clients
Clients are additional installable programs or tools They reside either on local front-end PCs accessed
by users or on back-end systems where they act as client programs within an SAP NetWeaver system
landscape
The clients that you can use with SAP NetWeaver Process Integration are described in the following
sections
SAP GUI
NOTE
We recommend that you use the following versionsI
SAP GUI for Windows 710 (or higher) with the latest patch level
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 2156
SAP GUI for Java 710 (or higher) with the latest revision
The integrated SAP ITS 710
For more information about the SAP GUI family see SAP Service Marketplace at http
servicesapcomsapgui
SAP offers three different client applications for accessing ABAP applications in SAP systems (such as
SAP NetWeaver systems with usage type AS ABAP) This SAP GUI family consists of
SAP GUI for HTML
SAP GUI for HTML is based on the SAP integrated Internet Transaction Server (ITS) which is
included in the installation of SAP NetWeaver systems as of SAP NetWeaver 2004 On the client
side only a suitable browser (such as Internet Explorer 70 or Firefox 20) and a virtual machine are
required SAP ITS 620 is not compatible with SAP NetWeaver 71
SAP GUI for the Java environment (SAP GUI for Java)
SAP GUI for Java is a generic SAP GUI that covers a variety of platforms
For more information about the installation of SAP GUI for Java see the documentation Installation
Guide ndash SAP Front End
SAP GUI for the Windows environment (SAP GUI for Windows)
SAP GUI for Windows is SAPs universal client for accessing all SAP applications built on ABAP
technology It is available on the Microsoft Windows platform only and offers the broadest feature
set of all members of the SAP GUI family
For more information about the installation of SAP GUI for Windows see the Installation Guide ndash
SAP Front End
SAP NetWeaver Developer Studio
The SAP NetWeaver Developer Studio is SAPrsquos Integrated Development Environment (IDE) for Java
and is based on the open-source tools framework Eclipse 33 With the SAP NetWeaver Developer Studio
you can develop Java EE 5 applications from scratch using the built-in support for new technologies
such as EJB 30 and JSF 12
During the installation of the SAP NetWeaver Developer Studio several features are offered for
installation For SAP NetWeaver PI 71 only the following features are relevant
SAP NetWeaver Developer Studio Platform
SAP NetWeaver Developer Studio Java EE
NOTE
If you want to use one of the other features you need SAP NetWeaver Composition Environment
and a corresponding developers licence
For more information about the installation of SAP NetWeaver Developer Studio see the Installation
Guide ndash SAP NetWeaver Developer Studio 71 or Installation Guide ndash SAP NetWeaver Developer Studio 71 Including
Enhancement Package 1
3 SAP NetWeaver PI Overview
31 Installable Software Units
2256 PUBLIC 2011-04-15
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
SAP enhancement packages are a new way of delivering new functions for SAP NetWeaver This allows
a clear separation between the delivery of new functions on the one hand and corrections legal changes
and security updates on the other hand (in Support Package stacks) SAP enhancement packages are
cumulative an enhancement package always contains the functions of the corresponding predecessor
enhancement packages
Enhancement packages are maintained by their own Support Packages while the main release is in
maintenance
Benefits
SAP enhancement packages offer the following benefits
You have reduced effort for testing and no effort for training when applying Support Packages as
new features are only shipped with enhancement packages
Adding new functions between releases becomes predictable and controllable
New functions can be added successively in small steps There is no need to fully upgrade your
system to get new functions
You have minimal training effort when applying an enhancement package because existing
functions are not replaced
Implementation
There are the following ways to get an SAP NetWeaver system with the release level of SAP enhancement
package 1 for SAP NetWeaver Process Integration 71
New installation of SAP NetWeaver PI 71 including enhancement package 1 using the standard
installation tool SAPinst
Upgrade of an existing SAP NetWeaver system from a release lower than SAP NetWeaver PI 71 to
SAP NetWeaver PI 71 including enhancement package 1 For this you use the upgrade programs
SAPup (for ABAP) and SAPJup (for Java)
Installation of the enhancement package on an existing SAP NetWeaver PI 71 system
For this you use the Software Update Manager (SUM) The Software Update Manager evolved
from the previously used SAP Enhancement Package Installer The tool has been renamed to reflect
its broader use for example you can also use it for applying Support Package Stacks to your system
On the ABAP side the Software Update Manager uses a system cloning and switch procedure for
installing enhancement packages It installs a copy of the system the shadow system parallel to
the original system This shadow system is used to update the relevant software components and
to install the additional components while the original system is still in production operation At
a certain point during downtime the switch to the new system is made and afterwards any parts
of the original system that are no longer needed are deleted The enhancement package installation
in a Java system uses a deploy-based procedure that is no shadow system is used The Software
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2011-04-15 PUBLIC 2356
Update Manager requires a stack configuration file (xml file) as input file for the enhancement
package installation procedure This file lists all the packages that are to be installed in your systems
The stack configuration file is generated when you download the required packages
As the Software Update Manager is updated regularly we recommend to always use the latest
version It is delivered as part of the SL toolset For more information see http
servicesapcomsltoolset
For an overview of all required steps for the enhancement package installation process and
corresponding documents see Process Overview Installation of Enhancement Package 1 on an Existing SAP
Netweaver PI 71 System [page 28]
Content of SAP Enhancement Package 1 for SAP NetWeaver PI 71
With enhancement package 1 for SAP NetWeaver PI 71 new features are introduced and some existing
are changed The following is a selection of some of the most important enhancements
Enhanced design and modelling options in the Enterprise Services Repository
New services registry
Support for new Web services standard (Web Services Reliable Messaging)
New modules for the Advanced Adapter Engine
Use of shared memory of the ABAP Application Server for message processing
For more information about the changes see SAP Library [page 12] at Whatacutes new in SAP NetWeaver PI 71
ndash Release Notes
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2456 PUBLIC 2011-04-15
4 SOA-Based Integration Use Case
41 Overview
You can use SOA-based integration to set up the communication between service providers and service
consumers in both application-to-application and business-to-business scenarios and to execute
operate and monitor the communication at runtime SOA-based integration covers both direct (point-
to-point) as well as mediated (via an Integration Server) communication between service providers and
service consumers
The use case spans the whole life cycle of a SOA-based integration scenario including
Scenario modeling and service design in the Enterprise Services Repository
Implementation of the service provider and consumer in the back-end systems
Configuration and finally execution monitoring and operation of the integration scenario
For scenarios using Integration Server or broker-based communication the configuration of the
different connectivity options (for example SOAP RFC Web Services Industry standards and JDBC)
and their enhancements is covered
For more information see the following documents
Service-Enabling with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdnsoa-modeling
Getting Started
Service-Enabling a Legacy Application with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdn
soa-servicebus Getting Started
In the following you will find information about the installation of the involved software units
42 System Landscape
The following figure shows the system landscape for this use case
4 SOA-Based Integration Use Case
41 Overview
2011-04-15 PUBLIC 2556
Figure 5 SOA-Based Integration
It is mandatory to have a dedicated PI system This applies to development quality and production
landscapes
For PI it is a prerequisite that no other system in your system landscape has a higher release than
the PI system For exceptions to this rule see SAP Note 1043047 For example SAP XI 30 is compatible
with SAP NetWeaver 640 and 70 application systems since the same XI protocol is used Apart
from these exceptions if you want to upgrade or install an application in your system landscape
you first have to make sure that the PI system is on the same release level If required you have to
upgrade the PI system first to the new or a higher release
CAUTION
Although it should be technically possible to run an application system with a higher release
than your PI system in your system landscape this is not supported by SAP (apart from the
exceptions listed in SAP Note 1043047) Therefore you run such a landscape at your own risk
You can use the Advanced Adapter Engine that is part of your PI system as a central Advanced
Adapter Engine
Adapter Engine (Java SE) can be installed in a non-SAP Java environment However it only hosts
a subset of the adapter functionality is only supported for compatibility reasons and should be
used only if this is a precondition in your environment
Optionally you can use the Change Management Service (CMS) of an SAP NetWeaver 70 system
with usage type DI to transport design objects and repository objects For more information see
the SAP Library [page 12] at Administratoracutes Guide Technical Operations for SAP NetWeaver Administration
of SAP NetWeaver Systems PI (Process Integration) Software Logistics Transporting ESR Content and Objects
of Integration Directory PI Transports Using the Change Management Service (CMS)
Smaller business partners or subsidiaries that do not run SAP NetWeaver install SAP Partner
Connectivity Kit in their system landscape SAP Partner Connectivity Kit enables XML document
4 SOA-Based Integration Use Case
42 System Landscape
2656 PUBLIC 2011-04-15
exchange between your SAP NetWeaver systems and the partner systems Since SAP Partner
Connectivity Kit gets installed in their system landscape it is not shown in the system landscape
figure above
The AS ABAP system acts as an application and service provider For Java Web Services you also
require AS Java In addition you require SAP NetWeaver Developer Studio on the client side as a
development environment
The Web service client can be either an SAP or a non-SAP application For example an AS ABAP
system or a Web browser could act as application or service consumer
You can install SAP Conversion Agent by Informatica in the system with usage type PI or on a host
where SAP Partner Connectivity Kit is installed or on a host where neither usage type PI nor SAP
Partner Connectivity Kit is installed
43 Implementation Sequence
Procedure
To install this use case perform the steps listed in the following table
StepAction[Corresponding Documentation] Remarks
1 Make sure that you have performed the preparation steps You have planned your system landscape [page 33]
(that is you have decided how many systems you require how you want to use each of these systems and which standalone engines and clients you require)
With the help of your hardware partner you have mapped your systems and standalone engines to properly sized hosts
You have planned and installed shared services [page 35]
2 Installation of system with usage type PI (includes the installation of AS ABAP and AS Java)
NOTE
For usage type PI a Unicode installation is mandatory
[Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt]
If you want to use the features of enhancement package 1 use the direct installation of SAP NetWeaver PI 71 including enhancement package 1
Make sure that you perform the configuration steps as described in the installation guide For certain usage types configuration tasks can be applied by the configuration wizard These configuration tasks as well as any additional configuration steps for your use case are listed in SAP Solution Manager For more information
4 SOA-Based Integration Use Case
43 Implementation Sequence
2011-04-15 PUBLIC 2756
StepAction[Corresponding Documentation] Remarks
see the Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt
3 Install the Adapter Engine (Java SE) engines if required[Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
4 To integrate small business partners and subsidiaries the business partners or subsidiaries install SAP Partner Connectivity Kit running on AS Java with parts of usage type PI in the business partners or subsidiarys system landscape[Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
5 Install SAP Conversion Agent by Informatica if required[SAP Library [page 12] at Function-Oriented View Process Integration SAP Conversion Agent by Informatica Deploying and Using Conversion Agent ]
6 Installation of clients SAP GUI
[Installation Guide ndash SAP Front End]
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
The process sequences give a comprehensive overview of the steps relevant for the enhancement
package installation on an existing SAP NetWeaver PI 71 system
The process sequence is divided into a planning phase and an implementation phase Each step in both
phases contains references to the corresponding documentation to ensure that you can easily find the
information you need
Process
NOTE
To download the enhancement package files and required Support Packages you require the SAP
Solution Manager Maintenance Optimizer You have the following options
Manual Selection
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2856 PUBLIC 2011-04-15
You manually select the required files from SAP Service Marketplace at http
servicesapcomswdc using the SP Stack Application You use the Maintenance Optimize
only to approve the packages which is a prerequisite for the download
Automatic Calculation
The Maintenance Optimizer supports the download of a consistent queue that includes all
necessary Support Packages and enhancement packages In addition SAP Solution Manager
calculates a valid import queue for the selected SAP system and generates the enhancement
package stack configuration file that you require for the installation
As a prerequisite the system that you want to update needs to be maintained correctly in
SAP Solution Manager System Landscape As the Maintenance Optimizer uses this data for
the calculation it is crucial that the data is up-to-date In addition the SAP Solution Manager
system requires a Minimum Support Package level (see below)
Planing PhaseStep Description Documentation
Hardware amp Software Prerequisites
Check which platforms are supported for your target release (OSDB dependencies)
Product Availability Matrix (PAM) at httpservicesapcompam
Check which hardware sizing is required for your target release
Sizing information at httpservicesapcomsizing
Solution Manager Prerequisites
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of the required software packages you have to make sure that your SAP Solution Manager system has the required Support Package levelAt least SAP Solution Manager 70 EHP1 Support Package Stack 17 is required We recommend to use SAP Solution Manager 70 EHP1 Support Package Stack 23Check if you need to do an update or upgrade of your SAP Solution ManagerMake sure that you run the guided procedure SOLMAN_SETUP after every installation or update of SAP Solution Manager and that it completes successfully
For upgrades from source release SAP Solution Manager 31 and 32Upgrade Guide ndash SAP Solution Manager 70 incl Enhancement Package 1For updates from SAP Solution Manager 70Update Guide SAP Enhancement Package 1 for SAP Solution Manager 70Follow-up activities after an Support Package Stack update or enhancement package updateSolution Operations Guide ndash SAP Solution Manager 70 EHP1 section Software Change Management All guides are available at http
servicesapcom instguides SAP Components SAP Solution Manager -gt Release 70 EHP 1
Implementation PhaseStep Description Documentation
1Solution Manager Preparation
Configure the SAP Solution Manager Maintenance Optimizer
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of software packages make sure your
Configuration of Maintenance Optimizer http
helpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Change Request Management and Change ControlMaintenance Optimizer
Prerequisites
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 2956
Implementation PhaseStep Description Documentation
system landscape data in SAP Solution Manager is maintained correctlyLandscape Verification 10 which is an add-on to SAP Solution Manager can support you in maintaining your system landscape data The use of this tool is optional
Landscape Verification http
wwwsdnsapcom irj
sdn alm-update-
management link Landscape Verification under Related Areas on Upgrade and Update Management (in the right column)
SAP Note 1468605 (Installation of Landscape Verification)
Maintaining System Landscape Information [page 47]Note that the information provided in this section is based on SAP Solution Manager 70 EHP1 SP23
2System Preparation
Prepare your system as described in the documentation for example perform OS DB specific preparations and the PI-specific preparations
Update Guide ndash Update of SAP Systems with Software Update Manager sections Planning and Preparation
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
3Software Download
Select and download the software packages in either of the following ways Automatic calculation Create
a maintenance transaction in the Maintenance Optimizer and choose the Calculate Files Automatically option
Manual Selection Create a maintenance transaction in the Maintenance Optimizer and choose the Select Files Manually option You then can select the files manually using the SP Stack application in SAP Service Marketplace
NOTE
You have to download the stack configuration file manually after you have selected all files in the SP Stack
httphelpsapcom SAP Solutions SAP Solution Manager
SAP Solution Manager 70 EHP1 ltSPgtChange Request Management and
Change Control Maintenance Optimizer Maintenance Procedure Scenarios
For information about the automatic calculation see Maintenance Transaction with Installation of an Enhancement PackageFor information about the manual selection and approval process see section Approve and Download Files in Download Basket
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
3056 PUBLIC 2011-04-15
Implementation PhaseStep Description Documentation
application Choose Generate Stack XML and save the file
4Enhancement Package Installation
Run Software Update Manager to update your system with the selected software packages
Update Guide ndash Update of SAP Systems with Software Update Manager
5Follow-Up Steps
Perform technical and PI-specific follow-up activities after the enhancement package installation is done
Update Guide ndash Update of SAP Systems with Software Update Manager section Follow-Up Activities
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
6Configuration
Configure newly installed enhancement package functions using SAP Solution Manager content
See Systems with Usage Types [page 16] section Configuration of Systems with Usage Types
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 3156
This page is left blank for documents that are printed on both sides
5 System Landscape
51 Planning Your System Landscape
The installable software units that make up your system landscape depend on the functions that you
want to implement For information about the features see systems [page 16] standalone engines [page 19]
and clients [page 21]
In addition you have to determine the required shared services [page 35] (such as SAP Solution Manager
or SAP NetWeaver Administrator) that run on central systems in your system landscape and the
landscape aspects relevant for their implementation
In the following you will find general information that you should consider when planning your system
landscape
Sizing
You have to map systems and standalone engines to hosts after you have a clear picture of the following
Which systems and standalone engines you require
How many systems you require and how you want to use each of these systems
NOTE
No general guideline can be given for the sizing of your landscape since this relies heavily on your
requirements You should therefore perform this task together with your hardware partner and
your technical consultant
For information about sizing your systems you can use the following information sources
Your first point of reference is the Quick Sizer
SAP built the Quick Sizer as an online sizing questionnaire Internet application in close cooperation
with its hardware partners This tool delivers general sizing categories based on your volume load
estimates The results provide an objective basis for sizing independent of platform and
configuration
For more information see SAP Service Marketplace at
httpservicesapcomsizing for the SAP NetWeaver PI 71 sizing guide available under
Sizing Guidelines Business Suite amp Services
httpservicesapcomquicksizer for more information and access to the tool itself
Also consider the following important aspects concerning sizing
High availability
5 System Landscape
51 Planning Your System Landscape
2011-04-15 PUBLIC 3356
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Technical Infrastructure High Availability
Unicode
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Internationalization
Contact your hardware partner to find out the appropriate number of sized hosts
The platform-independent abstract results of the Quick Sizer can be used by any of our hardware
partners to create a concrete offer SAP itself does not make any hardware recommendations the
responsibility for sizing and detailed hardware configuration lies with the hardware partners
Figure 6 Example of Mapping of Systems and Standalone Engines to Three Hosts
NOTE
Optionally you could also distribute single systems to multiple hosts For example you could
decide to install the database instance of an SAP system on a separate host for performance
reasons or distribute other system instances to achieve high availability
To provide a mapping that fits your required functions and performance your hardware partner
and your technical consultant have to identify the number of required instances of SAP NetWeaver
find out how to distribute these instances to hosts and what functions will run on which instance
Therefore the hardware partner and the technical consultant have to consider many different
aspects such as
Number of required SAPS (SAP Application Benchmark Performance Standard) for each
system (provided by Quick Sizer)
Landscape-relevant aspects concerning security For more information see the SAP Security
Guide in the SAP Library [page 12] at Administratoracutes Guide Security Guide
Landscape-relevant aspects concerning scalability high availability operation and software
life-cycle management
5 System Landscape
51 Planning Your System Landscape
3456 PUBLIC 2011-04-15
For more information about relevant aspects for the mapping of systems to hosts see the document
Technical Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
Scaling and Distribution Options
You may need to design your system landscape for a large number of users SAP NetWeaver PI offers
you different means of scalability The following list provides you with some examples
You could install multiple systems of one type and use them for different purposes
You could scale every system by installing dialog instances or by distributing the database instance
For more information about distribution options on the instance level see the Technical
Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
For every SAP system you could additionally install Web Dispatcher For more information see
the SAP Library [page 12] at FunctionndashOriented View Application Server Infrastructure SAP Web
Dispatcher
You could further distribute certain standalone engines ndash for example Search and Classification
(TREX) is based on a flexible architecture that supports a distributed installation For more
information see the Technical Infrastructure Guide ndash SAP NetWeaver PI 71 available in SAP Service
Marketplace at httpservicesapcominstallNWPI71
52 Shared Services
You normally run shared services on central systems in your system landscape The following features
could be used for SAP NetWeaver Process Integration to realize shared services
SAP Solution Manager
Used to implement train test maintain monitor control change and manage incidents of your
SAP solution system landscape (open end-to-end application management)
As of SAP Solution Manager (70) 40 Support Package 15 SAP Solution Manager has become the
platform for SAPs end-to-end solution operations strategy Functions for complete application
management has been combined with administrative tools and has been merged in newly created
role based work centers
NOTE
Be aware that you require an SAP Solution Manager system to install or upgrade to SAP
NetWeaver 70 and higher An SAP Solution Manager system is required to generate the SAP
Solution Manager key needed during the installation or upgrade process Without this key
the installation or upgrade process cannot continue
For SAP NetWeaver Process Integration you require SAP Solution Manager 70
For more information see SAP Note 805390
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3556
Solution Manager Diagnostics
An integral part of SAP Solution Manager that is running as a Java application on the Java stack of
SAP Solution Manager 70 Solution Manager Diagnostics is used to analyze the root cause of
incidents in your landscape in an efficient and safe way Before Go-Live Solution Manager
Diagnostics has to be set up and made accessible remotely
SAP NetWeaver Administrator
SAP NetWeaver Administrator is the central administration component which is used for
monitoring and administering Java applications It is included in SAP NetWeaver systems with AS
Java
SAP NetWeaver Administrator exists in the following flavors
A local mode which runs out of the box and which focuses on administrating the underlying
SAP NetWeaver AS Java
NOTE
For a SAP NetWeaver PI 71 it has a special role which you need to activate using a
configuation wizard
A central mode which has to be configured before use and which deals with the system
landscape management
SAP has decided to merge the central mode of SAP NetWeaver Administrator into the new work
centers available as of SAP Solution Manager 70 SP 15 Thus it can be used in an administrative
context together with non-Java-based administration tools Although the central mode of SAP
NetWeaver Administrator will be still available for some time SAP will not develop this tool any
further SAP focuses on optimizing the administrative work centers of SAP Solution Manager
instead
The local mode of SAP NetWeaver Administrator stays untouched It is available for current and
future releases of SAP NetWeaver
SAP Central Process Scheduling by Redwood
SAP Central Process Scheduling application by Redwood enables central job scheduling and job
monitoring of current and old releases of AS ABAP systems (as of Basis Release 31) This application
is fully integrated in SAP NetWeaver Depending on the business needs SAP business applications
are the initial trigger for scheduled activities You can now manage jobs and job chains conveniently
using a graphical user interface
System Landscape Directory
The System Landscape Directory is the central directory of system landscape information relevant
for the management of your software life-cycle It contains a description of your system landscape
(that is software components that are currently installed) and a repository of software components
that can theoretically be installed in your landscape (such as the software components available
from SAP)
Adaptive Computing Controller
5 System Landscape
52 Shared Services
3656 PUBLIC 2011-04-15
The Adaptive Computing Controller enables users to control an adaptive computing landscape
from a single point through observation operation and dynamic resource distribution With
adaptive computing hardware software and system services are able to adapt to changing business
needs In the Adaptive Computing Controller the run-time data of logical and physical landscapes
can be monitored application services can be startedstoppedrelocated and hardware resources
can be assigned to application services The operation can also be mass executed and be planned as
tasks to be executed
For more information about the installation of the Adaptive Computing Controller tool see the
document Installation Guide ndash Adaptive Computing Controller in SAP NetWeaver 71 available on SAP Service
Marketplace at httpservicesapcominstallNWPI71
For more information about Adaptive Computing in general see httpsdnsapcomirj
sdnadaptive
521 Use Cases
You can use the applications and tools described above for use cases that are normally performed
centrally The following sections describe these use cases
5211 End-to-End Solution Operations
Running business applications through their complete life-cycle is a challenge Therefore SAP has
started the Run SAP methodology for implementing End-to-End Solution Operations Based on a set
of SAP standards a roadmap and a package for training and certification Run SAP helps customers to
facilitate End-to-End Solution Operations
You can download the SAP standards for Solution Operations from SAP Service Marketplace at http
servicesapcomsupportstandards They describe roles customers typically have in their IT
environment For optimal role support SAP has grouped existing and new functions in SAP Solution
Manager work centers as of SAP Solution Manager 70 Support Package 15 Operations aspects are fully
covered by adding administrative functions for SAP NetWeaver as well Work centers are ABAP Web
Dynpro-based applications They offer the following advantages
Easy to use similar look and feel
Context transfer while jumping from one work center into another
Logical grouping of tools for a certain area
Simple authorization concept
Easy to expand
Each IT role belongs to one or more work centers For instance the Technical Administrator IT role is
covered by the work centers for System Monitoring System Administration and Landscape Management
The following work centers are available
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3756
Business Process Operations
Change Management
Root Cause Analysis
Implementation Upgrade
Incident Management
Test Management
Job Management
System Landscape Management
Solution Documentation Assistant
SAP Engagement and Service Delivery
SAP Solution Manager Administration
System Administration
System Monitoring
My Home is the central point of access to all important data of almost all work centers in SAP Solution
Manager
5212 Support Infrastructure
A key requirement for effective support of IT solutions is the ability to perform root cause analysis with
speed and efficiency
With SAP Solution Manager SAP has long had an infrastructure in place for its ABAP applications that
efficiently supports SAP solutions This helps ensure the high availability and smooth running of
business processes For more information see the SAP Solution Manager section
With Solution Manager Diagnostics this knowledge has been extended to Java applications If for
example homegrown Java applications cause instability Solution Manager Diagnostics helps trace the
cause to eradicate the problem rapidly Solution Manager Diagnostics is fully integrated into SAP
Solution Manager 70 Solution Manager Diagnostics also contains two third-party tools CArsquos Wily
Introscopereg for measuring performance as well as troubleshooting problems of the Java EE Engine
and applications running on it and Mercury Loadrunnerreg which enables SAP Support to produce a
defined load in the SAP solution landscape remotely For more information see Solution Manager
Diagnostics [page 43]
The support infrastructure provides SAP Support with safe access to your productive landscape for safe
root cause analysis so ensuring that SAP Support does not change your landscape inadvertently You
require a support infrastructure to run SAP NetWeaver
The following figure shows the overall infrastructure including SAP NetWeaver administration tools
that are used by administrators or operators at the customer site
5 System Landscape
52 Shared Services
3856 PUBLIC 2011-04-15
Landscape Aspects
If you use SAP NetWeaver Process Integration 71 productively besides SAP Solution Manager (as a
central support platform) you have to set up Solution Manager Diagnostics for supportability reasons
Implementation Sequence
For information about the implementation of the support infrastructure see the document Master
Guide ndash SAP Solution Manager 70 available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution Manager ltReleasegt
5213 Collection of Landscape Data
Amongst other applications and services the support infrastructure and the SAP NetWeaver
administration tools rely on system landscape data
For SAP NetWeaver PI 71 you have to run non-ABAP components in your solution landscape
Therefore the System Landscape Directory is mandatory The landscape data that is automatically
gathered by the System Landscape Directory is replicated to SAP Solution Manager There are several
topology options for the System Landscape Directory They offer different grades of availability
administration and operation effort
For more information see the System Landscape Directory section
5214 Authentication and Single Sign-On
Before implementing your system landscape plan how to implement authentication and how to
integrate different systems into a Single Sign-On landscape Single Sign-On reduces complexity for end
users saving them valuable time while also reducing administration effort for resetting passwords
thereby contributing to TCO reduction
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
5215 Integrated User and Access Management
In a system landscape containing a combination of ABAP and Java components we recommend that
you integrate your user and access management so that you can use the same user data across different
systems administer this data centrally and control access to data SAPs mature fine-grained
authorization concept allows detailed control of access rights SAP NetWeaver provides both ABAP and
Java-based user management solutions The user management solution that you use to administer
your user data depends on factors such as the type of systems that are running in your landscape
If you want to use central user administration we recommend that you run it in a non-production
system If you do not have a central user administration yet you can for example realize it in the SAP
Solution Manager system
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3956
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
522 Examples for the Overall System Landscape of Shared Services
In this section we provide examples of how shared services can be set up depending on the system
landscape they are intended for The following examples aggregate the landscape aspects given in the
Use Cases section
NOTE
The following sections and the figure mostly do not show information about the life-cycle of
shared services For example you may also need a development and testquality assurance system
for SAP Solution Manager You should consider this aspect in addition to the information given
in this section based on your requirements
Small and MediumndashSized Customer Landscapes with Java
As you use Java productively for SAP NetWeaver PI 71 besides SAP Solution Manager you have to set
up additional components for optimal monitoring administration and support Solution Manager
Diagnostics and the central mode of SAP NetWeaver Administrator are already fully integrated into
SAP Solution Manager 70 as the central operations hub For SAP Process Integration you must also
set up SAP NetWeaver Administrator with a special role
We recommend that you do not install SAP Central Process Scheduling in the SAP Solution Manager
system You have to set up and operate the system which hosts your productive scheduler as a mission
critical system
In the SAP Solution Manager system you should set up a local System Landscape Directory in addition
to a central runtime System Landscape Directory This way you have a clear separation between your
management system (SAP Solution Manager) and managed systems in your landscape In addition
SAP Solution Manager then does not rely on a System Landscape Directory running in the production
environment For this setup configure the SLD data suppliers of your SAP Solution Manager system
to send data to the central runtime System Landscape Directory In addition configure automatic
bridge forwarding from your runtime System Landscape Directory to the local System Landscape
Directory For more information see the Planning Guide - System Landscape Directory
If you want to use a central system for Adobe Document Services we recommend that you install a
dedicated system for this purpose in your production environment For detailed information about
the sizing of the system for the different use cases see the Sizing Guide for Adobe Document Services at
SAP Service Marketplace at httpservicesapcomsizing Sizing Guidelines Solutions amp
Platform
We recommend that you start with this centralized SAP Solution Manager approach as depicted in the
following figure
5 System Landscape
52 Shared Services
4056 PUBLIC 2011-04-15
Figure 7 Single SAP Solution Manager Landscape
Large Customer Landscapes with Java
Large customers who have environments in their landscape that are large and distributed administered
by different groups or separated for security reasons can consider a distributed operations setup In
addition to the centralized setup described for small- and medium-sized customers above large
customers can put parts of the central management functions on extra hosts or systems for performance
or policy reasons You have the following options for a distributed setup
You may set up an extra system or client for Central User Administration (CUA)
The Change and Transport System (CTS) can run on an extra system However it is not
performance- or data-intensive
You may set up an extra system for central CCMS monitoring Depending on the customizing
and on the landscape size central CCMS may generate a lot of system load You can connect a
separate central CCMS to SAP Solution Manager for displaying alerts in the alert inbox of the System
Monitoring work center
You can use a separate SAP NetWeaver 70 system with usage type BI together with SAP Solution
Manager This may make sense with respect to the amount of landscape management data that is
stored for reporting purposes The amount of data strongly depends on the data granularity
storage time frame and landscape size
You can easily put Wily Introscope Enterprise Manager on an separate host
Other aspects described above for small- and medium-customers (such as the setup of the System
Landscape Directory) are also valid for large customers
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4156
523 Feature Details
This section provides further information about the features described above
5231 SAP Solution Manager
SAP provides you with SAP Solution Manager as the strategic application management platform and
to enable the collaboration between you and SAP You need to install at least one productive SAP
Solution Manager in your system landscape To ensure the availability of this application management
platform an SAP Solution Manager system is technically required to install or upgrade to SAP
NetWeaver 70 or higher If you are already using SAP Solution Manager you can also use it to manage
the solution you build with SAP NetWeaver In this case we highly recommend that you update SAP
Solution Manager to the latest version
As of SAP Solution Manager 70 SP15 you can use the newly created work centers
NOTE
During the SAP system installation or upgrade process you are prompted to enter the SAP
Solution Manager key An SAP Solution Manager system is required to generate this key Without
this key the installation or upgrade process cannot continue
You may generate all needed keys for your entire system landscape (development quality
assurance and production system) in one SAP Solution Manager system In case you plan to install
several solution landscapes (for example in different countries) one SAP Solution Manager
system is still sufficient
For more information see SAP Note 805390
It is possible to install multiple SAP Solution Managers If you do so they should host separate business
solutions
If you want to reduce the risk of unavailability you should not install SAP Solution Manager as a central
component Instead you can operate a 2-system-landscape with both a test and production
environment of SAP Solution Manager (especially if you are using time-critical functions like Support
Desk) If you also develop your own content a 3-system-landscape with a development test and
production environment is recommended
For more information about SAP Solution Manager see the following table
Topic Where to Find More Information
System infrastructure scenarios installation and configuration of SAP Solution Manager
Master Guide ndash SAP Solution Manager available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution ManagerltReleasegt
Benefits and usage scenarios SAP Solution Manager ndash Learning Maps available on SAP Service Marketplace at http
5 System Landscape
52 Shared Services
4256 PUBLIC 2011-04-15
Topic Where to Find More Informationservicesapcomrkt-solman or https
servicesapcomsolutionmanager
Additional information See SAP Service Marketplace at http
servicesapcomsolutionmanager
5232 Solution Manager Diagnostics
Solution Manager Diagnostics provides efficient and safe root-cause analysis of incidents in customer
solutions powered by SAP NetWeaver It can help monitor on operating systems databases Java
application activities performance and logs It also supports the reporting of software and
configuration changes that can lead to malfunctions and errors
You must run one Solution Manager Diagnostics within your SAP solution landscape if you run
applications based on SAP NetWeaver systems with usage type AS Java Agents are responsible for
delivering the data from all productive hosts within your system landscape to the Solution Manager
Diagnostics system
CAUTION
SAP Support performs root-cause analysis on incoming incidents with Solution Manager
Diagnostics Not installing and configuring this support infrastructure results in a dramatically
reduced service level
Solution Manager Diagnostics is fully integrated into SAP Solution Manager 70
Solution Manager Diagnostics also contains Wily Introscope (Display Server and Agent part) for
measuring performance as well as to troubleshoot problems of Non-ABAP applications Wily Introscope
is heavily used for troubleshooting applications running on AS Java
SAP has signed a distribution agreement for Wily Introscope SAP customers are allowed to use this
tool in a preconfigured way
For more information about Solution Manager Diagnostics and an FAQ list see SAP Service Marketplace
at httpservicesapcomdiagnostics
5233 System Landscape Directory
The System Landscape Directory (SLD) of SAP NetWeaver is the central directory of system landscape
information relevant for the management of your software life-cycle
NOTE
Note that the abbreviation SLD is not intended to define a product since the System Landscape
Directory is part of SAP NetWeaver This abbreviation is solely intended to improve readability
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4356
The System Landscape Directory contains a description of your system landscape (that is software
components that are currently installed) and a repository of software components that can
theoretically be installed in your landscape (such as the software components available from SAP)
Since this data gets updated automatically the System Landscape Directory provides reliable and up-
to-date system landscape information with as little effort for you as possible In this way the System
Landscape Directory acts as a central information provider for SAP and third-party tools that use this
data to deliver the services you need to keep your landscape up and running
For the System Landscape Directory as part of an SAP NetWeaver PI 71 landscape consider the following
aspects
Part of SAP NetWeaver PI 71 is a new version of the System Landscape Directory It is automatically
included in every SAP NetWeaver 71 system with usage type AS Java It offers enhanced functions
such as a full automatic synchronization mechanism for all data stored in it That is both data
delivered by data suppliers and data entered or changed manually in the System Landscape
Directory can be synchronized automatically This synchronization offers the following
A fully automated mechanism so no user interaction is required and conflicts are resolved
automatically
Asynchronous propagation of information so some nodes may be down temporarily
Communication over HTTP protocol
Uni- and bi-directional synchronization
Depending on your use case the full automatic synchronization could significantly reduce manual
synchronization effort
For SAP NetWeaver PI 71 the configuration of the system landscape directory and its data suppliers
is already included in the standard implementation procedure with SAPinst For existing systems
you only have to perform some quick and easy configuration actions to start operating the system
landscape directory server in an AS Java system
For SAP NetWeaver PI 71 you have the following options concerning SLD
Option 1
Run SAP NetWeaver PI 71 against an existing SLD running on SAP NetWeaver 70 We only
recommend this for upgrades from SAP NetWeaver 70 if you have a central SLD in operation
not running on one of your PI systems
Option 2
Use the SLD included in an SAP NetWeaver PI 71 system We recommend this option for new
installations and upgrades from older releases than SAP NetWeaver 70 due to the enhanced
functions and improved performance of SLD 71
NOTE
If you already have a central SLD running on SAP NetWeaver 70 in operation you could run
two SLD versions in parallel ndash SLD running on SAP NetWeaver 71 for your PI systems and
SLD running on SAP NetWeaver 70 for all other systemsuse cases This way your SAP
5 System Landscape
52 Shared Services
4456 PUBLIC 2011-04-15
NetWeaver PI 71 systems would benefit from the new features while it would be easy to set
up and operate such an SLD landscape For this purpose you could use the new fully
automatic synchronization This feature enables the automatic forwarding of all SLD data
from an SLD running on SAP NetWeaver 70 to an SLD running on SAP NetWeaver 71 As a
result there is no need to adapt most existing systems as their SLD data suppliers could still
send their data to the central SLD In brief the following steps would be required
1 Put SLD in a PI system into operation (part of standard implementation procedure)
2 Configure PI systems to use the new SLD (part of standard implementation procedure
for new PI systems)
3 Set up the fully automatic synchronization from your old SLD to your new SLD
As soon as an upgrade or an installation of a standalone AS Java 71 system is available you
could move your central SLD also to SAP NetWeaver 71 Then you could optionally shift
your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems
Figure 8
We recommend that you use a Domain Name System (DNS) alias so that you are able to switch to
another System Landscape Directory easily For example if customers build a new landscape they
normally start with a sandbox environment Over time more and more environments are set up
Once the production environment is in place move the System Landscape Directory there To do
this you can configure a new System Landscape Directory in the production environment
synchronize it with the old System Landscape directory and switch to the new one
Topology
Apart from the considerations above the System Landscape Directory offers several topology options
with different grades of availability at the expense of low administration and operation effort There is
no generic rule therefore on how to set up a System Landscape Directory in your system landscape
To find the topology and synchronization strategy for the System Landscape Directory that fits your
requirements concerning the System Landscape Directory availability (and hence the availability of
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4556
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
523 Feature Details 42
5231 SAP Solution Manager 42
5232 Solution Manager Diagnostics 43
5233 System Landscape Directory 43
Chapter A Appendix 47
A1 Maintaining System Landscape Information 47
Chapter B Reference 51
B1 The Main SAP Documentation Types 51
B2 List of Documentation 51
2011-04-15 PUBLIC 756
This page is left blank for documents that are printed on both sides
1 Introduction
This Master Guide provides you with a central starting point for the technical implementation of SAP
NetWeaverreg Process Integration (SAP NetWeaver PI) It also contains information about enhancement
package 1 for SAP NetWeaver Process Integration 71
SAP NetWeaver PI 71 is based on an established architecture for realizing cross-system business processes
and supporting an service-oriented architecture (SOA) The focus is on the service-based integration
of applications
Structure of the Master Guide
The Master Guide consists of the following sections
Introduction
Contains an introduction to this guide
Before You Start
Contains information about this document important things which you need to know before you
start and information on how to access the SAP Library
SAP NetWeaver Overview
Describes the building blocks of SAP NetWeaver PI
SOA-Based Integration Use Case
Introduces the use case and explains how to install it
System Landscape
Contains information about how to install your system landscape
Reference
Contains information about the overall documentation concept for SAP systems
CAUTION
Make sure you have the latest version of the Master Guide by checking SAP Service Marketplace
immediately before starting the installation
The Master Guide is regularly updated on SAP Service Marketplace at http
servicesapcominstallnwpi71 Planning
Constraints
The business scenarios that are presented here serve as examples of how you can use SAP software in
your company The business scenarios are intended only as models and do not necessarily run the way
they are described here in your customer-specific system landscape Check your requirements and
systems to determine whether these scenarios can be used productively at your site Furthermore we
1 Introduction
2011-04-15 PUBLIC 956
recommend that you test these scenarios thoroughly in your test systems to ensure that they are
complete and free of errors before going live
1 Introduction
1056 PUBLIC 2011-04-15
2 Before You Start
21 SAP Notes
You must read the following SAP Notes before you use this Master Guide and implement SAP NetWeaver
Make sure that you have the up-to-date version of each SAP Note which you can find on SAP Service
Marketplace at httpservicesapcomnotes
NOTE
The SAP Notes related to SAP NetWeaver PI 71 are also listed on SAP Service Marketplace at
httpservicesapcomsapnotesnwpi71
List of Important SAP Notes
SAP Note Number Title Description
1004107 Release Restrictions for SAP NetWeaver PI 71
Some restrictions apply to the productive use of SAP NetWeaver PI 71 These are documented in this SAP Note
1247043 Release Restrictions for SAP EHP1 for SAP NetWeaver PI 71
Some restrictions apply to the productive use of enhancement package 1 for SAP NetWeaver PI 71 These are documented in this SAP Note
22 More Information
The following table contains links to information available on SAP Service Marketplace or in the SAP
Library which is important for implementing SAP NetWeaver
Content Location on SAP Service Marketplace or in SAP Library
The latest version of the installation and upgrade guides for SAP NetWeaver Process Integration
httpservicesapcominstguidesnwpi71
Information about supported platforms (operating systems databases browsers) for all SAP NetWeaver components
httpservicesapcomplatforms Product Availability Matrix
Sizing of SAP NetWeaver httpservicesapcomsizing
Information about security SAP Security Guide See the SAP Library [page 12] at Adminitstratoracutes Guide Security Guide
Information about the technical operation of SAP NetWeaver
Technical Operations Manual See the SAP Library [page 12] at Adminitstratoracutes Guide Technical Operations for SAP NetWeaver
2 Before You Start
21 SAP Notes
2011-04-15 PUBLIC 1156
Content Location on SAP Service Marketplace or in SAP Library
Information about SAP NetWeaver PI Support Package Stacks
httpservicesapcomnetweaver SAP NetWeaver PI 71- Release-Specific Information Support Package Stacks Information
Information about installing SAP NetWeaver Support Package Stacks
httpservicesapcomMaintenanceNWPI71
Support Package Stack Guide ndash SAP NetWeaver
23 Accessing the SAP Library
For more information about SAP NetWeaver Process Integration access the SAP Library from any of
the following
SAP Help Portal at httphelpsapcomNWPI71 SAP NetWeaver Process Integration 71 Library
ltLanguagegt SAP NetWeaver Process Integration Library
CAUTION
The SAP Help Portal contains the latest version of the SAP Library Therefore we recommend
that you use this channel to access the SAP Library
An SAP system if you have installed the online documentation Choose Help SAP Library
The browser starts
The help files on the online documentation CDs or DVDs
If you want to view the help files in HTMLHelp format from the online documentation CDs or
DVDs you need a PC running Microsoft Windows to install the HTMLHelp Viewer
2 Before You Start
23 Accessing the SAP Library
1256 PUBLIC 2011-04-15
3 SAP NetWeaver PI Overview
Introduction
SAP NetWeaver PI 71 is part of the SAP NetWeaver technology platform The complete offering of the
SAP NetWeaver technology platform is visualized in the SAP NetWeaver technology map which you
can access at httpsdnsapcomnetweaver SAP NetWeaver at a Glance The technology map
enables you to drill down from top-level technology areas (for example Lifecycle Management) to
individual capabilities (for example Administration Monitoring and so on)
SAP NetWeaver PI includes the following capabilities
Repository-based Modeling and Design
Service Bus-based Integration
SOA Management
A different view is introduced by the end-to-end use case concept This concept offers an
implementation view on SAP NetWeaver to structure and facilitate your implementation
A use cases is a process that typically involves several SAP NetWeaver capabilities It is not limited to a
single component or capability A use case guides you through the different phases of your
implementation project ndash from information through installation to the configuration phase This
implies that a uses case addresses several user roles administrator power user and end user
This document describes the SOA-based integration use case
Architecture Principals
The architecture of SAP NetWeaver Process Integration 71 (SAP NetWeaver PI 71) is based on an
established architecture for realizing cross-system business processes and is a further development of
lower releases (SAP NetWeaver 70 usage type Process Integration and SAP XI 30 as part of SAP
NetWeaver 2004) SAP NetWeaver PI 71 plays an important role in supporting an service-oriented
architecture (SOA) The focus is on the service-based integration of applications
SAP NetWeaver PI is based on general standards so as to enable 3rd-party systems to be integrated At
the center of SAP NetWeaver PI is an XML-based communication that uses HTTP (Hyper Text Transfer
Protocol) Irrespective of the scenario used the application-specific contents are transferred in messages
in user-defined XML (eXtensible Markup Language) from the sender to the receiver either via the
Integration Server or directly between the systems involved
The following figure gives an overview of the key capabilities of SAP NetWeaver Process Integration
3 SAP NetWeaver PI Overview
2011-04-15 PUBLIC 1356
Figure 1 SAP NetWeaver PI Key Capabilities Overview
SAP NetWeaver Process Integration 71 enables the integration of the applications of the following
communication parties
B2B Party Any business partners that want to integrate their application with other applications
outside their own system landscape Scenarios that require industry standards are supported as
well as any scenarios that do not adhere to a particular industry standard
SAP Applications that run on SAP systems This includes the processing of events by using the
Business Activity Monitoring (BAM) infrastructure
3rd-Party Application Applications from 3rd-party providers within one system landscape for
example database or file-system-based
3rd-Party Middleware Middleware systems from 3rd-party providers that are required for the
integration of applications within a company and across company boundaries
SAP NetWeaver PI also supports internal company scenarios and cross-company scenarios It enables
you to connect systems from different vendors (non-SAP and SAP) in different versions and
implemented in different programming languages (Java ABAP and so on) to each other Like the rest
of the SAP NetWeaver platform SAP NetWeaver PI is based on an open architecture uses open standards
(in particular those from the XML and Java environments) and offers those services that are essential
in a heterogeneous and complex system landscape
To enable end-to-end SOA development SAP NetWeaver Process Integration 71 offers a Universal
Description Discovery and Integration (UDDI) v3-based Services Registry where providers can publish
service endpoints definitions and associated metadata and consumers can discover the appropriate
services for their scenarios The Services Registry provides capabilities for classifying and browsing
3 SAP NetWeaver PI Overview
1456 PUBLIC 2011-04-15
services using semantic-rich classification systems The Services Registry is part of Application Server
Java (AS Java)
31 Installable Software Units
SAP NetWeaver comprises the following three types of installable software units
Systems that are configured for a specific purpose as indicated by one or more usage types
Standalone engines that provide one specific (server) function in combination with one or more
SAP NetWeaver PI systems
Clients used by (many) people from their local front-end PC to access functions offered by systems
of SAP NetWeaver PI or standalone engines in the system landscape
In the following sections you can find more details about the software units The figure below provides
and overview of the software units
Figure 2 Installable Software Units for SAP NetWeaver PI
For this and other figures in this guide the following legend applies
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1556
Figure 3 Legend
311 Systems with Usage Types
SAP systems are the main building blocks of SAP NetWeaver They are identified by unique SAP system
IDs (SAPSIDs) and configured for a certain purpose as indicated by usage types Usage types have the
following characteristics
They are a structuring element for SAP software on a technical level
Usage Types determine the intended purpose of a system and the role it plays in a given (distributed)
use case
They are realized by installing and configuring a collection of software components
They allow a logical view of the technology platform SAP NetWeaver PI
A usage type may require other usage types in the same system to operate
They can also be run in the same system together with other usage types that are not a prerequisite
How SAP NetWeaver Systems are Used
The following sections describe the usage types and their dependencies for SAP NetWeaver PI
Application Server ABAP (AS ABAP)
Purpose
AS ABAP is used to provide the ABAP foundation of SAP NetWeaver PI
Application Server ABAP provides a complete development and runtime environment for ABAP-based
applications It is optimized for the development of highly scalable business applications The ABAP
development and runtime environment makes it possible to develop complex business applications
3 SAP NetWeaver PI Overview
31 Installable Software Units
1656 PUBLIC 2011-04-15
without having to worry explicitly about technical details such as process or memory administration
multi-user capability database connections or similar issues These are provided in the basis services or
are integrated directly in the ABAP runtime The application development is similarly independent of
the underlying platform The application server decouples the application coding completely from the
operating system and database that are used
Dependencies
AS ABAP can be combined optionally with other usage types in one system
Application Server Java (AS Java)
Purpose
AS Java is used to provide the Java foundation of SAP NetWeaver PI using the Java Engine a Java EE-
compliant application server for running enterprise applications In addition to the pure Java EE
standard technologies the Java Engine implements complementary technologies such as Web Dynpro
or Web Services that are targeted at supporting large-scale real-business application development
projects
Dependencies
AS Java can be combined optionally with other usage types in one system
Process Integration (PI)
Purpose
PI consists of core components that model design automate and integrate processes in one or more
application systems For the integration of internal and cross-company processes PI is used to
incorporate all the functions of what was formerly known as Exchange Infrastructure (XI) In addition
PI contains core components for Business Process Management for application-embedded and
application-unbounded processes
The Advanced Adapter Engine is also part of usage type PI You use Advanced Adapter Engine to connect
to SAP systems (RFC adapter) and external systems You use the various adapters in Advanced Adapter
Engine to convert XML- and HTTP-based messages to the specific protocol and format required by
these systems and the other way around You can use the Advanced Adapter Engine that is part of
your PI system as a central Advanced Adapter Engine Optionally (for performance reasons) you can
install a non-central Advanced Adapter Engine [page 19] separately as a system with AS Java and parts of the
usage type PI on a separate host
Dependencies
PI requires AS ABAP and AS Java as prerequisites in the same system
For installing PI it is mandatory to have a dedicated PI system This applies to development quality
and production landscapes It is a prerequisite that no other system in your system landscape has a
higher release and enhancement package level than the PI system If you want to upgrade or install an
application in your system landscape you first have to make sure that the current release and
enhancement package level of the PI system is on the same level - if required you have to upgrade the
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1756
PI system first to the new or a higher release In a dedicated PI system this can be accomplished with a
minimum of downtime Also the PI system would not be affected by the downtime of other usage
types running in the same system
Configuration of Systems with Usage Types
Configuration information is available in the installation guides the configuration wizard and SAP
Solution Manager
In the Installation Guide ndash SAP NetWeaver PI 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt you find
initial technical configuration tasks This guide also informs you about how you can run the
configuration wizard and how you can access the configuration information in SAP Solution
Manager
For certain usage types configuration tasks can be applied by the configuration wizard after the
installation To do this you start the configuration wizard from SAP NetWeaver Administrator
The configuration steps for systems with usage types required for an use case are accessible through
SAP Solution Manager
To be able to use SAP Solution Manager for the configuration tasks you have to import the latest
SAP Solution Manager Implementation Content (Add-On ST-ICO) that is available for your SAP
Solution Manager release For more information see SAP Note 631042 (Release strategy for Implementation
Content (ST-ICO))
SAP Solution Manager Implementation Content is available on SAP Service Marketplace at
httpservicesapcomswdc Installations amp Upgrades Entry by Application Component SAP
Technology Components SAP Solution Manager ltReleasegt Content ST-ICO
In SAP Solution Manager you create a project and a project structure In the configuration phase
you select configuration structures with pre-delivered SAP content for your project You can find
the following different types of configuration tasks in SAP Solution Manager
Mandatory configuration tasks All configuration tasks that are mandatory for the standalone
engine or usage type
Optional configuration tasks Configuration tasks for areas where customers need to decide
if they want to use these functions (for example high availability or security settings)
Additional functions ndash configuration tasks Configuration tasks for functional units that are
used in certain use cases only
A marked checkbox in front of the configuration tasks indicates those configuration tasks that are
relevant for the use case you have chosen To configure ABAP systems SAP Solution Manager
offers executable configuration files (IMG activities)
For information about using SAP Solution Manager Content and creating a configuration guide
see the following documentation
httphelpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Implementing
and Upgrading SAP Solutions Configuration
3 SAP NetWeaver PI Overview
31 Installable Software Units
1856 PUBLIC 2011-04-15
How to Create a Configuration Guide using SAP Solution Manager available at http
servicesapcomsolutionmanager Media Library How-To Documents
Restrictions for Systems with Multiple Usage Types
If you have one system with multiple usage types be aware that we do not provide standard tools
to separate these usage types and distribute them to multiple systems at a later stage For example
if you have a system with usage types A and B you are not able to migrate it with SAP standard
tools into two systems one with usage type A only and the other with usage type B only
In addition we do not provide standard tools to merge multiple systems with different usage types
into one system with multiple usage types at a later stage
If you want to perform these tasks you require specific project support
The following figure shows that SAP standard system copy and migration tools do not support
you in separating or merging systems with usage types
Figure 4 No Support for Merging or Separating Systems with Usage Types
Although you can use one system for multiple usage types client restrictions apply for usage type
PI PI requires a dedicated client due to special PI requirements concerning the client pipeline
Whereas application client pipelines only send and receive messages the central PI pipeline can
also map messages to different formats before sending them
312 Standalone Engines
Standalone engines of SAP NetWeaver are additional installable software units They do not work as
full-blown systems of SAP NetWeaver but as standalone engines that provide a specific (server) function
in combination with one or more SAP NetWeaver systems
Standalone engines are not part of a usage type They do not run on AS ABAP or AS Java
The standalone engines that are available for SAP NetWeaver Process Integration are described in the
following
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1956
Gateway
It is possible to install an SAP instance of an SAP NetWeaver system based exclusively on a standalone
gateway This type of instance does not contain normal work process types (dialog background update
enqueue or spool) Only the gateway process (gwrd) is started If there is an SNA connection to an R
2 system gateway work processes (gwwp) are also started
SAP Conversion Agent by Informatica
SAP Conversion Agent by Informatica is a data conversion tool that enables you to create interfaces
between any data formats and XML-based systems SAP Conversion Agent can convert unstructured
semi-structured and structured formats to XML and the other way around The Conversion Agent
comprises the Conversion Agent Studio and the Conversion Agent Engine In the Conversion Agent
Studio you can develop and configure data conversions The Conversion Agent Engine executes the
data conversions
Search and Classification (TREX)
You can use Search and Classification with SAP NetWeaver PI to search for messages that were previously
indexed Message search using index provides additional methods of searching for specific messages In
addition to static header attributes you can also use adapter-specific message attributes and data from
the message payload for the search A requirement of this however is that the messages are indexed
first You can apply the index-based message search to one or all indexed components of an integration
landscape (domain) Integration Server Adapter Engines and ABAP business systems
For more information see the SAP Library [page 12] at Administratorrsquos Guide Technical Operations for SAP
NetWeaver Administration of SAP NetWeaver Systems Administering PI (Process Integration) Monitoring Index
Administration
Web Dispatcher
The Web Dispatcher lies between the Internet and your SAP system It is the entry point for HTTP(s)
requests into your system which consists of one or more SAP NetWeaver application servers As a
software web switch the Web dispatcher can reject connections or accept them When it accepts a
connection it balances the load to ensure an even distribution across the servers
You can use the Web dispatcher in ABAPJava systems and in pure Java systems as well as in pure ABAP
systems
It is also beneficial to use the Web Dispatcher if you do not need security functions (entry point in the
demilitarized zone (DMZ) SSL URL filtering) but you simply want to balance the load between
multiple SAP NetWeaver Application Server instances
Since Web Dispatcher is optional for every SAP system it is not contained in the system landscape and
the implementation sequence of the use case in this documentation
For more information see the SAP Library [page 12] at Function Oriented View Application Server Infrastructure
SAP Web Dispatcher
3 SAP NetWeaver PI Overview
31 Installable Software Units
2056 PUBLIC 2011-04-15
Advanced Adapter Engine
You use the Advanced Adapter Engine to connect to SAP systems (RFC adapter) and external systems
You use the various adapters in Advanced Adapter Engine to convert XML- and HTTP-based messages
to the specific protocol and format required by these systems and the other way around For specific
senderreceiver combinations messages can be processed without invoking the central Integration
Engine In principle you connect external systems using the adapters that are installed centrally or
non-centrally in Advanced Adapter Engine You can use the Advanced Adapter Engine that is part of
your PI system as a central Advanced Adapter Engine Optionally (for performance reasons) you can
install a non-central Advanced Adapter Engine separately as a system with AS Java and parts of the
usage type PI on a separate host
Adapter Engine (Java SE)
Adapter Engine (Java SE) is a separate software unit You can use it only if you have SAP NetWeaver
systems with usage type PI in your system landscape It has to be installed manually You use the Adapter
Engine (Java SE) to connect to external systems Using the various adapters in the Adapter Engine (Java
SE) XML and HTTP-based messages can be converted to the specific protocol and format required by
such systems and the other way around The Adapter Engine (Java SE) only provides some of these
adapters as a standalone version with restricted functions for operating systems that do not support
SAP NetWeaver PI 71 but that have at least a Java Runtime Environment 50 Therefore you should
use the Adapter Engine (Java SE) only if the platform prerequisites do not allow you to use the Advanced
Adapter Engine
SAP Partner Connectivity Kit
SAP Partner Connectivity Kit (PCK) runs on AS Java with parts of the usage type PI It enables a system
of a smaller company or subsidiary that does not run SAP NetWeaver PI to connect to your SAP
NetWeaver systems
313 Clients
Clients are additional installable programs or tools They reside either on local front-end PCs accessed
by users or on back-end systems where they act as client programs within an SAP NetWeaver system
landscape
The clients that you can use with SAP NetWeaver Process Integration are described in the following
sections
SAP GUI
NOTE
We recommend that you use the following versionsI
SAP GUI for Windows 710 (or higher) with the latest patch level
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 2156
SAP GUI for Java 710 (or higher) with the latest revision
The integrated SAP ITS 710
For more information about the SAP GUI family see SAP Service Marketplace at http
servicesapcomsapgui
SAP offers three different client applications for accessing ABAP applications in SAP systems (such as
SAP NetWeaver systems with usage type AS ABAP) This SAP GUI family consists of
SAP GUI for HTML
SAP GUI for HTML is based on the SAP integrated Internet Transaction Server (ITS) which is
included in the installation of SAP NetWeaver systems as of SAP NetWeaver 2004 On the client
side only a suitable browser (such as Internet Explorer 70 or Firefox 20) and a virtual machine are
required SAP ITS 620 is not compatible with SAP NetWeaver 71
SAP GUI for the Java environment (SAP GUI for Java)
SAP GUI for Java is a generic SAP GUI that covers a variety of platforms
For more information about the installation of SAP GUI for Java see the documentation Installation
Guide ndash SAP Front End
SAP GUI for the Windows environment (SAP GUI for Windows)
SAP GUI for Windows is SAPs universal client for accessing all SAP applications built on ABAP
technology It is available on the Microsoft Windows platform only and offers the broadest feature
set of all members of the SAP GUI family
For more information about the installation of SAP GUI for Windows see the Installation Guide ndash
SAP Front End
SAP NetWeaver Developer Studio
The SAP NetWeaver Developer Studio is SAPrsquos Integrated Development Environment (IDE) for Java
and is based on the open-source tools framework Eclipse 33 With the SAP NetWeaver Developer Studio
you can develop Java EE 5 applications from scratch using the built-in support for new technologies
such as EJB 30 and JSF 12
During the installation of the SAP NetWeaver Developer Studio several features are offered for
installation For SAP NetWeaver PI 71 only the following features are relevant
SAP NetWeaver Developer Studio Platform
SAP NetWeaver Developer Studio Java EE
NOTE
If you want to use one of the other features you need SAP NetWeaver Composition Environment
and a corresponding developers licence
For more information about the installation of SAP NetWeaver Developer Studio see the Installation
Guide ndash SAP NetWeaver Developer Studio 71 or Installation Guide ndash SAP NetWeaver Developer Studio 71 Including
Enhancement Package 1
3 SAP NetWeaver PI Overview
31 Installable Software Units
2256 PUBLIC 2011-04-15
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
SAP enhancement packages are a new way of delivering new functions for SAP NetWeaver This allows
a clear separation between the delivery of new functions on the one hand and corrections legal changes
and security updates on the other hand (in Support Package stacks) SAP enhancement packages are
cumulative an enhancement package always contains the functions of the corresponding predecessor
enhancement packages
Enhancement packages are maintained by their own Support Packages while the main release is in
maintenance
Benefits
SAP enhancement packages offer the following benefits
You have reduced effort for testing and no effort for training when applying Support Packages as
new features are only shipped with enhancement packages
Adding new functions between releases becomes predictable and controllable
New functions can be added successively in small steps There is no need to fully upgrade your
system to get new functions
You have minimal training effort when applying an enhancement package because existing
functions are not replaced
Implementation
There are the following ways to get an SAP NetWeaver system with the release level of SAP enhancement
package 1 for SAP NetWeaver Process Integration 71
New installation of SAP NetWeaver PI 71 including enhancement package 1 using the standard
installation tool SAPinst
Upgrade of an existing SAP NetWeaver system from a release lower than SAP NetWeaver PI 71 to
SAP NetWeaver PI 71 including enhancement package 1 For this you use the upgrade programs
SAPup (for ABAP) and SAPJup (for Java)
Installation of the enhancement package on an existing SAP NetWeaver PI 71 system
For this you use the Software Update Manager (SUM) The Software Update Manager evolved
from the previously used SAP Enhancement Package Installer The tool has been renamed to reflect
its broader use for example you can also use it for applying Support Package Stacks to your system
On the ABAP side the Software Update Manager uses a system cloning and switch procedure for
installing enhancement packages It installs a copy of the system the shadow system parallel to
the original system This shadow system is used to update the relevant software components and
to install the additional components while the original system is still in production operation At
a certain point during downtime the switch to the new system is made and afterwards any parts
of the original system that are no longer needed are deleted The enhancement package installation
in a Java system uses a deploy-based procedure that is no shadow system is used The Software
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2011-04-15 PUBLIC 2356
Update Manager requires a stack configuration file (xml file) as input file for the enhancement
package installation procedure This file lists all the packages that are to be installed in your systems
The stack configuration file is generated when you download the required packages
As the Software Update Manager is updated regularly we recommend to always use the latest
version It is delivered as part of the SL toolset For more information see http
servicesapcomsltoolset
For an overview of all required steps for the enhancement package installation process and
corresponding documents see Process Overview Installation of Enhancement Package 1 on an Existing SAP
Netweaver PI 71 System [page 28]
Content of SAP Enhancement Package 1 for SAP NetWeaver PI 71
With enhancement package 1 for SAP NetWeaver PI 71 new features are introduced and some existing
are changed The following is a selection of some of the most important enhancements
Enhanced design and modelling options in the Enterprise Services Repository
New services registry
Support for new Web services standard (Web Services Reliable Messaging)
New modules for the Advanced Adapter Engine
Use of shared memory of the ABAP Application Server for message processing
For more information about the changes see SAP Library [page 12] at Whatacutes new in SAP NetWeaver PI 71
ndash Release Notes
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2456 PUBLIC 2011-04-15
4 SOA-Based Integration Use Case
41 Overview
You can use SOA-based integration to set up the communication between service providers and service
consumers in both application-to-application and business-to-business scenarios and to execute
operate and monitor the communication at runtime SOA-based integration covers both direct (point-
to-point) as well as mediated (via an Integration Server) communication between service providers and
service consumers
The use case spans the whole life cycle of a SOA-based integration scenario including
Scenario modeling and service design in the Enterprise Services Repository
Implementation of the service provider and consumer in the back-end systems
Configuration and finally execution monitoring and operation of the integration scenario
For scenarios using Integration Server or broker-based communication the configuration of the
different connectivity options (for example SOAP RFC Web Services Industry standards and JDBC)
and their enhancements is covered
For more information see the following documents
Service-Enabling with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdnsoa-modeling
Getting Started
Service-Enabling a Legacy Application with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdn
soa-servicebus Getting Started
In the following you will find information about the installation of the involved software units
42 System Landscape
The following figure shows the system landscape for this use case
4 SOA-Based Integration Use Case
41 Overview
2011-04-15 PUBLIC 2556
Figure 5 SOA-Based Integration
It is mandatory to have a dedicated PI system This applies to development quality and production
landscapes
For PI it is a prerequisite that no other system in your system landscape has a higher release than
the PI system For exceptions to this rule see SAP Note 1043047 For example SAP XI 30 is compatible
with SAP NetWeaver 640 and 70 application systems since the same XI protocol is used Apart
from these exceptions if you want to upgrade or install an application in your system landscape
you first have to make sure that the PI system is on the same release level If required you have to
upgrade the PI system first to the new or a higher release
CAUTION
Although it should be technically possible to run an application system with a higher release
than your PI system in your system landscape this is not supported by SAP (apart from the
exceptions listed in SAP Note 1043047) Therefore you run such a landscape at your own risk
You can use the Advanced Adapter Engine that is part of your PI system as a central Advanced
Adapter Engine
Adapter Engine (Java SE) can be installed in a non-SAP Java environment However it only hosts
a subset of the adapter functionality is only supported for compatibility reasons and should be
used only if this is a precondition in your environment
Optionally you can use the Change Management Service (CMS) of an SAP NetWeaver 70 system
with usage type DI to transport design objects and repository objects For more information see
the SAP Library [page 12] at Administratoracutes Guide Technical Operations for SAP NetWeaver Administration
of SAP NetWeaver Systems PI (Process Integration) Software Logistics Transporting ESR Content and Objects
of Integration Directory PI Transports Using the Change Management Service (CMS)
Smaller business partners or subsidiaries that do not run SAP NetWeaver install SAP Partner
Connectivity Kit in their system landscape SAP Partner Connectivity Kit enables XML document
4 SOA-Based Integration Use Case
42 System Landscape
2656 PUBLIC 2011-04-15
exchange between your SAP NetWeaver systems and the partner systems Since SAP Partner
Connectivity Kit gets installed in their system landscape it is not shown in the system landscape
figure above
The AS ABAP system acts as an application and service provider For Java Web Services you also
require AS Java In addition you require SAP NetWeaver Developer Studio on the client side as a
development environment
The Web service client can be either an SAP or a non-SAP application For example an AS ABAP
system or a Web browser could act as application or service consumer
You can install SAP Conversion Agent by Informatica in the system with usage type PI or on a host
where SAP Partner Connectivity Kit is installed or on a host where neither usage type PI nor SAP
Partner Connectivity Kit is installed
43 Implementation Sequence
Procedure
To install this use case perform the steps listed in the following table
StepAction[Corresponding Documentation] Remarks
1 Make sure that you have performed the preparation steps You have planned your system landscape [page 33]
(that is you have decided how many systems you require how you want to use each of these systems and which standalone engines and clients you require)
With the help of your hardware partner you have mapped your systems and standalone engines to properly sized hosts
You have planned and installed shared services [page 35]
2 Installation of system with usage type PI (includes the installation of AS ABAP and AS Java)
NOTE
For usage type PI a Unicode installation is mandatory
[Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt]
If you want to use the features of enhancement package 1 use the direct installation of SAP NetWeaver PI 71 including enhancement package 1
Make sure that you perform the configuration steps as described in the installation guide For certain usage types configuration tasks can be applied by the configuration wizard These configuration tasks as well as any additional configuration steps for your use case are listed in SAP Solution Manager For more information
4 SOA-Based Integration Use Case
43 Implementation Sequence
2011-04-15 PUBLIC 2756
StepAction[Corresponding Documentation] Remarks
see the Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt
3 Install the Adapter Engine (Java SE) engines if required[Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
4 To integrate small business partners and subsidiaries the business partners or subsidiaries install SAP Partner Connectivity Kit running on AS Java with parts of usage type PI in the business partners or subsidiarys system landscape[Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
5 Install SAP Conversion Agent by Informatica if required[SAP Library [page 12] at Function-Oriented View Process Integration SAP Conversion Agent by Informatica Deploying and Using Conversion Agent ]
6 Installation of clients SAP GUI
[Installation Guide ndash SAP Front End]
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
The process sequences give a comprehensive overview of the steps relevant for the enhancement
package installation on an existing SAP NetWeaver PI 71 system
The process sequence is divided into a planning phase and an implementation phase Each step in both
phases contains references to the corresponding documentation to ensure that you can easily find the
information you need
Process
NOTE
To download the enhancement package files and required Support Packages you require the SAP
Solution Manager Maintenance Optimizer You have the following options
Manual Selection
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2856 PUBLIC 2011-04-15
You manually select the required files from SAP Service Marketplace at http
servicesapcomswdc using the SP Stack Application You use the Maintenance Optimize
only to approve the packages which is a prerequisite for the download
Automatic Calculation
The Maintenance Optimizer supports the download of a consistent queue that includes all
necessary Support Packages and enhancement packages In addition SAP Solution Manager
calculates a valid import queue for the selected SAP system and generates the enhancement
package stack configuration file that you require for the installation
As a prerequisite the system that you want to update needs to be maintained correctly in
SAP Solution Manager System Landscape As the Maintenance Optimizer uses this data for
the calculation it is crucial that the data is up-to-date In addition the SAP Solution Manager
system requires a Minimum Support Package level (see below)
Planing PhaseStep Description Documentation
Hardware amp Software Prerequisites
Check which platforms are supported for your target release (OSDB dependencies)
Product Availability Matrix (PAM) at httpservicesapcompam
Check which hardware sizing is required for your target release
Sizing information at httpservicesapcomsizing
Solution Manager Prerequisites
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of the required software packages you have to make sure that your SAP Solution Manager system has the required Support Package levelAt least SAP Solution Manager 70 EHP1 Support Package Stack 17 is required We recommend to use SAP Solution Manager 70 EHP1 Support Package Stack 23Check if you need to do an update or upgrade of your SAP Solution ManagerMake sure that you run the guided procedure SOLMAN_SETUP after every installation or update of SAP Solution Manager and that it completes successfully
For upgrades from source release SAP Solution Manager 31 and 32Upgrade Guide ndash SAP Solution Manager 70 incl Enhancement Package 1For updates from SAP Solution Manager 70Update Guide SAP Enhancement Package 1 for SAP Solution Manager 70Follow-up activities after an Support Package Stack update or enhancement package updateSolution Operations Guide ndash SAP Solution Manager 70 EHP1 section Software Change Management All guides are available at http
servicesapcom instguides SAP Components SAP Solution Manager -gt Release 70 EHP 1
Implementation PhaseStep Description Documentation
1Solution Manager Preparation
Configure the SAP Solution Manager Maintenance Optimizer
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of software packages make sure your
Configuration of Maintenance Optimizer http
helpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Change Request Management and Change ControlMaintenance Optimizer
Prerequisites
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 2956
Implementation PhaseStep Description Documentation
system landscape data in SAP Solution Manager is maintained correctlyLandscape Verification 10 which is an add-on to SAP Solution Manager can support you in maintaining your system landscape data The use of this tool is optional
Landscape Verification http
wwwsdnsapcom irj
sdn alm-update-
management link Landscape Verification under Related Areas on Upgrade and Update Management (in the right column)
SAP Note 1468605 (Installation of Landscape Verification)
Maintaining System Landscape Information [page 47]Note that the information provided in this section is based on SAP Solution Manager 70 EHP1 SP23
2System Preparation
Prepare your system as described in the documentation for example perform OS DB specific preparations and the PI-specific preparations
Update Guide ndash Update of SAP Systems with Software Update Manager sections Planning and Preparation
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
3Software Download
Select and download the software packages in either of the following ways Automatic calculation Create
a maintenance transaction in the Maintenance Optimizer and choose the Calculate Files Automatically option
Manual Selection Create a maintenance transaction in the Maintenance Optimizer and choose the Select Files Manually option You then can select the files manually using the SP Stack application in SAP Service Marketplace
NOTE
You have to download the stack configuration file manually after you have selected all files in the SP Stack
httphelpsapcom SAP Solutions SAP Solution Manager
SAP Solution Manager 70 EHP1 ltSPgtChange Request Management and
Change Control Maintenance Optimizer Maintenance Procedure Scenarios
For information about the automatic calculation see Maintenance Transaction with Installation of an Enhancement PackageFor information about the manual selection and approval process see section Approve and Download Files in Download Basket
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
3056 PUBLIC 2011-04-15
Implementation PhaseStep Description Documentation
application Choose Generate Stack XML and save the file
4Enhancement Package Installation
Run Software Update Manager to update your system with the selected software packages
Update Guide ndash Update of SAP Systems with Software Update Manager
5Follow-Up Steps
Perform technical and PI-specific follow-up activities after the enhancement package installation is done
Update Guide ndash Update of SAP Systems with Software Update Manager section Follow-Up Activities
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
6Configuration
Configure newly installed enhancement package functions using SAP Solution Manager content
See Systems with Usage Types [page 16] section Configuration of Systems with Usage Types
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 3156
This page is left blank for documents that are printed on both sides
5 System Landscape
51 Planning Your System Landscape
The installable software units that make up your system landscape depend on the functions that you
want to implement For information about the features see systems [page 16] standalone engines [page 19]
and clients [page 21]
In addition you have to determine the required shared services [page 35] (such as SAP Solution Manager
or SAP NetWeaver Administrator) that run on central systems in your system landscape and the
landscape aspects relevant for their implementation
In the following you will find general information that you should consider when planning your system
landscape
Sizing
You have to map systems and standalone engines to hosts after you have a clear picture of the following
Which systems and standalone engines you require
How many systems you require and how you want to use each of these systems
NOTE
No general guideline can be given for the sizing of your landscape since this relies heavily on your
requirements You should therefore perform this task together with your hardware partner and
your technical consultant
For information about sizing your systems you can use the following information sources
Your first point of reference is the Quick Sizer
SAP built the Quick Sizer as an online sizing questionnaire Internet application in close cooperation
with its hardware partners This tool delivers general sizing categories based on your volume load
estimates The results provide an objective basis for sizing independent of platform and
configuration
For more information see SAP Service Marketplace at
httpservicesapcomsizing for the SAP NetWeaver PI 71 sizing guide available under
Sizing Guidelines Business Suite amp Services
httpservicesapcomquicksizer for more information and access to the tool itself
Also consider the following important aspects concerning sizing
High availability
5 System Landscape
51 Planning Your System Landscape
2011-04-15 PUBLIC 3356
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Technical Infrastructure High Availability
Unicode
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Internationalization
Contact your hardware partner to find out the appropriate number of sized hosts
The platform-independent abstract results of the Quick Sizer can be used by any of our hardware
partners to create a concrete offer SAP itself does not make any hardware recommendations the
responsibility for sizing and detailed hardware configuration lies with the hardware partners
Figure 6 Example of Mapping of Systems and Standalone Engines to Three Hosts
NOTE
Optionally you could also distribute single systems to multiple hosts For example you could
decide to install the database instance of an SAP system on a separate host for performance
reasons or distribute other system instances to achieve high availability
To provide a mapping that fits your required functions and performance your hardware partner
and your technical consultant have to identify the number of required instances of SAP NetWeaver
find out how to distribute these instances to hosts and what functions will run on which instance
Therefore the hardware partner and the technical consultant have to consider many different
aspects such as
Number of required SAPS (SAP Application Benchmark Performance Standard) for each
system (provided by Quick Sizer)
Landscape-relevant aspects concerning security For more information see the SAP Security
Guide in the SAP Library [page 12] at Administratoracutes Guide Security Guide
Landscape-relevant aspects concerning scalability high availability operation and software
life-cycle management
5 System Landscape
51 Planning Your System Landscape
3456 PUBLIC 2011-04-15
For more information about relevant aspects for the mapping of systems to hosts see the document
Technical Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
Scaling and Distribution Options
You may need to design your system landscape for a large number of users SAP NetWeaver PI offers
you different means of scalability The following list provides you with some examples
You could install multiple systems of one type and use them for different purposes
You could scale every system by installing dialog instances or by distributing the database instance
For more information about distribution options on the instance level see the Technical
Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
For every SAP system you could additionally install Web Dispatcher For more information see
the SAP Library [page 12] at FunctionndashOriented View Application Server Infrastructure SAP Web
Dispatcher
You could further distribute certain standalone engines ndash for example Search and Classification
(TREX) is based on a flexible architecture that supports a distributed installation For more
information see the Technical Infrastructure Guide ndash SAP NetWeaver PI 71 available in SAP Service
Marketplace at httpservicesapcominstallNWPI71
52 Shared Services
You normally run shared services on central systems in your system landscape The following features
could be used for SAP NetWeaver Process Integration to realize shared services
SAP Solution Manager
Used to implement train test maintain monitor control change and manage incidents of your
SAP solution system landscape (open end-to-end application management)
As of SAP Solution Manager (70) 40 Support Package 15 SAP Solution Manager has become the
platform for SAPs end-to-end solution operations strategy Functions for complete application
management has been combined with administrative tools and has been merged in newly created
role based work centers
NOTE
Be aware that you require an SAP Solution Manager system to install or upgrade to SAP
NetWeaver 70 and higher An SAP Solution Manager system is required to generate the SAP
Solution Manager key needed during the installation or upgrade process Without this key
the installation or upgrade process cannot continue
For SAP NetWeaver Process Integration you require SAP Solution Manager 70
For more information see SAP Note 805390
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3556
Solution Manager Diagnostics
An integral part of SAP Solution Manager that is running as a Java application on the Java stack of
SAP Solution Manager 70 Solution Manager Diagnostics is used to analyze the root cause of
incidents in your landscape in an efficient and safe way Before Go-Live Solution Manager
Diagnostics has to be set up and made accessible remotely
SAP NetWeaver Administrator
SAP NetWeaver Administrator is the central administration component which is used for
monitoring and administering Java applications It is included in SAP NetWeaver systems with AS
Java
SAP NetWeaver Administrator exists in the following flavors
A local mode which runs out of the box and which focuses on administrating the underlying
SAP NetWeaver AS Java
NOTE
For a SAP NetWeaver PI 71 it has a special role which you need to activate using a
configuation wizard
A central mode which has to be configured before use and which deals with the system
landscape management
SAP has decided to merge the central mode of SAP NetWeaver Administrator into the new work
centers available as of SAP Solution Manager 70 SP 15 Thus it can be used in an administrative
context together with non-Java-based administration tools Although the central mode of SAP
NetWeaver Administrator will be still available for some time SAP will not develop this tool any
further SAP focuses on optimizing the administrative work centers of SAP Solution Manager
instead
The local mode of SAP NetWeaver Administrator stays untouched It is available for current and
future releases of SAP NetWeaver
SAP Central Process Scheduling by Redwood
SAP Central Process Scheduling application by Redwood enables central job scheduling and job
monitoring of current and old releases of AS ABAP systems (as of Basis Release 31) This application
is fully integrated in SAP NetWeaver Depending on the business needs SAP business applications
are the initial trigger for scheduled activities You can now manage jobs and job chains conveniently
using a graphical user interface
System Landscape Directory
The System Landscape Directory is the central directory of system landscape information relevant
for the management of your software life-cycle It contains a description of your system landscape
(that is software components that are currently installed) and a repository of software components
that can theoretically be installed in your landscape (such as the software components available
from SAP)
Adaptive Computing Controller
5 System Landscape
52 Shared Services
3656 PUBLIC 2011-04-15
The Adaptive Computing Controller enables users to control an adaptive computing landscape
from a single point through observation operation and dynamic resource distribution With
adaptive computing hardware software and system services are able to adapt to changing business
needs In the Adaptive Computing Controller the run-time data of logical and physical landscapes
can be monitored application services can be startedstoppedrelocated and hardware resources
can be assigned to application services The operation can also be mass executed and be planned as
tasks to be executed
For more information about the installation of the Adaptive Computing Controller tool see the
document Installation Guide ndash Adaptive Computing Controller in SAP NetWeaver 71 available on SAP Service
Marketplace at httpservicesapcominstallNWPI71
For more information about Adaptive Computing in general see httpsdnsapcomirj
sdnadaptive
521 Use Cases
You can use the applications and tools described above for use cases that are normally performed
centrally The following sections describe these use cases
5211 End-to-End Solution Operations
Running business applications through their complete life-cycle is a challenge Therefore SAP has
started the Run SAP methodology for implementing End-to-End Solution Operations Based on a set
of SAP standards a roadmap and a package for training and certification Run SAP helps customers to
facilitate End-to-End Solution Operations
You can download the SAP standards for Solution Operations from SAP Service Marketplace at http
servicesapcomsupportstandards They describe roles customers typically have in their IT
environment For optimal role support SAP has grouped existing and new functions in SAP Solution
Manager work centers as of SAP Solution Manager 70 Support Package 15 Operations aspects are fully
covered by adding administrative functions for SAP NetWeaver as well Work centers are ABAP Web
Dynpro-based applications They offer the following advantages
Easy to use similar look and feel
Context transfer while jumping from one work center into another
Logical grouping of tools for a certain area
Simple authorization concept
Easy to expand
Each IT role belongs to one or more work centers For instance the Technical Administrator IT role is
covered by the work centers for System Monitoring System Administration and Landscape Management
The following work centers are available
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3756
Business Process Operations
Change Management
Root Cause Analysis
Implementation Upgrade
Incident Management
Test Management
Job Management
System Landscape Management
Solution Documentation Assistant
SAP Engagement and Service Delivery
SAP Solution Manager Administration
System Administration
System Monitoring
My Home is the central point of access to all important data of almost all work centers in SAP Solution
Manager
5212 Support Infrastructure
A key requirement for effective support of IT solutions is the ability to perform root cause analysis with
speed and efficiency
With SAP Solution Manager SAP has long had an infrastructure in place for its ABAP applications that
efficiently supports SAP solutions This helps ensure the high availability and smooth running of
business processes For more information see the SAP Solution Manager section
With Solution Manager Diagnostics this knowledge has been extended to Java applications If for
example homegrown Java applications cause instability Solution Manager Diagnostics helps trace the
cause to eradicate the problem rapidly Solution Manager Diagnostics is fully integrated into SAP
Solution Manager 70 Solution Manager Diagnostics also contains two third-party tools CArsquos Wily
Introscopereg for measuring performance as well as troubleshooting problems of the Java EE Engine
and applications running on it and Mercury Loadrunnerreg which enables SAP Support to produce a
defined load in the SAP solution landscape remotely For more information see Solution Manager
Diagnostics [page 43]
The support infrastructure provides SAP Support with safe access to your productive landscape for safe
root cause analysis so ensuring that SAP Support does not change your landscape inadvertently You
require a support infrastructure to run SAP NetWeaver
The following figure shows the overall infrastructure including SAP NetWeaver administration tools
that are used by administrators or operators at the customer site
5 System Landscape
52 Shared Services
3856 PUBLIC 2011-04-15
Landscape Aspects
If you use SAP NetWeaver Process Integration 71 productively besides SAP Solution Manager (as a
central support platform) you have to set up Solution Manager Diagnostics for supportability reasons
Implementation Sequence
For information about the implementation of the support infrastructure see the document Master
Guide ndash SAP Solution Manager 70 available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution Manager ltReleasegt
5213 Collection of Landscape Data
Amongst other applications and services the support infrastructure and the SAP NetWeaver
administration tools rely on system landscape data
For SAP NetWeaver PI 71 you have to run non-ABAP components in your solution landscape
Therefore the System Landscape Directory is mandatory The landscape data that is automatically
gathered by the System Landscape Directory is replicated to SAP Solution Manager There are several
topology options for the System Landscape Directory They offer different grades of availability
administration and operation effort
For more information see the System Landscape Directory section
5214 Authentication and Single Sign-On
Before implementing your system landscape plan how to implement authentication and how to
integrate different systems into a Single Sign-On landscape Single Sign-On reduces complexity for end
users saving them valuable time while also reducing administration effort for resetting passwords
thereby contributing to TCO reduction
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
5215 Integrated User and Access Management
In a system landscape containing a combination of ABAP and Java components we recommend that
you integrate your user and access management so that you can use the same user data across different
systems administer this data centrally and control access to data SAPs mature fine-grained
authorization concept allows detailed control of access rights SAP NetWeaver provides both ABAP and
Java-based user management solutions The user management solution that you use to administer
your user data depends on factors such as the type of systems that are running in your landscape
If you want to use central user administration we recommend that you run it in a non-production
system If you do not have a central user administration yet you can for example realize it in the SAP
Solution Manager system
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3956
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
522 Examples for the Overall System Landscape of Shared Services
In this section we provide examples of how shared services can be set up depending on the system
landscape they are intended for The following examples aggregate the landscape aspects given in the
Use Cases section
NOTE
The following sections and the figure mostly do not show information about the life-cycle of
shared services For example you may also need a development and testquality assurance system
for SAP Solution Manager You should consider this aspect in addition to the information given
in this section based on your requirements
Small and MediumndashSized Customer Landscapes with Java
As you use Java productively for SAP NetWeaver PI 71 besides SAP Solution Manager you have to set
up additional components for optimal monitoring administration and support Solution Manager
Diagnostics and the central mode of SAP NetWeaver Administrator are already fully integrated into
SAP Solution Manager 70 as the central operations hub For SAP Process Integration you must also
set up SAP NetWeaver Administrator with a special role
We recommend that you do not install SAP Central Process Scheduling in the SAP Solution Manager
system You have to set up and operate the system which hosts your productive scheduler as a mission
critical system
In the SAP Solution Manager system you should set up a local System Landscape Directory in addition
to a central runtime System Landscape Directory This way you have a clear separation between your
management system (SAP Solution Manager) and managed systems in your landscape In addition
SAP Solution Manager then does not rely on a System Landscape Directory running in the production
environment For this setup configure the SLD data suppliers of your SAP Solution Manager system
to send data to the central runtime System Landscape Directory In addition configure automatic
bridge forwarding from your runtime System Landscape Directory to the local System Landscape
Directory For more information see the Planning Guide - System Landscape Directory
If you want to use a central system for Adobe Document Services we recommend that you install a
dedicated system for this purpose in your production environment For detailed information about
the sizing of the system for the different use cases see the Sizing Guide for Adobe Document Services at
SAP Service Marketplace at httpservicesapcomsizing Sizing Guidelines Solutions amp
Platform
We recommend that you start with this centralized SAP Solution Manager approach as depicted in the
following figure
5 System Landscape
52 Shared Services
4056 PUBLIC 2011-04-15
Figure 7 Single SAP Solution Manager Landscape
Large Customer Landscapes with Java
Large customers who have environments in their landscape that are large and distributed administered
by different groups or separated for security reasons can consider a distributed operations setup In
addition to the centralized setup described for small- and medium-sized customers above large
customers can put parts of the central management functions on extra hosts or systems for performance
or policy reasons You have the following options for a distributed setup
You may set up an extra system or client for Central User Administration (CUA)
The Change and Transport System (CTS) can run on an extra system However it is not
performance- or data-intensive
You may set up an extra system for central CCMS monitoring Depending on the customizing
and on the landscape size central CCMS may generate a lot of system load You can connect a
separate central CCMS to SAP Solution Manager for displaying alerts in the alert inbox of the System
Monitoring work center
You can use a separate SAP NetWeaver 70 system with usage type BI together with SAP Solution
Manager This may make sense with respect to the amount of landscape management data that is
stored for reporting purposes The amount of data strongly depends on the data granularity
storage time frame and landscape size
You can easily put Wily Introscope Enterprise Manager on an separate host
Other aspects described above for small- and medium-customers (such as the setup of the System
Landscape Directory) are also valid for large customers
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4156
523 Feature Details
This section provides further information about the features described above
5231 SAP Solution Manager
SAP provides you with SAP Solution Manager as the strategic application management platform and
to enable the collaboration between you and SAP You need to install at least one productive SAP
Solution Manager in your system landscape To ensure the availability of this application management
platform an SAP Solution Manager system is technically required to install or upgrade to SAP
NetWeaver 70 or higher If you are already using SAP Solution Manager you can also use it to manage
the solution you build with SAP NetWeaver In this case we highly recommend that you update SAP
Solution Manager to the latest version
As of SAP Solution Manager 70 SP15 you can use the newly created work centers
NOTE
During the SAP system installation or upgrade process you are prompted to enter the SAP
Solution Manager key An SAP Solution Manager system is required to generate this key Without
this key the installation or upgrade process cannot continue
You may generate all needed keys for your entire system landscape (development quality
assurance and production system) in one SAP Solution Manager system In case you plan to install
several solution landscapes (for example in different countries) one SAP Solution Manager
system is still sufficient
For more information see SAP Note 805390
It is possible to install multiple SAP Solution Managers If you do so they should host separate business
solutions
If you want to reduce the risk of unavailability you should not install SAP Solution Manager as a central
component Instead you can operate a 2-system-landscape with both a test and production
environment of SAP Solution Manager (especially if you are using time-critical functions like Support
Desk) If you also develop your own content a 3-system-landscape with a development test and
production environment is recommended
For more information about SAP Solution Manager see the following table
Topic Where to Find More Information
System infrastructure scenarios installation and configuration of SAP Solution Manager
Master Guide ndash SAP Solution Manager available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution ManagerltReleasegt
Benefits and usage scenarios SAP Solution Manager ndash Learning Maps available on SAP Service Marketplace at http
5 System Landscape
52 Shared Services
4256 PUBLIC 2011-04-15
Topic Where to Find More Informationservicesapcomrkt-solman or https
servicesapcomsolutionmanager
Additional information See SAP Service Marketplace at http
servicesapcomsolutionmanager
5232 Solution Manager Diagnostics
Solution Manager Diagnostics provides efficient and safe root-cause analysis of incidents in customer
solutions powered by SAP NetWeaver It can help monitor on operating systems databases Java
application activities performance and logs It also supports the reporting of software and
configuration changes that can lead to malfunctions and errors
You must run one Solution Manager Diagnostics within your SAP solution landscape if you run
applications based on SAP NetWeaver systems with usage type AS Java Agents are responsible for
delivering the data from all productive hosts within your system landscape to the Solution Manager
Diagnostics system
CAUTION
SAP Support performs root-cause analysis on incoming incidents with Solution Manager
Diagnostics Not installing and configuring this support infrastructure results in a dramatically
reduced service level
Solution Manager Diagnostics is fully integrated into SAP Solution Manager 70
Solution Manager Diagnostics also contains Wily Introscope (Display Server and Agent part) for
measuring performance as well as to troubleshoot problems of Non-ABAP applications Wily Introscope
is heavily used for troubleshooting applications running on AS Java
SAP has signed a distribution agreement for Wily Introscope SAP customers are allowed to use this
tool in a preconfigured way
For more information about Solution Manager Diagnostics and an FAQ list see SAP Service Marketplace
at httpservicesapcomdiagnostics
5233 System Landscape Directory
The System Landscape Directory (SLD) of SAP NetWeaver is the central directory of system landscape
information relevant for the management of your software life-cycle
NOTE
Note that the abbreviation SLD is not intended to define a product since the System Landscape
Directory is part of SAP NetWeaver This abbreviation is solely intended to improve readability
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4356
The System Landscape Directory contains a description of your system landscape (that is software
components that are currently installed) and a repository of software components that can
theoretically be installed in your landscape (such as the software components available from SAP)
Since this data gets updated automatically the System Landscape Directory provides reliable and up-
to-date system landscape information with as little effort for you as possible In this way the System
Landscape Directory acts as a central information provider for SAP and third-party tools that use this
data to deliver the services you need to keep your landscape up and running
For the System Landscape Directory as part of an SAP NetWeaver PI 71 landscape consider the following
aspects
Part of SAP NetWeaver PI 71 is a new version of the System Landscape Directory It is automatically
included in every SAP NetWeaver 71 system with usage type AS Java It offers enhanced functions
such as a full automatic synchronization mechanism for all data stored in it That is both data
delivered by data suppliers and data entered or changed manually in the System Landscape
Directory can be synchronized automatically This synchronization offers the following
A fully automated mechanism so no user interaction is required and conflicts are resolved
automatically
Asynchronous propagation of information so some nodes may be down temporarily
Communication over HTTP protocol
Uni- and bi-directional synchronization
Depending on your use case the full automatic synchronization could significantly reduce manual
synchronization effort
For SAP NetWeaver PI 71 the configuration of the system landscape directory and its data suppliers
is already included in the standard implementation procedure with SAPinst For existing systems
you only have to perform some quick and easy configuration actions to start operating the system
landscape directory server in an AS Java system
For SAP NetWeaver PI 71 you have the following options concerning SLD
Option 1
Run SAP NetWeaver PI 71 against an existing SLD running on SAP NetWeaver 70 We only
recommend this for upgrades from SAP NetWeaver 70 if you have a central SLD in operation
not running on one of your PI systems
Option 2
Use the SLD included in an SAP NetWeaver PI 71 system We recommend this option for new
installations and upgrades from older releases than SAP NetWeaver 70 due to the enhanced
functions and improved performance of SLD 71
NOTE
If you already have a central SLD running on SAP NetWeaver 70 in operation you could run
two SLD versions in parallel ndash SLD running on SAP NetWeaver 71 for your PI systems and
SLD running on SAP NetWeaver 70 for all other systemsuse cases This way your SAP
5 System Landscape
52 Shared Services
4456 PUBLIC 2011-04-15
NetWeaver PI 71 systems would benefit from the new features while it would be easy to set
up and operate such an SLD landscape For this purpose you could use the new fully
automatic synchronization This feature enables the automatic forwarding of all SLD data
from an SLD running on SAP NetWeaver 70 to an SLD running on SAP NetWeaver 71 As a
result there is no need to adapt most existing systems as their SLD data suppliers could still
send their data to the central SLD In brief the following steps would be required
1 Put SLD in a PI system into operation (part of standard implementation procedure)
2 Configure PI systems to use the new SLD (part of standard implementation procedure
for new PI systems)
3 Set up the fully automatic synchronization from your old SLD to your new SLD
As soon as an upgrade or an installation of a standalone AS Java 71 system is available you
could move your central SLD also to SAP NetWeaver 71 Then you could optionally shift
your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems
Figure 8
We recommend that you use a Domain Name System (DNS) alias so that you are able to switch to
another System Landscape Directory easily For example if customers build a new landscape they
normally start with a sandbox environment Over time more and more environments are set up
Once the production environment is in place move the System Landscape Directory there To do
this you can configure a new System Landscape Directory in the production environment
synchronize it with the old System Landscape directory and switch to the new one
Topology
Apart from the considerations above the System Landscape Directory offers several topology options
with different grades of availability at the expense of low administration and operation effort There is
no generic rule therefore on how to set up a System Landscape Directory in your system landscape
To find the topology and synchronization strategy for the System Landscape Directory that fits your
requirements concerning the System Landscape Directory availability (and hence the availability of
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4556
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
This page is left blank for documents that are printed on both sides
1 Introduction
This Master Guide provides you with a central starting point for the technical implementation of SAP
NetWeaverreg Process Integration (SAP NetWeaver PI) It also contains information about enhancement
package 1 for SAP NetWeaver Process Integration 71
SAP NetWeaver PI 71 is based on an established architecture for realizing cross-system business processes
and supporting an service-oriented architecture (SOA) The focus is on the service-based integration
of applications
Structure of the Master Guide
The Master Guide consists of the following sections
Introduction
Contains an introduction to this guide
Before You Start
Contains information about this document important things which you need to know before you
start and information on how to access the SAP Library
SAP NetWeaver Overview
Describes the building blocks of SAP NetWeaver PI
SOA-Based Integration Use Case
Introduces the use case and explains how to install it
System Landscape
Contains information about how to install your system landscape
Reference
Contains information about the overall documentation concept for SAP systems
CAUTION
Make sure you have the latest version of the Master Guide by checking SAP Service Marketplace
immediately before starting the installation
The Master Guide is regularly updated on SAP Service Marketplace at http
servicesapcominstallnwpi71 Planning
Constraints
The business scenarios that are presented here serve as examples of how you can use SAP software in
your company The business scenarios are intended only as models and do not necessarily run the way
they are described here in your customer-specific system landscape Check your requirements and
systems to determine whether these scenarios can be used productively at your site Furthermore we
1 Introduction
2011-04-15 PUBLIC 956
recommend that you test these scenarios thoroughly in your test systems to ensure that they are
complete and free of errors before going live
1 Introduction
1056 PUBLIC 2011-04-15
2 Before You Start
21 SAP Notes
You must read the following SAP Notes before you use this Master Guide and implement SAP NetWeaver
Make sure that you have the up-to-date version of each SAP Note which you can find on SAP Service
Marketplace at httpservicesapcomnotes
NOTE
The SAP Notes related to SAP NetWeaver PI 71 are also listed on SAP Service Marketplace at
httpservicesapcomsapnotesnwpi71
List of Important SAP Notes
SAP Note Number Title Description
1004107 Release Restrictions for SAP NetWeaver PI 71
Some restrictions apply to the productive use of SAP NetWeaver PI 71 These are documented in this SAP Note
1247043 Release Restrictions for SAP EHP1 for SAP NetWeaver PI 71
Some restrictions apply to the productive use of enhancement package 1 for SAP NetWeaver PI 71 These are documented in this SAP Note
22 More Information
The following table contains links to information available on SAP Service Marketplace or in the SAP
Library which is important for implementing SAP NetWeaver
Content Location on SAP Service Marketplace or in SAP Library
The latest version of the installation and upgrade guides for SAP NetWeaver Process Integration
httpservicesapcominstguidesnwpi71
Information about supported platforms (operating systems databases browsers) for all SAP NetWeaver components
httpservicesapcomplatforms Product Availability Matrix
Sizing of SAP NetWeaver httpservicesapcomsizing
Information about security SAP Security Guide See the SAP Library [page 12] at Adminitstratoracutes Guide Security Guide
Information about the technical operation of SAP NetWeaver
Technical Operations Manual See the SAP Library [page 12] at Adminitstratoracutes Guide Technical Operations for SAP NetWeaver
2 Before You Start
21 SAP Notes
2011-04-15 PUBLIC 1156
Content Location on SAP Service Marketplace or in SAP Library
Information about SAP NetWeaver PI Support Package Stacks
httpservicesapcomnetweaver SAP NetWeaver PI 71- Release-Specific Information Support Package Stacks Information
Information about installing SAP NetWeaver Support Package Stacks
httpservicesapcomMaintenanceNWPI71
Support Package Stack Guide ndash SAP NetWeaver
23 Accessing the SAP Library
For more information about SAP NetWeaver Process Integration access the SAP Library from any of
the following
SAP Help Portal at httphelpsapcomNWPI71 SAP NetWeaver Process Integration 71 Library
ltLanguagegt SAP NetWeaver Process Integration Library
CAUTION
The SAP Help Portal contains the latest version of the SAP Library Therefore we recommend
that you use this channel to access the SAP Library
An SAP system if you have installed the online documentation Choose Help SAP Library
The browser starts
The help files on the online documentation CDs or DVDs
If you want to view the help files in HTMLHelp format from the online documentation CDs or
DVDs you need a PC running Microsoft Windows to install the HTMLHelp Viewer
2 Before You Start
23 Accessing the SAP Library
1256 PUBLIC 2011-04-15
3 SAP NetWeaver PI Overview
Introduction
SAP NetWeaver PI 71 is part of the SAP NetWeaver technology platform The complete offering of the
SAP NetWeaver technology platform is visualized in the SAP NetWeaver technology map which you
can access at httpsdnsapcomnetweaver SAP NetWeaver at a Glance The technology map
enables you to drill down from top-level technology areas (for example Lifecycle Management) to
individual capabilities (for example Administration Monitoring and so on)
SAP NetWeaver PI includes the following capabilities
Repository-based Modeling and Design
Service Bus-based Integration
SOA Management
A different view is introduced by the end-to-end use case concept This concept offers an
implementation view on SAP NetWeaver to structure and facilitate your implementation
A use cases is a process that typically involves several SAP NetWeaver capabilities It is not limited to a
single component or capability A use case guides you through the different phases of your
implementation project ndash from information through installation to the configuration phase This
implies that a uses case addresses several user roles administrator power user and end user
This document describes the SOA-based integration use case
Architecture Principals
The architecture of SAP NetWeaver Process Integration 71 (SAP NetWeaver PI 71) is based on an
established architecture for realizing cross-system business processes and is a further development of
lower releases (SAP NetWeaver 70 usage type Process Integration and SAP XI 30 as part of SAP
NetWeaver 2004) SAP NetWeaver PI 71 plays an important role in supporting an service-oriented
architecture (SOA) The focus is on the service-based integration of applications
SAP NetWeaver PI is based on general standards so as to enable 3rd-party systems to be integrated At
the center of SAP NetWeaver PI is an XML-based communication that uses HTTP (Hyper Text Transfer
Protocol) Irrespective of the scenario used the application-specific contents are transferred in messages
in user-defined XML (eXtensible Markup Language) from the sender to the receiver either via the
Integration Server or directly between the systems involved
The following figure gives an overview of the key capabilities of SAP NetWeaver Process Integration
3 SAP NetWeaver PI Overview
2011-04-15 PUBLIC 1356
Figure 1 SAP NetWeaver PI Key Capabilities Overview
SAP NetWeaver Process Integration 71 enables the integration of the applications of the following
communication parties
B2B Party Any business partners that want to integrate their application with other applications
outside their own system landscape Scenarios that require industry standards are supported as
well as any scenarios that do not adhere to a particular industry standard
SAP Applications that run on SAP systems This includes the processing of events by using the
Business Activity Monitoring (BAM) infrastructure
3rd-Party Application Applications from 3rd-party providers within one system landscape for
example database or file-system-based
3rd-Party Middleware Middleware systems from 3rd-party providers that are required for the
integration of applications within a company and across company boundaries
SAP NetWeaver PI also supports internal company scenarios and cross-company scenarios It enables
you to connect systems from different vendors (non-SAP and SAP) in different versions and
implemented in different programming languages (Java ABAP and so on) to each other Like the rest
of the SAP NetWeaver platform SAP NetWeaver PI is based on an open architecture uses open standards
(in particular those from the XML and Java environments) and offers those services that are essential
in a heterogeneous and complex system landscape
To enable end-to-end SOA development SAP NetWeaver Process Integration 71 offers a Universal
Description Discovery and Integration (UDDI) v3-based Services Registry where providers can publish
service endpoints definitions and associated metadata and consumers can discover the appropriate
services for their scenarios The Services Registry provides capabilities for classifying and browsing
3 SAP NetWeaver PI Overview
1456 PUBLIC 2011-04-15
services using semantic-rich classification systems The Services Registry is part of Application Server
Java (AS Java)
31 Installable Software Units
SAP NetWeaver comprises the following three types of installable software units
Systems that are configured for a specific purpose as indicated by one or more usage types
Standalone engines that provide one specific (server) function in combination with one or more
SAP NetWeaver PI systems
Clients used by (many) people from their local front-end PC to access functions offered by systems
of SAP NetWeaver PI or standalone engines in the system landscape
In the following sections you can find more details about the software units The figure below provides
and overview of the software units
Figure 2 Installable Software Units for SAP NetWeaver PI
For this and other figures in this guide the following legend applies
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1556
Figure 3 Legend
311 Systems with Usage Types
SAP systems are the main building blocks of SAP NetWeaver They are identified by unique SAP system
IDs (SAPSIDs) and configured for a certain purpose as indicated by usage types Usage types have the
following characteristics
They are a structuring element for SAP software on a technical level
Usage Types determine the intended purpose of a system and the role it plays in a given (distributed)
use case
They are realized by installing and configuring a collection of software components
They allow a logical view of the technology platform SAP NetWeaver PI
A usage type may require other usage types in the same system to operate
They can also be run in the same system together with other usage types that are not a prerequisite
How SAP NetWeaver Systems are Used
The following sections describe the usage types and their dependencies for SAP NetWeaver PI
Application Server ABAP (AS ABAP)
Purpose
AS ABAP is used to provide the ABAP foundation of SAP NetWeaver PI
Application Server ABAP provides a complete development and runtime environment for ABAP-based
applications It is optimized for the development of highly scalable business applications The ABAP
development and runtime environment makes it possible to develop complex business applications
3 SAP NetWeaver PI Overview
31 Installable Software Units
1656 PUBLIC 2011-04-15
without having to worry explicitly about technical details such as process or memory administration
multi-user capability database connections or similar issues These are provided in the basis services or
are integrated directly in the ABAP runtime The application development is similarly independent of
the underlying platform The application server decouples the application coding completely from the
operating system and database that are used
Dependencies
AS ABAP can be combined optionally with other usage types in one system
Application Server Java (AS Java)
Purpose
AS Java is used to provide the Java foundation of SAP NetWeaver PI using the Java Engine a Java EE-
compliant application server for running enterprise applications In addition to the pure Java EE
standard technologies the Java Engine implements complementary technologies such as Web Dynpro
or Web Services that are targeted at supporting large-scale real-business application development
projects
Dependencies
AS Java can be combined optionally with other usage types in one system
Process Integration (PI)
Purpose
PI consists of core components that model design automate and integrate processes in one or more
application systems For the integration of internal and cross-company processes PI is used to
incorporate all the functions of what was formerly known as Exchange Infrastructure (XI) In addition
PI contains core components for Business Process Management for application-embedded and
application-unbounded processes
The Advanced Adapter Engine is also part of usage type PI You use Advanced Adapter Engine to connect
to SAP systems (RFC adapter) and external systems You use the various adapters in Advanced Adapter
Engine to convert XML- and HTTP-based messages to the specific protocol and format required by
these systems and the other way around You can use the Advanced Adapter Engine that is part of
your PI system as a central Advanced Adapter Engine Optionally (for performance reasons) you can
install a non-central Advanced Adapter Engine [page 19] separately as a system with AS Java and parts of the
usage type PI on a separate host
Dependencies
PI requires AS ABAP and AS Java as prerequisites in the same system
For installing PI it is mandatory to have a dedicated PI system This applies to development quality
and production landscapes It is a prerequisite that no other system in your system landscape has a
higher release and enhancement package level than the PI system If you want to upgrade or install an
application in your system landscape you first have to make sure that the current release and
enhancement package level of the PI system is on the same level - if required you have to upgrade the
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1756
PI system first to the new or a higher release In a dedicated PI system this can be accomplished with a
minimum of downtime Also the PI system would not be affected by the downtime of other usage
types running in the same system
Configuration of Systems with Usage Types
Configuration information is available in the installation guides the configuration wizard and SAP
Solution Manager
In the Installation Guide ndash SAP NetWeaver PI 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt you find
initial technical configuration tasks This guide also informs you about how you can run the
configuration wizard and how you can access the configuration information in SAP Solution
Manager
For certain usage types configuration tasks can be applied by the configuration wizard after the
installation To do this you start the configuration wizard from SAP NetWeaver Administrator
The configuration steps for systems with usage types required for an use case are accessible through
SAP Solution Manager
To be able to use SAP Solution Manager for the configuration tasks you have to import the latest
SAP Solution Manager Implementation Content (Add-On ST-ICO) that is available for your SAP
Solution Manager release For more information see SAP Note 631042 (Release strategy for Implementation
Content (ST-ICO))
SAP Solution Manager Implementation Content is available on SAP Service Marketplace at
httpservicesapcomswdc Installations amp Upgrades Entry by Application Component SAP
Technology Components SAP Solution Manager ltReleasegt Content ST-ICO
In SAP Solution Manager you create a project and a project structure In the configuration phase
you select configuration structures with pre-delivered SAP content for your project You can find
the following different types of configuration tasks in SAP Solution Manager
Mandatory configuration tasks All configuration tasks that are mandatory for the standalone
engine or usage type
Optional configuration tasks Configuration tasks for areas where customers need to decide
if they want to use these functions (for example high availability or security settings)
Additional functions ndash configuration tasks Configuration tasks for functional units that are
used in certain use cases only
A marked checkbox in front of the configuration tasks indicates those configuration tasks that are
relevant for the use case you have chosen To configure ABAP systems SAP Solution Manager
offers executable configuration files (IMG activities)
For information about using SAP Solution Manager Content and creating a configuration guide
see the following documentation
httphelpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Implementing
and Upgrading SAP Solutions Configuration
3 SAP NetWeaver PI Overview
31 Installable Software Units
1856 PUBLIC 2011-04-15
How to Create a Configuration Guide using SAP Solution Manager available at http
servicesapcomsolutionmanager Media Library How-To Documents
Restrictions for Systems with Multiple Usage Types
If you have one system with multiple usage types be aware that we do not provide standard tools
to separate these usage types and distribute them to multiple systems at a later stage For example
if you have a system with usage types A and B you are not able to migrate it with SAP standard
tools into two systems one with usage type A only and the other with usage type B only
In addition we do not provide standard tools to merge multiple systems with different usage types
into one system with multiple usage types at a later stage
If you want to perform these tasks you require specific project support
The following figure shows that SAP standard system copy and migration tools do not support
you in separating or merging systems with usage types
Figure 4 No Support for Merging or Separating Systems with Usage Types
Although you can use one system for multiple usage types client restrictions apply for usage type
PI PI requires a dedicated client due to special PI requirements concerning the client pipeline
Whereas application client pipelines only send and receive messages the central PI pipeline can
also map messages to different formats before sending them
312 Standalone Engines
Standalone engines of SAP NetWeaver are additional installable software units They do not work as
full-blown systems of SAP NetWeaver but as standalone engines that provide a specific (server) function
in combination with one or more SAP NetWeaver systems
Standalone engines are not part of a usage type They do not run on AS ABAP or AS Java
The standalone engines that are available for SAP NetWeaver Process Integration are described in the
following
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1956
Gateway
It is possible to install an SAP instance of an SAP NetWeaver system based exclusively on a standalone
gateway This type of instance does not contain normal work process types (dialog background update
enqueue or spool) Only the gateway process (gwrd) is started If there is an SNA connection to an R
2 system gateway work processes (gwwp) are also started
SAP Conversion Agent by Informatica
SAP Conversion Agent by Informatica is a data conversion tool that enables you to create interfaces
between any data formats and XML-based systems SAP Conversion Agent can convert unstructured
semi-structured and structured formats to XML and the other way around The Conversion Agent
comprises the Conversion Agent Studio and the Conversion Agent Engine In the Conversion Agent
Studio you can develop and configure data conversions The Conversion Agent Engine executes the
data conversions
Search and Classification (TREX)
You can use Search and Classification with SAP NetWeaver PI to search for messages that were previously
indexed Message search using index provides additional methods of searching for specific messages In
addition to static header attributes you can also use adapter-specific message attributes and data from
the message payload for the search A requirement of this however is that the messages are indexed
first You can apply the index-based message search to one or all indexed components of an integration
landscape (domain) Integration Server Adapter Engines and ABAP business systems
For more information see the SAP Library [page 12] at Administratorrsquos Guide Technical Operations for SAP
NetWeaver Administration of SAP NetWeaver Systems Administering PI (Process Integration) Monitoring Index
Administration
Web Dispatcher
The Web Dispatcher lies between the Internet and your SAP system It is the entry point for HTTP(s)
requests into your system which consists of one or more SAP NetWeaver application servers As a
software web switch the Web dispatcher can reject connections or accept them When it accepts a
connection it balances the load to ensure an even distribution across the servers
You can use the Web dispatcher in ABAPJava systems and in pure Java systems as well as in pure ABAP
systems
It is also beneficial to use the Web Dispatcher if you do not need security functions (entry point in the
demilitarized zone (DMZ) SSL URL filtering) but you simply want to balance the load between
multiple SAP NetWeaver Application Server instances
Since Web Dispatcher is optional for every SAP system it is not contained in the system landscape and
the implementation sequence of the use case in this documentation
For more information see the SAP Library [page 12] at Function Oriented View Application Server Infrastructure
SAP Web Dispatcher
3 SAP NetWeaver PI Overview
31 Installable Software Units
2056 PUBLIC 2011-04-15
Advanced Adapter Engine
You use the Advanced Adapter Engine to connect to SAP systems (RFC adapter) and external systems
You use the various adapters in Advanced Adapter Engine to convert XML- and HTTP-based messages
to the specific protocol and format required by these systems and the other way around For specific
senderreceiver combinations messages can be processed without invoking the central Integration
Engine In principle you connect external systems using the adapters that are installed centrally or
non-centrally in Advanced Adapter Engine You can use the Advanced Adapter Engine that is part of
your PI system as a central Advanced Adapter Engine Optionally (for performance reasons) you can
install a non-central Advanced Adapter Engine separately as a system with AS Java and parts of the
usage type PI on a separate host
Adapter Engine (Java SE)
Adapter Engine (Java SE) is a separate software unit You can use it only if you have SAP NetWeaver
systems with usage type PI in your system landscape It has to be installed manually You use the Adapter
Engine (Java SE) to connect to external systems Using the various adapters in the Adapter Engine (Java
SE) XML and HTTP-based messages can be converted to the specific protocol and format required by
such systems and the other way around The Adapter Engine (Java SE) only provides some of these
adapters as a standalone version with restricted functions for operating systems that do not support
SAP NetWeaver PI 71 but that have at least a Java Runtime Environment 50 Therefore you should
use the Adapter Engine (Java SE) only if the platform prerequisites do not allow you to use the Advanced
Adapter Engine
SAP Partner Connectivity Kit
SAP Partner Connectivity Kit (PCK) runs on AS Java with parts of the usage type PI It enables a system
of a smaller company or subsidiary that does not run SAP NetWeaver PI to connect to your SAP
NetWeaver systems
313 Clients
Clients are additional installable programs or tools They reside either on local front-end PCs accessed
by users or on back-end systems where they act as client programs within an SAP NetWeaver system
landscape
The clients that you can use with SAP NetWeaver Process Integration are described in the following
sections
SAP GUI
NOTE
We recommend that you use the following versionsI
SAP GUI for Windows 710 (or higher) with the latest patch level
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 2156
SAP GUI for Java 710 (or higher) with the latest revision
The integrated SAP ITS 710
For more information about the SAP GUI family see SAP Service Marketplace at http
servicesapcomsapgui
SAP offers three different client applications for accessing ABAP applications in SAP systems (such as
SAP NetWeaver systems with usage type AS ABAP) This SAP GUI family consists of
SAP GUI for HTML
SAP GUI for HTML is based on the SAP integrated Internet Transaction Server (ITS) which is
included in the installation of SAP NetWeaver systems as of SAP NetWeaver 2004 On the client
side only a suitable browser (such as Internet Explorer 70 or Firefox 20) and a virtual machine are
required SAP ITS 620 is not compatible with SAP NetWeaver 71
SAP GUI for the Java environment (SAP GUI for Java)
SAP GUI for Java is a generic SAP GUI that covers a variety of platforms
For more information about the installation of SAP GUI for Java see the documentation Installation
Guide ndash SAP Front End
SAP GUI for the Windows environment (SAP GUI for Windows)
SAP GUI for Windows is SAPs universal client for accessing all SAP applications built on ABAP
technology It is available on the Microsoft Windows platform only and offers the broadest feature
set of all members of the SAP GUI family
For more information about the installation of SAP GUI for Windows see the Installation Guide ndash
SAP Front End
SAP NetWeaver Developer Studio
The SAP NetWeaver Developer Studio is SAPrsquos Integrated Development Environment (IDE) for Java
and is based on the open-source tools framework Eclipse 33 With the SAP NetWeaver Developer Studio
you can develop Java EE 5 applications from scratch using the built-in support for new technologies
such as EJB 30 and JSF 12
During the installation of the SAP NetWeaver Developer Studio several features are offered for
installation For SAP NetWeaver PI 71 only the following features are relevant
SAP NetWeaver Developer Studio Platform
SAP NetWeaver Developer Studio Java EE
NOTE
If you want to use one of the other features you need SAP NetWeaver Composition Environment
and a corresponding developers licence
For more information about the installation of SAP NetWeaver Developer Studio see the Installation
Guide ndash SAP NetWeaver Developer Studio 71 or Installation Guide ndash SAP NetWeaver Developer Studio 71 Including
Enhancement Package 1
3 SAP NetWeaver PI Overview
31 Installable Software Units
2256 PUBLIC 2011-04-15
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
SAP enhancement packages are a new way of delivering new functions for SAP NetWeaver This allows
a clear separation between the delivery of new functions on the one hand and corrections legal changes
and security updates on the other hand (in Support Package stacks) SAP enhancement packages are
cumulative an enhancement package always contains the functions of the corresponding predecessor
enhancement packages
Enhancement packages are maintained by their own Support Packages while the main release is in
maintenance
Benefits
SAP enhancement packages offer the following benefits
You have reduced effort for testing and no effort for training when applying Support Packages as
new features are only shipped with enhancement packages
Adding new functions between releases becomes predictable and controllable
New functions can be added successively in small steps There is no need to fully upgrade your
system to get new functions
You have minimal training effort when applying an enhancement package because existing
functions are not replaced
Implementation
There are the following ways to get an SAP NetWeaver system with the release level of SAP enhancement
package 1 for SAP NetWeaver Process Integration 71
New installation of SAP NetWeaver PI 71 including enhancement package 1 using the standard
installation tool SAPinst
Upgrade of an existing SAP NetWeaver system from a release lower than SAP NetWeaver PI 71 to
SAP NetWeaver PI 71 including enhancement package 1 For this you use the upgrade programs
SAPup (for ABAP) and SAPJup (for Java)
Installation of the enhancement package on an existing SAP NetWeaver PI 71 system
For this you use the Software Update Manager (SUM) The Software Update Manager evolved
from the previously used SAP Enhancement Package Installer The tool has been renamed to reflect
its broader use for example you can also use it for applying Support Package Stacks to your system
On the ABAP side the Software Update Manager uses a system cloning and switch procedure for
installing enhancement packages It installs a copy of the system the shadow system parallel to
the original system This shadow system is used to update the relevant software components and
to install the additional components while the original system is still in production operation At
a certain point during downtime the switch to the new system is made and afterwards any parts
of the original system that are no longer needed are deleted The enhancement package installation
in a Java system uses a deploy-based procedure that is no shadow system is used The Software
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2011-04-15 PUBLIC 2356
Update Manager requires a stack configuration file (xml file) as input file for the enhancement
package installation procedure This file lists all the packages that are to be installed in your systems
The stack configuration file is generated when you download the required packages
As the Software Update Manager is updated regularly we recommend to always use the latest
version It is delivered as part of the SL toolset For more information see http
servicesapcomsltoolset
For an overview of all required steps for the enhancement package installation process and
corresponding documents see Process Overview Installation of Enhancement Package 1 on an Existing SAP
Netweaver PI 71 System [page 28]
Content of SAP Enhancement Package 1 for SAP NetWeaver PI 71
With enhancement package 1 for SAP NetWeaver PI 71 new features are introduced and some existing
are changed The following is a selection of some of the most important enhancements
Enhanced design and modelling options in the Enterprise Services Repository
New services registry
Support for new Web services standard (Web Services Reliable Messaging)
New modules for the Advanced Adapter Engine
Use of shared memory of the ABAP Application Server for message processing
For more information about the changes see SAP Library [page 12] at Whatacutes new in SAP NetWeaver PI 71
ndash Release Notes
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2456 PUBLIC 2011-04-15
4 SOA-Based Integration Use Case
41 Overview
You can use SOA-based integration to set up the communication between service providers and service
consumers in both application-to-application and business-to-business scenarios and to execute
operate and monitor the communication at runtime SOA-based integration covers both direct (point-
to-point) as well as mediated (via an Integration Server) communication between service providers and
service consumers
The use case spans the whole life cycle of a SOA-based integration scenario including
Scenario modeling and service design in the Enterprise Services Repository
Implementation of the service provider and consumer in the back-end systems
Configuration and finally execution monitoring and operation of the integration scenario
For scenarios using Integration Server or broker-based communication the configuration of the
different connectivity options (for example SOAP RFC Web Services Industry standards and JDBC)
and their enhancements is covered
For more information see the following documents
Service-Enabling with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdnsoa-modeling
Getting Started
Service-Enabling a Legacy Application with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdn
soa-servicebus Getting Started
In the following you will find information about the installation of the involved software units
42 System Landscape
The following figure shows the system landscape for this use case
4 SOA-Based Integration Use Case
41 Overview
2011-04-15 PUBLIC 2556
Figure 5 SOA-Based Integration
It is mandatory to have a dedicated PI system This applies to development quality and production
landscapes
For PI it is a prerequisite that no other system in your system landscape has a higher release than
the PI system For exceptions to this rule see SAP Note 1043047 For example SAP XI 30 is compatible
with SAP NetWeaver 640 and 70 application systems since the same XI protocol is used Apart
from these exceptions if you want to upgrade or install an application in your system landscape
you first have to make sure that the PI system is on the same release level If required you have to
upgrade the PI system first to the new or a higher release
CAUTION
Although it should be technically possible to run an application system with a higher release
than your PI system in your system landscape this is not supported by SAP (apart from the
exceptions listed in SAP Note 1043047) Therefore you run such a landscape at your own risk
You can use the Advanced Adapter Engine that is part of your PI system as a central Advanced
Adapter Engine
Adapter Engine (Java SE) can be installed in a non-SAP Java environment However it only hosts
a subset of the adapter functionality is only supported for compatibility reasons and should be
used only if this is a precondition in your environment
Optionally you can use the Change Management Service (CMS) of an SAP NetWeaver 70 system
with usage type DI to transport design objects and repository objects For more information see
the SAP Library [page 12] at Administratoracutes Guide Technical Operations for SAP NetWeaver Administration
of SAP NetWeaver Systems PI (Process Integration) Software Logistics Transporting ESR Content and Objects
of Integration Directory PI Transports Using the Change Management Service (CMS)
Smaller business partners or subsidiaries that do not run SAP NetWeaver install SAP Partner
Connectivity Kit in their system landscape SAP Partner Connectivity Kit enables XML document
4 SOA-Based Integration Use Case
42 System Landscape
2656 PUBLIC 2011-04-15
exchange between your SAP NetWeaver systems and the partner systems Since SAP Partner
Connectivity Kit gets installed in their system landscape it is not shown in the system landscape
figure above
The AS ABAP system acts as an application and service provider For Java Web Services you also
require AS Java In addition you require SAP NetWeaver Developer Studio on the client side as a
development environment
The Web service client can be either an SAP or a non-SAP application For example an AS ABAP
system or a Web browser could act as application or service consumer
You can install SAP Conversion Agent by Informatica in the system with usage type PI or on a host
where SAP Partner Connectivity Kit is installed or on a host where neither usage type PI nor SAP
Partner Connectivity Kit is installed
43 Implementation Sequence
Procedure
To install this use case perform the steps listed in the following table
StepAction[Corresponding Documentation] Remarks
1 Make sure that you have performed the preparation steps You have planned your system landscape [page 33]
(that is you have decided how many systems you require how you want to use each of these systems and which standalone engines and clients you require)
With the help of your hardware partner you have mapped your systems and standalone engines to properly sized hosts
You have planned and installed shared services [page 35]
2 Installation of system with usage type PI (includes the installation of AS ABAP and AS Java)
NOTE
For usage type PI a Unicode installation is mandatory
[Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt]
If you want to use the features of enhancement package 1 use the direct installation of SAP NetWeaver PI 71 including enhancement package 1
Make sure that you perform the configuration steps as described in the installation guide For certain usage types configuration tasks can be applied by the configuration wizard These configuration tasks as well as any additional configuration steps for your use case are listed in SAP Solution Manager For more information
4 SOA-Based Integration Use Case
43 Implementation Sequence
2011-04-15 PUBLIC 2756
StepAction[Corresponding Documentation] Remarks
see the Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt
3 Install the Adapter Engine (Java SE) engines if required[Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
4 To integrate small business partners and subsidiaries the business partners or subsidiaries install SAP Partner Connectivity Kit running on AS Java with parts of usage type PI in the business partners or subsidiarys system landscape[Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
5 Install SAP Conversion Agent by Informatica if required[SAP Library [page 12] at Function-Oriented View Process Integration SAP Conversion Agent by Informatica Deploying and Using Conversion Agent ]
6 Installation of clients SAP GUI
[Installation Guide ndash SAP Front End]
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
The process sequences give a comprehensive overview of the steps relevant for the enhancement
package installation on an existing SAP NetWeaver PI 71 system
The process sequence is divided into a planning phase and an implementation phase Each step in both
phases contains references to the corresponding documentation to ensure that you can easily find the
information you need
Process
NOTE
To download the enhancement package files and required Support Packages you require the SAP
Solution Manager Maintenance Optimizer You have the following options
Manual Selection
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2856 PUBLIC 2011-04-15
You manually select the required files from SAP Service Marketplace at http
servicesapcomswdc using the SP Stack Application You use the Maintenance Optimize
only to approve the packages which is a prerequisite for the download
Automatic Calculation
The Maintenance Optimizer supports the download of a consistent queue that includes all
necessary Support Packages and enhancement packages In addition SAP Solution Manager
calculates a valid import queue for the selected SAP system and generates the enhancement
package stack configuration file that you require for the installation
As a prerequisite the system that you want to update needs to be maintained correctly in
SAP Solution Manager System Landscape As the Maintenance Optimizer uses this data for
the calculation it is crucial that the data is up-to-date In addition the SAP Solution Manager
system requires a Minimum Support Package level (see below)
Planing PhaseStep Description Documentation
Hardware amp Software Prerequisites
Check which platforms are supported for your target release (OSDB dependencies)
Product Availability Matrix (PAM) at httpservicesapcompam
Check which hardware sizing is required for your target release
Sizing information at httpservicesapcomsizing
Solution Manager Prerequisites
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of the required software packages you have to make sure that your SAP Solution Manager system has the required Support Package levelAt least SAP Solution Manager 70 EHP1 Support Package Stack 17 is required We recommend to use SAP Solution Manager 70 EHP1 Support Package Stack 23Check if you need to do an update or upgrade of your SAP Solution ManagerMake sure that you run the guided procedure SOLMAN_SETUP after every installation or update of SAP Solution Manager and that it completes successfully
For upgrades from source release SAP Solution Manager 31 and 32Upgrade Guide ndash SAP Solution Manager 70 incl Enhancement Package 1For updates from SAP Solution Manager 70Update Guide SAP Enhancement Package 1 for SAP Solution Manager 70Follow-up activities after an Support Package Stack update or enhancement package updateSolution Operations Guide ndash SAP Solution Manager 70 EHP1 section Software Change Management All guides are available at http
servicesapcom instguides SAP Components SAP Solution Manager -gt Release 70 EHP 1
Implementation PhaseStep Description Documentation
1Solution Manager Preparation
Configure the SAP Solution Manager Maintenance Optimizer
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of software packages make sure your
Configuration of Maintenance Optimizer http
helpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Change Request Management and Change ControlMaintenance Optimizer
Prerequisites
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 2956
Implementation PhaseStep Description Documentation
system landscape data in SAP Solution Manager is maintained correctlyLandscape Verification 10 which is an add-on to SAP Solution Manager can support you in maintaining your system landscape data The use of this tool is optional
Landscape Verification http
wwwsdnsapcom irj
sdn alm-update-
management link Landscape Verification under Related Areas on Upgrade and Update Management (in the right column)
SAP Note 1468605 (Installation of Landscape Verification)
Maintaining System Landscape Information [page 47]Note that the information provided in this section is based on SAP Solution Manager 70 EHP1 SP23
2System Preparation
Prepare your system as described in the documentation for example perform OS DB specific preparations and the PI-specific preparations
Update Guide ndash Update of SAP Systems with Software Update Manager sections Planning and Preparation
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
3Software Download
Select and download the software packages in either of the following ways Automatic calculation Create
a maintenance transaction in the Maintenance Optimizer and choose the Calculate Files Automatically option
Manual Selection Create a maintenance transaction in the Maintenance Optimizer and choose the Select Files Manually option You then can select the files manually using the SP Stack application in SAP Service Marketplace
NOTE
You have to download the stack configuration file manually after you have selected all files in the SP Stack
httphelpsapcom SAP Solutions SAP Solution Manager
SAP Solution Manager 70 EHP1 ltSPgtChange Request Management and
Change Control Maintenance Optimizer Maintenance Procedure Scenarios
For information about the automatic calculation see Maintenance Transaction with Installation of an Enhancement PackageFor information about the manual selection and approval process see section Approve and Download Files in Download Basket
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
3056 PUBLIC 2011-04-15
Implementation PhaseStep Description Documentation
application Choose Generate Stack XML and save the file
4Enhancement Package Installation
Run Software Update Manager to update your system with the selected software packages
Update Guide ndash Update of SAP Systems with Software Update Manager
5Follow-Up Steps
Perform technical and PI-specific follow-up activities after the enhancement package installation is done
Update Guide ndash Update of SAP Systems with Software Update Manager section Follow-Up Activities
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
6Configuration
Configure newly installed enhancement package functions using SAP Solution Manager content
See Systems with Usage Types [page 16] section Configuration of Systems with Usage Types
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 3156
This page is left blank for documents that are printed on both sides
5 System Landscape
51 Planning Your System Landscape
The installable software units that make up your system landscape depend on the functions that you
want to implement For information about the features see systems [page 16] standalone engines [page 19]
and clients [page 21]
In addition you have to determine the required shared services [page 35] (such as SAP Solution Manager
or SAP NetWeaver Administrator) that run on central systems in your system landscape and the
landscape aspects relevant for their implementation
In the following you will find general information that you should consider when planning your system
landscape
Sizing
You have to map systems and standalone engines to hosts after you have a clear picture of the following
Which systems and standalone engines you require
How many systems you require and how you want to use each of these systems
NOTE
No general guideline can be given for the sizing of your landscape since this relies heavily on your
requirements You should therefore perform this task together with your hardware partner and
your technical consultant
For information about sizing your systems you can use the following information sources
Your first point of reference is the Quick Sizer
SAP built the Quick Sizer as an online sizing questionnaire Internet application in close cooperation
with its hardware partners This tool delivers general sizing categories based on your volume load
estimates The results provide an objective basis for sizing independent of platform and
configuration
For more information see SAP Service Marketplace at
httpservicesapcomsizing for the SAP NetWeaver PI 71 sizing guide available under
Sizing Guidelines Business Suite amp Services
httpservicesapcomquicksizer for more information and access to the tool itself
Also consider the following important aspects concerning sizing
High availability
5 System Landscape
51 Planning Your System Landscape
2011-04-15 PUBLIC 3356
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Technical Infrastructure High Availability
Unicode
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Internationalization
Contact your hardware partner to find out the appropriate number of sized hosts
The platform-independent abstract results of the Quick Sizer can be used by any of our hardware
partners to create a concrete offer SAP itself does not make any hardware recommendations the
responsibility for sizing and detailed hardware configuration lies with the hardware partners
Figure 6 Example of Mapping of Systems and Standalone Engines to Three Hosts
NOTE
Optionally you could also distribute single systems to multiple hosts For example you could
decide to install the database instance of an SAP system on a separate host for performance
reasons or distribute other system instances to achieve high availability
To provide a mapping that fits your required functions and performance your hardware partner
and your technical consultant have to identify the number of required instances of SAP NetWeaver
find out how to distribute these instances to hosts and what functions will run on which instance
Therefore the hardware partner and the technical consultant have to consider many different
aspects such as
Number of required SAPS (SAP Application Benchmark Performance Standard) for each
system (provided by Quick Sizer)
Landscape-relevant aspects concerning security For more information see the SAP Security
Guide in the SAP Library [page 12] at Administratoracutes Guide Security Guide
Landscape-relevant aspects concerning scalability high availability operation and software
life-cycle management
5 System Landscape
51 Planning Your System Landscape
3456 PUBLIC 2011-04-15
For more information about relevant aspects for the mapping of systems to hosts see the document
Technical Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
Scaling and Distribution Options
You may need to design your system landscape for a large number of users SAP NetWeaver PI offers
you different means of scalability The following list provides you with some examples
You could install multiple systems of one type and use them for different purposes
You could scale every system by installing dialog instances or by distributing the database instance
For more information about distribution options on the instance level see the Technical
Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
For every SAP system you could additionally install Web Dispatcher For more information see
the SAP Library [page 12] at FunctionndashOriented View Application Server Infrastructure SAP Web
Dispatcher
You could further distribute certain standalone engines ndash for example Search and Classification
(TREX) is based on a flexible architecture that supports a distributed installation For more
information see the Technical Infrastructure Guide ndash SAP NetWeaver PI 71 available in SAP Service
Marketplace at httpservicesapcominstallNWPI71
52 Shared Services
You normally run shared services on central systems in your system landscape The following features
could be used for SAP NetWeaver Process Integration to realize shared services
SAP Solution Manager
Used to implement train test maintain monitor control change and manage incidents of your
SAP solution system landscape (open end-to-end application management)
As of SAP Solution Manager (70) 40 Support Package 15 SAP Solution Manager has become the
platform for SAPs end-to-end solution operations strategy Functions for complete application
management has been combined with administrative tools and has been merged in newly created
role based work centers
NOTE
Be aware that you require an SAP Solution Manager system to install or upgrade to SAP
NetWeaver 70 and higher An SAP Solution Manager system is required to generate the SAP
Solution Manager key needed during the installation or upgrade process Without this key
the installation or upgrade process cannot continue
For SAP NetWeaver Process Integration you require SAP Solution Manager 70
For more information see SAP Note 805390
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3556
Solution Manager Diagnostics
An integral part of SAP Solution Manager that is running as a Java application on the Java stack of
SAP Solution Manager 70 Solution Manager Diagnostics is used to analyze the root cause of
incidents in your landscape in an efficient and safe way Before Go-Live Solution Manager
Diagnostics has to be set up and made accessible remotely
SAP NetWeaver Administrator
SAP NetWeaver Administrator is the central administration component which is used for
monitoring and administering Java applications It is included in SAP NetWeaver systems with AS
Java
SAP NetWeaver Administrator exists in the following flavors
A local mode which runs out of the box and which focuses on administrating the underlying
SAP NetWeaver AS Java
NOTE
For a SAP NetWeaver PI 71 it has a special role which you need to activate using a
configuation wizard
A central mode which has to be configured before use and which deals with the system
landscape management
SAP has decided to merge the central mode of SAP NetWeaver Administrator into the new work
centers available as of SAP Solution Manager 70 SP 15 Thus it can be used in an administrative
context together with non-Java-based administration tools Although the central mode of SAP
NetWeaver Administrator will be still available for some time SAP will not develop this tool any
further SAP focuses on optimizing the administrative work centers of SAP Solution Manager
instead
The local mode of SAP NetWeaver Administrator stays untouched It is available for current and
future releases of SAP NetWeaver
SAP Central Process Scheduling by Redwood
SAP Central Process Scheduling application by Redwood enables central job scheduling and job
monitoring of current and old releases of AS ABAP systems (as of Basis Release 31) This application
is fully integrated in SAP NetWeaver Depending on the business needs SAP business applications
are the initial trigger for scheduled activities You can now manage jobs and job chains conveniently
using a graphical user interface
System Landscape Directory
The System Landscape Directory is the central directory of system landscape information relevant
for the management of your software life-cycle It contains a description of your system landscape
(that is software components that are currently installed) and a repository of software components
that can theoretically be installed in your landscape (such as the software components available
from SAP)
Adaptive Computing Controller
5 System Landscape
52 Shared Services
3656 PUBLIC 2011-04-15
The Adaptive Computing Controller enables users to control an adaptive computing landscape
from a single point through observation operation and dynamic resource distribution With
adaptive computing hardware software and system services are able to adapt to changing business
needs In the Adaptive Computing Controller the run-time data of logical and physical landscapes
can be monitored application services can be startedstoppedrelocated and hardware resources
can be assigned to application services The operation can also be mass executed and be planned as
tasks to be executed
For more information about the installation of the Adaptive Computing Controller tool see the
document Installation Guide ndash Adaptive Computing Controller in SAP NetWeaver 71 available on SAP Service
Marketplace at httpservicesapcominstallNWPI71
For more information about Adaptive Computing in general see httpsdnsapcomirj
sdnadaptive
521 Use Cases
You can use the applications and tools described above for use cases that are normally performed
centrally The following sections describe these use cases
5211 End-to-End Solution Operations
Running business applications through their complete life-cycle is a challenge Therefore SAP has
started the Run SAP methodology for implementing End-to-End Solution Operations Based on a set
of SAP standards a roadmap and a package for training and certification Run SAP helps customers to
facilitate End-to-End Solution Operations
You can download the SAP standards for Solution Operations from SAP Service Marketplace at http
servicesapcomsupportstandards They describe roles customers typically have in their IT
environment For optimal role support SAP has grouped existing and new functions in SAP Solution
Manager work centers as of SAP Solution Manager 70 Support Package 15 Operations aspects are fully
covered by adding administrative functions for SAP NetWeaver as well Work centers are ABAP Web
Dynpro-based applications They offer the following advantages
Easy to use similar look and feel
Context transfer while jumping from one work center into another
Logical grouping of tools for a certain area
Simple authorization concept
Easy to expand
Each IT role belongs to one or more work centers For instance the Technical Administrator IT role is
covered by the work centers for System Monitoring System Administration and Landscape Management
The following work centers are available
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3756
Business Process Operations
Change Management
Root Cause Analysis
Implementation Upgrade
Incident Management
Test Management
Job Management
System Landscape Management
Solution Documentation Assistant
SAP Engagement and Service Delivery
SAP Solution Manager Administration
System Administration
System Monitoring
My Home is the central point of access to all important data of almost all work centers in SAP Solution
Manager
5212 Support Infrastructure
A key requirement for effective support of IT solutions is the ability to perform root cause analysis with
speed and efficiency
With SAP Solution Manager SAP has long had an infrastructure in place for its ABAP applications that
efficiently supports SAP solutions This helps ensure the high availability and smooth running of
business processes For more information see the SAP Solution Manager section
With Solution Manager Diagnostics this knowledge has been extended to Java applications If for
example homegrown Java applications cause instability Solution Manager Diagnostics helps trace the
cause to eradicate the problem rapidly Solution Manager Diagnostics is fully integrated into SAP
Solution Manager 70 Solution Manager Diagnostics also contains two third-party tools CArsquos Wily
Introscopereg for measuring performance as well as troubleshooting problems of the Java EE Engine
and applications running on it and Mercury Loadrunnerreg which enables SAP Support to produce a
defined load in the SAP solution landscape remotely For more information see Solution Manager
Diagnostics [page 43]
The support infrastructure provides SAP Support with safe access to your productive landscape for safe
root cause analysis so ensuring that SAP Support does not change your landscape inadvertently You
require a support infrastructure to run SAP NetWeaver
The following figure shows the overall infrastructure including SAP NetWeaver administration tools
that are used by administrators or operators at the customer site
5 System Landscape
52 Shared Services
3856 PUBLIC 2011-04-15
Landscape Aspects
If you use SAP NetWeaver Process Integration 71 productively besides SAP Solution Manager (as a
central support platform) you have to set up Solution Manager Diagnostics for supportability reasons
Implementation Sequence
For information about the implementation of the support infrastructure see the document Master
Guide ndash SAP Solution Manager 70 available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution Manager ltReleasegt
5213 Collection of Landscape Data
Amongst other applications and services the support infrastructure and the SAP NetWeaver
administration tools rely on system landscape data
For SAP NetWeaver PI 71 you have to run non-ABAP components in your solution landscape
Therefore the System Landscape Directory is mandatory The landscape data that is automatically
gathered by the System Landscape Directory is replicated to SAP Solution Manager There are several
topology options for the System Landscape Directory They offer different grades of availability
administration and operation effort
For more information see the System Landscape Directory section
5214 Authentication and Single Sign-On
Before implementing your system landscape plan how to implement authentication and how to
integrate different systems into a Single Sign-On landscape Single Sign-On reduces complexity for end
users saving them valuable time while also reducing administration effort for resetting passwords
thereby contributing to TCO reduction
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
5215 Integrated User and Access Management
In a system landscape containing a combination of ABAP and Java components we recommend that
you integrate your user and access management so that you can use the same user data across different
systems administer this data centrally and control access to data SAPs mature fine-grained
authorization concept allows detailed control of access rights SAP NetWeaver provides both ABAP and
Java-based user management solutions The user management solution that you use to administer
your user data depends on factors such as the type of systems that are running in your landscape
If you want to use central user administration we recommend that you run it in a non-production
system If you do not have a central user administration yet you can for example realize it in the SAP
Solution Manager system
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3956
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
522 Examples for the Overall System Landscape of Shared Services
In this section we provide examples of how shared services can be set up depending on the system
landscape they are intended for The following examples aggregate the landscape aspects given in the
Use Cases section
NOTE
The following sections and the figure mostly do not show information about the life-cycle of
shared services For example you may also need a development and testquality assurance system
for SAP Solution Manager You should consider this aspect in addition to the information given
in this section based on your requirements
Small and MediumndashSized Customer Landscapes with Java
As you use Java productively for SAP NetWeaver PI 71 besides SAP Solution Manager you have to set
up additional components for optimal monitoring administration and support Solution Manager
Diagnostics and the central mode of SAP NetWeaver Administrator are already fully integrated into
SAP Solution Manager 70 as the central operations hub For SAP Process Integration you must also
set up SAP NetWeaver Administrator with a special role
We recommend that you do not install SAP Central Process Scheduling in the SAP Solution Manager
system You have to set up and operate the system which hosts your productive scheduler as a mission
critical system
In the SAP Solution Manager system you should set up a local System Landscape Directory in addition
to a central runtime System Landscape Directory This way you have a clear separation between your
management system (SAP Solution Manager) and managed systems in your landscape In addition
SAP Solution Manager then does not rely on a System Landscape Directory running in the production
environment For this setup configure the SLD data suppliers of your SAP Solution Manager system
to send data to the central runtime System Landscape Directory In addition configure automatic
bridge forwarding from your runtime System Landscape Directory to the local System Landscape
Directory For more information see the Planning Guide - System Landscape Directory
If you want to use a central system for Adobe Document Services we recommend that you install a
dedicated system for this purpose in your production environment For detailed information about
the sizing of the system for the different use cases see the Sizing Guide for Adobe Document Services at
SAP Service Marketplace at httpservicesapcomsizing Sizing Guidelines Solutions amp
Platform
We recommend that you start with this centralized SAP Solution Manager approach as depicted in the
following figure
5 System Landscape
52 Shared Services
4056 PUBLIC 2011-04-15
Figure 7 Single SAP Solution Manager Landscape
Large Customer Landscapes with Java
Large customers who have environments in their landscape that are large and distributed administered
by different groups or separated for security reasons can consider a distributed operations setup In
addition to the centralized setup described for small- and medium-sized customers above large
customers can put parts of the central management functions on extra hosts or systems for performance
or policy reasons You have the following options for a distributed setup
You may set up an extra system or client for Central User Administration (CUA)
The Change and Transport System (CTS) can run on an extra system However it is not
performance- or data-intensive
You may set up an extra system for central CCMS monitoring Depending on the customizing
and on the landscape size central CCMS may generate a lot of system load You can connect a
separate central CCMS to SAP Solution Manager for displaying alerts in the alert inbox of the System
Monitoring work center
You can use a separate SAP NetWeaver 70 system with usage type BI together with SAP Solution
Manager This may make sense with respect to the amount of landscape management data that is
stored for reporting purposes The amount of data strongly depends on the data granularity
storage time frame and landscape size
You can easily put Wily Introscope Enterprise Manager on an separate host
Other aspects described above for small- and medium-customers (such as the setup of the System
Landscape Directory) are also valid for large customers
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4156
523 Feature Details
This section provides further information about the features described above
5231 SAP Solution Manager
SAP provides you with SAP Solution Manager as the strategic application management platform and
to enable the collaboration between you and SAP You need to install at least one productive SAP
Solution Manager in your system landscape To ensure the availability of this application management
platform an SAP Solution Manager system is technically required to install or upgrade to SAP
NetWeaver 70 or higher If you are already using SAP Solution Manager you can also use it to manage
the solution you build with SAP NetWeaver In this case we highly recommend that you update SAP
Solution Manager to the latest version
As of SAP Solution Manager 70 SP15 you can use the newly created work centers
NOTE
During the SAP system installation or upgrade process you are prompted to enter the SAP
Solution Manager key An SAP Solution Manager system is required to generate this key Without
this key the installation or upgrade process cannot continue
You may generate all needed keys for your entire system landscape (development quality
assurance and production system) in one SAP Solution Manager system In case you plan to install
several solution landscapes (for example in different countries) one SAP Solution Manager
system is still sufficient
For more information see SAP Note 805390
It is possible to install multiple SAP Solution Managers If you do so they should host separate business
solutions
If you want to reduce the risk of unavailability you should not install SAP Solution Manager as a central
component Instead you can operate a 2-system-landscape with both a test and production
environment of SAP Solution Manager (especially if you are using time-critical functions like Support
Desk) If you also develop your own content a 3-system-landscape with a development test and
production environment is recommended
For more information about SAP Solution Manager see the following table
Topic Where to Find More Information
System infrastructure scenarios installation and configuration of SAP Solution Manager
Master Guide ndash SAP Solution Manager available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution ManagerltReleasegt
Benefits and usage scenarios SAP Solution Manager ndash Learning Maps available on SAP Service Marketplace at http
5 System Landscape
52 Shared Services
4256 PUBLIC 2011-04-15
Topic Where to Find More Informationservicesapcomrkt-solman or https
servicesapcomsolutionmanager
Additional information See SAP Service Marketplace at http
servicesapcomsolutionmanager
5232 Solution Manager Diagnostics
Solution Manager Diagnostics provides efficient and safe root-cause analysis of incidents in customer
solutions powered by SAP NetWeaver It can help monitor on operating systems databases Java
application activities performance and logs It also supports the reporting of software and
configuration changes that can lead to malfunctions and errors
You must run one Solution Manager Diagnostics within your SAP solution landscape if you run
applications based on SAP NetWeaver systems with usage type AS Java Agents are responsible for
delivering the data from all productive hosts within your system landscape to the Solution Manager
Diagnostics system
CAUTION
SAP Support performs root-cause analysis on incoming incidents with Solution Manager
Diagnostics Not installing and configuring this support infrastructure results in a dramatically
reduced service level
Solution Manager Diagnostics is fully integrated into SAP Solution Manager 70
Solution Manager Diagnostics also contains Wily Introscope (Display Server and Agent part) for
measuring performance as well as to troubleshoot problems of Non-ABAP applications Wily Introscope
is heavily used for troubleshooting applications running on AS Java
SAP has signed a distribution agreement for Wily Introscope SAP customers are allowed to use this
tool in a preconfigured way
For more information about Solution Manager Diagnostics and an FAQ list see SAP Service Marketplace
at httpservicesapcomdiagnostics
5233 System Landscape Directory
The System Landscape Directory (SLD) of SAP NetWeaver is the central directory of system landscape
information relevant for the management of your software life-cycle
NOTE
Note that the abbreviation SLD is not intended to define a product since the System Landscape
Directory is part of SAP NetWeaver This abbreviation is solely intended to improve readability
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4356
The System Landscape Directory contains a description of your system landscape (that is software
components that are currently installed) and a repository of software components that can
theoretically be installed in your landscape (such as the software components available from SAP)
Since this data gets updated automatically the System Landscape Directory provides reliable and up-
to-date system landscape information with as little effort for you as possible In this way the System
Landscape Directory acts as a central information provider for SAP and third-party tools that use this
data to deliver the services you need to keep your landscape up and running
For the System Landscape Directory as part of an SAP NetWeaver PI 71 landscape consider the following
aspects
Part of SAP NetWeaver PI 71 is a new version of the System Landscape Directory It is automatically
included in every SAP NetWeaver 71 system with usage type AS Java It offers enhanced functions
such as a full automatic synchronization mechanism for all data stored in it That is both data
delivered by data suppliers and data entered or changed manually in the System Landscape
Directory can be synchronized automatically This synchronization offers the following
A fully automated mechanism so no user interaction is required and conflicts are resolved
automatically
Asynchronous propagation of information so some nodes may be down temporarily
Communication over HTTP protocol
Uni- and bi-directional synchronization
Depending on your use case the full automatic synchronization could significantly reduce manual
synchronization effort
For SAP NetWeaver PI 71 the configuration of the system landscape directory and its data suppliers
is already included in the standard implementation procedure with SAPinst For existing systems
you only have to perform some quick and easy configuration actions to start operating the system
landscape directory server in an AS Java system
For SAP NetWeaver PI 71 you have the following options concerning SLD
Option 1
Run SAP NetWeaver PI 71 against an existing SLD running on SAP NetWeaver 70 We only
recommend this for upgrades from SAP NetWeaver 70 if you have a central SLD in operation
not running on one of your PI systems
Option 2
Use the SLD included in an SAP NetWeaver PI 71 system We recommend this option for new
installations and upgrades from older releases than SAP NetWeaver 70 due to the enhanced
functions and improved performance of SLD 71
NOTE
If you already have a central SLD running on SAP NetWeaver 70 in operation you could run
two SLD versions in parallel ndash SLD running on SAP NetWeaver 71 for your PI systems and
SLD running on SAP NetWeaver 70 for all other systemsuse cases This way your SAP
5 System Landscape
52 Shared Services
4456 PUBLIC 2011-04-15
NetWeaver PI 71 systems would benefit from the new features while it would be easy to set
up and operate such an SLD landscape For this purpose you could use the new fully
automatic synchronization This feature enables the automatic forwarding of all SLD data
from an SLD running on SAP NetWeaver 70 to an SLD running on SAP NetWeaver 71 As a
result there is no need to adapt most existing systems as their SLD data suppliers could still
send their data to the central SLD In brief the following steps would be required
1 Put SLD in a PI system into operation (part of standard implementation procedure)
2 Configure PI systems to use the new SLD (part of standard implementation procedure
for new PI systems)
3 Set up the fully automatic synchronization from your old SLD to your new SLD
As soon as an upgrade or an installation of a standalone AS Java 71 system is available you
could move your central SLD also to SAP NetWeaver 71 Then you could optionally shift
your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems
Figure 8
We recommend that you use a Domain Name System (DNS) alias so that you are able to switch to
another System Landscape Directory easily For example if customers build a new landscape they
normally start with a sandbox environment Over time more and more environments are set up
Once the production environment is in place move the System Landscape Directory there To do
this you can configure a new System Landscape Directory in the production environment
synchronize it with the old System Landscape directory and switch to the new one
Topology
Apart from the considerations above the System Landscape Directory offers several topology options
with different grades of availability at the expense of low administration and operation effort There is
no generic rule therefore on how to set up a System Landscape Directory in your system landscape
To find the topology and synchronization strategy for the System Landscape Directory that fits your
requirements concerning the System Landscape Directory availability (and hence the availability of
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4556
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
1 Introduction
This Master Guide provides you with a central starting point for the technical implementation of SAP
NetWeaverreg Process Integration (SAP NetWeaver PI) It also contains information about enhancement
package 1 for SAP NetWeaver Process Integration 71
SAP NetWeaver PI 71 is based on an established architecture for realizing cross-system business processes
and supporting an service-oriented architecture (SOA) The focus is on the service-based integration
of applications
Structure of the Master Guide
The Master Guide consists of the following sections
Introduction
Contains an introduction to this guide
Before You Start
Contains information about this document important things which you need to know before you
start and information on how to access the SAP Library
SAP NetWeaver Overview
Describes the building blocks of SAP NetWeaver PI
SOA-Based Integration Use Case
Introduces the use case and explains how to install it
System Landscape
Contains information about how to install your system landscape
Reference
Contains information about the overall documentation concept for SAP systems
CAUTION
Make sure you have the latest version of the Master Guide by checking SAP Service Marketplace
immediately before starting the installation
The Master Guide is regularly updated on SAP Service Marketplace at http
servicesapcominstallnwpi71 Planning
Constraints
The business scenarios that are presented here serve as examples of how you can use SAP software in
your company The business scenarios are intended only as models and do not necessarily run the way
they are described here in your customer-specific system landscape Check your requirements and
systems to determine whether these scenarios can be used productively at your site Furthermore we
1 Introduction
2011-04-15 PUBLIC 956
recommend that you test these scenarios thoroughly in your test systems to ensure that they are
complete and free of errors before going live
1 Introduction
1056 PUBLIC 2011-04-15
2 Before You Start
21 SAP Notes
You must read the following SAP Notes before you use this Master Guide and implement SAP NetWeaver
Make sure that you have the up-to-date version of each SAP Note which you can find on SAP Service
Marketplace at httpservicesapcomnotes
NOTE
The SAP Notes related to SAP NetWeaver PI 71 are also listed on SAP Service Marketplace at
httpservicesapcomsapnotesnwpi71
List of Important SAP Notes
SAP Note Number Title Description
1004107 Release Restrictions for SAP NetWeaver PI 71
Some restrictions apply to the productive use of SAP NetWeaver PI 71 These are documented in this SAP Note
1247043 Release Restrictions for SAP EHP1 for SAP NetWeaver PI 71
Some restrictions apply to the productive use of enhancement package 1 for SAP NetWeaver PI 71 These are documented in this SAP Note
22 More Information
The following table contains links to information available on SAP Service Marketplace or in the SAP
Library which is important for implementing SAP NetWeaver
Content Location on SAP Service Marketplace or in SAP Library
The latest version of the installation and upgrade guides for SAP NetWeaver Process Integration
httpservicesapcominstguidesnwpi71
Information about supported platforms (operating systems databases browsers) for all SAP NetWeaver components
httpservicesapcomplatforms Product Availability Matrix
Sizing of SAP NetWeaver httpservicesapcomsizing
Information about security SAP Security Guide See the SAP Library [page 12] at Adminitstratoracutes Guide Security Guide
Information about the technical operation of SAP NetWeaver
Technical Operations Manual See the SAP Library [page 12] at Adminitstratoracutes Guide Technical Operations for SAP NetWeaver
2 Before You Start
21 SAP Notes
2011-04-15 PUBLIC 1156
Content Location on SAP Service Marketplace or in SAP Library
Information about SAP NetWeaver PI Support Package Stacks
httpservicesapcomnetweaver SAP NetWeaver PI 71- Release-Specific Information Support Package Stacks Information
Information about installing SAP NetWeaver Support Package Stacks
httpservicesapcomMaintenanceNWPI71
Support Package Stack Guide ndash SAP NetWeaver
23 Accessing the SAP Library
For more information about SAP NetWeaver Process Integration access the SAP Library from any of
the following
SAP Help Portal at httphelpsapcomNWPI71 SAP NetWeaver Process Integration 71 Library
ltLanguagegt SAP NetWeaver Process Integration Library
CAUTION
The SAP Help Portal contains the latest version of the SAP Library Therefore we recommend
that you use this channel to access the SAP Library
An SAP system if you have installed the online documentation Choose Help SAP Library
The browser starts
The help files on the online documentation CDs or DVDs
If you want to view the help files in HTMLHelp format from the online documentation CDs or
DVDs you need a PC running Microsoft Windows to install the HTMLHelp Viewer
2 Before You Start
23 Accessing the SAP Library
1256 PUBLIC 2011-04-15
3 SAP NetWeaver PI Overview
Introduction
SAP NetWeaver PI 71 is part of the SAP NetWeaver technology platform The complete offering of the
SAP NetWeaver technology platform is visualized in the SAP NetWeaver technology map which you
can access at httpsdnsapcomnetweaver SAP NetWeaver at a Glance The technology map
enables you to drill down from top-level technology areas (for example Lifecycle Management) to
individual capabilities (for example Administration Monitoring and so on)
SAP NetWeaver PI includes the following capabilities
Repository-based Modeling and Design
Service Bus-based Integration
SOA Management
A different view is introduced by the end-to-end use case concept This concept offers an
implementation view on SAP NetWeaver to structure and facilitate your implementation
A use cases is a process that typically involves several SAP NetWeaver capabilities It is not limited to a
single component or capability A use case guides you through the different phases of your
implementation project ndash from information through installation to the configuration phase This
implies that a uses case addresses several user roles administrator power user and end user
This document describes the SOA-based integration use case
Architecture Principals
The architecture of SAP NetWeaver Process Integration 71 (SAP NetWeaver PI 71) is based on an
established architecture for realizing cross-system business processes and is a further development of
lower releases (SAP NetWeaver 70 usage type Process Integration and SAP XI 30 as part of SAP
NetWeaver 2004) SAP NetWeaver PI 71 plays an important role in supporting an service-oriented
architecture (SOA) The focus is on the service-based integration of applications
SAP NetWeaver PI is based on general standards so as to enable 3rd-party systems to be integrated At
the center of SAP NetWeaver PI is an XML-based communication that uses HTTP (Hyper Text Transfer
Protocol) Irrespective of the scenario used the application-specific contents are transferred in messages
in user-defined XML (eXtensible Markup Language) from the sender to the receiver either via the
Integration Server or directly between the systems involved
The following figure gives an overview of the key capabilities of SAP NetWeaver Process Integration
3 SAP NetWeaver PI Overview
2011-04-15 PUBLIC 1356
Figure 1 SAP NetWeaver PI Key Capabilities Overview
SAP NetWeaver Process Integration 71 enables the integration of the applications of the following
communication parties
B2B Party Any business partners that want to integrate their application with other applications
outside their own system landscape Scenarios that require industry standards are supported as
well as any scenarios that do not adhere to a particular industry standard
SAP Applications that run on SAP systems This includes the processing of events by using the
Business Activity Monitoring (BAM) infrastructure
3rd-Party Application Applications from 3rd-party providers within one system landscape for
example database or file-system-based
3rd-Party Middleware Middleware systems from 3rd-party providers that are required for the
integration of applications within a company and across company boundaries
SAP NetWeaver PI also supports internal company scenarios and cross-company scenarios It enables
you to connect systems from different vendors (non-SAP and SAP) in different versions and
implemented in different programming languages (Java ABAP and so on) to each other Like the rest
of the SAP NetWeaver platform SAP NetWeaver PI is based on an open architecture uses open standards
(in particular those from the XML and Java environments) and offers those services that are essential
in a heterogeneous and complex system landscape
To enable end-to-end SOA development SAP NetWeaver Process Integration 71 offers a Universal
Description Discovery and Integration (UDDI) v3-based Services Registry where providers can publish
service endpoints definitions and associated metadata and consumers can discover the appropriate
services for their scenarios The Services Registry provides capabilities for classifying and browsing
3 SAP NetWeaver PI Overview
1456 PUBLIC 2011-04-15
services using semantic-rich classification systems The Services Registry is part of Application Server
Java (AS Java)
31 Installable Software Units
SAP NetWeaver comprises the following three types of installable software units
Systems that are configured for a specific purpose as indicated by one or more usage types
Standalone engines that provide one specific (server) function in combination with one or more
SAP NetWeaver PI systems
Clients used by (many) people from their local front-end PC to access functions offered by systems
of SAP NetWeaver PI or standalone engines in the system landscape
In the following sections you can find more details about the software units The figure below provides
and overview of the software units
Figure 2 Installable Software Units for SAP NetWeaver PI
For this and other figures in this guide the following legend applies
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1556
Figure 3 Legend
311 Systems with Usage Types
SAP systems are the main building blocks of SAP NetWeaver They are identified by unique SAP system
IDs (SAPSIDs) and configured for a certain purpose as indicated by usage types Usage types have the
following characteristics
They are a structuring element for SAP software on a technical level
Usage Types determine the intended purpose of a system and the role it plays in a given (distributed)
use case
They are realized by installing and configuring a collection of software components
They allow a logical view of the technology platform SAP NetWeaver PI
A usage type may require other usage types in the same system to operate
They can also be run in the same system together with other usage types that are not a prerequisite
How SAP NetWeaver Systems are Used
The following sections describe the usage types and their dependencies for SAP NetWeaver PI
Application Server ABAP (AS ABAP)
Purpose
AS ABAP is used to provide the ABAP foundation of SAP NetWeaver PI
Application Server ABAP provides a complete development and runtime environment for ABAP-based
applications It is optimized for the development of highly scalable business applications The ABAP
development and runtime environment makes it possible to develop complex business applications
3 SAP NetWeaver PI Overview
31 Installable Software Units
1656 PUBLIC 2011-04-15
without having to worry explicitly about technical details such as process or memory administration
multi-user capability database connections or similar issues These are provided in the basis services or
are integrated directly in the ABAP runtime The application development is similarly independent of
the underlying platform The application server decouples the application coding completely from the
operating system and database that are used
Dependencies
AS ABAP can be combined optionally with other usage types in one system
Application Server Java (AS Java)
Purpose
AS Java is used to provide the Java foundation of SAP NetWeaver PI using the Java Engine a Java EE-
compliant application server for running enterprise applications In addition to the pure Java EE
standard technologies the Java Engine implements complementary technologies such as Web Dynpro
or Web Services that are targeted at supporting large-scale real-business application development
projects
Dependencies
AS Java can be combined optionally with other usage types in one system
Process Integration (PI)
Purpose
PI consists of core components that model design automate and integrate processes in one or more
application systems For the integration of internal and cross-company processes PI is used to
incorporate all the functions of what was formerly known as Exchange Infrastructure (XI) In addition
PI contains core components for Business Process Management for application-embedded and
application-unbounded processes
The Advanced Adapter Engine is also part of usage type PI You use Advanced Adapter Engine to connect
to SAP systems (RFC adapter) and external systems You use the various adapters in Advanced Adapter
Engine to convert XML- and HTTP-based messages to the specific protocol and format required by
these systems and the other way around You can use the Advanced Adapter Engine that is part of
your PI system as a central Advanced Adapter Engine Optionally (for performance reasons) you can
install a non-central Advanced Adapter Engine [page 19] separately as a system with AS Java and parts of the
usage type PI on a separate host
Dependencies
PI requires AS ABAP and AS Java as prerequisites in the same system
For installing PI it is mandatory to have a dedicated PI system This applies to development quality
and production landscapes It is a prerequisite that no other system in your system landscape has a
higher release and enhancement package level than the PI system If you want to upgrade or install an
application in your system landscape you first have to make sure that the current release and
enhancement package level of the PI system is on the same level - if required you have to upgrade the
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1756
PI system first to the new or a higher release In a dedicated PI system this can be accomplished with a
minimum of downtime Also the PI system would not be affected by the downtime of other usage
types running in the same system
Configuration of Systems with Usage Types
Configuration information is available in the installation guides the configuration wizard and SAP
Solution Manager
In the Installation Guide ndash SAP NetWeaver PI 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt you find
initial technical configuration tasks This guide also informs you about how you can run the
configuration wizard and how you can access the configuration information in SAP Solution
Manager
For certain usage types configuration tasks can be applied by the configuration wizard after the
installation To do this you start the configuration wizard from SAP NetWeaver Administrator
The configuration steps for systems with usage types required for an use case are accessible through
SAP Solution Manager
To be able to use SAP Solution Manager for the configuration tasks you have to import the latest
SAP Solution Manager Implementation Content (Add-On ST-ICO) that is available for your SAP
Solution Manager release For more information see SAP Note 631042 (Release strategy for Implementation
Content (ST-ICO))
SAP Solution Manager Implementation Content is available on SAP Service Marketplace at
httpservicesapcomswdc Installations amp Upgrades Entry by Application Component SAP
Technology Components SAP Solution Manager ltReleasegt Content ST-ICO
In SAP Solution Manager you create a project and a project structure In the configuration phase
you select configuration structures with pre-delivered SAP content for your project You can find
the following different types of configuration tasks in SAP Solution Manager
Mandatory configuration tasks All configuration tasks that are mandatory for the standalone
engine or usage type
Optional configuration tasks Configuration tasks for areas where customers need to decide
if they want to use these functions (for example high availability or security settings)
Additional functions ndash configuration tasks Configuration tasks for functional units that are
used in certain use cases only
A marked checkbox in front of the configuration tasks indicates those configuration tasks that are
relevant for the use case you have chosen To configure ABAP systems SAP Solution Manager
offers executable configuration files (IMG activities)
For information about using SAP Solution Manager Content and creating a configuration guide
see the following documentation
httphelpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Implementing
and Upgrading SAP Solutions Configuration
3 SAP NetWeaver PI Overview
31 Installable Software Units
1856 PUBLIC 2011-04-15
How to Create a Configuration Guide using SAP Solution Manager available at http
servicesapcomsolutionmanager Media Library How-To Documents
Restrictions for Systems with Multiple Usage Types
If you have one system with multiple usage types be aware that we do not provide standard tools
to separate these usage types and distribute them to multiple systems at a later stage For example
if you have a system with usage types A and B you are not able to migrate it with SAP standard
tools into two systems one with usage type A only and the other with usage type B only
In addition we do not provide standard tools to merge multiple systems with different usage types
into one system with multiple usage types at a later stage
If you want to perform these tasks you require specific project support
The following figure shows that SAP standard system copy and migration tools do not support
you in separating or merging systems with usage types
Figure 4 No Support for Merging or Separating Systems with Usage Types
Although you can use one system for multiple usage types client restrictions apply for usage type
PI PI requires a dedicated client due to special PI requirements concerning the client pipeline
Whereas application client pipelines only send and receive messages the central PI pipeline can
also map messages to different formats before sending them
312 Standalone Engines
Standalone engines of SAP NetWeaver are additional installable software units They do not work as
full-blown systems of SAP NetWeaver but as standalone engines that provide a specific (server) function
in combination with one or more SAP NetWeaver systems
Standalone engines are not part of a usage type They do not run on AS ABAP or AS Java
The standalone engines that are available for SAP NetWeaver Process Integration are described in the
following
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1956
Gateway
It is possible to install an SAP instance of an SAP NetWeaver system based exclusively on a standalone
gateway This type of instance does not contain normal work process types (dialog background update
enqueue or spool) Only the gateway process (gwrd) is started If there is an SNA connection to an R
2 system gateway work processes (gwwp) are also started
SAP Conversion Agent by Informatica
SAP Conversion Agent by Informatica is a data conversion tool that enables you to create interfaces
between any data formats and XML-based systems SAP Conversion Agent can convert unstructured
semi-structured and structured formats to XML and the other way around The Conversion Agent
comprises the Conversion Agent Studio and the Conversion Agent Engine In the Conversion Agent
Studio you can develop and configure data conversions The Conversion Agent Engine executes the
data conversions
Search and Classification (TREX)
You can use Search and Classification with SAP NetWeaver PI to search for messages that were previously
indexed Message search using index provides additional methods of searching for specific messages In
addition to static header attributes you can also use adapter-specific message attributes and data from
the message payload for the search A requirement of this however is that the messages are indexed
first You can apply the index-based message search to one or all indexed components of an integration
landscape (domain) Integration Server Adapter Engines and ABAP business systems
For more information see the SAP Library [page 12] at Administratorrsquos Guide Technical Operations for SAP
NetWeaver Administration of SAP NetWeaver Systems Administering PI (Process Integration) Monitoring Index
Administration
Web Dispatcher
The Web Dispatcher lies between the Internet and your SAP system It is the entry point for HTTP(s)
requests into your system which consists of one or more SAP NetWeaver application servers As a
software web switch the Web dispatcher can reject connections or accept them When it accepts a
connection it balances the load to ensure an even distribution across the servers
You can use the Web dispatcher in ABAPJava systems and in pure Java systems as well as in pure ABAP
systems
It is also beneficial to use the Web Dispatcher if you do not need security functions (entry point in the
demilitarized zone (DMZ) SSL URL filtering) but you simply want to balance the load between
multiple SAP NetWeaver Application Server instances
Since Web Dispatcher is optional for every SAP system it is not contained in the system landscape and
the implementation sequence of the use case in this documentation
For more information see the SAP Library [page 12] at Function Oriented View Application Server Infrastructure
SAP Web Dispatcher
3 SAP NetWeaver PI Overview
31 Installable Software Units
2056 PUBLIC 2011-04-15
Advanced Adapter Engine
You use the Advanced Adapter Engine to connect to SAP systems (RFC adapter) and external systems
You use the various adapters in Advanced Adapter Engine to convert XML- and HTTP-based messages
to the specific protocol and format required by these systems and the other way around For specific
senderreceiver combinations messages can be processed without invoking the central Integration
Engine In principle you connect external systems using the adapters that are installed centrally or
non-centrally in Advanced Adapter Engine You can use the Advanced Adapter Engine that is part of
your PI system as a central Advanced Adapter Engine Optionally (for performance reasons) you can
install a non-central Advanced Adapter Engine separately as a system with AS Java and parts of the
usage type PI on a separate host
Adapter Engine (Java SE)
Adapter Engine (Java SE) is a separate software unit You can use it only if you have SAP NetWeaver
systems with usage type PI in your system landscape It has to be installed manually You use the Adapter
Engine (Java SE) to connect to external systems Using the various adapters in the Adapter Engine (Java
SE) XML and HTTP-based messages can be converted to the specific protocol and format required by
such systems and the other way around The Adapter Engine (Java SE) only provides some of these
adapters as a standalone version with restricted functions for operating systems that do not support
SAP NetWeaver PI 71 but that have at least a Java Runtime Environment 50 Therefore you should
use the Adapter Engine (Java SE) only if the platform prerequisites do not allow you to use the Advanced
Adapter Engine
SAP Partner Connectivity Kit
SAP Partner Connectivity Kit (PCK) runs on AS Java with parts of the usage type PI It enables a system
of a smaller company or subsidiary that does not run SAP NetWeaver PI to connect to your SAP
NetWeaver systems
313 Clients
Clients are additional installable programs or tools They reside either on local front-end PCs accessed
by users or on back-end systems where they act as client programs within an SAP NetWeaver system
landscape
The clients that you can use with SAP NetWeaver Process Integration are described in the following
sections
SAP GUI
NOTE
We recommend that you use the following versionsI
SAP GUI for Windows 710 (or higher) with the latest patch level
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 2156
SAP GUI for Java 710 (or higher) with the latest revision
The integrated SAP ITS 710
For more information about the SAP GUI family see SAP Service Marketplace at http
servicesapcomsapgui
SAP offers three different client applications for accessing ABAP applications in SAP systems (such as
SAP NetWeaver systems with usage type AS ABAP) This SAP GUI family consists of
SAP GUI for HTML
SAP GUI for HTML is based on the SAP integrated Internet Transaction Server (ITS) which is
included in the installation of SAP NetWeaver systems as of SAP NetWeaver 2004 On the client
side only a suitable browser (such as Internet Explorer 70 or Firefox 20) and a virtual machine are
required SAP ITS 620 is not compatible with SAP NetWeaver 71
SAP GUI for the Java environment (SAP GUI for Java)
SAP GUI for Java is a generic SAP GUI that covers a variety of platforms
For more information about the installation of SAP GUI for Java see the documentation Installation
Guide ndash SAP Front End
SAP GUI for the Windows environment (SAP GUI for Windows)
SAP GUI for Windows is SAPs universal client for accessing all SAP applications built on ABAP
technology It is available on the Microsoft Windows platform only and offers the broadest feature
set of all members of the SAP GUI family
For more information about the installation of SAP GUI for Windows see the Installation Guide ndash
SAP Front End
SAP NetWeaver Developer Studio
The SAP NetWeaver Developer Studio is SAPrsquos Integrated Development Environment (IDE) for Java
and is based on the open-source tools framework Eclipse 33 With the SAP NetWeaver Developer Studio
you can develop Java EE 5 applications from scratch using the built-in support for new technologies
such as EJB 30 and JSF 12
During the installation of the SAP NetWeaver Developer Studio several features are offered for
installation For SAP NetWeaver PI 71 only the following features are relevant
SAP NetWeaver Developer Studio Platform
SAP NetWeaver Developer Studio Java EE
NOTE
If you want to use one of the other features you need SAP NetWeaver Composition Environment
and a corresponding developers licence
For more information about the installation of SAP NetWeaver Developer Studio see the Installation
Guide ndash SAP NetWeaver Developer Studio 71 or Installation Guide ndash SAP NetWeaver Developer Studio 71 Including
Enhancement Package 1
3 SAP NetWeaver PI Overview
31 Installable Software Units
2256 PUBLIC 2011-04-15
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
SAP enhancement packages are a new way of delivering new functions for SAP NetWeaver This allows
a clear separation between the delivery of new functions on the one hand and corrections legal changes
and security updates on the other hand (in Support Package stacks) SAP enhancement packages are
cumulative an enhancement package always contains the functions of the corresponding predecessor
enhancement packages
Enhancement packages are maintained by their own Support Packages while the main release is in
maintenance
Benefits
SAP enhancement packages offer the following benefits
You have reduced effort for testing and no effort for training when applying Support Packages as
new features are only shipped with enhancement packages
Adding new functions between releases becomes predictable and controllable
New functions can be added successively in small steps There is no need to fully upgrade your
system to get new functions
You have minimal training effort when applying an enhancement package because existing
functions are not replaced
Implementation
There are the following ways to get an SAP NetWeaver system with the release level of SAP enhancement
package 1 for SAP NetWeaver Process Integration 71
New installation of SAP NetWeaver PI 71 including enhancement package 1 using the standard
installation tool SAPinst
Upgrade of an existing SAP NetWeaver system from a release lower than SAP NetWeaver PI 71 to
SAP NetWeaver PI 71 including enhancement package 1 For this you use the upgrade programs
SAPup (for ABAP) and SAPJup (for Java)
Installation of the enhancement package on an existing SAP NetWeaver PI 71 system
For this you use the Software Update Manager (SUM) The Software Update Manager evolved
from the previously used SAP Enhancement Package Installer The tool has been renamed to reflect
its broader use for example you can also use it for applying Support Package Stacks to your system
On the ABAP side the Software Update Manager uses a system cloning and switch procedure for
installing enhancement packages It installs a copy of the system the shadow system parallel to
the original system This shadow system is used to update the relevant software components and
to install the additional components while the original system is still in production operation At
a certain point during downtime the switch to the new system is made and afterwards any parts
of the original system that are no longer needed are deleted The enhancement package installation
in a Java system uses a deploy-based procedure that is no shadow system is used The Software
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2011-04-15 PUBLIC 2356
Update Manager requires a stack configuration file (xml file) as input file for the enhancement
package installation procedure This file lists all the packages that are to be installed in your systems
The stack configuration file is generated when you download the required packages
As the Software Update Manager is updated regularly we recommend to always use the latest
version It is delivered as part of the SL toolset For more information see http
servicesapcomsltoolset
For an overview of all required steps for the enhancement package installation process and
corresponding documents see Process Overview Installation of Enhancement Package 1 on an Existing SAP
Netweaver PI 71 System [page 28]
Content of SAP Enhancement Package 1 for SAP NetWeaver PI 71
With enhancement package 1 for SAP NetWeaver PI 71 new features are introduced and some existing
are changed The following is a selection of some of the most important enhancements
Enhanced design and modelling options in the Enterprise Services Repository
New services registry
Support for new Web services standard (Web Services Reliable Messaging)
New modules for the Advanced Adapter Engine
Use of shared memory of the ABAP Application Server for message processing
For more information about the changes see SAP Library [page 12] at Whatacutes new in SAP NetWeaver PI 71
ndash Release Notes
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2456 PUBLIC 2011-04-15
4 SOA-Based Integration Use Case
41 Overview
You can use SOA-based integration to set up the communication between service providers and service
consumers in both application-to-application and business-to-business scenarios and to execute
operate and monitor the communication at runtime SOA-based integration covers both direct (point-
to-point) as well as mediated (via an Integration Server) communication between service providers and
service consumers
The use case spans the whole life cycle of a SOA-based integration scenario including
Scenario modeling and service design in the Enterprise Services Repository
Implementation of the service provider and consumer in the back-end systems
Configuration and finally execution monitoring and operation of the integration scenario
For scenarios using Integration Server or broker-based communication the configuration of the
different connectivity options (for example SOAP RFC Web Services Industry standards and JDBC)
and their enhancements is covered
For more information see the following documents
Service-Enabling with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdnsoa-modeling
Getting Started
Service-Enabling a Legacy Application with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdn
soa-servicebus Getting Started
In the following you will find information about the installation of the involved software units
42 System Landscape
The following figure shows the system landscape for this use case
4 SOA-Based Integration Use Case
41 Overview
2011-04-15 PUBLIC 2556
Figure 5 SOA-Based Integration
It is mandatory to have a dedicated PI system This applies to development quality and production
landscapes
For PI it is a prerequisite that no other system in your system landscape has a higher release than
the PI system For exceptions to this rule see SAP Note 1043047 For example SAP XI 30 is compatible
with SAP NetWeaver 640 and 70 application systems since the same XI protocol is used Apart
from these exceptions if you want to upgrade or install an application in your system landscape
you first have to make sure that the PI system is on the same release level If required you have to
upgrade the PI system first to the new or a higher release
CAUTION
Although it should be technically possible to run an application system with a higher release
than your PI system in your system landscape this is not supported by SAP (apart from the
exceptions listed in SAP Note 1043047) Therefore you run such a landscape at your own risk
You can use the Advanced Adapter Engine that is part of your PI system as a central Advanced
Adapter Engine
Adapter Engine (Java SE) can be installed in a non-SAP Java environment However it only hosts
a subset of the adapter functionality is only supported for compatibility reasons and should be
used only if this is a precondition in your environment
Optionally you can use the Change Management Service (CMS) of an SAP NetWeaver 70 system
with usage type DI to transport design objects and repository objects For more information see
the SAP Library [page 12] at Administratoracutes Guide Technical Operations for SAP NetWeaver Administration
of SAP NetWeaver Systems PI (Process Integration) Software Logistics Transporting ESR Content and Objects
of Integration Directory PI Transports Using the Change Management Service (CMS)
Smaller business partners or subsidiaries that do not run SAP NetWeaver install SAP Partner
Connectivity Kit in their system landscape SAP Partner Connectivity Kit enables XML document
4 SOA-Based Integration Use Case
42 System Landscape
2656 PUBLIC 2011-04-15
exchange between your SAP NetWeaver systems and the partner systems Since SAP Partner
Connectivity Kit gets installed in their system landscape it is not shown in the system landscape
figure above
The AS ABAP system acts as an application and service provider For Java Web Services you also
require AS Java In addition you require SAP NetWeaver Developer Studio on the client side as a
development environment
The Web service client can be either an SAP or a non-SAP application For example an AS ABAP
system or a Web browser could act as application or service consumer
You can install SAP Conversion Agent by Informatica in the system with usage type PI or on a host
where SAP Partner Connectivity Kit is installed or on a host where neither usage type PI nor SAP
Partner Connectivity Kit is installed
43 Implementation Sequence
Procedure
To install this use case perform the steps listed in the following table
StepAction[Corresponding Documentation] Remarks
1 Make sure that you have performed the preparation steps You have planned your system landscape [page 33]
(that is you have decided how many systems you require how you want to use each of these systems and which standalone engines and clients you require)
With the help of your hardware partner you have mapped your systems and standalone engines to properly sized hosts
You have planned and installed shared services [page 35]
2 Installation of system with usage type PI (includes the installation of AS ABAP and AS Java)
NOTE
For usage type PI a Unicode installation is mandatory
[Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt]
If you want to use the features of enhancement package 1 use the direct installation of SAP NetWeaver PI 71 including enhancement package 1
Make sure that you perform the configuration steps as described in the installation guide For certain usage types configuration tasks can be applied by the configuration wizard These configuration tasks as well as any additional configuration steps for your use case are listed in SAP Solution Manager For more information
4 SOA-Based Integration Use Case
43 Implementation Sequence
2011-04-15 PUBLIC 2756
StepAction[Corresponding Documentation] Remarks
see the Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt
3 Install the Adapter Engine (Java SE) engines if required[Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
4 To integrate small business partners and subsidiaries the business partners or subsidiaries install SAP Partner Connectivity Kit running on AS Java with parts of usage type PI in the business partners or subsidiarys system landscape[Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
5 Install SAP Conversion Agent by Informatica if required[SAP Library [page 12] at Function-Oriented View Process Integration SAP Conversion Agent by Informatica Deploying and Using Conversion Agent ]
6 Installation of clients SAP GUI
[Installation Guide ndash SAP Front End]
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
The process sequences give a comprehensive overview of the steps relevant for the enhancement
package installation on an existing SAP NetWeaver PI 71 system
The process sequence is divided into a planning phase and an implementation phase Each step in both
phases contains references to the corresponding documentation to ensure that you can easily find the
information you need
Process
NOTE
To download the enhancement package files and required Support Packages you require the SAP
Solution Manager Maintenance Optimizer You have the following options
Manual Selection
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2856 PUBLIC 2011-04-15
You manually select the required files from SAP Service Marketplace at http
servicesapcomswdc using the SP Stack Application You use the Maintenance Optimize
only to approve the packages which is a prerequisite for the download
Automatic Calculation
The Maintenance Optimizer supports the download of a consistent queue that includes all
necessary Support Packages and enhancement packages In addition SAP Solution Manager
calculates a valid import queue for the selected SAP system and generates the enhancement
package stack configuration file that you require for the installation
As a prerequisite the system that you want to update needs to be maintained correctly in
SAP Solution Manager System Landscape As the Maintenance Optimizer uses this data for
the calculation it is crucial that the data is up-to-date In addition the SAP Solution Manager
system requires a Minimum Support Package level (see below)
Planing PhaseStep Description Documentation
Hardware amp Software Prerequisites
Check which platforms are supported for your target release (OSDB dependencies)
Product Availability Matrix (PAM) at httpservicesapcompam
Check which hardware sizing is required for your target release
Sizing information at httpservicesapcomsizing
Solution Manager Prerequisites
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of the required software packages you have to make sure that your SAP Solution Manager system has the required Support Package levelAt least SAP Solution Manager 70 EHP1 Support Package Stack 17 is required We recommend to use SAP Solution Manager 70 EHP1 Support Package Stack 23Check if you need to do an update or upgrade of your SAP Solution ManagerMake sure that you run the guided procedure SOLMAN_SETUP after every installation or update of SAP Solution Manager and that it completes successfully
For upgrades from source release SAP Solution Manager 31 and 32Upgrade Guide ndash SAP Solution Manager 70 incl Enhancement Package 1For updates from SAP Solution Manager 70Update Guide SAP Enhancement Package 1 for SAP Solution Manager 70Follow-up activities after an Support Package Stack update or enhancement package updateSolution Operations Guide ndash SAP Solution Manager 70 EHP1 section Software Change Management All guides are available at http
servicesapcom instguides SAP Components SAP Solution Manager -gt Release 70 EHP 1
Implementation PhaseStep Description Documentation
1Solution Manager Preparation
Configure the SAP Solution Manager Maintenance Optimizer
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of software packages make sure your
Configuration of Maintenance Optimizer http
helpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Change Request Management and Change ControlMaintenance Optimizer
Prerequisites
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 2956
Implementation PhaseStep Description Documentation
system landscape data in SAP Solution Manager is maintained correctlyLandscape Verification 10 which is an add-on to SAP Solution Manager can support you in maintaining your system landscape data The use of this tool is optional
Landscape Verification http
wwwsdnsapcom irj
sdn alm-update-
management link Landscape Verification under Related Areas on Upgrade and Update Management (in the right column)
SAP Note 1468605 (Installation of Landscape Verification)
Maintaining System Landscape Information [page 47]Note that the information provided in this section is based on SAP Solution Manager 70 EHP1 SP23
2System Preparation
Prepare your system as described in the documentation for example perform OS DB specific preparations and the PI-specific preparations
Update Guide ndash Update of SAP Systems with Software Update Manager sections Planning and Preparation
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
3Software Download
Select and download the software packages in either of the following ways Automatic calculation Create
a maintenance transaction in the Maintenance Optimizer and choose the Calculate Files Automatically option
Manual Selection Create a maintenance transaction in the Maintenance Optimizer and choose the Select Files Manually option You then can select the files manually using the SP Stack application in SAP Service Marketplace
NOTE
You have to download the stack configuration file manually after you have selected all files in the SP Stack
httphelpsapcom SAP Solutions SAP Solution Manager
SAP Solution Manager 70 EHP1 ltSPgtChange Request Management and
Change Control Maintenance Optimizer Maintenance Procedure Scenarios
For information about the automatic calculation see Maintenance Transaction with Installation of an Enhancement PackageFor information about the manual selection and approval process see section Approve and Download Files in Download Basket
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
3056 PUBLIC 2011-04-15
Implementation PhaseStep Description Documentation
application Choose Generate Stack XML and save the file
4Enhancement Package Installation
Run Software Update Manager to update your system with the selected software packages
Update Guide ndash Update of SAP Systems with Software Update Manager
5Follow-Up Steps
Perform technical and PI-specific follow-up activities after the enhancement package installation is done
Update Guide ndash Update of SAP Systems with Software Update Manager section Follow-Up Activities
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
6Configuration
Configure newly installed enhancement package functions using SAP Solution Manager content
See Systems with Usage Types [page 16] section Configuration of Systems with Usage Types
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 3156
This page is left blank for documents that are printed on both sides
5 System Landscape
51 Planning Your System Landscape
The installable software units that make up your system landscape depend on the functions that you
want to implement For information about the features see systems [page 16] standalone engines [page 19]
and clients [page 21]
In addition you have to determine the required shared services [page 35] (such as SAP Solution Manager
or SAP NetWeaver Administrator) that run on central systems in your system landscape and the
landscape aspects relevant for their implementation
In the following you will find general information that you should consider when planning your system
landscape
Sizing
You have to map systems and standalone engines to hosts after you have a clear picture of the following
Which systems and standalone engines you require
How many systems you require and how you want to use each of these systems
NOTE
No general guideline can be given for the sizing of your landscape since this relies heavily on your
requirements You should therefore perform this task together with your hardware partner and
your technical consultant
For information about sizing your systems you can use the following information sources
Your first point of reference is the Quick Sizer
SAP built the Quick Sizer as an online sizing questionnaire Internet application in close cooperation
with its hardware partners This tool delivers general sizing categories based on your volume load
estimates The results provide an objective basis for sizing independent of platform and
configuration
For more information see SAP Service Marketplace at
httpservicesapcomsizing for the SAP NetWeaver PI 71 sizing guide available under
Sizing Guidelines Business Suite amp Services
httpservicesapcomquicksizer for more information and access to the tool itself
Also consider the following important aspects concerning sizing
High availability
5 System Landscape
51 Planning Your System Landscape
2011-04-15 PUBLIC 3356
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Technical Infrastructure High Availability
Unicode
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Internationalization
Contact your hardware partner to find out the appropriate number of sized hosts
The platform-independent abstract results of the Quick Sizer can be used by any of our hardware
partners to create a concrete offer SAP itself does not make any hardware recommendations the
responsibility for sizing and detailed hardware configuration lies with the hardware partners
Figure 6 Example of Mapping of Systems and Standalone Engines to Three Hosts
NOTE
Optionally you could also distribute single systems to multiple hosts For example you could
decide to install the database instance of an SAP system on a separate host for performance
reasons or distribute other system instances to achieve high availability
To provide a mapping that fits your required functions and performance your hardware partner
and your technical consultant have to identify the number of required instances of SAP NetWeaver
find out how to distribute these instances to hosts and what functions will run on which instance
Therefore the hardware partner and the technical consultant have to consider many different
aspects such as
Number of required SAPS (SAP Application Benchmark Performance Standard) for each
system (provided by Quick Sizer)
Landscape-relevant aspects concerning security For more information see the SAP Security
Guide in the SAP Library [page 12] at Administratoracutes Guide Security Guide
Landscape-relevant aspects concerning scalability high availability operation and software
life-cycle management
5 System Landscape
51 Planning Your System Landscape
3456 PUBLIC 2011-04-15
For more information about relevant aspects for the mapping of systems to hosts see the document
Technical Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
Scaling and Distribution Options
You may need to design your system landscape for a large number of users SAP NetWeaver PI offers
you different means of scalability The following list provides you with some examples
You could install multiple systems of one type and use them for different purposes
You could scale every system by installing dialog instances or by distributing the database instance
For more information about distribution options on the instance level see the Technical
Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
For every SAP system you could additionally install Web Dispatcher For more information see
the SAP Library [page 12] at FunctionndashOriented View Application Server Infrastructure SAP Web
Dispatcher
You could further distribute certain standalone engines ndash for example Search and Classification
(TREX) is based on a flexible architecture that supports a distributed installation For more
information see the Technical Infrastructure Guide ndash SAP NetWeaver PI 71 available in SAP Service
Marketplace at httpservicesapcominstallNWPI71
52 Shared Services
You normally run shared services on central systems in your system landscape The following features
could be used for SAP NetWeaver Process Integration to realize shared services
SAP Solution Manager
Used to implement train test maintain monitor control change and manage incidents of your
SAP solution system landscape (open end-to-end application management)
As of SAP Solution Manager (70) 40 Support Package 15 SAP Solution Manager has become the
platform for SAPs end-to-end solution operations strategy Functions for complete application
management has been combined with administrative tools and has been merged in newly created
role based work centers
NOTE
Be aware that you require an SAP Solution Manager system to install or upgrade to SAP
NetWeaver 70 and higher An SAP Solution Manager system is required to generate the SAP
Solution Manager key needed during the installation or upgrade process Without this key
the installation or upgrade process cannot continue
For SAP NetWeaver Process Integration you require SAP Solution Manager 70
For more information see SAP Note 805390
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3556
Solution Manager Diagnostics
An integral part of SAP Solution Manager that is running as a Java application on the Java stack of
SAP Solution Manager 70 Solution Manager Diagnostics is used to analyze the root cause of
incidents in your landscape in an efficient and safe way Before Go-Live Solution Manager
Diagnostics has to be set up and made accessible remotely
SAP NetWeaver Administrator
SAP NetWeaver Administrator is the central administration component which is used for
monitoring and administering Java applications It is included in SAP NetWeaver systems with AS
Java
SAP NetWeaver Administrator exists in the following flavors
A local mode which runs out of the box and which focuses on administrating the underlying
SAP NetWeaver AS Java
NOTE
For a SAP NetWeaver PI 71 it has a special role which you need to activate using a
configuation wizard
A central mode which has to be configured before use and which deals with the system
landscape management
SAP has decided to merge the central mode of SAP NetWeaver Administrator into the new work
centers available as of SAP Solution Manager 70 SP 15 Thus it can be used in an administrative
context together with non-Java-based administration tools Although the central mode of SAP
NetWeaver Administrator will be still available for some time SAP will not develop this tool any
further SAP focuses on optimizing the administrative work centers of SAP Solution Manager
instead
The local mode of SAP NetWeaver Administrator stays untouched It is available for current and
future releases of SAP NetWeaver
SAP Central Process Scheduling by Redwood
SAP Central Process Scheduling application by Redwood enables central job scheduling and job
monitoring of current and old releases of AS ABAP systems (as of Basis Release 31) This application
is fully integrated in SAP NetWeaver Depending on the business needs SAP business applications
are the initial trigger for scheduled activities You can now manage jobs and job chains conveniently
using a graphical user interface
System Landscape Directory
The System Landscape Directory is the central directory of system landscape information relevant
for the management of your software life-cycle It contains a description of your system landscape
(that is software components that are currently installed) and a repository of software components
that can theoretically be installed in your landscape (such as the software components available
from SAP)
Adaptive Computing Controller
5 System Landscape
52 Shared Services
3656 PUBLIC 2011-04-15
The Adaptive Computing Controller enables users to control an adaptive computing landscape
from a single point through observation operation and dynamic resource distribution With
adaptive computing hardware software and system services are able to adapt to changing business
needs In the Adaptive Computing Controller the run-time data of logical and physical landscapes
can be monitored application services can be startedstoppedrelocated and hardware resources
can be assigned to application services The operation can also be mass executed and be planned as
tasks to be executed
For more information about the installation of the Adaptive Computing Controller tool see the
document Installation Guide ndash Adaptive Computing Controller in SAP NetWeaver 71 available on SAP Service
Marketplace at httpservicesapcominstallNWPI71
For more information about Adaptive Computing in general see httpsdnsapcomirj
sdnadaptive
521 Use Cases
You can use the applications and tools described above for use cases that are normally performed
centrally The following sections describe these use cases
5211 End-to-End Solution Operations
Running business applications through their complete life-cycle is a challenge Therefore SAP has
started the Run SAP methodology for implementing End-to-End Solution Operations Based on a set
of SAP standards a roadmap and a package for training and certification Run SAP helps customers to
facilitate End-to-End Solution Operations
You can download the SAP standards for Solution Operations from SAP Service Marketplace at http
servicesapcomsupportstandards They describe roles customers typically have in their IT
environment For optimal role support SAP has grouped existing and new functions in SAP Solution
Manager work centers as of SAP Solution Manager 70 Support Package 15 Operations aspects are fully
covered by adding administrative functions for SAP NetWeaver as well Work centers are ABAP Web
Dynpro-based applications They offer the following advantages
Easy to use similar look and feel
Context transfer while jumping from one work center into another
Logical grouping of tools for a certain area
Simple authorization concept
Easy to expand
Each IT role belongs to one or more work centers For instance the Technical Administrator IT role is
covered by the work centers for System Monitoring System Administration and Landscape Management
The following work centers are available
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3756
Business Process Operations
Change Management
Root Cause Analysis
Implementation Upgrade
Incident Management
Test Management
Job Management
System Landscape Management
Solution Documentation Assistant
SAP Engagement and Service Delivery
SAP Solution Manager Administration
System Administration
System Monitoring
My Home is the central point of access to all important data of almost all work centers in SAP Solution
Manager
5212 Support Infrastructure
A key requirement for effective support of IT solutions is the ability to perform root cause analysis with
speed and efficiency
With SAP Solution Manager SAP has long had an infrastructure in place for its ABAP applications that
efficiently supports SAP solutions This helps ensure the high availability and smooth running of
business processes For more information see the SAP Solution Manager section
With Solution Manager Diagnostics this knowledge has been extended to Java applications If for
example homegrown Java applications cause instability Solution Manager Diagnostics helps trace the
cause to eradicate the problem rapidly Solution Manager Diagnostics is fully integrated into SAP
Solution Manager 70 Solution Manager Diagnostics also contains two third-party tools CArsquos Wily
Introscopereg for measuring performance as well as troubleshooting problems of the Java EE Engine
and applications running on it and Mercury Loadrunnerreg which enables SAP Support to produce a
defined load in the SAP solution landscape remotely For more information see Solution Manager
Diagnostics [page 43]
The support infrastructure provides SAP Support with safe access to your productive landscape for safe
root cause analysis so ensuring that SAP Support does not change your landscape inadvertently You
require a support infrastructure to run SAP NetWeaver
The following figure shows the overall infrastructure including SAP NetWeaver administration tools
that are used by administrators or operators at the customer site
5 System Landscape
52 Shared Services
3856 PUBLIC 2011-04-15
Landscape Aspects
If you use SAP NetWeaver Process Integration 71 productively besides SAP Solution Manager (as a
central support platform) you have to set up Solution Manager Diagnostics for supportability reasons
Implementation Sequence
For information about the implementation of the support infrastructure see the document Master
Guide ndash SAP Solution Manager 70 available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution Manager ltReleasegt
5213 Collection of Landscape Data
Amongst other applications and services the support infrastructure and the SAP NetWeaver
administration tools rely on system landscape data
For SAP NetWeaver PI 71 you have to run non-ABAP components in your solution landscape
Therefore the System Landscape Directory is mandatory The landscape data that is automatically
gathered by the System Landscape Directory is replicated to SAP Solution Manager There are several
topology options for the System Landscape Directory They offer different grades of availability
administration and operation effort
For more information see the System Landscape Directory section
5214 Authentication and Single Sign-On
Before implementing your system landscape plan how to implement authentication and how to
integrate different systems into a Single Sign-On landscape Single Sign-On reduces complexity for end
users saving them valuable time while also reducing administration effort for resetting passwords
thereby contributing to TCO reduction
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
5215 Integrated User and Access Management
In a system landscape containing a combination of ABAP and Java components we recommend that
you integrate your user and access management so that you can use the same user data across different
systems administer this data centrally and control access to data SAPs mature fine-grained
authorization concept allows detailed control of access rights SAP NetWeaver provides both ABAP and
Java-based user management solutions The user management solution that you use to administer
your user data depends on factors such as the type of systems that are running in your landscape
If you want to use central user administration we recommend that you run it in a non-production
system If you do not have a central user administration yet you can for example realize it in the SAP
Solution Manager system
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3956
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
522 Examples for the Overall System Landscape of Shared Services
In this section we provide examples of how shared services can be set up depending on the system
landscape they are intended for The following examples aggregate the landscape aspects given in the
Use Cases section
NOTE
The following sections and the figure mostly do not show information about the life-cycle of
shared services For example you may also need a development and testquality assurance system
for SAP Solution Manager You should consider this aspect in addition to the information given
in this section based on your requirements
Small and MediumndashSized Customer Landscapes with Java
As you use Java productively for SAP NetWeaver PI 71 besides SAP Solution Manager you have to set
up additional components for optimal monitoring administration and support Solution Manager
Diagnostics and the central mode of SAP NetWeaver Administrator are already fully integrated into
SAP Solution Manager 70 as the central operations hub For SAP Process Integration you must also
set up SAP NetWeaver Administrator with a special role
We recommend that you do not install SAP Central Process Scheduling in the SAP Solution Manager
system You have to set up and operate the system which hosts your productive scheduler as a mission
critical system
In the SAP Solution Manager system you should set up a local System Landscape Directory in addition
to a central runtime System Landscape Directory This way you have a clear separation between your
management system (SAP Solution Manager) and managed systems in your landscape In addition
SAP Solution Manager then does not rely on a System Landscape Directory running in the production
environment For this setup configure the SLD data suppliers of your SAP Solution Manager system
to send data to the central runtime System Landscape Directory In addition configure automatic
bridge forwarding from your runtime System Landscape Directory to the local System Landscape
Directory For more information see the Planning Guide - System Landscape Directory
If you want to use a central system for Adobe Document Services we recommend that you install a
dedicated system for this purpose in your production environment For detailed information about
the sizing of the system for the different use cases see the Sizing Guide for Adobe Document Services at
SAP Service Marketplace at httpservicesapcomsizing Sizing Guidelines Solutions amp
Platform
We recommend that you start with this centralized SAP Solution Manager approach as depicted in the
following figure
5 System Landscape
52 Shared Services
4056 PUBLIC 2011-04-15
Figure 7 Single SAP Solution Manager Landscape
Large Customer Landscapes with Java
Large customers who have environments in their landscape that are large and distributed administered
by different groups or separated for security reasons can consider a distributed operations setup In
addition to the centralized setup described for small- and medium-sized customers above large
customers can put parts of the central management functions on extra hosts or systems for performance
or policy reasons You have the following options for a distributed setup
You may set up an extra system or client for Central User Administration (CUA)
The Change and Transport System (CTS) can run on an extra system However it is not
performance- or data-intensive
You may set up an extra system for central CCMS monitoring Depending on the customizing
and on the landscape size central CCMS may generate a lot of system load You can connect a
separate central CCMS to SAP Solution Manager for displaying alerts in the alert inbox of the System
Monitoring work center
You can use a separate SAP NetWeaver 70 system with usage type BI together with SAP Solution
Manager This may make sense with respect to the amount of landscape management data that is
stored for reporting purposes The amount of data strongly depends on the data granularity
storage time frame and landscape size
You can easily put Wily Introscope Enterprise Manager on an separate host
Other aspects described above for small- and medium-customers (such as the setup of the System
Landscape Directory) are also valid for large customers
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4156
523 Feature Details
This section provides further information about the features described above
5231 SAP Solution Manager
SAP provides you with SAP Solution Manager as the strategic application management platform and
to enable the collaboration between you and SAP You need to install at least one productive SAP
Solution Manager in your system landscape To ensure the availability of this application management
platform an SAP Solution Manager system is technically required to install or upgrade to SAP
NetWeaver 70 or higher If you are already using SAP Solution Manager you can also use it to manage
the solution you build with SAP NetWeaver In this case we highly recommend that you update SAP
Solution Manager to the latest version
As of SAP Solution Manager 70 SP15 you can use the newly created work centers
NOTE
During the SAP system installation or upgrade process you are prompted to enter the SAP
Solution Manager key An SAP Solution Manager system is required to generate this key Without
this key the installation or upgrade process cannot continue
You may generate all needed keys for your entire system landscape (development quality
assurance and production system) in one SAP Solution Manager system In case you plan to install
several solution landscapes (for example in different countries) one SAP Solution Manager
system is still sufficient
For more information see SAP Note 805390
It is possible to install multiple SAP Solution Managers If you do so they should host separate business
solutions
If you want to reduce the risk of unavailability you should not install SAP Solution Manager as a central
component Instead you can operate a 2-system-landscape with both a test and production
environment of SAP Solution Manager (especially if you are using time-critical functions like Support
Desk) If you also develop your own content a 3-system-landscape with a development test and
production environment is recommended
For more information about SAP Solution Manager see the following table
Topic Where to Find More Information
System infrastructure scenarios installation and configuration of SAP Solution Manager
Master Guide ndash SAP Solution Manager available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution ManagerltReleasegt
Benefits and usage scenarios SAP Solution Manager ndash Learning Maps available on SAP Service Marketplace at http
5 System Landscape
52 Shared Services
4256 PUBLIC 2011-04-15
Topic Where to Find More Informationservicesapcomrkt-solman or https
servicesapcomsolutionmanager
Additional information See SAP Service Marketplace at http
servicesapcomsolutionmanager
5232 Solution Manager Diagnostics
Solution Manager Diagnostics provides efficient and safe root-cause analysis of incidents in customer
solutions powered by SAP NetWeaver It can help monitor on operating systems databases Java
application activities performance and logs It also supports the reporting of software and
configuration changes that can lead to malfunctions and errors
You must run one Solution Manager Diagnostics within your SAP solution landscape if you run
applications based on SAP NetWeaver systems with usage type AS Java Agents are responsible for
delivering the data from all productive hosts within your system landscape to the Solution Manager
Diagnostics system
CAUTION
SAP Support performs root-cause analysis on incoming incidents with Solution Manager
Diagnostics Not installing and configuring this support infrastructure results in a dramatically
reduced service level
Solution Manager Diagnostics is fully integrated into SAP Solution Manager 70
Solution Manager Diagnostics also contains Wily Introscope (Display Server and Agent part) for
measuring performance as well as to troubleshoot problems of Non-ABAP applications Wily Introscope
is heavily used for troubleshooting applications running on AS Java
SAP has signed a distribution agreement for Wily Introscope SAP customers are allowed to use this
tool in a preconfigured way
For more information about Solution Manager Diagnostics and an FAQ list see SAP Service Marketplace
at httpservicesapcomdiagnostics
5233 System Landscape Directory
The System Landscape Directory (SLD) of SAP NetWeaver is the central directory of system landscape
information relevant for the management of your software life-cycle
NOTE
Note that the abbreviation SLD is not intended to define a product since the System Landscape
Directory is part of SAP NetWeaver This abbreviation is solely intended to improve readability
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4356
The System Landscape Directory contains a description of your system landscape (that is software
components that are currently installed) and a repository of software components that can
theoretically be installed in your landscape (such as the software components available from SAP)
Since this data gets updated automatically the System Landscape Directory provides reliable and up-
to-date system landscape information with as little effort for you as possible In this way the System
Landscape Directory acts as a central information provider for SAP and third-party tools that use this
data to deliver the services you need to keep your landscape up and running
For the System Landscape Directory as part of an SAP NetWeaver PI 71 landscape consider the following
aspects
Part of SAP NetWeaver PI 71 is a new version of the System Landscape Directory It is automatically
included in every SAP NetWeaver 71 system with usage type AS Java It offers enhanced functions
such as a full automatic synchronization mechanism for all data stored in it That is both data
delivered by data suppliers and data entered or changed manually in the System Landscape
Directory can be synchronized automatically This synchronization offers the following
A fully automated mechanism so no user interaction is required and conflicts are resolved
automatically
Asynchronous propagation of information so some nodes may be down temporarily
Communication over HTTP protocol
Uni- and bi-directional synchronization
Depending on your use case the full automatic synchronization could significantly reduce manual
synchronization effort
For SAP NetWeaver PI 71 the configuration of the system landscape directory and its data suppliers
is already included in the standard implementation procedure with SAPinst For existing systems
you only have to perform some quick and easy configuration actions to start operating the system
landscape directory server in an AS Java system
For SAP NetWeaver PI 71 you have the following options concerning SLD
Option 1
Run SAP NetWeaver PI 71 against an existing SLD running on SAP NetWeaver 70 We only
recommend this for upgrades from SAP NetWeaver 70 if you have a central SLD in operation
not running on one of your PI systems
Option 2
Use the SLD included in an SAP NetWeaver PI 71 system We recommend this option for new
installations and upgrades from older releases than SAP NetWeaver 70 due to the enhanced
functions and improved performance of SLD 71
NOTE
If you already have a central SLD running on SAP NetWeaver 70 in operation you could run
two SLD versions in parallel ndash SLD running on SAP NetWeaver 71 for your PI systems and
SLD running on SAP NetWeaver 70 for all other systemsuse cases This way your SAP
5 System Landscape
52 Shared Services
4456 PUBLIC 2011-04-15
NetWeaver PI 71 systems would benefit from the new features while it would be easy to set
up and operate such an SLD landscape For this purpose you could use the new fully
automatic synchronization This feature enables the automatic forwarding of all SLD data
from an SLD running on SAP NetWeaver 70 to an SLD running on SAP NetWeaver 71 As a
result there is no need to adapt most existing systems as their SLD data suppliers could still
send their data to the central SLD In brief the following steps would be required
1 Put SLD in a PI system into operation (part of standard implementation procedure)
2 Configure PI systems to use the new SLD (part of standard implementation procedure
for new PI systems)
3 Set up the fully automatic synchronization from your old SLD to your new SLD
As soon as an upgrade or an installation of a standalone AS Java 71 system is available you
could move your central SLD also to SAP NetWeaver 71 Then you could optionally shift
your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems
Figure 8
We recommend that you use a Domain Name System (DNS) alias so that you are able to switch to
another System Landscape Directory easily For example if customers build a new landscape they
normally start with a sandbox environment Over time more and more environments are set up
Once the production environment is in place move the System Landscape Directory there To do
this you can configure a new System Landscape Directory in the production environment
synchronize it with the old System Landscape directory and switch to the new one
Topology
Apart from the considerations above the System Landscape Directory offers several topology options
with different grades of availability at the expense of low administration and operation effort There is
no generic rule therefore on how to set up a System Landscape Directory in your system landscape
To find the topology and synchronization strategy for the System Landscape Directory that fits your
requirements concerning the System Landscape Directory availability (and hence the availability of
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4556
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
recommend that you test these scenarios thoroughly in your test systems to ensure that they are
complete and free of errors before going live
1 Introduction
1056 PUBLIC 2011-04-15
2 Before You Start
21 SAP Notes
You must read the following SAP Notes before you use this Master Guide and implement SAP NetWeaver
Make sure that you have the up-to-date version of each SAP Note which you can find on SAP Service
Marketplace at httpservicesapcomnotes
NOTE
The SAP Notes related to SAP NetWeaver PI 71 are also listed on SAP Service Marketplace at
httpservicesapcomsapnotesnwpi71
List of Important SAP Notes
SAP Note Number Title Description
1004107 Release Restrictions for SAP NetWeaver PI 71
Some restrictions apply to the productive use of SAP NetWeaver PI 71 These are documented in this SAP Note
1247043 Release Restrictions for SAP EHP1 for SAP NetWeaver PI 71
Some restrictions apply to the productive use of enhancement package 1 for SAP NetWeaver PI 71 These are documented in this SAP Note
22 More Information
The following table contains links to information available on SAP Service Marketplace or in the SAP
Library which is important for implementing SAP NetWeaver
Content Location on SAP Service Marketplace or in SAP Library
The latest version of the installation and upgrade guides for SAP NetWeaver Process Integration
httpservicesapcominstguidesnwpi71
Information about supported platforms (operating systems databases browsers) for all SAP NetWeaver components
httpservicesapcomplatforms Product Availability Matrix
Sizing of SAP NetWeaver httpservicesapcomsizing
Information about security SAP Security Guide See the SAP Library [page 12] at Adminitstratoracutes Guide Security Guide
Information about the technical operation of SAP NetWeaver
Technical Operations Manual See the SAP Library [page 12] at Adminitstratoracutes Guide Technical Operations for SAP NetWeaver
2 Before You Start
21 SAP Notes
2011-04-15 PUBLIC 1156
Content Location on SAP Service Marketplace or in SAP Library
Information about SAP NetWeaver PI Support Package Stacks
httpservicesapcomnetweaver SAP NetWeaver PI 71- Release-Specific Information Support Package Stacks Information
Information about installing SAP NetWeaver Support Package Stacks
httpservicesapcomMaintenanceNWPI71
Support Package Stack Guide ndash SAP NetWeaver
23 Accessing the SAP Library
For more information about SAP NetWeaver Process Integration access the SAP Library from any of
the following
SAP Help Portal at httphelpsapcomNWPI71 SAP NetWeaver Process Integration 71 Library
ltLanguagegt SAP NetWeaver Process Integration Library
CAUTION
The SAP Help Portal contains the latest version of the SAP Library Therefore we recommend
that you use this channel to access the SAP Library
An SAP system if you have installed the online documentation Choose Help SAP Library
The browser starts
The help files on the online documentation CDs or DVDs
If you want to view the help files in HTMLHelp format from the online documentation CDs or
DVDs you need a PC running Microsoft Windows to install the HTMLHelp Viewer
2 Before You Start
23 Accessing the SAP Library
1256 PUBLIC 2011-04-15
3 SAP NetWeaver PI Overview
Introduction
SAP NetWeaver PI 71 is part of the SAP NetWeaver technology platform The complete offering of the
SAP NetWeaver technology platform is visualized in the SAP NetWeaver technology map which you
can access at httpsdnsapcomnetweaver SAP NetWeaver at a Glance The technology map
enables you to drill down from top-level technology areas (for example Lifecycle Management) to
individual capabilities (for example Administration Monitoring and so on)
SAP NetWeaver PI includes the following capabilities
Repository-based Modeling and Design
Service Bus-based Integration
SOA Management
A different view is introduced by the end-to-end use case concept This concept offers an
implementation view on SAP NetWeaver to structure and facilitate your implementation
A use cases is a process that typically involves several SAP NetWeaver capabilities It is not limited to a
single component or capability A use case guides you through the different phases of your
implementation project ndash from information through installation to the configuration phase This
implies that a uses case addresses several user roles administrator power user and end user
This document describes the SOA-based integration use case
Architecture Principals
The architecture of SAP NetWeaver Process Integration 71 (SAP NetWeaver PI 71) is based on an
established architecture for realizing cross-system business processes and is a further development of
lower releases (SAP NetWeaver 70 usage type Process Integration and SAP XI 30 as part of SAP
NetWeaver 2004) SAP NetWeaver PI 71 plays an important role in supporting an service-oriented
architecture (SOA) The focus is on the service-based integration of applications
SAP NetWeaver PI is based on general standards so as to enable 3rd-party systems to be integrated At
the center of SAP NetWeaver PI is an XML-based communication that uses HTTP (Hyper Text Transfer
Protocol) Irrespective of the scenario used the application-specific contents are transferred in messages
in user-defined XML (eXtensible Markup Language) from the sender to the receiver either via the
Integration Server or directly between the systems involved
The following figure gives an overview of the key capabilities of SAP NetWeaver Process Integration
3 SAP NetWeaver PI Overview
2011-04-15 PUBLIC 1356
Figure 1 SAP NetWeaver PI Key Capabilities Overview
SAP NetWeaver Process Integration 71 enables the integration of the applications of the following
communication parties
B2B Party Any business partners that want to integrate their application with other applications
outside their own system landscape Scenarios that require industry standards are supported as
well as any scenarios that do not adhere to a particular industry standard
SAP Applications that run on SAP systems This includes the processing of events by using the
Business Activity Monitoring (BAM) infrastructure
3rd-Party Application Applications from 3rd-party providers within one system landscape for
example database or file-system-based
3rd-Party Middleware Middleware systems from 3rd-party providers that are required for the
integration of applications within a company and across company boundaries
SAP NetWeaver PI also supports internal company scenarios and cross-company scenarios It enables
you to connect systems from different vendors (non-SAP and SAP) in different versions and
implemented in different programming languages (Java ABAP and so on) to each other Like the rest
of the SAP NetWeaver platform SAP NetWeaver PI is based on an open architecture uses open standards
(in particular those from the XML and Java environments) and offers those services that are essential
in a heterogeneous and complex system landscape
To enable end-to-end SOA development SAP NetWeaver Process Integration 71 offers a Universal
Description Discovery and Integration (UDDI) v3-based Services Registry where providers can publish
service endpoints definitions and associated metadata and consumers can discover the appropriate
services for their scenarios The Services Registry provides capabilities for classifying and browsing
3 SAP NetWeaver PI Overview
1456 PUBLIC 2011-04-15
services using semantic-rich classification systems The Services Registry is part of Application Server
Java (AS Java)
31 Installable Software Units
SAP NetWeaver comprises the following three types of installable software units
Systems that are configured for a specific purpose as indicated by one or more usage types
Standalone engines that provide one specific (server) function in combination with one or more
SAP NetWeaver PI systems
Clients used by (many) people from their local front-end PC to access functions offered by systems
of SAP NetWeaver PI or standalone engines in the system landscape
In the following sections you can find more details about the software units The figure below provides
and overview of the software units
Figure 2 Installable Software Units for SAP NetWeaver PI
For this and other figures in this guide the following legend applies
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1556
Figure 3 Legend
311 Systems with Usage Types
SAP systems are the main building blocks of SAP NetWeaver They are identified by unique SAP system
IDs (SAPSIDs) and configured for a certain purpose as indicated by usage types Usage types have the
following characteristics
They are a structuring element for SAP software on a technical level
Usage Types determine the intended purpose of a system and the role it plays in a given (distributed)
use case
They are realized by installing and configuring a collection of software components
They allow a logical view of the technology platform SAP NetWeaver PI
A usage type may require other usage types in the same system to operate
They can also be run in the same system together with other usage types that are not a prerequisite
How SAP NetWeaver Systems are Used
The following sections describe the usage types and their dependencies for SAP NetWeaver PI
Application Server ABAP (AS ABAP)
Purpose
AS ABAP is used to provide the ABAP foundation of SAP NetWeaver PI
Application Server ABAP provides a complete development and runtime environment for ABAP-based
applications It is optimized for the development of highly scalable business applications The ABAP
development and runtime environment makes it possible to develop complex business applications
3 SAP NetWeaver PI Overview
31 Installable Software Units
1656 PUBLIC 2011-04-15
without having to worry explicitly about technical details such as process or memory administration
multi-user capability database connections or similar issues These are provided in the basis services or
are integrated directly in the ABAP runtime The application development is similarly independent of
the underlying platform The application server decouples the application coding completely from the
operating system and database that are used
Dependencies
AS ABAP can be combined optionally with other usage types in one system
Application Server Java (AS Java)
Purpose
AS Java is used to provide the Java foundation of SAP NetWeaver PI using the Java Engine a Java EE-
compliant application server for running enterprise applications In addition to the pure Java EE
standard technologies the Java Engine implements complementary technologies such as Web Dynpro
or Web Services that are targeted at supporting large-scale real-business application development
projects
Dependencies
AS Java can be combined optionally with other usage types in one system
Process Integration (PI)
Purpose
PI consists of core components that model design automate and integrate processes in one or more
application systems For the integration of internal and cross-company processes PI is used to
incorporate all the functions of what was formerly known as Exchange Infrastructure (XI) In addition
PI contains core components for Business Process Management for application-embedded and
application-unbounded processes
The Advanced Adapter Engine is also part of usage type PI You use Advanced Adapter Engine to connect
to SAP systems (RFC adapter) and external systems You use the various adapters in Advanced Adapter
Engine to convert XML- and HTTP-based messages to the specific protocol and format required by
these systems and the other way around You can use the Advanced Adapter Engine that is part of
your PI system as a central Advanced Adapter Engine Optionally (for performance reasons) you can
install a non-central Advanced Adapter Engine [page 19] separately as a system with AS Java and parts of the
usage type PI on a separate host
Dependencies
PI requires AS ABAP and AS Java as prerequisites in the same system
For installing PI it is mandatory to have a dedicated PI system This applies to development quality
and production landscapes It is a prerequisite that no other system in your system landscape has a
higher release and enhancement package level than the PI system If you want to upgrade or install an
application in your system landscape you first have to make sure that the current release and
enhancement package level of the PI system is on the same level - if required you have to upgrade the
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1756
PI system first to the new or a higher release In a dedicated PI system this can be accomplished with a
minimum of downtime Also the PI system would not be affected by the downtime of other usage
types running in the same system
Configuration of Systems with Usage Types
Configuration information is available in the installation guides the configuration wizard and SAP
Solution Manager
In the Installation Guide ndash SAP NetWeaver PI 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt you find
initial technical configuration tasks This guide also informs you about how you can run the
configuration wizard and how you can access the configuration information in SAP Solution
Manager
For certain usage types configuration tasks can be applied by the configuration wizard after the
installation To do this you start the configuration wizard from SAP NetWeaver Administrator
The configuration steps for systems with usage types required for an use case are accessible through
SAP Solution Manager
To be able to use SAP Solution Manager for the configuration tasks you have to import the latest
SAP Solution Manager Implementation Content (Add-On ST-ICO) that is available for your SAP
Solution Manager release For more information see SAP Note 631042 (Release strategy for Implementation
Content (ST-ICO))
SAP Solution Manager Implementation Content is available on SAP Service Marketplace at
httpservicesapcomswdc Installations amp Upgrades Entry by Application Component SAP
Technology Components SAP Solution Manager ltReleasegt Content ST-ICO
In SAP Solution Manager you create a project and a project structure In the configuration phase
you select configuration structures with pre-delivered SAP content for your project You can find
the following different types of configuration tasks in SAP Solution Manager
Mandatory configuration tasks All configuration tasks that are mandatory for the standalone
engine or usage type
Optional configuration tasks Configuration tasks for areas where customers need to decide
if they want to use these functions (for example high availability or security settings)
Additional functions ndash configuration tasks Configuration tasks for functional units that are
used in certain use cases only
A marked checkbox in front of the configuration tasks indicates those configuration tasks that are
relevant for the use case you have chosen To configure ABAP systems SAP Solution Manager
offers executable configuration files (IMG activities)
For information about using SAP Solution Manager Content and creating a configuration guide
see the following documentation
httphelpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Implementing
and Upgrading SAP Solutions Configuration
3 SAP NetWeaver PI Overview
31 Installable Software Units
1856 PUBLIC 2011-04-15
How to Create a Configuration Guide using SAP Solution Manager available at http
servicesapcomsolutionmanager Media Library How-To Documents
Restrictions for Systems with Multiple Usage Types
If you have one system with multiple usage types be aware that we do not provide standard tools
to separate these usage types and distribute them to multiple systems at a later stage For example
if you have a system with usage types A and B you are not able to migrate it with SAP standard
tools into two systems one with usage type A only and the other with usage type B only
In addition we do not provide standard tools to merge multiple systems with different usage types
into one system with multiple usage types at a later stage
If you want to perform these tasks you require specific project support
The following figure shows that SAP standard system copy and migration tools do not support
you in separating or merging systems with usage types
Figure 4 No Support for Merging or Separating Systems with Usage Types
Although you can use one system for multiple usage types client restrictions apply for usage type
PI PI requires a dedicated client due to special PI requirements concerning the client pipeline
Whereas application client pipelines only send and receive messages the central PI pipeline can
also map messages to different formats before sending them
312 Standalone Engines
Standalone engines of SAP NetWeaver are additional installable software units They do not work as
full-blown systems of SAP NetWeaver but as standalone engines that provide a specific (server) function
in combination with one or more SAP NetWeaver systems
Standalone engines are not part of a usage type They do not run on AS ABAP or AS Java
The standalone engines that are available for SAP NetWeaver Process Integration are described in the
following
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1956
Gateway
It is possible to install an SAP instance of an SAP NetWeaver system based exclusively on a standalone
gateway This type of instance does not contain normal work process types (dialog background update
enqueue or spool) Only the gateway process (gwrd) is started If there is an SNA connection to an R
2 system gateway work processes (gwwp) are also started
SAP Conversion Agent by Informatica
SAP Conversion Agent by Informatica is a data conversion tool that enables you to create interfaces
between any data formats and XML-based systems SAP Conversion Agent can convert unstructured
semi-structured and structured formats to XML and the other way around The Conversion Agent
comprises the Conversion Agent Studio and the Conversion Agent Engine In the Conversion Agent
Studio you can develop and configure data conversions The Conversion Agent Engine executes the
data conversions
Search and Classification (TREX)
You can use Search and Classification with SAP NetWeaver PI to search for messages that were previously
indexed Message search using index provides additional methods of searching for specific messages In
addition to static header attributes you can also use adapter-specific message attributes and data from
the message payload for the search A requirement of this however is that the messages are indexed
first You can apply the index-based message search to one or all indexed components of an integration
landscape (domain) Integration Server Adapter Engines and ABAP business systems
For more information see the SAP Library [page 12] at Administratorrsquos Guide Technical Operations for SAP
NetWeaver Administration of SAP NetWeaver Systems Administering PI (Process Integration) Monitoring Index
Administration
Web Dispatcher
The Web Dispatcher lies between the Internet and your SAP system It is the entry point for HTTP(s)
requests into your system which consists of one or more SAP NetWeaver application servers As a
software web switch the Web dispatcher can reject connections or accept them When it accepts a
connection it balances the load to ensure an even distribution across the servers
You can use the Web dispatcher in ABAPJava systems and in pure Java systems as well as in pure ABAP
systems
It is also beneficial to use the Web Dispatcher if you do not need security functions (entry point in the
demilitarized zone (DMZ) SSL URL filtering) but you simply want to balance the load between
multiple SAP NetWeaver Application Server instances
Since Web Dispatcher is optional for every SAP system it is not contained in the system landscape and
the implementation sequence of the use case in this documentation
For more information see the SAP Library [page 12] at Function Oriented View Application Server Infrastructure
SAP Web Dispatcher
3 SAP NetWeaver PI Overview
31 Installable Software Units
2056 PUBLIC 2011-04-15
Advanced Adapter Engine
You use the Advanced Adapter Engine to connect to SAP systems (RFC adapter) and external systems
You use the various adapters in Advanced Adapter Engine to convert XML- and HTTP-based messages
to the specific protocol and format required by these systems and the other way around For specific
senderreceiver combinations messages can be processed without invoking the central Integration
Engine In principle you connect external systems using the adapters that are installed centrally or
non-centrally in Advanced Adapter Engine You can use the Advanced Adapter Engine that is part of
your PI system as a central Advanced Adapter Engine Optionally (for performance reasons) you can
install a non-central Advanced Adapter Engine separately as a system with AS Java and parts of the
usage type PI on a separate host
Adapter Engine (Java SE)
Adapter Engine (Java SE) is a separate software unit You can use it only if you have SAP NetWeaver
systems with usage type PI in your system landscape It has to be installed manually You use the Adapter
Engine (Java SE) to connect to external systems Using the various adapters in the Adapter Engine (Java
SE) XML and HTTP-based messages can be converted to the specific protocol and format required by
such systems and the other way around The Adapter Engine (Java SE) only provides some of these
adapters as a standalone version with restricted functions for operating systems that do not support
SAP NetWeaver PI 71 but that have at least a Java Runtime Environment 50 Therefore you should
use the Adapter Engine (Java SE) only if the platform prerequisites do not allow you to use the Advanced
Adapter Engine
SAP Partner Connectivity Kit
SAP Partner Connectivity Kit (PCK) runs on AS Java with parts of the usage type PI It enables a system
of a smaller company or subsidiary that does not run SAP NetWeaver PI to connect to your SAP
NetWeaver systems
313 Clients
Clients are additional installable programs or tools They reside either on local front-end PCs accessed
by users or on back-end systems where they act as client programs within an SAP NetWeaver system
landscape
The clients that you can use with SAP NetWeaver Process Integration are described in the following
sections
SAP GUI
NOTE
We recommend that you use the following versionsI
SAP GUI for Windows 710 (or higher) with the latest patch level
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 2156
SAP GUI for Java 710 (or higher) with the latest revision
The integrated SAP ITS 710
For more information about the SAP GUI family see SAP Service Marketplace at http
servicesapcomsapgui
SAP offers three different client applications for accessing ABAP applications in SAP systems (such as
SAP NetWeaver systems with usage type AS ABAP) This SAP GUI family consists of
SAP GUI for HTML
SAP GUI for HTML is based on the SAP integrated Internet Transaction Server (ITS) which is
included in the installation of SAP NetWeaver systems as of SAP NetWeaver 2004 On the client
side only a suitable browser (such as Internet Explorer 70 or Firefox 20) and a virtual machine are
required SAP ITS 620 is not compatible with SAP NetWeaver 71
SAP GUI for the Java environment (SAP GUI for Java)
SAP GUI for Java is a generic SAP GUI that covers a variety of platforms
For more information about the installation of SAP GUI for Java see the documentation Installation
Guide ndash SAP Front End
SAP GUI for the Windows environment (SAP GUI for Windows)
SAP GUI for Windows is SAPs universal client for accessing all SAP applications built on ABAP
technology It is available on the Microsoft Windows platform only and offers the broadest feature
set of all members of the SAP GUI family
For more information about the installation of SAP GUI for Windows see the Installation Guide ndash
SAP Front End
SAP NetWeaver Developer Studio
The SAP NetWeaver Developer Studio is SAPrsquos Integrated Development Environment (IDE) for Java
and is based on the open-source tools framework Eclipse 33 With the SAP NetWeaver Developer Studio
you can develop Java EE 5 applications from scratch using the built-in support for new technologies
such as EJB 30 and JSF 12
During the installation of the SAP NetWeaver Developer Studio several features are offered for
installation For SAP NetWeaver PI 71 only the following features are relevant
SAP NetWeaver Developer Studio Platform
SAP NetWeaver Developer Studio Java EE
NOTE
If you want to use one of the other features you need SAP NetWeaver Composition Environment
and a corresponding developers licence
For more information about the installation of SAP NetWeaver Developer Studio see the Installation
Guide ndash SAP NetWeaver Developer Studio 71 or Installation Guide ndash SAP NetWeaver Developer Studio 71 Including
Enhancement Package 1
3 SAP NetWeaver PI Overview
31 Installable Software Units
2256 PUBLIC 2011-04-15
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
SAP enhancement packages are a new way of delivering new functions for SAP NetWeaver This allows
a clear separation between the delivery of new functions on the one hand and corrections legal changes
and security updates on the other hand (in Support Package stacks) SAP enhancement packages are
cumulative an enhancement package always contains the functions of the corresponding predecessor
enhancement packages
Enhancement packages are maintained by their own Support Packages while the main release is in
maintenance
Benefits
SAP enhancement packages offer the following benefits
You have reduced effort for testing and no effort for training when applying Support Packages as
new features are only shipped with enhancement packages
Adding new functions between releases becomes predictable and controllable
New functions can be added successively in small steps There is no need to fully upgrade your
system to get new functions
You have minimal training effort when applying an enhancement package because existing
functions are not replaced
Implementation
There are the following ways to get an SAP NetWeaver system with the release level of SAP enhancement
package 1 for SAP NetWeaver Process Integration 71
New installation of SAP NetWeaver PI 71 including enhancement package 1 using the standard
installation tool SAPinst
Upgrade of an existing SAP NetWeaver system from a release lower than SAP NetWeaver PI 71 to
SAP NetWeaver PI 71 including enhancement package 1 For this you use the upgrade programs
SAPup (for ABAP) and SAPJup (for Java)
Installation of the enhancement package on an existing SAP NetWeaver PI 71 system
For this you use the Software Update Manager (SUM) The Software Update Manager evolved
from the previously used SAP Enhancement Package Installer The tool has been renamed to reflect
its broader use for example you can also use it for applying Support Package Stacks to your system
On the ABAP side the Software Update Manager uses a system cloning and switch procedure for
installing enhancement packages It installs a copy of the system the shadow system parallel to
the original system This shadow system is used to update the relevant software components and
to install the additional components while the original system is still in production operation At
a certain point during downtime the switch to the new system is made and afterwards any parts
of the original system that are no longer needed are deleted The enhancement package installation
in a Java system uses a deploy-based procedure that is no shadow system is used The Software
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2011-04-15 PUBLIC 2356
Update Manager requires a stack configuration file (xml file) as input file for the enhancement
package installation procedure This file lists all the packages that are to be installed in your systems
The stack configuration file is generated when you download the required packages
As the Software Update Manager is updated regularly we recommend to always use the latest
version It is delivered as part of the SL toolset For more information see http
servicesapcomsltoolset
For an overview of all required steps for the enhancement package installation process and
corresponding documents see Process Overview Installation of Enhancement Package 1 on an Existing SAP
Netweaver PI 71 System [page 28]
Content of SAP Enhancement Package 1 for SAP NetWeaver PI 71
With enhancement package 1 for SAP NetWeaver PI 71 new features are introduced and some existing
are changed The following is a selection of some of the most important enhancements
Enhanced design and modelling options in the Enterprise Services Repository
New services registry
Support for new Web services standard (Web Services Reliable Messaging)
New modules for the Advanced Adapter Engine
Use of shared memory of the ABAP Application Server for message processing
For more information about the changes see SAP Library [page 12] at Whatacutes new in SAP NetWeaver PI 71
ndash Release Notes
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2456 PUBLIC 2011-04-15
4 SOA-Based Integration Use Case
41 Overview
You can use SOA-based integration to set up the communication between service providers and service
consumers in both application-to-application and business-to-business scenarios and to execute
operate and monitor the communication at runtime SOA-based integration covers both direct (point-
to-point) as well as mediated (via an Integration Server) communication between service providers and
service consumers
The use case spans the whole life cycle of a SOA-based integration scenario including
Scenario modeling and service design in the Enterprise Services Repository
Implementation of the service provider and consumer in the back-end systems
Configuration and finally execution monitoring and operation of the integration scenario
For scenarios using Integration Server or broker-based communication the configuration of the
different connectivity options (for example SOAP RFC Web Services Industry standards and JDBC)
and their enhancements is covered
For more information see the following documents
Service-Enabling with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdnsoa-modeling
Getting Started
Service-Enabling a Legacy Application with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdn
soa-servicebus Getting Started
In the following you will find information about the installation of the involved software units
42 System Landscape
The following figure shows the system landscape for this use case
4 SOA-Based Integration Use Case
41 Overview
2011-04-15 PUBLIC 2556
Figure 5 SOA-Based Integration
It is mandatory to have a dedicated PI system This applies to development quality and production
landscapes
For PI it is a prerequisite that no other system in your system landscape has a higher release than
the PI system For exceptions to this rule see SAP Note 1043047 For example SAP XI 30 is compatible
with SAP NetWeaver 640 and 70 application systems since the same XI protocol is used Apart
from these exceptions if you want to upgrade or install an application in your system landscape
you first have to make sure that the PI system is on the same release level If required you have to
upgrade the PI system first to the new or a higher release
CAUTION
Although it should be technically possible to run an application system with a higher release
than your PI system in your system landscape this is not supported by SAP (apart from the
exceptions listed in SAP Note 1043047) Therefore you run such a landscape at your own risk
You can use the Advanced Adapter Engine that is part of your PI system as a central Advanced
Adapter Engine
Adapter Engine (Java SE) can be installed in a non-SAP Java environment However it only hosts
a subset of the adapter functionality is only supported for compatibility reasons and should be
used only if this is a precondition in your environment
Optionally you can use the Change Management Service (CMS) of an SAP NetWeaver 70 system
with usage type DI to transport design objects and repository objects For more information see
the SAP Library [page 12] at Administratoracutes Guide Technical Operations for SAP NetWeaver Administration
of SAP NetWeaver Systems PI (Process Integration) Software Logistics Transporting ESR Content and Objects
of Integration Directory PI Transports Using the Change Management Service (CMS)
Smaller business partners or subsidiaries that do not run SAP NetWeaver install SAP Partner
Connectivity Kit in their system landscape SAP Partner Connectivity Kit enables XML document
4 SOA-Based Integration Use Case
42 System Landscape
2656 PUBLIC 2011-04-15
exchange between your SAP NetWeaver systems and the partner systems Since SAP Partner
Connectivity Kit gets installed in their system landscape it is not shown in the system landscape
figure above
The AS ABAP system acts as an application and service provider For Java Web Services you also
require AS Java In addition you require SAP NetWeaver Developer Studio on the client side as a
development environment
The Web service client can be either an SAP or a non-SAP application For example an AS ABAP
system or a Web browser could act as application or service consumer
You can install SAP Conversion Agent by Informatica in the system with usage type PI or on a host
where SAP Partner Connectivity Kit is installed or on a host where neither usage type PI nor SAP
Partner Connectivity Kit is installed
43 Implementation Sequence
Procedure
To install this use case perform the steps listed in the following table
StepAction[Corresponding Documentation] Remarks
1 Make sure that you have performed the preparation steps You have planned your system landscape [page 33]
(that is you have decided how many systems you require how you want to use each of these systems and which standalone engines and clients you require)
With the help of your hardware partner you have mapped your systems and standalone engines to properly sized hosts
You have planned and installed shared services [page 35]
2 Installation of system with usage type PI (includes the installation of AS ABAP and AS Java)
NOTE
For usage type PI a Unicode installation is mandatory
[Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt]
If you want to use the features of enhancement package 1 use the direct installation of SAP NetWeaver PI 71 including enhancement package 1
Make sure that you perform the configuration steps as described in the installation guide For certain usage types configuration tasks can be applied by the configuration wizard These configuration tasks as well as any additional configuration steps for your use case are listed in SAP Solution Manager For more information
4 SOA-Based Integration Use Case
43 Implementation Sequence
2011-04-15 PUBLIC 2756
StepAction[Corresponding Documentation] Remarks
see the Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt
3 Install the Adapter Engine (Java SE) engines if required[Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
4 To integrate small business partners and subsidiaries the business partners or subsidiaries install SAP Partner Connectivity Kit running on AS Java with parts of usage type PI in the business partners or subsidiarys system landscape[Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
5 Install SAP Conversion Agent by Informatica if required[SAP Library [page 12] at Function-Oriented View Process Integration SAP Conversion Agent by Informatica Deploying and Using Conversion Agent ]
6 Installation of clients SAP GUI
[Installation Guide ndash SAP Front End]
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
The process sequences give a comprehensive overview of the steps relevant for the enhancement
package installation on an existing SAP NetWeaver PI 71 system
The process sequence is divided into a planning phase and an implementation phase Each step in both
phases contains references to the corresponding documentation to ensure that you can easily find the
information you need
Process
NOTE
To download the enhancement package files and required Support Packages you require the SAP
Solution Manager Maintenance Optimizer You have the following options
Manual Selection
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2856 PUBLIC 2011-04-15
You manually select the required files from SAP Service Marketplace at http
servicesapcomswdc using the SP Stack Application You use the Maintenance Optimize
only to approve the packages which is a prerequisite for the download
Automatic Calculation
The Maintenance Optimizer supports the download of a consistent queue that includes all
necessary Support Packages and enhancement packages In addition SAP Solution Manager
calculates a valid import queue for the selected SAP system and generates the enhancement
package stack configuration file that you require for the installation
As a prerequisite the system that you want to update needs to be maintained correctly in
SAP Solution Manager System Landscape As the Maintenance Optimizer uses this data for
the calculation it is crucial that the data is up-to-date In addition the SAP Solution Manager
system requires a Minimum Support Package level (see below)
Planing PhaseStep Description Documentation
Hardware amp Software Prerequisites
Check which platforms are supported for your target release (OSDB dependencies)
Product Availability Matrix (PAM) at httpservicesapcompam
Check which hardware sizing is required for your target release
Sizing information at httpservicesapcomsizing
Solution Manager Prerequisites
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of the required software packages you have to make sure that your SAP Solution Manager system has the required Support Package levelAt least SAP Solution Manager 70 EHP1 Support Package Stack 17 is required We recommend to use SAP Solution Manager 70 EHP1 Support Package Stack 23Check if you need to do an update or upgrade of your SAP Solution ManagerMake sure that you run the guided procedure SOLMAN_SETUP after every installation or update of SAP Solution Manager and that it completes successfully
For upgrades from source release SAP Solution Manager 31 and 32Upgrade Guide ndash SAP Solution Manager 70 incl Enhancement Package 1For updates from SAP Solution Manager 70Update Guide SAP Enhancement Package 1 for SAP Solution Manager 70Follow-up activities after an Support Package Stack update or enhancement package updateSolution Operations Guide ndash SAP Solution Manager 70 EHP1 section Software Change Management All guides are available at http
servicesapcom instguides SAP Components SAP Solution Manager -gt Release 70 EHP 1
Implementation PhaseStep Description Documentation
1Solution Manager Preparation
Configure the SAP Solution Manager Maintenance Optimizer
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of software packages make sure your
Configuration of Maintenance Optimizer http
helpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Change Request Management and Change ControlMaintenance Optimizer
Prerequisites
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 2956
Implementation PhaseStep Description Documentation
system landscape data in SAP Solution Manager is maintained correctlyLandscape Verification 10 which is an add-on to SAP Solution Manager can support you in maintaining your system landscape data The use of this tool is optional
Landscape Verification http
wwwsdnsapcom irj
sdn alm-update-
management link Landscape Verification under Related Areas on Upgrade and Update Management (in the right column)
SAP Note 1468605 (Installation of Landscape Verification)
Maintaining System Landscape Information [page 47]Note that the information provided in this section is based on SAP Solution Manager 70 EHP1 SP23
2System Preparation
Prepare your system as described in the documentation for example perform OS DB specific preparations and the PI-specific preparations
Update Guide ndash Update of SAP Systems with Software Update Manager sections Planning and Preparation
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
3Software Download
Select and download the software packages in either of the following ways Automatic calculation Create
a maintenance transaction in the Maintenance Optimizer and choose the Calculate Files Automatically option
Manual Selection Create a maintenance transaction in the Maintenance Optimizer and choose the Select Files Manually option You then can select the files manually using the SP Stack application in SAP Service Marketplace
NOTE
You have to download the stack configuration file manually after you have selected all files in the SP Stack
httphelpsapcom SAP Solutions SAP Solution Manager
SAP Solution Manager 70 EHP1 ltSPgtChange Request Management and
Change Control Maintenance Optimizer Maintenance Procedure Scenarios
For information about the automatic calculation see Maintenance Transaction with Installation of an Enhancement PackageFor information about the manual selection and approval process see section Approve and Download Files in Download Basket
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
3056 PUBLIC 2011-04-15
Implementation PhaseStep Description Documentation
application Choose Generate Stack XML and save the file
4Enhancement Package Installation
Run Software Update Manager to update your system with the selected software packages
Update Guide ndash Update of SAP Systems with Software Update Manager
5Follow-Up Steps
Perform technical and PI-specific follow-up activities after the enhancement package installation is done
Update Guide ndash Update of SAP Systems with Software Update Manager section Follow-Up Activities
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
6Configuration
Configure newly installed enhancement package functions using SAP Solution Manager content
See Systems with Usage Types [page 16] section Configuration of Systems with Usage Types
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 3156
This page is left blank for documents that are printed on both sides
5 System Landscape
51 Planning Your System Landscape
The installable software units that make up your system landscape depend on the functions that you
want to implement For information about the features see systems [page 16] standalone engines [page 19]
and clients [page 21]
In addition you have to determine the required shared services [page 35] (such as SAP Solution Manager
or SAP NetWeaver Administrator) that run on central systems in your system landscape and the
landscape aspects relevant for their implementation
In the following you will find general information that you should consider when planning your system
landscape
Sizing
You have to map systems and standalone engines to hosts after you have a clear picture of the following
Which systems and standalone engines you require
How many systems you require and how you want to use each of these systems
NOTE
No general guideline can be given for the sizing of your landscape since this relies heavily on your
requirements You should therefore perform this task together with your hardware partner and
your technical consultant
For information about sizing your systems you can use the following information sources
Your first point of reference is the Quick Sizer
SAP built the Quick Sizer as an online sizing questionnaire Internet application in close cooperation
with its hardware partners This tool delivers general sizing categories based on your volume load
estimates The results provide an objective basis for sizing independent of platform and
configuration
For more information see SAP Service Marketplace at
httpservicesapcomsizing for the SAP NetWeaver PI 71 sizing guide available under
Sizing Guidelines Business Suite amp Services
httpservicesapcomquicksizer for more information and access to the tool itself
Also consider the following important aspects concerning sizing
High availability
5 System Landscape
51 Planning Your System Landscape
2011-04-15 PUBLIC 3356
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Technical Infrastructure High Availability
Unicode
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Internationalization
Contact your hardware partner to find out the appropriate number of sized hosts
The platform-independent abstract results of the Quick Sizer can be used by any of our hardware
partners to create a concrete offer SAP itself does not make any hardware recommendations the
responsibility for sizing and detailed hardware configuration lies with the hardware partners
Figure 6 Example of Mapping of Systems and Standalone Engines to Three Hosts
NOTE
Optionally you could also distribute single systems to multiple hosts For example you could
decide to install the database instance of an SAP system on a separate host for performance
reasons or distribute other system instances to achieve high availability
To provide a mapping that fits your required functions and performance your hardware partner
and your technical consultant have to identify the number of required instances of SAP NetWeaver
find out how to distribute these instances to hosts and what functions will run on which instance
Therefore the hardware partner and the technical consultant have to consider many different
aspects such as
Number of required SAPS (SAP Application Benchmark Performance Standard) for each
system (provided by Quick Sizer)
Landscape-relevant aspects concerning security For more information see the SAP Security
Guide in the SAP Library [page 12] at Administratoracutes Guide Security Guide
Landscape-relevant aspects concerning scalability high availability operation and software
life-cycle management
5 System Landscape
51 Planning Your System Landscape
3456 PUBLIC 2011-04-15
For more information about relevant aspects for the mapping of systems to hosts see the document
Technical Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
Scaling and Distribution Options
You may need to design your system landscape for a large number of users SAP NetWeaver PI offers
you different means of scalability The following list provides you with some examples
You could install multiple systems of one type and use them for different purposes
You could scale every system by installing dialog instances or by distributing the database instance
For more information about distribution options on the instance level see the Technical
Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
For every SAP system you could additionally install Web Dispatcher For more information see
the SAP Library [page 12] at FunctionndashOriented View Application Server Infrastructure SAP Web
Dispatcher
You could further distribute certain standalone engines ndash for example Search and Classification
(TREX) is based on a flexible architecture that supports a distributed installation For more
information see the Technical Infrastructure Guide ndash SAP NetWeaver PI 71 available in SAP Service
Marketplace at httpservicesapcominstallNWPI71
52 Shared Services
You normally run shared services on central systems in your system landscape The following features
could be used for SAP NetWeaver Process Integration to realize shared services
SAP Solution Manager
Used to implement train test maintain monitor control change and manage incidents of your
SAP solution system landscape (open end-to-end application management)
As of SAP Solution Manager (70) 40 Support Package 15 SAP Solution Manager has become the
platform for SAPs end-to-end solution operations strategy Functions for complete application
management has been combined with administrative tools and has been merged in newly created
role based work centers
NOTE
Be aware that you require an SAP Solution Manager system to install or upgrade to SAP
NetWeaver 70 and higher An SAP Solution Manager system is required to generate the SAP
Solution Manager key needed during the installation or upgrade process Without this key
the installation or upgrade process cannot continue
For SAP NetWeaver Process Integration you require SAP Solution Manager 70
For more information see SAP Note 805390
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3556
Solution Manager Diagnostics
An integral part of SAP Solution Manager that is running as a Java application on the Java stack of
SAP Solution Manager 70 Solution Manager Diagnostics is used to analyze the root cause of
incidents in your landscape in an efficient and safe way Before Go-Live Solution Manager
Diagnostics has to be set up and made accessible remotely
SAP NetWeaver Administrator
SAP NetWeaver Administrator is the central administration component which is used for
monitoring and administering Java applications It is included in SAP NetWeaver systems with AS
Java
SAP NetWeaver Administrator exists in the following flavors
A local mode which runs out of the box and which focuses on administrating the underlying
SAP NetWeaver AS Java
NOTE
For a SAP NetWeaver PI 71 it has a special role which you need to activate using a
configuation wizard
A central mode which has to be configured before use and which deals with the system
landscape management
SAP has decided to merge the central mode of SAP NetWeaver Administrator into the new work
centers available as of SAP Solution Manager 70 SP 15 Thus it can be used in an administrative
context together with non-Java-based administration tools Although the central mode of SAP
NetWeaver Administrator will be still available for some time SAP will not develop this tool any
further SAP focuses on optimizing the administrative work centers of SAP Solution Manager
instead
The local mode of SAP NetWeaver Administrator stays untouched It is available for current and
future releases of SAP NetWeaver
SAP Central Process Scheduling by Redwood
SAP Central Process Scheduling application by Redwood enables central job scheduling and job
monitoring of current and old releases of AS ABAP systems (as of Basis Release 31) This application
is fully integrated in SAP NetWeaver Depending on the business needs SAP business applications
are the initial trigger for scheduled activities You can now manage jobs and job chains conveniently
using a graphical user interface
System Landscape Directory
The System Landscape Directory is the central directory of system landscape information relevant
for the management of your software life-cycle It contains a description of your system landscape
(that is software components that are currently installed) and a repository of software components
that can theoretically be installed in your landscape (such as the software components available
from SAP)
Adaptive Computing Controller
5 System Landscape
52 Shared Services
3656 PUBLIC 2011-04-15
The Adaptive Computing Controller enables users to control an adaptive computing landscape
from a single point through observation operation and dynamic resource distribution With
adaptive computing hardware software and system services are able to adapt to changing business
needs In the Adaptive Computing Controller the run-time data of logical and physical landscapes
can be monitored application services can be startedstoppedrelocated and hardware resources
can be assigned to application services The operation can also be mass executed and be planned as
tasks to be executed
For more information about the installation of the Adaptive Computing Controller tool see the
document Installation Guide ndash Adaptive Computing Controller in SAP NetWeaver 71 available on SAP Service
Marketplace at httpservicesapcominstallNWPI71
For more information about Adaptive Computing in general see httpsdnsapcomirj
sdnadaptive
521 Use Cases
You can use the applications and tools described above for use cases that are normally performed
centrally The following sections describe these use cases
5211 End-to-End Solution Operations
Running business applications through their complete life-cycle is a challenge Therefore SAP has
started the Run SAP methodology for implementing End-to-End Solution Operations Based on a set
of SAP standards a roadmap and a package for training and certification Run SAP helps customers to
facilitate End-to-End Solution Operations
You can download the SAP standards for Solution Operations from SAP Service Marketplace at http
servicesapcomsupportstandards They describe roles customers typically have in their IT
environment For optimal role support SAP has grouped existing and new functions in SAP Solution
Manager work centers as of SAP Solution Manager 70 Support Package 15 Operations aspects are fully
covered by adding administrative functions for SAP NetWeaver as well Work centers are ABAP Web
Dynpro-based applications They offer the following advantages
Easy to use similar look and feel
Context transfer while jumping from one work center into another
Logical grouping of tools for a certain area
Simple authorization concept
Easy to expand
Each IT role belongs to one or more work centers For instance the Technical Administrator IT role is
covered by the work centers for System Monitoring System Administration and Landscape Management
The following work centers are available
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3756
Business Process Operations
Change Management
Root Cause Analysis
Implementation Upgrade
Incident Management
Test Management
Job Management
System Landscape Management
Solution Documentation Assistant
SAP Engagement and Service Delivery
SAP Solution Manager Administration
System Administration
System Monitoring
My Home is the central point of access to all important data of almost all work centers in SAP Solution
Manager
5212 Support Infrastructure
A key requirement for effective support of IT solutions is the ability to perform root cause analysis with
speed and efficiency
With SAP Solution Manager SAP has long had an infrastructure in place for its ABAP applications that
efficiently supports SAP solutions This helps ensure the high availability and smooth running of
business processes For more information see the SAP Solution Manager section
With Solution Manager Diagnostics this knowledge has been extended to Java applications If for
example homegrown Java applications cause instability Solution Manager Diagnostics helps trace the
cause to eradicate the problem rapidly Solution Manager Diagnostics is fully integrated into SAP
Solution Manager 70 Solution Manager Diagnostics also contains two third-party tools CArsquos Wily
Introscopereg for measuring performance as well as troubleshooting problems of the Java EE Engine
and applications running on it and Mercury Loadrunnerreg which enables SAP Support to produce a
defined load in the SAP solution landscape remotely For more information see Solution Manager
Diagnostics [page 43]
The support infrastructure provides SAP Support with safe access to your productive landscape for safe
root cause analysis so ensuring that SAP Support does not change your landscape inadvertently You
require a support infrastructure to run SAP NetWeaver
The following figure shows the overall infrastructure including SAP NetWeaver administration tools
that are used by administrators or operators at the customer site
5 System Landscape
52 Shared Services
3856 PUBLIC 2011-04-15
Landscape Aspects
If you use SAP NetWeaver Process Integration 71 productively besides SAP Solution Manager (as a
central support platform) you have to set up Solution Manager Diagnostics for supportability reasons
Implementation Sequence
For information about the implementation of the support infrastructure see the document Master
Guide ndash SAP Solution Manager 70 available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution Manager ltReleasegt
5213 Collection of Landscape Data
Amongst other applications and services the support infrastructure and the SAP NetWeaver
administration tools rely on system landscape data
For SAP NetWeaver PI 71 you have to run non-ABAP components in your solution landscape
Therefore the System Landscape Directory is mandatory The landscape data that is automatically
gathered by the System Landscape Directory is replicated to SAP Solution Manager There are several
topology options for the System Landscape Directory They offer different grades of availability
administration and operation effort
For more information see the System Landscape Directory section
5214 Authentication and Single Sign-On
Before implementing your system landscape plan how to implement authentication and how to
integrate different systems into a Single Sign-On landscape Single Sign-On reduces complexity for end
users saving them valuable time while also reducing administration effort for resetting passwords
thereby contributing to TCO reduction
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
5215 Integrated User and Access Management
In a system landscape containing a combination of ABAP and Java components we recommend that
you integrate your user and access management so that you can use the same user data across different
systems administer this data centrally and control access to data SAPs mature fine-grained
authorization concept allows detailed control of access rights SAP NetWeaver provides both ABAP and
Java-based user management solutions The user management solution that you use to administer
your user data depends on factors such as the type of systems that are running in your landscape
If you want to use central user administration we recommend that you run it in a non-production
system If you do not have a central user administration yet you can for example realize it in the SAP
Solution Manager system
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3956
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
522 Examples for the Overall System Landscape of Shared Services
In this section we provide examples of how shared services can be set up depending on the system
landscape they are intended for The following examples aggregate the landscape aspects given in the
Use Cases section
NOTE
The following sections and the figure mostly do not show information about the life-cycle of
shared services For example you may also need a development and testquality assurance system
for SAP Solution Manager You should consider this aspect in addition to the information given
in this section based on your requirements
Small and MediumndashSized Customer Landscapes with Java
As you use Java productively for SAP NetWeaver PI 71 besides SAP Solution Manager you have to set
up additional components for optimal monitoring administration and support Solution Manager
Diagnostics and the central mode of SAP NetWeaver Administrator are already fully integrated into
SAP Solution Manager 70 as the central operations hub For SAP Process Integration you must also
set up SAP NetWeaver Administrator with a special role
We recommend that you do not install SAP Central Process Scheduling in the SAP Solution Manager
system You have to set up and operate the system which hosts your productive scheduler as a mission
critical system
In the SAP Solution Manager system you should set up a local System Landscape Directory in addition
to a central runtime System Landscape Directory This way you have a clear separation between your
management system (SAP Solution Manager) and managed systems in your landscape In addition
SAP Solution Manager then does not rely on a System Landscape Directory running in the production
environment For this setup configure the SLD data suppliers of your SAP Solution Manager system
to send data to the central runtime System Landscape Directory In addition configure automatic
bridge forwarding from your runtime System Landscape Directory to the local System Landscape
Directory For more information see the Planning Guide - System Landscape Directory
If you want to use a central system for Adobe Document Services we recommend that you install a
dedicated system for this purpose in your production environment For detailed information about
the sizing of the system for the different use cases see the Sizing Guide for Adobe Document Services at
SAP Service Marketplace at httpservicesapcomsizing Sizing Guidelines Solutions amp
Platform
We recommend that you start with this centralized SAP Solution Manager approach as depicted in the
following figure
5 System Landscape
52 Shared Services
4056 PUBLIC 2011-04-15
Figure 7 Single SAP Solution Manager Landscape
Large Customer Landscapes with Java
Large customers who have environments in their landscape that are large and distributed administered
by different groups or separated for security reasons can consider a distributed operations setup In
addition to the centralized setup described for small- and medium-sized customers above large
customers can put parts of the central management functions on extra hosts or systems for performance
or policy reasons You have the following options for a distributed setup
You may set up an extra system or client for Central User Administration (CUA)
The Change and Transport System (CTS) can run on an extra system However it is not
performance- or data-intensive
You may set up an extra system for central CCMS monitoring Depending on the customizing
and on the landscape size central CCMS may generate a lot of system load You can connect a
separate central CCMS to SAP Solution Manager for displaying alerts in the alert inbox of the System
Monitoring work center
You can use a separate SAP NetWeaver 70 system with usage type BI together with SAP Solution
Manager This may make sense with respect to the amount of landscape management data that is
stored for reporting purposes The amount of data strongly depends on the data granularity
storage time frame and landscape size
You can easily put Wily Introscope Enterprise Manager on an separate host
Other aspects described above for small- and medium-customers (such as the setup of the System
Landscape Directory) are also valid for large customers
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4156
523 Feature Details
This section provides further information about the features described above
5231 SAP Solution Manager
SAP provides you with SAP Solution Manager as the strategic application management platform and
to enable the collaboration between you and SAP You need to install at least one productive SAP
Solution Manager in your system landscape To ensure the availability of this application management
platform an SAP Solution Manager system is technically required to install or upgrade to SAP
NetWeaver 70 or higher If you are already using SAP Solution Manager you can also use it to manage
the solution you build with SAP NetWeaver In this case we highly recommend that you update SAP
Solution Manager to the latest version
As of SAP Solution Manager 70 SP15 you can use the newly created work centers
NOTE
During the SAP system installation or upgrade process you are prompted to enter the SAP
Solution Manager key An SAP Solution Manager system is required to generate this key Without
this key the installation or upgrade process cannot continue
You may generate all needed keys for your entire system landscape (development quality
assurance and production system) in one SAP Solution Manager system In case you plan to install
several solution landscapes (for example in different countries) one SAP Solution Manager
system is still sufficient
For more information see SAP Note 805390
It is possible to install multiple SAP Solution Managers If you do so they should host separate business
solutions
If you want to reduce the risk of unavailability you should not install SAP Solution Manager as a central
component Instead you can operate a 2-system-landscape with both a test and production
environment of SAP Solution Manager (especially if you are using time-critical functions like Support
Desk) If you also develop your own content a 3-system-landscape with a development test and
production environment is recommended
For more information about SAP Solution Manager see the following table
Topic Where to Find More Information
System infrastructure scenarios installation and configuration of SAP Solution Manager
Master Guide ndash SAP Solution Manager available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution ManagerltReleasegt
Benefits and usage scenarios SAP Solution Manager ndash Learning Maps available on SAP Service Marketplace at http
5 System Landscape
52 Shared Services
4256 PUBLIC 2011-04-15
Topic Where to Find More Informationservicesapcomrkt-solman or https
servicesapcomsolutionmanager
Additional information See SAP Service Marketplace at http
servicesapcomsolutionmanager
5232 Solution Manager Diagnostics
Solution Manager Diagnostics provides efficient and safe root-cause analysis of incidents in customer
solutions powered by SAP NetWeaver It can help monitor on operating systems databases Java
application activities performance and logs It also supports the reporting of software and
configuration changes that can lead to malfunctions and errors
You must run one Solution Manager Diagnostics within your SAP solution landscape if you run
applications based on SAP NetWeaver systems with usage type AS Java Agents are responsible for
delivering the data from all productive hosts within your system landscape to the Solution Manager
Diagnostics system
CAUTION
SAP Support performs root-cause analysis on incoming incidents with Solution Manager
Diagnostics Not installing and configuring this support infrastructure results in a dramatically
reduced service level
Solution Manager Diagnostics is fully integrated into SAP Solution Manager 70
Solution Manager Diagnostics also contains Wily Introscope (Display Server and Agent part) for
measuring performance as well as to troubleshoot problems of Non-ABAP applications Wily Introscope
is heavily used for troubleshooting applications running on AS Java
SAP has signed a distribution agreement for Wily Introscope SAP customers are allowed to use this
tool in a preconfigured way
For more information about Solution Manager Diagnostics and an FAQ list see SAP Service Marketplace
at httpservicesapcomdiagnostics
5233 System Landscape Directory
The System Landscape Directory (SLD) of SAP NetWeaver is the central directory of system landscape
information relevant for the management of your software life-cycle
NOTE
Note that the abbreviation SLD is not intended to define a product since the System Landscape
Directory is part of SAP NetWeaver This abbreviation is solely intended to improve readability
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4356
The System Landscape Directory contains a description of your system landscape (that is software
components that are currently installed) and a repository of software components that can
theoretically be installed in your landscape (such as the software components available from SAP)
Since this data gets updated automatically the System Landscape Directory provides reliable and up-
to-date system landscape information with as little effort for you as possible In this way the System
Landscape Directory acts as a central information provider for SAP and third-party tools that use this
data to deliver the services you need to keep your landscape up and running
For the System Landscape Directory as part of an SAP NetWeaver PI 71 landscape consider the following
aspects
Part of SAP NetWeaver PI 71 is a new version of the System Landscape Directory It is automatically
included in every SAP NetWeaver 71 system with usage type AS Java It offers enhanced functions
such as a full automatic synchronization mechanism for all data stored in it That is both data
delivered by data suppliers and data entered or changed manually in the System Landscape
Directory can be synchronized automatically This synchronization offers the following
A fully automated mechanism so no user interaction is required and conflicts are resolved
automatically
Asynchronous propagation of information so some nodes may be down temporarily
Communication over HTTP protocol
Uni- and bi-directional synchronization
Depending on your use case the full automatic synchronization could significantly reduce manual
synchronization effort
For SAP NetWeaver PI 71 the configuration of the system landscape directory and its data suppliers
is already included in the standard implementation procedure with SAPinst For existing systems
you only have to perform some quick and easy configuration actions to start operating the system
landscape directory server in an AS Java system
For SAP NetWeaver PI 71 you have the following options concerning SLD
Option 1
Run SAP NetWeaver PI 71 against an existing SLD running on SAP NetWeaver 70 We only
recommend this for upgrades from SAP NetWeaver 70 if you have a central SLD in operation
not running on one of your PI systems
Option 2
Use the SLD included in an SAP NetWeaver PI 71 system We recommend this option for new
installations and upgrades from older releases than SAP NetWeaver 70 due to the enhanced
functions and improved performance of SLD 71
NOTE
If you already have a central SLD running on SAP NetWeaver 70 in operation you could run
two SLD versions in parallel ndash SLD running on SAP NetWeaver 71 for your PI systems and
SLD running on SAP NetWeaver 70 for all other systemsuse cases This way your SAP
5 System Landscape
52 Shared Services
4456 PUBLIC 2011-04-15
NetWeaver PI 71 systems would benefit from the new features while it would be easy to set
up and operate such an SLD landscape For this purpose you could use the new fully
automatic synchronization This feature enables the automatic forwarding of all SLD data
from an SLD running on SAP NetWeaver 70 to an SLD running on SAP NetWeaver 71 As a
result there is no need to adapt most existing systems as their SLD data suppliers could still
send their data to the central SLD In brief the following steps would be required
1 Put SLD in a PI system into operation (part of standard implementation procedure)
2 Configure PI systems to use the new SLD (part of standard implementation procedure
for new PI systems)
3 Set up the fully automatic synchronization from your old SLD to your new SLD
As soon as an upgrade or an installation of a standalone AS Java 71 system is available you
could move your central SLD also to SAP NetWeaver 71 Then you could optionally shift
your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems
Figure 8
We recommend that you use a Domain Name System (DNS) alias so that you are able to switch to
another System Landscape Directory easily For example if customers build a new landscape they
normally start with a sandbox environment Over time more and more environments are set up
Once the production environment is in place move the System Landscape Directory there To do
this you can configure a new System Landscape Directory in the production environment
synchronize it with the old System Landscape directory and switch to the new one
Topology
Apart from the considerations above the System Landscape Directory offers several topology options
with different grades of availability at the expense of low administration and operation effort There is
no generic rule therefore on how to set up a System Landscape Directory in your system landscape
To find the topology and synchronization strategy for the System Landscape Directory that fits your
requirements concerning the System Landscape Directory availability (and hence the availability of
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4556
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
2 Before You Start
21 SAP Notes
You must read the following SAP Notes before you use this Master Guide and implement SAP NetWeaver
Make sure that you have the up-to-date version of each SAP Note which you can find on SAP Service
Marketplace at httpservicesapcomnotes
NOTE
The SAP Notes related to SAP NetWeaver PI 71 are also listed on SAP Service Marketplace at
httpservicesapcomsapnotesnwpi71
List of Important SAP Notes
SAP Note Number Title Description
1004107 Release Restrictions for SAP NetWeaver PI 71
Some restrictions apply to the productive use of SAP NetWeaver PI 71 These are documented in this SAP Note
1247043 Release Restrictions for SAP EHP1 for SAP NetWeaver PI 71
Some restrictions apply to the productive use of enhancement package 1 for SAP NetWeaver PI 71 These are documented in this SAP Note
22 More Information
The following table contains links to information available on SAP Service Marketplace or in the SAP
Library which is important for implementing SAP NetWeaver
Content Location on SAP Service Marketplace or in SAP Library
The latest version of the installation and upgrade guides for SAP NetWeaver Process Integration
httpservicesapcominstguidesnwpi71
Information about supported platforms (operating systems databases browsers) for all SAP NetWeaver components
httpservicesapcomplatforms Product Availability Matrix
Sizing of SAP NetWeaver httpservicesapcomsizing
Information about security SAP Security Guide See the SAP Library [page 12] at Adminitstratoracutes Guide Security Guide
Information about the technical operation of SAP NetWeaver
Technical Operations Manual See the SAP Library [page 12] at Adminitstratoracutes Guide Technical Operations for SAP NetWeaver
2 Before You Start
21 SAP Notes
2011-04-15 PUBLIC 1156
Content Location on SAP Service Marketplace or in SAP Library
Information about SAP NetWeaver PI Support Package Stacks
httpservicesapcomnetweaver SAP NetWeaver PI 71- Release-Specific Information Support Package Stacks Information
Information about installing SAP NetWeaver Support Package Stacks
httpservicesapcomMaintenanceNWPI71
Support Package Stack Guide ndash SAP NetWeaver
23 Accessing the SAP Library
For more information about SAP NetWeaver Process Integration access the SAP Library from any of
the following
SAP Help Portal at httphelpsapcomNWPI71 SAP NetWeaver Process Integration 71 Library
ltLanguagegt SAP NetWeaver Process Integration Library
CAUTION
The SAP Help Portal contains the latest version of the SAP Library Therefore we recommend
that you use this channel to access the SAP Library
An SAP system if you have installed the online documentation Choose Help SAP Library
The browser starts
The help files on the online documentation CDs or DVDs
If you want to view the help files in HTMLHelp format from the online documentation CDs or
DVDs you need a PC running Microsoft Windows to install the HTMLHelp Viewer
2 Before You Start
23 Accessing the SAP Library
1256 PUBLIC 2011-04-15
3 SAP NetWeaver PI Overview
Introduction
SAP NetWeaver PI 71 is part of the SAP NetWeaver technology platform The complete offering of the
SAP NetWeaver technology platform is visualized in the SAP NetWeaver technology map which you
can access at httpsdnsapcomnetweaver SAP NetWeaver at a Glance The technology map
enables you to drill down from top-level technology areas (for example Lifecycle Management) to
individual capabilities (for example Administration Monitoring and so on)
SAP NetWeaver PI includes the following capabilities
Repository-based Modeling and Design
Service Bus-based Integration
SOA Management
A different view is introduced by the end-to-end use case concept This concept offers an
implementation view on SAP NetWeaver to structure and facilitate your implementation
A use cases is a process that typically involves several SAP NetWeaver capabilities It is not limited to a
single component or capability A use case guides you through the different phases of your
implementation project ndash from information through installation to the configuration phase This
implies that a uses case addresses several user roles administrator power user and end user
This document describes the SOA-based integration use case
Architecture Principals
The architecture of SAP NetWeaver Process Integration 71 (SAP NetWeaver PI 71) is based on an
established architecture for realizing cross-system business processes and is a further development of
lower releases (SAP NetWeaver 70 usage type Process Integration and SAP XI 30 as part of SAP
NetWeaver 2004) SAP NetWeaver PI 71 plays an important role in supporting an service-oriented
architecture (SOA) The focus is on the service-based integration of applications
SAP NetWeaver PI is based on general standards so as to enable 3rd-party systems to be integrated At
the center of SAP NetWeaver PI is an XML-based communication that uses HTTP (Hyper Text Transfer
Protocol) Irrespective of the scenario used the application-specific contents are transferred in messages
in user-defined XML (eXtensible Markup Language) from the sender to the receiver either via the
Integration Server or directly between the systems involved
The following figure gives an overview of the key capabilities of SAP NetWeaver Process Integration
3 SAP NetWeaver PI Overview
2011-04-15 PUBLIC 1356
Figure 1 SAP NetWeaver PI Key Capabilities Overview
SAP NetWeaver Process Integration 71 enables the integration of the applications of the following
communication parties
B2B Party Any business partners that want to integrate their application with other applications
outside their own system landscape Scenarios that require industry standards are supported as
well as any scenarios that do not adhere to a particular industry standard
SAP Applications that run on SAP systems This includes the processing of events by using the
Business Activity Monitoring (BAM) infrastructure
3rd-Party Application Applications from 3rd-party providers within one system landscape for
example database or file-system-based
3rd-Party Middleware Middleware systems from 3rd-party providers that are required for the
integration of applications within a company and across company boundaries
SAP NetWeaver PI also supports internal company scenarios and cross-company scenarios It enables
you to connect systems from different vendors (non-SAP and SAP) in different versions and
implemented in different programming languages (Java ABAP and so on) to each other Like the rest
of the SAP NetWeaver platform SAP NetWeaver PI is based on an open architecture uses open standards
(in particular those from the XML and Java environments) and offers those services that are essential
in a heterogeneous and complex system landscape
To enable end-to-end SOA development SAP NetWeaver Process Integration 71 offers a Universal
Description Discovery and Integration (UDDI) v3-based Services Registry where providers can publish
service endpoints definitions and associated metadata and consumers can discover the appropriate
services for their scenarios The Services Registry provides capabilities for classifying and browsing
3 SAP NetWeaver PI Overview
1456 PUBLIC 2011-04-15
services using semantic-rich classification systems The Services Registry is part of Application Server
Java (AS Java)
31 Installable Software Units
SAP NetWeaver comprises the following three types of installable software units
Systems that are configured for a specific purpose as indicated by one or more usage types
Standalone engines that provide one specific (server) function in combination with one or more
SAP NetWeaver PI systems
Clients used by (many) people from their local front-end PC to access functions offered by systems
of SAP NetWeaver PI or standalone engines in the system landscape
In the following sections you can find more details about the software units The figure below provides
and overview of the software units
Figure 2 Installable Software Units for SAP NetWeaver PI
For this and other figures in this guide the following legend applies
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1556
Figure 3 Legend
311 Systems with Usage Types
SAP systems are the main building blocks of SAP NetWeaver They are identified by unique SAP system
IDs (SAPSIDs) and configured for a certain purpose as indicated by usage types Usage types have the
following characteristics
They are a structuring element for SAP software on a technical level
Usage Types determine the intended purpose of a system and the role it plays in a given (distributed)
use case
They are realized by installing and configuring a collection of software components
They allow a logical view of the technology platform SAP NetWeaver PI
A usage type may require other usage types in the same system to operate
They can also be run in the same system together with other usage types that are not a prerequisite
How SAP NetWeaver Systems are Used
The following sections describe the usage types and their dependencies for SAP NetWeaver PI
Application Server ABAP (AS ABAP)
Purpose
AS ABAP is used to provide the ABAP foundation of SAP NetWeaver PI
Application Server ABAP provides a complete development and runtime environment for ABAP-based
applications It is optimized for the development of highly scalable business applications The ABAP
development and runtime environment makes it possible to develop complex business applications
3 SAP NetWeaver PI Overview
31 Installable Software Units
1656 PUBLIC 2011-04-15
without having to worry explicitly about technical details such as process or memory administration
multi-user capability database connections or similar issues These are provided in the basis services or
are integrated directly in the ABAP runtime The application development is similarly independent of
the underlying platform The application server decouples the application coding completely from the
operating system and database that are used
Dependencies
AS ABAP can be combined optionally with other usage types in one system
Application Server Java (AS Java)
Purpose
AS Java is used to provide the Java foundation of SAP NetWeaver PI using the Java Engine a Java EE-
compliant application server for running enterprise applications In addition to the pure Java EE
standard technologies the Java Engine implements complementary technologies such as Web Dynpro
or Web Services that are targeted at supporting large-scale real-business application development
projects
Dependencies
AS Java can be combined optionally with other usage types in one system
Process Integration (PI)
Purpose
PI consists of core components that model design automate and integrate processes in one or more
application systems For the integration of internal and cross-company processes PI is used to
incorporate all the functions of what was formerly known as Exchange Infrastructure (XI) In addition
PI contains core components for Business Process Management for application-embedded and
application-unbounded processes
The Advanced Adapter Engine is also part of usage type PI You use Advanced Adapter Engine to connect
to SAP systems (RFC adapter) and external systems You use the various adapters in Advanced Adapter
Engine to convert XML- and HTTP-based messages to the specific protocol and format required by
these systems and the other way around You can use the Advanced Adapter Engine that is part of
your PI system as a central Advanced Adapter Engine Optionally (for performance reasons) you can
install a non-central Advanced Adapter Engine [page 19] separately as a system with AS Java and parts of the
usage type PI on a separate host
Dependencies
PI requires AS ABAP and AS Java as prerequisites in the same system
For installing PI it is mandatory to have a dedicated PI system This applies to development quality
and production landscapes It is a prerequisite that no other system in your system landscape has a
higher release and enhancement package level than the PI system If you want to upgrade or install an
application in your system landscape you first have to make sure that the current release and
enhancement package level of the PI system is on the same level - if required you have to upgrade the
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1756
PI system first to the new or a higher release In a dedicated PI system this can be accomplished with a
minimum of downtime Also the PI system would not be affected by the downtime of other usage
types running in the same system
Configuration of Systems with Usage Types
Configuration information is available in the installation guides the configuration wizard and SAP
Solution Manager
In the Installation Guide ndash SAP NetWeaver PI 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt you find
initial technical configuration tasks This guide also informs you about how you can run the
configuration wizard and how you can access the configuration information in SAP Solution
Manager
For certain usage types configuration tasks can be applied by the configuration wizard after the
installation To do this you start the configuration wizard from SAP NetWeaver Administrator
The configuration steps for systems with usage types required for an use case are accessible through
SAP Solution Manager
To be able to use SAP Solution Manager for the configuration tasks you have to import the latest
SAP Solution Manager Implementation Content (Add-On ST-ICO) that is available for your SAP
Solution Manager release For more information see SAP Note 631042 (Release strategy for Implementation
Content (ST-ICO))
SAP Solution Manager Implementation Content is available on SAP Service Marketplace at
httpservicesapcomswdc Installations amp Upgrades Entry by Application Component SAP
Technology Components SAP Solution Manager ltReleasegt Content ST-ICO
In SAP Solution Manager you create a project and a project structure In the configuration phase
you select configuration structures with pre-delivered SAP content for your project You can find
the following different types of configuration tasks in SAP Solution Manager
Mandatory configuration tasks All configuration tasks that are mandatory for the standalone
engine or usage type
Optional configuration tasks Configuration tasks for areas where customers need to decide
if they want to use these functions (for example high availability or security settings)
Additional functions ndash configuration tasks Configuration tasks for functional units that are
used in certain use cases only
A marked checkbox in front of the configuration tasks indicates those configuration tasks that are
relevant for the use case you have chosen To configure ABAP systems SAP Solution Manager
offers executable configuration files (IMG activities)
For information about using SAP Solution Manager Content and creating a configuration guide
see the following documentation
httphelpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Implementing
and Upgrading SAP Solutions Configuration
3 SAP NetWeaver PI Overview
31 Installable Software Units
1856 PUBLIC 2011-04-15
How to Create a Configuration Guide using SAP Solution Manager available at http
servicesapcomsolutionmanager Media Library How-To Documents
Restrictions for Systems with Multiple Usage Types
If you have one system with multiple usage types be aware that we do not provide standard tools
to separate these usage types and distribute them to multiple systems at a later stage For example
if you have a system with usage types A and B you are not able to migrate it with SAP standard
tools into two systems one with usage type A only and the other with usage type B only
In addition we do not provide standard tools to merge multiple systems with different usage types
into one system with multiple usage types at a later stage
If you want to perform these tasks you require specific project support
The following figure shows that SAP standard system copy and migration tools do not support
you in separating or merging systems with usage types
Figure 4 No Support for Merging or Separating Systems with Usage Types
Although you can use one system for multiple usage types client restrictions apply for usage type
PI PI requires a dedicated client due to special PI requirements concerning the client pipeline
Whereas application client pipelines only send and receive messages the central PI pipeline can
also map messages to different formats before sending them
312 Standalone Engines
Standalone engines of SAP NetWeaver are additional installable software units They do not work as
full-blown systems of SAP NetWeaver but as standalone engines that provide a specific (server) function
in combination with one or more SAP NetWeaver systems
Standalone engines are not part of a usage type They do not run on AS ABAP or AS Java
The standalone engines that are available for SAP NetWeaver Process Integration are described in the
following
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1956
Gateway
It is possible to install an SAP instance of an SAP NetWeaver system based exclusively on a standalone
gateway This type of instance does not contain normal work process types (dialog background update
enqueue or spool) Only the gateway process (gwrd) is started If there is an SNA connection to an R
2 system gateway work processes (gwwp) are also started
SAP Conversion Agent by Informatica
SAP Conversion Agent by Informatica is a data conversion tool that enables you to create interfaces
between any data formats and XML-based systems SAP Conversion Agent can convert unstructured
semi-structured and structured formats to XML and the other way around The Conversion Agent
comprises the Conversion Agent Studio and the Conversion Agent Engine In the Conversion Agent
Studio you can develop and configure data conversions The Conversion Agent Engine executes the
data conversions
Search and Classification (TREX)
You can use Search and Classification with SAP NetWeaver PI to search for messages that were previously
indexed Message search using index provides additional methods of searching for specific messages In
addition to static header attributes you can also use adapter-specific message attributes and data from
the message payload for the search A requirement of this however is that the messages are indexed
first You can apply the index-based message search to one or all indexed components of an integration
landscape (domain) Integration Server Adapter Engines and ABAP business systems
For more information see the SAP Library [page 12] at Administratorrsquos Guide Technical Operations for SAP
NetWeaver Administration of SAP NetWeaver Systems Administering PI (Process Integration) Monitoring Index
Administration
Web Dispatcher
The Web Dispatcher lies between the Internet and your SAP system It is the entry point for HTTP(s)
requests into your system which consists of one or more SAP NetWeaver application servers As a
software web switch the Web dispatcher can reject connections or accept them When it accepts a
connection it balances the load to ensure an even distribution across the servers
You can use the Web dispatcher in ABAPJava systems and in pure Java systems as well as in pure ABAP
systems
It is also beneficial to use the Web Dispatcher if you do not need security functions (entry point in the
demilitarized zone (DMZ) SSL URL filtering) but you simply want to balance the load between
multiple SAP NetWeaver Application Server instances
Since Web Dispatcher is optional for every SAP system it is not contained in the system landscape and
the implementation sequence of the use case in this documentation
For more information see the SAP Library [page 12] at Function Oriented View Application Server Infrastructure
SAP Web Dispatcher
3 SAP NetWeaver PI Overview
31 Installable Software Units
2056 PUBLIC 2011-04-15
Advanced Adapter Engine
You use the Advanced Adapter Engine to connect to SAP systems (RFC adapter) and external systems
You use the various adapters in Advanced Adapter Engine to convert XML- and HTTP-based messages
to the specific protocol and format required by these systems and the other way around For specific
senderreceiver combinations messages can be processed without invoking the central Integration
Engine In principle you connect external systems using the adapters that are installed centrally or
non-centrally in Advanced Adapter Engine You can use the Advanced Adapter Engine that is part of
your PI system as a central Advanced Adapter Engine Optionally (for performance reasons) you can
install a non-central Advanced Adapter Engine separately as a system with AS Java and parts of the
usage type PI on a separate host
Adapter Engine (Java SE)
Adapter Engine (Java SE) is a separate software unit You can use it only if you have SAP NetWeaver
systems with usage type PI in your system landscape It has to be installed manually You use the Adapter
Engine (Java SE) to connect to external systems Using the various adapters in the Adapter Engine (Java
SE) XML and HTTP-based messages can be converted to the specific protocol and format required by
such systems and the other way around The Adapter Engine (Java SE) only provides some of these
adapters as a standalone version with restricted functions for operating systems that do not support
SAP NetWeaver PI 71 but that have at least a Java Runtime Environment 50 Therefore you should
use the Adapter Engine (Java SE) only if the platform prerequisites do not allow you to use the Advanced
Adapter Engine
SAP Partner Connectivity Kit
SAP Partner Connectivity Kit (PCK) runs on AS Java with parts of the usage type PI It enables a system
of a smaller company or subsidiary that does not run SAP NetWeaver PI to connect to your SAP
NetWeaver systems
313 Clients
Clients are additional installable programs or tools They reside either on local front-end PCs accessed
by users or on back-end systems where they act as client programs within an SAP NetWeaver system
landscape
The clients that you can use with SAP NetWeaver Process Integration are described in the following
sections
SAP GUI
NOTE
We recommend that you use the following versionsI
SAP GUI for Windows 710 (or higher) with the latest patch level
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 2156
SAP GUI for Java 710 (or higher) with the latest revision
The integrated SAP ITS 710
For more information about the SAP GUI family see SAP Service Marketplace at http
servicesapcomsapgui
SAP offers three different client applications for accessing ABAP applications in SAP systems (such as
SAP NetWeaver systems with usage type AS ABAP) This SAP GUI family consists of
SAP GUI for HTML
SAP GUI for HTML is based on the SAP integrated Internet Transaction Server (ITS) which is
included in the installation of SAP NetWeaver systems as of SAP NetWeaver 2004 On the client
side only a suitable browser (such as Internet Explorer 70 or Firefox 20) and a virtual machine are
required SAP ITS 620 is not compatible with SAP NetWeaver 71
SAP GUI for the Java environment (SAP GUI for Java)
SAP GUI for Java is a generic SAP GUI that covers a variety of platforms
For more information about the installation of SAP GUI for Java see the documentation Installation
Guide ndash SAP Front End
SAP GUI for the Windows environment (SAP GUI for Windows)
SAP GUI for Windows is SAPs universal client for accessing all SAP applications built on ABAP
technology It is available on the Microsoft Windows platform only and offers the broadest feature
set of all members of the SAP GUI family
For more information about the installation of SAP GUI for Windows see the Installation Guide ndash
SAP Front End
SAP NetWeaver Developer Studio
The SAP NetWeaver Developer Studio is SAPrsquos Integrated Development Environment (IDE) for Java
and is based on the open-source tools framework Eclipse 33 With the SAP NetWeaver Developer Studio
you can develop Java EE 5 applications from scratch using the built-in support for new technologies
such as EJB 30 and JSF 12
During the installation of the SAP NetWeaver Developer Studio several features are offered for
installation For SAP NetWeaver PI 71 only the following features are relevant
SAP NetWeaver Developer Studio Platform
SAP NetWeaver Developer Studio Java EE
NOTE
If you want to use one of the other features you need SAP NetWeaver Composition Environment
and a corresponding developers licence
For more information about the installation of SAP NetWeaver Developer Studio see the Installation
Guide ndash SAP NetWeaver Developer Studio 71 or Installation Guide ndash SAP NetWeaver Developer Studio 71 Including
Enhancement Package 1
3 SAP NetWeaver PI Overview
31 Installable Software Units
2256 PUBLIC 2011-04-15
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
SAP enhancement packages are a new way of delivering new functions for SAP NetWeaver This allows
a clear separation between the delivery of new functions on the one hand and corrections legal changes
and security updates on the other hand (in Support Package stacks) SAP enhancement packages are
cumulative an enhancement package always contains the functions of the corresponding predecessor
enhancement packages
Enhancement packages are maintained by their own Support Packages while the main release is in
maintenance
Benefits
SAP enhancement packages offer the following benefits
You have reduced effort for testing and no effort for training when applying Support Packages as
new features are only shipped with enhancement packages
Adding new functions between releases becomes predictable and controllable
New functions can be added successively in small steps There is no need to fully upgrade your
system to get new functions
You have minimal training effort when applying an enhancement package because existing
functions are not replaced
Implementation
There are the following ways to get an SAP NetWeaver system with the release level of SAP enhancement
package 1 for SAP NetWeaver Process Integration 71
New installation of SAP NetWeaver PI 71 including enhancement package 1 using the standard
installation tool SAPinst
Upgrade of an existing SAP NetWeaver system from a release lower than SAP NetWeaver PI 71 to
SAP NetWeaver PI 71 including enhancement package 1 For this you use the upgrade programs
SAPup (for ABAP) and SAPJup (for Java)
Installation of the enhancement package on an existing SAP NetWeaver PI 71 system
For this you use the Software Update Manager (SUM) The Software Update Manager evolved
from the previously used SAP Enhancement Package Installer The tool has been renamed to reflect
its broader use for example you can also use it for applying Support Package Stacks to your system
On the ABAP side the Software Update Manager uses a system cloning and switch procedure for
installing enhancement packages It installs a copy of the system the shadow system parallel to
the original system This shadow system is used to update the relevant software components and
to install the additional components while the original system is still in production operation At
a certain point during downtime the switch to the new system is made and afterwards any parts
of the original system that are no longer needed are deleted The enhancement package installation
in a Java system uses a deploy-based procedure that is no shadow system is used The Software
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2011-04-15 PUBLIC 2356
Update Manager requires a stack configuration file (xml file) as input file for the enhancement
package installation procedure This file lists all the packages that are to be installed in your systems
The stack configuration file is generated when you download the required packages
As the Software Update Manager is updated regularly we recommend to always use the latest
version It is delivered as part of the SL toolset For more information see http
servicesapcomsltoolset
For an overview of all required steps for the enhancement package installation process and
corresponding documents see Process Overview Installation of Enhancement Package 1 on an Existing SAP
Netweaver PI 71 System [page 28]
Content of SAP Enhancement Package 1 for SAP NetWeaver PI 71
With enhancement package 1 for SAP NetWeaver PI 71 new features are introduced and some existing
are changed The following is a selection of some of the most important enhancements
Enhanced design and modelling options in the Enterprise Services Repository
New services registry
Support for new Web services standard (Web Services Reliable Messaging)
New modules for the Advanced Adapter Engine
Use of shared memory of the ABAP Application Server for message processing
For more information about the changes see SAP Library [page 12] at Whatacutes new in SAP NetWeaver PI 71
ndash Release Notes
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2456 PUBLIC 2011-04-15
4 SOA-Based Integration Use Case
41 Overview
You can use SOA-based integration to set up the communication between service providers and service
consumers in both application-to-application and business-to-business scenarios and to execute
operate and monitor the communication at runtime SOA-based integration covers both direct (point-
to-point) as well as mediated (via an Integration Server) communication between service providers and
service consumers
The use case spans the whole life cycle of a SOA-based integration scenario including
Scenario modeling and service design in the Enterprise Services Repository
Implementation of the service provider and consumer in the back-end systems
Configuration and finally execution monitoring and operation of the integration scenario
For scenarios using Integration Server or broker-based communication the configuration of the
different connectivity options (for example SOAP RFC Web Services Industry standards and JDBC)
and their enhancements is covered
For more information see the following documents
Service-Enabling with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdnsoa-modeling
Getting Started
Service-Enabling a Legacy Application with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdn
soa-servicebus Getting Started
In the following you will find information about the installation of the involved software units
42 System Landscape
The following figure shows the system landscape for this use case
4 SOA-Based Integration Use Case
41 Overview
2011-04-15 PUBLIC 2556
Figure 5 SOA-Based Integration
It is mandatory to have a dedicated PI system This applies to development quality and production
landscapes
For PI it is a prerequisite that no other system in your system landscape has a higher release than
the PI system For exceptions to this rule see SAP Note 1043047 For example SAP XI 30 is compatible
with SAP NetWeaver 640 and 70 application systems since the same XI protocol is used Apart
from these exceptions if you want to upgrade or install an application in your system landscape
you first have to make sure that the PI system is on the same release level If required you have to
upgrade the PI system first to the new or a higher release
CAUTION
Although it should be technically possible to run an application system with a higher release
than your PI system in your system landscape this is not supported by SAP (apart from the
exceptions listed in SAP Note 1043047) Therefore you run such a landscape at your own risk
You can use the Advanced Adapter Engine that is part of your PI system as a central Advanced
Adapter Engine
Adapter Engine (Java SE) can be installed in a non-SAP Java environment However it only hosts
a subset of the adapter functionality is only supported for compatibility reasons and should be
used only if this is a precondition in your environment
Optionally you can use the Change Management Service (CMS) of an SAP NetWeaver 70 system
with usage type DI to transport design objects and repository objects For more information see
the SAP Library [page 12] at Administratoracutes Guide Technical Operations for SAP NetWeaver Administration
of SAP NetWeaver Systems PI (Process Integration) Software Logistics Transporting ESR Content and Objects
of Integration Directory PI Transports Using the Change Management Service (CMS)
Smaller business partners or subsidiaries that do not run SAP NetWeaver install SAP Partner
Connectivity Kit in their system landscape SAP Partner Connectivity Kit enables XML document
4 SOA-Based Integration Use Case
42 System Landscape
2656 PUBLIC 2011-04-15
exchange between your SAP NetWeaver systems and the partner systems Since SAP Partner
Connectivity Kit gets installed in their system landscape it is not shown in the system landscape
figure above
The AS ABAP system acts as an application and service provider For Java Web Services you also
require AS Java In addition you require SAP NetWeaver Developer Studio on the client side as a
development environment
The Web service client can be either an SAP or a non-SAP application For example an AS ABAP
system or a Web browser could act as application or service consumer
You can install SAP Conversion Agent by Informatica in the system with usage type PI or on a host
where SAP Partner Connectivity Kit is installed or on a host where neither usage type PI nor SAP
Partner Connectivity Kit is installed
43 Implementation Sequence
Procedure
To install this use case perform the steps listed in the following table
StepAction[Corresponding Documentation] Remarks
1 Make sure that you have performed the preparation steps You have planned your system landscape [page 33]
(that is you have decided how many systems you require how you want to use each of these systems and which standalone engines and clients you require)
With the help of your hardware partner you have mapped your systems and standalone engines to properly sized hosts
You have planned and installed shared services [page 35]
2 Installation of system with usage type PI (includes the installation of AS ABAP and AS Java)
NOTE
For usage type PI a Unicode installation is mandatory
[Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt]
If you want to use the features of enhancement package 1 use the direct installation of SAP NetWeaver PI 71 including enhancement package 1
Make sure that you perform the configuration steps as described in the installation guide For certain usage types configuration tasks can be applied by the configuration wizard These configuration tasks as well as any additional configuration steps for your use case are listed in SAP Solution Manager For more information
4 SOA-Based Integration Use Case
43 Implementation Sequence
2011-04-15 PUBLIC 2756
StepAction[Corresponding Documentation] Remarks
see the Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt
3 Install the Adapter Engine (Java SE) engines if required[Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
4 To integrate small business partners and subsidiaries the business partners or subsidiaries install SAP Partner Connectivity Kit running on AS Java with parts of usage type PI in the business partners or subsidiarys system landscape[Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
5 Install SAP Conversion Agent by Informatica if required[SAP Library [page 12] at Function-Oriented View Process Integration SAP Conversion Agent by Informatica Deploying and Using Conversion Agent ]
6 Installation of clients SAP GUI
[Installation Guide ndash SAP Front End]
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
The process sequences give a comprehensive overview of the steps relevant for the enhancement
package installation on an existing SAP NetWeaver PI 71 system
The process sequence is divided into a planning phase and an implementation phase Each step in both
phases contains references to the corresponding documentation to ensure that you can easily find the
information you need
Process
NOTE
To download the enhancement package files and required Support Packages you require the SAP
Solution Manager Maintenance Optimizer You have the following options
Manual Selection
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2856 PUBLIC 2011-04-15
You manually select the required files from SAP Service Marketplace at http
servicesapcomswdc using the SP Stack Application You use the Maintenance Optimize
only to approve the packages which is a prerequisite for the download
Automatic Calculation
The Maintenance Optimizer supports the download of a consistent queue that includes all
necessary Support Packages and enhancement packages In addition SAP Solution Manager
calculates a valid import queue for the selected SAP system and generates the enhancement
package stack configuration file that you require for the installation
As a prerequisite the system that you want to update needs to be maintained correctly in
SAP Solution Manager System Landscape As the Maintenance Optimizer uses this data for
the calculation it is crucial that the data is up-to-date In addition the SAP Solution Manager
system requires a Minimum Support Package level (see below)
Planing PhaseStep Description Documentation
Hardware amp Software Prerequisites
Check which platforms are supported for your target release (OSDB dependencies)
Product Availability Matrix (PAM) at httpservicesapcompam
Check which hardware sizing is required for your target release
Sizing information at httpservicesapcomsizing
Solution Manager Prerequisites
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of the required software packages you have to make sure that your SAP Solution Manager system has the required Support Package levelAt least SAP Solution Manager 70 EHP1 Support Package Stack 17 is required We recommend to use SAP Solution Manager 70 EHP1 Support Package Stack 23Check if you need to do an update or upgrade of your SAP Solution ManagerMake sure that you run the guided procedure SOLMAN_SETUP after every installation or update of SAP Solution Manager and that it completes successfully
For upgrades from source release SAP Solution Manager 31 and 32Upgrade Guide ndash SAP Solution Manager 70 incl Enhancement Package 1For updates from SAP Solution Manager 70Update Guide SAP Enhancement Package 1 for SAP Solution Manager 70Follow-up activities after an Support Package Stack update or enhancement package updateSolution Operations Guide ndash SAP Solution Manager 70 EHP1 section Software Change Management All guides are available at http
servicesapcom instguides SAP Components SAP Solution Manager -gt Release 70 EHP 1
Implementation PhaseStep Description Documentation
1Solution Manager Preparation
Configure the SAP Solution Manager Maintenance Optimizer
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of software packages make sure your
Configuration of Maintenance Optimizer http
helpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Change Request Management and Change ControlMaintenance Optimizer
Prerequisites
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 2956
Implementation PhaseStep Description Documentation
system landscape data in SAP Solution Manager is maintained correctlyLandscape Verification 10 which is an add-on to SAP Solution Manager can support you in maintaining your system landscape data The use of this tool is optional
Landscape Verification http
wwwsdnsapcom irj
sdn alm-update-
management link Landscape Verification under Related Areas on Upgrade and Update Management (in the right column)
SAP Note 1468605 (Installation of Landscape Verification)
Maintaining System Landscape Information [page 47]Note that the information provided in this section is based on SAP Solution Manager 70 EHP1 SP23
2System Preparation
Prepare your system as described in the documentation for example perform OS DB specific preparations and the PI-specific preparations
Update Guide ndash Update of SAP Systems with Software Update Manager sections Planning and Preparation
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
3Software Download
Select and download the software packages in either of the following ways Automatic calculation Create
a maintenance transaction in the Maintenance Optimizer and choose the Calculate Files Automatically option
Manual Selection Create a maintenance transaction in the Maintenance Optimizer and choose the Select Files Manually option You then can select the files manually using the SP Stack application in SAP Service Marketplace
NOTE
You have to download the stack configuration file manually after you have selected all files in the SP Stack
httphelpsapcom SAP Solutions SAP Solution Manager
SAP Solution Manager 70 EHP1 ltSPgtChange Request Management and
Change Control Maintenance Optimizer Maintenance Procedure Scenarios
For information about the automatic calculation see Maintenance Transaction with Installation of an Enhancement PackageFor information about the manual selection and approval process see section Approve and Download Files in Download Basket
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
3056 PUBLIC 2011-04-15
Implementation PhaseStep Description Documentation
application Choose Generate Stack XML and save the file
4Enhancement Package Installation
Run Software Update Manager to update your system with the selected software packages
Update Guide ndash Update of SAP Systems with Software Update Manager
5Follow-Up Steps
Perform technical and PI-specific follow-up activities after the enhancement package installation is done
Update Guide ndash Update of SAP Systems with Software Update Manager section Follow-Up Activities
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
6Configuration
Configure newly installed enhancement package functions using SAP Solution Manager content
See Systems with Usage Types [page 16] section Configuration of Systems with Usage Types
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 3156
This page is left blank for documents that are printed on both sides
5 System Landscape
51 Planning Your System Landscape
The installable software units that make up your system landscape depend on the functions that you
want to implement For information about the features see systems [page 16] standalone engines [page 19]
and clients [page 21]
In addition you have to determine the required shared services [page 35] (such as SAP Solution Manager
or SAP NetWeaver Administrator) that run on central systems in your system landscape and the
landscape aspects relevant for their implementation
In the following you will find general information that you should consider when planning your system
landscape
Sizing
You have to map systems and standalone engines to hosts after you have a clear picture of the following
Which systems and standalone engines you require
How many systems you require and how you want to use each of these systems
NOTE
No general guideline can be given for the sizing of your landscape since this relies heavily on your
requirements You should therefore perform this task together with your hardware partner and
your technical consultant
For information about sizing your systems you can use the following information sources
Your first point of reference is the Quick Sizer
SAP built the Quick Sizer as an online sizing questionnaire Internet application in close cooperation
with its hardware partners This tool delivers general sizing categories based on your volume load
estimates The results provide an objective basis for sizing independent of platform and
configuration
For more information see SAP Service Marketplace at
httpservicesapcomsizing for the SAP NetWeaver PI 71 sizing guide available under
Sizing Guidelines Business Suite amp Services
httpservicesapcomquicksizer for more information and access to the tool itself
Also consider the following important aspects concerning sizing
High availability
5 System Landscape
51 Planning Your System Landscape
2011-04-15 PUBLIC 3356
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Technical Infrastructure High Availability
Unicode
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Internationalization
Contact your hardware partner to find out the appropriate number of sized hosts
The platform-independent abstract results of the Quick Sizer can be used by any of our hardware
partners to create a concrete offer SAP itself does not make any hardware recommendations the
responsibility for sizing and detailed hardware configuration lies with the hardware partners
Figure 6 Example of Mapping of Systems and Standalone Engines to Three Hosts
NOTE
Optionally you could also distribute single systems to multiple hosts For example you could
decide to install the database instance of an SAP system on a separate host for performance
reasons or distribute other system instances to achieve high availability
To provide a mapping that fits your required functions and performance your hardware partner
and your technical consultant have to identify the number of required instances of SAP NetWeaver
find out how to distribute these instances to hosts and what functions will run on which instance
Therefore the hardware partner and the technical consultant have to consider many different
aspects such as
Number of required SAPS (SAP Application Benchmark Performance Standard) for each
system (provided by Quick Sizer)
Landscape-relevant aspects concerning security For more information see the SAP Security
Guide in the SAP Library [page 12] at Administratoracutes Guide Security Guide
Landscape-relevant aspects concerning scalability high availability operation and software
life-cycle management
5 System Landscape
51 Planning Your System Landscape
3456 PUBLIC 2011-04-15
For more information about relevant aspects for the mapping of systems to hosts see the document
Technical Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
Scaling and Distribution Options
You may need to design your system landscape for a large number of users SAP NetWeaver PI offers
you different means of scalability The following list provides you with some examples
You could install multiple systems of one type and use them for different purposes
You could scale every system by installing dialog instances or by distributing the database instance
For more information about distribution options on the instance level see the Technical
Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
For every SAP system you could additionally install Web Dispatcher For more information see
the SAP Library [page 12] at FunctionndashOriented View Application Server Infrastructure SAP Web
Dispatcher
You could further distribute certain standalone engines ndash for example Search and Classification
(TREX) is based on a flexible architecture that supports a distributed installation For more
information see the Technical Infrastructure Guide ndash SAP NetWeaver PI 71 available in SAP Service
Marketplace at httpservicesapcominstallNWPI71
52 Shared Services
You normally run shared services on central systems in your system landscape The following features
could be used for SAP NetWeaver Process Integration to realize shared services
SAP Solution Manager
Used to implement train test maintain monitor control change and manage incidents of your
SAP solution system landscape (open end-to-end application management)
As of SAP Solution Manager (70) 40 Support Package 15 SAP Solution Manager has become the
platform for SAPs end-to-end solution operations strategy Functions for complete application
management has been combined with administrative tools and has been merged in newly created
role based work centers
NOTE
Be aware that you require an SAP Solution Manager system to install or upgrade to SAP
NetWeaver 70 and higher An SAP Solution Manager system is required to generate the SAP
Solution Manager key needed during the installation or upgrade process Without this key
the installation or upgrade process cannot continue
For SAP NetWeaver Process Integration you require SAP Solution Manager 70
For more information see SAP Note 805390
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3556
Solution Manager Diagnostics
An integral part of SAP Solution Manager that is running as a Java application on the Java stack of
SAP Solution Manager 70 Solution Manager Diagnostics is used to analyze the root cause of
incidents in your landscape in an efficient and safe way Before Go-Live Solution Manager
Diagnostics has to be set up and made accessible remotely
SAP NetWeaver Administrator
SAP NetWeaver Administrator is the central administration component which is used for
monitoring and administering Java applications It is included in SAP NetWeaver systems with AS
Java
SAP NetWeaver Administrator exists in the following flavors
A local mode which runs out of the box and which focuses on administrating the underlying
SAP NetWeaver AS Java
NOTE
For a SAP NetWeaver PI 71 it has a special role which you need to activate using a
configuation wizard
A central mode which has to be configured before use and which deals with the system
landscape management
SAP has decided to merge the central mode of SAP NetWeaver Administrator into the new work
centers available as of SAP Solution Manager 70 SP 15 Thus it can be used in an administrative
context together with non-Java-based administration tools Although the central mode of SAP
NetWeaver Administrator will be still available for some time SAP will not develop this tool any
further SAP focuses on optimizing the administrative work centers of SAP Solution Manager
instead
The local mode of SAP NetWeaver Administrator stays untouched It is available for current and
future releases of SAP NetWeaver
SAP Central Process Scheduling by Redwood
SAP Central Process Scheduling application by Redwood enables central job scheduling and job
monitoring of current and old releases of AS ABAP systems (as of Basis Release 31) This application
is fully integrated in SAP NetWeaver Depending on the business needs SAP business applications
are the initial trigger for scheduled activities You can now manage jobs and job chains conveniently
using a graphical user interface
System Landscape Directory
The System Landscape Directory is the central directory of system landscape information relevant
for the management of your software life-cycle It contains a description of your system landscape
(that is software components that are currently installed) and a repository of software components
that can theoretically be installed in your landscape (such as the software components available
from SAP)
Adaptive Computing Controller
5 System Landscape
52 Shared Services
3656 PUBLIC 2011-04-15
The Adaptive Computing Controller enables users to control an adaptive computing landscape
from a single point through observation operation and dynamic resource distribution With
adaptive computing hardware software and system services are able to adapt to changing business
needs In the Adaptive Computing Controller the run-time data of logical and physical landscapes
can be monitored application services can be startedstoppedrelocated and hardware resources
can be assigned to application services The operation can also be mass executed and be planned as
tasks to be executed
For more information about the installation of the Adaptive Computing Controller tool see the
document Installation Guide ndash Adaptive Computing Controller in SAP NetWeaver 71 available on SAP Service
Marketplace at httpservicesapcominstallNWPI71
For more information about Adaptive Computing in general see httpsdnsapcomirj
sdnadaptive
521 Use Cases
You can use the applications and tools described above for use cases that are normally performed
centrally The following sections describe these use cases
5211 End-to-End Solution Operations
Running business applications through their complete life-cycle is a challenge Therefore SAP has
started the Run SAP methodology for implementing End-to-End Solution Operations Based on a set
of SAP standards a roadmap and a package for training and certification Run SAP helps customers to
facilitate End-to-End Solution Operations
You can download the SAP standards for Solution Operations from SAP Service Marketplace at http
servicesapcomsupportstandards They describe roles customers typically have in their IT
environment For optimal role support SAP has grouped existing and new functions in SAP Solution
Manager work centers as of SAP Solution Manager 70 Support Package 15 Operations aspects are fully
covered by adding administrative functions for SAP NetWeaver as well Work centers are ABAP Web
Dynpro-based applications They offer the following advantages
Easy to use similar look and feel
Context transfer while jumping from one work center into another
Logical grouping of tools for a certain area
Simple authorization concept
Easy to expand
Each IT role belongs to one or more work centers For instance the Technical Administrator IT role is
covered by the work centers for System Monitoring System Administration and Landscape Management
The following work centers are available
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3756
Business Process Operations
Change Management
Root Cause Analysis
Implementation Upgrade
Incident Management
Test Management
Job Management
System Landscape Management
Solution Documentation Assistant
SAP Engagement and Service Delivery
SAP Solution Manager Administration
System Administration
System Monitoring
My Home is the central point of access to all important data of almost all work centers in SAP Solution
Manager
5212 Support Infrastructure
A key requirement for effective support of IT solutions is the ability to perform root cause analysis with
speed and efficiency
With SAP Solution Manager SAP has long had an infrastructure in place for its ABAP applications that
efficiently supports SAP solutions This helps ensure the high availability and smooth running of
business processes For more information see the SAP Solution Manager section
With Solution Manager Diagnostics this knowledge has been extended to Java applications If for
example homegrown Java applications cause instability Solution Manager Diagnostics helps trace the
cause to eradicate the problem rapidly Solution Manager Diagnostics is fully integrated into SAP
Solution Manager 70 Solution Manager Diagnostics also contains two third-party tools CArsquos Wily
Introscopereg for measuring performance as well as troubleshooting problems of the Java EE Engine
and applications running on it and Mercury Loadrunnerreg which enables SAP Support to produce a
defined load in the SAP solution landscape remotely For more information see Solution Manager
Diagnostics [page 43]
The support infrastructure provides SAP Support with safe access to your productive landscape for safe
root cause analysis so ensuring that SAP Support does not change your landscape inadvertently You
require a support infrastructure to run SAP NetWeaver
The following figure shows the overall infrastructure including SAP NetWeaver administration tools
that are used by administrators or operators at the customer site
5 System Landscape
52 Shared Services
3856 PUBLIC 2011-04-15
Landscape Aspects
If you use SAP NetWeaver Process Integration 71 productively besides SAP Solution Manager (as a
central support platform) you have to set up Solution Manager Diagnostics for supportability reasons
Implementation Sequence
For information about the implementation of the support infrastructure see the document Master
Guide ndash SAP Solution Manager 70 available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution Manager ltReleasegt
5213 Collection of Landscape Data
Amongst other applications and services the support infrastructure and the SAP NetWeaver
administration tools rely on system landscape data
For SAP NetWeaver PI 71 you have to run non-ABAP components in your solution landscape
Therefore the System Landscape Directory is mandatory The landscape data that is automatically
gathered by the System Landscape Directory is replicated to SAP Solution Manager There are several
topology options for the System Landscape Directory They offer different grades of availability
administration and operation effort
For more information see the System Landscape Directory section
5214 Authentication and Single Sign-On
Before implementing your system landscape plan how to implement authentication and how to
integrate different systems into a Single Sign-On landscape Single Sign-On reduces complexity for end
users saving them valuable time while also reducing administration effort for resetting passwords
thereby contributing to TCO reduction
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
5215 Integrated User and Access Management
In a system landscape containing a combination of ABAP and Java components we recommend that
you integrate your user and access management so that you can use the same user data across different
systems administer this data centrally and control access to data SAPs mature fine-grained
authorization concept allows detailed control of access rights SAP NetWeaver provides both ABAP and
Java-based user management solutions The user management solution that you use to administer
your user data depends on factors such as the type of systems that are running in your landscape
If you want to use central user administration we recommend that you run it in a non-production
system If you do not have a central user administration yet you can for example realize it in the SAP
Solution Manager system
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3956
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
522 Examples for the Overall System Landscape of Shared Services
In this section we provide examples of how shared services can be set up depending on the system
landscape they are intended for The following examples aggregate the landscape aspects given in the
Use Cases section
NOTE
The following sections and the figure mostly do not show information about the life-cycle of
shared services For example you may also need a development and testquality assurance system
for SAP Solution Manager You should consider this aspect in addition to the information given
in this section based on your requirements
Small and MediumndashSized Customer Landscapes with Java
As you use Java productively for SAP NetWeaver PI 71 besides SAP Solution Manager you have to set
up additional components for optimal monitoring administration and support Solution Manager
Diagnostics and the central mode of SAP NetWeaver Administrator are already fully integrated into
SAP Solution Manager 70 as the central operations hub For SAP Process Integration you must also
set up SAP NetWeaver Administrator with a special role
We recommend that you do not install SAP Central Process Scheduling in the SAP Solution Manager
system You have to set up and operate the system which hosts your productive scheduler as a mission
critical system
In the SAP Solution Manager system you should set up a local System Landscape Directory in addition
to a central runtime System Landscape Directory This way you have a clear separation between your
management system (SAP Solution Manager) and managed systems in your landscape In addition
SAP Solution Manager then does not rely on a System Landscape Directory running in the production
environment For this setup configure the SLD data suppliers of your SAP Solution Manager system
to send data to the central runtime System Landscape Directory In addition configure automatic
bridge forwarding from your runtime System Landscape Directory to the local System Landscape
Directory For more information see the Planning Guide - System Landscape Directory
If you want to use a central system for Adobe Document Services we recommend that you install a
dedicated system for this purpose in your production environment For detailed information about
the sizing of the system for the different use cases see the Sizing Guide for Adobe Document Services at
SAP Service Marketplace at httpservicesapcomsizing Sizing Guidelines Solutions amp
Platform
We recommend that you start with this centralized SAP Solution Manager approach as depicted in the
following figure
5 System Landscape
52 Shared Services
4056 PUBLIC 2011-04-15
Figure 7 Single SAP Solution Manager Landscape
Large Customer Landscapes with Java
Large customers who have environments in their landscape that are large and distributed administered
by different groups or separated for security reasons can consider a distributed operations setup In
addition to the centralized setup described for small- and medium-sized customers above large
customers can put parts of the central management functions on extra hosts or systems for performance
or policy reasons You have the following options for a distributed setup
You may set up an extra system or client for Central User Administration (CUA)
The Change and Transport System (CTS) can run on an extra system However it is not
performance- or data-intensive
You may set up an extra system for central CCMS monitoring Depending on the customizing
and on the landscape size central CCMS may generate a lot of system load You can connect a
separate central CCMS to SAP Solution Manager for displaying alerts in the alert inbox of the System
Monitoring work center
You can use a separate SAP NetWeaver 70 system with usage type BI together with SAP Solution
Manager This may make sense with respect to the amount of landscape management data that is
stored for reporting purposes The amount of data strongly depends on the data granularity
storage time frame and landscape size
You can easily put Wily Introscope Enterprise Manager on an separate host
Other aspects described above for small- and medium-customers (such as the setup of the System
Landscape Directory) are also valid for large customers
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4156
523 Feature Details
This section provides further information about the features described above
5231 SAP Solution Manager
SAP provides you with SAP Solution Manager as the strategic application management platform and
to enable the collaboration between you and SAP You need to install at least one productive SAP
Solution Manager in your system landscape To ensure the availability of this application management
platform an SAP Solution Manager system is technically required to install or upgrade to SAP
NetWeaver 70 or higher If you are already using SAP Solution Manager you can also use it to manage
the solution you build with SAP NetWeaver In this case we highly recommend that you update SAP
Solution Manager to the latest version
As of SAP Solution Manager 70 SP15 you can use the newly created work centers
NOTE
During the SAP system installation or upgrade process you are prompted to enter the SAP
Solution Manager key An SAP Solution Manager system is required to generate this key Without
this key the installation or upgrade process cannot continue
You may generate all needed keys for your entire system landscape (development quality
assurance and production system) in one SAP Solution Manager system In case you plan to install
several solution landscapes (for example in different countries) one SAP Solution Manager
system is still sufficient
For more information see SAP Note 805390
It is possible to install multiple SAP Solution Managers If you do so they should host separate business
solutions
If you want to reduce the risk of unavailability you should not install SAP Solution Manager as a central
component Instead you can operate a 2-system-landscape with both a test and production
environment of SAP Solution Manager (especially if you are using time-critical functions like Support
Desk) If you also develop your own content a 3-system-landscape with a development test and
production environment is recommended
For more information about SAP Solution Manager see the following table
Topic Where to Find More Information
System infrastructure scenarios installation and configuration of SAP Solution Manager
Master Guide ndash SAP Solution Manager available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution ManagerltReleasegt
Benefits and usage scenarios SAP Solution Manager ndash Learning Maps available on SAP Service Marketplace at http
5 System Landscape
52 Shared Services
4256 PUBLIC 2011-04-15
Topic Where to Find More Informationservicesapcomrkt-solman or https
servicesapcomsolutionmanager
Additional information See SAP Service Marketplace at http
servicesapcomsolutionmanager
5232 Solution Manager Diagnostics
Solution Manager Diagnostics provides efficient and safe root-cause analysis of incidents in customer
solutions powered by SAP NetWeaver It can help monitor on operating systems databases Java
application activities performance and logs It also supports the reporting of software and
configuration changes that can lead to malfunctions and errors
You must run one Solution Manager Diagnostics within your SAP solution landscape if you run
applications based on SAP NetWeaver systems with usage type AS Java Agents are responsible for
delivering the data from all productive hosts within your system landscape to the Solution Manager
Diagnostics system
CAUTION
SAP Support performs root-cause analysis on incoming incidents with Solution Manager
Diagnostics Not installing and configuring this support infrastructure results in a dramatically
reduced service level
Solution Manager Diagnostics is fully integrated into SAP Solution Manager 70
Solution Manager Diagnostics also contains Wily Introscope (Display Server and Agent part) for
measuring performance as well as to troubleshoot problems of Non-ABAP applications Wily Introscope
is heavily used for troubleshooting applications running on AS Java
SAP has signed a distribution agreement for Wily Introscope SAP customers are allowed to use this
tool in a preconfigured way
For more information about Solution Manager Diagnostics and an FAQ list see SAP Service Marketplace
at httpservicesapcomdiagnostics
5233 System Landscape Directory
The System Landscape Directory (SLD) of SAP NetWeaver is the central directory of system landscape
information relevant for the management of your software life-cycle
NOTE
Note that the abbreviation SLD is not intended to define a product since the System Landscape
Directory is part of SAP NetWeaver This abbreviation is solely intended to improve readability
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4356
The System Landscape Directory contains a description of your system landscape (that is software
components that are currently installed) and a repository of software components that can
theoretically be installed in your landscape (such as the software components available from SAP)
Since this data gets updated automatically the System Landscape Directory provides reliable and up-
to-date system landscape information with as little effort for you as possible In this way the System
Landscape Directory acts as a central information provider for SAP and third-party tools that use this
data to deliver the services you need to keep your landscape up and running
For the System Landscape Directory as part of an SAP NetWeaver PI 71 landscape consider the following
aspects
Part of SAP NetWeaver PI 71 is a new version of the System Landscape Directory It is automatically
included in every SAP NetWeaver 71 system with usage type AS Java It offers enhanced functions
such as a full automatic synchronization mechanism for all data stored in it That is both data
delivered by data suppliers and data entered or changed manually in the System Landscape
Directory can be synchronized automatically This synchronization offers the following
A fully automated mechanism so no user interaction is required and conflicts are resolved
automatically
Asynchronous propagation of information so some nodes may be down temporarily
Communication over HTTP protocol
Uni- and bi-directional synchronization
Depending on your use case the full automatic synchronization could significantly reduce manual
synchronization effort
For SAP NetWeaver PI 71 the configuration of the system landscape directory and its data suppliers
is already included in the standard implementation procedure with SAPinst For existing systems
you only have to perform some quick and easy configuration actions to start operating the system
landscape directory server in an AS Java system
For SAP NetWeaver PI 71 you have the following options concerning SLD
Option 1
Run SAP NetWeaver PI 71 against an existing SLD running on SAP NetWeaver 70 We only
recommend this for upgrades from SAP NetWeaver 70 if you have a central SLD in operation
not running on one of your PI systems
Option 2
Use the SLD included in an SAP NetWeaver PI 71 system We recommend this option for new
installations and upgrades from older releases than SAP NetWeaver 70 due to the enhanced
functions and improved performance of SLD 71
NOTE
If you already have a central SLD running on SAP NetWeaver 70 in operation you could run
two SLD versions in parallel ndash SLD running on SAP NetWeaver 71 for your PI systems and
SLD running on SAP NetWeaver 70 for all other systemsuse cases This way your SAP
5 System Landscape
52 Shared Services
4456 PUBLIC 2011-04-15
NetWeaver PI 71 systems would benefit from the new features while it would be easy to set
up and operate such an SLD landscape For this purpose you could use the new fully
automatic synchronization This feature enables the automatic forwarding of all SLD data
from an SLD running on SAP NetWeaver 70 to an SLD running on SAP NetWeaver 71 As a
result there is no need to adapt most existing systems as their SLD data suppliers could still
send their data to the central SLD In brief the following steps would be required
1 Put SLD in a PI system into operation (part of standard implementation procedure)
2 Configure PI systems to use the new SLD (part of standard implementation procedure
for new PI systems)
3 Set up the fully automatic synchronization from your old SLD to your new SLD
As soon as an upgrade or an installation of a standalone AS Java 71 system is available you
could move your central SLD also to SAP NetWeaver 71 Then you could optionally shift
your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems
Figure 8
We recommend that you use a Domain Name System (DNS) alias so that you are able to switch to
another System Landscape Directory easily For example if customers build a new landscape they
normally start with a sandbox environment Over time more and more environments are set up
Once the production environment is in place move the System Landscape Directory there To do
this you can configure a new System Landscape Directory in the production environment
synchronize it with the old System Landscape directory and switch to the new one
Topology
Apart from the considerations above the System Landscape Directory offers several topology options
with different grades of availability at the expense of low administration and operation effort There is
no generic rule therefore on how to set up a System Landscape Directory in your system landscape
To find the topology and synchronization strategy for the System Landscape Directory that fits your
requirements concerning the System Landscape Directory availability (and hence the availability of
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4556
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
Content Location on SAP Service Marketplace or in SAP Library
Information about SAP NetWeaver PI Support Package Stacks
httpservicesapcomnetweaver SAP NetWeaver PI 71- Release-Specific Information Support Package Stacks Information
Information about installing SAP NetWeaver Support Package Stacks
httpservicesapcomMaintenanceNWPI71
Support Package Stack Guide ndash SAP NetWeaver
23 Accessing the SAP Library
For more information about SAP NetWeaver Process Integration access the SAP Library from any of
the following
SAP Help Portal at httphelpsapcomNWPI71 SAP NetWeaver Process Integration 71 Library
ltLanguagegt SAP NetWeaver Process Integration Library
CAUTION
The SAP Help Portal contains the latest version of the SAP Library Therefore we recommend
that you use this channel to access the SAP Library
An SAP system if you have installed the online documentation Choose Help SAP Library
The browser starts
The help files on the online documentation CDs or DVDs
If you want to view the help files in HTMLHelp format from the online documentation CDs or
DVDs you need a PC running Microsoft Windows to install the HTMLHelp Viewer
2 Before You Start
23 Accessing the SAP Library
1256 PUBLIC 2011-04-15
3 SAP NetWeaver PI Overview
Introduction
SAP NetWeaver PI 71 is part of the SAP NetWeaver technology platform The complete offering of the
SAP NetWeaver technology platform is visualized in the SAP NetWeaver technology map which you
can access at httpsdnsapcomnetweaver SAP NetWeaver at a Glance The technology map
enables you to drill down from top-level technology areas (for example Lifecycle Management) to
individual capabilities (for example Administration Monitoring and so on)
SAP NetWeaver PI includes the following capabilities
Repository-based Modeling and Design
Service Bus-based Integration
SOA Management
A different view is introduced by the end-to-end use case concept This concept offers an
implementation view on SAP NetWeaver to structure and facilitate your implementation
A use cases is a process that typically involves several SAP NetWeaver capabilities It is not limited to a
single component or capability A use case guides you through the different phases of your
implementation project ndash from information through installation to the configuration phase This
implies that a uses case addresses several user roles administrator power user and end user
This document describes the SOA-based integration use case
Architecture Principals
The architecture of SAP NetWeaver Process Integration 71 (SAP NetWeaver PI 71) is based on an
established architecture for realizing cross-system business processes and is a further development of
lower releases (SAP NetWeaver 70 usage type Process Integration and SAP XI 30 as part of SAP
NetWeaver 2004) SAP NetWeaver PI 71 plays an important role in supporting an service-oriented
architecture (SOA) The focus is on the service-based integration of applications
SAP NetWeaver PI is based on general standards so as to enable 3rd-party systems to be integrated At
the center of SAP NetWeaver PI is an XML-based communication that uses HTTP (Hyper Text Transfer
Protocol) Irrespective of the scenario used the application-specific contents are transferred in messages
in user-defined XML (eXtensible Markup Language) from the sender to the receiver either via the
Integration Server or directly between the systems involved
The following figure gives an overview of the key capabilities of SAP NetWeaver Process Integration
3 SAP NetWeaver PI Overview
2011-04-15 PUBLIC 1356
Figure 1 SAP NetWeaver PI Key Capabilities Overview
SAP NetWeaver Process Integration 71 enables the integration of the applications of the following
communication parties
B2B Party Any business partners that want to integrate their application with other applications
outside their own system landscape Scenarios that require industry standards are supported as
well as any scenarios that do not adhere to a particular industry standard
SAP Applications that run on SAP systems This includes the processing of events by using the
Business Activity Monitoring (BAM) infrastructure
3rd-Party Application Applications from 3rd-party providers within one system landscape for
example database or file-system-based
3rd-Party Middleware Middleware systems from 3rd-party providers that are required for the
integration of applications within a company and across company boundaries
SAP NetWeaver PI also supports internal company scenarios and cross-company scenarios It enables
you to connect systems from different vendors (non-SAP and SAP) in different versions and
implemented in different programming languages (Java ABAP and so on) to each other Like the rest
of the SAP NetWeaver platform SAP NetWeaver PI is based on an open architecture uses open standards
(in particular those from the XML and Java environments) and offers those services that are essential
in a heterogeneous and complex system landscape
To enable end-to-end SOA development SAP NetWeaver Process Integration 71 offers a Universal
Description Discovery and Integration (UDDI) v3-based Services Registry where providers can publish
service endpoints definitions and associated metadata and consumers can discover the appropriate
services for their scenarios The Services Registry provides capabilities for classifying and browsing
3 SAP NetWeaver PI Overview
1456 PUBLIC 2011-04-15
services using semantic-rich classification systems The Services Registry is part of Application Server
Java (AS Java)
31 Installable Software Units
SAP NetWeaver comprises the following three types of installable software units
Systems that are configured for a specific purpose as indicated by one or more usage types
Standalone engines that provide one specific (server) function in combination with one or more
SAP NetWeaver PI systems
Clients used by (many) people from their local front-end PC to access functions offered by systems
of SAP NetWeaver PI or standalone engines in the system landscape
In the following sections you can find more details about the software units The figure below provides
and overview of the software units
Figure 2 Installable Software Units for SAP NetWeaver PI
For this and other figures in this guide the following legend applies
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1556
Figure 3 Legend
311 Systems with Usage Types
SAP systems are the main building blocks of SAP NetWeaver They are identified by unique SAP system
IDs (SAPSIDs) and configured for a certain purpose as indicated by usage types Usage types have the
following characteristics
They are a structuring element for SAP software on a technical level
Usage Types determine the intended purpose of a system and the role it plays in a given (distributed)
use case
They are realized by installing and configuring a collection of software components
They allow a logical view of the technology platform SAP NetWeaver PI
A usage type may require other usage types in the same system to operate
They can also be run in the same system together with other usage types that are not a prerequisite
How SAP NetWeaver Systems are Used
The following sections describe the usage types and their dependencies for SAP NetWeaver PI
Application Server ABAP (AS ABAP)
Purpose
AS ABAP is used to provide the ABAP foundation of SAP NetWeaver PI
Application Server ABAP provides a complete development and runtime environment for ABAP-based
applications It is optimized for the development of highly scalable business applications The ABAP
development and runtime environment makes it possible to develop complex business applications
3 SAP NetWeaver PI Overview
31 Installable Software Units
1656 PUBLIC 2011-04-15
without having to worry explicitly about technical details such as process or memory administration
multi-user capability database connections or similar issues These are provided in the basis services or
are integrated directly in the ABAP runtime The application development is similarly independent of
the underlying platform The application server decouples the application coding completely from the
operating system and database that are used
Dependencies
AS ABAP can be combined optionally with other usage types in one system
Application Server Java (AS Java)
Purpose
AS Java is used to provide the Java foundation of SAP NetWeaver PI using the Java Engine a Java EE-
compliant application server for running enterprise applications In addition to the pure Java EE
standard technologies the Java Engine implements complementary technologies such as Web Dynpro
or Web Services that are targeted at supporting large-scale real-business application development
projects
Dependencies
AS Java can be combined optionally with other usage types in one system
Process Integration (PI)
Purpose
PI consists of core components that model design automate and integrate processes in one or more
application systems For the integration of internal and cross-company processes PI is used to
incorporate all the functions of what was formerly known as Exchange Infrastructure (XI) In addition
PI contains core components for Business Process Management for application-embedded and
application-unbounded processes
The Advanced Adapter Engine is also part of usage type PI You use Advanced Adapter Engine to connect
to SAP systems (RFC adapter) and external systems You use the various adapters in Advanced Adapter
Engine to convert XML- and HTTP-based messages to the specific protocol and format required by
these systems and the other way around You can use the Advanced Adapter Engine that is part of
your PI system as a central Advanced Adapter Engine Optionally (for performance reasons) you can
install a non-central Advanced Adapter Engine [page 19] separately as a system with AS Java and parts of the
usage type PI on a separate host
Dependencies
PI requires AS ABAP and AS Java as prerequisites in the same system
For installing PI it is mandatory to have a dedicated PI system This applies to development quality
and production landscapes It is a prerequisite that no other system in your system landscape has a
higher release and enhancement package level than the PI system If you want to upgrade or install an
application in your system landscape you first have to make sure that the current release and
enhancement package level of the PI system is on the same level - if required you have to upgrade the
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1756
PI system first to the new or a higher release In a dedicated PI system this can be accomplished with a
minimum of downtime Also the PI system would not be affected by the downtime of other usage
types running in the same system
Configuration of Systems with Usage Types
Configuration information is available in the installation guides the configuration wizard and SAP
Solution Manager
In the Installation Guide ndash SAP NetWeaver PI 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt you find
initial technical configuration tasks This guide also informs you about how you can run the
configuration wizard and how you can access the configuration information in SAP Solution
Manager
For certain usage types configuration tasks can be applied by the configuration wizard after the
installation To do this you start the configuration wizard from SAP NetWeaver Administrator
The configuration steps for systems with usage types required for an use case are accessible through
SAP Solution Manager
To be able to use SAP Solution Manager for the configuration tasks you have to import the latest
SAP Solution Manager Implementation Content (Add-On ST-ICO) that is available for your SAP
Solution Manager release For more information see SAP Note 631042 (Release strategy for Implementation
Content (ST-ICO))
SAP Solution Manager Implementation Content is available on SAP Service Marketplace at
httpservicesapcomswdc Installations amp Upgrades Entry by Application Component SAP
Technology Components SAP Solution Manager ltReleasegt Content ST-ICO
In SAP Solution Manager you create a project and a project structure In the configuration phase
you select configuration structures with pre-delivered SAP content for your project You can find
the following different types of configuration tasks in SAP Solution Manager
Mandatory configuration tasks All configuration tasks that are mandatory for the standalone
engine or usage type
Optional configuration tasks Configuration tasks for areas where customers need to decide
if they want to use these functions (for example high availability or security settings)
Additional functions ndash configuration tasks Configuration tasks for functional units that are
used in certain use cases only
A marked checkbox in front of the configuration tasks indicates those configuration tasks that are
relevant for the use case you have chosen To configure ABAP systems SAP Solution Manager
offers executable configuration files (IMG activities)
For information about using SAP Solution Manager Content and creating a configuration guide
see the following documentation
httphelpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Implementing
and Upgrading SAP Solutions Configuration
3 SAP NetWeaver PI Overview
31 Installable Software Units
1856 PUBLIC 2011-04-15
How to Create a Configuration Guide using SAP Solution Manager available at http
servicesapcomsolutionmanager Media Library How-To Documents
Restrictions for Systems with Multiple Usage Types
If you have one system with multiple usage types be aware that we do not provide standard tools
to separate these usage types and distribute them to multiple systems at a later stage For example
if you have a system with usage types A and B you are not able to migrate it with SAP standard
tools into two systems one with usage type A only and the other with usage type B only
In addition we do not provide standard tools to merge multiple systems with different usage types
into one system with multiple usage types at a later stage
If you want to perform these tasks you require specific project support
The following figure shows that SAP standard system copy and migration tools do not support
you in separating or merging systems with usage types
Figure 4 No Support for Merging or Separating Systems with Usage Types
Although you can use one system for multiple usage types client restrictions apply for usage type
PI PI requires a dedicated client due to special PI requirements concerning the client pipeline
Whereas application client pipelines only send and receive messages the central PI pipeline can
also map messages to different formats before sending them
312 Standalone Engines
Standalone engines of SAP NetWeaver are additional installable software units They do not work as
full-blown systems of SAP NetWeaver but as standalone engines that provide a specific (server) function
in combination with one or more SAP NetWeaver systems
Standalone engines are not part of a usage type They do not run on AS ABAP or AS Java
The standalone engines that are available for SAP NetWeaver Process Integration are described in the
following
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1956
Gateway
It is possible to install an SAP instance of an SAP NetWeaver system based exclusively on a standalone
gateway This type of instance does not contain normal work process types (dialog background update
enqueue or spool) Only the gateway process (gwrd) is started If there is an SNA connection to an R
2 system gateway work processes (gwwp) are also started
SAP Conversion Agent by Informatica
SAP Conversion Agent by Informatica is a data conversion tool that enables you to create interfaces
between any data formats and XML-based systems SAP Conversion Agent can convert unstructured
semi-structured and structured formats to XML and the other way around The Conversion Agent
comprises the Conversion Agent Studio and the Conversion Agent Engine In the Conversion Agent
Studio you can develop and configure data conversions The Conversion Agent Engine executes the
data conversions
Search and Classification (TREX)
You can use Search and Classification with SAP NetWeaver PI to search for messages that were previously
indexed Message search using index provides additional methods of searching for specific messages In
addition to static header attributes you can also use adapter-specific message attributes and data from
the message payload for the search A requirement of this however is that the messages are indexed
first You can apply the index-based message search to one or all indexed components of an integration
landscape (domain) Integration Server Adapter Engines and ABAP business systems
For more information see the SAP Library [page 12] at Administratorrsquos Guide Technical Operations for SAP
NetWeaver Administration of SAP NetWeaver Systems Administering PI (Process Integration) Monitoring Index
Administration
Web Dispatcher
The Web Dispatcher lies between the Internet and your SAP system It is the entry point for HTTP(s)
requests into your system which consists of one or more SAP NetWeaver application servers As a
software web switch the Web dispatcher can reject connections or accept them When it accepts a
connection it balances the load to ensure an even distribution across the servers
You can use the Web dispatcher in ABAPJava systems and in pure Java systems as well as in pure ABAP
systems
It is also beneficial to use the Web Dispatcher if you do not need security functions (entry point in the
demilitarized zone (DMZ) SSL URL filtering) but you simply want to balance the load between
multiple SAP NetWeaver Application Server instances
Since Web Dispatcher is optional for every SAP system it is not contained in the system landscape and
the implementation sequence of the use case in this documentation
For more information see the SAP Library [page 12] at Function Oriented View Application Server Infrastructure
SAP Web Dispatcher
3 SAP NetWeaver PI Overview
31 Installable Software Units
2056 PUBLIC 2011-04-15
Advanced Adapter Engine
You use the Advanced Adapter Engine to connect to SAP systems (RFC adapter) and external systems
You use the various adapters in Advanced Adapter Engine to convert XML- and HTTP-based messages
to the specific protocol and format required by these systems and the other way around For specific
senderreceiver combinations messages can be processed without invoking the central Integration
Engine In principle you connect external systems using the adapters that are installed centrally or
non-centrally in Advanced Adapter Engine You can use the Advanced Adapter Engine that is part of
your PI system as a central Advanced Adapter Engine Optionally (for performance reasons) you can
install a non-central Advanced Adapter Engine separately as a system with AS Java and parts of the
usage type PI on a separate host
Adapter Engine (Java SE)
Adapter Engine (Java SE) is a separate software unit You can use it only if you have SAP NetWeaver
systems with usage type PI in your system landscape It has to be installed manually You use the Adapter
Engine (Java SE) to connect to external systems Using the various adapters in the Adapter Engine (Java
SE) XML and HTTP-based messages can be converted to the specific protocol and format required by
such systems and the other way around The Adapter Engine (Java SE) only provides some of these
adapters as a standalone version with restricted functions for operating systems that do not support
SAP NetWeaver PI 71 but that have at least a Java Runtime Environment 50 Therefore you should
use the Adapter Engine (Java SE) only if the platform prerequisites do not allow you to use the Advanced
Adapter Engine
SAP Partner Connectivity Kit
SAP Partner Connectivity Kit (PCK) runs on AS Java with parts of the usage type PI It enables a system
of a smaller company or subsidiary that does not run SAP NetWeaver PI to connect to your SAP
NetWeaver systems
313 Clients
Clients are additional installable programs or tools They reside either on local front-end PCs accessed
by users or on back-end systems where they act as client programs within an SAP NetWeaver system
landscape
The clients that you can use with SAP NetWeaver Process Integration are described in the following
sections
SAP GUI
NOTE
We recommend that you use the following versionsI
SAP GUI for Windows 710 (or higher) with the latest patch level
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 2156
SAP GUI for Java 710 (or higher) with the latest revision
The integrated SAP ITS 710
For more information about the SAP GUI family see SAP Service Marketplace at http
servicesapcomsapgui
SAP offers three different client applications for accessing ABAP applications in SAP systems (such as
SAP NetWeaver systems with usage type AS ABAP) This SAP GUI family consists of
SAP GUI for HTML
SAP GUI for HTML is based on the SAP integrated Internet Transaction Server (ITS) which is
included in the installation of SAP NetWeaver systems as of SAP NetWeaver 2004 On the client
side only a suitable browser (such as Internet Explorer 70 or Firefox 20) and a virtual machine are
required SAP ITS 620 is not compatible with SAP NetWeaver 71
SAP GUI for the Java environment (SAP GUI for Java)
SAP GUI for Java is a generic SAP GUI that covers a variety of platforms
For more information about the installation of SAP GUI for Java see the documentation Installation
Guide ndash SAP Front End
SAP GUI for the Windows environment (SAP GUI for Windows)
SAP GUI for Windows is SAPs universal client for accessing all SAP applications built on ABAP
technology It is available on the Microsoft Windows platform only and offers the broadest feature
set of all members of the SAP GUI family
For more information about the installation of SAP GUI for Windows see the Installation Guide ndash
SAP Front End
SAP NetWeaver Developer Studio
The SAP NetWeaver Developer Studio is SAPrsquos Integrated Development Environment (IDE) for Java
and is based on the open-source tools framework Eclipse 33 With the SAP NetWeaver Developer Studio
you can develop Java EE 5 applications from scratch using the built-in support for new technologies
such as EJB 30 and JSF 12
During the installation of the SAP NetWeaver Developer Studio several features are offered for
installation For SAP NetWeaver PI 71 only the following features are relevant
SAP NetWeaver Developer Studio Platform
SAP NetWeaver Developer Studio Java EE
NOTE
If you want to use one of the other features you need SAP NetWeaver Composition Environment
and a corresponding developers licence
For more information about the installation of SAP NetWeaver Developer Studio see the Installation
Guide ndash SAP NetWeaver Developer Studio 71 or Installation Guide ndash SAP NetWeaver Developer Studio 71 Including
Enhancement Package 1
3 SAP NetWeaver PI Overview
31 Installable Software Units
2256 PUBLIC 2011-04-15
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
SAP enhancement packages are a new way of delivering new functions for SAP NetWeaver This allows
a clear separation between the delivery of new functions on the one hand and corrections legal changes
and security updates on the other hand (in Support Package stacks) SAP enhancement packages are
cumulative an enhancement package always contains the functions of the corresponding predecessor
enhancement packages
Enhancement packages are maintained by their own Support Packages while the main release is in
maintenance
Benefits
SAP enhancement packages offer the following benefits
You have reduced effort for testing and no effort for training when applying Support Packages as
new features are only shipped with enhancement packages
Adding new functions between releases becomes predictable and controllable
New functions can be added successively in small steps There is no need to fully upgrade your
system to get new functions
You have minimal training effort when applying an enhancement package because existing
functions are not replaced
Implementation
There are the following ways to get an SAP NetWeaver system with the release level of SAP enhancement
package 1 for SAP NetWeaver Process Integration 71
New installation of SAP NetWeaver PI 71 including enhancement package 1 using the standard
installation tool SAPinst
Upgrade of an existing SAP NetWeaver system from a release lower than SAP NetWeaver PI 71 to
SAP NetWeaver PI 71 including enhancement package 1 For this you use the upgrade programs
SAPup (for ABAP) and SAPJup (for Java)
Installation of the enhancement package on an existing SAP NetWeaver PI 71 system
For this you use the Software Update Manager (SUM) The Software Update Manager evolved
from the previously used SAP Enhancement Package Installer The tool has been renamed to reflect
its broader use for example you can also use it for applying Support Package Stacks to your system
On the ABAP side the Software Update Manager uses a system cloning and switch procedure for
installing enhancement packages It installs a copy of the system the shadow system parallel to
the original system This shadow system is used to update the relevant software components and
to install the additional components while the original system is still in production operation At
a certain point during downtime the switch to the new system is made and afterwards any parts
of the original system that are no longer needed are deleted The enhancement package installation
in a Java system uses a deploy-based procedure that is no shadow system is used The Software
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2011-04-15 PUBLIC 2356
Update Manager requires a stack configuration file (xml file) as input file for the enhancement
package installation procedure This file lists all the packages that are to be installed in your systems
The stack configuration file is generated when you download the required packages
As the Software Update Manager is updated regularly we recommend to always use the latest
version It is delivered as part of the SL toolset For more information see http
servicesapcomsltoolset
For an overview of all required steps for the enhancement package installation process and
corresponding documents see Process Overview Installation of Enhancement Package 1 on an Existing SAP
Netweaver PI 71 System [page 28]
Content of SAP Enhancement Package 1 for SAP NetWeaver PI 71
With enhancement package 1 for SAP NetWeaver PI 71 new features are introduced and some existing
are changed The following is a selection of some of the most important enhancements
Enhanced design and modelling options in the Enterprise Services Repository
New services registry
Support for new Web services standard (Web Services Reliable Messaging)
New modules for the Advanced Adapter Engine
Use of shared memory of the ABAP Application Server for message processing
For more information about the changes see SAP Library [page 12] at Whatacutes new in SAP NetWeaver PI 71
ndash Release Notes
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2456 PUBLIC 2011-04-15
4 SOA-Based Integration Use Case
41 Overview
You can use SOA-based integration to set up the communication between service providers and service
consumers in both application-to-application and business-to-business scenarios and to execute
operate and monitor the communication at runtime SOA-based integration covers both direct (point-
to-point) as well as mediated (via an Integration Server) communication between service providers and
service consumers
The use case spans the whole life cycle of a SOA-based integration scenario including
Scenario modeling and service design in the Enterprise Services Repository
Implementation of the service provider and consumer in the back-end systems
Configuration and finally execution monitoring and operation of the integration scenario
For scenarios using Integration Server or broker-based communication the configuration of the
different connectivity options (for example SOAP RFC Web Services Industry standards and JDBC)
and their enhancements is covered
For more information see the following documents
Service-Enabling with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdnsoa-modeling
Getting Started
Service-Enabling a Legacy Application with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdn
soa-servicebus Getting Started
In the following you will find information about the installation of the involved software units
42 System Landscape
The following figure shows the system landscape for this use case
4 SOA-Based Integration Use Case
41 Overview
2011-04-15 PUBLIC 2556
Figure 5 SOA-Based Integration
It is mandatory to have a dedicated PI system This applies to development quality and production
landscapes
For PI it is a prerequisite that no other system in your system landscape has a higher release than
the PI system For exceptions to this rule see SAP Note 1043047 For example SAP XI 30 is compatible
with SAP NetWeaver 640 and 70 application systems since the same XI protocol is used Apart
from these exceptions if you want to upgrade or install an application in your system landscape
you first have to make sure that the PI system is on the same release level If required you have to
upgrade the PI system first to the new or a higher release
CAUTION
Although it should be technically possible to run an application system with a higher release
than your PI system in your system landscape this is not supported by SAP (apart from the
exceptions listed in SAP Note 1043047) Therefore you run such a landscape at your own risk
You can use the Advanced Adapter Engine that is part of your PI system as a central Advanced
Adapter Engine
Adapter Engine (Java SE) can be installed in a non-SAP Java environment However it only hosts
a subset of the adapter functionality is only supported for compatibility reasons and should be
used only if this is a precondition in your environment
Optionally you can use the Change Management Service (CMS) of an SAP NetWeaver 70 system
with usage type DI to transport design objects and repository objects For more information see
the SAP Library [page 12] at Administratoracutes Guide Technical Operations for SAP NetWeaver Administration
of SAP NetWeaver Systems PI (Process Integration) Software Logistics Transporting ESR Content and Objects
of Integration Directory PI Transports Using the Change Management Service (CMS)
Smaller business partners or subsidiaries that do not run SAP NetWeaver install SAP Partner
Connectivity Kit in their system landscape SAP Partner Connectivity Kit enables XML document
4 SOA-Based Integration Use Case
42 System Landscape
2656 PUBLIC 2011-04-15
exchange between your SAP NetWeaver systems and the partner systems Since SAP Partner
Connectivity Kit gets installed in their system landscape it is not shown in the system landscape
figure above
The AS ABAP system acts as an application and service provider For Java Web Services you also
require AS Java In addition you require SAP NetWeaver Developer Studio on the client side as a
development environment
The Web service client can be either an SAP or a non-SAP application For example an AS ABAP
system or a Web browser could act as application or service consumer
You can install SAP Conversion Agent by Informatica in the system with usage type PI or on a host
where SAP Partner Connectivity Kit is installed or on a host where neither usage type PI nor SAP
Partner Connectivity Kit is installed
43 Implementation Sequence
Procedure
To install this use case perform the steps listed in the following table
StepAction[Corresponding Documentation] Remarks
1 Make sure that you have performed the preparation steps You have planned your system landscape [page 33]
(that is you have decided how many systems you require how you want to use each of these systems and which standalone engines and clients you require)
With the help of your hardware partner you have mapped your systems and standalone engines to properly sized hosts
You have planned and installed shared services [page 35]
2 Installation of system with usage type PI (includes the installation of AS ABAP and AS Java)
NOTE
For usage type PI a Unicode installation is mandatory
[Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt]
If you want to use the features of enhancement package 1 use the direct installation of SAP NetWeaver PI 71 including enhancement package 1
Make sure that you perform the configuration steps as described in the installation guide For certain usage types configuration tasks can be applied by the configuration wizard These configuration tasks as well as any additional configuration steps for your use case are listed in SAP Solution Manager For more information
4 SOA-Based Integration Use Case
43 Implementation Sequence
2011-04-15 PUBLIC 2756
StepAction[Corresponding Documentation] Remarks
see the Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt
3 Install the Adapter Engine (Java SE) engines if required[Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
4 To integrate small business partners and subsidiaries the business partners or subsidiaries install SAP Partner Connectivity Kit running on AS Java with parts of usage type PI in the business partners or subsidiarys system landscape[Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
5 Install SAP Conversion Agent by Informatica if required[SAP Library [page 12] at Function-Oriented View Process Integration SAP Conversion Agent by Informatica Deploying and Using Conversion Agent ]
6 Installation of clients SAP GUI
[Installation Guide ndash SAP Front End]
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
The process sequences give a comprehensive overview of the steps relevant for the enhancement
package installation on an existing SAP NetWeaver PI 71 system
The process sequence is divided into a planning phase and an implementation phase Each step in both
phases contains references to the corresponding documentation to ensure that you can easily find the
information you need
Process
NOTE
To download the enhancement package files and required Support Packages you require the SAP
Solution Manager Maintenance Optimizer You have the following options
Manual Selection
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2856 PUBLIC 2011-04-15
You manually select the required files from SAP Service Marketplace at http
servicesapcomswdc using the SP Stack Application You use the Maintenance Optimize
only to approve the packages which is a prerequisite for the download
Automatic Calculation
The Maintenance Optimizer supports the download of a consistent queue that includes all
necessary Support Packages and enhancement packages In addition SAP Solution Manager
calculates a valid import queue for the selected SAP system and generates the enhancement
package stack configuration file that you require for the installation
As a prerequisite the system that you want to update needs to be maintained correctly in
SAP Solution Manager System Landscape As the Maintenance Optimizer uses this data for
the calculation it is crucial that the data is up-to-date In addition the SAP Solution Manager
system requires a Minimum Support Package level (see below)
Planing PhaseStep Description Documentation
Hardware amp Software Prerequisites
Check which platforms are supported for your target release (OSDB dependencies)
Product Availability Matrix (PAM) at httpservicesapcompam
Check which hardware sizing is required for your target release
Sizing information at httpservicesapcomsizing
Solution Manager Prerequisites
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of the required software packages you have to make sure that your SAP Solution Manager system has the required Support Package levelAt least SAP Solution Manager 70 EHP1 Support Package Stack 17 is required We recommend to use SAP Solution Manager 70 EHP1 Support Package Stack 23Check if you need to do an update or upgrade of your SAP Solution ManagerMake sure that you run the guided procedure SOLMAN_SETUP after every installation or update of SAP Solution Manager and that it completes successfully
For upgrades from source release SAP Solution Manager 31 and 32Upgrade Guide ndash SAP Solution Manager 70 incl Enhancement Package 1For updates from SAP Solution Manager 70Update Guide SAP Enhancement Package 1 for SAP Solution Manager 70Follow-up activities after an Support Package Stack update or enhancement package updateSolution Operations Guide ndash SAP Solution Manager 70 EHP1 section Software Change Management All guides are available at http
servicesapcom instguides SAP Components SAP Solution Manager -gt Release 70 EHP 1
Implementation PhaseStep Description Documentation
1Solution Manager Preparation
Configure the SAP Solution Manager Maintenance Optimizer
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of software packages make sure your
Configuration of Maintenance Optimizer http
helpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Change Request Management and Change ControlMaintenance Optimizer
Prerequisites
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 2956
Implementation PhaseStep Description Documentation
system landscape data in SAP Solution Manager is maintained correctlyLandscape Verification 10 which is an add-on to SAP Solution Manager can support you in maintaining your system landscape data The use of this tool is optional
Landscape Verification http
wwwsdnsapcom irj
sdn alm-update-
management link Landscape Verification under Related Areas on Upgrade and Update Management (in the right column)
SAP Note 1468605 (Installation of Landscape Verification)
Maintaining System Landscape Information [page 47]Note that the information provided in this section is based on SAP Solution Manager 70 EHP1 SP23
2System Preparation
Prepare your system as described in the documentation for example perform OS DB specific preparations and the PI-specific preparations
Update Guide ndash Update of SAP Systems with Software Update Manager sections Planning and Preparation
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
3Software Download
Select and download the software packages in either of the following ways Automatic calculation Create
a maintenance transaction in the Maintenance Optimizer and choose the Calculate Files Automatically option
Manual Selection Create a maintenance transaction in the Maintenance Optimizer and choose the Select Files Manually option You then can select the files manually using the SP Stack application in SAP Service Marketplace
NOTE
You have to download the stack configuration file manually after you have selected all files in the SP Stack
httphelpsapcom SAP Solutions SAP Solution Manager
SAP Solution Manager 70 EHP1 ltSPgtChange Request Management and
Change Control Maintenance Optimizer Maintenance Procedure Scenarios
For information about the automatic calculation see Maintenance Transaction with Installation of an Enhancement PackageFor information about the manual selection and approval process see section Approve and Download Files in Download Basket
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
3056 PUBLIC 2011-04-15
Implementation PhaseStep Description Documentation
application Choose Generate Stack XML and save the file
4Enhancement Package Installation
Run Software Update Manager to update your system with the selected software packages
Update Guide ndash Update of SAP Systems with Software Update Manager
5Follow-Up Steps
Perform technical and PI-specific follow-up activities after the enhancement package installation is done
Update Guide ndash Update of SAP Systems with Software Update Manager section Follow-Up Activities
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
6Configuration
Configure newly installed enhancement package functions using SAP Solution Manager content
See Systems with Usage Types [page 16] section Configuration of Systems with Usage Types
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 3156
This page is left blank for documents that are printed on both sides
5 System Landscape
51 Planning Your System Landscape
The installable software units that make up your system landscape depend on the functions that you
want to implement For information about the features see systems [page 16] standalone engines [page 19]
and clients [page 21]
In addition you have to determine the required shared services [page 35] (such as SAP Solution Manager
or SAP NetWeaver Administrator) that run on central systems in your system landscape and the
landscape aspects relevant for their implementation
In the following you will find general information that you should consider when planning your system
landscape
Sizing
You have to map systems and standalone engines to hosts after you have a clear picture of the following
Which systems and standalone engines you require
How many systems you require and how you want to use each of these systems
NOTE
No general guideline can be given for the sizing of your landscape since this relies heavily on your
requirements You should therefore perform this task together with your hardware partner and
your technical consultant
For information about sizing your systems you can use the following information sources
Your first point of reference is the Quick Sizer
SAP built the Quick Sizer as an online sizing questionnaire Internet application in close cooperation
with its hardware partners This tool delivers general sizing categories based on your volume load
estimates The results provide an objective basis for sizing independent of platform and
configuration
For more information see SAP Service Marketplace at
httpservicesapcomsizing for the SAP NetWeaver PI 71 sizing guide available under
Sizing Guidelines Business Suite amp Services
httpservicesapcomquicksizer for more information and access to the tool itself
Also consider the following important aspects concerning sizing
High availability
5 System Landscape
51 Planning Your System Landscape
2011-04-15 PUBLIC 3356
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Technical Infrastructure High Availability
Unicode
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Internationalization
Contact your hardware partner to find out the appropriate number of sized hosts
The platform-independent abstract results of the Quick Sizer can be used by any of our hardware
partners to create a concrete offer SAP itself does not make any hardware recommendations the
responsibility for sizing and detailed hardware configuration lies with the hardware partners
Figure 6 Example of Mapping of Systems and Standalone Engines to Three Hosts
NOTE
Optionally you could also distribute single systems to multiple hosts For example you could
decide to install the database instance of an SAP system on a separate host for performance
reasons or distribute other system instances to achieve high availability
To provide a mapping that fits your required functions and performance your hardware partner
and your technical consultant have to identify the number of required instances of SAP NetWeaver
find out how to distribute these instances to hosts and what functions will run on which instance
Therefore the hardware partner and the technical consultant have to consider many different
aspects such as
Number of required SAPS (SAP Application Benchmark Performance Standard) for each
system (provided by Quick Sizer)
Landscape-relevant aspects concerning security For more information see the SAP Security
Guide in the SAP Library [page 12] at Administratoracutes Guide Security Guide
Landscape-relevant aspects concerning scalability high availability operation and software
life-cycle management
5 System Landscape
51 Planning Your System Landscape
3456 PUBLIC 2011-04-15
For more information about relevant aspects for the mapping of systems to hosts see the document
Technical Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
Scaling and Distribution Options
You may need to design your system landscape for a large number of users SAP NetWeaver PI offers
you different means of scalability The following list provides you with some examples
You could install multiple systems of one type and use them for different purposes
You could scale every system by installing dialog instances or by distributing the database instance
For more information about distribution options on the instance level see the Technical
Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
For every SAP system you could additionally install Web Dispatcher For more information see
the SAP Library [page 12] at FunctionndashOriented View Application Server Infrastructure SAP Web
Dispatcher
You could further distribute certain standalone engines ndash for example Search and Classification
(TREX) is based on a flexible architecture that supports a distributed installation For more
information see the Technical Infrastructure Guide ndash SAP NetWeaver PI 71 available in SAP Service
Marketplace at httpservicesapcominstallNWPI71
52 Shared Services
You normally run shared services on central systems in your system landscape The following features
could be used for SAP NetWeaver Process Integration to realize shared services
SAP Solution Manager
Used to implement train test maintain monitor control change and manage incidents of your
SAP solution system landscape (open end-to-end application management)
As of SAP Solution Manager (70) 40 Support Package 15 SAP Solution Manager has become the
platform for SAPs end-to-end solution operations strategy Functions for complete application
management has been combined with administrative tools and has been merged in newly created
role based work centers
NOTE
Be aware that you require an SAP Solution Manager system to install or upgrade to SAP
NetWeaver 70 and higher An SAP Solution Manager system is required to generate the SAP
Solution Manager key needed during the installation or upgrade process Without this key
the installation or upgrade process cannot continue
For SAP NetWeaver Process Integration you require SAP Solution Manager 70
For more information see SAP Note 805390
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3556
Solution Manager Diagnostics
An integral part of SAP Solution Manager that is running as a Java application on the Java stack of
SAP Solution Manager 70 Solution Manager Diagnostics is used to analyze the root cause of
incidents in your landscape in an efficient and safe way Before Go-Live Solution Manager
Diagnostics has to be set up and made accessible remotely
SAP NetWeaver Administrator
SAP NetWeaver Administrator is the central administration component which is used for
monitoring and administering Java applications It is included in SAP NetWeaver systems with AS
Java
SAP NetWeaver Administrator exists in the following flavors
A local mode which runs out of the box and which focuses on administrating the underlying
SAP NetWeaver AS Java
NOTE
For a SAP NetWeaver PI 71 it has a special role which you need to activate using a
configuation wizard
A central mode which has to be configured before use and which deals with the system
landscape management
SAP has decided to merge the central mode of SAP NetWeaver Administrator into the new work
centers available as of SAP Solution Manager 70 SP 15 Thus it can be used in an administrative
context together with non-Java-based administration tools Although the central mode of SAP
NetWeaver Administrator will be still available for some time SAP will not develop this tool any
further SAP focuses on optimizing the administrative work centers of SAP Solution Manager
instead
The local mode of SAP NetWeaver Administrator stays untouched It is available for current and
future releases of SAP NetWeaver
SAP Central Process Scheduling by Redwood
SAP Central Process Scheduling application by Redwood enables central job scheduling and job
monitoring of current and old releases of AS ABAP systems (as of Basis Release 31) This application
is fully integrated in SAP NetWeaver Depending on the business needs SAP business applications
are the initial trigger for scheduled activities You can now manage jobs and job chains conveniently
using a graphical user interface
System Landscape Directory
The System Landscape Directory is the central directory of system landscape information relevant
for the management of your software life-cycle It contains a description of your system landscape
(that is software components that are currently installed) and a repository of software components
that can theoretically be installed in your landscape (such as the software components available
from SAP)
Adaptive Computing Controller
5 System Landscape
52 Shared Services
3656 PUBLIC 2011-04-15
The Adaptive Computing Controller enables users to control an adaptive computing landscape
from a single point through observation operation and dynamic resource distribution With
adaptive computing hardware software and system services are able to adapt to changing business
needs In the Adaptive Computing Controller the run-time data of logical and physical landscapes
can be monitored application services can be startedstoppedrelocated and hardware resources
can be assigned to application services The operation can also be mass executed and be planned as
tasks to be executed
For more information about the installation of the Adaptive Computing Controller tool see the
document Installation Guide ndash Adaptive Computing Controller in SAP NetWeaver 71 available on SAP Service
Marketplace at httpservicesapcominstallNWPI71
For more information about Adaptive Computing in general see httpsdnsapcomirj
sdnadaptive
521 Use Cases
You can use the applications and tools described above for use cases that are normally performed
centrally The following sections describe these use cases
5211 End-to-End Solution Operations
Running business applications through their complete life-cycle is a challenge Therefore SAP has
started the Run SAP methodology for implementing End-to-End Solution Operations Based on a set
of SAP standards a roadmap and a package for training and certification Run SAP helps customers to
facilitate End-to-End Solution Operations
You can download the SAP standards for Solution Operations from SAP Service Marketplace at http
servicesapcomsupportstandards They describe roles customers typically have in their IT
environment For optimal role support SAP has grouped existing and new functions in SAP Solution
Manager work centers as of SAP Solution Manager 70 Support Package 15 Operations aspects are fully
covered by adding administrative functions for SAP NetWeaver as well Work centers are ABAP Web
Dynpro-based applications They offer the following advantages
Easy to use similar look and feel
Context transfer while jumping from one work center into another
Logical grouping of tools for a certain area
Simple authorization concept
Easy to expand
Each IT role belongs to one or more work centers For instance the Technical Administrator IT role is
covered by the work centers for System Monitoring System Administration and Landscape Management
The following work centers are available
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3756
Business Process Operations
Change Management
Root Cause Analysis
Implementation Upgrade
Incident Management
Test Management
Job Management
System Landscape Management
Solution Documentation Assistant
SAP Engagement and Service Delivery
SAP Solution Manager Administration
System Administration
System Monitoring
My Home is the central point of access to all important data of almost all work centers in SAP Solution
Manager
5212 Support Infrastructure
A key requirement for effective support of IT solutions is the ability to perform root cause analysis with
speed and efficiency
With SAP Solution Manager SAP has long had an infrastructure in place for its ABAP applications that
efficiently supports SAP solutions This helps ensure the high availability and smooth running of
business processes For more information see the SAP Solution Manager section
With Solution Manager Diagnostics this knowledge has been extended to Java applications If for
example homegrown Java applications cause instability Solution Manager Diagnostics helps trace the
cause to eradicate the problem rapidly Solution Manager Diagnostics is fully integrated into SAP
Solution Manager 70 Solution Manager Diagnostics also contains two third-party tools CArsquos Wily
Introscopereg for measuring performance as well as troubleshooting problems of the Java EE Engine
and applications running on it and Mercury Loadrunnerreg which enables SAP Support to produce a
defined load in the SAP solution landscape remotely For more information see Solution Manager
Diagnostics [page 43]
The support infrastructure provides SAP Support with safe access to your productive landscape for safe
root cause analysis so ensuring that SAP Support does not change your landscape inadvertently You
require a support infrastructure to run SAP NetWeaver
The following figure shows the overall infrastructure including SAP NetWeaver administration tools
that are used by administrators or operators at the customer site
5 System Landscape
52 Shared Services
3856 PUBLIC 2011-04-15
Landscape Aspects
If you use SAP NetWeaver Process Integration 71 productively besides SAP Solution Manager (as a
central support platform) you have to set up Solution Manager Diagnostics for supportability reasons
Implementation Sequence
For information about the implementation of the support infrastructure see the document Master
Guide ndash SAP Solution Manager 70 available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution Manager ltReleasegt
5213 Collection of Landscape Data
Amongst other applications and services the support infrastructure and the SAP NetWeaver
administration tools rely on system landscape data
For SAP NetWeaver PI 71 you have to run non-ABAP components in your solution landscape
Therefore the System Landscape Directory is mandatory The landscape data that is automatically
gathered by the System Landscape Directory is replicated to SAP Solution Manager There are several
topology options for the System Landscape Directory They offer different grades of availability
administration and operation effort
For more information see the System Landscape Directory section
5214 Authentication and Single Sign-On
Before implementing your system landscape plan how to implement authentication and how to
integrate different systems into a Single Sign-On landscape Single Sign-On reduces complexity for end
users saving them valuable time while also reducing administration effort for resetting passwords
thereby contributing to TCO reduction
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
5215 Integrated User and Access Management
In a system landscape containing a combination of ABAP and Java components we recommend that
you integrate your user and access management so that you can use the same user data across different
systems administer this data centrally and control access to data SAPs mature fine-grained
authorization concept allows detailed control of access rights SAP NetWeaver provides both ABAP and
Java-based user management solutions The user management solution that you use to administer
your user data depends on factors such as the type of systems that are running in your landscape
If you want to use central user administration we recommend that you run it in a non-production
system If you do not have a central user administration yet you can for example realize it in the SAP
Solution Manager system
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3956
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
522 Examples for the Overall System Landscape of Shared Services
In this section we provide examples of how shared services can be set up depending on the system
landscape they are intended for The following examples aggregate the landscape aspects given in the
Use Cases section
NOTE
The following sections and the figure mostly do not show information about the life-cycle of
shared services For example you may also need a development and testquality assurance system
for SAP Solution Manager You should consider this aspect in addition to the information given
in this section based on your requirements
Small and MediumndashSized Customer Landscapes with Java
As you use Java productively for SAP NetWeaver PI 71 besides SAP Solution Manager you have to set
up additional components for optimal monitoring administration and support Solution Manager
Diagnostics and the central mode of SAP NetWeaver Administrator are already fully integrated into
SAP Solution Manager 70 as the central operations hub For SAP Process Integration you must also
set up SAP NetWeaver Administrator with a special role
We recommend that you do not install SAP Central Process Scheduling in the SAP Solution Manager
system You have to set up and operate the system which hosts your productive scheduler as a mission
critical system
In the SAP Solution Manager system you should set up a local System Landscape Directory in addition
to a central runtime System Landscape Directory This way you have a clear separation between your
management system (SAP Solution Manager) and managed systems in your landscape In addition
SAP Solution Manager then does not rely on a System Landscape Directory running in the production
environment For this setup configure the SLD data suppliers of your SAP Solution Manager system
to send data to the central runtime System Landscape Directory In addition configure automatic
bridge forwarding from your runtime System Landscape Directory to the local System Landscape
Directory For more information see the Planning Guide - System Landscape Directory
If you want to use a central system for Adobe Document Services we recommend that you install a
dedicated system for this purpose in your production environment For detailed information about
the sizing of the system for the different use cases see the Sizing Guide for Adobe Document Services at
SAP Service Marketplace at httpservicesapcomsizing Sizing Guidelines Solutions amp
Platform
We recommend that you start with this centralized SAP Solution Manager approach as depicted in the
following figure
5 System Landscape
52 Shared Services
4056 PUBLIC 2011-04-15
Figure 7 Single SAP Solution Manager Landscape
Large Customer Landscapes with Java
Large customers who have environments in their landscape that are large and distributed administered
by different groups or separated for security reasons can consider a distributed operations setup In
addition to the centralized setup described for small- and medium-sized customers above large
customers can put parts of the central management functions on extra hosts or systems for performance
or policy reasons You have the following options for a distributed setup
You may set up an extra system or client for Central User Administration (CUA)
The Change and Transport System (CTS) can run on an extra system However it is not
performance- or data-intensive
You may set up an extra system for central CCMS monitoring Depending on the customizing
and on the landscape size central CCMS may generate a lot of system load You can connect a
separate central CCMS to SAP Solution Manager for displaying alerts in the alert inbox of the System
Monitoring work center
You can use a separate SAP NetWeaver 70 system with usage type BI together with SAP Solution
Manager This may make sense with respect to the amount of landscape management data that is
stored for reporting purposes The amount of data strongly depends on the data granularity
storage time frame and landscape size
You can easily put Wily Introscope Enterprise Manager on an separate host
Other aspects described above for small- and medium-customers (such as the setup of the System
Landscape Directory) are also valid for large customers
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4156
523 Feature Details
This section provides further information about the features described above
5231 SAP Solution Manager
SAP provides you with SAP Solution Manager as the strategic application management platform and
to enable the collaboration between you and SAP You need to install at least one productive SAP
Solution Manager in your system landscape To ensure the availability of this application management
platform an SAP Solution Manager system is technically required to install or upgrade to SAP
NetWeaver 70 or higher If you are already using SAP Solution Manager you can also use it to manage
the solution you build with SAP NetWeaver In this case we highly recommend that you update SAP
Solution Manager to the latest version
As of SAP Solution Manager 70 SP15 you can use the newly created work centers
NOTE
During the SAP system installation or upgrade process you are prompted to enter the SAP
Solution Manager key An SAP Solution Manager system is required to generate this key Without
this key the installation or upgrade process cannot continue
You may generate all needed keys for your entire system landscape (development quality
assurance and production system) in one SAP Solution Manager system In case you plan to install
several solution landscapes (for example in different countries) one SAP Solution Manager
system is still sufficient
For more information see SAP Note 805390
It is possible to install multiple SAP Solution Managers If you do so they should host separate business
solutions
If you want to reduce the risk of unavailability you should not install SAP Solution Manager as a central
component Instead you can operate a 2-system-landscape with both a test and production
environment of SAP Solution Manager (especially if you are using time-critical functions like Support
Desk) If you also develop your own content a 3-system-landscape with a development test and
production environment is recommended
For more information about SAP Solution Manager see the following table
Topic Where to Find More Information
System infrastructure scenarios installation and configuration of SAP Solution Manager
Master Guide ndash SAP Solution Manager available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution ManagerltReleasegt
Benefits and usage scenarios SAP Solution Manager ndash Learning Maps available on SAP Service Marketplace at http
5 System Landscape
52 Shared Services
4256 PUBLIC 2011-04-15
Topic Where to Find More Informationservicesapcomrkt-solman or https
servicesapcomsolutionmanager
Additional information See SAP Service Marketplace at http
servicesapcomsolutionmanager
5232 Solution Manager Diagnostics
Solution Manager Diagnostics provides efficient and safe root-cause analysis of incidents in customer
solutions powered by SAP NetWeaver It can help monitor on operating systems databases Java
application activities performance and logs It also supports the reporting of software and
configuration changes that can lead to malfunctions and errors
You must run one Solution Manager Diagnostics within your SAP solution landscape if you run
applications based on SAP NetWeaver systems with usage type AS Java Agents are responsible for
delivering the data from all productive hosts within your system landscape to the Solution Manager
Diagnostics system
CAUTION
SAP Support performs root-cause analysis on incoming incidents with Solution Manager
Diagnostics Not installing and configuring this support infrastructure results in a dramatically
reduced service level
Solution Manager Diagnostics is fully integrated into SAP Solution Manager 70
Solution Manager Diagnostics also contains Wily Introscope (Display Server and Agent part) for
measuring performance as well as to troubleshoot problems of Non-ABAP applications Wily Introscope
is heavily used for troubleshooting applications running on AS Java
SAP has signed a distribution agreement for Wily Introscope SAP customers are allowed to use this
tool in a preconfigured way
For more information about Solution Manager Diagnostics and an FAQ list see SAP Service Marketplace
at httpservicesapcomdiagnostics
5233 System Landscape Directory
The System Landscape Directory (SLD) of SAP NetWeaver is the central directory of system landscape
information relevant for the management of your software life-cycle
NOTE
Note that the abbreviation SLD is not intended to define a product since the System Landscape
Directory is part of SAP NetWeaver This abbreviation is solely intended to improve readability
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4356
The System Landscape Directory contains a description of your system landscape (that is software
components that are currently installed) and a repository of software components that can
theoretically be installed in your landscape (such as the software components available from SAP)
Since this data gets updated automatically the System Landscape Directory provides reliable and up-
to-date system landscape information with as little effort for you as possible In this way the System
Landscape Directory acts as a central information provider for SAP and third-party tools that use this
data to deliver the services you need to keep your landscape up and running
For the System Landscape Directory as part of an SAP NetWeaver PI 71 landscape consider the following
aspects
Part of SAP NetWeaver PI 71 is a new version of the System Landscape Directory It is automatically
included in every SAP NetWeaver 71 system with usage type AS Java It offers enhanced functions
such as a full automatic synchronization mechanism for all data stored in it That is both data
delivered by data suppliers and data entered or changed manually in the System Landscape
Directory can be synchronized automatically This synchronization offers the following
A fully automated mechanism so no user interaction is required and conflicts are resolved
automatically
Asynchronous propagation of information so some nodes may be down temporarily
Communication over HTTP protocol
Uni- and bi-directional synchronization
Depending on your use case the full automatic synchronization could significantly reduce manual
synchronization effort
For SAP NetWeaver PI 71 the configuration of the system landscape directory and its data suppliers
is already included in the standard implementation procedure with SAPinst For existing systems
you only have to perform some quick and easy configuration actions to start operating the system
landscape directory server in an AS Java system
For SAP NetWeaver PI 71 you have the following options concerning SLD
Option 1
Run SAP NetWeaver PI 71 against an existing SLD running on SAP NetWeaver 70 We only
recommend this for upgrades from SAP NetWeaver 70 if you have a central SLD in operation
not running on one of your PI systems
Option 2
Use the SLD included in an SAP NetWeaver PI 71 system We recommend this option for new
installations and upgrades from older releases than SAP NetWeaver 70 due to the enhanced
functions and improved performance of SLD 71
NOTE
If you already have a central SLD running on SAP NetWeaver 70 in operation you could run
two SLD versions in parallel ndash SLD running on SAP NetWeaver 71 for your PI systems and
SLD running on SAP NetWeaver 70 for all other systemsuse cases This way your SAP
5 System Landscape
52 Shared Services
4456 PUBLIC 2011-04-15
NetWeaver PI 71 systems would benefit from the new features while it would be easy to set
up and operate such an SLD landscape For this purpose you could use the new fully
automatic synchronization This feature enables the automatic forwarding of all SLD data
from an SLD running on SAP NetWeaver 70 to an SLD running on SAP NetWeaver 71 As a
result there is no need to adapt most existing systems as their SLD data suppliers could still
send their data to the central SLD In brief the following steps would be required
1 Put SLD in a PI system into operation (part of standard implementation procedure)
2 Configure PI systems to use the new SLD (part of standard implementation procedure
for new PI systems)
3 Set up the fully automatic synchronization from your old SLD to your new SLD
As soon as an upgrade or an installation of a standalone AS Java 71 system is available you
could move your central SLD also to SAP NetWeaver 71 Then you could optionally shift
your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems
Figure 8
We recommend that you use a Domain Name System (DNS) alias so that you are able to switch to
another System Landscape Directory easily For example if customers build a new landscape they
normally start with a sandbox environment Over time more and more environments are set up
Once the production environment is in place move the System Landscape Directory there To do
this you can configure a new System Landscape Directory in the production environment
synchronize it with the old System Landscape directory and switch to the new one
Topology
Apart from the considerations above the System Landscape Directory offers several topology options
with different grades of availability at the expense of low administration and operation effort There is
no generic rule therefore on how to set up a System Landscape Directory in your system landscape
To find the topology and synchronization strategy for the System Landscape Directory that fits your
requirements concerning the System Landscape Directory availability (and hence the availability of
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4556
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
3 SAP NetWeaver PI Overview
Introduction
SAP NetWeaver PI 71 is part of the SAP NetWeaver technology platform The complete offering of the
SAP NetWeaver technology platform is visualized in the SAP NetWeaver technology map which you
can access at httpsdnsapcomnetweaver SAP NetWeaver at a Glance The technology map
enables you to drill down from top-level technology areas (for example Lifecycle Management) to
individual capabilities (for example Administration Monitoring and so on)
SAP NetWeaver PI includes the following capabilities
Repository-based Modeling and Design
Service Bus-based Integration
SOA Management
A different view is introduced by the end-to-end use case concept This concept offers an
implementation view on SAP NetWeaver to structure and facilitate your implementation
A use cases is a process that typically involves several SAP NetWeaver capabilities It is not limited to a
single component or capability A use case guides you through the different phases of your
implementation project ndash from information through installation to the configuration phase This
implies that a uses case addresses several user roles administrator power user and end user
This document describes the SOA-based integration use case
Architecture Principals
The architecture of SAP NetWeaver Process Integration 71 (SAP NetWeaver PI 71) is based on an
established architecture for realizing cross-system business processes and is a further development of
lower releases (SAP NetWeaver 70 usage type Process Integration and SAP XI 30 as part of SAP
NetWeaver 2004) SAP NetWeaver PI 71 plays an important role in supporting an service-oriented
architecture (SOA) The focus is on the service-based integration of applications
SAP NetWeaver PI is based on general standards so as to enable 3rd-party systems to be integrated At
the center of SAP NetWeaver PI is an XML-based communication that uses HTTP (Hyper Text Transfer
Protocol) Irrespective of the scenario used the application-specific contents are transferred in messages
in user-defined XML (eXtensible Markup Language) from the sender to the receiver either via the
Integration Server or directly between the systems involved
The following figure gives an overview of the key capabilities of SAP NetWeaver Process Integration
3 SAP NetWeaver PI Overview
2011-04-15 PUBLIC 1356
Figure 1 SAP NetWeaver PI Key Capabilities Overview
SAP NetWeaver Process Integration 71 enables the integration of the applications of the following
communication parties
B2B Party Any business partners that want to integrate their application with other applications
outside their own system landscape Scenarios that require industry standards are supported as
well as any scenarios that do not adhere to a particular industry standard
SAP Applications that run on SAP systems This includes the processing of events by using the
Business Activity Monitoring (BAM) infrastructure
3rd-Party Application Applications from 3rd-party providers within one system landscape for
example database or file-system-based
3rd-Party Middleware Middleware systems from 3rd-party providers that are required for the
integration of applications within a company and across company boundaries
SAP NetWeaver PI also supports internal company scenarios and cross-company scenarios It enables
you to connect systems from different vendors (non-SAP and SAP) in different versions and
implemented in different programming languages (Java ABAP and so on) to each other Like the rest
of the SAP NetWeaver platform SAP NetWeaver PI is based on an open architecture uses open standards
(in particular those from the XML and Java environments) and offers those services that are essential
in a heterogeneous and complex system landscape
To enable end-to-end SOA development SAP NetWeaver Process Integration 71 offers a Universal
Description Discovery and Integration (UDDI) v3-based Services Registry where providers can publish
service endpoints definitions and associated metadata and consumers can discover the appropriate
services for their scenarios The Services Registry provides capabilities for classifying and browsing
3 SAP NetWeaver PI Overview
1456 PUBLIC 2011-04-15
services using semantic-rich classification systems The Services Registry is part of Application Server
Java (AS Java)
31 Installable Software Units
SAP NetWeaver comprises the following three types of installable software units
Systems that are configured for a specific purpose as indicated by one or more usage types
Standalone engines that provide one specific (server) function in combination with one or more
SAP NetWeaver PI systems
Clients used by (many) people from their local front-end PC to access functions offered by systems
of SAP NetWeaver PI or standalone engines in the system landscape
In the following sections you can find more details about the software units The figure below provides
and overview of the software units
Figure 2 Installable Software Units for SAP NetWeaver PI
For this and other figures in this guide the following legend applies
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1556
Figure 3 Legend
311 Systems with Usage Types
SAP systems are the main building blocks of SAP NetWeaver They are identified by unique SAP system
IDs (SAPSIDs) and configured for a certain purpose as indicated by usage types Usage types have the
following characteristics
They are a structuring element for SAP software on a technical level
Usage Types determine the intended purpose of a system and the role it plays in a given (distributed)
use case
They are realized by installing and configuring a collection of software components
They allow a logical view of the technology platform SAP NetWeaver PI
A usage type may require other usage types in the same system to operate
They can also be run in the same system together with other usage types that are not a prerequisite
How SAP NetWeaver Systems are Used
The following sections describe the usage types and their dependencies for SAP NetWeaver PI
Application Server ABAP (AS ABAP)
Purpose
AS ABAP is used to provide the ABAP foundation of SAP NetWeaver PI
Application Server ABAP provides a complete development and runtime environment for ABAP-based
applications It is optimized for the development of highly scalable business applications The ABAP
development and runtime environment makes it possible to develop complex business applications
3 SAP NetWeaver PI Overview
31 Installable Software Units
1656 PUBLIC 2011-04-15
without having to worry explicitly about technical details such as process or memory administration
multi-user capability database connections or similar issues These are provided in the basis services or
are integrated directly in the ABAP runtime The application development is similarly independent of
the underlying platform The application server decouples the application coding completely from the
operating system and database that are used
Dependencies
AS ABAP can be combined optionally with other usage types in one system
Application Server Java (AS Java)
Purpose
AS Java is used to provide the Java foundation of SAP NetWeaver PI using the Java Engine a Java EE-
compliant application server for running enterprise applications In addition to the pure Java EE
standard technologies the Java Engine implements complementary technologies such as Web Dynpro
or Web Services that are targeted at supporting large-scale real-business application development
projects
Dependencies
AS Java can be combined optionally with other usage types in one system
Process Integration (PI)
Purpose
PI consists of core components that model design automate and integrate processes in one or more
application systems For the integration of internal and cross-company processes PI is used to
incorporate all the functions of what was formerly known as Exchange Infrastructure (XI) In addition
PI contains core components for Business Process Management for application-embedded and
application-unbounded processes
The Advanced Adapter Engine is also part of usage type PI You use Advanced Adapter Engine to connect
to SAP systems (RFC adapter) and external systems You use the various adapters in Advanced Adapter
Engine to convert XML- and HTTP-based messages to the specific protocol and format required by
these systems and the other way around You can use the Advanced Adapter Engine that is part of
your PI system as a central Advanced Adapter Engine Optionally (for performance reasons) you can
install a non-central Advanced Adapter Engine [page 19] separately as a system with AS Java and parts of the
usage type PI on a separate host
Dependencies
PI requires AS ABAP and AS Java as prerequisites in the same system
For installing PI it is mandatory to have a dedicated PI system This applies to development quality
and production landscapes It is a prerequisite that no other system in your system landscape has a
higher release and enhancement package level than the PI system If you want to upgrade or install an
application in your system landscape you first have to make sure that the current release and
enhancement package level of the PI system is on the same level - if required you have to upgrade the
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1756
PI system first to the new or a higher release In a dedicated PI system this can be accomplished with a
minimum of downtime Also the PI system would not be affected by the downtime of other usage
types running in the same system
Configuration of Systems with Usage Types
Configuration information is available in the installation guides the configuration wizard and SAP
Solution Manager
In the Installation Guide ndash SAP NetWeaver PI 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt you find
initial technical configuration tasks This guide also informs you about how you can run the
configuration wizard and how you can access the configuration information in SAP Solution
Manager
For certain usage types configuration tasks can be applied by the configuration wizard after the
installation To do this you start the configuration wizard from SAP NetWeaver Administrator
The configuration steps for systems with usage types required for an use case are accessible through
SAP Solution Manager
To be able to use SAP Solution Manager for the configuration tasks you have to import the latest
SAP Solution Manager Implementation Content (Add-On ST-ICO) that is available for your SAP
Solution Manager release For more information see SAP Note 631042 (Release strategy for Implementation
Content (ST-ICO))
SAP Solution Manager Implementation Content is available on SAP Service Marketplace at
httpservicesapcomswdc Installations amp Upgrades Entry by Application Component SAP
Technology Components SAP Solution Manager ltReleasegt Content ST-ICO
In SAP Solution Manager you create a project and a project structure In the configuration phase
you select configuration structures with pre-delivered SAP content for your project You can find
the following different types of configuration tasks in SAP Solution Manager
Mandatory configuration tasks All configuration tasks that are mandatory for the standalone
engine or usage type
Optional configuration tasks Configuration tasks for areas where customers need to decide
if they want to use these functions (for example high availability or security settings)
Additional functions ndash configuration tasks Configuration tasks for functional units that are
used in certain use cases only
A marked checkbox in front of the configuration tasks indicates those configuration tasks that are
relevant for the use case you have chosen To configure ABAP systems SAP Solution Manager
offers executable configuration files (IMG activities)
For information about using SAP Solution Manager Content and creating a configuration guide
see the following documentation
httphelpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Implementing
and Upgrading SAP Solutions Configuration
3 SAP NetWeaver PI Overview
31 Installable Software Units
1856 PUBLIC 2011-04-15
How to Create a Configuration Guide using SAP Solution Manager available at http
servicesapcomsolutionmanager Media Library How-To Documents
Restrictions for Systems with Multiple Usage Types
If you have one system with multiple usage types be aware that we do not provide standard tools
to separate these usage types and distribute them to multiple systems at a later stage For example
if you have a system with usage types A and B you are not able to migrate it with SAP standard
tools into two systems one with usage type A only and the other with usage type B only
In addition we do not provide standard tools to merge multiple systems with different usage types
into one system with multiple usage types at a later stage
If you want to perform these tasks you require specific project support
The following figure shows that SAP standard system copy and migration tools do not support
you in separating or merging systems with usage types
Figure 4 No Support for Merging or Separating Systems with Usage Types
Although you can use one system for multiple usage types client restrictions apply for usage type
PI PI requires a dedicated client due to special PI requirements concerning the client pipeline
Whereas application client pipelines only send and receive messages the central PI pipeline can
also map messages to different formats before sending them
312 Standalone Engines
Standalone engines of SAP NetWeaver are additional installable software units They do not work as
full-blown systems of SAP NetWeaver but as standalone engines that provide a specific (server) function
in combination with one or more SAP NetWeaver systems
Standalone engines are not part of a usage type They do not run on AS ABAP or AS Java
The standalone engines that are available for SAP NetWeaver Process Integration are described in the
following
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1956
Gateway
It is possible to install an SAP instance of an SAP NetWeaver system based exclusively on a standalone
gateway This type of instance does not contain normal work process types (dialog background update
enqueue or spool) Only the gateway process (gwrd) is started If there is an SNA connection to an R
2 system gateway work processes (gwwp) are also started
SAP Conversion Agent by Informatica
SAP Conversion Agent by Informatica is a data conversion tool that enables you to create interfaces
between any data formats and XML-based systems SAP Conversion Agent can convert unstructured
semi-structured and structured formats to XML and the other way around The Conversion Agent
comprises the Conversion Agent Studio and the Conversion Agent Engine In the Conversion Agent
Studio you can develop and configure data conversions The Conversion Agent Engine executes the
data conversions
Search and Classification (TREX)
You can use Search and Classification with SAP NetWeaver PI to search for messages that were previously
indexed Message search using index provides additional methods of searching for specific messages In
addition to static header attributes you can also use adapter-specific message attributes and data from
the message payload for the search A requirement of this however is that the messages are indexed
first You can apply the index-based message search to one or all indexed components of an integration
landscape (domain) Integration Server Adapter Engines and ABAP business systems
For more information see the SAP Library [page 12] at Administratorrsquos Guide Technical Operations for SAP
NetWeaver Administration of SAP NetWeaver Systems Administering PI (Process Integration) Monitoring Index
Administration
Web Dispatcher
The Web Dispatcher lies between the Internet and your SAP system It is the entry point for HTTP(s)
requests into your system which consists of one or more SAP NetWeaver application servers As a
software web switch the Web dispatcher can reject connections or accept them When it accepts a
connection it balances the load to ensure an even distribution across the servers
You can use the Web dispatcher in ABAPJava systems and in pure Java systems as well as in pure ABAP
systems
It is also beneficial to use the Web Dispatcher if you do not need security functions (entry point in the
demilitarized zone (DMZ) SSL URL filtering) but you simply want to balance the load between
multiple SAP NetWeaver Application Server instances
Since Web Dispatcher is optional for every SAP system it is not contained in the system landscape and
the implementation sequence of the use case in this documentation
For more information see the SAP Library [page 12] at Function Oriented View Application Server Infrastructure
SAP Web Dispatcher
3 SAP NetWeaver PI Overview
31 Installable Software Units
2056 PUBLIC 2011-04-15
Advanced Adapter Engine
You use the Advanced Adapter Engine to connect to SAP systems (RFC adapter) and external systems
You use the various adapters in Advanced Adapter Engine to convert XML- and HTTP-based messages
to the specific protocol and format required by these systems and the other way around For specific
senderreceiver combinations messages can be processed without invoking the central Integration
Engine In principle you connect external systems using the adapters that are installed centrally or
non-centrally in Advanced Adapter Engine You can use the Advanced Adapter Engine that is part of
your PI system as a central Advanced Adapter Engine Optionally (for performance reasons) you can
install a non-central Advanced Adapter Engine separately as a system with AS Java and parts of the
usage type PI on a separate host
Adapter Engine (Java SE)
Adapter Engine (Java SE) is a separate software unit You can use it only if you have SAP NetWeaver
systems with usage type PI in your system landscape It has to be installed manually You use the Adapter
Engine (Java SE) to connect to external systems Using the various adapters in the Adapter Engine (Java
SE) XML and HTTP-based messages can be converted to the specific protocol and format required by
such systems and the other way around The Adapter Engine (Java SE) only provides some of these
adapters as a standalone version with restricted functions for operating systems that do not support
SAP NetWeaver PI 71 but that have at least a Java Runtime Environment 50 Therefore you should
use the Adapter Engine (Java SE) only if the platform prerequisites do not allow you to use the Advanced
Adapter Engine
SAP Partner Connectivity Kit
SAP Partner Connectivity Kit (PCK) runs on AS Java with parts of the usage type PI It enables a system
of a smaller company or subsidiary that does not run SAP NetWeaver PI to connect to your SAP
NetWeaver systems
313 Clients
Clients are additional installable programs or tools They reside either on local front-end PCs accessed
by users or on back-end systems where they act as client programs within an SAP NetWeaver system
landscape
The clients that you can use with SAP NetWeaver Process Integration are described in the following
sections
SAP GUI
NOTE
We recommend that you use the following versionsI
SAP GUI for Windows 710 (or higher) with the latest patch level
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 2156
SAP GUI for Java 710 (or higher) with the latest revision
The integrated SAP ITS 710
For more information about the SAP GUI family see SAP Service Marketplace at http
servicesapcomsapgui
SAP offers three different client applications for accessing ABAP applications in SAP systems (such as
SAP NetWeaver systems with usage type AS ABAP) This SAP GUI family consists of
SAP GUI for HTML
SAP GUI for HTML is based on the SAP integrated Internet Transaction Server (ITS) which is
included in the installation of SAP NetWeaver systems as of SAP NetWeaver 2004 On the client
side only a suitable browser (such as Internet Explorer 70 or Firefox 20) and a virtual machine are
required SAP ITS 620 is not compatible with SAP NetWeaver 71
SAP GUI for the Java environment (SAP GUI for Java)
SAP GUI for Java is a generic SAP GUI that covers a variety of platforms
For more information about the installation of SAP GUI for Java see the documentation Installation
Guide ndash SAP Front End
SAP GUI for the Windows environment (SAP GUI for Windows)
SAP GUI for Windows is SAPs universal client for accessing all SAP applications built on ABAP
technology It is available on the Microsoft Windows platform only and offers the broadest feature
set of all members of the SAP GUI family
For more information about the installation of SAP GUI for Windows see the Installation Guide ndash
SAP Front End
SAP NetWeaver Developer Studio
The SAP NetWeaver Developer Studio is SAPrsquos Integrated Development Environment (IDE) for Java
and is based on the open-source tools framework Eclipse 33 With the SAP NetWeaver Developer Studio
you can develop Java EE 5 applications from scratch using the built-in support for new technologies
such as EJB 30 and JSF 12
During the installation of the SAP NetWeaver Developer Studio several features are offered for
installation For SAP NetWeaver PI 71 only the following features are relevant
SAP NetWeaver Developer Studio Platform
SAP NetWeaver Developer Studio Java EE
NOTE
If you want to use one of the other features you need SAP NetWeaver Composition Environment
and a corresponding developers licence
For more information about the installation of SAP NetWeaver Developer Studio see the Installation
Guide ndash SAP NetWeaver Developer Studio 71 or Installation Guide ndash SAP NetWeaver Developer Studio 71 Including
Enhancement Package 1
3 SAP NetWeaver PI Overview
31 Installable Software Units
2256 PUBLIC 2011-04-15
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
SAP enhancement packages are a new way of delivering new functions for SAP NetWeaver This allows
a clear separation between the delivery of new functions on the one hand and corrections legal changes
and security updates on the other hand (in Support Package stacks) SAP enhancement packages are
cumulative an enhancement package always contains the functions of the corresponding predecessor
enhancement packages
Enhancement packages are maintained by their own Support Packages while the main release is in
maintenance
Benefits
SAP enhancement packages offer the following benefits
You have reduced effort for testing and no effort for training when applying Support Packages as
new features are only shipped with enhancement packages
Adding new functions between releases becomes predictable and controllable
New functions can be added successively in small steps There is no need to fully upgrade your
system to get new functions
You have minimal training effort when applying an enhancement package because existing
functions are not replaced
Implementation
There are the following ways to get an SAP NetWeaver system with the release level of SAP enhancement
package 1 for SAP NetWeaver Process Integration 71
New installation of SAP NetWeaver PI 71 including enhancement package 1 using the standard
installation tool SAPinst
Upgrade of an existing SAP NetWeaver system from a release lower than SAP NetWeaver PI 71 to
SAP NetWeaver PI 71 including enhancement package 1 For this you use the upgrade programs
SAPup (for ABAP) and SAPJup (for Java)
Installation of the enhancement package on an existing SAP NetWeaver PI 71 system
For this you use the Software Update Manager (SUM) The Software Update Manager evolved
from the previously used SAP Enhancement Package Installer The tool has been renamed to reflect
its broader use for example you can also use it for applying Support Package Stacks to your system
On the ABAP side the Software Update Manager uses a system cloning and switch procedure for
installing enhancement packages It installs a copy of the system the shadow system parallel to
the original system This shadow system is used to update the relevant software components and
to install the additional components while the original system is still in production operation At
a certain point during downtime the switch to the new system is made and afterwards any parts
of the original system that are no longer needed are deleted The enhancement package installation
in a Java system uses a deploy-based procedure that is no shadow system is used The Software
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2011-04-15 PUBLIC 2356
Update Manager requires a stack configuration file (xml file) as input file for the enhancement
package installation procedure This file lists all the packages that are to be installed in your systems
The stack configuration file is generated when you download the required packages
As the Software Update Manager is updated regularly we recommend to always use the latest
version It is delivered as part of the SL toolset For more information see http
servicesapcomsltoolset
For an overview of all required steps for the enhancement package installation process and
corresponding documents see Process Overview Installation of Enhancement Package 1 on an Existing SAP
Netweaver PI 71 System [page 28]
Content of SAP Enhancement Package 1 for SAP NetWeaver PI 71
With enhancement package 1 for SAP NetWeaver PI 71 new features are introduced and some existing
are changed The following is a selection of some of the most important enhancements
Enhanced design and modelling options in the Enterprise Services Repository
New services registry
Support for new Web services standard (Web Services Reliable Messaging)
New modules for the Advanced Adapter Engine
Use of shared memory of the ABAP Application Server for message processing
For more information about the changes see SAP Library [page 12] at Whatacutes new in SAP NetWeaver PI 71
ndash Release Notes
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2456 PUBLIC 2011-04-15
4 SOA-Based Integration Use Case
41 Overview
You can use SOA-based integration to set up the communication between service providers and service
consumers in both application-to-application and business-to-business scenarios and to execute
operate and monitor the communication at runtime SOA-based integration covers both direct (point-
to-point) as well as mediated (via an Integration Server) communication between service providers and
service consumers
The use case spans the whole life cycle of a SOA-based integration scenario including
Scenario modeling and service design in the Enterprise Services Repository
Implementation of the service provider and consumer in the back-end systems
Configuration and finally execution monitoring and operation of the integration scenario
For scenarios using Integration Server or broker-based communication the configuration of the
different connectivity options (for example SOAP RFC Web Services Industry standards and JDBC)
and their enhancements is covered
For more information see the following documents
Service-Enabling with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdnsoa-modeling
Getting Started
Service-Enabling a Legacy Application with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdn
soa-servicebus Getting Started
In the following you will find information about the installation of the involved software units
42 System Landscape
The following figure shows the system landscape for this use case
4 SOA-Based Integration Use Case
41 Overview
2011-04-15 PUBLIC 2556
Figure 5 SOA-Based Integration
It is mandatory to have a dedicated PI system This applies to development quality and production
landscapes
For PI it is a prerequisite that no other system in your system landscape has a higher release than
the PI system For exceptions to this rule see SAP Note 1043047 For example SAP XI 30 is compatible
with SAP NetWeaver 640 and 70 application systems since the same XI protocol is used Apart
from these exceptions if you want to upgrade or install an application in your system landscape
you first have to make sure that the PI system is on the same release level If required you have to
upgrade the PI system first to the new or a higher release
CAUTION
Although it should be technically possible to run an application system with a higher release
than your PI system in your system landscape this is not supported by SAP (apart from the
exceptions listed in SAP Note 1043047) Therefore you run such a landscape at your own risk
You can use the Advanced Adapter Engine that is part of your PI system as a central Advanced
Adapter Engine
Adapter Engine (Java SE) can be installed in a non-SAP Java environment However it only hosts
a subset of the adapter functionality is only supported for compatibility reasons and should be
used only if this is a precondition in your environment
Optionally you can use the Change Management Service (CMS) of an SAP NetWeaver 70 system
with usage type DI to transport design objects and repository objects For more information see
the SAP Library [page 12] at Administratoracutes Guide Technical Operations for SAP NetWeaver Administration
of SAP NetWeaver Systems PI (Process Integration) Software Logistics Transporting ESR Content and Objects
of Integration Directory PI Transports Using the Change Management Service (CMS)
Smaller business partners or subsidiaries that do not run SAP NetWeaver install SAP Partner
Connectivity Kit in their system landscape SAP Partner Connectivity Kit enables XML document
4 SOA-Based Integration Use Case
42 System Landscape
2656 PUBLIC 2011-04-15
exchange between your SAP NetWeaver systems and the partner systems Since SAP Partner
Connectivity Kit gets installed in their system landscape it is not shown in the system landscape
figure above
The AS ABAP system acts as an application and service provider For Java Web Services you also
require AS Java In addition you require SAP NetWeaver Developer Studio on the client side as a
development environment
The Web service client can be either an SAP or a non-SAP application For example an AS ABAP
system or a Web browser could act as application or service consumer
You can install SAP Conversion Agent by Informatica in the system with usage type PI or on a host
where SAP Partner Connectivity Kit is installed or on a host where neither usage type PI nor SAP
Partner Connectivity Kit is installed
43 Implementation Sequence
Procedure
To install this use case perform the steps listed in the following table
StepAction[Corresponding Documentation] Remarks
1 Make sure that you have performed the preparation steps You have planned your system landscape [page 33]
(that is you have decided how many systems you require how you want to use each of these systems and which standalone engines and clients you require)
With the help of your hardware partner you have mapped your systems and standalone engines to properly sized hosts
You have planned and installed shared services [page 35]
2 Installation of system with usage type PI (includes the installation of AS ABAP and AS Java)
NOTE
For usage type PI a Unicode installation is mandatory
[Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt]
If you want to use the features of enhancement package 1 use the direct installation of SAP NetWeaver PI 71 including enhancement package 1
Make sure that you perform the configuration steps as described in the installation guide For certain usage types configuration tasks can be applied by the configuration wizard These configuration tasks as well as any additional configuration steps for your use case are listed in SAP Solution Manager For more information
4 SOA-Based Integration Use Case
43 Implementation Sequence
2011-04-15 PUBLIC 2756
StepAction[Corresponding Documentation] Remarks
see the Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt
3 Install the Adapter Engine (Java SE) engines if required[Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
4 To integrate small business partners and subsidiaries the business partners or subsidiaries install SAP Partner Connectivity Kit running on AS Java with parts of usage type PI in the business partners or subsidiarys system landscape[Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
5 Install SAP Conversion Agent by Informatica if required[SAP Library [page 12] at Function-Oriented View Process Integration SAP Conversion Agent by Informatica Deploying and Using Conversion Agent ]
6 Installation of clients SAP GUI
[Installation Guide ndash SAP Front End]
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
The process sequences give a comprehensive overview of the steps relevant for the enhancement
package installation on an existing SAP NetWeaver PI 71 system
The process sequence is divided into a planning phase and an implementation phase Each step in both
phases contains references to the corresponding documentation to ensure that you can easily find the
information you need
Process
NOTE
To download the enhancement package files and required Support Packages you require the SAP
Solution Manager Maintenance Optimizer You have the following options
Manual Selection
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2856 PUBLIC 2011-04-15
You manually select the required files from SAP Service Marketplace at http
servicesapcomswdc using the SP Stack Application You use the Maintenance Optimize
only to approve the packages which is a prerequisite for the download
Automatic Calculation
The Maintenance Optimizer supports the download of a consistent queue that includes all
necessary Support Packages and enhancement packages In addition SAP Solution Manager
calculates a valid import queue for the selected SAP system and generates the enhancement
package stack configuration file that you require for the installation
As a prerequisite the system that you want to update needs to be maintained correctly in
SAP Solution Manager System Landscape As the Maintenance Optimizer uses this data for
the calculation it is crucial that the data is up-to-date In addition the SAP Solution Manager
system requires a Minimum Support Package level (see below)
Planing PhaseStep Description Documentation
Hardware amp Software Prerequisites
Check which platforms are supported for your target release (OSDB dependencies)
Product Availability Matrix (PAM) at httpservicesapcompam
Check which hardware sizing is required for your target release
Sizing information at httpservicesapcomsizing
Solution Manager Prerequisites
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of the required software packages you have to make sure that your SAP Solution Manager system has the required Support Package levelAt least SAP Solution Manager 70 EHP1 Support Package Stack 17 is required We recommend to use SAP Solution Manager 70 EHP1 Support Package Stack 23Check if you need to do an update or upgrade of your SAP Solution ManagerMake sure that you run the guided procedure SOLMAN_SETUP after every installation or update of SAP Solution Manager and that it completes successfully
For upgrades from source release SAP Solution Manager 31 and 32Upgrade Guide ndash SAP Solution Manager 70 incl Enhancement Package 1For updates from SAP Solution Manager 70Update Guide SAP Enhancement Package 1 for SAP Solution Manager 70Follow-up activities after an Support Package Stack update or enhancement package updateSolution Operations Guide ndash SAP Solution Manager 70 EHP1 section Software Change Management All guides are available at http
servicesapcom instguides SAP Components SAP Solution Manager -gt Release 70 EHP 1
Implementation PhaseStep Description Documentation
1Solution Manager Preparation
Configure the SAP Solution Manager Maintenance Optimizer
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of software packages make sure your
Configuration of Maintenance Optimizer http
helpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Change Request Management and Change ControlMaintenance Optimizer
Prerequisites
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 2956
Implementation PhaseStep Description Documentation
system landscape data in SAP Solution Manager is maintained correctlyLandscape Verification 10 which is an add-on to SAP Solution Manager can support you in maintaining your system landscape data The use of this tool is optional
Landscape Verification http
wwwsdnsapcom irj
sdn alm-update-
management link Landscape Verification under Related Areas on Upgrade and Update Management (in the right column)
SAP Note 1468605 (Installation of Landscape Verification)
Maintaining System Landscape Information [page 47]Note that the information provided in this section is based on SAP Solution Manager 70 EHP1 SP23
2System Preparation
Prepare your system as described in the documentation for example perform OS DB specific preparations and the PI-specific preparations
Update Guide ndash Update of SAP Systems with Software Update Manager sections Planning and Preparation
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
3Software Download
Select and download the software packages in either of the following ways Automatic calculation Create
a maintenance transaction in the Maintenance Optimizer and choose the Calculate Files Automatically option
Manual Selection Create a maintenance transaction in the Maintenance Optimizer and choose the Select Files Manually option You then can select the files manually using the SP Stack application in SAP Service Marketplace
NOTE
You have to download the stack configuration file manually after you have selected all files in the SP Stack
httphelpsapcom SAP Solutions SAP Solution Manager
SAP Solution Manager 70 EHP1 ltSPgtChange Request Management and
Change Control Maintenance Optimizer Maintenance Procedure Scenarios
For information about the automatic calculation see Maintenance Transaction with Installation of an Enhancement PackageFor information about the manual selection and approval process see section Approve and Download Files in Download Basket
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
3056 PUBLIC 2011-04-15
Implementation PhaseStep Description Documentation
application Choose Generate Stack XML and save the file
4Enhancement Package Installation
Run Software Update Manager to update your system with the selected software packages
Update Guide ndash Update of SAP Systems with Software Update Manager
5Follow-Up Steps
Perform technical and PI-specific follow-up activities after the enhancement package installation is done
Update Guide ndash Update of SAP Systems with Software Update Manager section Follow-Up Activities
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
6Configuration
Configure newly installed enhancement package functions using SAP Solution Manager content
See Systems with Usage Types [page 16] section Configuration of Systems with Usage Types
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 3156
This page is left blank for documents that are printed on both sides
5 System Landscape
51 Planning Your System Landscape
The installable software units that make up your system landscape depend on the functions that you
want to implement For information about the features see systems [page 16] standalone engines [page 19]
and clients [page 21]
In addition you have to determine the required shared services [page 35] (such as SAP Solution Manager
or SAP NetWeaver Administrator) that run on central systems in your system landscape and the
landscape aspects relevant for their implementation
In the following you will find general information that you should consider when planning your system
landscape
Sizing
You have to map systems and standalone engines to hosts after you have a clear picture of the following
Which systems and standalone engines you require
How many systems you require and how you want to use each of these systems
NOTE
No general guideline can be given for the sizing of your landscape since this relies heavily on your
requirements You should therefore perform this task together with your hardware partner and
your technical consultant
For information about sizing your systems you can use the following information sources
Your first point of reference is the Quick Sizer
SAP built the Quick Sizer as an online sizing questionnaire Internet application in close cooperation
with its hardware partners This tool delivers general sizing categories based on your volume load
estimates The results provide an objective basis for sizing independent of platform and
configuration
For more information see SAP Service Marketplace at
httpservicesapcomsizing for the SAP NetWeaver PI 71 sizing guide available under
Sizing Guidelines Business Suite amp Services
httpservicesapcomquicksizer for more information and access to the tool itself
Also consider the following important aspects concerning sizing
High availability
5 System Landscape
51 Planning Your System Landscape
2011-04-15 PUBLIC 3356
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Technical Infrastructure High Availability
Unicode
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Internationalization
Contact your hardware partner to find out the appropriate number of sized hosts
The platform-independent abstract results of the Quick Sizer can be used by any of our hardware
partners to create a concrete offer SAP itself does not make any hardware recommendations the
responsibility for sizing and detailed hardware configuration lies with the hardware partners
Figure 6 Example of Mapping of Systems and Standalone Engines to Three Hosts
NOTE
Optionally you could also distribute single systems to multiple hosts For example you could
decide to install the database instance of an SAP system on a separate host for performance
reasons or distribute other system instances to achieve high availability
To provide a mapping that fits your required functions and performance your hardware partner
and your technical consultant have to identify the number of required instances of SAP NetWeaver
find out how to distribute these instances to hosts and what functions will run on which instance
Therefore the hardware partner and the technical consultant have to consider many different
aspects such as
Number of required SAPS (SAP Application Benchmark Performance Standard) for each
system (provided by Quick Sizer)
Landscape-relevant aspects concerning security For more information see the SAP Security
Guide in the SAP Library [page 12] at Administratoracutes Guide Security Guide
Landscape-relevant aspects concerning scalability high availability operation and software
life-cycle management
5 System Landscape
51 Planning Your System Landscape
3456 PUBLIC 2011-04-15
For more information about relevant aspects for the mapping of systems to hosts see the document
Technical Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
Scaling and Distribution Options
You may need to design your system landscape for a large number of users SAP NetWeaver PI offers
you different means of scalability The following list provides you with some examples
You could install multiple systems of one type and use them for different purposes
You could scale every system by installing dialog instances or by distributing the database instance
For more information about distribution options on the instance level see the Technical
Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
For every SAP system you could additionally install Web Dispatcher For more information see
the SAP Library [page 12] at FunctionndashOriented View Application Server Infrastructure SAP Web
Dispatcher
You could further distribute certain standalone engines ndash for example Search and Classification
(TREX) is based on a flexible architecture that supports a distributed installation For more
information see the Technical Infrastructure Guide ndash SAP NetWeaver PI 71 available in SAP Service
Marketplace at httpservicesapcominstallNWPI71
52 Shared Services
You normally run shared services on central systems in your system landscape The following features
could be used for SAP NetWeaver Process Integration to realize shared services
SAP Solution Manager
Used to implement train test maintain monitor control change and manage incidents of your
SAP solution system landscape (open end-to-end application management)
As of SAP Solution Manager (70) 40 Support Package 15 SAP Solution Manager has become the
platform for SAPs end-to-end solution operations strategy Functions for complete application
management has been combined with administrative tools and has been merged in newly created
role based work centers
NOTE
Be aware that you require an SAP Solution Manager system to install or upgrade to SAP
NetWeaver 70 and higher An SAP Solution Manager system is required to generate the SAP
Solution Manager key needed during the installation or upgrade process Without this key
the installation or upgrade process cannot continue
For SAP NetWeaver Process Integration you require SAP Solution Manager 70
For more information see SAP Note 805390
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3556
Solution Manager Diagnostics
An integral part of SAP Solution Manager that is running as a Java application on the Java stack of
SAP Solution Manager 70 Solution Manager Diagnostics is used to analyze the root cause of
incidents in your landscape in an efficient and safe way Before Go-Live Solution Manager
Diagnostics has to be set up and made accessible remotely
SAP NetWeaver Administrator
SAP NetWeaver Administrator is the central administration component which is used for
monitoring and administering Java applications It is included in SAP NetWeaver systems with AS
Java
SAP NetWeaver Administrator exists in the following flavors
A local mode which runs out of the box and which focuses on administrating the underlying
SAP NetWeaver AS Java
NOTE
For a SAP NetWeaver PI 71 it has a special role which you need to activate using a
configuation wizard
A central mode which has to be configured before use and which deals with the system
landscape management
SAP has decided to merge the central mode of SAP NetWeaver Administrator into the new work
centers available as of SAP Solution Manager 70 SP 15 Thus it can be used in an administrative
context together with non-Java-based administration tools Although the central mode of SAP
NetWeaver Administrator will be still available for some time SAP will not develop this tool any
further SAP focuses on optimizing the administrative work centers of SAP Solution Manager
instead
The local mode of SAP NetWeaver Administrator stays untouched It is available for current and
future releases of SAP NetWeaver
SAP Central Process Scheduling by Redwood
SAP Central Process Scheduling application by Redwood enables central job scheduling and job
monitoring of current and old releases of AS ABAP systems (as of Basis Release 31) This application
is fully integrated in SAP NetWeaver Depending on the business needs SAP business applications
are the initial trigger for scheduled activities You can now manage jobs and job chains conveniently
using a graphical user interface
System Landscape Directory
The System Landscape Directory is the central directory of system landscape information relevant
for the management of your software life-cycle It contains a description of your system landscape
(that is software components that are currently installed) and a repository of software components
that can theoretically be installed in your landscape (such as the software components available
from SAP)
Adaptive Computing Controller
5 System Landscape
52 Shared Services
3656 PUBLIC 2011-04-15
The Adaptive Computing Controller enables users to control an adaptive computing landscape
from a single point through observation operation and dynamic resource distribution With
adaptive computing hardware software and system services are able to adapt to changing business
needs In the Adaptive Computing Controller the run-time data of logical and physical landscapes
can be monitored application services can be startedstoppedrelocated and hardware resources
can be assigned to application services The operation can also be mass executed and be planned as
tasks to be executed
For more information about the installation of the Adaptive Computing Controller tool see the
document Installation Guide ndash Adaptive Computing Controller in SAP NetWeaver 71 available on SAP Service
Marketplace at httpservicesapcominstallNWPI71
For more information about Adaptive Computing in general see httpsdnsapcomirj
sdnadaptive
521 Use Cases
You can use the applications and tools described above for use cases that are normally performed
centrally The following sections describe these use cases
5211 End-to-End Solution Operations
Running business applications through their complete life-cycle is a challenge Therefore SAP has
started the Run SAP methodology for implementing End-to-End Solution Operations Based on a set
of SAP standards a roadmap and a package for training and certification Run SAP helps customers to
facilitate End-to-End Solution Operations
You can download the SAP standards for Solution Operations from SAP Service Marketplace at http
servicesapcomsupportstandards They describe roles customers typically have in their IT
environment For optimal role support SAP has grouped existing and new functions in SAP Solution
Manager work centers as of SAP Solution Manager 70 Support Package 15 Operations aspects are fully
covered by adding administrative functions for SAP NetWeaver as well Work centers are ABAP Web
Dynpro-based applications They offer the following advantages
Easy to use similar look and feel
Context transfer while jumping from one work center into another
Logical grouping of tools for a certain area
Simple authorization concept
Easy to expand
Each IT role belongs to one or more work centers For instance the Technical Administrator IT role is
covered by the work centers for System Monitoring System Administration and Landscape Management
The following work centers are available
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3756
Business Process Operations
Change Management
Root Cause Analysis
Implementation Upgrade
Incident Management
Test Management
Job Management
System Landscape Management
Solution Documentation Assistant
SAP Engagement and Service Delivery
SAP Solution Manager Administration
System Administration
System Monitoring
My Home is the central point of access to all important data of almost all work centers in SAP Solution
Manager
5212 Support Infrastructure
A key requirement for effective support of IT solutions is the ability to perform root cause analysis with
speed and efficiency
With SAP Solution Manager SAP has long had an infrastructure in place for its ABAP applications that
efficiently supports SAP solutions This helps ensure the high availability and smooth running of
business processes For more information see the SAP Solution Manager section
With Solution Manager Diagnostics this knowledge has been extended to Java applications If for
example homegrown Java applications cause instability Solution Manager Diagnostics helps trace the
cause to eradicate the problem rapidly Solution Manager Diagnostics is fully integrated into SAP
Solution Manager 70 Solution Manager Diagnostics also contains two third-party tools CArsquos Wily
Introscopereg for measuring performance as well as troubleshooting problems of the Java EE Engine
and applications running on it and Mercury Loadrunnerreg which enables SAP Support to produce a
defined load in the SAP solution landscape remotely For more information see Solution Manager
Diagnostics [page 43]
The support infrastructure provides SAP Support with safe access to your productive landscape for safe
root cause analysis so ensuring that SAP Support does not change your landscape inadvertently You
require a support infrastructure to run SAP NetWeaver
The following figure shows the overall infrastructure including SAP NetWeaver administration tools
that are used by administrators or operators at the customer site
5 System Landscape
52 Shared Services
3856 PUBLIC 2011-04-15
Landscape Aspects
If you use SAP NetWeaver Process Integration 71 productively besides SAP Solution Manager (as a
central support platform) you have to set up Solution Manager Diagnostics for supportability reasons
Implementation Sequence
For information about the implementation of the support infrastructure see the document Master
Guide ndash SAP Solution Manager 70 available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution Manager ltReleasegt
5213 Collection of Landscape Data
Amongst other applications and services the support infrastructure and the SAP NetWeaver
administration tools rely on system landscape data
For SAP NetWeaver PI 71 you have to run non-ABAP components in your solution landscape
Therefore the System Landscape Directory is mandatory The landscape data that is automatically
gathered by the System Landscape Directory is replicated to SAP Solution Manager There are several
topology options for the System Landscape Directory They offer different grades of availability
administration and operation effort
For more information see the System Landscape Directory section
5214 Authentication and Single Sign-On
Before implementing your system landscape plan how to implement authentication and how to
integrate different systems into a Single Sign-On landscape Single Sign-On reduces complexity for end
users saving them valuable time while also reducing administration effort for resetting passwords
thereby contributing to TCO reduction
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
5215 Integrated User and Access Management
In a system landscape containing a combination of ABAP and Java components we recommend that
you integrate your user and access management so that you can use the same user data across different
systems administer this data centrally and control access to data SAPs mature fine-grained
authorization concept allows detailed control of access rights SAP NetWeaver provides both ABAP and
Java-based user management solutions The user management solution that you use to administer
your user data depends on factors such as the type of systems that are running in your landscape
If you want to use central user administration we recommend that you run it in a non-production
system If you do not have a central user administration yet you can for example realize it in the SAP
Solution Manager system
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3956
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
522 Examples for the Overall System Landscape of Shared Services
In this section we provide examples of how shared services can be set up depending on the system
landscape they are intended for The following examples aggregate the landscape aspects given in the
Use Cases section
NOTE
The following sections and the figure mostly do not show information about the life-cycle of
shared services For example you may also need a development and testquality assurance system
for SAP Solution Manager You should consider this aspect in addition to the information given
in this section based on your requirements
Small and MediumndashSized Customer Landscapes with Java
As you use Java productively for SAP NetWeaver PI 71 besides SAP Solution Manager you have to set
up additional components for optimal monitoring administration and support Solution Manager
Diagnostics and the central mode of SAP NetWeaver Administrator are already fully integrated into
SAP Solution Manager 70 as the central operations hub For SAP Process Integration you must also
set up SAP NetWeaver Administrator with a special role
We recommend that you do not install SAP Central Process Scheduling in the SAP Solution Manager
system You have to set up and operate the system which hosts your productive scheduler as a mission
critical system
In the SAP Solution Manager system you should set up a local System Landscape Directory in addition
to a central runtime System Landscape Directory This way you have a clear separation between your
management system (SAP Solution Manager) and managed systems in your landscape In addition
SAP Solution Manager then does not rely on a System Landscape Directory running in the production
environment For this setup configure the SLD data suppliers of your SAP Solution Manager system
to send data to the central runtime System Landscape Directory In addition configure automatic
bridge forwarding from your runtime System Landscape Directory to the local System Landscape
Directory For more information see the Planning Guide - System Landscape Directory
If you want to use a central system for Adobe Document Services we recommend that you install a
dedicated system for this purpose in your production environment For detailed information about
the sizing of the system for the different use cases see the Sizing Guide for Adobe Document Services at
SAP Service Marketplace at httpservicesapcomsizing Sizing Guidelines Solutions amp
Platform
We recommend that you start with this centralized SAP Solution Manager approach as depicted in the
following figure
5 System Landscape
52 Shared Services
4056 PUBLIC 2011-04-15
Figure 7 Single SAP Solution Manager Landscape
Large Customer Landscapes with Java
Large customers who have environments in their landscape that are large and distributed administered
by different groups or separated for security reasons can consider a distributed operations setup In
addition to the centralized setup described for small- and medium-sized customers above large
customers can put parts of the central management functions on extra hosts or systems for performance
or policy reasons You have the following options for a distributed setup
You may set up an extra system or client for Central User Administration (CUA)
The Change and Transport System (CTS) can run on an extra system However it is not
performance- or data-intensive
You may set up an extra system for central CCMS monitoring Depending on the customizing
and on the landscape size central CCMS may generate a lot of system load You can connect a
separate central CCMS to SAP Solution Manager for displaying alerts in the alert inbox of the System
Monitoring work center
You can use a separate SAP NetWeaver 70 system with usage type BI together with SAP Solution
Manager This may make sense with respect to the amount of landscape management data that is
stored for reporting purposes The amount of data strongly depends on the data granularity
storage time frame and landscape size
You can easily put Wily Introscope Enterprise Manager on an separate host
Other aspects described above for small- and medium-customers (such as the setup of the System
Landscape Directory) are also valid for large customers
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4156
523 Feature Details
This section provides further information about the features described above
5231 SAP Solution Manager
SAP provides you with SAP Solution Manager as the strategic application management platform and
to enable the collaboration between you and SAP You need to install at least one productive SAP
Solution Manager in your system landscape To ensure the availability of this application management
platform an SAP Solution Manager system is technically required to install or upgrade to SAP
NetWeaver 70 or higher If you are already using SAP Solution Manager you can also use it to manage
the solution you build with SAP NetWeaver In this case we highly recommend that you update SAP
Solution Manager to the latest version
As of SAP Solution Manager 70 SP15 you can use the newly created work centers
NOTE
During the SAP system installation or upgrade process you are prompted to enter the SAP
Solution Manager key An SAP Solution Manager system is required to generate this key Without
this key the installation or upgrade process cannot continue
You may generate all needed keys for your entire system landscape (development quality
assurance and production system) in one SAP Solution Manager system In case you plan to install
several solution landscapes (for example in different countries) one SAP Solution Manager
system is still sufficient
For more information see SAP Note 805390
It is possible to install multiple SAP Solution Managers If you do so they should host separate business
solutions
If you want to reduce the risk of unavailability you should not install SAP Solution Manager as a central
component Instead you can operate a 2-system-landscape with both a test and production
environment of SAP Solution Manager (especially if you are using time-critical functions like Support
Desk) If you also develop your own content a 3-system-landscape with a development test and
production environment is recommended
For more information about SAP Solution Manager see the following table
Topic Where to Find More Information
System infrastructure scenarios installation and configuration of SAP Solution Manager
Master Guide ndash SAP Solution Manager available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution ManagerltReleasegt
Benefits and usage scenarios SAP Solution Manager ndash Learning Maps available on SAP Service Marketplace at http
5 System Landscape
52 Shared Services
4256 PUBLIC 2011-04-15
Topic Where to Find More Informationservicesapcomrkt-solman or https
servicesapcomsolutionmanager
Additional information See SAP Service Marketplace at http
servicesapcomsolutionmanager
5232 Solution Manager Diagnostics
Solution Manager Diagnostics provides efficient and safe root-cause analysis of incidents in customer
solutions powered by SAP NetWeaver It can help monitor on operating systems databases Java
application activities performance and logs It also supports the reporting of software and
configuration changes that can lead to malfunctions and errors
You must run one Solution Manager Diagnostics within your SAP solution landscape if you run
applications based on SAP NetWeaver systems with usage type AS Java Agents are responsible for
delivering the data from all productive hosts within your system landscape to the Solution Manager
Diagnostics system
CAUTION
SAP Support performs root-cause analysis on incoming incidents with Solution Manager
Diagnostics Not installing and configuring this support infrastructure results in a dramatically
reduced service level
Solution Manager Diagnostics is fully integrated into SAP Solution Manager 70
Solution Manager Diagnostics also contains Wily Introscope (Display Server and Agent part) for
measuring performance as well as to troubleshoot problems of Non-ABAP applications Wily Introscope
is heavily used for troubleshooting applications running on AS Java
SAP has signed a distribution agreement for Wily Introscope SAP customers are allowed to use this
tool in a preconfigured way
For more information about Solution Manager Diagnostics and an FAQ list see SAP Service Marketplace
at httpservicesapcomdiagnostics
5233 System Landscape Directory
The System Landscape Directory (SLD) of SAP NetWeaver is the central directory of system landscape
information relevant for the management of your software life-cycle
NOTE
Note that the abbreviation SLD is not intended to define a product since the System Landscape
Directory is part of SAP NetWeaver This abbreviation is solely intended to improve readability
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4356
The System Landscape Directory contains a description of your system landscape (that is software
components that are currently installed) and a repository of software components that can
theoretically be installed in your landscape (such as the software components available from SAP)
Since this data gets updated automatically the System Landscape Directory provides reliable and up-
to-date system landscape information with as little effort for you as possible In this way the System
Landscape Directory acts as a central information provider for SAP and third-party tools that use this
data to deliver the services you need to keep your landscape up and running
For the System Landscape Directory as part of an SAP NetWeaver PI 71 landscape consider the following
aspects
Part of SAP NetWeaver PI 71 is a new version of the System Landscape Directory It is automatically
included in every SAP NetWeaver 71 system with usage type AS Java It offers enhanced functions
such as a full automatic synchronization mechanism for all data stored in it That is both data
delivered by data suppliers and data entered or changed manually in the System Landscape
Directory can be synchronized automatically This synchronization offers the following
A fully automated mechanism so no user interaction is required and conflicts are resolved
automatically
Asynchronous propagation of information so some nodes may be down temporarily
Communication over HTTP protocol
Uni- and bi-directional synchronization
Depending on your use case the full automatic synchronization could significantly reduce manual
synchronization effort
For SAP NetWeaver PI 71 the configuration of the system landscape directory and its data suppliers
is already included in the standard implementation procedure with SAPinst For existing systems
you only have to perform some quick and easy configuration actions to start operating the system
landscape directory server in an AS Java system
For SAP NetWeaver PI 71 you have the following options concerning SLD
Option 1
Run SAP NetWeaver PI 71 against an existing SLD running on SAP NetWeaver 70 We only
recommend this for upgrades from SAP NetWeaver 70 if you have a central SLD in operation
not running on one of your PI systems
Option 2
Use the SLD included in an SAP NetWeaver PI 71 system We recommend this option for new
installations and upgrades from older releases than SAP NetWeaver 70 due to the enhanced
functions and improved performance of SLD 71
NOTE
If you already have a central SLD running on SAP NetWeaver 70 in operation you could run
two SLD versions in parallel ndash SLD running on SAP NetWeaver 71 for your PI systems and
SLD running on SAP NetWeaver 70 for all other systemsuse cases This way your SAP
5 System Landscape
52 Shared Services
4456 PUBLIC 2011-04-15
NetWeaver PI 71 systems would benefit from the new features while it would be easy to set
up and operate such an SLD landscape For this purpose you could use the new fully
automatic synchronization This feature enables the automatic forwarding of all SLD data
from an SLD running on SAP NetWeaver 70 to an SLD running on SAP NetWeaver 71 As a
result there is no need to adapt most existing systems as their SLD data suppliers could still
send their data to the central SLD In brief the following steps would be required
1 Put SLD in a PI system into operation (part of standard implementation procedure)
2 Configure PI systems to use the new SLD (part of standard implementation procedure
for new PI systems)
3 Set up the fully automatic synchronization from your old SLD to your new SLD
As soon as an upgrade or an installation of a standalone AS Java 71 system is available you
could move your central SLD also to SAP NetWeaver 71 Then you could optionally shift
your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems
Figure 8
We recommend that you use a Domain Name System (DNS) alias so that you are able to switch to
another System Landscape Directory easily For example if customers build a new landscape they
normally start with a sandbox environment Over time more and more environments are set up
Once the production environment is in place move the System Landscape Directory there To do
this you can configure a new System Landscape Directory in the production environment
synchronize it with the old System Landscape directory and switch to the new one
Topology
Apart from the considerations above the System Landscape Directory offers several topology options
with different grades of availability at the expense of low administration and operation effort There is
no generic rule therefore on how to set up a System Landscape Directory in your system landscape
To find the topology and synchronization strategy for the System Landscape Directory that fits your
requirements concerning the System Landscape Directory availability (and hence the availability of
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4556
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
Figure 1 SAP NetWeaver PI Key Capabilities Overview
SAP NetWeaver Process Integration 71 enables the integration of the applications of the following
communication parties
B2B Party Any business partners that want to integrate their application with other applications
outside their own system landscape Scenarios that require industry standards are supported as
well as any scenarios that do not adhere to a particular industry standard
SAP Applications that run on SAP systems This includes the processing of events by using the
Business Activity Monitoring (BAM) infrastructure
3rd-Party Application Applications from 3rd-party providers within one system landscape for
example database or file-system-based
3rd-Party Middleware Middleware systems from 3rd-party providers that are required for the
integration of applications within a company and across company boundaries
SAP NetWeaver PI also supports internal company scenarios and cross-company scenarios It enables
you to connect systems from different vendors (non-SAP and SAP) in different versions and
implemented in different programming languages (Java ABAP and so on) to each other Like the rest
of the SAP NetWeaver platform SAP NetWeaver PI is based on an open architecture uses open standards
(in particular those from the XML and Java environments) and offers those services that are essential
in a heterogeneous and complex system landscape
To enable end-to-end SOA development SAP NetWeaver Process Integration 71 offers a Universal
Description Discovery and Integration (UDDI) v3-based Services Registry where providers can publish
service endpoints definitions and associated metadata and consumers can discover the appropriate
services for their scenarios The Services Registry provides capabilities for classifying and browsing
3 SAP NetWeaver PI Overview
1456 PUBLIC 2011-04-15
services using semantic-rich classification systems The Services Registry is part of Application Server
Java (AS Java)
31 Installable Software Units
SAP NetWeaver comprises the following three types of installable software units
Systems that are configured for a specific purpose as indicated by one or more usage types
Standalone engines that provide one specific (server) function in combination with one or more
SAP NetWeaver PI systems
Clients used by (many) people from their local front-end PC to access functions offered by systems
of SAP NetWeaver PI or standalone engines in the system landscape
In the following sections you can find more details about the software units The figure below provides
and overview of the software units
Figure 2 Installable Software Units for SAP NetWeaver PI
For this and other figures in this guide the following legend applies
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1556
Figure 3 Legend
311 Systems with Usage Types
SAP systems are the main building blocks of SAP NetWeaver They are identified by unique SAP system
IDs (SAPSIDs) and configured for a certain purpose as indicated by usage types Usage types have the
following characteristics
They are a structuring element for SAP software on a technical level
Usage Types determine the intended purpose of a system and the role it plays in a given (distributed)
use case
They are realized by installing and configuring a collection of software components
They allow a logical view of the technology platform SAP NetWeaver PI
A usage type may require other usage types in the same system to operate
They can also be run in the same system together with other usage types that are not a prerequisite
How SAP NetWeaver Systems are Used
The following sections describe the usage types and their dependencies for SAP NetWeaver PI
Application Server ABAP (AS ABAP)
Purpose
AS ABAP is used to provide the ABAP foundation of SAP NetWeaver PI
Application Server ABAP provides a complete development and runtime environment for ABAP-based
applications It is optimized for the development of highly scalable business applications The ABAP
development and runtime environment makes it possible to develop complex business applications
3 SAP NetWeaver PI Overview
31 Installable Software Units
1656 PUBLIC 2011-04-15
without having to worry explicitly about technical details such as process or memory administration
multi-user capability database connections or similar issues These are provided in the basis services or
are integrated directly in the ABAP runtime The application development is similarly independent of
the underlying platform The application server decouples the application coding completely from the
operating system and database that are used
Dependencies
AS ABAP can be combined optionally with other usage types in one system
Application Server Java (AS Java)
Purpose
AS Java is used to provide the Java foundation of SAP NetWeaver PI using the Java Engine a Java EE-
compliant application server for running enterprise applications In addition to the pure Java EE
standard technologies the Java Engine implements complementary technologies such as Web Dynpro
or Web Services that are targeted at supporting large-scale real-business application development
projects
Dependencies
AS Java can be combined optionally with other usage types in one system
Process Integration (PI)
Purpose
PI consists of core components that model design automate and integrate processes in one or more
application systems For the integration of internal and cross-company processes PI is used to
incorporate all the functions of what was formerly known as Exchange Infrastructure (XI) In addition
PI contains core components for Business Process Management for application-embedded and
application-unbounded processes
The Advanced Adapter Engine is also part of usage type PI You use Advanced Adapter Engine to connect
to SAP systems (RFC adapter) and external systems You use the various adapters in Advanced Adapter
Engine to convert XML- and HTTP-based messages to the specific protocol and format required by
these systems and the other way around You can use the Advanced Adapter Engine that is part of
your PI system as a central Advanced Adapter Engine Optionally (for performance reasons) you can
install a non-central Advanced Adapter Engine [page 19] separately as a system with AS Java and parts of the
usage type PI on a separate host
Dependencies
PI requires AS ABAP and AS Java as prerequisites in the same system
For installing PI it is mandatory to have a dedicated PI system This applies to development quality
and production landscapes It is a prerequisite that no other system in your system landscape has a
higher release and enhancement package level than the PI system If you want to upgrade or install an
application in your system landscape you first have to make sure that the current release and
enhancement package level of the PI system is on the same level - if required you have to upgrade the
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1756
PI system first to the new or a higher release In a dedicated PI system this can be accomplished with a
minimum of downtime Also the PI system would not be affected by the downtime of other usage
types running in the same system
Configuration of Systems with Usage Types
Configuration information is available in the installation guides the configuration wizard and SAP
Solution Manager
In the Installation Guide ndash SAP NetWeaver PI 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt you find
initial technical configuration tasks This guide also informs you about how you can run the
configuration wizard and how you can access the configuration information in SAP Solution
Manager
For certain usage types configuration tasks can be applied by the configuration wizard after the
installation To do this you start the configuration wizard from SAP NetWeaver Administrator
The configuration steps for systems with usage types required for an use case are accessible through
SAP Solution Manager
To be able to use SAP Solution Manager for the configuration tasks you have to import the latest
SAP Solution Manager Implementation Content (Add-On ST-ICO) that is available for your SAP
Solution Manager release For more information see SAP Note 631042 (Release strategy for Implementation
Content (ST-ICO))
SAP Solution Manager Implementation Content is available on SAP Service Marketplace at
httpservicesapcomswdc Installations amp Upgrades Entry by Application Component SAP
Technology Components SAP Solution Manager ltReleasegt Content ST-ICO
In SAP Solution Manager you create a project and a project structure In the configuration phase
you select configuration structures with pre-delivered SAP content for your project You can find
the following different types of configuration tasks in SAP Solution Manager
Mandatory configuration tasks All configuration tasks that are mandatory for the standalone
engine or usage type
Optional configuration tasks Configuration tasks for areas where customers need to decide
if they want to use these functions (for example high availability or security settings)
Additional functions ndash configuration tasks Configuration tasks for functional units that are
used in certain use cases only
A marked checkbox in front of the configuration tasks indicates those configuration tasks that are
relevant for the use case you have chosen To configure ABAP systems SAP Solution Manager
offers executable configuration files (IMG activities)
For information about using SAP Solution Manager Content and creating a configuration guide
see the following documentation
httphelpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Implementing
and Upgrading SAP Solutions Configuration
3 SAP NetWeaver PI Overview
31 Installable Software Units
1856 PUBLIC 2011-04-15
How to Create a Configuration Guide using SAP Solution Manager available at http
servicesapcomsolutionmanager Media Library How-To Documents
Restrictions for Systems with Multiple Usage Types
If you have one system with multiple usage types be aware that we do not provide standard tools
to separate these usage types and distribute them to multiple systems at a later stage For example
if you have a system with usage types A and B you are not able to migrate it with SAP standard
tools into two systems one with usage type A only and the other with usage type B only
In addition we do not provide standard tools to merge multiple systems with different usage types
into one system with multiple usage types at a later stage
If you want to perform these tasks you require specific project support
The following figure shows that SAP standard system copy and migration tools do not support
you in separating or merging systems with usage types
Figure 4 No Support for Merging or Separating Systems with Usage Types
Although you can use one system for multiple usage types client restrictions apply for usage type
PI PI requires a dedicated client due to special PI requirements concerning the client pipeline
Whereas application client pipelines only send and receive messages the central PI pipeline can
also map messages to different formats before sending them
312 Standalone Engines
Standalone engines of SAP NetWeaver are additional installable software units They do not work as
full-blown systems of SAP NetWeaver but as standalone engines that provide a specific (server) function
in combination with one or more SAP NetWeaver systems
Standalone engines are not part of a usage type They do not run on AS ABAP or AS Java
The standalone engines that are available for SAP NetWeaver Process Integration are described in the
following
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1956
Gateway
It is possible to install an SAP instance of an SAP NetWeaver system based exclusively on a standalone
gateway This type of instance does not contain normal work process types (dialog background update
enqueue or spool) Only the gateway process (gwrd) is started If there is an SNA connection to an R
2 system gateway work processes (gwwp) are also started
SAP Conversion Agent by Informatica
SAP Conversion Agent by Informatica is a data conversion tool that enables you to create interfaces
between any data formats and XML-based systems SAP Conversion Agent can convert unstructured
semi-structured and structured formats to XML and the other way around The Conversion Agent
comprises the Conversion Agent Studio and the Conversion Agent Engine In the Conversion Agent
Studio you can develop and configure data conversions The Conversion Agent Engine executes the
data conversions
Search and Classification (TREX)
You can use Search and Classification with SAP NetWeaver PI to search for messages that were previously
indexed Message search using index provides additional methods of searching for specific messages In
addition to static header attributes you can also use adapter-specific message attributes and data from
the message payload for the search A requirement of this however is that the messages are indexed
first You can apply the index-based message search to one or all indexed components of an integration
landscape (domain) Integration Server Adapter Engines and ABAP business systems
For more information see the SAP Library [page 12] at Administratorrsquos Guide Technical Operations for SAP
NetWeaver Administration of SAP NetWeaver Systems Administering PI (Process Integration) Monitoring Index
Administration
Web Dispatcher
The Web Dispatcher lies between the Internet and your SAP system It is the entry point for HTTP(s)
requests into your system which consists of one or more SAP NetWeaver application servers As a
software web switch the Web dispatcher can reject connections or accept them When it accepts a
connection it balances the load to ensure an even distribution across the servers
You can use the Web dispatcher in ABAPJava systems and in pure Java systems as well as in pure ABAP
systems
It is also beneficial to use the Web Dispatcher if you do not need security functions (entry point in the
demilitarized zone (DMZ) SSL URL filtering) but you simply want to balance the load between
multiple SAP NetWeaver Application Server instances
Since Web Dispatcher is optional for every SAP system it is not contained in the system landscape and
the implementation sequence of the use case in this documentation
For more information see the SAP Library [page 12] at Function Oriented View Application Server Infrastructure
SAP Web Dispatcher
3 SAP NetWeaver PI Overview
31 Installable Software Units
2056 PUBLIC 2011-04-15
Advanced Adapter Engine
You use the Advanced Adapter Engine to connect to SAP systems (RFC adapter) and external systems
You use the various adapters in Advanced Adapter Engine to convert XML- and HTTP-based messages
to the specific protocol and format required by these systems and the other way around For specific
senderreceiver combinations messages can be processed without invoking the central Integration
Engine In principle you connect external systems using the adapters that are installed centrally or
non-centrally in Advanced Adapter Engine You can use the Advanced Adapter Engine that is part of
your PI system as a central Advanced Adapter Engine Optionally (for performance reasons) you can
install a non-central Advanced Adapter Engine separately as a system with AS Java and parts of the
usage type PI on a separate host
Adapter Engine (Java SE)
Adapter Engine (Java SE) is a separate software unit You can use it only if you have SAP NetWeaver
systems with usage type PI in your system landscape It has to be installed manually You use the Adapter
Engine (Java SE) to connect to external systems Using the various adapters in the Adapter Engine (Java
SE) XML and HTTP-based messages can be converted to the specific protocol and format required by
such systems and the other way around The Adapter Engine (Java SE) only provides some of these
adapters as a standalone version with restricted functions for operating systems that do not support
SAP NetWeaver PI 71 but that have at least a Java Runtime Environment 50 Therefore you should
use the Adapter Engine (Java SE) only if the platform prerequisites do not allow you to use the Advanced
Adapter Engine
SAP Partner Connectivity Kit
SAP Partner Connectivity Kit (PCK) runs on AS Java with parts of the usage type PI It enables a system
of a smaller company or subsidiary that does not run SAP NetWeaver PI to connect to your SAP
NetWeaver systems
313 Clients
Clients are additional installable programs or tools They reside either on local front-end PCs accessed
by users or on back-end systems where they act as client programs within an SAP NetWeaver system
landscape
The clients that you can use with SAP NetWeaver Process Integration are described in the following
sections
SAP GUI
NOTE
We recommend that you use the following versionsI
SAP GUI for Windows 710 (or higher) with the latest patch level
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 2156
SAP GUI for Java 710 (or higher) with the latest revision
The integrated SAP ITS 710
For more information about the SAP GUI family see SAP Service Marketplace at http
servicesapcomsapgui
SAP offers three different client applications for accessing ABAP applications in SAP systems (such as
SAP NetWeaver systems with usage type AS ABAP) This SAP GUI family consists of
SAP GUI for HTML
SAP GUI for HTML is based on the SAP integrated Internet Transaction Server (ITS) which is
included in the installation of SAP NetWeaver systems as of SAP NetWeaver 2004 On the client
side only a suitable browser (such as Internet Explorer 70 or Firefox 20) and a virtual machine are
required SAP ITS 620 is not compatible with SAP NetWeaver 71
SAP GUI for the Java environment (SAP GUI for Java)
SAP GUI for Java is a generic SAP GUI that covers a variety of platforms
For more information about the installation of SAP GUI for Java see the documentation Installation
Guide ndash SAP Front End
SAP GUI for the Windows environment (SAP GUI for Windows)
SAP GUI for Windows is SAPs universal client for accessing all SAP applications built on ABAP
technology It is available on the Microsoft Windows platform only and offers the broadest feature
set of all members of the SAP GUI family
For more information about the installation of SAP GUI for Windows see the Installation Guide ndash
SAP Front End
SAP NetWeaver Developer Studio
The SAP NetWeaver Developer Studio is SAPrsquos Integrated Development Environment (IDE) for Java
and is based on the open-source tools framework Eclipse 33 With the SAP NetWeaver Developer Studio
you can develop Java EE 5 applications from scratch using the built-in support for new technologies
such as EJB 30 and JSF 12
During the installation of the SAP NetWeaver Developer Studio several features are offered for
installation For SAP NetWeaver PI 71 only the following features are relevant
SAP NetWeaver Developer Studio Platform
SAP NetWeaver Developer Studio Java EE
NOTE
If you want to use one of the other features you need SAP NetWeaver Composition Environment
and a corresponding developers licence
For more information about the installation of SAP NetWeaver Developer Studio see the Installation
Guide ndash SAP NetWeaver Developer Studio 71 or Installation Guide ndash SAP NetWeaver Developer Studio 71 Including
Enhancement Package 1
3 SAP NetWeaver PI Overview
31 Installable Software Units
2256 PUBLIC 2011-04-15
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
SAP enhancement packages are a new way of delivering new functions for SAP NetWeaver This allows
a clear separation between the delivery of new functions on the one hand and corrections legal changes
and security updates on the other hand (in Support Package stacks) SAP enhancement packages are
cumulative an enhancement package always contains the functions of the corresponding predecessor
enhancement packages
Enhancement packages are maintained by their own Support Packages while the main release is in
maintenance
Benefits
SAP enhancement packages offer the following benefits
You have reduced effort for testing and no effort for training when applying Support Packages as
new features are only shipped with enhancement packages
Adding new functions between releases becomes predictable and controllable
New functions can be added successively in small steps There is no need to fully upgrade your
system to get new functions
You have minimal training effort when applying an enhancement package because existing
functions are not replaced
Implementation
There are the following ways to get an SAP NetWeaver system with the release level of SAP enhancement
package 1 for SAP NetWeaver Process Integration 71
New installation of SAP NetWeaver PI 71 including enhancement package 1 using the standard
installation tool SAPinst
Upgrade of an existing SAP NetWeaver system from a release lower than SAP NetWeaver PI 71 to
SAP NetWeaver PI 71 including enhancement package 1 For this you use the upgrade programs
SAPup (for ABAP) and SAPJup (for Java)
Installation of the enhancement package on an existing SAP NetWeaver PI 71 system
For this you use the Software Update Manager (SUM) The Software Update Manager evolved
from the previously used SAP Enhancement Package Installer The tool has been renamed to reflect
its broader use for example you can also use it for applying Support Package Stacks to your system
On the ABAP side the Software Update Manager uses a system cloning and switch procedure for
installing enhancement packages It installs a copy of the system the shadow system parallel to
the original system This shadow system is used to update the relevant software components and
to install the additional components while the original system is still in production operation At
a certain point during downtime the switch to the new system is made and afterwards any parts
of the original system that are no longer needed are deleted The enhancement package installation
in a Java system uses a deploy-based procedure that is no shadow system is used The Software
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2011-04-15 PUBLIC 2356
Update Manager requires a stack configuration file (xml file) as input file for the enhancement
package installation procedure This file lists all the packages that are to be installed in your systems
The stack configuration file is generated when you download the required packages
As the Software Update Manager is updated regularly we recommend to always use the latest
version It is delivered as part of the SL toolset For more information see http
servicesapcomsltoolset
For an overview of all required steps for the enhancement package installation process and
corresponding documents see Process Overview Installation of Enhancement Package 1 on an Existing SAP
Netweaver PI 71 System [page 28]
Content of SAP Enhancement Package 1 for SAP NetWeaver PI 71
With enhancement package 1 for SAP NetWeaver PI 71 new features are introduced and some existing
are changed The following is a selection of some of the most important enhancements
Enhanced design and modelling options in the Enterprise Services Repository
New services registry
Support for new Web services standard (Web Services Reliable Messaging)
New modules for the Advanced Adapter Engine
Use of shared memory of the ABAP Application Server for message processing
For more information about the changes see SAP Library [page 12] at Whatacutes new in SAP NetWeaver PI 71
ndash Release Notes
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2456 PUBLIC 2011-04-15
4 SOA-Based Integration Use Case
41 Overview
You can use SOA-based integration to set up the communication between service providers and service
consumers in both application-to-application and business-to-business scenarios and to execute
operate and monitor the communication at runtime SOA-based integration covers both direct (point-
to-point) as well as mediated (via an Integration Server) communication between service providers and
service consumers
The use case spans the whole life cycle of a SOA-based integration scenario including
Scenario modeling and service design in the Enterprise Services Repository
Implementation of the service provider and consumer in the back-end systems
Configuration and finally execution monitoring and operation of the integration scenario
For scenarios using Integration Server or broker-based communication the configuration of the
different connectivity options (for example SOAP RFC Web Services Industry standards and JDBC)
and their enhancements is covered
For more information see the following documents
Service-Enabling with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdnsoa-modeling
Getting Started
Service-Enabling a Legacy Application with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdn
soa-servicebus Getting Started
In the following you will find information about the installation of the involved software units
42 System Landscape
The following figure shows the system landscape for this use case
4 SOA-Based Integration Use Case
41 Overview
2011-04-15 PUBLIC 2556
Figure 5 SOA-Based Integration
It is mandatory to have a dedicated PI system This applies to development quality and production
landscapes
For PI it is a prerequisite that no other system in your system landscape has a higher release than
the PI system For exceptions to this rule see SAP Note 1043047 For example SAP XI 30 is compatible
with SAP NetWeaver 640 and 70 application systems since the same XI protocol is used Apart
from these exceptions if you want to upgrade or install an application in your system landscape
you first have to make sure that the PI system is on the same release level If required you have to
upgrade the PI system first to the new or a higher release
CAUTION
Although it should be technically possible to run an application system with a higher release
than your PI system in your system landscape this is not supported by SAP (apart from the
exceptions listed in SAP Note 1043047) Therefore you run such a landscape at your own risk
You can use the Advanced Adapter Engine that is part of your PI system as a central Advanced
Adapter Engine
Adapter Engine (Java SE) can be installed in a non-SAP Java environment However it only hosts
a subset of the adapter functionality is only supported for compatibility reasons and should be
used only if this is a precondition in your environment
Optionally you can use the Change Management Service (CMS) of an SAP NetWeaver 70 system
with usage type DI to transport design objects and repository objects For more information see
the SAP Library [page 12] at Administratoracutes Guide Technical Operations for SAP NetWeaver Administration
of SAP NetWeaver Systems PI (Process Integration) Software Logistics Transporting ESR Content and Objects
of Integration Directory PI Transports Using the Change Management Service (CMS)
Smaller business partners or subsidiaries that do not run SAP NetWeaver install SAP Partner
Connectivity Kit in their system landscape SAP Partner Connectivity Kit enables XML document
4 SOA-Based Integration Use Case
42 System Landscape
2656 PUBLIC 2011-04-15
exchange between your SAP NetWeaver systems and the partner systems Since SAP Partner
Connectivity Kit gets installed in their system landscape it is not shown in the system landscape
figure above
The AS ABAP system acts as an application and service provider For Java Web Services you also
require AS Java In addition you require SAP NetWeaver Developer Studio on the client side as a
development environment
The Web service client can be either an SAP or a non-SAP application For example an AS ABAP
system or a Web browser could act as application or service consumer
You can install SAP Conversion Agent by Informatica in the system with usage type PI or on a host
where SAP Partner Connectivity Kit is installed or on a host where neither usage type PI nor SAP
Partner Connectivity Kit is installed
43 Implementation Sequence
Procedure
To install this use case perform the steps listed in the following table
StepAction[Corresponding Documentation] Remarks
1 Make sure that you have performed the preparation steps You have planned your system landscape [page 33]
(that is you have decided how many systems you require how you want to use each of these systems and which standalone engines and clients you require)
With the help of your hardware partner you have mapped your systems and standalone engines to properly sized hosts
You have planned and installed shared services [page 35]
2 Installation of system with usage type PI (includes the installation of AS ABAP and AS Java)
NOTE
For usage type PI a Unicode installation is mandatory
[Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt]
If you want to use the features of enhancement package 1 use the direct installation of SAP NetWeaver PI 71 including enhancement package 1
Make sure that you perform the configuration steps as described in the installation guide For certain usage types configuration tasks can be applied by the configuration wizard These configuration tasks as well as any additional configuration steps for your use case are listed in SAP Solution Manager For more information
4 SOA-Based Integration Use Case
43 Implementation Sequence
2011-04-15 PUBLIC 2756
StepAction[Corresponding Documentation] Remarks
see the Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt
3 Install the Adapter Engine (Java SE) engines if required[Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
4 To integrate small business partners and subsidiaries the business partners or subsidiaries install SAP Partner Connectivity Kit running on AS Java with parts of usage type PI in the business partners or subsidiarys system landscape[Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
5 Install SAP Conversion Agent by Informatica if required[SAP Library [page 12] at Function-Oriented View Process Integration SAP Conversion Agent by Informatica Deploying and Using Conversion Agent ]
6 Installation of clients SAP GUI
[Installation Guide ndash SAP Front End]
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
The process sequences give a comprehensive overview of the steps relevant for the enhancement
package installation on an existing SAP NetWeaver PI 71 system
The process sequence is divided into a planning phase and an implementation phase Each step in both
phases contains references to the corresponding documentation to ensure that you can easily find the
information you need
Process
NOTE
To download the enhancement package files and required Support Packages you require the SAP
Solution Manager Maintenance Optimizer You have the following options
Manual Selection
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2856 PUBLIC 2011-04-15
You manually select the required files from SAP Service Marketplace at http
servicesapcomswdc using the SP Stack Application You use the Maintenance Optimize
only to approve the packages which is a prerequisite for the download
Automatic Calculation
The Maintenance Optimizer supports the download of a consistent queue that includes all
necessary Support Packages and enhancement packages In addition SAP Solution Manager
calculates a valid import queue for the selected SAP system and generates the enhancement
package stack configuration file that you require for the installation
As a prerequisite the system that you want to update needs to be maintained correctly in
SAP Solution Manager System Landscape As the Maintenance Optimizer uses this data for
the calculation it is crucial that the data is up-to-date In addition the SAP Solution Manager
system requires a Minimum Support Package level (see below)
Planing PhaseStep Description Documentation
Hardware amp Software Prerequisites
Check which platforms are supported for your target release (OSDB dependencies)
Product Availability Matrix (PAM) at httpservicesapcompam
Check which hardware sizing is required for your target release
Sizing information at httpservicesapcomsizing
Solution Manager Prerequisites
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of the required software packages you have to make sure that your SAP Solution Manager system has the required Support Package levelAt least SAP Solution Manager 70 EHP1 Support Package Stack 17 is required We recommend to use SAP Solution Manager 70 EHP1 Support Package Stack 23Check if you need to do an update or upgrade of your SAP Solution ManagerMake sure that you run the guided procedure SOLMAN_SETUP after every installation or update of SAP Solution Manager and that it completes successfully
For upgrades from source release SAP Solution Manager 31 and 32Upgrade Guide ndash SAP Solution Manager 70 incl Enhancement Package 1For updates from SAP Solution Manager 70Update Guide SAP Enhancement Package 1 for SAP Solution Manager 70Follow-up activities after an Support Package Stack update or enhancement package updateSolution Operations Guide ndash SAP Solution Manager 70 EHP1 section Software Change Management All guides are available at http
servicesapcom instguides SAP Components SAP Solution Manager -gt Release 70 EHP 1
Implementation PhaseStep Description Documentation
1Solution Manager Preparation
Configure the SAP Solution Manager Maintenance Optimizer
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of software packages make sure your
Configuration of Maintenance Optimizer http
helpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Change Request Management and Change ControlMaintenance Optimizer
Prerequisites
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 2956
Implementation PhaseStep Description Documentation
system landscape data in SAP Solution Manager is maintained correctlyLandscape Verification 10 which is an add-on to SAP Solution Manager can support you in maintaining your system landscape data The use of this tool is optional
Landscape Verification http
wwwsdnsapcom irj
sdn alm-update-
management link Landscape Verification under Related Areas on Upgrade and Update Management (in the right column)
SAP Note 1468605 (Installation of Landscape Verification)
Maintaining System Landscape Information [page 47]Note that the information provided in this section is based on SAP Solution Manager 70 EHP1 SP23
2System Preparation
Prepare your system as described in the documentation for example perform OS DB specific preparations and the PI-specific preparations
Update Guide ndash Update of SAP Systems with Software Update Manager sections Planning and Preparation
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
3Software Download
Select and download the software packages in either of the following ways Automatic calculation Create
a maintenance transaction in the Maintenance Optimizer and choose the Calculate Files Automatically option
Manual Selection Create a maintenance transaction in the Maintenance Optimizer and choose the Select Files Manually option You then can select the files manually using the SP Stack application in SAP Service Marketplace
NOTE
You have to download the stack configuration file manually after you have selected all files in the SP Stack
httphelpsapcom SAP Solutions SAP Solution Manager
SAP Solution Manager 70 EHP1 ltSPgtChange Request Management and
Change Control Maintenance Optimizer Maintenance Procedure Scenarios
For information about the automatic calculation see Maintenance Transaction with Installation of an Enhancement PackageFor information about the manual selection and approval process see section Approve and Download Files in Download Basket
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
3056 PUBLIC 2011-04-15
Implementation PhaseStep Description Documentation
application Choose Generate Stack XML and save the file
4Enhancement Package Installation
Run Software Update Manager to update your system with the selected software packages
Update Guide ndash Update of SAP Systems with Software Update Manager
5Follow-Up Steps
Perform technical and PI-specific follow-up activities after the enhancement package installation is done
Update Guide ndash Update of SAP Systems with Software Update Manager section Follow-Up Activities
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
6Configuration
Configure newly installed enhancement package functions using SAP Solution Manager content
See Systems with Usage Types [page 16] section Configuration of Systems with Usage Types
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 3156
This page is left blank for documents that are printed on both sides
5 System Landscape
51 Planning Your System Landscape
The installable software units that make up your system landscape depend on the functions that you
want to implement For information about the features see systems [page 16] standalone engines [page 19]
and clients [page 21]
In addition you have to determine the required shared services [page 35] (such as SAP Solution Manager
or SAP NetWeaver Administrator) that run on central systems in your system landscape and the
landscape aspects relevant for their implementation
In the following you will find general information that you should consider when planning your system
landscape
Sizing
You have to map systems and standalone engines to hosts after you have a clear picture of the following
Which systems and standalone engines you require
How many systems you require and how you want to use each of these systems
NOTE
No general guideline can be given for the sizing of your landscape since this relies heavily on your
requirements You should therefore perform this task together with your hardware partner and
your technical consultant
For information about sizing your systems you can use the following information sources
Your first point of reference is the Quick Sizer
SAP built the Quick Sizer as an online sizing questionnaire Internet application in close cooperation
with its hardware partners This tool delivers general sizing categories based on your volume load
estimates The results provide an objective basis for sizing independent of platform and
configuration
For more information see SAP Service Marketplace at
httpservicesapcomsizing for the SAP NetWeaver PI 71 sizing guide available under
Sizing Guidelines Business Suite amp Services
httpservicesapcomquicksizer for more information and access to the tool itself
Also consider the following important aspects concerning sizing
High availability
5 System Landscape
51 Planning Your System Landscape
2011-04-15 PUBLIC 3356
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Technical Infrastructure High Availability
Unicode
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Internationalization
Contact your hardware partner to find out the appropriate number of sized hosts
The platform-independent abstract results of the Quick Sizer can be used by any of our hardware
partners to create a concrete offer SAP itself does not make any hardware recommendations the
responsibility for sizing and detailed hardware configuration lies with the hardware partners
Figure 6 Example of Mapping of Systems and Standalone Engines to Three Hosts
NOTE
Optionally you could also distribute single systems to multiple hosts For example you could
decide to install the database instance of an SAP system on a separate host for performance
reasons or distribute other system instances to achieve high availability
To provide a mapping that fits your required functions and performance your hardware partner
and your technical consultant have to identify the number of required instances of SAP NetWeaver
find out how to distribute these instances to hosts and what functions will run on which instance
Therefore the hardware partner and the technical consultant have to consider many different
aspects such as
Number of required SAPS (SAP Application Benchmark Performance Standard) for each
system (provided by Quick Sizer)
Landscape-relevant aspects concerning security For more information see the SAP Security
Guide in the SAP Library [page 12] at Administratoracutes Guide Security Guide
Landscape-relevant aspects concerning scalability high availability operation and software
life-cycle management
5 System Landscape
51 Planning Your System Landscape
3456 PUBLIC 2011-04-15
For more information about relevant aspects for the mapping of systems to hosts see the document
Technical Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
Scaling and Distribution Options
You may need to design your system landscape for a large number of users SAP NetWeaver PI offers
you different means of scalability The following list provides you with some examples
You could install multiple systems of one type and use them for different purposes
You could scale every system by installing dialog instances or by distributing the database instance
For more information about distribution options on the instance level see the Technical
Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
For every SAP system you could additionally install Web Dispatcher For more information see
the SAP Library [page 12] at FunctionndashOriented View Application Server Infrastructure SAP Web
Dispatcher
You could further distribute certain standalone engines ndash for example Search and Classification
(TREX) is based on a flexible architecture that supports a distributed installation For more
information see the Technical Infrastructure Guide ndash SAP NetWeaver PI 71 available in SAP Service
Marketplace at httpservicesapcominstallNWPI71
52 Shared Services
You normally run shared services on central systems in your system landscape The following features
could be used for SAP NetWeaver Process Integration to realize shared services
SAP Solution Manager
Used to implement train test maintain monitor control change and manage incidents of your
SAP solution system landscape (open end-to-end application management)
As of SAP Solution Manager (70) 40 Support Package 15 SAP Solution Manager has become the
platform for SAPs end-to-end solution operations strategy Functions for complete application
management has been combined with administrative tools and has been merged in newly created
role based work centers
NOTE
Be aware that you require an SAP Solution Manager system to install or upgrade to SAP
NetWeaver 70 and higher An SAP Solution Manager system is required to generate the SAP
Solution Manager key needed during the installation or upgrade process Without this key
the installation or upgrade process cannot continue
For SAP NetWeaver Process Integration you require SAP Solution Manager 70
For more information see SAP Note 805390
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3556
Solution Manager Diagnostics
An integral part of SAP Solution Manager that is running as a Java application on the Java stack of
SAP Solution Manager 70 Solution Manager Diagnostics is used to analyze the root cause of
incidents in your landscape in an efficient and safe way Before Go-Live Solution Manager
Diagnostics has to be set up and made accessible remotely
SAP NetWeaver Administrator
SAP NetWeaver Administrator is the central administration component which is used for
monitoring and administering Java applications It is included in SAP NetWeaver systems with AS
Java
SAP NetWeaver Administrator exists in the following flavors
A local mode which runs out of the box and which focuses on administrating the underlying
SAP NetWeaver AS Java
NOTE
For a SAP NetWeaver PI 71 it has a special role which you need to activate using a
configuation wizard
A central mode which has to be configured before use and which deals with the system
landscape management
SAP has decided to merge the central mode of SAP NetWeaver Administrator into the new work
centers available as of SAP Solution Manager 70 SP 15 Thus it can be used in an administrative
context together with non-Java-based administration tools Although the central mode of SAP
NetWeaver Administrator will be still available for some time SAP will not develop this tool any
further SAP focuses on optimizing the administrative work centers of SAP Solution Manager
instead
The local mode of SAP NetWeaver Administrator stays untouched It is available for current and
future releases of SAP NetWeaver
SAP Central Process Scheduling by Redwood
SAP Central Process Scheduling application by Redwood enables central job scheduling and job
monitoring of current and old releases of AS ABAP systems (as of Basis Release 31) This application
is fully integrated in SAP NetWeaver Depending on the business needs SAP business applications
are the initial trigger for scheduled activities You can now manage jobs and job chains conveniently
using a graphical user interface
System Landscape Directory
The System Landscape Directory is the central directory of system landscape information relevant
for the management of your software life-cycle It contains a description of your system landscape
(that is software components that are currently installed) and a repository of software components
that can theoretically be installed in your landscape (such as the software components available
from SAP)
Adaptive Computing Controller
5 System Landscape
52 Shared Services
3656 PUBLIC 2011-04-15
The Adaptive Computing Controller enables users to control an adaptive computing landscape
from a single point through observation operation and dynamic resource distribution With
adaptive computing hardware software and system services are able to adapt to changing business
needs In the Adaptive Computing Controller the run-time data of logical and physical landscapes
can be monitored application services can be startedstoppedrelocated and hardware resources
can be assigned to application services The operation can also be mass executed and be planned as
tasks to be executed
For more information about the installation of the Adaptive Computing Controller tool see the
document Installation Guide ndash Adaptive Computing Controller in SAP NetWeaver 71 available on SAP Service
Marketplace at httpservicesapcominstallNWPI71
For more information about Adaptive Computing in general see httpsdnsapcomirj
sdnadaptive
521 Use Cases
You can use the applications and tools described above for use cases that are normally performed
centrally The following sections describe these use cases
5211 End-to-End Solution Operations
Running business applications through their complete life-cycle is a challenge Therefore SAP has
started the Run SAP methodology for implementing End-to-End Solution Operations Based on a set
of SAP standards a roadmap and a package for training and certification Run SAP helps customers to
facilitate End-to-End Solution Operations
You can download the SAP standards for Solution Operations from SAP Service Marketplace at http
servicesapcomsupportstandards They describe roles customers typically have in their IT
environment For optimal role support SAP has grouped existing and new functions in SAP Solution
Manager work centers as of SAP Solution Manager 70 Support Package 15 Operations aspects are fully
covered by adding administrative functions for SAP NetWeaver as well Work centers are ABAP Web
Dynpro-based applications They offer the following advantages
Easy to use similar look and feel
Context transfer while jumping from one work center into another
Logical grouping of tools for a certain area
Simple authorization concept
Easy to expand
Each IT role belongs to one or more work centers For instance the Technical Administrator IT role is
covered by the work centers for System Monitoring System Administration and Landscape Management
The following work centers are available
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3756
Business Process Operations
Change Management
Root Cause Analysis
Implementation Upgrade
Incident Management
Test Management
Job Management
System Landscape Management
Solution Documentation Assistant
SAP Engagement and Service Delivery
SAP Solution Manager Administration
System Administration
System Monitoring
My Home is the central point of access to all important data of almost all work centers in SAP Solution
Manager
5212 Support Infrastructure
A key requirement for effective support of IT solutions is the ability to perform root cause analysis with
speed and efficiency
With SAP Solution Manager SAP has long had an infrastructure in place for its ABAP applications that
efficiently supports SAP solutions This helps ensure the high availability and smooth running of
business processes For more information see the SAP Solution Manager section
With Solution Manager Diagnostics this knowledge has been extended to Java applications If for
example homegrown Java applications cause instability Solution Manager Diagnostics helps trace the
cause to eradicate the problem rapidly Solution Manager Diagnostics is fully integrated into SAP
Solution Manager 70 Solution Manager Diagnostics also contains two third-party tools CArsquos Wily
Introscopereg for measuring performance as well as troubleshooting problems of the Java EE Engine
and applications running on it and Mercury Loadrunnerreg which enables SAP Support to produce a
defined load in the SAP solution landscape remotely For more information see Solution Manager
Diagnostics [page 43]
The support infrastructure provides SAP Support with safe access to your productive landscape for safe
root cause analysis so ensuring that SAP Support does not change your landscape inadvertently You
require a support infrastructure to run SAP NetWeaver
The following figure shows the overall infrastructure including SAP NetWeaver administration tools
that are used by administrators or operators at the customer site
5 System Landscape
52 Shared Services
3856 PUBLIC 2011-04-15
Landscape Aspects
If you use SAP NetWeaver Process Integration 71 productively besides SAP Solution Manager (as a
central support platform) you have to set up Solution Manager Diagnostics for supportability reasons
Implementation Sequence
For information about the implementation of the support infrastructure see the document Master
Guide ndash SAP Solution Manager 70 available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution Manager ltReleasegt
5213 Collection of Landscape Data
Amongst other applications and services the support infrastructure and the SAP NetWeaver
administration tools rely on system landscape data
For SAP NetWeaver PI 71 you have to run non-ABAP components in your solution landscape
Therefore the System Landscape Directory is mandatory The landscape data that is automatically
gathered by the System Landscape Directory is replicated to SAP Solution Manager There are several
topology options for the System Landscape Directory They offer different grades of availability
administration and operation effort
For more information see the System Landscape Directory section
5214 Authentication and Single Sign-On
Before implementing your system landscape plan how to implement authentication and how to
integrate different systems into a Single Sign-On landscape Single Sign-On reduces complexity for end
users saving them valuable time while also reducing administration effort for resetting passwords
thereby contributing to TCO reduction
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
5215 Integrated User and Access Management
In a system landscape containing a combination of ABAP and Java components we recommend that
you integrate your user and access management so that you can use the same user data across different
systems administer this data centrally and control access to data SAPs mature fine-grained
authorization concept allows detailed control of access rights SAP NetWeaver provides both ABAP and
Java-based user management solutions The user management solution that you use to administer
your user data depends on factors such as the type of systems that are running in your landscape
If you want to use central user administration we recommend that you run it in a non-production
system If you do not have a central user administration yet you can for example realize it in the SAP
Solution Manager system
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3956
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
522 Examples for the Overall System Landscape of Shared Services
In this section we provide examples of how shared services can be set up depending on the system
landscape they are intended for The following examples aggregate the landscape aspects given in the
Use Cases section
NOTE
The following sections and the figure mostly do not show information about the life-cycle of
shared services For example you may also need a development and testquality assurance system
for SAP Solution Manager You should consider this aspect in addition to the information given
in this section based on your requirements
Small and MediumndashSized Customer Landscapes with Java
As you use Java productively for SAP NetWeaver PI 71 besides SAP Solution Manager you have to set
up additional components for optimal monitoring administration and support Solution Manager
Diagnostics and the central mode of SAP NetWeaver Administrator are already fully integrated into
SAP Solution Manager 70 as the central operations hub For SAP Process Integration you must also
set up SAP NetWeaver Administrator with a special role
We recommend that you do not install SAP Central Process Scheduling in the SAP Solution Manager
system You have to set up and operate the system which hosts your productive scheduler as a mission
critical system
In the SAP Solution Manager system you should set up a local System Landscape Directory in addition
to a central runtime System Landscape Directory This way you have a clear separation between your
management system (SAP Solution Manager) and managed systems in your landscape In addition
SAP Solution Manager then does not rely on a System Landscape Directory running in the production
environment For this setup configure the SLD data suppliers of your SAP Solution Manager system
to send data to the central runtime System Landscape Directory In addition configure automatic
bridge forwarding from your runtime System Landscape Directory to the local System Landscape
Directory For more information see the Planning Guide - System Landscape Directory
If you want to use a central system for Adobe Document Services we recommend that you install a
dedicated system for this purpose in your production environment For detailed information about
the sizing of the system for the different use cases see the Sizing Guide for Adobe Document Services at
SAP Service Marketplace at httpservicesapcomsizing Sizing Guidelines Solutions amp
Platform
We recommend that you start with this centralized SAP Solution Manager approach as depicted in the
following figure
5 System Landscape
52 Shared Services
4056 PUBLIC 2011-04-15
Figure 7 Single SAP Solution Manager Landscape
Large Customer Landscapes with Java
Large customers who have environments in their landscape that are large and distributed administered
by different groups or separated for security reasons can consider a distributed operations setup In
addition to the centralized setup described for small- and medium-sized customers above large
customers can put parts of the central management functions on extra hosts or systems for performance
or policy reasons You have the following options for a distributed setup
You may set up an extra system or client for Central User Administration (CUA)
The Change and Transport System (CTS) can run on an extra system However it is not
performance- or data-intensive
You may set up an extra system for central CCMS monitoring Depending on the customizing
and on the landscape size central CCMS may generate a lot of system load You can connect a
separate central CCMS to SAP Solution Manager for displaying alerts in the alert inbox of the System
Monitoring work center
You can use a separate SAP NetWeaver 70 system with usage type BI together with SAP Solution
Manager This may make sense with respect to the amount of landscape management data that is
stored for reporting purposes The amount of data strongly depends on the data granularity
storage time frame and landscape size
You can easily put Wily Introscope Enterprise Manager on an separate host
Other aspects described above for small- and medium-customers (such as the setup of the System
Landscape Directory) are also valid for large customers
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4156
523 Feature Details
This section provides further information about the features described above
5231 SAP Solution Manager
SAP provides you with SAP Solution Manager as the strategic application management platform and
to enable the collaboration between you and SAP You need to install at least one productive SAP
Solution Manager in your system landscape To ensure the availability of this application management
platform an SAP Solution Manager system is technically required to install or upgrade to SAP
NetWeaver 70 or higher If you are already using SAP Solution Manager you can also use it to manage
the solution you build with SAP NetWeaver In this case we highly recommend that you update SAP
Solution Manager to the latest version
As of SAP Solution Manager 70 SP15 you can use the newly created work centers
NOTE
During the SAP system installation or upgrade process you are prompted to enter the SAP
Solution Manager key An SAP Solution Manager system is required to generate this key Without
this key the installation or upgrade process cannot continue
You may generate all needed keys for your entire system landscape (development quality
assurance and production system) in one SAP Solution Manager system In case you plan to install
several solution landscapes (for example in different countries) one SAP Solution Manager
system is still sufficient
For more information see SAP Note 805390
It is possible to install multiple SAP Solution Managers If you do so they should host separate business
solutions
If you want to reduce the risk of unavailability you should not install SAP Solution Manager as a central
component Instead you can operate a 2-system-landscape with both a test and production
environment of SAP Solution Manager (especially if you are using time-critical functions like Support
Desk) If you also develop your own content a 3-system-landscape with a development test and
production environment is recommended
For more information about SAP Solution Manager see the following table
Topic Where to Find More Information
System infrastructure scenarios installation and configuration of SAP Solution Manager
Master Guide ndash SAP Solution Manager available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution ManagerltReleasegt
Benefits and usage scenarios SAP Solution Manager ndash Learning Maps available on SAP Service Marketplace at http
5 System Landscape
52 Shared Services
4256 PUBLIC 2011-04-15
Topic Where to Find More Informationservicesapcomrkt-solman or https
servicesapcomsolutionmanager
Additional information See SAP Service Marketplace at http
servicesapcomsolutionmanager
5232 Solution Manager Diagnostics
Solution Manager Diagnostics provides efficient and safe root-cause analysis of incidents in customer
solutions powered by SAP NetWeaver It can help monitor on operating systems databases Java
application activities performance and logs It also supports the reporting of software and
configuration changes that can lead to malfunctions and errors
You must run one Solution Manager Diagnostics within your SAP solution landscape if you run
applications based on SAP NetWeaver systems with usage type AS Java Agents are responsible for
delivering the data from all productive hosts within your system landscape to the Solution Manager
Diagnostics system
CAUTION
SAP Support performs root-cause analysis on incoming incidents with Solution Manager
Diagnostics Not installing and configuring this support infrastructure results in a dramatically
reduced service level
Solution Manager Diagnostics is fully integrated into SAP Solution Manager 70
Solution Manager Diagnostics also contains Wily Introscope (Display Server and Agent part) for
measuring performance as well as to troubleshoot problems of Non-ABAP applications Wily Introscope
is heavily used for troubleshooting applications running on AS Java
SAP has signed a distribution agreement for Wily Introscope SAP customers are allowed to use this
tool in a preconfigured way
For more information about Solution Manager Diagnostics and an FAQ list see SAP Service Marketplace
at httpservicesapcomdiagnostics
5233 System Landscape Directory
The System Landscape Directory (SLD) of SAP NetWeaver is the central directory of system landscape
information relevant for the management of your software life-cycle
NOTE
Note that the abbreviation SLD is not intended to define a product since the System Landscape
Directory is part of SAP NetWeaver This abbreviation is solely intended to improve readability
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4356
The System Landscape Directory contains a description of your system landscape (that is software
components that are currently installed) and a repository of software components that can
theoretically be installed in your landscape (such as the software components available from SAP)
Since this data gets updated automatically the System Landscape Directory provides reliable and up-
to-date system landscape information with as little effort for you as possible In this way the System
Landscape Directory acts as a central information provider for SAP and third-party tools that use this
data to deliver the services you need to keep your landscape up and running
For the System Landscape Directory as part of an SAP NetWeaver PI 71 landscape consider the following
aspects
Part of SAP NetWeaver PI 71 is a new version of the System Landscape Directory It is automatically
included in every SAP NetWeaver 71 system with usage type AS Java It offers enhanced functions
such as a full automatic synchronization mechanism for all data stored in it That is both data
delivered by data suppliers and data entered or changed manually in the System Landscape
Directory can be synchronized automatically This synchronization offers the following
A fully automated mechanism so no user interaction is required and conflicts are resolved
automatically
Asynchronous propagation of information so some nodes may be down temporarily
Communication over HTTP protocol
Uni- and bi-directional synchronization
Depending on your use case the full automatic synchronization could significantly reduce manual
synchronization effort
For SAP NetWeaver PI 71 the configuration of the system landscape directory and its data suppliers
is already included in the standard implementation procedure with SAPinst For existing systems
you only have to perform some quick and easy configuration actions to start operating the system
landscape directory server in an AS Java system
For SAP NetWeaver PI 71 you have the following options concerning SLD
Option 1
Run SAP NetWeaver PI 71 against an existing SLD running on SAP NetWeaver 70 We only
recommend this for upgrades from SAP NetWeaver 70 if you have a central SLD in operation
not running on one of your PI systems
Option 2
Use the SLD included in an SAP NetWeaver PI 71 system We recommend this option for new
installations and upgrades from older releases than SAP NetWeaver 70 due to the enhanced
functions and improved performance of SLD 71
NOTE
If you already have a central SLD running on SAP NetWeaver 70 in operation you could run
two SLD versions in parallel ndash SLD running on SAP NetWeaver 71 for your PI systems and
SLD running on SAP NetWeaver 70 for all other systemsuse cases This way your SAP
5 System Landscape
52 Shared Services
4456 PUBLIC 2011-04-15
NetWeaver PI 71 systems would benefit from the new features while it would be easy to set
up and operate such an SLD landscape For this purpose you could use the new fully
automatic synchronization This feature enables the automatic forwarding of all SLD data
from an SLD running on SAP NetWeaver 70 to an SLD running on SAP NetWeaver 71 As a
result there is no need to adapt most existing systems as their SLD data suppliers could still
send their data to the central SLD In brief the following steps would be required
1 Put SLD in a PI system into operation (part of standard implementation procedure)
2 Configure PI systems to use the new SLD (part of standard implementation procedure
for new PI systems)
3 Set up the fully automatic synchronization from your old SLD to your new SLD
As soon as an upgrade or an installation of a standalone AS Java 71 system is available you
could move your central SLD also to SAP NetWeaver 71 Then you could optionally shift
your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems
Figure 8
We recommend that you use a Domain Name System (DNS) alias so that you are able to switch to
another System Landscape Directory easily For example if customers build a new landscape they
normally start with a sandbox environment Over time more and more environments are set up
Once the production environment is in place move the System Landscape Directory there To do
this you can configure a new System Landscape Directory in the production environment
synchronize it with the old System Landscape directory and switch to the new one
Topology
Apart from the considerations above the System Landscape Directory offers several topology options
with different grades of availability at the expense of low administration and operation effort There is
no generic rule therefore on how to set up a System Landscape Directory in your system landscape
To find the topology and synchronization strategy for the System Landscape Directory that fits your
requirements concerning the System Landscape Directory availability (and hence the availability of
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4556
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
services using semantic-rich classification systems The Services Registry is part of Application Server
Java (AS Java)
31 Installable Software Units
SAP NetWeaver comprises the following three types of installable software units
Systems that are configured for a specific purpose as indicated by one or more usage types
Standalone engines that provide one specific (server) function in combination with one or more
SAP NetWeaver PI systems
Clients used by (many) people from their local front-end PC to access functions offered by systems
of SAP NetWeaver PI or standalone engines in the system landscape
In the following sections you can find more details about the software units The figure below provides
and overview of the software units
Figure 2 Installable Software Units for SAP NetWeaver PI
For this and other figures in this guide the following legend applies
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1556
Figure 3 Legend
311 Systems with Usage Types
SAP systems are the main building blocks of SAP NetWeaver They are identified by unique SAP system
IDs (SAPSIDs) and configured for a certain purpose as indicated by usage types Usage types have the
following characteristics
They are a structuring element for SAP software on a technical level
Usage Types determine the intended purpose of a system and the role it plays in a given (distributed)
use case
They are realized by installing and configuring a collection of software components
They allow a logical view of the technology platform SAP NetWeaver PI
A usage type may require other usage types in the same system to operate
They can also be run in the same system together with other usage types that are not a prerequisite
How SAP NetWeaver Systems are Used
The following sections describe the usage types and their dependencies for SAP NetWeaver PI
Application Server ABAP (AS ABAP)
Purpose
AS ABAP is used to provide the ABAP foundation of SAP NetWeaver PI
Application Server ABAP provides a complete development and runtime environment for ABAP-based
applications It is optimized for the development of highly scalable business applications The ABAP
development and runtime environment makes it possible to develop complex business applications
3 SAP NetWeaver PI Overview
31 Installable Software Units
1656 PUBLIC 2011-04-15
without having to worry explicitly about technical details such as process or memory administration
multi-user capability database connections or similar issues These are provided in the basis services or
are integrated directly in the ABAP runtime The application development is similarly independent of
the underlying platform The application server decouples the application coding completely from the
operating system and database that are used
Dependencies
AS ABAP can be combined optionally with other usage types in one system
Application Server Java (AS Java)
Purpose
AS Java is used to provide the Java foundation of SAP NetWeaver PI using the Java Engine a Java EE-
compliant application server for running enterprise applications In addition to the pure Java EE
standard technologies the Java Engine implements complementary technologies such as Web Dynpro
or Web Services that are targeted at supporting large-scale real-business application development
projects
Dependencies
AS Java can be combined optionally with other usage types in one system
Process Integration (PI)
Purpose
PI consists of core components that model design automate and integrate processes in one or more
application systems For the integration of internal and cross-company processes PI is used to
incorporate all the functions of what was formerly known as Exchange Infrastructure (XI) In addition
PI contains core components for Business Process Management for application-embedded and
application-unbounded processes
The Advanced Adapter Engine is also part of usage type PI You use Advanced Adapter Engine to connect
to SAP systems (RFC adapter) and external systems You use the various adapters in Advanced Adapter
Engine to convert XML- and HTTP-based messages to the specific protocol and format required by
these systems and the other way around You can use the Advanced Adapter Engine that is part of
your PI system as a central Advanced Adapter Engine Optionally (for performance reasons) you can
install a non-central Advanced Adapter Engine [page 19] separately as a system with AS Java and parts of the
usage type PI on a separate host
Dependencies
PI requires AS ABAP and AS Java as prerequisites in the same system
For installing PI it is mandatory to have a dedicated PI system This applies to development quality
and production landscapes It is a prerequisite that no other system in your system landscape has a
higher release and enhancement package level than the PI system If you want to upgrade or install an
application in your system landscape you first have to make sure that the current release and
enhancement package level of the PI system is on the same level - if required you have to upgrade the
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1756
PI system first to the new or a higher release In a dedicated PI system this can be accomplished with a
minimum of downtime Also the PI system would not be affected by the downtime of other usage
types running in the same system
Configuration of Systems with Usage Types
Configuration information is available in the installation guides the configuration wizard and SAP
Solution Manager
In the Installation Guide ndash SAP NetWeaver PI 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt you find
initial technical configuration tasks This guide also informs you about how you can run the
configuration wizard and how you can access the configuration information in SAP Solution
Manager
For certain usage types configuration tasks can be applied by the configuration wizard after the
installation To do this you start the configuration wizard from SAP NetWeaver Administrator
The configuration steps for systems with usage types required for an use case are accessible through
SAP Solution Manager
To be able to use SAP Solution Manager for the configuration tasks you have to import the latest
SAP Solution Manager Implementation Content (Add-On ST-ICO) that is available for your SAP
Solution Manager release For more information see SAP Note 631042 (Release strategy for Implementation
Content (ST-ICO))
SAP Solution Manager Implementation Content is available on SAP Service Marketplace at
httpservicesapcomswdc Installations amp Upgrades Entry by Application Component SAP
Technology Components SAP Solution Manager ltReleasegt Content ST-ICO
In SAP Solution Manager you create a project and a project structure In the configuration phase
you select configuration structures with pre-delivered SAP content for your project You can find
the following different types of configuration tasks in SAP Solution Manager
Mandatory configuration tasks All configuration tasks that are mandatory for the standalone
engine or usage type
Optional configuration tasks Configuration tasks for areas where customers need to decide
if they want to use these functions (for example high availability or security settings)
Additional functions ndash configuration tasks Configuration tasks for functional units that are
used in certain use cases only
A marked checkbox in front of the configuration tasks indicates those configuration tasks that are
relevant for the use case you have chosen To configure ABAP systems SAP Solution Manager
offers executable configuration files (IMG activities)
For information about using SAP Solution Manager Content and creating a configuration guide
see the following documentation
httphelpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Implementing
and Upgrading SAP Solutions Configuration
3 SAP NetWeaver PI Overview
31 Installable Software Units
1856 PUBLIC 2011-04-15
How to Create a Configuration Guide using SAP Solution Manager available at http
servicesapcomsolutionmanager Media Library How-To Documents
Restrictions for Systems with Multiple Usage Types
If you have one system with multiple usage types be aware that we do not provide standard tools
to separate these usage types and distribute them to multiple systems at a later stage For example
if you have a system with usage types A and B you are not able to migrate it with SAP standard
tools into two systems one with usage type A only and the other with usage type B only
In addition we do not provide standard tools to merge multiple systems with different usage types
into one system with multiple usage types at a later stage
If you want to perform these tasks you require specific project support
The following figure shows that SAP standard system copy and migration tools do not support
you in separating or merging systems with usage types
Figure 4 No Support for Merging or Separating Systems with Usage Types
Although you can use one system for multiple usage types client restrictions apply for usage type
PI PI requires a dedicated client due to special PI requirements concerning the client pipeline
Whereas application client pipelines only send and receive messages the central PI pipeline can
also map messages to different formats before sending them
312 Standalone Engines
Standalone engines of SAP NetWeaver are additional installable software units They do not work as
full-blown systems of SAP NetWeaver but as standalone engines that provide a specific (server) function
in combination with one or more SAP NetWeaver systems
Standalone engines are not part of a usage type They do not run on AS ABAP or AS Java
The standalone engines that are available for SAP NetWeaver Process Integration are described in the
following
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1956
Gateway
It is possible to install an SAP instance of an SAP NetWeaver system based exclusively on a standalone
gateway This type of instance does not contain normal work process types (dialog background update
enqueue or spool) Only the gateway process (gwrd) is started If there is an SNA connection to an R
2 system gateway work processes (gwwp) are also started
SAP Conversion Agent by Informatica
SAP Conversion Agent by Informatica is a data conversion tool that enables you to create interfaces
between any data formats and XML-based systems SAP Conversion Agent can convert unstructured
semi-structured and structured formats to XML and the other way around The Conversion Agent
comprises the Conversion Agent Studio and the Conversion Agent Engine In the Conversion Agent
Studio you can develop and configure data conversions The Conversion Agent Engine executes the
data conversions
Search and Classification (TREX)
You can use Search and Classification with SAP NetWeaver PI to search for messages that were previously
indexed Message search using index provides additional methods of searching for specific messages In
addition to static header attributes you can also use adapter-specific message attributes and data from
the message payload for the search A requirement of this however is that the messages are indexed
first You can apply the index-based message search to one or all indexed components of an integration
landscape (domain) Integration Server Adapter Engines and ABAP business systems
For more information see the SAP Library [page 12] at Administratorrsquos Guide Technical Operations for SAP
NetWeaver Administration of SAP NetWeaver Systems Administering PI (Process Integration) Monitoring Index
Administration
Web Dispatcher
The Web Dispatcher lies between the Internet and your SAP system It is the entry point for HTTP(s)
requests into your system which consists of one or more SAP NetWeaver application servers As a
software web switch the Web dispatcher can reject connections or accept them When it accepts a
connection it balances the load to ensure an even distribution across the servers
You can use the Web dispatcher in ABAPJava systems and in pure Java systems as well as in pure ABAP
systems
It is also beneficial to use the Web Dispatcher if you do not need security functions (entry point in the
demilitarized zone (DMZ) SSL URL filtering) but you simply want to balance the load between
multiple SAP NetWeaver Application Server instances
Since Web Dispatcher is optional for every SAP system it is not contained in the system landscape and
the implementation sequence of the use case in this documentation
For more information see the SAP Library [page 12] at Function Oriented View Application Server Infrastructure
SAP Web Dispatcher
3 SAP NetWeaver PI Overview
31 Installable Software Units
2056 PUBLIC 2011-04-15
Advanced Adapter Engine
You use the Advanced Adapter Engine to connect to SAP systems (RFC adapter) and external systems
You use the various adapters in Advanced Adapter Engine to convert XML- and HTTP-based messages
to the specific protocol and format required by these systems and the other way around For specific
senderreceiver combinations messages can be processed without invoking the central Integration
Engine In principle you connect external systems using the adapters that are installed centrally or
non-centrally in Advanced Adapter Engine You can use the Advanced Adapter Engine that is part of
your PI system as a central Advanced Adapter Engine Optionally (for performance reasons) you can
install a non-central Advanced Adapter Engine separately as a system with AS Java and parts of the
usage type PI on a separate host
Adapter Engine (Java SE)
Adapter Engine (Java SE) is a separate software unit You can use it only if you have SAP NetWeaver
systems with usage type PI in your system landscape It has to be installed manually You use the Adapter
Engine (Java SE) to connect to external systems Using the various adapters in the Adapter Engine (Java
SE) XML and HTTP-based messages can be converted to the specific protocol and format required by
such systems and the other way around The Adapter Engine (Java SE) only provides some of these
adapters as a standalone version with restricted functions for operating systems that do not support
SAP NetWeaver PI 71 but that have at least a Java Runtime Environment 50 Therefore you should
use the Adapter Engine (Java SE) only if the platform prerequisites do not allow you to use the Advanced
Adapter Engine
SAP Partner Connectivity Kit
SAP Partner Connectivity Kit (PCK) runs on AS Java with parts of the usage type PI It enables a system
of a smaller company or subsidiary that does not run SAP NetWeaver PI to connect to your SAP
NetWeaver systems
313 Clients
Clients are additional installable programs or tools They reside either on local front-end PCs accessed
by users or on back-end systems where they act as client programs within an SAP NetWeaver system
landscape
The clients that you can use with SAP NetWeaver Process Integration are described in the following
sections
SAP GUI
NOTE
We recommend that you use the following versionsI
SAP GUI for Windows 710 (or higher) with the latest patch level
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 2156
SAP GUI for Java 710 (or higher) with the latest revision
The integrated SAP ITS 710
For more information about the SAP GUI family see SAP Service Marketplace at http
servicesapcomsapgui
SAP offers three different client applications for accessing ABAP applications in SAP systems (such as
SAP NetWeaver systems with usage type AS ABAP) This SAP GUI family consists of
SAP GUI for HTML
SAP GUI for HTML is based on the SAP integrated Internet Transaction Server (ITS) which is
included in the installation of SAP NetWeaver systems as of SAP NetWeaver 2004 On the client
side only a suitable browser (such as Internet Explorer 70 or Firefox 20) and a virtual machine are
required SAP ITS 620 is not compatible with SAP NetWeaver 71
SAP GUI for the Java environment (SAP GUI for Java)
SAP GUI for Java is a generic SAP GUI that covers a variety of platforms
For more information about the installation of SAP GUI for Java see the documentation Installation
Guide ndash SAP Front End
SAP GUI for the Windows environment (SAP GUI for Windows)
SAP GUI for Windows is SAPs universal client for accessing all SAP applications built on ABAP
technology It is available on the Microsoft Windows platform only and offers the broadest feature
set of all members of the SAP GUI family
For more information about the installation of SAP GUI for Windows see the Installation Guide ndash
SAP Front End
SAP NetWeaver Developer Studio
The SAP NetWeaver Developer Studio is SAPrsquos Integrated Development Environment (IDE) for Java
and is based on the open-source tools framework Eclipse 33 With the SAP NetWeaver Developer Studio
you can develop Java EE 5 applications from scratch using the built-in support for new technologies
such as EJB 30 and JSF 12
During the installation of the SAP NetWeaver Developer Studio several features are offered for
installation For SAP NetWeaver PI 71 only the following features are relevant
SAP NetWeaver Developer Studio Platform
SAP NetWeaver Developer Studio Java EE
NOTE
If you want to use one of the other features you need SAP NetWeaver Composition Environment
and a corresponding developers licence
For more information about the installation of SAP NetWeaver Developer Studio see the Installation
Guide ndash SAP NetWeaver Developer Studio 71 or Installation Guide ndash SAP NetWeaver Developer Studio 71 Including
Enhancement Package 1
3 SAP NetWeaver PI Overview
31 Installable Software Units
2256 PUBLIC 2011-04-15
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
SAP enhancement packages are a new way of delivering new functions for SAP NetWeaver This allows
a clear separation between the delivery of new functions on the one hand and corrections legal changes
and security updates on the other hand (in Support Package stacks) SAP enhancement packages are
cumulative an enhancement package always contains the functions of the corresponding predecessor
enhancement packages
Enhancement packages are maintained by their own Support Packages while the main release is in
maintenance
Benefits
SAP enhancement packages offer the following benefits
You have reduced effort for testing and no effort for training when applying Support Packages as
new features are only shipped with enhancement packages
Adding new functions between releases becomes predictable and controllable
New functions can be added successively in small steps There is no need to fully upgrade your
system to get new functions
You have minimal training effort when applying an enhancement package because existing
functions are not replaced
Implementation
There are the following ways to get an SAP NetWeaver system with the release level of SAP enhancement
package 1 for SAP NetWeaver Process Integration 71
New installation of SAP NetWeaver PI 71 including enhancement package 1 using the standard
installation tool SAPinst
Upgrade of an existing SAP NetWeaver system from a release lower than SAP NetWeaver PI 71 to
SAP NetWeaver PI 71 including enhancement package 1 For this you use the upgrade programs
SAPup (for ABAP) and SAPJup (for Java)
Installation of the enhancement package on an existing SAP NetWeaver PI 71 system
For this you use the Software Update Manager (SUM) The Software Update Manager evolved
from the previously used SAP Enhancement Package Installer The tool has been renamed to reflect
its broader use for example you can also use it for applying Support Package Stacks to your system
On the ABAP side the Software Update Manager uses a system cloning and switch procedure for
installing enhancement packages It installs a copy of the system the shadow system parallel to
the original system This shadow system is used to update the relevant software components and
to install the additional components while the original system is still in production operation At
a certain point during downtime the switch to the new system is made and afterwards any parts
of the original system that are no longer needed are deleted The enhancement package installation
in a Java system uses a deploy-based procedure that is no shadow system is used The Software
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2011-04-15 PUBLIC 2356
Update Manager requires a stack configuration file (xml file) as input file for the enhancement
package installation procedure This file lists all the packages that are to be installed in your systems
The stack configuration file is generated when you download the required packages
As the Software Update Manager is updated regularly we recommend to always use the latest
version It is delivered as part of the SL toolset For more information see http
servicesapcomsltoolset
For an overview of all required steps for the enhancement package installation process and
corresponding documents see Process Overview Installation of Enhancement Package 1 on an Existing SAP
Netweaver PI 71 System [page 28]
Content of SAP Enhancement Package 1 for SAP NetWeaver PI 71
With enhancement package 1 for SAP NetWeaver PI 71 new features are introduced and some existing
are changed The following is a selection of some of the most important enhancements
Enhanced design and modelling options in the Enterprise Services Repository
New services registry
Support for new Web services standard (Web Services Reliable Messaging)
New modules for the Advanced Adapter Engine
Use of shared memory of the ABAP Application Server for message processing
For more information about the changes see SAP Library [page 12] at Whatacutes new in SAP NetWeaver PI 71
ndash Release Notes
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2456 PUBLIC 2011-04-15
4 SOA-Based Integration Use Case
41 Overview
You can use SOA-based integration to set up the communication between service providers and service
consumers in both application-to-application and business-to-business scenarios and to execute
operate and monitor the communication at runtime SOA-based integration covers both direct (point-
to-point) as well as mediated (via an Integration Server) communication between service providers and
service consumers
The use case spans the whole life cycle of a SOA-based integration scenario including
Scenario modeling and service design in the Enterprise Services Repository
Implementation of the service provider and consumer in the back-end systems
Configuration and finally execution monitoring and operation of the integration scenario
For scenarios using Integration Server or broker-based communication the configuration of the
different connectivity options (for example SOAP RFC Web Services Industry standards and JDBC)
and their enhancements is covered
For more information see the following documents
Service-Enabling with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdnsoa-modeling
Getting Started
Service-Enabling a Legacy Application with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdn
soa-servicebus Getting Started
In the following you will find information about the installation of the involved software units
42 System Landscape
The following figure shows the system landscape for this use case
4 SOA-Based Integration Use Case
41 Overview
2011-04-15 PUBLIC 2556
Figure 5 SOA-Based Integration
It is mandatory to have a dedicated PI system This applies to development quality and production
landscapes
For PI it is a prerequisite that no other system in your system landscape has a higher release than
the PI system For exceptions to this rule see SAP Note 1043047 For example SAP XI 30 is compatible
with SAP NetWeaver 640 and 70 application systems since the same XI protocol is used Apart
from these exceptions if you want to upgrade or install an application in your system landscape
you first have to make sure that the PI system is on the same release level If required you have to
upgrade the PI system first to the new or a higher release
CAUTION
Although it should be technically possible to run an application system with a higher release
than your PI system in your system landscape this is not supported by SAP (apart from the
exceptions listed in SAP Note 1043047) Therefore you run such a landscape at your own risk
You can use the Advanced Adapter Engine that is part of your PI system as a central Advanced
Adapter Engine
Adapter Engine (Java SE) can be installed in a non-SAP Java environment However it only hosts
a subset of the adapter functionality is only supported for compatibility reasons and should be
used only if this is a precondition in your environment
Optionally you can use the Change Management Service (CMS) of an SAP NetWeaver 70 system
with usage type DI to transport design objects and repository objects For more information see
the SAP Library [page 12] at Administratoracutes Guide Technical Operations for SAP NetWeaver Administration
of SAP NetWeaver Systems PI (Process Integration) Software Logistics Transporting ESR Content and Objects
of Integration Directory PI Transports Using the Change Management Service (CMS)
Smaller business partners or subsidiaries that do not run SAP NetWeaver install SAP Partner
Connectivity Kit in their system landscape SAP Partner Connectivity Kit enables XML document
4 SOA-Based Integration Use Case
42 System Landscape
2656 PUBLIC 2011-04-15
exchange between your SAP NetWeaver systems and the partner systems Since SAP Partner
Connectivity Kit gets installed in their system landscape it is not shown in the system landscape
figure above
The AS ABAP system acts as an application and service provider For Java Web Services you also
require AS Java In addition you require SAP NetWeaver Developer Studio on the client side as a
development environment
The Web service client can be either an SAP or a non-SAP application For example an AS ABAP
system or a Web browser could act as application or service consumer
You can install SAP Conversion Agent by Informatica in the system with usage type PI or on a host
where SAP Partner Connectivity Kit is installed or on a host where neither usage type PI nor SAP
Partner Connectivity Kit is installed
43 Implementation Sequence
Procedure
To install this use case perform the steps listed in the following table
StepAction[Corresponding Documentation] Remarks
1 Make sure that you have performed the preparation steps You have planned your system landscape [page 33]
(that is you have decided how many systems you require how you want to use each of these systems and which standalone engines and clients you require)
With the help of your hardware partner you have mapped your systems and standalone engines to properly sized hosts
You have planned and installed shared services [page 35]
2 Installation of system with usage type PI (includes the installation of AS ABAP and AS Java)
NOTE
For usage type PI a Unicode installation is mandatory
[Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt]
If you want to use the features of enhancement package 1 use the direct installation of SAP NetWeaver PI 71 including enhancement package 1
Make sure that you perform the configuration steps as described in the installation guide For certain usage types configuration tasks can be applied by the configuration wizard These configuration tasks as well as any additional configuration steps for your use case are listed in SAP Solution Manager For more information
4 SOA-Based Integration Use Case
43 Implementation Sequence
2011-04-15 PUBLIC 2756
StepAction[Corresponding Documentation] Remarks
see the Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt
3 Install the Adapter Engine (Java SE) engines if required[Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
4 To integrate small business partners and subsidiaries the business partners or subsidiaries install SAP Partner Connectivity Kit running on AS Java with parts of usage type PI in the business partners or subsidiarys system landscape[Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
5 Install SAP Conversion Agent by Informatica if required[SAP Library [page 12] at Function-Oriented View Process Integration SAP Conversion Agent by Informatica Deploying and Using Conversion Agent ]
6 Installation of clients SAP GUI
[Installation Guide ndash SAP Front End]
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
The process sequences give a comprehensive overview of the steps relevant for the enhancement
package installation on an existing SAP NetWeaver PI 71 system
The process sequence is divided into a planning phase and an implementation phase Each step in both
phases contains references to the corresponding documentation to ensure that you can easily find the
information you need
Process
NOTE
To download the enhancement package files and required Support Packages you require the SAP
Solution Manager Maintenance Optimizer You have the following options
Manual Selection
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2856 PUBLIC 2011-04-15
You manually select the required files from SAP Service Marketplace at http
servicesapcomswdc using the SP Stack Application You use the Maintenance Optimize
only to approve the packages which is a prerequisite for the download
Automatic Calculation
The Maintenance Optimizer supports the download of a consistent queue that includes all
necessary Support Packages and enhancement packages In addition SAP Solution Manager
calculates a valid import queue for the selected SAP system and generates the enhancement
package stack configuration file that you require for the installation
As a prerequisite the system that you want to update needs to be maintained correctly in
SAP Solution Manager System Landscape As the Maintenance Optimizer uses this data for
the calculation it is crucial that the data is up-to-date In addition the SAP Solution Manager
system requires a Minimum Support Package level (see below)
Planing PhaseStep Description Documentation
Hardware amp Software Prerequisites
Check which platforms are supported for your target release (OSDB dependencies)
Product Availability Matrix (PAM) at httpservicesapcompam
Check which hardware sizing is required for your target release
Sizing information at httpservicesapcomsizing
Solution Manager Prerequisites
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of the required software packages you have to make sure that your SAP Solution Manager system has the required Support Package levelAt least SAP Solution Manager 70 EHP1 Support Package Stack 17 is required We recommend to use SAP Solution Manager 70 EHP1 Support Package Stack 23Check if you need to do an update or upgrade of your SAP Solution ManagerMake sure that you run the guided procedure SOLMAN_SETUP after every installation or update of SAP Solution Manager and that it completes successfully
For upgrades from source release SAP Solution Manager 31 and 32Upgrade Guide ndash SAP Solution Manager 70 incl Enhancement Package 1For updates from SAP Solution Manager 70Update Guide SAP Enhancement Package 1 for SAP Solution Manager 70Follow-up activities after an Support Package Stack update or enhancement package updateSolution Operations Guide ndash SAP Solution Manager 70 EHP1 section Software Change Management All guides are available at http
servicesapcom instguides SAP Components SAP Solution Manager -gt Release 70 EHP 1
Implementation PhaseStep Description Documentation
1Solution Manager Preparation
Configure the SAP Solution Manager Maintenance Optimizer
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of software packages make sure your
Configuration of Maintenance Optimizer http
helpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Change Request Management and Change ControlMaintenance Optimizer
Prerequisites
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 2956
Implementation PhaseStep Description Documentation
system landscape data in SAP Solution Manager is maintained correctlyLandscape Verification 10 which is an add-on to SAP Solution Manager can support you in maintaining your system landscape data The use of this tool is optional
Landscape Verification http
wwwsdnsapcom irj
sdn alm-update-
management link Landscape Verification under Related Areas on Upgrade and Update Management (in the right column)
SAP Note 1468605 (Installation of Landscape Verification)
Maintaining System Landscape Information [page 47]Note that the information provided in this section is based on SAP Solution Manager 70 EHP1 SP23
2System Preparation
Prepare your system as described in the documentation for example perform OS DB specific preparations and the PI-specific preparations
Update Guide ndash Update of SAP Systems with Software Update Manager sections Planning and Preparation
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
3Software Download
Select and download the software packages in either of the following ways Automatic calculation Create
a maintenance transaction in the Maintenance Optimizer and choose the Calculate Files Automatically option
Manual Selection Create a maintenance transaction in the Maintenance Optimizer and choose the Select Files Manually option You then can select the files manually using the SP Stack application in SAP Service Marketplace
NOTE
You have to download the stack configuration file manually after you have selected all files in the SP Stack
httphelpsapcom SAP Solutions SAP Solution Manager
SAP Solution Manager 70 EHP1 ltSPgtChange Request Management and
Change Control Maintenance Optimizer Maintenance Procedure Scenarios
For information about the automatic calculation see Maintenance Transaction with Installation of an Enhancement PackageFor information about the manual selection and approval process see section Approve and Download Files in Download Basket
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
3056 PUBLIC 2011-04-15
Implementation PhaseStep Description Documentation
application Choose Generate Stack XML and save the file
4Enhancement Package Installation
Run Software Update Manager to update your system with the selected software packages
Update Guide ndash Update of SAP Systems with Software Update Manager
5Follow-Up Steps
Perform technical and PI-specific follow-up activities after the enhancement package installation is done
Update Guide ndash Update of SAP Systems with Software Update Manager section Follow-Up Activities
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
6Configuration
Configure newly installed enhancement package functions using SAP Solution Manager content
See Systems with Usage Types [page 16] section Configuration of Systems with Usage Types
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 3156
This page is left blank for documents that are printed on both sides
5 System Landscape
51 Planning Your System Landscape
The installable software units that make up your system landscape depend on the functions that you
want to implement For information about the features see systems [page 16] standalone engines [page 19]
and clients [page 21]
In addition you have to determine the required shared services [page 35] (such as SAP Solution Manager
or SAP NetWeaver Administrator) that run on central systems in your system landscape and the
landscape aspects relevant for their implementation
In the following you will find general information that you should consider when planning your system
landscape
Sizing
You have to map systems and standalone engines to hosts after you have a clear picture of the following
Which systems and standalone engines you require
How many systems you require and how you want to use each of these systems
NOTE
No general guideline can be given for the sizing of your landscape since this relies heavily on your
requirements You should therefore perform this task together with your hardware partner and
your technical consultant
For information about sizing your systems you can use the following information sources
Your first point of reference is the Quick Sizer
SAP built the Quick Sizer as an online sizing questionnaire Internet application in close cooperation
with its hardware partners This tool delivers general sizing categories based on your volume load
estimates The results provide an objective basis for sizing independent of platform and
configuration
For more information see SAP Service Marketplace at
httpservicesapcomsizing for the SAP NetWeaver PI 71 sizing guide available under
Sizing Guidelines Business Suite amp Services
httpservicesapcomquicksizer for more information and access to the tool itself
Also consider the following important aspects concerning sizing
High availability
5 System Landscape
51 Planning Your System Landscape
2011-04-15 PUBLIC 3356
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Technical Infrastructure High Availability
Unicode
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Internationalization
Contact your hardware partner to find out the appropriate number of sized hosts
The platform-independent abstract results of the Quick Sizer can be used by any of our hardware
partners to create a concrete offer SAP itself does not make any hardware recommendations the
responsibility for sizing and detailed hardware configuration lies with the hardware partners
Figure 6 Example of Mapping of Systems and Standalone Engines to Three Hosts
NOTE
Optionally you could also distribute single systems to multiple hosts For example you could
decide to install the database instance of an SAP system on a separate host for performance
reasons or distribute other system instances to achieve high availability
To provide a mapping that fits your required functions and performance your hardware partner
and your technical consultant have to identify the number of required instances of SAP NetWeaver
find out how to distribute these instances to hosts and what functions will run on which instance
Therefore the hardware partner and the technical consultant have to consider many different
aspects such as
Number of required SAPS (SAP Application Benchmark Performance Standard) for each
system (provided by Quick Sizer)
Landscape-relevant aspects concerning security For more information see the SAP Security
Guide in the SAP Library [page 12] at Administratoracutes Guide Security Guide
Landscape-relevant aspects concerning scalability high availability operation and software
life-cycle management
5 System Landscape
51 Planning Your System Landscape
3456 PUBLIC 2011-04-15
For more information about relevant aspects for the mapping of systems to hosts see the document
Technical Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
Scaling and Distribution Options
You may need to design your system landscape for a large number of users SAP NetWeaver PI offers
you different means of scalability The following list provides you with some examples
You could install multiple systems of one type and use them for different purposes
You could scale every system by installing dialog instances or by distributing the database instance
For more information about distribution options on the instance level see the Technical
Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
For every SAP system you could additionally install Web Dispatcher For more information see
the SAP Library [page 12] at FunctionndashOriented View Application Server Infrastructure SAP Web
Dispatcher
You could further distribute certain standalone engines ndash for example Search and Classification
(TREX) is based on a flexible architecture that supports a distributed installation For more
information see the Technical Infrastructure Guide ndash SAP NetWeaver PI 71 available in SAP Service
Marketplace at httpservicesapcominstallNWPI71
52 Shared Services
You normally run shared services on central systems in your system landscape The following features
could be used for SAP NetWeaver Process Integration to realize shared services
SAP Solution Manager
Used to implement train test maintain monitor control change and manage incidents of your
SAP solution system landscape (open end-to-end application management)
As of SAP Solution Manager (70) 40 Support Package 15 SAP Solution Manager has become the
platform for SAPs end-to-end solution operations strategy Functions for complete application
management has been combined with administrative tools and has been merged in newly created
role based work centers
NOTE
Be aware that you require an SAP Solution Manager system to install or upgrade to SAP
NetWeaver 70 and higher An SAP Solution Manager system is required to generate the SAP
Solution Manager key needed during the installation or upgrade process Without this key
the installation or upgrade process cannot continue
For SAP NetWeaver Process Integration you require SAP Solution Manager 70
For more information see SAP Note 805390
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3556
Solution Manager Diagnostics
An integral part of SAP Solution Manager that is running as a Java application on the Java stack of
SAP Solution Manager 70 Solution Manager Diagnostics is used to analyze the root cause of
incidents in your landscape in an efficient and safe way Before Go-Live Solution Manager
Diagnostics has to be set up and made accessible remotely
SAP NetWeaver Administrator
SAP NetWeaver Administrator is the central administration component which is used for
monitoring and administering Java applications It is included in SAP NetWeaver systems with AS
Java
SAP NetWeaver Administrator exists in the following flavors
A local mode which runs out of the box and which focuses on administrating the underlying
SAP NetWeaver AS Java
NOTE
For a SAP NetWeaver PI 71 it has a special role which you need to activate using a
configuation wizard
A central mode which has to be configured before use and which deals with the system
landscape management
SAP has decided to merge the central mode of SAP NetWeaver Administrator into the new work
centers available as of SAP Solution Manager 70 SP 15 Thus it can be used in an administrative
context together with non-Java-based administration tools Although the central mode of SAP
NetWeaver Administrator will be still available for some time SAP will not develop this tool any
further SAP focuses on optimizing the administrative work centers of SAP Solution Manager
instead
The local mode of SAP NetWeaver Administrator stays untouched It is available for current and
future releases of SAP NetWeaver
SAP Central Process Scheduling by Redwood
SAP Central Process Scheduling application by Redwood enables central job scheduling and job
monitoring of current and old releases of AS ABAP systems (as of Basis Release 31) This application
is fully integrated in SAP NetWeaver Depending on the business needs SAP business applications
are the initial trigger for scheduled activities You can now manage jobs and job chains conveniently
using a graphical user interface
System Landscape Directory
The System Landscape Directory is the central directory of system landscape information relevant
for the management of your software life-cycle It contains a description of your system landscape
(that is software components that are currently installed) and a repository of software components
that can theoretically be installed in your landscape (such as the software components available
from SAP)
Adaptive Computing Controller
5 System Landscape
52 Shared Services
3656 PUBLIC 2011-04-15
The Adaptive Computing Controller enables users to control an adaptive computing landscape
from a single point through observation operation and dynamic resource distribution With
adaptive computing hardware software and system services are able to adapt to changing business
needs In the Adaptive Computing Controller the run-time data of logical and physical landscapes
can be monitored application services can be startedstoppedrelocated and hardware resources
can be assigned to application services The operation can also be mass executed and be planned as
tasks to be executed
For more information about the installation of the Adaptive Computing Controller tool see the
document Installation Guide ndash Adaptive Computing Controller in SAP NetWeaver 71 available on SAP Service
Marketplace at httpservicesapcominstallNWPI71
For more information about Adaptive Computing in general see httpsdnsapcomirj
sdnadaptive
521 Use Cases
You can use the applications and tools described above for use cases that are normally performed
centrally The following sections describe these use cases
5211 End-to-End Solution Operations
Running business applications through their complete life-cycle is a challenge Therefore SAP has
started the Run SAP methodology for implementing End-to-End Solution Operations Based on a set
of SAP standards a roadmap and a package for training and certification Run SAP helps customers to
facilitate End-to-End Solution Operations
You can download the SAP standards for Solution Operations from SAP Service Marketplace at http
servicesapcomsupportstandards They describe roles customers typically have in their IT
environment For optimal role support SAP has grouped existing and new functions in SAP Solution
Manager work centers as of SAP Solution Manager 70 Support Package 15 Operations aspects are fully
covered by adding administrative functions for SAP NetWeaver as well Work centers are ABAP Web
Dynpro-based applications They offer the following advantages
Easy to use similar look and feel
Context transfer while jumping from one work center into another
Logical grouping of tools for a certain area
Simple authorization concept
Easy to expand
Each IT role belongs to one or more work centers For instance the Technical Administrator IT role is
covered by the work centers for System Monitoring System Administration and Landscape Management
The following work centers are available
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3756
Business Process Operations
Change Management
Root Cause Analysis
Implementation Upgrade
Incident Management
Test Management
Job Management
System Landscape Management
Solution Documentation Assistant
SAP Engagement and Service Delivery
SAP Solution Manager Administration
System Administration
System Monitoring
My Home is the central point of access to all important data of almost all work centers in SAP Solution
Manager
5212 Support Infrastructure
A key requirement for effective support of IT solutions is the ability to perform root cause analysis with
speed and efficiency
With SAP Solution Manager SAP has long had an infrastructure in place for its ABAP applications that
efficiently supports SAP solutions This helps ensure the high availability and smooth running of
business processes For more information see the SAP Solution Manager section
With Solution Manager Diagnostics this knowledge has been extended to Java applications If for
example homegrown Java applications cause instability Solution Manager Diagnostics helps trace the
cause to eradicate the problem rapidly Solution Manager Diagnostics is fully integrated into SAP
Solution Manager 70 Solution Manager Diagnostics also contains two third-party tools CArsquos Wily
Introscopereg for measuring performance as well as troubleshooting problems of the Java EE Engine
and applications running on it and Mercury Loadrunnerreg which enables SAP Support to produce a
defined load in the SAP solution landscape remotely For more information see Solution Manager
Diagnostics [page 43]
The support infrastructure provides SAP Support with safe access to your productive landscape for safe
root cause analysis so ensuring that SAP Support does not change your landscape inadvertently You
require a support infrastructure to run SAP NetWeaver
The following figure shows the overall infrastructure including SAP NetWeaver administration tools
that are used by administrators or operators at the customer site
5 System Landscape
52 Shared Services
3856 PUBLIC 2011-04-15
Landscape Aspects
If you use SAP NetWeaver Process Integration 71 productively besides SAP Solution Manager (as a
central support platform) you have to set up Solution Manager Diagnostics for supportability reasons
Implementation Sequence
For information about the implementation of the support infrastructure see the document Master
Guide ndash SAP Solution Manager 70 available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution Manager ltReleasegt
5213 Collection of Landscape Data
Amongst other applications and services the support infrastructure and the SAP NetWeaver
administration tools rely on system landscape data
For SAP NetWeaver PI 71 you have to run non-ABAP components in your solution landscape
Therefore the System Landscape Directory is mandatory The landscape data that is automatically
gathered by the System Landscape Directory is replicated to SAP Solution Manager There are several
topology options for the System Landscape Directory They offer different grades of availability
administration and operation effort
For more information see the System Landscape Directory section
5214 Authentication and Single Sign-On
Before implementing your system landscape plan how to implement authentication and how to
integrate different systems into a Single Sign-On landscape Single Sign-On reduces complexity for end
users saving them valuable time while also reducing administration effort for resetting passwords
thereby contributing to TCO reduction
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
5215 Integrated User and Access Management
In a system landscape containing a combination of ABAP and Java components we recommend that
you integrate your user and access management so that you can use the same user data across different
systems administer this data centrally and control access to data SAPs mature fine-grained
authorization concept allows detailed control of access rights SAP NetWeaver provides both ABAP and
Java-based user management solutions The user management solution that you use to administer
your user data depends on factors such as the type of systems that are running in your landscape
If you want to use central user administration we recommend that you run it in a non-production
system If you do not have a central user administration yet you can for example realize it in the SAP
Solution Manager system
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3956
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
522 Examples for the Overall System Landscape of Shared Services
In this section we provide examples of how shared services can be set up depending on the system
landscape they are intended for The following examples aggregate the landscape aspects given in the
Use Cases section
NOTE
The following sections and the figure mostly do not show information about the life-cycle of
shared services For example you may also need a development and testquality assurance system
for SAP Solution Manager You should consider this aspect in addition to the information given
in this section based on your requirements
Small and MediumndashSized Customer Landscapes with Java
As you use Java productively for SAP NetWeaver PI 71 besides SAP Solution Manager you have to set
up additional components for optimal monitoring administration and support Solution Manager
Diagnostics and the central mode of SAP NetWeaver Administrator are already fully integrated into
SAP Solution Manager 70 as the central operations hub For SAP Process Integration you must also
set up SAP NetWeaver Administrator with a special role
We recommend that you do not install SAP Central Process Scheduling in the SAP Solution Manager
system You have to set up and operate the system which hosts your productive scheduler as a mission
critical system
In the SAP Solution Manager system you should set up a local System Landscape Directory in addition
to a central runtime System Landscape Directory This way you have a clear separation between your
management system (SAP Solution Manager) and managed systems in your landscape In addition
SAP Solution Manager then does not rely on a System Landscape Directory running in the production
environment For this setup configure the SLD data suppliers of your SAP Solution Manager system
to send data to the central runtime System Landscape Directory In addition configure automatic
bridge forwarding from your runtime System Landscape Directory to the local System Landscape
Directory For more information see the Planning Guide - System Landscape Directory
If you want to use a central system for Adobe Document Services we recommend that you install a
dedicated system for this purpose in your production environment For detailed information about
the sizing of the system for the different use cases see the Sizing Guide for Adobe Document Services at
SAP Service Marketplace at httpservicesapcomsizing Sizing Guidelines Solutions amp
Platform
We recommend that you start with this centralized SAP Solution Manager approach as depicted in the
following figure
5 System Landscape
52 Shared Services
4056 PUBLIC 2011-04-15
Figure 7 Single SAP Solution Manager Landscape
Large Customer Landscapes with Java
Large customers who have environments in their landscape that are large and distributed administered
by different groups or separated for security reasons can consider a distributed operations setup In
addition to the centralized setup described for small- and medium-sized customers above large
customers can put parts of the central management functions on extra hosts or systems for performance
or policy reasons You have the following options for a distributed setup
You may set up an extra system or client for Central User Administration (CUA)
The Change and Transport System (CTS) can run on an extra system However it is not
performance- or data-intensive
You may set up an extra system for central CCMS monitoring Depending on the customizing
and on the landscape size central CCMS may generate a lot of system load You can connect a
separate central CCMS to SAP Solution Manager for displaying alerts in the alert inbox of the System
Monitoring work center
You can use a separate SAP NetWeaver 70 system with usage type BI together with SAP Solution
Manager This may make sense with respect to the amount of landscape management data that is
stored for reporting purposes The amount of data strongly depends on the data granularity
storage time frame and landscape size
You can easily put Wily Introscope Enterprise Manager on an separate host
Other aspects described above for small- and medium-customers (such as the setup of the System
Landscape Directory) are also valid for large customers
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4156
523 Feature Details
This section provides further information about the features described above
5231 SAP Solution Manager
SAP provides you with SAP Solution Manager as the strategic application management platform and
to enable the collaboration between you and SAP You need to install at least one productive SAP
Solution Manager in your system landscape To ensure the availability of this application management
platform an SAP Solution Manager system is technically required to install or upgrade to SAP
NetWeaver 70 or higher If you are already using SAP Solution Manager you can also use it to manage
the solution you build with SAP NetWeaver In this case we highly recommend that you update SAP
Solution Manager to the latest version
As of SAP Solution Manager 70 SP15 you can use the newly created work centers
NOTE
During the SAP system installation or upgrade process you are prompted to enter the SAP
Solution Manager key An SAP Solution Manager system is required to generate this key Without
this key the installation or upgrade process cannot continue
You may generate all needed keys for your entire system landscape (development quality
assurance and production system) in one SAP Solution Manager system In case you plan to install
several solution landscapes (for example in different countries) one SAP Solution Manager
system is still sufficient
For more information see SAP Note 805390
It is possible to install multiple SAP Solution Managers If you do so they should host separate business
solutions
If you want to reduce the risk of unavailability you should not install SAP Solution Manager as a central
component Instead you can operate a 2-system-landscape with both a test and production
environment of SAP Solution Manager (especially if you are using time-critical functions like Support
Desk) If you also develop your own content a 3-system-landscape with a development test and
production environment is recommended
For more information about SAP Solution Manager see the following table
Topic Where to Find More Information
System infrastructure scenarios installation and configuration of SAP Solution Manager
Master Guide ndash SAP Solution Manager available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution ManagerltReleasegt
Benefits and usage scenarios SAP Solution Manager ndash Learning Maps available on SAP Service Marketplace at http
5 System Landscape
52 Shared Services
4256 PUBLIC 2011-04-15
Topic Where to Find More Informationservicesapcomrkt-solman or https
servicesapcomsolutionmanager
Additional information See SAP Service Marketplace at http
servicesapcomsolutionmanager
5232 Solution Manager Diagnostics
Solution Manager Diagnostics provides efficient and safe root-cause analysis of incidents in customer
solutions powered by SAP NetWeaver It can help monitor on operating systems databases Java
application activities performance and logs It also supports the reporting of software and
configuration changes that can lead to malfunctions and errors
You must run one Solution Manager Diagnostics within your SAP solution landscape if you run
applications based on SAP NetWeaver systems with usage type AS Java Agents are responsible for
delivering the data from all productive hosts within your system landscape to the Solution Manager
Diagnostics system
CAUTION
SAP Support performs root-cause analysis on incoming incidents with Solution Manager
Diagnostics Not installing and configuring this support infrastructure results in a dramatically
reduced service level
Solution Manager Diagnostics is fully integrated into SAP Solution Manager 70
Solution Manager Diagnostics also contains Wily Introscope (Display Server and Agent part) for
measuring performance as well as to troubleshoot problems of Non-ABAP applications Wily Introscope
is heavily used for troubleshooting applications running on AS Java
SAP has signed a distribution agreement for Wily Introscope SAP customers are allowed to use this
tool in a preconfigured way
For more information about Solution Manager Diagnostics and an FAQ list see SAP Service Marketplace
at httpservicesapcomdiagnostics
5233 System Landscape Directory
The System Landscape Directory (SLD) of SAP NetWeaver is the central directory of system landscape
information relevant for the management of your software life-cycle
NOTE
Note that the abbreviation SLD is not intended to define a product since the System Landscape
Directory is part of SAP NetWeaver This abbreviation is solely intended to improve readability
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4356
The System Landscape Directory contains a description of your system landscape (that is software
components that are currently installed) and a repository of software components that can
theoretically be installed in your landscape (such as the software components available from SAP)
Since this data gets updated automatically the System Landscape Directory provides reliable and up-
to-date system landscape information with as little effort for you as possible In this way the System
Landscape Directory acts as a central information provider for SAP and third-party tools that use this
data to deliver the services you need to keep your landscape up and running
For the System Landscape Directory as part of an SAP NetWeaver PI 71 landscape consider the following
aspects
Part of SAP NetWeaver PI 71 is a new version of the System Landscape Directory It is automatically
included in every SAP NetWeaver 71 system with usage type AS Java It offers enhanced functions
such as a full automatic synchronization mechanism for all data stored in it That is both data
delivered by data suppliers and data entered or changed manually in the System Landscape
Directory can be synchronized automatically This synchronization offers the following
A fully automated mechanism so no user interaction is required and conflicts are resolved
automatically
Asynchronous propagation of information so some nodes may be down temporarily
Communication over HTTP protocol
Uni- and bi-directional synchronization
Depending on your use case the full automatic synchronization could significantly reduce manual
synchronization effort
For SAP NetWeaver PI 71 the configuration of the system landscape directory and its data suppliers
is already included in the standard implementation procedure with SAPinst For existing systems
you only have to perform some quick and easy configuration actions to start operating the system
landscape directory server in an AS Java system
For SAP NetWeaver PI 71 you have the following options concerning SLD
Option 1
Run SAP NetWeaver PI 71 against an existing SLD running on SAP NetWeaver 70 We only
recommend this for upgrades from SAP NetWeaver 70 if you have a central SLD in operation
not running on one of your PI systems
Option 2
Use the SLD included in an SAP NetWeaver PI 71 system We recommend this option for new
installations and upgrades from older releases than SAP NetWeaver 70 due to the enhanced
functions and improved performance of SLD 71
NOTE
If you already have a central SLD running on SAP NetWeaver 70 in operation you could run
two SLD versions in parallel ndash SLD running on SAP NetWeaver 71 for your PI systems and
SLD running on SAP NetWeaver 70 for all other systemsuse cases This way your SAP
5 System Landscape
52 Shared Services
4456 PUBLIC 2011-04-15
NetWeaver PI 71 systems would benefit from the new features while it would be easy to set
up and operate such an SLD landscape For this purpose you could use the new fully
automatic synchronization This feature enables the automatic forwarding of all SLD data
from an SLD running on SAP NetWeaver 70 to an SLD running on SAP NetWeaver 71 As a
result there is no need to adapt most existing systems as their SLD data suppliers could still
send their data to the central SLD In brief the following steps would be required
1 Put SLD in a PI system into operation (part of standard implementation procedure)
2 Configure PI systems to use the new SLD (part of standard implementation procedure
for new PI systems)
3 Set up the fully automatic synchronization from your old SLD to your new SLD
As soon as an upgrade or an installation of a standalone AS Java 71 system is available you
could move your central SLD also to SAP NetWeaver 71 Then you could optionally shift
your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems
Figure 8
We recommend that you use a Domain Name System (DNS) alias so that you are able to switch to
another System Landscape Directory easily For example if customers build a new landscape they
normally start with a sandbox environment Over time more and more environments are set up
Once the production environment is in place move the System Landscape Directory there To do
this you can configure a new System Landscape Directory in the production environment
synchronize it with the old System Landscape directory and switch to the new one
Topology
Apart from the considerations above the System Landscape Directory offers several topology options
with different grades of availability at the expense of low administration and operation effort There is
no generic rule therefore on how to set up a System Landscape Directory in your system landscape
To find the topology and synchronization strategy for the System Landscape Directory that fits your
requirements concerning the System Landscape Directory availability (and hence the availability of
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4556
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
Figure 3 Legend
311 Systems with Usage Types
SAP systems are the main building blocks of SAP NetWeaver They are identified by unique SAP system
IDs (SAPSIDs) and configured for a certain purpose as indicated by usage types Usage types have the
following characteristics
They are a structuring element for SAP software on a technical level
Usage Types determine the intended purpose of a system and the role it plays in a given (distributed)
use case
They are realized by installing and configuring a collection of software components
They allow a logical view of the technology platform SAP NetWeaver PI
A usage type may require other usage types in the same system to operate
They can also be run in the same system together with other usage types that are not a prerequisite
How SAP NetWeaver Systems are Used
The following sections describe the usage types and their dependencies for SAP NetWeaver PI
Application Server ABAP (AS ABAP)
Purpose
AS ABAP is used to provide the ABAP foundation of SAP NetWeaver PI
Application Server ABAP provides a complete development and runtime environment for ABAP-based
applications It is optimized for the development of highly scalable business applications The ABAP
development and runtime environment makes it possible to develop complex business applications
3 SAP NetWeaver PI Overview
31 Installable Software Units
1656 PUBLIC 2011-04-15
without having to worry explicitly about technical details such as process or memory administration
multi-user capability database connections or similar issues These are provided in the basis services or
are integrated directly in the ABAP runtime The application development is similarly independent of
the underlying platform The application server decouples the application coding completely from the
operating system and database that are used
Dependencies
AS ABAP can be combined optionally with other usage types in one system
Application Server Java (AS Java)
Purpose
AS Java is used to provide the Java foundation of SAP NetWeaver PI using the Java Engine a Java EE-
compliant application server for running enterprise applications In addition to the pure Java EE
standard technologies the Java Engine implements complementary technologies such as Web Dynpro
or Web Services that are targeted at supporting large-scale real-business application development
projects
Dependencies
AS Java can be combined optionally with other usage types in one system
Process Integration (PI)
Purpose
PI consists of core components that model design automate and integrate processes in one or more
application systems For the integration of internal and cross-company processes PI is used to
incorporate all the functions of what was formerly known as Exchange Infrastructure (XI) In addition
PI contains core components for Business Process Management for application-embedded and
application-unbounded processes
The Advanced Adapter Engine is also part of usage type PI You use Advanced Adapter Engine to connect
to SAP systems (RFC adapter) and external systems You use the various adapters in Advanced Adapter
Engine to convert XML- and HTTP-based messages to the specific protocol and format required by
these systems and the other way around You can use the Advanced Adapter Engine that is part of
your PI system as a central Advanced Adapter Engine Optionally (for performance reasons) you can
install a non-central Advanced Adapter Engine [page 19] separately as a system with AS Java and parts of the
usage type PI on a separate host
Dependencies
PI requires AS ABAP and AS Java as prerequisites in the same system
For installing PI it is mandatory to have a dedicated PI system This applies to development quality
and production landscapes It is a prerequisite that no other system in your system landscape has a
higher release and enhancement package level than the PI system If you want to upgrade or install an
application in your system landscape you first have to make sure that the current release and
enhancement package level of the PI system is on the same level - if required you have to upgrade the
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1756
PI system first to the new or a higher release In a dedicated PI system this can be accomplished with a
minimum of downtime Also the PI system would not be affected by the downtime of other usage
types running in the same system
Configuration of Systems with Usage Types
Configuration information is available in the installation guides the configuration wizard and SAP
Solution Manager
In the Installation Guide ndash SAP NetWeaver PI 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt you find
initial technical configuration tasks This guide also informs you about how you can run the
configuration wizard and how you can access the configuration information in SAP Solution
Manager
For certain usage types configuration tasks can be applied by the configuration wizard after the
installation To do this you start the configuration wizard from SAP NetWeaver Administrator
The configuration steps for systems with usage types required for an use case are accessible through
SAP Solution Manager
To be able to use SAP Solution Manager for the configuration tasks you have to import the latest
SAP Solution Manager Implementation Content (Add-On ST-ICO) that is available for your SAP
Solution Manager release For more information see SAP Note 631042 (Release strategy for Implementation
Content (ST-ICO))
SAP Solution Manager Implementation Content is available on SAP Service Marketplace at
httpservicesapcomswdc Installations amp Upgrades Entry by Application Component SAP
Technology Components SAP Solution Manager ltReleasegt Content ST-ICO
In SAP Solution Manager you create a project and a project structure In the configuration phase
you select configuration structures with pre-delivered SAP content for your project You can find
the following different types of configuration tasks in SAP Solution Manager
Mandatory configuration tasks All configuration tasks that are mandatory for the standalone
engine or usage type
Optional configuration tasks Configuration tasks for areas where customers need to decide
if they want to use these functions (for example high availability or security settings)
Additional functions ndash configuration tasks Configuration tasks for functional units that are
used in certain use cases only
A marked checkbox in front of the configuration tasks indicates those configuration tasks that are
relevant for the use case you have chosen To configure ABAP systems SAP Solution Manager
offers executable configuration files (IMG activities)
For information about using SAP Solution Manager Content and creating a configuration guide
see the following documentation
httphelpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Implementing
and Upgrading SAP Solutions Configuration
3 SAP NetWeaver PI Overview
31 Installable Software Units
1856 PUBLIC 2011-04-15
How to Create a Configuration Guide using SAP Solution Manager available at http
servicesapcomsolutionmanager Media Library How-To Documents
Restrictions for Systems with Multiple Usage Types
If you have one system with multiple usage types be aware that we do not provide standard tools
to separate these usage types and distribute them to multiple systems at a later stage For example
if you have a system with usage types A and B you are not able to migrate it with SAP standard
tools into two systems one with usage type A only and the other with usage type B only
In addition we do not provide standard tools to merge multiple systems with different usage types
into one system with multiple usage types at a later stage
If you want to perform these tasks you require specific project support
The following figure shows that SAP standard system copy and migration tools do not support
you in separating or merging systems with usage types
Figure 4 No Support for Merging or Separating Systems with Usage Types
Although you can use one system for multiple usage types client restrictions apply for usage type
PI PI requires a dedicated client due to special PI requirements concerning the client pipeline
Whereas application client pipelines only send and receive messages the central PI pipeline can
also map messages to different formats before sending them
312 Standalone Engines
Standalone engines of SAP NetWeaver are additional installable software units They do not work as
full-blown systems of SAP NetWeaver but as standalone engines that provide a specific (server) function
in combination with one or more SAP NetWeaver systems
Standalone engines are not part of a usage type They do not run on AS ABAP or AS Java
The standalone engines that are available for SAP NetWeaver Process Integration are described in the
following
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1956
Gateway
It is possible to install an SAP instance of an SAP NetWeaver system based exclusively on a standalone
gateway This type of instance does not contain normal work process types (dialog background update
enqueue or spool) Only the gateway process (gwrd) is started If there is an SNA connection to an R
2 system gateway work processes (gwwp) are also started
SAP Conversion Agent by Informatica
SAP Conversion Agent by Informatica is a data conversion tool that enables you to create interfaces
between any data formats and XML-based systems SAP Conversion Agent can convert unstructured
semi-structured and structured formats to XML and the other way around The Conversion Agent
comprises the Conversion Agent Studio and the Conversion Agent Engine In the Conversion Agent
Studio you can develop and configure data conversions The Conversion Agent Engine executes the
data conversions
Search and Classification (TREX)
You can use Search and Classification with SAP NetWeaver PI to search for messages that were previously
indexed Message search using index provides additional methods of searching for specific messages In
addition to static header attributes you can also use adapter-specific message attributes and data from
the message payload for the search A requirement of this however is that the messages are indexed
first You can apply the index-based message search to one or all indexed components of an integration
landscape (domain) Integration Server Adapter Engines and ABAP business systems
For more information see the SAP Library [page 12] at Administratorrsquos Guide Technical Operations for SAP
NetWeaver Administration of SAP NetWeaver Systems Administering PI (Process Integration) Monitoring Index
Administration
Web Dispatcher
The Web Dispatcher lies between the Internet and your SAP system It is the entry point for HTTP(s)
requests into your system which consists of one or more SAP NetWeaver application servers As a
software web switch the Web dispatcher can reject connections or accept them When it accepts a
connection it balances the load to ensure an even distribution across the servers
You can use the Web dispatcher in ABAPJava systems and in pure Java systems as well as in pure ABAP
systems
It is also beneficial to use the Web Dispatcher if you do not need security functions (entry point in the
demilitarized zone (DMZ) SSL URL filtering) but you simply want to balance the load between
multiple SAP NetWeaver Application Server instances
Since Web Dispatcher is optional for every SAP system it is not contained in the system landscape and
the implementation sequence of the use case in this documentation
For more information see the SAP Library [page 12] at Function Oriented View Application Server Infrastructure
SAP Web Dispatcher
3 SAP NetWeaver PI Overview
31 Installable Software Units
2056 PUBLIC 2011-04-15
Advanced Adapter Engine
You use the Advanced Adapter Engine to connect to SAP systems (RFC adapter) and external systems
You use the various adapters in Advanced Adapter Engine to convert XML- and HTTP-based messages
to the specific protocol and format required by these systems and the other way around For specific
senderreceiver combinations messages can be processed without invoking the central Integration
Engine In principle you connect external systems using the adapters that are installed centrally or
non-centrally in Advanced Adapter Engine You can use the Advanced Adapter Engine that is part of
your PI system as a central Advanced Adapter Engine Optionally (for performance reasons) you can
install a non-central Advanced Adapter Engine separately as a system with AS Java and parts of the
usage type PI on a separate host
Adapter Engine (Java SE)
Adapter Engine (Java SE) is a separate software unit You can use it only if you have SAP NetWeaver
systems with usage type PI in your system landscape It has to be installed manually You use the Adapter
Engine (Java SE) to connect to external systems Using the various adapters in the Adapter Engine (Java
SE) XML and HTTP-based messages can be converted to the specific protocol and format required by
such systems and the other way around The Adapter Engine (Java SE) only provides some of these
adapters as a standalone version with restricted functions for operating systems that do not support
SAP NetWeaver PI 71 but that have at least a Java Runtime Environment 50 Therefore you should
use the Adapter Engine (Java SE) only if the platform prerequisites do not allow you to use the Advanced
Adapter Engine
SAP Partner Connectivity Kit
SAP Partner Connectivity Kit (PCK) runs on AS Java with parts of the usage type PI It enables a system
of a smaller company or subsidiary that does not run SAP NetWeaver PI to connect to your SAP
NetWeaver systems
313 Clients
Clients are additional installable programs or tools They reside either on local front-end PCs accessed
by users or on back-end systems where they act as client programs within an SAP NetWeaver system
landscape
The clients that you can use with SAP NetWeaver Process Integration are described in the following
sections
SAP GUI
NOTE
We recommend that you use the following versionsI
SAP GUI for Windows 710 (or higher) with the latest patch level
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 2156
SAP GUI for Java 710 (or higher) with the latest revision
The integrated SAP ITS 710
For more information about the SAP GUI family see SAP Service Marketplace at http
servicesapcomsapgui
SAP offers three different client applications for accessing ABAP applications in SAP systems (such as
SAP NetWeaver systems with usage type AS ABAP) This SAP GUI family consists of
SAP GUI for HTML
SAP GUI for HTML is based on the SAP integrated Internet Transaction Server (ITS) which is
included in the installation of SAP NetWeaver systems as of SAP NetWeaver 2004 On the client
side only a suitable browser (such as Internet Explorer 70 or Firefox 20) and a virtual machine are
required SAP ITS 620 is not compatible with SAP NetWeaver 71
SAP GUI for the Java environment (SAP GUI for Java)
SAP GUI for Java is a generic SAP GUI that covers a variety of platforms
For more information about the installation of SAP GUI for Java see the documentation Installation
Guide ndash SAP Front End
SAP GUI for the Windows environment (SAP GUI for Windows)
SAP GUI for Windows is SAPs universal client for accessing all SAP applications built on ABAP
technology It is available on the Microsoft Windows platform only and offers the broadest feature
set of all members of the SAP GUI family
For more information about the installation of SAP GUI for Windows see the Installation Guide ndash
SAP Front End
SAP NetWeaver Developer Studio
The SAP NetWeaver Developer Studio is SAPrsquos Integrated Development Environment (IDE) for Java
and is based on the open-source tools framework Eclipse 33 With the SAP NetWeaver Developer Studio
you can develop Java EE 5 applications from scratch using the built-in support for new technologies
such as EJB 30 and JSF 12
During the installation of the SAP NetWeaver Developer Studio several features are offered for
installation For SAP NetWeaver PI 71 only the following features are relevant
SAP NetWeaver Developer Studio Platform
SAP NetWeaver Developer Studio Java EE
NOTE
If you want to use one of the other features you need SAP NetWeaver Composition Environment
and a corresponding developers licence
For more information about the installation of SAP NetWeaver Developer Studio see the Installation
Guide ndash SAP NetWeaver Developer Studio 71 or Installation Guide ndash SAP NetWeaver Developer Studio 71 Including
Enhancement Package 1
3 SAP NetWeaver PI Overview
31 Installable Software Units
2256 PUBLIC 2011-04-15
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
SAP enhancement packages are a new way of delivering new functions for SAP NetWeaver This allows
a clear separation between the delivery of new functions on the one hand and corrections legal changes
and security updates on the other hand (in Support Package stacks) SAP enhancement packages are
cumulative an enhancement package always contains the functions of the corresponding predecessor
enhancement packages
Enhancement packages are maintained by their own Support Packages while the main release is in
maintenance
Benefits
SAP enhancement packages offer the following benefits
You have reduced effort for testing and no effort for training when applying Support Packages as
new features are only shipped with enhancement packages
Adding new functions between releases becomes predictable and controllable
New functions can be added successively in small steps There is no need to fully upgrade your
system to get new functions
You have minimal training effort when applying an enhancement package because existing
functions are not replaced
Implementation
There are the following ways to get an SAP NetWeaver system with the release level of SAP enhancement
package 1 for SAP NetWeaver Process Integration 71
New installation of SAP NetWeaver PI 71 including enhancement package 1 using the standard
installation tool SAPinst
Upgrade of an existing SAP NetWeaver system from a release lower than SAP NetWeaver PI 71 to
SAP NetWeaver PI 71 including enhancement package 1 For this you use the upgrade programs
SAPup (for ABAP) and SAPJup (for Java)
Installation of the enhancement package on an existing SAP NetWeaver PI 71 system
For this you use the Software Update Manager (SUM) The Software Update Manager evolved
from the previously used SAP Enhancement Package Installer The tool has been renamed to reflect
its broader use for example you can also use it for applying Support Package Stacks to your system
On the ABAP side the Software Update Manager uses a system cloning and switch procedure for
installing enhancement packages It installs a copy of the system the shadow system parallel to
the original system This shadow system is used to update the relevant software components and
to install the additional components while the original system is still in production operation At
a certain point during downtime the switch to the new system is made and afterwards any parts
of the original system that are no longer needed are deleted The enhancement package installation
in a Java system uses a deploy-based procedure that is no shadow system is used The Software
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2011-04-15 PUBLIC 2356
Update Manager requires a stack configuration file (xml file) as input file for the enhancement
package installation procedure This file lists all the packages that are to be installed in your systems
The stack configuration file is generated when you download the required packages
As the Software Update Manager is updated regularly we recommend to always use the latest
version It is delivered as part of the SL toolset For more information see http
servicesapcomsltoolset
For an overview of all required steps for the enhancement package installation process and
corresponding documents see Process Overview Installation of Enhancement Package 1 on an Existing SAP
Netweaver PI 71 System [page 28]
Content of SAP Enhancement Package 1 for SAP NetWeaver PI 71
With enhancement package 1 for SAP NetWeaver PI 71 new features are introduced and some existing
are changed The following is a selection of some of the most important enhancements
Enhanced design and modelling options in the Enterprise Services Repository
New services registry
Support for new Web services standard (Web Services Reliable Messaging)
New modules for the Advanced Adapter Engine
Use of shared memory of the ABAP Application Server for message processing
For more information about the changes see SAP Library [page 12] at Whatacutes new in SAP NetWeaver PI 71
ndash Release Notes
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2456 PUBLIC 2011-04-15
4 SOA-Based Integration Use Case
41 Overview
You can use SOA-based integration to set up the communication between service providers and service
consumers in both application-to-application and business-to-business scenarios and to execute
operate and monitor the communication at runtime SOA-based integration covers both direct (point-
to-point) as well as mediated (via an Integration Server) communication between service providers and
service consumers
The use case spans the whole life cycle of a SOA-based integration scenario including
Scenario modeling and service design in the Enterprise Services Repository
Implementation of the service provider and consumer in the back-end systems
Configuration and finally execution monitoring and operation of the integration scenario
For scenarios using Integration Server or broker-based communication the configuration of the
different connectivity options (for example SOAP RFC Web Services Industry standards and JDBC)
and their enhancements is covered
For more information see the following documents
Service-Enabling with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdnsoa-modeling
Getting Started
Service-Enabling a Legacy Application with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdn
soa-servicebus Getting Started
In the following you will find information about the installation of the involved software units
42 System Landscape
The following figure shows the system landscape for this use case
4 SOA-Based Integration Use Case
41 Overview
2011-04-15 PUBLIC 2556
Figure 5 SOA-Based Integration
It is mandatory to have a dedicated PI system This applies to development quality and production
landscapes
For PI it is a prerequisite that no other system in your system landscape has a higher release than
the PI system For exceptions to this rule see SAP Note 1043047 For example SAP XI 30 is compatible
with SAP NetWeaver 640 and 70 application systems since the same XI protocol is used Apart
from these exceptions if you want to upgrade or install an application in your system landscape
you first have to make sure that the PI system is on the same release level If required you have to
upgrade the PI system first to the new or a higher release
CAUTION
Although it should be technically possible to run an application system with a higher release
than your PI system in your system landscape this is not supported by SAP (apart from the
exceptions listed in SAP Note 1043047) Therefore you run such a landscape at your own risk
You can use the Advanced Adapter Engine that is part of your PI system as a central Advanced
Adapter Engine
Adapter Engine (Java SE) can be installed in a non-SAP Java environment However it only hosts
a subset of the adapter functionality is only supported for compatibility reasons and should be
used only if this is a precondition in your environment
Optionally you can use the Change Management Service (CMS) of an SAP NetWeaver 70 system
with usage type DI to transport design objects and repository objects For more information see
the SAP Library [page 12] at Administratoracutes Guide Technical Operations for SAP NetWeaver Administration
of SAP NetWeaver Systems PI (Process Integration) Software Logistics Transporting ESR Content and Objects
of Integration Directory PI Transports Using the Change Management Service (CMS)
Smaller business partners or subsidiaries that do not run SAP NetWeaver install SAP Partner
Connectivity Kit in their system landscape SAP Partner Connectivity Kit enables XML document
4 SOA-Based Integration Use Case
42 System Landscape
2656 PUBLIC 2011-04-15
exchange between your SAP NetWeaver systems and the partner systems Since SAP Partner
Connectivity Kit gets installed in their system landscape it is not shown in the system landscape
figure above
The AS ABAP system acts as an application and service provider For Java Web Services you also
require AS Java In addition you require SAP NetWeaver Developer Studio on the client side as a
development environment
The Web service client can be either an SAP or a non-SAP application For example an AS ABAP
system or a Web browser could act as application or service consumer
You can install SAP Conversion Agent by Informatica in the system with usage type PI or on a host
where SAP Partner Connectivity Kit is installed or on a host where neither usage type PI nor SAP
Partner Connectivity Kit is installed
43 Implementation Sequence
Procedure
To install this use case perform the steps listed in the following table
StepAction[Corresponding Documentation] Remarks
1 Make sure that you have performed the preparation steps You have planned your system landscape [page 33]
(that is you have decided how many systems you require how you want to use each of these systems and which standalone engines and clients you require)
With the help of your hardware partner you have mapped your systems and standalone engines to properly sized hosts
You have planned and installed shared services [page 35]
2 Installation of system with usage type PI (includes the installation of AS ABAP and AS Java)
NOTE
For usage type PI a Unicode installation is mandatory
[Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt]
If you want to use the features of enhancement package 1 use the direct installation of SAP NetWeaver PI 71 including enhancement package 1
Make sure that you perform the configuration steps as described in the installation guide For certain usage types configuration tasks can be applied by the configuration wizard These configuration tasks as well as any additional configuration steps for your use case are listed in SAP Solution Manager For more information
4 SOA-Based Integration Use Case
43 Implementation Sequence
2011-04-15 PUBLIC 2756
StepAction[Corresponding Documentation] Remarks
see the Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt
3 Install the Adapter Engine (Java SE) engines if required[Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
4 To integrate small business partners and subsidiaries the business partners or subsidiaries install SAP Partner Connectivity Kit running on AS Java with parts of usage type PI in the business partners or subsidiarys system landscape[Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
5 Install SAP Conversion Agent by Informatica if required[SAP Library [page 12] at Function-Oriented View Process Integration SAP Conversion Agent by Informatica Deploying and Using Conversion Agent ]
6 Installation of clients SAP GUI
[Installation Guide ndash SAP Front End]
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
The process sequences give a comprehensive overview of the steps relevant for the enhancement
package installation on an existing SAP NetWeaver PI 71 system
The process sequence is divided into a planning phase and an implementation phase Each step in both
phases contains references to the corresponding documentation to ensure that you can easily find the
information you need
Process
NOTE
To download the enhancement package files and required Support Packages you require the SAP
Solution Manager Maintenance Optimizer You have the following options
Manual Selection
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2856 PUBLIC 2011-04-15
You manually select the required files from SAP Service Marketplace at http
servicesapcomswdc using the SP Stack Application You use the Maintenance Optimize
only to approve the packages which is a prerequisite for the download
Automatic Calculation
The Maintenance Optimizer supports the download of a consistent queue that includes all
necessary Support Packages and enhancement packages In addition SAP Solution Manager
calculates a valid import queue for the selected SAP system and generates the enhancement
package stack configuration file that you require for the installation
As a prerequisite the system that you want to update needs to be maintained correctly in
SAP Solution Manager System Landscape As the Maintenance Optimizer uses this data for
the calculation it is crucial that the data is up-to-date In addition the SAP Solution Manager
system requires a Minimum Support Package level (see below)
Planing PhaseStep Description Documentation
Hardware amp Software Prerequisites
Check which platforms are supported for your target release (OSDB dependencies)
Product Availability Matrix (PAM) at httpservicesapcompam
Check which hardware sizing is required for your target release
Sizing information at httpservicesapcomsizing
Solution Manager Prerequisites
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of the required software packages you have to make sure that your SAP Solution Manager system has the required Support Package levelAt least SAP Solution Manager 70 EHP1 Support Package Stack 17 is required We recommend to use SAP Solution Manager 70 EHP1 Support Package Stack 23Check if you need to do an update or upgrade of your SAP Solution ManagerMake sure that you run the guided procedure SOLMAN_SETUP after every installation or update of SAP Solution Manager and that it completes successfully
For upgrades from source release SAP Solution Manager 31 and 32Upgrade Guide ndash SAP Solution Manager 70 incl Enhancement Package 1For updates from SAP Solution Manager 70Update Guide SAP Enhancement Package 1 for SAP Solution Manager 70Follow-up activities after an Support Package Stack update or enhancement package updateSolution Operations Guide ndash SAP Solution Manager 70 EHP1 section Software Change Management All guides are available at http
servicesapcom instguides SAP Components SAP Solution Manager -gt Release 70 EHP 1
Implementation PhaseStep Description Documentation
1Solution Manager Preparation
Configure the SAP Solution Manager Maintenance Optimizer
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of software packages make sure your
Configuration of Maintenance Optimizer http
helpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Change Request Management and Change ControlMaintenance Optimizer
Prerequisites
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 2956
Implementation PhaseStep Description Documentation
system landscape data in SAP Solution Manager is maintained correctlyLandscape Verification 10 which is an add-on to SAP Solution Manager can support you in maintaining your system landscape data The use of this tool is optional
Landscape Verification http
wwwsdnsapcom irj
sdn alm-update-
management link Landscape Verification under Related Areas on Upgrade and Update Management (in the right column)
SAP Note 1468605 (Installation of Landscape Verification)
Maintaining System Landscape Information [page 47]Note that the information provided in this section is based on SAP Solution Manager 70 EHP1 SP23
2System Preparation
Prepare your system as described in the documentation for example perform OS DB specific preparations and the PI-specific preparations
Update Guide ndash Update of SAP Systems with Software Update Manager sections Planning and Preparation
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
3Software Download
Select and download the software packages in either of the following ways Automatic calculation Create
a maintenance transaction in the Maintenance Optimizer and choose the Calculate Files Automatically option
Manual Selection Create a maintenance transaction in the Maintenance Optimizer and choose the Select Files Manually option You then can select the files manually using the SP Stack application in SAP Service Marketplace
NOTE
You have to download the stack configuration file manually after you have selected all files in the SP Stack
httphelpsapcom SAP Solutions SAP Solution Manager
SAP Solution Manager 70 EHP1 ltSPgtChange Request Management and
Change Control Maintenance Optimizer Maintenance Procedure Scenarios
For information about the automatic calculation see Maintenance Transaction with Installation of an Enhancement PackageFor information about the manual selection and approval process see section Approve and Download Files in Download Basket
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
3056 PUBLIC 2011-04-15
Implementation PhaseStep Description Documentation
application Choose Generate Stack XML and save the file
4Enhancement Package Installation
Run Software Update Manager to update your system with the selected software packages
Update Guide ndash Update of SAP Systems with Software Update Manager
5Follow-Up Steps
Perform technical and PI-specific follow-up activities after the enhancement package installation is done
Update Guide ndash Update of SAP Systems with Software Update Manager section Follow-Up Activities
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
6Configuration
Configure newly installed enhancement package functions using SAP Solution Manager content
See Systems with Usage Types [page 16] section Configuration of Systems with Usage Types
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 3156
This page is left blank for documents that are printed on both sides
5 System Landscape
51 Planning Your System Landscape
The installable software units that make up your system landscape depend on the functions that you
want to implement For information about the features see systems [page 16] standalone engines [page 19]
and clients [page 21]
In addition you have to determine the required shared services [page 35] (such as SAP Solution Manager
or SAP NetWeaver Administrator) that run on central systems in your system landscape and the
landscape aspects relevant for their implementation
In the following you will find general information that you should consider when planning your system
landscape
Sizing
You have to map systems and standalone engines to hosts after you have a clear picture of the following
Which systems and standalone engines you require
How many systems you require and how you want to use each of these systems
NOTE
No general guideline can be given for the sizing of your landscape since this relies heavily on your
requirements You should therefore perform this task together with your hardware partner and
your technical consultant
For information about sizing your systems you can use the following information sources
Your first point of reference is the Quick Sizer
SAP built the Quick Sizer as an online sizing questionnaire Internet application in close cooperation
with its hardware partners This tool delivers general sizing categories based on your volume load
estimates The results provide an objective basis for sizing independent of platform and
configuration
For more information see SAP Service Marketplace at
httpservicesapcomsizing for the SAP NetWeaver PI 71 sizing guide available under
Sizing Guidelines Business Suite amp Services
httpservicesapcomquicksizer for more information and access to the tool itself
Also consider the following important aspects concerning sizing
High availability
5 System Landscape
51 Planning Your System Landscape
2011-04-15 PUBLIC 3356
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Technical Infrastructure High Availability
Unicode
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Internationalization
Contact your hardware partner to find out the appropriate number of sized hosts
The platform-independent abstract results of the Quick Sizer can be used by any of our hardware
partners to create a concrete offer SAP itself does not make any hardware recommendations the
responsibility for sizing and detailed hardware configuration lies with the hardware partners
Figure 6 Example of Mapping of Systems and Standalone Engines to Three Hosts
NOTE
Optionally you could also distribute single systems to multiple hosts For example you could
decide to install the database instance of an SAP system on a separate host for performance
reasons or distribute other system instances to achieve high availability
To provide a mapping that fits your required functions and performance your hardware partner
and your technical consultant have to identify the number of required instances of SAP NetWeaver
find out how to distribute these instances to hosts and what functions will run on which instance
Therefore the hardware partner and the technical consultant have to consider many different
aspects such as
Number of required SAPS (SAP Application Benchmark Performance Standard) for each
system (provided by Quick Sizer)
Landscape-relevant aspects concerning security For more information see the SAP Security
Guide in the SAP Library [page 12] at Administratoracutes Guide Security Guide
Landscape-relevant aspects concerning scalability high availability operation and software
life-cycle management
5 System Landscape
51 Planning Your System Landscape
3456 PUBLIC 2011-04-15
For more information about relevant aspects for the mapping of systems to hosts see the document
Technical Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
Scaling and Distribution Options
You may need to design your system landscape for a large number of users SAP NetWeaver PI offers
you different means of scalability The following list provides you with some examples
You could install multiple systems of one type and use them for different purposes
You could scale every system by installing dialog instances or by distributing the database instance
For more information about distribution options on the instance level see the Technical
Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
For every SAP system you could additionally install Web Dispatcher For more information see
the SAP Library [page 12] at FunctionndashOriented View Application Server Infrastructure SAP Web
Dispatcher
You could further distribute certain standalone engines ndash for example Search and Classification
(TREX) is based on a flexible architecture that supports a distributed installation For more
information see the Technical Infrastructure Guide ndash SAP NetWeaver PI 71 available in SAP Service
Marketplace at httpservicesapcominstallNWPI71
52 Shared Services
You normally run shared services on central systems in your system landscape The following features
could be used for SAP NetWeaver Process Integration to realize shared services
SAP Solution Manager
Used to implement train test maintain monitor control change and manage incidents of your
SAP solution system landscape (open end-to-end application management)
As of SAP Solution Manager (70) 40 Support Package 15 SAP Solution Manager has become the
platform for SAPs end-to-end solution operations strategy Functions for complete application
management has been combined with administrative tools and has been merged in newly created
role based work centers
NOTE
Be aware that you require an SAP Solution Manager system to install or upgrade to SAP
NetWeaver 70 and higher An SAP Solution Manager system is required to generate the SAP
Solution Manager key needed during the installation or upgrade process Without this key
the installation or upgrade process cannot continue
For SAP NetWeaver Process Integration you require SAP Solution Manager 70
For more information see SAP Note 805390
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3556
Solution Manager Diagnostics
An integral part of SAP Solution Manager that is running as a Java application on the Java stack of
SAP Solution Manager 70 Solution Manager Diagnostics is used to analyze the root cause of
incidents in your landscape in an efficient and safe way Before Go-Live Solution Manager
Diagnostics has to be set up and made accessible remotely
SAP NetWeaver Administrator
SAP NetWeaver Administrator is the central administration component which is used for
monitoring and administering Java applications It is included in SAP NetWeaver systems with AS
Java
SAP NetWeaver Administrator exists in the following flavors
A local mode which runs out of the box and which focuses on administrating the underlying
SAP NetWeaver AS Java
NOTE
For a SAP NetWeaver PI 71 it has a special role which you need to activate using a
configuation wizard
A central mode which has to be configured before use and which deals with the system
landscape management
SAP has decided to merge the central mode of SAP NetWeaver Administrator into the new work
centers available as of SAP Solution Manager 70 SP 15 Thus it can be used in an administrative
context together with non-Java-based administration tools Although the central mode of SAP
NetWeaver Administrator will be still available for some time SAP will not develop this tool any
further SAP focuses on optimizing the administrative work centers of SAP Solution Manager
instead
The local mode of SAP NetWeaver Administrator stays untouched It is available for current and
future releases of SAP NetWeaver
SAP Central Process Scheduling by Redwood
SAP Central Process Scheduling application by Redwood enables central job scheduling and job
monitoring of current and old releases of AS ABAP systems (as of Basis Release 31) This application
is fully integrated in SAP NetWeaver Depending on the business needs SAP business applications
are the initial trigger for scheduled activities You can now manage jobs and job chains conveniently
using a graphical user interface
System Landscape Directory
The System Landscape Directory is the central directory of system landscape information relevant
for the management of your software life-cycle It contains a description of your system landscape
(that is software components that are currently installed) and a repository of software components
that can theoretically be installed in your landscape (such as the software components available
from SAP)
Adaptive Computing Controller
5 System Landscape
52 Shared Services
3656 PUBLIC 2011-04-15
The Adaptive Computing Controller enables users to control an adaptive computing landscape
from a single point through observation operation and dynamic resource distribution With
adaptive computing hardware software and system services are able to adapt to changing business
needs In the Adaptive Computing Controller the run-time data of logical and physical landscapes
can be monitored application services can be startedstoppedrelocated and hardware resources
can be assigned to application services The operation can also be mass executed and be planned as
tasks to be executed
For more information about the installation of the Adaptive Computing Controller tool see the
document Installation Guide ndash Adaptive Computing Controller in SAP NetWeaver 71 available on SAP Service
Marketplace at httpservicesapcominstallNWPI71
For more information about Adaptive Computing in general see httpsdnsapcomirj
sdnadaptive
521 Use Cases
You can use the applications and tools described above for use cases that are normally performed
centrally The following sections describe these use cases
5211 End-to-End Solution Operations
Running business applications through their complete life-cycle is a challenge Therefore SAP has
started the Run SAP methodology for implementing End-to-End Solution Operations Based on a set
of SAP standards a roadmap and a package for training and certification Run SAP helps customers to
facilitate End-to-End Solution Operations
You can download the SAP standards for Solution Operations from SAP Service Marketplace at http
servicesapcomsupportstandards They describe roles customers typically have in their IT
environment For optimal role support SAP has grouped existing and new functions in SAP Solution
Manager work centers as of SAP Solution Manager 70 Support Package 15 Operations aspects are fully
covered by adding administrative functions for SAP NetWeaver as well Work centers are ABAP Web
Dynpro-based applications They offer the following advantages
Easy to use similar look and feel
Context transfer while jumping from one work center into another
Logical grouping of tools for a certain area
Simple authorization concept
Easy to expand
Each IT role belongs to one or more work centers For instance the Technical Administrator IT role is
covered by the work centers for System Monitoring System Administration and Landscape Management
The following work centers are available
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3756
Business Process Operations
Change Management
Root Cause Analysis
Implementation Upgrade
Incident Management
Test Management
Job Management
System Landscape Management
Solution Documentation Assistant
SAP Engagement and Service Delivery
SAP Solution Manager Administration
System Administration
System Monitoring
My Home is the central point of access to all important data of almost all work centers in SAP Solution
Manager
5212 Support Infrastructure
A key requirement for effective support of IT solutions is the ability to perform root cause analysis with
speed and efficiency
With SAP Solution Manager SAP has long had an infrastructure in place for its ABAP applications that
efficiently supports SAP solutions This helps ensure the high availability and smooth running of
business processes For more information see the SAP Solution Manager section
With Solution Manager Diagnostics this knowledge has been extended to Java applications If for
example homegrown Java applications cause instability Solution Manager Diagnostics helps trace the
cause to eradicate the problem rapidly Solution Manager Diagnostics is fully integrated into SAP
Solution Manager 70 Solution Manager Diagnostics also contains two third-party tools CArsquos Wily
Introscopereg for measuring performance as well as troubleshooting problems of the Java EE Engine
and applications running on it and Mercury Loadrunnerreg which enables SAP Support to produce a
defined load in the SAP solution landscape remotely For more information see Solution Manager
Diagnostics [page 43]
The support infrastructure provides SAP Support with safe access to your productive landscape for safe
root cause analysis so ensuring that SAP Support does not change your landscape inadvertently You
require a support infrastructure to run SAP NetWeaver
The following figure shows the overall infrastructure including SAP NetWeaver administration tools
that are used by administrators or operators at the customer site
5 System Landscape
52 Shared Services
3856 PUBLIC 2011-04-15
Landscape Aspects
If you use SAP NetWeaver Process Integration 71 productively besides SAP Solution Manager (as a
central support platform) you have to set up Solution Manager Diagnostics for supportability reasons
Implementation Sequence
For information about the implementation of the support infrastructure see the document Master
Guide ndash SAP Solution Manager 70 available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution Manager ltReleasegt
5213 Collection of Landscape Data
Amongst other applications and services the support infrastructure and the SAP NetWeaver
administration tools rely on system landscape data
For SAP NetWeaver PI 71 you have to run non-ABAP components in your solution landscape
Therefore the System Landscape Directory is mandatory The landscape data that is automatically
gathered by the System Landscape Directory is replicated to SAP Solution Manager There are several
topology options for the System Landscape Directory They offer different grades of availability
administration and operation effort
For more information see the System Landscape Directory section
5214 Authentication and Single Sign-On
Before implementing your system landscape plan how to implement authentication and how to
integrate different systems into a Single Sign-On landscape Single Sign-On reduces complexity for end
users saving them valuable time while also reducing administration effort for resetting passwords
thereby contributing to TCO reduction
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
5215 Integrated User and Access Management
In a system landscape containing a combination of ABAP and Java components we recommend that
you integrate your user and access management so that you can use the same user data across different
systems administer this data centrally and control access to data SAPs mature fine-grained
authorization concept allows detailed control of access rights SAP NetWeaver provides both ABAP and
Java-based user management solutions The user management solution that you use to administer
your user data depends on factors such as the type of systems that are running in your landscape
If you want to use central user administration we recommend that you run it in a non-production
system If you do not have a central user administration yet you can for example realize it in the SAP
Solution Manager system
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3956
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
522 Examples for the Overall System Landscape of Shared Services
In this section we provide examples of how shared services can be set up depending on the system
landscape they are intended for The following examples aggregate the landscape aspects given in the
Use Cases section
NOTE
The following sections and the figure mostly do not show information about the life-cycle of
shared services For example you may also need a development and testquality assurance system
for SAP Solution Manager You should consider this aspect in addition to the information given
in this section based on your requirements
Small and MediumndashSized Customer Landscapes with Java
As you use Java productively for SAP NetWeaver PI 71 besides SAP Solution Manager you have to set
up additional components for optimal monitoring administration and support Solution Manager
Diagnostics and the central mode of SAP NetWeaver Administrator are already fully integrated into
SAP Solution Manager 70 as the central operations hub For SAP Process Integration you must also
set up SAP NetWeaver Administrator with a special role
We recommend that you do not install SAP Central Process Scheduling in the SAP Solution Manager
system You have to set up and operate the system which hosts your productive scheduler as a mission
critical system
In the SAP Solution Manager system you should set up a local System Landscape Directory in addition
to a central runtime System Landscape Directory This way you have a clear separation between your
management system (SAP Solution Manager) and managed systems in your landscape In addition
SAP Solution Manager then does not rely on a System Landscape Directory running in the production
environment For this setup configure the SLD data suppliers of your SAP Solution Manager system
to send data to the central runtime System Landscape Directory In addition configure automatic
bridge forwarding from your runtime System Landscape Directory to the local System Landscape
Directory For more information see the Planning Guide - System Landscape Directory
If you want to use a central system for Adobe Document Services we recommend that you install a
dedicated system for this purpose in your production environment For detailed information about
the sizing of the system for the different use cases see the Sizing Guide for Adobe Document Services at
SAP Service Marketplace at httpservicesapcomsizing Sizing Guidelines Solutions amp
Platform
We recommend that you start with this centralized SAP Solution Manager approach as depicted in the
following figure
5 System Landscape
52 Shared Services
4056 PUBLIC 2011-04-15
Figure 7 Single SAP Solution Manager Landscape
Large Customer Landscapes with Java
Large customers who have environments in their landscape that are large and distributed administered
by different groups or separated for security reasons can consider a distributed operations setup In
addition to the centralized setup described for small- and medium-sized customers above large
customers can put parts of the central management functions on extra hosts or systems for performance
or policy reasons You have the following options for a distributed setup
You may set up an extra system or client for Central User Administration (CUA)
The Change and Transport System (CTS) can run on an extra system However it is not
performance- or data-intensive
You may set up an extra system for central CCMS monitoring Depending on the customizing
and on the landscape size central CCMS may generate a lot of system load You can connect a
separate central CCMS to SAP Solution Manager for displaying alerts in the alert inbox of the System
Monitoring work center
You can use a separate SAP NetWeaver 70 system with usage type BI together with SAP Solution
Manager This may make sense with respect to the amount of landscape management data that is
stored for reporting purposes The amount of data strongly depends on the data granularity
storage time frame and landscape size
You can easily put Wily Introscope Enterprise Manager on an separate host
Other aspects described above for small- and medium-customers (such as the setup of the System
Landscape Directory) are also valid for large customers
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4156
523 Feature Details
This section provides further information about the features described above
5231 SAP Solution Manager
SAP provides you with SAP Solution Manager as the strategic application management platform and
to enable the collaboration between you and SAP You need to install at least one productive SAP
Solution Manager in your system landscape To ensure the availability of this application management
platform an SAP Solution Manager system is technically required to install or upgrade to SAP
NetWeaver 70 or higher If you are already using SAP Solution Manager you can also use it to manage
the solution you build with SAP NetWeaver In this case we highly recommend that you update SAP
Solution Manager to the latest version
As of SAP Solution Manager 70 SP15 you can use the newly created work centers
NOTE
During the SAP system installation or upgrade process you are prompted to enter the SAP
Solution Manager key An SAP Solution Manager system is required to generate this key Without
this key the installation or upgrade process cannot continue
You may generate all needed keys for your entire system landscape (development quality
assurance and production system) in one SAP Solution Manager system In case you plan to install
several solution landscapes (for example in different countries) one SAP Solution Manager
system is still sufficient
For more information see SAP Note 805390
It is possible to install multiple SAP Solution Managers If you do so they should host separate business
solutions
If you want to reduce the risk of unavailability you should not install SAP Solution Manager as a central
component Instead you can operate a 2-system-landscape with both a test and production
environment of SAP Solution Manager (especially if you are using time-critical functions like Support
Desk) If you also develop your own content a 3-system-landscape with a development test and
production environment is recommended
For more information about SAP Solution Manager see the following table
Topic Where to Find More Information
System infrastructure scenarios installation and configuration of SAP Solution Manager
Master Guide ndash SAP Solution Manager available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution ManagerltReleasegt
Benefits and usage scenarios SAP Solution Manager ndash Learning Maps available on SAP Service Marketplace at http
5 System Landscape
52 Shared Services
4256 PUBLIC 2011-04-15
Topic Where to Find More Informationservicesapcomrkt-solman or https
servicesapcomsolutionmanager
Additional information See SAP Service Marketplace at http
servicesapcomsolutionmanager
5232 Solution Manager Diagnostics
Solution Manager Diagnostics provides efficient and safe root-cause analysis of incidents in customer
solutions powered by SAP NetWeaver It can help monitor on operating systems databases Java
application activities performance and logs It also supports the reporting of software and
configuration changes that can lead to malfunctions and errors
You must run one Solution Manager Diagnostics within your SAP solution landscape if you run
applications based on SAP NetWeaver systems with usage type AS Java Agents are responsible for
delivering the data from all productive hosts within your system landscape to the Solution Manager
Diagnostics system
CAUTION
SAP Support performs root-cause analysis on incoming incidents with Solution Manager
Diagnostics Not installing and configuring this support infrastructure results in a dramatically
reduced service level
Solution Manager Diagnostics is fully integrated into SAP Solution Manager 70
Solution Manager Diagnostics also contains Wily Introscope (Display Server and Agent part) for
measuring performance as well as to troubleshoot problems of Non-ABAP applications Wily Introscope
is heavily used for troubleshooting applications running on AS Java
SAP has signed a distribution agreement for Wily Introscope SAP customers are allowed to use this
tool in a preconfigured way
For more information about Solution Manager Diagnostics and an FAQ list see SAP Service Marketplace
at httpservicesapcomdiagnostics
5233 System Landscape Directory
The System Landscape Directory (SLD) of SAP NetWeaver is the central directory of system landscape
information relevant for the management of your software life-cycle
NOTE
Note that the abbreviation SLD is not intended to define a product since the System Landscape
Directory is part of SAP NetWeaver This abbreviation is solely intended to improve readability
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4356
The System Landscape Directory contains a description of your system landscape (that is software
components that are currently installed) and a repository of software components that can
theoretically be installed in your landscape (such as the software components available from SAP)
Since this data gets updated automatically the System Landscape Directory provides reliable and up-
to-date system landscape information with as little effort for you as possible In this way the System
Landscape Directory acts as a central information provider for SAP and third-party tools that use this
data to deliver the services you need to keep your landscape up and running
For the System Landscape Directory as part of an SAP NetWeaver PI 71 landscape consider the following
aspects
Part of SAP NetWeaver PI 71 is a new version of the System Landscape Directory It is automatically
included in every SAP NetWeaver 71 system with usage type AS Java It offers enhanced functions
such as a full automatic synchronization mechanism for all data stored in it That is both data
delivered by data suppliers and data entered or changed manually in the System Landscape
Directory can be synchronized automatically This synchronization offers the following
A fully automated mechanism so no user interaction is required and conflicts are resolved
automatically
Asynchronous propagation of information so some nodes may be down temporarily
Communication over HTTP protocol
Uni- and bi-directional synchronization
Depending on your use case the full automatic synchronization could significantly reduce manual
synchronization effort
For SAP NetWeaver PI 71 the configuration of the system landscape directory and its data suppliers
is already included in the standard implementation procedure with SAPinst For existing systems
you only have to perform some quick and easy configuration actions to start operating the system
landscape directory server in an AS Java system
For SAP NetWeaver PI 71 you have the following options concerning SLD
Option 1
Run SAP NetWeaver PI 71 against an existing SLD running on SAP NetWeaver 70 We only
recommend this for upgrades from SAP NetWeaver 70 if you have a central SLD in operation
not running on one of your PI systems
Option 2
Use the SLD included in an SAP NetWeaver PI 71 system We recommend this option for new
installations and upgrades from older releases than SAP NetWeaver 70 due to the enhanced
functions and improved performance of SLD 71
NOTE
If you already have a central SLD running on SAP NetWeaver 70 in operation you could run
two SLD versions in parallel ndash SLD running on SAP NetWeaver 71 for your PI systems and
SLD running on SAP NetWeaver 70 for all other systemsuse cases This way your SAP
5 System Landscape
52 Shared Services
4456 PUBLIC 2011-04-15
NetWeaver PI 71 systems would benefit from the new features while it would be easy to set
up and operate such an SLD landscape For this purpose you could use the new fully
automatic synchronization This feature enables the automatic forwarding of all SLD data
from an SLD running on SAP NetWeaver 70 to an SLD running on SAP NetWeaver 71 As a
result there is no need to adapt most existing systems as their SLD data suppliers could still
send their data to the central SLD In brief the following steps would be required
1 Put SLD in a PI system into operation (part of standard implementation procedure)
2 Configure PI systems to use the new SLD (part of standard implementation procedure
for new PI systems)
3 Set up the fully automatic synchronization from your old SLD to your new SLD
As soon as an upgrade or an installation of a standalone AS Java 71 system is available you
could move your central SLD also to SAP NetWeaver 71 Then you could optionally shift
your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems
Figure 8
We recommend that you use a Domain Name System (DNS) alias so that you are able to switch to
another System Landscape Directory easily For example if customers build a new landscape they
normally start with a sandbox environment Over time more and more environments are set up
Once the production environment is in place move the System Landscape Directory there To do
this you can configure a new System Landscape Directory in the production environment
synchronize it with the old System Landscape directory and switch to the new one
Topology
Apart from the considerations above the System Landscape Directory offers several topology options
with different grades of availability at the expense of low administration and operation effort There is
no generic rule therefore on how to set up a System Landscape Directory in your system landscape
To find the topology and synchronization strategy for the System Landscape Directory that fits your
requirements concerning the System Landscape Directory availability (and hence the availability of
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4556
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
without having to worry explicitly about technical details such as process or memory administration
multi-user capability database connections or similar issues These are provided in the basis services or
are integrated directly in the ABAP runtime The application development is similarly independent of
the underlying platform The application server decouples the application coding completely from the
operating system and database that are used
Dependencies
AS ABAP can be combined optionally with other usage types in one system
Application Server Java (AS Java)
Purpose
AS Java is used to provide the Java foundation of SAP NetWeaver PI using the Java Engine a Java EE-
compliant application server for running enterprise applications In addition to the pure Java EE
standard technologies the Java Engine implements complementary technologies such as Web Dynpro
or Web Services that are targeted at supporting large-scale real-business application development
projects
Dependencies
AS Java can be combined optionally with other usage types in one system
Process Integration (PI)
Purpose
PI consists of core components that model design automate and integrate processes in one or more
application systems For the integration of internal and cross-company processes PI is used to
incorporate all the functions of what was formerly known as Exchange Infrastructure (XI) In addition
PI contains core components for Business Process Management for application-embedded and
application-unbounded processes
The Advanced Adapter Engine is also part of usage type PI You use Advanced Adapter Engine to connect
to SAP systems (RFC adapter) and external systems You use the various adapters in Advanced Adapter
Engine to convert XML- and HTTP-based messages to the specific protocol and format required by
these systems and the other way around You can use the Advanced Adapter Engine that is part of
your PI system as a central Advanced Adapter Engine Optionally (for performance reasons) you can
install a non-central Advanced Adapter Engine [page 19] separately as a system with AS Java and parts of the
usage type PI on a separate host
Dependencies
PI requires AS ABAP and AS Java as prerequisites in the same system
For installing PI it is mandatory to have a dedicated PI system This applies to development quality
and production landscapes It is a prerequisite that no other system in your system landscape has a
higher release and enhancement package level than the PI system If you want to upgrade or install an
application in your system landscape you first have to make sure that the current release and
enhancement package level of the PI system is on the same level - if required you have to upgrade the
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1756
PI system first to the new or a higher release In a dedicated PI system this can be accomplished with a
minimum of downtime Also the PI system would not be affected by the downtime of other usage
types running in the same system
Configuration of Systems with Usage Types
Configuration information is available in the installation guides the configuration wizard and SAP
Solution Manager
In the Installation Guide ndash SAP NetWeaver PI 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt you find
initial technical configuration tasks This guide also informs you about how you can run the
configuration wizard and how you can access the configuration information in SAP Solution
Manager
For certain usage types configuration tasks can be applied by the configuration wizard after the
installation To do this you start the configuration wizard from SAP NetWeaver Administrator
The configuration steps for systems with usage types required for an use case are accessible through
SAP Solution Manager
To be able to use SAP Solution Manager for the configuration tasks you have to import the latest
SAP Solution Manager Implementation Content (Add-On ST-ICO) that is available for your SAP
Solution Manager release For more information see SAP Note 631042 (Release strategy for Implementation
Content (ST-ICO))
SAP Solution Manager Implementation Content is available on SAP Service Marketplace at
httpservicesapcomswdc Installations amp Upgrades Entry by Application Component SAP
Technology Components SAP Solution Manager ltReleasegt Content ST-ICO
In SAP Solution Manager you create a project and a project structure In the configuration phase
you select configuration structures with pre-delivered SAP content for your project You can find
the following different types of configuration tasks in SAP Solution Manager
Mandatory configuration tasks All configuration tasks that are mandatory for the standalone
engine or usage type
Optional configuration tasks Configuration tasks for areas where customers need to decide
if they want to use these functions (for example high availability or security settings)
Additional functions ndash configuration tasks Configuration tasks for functional units that are
used in certain use cases only
A marked checkbox in front of the configuration tasks indicates those configuration tasks that are
relevant for the use case you have chosen To configure ABAP systems SAP Solution Manager
offers executable configuration files (IMG activities)
For information about using SAP Solution Manager Content and creating a configuration guide
see the following documentation
httphelpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Implementing
and Upgrading SAP Solutions Configuration
3 SAP NetWeaver PI Overview
31 Installable Software Units
1856 PUBLIC 2011-04-15
How to Create a Configuration Guide using SAP Solution Manager available at http
servicesapcomsolutionmanager Media Library How-To Documents
Restrictions for Systems with Multiple Usage Types
If you have one system with multiple usage types be aware that we do not provide standard tools
to separate these usage types and distribute them to multiple systems at a later stage For example
if you have a system with usage types A and B you are not able to migrate it with SAP standard
tools into two systems one with usage type A only and the other with usage type B only
In addition we do not provide standard tools to merge multiple systems with different usage types
into one system with multiple usage types at a later stage
If you want to perform these tasks you require specific project support
The following figure shows that SAP standard system copy and migration tools do not support
you in separating or merging systems with usage types
Figure 4 No Support for Merging or Separating Systems with Usage Types
Although you can use one system for multiple usage types client restrictions apply for usage type
PI PI requires a dedicated client due to special PI requirements concerning the client pipeline
Whereas application client pipelines only send and receive messages the central PI pipeline can
also map messages to different formats before sending them
312 Standalone Engines
Standalone engines of SAP NetWeaver are additional installable software units They do not work as
full-blown systems of SAP NetWeaver but as standalone engines that provide a specific (server) function
in combination with one or more SAP NetWeaver systems
Standalone engines are not part of a usage type They do not run on AS ABAP or AS Java
The standalone engines that are available for SAP NetWeaver Process Integration are described in the
following
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1956
Gateway
It is possible to install an SAP instance of an SAP NetWeaver system based exclusively on a standalone
gateway This type of instance does not contain normal work process types (dialog background update
enqueue or spool) Only the gateway process (gwrd) is started If there is an SNA connection to an R
2 system gateway work processes (gwwp) are also started
SAP Conversion Agent by Informatica
SAP Conversion Agent by Informatica is a data conversion tool that enables you to create interfaces
between any data formats and XML-based systems SAP Conversion Agent can convert unstructured
semi-structured and structured formats to XML and the other way around The Conversion Agent
comprises the Conversion Agent Studio and the Conversion Agent Engine In the Conversion Agent
Studio you can develop and configure data conversions The Conversion Agent Engine executes the
data conversions
Search and Classification (TREX)
You can use Search and Classification with SAP NetWeaver PI to search for messages that were previously
indexed Message search using index provides additional methods of searching for specific messages In
addition to static header attributes you can also use adapter-specific message attributes and data from
the message payload for the search A requirement of this however is that the messages are indexed
first You can apply the index-based message search to one or all indexed components of an integration
landscape (domain) Integration Server Adapter Engines and ABAP business systems
For more information see the SAP Library [page 12] at Administratorrsquos Guide Technical Operations for SAP
NetWeaver Administration of SAP NetWeaver Systems Administering PI (Process Integration) Monitoring Index
Administration
Web Dispatcher
The Web Dispatcher lies between the Internet and your SAP system It is the entry point for HTTP(s)
requests into your system which consists of one or more SAP NetWeaver application servers As a
software web switch the Web dispatcher can reject connections or accept them When it accepts a
connection it balances the load to ensure an even distribution across the servers
You can use the Web dispatcher in ABAPJava systems and in pure Java systems as well as in pure ABAP
systems
It is also beneficial to use the Web Dispatcher if you do not need security functions (entry point in the
demilitarized zone (DMZ) SSL URL filtering) but you simply want to balance the load between
multiple SAP NetWeaver Application Server instances
Since Web Dispatcher is optional for every SAP system it is not contained in the system landscape and
the implementation sequence of the use case in this documentation
For more information see the SAP Library [page 12] at Function Oriented View Application Server Infrastructure
SAP Web Dispatcher
3 SAP NetWeaver PI Overview
31 Installable Software Units
2056 PUBLIC 2011-04-15
Advanced Adapter Engine
You use the Advanced Adapter Engine to connect to SAP systems (RFC adapter) and external systems
You use the various adapters in Advanced Adapter Engine to convert XML- and HTTP-based messages
to the specific protocol and format required by these systems and the other way around For specific
senderreceiver combinations messages can be processed without invoking the central Integration
Engine In principle you connect external systems using the adapters that are installed centrally or
non-centrally in Advanced Adapter Engine You can use the Advanced Adapter Engine that is part of
your PI system as a central Advanced Adapter Engine Optionally (for performance reasons) you can
install a non-central Advanced Adapter Engine separately as a system with AS Java and parts of the
usage type PI on a separate host
Adapter Engine (Java SE)
Adapter Engine (Java SE) is a separate software unit You can use it only if you have SAP NetWeaver
systems with usage type PI in your system landscape It has to be installed manually You use the Adapter
Engine (Java SE) to connect to external systems Using the various adapters in the Adapter Engine (Java
SE) XML and HTTP-based messages can be converted to the specific protocol and format required by
such systems and the other way around The Adapter Engine (Java SE) only provides some of these
adapters as a standalone version with restricted functions for operating systems that do not support
SAP NetWeaver PI 71 but that have at least a Java Runtime Environment 50 Therefore you should
use the Adapter Engine (Java SE) only if the platform prerequisites do not allow you to use the Advanced
Adapter Engine
SAP Partner Connectivity Kit
SAP Partner Connectivity Kit (PCK) runs on AS Java with parts of the usage type PI It enables a system
of a smaller company or subsidiary that does not run SAP NetWeaver PI to connect to your SAP
NetWeaver systems
313 Clients
Clients are additional installable programs or tools They reside either on local front-end PCs accessed
by users or on back-end systems where they act as client programs within an SAP NetWeaver system
landscape
The clients that you can use with SAP NetWeaver Process Integration are described in the following
sections
SAP GUI
NOTE
We recommend that you use the following versionsI
SAP GUI for Windows 710 (or higher) with the latest patch level
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 2156
SAP GUI for Java 710 (or higher) with the latest revision
The integrated SAP ITS 710
For more information about the SAP GUI family see SAP Service Marketplace at http
servicesapcomsapgui
SAP offers three different client applications for accessing ABAP applications in SAP systems (such as
SAP NetWeaver systems with usage type AS ABAP) This SAP GUI family consists of
SAP GUI for HTML
SAP GUI for HTML is based on the SAP integrated Internet Transaction Server (ITS) which is
included in the installation of SAP NetWeaver systems as of SAP NetWeaver 2004 On the client
side only a suitable browser (such as Internet Explorer 70 or Firefox 20) and a virtual machine are
required SAP ITS 620 is not compatible with SAP NetWeaver 71
SAP GUI for the Java environment (SAP GUI for Java)
SAP GUI for Java is a generic SAP GUI that covers a variety of platforms
For more information about the installation of SAP GUI for Java see the documentation Installation
Guide ndash SAP Front End
SAP GUI for the Windows environment (SAP GUI for Windows)
SAP GUI for Windows is SAPs universal client for accessing all SAP applications built on ABAP
technology It is available on the Microsoft Windows platform only and offers the broadest feature
set of all members of the SAP GUI family
For more information about the installation of SAP GUI for Windows see the Installation Guide ndash
SAP Front End
SAP NetWeaver Developer Studio
The SAP NetWeaver Developer Studio is SAPrsquos Integrated Development Environment (IDE) for Java
and is based on the open-source tools framework Eclipse 33 With the SAP NetWeaver Developer Studio
you can develop Java EE 5 applications from scratch using the built-in support for new technologies
such as EJB 30 and JSF 12
During the installation of the SAP NetWeaver Developer Studio several features are offered for
installation For SAP NetWeaver PI 71 only the following features are relevant
SAP NetWeaver Developer Studio Platform
SAP NetWeaver Developer Studio Java EE
NOTE
If you want to use one of the other features you need SAP NetWeaver Composition Environment
and a corresponding developers licence
For more information about the installation of SAP NetWeaver Developer Studio see the Installation
Guide ndash SAP NetWeaver Developer Studio 71 or Installation Guide ndash SAP NetWeaver Developer Studio 71 Including
Enhancement Package 1
3 SAP NetWeaver PI Overview
31 Installable Software Units
2256 PUBLIC 2011-04-15
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
SAP enhancement packages are a new way of delivering new functions for SAP NetWeaver This allows
a clear separation between the delivery of new functions on the one hand and corrections legal changes
and security updates on the other hand (in Support Package stacks) SAP enhancement packages are
cumulative an enhancement package always contains the functions of the corresponding predecessor
enhancement packages
Enhancement packages are maintained by their own Support Packages while the main release is in
maintenance
Benefits
SAP enhancement packages offer the following benefits
You have reduced effort for testing and no effort for training when applying Support Packages as
new features are only shipped with enhancement packages
Adding new functions between releases becomes predictable and controllable
New functions can be added successively in small steps There is no need to fully upgrade your
system to get new functions
You have minimal training effort when applying an enhancement package because existing
functions are not replaced
Implementation
There are the following ways to get an SAP NetWeaver system with the release level of SAP enhancement
package 1 for SAP NetWeaver Process Integration 71
New installation of SAP NetWeaver PI 71 including enhancement package 1 using the standard
installation tool SAPinst
Upgrade of an existing SAP NetWeaver system from a release lower than SAP NetWeaver PI 71 to
SAP NetWeaver PI 71 including enhancement package 1 For this you use the upgrade programs
SAPup (for ABAP) and SAPJup (for Java)
Installation of the enhancement package on an existing SAP NetWeaver PI 71 system
For this you use the Software Update Manager (SUM) The Software Update Manager evolved
from the previously used SAP Enhancement Package Installer The tool has been renamed to reflect
its broader use for example you can also use it for applying Support Package Stacks to your system
On the ABAP side the Software Update Manager uses a system cloning and switch procedure for
installing enhancement packages It installs a copy of the system the shadow system parallel to
the original system This shadow system is used to update the relevant software components and
to install the additional components while the original system is still in production operation At
a certain point during downtime the switch to the new system is made and afterwards any parts
of the original system that are no longer needed are deleted The enhancement package installation
in a Java system uses a deploy-based procedure that is no shadow system is used The Software
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2011-04-15 PUBLIC 2356
Update Manager requires a stack configuration file (xml file) as input file for the enhancement
package installation procedure This file lists all the packages that are to be installed in your systems
The stack configuration file is generated when you download the required packages
As the Software Update Manager is updated regularly we recommend to always use the latest
version It is delivered as part of the SL toolset For more information see http
servicesapcomsltoolset
For an overview of all required steps for the enhancement package installation process and
corresponding documents see Process Overview Installation of Enhancement Package 1 on an Existing SAP
Netweaver PI 71 System [page 28]
Content of SAP Enhancement Package 1 for SAP NetWeaver PI 71
With enhancement package 1 for SAP NetWeaver PI 71 new features are introduced and some existing
are changed The following is a selection of some of the most important enhancements
Enhanced design and modelling options in the Enterprise Services Repository
New services registry
Support for new Web services standard (Web Services Reliable Messaging)
New modules for the Advanced Adapter Engine
Use of shared memory of the ABAP Application Server for message processing
For more information about the changes see SAP Library [page 12] at Whatacutes new in SAP NetWeaver PI 71
ndash Release Notes
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2456 PUBLIC 2011-04-15
4 SOA-Based Integration Use Case
41 Overview
You can use SOA-based integration to set up the communication between service providers and service
consumers in both application-to-application and business-to-business scenarios and to execute
operate and monitor the communication at runtime SOA-based integration covers both direct (point-
to-point) as well as mediated (via an Integration Server) communication between service providers and
service consumers
The use case spans the whole life cycle of a SOA-based integration scenario including
Scenario modeling and service design in the Enterprise Services Repository
Implementation of the service provider and consumer in the back-end systems
Configuration and finally execution monitoring and operation of the integration scenario
For scenarios using Integration Server or broker-based communication the configuration of the
different connectivity options (for example SOAP RFC Web Services Industry standards and JDBC)
and their enhancements is covered
For more information see the following documents
Service-Enabling with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdnsoa-modeling
Getting Started
Service-Enabling a Legacy Application with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdn
soa-servicebus Getting Started
In the following you will find information about the installation of the involved software units
42 System Landscape
The following figure shows the system landscape for this use case
4 SOA-Based Integration Use Case
41 Overview
2011-04-15 PUBLIC 2556
Figure 5 SOA-Based Integration
It is mandatory to have a dedicated PI system This applies to development quality and production
landscapes
For PI it is a prerequisite that no other system in your system landscape has a higher release than
the PI system For exceptions to this rule see SAP Note 1043047 For example SAP XI 30 is compatible
with SAP NetWeaver 640 and 70 application systems since the same XI protocol is used Apart
from these exceptions if you want to upgrade or install an application in your system landscape
you first have to make sure that the PI system is on the same release level If required you have to
upgrade the PI system first to the new or a higher release
CAUTION
Although it should be technically possible to run an application system with a higher release
than your PI system in your system landscape this is not supported by SAP (apart from the
exceptions listed in SAP Note 1043047) Therefore you run such a landscape at your own risk
You can use the Advanced Adapter Engine that is part of your PI system as a central Advanced
Adapter Engine
Adapter Engine (Java SE) can be installed in a non-SAP Java environment However it only hosts
a subset of the adapter functionality is only supported for compatibility reasons and should be
used only if this is a precondition in your environment
Optionally you can use the Change Management Service (CMS) of an SAP NetWeaver 70 system
with usage type DI to transport design objects and repository objects For more information see
the SAP Library [page 12] at Administratoracutes Guide Technical Operations for SAP NetWeaver Administration
of SAP NetWeaver Systems PI (Process Integration) Software Logistics Transporting ESR Content and Objects
of Integration Directory PI Transports Using the Change Management Service (CMS)
Smaller business partners or subsidiaries that do not run SAP NetWeaver install SAP Partner
Connectivity Kit in their system landscape SAP Partner Connectivity Kit enables XML document
4 SOA-Based Integration Use Case
42 System Landscape
2656 PUBLIC 2011-04-15
exchange between your SAP NetWeaver systems and the partner systems Since SAP Partner
Connectivity Kit gets installed in their system landscape it is not shown in the system landscape
figure above
The AS ABAP system acts as an application and service provider For Java Web Services you also
require AS Java In addition you require SAP NetWeaver Developer Studio on the client side as a
development environment
The Web service client can be either an SAP or a non-SAP application For example an AS ABAP
system or a Web browser could act as application or service consumer
You can install SAP Conversion Agent by Informatica in the system with usage type PI or on a host
where SAP Partner Connectivity Kit is installed or on a host where neither usage type PI nor SAP
Partner Connectivity Kit is installed
43 Implementation Sequence
Procedure
To install this use case perform the steps listed in the following table
StepAction[Corresponding Documentation] Remarks
1 Make sure that you have performed the preparation steps You have planned your system landscape [page 33]
(that is you have decided how many systems you require how you want to use each of these systems and which standalone engines and clients you require)
With the help of your hardware partner you have mapped your systems and standalone engines to properly sized hosts
You have planned and installed shared services [page 35]
2 Installation of system with usage type PI (includes the installation of AS ABAP and AS Java)
NOTE
For usage type PI a Unicode installation is mandatory
[Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt]
If you want to use the features of enhancement package 1 use the direct installation of SAP NetWeaver PI 71 including enhancement package 1
Make sure that you perform the configuration steps as described in the installation guide For certain usage types configuration tasks can be applied by the configuration wizard These configuration tasks as well as any additional configuration steps for your use case are listed in SAP Solution Manager For more information
4 SOA-Based Integration Use Case
43 Implementation Sequence
2011-04-15 PUBLIC 2756
StepAction[Corresponding Documentation] Remarks
see the Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt
3 Install the Adapter Engine (Java SE) engines if required[Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
4 To integrate small business partners and subsidiaries the business partners or subsidiaries install SAP Partner Connectivity Kit running on AS Java with parts of usage type PI in the business partners or subsidiarys system landscape[Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
5 Install SAP Conversion Agent by Informatica if required[SAP Library [page 12] at Function-Oriented View Process Integration SAP Conversion Agent by Informatica Deploying and Using Conversion Agent ]
6 Installation of clients SAP GUI
[Installation Guide ndash SAP Front End]
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
The process sequences give a comprehensive overview of the steps relevant for the enhancement
package installation on an existing SAP NetWeaver PI 71 system
The process sequence is divided into a planning phase and an implementation phase Each step in both
phases contains references to the corresponding documentation to ensure that you can easily find the
information you need
Process
NOTE
To download the enhancement package files and required Support Packages you require the SAP
Solution Manager Maintenance Optimizer You have the following options
Manual Selection
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2856 PUBLIC 2011-04-15
You manually select the required files from SAP Service Marketplace at http
servicesapcomswdc using the SP Stack Application You use the Maintenance Optimize
only to approve the packages which is a prerequisite for the download
Automatic Calculation
The Maintenance Optimizer supports the download of a consistent queue that includes all
necessary Support Packages and enhancement packages In addition SAP Solution Manager
calculates a valid import queue for the selected SAP system and generates the enhancement
package stack configuration file that you require for the installation
As a prerequisite the system that you want to update needs to be maintained correctly in
SAP Solution Manager System Landscape As the Maintenance Optimizer uses this data for
the calculation it is crucial that the data is up-to-date In addition the SAP Solution Manager
system requires a Minimum Support Package level (see below)
Planing PhaseStep Description Documentation
Hardware amp Software Prerequisites
Check which platforms are supported for your target release (OSDB dependencies)
Product Availability Matrix (PAM) at httpservicesapcompam
Check which hardware sizing is required for your target release
Sizing information at httpservicesapcomsizing
Solution Manager Prerequisites
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of the required software packages you have to make sure that your SAP Solution Manager system has the required Support Package levelAt least SAP Solution Manager 70 EHP1 Support Package Stack 17 is required We recommend to use SAP Solution Manager 70 EHP1 Support Package Stack 23Check if you need to do an update or upgrade of your SAP Solution ManagerMake sure that you run the guided procedure SOLMAN_SETUP after every installation or update of SAP Solution Manager and that it completes successfully
For upgrades from source release SAP Solution Manager 31 and 32Upgrade Guide ndash SAP Solution Manager 70 incl Enhancement Package 1For updates from SAP Solution Manager 70Update Guide SAP Enhancement Package 1 for SAP Solution Manager 70Follow-up activities after an Support Package Stack update or enhancement package updateSolution Operations Guide ndash SAP Solution Manager 70 EHP1 section Software Change Management All guides are available at http
servicesapcom instguides SAP Components SAP Solution Manager -gt Release 70 EHP 1
Implementation PhaseStep Description Documentation
1Solution Manager Preparation
Configure the SAP Solution Manager Maintenance Optimizer
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of software packages make sure your
Configuration of Maintenance Optimizer http
helpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Change Request Management and Change ControlMaintenance Optimizer
Prerequisites
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 2956
Implementation PhaseStep Description Documentation
system landscape data in SAP Solution Manager is maintained correctlyLandscape Verification 10 which is an add-on to SAP Solution Manager can support you in maintaining your system landscape data The use of this tool is optional
Landscape Verification http
wwwsdnsapcom irj
sdn alm-update-
management link Landscape Verification under Related Areas on Upgrade and Update Management (in the right column)
SAP Note 1468605 (Installation of Landscape Verification)
Maintaining System Landscape Information [page 47]Note that the information provided in this section is based on SAP Solution Manager 70 EHP1 SP23
2System Preparation
Prepare your system as described in the documentation for example perform OS DB specific preparations and the PI-specific preparations
Update Guide ndash Update of SAP Systems with Software Update Manager sections Planning and Preparation
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
3Software Download
Select and download the software packages in either of the following ways Automatic calculation Create
a maintenance transaction in the Maintenance Optimizer and choose the Calculate Files Automatically option
Manual Selection Create a maintenance transaction in the Maintenance Optimizer and choose the Select Files Manually option You then can select the files manually using the SP Stack application in SAP Service Marketplace
NOTE
You have to download the stack configuration file manually after you have selected all files in the SP Stack
httphelpsapcom SAP Solutions SAP Solution Manager
SAP Solution Manager 70 EHP1 ltSPgtChange Request Management and
Change Control Maintenance Optimizer Maintenance Procedure Scenarios
For information about the automatic calculation see Maintenance Transaction with Installation of an Enhancement PackageFor information about the manual selection and approval process see section Approve and Download Files in Download Basket
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
3056 PUBLIC 2011-04-15
Implementation PhaseStep Description Documentation
application Choose Generate Stack XML and save the file
4Enhancement Package Installation
Run Software Update Manager to update your system with the selected software packages
Update Guide ndash Update of SAP Systems with Software Update Manager
5Follow-Up Steps
Perform technical and PI-specific follow-up activities after the enhancement package installation is done
Update Guide ndash Update of SAP Systems with Software Update Manager section Follow-Up Activities
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
6Configuration
Configure newly installed enhancement package functions using SAP Solution Manager content
See Systems with Usage Types [page 16] section Configuration of Systems with Usage Types
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 3156
This page is left blank for documents that are printed on both sides
5 System Landscape
51 Planning Your System Landscape
The installable software units that make up your system landscape depend on the functions that you
want to implement For information about the features see systems [page 16] standalone engines [page 19]
and clients [page 21]
In addition you have to determine the required shared services [page 35] (such as SAP Solution Manager
or SAP NetWeaver Administrator) that run on central systems in your system landscape and the
landscape aspects relevant for their implementation
In the following you will find general information that you should consider when planning your system
landscape
Sizing
You have to map systems and standalone engines to hosts after you have a clear picture of the following
Which systems and standalone engines you require
How many systems you require and how you want to use each of these systems
NOTE
No general guideline can be given for the sizing of your landscape since this relies heavily on your
requirements You should therefore perform this task together with your hardware partner and
your technical consultant
For information about sizing your systems you can use the following information sources
Your first point of reference is the Quick Sizer
SAP built the Quick Sizer as an online sizing questionnaire Internet application in close cooperation
with its hardware partners This tool delivers general sizing categories based on your volume load
estimates The results provide an objective basis for sizing independent of platform and
configuration
For more information see SAP Service Marketplace at
httpservicesapcomsizing for the SAP NetWeaver PI 71 sizing guide available under
Sizing Guidelines Business Suite amp Services
httpservicesapcomquicksizer for more information and access to the tool itself
Also consider the following important aspects concerning sizing
High availability
5 System Landscape
51 Planning Your System Landscape
2011-04-15 PUBLIC 3356
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Technical Infrastructure High Availability
Unicode
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Internationalization
Contact your hardware partner to find out the appropriate number of sized hosts
The platform-independent abstract results of the Quick Sizer can be used by any of our hardware
partners to create a concrete offer SAP itself does not make any hardware recommendations the
responsibility for sizing and detailed hardware configuration lies with the hardware partners
Figure 6 Example of Mapping of Systems and Standalone Engines to Three Hosts
NOTE
Optionally you could also distribute single systems to multiple hosts For example you could
decide to install the database instance of an SAP system on a separate host for performance
reasons or distribute other system instances to achieve high availability
To provide a mapping that fits your required functions and performance your hardware partner
and your technical consultant have to identify the number of required instances of SAP NetWeaver
find out how to distribute these instances to hosts and what functions will run on which instance
Therefore the hardware partner and the technical consultant have to consider many different
aspects such as
Number of required SAPS (SAP Application Benchmark Performance Standard) for each
system (provided by Quick Sizer)
Landscape-relevant aspects concerning security For more information see the SAP Security
Guide in the SAP Library [page 12] at Administratoracutes Guide Security Guide
Landscape-relevant aspects concerning scalability high availability operation and software
life-cycle management
5 System Landscape
51 Planning Your System Landscape
3456 PUBLIC 2011-04-15
For more information about relevant aspects for the mapping of systems to hosts see the document
Technical Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
Scaling and Distribution Options
You may need to design your system landscape for a large number of users SAP NetWeaver PI offers
you different means of scalability The following list provides you with some examples
You could install multiple systems of one type and use them for different purposes
You could scale every system by installing dialog instances or by distributing the database instance
For more information about distribution options on the instance level see the Technical
Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
For every SAP system you could additionally install Web Dispatcher For more information see
the SAP Library [page 12] at FunctionndashOriented View Application Server Infrastructure SAP Web
Dispatcher
You could further distribute certain standalone engines ndash for example Search and Classification
(TREX) is based on a flexible architecture that supports a distributed installation For more
information see the Technical Infrastructure Guide ndash SAP NetWeaver PI 71 available in SAP Service
Marketplace at httpservicesapcominstallNWPI71
52 Shared Services
You normally run shared services on central systems in your system landscape The following features
could be used for SAP NetWeaver Process Integration to realize shared services
SAP Solution Manager
Used to implement train test maintain monitor control change and manage incidents of your
SAP solution system landscape (open end-to-end application management)
As of SAP Solution Manager (70) 40 Support Package 15 SAP Solution Manager has become the
platform for SAPs end-to-end solution operations strategy Functions for complete application
management has been combined with administrative tools and has been merged in newly created
role based work centers
NOTE
Be aware that you require an SAP Solution Manager system to install or upgrade to SAP
NetWeaver 70 and higher An SAP Solution Manager system is required to generate the SAP
Solution Manager key needed during the installation or upgrade process Without this key
the installation or upgrade process cannot continue
For SAP NetWeaver Process Integration you require SAP Solution Manager 70
For more information see SAP Note 805390
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3556
Solution Manager Diagnostics
An integral part of SAP Solution Manager that is running as a Java application on the Java stack of
SAP Solution Manager 70 Solution Manager Diagnostics is used to analyze the root cause of
incidents in your landscape in an efficient and safe way Before Go-Live Solution Manager
Diagnostics has to be set up and made accessible remotely
SAP NetWeaver Administrator
SAP NetWeaver Administrator is the central administration component which is used for
monitoring and administering Java applications It is included in SAP NetWeaver systems with AS
Java
SAP NetWeaver Administrator exists in the following flavors
A local mode which runs out of the box and which focuses on administrating the underlying
SAP NetWeaver AS Java
NOTE
For a SAP NetWeaver PI 71 it has a special role which you need to activate using a
configuation wizard
A central mode which has to be configured before use and which deals with the system
landscape management
SAP has decided to merge the central mode of SAP NetWeaver Administrator into the new work
centers available as of SAP Solution Manager 70 SP 15 Thus it can be used in an administrative
context together with non-Java-based administration tools Although the central mode of SAP
NetWeaver Administrator will be still available for some time SAP will not develop this tool any
further SAP focuses on optimizing the administrative work centers of SAP Solution Manager
instead
The local mode of SAP NetWeaver Administrator stays untouched It is available for current and
future releases of SAP NetWeaver
SAP Central Process Scheduling by Redwood
SAP Central Process Scheduling application by Redwood enables central job scheduling and job
monitoring of current and old releases of AS ABAP systems (as of Basis Release 31) This application
is fully integrated in SAP NetWeaver Depending on the business needs SAP business applications
are the initial trigger for scheduled activities You can now manage jobs and job chains conveniently
using a graphical user interface
System Landscape Directory
The System Landscape Directory is the central directory of system landscape information relevant
for the management of your software life-cycle It contains a description of your system landscape
(that is software components that are currently installed) and a repository of software components
that can theoretically be installed in your landscape (such as the software components available
from SAP)
Adaptive Computing Controller
5 System Landscape
52 Shared Services
3656 PUBLIC 2011-04-15
The Adaptive Computing Controller enables users to control an adaptive computing landscape
from a single point through observation operation and dynamic resource distribution With
adaptive computing hardware software and system services are able to adapt to changing business
needs In the Adaptive Computing Controller the run-time data of logical and physical landscapes
can be monitored application services can be startedstoppedrelocated and hardware resources
can be assigned to application services The operation can also be mass executed and be planned as
tasks to be executed
For more information about the installation of the Adaptive Computing Controller tool see the
document Installation Guide ndash Adaptive Computing Controller in SAP NetWeaver 71 available on SAP Service
Marketplace at httpservicesapcominstallNWPI71
For more information about Adaptive Computing in general see httpsdnsapcomirj
sdnadaptive
521 Use Cases
You can use the applications and tools described above for use cases that are normally performed
centrally The following sections describe these use cases
5211 End-to-End Solution Operations
Running business applications through their complete life-cycle is a challenge Therefore SAP has
started the Run SAP methodology for implementing End-to-End Solution Operations Based on a set
of SAP standards a roadmap and a package for training and certification Run SAP helps customers to
facilitate End-to-End Solution Operations
You can download the SAP standards for Solution Operations from SAP Service Marketplace at http
servicesapcomsupportstandards They describe roles customers typically have in their IT
environment For optimal role support SAP has grouped existing and new functions in SAP Solution
Manager work centers as of SAP Solution Manager 70 Support Package 15 Operations aspects are fully
covered by adding administrative functions for SAP NetWeaver as well Work centers are ABAP Web
Dynpro-based applications They offer the following advantages
Easy to use similar look and feel
Context transfer while jumping from one work center into another
Logical grouping of tools for a certain area
Simple authorization concept
Easy to expand
Each IT role belongs to one or more work centers For instance the Technical Administrator IT role is
covered by the work centers for System Monitoring System Administration and Landscape Management
The following work centers are available
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3756
Business Process Operations
Change Management
Root Cause Analysis
Implementation Upgrade
Incident Management
Test Management
Job Management
System Landscape Management
Solution Documentation Assistant
SAP Engagement and Service Delivery
SAP Solution Manager Administration
System Administration
System Monitoring
My Home is the central point of access to all important data of almost all work centers in SAP Solution
Manager
5212 Support Infrastructure
A key requirement for effective support of IT solutions is the ability to perform root cause analysis with
speed and efficiency
With SAP Solution Manager SAP has long had an infrastructure in place for its ABAP applications that
efficiently supports SAP solutions This helps ensure the high availability and smooth running of
business processes For more information see the SAP Solution Manager section
With Solution Manager Diagnostics this knowledge has been extended to Java applications If for
example homegrown Java applications cause instability Solution Manager Diagnostics helps trace the
cause to eradicate the problem rapidly Solution Manager Diagnostics is fully integrated into SAP
Solution Manager 70 Solution Manager Diagnostics also contains two third-party tools CArsquos Wily
Introscopereg for measuring performance as well as troubleshooting problems of the Java EE Engine
and applications running on it and Mercury Loadrunnerreg which enables SAP Support to produce a
defined load in the SAP solution landscape remotely For more information see Solution Manager
Diagnostics [page 43]
The support infrastructure provides SAP Support with safe access to your productive landscape for safe
root cause analysis so ensuring that SAP Support does not change your landscape inadvertently You
require a support infrastructure to run SAP NetWeaver
The following figure shows the overall infrastructure including SAP NetWeaver administration tools
that are used by administrators or operators at the customer site
5 System Landscape
52 Shared Services
3856 PUBLIC 2011-04-15
Landscape Aspects
If you use SAP NetWeaver Process Integration 71 productively besides SAP Solution Manager (as a
central support platform) you have to set up Solution Manager Diagnostics for supportability reasons
Implementation Sequence
For information about the implementation of the support infrastructure see the document Master
Guide ndash SAP Solution Manager 70 available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution Manager ltReleasegt
5213 Collection of Landscape Data
Amongst other applications and services the support infrastructure and the SAP NetWeaver
administration tools rely on system landscape data
For SAP NetWeaver PI 71 you have to run non-ABAP components in your solution landscape
Therefore the System Landscape Directory is mandatory The landscape data that is automatically
gathered by the System Landscape Directory is replicated to SAP Solution Manager There are several
topology options for the System Landscape Directory They offer different grades of availability
administration and operation effort
For more information see the System Landscape Directory section
5214 Authentication and Single Sign-On
Before implementing your system landscape plan how to implement authentication and how to
integrate different systems into a Single Sign-On landscape Single Sign-On reduces complexity for end
users saving them valuable time while also reducing administration effort for resetting passwords
thereby contributing to TCO reduction
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
5215 Integrated User and Access Management
In a system landscape containing a combination of ABAP and Java components we recommend that
you integrate your user and access management so that you can use the same user data across different
systems administer this data centrally and control access to data SAPs mature fine-grained
authorization concept allows detailed control of access rights SAP NetWeaver provides both ABAP and
Java-based user management solutions The user management solution that you use to administer
your user data depends on factors such as the type of systems that are running in your landscape
If you want to use central user administration we recommend that you run it in a non-production
system If you do not have a central user administration yet you can for example realize it in the SAP
Solution Manager system
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3956
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
522 Examples for the Overall System Landscape of Shared Services
In this section we provide examples of how shared services can be set up depending on the system
landscape they are intended for The following examples aggregate the landscape aspects given in the
Use Cases section
NOTE
The following sections and the figure mostly do not show information about the life-cycle of
shared services For example you may also need a development and testquality assurance system
for SAP Solution Manager You should consider this aspect in addition to the information given
in this section based on your requirements
Small and MediumndashSized Customer Landscapes with Java
As you use Java productively for SAP NetWeaver PI 71 besides SAP Solution Manager you have to set
up additional components for optimal monitoring administration and support Solution Manager
Diagnostics and the central mode of SAP NetWeaver Administrator are already fully integrated into
SAP Solution Manager 70 as the central operations hub For SAP Process Integration you must also
set up SAP NetWeaver Administrator with a special role
We recommend that you do not install SAP Central Process Scheduling in the SAP Solution Manager
system You have to set up and operate the system which hosts your productive scheduler as a mission
critical system
In the SAP Solution Manager system you should set up a local System Landscape Directory in addition
to a central runtime System Landscape Directory This way you have a clear separation between your
management system (SAP Solution Manager) and managed systems in your landscape In addition
SAP Solution Manager then does not rely on a System Landscape Directory running in the production
environment For this setup configure the SLD data suppliers of your SAP Solution Manager system
to send data to the central runtime System Landscape Directory In addition configure automatic
bridge forwarding from your runtime System Landscape Directory to the local System Landscape
Directory For more information see the Planning Guide - System Landscape Directory
If you want to use a central system for Adobe Document Services we recommend that you install a
dedicated system for this purpose in your production environment For detailed information about
the sizing of the system for the different use cases see the Sizing Guide for Adobe Document Services at
SAP Service Marketplace at httpservicesapcomsizing Sizing Guidelines Solutions amp
Platform
We recommend that you start with this centralized SAP Solution Manager approach as depicted in the
following figure
5 System Landscape
52 Shared Services
4056 PUBLIC 2011-04-15
Figure 7 Single SAP Solution Manager Landscape
Large Customer Landscapes with Java
Large customers who have environments in their landscape that are large and distributed administered
by different groups or separated for security reasons can consider a distributed operations setup In
addition to the centralized setup described for small- and medium-sized customers above large
customers can put parts of the central management functions on extra hosts or systems for performance
or policy reasons You have the following options for a distributed setup
You may set up an extra system or client for Central User Administration (CUA)
The Change and Transport System (CTS) can run on an extra system However it is not
performance- or data-intensive
You may set up an extra system for central CCMS monitoring Depending on the customizing
and on the landscape size central CCMS may generate a lot of system load You can connect a
separate central CCMS to SAP Solution Manager for displaying alerts in the alert inbox of the System
Monitoring work center
You can use a separate SAP NetWeaver 70 system with usage type BI together with SAP Solution
Manager This may make sense with respect to the amount of landscape management data that is
stored for reporting purposes The amount of data strongly depends on the data granularity
storage time frame and landscape size
You can easily put Wily Introscope Enterprise Manager on an separate host
Other aspects described above for small- and medium-customers (such as the setup of the System
Landscape Directory) are also valid for large customers
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4156
523 Feature Details
This section provides further information about the features described above
5231 SAP Solution Manager
SAP provides you with SAP Solution Manager as the strategic application management platform and
to enable the collaboration between you and SAP You need to install at least one productive SAP
Solution Manager in your system landscape To ensure the availability of this application management
platform an SAP Solution Manager system is technically required to install or upgrade to SAP
NetWeaver 70 or higher If you are already using SAP Solution Manager you can also use it to manage
the solution you build with SAP NetWeaver In this case we highly recommend that you update SAP
Solution Manager to the latest version
As of SAP Solution Manager 70 SP15 you can use the newly created work centers
NOTE
During the SAP system installation or upgrade process you are prompted to enter the SAP
Solution Manager key An SAP Solution Manager system is required to generate this key Without
this key the installation or upgrade process cannot continue
You may generate all needed keys for your entire system landscape (development quality
assurance and production system) in one SAP Solution Manager system In case you plan to install
several solution landscapes (for example in different countries) one SAP Solution Manager
system is still sufficient
For more information see SAP Note 805390
It is possible to install multiple SAP Solution Managers If you do so they should host separate business
solutions
If you want to reduce the risk of unavailability you should not install SAP Solution Manager as a central
component Instead you can operate a 2-system-landscape with both a test and production
environment of SAP Solution Manager (especially if you are using time-critical functions like Support
Desk) If you also develop your own content a 3-system-landscape with a development test and
production environment is recommended
For more information about SAP Solution Manager see the following table
Topic Where to Find More Information
System infrastructure scenarios installation and configuration of SAP Solution Manager
Master Guide ndash SAP Solution Manager available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution ManagerltReleasegt
Benefits and usage scenarios SAP Solution Manager ndash Learning Maps available on SAP Service Marketplace at http
5 System Landscape
52 Shared Services
4256 PUBLIC 2011-04-15
Topic Where to Find More Informationservicesapcomrkt-solman or https
servicesapcomsolutionmanager
Additional information See SAP Service Marketplace at http
servicesapcomsolutionmanager
5232 Solution Manager Diagnostics
Solution Manager Diagnostics provides efficient and safe root-cause analysis of incidents in customer
solutions powered by SAP NetWeaver It can help monitor on operating systems databases Java
application activities performance and logs It also supports the reporting of software and
configuration changes that can lead to malfunctions and errors
You must run one Solution Manager Diagnostics within your SAP solution landscape if you run
applications based on SAP NetWeaver systems with usage type AS Java Agents are responsible for
delivering the data from all productive hosts within your system landscape to the Solution Manager
Diagnostics system
CAUTION
SAP Support performs root-cause analysis on incoming incidents with Solution Manager
Diagnostics Not installing and configuring this support infrastructure results in a dramatically
reduced service level
Solution Manager Diagnostics is fully integrated into SAP Solution Manager 70
Solution Manager Diagnostics also contains Wily Introscope (Display Server and Agent part) for
measuring performance as well as to troubleshoot problems of Non-ABAP applications Wily Introscope
is heavily used for troubleshooting applications running on AS Java
SAP has signed a distribution agreement for Wily Introscope SAP customers are allowed to use this
tool in a preconfigured way
For more information about Solution Manager Diagnostics and an FAQ list see SAP Service Marketplace
at httpservicesapcomdiagnostics
5233 System Landscape Directory
The System Landscape Directory (SLD) of SAP NetWeaver is the central directory of system landscape
information relevant for the management of your software life-cycle
NOTE
Note that the abbreviation SLD is not intended to define a product since the System Landscape
Directory is part of SAP NetWeaver This abbreviation is solely intended to improve readability
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4356
The System Landscape Directory contains a description of your system landscape (that is software
components that are currently installed) and a repository of software components that can
theoretically be installed in your landscape (such as the software components available from SAP)
Since this data gets updated automatically the System Landscape Directory provides reliable and up-
to-date system landscape information with as little effort for you as possible In this way the System
Landscape Directory acts as a central information provider for SAP and third-party tools that use this
data to deliver the services you need to keep your landscape up and running
For the System Landscape Directory as part of an SAP NetWeaver PI 71 landscape consider the following
aspects
Part of SAP NetWeaver PI 71 is a new version of the System Landscape Directory It is automatically
included in every SAP NetWeaver 71 system with usage type AS Java It offers enhanced functions
such as a full automatic synchronization mechanism for all data stored in it That is both data
delivered by data suppliers and data entered or changed manually in the System Landscape
Directory can be synchronized automatically This synchronization offers the following
A fully automated mechanism so no user interaction is required and conflicts are resolved
automatically
Asynchronous propagation of information so some nodes may be down temporarily
Communication over HTTP protocol
Uni- and bi-directional synchronization
Depending on your use case the full automatic synchronization could significantly reduce manual
synchronization effort
For SAP NetWeaver PI 71 the configuration of the system landscape directory and its data suppliers
is already included in the standard implementation procedure with SAPinst For existing systems
you only have to perform some quick and easy configuration actions to start operating the system
landscape directory server in an AS Java system
For SAP NetWeaver PI 71 you have the following options concerning SLD
Option 1
Run SAP NetWeaver PI 71 against an existing SLD running on SAP NetWeaver 70 We only
recommend this for upgrades from SAP NetWeaver 70 if you have a central SLD in operation
not running on one of your PI systems
Option 2
Use the SLD included in an SAP NetWeaver PI 71 system We recommend this option for new
installations and upgrades from older releases than SAP NetWeaver 70 due to the enhanced
functions and improved performance of SLD 71
NOTE
If you already have a central SLD running on SAP NetWeaver 70 in operation you could run
two SLD versions in parallel ndash SLD running on SAP NetWeaver 71 for your PI systems and
SLD running on SAP NetWeaver 70 for all other systemsuse cases This way your SAP
5 System Landscape
52 Shared Services
4456 PUBLIC 2011-04-15
NetWeaver PI 71 systems would benefit from the new features while it would be easy to set
up and operate such an SLD landscape For this purpose you could use the new fully
automatic synchronization This feature enables the automatic forwarding of all SLD data
from an SLD running on SAP NetWeaver 70 to an SLD running on SAP NetWeaver 71 As a
result there is no need to adapt most existing systems as their SLD data suppliers could still
send their data to the central SLD In brief the following steps would be required
1 Put SLD in a PI system into operation (part of standard implementation procedure)
2 Configure PI systems to use the new SLD (part of standard implementation procedure
for new PI systems)
3 Set up the fully automatic synchronization from your old SLD to your new SLD
As soon as an upgrade or an installation of a standalone AS Java 71 system is available you
could move your central SLD also to SAP NetWeaver 71 Then you could optionally shift
your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems
Figure 8
We recommend that you use a Domain Name System (DNS) alias so that you are able to switch to
another System Landscape Directory easily For example if customers build a new landscape they
normally start with a sandbox environment Over time more and more environments are set up
Once the production environment is in place move the System Landscape Directory there To do
this you can configure a new System Landscape Directory in the production environment
synchronize it with the old System Landscape directory and switch to the new one
Topology
Apart from the considerations above the System Landscape Directory offers several topology options
with different grades of availability at the expense of low administration and operation effort There is
no generic rule therefore on how to set up a System Landscape Directory in your system landscape
To find the topology and synchronization strategy for the System Landscape Directory that fits your
requirements concerning the System Landscape Directory availability (and hence the availability of
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4556
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
PI system first to the new or a higher release In a dedicated PI system this can be accomplished with a
minimum of downtime Also the PI system would not be affected by the downtime of other usage
types running in the same system
Configuration of Systems with Usage Types
Configuration information is available in the installation guides the configuration wizard and SAP
Solution Manager
In the Installation Guide ndash SAP NetWeaver PI 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt you find
initial technical configuration tasks This guide also informs you about how you can run the
configuration wizard and how you can access the configuration information in SAP Solution
Manager
For certain usage types configuration tasks can be applied by the configuration wizard after the
installation To do this you start the configuration wizard from SAP NetWeaver Administrator
The configuration steps for systems with usage types required for an use case are accessible through
SAP Solution Manager
To be able to use SAP Solution Manager for the configuration tasks you have to import the latest
SAP Solution Manager Implementation Content (Add-On ST-ICO) that is available for your SAP
Solution Manager release For more information see SAP Note 631042 (Release strategy for Implementation
Content (ST-ICO))
SAP Solution Manager Implementation Content is available on SAP Service Marketplace at
httpservicesapcomswdc Installations amp Upgrades Entry by Application Component SAP
Technology Components SAP Solution Manager ltReleasegt Content ST-ICO
In SAP Solution Manager you create a project and a project structure In the configuration phase
you select configuration structures with pre-delivered SAP content for your project You can find
the following different types of configuration tasks in SAP Solution Manager
Mandatory configuration tasks All configuration tasks that are mandatory for the standalone
engine or usage type
Optional configuration tasks Configuration tasks for areas where customers need to decide
if they want to use these functions (for example high availability or security settings)
Additional functions ndash configuration tasks Configuration tasks for functional units that are
used in certain use cases only
A marked checkbox in front of the configuration tasks indicates those configuration tasks that are
relevant for the use case you have chosen To configure ABAP systems SAP Solution Manager
offers executable configuration files (IMG activities)
For information about using SAP Solution Manager Content and creating a configuration guide
see the following documentation
httphelpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Implementing
and Upgrading SAP Solutions Configuration
3 SAP NetWeaver PI Overview
31 Installable Software Units
1856 PUBLIC 2011-04-15
How to Create a Configuration Guide using SAP Solution Manager available at http
servicesapcomsolutionmanager Media Library How-To Documents
Restrictions for Systems with Multiple Usage Types
If you have one system with multiple usage types be aware that we do not provide standard tools
to separate these usage types and distribute them to multiple systems at a later stage For example
if you have a system with usage types A and B you are not able to migrate it with SAP standard
tools into two systems one with usage type A only and the other with usage type B only
In addition we do not provide standard tools to merge multiple systems with different usage types
into one system with multiple usage types at a later stage
If you want to perform these tasks you require specific project support
The following figure shows that SAP standard system copy and migration tools do not support
you in separating or merging systems with usage types
Figure 4 No Support for Merging or Separating Systems with Usage Types
Although you can use one system for multiple usage types client restrictions apply for usage type
PI PI requires a dedicated client due to special PI requirements concerning the client pipeline
Whereas application client pipelines only send and receive messages the central PI pipeline can
also map messages to different formats before sending them
312 Standalone Engines
Standalone engines of SAP NetWeaver are additional installable software units They do not work as
full-blown systems of SAP NetWeaver but as standalone engines that provide a specific (server) function
in combination with one or more SAP NetWeaver systems
Standalone engines are not part of a usage type They do not run on AS ABAP or AS Java
The standalone engines that are available for SAP NetWeaver Process Integration are described in the
following
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1956
Gateway
It is possible to install an SAP instance of an SAP NetWeaver system based exclusively on a standalone
gateway This type of instance does not contain normal work process types (dialog background update
enqueue or spool) Only the gateway process (gwrd) is started If there is an SNA connection to an R
2 system gateway work processes (gwwp) are also started
SAP Conversion Agent by Informatica
SAP Conversion Agent by Informatica is a data conversion tool that enables you to create interfaces
between any data formats and XML-based systems SAP Conversion Agent can convert unstructured
semi-structured and structured formats to XML and the other way around The Conversion Agent
comprises the Conversion Agent Studio and the Conversion Agent Engine In the Conversion Agent
Studio you can develop and configure data conversions The Conversion Agent Engine executes the
data conversions
Search and Classification (TREX)
You can use Search and Classification with SAP NetWeaver PI to search for messages that were previously
indexed Message search using index provides additional methods of searching for specific messages In
addition to static header attributes you can also use adapter-specific message attributes and data from
the message payload for the search A requirement of this however is that the messages are indexed
first You can apply the index-based message search to one or all indexed components of an integration
landscape (domain) Integration Server Adapter Engines and ABAP business systems
For more information see the SAP Library [page 12] at Administratorrsquos Guide Technical Operations for SAP
NetWeaver Administration of SAP NetWeaver Systems Administering PI (Process Integration) Monitoring Index
Administration
Web Dispatcher
The Web Dispatcher lies between the Internet and your SAP system It is the entry point for HTTP(s)
requests into your system which consists of one or more SAP NetWeaver application servers As a
software web switch the Web dispatcher can reject connections or accept them When it accepts a
connection it balances the load to ensure an even distribution across the servers
You can use the Web dispatcher in ABAPJava systems and in pure Java systems as well as in pure ABAP
systems
It is also beneficial to use the Web Dispatcher if you do not need security functions (entry point in the
demilitarized zone (DMZ) SSL URL filtering) but you simply want to balance the load between
multiple SAP NetWeaver Application Server instances
Since Web Dispatcher is optional for every SAP system it is not contained in the system landscape and
the implementation sequence of the use case in this documentation
For more information see the SAP Library [page 12] at Function Oriented View Application Server Infrastructure
SAP Web Dispatcher
3 SAP NetWeaver PI Overview
31 Installable Software Units
2056 PUBLIC 2011-04-15
Advanced Adapter Engine
You use the Advanced Adapter Engine to connect to SAP systems (RFC adapter) and external systems
You use the various adapters in Advanced Adapter Engine to convert XML- and HTTP-based messages
to the specific protocol and format required by these systems and the other way around For specific
senderreceiver combinations messages can be processed without invoking the central Integration
Engine In principle you connect external systems using the adapters that are installed centrally or
non-centrally in Advanced Adapter Engine You can use the Advanced Adapter Engine that is part of
your PI system as a central Advanced Adapter Engine Optionally (for performance reasons) you can
install a non-central Advanced Adapter Engine separately as a system with AS Java and parts of the
usage type PI on a separate host
Adapter Engine (Java SE)
Adapter Engine (Java SE) is a separate software unit You can use it only if you have SAP NetWeaver
systems with usage type PI in your system landscape It has to be installed manually You use the Adapter
Engine (Java SE) to connect to external systems Using the various adapters in the Adapter Engine (Java
SE) XML and HTTP-based messages can be converted to the specific protocol and format required by
such systems and the other way around The Adapter Engine (Java SE) only provides some of these
adapters as a standalone version with restricted functions for operating systems that do not support
SAP NetWeaver PI 71 but that have at least a Java Runtime Environment 50 Therefore you should
use the Adapter Engine (Java SE) only if the platform prerequisites do not allow you to use the Advanced
Adapter Engine
SAP Partner Connectivity Kit
SAP Partner Connectivity Kit (PCK) runs on AS Java with parts of the usage type PI It enables a system
of a smaller company or subsidiary that does not run SAP NetWeaver PI to connect to your SAP
NetWeaver systems
313 Clients
Clients are additional installable programs or tools They reside either on local front-end PCs accessed
by users or on back-end systems where they act as client programs within an SAP NetWeaver system
landscape
The clients that you can use with SAP NetWeaver Process Integration are described in the following
sections
SAP GUI
NOTE
We recommend that you use the following versionsI
SAP GUI for Windows 710 (or higher) with the latest patch level
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 2156
SAP GUI for Java 710 (or higher) with the latest revision
The integrated SAP ITS 710
For more information about the SAP GUI family see SAP Service Marketplace at http
servicesapcomsapgui
SAP offers three different client applications for accessing ABAP applications in SAP systems (such as
SAP NetWeaver systems with usage type AS ABAP) This SAP GUI family consists of
SAP GUI for HTML
SAP GUI for HTML is based on the SAP integrated Internet Transaction Server (ITS) which is
included in the installation of SAP NetWeaver systems as of SAP NetWeaver 2004 On the client
side only a suitable browser (such as Internet Explorer 70 or Firefox 20) and a virtual machine are
required SAP ITS 620 is not compatible with SAP NetWeaver 71
SAP GUI for the Java environment (SAP GUI for Java)
SAP GUI for Java is a generic SAP GUI that covers a variety of platforms
For more information about the installation of SAP GUI for Java see the documentation Installation
Guide ndash SAP Front End
SAP GUI for the Windows environment (SAP GUI for Windows)
SAP GUI for Windows is SAPs universal client for accessing all SAP applications built on ABAP
technology It is available on the Microsoft Windows platform only and offers the broadest feature
set of all members of the SAP GUI family
For more information about the installation of SAP GUI for Windows see the Installation Guide ndash
SAP Front End
SAP NetWeaver Developer Studio
The SAP NetWeaver Developer Studio is SAPrsquos Integrated Development Environment (IDE) for Java
and is based on the open-source tools framework Eclipse 33 With the SAP NetWeaver Developer Studio
you can develop Java EE 5 applications from scratch using the built-in support for new technologies
such as EJB 30 and JSF 12
During the installation of the SAP NetWeaver Developer Studio several features are offered for
installation For SAP NetWeaver PI 71 only the following features are relevant
SAP NetWeaver Developer Studio Platform
SAP NetWeaver Developer Studio Java EE
NOTE
If you want to use one of the other features you need SAP NetWeaver Composition Environment
and a corresponding developers licence
For more information about the installation of SAP NetWeaver Developer Studio see the Installation
Guide ndash SAP NetWeaver Developer Studio 71 or Installation Guide ndash SAP NetWeaver Developer Studio 71 Including
Enhancement Package 1
3 SAP NetWeaver PI Overview
31 Installable Software Units
2256 PUBLIC 2011-04-15
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
SAP enhancement packages are a new way of delivering new functions for SAP NetWeaver This allows
a clear separation between the delivery of new functions on the one hand and corrections legal changes
and security updates on the other hand (in Support Package stacks) SAP enhancement packages are
cumulative an enhancement package always contains the functions of the corresponding predecessor
enhancement packages
Enhancement packages are maintained by their own Support Packages while the main release is in
maintenance
Benefits
SAP enhancement packages offer the following benefits
You have reduced effort for testing and no effort for training when applying Support Packages as
new features are only shipped with enhancement packages
Adding new functions between releases becomes predictable and controllable
New functions can be added successively in small steps There is no need to fully upgrade your
system to get new functions
You have minimal training effort when applying an enhancement package because existing
functions are not replaced
Implementation
There are the following ways to get an SAP NetWeaver system with the release level of SAP enhancement
package 1 for SAP NetWeaver Process Integration 71
New installation of SAP NetWeaver PI 71 including enhancement package 1 using the standard
installation tool SAPinst
Upgrade of an existing SAP NetWeaver system from a release lower than SAP NetWeaver PI 71 to
SAP NetWeaver PI 71 including enhancement package 1 For this you use the upgrade programs
SAPup (for ABAP) and SAPJup (for Java)
Installation of the enhancement package on an existing SAP NetWeaver PI 71 system
For this you use the Software Update Manager (SUM) The Software Update Manager evolved
from the previously used SAP Enhancement Package Installer The tool has been renamed to reflect
its broader use for example you can also use it for applying Support Package Stacks to your system
On the ABAP side the Software Update Manager uses a system cloning and switch procedure for
installing enhancement packages It installs a copy of the system the shadow system parallel to
the original system This shadow system is used to update the relevant software components and
to install the additional components while the original system is still in production operation At
a certain point during downtime the switch to the new system is made and afterwards any parts
of the original system that are no longer needed are deleted The enhancement package installation
in a Java system uses a deploy-based procedure that is no shadow system is used The Software
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2011-04-15 PUBLIC 2356
Update Manager requires a stack configuration file (xml file) as input file for the enhancement
package installation procedure This file lists all the packages that are to be installed in your systems
The stack configuration file is generated when you download the required packages
As the Software Update Manager is updated regularly we recommend to always use the latest
version It is delivered as part of the SL toolset For more information see http
servicesapcomsltoolset
For an overview of all required steps for the enhancement package installation process and
corresponding documents see Process Overview Installation of Enhancement Package 1 on an Existing SAP
Netweaver PI 71 System [page 28]
Content of SAP Enhancement Package 1 for SAP NetWeaver PI 71
With enhancement package 1 for SAP NetWeaver PI 71 new features are introduced and some existing
are changed The following is a selection of some of the most important enhancements
Enhanced design and modelling options in the Enterprise Services Repository
New services registry
Support for new Web services standard (Web Services Reliable Messaging)
New modules for the Advanced Adapter Engine
Use of shared memory of the ABAP Application Server for message processing
For more information about the changes see SAP Library [page 12] at Whatacutes new in SAP NetWeaver PI 71
ndash Release Notes
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2456 PUBLIC 2011-04-15
4 SOA-Based Integration Use Case
41 Overview
You can use SOA-based integration to set up the communication between service providers and service
consumers in both application-to-application and business-to-business scenarios and to execute
operate and monitor the communication at runtime SOA-based integration covers both direct (point-
to-point) as well as mediated (via an Integration Server) communication between service providers and
service consumers
The use case spans the whole life cycle of a SOA-based integration scenario including
Scenario modeling and service design in the Enterprise Services Repository
Implementation of the service provider and consumer in the back-end systems
Configuration and finally execution monitoring and operation of the integration scenario
For scenarios using Integration Server or broker-based communication the configuration of the
different connectivity options (for example SOAP RFC Web Services Industry standards and JDBC)
and their enhancements is covered
For more information see the following documents
Service-Enabling with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdnsoa-modeling
Getting Started
Service-Enabling a Legacy Application with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdn
soa-servicebus Getting Started
In the following you will find information about the installation of the involved software units
42 System Landscape
The following figure shows the system landscape for this use case
4 SOA-Based Integration Use Case
41 Overview
2011-04-15 PUBLIC 2556
Figure 5 SOA-Based Integration
It is mandatory to have a dedicated PI system This applies to development quality and production
landscapes
For PI it is a prerequisite that no other system in your system landscape has a higher release than
the PI system For exceptions to this rule see SAP Note 1043047 For example SAP XI 30 is compatible
with SAP NetWeaver 640 and 70 application systems since the same XI protocol is used Apart
from these exceptions if you want to upgrade or install an application in your system landscape
you first have to make sure that the PI system is on the same release level If required you have to
upgrade the PI system first to the new or a higher release
CAUTION
Although it should be technically possible to run an application system with a higher release
than your PI system in your system landscape this is not supported by SAP (apart from the
exceptions listed in SAP Note 1043047) Therefore you run such a landscape at your own risk
You can use the Advanced Adapter Engine that is part of your PI system as a central Advanced
Adapter Engine
Adapter Engine (Java SE) can be installed in a non-SAP Java environment However it only hosts
a subset of the adapter functionality is only supported for compatibility reasons and should be
used only if this is a precondition in your environment
Optionally you can use the Change Management Service (CMS) of an SAP NetWeaver 70 system
with usage type DI to transport design objects and repository objects For more information see
the SAP Library [page 12] at Administratoracutes Guide Technical Operations for SAP NetWeaver Administration
of SAP NetWeaver Systems PI (Process Integration) Software Logistics Transporting ESR Content and Objects
of Integration Directory PI Transports Using the Change Management Service (CMS)
Smaller business partners or subsidiaries that do not run SAP NetWeaver install SAP Partner
Connectivity Kit in their system landscape SAP Partner Connectivity Kit enables XML document
4 SOA-Based Integration Use Case
42 System Landscape
2656 PUBLIC 2011-04-15
exchange between your SAP NetWeaver systems and the partner systems Since SAP Partner
Connectivity Kit gets installed in their system landscape it is not shown in the system landscape
figure above
The AS ABAP system acts as an application and service provider For Java Web Services you also
require AS Java In addition you require SAP NetWeaver Developer Studio on the client side as a
development environment
The Web service client can be either an SAP or a non-SAP application For example an AS ABAP
system or a Web browser could act as application or service consumer
You can install SAP Conversion Agent by Informatica in the system with usage type PI or on a host
where SAP Partner Connectivity Kit is installed or on a host where neither usage type PI nor SAP
Partner Connectivity Kit is installed
43 Implementation Sequence
Procedure
To install this use case perform the steps listed in the following table
StepAction[Corresponding Documentation] Remarks
1 Make sure that you have performed the preparation steps You have planned your system landscape [page 33]
(that is you have decided how many systems you require how you want to use each of these systems and which standalone engines and clients you require)
With the help of your hardware partner you have mapped your systems and standalone engines to properly sized hosts
You have planned and installed shared services [page 35]
2 Installation of system with usage type PI (includes the installation of AS ABAP and AS Java)
NOTE
For usage type PI a Unicode installation is mandatory
[Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt]
If you want to use the features of enhancement package 1 use the direct installation of SAP NetWeaver PI 71 including enhancement package 1
Make sure that you perform the configuration steps as described in the installation guide For certain usage types configuration tasks can be applied by the configuration wizard These configuration tasks as well as any additional configuration steps for your use case are listed in SAP Solution Manager For more information
4 SOA-Based Integration Use Case
43 Implementation Sequence
2011-04-15 PUBLIC 2756
StepAction[Corresponding Documentation] Remarks
see the Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt
3 Install the Adapter Engine (Java SE) engines if required[Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
4 To integrate small business partners and subsidiaries the business partners or subsidiaries install SAP Partner Connectivity Kit running on AS Java with parts of usage type PI in the business partners or subsidiarys system landscape[Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
5 Install SAP Conversion Agent by Informatica if required[SAP Library [page 12] at Function-Oriented View Process Integration SAP Conversion Agent by Informatica Deploying and Using Conversion Agent ]
6 Installation of clients SAP GUI
[Installation Guide ndash SAP Front End]
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
The process sequences give a comprehensive overview of the steps relevant for the enhancement
package installation on an existing SAP NetWeaver PI 71 system
The process sequence is divided into a planning phase and an implementation phase Each step in both
phases contains references to the corresponding documentation to ensure that you can easily find the
information you need
Process
NOTE
To download the enhancement package files and required Support Packages you require the SAP
Solution Manager Maintenance Optimizer You have the following options
Manual Selection
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2856 PUBLIC 2011-04-15
You manually select the required files from SAP Service Marketplace at http
servicesapcomswdc using the SP Stack Application You use the Maintenance Optimize
only to approve the packages which is a prerequisite for the download
Automatic Calculation
The Maintenance Optimizer supports the download of a consistent queue that includes all
necessary Support Packages and enhancement packages In addition SAP Solution Manager
calculates a valid import queue for the selected SAP system and generates the enhancement
package stack configuration file that you require for the installation
As a prerequisite the system that you want to update needs to be maintained correctly in
SAP Solution Manager System Landscape As the Maintenance Optimizer uses this data for
the calculation it is crucial that the data is up-to-date In addition the SAP Solution Manager
system requires a Minimum Support Package level (see below)
Planing PhaseStep Description Documentation
Hardware amp Software Prerequisites
Check which platforms are supported for your target release (OSDB dependencies)
Product Availability Matrix (PAM) at httpservicesapcompam
Check which hardware sizing is required for your target release
Sizing information at httpservicesapcomsizing
Solution Manager Prerequisites
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of the required software packages you have to make sure that your SAP Solution Manager system has the required Support Package levelAt least SAP Solution Manager 70 EHP1 Support Package Stack 17 is required We recommend to use SAP Solution Manager 70 EHP1 Support Package Stack 23Check if you need to do an update or upgrade of your SAP Solution ManagerMake sure that you run the guided procedure SOLMAN_SETUP after every installation or update of SAP Solution Manager and that it completes successfully
For upgrades from source release SAP Solution Manager 31 and 32Upgrade Guide ndash SAP Solution Manager 70 incl Enhancement Package 1For updates from SAP Solution Manager 70Update Guide SAP Enhancement Package 1 for SAP Solution Manager 70Follow-up activities after an Support Package Stack update or enhancement package updateSolution Operations Guide ndash SAP Solution Manager 70 EHP1 section Software Change Management All guides are available at http
servicesapcom instguides SAP Components SAP Solution Manager -gt Release 70 EHP 1
Implementation PhaseStep Description Documentation
1Solution Manager Preparation
Configure the SAP Solution Manager Maintenance Optimizer
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of software packages make sure your
Configuration of Maintenance Optimizer http
helpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Change Request Management and Change ControlMaintenance Optimizer
Prerequisites
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 2956
Implementation PhaseStep Description Documentation
system landscape data in SAP Solution Manager is maintained correctlyLandscape Verification 10 which is an add-on to SAP Solution Manager can support you in maintaining your system landscape data The use of this tool is optional
Landscape Verification http
wwwsdnsapcom irj
sdn alm-update-
management link Landscape Verification under Related Areas on Upgrade and Update Management (in the right column)
SAP Note 1468605 (Installation of Landscape Verification)
Maintaining System Landscape Information [page 47]Note that the information provided in this section is based on SAP Solution Manager 70 EHP1 SP23
2System Preparation
Prepare your system as described in the documentation for example perform OS DB specific preparations and the PI-specific preparations
Update Guide ndash Update of SAP Systems with Software Update Manager sections Planning and Preparation
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
3Software Download
Select and download the software packages in either of the following ways Automatic calculation Create
a maintenance transaction in the Maintenance Optimizer and choose the Calculate Files Automatically option
Manual Selection Create a maintenance transaction in the Maintenance Optimizer and choose the Select Files Manually option You then can select the files manually using the SP Stack application in SAP Service Marketplace
NOTE
You have to download the stack configuration file manually after you have selected all files in the SP Stack
httphelpsapcom SAP Solutions SAP Solution Manager
SAP Solution Manager 70 EHP1 ltSPgtChange Request Management and
Change Control Maintenance Optimizer Maintenance Procedure Scenarios
For information about the automatic calculation see Maintenance Transaction with Installation of an Enhancement PackageFor information about the manual selection and approval process see section Approve and Download Files in Download Basket
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
3056 PUBLIC 2011-04-15
Implementation PhaseStep Description Documentation
application Choose Generate Stack XML and save the file
4Enhancement Package Installation
Run Software Update Manager to update your system with the selected software packages
Update Guide ndash Update of SAP Systems with Software Update Manager
5Follow-Up Steps
Perform technical and PI-specific follow-up activities after the enhancement package installation is done
Update Guide ndash Update of SAP Systems with Software Update Manager section Follow-Up Activities
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
6Configuration
Configure newly installed enhancement package functions using SAP Solution Manager content
See Systems with Usage Types [page 16] section Configuration of Systems with Usage Types
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 3156
This page is left blank for documents that are printed on both sides
5 System Landscape
51 Planning Your System Landscape
The installable software units that make up your system landscape depend on the functions that you
want to implement For information about the features see systems [page 16] standalone engines [page 19]
and clients [page 21]
In addition you have to determine the required shared services [page 35] (such as SAP Solution Manager
or SAP NetWeaver Administrator) that run on central systems in your system landscape and the
landscape aspects relevant for their implementation
In the following you will find general information that you should consider when planning your system
landscape
Sizing
You have to map systems and standalone engines to hosts after you have a clear picture of the following
Which systems and standalone engines you require
How many systems you require and how you want to use each of these systems
NOTE
No general guideline can be given for the sizing of your landscape since this relies heavily on your
requirements You should therefore perform this task together with your hardware partner and
your technical consultant
For information about sizing your systems you can use the following information sources
Your first point of reference is the Quick Sizer
SAP built the Quick Sizer as an online sizing questionnaire Internet application in close cooperation
with its hardware partners This tool delivers general sizing categories based on your volume load
estimates The results provide an objective basis for sizing independent of platform and
configuration
For more information see SAP Service Marketplace at
httpservicesapcomsizing for the SAP NetWeaver PI 71 sizing guide available under
Sizing Guidelines Business Suite amp Services
httpservicesapcomquicksizer for more information and access to the tool itself
Also consider the following important aspects concerning sizing
High availability
5 System Landscape
51 Planning Your System Landscape
2011-04-15 PUBLIC 3356
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Technical Infrastructure High Availability
Unicode
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Internationalization
Contact your hardware partner to find out the appropriate number of sized hosts
The platform-independent abstract results of the Quick Sizer can be used by any of our hardware
partners to create a concrete offer SAP itself does not make any hardware recommendations the
responsibility for sizing and detailed hardware configuration lies with the hardware partners
Figure 6 Example of Mapping of Systems and Standalone Engines to Three Hosts
NOTE
Optionally you could also distribute single systems to multiple hosts For example you could
decide to install the database instance of an SAP system on a separate host for performance
reasons or distribute other system instances to achieve high availability
To provide a mapping that fits your required functions and performance your hardware partner
and your technical consultant have to identify the number of required instances of SAP NetWeaver
find out how to distribute these instances to hosts and what functions will run on which instance
Therefore the hardware partner and the technical consultant have to consider many different
aspects such as
Number of required SAPS (SAP Application Benchmark Performance Standard) for each
system (provided by Quick Sizer)
Landscape-relevant aspects concerning security For more information see the SAP Security
Guide in the SAP Library [page 12] at Administratoracutes Guide Security Guide
Landscape-relevant aspects concerning scalability high availability operation and software
life-cycle management
5 System Landscape
51 Planning Your System Landscape
3456 PUBLIC 2011-04-15
For more information about relevant aspects for the mapping of systems to hosts see the document
Technical Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
Scaling and Distribution Options
You may need to design your system landscape for a large number of users SAP NetWeaver PI offers
you different means of scalability The following list provides you with some examples
You could install multiple systems of one type and use them for different purposes
You could scale every system by installing dialog instances or by distributing the database instance
For more information about distribution options on the instance level see the Technical
Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
For every SAP system you could additionally install Web Dispatcher For more information see
the SAP Library [page 12] at FunctionndashOriented View Application Server Infrastructure SAP Web
Dispatcher
You could further distribute certain standalone engines ndash for example Search and Classification
(TREX) is based on a flexible architecture that supports a distributed installation For more
information see the Technical Infrastructure Guide ndash SAP NetWeaver PI 71 available in SAP Service
Marketplace at httpservicesapcominstallNWPI71
52 Shared Services
You normally run shared services on central systems in your system landscape The following features
could be used for SAP NetWeaver Process Integration to realize shared services
SAP Solution Manager
Used to implement train test maintain monitor control change and manage incidents of your
SAP solution system landscape (open end-to-end application management)
As of SAP Solution Manager (70) 40 Support Package 15 SAP Solution Manager has become the
platform for SAPs end-to-end solution operations strategy Functions for complete application
management has been combined with administrative tools and has been merged in newly created
role based work centers
NOTE
Be aware that you require an SAP Solution Manager system to install or upgrade to SAP
NetWeaver 70 and higher An SAP Solution Manager system is required to generate the SAP
Solution Manager key needed during the installation or upgrade process Without this key
the installation or upgrade process cannot continue
For SAP NetWeaver Process Integration you require SAP Solution Manager 70
For more information see SAP Note 805390
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3556
Solution Manager Diagnostics
An integral part of SAP Solution Manager that is running as a Java application on the Java stack of
SAP Solution Manager 70 Solution Manager Diagnostics is used to analyze the root cause of
incidents in your landscape in an efficient and safe way Before Go-Live Solution Manager
Diagnostics has to be set up and made accessible remotely
SAP NetWeaver Administrator
SAP NetWeaver Administrator is the central administration component which is used for
monitoring and administering Java applications It is included in SAP NetWeaver systems with AS
Java
SAP NetWeaver Administrator exists in the following flavors
A local mode which runs out of the box and which focuses on administrating the underlying
SAP NetWeaver AS Java
NOTE
For a SAP NetWeaver PI 71 it has a special role which you need to activate using a
configuation wizard
A central mode which has to be configured before use and which deals with the system
landscape management
SAP has decided to merge the central mode of SAP NetWeaver Administrator into the new work
centers available as of SAP Solution Manager 70 SP 15 Thus it can be used in an administrative
context together with non-Java-based administration tools Although the central mode of SAP
NetWeaver Administrator will be still available for some time SAP will not develop this tool any
further SAP focuses on optimizing the administrative work centers of SAP Solution Manager
instead
The local mode of SAP NetWeaver Administrator stays untouched It is available for current and
future releases of SAP NetWeaver
SAP Central Process Scheduling by Redwood
SAP Central Process Scheduling application by Redwood enables central job scheduling and job
monitoring of current and old releases of AS ABAP systems (as of Basis Release 31) This application
is fully integrated in SAP NetWeaver Depending on the business needs SAP business applications
are the initial trigger for scheduled activities You can now manage jobs and job chains conveniently
using a graphical user interface
System Landscape Directory
The System Landscape Directory is the central directory of system landscape information relevant
for the management of your software life-cycle It contains a description of your system landscape
(that is software components that are currently installed) and a repository of software components
that can theoretically be installed in your landscape (such as the software components available
from SAP)
Adaptive Computing Controller
5 System Landscape
52 Shared Services
3656 PUBLIC 2011-04-15
The Adaptive Computing Controller enables users to control an adaptive computing landscape
from a single point through observation operation and dynamic resource distribution With
adaptive computing hardware software and system services are able to adapt to changing business
needs In the Adaptive Computing Controller the run-time data of logical and physical landscapes
can be monitored application services can be startedstoppedrelocated and hardware resources
can be assigned to application services The operation can also be mass executed and be planned as
tasks to be executed
For more information about the installation of the Adaptive Computing Controller tool see the
document Installation Guide ndash Adaptive Computing Controller in SAP NetWeaver 71 available on SAP Service
Marketplace at httpservicesapcominstallNWPI71
For more information about Adaptive Computing in general see httpsdnsapcomirj
sdnadaptive
521 Use Cases
You can use the applications and tools described above for use cases that are normally performed
centrally The following sections describe these use cases
5211 End-to-End Solution Operations
Running business applications through their complete life-cycle is a challenge Therefore SAP has
started the Run SAP methodology for implementing End-to-End Solution Operations Based on a set
of SAP standards a roadmap and a package for training and certification Run SAP helps customers to
facilitate End-to-End Solution Operations
You can download the SAP standards for Solution Operations from SAP Service Marketplace at http
servicesapcomsupportstandards They describe roles customers typically have in their IT
environment For optimal role support SAP has grouped existing and new functions in SAP Solution
Manager work centers as of SAP Solution Manager 70 Support Package 15 Operations aspects are fully
covered by adding administrative functions for SAP NetWeaver as well Work centers are ABAP Web
Dynpro-based applications They offer the following advantages
Easy to use similar look and feel
Context transfer while jumping from one work center into another
Logical grouping of tools for a certain area
Simple authorization concept
Easy to expand
Each IT role belongs to one or more work centers For instance the Technical Administrator IT role is
covered by the work centers for System Monitoring System Administration and Landscape Management
The following work centers are available
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3756
Business Process Operations
Change Management
Root Cause Analysis
Implementation Upgrade
Incident Management
Test Management
Job Management
System Landscape Management
Solution Documentation Assistant
SAP Engagement and Service Delivery
SAP Solution Manager Administration
System Administration
System Monitoring
My Home is the central point of access to all important data of almost all work centers in SAP Solution
Manager
5212 Support Infrastructure
A key requirement for effective support of IT solutions is the ability to perform root cause analysis with
speed and efficiency
With SAP Solution Manager SAP has long had an infrastructure in place for its ABAP applications that
efficiently supports SAP solutions This helps ensure the high availability and smooth running of
business processes For more information see the SAP Solution Manager section
With Solution Manager Diagnostics this knowledge has been extended to Java applications If for
example homegrown Java applications cause instability Solution Manager Diagnostics helps trace the
cause to eradicate the problem rapidly Solution Manager Diagnostics is fully integrated into SAP
Solution Manager 70 Solution Manager Diagnostics also contains two third-party tools CArsquos Wily
Introscopereg for measuring performance as well as troubleshooting problems of the Java EE Engine
and applications running on it and Mercury Loadrunnerreg which enables SAP Support to produce a
defined load in the SAP solution landscape remotely For more information see Solution Manager
Diagnostics [page 43]
The support infrastructure provides SAP Support with safe access to your productive landscape for safe
root cause analysis so ensuring that SAP Support does not change your landscape inadvertently You
require a support infrastructure to run SAP NetWeaver
The following figure shows the overall infrastructure including SAP NetWeaver administration tools
that are used by administrators or operators at the customer site
5 System Landscape
52 Shared Services
3856 PUBLIC 2011-04-15
Landscape Aspects
If you use SAP NetWeaver Process Integration 71 productively besides SAP Solution Manager (as a
central support platform) you have to set up Solution Manager Diagnostics for supportability reasons
Implementation Sequence
For information about the implementation of the support infrastructure see the document Master
Guide ndash SAP Solution Manager 70 available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution Manager ltReleasegt
5213 Collection of Landscape Data
Amongst other applications and services the support infrastructure and the SAP NetWeaver
administration tools rely on system landscape data
For SAP NetWeaver PI 71 you have to run non-ABAP components in your solution landscape
Therefore the System Landscape Directory is mandatory The landscape data that is automatically
gathered by the System Landscape Directory is replicated to SAP Solution Manager There are several
topology options for the System Landscape Directory They offer different grades of availability
administration and operation effort
For more information see the System Landscape Directory section
5214 Authentication and Single Sign-On
Before implementing your system landscape plan how to implement authentication and how to
integrate different systems into a Single Sign-On landscape Single Sign-On reduces complexity for end
users saving them valuable time while also reducing administration effort for resetting passwords
thereby contributing to TCO reduction
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
5215 Integrated User and Access Management
In a system landscape containing a combination of ABAP and Java components we recommend that
you integrate your user and access management so that you can use the same user data across different
systems administer this data centrally and control access to data SAPs mature fine-grained
authorization concept allows detailed control of access rights SAP NetWeaver provides both ABAP and
Java-based user management solutions The user management solution that you use to administer
your user data depends on factors such as the type of systems that are running in your landscape
If you want to use central user administration we recommend that you run it in a non-production
system If you do not have a central user administration yet you can for example realize it in the SAP
Solution Manager system
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3956
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
522 Examples for the Overall System Landscape of Shared Services
In this section we provide examples of how shared services can be set up depending on the system
landscape they are intended for The following examples aggregate the landscape aspects given in the
Use Cases section
NOTE
The following sections and the figure mostly do not show information about the life-cycle of
shared services For example you may also need a development and testquality assurance system
for SAP Solution Manager You should consider this aspect in addition to the information given
in this section based on your requirements
Small and MediumndashSized Customer Landscapes with Java
As you use Java productively for SAP NetWeaver PI 71 besides SAP Solution Manager you have to set
up additional components for optimal monitoring administration and support Solution Manager
Diagnostics and the central mode of SAP NetWeaver Administrator are already fully integrated into
SAP Solution Manager 70 as the central operations hub For SAP Process Integration you must also
set up SAP NetWeaver Administrator with a special role
We recommend that you do not install SAP Central Process Scheduling in the SAP Solution Manager
system You have to set up and operate the system which hosts your productive scheduler as a mission
critical system
In the SAP Solution Manager system you should set up a local System Landscape Directory in addition
to a central runtime System Landscape Directory This way you have a clear separation between your
management system (SAP Solution Manager) and managed systems in your landscape In addition
SAP Solution Manager then does not rely on a System Landscape Directory running in the production
environment For this setup configure the SLD data suppliers of your SAP Solution Manager system
to send data to the central runtime System Landscape Directory In addition configure automatic
bridge forwarding from your runtime System Landscape Directory to the local System Landscape
Directory For more information see the Planning Guide - System Landscape Directory
If you want to use a central system for Adobe Document Services we recommend that you install a
dedicated system for this purpose in your production environment For detailed information about
the sizing of the system for the different use cases see the Sizing Guide for Adobe Document Services at
SAP Service Marketplace at httpservicesapcomsizing Sizing Guidelines Solutions amp
Platform
We recommend that you start with this centralized SAP Solution Manager approach as depicted in the
following figure
5 System Landscape
52 Shared Services
4056 PUBLIC 2011-04-15
Figure 7 Single SAP Solution Manager Landscape
Large Customer Landscapes with Java
Large customers who have environments in their landscape that are large and distributed administered
by different groups or separated for security reasons can consider a distributed operations setup In
addition to the centralized setup described for small- and medium-sized customers above large
customers can put parts of the central management functions on extra hosts or systems for performance
or policy reasons You have the following options for a distributed setup
You may set up an extra system or client for Central User Administration (CUA)
The Change and Transport System (CTS) can run on an extra system However it is not
performance- or data-intensive
You may set up an extra system for central CCMS monitoring Depending on the customizing
and on the landscape size central CCMS may generate a lot of system load You can connect a
separate central CCMS to SAP Solution Manager for displaying alerts in the alert inbox of the System
Monitoring work center
You can use a separate SAP NetWeaver 70 system with usage type BI together with SAP Solution
Manager This may make sense with respect to the amount of landscape management data that is
stored for reporting purposes The amount of data strongly depends on the data granularity
storage time frame and landscape size
You can easily put Wily Introscope Enterprise Manager on an separate host
Other aspects described above for small- and medium-customers (such as the setup of the System
Landscape Directory) are also valid for large customers
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4156
523 Feature Details
This section provides further information about the features described above
5231 SAP Solution Manager
SAP provides you with SAP Solution Manager as the strategic application management platform and
to enable the collaboration between you and SAP You need to install at least one productive SAP
Solution Manager in your system landscape To ensure the availability of this application management
platform an SAP Solution Manager system is technically required to install or upgrade to SAP
NetWeaver 70 or higher If you are already using SAP Solution Manager you can also use it to manage
the solution you build with SAP NetWeaver In this case we highly recommend that you update SAP
Solution Manager to the latest version
As of SAP Solution Manager 70 SP15 you can use the newly created work centers
NOTE
During the SAP system installation or upgrade process you are prompted to enter the SAP
Solution Manager key An SAP Solution Manager system is required to generate this key Without
this key the installation or upgrade process cannot continue
You may generate all needed keys for your entire system landscape (development quality
assurance and production system) in one SAP Solution Manager system In case you plan to install
several solution landscapes (for example in different countries) one SAP Solution Manager
system is still sufficient
For more information see SAP Note 805390
It is possible to install multiple SAP Solution Managers If you do so they should host separate business
solutions
If you want to reduce the risk of unavailability you should not install SAP Solution Manager as a central
component Instead you can operate a 2-system-landscape with both a test and production
environment of SAP Solution Manager (especially if you are using time-critical functions like Support
Desk) If you also develop your own content a 3-system-landscape with a development test and
production environment is recommended
For more information about SAP Solution Manager see the following table
Topic Where to Find More Information
System infrastructure scenarios installation and configuration of SAP Solution Manager
Master Guide ndash SAP Solution Manager available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution ManagerltReleasegt
Benefits and usage scenarios SAP Solution Manager ndash Learning Maps available on SAP Service Marketplace at http
5 System Landscape
52 Shared Services
4256 PUBLIC 2011-04-15
Topic Where to Find More Informationservicesapcomrkt-solman or https
servicesapcomsolutionmanager
Additional information See SAP Service Marketplace at http
servicesapcomsolutionmanager
5232 Solution Manager Diagnostics
Solution Manager Diagnostics provides efficient and safe root-cause analysis of incidents in customer
solutions powered by SAP NetWeaver It can help monitor on operating systems databases Java
application activities performance and logs It also supports the reporting of software and
configuration changes that can lead to malfunctions and errors
You must run one Solution Manager Diagnostics within your SAP solution landscape if you run
applications based on SAP NetWeaver systems with usage type AS Java Agents are responsible for
delivering the data from all productive hosts within your system landscape to the Solution Manager
Diagnostics system
CAUTION
SAP Support performs root-cause analysis on incoming incidents with Solution Manager
Diagnostics Not installing and configuring this support infrastructure results in a dramatically
reduced service level
Solution Manager Diagnostics is fully integrated into SAP Solution Manager 70
Solution Manager Diagnostics also contains Wily Introscope (Display Server and Agent part) for
measuring performance as well as to troubleshoot problems of Non-ABAP applications Wily Introscope
is heavily used for troubleshooting applications running on AS Java
SAP has signed a distribution agreement for Wily Introscope SAP customers are allowed to use this
tool in a preconfigured way
For more information about Solution Manager Diagnostics and an FAQ list see SAP Service Marketplace
at httpservicesapcomdiagnostics
5233 System Landscape Directory
The System Landscape Directory (SLD) of SAP NetWeaver is the central directory of system landscape
information relevant for the management of your software life-cycle
NOTE
Note that the abbreviation SLD is not intended to define a product since the System Landscape
Directory is part of SAP NetWeaver This abbreviation is solely intended to improve readability
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4356
The System Landscape Directory contains a description of your system landscape (that is software
components that are currently installed) and a repository of software components that can
theoretically be installed in your landscape (such as the software components available from SAP)
Since this data gets updated automatically the System Landscape Directory provides reliable and up-
to-date system landscape information with as little effort for you as possible In this way the System
Landscape Directory acts as a central information provider for SAP and third-party tools that use this
data to deliver the services you need to keep your landscape up and running
For the System Landscape Directory as part of an SAP NetWeaver PI 71 landscape consider the following
aspects
Part of SAP NetWeaver PI 71 is a new version of the System Landscape Directory It is automatically
included in every SAP NetWeaver 71 system with usage type AS Java It offers enhanced functions
such as a full automatic synchronization mechanism for all data stored in it That is both data
delivered by data suppliers and data entered or changed manually in the System Landscape
Directory can be synchronized automatically This synchronization offers the following
A fully automated mechanism so no user interaction is required and conflicts are resolved
automatically
Asynchronous propagation of information so some nodes may be down temporarily
Communication over HTTP protocol
Uni- and bi-directional synchronization
Depending on your use case the full automatic synchronization could significantly reduce manual
synchronization effort
For SAP NetWeaver PI 71 the configuration of the system landscape directory and its data suppliers
is already included in the standard implementation procedure with SAPinst For existing systems
you only have to perform some quick and easy configuration actions to start operating the system
landscape directory server in an AS Java system
For SAP NetWeaver PI 71 you have the following options concerning SLD
Option 1
Run SAP NetWeaver PI 71 against an existing SLD running on SAP NetWeaver 70 We only
recommend this for upgrades from SAP NetWeaver 70 if you have a central SLD in operation
not running on one of your PI systems
Option 2
Use the SLD included in an SAP NetWeaver PI 71 system We recommend this option for new
installations and upgrades from older releases than SAP NetWeaver 70 due to the enhanced
functions and improved performance of SLD 71
NOTE
If you already have a central SLD running on SAP NetWeaver 70 in operation you could run
two SLD versions in parallel ndash SLD running on SAP NetWeaver 71 for your PI systems and
SLD running on SAP NetWeaver 70 for all other systemsuse cases This way your SAP
5 System Landscape
52 Shared Services
4456 PUBLIC 2011-04-15
NetWeaver PI 71 systems would benefit from the new features while it would be easy to set
up and operate such an SLD landscape For this purpose you could use the new fully
automatic synchronization This feature enables the automatic forwarding of all SLD data
from an SLD running on SAP NetWeaver 70 to an SLD running on SAP NetWeaver 71 As a
result there is no need to adapt most existing systems as their SLD data suppliers could still
send their data to the central SLD In brief the following steps would be required
1 Put SLD in a PI system into operation (part of standard implementation procedure)
2 Configure PI systems to use the new SLD (part of standard implementation procedure
for new PI systems)
3 Set up the fully automatic synchronization from your old SLD to your new SLD
As soon as an upgrade or an installation of a standalone AS Java 71 system is available you
could move your central SLD also to SAP NetWeaver 71 Then you could optionally shift
your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems
Figure 8
We recommend that you use a Domain Name System (DNS) alias so that you are able to switch to
another System Landscape Directory easily For example if customers build a new landscape they
normally start with a sandbox environment Over time more and more environments are set up
Once the production environment is in place move the System Landscape Directory there To do
this you can configure a new System Landscape Directory in the production environment
synchronize it with the old System Landscape directory and switch to the new one
Topology
Apart from the considerations above the System Landscape Directory offers several topology options
with different grades of availability at the expense of low administration and operation effort There is
no generic rule therefore on how to set up a System Landscape Directory in your system landscape
To find the topology and synchronization strategy for the System Landscape Directory that fits your
requirements concerning the System Landscape Directory availability (and hence the availability of
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4556
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
How to Create a Configuration Guide using SAP Solution Manager available at http
servicesapcomsolutionmanager Media Library How-To Documents
Restrictions for Systems with Multiple Usage Types
If you have one system with multiple usage types be aware that we do not provide standard tools
to separate these usage types and distribute them to multiple systems at a later stage For example
if you have a system with usage types A and B you are not able to migrate it with SAP standard
tools into two systems one with usage type A only and the other with usage type B only
In addition we do not provide standard tools to merge multiple systems with different usage types
into one system with multiple usage types at a later stage
If you want to perform these tasks you require specific project support
The following figure shows that SAP standard system copy and migration tools do not support
you in separating or merging systems with usage types
Figure 4 No Support for Merging or Separating Systems with Usage Types
Although you can use one system for multiple usage types client restrictions apply for usage type
PI PI requires a dedicated client due to special PI requirements concerning the client pipeline
Whereas application client pipelines only send and receive messages the central PI pipeline can
also map messages to different formats before sending them
312 Standalone Engines
Standalone engines of SAP NetWeaver are additional installable software units They do not work as
full-blown systems of SAP NetWeaver but as standalone engines that provide a specific (server) function
in combination with one or more SAP NetWeaver systems
Standalone engines are not part of a usage type They do not run on AS ABAP or AS Java
The standalone engines that are available for SAP NetWeaver Process Integration are described in the
following
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 1956
Gateway
It is possible to install an SAP instance of an SAP NetWeaver system based exclusively on a standalone
gateway This type of instance does not contain normal work process types (dialog background update
enqueue or spool) Only the gateway process (gwrd) is started If there is an SNA connection to an R
2 system gateway work processes (gwwp) are also started
SAP Conversion Agent by Informatica
SAP Conversion Agent by Informatica is a data conversion tool that enables you to create interfaces
between any data formats and XML-based systems SAP Conversion Agent can convert unstructured
semi-structured and structured formats to XML and the other way around The Conversion Agent
comprises the Conversion Agent Studio and the Conversion Agent Engine In the Conversion Agent
Studio you can develop and configure data conversions The Conversion Agent Engine executes the
data conversions
Search and Classification (TREX)
You can use Search and Classification with SAP NetWeaver PI to search for messages that were previously
indexed Message search using index provides additional methods of searching for specific messages In
addition to static header attributes you can also use adapter-specific message attributes and data from
the message payload for the search A requirement of this however is that the messages are indexed
first You can apply the index-based message search to one or all indexed components of an integration
landscape (domain) Integration Server Adapter Engines and ABAP business systems
For more information see the SAP Library [page 12] at Administratorrsquos Guide Technical Operations for SAP
NetWeaver Administration of SAP NetWeaver Systems Administering PI (Process Integration) Monitoring Index
Administration
Web Dispatcher
The Web Dispatcher lies between the Internet and your SAP system It is the entry point for HTTP(s)
requests into your system which consists of one or more SAP NetWeaver application servers As a
software web switch the Web dispatcher can reject connections or accept them When it accepts a
connection it balances the load to ensure an even distribution across the servers
You can use the Web dispatcher in ABAPJava systems and in pure Java systems as well as in pure ABAP
systems
It is also beneficial to use the Web Dispatcher if you do not need security functions (entry point in the
demilitarized zone (DMZ) SSL URL filtering) but you simply want to balance the load between
multiple SAP NetWeaver Application Server instances
Since Web Dispatcher is optional for every SAP system it is not contained in the system landscape and
the implementation sequence of the use case in this documentation
For more information see the SAP Library [page 12] at Function Oriented View Application Server Infrastructure
SAP Web Dispatcher
3 SAP NetWeaver PI Overview
31 Installable Software Units
2056 PUBLIC 2011-04-15
Advanced Adapter Engine
You use the Advanced Adapter Engine to connect to SAP systems (RFC adapter) and external systems
You use the various adapters in Advanced Adapter Engine to convert XML- and HTTP-based messages
to the specific protocol and format required by these systems and the other way around For specific
senderreceiver combinations messages can be processed without invoking the central Integration
Engine In principle you connect external systems using the adapters that are installed centrally or
non-centrally in Advanced Adapter Engine You can use the Advanced Adapter Engine that is part of
your PI system as a central Advanced Adapter Engine Optionally (for performance reasons) you can
install a non-central Advanced Adapter Engine separately as a system with AS Java and parts of the
usage type PI on a separate host
Adapter Engine (Java SE)
Adapter Engine (Java SE) is a separate software unit You can use it only if you have SAP NetWeaver
systems with usage type PI in your system landscape It has to be installed manually You use the Adapter
Engine (Java SE) to connect to external systems Using the various adapters in the Adapter Engine (Java
SE) XML and HTTP-based messages can be converted to the specific protocol and format required by
such systems and the other way around The Adapter Engine (Java SE) only provides some of these
adapters as a standalone version with restricted functions for operating systems that do not support
SAP NetWeaver PI 71 but that have at least a Java Runtime Environment 50 Therefore you should
use the Adapter Engine (Java SE) only if the platform prerequisites do not allow you to use the Advanced
Adapter Engine
SAP Partner Connectivity Kit
SAP Partner Connectivity Kit (PCK) runs on AS Java with parts of the usage type PI It enables a system
of a smaller company or subsidiary that does not run SAP NetWeaver PI to connect to your SAP
NetWeaver systems
313 Clients
Clients are additional installable programs or tools They reside either on local front-end PCs accessed
by users or on back-end systems where they act as client programs within an SAP NetWeaver system
landscape
The clients that you can use with SAP NetWeaver Process Integration are described in the following
sections
SAP GUI
NOTE
We recommend that you use the following versionsI
SAP GUI for Windows 710 (or higher) with the latest patch level
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 2156
SAP GUI for Java 710 (or higher) with the latest revision
The integrated SAP ITS 710
For more information about the SAP GUI family see SAP Service Marketplace at http
servicesapcomsapgui
SAP offers three different client applications for accessing ABAP applications in SAP systems (such as
SAP NetWeaver systems with usage type AS ABAP) This SAP GUI family consists of
SAP GUI for HTML
SAP GUI for HTML is based on the SAP integrated Internet Transaction Server (ITS) which is
included in the installation of SAP NetWeaver systems as of SAP NetWeaver 2004 On the client
side only a suitable browser (such as Internet Explorer 70 or Firefox 20) and a virtual machine are
required SAP ITS 620 is not compatible with SAP NetWeaver 71
SAP GUI for the Java environment (SAP GUI for Java)
SAP GUI for Java is a generic SAP GUI that covers a variety of platforms
For more information about the installation of SAP GUI for Java see the documentation Installation
Guide ndash SAP Front End
SAP GUI for the Windows environment (SAP GUI for Windows)
SAP GUI for Windows is SAPs universal client for accessing all SAP applications built on ABAP
technology It is available on the Microsoft Windows platform only and offers the broadest feature
set of all members of the SAP GUI family
For more information about the installation of SAP GUI for Windows see the Installation Guide ndash
SAP Front End
SAP NetWeaver Developer Studio
The SAP NetWeaver Developer Studio is SAPrsquos Integrated Development Environment (IDE) for Java
and is based on the open-source tools framework Eclipse 33 With the SAP NetWeaver Developer Studio
you can develop Java EE 5 applications from scratch using the built-in support for new technologies
such as EJB 30 and JSF 12
During the installation of the SAP NetWeaver Developer Studio several features are offered for
installation For SAP NetWeaver PI 71 only the following features are relevant
SAP NetWeaver Developer Studio Platform
SAP NetWeaver Developer Studio Java EE
NOTE
If you want to use one of the other features you need SAP NetWeaver Composition Environment
and a corresponding developers licence
For more information about the installation of SAP NetWeaver Developer Studio see the Installation
Guide ndash SAP NetWeaver Developer Studio 71 or Installation Guide ndash SAP NetWeaver Developer Studio 71 Including
Enhancement Package 1
3 SAP NetWeaver PI Overview
31 Installable Software Units
2256 PUBLIC 2011-04-15
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
SAP enhancement packages are a new way of delivering new functions for SAP NetWeaver This allows
a clear separation between the delivery of new functions on the one hand and corrections legal changes
and security updates on the other hand (in Support Package stacks) SAP enhancement packages are
cumulative an enhancement package always contains the functions of the corresponding predecessor
enhancement packages
Enhancement packages are maintained by their own Support Packages while the main release is in
maintenance
Benefits
SAP enhancement packages offer the following benefits
You have reduced effort for testing and no effort for training when applying Support Packages as
new features are only shipped with enhancement packages
Adding new functions between releases becomes predictable and controllable
New functions can be added successively in small steps There is no need to fully upgrade your
system to get new functions
You have minimal training effort when applying an enhancement package because existing
functions are not replaced
Implementation
There are the following ways to get an SAP NetWeaver system with the release level of SAP enhancement
package 1 for SAP NetWeaver Process Integration 71
New installation of SAP NetWeaver PI 71 including enhancement package 1 using the standard
installation tool SAPinst
Upgrade of an existing SAP NetWeaver system from a release lower than SAP NetWeaver PI 71 to
SAP NetWeaver PI 71 including enhancement package 1 For this you use the upgrade programs
SAPup (for ABAP) and SAPJup (for Java)
Installation of the enhancement package on an existing SAP NetWeaver PI 71 system
For this you use the Software Update Manager (SUM) The Software Update Manager evolved
from the previously used SAP Enhancement Package Installer The tool has been renamed to reflect
its broader use for example you can also use it for applying Support Package Stacks to your system
On the ABAP side the Software Update Manager uses a system cloning and switch procedure for
installing enhancement packages It installs a copy of the system the shadow system parallel to
the original system This shadow system is used to update the relevant software components and
to install the additional components while the original system is still in production operation At
a certain point during downtime the switch to the new system is made and afterwards any parts
of the original system that are no longer needed are deleted The enhancement package installation
in a Java system uses a deploy-based procedure that is no shadow system is used The Software
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2011-04-15 PUBLIC 2356
Update Manager requires a stack configuration file (xml file) as input file for the enhancement
package installation procedure This file lists all the packages that are to be installed in your systems
The stack configuration file is generated when you download the required packages
As the Software Update Manager is updated regularly we recommend to always use the latest
version It is delivered as part of the SL toolset For more information see http
servicesapcomsltoolset
For an overview of all required steps for the enhancement package installation process and
corresponding documents see Process Overview Installation of Enhancement Package 1 on an Existing SAP
Netweaver PI 71 System [page 28]
Content of SAP Enhancement Package 1 for SAP NetWeaver PI 71
With enhancement package 1 for SAP NetWeaver PI 71 new features are introduced and some existing
are changed The following is a selection of some of the most important enhancements
Enhanced design and modelling options in the Enterprise Services Repository
New services registry
Support for new Web services standard (Web Services Reliable Messaging)
New modules for the Advanced Adapter Engine
Use of shared memory of the ABAP Application Server for message processing
For more information about the changes see SAP Library [page 12] at Whatacutes new in SAP NetWeaver PI 71
ndash Release Notes
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2456 PUBLIC 2011-04-15
4 SOA-Based Integration Use Case
41 Overview
You can use SOA-based integration to set up the communication between service providers and service
consumers in both application-to-application and business-to-business scenarios and to execute
operate and monitor the communication at runtime SOA-based integration covers both direct (point-
to-point) as well as mediated (via an Integration Server) communication between service providers and
service consumers
The use case spans the whole life cycle of a SOA-based integration scenario including
Scenario modeling and service design in the Enterprise Services Repository
Implementation of the service provider and consumer in the back-end systems
Configuration and finally execution monitoring and operation of the integration scenario
For scenarios using Integration Server or broker-based communication the configuration of the
different connectivity options (for example SOAP RFC Web Services Industry standards and JDBC)
and their enhancements is covered
For more information see the following documents
Service-Enabling with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdnsoa-modeling
Getting Started
Service-Enabling a Legacy Application with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdn
soa-servicebus Getting Started
In the following you will find information about the installation of the involved software units
42 System Landscape
The following figure shows the system landscape for this use case
4 SOA-Based Integration Use Case
41 Overview
2011-04-15 PUBLIC 2556
Figure 5 SOA-Based Integration
It is mandatory to have a dedicated PI system This applies to development quality and production
landscapes
For PI it is a prerequisite that no other system in your system landscape has a higher release than
the PI system For exceptions to this rule see SAP Note 1043047 For example SAP XI 30 is compatible
with SAP NetWeaver 640 and 70 application systems since the same XI protocol is used Apart
from these exceptions if you want to upgrade or install an application in your system landscape
you first have to make sure that the PI system is on the same release level If required you have to
upgrade the PI system first to the new or a higher release
CAUTION
Although it should be technically possible to run an application system with a higher release
than your PI system in your system landscape this is not supported by SAP (apart from the
exceptions listed in SAP Note 1043047) Therefore you run such a landscape at your own risk
You can use the Advanced Adapter Engine that is part of your PI system as a central Advanced
Adapter Engine
Adapter Engine (Java SE) can be installed in a non-SAP Java environment However it only hosts
a subset of the adapter functionality is only supported for compatibility reasons and should be
used only if this is a precondition in your environment
Optionally you can use the Change Management Service (CMS) of an SAP NetWeaver 70 system
with usage type DI to transport design objects and repository objects For more information see
the SAP Library [page 12] at Administratoracutes Guide Technical Operations for SAP NetWeaver Administration
of SAP NetWeaver Systems PI (Process Integration) Software Logistics Transporting ESR Content and Objects
of Integration Directory PI Transports Using the Change Management Service (CMS)
Smaller business partners or subsidiaries that do not run SAP NetWeaver install SAP Partner
Connectivity Kit in their system landscape SAP Partner Connectivity Kit enables XML document
4 SOA-Based Integration Use Case
42 System Landscape
2656 PUBLIC 2011-04-15
exchange between your SAP NetWeaver systems and the partner systems Since SAP Partner
Connectivity Kit gets installed in their system landscape it is not shown in the system landscape
figure above
The AS ABAP system acts as an application and service provider For Java Web Services you also
require AS Java In addition you require SAP NetWeaver Developer Studio on the client side as a
development environment
The Web service client can be either an SAP or a non-SAP application For example an AS ABAP
system or a Web browser could act as application or service consumer
You can install SAP Conversion Agent by Informatica in the system with usage type PI or on a host
where SAP Partner Connectivity Kit is installed or on a host where neither usage type PI nor SAP
Partner Connectivity Kit is installed
43 Implementation Sequence
Procedure
To install this use case perform the steps listed in the following table
StepAction[Corresponding Documentation] Remarks
1 Make sure that you have performed the preparation steps You have planned your system landscape [page 33]
(that is you have decided how many systems you require how you want to use each of these systems and which standalone engines and clients you require)
With the help of your hardware partner you have mapped your systems and standalone engines to properly sized hosts
You have planned and installed shared services [page 35]
2 Installation of system with usage type PI (includes the installation of AS ABAP and AS Java)
NOTE
For usage type PI a Unicode installation is mandatory
[Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt]
If you want to use the features of enhancement package 1 use the direct installation of SAP NetWeaver PI 71 including enhancement package 1
Make sure that you perform the configuration steps as described in the installation guide For certain usage types configuration tasks can be applied by the configuration wizard These configuration tasks as well as any additional configuration steps for your use case are listed in SAP Solution Manager For more information
4 SOA-Based Integration Use Case
43 Implementation Sequence
2011-04-15 PUBLIC 2756
StepAction[Corresponding Documentation] Remarks
see the Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt
3 Install the Adapter Engine (Java SE) engines if required[Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
4 To integrate small business partners and subsidiaries the business partners or subsidiaries install SAP Partner Connectivity Kit running on AS Java with parts of usage type PI in the business partners or subsidiarys system landscape[Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
5 Install SAP Conversion Agent by Informatica if required[SAP Library [page 12] at Function-Oriented View Process Integration SAP Conversion Agent by Informatica Deploying and Using Conversion Agent ]
6 Installation of clients SAP GUI
[Installation Guide ndash SAP Front End]
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
The process sequences give a comprehensive overview of the steps relevant for the enhancement
package installation on an existing SAP NetWeaver PI 71 system
The process sequence is divided into a planning phase and an implementation phase Each step in both
phases contains references to the corresponding documentation to ensure that you can easily find the
information you need
Process
NOTE
To download the enhancement package files and required Support Packages you require the SAP
Solution Manager Maintenance Optimizer You have the following options
Manual Selection
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2856 PUBLIC 2011-04-15
You manually select the required files from SAP Service Marketplace at http
servicesapcomswdc using the SP Stack Application You use the Maintenance Optimize
only to approve the packages which is a prerequisite for the download
Automatic Calculation
The Maintenance Optimizer supports the download of a consistent queue that includes all
necessary Support Packages and enhancement packages In addition SAP Solution Manager
calculates a valid import queue for the selected SAP system and generates the enhancement
package stack configuration file that you require for the installation
As a prerequisite the system that you want to update needs to be maintained correctly in
SAP Solution Manager System Landscape As the Maintenance Optimizer uses this data for
the calculation it is crucial that the data is up-to-date In addition the SAP Solution Manager
system requires a Minimum Support Package level (see below)
Planing PhaseStep Description Documentation
Hardware amp Software Prerequisites
Check which platforms are supported for your target release (OSDB dependencies)
Product Availability Matrix (PAM) at httpservicesapcompam
Check which hardware sizing is required for your target release
Sizing information at httpservicesapcomsizing
Solution Manager Prerequisites
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of the required software packages you have to make sure that your SAP Solution Manager system has the required Support Package levelAt least SAP Solution Manager 70 EHP1 Support Package Stack 17 is required We recommend to use SAP Solution Manager 70 EHP1 Support Package Stack 23Check if you need to do an update or upgrade of your SAP Solution ManagerMake sure that you run the guided procedure SOLMAN_SETUP after every installation or update of SAP Solution Manager and that it completes successfully
For upgrades from source release SAP Solution Manager 31 and 32Upgrade Guide ndash SAP Solution Manager 70 incl Enhancement Package 1For updates from SAP Solution Manager 70Update Guide SAP Enhancement Package 1 for SAP Solution Manager 70Follow-up activities after an Support Package Stack update or enhancement package updateSolution Operations Guide ndash SAP Solution Manager 70 EHP1 section Software Change Management All guides are available at http
servicesapcom instguides SAP Components SAP Solution Manager -gt Release 70 EHP 1
Implementation PhaseStep Description Documentation
1Solution Manager Preparation
Configure the SAP Solution Manager Maintenance Optimizer
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of software packages make sure your
Configuration of Maintenance Optimizer http
helpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Change Request Management and Change ControlMaintenance Optimizer
Prerequisites
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 2956
Implementation PhaseStep Description Documentation
system landscape data in SAP Solution Manager is maintained correctlyLandscape Verification 10 which is an add-on to SAP Solution Manager can support you in maintaining your system landscape data The use of this tool is optional
Landscape Verification http
wwwsdnsapcom irj
sdn alm-update-
management link Landscape Verification under Related Areas on Upgrade and Update Management (in the right column)
SAP Note 1468605 (Installation of Landscape Verification)
Maintaining System Landscape Information [page 47]Note that the information provided in this section is based on SAP Solution Manager 70 EHP1 SP23
2System Preparation
Prepare your system as described in the documentation for example perform OS DB specific preparations and the PI-specific preparations
Update Guide ndash Update of SAP Systems with Software Update Manager sections Planning and Preparation
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
3Software Download
Select and download the software packages in either of the following ways Automatic calculation Create
a maintenance transaction in the Maintenance Optimizer and choose the Calculate Files Automatically option
Manual Selection Create a maintenance transaction in the Maintenance Optimizer and choose the Select Files Manually option You then can select the files manually using the SP Stack application in SAP Service Marketplace
NOTE
You have to download the stack configuration file manually after you have selected all files in the SP Stack
httphelpsapcom SAP Solutions SAP Solution Manager
SAP Solution Manager 70 EHP1 ltSPgtChange Request Management and
Change Control Maintenance Optimizer Maintenance Procedure Scenarios
For information about the automatic calculation see Maintenance Transaction with Installation of an Enhancement PackageFor information about the manual selection and approval process see section Approve and Download Files in Download Basket
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
3056 PUBLIC 2011-04-15
Implementation PhaseStep Description Documentation
application Choose Generate Stack XML and save the file
4Enhancement Package Installation
Run Software Update Manager to update your system with the selected software packages
Update Guide ndash Update of SAP Systems with Software Update Manager
5Follow-Up Steps
Perform technical and PI-specific follow-up activities after the enhancement package installation is done
Update Guide ndash Update of SAP Systems with Software Update Manager section Follow-Up Activities
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
6Configuration
Configure newly installed enhancement package functions using SAP Solution Manager content
See Systems with Usage Types [page 16] section Configuration of Systems with Usage Types
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 3156
This page is left blank for documents that are printed on both sides
5 System Landscape
51 Planning Your System Landscape
The installable software units that make up your system landscape depend on the functions that you
want to implement For information about the features see systems [page 16] standalone engines [page 19]
and clients [page 21]
In addition you have to determine the required shared services [page 35] (such as SAP Solution Manager
or SAP NetWeaver Administrator) that run on central systems in your system landscape and the
landscape aspects relevant for their implementation
In the following you will find general information that you should consider when planning your system
landscape
Sizing
You have to map systems and standalone engines to hosts after you have a clear picture of the following
Which systems and standalone engines you require
How many systems you require and how you want to use each of these systems
NOTE
No general guideline can be given for the sizing of your landscape since this relies heavily on your
requirements You should therefore perform this task together with your hardware partner and
your technical consultant
For information about sizing your systems you can use the following information sources
Your first point of reference is the Quick Sizer
SAP built the Quick Sizer as an online sizing questionnaire Internet application in close cooperation
with its hardware partners This tool delivers general sizing categories based on your volume load
estimates The results provide an objective basis for sizing independent of platform and
configuration
For more information see SAP Service Marketplace at
httpservicesapcomsizing for the SAP NetWeaver PI 71 sizing guide available under
Sizing Guidelines Business Suite amp Services
httpservicesapcomquicksizer for more information and access to the tool itself
Also consider the following important aspects concerning sizing
High availability
5 System Landscape
51 Planning Your System Landscape
2011-04-15 PUBLIC 3356
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Technical Infrastructure High Availability
Unicode
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Internationalization
Contact your hardware partner to find out the appropriate number of sized hosts
The platform-independent abstract results of the Quick Sizer can be used by any of our hardware
partners to create a concrete offer SAP itself does not make any hardware recommendations the
responsibility for sizing and detailed hardware configuration lies with the hardware partners
Figure 6 Example of Mapping of Systems and Standalone Engines to Three Hosts
NOTE
Optionally you could also distribute single systems to multiple hosts For example you could
decide to install the database instance of an SAP system on a separate host for performance
reasons or distribute other system instances to achieve high availability
To provide a mapping that fits your required functions and performance your hardware partner
and your technical consultant have to identify the number of required instances of SAP NetWeaver
find out how to distribute these instances to hosts and what functions will run on which instance
Therefore the hardware partner and the technical consultant have to consider many different
aspects such as
Number of required SAPS (SAP Application Benchmark Performance Standard) for each
system (provided by Quick Sizer)
Landscape-relevant aspects concerning security For more information see the SAP Security
Guide in the SAP Library [page 12] at Administratoracutes Guide Security Guide
Landscape-relevant aspects concerning scalability high availability operation and software
life-cycle management
5 System Landscape
51 Planning Your System Landscape
3456 PUBLIC 2011-04-15
For more information about relevant aspects for the mapping of systems to hosts see the document
Technical Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
Scaling and Distribution Options
You may need to design your system landscape for a large number of users SAP NetWeaver PI offers
you different means of scalability The following list provides you with some examples
You could install multiple systems of one type and use them for different purposes
You could scale every system by installing dialog instances or by distributing the database instance
For more information about distribution options on the instance level see the Technical
Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
For every SAP system you could additionally install Web Dispatcher For more information see
the SAP Library [page 12] at FunctionndashOriented View Application Server Infrastructure SAP Web
Dispatcher
You could further distribute certain standalone engines ndash for example Search and Classification
(TREX) is based on a flexible architecture that supports a distributed installation For more
information see the Technical Infrastructure Guide ndash SAP NetWeaver PI 71 available in SAP Service
Marketplace at httpservicesapcominstallNWPI71
52 Shared Services
You normally run shared services on central systems in your system landscape The following features
could be used for SAP NetWeaver Process Integration to realize shared services
SAP Solution Manager
Used to implement train test maintain monitor control change and manage incidents of your
SAP solution system landscape (open end-to-end application management)
As of SAP Solution Manager (70) 40 Support Package 15 SAP Solution Manager has become the
platform for SAPs end-to-end solution operations strategy Functions for complete application
management has been combined with administrative tools and has been merged in newly created
role based work centers
NOTE
Be aware that you require an SAP Solution Manager system to install or upgrade to SAP
NetWeaver 70 and higher An SAP Solution Manager system is required to generate the SAP
Solution Manager key needed during the installation or upgrade process Without this key
the installation or upgrade process cannot continue
For SAP NetWeaver Process Integration you require SAP Solution Manager 70
For more information see SAP Note 805390
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3556
Solution Manager Diagnostics
An integral part of SAP Solution Manager that is running as a Java application on the Java stack of
SAP Solution Manager 70 Solution Manager Diagnostics is used to analyze the root cause of
incidents in your landscape in an efficient and safe way Before Go-Live Solution Manager
Diagnostics has to be set up and made accessible remotely
SAP NetWeaver Administrator
SAP NetWeaver Administrator is the central administration component which is used for
monitoring and administering Java applications It is included in SAP NetWeaver systems with AS
Java
SAP NetWeaver Administrator exists in the following flavors
A local mode which runs out of the box and which focuses on administrating the underlying
SAP NetWeaver AS Java
NOTE
For a SAP NetWeaver PI 71 it has a special role which you need to activate using a
configuation wizard
A central mode which has to be configured before use and which deals with the system
landscape management
SAP has decided to merge the central mode of SAP NetWeaver Administrator into the new work
centers available as of SAP Solution Manager 70 SP 15 Thus it can be used in an administrative
context together with non-Java-based administration tools Although the central mode of SAP
NetWeaver Administrator will be still available for some time SAP will not develop this tool any
further SAP focuses on optimizing the administrative work centers of SAP Solution Manager
instead
The local mode of SAP NetWeaver Administrator stays untouched It is available for current and
future releases of SAP NetWeaver
SAP Central Process Scheduling by Redwood
SAP Central Process Scheduling application by Redwood enables central job scheduling and job
monitoring of current and old releases of AS ABAP systems (as of Basis Release 31) This application
is fully integrated in SAP NetWeaver Depending on the business needs SAP business applications
are the initial trigger for scheduled activities You can now manage jobs and job chains conveniently
using a graphical user interface
System Landscape Directory
The System Landscape Directory is the central directory of system landscape information relevant
for the management of your software life-cycle It contains a description of your system landscape
(that is software components that are currently installed) and a repository of software components
that can theoretically be installed in your landscape (such as the software components available
from SAP)
Adaptive Computing Controller
5 System Landscape
52 Shared Services
3656 PUBLIC 2011-04-15
The Adaptive Computing Controller enables users to control an adaptive computing landscape
from a single point through observation operation and dynamic resource distribution With
adaptive computing hardware software and system services are able to adapt to changing business
needs In the Adaptive Computing Controller the run-time data of logical and physical landscapes
can be monitored application services can be startedstoppedrelocated and hardware resources
can be assigned to application services The operation can also be mass executed and be planned as
tasks to be executed
For more information about the installation of the Adaptive Computing Controller tool see the
document Installation Guide ndash Adaptive Computing Controller in SAP NetWeaver 71 available on SAP Service
Marketplace at httpservicesapcominstallNWPI71
For more information about Adaptive Computing in general see httpsdnsapcomirj
sdnadaptive
521 Use Cases
You can use the applications and tools described above for use cases that are normally performed
centrally The following sections describe these use cases
5211 End-to-End Solution Operations
Running business applications through their complete life-cycle is a challenge Therefore SAP has
started the Run SAP methodology for implementing End-to-End Solution Operations Based on a set
of SAP standards a roadmap and a package for training and certification Run SAP helps customers to
facilitate End-to-End Solution Operations
You can download the SAP standards for Solution Operations from SAP Service Marketplace at http
servicesapcomsupportstandards They describe roles customers typically have in their IT
environment For optimal role support SAP has grouped existing and new functions in SAP Solution
Manager work centers as of SAP Solution Manager 70 Support Package 15 Operations aspects are fully
covered by adding administrative functions for SAP NetWeaver as well Work centers are ABAP Web
Dynpro-based applications They offer the following advantages
Easy to use similar look and feel
Context transfer while jumping from one work center into another
Logical grouping of tools for a certain area
Simple authorization concept
Easy to expand
Each IT role belongs to one or more work centers For instance the Technical Administrator IT role is
covered by the work centers for System Monitoring System Administration and Landscape Management
The following work centers are available
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3756
Business Process Operations
Change Management
Root Cause Analysis
Implementation Upgrade
Incident Management
Test Management
Job Management
System Landscape Management
Solution Documentation Assistant
SAP Engagement and Service Delivery
SAP Solution Manager Administration
System Administration
System Monitoring
My Home is the central point of access to all important data of almost all work centers in SAP Solution
Manager
5212 Support Infrastructure
A key requirement for effective support of IT solutions is the ability to perform root cause analysis with
speed and efficiency
With SAP Solution Manager SAP has long had an infrastructure in place for its ABAP applications that
efficiently supports SAP solutions This helps ensure the high availability and smooth running of
business processes For more information see the SAP Solution Manager section
With Solution Manager Diagnostics this knowledge has been extended to Java applications If for
example homegrown Java applications cause instability Solution Manager Diagnostics helps trace the
cause to eradicate the problem rapidly Solution Manager Diagnostics is fully integrated into SAP
Solution Manager 70 Solution Manager Diagnostics also contains two third-party tools CArsquos Wily
Introscopereg for measuring performance as well as troubleshooting problems of the Java EE Engine
and applications running on it and Mercury Loadrunnerreg which enables SAP Support to produce a
defined load in the SAP solution landscape remotely For more information see Solution Manager
Diagnostics [page 43]
The support infrastructure provides SAP Support with safe access to your productive landscape for safe
root cause analysis so ensuring that SAP Support does not change your landscape inadvertently You
require a support infrastructure to run SAP NetWeaver
The following figure shows the overall infrastructure including SAP NetWeaver administration tools
that are used by administrators or operators at the customer site
5 System Landscape
52 Shared Services
3856 PUBLIC 2011-04-15
Landscape Aspects
If you use SAP NetWeaver Process Integration 71 productively besides SAP Solution Manager (as a
central support platform) you have to set up Solution Manager Diagnostics for supportability reasons
Implementation Sequence
For information about the implementation of the support infrastructure see the document Master
Guide ndash SAP Solution Manager 70 available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution Manager ltReleasegt
5213 Collection of Landscape Data
Amongst other applications and services the support infrastructure and the SAP NetWeaver
administration tools rely on system landscape data
For SAP NetWeaver PI 71 you have to run non-ABAP components in your solution landscape
Therefore the System Landscape Directory is mandatory The landscape data that is automatically
gathered by the System Landscape Directory is replicated to SAP Solution Manager There are several
topology options for the System Landscape Directory They offer different grades of availability
administration and operation effort
For more information see the System Landscape Directory section
5214 Authentication and Single Sign-On
Before implementing your system landscape plan how to implement authentication and how to
integrate different systems into a Single Sign-On landscape Single Sign-On reduces complexity for end
users saving them valuable time while also reducing administration effort for resetting passwords
thereby contributing to TCO reduction
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
5215 Integrated User and Access Management
In a system landscape containing a combination of ABAP and Java components we recommend that
you integrate your user and access management so that you can use the same user data across different
systems administer this data centrally and control access to data SAPs mature fine-grained
authorization concept allows detailed control of access rights SAP NetWeaver provides both ABAP and
Java-based user management solutions The user management solution that you use to administer
your user data depends on factors such as the type of systems that are running in your landscape
If you want to use central user administration we recommend that you run it in a non-production
system If you do not have a central user administration yet you can for example realize it in the SAP
Solution Manager system
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3956
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
522 Examples for the Overall System Landscape of Shared Services
In this section we provide examples of how shared services can be set up depending on the system
landscape they are intended for The following examples aggregate the landscape aspects given in the
Use Cases section
NOTE
The following sections and the figure mostly do not show information about the life-cycle of
shared services For example you may also need a development and testquality assurance system
for SAP Solution Manager You should consider this aspect in addition to the information given
in this section based on your requirements
Small and MediumndashSized Customer Landscapes with Java
As you use Java productively for SAP NetWeaver PI 71 besides SAP Solution Manager you have to set
up additional components for optimal monitoring administration and support Solution Manager
Diagnostics and the central mode of SAP NetWeaver Administrator are already fully integrated into
SAP Solution Manager 70 as the central operations hub For SAP Process Integration you must also
set up SAP NetWeaver Administrator with a special role
We recommend that you do not install SAP Central Process Scheduling in the SAP Solution Manager
system You have to set up and operate the system which hosts your productive scheduler as a mission
critical system
In the SAP Solution Manager system you should set up a local System Landscape Directory in addition
to a central runtime System Landscape Directory This way you have a clear separation between your
management system (SAP Solution Manager) and managed systems in your landscape In addition
SAP Solution Manager then does not rely on a System Landscape Directory running in the production
environment For this setup configure the SLD data suppliers of your SAP Solution Manager system
to send data to the central runtime System Landscape Directory In addition configure automatic
bridge forwarding from your runtime System Landscape Directory to the local System Landscape
Directory For more information see the Planning Guide - System Landscape Directory
If you want to use a central system for Adobe Document Services we recommend that you install a
dedicated system for this purpose in your production environment For detailed information about
the sizing of the system for the different use cases see the Sizing Guide for Adobe Document Services at
SAP Service Marketplace at httpservicesapcomsizing Sizing Guidelines Solutions amp
Platform
We recommend that you start with this centralized SAP Solution Manager approach as depicted in the
following figure
5 System Landscape
52 Shared Services
4056 PUBLIC 2011-04-15
Figure 7 Single SAP Solution Manager Landscape
Large Customer Landscapes with Java
Large customers who have environments in their landscape that are large and distributed administered
by different groups or separated for security reasons can consider a distributed operations setup In
addition to the centralized setup described for small- and medium-sized customers above large
customers can put parts of the central management functions on extra hosts or systems for performance
or policy reasons You have the following options for a distributed setup
You may set up an extra system or client for Central User Administration (CUA)
The Change and Transport System (CTS) can run on an extra system However it is not
performance- or data-intensive
You may set up an extra system for central CCMS monitoring Depending on the customizing
and on the landscape size central CCMS may generate a lot of system load You can connect a
separate central CCMS to SAP Solution Manager for displaying alerts in the alert inbox of the System
Monitoring work center
You can use a separate SAP NetWeaver 70 system with usage type BI together with SAP Solution
Manager This may make sense with respect to the amount of landscape management data that is
stored for reporting purposes The amount of data strongly depends on the data granularity
storage time frame and landscape size
You can easily put Wily Introscope Enterprise Manager on an separate host
Other aspects described above for small- and medium-customers (such as the setup of the System
Landscape Directory) are also valid for large customers
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4156
523 Feature Details
This section provides further information about the features described above
5231 SAP Solution Manager
SAP provides you with SAP Solution Manager as the strategic application management platform and
to enable the collaboration between you and SAP You need to install at least one productive SAP
Solution Manager in your system landscape To ensure the availability of this application management
platform an SAP Solution Manager system is technically required to install or upgrade to SAP
NetWeaver 70 or higher If you are already using SAP Solution Manager you can also use it to manage
the solution you build with SAP NetWeaver In this case we highly recommend that you update SAP
Solution Manager to the latest version
As of SAP Solution Manager 70 SP15 you can use the newly created work centers
NOTE
During the SAP system installation or upgrade process you are prompted to enter the SAP
Solution Manager key An SAP Solution Manager system is required to generate this key Without
this key the installation or upgrade process cannot continue
You may generate all needed keys for your entire system landscape (development quality
assurance and production system) in one SAP Solution Manager system In case you plan to install
several solution landscapes (for example in different countries) one SAP Solution Manager
system is still sufficient
For more information see SAP Note 805390
It is possible to install multiple SAP Solution Managers If you do so they should host separate business
solutions
If you want to reduce the risk of unavailability you should not install SAP Solution Manager as a central
component Instead you can operate a 2-system-landscape with both a test and production
environment of SAP Solution Manager (especially if you are using time-critical functions like Support
Desk) If you also develop your own content a 3-system-landscape with a development test and
production environment is recommended
For more information about SAP Solution Manager see the following table
Topic Where to Find More Information
System infrastructure scenarios installation and configuration of SAP Solution Manager
Master Guide ndash SAP Solution Manager available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution ManagerltReleasegt
Benefits and usage scenarios SAP Solution Manager ndash Learning Maps available on SAP Service Marketplace at http
5 System Landscape
52 Shared Services
4256 PUBLIC 2011-04-15
Topic Where to Find More Informationservicesapcomrkt-solman or https
servicesapcomsolutionmanager
Additional information See SAP Service Marketplace at http
servicesapcomsolutionmanager
5232 Solution Manager Diagnostics
Solution Manager Diagnostics provides efficient and safe root-cause analysis of incidents in customer
solutions powered by SAP NetWeaver It can help monitor on operating systems databases Java
application activities performance and logs It also supports the reporting of software and
configuration changes that can lead to malfunctions and errors
You must run one Solution Manager Diagnostics within your SAP solution landscape if you run
applications based on SAP NetWeaver systems with usage type AS Java Agents are responsible for
delivering the data from all productive hosts within your system landscape to the Solution Manager
Diagnostics system
CAUTION
SAP Support performs root-cause analysis on incoming incidents with Solution Manager
Diagnostics Not installing and configuring this support infrastructure results in a dramatically
reduced service level
Solution Manager Diagnostics is fully integrated into SAP Solution Manager 70
Solution Manager Diagnostics also contains Wily Introscope (Display Server and Agent part) for
measuring performance as well as to troubleshoot problems of Non-ABAP applications Wily Introscope
is heavily used for troubleshooting applications running on AS Java
SAP has signed a distribution agreement for Wily Introscope SAP customers are allowed to use this
tool in a preconfigured way
For more information about Solution Manager Diagnostics and an FAQ list see SAP Service Marketplace
at httpservicesapcomdiagnostics
5233 System Landscape Directory
The System Landscape Directory (SLD) of SAP NetWeaver is the central directory of system landscape
information relevant for the management of your software life-cycle
NOTE
Note that the abbreviation SLD is not intended to define a product since the System Landscape
Directory is part of SAP NetWeaver This abbreviation is solely intended to improve readability
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4356
The System Landscape Directory contains a description of your system landscape (that is software
components that are currently installed) and a repository of software components that can
theoretically be installed in your landscape (such as the software components available from SAP)
Since this data gets updated automatically the System Landscape Directory provides reliable and up-
to-date system landscape information with as little effort for you as possible In this way the System
Landscape Directory acts as a central information provider for SAP and third-party tools that use this
data to deliver the services you need to keep your landscape up and running
For the System Landscape Directory as part of an SAP NetWeaver PI 71 landscape consider the following
aspects
Part of SAP NetWeaver PI 71 is a new version of the System Landscape Directory It is automatically
included in every SAP NetWeaver 71 system with usage type AS Java It offers enhanced functions
such as a full automatic synchronization mechanism for all data stored in it That is both data
delivered by data suppliers and data entered or changed manually in the System Landscape
Directory can be synchronized automatically This synchronization offers the following
A fully automated mechanism so no user interaction is required and conflicts are resolved
automatically
Asynchronous propagation of information so some nodes may be down temporarily
Communication over HTTP protocol
Uni- and bi-directional synchronization
Depending on your use case the full automatic synchronization could significantly reduce manual
synchronization effort
For SAP NetWeaver PI 71 the configuration of the system landscape directory and its data suppliers
is already included in the standard implementation procedure with SAPinst For existing systems
you only have to perform some quick and easy configuration actions to start operating the system
landscape directory server in an AS Java system
For SAP NetWeaver PI 71 you have the following options concerning SLD
Option 1
Run SAP NetWeaver PI 71 against an existing SLD running on SAP NetWeaver 70 We only
recommend this for upgrades from SAP NetWeaver 70 if you have a central SLD in operation
not running on one of your PI systems
Option 2
Use the SLD included in an SAP NetWeaver PI 71 system We recommend this option for new
installations and upgrades from older releases than SAP NetWeaver 70 due to the enhanced
functions and improved performance of SLD 71
NOTE
If you already have a central SLD running on SAP NetWeaver 70 in operation you could run
two SLD versions in parallel ndash SLD running on SAP NetWeaver 71 for your PI systems and
SLD running on SAP NetWeaver 70 for all other systemsuse cases This way your SAP
5 System Landscape
52 Shared Services
4456 PUBLIC 2011-04-15
NetWeaver PI 71 systems would benefit from the new features while it would be easy to set
up and operate such an SLD landscape For this purpose you could use the new fully
automatic synchronization This feature enables the automatic forwarding of all SLD data
from an SLD running on SAP NetWeaver 70 to an SLD running on SAP NetWeaver 71 As a
result there is no need to adapt most existing systems as their SLD data suppliers could still
send their data to the central SLD In brief the following steps would be required
1 Put SLD in a PI system into operation (part of standard implementation procedure)
2 Configure PI systems to use the new SLD (part of standard implementation procedure
for new PI systems)
3 Set up the fully automatic synchronization from your old SLD to your new SLD
As soon as an upgrade or an installation of a standalone AS Java 71 system is available you
could move your central SLD also to SAP NetWeaver 71 Then you could optionally shift
your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems
Figure 8
We recommend that you use a Domain Name System (DNS) alias so that you are able to switch to
another System Landscape Directory easily For example if customers build a new landscape they
normally start with a sandbox environment Over time more and more environments are set up
Once the production environment is in place move the System Landscape Directory there To do
this you can configure a new System Landscape Directory in the production environment
synchronize it with the old System Landscape directory and switch to the new one
Topology
Apart from the considerations above the System Landscape Directory offers several topology options
with different grades of availability at the expense of low administration and operation effort There is
no generic rule therefore on how to set up a System Landscape Directory in your system landscape
To find the topology and synchronization strategy for the System Landscape Directory that fits your
requirements concerning the System Landscape Directory availability (and hence the availability of
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4556
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
Gateway
It is possible to install an SAP instance of an SAP NetWeaver system based exclusively on a standalone
gateway This type of instance does not contain normal work process types (dialog background update
enqueue or spool) Only the gateway process (gwrd) is started If there is an SNA connection to an R
2 system gateway work processes (gwwp) are also started
SAP Conversion Agent by Informatica
SAP Conversion Agent by Informatica is a data conversion tool that enables you to create interfaces
between any data formats and XML-based systems SAP Conversion Agent can convert unstructured
semi-structured and structured formats to XML and the other way around The Conversion Agent
comprises the Conversion Agent Studio and the Conversion Agent Engine In the Conversion Agent
Studio you can develop and configure data conversions The Conversion Agent Engine executes the
data conversions
Search and Classification (TREX)
You can use Search and Classification with SAP NetWeaver PI to search for messages that were previously
indexed Message search using index provides additional methods of searching for specific messages In
addition to static header attributes you can also use adapter-specific message attributes and data from
the message payload for the search A requirement of this however is that the messages are indexed
first You can apply the index-based message search to one or all indexed components of an integration
landscape (domain) Integration Server Adapter Engines and ABAP business systems
For more information see the SAP Library [page 12] at Administratorrsquos Guide Technical Operations for SAP
NetWeaver Administration of SAP NetWeaver Systems Administering PI (Process Integration) Monitoring Index
Administration
Web Dispatcher
The Web Dispatcher lies between the Internet and your SAP system It is the entry point for HTTP(s)
requests into your system which consists of one or more SAP NetWeaver application servers As a
software web switch the Web dispatcher can reject connections or accept them When it accepts a
connection it balances the load to ensure an even distribution across the servers
You can use the Web dispatcher in ABAPJava systems and in pure Java systems as well as in pure ABAP
systems
It is also beneficial to use the Web Dispatcher if you do not need security functions (entry point in the
demilitarized zone (DMZ) SSL URL filtering) but you simply want to balance the load between
multiple SAP NetWeaver Application Server instances
Since Web Dispatcher is optional for every SAP system it is not contained in the system landscape and
the implementation sequence of the use case in this documentation
For more information see the SAP Library [page 12] at Function Oriented View Application Server Infrastructure
SAP Web Dispatcher
3 SAP NetWeaver PI Overview
31 Installable Software Units
2056 PUBLIC 2011-04-15
Advanced Adapter Engine
You use the Advanced Adapter Engine to connect to SAP systems (RFC adapter) and external systems
You use the various adapters in Advanced Adapter Engine to convert XML- and HTTP-based messages
to the specific protocol and format required by these systems and the other way around For specific
senderreceiver combinations messages can be processed without invoking the central Integration
Engine In principle you connect external systems using the adapters that are installed centrally or
non-centrally in Advanced Adapter Engine You can use the Advanced Adapter Engine that is part of
your PI system as a central Advanced Adapter Engine Optionally (for performance reasons) you can
install a non-central Advanced Adapter Engine separately as a system with AS Java and parts of the
usage type PI on a separate host
Adapter Engine (Java SE)
Adapter Engine (Java SE) is a separate software unit You can use it only if you have SAP NetWeaver
systems with usage type PI in your system landscape It has to be installed manually You use the Adapter
Engine (Java SE) to connect to external systems Using the various adapters in the Adapter Engine (Java
SE) XML and HTTP-based messages can be converted to the specific protocol and format required by
such systems and the other way around The Adapter Engine (Java SE) only provides some of these
adapters as a standalone version with restricted functions for operating systems that do not support
SAP NetWeaver PI 71 but that have at least a Java Runtime Environment 50 Therefore you should
use the Adapter Engine (Java SE) only if the platform prerequisites do not allow you to use the Advanced
Adapter Engine
SAP Partner Connectivity Kit
SAP Partner Connectivity Kit (PCK) runs on AS Java with parts of the usage type PI It enables a system
of a smaller company or subsidiary that does not run SAP NetWeaver PI to connect to your SAP
NetWeaver systems
313 Clients
Clients are additional installable programs or tools They reside either on local front-end PCs accessed
by users or on back-end systems where they act as client programs within an SAP NetWeaver system
landscape
The clients that you can use with SAP NetWeaver Process Integration are described in the following
sections
SAP GUI
NOTE
We recommend that you use the following versionsI
SAP GUI for Windows 710 (or higher) with the latest patch level
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 2156
SAP GUI for Java 710 (or higher) with the latest revision
The integrated SAP ITS 710
For more information about the SAP GUI family see SAP Service Marketplace at http
servicesapcomsapgui
SAP offers three different client applications for accessing ABAP applications in SAP systems (such as
SAP NetWeaver systems with usage type AS ABAP) This SAP GUI family consists of
SAP GUI for HTML
SAP GUI for HTML is based on the SAP integrated Internet Transaction Server (ITS) which is
included in the installation of SAP NetWeaver systems as of SAP NetWeaver 2004 On the client
side only a suitable browser (such as Internet Explorer 70 or Firefox 20) and a virtual machine are
required SAP ITS 620 is not compatible with SAP NetWeaver 71
SAP GUI for the Java environment (SAP GUI for Java)
SAP GUI for Java is a generic SAP GUI that covers a variety of platforms
For more information about the installation of SAP GUI for Java see the documentation Installation
Guide ndash SAP Front End
SAP GUI for the Windows environment (SAP GUI for Windows)
SAP GUI for Windows is SAPs universal client for accessing all SAP applications built on ABAP
technology It is available on the Microsoft Windows platform only and offers the broadest feature
set of all members of the SAP GUI family
For more information about the installation of SAP GUI for Windows see the Installation Guide ndash
SAP Front End
SAP NetWeaver Developer Studio
The SAP NetWeaver Developer Studio is SAPrsquos Integrated Development Environment (IDE) for Java
and is based on the open-source tools framework Eclipse 33 With the SAP NetWeaver Developer Studio
you can develop Java EE 5 applications from scratch using the built-in support for new technologies
such as EJB 30 and JSF 12
During the installation of the SAP NetWeaver Developer Studio several features are offered for
installation For SAP NetWeaver PI 71 only the following features are relevant
SAP NetWeaver Developer Studio Platform
SAP NetWeaver Developer Studio Java EE
NOTE
If you want to use one of the other features you need SAP NetWeaver Composition Environment
and a corresponding developers licence
For more information about the installation of SAP NetWeaver Developer Studio see the Installation
Guide ndash SAP NetWeaver Developer Studio 71 or Installation Guide ndash SAP NetWeaver Developer Studio 71 Including
Enhancement Package 1
3 SAP NetWeaver PI Overview
31 Installable Software Units
2256 PUBLIC 2011-04-15
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
SAP enhancement packages are a new way of delivering new functions for SAP NetWeaver This allows
a clear separation between the delivery of new functions on the one hand and corrections legal changes
and security updates on the other hand (in Support Package stacks) SAP enhancement packages are
cumulative an enhancement package always contains the functions of the corresponding predecessor
enhancement packages
Enhancement packages are maintained by their own Support Packages while the main release is in
maintenance
Benefits
SAP enhancement packages offer the following benefits
You have reduced effort for testing and no effort for training when applying Support Packages as
new features are only shipped with enhancement packages
Adding new functions between releases becomes predictable and controllable
New functions can be added successively in small steps There is no need to fully upgrade your
system to get new functions
You have minimal training effort when applying an enhancement package because existing
functions are not replaced
Implementation
There are the following ways to get an SAP NetWeaver system with the release level of SAP enhancement
package 1 for SAP NetWeaver Process Integration 71
New installation of SAP NetWeaver PI 71 including enhancement package 1 using the standard
installation tool SAPinst
Upgrade of an existing SAP NetWeaver system from a release lower than SAP NetWeaver PI 71 to
SAP NetWeaver PI 71 including enhancement package 1 For this you use the upgrade programs
SAPup (for ABAP) and SAPJup (for Java)
Installation of the enhancement package on an existing SAP NetWeaver PI 71 system
For this you use the Software Update Manager (SUM) The Software Update Manager evolved
from the previously used SAP Enhancement Package Installer The tool has been renamed to reflect
its broader use for example you can also use it for applying Support Package Stacks to your system
On the ABAP side the Software Update Manager uses a system cloning and switch procedure for
installing enhancement packages It installs a copy of the system the shadow system parallel to
the original system This shadow system is used to update the relevant software components and
to install the additional components while the original system is still in production operation At
a certain point during downtime the switch to the new system is made and afterwards any parts
of the original system that are no longer needed are deleted The enhancement package installation
in a Java system uses a deploy-based procedure that is no shadow system is used The Software
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2011-04-15 PUBLIC 2356
Update Manager requires a stack configuration file (xml file) as input file for the enhancement
package installation procedure This file lists all the packages that are to be installed in your systems
The stack configuration file is generated when you download the required packages
As the Software Update Manager is updated regularly we recommend to always use the latest
version It is delivered as part of the SL toolset For more information see http
servicesapcomsltoolset
For an overview of all required steps for the enhancement package installation process and
corresponding documents see Process Overview Installation of Enhancement Package 1 on an Existing SAP
Netweaver PI 71 System [page 28]
Content of SAP Enhancement Package 1 for SAP NetWeaver PI 71
With enhancement package 1 for SAP NetWeaver PI 71 new features are introduced and some existing
are changed The following is a selection of some of the most important enhancements
Enhanced design and modelling options in the Enterprise Services Repository
New services registry
Support for new Web services standard (Web Services Reliable Messaging)
New modules for the Advanced Adapter Engine
Use of shared memory of the ABAP Application Server for message processing
For more information about the changes see SAP Library [page 12] at Whatacutes new in SAP NetWeaver PI 71
ndash Release Notes
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2456 PUBLIC 2011-04-15
4 SOA-Based Integration Use Case
41 Overview
You can use SOA-based integration to set up the communication between service providers and service
consumers in both application-to-application and business-to-business scenarios and to execute
operate and monitor the communication at runtime SOA-based integration covers both direct (point-
to-point) as well as mediated (via an Integration Server) communication between service providers and
service consumers
The use case spans the whole life cycle of a SOA-based integration scenario including
Scenario modeling and service design in the Enterprise Services Repository
Implementation of the service provider and consumer in the back-end systems
Configuration and finally execution monitoring and operation of the integration scenario
For scenarios using Integration Server or broker-based communication the configuration of the
different connectivity options (for example SOAP RFC Web Services Industry standards and JDBC)
and their enhancements is covered
For more information see the following documents
Service-Enabling with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdnsoa-modeling
Getting Started
Service-Enabling a Legacy Application with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdn
soa-servicebus Getting Started
In the following you will find information about the installation of the involved software units
42 System Landscape
The following figure shows the system landscape for this use case
4 SOA-Based Integration Use Case
41 Overview
2011-04-15 PUBLIC 2556
Figure 5 SOA-Based Integration
It is mandatory to have a dedicated PI system This applies to development quality and production
landscapes
For PI it is a prerequisite that no other system in your system landscape has a higher release than
the PI system For exceptions to this rule see SAP Note 1043047 For example SAP XI 30 is compatible
with SAP NetWeaver 640 and 70 application systems since the same XI protocol is used Apart
from these exceptions if you want to upgrade or install an application in your system landscape
you first have to make sure that the PI system is on the same release level If required you have to
upgrade the PI system first to the new or a higher release
CAUTION
Although it should be technically possible to run an application system with a higher release
than your PI system in your system landscape this is not supported by SAP (apart from the
exceptions listed in SAP Note 1043047) Therefore you run such a landscape at your own risk
You can use the Advanced Adapter Engine that is part of your PI system as a central Advanced
Adapter Engine
Adapter Engine (Java SE) can be installed in a non-SAP Java environment However it only hosts
a subset of the adapter functionality is only supported for compatibility reasons and should be
used only if this is a precondition in your environment
Optionally you can use the Change Management Service (CMS) of an SAP NetWeaver 70 system
with usage type DI to transport design objects and repository objects For more information see
the SAP Library [page 12] at Administratoracutes Guide Technical Operations for SAP NetWeaver Administration
of SAP NetWeaver Systems PI (Process Integration) Software Logistics Transporting ESR Content and Objects
of Integration Directory PI Transports Using the Change Management Service (CMS)
Smaller business partners or subsidiaries that do not run SAP NetWeaver install SAP Partner
Connectivity Kit in their system landscape SAP Partner Connectivity Kit enables XML document
4 SOA-Based Integration Use Case
42 System Landscape
2656 PUBLIC 2011-04-15
exchange between your SAP NetWeaver systems and the partner systems Since SAP Partner
Connectivity Kit gets installed in their system landscape it is not shown in the system landscape
figure above
The AS ABAP system acts as an application and service provider For Java Web Services you also
require AS Java In addition you require SAP NetWeaver Developer Studio on the client side as a
development environment
The Web service client can be either an SAP or a non-SAP application For example an AS ABAP
system or a Web browser could act as application or service consumer
You can install SAP Conversion Agent by Informatica in the system with usage type PI or on a host
where SAP Partner Connectivity Kit is installed or on a host where neither usage type PI nor SAP
Partner Connectivity Kit is installed
43 Implementation Sequence
Procedure
To install this use case perform the steps listed in the following table
StepAction[Corresponding Documentation] Remarks
1 Make sure that you have performed the preparation steps You have planned your system landscape [page 33]
(that is you have decided how many systems you require how you want to use each of these systems and which standalone engines and clients you require)
With the help of your hardware partner you have mapped your systems and standalone engines to properly sized hosts
You have planned and installed shared services [page 35]
2 Installation of system with usage type PI (includes the installation of AS ABAP and AS Java)
NOTE
For usage type PI a Unicode installation is mandatory
[Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt]
If you want to use the features of enhancement package 1 use the direct installation of SAP NetWeaver PI 71 including enhancement package 1
Make sure that you perform the configuration steps as described in the installation guide For certain usage types configuration tasks can be applied by the configuration wizard These configuration tasks as well as any additional configuration steps for your use case are listed in SAP Solution Manager For more information
4 SOA-Based Integration Use Case
43 Implementation Sequence
2011-04-15 PUBLIC 2756
StepAction[Corresponding Documentation] Remarks
see the Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt
3 Install the Adapter Engine (Java SE) engines if required[Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
4 To integrate small business partners and subsidiaries the business partners or subsidiaries install SAP Partner Connectivity Kit running on AS Java with parts of usage type PI in the business partners or subsidiarys system landscape[Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
5 Install SAP Conversion Agent by Informatica if required[SAP Library [page 12] at Function-Oriented View Process Integration SAP Conversion Agent by Informatica Deploying and Using Conversion Agent ]
6 Installation of clients SAP GUI
[Installation Guide ndash SAP Front End]
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
The process sequences give a comprehensive overview of the steps relevant for the enhancement
package installation on an existing SAP NetWeaver PI 71 system
The process sequence is divided into a planning phase and an implementation phase Each step in both
phases contains references to the corresponding documentation to ensure that you can easily find the
information you need
Process
NOTE
To download the enhancement package files and required Support Packages you require the SAP
Solution Manager Maintenance Optimizer You have the following options
Manual Selection
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2856 PUBLIC 2011-04-15
You manually select the required files from SAP Service Marketplace at http
servicesapcomswdc using the SP Stack Application You use the Maintenance Optimize
only to approve the packages which is a prerequisite for the download
Automatic Calculation
The Maintenance Optimizer supports the download of a consistent queue that includes all
necessary Support Packages and enhancement packages In addition SAP Solution Manager
calculates a valid import queue for the selected SAP system and generates the enhancement
package stack configuration file that you require for the installation
As a prerequisite the system that you want to update needs to be maintained correctly in
SAP Solution Manager System Landscape As the Maintenance Optimizer uses this data for
the calculation it is crucial that the data is up-to-date In addition the SAP Solution Manager
system requires a Minimum Support Package level (see below)
Planing PhaseStep Description Documentation
Hardware amp Software Prerequisites
Check which platforms are supported for your target release (OSDB dependencies)
Product Availability Matrix (PAM) at httpservicesapcompam
Check which hardware sizing is required for your target release
Sizing information at httpservicesapcomsizing
Solution Manager Prerequisites
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of the required software packages you have to make sure that your SAP Solution Manager system has the required Support Package levelAt least SAP Solution Manager 70 EHP1 Support Package Stack 17 is required We recommend to use SAP Solution Manager 70 EHP1 Support Package Stack 23Check if you need to do an update or upgrade of your SAP Solution ManagerMake sure that you run the guided procedure SOLMAN_SETUP after every installation or update of SAP Solution Manager and that it completes successfully
For upgrades from source release SAP Solution Manager 31 and 32Upgrade Guide ndash SAP Solution Manager 70 incl Enhancement Package 1For updates from SAP Solution Manager 70Update Guide SAP Enhancement Package 1 for SAP Solution Manager 70Follow-up activities after an Support Package Stack update or enhancement package updateSolution Operations Guide ndash SAP Solution Manager 70 EHP1 section Software Change Management All guides are available at http
servicesapcom instguides SAP Components SAP Solution Manager -gt Release 70 EHP 1
Implementation PhaseStep Description Documentation
1Solution Manager Preparation
Configure the SAP Solution Manager Maintenance Optimizer
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of software packages make sure your
Configuration of Maintenance Optimizer http
helpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Change Request Management and Change ControlMaintenance Optimizer
Prerequisites
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 2956
Implementation PhaseStep Description Documentation
system landscape data in SAP Solution Manager is maintained correctlyLandscape Verification 10 which is an add-on to SAP Solution Manager can support you in maintaining your system landscape data The use of this tool is optional
Landscape Verification http
wwwsdnsapcom irj
sdn alm-update-
management link Landscape Verification under Related Areas on Upgrade and Update Management (in the right column)
SAP Note 1468605 (Installation of Landscape Verification)
Maintaining System Landscape Information [page 47]Note that the information provided in this section is based on SAP Solution Manager 70 EHP1 SP23
2System Preparation
Prepare your system as described in the documentation for example perform OS DB specific preparations and the PI-specific preparations
Update Guide ndash Update of SAP Systems with Software Update Manager sections Planning and Preparation
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
3Software Download
Select and download the software packages in either of the following ways Automatic calculation Create
a maintenance transaction in the Maintenance Optimizer and choose the Calculate Files Automatically option
Manual Selection Create a maintenance transaction in the Maintenance Optimizer and choose the Select Files Manually option You then can select the files manually using the SP Stack application in SAP Service Marketplace
NOTE
You have to download the stack configuration file manually after you have selected all files in the SP Stack
httphelpsapcom SAP Solutions SAP Solution Manager
SAP Solution Manager 70 EHP1 ltSPgtChange Request Management and
Change Control Maintenance Optimizer Maintenance Procedure Scenarios
For information about the automatic calculation see Maintenance Transaction with Installation of an Enhancement PackageFor information about the manual selection and approval process see section Approve and Download Files in Download Basket
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
3056 PUBLIC 2011-04-15
Implementation PhaseStep Description Documentation
application Choose Generate Stack XML and save the file
4Enhancement Package Installation
Run Software Update Manager to update your system with the selected software packages
Update Guide ndash Update of SAP Systems with Software Update Manager
5Follow-Up Steps
Perform technical and PI-specific follow-up activities after the enhancement package installation is done
Update Guide ndash Update of SAP Systems with Software Update Manager section Follow-Up Activities
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
6Configuration
Configure newly installed enhancement package functions using SAP Solution Manager content
See Systems with Usage Types [page 16] section Configuration of Systems with Usage Types
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 3156
This page is left blank for documents that are printed on both sides
5 System Landscape
51 Planning Your System Landscape
The installable software units that make up your system landscape depend on the functions that you
want to implement For information about the features see systems [page 16] standalone engines [page 19]
and clients [page 21]
In addition you have to determine the required shared services [page 35] (such as SAP Solution Manager
or SAP NetWeaver Administrator) that run on central systems in your system landscape and the
landscape aspects relevant for their implementation
In the following you will find general information that you should consider when planning your system
landscape
Sizing
You have to map systems and standalone engines to hosts after you have a clear picture of the following
Which systems and standalone engines you require
How many systems you require and how you want to use each of these systems
NOTE
No general guideline can be given for the sizing of your landscape since this relies heavily on your
requirements You should therefore perform this task together with your hardware partner and
your technical consultant
For information about sizing your systems you can use the following information sources
Your first point of reference is the Quick Sizer
SAP built the Quick Sizer as an online sizing questionnaire Internet application in close cooperation
with its hardware partners This tool delivers general sizing categories based on your volume load
estimates The results provide an objective basis for sizing independent of platform and
configuration
For more information see SAP Service Marketplace at
httpservicesapcomsizing for the SAP NetWeaver PI 71 sizing guide available under
Sizing Guidelines Business Suite amp Services
httpservicesapcomquicksizer for more information and access to the tool itself
Also consider the following important aspects concerning sizing
High availability
5 System Landscape
51 Planning Your System Landscape
2011-04-15 PUBLIC 3356
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Technical Infrastructure High Availability
Unicode
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Internationalization
Contact your hardware partner to find out the appropriate number of sized hosts
The platform-independent abstract results of the Quick Sizer can be used by any of our hardware
partners to create a concrete offer SAP itself does not make any hardware recommendations the
responsibility for sizing and detailed hardware configuration lies with the hardware partners
Figure 6 Example of Mapping of Systems and Standalone Engines to Three Hosts
NOTE
Optionally you could also distribute single systems to multiple hosts For example you could
decide to install the database instance of an SAP system on a separate host for performance
reasons or distribute other system instances to achieve high availability
To provide a mapping that fits your required functions and performance your hardware partner
and your technical consultant have to identify the number of required instances of SAP NetWeaver
find out how to distribute these instances to hosts and what functions will run on which instance
Therefore the hardware partner and the technical consultant have to consider many different
aspects such as
Number of required SAPS (SAP Application Benchmark Performance Standard) for each
system (provided by Quick Sizer)
Landscape-relevant aspects concerning security For more information see the SAP Security
Guide in the SAP Library [page 12] at Administratoracutes Guide Security Guide
Landscape-relevant aspects concerning scalability high availability operation and software
life-cycle management
5 System Landscape
51 Planning Your System Landscape
3456 PUBLIC 2011-04-15
For more information about relevant aspects for the mapping of systems to hosts see the document
Technical Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
Scaling and Distribution Options
You may need to design your system landscape for a large number of users SAP NetWeaver PI offers
you different means of scalability The following list provides you with some examples
You could install multiple systems of one type and use them for different purposes
You could scale every system by installing dialog instances or by distributing the database instance
For more information about distribution options on the instance level see the Technical
Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
For every SAP system you could additionally install Web Dispatcher For more information see
the SAP Library [page 12] at FunctionndashOriented View Application Server Infrastructure SAP Web
Dispatcher
You could further distribute certain standalone engines ndash for example Search and Classification
(TREX) is based on a flexible architecture that supports a distributed installation For more
information see the Technical Infrastructure Guide ndash SAP NetWeaver PI 71 available in SAP Service
Marketplace at httpservicesapcominstallNWPI71
52 Shared Services
You normally run shared services on central systems in your system landscape The following features
could be used for SAP NetWeaver Process Integration to realize shared services
SAP Solution Manager
Used to implement train test maintain monitor control change and manage incidents of your
SAP solution system landscape (open end-to-end application management)
As of SAP Solution Manager (70) 40 Support Package 15 SAP Solution Manager has become the
platform for SAPs end-to-end solution operations strategy Functions for complete application
management has been combined with administrative tools and has been merged in newly created
role based work centers
NOTE
Be aware that you require an SAP Solution Manager system to install or upgrade to SAP
NetWeaver 70 and higher An SAP Solution Manager system is required to generate the SAP
Solution Manager key needed during the installation or upgrade process Without this key
the installation or upgrade process cannot continue
For SAP NetWeaver Process Integration you require SAP Solution Manager 70
For more information see SAP Note 805390
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3556
Solution Manager Diagnostics
An integral part of SAP Solution Manager that is running as a Java application on the Java stack of
SAP Solution Manager 70 Solution Manager Diagnostics is used to analyze the root cause of
incidents in your landscape in an efficient and safe way Before Go-Live Solution Manager
Diagnostics has to be set up and made accessible remotely
SAP NetWeaver Administrator
SAP NetWeaver Administrator is the central administration component which is used for
monitoring and administering Java applications It is included in SAP NetWeaver systems with AS
Java
SAP NetWeaver Administrator exists in the following flavors
A local mode which runs out of the box and which focuses on administrating the underlying
SAP NetWeaver AS Java
NOTE
For a SAP NetWeaver PI 71 it has a special role which you need to activate using a
configuation wizard
A central mode which has to be configured before use and which deals with the system
landscape management
SAP has decided to merge the central mode of SAP NetWeaver Administrator into the new work
centers available as of SAP Solution Manager 70 SP 15 Thus it can be used in an administrative
context together with non-Java-based administration tools Although the central mode of SAP
NetWeaver Administrator will be still available for some time SAP will not develop this tool any
further SAP focuses on optimizing the administrative work centers of SAP Solution Manager
instead
The local mode of SAP NetWeaver Administrator stays untouched It is available for current and
future releases of SAP NetWeaver
SAP Central Process Scheduling by Redwood
SAP Central Process Scheduling application by Redwood enables central job scheduling and job
monitoring of current and old releases of AS ABAP systems (as of Basis Release 31) This application
is fully integrated in SAP NetWeaver Depending on the business needs SAP business applications
are the initial trigger for scheduled activities You can now manage jobs and job chains conveniently
using a graphical user interface
System Landscape Directory
The System Landscape Directory is the central directory of system landscape information relevant
for the management of your software life-cycle It contains a description of your system landscape
(that is software components that are currently installed) and a repository of software components
that can theoretically be installed in your landscape (such as the software components available
from SAP)
Adaptive Computing Controller
5 System Landscape
52 Shared Services
3656 PUBLIC 2011-04-15
The Adaptive Computing Controller enables users to control an adaptive computing landscape
from a single point through observation operation and dynamic resource distribution With
adaptive computing hardware software and system services are able to adapt to changing business
needs In the Adaptive Computing Controller the run-time data of logical and physical landscapes
can be monitored application services can be startedstoppedrelocated and hardware resources
can be assigned to application services The operation can also be mass executed and be planned as
tasks to be executed
For more information about the installation of the Adaptive Computing Controller tool see the
document Installation Guide ndash Adaptive Computing Controller in SAP NetWeaver 71 available on SAP Service
Marketplace at httpservicesapcominstallNWPI71
For more information about Adaptive Computing in general see httpsdnsapcomirj
sdnadaptive
521 Use Cases
You can use the applications and tools described above for use cases that are normally performed
centrally The following sections describe these use cases
5211 End-to-End Solution Operations
Running business applications through their complete life-cycle is a challenge Therefore SAP has
started the Run SAP methodology for implementing End-to-End Solution Operations Based on a set
of SAP standards a roadmap and a package for training and certification Run SAP helps customers to
facilitate End-to-End Solution Operations
You can download the SAP standards for Solution Operations from SAP Service Marketplace at http
servicesapcomsupportstandards They describe roles customers typically have in their IT
environment For optimal role support SAP has grouped existing and new functions in SAP Solution
Manager work centers as of SAP Solution Manager 70 Support Package 15 Operations aspects are fully
covered by adding administrative functions for SAP NetWeaver as well Work centers are ABAP Web
Dynpro-based applications They offer the following advantages
Easy to use similar look and feel
Context transfer while jumping from one work center into another
Logical grouping of tools for a certain area
Simple authorization concept
Easy to expand
Each IT role belongs to one or more work centers For instance the Technical Administrator IT role is
covered by the work centers for System Monitoring System Administration and Landscape Management
The following work centers are available
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3756
Business Process Operations
Change Management
Root Cause Analysis
Implementation Upgrade
Incident Management
Test Management
Job Management
System Landscape Management
Solution Documentation Assistant
SAP Engagement and Service Delivery
SAP Solution Manager Administration
System Administration
System Monitoring
My Home is the central point of access to all important data of almost all work centers in SAP Solution
Manager
5212 Support Infrastructure
A key requirement for effective support of IT solutions is the ability to perform root cause analysis with
speed and efficiency
With SAP Solution Manager SAP has long had an infrastructure in place for its ABAP applications that
efficiently supports SAP solutions This helps ensure the high availability and smooth running of
business processes For more information see the SAP Solution Manager section
With Solution Manager Diagnostics this knowledge has been extended to Java applications If for
example homegrown Java applications cause instability Solution Manager Diagnostics helps trace the
cause to eradicate the problem rapidly Solution Manager Diagnostics is fully integrated into SAP
Solution Manager 70 Solution Manager Diagnostics also contains two third-party tools CArsquos Wily
Introscopereg for measuring performance as well as troubleshooting problems of the Java EE Engine
and applications running on it and Mercury Loadrunnerreg which enables SAP Support to produce a
defined load in the SAP solution landscape remotely For more information see Solution Manager
Diagnostics [page 43]
The support infrastructure provides SAP Support with safe access to your productive landscape for safe
root cause analysis so ensuring that SAP Support does not change your landscape inadvertently You
require a support infrastructure to run SAP NetWeaver
The following figure shows the overall infrastructure including SAP NetWeaver administration tools
that are used by administrators or operators at the customer site
5 System Landscape
52 Shared Services
3856 PUBLIC 2011-04-15
Landscape Aspects
If you use SAP NetWeaver Process Integration 71 productively besides SAP Solution Manager (as a
central support platform) you have to set up Solution Manager Diagnostics for supportability reasons
Implementation Sequence
For information about the implementation of the support infrastructure see the document Master
Guide ndash SAP Solution Manager 70 available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution Manager ltReleasegt
5213 Collection of Landscape Data
Amongst other applications and services the support infrastructure and the SAP NetWeaver
administration tools rely on system landscape data
For SAP NetWeaver PI 71 you have to run non-ABAP components in your solution landscape
Therefore the System Landscape Directory is mandatory The landscape data that is automatically
gathered by the System Landscape Directory is replicated to SAP Solution Manager There are several
topology options for the System Landscape Directory They offer different grades of availability
administration and operation effort
For more information see the System Landscape Directory section
5214 Authentication and Single Sign-On
Before implementing your system landscape plan how to implement authentication and how to
integrate different systems into a Single Sign-On landscape Single Sign-On reduces complexity for end
users saving them valuable time while also reducing administration effort for resetting passwords
thereby contributing to TCO reduction
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
5215 Integrated User and Access Management
In a system landscape containing a combination of ABAP and Java components we recommend that
you integrate your user and access management so that you can use the same user data across different
systems administer this data centrally and control access to data SAPs mature fine-grained
authorization concept allows detailed control of access rights SAP NetWeaver provides both ABAP and
Java-based user management solutions The user management solution that you use to administer
your user data depends on factors such as the type of systems that are running in your landscape
If you want to use central user administration we recommend that you run it in a non-production
system If you do not have a central user administration yet you can for example realize it in the SAP
Solution Manager system
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3956
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
522 Examples for the Overall System Landscape of Shared Services
In this section we provide examples of how shared services can be set up depending on the system
landscape they are intended for The following examples aggregate the landscape aspects given in the
Use Cases section
NOTE
The following sections and the figure mostly do not show information about the life-cycle of
shared services For example you may also need a development and testquality assurance system
for SAP Solution Manager You should consider this aspect in addition to the information given
in this section based on your requirements
Small and MediumndashSized Customer Landscapes with Java
As you use Java productively for SAP NetWeaver PI 71 besides SAP Solution Manager you have to set
up additional components for optimal monitoring administration and support Solution Manager
Diagnostics and the central mode of SAP NetWeaver Administrator are already fully integrated into
SAP Solution Manager 70 as the central operations hub For SAP Process Integration you must also
set up SAP NetWeaver Administrator with a special role
We recommend that you do not install SAP Central Process Scheduling in the SAP Solution Manager
system You have to set up and operate the system which hosts your productive scheduler as a mission
critical system
In the SAP Solution Manager system you should set up a local System Landscape Directory in addition
to a central runtime System Landscape Directory This way you have a clear separation between your
management system (SAP Solution Manager) and managed systems in your landscape In addition
SAP Solution Manager then does not rely on a System Landscape Directory running in the production
environment For this setup configure the SLD data suppliers of your SAP Solution Manager system
to send data to the central runtime System Landscape Directory In addition configure automatic
bridge forwarding from your runtime System Landscape Directory to the local System Landscape
Directory For more information see the Planning Guide - System Landscape Directory
If you want to use a central system for Adobe Document Services we recommend that you install a
dedicated system for this purpose in your production environment For detailed information about
the sizing of the system for the different use cases see the Sizing Guide for Adobe Document Services at
SAP Service Marketplace at httpservicesapcomsizing Sizing Guidelines Solutions amp
Platform
We recommend that you start with this centralized SAP Solution Manager approach as depicted in the
following figure
5 System Landscape
52 Shared Services
4056 PUBLIC 2011-04-15
Figure 7 Single SAP Solution Manager Landscape
Large Customer Landscapes with Java
Large customers who have environments in their landscape that are large and distributed administered
by different groups or separated for security reasons can consider a distributed operations setup In
addition to the centralized setup described for small- and medium-sized customers above large
customers can put parts of the central management functions on extra hosts or systems for performance
or policy reasons You have the following options for a distributed setup
You may set up an extra system or client for Central User Administration (CUA)
The Change and Transport System (CTS) can run on an extra system However it is not
performance- or data-intensive
You may set up an extra system for central CCMS monitoring Depending on the customizing
and on the landscape size central CCMS may generate a lot of system load You can connect a
separate central CCMS to SAP Solution Manager for displaying alerts in the alert inbox of the System
Monitoring work center
You can use a separate SAP NetWeaver 70 system with usage type BI together with SAP Solution
Manager This may make sense with respect to the amount of landscape management data that is
stored for reporting purposes The amount of data strongly depends on the data granularity
storage time frame and landscape size
You can easily put Wily Introscope Enterprise Manager on an separate host
Other aspects described above for small- and medium-customers (such as the setup of the System
Landscape Directory) are also valid for large customers
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4156
523 Feature Details
This section provides further information about the features described above
5231 SAP Solution Manager
SAP provides you with SAP Solution Manager as the strategic application management platform and
to enable the collaboration between you and SAP You need to install at least one productive SAP
Solution Manager in your system landscape To ensure the availability of this application management
platform an SAP Solution Manager system is technically required to install or upgrade to SAP
NetWeaver 70 or higher If you are already using SAP Solution Manager you can also use it to manage
the solution you build with SAP NetWeaver In this case we highly recommend that you update SAP
Solution Manager to the latest version
As of SAP Solution Manager 70 SP15 you can use the newly created work centers
NOTE
During the SAP system installation or upgrade process you are prompted to enter the SAP
Solution Manager key An SAP Solution Manager system is required to generate this key Without
this key the installation or upgrade process cannot continue
You may generate all needed keys for your entire system landscape (development quality
assurance and production system) in one SAP Solution Manager system In case you plan to install
several solution landscapes (for example in different countries) one SAP Solution Manager
system is still sufficient
For more information see SAP Note 805390
It is possible to install multiple SAP Solution Managers If you do so they should host separate business
solutions
If you want to reduce the risk of unavailability you should not install SAP Solution Manager as a central
component Instead you can operate a 2-system-landscape with both a test and production
environment of SAP Solution Manager (especially if you are using time-critical functions like Support
Desk) If you also develop your own content a 3-system-landscape with a development test and
production environment is recommended
For more information about SAP Solution Manager see the following table
Topic Where to Find More Information
System infrastructure scenarios installation and configuration of SAP Solution Manager
Master Guide ndash SAP Solution Manager available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution ManagerltReleasegt
Benefits and usage scenarios SAP Solution Manager ndash Learning Maps available on SAP Service Marketplace at http
5 System Landscape
52 Shared Services
4256 PUBLIC 2011-04-15
Topic Where to Find More Informationservicesapcomrkt-solman or https
servicesapcomsolutionmanager
Additional information See SAP Service Marketplace at http
servicesapcomsolutionmanager
5232 Solution Manager Diagnostics
Solution Manager Diagnostics provides efficient and safe root-cause analysis of incidents in customer
solutions powered by SAP NetWeaver It can help monitor on operating systems databases Java
application activities performance and logs It also supports the reporting of software and
configuration changes that can lead to malfunctions and errors
You must run one Solution Manager Diagnostics within your SAP solution landscape if you run
applications based on SAP NetWeaver systems with usage type AS Java Agents are responsible for
delivering the data from all productive hosts within your system landscape to the Solution Manager
Diagnostics system
CAUTION
SAP Support performs root-cause analysis on incoming incidents with Solution Manager
Diagnostics Not installing and configuring this support infrastructure results in a dramatically
reduced service level
Solution Manager Diagnostics is fully integrated into SAP Solution Manager 70
Solution Manager Diagnostics also contains Wily Introscope (Display Server and Agent part) for
measuring performance as well as to troubleshoot problems of Non-ABAP applications Wily Introscope
is heavily used for troubleshooting applications running on AS Java
SAP has signed a distribution agreement for Wily Introscope SAP customers are allowed to use this
tool in a preconfigured way
For more information about Solution Manager Diagnostics and an FAQ list see SAP Service Marketplace
at httpservicesapcomdiagnostics
5233 System Landscape Directory
The System Landscape Directory (SLD) of SAP NetWeaver is the central directory of system landscape
information relevant for the management of your software life-cycle
NOTE
Note that the abbreviation SLD is not intended to define a product since the System Landscape
Directory is part of SAP NetWeaver This abbreviation is solely intended to improve readability
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4356
The System Landscape Directory contains a description of your system landscape (that is software
components that are currently installed) and a repository of software components that can
theoretically be installed in your landscape (such as the software components available from SAP)
Since this data gets updated automatically the System Landscape Directory provides reliable and up-
to-date system landscape information with as little effort for you as possible In this way the System
Landscape Directory acts as a central information provider for SAP and third-party tools that use this
data to deliver the services you need to keep your landscape up and running
For the System Landscape Directory as part of an SAP NetWeaver PI 71 landscape consider the following
aspects
Part of SAP NetWeaver PI 71 is a new version of the System Landscape Directory It is automatically
included in every SAP NetWeaver 71 system with usage type AS Java It offers enhanced functions
such as a full automatic synchronization mechanism for all data stored in it That is both data
delivered by data suppliers and data entered or changed manually in the System Landscape
Directory can be synchronized automatically This synchronization offers the following
A fully automated mechanism so no user interaction is required and conflicts are resolved
automatically
Asynchronous propagation of information so some nodes may be down temporarily
Communication over HTTP protocol
Uni- and bi-directional synchronization
Depending on your use case the full automatic synchronization could significantly reduce manual
synchronization effort
For SAP NetWeaver PI 71 the configuration of the system landscape directory and its data suppliers
is already included in the standard implementation procedure with SAPinst For existing systems
you only have to perform some quick and easy configuration actions to start operating the system
landscape directory server in an AS Java system
For SAP NetWeaver PI 71 you have the following options concerning SLD
Option 1
Run SAP NetWeaver PI 71 against an existing SLD running on SAP NetWeaver 70 We only
recommend this for upgrades from SAP NetWeaver 70 if you have a central SLD in operation
not running on one of your PI systems
Option 2
Use the SLD included in an SAP NetWeaver PI 71 system We recommend this option for new
installations and upgrades from older releases than SAP NetWeaver 70 due to the enhanced
functions and improved performance of SLD 71
NOTE
If you already have a central SLD running on SAP NetWeaver 70 in operation you could run
two SLD versions in parallel ndash SLD running on SAP NetWeaver 71 for your PI systems and
SLD running on SAP NetWeaver 70 for all other systemsuse cases This way your SAP
5 System Landscape
52 Shared Services
4456 PUBLIC 2011-04-15
NetWeaver PI 71 systems would benefit from the new features while it would be easy to set
up and operate such an SLD landscape For this purpose you could use the new fully
automatic synchronization This feature enables the automatic forwarding of all SLD data
from an SLD running on SAP NetWeaver 70 to an SLD running on SAP NetWeaver 71 As a
result there is no need to adapt most existing systems as their SLD data suppliers could still
send their data to the central SLD In brief the following steps would be required
1 Put SLD in a PI system into operation (part of standard implementation procedure)
2 Configure PI systems to use the new SLD (part of standard implementation procedure
for new PI systems)
3 Set up the fully automatic synchronization from your old SLD to your new SLD
As soon as an upgrade or an installation of a standalone AS Java 71 system is available you
could move your central SLD also to SAP NetWeaver 71 Then you could optionally shift
your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems
Figure 8
We recommend that you use a Domain Name System (DNS) alias so that you are able to switch to
another System Landscape Directory easily For example if customers build a new landscape they
normally start with a sandbox environment Over time more and more environments are set up
Once the production environment is in place move the System Landscape Directory there To do
this you can configure a new System Landscape Directory in the production environment
synchronize it with the old System Landscape directory and switch to the new one
Topology
Apart from the considerations above the System Landscape Directory offers several topology options
with different grades of availability at the expense of low administration and operation effort There is
no generic rule therefore on how to set up a System Landscape Directory in your system landscape
To find the topology and synchronization strategy for the System Landscape Directory that fits your
requirements concerning the System Landscape Directory availability (and hence the availability of
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4556
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
Advanced Adapter Engine
You use the Advanced Adapter Engine to connect to SAP systems (RFC adapter) and external systems
You use the various adapters in Advanced Adapter Engine to convert XML- and HTTP-based messages
to the specific protocol and format required by these systems and the other way around For specific
senderreceiver combinations messages can be processed without invoking the central Integration
Engine In principle you connect external systems using the adapters that are installed centrally or
non-centrally in Advanced Adapter Engine You can use the Advanced Adapter Engine that is part of
your PI system as a central Advanced Adapter Engine Optionally (for performance reasons) you can
install a non-central Advanced Adapter Engine separately as a system with AS Java and parts of the
usage type PI on a separate host
Adapter Engine (Java SE)
Adapter Engine (Java SE) is a separate software unit You can use it only if you have SAP NetWeaver
systems with usage type PI in your system landscape It has to be installed manually You use the Adapter
Engine (Java SE) to connect to external systems Using the various adapters in the Adapter Engine (Java
SE) XML and HTTP-based messages can be converted to the specific protocol and format required by
such systems and the other way around The Adapter Engine (Java SE) only provides some of these
adapters as a standalone version with restricted functions for operating systems that do not support
SAP NetWeaver PI 71 but that have at least a Java Runtime Environment 50 Therefore you should
use the Adapter Engine (Java SE) only if the platform prerequisites do not allow you to use the Advanced
Adapter Engine
SAP Partner Connectivity Kit
SAP Partner Connectivity Kit (PCK) runs on AS Java with parts of the usage type PI It enables a system
of a smaller company or subsidiary that does not run SAP NetWeaver PI to connect to your SAP
NetWeaver systems
313 Clients
Clients are additional installable programs or tools They reside either on local front-end PCs accessed
by users or on back-end systems where they act as client programs within an SAP NetWeaver system
landscape
The clients that you can use with SAP NetWeaver Process Integration are described in the following
sections
SAP GUI
NOTE
We recommend that you use the following versionsI
SAP GUI for Windows 710 (or higher) with the latest patch level
3 SAP NetWeaver PI Overview
31 Installable Software Units
2011-04-15 PUBLIC 2156
SAP GUI for Java 710 (or higher) with the latest revision
The integrated SAP ITS 710
For more information about the SAP GUI family see SAP Service Marketplace at http
servicesapcomsapgui
SAP offers three different client applications for accessing ABAP applications in SAP systems (such as
SAP NetWeaver systems with usage type AS ABAP) This SAP GUI family consists of
SAP GUI for HTML
SAP GUI for HTML is based on the SAP integrated Internet Transaction Server (ITS) which is
included in the installation of SAP NetWeaver systems as of SAP NetWeaver 2004 On the client
side only a suitable browser (such as Internet Explorer 70 or Firefox 20) and a virtual machine are
required SAP ITS 620 is not compatible with SAP NetWeaver 71
SAP GUI for the Java environment (SAP GUI for Java)
SAP GUI for Java is a generic SAP GUI that covers a variety of platforms
For more information about the installation of SAP GUI for Java see the documentation Installation
Guide ndash SAP Front End
SAP GUI for the Windows environment (SAP GUI for Windows)
SAP GUI for Windows is SAPs universal client for accessing all SAP applications built on ABAP
technology It is available on the Microsoft Windows platform only and offers the broadest feature
set of all members of the SAP GUI family
For more information about the installation of SAP GUI for Windows see the Installation Guide ndash
SAP Front End
SAP NetWeaver Developer Studio
The SAP NetWeaver Developer Studio is SAPrsquos Integrated Development Environment (IDE) for Java
and is based on the open-source tools framework Eclipse 33 With the SAP NetWeaver Developer Studio
you can develop Java EE 5 applications from scratch using the built-in support for new technologies
such as EJB 30 and JSF 12
During the installation of the SAP NetWeaver Developer Studio several features are offered for
installation For SAP NetWeaver PI 71 only the following features are relevant
SAP NetWeaver Developer Studio Platform
SAP NetWeaver Developer Studio Java EE
NOTE
If you want to use one of the other features you need SAP NetWeaver Composition Environment
and a corresponding developers licence
For more information about the installation of SAP NetWeaver Developer Studio see the Installation
Guide ndash SAP NetWeaver Developer Studio 71 or Installation Guide ndash SAP NetWeaver Developer Studio 71 Including
Enhancement Package 1
3 SAP NetWeaver PI Overview
31 Installable Software Units
2256 PUBLIC 2011-04-15
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
SAP enhancement packages are a new way of delivering new functions for SAP NetWeaver This allows
a clear separation between the delivery of new functions on the one hand and corrections legal changes
and security updates on the other hand (in Support Package stacks) SAP enhancement packages are
cumulative an enhancement package always contains the functions of the corresponding predecessor
enhancement packages
Enhancement packages are maintained by their own Support Packages while the main release is in
maintenance
Benefits
SAP enhancement packages offer the following benefits
You have reduced effort for testing and no effort for training when applying Support Packages as
new features are only shipped with enhancement packages
Adding new functions between releases becomes predictable and controllable
New functions can be added successively in small steps There is no need to fully upgrade your
system to get new functions
You have minimal training effort when applying an enhancement package because existing
functions are not replaced
Implementation
There are the following ways to get an SAP NetWeaver system with the release level of SAP enhancement
package 1 for SAP NetWeaver Process Integration 71
New installation of SAP NetWeaver PI 71 including enhancement package 1 using the standard
installation tool SAPinst
Upgrade of an existing SAP NetWeaver system from a release lower than SAP NetWeaver PI 71 to
SAP NetWeaver PI 71 including enhancement package 1 For this you use the upgrade programs
SAPup (for ABAP) and SAPJup (for Java)
Installation of the enhancement package on an existing SAP NetWeaver PI 71 system
For this you use the Software Update Manager (SUM) The Software Update Manager evolved
from the previously used SAP Enhancement Package Installer The tool has been renamed to reflect
its broader use for example you can also use it for applying Support Package Stacks to your system
On the ABAP side the Software Update Manager uses a system cloning and switch procedure for
installing enhancement packages It installs a copy of the system the shadow system parallel to
the original system This shadow system is used to update the relevant software components and
to install the additional components while the original system is still in production operation At
a certain point during downtime the switch to the new system is made and afterwards any parts
of the original system that are no longer needed are deleted The enhancement package installation
in a Java system uses a deploy-based procedure that is no shadow system is used The Software
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2011-04-15 PUBLIC 2356
Update Manager requires a stack configuration file (xml file) as input file for the enhancement
package installation procedure This file lists all the packages that are to be installed in your systems
The stack configuration file is generated when you download the required packages
As the Software Update Manager is updated regularly we recommend to always use the latest
version It is delivered as part of the SL toolset For more information see http
servicesapcomsltoolset
For an overview of all required steps for the enhancement package installation process and
corresponding documents see Process Overview Installation of Enhancement Package 1 on an Existing SAP
Netweaver PI 71 System [page 28]
Content of SAP Enhancement Package 1 for SAP NetWeaver PI 71
With enhancement package 1 for SAP NetWeaver PI 71 new features are introduced and some existing
are changed The following is a selection of some of the most important enhancements
Enhanced design and modelling options in the Enterprise Services Repository
New services registry
Support for new Web services standard (Web Services Reliable Messaging)
New modules for the Advanced Adapter Engine
Use of shared memory of the ABAP Application Server for message processing
For more information about the changes see SAP Library [page 12] at Whatacutes new in SAP NetWeaver PI 71
ndash Release Notes
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2456 PUBLIC 2011-04-15
4 SOA-Based Integration Use Case
41 Overview
You can use SOA-based integration to set up the communication between service providers and service
consumers in both application-to-application and business-to-business scenarios and to execute
operate and monitor the communication at runtime SOA-based integration covers both direct (point-
to-point) as well as mediated (via an Integration Server) communication between service providers and
service consumers
The use case spans the whole life cycle of a SOA-based integration scenario including
Scenario modeling and service design in the Enterprise Services Repository
Implementation of the service provider and consumer in the back-end systems
Configuration and finally execution monitoring and operation of the integration scenario
For scenarios using Integration Server or broker-based communication the configuration of the
different connectivity options (for example SOAP RFC Web Services Industry standards and JDBC)
and their enhancements is covered
For more information see the following documents
Service-Enabling with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdnsoa-modeling
Getting Started
Service-Enabling a Legacy Application with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdn
soa-servicebus Getting Started
In the following you will find information about the installation of the involved software units
42 System Landscape
The following figure shows the system landscape for this use case
4 SOA-Based Integration Use Case
41 Overview
2011-04-15 PUBLIC 2556
Figure 5 SOA-Based Integration
It is mandatory to have a dedicated PI system This applies to development quality and production
landscapes
For PI it is a prerequisite that no other system in your system landscape has a higher release than
the PI system For exceptions to this rule see SAP Note 1043047 For example SAP XI 30 is compatible
with SAP NetWeaver 640 and 70 application systems since the same XI protocol is used Apart
from these exceptions if you want to upgrade or install an application in your system landscape
you first have to make sure that the PI system is on the same release level If required you have to
upgrade the PI system first to the new or a higher release
CAUTION
Although it should be technically possible to run an application system with a higher release
than your PI system in your system landscape this is not supported by SAP (apart from the
exceptions listed in SAP Note 1043047) Therefore you run such a landscape at your own risk
You can use the Advanced Adapter Engine that is part of your PI system as a central Advanced
Adapter Engine
Adapter Engine (Java SE) can be installed in a non-SAP Java environment However it only hosts
a subset of the adapter functionality is only supported for compatibility reasons and should be
used only if this is a precondition in your environment
Optionally you can use the Change Management Service (CMS) of an SAP NetWeaver 70 system
with usage type DI to transport design objects and repository objects For more information see
the SAP Library [page 12] at Administratoracutes Guide Technical Operations for SAP NetWeaver Administration
of SAP NetWeaver Systems PI (Process Integration) Software Logistics Transporting ESR Content and Objects
of Integration Directory PI Transports Using the Change Management Service (CMS)
Smaller business partners or subsidiaries that do not run SAP NetWeaver install SAP Partner
Connectivity Kit in their system landscape SAP Partner Connectivity Kit enables XML document
4 SOA-Based Integration Use Case
42 System Landscape
2656 PUBLIC 2011-04-15
exchange between your SAP NetWeaver systems and the partner systems Since SAP Partner
Connectivity Kit gets installed in their system landscape it is not shown in the system landscape
figure above
The AS ABAP system acts as an application and service provider For Java Web Services you also
require AS Java In addition you require SAP NetWeaver Developer Studio on the client side as a
development environment
The Web service client can be either an SAP or a non-SAP application For example an AS ABAP
system or a Web browser could act as application or service consumer
You can install SAP Conversion Agent by Informatica in the system with usage type PI or on a host
where SAP Partner Connectivity Kit is installed or on a host where neither usage type PI nor SAP
Partner Connectivity Kit is installed
43 Implementation Sequence
Procedure
To install this use case perform the steps listed in the following table
StepAction[Corresponding Documentation] Remarks
1 Make sure that you have performed the preparation steps You have planned your system landscape [page 33]
(that is you have decided how many systems you require how you want to use each of these systems and which standalone engines and clients you require)
With the help of your hardware partner you have mapped your systems and standalone engines to properly sized hosts
You have planned and installed shared services [page 35]
2 Installation of system with usage type PI (includes the installation of AS ABAP and AS Java)
NOTE
For usage type PI a Unicode installation is mandatory
[Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt]
If you want to use the features of enhancement package 1 use the direct installation of SAP NetWeaver PI 71 including enhancement package 1
Make sure that you perform the configuration steps as described in the installation guide For certain usage types configuration tasks can be applied by the configuration wizard These configuration tasks as well as any additional configuration steps for your use case are listed in SAP Solution Manager For more information
4 SOA-Based Integration Use Case
43 Implementation Sequence
2011-04-15 PUBLIC 2756
StepAction[Corresponding Documentation] Remarks
see the Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt
3 Install the Adapter Engine (Java SE) engines if required[Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
4 To integrate small business partners and subsidiaries the business partners or subsidiaries install SAP Partner Connectivity Kit running on AS Java with parts of usage type PI in the business partners or subsidiarys system landscape[Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
5 Install SAP Conversion Agent by Informatica if required[SAP Library [page 12] at Function-Oriented View Process Integration SAP Conversion Agent by Informatica Deploying and Using Conversion Agent ]
6 Installation of clients SAP GUI
[Installation Guide ndash SAP Front End]
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
The process sequences give a comprehensive overview of the steps relevant for the enhancement
package installation on an existing SAP NetWeaver PI 71 system
The process sequence is divided into a planning phase and an implementation phase Each step in both
phases contains references to the corresponding documentation to ensure that you can easily find the
information you need
Process
NOTE
To download the enhancement package files and required Support Packages you require the SAP
Solution Manager Maintenance Optimizer You have the following options
Manual Selection
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2856 PUBLIC 2011-04-15
You manually select the required files from SAP Service Marketplace at http
servicesapcomswdc using the SP Stack Application You use the Maintenance Optimize
only to approve the packages which is a prerequisite for the download
Automatic Calculation
The Maintenance Optimizer supports the download of a consistent queue that includes all
necessary Support Packages and enhancement packages In addition SAP Solution Manager
calculates a valid import queue for the selected SAP system and generates the enhancement
package stack configuration file that you require for the installation
As a prerequisite the system that you want to update needs to be maintained correctly in
SAP Solution Manager System Landscape As the Maintenance Optimizer uses this data for
the calculation it is crucial that the data is up-to-date In addition the SAP Solution Manager
system requires a Minimum Support Package level (see below)
Planing PhaseStep Description Documentation
Hardware amp Software Prerequisites
Check which platforms are supported for your target release (OSDB dependencies)
Product Availability Matrix (PAM) at httpservicesapcompam
Check which hardware sizing is required for your target release
Sizing information at httpservicesapcomsizing
Solution Manager Prerequisites
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of the required software packages you have to make sure that your SAP Solution Manager system has the required Support Package levelAt least SAP Solution Manager 70 EHP1 Support Package Stack 17 is required We recommend to use SAP Solution Manager 70 EHP1 Support Package Stack 23Check if you need to do an update or upgrade of your SAP Solution ManagerMake sure that you run the guided procedure SOLMAN_SETUP after every installation or update of SAP Solution Manager and that it completes successfully
For upgrades from source release SAP Solution Manager 31 and 32Upgrade Guide ndash SAP Solution Manager 70 incl Enhancement Package 1For updates from SAP Solution Manager 70Update Guide SAP Enhancement Package 1 for SAP Solution Manager 70Follow-up activities after an Support Package Stack update or enhancement package updateSolution Operations Guide ndash SAP Solution Manager 70 EHP1 section Software Change Management All guides are available at http
servicesapcom instguides SAP Components SAP Solution Manager -gt Release 70 EHP 1
Implementation PhaseStep Description Documentation
1Solution Manager Preparation
Configure the SAP Solution Manager Maintenance Optimizer
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of software packages make sure your
Configuration of Maintenance Optimizer http
helpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Change Request Management and Change ControlMaintenance Optimizer
Prerequisites
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 2956
Implementation PhaseStep Description Documentation
system landscape data in SAP Solution Manager is maintained correctlyLandscape Verification 10 which is an add-on to SAP Solution Manager can support you in maintaining your system landscape data The use of this tool is optional
Landscape Verification http
wwwsdnsapcom irj
sdn alm-update-
management link Landscape Verification under Related Areas on Upgrade and Update Management (in the right column)
SAP Note 1468605 (Installation of Landscape Verification)
Maintaining System Landscape Information [page 47]Note that the information provided in this section is based on SAP Solution Manager 70 EHP1 SP23
2System Preparation
Prepare your system as described in the documentation for example perform OS DB specific preparations and the PI-specific preparations
Update Guide ndash Update of SAP Systems with Software Update Manager sections Planning and Preparation
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
3Software Download
Select and download the software packages in either of the following ways Automatic calculation Create
a maintenance transaction in the Maintenance Optimizer and choose the Calculate Files Automatically option
Manual Selection Create a maintenance transaction in the Maintenance Optimizer and choose the Select Files Manually option You then can select the files manually using the SP Stack application in SAP Service Marketplace
NOTE
You have to download the stack configuration file manually after you have selected all files in the SP Stack
httphelpsapcom SAP Solutions SAP Solution Manager
SAP Solution Manager 70 EHP1 ltSPgtChange Request Management and
Change Control Maintenance Optimizer Maintenance Procedure Scenarios
For information about the automatic calculation see Maintenance Transaction with Installation of an Enhancement PackageFor information about the manual selection and approval process see section Approve and Download Files in Download Basket
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
3056 PUBLIC 2011-04-15
Implementation PhaseStep Description Documentation
application Choose Generate Stack XML and save the file
4Enhancement Package Installation
Run Software Update Manager to update your system with the selected software packages
Update Guide ndash Update of SAP Systems with Software Update Manager
5Follow-Up Steps
Perform technical and PI-specific follow-up activities after the enhancement package installation is done
Update Guide ndash Update of SAP Systems with Software Update Manager section Follow-Up Activities
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
6Configuration
Configure newly installed enhancement package functions using SAP Solution Manager content
See Systems with Usage Types [page 16] section Configuration of Systems with Usage Types
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 3156
This page is left blank for documents that are printed on both sides
5 System Landscape
51 Planning Your System Landscape
The installable software units that make up your system landscape depend on the functions that you
want to implement For information about the features see systems [page 16] standalone engines [page 19]
and clients [page 21]
In addition you have to determine the required shared services [page 35] (such as SAP Solution Manager
or SAP NetWeaver Administrator) that run on central systems in your system landscape and the
landscape aspects relevant for their implementation
In the following you will find general information that you should consider when planning your system
landscape
Sizing
You have to map systems and standalone engines to hosts after you have a clear picture of the following
Which systems and standalone engines you require
How many systems you require and how you want to use each of these systems
NOTE
No general guideline can be given for the sizing of your landscape since this relies heavily on your
requirements You should therefore perform this task together with your hardware partner and
your technical consultant
For information about sizing your systems you can use the following information sources
Your first point of reference is the Quick Sizer
SAP built the Quick Sizer as an online sizing questionnaire Internet application in close cooperation
with its hardware partners This tool delivers general sizing categories based on your volume load
estimates The results provide an objective basis for sizing independent of platform and
configuration
For more information see SAP Service Marketplace at
httpservicesapcomsizing for the SAP NetWeaver PI 71 sizing guide available under
Sizing Guidelines Business Suite amp Services
httpservicesapcomquicksizer for more information and access to the tool itself
Also consider the following important aspects concerning sizing
High availability
5 System Landscape
51 Planning Your System Landscape
2011-04-15 PUBLIC 3356
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Technical Infrastructure High Availability
Unicode
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Internationalization
Contact your hardware partner to find out the appropriate number of sized hosts
The platform-independent abstract results of the Quick Sizer can be used by any of our hardware
partners to create a concrete offer SAP itself does not make any hardware recommendations the
responsibility for sizing and detailed hardware configuration lies with the hardware partners
Figure 6 Example of Mapping of Systems and Standalone Engines to Three Hosts
NOTE
Optionally you could also distribute single systems to multiple hosts For example you could
decide to install the database instance of an SAP system on a separate host for performance
reasons or distribute other system instances to achieve high availability
To provide a mapping that fits your required functions and performance your hardware partner
and your technical consultant have to identify the number of required instances of SAP NetWeaver
find out how to distribute these instances to hosts and what functions will run on which instance
Therefore the hardware partner and the technical consultant have to consider many different
aspects such as
Number of required SAPS (SAP Application Benchmark Performance Standard) for each
system (provided by Quick Sizer)
Landscape-relevant aspects concerning security For more information see the SAP Security
Guide in the SAP Library [page 12] at Administratoracutes Guide Security Guide
Landscape-relevant aspects concerning scalability high availability operation and software
life-cycle management
5 System Landscape
51 Planning Your System Landscape
3456 PUBLIC 2011-04-15
For more information about relevant aspects for the mapping of systems to hosts see the document
Technical Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
Scaling and Distribution Options
You may need to design your system landscape for a large number of users SAP NetWeaver PI offers
you different means of scalability The following list provides you with some examples
You could install multiple systems of one type and use them for different purposes
You could scale every system by installing dialog instances or by distributing the database instance
For more information about distribution options on the instance level see the Technical
Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
For every SAP system you could additionally install Web Dispatcher For more information see
the SAP Library [page 12] at FunctionndashOriented View Application Server Infrastructure SAP Web
Dispatcher
You could further distribute certain standalone engines ndash for example Search and Classification
(TREX) is based on a flexible architecture that supports a distributed installation For more
information see the Technical Infrastructure Guide ndash SAP NetWeaver PI 71 available in SAP Service
Marketplace at httpservicesapcominstallNWPI71
52 Shared Services
You normally run shared services on central systems in your system landscape The following features
could be used for SAP NetWeaver Process Integration to realize shared services
SAP Solution Manager
Used to implement train test maintain monitor control change and manage incidents of your
SAP solution system landscape (open end-to-end application management)
As of SAP Solution Manager (70) 40 Support Package 15 SAP Solution Manager has become the
platform for SAPs end-to-end solution operations strategy Functions for complete application
management has been combined with administrative tools and has been merged in newly created
role based work centers
NOTE
Be aware that you require an SAP Solution Manager system to install or upgrade to SAP
NetWeaver 70 and higher An SAP Solution Manager system is required to generate the SAP
Solution Manager key needed during the installation or upgrade process Without this key
the installation or upgrade process cannot continue
For SAP NetWeaver Process Integration you require SAP Solution Manager 70
For more information see SAP Note 805390
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3556
Solution Manager Diagnostics
An integral part of SAP Solution Manager that is running as a Java application on the Java stack of
SAP Solution Manager 70 Solution Manager Diagnostics is used to analyze the root cause of
incidents in your landscape in an efficient and safe way Before Go-Live Solution Manager
Diagnostics has to be set up and made accessible remotely
SAP NetWeaver Administrator
SAP NetWeaver Administrator is the central administration component which is used for
monitoring and administering Java applications It is included in SAP NetWeaver systems with AS
Java
SAP NetWeaver Administrator exists in the following flavors
A local mode which runs out of the box and which focuses on administrating the underlying
SAP NetWeaver AS Java
NOTE
For a SAP NetWeaver PI 71 it has a special role which you need to activate using a
configuation wizard
A central mode which has to be configured before use and which deals with the system
landscape management
SAP has decided to merge the central mode of SAP NetWeaver Administrator into the new work
centers available as of SAP Solution Manager 70 SP 15 Thus it can be used in an administrative
context together with non-Java-based administration tools Although the central mode of SAP
NetWeaver Administrator will be still available for some time SAP will not develop this tool any
further SAP focuses on optimizing the administrative work centers of SAP Solution Manager
instead
The local mode of SAP NetWeaver Administrator stays untouched It is available for current and
future releases of SAP NetWeaver
SAP Central Process Scheduling by Redwood
SAP Central Process Scheduling application by Redwood enables central job scheduling and job
monitoring of current and old releases of AS ABAP systems (as of Basis Release 31) This application
is fully integrated in SAP NetWeaver Depending on the business needs SAP business applications
are the initial trigger for scheduled activities You can now manage jobs and job chains conveniently
using a graphical user interface
System Landscape Directory
The System Landscape Directory is the central directory of system landscape information relevant
for the management of your software life-cycle It contains a description of your system landscape
(that is software components that are currently installed) and a repository of software components
that can theoretically be installed in your landscape (such as the software components available
from SAP)
Adaptive Computing Controller
5 System Landscape
52 Shared Services
3656 PUBLIC 2011-04-15
The Adaptive Computing Controller enables users to control an adaptive computing landscape
from a single point through observation operation and dynamic resource distribution With
adaptive computing hardware software and system services are able to adapt to changing business
needs In the Adaptive Computing Controller the run-time data of logical and physical landscapes
can be monitored application services can be startedstoppedrelocated and hardware resources
can be assigned to application services The operation can also be mass executed and be planned as
tasks to be executed
For more information about the installation of the Adaptive Computing Controller tool see the
document Installation Guide ndash Adaptive Computing Controller in SAP NetWeaver 71 available on SAP Service
Marketplace at httpservicesapcominstallNWPI71
For more information about Adaptive Computing in general see httpsdnsapcomirj
sdnadaptive
521 Use Cases
You can use the applications and tools described above for use cases that are normally performed
centrally The following sections describe these use cases
5211 End-to-End Solution Operations
Running business applications through their complete life-cycle is a challenge Therefore SAP has
started the Run SAP methodology for implementing End-to-End Solution Operations Based on a set
of SAP standards a roadmap and a package for training and certification Run SAP helps customers to
facilitate End-to-End Solution Operations
You can download the SAP standards for Solution Operations from SAP Service Marketplace at http
servicesapcomsupportstandards They describe roles customers typically have in their IT
environment For optimal role support SAP has grouped existing and new functions in SAP Solution
Manager work centers as of SAP Solution Manager 70 Support Package 15 Operations aspects are fully
covered by adding administrative functions for SAP NetWeaver as well Work centers are ABAP Web
Dynpro-based applications They offer the following advantages
Easy to use similar look and feel
Context transfer while jumping from one work center into another
Logical grouping of tools for a certain area
Simple authorization concept
Easy to expand
Each IT role belongs to one or more work centers For instance the Technical Administrator IT role is
covered by the work centers for System Monitoring System Administration and Landscape Management
The following work centers are available
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3756
Business Process Operations
Change Management
Root Cause Analysis
Implementation Upgrade
Incident Management
Test Management
Job Management
System Landscape Management
Solution Documentation Assistant
SAP Engagement and Service Delivery
SAP Solution Manager Administration
System Administration
System Monitoring
My Home is the central point of access to all important data of almost all work centers in SAP Solution
Manager
5212 Support Infrastructure
A key requirement for effective support of IT solutions is the ability to perform root cause analysis with
speed and efficiency
With SAP Solution Manager SAP has long had an infrastructure in place for its ABAP applications that
efficiently supports SAP solutions This helps ensure the high availability and smooth running of
business processes For more information see the SAP Solution Manager section
With Solution Manager Diagnostics this knowledge has been extended to Java applications If for
example homegrown Java applications cause instability Solution Manager Diagnostics helps trace the
cause to eradicate the problem rapidly Solution Manager Diagnostics is fully integrated into SAP
Solution Manager 70 Solution Manager Diagnostics also contains two third-party tools CArsquos Wily
Introscopereg for measuring performance as well as troubleshooting problems of the Java EE Engine
and applications running on it and Mercury Loadrunnerreg which enables SAP Support to produce a
defined load in the SAP solution landscape remotely For more information see Solution Manager
Diagnostics [page 43]
The support infrastructure provides SAP Support with safe access to your productive landscape for safe
root cause analysis so ensuring that SAP Support does not change your landscape inadvertently You
require a support infrastructure to run SAP NetWeaver
The following figure shows the overall infrastructure including SAP NetWeaver administration tools
that are used by administrators or operators at the customer site
5 System Landscape
52 Shared Services
3856 PUBLIC 2011-04-15
Landscape Aspects
If you use SAP NetWeaver Process Integration 71 productively besides SAP Solution Manager (as a
central support platform) you have to set up Solution Manager Diagnostics for supportability reasons
Implementation Sequence
For information about the implementation of the support infrastructure see the document Master
Guide ndash SAP Solution Manager 70 available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution Manager ltReleasegt
5213 Collection of Landscape Data
Amongst other applications and services the support infrastructure and the SAP NetWeaver
administration tools rely on system landscape data
For SAP NetWeaver PI 71 you have to run non-ABAP components in your solution landscape
Therefore the System Landscape Directory is mandatory The landscape data that is automatically
gathered by the System Landscape Directory is replicated to SAP Solution Manager There are several
topology options for the System Landscape Directory They offer different grades of availability
administration and operation effort
For more information see the System Landscape Directory section
5214 Authentication and Single Sign-On
Before implementing your system landscape plan how to implement authentication and how to
integrate different systems into a Single Sign-On landscape Single Sign-On reduces complexity for end
users saving them valuable time while also reducing administration effort for resetting passwords
thereby contributing to TCO reduction
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
5215 Integrated User and Access Management
In a system landscape containing a combination of ABAP and Java components we recommend that
you integrate your user and access management so that you can use the same user data across different
systems administer this data centrally and control access to data SAPs mature fine-grained
authorization concept allows detailed control of access rights SAP NetWeaver provides both ABAP and
Java-based user management solutions The user management solution that you use to administer
your user data depends on factors such as the type of systems that are running in your landscape
If you want to use central user administration we recommend that you run it in a non-production
system If you do not have a central user administration yet you can for example realize it in the SAP
Solution Manager system
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3956
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
522 Examples for the Overall System Landscape of Shared Services
In this section we provide examples of how shared services can be set up depending on the system
landscape they are intended for The following examples aggregate the landscape aspects given in the
Use Cases section
NOTE
The following sections and the figure mostly do not show information about the life-cycle of
shared services For example you may also need a development and testquality assurance system
for SAP Solution Manager You should consider this aspect in addition to the information given
in this section based on your requirements
Small and MediumndashSized Customer Landscapes with Java
As you use Java productively for SAP NetWeaver PI 71 besides SAP Solution Manager you have to set
up additional components for optimal monitoring administration and support Solution Manager
Diagnostics and the central mode of SAP NetWeaver Administrator are already fully integrated into
SAP Solution Manager 70 as the central operations hub For SAP Process Integration you must also
set up SAP NetWeaver Administrator with a special role
We recommend that you do not install SAP Central Process Scheduling in the SAP Solution Manager
system You have to set up and operate the system which hosts your productive scheduler as a mission
critical system
In the SAP Solution Manager system you should set up a local System Landscape Directory in addition
to a central runtime System Landscape Directory This way you have a clear separation between your
management system (SAP Solution Manager) and managed systems in your landscape In addition
SAP Solution Manager then does not rely on a System Landscape Directory running in the production
environment For this setup configure the SLD data suppliers of your SAP Solution Manager system
to send data to the central runtime System Landscape Directory In addition configure automatic
bridge forwarding from your runtime System Landscape Directory to the local System Landscape
Directory For more information see the Planning Guide - System Landscape Directory
If you want to use a central system for Adobe Document Services we recommend that you install a
dedicated system for this purpose in your production environment For detailed information about
the sizing of the system for the different use cases see the Sizing Guide for Adobe Document Services at
SAP Service Marketplace at httpservicesapcomsizing Sizing Guidelines Solutions amp
Platform
We recommend that you start with this centralized SAP Solution Manager approach as depicted in the
following figure
5 System Landscape
52 Shared Services
4056 PUBLIC 2011-04-15
Figure 7 Single SAP Solution Manager Landscape
Large Customer Landscapes with Java
Large customers who have environments in their landscape that are large and distributed administered
by different groups or separated for security reasons can consider a distributed operations setup In
addition to the centralized setup described for small- and medium-sized customers above large
customers can put parts of the central management functions on extra hosts or systems for performance
or policy reasons You have the following options for a distributed setup
You may set up an extra system or client for Central User Administration (CUA)
The Change and Transport System (CTS) can run on an extra system However it is not
performance- or data-intensive
You may set up an extra system for central CCMS monitoring Depending on the customizing
and on the landscape size central CCMS may generate a lot of system load You can connect a
separate central CCMS to SAP Solution Manager for displaying alerts in the alert inbox of the System
Monitoring work center
You can use a separate SAP NetWeaver 70 system with usage type BI together with SAP Solution
Manager This may make sense with respect to the amount of landscape management data that is
stored for reporting purposes The amount of data strongly depends on the data granularity
storage time frame and landscape size
You can easily put Wily Introscope Enterprise Manager on an separate host
Other aspects described above for small- and medium-customers (such as the setup of the System
Landscape Directory) are also valid for large customers
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4156
523 Feature Details
This section provides further information about the features described above
5231 SAP Solution Manager
SAP provides you with SAP Solution Manager as the strategic application management platform and
to enable the collaboration between you and SAP You need to install at least one productive SAP
Solution Manager in your system landscape To ensure the availability of this application management
platform an SAP Solution Manager system is technically required to install or upgrade to SAP
NetWeaver 70 or higher If you are already using SAP Solution Manager you can also use it to manage
the solution you build with SAP NetWeaver In this case we highly recommend that you update SAP
Solution Manager to the latest version
As of SAP Solution Manager 70 SP15 you can use the newly created work centers
NOTE
During the SAP system installation or upgrade process you are prompted to enter the SAP
Solution Manager key An SAP Solution Manager system is required to generate this key Without
this key the installation or upgrade process cannot continue
You may generate all needed keys for your entire system landscape (development quality
assurance and production system) in one SAP Solution Manager system In case you plan to install
several solution landscapes (for example in different countries) one SAP Solution Manager
system is still sufficient
For more information see SAP Note 805390
It is possible to install multiple SAP Solution Managers If you do so they should host separate business
solutions
If you want to reduce the risk of unavailability you should not install SAP Solution Manager as a central
component Instead you can operate a 2-system-landscape with both a test and production
environment of SAP Solution Manager (especially if you are using time-critical functions like Support
Desk) If you also develop your own content a 3-system-landscape with a development test and
production environment is recommended
For more information about SAP Solution Manager see the following table
Topic Where to Find More Information
System infrastructure scenarios installation and configuration of SAP Solution Manager
Master Guide ndash SAP Solution Manager available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution ManagerltReleasegt
Benefits and usage scenarios SAP Solution Manager ndash Learning Maps available on SAP Service Marketplace at http
5 System Landscape
52 Shared Services
4256 PUBLIC 2011-04-15
Topic Where to Find More Informationservicesapcomrkt-solman or https
servicesapcomsolutionmanager
Additional information See SAP Service Marketplace at http
servicesapcomsolutionmanager
5232 Solution Manager Diagnostics
Solution Manager Diagnostics provides efficient and safe root-cause analysis of incidents in customer
solutions powered by SAP NetWeaver It can help monitor on operating systems databases Java
application activities performance and logs It also supports the reporting of software and
configuration changes that can lead to malfunctions and errors
You must run one Solution Manager Diagnostics within your SAP solution landscape if you run
applications based on SAP NetWeaver systems with usage type AS Java Agents are responsible for
delivering the data from all productive hosts within your system landscape to the Solution Manager
Diagnostics system
CAUTION
SAP Support performs root-cause analysis on incoming incidents with Solution Manager
Diagnostics Not installing and configuring this support infrastructure results in a dramatically
reduced service level
Solution Manager Diagnostics is fully integrated into SAP Solution Manager 70
Solution Manager Diagnostics also contains Wily Introscope (Display Server and Agent part) for
measuring performance as well as to troubleshoot problems of Non-ABAP applications Wily Introscope
is heavily used for troubleshooting applications running on AS Java
SAP has signed a distribution agreement for Wily Introscope SAP customers are allowed to use this
tool in a preconfigured way
For more information about Solution Manager Diagnostics and an FAQ list see SAP Service Marketplace
at httpservicesapcomdiagnostics
5233 System Landscape Directory
The System Landscape Directory (SLD) of SAP NetWeaver is the central directory of system landscape
information relevant for the management of your software life-cycle
NOTE
Note that the abbreviation SLD is not intended to define a product since the System Landscape
Directory is part of SAP NetWeaver This abbreviation is solely intended to improve readability
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4356
The System Landscape Directory contains a description of your system landscape (that is software
components that are currently installed) and a repository of software components that can
theoretically be installed in your landscape (such as the software components available from SAP)
Since this data gets updated automatically the System Landscape Directory provides reliable and up-
to-date system landscape information with as little effort for you as possible In this way the System
Landscape Directory acts as a central information provider for SAP and third-party tools that use this
data to deliver the services you need to keep your landscape up and running
For the System Landscape Directory as part of an SAP NetWeaver PI 71 landscape consider the following
aspects
Part of SAP NetWeaver PI 71 is a new version of the System Landscape Directory It is automatically
included in every SAP NetWeaver 71 system with usage type AS Java It offers enhanced functions
such as a full automatic synchronization mechanism for all data stored in it That is both data
delivered by data suppliers and data entered or changed manually in the System Landscape
Directory can be synchronized automatically This synchronization offers the following
A fully automated mechanism so no user interaction is required and conflicts are resolved
automatically
Asynchronous propagation of information so some nodes may be down temporarily
Communication over HTTP protocol
Uni- and bi-directional synchronization
Depending on your use case the full automatic synchronization could significantly reduce manual
synchronization effort
For SAP NetWeaver PI 71 the configuration of the system landscape directory and its data suppliers
is already included in the standard implementation procedure with SAPinst For existing systems
you only have to perform some quick and easy configuration actions to start operating the system
landscape directory server in an AS Java system
For SAP NetWeaver PI 71 you have the following options concerning SLD
Option 1
Run SAP NetWeaver PI 71 against an existing SLD running on SAP NetWeaver 70 We only
recommend this for upgrades from SAP NetWeaver 70 if you have a central SLD in operation
not running on one of your PI systems
Option 2
Use the SLD included in an SAP NetWeaver PI 71 system We recommend this option for new
installations and upgrades from older releases than SAP NetWeaver 70 due to the enhanced
functions and improved performance of SLD 71
NOTE
If you already have a central SLD running on SAP NetWeaver 70 in operation you could run
two SLD versions in parallel ndash SLD running on SAP NetWeaver 71 for your PI systems and
SLD running on SAP NetWeaver 70 for all other systemsuse cases This way your SAP
5 System Landscape
52 Shared Services
4456 PUBLIC 2011-04-15
NetWeaver PI 71 systems would benefit from the new features while it would be easy to set
up and operate such an SLD landscape For this purpose you could use the new fully
automatic synchronization This feature enables the automatic forwarding of all SLD data
from an SLD running on SAP NetWeaver 70 to an SLD running on SAP NetWeaver 71 As a
result there is no need to adapt most existing systems as their SLD data suppliers could still
send their data to the central SLD In brief the following steps would be required
1 Put SLD in a PI system into operation (part of standard implementation procedure)
2 Configure PI systems to use the new SLD (part of standard implementation procedure
for new PI systems)
3 Set up the fully automatic synchronization from your old SLD to your new SLD
As soon as an upgrade or an installation of a standalone AS Java 71 system is available you
could move your central SLD also to SAP NetWeaver 71 Then you could optionally shift
your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems
Figure 8
We recommend that you use a Domain Name System (DNS) alias so that you are able to switch to
another System Landscape Directory easily For example if customers build a new landscape they
normally start with a sandbox environment Over time more and more environments are set up
Once the production environment is in place move the System Landscape Directory there To do
this you can configure a new System Landscape Directory in the production environment
synchronize it with the old System Landscape directory and switch to the new one
Topology
Apart from the considerations above the System Landscape Directory offers several topology options
with different grades of availability at the expense of low administration and operation effort There is
no generic rule therefore on how to set up a System Landscape Directory in your system landscape
To find the topology and synchronization strategy for the System Landscape Directory that fits your
requirements concerning the System Landscape Directory availability (and hence the availability of
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4556
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
SAP GUI for Java 710 (or higher) with the latest revision
The integrated SAP ITS 710
For more information about the SAP GUI family see SAP Service Marketplace at http
servicesapcomsapgui
SAP offers three different client applications for accessing ABAP applications in SAP systems (such as
SAP NetWeaver systems with usage type AS ABAP) This SAP GUI family consists of
SAP GUI for HTML
SAP GUI for HTML is based on the SAP integrated Internet Transaction Server (ITS) which is
included in the installation of SAP NetWeaver systems as of SAP NetWeaver 2004 On the client
side only a suitable browser (such as Internet Explorer 70 or Firefox 20) and a virtual machine are
required SAP ITS 620 is not compatible with SAP NetWeaver 71
SAP GUI for the Java environment (SAP GUI for Java)
SAP GUI for Java is a generic SAP GUI that covers a variety of platforms
For more information about the installation of SAP GUI for Java see the documentation Installation
Guide ndash SAP Front End
SAP GUI for the Windows environment (SAP GUI for Windows)
SAP GUI for Windows is SAPs universal client for accessing all SAP applications built on ABAP
technology It is available on the Microsoft Windows platform only and offers the broadest feature
set of all members of the SAP GUI family
For more information about the installation of SAP GUI for Windows see the Installation Guide ndash
SAP Front End
SAP NetWeaver Developer Studio
The SAP NetWeaver Developer Studio is SAPrsquos Integrated Development Environment (IDE) for Java
and is based on the open-source tools framework Eclipse 33 With the SAP NetWeaver Developer Studio
you can develop Java EE 5 applications from scratch using the built-in support for new technologies
such as EJB 30 and JSF 12
During the installation of the SAP NetWeaver Developer Studio several features are offered for
installation For SAP NetWeaver PI 71 only the following features are relevant
SAP NetWeaver Developer Studio Platform
SAP NetWeaver Developer Studio Java EE
NOTE
If you want to use one of the other features you need SAP NetWeaver Composition Environment
and a corresponding developers licence
For more information about the installation of SAP NetWeaver Developer Studio see the Installation
Guide ndash SAP NetWeaver Developer Studio 71 or Installation Guide ndash SAP NetWeaver Developer Studio 71 Including
Enhancement Package 1
3 SAP NetWeaver PI Overview
31 Installable Software Units
2256 PUBLIC 2011-04-15
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
SAP enhancement packages are a new way of delivering new functions for SAP NetWeaver This allows
a clear separation between the delivery of new functions on the one hand and corrections legal changes
and security updates on the other hand (in Support Package stacks) SAP enhancement packages are
cumulative an enhancement package always contains the functions of the corresponding predecessor
enhancement packages
Enhancement packages are maintained by their own Support Packages while the main release is in
maintenance
Benefits
SAP enhancement packages offer the following benefits
You have reduced effort for testing and no effort for training when applying Support Packages as
new features are only shipped with enhancement packages
Adding new functions between releases becomes predictable and controllable
New functions can be added successively in small steps There is no need to fully upgrade your
system to get new functions
You have minimal training effort when applying an enhancement package because existing
functions are not replaced
Implementation
There are the following ways to get an SAP NetWeaver system with the release level of SAP enhancement
package 1 for SAP NetWeaver Process Integration 71
New installation of SAP NetWeaver PI 71 including enhancement package 1 using the standard
installation tool SAPinst
Upgrade of an existing SAP NetWeaver system from a release lower than SAP NetWeaver PI 71 to
SAP NetWeaver PI 71 including enhancement package 1 For this you use the upgrade programs
SAPup (for ABAP) and SAPJup (for Java)
Installation of the enhancement package on an existing SAP NetWeaver PI 71 system
For this you use the Software Update Manager (SUM) The Software Update Manager evolved
from the previously used SAP Enhancement Package Installer The tool has been renamed to reflect
its broader use for example you can also use it for applying Support Package Stacks to your system
On the ABAP side the Software Update Manager uses a system cloning and switch procedure for
installing enhancement packages It installs a copy of the system the shadow system parallel to
the original system This shadow system is used to update the relevant software components and
to install the additional components while the original system is still in production operation At
a certain point during downtime the switch to the new system is made and afterwards any parts
of the original system that are no longer needed are deleted The enhancement package installation
in a Java system uses a deploy-based procedure that is no shadow system is used The Software
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2011-04-15 PUBLIC 2356
Update Manager requires a stack configuration file (xml file) as input file for the enhancement
package installation procedure This file lists all the packages that are to be installed in your systems
The stack configuration file is generated when you download the required packages
As the Software Update Manager is updated regularly we recommend to always use the latest
version It is delivered as part of the SL toolset For more information see http
servicesapcomsltoolset
For an overview of all required steps for the enhancement package installation process and
corresponding documents see Process Overview Installation of Enhancement Package 1 on an Existing SAP
Netweaver PI 71 System [page 28]
Content of SAP Enhancement Package 1 for SAP NetWeaver PI 71
With enhancement package 1 for SAP NetWeaver PI 71 new features are introduced and some existing
are changed The following is a selection of some of the most important enhancements
Enhanced design and modelling options in the Enterprise Services Repository
New services registry
Support for new Web services standard (Web Services Reliable Messaging)
New modules for the Advanced Adapter Engine
Use of shared memory of the ABAP Application Server for message processing
For more information about the changes see SAP Library [page 12] at Whatacutes new in SAP NetWeaver PI 71
ndash Release Notes
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2456 PUBLIC 2011-04-15
4 SOA-Based Integration Use Case
41 Overview
You can use SOA-based integration to set up the communication between service providers and service
consumers in both application-to-application and business-to-business scenarios and to execute
operate and monitor the communication at runtime SOA-based integration covers both direct (point-
to-point) as well as mediated (via an Integration Server) communication between service providers and
service consumers
The use case spans the whole life cycle of a SOA-based integration scenario including
Scenario modeling and service design in the Enterprise Services Repository
Implementation of the service provider and consumer in the back-end systems
Configuration and finally execution monitoring and operation of the integration scenario
For scenarios using Integration Server or broker-based communication the configuration of the
different connectivity options (for example SOAP RFC Web Services Industry standards and JDBC)
and their enhancements is covered
For more information see the following documents
Service-Enabling with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdnsoa-modeling
Getting Started
Service-Enabling a Legacy Application with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdn
soa-servicebus Getting Started
In the following you will find information about the installation of the involved software units
42 System Landscape
The following figure shows the system landscape for this use case
4 SOA-Based Integration Use Case
41 Overview
2011-04-15 PUBLIC 2556
Figure 5 SOA-Based Integration
It is mandatory to have a dedicated PI system This applies to development quality and production
landscapes
For PI it is a prerequisite that no other system in your system landscape has a higher release than
the PI system For exceptions to this rule see SAP Note 1043047 For example SAP XI 30 is compatible
with SAP NetWeaver 640 and 70 application systems since the same XI protocol is used Apart
from these exceptions if you want to upgrade or install an application in your system landscape
you first have to make sure that the PI system is on the same release level If required you have to
upgrade the PI system first to the new or a higher release
CAUTION
Although it should be technically possible to run an application system with a higher release
than your PI system in your system landscape this is not supported by SAP (apart from the
exceptions listed in SAP Note 1043047) Therefore you run such a landscape at your own risk
You can use the Advanced Adapter Engine that is part of your PI system as a central Advanced
Adapter Engine
Adapter Engine (Java SE) can be installed in a non-SAP Java environment However it only hosts
a subset of the adapter functionality is only supported for compatibility reasons and should be
used only if this is a precondition in your environment
Optionally you can use the Change Management Service (CMS) of an SAP NetWeaver 70 system
with usage type DI to transport design objects and repository objects For more information see
the SAP Library [page 12] at Administratoracutes Guide Technical Operations for SAP NetWeaver Administration
of SAP NetWeaver Systems PI (Process Integration) Software Logistics Transporting ESR Content and Objects
of Integration Directory PI Transports Using the Change Management Service (CMS)
Smaller business partners or subsidiaries that do not run SAP NetWeaver install SAP Partner
Connectivity Kit in their system landscape SAP Partner Connectivity Kit enables XML document
4 SOA-Based Integration Use Case
42 System Landscape
2656 PUBLIC 2011-04-15
exchange between your SAP NetWeaver systems and the partner systems Since SAP Partner
Connectivity Kit gets installed in their system landscape it is not shown in the system landscape
figure above
The AS ABAP system acts as an application and service provider For Java Web Services you also
require AS Java In addition you require SAP NetWeaver Developer Studio on the client side as a
development environment
The Web service client can be either an SAP or a non-SAP application For example an AS ABAP
system or a Web browser could act as application or service consumer
You can install SAP Conversion Agent by Informatica in the system with usage type PI or on a host
where SAP Partner Connectivity Kit is installed or on a host where neither usage type PI nor SAP
Partner Connectivity Kit is installed
43 Implementation Sequence
Procedure
To install this use case perform the steps listed in the following table
StepAction[Corresponding Documentation] Remarks
1 Make sure that you have performed the preparation steps You have planned your system landscape [page 33]
(that is you have decided how many systems you require how you want to use each of these systems and which standalone engines and clients you require)
With the help of your hardware partner you have mapped your systems and standalone engines to properly sized hosts
You have planned and installed shared services [page 35]
2 Installation of system with usage type PI (includes the installation of AS ABAP and AS Java)
NOTE
For usage type PI a Unicode installation is mandatory
[Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt]
If you want to use the features of enhancement package 1 use the direct installation of SAP NetWeaver PI 71 including enhancement package 1
Make sure that you perform the configuration steps as described in the installation guide For certain usage types configuration tasks can be applied by the configuration wizard These configuration tasks as well as any additional configuration steps for your use case are listed in SAP Solution Manager For more information
4 SOA-Based Integration Use Case
43 Implementation Sequence
2011-04-15 PUBLIC 2756
StepAction[Corresponding Documentation] Remarks
see the Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt
3 Install the Adapter Engine (Java SE) engines if required[Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
4 To integrate small business partners and subsidiaries the business partners or subsidiaries install SAP Partner Connectivity Kit running on AS Java with parts of usage type PI in the business partners or subsidiarys system landscape[Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
5 Install SAP Conversion Agent by Informatica if required[SAP Library [page 12] at Function-Oriented View Process Integration SAP Conversion Agent by Informatica Deploying and Using Conversion Agent ]
6 Installation of clients SAP GUI
[Installation Guide ndash SAP Front End]
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
The process sequences give a comprehensive overview of the steps relevant for the enhancement
package installation on an existing SAP NetWeaver PI 71 system
The process sequence is divided into a planning phase and an implementation phase Each step in both
phases contains references to the corresponding documentation to ensure that you can easily find the
information you need
Process
NOTE
To download the enhancement package files and required Support Packages you require the SAP
Solution Manager Maintenance Optimizer You have the following options
Manual Selection
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2856 PUBLIC 2011-04-15
You manually select the required files from SAP Service Marketplace at http
servicesapcomswdc using the SP Stack Application You use the Maintenance Optimize
only to approve the packages which is a prerequisite for the download
Automatic Calculation
The Maintenance Optimizer supports the download of a consistent queue that includes all
necessary Support Packages and enhancement packages In addition SAP Solution Manager
calculates a valid import queue for the selected SAP system and generates the enhancement
package stack configuration file that you require for the installation
As a prerequisite the system that you want to update needs to be maintained correctly in
SAP Solution Manager System Landscape As the Maintenance Optimizer uses this data for
the calculation it is crucial that the data is up-to-date In addition the SAP Solution Manager
system requires a Minimum Support Package level (see below)
Planing PhaseStep Description Documentation
Hardware amp Software Prerequisites
Check which platforms are supported for your target release (OSDB dependencies)
Product Availability Matrix (PAM) at httpservicesapcompam
Check which hardware sizing is required for your target release
Sizing information at httpservicesapcomsizing
Solution Manager Prerequisites
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of the required software packages you have to make sure that your SAP Solution Manager system has the required Support Package levelAt least SAP Solution Manager 70 EHP1 Support Package Stack 17 is required We recommend to use SAP Solution Manager 70 EHP1 Support Package Stack 23Check if you need to do an update or upgrade of your SAP Solution ManagerMake sure that you run the guided procedure SOLMAN_SETUP after every installation or update of SAP Solution Manager and that it completes successfully
For upgrades from source release SAP Solution Manager 31 and 32Upgrade Guide ndash SAP Solution Manager 70 incl Enhancement Package 1For updates from SAP Solution Manager 70Update Guide SAP Enhancement Package 1 for SAP Solution Manager 70Follow-up activities after an Support Package Stack update or enhancement package updateSolution Operations Guide ndash SAP Solution Manager 70 EHP1 section Software Change Management All guides are available at http
servicesapcom instguides SAP Components SAP Solution Manager -gt Release 70 EHP 1
Implementation PhaseStep Description Documentation
1Solution Manager Preparation
Configure the SAP Solution Manager Maintenance Optimizer
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of software packages make sure your
Configuration of Maintenance Optimizer http
helpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Change Request Management and Change ControlMaintenance Optimizer
Prerequisites
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 2956
Implementation PhaseStep Description Documentation
system landscape data in SAP Solution Manager is maintained correctlyLandscape Verification 10 which is an add-on to SAP Solution Manager can support you in maintaining your system landscape data The use of this tool is optional
Landscape Verification http
wwwsdnsapcom irj
sdn alm-update-
management link Landscape Verification under Related Areas on Upgrade and Update Management (in the right column)
SAP Note 1468605 (Installation of Landscape Verification)
Maintaining System Landscape Information [page 47]Note that the information provided in this section is based on SAP Solution Manager 70 EHP1 SP23
2System Preparation
Prepare your system as described in the documentation for example perform OS DB specific preparations and the PI-specific preparations
Update Guide ndash Update of SAP Systems with Software Update Manager sections Planning and Preparation
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
3Software Download
Select and download the software packages in either of the following ways Automatic calculation Create
a maintenance transaction in the Maintenance Optimizer and choose the Calculate Files Automatically option
Manual Selection Create a maintenance transaction in the Maintenance Optimizer and choose the Select Files Manually option You then can select the files manually using the SP Stack application in SAP Service Marketplace
NOTE
You have to download the stack configuration file manually after you have selected all files in the SP Stack
httphelpsapcom SAP Solutions SAP Solution Manager
SAP Solution Manager 70 EHP1 ltSPgtChange Request Management and
Change Control Maintenance Optimizer Maintenance Procedure Scenarios
For information about the automatic calculation see Maintenance Transaction with Installation of an Enhancement PackageFor information about the manual selection and approval process see section Approve and Download Files in Download Basket
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
3056 PUBLIC 2011-04-15
Implementation PhaseStep Description Documentation
application Choose Generate Stack XML and save the file
4Enhancement Package Installation
Run Software Update Manager to update your system with the selected software packages
Update Guide ndash Update of SAP Systems with Software Update Manager
5Follow-Up Steps
Perform technical and PI-specific follow-up activities after the enhancement package installation is done
Update Guide ndash Update of SAP Systems with Software Update Manager section Follow-Up Activities
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
6Configuration
Configure newly installed enhancement package functions using SAP Solution Manager content
See Systems with Usage Types [page 16] section Configuration of Systems with Usage Types
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 3156
This page is left blank for documents that are printed on both sides
5 System Landscape
51 Planning Your System Landscape
The installable software units that make up your system landscape depend on the functions that you
want to implement For information about the features see systems [page 16] standalone engines [page 19]
and clients [page 21]
In addition you have to determine the required shared services [page 35] (such as SAP Solution Manager
or SAP NetWeaver Administrator) that run on central systems in your system landscape and the
landscape aspects relevant for their implementation
In the following you will find general information that you should consider when planning your system
landscape
Sizing
You have to map systems and standalone engines to hosts after you have a clear picture of the following
Which systems and standalone engines you require
How many systems you require and how you want to use each of these systems
NOTE
No general guideline can be given for the sizing of your landscape since this relies heavily on your
requirements You should therefore perform this task together with your hardware partner and
your technical consultant
For information about sizing your systems you can use the following information sources
Your first point of reference is the Quick Sizer
SAP built the Quick Sizer as an online sizing questionnaire Internet application in close cooperation
with its hardware partners This tool delivers general sizing categories based on your volume load
estimates The results provide an objective basis for sizing independent of platform and
configuration
For more information see SAP Service Marketplace at
httpservicesapcomsizing for the SAP NetWeaver PI 71 sizing guide available under
Sizing Guidelines Business Suite amp Services
httpservicesapcomquicksizer for more information and access to the tool itself
Also consider the following important aspects concerning sizing
High availability
5 System Landscape
51 Planning Your System Landscape
2011-04-15 PUBLIC 3356
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Technical Infrastructure High Availability
Unicode
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Internationalization
Contact your hardware partner to find out the appropriate number of sized hosts
The platform-independent abstract results of the Quick Sizer can be used by any of our hardware
partners to create a concrete offer SAP itself does not make any hardware recommendations the
responsibility for sizing and detailed hardware configuration lies with the hardware partners
Figure 6 Example of Mapping of Systems and Standalone Engines to Three Hosts
NOTE
Optionally you could also distribute single systems to multiple hosts For example you could
decide to install the database instance of an SAP system on a separate host for performance
reasons or distribute other system instances to achieve high availability
To provide a mapping that fits your required functions and performance your hardware partner
and your technical consultant have to identify the number of required instances of SAP NetWeaver
find out how to distribute these instances to hosts and what functions will run on which instance
Therefore the hardware partner and the technical consultant have to consider many different
aspects such as
Number of required SAPS (SAP Application Benchmark Performance Standard) for each
system (provided by Quick Sizer)
Landscape-relevant aspects concerning security For more information see the SAP Security
Guide in the SAP Library [page 12] at Administratoracutes Guide Security Guide
Landscape-relevant aspects concerning scalability high availability operation and software
life-cycle management
5 System Landscape
51 Planning Your System Landscape
3456 PUBLIC 2011-04-15
For more information about relevant aspects for the mapping of systems to hosts see the document
Technical Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
Scaling and Distribution Options
You may need to design your system landscape for a large number of users SAP NetWeaver PI offers
you different means of scalability The following list provides you with some examples
You could install multiple systems of one type and use them for different purposes
You could scale every system by installing dialog instances or by distributing the database instance
For more information about distribution options on the instance level see the Technical
Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
For every SAP system you could additionally install Web Dispatcher For more information see
the SAP Library [page 12] at FunctionndashOriented View Application Server Infrastructure SAP Web
Dispatcher
You could further distribute certain standalone engines ndash for example Search and Classification
(TREX) is based on a flexible architecture that supports a distributed installation For more
information see the Technical Infrastructure Guide ndash SAP NetWeaver PI 71 available in SAP Service
Marketplace at httpservicesapcominstallNWPI71
52 Shared Services
You normally run shared services on central systems in your system landscape The following features
could be used for SAP NetWeaver Process Integration to realize shared services
SAP Solution Manager
Used to implement train test maintain monitor control change and manage incidents of your
SAP solution system landscape (open end-to-end application management)
As of SAP Solution Manager (70) 40 Support Package 15 SAP Solution Manager has become the
platform for SAPs end-to-end solution operations strategy Functions for complete application
management has been combined with administrative tools and has been merged in newly created
role based work centers
NOTE
Be aware that you require an SAP Solution Manager system to install or upgrade to SAP
NetWeaver 70 and higher An SAP Solution Manager system is required to generate the SAP
Solution Manager key needed during the installation or upgrade process Without this key
the installation or upgrade process cannot continue
For SAP NetWeaver Process Integration you require SAP Solution Manager 70
For more information see SAP Note 805390
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3556
Solution Manager Diagnostics
An integral part of SAP Solution Manager that is running as a Java application on the Java stack of
SAP Solution Manager 70 Solution Manager Diagnostics is used to analyze the root cause of
incidents in your landscape in an efficient and safe way Before Go-Live Solution Manager
Diagnostics has to be set up and made accessible remotely
SAP NetWeaver Administrator
SAP NetWeaver Administrator is the central administration component which is used for
monitoring and administering Java applications It is included in SAP NetWeaver systems with AS
Java
SAP NetWeaver Administrator exists in the following flavors
A local mode which runs out of the box and which focuses on administrating the underlying
SAP NetWeaver AS Java
NOTE
For a SAP NetWeaver PI 71 it has a special role which you need to activate using a
configuation wizard
A central mode which has to be configured before use and which deals with the system
landscape management
SAP has decided to merge the central mode of SAP NetWeaver Administrator into the new work
centers available as of SAP Solution Manager 70 SP 15 Thus it can be used in an administrative
context together with non-Java-based administration tools Although the central mode of SAP
NetWeaver Administrator will be still available for some time SAP will not develop this tool any
further SAP focuses on optimizing the administrative work centers of SAP Solution Manager
instead
The local mode of SAP NetWeaver Administrator stays untouched It is available for current and
future releases of SAP NetWeaver
SAP Central Process Scheduling by Redwood
SAP Central Process Scheduling application by Redwood enables central job scheduling and job
monitoring of current and old releases of AS ABAP systems (as of Basis Release 31) This application
is fully integrated in SAP NetWeaver Depending on the business needs SAP business applications
are the initial trigger for scheduled activities You can now manage jobs and job chains conveniently
using a graphical user interface
System Landscape Directory
The System Landscape Directory is the central directory of system landscape information relevant
for the management of your software life-cycle It contains a description of your system landscape
(that is software components that are currently installed) and a repository of software components
that can theoretically be installed in your landscape (such as the software components available
from SAP)
Adaptive Computing Controller
5 System Landscape
52 Shared Services
3656 PUBLIC 2011-04-15
The Adaptive Computing Controller enables users to control an adaptive computing landscape
from a single point through observation operation and dynamic resource distribution With
adaptive computing hardware software and system services are able to adapt to changing business
needs In the Adaptive Computing Controller the run-time data of logical and physical landscapes
can be monitored application services can be startedstoppedrelocated and hardware resources
can be assigned to application services The operation can also be mass executed and be planned as
tasks to be executed
For more information about the installation of the Adaptive Computing Controller tool see the
document Installation Guide ndash Adaptive Computing Controller in SAP NetWeaver 71 available on SAP Service
Marketplace at httpservicesapcominstallNWPI71
For more information about Adaptive Computing in general see httpsdnsapcomirj
sdnadaptive
521 Use Cases
You can use the applications and tools described above for use cases that are normally performed
centrally The following sections describe these use cases
5211 End-to-End Solution Operations
Running business applications through their complete life-cycle is a challenge Therefore SAP has
started the Run SAP methodology for implementing End-to-End Solution Operations Based on a set
of SAP standards a roadmap and a package for training and certification Run SAP helps customers to
facilitate End-to-End Solution Operations
You can download the SAP standards for Solution Operations from SAP Service Marketplace at http
servicesapcomsupportstandards They describe roles customers typically have in their IT
environment For optimal role support SAP has grouped existing and new functions in SAP Solution
Manager work centers as of SAP Solution Manager 70 Support Package 15 Operations aspects are fully
covered by adding administrative functions for SAP NetWeaver as well Work centers are ABAP Web
Dynpro-based applications They offer the following advantages
Easy to use similar look and feel
Context transfer while jumping from one work center into another
Logical grouping of tools for a certain area
Simple authorization concept
Easy to expand
Each IT role belongs to one or more work centers For instance the Technical Administrator IT role is
covered by the work centers for System Monitoring System Administration and Landscape Management
The following work centers are available
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3756
Business Process Operations
Change Management
Root Cause Analysis
Implementation Upgrade
Incident Management
Test Management
Job Management
System Landscape Management
Solution Documentation Assistant
SAP Engagement and Service Delivery
SAP Solution Manager Administration
System Administration
System Monitoring
My Home is the central point of access to all important data of almost all work centers in SAP Solution
Manager
5212 Support Infrastructure
A key requirement for effective support of IT solutions is the ability to perform root cause analysis with
speed and efficiency
With SAP Solution Manager SAP has long had an infrastructure in place for its ABAP applications that
efficiently supports SAP solutions This helps ensure the high availability and smooth running of
business processes For more information see the SAP Solution Manager section
With Solution Manager Diagnostics this knowledge has been extended to Java applications If for
example homegrown Java applications cause instability Solution Manager Diagnostics helps trace the
cause to eradicate the problem rapidly Solution Manager Diagnostics is fully integrated into SAP
Solution Manager 70 Solution Manager Diagnostics also contains two third-party tools CArsquos Wily
Introscopereg for measuring performance as well as troubleshooting problems of the Java EE Engine
and applications running on it and Mercury Loadrunnerreg which enables SAP Support to produce a
defined load in the SAP solution landscape remotely For more information see Solution Manager
Diagnostics [page 43]
The support infrastructure provides SAP Support with safe access to your productive landscape for safe
root cause analysis so ensuring that SAP Support does not change your landscape inadvertently You
require a support infrastructure to run SAP NetWeaver
The following figure shows the overall infrastructure including SAP NetWeaver administration tools
that are used by administrators or operators at the customer site
5 System Landscape
52 Shared Services
3856 PUBLIC 2011-04-15
Landscape Aspects
If you use SAP NetWeaver Process Integration 71 productively besides SAP Solution Manager (as a
central support platform) you have to set up Solution Manager Diagnostics for supportability reasons
Implementation Sequence
For information about the implementation of the support infrastructure see the document Master
Guide ndash SAP Solution Manager 70 available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution Manager ltReleasegt
5213 Collection of Landscape Data
Amongst other applications and services the support infrastructure and the SAP NetWeaver
administration tools rely on system landscape data
For SAP NetWeaver PI 71 you have to run non-ABAP components in your solution landscape
Therefore the System Landscape Directory is mandatory The landscape data that is automatically
gathered by the System Landscape Directory is replicated to SAP Solution Manager There are several
topology options for the System Landscape Directory They offer different grades of availability
administration and operation effort
For more information see the System Landscape Directory section
5214 Authentication and Single Sign-On
Before implementing your system landscape plan how to implement authentication and how to
integrate different systems into a Single Sign-On landscape Single Sign-On reduces complexity for end
users saving them valuable time while also reducing administration effort for resetting passwords
thereby contributing to TCO reduction
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
5215 Integrated User and Access Management
In a system landscape containing a combination of ABAP and Java components we recommend that
you integrate your user and access management so that you can use the same user data across different
systems administer this data centrally and control access to data SAPs mature fine-grained
authorization concept allows detailed control of access rights SAP NetWeaver provides both ABAP and
Java-based user management solutions The user management solution that you use to administer
your user data depends on factors such as the type of systems that are running in your landscape
If you want to use central user administration we recommend that you run it in a non-production
system If you do not have a central user administration yet you can for example realize it in the SAP
Solution Manager system
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3956
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
522 Examples for the Overall System Landscape of Shared Services
In this section we provide examples of how shared services can be set up depending on the system
landscape they are intended for The following examples aggregate the landscape aspects given in the
Use Cases section
NOTE
The following sections and the figure mostly do not show information about the life-cycle of
shared services For example you may also need a development and testquality assurance system
for SAP Solution Manager You should consider this aspect in addition to the information given
in this section based on your requirements
Small and MediumndashSized Customer Landscapes with Java
As you use Java productively for SAP NetWeaver PI 71 besides SAP Solution Manager you have to set
up additional components for optimal monitoring administration and support Solution Manager
Diagnostics and the central mode of SAP NetWeaver Administrator are already fully integrated into
SAP Solution Manager 70 as the central operations hub For SAP Process Integration you must also
set up SAP NetWeaver Administrator with a special role
We recommend that you do not install SAP Central Process Scheduling in the SAP Solution Manager
system You have to set up and operate the system which hosts your productive scheduler as a mission
critical system
In the SAP Solution Manager system you should set up a local System Landscape Directory in addition
to a central runtime System Landscape Directory This way you have a clear separation between your
management system (SAP Solution Manager) and managed systems in your landscape In addition
SAP Solution Manager then does not rely on a System Landscape Directory running in the production
environment For this setup configure the SLD data suppliers of your SAP Solution Manager system
to send data to the central runtime System Landscape Directory In addition configure automatic
bridge forwarding from your runtime System Landscape Directory to the local System Landscape
Directory For more information see the Planning Guide - System Landscape Directory
If you want to use a central system for Adobe Document Services we recommend that you install a
dedicated system for this purpose in your production environment For detailed information about
the sizing of the system for the different use cases see the Sizing Guide for Adobe Document Services at
SAP Service Marketplace at httpservicesapcomsizing Sizing Guidelines Solutions amp
Platform
We recommend that you start with this centralized SAP Solution Manager approach as depicted in the
following figure
5 System Landscape
52 Shared Services
4056 PUBLIC 2011-04-15
Figure 7 Single SAP Solution Manager Landscape
Large Customer Landscapes with Java
Large customers who have environments in their landscape that are large and distributed administered
by different groups or separated for security reasons can consider a distributed operations setup In
addition to the centralized setup described for small- and medium-sized customers above large
customers can put parts of the central management functions on extra hosts or systems for performance
or policy reasons You have the following options for a distributed setup
You may set up an extra system or client for Central User Administration (CUA)
The Change and Transport System (CTS) can run on an extra system However it is not
performance- or data-intensive
You may set up an extra system for central CCMS monitoring Depending on the customizing
and on the landscape size central CCMS may generate a lot of system load You can connect a
separate central CCMS to SAP Solution Manager for displaying alerts in the alert inbox of the System
Monitoring work center
You can use a separate SAP NetWeaver 70 system with usage type BI together with SAP Solution
Manager This may make sense with respect to the amount of landscape management data that is
stored for reporting purposes The amount of data strongly depends on the data granularity
storage time frame and landscape size
You can easily put Wily Introscope Enterprise Manager on an separate host
Other aspects described above for small- and medium-customers (such as the setup of the System
Landscape Directory) are also valid for large customers
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4156
523 Feature Details
This section provides further information about the features described above
5231 SAP Solution Manager
SAP provides you with SAP Solution Manager as the strategic application management platform and
to enable the collaboration between you and SAP You need to install at least one productive SAP
Solution Manager in your system landscape To ensure the availability of this application management
platform an SAP Solution Manager system is technically required to install or upgrade to SAP
NetWeaver 70 or higher If you are already using SAP Solution Manager you can also use it to manage
the solution you build with SAP NetWeaver In this case we highly recommend that you update SAP
Solution Manager to the latest version
As of SAP Solution Manager 70 SP15 you can use the newly created work centers
NOTE
During the SAP system installation or upgrade process you are prompted to enter the SAP
Solution Manager key An SAP Solution Manager system is required to generate this key Without
this key the installation or upgrade process cannot continue
You may generate all needed keys for your entire system landscape (development quality
assurance and production system) in one SAP Solution Manager system In case you plan to install
several solution landscapes (for example in different countries) one SAP Solution Manager
system is still sufficient
For more information see SAP Note 805390
It is possible to install multiple SAP Solution Managers If you do so they should host separate business
solutions
If you want to reduce the risk of unavailability you should not install SAP Solution Manager as a central
component Instead you can operate a 2-system-landscape with both a test and production
environment of SAP Solution Manager (especially if you are using time-critical functions like Support
Desk) If you also develop your own content a 3-system-landscape with a development test and
production environment is recommended
For more information about SAP Solution Manager see the following table
Topic Where to Find More Information
System infrastructure scenarios installation and configuration of SAP Solution Manager
Master Guide ndash SAP Solution Manager available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution ManagerltReleasegt
Benefits and usage scenarios SAP Solution Manager ndash Learning Maps available on SAP Service Marketplace at http
5 System Landscape
52 Shared Services
4256 PUBLIC 2011-04-15
Topic Where to Find More Informationservicesapcomrkt-solman or https
servicesapcomsolutionmanager
Additional information See SAP Service Marketplace at http
servicesapcomsolutionmanager
5232 Solution Manager Diagnostics
Solution Manager Diagnostics provides efficient and safe root-cause analysis of incidents in customer
solutions powered by SAP NetWeaver It can help monitor on operating systems databases Java
application activities performance and logs It also supports the reporting of software and
configuration changes that can lead to malfunctions and errors
You must run one Solution Manager Diagnostics within your SAP solution landscape if you run
applications based on SAP NetWeaver systems with usage type AS Java Agents are responsible for
delivering the data from all productive hosts within your system landscape to the Solution Manager
Diagnostics system
CAUTION
SAP Support performs root-cause analysis on incoming incidents with Solution Manager
Diagnostics Not installing and configuring this support infrastructure results in a dramatically
reduced service level
Solution Manager Diagnostics is fully integrated into SAP Solution Manager 70
Solution Manager Diagnostics also contains Wily Introscope (Display Server and Agent part) for
measuring performance as well as to troubleshoot problems of Non-ABAP applications Wily Introscope
is heavily used for troubleshooting applications running on AS Java
SAP has signed a distribution agreement for Wily Introscope SAP customers are allowed to use this
tool in a preconfigured way
For more information about Solution Manager Diagnostics and an FAQ list see SAP Service Marketplace
at httpservicesapcomdiagnostics
5233 System Landscape Directory
The System Landscape Directory (SLD) of SAP NetWeaver is the central directory of system landscape
information relevant for the management of your software life-cycle
NOTE
Note that the abbreviation SLD is not intended to define a product since the System Landscape
Directory is part of SAP NetWeaver This abbreviation is solely intended to improve readability
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4356
The System Landscape Directory contains a description of your system landscape (that is software
components that are currently installed) and a repository of software components that can
theoretically be installed in your landscape (such as the software components available from SAP)
Since this data gets updated automatically the System Landscape Directory provides reliable and up-
to-date system landscape information with as little effort for you as possible In this way the System
Landscape Directory acts as a central information provider for SAP and third-party tools that use this
data to deliver the services you need to keep your landscape up and running
For the System Landscape Directory as part of an SAP NetWeaver PI 71 landscape consider the following
aspects
Part of SAP NetWeaver PI 71 is a new version of the System Landscape Directory It is automatically
included in every SAP NetWeaver 71 system with usage type AS Java It offers enhanced functions
such as a full automatic synchronization mechanism for all data stored in it That is both data
delivered by data suppliers and data entered or changed manually in the System Landscape
Directory can be synchronized automatically This synchronization offers the following
A fully automated mechanism so no user interaction is required and conflicts are resolved
automatically
Asynchronous propagation of information so some nodes may be down temporarily
Communication over HTTP protocol
Uni- and bi-directional synchronization
Depending on your use case the full automatic synchronization could significantly reduce manual
synchronization effort
For SAP NetWeaver PI 71 the configuration of the system landscape directory and its data suppliers
is already included in the standard implementation procedure with SAPinst For existing systems
you only have to perform some quick and easy configuration actions to start operating the system
landscape directory server in an AS Java system
For SAP NetWeaver PI 71 you have the following options concerning SLD
Option 1
Run SAP NetWeaver PI 71 against an existing SLD running on SAP NetWeaver 70 We only
recommend this for upgrades from SAP NetWeaver 70 if you have a central SLD in operation
not running on one of your PI systems
Option 2
Use the SLD included in an SAP NetWeaver PI 71 system We recommend this option for new
installations and upgrades from older releases than SAP NetWeaver 70 due to the enhanced
functions and improved performance of SLD 71
NOTE
If you already have a central SLD running on SAP NetWeaver 70 in operation you could run
two SLD versions in parallel ndash SLD running on SAP NetWeaver 71 for your PI systems and
SLD running on SAP NetWeaver 70 for all other systemsuse cases This way your SAP
5 System Landscape
52 Shared Services
4456 PUBLIC 2011-04-15
NetWeaver PI 71 systems would benefit from the new features while it would be easy to set
up and operate such an SLD landscape For this purpose you could use the new fully
automatic synchronization This feature enables the automatic forwarding of all SLD data
from an SLD running on SAP NetWeaver 70 to an SLD running on SAP NetWeaver 71 As a
result there is no need to adapt most existing systems as their SLD data suppliers could still
send their data to the central SLD In brief the following steps would be required
1 Put SLD in a PI system into operation (part of standard implementation procedure)
2 Configure PI systems to use the new SLD (part of standard implementation procedure
for new PI systems)
3 Set up the fully automatic synchronization from your old SLD to your new SLD
As soon as an upgrade or an installation of a standalone AS Java 71 system is available you
could move your central SLD also to SAP NetWeaver 71 Then you could optionally shift
your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems
Figure 8
We recommend that you use a Domain Name System (DNS) alias so that you are able to switch to
another System Landscape Directory easily For example if customers build a new landscape they
normally start with a sandbox environment Over time more and more environments are set up
Once the production environment is in place move the System Landscape Directory there To do
this you can configure a new System Landscape Directory in the production environment
synchronize it with the old System Landscape directory and switch to the new one
Topology
Apart from the considerations above the System Landscape Directory offers several topology options
with different grades of availability at the expense of low administration and operation effort There is
no generic rule therefore on how to set up a System Landscape Directory in your system landscape
To find the topology and synchronization strategy for the System Landscape Directory that fits your
requirements concerning the System Landscape Directory availability (and hence the availability of
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4556
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
SAP enhancement packages are a new way of delivering new functions for SAP NetWeaver This allows
a clear separation between the delivery of new functions on the one hand and corrections legal changes
and security updates on the other hand (in Support Package stacks) SAP enhancement packages are
cumulative an enhancement package always contains the functions of the corresponding predecessor
enhancement packages
Enhancement packages are maintained by their own Support Packages while the main release is in
maintenance
Benefits
SAP enhancement packages offer the following benefits
You have reduced effort for testing and no effort for training when applying Support Packages as
new features are only shipped with enhancement packages
Adding new functions between releases becomes predictable and controllable
New functions can be added successively in small steps There is no need to fully upgrade your
system to get new functions
You have minimal training effort when applying an enhancement package because existing
functions are not replaced
Implementation
There are the following ways to get an SAP NetWeaver system with the release level of SAP enhancement
package 1 for SAP NetWeaver Process Integration 71
New installation of SAP NetWeaver PI 71 including enhancement package 1 using the standard
installation tool SAPinst
Upgrade of an existing SAP NetWeaver system from a release lower than SAP NetWeaver PI 71 to
SAP NetWeaver PI 71 including enhancement package 1 For this you use the upgrade programs
SAPup (for ABAP) and SAPJup (for Java)
Installation of the enhancement package on an existing SAP NetWeaver PI 71 system
For this you use the Software Update Manager (SUM) The Software Update Manager evolved
from the previously used SAP Enhancement Package Installer The tool has been renamed to reflect
its broader use for example you can also use it for applying Support Package Stacks to your system
On the ABAP side the Software Update Manager uses a system cloning and switch procedure for
installing enhancement packages It installs a copy of the system the shadow system parallel to
the original system This shadow system is used to update the relevant software components and
to install the additional components while the original system is still in production operation At
a certain point during downtime the switch to the new system is made and afterwards any parts
of the original system that are no longer needed are deleted The enhancement package installation
in a Java system uses a deploy-based procedure that is no shadow system is used The Software
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2011-04-15 PUBLIC 2356
Update Manager requires a stack configuration file (xml file) as input file for the enhancement
package installation procedure This file lists all the packages that are to be installed in your systems
The stack configuration file is generated when you download the required packages
As the Software Update Manager is updated regularly we recommend to always use the latest
version It is delivered as part of the SL toolset For more information see http
servicesapcomsltoolset
For an overview of all required steps for the enhancement package installation process and
corresponding documents see Process Overview Installation of Enhancement Package 1 on an Existing SAP
Netweaver PI 71 System [page 28]
Content of SAP Enhancement Package 1 for SAP NetWeaver PI 71
With enhancement package 1 for SAP NetWeaver PI 71 new features are introduced and some existing
are changed The following is a selection of some of the most important enhancements
Enhanced design and modelling options in the Enterprise Services Repository
New services registry
Support for new Web services standard (Web Services Reliable Messaging)
New modules for the Advanced Adapter Engine
Use of shared memory of the ABAP Application Server for message processing
For more information about the changes see SAP Library [page 12] at Whatacutes new in SAP NetWeaver PI 71
ndash Release Notes
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2456 PUBLIC 2011-04-15
4 SOA-Based Integration Use Case
41 Overview
You can use SOA-based integration to set up the communication between service providers and service
consumers in both application-to-application and business-to-business scenarios and to execute
operate and monitor the communication at runtime SOA-based integration covers both direct (point-
to-point) as well as mediated (via an Integration Server) communication between service providers and
service consumers
The use case spans the whole life cycle of a SOA-based integration scenario including
Scenario modeling and service design in the Enterprise Services Repository
Implementation of the service provider and consumer in the back-end systems
Configuration and finally execution monitoring and operation of the integration scenario
For scenarios using Integration Server or broker-based communication the configuration of the
different connectivity options (for example SOAP RFC Web Services Industry standards and JDBC)
and their enhancements is covered
For more information see the following documents
Service-Enabling with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdnsoa-modeling
Getting Started
Service-Enabling a Legacy Application with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdn
soa-servicebus Getting Started
In the following you will find information about the installation of the involved software units
42 System Landscape
The following figure shows the system landscape for this use case
4 SOA-Based Integration Use Case
41 Overview
2011-04-15 PUBLIC 2556
Figure 5 SOA-Based Integration
It is mandatory to have a dedicated PI system This applies to development quality and production
landscapes
For PI it is a prerequisite that no other system in your system landscape has a higher release than
the PI system For exceptions to this rule see SAP Note 1043047 For example SAP XI 30 is compatible
with SAP NetWeaver 640 and 70 application systems since the same XI protocol is used Apart
from these exceptions if you want to upgrade or install an application in your system landscape
you first have to make sure that the PI system is on the same release level If required you have to
upgrade the PI system first to the new or a higher release
CAUTION
Although it should be technically possible to run an application system with a higher release
than your PI system in your system landscape this is not supported by SAP (apart from the
exceptions listed in SAP Note 1043047) Therefore you run such a landscape at your own risk
You can use the Advanced Adapter Engine that is part of your PI system as a central Advanced
Adapter Engine
Adapter Engine (Java SE) can be installed in a non-SAP Java environment However it only hosts
a subset of the adapter functionality is only supported for compatibility reasons and should be
used only if this is a precondition in your environment
Optionally you can use the Change Management Service (CMS) of an SAP NetWeaver 70 system
with usage type DI to transport design objects and repository objects For more information see
the SAP Library [page 12] at Administratoracutes Guide Technical Operations for SAP NetWeaver Administration
of SAP NetWeaver Systems PI (Process Integration) Software Logistics Transporting ESR Content and Objects
of Integration Directory PI Transports Using the Change Management Service (CMS)
Smaller business partners or subsidiaries that do not run SAP NetWeaver install SAP Partner
Connectivity Kit in their system landscape SAP Partner Connectivity Kit enables XML document
4 SOA-Based Integration Use Case
42 System Landscape
2656 PUBLIC 2011-04-15
exchange between your SAP NetWeaver systems and the partner systems Since SAP Partner
Connectivity Kit gets installed in their system landscape it is not shown in the system landscape
figure above
The AS ABAP system acts as an application and service provider For Java Web Services you also
require AS Java In addition you require SAP NetWeaver Developer Studio on the client side as a
development environment
The Web service client can be either an SAP or a non-SAP application For example an AS ABAP
system or a Web browser could act as application or service consumer
You can install SAP Conversion Agent by Informatica in the system with usage type PI or on a host
where SAP Partner Connectivity Kit is installed or on a host where neither usage type PI nor SAP
Partner Connectivity Kit is installed
43 Implementation Sequence
Procedure
To install this use case perform the steps listed in the following table
StepAction[Corresponding Documentation] Remarks
1 Make sure that you have performed the preparation steps You have planned your system landscape [page 33]
(that is you have decided how many systems you require how you want to use each of these systems and which standalone engines and clients you require)
With the help of your hardware partner you have mapped your systems and standalone engines to properly sized hosts
You have planned and installed shared services [page 35]
2 Installation of system with usage type PI (includes the installation of AS ABAP and AS Java)
NOTE
For usage type PI a Unicode installation is mandatory
[Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt]
If you want to use the features of enhancement package 1 use the direct installation of SAP NetWeaver PI 71 including enhancement package 1
Make sure that you perform the configuration steps as described in the installation guide For certain usage types configuration tasks can be applied by the configuration wizard These configuration tasks as well as any additional configuration steps for your use case are listed in SAP Solution Manager For more information
4 SOA-Based Integration Use Case
43 Implementation Sequence
2011-04-15 PUBLIC 2756
StepAction[Corresponding Documentation] Remarks
see the Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt
3 Install the Adapter Engine (Java SE) engines if required[Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
4 To integrate small business partners and subsidiaries the business partners or subsidiaries install SAP Partner Connectivity Kit running on AS Java with parts of usage type PI in the business partners or subsidiarys system landscape[Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
5 Install SAP Conversion Agent by Informatica if required[SAP Library [page 12] at Function-Oriented View Process Integration SAP Conversion Agent by Informatica Deploying and Using Conversion Agent ]
6 Installation of clients SAP GUI
[Installation Guide ndash SAP Front End]
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
The process sequences give a comprehensive overview of the steps relevant for the enhancement
package installation on an existing SAP NetWeaver PI 71 system
The process sequence is divided into a planning phase and an implementation phase Each step in both
phases contains references to the corresponding documentation to ensure that you can easily find the
information you need
Process
NOTE
To download the enhancement package files and required Support Packages you require the SAP
Solution Manager Maintenance Optimizer You have the following options
Manual Selection
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2856 PUBLIC 2011-04-15
You manually select the required files from SAP Service Marketplace at http
servicesapcomswdc using the SP Stack Application You use the Maintenance Optimize
only to approve the packages which is a prerequisite for the download
Automatic Calculation
The Maintenance Optimizer supports the download of a consistent queue that includes all
necessary Support Packages and enhancement packages In addition SAP Solution Manager
calculates a valid import queue for the selected SAP system and generates the enhancement
package stack configuration file that you require for the installation
As a prerequisite the system that you want to update needs to be maintained correctly in
SAP Solution Manager System Landscape As the Maintenance Optimizer uses this data for
the calculation it is crucial that the data is up-to-date In addition the SAP Solution Manager
system requires a Minimum Support Package level (see below)
Planing PhaseStep Description Documentation
Hardware amp Software Prerequisites
Check which platforms are supported for your target release (OSDB dependencies)
Product Availability Matrix (PAM) at httpservicesapcompam
Check which hardware sizing is required for your target release
Sizing information at httpservicesapcomsizing
Solution Manager Prerequisites
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of the required software packages you have to make sure that your SAP Solution Manager system has the required Support Package levelAt least SAP Solution Manager 70 EHP1 Support Package Stack 17 is required We recommend to use SAP Solution Manager 70 EHP1 Support Package Stack 23Check if you need to do an update or upgrade of your SAP Solution ManagerMake sure that you run the guided procedure SOLMAN_SETUP after every installation or update of SAP Solution Manager and that it completes successfully
For upgrades from source release SAP Solution Manager 31 and 32Upgrade Guide ndash SAP Solution Manager 70 incl Enhancement Package 1For updates from SAP Solution Manager 70Update Guide SAP Enhancement Package 1 for SAP Solution Manager 70Follow-up activities after an Support Package Stack update or enhancement package updateSolution Operations Guide ndash SAP Solution Manager 70 EHP1 section Software Change Management All guides are available at http
servicesapcom instguides SAP Components SAP Solution Manager -gt Release 70 EHP 1
Implementation PhaseStep Description Documentation
1Solution Manager Preparation
Configure the SAP Solution Manager Maintenance Optimizer
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of software packages make sure your
Configuration of Maintenance Optimizer http
helpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Change Request Management and Change ControlMaintenance Optimizer
Prerequisites
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 2956
Implementation PhaseStep Description Documentation
system landscape data in SAP Solution Manager is maintained correctlyLandscape Verification 10 which is an add-on to SAP Solution Manager can support you in maintaining your system landscape data The use of this tool is optional
Landscape Verification http
wwwsdnsapcom irj
sdn alm-update-
management link Landscape Verification under Related Areas on Upgrade and Update Management (in the right column)
SAP Note 1468605 (Installation of Landscape Verification)
Maintaining System Landscape Information [page 47]Note that the information provided in this section is based on SAP Solution Manager 70 EHP1 SP23
2System Preparation
Prepare your system as described in the documentation for example perform OS DB specific preparations and the PI-specific preparations
Update Guide ndash Update of SAP Systems with Software Update Manager sections Planning and Preparation
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
3Software Download
Select and download the software packages in either of the following ways Automatic calculation Create
a maintenance transaction in the Maintenance Optimizer and choose the Calculate Files Automatically option
Manual Selection Create a maintenance transaction in the Maintenance Optimizer and choose the Select Files Manually option You then can select the files manually using the SP Stack application in SAP Service Marketplace
NOTE
You have to download the stack configuration file manually after you have selected all files in the SP Stack
httphelpsapcom SAP Solutions SAP Solution Manager
SAP Solution Manager 70 EHP1 ltSPgtChange Request Management and
Change Control Maintenance Optimizer Maintenance Procedure Scenarios
For information about the automatic calculation see Maintenance Transaction with Installation of an Enhancement PackageFor information about the manual selection and approval process see section Approve and Download Files in Download Basket
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
3056 PUBLIC 2011-04-15
Implementation PhaseStep Description Documentation
application Choose Generate Stack XML and save the file
4Enhancement Package Installation
Run Software Update Manager to update your system with the selected software packages
Update Guide ndash Update of SAP Systems with Software Update Manager
5Follow-Up Steps
Perform technical and PI-specific follow-up activities after the enhancement package installation is done
Update Guide ndash Update of SAP Systems with Software Update Manager section Follow-Up Activities
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
6Configuration
Configure newly installed enhancement package functions using SAP Solution Manager content
See Systems with Usage Types [page 16] section Configuration of Systems with Usage Types
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 3156
This page is left blank for documents that are printed on both sides
5 System Landscape
51 Planning Your System Landscape
The installable software units that make up your system landscape depend on the functions that you
want to implement For information about the features see systems [page 16] standalone engines [page 19]
and clients [page 21]
In addition you have to determine the required shared services [page 35] (such as SAP Solution Manager
or SAP NetWeaver Administrator) that run on central systems in your system landscape and the
landscape aspects relevant for their implementation
In the following you will find general information that you should consider when planning your system
landscape
Sizing
You have to map systems and standalone engines to hosts after you have a clear picture of the following
Which systems and standalone engines you require
How many systems you require and how you want to use each of these systems
NOTE
No general guideline can be given for the sizing of your landscape since this relies heavily on your
requirements You should therefore perform this task together with your hardware partner and
your technical consultant
For information about sizing your systems you can use the following information sources
Your first point of reference is the Quick Sizer
SAP built the Quick Sizer as an online sizing questionnaire Internet application in close cooperation
with its hardware partners This tool delivers general sizing categories based on your volume load
estimates The results provide an objective basis for sizing independent of platform and
configuration
For more information see SAP Service Marketplace at
httpservicesapcomsizing for the SAP NetWeaver PI 71 sizing guide available under
Sizing Guidelines Business Suite amp Services
httpservicesapcomquicksizer for more information and access to the tool itself
Also consider the following important aspects concerning sizing
High availability
5 System Landscape
51 Planning Your System Landscape
2011-04-15 PUBLIC 3356
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Technical Infrastructure High Availability
Unicode
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Internationalization
Contact your hardware partner to find out the appropriate number of sized hosts
The platform-independent abstract results of the Quick Sizer can be used by any of our hardware
partners to create a concrete offer SAP itself does not make any hardware recommendations the
responsibility for sizing and detailed hardware configuration lies with the hardware partners
Figure 6 Example of Mapping of Systems and Standalone Engines to Three Hosts
NOTE
Optionally you could also distribute single systems to multiple hosts For example you could
decide to install the database instance of an SAP system on a separate host for performance
reasons or distribute other system instances to achieve high availability
To provide a mapping that fits your required functions and performance your hardware partner
and your technical consultant have to identify the number of required instances of SAP NetWeaver
find out how to distribute these instances to hosts and what functions will run on which instance
Therefore the hardware partner and the technical consultant have to consider many different
aspects such as
Number of required SAPS (SAP Application Benchmark Performance Standard) for each
system (provided by Quick Sizer)
Landscape-relevant aspects concerning security For more information see the SAP Security
Guide in the SAP Library [page 12] at Administratoracutes Guide Security Guide
Landscape-relevant aspects concerning scalability high availability operation and software
life-cycle management
5 System Landscape
51 Planning Your System Landscape
3456 PUBLIC 2011-04-15
For more information about relevant aspects for the mapping of systems to hosts see the document
Technical Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
Scaling and Distribution Options
You may need to design your system landscape for a large number of users SAP NetWeaver PI offers
you different means of scalability The following list provides you with some examples
You could install multiple systems of one type and use them for different purposes
You could scale every system by installing dialog instances or by distributing the database instance
For more information about distribution options on the instance level see the Technical
Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
For every SAP system you could additionally install Web Dispatcher For more information see
the SAP Library [page 12] at FunctionndashOriented View Application Server Infrastructure SAP Web
Dispatcher
You could further distribute certain standalone engines ndash for example Search and Classification
(TREX) is based on a flexible architecture that supports a distributed installation For more
information see the Technical Infrastructure Guide ndash SAP NetWeaver PI 71 available in SAP Service
Marketplace at httpservicesapcominstallNWPI71
52 Shared Services
You normally run shared services on central systems in your system landscape The following features
could be used for SAP NetWeaver Process Integration to realize shared services
SAP Solution Manager
Used to implement train test maintain monitor control change and manage incidents of your
SAP solution system landscape (open end-to-end application management)
As of SAP Solution Manager (70) 40 Support Package 15 SAP Solution Manager has become the
platform for SAPs end-to-end solution operations strategy Functions for complete application
management has been combined with administrative tools and has been merged in newly created
role based work centers
NOTE
Be aware that you require an SAP Solution Manager system to install or upgrade to SAP
NetWeaver 70 and higher An SAP Solution Manager system is required to generate the SAP
Solution Manager key needed during the installation or upgrade process Without this key
the installation or upgrade process cannot continue
For SAP NetWeaver Process Integration you require SAP Solution Manager 70
For more information see SAP Note 805390
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3556
Solution Manager Diagnostics
An integral part of SAP Solution Manager that is running as a Java application on the Java stack of
SAP Solution Manager 70 Solution Manager Diagnostics is used to analyze the root cause of
incidents in your landscape in an efficient and safe way Before Go-Live Solution Manager
Diagnostics has to be set up and made accessible remotely
SAP NetWeaver Administrator
SAP NetWeaver Administrator is the central administration component which is used for
monitoring and administering Java applications It is included in SAP NetWeaver systems with AS
Java
SAP NetWeaver Administrator exists in the following flavors
A local mode which runs out of the box and which focuses on administrating the underlying
SAP NetWeaver AS Java
NOTE
For a SAP NetWeaver PI 71 it has a special role which you need to activate using a
configuation wizard
A central mode which has to be configured before use and which deals with the system
landscape management
SAP has decided to merge the central mode of SAP NetWeaver Administrator into the new work
centers available as of SAP Solution Manager 70 SP 15 Thus it can be used in an administrative
context together with non-Java-based administration tools Although the central mode of SAP
NetWeaver Administrator will be still available for some time SAP will not develop this tool any
further SAP focuses on optimizing the administrative work centers of SAP Solution Manager
instead
The local mode of SAP NetWeaver Administrator stays untouched It is available for current and
future releases of SAP NetWeaver
SAP Central Process Scheduling by Redwood
SAP Central Process Scheduling application by Redwood enables central job scheduling and job
monitoring of current and old releases of AS ABAP systems (as of Basis Release 31) This application
is fully integrated in SAP NetWeaver Depending on the business needs SAP business applications
are the initial trigger for scheduled activities You can now manage jobs and job chains conveniently
using a graphical user interface
System Landscape Directory
The System Landscape Directory is the central directory of system landscape information relevant
for the management of your software life-cycle It contains a description of your system landscape
(that is software components that are currently installed) and a repository of software components
that can theoretically be installed in your landscape (such as the software components available
from SAP)
Adaptive Computing Controller
5 System Landscape
52 Shared Services
3656 PUBLIC 2011-04-15
The Adaptive Computing Controller enables users to control an adaptive computing landscape
from a single point through observation operation and dynamic resource distribution With
adaptive computing hardware software and system services are able to adapt to changing business
needs In the Adaptive Computing Controller the run-time data of logical and physical landscapes
can be monitored application services can be startedstoppedrelocated and hardware resources
can be assigned to application services The operation can also be mass executed and be planned as
tasks to be executed
For more information about the installation of the Adaptive Computing Controller tool see the
document Installation Guide ndash Adaptive Computing Controller in SAP NetWeaver 71 available on SAP Service
Marketplace at httpservicesapcominstallNWPI71
For more information about Adaptive Computing in general see httpsdnsapcomirj
sdnadaptive
521 Use Cases
You can use the applications and tools described above for use cases that are normally performed
centrally The following sections describe these use cases
5211 End-to-End Solution Operations
Running business applications through their complete life-cycle is a challenge Therefore SAP has
started the Run SAP methodology for implementing End-to-End Solution Operations Based on a set
of SAP standards a roadmap and a package for training and certification Run SAP helps customers to
facilitate End-to-End Solution Operations
You can download the SAP standards for Solution Operations from SAP Service Marketplace at http
servicesapcomsupportstandards They describe roles customers typically have in their IT
environment For optimal role support SAP has grouped existing and new functions in SAP Solution
Manager work centers as of SAP Solution Manager 70 Support Package 15 Operations aspects are fully
covered by adding administrative functions for SAP NetWeaver as well Work centers are ABAP Web
Dynpro-based applications They offer the following advantages
Easy to use similar look and feel
Context transfer while jumping from one work center into another
Logical grouping of tools for a certain area
Simple authorization concept
Easy to expand
Each IT role belongs to one or more work centers For instance the Technical Administrator IT role is
covered by the work centers for System Monitoring System Administration and Landscape Management
The following work centers are available
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3756
Business Process Operations
Change Management
Root Cause Analysis
Implementation Upgrade
Incident Management
Test Management
Job Management
System Landscape Management
Solution Documentation Assistant
SAP Engagement and Service Delivery
SAP Solution Manager Administration
System Administration
System Monitoring
My Home is the central point of access to all important data of almost all work centers in SAP Solution
Manager
5212 Support Infrastructure
A key requirement for effective support of IT solutions is the ability to perform root cause analysis with
speed and efficiency
With SAP Solution Manager SAP has long had an infrastructure in place for its ABAP applications that
efficiently supports SAP solutions This helps ensure the high availability and smooth running of
business processes For more information see the SAP Solution Manager section
With Solution Manager Diagnostics this knowledge has been extended to Java applications If for
example homegrown Java applications cause instability Solution Manager Diagnostics helps trace the
cause to eradicate the problem rapidly Solution Manager Diagnostics is fully integrated into SAP
Solution Manager 70 Solution Manager Diagnostics also contains two third-party tools CArsquos Wily
Introscopereg for measuring performance as well as troubleshooting problems of the Java EE Engine
and applications running on it and Mercury Loadrunnerreg which enables SAP Support to produce a
defined load in the SAP solution landscape remotely For more information see Solution Manager
Diagnostics [page 43]
The support infrastructure provides SAP Support with safe access to your productive landscape for safe
root cause analysis so ensuring that SAP Support does not change your landscape inadvertently You
require a support infrastructure to run SAP NetWeaver
The following figure shows the overall infrastructure including SAP NetWeaver administration tools
that are used by administrators or operators at the customer site
5 System Landscape
52 Shared Services
3856 PUBLIC 2011-04-15
Landscape Aspects
If you use SAP NetWeaver Process Integration 71 productively besides SAP Solution Manager (as a
central support platform) you have to set up Solution Manager Diagnostics for supportability reasons
Implementation Sequence
For information about the implementation of the support infrastructure see the document Master
Guide ndash SAP Solution Manager 70 available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution Manager ltReleasegt
5213 Collection of Landscape Data
Amongst other applications and services the support infrastructure and the SAP NetWeaver
administration tools rely on system landscape data
For SAP NetWeaver PI 71 you have to run non-ABAP components in your solution landscape
Therefore the System Landscape Directory is mandatory The landscape data that is automatically
gathered by the System Landscape Directory is replicated to SAP Solution Manager There are several
topology options for the System Landscape Directory They offer different grades of availability
administration and operation effort
For more information see the System Landscape Directory section
5214 Authentication and Single Sign-On
Before implementing your system landscape plan how to implement authentication and how to
integrate different systems into a Single Sign-On landscape Single Sign-On reduces complexity for end
users saving them valuable time while also reducing administration effort for resetting passwords
thereby contributing to TCO reduction
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
5215 Integrated User and Access Management
In a system landscape containing a combination of ABAP and Java components we recommend that
you integrate your user and access management so that you can use the same user data across different
systems administer this data centrally and control access to data SAPs mature fine-grained
authorization concept allows detailed control of access rights SAP NetWeaver provides both ABAP and
Java-based user management solutions The user management solution that you use to administer
your user data depends on factors such as the type of systems that are running in your landscape
If you want to use central user administration we recommend that you run it in a non-production
system If you do not have a central user administration yet you can for example realize it in the SAP
Solution Manager system
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3956
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
522 Examples for the Overall System Landscape of Shared Services
In this section we provide examples of how shared services can be set up depending on the system
landscape they are intended for The following examples aggregate the landscape aspects given in the
Use Cases section
NOTE
The following sections and the figure mostly do not show information about the life-cycle of
shared services For example you may also need a development and testquality assurance system
for SAP Solution Manager You should consider this aspect in addition to the information given
in this section based on your requirements
Small and MediumndashSized Customer Landscapes with Java
As you use Java productively for SAP NetWeaver PI 71 besides SAP Solution Manager you have to set
up additional components for optimal monitoring administration and support Solution Manager
Diagnostics and the central mode of SAP NetWeaver Administrator are already fully integrated into
SAP Solution Manager 70 as the central operations hub For SAP Process Integration you must also
set up SAP NetWeaver Administrator with a special role
We recommend that you do not install SAP Central Process Scheduling in the SAP Solution Manager
system You have to set up and operate the system which hosts your productive scheduler as a mission
critical system
In the SAP Solution Manager system you should set up a local System Landscape Directory in addition
to a central runtime System Landscape Directory This way you have a clear separation between your
management system (SAP Solution Manager) and managed systems in your landscape In addition
SAP Solution Manager then does not rely on a System Landscape Directory running in the production
environment For this setup configure the SLD data suppliers of your SAP Solution Manager system
to send data to the central runtime System Landscape Directory In addition configure automatic
bridge forwarding from your runtime System Landscape Directory to the local System Landscape
Directory For more information see the Planning Guide - System Landscape Directory
If you want to use a central system for Adobe Document Services we recommend that you install a
dedicated system for this purpose in your production environment For detailed information about
the sizing of the system for the different use cases see the Sizing Guide for Adobe Document Services at
SAP Service Marketplace at httpservicesapcomsizing Sizing Guidelines Solutions amp
Platform
We recommend that you start with this centralized SAP Solution Manager approach as depicted in the
following figure
5 System Landscape
52 Shared Services
4056 PUBLIC 2011-04-15
Figure 7 Single SAP Solution Manager Landscape
Large Customer Landscapes with Java
Large customers who have environments in their landscape that are large and distributed administered
by different groups or separated for security reasons can consider a distributed operations setup In
addition to the centralized setup described for small- and medium-sized customers above large
customers can put parts of the central management functions on extra hosts or systems for performance
or policy reasons You have the following options for a distributed setup
You may set up an extra system or client for Central User Administration (CUA)
The Change and Transport System (CTS) can run on an extra system However it is not
performance- or data-intensive
You may set up an extra system for central CCMS monitoring Depending on the customizing
and on the landscape size central CCMS may generate a lot of system load You can connect a
separate central CCMS to SAP Solution Manager for displaying alerts in the alert inbox of the System
Monitoring work center
You can use a separate SAP NetWeaver 70 system with usage type BI together with SAP Solution
Manager This may make sense with respect to the amount of landscape management data that is
stored for reporting purposes The amount of data strongly depends on the data granularity
storage time frame and landscape size
You can easily put Wily Introscope Enterprise Manager on an separate host
Other aspects described above for small- and medium-customers (such as the setup of the System
Landscape Directory) are also valid for large customers
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4156
523 Feature Details
This section provides further information about the features described above
5231 SAP Solution Manager
SAP provides you with SAP Solution Manager as the strategic application management platform and
to enable the collaboration between you and SAP You need to install at least one productive SAP
Solution Manager in your system landscape To ensure the availability of this application management
platform an SAP Solution Manager system is technically required to install or upgrade to SAP
NetWeaver 70 or higher If you are already using SAP Solution Manager you can also use it to manage
the solution you build with SAP NetWeaver In this case we highly recommend that you update SAP
Solution Manager to the latest version
As of SAP Solution Manager 70 SP15 you can use the newly created work centers
NOTE
During the SAP system installation or upgrade process you are prompted to enter the SAP
Solution Manager key An SAP Solution Manager system is required to generate this key Without
this key the installation or upgrade process cannot continue
You may generate all needed keys for your entire system landscape (development quality
assurance and production system) in one SAP Solution Manager system In case you plan to install
several solution landscapes (for example in different countries) one SAP Solution Manager
system is still sufficient
For more information see SAP Note 805390
It is possible to install multiple SAP Solution Managers If you do so they should host separate business
solutions
If you want to reduce the risk of unavailability you should not install SAP Solution Manager as a central
component Instead you can operate a 2-system-landscape with both a test and production
environment of SAP Solution Manager (especially if you are using time-critical functions like Support
Desk) If you also develop your own content a 3-system-landscape with a development test and
production environment is recommended
For more information about SAP Solution Manager see the following table
Topic Where to Find More Information
System infrastructure scenarios installation and configuration of SAP Solution Manager
Master Guide ndash SAP Solution Manager available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution ManagerltReleasegt
Benefits and usage scenarios SAP Solution Manager ndash Learning Maps available on SAP Service Marketplace at http
5 System Landscape
52 Shared Services
4256 PUBLIC 2011-04-15
Topic Where to Find More Informationservicesapcomrkt-solman or https
servicesapcomsolutionmanager
Additional information See SAP Service Marketplace at http
servicesapcomsolutionmanager
5232 Solution Manager Diagnostics
Solution Manager Diagnostics provides efficient and safe root-cause analysis of incidents in customer
solutions powered by SAP NetWeaver It can help monitor on operating systems databases Java
application activities performance and logs It also supports the reporting of software and
configuration changes that can lead to malfunctions and errors
You must run one Solution Manager Diagnostics within your SAP solution landscape if you run
applications based on SAP NetWeaver systems with usage type AS Java Agents are responsible for
delivering the data from all productive hosts within your system landscape to the Solution Manager
Diagnostics system
CAUTION
SAP Support performs root-cause analysis on incoming incidents with Solution Manager
Diagnostics Not installing and configuring this support infrastructure results in a dramatically
reduced service level
Solution Manager Diagnostics is fully integrated into SAP Solution Manager 70
Solution Manager Diagnostics also contains Wily Introscope (Display Server and Agent part) for
measuring performance as well as to troubleshoot problems of Non-ABAP applications Wily Introscope
is heavily used for troubleshooting applications running on AS Java
SAP has signed a distribution agreement for Wily Introscope SAP customers are allowed to use this
tool in a preconfigured way
For more information about Solution Manager Diagnostics and an FAQ list see SAP Service Marketplace
at httpservicesapcomdiagnostics
5233 System Landscape Directory
The System Landscape Directory (SLD) of SAP NetWeaver is the central directory of system landscape
information relevant for the management of your software life-cycle
NOTE
Note that the abbreviation SLD is not intended to define a product since the System Landscape
Directory is part of SAP NetWeaver This abbreviation is solely intended to improve readability
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4356
The System Landscape Directory contains a description of your system landscape (that is software
components that are currently installed) and a repository of software components that can
theoretically be installed in your landscape (such as the software components available from SAP)
Since this data gets updated automatically the System Landscape Directory provides reliable and up-
to-date system landscape information with as little effort for you as possible In this way the System
Landscape Directory acts as a central information provider for SAP and third-party tools that use this
data to deliver the services you need to keep your landscape up and running
For the System Landscape Directory as part of an SAP NetWeaver PI 71 landscape consider the following
aspects
Part of SAP NetWeaver PI 71 is a new version of the System Landscape Directory It is automatically
included in every SAP NetWeaver 71 system with usage type AS Java It offers enhanced functions
such as a full automatic synchronization mechanism for all data stored in it That is both data
delivered by data suppliers and data entered or changed manually in the System Landscape
Directory can be synchronized automatically This synchronization offers the following
A fully automated mechanism so no user interaction is required and conflicts are resolved
automatically
Asynchronous propagation of information so some nodes may be down temporarily
Communication over HTTP protocol
Uni- and bi-directional synchronization
Depending on your use case the full automatic synchronization could significantly reduce manual
synchronization effort
For SAP NetWeaver PI 71 the configuration of the system landscape directory and its data suppliers
is already included in the standard implementation procedure with SAPinst For existing systems
you only have to perform some quick and easy configuration actions to start operating the system
landscape directory server in an AS Java system
For SAP NetWeaver PI 71 you have the following options concerning SLD
Option 1
Run SAP NetWeaver PI 71 against an existing SLD running on SAP NetWeaver 70 We only
recommend this for upgrades from SAP NetWeaver 70 if you have a central SLD in operation
not running on one of your PI systems
Option 2
Use the SLD included in an SAP NetWeaver PI 71 system We recommend this option for new
installations and upgrades from older releases than SAP NetWeaver 70 due to the enhanced
functions and improved performance of SLD 71
NOTE
If you already have a central SLD running on SAP NetWeaver 70 in operation you could run
two SLD versions in parallel ndash SLD running on SAP NetWeaver 71 for your PI systems and
SLD running on SAP NetWeaver 70 for all other systemsuse cases This way your SAP
5 System Landscape
52 Shared Services
4456 PUBLIC 2011-04-15
NetWeaver PI 71 systems would benefit from the new features while it would be easy to set
up and operate such an SLD landscape For this purpose you could use the new fully
automatic synchronization This feature enables the automatic forwarding of all SLD data
from an SLD running on SAP NetWeaver 70 to an SLD running on SAP NetWeaver 71 As a
result there is no need to adapt most existing systems as their SLD data suppliers could still
send their data to the central SLD In brief the following steps would be required
1 Put SLD in a PI system into operation (part of standard implementation procedure)
2 Configure PI systems to use the new SLD (part of standard implementation procedure
for new PI systems)
3 Set up the fully automatic synchronization from your old SLD to your new SLD
As soon as an upgrade or an installation of a standalone AS Java 71 system is available you
could move your central SLD also to SAP NetWeaver 71 Then you could optionally shift
your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems
Figure 8
We recommend that you use a Domain Name System (DNS) alias so that you are able to switch to
another System Landscape Directory easily For example if customers build a new landscape they
normally start with a sandbox environment Over time more and more environments are set up
Once the production environment is in place move the System Landscape Directory there To do
this you can configure a new System Landscape Directory in the production environment
synchronize it with the old System Landscape directory and switch to the new one
Topology
Apart from the considerations above the System Landscape Directory offers several topology options
with different grades of availability at the expense of low administration and operation effort There is
no generic rule therefore on how to set up a System Landscape Directory in your system landscape
To find the topology and synchronization strategy for the System Landscape Directory that fits your
requirements concerning the System Landscape Directory availability (and hence the availability of
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4556
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
Update Manager requires a stack configuration file (xml file) as input file for the enhancement
package installation procedure This file lists all the packages that are to be installed in your systems
The stack configuration file is generated when you download the required packages
As the Software Update Manager is updated regularly we recommend to always use the latest
version It is delivered as part of the SL toolset For more information see http
servicesapcomsltoolset
For an overview of all required steps for the enhancement package installation process and
corresponding documents see Process Overview Installation of Enhancement Package 1 on an Existing SAP
Netweaver PI 71 System [page 28]
Content of SAP Enhancement Package 1 for SAP NetWeaver PI 71
With enhancement package 1 for SAP NetWeaver PI 71 new features are introduced and some existing
are changed The following is a selection of some of the most important enhancements
Enhanced design and modelling options in the Enterprise Services Repository
New services registry
Support for new Web services standard (Web Services Reliable Messaging)
New modules for the Advanced Adapter Engine
Use of shared memory of the ABAP Application Server for message processing
For more information about the changes see SAP Library [page 12] at Whatacutes new in SAP NetWeaver PI 71
ndash Release Notes
3 SAP NetWeaver PI Overview
32 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 71
2456 PUBLIC 2011-04-15
4 SOA-Based Integration Use Case
41 Overview
You can use SOA-based integration to set up the communication between service providers and service
consumers in both application-to-application and business-to-business scenarios and to execute
operate and monitor the communication at runtime SOA-based integration covers both direct (point-
to-point) as well as mediated (via an Integration Server) communication between service providers and
service consumers
The use case spans the whole life cycle of a SOA-based integration scenario including
Scenario modeling and service design in the Enterprise Services Repository
Implementation of the service provider and consumer in the back-end systems
Configuration and finally execution monitoring and operation of the integration scenario
For scenarios using Integration Server or broker-based communication the configuration of the
different connectivity options (for example SOAP RFC Web Services Industry standards and JDBC)
and their enhancements is covered
For more information see the following documents
Service-Enabling with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdnsoa-modeling
Getting Started
Service-Enabling a Legacy Application with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdn
soa-servicebus Getting Started
In the following you will find information about the installation of the involved software units
42 System Landscape
The following figure shows the system landscape for this use case
4 SOA-Based Integration Use Case
41 Overview
2011-04-15 PUBLIC 2556
Figure 5 SOA-Based Integration
It is mandatory to have a dedicated PI system This applies to development quality and production
landscapes
For PI it is a prerequisite that no other system in your system landscape has a higher release than
the PI system For exceptions to this rule see SAP Note 1043047 For example SAP XI 30 is compatible
with SAP NetWeaver 640 and 70 application systems since the same XI protocol is used Apart
from these exceptions if you want to upgrade or install an application in your system landscape
you first have to make sure that the PI system is on the same release level If required you have to
upgrade the PI system first to the new or a higher release
CAUTION
Although it should be technically possible to run an application system with a higher release
than your PI system in your system landscape this is not supported by SAP (apart from the
exceptions listed in SAP Note 1043047) Therefore you run such a landscape at your own risk
You can use the Advanced Adapter Engine that is part of your PI system as a central Advanced
Adapter Engine
Adapter Engine (Java SE) can be installed in a non-SAP Java environment However it only hosts
a subset of the adapter functionality is only supported for compatibility reasons and should be
used only if this is a precondition in your environment
Optionally you can use the Change Management Service (CMS) of an SAP NetWeaver 70 system
with usage type DI to transport design objects and repository objects For more information see
the SAP Library [page 12] at Administratoracutes Guide Technical Operations for SAP NetWeaver Administration
of SAP NetWeaver Systems PI (Process Integration) Software Logistics Transporting ESR Content and Objects
of Integration Directory PI Transports Using the Change Management Service (CMS)
Smaller business partners or subsidiaries that do not run SAP NetWeaver install SAP Partner
Connectivity Kit in their system landscape SAP Partner Connectivity Kit enables XML document
4 SOA-Based Integration Use Case
42 System Landscape
2656 PUBLIC 2011-04-15
exchange between your SAP NetWeaver systems and the partner systems Since SAP Partner
Connectivity Kit gets installed in their system landscape it is not shown in the system landscape
figure above
The AS ABAP system acts as an application and service provider For Java Web Services you also
require AS Java In addition you require SAP NetWeaver Developer Studio on the client side as a
development environment
The Web service client can be either an SAP or a non-SAP application For example an AS ABAP
system or a Web browser could act as application or service consumer
You can install SAP Conversion Agent by Informatica in the system with usage type PI or on a host
where SAP Partner Connectivity Kit is installed or on a host where neither usage type PI nor SAP
Partner Connectivity Kit is installed
43 Implementation Sequence
Procedure
To install this use case perform the steps listed in the following table
StepAction[Corresponding Documentation] Remarks
1 Make sure that you have performed the preparation steps You have planned your system landscape [page 33]
(that is you have decided how many systems you require how you want to use each of these systems and which standalone engines and clients you require)
With the help of your hardware partner you have mapped your systems and standalone engines to properly sized hosts
You have planned and installed shared services [page 35]
2 Installation of system with usage type PI (includes the installation of AS ABAP and AS Java)
NOTE
For usage type PI a Unicode installation is mandatory
[Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt]
If you want to use the features of enhancement package 1 use the direct installation of SAP NetWeaver PI 71 including enhancement package 1
Make sure that you perform the configuration steps as described in the installation guide For certain usage types configuration tasks can be applied by the configuration wizard These configuration tasks as well as any additional configuration steps for your use case are listed in SAP Solution Manager For more information
4 SOA-Based Integration Use Case
43 Implementation Sequence
2011-04-15 PUBLIC 2756
StepAction[Corresponding Documentation] Remarks
see the Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt
3 Install the Adapter Engine (Java SE) engines if required[Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
4 To integrate small business partners and subsidiaries the business partners or subsidiaries install SAP Partner Connectivity Kit running on AS Java with parts of usage type PI in the business partners or subsidiarys system landscape[Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
5 Install SAP Conversion Agent by Informatica if required[SAP Library [page 12] at Function-Oriented View Process Integration SAP Conversion Agent by Informatica Deploying and Using Conversion Agent ]
6 Installation of clients SAP GUI
[Installation Guide ndash SAP Front End]
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
The process sequences give a comprehensive overview of the steps relevant for the enhancement
package installation on an existing SAP NetWeaver PI 71 system
The process sequence is divided into a planning phase and an implementation phase Each step in both
phases contains references to the corresponding documentation to ensure that you can easily find the
information you need
Process
NOTE
To download the enhancement package files and required Support Packages you require the SAP
Solution Manager Maintenance Optimizer You have the following options
Manual Selection
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2856 PUBLIC 2011-04-15
You manually select the required files from SAP Service Marketplace at http
servicesapcomswdc using the SP Stack Application You use the Maintenance Optimize
only to approve the packages which is a prerequisite for the download
Automatic Calculation
The Maintenance Optimizer supports the download of a consistent queue that includes all
necessary Support Packages and enhancement packages In addition SAP Solution Manager
calculates a valid import queue for the selected SAP system and generates the enhancement
package stack configuration file that you require for the installation
As a prerequisite the system that you want to update needs to be maintained correctly in
SAP Solution Manager System Landscape As the Maintenance Optimizer uses this data for
the calculation it is crucial that the data is up-to-date In addition the SAP Solution Manager
system requires a Minimum Support Package level (see below)
Planing PhaseStep Description Documentation
Hardware amp Software Prerequisites
Check which platforms are supported for your target release (OSDB dependencies)
Product Availability Matrix (PAM) at httpservicesapcompam
Check which hardware sizing is required for your target release
Sizing information at httpservicesapcomsizing
Solution Manager Prerequisites
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of the required software packages you have to make sure that your SAP Solution Manager system has the required Support Package levelAt least SAP Solution Manager 70 EHP1 Support Package Stack 17 is required We recommend to use SAP Solution Manager 70 EHP1 Support Package Stack 23Check if you need to do an update or upgrade of your SAP Solution ManagerMake sure that you run the guided procedure SOLMAN_SETUP after every installation or update of SAP Solution Manager and that it completes successfully
For upgrades from source release SAP Solution Manager 31 and 32Upgrade Guide ndash SAP Solution Manager 70 incl Enhancement Package 1For updates from SAP Solution Manager 70Update Guide SAP Enhancement Package 1 for SAP Solution Manager 70Follow-up activities after an Support Package Stack update or enhancement package updateSolution Operations Guide ndash SAP Solution Manager 70 EHP1 section Software Change Management All guides are available at http
servicesapcom instguides SAP Components SAP Solution Manager -gt Release 70 EHP 1
Implementation PhaseStep Description Documentation
1Solution Manager Preparation
Configure the SAP Solution Manager Maintenance Optimizer
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of software packages make sure your
Configuration of Maintenance Optimizer http
helpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Change Request Management and Change ControlMaintenance Optimizer
Prerequisites
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 2956
Implementation PhaseStep Description Documentation
system landscape data in SAP Solution Manager is maintained correctlyLandscape Verification 10 which is an add-on to SAP Solution Manager can support you in maintaining your system landscape data The use of this tool is optional
Landscape Verification http
wwwsdnsapcom irj
sdn alm-update-
management link Landscape Verification under Related Areas on Upgrade and Update Management (in the right column)
SAP Note 1468605 (Installation of Landscape Verification)
Maintaining System Landscape Information [page 47]Note that the information provided in this section is based on SAP Solution Manager 70 EHP1 SP23
2System Preparation
Prepare your system as described in the documentation for example perform OS DB specific preparations and the PI-specific preparations
Update Guide ndash Update of SAP Systems with Software Update Manager sections Planning and Preparation
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
3Software Download
Select and download the software packages in either of the following ways Automatic calculation Create
a maintenance transaction in the Maintenance Optimizer and choose the Calculate Files Automatically option
Manual Selection Create a maintenance transaction in the Maintenance Optimizer and choose the Select Files Manually option You then can select the files manually using the SP Stack application in SAP Service Marketplace
NOTE
You have to download the stack configuration file manually after you have selected all files in the SP Stack
httphelpsapcom SAP Solutions SAP Solution Manager
SAP Solution Manager 70 EHP1 ltSPgtChange Request Management and
Change Control Maintenance Optimizer Maintenance Procedure Scenarios
For information about the automatic calculation see Maintenance Transaction with Installation of an Enhancement PackageFor information about the manual selection and approval process see section Approve and Download Files in Download Basket
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
3056 PUBLIC 2011-04-15
Implementation PhaseStep Description Documentation
application Choose Generate Stack XML and save the file
4Enhancement Package Installation
Run Software Update Manager to update your system with the selected software packages
Update Guide ndash Update of SAP Systems with Software Update Manager
5Follow-Up Steps
Perform technical and PI-specific follow-up activities after the enhancement package installation is done
Update Guide ndash Update of SAP Systems with Software Update Manager section Follow-Up Activities
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
6Configuration
Configure newly installed enhancement package functions using SAP Solution Manager content
See Systems with Usage Types [page 16] section Configuration of Systems with Usage Types
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 3156
This page is left blank for documents that are printed on both sides
5 System Landscape
51 Planning Your System Landscape
The installable software units that make up your system landscape depend on the functions that you
want to implement For information about the features see systems [page 16] standalone engines [page 19]
and clients [page 21]
In addition you have to determine the required shared services [page 35] (such as SAP Solution Manager
or SAP NetWeaver Administrator) that run on central systems in your system landscape and the
landscape aspects relevant for their implementation
In the following you will find general information that you should consider when planning your system
landscape
Sizing
You have to map systems and standalone engines to hosts after you have a clear picture of the following
Which systems and standalone engines you require
How many systems you require and how you want to use each of these systems
NOTE
No general guideline can be given for the sizing of your landscape since this relies heavily on your
requirements You should therefore perform this task together with your hardware partner and
your technical consultant
For information about sizing your systems you can use the following information sources
Your first point of reference is the Quick Sizer
SAP built the Quick Sizer as an online sizing questionnaire Internet application in close cooperation
with its hardware partners This tool delivers general sizing categories based on your volume load
estimates The results provide an objective basis for sizing independent of platform and
configuration
For more information see SAP Service Marketplace at
httpservicesapcomsizing for the SAP NetWeaver PI 71 sizing guide available under
Sizing Guidelines Business Suite amp Services
httpservicesapcomquicksizer for more information and access to the tool itself
Also consider the following important aspects concerning sizing
High availability
5 System Landscape
51 Planning Your System Landscape
2011-04-15 PUBLIC 3356
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Technical Infrastructure High Availability
Unicode
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Internationalization
Contact your hardware partner to find out the appropriate number of sized hosts
The platform-independent abstract results of the Quick Sizer can be used by any of our hardware
partners to create a concrete offer SAP itself does not make any hardware recommendations the
responsibility for sizing and detailed hardware configuration lies with the hardware partners
Figure 6 Example of Mapping of Systems and Standalone Engines to Three Hosts
NOTE
Optionally you could also distribute single systems to multiple hosts For example you could
decide to install the database instance of an SAP system on a separate host for performance
reasons or distribute other system instances to achieve high availability
To provide a mapping that fits your required functions and performance your hardware partner
and your technical consultant have to identify the number of required instances of SAP NetWeaver
find out how to distribute these instances to hosts and what functions will run on which instance
Therefore the hardware partner and the technical consultant have to consider many different
aspects such as
Number of required SAPS (SAP Application Benchmark Performance Standard) for each
system (provided by Quick Sizer)
Landscape-relevant aspects concerning security For more information see the SAP Security
Guide in the SAP Library [page 12] at Administratoracutes Guide Security Guide
Landscape-relevant aspects concerning scalability high availability operation and software
life-cycle management
5 System Landscape
51 Planning Your System Landscape
3456 PUBLIC 2011-04-15
For more information about relevant aspects for the mapping of systems to hosts see the document
Technical Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
Scaling and Distribution Options
You may need to design your system landscape for a large number of users SAP NetWeaver PI offers
you different means of scalability The following list provides you with some examples
You could install multiple systems of one type and use them for different purposes
You could scale every system by installing dialog instances or by distributing the database instance
For more information about distribution options on the instance level see the Technical
Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
For every SAP system you could additionally install Web Dispatcher For more information see
the SAP Library [page 12] at FunctionndashOriented View Application Server Infrastructure SAP Web
Dispatcher
You could further distribute certain standalone engines ndash for example Search and Classification
(TREX) is based on a flexible architecture that supports a distributed installation For more
information see the Technical Infrastructure Guide ndash SAP NetWeaver PI 71 available in SAP Service
Marketplace at httpservicesapcominstallNWPI71
52 Shared Services
You normally run shared services on central systems in your system landscape The following features
could be used for SAP NetWeaver Process Integration to realize shared services
SAP Solution Manager
Used to implement train test maintain monitor control change and manage incidents of your
SAP solution system landscape (open end-to-end application management)
As of SAP Solution Manager (70) 40 Support Package 15 SAP Solution Manager has become the
platform for SAPs end-to-end solution operations strategy Functions for complete application
management has been combined with administrative tools and has been merged in newly created
role based work centers
NOTE
Be aware that you require an SAP Solution Manager system to install or upgrade to SAP
NetWeaver 70 and higher An SAP Solution Manager system is required to generate the SAP
Solution Manager key needed during the installation or upgrade process Without this key
the installation or upgrade process cannot continue
For SAP NetWeaver Process Integration you require SAP Solution Manager 70
For more information see SAP Note 805390
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3556
Solution Manager Diagnostics
An integral part of SAP Solution Manager that is running as a Java application on the Java stack of
SAP Solution Manager 70 Solution Manager Diagnostics is used to analyze the root cause of
incidents in your landscape in an efficient and safe way Before Go-Live Solution Manager
Diagnostics has to be set up and made accessible remotely
SAP NetWeaver Administrator
SAP NetWeaver Administrator is the central administration component which is used for
monitoring and administering Java applications It is included in SAP NetWeaver systems with AS
Java
SAP NetWeaver Administrator exists in the following flavors
A local mode which runs out of the box and which focuses on administrating the underlying
SAP NetWeaver AS Java
NOTE
For a SAP NetWeaver PI 71 it has a special role which you need to activate using a
configuation wizard
A central mode which has to be configured before use and which deals with the system
landscape management
SAP has decided to merge the central mode of SAP NetWeaver Administrator into the new work
centers available as of SAP Solution Manager 70 SP 15 Thus it can be used in an administrative
context together with non-Java-based administration tools Although the central mode of SAP
NetWeaver Administrator will be still available for some time SAP will not develop this tool any
further SAP focuses on optimizing the administrative work centers of SAP Solution Manager
instead
The local mode of SAP NetWeaver Administrator stays untouched It is available for current and
future releases of SAP NetWeaver
SAP Central Process Scheduling by Redwood
SAP Central Process Scheduling application by Redwood enables central job scheduling and job
monitoring of current and old releases of AS ABAP systems (as of Basis Release 31) This application
is fully integrated in SAP NetWeaver Depending on the business needs SAP business applications
are the initial trigger for scheduled activities You can now manage jobs and job chains conveniently
using a graphical user interface
System Landscape Directory
The System Landscape Directory is the central directory of system landscape information relevant
for the management of your software life-cycle It contains a description of your system landscape
(that is software components that are currently installed) and a repository of software components
that can theoretically be installed in your landscape (such as the software components available
from SAP)
Adaptive Computing Controller
5 System Landscape
52 Shared Services
3656 PUBLIC 2011-04-15
The Adaptive Computing Controller enables users to control an adaptive computing landscape
from a single point through observation operation and dynamic resource distribution With
adaptive computing hardware software and system services are able to adapt to changing business
needs In the Adaptive Computing Controller the run-time data of logical and physical landscapes
can be monitored application services can be startedstoppedrelocated and hardware resources
can be assigned to application services The operation can also be mass executed and be planned as
tasks to be executed
For more information about the installation of the Adaptive Computing Controller tool see the
document Installation Guide ndash Adaptive Computing Controller in SAP NetWeaver 71 available on SAP Service
Marketplace at httpservicesapcominstallNWPI71
For more information about Adaptive Computing in general see httpsdnsapcomirj
sdnadaptive
521 Use Cases
You can use the applications and tools described above for use cases that are normally performed
centrally The following sections describe these use cases
5211 End-to-End Solution Operations
Running business applications through their complete life-cycle is a challenge Therefore SAP has
started the Run SAP methodology for implementing End-to-End Solution Operations Based on a set
of SAP standards a roadmap and a package for training and certification Run SAP helps customers to
facilitate End-to-End Solution Operations
You can download the SAP standards for Solution Operations from SAP Service Marketplace at http
servicesapcomsupportstandards They describe roles customers typically have in their IT
environment For optimal role support SAP has grouped existing and new functions in SAP Solution
Manager work centers as of SAP Solution Manager 70 Support Package 15 Operations aspects are fully
covered by adding administrative functions for SAP NetWeaver as well Work centers are ABAP Web
Dynpro-based applications They offer the following advantages
Easy to use similar look and feel
Context transfer while jumping from one work center into another
Logical grouping of tools for a certain area
Simple authorization concept
Easy to expand
Each IT role belongs to one or more work centers For instance the Technical Administrator IT role is
covered by the work centers for System Monitoring System Administration and Landscape Management
The following work centers are available
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3756
Business Process Operations
Change Management
Root Cause Analysis
Implementation Upgrade
Incident Management
Test Management
Job Management
System Landscape Management
Solution Documentation Assistant
SAP Engagement and Service Delivery
SAP Solution Manager Administration
System Administration
System Monitoring
My Home is the central point of access to all important data of almost all work centers in SAP Solution
Manager
5212 Support Infrastructure
A key requirement for effective support of IT solutions is the ability to perform root cause analysis with
speed and efficiency
With SAP Solution Manager SAP has long had an infrastructure in place for its ABAP applications that
efficiently supports SAP solutions This helps ensure the high availability and smooth running of
business processes For more information see the SAP Solution Manager section
With Solution Manager Diagnostics this knowledge has been extended to Java applications If for
example homegrown Java applications cause instability Solution Manager Diagnostics helps trace the
cause to eradicate the problem rapidly Solution Manager Diagnostics is fully integrated into SAP
Solution Manager 70 Solution Manager Diagnostics also contains two third-party tools CArsquos Wily
Introscopereg for measuring performance as well as troubleshooting problems of the Java EE Engine
and applications running on it and Mercury Loadrunnerreg which enables SAP Support to produce a
defined load in the SAP solution landscape remotely For more information see Solution Manager
Diagnostics [page 43]
The support infrastructure provides SAP Support with safe access to your productive landscape for safe
root cause analysis so ensuring that SAP Support does not change your landscape inadvertently You
require a support infrastructure to run SAP NetWeaver
The following figure shows the overall infrastructure including SAP NetWeaver administration tools
that are used by administrators or operators at the customer site
5 System Landscape
52 Shared Services
3856 PUBLIC 2011-04-15
Landscape Aspects
If you use SAP NetWeaver Process Integration 71 productively besides SAP Solution Manager (as a
central support platform) you have to set up Solution Manager Diagnostics for supportability reasons
Implementation Sequence
For information about the implementation of the support infrastructure see the document Master
Guide ndash SAP Solution Manager 70 available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution Manager ltReleasegt
5213 Collection of Landscape Data
Amongst other applications and services the support infrastructure and the SAP NetWeaver
administration tools rely on system landscape data
For SAP NetWeaver PI 71 you have to run non-ABAP components in your solution landscape
Therefore the System Landscape Directory is mandatory The landscape data that is automatically
gathered by the System Landscape Directory is replicated to SAP Solution Manager There are several
topology options for the System Landscape Directory They offer different grades of availability
administration and operation effort
For more information see the System Landscape Directory section
5214 Authentication and Single Sign-On
Before implementing your system landscape plan how to implement authentication and how to
integrate different systems into a Single Sign-On landscape Single Sign-On reduces complexity for end
users saving them valuable time while also reducing administration effort for resetting passwords
thereby contributing to TCO reduction
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
5215 Integrated User and Access Management
In a system landscape containing a combination of ABAP and Java components we recommend that
you integrate your user and access management so that you can use the same user data across different
systems administer this data centrally and control access to data SAPs mature fine-grained
authorization concept allows detailed control of access rights SAP NetWeaver provides both ABAP and
Java-based user management solutions The user management solution that you use to administer
your user data depends on factors such as the type of systems that are running in your landscape
If you want to use central user administration we recommend that you run it in a non-production
system If you do not have a central user administration yet you can for example realize it in the SAP
Solution Manager system
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3956
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
522 Examples for the Overall System Landscape of Shared Services
In this section we provide examples of how shared services can be set up depending on the system
landscape they are intended for The following examples aggregate the landscape aspects given in the
Use Cases section
NOTE
The following sections and the figure mostly do not show information about the life-cycle of
shared services For example you may also need a development and testquality assurance system
for SAP Solution Manager You should consider this aspect in addition to the information given
in this section based on your requirements
Small and MediumndashSized Customer Landscapes with Java
As you use Java productively for SAP NetWeaver PI 71 besides SAP Solution Manager you have to set
up additional components for optimal monitoring administration and support Solution Manager
Diagnostics and the central mode of SAP NetWeaver Administrator are already fully integrated into
SAP Solution Manager 70 as the central operations hub For SAP Process Integration you must also
set up SAP NetWeaver Administrator with a special role
We recommend that you do not install SAP Central Process Scheduling in the SAP Solution Manager
system You have to set up and operate the system which hosts your productive scheduler as a mission
critical system
In the SAP Solution Manager system you should set up a local System Landscape Directory in addition
to a central runtime System Landscape Directory This way you have a clear separation between your
management system (SAP Solution Manager) and managed systems in your landscape In addition
SAP Solution Manager then does not rely on a System Landscape Directory running in the production
environment For this setup configure the SLD data suppliers of your SAP Solution Manager system
to send data to the central runtime System Landscape Directory In addition configure automatic
bridge forwarding from your runtime System Landscape Directory to the local System Landscape
Directory For more information see the Planning Guide - System Landscape Directory
If you want to use a central system for Adobe Document Services we recommend that you install a
dedicated system for this purpose in your production environment For detailed information about
the sizing of the system for the different use cases see the Sizing Guide for Adobe Document Services at
SAP Service Marketplace at httpservicesapcomsizing Sizing Guidelines Solutions amp
Platform
We recommend that you start with this centralized SAP Solution Manager approach as depicted in the
following figure
5 System Landscape
52 Shared Services
4056 PUBLIC 2011-04-15
Figure 7 Single SAP Solution Manager Landscape
Large Customer Landscapes with Java
Large customers who have environments in their landscape that are large and distributed administered
by different groups or separated for security reasons can consider a distributed operations setup In
addition to the centralized setup described for small- and medium-sized customers above large
customers can put parts of the central management functions on extra hosts or systems for performance
or policy reasons You have the following options for a distributed setup
You may set up an extra system or client for Central User Administration (CUA)
The Change and Transport System (CTS) can run on an extra system However it is not
performance- or data-intensive
You may set up an extra system for central CCMS monitoring Depending on the customizing
and on the landscape size central CCMS may generate a lot of system load You can connect a
separate central CCMS to SAP Solution Manager for displaying alerts in the alert inbox of the System
Monitoring work center
You can use a separate SAP NetWeaver 70 system with usage type BI together with SAP Solution
Manager This may make sense with respect to the amount of landscape management data that is
stored for reporting purposes The amount of data strongly depends on the data granularity
storage time frame and landscape size
You can easily put Wily Introscope Enterprise Manager on an separate host
Other aspects described above for small- and medium-customers (such as the setup of the System
Landscape Directory) are also valid for large customers
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4156
523 Feature Details
This section provides further information about the features described above
5231 SAP Solution Manager
SAP provides you with SAP Solution Manager as the strategic application management platform and
to enable the collaboration between you and SAP You need to install at least one productive SAP
Solution Manager in your system landscape To ensure the availability of this application management
platform an SAP Solution Manager system is technically required to install or upgrade to SAP
NetWeaver 70 or higher If you are already using SAP Solution Manager you can also use it to manage
the solution you build with SAP NetWeaver In this case we highly recommend that you update SAP
Solution Manager to the latest version
As of SAP Solution Manager 70 SP15 you can use the newly created work centers
NOTE
During the SAP system installation or upgrade process you are prompted to enter the SAP
Solution Manager key An SAP Solution Manager system is required to generate this key Without
this key the installation or upgrade process cannot continue
You may generate all needed keys for your entire system landscape (development quality
assurance and production system) in one SAP Solution Manager system In case you plan to install
several solution landscapes (for example in different countries) one SAP Solution Manager
system is still sufficient
For more information see SAP Note 805390
It is possible to install multiple SAP Solution Managers If you do so they should host separate business
solutions
If you want to reduce the risk of unavailability you should not install SAP Solution Manager as a central
component Instead you can operate a 2-system-landscape with both a test and production
environment of SAP Solution Manager (especially if you are using time-critical functions like Support
Desk) If you also develop your own content a 3-system-landscape with a development test and
production environment is recommended
For more information about SAP Solution Manager see the following table
Topic Where to Find More Information
System infrastructure scenarios installation and configuration of SAP Solution Manager
Master Guide ndash SAP Solution Manager available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution ManagerltReleasegt
Benefits and usage scenarios SAP Solution Manager ndash Learning Maps available on SAP Service Marketplace at http
5 System Landscape
52 Shared Services
4256 PUBLIC 2011-04-15
Topic Where to Find More Informationservicesapcomrkt-solman or https
servicesapcomsolutionmanager
Additional information See SAP Service Marketplace at http
servicesapcomsolutionmanager
5232 Solution Manager Diagnostics
Solution Manager Diagnostics provides efficient and safe root-cause analysis of incidents in customer
solutions powered by SAP NetWeaver It can help monitor on operating systems databases Java
application activities performance and logs It also supports the reporting of software and
configuration changes that can lead to malfunctions and errors
You must run one Solution Manager Diagnostics within your SAP solution landscape if you run
applications based on SAP NetWeaver systems with usage type AS Java Agents are responsible for
delivering the data from all productive hosts within your system landscape to the Solution Manager
Diagnostics system
CAUTION
SAP Support performs root-cause analysis on incoming incidents with Solution Manager
Diagnostics Not installing and configuring this support infrastructure results in a dramatically
reduced service level
Solution Manager Diagnostics is fully integrated into SAP Solution Manager 70
Solution Manager Diagnostics also contains Wily Introscope (Display Server and Agent part) for
measuring performance as well as to troubleshoot problems of Non-ABAP applications Wily Introscope
is heavily used for troubleshooting applications running on AS Java
SAP has signed a distribution agreement for Wily Introscope SAP customers are allowed to use this
tool in a preconfigured way
For more information about Solution Manager Diagnostics and an FAQ list see SAP Service Marketplace
at httpservicesapcomdiagnostics
5233 System Landscape Directory
The System Landscape Directory (SLD) of SAP NetWeaver is the central directory of system landscape
information relevant for the management of your software life-cycle
NOTE
Note that the abbreviation SLD is not intended to define a product since the System Landscape
Directory is part of SAP NetWeaver This abbreviation is solely intended to improve readability
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4356
The System Landscape Directory contains a description of your system landscape (that is software
components that are currently installed) and a repository of software components that can
theoretically be installed in your landscape (such as the software components available from SAP)
Since this data gets updated automatically the System Landscape Directory provides reliable and up-
to-date system landscape information with as little effort for you as possible In this way the System
Landscape Directory acts as a central information provider for SAP and third-party tools that use this
data to deliver the services you need to keep your landscape up and running
For the System Landscape Directory as part of an SAP NetWeaver PI 71 landscape consider the following
aspects
Part of SAP NetWeaver PI 71 is a new version of the System Landscape Directory It is automatically
included in every SAP NetWeaver 71 system with usage type AS Java It offers enhanced functions
such as a full automatic synchronization mechanism for all data stored in it That is both data
delivered by data suppliers and data entered or changed manually in the System Landscape
Directory can be synchronized automatically This synchronization offers the following
A fully automated mechanism so no user interaction is required and conflicts are resolved
automatically
Asynchronous propagation of information so some nodes may be down temporarily
Communication over HTTP protocol
Uni- and bi-directional synchronization
Depending on your use case the full automatic synchronization could significantly reduce manual
synchronization effort
For SAP NetWeaver PI 71 the configuration of the system landscape directory and its data suppliers
is already included in the standard implementation procedure with SAPinst For existing systems
you only have to perform some quick and easy configuration actions to start operating the system
landscape directory server in an AS Java system
For SAP NetWeaver PI 71 you have the following options concerning SLD
Option 1
Run SAP NetWeaver PI 71 against an existing SLD running on SAP NetWeaver 70 We only
recommend this for upgrades from SAP NetWeaver 70 if you have a central SLD in operation
not running on one of your PI systems
Option 2
Use the SLD included in an SAP NetWeaver PI 71 system We recommend this option for new
installations and upgrades from older releases than SAP NetWeaver 70 due to the enhanced
functions and improved performance of SLD 71
NOTE
If you already have a central SLD running on SAP NetWeaver 70 in operation you could run
two SLD versions in parallel ndash SLD running on SAP NetWeaver 71 for your PI systems and
SLD running on SAP NetWeaver 70 for all other systemsuse cases This way your SAP
5 System Landscape
52 Shared Services
4456 PUBLIC 2011-04-15
NetWeaver PI 71 systems would benefit from the new features while it would be easy to set
up and operate such an SLD landscape For this purpose you could use the new fully
automatic synchronization This feature enables the automatic forwarding of all SLD data
from an SLD running on SAP NetWeaver 70 to an SLD running on SAP NetWeaver 71 As a
result there is no need to adapt most existing systems as their SLD data suppliers could still
send their data to the central SLD In brief the following steps would be required
1 Put SLD in a PI system into operation (part of standard implementation procedure)
2 Configure PI systems to use the new SLD (part of standard implementation procedure
for new PI systems)
3 Set up the fully automatic synchronization from your old SLD to your new SLD
As soon as an upgrade or an installation of a standalone AS Java 71 system is available you
could move your central SLD also to SAP NetWeaver 71 Then you could optionally shift
your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems
Figure 8
We recommend that you use a Domain Name System (DNS) alias so that you are able to switch to
another System Landscape Directory easily For example if customers build a new landscape they
normally start with a sandbox environment Over time more and more environments are set up
Once the production environment is in place move the System Landscape Directory there To do
this you can configure a new System Landscape Directory in the production environment
synchronize it with the old System Landscape directory and switch to the new one
Topology
Apart from the considerations above the System Landscape Directory offers several topology options
with different grades of availability at the expense of low administration and operation effort There is
no generic rule therefore on how to set up a System Landscape Directory in your system landscape
To find the topology and synchronization strategy for the System Landscape Directory that fits your
requirements concerning the System Landscape Directory availability (and hence the availability of
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4556
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
4 SOA-Based Integration Use Case
41 Overview
You can use SOA-based integration to set up the communication between service providers and service
consumers in both application-to-application and business-to-business scenarios and to execute
operate and monitor the communication at runtime SOA-based integration covers both direct (point-
to-point) as well as mediated (via an Integration Server) communication between service providers and
service consumers
The use case spans the whole life cycle of a SOA-based integration scenario including
Scenario modeling and service design in the Enterprise Services Repository
Implementation of the service provider and consumer in the back-end systems
Configuration and finally execution monitoring and operation of the integration scenario
For scenarios using Integration Server or broker-based communication the configuration of the
different connectivity options (for example SOAP RFC Web Services Industry standards and JDBC)
and their enhancements is covered
For more information see the following documents
Service-Enabling with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdnsoa-modeling
Getting Started
Service-Enabling a Legacy Application with SAP NetWeaver PI 71 at httpswwwsdnsapcomirjsdn
soa-servicebus Getting Started
In the following you will find information about the installation of the involved software units
42 System Landscape
The following figure shows the system landscape for this use case
4 SOA-Based Integration Use Case
41 Overview
2011-04-15 PUBLIC 2556
Figure 5 SOA-Based Integration
It is mandatory to have a dedicated PI system This applies to development quality and production
landscapes
For PI it is a prerequisite that no other system in your system landscape has a higher release than
the PI system For exceptions to this rule see SAP Note 1043047 For example SAP XI 30 is compatible
with SAP NetWeaver 640 and 70 application systems since the same XI protocol is used Apart
from these exceptions if you want to upgrade or install an application in your system landscape
you first have to make sure that the PI system is on the same release level If required you have to
upgrade the PI system first to the new or a higher release
CAUTION
Although it should be technically possible to run an application system with a higher release
than your PI system in your system landscape this is not supported by SAP (apart from the
exceptions listed in SAP Note 1043047) Therefore you run such a landscape at your own risk
You can use the Advanced Adapter Engine that is part of your PI system as a central Advanced
Adapter Engine
Adapter Engine (Java SE) can be installed in a non-SAP Java environment However it only hosts
a subset of the adapter functionality is only supported for compatibility reasons and should be
used only if this is a precondition in your environment
Optionally you can use the Change Management Service (CMS) of an SAP NetWeaver 70 system
with usage type DI to transport design objects and repository objects For more information see
the SAP Library [page 12] at Administratoracutes Guide Technical Operations for SAP NetWeaver Administration
of SAP NetWeaver Systems PI (Process Integration) Software Logistics Transporting ESR Content and Objects
of Integration Directory PI Transports Using the Change Management Service (CMS)
Smaller business partners or subsidiaries that do not run SAP NetWeaver install SAP Partner
Connectivity Kit in their system landscape SAP Partner Connectivity Kit enables XML document
4 SOA-Based Integration Use Case
42 System Landscape
2656 PUBLIC 2011-04-15
exchange between your SAP NetWeaver systems and the partner systems Since SAP Partner
Connectivity Kit gets installed in their system landscape it is not shown in the system landscape
figure above
The AS ABAP system acts as an application and service provider For Java Web Services you also
require AS Java In addition you require SAP NetWeaver Developer Studio on the client side as a
development environment
The Web service client can be either an SAP or a non-SAP application For example an AS ABAP
system or a Web browser could act as application or service consumer
You can install SAP Conversion Agent by Informatica in the system with usage type PI or on a host
where SAP Partner Connectivity Kit is installed or on a host where neither usage type PI nor SAP
Partner Connectivity Kit is installed
43 Implementation Sequence
Procedure
To install this use case perform the steps listed in the following table
StepAction[Corresponding Documentation] Remarks
1 Make sure that you have performed the preparation steps You have planned your system landscape [page 33]
(that is you have decided how many systems you require how you want to use each of these systems and which standalone engines and clients you require)
With the help of your hardware partner you have mapped your systems and standalone engines to properly sized hosts
You have planned and installed shared services [page 35]
2 Installation of system with usage type PI (includes the installation of AS ABAP and AS Java)
NOTE
For usage type PI a Unicode installation is mandatory
[Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt]
If you want to use the features of enhancement package 1 use the direct installation of SAP NetWeaver PI 71 including enhancement package 1
Make sure that you perform the configuration steps as described in the installation guide For certain usage types configuration tasks can be applied by the configuration wizard These configuration tasks as well as any additional configuration steps for your use case are listed in SAP Solution Manager For more information
4 SOA-Based Integration Use Case
43 Implementation Sequence
2011-04-15 PUBLIC 2756
StepAction[Corresponding Documentation] Remarks
see the Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt
3 Install the Adapter Engine (Java SE) engines if required[Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
4 To integrate small business partners and subsidiaries the business partners or subsidiaries install SAP Partner Connectivity Kit running on AS Java with parts of usage type PI in the business partners or subsidiarys system landscape[Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
5 Install SAP Conversion Agent by Informatica if required[SAP Library [page 12] at Function-Oriented View Process Integration SAP Conversion Agent by Informatica Deploying and Using Conversion Agent ]
6 Installation of clients SAP GUI
[Installation Guide ndash SAP Front End]
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
The process sequences give a comprehensive overview of the steps relevant for the enhancement
package installation on an existing SAP NetWeaver PI 71 system
The process sequence is divided into a planning phase and an implementation phase Each step in both
phases contains references to the corresponding documentation to ensure that you can easily find the
information you need
Process
NOTE
To download the enhancement package files and required Support Packages you require the SAP
Solution Manager Maintenance Optimizer You have the following options
Manual Selection
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2856 PUBLIC 2011-04-15
You manually select the required files from SAP Service Marketplace at http
servicesapcomswdc using the SP Stack Application You use the Maintenance Optimize
only to approve the packages which is a prerequisite for the download
Automatic Calculation
The Maintenance Optimizer supports the download of a consistent queue that includes all
necessary Support Packages and enhancement packages In addition SAP Solution Manager
calculates a valid import queue for the selected SAP system and generates the enhancement
package stack configuration file that you require for the installation
As a prerequisite the system that you want to update needs to be maintained correctly in
SAP Solution Manager System Landscape As the Maintenance Optimizer uses this data for
the calculation it is crucial that the data is up-to-date In addition the SAP Solution Manager
system requires a Minimum Support Package level (see below)
Planing PhaseStep Description Documentation
Hardware amp Software Prerequisites
Check which platforms are supported for your target release (OSDB dependencies)
Product Availability Matrix (PAM) at httpservicesapcompam
Check which hardware sizing is required for your target release
Sizing information at httpservicesapcomsizing
Solution Manager Prerequisites
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of the required software packages you have to make sure that your SAP Solution Manager system has the required Support Package levelAt least SAP Solution Manager 70 EHP1 Support Package Stack 17 is required We recommend to use SAP Solution Manager 70 EHP1 Support Package Stack 23Check if you need to do an update or upgrade of your SAP Solution ManagerMake sure that you run the guided procedure SOLMAN_SETUP after every installation or update of SAP Solution Manager and that it completes successfully
For upgrades from source release SAP Solution Manager 31 and 32Upgrade Guide ndash SAP Solution Manager 70 incl Enhancement Package 1For updates from SAP Solution Manager 70Update Guide SAP Enhancement Package 1 for SAP Solution Manager 70Follow-up activities after an Support Package Stack update or enhancement package updateSolution Operations Guide ndash SAP Solution Manager 70 EHP1 section Software Change Management All guides are available at http
servicesapcom instguides SAP Components SAP Solution Manager -gt Release 70 EHP 1
Implementation PhaseStep Description Documentation
1Solution Manager Preparation
Configure the SAP Solution Manager Maintenance Optimizer
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of software packages make sure your
Configuration of Maintenance Optimizer http
helpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Change Request Management and Change ControlMaintenance Optimizer
Prerequisites
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 2956
Implementation PhaseStep Description Documentation
system landscape data in SAP Solution Manager is maintained correctlyLandscape Verification 10 which is an add-on to SAP Solution Manager can support you in maintaining your system landscape data The use of this tool is optional
Landscape Verification http
wwwsdnsapcom irj
sdn alm-update-
management link Landscape Verification under Related Areas on Upgrade and Update Management (in the right column)
SAP Note 1468605 (Installation of Landscape Verification)
Maintaining System Landscape Information [page 47]Note that the information provided in this section is based on SAP Solution Manager 70 EHP1 SP23
2System Preparation
Prepare your system as described in the documentation for example perform OS DB specific preparations and the PI-specific preparations
Update Guide ndash Update of SAP Systems with Software Update Manager sections Planning and Preparation
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
3Software Download
Select and download the software packages in either of the following ways Automatic calculation Create
a maintenance transaction in the Maintenance Optimizer and choose the Calculate Files Automatically option
Manual Selection Create a maintenance transaction in the Maintenance Optimizer and choose the Select Files Manually option You then can select the files manually using the SP Stack application in SAP Service Marketplace
NOTE
You have to download the stack configuration file manually after you have selected all files in the SP Stack
httphelpsapcom SAP Solutions SAP Solution Manager
SAP Solution Manager 70 EHP1 ltSPgtChange Request Management and
Change Control Maintenance Optimizer Maintenance Procedure Scenarios
For information about the automatic calculation see Maintenance Transaction with Installation of an Enhancement PackageFor information about the manual selection and approval process see section Approve and Download Files in Download Basket
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
3056 PUBLIC 2011-04-15
Implementation PhaseStep Description Documentation
application Choose Generate Stack XML and save the file
4Enhancement Package Installation
Run Software Update Manager to update your system with the selected software packages
Update Guide ndash Update of SAP Systems with Software Update Manager
5Follow-Up Steps
Perform technical and PI-specific follow-up activities after the enhancement package installation is done
Update Guide ndash Update of SAP Systems with Software Update Manager section Follow-Up Activities
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
6Configuration
Configure newly installed enhancement package functions using SAP Solution Manager content
See Systems with Usage Types [page 16] section Configuration of Systems with Usage Types
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 3156
This page is left blank for documents that are printed on both sides
5 System Landscape
51 Planning Your System Landscape
The installable software units that make up your system landscape depend on the functions that you
want to implement For information about the features see systems [page 16] standalone engines [page 19]
and clients [page 21]
In addition you have to determine the required shared services [page 35] (such as SAP Solution Manager
or SAP NetWeaver Administrator) that run on central systems in your system landscape and the
landscape aspects relevant for their implementation
In the following you will find general information that you should consider when planning your system
landscape
Sizing
You have to map systems and standalone engines to hosts after you have a clear picture of the following
Which systems and standalone engines you require
How many systems you require and how you want to use each of these systems
NOTE
No general guideline can be given for the sizing of your landscape since this relies heavily on your
requirements You should therefore perform this task together with your hardware partner and
your technical consultant
For information about sizing your systems you can use the following information sources
Your first point of reference is the Quick Sizer
SAP built the Quick Sizer as an online sizing questionnaire Internet application in close cooperation
with its hardware partners This tool delivers general sizing categories based on your volume load
estimates The results provide an objective basis for sizing independent of platform and
configuration
For more information see SAP Service Marketplace at
httpservicesapcomsizing for the SAP NetWeaver PI 71 sizing guide available under
Sizing Guidelines Business Suite amp Services
httpservicesapcomquicksizer for more information and access to the tool itself
Also consider the following important aspects concerning sizing
High availability
5 System Landscape
51 Planning Your System Landscape
2011-04-15 PUBLIC 3356
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Technical Infrastructure High Availability
Unicode
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Internationalization
Contact your hardware partner to find out the appropriate number of sized hosts
The platform-independent abstract results of the Quick Sizer can be used by any of our hardware
partners to create a concrete offer SAP itself does not make any hardware recommendations the
responsibility for sizing and detailed hardware configuration lies with the hardware partners
Figure 6 Example of Mapping of Systems and Standalone Engines to Three Hosts
NOTE
Optionally you could also distribute single systems to multiple hosts For example you could
decide to install the database instance of an SAP system on a separate host for performance
reasons or distribute other system instances to achieve high availability
To provide a mapping that fits your required functions and performance your hardware partner
and your technical consultant have to identify the number of required instances of SAP NetWeaver
find out how to distribute these instances to hosts and what functions will run on which instance
Therefore the hardware partner and the technical consultant have to consider many different
aspects such as
Number of required SAPS (SAP Application Benchmark Performance Standard) for each
system (provided by Quick Sizer)
Landscape-relevant aspects concerning security For more information see the SAP Security
Guide in the SAP Library [page 12] at Administratoracutes Guide Security Guide
Landscape-relevant aspects concerning scalability high availability operation and software
life-cycle management
5 System Landscape
51 Planning Your System Landscape
3456 PUBLIC 2011-04-15
For more information about relevant aspects for the mapping of systems to hosts see the document
Technical Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
Scaling and Distribution Options
You may need to design your system landscape for a large number of users SAP NetWeaver PI offers
you different means of scalability The following list provides you with some examples
You could install multiple systems of one type and use them for different purposes
You could scale every system by installing dialog instances or by distributing the database instance
For more information about distribution options on the instance level see the Technical
Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
For every SAP system you could additionally install Web Dispatcher For more information see
the SAP Library [page 12] at FunctionndashOriented View Application Server Infrastructure SAP Web
Dispatcher
You could further distribute certain standalone engines ndash for example Search and Classification
(TREX) is based on a flexible architecture that supports a distributed installation For more
information see the Technical Infrastructure Guide ndash SAP NetWeaver PI 71 available in SAP Service
Marketplace at httpservicesapcominstallNWPI71
52 Shared Services
You normally run shared services on central systems in your system landscape The following features
could be used for SAP NetWeaver Process Integration to realize shared services
SAP Solution Manager
Used to implement train test maintain monitor control change and manage incidents of your
SAP solution system landscape (open end-to-end application management)
As of SAP Solution Manager (70) 40 Support Package 15 SAP Solution Manager has become the
platform for SAPs end-to-end solution operations strategy Functions for complete application
management has been combined with administrative tools and has been merged in newly created
role based work centers
NOTE
Be aware that you require an SAP Solution Manager system to install or upgrade to SAP
NetWeaver 70 and higher An SAP Solution Manager system is required to generate the SAP
Solution Manager key needed during the installation or upgrade process Without this key
the installation or upgrade process cannot continue
For SAP NetWeaver Process Integration you require SAP Solution Manager 70
For more information see SAP Note 805390
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3556
Solution Manager Diagnostics
An integral part of SAP Solution Manager that is running as a Java application on the Java stack of
SAP Solution Manager 70 Solution Manager Diagnostics is used to analyze the root cause of
incidents in your landscape in an efficient and safe way Before Go-Live Solution Manager
Diagnostics has to be set up and made accessible remotely
SAP NetWeaver Administrator
SAP NetWeaver Administrator is the central administration component which is used for
monitoring and administering Java applications It is included in SAP NetWeaver systems with AS
Java
SAP NetWeaver Administrator exists in the following flavors
A local mode which runs out of the box and which focuses on administrating the underlying
SAP NetWeaver AS Java
NOTE
For a SAP NetWeaver PI 71 it has a special role which you need to activate using a
configuation wizard
A central mode which has to be configured before use and which deals with the system
landscape management
SAP has decided to merge the central mode of SAP NetWeaver Administrator into the new work
centers available as of SAP Solution Manager 70 SP 15 Thus it can be used in an administrative
context together with non-Java-based administration tools Although the central mode of SAP
NetWeaver Administrator will be still available for some time SAP will not develop this tool any
further SAP focuses on optimizing the administrative work centers of SAP Solution Manager
instead
The local mode of SAP NetWeaver Administrator stays untouched It is available for current and
future releases of SAP NetWeaver
SAP Central Process Scheduling by Redwood
SAP Central Process Scheduling application by Redwood enables central job scheduling and job
monitoring of current and old releases of AS ABAP systems (as of Basis Release 31) This application
is fully integrated in SAP NetWeaver Depending on the business needs SAP business applications
are the initial trigger for scheduled activities You can now manage jobs and job chains conveniently
using a graphical user interface
System Landscape Directory
The System Landscape Directory is the central directory of system landscape information relevant
for the management of your software life-cycle It contains a description of your system landscape
(that is software components that are currently installed) and a repository of software components
that can theoretically be installed in your landscape (such as the software components available
from SAP)
Adaptive Computing Controller
5 System Landscape
52 Shared Services
3656 PUBLIC 2011-04-15
The Adaptive Computing Controller enables users to control an adaptive computing landscape
from a single point through observation operation and dynamic resource distribution With
adaptive computing hardware software and system services are able to adapt to changing business
needs In the Adaptive Computing Controller the run-time data of logical and physical landscapes
can be monitored application services can be startedstoppedrelocated and hardware resources
can be assigned to application services The operation can also be mass executed and be planned as
tasks to be executed
For more information about the installation of the Adaptive Computing Controller tool see the
document Installation Guide ndash Adaptive Computing Controller in SAP NetWeaver 71 available on SAP Service
Marketplace at httpservicesapcominstallNWPI71
For more information about Adaptive Computing in general see httpsdnsapcomirj
sdnadaptive
521 Use Cases
You can use the applications and tools described above for use cases that are normally performed
centrally The following sections describe these use cases
5211 End-to-End Solution Operations
Running business applications through their complete life-cycle is a challenge Therefore SAP has
started the Run SAP methodology for implementing End-to-End Solution Operations Based on a set
of SAP standards a roadmap and a package for training and certification Run SAP helps customers to
facilitate End-to-End Solution Operations
You can download the SAP standards for Solution Operations from SAP Service Marketplace at http
servicesapcomsupportstandards They describe roles customers typically have in their IT
environment For optimal role support SAP has grouped existing and new functions in SAP Solution
Manager work centers as of SAP Solution Manager 70 Support Package 15 Operations aspects are fully
covered by adding administrative functions for SAP NetWeaver as well Work centers are ABAP Web
Dynpro-based applications They offer the following advantages
Easy to use similar look and feel
Context transfer while jumping from one work center into another
Logical grouping of tools for a certain area
Simple authorization concept
Easy to expand
Each IT role belongs to one or more work centers For instance the Technical Administrator IT role is
covered by the work centers for System Monitoring System Administration and Landscape Management
The following work centers are available
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3756
Business Process Operations
Change Management
Root Cause Analysis
Implementation Upgrade
Incident Management
Test Management
Job Management
System Landscape Management
Solution Documentation Assistant
SAP Engagement and Service Delivery
SAP Solution Manager Administration
System Administration
System Monitoring
My Home is the central point of access to all important data of almost all work centers in SAP Solution
Manager
5212 Support Infrastructure
A key requirement for effective support of IT solutions is the ability to perform root cause analysis with
speed and efficiency
With SAP Solution Manager SAP has long had an infrastructure in place for its ABAP applications that
efficiently supports SAP solutions This helps ensure the high availability and smooth running of
business processes For more information see the SAP Solution Manager section
With Solution Manager Diagnostics this knowledge has been extended to Java applications If for
example homegrown Java applications cause instability Solution Manager Diagnostics helps trace the
cause to eradicate the problem rapidly Solution Manager Diagnostics is fully integrated into SAP
Solution Manager 70 Solution Manager Diagnostics also contains two third-party tools CArsquos Wily
Introscopereg for measuring performance as well as troubleshooting problems of the Java EE Engine
and applications running on it and Mercury Loadrunnerreg which enables SAP Support to produce a
defined load in the SAP solution landscape remotely For more information see Solution Manager
Diagnostics [page 43]
The support infrastructure provides SAP Support with safe access to your productive landscape for safe
root cause analysis so ensuring that SAP Support does not change your landscape inadvertently You
require a support infrastructure to run SAP NetWeaver
The following figure shows the overall infrastructure including SAP NetWeaver administration tools
that are used by administrators or operators at the customer site
5 System Landscape
52 Shared Services
3856 PUBLIC 2011-04-15
Landscape Aspects
If you use SAP NetWeaver Process Integration 71 productively besides SAP Solution Manager (as a
central support platform) you have to set up Solution Manager Diagnostics for supportability reasons
Implementation Sequence
For information about the implementation of the support infrastructure see the document Master
Guide ndash SAP Solution Manager 70 available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution Manager ltReleasegt
5213 Collection of Landscape Data
Amongst other applications and services the support infrastructure and the SAP NetWeaver
administration tools rely on system landscape data
For SAP NetWeaver PI 71 you have to run non-ABAP components in your solution landscape
Therefore the System Landscape Directory is mandatory The landscape data that is automatically
gathered by the System Landscape Directory is replicated to SAP Solution Manager There are several
topology options for the System Landscape Directory They offer different grades of availability
administration and operation effort
For more information see the System Landscape Directory section
5214 Authentication and Single Sign-On
Before implementing your system landscape plan how to implement authentication and how to
integrate different systems into a Single Sign-On landscape Single Sign-On reduces complexity for end
users saving them valuable time while also reducing administration effort for resetting passwords
thereby contributing to TCO reduction
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
5215 Integrated User and Access Management
In a system landscape containing a combination of ABAP and Java components we recommend that
you integrate your user and access management so that you can use the same user data across different
systems administer this data centrally and control access to data SAPs mature fine-grained
authorization concept allows detailed control of access rights SAP NetWeaver provides both ABAP and
Java-based user management solutions The user management solution that you use to administer
your user data depends on factors such as the type of systems that are running in your landscape
If you want to use central user administration we recommend that you run it in a non-production
system If you do not have a central user administration yet you can for example realize it in the SAP
Solution Manager system
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3956
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
522 Examples for the Overall System Landscape of Shared Services
In this section we provide examples of how shared services can be set up depending on the system
landscape they are intended for The following examples aggregate the landscape aspects given in the
Use Cases section
NOTE
The following sections and the figure mostly do not show information about the life-cycle of
shared services For example you may also need a development and testquality assurance system
for SAP Solution Manager You should consider this aspect in addition to the information given
in this section based on your requirements
Small and MediumndashSized Customer Landscapes with Java
As you use Java productively for SAP NetWeaver PI 71 besides SAP Solution Manager you have to set
up additional components for optimal monitoring administration and support Solution Manager
Diagnostics and the central mode of SAP NetWeaver Administrator are already fully integrated into
SAP Solution Manager 70 as the central operations hub For SAP Process Integration you must also
set up SAP NetWeaver Administrator with a special role
We recommend that you do not install SAP Central Process Scheduling in the SAP Solution Manager
system You have to set up and operate the system which hosts your productive scheduler as a mission
critical system
In the SAP Solution Manager system you should set up a local System Landscape Directory in addition
to a central runtime System Landscape Directory This way you have a clear separation between your
management system (SAP Solution Manager) and managed systems in your landscape In addition
SAP Solution Manager then does not rely on a System Landscape Directory running in the production
environment For this setup configure the SLD data suppliers of your SAP Solution Manager system
to send data to the central runtime System Landscape Directory In addition configure automatic
bridge forwarding from your runtime System Landscape Directory to the local System Landscape
Directory For more information see the Planning Guide - System Landscape Directory
If you want to use a central system for Adobe Document Services we recommend that you install a
dedicated system for this purpose in your production environment For detailed information about
the sizing of the system for the different use cases see the Sizing Guide for Adobe Document Services at
SAP Service Marketplace at httpservicesapcomsizing Sizing Guidelines Solutions amp
Platform
We recommend that you start with this centralized SAP Solution Manager approach as depicted in the
following figure
5 System Landscape
52 Shared Services
4056 PUBLIC 2011-04-15
Figure 7 Single SAP Solution Manager Landscape
Large Customer Landscapes with Java
Large customers who have environments in their landscape that are large and distributed administered
by different groups or separated for security reasons can consider a distributed operations setup In
addition to the centralized setup described for small- and medium-sized customers above large
customers can put parts of the central management functions on extra hosts or systems for performance
or policy reasons You have the following options for a distributed setup
You may set up an extra system or client for Central User Administration (CUA)
The Change and Transport System (CTS) can run on an extra system However it is not
performance- or data-intensive
You may set up an extra system for central CCMS monitoring Depending on the customizing
and on the landscape size central CCMS may generate a lot of system load You can connect a
separate central CCMS to SAP Solution Manager for displaying alerts in the alert inbox of the System
Monitoring work center
You can use a separate SAP NetWeaver 70 system with usage type BI together with SAP Solution
Manager This may make sense with respect to the amount of landscape management data that is
stored for reporting purposes The amount of data strongly depends on the data granularity
storage time frame and landscape size
You can easily put Wily Introscope Enterprise Manager on an separate host
Other aspects described above for small- and medium-customers (such as the setup of the System
Landscape Directory) are also valid for large customers
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4156
523 Feature Details
This section provides further information about the features described above
5231 SAP Solution Manager
SAP provides you with SAP Solution Manager as the strategic application management platform and
to enable the collaboration between you and SAP You need to install at least one productive SAP
Solution Manager in your system landscape To ensure the availability of this application management
platform an SAP Solution Manager system is technically required to install or upgrade to SAP
NetWeaver 70 or higher If you are already using SAP Solution Manager you can also use it to manage
the solution you build with SAP NetWeaver In this case we highly recommend that you update SAP
Solution Manager to the latest version
As of SAP Solution Manager 70 SP15 you can use the newly created work centers
NOTE
During the SAP system installation or upgrade process you are prompted to enter the SAP
Solution Manager key An SAP Solution Manager system is required to generate this key Without
this key the installation or upgrade process cannot continue
You may generate all needed keys for your entire system landscape (development quality
assurance and production system) in one SAP Solution Manager system In case you plan to install
several solution landscapes (for example in different countries) one SAP Solution Manager
system is still sufficient
For more information see SAP Note 805390
It is possible to install multiple SAP Solution Managers If you do so they should host separate business
solutions
If you want to reduce the risk of unavailability you should not install SAP Solution Manager as a central
component Instead you can operate a 2-system-landscape with both a test and production
environment of SAP Solution Manager (especially if you are using time-critical functions like Support
Desk) If you also develop your own content a 3-system-landscape with a development test and
production environment is recommended
For more information about SAP Solution Manager see the following table
Topic Where to Find More Information
System infrastructure scenarios installation and configuration of SAP Solution Manager
Master Guide ndash SAP Solution Manager available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution ManagerltReleasegt
Benefits and usage scenarios SAP Solution Manager ndash Learning Maps available on SAP Service Marketplace at http
5 System Landscape
52 Shared Services
4256 PUBLIC 2011-04-15
Topic Where to Find More Informationservicesapcomrkt-solman or https
servicesapcomsolutionmanager
Additional information See SAP Service Marketplace at http
servicesapcomsolutionmanager
5232 Solution Manager Diagnostics
Solution Manager Diagnostics provides efficient and safe root-cause analysis of incidents in customer
solutions powered by SAP NetWeaver It can help monitor on operating systems databases Java
application activities performance and logs It also supports the reporting of software and
configuration changes that can lead to malfunctions and errors
You must run one Solution Manager Diagnostics within your SAP solution landscape if you run
applications based on SAP NetWeaver systems with usage type AS Java Agents are responsible for
delivering the data from all productive hosts within your system landscape to the Solution Manager
Diagnostics system
CAUTION
SAP Support performs root-cause analysis on incoming incidents with Solution Manager
Diagnostics Not installing and configuring this support infrastructure results in a dramatically
reduced service level
Solution Manager Diagnostics is fully integrated into SAP Solution Manager 70
Solution Manager Diagnostics also contains Wily Introscope (Display Server and Agent part) for
measuring performance as well as to troubleshoot problems of Non-ABAP applications Wily Introscope
is heavily used for troubleshooting applications running on AS Java
SAP has signed a distribution agreement for Wily Introscope SAP customers are allowed to use this
tool in a preconfigured way
For more information about Solution Manager Diagnostics and an FAQ list see SAP Service Marketplace
at httpservicesapcomdiagnostics
5233 System Landscape Directory
The System Landscape Directory (SLD) of SAP NetWeaver is the central directory of system landscape
information relevant for the management of your software life-cycle
NOTE
Note that the abbreviation SLD is not intended to define a product since the System Landscape
Directory is part of SAP NetWeaver This abbreviation is solely intended to improve readability
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4356
The System Landscape Directory contains a description of your system landscape (that is software
components that are currently installed) and a repository of software components that can
theoretically be installed in your landscape (such as the software components available from SAP)
Since this data gets updated automatically the System Landscape Directory provides reliable and up-
to-date system landscape information with as little effort for you as possible In this way the System
Landscape Directory acts as a central information provider for SAP and third-party tools that use this
data to deliver the services you need to keep your landscape up and running
For the System Landscape Directory as part of an SAP NetWeaver PI 71 landscape consider the following
aspects
Part of SAP NetWeaver PI 71 is a new version of the System Landscape Directory It is automatically
included in every SAP NetWeaver 71 system with usage type AS Java It offers enhanced functions
such as a full automatic synchronization mechanism for all data stored in it That is both data
delivered by data suppliers and data entered or changed manually in the System Landscape
Directory can be synchronized automatically This synchronization offers the following
A fully automated mechanism so no user interaction is required and conflicts are resolved
automatically
Asynchronous propagation of information so some nodes may be down temporarily
Communication over HTTP protocol
Uni- and bi-directional synchronization
Depending on your use case the full automatic synchronization could significantly reduce manual
synchronization effort
For SAP NetWeaver PI 71 the configuration of the system landscape directory and its data suppliers
is already included in the standard implementation procedure with SAPinst For existing systems
you only have to perform some quick and easy configuration actions to start operating the system
landscape directory server in an AS Java system
For SAP NetWeaver PI 71 you have the following options concerning SLD
Option 1
Run SAP NetWeaver PI 71 against an existing SLD running on SAP NetWeaver 70 We only
recommend this for upgrades from SAP NetWeaver 70 if you have a central SLD in operation
not running on one of your PI systems
Option 2
Use the SLD included in an SAP NetWeaver PI 71 system We recommend this option for new
installations and upgrades from older releases than SAP NetWeaver 70 due to the enhanced
functions and improved performance of SLD 71
NOTE
If you already have a central SLD running on SAP NetWeaver 70 in operation you could run
two SLD versions in parallel ndash SLD running on SAP NetWeaver 71 for your PI systems and
SLD running on SAP NetWeaver 70 for all other systemsuse cases This way your SAP
5 System Landscape
52 Shared Services
4456 PUBLIC 2011-04-15
NetWeaver PI 71 systems would benefit from the new features while it would be easy to set
up and operate such an SLD landscape For this purpose you could use the new fully
automatic synchronization This feature enables the automatic forwarding of all SLD data
from an SLD running on SAP NetWeaver 70 to an SLD running on SAP NetWeaver 71 As a
result there is no need to adapt most existing systems as their SLD data suppliers could still
send their data to the central SLD In brief the following steps would be required
1 Put SLD in a PI system into operation (part of standard implementation procedure)
2 Configure PI systems to use the new SLD (part of standard implementation procedure
for new PI systems)
3 Set up the fully automatic synchronization from your old SLD to your new SLD
As soon as an upgrade or an installation of a standalone AS Java 71 system is available you
could move your central SLD also to SAP NetWeaver 71 Then you could optionally shift
your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems
Figure 8
We recommend that you use a Domain Name System (DNS) alias so that you are able to switch to
another System Landscape Directory easily For example if customers build a new landscape they
normally start with a sandbox environment Over time more and more environments are set up
Once the production environment is in place move the System Landscape Directory there To do
this you can configure a new System Landscape Directory in the production environment
synchronize it with the old System Landscape directory and switch to the new one
Topology
Apart from the considerations above the System Landscape Directory offers several topology options
with different grades of availability at the expense of low administration and operation effort There is
no generic rule therefore on how to set up a System Landscape Directory in your system landscape
To find the topology and synchronization strategy for the System Landscape Directory that fits your
requirements concerning the System Landscape Directory availability (and hence the availability of
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4556
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
Figure 5 SOA-Based Integration
It is mandatory to have a dedicated PI system This applies to development quality and production
landscapes
For PI it is a prerequisite that no other system in your system landscape has a higher release than
the PI system For exceptions to this rule see SAP Note 1043047 For example SAP XI 30 is compatible
with SAP NetWeaver 640 and 70 application systems since the same XI protocol is used Apart
from these exceptions if you want to upgrade or install an application in your system landscape
you first have to make sure that the PI system is on the same release level If required you have to
upgrade the PI system first to the new or a higher release
CAUTION
Although it should be technically possible to run an application system with a higher release
than your PI system in your system landscape this is not supported by SAP (apart from the
exceptions listed in SAP Note 1043047) Therefore you run such a landscape at your own risk
You can use the Advanced Adapter Engine that is part of your PI system as a central Advanced
Adapter Engine
Adapter Engine (Java SE) can be installed in a non-SAP Java environment However it only hosts
a subset of the adapter functionality is only supported for compatibility reasons and should be
used only if this is a precondition in your environment
Optionally you can use the Change Management Service (CMS) of an SAP NetWeaver 70 system
with usage type DI to transport design objects and repository objects For more information see
the SAP Library [page 12] at Administratoracutes Guide Technical Operations for SAP NetWeaver Administration
of SAP NetWeaver Systems PI (Process Integration) Software Logistics Transporting ESR Content and Objects
of Integration Directory PI Transports Using the Change Management Service (CMS)
Smaller business partners or subsidiaries that do not run SAP NetWeaver install SAP Partner
Connectivity Kit in their system landscape SAP Partner Connectivity Kit enables XML document
4 SOA-Based Integration Use Case
42 System Landscape
2656 PUBLIC 2011-04-15
exchange between your SAP NetWeaver systems and the partner systems Since SAP Partner
Connectivity Kit gets installed in their system landscape it is not shown in the system landscape
figure above
The AS ABAP system acts as an application and service provider For Java Web Services you also
require AS Java In addition you require SAP NetWeaver Developer Studio on the client side as a
development environment
The Web service client can be either an SAP or a non-SAP application For example an AS ABAP
system or a Web browser could act as application or service consumer
You can install SAP Conversion Agent by Informatica in the system with usage type PI or on a host
where SAP Partner Connectivity Kit is installed or on a host where neither usage type PI nor SAP
Partner Connectivity Kit is installed
43 Implementation Sequence
Procedure
To install this use case perform the steps listed in the following table
StepAction[Corresponding Documentation] Remarks
1 Make sure that you have performed the preparation steps You have planned your system landscape [page 33]
(that is you have decided how many systems you require how you want to use each of these systems and which standalone engines and clients you require)
With the help of your hardware partner you have mapped your systems and standalone engines to properly sized hosts
You have planned and installed shared services [page 35]
2 Installation of system with usage type PI (includes the installation of AS ABAP and AS Java)
NOTE
For usage type PI a Unicode installation is mandatory
[Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt]
If you want to use the features of enhancement package 1 use the direct installation of SAP NetWeaver PI 71 including enhancement package 1
Make sure that you perform the configuration steps as described in the installation guide For certain usage types configuration tasks can be applied by the configuration wizard These configuration tasks as well as any additional configuration steps for your use case are listed in SAP Solution Manager For more information
4 SOA-Based Integration Use Case
43 Implementation Sequence
2011-04-15 PUBLIC 2756
StepAction[Corresponding Documentation] Remarks
see the Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt
3 Install the Adapter Engine (Java SE) engines if required[Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
4 To integrate small business partners and subsidiaries the business partners or subsidiaries install SAP Partner Connectivity Kit running on AS Java with parts of usage type PI in the business partners or subsidiarys system landscape[Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
5 Install SAP Conversion Agent by Informatica if required[SAP Library [page 12] at Function-Oriented View Process Integration SAP Conversion Agent by Informatica Deploying and Using Conversion Agent ]
6 Installation of clients SAP GUI
[Installation Guide ndash SAP Front End]
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
The process sequences give a comprehensive overview of the steps relevant for the enhancement
package installation on an existing SAP NetWeaver PI 71 system
The process sequence is divided into a planning phase and an implementation phase Each step in both
phases contains references to the corresponding documentation to ensure that you can easily find the
information you need
Process
NOTE
To download the enhancement package files and required Support Packages you require the SAP
Solution Manager Maintenance Optimizer You have the following options
Manual Selection
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2856 PUBLIC 2011-04-15
You manually select the required files from SAP Service Marketplace at http
servicesapcomswdc using the SP Stack Application You use the Maintenance Optimize
only to approve the packages which is a prerequisite for the download
Automatic Calculation
The Maintenance Optimizer supports the download of a consistent queue that includes all
necessary Support Packages and enhancement packages In addition SAP Solution Manager
calculates a valid import queue for the selected SAP system and generates the enhancement
package stack configuration file that you require for the installation
As a prerequisite the system that you want to update needs to be maintained correctly in
SAP Solution Manager System Landscape As the Maintenance Optimizer uses this data for
the calculation it is crucial that the data is up-to-date In addition the SAP Solution Manager
system requires a Minimum Support Package level (see below)
Planing PhaseStep Description Documentation
Hardware amp Software Prerequisites
Check which platforms are supported for your target release (OSDB dependencies)
Product Availability Matrix (PAM) at httpservicesapcompam
Check which hardware sizing is required for your target release
Sizing information at httpservicesapcomsizing
Solution Manager Prerequisites
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of the required software packages you have to make sure that your SAP Solution Manager system has the required Support Package levelAt least SAP Solution Manager 70 EHP1 Support Package Stack 17 is required We recommend to use SAP Solution Manager 70 EHP1 Support Package Stack 23Check if you need to do an update or upgrade of your SAP Solution ManagerMake sure that you run the guided procedure SOLMAN_SETUP after every installation or update of SAP Solution Manager and that it completes successfully
For upgrades from source release SAP Solution Manager 31 and 32Upgrade Guide ndash SAP Solution Manager 70 incl Enhancement Package 1For updates from SAP Solution Manager 70Update Guide SAP Enhancement Package 1 for SAP Solution Manager 70Follow-up activities after an Support Package Stack update or enhancement package updateSolution Operations Guide ndash SAP Solution Manager 70 EHP1 section Software Change Management All guides are available at http
servicesapcom instguides SAP Components SAP Solution Manager -gt Release 70 EHP 1
Implementation PhaseStep Description Documentation
1Solution Manager Preparation
Configure the SAP Solution Manager Maintenance Optimizer
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of software packages make sure your
Configuration of Maintenance Optimizer http
helpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Change Request Management and Change ControlMaintenance Optimizer
Prerequisites
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 2956
Implementation PhaseStep Description Documentation
system landscape data in SAP Solution Manager is maintained correctlyLandscape Verification 10 which is an add-on to SAP Solution Manager can support you in maintaining your system landscape data The use of this tool is optional
Landscape Verification http
wwwsdnsapcom irj
sdn alm-update-
management link Landscape Verification under Related Areas on Upgrade and Update Management (in the right column)
SAP Note 1468605 (Installation of Landscape Verification)
Maintaining System Landscape Information [page 47]Note that the information provided in this section is based on SAP Solution Manager 70 EHP1 SP23
2System Preparation
Prepare your system as described in the documentation for example perform OS DB specific preparations and the PI-specific preparations
Update Guide ndash Update of SAP Systems with Software Update Manager sections Planning and Preparation
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
3Software Download
Select and download the software packages in either of the following ways Automatic calculation Create
a maintenance transaction in the Maintenance Optimizer and choose the Calculate Files Automatically option
Manual Selection Create a maintenance transaction in the Maintenance Optimizer and choose the Select Files Manually option You then can select the files manually using the SP Stack application in SAP Service Marketplace
NOTE
You have to download the stack configuration file manually after you have selected all files in the SP Stack
httphelpsapcom SAP Solutions SAP Solution Manager
SAP Solution Manager 70 EHP1 ltSPgtChange Request Management and
Change Control Maintenance Optimizer Maintenance Procedure Scenarios
For information about the automatic calculation see Maintenance Transaction with Installation of an Enhancement PackageFor information about the manual selection and approval process see section Approve and Download Files in Download Basket
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
3056 PUBLIC 2011-04-15
Implementation PhaseStep Description Documentation
application Choose Generate Stack XML and save the file
4Enhancement Package Installation
Run Software Update Manager to update your system with the selected software packages
Update Guide ndash Update of SAP Systems with Software Update Manager
5Follow-Up Steps
Perform technical and PI-specific follow-up activities after the enhancement package installation is done
Update Guide ndash Update of SAP Systems with Software Update Manager section Follow-Up Activities
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
6Configuration
Configure newly installed enhancement package functions using SAP Solution Manager content
See Systems with Usage Types [page 16] section Configuration of Systems with Usage Types
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 3156
This page is left blank for documents that are printed on both sides
5 System Landscape
51 Planning Your System Landscape
The installable software units that make up your system landscape depend on the functions that you
want to implement For information about the features see systems [page 16] standalone engines [page 19]
and clients [page 21]
In addition you have to determine the required shared services [page 35] (such as SAP Solution Manager
or SAP NetWeaver Administrator) that run on central systems in your system landscape and the
landscape aspects relevant for their implementation
In the following you will find general information that you should consider when planning your system
landscape
Sizing
You have to map systems and standalone engines to hosts after you have a clear picture of the following
Which systems and standalone engines you require
How many systems you require and how you want to use each of these systems
NOTE
No general guideline can be given for the sizing of your landscape since this relies heavily on your
requirements You should therefore perform this task together with your hardware partner and
your technical consultant
For information about sizing your systems you can use the following information sources
Your first point of reference is the Quick Sizer
SAP built the Quick Sizer as an online sizing questionnaire Internet application in close cooperation
with its hardware partners This tool delivers general sizing categories based on your volume load
estimates The results provide an objective basis for sizing independent of platform and
configuration
For more information see SAP Service Marketplace at
httpservicesapcomsizing for the SAP NetWeaver PI 71 sizing guide available under
Sizing Guidelines Business Suite amp Services
httpservicesapcomquicksizer for more information and access to the tool itself
Also consider the following important aspects concerning sizing
High availability
5 System Landscape
51 Planning Your System Landscape
2011-04-15 PUBLIC 3356
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Technical Infrastructure High Availability
Unicode
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Internationalization
Contact your hardware partner to find out the appropriate number of sized hosts
The platform-independent abstract results of the Quick Sizer can be used by any of our hardware
partners to create a concrete offer SAP itself does not make any hardware recommendations the
responsibility for sizing and detailed hardware configuration lies with the hardware partners
Figure 6 Example of Mapping of Systems and Standalone Engines to Three Hosts
NOTE
Optionally you could also distribute single systems to multiple hosts For example you could
decide to install the database instance of an SAP system on a separate host for performance
reasons or distribute other system instances to achieve high availability
To provide a mapping that fits your required functions and performance your hardware partner
and your technical consultant have to identify the number of required instances of SAP NetWeaver
find out how to distribute these instances to hosts and what functions will run on which instance
Therefore the hardware partner and the technical consultant have to consider many different
aspects such as
Number of required SAPS (SAP Application Benchmark Performance Standard) for each
system (provided by Quick Sizer)
Landscape-relevant aspects concerning security For more information see the SAP Security
Guide in the SAP Library [page 12] at Administratoracutes Guide Security Guide
Landscape-relevant aspects concerning scalability high availability operation and software
life-cycle management
5 System Landscape
51 Planning Your System Landscape
3456 PUBLIC 2011-04-15
For more information about relevant aspects for the mapping of systems to hosts see the document
Technical Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
Scaling and Distribution Options
You may need to design your system landscape for a large number of users SAP NetWeaver PI offers
you different means of scalability The following list provides you with some examples
You could install multiple systems of one type and use them for different purposes
You could scale every system by installing dialog instances or by distributing the database instance
For more information about distribution options on the instance level see the Technical
Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
For every SAP system you could additionally install Web Dispatcher For more information see
the SAP Library [page 12] at FunctionndashOriented View Application Server Infrastructure SAP Web
Dispatcher
You could further distribute certain standalone engines ndash for example Search and Classification
(TREX) is based on a flexible architecture that supports a distributed installation For more
information see the Technical Infrastructure Guide ndash SAP NetWeaver PI 71 available in SAP Service
Marketplace at httpservicesapcominstallNWPI71
52 Shared Services
You normally run shared services on central systems in your system landscape The following features
could be used for SAP NetWeaver Process Integration to realize shared services
SAP Solution Manager
Used to implement train test maintain monitor control change and manage incidents of your
SAP solution system landscape (open end-to-end application management)
As of SAP Solution Manager (70) 40 Support Package 15 SAP Solution Manager has become the
platform for SAPs end-to-end solution operations strategy Functions for complete application
management has been combined with administrative tools and has been merged in newly created
role based work centers
NOTE
Be aware that you require an SAP Solution Manager system to install or upgrade to SAP
NetWeaver 70 and higher An SAP Solution Manager system is required to generate the SAP
Solution Manager key needed during the installation or upgrade process Without this key
the installation or upgrade process cannot continue
For SAP NetWeaver Process Integration you require SAP Solution Manager 70
For more information see SAP Note 805390
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3556
Solution Manager Diagnostics
An integral part of SAP Solution Manager that is running as a Java application on the Java stack of
SAP Solution Manager 70 Solution Manager Diagnostics is used to analyze the root cause of
incidents in your landscape in an efficient and safe way Before Go-Live Solution Manager
Diagnostics has to be set up and made accessible remotely
SAP NetWeaver Administrator
SAP NetWeaver Administrator is the central administration component which is used for
monitoring and administering Java applications It is included in SAP NetWeaver systems with AS
Java
SAP NetWeaver Administrator exists in the following flavors
A local mode which runs out of the box and which focuses on administrating the underlying
SAP NetWeaver AS Java
NOTE
For a SAP NetWeaver PI 71 it has a special role which you need to activate using a
configuation wizard
A central mode which has to be configured before use and which deals with the system
landscape management
SAP has decided to merge the central mode of SAP NetWeaver Administrator into the new work
centers available as of SAP Solution Manager 70 SP 15 Thus it can be used in an administrative
context together with non-Java-based administration tools Although the central mode of SAP
NetWeaver Administrator will be still available for some time SAP will not develop this tool any
further SAP focuses on optimizing the administrative work centers of SAP Solution Manager
instead
The local mode of SAP NetWeaver Administrator stays untouched It is available for current and
future releases of SAP NetWeaver
SAP Central Process Scheduling by Redwood
SAP Central Process Scheduling application by Redwood enables central job scheduling and job
monitoring of current and old releases of AS ABAP systems (as of Basis Release 31) This application
is fully integrated in SAP NetWeaver Depending on the business needs SAP business applications
are the initial trigger for scheduled activities You can now manage jobs and job chains conveniently
using a graphical user interface
System Landscape Directory
The System Landscape Directory is the central directory of system landscape information relevant
for the management of your software life-cycle It contains a description of your system landscape
(that is software components that are currently installed) and a repository of software components
that can theoretically be installed in your landscape (such as the software components available
from SAP)
Adaptive Computing Controller
5 System Landscape
52 Shared Services
3656 PUBLIC 2011-04-15
The Adaptive Computing Controller enables users to control an adaptive computing landscape
from a single point through observation operation and dynamic resource distribution With
adaptive computing hardware software and system services are able to adapt to changing business
needs In the Adaptive Computing Controller the run-time data of logical and physical landscapes
can be monitored application services can be startedstoppedrelocated and hardware resources
can be assigned to application services The operation can also be mass executed and be planned as
tasks to be executed
For more information about the installation of the Adaptive Computing Controller tool see the
document Installation Guide ndash Adaptive Computing Controller in SAP NetWeaver 71 available on SAP Service
Marketplace at httpservicesapcominstallNWPI71
For more information about Adaptive Computing in general see httpsdnsapcomirj
sdnadaptive
521 Use Cases
You can use the applications and tools described above for use cases that are normally performed
centrally The following sections describe these use cases
5211 End-to-End Solution Operations
Running business applications through their complete life-cycle is a challenge Therefore SAP has
started the Run SAP methodology for implementing End-to-End Solution Operations Based on a set
of SAP standards a roadmap and a package for training and certification Run SAP helps customers to
facilitate End-to-End Solution Operations
You can download the SAP standards for Solution Operations from SAP Service Marketplace at http
servicesapcomsupportstandards They describe roles customers typically have in their IT
environment For optimal role support SAP has grouped existing and new functions in SAP Solution
Manager work centers as of SAP Solution Manager 70 Support Package 15 Operations aspects are fully
covered by adding administrative functions for SAP NetWeaver as well Work centers are ABAP Web
Dynpro-based applications They offer the following advantages
Easy to use similar look and feel
Context transfer while jumping from one work center into another
Logical grouping of tools for a certain area
Simple authorization concept
Easy to expand
Each IT role belongs to one or more work centers For instance the Technical Administrator IT role is
covered by the work centers for System Monitoring System Administration and Landscape Management
The following work centers are available
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3756
Business Process Operations
Change Management
Root Cause Analysis
Implementation Upgrade
Incident Management
Test Management
Job Management
System Landscape Management
Solution Documentation Assistant
SAP Engagement and Service Delivery
SAP Solution Manager Administration
System Administration
System Monitoring
My Home is the central point of access to all important data of almost all work centers in SAP Solution
Manager
5212 Support Infrastructure
A key requirement for effective support of IT solutions is the ability to perform root cause analysis with
speed and efficiency
With SAP Solution Manager SAP has long had an infrastructure in place for its ABAP applications that
efficiently supports SAP solutions This helps ensure the high availability and smooth running of
business processes For more information see the SAP Solution Manager section
With Solution Manager Diagnostics this knowledge has been extended to Java applications If for
example homegrown Java applications cause instability Solution Manager Diagnostics helps trace the
cause to eradicate the problem rapidly Solution Manager Diagnostics is fully integrated into SAP
Solution Manager 70 Solution Manager Diagnostics also contains two third-party tools CArsquos Wily
Introscopereg for measuring performance as well as troubleshooting problems of the Java EE Engine
and applications running on it and Mercury Loadrunnerreg which enables SAP Support to produce a
defined load in the SAP solution landscape remotely For more information see Solution Manager
Diagnostics [page 43]
The support infrastructure provides SAP Support with safe access to your productive landscape for safe
root cause analysis so ensuring that SAP Support does not change your landscape inadvertently You
require a support infrastructure to run SAP NetWeaver
The following figure shows the overall infrastructure including SAP NetWeaver administration tools
that are used by administrators or operators at the customer site
5 System Landscape
52 Shared Services
3856 PUBLIC 2011-04-15
Landscape Aspects
If you use SAP NetWeaver Process Integration 71 productively besides SAP Solution Manager (as a
central support platform) you have to set up Solution Manager Diagnostics for supportability reasons
Implementation Sequence
For information about the implementation of the support infrastructure see the document Master
Guide ndash SAP Solution Manager 70 available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution Manager ltReleasegt
5213 Collection of Landscape Data
Amongst other applications and services the support infrastructure and the SAP NetWeaver
administration tools rely on system landscape data
For SAP NetWeaver PI 71 you have to run non-ABAP components in your solution landscape
Therefore the System Landscape Directory is mandatory The landscape data that is automatically
gathered by the System Landscape Directory is replicated to SAP Solution Manager There are several
topology options for the System Landscape Directory They offer different grades of availability
administration and operation effort
For more information see the System Landscape Directory section
5214 Authentication and Single Sign-On
Before implementing your system landscape plan how to implement authentication and how to
integrate different systems into a Single Sign-On landscape Single Sign-On reduces complexity for end
users saving them valuable time while also reducing administration effort for resetting passwords
thereby contributing to TCO reduction
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
5215 Integrated User and Access Management
In a system landscape containing a combination of ABAP and Java components we recommend that
you integrate your user and access management so that you can use the same user data across different
systems administer this data centrally and control access to data SAPs mature fine-grained
authorization concept allows detailed control of access rights SAP NetWeaver provides both ABAP and
Java-based user management solutions The user management solution that you use to administer
your user data depends on factors such as the type of systems that are running in your landscape
If you want to use central user administration we recommend that you run it in a non-production
system If you do not have a central user administration yet you can for example realize it in the SAP
Solution Manager system
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3956
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
522 Examples for the Overall System Landscape of Shared Services
In this section we provide examples of how shared services can be set up depending on the system
landscape they are intended for The following examples aggregate the landscape aspects given in the
Use Cases section
NOTE
The following sections and the figure mostly do not show information about the life-cycle of
shared services For example you may also need a development and testquality assurance system
for SAP Solution Manager You should consider this aspect in addition to the information given
in this section based on your requirements
Small and MediumndashSized Customer Landscapes with Java
As you use Java productively for SAP NetWeaver PI 71 besides SAP Solution Manager you have to set
up additional components for optimal monitoring administration and support Solution Manager
Diagnostics and the central mode of SAP NetWeaver Administrator are already fully integrated into
SAP Solution Manager 70 as the central operations hub For SAP Process Integration you must also
set up SAP NetWeaver Administrator with a special role
We recommend that you do not install SAP Central Process Scheduling in the SAP Solution Manager
system You have to set up and operate the system which hosts your productive scheduler as a mission
critical system
In the SAP Solution Manager system you should set up a local System Landscape Directory in addition
to a central runtime System Landscape Directory This way you have a clear separation between your
management system (SAP Solution Manager) and managed systems in your landscape In addition
SAP Solution Manager then does not rely on a System Landscape Directory running in the production
environment For this setup configure the SLD data suppliers of your SAP Solution Manager system
to send data to the central runtime System Landscape Directory In addition configure automatic
bridge forwarding from your runtime System Landscape Directory to the local System Landscape
Directory For more information see the Planning Guide - System Landscape Directory
If you want to use a central system for Adobe Document Services we recommend that you install a
dedicated system for this purpose in your production environment For detailed information about
the sizing of the system for the different use cases see the Sizing Guide for Adobe Document Services at
SAP Service Marketplace at httpservicesapcomsizing Sizing Guidelines Solutions amp
Platform
We recommend that you start with this centralized SAP Solution Manager approach as depicted in the
following figure
5 System Landscape
52 Shared Services
4056 PUBLIC 2011-04-15
Figure 7 Single SAP Solution Manager Landscape
Large Customer Landscapes with Java
Large customers who have environments in their landscape that are large and distributed administered
by different groups or separated for security reasons can consider a distributed operations setup In
addition to the centralized setup described for small- and medium-sized customers above large
customers can put parts of the central management functions on extra hosts or systems for performance
or policy reasons You have the following options for a distributed setup
You may set up an extra system or client for Central User Administration (CUA)
The Change and Transport System (CTS) can run on an extra system However it is not
performance- or data-intensive
You may set up an extra system for central CCMS monitoring Depending on the customizing
and on the landscape size central CCMS may generate a lot of system load You can connect a
separate central CCMS to SAP Solution Manager for displaying alerts in the alert inbox of the System
Monitoring work center
You can use a separate SAP NetWeaver 70 system with usage type BI together with SAP Solution
Manager This may make sense with respect to the amount of landscape management data that is
stored for reporting purposes The amount of data strongly depends on the data granularity
storage time frame and landscape size
You can easily put Wily Introscope Enterprise Manager on an separate host
Other aspects described above for small- and medium-customers (such as the setup of the System
Landscape Directory) are also valid for large customers
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4156
523 Feature Details
This section provides further information about the features described above
5231 SAP Solution Manager
SAP provides you with SAP Solution Manager as the strategic application management platform and
to enable the collaboration between you and SAP You need to install at least one productive SAP
Solution Manager in your system landscape To ensure the availability of this application management
platform an SAP Solution Manager system is technically required to install or upgrade to SAP
NetWeaver 70 or higher If you are already using SAP Solution Manager you can also use it to manage
the solution you build with SAP NetWeaver In this case we highly recommend that you update SAP
Solution Manager to the latest version
As of SAP Solution Manager 70 SP15 you can use the newly created work centers
NOTE
During the SAP system installation or upgrade process you are prompted to enter the SAP
Solution Manager key An SAP Solution Manager system is required to generate this key Without
this key the installation or upgrade process cannot continue
You may generate all needed keys for your entire system landscape (development quality
assurance and production system) in one SAP Solution Manager system In case you plan to install
several solution landscapes (for example in different countries) one SAP Solution Manager
system is still sufficient
For more information see SAP Note 805390
It is possible to install multiple SAP Solution Managers If you do so they should host separate business
solutions
If you want to reduce the risk of unavailability you should not install SAP Solution Manager as a central
component Instead you can operate a 2-system-landscape with both a test and production
environment of SAP Solution Manager (especially if you are using time-critical functions like Support
Desk) If you also develop your own content a 3-system-landscape with a development test and
production environment is recommended
For more information about SAP Solution Manager see the following table
Topic Where to Find More Information
System infrastructure scenarios installation and configuration of SAP Solution Manager
Master Guide ndash SAP Solution Manager available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution ManagerltReleasegt
Benefits and usage scenarios SAP Solution Manager ndash Learning Maps available on SAP Service Marketplace at http
5 System Landscape
52 Shared Services
4256 PUBLIC 2011-04-15
Topic Where to Find More Informationservicesapcomrkt-solman or https
servicesapcomsolutionmanager
Additional information See SAP Service Marketplace at http
servicesapcomsolutionmanager
5232 Solution Manager Diagnostics
Solution Manager Diagnostics provides efficient and safe root-cause analysis of incidents in customer
solutions powered by SAP NetWeaver It can help monitor on operating systems databases Java
application activities performance and logs It also supports the reporting of software and
configuration changes that can lead to malfunctions and errors
You must run one Solution Manager Diagnostics within your SAP solution landscape if you run
applications based on SAP NetWeaver systems with usage type AS Java Agents are responsible for
delivering the data from all productive hosts within your system landscape to the Solution Manager
Diagnostics system
CAUTION
SAP Support performs root-cause analysis on incoming incidents with Solution Manager
Diagnostics Not installing and configuring this support infrastructure results in a dramatically
reduced service level
Solution Manager Diagnostics is fully integrated into SAP Solution Manager 70
Solution Manager Diagnostics also contains Wily Introscope (Display Server and Agent part) for
measuring performance as well as to troubleshoot problems of Non-ABAP applications Wily Introscope
is heavily used for troubleshooting applications running on AS Java
SAP has signed a distribution agreement for Wily Introscope SAP customers are allowed to use this
tool in a preconfigured way
For more information about Solution Manager Diagnostics and an FAQ list see SAP Service Marketplace
at httpservicesapcomdiagnostics
5233 System Landscape Directory
The System Landscape Directory (SLD) of SAP NetWeaver is the central directory of system landscape
information relevant for the management of your software life-cycle
NOTE
Note that the abbreviation SLD is not intended to define a product since the System Landscape
Directory is part of SAP NetWeaver This abbreviation is solely intended to improve readability
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4356
The System Landscape Directory contains a description of your system landscape (that is software
components that are currently installed) and a repository of software components that can
theoretically be installed in your landscape (such as the software components available from SAP)
Since this data gets updated automatically the System Landscape Directory provides reliable and up-
to-date system landscape information with as little effort for you as possible In this way the System
Landscape Directory acts as a central information provider for SAP and third-party tools that use this
data to deliver the services you need to keep your landscape up and running
For the System Landscape Directory as part of an SAP NetWeaver PI 71 landscape consider the following
aspects
Part of SAP NetWeaver PI 71 is a new version of the System Landscape Directory It is automatically
included in every SAP NetWeaver 71 system with usage type AS Java It offers enhanced functions
such as a full automatic synchronization mechanism for all data stored in it That is both data
delivered by data suppliers and data entered or changed manually in the System Landscape
Directory can be synchronized automatically This synchronization offers the following
A fully automated mechanism so no user interaction is required and conflicts are resolved
automatically
Asynchronous propagation of information so some nodes may be down temporarily
Communication over HTTP protocol
Uni- and bi-directional synchronization
Depending on your use case the full automatic synchronization could significantly reduce manual
synchronization effort
For SAP NetWeaver PI 71 the configuration of the system landscape directory and its data suppliers
is already included in the standard implementation procedure with SAPinst For existing systems
you only have to perform some quick and easy configuration actions to start operating the system
landscape directory server in an AS Java system
For SAP NetWeaver PI 71 you have the following options concerning SLD
Option 1
Run SAP NetWeaver PI 71 against an existing SLD running on SAP NetWeaver 70 We only
recommend this for upgrades from SAP NetWeaver 70 if you have a central SLD in operation
not running on one of your PI systems
Option 2
Use the SLD included in an SAP NetWeaver PI 71 system We recommend this option for new
installations and upgrades from older releases than SAP NetWeaver 70 due to the enhanced
functions and improved performance of SLD 71
NOTE
If you already have a central SLD running on SAP NetWeaver 70 in operation you could run
two SLD versions in parallel ndash SLD running on SAP NetWeaver 71 for your PI systems and
SLD running on SAP NetWeaver 70 for all other systemsuse cases This way your SAP
5 System Landscape
52 Shared Services
4456 PUBLIC 2011-04-15
NetWeaver PI 71 systems would benefit from the new features while it would be easy to set
up and operate such an SLD landscape For this purpose you could use the new fully
automatic synchronization This feature enables the automatic forwarding of all SLD data
from an SLD running on SAP NetWeaver 70 to an SLD running on SAP NetWeaver 71 As a
result there is no need to adapt most existing systems as their SLD data suppliers could still
send their data to the central SLD In brief the following steps would be required
1 Put SLD in a PI system into operation (part of standard implementation procedure)
2 Configure PI systems to use the new SLD (part of standard implementation procedure
for new PI systems)
3 Set up the fully automatic synchronization from your old SLD to your new SLD
As soon as an upgrade or an installation of a standalone AS Java 71 system is available you
could move your central SLD also to SAP NetWeaver 71 Then you could optionally shift
your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems
Figure 8
We recommend that you use a Domain Name System (DNS) alias so that you are able to switch to
another System Landscape Directory easily For example if customers build a new landscape they
normally start with a sandbox environment Over time more and more environments are set up
Once the production environment is in place move the System Landscape Directory there To do
this you can configure a new System Landscape Directory in the production environment
synchronize it with the old System Landscape directory and switch to the new one
Topology
Apart from the considerations above the System Landscape Directory offers several topology options
with different grades of availability at the expense of low administration and operation effort There is
no generic rule therefore on how to set up a System Landscape Directory in your system landscape
To find the topology and synchronization strategy for the System Landscape Directory that fits your
requirements concerning the System Landscape Directory availability (and hence the availability of
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4556
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
exchange between your SAP NetWeaver systems and the partner systems Since SAP Partner
Connectivity Kit gets installed in their system landscape it is not shown in the system landscape
figure above
The AS ABAP system acts as an application and service provider For Java Web Services you also
require AS Java In addition you require SAP NetWeaver Developer Studio on the client side as a
development environment
The Web service client can be either an SAP or a non-SAP application For example an AS ABAP
system or a Web browser could act as application or service consumer
You can install SAP Conversion Agent by Informatica in the system with usage type PI or on a host
where SAP Partner Connectivity Kit is installed or on a host where neither usage type PI nor SAP
Partner Connectivity Kit is installed
43 Implementation Sequence
Procedure
To install this use case perform the steps listed in the following table
StepAction[Corresponding Documentation] Remarks
1 Make sure that you have performed the preparation steps You have planned your system landscape [page 33]
(that is you have decided how many systems you require how you want to use each of these systems and which standalone engines and clients you require)
With the help of your hardware partner you have mapped your systems and standalone engines to properly sized hosts
You have planned and installed shared services [page 35]
2 Installation of system with usage type PI (includes the installation of AS ABAP and AS Java)
NOTE
For usage type PI a Unicode installation is mandatory
[Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt]
If you want to use the features of enhancement package 1 use the direct installation of SAP NetWeaver PI 71 including enhancement package 1
Make sure that you perform the configuration steps as described in the installation guide For certain usage types configuration tasks can be applied by the configuration wizard These configuration tasks as well as any additional configuration steps for your use case are listed in SAP Solution Manager For more information
4 SOA-Based Integration Use Case
43 Implementation Sequence
2011-04-15 PUBLIC 2756
StepAction[Corresponding Documentation] Remarks
see the Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt
3 Install the Adapter Engine (Java SE) engines if required[Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
4 To integrate small business partners and subsidiaries the business partners or subsidiaries install SAP Partner Connectivity Kit running on AS Java with parts of usage type PI in the business partners or subsidiarys system landscape[Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
5 Install SAP Conversion Agent by Informatica if required[SAP Library [page 12] at Function-Oriented View Process Integration SAP Conversion Agent by Informatica Deploying and Using Conversion Agent ]
6 Installation of clients SAP GUI
[Installation Guide ndash SAP Front End]
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
The process sequences give a comprehensive overview of the steps relevant for the enhancement
package installation on an existing SAP NetWeaver PI 71 system
The process sequence is divided into a planning phase and an implementation phase Each step in both
phases contains references to the corresponding documentation to ensure that you can easily find the
information you need
Process
NOTE
To download the enhancement package files and required Support Packages you require the SAP
Solution Manager Maintenance Optimizer You have the following options
Manual Selection
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2856 PUBLIC 2011-04-15
You manually select the required files from SAP Service Marketplace at http
servicesapcomswdc using the SP Stack Application You use the Maintenance Optimize
only to approve the packages which is a prerequisite for the download
Automatic Calculation
The Maintenance Optimizer supports the download of a consistent queue that includes all
necessary Support Packages and enhancement packages In addition SAP Solution Manager
calculates a valid import queue for the selected SAP system and generates the enhancement
package stack configuration file that you require for the installation
As a prerequisite the system that you want to update needs to be maintained correctly in
SAP Solution Manager System Landscape As the Maintenance Optimizer uses this data for
the calculation it is crucial that the data is up-to-date In addition the SAP Solution Manager
system requires a Minimum Support Package level (see below)
Planing PhaseStep Description Documentation
Hardware amp Software Prerequisites
Check which platforms are supported for your target release (OSDB dependencies)
Product Availability Matrix (PAM) at httpservicesapcompam
Check which hardware sizing is required for your target release
Sizing information at httpservicesapcomsizing
Solution Manager Prerequisites
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of the required software packages you have to make sure that your SAP Solution Manager system has the required Support Package levelAt least SAP Solution Manager 70 EHP1 Support Package Stack 17 is required We recommend to use SAP Solution Manager 70 EHP1 Support Package Stack 23Check if you need to do an update or upgrade of your SAP Solution ManagerMake sure that you run the guided procedure SOLMAN_SETUP after every installation or update of SAP Solution Manager and that it completes successfully
For upgrades from source release SAP Solution Manager 31 and 32Upgrade Guide ndash SAP Solution Manager 70 incl Enhancement Package 1For updates from SAP Solution Manager 70Update Guide SAP Enhancement Package 1 for SAP Solution Manager 70Follow-up activities after an Support Package Stack update or enhancement package updateSolution Operations Guide ndash SAP Solution Manager 70 EHP1 section Software Change Management All guides are available at http
servicesapcom instguides SAP Components SAP Solution Manager -gt Release 70 EHP 1
Implementation PhaseStep Description Documentation
1Solution Manager Preparation
Configure the SAP Solution Manager Maintenance Optimizer
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of software packages make sure your
Configuration of Maintenance Optimizer http
helpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Change Request Management and Change ControlMaintenance Optimizer
Prerequisites
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 2956
Implementation PhaseStep Description Documentation
system landscape data in SAP Solution Manager is maintained correctlyLandscape Verification 10 which is an add-on to SAP Solution Manager can support you in maintaining your system landscape data The use of this tool is optional
Landscape Verification http
wwwsdnsapcom irj
sdn alm-update-
management link Landscape Verification under Related Areas on Upgrade and Update Management (in the right column)
SAP Note 1468605 (Installation of Landscape Verification)
Maintaining System Landscape Information [page 47]Note that the information provided in this section is based on SAP Solution Manager 70 EHP1 SP23
2System Preparation
Prepare your system as described in the documentation for example perform OS DB specific preparations and the PI-specific preparations
Update Guide ndash Update of SAP Systems with Software Update Manager sections Planning and Preparation
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
3Software Download
Select and download the software packages in either of the following ways Automatic calculation Create
a maintenance transaction in the Maintenance Optimizer and choose the Calculate Files Automatically option
Manual Selection Create a maintenance transaction in the Maintenance Optimizer and choose the Select Files Manually option You then can select the files manually using the SP Stack application in SAP Service Marketplace
NOTE
You have to download the stack configuration file manually after you have selected all files in the SP Stack
httphelpsapcom SAP Solutions SAP Solution Manager
SAP Solution Manager 70 EHP1 ltSPgtChange Request Management and
Change Control Maintenance Optimizer Maintenance Procedure Scenarios
For information about the automatic calculation see Maintenance Transaction with Installation of an Enhancement PackageFor information about the manual selection and approval process see section Approve and Download Files in Download Basket
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
3056 PUBLIC 2011-04-15
Implementation PhaseStep Description Documentation
application Choose Generate Stack XML and save the file
4Enhancement Package Installation
Run Software Update Manager to update your system with the selected software packages
Update Guide ndash Update of SAP Systems with Software Update Manager
5Follow-Up Steps
Perform technical and PI-specific follow-up activities after the enhancement package installation is done
Update Guide ndash Update of SAP Systems with Software Update Manager section Follow-Up Activities
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
6Configuration
Configure newly installed enhancement package functions using SAP Solution Manager content
See Systems with Usage Types [page 16] section Configuration of Systems with Usage Types
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 3156
This page is left blank for documents that are printed on both sides
5 System Landscape
51 Planning Your System Landscape
The installable software units that make up your system landscape depend on the functions that you
want to implement For information about the features see systems [page 16] standalone engines [page 19]
and clients [page 21]
In addition you have to determine the required shared services [page 35] (such as SAP Solution Manager
or SAP NetWeaver Administrator) that run on central systems in your system landscape and the
landscape aspects relevant for their implementation
In the following you will find general information that you should consider when planning your system
landscape
Sizing
You have to map systems and standalone engines to hosts after you have a clear picture of the following
Which systems and standalone engines you require
How many systems you require and how you want to use each of these systems
NOTE
No general guideline can be given for the sizing of your landscape since this relies heavily on your
requirements You should therefore perform this task together with your hardware partner and
your technical consultant
For information about sizing your systems you can use the following information sources
Your first point of reference is the Quick Sizer
SAP built the Quick Sizer as an online sizing questionnaire Internet application in close cooperation
with its hardware partners This tool delivers general sizing categories based on your volume load
estimates The results provide an objective basis for sizing independent of platform and
configuration
For more information see SAP Service Marketplace at
httpservicesapcomsizing for the SAP NetWeaver PI 71 sizing guide available under
Sizing Guidelines Business Suite amp Services
httpservicesapcomquicksizer for more information and access to the tool itself
Also consider the following important aspects concerning sizing
High availability
5 System Landscape
51 Planning Your System Landscape
2011-04-15 PUBLIC 3356
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Technical Infrastructure High Availability
Unicode
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Internationalization
Contact your hardware partner to find out the appropriate number of sized hosts
The platform-independent abstract results of the Quick Sizer can be used by any of our hardware
partners to create a concrete offer SAP itself does not make any hardware recommendations the
responsibility for sizing and detailed hardware configuration lies with the hardware partners
Figure 6 Example of Mapping of Systems and Standalone Engines to Three Hosts
NOTE
Optionally you could also distribute single systems to multiple hosts For example you could
decide to install the database instance of an SAP system on a separate host for performance
reasons or distribute other system instances to achieve high availability
To provide a mapping that fits your required functions and performance your hardware partner
and your technical consultant have to identify the number of required instances of SAP NetWeaver
find out how to distribute these instances to hosts and what functions will run on which instance
Therefore the hardware partner and the technical consultant have to consider many different
aspects such as
Number of required SAPS (SAP Application Benchmark Performance Standard) for each
system (provided by Quick Sizer)
Landscape-relevant aspects concerning security For more information see the SAP Security
Guide in the SAP Library [page 12] at Administratoracutes Guide Security Guide
Landscape-relevant aspects concerning scalability high availability operation and software
life-cycle management
5 System Landscape
51 Planning Your System Landscape
3456 PUBLIC 2011-04-15
For more information about relevant aspects for the mapping of systems to hosts see the document
Technical Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
Scaling and Distribution Options
You may need to design your system landscape for a large number of users SAP NetWeaver PI offers
you different means of scalability The following list provides you with some examples
You could install multiple systems of one type and use them for different purposes
You could scale every system by installing dialog instances or by distributing the database instance
For more information about distribution options on the instance level see the Technical
Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
For every SAP system you could additionally install Web Dispatcher For more information see
the SAP Library [page 12] at FunctionndashOriented View Application Server Infrastructure SAP Web
Dispatcher
You could further distribute certain standalone engines ndash for example Search and Classification
(TREX) is based on a flexible architecture that supports a distributed installation For more
information see the Technical Infrastructure Guide ndash SAP NetWeaver PI 71 available in SAP Service
Marketplace at httpservicesapcominstallNWPI71
52 Shared Services
You normally run shared services on central systems in your system landscape The following features
could be used for SAP NetWeaver Process Integration to realize shared services
SAP Solution Manager
Used to implement train test maintain monitor control change and manage incidents of your
SAP solution system landscape (open end-to-end application management)
As of SAP Solution Manager (70) 40 Support Package 15 SAP Solution Manager has become the
platform for SAPs end-to-end solution operations strategy Functions for complete application
management has been combined with administrative tools and has been merged in newly created
role based work centers
NOTE
Be aware that you require an SAP Solution Manager system to install or upgrade to SAP
NetWeaver 70 and higher An SAP Solution Manager system is required to generate the SAP
Solution Manager key needed during the installation or upgrade process Without this key
the installation or upgrade process cannot continue
For SAP NetWeaver Process Integration you require SAP Solution Manager 70
For more information see SAP Note 805390
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3556
Solution Manager Diagnostics
An integral part of SAP Solution Manager that is running as a Java application on the Java stack of
SAP Solution Manager 70 Solution Manager Diagnostics is used to analyze the root cause of
incidents in your landscape in an efficient and safe way Before Go-Live Solution Manager
Diagnostics has to be set up and made accessible remotely
SAP NetWeaver Administrator
SAP NetWeaver Administrator is the central administration component which is used for
monitoring and administering Java applications It is included in SAP NetWeaver systems with AS
Java
SAP NetWeaver Administrator exists in the following flavors
A local mode which runs out of the box and which focuses on administrating the underlying
SAP NetWeaver AS Java
NOTE
For a SAP NetWeaver PI 71 it has a special role which you need to activate using a
configuation wizard
A central mode which has to be configured before use and which deals with the system
landscape management
SAP has decided to merge the central mode of SAP NetWeaver Administrator into the new work
centers available as of SAP Solution Manager 70 SP 15 Thus it can be used in an administrative
context together with non-Java-based administration tools Although the central mode of SAP
NetWeaver Administrator will be still available for some time SAP will not develop this tool any
further SAP focuses on optimizing the administrative work centers of SAP Solution Manager
instead
The local mode of SAP NetWeaver Administrator stays untouched It is available for current and
future releases of SAP NetWeaver
SAP Central Process Scheduling by Redwood
SAP Central Process Scheduling application by Redwood enables central job scheduling and job
monitoring of current and old releases of AS ABAP systems (as of Basis Release 31) This application
is fully integrated in SAP NetWeaver Depending on the business needs SAP business applications
are the initial trigger for scheduled activities You can now manage jobs and job chains conveniently
using a graphical user interface
System Landscape Directory
The System Landscape Directory is the central directory of system landscape information relevant
for the management of your software life-cycle It contains a description of your system landscape
(that is software components that are currently installed) and a repository of software components
that can theoretically be installed in your landscape (such as the software components available
from SAP)
Adaptive Computing Controller
5 System Landscape
52 Shared Services
3656 PUBLIC 2011-04-15
The Adaptive Computing Controller enables users to control an adaptive computing landscape
from a single point through observation operation and dynamic resource distribution With
adaptive computing hardware software and system services are able to adapt to changing business
needs In the Adaptive Computing Controller the run-time data of logical and physical landscapes
can be monitored application services can be startedstoppedrelocated and hardware resources
can be assigned to application services The operation can also be mass executed and be planned as
tasks to be executed
For more information about the installation of the Adaptive Computing Controller tool see the
document Installation Guide ndash Adaptive Computing Controller in SAP NetWeaver 71 available on SAP Service
Marketplace at httpservicesapcominstallNWPI71
For more information about Adaptive Computing in general see httpsdnsapcomirj
sdnadaptive
521 Use Cases
You can use the applications and tools described above for use cases that are normally performed
centrally The following sections describe these use cases
5211 End-to-End Solution Operations
Running business applications through their complete life-cycle is a challenge Therefore SAP has
started the Run SAP methodology for implementing End-to-End Solution Operations Based on a set
of SAP standards a roadmap and a package for training and certification Run SAP helps customers to
facilitate End-to-End Solution Operations
You can download the SAP standards for Solution Operations from SAP Service Marketplace at http
servicesapcomsupportstandards They describe roles customers typically have in their IT
environment For optimal role support SAP has grouped existing and new functions in SAP Solution
Manager work centers as of SAP Solution Manager 70 Support Package 15 Operations aspects are fully
covered by adding administrative functions for SAP NetWeaver as well Work centers are ABAP Web
Dynpro-based applications They offer the following advantages
Easy to use similar look and feel
Context transfer while jumping from one work center into another
Logical grouping of tools for a certain area
Simple authorization concept
Easy to expand
Each IT role belongs to one or more work centers For instance the Technical Administrator IT role is
covered by the work centers for System Monitoring System Administration and Landscape Management
The following work centers are available
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3756
Business Process Operations
Change Management
Root Cause Analysis
Implementation Upgrade
Incident Management
Test Management
Job Management
System Landscape Management
Solution Documentation Assistant
SAP Engagement and Service Delivery
SAP Solution Manager Administration
System Administration
System Monitoring
My Home is the central point of access to all important data of almost all work centers in SAP Solution
Manager
5212 Support Infrastructure
A key requirement for effective support of IT solutions is the ability to perform root cause analysis with
speed and efficiency
With SAP Solution Manager SAP has long had an infrastructure in place for its ABAP applications that
efficiently supports SAP solutions This helps ensure the high availability and smooth running of
business processes For more information see the SAP Solution Manager section
With Solution Manager Diagnostics this knowledge has been extended to Java applications If for
example homegrown Java applications cause instability Solution Manager Diagnostics helps trace the
cause to eradicate the problem rapidly Solution Manager Diagnostics is fully integrated into SAP
Solution Manager 70 Solution Manager Diagnostics also contains two third-party tools CArsquos Wily
Introscopereg for measuring performance as well as troubleshooting problems of the Java EE Engine
and applications running on it and Mercury Loadrunnerreg which enables SAP Support to produce a
defined load in the SAP solution landscape remotely For more information see Solution Manager
Diagnostics [page 43]
The support infrastructure provides SAP Support with safe access to your productive landscape for safe
root cause analysis so ensuring that SAP Support does not change your landscape inadvertently You
require a support infrastructure to run SAP NetWeaver
The following figure shows the overall infrastructure including SAP NetWeaver administration tools
that are used by administrators or operators at the customer site
5 System Landscape
52 Shared Services
3856 PUBLIC 2011-04-15
Landscape Aspects
If you use SAP NetWeaver Process Integration 71 productively besides SAP Solution Manager (as a
central support platform) you have to set up Solution Manager Diagnostics for supportability reasons
Implementation Sequence
For information about the implementation of the support infrastructure see the document Master
Guide ndash SAP Solution Manager 70 available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution Manager ltReleasegt
5213 Collection of Landscape Data
Amongst other applications and services the support infrastructure and the SAP NetWeaver
administration tools rely on system landscape data
For SAP NetWeaver PI 71 you have to run non-ABAP components in your solution landscape
Therefore the System Landscape Directory is mandatory The landscape data that is automatically
gathered by the System Landscape Directory is replicated to SAP Solution Manager There are several
topology options for the System Landscape Directory They offer different grades of availability
administration and operation effort
For more information see the System Landscape Directory section
5214 Authentication and Single Sign-On
Before implementing your system landscape plan how to implement authentication and how to
integrate different systems into a Single Sign-On landscape Single Sign-On reduces complexity for end
users saving them valuable time while also reducing administration effort for resetting passwords
thereby contributing to TCO reduction
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
5215 Integrated User and Access Management
In a system landscape containing a combination of ABAP and Java components we recommend that
you integrate your user and access management so that you can use the same user data across different
systems administer this data centrally and control access to data SAPs mature fine-grained
authorization concept allows detailed control of access rights SAP NetWeaver provides both ABAP and
Java-based user management solutions The user management solution that you use to administer
your user data depends on factors such as the type of systems that are running in your landscape
If you want to use central user administration we recommend that you run it in a non-production
system If you do not have a central user administration yet you can for example realize it in the SAP
Solution Manager system
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3956
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
522 Examples for the Overall System Landscape of Shared Services
In this section we provide examples of how shared services can be set up depending on the system
landscape they are intended for The following examples aggregate the landscape aspects given in the
Use Cases section
NOTE
The following sections and the figure mostly do not show information about the life-cycle of
shared services For example you may also need a development and testquality assurance system
for SAP Solution Manager You should consider this aspect in addition to the information given
in this section based on your requirements
Small and MediumndashSized Customer Landscapes with Java
As you use Java productively for SAP NetWeaver PI 71 besides SAP Solution Manager you have to set
up additional components for optimal monitoring administration and support Solution Manager
Diagnostics and the central mode of SAP NetWeaver Administrator are already fully integrated into
SAP Solution Manager 70 as the central operations hub For SAP Process Integration you must also
set up SAP NetWeaver Administrator with a special role
We recommend that you do not install SAP Central Process Scheduling in the SAP Solution Manager
system You have to set up and operate the system which hosts your productive scheduler as a mission
critical system
In the SAP Solution Manager system you should set up a local System Landscape Directory in addition
to a central runtime System Landscape Directory This way you have a clear separation between your
management system (SAP Solution Manager) and managed systems in your landscape In addition
SAP Solution Manager then does not rely on a System Landscape Directory running in the production
environment For this setup configure the SLD data suppliers of your SAP Solution Manager system
to send data to the central runtime System Landscape Directory In addition configure automatic
bridge forwarding from your runtime System Landscape Directory to the local System Landscape
Directory For more information see the Planning Guide - System Landscape Directory
If you want to use a central system for Adobe Document Services we recommend that you install a
dedicated system for this purpose in your production environment For detailed information about
the sizing of the system for the different use cases see the Sizing Guide for Adobe Document Services at
SAP Service Marketplace at httpservicesapcomsizing Sizing Guidelines Solutions amp
Platform
We recommend that you start with this centralized SAP Solution Manager approach as depicted in the
following figure
5 System Landscape
52 Shared Services
4056 PUBLIC 2011-04-15
Figure 7 Single SAP Solution Manager Landscape
Large Customer Landscapes with Java
Large customers who have environments in their landscape that are large and distributed administered
by different groups or separated for security reasons can consider a distributed operations setup In
addition to the centralized setup described for small- and medium-sized customers above large
customers can put parts of the central management functions on extra hosts or systems for performance
or policy reasons You have the following options for a distributed setup
You may set up an extra system or client for Central User Administration (CUA)
The Change and Transport System (CTS) can run on an extra system However it is not
performance- or data-intensive
You may set up an extra system for central CCMS monitoring Depending on the customizing
and on the landscape size central CCMS may generate a lot of system load You can connect a
separate central CCMS to SAP Solution Manager for displaying alerts in the alert inbox of the System
Monitoring work center
You can use a separate SAP NetWeaver 70 system with usage type BI together with SAP Solution
Manager This may make sense with respect to the amount of landscape management data that is
stored for reporting purposes The amount of data strongly depends on the data granularity
storage time frame and landscape size
You can easily put Wily Introscope Enterprise Manager on an separate host
Other aspects described above for small- and medium-customers (such as the setup of the System
Landscape Directory) are also valid for large customers
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4156
523 Feature Details
This section provides further information about the features described above
5231 SAP Solution Manager
SAP provides you with SAP Solution Manager as the strategic application management platform and
to enable the collaboration between you and SAP You need to install at least one productive SAP
Solution Manager in your system landscape To ensure the availability of this application management
platform an SAP Solution Manager system is technically required to install or upgrade to SAP
NetWeaver 70 or higher If you are already using SAP Solution Manager you can also use it to manage
the solution you build with SAP NetWeaver In this case we highly recommend that you update SAP
Solution Manager to the latest version
As of SAP Solution Manager 70 SP15 you can use the newly created work centers
NOTE
During the SAP system installation or upgrade process you are prompted to enter the SAP
Solution Manager key An SAP Solution Manager system is required to generate this key Without
this key the installation or upgrade process cannot continue
You may generate all needed keys for your entire system landscape (development quality
assurance and production system) in one SAP Solution Manager system In case you plan to install
several solution landscapes (for example in different countries) one SAP Solution Manager
system is still sufficient
For more information see SAP Note 805390
It is possible to install multiple SAP Solution Managers If you do so they should host separate business
solutions
If you want to reduce the risk of unavailability you should not install SAP Solution Manager as a central
component Instead you can operate a 2-system-landscape with both a test and production
environment of SAP Solution Manager (especially if you are using time-critical functions like Support
Desk) If you also develop your own content a 3-system-landscape with a development test and
production environment is recommended
For more information about SAP Solution Manager see the following table
Topic Where to Find More Information
System infrastructure scenarios installation and configuration of SAP Solution Manager
Master Guide ndash SAP Solution Manager available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution ManagerltReleasegt
Benefits and usage scenarios SAP Solution Manager ndash Learning Maps available on SAP Service Marketplace at http
5 System Landscape
52 Shared Services
4256 PUBLIC 2011-04-15
Topic Where to Find More Informationservicesapcomrkt-solman or https
servicesapcomsolutionmanager
Additional information See SAP Service Marketplace at http
servicesapcomsolutionmanager
5232 Solution Manager Diagnostics
Solution Manager Diagnostics provides efficient and safe root-cause analysis of incidents in customer
solutions powered by SAP NetWeaver It can help monitor on operating systems databases Java
application activities performance and logs It also supports the reporting of software and
configuration changes that can lead to malfunctions and errors
You must run one Solution Manager Diagnostics within your SAP solution landscape if you run
applications based on SAP NetWeaver systems with usage type AS Java Agents are responsible for
delivering the data from all productive hosts within your system landscape to the Solution Manager
Diagnostics system
CAUTION
SAP Support performs root-cause analysis on incoming incidents with Solution Manager
Diagnostics Not installing and configuring this support infrastructure results in a dramatically
reduced service level
Solution Manager Diagnostics is fully integrated into SAP Solution Manager 70
Solution Manager Diagnostics also contains Wily Introscope (Display Server and Agent part) for
measuring performance as well as to troubleshoot problems of Non-ABAP applications Wily Introscope
is heavily used for troubleshooting applications running on AS Java
SAP has signed a distribution agreement for Wily Introscope SAP customers are allowed to use this
tool in a preconfigured way
For more information about Solution Manager Diagnostics and an FAQ list see SAP Service Marketplace
at httpservicesapcomdiagnostics
5233 System Landscape Directory
The System Landscape Directory (SLD) of SAP NetWeaver is the central directory of system landscape
information relevant for the management of your software life-cycle
NOTE
Note that the abbreviation SLD is not intended to define a product since the System Landscape
Directory is part of SAP NetWeaver This abbreviation is solely intended to improve readability
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4356
The System Landscape Directory contains a description of your system landscape (that is software
components that are currently installed) and a repository of software components that can
theoretically be installed in your landscape (such as the software components available from SAP)
Since this data gets updated automatically the System Landscape Directory provides reliable and up-
to-date system landscape information with as little effort for you as possible In this way the System
Landscape Directory acts as a central information provider for SAP and third-party tools that use this
data to deliver the services you need to keep your landscape up and running
For the System Landscape Directory as part of an SAP NetWeaver PI 71 landscape consider the following
aspects
Part of SAP NetWeaver PI 71 is a new version of the System Landscape Directory It is automatically
included in every SAP NetWeaver 71 system with usage type AS Java It offers enhanced functions
such as a full automatic synchronization mechanism for all data stored in it That is both data
delivered by data suppliers and data entered or changed manually in the System Landscape
Directory can be synchronized automatically This synchronization offers the following
A fully automated mechanism so no user interaction is required and conflicts are resolved
automatically
Asynchronous propagation of information so some nodes may be down temporarily
Communication over HTTP protocol
Uni- and bi-directional synchronization
Depending on your use case the full automatic synchronization could significantly reduce manual
synchronization effort
For SAP NetWeaver PI 71 the configuration of the system landscape directory and its data suppliers
is already included in the standard implementation procedure with SAPinst For existing systems
you only have to perform some quick and easy configuration actions to start operating the system
landscape directory server in an AS Java system
For SAP NetWeaver PI 71 you have the following options concerning SLD
Option 1
Run SAP NetWeaver PI 71 against an existing SLD running on SAP NetWeaver 70 We only
recommend this for upgrades from SAP NetWeaver 70 if you have a central SLD in operation
not running on one of your PI systems
Option 2
Use the SLD included in an SAP NetWeaver PI 71 system We recommend this option for new
installations and upgrades from older releases than SAP NetWeaver 70 due to the enhanced
functions and improved performance of SLD 71
NOTE
If you already have a central SLD running on SAP NetWeaver 70 in operation you could run
two SLD versions in parallel ndash SLD running on SAP NetWeaver 71 for your PI systems and
SLD running on SAP NetWeaver 70 for all other systemsuse cases This way your SAP
5 System Landscape
52 Shared Services
4456 PUBLIC 2011-04-15
NetWeaver PI 71 systems would benefit from the new features while it would be easy to set
up and operate such an SLD landscape For this purpose you could use the new fully
automatic synchronization This feature enables the automatic forwarding of all SLD data
from an SLD running on SAP NetWeaver 70 to an SLD running on SAP NetWeaver 71 As a
result there is no need to adapt most existing systems as their SLD data suppliers could still
send their data to the central SLD In brief the following steps would be required
1 Put SLD in a PI system into operation (part of standard implementation procedure)
2 Configure PI systems to use the new SLD (part of standard implementation procedure
for new PI systems)
3 Set up the fully automatic synchronization from your old SLD to your new SLD
As soon as an upgrade or an installation of a standalone AS Java 71 system is available you
could move your central SLD also to SAP NetWeaver 71 Then you could optionally shift
your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems
Figure 8
We recommend that you use a Domain Name System (DNS) alias so that you are able to switch to
another System Landscape Directory easily For example if customers build a new landscape they
normally start with a sandbox environment Over time more and more environments are set up
Once the production environment is in place move the System Landscape Directory there To do
this you can configure a new System Landscape Directory in the production environment
synchronize it with the old System Landscape directory and switch to the new one
Topology
Apart from the considerations above the System Landscape Directory offers several topology options
with different grades of availability at the expense of low administration and operation effort There is
no generic rule therefore on how to set up a System Landscape Directory in your system landscape
To find the topology and synchronization strategy for the System Landscape Directory that fits your
requirements concerning the System Landscape Directory availability (and hence the availability of
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4556
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
StepAction[Corresponding Documentation] Remarks
see the Installation Guide ndash SAP NetWeaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt
3 Install the Adapter Engine (Java SE) engines if required[Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
4 To integrate small business partners and subsidiaries the business partners or subsidiaries install SAP Partner Connectivity Kit running on AS Java with parts of usage type PI in the business partners or subsidiarys system landscape[Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt]
5 Install SAP Conversion Agent by Informatica if required[SAP Library [page 12] at Function-Oriented View Process Integration SAP Conversion Agent by Informatica Deploying and Using Conversion Agent ]
6 Installation of clients SAP GUI
[Installation Guide ndash SAP Front End]
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
The process sequences give a comprehensive overview of the steps relevant for the enhancement
package installation on an existing SAP NetWeaver PI 71 system
The process sequence is divided into a planning phase and an implementation phase Each step in both
phases contains references to the corresponding documentation to ensure that you can easily find the
information you need
Process
NOTE
To download the enhancement package files and required Support Packages you require the SAP
Solution Manager Maintenance Optimizer You have the following options
Manual Selection
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2856 PUBLIC 2011-04-15
You manually select the required files from SAP Service Marketplace at http
servicesapcomswdc using the SP Stack Application You use the Maintenance Optimize
only to approve the packages which is a prerequisite for the download
Automatic Calculation
The Maintenance Optimizer supports the download of a consistent queue that includes all
necessary Support Packages and enhancement packages In addition SAP Solution Manager
calculates a valid import queue for the selected SAP system and generates the enhancement
package stack configuration file that you require for the installation
As a prerequisite the system that you want to update needs to be maintained correctly in
SAP Solution Manager System Landscape As the Maintenance Optimizer uses this data for
the calculation it is crucial that the data is up-to-date In addition the SAP Solution Manager
system requires a Minimum Support Package level (see below)
Planing PhaseStep Description Documentation
Hardware amp Software Prerequisites
Check which platforms are supported for your target release (OSDB dependencies)
Product Availability Matrix (PAM) at httpservicesapcompam
Check which hardware sizing is required for your target release
Sizing information at httpservicesapcomsizing
Solution Manager Prerequisites
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of the required software packages you have to make sure that your SAP Solution Manager system has the required Support Package levelAt least SAP Solution Manager 70 EHP1 Support Package Stack 17 is required We recommend to use SAP Solution Manager 70 EHP1 Support Package Stack 23Check if you need to do an update or upgrade of your SAP Solution ManagerMake sure that you run the guided procedure SOLMAN_SETUP after every installation or update of SAP Solution Manager and that it completes successfully
For upgrades from source release SAP Solution Manager 31 and 32Upgrade Guide ndash SAP Solution Manager 70 incl Enhancement Package 1For updates from SAP Solution Manager 70Update Guide SAP Enhancement Package 1 for SAP Solution Manager 70Follow-up activities after an Support Package Stack update or enhancement package updateSolution Operations Guide ndash SAP Solution Manager 70 EHP1 section Software Change Management All guides are available at http
servicesapcom instguides SAP Components SAP Solution Manager -gt Release 70 EHP 1
Implementation PhaseStep Description Documentation
1Solution Manager Preparation
Configure the SAP Solution Manager Maintenance Optimizer
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of software packages make sure your
Configuration of Maintenance Optimizer http
helpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Change Request Management and Change ControlMaintenance Optimizer
Prerequisites
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 2956
Implementation PhaseStep Description Documentation
system landscape data in SAP Solution Manager is maintained correctlyLandscape Verification 10 which is an add-on to SAP Solution Manager can support you in maintaining your system landscape data The use of this tool is optional
Landscape Verification http
wwwsdnsapcom irj
sdn alm-update-
management link Landscape Verification under Related Areas on Upgrade and Update Management (in the right column)
SAP Note 1468605 (Installation of Landscape Verification)
Maintaining System Landscape Information [page 47]Note that the information provided in this section is based on SAP Solution Manager 70 EHP1 SP23
2System Preparation
Prepare your system as described in the documentation for example perform OS DB specific preparations and the PI-specific preparations
Update Guide ndash Update of SAP Systems with Software Update Manager sections Planning and Preparation
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
3Software Download
Select and download the software packages in either of the following ways Automatic calculation Create
a maintenance transaction in the Maintenance Optimizer and choose the Calculate Files Automatically option
Manual Selection Create a maintenance transaction in the Maintenance Optimizer and choose the Select Files Manually option You then can select the files manually using the SP Stack application in SAP Service Marketplace
NOTE
You have to download the stack configuration file manually after you have selected all files in the SP Stack
httphelpsapcom SAP Solutions SAP Solution Manager
SAP Solution Manager 70 EHP1 ltSPgtChange Request Management and
Change Control Maintenance Optimizer Maintenance Procedure Scenarios
For information about the automatic calculation see Maintenance Transaction with Installation of an Enhancement PackageFor information about the manual selection and approval process see section Approve and Download Files in Download Basket
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
3056 PUBLIC 2011-04-15
Implementation PhaseStep Description Documentation
application Choose Generate Stack XML and save the file
4Enhancement Package Installation
Run Software Update Manager to update your system with the selected software packages
Update Guide ndash Update of SAP Systems with Software Update Manager
5Follow-Up Steps
Perform technical and PI-specific follow-up activities after the enhancement package installation is done
Update Guide ndash Update of SAP Systems with Software Update Manager section Follow-Up Activities
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
6Configuration
Configure newly installed enhancement package functions using SAP Solution Manager content
See Systems with Usage Types [page 16] section Configuration of Systems with Usage Types
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 3156
This page is left blank for documents that are printed on both sides
5 System Landscape
51 Planning Your System Landscape
The installable software units that make up your system landscape depend on the functions that you
want to implement For information about the features see systems [page 16] standalone engines [page 19]
and clients [page 21]
In addition you have to determine the required shared services [page 35] (such as SAP Solution Manager
or SAP NetWeaver Administrator) that run on central systems in your system landscape and the
landscape aspects relevant for their implementation
In the following you will find general information that you should consider when planning your system
landscape
Sizing
You have to map systems and standalone engines to hosts after you have a clear picture of the following
Which systems and standalone engines you require
How many systems you require and how you want to use each of these systems
NOTE
No general guideline can be given for the sizing of your landscape since this relies heavily on your
requirements You should therefore perform this task together with your hardware partner and
your technical consultant
For information about sizing your systems you can use the following information sources
Your first point of reference is the Quick Sizer
SAP built the Quick Sizer as an online sizing questionnaire Internet application in close cooperation
with its hardware partners This tool delivers general sizing categories based on your volume load
estimates The results provide an objective basis for sizing independent of platform and
configuration
For more information see SAP Service Marketplace at
httpservicesapcomsizing for the SAP NetWeaver PI 71 sizing guide available under
Sizing Guidelines Business Suite amp Services
httpservicesapcomquicksizer for more information and access to the tool itself
Also consider the following important aspects concerning sizing
High availability
5 System Landscape
51 Planning Your System Landscape
2011-04-15 PUBLIC 3356
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Technical Infrastructure High Availability
Unicode
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Internationalization
Contact your hardware partner to find out the appropriate number of sized hosts
The platform-independent abstract results of the Quick Sizer can be used by any of our hardware
partners to create a concrete offer SAP itself does not make any hardware recommendations the
responsibility for sizing and detailed hardware configuration lies with the hardware partners
Figure 6 Example of Mapping of Systems and Standalone Engines to Three Hosts
NOTE
Optionally you could also distribute single systems to multiple hosts For example you could
decide to install the database instance of an SAP system on a separate host for performance
reasons or distribute other system instances to achieve high availability
To provide a mapping that fits your required functions and performance your hardware partner
and your technical consultant have to identify the number of required instances of SAP NetWeaver
find out how to distribute these instances to hosts and what functions will run on which instance
Therefore the hardware partner and the technical consultant have to consider many different
aspects such as
Number of required SAPS (SAP Application Benchmark Performance Standard) for each
system (provided by Quick Sizer)
Landscape-relevant aspects concerning security For more information see the SAP Security
Guide in the SAP Library [page 12] at Administratoracutes Guide Security Guide
Landscape-relevant aspects concerning scalability high availability operation and software
life-cycle management
5 System Landscape
51 Planning Your System Landscape
3456 PUBLIC 2011-04-15
For more information about relevant aspects for the mapping of systems to hosts see the document
Technical Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
Scaling and Distribution Options
You may need to design your system landscape for a large number of users SAP NetWeaver PI offers
you different means of scalability The following list provides you with some examples
You could install multiple systems of one type and use them for different purposes
You could scale every system by installing dialog instances or by distributing the database instance
For more information about distribution options on the instance level see the Technical
Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
For every SAP system you could additionally install Web Dispatcher For more information see
the SAP Library [page 12] at FunctionndashOriented View Application Server Infrastructure SAP Web
Dispatcher
You could further distribute certain standalone engines ndash for example Search and Classification
(TREX) is based on a flexible architecture that supports a distributed installation For more
information see the Technical Infrastructure Guide ndash SAP NetWeaver PI 71 available in SAP Service
Marketplace at httpservicesapcominstallNWPI71
52 Shared Services
You normally run shared services on central systems in your system landscape The following features
could be used for SAP NetWeaver Process Integration to realize shared services
SAP Solution Manager
Used to implement train test maintain monitor control change and manage incidents of your
SAP solution system landscape (open end-to-end application management)
As of SAP Solution Manager (70) 40 Support Package 15 SAP Solution Manager has become the
platform for SAPs end-to-end solution operations strategy Functions for complete application
management has been combined with administrative tools and has been merged in newly created
role based work centers
NOTE
Be aware that you require an SAP Solution Manager system to install or upgrade to SAP
NetWeaver 70 and higher An SAP Solution Manager system is required to generate the SAP
Solution Manager key needed during the installation or upgrade process Without this key
the installation or upgrade process cannot continue
For SAP NetWeaver Process Integration you require SAP Solution Manager 70
For more information see SAP Note 805390
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3556
Solution Manager Diagnostics
An integral part of SAP Solution Manager that is running as a Java application on the Java stack of
SAP Solution Manager 70 Solution Manager Diagnostics is used to analyze the root cause of
incidents in your landscape in an efficient and safe way Before Go-Live Solution Manager
Diagnostics has to be set up and made accessible remotely
SAP NetWeaver Administrator
SAP NetWeaver Administrator is the central administration component which is used for
monitoring and administering Java applications It is included in SAP NetWeaver systems with AS
Java
SAP NetWeaver Administrator exists in the following flavors
A local mode which runs out of the box and which focuses on administrating the underlying
SAP NetWeaver AS Java
NOTE
For a SAP NetWeaver PI 71 it has a special role which you need to activate using a
configuation wizard
A central mode which has to be configured before use and which deals with the system
landscape management
SAP has decided to merge the central mode of SAP NetWeaver Administrator into the new work
centers available as of SAP Solution Manager 70 SP 15 Thus it can be used in an administrative
context together with non-Java-based administration tools Although the central mode of SAP
NetWeaver Administrator will be still available for some time SAP will not develop this tool any
further SAP focuses on optimizing the administrative work centers of SAP Solution Manager
instead
The local mode of SAP NetWeaver Administrator stays untouched It is available for current and
future releases of SAP NetWeaver
SAP Central Process Scheduling by Redwood
SAP Central Process Scheduling application by Redwood enables central job scheduling and job
monitoring of current and old releases of AS ABAP systems (as of Basis Release 31) This application
is fully integrated in SAP NetWeaver Depending on the business needs SAP business applications
are the initial trigger for scheduled activities You can now manage jobs and job chains conveniently
using a graphical user interface
System Landscape Directory
The System Landscape Directory is the central directory of system landscape information relevant
for the management of your software life-cycle It contains a description of your system landscape
(that is software components that are currently installed) and a repository of software components
that can theoretically be installed in your landscape (such as the software components available
from SAP)
Adaptive Computing Controller
5 System Landscape
52 Shared Services
3656 PUBLIC 2011-04-15
The Adaptive Computing Controller enables users to control an adaptive computing landscape
from a single point through observation operation and dynamic resource distribution With
adaptive computing hardware software and system services are able to adapt to changing business
needs In the Adaptive Computing Controller the run-time data of logical and physical landscapes
can be monitored application services can be startedstoppedrelocated and hardware resources
can be assigned to application services The operation can also be mass executed and be planned as
tasks to be executed
For more information about the installation of the Adaptive Computing Controller tool see the
document Installation Guide ndash Adaptive Computing Controller in SAP NetWeaver 71 available on SAP Service
Marketplace at httpservicesapcominstallNWPI71
For more information about Adaptive Computing in general see httpsdnsapcomirj
sdnadaptive
521 Use Cases
You can use the applications and tools described above for use cases that are normally performed
centrally The following sections describe these use cases
5211 End-to-End Solution Operations
Running business applications through their complete life-cycle is a challenge Therefore SAP has
started the Run SAP methodology for implementing End-to-End Solution Operations Based on a set
of SAP standards a roadmap and a package for training and certification Run SAP helps customers to
facilitate End-to-End Solution Operations
You can download the SAP standards for Solution Operations from SAP Service Marketplace at http
servicesapcomsupportstandards They describe roles customers typically have in their IT
environment For optimal role support SAP has grouped existing and new functions in SAP Solution
Manager work centers as of SAP Solution Manager 70 Support Package 15 Operations aspects are fully
covered by adding administrative functions for SAP NetWeaver as well Work centers are ABAP Web
Dynpro-based applications They offer the following advantages
Easy to use similar look and feel
Context transfer while jumping from one work center into another
Logical grouping of tools for a certain area
Simple authorization concept
Easy to expand
Each IT role belongs to one or more work centers For instance the Technical Administrator IT role is
covered by the work centers for System Monitoring System Administration and Landscape Management
The following work centers are available
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3756
Business Process Operations
Change Management
Root Cause Analysis
Implementation Upgrade
Incident Management
Test Management
Job Management
System Landscape Management
Solution Documentation Assistant
SAP Engagement and Service Delivery
SAP Solution Manager Administration
System Administration
System Monitoring
My Home is the central point of access to all important data of almost all work centers in SAP Solution
Manager
5212 Support Infrastructure
A key requirement for effective support of IT solutions is the ability to perform root cause analysis with
speed and efficiency
With SAP Solution Manager SAP has long had an infrastructure in place for its ABAP applications that
efficiently supports SAP solutions This helps ensure the high availability and smooth running of
business processes For more information see the SAP Solution Manager section
With Solution Manager Diagnostics this knowledge has been extended to Java applications If for
example homegrown Java applications cause instability Solution Manager Diagnostics helps trace the
cause to eradicate the problem rapidly Solution Manager Diagnostics is fully integrated into SAP
Solution Manager 70 Solution Manager Diagnostics also contains two third-party tools CArsquos Wily
Introscopereg for measuring performance as well as troubleshooting problems of the Java EE Engine
and applications running on it and Mercury Loadrunnerreg which enables SAP Support to produce a
defined load in the SAP solution landscape remotely For more information see Solution Manager
Diagnostics [page 43]
The support infrastructure provides SAP Support with safe access to your productive landscape for safe
root cause analysis so ensuring that SAP Support does not change your landscape inadvertently You
require a support infrastructure to run SAP NetWeaver
The following figure shows the overall infrastructure including SAP NetWeaver administration tools
that are used by administrators or operators at the customer site
5 System Landscape
52 Shared Services
3856 PUBLIC 2011-04-15
Landscape Aspects
If you use SAP NetWeaver Process Integration 71 productively besides SAP Solution Manager (as a
central support platform) you have to set up Solution Manager Diagnostics for supportability reasons
Implementation Sequence
For information about the implementation of the support infrastructure see the document Master
Guide ndash SAP Solution Manager 70 available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution Manager ltReleasegt
5213 Collection of Landscape Data
Amongst other applications and services the support infrastructure and the SAP NetWeaver
administration tools rely on system landscape data
For SAP NetWeaver PI 71 you have to run non-ABAP components in your solution landscape
Therefore the System Landscape Directory is mandatory The landscape data that is automatically
gathered by the System Landscape Directory is replicated to SAP Solution Manager There are several
topology options for the System Landscape Directory They offer different grades of availability
administration and operation effort
For more information see the System Landscape Directory section
5214 Authentication and Single Sign-On
Before implementing your system landscape plan how to implement authentication and how to
integrate different systems into a Single Sign-On landscape Single Sign-On reduces complexity for end
users saving them valuable time while also reducing administration effort for resetting passwords
thereby contributing to TCO reduction
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
5215 Integrated User and Access Management
In a system landscape containing a combination of ABAP and Java components we recommend that
you integrate your user and access management so that you can use the same user data across different
systems administer this data centrally and control access to data SAPs mature fine-grained
authorization concept allows detailed control of access rights SAP NetWeaver provides both ABAP and
Java-based user management solutions The user management solution that you use to administer
your user data depends on factors such as the type of systems that are running in your landscape
If you want to use central user administration we recommend that you run it in a non-production
system If you do not have a central user administration yet you can for example realize it in the SAP
Solution Manager system
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3956
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
522 Examples for the Overall System Landscape of Shared Services
In this section we provide examples of how shared services can be set up depending on the system
landscape they are intended for The following examples aggregate the landscape aspects given in the
Use Cases section
NOTE
The following sections and the figure mostly do not show information about the life-cycle of
shared services For example you may also need a development and testquality assurance system
for SAP Solution Manager You should consider this aspect in addition to the information given
in this section based on your requirements
Small and MediumndashSized Customer Landscapes with Java
As you use Java productively for SAP NetWeaver PI 71 besides SAP Solution Manager you have to set
up additional components for optimal monitoring administration and support Solution Manager
Diagnostics and the central mode of SAP NetWeaver Administrator are already fully integrated into
SAP Solution Manager 70 as the central operations hub For SAP Process Integration you must also
set up SAP NetWeaver Administrator with a special role
We recommend that you do not install SAP Central Process Scheduling in the SAP Solution Manager
system You have to set up and operate the system which hosts your productive scheduler as a mission
critical system
In the SAP Solution Manager system you should set up a local System Landscape Directory in addition
to a central runtime System Landscape Directory This way you have a clear separation between your
management system (SAP Solution Manager) and managed systems in your landscape In addition
SAP Solution Manager then does not rely on a System Landscape Directory running in the production
environment For this setup configure the SLD data suppliers of your SAP Solution Manager system
to send data to the central runtime System Landscape Directory In addition configure automatic
bridge forwarding from your runtime System Landscape Directory to the local System Landscape
Directory For more information see the Planning Guide - System Landscape Directory
If you want to use a central system for Adobe Document Services we recommend that you install a
dedicated system for this purpose in your production environment For detailed information about
the sizing of the system for the different use cases see the Sizing Guide for Adobe Document Services at
SAP Service Marketplace at httpservicesapcomsizing Sizing Guidelines Solutions amp
Platform
We recommend that you start with this centralized SAP Solution Manager approach as depicted in the
following figure
5 System Landscape
52 Shared Services
4056 PUBLIC 2011-04-15
Figure 7 Single SAP Solution Manager Landscape
Large Customer Landscapes with Java
Large customers who have environments in their landscape that are large and distributed administered
by different groups or separated for security reasons can consider a distributed operations setup In
addition to the centralized setup described for small- and medium-sized customers above large
customers can put parts of the central management functions on extra hosts or systems for performance
or policy reasons You have the following options for a distributed setup
You may set up an extra system or client for Central User Administration (CUA)
The Change and Transport System (CTS) can run on an extra system However it is not
performance- or data-intensive
You may set up an extra system for central CCMS monitoring Depending on the customizing
and on the landscape size central CCMS may generate a lot of system load You can connect a
separate central CCMS to SAP Solution Manager for displaying alerts in the alert inbox of the System
Monitoring work center
You can use a separate SAP NetWeaver 70 system with usage type BI together with SAP Solution
Manager This may make sense with respect to the amount of landscape management data that is
stored for reporting purposes The amount of data strongly depends on the data granularity
storage time frame and landscape size
You can easily put Wily Introscope Enterprise Manager on an separate host
Other aspects described above for small- and medium-customers (such as the setup of the System
Landscape Directory) are also valid for large customers
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4156
523 Feature Details
This section provides further information about the features described above
5231 SAP Solution Manager
SAP provides you with SAP Solution Manager as the strategic application management platform and
to enable the collaboration between you and SAP You need to install at least one productive SAP
Solution Manager in your system landscape To ensure the availability of this application management
platform an SAP Solution Manager system is technically required to install or upgrade to SAP
NetWeaver 70 or higher If you are already using SAP Solution Manager you can also use it to manage
the solution you build with SAP NetWeaver In this case we highly recommend that you update SAP
Solution Manager to the latest version
As of SAP Solution Manager 70 SP15 you can use the newly created work centers
NOTE
During the SAP system installation or upgrade process you are prompted to enter the SAP
Solution Manager key An SAP Solution Manager system is required to generate this key Without
this key the installation or upgrade process cannot continue
You may generate all needed keys for your entire system landscape (development quality
assurance and production system) in one SAP Solution Manager system In case you plan to install
several solution landscapes (for example in different countries) one SAP Solution Manager
system is still sufficient
For more information see SAP Note 805390
It is possible to install multiple SAP Solution Managers If you do so they should host separate business
solutions
If you want to reduce the risk of unavailability you should not install SAP Solution Manager as a central
component Instead you can operate a 2-system-landscape with both a test and production
environment of SAP Solution Manager (especially if you are using time-critical functions like Support
Desk) If you also develop your own content a 3-system-landscape with a development test and
production environment is recommended
For more information about SAP Solution Manager see the following table
Topic Where to Find More Information
System infrastructure scenarios installation and configuration of SAP Solution Manager
Master Guide ndash SAP Solution Manager available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution ManagerltReleasegt
Benefits and usage scenarios SAP Solution Manager ndash Learning Maps available on SAP Service Marketplace at http
5 System Landscape
52 Shared Services
4256 PUBLIC 2011-04-15
Topic Where to Find More Informationservicesapcomrkt-solman or https
servicesapcomsolutionmanager
Additional information See SAP Service Marketplace at http
servicesapcomsolutionmanager
5232 Solution Manager Diagnostics
Solution Manager Diagnostics provides efficient and safe root-cause analysis of incidents in customer
solutions powered by SAP NetWeaver It can help monitor on operating systems databases Java
application activities performance and logs It also supports the reporting of software and
configuration changes that can lead to malfunctions and errors
You must run one Solution Manager Diagnostics within your SAP solution landscape if you run
applications based on SAP NetWeaver systems with usage type AS Java Agents are responsible for
delivering the data from all productive hosts within your system landscape to the Solution Manager
Diagnostics system
CAUTION
SAP Support performs root-cause analysis on incoming incidents with Solution Manager
Diagnostics Not installing and configuring this support infrastructure results in a dramatically
reduced service level
Solution Manager Diagnostics is fully integrated into SAP Solution Manager 70
Solution Manager Diagnostics also contains Wily Introscope (Display Server and Agent part) for
measuring performance as well as to troubleshoot problems of Non-ABAP applications Wily Introscope
is heavily used for troubleshooting applications running on AS Java
SAP has signed a distribution agreement for Wily Introscope SAP customers are allowed to use this
tool in a preconfigured way
For more information about Solution Manager Diagnostics and an FAQ list see SAP Service Marketplace
at httpservicesapcomdiagnostics
5233 System Landscape Directory
The System Landscape Directory (SLD) of SAP NetWeaver is the central directory of system landscape
information relevant for the management of your software life-cycle
NOTE
Note that the abbreviation SLD is not intended to define a product since the System Landscape
Directory is part of SAP NetWeaver This abbreviation is solely intended to improve readability
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4356
The System Landscape Directory contains a description of your system landscape (that is software
components that are currently installed) and a repository of software components that can
theoretically be installed in your landscape (such as the software components available from SAP)
Since this data gets updated automatically the System Landscape Directory provides reliable and up-
to-date system landscape information with as little effort for you as possible In this way the System
Landscape Directory acts as a central information provider for SAP and third-party tools that use this
data to deliver the services you need to keep your landscape up and running
For the System Landscape Directory as part of an SAP NetWeaver PI 71 landscape consider the following
aspects
Part of SAP NetWeaver PI 71 is a new version of the System Landscape Directory It is automatically
included in every SAP NetWeaver 71 system with usage type AS Java It offers enhanced functions
such as a full automatic synchronization mechanism for all data stored in it That is both data
delivered by data suppliers and data entered or changed manually in the System Landscape
Directory can be synchronized automatically This synchronization offers the following
A fully automated mechanism so no user interaction is required and conflicts are resolved
automatically
Asynchronous propagation of information so some nodes may be down temporarily
Communication over HTTP protocol
Uni- and bi-directional synchronization
Depending on your use case the full automatic synchronization could significantly reduce manual
synchronization effort
For SAP NetWeaver PI 71 the configuration of the system landscape directory and its data suppliers
is already included in the standard implementation procedure with SAPinst For existing systems
you only have to perform some quick and easy configuration actions to start operating the system
landscape directory server in an AS Java system
For SAP NetWeaver PI 71 you have the following options concerning SLD
Option 1
Run SAP NetWeaver PI 71 against an existing SLD running on SAP NetWeaver 70 We only
recommend this for upgrades from SAP NetWeaver 70 if you have a central SLD in operation
not running on one of your PI systems
Option 2
Use the SLD included in an SAP NetWeaver PI 71 system We recommend this option for new
installations and upgrades from older releases than SAP NetWeaver 70 due to the enhanced
functions and improved performance of SLD 71
NOTE
If you already have a central SLD running on SAP NetWeaver 70 in operation you could run
two SLD versions in parallel ndash SLD running on SAP NetWeaver 71 for your PI systems and
SLD running on SAP NetWeaver 70 for all other systemsuse cases This way your SAP
5 System Landscape
52 Shared Services
4456 PUBLIC 2011-04-15
NetWeaver PI 71 systems would benefit from the new features while it would be easy to set
up and operate such an SLD landscape For this purpose you could use the new fully
automatic synchronization This feature enables the automatic forwarding of all SLD data
from an SLD running on SAP NetWeaver 70 to an SLD running on SAP NetWeaver 71 As a
result there is no need to adapt most existing systems as their SLD data suppliers could still
send their data to the central SLD In brief the following steps would be required
1 Put SLD in a PI system into operation (part of standard implementation procedure)
2 Configure PI systems to use the new SLD (part of standard implementation procedure
for new PI systems)
3 Set up the fully automatic synchronization from your old SLD to your new SLD
As soon as an upgrade or an installation of a standalone AS Java 71 system is available you
could move your central SLD also to SAP NetWeaver 71 Then you could optionally shift
your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems
Figure 8
We recommend that you use a Domain Name System (DNS) alias so that you are able to switch to
another System Landscape Directory easily For example if customers build a new landscape they
normally start with a sandbox environment Over time more and more environments are set up
Once the production environment is in place move the System Landscape Directory there To do
this you can configure a new System Landscape Directory in the production environment
synchronize it with the old System Landscape directory and switch to the new one
Topology
Apart from the considerations above the System Landscape Directory offers several topology options
with different grades of availability at the expense of low administration and operation effort There is
no generic rule therefore on how to set up a System Landscape Directory in your system landscape
To find the topology and synchronization strategy for the System Landscape Directory that fits your
requirements concerning the System Landscape Directory availability (and hence the availability of
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4556
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
You manually select the required files from SAP Service Marketplace at http
servicesapcomswdc using the SP Stack Application You use the Maintenance Optimize
only to approve the packages which is a prerequisite for the download
Automatic Calculation
The Maintenance Optimizer supports the download of a consistent queue that includes all
necessary Support Packages and enhancement packages In addition SAP Solution Manager
calculates a valid import queue for the selected SAP system and generates the enhancement
package stack configuration file that you require for the installation
As a prerequisite the system that you want to update needs to be maintained correctly in
SAP Solution Manager System Landscape As the Maintenance Optimizer uses this data for
the calculation it is crucial that the data is up-to-date In addition the SAP Solution Manager
system requires a Minimum Support Package level (see below)
Planing PhaseStep Description Documentation
Hardware amp Software Prerequisites
Check which platforms are supported for your target release (OSDB dependencies)
Product Availability Matrix (PAM) at httpservicesapcompam
Check which hardware sizing is required for your target release
Sizing information at httpservicesapcomsizing
Solution Manager Prerequisites
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of the required software packages you have to make sure that your SAP Solution Manager system has the required Support Package levelAt least SAP Solution Manager 70 EHP1 Support Package Stack 17 is required We recommend to use SAP Solution Manager 70 EHP1 Support Package Stack 23Check if you need to do an update or upgrade of your SAP Solution ManagerMake sure that you run the guided procedure SOLMAN_SETUP after every installation or update of SAP Solution Manager and that it completes successfully
For upgrades from source release SAP Solution Manager 31 and 32Upgrade Guide ndash SAP Solution Manager 70 incl Enhancement Package 1For updates from SAP Solution Manager 70Update Guide SAP Enhancement Package 1 for SAP Solution Manager 70Follow-up activities after an Support Package Stack update or enhancement package updateSolution Operations Guide ndash SAP Solution Manager 70 EHP1 section Software Change Management All guides are available at http
servicesapcom instguides SAP Components SAP Solution Manager -gt Release 70 EHP 1
Implementation PhaseStep Description Documentation
1Solution Manager Preparation
Configure the SAP Solution Manager Maintenance Optimizer
If you want to use SAP Solution Manager Maintenance Optimizer for the automatic calculation of software packages make sure your
Configuration of Maintenance Optimizer http
helpsapcom SAP Solution Manager SAP Solution Manager ltReleasegt Change Request Management and Change ControlMaintenance Optimizer
Prerequisites
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 2956
Implementation PhaseStep Description Documentation
system landscape data in SAP Solution Manager is maintained correctlyLandscape Verification 10 which is an add-on to SAP Solution Manager can support you in maintaining your system landscape data The use of this tool is optional
Landscape Verification http
wwwsdnsapcom irj
sdn alm-update-
management link Landscape Verification under Related Areas on Upgrade and Update Management (in the right column)
SAP Note 1468605 (Installation of Landscape Verification)
Maintaining System Landscape Information [page 47]Note that the information provided in this section is based on SAP Solution Manager 70 EHP1 SP23
2System Preparation
Prepare your system as described in the documentation for example perform OS DB specific preparations and the PI-specific preparations
Update Guide ndash Update of SAP Systems with Software Update Manager sections Planning and Preparation
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
3Software Download
Select and download the software packages in either of the following ways Automatic calculation Create
a maintenance transaction in the Maintenance Optimizer and choose the Calculate Files Automatically option
Manual Selection Create a maintenance transaction in the Maintenance Optimizer and choose the Select Files Manually option You then can select the files manually using the SP Stack application in SAP Service Marketplace
NOTE
You have to download the stack configuration file manually after you have selected all files in the SP Stack
httphelpsapcom SAP Solutions SAP Solution Manager
SAP Solution Manager 70 EHP1 ltSPgtChange Request Management and
Change Control Maintenance Optimizer Maintenance Procedure Scenarios
For information about the automatic calculation see Maintenance Transaction with Installation of an Enhancement PackageFor information about the manual selection and approval process see section Approve and Download Files in Download Basket
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
3056 PUBLIC 2011-04-15
Implementation PhaseStep Description Documentation
application Choose Generate Stack XML and save the file
4Enhancement Package Installation
Run Software Update Manager to update your system with the selected software packages
Update Guide ndash Update of SAP Systems with Software Update Manager
5Follow-Up Steps
Perform technical and PI-specific follow-up activities after the enhancement package installation is done
Update Guide ndash Update of SAP Systems with Software Update Manager section Follow-Up Activities
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
6Configuration
Configure newly installed enhancement package functions using SAP Solution Manager content
See Systems with Usage Types [page 16] section Configuration of Systems with Usage Types
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 3156
This page is left blank for documents that are printed on both sides
5 System Landscape
51 Planning Your System Landscape
The installable software units that make up your system landscape depend on the functions that you
want to implement For information about the features see systems [page 16] standalone engines [page 19]
and clients [page 21]
In addition you have to determine the required shared services [page 35] (such as SAP Solution Manager
or SAP NetWeaver Administrator) that run on central systems in your system landscape and the
landscape aspects relevant for their implementation
In the following you will find general information that you should consider when planning your system
landscape
Sizing
You have to map systems and standalone engines to hosts after you have a clear picture of the following
Which systems and standalone engines you require
How many systems you require and how you want to use each of these systems
NOTE
No general guideline can be given for the sizing of your landscape since this relies heavily on your
requirements You should therefore perform this task together with your hardware partner and
your technical consultant
For information about sizing your systems you can use the following information sources
Your first point of reference is the Quick Sizer
SAP built the Quick Sizer as an online sizing questionnaire Internet application in close cooperation
with its hardware partners This tool delivers general sizing categories based on your volume load
estimates The results provide an objective basis for sizing independent of platform and
configuration
For more information see SAP Service Marketplace at
httpservicesapcomsizing for the SAP NetWeaver PI 71 sizing guide available under
Sizing Guidelines Business Suite amp Services
httpservicesapcomquicksizer for more information and access to the tool itself
Also consider the following important aspects concerning sizing
High availability
5 System Landscape
51 Planning Your System Landscape
2011-04-15 PUBLIC 3356
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Technical Infrastructure High Availability
Unicode
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Internationalization
Contact your hardware partner to find out the appropriate number of sized hosts
The platform-independent abstract results of the Quick Sizer can be used by any of our hardware
partners to create a concrete offer SAP itself does not make any hardware recommendations the
responsibility for sizing and detailed hardware configuration lies with the hardware partners
Figure 6 Example of Mapping of Systems and Standalone Engines to Three Hosts
NOTE
Optionally you could also distribute single systems to multiple hosts For example you could
decide to install the database instance of an SAP system on a separate host for performance
reasons or distribute other system instances to achieve high availability
To provide a mapping that fits your required functions and performance your hardware partner
and your technical consultant have to identify the number of required instances of SAP NetWeaver
find out how to distribute these instances to hosts and what functions will run on which instance
Therefore the hardware partner and the technical consultant have to consider many different
aspects such as
Number of required SAPS (SAP Application Benchmark Performance Standard) for each
system (provided by Quick Sizer)
Landscape-relevant aspects concerning security For more information see the SAP Security
Guide in the SAP Library [page 12] at Administratoracutes Guide Security Guide
Landscape-relevant aspects concerning scalability high availability operation and software
life-cycle management
5 System Landscape
51 Planning Your System Landscape
3456 PUBLIC 2011-04-15
For more information about relevant aspects for the mapping of systems to hosts see the document
Technical Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
Scaling and Distribution Options
You may need to design your system landscape for a large number of users SAP NetWeaver PI offers
you different means of scalability The following list provides you with some examples
You could install multiple systems of one type and use them for different purposes
You could scale every system by installing dialog instances or by distributing the database instance
For more information about distribution options on the instance level see the Technical
Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
For every SAP system you could additionally install Web Dispatcher For more information see
the SAP Library [page 12] at FunctionndashOriented View Application Server Infrastructure SAP Web
Dispatcher
You could further distribute certain standalone engines ndash for example Search and Classification
(TREX) is based on a flexible architecture that supports a distributed installation For more
information see the Technical Infrastructure Guide ndash SAP NetWeaver PI 71 available in SAP Service
Marketplace at httpservicesapcominstallNWPI71
52 Shared Services
You normally run shared services on central systems in your system landscape The following features
could be used for SAP NetWeaver Process Integration to realize shared services
SAP Solution Manager
Used to implement train test maintain monitor control change and manage incidents of your
SAP solution system landscape (open end-to-end application management)
As of SAP Solution Manager (70) 40 Support Package 15 SAP Solution Manager has become the
platform for SAPs end-to-end solution operations strategy Functions for complete application
management has been combined with administrative tools and has been merged in newly created
role based work centers
NOTE
Be aware that you require an SAP Solution Manager system to install or upgrade to SAP
NetWeaver 70 and higher An SAP Solution Manager system is required to generate the SAP
Solution Manager key needed during the installation or upgrade process Without this key
the installation or upgrade process cannot continue
For SAP NetWeaver Process Integration you require SAP Solution Manager 70
For more information see SAP Note 805390
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3556
Solution Manager Diagnostics
An integral part of SAP Solution Manager that is running as a Java application on the Java stack of
SAP Solution Manager 70 Solution Manager Diagnostics is used to analyze the root cause of
incidents in your landscape in an efficient and safe way Before Go-Live Solution Manager
Diagnostics has to be set up and made accessible remotely
SAP NetWeaver Administrator
SAP NetWeaver Administrator is the central administration component which is used for
monitoring and administering Java applications It is included in SAP NetWeaver systems with AS
Java
SAP NetWeaver Administrator exists in the following flavors
A local mode which runs out of the box and which focuses on administrating the underlying
SAP NetWeaver AS Java
NOTE
For a SAP NetWeaver PI 71 it has a special role which you need to activate using a
configuation wizard
A central mode which has to be configured before use and which deals with the system
landscape management
SAP has decided to merge the central mode of SAP NetWeaver Administrator into the new work
centers available as of SAP Solution Manager 70 SP 15 Thus it can be used in an administrative
context together with non-Java-based administration tools Although the central mode of SAP
NetWeaver Administrator will be still available for some time SAP will not develop this tool any
further SAP focuses on optimizing the administrative work centers of SAP Solution Manager
instead
The local mode of SAP NetWeaver Administrator stays untouched It is available for current and
future releases of SAP NetWeaver
SAP Central Process Scheduling by Redwood
SAP Central Process Scheduling application by Redwood enables central job scheduling and job
monitoring of current and old releases of AS ABAP systems (as of Basis Release 31) This application
is fully integrated in SAP NetWeaver Depending on the business needs SAP business applications
are the initial trigger for scheduled activities You can now manage jobs and job chains conveniently
using a graphical user interface
System Landscape Directory
The System Landscape Directory is the central directory of system landscape information relevant
for the management of your software life-cycle It contains a description of your system landscape
(that is software components that are currently installed) and a repository of software components
that can theoretically be installed in your landscape (such as the software components available
from SAP)
Adaptive Computing Controller
5 System Landscape
52 Shared Services
3656 PUBLIC 2011-04-15
The Adaptive Computing Controller enables users to control an adaptive computing landscape
from a single point through observation operation and dynamic resource distribution With
adaptive computing hardware software and system services are able to adapt to changing business
needs In the Adaptive Computing Controller the run-time data of logical and physical landscapes
can be monitored application services can be startedstoppedrelocated and hardware resources
can be assigned to application services The operation can also be mass executed and be planned as
tasks to be executed
For more information about the installation of the Adaptive Computing Controller tool see the
document Installation Guide ndash Adaptive Computing Controller in SAP NetWeaver 71 available on SAP Service
Marketplace at httpservicesapcominstallNWPI71
For more information about Adaptive Computing in general see httpsdnsapcomirj
sdnadaptive
521 Use Cases
You can use the applications and tools described above for use cases that are normally performed
centrally The following sections describe these use cases
5211 End-to-End Solution Operations
Running business applications through their complete life-cycle is a challenge Therefore SAP has
started the Run SAP methodology for implementing End-to-End Solution Operations Based on a set
of SAP standards a roadmap and a package for training and certification Run SAP helps customers to
facilitate End-to-End Solution Operations
You can download the SAP standards for Solution Operations from SAP Service Marketplace at http
servicesapcomsupportstandards They describe roles customers typically have in their IT
environment For optimal role support SAP has grouped existing and new functions in SAP Solution
Manager work centers as of SAP Solution Manager 70 Support Package 15 Operations aspects are fully
covered by adding administrative functions for SAP NetWeaver as well Work centers are ABAP Web
Dynpro-based applications They offer the following advantages
Easy to use similar look and feel
Context transfer while jumping from one work center into another
Logical grouping of tools for a certain area
Simple authorization concept
Easy to expand
Each IT role belongs to one or more work centers For instance the Technical Administrator IT role is
covered by the work centers for System Monitoring System Administration and Landscape Management
The following work centers are available
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3756
Business Process Operations
Change Management
Root Cause Analysis
Implementation Upgrade
Incident Management
Test Management
Job Management
System Landscape Management
Solution Documentation Assistant
SAP Engagement and Service Delivery
SAP Solution Manager Administration
System Administration
System Monitoring
My Home is the central point of access to all important data of almost all work centers in SAP Solution
Manager
5212 Support Infrastructure
A key requirement for effective support of IT solutions is the ability to perform root cause analysis with
speed and efficiency
With SAP Solution Manager SAP has long had an infrastructure in place for its ABAP applications that
efficiently supports SAP solutions This helps ensure the high availability and smooth running of
business processes For more information see the SAP Solution Manager section
With Solution Manager Diagnostics this knowledge has been extended to Java applications If for
example homegrown Java applications cause instability Solution Manager Diagnostics helps trace the
cause to eradicate the problem rapidly Solution Manager Diagnostics is fully integrated into SAP
Solution Manager 70 Solution Manager Diagnostics also contains two third-party tools CArsquos Wily
Introscopereg for measuring performance as well as troubleshooting problems of the Java EE Engine
and applications running on it and Mercury Loadrunnerreg which enables SAP Support to produce a
defined load in the SAP solution landscape remotely For more information see Solution Manager
Diagnostics [page 43]
The support infrastructure provides SAP Support with safe access to your productive landscape for safe
root cause analysis so ensuring that SAP Support does not change your landscape inadvertently You
require a support infrastructure to run SAP NetWeaver
The following figure shows the overall infrastructure including SAP NetWeaver administration tools
that are used by administrators or operators at the customer site
5 System Landscape
52 Shared Services
3856 PUBLIC 2011-04-15
Landscape Aspects
If you use SAP NetWeaver Process Integration 71 productively besides SAP Solution Manager (as a
central support platform) you have to set up Solution Manager Diagnostics for supportability reasons
Implementation Sequence
For information about the implementation of the support infrastructure see the document Master
Guide ndash SAP Solution Manager 70 available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution Manager ltReleasegt
5213 Collection of Landscape Data
Amongst other applications and services the support infrastructure and the SAP NetWeaver
administration tools rely on system landscape data
For SAP NetWeaver PI 71 you have to run non-ABAP components in your solution landscape
Therefore the System Landscape Directory is mandatory The landscape data that is automatically
gathered by the System Landscape Directory is replicated to SAP Solution Manager There are several
topology options for the System Landscape Directory They offer different grades of availability
administration and operation effort
For more information see the System Landscape Directory section
5214 Authentication and Single Sign-On
Before implementing your system landscape plan how to implement authentication and how to
integrate different systems into a Single Sign-On landscape Single Sign-On reduces complexity for end
users saving them valuable time while also reducing administration effort for resetting passwords
thereby contributing to TCO reduction
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
5215 Integrated User and Access Management
In a system landscape containing a combination of ABAP and Java components we recommend that
you integrate your user and access management so that you can use the same user data across different
systems administer this data centrally and control access to data SAPs mature fine-grained
authorization concept allows detailed control of access rights SAP NetWeaver provides both ABAP and
Java-based user management solutions The user management solution that you use to administer
your user data depends on factors such as the type of systems that are running in your landscape
If you want to use central user administration we recommend that you run it in a non-production
system If you do not have a central user administration yet you can for example realize it in the SAP
Solution Manager system
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3956
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
522 Examples for the Overall System Landscape of Shared Services
In this section we provide examples of how shared services can be set up depending on the system
landscape they are intended for The following examples aggregate the landscape aspects given in the
Use Cases section
NOTE
The following sections and the figure mostly do not show information about the life-cycle of
shared services For example you may also need a development and testquality assurance system
for SAP Solution Manager You should consider this aspect in addition to the information given
in this section based on your requirements
Small and MediumndashSized Customer Landscapes with Java
As you use Java productively for SAP NetWeaver PI 71 besides SAP Solution Manager you have to set
up additional components for optimal monitoring administration and support Solution Manager
Diagnostics and the central mode of SAP NetWeaver Administrator are already fully integrated into
SAP Solution Manager 70 as the central operations hub For SAP Process Integration you must also
set up SAP NetWeaver Administrator with a special role
We recommend that you do not install SAP Central Process Scheduling in the SAP Solution Manager
system You have to set up and operate the system which hosts your productive scheduler as a mission
critical system
In the SAP Solution Manager system you should set up a local System Landscape Directory in addition
to a central runtime System Landscape Directory This way you have a clear separation between your
management system (SAP Solution Manager) and managed systems in your landscape In addition
SAP Solution Manager then does not rely on a System Landscape Directory running in the production
environment For this setup configure the SLD data suppliers of your SAP Solution Manager system
to send data to the central runtime System Landscape Directory In addition configure automatic
bridge forwarding from your runtime System Landscape Directory to the local System Landscape
Directory For more information see the Planning Guide - System Landscape Directory
If you want to use a central system for Adobe Document Services we recommend that you install a
dedicated system for this purpose in your production environment For detailed information about
the sizing of the system for the different use cases see the Sizing Guide for Adobe Document Services at
SAP Service Marketplace at httpservicesapcomsizing Sizing Guidelines Solutions amp
Platform
We recommend that you start with this centralized SAP Solution Manager approach as depicted in the
following figure
5 System Landscape
52 Shared Services
4056 PUBLIC 2011-04-15
Figure 7 Single SAP Solution Manager Landscape
Large Customer Landscapes with Java
Large customers who have environments in their landscape that are large and distributed administered
by different groups or separated for security reasons can consider a distributed operations setup In
addition to the centralized setup described for small- and medium-sized customers above large
customers can put parts of the central management functions on extra hosts or systems for performance
or policy reasons You have the following options for a distributed setup
You may set up an extra system or client for Central User Administration (CUA)
The Change and Transport System (CTS) can run on an extra system However it is not
performance- or data-intensive
You may set up an extra system for central CCMS monitoring Depending on the customizing
and on the landscape size central CCMS may generate a lot of system load You can connect a
separate central CCMS to SAP Solution Manager for displaying alerts in the alert inbox of the System
Monitoring work center
You can use a separate SAP NetWeaver 70 system with usage type BI together with SAP Solution
Manager This may make sense with respect to the amount of landscape management data that is
stored for reporting purposes The amount of data strongly depends on the data granularity
storage time frame and landscape size
You can easily put Wily Introscope Enterprise Manager on an separate host
Other aspects described above for small- and medium-customers (such as the setup of the System
Landscape Directory) are also valid for large customers
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4156
523 Feature Details
This section provides further information about the features described above
5231 SAP Solution Manager
SAP provides you with SAP Solution Manager as the strategic application management platform and
to enable the collaboration between you and SAP You need to install at least one productive SAP
Solution Manager in your system landscape To ensure the availability of this application management
platform an SAP Solution Manager system is technically required to install or upgrade to SAP
NetWeaver 70 or higher If you are already using SAP Solution Manager you can also use it to manage
the solution you build with SAP NetWeaver In this case we highly recommend that you update SAP
Solution Manager to the latest version
As of SAP Solution Manager 70 SP15 you can use the newly created work centers
NOTE
During the SAP system installation or upgrade process you are prompted to enter the SAP
Solution Manager key An SAP Solution Manager system is required to generate this key Without
this key the installation or upgrade process cannot continue
You may generate all needed keys for your entire system landscape (development quality
assurance and production system) in one SAP Solution Manager system In case you plan to install
several solution landscapes (for example in different countries) one SAP Solution Manager
system is still sufficient
For more information see SAP Note 805390
It is possible to install multiple SAP Solution Managers If you do so they should host separate business
solutions
If you want to reduce the risk of unavailability you should not install SAP Solution Manager as a central
component Instead you can operate a 2-system-landscape with both a test and production
environment of SAP Solution Manager (especially if you are using time-critical functions like Support
Desk) If you also develop your own content a 3-system-landscape with a development test and
production environment is recommended
For more information about SAP Solution Manager see the following table
Topic Where to Find More Information
System infrastructure scenarios installation and configuration of SAP Solution Manager
Master Guide ndash SAP Solution Manager available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution ManagerltReleasegt
Benefits and usage scenarios SAP Solution Manager ndash Learning Maps available on SAP Service Marketplace at http
5 System Landscape
52 Shared Services
4256 PUBLIC 2011-04-15
Topic Where to Find More Informationservicesapcomrkt-solman or https
servicesapcomsolutionmanager
Additional information See SAP Service Marketplace at http
servicesapcomsolutionmanager
5232 Solution Manager Diagnostics
Solution Manager Diagnostics provides efficient and safe root-cause analysis of incidents in customer
solutions powered by SAP NetWeaver It can help monitor on operating systems databases Java
application activities performance and logs It also supports the reporting of software and
configuration changes that can lead to malfunctions and errors
You must run one Solution Manager Diagnostics within your SAP solution landscape if you run
applications based on SAP NetWeaver systems with usage type AS Java Agents are responsible for
delivering the data from all productive hosts within your system landscape to the Solution Manager
Diagnostics system
CAUTION
SAP Support performs root-cause analysis on incoming incidents with Solution Manager
Diagnostics Not installing and configuring this support infrastructure results in a dramatically
reduced service level
Solution Manager Diagnostics is fully integrated into SAP Solution Manager 70
Solution Manager Diagnostics also contains Wily Introscope (Display Server and Agent part) for
measuring performance as well as to troubleshoot problems of Non-ABAP applications Wily Introscope
is heavily used for troubleshooting applications running on AS Java
SAP has signed a distribution agreement for Wily Introscope SAP customers are allowed to use this
tool in a preconfigured way
For more information about Solution Manager Diagnostics and an FAQ list see SAP Service Marketplace
at httpservicesapcomdiagnostics
5233 System Landscape Directory
The System Landscape Directory (SLD) of SAP NetWeaver is the central directory of system landscape
information relevant for the management of your software life-cycle
NOTE
Note that the abbreviation SLD is not intended to define a product since the System Landscape
Directory is part of SAP NetWeaver This abbreviation is solely intended to improve readability
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4356
The System Landscape Directory contains a description of your system landscape (that is software
components that are currently installed) and a repository of software components that can
theoretically be installed in your landscape (such as the software components available from SAP)
Since this data gets updated automatically the System Landscape Directory provides reliable and up-
to-date system landscape information with as little effort for you as possible In this way the System
Landscape Directory acts as a central information provider for SAP and third-party tools that use this
data to deliver the services you need to keep your landscape up and running
For the System Landscape Directory as part of an SAP NetWeaver PI 71 landscape consider the following
aspects
Part of SAP NetWeaver PI 71 is a new version of the System Landscape Directory It is automatically
included in every SAP NetWeaver 71 system with usage type AS Java It offers enhanced functions
such as a full automatic synchronization mechanism for all data stored in it That is both data
delivered by data suppliers and data entered or changed manually in the System Landscape
Directory can be synchronized automatically This synchronization offers the following
A fully automated mechanism so no user interaction is required and conflicts are resolved
automatically
Asynchronous propagation of information so some nodes may be down temporarily
Communication over HTTP protocol
Uni- and bi-directional synchronization
Depending on your use case the full automatic synchronization could significantly reduce manual
synchronization effort
For SAP NetWeaver PI 71 the configuration of the system landscape directory and its data suppliers
is already included in the standard implementation procedure with SAPinst For existing systems
you only have to perform some quick and easy configuration actions to start operating the system
landscape directory server in an AS Java system
For SAP NetWeaver PI 71 you have the following options concerning SLD
Option 1
Run SAP NetWeaver PI 71 against an existing SLD running on SAP NetWeaver 70 We only
recommend this for upgrades from SAP NetWeaver 70 if you have a central SLD in operation
not running on one of your PI systems
Option 2
Use the SLD included in an SAP NetWeaver PI 71 system We recommend this option for new
installations and upgrades from older releases than SAP NetWeaver 70 due to the enhanced
functions and improved performance of SLD 71
NOTE
If you already have a central SLD running on SAP NetWeaver 70 in operation you could run
two SLD versions in parallel ndash SLD running on SAP NetWeaver 71 for your PI systems and
SLD running on SAP NetWeaver 70 for all other systemsuse cases This way your SAP
5 System Landscape
52 Shared Services
4456 PUBLIC 2011-04-15
NetWeaver PI 71 systems would benefit from the new features while it would be easy to set
up and operate such an SLD landscape For this purpose you could use the new fully
automatic synchronization This feature enables the automatic forwarding of all SLD data
from an SLD running on SAP NetWeaver 70 to an SLD running on SAP NetWeaver 71 As a
result there is no need to adapt most existing systems as their SLD data suppliers could still
send their data to the central SLD In brief the following steps would be required
1 Put SLD in a PI system into operation (part of standard implementation procedure)
2 Configure PI systems to use the new SLD (part of standard implementation procedure
for new PI systems)
3 Set up the fully automatic synchronization from your old SLD to your new SLD
As soon as an upgrade or an installation of a standalone AS Java 71 system is available you
could move your central SLD also to SAP NetWeaver 71 Then you could optionally shift
your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems
Figure 8
We recommend that you use a Domain Name System (DNS) alias so that you are able to switch to
another System Landscape Directory easily For example if customers build a new landscape they
normally start with a sandbox environment Over time more and more environments are set up
Once the production environment is in place move the System Landscape Directory there To do
this you can configure a new System Landscape Directory in the production environment
synchronize it with the old System Landscape directory and switch to the new one
Topology
Apart from the considerations above the System Landscape Directory offers several topology options
with different grades of availability at the expense of low administration and operation effort There is
no generic rule therefore on how to set up a System Landscape Directory in your system landscape
To find the topology and synchronization strategy for the System Landscape Directory that fits your
requirements concerning the System Landscape Directory availability (and hence the availability of
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4556
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
Implementation PhaseStep Description Documentation
system landscape data in SAP Solution Manager is maintained correctlyLandscape Verification 10 which is an add-on to SAP Solution Manager can support you in maintaining your system landscape data The use of this tool is optional
Landscape Verification http
wwwsdnsapcom irj
sdn alm-update-
management link Landscape Verification under Related Areas on Upgrade and Update Management (in the right column)
SAP Note 1468605 (Installation of Landscape Verification)
Maintaining System Landscape Information [page 47]Note that the information provided in this section is based on SAP Solution Manager 70 EHP1 SP23
2System Preparation
Prepare your system as described in the documentation for example perform OS DB specific preparations and the PI-specific preparations
Update Guide ndash Update of SAP Systems with Software Update Manager sections Planning and Preparation
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
3Software Download
Select and download the software packages in either of the following ways Automatic calculation Create
a maintenance transaction in the Maintenance Optimizer and choose the Calculate Files Automatically option
Manual Selection Create a maintenance transaction in the Maintenance Optimizer and choose the Select Files Manually option You then can select the files manually using the SP Stack application in SAP Service Marketplace
NOTE
You have to download the stack configuration file manually after you have selected all files in the SP Stack
httphelpsapcom SAP Solutions SAP Solution Manager
SAP Solution Manager 70 EHP1 ltSPgtChange Request Management and
Change Control Maintenance Optimizer Maintenance Procedure Scenarios
For information about the automatic calculation see Maintenance Transaction with Installation of an Enhancement PackageFor information about the manual selection and approval process see section Approve and Download Files in Download Basket
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
3056 PUBLIC 2011-04-15
Implementation PhaseStep Description Documentation
application Choose Generate Stack XML and save the file
4Enhancement Package Installation
Run Software Update Manager to update your system with the selected software packages
Update Guide ndash Update of SAP Systems with Software Update Manager
5Follow-Up Steps
Perform technical and PI-specific follow-up activities after the enhancement package installation is done
Update Guide ndash Update of SAP Systems with Software Update Manager section Follow-Up Activities
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
6Configuration
Configure newly installed enhancement package functions using SAP Solution Manager content
See Systems with Usage Types [page 16] section Configuration of Systems with Usage Types
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 3156
This page is left blank for documents that are printed on both sides
5 System Landscape
51 Planning Your System Landscape
The installable software units that make up your system landscape depend on the functions that you
want to implement For information about the features see systems [page 16] standalone engines [page 19]
and clients [page 21]
In addition you have to determine the required shared services [page 35] (such as SAP Solution Manager
or SAP NetWeaver Administrator) that run on central systems in your system landscape and the
landscape aspects relevant for their implementation
In the following you will find general information that you should consider when planning your system
landscape
Sizing
You have to map systems and standalone engines to hosts after you have a clear picture of the following
Which systems and standalone engines you require
How many systems you require and how you want to use each of these systems
NOTE
No general guideline can be given for the sizing of your landscape since this relies heavily on your
requirements You should therefore perform this task together with your hardware partner and
your technical consultant
For information about sizing your systems you can use the following information sources
Your first point of reference is the Quick Sizer
SAP built the Quick Sizer as an online sizing questionnaire Internet application in close cooperation
with its hardware partners This tool delivers general sizing categories based on your volume load
estimates The results provide an objective basis for sizing independent of platform and
configuration
For more information see SAP Service Marketplace at
httpservicesapcomsizing for the SAP NetWeaver PI 71 sizing guide available under
Sizing Guidelines Business Suite amp Services
httpservicesapcomquicksizer for more information and access to the tool itself
Also consider the following important aspects concerning sizing
High availability
5 System Landscape
51 Planning Your System Landscape
2011-04-15 PUBLIC 3356
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Technical Infrastructure High Availability
Unicode
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Internationalization
Contact your hardware partner to find out the appropriate number of sized hosts
The platform-independent abstract results of the Quick Sizer can be used by any of our hardware
partners to create a concrete offer SAP itself does not make any hardware recommendations the
responsibility for sizing and detailed hardware configuration lies with the hardware partners
Figure 6 Example of Mapping of Systems and Standalone Engines to Three Hosts
NOTE
Optionally you could also distribute single systems to multiple hosts For example you could
decide to install the database instance of an SAP system on a separate host for performance
reasons or distribute other system instances to achieve high availability
To provide a mapping that fits your required functions and performance your hardware partner
and your technical consultant have to identify the number of required instances of SAP NetWeaver
find out how to distribute these instances to hosts and what functions will run on which instance
Therefore the hardware partner and the technical consultant have to consider many different
aspects such as
Number of required SAPS (SAP Application Benchmark Performance Standard) for each
system (provided by Quick Sizer)
Landscape-relevant aspects concerning security For more information see the SAP Security
Guide in the SAP Library [page 12] at Administratoracutes Guide Security Guide
Landscape-relevant aspects concerning scalability high availability operation and software
life-cycle management
5 System Landscape
51 Planning Your System Landscape
3456 PUBLIC 2011-04-15
For more information about relevant aspects for the mapping of systems to hosts see the document
Technical Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
Scaling and Distribution Options
You may need to design your system landscape for a large number of users SAP NetWeaver PI offers
you different means of scalability The following list provides you with some examples
You could install multiple systems of one type and use them for different purposes
You could scale every system by installing dialog instances or by distributing the database instance
For more information about distribution options on the instance level see the Technical
Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
For every SAP system you could additionally install Web Dispatcher For more information see
the SAP Library [page 12] at FunctionndashOriented View Application Server Infrastructure SAP Web
Dispatcher
You could further distribute certain standalone engines ndash for example Search and Classification
(TREX) is based on a flexible architecture that supports a distributed installation For more
information see the Technical Infrastructure Guide ndash SAP NetWeaver PI 71 available in SAP Service
Marketplace at httpservicesapcominstallNWPI71
52 Shared Services
You normally run shared services on central systems in your system landscape The following features
could be used for SAP NetWeaver Process Integration to realize shared services
SAP Solution Manager
Used to implement train test maintain monitor control change and manage incidents of your
SAP solution system landscape (open end-to-end application management)
As of SAP Solution Manager (70) 40 Support Package 15 SAP Solution Manager has become the
platform for SAPs end-to-end solution operations strategy Functions for complete application
management has been combined with administrative tools and has been merged in newly created
role based work centers
NOTE
Be aware that you require an SAP Solution Manager system to install or upgrade to SAP
NetWeaver 70 and higher An SAP Solution Manager system is required to generate the SAP
Solution Manager key needed during the installation or upgrade process Without this key
the installation or upgrade process cannot continue
For SAP NetWeaver Process Integration you require SAP Solution Manager 70
For more information see SAP Note 805390
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3556
Solution Manager Diagnostics
An integral part of SAP Solution Manager that is running as a Java application on the Java stack of
SAP Solution Manager 70 Solution Manager Diagnostics is used to analyze the root cause of
incidents in your landscape in an efficient and safe way Before Go-Live Solution Manager
Diagnostics has to be set up and made accessible remotely
SAP NetWeaver Administrator
SAP NetWeaver Administrator is the central administration component which is used for
monitoring and administering Java applications It is included in SAP NetWeaver systems with AS
Java
SAP NetWeaver Administrator exists in the following flavors
A local mode which runs out of the box and which focuses on administrating the underlying
SAP NetWeaver AS Java
NOTE
For a SAP NetWeaver PI 71 it has a special role which you need to activate using a
configuation wizard
A central mode which has to be configured before use and which deals with the system
landscape management
SAP has decided to merge the central mode of SAP NetWeaver Administrator into the new work
centers available as of SAP Solution Manager 70 SP 15 Thus it can be used in an administrative
context together with non-Java-based administration tools Although the central mode of SAP
NetWeaver Administrator will be still available for some time SAP will not develop this tool any
further SAP focuses on optimizing the administrative work centers of SAP Solution Manager
instead
The local mode of SAP NetWeaver Administrator stays untouched It is available for current and
future releases of SAP NetWeaver
SAP Central Process Scheduling by Redwood
SAP Central Process Scheduling application by Redwood enables central job scheduling and job
monitoring of current and old releases of AS ABAP systems (as of Basis Release 31) This application
is fully integrated in SAP NetWeaver Depending on the business needs SAP business applications
are the initial trigger for scheduled activities You can now manage jobs and job chains conveniently
using a graphical user interface
System Landscape Directory
The System Landscape Directory is the central directory of system landscape information relevant
for the management of your software life-cycle It contains a description of your system landscape
(that is software components that are currently installed) and a repository of software components
that can theoretically be installed in your landscape (such as the software components available
from SAP)
Adaptive Computing Controller
5 System Landscape
52 Shared Services
3656 PUBLIC 2011-04-15
The Adaptive Computing Controller enables users to control an adaptive computing landscape
from a single point through observation operation and dynamic resource distribution With
adaptive computing hardware software and system services are able to adapt to changing business
needs In the Adaptive Computing Controller the run-time data of logical and physical landscapes
can be monitored application services can be startedstoppedrelocated and hardware resources
can be assigned to application services The operation can also be mass executed and be planned as
tasks to be executed
For more information about the installation of the Adaptive Computing Controller tool see the
document Installation Guide ndash Adaptive Computing Controller in SAP NetWeaver 71 available on SAP Service
Marketplace at httpservicesapcominstallNWPI71
For more information about Adaptive Computing in general see httpsdnsapcomirj
sdnadaptive
521 Use Cases
You can use the applications and tools described above for use cases that are normally performed
centrally The following sections describe these use cases
5211 End-to-End Solution Operations
Running business applications through their complete life-cycle is a challenge Therefore SAP has
started the Run SAP methodology for implementing End-to-End Solution Operations Based on a set
of SAP standards a roadmap and a package for training and certification Run SAP helps customers to
facilitate End-to-End Solution Operations
You can download the SAP standards for Solution Operations from SAP Service Marketplace at http
servicesapcomsupportstandards They describe roles customers typically have in their IT
environment For optimal role support SAP has grouped existing and new functions in SAP Solution
Manager work centers as of SAP Solution Manager 70 Support Package 15 Operations aspects are fully
covered by adding administrative functions for SAP NetWeaver as well Work centers are ABAP Web
Dynpro-based applications They offer the following advantages
Easy to use similar look and feel
Context transfer while jumping from one work center into another
Logical grouping of tools for a certain area
Simple authorization concept
Easy to expand
Each IT role belongs to one or more work centers For instance the Technical Administrator IT role is
covered by the work centers for System Monitoring System Administration and Landscape Management
The following work centers are available
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3756
Business Process Operations
Change Management
Root Cause Analysis
Implementation Upgrade
Incident Management
Test Management
Job Management
System Landscape Management
Solution Documentation Assistant
SAP Engagement and Service Delivery
SAP Solution Manager Administration
System Administration
System Monitoring
My Home is the central point of access to all important data of almost all work centers in SAP Solution
Manager
5212 Support Infrastructure
A key requirement for effective support of IT solutions is the ability to perform root cause analysis with
speed and efficiency
With SAP Solution Manager SAP has long had an infrastructure in place for its ABAP applications that
efficiently supports SAP solutions This helps ensure the high availability and smooth running of
business processes For more information see the SAP Solution Manager section
With Solution Manager Diagnostics this knowledge has been extended to Java applications If for
example homegrown Java applications cause instability Solution Manager Diagnostics helps trace the
cause to eradicate the problem rapidly Solution Manager Diagnostics is fully integrated into SAP
Solution Manager 70 Solution Manager Diagnostics also contains two third-party tools CArsquos Wily
Introscopereg for measuring performance as well as troubleshooting problems of the Java EE Engine
and applications running on it and Mercury Loadrunnerreg which enables SAP Support to produce a
defined load in the SAP solution landscape remotely For more information see Solution Manager
Diagnostics [page 43]
The support infrastructure provides SAP Support with safe access to your productive landscape for safe
root cause analysis so ensuring that SAP Support does not change your landscape inadvertently You
require a support infrastructure to run SAP NetWeaver
The following figure shows the overall infrastructure including SAP NetWeaver administration tools
that are used by administrators or operators at the customer site
5 System Landscape
52 Shared Services
3856 PUBLIC 2011-04-15
Landscape Aspects
If you use SAP NetWeaver Process Integration 71 productively besides SAP Solution Manager (as a
central support platform) you have to set up Solution Manager Diagnostics for supportability reasons
Implementation Sequence
For information about the implementation of the support infrastructure see the document Master
Guide ndash SAP Solution Manager 70 available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution Manager ltReleasegt
5213 Collection of Landscape Data
Amongst other applications and services the support infrastructure and the SAP NetWeaver
administration tools rely on system landscape data
For SAP NetWeaver PI 71 you have to run non-ABAP components in your solution landscape
Therefore the System Landscape Directory is mandatory The landscape data that is automatically
gathered by the System Landscape Directory is replicated to SAP Solution Manager There are several
topology options for the System Landscape Directory They offer different grades of availability
administration and operation effort
For more information see the System Landscape Directory section
5214 Authentication and Single Sign-On
Before implementing your system landscape plan how to implement authentication and how to
integrate different systems into a Single Sign-On landscape Single Sign-On reduces complexity for end
users saving them valuable time while also reducing administration effort for resetting passwords
thereby contributing to TCO reduction
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
5215 Integrated User and Access Management
In a system landscape containing a combination of ABAP and Java components we recommend that
you integrate your user and access management so that you can use the same user data across different
systems administer this data centrally and control access to data SAPs mature fine-grained
authorization concept allows detailed control of access rights SAP NetWeaver provides both ABAP and
Java-based user management solutions The user management solution that you use to administer
your user data depends on factors such as the type of systems that are running in your landscape
If you want to use central user administration we recommend that you run it in a non-production
system If you do not have a central user administration yet you can for example realize it in the SAP
Solution Manager system
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3956
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
522 Examples for the Overall System Landscape of Shared Services
In this section we provide examples of how shared services can be set up depending on the system
landscape they are intended for The following examples aggregate the landscape aspects given in the
Use Cases section
NOTE
The following sections and the figure mostly do not show information about the life-cycle of
shared services For example you may also need a development and testquality assurance system
for SAP Solution Manager You should consider this aspect in addition to the information given
in this section based on your requirements
Small and MediumndashSized Customer Landscapes with Java
As you use Java productively for SAP NetWeaver PI 71 besides SAP Solution Manager you have to set
up additional components for optimal monitoring administration and support Solution Manager
Diagnostics and the central mode of SAP NetWeaver Administrator are already fully integrated into
SAP Solution Manager 70 as the central operations hub For SAP Process Integration you must also
set up SAP NetWeaver Administrator with a special role
We recommend that you do not install SAP Central Process Scheduling in the SAP Solution Manager
system You have to set up and operate the system which hosts your productive scheduler as a mission
critical system
In the SAP Solution Manager system you should set up a local System Landscape Directory in addition
to a central runtime System Landscape Directory This way you have a clear separation between your
management system (SAP Solution Manager) and managed systems in your landscape In addition
SAP Solution Manager then does not rely on a System Landscape Directory running in the production
environment For this setup configure the SLD data suppliers of your SAP Solution Manager system
to send data to the central runtime System Landscape Directory In addition configure automatic
bridge forwarding from your runtime System Landscape Directory to the local System Landscape
Directory For more information see the Planning Guide - System Landscape Directory
If you want to use a central system for Adobe Document Services we recommend that you install a
dedicated system for this purpose in your production environment For detailed information about
the sizing of the system for the different use cases see the Sizing Guide for Adobe Document Services at
SAP Service Marketplace at httpservicesapcomsizing Sizing Guidelines Solutions amp
Platform
We recommend that you start with this centralized SAP Solution Manager approach as depicted in the
following figure
5 System Landscape
52 Shared Services
4056 PUBLIC 2011-04-15
Figure 7 Single SAP Solution Manager Landscape
Large Customer Landscapes with Java
Large customers who have environments in their landscape that are large and distributed administered
by different groups or separated for security reasons can consider a distributed operations setup In
addition to the centralized setup described for small- and medium-sized customers above large
customers can put parts of the central management functions on extra hosts or systems for performance
or policy reasons You have the following options for a distributed setup
You may set up an extra system or client for Central User Administration (CUA)
The Change and Transport System (CTS) can run on an extra system However it is not
performance- or data-intensive
You may set up an extra system for central CCMS monitoring Depending on the customizing
and on the landscape size central CCMS may generate a lot of system load You can connect a
separate central CCMS to SAP Solution Manager for displaying alerts in the alert inbox of the System
Monitoring work center
You can use a separate SAP NetWeaver 70 system with usage type BI together with SAP Solution
Manager This may make sense with respect to the amount of landscape management data that is
stored for reporting purposes The amount of data strongly depends on the data granularity
storage time frame and landscape size
You can easily put Wily Introscope Enterprise Manager on an separate host
Other aspects described above for small- and medium-customers (such as the setup of the System
Landscape Directory) are also valid for large customers
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4156
523 Feature Details
This section provides further information about the features described above
5231 SAP Solution Manager
SAP provides you with SAP Solution Manager as the strategic application management platform and
to enable the collaboration between you and SAP You need to install at least one productive SAP
Solution Manager in your system landscape To ensure the availability of this application management
platform an SAP Solution Manager system is technically required to install or upgrade to SAP
NetWeaver 70 or higher If you are already using SAP Solution Manager you can also use it to manage
the solution you build with SAP NetWeaver In this case we highly recommend that you update SAP
Solution Manager to the latest version
As of SAP Solution Manager 70 SP15 you can use the newly created work centers
NOTE
During the SAP system installation or upgrade process you are prompted to enter the SAP
Solution Manager key An SAP Solution Manager system is required to generate this key Without
this key the installation or upgrade process cannot continue
You may generate all needed keys for your entire system landscape (development quality
assurance and production system) in one SAP Solution Manager system In case you plan to install
several solution landscapes (for example in different countries) one SAP Solution Manager
system is still sufficient
For more information see SAP Note 805390
It is possible to install multiple SAP Solution Managers If you do so they should host separate business
solutions
If you want to reduce the risk of unavailability you should not install SAP Solution Manager as a central
component Instead you can operate a 2-system-landscape with both a test and production
environment of SAP Solution Manager (especially if you are using time-critical functions like Support
Desk) If you also develop your own content a 3-system-landscape with a development test and
production environment is recommended
For more information about SAP Solution Manager see the following table
Topic Where to Find More Information
System infrastructure scenarios installation and configuration of SAP Solution Manager
Master Guide ndash SAP Solution Manager available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution ManagerltReleasegt
Benefits and usage scenarios SAP Solution Manager ndash Learning Maps available on SAP Service Marketplace at http
5 System Landscape
52 Shared Services
4256 PUBLIC 2011-04-15
Topic Where to Find More Informationservicesapcomrkt-solman or https
servicesapcomsolutionmanager
Additional information See SAP Service Marketplace at http
servicesapcomsolutionmanager
5232 Solution Manager Diagnostics
Solution Manager Diagnostics provides efficient and safe root-cause analysis of incidents in customer
solutions powered by SAP NetWeaver It can help monitor on operating systems databases Java
application activities performance and logs It also supports the reporting of software and
configuration changes that can lead to malfunctions and errors
You must run one Solution Manager Diagnostics within your SAP solution landscape if you run
applications based on SAP NetWeaver systems with usage type AS Java Agents are responsible for
delivering the data from all productive hosts within your system landscape to the Solution Manager
Diagnostics system
CAUTION
SAP Support performs root-cause analysis on incoming incidents with Solution Manager
Diagnostics Not installing and configuring this support infrastructure results in a dramatically
reduced service level
Solution Manager Diagnostics is fully integrated into SAP Solution Manager 70
Solution Manager Diagnostics also contains Wily Introscope (Display Server and Agent part) for
measuring performance as well as to troubleshoot problems of Non-ABAP applications Wily Introscope
is heavily used for troubleshooting applications running on AS Java
SAP has signed a distribution agreement for Wily Introscope SAP customers are allowed to use this
tool in a preconfigured way
For more information about Solution Manager Diagnostics and an FAQ list see SAP Service Marketplace
at httpservicesapcomdiagnostics
5233 System Landscape Directory
The System Landscape Directory (SLD) of SAP NetWeaver is the central directory of system landscape
information relevant for the management of your software life-cycle
NOTE
Note that the abbreviation SLD is not intended to define a product since the System Landscape
Directory is part of SAP NetWeaver This abbreviation is solely intended to improve readability
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4356
The System Landscape Directory contains a description of your system landscape (that is software
components that are currently installed) and a repository of software components that can
theoretically be installed in your landscape (such as the software components available from SAP)
Since this data gets updated automatically the System Landscape Directory provides reliable and up-
to-date system landscape information with as little effort for you as possible In this way the System
Landscape Directory acts as a central information provider for SAP and third-party tools that use this
data to deliver the services you need to keep your landscape up and running
For the System Landscape Directory as part of an SAP NetWeaver PI 71 landscape consider the following
aspects
Part of SAP NetWeaver PI 71 is a new version of the System Landscape Directory It is automatically
included in every SAP NetWeaver 71 system with usage type AS Java It offers enhanced functions
such as a full automatic synchronization mechanism for all data stored in it That is both data
delivered by data suppliers and data entered or changed manually in the System Landscape
Directory can be synchronized automatically This synchronization offers the following
A fully automated mechanism so no user interaction is required and conflicts are resolved
automatically
Asynchronous propagation of information so some nodes may be down temporarily
Communication over HTTP protocol
Uni- and bi-directional synchronization
Depending on your use case the full automatic synchronization could significantly reduce manual
synchronization effort
For SAP NetWeaver PI 71 the configuration of the system landscape directory and its data suppliers
is already included in the standard implementation procedure with SAPinst For existing systems
you only have to perform some quick and easy configuration actions to start operating the system
landscape directory server in an AS Java system
For SAP NetWeaver PI 71 you have the following options concerning SLD
Option 1
Run SAP NetWeaver PI 71 against an existing SLD running on SAP NetWeaver 70 We only
recommend this for upgrades from SAP NetWeaver 70 if you have a central SLD in operation
not running on one of your PI systems
Option 2
Use the SLD included in an SAP NetWeaver PI 71 system We recommend this option for new
installations and upgrades from older releases than SAP NetWeaver 70 due to the enhanced
functions and improved performance of SLD 71
NOTE
If you already have a central SLD running on SAP NetWeaver 70 in operation you could run
two SLD versions in parallel ndash SLD running on SAP NetWeaver 71 for your PI systems and
SLD running on SAP NetWeaver 70 for all other systemsuse cases This way your SAP
5 System Landscape
52 Shared Services
4456 PUBLIC 2011-04-15
NetWeaver PI 71 systems would benefit from the new features while it would be easy to set
up and operate such an SLD landscape For this purpose you could use the new fully
automatic synchronization This feature enables the automatic forwarding of all SLD data
from an SLD running on SAP NetWeaver 70 to an SLD running on SAP NetWeaver 71 As a
result there is no need to adapt most existing systems as their SLD data suppliers could still
send their data to the central SLD In brief the following steps would be required
1 Put SLD in a PI system into operation (part of standard implementation procedure)
2 Configure PI systems to use the new SLD (part of standard implementation procedure
for new PI systems)
3 Set up the fully automatic synchronization from your old SLD to your new SLD
As soon as an upgrade or an installation of a standalone AS Java 71 system is available you
could move your central SLD also to SAP NetWeaver 71 Then you could optionally shift
your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems
Figure 8
We recommend that you use a Domain Name System (DNS) alias so that you are able to switch to
another System Landscape Directory easily For example if customers build a new landscape they
normally start with a sandbox environment Over time more and more environments are set up
Once the production environment is in place move the System Landscape Directory there To do
this you can configure a new System Landscape Directory in the production environment
synchronize it with the old System Landscape directory and switch to the new one
Topology
Apart from the considerations above the System Landscape Directory offers several topology options
with different grades of availability at the expense of low administration and operation effort There is
no generic rule therefore on how to set up a System Landscape Directory in your system landscape
To find the topology and synchronization strategy for the System Landscape Directory that fits your
requirements concerning the System Landscape Directory availability (and hence the availability of
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4556
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
Implementation PhaseStep Description Documentation
application Choose Generate Stack XML and save the file
4Enhancement Package Installation
Run Software Update Manager to update your system with the selected software packages
Update Guide ndash Update of SAP Systems with Software Update Manager
5Follow-Up Steps
Perform technical and PI-specific follow-up activities after the enhancement package installation is done
Update Guide ndash Update of SAP Systems with Software Update Manager section Follow-Up Activities
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
6Configuration
Configure newly installed enhancement package functions using SAP Solution Manager content
See Systems with Usage Types [page 16] section Configuration of Systems with Usage Types
4 SOA-Based Integration Use Case
44 Process Sequence Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 71 System
2011-04-15 PUBLIC 3156
This page is left blank for documents that are printed on both sides
5 System Landscape
51 Planning Your System Landscape
The installable software units that make up your system landscape depend on the functions that you
want to implement For information about the features see systems [page 16] standalone engines [page 19]
and clients [page 21]
In addition you have to determine the required shared services [page 35] (such as SAP Solution Manager
or SAP NetWeaver Administrator) that run on central systems in your system landscape and the
landscape aspects relevant for their implementation
In the following you will find general information that you should consider when planning your system
landscape
Sizing
You have to map systems and standalone engines to hosts after you have a clear picture of the following
Which systems and standalone engines you require
How many systems you require and how you want to use each of these systems
NOTE
No general guideline can be given for the sizing of your landscape since this relies heavily on your
requirements You should therefore perform this task together with your hardware partner and
your technical consultant
For information about sizing your systems you can use the following information sources
Your first point of reference is the Quick Sizer
SAP built the Quick Sizer as an online sizing questionnaire Internet application in close cooperation
with its hardware partners This tool delivers general sizing categories based on your volume load
estimates The results provide an objective basis for sizing independent of platform and
configuration
For more information see SAP Service Marketplace at
httpservicesapcomsizing for the SAP NetWeaver PI 71 sizing guide available under
Sizing Guidelines Business Suite amp Services
httpservicesapcomquicksizer for more information and access to the tool itself
Also consider the following important aspects concerning sizing
High availability
5 System Landscape
51 Planning Your System Landscape
2011-04-15 PUBLIC 3356
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Technical Infrastructure High Availability
Unicode
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Internationalization
Contact your hardware partner to find out the appropriate number of sized hosts
The platform-independent abstract results of the Quick Sizer can be used by any of our hardware
partners to create a concrete offer SAP itself does not make any hardware recommendations the
responsibility for sizing and detailed hardware configuration lies with the hardware partners
Figure 6 Example of Mapping of Systems and Standalone Engines to Three Hosts
NOTE
Optionally you could also distribute single systems to multiple hosts For example you could
decide to install the database instance of an SAP system on a separate host for performance
reasons or distribute other system instances to achieve high availability
To provide a mapping that fits your required functions and performance your hardware partner
and your technical consultant have to identify the number of required instances of SAP NetWeaver
find out how to distribute these instances to hosts and what functions will run on which instance
Therefore the hardware partner and the technical consultant have to consider many different
aspects such as
Number of required SAPS (SAP Application Benchmark Performance Standard) for each
system (provided by Quick Sizer)
Landscape-relevant aspects concerning security For more information see the SAP Security
Guide in the SAP Library [page 12] at Administratoracutes Guide Security Guide
Landscape-relevant aspects concerning scalability high availability operation and software
life-cycle management
5 System Landscape
51 Planning Your System Landscape
3456 PUBLIC 2011-04-15
For more information about relevant aspects for the mapping of systems to hosts see the document
Technical Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
Scaling and Distribution Options
You may need to design your system landscape for a large number of users SAP NetWeaver PI offers
you different means of scalability The following list provides you with some examples
You could install multiple systems of one type and use them for different purposes
You could scale every system by installing dialog instances or by distributing the database instance
For more information about distribution options on the instance level see the Technical
Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
For every SAP system you could additionally install Web Dispatcher For more information see
the SAP Library [page 12] at FunctionndashOriented View Application Server Infrastructure SAP Web
Dispatcher
You could further distribute certain standalone engines ndash for example Search and Classification
(TREX) is based on a flexible architecture that supports a distributed installation For more
information see the Technical Infrastructure Guide ndash SAP NetWeaver PI 71 available in SAP Service
Marketplace at httpservicesapcominstallNWPI71
52 Shared Services
You normally run shared services on central systems in your system landscape The following features
could be used for SAP NetWeaver Process Integration to realize shared services
SAP Solution Manager
Used to implement train test maintain monitor control change and manage incidents of your
SAP solution system landscape (open end-to-end application management)
As of SAP Solution Manager (70) 40 Support Package 15 SAP Solution Manager has become the
platform for SAPs end-to-end solution operations strategy Functions for complete application
management has been combined with administrative tools and has been merged in newly created
role based work centers
NOTE
Be aware that you require an SAP Solution Manager system to install or upgrade to SAP
NetWeaver 70 and higher An SAP Solution Manager system is required to generate the SAP
Solution Manager key needed during the installation or upgrade process Without this key
the installation or upgrade process cannot continue
For SAP NetWeaver Process Integration you require SAP Solution Manager 70
For more information see SAP Note 805390
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3556
Solution Manager Diagnostics
An integral part of SAP Solution Manager that is running as a Java application on the Java stack of
SAP Solution Manager 70 Solution Manager Diagnostics is used to analyze the root cause of
incidents in your landscape in an efficient and safe way Before Go-Live Solution Manager
Diagnostics has to be set up and made accessible remotely
SAP NetWeaver Administrator
SAP NetWeaver Administrator is the central administration component which is used for
monitoring and administering Java applications It is included in SAP NetWeaver systems with AS
Java
SAP NetWeaver Administrator exists in the following flavors
A local mode which runs out of the box and which focuses on administrating the underlying
SAP NetWeaver AS Java
NOTE
For a SAP NetWeaver PI 71 it has a special role which you need to activate using a
configuation wizard
A central mode which has to be configured before use and which deals with the system
landscape management
SAP has decided to merge the central mode of SAP NetWeaver Administrator into the new work
centers available as of SAP Solution Manager 70 SP 15 Thus it can be used in an administrative
context together with non-Java-based administration tools Although the central mode of SAP
NetWeaver Administrator will be still available for some time SAP will not develop this tool any
further SAP focuses on optimizing the administrative work centers of SAP Solution Manager
instead
The local mode of SAP NetWeaver Administrator stays untouched It is available for current and
future releases of SAP NetWeaver
SAP Central Process Scheduling by Redwood
SAP Central Process Scheduling application by Redwood enables central job scheduling and job
monitoring of current and old releases of AS ABAP systems (as of Basis Release 31) This application
is fully integrated in SAP NetWeaver Depending on the business needs SAP business applications
are the initial trigger for scheduled activities You can now manage jobs and job chains conveniently
using a graphical user interface
System Landscape Directory
The System Landscape Directory is the central directory of system landscape information relevant
for the management of your software life-cycle It contains a description of your system landscape
(that is software components that are currently installed) and a repository of software components
that can theoretically be installed in your landscape (such as the software components available
from SAP)
Adaptive Computing Controller
5 System Landscape
52 Shared Services
3656 PUBLIC 2011-04-15
The Adaptive Computing Controller enables users to control an adaptive computing landscape
from a single point through observation operation and dynamic resource distribution With
adaptive computing hardware software and system services are able to adapt to changing business
needs In the Adaptive Computing Controller the run-time data of logical and physical landscapes
can be monitored application services can be startedstoppedrelocated and hardware resources
can be assigned to application services The operation can also be mass executed and be planned as
tasks to be executed
For more information about the installation of the Adaptive Computing Controller tool see the
document Installation Guide ndash Adaptive Computing Controller in SAP NetWeaver 71 available on SAP Service
Marketplace at httpservicesapcominstallNWPI71
For more information about Adaptive Computing in general see httpsdnsapcomirj
sdnadaptive
521 Use Cases
You can use the applications and tools described above for use cases that are normally performed
centrally The following sections describe these use cases
5211 End-to-End Solution Operations
Running business applications through their complete life-cycle is a challenge Therefore SAP has
started the Run SAP methodology for implementing End-to-End Solution Operations Based on a set
of SAP standards a roadmap and a package for training and certification Run SAP helps customers to
facilitate End-to-End Solution Operations
You can download the SAP standards for Solution Operations from SAP Service Marketplace at http
servicesapcomsupportstandards They describe roles customers typically have in their IT
environment For optimal role support SAP has grouped existing and new functions in SAP Solution
Manager work centers as of SAP Solution Manager 70 Support Package 15 Operations aspects are fully
covered by adding administrative functions for SAP NetWeaver as well Work centers are ABAP Web
Dynpro-based applications They offer the following advantages
Easy to use similar look and feel
Context transfer while jumping from one work center into another
Logical grouping of tools for a certain area
Simple authorization concept
Easy to expand
Each IT role belongs to one or more work centers For instance the Technical Administrator IT role is
covered by the work centers for System Monitoring System Administration and Landscape Management
The following work centers are available
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3756
Business Process Operations
Change Management
Root Cause Analysis
Implementation Upgrade
Incident Management
Test Management
Job Management
System Landscape Management
Solution Documentation Assistant
SAP Engagement and Service Delivery
SAP Solution Manager Administration
System Administration
System Monitoring
My Home is the central point of access to all important data of almost all work centers in SAP Solution
Manager
5212 Support Infrastructure
A key requirement for effective support of IT solutions is the ability to perform root cause analysis with
speed and efficiency
With SAP Solution Manager SAP has long had an infrastructure in place for its ABAP applications that
efficiently supports SAP solutions This helps ensure the high availability and smooth running of
business processes For more information see the SAP Solution Manager section
With Solution Manager Diagnostics this knowledge has been extended to Java applications If for
example homegrown Java applications cause instability Solution Manager Diagnostics helps trace the
cause to eradicate the problem rapidly Solution Manager Diagnostics is fully integrated into SAP
Solution Manager 70 Solution Manager Diagnostics also contains two third-party tools CArsquos Wily
Introscopereg for measuring performance as well as troubleshooting problems of the Java EE Engine
and applications running on it and Mercury Loadrunnerreg which enables SAP Support to produce a
defined load in the SAP solution landscape remotely For more information see Solution Manager
Diagnostics [page 43]
The support infrastructure provides SAP Support with safe access to your productive landscape for safe
root cause analysis so ensuring that SAP Support does not change your landscape inadvertently You
require a support infrastructure to run SAP NetWeaver
The following figure shows the overall infrastructure including SAP NetWeaver administration tools
that are used by administrators or operators at the customer site
5 System Landscape
52 Shared Services
3856 PUBLIC 2011-04-15
Landscape Aspects
If you use SAP NetWeaver Process Integration 71 productively besides SAP Solution Manager (as a
central support platform) you have to set up Solution Manager Diagnostics for supportability reasons
Implementation Sequence
For information about the implementation of the support infrastructure see the document Master
Guide ndash SAP Solution Manager 70 available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution Manager ltReleasegt
5213 Collection of Landscape Data
Amongst other applications and services the support infrastructure and the SAP NetWeaver
administration tools rely on system landscape data
For SAP NetWeaver PI 71 you have to run non-ABAP components in your solution landscape
Therefore the System Landscape Directory is mandatory The landscape data that is automatically
gathered by the System Landscape Directory is replicated to SAP Solution Manager There are several
topology options for the System Landscape Directory They offer different grades of availability
administration and operation effort
For more information see the System Landscape Directory section
5214 Authentication and Single Sign-On
Before implementing your system landscape plan how to implement authentication and how to
integrate different systems into a Single Sign-On landscape Single Sign-On reduces complexity for end
users saving them valuable time while also reducing administration effort for resetting passwords
thereby contributing to TCO reduction
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
5215 Integrated User and Access Management
In a system landscape containing a combination of ABAP and Java components we recommend that
you integrate your user and access management so that you can use the same user data across different
systems administer this data centrally and control access to data SAPs mature fine-grained
authorization concept allows detailed control of access rights SAP NetWeaver provides both ABAP and
Java-based user management solutions The user management solution that you use to administer
your user data depends on factors such as the type of systems that are running in your landscape
If you want to use central user administration we recommend that you run it in a non-production
system If you do not have a central user administration yet you can for example realize it in the SAP
Solution Manager system
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3956
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
522 Examples for the Overall System Landscape of Shared Services
In this section we provide examples of how shared services can be set up depending on the system
landscape they are intended for The following examples aggregate the landscape aspects given in the
Use Cases section
NOTE
The following sections and the figure mostly do not show information about the life-cycle of
shared services For example you may also need a development and testquality assurance system
for SAP Solution Manager You should consider this aspect in addition to the information given
in this section based on your requirements
Small and MediumndashSized Customer Landscapes with Java
As you use Java productively for SAP NetWeaver PI 71 besides SAP Solution Manager you have to set
up additional components for optimal monitoring administration and support Solution Manager
Diagnostics and the central mode of SAP NetWeaver Administrator are already fully integrated into
SAP Solution Manager 70 as the central operations hub For SAP Process Integration you must also
set up SAP NetWeaver Administrator with a special role
We recommend that you do not install SAP Central Process Scheduling in the SAP Solution Manager
system You have to set up and operate the system which hosts your productive scheduler as a mission
critical system
In the SAP Solution Manager system you should set up a local System Landscape Directory in addition
to a central runtime System Landscape Directory This way you have a clear separation between your
management system (SAP Solution Manager) and managed systems in your landscape In addition
SAP Solution Manager then does not rely on a System Landscape Directory running in the production
environment For this setup configure the SLD data suppliers of your SAP Solution Manager system
to send data to the central runtime System Landscape Directory In addition configure automatic
bridge forwarding from your runtime System Landscape Directory to the local System Landscape
Directory For more information see the Planning Guide - System Landscape Directory
If you want to use a central system for Adobe Document Services we recommend that you install a
dedicated system for this purpose in your production environment For detailed information about
the sizing of the system for the different use cases see the Sizing Guide for Adobe Document Services at
SAP Service Marketplace at httpservicesapcomsizing Sizing Guidelines Solutions amp
Platform
We recommend that you start with this centralized SAP Solution Manager approach as depicted in the
following figure
5 System Landscape
52 Shared Services
4056 PUBLIC 2011-04-15
Figure 7 Single SAP Solution Manager Landscape
Large Customer Landscapes with Java
Large customers who have environments in their landscape that are large and distributed administered
by different groups or separated for security reasons can consider a distributed operations setup In
addition to the centralized setup described for small- and medium-sized customers above large
customers can put parts of the central management functions on extra hosts or systems for performance
or policy reasons You have the following options for a distributed setup
You may set up an extra system or client for Central User Administration (CUA)
The Change and Transport System (CTS) can run on an extra system However it is not
performance- or data-intensive
You may set up an extra system for central CCMS monitoring Depending on the customizing
and on the landscape size central CCMS may generate a lot of system load You can connect a
separate central CCMS to SAP Solution Manager for displaying alerts in the alert inbox of the System
Monitoring work center
You can use a separate SAP NetWeaver 70 system with usage type BI together with SAP Solution
Manager This may make sense with respect to the amount of landscape management data that is
stored for reporting purposes The amount of data strongly depends on the data granularity
storage time frame and landscape size
You can easily put Wily Introscope Enterprise Manager on an separate host
Other aspects described above for small- and medium-customers (such as the setup of the System
Landscape Directory) are also valid for large customers
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4156
523 Feature Details
This section provides further information about the features described above
5231 SAP Solution Manager
SAP provides you with SAP Solution Manager as the strategic application management platform and
to enable the collaboration between you and SAP You need to install at least one productive SAP
Solution Manager in your system landscape To ensure the availability of this application management
platform an SAP Solution Manager system is technically required to install or upgrade to SAP
NetWeaver 70 or higher If you are already using SAP Solution Manager you can also use it to manage
the solution you build with SAP NetWeaver In this case we highly recommend that you update SAP
Solution Manager to the latest version
As of SAP Solution Manager 70 SP15 you can use the newly created work centers
NOTE
During the SAP system installation or upgrade process you are prompted to enter the SAP
Solution Manager key An SAP Solution Manager system is required to generate this key Without
this key the installation or upgrade process cannot continue
You may generate all needed keys for your entire system landscape (development quality
assurance and production system) in one SAP Solution Manager system In case you plan to install
several solution landscapes (for example in different countries) one SAP Solution Manager
system is still sufficient
For more information see SAP Note 805390
It is possible to install multiple SAP Solution Managers If you do so they should host separate business
solutions
If you want to reduce the risk of unavailability you should not install SAP Solution Manager as a central
component Instead you can operate a 2-system-landscape with both a test and production
environment of SAP Solution Manager (especially if you are using time-critical functions like Support
Desk) If you also develop your own content a 3-system-landscape with a development test and
production environment is recommended
For more information about SAP Solution Manager see the following table
Topic Where to Find More Information
System infrastructure scenarios installation and configuration of SAP Solution Manager
Master Guide ndash SAP Solution Manager available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution ManagerltReleasegt
Benefits and usage scenarios SAP Solution Manager ndash Learning Maps available on SAP Service Marketplace at http
5 System Landscape
52 Shared Services
4256 PUBLIC 2011-04-15
Topic Where to Find More Informationservicesapcomrkt-solman or https
servicesapcomsolutionmanager
Additional information See SAP Service Marketplace at http
servicesapcomsolutionmanager
5232 Solution Manager Diagnostics
Solution Manager Diagnostics provides efficient and safe root-cause analysis of incidents in customer
solutions powered by SAP NetWeaver It can help monitor on operating systems databases Java
application activities performance and logs It also supports the reporting of software and
configuration changes that can lead to malfunctions and errors
You must run one Solution Manager Diagnostics within your SAP solution landscape if you run
applications based on SAP NetWeaver systems with usage type AS Java Agents are responsible for
delivering the data from all productive hosts within your system landscape to the Solution Manager
Diagnostics system
CAUTION
SAP Support performs root-cause analysis on incoming incidents with Solution Manager
Diagnostics Not installing and configuring this support infrastructure results in a dramatically
reduced service level
Solution Manager Diagnostics is fully integrated into SAP Solution Manager 70
Solution Manager Diagnostics also contains Wily Introscope (Display Server and Agent part) for
measuring performance as well as to troubleshoot problems of Non-ABAP applications Wily Introscope
is heavily used for troubleshooting applications running on AS Java
SAP has signed a distribution agreement for Wily Introscope SAP customers are allowed to use this
tool in a preconfigured way
For more information about Solution Manager Diagnostics and an FAQ list see SAP Service Marketplace
at httpservicesapcomdiagnostics
5233 System Landscape Directory
The System Landscape Directory (SLD) of SAP NetWeaver is the central directory of system landscape
information relevant for the management of your software life-cycle
NOTE
Note that the abbreviation SLD is not intended to define a product since the System Landscape
Directory is part of SAP NetWeaver This abbreviation is solely intended to improve readability
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4356
The System Landscape Directory contains a description of your system landscape (that is software
components that are currently installed) and a repository of software components that can
theoretically be installed in your landscape (such as the software components available from SAP)
Since this data gets updated automatically the System Landscape Directory provides reliable and up-
to-date system landscape information with as little effort for you as possible In this way the System
Landscape Directory acts as a central information provider for SAP and third-party tools that use this
data to deliver the services you need to keep your landscape up and running
For the System Landscape Directory as part of an SAP NetWeaver PI 71 landscape consider the following
aspects
Part of SAP NetWeaver PI 71 is a new version of the System Landscape Directory It is automatically
included in every SAP NetWeaver 71 system with usage type AS Java It offers enhanced functions
such as a full automatic synchronization mechanism for all data stored in it That is both data
delivered by data suppliers and data entered or changed manually in the System Landscape
Directory can be synchronized automatically This synchronization offers the following
A fully automated mechanism so no user interaction is required and conflicts are resolved
automatically
Asynchronous propagation of information so some nodes may be down temporarily
Communication over HTTP protocol
Uni- and bi-directional synchronization
Depending on your use case the full automatic synchronization could significantly reduce manual
synchronization effort
For SAP NetWeaver PI 71 the configuration of the system landscape directory and its data suppliers
is already included in the standard implementation procedure with SAPinst For existing systems
you only have to perform some quick and easy configuration actions to start operating the system
landscape directory server in an AS Java system
For SAP NetWeaver PI 71 you have the following options concerning SLD
Option 1
Run SAP NetWeaver PI 71 against an existing SLD running on SAP NetWeaver 70 We only
recommend this for upgrades from SAP NetWeaver 70 if you have a central SLD in operation
not running on one of your PI systems
Option 2
Use the SLD included in an SAP NetWeaver PI 71 system We recommend this option for new
installations and upgrades from older releases than SAP NetWeaver 70 due to the enhanced
functions and improved performance of SLD 71
NOTE
If you already have a central SLD running on SAP NetWeaver 70 in operation you could run
two SLD versions in parallel ndash SLD running on SAP NetWeaver 71 for your PI systems and
SLD running on SAP NetWeaver 70 for all other systemsuse cases This way your SAP
5 System Landscape
52 Shared Services
4456 PUBLIC 2011-04-15
NetWeaver PI 71 systems would benefit from the new features while it would be easy to set
up and operate such an SLD landscape For this purpose you could use the new fully
automatic synchronization This feature enables the automatic forwarding of all SLD data
from an SLD running on SAP NetWeaver 70 to an SLD running on SAP NetWeaver 71 As a
result there is no need to adapt most existing systems as their SLD data suppliers could still
send their data to the central SLD In brief the following steps would be required
1 Put SLD in a PI system into operation (part of standard implementation procedure)
2 Configure PI systems to use the new SLD (part of standard implementation procedure
for new PI systems)
3 Set up the fully automatic synchronization from your old SLD to your new SLD
As soon as an upgrade or an installation of a standalone AS Java 71 system is available you
could move your central SLD also to SAP NetWeaver 71 Then you could optionally shift
your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems
Figure 8
We recommend that you use a Domain Name System (DNS) alias so that you are able to switch to
another System Landscape Directory easily For example if customers build a new landscape they
normally start with a sandbox environment Over time more and more environments are set up
Once the production environment is in place move the System Landscape Directory there To do
this you can configure a new System Landscape Directory in the production environment
synchronize it with the old System Landscape directory and switch to the new one
Topology
Apart from the considerations above the System Landscape Directory offers several topology options
with different grades of availability at the expense of low administration and operation effort There is
no generic rule therefore on how to set up a System Landscape Directory in your system landscape
To find the topology and synchronization strategy for the System Landscape Directory that fits your
requirements concerning the System Landscape Directory availability (and hence the availability of
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4556
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
This page is left blank for documents that are printed on both sides
5 System Landscape
51 Planning Your System Landscape
The installable software units that make up your system landscape depend on the functions that you
want to implement For information about the features see systems [page 16] standalone engines [page 19]
and clients [page 21]
In addition you have to determine the required shared services [page 35] (such as SAP Solution Manager
or SAP NetWeaver Administrator) that run on central systems in your system landscape and the
landscape aspects relevant for their implementation
In the following you will find general information that you should consider when planning your system
landscape
Sizing
You have to map systems and standalone engines to hosts after you have a clear picture of the following
Which systems and standalone engines you require
How many systems you require and how you want to use each of these systems
NOTE
No general guideline can be given for the sizing of your landscape since this relies heavily on your
requirements You should therefore perform this task together with your hardware partner and
your technical consultant
For information about sizing your systems you can use the following information sources
Your first point of reference is the Quick Sizer
SAP built the Quick Sizer as an online sizing questionnaire Internet application in close cooperation
with its hardware partners This tool delivers general sizing categories based on your volume load
estimates The results provide an objective basis for sizing independent of platform and
configuration
For more information see SAP Service Marketplace at
httpservicesapcomsizing for the SAP NetWeaver PI 71 sizing guide available under
Sizing Guidelines Business Suite amp Services
httpservicesapcomquicksizer for more information and access to the tool itself
Also consider the following important aspects concerning sizing
High availability
5 System Landscape
51 Planning Your System Landscape
2011-04-15 PUBLIC 3356
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Technical Infrastructure High Availability
Unicode
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Internationalization
Contact your hardware partner to find out the appropriate number of sized hosts
The platform-independent abstract results of the Quick Sizer can be used by any of our hardware
partners to create a concrete offer SAP itself does not make any hardware recommendations the
responsibility for sizing and detailed hardware configuration lies with the hardware partners
Figure 6 Example of Mapping of Systems and Standalone Engines to Three Hosts
NOTE
Optionally you could also distribute single systems to multiple hosts For example you could
decide to install the database instance of an SAP system on a separate host for performance
reasons or distribute other system instances to achieve high availability
To provide a mapping that fits your required functions and performance your hardware partner
and your technical consultant have to identify the number of required instances of SAP NetWeaver
find out how to distribute these instances to hosts and what functions will run on which instance
Therefore the hardware partner and the technical consultant have to consider many different
aspects such as
Number of required SAPS (SAP Application Benchmark Performance Standard) for each
system (provided by Quick Sizer)
Landscape-relevant aspects concerning security For more information see the SAP Security
Guide in the SAP Library [page 12] at Administratoracutes Guide Security Guide
Landscape-relevant aspects concerning scalability high availability operation and software
life-cycle management
5 System Landscape
51 Planning Your System Landscape
3456 PUBLIC 2011-04-15
For more information about relevant aspects for the mapping of systems to hosts see the document
Technical Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
Scaling and Distribution Options
You may need to design your system landscape for a large number of users SAP NetWeaver PI offers
you different means of scalability The following list provides you with some examples
You could install multiple systems of one type and use them for different purposes
You could scale every system by installing dialog instances or by distributing the database instance
For more information about distribution options on the instance level see the Technical
Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
For every SAP system you could additionally install Web Dispatcher For more information see
the SAP Library [page 12] at FunctionndashOriented View Application Server Infrastructure SAP Web
Dispatcher
You could further distribute certain standalone engines ndash for example Search and Classification
(TREX) is based on a flexible architecture that supports a distributed installation For more
information see the Technical Infrastructure Guide ndash SAP NetWeaver PI 71 available in SAP Service
Marketplace at httpservicesapcominstallNWPI71
52 Shared Services
You normally run shared services on central systems in your system landscape The following features
could be used for SAP NetWeaver Process Integration to realize shared services
SAP Solution Manager
Used to implement train test maintain monitor control change and manage incidents of your
SAP solution system landscape (open end-to-end application management)
As of SAP Solution Manager (70) 40 Support Package 15 SAP Solution Manager has become the
platform for SAPs end-to-end solution operations strategy Functions for complete application
management has been combined with administrative tools and has been merged in newly created
role based work centers
NOTE
Be aware that you require an SAP Solution Manager system to install or upgrade to SAP
NetWeaver 70 and higher An SAP Solution Manager system is required to generate the SAP
Solution Manager key needed during the installation or upgrade process Without this key
the installation or upgrade process cannot continue
For SAP NetWeaver Process Integration you require SAP Solution Manager 70
For more information see SAP Note 805390
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3556
Solution Manager Diagnostics
An integral part of SAP Solution Manager that is running as a Java application on the Java stack of
SAP Solution Manager 70 Solution Manager Diagnostics is used to analyze the root cause of
incidents in your landscape in an efficient and safe way Before Go-Live Solution Manager
Diagnostics has to be set up and made accessible remotely
SAP NetWeaver Administrator
SAP NetWeaver Administrator is the central administration component which is used for
monitoring and administering Java applications It is included in SAP NetWeaver systems with AS
Java
SAP NetWeaver Administrator exists in the following flavors
A local mode which runs out of the box and which focuses on administrating the underlying
SAP NetWeaver AS Java
NOTE
For a SAP NetWeaver PI 71 it has a special role which you need to activate using a
configuation wizard
A central mode which has to be configured before use and which deals with the system
landscape management
SAP has decided to merge the central mode of SAP NetWeaver Administrator into the new work
centers available as of SAP Solution Manager 70 SP 15 Thus it can be used in an administrative
context together with non-Java-based administration tools Although the central mode of SAP
NetWeaver Administrator will be still available for some time SAP will not develop this tool any
further SAP focuses on optimizing the administrative work centers of SAP Solution Manager
instead
The local mode of SAP NetWeaver Administrator stays untouched It is available for current and
future releases of SAP NetWeaver
SAP Central Process Scheduling by Redwood
SAP Central Process Scheduling application by Redwood enables central job scheduling and job
monitoring of current and old releases of AS ABAP systems (as of Basis Release 31) This application
is fully integrated in SAP NetWeaver Depending on the business needs SAP business applications
are the initial trigger for scheduled activities You can now manage jobs and job chains conveniently
using a graphical user interface
System Landscape Directory
The System Landscape Directory is the central directory of system landscape information relevant
for the management of your software life-cycle It contains a description of your system landscape
(that is software components that are currently installed) and a repository of software components
that can theoretically be installed in your landscape (such as the software components available
from SAP)
Adaptive Computing Controller
5 System Landscape
52 Shared Services
3656 PUBLIC 2011-04-15
The Adaptive Computing Controller enables users to control an adaptive computing landscape
from a single point through observation operation and dynamic resource distribution With
adaptive computing hardware software and system services are able to adapt to changing business
needs In the Adaptive Computing Controller the run-time data of logical and physical landscapes
can be monitored application services can be startedstoppedrelocated and hardware resources
can be assigned to application services The operation can also be mass executed and be planned as
tasks to be executed
For more information about the installation of the Adaptive Computing Controller tool see the
document Installation Guide ndash Adaptive Computing Controller in SAP NetWeaver 71 available on SAP Service
Marketplace at httpservicesapcominstallNWPI71
For more information about Adaptive Computing in general see httpsdnsapcomirj
sdnadaptive
521 Use Cases
You can use the applications and tools described above for use cases that are normally performed
centrally The following sections describe these use cases
5211 End-to-End Solution Operations
Running business applications through their complete life-cycle is a challenge Therefore SAP has
started the Run SAP methodology for implementing End-to-End Solution Operations Based on a set
of SAP standards a roadmap and a package for training and certification Run SAP helps customers to
facilitate End-to-End Solution Operations
You can download the SAP standards for Solution Operations from SAP Service Marketplace at http
servicesapcomsupportstandards They describe roles customers typically have in their IT
environment For optimal role support SAP has grouped existing and new functions in SAP Solution
Manager work centers as of SAP Solution Manager 70 Support Package 15 Operations aspects are fully
covered by adding administrative functions for SAP NetWeaver as well Work centers are ABAP Web
Dynpro-based applications They offer the following advantages
Easy to use similar look and feel
Context transfer while jumping from one work center into another
Logical grouping of tools for a certain area
Simple authorization concept
Easy to expand
Each IT role belongs to one or more work centers For instance the Technical Administrator IT role is
covered by the work centers for System Monitoring System Administration and Landscape Management
The following work centers are available
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3756
Business Process Operations
Change Management
Root Cause Analysis
Implementation Upgrade
Incident Management
Test Management
Job Management
System Landscape Management
Solution Documentation Assistant
SAP Engagement and Service Delivery
SAP Solution Manager Administration
System Administration
System Monitoring
My Home is the central point of access to all important data of almost all work centers in SAP Solution
Manager
5212 Support Infrastructure
A key requirement for effective support of IT solutions is the ability to perform root cause analysis with
speed and efficiency
With SAP Solution Manager SAP has long had an infrastructure in place for its ABAP applications that
efficiently supports SAP solutions This helps ensure the high availability and smooth running of
business processes For more information see the SAP Solution Manager section
With Solution Manager Diagnostics this knowledge has been extended to Java applications If for
example homegrown Java applications cause instability Solution Manager Diagnostics helps trace the
cause to eradicate the problem rapidly Solution Manager Diagnostics is fully integrated into SAP
Solution Manager 70 Solution Manager Diagnostics also contains two third-party tools CArsquos Wily
Introscopereg for measuring performance as well as troubleshooting problems of the Java EE Engine
and applications running on it and Mercury Loadrunnerreg which enables SAP Support to produce a
defined load in the SAP solution landscape remotely For more information see Solution Manager
Diagnostics [page 43]
The support infrastructure provides SAP Support with safe access to your productive landscape for safe
root cause analysis so ensuring that SAP Support does not change your landscape inadvertently You
require a support infrastructure to run SAP NetWeaver
The following figure shows the overall infrastructure including SAP NetWeaver administration tools
that are used by administrators or operators at the customer site
5 System Landscape
52 Shared Services
3856 PUBLIC 2011-04-15
Landscape Aspects
If you use SAP NetWeaver Process Integration 71 productively besides SAP Solution Manager (as a
central support platform) you have to set up Solution Manager Diagnostics for supportability reasons
Implementation Sequence
For information about the implementation of the support infrastructure see the document Master
Guide ndash SAP Solution Manager 70 available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution Manager ltReleasegt
5213 Collection of Landscape Data
Amongst other applications and services the support infrastructure and the SAP NetWeaver
administration tools rely on system landscape data
For SAP NetWeaver PI 71 you have to run non-ABAP components in your solution landscape
Therefore the System Landscape Directory is mandatory The landscape data that is automatically
gathered by the System Landscape Directory is replicated to SAP Solution Manager There are several
topology options for the System Landscape Directory They offer different grades of availability
administration and operation effort
For more information see the System Landscape Directory section
5214 Authentication and Single Sign-On
Before implementing your system landscape plan how to implement authentication and how to
integrate different systems into a Single Sign-On landscape Single Sign-On reduces complexity for end
users saving them valuable time while also reducing administration effort for resetting passwords
thereby contributing to TCO reduction
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
5215 Integrated User and Access Management
In a system landscape containing a combination of ABAP and Java components we recommend that
you integrate your user and access management so that you can use the same user data across different
systems administer this data centrally and control access to data SAPs mature fine-grained
authorization concept allows detailed control of access rights SAP NetWeaver provides both ABAP and
Java-based user management solutions The user management solution that you use to administer
your user data depends on factors such as the type of systems that are running in your landscape
If you want to use central user administration we recommend that you run it in a non-production
system If you do not have a central user administration yet you can for example realize it in the SAP
Solution Manager system
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3956
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
522 Examples for the Overall System Landscape of Shared Services
In this section we provide examples of how shared services can be set up depending on the system
landscape they are intended for The following examples aggregate the landscape aspects given in the
Use Cases section
NOTE
The following sections and the figure mostly do not show information about the life-cycle of
shared services For example you may also need a development and testquality assurance system
for SAP Solution Manager You should consider this aspect in addition to the information given
in this section based on your requirements
Small and MediumndashSized Customer Landscapes with Java
As you use Java productively for SAP NetWeaver PI 71 besides SAP Solution Manager you have to set
up additional components for optimal monitoring administration and support Solution Manager
Diagnostics and the central mode of SAP NetWeaver Administrator are already fully integrated into
SAP Solution Manager 70 as the central operations hub For SAP Process Integration you must also
set up SAP NetWeaver Administrator with a special role
We recommend that you do not install SAP Central Process Scheduling in the SAP Solution Manager
system You have to set up and operate the system which hosts your productive scheduler as a mission
critical system
In the SAP Solution Manager system you should set up a local System Landscape Directory in addition
to a central runtime System Landscape Directory This way you have a clear separation between your
management system (SAP Solution Manager) and managed systems in your landscape In addition
SAP Solution Manager then does not rely on a System Landscape Directory running in the production
environment For this setup configure the SLD data suppliers of your SAP Solution Manager system
to send data to the central runtime System Landscape Directory In addition configure automatic
bridge forwarding from your runtime System Landscape Directory to the local System Landscape
Directory For more information see the Planning Guide - System Landscape Directory
If you want to use a central system for Adobe Document Services we recommend that you install a
dedicated system for this purpose in your production environment For detailed information about
the sizing of the system for the different use cases see the Sizing Guide for Adobe Document Services at
SAP Service Marketplace at httpservicesapcomsizing Sizing Guidelines Solutions amp
Platform
We recommend that you start with this centralized SAP Solution Manager approach as depicted in the
following figure
5 System Landscape
52 Shared Services
4056 PUBLIC 2011-04-15
Figure 7 Single SAP Solution Manager Landscape
Large Customer Landscapes with Java
Large customers who have environments in their landscape that are large and distributed administered
by different groups or separated for security reasons can consider a distributed operations setup In
addition to the centralized setup described for small- and medium-sized customers above large
customers can put parts of the central management functions on extra hosts or systems for performance
or policy reasons You have the following options for a distributed setup
You may set up an extra system or client for Central User Administration (CUA)
The Change and Transport System (CTS) can run on an extra system However it is not
performance- or data-intensive
You may set up an extra system for central CCMS monitoring Depending on the customizing
and on the landscape size central CCMS may generate a lot of system load You can connect a
separate central CCMS to SAP Solution Manager for displaying alerts in the alert inbox of the System
Monitoring work center
You can use a separate SAP NetWeaver 70 system with usage type BI together with SAP Solution
Manager This may make sense with respect to the amount of landscape management data that is
stored for reporting purposes The amount of data strongly depends on the data granularity
storage time frame and landscape size
You can easily put Wily Introscope Enterprise Manager on an separate host
Other aspects described above for small- and medium-customers (such as the setup of the System
Landscape Directory) are also valid for large customers
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4156
523 Feature Details
This section provides further information about the features described above
5231 SAP Solution Manager
SAP provides you with SAP Solution Manager as the strategic application management platform and
to enable the collaboration between you and SAP You need to install at least one productive SAP
Solution Manager in your system landscape To ensure the availability of this application management
platform an SAP Solution Manager system is technically required to install or upgrade to SAP
NetWeaver 70 or higher If you are already using SAP Solution Manager you can also use it to manage
the solution you build with SAP NetWeaver In this case we highly recommend that you update SAP
Solution Manager to the latest version
As of SAP Solution Manager 70 SP15 you can use the newly created work centers
NOTE
During the SAP system installation or upgrade process you are prompted to enter the SAP
Solution Manager key An SAP Solution Manager system is required to generate this key Without
this key the installation or upgrade process cannot continue
You may generate all needed keys for your entire system landscape (development quality
assurance and production system) in one SAP Solution Manager system In case you plan to install
several solution landscapes (for example in different countries) one SAP Solution Manager
system is still sufficient
For more information see SAP Note 805390
It is possible to install multiple SAP Solution Managers If you do so they should host separate business
solutions
If you want to reduce the risk of unavailability you should not install SAP Solution Manager as a central
component Instead you can operate a 2-system-landscape with both a test and production
environment of SAP Solution Manager (especially if you are using time-critical functions like Support
Desk) If you also develop your own content a 3-system-landscape with a development test and
production environment is recommended
For more information about SAP Solution Manager see the following table
Topic Where to Find More Information
System infrastructure scenarios installation and configuration of SAP Solution Manager
Master Guide ndash SAP Solution Manager available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution ManagerltReleasegt
Benefits and usage scenarios SAP Solution Manager ndash Learning Maps available on SAP Service Marketplace at http
5 System Landscape
52 Shared Services
4256 PUBLIC 2011-04-15
Topic Where to Find More Informationservicesapcomrkt-solman or https
servicesapcomsolutionmanager
Additional information See SAP Service Marketplace at http
servicesapcomsolutionmanager
5232 Solution Manager Diagnostics
Solution Manager Diagnostics provides efficient and safe root-cause analysis of incidents in customer
solutions powered by SAP NetWeaver It can help monitor on operating systems databases Java
application activities performance and logs It also supports the reporting of software and
configuration changes that can lead to malfunctions and errors
You must run one Solution Manager Diagnostics within your SAP solution landscape if you run
applications based on SAP NetWeaver systems with usage type AS Java Agents are responsible for
delivering the data from all productive hosts within your system landscape to the Solution Manager
Diagnostics system
CAUTION
SAP Support performs root-cause analysis on incoming incidents with Solution Manager
Diagnostics Not installing and configuring this support infrastructure results in a dramatically
reduced service level
Solution Manager Diagnostics is fully integrated into SAP Solution Manager 70
Solution Manager Diagnostics also contains Wily Introscope (Display Server and Agent part) for
measuring performance as well as to troubleshoot problems of Non-ABAP applications Wily Introscope
is heavily used for troubleshooting applications running on AS Java
SAP has signed a distribution agreement for Wily Introscope SAP customers are allowed to use this
tool in a preconfigured way
For more information about Solution Manager Diagnostics and an FAQ list see SAP Service Marketplace
at httpservicesapcomdiagnostics
5233 System Landscape Directory
The System Landscape Directory (SLD) of SAP NetWeaver is the central directory of system landscape
information relevant for the management of your software life-cycle
NOTE
Note that the abbreviation SLD is not intended to define a product since the System Landscape
Directory is part of SAP NetWeaver This abbreviation is solely intended to improve readability
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4356
The System Landscape Directory contains a description of your system landscape (that is software
components that are currently installed) and a repository of software components that can
theoretically be installed in your landscape (such as the software components available from SAP)
Since this data gets updated automatically the System Landscape Directory provides reliable and up-
to-date system landscape information with as little effort for you as possible In this way the System
Landscape Directory acts as a central information provider for SAP and third-party tools that use this
data to deliver the services you need to keep your landscape up and running
For the System Landscape Directory as part of an SAP NetWeaver PI 71 landscape consider the following
aspects
Part of SAP NetWeaver PI 71 is a new version of the System Landscape Directory It is automatically
included in every SAP NetWeaver 71 system with usage type AS Java It offers enhanced functions
such as a full automatic synchronization mechanism for all data stored in it That is both data
delivered by data suppliers and data entered or changed manually in the System Landscape
Directory can be synchronized automatically This synchronization offers the following
A fully automated mechanism so no user interaction is required and conflicts are resolved
automatically
Asynchronous propagation of information so some nodes may be down temporarily
Communication over HTTP protocol
Uni- and bi-directional synchronization
Depending on your use case the full automatic synchronization could significantly reduce manual
synchronization effort
For SAP NetWeaver PI 71 the configuration of the system landscape directory and its data suppliers
is already included in the standard implementation procedure with SAPinst For existing systems
you only have to perform some quick and easy configuration actions to start operating the system
landscape directory server in an AS Java system
For SAP NetWeaver PI 71 you have the following options concerning SLD
Option 1
Run SAP NetWeaver PI 71 against an existing SLD running on SAP NetWeaver 70 We only
recommend this for upgrades from SAP NetWeaver 70 if you have a central SLD in operation
not running on one of your PI systems
Option 2
Use the SLD included in an SAP NetWeaver PI 71 system We recommend this option for new
installations and upgrades from older releases than SAP NetWeaver 70 due to the enhanced
functions and improved performance of SLD 71
NOTE
If you already have a central SLD running on SAP NetWeaver 70 in operation you could run
two SLD versions in parallel ndash SLD running on SAP NetWeaver 71 for your PI systems and
SLD running on SAP NetWeaver 70 for all other systemsuse cases This way your SAP
5 System Landscape
52 Shared Services
4456 PUBLIC 2011-04-15
NetWeaver PI 71 systems would benefit from the new features while it would be easy to set
up and operate such an SLD landscape For this purpose you could use the new fully
automatic synchronization This feature enables the automatic forwarding of all SLD data
from an SLD running on SAP NetWeaver 70 to an SLD running on SAP NetWeaver 71 As a
result there is no need to adapt most existing systems as their SLD data suppliers could still
send their data to the central SLD In brief the following steps would be required
1 Put SLD in a PI system into operation (part of standard implementation procedure)
2 Configure PI systems to use the new SLD (part of standard implementation procedure
for new PI systems)
3 Set up the fully automatic synchronization from your old SLD to your new SLD
As soon as an upgrade or an installation of a standalone AS Java 71 system is available you
could move your central SLD also to SAP NetWeaver 71 Then you could optionally shift
your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems
Figure 8
We recommend that you use a Domain Name System (DNS) alias so that you are able to switch to
another System Landscape Directory easily For example if customers build a new landscape they
normally start with a sandbox environment Over time more and more environments are set up
Once the production environment is in place move the System Landscape Directory there To do
this you can configure a new System Landscape Directory in the production environment
synchronize it with the old System Landscape directory and switch to the new one
Topology
Apart from the considerations above the System Landscape Directory offers several topology options
with different grades of availability at the expense of low administration and operation effort There is
no generic rule therefore on how to set up a System Landscape Directory in your system landscape
To find the topology and synchronization strategy for the System Landscape Directory that fits your
requirements concerning the System Landscape Directory availability (and hence the availability of
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4556
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
5 System Landscape
51 Planning Your System Landscape
The installable software units that make up your system landscape depend on the functions that you
want to implement For information about the features see systems [page 16] standalone engines [page 19]
and clients [page 21]
In addition you have to determine the required shared services [page 35] (such as SAP Solution Manager
or SAP NetWeaver Administrator) that run on central systems in your system landscape and the
landscape aspects relevant for their implementation
In the following you will find general information that you should consider when planning your system
landscape
Sizing
You have to map systems and standalone engines to hosts after you have a clear picture of the following
Which systems and standalone engines you require
How many systems you require and how you want to use each of these systems
NOTE
No general guideline can be given for the sizing of your landscape since this relies heavily on your
requirements You should therefore perform this task together with your hardware partner and
your technical consultant
For information about sizing your systems you can use the following information sources
Your first point of reference is the Quick Sizer
SAP built the Quick Sizer as an online sizing questionnaire Internet application in close cooperation
with its hardware partners This tool delivers general sizing categories based on your volume load
estimates The results provide an objective basis for sizing independent of platform and
configuration
For more information see SAP Service Marketplace at
httpservicesapcomsizing for the SAP NetWeaver PI 71 sizing guide available under
Sizing Guidelines Business Suite amp Services
httpservicesapcomquicksizer for more information and access to the tool itself
Also consider the following important aspects concerning sizing
High availability
5 System Landscape
51 Planning Your System Landscape
2011-04-15 PUBLIC 3356
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Technical Infrastructure High Availability
Unicode
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Internationalization
Contact your hardware partner to find out the appropriate number of sized hosts
The platform-independent abstract results of the Quick Sizer can be used by any of our hardware
partners to create a concrete offer SAP itself does not make any hardware recommendations the
responsibility for sizing and detailed hardware configuration lies with the hardware partners
Figure 6 Example of Mapping of Systems and Standalone Engines to Three Hosts
NOTE
Optionally you could also distribute single systems to multiple hosts For example you could
decide to install the database instance of an SAP system on a separate host for performance
reasons or distribute other system instances to achieve high availability
To provide a mapping that fits your required functions and performance your hardware partner
and your technical consultant have to identify the number of required instances of SAP NetWeaver
find out how to distribute these instances to hosts and what functions will run on which instance
Therefore the hardware partner and the technical consultant have to consider many different
aspects such as
Number of required SAPS (SAP Application Benchmark Performance Standard) for each
system (provided by Quick Sizer)
Landscape-relevant aspects concerning security For more information see the SAP Security
Guide in the SAP Library [page 12] at Administratoracutes Guide Security Guide
Landscape-relevant aspects concerning scalability high availability operation and software
life-cycle management
5 System Landscape
51 Planning Your System Landscape
3456 PUBLIC 2011-04-15
For more information about relevant aspects for the mapping of systems to hosts see the document
Technical Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
Scaling and Distribution Options
You may need to design your system landscape for a large number of users SAP NetWeaver PI offers
you different means of scalability The following list provides you with some examples
You could install multiple systems of one type and use them for different purposes
You could scale every system by installing dialog instances or by distributing the database instance
For more information about distribution options on the instance level see the Technical
Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
For every SAP system you could additionally install Web Dispatcher For more information see
the SAP Library [page 12] at FunctionndashOriented View Application Server Infrastructure SAP Web
Dispatcher
You could further distribute certain standalone engines ndash for example Search and Classification
(TREX) is based on a flexible architecture that supports a distributed installation For more
information see the Technical Infrastructure Guide ndash SAP NetWeaver PI 71 available in SAP Service
Marketplace at httpservicesapcominstallNWPI71
52 Shared Services
You normally run shared services on central systems in your system landscape The following features
could be used for SAP NetWeaver Process Integration to realize shared services
SAP Solution Manager
Used to implement train test maintain monitor control change and manage incidents of your
SAP solution system landscape (open end-to-end application management)
As of SAP Solution Manager (70) 40 Support Package 15 SAP Solution Manager has become the
platform for SAPs end-to-end solution operations strategy Functions for complete application
management has been combined with administrative tools and has been merged in newly created
role based work centers
NOTE
Be aware that you require an SAP Solution Manager system to install or upgrade to SAP
NetWeaver 70 and higher An SAP Solution Manager system is required to generate the SAP
Solution Manager key needed during the installation or upgrade process Without this key
the installation or upgrade process cannot continue
For SAP NetWeaver Process Integration you require SAP Solution Manager 70
For more information see SAP Note 805390
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3556
Solution Manager Diagnostics
An integral part of SAP Solution Manager that is running as a Java application on the Java stack of
SAP Solution Manager 70 Solution Manager Diagnostics is used to analyze the root cause of
incidents in your landscape in an efficient and safe way Before Go-Live Solution Manager
Diagnostics has to be set up and made accessible remotely
SAP NetWeaver Administrator
SAP NetWeaver Administrator is the central administration component which is used for
monitoring and administering Java applications It is included in SAP NetWeaver systems with AS
Java
SAP NetWeaver Administrator exists in the following flavors
A local mode which runs out of the box and which focuses on administrating the underlying
SAP NetWeaver AS Java
NOTE
For a SAP NetWeaver PI 71 it has a special role which you need to activate using a
configuation wizard
A central mode which has to be configured before use and which deals with the system
landscape management
SAP has decided to merge the central mode of SAP NetWeaver Administrator into the new work
centers available as of SAP Solution Manager 70 SP 15 Thus it can be used in an administrative
context together with non-Java-based administration tools Although the central mode of SAP
NetWeaver Administrator will be still available for some time SAP will not develop this tool any
further SAP focuses on optimizing the administrative work centers of SAP Solution Manager
instead
The local mode of SAP NetWeaver Administrator stays untouched It is available for current and
future releases of SAP NetWeaver
SAP Central Process Scheduling by Redwood
SAP Central Process Scheduling application by Redwood enables central job scheduling and job
monitoring of current and old releases of AS ABAP systems (as of Basis Release 31) This application
is fully integrated in SAP NetWeaver Depending on the business needs SAP business applications
are the initial trigger for scheduled activities You can now manage jobs and job chains conveniently
using a graphical user interface
System Landscape Directory
The System Landscape Directory is the central directory of system landscape information relevant
for the management of your software life-cycle It contains a description of your system landscape
(that is software components that are currently installed) and a repository of software components
that can theoretically be installed in your landscape (such as the software components available
from SAP)
Adaptive Computing Controller
5 System Landscape
52 Shared Services
3656 PUBLIC 2011-04-15
The Adaptive Computing Controller enables users to control an adaptive computing landscape
from a single point through observation operation and dynamic resource distribution With
adaptive computing hardware software and system services are able to adapt to changing business
needs In the Adaptive Computing Controller the run-time data of logical and physical landscapes
can be monitored application services can be startedstoppedrelocated and hardware resources
can be assigned to application services The operation can also be mass executed and be planned as
tasks to be executed
For more information about the installation of the Adaptive Computing Controller tool see the
document Installation Guide ndash Adaptive Computing Controller in SAP NetWeaver 71 available on SAP Service
Marketplace at httpservicesapcominstallNWPI71
For more information about Adaptive Computing in general see httpsdnsapcomirj
sdnadaptive
521 Use Cases
You can use the applications and tools described above for use cases that are normally performed
centrally The following sections describe these use cases
5211 End-to-End Solution Operations
Running business applications through their complete life-cycle is a challenge Therefore SAP has
started the Run SAP methodology for implementing End-to-End Solution Operations Based on a set
of SAP standards a roadmap and a package for training and certification Run SAP helps customers to
facilitate End-to-End Solution Operations
You can download the SAP standards for Solution Operations from SAP Service Marketplace at http
servicesapcomsupportstandards They describe roles customers typically have in their IT
environment For optimal role support SAP has grouped existing and new functions in SAP Solution
Manager work centers as of SAP Solution Manager 70 Support Package 15 Operations aspects are fully
covered by adding administrative functions for SAP NetWeaver as well Work centers are ABAP Web
Dynpro-based applications They offer the following advantages
Easy to use similar look and feel
Context transfer while jumping from one work center into another
Logical grouping of tools for a certain area
Simple authorization concept
Easy to expand
Each IT role belongs to one or more work centers For instance the Technical Administrator IT role is
covered by the work centers for System Monitoring System Administration and Landscape Management
The following work centers are available
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3756
Business Process Operations
Change Management
Root Cause Analysis
Implementation Upgrade
Incident Management
Test Management
Job Management
System Landscape Management
Solution Documentation Assistant
SAP Engagement and Service Delivery
SAP Solution Manager Administration
System Administration
System Monitoring
My Home is the central point of access to all important data of almost all work centers in SAP Solution
Manager
5212 Support Infrastructure
A key requirement for effective support of IT solutions is the ability to perform root cause analysis with
speed and efficiency
With SAP Solution Manager SAP has long had an infrastructure in place for its ABAP applications that
efficiently supports SAP solutions This helps ensure the high availability and smooth running of
business processes For more information see the SAP Solution Manager section
With Solution Manager Diagnostics this knowledge has been extended to Java applications If for
example homegrown Java applications cause instability Solution Manager Diagnostics helps trace the
cause to eradicate the problem rapidly Solution Manager Diagnostics is fully integrated into SAP
Solution Manager 70 Solution Manager Diagnostics also contains two third-party tools CArsquos Wily
Introscopereg for measuring performance as well as troubleshooting problems of the Java EE Engine
and applications running on it and Mercury Loadrunnerreg which enables SAP Support to produce a
defined load in the SAP solution landscape remotely For more information see Solution Manager
Diagnostics [page 43]
The support infrastructure provides SAP Support with safe access to your productive landscape for safe
root cause analysis so ensuring that SAP Support does not change your landscape inadvertently You
require a support infrastructure to run SAP NetWeaver
The following figure shows the overall infrastructure including SAP NetWeaver administration tools
that are used by administrators or operators at the customer site
5 System Landscape
52 Shared Services
3856 PUBLIC 2011-04-15
Landscape Aspects
If you use SAP NetWeaver Process Integration 71 productively besides SAP Solution Manager (as a
central support platform) you have to set up Solution Manager Diagnostics for supportability reasons
Implementation Sequence
For information about the implementation of the support infrastructure see the document Master
Guide ndash SAP Solution Manager 70 available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution Manager ltReleasegt
5213 Collection of Landscape Data
Amongst other applications and services the support infrastructure and the SAP NetWeaver
administration tools rely on system landscape data
For SAP NetWeaver PI 71 you have to run non-ABAP components in your solution landscape
Therefore the System Landscape Directory is mandatory The landscape data that is automatically
gathered by the System Landscape Directory is replicated to SAP Solution Manager There are several
topology options for the System Landscape Directory They offer different grades of availability
administration and operation effort
For more information see the System Landscape Directory section
5214 Authentication and Single Sign-On
Before implementing your system landscape plan how to implement authentication and how to
integrate different systems into a Single Sign-On landscape Single Sign-On reduces complexity for end
users saving them valuable time while also reducing administration effort for resetting passwords
thereby contributing to TCO reduction
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
5215 Integrated User and Access Management
In a system landscape containing a combination of ABAP and Java components we recommend that
you integrate your user and access management so that you can use the same user data across different
systems administer this data centrally and control access to data SAPs mature fine-grained
authorization concept allows detailed control of access rights SAP NetWeaver provides both ABAP and
Java-based user management solutions The user management solution that you use to administer
your user data depends on factors such as the type of systems that are running in your landscape
If you want to use central user administration we recommend that you run it in a non-production
system If you do not have a central user administration yet you can for example realize it in the SAP
Solution Manager system
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3956
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
522 Examples for the Overall System Landscape of Shared Services
In this section we provide examples of how shared services can be set up depending on the system
landscape they are intended for The following examples aggregate the landscape aspects given in the
Use Cases section
NOTE
The following sections and the figure mostly do not show information about the life-cycle of
shared services For example you may also need a development and testquality assurance system
for SAP Solution Manager You should consider this aspect in addition to the information given
in this section based on your requirements
Small and MediumndashSized Customer Landscapes with Java
As you use Java productively for SAP NetWeaver PI 71 besides SAP Solution Manager you have to set
up additional components for optimal monitoring administration and support Solution Manager
Diagnostics and the central mode of SAP NetWeaver Administrator are already fully integrated into
SAP Solution Manager 70 as the central operations hub For SAP Process Integration you must also
set up SAP NetWeaver Administrator with a special role
We recommend that you do not install SAP Central Process Scheduling in the SAP Solution Manager
system You have to set up and operate the system which hosts your productive scheduler as a mission
critical system
In the SAP Solution Manager system you should set up a local System Landscape Directory in addition
to a central runtime System Landscape Directory This way you have a clear separation between your
management system (SAP Solution Manager) and managed systems in your landscape In addition
SAP Solution Manager then does not rely on a System Landscape Directory running in the production
environment For this setup configure the SLD data suppliers of your SAP Solution Manager system
to send data to the central runtime System Landscape Directory In addition configure automatic
bridge forwarding from your runtime System Landscape Directory to the local System Landscape
Directory For more information see the Planning Guide - System Landscape Directory
If you want to use a central system for Adobe Document Services we recommend that you install a
dedicated system for this purpose in your production environment For detailed information about
the sizing of the system for the different use cases see the Sizing Guide for Adobe Document Services at
SAP Service Marketplace at httpservicesapcomsizing Sizing Guidelines Solutions amp
Platform
We recommend that you start with this centralized SAP Solution Manager approach as depicted in the
following figure
5 System Landscape
52 Shared Services
4056 PUBLIC 2011-04-15
Figure 7 Single SAP Solution Manager Landscape
Large Customer Landscapes with Java
Large customers who have environments in their landscape that are large and distributed administered
by different groups or separated for security reasons can consider a distributed operations setup In
addition to the centralized setup described for small- and medium-sized customers above large
customers can put parts of the central management functions on extra hosts or systems for performance
or policy reasons You have the following options for a distributed setup
You may set up an extra system or client for Central User Administration (CUA)
The Change and Transport System (CTS) can run on an extra system However it is not
performance- or data-intensive
You may set up an extra system for central CCMS monitoring Depending on the customizing
and on the landscape size central CCMS may generate a lot of system load You can connect a
separate central CCMS to SAP Solution Manager for displaying alerts in the alert inbox of the System
Monitoring work center
You can use a separate SAP NetWeaver 70 system with usage type BI together with SAP Solution
Manager This may make sense with respect to the amount of landscape management data that is
stored for reporting purposes The amount of data strongly depends on the data granularity
storage time frame and landscape size
You can easily put Wily Introscope Enterprise Manager on an separate host
Other aspects described above for small- and medium-customers (such as the setup of the System
Landscape Directory) are also valid for large customers
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4156
523 Feature Details
This section provides further information about the features described above
5231 SAP Solution Manager
SAP provides you with SAP Solution Manager as the strategic application management platform and
to enable the collaboration between you and SAP You need to install at least one productive SAP
Solution Manager in your system landscape To ensure the availability of this application management
platform an SAP Solution Manager system is technically required to install or upgrade to SAP
NetWeaver 70 or higher If you are already using SAP Solution Manager you can also use it to manage
the solution you build with SAP NetWeaver In this case we highly recommend that you update SAP
Solution Manager to the latest version
As of SAP Solution Manager 70 SP15 you can use the newly created work centers
NOTE
During the SAP system installation or upgrade process you are prompted to enter the SAP
Solution Manager key An SAP Solution Manager system is required to generate this key Without
this key the installation or upgrade process cannot continue
You may generate all needed keys for your entire system landscape (development quality
assurance and production system) in one SAP Solution Manager system In case you plan to install
several solution landscapes (for example in different countries) one SAP Solution Manager
system is still sufficient
For more information see SAP Note 805390
It is possible to install multiple SAP Solution Managers If you do so they should host separate business
solutions
If you want to reduce the risk of unavailability you should not install SAP Solution Manager as a central
component Instead you can operate a 2-system-landscape with both a test and production
environment of SAP Solution Manager (especially if you are using time-critical functions like Support
Desk) If you also develop your own content a 3-system-landscape with a development test and
production environment is recommended
For more information about SAP Solution Manager see the following table
Topic Where to Find More Information
System infrastructure scenarios installation and configuration of SAP Solution Manager
Master Guide ndash SAP Solution Manager available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution ManagerltReleasegt
Benefits and usage scenarios SAP Solution Manager ndash Learning Maps available on SAP Service Marketplace at http
5 System Landscape
52 Shared Services
4256 PUBLIC 2011-04-15
Topic Where to Find More Informationservicesapcomrkt-solman or https
servicesapcomsolutionmanager
Additional information See SAP Service Marketplace at http
servicesapcomsolutionmanager
5232 Solution Manager Diagnostics
Solution Manager Diagnostics provides efficient and safe root-cause analysis of incidents in customer
solutions powered by SAP NetWeaver It can help monitor on operating systems databases Java
application activities performance and logs It also supports the reporting of software and
configuration changes that can lead to malfunctions and errors
You must run one Solution Manager Diagnostics within your SAP solution landscape if you run
applications based on SAP NetWeaver systems with usage type AS Java Agents are responsible for
delivering the data from all productive hosts within your system landscape to the Solution Manager
Diagnostics system
CAUTION
SAP Support performs root-cause analysis on incoming incidents with Solution Manager
Diagnostics Not installing and configuring this support infrastructure results in a dramatically
reduced service level
Solution Manager Diagnostics is fully integrated into SAP Solution Manager 70
Solution Manager Diagnostics also contains Wily Introscope (Display Server and Agent part) for
measuring performance as well as to troubleshoot problems of Non-ABAP applications Wily Introscope
is heavily used for troubleshooting applications running on AS Java
SAP has signed a distribution agreement for Wily Introscope SAP customers are allowed to use this
tool in a preconfigured way
For more information about Solution Manager Diagnostics and an FAQ list see SAP Service Marketplace
at httpservicesapcomdiagnostics
5233 System Landscape Directory
The System Landscape Directory (SLD) of SAP NetWeaver is the central directory of system landscape
information relevant for the management of your software life-cycle
NOTE
Note that the abbreviation SLD is not intended to define a product since the System Landscape
Directory is part of SAP NetWeaver This abbreviation is solely intended to improve readability
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4356
The System Landscape Directory contains a description of your system landscape (that is software
components that are currently installed) and a repository of software components that can
theoretically be installed in your landscape (such as the software components available from SAP)
Since this data gets updated automatically the System Landscape Directory provides reliable and up-
to-date system landscape information with as little effort for you as possible In this way the System
Landscape Directory acts as a central information provider for SAP and third-party tools that use this
data to deliver the services you need to keep your landscape up and running
For the System Landscape Directory as part of an SAP NetWeaver PI 71 landscape consider the following
aspects
Part of SAP NetWeaver PI 71 is a new version of the System Landscape Directory It is automatically
included in every SAP NetWeaver 71 system with usage type AS Java It offers enhanced functions
such as a full automatic synchronization mechanism for all data stored in it That is both data
delivered by data suppliers and data entered or changed manually in the System Landscape
Directory can be synchronized automatically This synchronization offers the following
A fully automated mechanism so no user interaction is required and conflicts are resolved
automatically
Asynchronous propagation of information so some nodes may be down temporarily
Communication over HTTP protocol
Uni- and bi-directional synchronization
Depending on your use case the full automatic synchronization could significantly reduce manual
synchronization effort
For SAP NetWeaver PI 71 the configuration of the system landscape directory and its data suppliers
is already included in the standard implementation procedure with SAPinst For existing systems
you only have to perform some quick and easy configuration actions to start operating the system
landscape directory server in an AS Java system
For SAP NetWeaver PI 71 you have the following options concerning SLD
Option 1
Run SAP NetWeaver PI 71 against an existing SLD running on SAP NetWeaver 70 We only
recommend this for upgrades from SAP NetWeaver 70 if you have a central SLD in operation
not running on one of your PI systems
Option 2
Use the SLD included in an SAP NetWeaver PI 71 system We recommend this option for new
installations and upgrades from older releases than SAP NetWeaver 70 due to the enhanced
functions and improved performance of SLD 71
NOTE
If you already have a central SLD running on SAP NetWeaver 70 in operation you could run
two SLD versions in parallel ndash SLD running on SAP NetWeaver 71 for your PI systems and
SLD running on SAP NetWeaver 70 for all other systemsuse cases This way your SAP
5 System Landscape
52 Shared Services
4456 PUBLIC 2011-04-15
NetWeaver PI 71 systems would benefit from the new features while it would be easy to set
up and operate such an SLD landscape For this purpose you could use the new fully
automatic synchronization This feature enables the automatic forwarding of all SLD data
from an SLD running on SAP NetWeaver 70 to an SLD running on SAP NetWeaver 71 As a
result there is no need to adapt most existing systems as their SLD data suppliers could still
send their data to the central SLD In brief the following steps would be required
1 Put SLD in a PI system into operation (part of standard implementation procedure)
2 Configure PI systems to use the new SLD (part of standard implementation procedure
for new PI systems)
3 Set up the fully automatic synchronization from your old SLD to your new SLD
As soon as an upgrade or an installation of a standalone AS Java 71 system is available you
could move your central SLD also to SAP NetWeaver 71 Then you could optionally shift
your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems
Figure 8
We recommend that you use a Domain Name System (DNS) alias so that you are able to switch to
another System Landscape Directory easily For example if customers build a new landscape they
normally start with a sandbox environment Over time more and more environments are set up
Once the production environment is in place move the System Landscape Directory there To do
this you can configure a new System Landscape Directory in the production environment
synchronize it with the old System Landscape directory and switch to the new one
Topology
Apart from the considerations above the System Landscape Directory offers several topology options
with different grades of availability at the expense of low administration and operation effort There is
no generic rule therefore on how to set up a System Landscape Directory in your system landscape
To find the topology and synchronization strategy for the System Landscape Directory that fits your
requirements concerning the System Landscape Directory availability (and hence the availability of
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4556
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Technical Infrastructure High Availability
Unicode
For more information see SAP Developers Network at httpsdnsapcomirjsdn
landscapedesign Internationalization
Contact your hardware partner to find out the appropriate number of sized hosts
The platform-independent abstract results of the Quick Sizer can be used by any of our hardware
partners to create a concrete offer SAP itself does not make any hardware recommendations the
responsibility for sizing and detailed hardware configuration lies with the hardware partners
Figure 6 Example of Mapping of Systems and Standalone Engines to Three Hosts
NOTE
Optionally you could also distribute single systems to multiple hosts For example you could
decide to install the database instance of an SAP system on a separate host for performance
reasons or distribute other system instances to achieve high availability
To provide a mapping that fits your required functions and performance your hardware partner
and your technical consultant have to identify the number of required instances of SAP NetWeaver
find out how to distribute these instances to hosts and what functions will run on which instance
Therefore the hardware partner and the technical consultant have to consider many different
aspects such as
Number of required SAPS (SAP Application Benchmark Performance Standard) for each
system (provided by Quick Sizer)
Landscape-relevant aspects concerning security For more information see the SAP Security
Guide in the SAP Library [page 12] at Administratoracutes Guide Security Guide
Landscape-relevant aspects concerning scalability high availability operation and software
life-cycle management
5 System Landscape
51 Planning Your System Landscape
3456 PUBLIC 2011-04-15
For more information about relevant aspects for the mapping of systems to hosts see the document
Technical Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
Scaling and Distribution Options
You may need to design your system landscape for a large number of users SAP NetWeaver PI offers
you different means of scalability The following list provides you with some examples
You could install multiple systems of one type and use them for different purposes
You could scale every system by installing dialog instances or by distributing the database instance
For more information about distribution options on the instance level see the Technical
Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
For every SAP system you could additionally install Web Dispatcher For more information see
the SAP Library [page 12] at FunctionndashOriented View Application Server Infrastructure SAP Web
Dispatcher
You could further distribute certain standalone engines ndash for example Search and Classification
(TREX) is based on a flexible architecture that supports a distributed installation For more
information see the Technical Infrastructure Guide ndash SAP NetWeaver PI 71 available in SAP Service
Marketplace at httpservicesapcominstallNWPI71
52 Shared Services
You normally run shared services on central systems in your system landscape The following features
could be used for SAP NetWeaver Process Integration to realize shared services
SAP Solution Manager
Used to implement train test maintain monitor control change and manage incidents of your
SAP solution system landscape (open end-to-end application management)
As of SAP Solution Manager (70) 40 Support Package 15 SAP Solution Manager has become the
platform for SAPs end-to-end solution operations strategy Functions for complete application
management has been combined with administrative tools and has been merged in newly created
role based work centers
NOTE
Be aware that you require an SAP Solution Manager system to install or upgrade to SAP
NetWeaver 70 and higher An SAP Solution Manager system is required to generate the SAP
Solution Manager key needed during the installation or upgrade process Without this key
the installation or upgrade process cannot continue
For SAP NetWeaver Process Integration you require SAP Solution Manager 70
For more information see SAP Note 805390
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3556
Solution Manager Diagnostics
An integral part of SAP Solution Manager that is running as a Java application on the Java stack of
SAP Solution Manager 70 Solution Manager Diagnostics is used to analyze the root cause of
incidents in your landscape in an efficient and safe way Before Go-Live Solution Manager
Diagnostics has to be set up and made accessible remotely
SAP NetWeaver Administrator
SAP NetWeaver Administrator is the central administration component which is used for
monitoring and administering Java applications It is included in SAP NetWeaver systems with AS
Java
SAP NetWeaver Administrator exists in the following flavors
A local mode which runs out of the box and which focuses on administrating the underlying
SAP NetWeaver AS Java
NOTE
For a SAP NetWeaver PI 71 it has a special role which you need to activate using a
configuation wizard
A central mode which has to be configured before use and which deals with the system
landscape management
SAP has decided to merge the central mode of SAP NetWeaver Administrator into the new work
centers available as of SAP Solution Manager 70 SP 15 Thus it can be used in an administrative
context together with non-Java-based administration tools Although the central mode of SAP
NetWeaver Administrator will be still available for some time SAP will not develop this tool any
further SAP focuses on optimizing the administrative work centers of SAP Solution Manager
instead
The local mode of SAP NetWeaver Administrator stays untouched It is available for current and
future releases of SAP NetWeaver
SAP Central Process Scheduling by Redwood
SAP Central Process Scheduling application by Redwood enables central job scheduling and job
monitoring of current and old releases of AS ABAP systems (as of Basis Release 31) This application
is fully integrated in SAP NetWeaver Depending on the business needs SAP business applications
are the initial trigger for scheduled activities You can now manage jobs and job chains conveniently
using a graphical user interface
System Landscape Directory
The System Landscape Directory is the central directory of system landscape information relevant
for the management of your software life-cycle It contains a description of your system landscape
(that is software components that are currently installed) and a repository of software components
that can theoretically be installed in your landscape (such as the software components available
from SAP)
Adaptive Computing Controller
5 System Landscape
52 Shared Services
3656 PUBLIC 2011-04-15
The Adaptive Computing Controller enables users to control an adaptive computing landscape
from a single point through observation operation and dynamic resource distribution With
adaptive computing hardware software and system services are able to adapt to changing business
needs In the Adaptive Computing Controller the run-time data of logical and physical landscapes
can be monitored application services can be startedstoppedrelocated and hardware resources
can be assigned to application services The operation can also be mass executed and be planned as
tasks to be executed
For more information about the installation of the Adaptive Computing Controller tool see the
document Installation Guide ndash Adaptive Computing Controller in SAP NetWeaver 71 available on SAP Service
Marketplace at httpservicesapcominstallNWPI71
For more information about Adaptive Computing in general see httpsdnsapcomirj
sdnadaptive
521 Use Cases
You can use the applications and tools described above for use cases that are normally performed
centrally The following sections describe these use cases
5211 End-to-End Solution Operations
Running business applications through their complete life-cycle is a challenge Therefore SAP has
started the Run SAP methodology for implementing End-to-End Solution Operations Based on a set
of SAP standards a roadmap and a package for training and certification Run SAP helps customers to
facilitate End-to-End Solution Operations
You can download the SAP standards for Solution Operations from SAP Service Marketplace at http
servicesapcomsupportstandards They describe roles customers typically have in their IT
environment For optimal role support SAP has grouped existing and new functions in SAP Solution
Manager work centers as of SAP Solution Manager 70 Support Package 15 Operations aspects are fully
covered by adding administrative functions for SAP NetWeaver as well Work centers are ABAP Web
Dynpro-based applications They offer the following advantages
Easy to use similar look and feel
Context transfer while jumping from one work center into another
Logical grouping of tools for a certain area
Simple authorization concept
Easy to expand
Each IT role belongs to one or more work centers For instance the Technical Administrator IT role is
covered by the work centers for System Monitoring System Administration and Landscape Management
The following work centers are available
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3756
Business Process Operations
Change Management
Root Cause Analysis
Implementation Upgrade
Incident Management
Test Management
Job Management
System Landscape Management
Solution Documentation Assistant
SAP Engagement and Service Delivery
SAP Solution Manager Administration
System Administration
System Monitoring
My Home is the central point of access to all important data of almost all work centers in SAP Solution
Manager
5212 Support Infrastructure
A key requirement for effective support of IT solutions is the ability to perform root cause analysis with
speed and efficiency
With SAP Solution Manager SAP has long had an infrastructure in place for its ABAP applications that
efficiently supports SAP solutions This helps ensure the high availability and smooth running of
business processes For more information see the SAP Solution Manager section
With Solution Manager Diagnostics this knowledge has been extended to Java applications If for
example homegrown Java applications cause instability Solution Manager Diagnostics helps trace the
cause to eradicate the problem rapidly Solution Manager Diagnostics is fully integrated into SAP
Solution Manager 70 Solution Manager Diagnostics also contains two third-party tools CArsquos Wily
Introscopereg for measuring performance as well as troubleshooting problems of the Java EE Engine
and applications running on it and Mercury Loadrunnerreg which enables SAP Support to produce a
defined load in the SAP solution landscape remotely For more information see Solution Manager
Diagnostics [page 43]
The support infrastructure provides SAP Support with safe access to your productive landscape for safe
root cause analysis so ensuring that SAP Support does not change your landscape inadvertently You
require a support infrastructure to run SAP NetWeaver
The following figure shows the overall infrastructure including SAP NetWeaver administration tools
that are used by administrators or operators at the customer site
5 System Landscape
52 Shared Services
3856 PUBLIC 2011-04-15
Landscape Aspects
If you use SAP NetWeaver Process Integration 71 productively besides SAP Solution Manager (as a
central support platform) you have to set up Solution Manager Diagnostics for supportability reasons
Implementation Sequence
For information about the implementation of the support infrastructure see the document Master
Guide ndash SAP Solution Manager 70 available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution Manager ltReleasegt
5213 Collection of Landscape Data
Amongst other applications and services the support infrastructure and the SAP NetWeaver
administration tools rely on system landscape data
For SAP NetWeaver PI 71 you have to run non-ABAP components in your solution landscape
Therefore the System Landscape Directory is mandatory The landscape data that is automatically
gathered by the System Landscape Directory is replicated to SAP Solution Manager There are several
topology options for the System Landscape Directory They offer different grades of availability
administration and operation effort
For more information see the System Landscape Directory section
5214 Authentication and Single Sign-On
Before implementing your system landscape plan how to implement authentication and how to
integrate different systems into a Single Sign-On landscape Single Sign-On reduces complexity for end
users saving them valuable time while also reducing administration effort for resetting passwords
thereby contributing to TCO reduction
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
5215 Integrated User and Access Management
In a system landscape containing a combination of ABAP and Java components we recommend that
you integrate your user and access management so that you can use the same user data across different
systems administer this data centrally and control access to data SAPs mature fine-grained
authorization concept allows detailed control of access rights SAP NetWeaver provides both ABAP and
Java-based user management solutions The user management solution that you use to administer
your user data depends on factors such as the type of systems that are running in your landscape
If you want to use central user administration we recommend that you run it in a non-production
system If you do not have a central user administration yet you can for example realize it in the SAP
Solution Manager system
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3956
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
522 Examples for the Overall System Landscape of Shared Services
In this section we provide examples of how shared services can be set up depending on the system
landscape they are intended for The following examples aggregate the landscape aspects given in the
Use Cases section
NOTE
The following sections and the figure mostly do not show information about the life-cycle of
shared services For example you may also need a development and testquality assurance system
for SAP Solution Manager You should consider this aspect in addition to the information given
in this section based on your requirements
Small and MediumndashSized Customer Landscapes with Java
As you use Java productively for SAP NetWeaver PI 71 besides SAP Solution Manager you have to set
up additional components for optimal monitoring administration and support Solution Manager
Diagnostics and the central mode of SAP NetWeaver Administrator are already fully integrated into
SAP Solution Manager 70 as the central operations hub For SAP Process Integration you must also
set up SAP NetWeaver Administrator with a special role
We recommend that you do not install SAP Central Process Scheduling in the SAP Solution Manager
system You have to set up and operate the system which hosts your productive scheduler as a mission
critical system
In the SAP Solution Manager system you should set up a local System Landscape Directory in addition
to a central runtime System Landscape Directory This way you have a clear separation between your
management system (SAP Solution Manager) and managed systems in your landscape In addition
SAP Solution Manager then does not rely on a System Landscape Directory running in the production
environment For this setup configure the SLD data suppliers of your SAP Solution Manager system
to send data to the central runtime System Landscape Directory In addition configure automatic
bridge forwarding from your runtime System Landscape Directory to the local System Landscape
Directory For more information see the Planning Guide - System Landscape Directory
If you want to use a central system for Adobe Document Services we recommend that you install a
dedicated system for this purpose in your production environment For detailed information about
the sizing of the system for the different use cases see the Sizing Guide for Adobe Document Services at
SAP Service Marketplace at httpservicesapcomsizing Sizing Guidelines Solutions amp
Platform
We recommend that you start with this centralized SAP Solution Manager approach as depicted in the
following figure
5 System Landscape
52 Shared Services
4056 PUBLIC 2011-04-15
Figure 7 Single SAP Solution Manager Landscape
Large Customer Landscapes with Java
Large customers who have environments in their landscape that are large and distributed administered
by different groups or separated for security reasons can consider a distributed operations setup In
addition to the centralized setup described for small- and medium-sized customers above large
customers can put parts of the central management functions on extra hosts or systems for performance
or policy reasons You have the following options for a distributed setup
You may set up an extra system or client for Central User Administration (CUA)
The Change and Transport System (CTS) can run on an extra system However it is not
performance- or data-intensive
You may set up an extra system for central CCMS monitoring Depending on the customizing
and on the landscape size central CCMS may generate a lot of system load You can connect a
separate central CCMS to SAP Solution Manager for displaying alerts in the alert inbox of the System
Monitoring work center
You can use a separate SAP NetWeaver 70 system with usage type BI together with SAP Solution
Manager This may make sense with respect to the amount of landscape management data that is
stored for reporting purposes The amount of data strongly depends on the data granularity
storage time frame and landscape size
You can easily put Wily Introscope Enterprise Manager on an separate host
Other aspects described above for small- and medium-customers (such as the setup of the System
Landscape Directory) are also valid for large customers
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4156
523 Feature Details
This section provides further information about the features described above
5231 SAP Solution Manager
SAP provides you with SAP Solution Manager as the strategic application management platform and
to enable the collaboration between you and SAP You need to install at least one productive SAP
Solution Manager in your system landscape To ensure the availability of this application management
platform an SAP Solution Manager system is technically required to install or upgrade to SAP
NetWeaver 70 or higher If you are already using SAP Solution Manager you can also use it to manage
the solution you build with SAP NetWeaver In this case we highly recommend that you update SAP
Solution Manager to the latest version
As of SAP Solution Manager 70 SP15 you can use the newly created work centers
NOTE
During the SAP system installation or upgrade process you are prompted to enter the SAP
Solution Manager key An SAP Solution Manager system is required to generate this key Without
this key the installation or upgrade process cannot continue
You may generate all needed keys for your entire system landscape (development quality
assurance and production system) in one SAP Solution Manager system In case you plan to install
several solution landscapes (for example in different countries) one SAP Solution Manager
system is still sufficient
For more information see SAP Note 805390
It is possible to install multiple SAP Solution Managers If you do so they should host separate business
solutions
If you want to reduce the risk of unavailability you should not install SAP Solution Manager as a central
component Instead you can operate a 2-system-landscape with both a test and production
environment of SAP Solution Manager (especially if you are using time-critical functions like Support
Desk) If you also develop your own content a 3-system-landscape with a development test and
production environment is recommended
For more information about SAP Solution Manager see the following table
Topic Where to Find More Information
System infrastructure scenarios installation and configuration of SAP Solution Manager
Master Guide ndash SAP Solution Manager available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution ManagerltReleasegt
Benefits and usage scenarios SAP Solution Manager ndash Learning Maps available on SAP Service Marketplace at http
5 System Landscape
52 Shared Services
4256 PUBLIC 2011-04-15
Topic Where to Find More Informationservicesapcomrkt-solman or https
servicesapcomsolutionmanager
Additional information See SAP Service Marketplace at http
servicesapcomsolutionmanager
5232 Solution Manager Diagnostics
Solution Manager Diagnostics provides efficient and safe root-cause analysis of incidents in customer
solutions powered by SAP NetWeaver It can help monitor on operating systems databases Java
application activities performance and logs It also supports the reporting of software and
configuration changes that can lead to malfunctions and errors
You must run one Solution Manager Diagnostics within your SAP solution landscape if you run
applications based on SAP NetWeaver systems with usage type AS Java Agents are responsible for
delivering the data from all productive hosts within your system landscape to the Solution Manager
Diagnostics system
CAUTION
SAP Support performs root-cause analysis on incoming incidents with Solution Manager
Diagnostics Not installing and configuring this support infrastructure results in a dramatically
reduced service level
Solution Manager Diagnostics is fully integrated into SAP Solution Manager 70
Solution Manager Diagnostics also contains Wily Introscope (Display Server and Agent part) for
measuring performance as well as to troubleshoot problems of Non-ABAP applications Wily Introscope
is heavily used for troubleshooting applications running on AS Java
SAP has signed a distribution agreement for Wily Introscope SAP customers are allowed to use this
tool in a preconfigured way
For more information about Solution Manager Diagnostics and an FAQ list see SAP Service Marketplace
at httpservicesapcomdiagnostics
5233 System Landscape Directory
The System Landscape Directory (SLD) of SAP NetWeaver is the central directory of system landscape
information relevant for the management of your software life-cycle
NOTE
Note that the abbreviation SLD is not intended to define a product since the System Landscape
Directory is part of SAP NetWeaver This abbreviation is solely intended to improve readability
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4356
The System Landscape Directory contains a description of your system landscape (that is software
components that are currently installed) and a repository of software components that can
theoretically be installed in your landscape (such as the software components available from SAP)
Since this data gets updated automatically the System Landscape Directory provides reliable and up-
to-date system landscape information with as little effort for you as possible In this way the System
Landscape Directory acts as a central information provider for SAP and third-party tools that use this
data to deliver the services you need to keep your landscape up and running
For the System Landscape Directory as part of an SAP NetWeaver PI 71 landscape consider the following
aspects
Part of SAP NetWeaver PI 71 is a new version of the System Landscape Directory It is automatically
included in every SAP NetWeaver 71 system with usage type AS Java It offers enhanced functions
such as a full automatic synchronization mechanism for all data stored in it That is both data
delivered by data suppliers and data entered or changed manually in the System Landscape
Directory can be synchronized automatically This synchronization offers the following
A fully automated mechanism so no user interaction is required and conflicts are resolved
automatically
Asynchronous propagation of information so some nodes may be down temporarily
Communication over HTTP protocol
Uni- and bi-directional synchronization
Depending on your use case the full automatic synchronization could significantly reduce manual
synchronization effort
For SAP NetWeaver PI 71 the configuration of the system landscape directory and its data suppliers
is already included in the standard implementation procedure with SAPinst For existing systems
you only have to perform some quick and easy configuration actions to start operating the system
landscape directory server in an AS Java system
For SAP NetWeaver PI 71 you have the following options concerning SLD
Option 1
Run SAP NetWeaver PI 71 against an existing SLD running on SAP NetWeaver 70 We only
recommend this for upgrades from SAP NetWeaver 70 if you have a central SLD in operation
not running on one of your PI systems
Option 2
Use the SLD included in an SAP NetWeaver PI 71 system We recommend this option for new
installations and upgrades from older releases than SAP NetWeaver 70 due to the enhanced
functions and improved performance of SLD 71
NOTE
If you already have a central SLD running on SAP NetWeaver 70 in operation you could run
two SLD versions in parallel ndash SLD running on SAP NetWeaver 71 for your PI systems and
SLD running on SAP NetWeaver 70 for all other systemsuse cases This way your SAP
5 System Landscape
52 Shared Services
4456 PUBLIC 2011-04-15
NetWeaver PI 71 systems would benefit from the new features while it would be easy to set
up and operate such an SLD landscape For this purpose you could use the new fully
automatic synchronization This feature enables the automatic forwarding of all SLD data
from an SLD running on SAP NetWeaver 70 to an SLD running on SAP NetWeaver 71 As a
result there is no need to adapt most existing systems as their SLD data suppliers could still
send their data to the central SLD In brief the following steps would be required
1 Put SLD in a PI system into operation (part of standard implementation procedure)
2 Configure PI systems to use the new SLD (part of standard implementation procedure
for new PI systems)
3 Set up the fully automatic synchronization from your old SLD to your new SLD
As soon as an upgrade or an installation of a standalone AS Java 71 system is available you
could move your central SLD also to SAP NetWeaver 71 Then you could optionally shift
your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems
Figure 8
We recommend that you use a Domain Name System (DNS) alias so that you are able to switch to
another System Landscape Directory easily For example if customers build a new landscape they
normally start with a sandbox environment Over time more and more environments are set up
Once the production environment is in place move the System Landscape Directory there To do
this you can configure a new System Landscape Directory in the production environment
synchronize it with the old System Landscape directory and switch to the new one
Topology
Apart from the considerations above the System Landscape Directory offers several topology options
with different grades of availability at the expense of low administration and operation effort There is
no generic rule therefore on how to set up a System Landscape Directory in your system landscape
To find the topology and synchronization strategy for the System Landscape Directory that fits your
requirements concerning the System Landscape Directory availability (and hence the availability of
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4556
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
For more information about relevant aspects for the mapping of systems to hosts see the document
Technical Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
Scaling and Distribution Options
You may need to design your system landscape for a large number of users SAP NetWeaver PI offers
you different means of scalability The following list provides you with some examples
You could install multiple systems of one type and use them for different purposes
You could scale every system by installing dialog instances or by distributing the database instance
For more information about distribution options on the instance level see the Technical
Infrastructure Guide ndash SAP NetWeaver available on SAP Service Marketplace at http
servicesapcominstallNWPI71
For every SAP system you could additionally install Web Dispatcher For more information see
the SAP Library [page 12] at FunctionndashOriented View Application Server Infrastructure SAP Web
Dispatcher
You could further distribute certain standalone engines ndash for example Search and Classification
(TREX) is based on a flexible architecture that supports a distributed installation For more
information see the Technical Infrastructure Guide ndash SAP NetWeaver PI 71 available in SAP Service
Marketplace at httpservicesapcominstallNWPI71
52 Shared Services
You normally run shared services on central systems in your system landscape The following features
could be used for SAP NetWeaver Process Integration to realize shared services
SAP Solution Manager
Used to implement train test maintain monitor control change and manage incidents of your
SAP solution system landscape (open end-to-end application management)
As of SAP Solution Manager (70) 40 Support Package 15 SAP Solution Manager has become the
platform for SAPs end-to-end solution operations strategy Functions for complete application
management has been combined with administrative tools and has been merged in newly created
role based work centers
NOTE
Be aware that you require an SAP Solution Manager system to install or upgrade to SAP
NetWeaver 70 and higher An SAP Solution Manager system is required to generate the SAP
Solution Manager key needed during the installation or upgrade process Without this key
the installation or upgrade process cannot continue
For SAP NetWeaver Process Integration you require SAP Solution Manager 70
For more information see SAP Note 805390
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3556
Solution Manager Diagnostics
An integral part of SAP Solution Manager that is running as a Java application on the Java stack of
SAP Solution Manager 70 Solution Manager Diagnostics is used to analyze the root cause of
incidents in your landscape in an efficient and safe way Before Go-Live Solution Manager
Diagnostics has to be set up and made accessible remotely
SAP NetWeaver Administrator
SAP NetWeaver Administrator is the central administration component which is used for
monitoring and administering Java applications It is included in SAP NetWeaver systems with AS
Java
SAP NetWeaver Administrator exists in the following flavors
A local mode which runs out of the box and which focuses on administrating the underlying
SAP NetWeaver AS Java
NOTE
For a SAP NetWeaver PI 71 it has a special role which you need to activate using a
configuation wizard
A central mode which has to be configured before use and which deals with the system
landscape management
SAP has decided to merge the central mode of SAP NetWeaver Administrator into the new work
centers available as of SAP Solution Manager 70 SP 15 Thus it can be used in an administrative
context together with non-Java-based administration tools Although the central mode of SAP
NetWeaver Administrator will be still available for some time SAP will not develop this tool any
further SAP focuses on optimizing the administrative work centers of SAP Solution Manager
instead
The local mode of SAP NetWeaver Administrator stays untouched It is available for current and
future releases of SAP NetWeaver
SAP Central Process Scheduling by Redwood
SAP Central Process Scheduling application by Redwood enables central job scheduling and job
monitoring of current and old releases of AS ABAP systems (as of Basis Release 31) This application
is fully integrated in SAP NetWeaver Depending on the business needs SAP business applications
are the initial trigger for scheduled activities You can now manage jobs and job chains conveniently
using a graphical user interface
System Landscape Directory
The System Landscape Directory is the central directory of system landscape information relevant
for the management of your software life-cycle It contains a description of your system landscape
(that is software components that are currently installed) and a repository of software components
that can theoretically be installed in your landscape (such as the software components available
from SAP)
Adaptive Computing Controller
5 System Landscape
52 Shared Services
3656 PUBLIC 2011-04-15
The Adaptive Computing Controller enables users to control an adaptive computing landscape
from a single point through observation operation and dynamic resource distribution With
adaptive computing hardware software and system services are able to adapt to changing business
needs In the Adaptive Computing Controller the run-time data of logical and physical landscapes
can be monitored application services can be startedstoppedrelocated and hardware resources
can be assigned to application services The operation can also be mass executed and be planned as
tasks to be executed
For more information about the installation of the Adaptive Computing Controller tool see the
document Installation Guide ndash Adaptive Computing Controller in SAP NetWeaver 71 available on SAP Service
Marketplace at httpservicesapcominstallNWPI71
For more information about Adaptive Computing in general see httpsdnsapcomirj
sdnadaptive
521 Use Cases
You can use the applications and tools described above for use cases that are normally performed
centrally The following sections describe these use cases
5211 End-to-End Solution Operations
Running business applications through their complete life-cycle is a challenge Therefore SAP has
started the Run SAP methodology for implementing End-to-End Solution Operations Based on a set
of SAP standards a roadmap and a package for training and certification Run SAP helps customers to
facilitate End-to-End Solution Operations
You can download the SAP standards for Solution Operations from SAP Service Marketplace at http
servicesapcomsupportstandards They describe roles customers typically have in their IT
environment For optimal role support SAP has grouped existing and new functions in SAP Solution
Manager work centers as of SAP Solution Manager 70 Support Package 15 Operations aspects are fully
covered by adding administrative functions for SAP NetWeaver as well Work centers are ABAP Web
Dynpro-based applications They offer the following advantages
Easy to use similar look and feel
Context transfer while jumping from one work center into another
Logical grouping of tools for a certain area
Simple authorization concept
Easy to expand
Each IT role belongs to one or more work centers For instance the Technical Administrator IT role is
covered by the work centers for System Monitoring System Administration and Landscape Management
The following work centers are available
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3756
Business Process Operations
Change Management
Root Cause Analysis
Implementation Upgrade
Incident Management
Test Management
Job Management
System Landscape Management
Solution Documentation Assistant
SAP Engagement and Service Delivery
SAP Solution Manager Administration
System Administration
System Monitoring
My Home is the central point of access to all important data of almost all work centers in SAP Solution
Manager
5212 Support Infrastructure
A key requirement for effective support of IT solutions is the ability to perform root cause analysis with
speed and efficiency
With SAP Solution Manager SAP has long had an infrastructure in place for its ABAP applications that
efficiently supports SAP solutions This helps ensure the high availability and smooth running of
business processes For more information see the SAP Solution Manager section
With Solution Manager Diagnostics this knowledge has been extended to Java applications If for
example homegrown Java applications cause instability Solution Manager Diagnostics helps trace the
cause to eradicate the problem rapidly Solution Manager Diagnostics is fully integrated into SAP
Solution Manager 70 Solution Manager Diagnostics also contains two third-party tools CArsquos Wily
Introscopereg for measuring performance as well as troubleshooting problems of the Java EE Engine
and applications running on it and Mercury Loadrunnerreg which enables SAP Support to produce a
defined load in the SAP solution landscape remotely For more information see Solution Manager
Diagnostics [page 43]
The support infrastructure provides SAP Support with safe access to your productive landscape for safe
root cause analysis so ensuring that SAP Support does not change your landscape inadvertently You
require a support infrastructure to run SAP NetWeaver
The following figure shows the overall infrastructure including SAP NetWeaver administration tools
that are used by administrators or operators at the customer site
5 System Landscape
52 Shared Services
3856 PUBLIC 2011-04-15
Landscape Aspects
If you use SAP NetWeaver Process Integration 71 productively besides SAP Solution Manager (as a
central support platform) you have to set up Solution Manager Diagnostics for supportability reasons
Implementation Sequence
For information about the implementation of the support infrastructure see the document Master
Guide ndash SAP Solution Manager 70 available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution Manager ltReleasegt
5213 Collection of Landscape Data
Amongst other applications and services the support infrastructure and the SAP NetWeaver
administration tools rely on system landscape data
For SAP NetWeaver PI 71 you have to run non-ABAP components in your solution landscape
Therefore the System Landscape Directory is mandatory The landscape data that is automatically
gathered by the System Landscape Directory is replicated to SAP Solution Manager There are several
topology options for the System Landscape Directory They offer different grades of availability
administration and operation effort
For more information see the System Landscape Directory section
5214 Authentication and Single Sign-On
Before implementing your system landscape plan how to implement authentication and how to
integrate different systems into a Single Sign-On landscape Single Sign-On reduces complexity for end
users saving them valuable time while also reducing administration effort for resetting passwords
thereby contributing to TCO reduction
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
5215 Integrated User and Access Management
In a system landscape containing a combination of ABAP and Java components we recommend that
you integrate your user and access management so that you can use the same user data across different
systems administer this data centrally and control access to data SAPs mature fine-grained
authorization concept allows detailed control of access rights SAP NetWeaver provides both ABAP and
Java-based user management solutions The user management solution that you use to administer
your user data depends on factors such as the type of systems that are running in your landscape
If you want to use central user administration we recommend that you run it in a non-production
system If you do not have a central user administration yet you can for example realize it in the SAP
Solution Manager system
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3956
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
522 Examples for the Overall System Landscape of Shared Services
In this section we provide examples of how shared services can be set up depending on the system
landscape they are intended for The following examples aggregate the landscape aspects given in the
Use Cases section
NOTE
The following sections and the figure mostly do not show information about the life-cycle of
shared services For example you may also need a development and testquality assurance system
for SAP Solution Manager You should consider this aspect in addition to the information given
in this section based on your requirements
Small and MediumndashSized Customer Landscapes with Java
As you use Java productively for SAP NetWeaver PI 71 besides SAP Solution Manager you have to set
up additional components for optimal monitoring administration and support Solution Manager
Diagnostics and the central mode of SAP NetWeaver Administrator are already fully integrated into
SAP Solution Manager 70 as the central operations hub For SAP Process Integration you must also
set up SAP NetWeaver Administrator with a special role
We recommend that you do not install SAP Central Process Scheduling in the SAP Solution Manager
system You have to set up and operate the system which hosts your productive scheduler as a mission
critical system
In the SAP Solution Manager system you should set up a local System Landscape Directory in addition
to a central runtime System Landscape Directory This way you have a clear separation between your
management system (SAP Solution Manager) and managed systems in your landscape In addition
SAP Solution Manager then does not rely on a System Landscape Directory running in the production
environment For this setup configure the SLD data suppliers of your SAP Solution Manager system
to send data to the central runtime System Landscape Directory In addition configure automatic
bridge forwarding from your runtime System Landscape Directory to the local System Landscape
Directory For more information see the Planning Guide - System Landscape Directory
If you want to use a central system for Adobe Document Services we recommend that you install a
dedicated system for this purpose in your production environment For detailed information about
the sizing of the system for the different use cases see the Sizing Guide for Adobe Document Services at
SAP Service Marketplace at httpservicesapcomsizing Sizing Guidelines Solutions amp
Platform
We recommend that you start with this centralized SAP Solution Manager approach as depicted in the
following figure
5 System Landscape
52 Shared Services
4056 PUBLIC 2011-04-15
Figure 7 Single SAP Solution Manager Landscape
Large Customer Landscapes with Java
Large customers who have environments in their landscape that are large and distributed administered
by different groups or separated for security reasons can consider a distributed operations setup In
addition to the centralized setup described for small- and medium-sized customers above large
customers can put parts of the central management functions on extra hosts or systems for performance
or policy reasons You have the following options for a distributed setup
You may set up an extra system or client for Central User Administration (CUA)
The Change and Transport System (CTS) can run on an extra system However it is not
performance- or data-intensive
You may set up an extra system for central CCMS monitoring Depending on the customizing
and on the landscape size central CCMS may generate a lot of system load You can connect a
separate central CCMS to SAP Solution Manager for displaying alerts in the alert inbox of the System
Monitoring work center
You can use a separate SAP NetWeaver 70 system with usage type BI together with SAP Solution
Manager This may make sense with respect to the amount of landscape management data that is
stored for reporting purposes The amount of data strongly depends on the data granularity
storage time frame and landscape size
You can easily put Wily Introscope Enterprise Manager on an separate host
Other aspects described above for small- and medium-customers (such as the setup of the System
Landscape Directory) are also valid for large customers
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4156
523 Feature Details
This section provides further information about the features described above
5231 SAP Solution Manager
SAP provides you with SAP Solution Manager as the strategic application management platform and
to enable the collaboration between you and SAP You need to install at least one productive SAP
Solution Manager in your system landscape To ensure the availability of this application management
platform an SAP Solution Manager system is technically required to install or upgrade to SAP
NetWeaver 70 or higher If you are already using SAP Solution Manager you can also use it to manage
the solution you build with SAP NetWeaver In this case we highly recommend that you update SAP
Solution Manager to the latest version
As of SAP Solution Manager 70 SP15 you can use the newly created work centers
NOTE
During the SAP system installation or upgrade process you are prompted to enter the SAP
Solution Manager key An SAP Solution Manager system is required to generate this key Without
this key the installation or upgrade process cannot continue
You may generate all needed keys for your entire system landscape (development quality
assurance and production system) in one SAP Solution Manager system In case you plan to install
several solution landscapes (for example in different countries) one SAP Solution Manager
system is still sufficient
For more information see SAP Note 805390
It is possible to install multiple SAP Solution Managers If you do so they should host separate business
solutions
If you want to reduce the risk of unavailability you should not install SAP Solution Manager as a central
component Instead you can operate a 2-system-landscape with both a test and production
environment of SAP Solution Manager (especially if you are using time-critical functions like Support
Desk) If you also develop your own content a 3-system-landscape with a development test and
production environment is recommended
For more information about SAP Solution Manager see the following table
Topic Where to Find More Information
System infrastructure scenarios installation and configuration of SAP Solution Manager
Master Guide ndash SAP Solution Manager available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution ManagerltReleasegt
Benefits and usage scenarios SAP Solution Manager ndash Learning Maps available on SAP Service Marketplace at http
5 System Landscape
52 Shared Services
4256 PUBLIC 2011-04-15
Topic Where to Find More Informationservicesapcomrkt-solman or https
servicesapcomsolutionmanager
Additional information See SAP Service Marketplace at http
servicesapcomsolutionmanager
5232 Solution Manager Diagnostics
Solution Manager Diagnostics provides efficient and safe root-cause analysis of incidents in customer
solutions powered by SAP NetWeaver It can help monitor on operating systems databases Java
application activities performance and logs It also supports the reporting of software and
configuration changes that can lead to malfunctions and errors
You must run one Solution Manager Diagnostics within your SAP solution landscape if you run
applications based on SAP NetWeaver systems with usage type AS Java Agents are responsible for
delivering the data from all productive hosts within your system landscape to the Solution Manager
Diagnostics system
CAUTION
SAP Support performs root-cause analysis on incoming incidents with Solution Manager
Diagnostics Not installing and configuring this support infrastructure results in a dramatically
reduced service level
Solution Manager Diagnostics is fully integrated into SAP Solution Manager 70
Solution Manager Diagnostics also contains Wily Introscope (Display Server and Agent part) for
measuring performance as well as to troubleshoot problems of Non-ABAP applications Wily Introscope
is heavily used for troubleshooting applications running on AS Java
SAP has signed a distribution agreement for Wily Introscope SAP customers are allowed to use this
tool in a preconfigured way
For more information about Solution Manager Diagnostics and an FAQ list see SAP Service Marketplace
at httpservicesapcomdiagnostics
5233 System Landscape Directory
The System Landscape Directory (SLD) of SAP NetWeaver is the central directory of system landscape
information relevant for the management of your software life-cycle
NOTE
Note that the abbreviation SLD is not intended to define a product since the System Landscape
Directory is part of SAP NetWeaver This abbreviation is solely intended to improve readability
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4356
The System Landscape Directory contains a description of your system landscape (that is software
components that are currently installed) and a repository of software components that can
theoretically be installed in your landscape (such as the software components available from SAP)
Since this data gets updated automatically the System Landscape Directory provides reliable and up-
to-date system landscape information with as little effort for you as possible In this way the System
Landscape Directory acts as a central information provider for SAP and third-party tools that use this
data to deliver the services you need to keep your landscape up and running
For the System Landscape Directory as part of an SAP NetWeaver PI 71 landscape consider the following
aspects
Part of SAP NetWeaver PI 71 is a new version of the System Landscape Directory It is automatically
included in every SAP NetWeaver 71 system with usage type AS Java It offers enhanced functions
such as a full automatic synchronization mechanism for all data stored in it That is both data
delivered by data suppliers and data entered or changed manually in the System Landscape
Directory can be synchronized automatically This synchronization offers the following
A fully automated mechanism so no user interaction is required and conflicts are resolved
automatically
Asynchronous propagation of information so some nodes may be down temporarily
Communication over HTTP protocol
Uni- and bi-directional synchronization
Depending on your use case the full automatic synchronization could significantly reduce manual
synchronization effort
For SAP NetWeaver PI 71 the configuration of the system landscape directory and its data suppliers
is already included in the standard implementation procedure with SAPinst For existing systems
you only have to perform some quick and easy configuration actions to start operating the system
landscape directory server in an AS Java system
For SAP NetWeaver PI 71 you have the following options concerning SLD
Option 1
Run SAP NetWeaver PI 71 against an existing SLD running on SAP NetWeaver 70 We only
recommend this for upgrades from SAP NetWeaver 70 if you have a central SLD in operation
not running on one of your PI systems
Option 2
Use the SLD included in an SAP NetWeaver PI 71 system We recommend this option for new
installations and upgrades from older releases than SAP NetWeaver 70 due to the enhanced
functions and improved performance of SLD 71
NOTE
If you already have a central SLD running on SAP NetWeaver 70 in operation you could run
two SLD versions in parallel ndash SLD running on SAP NetWeaver 71 for your PI systems and
SLD running on SAP NetWeaver 70 for all other systemsuse cases This way your SAP
5 System Landscape
52 Shared Services
4456 PUBLIC 2011-04-15
NetWeaver PI 71 systems would benefit from the new features while it would be easy to set
up and operate such an SLD landscape For this purpose you could use the new fully
automatic synchronization This feature enables the automatic forwarding of all SLD data
from an SLD running on SAP NetWeaver 70 to an SLD running on SAP NetWeaver 71 As a
result there is no need to adapt most existing systems as their SLD data suppliers could still
send their data to the central SLD In brief the following steps would be required
1 Put SLD in a PI system into operation (part of standard implementation procedure)
2 Configure PI systems to use the new SLD (part of standard implementation procedure
for new PI systems)
3 Set up the fully automatic synchronization from your old SLD to your new SLD
As soon as an upgrade or an installation of a standalone AS Java 71 system is available you
could move your central SLD also to SAP NetWeaver 71 Then you could optionally shift
your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems
Figure 8
We recommend that you use a Domain Name System (DNS) alias so that you are able to switch to
another System Landscape Directory easily For example if customers build a new landscape they
normally start with a sandbox environment Over time more and more environments are set up
Once the production environment is in place move the System Landscape Directory there To do
this you can configure a new System Landscape Directory in the production environment
synchronize it with the old System Landscape directory and switch to the new one
Topology
Apart from the considerations above the System Landscape Directory offers several topology options
with different grades of availability at the expense of low administration and operation effort There is
no generic rule therefore on how to set up a System Landscape Directory in your system landscape
To find the topology and synchronization strategy for the System Landscape Directory that fits your
requirements concerning the System Landscape Directory availability (and hence the availability of
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4556
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
Solution Manager Diagnostics
An integral part of SAP Solution Manager that is running as a Java application on the Java stack of
SAP Solution Manager 70 Solution Manager Diagnostics is used to analyze the root cause of
incidents in your landscape in an efficient and safe way Before Go-Live Solution Manager
Diagnostics has to be set up and made accessible remotely
SAP NetWeaver Administrator
SAP NetWeaver Administrator is the central administration component which is used for
monitoring and administering Java applications It is included in SAP NetWeaver systems with AS
Java
SAP NetWeaver Administrator exists in the following flavors
A local mode which runs out of the box and which focuses on administrating the underlying
SAP NetWeaver AS Java
NOTE
For a SAP NetWeaver PI 71 it has a special role which you need to activate using a
configuation wizard
A central mode which has to be configured before use and which deals with the system
landscape management
SAP has decided to merge the central mode of SAP NetWeaver Administrator into the new work
centers available as of SAP Solution Manager 70 SP 15 Thus it can be used in an administrative
context together with non-Java-based administration tools Although the central mode of SAP
NetWeaver Administrator will be still available for some time SAP will not develop this tool any
further SAP focuses on optimizing the administrative work centers of SAP Solution Manager
instead
The local mode of SAP NetWeaver Administrator stays untouched It is available for current and
future releases of SAP NetWeaver
SAP Central Process Scheduling by Redwood
SAP Central Process Scheduling application by Redwood enables central job scheduling and job
monitoring of current and old releases of AS ABAP systems (as of Basis Release 31) This application
is fully integrated in SAP NetWeaver Depending on the business needs SAP business applications
are the initial trigger for scheduled activities You can now manage jobs and job chains conveniently
using a graphical user interface
System Landscape Directory
The System Landscape Directory is the central directory of system landscape information relevant
for the management of your software life-cycle It contains a description of your system landscape
(that is software components that are currently installed) and a repository of software components
that can theoretically be installed in your landscape (such as the software components available
from SAP)
Adaptive Computing Controller
5 System Landscape
52 Shared Services
3656 PUBLIC 2011-04-15
The Adaptive Computing Controller enables users to control an adaptive computing landscape
from a single point through observation operation and dynamic resource distribution With
adaptive computing hardware software and system services are able to adapt to changing business
needs In the Adaptive Computing Controller the run-time data of logical and physical landscapes
can be monitored application services can be startedstoppedrelocated and hardware resources
can be assigned to application services The operation can also be mass executed and be planned as
tasks to be executed
For more information about the installation of the Adaptive Computing Controller tool see the
document Installation Guide ndash Adaptive Computing Controller in SAP NetWeaver 71 available on SAP Service
Marketplace at httpservicesapcominstallNWPI71
For more information about Adaptive Computing in general see httpsdnsapcomirj
sdnadaptive
521 Use Cases
You can use the applications and tools described above for use cases that are normally performed
centrally The following sections describe these use cases
5211 End-to-End Solution Operations
Running business applications through their complete life-cycle is a challenge Therefore SAP has
started the Run SAP methodology for implementing End-to-End Solution Operations Based on a set
of SAP standards a roadmap and a package for training and certification Run SAP helps customers to
facilitate End-to-End Solution Operations
You can download the SAP standards for Solution Operations from SAP Service Marketplace at http
servicesapcomsupportstandards They describe roles customers typically have in their IT
environment For optimal role support SAP has grouped existing and new functions in SAP Solution
Manager work centers as of SAP Solution Manager 70 Support Package 15 Operations aspects are fully
covered by adding administrative functions for SAP NetWeaver as well Work centers are ABAP Web
Dynpro-based applications They offer the following advantages
Easy to use similar look and feel
Context transfer while jumping from one work center into another
Logical grouping of tools for a certain area
Simple authorization concept
Easy to expand
Each IT role belongs to one or more work centers For instance the Technical Administrator IT role is
covered by the work centers for System Monitoring System Administration and Landscape Management
The following work centers are available
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3756
Business Process Operations
Change Management
Root Cause Analysis
Implementation Upgrade
Incident Management
Test Management
Job Management
System Landscape Management
Solution Documentation Assistant
SAP Engagement and Service Delivery
SAP Solution Manager Administration
System Administration
System Monitoring
My Home is the central point of access to all important data of almost all work centers in SAP Solution
Manager
5212 Support Infrastructure
A key requirement for effective support of IT solutions is the ability to perform root cause analysis with
speed and efficiency
With SAP Solution Manager SAP has long had an infrastructure in place for its ABAP applications that
efficiently supports SAP solutions This helps ensure the high availability and smooth running of
business processes For more information see the SAP Solution Manager section
With Solution Manager Diagnostics this knowledge has been extended to Java applications If for
example homegrown Java applications cause instability Solution Manager Diagnostics helps trace the
cause to eradicate the problem rapidly Solution Manager Diagnostics is fully integrated into SAP
Solution Manager 70 Solution Manager Diagnostics also contains two third-party tools CArsquos Wily
Introscopereg for measuring performance as well as troubleshooting problems of the Java EE Engine
and applications running on it and Mercury Loadrunnerreg which enables SAP Support to produce a
defined load in the SAP solution landscape remotely For more information see Solution Manager
Diagnostics [page 43]
The support infrastructure provides SAP Support with safe access to your productive landscape for safe
root cause analysis so ensuring that SAP Support does not change your landscape inadvertently You
require a support infrastructure to run SAP NetWeaver
The following figure shows the overall infrastructure including SAP NetWeaver administration tools
that are used by administrators or operators at the customer site
5 System Landscape
52 Shared Services
3856 PUBLIC 2011-04-15
Landscape Aspects
If you use SAP NetWeaver Process Integration 71 productively besides SAP Solution Manager (as a
central support platform) you have to set up Solution Manager Diagnostics for supportability reasons
Implementation Sequence
For information about the implementation of the support infrastructure see the document Master
Guide ndash SAP Solution Manager 70 available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution Manager ltReleasegt
5213 Collection of Landscape Data
Amongst other applications and services the support infrastructure and the SAP NetWeaver
administration tools rely on system landscape data
For SAP NetWeaver PI 71 you have to run non-ABAP components in your solution landscape
Therefore the System Landscape Directory is mandatory The landscape data that is automatically
gathered by the System Landscape Directory is replicated to SAP Solution Manager There are several
topology options for the System Landscape Directory They offer different grades of availability
administration and operation effort
For more information see the System Landscape Directory section
5214 Authentication and Single Sign-On
Before implementing your system landscape plan how to implement authentication and how to
integrate different systems into a Single Sign-On landscape Single Sign-On reduces complexity for end
users saving them valuable time while also reducing administration effort for resetting passwords
thereby contributing to TCO reduction
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
5215 Integrated User and Access Management
In a system landscape containing a combination of ABAP and Java components we recommend that
you integrate your user and access management so that you can use the same user data across different
systems administer this data centrally and control access to data SAPs mature fine-grained
authorization concept allows detailed control of access rights SAP NetWeaver provides both ABAP and
Java-based user management solutions The user management solution that you use to administer
your user data depends on factors such as the type of systems that are running in your landscape
If you want to use central user administration we recommend that you run it in a non-production
system If you do not have a central user administration yet you can for example realize it in the SAP
Solution Manager system
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3956
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
522 Examples for the Overall System Landscape of Shared Services
In this section we provide examples of how shared services can be set up depending on the system
landscape they are intended for The following examples aggregate the landscape aspects given in the
Use Cases section
NOTE
The following sections and the figure mostly do not show information about the life-cycle of
shared services For example you may also need a development and testquality assurance system
for SAP Solution Manager You should consider this aspect in addition to the information given
in this section based on your requirements
Small and MediumndashSized Customer Landscapes with Java
As you use Java productively for SAP NetWeaver PI 71 besides SAP Solution Manager you have to set
up additional components for optimal monitoring administration and support Solution Manager
Diagnostics and the central mode of SAP NetWeaver Administrator are already fully integrated into
SAP Solution Manager 70 as the central operations hub For SAP Process Integration you must also
set up SAP NetWeaver Administrator with a special role
We recommend that you do not install SAP Central Process Scheduling in the SAP Solution Manager
system You have to set up and operate the system which hosts your productive scheduler as a mission
critical system
In the SAP Solution Manager system you should set up a local System Landscape Directory in addition
to a central runtime System Landscape Directory This way you have a clear separation between your
management system (SAP Solution Manager) and managed systems in your landscape In addition
SAP Solution Manager then does not rely on a System Landscape Directory running in the production
environment For this setup configure the SLD data suppliers of your SAP Solution Manager system
to send data to the central runtime System Landscape Directory In addition configure automatic
bridge forwarding from your runtime System Landscape Directory to the local System Landscape
Directory For more information see the Planning Guide - System Landscape Directory
If you want to use a central system for Adobe Document Services we recommend that you install a
dedicated system for this purpose in your production environment For detailed information about
the sizing of the system for the different use cases see the Sizing Guide for Adobe Document Services at
SAP Service Marketplace at httpservicesapcomsizing Sizing Guidelines Solutions amp
Platform
We recommend that you start with this centralized SAP Solution Manager approach as depicted in the
following figure
5 System Landscape
52 Shared Services
4056 PUBLIC 2011-04-15
Figure 7 Single SAP Solution Manager Landscape
Large Customer Landscapes with Java
Large customers who have environments in their landscape that are large and distributed administered
by different groups or separated for security reasons can consider a distributed operations setup In
addition to the centralized setup described for small- and medium-sized customers above large
customers can put parts of the central management functions on extra hosts or systems for performance
or policy reasons You have the following options for a distributed setup
You may set up an extra system or client for Central User Administration (CUA)
The Change and Transport System (CTS) can run on an extra system However it is not
performance- or data-intensive
You may set up an extra system for central CCMS monitoring Depending on the customizing
and on the landscape size central CCMS may generate a lot of system load You can connect a
separate central CCMS to SAP Solution Manager for displaying alerts in the alert inbox of the System
Monitoring work center
You can use a separate SAP NetWeaver 70 system with usage type BI together with SAP Solution
Manager This may make sense with respect to the amount of landscape management data that is
stored for reporting purposes The amount of data strongly depends on the data granularity
storage time frame and landscape size
You can easily put Wily Introscope Enterprise Manager on an separate host
Other aspects described above for small- and medium-customers (such as the setup of the System
Landscape Directory) are also valid for large customers
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4156
523 Feature Details
This section provides further information about the features described above
5231 SAP Solution Manager
SAP provides you with SAP Solution Manager as the strategic application management platform and
to enable the collaboration between you and SAP You need to install at least one productive SAP
Solution Manager in your system landscape To ensure the availability of this application management
platform an SAP Solution Manager system is technically required to install or upgrade to SAP
NetWeaver 70 or higher If you are already using SAP Solution Manager you can also use it to manage
the solution you build with SAP NetWeaver In this case we highly recommend that you update SAP
Solution Manager to the latest version
As of SAP Solution Manager 70 SP15 you can use the newly created work centers
NOTE
During the SAP system installation or upgrade process you are prompted to enter the SAP
Solution Manager key An SAP Solution Manager system is required to generate this key Without
this key the installation or upgrade process cannot continue
You may generate all needed keys for your entire system landscape (development quality
assurance and production system) in one SAP Solution Manager system In case you plan to install
several solution landscapes (for example in different countries) one SAP Solution Manager
system is still sufficient
For more information see SAP Note 805390
It is possible to install multiple SAP Solution Managers If you do so they should host separate business
solutions
If you want to reduce the risk of unavailability you should not install SAP Solution Manager as a central
component Instead you can operate a 2-system-landscape with both a test and production
environment of SAP Solution Manager (especially if you are using time-critical functions like Support
Desk) If you also develop your own content a 3-system-landscape with a development test and
production environment is recommended
For more information about SAP Solution Manager see the following table
Topic Where to Find More Information
System infrastructure scenarios installation and configuration of SAP Solution Manager
Master Guide ndash SAP Solution Manager available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution ManagerltReleasegt
Benefits and usage scenarios SAP Solution Manager ndash Learning Maps available on SAP Service Marketplace at http
5 System Landscape
52 Shared Services
4256 PUBLIC 2011-04-15
Topic Where to Find More Informationservicesapcomrkt-solman or https
servicesapcomsolutionmanager
Additional information See SAP Service Marketplace at http
servicesapcomsolutionmanager
5232 Solution Manager Diagnostics
Solution Manager Diagnostics provides efficient and safe root-cause analysis of incidents in customer
solutions powered by SAP NetWeaver It can help monitor on operating systems databases Java
application activities performance and logs It also supports the reporting of software and
configuration changes that can lead to malfunctions and errors
You must run one Solution Manager Diagnostics within your SAP solution landscape if you run
applications based on SAP NetWeaver systems with usage type AS Java Agents are responsible for
delivering the data from all productive hosts within your system landscape to the Solution Manager
Diagnostics system
CAUTION
SAP Support performs root-cause analysis on incoming incidents with Solution Manager
Diagnostics Not installing and configuring this support infrastructure results in a dramatically
reduced service level
Solution Manager Diagnostics is fully integrated into SAP Solution Manager 70
Solution Manager Diagnostics also contains Wily Introscope (Display Server and Agent part) for
measuring performance as well as to troubleshoot problems of Non-ABAP applications Wily Introscope
is heavily used for troubleshooting applications running on AS Java
SAP has signed a distribution agreement for Wily Introscope SAP customers are allowed to use this
tool in a preconfigured way
For more information about Solution Manager Diagnostics and an FAQ list see SAP Service Marketplace
at httpservicesapcomdiagnostics
5233 System Landscape Directory
The System Landscape Directory (SLD) of SAP NetWeaver is the central directory of system landscape
information relevant for the management of your software life-cycle
NOTE
Note that the abbreviation SLD is not intended to define a product since the System Landscape
Directory is part of SAP NetWeaver This abbreviation is solely intended to improve readability
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4356
The System Landscape Directory contains a description of your system landscape (that is software
components that are currently installed) and a repository of software components that can
theoretically be installed in your landscape (such as the software components available from SAP)
Since this data gets updated automatically the System Landscape Directory provides reliable and up-
to-date system landscape information with as little effort for you as possible In this way the System
Landscape Directory acts as a central information provider for SAP and third-party tools that use this
data to deliver the services you need to keep your landscape up and running
For the System Landscape Directory as part of an SAP NetWeaver PI 71 landscape consider the following
aspects
Part of SAP NetWeaver PI 71 is a new version of the System Landscape Directory It is automatically
included in every SAP NetWeaver 71 system with usage type AS Java It offers enhanced functions
such as a full automatic synchronization mechanism for all data stored in it That is both data
delivered by data suppliers and data entered or changed manually in the System Landscape
Directory can be synchronized automatically This synchronization offers the following
A fully automated mechanism so no user interaction is required and conflicts are resolved
automatically
Asynchronous propagation of information so some nodes may be down temporarily
Communication over HTTP protocol
Uni- and bi-directional synchronization
Depending on your use case the full automatic synchronization could significantly reduce manual
synchronization effort
For SAP NetWeaver PI 71 the configuration of the system landscape directory and its data suppliers
is already included in the standard implementation procedure with SAPinst For existing systems
you only have to perform some quick and easy configuration actions to start operating the system
landscape directory server in an AS Java system
For SAP NetWeaver PI 71 you have the following options concerning SLD
Option 1
Run SAP NetWeaver PI 71 against an existing SLD running on SAP NetWeaver 70 We only
recommend this for upgrades from SAP NetWeaver 70 if you have a central SLD in operation
not running on one of your PI systems
Option 2
Use the SLD included in an SAP NetWeaver PI 71 system We recommend this option for new
installations and upgrades from older releases than SAP NetWeaver 70 due to the enhanced
functions and improved performance of SLD 71
NOTE
If you already have a central SLD running on SAP NetWeaver 70 in operation you could run
two SLD versions in parallel ndash SLD running on SAP NetWeaver 71 for your PI systems and
SLD running on SAP NetWeaver 70 for all other systemsuse cases This way your SAP
5 System Landscape
52 Shared Services
4456 PUBLIC 2011-04-15
NetWeaver PI 71 systems would benefit from the new features while it would be easy to set
up and operate such an SLD landscape For this purpose you could use the new fully
automatic synchronization This feature enables the automatic forwarding of all SLD data
from an SLD running on SAP NetWeaver 70 to an SLD running on SAP NetWeaver 71 As a
result there is no need to adapt most existing systems as their SLD data suppliers could still
send their data to the central SLD In brief the following steps would be required
1 Put SLD in a PI system into operation (part of standard implementation procedure)
2 Configure PI systems to use the new SLD (part of standard implementation procedure
for new PI systems)
3 Set up the fully automatic synchronization from your old SLD to your new SLD
As soon as an upgrade or an installation of a standalone AS Java 71 system is available you
could move your central SLD also to SAP NetWeaver 71 Then you could optionally shift
your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems
Figure 8
We recommend that you use a Domain Name System (DNS) alias so that you are able to switch to
another System Landscape Directory easily For example if customers build a new landscape they
normally start with a sandbox environment Over time more and more environments are set up
Once the production environment is in place move the System Landscape Directory there To do
this you can configure a new System Landscape Directory in the production environment
synchronize it with the old System Landscape directory and switch to the new one
Topology
Apart from the considerations above the System Landscape Directory offers several topology options
with different grades of availability at the expense of low administration and operation effort There is
no generic rule therefore on how to set up a System Landscape Directory in your system landscape
To find the topology and synchronization strategy for the System Landscape Directory that fits your
requirements concerning the System Landscape Directory availability (and hence the availability of
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4556
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
The Adaptive Computing Controller enables users to control an adaptive computing landscape
from a single point through observation operation and dynamic resource distribution With
adaptive computing hardware software and system services are able to adapt to changing business
needs In the Adaptive Computing Controller the run-time data of logical and physical landscapes
can be monitored application services can be startedstoppedrelocated and hardware resources
can be assigned to application services The operation can also be mass executed and be planned as
tasks to be executed
For more information about the installation of the Adaptive Computing Controller tool see the
document Installation Guide ndash Adaptive Computing Controller in SAP NetWeaver 71 available on SAP Service
Marketplace at httpservicesapcominstallNWPI71
For more information about Adaptive Computing in general see httpsdnsapcomirj
sdnadaptive
521 Use Cases
You can use the applications and tools described above for use cases that are normally performed
centrally The following sections describe these use cases
5211 End-to-End Solution Operations
Running business applications through their complete life-cycle is a challenge Therefore SAP has
started the Run SAP methodology for implementing End-to-End Solution Operations Based on a set
of SAP standards a roadmap and a package for training and certification Run SAP helps customers to
facilitate End-to-End Solution Operations
You can download the SAP standards for Solution Operations from SAP Service Marketplace at http
servicesapcomsupportstandards They describe roles customers typically have in their IT
environment For optimal role support SAP has grouped existing and new functions in SAP Solution
Manager work centers as of SAP Solution Manager 70 Support Package 15 Operations aspects are fully
covered by adding administrative functions for SAP NetWeaver as well Work centers are ABAP Web
Dynpro-based applications They offer the following advantages
Easy to use similar look and feel
Context transfer while jumping from one work center into another
Logical grouping of tools for a certain area
Simple authorization concept
Easy to expand
Each IT role belongs to one or more work centers For instance the Technical Administrator IT role is
covered by the work centers for System Monitoring System Administration and Landscape Management
The following work centers are available
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3756
Business Process Operations
Change Management
Root Cause Analysis
Implementation Upgrade
Incident Management
Test Management
Job Management
System Landscape Management
Solution Documentation Assistant
SAP Engagement and Service Delivery
SAP Solution Manager Administration
System Administration
System Monitoring
My Home is the central point of access to all important data of almost all work centers in SAP Solution
Manager
5212 Support Infrastructure
A key requirement for effective support of IT solutions is the ability to perform root cause analysis with
speed and efficiency
With SAP Solution Manager SAP has long had an infrastructure in place for its ABAP applications that
efficiently supports SAP solutions This helps ensure the high availability and smooth running of
business processes For more information see the SAP Solution Manager section
With Solution Manager Diagnostics this knowledge has been extended to Java applications If for
example homegrown Java applications cause instability Solution Manager Diagnostics helps trace the
cause to eradicate the problem rapidly Solution Manager Diagnostics is fully integrated into SAP
Solution Manager 70 Solution Manager Diagnostics also contains two third-party tools CArsquos Wily
Introscopereg for measuring performance as well as troubleshooting problems of the Java EE Engine
and applications running on it and Mercury Loadrunnerreg which enables SAP Support to produce a
defined load in the SAP solution landscape remotely For more information see Solution Manager
Diagnostics [page 43]
The support infrastructure provides SAP Support with safe access to your productive landscape for safe
root cause analysis so ensuring that SAP Support does not change your landscape inadvertently You
require a support infrastructure to run SAP NetWeaver
The following figure shows the overall infrastructure including SAP NetWeaver administration tools
that are used by administrators or operators at the customer site
5 System Landscape
52 Shared Services
3856 PUBLIC 2011-04-15
Landscape Aspects
If you use SAP NetWeaver Process Integration 71 productively besides SAP Solution Manager (as a
central support platform) you have to set up Solution Manager Diagnostics for supportability reasons
Implementation Sequence
For information about the implementation of the support infrastructure see the document Master
Guide ndash SAP Solution Manager 70 available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution Manager ltReleasegt
5213 Collection of Landscape Data
Amongst other applications and services the support infrastructure and the SAP NetWeaver
administration tools rely on system landscape data
For SAP NetWeaver PI 71 you have to run non-ABAP components in your solution landscape
Therefore the System Landscape Directory is mandatory The landscape data that is automatically
gathered by the System Landscape Directory is replicated to SAP Solution Manager There are several
topology options for the System Landscape Directory They offer different grades of availability
administration and operation effort
For more information see the System Landscape Directory section
5214 Authentication and Single Sign-On
Before implementing your system landscape plan how to implement authentication and how to
integrate different systems into a Single Sign-On landscape Single Sign-On reduces complexity for end
users saving them valuable time while also reducing administration effort for resetting passwords
thereby contributing to TCO reduction
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
5215 Integrated User and Access Management
In a system landscape containing a combination of ABAP and Java components we recommend that
you integrate your user and access management so that you can use the same user data across different
systems administer this data centrally and control access to data SAPs mature fine-grained
authorization concept allows detailed control of access rights SAP NetWeaver provides both ABAP and
Java-based user management solutions The user management solution that you use to administer
your user data depends on factors such as the type of systems that are running in your landscape
If you want to use central user administration we recommend that you run it in a non-production
system If you do not have a central user administration yet you can for example realize it in the SAP
Solution Manager system
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3956
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
522 Examples for the Overall System Landscape of Shared Services
In this section we provide examples of how shared services can be set up depending on the system
landscape they are intended for The following examples aggregate the landscape aspects given in the
Use Cases section
NOTE
The following sections and the figure mostly do not show information about the life-cycle of
shared services For example you may also need a development and testquality assurance system
for SAP Solution Manager You should consider this aspect in addition to the information given
in this section based on your requirements
Small and MediumndashSized Customer Landscapes with Java
As you use Java productively for SAP NetWeaver PI 71 besides SAP Solution Manager you have to set
up additional components for optimal monitoring administration and support Solution Manager
Diagnostics and the central mode of SAP NetWeaver Administrator are already fully integrated into
SAP Solution Manager 70 as the central operations hub For SAP Process Integration you must also
set up SAP NetWeaver Administrator with a special role
We recommend that you do not install SAP Central Process Scheduling in the SAP Solution Manager
system You have to set up and operate the system which hosts your productive scheduler as a mission
critical system
In the SAP Solution Manager system you should set up a local System Landscape Directory in addition
to a central runtime System Landscape Directory This way you have a clear separation between your
management system (SAP Solution Manager) and managed systems in your landscape In addition
SAP Solution Manager then does not rely on a System Landscape Directory running in the production
environment For this setup configure the SLD data suppliers of your SAP Solution Manager system
to send data to the central runtime System Landscape Directory In addition configure automatic
bridge forwarding from your runtime System Landscape Directory to the local System Landscape
Directory For more information see the Planning Guide - System Landscape Directory
If you want to use a central system for Adobe Document Services we recommend that you install a
dedicated system for this purpose in your production environment For detailed information about
the sizing of the system for the different use cases see the Sizing Guide for Adobe Document Services at
SAP Service Marketplace at httpservicesapcomsizing Sizing Guidelines Solutions amp
Platform
We recommend that you start with this centralized SAP Solution Manager approach as depicted in the
following figure
5 System Landscape
52 Shared Services
4056 PUBLIC 2011-04-15
Figure 7 Single SAP Solution Manager Landscape
Large Customer Landscapes with Java
Large customers who have environments in their landscape that are large and distributed administered
by different groups or separated for security reasons can consider a distributed operations setup In
addition to the centralized setup described for small- and medium-sized customers above large
customers can put parts of the central management functions on extra hosts or systems for performance
or policy reasons You have the following options for a distributed setup
You may set up an extra system or client for Central User Administration (CUA)
The Change and Transport System (CTS) can run on an extra system However it is not
performance- or data-intensive
You may set up an extra system for central CCMS monitoring Depending on the customizing
and on the landscape size central CCMS may generate a lot of system load You can connect a
separate central CCMS to SAP Solution Manager for displaying alerts in the alert inbox of the System
Monitoring work center
You can use a separate SAP NetWeaver 70 system with usage type BI together with SAP Solution
Manager This may make sense with respect to the amount of landscape management data that is
stored for reporting purposes The amount of data strongly depends on the data granularity
storage time frame and landscape size
You can easily put Wily Introscope Enterprise Manager on an separate host
Other aspects described above for small- and medium-customers (such as the setup of the System
Landscape Directory) are also valid for large customers
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4156
523 Feature Details
This section provides further information about the features described above
5231 SAP Solution Manager
SAP provides you with SAP Solution Manager as the strategic application management platform and
to enable the collaboration between you and SAP You need to install at least one productive SAP
Solution Manager in your system landscape To ensure the availability of this application management
platform an SAP Solution Manager system is technically required to install or upgrade to SAP
NetWeaver 70 or higher If you are already using SAP Solution Manager you can also use it to manage
the solution you build with SAP NetWeaver In this case we highly recommend that you update SAP
Solution Manager to the latest version
As of SAP Solution Manager 70 SP15 you can use the newly created work centers
NOTE
During the SAP system installation or upgrade process you are prompted to enter the SAP
Solution Manager key An SAP Solution Manager system is required to generate this key Without
this key the installation or upgrade process cannot continue
You may generate all needed keys for your entire system landscape (development quality
assurance and production system) in one SAP Solution Manager system In case you plan to install
several solution landscapes (for example in different countries) one SAP Solution Manager
system is still sufficient
For more information see SAP Note 805390
It is possible to install multiple SAP Solution Managers If you do so they should host separate business
solutions
If you want to reduce the risk of unavailability you should not install SAP Solution Manager as a central
component Instead you can operate a 2-system-landscape with both a test and production
environment of SAP Solution Manager (especially if you are using time-critical functions like Support
Desk) If you also develop your own content a 3-system-landscape with a development test and
production environment is recommended
For more information about SAP Solution Manager see the following table
Topic Where to Find More Information
System infrastructure scenarios installation and configuration of SAP Solution Manager
Master Guide ndash SAP Solution Manager available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution ManagerltReleasegt
Benefits and usage scenarios SAP Solution Manager ndash Learning Maps available on SAP Service Marketplace at http
5 System Landscape
52 Shared Services
4256 PUBLIC 2011-04-15
Topic Where to Find More Informationservicesapcomrkt-solman or https
servicesapcomsolutionmanager
Additional information See SAP Service Marketplace at http
servicesapcomsolutionmanager
5232 Solution Manager Diagnostics
Solution Manager Diagnostics provides efficient and safe root-cause analysis of incidents in customer
solutions powered by SAP NetWeaver It can help monitor on operating systems databases Java
application activities performance and logs It also supports the reporting of software and
configuration changes that can lead to malfunctions and errors
You must run one Solution Manager Diagnostics within your SAP solution landscape if you run
applications based on SAP NetWeaver systems with usage type AS Java Agents are responsible for
delivering the data from all productive hosts within your system landscape to the Solution Manager
Diagnostics system
CAUTION
SAP Support performs root-cause analysis on incoming incidents with Solution Manager
Diagnostics Not installing and configuring this support infrastructure results in a dramatically
reduced service level
Solution Manager Diagnostics is fully integrated into SAP Solution Manager 70
Solution Manager Diagnostics also contains Wily Introscope (Display Server and Agent part) for
measuring performance as well as to troubleshoot problems of Non-ABAP applications Wily Introscope
is heavily used for troubleshooting applications running on AS Java
SAP has signed a distribution agreement for Wily Introscope SAP customers are allowed to use this
tool in a preconfigured way
For more information about Solution Manager Diagnostics and an FAQ list see SAP Service Marketplace
at httpservicesapcomdiagnostics
5233 System Landscape Directory
The System Landscape Directory (SLD) of SAP NetWeaver is the central directory of system landscape
information relevant for the management of your software life-cycle
NOTE
Note that the abbreviation SLD is not intended to define a product since the System Landscape
Directory is part of SAP NetWeaver This abbreviation is solely intended to improve readability
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4356
The System Landscape Directory contains a description of your system landscape (that is software
components that are currently installed) and a repository of software components that can
theoretically be installed in your landscape (such as the software components available from SAP)
Since this data gets updated automatically the System Landscape Directory provides reliable and up-
to-date system landscape information with as little effort for you as possible In this way the System
Landscape Directory acts as a central information provider for SAP and third-party tools that use this
data to deliver the services you need to keep your landscape up and running
For the System Landscape Directory as part of an SAP NetWeaver PI 71 landscape consider the following
aspects
Part of SAP NetWeaver PI 71 is a new version of the System Landscape Directory It is automatically
included in every SAP NetWeaver 71 system with usage type AS Java It offers enhanced functions
such as a full automatic synchronization mechanism for all data stored in it That is both data
delivered by data suppliers and data entered or changed manually in the System Landscape
Directory can be synchronized automatically This synchronization offers the following
A fully automated mechanism so no user interaction is required and conflicts are resolved
automatically
Asynchronous propagation of information so some nodes may be down temporarily
Communication over HTTP protocol
Uni- and bi-directional synchronization
Depending on your use case the full automatic synchronization could significantly reduce manual
synchronization effort
For SAP NetWeaver PI 71 the configuration of the system landscape directory and its data suppliers
is already included in the standard implementation procedure with SAPinst For existing systems
you only have to perform some quick and easy configuration actions to start operating the system
landscape directory server in an AS Java system
For SAP NetWeaver PI 71 you have the following options concerning SLD
Option 1
Run SAP NetWeaver PI 71 against an existing SLD running on SAP NetWeaver 70 We only
recommend this for upgrades from SAP NetWeaver 70 if you have a central SLD in operation
not running on one of your PI systems
Option 2
Use the SLD included in an SAP NetWeaver PI 71 system We recommend this option for new
installations and upgrades from older releases than SAP NetWeaver 70 due to the enhanced
functions and improved performance of SLD 71
NOTE
If you already have a central SLD running on SAP NetWeaver 70 in operation you could run
two SLD versions in parallel ndash SLD running on SAP NetWeaver 71 for your PI systems and
SLD running on SAP NetWeaver 70 for all other systemsuse cases This way your SAP
5 System Landscape
52 Shared Services
4456 PUBLIC 2011-04-15
NetWeaver PI 71 systems would benefit from the new features while it would be easy to set
up and operate such an SLD landscape For this purpose you could use the new fully
automatic synchronization This feature enables the automatic forwarding of all SLD data
from an SLD running on SAP NetWeaver 70 to an SLD running on SAP NetWeaver 71 As a
result there is no need to adapt most existing systems as their SLD data suppliers could still
send their data to the central SLD In brief the following steps would be required
1 Put SLD in a PI system into operation (part of standard implementation procedure)
2 Configure PI systems to use the new SLD (part of standard implementation procedure
for new PI systems)
3 Set up the fully automatic synchronization from your old SLD to your new SLD
As soon as an upgrade or an installation of a standalone AS Java 71 system is available you
could move your central SLD also to SAP NetWeaver 71 Then you could optionally shift
your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems
Figure 8
We recommend that you use a Domain Name System (DNS) alias so that you are able to switch to
another System Landscape Directory easily For example if customers build a new landscape they
normally start with a sandbox environment Over time more and more environments are set up
Once the production environment is in place move the System Landscape Directory there To do
this you can configure a new System Landscape Directory in the production environment
synchronize it with the old System Landscape directory and switch to the new one
Topology
Apart from the considerations above the System Landscape Directory offers several topology options
with different grades of availability at the expense of low administration and operation effort There is
no generic rule therefore on how to set up a System Landscape Directory in your system landscape
To find the topology and synchronization strategy for the System Landscape Directory that fits your
requirements concerning the System Landscape Directory availability (and hence the availability of
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4556
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
Business Process Operations
Change Management
Root Cause Analysis
Implementation Upgrade
Incident Management
Test Management
Job Management
System Landscape Management
Solution Documentation Assistant
SAP Engagement and Service Delivery
SAP Solution Manager Administration
System Administration
System Monitoring
My Home is the central point of access to all important data of almost all work centers in SAP Solution
Manager
5212 Support Infrastructure
A key requirement for effective support of IT solutions is the ability to perform root cause analysis with
speed and efficiency
With SAP Solution Manager SAP has long had an infrastructure in place for its ABAP applications that
efficiently supports SAP solutions This helps ensure the high availability and smooth running of
business processes For more information see the SAP Solution Manager section
With Solution Manager Diagnostics this knowledge has been extended to Java applications If for
example homegrown Java applications cause instability Solution Manager Diagnostics helps trace the
cause to eradicate the problem rapidly Solution Manager Diagnostics is fully integrated into SAP
Solution Manager 70 Solution Manager Diagnostics also contains two third-party tools CArsquos Wily
Introscopereg for measuring performance as well as troubleshooting problems of the Java EE Engine
and applications running on it and Mercury Loadrunnerreg which enables SAP Support to produce a
defined load in the SAP solution landscape remotely For more information see Solution Manager
Diagnostics [page 43]
The support infrastructure provides SAP Support with safe access to your productive landscape for safe
root cause analysis so ensuring that SAP Support does not change your landscape inadvertently You
require a support infrastructure to run SAP NetWeaver
The following figure shows the overall infrastructure including SAP NetWeaver administration tools
that are used by administrators or operators at the customer site
5 System Landscape
52 Shared Services
3856 PUBLIC 2011-04-15
Landscape Aspects
If you use SAP NetWeaver Process Integration 71 productively besides SAP Solution Manager (as a
central support platform) you have to set up Solution Manager Diagnostics for supportability reasons
Implementation Sequence
For information about the implementation of the support infrastructure see the document Master
Guide ndash SAP Solution Manager 70 available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution Manager ltReleasegt
5213 Collection of Landscape Data
Amongst other applications and services the support infrastructure and the SAP NetWeaver
administration tools rely on system landscape data
For SAP NetWeaver PI 71 you have to run non-ABAP components in your solution landscape
Therefore the System Landscape Directory is mandatory The landscape data that is automatically
gathered by the System Landscape Directory is replicated to SAP Solution Manager There are several
topology options for the System Landscape Directory They offer different grades of availability
administration and operation effort
For more information see the System Landscape Directory section
5214 Authentication and Single Sign-On
Before implementing your system landscape plan how to implement authentication and how to
integrate different systems into a Single Sign-On landscape Single Sign-On reduces complexity for end
users saving them valuable time while also reducing administration effort for resetting passwords
thereby contributing to TCO reduction
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
5215 Integrated User and Access Management
In a system landscape containing a combination of ABAP and Java components we recommend that
you integrate your user and access management so that you can use the same user data across different
systems administer this data centrally and control access to data SAPs mature fine-grained
authorization concept allows detailed control of access rights SAP NetWeaver provides both ABAP and
Java-based user management solutions The user management solution that you use to administer
your user data depends on factors such as the type of systems that are running in your landscape
If you want to use central user administration we recommend that you run it in a non-production
system If you do not have a central user administration yet you can for example realize it in the SAP
Solution Manager system
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3956
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
522 Examples for the Overall System Landscape of Shared Services
In this section we provide examples of how shared services can be set up depending on the system
landscape they are intended for The following examples aggregate the landscape aspects given in the
Use Cases section
NOTE
The following sections and the figure mostly do not show information about the life-cycle of
shared services For example you may also need a development and testquality assurance system
for SAP Solution Manager You should consider this aspect in addition to the information given
in this section based on your requirements
Small and MediumndashSized Customer Landscapes with Java
As you use Java productively for SAP NetWeaver PI 71 besides SAP Solution Manager you have to set
up additional components for optimal monitoring administration and support Solution Manager
Diagnostics and the central mode of SAP NetWeaver Administrator are already fully integrated into
SAP Solution Manager 70 as the central operations hub For SAP Process Integration you must also
set up SAP NetWeaver Administrator with a special role
We recommend that you do not install SAP Central Process Scheduling in the SAP Solution Manager
system You have to set up and operate the system which hosts your productive scheduler as a mission
critical system
In the SAP Solution Manager system you should set up a local System Landscape Directory in addition
to a central runtime System Landscape Directory This way you have a clear separation between your
management system (SAP Solution Manager) and managed systems in your landscape In addition
SAP Solution Manager then does not rely on a System Landscape Directory running in the production
environment For this setup configure the SLD data suppliers of your SAP Solution Manager system
to send data to the central runtime System Landscape Directory In addition configure automatic
bridge forwarding from your runtime System Landscape Directory to the local System Landscape
Directory For more information see the Planning Guide - System Landscape Directory
If you want to use a central system for Adobe Document Services we recommend that you install a
dedicated system for this purpose in your production environment For detailed information about
the sizing of the system for the different use cases see the Sizing Guide for Adobe Document Services at
SAP Service Marketplace at httpservicesapcomsizing Sizing Guidelines Solutions amp
Platform
We recommend that you start with this centralized SAP Solution Manager approach as depicted in the
following figure
5 System Landscape
52 Shared Services
4056 PUBLIC 2011-04-15
Figure 7 Single SAP Solution Manager Landscape
Large Customer Landscapes with Java
Large customers who have environments in their landscape that are large and distributed administered
by different groups or separated for security reasons can consider a distributed operations setup In
addition to the centralized setup described for small- and medium-sized customers above large
customers can put parts of the central management functions on extra hosts or systems for performance
or policy reasons You have the following options for a distributed setup
You may set up an extra system or client for Central User Administration (CUA)
The Change and Transport System (CTS) can run on an extra system However it is not
performance- or data-intensive
You may set up an extra system for central CCMS monitoring Depending on the customizing
and on the landscape size central CCMS may generate a lot of system load You can connect a
separate central CCMS to SAP Solution Manager for displaying alerts in the alert inbox of the System
Monitoring work center
You can use a separate SAP NetWeaver 70 system with usage type BI together with SAP Solution
Manager This may make sense with respect to the amount of landscape management data that is
stored for reporting purposes The amount of data strongly depends on the data granularity
storage time frame and landscape size
You can easily put Wily Introscope Enterprise Manager on an separate host
Other aspects described above for small- and medium-customers (such as the setup of the System
Landscape Directory) are also valid for large customers
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4156
523 Feature Details
This section provides further information about the features described above
5231 SAP Solution Manager
SAP provides you with SAP Solution Manager as the strategic application management platform and
to enable the collaboration between you and SAP You need to install at least one productive SAP
Solution Manager in your system landscape To ensure the availability of this application management
platform an SAP Solution Manager system is technically required to install or upgrade to SAP
NetWeaver 70 or higher If you are already using SAP Solution Manager you can also use it to manage
the solution you build with SAP NetWeaver In this case we highly recommend that you update SAP
Solution Manager to the latest version
As of SAP Solution Manager 70 SP15 you can use the newly created work centers
NOTE
During the SAP system installation or upgrade process you are prompted to enter the SAP
Solution Manager key An SAP Solution Manager system is required to generate this key Without
this key the installation or upgrade process cannot continue
You may generate all needed keys for your entire system landscape (development quality
assurance and production system) in one SAP Solution Manager system In case you plan to install
several solution landscapes (for example in different countries) one SAP Solution Manager
system is still sufficient
For more information see SAP Note 805390
It is possible to install multiple SAP Solution Managers If you do so they should host separate business
solutions
If you want to reduce the risk of unavailability you should not install SAP Solution Manager as a central
component Instead you can operate a 2-system-landscape with both a test and production
environment of SAP Solution Manager (especially if you are using time-critical functions like Support
Desk) If you also develop your own content a 3-system-landscape with a development test and
production environment is recommended
For more information about SAP Solution Manager see the following table
Topic Where to Find More Information
System infrastructure scenarios installation and configuration of SAP Solution Manager
Master Guide ndash SAP Solution Manager available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution ManagerltReleasegt
Benefits and usage scenarios SAP Solution Manager ndash Learning Maps available on SAP Service Marketplace at http
5 System Landscape
52 Shared Services
4256 PUBLIC 2011-04-15
Topic Where to Find More Informationservicesapcomrkt-solman or https
servicesapcomsolutionmanager
Additional information See SAP Service Marketplace at http
servicesapcomsolutionmanager
5232 Solution Manager Diagnostics
Solution Manager Diagnostics provides efficient and safe root-cause analysis of incidents in customer
solutions powered by SAP NetWeaver It can help monitor on operating systems databases Java
application activities performance and logs It also supports the reporting of software and
configuration changes that can lead to malfunctions and errors
You must run one Solution Manager Diagnostics within your SAP solution landscape if you run
applications based on SAP NetWeaver systems with usage type AS Java Agents are responsible for
delivering the data from all productive hosts within your system landscape to the Solution Manager
Diagnostics system
CAUTION
SAP Support performs root-cause analysis on incoming incidents with Solution Manager
Diagnostics Not installing and configuring this support infrastructure results in a dramatically
reduced service level
Solution Manager Diagnostics is fully integrated into SAP Solution Manager 70
Solution Manager Diagnostics also contains Wily Introscope (Display Server and Agent part) for
measuring performance as well as to troubleshoot problems of Non-ABAP applications Wily Introscope
is heavily used for troubleshooting applications running on AS Java
SAP has signed a distribution agreement for Wily Introscope SAP customers are allowed to use this
tool in a preconfigured way
For more information about Solution Manager Diagnostics and an FAQ list see SAP Service Marketplace
at httpservicesapcomdiagnostics
5233 System Landscape Directory
The System Landscape Directory (SLD) of SAP NetWeaver is the central directory of system landscape
information relevant for the management of your software life-cycle
NOTE
Note that the abbreviation SLD is not intended to define a product since the System Landscape
Directory is part of SAP NetWeaver This abbreviation is solely intended to improve readability
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4356
The System Landscape Directory contains a description of your system landscape (that is software
components that are currently installed) and a repository of software components that can
theoretically be installed in your landscape (such as the software components available from SAP)
Since this data gets updated automatically the System Landscape Directory provides reliable and up-
to-date system landscape information with as little effort for you as possible In this way the System
Landscape Directory acts as a central information provider for SAP and third-party tools that use this
data to deliver the services you need to keep your landscape up and running
For the System Landscape Directory as part of an SAP NetWeaver PI 71 landscape consider the following
aspects
Part of SAP NetWeaver PI 71 is a new version of the System Landscape Directory It is automatically
included in every SAP NetWeaver 71 system with usage type AS Java It offers enhanced functions
such as a full automatic synchronization mechanism for all data stored in it That is both data
delivered by data suppliers and data entered or changed manually in the System Landscape
Directory can be synchronized automatically This synchronization offers the following
A fully automated mechanism so no user interaction is required and conflicts are resolved
automatically
Asynchronous propagation of information so some nodes may be down temporarily
Communication over HTTP protocol
Uni- and bi-directional synchronization
Depending on your use case the full automatic synchronization could significantly reduce manual
synchronization effort
For SAP NetWeaver PI 71 the configuration of the system landscape directory and its data suppliers
is already included in the standard implementation procedure with SAPinst For existing systems
you only have to perform some quick and easy configuration actions to start operating the system
landscape directory server in an AS Java system
For SAP NetWeaver PI 71 you have the following options concerning SLD
Option 1
Run SAP NetWeaver PI 71 against an existing SLD running on SAP NetWeaver 70 We only
recommend this for upgrades from SAP NetWeaver 70 if you have a central SLD in operation
not running on one of your PI systems
Option 2
Use the SLD included in an SAP NetWeaver PI 71 system We recommend this option for new
installations and upgrades from older releases than SAP NetWeaver 70 due to the enhanced
functions and improved performance of SLD 71
NOTE
If you already have a central SLD running on SAP NetWeaver 70 in operation you could run
two SLD versions in parallel ndash SLD running on SAP NetWeaver 71 for your PI systems and
SLD running on SAP NetWeaver 70 for all other systemsuse cases This way your SAP
5 System Landscape
52 Shared Services
4456 PUBLIC 2011-04-15
NetWeaver PI 71 systems would benefit from the new features while it would be easy to set
up and operate such an SLD landscape For this purpose you could use the new fully
automatic synchronization This feature enables the automatic forwarding of all SLD data
from an SLD running on SAP NetWeaver 70 to an SLD running on SAP NetWeaver 71 As a
result there is no need to adapt most existing systems as their SLD data suppliers could still
send their data to the central SLD In brief the following steps would be required
1 Put SLD in a PI system into operation (part of standard implementation procedure)
2 Configure PI systems to use the new SLD (part of standard implementation procedure
for new PI systems)
3 Set up the fully automatic synchronization from your old SLD to your new SLD
As soon as an upgrade or an installation of a standalone AS Java 71 system is available you
could move your central SLD also to SAP NetWeaver 71 Then you could optionally shift
your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems
Figure 8
We recommend that you use a Domain Name System (DNS) alias so that you are able to switch to
another System Landscape Directory easily For example if customers build a new landscape they
normally start with a sandbox environment Over time more and more environments are set up
Once the production environment is in place move the System Landscape Directory there To do
this you can configure a new System Landscape Directory in the production environment
synchronize it with the old System Landscape directory and switch to the new one
Topology
Apart from the considerations above the System Landscape Directory offers several topology options
with different grades of availability at the expense of low administration and operation effort There is
no generic rule therefore on how to set up a System Landscape Directory in your system landscape
To find the topology and synchronization strategy for the System Landscape Directory that fits your
requirements concerning the System Landscape Directory availability (and hence the availability of
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4556
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
Landscape Aspects
If you use SAP NetWeaver Process Integration 71 productively besides SAP Solution Manager (as a
central support platform) you have to set up Solution Manager Diagnostics for supportability reasons
Implementation Sequence
For information about the implementation of the support infrastructure see the document Master
Guide ndash SAP Solution Manager 70 available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution Manager ltReleasegt
5213 Collection of Landscape Data
Amongst other applications and services the support infrastructure and the SAP NetWeaver
administration tools rely on system landscape data
For SAP NetWeaver PI 71 you have to run non-ABAP components in your solution landscape
Therefore the System Landscape Directory is mandatory The landscape data that is automatically
gathered by the System Landscape Directory is replicated to SAP Solution Manager There are several
topology options for the System Landscape Directory They offer different grades of availability
administration and operation effort
For more information see the System Landscape Directory section
5214 Authentication and Single Sign-On
Before implementing your system landscape plan how to implement authentication and how to
integrate different systems into a Single Sign-On landscape Single Sign-On reduces complexity for end
users saving them valuable time while also reducing administration effort for resetting passwords
thereby contributing to TCO reduction
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
5215 Integrated User and Access Management
In a system landscape containing a combination of ABAP and Java components we recommend that
you integrate your user and access management so that you can use the same user data across different
systems administer this data centrally and control access to data SAPs mature fine-grained
authorization concept allows detailed control of access rights SAP NetWeaver provides both ABAP and
Java-based user management solutions The user management solution that you use to administer
your user data depends on factors such as the type of systems that are running in your landscape
If you want to use central user administration we recommend that you run it in a non-production
system If you do not have a central user administration yet you can for example realize it in the SAP
Solution Manager system
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 3956
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
522 Examples for the Overall System Landscape of Shared Services
In this section we provide examples of how shared services can be set up depending on the system
landscape they are intended for The following examples aggregate the landscape aspects given in the
Use Cases section
NOTE
The following sections and the figure mostly do not show information about the life-cycle of
shared services For example you may also need a development and testquality assurance system
for SAP Solution Manager You should consider this aspect in addition to the information given
in this section based on your requirements
Small and MediumndashSized Customer Landscapes with Java
As you use Java productively for SAP NetWeaver PI 71 besides SAP Solution Manager you have to set
up additional components for optimal monitoring administration and support Solution Manager
Diagnostics and the central mode of SAP NetWeaver Administrator are already fully integrated into
SAP Solution Manager 70 as the central operations hub For SAP Process Integration you must also
set up SAP NetWeaver Administrator with a special role
We recommend that you do not install SAP Central Process Scheduling in the SAP Solution Manager
system You have to set up and operate the system which hosts your productive scheduler as a mission
critical system
In the SAP Solution Manager system you should set up a local System Landscape Directory in addition
to a central runtime System Landscape Directory This way you have a clear separation between your
management system (SAP Solution Manager) and managed systems in your landscape In addition
SAP Solution Manager then does not rely on a System Landscape Directory running in the production
environment For this setup configure the SLD data suppliers of your SAP Solution Manager system
to send data to the central runtime System Landscape Directory In addition configure automatic
bridge forwarding from your runtime System Landscape Directory to the local System Landscape
Directory For more information see the Planning Guide - System Landscape Directory
If you want to use a central system for Adobe Document Services we recommend that you install a
dedicated system for this purpose in your production environment For detailed information about
the sizing of the system for the different use cases see the Sizing Guide for Adobe Document Services at
SAP Service Marketplace at httpservicesapcomsizing Sizing Guidelines Solutions amp
Platform
We recommend that you start with this centralized SAP Solution Manager approach as depicted in the
following figure
5 System Landscape
52 Shared Services
4056 PUBLIC 2011-04-15
Figure 7 Single SAP Solution Manager Landscape
Large Customer Landscapes with Java
Large customers who have environments in their landscape that are large and distributed administered
by different groups or separated for security reasons can consider a distributed operations setup In
addition to the centralized setup described for small- and medium-sized customers above large
customers can put parts of the central management functions on extra hosts or systems for performance
or policy reasons You have the following options for a distributed setup
You may set up an extra system or client for Central User Administration (CUA)
The Change and Transport System (CTS) can run on an extra system However it is not
performance- or data-intensive
You may set up an extra system for central CCMS monitoring Depending on the customizing
and on the landscape size central CCMS may generate a lot of system load You can connect a
separate central CCMS to SAP Solution Manager for displaying alerts in the alert inbox of the System
Monitoring work center
You can use a separate SAP NetWeaver 70 system with usage type BI together with SAP Solution
Manager This may make sense with respect to the amount of landscape management data that is
stored for reporting purposes The amount of data strongly depends on the data granularity
storage time frame and landscape size
You can easily put Wily Introscope Enterprise Manager on an separate host
Other aspects described above for small- and medium-customers (such as the setup of the System
Landscape Directory) are also valid for large customers
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4156
523 Feature Details
This section provides further information about the features described above
5231 SAP Solution Manager
SAP provides you with SAP Solution Manager as the strategic application management platform and
to enable the collaboration between you and SAP You need to install at least one productive SAP
Solution Manager in your system landscape To ensure the availability of this application management
platform an SAP Solution Manager system is technically required to install or upgrade to SAP
NetWeaver 70 or higher If you are already using SAP Solution Manager you can also use it to manage
the solution you build with SAP NetWeaver In this case we highly recommend that you update SAP
Solution Manager to the latest version
As of SAP Solution Manager 70 SP15 you can use the newly created work centers
NOTE
During the SAP system installation or upgrade process you are prompted to enter the SAP
Solution Manager key An SAP Solution Manager system is required to generate this key Without
this key the installation or upgrade process cannot continue
You may generate all needed keys for your entire system landscape (development quality
assurance and production system) in one SAP Solution Manager system In case you plan to install
several solution landscapes (for example in different countries) one SAP Solution Manager
system is still sufficient
For more information see SAP Note 805390
It is possible to install multiple SAP Solution Managers If you do so they should host separate business
solutions
If you want to reduce the risk of unavailability you should not install SAP Solution Manager as a central
component Instead you can operate a 2-system-landscape with both a test and production
environment of SAP Solution Manager (especially if you are using time-critical functions like Support
Desk) If you also develop your own content a 3-system-landscape with a development test and
production environment is recommended
For more information about SAP Solution Manager see the following table
Topic Where to Find More Information
System infrastructure scenarios installation and configuration of SAP Solution Manager
Master Guide ndash SAP Solution Manager available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution ManagerltReleasegt
Benefits and usage scenarios SAP Solution Manager ndash Learning Maps available on SAP Service Marketplace at http
5 System Landscape
52 Shared Services
4256 PUBLIC 2011-04-15
Topic Where to Find More Informationservicesapcomrkt-solman or https
servicesapcomsolutionmanager
Additional information See SAP Service Marketplace at http
servicesapcomsolutionmanager
5232 Solution Manager Diagnostics
Solution Manager Diagnostics provides efficient and safe root-cause analysis of incidents in customer
solutions powered by SAP NetWeaver It can help monitor on operating systems databases Java
application activities performance and logs It also supports the reporting of software and
configuration changes that can lead to malfunctions and errors
You must run one Solution Manager Diagnostics within your SAP solution landscape if you run
applications based on SAP NetWeaver systems with usage type AS Java Agents are responsible for
delivering the data from all productive hosts within your system landscape to the Solution Manager
Diagnostics system
CAUTION
SAP Support performs root-cause analysis on incoming incidents with Solution Manager
Diagnostics Not installing and configuring this support infrastructure results in a dramatically
reduced service level
Solution Manager Diagnostics is fully integrated into SAP Solution Manager 70
Solution Manager Diagnostics also contains Wily Introscope (Display Server and Agent part) for
measuring performance as well as to troubleshoot problems of Non-ABAP applications Wily Introscope
is heavily used for troubleshooting applications running on AS Java
SAP has signed a distribution agreement for Wily Introscope SAP customers are allowed to use this
tool in a preconfigured way
For more information about Solution Manager Diagnostics and an FAQ list see SAP Service Marketplace
at httpservicesapcomdiagnostics
5233 System Landscape Directory
The System Landscape Directory (SLD) of SAP NetWeaver is the central directory of system landscape
information relevant for the management of your software life-cycle
NOTE
Note that the abbreviation SLD is not intended to define a product since the System Landscape
Directory is part of SAP NetWeaver This abbreviation is solely intended to improve readability
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4356
The System Landscape Directory contains a description of your system landscape (that is software
components that are currently installed) and a repository of software components that can
theoretically be installed in your landscape (such as the software components available from SAP)
Since this data gets updated automatically the System Landscape Directory provides reliable and up-
to-date system landscape information with as little effort for you as possible In this way the System
Landscape Directory acts as a central information provider for SAP and third-party tools that use this
data to deliver the services you need to keep your landscape up and running
For the System Landscape Directory as part of an SAP NetWeaver PI 71 landscape consider the following
aspects
Part of SAP NetWeaver PI 71 is a new version of the System Landscape Directory It is automatically
included in every SAP NetWeaver 71 system with usage type AS Java It offers enhanced functions
such as a full automatic synchronization mechanism for all data stored in it That is both data
delivered by data suppliers and data entered or changed manually in the System Landscape
Directory can be synchronized automatically This synchronization offers the following
A fully automated mechanism so no user interaction is required and conflicts are resolved
automatically
Asynchronous propagation of information so some nodes may be down temporarily
Communication over HTTP protocol
Uni- and bi-directional synchronization
Depending on your use case the full automatic synchronization could significantly reduce manual
synchronization effort
For SAP NetWeaver PI 71 the configuration of the system landscape directory and its data suppliers
is already included in the standard implementation procedure with SAPinst For existing systems
you only have to perform some quick and easy configuration actions to start operating the system
landscape directory server in an AS Java system
For SAP NetWeaver PI 71 you have the following options concerning SLD
Option 1
Run SAP NetWeaver PI 71 against an existing SLD running on SAP NetWeaver 70 We only
recommend this for upgrades from SAP NetWeaver 70 if you have a central SLD in operation
not running on one of your PI systems
Option 2
Use the SLD included in an SAP NetWeaver PI 71 system We recommend this option for new
installations and upgrades from older releases than SAP NetWeaver 70 due to the enhanced
functions and improved performance of SLD 71
NOTE
If you already have a central SLD running on SAP NetWeaver 70 in operation you could run
two SLD versions in parallel ndash SLD running on SAP NetWeaver 71 for your PI systems and
SLD running on SAP NetWeaver 70 for all other systemsuse cases This way your SAP
5 System Landscape
52 Shared Services
4456 PUBLIC 2011-04-15
NetWeaver PI 71 systems would benefit from the new features while it would be easy to set
up and operate such an SLD landscape For this purpose you could use the new fully
automatic synchronization This feature enables the automatic forwarding of all SLD data
from an SLD running on SAP NetWeaver 70 to an SLD running on SAP NetWeaver 71 As a
result there is no need to adapt most existing systems as their SLD data suppliers could still
send their data to the central SLD In brief the following steps would be required
1 Put SLD in a PI system into operation (part of standard implementation procedure)
2 Configure PI systems to use the new SLD (part of standard implementation procedure
for new PI systems)
3 Set up the fully automatic synchronization from your old SLD to your new SLD
As soon as an upgrade or an installation of a standalone AS Java 71 system is available you
could move your central SLD also to SAP NetWeaver 71 Then you could optionally shift
your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems
Figure 8
We recommend that you use a Domain Name System (DNS) alias so that you are able to switch to
another System Landscape Directory easily For example if customers build a new landscape they
normally start with a sandbox environment Over time more and more environments are set up
Once the production environment is in place move the System Landscape Directory there To do
this you can configure a new System Landscape Directory in the production environment
synchronize it with the old System Landscape directory and switch to the new one
Topology
Apart from the considerations above the System Landscape Directory offers several topology options
with different grades of availability at the expense of low administration and operation effort There is
no generic rule therefore on how to set up a System Landscape Directory in your system landscape
To find the topology and synchronization strategy for the System Landscape Directory that fits your
requirements concerning the System Landscape Directory availability (and hence the availability of
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4556
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
For more information see the SAP Library [page 12] at Administratoracutes Guide Security Guide
522 Examples for the Overall System Landscape of Shared Services
In this section we provide examples of how shared services can be set up depending on the system
landscape they are intended for The following examples aggregate the landscape aspects given in the
Use Cases section
NOTE
The following sections and the figure mostly do not show information about the life-cycle of
shared services For example you may also need a development and testquality assurance system
for SAP Solution Manager You should consider this aspect in addition to the information given
in this section based on your requirements
Small and MediumndashSized Customer Landscapes with Java
As you use Java productively for SAP NetWeaver PI 71 besides SAP Solution Manager you have to set
up additional components for optimal monitoring administration and support Solution Manager
Diagnostics and the central mode of SAP NetWeaver Administrator are already fully integrated into
SAP Solution Manager 70 as the central operations hub For SAP Process Integration you must also
set up SAP NetWeaver Administrator with a special role
We recommend that you do not install SAP Central Process Scheduling in the SAP Solution Manager
system You have to set up and operate the system which hosts your productive scheduler as a mission
critical system
In the SAP Solution Manager system you should set up a local System Landscape Directory in addition
to a central runtime System Landscape Directory This way you have a clear separation between your
management system (SAP Solution Manager) and managed systems in your landscape In addition
SAP Solution Manager then does not rely on a System Landscape Directory running in the production
environment For this setup configure the SLD data suppliers of your SAP Solution Manager system
to send data to the central runtime System Landscape Directory In addition configure automatic
bridge forwarding from your runtime System Landscape Directory to the local System Landscape
Directory For more information see the Planning Guide - System Landscape Directory
If you want to use a central system for Adobe Document Services we recommend that you install a
dedicated system for this purpose in your production environment For detailed information about
the sizing of the system for the different use cases see the Sizing Guide for Adobe Document Services at
SAP Service Marketplace at httpservicesapcomsizing Sizing Guidelines Solutions amp
Platform
We recommend that you start with this centralized SAP Solution Manager approach as depicted in the
following figure
5 System Landscape
52 Shared Services
4056 PUBLIC 2011-04-15
Figure 7 Single SAP Solution Manager Landscape
Large Customer Landscapes with Java
Large customers who have environments in their landscape that are large and distributed administered
by different groups or separated for security reasons can consider a distributed operations setup In
addition to the centralized setup described for small- and medium-sized customers above large
customers can put parts of the central management functions on extra hosts or systems for performance
or policy reasons You have the following options for a distributed setup
You may set up an extra system or client for Central User Administration (CUA)
The Change and Transport System (CTS) can run on an extra system However it is not
performance- or data-intensive
You may set up an extra system for central CCMS monitoring Depending on the customizing
and on the landscape size central CCMS may generate a lot of system load You can connect a
separate central CCMS to SAP Solution Manager for displaying alerts in the alert inbox of the System
Monitoring work center
You can use a separate SAP NetWeaver 70 system with usage type BI together with SAP Solution
Manager This may make sense with respect to the amount of landscape management data that is
stored for reporting purposes The amount of data strongly depends on the data granularity
storage time frame and landscape size
You can easily put Wily Introscope Enterprise Manager on an separate host
Other aspects described above for small- and medium-customers (such as the setup of the System
Landscape Directory) are also valid for large customers
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4156
523 Feature Details
This section provides further information about the features described above
5231 SAP Solution Manager
SAP provides you with SAP Solution Manager as the strategic application management platform and
to enable the collaboration between you and SAP You need to install at least one productive SAP
Solution Manager in your system landscape To ensure the availability of this application management
platform an SAP Solution Manager system is technically required to install or upgrade to SAP
NetWeaver 70 or higher If you are already using SAP Solution Manager you can also use it to manage
the solution you build with SAP NetWeaver In this case we highly recommend that you update SAP
Solution Manager to the latest version
As of SAP Solution Manager 70 SP15 you can use the newly created work centers
NOTE
During the SAP system installation or upgrade process you are prompted to enter the SAP
Solution Manager key An SAP Solution Manager system is required to generate this key Without
this key the installation or upgrade process cannot continue
You may generate all needed keys for your entire system landscape (development quality
assurance and production system) in one SAP Solution Manager system In case you plan to install
several solution landscapes (for example in different countries) one SAP Solution Manager
system is still sufficient
For more information see SAP Note 805390
It is possible to install multiple SAP Solution Managers If you do so they should host separate business
solutions
If you want to reduce the risk of unavailability you should not install SAP Solution Manager as a central
component Instead you can operate a 2-system-landscape with both a test and production
environment of SAP Solution Manager (especially if you are using time-critical functions like Support
Desk) If you also develop your own content a 3-system-landscape with a development test and
production environment is recommended
For more information about SAP Solution Manager see the following table
Topic Where to Find More Information
System infrastructure scenarios installation and configuration of SAP Solution Manager
Master Guide ndash SAP Solution Manager available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution ManagerltReleasegt
Benefits and usage scenarios SAP Solution Manager ndash Learning Maps available on SAP Service Marketplace at http
5 System Landscape
52 Shared Services
4256 PUBLIC 2011-04-15
Topic Where to Find More Informationservicesapcomrkt-solman or https
servicesapcomsolutionmanager
Additional information See SAP Service Marketplace at http
servicesapcomsolutionmanager
5232 Solution Manager Diagnostics
Solution Manager Diagnostics provides efficient and safe root-cause analysis of incidents in customer
solutions powered by SAP NetWeaver It can help monitor on operating systems databases Java
application activities performance and logs It also supports the reporting of software and
configuration changes that can lead to malfunctions and errors
You must run one Solution Manager Diagnostics within your SAP solution landscape if you run
applications based on SAP NetWeaver systems with usage type AS Java Agents are responsible for
delivering the data from all productive hosts within your system landscape to the Solution Manager
Diagnostics system
CAUTION
SAP Support performs root-cause analysis on incoming incidents with Solution Manager
Diagnostics Not installing and configuring this support infrastructure results in a dramatically
reduced service level
Solution Manager Diagnostics is fully integrated into SAP Solution Manager 70
Solution Manager Diagnostics also contains Wily Introscope (Display Server and Agent part) for
measuring performance as well as to troubleshoot problems of Non-ABAP applications Wily Introscope
is heavily used for troubleshooting applications running on AS Java
SAP has signed a distribution agreement for Wily Introscope SAP customers are allowed to use this
tool in a preconfigured way
For more information about Solution Manager Diagnostics and an FAQ list see SAP Service Marketplace
at httpservicesapcomdiagnostics
5233 System Landscape Directory
The System Landscape Directory (SLD) of SAP NetWeaver is the central directory of system landscape
information relevant for the management of your software life-cycle
NOTE
Note that the abbreviation SLD is not intended to define a product since the System Landscape
Directory is part of SAP NetWeaver This abbreviation is solely intended to improve readability
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4356
The System Landscape Directory contains a description of your system landscape (that is software
components that are currently installed) and a repository of software components that can
theoretically be installed in your landscape (such as the software components available from SAP)
Since this data gets updated automatically the System Landscape Directory provides reliable and up-
to-date system landscape information with as little effort for you as possible In this way the System
Landscape Directory acts as a central information provider for SAP and third-party tools that use this
data to deliver the services you need to keep your landscape up and running
For the System Landscape Directory as part of an SAP NetWeaver PI 71 landscape consider the following
aspects
Part of SAP NetWeaver PI 71 is a new version of the System Landscape Directory It is automatically
included in every SAP NetWeaver 71 system with usage type AS Java It offers enhanced functions
such as a full automatic synchronization mechanism for all data stored in it That is both data
delivered by data suppliers and data entered or changed manually in the System Landscape
Directory can be synchronized automatically This synchronization offers the following
A fully automated mechanism so no user interaction is required and conflicts are resolved
automatically
Asynchronous propagation of information so some nodes may be down temporarily
Communication over HTTP protocol
Uni- and bi-directional synchronization
Depending on your use case the full automatic synchronization could significantly reduce manual
synchronization effort
For SAP NetWeaver PI 71 the configuration of the system landscape directory and its data suppliers
is already included in the standard implementation procedure with SAPinst For existing systems
you only have to perform some quick and easy configuration actions to start operating the system
landscape directory server in an AS Java system
For SAP NetWeaver PI 71 you have the following options concerning SLD
Option 1
Run SAP NetWeaver PI 71 against an existing SLD running on SAP NetWeaver 70 We only
recommend this for upgrades from SAP NetWeaver 70 if you have a central SLD in operation
not running on one of your PI systems
Option 2
Use the SLD included in an SAP NetWeaver PI 71 system We recommend this option for new
installations and upgrades from older releases than SAP NetWeaver 70 due to the enhanced
functions and improved performance of SLD 71
NOTE
If you already have a central SLD running on SAP NetWeaver 70 in operation you could run
two SLD versions in parallel ndash SLD running on SAP NetWeaver 71 for your PI systems and
SLD running on SAP NetWeaver 70 for all other systemsuse cases This way your SAP
5 System Landscape
52 Shared Services
4456 PUBLIC 2011-04-15
NetWeaver PI 71 systems would benefit from the new features while it would be easy to set
up and operate such an SLD landscape For this purpose you could use the new fully
automatic synchronization This feature enables the automatic forwarding of all SLD data
from an SLD running on SAP NetWeaver 70 to an SLD running on SAP NetWeaver 71 As a
result there is no need to adapt most existing systems as their SLD data suppliers could still
send their data to the central SLD In brief the following steps would be required
1 Put SLD in a PI system into operation (part of standard implementation procedure)
2 Configure PI systems to use the new SLD (part of standard implementation procedure
for new PI systems)
3 Set up the fully automatic synchronization from your old SLD to your new SLD
As soon as an upgrade or an installation of a standalone AS Java 71 system is available you
could move your central SLD also to SAP NetWeaver 71 Then you could optionally shift
your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems
Figure 8
We recommend that you use a Domain Name System (DNS) alias so that you are able to switch to
another System Landscape Directory easily For example if customers build a new landscape they
normally start with a sandbox environment Over time more and more environments are set up
Once the production environment is in place move the System Landscape Directory there To do
this you can configure a new System Landscape Directory in the production environment
synchronize it with the old System Landscape directory and switch to the new one
Topology
Apart from the considerations above the System Landscape Directory offers several topology options
with different grades of availability at the expense of low administration and operation effort There is
no generic rule therefore on how to set up a System Landscape Directory in your system landscape
To find the topology and synchronization strategy for the System Landscape Directory that fits your
requirements concerning the System Landscape Directory availability (and hence the availability of
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4556
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
Figure 7 Single SAP Solution Manager Landscape
Large Customer Landscapes with Java
Large customers who have environments in their landscape that are large and distributed administered
by different groups or separated for security reasons can consider a distributed operations setup In
addition to the centralized setup described for small- and medium-sized customers above large
customers can put parts of the central management functions on extra hosts or systems for performance
or policy reasons You have the following options for a distributed setup
You may set up an extra system or client for Central User Administration (CUA)
The Change and Transport System (CTS) can run on an extra system However it is not
performance- or data-intensive
You may set up an extra system for central CCMS monitoring Depending on the customizing
and on the landscape size central CCMS may generate a lot of system load You can connect a
separate central CCMS to SAP Solution Manager for displaying alerts in the alert inbox of the System
Monitoring work center
You can use a separate SAP NetWeaver 70 system with usage type BI together with SAP Solution
Manager This may make sense with respect to the amount of landscape management data that is
stored for reporting purposes The amount of data strongly depends on the data granularity
storage time frame and landscape size
You can easily put Wily Introscope Enterprise Manager on an separate host
Other aspects described above for small- and medium-customers (such as the setup of the System
Landscape Directory) are also valid for large customers
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4156
523 Feature Details
This section provides further information about the features described above
5231 SAP Solution Manager
SAP provides you with SAP Solution Manager as the strategic application management platform and
to enable the collaboration between you and SAP You need to install at least one productive SAP
Solution Manager in your system landscape To ensure the availability of this application management
platform an SAP Solution Manager system is technically required to install or upgrade to SAP
NetWeaver 70 or higher If you are already using SAP Solution Manager you can also use it to manage
the solution you build with SAP NetWeaver In this case we highly recommend that you update SAP
Solution Manager to the latest version
As of SAP Solution Manager 70 SP15 you can use the newly created work centers
NOTE
During the SAP system installation or upgrade process you are prompted to enter the SAP
Solution Manager key An SAP Solution Manager system is required to generate this key Without
this key the installation or upgrade process cannot continue
You may generate all needed keys for your entire system landscape (development quality
assurance and production system) in one SAP Solution Manager system In case you plan to install
several solution landscapes (for example in different countries) one SAP Solution Manager
system is still sufficient
For more information see SAP Note 805390
It is possible to install multiple SAP Solution Managers If you do so they should host separate business
solutions
If you want to reduce the risk of unavailability you should not install SAP Solution Manager as a central
component Instead you can operate a 2-system-landscape with both a test and production
environment of SAP Solution Manager (especially if you are using time-critical functions like Support
Desk) If you also develop your own content a 3-system-landscape with a development test and
production environment is recommended
For more information about SAP Solution Manager see the following table
Topic Where to Find More Information
System infrastructure scenarios installation and configuration of SAP Solution Manager
Master Guide ndash SAP Solution Manager available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution ManagerltReleasegt
Benefits and usage scenarios SAP Solution Manager ndash Learning Maps available on SAP Service Marketplace at http
5 System Landscape
52 Shared Services
4256 PUBLIC 2011-04-15
Topic Where to Find More Informationservicesapcomrkt-solman or https
servicesapcomsolutionmanager
Additional information See SAP Service Marketplace at http
servicesapcomsolutionmanager
5232 Solution Manager Diagnostics
Solution Manager Diagnostics provides efficient and safe root-cause analysis of incidents in customer
solutions powered by SAP NetWeaver It can help monitor on operating systems databases Java
application activities performance and logs It also supports the reporting of software and
configuration changes that can lead to malfunctions and errors
You must run one Solution Manager Diagnostics within your SAP solution landscape if you run
applications based on SAP NetWeaver systems with usage type AS Java Agents are responsible for
delivering the data from all productive hosts within your system landscape to the Solution Manager
Diagnostics system
CAUTION
SAP Support performs root-cause analysis on incoming incidents with Solution Manager
Diagnostics Not installing and configuring this support infrastructure results in a dramatically
reduced service level
Solution Manager Diagnostics is fully integrated into SAP Solution Manager 70
Solution Manager Diagnostics also contains Wily Introscope (Display Server and Agent part) for
measuring performance as well as to troubleshoot problems of Non-ABAP applications Wily Introscope
is heavily used for troubleshooting applications running on AS Java
SAP has signed a distribution agreement for Wily Introscope SAP customers are allowed to use this
tool in a preconfigured way
For more information about Solution Manager Diagnostics and an FAQ list see SAP Service Marketplace
at httpservicesapcomdiagnostics
5233 System Landscape Directory
The System Landscape Directory (SLD) of SAP NetWeaver is the central directory of system landscape
information relevant for the management of your software life-cycle
NOTE
Note that the abbreviation SLD is not intended to define a product since the System Landscape
Directory is part of SAP NetWeaver This abbreviation is solely intended to improve readability
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4356
The System Landscape Directory contains a description of your system landscape (that is software
components that are currently installed) and a repository of software components that can
theoretically be installed in your landscape (such as the software components available from SAP)
Since this data gets updated automatically the System Landscape Directory provides reliable and up-
to-date system landscape information with as little effort for you as possible In this way the System
Landscape Directory acts as a central information provider for SAP and third-party tools that use this
data to deliver the services you need to keep your landscape up and running
For the System Landscape Directory as part of an SAP NetWeaver PI 71 landscape consider the following
aspects
Part of SAP NetWeaver PI 71 is a new version of the System Landscape Directory It is automatically
included in every SAP NetWeaver 71 system with usage type AS Java It offers enhanced functions
such as a full automatic synchronization mechanism for all data stored in it That is both data
delivered by data suppliers and data entered or changed manually in the System Landscape
Directory can be synchronized automatically This synchronization offers the following
A fully automated mechanism so no user interaction is required and conflicts are resolved
automatically
Asynchronous propagation of information so some nodes may be down temporarily
Communication over HTTP protocol
Uni- and bi-directional synchronization
Depending on your use case the full automatic synchronization could significantly reduce manual
synchronization effort
For SAP NetWeaver PI 71 the configuration of the system landscape directory and its data suppliers
is already included in the standard implementation procedure with SAPinst For existing systems
you only have to perform some quick and easy configuration actions to start operating the system
landscape directory server in an AS Java system
For SAP NetWeaver PI 71 you have the following options concerning SLD
Option 1
Run SAP NetWeaver PI 71 against an existing SLD running on SAP NetWeaver 70 We only
recommend this for upgrades from SAP NetWeaver 70 if you have a central SLD in operation
not running on one of your PI systems
Option 2
Use the SLD included in an SAP NetWeaver PI 71 system We recommend this option for new
installations and upgrades from older releases than SAP NetWeaver 70 due to the enhanced
functions and improved performance of SLD 71
NOTE
If you already have a central SLD running on SAP NetWeaver 70 in operation you could run
two SLD versions in parallel ndash SLD running on SAP NetWeaver 71 for your PI systems and
SLD running on SAP NetWeaver 70 for all other systemsuse cases This way your SAP
5 System Landscape
52 Shared Services
4456 PUBLIC 2011-04-15
NetWeaver PI 71 systems would benefit from the new features while it would be easy to set
up and operate such an SLD landscape For this purpose you could use the new fully
automatic synchronization This feature enables the automatic forwarding of all SLD data
from an SLD running on SAP NetWeaver 70 to an SLD running on SAP NetWeaver 71 As a
result there is no need to adapt most existing systems as their SLD data suppliers could still
send their data to the central SLD In brief the following steps would be required
1 Put SLD in a PI system into operation (part of standard implementation procedure)
2 Configure PI systems to use the new SLD (part of standard implementation procedure
for new PI systems)
3 Set up the fully automatic synchronization from your old SLD to your new SLD
As soon as an upgrade or an installation of a standalone AS Java 71 system is available you
could move your central SLD also to SAP NetWeaver 71 Then you could optionally shift
your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems
Figure 8
We recommend that you use a Domain Name System (DNS) alias so that you are able to switch to
another System Landscape Directory easily For example if customers build a new landscape they
normally start with a sandbox environment Over time more and more environments are set up
Once the production environment is in place move the System Landscape Directory there To do
this you can configure a new System Landscape Directory in the production environment
synchronize it with the old System Landscape directory and switch to the new one
Topology
Apart from the considerations above the System Landscape Directory offers several topology options
with different grades of availability at the expense of low administration and operation effort There is
no generic rule therefore on how to set up a System Landscape Directory in your system landscape
To find the topology and synchronization strategy for the System Landscape Directory that fits your
requirements concerning the System Landscape Directory availability (and hence the availability of
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4556
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
523 Feature Details
This section provides further information about the features described above
5231 SAP Solution Manager
SAP provides you with SAP Solution Manager as the strategic application management platform and
to enable the collaboration between you and SAP You need to install at least one productive SAP
Solution Manager in your system landscape To ensure the availability of this application management
platform an SAP Solution Manager system is technically required to install or upgrade to SAP
NetWeaver 70 or higher If you are already using SAP Solution Manager you can also use it to manage
the solution you build with SAP NetWeaver In this case we highly recommend that you update SAP
Solution Manager to the latest version
As of SAP Solution Manager 70 SP15 you can use the newly created work centers
NOTE
During the SAP system installation or upgrade process you are prompted to enter the SAP
Solution Manager key An SAP Solution Manager system is required to generate this key Without
this key the installation or upgrade process cannot continue
You may generate all needed keys for your entire system landscape (development quality
assurance and production system) in one SAP Solution Manager system In case you plan to install
several solution landscapes (for example in different countries) one SAP Solution Manager
system is still sufficient
For more information see SAP Note 805390
It is possible to install multiple SAP Solution Managers If you do so they should host separate business
solutions
If you want to reduce the risk of unavailability you should not install SAP Solution Manager as a central
component Instead you can operate a 2-system-landscape with both a test and production
environment of SAP Solution Manager (especially if you are using time-critical functions like Support
Desk) If you also develop your own content a 3-system-landscape with a development test and
production environment is recommended
For more information about SAP Solution Manager see the following table
Topic Where to Find More Information
System infrastructure scenarios installation and configuration of SAP Solution Manager
Master Guide ndash SAP Solution Manager available on SAP Service Marketplace at httpservicesapcom
instguides SAP Components SAP Solution ManagerltReleasegt
Benefits and usage scenarios SAP Solution Manager ndash Learning Maps available on SAP Service Marketplace at http
5 System Landscape
52 Shared Services
4256 PUBLIC 2011-04-15
Topic Where to Find More Informationservicesapcomrkt-solman or https
servicesapcomsolutionmanager
Additional information See SAP Service Marketplace at http
servicesapcomsolutionmanager
5232 Solution Manager Diagnostics
Solution Manager Diagnostics provides efficient and safe root-cause analysis of incidents in customer
solutions powered by SAP NetWeaver It can help monitor on operating systems databases Java
application activities performance and logs It also supports the reporting of software and
configuration changes that can lead to malfunctions and errors
You must run one Solution Manager Diagnostics within your SAP solution landscape if you run
applications based on SAP NetWeaver systems with usage type AS Java Agents are responsible for
delivering the data from all productive hosts within your system landscape to the Solution Manager
Diagnostics system
CAUTION
SAP Support performs root-cause analysis on incoming incidents with Solution Manager
Diagnostics Not installing and configuring this support infrastructure results in a dramatically
reduced service level
Solution Manager Diagnostics is fully integrated into SAP Solution Manager 70
Solution Manager Diagnostics also contains Wily Introscope (Display Server and Agent part) for
measuring performance as well as to troubleshoot problems of Non-ABAP applications Wily Introscope
is heavily used for troubleshooting applications running on AS Java
SAP has signed a distribution agreement for Wily Introscope SAP customers are allowed to use this
tool in a preconfigured way
For more information about Solution Manager Diagnostics and an FAQ list see SAP Service Marketplace
at httpservicesapcomdiagnostics
5233 System Landscape Directory
The System Landscape Directory (SLD) of SAP NetWeaver is the central directory of system landscape
information relevant for the management of your software life-cycle
NOTE
Note that the abbreviation SLD is not intended to define a product since the System Landscape
Directory is part of SAP NetWeaver This abbreviation is solely intended to improve readability
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4356
The System Landscape Directory contains a description of your system landscape (that is software
components that are currently installed) and a repository of software components that can
theoretically be installed in your landscape (such as the software components available from SAP)
Since this data gets updated automatically the System Landscape Directory provides reliable and up-
to-date system landscape information with as little effort for you as possible In this way the System
Landscape Directory acts as a central information provider for SAP and third-party tools that use this
data to deliver the services you need to keep your landscape up and running
For the System Landscape Directory as part of an SAP NetWeaver PI 71 landscape consider the following
aspects
Part of SAP NetWeaver PI 71 is a new version of the System Landscape Directory It is automatically
included in every SAP NetWeaver 71 system with usage type AS Java It offers enhanced functions
such as a full automatic synchronization mechanism for all data stored in it That is both data
delivered by data suppliers and data entered or changed manually in the System Landscape
Directory can be synchronized automatically This synchronization offers the following
A fully automated mechanism so no user interaction is required and conflicts are resolved
automatically
Asynchronous propagation of information so some nodes may be down temporarily
Communication over HTTP protocol
Uni- and bi-directional synchronization
Depending on your use case the full automatic synchronization could significantly reduce manual
synchronization effort
For SAP NetWeaver PI 71 the configuration of the system landscape directory and its data suppliers
is already included in the standard implementation procedure with SAPinst For existing systems
you only have to perform some quick and easy configuration actions to start operating the system
landscape directory server in an AS Java system
For SAP NetWeaver PI 71 you have the following options concerning SLD
Option 1
Run SAP NetWeaver PI 71 against an existing SLD running on SAP NetWeaver 70 We only
recommend this for upgrades from SAP NetWeaver 70 if you have a central SLD in operation
not running on one of your PI systems
Option 2
Use the SLD included in an SAP NetWeaver PI 71 system We recommend this option for new
installations and upgrades from older releases than SAP NetWeaver 70 due to the enhanced
functions and improved performance of SLD 71
NOTE
If you already have a central SLD running on SAP NetWeaver 70 in operation you could run
two SLD versions in parallel ndash SLD running on SAP NetWeaver 71 for your PI systems and
SLD running on SAP NetWeaver 70 for all other systemsuse cases This way your SAP
5 System Landscape
52 Shared Services
4456 PUBLIC 2011-04-15
NetWeaver PI 71 systems would benefit from the new features while it would be easy to set
up and operate such an SLD landscape For this purpose you could use the new fully
automatic synchronization This feature enables the automatic forwarding of all SLD data
from an SLD running on SAP NetWeaver 70 to an SLD running on SAP NetWeaver 71 As a
result there is no need to adapt most existing systems as their SLD data suppliers could still
send their data to the central SLD In brief the following steps would be required
1 Put SLD in a PI system into operation (part of standard implementation procedure)
2 Configure PI systems to use the new SLD (part of standard implementation procedure
for new PI systems)
3 Set up the fully automatic synchronization from your old SLD to your new SLD
As soon as an upgrade or an installation of a standalone AS Java 71 system is available you
could move your central SLD also to SAP NetWeaver 71 Then you could optionally shift
your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems
Figure 8
We recommend that you use a Domain Name System (DNS) alias so that you are able to switch to
another System Landscape Directory easily For example if customers build a new landscape they
normally start with a sandbox environment Over time more and more environments are set up
Once the production environment is in place move the System Landscape Directory there To do
this you can configure a new System Landscape Directory in the production environment
synchronize it with the old System Landscape directory and switch to the new one
Topology
Apart from the considerations above the System Landscape Directory offers several topology options
with different grades of availability at the expense of low administration and operation effort There is
no generic rule therefore on how to set up a System Landscape Directory in your system landscape
To find the topology and synchronization strategy for the System Landscape Directory that fits your
requirements concerning the System Landscape Directory availability (and hence the availability of
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4556
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
Topic Where to Find More Informationservicesapcomrkt-solman or https
servicesapcomsolutionmanager
Additional information See SAP Service Marketplace at http
servicesapcomsolutionmanager
5232 Solution Manager Diagnostics
Solution Manager Diagnostics provides efficient and safe root-cause analysis of incidents in customer
solutions powered by SAP NetWeaver It can help monitor on operating systems databases Java
application activities performance and logs It also supports the reporting of software and
configuration changes that can lead to malfunctions and errors
You must run one Solution Manager Diagnostics within your SAP solution landscape if you run
applications based on SAP NetWeaver systems with usage type AS Java Agents are responsible for
delivering the data from all productive hosts within your system landscape to the Solution Manager
Diagnostics system
CAUTION
SAP Support performs root-cause analysis on incoming incidents with Solution Manager
Diagnostics Not installing and configuring this support infrastructure results in a dramatically
reduced service level
Solution Manager Diagnostics is fully integrated into SAP Solution Manager 70
Solution Manager Diagnostics also contains Wily Introscope (Display Server and Agent part) for
measuring performance as well as to troubleshoot problems of Non-ABAP applications Wily Introscope
is heavily used for troubleshooting applications running on AS Java
SAP has signed a distribution agreement for Wily Introscope SAP customers are allowed to use this
tool in a preconfigured way
For more information about Solution Manager Diagnostics and an FAQ list see SAP Service Marketplace
at httpservicesapcomdiagnostics
5233 System Landscape Directory
The System Landscape Directory (SLD) of SAP NetWeaver is the central directory of system landscape
information relevant for the management of your software life-cycle
NOTE
Note that the abbreviation SLD is not intended to define a product since the System Landscape
Directory is part of SAP NetWeaver This abbreviation is solely intended to improve readability
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4356
The System Landscape Directory contains a description of your system landscape (that is software
components that are currently installed) and a repository of software components that can
theoretically be installed in your landscape (such as the software components available from SAP)
Since this data gets updated automatically the System Landscape Directory provides reliable and up-
to-date system landscape information with as little effort for you as possible In this way the System
Landscape Directory acts as a central information provider for SAP and third-party tools that use this
data to deliver the services you need to keep your landscape up and running
For the System Landscape Directory as part of an SAP NetWeaver PI 71 landscape consider the following
aspects
Part of SAP NetWeaver PI 71 is a new version of the System Landscape Directory It is automatically
included in every SAP NetWeaver 71 system with usage type AS Java It offers enhanced functions
such as a full automatic synchronization mechanism for all data stored in it That is both data
delivered by data suppliers and data entered or changed manually in the System Landscape
Directory can be synchronized automatically This synchronization offers the following
A fully automated mechanism so no user interaction is required and conflicts are resolved
automatically
Asynchronous propagation of information so some nodes may be down temporarily
Communication over HTTP protocol
Uni- and bi-directional synchronization
Depending on your use case the full automatic synchronization could significantly reduce manual
synchronization effort
For SAP NetWeaver PI 71 the configuration of the system landscape directory and its data suppliers
is already included in the standard implementation procedure with SAPinst For existing systems
you only have to perform some quick and easy configuration actions to start operating the system
landscape directory server in an AS Java system
For SAP NetWeaver PI 71 you have the following options concerning SLD
Option 1
Run SAP NetWeaver PI 71 against an existing SLD running on SAP NetWeaver 70 We only
recommend this for upgrades from SAP NetWeaver 70 if you have a central SLD in operation
not running on one of your PI systems
Option 2
Use the SLD included in an SAP NetWeaver PI 71 system We recommend this option for new
installations and upgrades from older releases than SAP NetWeaver 70 due to the enhanced
functions and improved performance of SLD 71
NOTE
If you already have a central SLD running on SAP NetWeaver 70 in operation you could run
two SLD versions in parallel ndash SLD running on SAP NetWeaver 71 for your PI systems and
SLD running on SAP NetWeaver 70 for all other systemsuse cases This way your SAP
5 System Landscape
52 Shared Services
4456 PUBLIC 2011-04-15
NetWeaver PI 71 systems would benefit from the new features while it would be easy to set
up and operate such an SLD landscape For this purpose you could use the new fully
automatic synchronization This feature enables the automatic forwarding of all SLD data
from an SLD running on SAP NetWeaver 70 to an SLD running on SAP NetWeaver 71 As a
result there is no need to adapt most existing systems as their SLD data suppliers could still
send their data to the central SLD In brief the following steps would be required
1 Put SLD in a PI system into operation (part of standard implementation procedure)
2 Configure PI systems to use the new SLD (part of standard implementation procedure
for new PI systems)
3 Set up the fully automatic synchronization from your old SLD to your new SLD
As soon as an upgrade or an installation of a standalone AS Java 71 system is available you
could move your central SLD also to SAP NetWeaver 71 Then you could optionally shift
your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems
Figure 8
We recommend that you use a Domain Name System (DNS) alias so that you are able to switch to
another System Landscape Directory easily For example if customers build a new landscape they
normally start with a sandbox environment Over time more and more environments are set up
Once the production environment is in place move the System Landscape Directory there To do
this you can configure a new System Landscape Directory in the production environment
synchronize it with the old System Landscape directory and switch to the new one
Topology
Apart from the considerations above the System Landscape Directory offers several topology options
with different grades of availability at the expense of low administration and operation effort There is
no generic rule therefore on how to set up a System Landscape Directory in your system landscape
To find the topology and synchronization strategy for the System Landscape Directory that fits your
requirements concerning the System Landscape Directory availability (and hence the availability of
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4556
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
The System Landscape Directory contains a description of your system landscape (that is software
components that are currently installed) and a repository of software components that can
theoretically be installed in your landscape (such as the software components available from SAP)
Since this data gets updated automatically the System Landscape Directory provides reliable and up-
to-date system landscape information with as little effort for you as possible In this way the System
Landscape Directory acts as a central information provider for SAP and third-party tools that use this
data to deliver the services you need to keep your landscape up and running
For the System Landscape Directory as part of an SAP NetWeaver PI 71 landscape consider the following
aspects
Part of SAP NetWeaver PI 71 is a new version of the System Landscape Directory It is automatically
included in every SAP NetWeaver 71 system with usage type AS Java It offers enhanced functions
such as a full automatic synchronization mechanism for all data stored in it That is both data
delivered by data suppliers and data entered or changed manually in the System Landscape
Directory can be synchronized automatically This synchronization offers the following
A fully automated mechanism so no user interaction is required and conflicts are resolved
automatically
Asynchronous propagation of information so some nodes may be down temporarily
Communication over HTTP protocol
Uni- and bi-directional synchronization
Depending on your use case the full automatic synchronization could significantly reduce manual
synchronization effort
For SAP NetWeaver PI 71 the configuration of the system landscape directory and its data suppliers
is already included in the standard implementation procedure with SAPinst For existing systems
you only have to perform some quick and easy configuration actions to start operating the system
landscape directory server in an AS Java system
For SAP NetWeaver PI 71 you have the following options concerning SLD
Option 1
Run SAP NetWeaver PI 71 against an existing SLD running on SAP NetWeaver 70 We only
recommend this for upgrades from SAP NetWeaver 70 if you have a central SLD in operation
not running on one of your PI systems
Option 2
Use the SLD included in an SAP NetWeaver PI 71 system We recommend this option for new
installations and upgrades from older releases than SAP NetWeaver 70 due to the enhanced
functions and improved performance of SLD 71
NOTE
If you already have a central SLD running on SAP NetWeaver 70 in operation you could run
two SLD versions in parallel ndash SLD running on SAP NetWeaver 71 for your PI systems and
SLD running on SAP NetWeaver 70 for all other systemsuse cases This way your SAP
5 System Landscape
52 Shared Services
4456 PUBLIC 2011-04-15
NetWeaver PI 71 systems would benefit from the new features while it would be easy to set
up and operate such an SLD landscape For this purpose you could use the new fully
automatic synchronization This feature enables the automatic forwarding of all SLD data
from an SLD running on SAP NetWeaver 70 to an SLD running on SAP NetWeaver 71 As a
result there is no need to adapt most existing systems as their SLD data suppliers could still
send their data to the central SLD In brief the following steps would be required
1 Put SLD in a PI system into operation (part of standard implementation procedure)
2 Configure PI systems to use the new SLD (part of standard implementation procedure
for new PI systems)
3 Set up the fully automatic synchronization from your old SLD to your new SLD
As soon as an upgrade or an installation of a standalone AS Java 71 system is available you
could move your central SLD also to SAP NetWeaver 71 Then you could optionally shift
your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems
Figure 8
We recommend that you use a Domain Name System (DNS) alias so that you are able to switch to
another System Landscape Directory easily For example if customers build a new landscape they
normally start with a sandbox environment Over time more and more environments are set up
Once the production environment is in place move the System Landscape Directory there To do
this you can configure a new System Landscape Directory in the production environment
synchronize it with the old System Landscape directory and switch to the new one
Topology
Apart from the considerations above the System Landscape Directory offers several topology options
with different grades of availability at the expense of low administration and operation effort There is
no generic rule therefore on how to set up a System Landscape Directory in your system landscape
To find the topology and synchronization strategy for the System Landscape Directory that fits your
requirements concerning the System Landscape Directory availability (and hence the availability of
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4556
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
NetWeaver PI 71 systems would benefit from the new features while it would be easy to set
up and operate such an SLD landscape For this purpose you could use the new fully
automatic synchronization This feature enables the automatic forwarding of all SLD data
from an SLD running on SAP NetWeaver 70 to an SLD running on SAP NetWeaver 71 As a
result there is no need to adapt most existing systems as their SLD data suppliers could still
send their data to the central SLD In brief the following steps would be required
1 Put SLD in a PI system into operation (part of standard implementation procedure)
2 Configure PI systems to use the new SLD (part of standard implementation procedure
for new PI systems)
3 Set up the fully automatic synchronization from your old SLD to your new SLD
As soon as an upgrade or an installation of a standalone AS Java 71 system is available you
could move your central SLD also to SAP NetWeaver 71 Then you could optionally shift
your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems
Figure 8
We recommend that you use a Domain Name System (DNS) alias so that you are able to switch to
another System Landscape Directory easily For example if customers build a new landscape they
normally start with a sandbox environment Over time more and more environments are set up
Once the production environment is in place move the System Landscape Directory there To do
this you can configure a new System Landscape Directory in the production environment
synchronize it with the old System Landscape directory and switch to the new one
Topology
Apart from the considerations above the System Landscape Directory offers several topology options
with different grades of availability at the expense of low administration and operation effort There is
no generic rule therefore on how to set up a System Landscape Directory in your system landscape
To find the topology and synchronization strategy for the System Landscape Directory that fits your
requirements concerning the System Landscape Directory availability (and hence the availability of
5 System Landscape
52 Shared Services
2011-04-15 PUBLIC 4556
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
the applications that rely on it) see the documentation Planning Guide ndash System Landscape Directory available
in SAP Developers Network at httpsdnsapcomirjsdnnw-sld
Implementation Sequence
Perform the following steps
NoAction[Corresponding Documentation] Remarks and Subsequent Steps
1 During the installation of the PI 71 system perform the corresponding automatic configuration steps for the SLD offered by the installation procedure[Installation Guide ndash SAP Netweaver Process Integration 71 on ltOperating Systemgt ltDatabasegt]
If you want to configure the SLD in an existing AS Java system see the User Guide ndash System Landscape Directory
For the data exchange between the data suppliers of ABAP-based systems and the system landscape directory a gateway process is required since the data is exchanged using RFC As of SAP NetWeaver 71 AS Java comprises such a gateway process which is configured automatically to be used by the system landscape directory Therefore you no longer require to install a separate gateway
2 Download and install the most current system landscape directory content - updated monthly - available on SAP Service Marketplace[SAP Note 669669]
5 System Landscape
52 Shared Services
4656 PUBLIC 2011-04-15
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
A Appendix
A1 Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape
Therefore it is crucial that this data is correctly maintained in SAP Solution Managerrsquos system landscape
(transaction SMSY) If you have already maintained the system landscape data check carefully if this
data is correct
Proceed in the following order
1 If you have not already done so capture the system data using the System Landscape Directory
(SLD)
2 Optional Run the landscape verification 10 to check the system landscape data
3 Maintain the system data in SAP Solution Manager
Procedure
Capturing System Data Using SLD
1 Register all systems that you want to update in your central SLD In case of a dual stack system
you have to register both the ABAP stack and the Java stack
Depending on your applications this can either be the SLD of your SAP Solution Manager system
(if there are no dependencies of productive runtime systems) or you have separate SLD systems
for productive and non-productive use (default recommendation)
If you use a central runtime SLD distribute the data of all technical systems that are registered in
the central SLD from the central SLD to the development SLDs and to the local SLD in SAP Solution
Manager
For more information about the SLD topology options and synchronization see the Planning Guide
ndash System Landscape Directory available at httpsdnsapcomirjsdnnw-sld
To register Java systems you use the Visual Administrator To register the ABAP system you use
transaction RZ70
For more information see SAP Library at httphelpsapcom SAP NetWeaver SAP
NetWeaver Process Integration SAP NetWeaver Process Integration Library ltLanguagegt SAP NetWeaver Process
Integration Library Function-Oriented View Application Server Infrastructure Configuring Working with and
Administering System Landscape Directory Configuring Systems to Connect to the SLD
If the registration was successful both the ABAP system and the Java system appear in the SLD
under Technical Systems
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4756
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
2 To transfer the data from the SLD to the SAP Solution Manager system landscape schedule SLD
update jobs in the SAP Solution Manager transaction SMSY_SETUP
For more information see the SAP Solution Manager Library at httphelpsapcom SAP
Solution Manager 70 ltLanguagegt Basic Settings Solution Manager System Landscape Set Up Automatic Data
Capture for System Landscape
Figure 9 Capturing System Data Using SLD
Running the Landscape Verification 10
Running the landscape verification 10 is an optional step This tool checks how your systems are
maintained in the SAP Solution Manager system If it detects any inconsistencies you are prompted to
correct existing entries or enter missing data The tool provides you with information how to maintain
the data
As of SP01 for landscape verification 10 for SAP Solution Manager two additional wizards are available
which enable you to correct the detected problems directly These wizards enable you to correct the
description of technical systems and product systems in which problems were detected The wizards
also include help for making the correct settings
To start the landscape verification call transaction LVSM in SAP Solution Manager
For more information about the landscape verification choose the Help link from within the
application
A Appendix
A1 Maintaining System Landscape Information
4856 PUBLIC 2011-04-15
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
Figure 10 Landscape Verification 10
Maintaining System Data
When your product systems are known in SAP Solution Manager you have to check and maintain the
system data add your system to a logical component and to a solution
1 In transaction SMSY choose Landscape Components Product System ltSystemgt
2 Check whether the product version is correct The product version is displayed in the right pane
below the name of your system
3 Choose the Selection of Product Instances tab and check that everything that is installed in your system
is flagged as Relevant Make sure that no instance is marked as relevant that is not installed in your
system as this would lead to the installation of unwanted software components in your system
NOTE
You can only select one ABAP instance as relevant You have to flag further ABAP instances
as Also Installed in Relevant ABAP Product Instance
For more information about selecting the instances and required settings see SAP Note 1344564 -
Maintenance Optimizer Check system landscape and SAP Note 1429764 -Automatic assignment of products in
SMSY
4 Creating the logical component
1 In transaction SMSY choose System Groups and Logical Components
2 In the context menu of Logical Components choose Create New Logical Component
3 Enter your system data
The name of your logical component must start with ldquoZrdquo
5 Assigning the system to the logical component
In the Current System Assignments of the newly created logical component add your systems with the
appropriate roles (such as Development System or Production System)
A Appendix
A1 Maintaining System Landscape Information
2011-04-15 PUBLIC 4956
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
RECOMMENDATION
We recommend adding all systems of one product to one logical component This means
that you create one logical component and add the development system the quality
assurance system and the production system to the same logical component
6 Optional Adding the product system to a solution
It is no longer mandatory to create a solution and to add your product system to a solution
However if you already have a solution then add your product system to it When you later create
a maintenance transaction you can select this solution and thus restrict the number of product
systems displayed
1 Call transaction solution_manager and create a solution if it does not yet exist
2 Choose Solution Landscape and Solution Landscape Maintenance
3 Add your SAP system to the solution as follows
1 Change to edit mode
2 Place the cursor on a new line in the Logical Component column
3 Use the input help to select your system from the list (product logical component)
4 Choose Complete System Data Replication
5 Save your selection
A Appendix
A1 Maintaining System Landscape Information
5056 PUBLIC 2011-04-15
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
B Reference
B1 The Main SAP Documentation Types
The following is an overview of the most important documentation types that you need in the various
phases in the life cycle of SAP software
Cross-Phase Documentation
SAPterm is SAPrsquos terminology database It contains SAP-specific vocabulary in over 30 languages as
well as many glossary entries in English and German
Target group
Relevant for all target groups
Current version
On SAP Help Portal at httphelpsapcom Glossary
In the SAP system in transaction STERM
SAP Library is a collection of documentation for SAP software covering functions and processes
Target group
Consultants
System administrators
Project teams for implementations or upgrades
Current version
On SAP Help Portal at httphelpsapcom (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for raising
security levels A collective security guide is available for SAP NetWeaver This document contains
general guidelines and suggestions SAP applications have a security guide of their own
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcomsecurityguide
Implementation
The master guide is the starting point for implementing an SAP solution It lists the required installable
units for each business or IT scenario It provides scenario-specific descriptions of preparation
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5156
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
execution and follow-up of an implementation It also provides references to other documents such
as installation guides the technical infrastructure guide and SAP Notes
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The installation guide describes the technical implementation of an installable unit taking into
account the combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for implementations
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Configuration Documentation in SAP Solution Manager ndash SAP Solution Manager is a life-cycle
platform One of its main functions is the configuration of business scenarios business processes and
implementable steps It contains Customizing activities transactions and so on as well as
documentation
Target group
Technology consultants
Solution consultants
Project teams for implementations
Current version
In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system The
Customizing activities and their documentation are structured from a functional perspective (In order
to configure a whole system landscape from a process-oriented perspective SAP Solution Manager
which refers to the relevant Customizing activities in the individual SAP systems is used)
Target group
Solution consultants
Project teams for implementations or upgrades
Current version
In the SAP menu of the SAP system under Tools Customizing IMG
Production Operation
The technical operations manual is the starting point for operating a system that runs on SAP
NetWeaver and precedes the application operations guides of SAP Business Suite The manual refers
B Reference
B1 The Main SAP Documentation Types
5256 PUBLIC 2011-04-15
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
users to the tools and documentation that are needed to carry out various tasks such as monitoring
backup restore master data maintenance transports and tests
Target group
System administrators
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The application operations guide is used for operating an SAP application once all tasks in the
technical operations manual have been completed It refers users to the tools and documentation that
are needed to carry out the various operations-related tasks
Target group
System administrators
Technology consultants
Solution consultants
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Upgrade
The upgrade master guide is the starting point for upgrading the business scenarios and processes of
an SAP solution It provides scenario-specific descriptions of preparation execution and follow-up of
an upgrade It also refers to other documents such as upgrade guides and SAP Notes
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
The upgrade guide describes the technical upgrade of an installable unit taking into account the
combinations of operating systems and databases It does not describe any business-related
configuration
Target group
Technology consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcominstguides
Release notes are documents that contain short descriptions of new features in a particular release or
changes to existing features since the previous release Release notes about ABAP developments are the
technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide
(IMG)
Target group
B Reference
B1 The Main SAP Documentation Types
2011-04-15 PUBLIC 5356
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
Consultants
Project teams for upgrades
Current version
On SAP Service Marketplace at httpservicesapcomreleasenotes
In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)
B2 List of Documentation
Title Location
Master Guide SAP NetWeaver Process Integration 71 See SAP Service Marketplace at httpservicesapcominstallNWPI71
Technical Infrastructure Guide ndash SAP NetWeaver Process Integration 71
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Master Guide ndash SAP Solution Manager See SAP Service Marketplace at servicesapcom
instguides SAP Components SAP Solution ManagerltReleaesgt
Installation Guide ndash SAP Netweaver Process Integration 71 ltTechnologygt on ltOperating Systemgt ltDatabasegt or Installation Guide ndash SAP NetWeaver Process Integration 71 including Enhancement Package 1 ltTechnologygt on ltOperating Systemgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Front End See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Single Host See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP NetWeaver 71 TREX Multiple Hosts See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide SAP NetWeaver Developer Studio See SAP Service Marketplace at httpservicesapcominstallNWPI71
Planning Guide ndash System Landscape Directory See SDN at httpsdnsapcomnw-sld
User Guide ndash System Landscape Directory of SAP NetWeaver 71 See SDN at httpsdnsapcomnw-sld
Installation Guide ndash Adapter Engine (Java EE) on ltPlatformgt for SAP NetWeaver 71 or Installation Guide ndash Adapter Engine (Java EE) 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Installation Guide ndash SAP Partner Connectivity Kit 71 on ltPlatformgt or Installation Guide ndash Partner Connectivity Kit 71 Including Enhancement Package 1 on ltPlatformgt ltDatabasegt
See SAP Service Marketplace at httpservicesapcominstallNWPI71
Update Guide ndash Update of SAP Systems with Software Update Manager
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
Installation Guide ndash SAP Enhancement Package Installation for SAP NetWeaver Process Integration 71 Additional PI-Specific Information
See SAP Service Marketplace at httpservicesapcommaintenanceNWPI71
B Reference
B2 List of Documentation
5456 PUBLIC 2011-04-15
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2011 SAP AG All rights reservedNo 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