7/30/2019 PI FastTrackCourse SLD

1/16

USIPI- PI Fast Track Course

Fed 2010

SAP NetWeaver- Process Integration

System landscape Directory

7/30/2019 PI FastTrackCourse SLD

2/16

2009 Deloitte Touche Tohmatsu2

Objectives of the Session

Benefits of Process Integration .

Describes Application Platform Suite .

Describes Various Components in Process Integration.

Purpose of System Landscape Directory .

Describes Software Catalogs, Products and Component Version.

Describes Technical and Business System.

7/30/2019 PI FastTrackCourse SLD

3/16

2009 Deloitte Touche Tohmatsu3

Mission

SAP PI is an Integration technology and Platform

for SAP and non SAP Application.

for A2A and B2B scenarios .

for asynchronous and synchronous communication.

for cross-component Business Process Management.

7/30/2019 PI FastTrackCourse SLD

4/16

2009 Deloitte Touche Tohmatsu

Advantages

Out of Box Integration.

Versioning and modification management of integration meta-data.

Openness and interoperability .

Use open XML based standards for Integration .

Loose coupling via XML messaging .

Leverage existing Investments.

Arrive at new integration landscape in an evolutionary manner.

Allow easy and non-disruptive addition of new services and Processes .

SAP Solutions bring integration meta data such as SRM ,MDM ,BI ..

4

7/30/2019 PI FastTrackCourse SLD

5/16

2009 Deloitte Touche Tohmatsu5

Overview SAP Application Platform Suite

Integration across technology

and origination boundaries.

Full .NET and J2EE

interoperability .

Powers business Readysolutions that reduce custom

integration .

Enterprise Services Architecture

increases business process

flexibility .

7/30/2019 PI FastTrackCourse SLD

6/16

2009 Deloitte Touche Tohmatsu

Overview- SAP Application Platform Suite

6

People Integration

People Integration brings together the right

functionality and the right information to the rightpeople.

Portal provides industry-leading portal technology

that delivers unified, personalized, and role-based

user access to heterogeneous IT environment.

Information Integration

Information integration provides company with both

structured and unstructured information that isconsistent and accessible.

Application Integration

The Application Server provides a complete

development infrastructure to develop, distribute, and

execute platform-independent, robust, and scalable

Web services and business applications.

The Application Server supports ABAP, Java, and

Web services.

Process Integration

The Integration Broker provides a technical

infrastructure for XML-based message exchange to

enable the integration of SAP systems with SAP and

non-SAP systems.

7/30/2019 PI FastTrackCourse SLD

7/16 2009 Deloitte Touche Tohmatsu7

Overview-Architecture of SAP PI

PI is collection of components, work together flexibly to

implement integration scenario.

Architecture includes components to be used at Design time,

Configuration time and at Run Time.

7/30/2019 PI FastTrackCourse SLD

8/16 2009 Deloitte Touche Tohmatsu

Overview-Architecture of SAP PI

8

ES Integration Repository

Central repository define, access, and manage

SOA assets as services, data types.

Repository stores the definitions and metadata of

enterprise services and business processes.

Integration Directory

Configure business process ,modeled and

specified in the ES Repository.

Logical routing, technical routing, and mapping are

all configured for a particular configuration scenario

and a specific system landscape.

Integration Server

Distribute the messages received according to the

rules ,configured in the Integration Directory.

Messages can be exchanged between all systems in

a heterogeneous system landscape

SLD & Monitoring

SLD is a Central Repository of Information aboutSoftware and System in Data Center.

Monitoring Provides Comprehensive and Focused

View of all Components and Processes atRuntime.

7/30/2019 PI FastTrackCourse SLD

9/16

2009 Deloitte Touche Tohmatsu9

SLD-System Landscape Directory

SLD stores information about all

installable and installed components ofa system landscape.

SLD is based on the Common

Information Model (CIM) standard.

The Common Information Model (CIM)

is standard of the Distributed

Management Task Force (DMTF) and

is based on the object-oriented

modeling approach. For example CIM

class SAP Product can have instances

such as my SAP CRM and R/3.

Content of the Master Component

Repository will be published on the

service market place due to this

customer can update their individual

component information

7/30/2019 PI FastTrackCourse SLD

10/16

2009 Deloitte Touche Tohmatsu

SLD-Catalogs

10

SLD

Catalogs

Software Catalog System Catalog

Logical View

(Business System)Physical View

(Technical System)

The SLD contains a software catalog of all

installable SAP products and software

components.

Information from Software catalog used in

Repository to Organize development efforts

The SLD contains a system catalog describes the system in

the data center from two perspective a logical view (Business

System ) and Physical view(Technical System).

Information from System catalog used in Integration Directory

to drive specific configuration of Integration scenarios

7/30/2019 PI FastTrackCourse SLD

11/16

2009 Deloitte Touche Tohmatsu11

SLD-Products and Versions

Product

A collection of all versions of a product. A

product is a unit that is delivered,

In an SAP environment, a product correspondsto an SAP technical component.

Example SAP R/3,SAP ECC

Software Component

A collection of all versions of a software component.

Unit of software Delivery that has it own support

package track . Example SAP_APPL,SAP_HR.

A particular version of a

product Example 4.6C,4.6d

Product VersionSoftware Component Version

Software Product composed of one

or more software components .

For instance R/3 version 4.6C hascomponents SAP_HR,SAP_BASIS.

Software Unit

Relationship between a software Product and its

constituent components is described in SLD by an

association.

7/30/2019 PI FastTrackCourse SLD

12/16

2009 Deloitte Touche Tohmatsu12

SLD- Business and Technical Systems

Technical systems are application systems that are installed in system landscape.

An example of an application system is an SAP Customer Relationship Management (CRM) server.

Business systems are logical systems, which function as senders or receivers within SAP

NetWeaver Process Integration.

Business systems can be SAP systems or third-party systems. An example of business system,

which is associated with a client of an AS ABAP

The association between Technical System and Business System is Dependent on Technical

System type ; for instance system based on SAP Web ASABAP each client in the system is a

Separate Business System

7/30/2019 PI FastTrackCourse SLD

13/16

2009 Deloitte Touche Tohmatsu13

SLD elements Role in Integration Repository

SLD ESR

Design objects in ESR is organized by Software Component Version, logically belongs

to a particular version.

For example MATMAS03 IDOC used from SAP system version 4.0 onwards but

MATMAS05 is used from 4.7 onwards and IDOC is belongs to software component

SAP APPL.

7/30/2019 PI FastTrackCourse SLD

14/16

2009 Deloitte Touche Tohmatsu14

SLD elements Role in Integration Directory

Routing Relations in ID Point to the Business System that are maintained in the System Catalog

of SLD and through associated to the technical Systems.

7/30/2019 PI FastTrackCourse SLD

15/16

2009 Deloitte Touche Tohmatsu15

SLD Object Structure

Products are collection of software Components .

Products are installed on Technical System .

Application communication with Business System provides a

Logical View of systems Participating in a Particular Integration

Scenario

7/30/2019 PI FastTrackCourse SLD

16/16

2009 Deloitte Touche Tohmatsu