SAP Exchange Infrastructure – Process Centric Integration XI Overview

SAP Exchange Infrastructure – Process Centric Integration XI Overview
SAP NetWeaverTM Process Integration SAP Exchange Infrastructure – Process Centric Integration XI Overview

Exchange Infrastructure Overview: Unit Objectives
After completing this unit, you will be able to: Explain need for and the benefits of the SAP Exchange Infrastructure. Describe the components of the SAP Exchange Infrastructure. Detail the key functionality of SAP XI.

SAP Exchange Infrastructure
Agenda Positioning Architecture Overview Key Functionality Summary

SAP XI is an integration technology and platform…
Mission SAP XI is an integration technology and platform… …for SAP and non-SAP applications. …for A2A and B2B scenarios. …for asynchronous and synchronous communication. …for cross-component Business Process Management. SERVER A goal of the Exchange Infrastructure (XI) is to provide a single point of integration for all systems, SAP and non-SAP, inside and outside the corporate boundary. The XI supports B2B as well as A2A exchanges; supports synchronous and asynchronous message exchange; and includes a built-in engine for designing and executing Integration Processes (Business Processes). An important feature of the XI is that it provides openness and transparency to the integration process BUILDER

Composite Application Framework
SAP NetWeaver™ SAP NetWeaver™ Unifies and aligns people, information and business processes Integrates across technologies and organizational boundaries A safe choice with full .NET and J2EE interoperability The business foundation for SAP and partners Powers business-ready solutions that reduce custom integration Its Enterprise Services Architecture increases business process flexibility SAP NetWeaver™ PEOPLE INTEGRATION Multi channel access Portal Collaboration INFORMATION INTEGRATION Bus. Intelligence Knowledge Mgmt Master Data Mgmt Composite Application Framework Life Cycle Mgmt PROCESS INTEGRATION Integration Broker Business Process Mgmt APPLICATION PLATFORM J2EE ABAP SAP NetWeaver is the integration and application platform for mySAP solutions; XI represents the Process Integration layer of the NetWeaver stack, and is a crucial element of the Enterprise Services Architecture (ESA). DB and OS Abstraction

One Customer’s Complex Integration Landscape
ERP legacy: ~15 systems SAP R/3: ~30 systems, versions 3.1I – 4.6B ERP non-SAP: ~25 systems, different versions e-Procurement: in 10 units SAPMarkets Enterprise Buyer (Professional Edition) Technical Systems Today, integration complexity abounds. Many components in customer system landscapes are directly connected 1:1, with all integration capabilities hardwired into the application components and individual mapping programs. Imagine a common complex IT landscape at a customer site. This sort of ”spider web” is the epitome of today’s application integration challenge. What you see is a wildly grown integration landscape with different application systems and multiple individual connections between different interfaces. Connecting these applications does not only lead to a high complexity in managing and maintaining – there is also a lot of cost associated with it. These systems have been integrated over time using whatever integration technology or middleware was available. The integration knowledge is hidden within the different applications or within the used middleware tools and the interface descriptions. The overall key concept of the SAP Exchange infrastructure is to drive integrated business processes across heterogeneous and highly dynamic IT landscapes in a more manageable and cost effective way. Trading e-Sales Collaborative Engineering

Exchange Infrastructure for Collaboration
Enterprise Resource Planning Inter-/Intra-Enterprise Co-operation Collaborative Business Integration Engine & Bus Infrastructure Shared central knowledge, Small number of peer-to-peer connections Database Integration Integration by single centralized data model Direct Connections Integration challenge Quadratically growing complexity How integration has evolved at SAP: At first a single database integration in a single centralized data model: in one system with several applications one database, (e.g. an R/3 system with MM, SD, CO, FI, HR,…) with the applications having access to the data structures across the components. Integration in this case is and was fairly easy. Then SAP and 3rd party vendors provided other solutions as e.g. CRM, SRM, … These solutions and their respective systems needed to be integrated to the ERP environment (e.g. an R/3 backend system). This brought added complexity and the beginning of many individual point-to-point connections. With the SAP Exchange Infrastructure and collaborative business, SAP approaches the integration challenge from a different angle. The basic idea is to provide a runtime infrastructure which allows heterogeneous systems to be tied together with fewer connections and at the same time, in order to connect those applications and let messages flow from one application to the other, have a centralized storage of the integration knowledge.

