AK Iseries SLD Print

System Landscape Directory of SAP NetWeaver
Overview and Best Practices
Boris Zarske (boris.zarske@sap.com)

Senior Product Specialist SAP NetWeaver Product Management
14. November 2007
Learning Objectives
As a result of this presentation, you will know: Basic concepts and features of system landscape directory (SLD) of SAP NetWeaver How SLD is used
How clients work with SLD How clients rely on the data stored in SLD
How to define a landscape strategy for SLD
SAP 2007 / Page 2
Agenda
1. Introduction
1.1. Motivation 1.2. Key Features
2. 3. 4. 5.
SLD Data Suppliers SLD Data Consumers Topology Summary
SAP 2007 / Page 3
Motivation: Some of the Challenges Addressed by SLD

Where can I get a consistent and up-to-date overview of SAP software installed in my landscape? Infrastructure data like hosts and ports of back-end systems should be stored centrally!
Where can I get technical information about SAP products regularly updated?
Configuration of software development should be maintained centrally including interdependencies!
How can I make sure that my central administration tools use the same, up-todate landscape information?
How can I make sure that the names of Java development objects are unique internally + externally although I have several development teams?
SAP 2007 / Page 4
SLD: The Basic Idea
Applications and Tools

J2EE B ackend S erver
PPMS System
SAP NetWeaver PI Software Lifecycle Manager
Bu sine ss D ata
Web S ervice Provider

Web Ser vice
SO AP
Bu sine ss Dat a
ABA P Backend Busin ess B ackend App li cation Ba c kend Application Server
Da ta R FC ena ble d Fun ctio n Mod ule s
RFC
Cen tral M onito ring & Admin istration System SAP NetWeaver Administrator
EJB ( e.a .)
RMI
SLD
D ep o l ye d We b De plo yed Dy Wenpr b o App Dyn pr o Ap p
J2EE Web Dynpro Runt ime
AB AP Web Dynpro Runti me
W eb Dynp ro We b D ynp ro Ap p Ap p
Pr odu ctiv e La nds cape
Solution Manager
SAP S AP Net Weaver NetWeaver Developer Developer Studio S tudio
HTTP( S)
A BAP development Workbench
M oni toring anagem ent M oni toring& &M M anagem entConnectivity Connectivity Layer Layer (JMX, (JMX,Agents) Agents)
Partner Applications,
Web Dyn pr o Ap plica tion
ABAP Syst em
Java System
Non- SAP Component
S AP Enterprise Portal
Web Dynpro Runtime
SAP Solution Manager
SAP NetWeaver Administrator
Synchronize
Master Component Repository
Applications
Automatic registration Customer Landscape SLD + update Landscape description
Scenarios
Software Units
Update
Component information
3rd-Party / Customer Component Types
Landscape Patterns
Regular manual task

(SAP Note 669669)
Customer
SAP 2007 / Page 5
Motivation (Cont.)
Approach Provide one central provider of landscape information:

Catalog of installable software: All components that can theoretically be installed Component information repository List of installed software (including technical details) Landscape description
Customer Landscape
Result:
Landscape data is gathered + updated automatically No manual gathering (from SAP Service Marketplace + every system, ) Data stored centrally + consistently (not in Excel sheets, for example) Stored information ca act as basis for different tools and services
SAP 2007 / Page 6
Agenda
1. Introduction
1.1. Motivation 1.2. Key Features
2. 3. 4. 5.
SLD Data Suppliers SLD Data Consumers Topology Summary
SAP 2007 / Page 7
Key Features of SLD

SLD is a component of SAP NetWeaver and completely implemented with Java technology Based on proven industry standards of DMTF*: Object-oriented Extensible Open:

3rd-party software as SLD data provider 3rd-party software as SLD data consumer
How to get it? SLD contained in Application Server Java (AS Java) systems Standard implementation procedure already comprises configuration of SLD and data suppliers
Access it at http://<hostname>:<HTTP port>/sld
* Distributed Management Task Force www.dmtf.org
SAP 2007 / Page 8
AS Java
Web-Based SLD User Interface: Initial Page
Landscape Description Technical Landscape Landscapes Business Systems
Software Catalog
Name Reservation for Java Development
SAP 2007 / Page 9
Information Stored in SLD: Software Catalog

