SAP Exchange Infrastructure

SAP Exchange Infrastructure
Integration Directory
Integration Directory: Unit Objectives
After completing this unit, you will be able to: Describe the Configuration Time Activities of the Exchange Infrastructure Detail the task areas and configuration objects of the Integration Directory Create and work with Collaboration Profiles
Design Logical Routings

Work with Collaboration Agreements Completely and correctly configure Integration Scenarios within the Integration Directory
SAP AG 2003, Title of Presentation, Speaker Name / 2
Integration Directory: Business Scenario
The Development Consultants on your project have designed and developed Integration Scenarios and the related objects to enable A2A and B2B communication. You are tasked with configuring these scenarios in the Integration Directory so they can be successfully executed at runtime.
Agenda
Topics
Introduction to SAP XI 3.0 System Landscape Directory Integration Repository Integration Directory Monitoring Adapter Framework Business Process Management Server Administration Security B2B and Industry Standards
Integration Directory XI 3.0
Agenda
XI 3.0 Integration Directory Overview and Concepts Business Scenarios Collaboration Profiles Routing Rules Collaboration Agreements Facilities Cache updates
Agenda
XI Configuration Concept
The goal of the Integration Directory is for the customer to configure the sender-receiver relationships which will be used at runtime.
Service A
Service B
XI 3.0 Integration Directory: Overview

Integration Builder Integration Directory
Business Scenarios
Configuration Wizards Business Processes Collaboration Profiles
Parties , Services & Channels
Adapt integration content to specific configuration Delivered empty, without predefined content
all content is customer-specific
Integration content derived from Integration Repository
Configuration Editors
Routing Rules
Receiver Determination Rules
Open for Customer to add collaboration knowledge relevant to non-SAP components

Home for centralized adapter configuration Data provider for IS runtime
Interface Determination Rules (including Mapping Assignment)
Collaboration Agreements
Sender & Receiver Agreements
Task Areas At Configuration Time

Area in the Integration Directory Collaboration Profile (Objects: Communication Party, Service, Communication Channel) Logical Routing (Objects: Receiver Determination, Interface Determination) Collaboration Agreement (Objects: Sender Agreement, Receiver Agreement) Tasks
In the collaboration profile, you document the technical options available to the communication parties for exchanging messages. Specify the potential senders and receivers of messages and the technical communication paths. In logical routing, you define the flow of messages in a system landscape.
In collaboration agreements, you define the technical details for message processing (for example, adapter configuration) and the security settings for specific sender/receiver pairs.
Collaboration Profile Objects

Services are used to: Represent a technical or business unit, which is to be addressed as the sender or receiver of messages. Group interfaces to exchange messages according to particular task areas. Address business systems and business processes as senders or receivers of messages. A Communication Channel defines how an adapter transforms a message so that it can be processed by the Integration Engine A communication party represents a larger unit which is involved in a cross-system process (for example a company).
Logical Routing Objects
A Receiver Determination defines one or more receivers for a sender and an outbound interface
An Interface Determination specifies which interface is to be used for the inbound processing of a message
Collaboration Agreement Objects
In the sender agreement, you define how the message is to be transformed so that it can be processed by the Integration Engine
In the receiver agreement, you define how the message is to be transformed so that it can be processed by a receiver.
Configuration Model: Overview

0..1 0..* Service Service ... ServiceName
Party Party
... PartyName AlternativeIdentifiers
Service may be: a B2B service a Business System a Process
AlternativeIdentifiers 1 Collaboration Profile Interfaces

0..*
Channel Channel ... ChannelName
Receiver Determination Receiver Determination ...
Interface Determination Interface Determination
AdapterEngine TransportProtocol BusinessProtocol BusinessProtocolVersion SenderAgreement Agreement URL Sender LogonData