The Solution – Shared Business Semantics
Shared Integration Knowledge Integration scenarios, business processes, Web services, interfaces, mappings, routing rules, ... For a common understanding how collaborative business processes work Enabling distributed execution Shared classification and discovery of businesses and services Support for UDDI (Universal Description, Discovery and Integration) Loose coupling via XML messaging Asynchronous communication as far as possible Synchronous communication where required Evolution Allow easy and non-disruptive addition of new services and processes Integration of existing and new SAP components Integration of existing customer and 3rd party components The complete integration knowledge of mySAP.com e-business platform is described in shared repositories and directories. Traditionally, interfaces were described within components in an implementation-dependent programming language. E.g. Interfaces in the Integration Repository introduce a new level of transparency and homogeneity in interface development. The integration knowledge is not distributed across individual applications, but is centrally configured. XML-messaging: Loosely coupled applications communicate by exchanging XML messages via the integration infrastructure. Communication is asynchronous in most cases to allow complete decoupling. Synchronous calls are supported and used where needed. Integration Engine: A highly scalable infrastructure for local and central execution of integration logic needed for component integration. The integration infrastructure provides an integrated error handling and monitoring of integration processes across the entire landscape. Availability: As a central and critical functionality in the entire system landscape, integration services need to be highly available and centrally managed. The architecture allows Peer-to-peer connectivity (still centrally controlled) to avoid additional point of failures Evolution: New applications or services can be added to the landscape in a non-disruptive fashion due to the central management of integration knowledge. Existing SAP and 3rd party components can be integrated into the new infrastructure seamlessly.

Advantage: Pre-delivered Integration Content
3rd Party Catalog Data EBP SAP solutions bring their integration meta-data (CRM, SRM, SCM, xApps like xRPM, etc.) Delivered with the Integration Repository of SAP XI SUS Benefits Out-of-the-box integration of SAP solutions Simplified upgrade of SAP Solutions Versioning and modification management of integration meta-data SAP provides content for mySAP solutions in files that are imported into the XI.

Advantage: Openness and Interoperability
Connect to existing integration solutions Through JMS messaging (e.g. MQSeries) Through SOAP Use open, XML based standards for integration Incorporate existing functionality into new processes Adapters (JCA) Web Services (WSDL) 3rd Party Application SAP Application 3rd Party Middleware Component 3rd Party Application Benefits Leverage existing investments Arrive at new integration landscape in an evolutionary manner Allow easy and non-disruptive addition of new services and processes XI is open and flexible; it uses web standards such as Web Services Description Language (WSDL), XML Schema Definition Language (XSD), and SOAP messaging for describing objects and communicating with other systems.

SAP Applications Using XI
More and more SAP applications are making use of SAP Exchange Infrastructure and introducing XI to a customer landscape The following applications now use XI: xApps (such as xRPM, Resource and Program Management) MDM (SAP Master Data Management) SRM (SAP Supplier Relationship Management) ICH (SAP Inventory Collaboration Hub within SAP SCM) BI (SAP Business Intelligence, for Global Spending Reporting) R/3 Enterprise (for Industry Standard Support) CRM (SAP Customer Relationship Management, for Extended Order Management) SBO (SAP Business One)

