Anda di halaman 1dari 56

Master Guide SAP NetWeaver Process Integration 7.

1
Target Audience EB System administrators EB Technology consultants

PUBLIC =[sA>}"nPpz0)XA* =Ds\>B};nNiZ

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www.sap.com

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 notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, R/3, 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 countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. in the United States and in other countries. Sybase 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 company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
Disclaimer

Some components of this product are based on Java. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited, as is any decompilation of these components. Any Java Source Code delivered with this product is only to be used by SAPs Support Services and may not be modified or altered in any way.

2/56

PUBLIC

2011-04-15

Documentation in the SAP Service Marketplace

You can find this document at the following address: http://service.sap.com/instguides

2011-04-15

PUBLIC

3/56

Typographic Conventions

Example
<Example>

Description

Example Example Example


Example

Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, Enter your <User Name>. Arrows separating the parts of a navigation path, for example, menu options Emphasized words or expressions Words or characters that you enter in the system exactly as they appear in the documentation Textual cross-references to an internet address Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web Hyperlink to an SAP Note, for example, SAP Note 123456  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  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 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 Keys on the keyboard

http://www.sap.com /example

123456 Example

Example

EXAMPLE

EXAMPLE

4/56

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 http://service.sap.com/ instguides. The following table provides an overview on the most important document changes:
Version Date Description

1.0 1.1 1.2 1.3 1.4 1.5 1.6 1.7

2007-12-07 2008-02-05 2008-04-22 2008-05-29 2008-12-12 2009-03-19 2009-03-20 2011-04-15

First version WnB Changes to System Landscape Directory section WnB Minor changes Major revision of Shared Services section Information about dedicated PI system updated WnB Restructuring of content according to use case concept WnB Information about SAP enhancement package 1 for SAP NetWeaver PI 7.1 added Minor changes (mainly language corrections) Minor error corrections WnB Section SAP Enhancement Package 1 for SAP NetWeaver PI 7.1 updated (Software Update Manager replaces SAP Enhancement Package Installer) WnB Section Process Sequence: Installation of Enhancement Package 1 on an Existing SAP NetWeaver PI 7.1 system added WnB Section Maintaining System Landscape Information added WnB Further minor changes

2011-04-15

PUBLIC

5/56

Table of Contents

Chapter 1 Chapter 2 2.1 2.2 2.3 Chapter 3 3.1 3.1.1 3.1.2 3.1.3 3.2

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Before You Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . More Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing the SAP Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SAP NetWeaver PI Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installable Software Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Systems with Usage Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standalone Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SAP Enhancement Package 1 for SAP NetWeaver Process Integration 7.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SOA-Based Integration Use Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Implementation Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Process Sequence: Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 7.1 System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning Your System Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . End-to-End Solution Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Support Infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Collection of Landscape Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Authentication and Single Sign-On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Integrated User and Access Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Examples for the Overall System Landscape of Shared Services . . . . . . . . . . . . 11 11 11 12 13 15 16 19 21 23 25 25 25 27 28 33 33 35 37 37 38 39 39 39 40

Chapter 4 4.1 4.2 4.3 4.4

Chapter 5 5.1 5.2 5.2.1 5.2.1.1 5.2.1.2 5.2.1.3 5.2.1.4 5.2.1.5 5.2.2

6/56

PUBLIC

2011-04-15

5.2.3 5.2.3.1 5.2.3.2 5.2.3.3 Chapter A A.1 Chapter B B.1 B.2

Feature Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SAP Solution Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Solution Manager Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Landscape Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

42 42 43 43

Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Maintaining System Landscape Information . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 The Main SAP Documentation Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 List of Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

2011-04-15

PUBLIC

7/56

This page is left blank for documents that are printed on both sides.

Introduction

1 Introduction

This Master Guide provides you with a central starting point for the technical implementation of SAP NetWeaver Process Integration (SAP NetWeaver PI). It also contains information about enhancement package 1 for SAP NetWeaver Process Integration 7.1. SAP NetWeaver PI 7.1 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: X@ Introduction Contains an introduction to this guide. X@ 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. X@ SAP NetWeaver Overview Describes the building blocks of SAP NetWeaver PI. X@ SOA-Based Integration Use Case Introduces the use case and explains how to install it. X@ System Landscape Contains information about how to install your system landscape. X@ 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:// service.sap.com/installnwpi71 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

2011-04-15

PUBLIC

9/56

Introduction

recommend that you test these scenarios thoroughly in your test systems to ensure that they are complete and free of errors before going live.

10/56

PUBLIC

2011-04-15

2 2.1

