Planning Guide

System Landscape Directory
Document Version 2.05 – December 2008

© Copyright 2008 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. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries. These materials are subject to change without notice. These materials 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. MaxDB is a trademark of MySQL AB, Sweden.

other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. 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.

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. SAP Library document classification: PUBLIC

Typographic Conventions
Type Style Example Text Represents Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options. Cross-references to other documentation Example text Emphasized words or phrases in body text, titles of graphics and tables Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE. Screen output. This includes file and directory names and their paths, messages, names of variables and parameters, source code as well as names of installation, upgrade and database tools. Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries. Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Icons
Icon Meaning Caution Example Note Recommendation Syntax

EXAMPLE TEXT

Example text

Example text

<Example text>

EXAMPLE TEXT

Planning Guide – System Landscape Directory

Document History
Before you start planning, make sure you have the latest version of this document. You can find the latest version on the SAP Developer Network (SDN) at: http://sdn.sap.com/irj/sdn/nw-sld (or choose http://sdn.sap.com SAP NetWeaver Capabilities Lifecycle Management Application Management System Landscape Directory).

The following table provides an overview on the most important changes to this document. Version 2.05 2.04 2.03 Date Sept./Dec. 2008 August 2008 April 2008 Description Adapted general recommendation. Adapted recommendation for SAP Solution Manager to have always a local SLD (see section SAP Solution Manager). Added recommendation to start an additional gateway service (used as Standalone Gateway for SLD) for the Java SCS instance of a standalone SLD in section Where to Run SLD in Your System Landscape. Added information and recommendation about SAP Solution Manager. Added information about restrictions of switching DNS aliases. Guide restructured (such as in section SLD Landscape Planning), added new general landscape recommendations Added information about the transport of SLD objects with the enhanced Change and Transport System in section Synchronization Options Minor changes 1.51 January 2008 Added further information about how SAP Solution Manager relies on SLD. Minor changes 1.50 December 2007 Added information about full automated synchronization provided with SAP NetWeaver 7.1. Guide restructured Minor changes 1.45 July 2007 In sections Automatic Forwarding of Landscape Data and Release Compatibility, changed statement concerning required CIM data models and SAP CR content versions of SLD instances that synchronize data using automatic forwarding – in contrast to the former statement, automatic forwarding works independent of releases, patch levels, and installed CIM data models and SAP CR content versions of the involved SLD instances, as the SLD bridge forwards data without interpreting or changing it. Added section Central SLD Running on a Production System. Minor changes

2.02 2.01 2.00

April 2008 March 2008 March 2008

4

December 2008

Planning Guide – System Landscape Directory

Contents
1 Introduction.................................................................................................................... 6 1.1 1.2 1.3 2 3 Structure of the Planning Guide............................................................................... 6 More Information..................................................................................................... 6 Accessing the SAP Library...................................................................................... 7

Overview ....................................................................................................................... 8 SLD Topology................................................................................................................ 9 3.1 Process to Define Your SLD Landscape Strategy.................................................... 9 3.2 SLD Clients – How the SLD is Used by SAP Applications...................................... 12 3.2.1 SAP NetWeaver Process Integration ................................................................. 13 3.2.2 Web Dynpro Applications .................................................................................. 14 3.2.3 SAP NetWeaver Development Infrastructure ..................................................... 15 3.2.4 SAP Solution Manager ...................................................................................... 15 3.2.5 SAP NetWeaver Administrator........................................................................... 16 3.2.6 Adaptive Computing Controller .......................................................................... 16 3.3 Fundamental SLD Concepts ................................................................................. 17 3.3.1 Reasons to Have Several SLD instances........................................................... 17 3.3.2 Synchronization Options.................................................................................... 17 3.3.3 Release Compatibility........................................................................................ 24 3.3.4 How You Can Handle Possible Changes to Your SLD Strategy ......................... 25 3.4 SLD Landscape Planning...................................................................................... 26 3.4.1 Recommendations for SLD Landscapes ............................................................ 26 3.4.2 Where to Run SLD in Your System Landscape .................................................. 42 3.4.3 Sizing Requirements of a System for SLD ......................................................... 45

4

Appendix ..................................................................................................................... 47 4.1 Network Access Scenarios.................................................................................... 47 4.1.1 Intranet Scenario ............................................................................................... 47 4.1.2 Extranet Scenario.............................................................................................. 48 4.2 Overview of Connections to and from SLD ............................................................ 49 4.2.1 ABAP Data Supplier (1)..................................................................................... 49 4.2.2 Java Data Supplier (2)....................................................................................... 49 4.2.3 External Data Supplier (3).................................................................................. 50 4.2.4 Java SLD Client (4) ........................................................................................... 50 4.2.5 ABAP SLD Client (5) ......................................................................................... 50 4.2.6 SLD to SLD Message Forwarding (6)................................................................. 50

December 2008

5

com SAP NetWeaver Capabilities Lifecycle Management Application Management System Landscape Directory User Manual – SLD: http://sdn.sap.com SAP NetWeaver Capabilities Lifecycle Management Application Management System Landscape Directory Platform and Technology Information Center Sizing of SAP NetWeaver SAP Service Marketplace at: service. and recommendations for typical SLD landscapes.sap.2 More Information The following list contains links to information about the SLD on the SDN and in the SAP Library: Content Information about the SLD and corresponding documentation Location on SDN or in the SAP Library http://sdn. It provides information about landscape scenarios.Planning Guide – System Landscape Directory 1 Introduction This documentation provides you with a central starting point for the planning of your landscape strategy for the System Landscape Directory (SLD) of SAP NetWeaver®. 1.com/irj/sdn/nw-sld or choose http://sdn.com/irj/sdn/nw-sld or choose http://sdn.1 Structure of the Planning Guide The planning guide consists of the following sections: Introduction This section contains information about this documentation and related information important for the planning of the SLD.sap. Appendix This section provides additional information.sap. System Landscape Directory Topology This section introduces a high-level process to define an individual landscape strategy for the SLD based on your requirements. recommendations on which host you could run the SLD in your system landscape. Overview Contains a short introduction to the SLD. such as network access scenarios and information about all communication paths to and from the SLD.sap.com/platforms SAP Service Marketplace at: service. 1.com/sizing Configuring and using the SLD 6 December 2008 .sap.

The browser starts. Therefore.com Select the required language. An SAP system if you have installed the online documentation: Choose Help SAP Library. The help files on the online documentation CDs or DVDs If you want to view the help files in HTML Help format from the online documentation CDs or DVDs. SAP NetWeaver <Release> The SAP Help Portal contains the latest version of the SAP Library. December 2008 7 . we recommend that you use this channel to access the SAP Library.3 Accessing the SAP Library You can access the SAP Library as follows: SAP Help Portal at help.sap.Planning Guide – System Landscape Directory Content Information about security Location on SAP Community Network or in the SAP Library SAP Security Guide: Located in the SAP Library [page 7] at SAP NetWeaver Library System Administration SAP NetWeaver Security Guide Technical Operations Manual: Located in the SAP Library [page 7] at SAP NetWeaver Library System Administration Technical Operations Manual for SAP NetWeaver Information about the technical operation of SAP NetWeaver 1. you need a PC running Microsoft Windows on which you can install the HTML Help viewer.

