AK iSeries SLD Print

7/16/2019 AK iSeries SLD Print

http://slidepdf.com/reader/full/ak-iseries-sld-print 1/72

System Landscape Directory

of SAP NetWeaver ®

Overview and Best Practices

Boris Zarske ([email protected])Senior Product Specialist

SAP NetWeaver Product Management

14. November 2007

mailto:[email protected]

mailto:[email protected]



©SAP 2007 / Page 2

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 3

1. Introduction

1.1. Motivation

1.2. Key Features

2. SLD Data Suppliers

3. SLD Data Consumers

4. Topology

5. Summary

Agenda



©SAP 2007 / Page 4

Motivation: Some of the Challenges Addressed

by SLD

Where can I get a consistentand up-to-date overview of SAP software installed in

my landscape?

Where can I gettechnical informationabout SAP products –

regularly updated?

Infrastructure data – li kehosts and ports of back-endsystems – should be stored

centrally!

How can I make surethat the names of Javadevelopment objects

are unique internally +externally – although I

have severaldevelopment teams?

How can I make surethat my central

administration toolsuse the same, up-to-

date landscapeinformation?

Configuration of software development

should be maintainedcentrally – inc ludinginterdependencies!

……



©SAP 2007 / Page 5

SLD: The Basic Idea

Synchronize

PPMS

System

Customer

3rd-Party / Customer

Component Types

Customer LandscapeSLD

Component

information

Landscape

description

Update

Automatic

registration

+ update

Master

Component

Repository

App li cat ions

Scenarios

Software Units

Landscape Patterns

Regular manual task(SAP Note 669669)

Appl ications and Tools

SAP NetWeaver PI

Web Dynpro

RuntimeSoftware Lifecycle

Manager

SAP Solution

Manager

SAP NetWeaver

Admin istr ator

Web Service

Provider

J2EE

BackendServer

J2EEWeb Dynpro

Runtime

DeployedWebDynproApp

Deployed WebDynproApp

SAP Enterprise Portal

WebDynproApplication

HTTP(S)SAP

NetWeaver

DeveloperStudio

SAPNetWeaver

Developer

Studio

ABAPWeb DynproRuntime

WebDynproAppW

ebDynproApp

ABAP developmentWorkbench

BackendApplication

BackendApplication

ABAP

BackendServer

WebService

RMI S OAP RFC

RFCenabledFunctionModulesEJB(e.a.)

BusinessData

BusinessData

BusinessData

Web Service

Provider

J2EE

BackendServer

J2EEWeb Dynpro

Runtime

DeployedWebDynproApp

Deployed WebDynproApp

SAP Enterprise Portal

WebDynproApplication

HTTP(S)SAP

NetWeaver

DeveloperStudio

SAPNetWeaver

Developer

Studio

ABAPWeb DynproRuntime

WebDynproAppW

ebDynproApp

ABAP developmentWorkbench

BackendApplication

BackendApplication

ABAP

BackendServer

WebService

RMI S OAP RFC

RFCenabledFunctionModulesEJB(e.a.)

BusinessData

BusinessData

BusinessData

BusinessData

Partner

App li cati on s,

…

Monitoring&ManagementConnectivityLayer(JMX, Agents…)

Monitoring&ManagementConnectivityLayer(JMX,Agents…)

Pr

odu ctiv e La nds cape

Cen t r al M oni t o r ing

& A dm in is t r at ion

S y s t em

S A P Net W eav er

Administ rator

SLD SolutionManager

ABAPSys tem

Java

Sys tem

N on- SAP

C om ponent

Monitoring&ManagementConnectivityLayer(JMX, Agents…)

Monitoring&ManagementConnectivityLayer(JMX,Agents…)

Pr

odu ctiv e La nds cape

Cen t r al M oni t o r ing


S y s t em

S A P Net W eav er

Administ rator

C

en t r al M oni t o r ing


S y s t em

C

en t r al M oni t o r ing


S y s t em

S A P Net W eav er

Administ rator

SLD SolutionManager

ABAPSys tem

Java

Sys tem

N on- SAP

C om ponent



©SAP 2007 / Page 6