Before You Start SAP Notes

2 Before You Start

2.1 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 http://service.sap.com/notes .
NOTE

The SAP Notes related to SAP NetWeaver PI 7.1 are also listed on SAP Service Marketplace at http://service.sap.com/sapnotesnwpi71.
List of Important SAP Notes SAP Note Number Title Description

1004107

Release Restrictions for SAP NetWeaver PI 7.1

1247043

Release Restrictions for SAP EHP1 for SAP NetWeaver PI 7.1

Some restrictions apply to the productive use of SAP NetWeaver PI 7.1. These are documented in this SAP Note. Some restrictions apply to the productive use of enhancement package 1 for SAP NetWeaver PI 7.1. These are documented in this SAP Note.

2.2 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 http://service.sap.com/instguidesnwpi71 for SAP NetWeaver Process Integration http://service.sap.com/platforms Product Information about supported platforms (operating systems, databases, browsers) for all SAP NetWeaver Availability Matrix components Sizing of SAP NetWeaver http://service.sap.com/sizing Information about security SAP Security Guide: See the SAP Library [page 12] at Adminitstrators Guide Security Guide Information about the technical operation of SAP Technical Operations Manual: See the SAP Library [page 12] NetWeaver at Adminitstrators Guide Technical Operations for SAP NetWeaver

2011-04-15

PUBLIC

11/56

2 2.3

Before You Start Accessing the SAP Library Location on SAP Service Marketplace or in SAP Library

Content

Information about SAP NetWeaver PI Support Package http://service.sap.com/netweaver SAP NetWeaver PI 7.1- Release-Specific Information Support Stacks Package Stacks Information Information about installing SAP NetWeaver Support http://service.sap.com/MaintenanceNWPI71 Support Package Stack Guide SAP NetWeaver Package Stacks.

2.3 Accessing the SAP Library


For more information about SAP NetWeaver Process Integration, access the SAP Library from any of the following: *?qK0 SAP Help Portal at http://help.sap.com/NWPI71 SAP NetWeaver Process Integration 7.1 Library <Language> 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. *?qK0 An SAP system if you have installed the online documentation: Choose Help SAP Library The browser starts. *?qK0 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.

12/56

PUBLIC

2011-04-15

SAP NetWeaver PI Overview

3 SAP NetWeaver PI Overview

Introduction

SAP NetWeaver PI 7.1 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 http://sdn.sap.com/netweaver 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: 5: Repository-based Modeling and Design 5: Service Bus-based Integration 5: 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 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 7.1 (SAP NetWeaver PI 7.1) is based on an established architecture for realizing cross-system business processes and is a further development of lower releases (SAP NetWeaver 7.0 usage type Process Integration and SAP XI 3.0 as part of SAP NetWeaver 2004). SAP NetWeaver PI 7.1 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:

2011-04-15

PUBLIC

13/56

SAP NetWeaver PI Overview

TU/p|SAP NetWeaver PI Key Capabilities Overview

SAP NetWeaver Process Integration 7.1 enables the integration of the applications of the following communication parties: &qM 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. &qM SAP: Applications that run on SAP systems. This includes the processing of events by using the Business Activity Monitoring (BAM) infrastructure. &qM 3rd-Party Application: Applications from 3rd-party providers within one system landscape, for example, database or file-system-based. &qM 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 7.1 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

14/56

PUBLIC

2011-04-15

3 3.1

SAP NetWeaver PI Overview Installable Software Units

services using semantic-rich classification systems. The Services Registry is part of Application Server Java (AS Java).

3.1 Installable Software Units


SAP NetWeaver comprises the following three types of installable software units: 2L Systems that are configured for a specific purpose, as indicated by one or more usage types 2L Standalone engines that provide one specific (server) function in combination with one or more SAP NetWeaver PI systems 2L 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:

2i\Ce2Installable Software Units for SAP NetWeaver PI

For this and other figures in this guide, the following legend applies:

2011-04-15

PUBLIC

15/56

3 3.1

SAP NetWeaver PI Overview Installable Software Units

