1_pi overview & sld

7/30/2019 1_PI Overview & SLD

1/18

Mar 2010

SAP NetWeaver PI TrainingAccelerated..


2/18

2009 Deloitte Touche Tohmatsu2

Objectives

Theory Both Basic and Advanced

Hands-on


3/18

SAP NetWeaver- Process Integration

PI Overview andSystem Landscape Directory (SLD)


4/18


Objectives of the Session

What is PI?

Application Platform Suite

Components in Process Integration

System Landscape Directory (SLD)

SLD Components


5/18


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


6/18

2009 Deloitte Touche Tohmatsu

Advantages

Serves as Enterprise Service Bus

Reliable, Scalable and Stable

Openness and interoperability

Loose coupling via XML messaging

Leverage existing Investments

Arrive at new integration landscape in an evolutionary manner

Easy and non-disruptive addition of new services and Processes

Pre-delivered integration content for SAP Solutions SAP guarantees the integration

6


7/18 2009 Deloitte Touche Tohmatsu

Disadvantages

Complex set up

Two Engines : ABAP + JAVA

Fine tuning often requires support from SAP

Large volumes although the latest version does have significant performance

improvement measures

Pricing based on Volume of Non-SAP data

Resource Skills Difficult to find

7


8/18 2009 Deloitte Touche Tohmatsu8

Overview SAP Application Platform Suite

People Integration

People Integration brings together the right

functionality and the right information to the right

people

Information Integration

Information integration provides company with both

structured and unstructured information that is

consistent and accessible

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.

Application Integration

The Application Server provides a completedevelopment infrastructure to develop, distribute,

and execute platform-independent, robust, and

scalable Web services and business applications.


9/18


Overview-Architecture of SAP PI

PI is collection of components, that work together flexibly to

achieve process integration.

Architecture includes components to be used at Design time,

Configuration time and at Run Time.


10/18


Overview-Architecture of SAP PI

10

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.


11/18


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 The customer

can update their individual component

information


12/18


SLD-Catalogs

12

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


13/18


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.


14/18


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


15/18


SLD elements Role in Integration Repository

SLD ESR

Design objects in ESR, organized by Software Component Version, logically belong 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 belongs to software component

SAP APPL.


16/18


SLD elements Role in Integration Directory

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

of SLD


17/18


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


18/18


1_pi overview & sld

Documents