since the SLD is part of SAP NetWeaver. the 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). the SLD 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. the SLD provides reliable and up-to-date information with minimized effort for you. It contains a description of your system landscape (that is. 8 December 2008 . This abbreviation is solely intended to improve readability.Planning Guide – System Landscape Directory 2 Overview The system landscape directory of SAP NetWeaver (abbreviated to SLD in the rest of this documentation) is the central directory of system landscape information that is relevant for the management of your software life-cycle. The abbreviation SLD is not intended to define a product. Since the landscape description is updated automatically. In this way.

such as reasons to have more than one SLD. The following figure shows a possible process to define a strategy about how and where to run SLD in your system landscape: How and where to run SLD in my system landscape? Learn SLD concepts Identify your Logical SLD landscape Where to run SLD? Synchronization 1. Therefore.1 Process to Define Your SLD Landscape Strategy You can install and run the SLD in your SAP NetWeaver landscape in many different ways. For more information about fundamental SLD concepts. synchronization options of SLD.Planning Guide – System Landscape Directory 3 SLD Topology 3. see the following sections: Reasons to Have Several SLDs [page 17] Synchronization Options [page 17] Release Compatibility [page 22] How You Can Handle Possible Changes to Your SLD Strategy [page 25] December 2008 9 . see section SLD Clients – How SLD is Used by SAP Applications [page 12]. Each option has different advantages and disadvantages. Familiarize yourself with how the SLD is used by SAP applications and with fundamental concepts. you must plan the installation of the SLD properly according to your landscape requirements. and release compatibility considerations: For more information about how the SLD is used by SAP applications.

Make sure that you have up-to-date versions of SAP Notes. 3. the corresponding decision results from the requirements you are facing in your landscape concerning SLD (for example. SAP provides a full automatic synchronization mechanism for all SLD data that could dramatically reduce manual synchronization effort in SAP NetWeaver 7. which you can find on SAP Service Marketplace at service. retention periods. required availability of the SLD and the impact on your system landscape if an SLD is temporary not available Required performance for accessing the SLD (for example. affected by network lags due to a large physical distance between an SLD client and your SLD itself or insufficient hardware performance of the host on which you run your SLD) Technical constraints of your system landscape (such as networks. and high availability) Required visibility and changeability of certain data stored in the SLD (for example. define your logical SLD landscape and define the number of required SLD instances). Decide how your SLD landscape will look like based on the information provided in section SLD Landscape Planning [page 26]: a. Next. you might have the requirement to restrict access to the data of production systems for developers) Legal constraints (such as sensitivity of data. Consider the recommendations about how to set up an SLD in your system landscape in section Recommendations for SLD Landscapes [page 26]. The following are example requirements: Applications that rely critically on the SLD in your system landscape. you have to think about synchronizing the SLD data stored in your SLD instances. decide on which system or systems you want to run your SLD instance or instances. your SAP NetWeaver Process Integration system) on an existing system. b. As a result of this step. This is the most important step for defining an individual SLD landscape strategy. load of the corresponding host. see sections Where to Run SLD in Your System Landscape [page 42] and Sizing Requirements of a System for SLD [page 45]. For example.sap. network connection). To a certain degree. you should get a clear picture of the SLD landscape you want to run. firewalls. planned/unplanned downtime. get a clear picture of the requirements that your system landscape demands concerning the data stored in the SLD and map those requirements to the SLD landscape recommendations provided in this documentation. and country-specific laws) Company rules.1 and higher. You can run an SLD either on a dedicated AS Java system or together with other central shared services or business functions (for example.com/notes. Firstly. 10 December 2008 . For more information. organizational structures or governance models For more information. message volumes. see section Synchronization Options [page 17]. high availability features. If you require more than one SLD. For more information about available synchronization options.Planning Guide – System Landscape Directory 2. hardware. Secondly. see SAP Note 764393 (Configuration of the SAP System Landscape Directory).

In addition. see SAP Note 764393 (Configuration of the SAP System Landscape Directory). you should receive a synchronization strategy for your SLD instances.Planning Guide – System Landscape Directory To do so. For example. you might want to restrict the forwarding of certain data to certain SLD instances in your landscape to generate different views. we recommend that you create some kind of operation manual that helps to establish a process about when and how synchronization must be performed. December 2008 11 . create a model to understand which data is required in which of your planned SLD instances. For further information about synchronizing SLD instances in a landscape. and by whom. If manual synchronization is required. As a result of this step. you may not want to forward data of your production systems to a development SLD.

configuration Deployed Web Deployed Web Dynpro App Dynpro App J2EE Web Dynpro Runtime ABAP Web Dynpro Runtime Web Dynpro Web Dynpro App App Retrieve dev. 12 December 2008 . configuration SLD Register dev.Planning Guide – System Landscape Directory 3. configuration SAP NetWeaver Developer Studio HTTP(S) ABAP development Workbench DTR Development Objects CMS (Landscape Configurator) Web Dynpro Application CBS /workspace /inactive /active /buildspace Binaries of used SCs SAP Enterprise Portal Web Dynpro Runtime Development Configuration Software Lifecycle Manager of SAP NetWeaver SAP NetWeaver Development Infrastructure SLD SAP NetWeaver Process Integration … Other Clients Central Monitoring & Administration System SAP NetWeaver Administrator SLD Solution Manager Adaptive Computin g Controller Solution Manager Cont rol Node Productive Landscape Centralized Storage System Monitoring Monitoring& &Management ManagementConnectivity ConnectivityLayer Layer (JMX. To do so.a.) RMI Business Data Web Service Provider Web Service SOAP Business Data ABAP Backend Business Backend Backend Application Application Server Data RFC enabled Function Modules RFC Retrieve storage location of dev. (JMX. The following figure shows applications and tools .that use the data stored in the SLD to provide service.2 SLD Clients – How the SLD is Used by SAP Applications This section provides information how the SLD is used by different applications. the SLD clients read data from and write data to the SLD: J2EE Backend Server EJB (e.known as SLD clients .Agents…) Agents…) Server Network Switch ABAP System Java System Non-SAP Component Computing Nodes SAP NetWeaver Administrator Storage Network Switch SAP Solution Manager Adaptive Computing Controller The following sections provide information about how the most important applications shown above use and rely on data stored in the SLD.

if your SAP NetWeaver PI systems use more than one SLD. These transport targets define which system in one environment (DEV. QA. if you have configured that a message is sent from PID to BSD in your development environment. PROD SLD requires information about the business systems from both QA and PROD environment. from TEST to QA. and from QA to PROD so that each SLD contains the business systems from its own environment and from the environment of the predecessor SLD: DEV SLD only requires information about DEV business systems. If you now transport configuration objects from one environment to the other. also propagate business systems (and the corresponding technical systems) from DEV to TEST. QA SLD requires information about the business systems from both DEV and QA environments. In the SLD. For example. this configuration will be changed to PIQ BSQ in your quality assurance environment. As a result. It is used: For receiver determination in the Integration Directory of SAP NetWeaver PI By application systems to get their own business system name (Java Proxy Framework and SAP systems) Therefore. you define that the business system BSD in your development environment corresponds to a business system BSQ in your quality assurance environment and that the SAP NetWeaver PI system PID in your development environment corresponds to PIQ in your quality assurance environment. For example.2. TEST. How Does SAP NetWeaver PI Use the SLD? SAP NetWeaver PI has several SLD use cases: The SLD acts as a server for business system names (these have to be associated with the corresponding technical systems received from their data suppliers). you create transport targets for Integration Directory content transports.1 SAP NetWeaver Process Integration SAP NetWeaver Process Integration (SAP NetWeaver PI) is SAP's platform for process integration using the exchange of XML messages. you must make sure that all business systems (and the corresponding technical systems) that an SAP NetWeaver PI system communicates with are available in the SLD that is used by this SAP NetWeaver PI system. PROD) corresponds to which system in another environment. the corresponding systems from the source environment will be mapped to the target environment during the import. because business systems from QA are imported and mapped to business systems from PROD. because business systems from DEV are imported and mapped to business systems from QA.Planning Guide – System Landscape Directory 3. because business systems are not imported from other environments. December 2008 13 .

the GUIDs (globally unique identifier) of the software component versions have to be identical in both the source and the target SLD.2. Availability of the SLD is required at every restart of SAP NetWeaver PI so that the latter can load its caches. 3. How Does SAP NetWeaver PI Rely on SLD? SAP NetWeaver PI relies on SLD in the following way: During SLD downtime. access to the SLD is critical during startup and runtime. For Web Dynpro applications that use adaptive RFC calls. This information is stored in the SLD. To do so. The SLD provides the address for the transfer of adapter configuration data from the Integration Directory to the adapter cache.Planning Guide – System Landscape Directory For example. you can plan these cache refreshes in a normal production environment. PI caches might have to be refreshed during runtime (either initiated by Enterprise Services Builder tools after released changes or initiated manually to update the content).2 Web Dynpro Applications The SLD stores destination information for ABAP systems and Web services centrally. The Integration Repository of SAP NetWeaver PI requires information about products and software component versions. You have to make sure that this component repository data is available in every SLD that is used by SAP NetWeaver PI. Since unexpected restarts of an SAP NetWeaver PI system or parts of it might be required. all business systems and corresponding technical systems from the SLD that is used by PID must also be available in the SLD that is used by PIQ. so that the mapping mentioned above can be defined in the SLD of the QA environment. You could also create products and software component versions directly in the target SLD instead of transporting them from a source SLD. no end-to-end monitoring can be performed in the Runtime Workbench. the application systems will continue to use their old business system names. 14 December 2008 . If an SLD is down during this refresh.1 and higher or by using the manual export/import mechanism). you cannot create or change PI development objects (such as business systems and software component versions) in the SLD. However. During SLD downtime. This information is required by Web Dynpro applications to resolve adaptive RFC calls. the availability of the SLD is considered critical during runtime for SAP NetWeaver PI. we recommend that you transport this data (either by using the full automatic synchronization mechanism available in SAP NetWeaver 7. which is assured by transporting this data. ABAP application systems try to contact the SLD daily to update their business system names. Nevertheless. The SLD provides all systems and Adapter Engines for end-to-end monitoring in the Runtime Workbench of SAP NetWeaver PI.

train. Therefore. no data updates for J2EE components within your landscape are available in SAP Solution Manager. we strongly recommend that you run a local SLD in SAP Solution Manager. including interdependencies As central storage of development configurations required for development During downtime of the SLD. In addition. nor can you register any names.1 could also require a release upgrade of SLD to 7. For example. we strongly recommend that you do not use this local SLD in SAP Solution Manager as central runtime SLD. You would then require a (separate) central runtime SLD 7. there are different release strategies for SAP Solution Manager and SAP NetWeaver (and therefore the SLD).1 for this application. test.0. To provide these features. see SAP Note 1148028 and SLD Landscape Planning [page 26]. Note that the end-to-end root cause analysis scenario in SAP Solution Manager in particular stores connection data (Web Dynpro JCo destinations such as E2E_SMD_SM_DATA and E2E_SMD_SM_METADATA) in the SLD. and versions to be developed. as no runtime dependencies to this SLD exist.3 SAP NetWeaver Development Infrastructure SAP NetWeaver Development Infrastructure provides the environment for all processes of Java-based development and Java-based software life-cycle management. December 2008 15 .0 also comprises AS Java. you can use the SLD running on the SAP Solution Manager system as central SLD. the upgrade of an SAP application to SAP NetWeaver 7. end-to-end root cause analysis functions might be limited.4 SAP Solution Manager You can use SAP Solution Manager to implement. you can run this local SLD inside the SAP Solution Manager system itself. If you are not using SAP NetWeaver PI or Web Dynpro Java applications and also do not plan to do so in the near future. SAP NetWeaver Development Infrastructure uses the SLD: As name server for the reservation of development object names For a central definition of software. for instance an SLD. you cannot log on to the SAP NetWeaver Development Infrastructure. set up the SLD data suppliers of your SAP Solution Manager to send data to the central runtime SLD and configure automatic bridge forwarding from your central runtime SLD to the local SLD running inside SAP Solution Manager. software components.2. During SLD downtime. To ensure that the maintenance of SAP Solution Manager does not interfere with productive operations. which might be critical in the case of issues with production systems in your landscape that you want to analyze (especially if you want to perform root cause analysis for issues on your SLD system). Moreover.Planning Guide – System Landscape Directory 3. In addition. SAP Solution Manager requires a system data repository. Since SAP Solution Manager 7. a conflict might occur if you choose not to follow these recommendations and decide to use the local SLD running inside SAP Solution Manager 7. if you are using SAP NetWeaver PI or Web Dynpro Java applications in your system landscape. root-cause analyze and manage incidents of your SAP solution system landscape (open end-to-end application management). For more information. monitor. 3. products. Since the highest release of SAP Solution Manager is currently based on SAP NetWeaver 7. the SLD client (and not the SLD data supplier) of the upgraded application system would in this example no longer be able to use the SLD inside SAP Solution Manager. control change. maintain.1.0 also as a central runtime SLD.2. Therefore.

SAP NetWeaver Administrator retrieves landscape data from the SLD. the SLD is no longer required for SAP NetWeaver Administrator if you use the new work centers of SAP Solution Manager. the central services of SAP NetWeaver Administrator have been moved to a work center in SAP Solution Manager. It requires this information for central remote monitoring functions.sap. SAP will focus on optimizing the administrative work centers of SAP Solution Manager instead. or Adaptive Computing Controller. navigate to the Master Guide for your SAP NetWeaver release. As a result. It requires this information for its operation (that is. 3. Thus. 16 December 2008 . SAP will not develop this tool any further. SAP Solution Manager. operation. SAP NetWeaver Administrator. In SAP Solution Manager 7. SAP has decided to merge the central mode of SAP NetWeaver Administrator with the new work centers available in SAP Solution Manager 7. it can be used in an administrative context together with non-Java based administration tools.from there.6 Adaptive Computing Controller Adaptive Computing Controller enables users to control an adaptive computing landscape from a single point through observation.2.com/instguides SAP NetWeaver <Release> .5 SAP NetWeaver Administrator SAP NetWeaver Administrator offers a central entry point to administration and monitoring tasks for your whole SAP NetWeaver system landscape. Adaptive Computing Controller retrieves landscape data from the SLD. During SLD downtime. 3. For more information about SAP NetWeaver Process Integration. Nevertheless. stopping and changing resources). The local mode of SAP NetWeaver Administrator will not be modified: It is available for current and future releases of SAP NetWeaver. and dynamic resource distribution. Although the central mode of SAP NetWeaver Administrator will be still available for some time.2. only the monitoring functions of Adaptive Computing Controller are available.0 SP Stack 15 and higher.0 SP Stack 15 and higher. local SAP NetWeaver Administrator services do not require landscape data. no central administration of systems is possible. see the Master Guide – SAP NetWeaver on SAP Service Marketplace at service. SAP NetWeaver Development Infrastructure.Planning Guide – System Landscape Directory This enables you to clearly separate your management system (SAP Solution Manager) from the managed systems in your landscape because: SAP Solution Manager would not rely on an SLD running in the production environment No managed system would have runtime dependencies to SAP Solution Manager. During SLD downtime. starting.

several system landscape directories might be required if you want to isolate your production environment.3.3. By having an SLD dedicated for your production systems.2 Synchronization Options If you have several SLD instances in your landscape.1 Reasons to Have Several SLD instances There may be several reasons to have more than one SLD. we provide the following synchronization mechanisms: Full automatic synchronization Automatic message forwarding Sophisticated data export and import functions Transport of SLD objects with the enhanced Change and Transport System (CTS) December 2008 17 .3 Fundamental SLD Concepts 3. A very important reason to have several SLD instances is to provide improved availability of the information stored there. you can make sure that only administrators access your runtime SLD. you require a dedicated SLD to be able to provide different views on SLD data. 3. see SLD Clients [page 12]. In addition. Having more than one SLD also gives you the possibility to test content imports. For more information. whereas developers can use a design-time SLD. Synchronization means the interchange or forwarding of SLD data. To support the operation of several SLD instances. and patches first before performing them in the SLD used for your production environment. if you have geographically distributed locations with local administration groups that want to see only their local systems in the SLD. This information could be essential for applications running in your production landscape.Planning Guide – System Landscape Directory 3. For example. CIM data model updates. you might have to synchronize SLD data.

Synchronization takes place asynchronously.or higher could automatically forward all its content to an SLD running on AS Java 7. A ranking of connected SLDs defines which SLD takes the lead in case of a conflict. you can install a new SLD system (if required. performing upgrades.1 SP Stack 1 and higher. filtering of namespace content to be synchronized is not supported. 18 December 2008 . You can even use the full content synchronization to improve SLD availability for software life-cycle tasks (such as applying patches.3. but not the other way around. The full automatic SLD content synchronization is fully supported by AS Java 7.Planning Guide – System Landscape Directory 3. by means of DNS aliasing) to switch (temporary or permanently) to this new SLD. Additionally. this dramatically reduces manual synchronization effort. and relocating hardware). At present.1 Full Automatic Synchronization In SAP NetWeaver 7. This means that data delivered by data suppliers and data entered or changed manually in SLD can be propagated to another SLD automatically. an SLD based on 7. an SLD running on AS Java 7.0 SP Stack 12 and above can be used as the source system for unidirectional synchronization only.1 and higher. we provide a full automatic synchronization mechanism for all SLD data. due to network or system downtime) and synchronizes itself afterwards. The following figure shows a full automatic synchronization set up for two SLD instances: The following list shows important properties and features of the full automatic synchronization of SLD content: You are able to set up this synchronization as either unidirectional or bidirectional. Therefore.2. Depending on your use case. content synchronization is only possible for the whole content of participating namespaces.1. on a higher release) in parallel to an SLD with a lower release version and use content synchronization and host name virtualization (for example. it is now possible to define the required transport topology and perform automated synchronization of all content changes without regular manual operations. Reconciliation of conflicts (due to conflicting parallel changes) is done automatically: no user interaction is required.0 SP Stack 12. The communication for this synchronization takes place by using the HTTP protocol. That is. To do so. so that a system can be temporary unreachable (for example.

Therefore. The same restriction applies for data written by other applications such as SAP NetWeaver PI or SAP Solution Manager. DNS aliases cannot be used for an immediate. synchronous conversion of the links.3. the original sender will write an error message in its log file that the data received by automatic forwarding is already contained in its local SLD. Therefore.2 Automatic Forwarding of Landscape Data To keep different SLD instances informed about changes to data reported by SLD data suppliers. business systems required for SAP NetWeaver PI. December 2008 19 . The following landscape data can be synchronized with automatic forwarding: ABAP system data (transaction RZ70) Java system data (SLD data supplier service) Host data (SAPOSCOL) Other system data (sldreg) In SAP NetWeaver 7. or name reservation data) cannot be forwarded automatically with this mechanism and stays within the local SLD only. In addition.Planning Guide – System Landscape Directory Depending on the configuration and the number of DNS servers. this approach will not be suitable for all requirements and you maybe have to complement the automatic forwarding with other synchronization mechanisms (such as manual export/import).0 SP Stack 10 or a lower release/SP Stack version. If your SLD instances run on SAP NetWeaver 7. Although the original sender does not forward data again (after the original sender received the data from the other SLD). With automatic forwarding.0 SP Stack 11 and higher. 3. switching a DNS alias may take some time (hours or days). the SLD allows direct server-to-server synchronization. you get the flexibility to run several SLD instances in your system landscape with little manual effort if full automatic synchronization can not be used. with automatic forwarding. circular forwarding is fully supported. you will have manually update the component information and the CIM model from SAP Service Marketplace for every single SLD (for more information. see SAP Note 669669). Any changes and entries that you entered manually in the SLD (for example. we do not recommend that you set up a circular exchange of data between two or more SLD instances with automatic forwarding. component repository extensions. Since only landscape data received from SLD data suppliers is forwarded automatically. you can configure the SLD bridge to forward data to other SLD instances. In addition. further caches are often implemented for the IP addresses in the application systems.2.

20 December 2008 . and full automatic synchronization can not be used (because your SLD instances do not run on SAP NetWeaver 7. concerning availability) or if you only have a small number of manual changes to your SLD data that have to be transported manually. you can use the export/import function in the SLD to manually synchronize them.2.3. SLD content is divided into the following three categories: Landscape data (LD) Component repository data (CR) Name reservation data (NR) The export and import functions of SLD support the transport of SLD content for each sub-category as well as for all data. patch levels. You can then use this master SLD to update the other SLD instances. 3. Export and import provides the best flexibility while it may require considerable operational effort. automatic forwarding works independently of releases. only changes are exported: these are known as ‘delta exports’. To ensure proper distribution of data.1 or because you do not want to synchronize all SLD data). After an initial ‘full export’. Therefore.3 SLD Export and Import Functions If several SLD instances have to contain a consistent view of data not delivered by data suppliers. We recommend that you transport all three categories together (select export line: ALL in SLD administration). Simple export and import functions allow you to export data from one SLD and import it to another SLD manually. you must designate one SLD as the master SLD. it is only recommended if you have corresponding requirements (for example. and installed CIM data models and SAP Component Repository content versions of the involved SLD instances.Planning Guide – System Landscape Directory The following figure shows automatic forwarding set up for two SLD instances: SAP System SAP System Automatic forwarding of landscape data SLD SAP System SLD SAP System SAP System Since the SLD bridge forwards data without interpreting or changing it.

0 SP Stack 14 and higher. and SLD objects). you simplify your transport management and avoid inconsistent system states as objects that belong together get transported together as one unit. export/import will still work as long as you have imported the same CIM data model and SAP CR content versions (downloaded from SAP Service Marketplace: for more information. and products. December 2008 21 . business systems. 3.0 SP Stack 12 and higher. you have to import the SAP CR delta archives into the master SLD only. If you have SLD instances with different release versions or patch levels in your system landscape. such as: Objects from the SAP NetWeaver usage type EP (Enterprise Portal Archives) Objects from the SAP NetWeaver usage type PI (PI transport files) Objects from the SAP NetWeaver usage type DI (such as software component archives and development component archives) In SAP NetWeaver 7. see SAP Note 669669) in each of these SLD instances. This enables you to manage transports between both ABAP and non-ABAP SAP systems in a central CTS. you can also transport the following SLD objects with the enhanced CTS: technical systems. The objects are transported in transport requests along the transport routes defined between systems in CTS.3. you also update the component data delivered by SAP. the existing Change and Transport System (CTS) in SAP NetWeaver Application Server ABAP has been enhanced so that you can now use the transport functions in Transport Organizer and Transport Management System to also transport non-ABAP objects. By synchronizing different updates (such as the changes performed as part of PI development comprising ABAP. Java. software components.2.4 Transport of SLD Objects with the Enhanced CTS In SAP NetWeaver 7. Thus.Planning Guide – System Landscape Directory The following figure shows the export and import of SLD data from one SLD to another: SAP System SAP System Master SLD SLD SAP System Export and import of SLD data SAP System SAP System When you transport all SLD data from one SLD instance to another.

this could be a valid alternative for the export/import functions of SLD – especially if you already use enhanced CTS already for other transports in your landscape which contain SLD objects (such as transports occurring in the context of SAP NetWeaver PI development).Planning Guide – System Landscape Directory Since you can use enhanced CTS to transport selected SLD objects on request. However. you do not set up full automatic synchronization from SLD A to SLD B and configure automatic forwarding from SLD A to SLD B because both mechanisms would synchronize landscape data. all SLD data) SLD 5 on AS Java 7. use different synchronization mechanisms for different synchronization paths or for different SLD data in your SLD landscape). you could supplement automatic forwarding with regular export/import of manually entered data from SLD A to SLD B). you must not use several synchronization mechanisms for the same SLD data on the same synchronization path (for example.5 Interplay of the SLD Synchronization Mechanisms The synchronization mechanisms described above have different characteristics. 3. If required.1 or higher SAP System SAP System Full automatic synchronization from SLD 2 to SLD 4 (unidirectional. all SLD data) SLD 2 on AS Java 7. all SLD data) Full automatic synchronization between SLD 4 and SLD 5 (bidirectional. Nevertheless.1 or higher SAP System SLD 3 on AS Java SAP System SAP System 22 December 2008 .3.2. you can also use several of these mechanisms to synchronize your SLD landscape (that is. only selected SLD data) on AS Java 7. The following figure shows a system landscape where different synchronization mechanisms are used in parallel: SLD 1 on AS Java Automatic forwarding of data supplier data from SLD 1 and SLD 2 (unidirectional.0 SPS 12 SLD 4 SAP System Export/import between SLD 2 and SLD 3 (unidirectional.

only data reported by SLD data suppliers). You can also export all SLD data (including SAP CR delta archives).1 or higher If only landscape data reported by SLD data suppliers has to be synchronized If your SLD instances do not run on AS Java 7. this data is forwarded to other SLD instances) Manual procedure either incremental or selective If your SLD instances do not run on AS Java 7. unior bi-directional Automatic forwarding (whenever the SLD bridge receives data from an SLD data supplier. If enhanced CTS is already used for other transports in your landscape which also include SLD objects (such as in the context of SAP NetWeaver PI development).1 or higher (source SLD can also run on AS Java 7.1 or higher and more data has to be synchronized than just the data covered by automatic forwarding If only a small amount of SLD data has to be synchronized on an irregular basis Provides best flexibility but may require considerable operational effort Enhanced Change and Transport System (CTS) Transportable SLD objects: technical systems. business systems. data entered manually. SAP CR content updates.0 SP Stack 12 or higher) Manual export/import You can choose the SLD content of each subcategory (LD. and products. Note that all data including the CIM model is active in the target SLD immediately after the propagation. December 2008 23 . such as single business systems or software components. How? Automatic propagation of all changes in the source system When to use this mechanism? If your SLD instances run on AS Java 7. Manual procedure using the enhanced CTS If you want to be in control when specific SLD objects are transported. Automatic forwarding Specific landscape data (that is. CR. NR). CIM model). software components. unior bi-directional.Planning Guide – System Landscape Directory The following table provides an overview of the different synchronization mechanisms in the SLD: Synchronization Mechanism Full automatic synchronization What is synchronized? Always all SLD data in an SLD namespace (data reported by SLD data suppliers.

different SP Stacks of SLD client and server are supported. however. Between the SLD and SLD data suppliers An SLD data supplier is used by a system to report landscape data to the SLD (write access only).1 Release Compatibility between the SLD and SLD Data Suppliers It is possible to connect an SLD data supplier of a system with a higher release to an SLD running on a system with a lower release. Within a release. That means that an SLD running on AS Java 7.3. new SLD parameters sent by a new data supplier might not get stored in an SLD running on a system with an older release). we recommend that the SLD runs on a system with the highest SAP NetWeaver release in your landscape.3.0 system to send data to an SLD running on SAP NetWeaver 2004.3 Release Compatibility You have to consider three kinds of interdependencies concerning releases: Between SLD instances with regard to synchronization (if you run several SLD instances in your landscape) Full automatic synchronization Full automatic SLD content synchronization is available in AS Java 7. Therefore. Between the SLD and SLD clients An SLD client is a system that uses data that is stored in the SLD (read/write access). 24 December 2008 . If you nevertheless want to connect an SLD data supplier with a higher release to an SLD with a lower release. Automatic forwarding Since the SLD bridge forwards data without interpreting or changing it.0 SP Stack 12 or higher could automatically forward all its content to an SLD running on AS Java 7. The reason for this recommendation is that it might be that SLD data that was introduced with a new release is ignored if received by an SLD running on a system with an older release (that is. Additionally. Export/import: If you have SLD instances with different release versions or patch levels in your system landscape.0 SP Stack 12 and above can be used as the source system for unidirectional synchronization only. and installed CIM data models and SAP CR content versions of the involved SLD instances. For example. we do not recommend that you do so. patch levels. make sure that you have imported a new CIM data model version to the SLD with the lower release and check the SLD content regularly. For example.3. but not the other way around. an SLD instance based on 7. you can configure the data supplier of an SAP NetWeaver 7. we do not recommend that you do so. automatic forwarding works independently of releases. the data supplier of an SAP system sends landscape data to the SLD. export/import will still work as long as you have imported the same CIM data model and SAP CR content versions (downloaded from SAP Service Marketplace – for more information.1 SP Stack 1 and higher.Planning Guide – System Landscape Directory 3. Instead. you can use any patch sequence within a release for the systems in your landscape on which your SLD server and your SLD data suppliers run. For example. see SAP Note 669669) in each of these SLD instances. a Web Dynpro application is an SLD client that reads data from the SLD for adaptive RFC calls. 3. however.1.

Planning Guide – System Landscape Directory 3. an SAP NetWeaver 7. using an SLD running on SAP NetWeaver 2004 for SAP Solution Manager 7. which you can find on SAP Service Marketplace at service. see SAP Note 954820 (Compatibility of SLD in the system landscape).3. different SP Stacks of SLD clients and SLD instances are supported. Within a release. Therefore. the following SAP Notes (and related SAP Notes) provide information about how to split or merge SLD instances: Make sure that you have the most up-to-date version of each SAP Note.com/notes.4 How You Can Handle Possible Changes to Your SLD Strategy If you have to change your strategy in the future for any reason (for example. you can use any patch sequence for your landscape with SLD and SLD client applications within a release.2 Release Compatibility between the SLD and SLD Clients It is not generally supported that an SLD client with a higher release use an SLD running on a lower release (for example. 936318 935245 Splitting an SLD instance Importance of “Object Server” SLD parameter Reduce the number of System Landscape Directories (SLD) 720717 December 2008 25 . This SAP Note describes manual actions you have to perform for SAP NetWeaver PI if you merge multiple SLD instances.3. For example. For more information about released combinations of SLD server and SLD client releases.sap. which could be required to split or merge an SLD. This SAP Note describes the consequences of changing the object server.0). We recommend that SLD instances run on a system with the highest SAP NetWeaver release in your landscape. 3. Whether this is supported or not depends on the actual client application.0 based on SAP NetWeaver 7. you started with one central SLD and now want to extend this approach by adding a second central SLD for your non-productive environment). This SAP Note describes how you can split an SLD into two or more instances. SAP Note Number 935474 Title Grouping SLD instances Description This SAP Note describes how you can merge two SLD instances by importing the content of one SLD into another SLD.0 Process Integration system can be the SLD client of an SLD running on SAP NetWeaver 2004 because this is listed in the SAP Note mentioned above.3.

Depending on the configuration and the number of the DNS servers. on a management system. switching a DNS alias may take some time (hours or days). or in case of technical problems. In addition.Instance ID needs to be identical For details see SAP Note 764393. By doing so. To enable an easy switch between SLD instances using DNS alias do as follows: .0 Support Package Stack 12 or higher. it is possible to switch SLD hosts easily. How many SLD instances to run in your landscape (your logical SLD landscape) 2.1 Recommendations for SLD Landscapes This section provides recommendations about how to set up an SLD in your system landscape: SLD Landscape: General Recommendation [page 26] This landscape is our general recommendation. further caches are often implemented for the IP addresses in the application systems. In all cases. upgrades. It will help you to make the following decisions: 1. which might be required for maintenance (updates). For example. Most of the SLDs discussed in this section are logical systems until you decide where to physically run them as discussed in section Where to Run SLD in Your System Landscape [page 42] (only exception is the SLD running locally in the SAP Solution Manager system). you could install a new AS Java system with a higher release. SLD Landscape: Possible Exceptions [page 37] This section contains information about further SLD landscape approaches that are only applicable for specific use cases. or on an application system) – including information about the sizing requirements of an SLD.4 SLD Landscape Planning This section provides you with recommendations about how to setup an SLD landscape. SLD Landscape: Reasonable Alternative [page 36] This landscape is an extension of the general recommendation SLD landscape for specific use cases or customer scenarios.4. With the new full automatic synchronization option available in SAP NetWeaver 7.1 and higher. import the data of your current SLD to the new SLD and switch to this new SLD.HTTP(s) ports need to be identical (this can be changed later) . 26 December 2008 . synchronous conversion of the links. if your existing SLD runs on SAP NetWeaver 7. we recommend that you use DNS aliases to address the SLD. 3. Where to run your SLD instances (either as dedicated SLD systems. It is the best choice for the majority of typical SLD landscape use cases and is accepted by a wide base of customers. DNS aliases cannot be used for an immediate. This way. configure an SLD on this new system. the synchronization of your new SLD with the existing one is also very easy to perform. you have upgraded to a higher release with minimal SLD downtime.Planning Guide – System Landscape Directory 3. Therefore.

For these non-production systems.1. there are non-productive systems in a non-productive environment on the left including one or several SAP NetWeaver Development Infrastructure (NWDI) systems. such as to which SLD the SLD clients connect. you will learn about different SLD-relevant aspects of the recommended landscape. One recommendation if you are using SAP NetWeaver PI and/or Web Dynpro Java applications or plan to do so in the near future. You should treat the recommended landscape as proposal that we consider as a general approach for most SLD use cases – and even in those cases. run your production systems against the SLD running on SAP Solution Manager: In this landscape. such as SAP Solution Manager. In the upper part. there are management systems.1 SLD Landscape: General Recommendation This section provides general recommendations for SLD landscapes based on the SLD clients you use in your landscape: One recommendation if you are not using SAP NetWeaver Process Integration and/or Web Dynpro Java applications today and also do not plan to do so in the near future.Planning Guide – System Landscape Directory 3. you should use this landscape only as a starting point for your SLD landscape discussion. December 2008 27 .4. There. and finally how you could extend the landscape according to your specific needs.1 SLD Landscape: General Recommendation – Landscapes without SAP NetWeaver PI and without Web Dynpro Java Applications If neither SAP NetWeaver usage type PI nor Web Dynpro Java is used and you do not plan to use them in the near future either. Pay attention that most of the SLDs discussed in this section are logical systems until you decide where to physically run them as discussed in section Where to Run SLD in Your System Landscape [page42] (only exception is the SLD running locally in the SAP Solution Manager system).1. you run your central SLD on the SAP Solution Manager system. 3.1. you use a central design-time SLD. how the different SLD instances synchronize data. Starting from a picture of the overall landscape. how the SLD data suppliers must be set up.4.

This landscape also corresponds to our long-term SLD landscape recommendation. For these production systems.Planning Guide – System Landscape Directory On the right. there is a environment comprising production systems (without SAP NetWeaver PI and without Web Dynpro Java applications). 28 December 2008 . you use the central SLD on the SAP Solution Manager system. In addition. front-end applications (such as SAP NetWeaver Developer Studio) complete the landscape.

you can create and administrate all SLD data supplier users in the user management of one SLD (because each SLD data supplier must have a dedicated user in the SLD).Planning Guide – System Landscape Directory SLD Data Suppliers The following explains how to set up the SLD data suppliers in this recommended landscape. In addition.) Other systems (prod. this has the advantage that you can use one unified system configuration for all SAP systems in your landscape. the SLD data suppliers of all SAP systems register with the SAP Solution Manager’s SLD: Front Ends SAP NetWeaver Developer Studio Management Systems SAP Solution Manager SLD Data Supplier communication (sending of technical system data) SLD SLD (design-time) SLD NWDI Other systems (non-prod. Altogether. December 2008 29 . As shown in the following figure.) Managed Non-Production Systems Managed Production Systems Pay attention that all SLD data suppliers are configured against the SLD of the SAP Solution Manager system.

30 December 2008 .) Other systems (prod. In addition. Access to the production systems can be restricted to technical administration users running the production systems. products. NWDI only uses the design-time SLD. SAP Solution Manager and all production systems use the central SLD on the SAP Solution Manager system. you have separated and safeguarded the production systems.) Managed Non-Production Systems Managed Production Systems In this way. you have to use local SLDs for these use cases or an additional runtime SLD as outlined in the next session. If you should change your strategy in the future and decide to use SAP NetWeaver PI or Web Dynpro Java applications. and software components in the Java development context. as there must be no runtime dependency to the SAP Solution Manager system.Planning Guide – System Landscape Directory SLD Clients The following explains how the SLD instances are used. no runtime dependencies exist to the central SLD running on the SAP Solution Manager system. On the other hand. The design-time SLD is used for all other SLD client systems (such as all DEV and QA systems including all NWDI systems and all SAP NetWeaver Developer Studio instances) and for the definition of software. As you are not using SAP NetWeaver PI or Web Dynpro Java applications and also do not plan to do so in the near future. development and QA systems. as well as the respective staff for development and QA are only allowed to access the design-time SLD. The following figure shows the corresponding SLD client connections that provide the information about which SLD is used by which application as described above: Front Ends SAP NetWeaver Developer Studio Management Systems SAP Solution Manager SLD client access (retrieve/write data) SLD SLD (design-time) SLD NWDI Other systems (non-prod.

December 2008 31 . the SAP Solution Manager’s SLD automatically forwards all technical landscape data to the design-time SLD as shown in the following figure: Front Ends SAP NetWeaver Developer Studio Management Systems SAP Solution Manager Synchronization communication between SLDs (forwarding of SLD data) SLD Automatic Forwarding of all technical landscape data SLD (design-time) SLD NWDI Other systems (non-prod.) Other systems (prod.Planning Guide – System Landscape Directory SLD Synchronization To enable the interplay between the two SLD instances.) Managed Non-Production Systems Managed Production Systems No synchronization would be required from the design-time SLD to the central SLD.

) Other systems (prod. In the upper part. there are non-productive systems (both SAP NetWeaver Process Integration and other application systems) in a non-productive environment on the left including one or several SAP NetWeaver Development Infrastructure (NWDI) systems.1. On the right.2 SLD Landscape: General Recommendation – Landscapes with SAP NetWeaver PI and/or Web Dynpro Java Applications The following figure shows our general recommendation for an SLD landscape. front-end applications (such as SAP NetWeaver Developer Studio) complete the landscape. such as SAP Solution Manager. we assume that in the landscape SAP NetWeaver usage type PI is present and/or that Web Dynpro Java is in use as an SLD client: Front Ends SAP NetWeaver Developer Studio Management Systems SAP Solution Manager SLD SLD (design-time) SLD SLD SLD (runtime) NWDI PI (non-prod. there is a second environment comprising production systems. there are management systems. you use a central designtime SLD. 32 December 2008 . you run a third SLD locally for SAP Solution Manager. For these non-production systems.) PI (prod.) Other systems (non-prod. you use a central runtime SLD. There. In addition. For these production systems.Planning Guide – System Landscape Directory 3.) Managed Non-Production Systems Managed Production Systems In this landscape. In this case.4.1.

) Managed Non-Production Systems Managed Production Systems Pay attention that also the SLD data suppliers of the SAP Solution Manager system are configured against the runtime SLD.) Other systems (prod. the SLD data suppliers of all SAP systems register with the runtime SLD: Front Ends SAP NetWeaver Developer Studio Management Systems SAP Solution Manager SLD Data Supplier communication (sending of technical system data) SLD SLD (design-time) SLD SLD SLD (runtime) NWDI PI (non-prod. this has the advantage that you can use one unified system configuration for all SAP systems in your landscape.) Other systems (non-prod. As shown in the following figure. you can create and administrate all SLD data supplier users in the user management of one SLD (because each SLD data supplier must have a dedicated user in the SLD). December 2008 33 .) PI (prod. Altogether. In addition.Planning Guide – System Landscape Directory SLD Data Suppliers The following explains how to set up the SLD data suppliers in this recommended landscape.

The following figure shows the corresponding SLD client connections that provide the information about which SLD is used by which application as described above: Front Ends SAP NetWeaver Developer Studio Management Systems SAP Solution Manager SLD client access (retrieve/write data) SLD SLD (design-time) SLD SLD SLD (runtime) NWDI PI (non-prod. On the other hand. you have separated and safeguarded the production systems. and software components in the Java development context. In addition.) Other systems (non-prod. products. SAP Solution Manager uses its local SLD. The runtime SLD is used for production purposes. development and QA systems.) Other systems (prod. 34 December 2008 .Planning Guide – System Landscape Directory SLD Clients The following explains how the SLD instances are used. NWDI only uses the design-time SLD. as well as the respective staff for development and QA are only allowed to access the design-time SLD.) Managed Non-Production Systems Managed Production Systems In this way.) PI (prod. Access to the production systems can be restricted to technical administration users running the production systems. whereas the design-time SLD is used for all other SLD client systems (such as all DEV and QA systems including all NWDI systems and all SAP NetWeaver Developer Studio instances) and for the definition of software.

products. For more information about the single synchronization mechanisms in the SLD. To do so. Alternatively.) Managed Non-Production Systems Managed Production Systems In addition.) Other systems (non-prod. either export/import or transport SLD objects with the enhanced Change and Transport System. and software component versions required by SAP NetWeaver PI) from the design-time SLD to the runtime SLD on demand. December 2008 35 . the runtime SLD automatically forwards all technical landscape data to the design-time SLD and to the SLD of SAP Solution Manager as shown in the following figure: Front Ends SAP NetWeaver Developer Studio Management Systems SAP Solution Manager Synchronization communication between SLDs (forwarding of SLD data) SLD Automatic Forwarding SLD (design-time) SLD of all technical landscape data SLD SLD (runtime) Selective Transport of individual data NWDI PI (non-prod.) PI (prod.) Other systems (prod. you can use the full automatic synchronization option for any of the synchronization mechanisms described above. see Synchronization Options [page 17]. you transport individual objects (such as business systems.Planning Guide – System Landscape Directory SLD Synchronization To enable the interplay between the three SLD instances.

) ABAP (Runtime) Managed Non-Production Systems Managed Production Systems For this additional local SLD. Pay attention that most of the SLDs discussed in this section are logical systems until you decide where to physically run them as discussed in section Where to Run SLD in Your System Landscape [page 42] (only exception is the SLD running locally in the SAP Solution Manager system).) Other systems (prod. This means that you can set up additional local SLD instances. You configure the central runtime SLD to automatically forward all technical landscape data to all other SLD instances in your landscape (including the additional local SLD used for the Web Dynpro application).4. Another use case could be to further separate your environments by running separate SLD instances for your development environment and for your test environment in addition to the runtime SLD. for example to improve the availability of SLD data for certain use cases (such as for Web Dynpro Java applications using adaptive RFC calls or for SAP NetWeaver PI).) PI (prod. The Web Dynpro application then uses the local SLD to operate. The following figure shows the recommended SLD landscape enhanced by a local SLD for a Web Dynpro application: Front Ends SAP NetWeaver Developer Studio Management Systems SAP Solution Manager SLD Data Supplier communication (sending of technical system data) Synchronization communication between SLDs (forwarding of SLD data) SLD client access (retrieve/write data) SLD SLD (design-time) SLD SLD (runtime) SLD Java (Runtime) SLD SLD (local) NWDI PI (non-prod. 36 December 2008 . you also configure the SLD data suppliers of the ABAP backend runtime system and of the Java Web Dynpro runtime systems to register with the central runtime SLD.1.Planning Guide – System Landscape Directory 3.2 SLD Landscape: Reasonable Alternative The recommendation provided in the previous section offers a generic approach because you can extend it further according to your requirements.) Other systems (non-prod. you would set up the following connections: Just like all other SAP systems in your landscape.

including all sub networks.3 SLD Landscape: Possible Exceptions Since the general recommendation for an SLD landscape in the previous sections cannot cover all requirements.4. easier administration. you may have to consider different SLD landscape approaches that are only useful for specific use cases. you might face high availability requirements (depending on your SLD use cases) and all user groups (such as developers and administrators) will work within the runtime SLD and view/access the same SLD and the same SLD data.Planning Guide – System Landscape Directory 3. The advantages of using a single system landscape directory for the entire system landscape are consistent data. we consider that this approach is useful for specific use cases only. One Single Central SLD The easiest setup is to have a single SLD that acts as a central information provider for the enterprise system landscape. for example for very small landscapes with no critical application relying critically on SLD data. The following figure shows a corresponding example: Extranet Intranet Intranet Intranet SAP System SAP System SLD SAP System SAP System SAP System SAP System December 2008 37 . share a single SLD that contains information about the whole system landscape. Since we consider that the drawbacks of this single-SLD approach outweigh the advantages.1. All systems in your system landscape. Pay attention that the SLDs discussed in this section are logical systems until you decide where to physically run them as discussed in section Where to Run SLD in Your System Landscape [page 42]. Nevertheless. and lower operating expense. the testing of changes to the SLD or SLD data is either not possible at all or is restricted. In addition.

Landscape data (or all SLD data) from all divisions accumulates as the complete system landscape in the headquarters’ SLD. you forward the required SLD data from the sub-divisions to a master SLD for the hosting provider. The following figure shows a hosting scenario with separate customer system landscapes. The local SLD instances of the divisions serve all local needs. you can use distributed SLD instances as an alternative to our general recommendation. Thus. To achieve this. The hosting provider itself must have access to the system landscape of all customers. However. you can also run several distributed SLD instances in your landscape as described below: Hierarchical Organization This organizational form incorporates several fully separated divisions headed by the headquarters. again consider our general recommendations for the SLD landscape described in the previous sections.Planning Guide – System Landscape Directory Distributed SLD Instances in Special Circumstances If you have special requirements. the effort and cost to operate such an SLD landscape might increase due to greater hardware consumption and additional operation tasks (such as manual model and content updates in all SLD instances and regular synchronization activities for the additional SLD instances). Hosting Provider SLD Customer 1 Master SLD Customer 2 Forwarding of required SLD data SAP System SAP System SLD SLD Local SLD Setup (Customer 1) SLD SLD Local SLD Setup (Customer 2) SAP System SAP System SAP System 38 December 2008 . Besides the recommended SLD landscapes shown in the previous sections. you can use a hierarchical organization of several SLD stages to create different views of your landscape. Each customer landscape incorporates its own SLD setup containing data about this customer’s landscape only. For the local SLD setups.

as shown in the following figure: SAP System SAP System SLD SLD Local SLD Setup SAP System SLD SLD Local SLD Setup SAP System SAP System For the local SLD setups.Planning Guide – System Landscape Directory Fully-Separated Organizations (Several Standalone SLD instances) You can use several local SLD setups for a fully-separated management of data that is independent of each other. December 2008 39 . again consider our general recommendations for the SLD landscape described in the previous sections.

again consider our general recommendations for the SLD landscape described in the previous sections. The following figure shows a corresponding example: SAP System SAP System Synchronization SLD SLD Local SLD Setup SAP System SLD SLD Local SLD Setup SAP System SAP System Another example is the use case of a distributed development environment. For the local SLD setups. Forwarding landscape data or full automatic synchronization of all SLD data can be used to provide global back-end access in distributed Web Dynpro development landscapes. The availability of local SLD instances in each region enables quick responses and avoids network traffic. it is essential for each regional development department to have SLD data locally available.Planning Guide – System Landscape Directory Several Coupled SLD Landscapes Global or widely distributed IT landscapes might require more than just a central runtime SLD. Nevertheless. Large and multinational companies tend to spread development departments all over the world. It is then expected that SLD data is locally available but that it provides more than just a local view. 40 December 2008 . This may be due to cost effectiveness (offshoring) or organizational reasons. You can achieve this by coupling several distributed SLD setups that exchange all or just specific SLD data.

Planning Guide – System Landscape Directory The following figure shows the propagation of SLD data from the SLD setup in region 2 to the SLD setup in region 1: Extranet (World Wide Company Network) Region 1 Back-End System Propagation of SLD data for back end systems (either automatic forwarding or full automatic synchronization) Region 2 Back-End System SLD SLD Local SLD Setup (Region 1) SLD SLD Local SLD Setup (Region 2) PCs running IDE PCs running IDE December 2008 41 .

Availability requirements might require a highavailability setup . it is easier to plan the downtime of a standalone application system. the following points can act as a basis for your decision-making: Dedicated/standalone SLD system: This is the most flexible way to run an SLD.Planning Guide – System Landscape Directory 3. Factor + Flexibility Explanation It is easier to plan and perform changes in your system landscape – for example. you should now decide where to run the single SLDs.lst that is located at: /usr/sap/<SID>/SYS/exe/uc/<os>/scs. Relevant Aspects To decide where to run your SLDs in your landscape. . gwrd to the sapcpe file scs. 42 December 2008 . a high-availability setup might be required for this SLD system. Therefore. In a normal landscape.for more information.2 Where to Run SLD in Your System Landscape After having identified the number of SLDs to run in your landscape.4. see SAP Note 1064290. by running a central runtime SLD on your production SAP NetWeaver PI system. because SLD is backward-compatible. you might have realized a mix of these options (for example. applications using this SLD are not affected by the upgrade of the corresponding SLD system. we recommend that you start an additional Gateway service (used as the Standalone Gateway required for data suppliers of AS ABAP systems to send data to SLD) for the Java SCS instance as follows: a) Add an entry to the start profile START_SCS<inst_no. You have to operate and maintain an additional system. and a local SLD on your SAP Solution Manager system).>_<virtual_host>. for example: #--------------------------------------------------------------# Start SAP gateway service #--------------------------------------------------------------_GW = $(DIR_EXECUTABLE)\gwrd$(FT_EXE) Start_Program_05 = local $(_GW) pf=$(_PF) b) Add gwmon.lst c) Check the enqueue replication port settings . because you do not have to consider SLD availability requirements for other applications using this SLD as well. In addition. There are different options and each option has different advantages and disadvantages.Cost Depending on the availability requirements you would face for this dedicated SLD. If you use a high-availability setup for your dedicated SLD system. you have achieved release independency between your SLD system and the systems using this SLD. a central design-time SLD on a non-production SAP NetWeaver PI system.

This would then run without dependencies to any applications in the system (for example.1 system. because the application is down as well. see the Master Guide – SAP NetWeaver available in SAP Service Marketplace at service. a design-time SLD on a non-production SAP NetWeaver PI system. the SLD is also available. If an upgrade to a required release is not yet available for the application. + Cost You do not have to operate and maintain an additional system. we recommend the following: If you use SAP NetWeaver PI. This is the easiest and cheapest way to run an SLD. read SAP Note 1031321). this runtime SLD should run on the PROD CE system An alternative option would be to run a dedicated runtime SLD on a standalone system. Recommendation for the Landscape of our General Recommendation If you have a central SLD on SAP Solution Manager. (For the use of a local SLD on an SAP NetWeaver PI 7. if you plan the downtime of an application system.Inflexibility Explanation Planning and performing changes is more complicated – for example. Factor . In addition. you have to consider SLD availability requirements of other applications relying on this SLD as well. the SLD is not available. you have to postpone the upgrade or move the SLD to a different system. but this would not be critical for the application. the SLD would automatically profit from a possible highavailability setup of the application. + Improved availability for one application Availability of the SLD is the same as the application – if the application system is up. the SLD could be updated/upgraded without updating/upgrading the application also).the application would be affected by upgrade requirements of your SLD and the other way around. If you require a runtime SLD in addition to the SLD on SAP Solution Manager and to the design-time SLD (for example for a productive PI system). If customer uses SAP NetWeaver CE 7. SAP NetWeaver PI) or with a central shared service (such as SAP Solution Manager). For more information about shared services (such as SAP Solution Manager).1. this runtime SLD should run on the PROD PI system.sap. Example The following figure shows an example landscape based on our general landscape recommendation with three SLD instances (a runtime SLD on your production SAP NetWeaver PI system. but not PI. and a local SLD on your SAP Solution Manager system): December 2008 43 . If the system is down.com/instguides SAP NetWeaver <Release> and navigate to the Master Guide for your SAP NetWeaver release. there is a release dependency between the SLD and the application . In addition.Planning Guide – System Landscape Directory Running SLD integrated with an SAP application or SAP NetWeaver system (for example. you only have to decide where to run your design-time SLD (here we assume no productive PI system is used nor Web Dynpro applications).

For example. your developers would only use the SLD running in the non-productive environment.) incl. SLD Other application systems (prod. You have a release dependency between the local SLD and SAP Solution Manager.) Other application incl. No productive system relies on the availability of the SLD running inside SAP Solution Manager. SAP Solution Manager does not rely on an SLD running in the productive environment. You would have a clear separation between your management system (SAP Solution Manager) and the managed systems in your landscape. because SAP Solution Manger uses a local SLD – this is especially crucial for end-to-end root cause analysis functions of Solution Manager Diagnostics if problems arise with your runtime SLD/production PI system. you profit from a possible high-availability setup of your production PI system that would also increase availability of the central runtime SLD for other use cases.Planning Guide – System Landscape Directory Front Ends SAP NetWeaver Developer Studio Management Systems SAP Solution Manager SLD SLD NWDI PI (non-prod. You profit from increased availability for SAP Solution Manager. SLD systems (non-prod. Possible downtimes of your PI system would affect other applications that use this SLD as well. If an upgrade to a required release is not yet available for SAP Solution Manager.) Non-Production Environment Here is an assessment of this example: Production Environment You profit from increased availability for your critical PI processes. you cannot profit from new features for your local SLD. you have to upgrade your PI system. In addition. If you want to profit from new SLD features only available with a higher SAP NetWeaver release. You have a clear separation between your non-productive and productive environments.) SLD PI (prod. You have a release dependency between the SLD and PI. because the production PI system uses a local SLD. 44 December 2008 .

For more information. see SAP Service Marketplace at service. see SAP Service Marketplace at service.2 System Design We recommend that you run the SLD on a non-clustered system.3.com/instguidesnw. we assume the following maximum processing times for the SLD (based on the hardware listed above): 10 seconds for data received from the data supplier of an ABAP system 30 seconds for data received from the data supplier of a Java system December 2008 45 . For example. and on up-to-date hardware for the other parts as well (such as disks and so on).3 Sizing Requirements of a System for SLD The following sections provide relevant considerations to size a system used for the SLD.3. be aware that all applications running shared on this system will compete for hardware resources.3. 3. 3. If you run the SLD for SAP NetWeaver 2004 or SAP NetWeaver 7.1 Hardware As a starting point. see SAP Note 825116.4.3 Estimation of System Load The following rule of thumb helps you to judge the hardware requirements based on the load in an SLD caused by SLD data suppliers. we recommend that you run the SLD for SAP NetWeaver 7. If you plan to run the SLD on a system shared by several applications.0 on a host with at least a 64-bit dual core CPU with not less than 4 GB of RAM. make sure you disable the SLD cache.4. More information: For hardware recommendations. This is normally suitable for most SLD use cases. 3.4.sap. To compute the data received by one SLD data supplier.Planning Guide – System Landscape Directory 3.4. For general sizing of SAP NetWeaver.0 on a clustered system. Running the SLD on hardware that is more powerful should reduce the processing times assumed below for the estimation of the system load.com/sizing. we recommend that you stick to the recommendation for an AS Java system given in the implementation documentation of SAP NetWeaver. you can perform normal AS Java sizing.sap. For large use cases.

Planning Guide – System Landscape Directory For example. you would get a maximum processing time for data suppliers of 50 minutes (60 ABAP systems * 2 messages per system and day * 10 seconds/per message + 30 Java systems * 2 messages per system and day * 30 seconds/per message = 3000 seconds per day = 50 minutes per day). you should restrict the number to several hundred connected systems. Additional load is generated when users access the UI and browse the data in the SLD. it could be a problem for the SLD if all data suppliers send updates at the same time. if you want to reduce the load of your SLD. As this can hardly be guaranteed. Also. if you have 60 ABAP and 30 Java systems connected to your SLD and each of these systems sends data twice a day (which correlates to the standard data supplier configuration). a system as proposed above could process the data of the data suppliers of over 1000 ABAP and 1000 Java systems. and when clients read data from and write data to the SLD (for example. Therefore. we recommend that you add further reserves and use factors of safety. As a result. The resulting load is difficult to estimate because it heavily depends on your system landscape and how you use the single clients that rely on the SLD. you halve the corresponding processing time to handle data supplier data in the SLD. 46 December 2008 . by reducing the update frequency from twice to once a day. In our example. reduce the update frequency or use a stronger host. For example. These assumptions do not consider peak loads of the SLD. but only if the updates are sent spread over the day. you could consider reducing how often data suppliers send updates to the SLD and try to deconcentrate the time when the single data suppliers send updates to the SLD. SAP NetWeaver PI and SAP Solution Manager).

4.1.as well as the new SAP Web Dispatcher. The non-existence of barriers such as firewalls and NAT (Network Address Translation) allows you to use both SAP load balancing . Although corporate networks incorporate different kinds of networks.1 Intranet Scenario Intranet means the use of Internet techniques within a corporate network.Planning Guide – System Landscape Directory 4 Appendix 4. the existence of company wide naming and addressing rules ensures direct addressing and communication between all servers.1 Network Access Scenarios This section shows various SLD setups that take networking aspects into account. such as LAN. WAN. The load balancing solution distributes requests to a clustered AS Java system on which an SLD is running. The following figure shows the Intranet scenario: Business systems located within the company‘s network Business systems located within the LAN Load balancing using message server redirection Business System Business System SLD running on a clustered AS Java system SAP Web Dispatcher or Reverse Proxy Business System Load balancing AS Java (multiple nodes) AS Java (multiple nodes) (multiple nodes) AS Java Business System Business System December 2008 47 . or leased lines. VPN.the SAP message server redirect mechanism .

Planning Guide – System Landscape Directory 4. These business systems are normally connected over point-to-point access through VPN or leased lines but not over public networks. The following figure shows the Extranet scenario: Well known business systems located in remote networks DMZ (demilitarized zone) Business systems located within the LAN Business System SAP Web Dispatcher or Reverse Proxy Access Router Leased line Load balancing with HTTP based communication VPN T unn el Business System SLD (multiple servers) SLDservers) (multiple (multiple servers) Firewall SLD Business System SAProuter Leased line NT VP el unn Business System with RFC based communication Business System 48 December 2008 . SAProuter can be used to check and forward RFC connections. these systems are not allowed to access the whole corporate network but only a few dedicated servers. Nevertheless. Well-known systems – for example.1. systems of business partners – get access to specific servers within the Intranet. This restriction is normally achieved employing some kind of reverse proxy within the DMZ (Demilitarized Zone). SAP provides the SAP Web Dispatcher for use as an HTTP reverse proxy and load balancer.2 Extranet Scenario Extranets extend the range of the Intranet. This proxy forwards the requests to permissible servers.

2. The SLD data suppliers are displayed on the right side (bullets 1 to 3).2 Overview of Connections to and from SLD The following figure gives you an overview of all communication paths to and from the SLD.2 Java Data Supplier (2) Java data suppliers send their data directly to the SLD bridge by using HTTP/HTTPS protocol.1 ABAP Data Supplier (1) ABAP data suppliers must send their data to the SLD bridge by using RFC. SLD clients on the left side are capable of interacting with the SLD. send. The following figure shows all communication paths explained in the following sections: SLD Clients Data Supplier SAP System Java SLD System Java Application SLD Client LCRABAP API ) (WBEM HTTP/S SLD Server SLD Client LCRABAP API SLD Bridge 3 /S TP HT sidreg C++ Programm System not based on SAP NetWeaver 4 5 ABAP SAP System HTT P/S JCO RFC Application 5 RFC JCO RFC SAP Gateway 2 RF C Java Application Application C RF SAP System ABAP 1 SLD System HTTP Java SLD Server SLD Client ABAP 5 Application Application 6 SLD Bridge 4. 4. December 2008 49 . This means they can retrieve. which is registered with the gateway and provides the connection to the SLD bridge running in the Java environment. and update system landscape data with the SLD. The destination is a Java Connector (JCo).Planning Guide – System Landscape Directory 4. They send up-to-date system landscape data to the SLD.2.

The first communication step is with an RFC server (RFC destination LCRABAP-API) registered with a gateway. You can use this forwarding mechanism to update or synchronize several SLD instances in large IT landscapes.2.Planning Guide – System Landscape Directory 4.5 ABAP SLD Client (5) An SLD ABAP client cannot communicate with the SAP server directly.2. 50 December 2008 . 4. you can configure each SLD bridge to forward all incoming data supplier messages to other SLD bridges as well.2. see Automatic Forwarding of Landscape Data [page 18].4 Java SLD Client (4) The SLD Java client is able to interact directly with the SLD server by using HTTP/HTTPS protocol. The LCRABAP server interfaces with the SLD client.3 External Data Supplier (3) Applications not running on the SAP NetWeaver Application Server may use sldreg to send their landscape data. 4. For more information. 4.6 SLD to SLD Message Forwarding (6) Data suppliers send their messages to the SLD bridge to which they are connected only. sldreg can be used as an interface to send the data to the SLD bridge by using HTTP/HTTPS protocol. Nevertheless. which communicates with SLD using HTTP/HTTPS protocol.2.