Motivation (Cont.)

Approach – Provide one central provider of landscape information: Catalog of installable software:

All components that can – theoretical ly – be ins tal led

Component information repository

List of installed software (including technical details)

Landscape description

Result:

Landscape data is gathered + updated automatically

No manual gathering (from SAP Service Marketplace + every system,…)

Data stored centrally + cons istently (not in Excel sheets, for example)

Stored information ca act as basis for different tools and services

Customer Landscape



©SAP 2007 / Page 7

1. Introduction

1.1. Motivation

1.2. Key Features



4. Topology

5. Summary

Agenda



©SAP 2007 / Page 8

Key Features of SLD

SLD is a component of SAP NetWeaver and

completely implemented with Java technology

Based on proven industry s tandards 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 comprisesconfiguration of SLD and data suppliers

Access it at http://<hostname>:<HTTP port>/sld

* Distribu ted Management Task Force – www.dmtf.org

AS J ava

http://www.dmtf.org/

http://www.dmtf.org/



©SAP 2007 / Page 9

Web-Based SLD User Interface: Initial Page

Landscape Description

Technical Landscape

Landscapes

Business Systems

Software

Catalog

Name

Reservation

for Java

Development



©SAP 2007 / Page 10

Information Stored in SLD:

Software Catalog

Provides information about

all available SAP software: Avai lable releases

Avai lable suppor t package levels

Dependencies

Provided by SAP

Basis for landscape description



©SAP 2007 / Page 11

Information Stored in SLD:

Landscape Description

Provides informationabout installed systems:

Products andcomponents

Installed

versions and patch

levels

Timestamp

(last update)

Can be enrichedindividually

(admin contact,

description, …)



©SAP 2007 / Page 12

Landscape Description (Cont’d):

Installed Products



©SAP 2007 / Page 13

1. Introduction



4. Topology5. Summary

Agenda



©SAP 2007 / Page 14

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 rel iable and up-to-date data automatical ly:

At system startup

Periodically (batch job)

ABAPSystem

ABAP

DataSupplier

Java

System

Java

Data

Supplier

Other

System

Other

Data

Supplier

sldreg

(lib/exe)

JavaSystem

SLD

RFC

HTTP

HTTPC

Gate-way



©SAP 2007 / Page 15

Data Supplier – ABAP-Based Systems

Transaction RZ70

Standard implementation

procedure already

comprises configuration –

manual configuration only

required for existing

systems



©SAP 2007 / Page 16


by SLD

Consistent and up-to-date overview of

installed SAP software

Technicalinformation about

SAP products –regularly updated

Central store of infrastructure data – likehosts and ports of back-

end systems

Unique names of

Java developmentobjects

Centraladministration tools

use same up-to-date landscape

information

Configuration of

SW developmentmanaged centrally

SLD

Component

information

Landscape

description

SLD is central

provider for landscape

data, data updated bySLD systems

automatically



©SAP 2007 / Page 17


by SLD

Consistent and up-to-date overview of

installed SAP software



Central store of infrastructure data – likehosts and ports of back-

end systems

Unique names of




information

Configuration of

SW developmentmanaged centrally

SLD

Component

information

Landscape

description

SLD provides

a software

catalog basedon SAP data



©SAP 2007 / Page 18

1. Introduction



3.1. Overview3.2. SAP NetWeaver Process Integration

3.3 Web Dynpro

3.4 J ava development (NWDI)

3.5 SAP Solution Manager

3.6 Other SLD clients


Agenda





©SAP 2007 / Page 20

1. Introduction




3.3 Web Dynpro





Agenda



©SAP 2007 / Page 21

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 informationhow 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 22

SAP NetWeaver PI as SLD Client (Cont’d)

Main SLD use cases for SAP NetWeaver PI:

1. SLD provides business system names:

Business systems are logical systems that funct ion as sender or receiver within PI

SLD maps “business system name” to “ technical system” so that PI can determinethe receiver of a message

PI

To whichtechnical system

belongsbusiness system

<abc> ?

Business system<abc> belongs to

technical system<XYZ> !

SLDMESSAGETO: abcMESSAGETO: XYZ

abc XYZ