Provides information about all available SAP software: Available releases Available support package levels Dependencies Provided by SAP Basis for landscape description
SAP 2007 / Page 10
Information Stored in SLD: Landscape Description

Provides information about installed systems:
Products and components Installed versions and patch levels Timestamp (last update) Can be enriched individually (admin contact, description, )
SAP 2007 / Page 11
Landscape Description (Contd): Installed Products
SAP 2007 / Page 12
Agenda
1. 2. 3. 4. 5.
Introduction SLD Data Suppliers SLD Data Consumers Topology Summary
SAP 2007 / Page 13
How Does SLD get Landscape Description Data?

SAP systems contain data suppliers that collect and send data to SLD:
Must be configured once per landscape element After that, they send reliable and up-to-date data automatically: At system startup Periodically (batch job)
ABAP System
ABAP Data Supplier
RFC
Gateway
Java System
Java Data Supplier
HTTP
SLD
Java System
Other System
Other Data Supplier
sldreg (lib/exe)
HTTP
SAP 2007 / Page 14
Data Supplier ABAP-Based Systems

Transaction RZ70
Standard implementation procedure already comprises configuration manual configuration only required for existing systems
SAP 2007 / Page 15

Consistent and up-todate overview of installed SAP software Central store of infrastructure data like hosts and ports of backend systems
Technical information about SAP products regularly updated
SLD is central provider for landscape data, data updated by SLD systems automatically
SLD Landscape description
Configuration of SW development managed centrally
Central administration tools use same up-todate landscape information
Unique names of Java development objects
SAP 2007 / Page 16

SLD provides a software catalog based on SAP data

SAP 2007 / Page 17
Agenda
1. Introduction 2. SLD Data Suppliers 3. SLD Data Consumers

3.1. 3.2. 3.3 3.4 3.5 3.6 Overview SAP NetWeaver Process Integration Web Dynpro Java development (NWDI) SAP Solution Manager Other SLD clients
4. Topology 5. Summary
SAP 2007 / Page 18
Information in SLD as Foundation for SAP Applications