Component Overview Shared Collaboration Knowledge
Execution of Collaborative Business Processes Integration Builder Central Monitoring SAP Systems Integration Server (IS) Integration Repository (IR) Integration Directory (ID) 3rd Party Systems 3rd Party Middleware Component Marketplace/ Business Partner The XI is not a single component, but rather a collection of components that work together flexibly to implement integration scenarios. The architecture includes components to be used at design time, components to be used at configuration time, and components to be used at runtime. XI components include: The System Landscape Directory: a central repository of information about software and systems in the data center. The Integration Builder: A client-server framework for accessing and editing two stores of Shared Collaboration Knowledge: The Integration Repository: For the design and development of Interface, Process, and Mapping objects that are used to implement Integration Scenarios. The Integration Directory: For configuring scenarios from the Integration Repository in the concrete customer landscape. The Integration Server: The central processing engine of the XI. All messages, whether SAP or non-SAP, A2A or B2B, regardless of backend technology or vendor, are processed in a consistent way. Central Monitoring: To give a comprehensive and focused view of all components and processes at runtime. The Adapter Engine: A Java Connector Architecture (JCA) compliant adapter engine for connecting backend systems to the XI. System Landscape Directory (SLD)

Capturing Shared Knowledge at Design/Config Time
Integration Repository Product to be used at design/development time At SAP, partner, and customer site Shipped along with content Integration Directory Product to be used at configuration time At customer site Content partially derivable from Integration Repository by configuration tools Integration Engine Product to be used at runtime Relies on content of Integration Directory By separating design time activities from configuration time activities, SAP can ship content for the Integration Repository, which each customer can implement for their specific landscape in the Integration Directory. As far as possible the goal is to reduce the problem of developing interfaces to the simpler task of configuring interfaces. At runtime, the Integration Engine is based on the solid architecture of the SAP Web Application Server, leveraging the power, scalability, and manageability of the platform. Integration Engine

Exchange Infrastructure – Integration Landscape
Integration Repository Integration Server connects to different SAP and Non-SAP Systems, to Business Partners and Public Marketplaces SAP 3.x Integration Directory SAP 4.x Market- place SAP Adapter Firewall Business Partner 3rd Party Adapter Third Party System mySAP Solution* Business Partner The SAP Exchange Infrastructure connects to different SAP and Non-SAP systems. In this example of an integration landscape at a customer site, an SAP R/3 3x (e.g. R/3 3.1I), an SAP R/3 4.x (e.g. R/3 4.OB), a third party system and a new mySAP solution (e.g. mySAP SRM) are integrated via the SAP Exchange Infrastructure. The Integration Server also handles the connection to different Business Partners as well as to a Public Marketplace. Certain adapters are needed in cases where the Integration Server is to exchange messages with an R/3 system based on a basis kernel lower than 6.20 (RFC adapter, IDoc adapter), or in order to connect to a specific marketplace (depending on the marketplace product). There are no additional adapters needed, when the Integration Server connects to a new mySAP solution which is based on the SAP Web Application Server 6.20, as the components of these solutions carry themselves a “small” Integration Engine – those systems can directly interact and communicate with the Integration Server to exchange XML messages. Business Partner * based on SAP Web Application Server 6.20+

Integration Builder – Common tool framework
Integration Directory Integration Repository Client-server framework Consistent look and feel Based on Java Web Start UI Client Integration Builder Client Framework Layout Building Blocks Personalization Navigation Server Integration Builder Server Framework Query Service & Cross References Import/Export & CMS interface Internationalization Change list Management Versioning Locking Authorization & Authentication The Integration Builder is the common tool framework for design and configuration time activities. The Integration Builder allows you to work with objects in both repositories in a consistent way, with a consistent interface and a common look-and-feel. The Integration Builder is a Java application. On the client side it provides the user interface for working with XI objects. On the server side it offers services for authentication, lock management, import and export of interface objects, internationalization, versioning, and change management. Because the client applications (Integration Repository and Integration Directory) are “fat” clients, Java Web Start is required. JWS is a caching application for Java clients (download once and store locally). DB