©SAP 2007 / Page 23


2. 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 conf iguration objects, business systems from source environment

will be mapped to target environment during import

QA

Environment

PI System

PIQ

Business

SystemB1Q

BusinessSystemB2Q

PROD

Environment

PI System

PIP

Business

System

B1P

BusinessSystem

B2P

Example with QA and PROD environments

REQUIRED:

Mapping “ B1Q PIQ B2Q” (QA) to

“ B1P PIP B2P” (PROD)

SOLUTION:

Create the following tr ansport targets in SLD:

B1Q B1P

PIQ PIP

B2Q B2P



©SAP 2007 / Page 24


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 25

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 star tup, 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 26

1. Introduction




3.3 Web Dynpro




4. Topology

5. Summary

Agenda



©SAP 2007 / Page 27

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 beupdated in SLD, not in all applications communicating with this back-end system

WebDynpro

SLD

Back-EndSystem

XYZ

aRFCTO: abc

Connection Data

aRFCTO: XYZ

Web

Dynpro

Web

Dynpro

WebDynpro



©SAP 2007 / Page 28

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

Expiration Time Invalidation Time

Web Dynprocache used

If refresh was not possible (SLDdowntime), cache will be used with

warningERROR

During SLD downtime, Web Dynpro applications

using aRFC are endangered



©SAP 2007 / Page 29


by SLD

Consistent and up-to-

date overview of installed SAP software



Central store of

infrastructure data – likehosts and ports of back-

end systems

Unique names of




information

Configuration of SW development

managed centrally

SLD

Component

information

Landscape

description

SLD as data

provider of

infrastructuredata for PI/XI

and Web Dynpro



©SAP 2007 / Page 30

1. Introduction



3.1. Overview

3.2. SAP NetWeaver Process Integration

3.3 Web Dynpro

3.4 Java development (NWDI)



4. Topology

5. Summary

Agenda



©SAP 2007 / Page 31

SLD Used for Java Development

For Java development, SLD provides the following services:

1. Definition of software, products, and software componentsto be developed with interdependencies:

Dependencies to other software components during build time

Dependencies to other software components during runtime

2. Naming ServiceReserve namespace prefixes fo r uniquenames of development components

3. Storage of development configurations required for development

Determine software components to be developed and control access to objects in SAPNetWeaver Development Infrastructure

Al l developers who share same configuration work with same consis tent set of objects

SAP NetWeaver Development Infrastructure (NWDI) provides theenvironment for all processes of Java-based development andJava-based software life-cycle management



©SAP 2007 / Page 32

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 multipleproducts

– Can have multiple versions

Performed by software architect

S L D v

i e

w



©SAP 2007 / Page 33

SLD Used for Java Development:1. Definition of Java Products + Software Components in SLD



©SAP 2007 / Page 34


by SLD





Central store of


end systems

Unique names of



use same up-to-date landscapeinformation


managed centrally

SLD

Component

information

Landscape

description

In SLD, defineJava software,products, and

SW componentsto be developed



©SAP 2007 / Page 35

SLD Used for Java Development: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 tables2. 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 36

SLD Used for Java Development:2. Name Reservation in SAP NetWeaver Developer Studio

With an SLD name server inoperation, name reservation for development components andtable or index namesis done automatically

Example:Creation of a newdevelopment component



©SAP 2007 / Page 37


by SLD





Central store of


end systems

Unique names of





managed centrally

SLD

Component

information

Landscape

description

SLD offers

naming service



©SAP 2007 / Page 38

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 regist ration possible

Nevertheless, Java development not treated as runtime-relevant



©SAP 2007 / Page 39

1. Introduction



3.1. Overview


3.3 Web Dynpro




4. Topology

5. Summary

Agenda



©SAP 2007 / Page 40

SAP Solution Manager and SLD

SAP Solution Manager:

Platform that prov ides integrated content, tools, and methodolog ies 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 reposi tory for

SAP Solut ion Manager

Use it’s 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 41

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 fromclient table T000)

Installed software components

Data retrieved from SLD:

For ABAP systems

System name

System number

Message server

Clients (information fromclient table T000)

Installed software components,releases, and patch levels