J2EE Backend Server
EJB (e.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. configuration
SLD
Deployed Web Deployed Web Dynpro App Dynpro App
J2EE Web Dynpro Runtime
ABAP Web Dynpro Runtime
Web Dynpro Web Dynpro App App
Retrieve dev. configuration
Register dev. configuration
CMS (Landscape Configurator)
SAP NetWeaver Developer Studio
HTTP(S)
ABAP development Workbench

DTR CBS
/workspace /inactive /buildspace Binaries of used SCs Development Objects
Web Dynpro Application
SAP Enterprise Portal
/active
Web Dynpro Runtime Software Lifecycle Manager of SAP NetWeaver
Development Configuration
SAP NetWeaver Development Infrastructure
SLD
SAP NetWeaver Process Integration
Further applications (including partner applications)
Central Monitoring & Administration System SAP NetWeaver Administrator
Adaptive Computing Controller Solution Manager
SLD
Solution Manager
Control Node Centralized Storage System
Productive Landscape
Monitoring Monitoring& &Management ManagementConnectivity ConnectivityLayer Layer (JMX, (JMX,Agents) Agents)
Server Network Switch
ABAP System
Java System
Non-SAP Component
Computing Nodes
SAP NetWeaver Administrator
Storage Network Switch
Adaptive Computing Controller

SAP 2007 / Page 19
Agenda

SAP 2007 / Page 20
SAP NetWeaver Process Integration as SLD Client

SAP NetWeaver Process Integration (PI):
SAP's platform for process integration using the exchange of XML messages Former name: SAP NetWeaver Exchange Infrastructure (SAP NetWeaver XI)
The following slides provide information how SAP NetWeaver PI works with SLD:
Which data stored in SLD is required by SAP NetWeaver PI How SAP NetWeaver PI relies on SLD
SAP NetWeaver Process Integration
SAP 2007 / Page 21
SAP NetWeaver PI as SLD Client (Contd)
Main SLD use cases for SAP NetWeaver PI:

1.
SLD provides business system names:

Business systems are logical systems that function as sender or receiver within PI SLD maps business system name to technical system so that PI can determine the receiver of a message To which technical system belongs business system <abc>? Business system <abc> belongs to technical system <XYZ>!
MESSAGE abc TO: XYZ
PI
SLD
abc XYZ
SAP 2007 / Page 22

SLD provides transport targets for content transports of PI:
For each business system, define which business system corresponds to it in other environment (DEV, TEST, QA, PROD) If you transport configuration objects, business systems from source environment will be mapped to target environment during import
2.
Example with QA and PROD environments

Business System B1Q Business System B1P
REQUIRED: Mapping B1Q B1P
PIQ PIP
B2Q (QA) to B2P (PROD)
PI System PIQ
PI System PIP
SOLUTION: Create the following transport targets in SLD: B1Q B1P PIP B2P PIQ B2Q
Business System B2Q
Business System B2P
QA Environment
SAP 2007 / Page 23
PROD Environment
3.
SLD provides information about software component versions
4.
SLD provides data of PI topology: Systems and adapter engines for PI end-to-end monitoring Addresses for transfer of adapter configuration data inside of PI
SAP 2007 / Page 24
How Does PI Rely on SLD?
PI caches SLD data SLD access required if you develop or deploy PI transports SLD access required during PI startup: At startup, PI loads SLD data into caches SLD access might also be required during runtime: Such as for unexpected restart of PI system
During SLD downtime, operation of your PI system is endangered
SAP 2007 / Page 25
Agenda

SAP 2007 / Page 26
Web Dynpro Runtime as SLD Client

Web Dynpro requires SLD for adaptive RFC calls:
SLD stores back-end connection data centrally Changes in landscape need only be reflected in SLD For example, after move of a back-end system, infrastructure data has only to be updated in SLD, not in all applications communicating with this back-end system
aRFC
TO: XYZ abc TO:
Web Dynpro
Web Dynpro
Web Dynpro
Web Dynpro
Connection Data
Back-End System XYZ
SLD
SAP 2007 / Page 27
How do Web Dynpro Applications Rely on SLD?
Caching of SLD data: Caching for performance reasons, only in memory SLD access required during startup SLD access required during runtime
Web Dynpro cache used
If refresh was not possible (SLD downtime), cache will be used with warning
ERROR
Expiration Time
Invalidation Time
During SLD downtime, Web Dynpro applications using aRFC are endangered
SAP 2007 / Page 28

SLD as data provider of infrastructure data for PI/XI and Web Dynpro
SAP 2007 / Page 29
Agenda

SAP 2007 / Page 30
SLD Used for Java Development

SAP NetWeaver Development Infrastructure (NWDI) provides the environment for all processes of Java-based development and Java-based software life-cycle management
For Java development, SLD provides the following services:
1.
Definition of software, products, and software components to be developed with interdependencies:

Dependencies to other software components during build time Dependencies to other software components during runtime
2.
Naming Service Reserve namespace prefixes for unique names of development components Storage of development configurations required for development
Determine software components to be developed and control access to objects in SAP NetWeaver Development Infrastructure All developers who share same configuration work with same consistent set of objects
3.
SAP 2007 / Page 31
SLD Used for Java Development:
1. Definition of Java Products + Software Components in SLD
Products

Defined in SLD Can have multiple versions Can contain multiple software components
Software Components

Defined in SLD Can be assigned to multiple products Can have multiple versions
Performed by software architect
SAP 2007 / Page 32
SLD view
1. Definition of Java Products + Software Components in SLD
SAP 2007 / Page 33

In SLD, define Java software, products, and SW components to be developed

SAP 2007 / Page 34

2. Name Reservation
Reserve namespace prefixes for unique names of development objects

1.
Reserve namespace prefix at SAP Service Marketplace (service.sap.com/namespaces). Globally unique prefix Valid for objects without Internet domain, such as table fields or tables
2.
Enter the reserved namespace prefix in SLD Name Server of your company Avoids name clashes between Java development objects of different development teams within your company and of other companies Actual name reservation is performed in the SAP NetWeaver Developer Studio (see next slide)
SAP 2007 / Page 35
2. Name Reservation in SAP NetWeaver Developer Studio
With an SLD name server in operation, name reservation for development components and table or index names is done automatically
Example: Creation of a new development component
SAP 2007 / Page 36

SLD offers naming service
SAP 2007 / Page 37
How Does Java Development Rely on SLD?
Information stored in SLD is essential for Java development:

During SLD downtime: No login to SAP NetWeaver Development Infrastructure No name registration possible Nevertheless, Java development not treated as runtime-relevant
SAP 2007 / Page 38
Agenda

SAP 2007 / Page 39
SAP Solution Manager and SLD
SAP Solution Manager:

Platform that provides integrated content, tools, and methodologies that you need to implement, support, operate and monitor your enterprise's solutions from SAP Provides a data repository for system data on its own SAP Solution Manager can either: Use SLD as data repository for SAP Solution Manager Use its own data repository Recommendation depends on your landscape: Only ABAP components in your landscape SLD is optional Also Java components in your landscape (such as SAP NetWeaver Enterprise Portal and SAP NetWeaver PI) SLD is mandatory
SAP 2007 / Page 40
Which Data is Retrieved From SLD by SAP Solution Manager?

Data retrieved without SLD:
For ABAP systems System name System number Message server Clients (information from client table T000) Installed software components
Data retrieved from SLD:
If you use SLD as data repository for SAP Solution Manager:

You get additional ABAP data You get data about Java systems Data in SLD is updated automatically
For ABAP systems System name System number Message server Clients (information from client table T000) Installed software components, releases, and patch levels Instances of the system Servers assigned to the instances Server data Databases of a system Server of a database For Java systems Instances of the system Servers assigned to the instances Server roles (types) Installed software components, releases, and patch levels
SAP 2007 / Page 41
How to Switch SAP Solution Manager to SLD?

To switch to SLD, use transaction SMSY_SETUP in SAP Solution Manager:
SAP 2007 / Page 42
How Does SAP Solution Manager Rely on SLD?
Information stored in SLD not essential for SAP Solution Manager: During SLD downtime: No updates to landscape data available in SAP Solution Manager Nevertheless, not treated as runtime-relevant
SAP 2007 / Page 43
Agenda

SAP 2007 / Page 44
How Do Other Applications Rely on SLD?
Information stored in SLD could also be essential for further applications in your production landscape:
SAP NetWeaver Administrator: Tool for administration and monitoring, offering a central entry point to whole SAP NetWeaver system landscape Requires SLD for remote monitoring functions During SLD downtime, no central administration of systems is possible Adaptive Computing Controller: Enables users to control an adaptive computing landscape from a single point through observation, operation and dynamic resource distribution Requires SLD for its operation (that is, start, stop and change of resources) During SLD downtime, only monitoring functions of Adaptive Computing Controller are available
SAP 2007 / Page 45

SLD as data provider for PI/XI, SAP Solution Manager, Web Dynpro, NWA, ACC,
SAP 2007 / Page 46
Agenda
1. 2. 3. 4. 5.
SAP 2007 / Page 47
Reasons to Have Several SLDs
Web Dynpro
DEV
CONS
QA
Firewall
PROD
SAP NetWeaver PI
7X
24
SAP NetWeaver Admin.
Isolated production environment
Improve availability for applications relying on SLD data
HQ
SLD SLD
PROD Different user groups with different views (such as distributed locations with local admin groups)
SAP 2007 / Page 48
Sandbox SLD to test content imports, CIM data updates, patches,
Process To Define Your SLD Strategy

How and where to run SLD in my system landscape?
Learn SLD concepts
How many SLDs?
Synchronization?
Where to run SLD?
Whole planning process thoroughly covered in Planning Guide SLD
SAP 2007 / Page 49
Fundamental SLD Concepts and Options

1.
Get overview of SLD concepts + options Central or distributed organization Synchronization options (automatic forwarding and export/import) Master SLD Applications that rely critically on SLD data Release interoperability Possibilities to change your SLD landscape in the future
Learn SLD concepts
How many SLDs?
Synchronization?
Where to run SLD?
SAP 2007 / Page 50
Example for Topology Option: Central Organization

Central Organization:
Extranet Intranet
SAP System
Intranet
SAP System
One single SLD for entire customer enterprise network Advantages:
SAP System
Intranet
Easy setup + low operation effort No redundancy, consistent foundation
SAP System
SLD
Drawbacks: High demand on SLD regarding availability and stability
SAP System SAP System SAP System
Different user groups (developers, administrators, ) are working within the production SLD Data of all systems visible/accessible
SAP 2007 / Page 51
Example for Topology Option: Distributed Organization

Distributed Organization:
Several distributed SLDs
SLD Customer 1
SAP System
Advantages:
Customer 2
SAP System
Availability improved Restricted views possible Environments can be isolated
SAP System
SLD
SLD
SAP System
Drawbacks: Higher operation effort
SAP System
SAP System
Several
CIM model updates required synchronization
Possible
SAP 2007 / Page 52
Changing Your SLD Landscape
SAP System
SAP System
SAP System
SAP System
SAP Note 936318

SLD
SAP System
SAP System
SLD
SLD
SAP Note 935474

SAP System SAP System SAP System SAP System
SAP Note Number

935474
Title
Grouping SLD instances
Description
Describes how you can merge two SLDs by importing the content of one SLD into another SLD. Describes how you can split an SLD into two or more instances.
936318
Splitting an SLD instance
SAP 2007 / Page 53
Synchronization of Distributed SLDs
If you have several SLDs, you might have to synchronize SLD data Synchronization means interchange/ forwarding of SLD data Two options:
1.
Extranet
Region 1 SAP System Region 2 SAP System
1
SAP System
SLD
Automatic forwarding of landscape data
SLD
SAP System
Automatic forwarding of only certain SLD data Automatically/regular sync Only data received from SLD data suppliers, no manually entered data, no filtering!
SAP System
SAP System
Extranet
Region 1
SAP System
Region 2
SAP System
2.
Manual export/import Manual/one time sync All data can be synced (selective!) Can result in high operation effort 2
SLD
SAP System SAP System Export and import of SLD data
SLD
SAP System
SAP System
SAP 2007 / Page 54
Synchronization of Distributed SLDs: Comparison of Sync Options

Sync Method Automatic Procedure? Sync of All SLD Data? Filtering Possible? Ideal Use Case?
Automatic Forwarding
Only sync of technical system information required Low frequency / low amount of manually entered data has to be synchronized
Export/ Import
Different sync methods can be combined in a landscape!
SAP 2007 / Page 55
Number of Required SLDs
2.
Learn SLD concepts
How many SLDs?
Synchronization?
Where to run SLD?
Identify number of required SLDs in your landscape Depends on your requirements concerning data stored in SLD: Which applications do you run that rely on SLD data? Required availability of SLD data + impact on your system landscape if SLD data would temporarily not be available Required performance for accessing SLD data Technical constraints of your system landscape Visibility and changeability of certain data stored in SLD Legal constraints Company rules, organizational structures or governance models
SAP 2007 / Page 56
Best Practices: Central SLD for all Applications

AS Java Realized as High Availability Cluster
Central SLD
NWDI
Web Dynpro Prod Web Dynpro Web Dynpro
QA
Dev
QA Prod
Dev
SAP NetWeaver PI
JCO / RFC Dev
ABAP QA ABAP Back Prod End Back End ABAP Back End
SAP 2007 / Page 57
Best Practices: Separate SLD for DEV/QA and PROD

Development and Quality Assurance Systems Production Systems
SLD
for DEV and QA
SLD
Transport of data
for Overall System Landscape
Dev QA Prod Dev
SAP NetWeaver PI
Web QA Dynpro Web Dynpro
Web Dynpro
Prod
SAP NetWeaver PI
JCO / RFC
Dev
JCO / RFC
NWDI
ABAP QA Back End ABAP Back End
ABAP Back End
Prod
SAP 2007 / Page 58
Best Practices: Separate SLD for SAP NetWeaver Development Infrastructure (NWDI)
SAP NetWeaver Development Infrastructure (NWDI) Production, QA and DEV System
SAP NetWeaver Development Infrastructure
Prod
CMS
Name Server SLD for NWDI
Landscape SLD
CBS
Dev QA Dev Prod Prod
DTR
QA Web Dynpro Prod Web Dynpro Web Dynpro
SAP Business System
Developer PC
JCO / RFC
Dev
ABAP QA Back ABAP End Prod Back End ABAP Back End
SAP 2007 / Page 59
SLD Synchronization Strategy

3.
If you require several SLDs, define a synchronization strategy for the data stored in your SLDs
Learn SLD concepts
How many SLDs?
Synchronization?
Where to run SLD?
SAP 2007 / Page 60
SLD Synchronization Strategy
If you require more than one SLD, think about how to synchronize the data stored in your SLDs Create a model to understand which data is required in which of your planned SLDs To generate different views, plan to restrict the forwarding of certain data to certain SLDs in your landscape For example, you may not want to forward data of your production systems into development SLDs If manual synchronization is required, an operation manual helps to establish a process when and how synchronization should be performed by whom
SAP 2007 / Page 61
Where to Run SLD in Your System Landscape?
4.
On which system(s) you want to run your SLD(s)?
Learn SLD concepts
How many SLDs?
Synchronization?
Where to run SLD?
Options (each with pros/cons): Dedicated SLD system With other central shared services (such as SAP NetWeaver Administrator) With a business function (such as SAP NetWeaver PI) SLD requirements that affect this decision? Which applications do you run that rely on SLD data? High availability Planned/unplanned downtime Load of the corresponding host Network connection
SAP 2007 / Page 62
Where to Run SLD in Your System Landscape?
For details, see Planning Guide SLD
SAP 2007 / Page 63
Outlook: Synchronization With Next Release of SAP NetWeaver

Full automatic synchronization mechanism planned with next release of SAP NetWeaver All SLD data gets synchronized automatically Fully automated: No user interaction Automatic conflict resolution
Uni- and bi-directional Asynchronous propagation (able to handle temporary downtimes of nodes) Communication over HTTP protocol Benefits: Reduction of manual synchronization effort Continuous availability possible (for example, during upgrade) Performance Consider this planned feature for your mid- and long-term SLD strategy
SAP 2007 / Page 64
Outlook: Synchronization With Next SAP NetWeaver Release Comparison of Sync Options
Sync Method Automatic Procedure? Sync of All SLD Data? Filtering Possible? Ideal Use Case?
Automatic Forwarding Export/ Import
Only sync of technical system information required Low frequency / low amount of manually entered data has to be synchronized Recommended sync method as of next SAP NetWeaver release
Full Automatic Sync
Different sync methods can be combined!
SAP 2007 / Page 65
Outlook: One Transport Order for SLD

Enhanced Change & Transport System (CTS)
Enhancement of existing ABAP CTS to transport also non-ABAP objects: Java objects (J2EE, Java EE) SAP-specific non-ABAP technologies (such as Web Dynpro Java or SAP NetWeaver Portal) Combined transport requests for mixed sets of objects (ABAP, Java, ) Simplified transport management, avoids inconsistent system states Central administration of all transports (ABAP, Java, ) in one UI Synchronized updates of mixed processes (ABAP/Java applications) Available as of SAP NetWeaver 7.0 Support Package Stack (SPS) 12
Also for SLD transports

Available with SAP NetWeaver 7.0 SPS 13 Alternative for Export/Import
SAP 2007 / Page 66
Agenda
1. 2. 3. 4. 5.
SAP 2007 / Page 67
Summary
SLD acts as central information provider in your system landscape
Using the SLD helps to reduce the redundancy of system landscape information SAP systems inside a landscape report data automatically to the SLD
SLD serves as the landscape data foundation for applications based on it Based on your requirements, we offer different options how and where to run SLD in your landscape

Plan your SLD landscape strategy well in advance Starting point: Planning Guide SLD
SAP 2007 / Page 68
Thank you!
SAP 2007 / Page 69
Further Information
SAP Service Marketplace:

Planning Guide System Landscape Directory available under http://service.sap.com/sld Media Library (How to plan your SLD system landscape) Post-Installation Guide System Landscape Directory available under http://service.sap.com/sld Media Library (How to set up SLD in an AS Java system) Master Guide SAP NetWeaver available under http://service.sap.com/installnw70 (Information about shared services + how to run them together with SLD)
SAP 2007 / Page 70
Further Information List of Important SAP Notes for SLD

SAP Note Number 935474 936318 935245 720717 Title Grouping SLD instances Splitting an SLD instance Importance of Object Server SLD parameter Reduce the number of System Landscape Directories (SLD) Compatibility of SLD in the system landscape Configuration of the SAP System Landscape Directory Updating the SAP Component Repository Description Describes how you can merge two SLDs by importing the content of one SLD into another SLD. Describes how you can split an SLD into two or more instances. Describes the consequences of changing the object server, which could be required to split or merge SLDs. Describes manual actions you have to perform for SAP NetWeaver Process Integration if you merge multiple SLDs. Gives information about released combinations of SLD server and SLD client releases. Contains further information about the required number of SLD instances in a landscape and how to synchronize them. Describes how you can perform the manual update of the component information and of the CIM model
954820 764393
669669
SAP 2007 / Page 71
Copyright 2007 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, Duet, Business ByDesign, ByDesign, PartnerEdge 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 in several other countries all over the world. All other product and service names mentioned and associated logos displayed are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. The information in this document is proprietary to SAP. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence. The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages
Weitergabe und Vervielfltigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrckliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen knnen ohne vorherige Ankndigung gendert werden. Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte knnen Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwhnte SAP-Produkte und Services sowie die dazugehrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Lndern weltweit. Alle anderen in diesem Dokument erwhnten Namen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. Produkte knnen lnderspezifische Unterschiede aufweisen. Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderen Vereinbarung mit SAP. Dieses Dokument enthlt nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP-Produkts und ist fr SAP nicht bindend, einen bestimmten Geschftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP bernimmt keine Verantwortung fr Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht die Richtigkeit oder Vollstndigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewhr, weder ausdrcklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschlielich, hinsichtlich der Gewhrleistung der Marktgngigkeit und der Eignung fr einen bestimmten Zweck sowie fr die Gewhrleistung der Nichtverletzung geltenden Rechts. SAP bernimmt keine Haftung fr Schden jeglicher Art, einschlielich und ohne Einschrnkung fr direkte, spezielle, indirekte oder Folgeschden im Zusammenhang mit der Verwendung dieser Unterlagen. Diese Einschrnkung gilt nicht bei Vorsatz oder grober Fahrlssigkeit. Die gesetzliche Haftung bei Personenschden oder die Produkthaftung bleibt unberhrt. Die Informationen, auf die Sie mglicherweise ber die in diesem Material enthaltenen Hotlinks zugreifen, unterliegen nicht dem Einfluss von SAP, und SAP untersttzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewhrleistungen oder Zusagen ber Internetseiten Dritter ab. Alle Rechte vorbehalten.
SAP 2007 / Page 72

AK Iseries SLD Print

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

AK Iseries SLD Print

Uploaded by

Copyright:

Available Formats

System Landscape Directory of SAP NetWeaver

Overview and Best Practices

Boris Zarske (boris.zarske@sap.com)

14. November 2007

How to define a landscape strategy for SLD

SAP 2007 / Page 2

SLD Data Suppliers SLD Data Consumers Topology Summary

SAP 2007 / Page 3

Motivation: Some of the Challenges Addressed by SLD

Configuration of software development should be maintained centrally including interdependencies!

SAP 2007 / Page 4

SLD: The Basic Idea

Applications and Tools

Web S ervice Provider

J2EE Web Dynpro Runt ime

AB AP Web Dynpro Runti me

SAP S AP Net Weaver NetWeaver Developer Developer Studio S tudio

A BAP development Workbench

Web Dyn pr o Ap plica tion

Non- SAP Component

Web Dynpro Runtime

SAP Solution Manager

SAP NetWeaver Administrator

Automatic registration Customer Landscape SLD + update Landscape description

3rd-Party / Customer Component Types

Regular manual task

Approach Provide one central provider of landscape information:

SAP 2007 / Page 6

SLD Data Suppliers SLD Data Consumers Topology Summary

SAP 2007 / Page 7

Key Features of SLD

Web-Based SLD User Interface: Initial Page

Landscape Description Technical Landscape Landscapes Business Systems

Name Reservation for Java Development

SAP 2007 / Page 9

Information Stored in SLD: Software Catalog

SAP 2007 / Page 10

Information Stored in SLD: Landscape Description

SAP 2007 / Page 11

Landscape Description (Contd): Installed Products

SAP 2007 / Page 12

Introduction SLD Data Suppliers SLD Data Consumers Topology Summary

SAP 2007 / Page 13

How Does SLD get Landscape Description Data?

ABAP Data Supplier

Java Data Supplier

Other Data Supplier

SAP 2007 / Page 14

Data Supplier ABAP-Based Systems

Motivation: Some of the Challenges Addressed by SLD

Technical information about SAP products regularly updated

Configuration of SW development managed centrally

Central administration tools use same up-todate landscape information

Unique names of Java development objects

Motivation: Some of the Challenges Addressed by SLD

Technical information about SAP products regularly updated

SLD provides a software catalog based on SAP data

Configuration of SW development managed centrally

Central administration tools use same up-todate landscape information

Unique names of Java development objects

1. Introduction 2. SLD Data Suppliers 3. SLD Data Consumers

SAP 2007 / Page 18

Information in SLD as Foundation for SAP Applications