Integration Repository Software Component Version
Design Integration Builder Pre-delivered Integration Content for mySAP solutions Open for collaboration knowledge of non- SAP systems, using open standards (e.g. WSDL) Provision to enhance XI design time objects by customers / partners Java based graphical tools Integration Repository Scenario Editor Business Scenarios Process Editor Business Processes BPEL Mapping Editor Mappings XSLT Java Condition Editor Context Objects XPath Message Interfaces WSDL Message Types Data Types (XSD) Data Type Editor SAP provides the design content for mySAP solutions; other SAP interfaces, such as Remote-enabled Function Modules or IDOCs, are imported into the Integration Repository. The customer can add the collaboration knowledge of the non-SAP systems that are participating in an integration scenario. The Integration Builder provides the editors for each object type in the Integration Repository. All XI objects are described using web standards: Web Services Description Language (WSDL) for interfaces, XML Schema Definition Language (XSD) for messages and data types, XPath for “slicing and dicing” data in XML documents, and Business Process Execution Language (BPEL) for Integration Processes (Business Processes). System Landscape Directory Software Component Web AS SAP Software Component Version J2EE/ ABAP Proxies

Integration Directory Collaboration Agreements Collaboration Profiles
Configuration Integration Builder Adapt integration content to specific configuration Derive integration content from Integration Repository Open for Customer to add collaboration knowledge relevant to non-SAP components Java based graphical tools Central configuration for B2B processes and BPM Centralized adapter configuration Integration Directory Business Scenarios Configuration Wizards Business Processes Routing Rules Receiver Determination Rules Interface Determination Rules (including Mapping Assignment) Configuration Editors Collaboration Agreements Security Once Integration content has been created in the Integration Repository, scenarios are configured in the Integration Directory. In the directory we specify the actual systems that will be exchanging messages, and configure the details of the message exchange (security, transport protocol, etc.) Collaboration Profiles Parties & Services Channels

System Landscape Directory
Describes concrete system landscape of customer installation What component is actively available on which machine/instance/client, etc. Information about domain contained, i.e. in which network environment (local / remote) are components accessible Any number of different landscapes Any type of component (SAP, partner products, other packages, legacy systems ..) Open architecture, based on CIM Base for structuring design objects in the repository, and for configuring routing rules in the directory The System Landscape Directory (SLD) is a central repository of information about systems and software in the data center. The SLD is a server application; the XI is technically a client of the SLD. The SLD adheres to the Common Information Model (CIM), a standard proposed by the Distributed Management Task Force (DMTF).

Runtime Central Monitoring Integration Directory
Business Process Engine Integration Engine System Landscape Directory Adapter Engine XI Protocol XI Protocol RosettaNet, … SAP Web AS ≥ 6.20 SAP System File DB JMS 3rd Party Apps Apps of Business Partner Partner Connectivity Kit Local Integration Engine IDocs RFCs At runtime, the Integration Scenarios that have been developed in the Integration Repository and configured in the Integration Directory are executed by the Integration Server. The Integration Server includes engines for executing Integration Processes (Business Processes), processing messages, and connecting to backend systems. Communication between mySAP systems based on the SAP Web Application Server version 6.40 or higher communicate natively with the XI; other systems, including those using B2B standards such as RosettaNet, CIDX, and PIDX, communicate via adapters. SAP also provides the Partner Connectivity Kit (PCK), which allows smaller partners and subsidiaries that may not have XML messaging or B2B capabilities to communicate natively with the XI across firewalls and across the Internet. Proxy Runtime Apps of (small) Business Partner Proxy

Decoupling Of Integrated Applications
Integration Directory A sample message flow from one application to another is depicted Logical decoupling of senders and receivers Decoupling of sender and receiver interface formats Routing Rules Mappings SAP R/3 3.1i Collaboration Profiles Integration Server Channel Determination SAP Adapter Receiver Determination Marketplace Mapping Firewall Business Partner SAP R/3 Enterprise SAP XI abandons the point-to-point integration approach, favoring instead a model that features loosely coupled applications communicating via XML/SOAP/HTTP. A message is received at the Integration Server and is examined by the runtime environment; based on the configuration for the particular message type and content, the message is routed to the appropriate receiver(s), perhaps undergoing a mapping to the partner format along the way. Business Partner 3rd Party Adapter 3rd Party App Business Partner

