View
234
Download
0
Category
Preview:
Citation preview
7/30/2019 SAP Exchange Infrastructure- Integration Directory
1/49
SAP ExchangeInfrastructure
Integration Directory
7/30/2019 SAP Exchange Infrastructure- Integration Directory
2/49
SAP AG 2003, Title of Presentation, Speaker Name / 2
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
Integration Directory: Unit Objectives
7/30/2019 SAP Exchange Infrastructure- Integration Directory
3/49
SAP AG 2003, Title of Presentation, Speaker Name / 3
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 inthe Integration Directory so they can be successfully
executed at runtime.
Integration Directory: Business Scenario
7/30/2019 SAP Exchange Infrastructure- Integration Directory
4/49
SAP AG 2003, Title of Presentation, Speaker Name / 4
Topics
Agenda
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
7/30/2019 SAP Exchange Infrastructure- Integration Directory
5/49
SAP AG 2003, Title of Presentation, Speaker Name / 5
Agenda
Integration Directory XI 3.0
XI 3.0 Integration Directory
Overview and Concepts
Business Scenarios
Collaboration Profiles
Routing Rules
Collaboration Agreements
Facilities
Cache updates
7/30/2019 SAP Exchange Infrastructure- Integration Directory
6/49
SAP AG 2003, Title of Presentation, Speaker Name / 6
Agenda
Integration Directory XI 3.0
XI 3.0 Integration Directory
Overview and Concepts
Business Scenarios
Collaboration Profiles
Routing Rules
Collaboration Agreements
Facilities
Cache updates
7/30/2019 SAP Exchange Infrastructure- Integration Directory
7/49 SAP AG 2003, Title of Presentation, Speaker Name / 7
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
BService A
7/30/2019 SAP Exchange Infrastructure- Integration Directory
8/49 SAP AG 2003, Title of Presentation, Speaker Name / 8
XI 3.0 Integration Directory: Overview
Integration Directory
Adapt integration content tospecific configuration
Delivered empty, withoutpredefined content
all content is customer-specific
Integration content derivedfrom Integration Repository
Open for Customer to addcollaboration knowledgerelevant to non-SAPcomponents
Home for centralized adapterconfiguration
Data provider for IS runtime
Integration Builder
Integration Directory
Business Processes
Routing Rules
Business Scenarios
Receiver Determination Rules
Interface Determination Rules
(including Mapping Assignment)
Configuration
Editors
Configuration
Wizards
Collaboration Profiles
Parties , Services
& Channels
Collaboration Agreements
Sender & Receiver Agreements
7/30/2019 SAP Exchange Infrastructure- Integration Directory
9/49 SAP AG 2003, Title of Presentation, Speaker Name / 9
Task Areas At Configuration Time
Area in the Integration
Directory
Tasks
Collaboration Profile
(Objects:
Communication Party,
Service,
Communication Channel)
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.
Logical Routing
(Objects:
Receiver Determination,
Interface Determination)
In logical routing, you define the flow of messages
in a system landscape.
Collaboration Agreement
(Objects:
Sender Agreement,
Receiver Agreement)
In collaboration agreements, you define thetechnical details for message processing (for
example, adapter configuration) and the security
settings for specific sender/receiver pairs.
7/30/2019 SAP Exchange Infrastructure- Integration Directory
10/49 SAP AG 2003, Title of Presentation, Speaker Name / 10
Collaboration Profile Objects
A communication party
represents a larger unit which is
involved in a cross-system
process (for example acompany).
Services are used to:
Represent a technical or
business unit, which is tobe 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 sothat it can be processed by
the Integration Engine
7/30/2019 SAP Exchange Infrastructure- Integration Directory
11/49 SAP AG 2003, Title of Presentation, Speaker Name / 11
Logical Routing Objects
A Receiver
Determination definesone 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
7/30/2019 SAP Exchange Infrastructure- Integration Directory
12/49 SAP AG 2003, Title of Presentation, Speaker Name / 12
Collaboration Agreement Objects
In the receiver agreement,
you define how the message
is to be transformed so that it
can be processed by a
receiver.
In the sender agreement, you
define how the message is to
be transformed so that it can
be processed by the
Integration Engine
7/30/2019 SAP Exchange Infrastructure- Integration Directory
13/49 SAP AG 2003, Title of Presentation, Speaker Name / 13
Collaboration Profile
Logical RoutingCollaboration
Agreement
...
Sender Agreement
...
Receiver Agreement
Configuration Model: Overview
SenderParty
SenderServiceSenderInterfaceNamespace
SenderInterfaceName
ReceiverParty
InboundChannel
Certificates
Sender Agreement
SenderParty
ReceiverPartyReceiverService
ReceiverInterfaceNamespace
ReceiverInterfaceName
OutboundCannel
Certificates
Receiver Agreement
...
Interface Determination
...
Receiver Determination
SenderParty
SenderServiceSenderInterfaceNamespace
SenderInterfaceName
ReceiverParty
ReceiverService
Conditions
Receiver Determination
SenderParty
SenderServiceSenderInterfaceNamespace
SenderInterfaceName
ReceiverParty
ReceiverService
ReceiverInterfaceNamespace
ReceiverInterfaceName
MappingProgramName
Interface Determination
... ...
...
Party Service
1
0..*
Channel
0..1 0..*
ServiceName
AlternativeIdentifiers
Interfaces
Service
PartyName
AlternativeIdentifiers
Party
Service may be:
a B2B service
a Business System
a Process
ChannelName
AdapterEngine
TransportProtocol
BusinessProtocol
BusinessProtocolVersion
URL
LogonData
Channel
7/30/2019 SAP Exchange Infrastructure- Integration Directory
14/49 SAP AG 2003, Title of Presentation, Speaker Name / 14
Ford JBL
POCreate
POConfirm
XI
CP
CA
Configuration Model: Terminology
Ford JBL
What must
XI do, so
that Ford is
able tosend a
POCreate
What must
XI do, so
that XI is
able to
forward a
POCreate
to JBL
SenderAgreement ReceiverAgreement
XI must
decryptXI must
encrypt
Sender Channels
Sender InterfacesSender Agreements
Receiver Channels
Receiver InterfacesReceiver Agreements
Attention: the notion of Role may be misleading
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
7/30/2019 SAP Exchange Infrastructure- Integration Directory
15/49 SAP AG 2003, Title of Presentation, Speaker Name / 15
Agenda
Integration Directory XI 3.0
XI 3.0 Integration Directory
Overview and Concepts
Business Scenarios
Collaboration Profiles
Routing Rules
Collaboration Agreements
Facilities
Cache updates
7/30/2019 SAP Exchange Infrastructure- Integration Directory
16/49 SAP AG 2003, Title of Presentation, Speaker Name / 16
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).
XI 3.0 Configuration: Business Scenario
7/30/2019 SAP Exchange Infrastructure- Integration Directory
17/49 SAP AG 2003, Title of Presentation, Speaker Name / 17
Creating Business Scenarios
Add Collaboration Profile objects (Partners,
Services, and Communication Channels)
Add Logical Routing objects (ReceiverDetermination, Interface Determination) and
Collaboration Agreement objects (Sender
Agreements, Receiver Agreements) or use
the Configuration Wizard.
ConfigurationWizard
7/30/2019 SAP Exchange Infrastructure- Integration Directory
18/49 SAP AG 2003, Title of Presentation, Speaker Name / 18
Agenda
Integration Directory XI 3.0
XI 3.0 Integration Directory
Overview and Concepts
Business Scenarios
Collaboration Profiles
Routing Rules
Collaboration Agreements
Facilities
Cache updates
7/30/2019 SAP Exchange Infrastructure- Integration Directory
19/49
SAP AG 2003, Title of Presentation, Speaker Name / 19
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
7/30/2019 SAP Exchange Infrastructure- Integration Directory
20/49
SAP AG 2003, Title of Presentation, Speaker Name / 20
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
7/30/2019 SAP Exchange Infrastructure- Integration Directory
21/49
SAP AG 2003, Title of Presentation, Speaker Name / 21
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
7/30/2019 SAP Exchange Infrastructure- Integration Directory
22/49
SAP AG 2003, Title of Presentation, Speaker Name / 22
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/outboundinterfaces are exposed.
Can be addressed as a sender or receiver of messages
7/30/2019 SAP Exchange Infrastructure- Integration Directory
23/49
SAP AG 2003, Title of Presentation, Speaker Name / 23
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 C ll b ti P fil Ch l
7/30/2019 SAP Exchange Infrastructure- Integration Directory
24/49
SAP AG 2003, Title of Presentation, Speaker Name / 24
XI 3.0 Collaboration Profile: 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
Sender o r
Receiver channel
Ad t T
7/30/2019 SAP Exchange Infrastructure- Integration Directory
25/49
SAP AG 2003, Title of Presentation, Speaker Name / 25
Adapter Types
Abbreviation Description
XI
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
IDoc For communicating with an SAP System by using the IDoc adapter
RFC For communicating with an SAP System by using the RFC adapter
http For communicating with http server by using the http adapter
JDBC For communicating with a database system by using the JDBC adapter
JMS For communicating with a messaging system by using the JMS adapter
Marketplace For communicating with marketplaces (see: Marketplace Adapter)
File For communicating with a file system by using the File/FTP adapter
RNIFFor connecting to the RNIF protocol (RosettaNet Implementation
Framework) by using the RNIF adapter
I t ti Di t XI 3 0
7/30/2019 SAP Exchange Infrastructure- Integration Directory
26/49
SAP AG 2003, Title of Presentation, Speaker Name / 26
Agenda
Integration Directory XI 3.0
XI 3.0 Integration Directory
Overview and Concepts
Business Scenarios
Collaboration Profiles
Routing Rules
Collaboration Agreements
Facilities
Cache updates
R ti R l R i D t i ti
7/30/2019 SAP Exchange Infrastructure- Integration Directory
27/49
SAP AG 2003, Title of Presentation, Speaker Name / 27
Routing Rule: Receiver Determination
Use the condition editor
to enter conditions forrouting
Assign one or more receivers to a sender/outboundinterface pair.
Content-based receiver determination is possible
(via XPath/context objects)
Receiver should be an existing service (with or
without Party).
R ti R l I t f D t i ti
7/30/2019 SAP Exchange Infrastructure- Integration Directory
28/49
SAP AG 2003, Title of Presentation, Speaker Name / 28
Routing Rule: Interface Determination
Assign one or more inbound interfaces to be used for the inboundprocessing of a message (after the receiver determination).
Assign an Interface Mapping for each outbound-inbound interface pair
I t ti Di t XI 3 0
7/30/2019 SAP Exchange Infrastructure- Integration Directory
29/49
SAP AG 2003, Title of Presentation, Speaker Name / 29
Agenda
Integration Directory XI 3.0
XI 3.0 Integration Directory
Overview and Concepts
Business Scenarios
Collaboration Profiles
Routing Rules
Collaboration Agreements
Facilities
Cache updates
XI 3 0 Collaboration Agreement
7/30/2019 SAP Exchange Infrastructure- Integration Directory
30/49
SAP AG 2003, Title of Presentation, Speaker Name / 30
XI 3.0 Collaboration Agreement
The objects Sender Agreement and Receiver Agreement
Specify a binding between an interface and a communicationchannel
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
7/30/2019 SAP Exchange Infrastructure- Integration Directory
31/49
SAP AG 2003, Title of Presentation, Speaker Name / 31
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
Header mapping
The header mapping is a part of thecollaboration agreement and allows
you to overwrite specific fields ofthe header
Content can be provided from
Constant valueMessage Payload
Context object
Integration Directory XI 3 0
7/30/2019 SAP Exchange Infrastructure- Integration Directory
32/49
SAP AG 2003, Title of Presentation, Speaker Name / 32
Agenda
Integration Directory XI 3.0
XI 3.0 Integration Directory
Overview and Concepts
Business Scenarios
Collaboration Profiles
Routing Rules
Collaboration Agreements
Facilities
Cache updates
Facilities: Configuration Assistant
7/30/2019 SAP Exchange Infrastructure- Integration Directory
33/49
SAP AG 2003, Title of Presentation, Speaker Name / 33
Facilities: Configuration Assistant
Configuration Assistant: Internal Communication
7/30/2019 SAP Exchange Infrastructure- Integration Directory
34/49
SAP AG 2003, Title of Presentation, Speaker Name / 34
Configuration Assistant: Internal Communication
Configuration Steps:
Specify Inbound Message
Specify Outbound Message
Define Message Processing
Confirm Configuration Data
Configuration Assistant: Communication with
7/30/2019 SAP Exchange Infrastructure- Integration Directory
35/49
SAP AG 2003, Title of Presentation, Speaker Name / 35
gPartners
Facilities: Business Scenario Configurator
7/30/2019 SAP Exchange Infrastructure- Integration Directory
36/49
SAP AG 2003, Title of Presentation, Speaker Name / 36
Facilities: Business Scenario Configurator
From the BusinessScenario Editor, click
this icon to start the
configuration wizard
All of the configuration objects that areneeded for a given scenario can be
created manually; Alternately, you can
use the Business Scenario Configuration
Wizard to generate all of the objects thatare necessary to implement the scenario.
Step 1: Select Component View
7/30/2019 SAP Exchange Infrastructure- Integration Directory
37/49
SAP AG 2003, Title of Presentation, Speaker Name / 37
Step 1: Select Component View
You assign a Business Scenario Fromthe Integration Repository to use as
the basis of the configuration.
Each Role in theBusiness Scenario is
assigned to a Service
Each Connection in the
Business Scenario isassigned to an Interface
Mapping (if necessary)
Step 2: Assign Services
7/30/2019 SAP Exchange Infrastructure- Integration Directory
38/49
SAP AG 2003, Title of Presentation, Speaker Name / 38
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
7/30/2019 SAP Exchange Infrastructure- Integration Directory
39/49
SAP AG 2003, Title of Presentation, Speaker Name / 39
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
7/30/2019 SAP Exchange Infrastructure- Integration Directory
40/49
SAP AG 2003, Title of Presentation, Speaker Name / 40
Step 4: Generate
Specify whether you will
simulate or generate the
configuration objects
Set the objects togenerate
Specify a change list (for
generation only)
Start generation
Step 5: Review Generation Log
7/30/2019 SAP Exchange Infrastructure- Integration Directory
41/49
SAP AG 2003, Title of Presentation, Speaker Name / 41
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
7/30/2019 SAP Exchange Infrastructure- Integration Directory
42/49
SAP AG 2003, Title of Presentation, Speaker Name / 42
Value Mapping
TheValue mapping function provides a
specific value transformation.
1. Use the standard functionConversions ->Value mappingto
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, usehttp://sap.com/xi/XI
Agency and Schema for senderand receiver messages. Any
arbitrary string value can be
used.
Value Mapping
7/30/2019 SAP Exchange Infrastructure- Integration Directory
43/49
SAP AG 2003, Title of Presentation, Speaker Name / 43
Integration DirectoryIntegration Directory
Value Mapping
Integration Directory
Value Mapping
Tool
Value Mapping
Tool
Value MappingTool
Value Mapping
ToolValue Mapping
Tool
3rd party component
Integration Server
Value Mapping API
Display UIValueMapping Server
Value Mapping Cache
Value Mapping API
Mapping Runtime
Mapping Program
Preliminary Receiver Determination
7/30/2019 SAP Exchange Infrastructure- Integration Directory
44/49
SAP AG 2003, Title of Presentation, Speaker Name / 44
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
Integration Directory XI 3.0
7/30/2019 SAP Exchange Infrastructure- Integration Directory
45/49
SAP AG 2003, Title of Presentation, Speaker Name / 45
Agenda
Integration Directory XI 3.0
XI 3.0 Integration Directory
Overview and Concepts
Business Scenarios
Collaboration Profiles
Routing Rules
Collaboration Agreements
Facilities
Cache updates
Cache updates
7/30/2019 SAP Exchange Infrastructure- Integration Directory
46/49
SAP AG 2003, Title of Presentation, Speaker Name / 46
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)
Integration
Directory
Central Adapter Engine
Integration Engine
Bus. Process Engine
Decentral Adapter Engine
Decentral Adapter Engine
SXI_CACHE
CPA CACHE
Information about the
adapter engines is
obtained from the SLD
Cache Notifications
7/30/2019 SAP Exchange Infrastructure- Integration Directory
47/49
SAP AG 2003, Title of Presentation, Speaker Name / 47
Cache Notifications
IS Runtime cache
7/30/2019 SAP Exchange Infrastructure- Integration Directory
48/49
SAP AG 2003, Title of Presentation, Speaker Name / 48
Goto AE Cacheto list the connections from
the IS to the adapter
engines
Integration Directory: Unit Summary
7/30/2019 SAP Exchange Infrastructure- Integration Directory
49/49
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
g y y
Recommended