SAP Exchange

Infrastructure

System Landscape Directory

Lecture topics

Topics
XI Overview
System Landscape Directory
Integration Repository
Integration Directory
Runtime
Runtime Workbench
Adapter Framework
Business Process Management
Server Administration
Security
B2B and Industry Standards
SAP AG 2004, System Landscape Directory, 2

System Landscape Directory: Objectives

After completing this lesson, you will be able to:

z Explain the purpose of the System Landscape
Directory and its role as an information provider.
z Describe the content types in the System
Landscape Directory.
z Create Software Component descriptions in the
System Landscape Directory.
z Define Technical Systems in the System Landscape
Directory.
z Define Business Systems in the System Landscape
Directory.

SAP AG 2004, System Landscape Directory, 3

System Landscape Directory Overview

Central information provider for NetWeaver system landscapes
Manage software components and platform dependencies
Facilitate Installations, upgrades and transports
Based on Common Information Model (CIM) of the Distributed
Management Task Force (DMTF)

Basis for SAP Solution Manager

Information provider for SAP XI

SAP AG 2004, System Landscape Directory, 4

The System Landscape Directory is a central repository of information about

software and systems in the data center, expressed in a standard schema called
the Common Information Model, or CIM.
CIM was developed by the Distributed Management Task Force, or DMTF, an
industry consortium whose goal is to enable management of IT systems in
distributed environments using web standards.
For more information, see www.dmtf.org.

Aspects of system landscapes

SAP AG 2004, System Landscape Directory, 5

System Landscapes have 3 dimensions: the solution dimension (i.e., what

software processes are installed), the transport dimension (DEV, QAS, and PRD,
for instance), and the technical dimension (what products are installed on which
hosts on particular networks).
The SLD should capture all three dimensions of the System Landscape.

SLD content type

Component Information

Describes building blocks of solutions

Describes possible combinations and dependencies

Delivered by SAP, extensible by customer

Landscape Description

Information on installed landscape elements

Customer-specific

SAP XI utilizes both types of content:

Integration Repository: Component Information
Integration Directory: Landscape Description

SAP AG 2004, System Landscape Directory, 6

There are two main areas of content in the SLD: the software catalog, and the
systems catalog.
The Software catalog describes the installed products and their constituent
components. The software catalog is delivered with content about all SAP
products. Customers and Partners can extend this catalog with information about
software from other vendors.
The Systems catalog describes the systems in the data center from two
perspectives: a logical view (business systems) and a physical view (technical
systems). In other words, the Systems catalog describes the concrete
implementation of the customer landscape.
Information from the software catalog is used in the Integration Repository to
organize development efforts. Information from the systems catalog is used in the
Integration Directory to drive the specific configuration of Integration scenarios.

System Landscape Directory

Applications
Applications and
and Tools
Tools
Graphical
Design Tool

PPMS

..

..

..

Technical
Technical
Configuration
Configuration
..

Validation
Validation
Registration
..

Software
Software
Logistics
Logistics
..

..
1

..

..

Synchronize, XML
Master
Master
Component
Component
Repository
Repository

System
System Landscape
Landscape
Directory
Directory

Any
Any Landscape
Landscape
Element
Element
Customer
Customer Landscape
Landscape

Landscape
WBEM,
Landscape
XML
description
description
CIM
CIM

Component
Types
Landscape
Patterns

Update
Possible
Combinations

SAP

Component
WBEM,
Component
XML
information
information
CIM
CIM

rd-Party
33rd
-Party // Customer
Customer
Component
Component Types
Types

Customer

SAP AG 2004, System Landscape Directory, 7

Importing / synchronizing PPMS-data as XML-file into the Master Component

Repository at the SAP-site. Therefore the Master Component Repository contains
up-to-date information about all available SAP products.
The content of the Master Component Repository will be published on the Service
Marketplace so that customers can update their individual component information.
Customers can insert additional information about 3rd-party products which are in
operation by them into their individual component information.
The landscape description contains information about all installed products /
components at customers site.
Applications and tools (installation, administration etc.) can use information from
the System Landscape Directory as a central information provider.