I_?C^)g&Tvi(Legend

3.1.1 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: I_?q They are a structuring element for SAP software on a technical level. I_?q Usage Types determine the intended purpose of a system and the role it plays in a given (distributed) use case. I_?q They are realized by installing and configuring a collection of software components. I_?q They allow a logical view of the technology platform SAP NetWeaver PI. I_?q A usage type may require other usage types in the same system to operate. I_?q 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,

16/56

PUBLIC

2011-04-15

3 3.1

SAP NetWeaver PI Overview Installable Software Units

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 EEcompliant 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

2011-04-15

PUBLIC

17/56

3 3.1

SAP NetWeaver PI Overview Installable Software Units

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 SAP NetWeaver PI 7.1 <Technology> on <Operating System>: <Database> 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 http://service.sap.com/swdc Installations & Upgrades Entry by Application Component SAP Technology Components SAP Solution Manager <Release> 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 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: http://help.sap.com/ SAP Solution Manager SAP Solution Manager <Release> Implementing and Upgrading SAP Solutions Configuration

18/56

PUBLIC

2011-04-15

3 3.1

SAP NetWeaver PI Overview Installable Software Units

~ How to Create a Configuration Guide using SAP Solution Manager available at http:// service.sap.com/solutionmanager 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:

|.gd)O{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.

3.1.2 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.

2011-04-15

PUBLIC

19/56

3 3.1

SAP NetWeaver PI Overview Installable Software Units

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 Administrators 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 ABAP/Java 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 .

20/56

PUBLIC

2011-04-15

3 3.1

SAP NetWeaver PI Overview Installable Software Units

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 sender/receiver 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 7.1, but that have at least a Java Runtime Environment 5.0. 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.

3.1.3 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 versions:I :Bj: SAP GUI for Windows 7.10 (or higher) with the latest patch level

2011-04-15

PUBLIC

21/56

3 3.1

SAP NetWeaver PI Overview Installable Software Units

Wq SAP GUI for Java 7.10 (or higher) with the latest revision Wq The integrated SAP ITS 7.10 For more information about the SAP GUI family, see SAP Service Marketplace at http:// service.sap.com/sapgui. 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: Wq 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 7.0 or Firefox 2.0) and a virtual machine are required. SAP ITS 6.20 is not compatible with SAP NetWeaver 7.1. Wq 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 SAP Front End. Wq SAP GUI for the Windows environment (SAP GUI for Windows) SAP GUI for Windows is SAP's 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 SAP Front End.
SAP NetWeaver Developer Studio

The SAP NetWeaver Developer Studio is SAPs Integrated Development Environment (IDE) for Java and is based on the open-source tools framework Eclipse 3.3. 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 3.0 and JSF 1.2. During the installation of the SAP NetWeaver Developer Studio, several features are offered for installation. For SAP NetWeaver PI 7.1, only the following features are relevant: Wq SAP NetWeaver Developer Studio Platform Wq 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 developer's licence. For more information about the installation of SAP NetWeaver Developer Studio, see the Installation Guide SAP NetWeaver Developer Studio 7.1 or Installation Guide SAP NetWeaver Developer Studio 7.1 Including Enhancement Package 1.

22/56

PUBLIC

2011-04-15

3 3.2

SAP NetWeaver PI Overview SAP Enhancement Package 1 for SAP NetWeaver Process Integration 7.1

3.2 SAP Enhancement Package 1 for SAP NetWeaver Process Integration 7.1
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: Y+ You have reduced effort for testing and no effort for training when applying Support Packages, as new features are only shipped with enhancement packages. Y+ Adding new functions between releases becomes predictable and controllable. Y+ New functions can be added successively in small steps. There is no need to fully upgrade your system to get new functions. Y+ 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 7.1: Y+ New installation of SAP NetWeaver PI 7.1 including enhancement package 1 using the standard installation tool SAPinst. Y+ Upgrade of an existing SAP NetWeaver system from a release lower than SAP NetWeaver PI 7.1 to SAP NetWeaver PI 7.1 including enhancement package 1. For this, you use the upgrade programs SAPup (for ABAP) and SAPJup (for Java). Y+ Installation of the enhancement package on an existing SAP NetWeaver PI 7.1 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

2011-04-15

PUBLIC

23/56

3 3.2

SAP NetWeaver PI Overview SAP Enhancement Package 1 for SAP NetWeaver Process Integration 7.1

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:// service.sap.com/sltoolset. 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 7.1 System [page 28].
Content of SAP Enhancement Package 1 for SAP NetWeaver PI 7.1

With enhancement package 1 for SAP NetWeaver PI 7.1, new features are introduced and some existing are changed. The following is a selection of some of the most important enhancements: W/ Enhanced design and modelling options in the Enterprise Services Repository W/ New services registry W/ Support for new Web services standard (Web Services Reliable Messaging) W/ New modules for the Advanced Adapter Engine W/ Use of shared memory of the ABAP Application Server for message processing For more information about the changes, see SAP Library [page 12] at Whats new in SAP NetWeaver PI 7.1 Release Notes.

24/56

PUBLIC

2011-04-15

4 4.1

SOA-Based Integration Use Case Overview

4 SOA-Based Integration Use Case

4.1 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 (pointto-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 7.1 at https://www.sdn.sap.com/irj/sdn/soa-modeling Getting Started ; Service-Enabling a Legacy Application with SAP NetWeaver PI 7.1 at https://www.sdn.sap.com/irj/sdn/ soa-servicebus Getting Started In the following, you will find information about the installation of the involved software units.

4.2 System Landscape


The following figure shows the system landscape for this use case:

2011-04-15

PUBLIC

25/56

4 4.2

SOA-Based Integration Use Case System Landscape

t\e.3>\USOA-Based Integration

t\NC 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 3.0 is compatible with SAP NetWeaver 6.40 and 7.0 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

t\NC t\NC

t\NC

t\NC

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 7.0 system with usage type DI to transport design objects and repository objects. For more information, see the SAP Library [page 12] at Administrators 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

26/56

PUBLIC

2011-04-15

4 4.3

SOA-Based Integration Use Case Implementation Sequence

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. q7 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. q7 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.

4.3 Implementation Sequence


Procedure

To install this use case, perform the steps listed in the following table:
Step Action [Corresponding Documentation] Remarks

Make sure that you have performed the preparation / steps: q7 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). q7 With the help of your hardware partner, you have mapped your systems and standalone engines to properly sized hosts. q7 You have planned and installed shared services [page 35]. Installation of system with usage type PI (includes the q7 If you want to use the features of installation of AS ABAP and AS Java) enhancement package 1, use the direct installation of SAP NOTE NetWeaver PI 7.1 including For usage type PI, a Unicode installation is enhancement package 1. mandatory. q7 Make sure that you perform the configuration steps as described in [Installation Guide SAP NetWeaver Process Integration 7.1 the installation guide. For certain <Technology> on <Operating System>: <Database> or usage types, configuration tasks can Installation Guide SAP NetWeaver Process Integration 7.1 be applied by the configuration including Enhancement Package 1 <Technology> on <Operating wizard. These configuration tasks, System>: <Database>] as well as any additional configuration steps for your use case are listed in SAP Solution Manager. For more information,

2011-04-15

PUBLIC

27/56

4 4.4

SOA-Based Integration Use Case Process Sequence: Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 7.1 System Action [Corresponding Documentation]

Step

Remarks

see the Installation Guide SAP NetWeaver Process Integration 7.1 <Technology> on <Operating System>: <Database>. 3 Install the Adapter Engine (Java SE) engines, if required. [Installation Guide Adapter Engine (Java EE) on <Platform> for SAP NetWeaver 7.1 or Installation Guide Adapter Engine (Java EE) 7.1 Including Enhancement Package 1 on <Platform>: <Database>] 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 partner's or subsidiary's system landscape [Installation Guide SAP Partner Connectivity Kit 7.1 on <Platform> or Installation Guide Partner Connectivity Kit 7.1 Including Enhancement Package 1 on <Platform>: <Database>] 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 ] Installation of clients: CN[c SAP GUI [Installation Guide SAP Front End]

4.4 Process Sequence: Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 7.1 System
The process sequences give a comprehensive overview of the steps relevant for the enhancement package installation on an existing SAP NetWeaver PI 7.1 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: CN[c Manual Selection

28/56

PUBLIC

2011-04-15

4 4.4

SOA-Based Integration Use Case Process Sequence: Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 7.1 System

You manually select the required files from SAP Service Marketplace at http:// service.sap.com/swdc using the SP Stack Application. You use the Maintenance Optimize only to approve the packages which is a prerequisite for the download. Kf 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 Phase Step Description Documentation

Hardware & Software Prerequisites Solution Manager Prerequisites

Check which platforms are supported for your target release (OS/DB dependencies) Check which hardware sizing is required for your target release 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 level. At least SAP Solution Manager 7.0 EHP1 Support Package Stack 17 is required. We recommend to use SAP Solution Manager 7.0 EHP1 Support Package Stack 23. Check if you need to do an update or upgrade of your SAP Solution Manager. Make sure that you run the guided procedure SOLMAN_SETUP after every installation or update of SAP Solution Manager and that it completes successfully.

Product Availability Matrix (PAM) at http://


service.sap.com/pam

Sizing information at http://


service.sap.com/sizing

For upgrades from source release SAP Solution Manager 3.1 and 3.2: Upgrade Guide SAP Solution Manager 7.0 incl. Enhancement Package 1 For updates from SAP Solution Manager 7.0: Update Guide SAP Enhancement Package 1 for SAP Solution Manager 7.0 Follow-up activities after an Support Package Stack update or enhancement package update: Solution Operations Guide SAP Solution Manager 7.0 EHP1, section Software Change Management All guides are available at http:// service.sap.com /instguides SAP Components SAP Solution Manager -> Release 7.0 EHP 1

Implementation Phase Step

Description

Documentation

1 Solution Manager Preparation

Kf Configure the SAP Solution Kf Configuration of Maintenance Manager Maintenance Optimizer: http:// help.sap.com SAP Solution Optimizer. Manager SAP Solution Manager If you want to use SAP Solution Kf <Release> Change Request Manager Maintenance Management and Change Control Optimizer for the automatic Maintenance Optimizer calculation of software Prerequisites packages, make sure your

2011-04-15

PUBLIC

29/56

4 4.4

SOA-Based Integration Use Case Process Sequence: Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 7.1 System

Implementation Phase Step

Description

Documentation

2 System Preparation

3 Software Download

system landscape data in SAP :` Landscape Verification: Solution Manager is http:// :` maintained correctly. www.sdn.sap.com/irj/ Landscape Verification 1.0, sdn/alm-updatewhich is an add-on to SAP management link Solution Manager can support Landscape Verification under you in maintaining your Related Areas on Upgrade and system landscape data. The use Update Management (in the of this tool is optional. 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 7.0 EHP1 SP23. Prepare your system as described in :` Update Guide Update of SAP Systems with Software Update the documentation, for example perform OS / DB specific Manager , sections Planning and preparations and the PI-specific Preparation preparations :` Installation Guide SAP Enhancement Package Installation for SAP NetWeaver Process Integration 7.1: Additional PI-Specific Information http://help.sap.com SAP Select and download the software packages in either of the following Solutions SAP Solution Manager SAP Solution Manager 7.0 EHP1 <SP> ways: Change Request Management and :` Automatic calculation: Create a maintenance transaction in Change Control Maintenance Optimizer Maintenance Procedure Scenarios the Maintenance Optimizer and choose the Calculate Files For information about the automatic calculation, see Automatically option. Maintenance Transaction with Installation of Manual Selection: Create a :` maintenance transaction in the an Enhancement Package. Maintenance Optimizer and For information about the manual choose the Select Files Manually selection and approval process, see option. You then can select the section Approve and Download Files in Download Basket . 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

30/56

PUBLIC

2011-04-15

4 4.4

SOA-Based Integration Use Case Process Sequence: Installation of Enhancement Package 1 on an Existing SAP Netweaver PI 7.1 System

Implementation Phase Step

Description

Documentation

application. Choose Generate Stack XML and save the file. Run Software Update Manager to Update Guide Update of SAP Systems with 4 Software Update Manager Enhancement Package Installation update your system with the selected software packages. Perform technical and PI-specific 5 #(>Z Update Guide Update of SAP Systems with Software Update Follow-Up Steps follow-up activities after the enhancement package installation Manager , section Follow-Up is done. Activities. #(>Z Installation Guide SAP Enhancement Package Installation for SAP NetWeaver Process Integration 7.1: Additional PI-Specific Information Configure newly installed See Systems with Usage Types [page 16], 6 Configuration enhancement package functions section Configuration of Systems with using SAP Solution Manager Usage Types content.

2011-04-15

PUBLIC

31/56

This page is left blank for documents that are printed on both sides.

5 5.1

System Landscape Planning Your System Landscape

5 System Landscape

5.1 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: j$ Which systems and standalone engines you require j$ 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: j$ 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: j$ http://service.sap.com/sizing for the SAP NetWeaver PI 7.1 sizing guide available under Sizing Guidelines Business Suite & Services . j$ http://service.sap.com/quicksizer for more information and access to the tool itself j$ Also consider the following important aspects concerning sizing: j$ High availability

2011-04-15

PUBLIC

33/56

5 5.1

System Landscape Planning Your System Landscape

For more information, see SAP Developers Network at http://sdn.sap.com//irj/sdn/ landscapedesign Technical Infrastructure High Availability . 2 Unicode For more information, see SAP Developers Network at http://sdn.sap.com//irj/sdn/ landscapedesign Internationalization . 2 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.

Htl niExample 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: 2 Number of required SAPS (SAP Application Benchmark Performance Standard) for each system (provided by Quick Sizer) 2 Landscape-relevant aspects concerning security. For more information, see the SAP Security Guide in the SAP Library [page 12] at Administrators Guide Security Guide . 2 Landscape-relevant aspects concerning scalability, high availability, operation, and software life-cycle management

34/56

PUBLIC

2011-04-15

5 5.2

System Landscape Shared Services

For more information about relevant aspects for the mapping of systems to hosts, see the document Technical Infrastructure Guide SAP NetWeaver available on SAP Service Marketplace at http:// service.sap.com/installNWPI71.
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: BOJ You could install multiple systems of one type and use them for different purposes. BOJ 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 SAP NetWeaver available on SAP Service Marketplace at http:// service.sap.com/installNWPI71. BOJ For every SAP system, you could additionally install Web Dispatcher. For more information, see the SAP Library [page 12] at FunctionOriented View Application Server Infrastructure SAP Web Dispatcher . BOJ You could further distribute certain standalone engines 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 SAP NetWeaver PI 7.1 available in SAP Service Marketplace at http://service.sap.com/installNWPI71.

5.2 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: BOJ 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 (7.0) 4.0 Support Package 15, SAP Solution Manager has become the platform for SAP's 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 7.0 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 7.0. For more information, see SAP Note 805390.

2011-04-15

PUBLIC

35/56

5 5.2

System Landscape Shared Services

jBt 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 7.0. 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. jBt 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: jB 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 7.1, it has a special role, which you need to activate using a configuation wizard. jB 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 7.0 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. jBt 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 3.1). 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. jBt 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). jBt Adaptive Computing Controller

36/56

PUBLIC

2011-04-15

5 5.2

System Landscape Shared Services

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 started/stopped/relocated, 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 Adaptive Computing Controller in SAP NetWeaver 7.1 available on SAP Service Marketplace at http://service.sap.com/installNWPI71. For more information about Adaptive Computing in general, see http://sdn.sap.com/irj/ sdn/adaptive .

5.2.1 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.

5.2.1.1 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:// service.sap.com/supportstandards. 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 7.0 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: ~b Easy to use, similar look and feel ~b Context transfer while jumping from one work center into another ~b Logical grouping of tools for a certain area ~b Simple authorization concept ~b 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:

2011-04-15

PUBLIC

37/56

5 5.2

System Landscape Shared Services

G Business Process Operations G Change Management G Root Cause Analysis G Implementation / Upgrade G Incident Management G Test Management G Job Management G System Landscape Management G Solution Documentation Assistant G SAP Engagement and Service Delivery G SAP Solution Manager Administration G System Administration G System Monitoring My Home is the central point of access to all important data of almost all work centers in SAP Solution Manager.

5.2.1.2 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 7.0. Solution Manager Diagnostics also contains two third-party tools, CAs Wily Introscope for measuring performance, as well as troubleshooting problems of the Java EE Engine and applications running on it, and Mercury Loadrunner, 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.

38/56

PUBLIC

2011-04-15

5 5.2

System Landscape Shared Services

Landscape Aspects

If you use SAP NetWeaver Process Integration 7.1 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 SAP Solution Manager 7.0 available on SAP Service Marketplace at http://service.sap.com/ instguides SAP Components SAP Solution Manager <Release> .

5.2.1.3 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 7.1, 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.

5.2.1.4 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 Administrators Guide Security Guide

5.2.1.5 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. SAP's 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.

2011-04-15

PUBLIC

39/56

5 5.2

System Landscape Shared Services

For more information, see the SAP Library [page 12] at Administrators Guide Security Guide .

5.2.2 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 test/quality 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 MediumSized Customer Landscapes with Java

As you use Java productively for SAP NetWeaver PI 7.1, 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 7.0 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 http://service.sap.com/sizing Sizing Guidelines Solutions & Platform . We recommend that you start with this centralized SAP Solution Manager approach as depicted in the following figure:

40/56

PUBLIC

2011-04-15

5 5.2

System Landscape Shared Services

VNB
@WN"089Single 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: Vk You may set up an extra system or client for Central User Administration (CUA). Vk The Change and Transport System (CTS) can run on an extra system. However, it is not performance- or data-intensive. Vk 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. Vk You can use a separate SAP NetWeaver 7.0 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. Vk 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.

2011-04-15

PUBLIC

41/56

5 5.2

System Landscape Shared Services

5.2.3 Feature Details


This section provides further information about the features described above.

5.2.3.1 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 7.0 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 7.0 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

Benefits and usage scenarios

Master Guide SAP Solution Manager available on SAP Service Marketplace at http://service.sap.com/ instguides SAP Components SAP Solution Manager <Release> SAP Solution Manager Learning Maps available on SAP Service Marketplace at http://

42/56

PUBLIC

2011-04-15

5 5.2 Topic

System Landscape Shared Services Where to Find More Information


service.sap.com/rkt-solman

or

https://

service.sap.com/solutionmanager

Additional information

See SAP Service Marketplace at

http://

service.sap.com/solutionmanager

5.2.3.2 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 7.0. 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 http://service.sap.com/diagnostics.

5.2.3.3 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.

2011-04-15

PUBLIC

43/56

5 5.2

System Landscape Shared Services

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 upto-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 7.1 landscape, consider the following aspects: ,( Part of SAP NetWeaver PI 7.1 is a new version of the System Landscape Directory. It is automatically included in every SAP NetWeaver 7.1 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 7.1, 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 7.1, you have the following options concerning SLD: ,( Option 1: Run SAP NetWeaver PI 7.1 against an existing SLD running on SAP NetWeaver 7.0. We only recommend this for upgrades from SAP NetWeaver 7.0 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 7.1 system. We recommend this option for new installations and upgrades from older releases than SAP NetWeaver 7.0 due to the enhanced functions and improved performance of SLD 7.1.
NOTE

If you already have a central SLD running on SAP NetWeaver 7.0 in operation, you could run two SLD versions in parallel SLD running on SAP NetWeaver 7.1 for your PI systems and SLD running on SAP NetWeaver 7.0 for all other systems/use cases. This way, your SAP

44/56

PUBLIC

2011-04-15

5 5.2

System Landscape Shared Services

NetWeaver PI 7.1 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 7.0 to an SLD running on SAP NetWeaver 7.1. 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 7.1 system is available, you could move your central SLD also to SAP NetWeaver 7.1. Then, you could optionally shift your PI data back to the central SLD or continue to run a dedicated SLD for your PI systems.

=vh`)YW

=7 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

2011-04-15

PUBLIC

45/56

5 5.2

System Landscape Shared Services

the applications that rely on it), see the documentation Planning Guide System Landscape Directory available in SAP Developers Network at http://sdn.sap.com/irj/sdn/nw-sld .
Implementation Sequence

Perform the following steps:


No. Action [Corresponding Documentation] Remarks and Subsequent Steps

During the installation of the PI 7.1 system, ZI If you want to configure the SLD in an perform the corresponding automatic existing AS Java system, see the User Guide configuration steps for the SLD offered by the System Landscape Directory. installation procedure. ZI For the data exchange between the data [Installation Guide SAP Netweaver Process Integration 7.1 suppliers of ABAP-based systems and the on <Operating System>: <Database>] system landscape directory, a gateway process is required since the data is exchanged using RFC. As of SAP NetWeaver 7.1, 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. Download and install the most current system landscape directory content - updated monthly available on SAP Service Marketplace. [SAP Note 669669]

46/56

PUBLIC

2011-04-15

A A.1

Appendix Maintaining System Landscape Information

A Appendix

A.1 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 Managers 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 1.0 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 System Landscape Directory available at http://sdn.sap.com/irj/sdn/nw-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 http://help.sap.com/ SAP NetWeaver SAP NetWeaver Process Integration SAP NetWeaver Process Integration Library <Language> 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.

2011-04-15

PUBLIC

47/56

A A.1

Appendix Maintaining System Landscape Information

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 http://help.sap.com SAP Solution Manager 7.0 <Language> Basic Settings Solution Manager System Landscape Set Up Automatic Data Capture for System Landscape .

b8|Ud6]Capturing System Data Using SLD Running the Landscape Verification 1.0

Running the landscape verification 1.0 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 1.0 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.

48/56

PUBLIC

2011-04-15

A A.1

Appendix Maintaining System Landscape Information

')Ax Z/mULandscape Verification 1.0 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 <System> . 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. 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 Z.... 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).

4.

5.

2011-04-15

PUBLIC

49/56

A A.1

Appendix Maintaining System Landscape Information RECOMMENDATION

6.

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. 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.

50/56

PUBLIC

2011-04-15

B B.1

Reference The Main SAP Documentation Types

B Reference

B.1 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 SAPs terminology database. It contains SAP-specific vocabulary in over 30 languages, as well as many glossary entries in English and German. K Target group: Kl Relevant for all target groups K Current version: Kl On SAP Help Portal at http://help.sap.com Glossary Kl In the SAP system in transaction STERM SAP Library is a collection of documentation for SAP software covering functions and processes. K Target group: Kl Consultants Kl System administrators Kl Project teams for implementations or upgrades K Current version: Kl On SAP Help Portal at http://help.sap.com (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. K Target group: Kl System administrators Kl Technology consultants Kl Solution consultants K Current version: Kl On SAP Service Marketplace at http://service.sap.com/securityguide
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,

2011-04-15

PUBLIC

51/56

B B.1

Reference The Main SAP Documentation Types

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. (`Rd Target group: (`R Technology consultants (`R Project teams for implementations (`Rd Current version: (`R On SAP Service Marketplace at http://service.sap.com/instguides 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. (`Rd Target group: (`R Technology consultants (`R Project teams for implementations (`Rd Current version: (`R On SAP Service Marketplace at http://service.sap.com/instguides Configuration Documentation in SAP Solution Manager 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. (`Rd Target group: (`R Technology consultants (`R Solution consultants (`R Project teams for implementations (`Rd Current version: (`R 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.) (`Rd Target group: (`R Solution consultants (`R Project teams for implementations or upgrades (`Rd Current version: (`R 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

52/56

PUBLIC

2011-04-15

B B.1

Reference The Main SAP Documentation Types

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. %ClH Target group: %ClH System administrators %ClH Current version: %ClH On SAP Service Marketplace at http://service.sap.com/instguides 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. %ClH Target group: %ClH System administrators %ClH Technology consultants %ClH Solution consultants %ClH Current version: %ClH On SAP Service Marketplace at http://service.sap.com/instguides
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. %ClH Target group: %ClH Technology consultants %ClH Project teams for upgrades %ClH Current version: %ClH On SAP Service Marketplace at http://service.sap.com/instguides 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. %ClH Target group: %ClH Technology consultants %ClH Project teams for upgrades %ClH Current version: %ClH On SAP Service Marketplace at http://service.sap.com/instguides 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). %ClH Target group:

2011-04-15

PUBLIC

53/56

B B.2

Reference List of Documentation

m Consultants m Project teams for upgrades mr Current version: m On SAP Service Marketplace at http://service.sap.com/releasenotes m In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)

B.2 List of Documentation


Title Location

Master Guide SAP NetWeaver Process Integration 7.1 Technical Infrastructure Guide SAP NetWeaver Process Integration 7.1 Master Guide SAP Solution Manager

See SAP Service Marketplace at http://


service.sap.com/installNWPI71

See SAP Service Marketplace at http://


service.sap.com/installNWPI71

Installation Guide SAP Netweaver Process Integration 7.1 <Technology> on <Operating System>: <Database> or service.sap.com/installNWPI71 Installation Guide SAP NetWeaver Process Integration 7.1 including Enhancement Package 1 <Technology> on <Operating System>: <Database> Installation Guide SAP Front End See SAP Service Marketplace at http://
service.sap.com/installNWPI71

See SAP Service Marketplace at service.sap.com/ instguides SAP Components SAP Solution Manager <Releaes> See SAP Service Marketplace at http://

Installation Guide SAP NetWeaver 7.1 TREX Single Host

See SAP Service Marketplace at http://


service.sap.com/installNWPI71

Installation Guide SAP NetWeaver 7.1 TREX Multiple Hosts See SAP Service Marketplace at http://
service.sap.com/installNWPI71

Installation Guide SAP NetWeaver Developer Studio Planning Guide System Landscape Directory User Guide System Landscape Directory of SAP NetWeaver 7.1 Installation Guide Adapter Engine (Java EE) on <Platform> for SAP NetWeaver 7.1 or Installation Guide Adapter Engine (Java EE) 7.1 Including Enhancement Package 1 on <Platform>: <Database> Installation Guide SAP Partner Connectivity Kit 7.1 on <Platform> or Installation Guide Partner Connectivity Kit 7.1 Including Enhancement Package 1 on <Platform>: <Database> Update Guide Update of SAP Systems with Software Update Manager Installation Guide SAP Enhancement Package Installation for SAP NetWeaver Process Integration 7.1: Additional PI-Specific Information

See SAP Service Marketplace at http://


service.sap.com/installNWPI71

See SDN at http://sdn.sap.com/nw-sld See SDN at http://sdn.sap.com/nw-sld See SAP Service Marketplace at http://
service.sap.com/installNWPI71

See SAP Service Marketplace at http://


service.sap.com/installNWPI71

See SAP Service Marketplace at http://


service.sap.com/maintenanceNWPI71

See SAP Service Marketplace at http://


service.sap.com/maintenanceNWPI71

54/56

PUBLIC

2011-04-15

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www.sap.com

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 notice.