SenderParty SenderService SenderInterfaceNamespace SenderInterfaceName ReceiverParty InboundChannel Certificates
...
Receiver Agreement Receiver Agreement ...
SenderParty SenderService SenderInterfaceNamespace SenderInterfaceName ReceiverParty ReceiverService Conditions
Logical Routing
SenderParty SenderService SenderInterfaceNamespace SenderInterfaceName ReceiverParty ReceiverService ReceiverInterfaceNamespace ReceiverInterfaceName MappingProgramName
...
Collaboration Agreement
SenderParty ReceiverParty ReceiverService ReceiverInterfaceNamespace ReceiverInterfaceName OutboundCannel Certificates
Configuration Model: Terminology

What must XI do, so that Ford is Sender Channels Ford able to Sender Interfaces send a Sender Agreements POCreate
XI
CP
What must XI do, so XI is JBL Receiver Channels that able to Receiver Interfaces forward a POCreate Receiver Agreements to JBL
XI must decrypt
SenderAgreement Ford
CA
ReceiverAgreement JBL
XI must encrypt
POCreate
Attention: the notion of Role may be misleading POConfirm In the purchasing scenario, Ford is a buyer and may be a technical sender (POCreate) and a technical receiver (POConfirm) and vice versa RNIF and the Repository scenario knows Roles in the sense of Business Roles
Agenda
XI 3.0 Configuration: Business Scenario

Business Scenario objects (optional): Serve as grouping for related configuration objects Can be derived from the Integration Repository via a wizard Can serve as the basis of the Configuration wizard (Business Scenario Configurator).
Creating Business Scenarios
Configuration Wizard
Add Collaboration Profile objects (Partners, Services, and Communication Channels)
Add Logical Routing objects (Receiver Determination, Interface Determination) and Collaboration Agreement objects (Sender Agreements, Receiver Agreements) or use the Configuration Wizard.
Agenda
XI 3.0 Collaboration Profile: Partner (Party)

The optional object party facilitates the B2B functions of SAP Exchange Infrastructure and contains the following information: A Name and a Description Additional identifiers (DUNS, DUNS+4, GLN) Assigned Services
XI 3.0 Collaboration Profile: Service
Service Objects:
Address business systems and business processes as senders or receivers of messages Serve as grouping of interfaces for message exchange according to particular task areas Contain the following information:
Interfaces (inbound/outbound) Communication channels (sender/receiver)
3 Types Of Service:
Business Service Business System Business Process
XI 3.0 Service Object : Business Service
A Business Service represents an abstract entity for addressing the senders and receivers of messages A Business Service can be used in cross-company processes, for example, if the parties involved have only published their interfaces and not their system landscape, or it is only partly known. With a Business Service, you can define the technical or business subunits of the companies (parties) involved and then assign the relevant interfaces Can be used to group interfaces
XI 3.0 Service Object : Business System
Business System objects are derived directly from existing XI Business Systems in the System Landscape Directory. As such, they contain information about Software Components assigned to the Business System, and which inbound/outbound interfaces are exposed. Can be addressed as a sender or receiver of messages
XI 3.0 Service Object : Business Process

A Business Process can send or receive messages by using Abstract Interfaces
At configuration time, Business Processes are handled as senders and receivers or messages Derived from the Integration Repository where the process is defined
XI 3.0 Collaboration Profile: Channel
Sender or Receiver channel
Communication Channel
Contains specific information for the message protocol, transport protocol, URL, logon data and adapter-specific configuration For configuring specific adapters, pre-delivered communication channels, called channel templates, are available in the Integration Repository
Adapter Types
Abbreviation
XI IDoc RFC http JDBC JMS Marketplace File RNIF
Description
For communicating using the proxy runtime. You can also use this adapter type to communicate with an Adapter Engine at the receiver that is based on XI 2.0 For communicating with an SAP System by using the IDoc adapter For communicating with an SAP System by using the RFC adapter For communicating with http server by using the http adapter For communicating with a database system by using the JDBC adapter For communicating with a messaging system by using the JMS adapter For communicating with marketplaces (see: Marketplace Adapter) For communicating with a file system by using the File/FTP adapter
For connecting to the RNIF protocol (RosettaNet Implementation Framework) by using the RNIF adapter
Agenda
Routing Rule: Receiver Determination
Use the condition editor to enter conditions for routing
Assign one or more receivers to a sender/outbound interface pair. Content-based receiver determination is possible (via XPath/context objects) Receiver should be an existing service (with or without Party).
Routing Rule: Interface Determination
Assign one or more inbound interfaces to be used for the inbound processing of a message (after the receiver determination). Assign an Interface Mapping for each outbound-inbound interface pair
Agenda
XI 3.0 Collaboration Agreement
The objects Sender Agreement and Receiver Agreement
Specify a binding between an interface and a communication channel Contain additional security settings, such as certificates. The sender agreement is used on the Integration Server for inbound processing, the receiver agreement for outbound processing
Header mapping
The header mapping is a part of the collaboration agreement and allows you to overwrite specific fields of the header
Use cases
Overwrite party/service information based on IDoc control record Add payload information to the XI message header Normalization/de-normalization of alternative party identifiers
Content can be provided from Constant value Message Payload Context object
Agenda
Facilities: Configuration Assistant
Configuration Assistant: Internal Communication
Configuration Steps: Specify Inbound Message
Specify Outbound Message

