SAP NetWeaver- Process Integration

Integration Directory

USIPI- Accelerated PI Traning course Fed 2010

Objectives of the Session

Overview of Integration Directory. Describes Various communication types. Details the task areas and Configuration objects. Routing Concepts. Object References. Describes Outbound & Inbound Process.

2009 Deloitte Touche Tohmatsu

ID Integration Directory
ID Used to Configure Business Scenario created at Design time . ID determines Identity systems involved in integration scenario. how messages are exchanged within this system landscape (routing).

Supported Communication Types Communication using the Integration Server. Communication using the Advanced Adapter Engine. Direction communication (point-to-point).

Message sent from system 1a to the integration broker and forwarded from there to systems 2a-c

2009 Deloitte Touche Tohmatsu

Overview
Communication Profile describes technical sender and receiver options using communication parties, services, communication components and communication channels. Receiver Determinations specify the receiver or receivers of a message. The communication components can be a business system, an integration process, or a service for a B2B communication. Interface Determinations Assignment of a receiver interface to a sender interface In a sender or receiver agreement define which communication channel to use to process messages for a particular combination of senders and receivers Configuration Scenarios Grouping of all configuration objects by the scenario in which they are required

2009 Deloitte Touche Tohmatsu

Use of the Terms Outbound and Inbound

When used in the context of design time objects, the terms outbound/inbound refer to the perspective of the application.

When used in the context of configuration time objects, the terms outbound/inbound refer to the perspective of the integration broker.

2009 Deloitte Touche Tohmatsu

Configuration Objects - Integration Server Communication

Configuration Tasks
Define collaboration profile

Configuration Objects
Communication Party Communication Component Communication Channel

Configuring inbound processing on the Integration Server Define routing

Sender agreement Receiver determination Interface determination Receiver rule

Configuring outbound processing on the Integration Server

6

Receiver agreement
2009 Deloitte Touche Tohmatsu

Configuration Objects Advanced Adapter Engine

Configuration Tasks
Define collaboration profile

Configuration Objects
Communication Party Communication Component Communication Channel Integrated configuration

Define integrated configuration

2009 Deloitte Touche Tohmatsu

Configuration Objects Direct Communication

Configuration Tasks
Define collaboration profile

Configuration Objects
Communication Party Communication Component Communication Channel Direct Connection

Define Direct Connection

2009 Deloitte Touche Tohmatsu

Collaboration Profile Objects

Represents a company unit involved and addressed in message exchange.

Represents a entity used to address a sender or receiver of messages.

Defines how an adapter transforms a message during inbound or outbound processing.

2009 Deloitte Touche Tohmatsu

Logical Routing Objects

Defines one or more receivers for an sender and an outbound interface

Represents a entity used to address a sender or receiver of messages.

Specifies interface to be used for an inbound processing message .

10

2009 Deloitte Touche Tohmatsu

Collaboration Agreement Objects

Inbound processing of a message for a particular sender/receiver pair

Outbound processing of a message for a specific sender-receiver pair.

11

2009 Deloitte Touche Tohmatsu

Object References (Configuration Objects)

12

2009 Deloitte Touche Tohmatsu

Routing Routing Content-Based Routing Message Split

Interface Split Mapping-Based Message Split Routing the Split Messages to Different Receiver Systems

13

2009 Deloitte Touche Tohmatsu

Routing : Content-Based Routing

In many business cases, it is necessary to define conditions with which the receivers of a message are determined during routing for example If the value of a specific field in the message is x, then forward the message to receiver y. At configuration time, you can define conditions that depend on the content of the message. This can be done by receiver determinations and interface determinations.

14

2009 Deloitte Touche Tohmatsu

Routing : Content-Based Routing ---Procedure

Inserting a receiver rule into a receiver determination

Expression editor to specify a payload element Inserting a receiver rule into a receiver determination

15

2009 Deloitte Touche Tohmatsu

Routing : Message Split

Interface split

Message split based on a 1:n multi-mapping

16

2009 Deloitte Touche Tohmatsu

Routing : Message Split

Configuring a message split with different receiver systems

17

2009 Deloitte Touche Tohmatsu

Defining Inbound Processing

Defining the inbound processing of a message coming in a sender agreement

Routing of an incoming message to three receiver systems 2a-c

18

2009 Deloitte Touche Tohmatsu

Defining Inbound Processing

Routing of an incoming message to a particular inbound interface of a receiver system

19

2009 Deloitte Touche Tohmatsu

Defining Outbound Processing

Defining the outbound processing of a message in a receiver agreement

20

2009 Deloitte Touche Tohmatsu

Adapter Types
Application Adapters Industry Standard Adapters
Rosetta Net (RNIF 1.1) Adapter Rosetta Net (RNIF 2.0) Adapter CIDX (RNIF 1.1) Adapter

Technical Adapters

RFC Adapter IDoc Adapter

Connectivity with WS providers and WS consumers (WS channel) File/FTP Adapter (file system, FTP servers) Database (JDBC) Adapter

Java Messaging Service (JMS) Adapter

SOAP Adapter "Plain HTTP" Adapter Mail Adapter (mail servers using SMTP, IMAP4, POP3) SAP Business Connector Adapter (SAP BC) Marketplace Adapter (mySAP marketplaces)

21

2009 Deloitte Touche Tohmatsu

Calling Process Integration Start Page

Call transaction SXMB_IFR in the SAP system of the Integration Server. The URL of the PI start page in general is: http://<host name of Integration Server>:<HTTP port>/dir.

22

2009 Deloitte Touche Tohmatsu

 2009 Deloitte Touche Tohmatsu