Instances of the system Servers assigned to the instances

Server data

Databases of a s ystem

Server o f a database

For Java systems

Instances of the system

Servers assigned to the instances

Server roles (types)

Installed software components, releases,and patch levels

If you use SLD as datarepository for SAP SolutionManager:

You get additional ABAP data

You get data about Java systems

Data in SLD is updated

automatically



©SAP 2007 / Page 42

How to Switch SAP Solution Manager to SLD?

To switch to SLD, use transaction SMSY_SETUP in SAP Solution Manager:



©SAP 2007 / Page 43

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 44

1. Introduction



3.1. Overview


3.3 Web Dynpro




4. Topology

5. Summary

Agenda



©SAP 2007 / Page 45

How Do Other Applications Rely on SLD?

Information stored in SLD could also be essential for further

applications in your production landscape:

SAP NetWeaver Administ rator:

Tool for administration and monitoring, offering a central entry point to whole SAP

NetWeaver system landscape

Requires SLD for remote monitoring funct ions

During SLD downtime, no central administration of systems is poss ible

Adapt ive Computing Control ler: Enables users to cont rol an adaptive computing landscape from a sing le point

through observation, operation and dynamic resource distribu tion

Requires SLD for its operation (that is, start, stop and change of resources)

During SLD downtime, only monitoring functions o f Adaptive Computing Controller

are available



©SAP 2007 / Page 46


by SLD





Central store of


end systems

Unique names of





managed centrally

SLD

Component

information

Landscape

description

SLD as data

provider for PI/XI,

SAP Solution Manager,

Web Dynpro, NWA,

ACC, …



©SAP 2007 / Page 47

1. Introduction




Agenda



©SAP 2007 / Page 48

Reasons to Have Several SLDs

Different user groups with

different views (such as

distributed locations with local

admin groups)

Isolated production environment

Improve availability for applications relying on SLD data

…

DEV CONS QA PRODFirewall

HQ

SAP

NetWeaver PI

Web

Dynpro

SAP

NetWeaver Admin .

24

Sandbox SLD to test content imports,

CIM data updates, patches, …

PROD

SLD SLD



©SAP 2007 / Page 49

Process To Define Your SLD Strategy

How and where to

run SLD in mysystem landscape?

Learn SLD concepts

How many SLDs?

Synchronization?

Where to run SLD? Whole planning processthoroughly covered in

Planning Guide – SLD



©SAP 2007 / Page 50

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

Appl ications that rely cri ti call y

on SLD data

Release interoperabili ty

Possibilities to change your

SLD landscape in the future

How and where to

run SLD in my

system landscape?

Learn SLD concepts

How many SLDs?

Synchronization?

Where to run SLD?



©SAP 2007 / Page 51

Example for Topology Option:

Central Organization

Central Organization:

One single SLD for entirecustomer enterprise network

Advantages:

Easy setup + low operation

effort

No redundancy, consistent

foundation

Drawbacks: High demand on SLD

regarding availability and

stability

Different user groups

(developers, administrators,

…) are working within the

production SLD

Data of all systemsvisible/accessible

Extranet

Intranet

Intranet

SAP

System

SLD

Intranet

SAP

System

SAP

System

SAP

System

SAP

SystemSAP

System

SAP

System



©SAP 2007 / Page 52

Example for Topology Option:

Distributed Organization

Distributed Organization: Several distributed SLDs

Advantages:

Availabi li ty improved

Restricted views possible

Environments can be i solated

Drawbacks: Higher operation effort

– Several CIM model updates

required

– Possible synchronization

Customer 1

SAP

System

SLD

Customer 2

SAP

System

SAP

System

SAP

System

SAP

System

SAP

System

SLD

SLD



©SAP 2007 / Page 53

Changing Your SLD Landscape

Describes how you can split an SLD into two or more instances.Splitting an SLD instance936318

Describes how you can merge two SLDs by importing the content of one SLDinto another SLD.

Grouping SLD instances935474

Description TitleSAP Note Number

SAP

System

SLD

SAP

System

SAP

SystemSAP

System

SAP

System

SAP

System

SLD

SAP

System