Define Message Processing Confirm Configuration Data
Configuration Assistant: Communication with Partners
Facilities: Business Scenario Configurator
All of the configuration objects that are needed for a given scenario can be created manually; Alternately, you can use the Business Scenario Configuration Wizard to generate all of the objects that are necessary to implement the scenario.
From the Business Scenario Editor, click this icon to start the configuration wizard
Step 1: Select Component View
You assign a Business Scenario From the Integration Repository to use as the basis of the configuration.
Each Role in the Business Scenario is assigned to a Service
Each Connection in the Business Scenario is assigned to an Interface Mapping (if necessary)
Step 2: Assign Services

Use the Left and Right arrows to navigate through all Roles (swim lanes) of the scenario and assign the appropriate service
Assign a service for each Role in the Integration Scenario
Step3: Configure Connections
Use the Left and Right arrows to navigate through the connections
Use the Mapping tab to assign Mappings (where necessary) between interfaces
Step 4: Generate
Specify whether you will simulate or generate the configuration objects
Set the objects to generate
Specify a change list (for generation only)
Start generation
Step 5: Review Generation Log
Review the Generation Log to insure that all objects were created correctly. You have the option of saving the log. When you close the wizard, you will be asked if you want to keep the changes; if you are satisfied with the results of the wizard, save the assignments.
Value Mapping
The Value mapping function provides a specific value transformation. 1. Use the standard function Conversions -> Value mapping to link source and target element 2. Double click to define properties 3. Define access keys for table entries: Value Mapping Context stores information on the origin of the data. If data is maintained in the Integration Directory, use http://sap.com/xi/XI
Agency and Schema for sender and receiver messages. Any arbitrary string value can be used.
Value Mapping
Value Mapping Tool
Integration Server
Mapping Runtime
Mapping Program Value Mapping API
Value Mapping API
ValueMapping Server
Display UI
Integration Directory Integration Directory 3rd party component

Value Mapping Value Mapping Tool Tool Value Mapping Value Mapping Tool Tool
Value Mapping Cache
Preliminary Receiver Determination
Find out at the application level whether a receiver exists for a given outbound interface
Routing rule must be maintained in directory (virtual receiver)
This is done before generating and sending the message at runtime

Avoid unnecessary construction of message Avoid unnecessary parsing of message by runtime engine
Agenda
Cache updates
When Integration Directory objects are activated, the changes are replicated
In the Integration Server runtime cache (accessed via SXI_CACHE) In the CPA cache of each adapter engine (central and de-central)
Bus. Process Engine SXI_CACHE Integration Directory Integration Engine Central Adapter Engine CPA CACHE Decentral Adapter Engine Information about the adapter engines is obtained from the SLD
Decentral Adapter Engine
Cache Notifications
IS Runtime cache
Goto AE Cache to list the connections from the IS to the adapter engines
Integration Directory: Unit Summary
You should now be able to: Describe the Configuration Time Activities of the Exchange Infrastructure Detail the task areas and configuration objects of the Integration Directory Create and work with Collaboration Profiles Design Logical Routings Work with Collaboration Agreements Completely and correctly configure Integration Scenarios within the Integration Directory