XI Runtime Environment
Functionality Communication Synchronous: always “best effort” Asynchronous: exactly-once or exactly-once-in-order Retry mechanism Acknowledgment is supported Including error handling Synchronous: error messages sent back to sender Asynchronous: errors made persistent Transport of (XML) messages based on HTTP or HTTPS “SOAP Messages with Attachments” as wire format Messaging protocol based on SOAP envelope with header extensions The XI supports Synchronous and Asynchronous delivery; in XI terms, these are described with a Quality of Service (QoS) descriptor. The XI supports QoS Best Effort (BE), Exactly-once (EO), and Exactly-once-in-order (EOIO). These are equivalent to RFC types Synchronous RFC (sRFC), Transactional RFC (tRFC), and Queued RFC (qRFC), respectively. The XI is used to exchange XML messages in an implementation of the SOAP protocol. The SAP implementation of SOAP includes messages sent as attachments to the SOAP document.

Connectivity / Adapters
Execute Collaborative Business Processes Central Monitoring – ensures collaboration reliability SAP Systems Partner Connectivity Kit Marketplace/ Business Partner Business Process Engine Integration Server Integration Engine Central Adapter Engine Adapter Framework Messaging Queuing Security Handling Resource Adapter Application Techn. System File/DB/JMS Adapter framework based on Java Connector Architecture (JCA) Adapters work as plug- ins to the Adapter Framework Adapter Development Kit - customers and partners can develop adapters SAP NetWeaver certification of 3rd party adapters based on JCA adapter framework Reselling of JCA adapters from selected partners (iWay, Seeburger) SAP XI includes the Adapter Framework for developing adapters to non-SAP systems that can be executed by the Adapter Engine. The Adapter Framework is a JCA-compliant framework for developing connectors to the XI. The framework includes: Technical Resource Adapters Non-SAP backend integration adapters B2B Adapters Additional APIs for Monitoring, Error Handling, Configuration

Adapter Architecture Integration Repository / Integration Directory / System Landscape Directory Integration Server Business Process Engine Integration Engine Partner Connectivity Kit Optional Decentral Adapter Engine Central Adapter Engine PCK Configuration and Monitoring J2SE Adapter Engine Adapter FW Messaging Queuing Security Handling Adapter FW Messaging Queuing Security Handling Adapter Framework Messaging Queuing Security Handling Resource Adapter Resource Adapter RFC/IDoc Adapter Resource Adapter Adapter The XI Adapter Engine is based on the integrated J2EE engine of the SAP Web AS; it allows for central configuration and monitoring of all adapters, even those that are installed de-centrally (close to the backend system). The Adapter Engine includes its own security, message processing, and message queuing functionality. File DB JMS SAP System Application Techn. System File/DB/JMS 3rd Party Application 3rd Party Application

Cross-Component Business Process Management
Business System 1 Business System 2 Business System 3 Orchestrates message choreography based on stateful interactions Design, execute and monitor automated processes across applications and systems Provides process control in the central technology layer Contains a Graphical Modeler Integral part of XI Modeling enables linkage to XI design objects: interfaces, mappings … BPM runtime is embedded in the Integration Server runtime Adheres to standards Industry Standard support (BPEL4WS) Import/ export of process definitions 1 2 3 Messages Integration Server 4 Integration Processes (Cross-Component Business Processes), are executable processes that allow for stateful interactions between loosely-coupled systems. XI includes capabilities for designing, documenting, implementing, configuring, and executing Integration Processes. Integration Processes are built using the web standard Business Process Execution Language for Web Services (BPEL4WS or just BPEL). Message Business System 4

SAP XI and B2B enablement (1)
Industry B2B Protocols Apps of (small) Business Partner Integration Repository (IR) Integration Directory (ID) Integration Server (IS) XI Protocol Partner Connectivity Kit System Landscape Directory (SLD) Apps of (small) Business Partner Enable business partners to conduct B2B processes with XI Security enrichments for B2B Digital Signature and Encryption Partner Connectivity Kit Enable partners of XI customers to conduct XML document exchange with XI In order to enable B2B scenarios, XI includes security features such as message encryption, digital signatures, and non-repudiation. Additionally, the PCK allows smaller partners or subsidiaries with no native B2B messaging capabilities to communicate with XI.