SAP

SystemSAP

System

SAP

System

SLDSLD

SAP Note 936318

SAP Note 935474



©SAP 2007 / Page 54

Synchronization of Distributed SLDs

If you have several SLDs, you mighthave to synchronize SLD data

Synchronization means interchange/

forwarding of SLD data

Two options:

1. Automat ic fo rward ing of only certain

SLD data

Automat icall y/regular sync

Only data received from SLD

data suppliers, no manually

entered data, no fi ltering!

2. Manual export/import

Manual/one time sync

All data can be synced (select ive!)

Can result in high operation effort

Extranet

Region 1

SAP

System

SLD

Region 2

SAP

System

SAP

System

SAPSystem

SAP

System

SAP

System

SLD

Aut omat ic

forwarding of landscape data

Extranet

Region 1

SAP

System

SLD

Region 2

SAPSystem

SAP

System

SAP

System

SAPSystem

SAP

System

SLDExport and

import of SLD data

1

2



©SAP 2007 / Page 55

Synchronization of Distributed SLDs:

Comparison of Sync Options

Automatic

Procedure?

Sync of All

SLD Data?

Low frequency / lowamount of manuallyentered data has to besynchronized

Export/

Import

Only sync of technicalsystem informationrequired

Automatic

Forwarding

Ideal Use Case?iltering

Possible?

Sync Method

Different sync methods can be combined in a landscape!



©SAP 2007 / Page 56

Number of Required SLDs

2. Identify number of required SLDs in your landscape –Depends on your requirements concerning datastored in SLD:

Which applications do you run thatrely on SLD data?

Required availability of SLD data + impacton your system landscape if SLD data

would temporarily not be available Required performance for accessing SLD

data

Technical constraints of your sys temlandscape

Visibility and changeabilit y of certain datastored in SLD

Legal constraints

Company rules, organizational structuresor governance models

How and where to


Learn SLD concepts

How many SLDs?

Synchronization?

Where to run SLD?



©SAP 2007 / Page 57

Best Practices:

Central SLD for all Applications

AS J ava Realized asHigh Availability Cluster

CentralSLD

SAP

Solution

Manager

SAP

NetWeaver

PI

Prod

QA

Dev

Web DynproWeb Dynpro

Web Dynpro

Dev

ABAP

Back End ABAP

Back End ABAP

Back End

DevQA

Prod

NWDI

J CO / RFC

QA

Prod



©SAP 2007 / Page 58

Development and Quality Assurance Systems Production Systems

SLDfor

DEV and QA

SLDfor Overall

System Landscape Transportof data

SAP

Solution

Manager

SAP

NetWeaver

PI

Prod

SAP

NetWeaver

PI

QA

Dev

Web

DynproWeb

Dynpro

Web

Dynpro

ABAP

Back End ABAP

Back End

ABAP

Back End

Prod

Prod

Dev

Dev

QA

QANWDI

J CO / RFC J CO / RFC

Best Practices:

Separate SLD for DEV/QA and PROD



©SAP 2007 / Page 59

Best Practices: Separate SLD for SAP

NetWeaver Development Infrastructure (NWDI)

SAP NetWeaver Development Inf ras truc tu re (NWDI) Product ion, QA and DEV System

Name Server

SLD

for NWDI

Landscape

SLD

Web Dynpro

Web Dynpro

QA

Web Dynpro

Prod

ABAP

Back End ABAP

Back End

Dev

QA

ABAPBack End

Prod

J CO / RFC

Prod

SAP

Solution

Manager

QA

Dev

Prod

SAP

Business

System

Prod

SAP NetWeaver

DevelopmentInfrastructure

CMS

CBS

DTR

Developer

PC

Dev



©SAP 2007 / Page 60

SLD Synchronization Strategy

3. If you require several SLDs, definea synchronization strategy for the

data stored in your SLDs

How and where to

run SLD in my

system landscape?

Learn SLD concepts

How many SLDs?

Synchronization?

Where to run SLD?



©SAP 2007 / Page 61

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 62

Where to Run SLD in Your System Landscape?

4. On which system(s) you want to run your

SLD(s)? 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 thisdecision?