SAP Exchange Infrastructure - Integration Directory

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP Exchange Infrastructure - Integration Directory

Uploaded by

Copyright:

Available Formats

Integration Directory: Unit Objectives

Design Logical Routings

SAP AG 2003, Title of Presentation, Speaker Name / 2

Integration Directory: Business Scenario

SAP AG 2003, Title of Presentation, Speaker Name / 3

SAP AG 2003, Title of Presentation, Speaker Name / 4

Integration Directory XI 3.0

SAP AG 2003, Title of Presentation, Speaker Name / 5

Integration Directory XI 3.0

SAP AG 2003, Title of Presentation, Speaker Name / 6

SAP AG 2003, Title of Presentation, Speaker Name / 7

XI 3.0 Integration Directory: Overview

Integration content derived from Integration Repository

Open for Customer to add collaboration knowledge relevant to non-SAP components

Interface Determination Rules (including Mapping Assignment)

SAP AG 2003, Title of Presentation, Speaker Name / 8

Task Areas At Configuration Time

SAP AG 2003, Title of Presentation, Speaker Name / 9

Collaboration Profile Objects

SAP AG 2003, Title of Presentation, Speaker Name / 10

Logical Routing Objects

Collaboration Agreement Objects

SAP AG 2003, Title of Presentation, Speaker Name / 12

Configuration Model: Overview

Service may be: a B2B service a Business System a Process

AlternativeIdentifiers 1 Collaboration Profile Interfaces

Receiver Determination Receiver Determination ...

Interface Determination Interface Determination

AdapterEngine TransportProtocol BusinessProtocol BusinessProtocolVersion SenderAgreement Agreement URL Sender LogonData

Receiver Agreement Receiver Agreement ...

SenderParty SenderService SenderInterfaceNamespace SenderInterfaceName ReceiverParty ReceiverService Conditions

SenderParty SenderService SenderInterfaceNamespace SenderInterfaceName ReceiverParty ReceiverService ReceiverInterfaceNamespace ReceiverInterfaceName MappingProgramName

SenderParty ReceiverParty ReceiverService ReceiverInterfaceNamespace ReceiverInterfaceName OutboundCannel Certificates

SAP AG 2003, Title of Presentation, Speaker Name / 13

Configuration Model: Terminology

Integration Directory XI 3.0

SAP AG 2003, Title of Presentation, Speaker Name / 15

XI 3.0 Configuration: Business Scenario

SAP AG 2003, Title of Presentation, Speaker Name / 16

Creating Business Scenarios

Add Collaboration Profile objects (Partners, Services, and Communication Channels)

SAP AG 2003, Title of Presentation, Speaker Name / 17

Integration Directory XI 3.0

SAP AG 2003, Title of Presentation, Speaker Name / 18

XI 3.0 Collaboration Profile: Partner (Party)

SAP AG 2003, Title of Presentation, Speaker Name / 19

XI 3.0 Collaboration Profile: Service

Interfaces (inbound/outbound) Communication channels (sender/receiver)

Business Service Business System Business Process

SAP AG 2003, Title of Presentation, Speaker Name / 20

XI 3.0 Service Object : Business Service

SAP AG 2003, Title of Presentation, Speaker Name / 21

XI 3.0 Service Object : Business System

SAP AG 2003, Title of Presentation, Speaker Name / 22

XI 3.0 Service Object : Business Process

SAP AG 2003, Title of Presentation, Speaker Name / 23

XI 3.0 Collaboration Profile: Channel

Sender or Receiver channel

SAP AG 2003, Title of Presentation, Speaker Name / 24

SAP AG 2003, Title of Presentation, Speaker Name / 25

Integration Directory XI 3.0

SAP AG 2003, Title of Presentation, Speaker Name / 26