SAP XI and B2B enablement (2)
Industry Standards Content Collaboration Profile Collaboration Agreement Industry B2B Protocols Apps of (small) Business Partner Integration Repository (IR) Integration Directory (ID) Integration Server (IS) XI Protocol Partner Connectivity Kit System Landscape Directory (SLD) Apps of (small) Business Partner Industry Standards Content (e.g. RosettaNet PIPs, specific mappings) Collaboration Profile and Collaboration Agreement in Integration Directory Manages technical characteristics of partners to facilitate document exchange, such as Party identification Message formats and versions supported Security requirements SAP provides Industry Standards content for the Integration Repository; for instance, implementations of RosettaNet Partner Interface Processes (PIP’s). The Integration Directory includes Collaboration Profiles and Collaboration Agreements for enabling B2B communication.

Value-added Web Services Through XI
3rd Party App Adapter ‘Managed’ Web Service Integration Server Web Service Client (SAP/non-SAP) SOAP Adapter IDocs RFCs Mapping Routing SAP System Business Processes XI Protocol or SOAP Proxy Proxy Runtime Local Integration Engine Web Service Client (SAP/non-SAP) SOAP The SAP Web Application Server includes native XML messaging capability, and the ability to provide web services based on the SOAP protocol. Because of the enhancements to the basic SOAP protocol used by XI, it is possible to implement “value-added” web services through the XI. XI allows to include additional payloads to a message, and to implement additional functionality through enhanced SOAP headers. Web Services Framework ‘Basic’ Web Service SAP Web AS  6.40

Runtime Workbench Central monitoring tool for the complete XI landscape Component monitoring Message monitoring Graphical end-to-end monitoring Performance monitoring Smooth integration with CCMS Easy Configuration Exploiting System Landscape Directory Web-based user interface The Runtime Workbench is an XI component that offers a central monitoring view of all XI components and processes. The Workbench includes graphical end-to-end monitoring of integration scenarios. It provides smooth and easy integration with CCMS, and CCMS alerts can be viewed through the Runtime Workbench.

Summary SAP XI addresses integration challenges
Is a A2A and B2B integration solution Industry standard support Supports the whole process integration lifecycle Comes with pre-delivered content Is suited for heterogeneous integration landscapes Is interoperable based on open standards SAP XI is SAP’s strategic process integration platform mySAP SRM, mySAP SCM, SAP for Retail, … Synergetic use inside SAP NetWeaver with SAP MDM, BPM, CAF, … SAP XI is more than just an Integration Broker Cross-Component BPM SAP XI is a serious approach to the integration challenge, and represents the Process Integration layer of the NetWeaver stack. It leverages the flexibility of web standards such as Java and WSDL, as well as the power and scalability of ABAP. It is a crucial element in implementing the Enterprise Services Architecture. XI supports both A2A and B2B scenarios. It includes content provided by SAP, reducing the amount of work the customer must do to implement an integration scenario. It provides for the rapid development of new interfaces in an intuitive, non-disruptive way. It includes shared collaboration knowledge for transparency in integration scenarios. XI offers one platform for implementing messaging and Integration Processes (Business Processes).

Exchange Infrastructure Overview: Unit Summary
You should now be able to: Explain need for and the benefits of the SAP Exchange Infrastructure. Describe the components of the SAP Exchange Infrastructure. Detail the key functionality of SAP XI.

SAP Exchange Infrastructure – Process Centric Integration XI Overview

Similar presentations

Presentation on theme: "SAP Exchange Infrastructure – Process Centric Integration XI Overview"— Presentation transcript:

Similar presentations

About project

Feedback

Войти

Auth with social network:

SAP Exchange Infrastructure – Process Centric Integration XI Overview

Similar presentations

Presentation on theme: "SAP Exchange Infrastructure – Process Centric Integration XI Overview"— Presentation transcript:

Similar presentations

About project

Feedback