– Which applications do you run thatrely on SLD data?

– High availability

– Planned/unplanned downt ime– Load of the corresponding host

– Network connection

– …

How and where to


Learn SLD concepts

How many SLDs?

Synchronization?

Where to run SLD?



©SAP 2007 / Page 63

Where to Run SLD in Your System Landscape?

For details, seePlanning Guide – SLD



©SAP 2007 / Page 64

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 conf lic t resolu tion

Uni- and bi-directional

Asynchronous propagat ion (able tohandle 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 65

Automatic

Procedure?

Sync of All

SLD Data?

Recommended syncmethod as of next SAPNetWeaver release

Full

Automatic

Sync

Low frequency / low

amount of manuallyentered data has to besynchronized

Export/

Import

Only sync of technicalsystem informationrequired

Automatic

Forwarding

Ideal Use Case?iltering

Possible?

Sync Method

Different sync methods can be combined!

Outlook: Synchronization With Next SAP

NetWeaver Release – Comparison of Sync Options



©SAP 2007 / Page 66

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 o f 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 appl ications) Avai lable as of SAP NetWeaver 7.0 Support Package Stack (SPS) 12

Also for SLD transports

Avai lable wi th SAP NetWeaver 7.0 SPS 13

Alternat ive for Export /Import



©SAP 2007 / Page 67

1. Introduction



4. Topology

5. Summary

Agenda



©SAP 2007 / Page 68

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 i t

Based on your requirements, we offer dif ferent opt ions 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 69

Thank you!

F th I f ti



©SAP 2007 / Page 70

SAP Service Marketplace:

Planning Guide – System Landscape Directory available underhttp://service.sap.com/sld Media Library(How to plan your SLD system landscape)

Post-Installation Guide – System Landscape Directory availableunder http://service.sap.com/sld Media Library

(How to set up SLD in an AS J ava system)

Master Guide – SAP NetWeaver available underhttp://service.sap.com/installnw70(Information about shared services + how to run them together with SLD)

Further Information

F th I f ti Li t f I t t SAP

http://service.sap.com/sld


http://service.sap.com/installnw70

http://service.sap.com/installnw70





©SAP 2007 / Page 71

Further Information – List of Important SAP

Notes for SLD

Describes how you can perform the manual update of thecomponent information and of the CIM model

Updating the SAPComponent Repository

669669

Contains further information about the required number of SLD instances in a landscape and how to synchronize them.

Configuration of the SAPSystem LandscapeDirectory

764393

Gives information about released combinations of SLD serverand SLD client releases.

Compatibility of SLD in thesystem landscape

954820

Describes manual actions you have to perform for SAPNetWeaver Process Integration if you merge multiple SLDs.

Reduce the number of System LandscapeDirectories (SLD)

720717

Describes the consequences of changing the object server,

which could be required to split or merge SLDs.

Importance of “Object

Server”SLD parameter

935245

Describes how you can split an SLD into two or moreinstances.

Splitting an SLD instance936318

Describes how you can merge two SLDs by importing thecontent of one SLD into another SLD.

Grouping SLD instances935474

Descriptionitle

SAP Note

Number

C i ht 2007 SAP AG



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 changedwithout 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 theirrespective 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 andassociated 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 documentcontains 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, orother 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 limitationshall 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 thatyou may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durchSAP AG nicht gestattet. In dieser P ublikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.

Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können 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 erwähnte SAP-Produkte und Servicessowie die dazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Alle anderen in diesem Dokument erwähntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken. Produkte können länderspezifische Unterschiede aufweisen.

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmtenGeschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiertnicht dieRichtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, wederausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zwecksowie für die Gewährleistung der Nichtverletzung geltenden Rechts.

SAP übernimmt keine Haftung für Schäden jeglicher Art, einschließlich und ohne Einschränkung für direkte, spezielle, indirekte oder Folgeschäden im Zusammenhang mit der Verwendung

dieser Unterlagen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit.

Die gesetzliche Haftung bei P ersonenschäden oder die Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinkszugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen überInternetseiten Dritter ab.

Alle Rechte vorbehalten.

Documents

AK iSeries SLD Print