Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Integration Directory
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
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
Agenda
XI 3.0 Integration Directory Overview and Concepts Business Scenarios Collaboration Profiles Routing Rules Collaboration Agreements Facilities Cache updates
Agenda
XI 3.0 Integration Directory Overview and Concepts Business Scenarios Collaboration Profiles Routing Rules Collaboration Agreements Facilities Cache updates
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
Integration Directory
Adapt integration content to specific configuration Delivered empty, without predefined content
all content is customer-specific
Configuration Editors
Routing Rules
Receiver Determination Rules
Collaboration Agreements
Sender & Receiver Agreements
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.
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
SAP AG 2003, Title of Presentation, Speaker Name / 11
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.
Party Party
... PartyName AlternativeIdentifiers
Logical Routing
...
Collaboration Agreement
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
SAP AG 2003, Title of Presentation, Speaker Name / 14
Agenda
XI 3.0 Integration Directory Overview and Concepts Business Scenarios Collaboration Profiles Routing Rules Collaboration Agreements Facilities Cache updates
Configuration Wizard
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 Integration Directory Overview and Concepts Business Scenarios Collaboration Profiles Routing Rules Collaboration Agreements Facilities Cache updates
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:
3 Types Of 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
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
At configuration time, Business Processes are handled as senders and receivers or messages Derived from the Integration Repository where the process is defined
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
XI 3.0 Integration Directory Overview and Concepts Business Scenarios Collaboration Profiles Routing Rules Collaboration Agreements Facilities Cache updates
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).
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 Integration Directory Overview and Concepts Business Scenarios Collaboration Profiles Routing Rules Collaboration Agreements Facilities Cache updates
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
XI 3.0 Integration Directory Overview and Concepts Business Scenarios Collaboration Profiles Routing Rules Collaboration Agreements Facilities Cache updates
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
You assign a Business Scenario From the Integration Repository to use as the basis of the configuration.
Each Connection in the Business Scenario is assigned to an Interface Mapping (if necessary)
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
Start generation
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
Integration Directory
Value Mapping Tool
Integration Server
Mapping Runtime
Mapping Program Value Mapping API
ValueMapping Server
Display UI
Find out at the application level whether a receiver exists for a given outbound interface
Routing rule must be maintained in directory (virtual receiver)
Agenda
XI 3.0 Integration Directory Overview and Concepts Business Scenarios Collaboration Profiles Routing Rules Collaboration Agreements Facilities Cache updates
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
Cache Notifications
IS Runtime cache
Goto AE Cache to list the connections from the IS to the adapter engines
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