SLD: Products and Software Components

Product

Software Component

0..1

0..1

Product Version

Software Component Version

Software Feature

SAP AG 2004, System Landscape Directory, 8

A Software Product (such as SAP R/3) may exist in multiple versions (such as
4.6c, 4.6d, 4.7 .
A Software Component is a unit of software delivery that has its own support
package track. Example of Software Components are SAP_APPL, SAP_ABA,
SAP_HR, etc.
A Software Product is composed of one or more software components. For
instance, the product R/3 version 4.6C has components:
z SAP BASIS
z SAP APPL
z SAP ABA
z SAP HR
z SAP GUI

The relationship between a software product and its constituent components is

described in the SLD by an association called a Software Feature.

Example: SAP APO

SAP AG 2004, System Landscape Directory, 9

An example of the relationship between software product version and its

components: SAP APO v. 3.1.

Example: workshop exercise

Product

Software Feature:
Associations

Software Component

1
n

Product Version

TBIT40_WORKSHOP
of SAP
TBIT40_WORKSHOP, 1.0
of SAP

Software Component
Version

TBIT40_WORKSHOP ##
of SAP
TBIT40_WORKSHOP ##, 1.0
of SAP

SAP AG 2004, System Landscape Directory, 10

This workshop uses the above Software Product and Component for organizing
development work.

Defining the Software Component

To define a Software Component:

From the main screen of the SLD,
choose Software Catalog.
Use the drop-down to select the
Software Components type, and then
select New Component to start the
wizard.

Select the Product from the drop-down

Enter the software vendor
Enter the Software Component Name
Enter the Software
Component version (SWCV)
Choose Create
SAP AG 2004, System Landscape Directory, 11

Defining third-party Products and Software Components is easy in the SLD,

because there are wizards to guide you through the process.

SLD: Technical System

Technical System
WebAS ABAP
Name; host name; system number; Release
Installed clients

Business System

Message Server
Installed Products
WebAS Java
Name; host name; SID; System Home
Standalone JAVA
Technical System ID
Third Party

Business Systems
Business Systems

Installed Products

SAP AG 2004, System Landscape Directory, 12

In the Systems Catalog we define each Technical System in the landscape. The
Technical System correlates the software to the physical host on which it is
installed. The exact settings for each System depend on the system type.
Technical systems are the basis for defining Business Systems. The association
between the Technical system and the Business System is dependent on the TS
type; for instance, in a system based on SAP Web AS (ABAP), each client in the
system is a separate Business System (this corresponds to the notion of a client
as a Logical System in ALE configuration).

Defining the Technical System

From the Technical System browser choose New
Technical System

specify the Technical System Type

select (and add) the products and

components that are installed on the
technical system...

click Finish.
SAP AG 2004, System Landscape Directory, 13

To create a Technical System definition there is a wizard interface in the SLD.

You can launch the wizard from the Technical System browser (from the main
screen of the SLD, choose Technical Landscape under System Landscape). In
the Technical System browser there is a button labeled New Technical System
that starts the wizard.
The exact data to define the technical system depends on the Technical System
type (see previous slide). For the workshop exercises you will create a ThirdParty system type. Choose the appropriate system type and click Next.
In the subsequent screen(s), you will enter the specific details of the Technical
System (dependent on type); for the workshop exercises, we are using a thirdparty type and therefore need only detail the installed products. Of course, a
technical system may have multiple products installed on it.
A product may be installed on a system without all of its possible components. For
instance, the SWCV Internet Transaction Server (ITS) version 4.6C is a
component of the product SAP R/3 version 4.6C; but it is possible to have a 4.6C
system that is not using ITS. The wizard allows you choose the specific
components associated with a system as follows:
For each selected product, the associated SWCVs will be listed with checkboxes;
you can deselect any components that are not part of the installation.

SLD: Business System

Business System
WebAS ABAP
Related Integration Server
client

Technical System

Installed Products
WebAS Java
Related Integration Server
Name
Third Party Systems

Technical System
Technical System

Related Integration Server

Installed Products
Standalone Java
Name

Technical System

SAP AG 2004, System Landscape Directory, 14

The Business System definition points to the appropriate Technical System. The
SLD makes the appropriate association.

Defining the Business System

Give the system a unique name

specify the associated Technical System

(and Logical System, if necesary)
select the installed products
(from the technical system
definition)

and the Related Integration Server

click Finish.
SAP AG 2004, System Landscape Directory, 15

For defining Business Systems, the four important pieces of data are:
Business System Name (must be unique in the landscape).
Associated Technical System, and if the Business System will be used with IDOC interfaces, a
Logical System Name. Note that multiple Business Systems can be defined off of a single
technical system (for instance, each numbered client of an SAP system is a unique Business
System). The logical system name is mandatory in case the Business system will act as a
sender or receiver of IDocs. In this case it should match exactly the logical system name as
defined in the SAP client (if the Business system is of type WebAS-ABAP). The IDoc adapter
will make use of this entry to resolve a Business system name into an ALE logical system
name and vice-versa.
The Software Products (and associated SWCVs) that are used by the Business System. The
products are brought through from the Technical System definition; but for a particular
Technical System, not all products will necessarily be associated with a particular Business
System. For instance, you may install mySAP SRM and mySAP CRM solutions as separate
clients on a single (technical) system; but the Business System definition for each would only
include the appropriate product (SAP SRM or SAP CRM).
The Related Integration Server. Application systems are associated with particular Integration
Servers, which makes change management in the XI landscape easier.

All of these settings can be defined in the Business System wizard.

SLD and XI Integration Repository

Integration Repository (Design)

Software Component
Version
Business Scenario
Application Component
Role
Product Version

System Landscape Directory

Mapping Objects
Product
Interface Objects

Product Version
Software Component
Software Component Version

SAP AG 2004, System Landscape Directory, 16

All design work in the Integration Repository is organized by Software Component

Version. This makes sense, as interfaces logically belong to a software
component and to a particular version. For instance, a BOMMAT03 IDOC is used
by SAP systems from version 4.0 on, but a BOMMAT05 IDOC is used by SAP
systems from 4.7 on. And, more specifically, the IDOC specifically belongs to the
software component SAP APPL (which is why a BOMMAT IDOC does not exist in
a Web AS with no application layer).
Before development can begin, the Software Component Versions (SWCVs) ust
be imported from the SLD to the Integration Repository.
Additionally, when we design business scenarios in the Integration Repository, the
Application Components that we assign in the scenario editor are assigned from
Product Versions in the SLD.

SLD and Repository: usage dependencies

SAP Integration Builder
Repository (Design)

A dependency can be defined in the SLD

This dependency will be automatically
detected in the Integration Repository

Software Component
Version A

...

Basis objects
System Landscape Directory
X
Software Component Version A
Software Component
Version B

Software Component Version B

Usage Dependency

X
SAP AG 2004, System Landscape Directory, 17

SLD and Directory

SAP Integration Directory (Configuration)

Routing Relations
Sender Service:

Business System

Receiver Service:

Business System

System Landscape Directory

A service object in the Integration
Directory can be derived from the SLD.
Business System
Technical System

SAP AG 2004, System Landscape Directory, 18

Routing Relations in the Integration Directory point to the Business Systems that
are maintained in the System Catalog of the SLD, and through the appropriate
association, to the technical systems.

Summary: object structure in SLD

SAP AG 2004, System Landscape Directory, 19

To summarize: Products are collections of Software Components; both Software

Products and Components exist in versions.
Products are installed on Technical Systems, which describe the concrete
structure of Systems in the Data Center.
Applications communicate with Business Systems, which provide a logical view of
the system that participate in a particular Integration Scenario.

System Landscape Directory: Summary

You should now be able to:

z Explain the purpose of the System Landscape
Directory and its role as an information provider.
z Describe the content types in the System Landscape
Directory.
z Create Software Component descriptions in the
System Landscape Directory.
z Define Technical Systems in the System Landscape
Directory.
z Define Business Systems in the System Landscape
Directory.

SAP AG 2004, System Landscape Directory, 20