Tbit40 en Coll44 Show
April 8, 2017 | Author: api-3807985 | Category: N/A
Short Description
Download Tbit40 en Coll44 Show...
Description
TADMBO Implementation&Operation II
TBIT40
Implementation & Operation II
THE BEST-RUN BUSINESSES RUN SAP SAP AG 2004 © SAP AG©2004
2004/Q4
Material number: 50069569
© SAP AG
Course Overview - 1
SAP Exchange Infrastructure 3.0 TBIT40 XI Foundations
Lecture topics
Topics XI Overview System Landscape Directory Integration Repository Integration Directory Runtime Runtime Workbench Adapter Framework Business Process Management Server Administration Security B2B and Industry Standards © SAP AG 2003, PM Process Integration 2
Exercise topics
Topics Exercise 1:
File to IDoc
Exercise 2:
File to JDBC
Exercise 3:
HTTP to (t)RFC
Exercise 4:
ABAP Proxy to RFC
Exercise 5:
BPM Async-Sync
© SAP AG 2003, PM Process Integration 3
TM
SAP NetWeaver Process Integration
SAP Exchange Infrastructure – Process Centric Integration
XI Overview
Lecture topics
Topics XI Overview System Landscape Directory Integration Repository Integration Directory Runtime Runtime Workbench Adapter Framework Business Process Management Server Administration Security B2B and Industry Standards © SAP AG 2004, TBIT40 01 XI Overview 2
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 AG 2004, TBIT40 01 XI Overview 3
SAP Exchange Infrastructure
Agenda
Positioning Architecture Overview Key Functionality Summary
© SAP AG 2004, TBIT40 01 XI Overview 4
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 BUILDER
© SAP AG 2004, TBIT40 01 XI Overview 5
SAP NetWeaver™ SAP NetWeaver™
Unifies and aligns people, information and business processes
SAP NetWeaver™
PEOPLE INTEGRATION
Portal
Integrates across technologies and organizational boundaries
Collaboration
INFORMATION INTEGRATION Bus. Intelligence
Knowledge Mgmt
Master Data Mgmt PROCESS INTEGRATION Integration Broker
Business Process Mgmt
APPLICATION PLATFORM J2EE DB and OS Abstraction
© SAP AG 2004, TBIT40 01 XI Overview 6
ABAP
Life Cycle Mgmt
Composite Application Framework
Multi channel access
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
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
e-Sales
Trading Collaborative Engineering © SAP AG 2004, TBIT40 01 XI Overview 7
Exchange Infrastructure for Collaboration Enterprise Resource Planning
Inter-/Intra-Enterprise Co-operation
Database Integration
Direct Connections
Integration by single centralized data model
Integration challenge Quadratically growing complexity
© SAP AG 2004, TBIT40 01 XI Overview 8
Collaborative Business
Integration Engine & Bus Infrastructure Shared central knowledge, Small number of peer-to-peer connections
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 © SAP AG 2004, TBIT40 01 XI Overview 9
Advantage: Pre-delivered Integration Content
3rd Party Catalog Data EBP
SUS
SAP solutions bring their integration meta-data (CRM, SRM, SCM, xApps like xRPM, etc.) Delivered with the Integration Repository of SAP XI
Benefits Out-of-the-box integration of SAP solutions Simplified upgrade of SAP Solutions Versioning and modification management of integration meta-data
© SAP AG 2004, TBIT40 01 XI Overview 10
Advantage: Openness and Interoperability Connect to existing integration solutions Through JMS messaging (e.g. MQSeries)
3rd Party Application
Through SOAP
Use open, XML based standards for integration Incorporate existing functionality into new processes
SAP Application
Adapters (JCA) Web Services (WSDL)
3rd Party Application
3rd Party Middleware Component
Benefits Leverage existing investments Arrive at new integration landscape in an evolutionary manner Allow easy and non-disruptive addition of new services and processes © SAP AG 2004, TBIT40 01 XI Overview 11
SAP Exchange Infrastructure
Agenda
Positioning Architecture Overview Key Functionality Summary
© SAP AG 2004, TBIT40 01 XI Overview 12
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)
© SAP AG 2004, TBIT40 01 XI Overview 13
Component Overview Shared Collaboration Knowledge
Execution of Collaborative Business Processes
Integration Builder
Central Monitoring SAP Systems
Integration Repository (IR)
Integration Directory (ID)
Integration Server (IS)
3rd Party Systems 3rd Party Middleware Component Marketplace/ Business Partner
System Landscape Directory (SLD)
© SAP AG 2004, TBIT40 01 XI Overview 14
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 At customer site Relies on content of Integration Directory
© SAP AG 2004, TBIT40 01 XI Overview 15
Integration Engine
Exchange Infrastructure – Integration Landscape
Integration Repository Integration Directory
SAP SAP 3.x 3.x
SAP SAP 4.x 4.x
Integration Server connects to different SAP and Non-SAP Systems, to Business Partners and Public Marketplaces
SAP Adapter
MarketMarketplace place Firewall
Third Third Party Party System System
3rd Party Adapter
mySAP mySAP Solution* Solution*
Business Business Partner Partner
Business Business Partner Partner Business Business Partner Partner
* based on SAP Web Application Server 6.20+ © SAP AG 2004, TBIT40 01 XI Overview 16
SAP Exchange Infrastructure
Agenda
Positioning Architecture Overview Key Functionality Summary
© SAP AG 2004, TBIT40 01 XI Overview 17
Integration Builder – Common tool framework Integration Repository
Integration Directory
Client-server framework Consistent look and feel
UI Client
Layout Building Blocks Personalization Navigation Integration Builder Client Framework
Server
Query Service & Cross References Import/Export & CMS interface Internationalization Change list Management Versioning Locking Authorization & Authentication Integration Builder Server Framework
DB © SAP AG 2004, TBIT40 01 XI Overview 18
Based on Java Web Start
Design Integration Builder 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 Type Editor
Data Types (XSD)
© SAP AG 2004, TBIT40 01 XI Overview 19
SAP Web AS
System Software Component Version Landscape Software Component Directory
Pre-delivered Integration Content for mySAP solutions Open for collaboration knowledge of nonSAP systems, using open standards (e.g. WSDL) Provision to enhance XI design time objects by customers / partners Java based graphical tools
J2EE/ ABAP Proxies
Configuration Integration Builder Integration Directory Business Scenarios Configuration Wizards
Business Processes Routing Rules Receiver Determination Rules
Configuration Editors
Derive integration content from Integration Repository Open for Customer to add collaboration knowledge relevant to non-SAP components
Interface Determination Rules (including Mapping Assignment)
Java based graphical tools
Collaboration Agreements
Central configuration for B2B processes and BPM
Security
Collaboration Profiles Parties & Services Channels
© SAP AG 2004, TBIT40 01 XI Overview 20
Adapt integration content to specific configuration
Centralized adapter configuration
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
© SAP AG 2004, TBIT40 01 XI Overview 21
Runtime Central Monitoring
Integration Directory
Business Process Engine
Integration Engine System Landscape Directory
Adapter Engine XI Protocol Local Integration Engine
RosettaNet, …
IDocs RFCs
Proxy Runtime Proxy
SAP Web AS ≥ 6.20 © SAP AG 2004, TBIT40 01 XI Overview 22
File DB JMS SAP System
3rd Party Apps
Apps of Business Partner
XI Protocol
Partner Connectivity Kit Apps of (small) Business Partner
Decoupling Of Integrated Applications Integration Directory Routing Rules Mappings Collaboration Profiles
SAP R/3 3.1i
Integration Server
SAP Adapter
Channel Determination
A sample message flow from one application to another is depicted Logical decoupling of senders and receivers Decoupling of sender and receiver interface formats
Receiver Determination
Marketplace
Mapping
Firewall
SAP R/3 Enterprise 3rd Party Adapter
© SAP AG 2004, TBIT40 01 XI Overview 23
Business Partner Business Partner
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 © SAP AG 2004, TBIT40 01 XI Overview 24
Connectivity / Adapters Execute Execute Collaborative Collaborative Business Business Processes Processes
Central Central Monitoring Monitoring ––
Adapter framework based on Java Connector Architecture (JCA)
ensures ensures collaboration collaboration reliability reliability
Integration Server Business Process Engine Integration Engine
Central Adapter Engine Messaging Queuing Security Handling
Resource Adapter
Adapter Framework
SAP SAP Systems Systems Marketplace/ Marketplace/ Business Business Partner Partner Partner Partner Connectivity Connectivity Kit Kit Application Techn. System File/DB/JMS
Adapters work as plugins 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 AG 2004, TBIT40 01 XI Overview 25
Adapter Architecture Integration Repository / Integration Directory / System Landscape Directory Integration Server Business Process Engine Integration Engine
© SAP AG 2004, TBIT40 01 XI Overview 26
Application Techn. System File/DB/JMS
3rd Party Application
and Monitoring Adapter FW Messaging Queuing Security Handling
3rd Party Application
Resource Adapter
SAP System
Adapter FW Messaging Queuing Security Handling
Resource Adapter
File DB JMS
Adapter Framework Messaging Queuing Security Handling
Resource Adapter
Adapter
Optional Decentral Adapter Engine
Central Adapter Engine RFC/IDoc Adapter
J2SE Adapter Engine
Partner Connectivity Kit PCK Configuration
Cross-Component Business Process Management Business System 1
Business System 2
Business System 3
1
2
3
Messages
Integration Server
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
4 Message
Business System 4 © SAP AG 2004, TBIT40 01 XI Overview 27
Adheres to standards Industry Standard support (BPEL4WS) Import/ export of process definitions
SAP XI and B2B enablement (1) Industry B2B Protocols
Integration Repository (IR)
Integration Directory (ID)
Integration Server (IS)
Apps of (small) Business Partner
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 © SAP AG 2004, TBIT40 01 XI Overview 28
SAP XI and B2B enablement (2) Industry Standards Content
Integration Repository (IR)
Collaboration Profile Collaboration Agreement
Integration Directory (ID)
Industry B2B Protocols
Integration Server (IS)
Apps of (small) Business Partner
XI Protocol Partner Connectivity Kit
System Landscape Directory (SLD) Industry Standards Content (e.g. RosettaNet PIPs, specific mappings)
Apps of (small) Business Partner
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 AG 2004, TBIT40 01 XI Overview 29
Value-added Web Services Through XI
Adapter
‘Managed’ Web Service
3rd Party App
Integration Server Web Service Client (SAP/non-SAP)
SOAP
Mapping Routing
Adapter
IDocs RFCs
SAP System
Business Processes
XI Protocol or SOAP
Proxy Proxy Runtime
Web Service Client (SAP/non-SAP)
© SAP AG 2004, TBIT40 01 XI Overview 30
Local Integration Engine SOAP
‘Basic’ Web Service
Web Services Framework
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
© SAP AG 2004, TBIT40 01 XI Overview 31
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 AG 2004, TBIT40 01 XI Overview 32
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 AG 2004, TBIT40 01 XI Overview 33
SAP Exchange Infrastructure
System Landscape Directory
Lecture topics
Topics XI Overview System Landscape Directory Integration Repository Integration Directory Runtime Runtime Workbench Adapter Framework Business Process Management Server Administration Security B2B and Industry Standards © SAP AG 2004, TBIT40 02 SLD 2
System Landscape Directory: Unit Objectives
After completing this unit, you will be able to: z Explain the purpose of the System Landscape Directory and its role as an information provider. z Describe the content types in the System Landscape Directory. z Create Software Component descriptions in the System Landscape Directory. z Define Technical Systems in the System Landscape Directory. z Define Business Systems in the System Landscape Directory.
© SAP AG 2004, TBIT40 02 SLD 3
System Landscape Directory Overview Central information provider for NetWeaver system landscapes Manage software components and platform dependencies Facilitate Installations, upgrades and transports Based on Common Information Model (CIM) of the Distributed Management Task Force (DMTF)
Basis for SAP Solution Manager Information provider for SAP XI
© SAP AG 2004, TBIT40 02 SLD 4
Aspects of system landscapes
© SAP AG 2004, TBIT40 02 SLD 5
SLD content type Component Information
Describes building blocks of solutions
Describes possible combinations and dependencies
Delivered by SAP, extensible by customer
Landscape Description
Information on installed landscape elements
Customer-specific
SAP XI utilizes both types of content: Integration Repository: Component Information Integration Directory: Landscape Description
© SAP AG 2004, TBIT40 02 SLD 6
System Landscape Directory Applications Applications and and Tools Tools Graphical Design Tool
PPMS
..
..
..
Technical Technical Configuration Configuration ..
Validation Validation Registration ..
Software Software Logistics Logistics ..
.. 1
..
..
1
2
Synchronize, XML Master Master Component Component Repository Repository
System System Landscape Landscape Directory Directory
Any Any Landscape Landscape Element Element Customer Customer Landscape Landscape
Landscape WBEM, Landscape XML description description CIM CIM
Component Types Landscape Patterns
Update Possible Combinations
SAP © SAP AG 2004, TBIT40 02 SLD 7
Component WBEM, Component XML information information CIM CIM
rd-Party 33rd -Party // Customer Customer Component Component Types Types
Customer
SLD: Products and Software Components
Product
Software Component
0..1
0..1
*
*
Product Version
Software Component Version
*
1
*
© SAP AG 2004, TBIT40 02 SLD 8
Software Feature
*
Example: SAP APO
© SAP AG 2004, TBIT40 02 SLD 9
Example: workshop exercise Product
Software Feature: Associations
Software Component
1
1 n
Product Version
TBIT40_WORKSHOP of SAP TBIT40_WORKSHOP, 1.0 of SAP
© SAP AG 2004, TBIT40 02 SLD 10
Software Component Version
n
TBIT40_WORKSHOP ## of SAP TBIT40_WORKSHOP ##, 1.0 of SAP
Defining the Software Component
To define a Software Component: From the main screen of the SLD, choose “Software Catalog.” Use the drop-down to select the Software Components type, and then select “New Component” to start the wizard.
Select the Product from the drop-down Enter the software vendor Enter the Software Component Name Enter the Software Component version (SWCV) Choose “Create” © SAP AG 2004, TBIT40 02 SLD 11
SLD: Technical System
Technical System WebAS ABAP Name; host name; system number; Release Installed clients
Business System
Message Server Installed Products WebAS Java Name; host name; SID; System Home Standalone JAVA Technical System ID Third Party Installed Products
© SAP AG 2004, TBIT40 02 SLD 12
Business Systems Business Systems
Defining the Technical System From the Technical System browser choose “New Technical System…”
… specify the Technical System Type…
… select (and add) the products and components that are installed on the technical system...
… click “Finish.” © SAP AG 2004, TBIT40 02 SLD 13
SLD: Business System
Business System WebAS ABAP Related Integration Server client
Technical System
Installed Products WebAS Java Related Integration Server Name Third Party Systems
Technical System Technical System
Related Integration Server Installed Products Standalone Java Name
© SAP AG 2004, TBIT40 02 SLD 14
Technical System
Defining the Business System
Give the system a unique name…
… specify the associated Technical System (and Logical System, if necesary)… … select the installed products (from the technical system definition)…
… and the Related Integration Server
… click “Finish.” © SAP AG 2004, TBIT40 02 SLD 15
SLD and XI Integration Repository
Integration Repository (Design)
Software Component Version Business Scenario Application Component Role Product Version
System Landscape Directory
Mapping Objects Product Interface Objects
Product Version Software Component Software Component Version
© SAP AG 2004, TBIT40 02 SLD 16
SLD and Repository: usage dependencies SAP Integration Builder Repository (Design)
A dependency can be defined in the SLD This dependency will be automatically detected in the Integration Repository
Software Component Version A
...
Basis objects System Landscape Directory X Software Component Version A Software Component Version B
Software Component Version B Usage Dependency
X © SAP AG 2004, TBIT40 02 SLD 17
SLD and Directory SAP Integration Directory (Configuration)
Routing Relations Sender Service:
Business System
Receiver Service:
Business System
System Landscape Directory A service object in the Integration Directory can be derived from the SLD. Business System Technical System
© SAP AG 2004, TBIT40 02 SLD 18
Summary: object structure in SLD
© SAP AG 2004, TBIT40 02 SLD 19
System Landscape Directory: Unit Summary
You should now be able to: z Explain the purpose of the System Landscape Directory and its role as an information provider. z Describe the content types in the System Landscape Directory. z Create Software Component descriptions in the System Landscape Directory. z Define Technical Systems in the System Landscape Directory. z Define Business Systems in the System Landscape Directory.
© SAP AG 2004, TBIT40 02 SLD 20
SAP Exchange Infrastructure
Integration Repository
Lecture topics
Topics XI Overview System Landscape Directory Integration Repository Integration Directory Runtime Runtime Workbench Adapter Framework Business Process Management Server Administration Security B2B and Industry Standards © SAP AG 2004, TBIT40 03 Integration Repository 2
Integration Repository: Unit Objectives After completing this unit, you will be able to: z Describe the Integration Repository and the objects that are created in it. z Understand various Interface Objects and their roles in integration scenarios. z Detail the use of web standards in the descriptions of interface objects in the Integration Repository. z Explain the Proxy functionality in XI. z Describe message mappings and list the different types of mappings available in XI. z Explain Business Processes and their role in integration scenarios. z Describe how to import various objects into the Integration Repository. © SAP AG 2004, TBIT40 03 Integration Repository 3
Integration Repository: Business Scenario
z You need to implement and Integration Scenario. z You must first create the appropriate objects and processes in the Integration Repository.
© SAP AG 2004, TBIT40 03 Integration Repository 4
Integration Repository
Agenda XI 3.0 Integration Repository Overview and concepts Software components and namespaces Interface objects Proxy generation Mapping objects Business Process objects Miscellaneous
© SAP AG 2004, TBIT40 03 Integration Repository 5
Integration Repository
Agenda XI 3.0 Integration Repository Overview and concepts Software components and namespaces Interface objects Proxy generation Mapping objects Business Process objects Miscellaneous
© SAP AG 2004, TBIT40 03 Integration Repository 6
Business Process In A Distributed Landscape
Before starting an XI Integration project, a component view of the business process requirements must be established
© SAP AG 2004, TBIT40 03 Integration Repository 7
External Interfaces In A Distributed Landscape
XI Integration is interface-driven. An interface represents: The transfer of data between two components Synchronous or asynchronous message exchange
© SAP AG 2004, TBIT40 03 Integration Repository 8
Software Components, Interfaces And Mappings
© SAP AG 2004, TBIT40 03 Integration Repository 9
Design Time Integration Builder Integration Repository Scenario Editor
Business Scenarios
Process Editor
Business Processes
BPEL
Mapping Editor
Mappings
XSLT Java
Condition Editor
Context Objects
XPath
Message Interfaces
WSDL
Interface Editor
Proxies
Message Types Data Types
XSD
Software Component Version
Software Component
System Landscape Directory © SAP AG 2004, TBIT40 03 Integration Repository 10
J2EE/ABAP
SAP Web AS ≥ 6.20
Integration Repository
Agenda XI 3.0 Integration Repository Overview and concepts Software components and namespaces Interface objects Proxy generation Mapping objects Business Process objects Miscellaneous
© SAP AG 2004, TBIT40 03 Integration Repository 11
Software Component Version Primary container for all Integration Repository objects Imported directly from the SLD Usage dependencies from SLD are reflected in the Repository (‘Basis objects‘)
For each software component version, the following can be assigned: A connection to an existing SAP system
for the import of IDoc/RFC interfaces
One or more namespaces
© SAP AG 2004, TBIT40 03 Integration Repository 12
Namespaces (Globally) unique identifier for related Integration Repository objects Usually vendor-based
Same concept as XML namespaces Several namespaces can be assigned to the same SWCV Naming convention:
URI
http://sap.com/xi/demo
URN
urn:sap-com:xi:demo
z (URI without protocol assignment)
© SAP AG 2004, TBIT40 03 Integration Repository 13
Integration Repository
Agenda XI 3.0 Integration Repository Overview and concepts Software components and namespaces Interface objects Proxy generation Mapping objects Business Process objects Miscellaneous
© SAP AG 2004, TBIT40 03 Integration Repository 14
Interface Objects: Data Type Data types are the most basic entity to define the structure of XML elements Equivalent to XML Schema (XSD) Data type editor provides all XSD basic data types. Nesting of data types possible Export of data type in XSD format possible
© SAP AG 2004, TBIT40 03 Integration Repository 15
Interface Objects: Message Type The Message type corresponds to the root of the XML message Name and namespace must match exactly the root of XML Business documents The Message type references one single data type XSD representation available for export
© SAP AG 2004, TBIT40 03 Integration Repository 16
Interface Objects: Message Interface
The Message Interface is the highest-level representation of XML metadata. Inbound or outbound (respective to the application), or abstract (for BPM only) Synchronous or asynchronous Asynchronous Synchronous
refers to one message type
refers to two message types (request and
response)
References fault message types for exception handling WSDL representation available for export Starting point for proxy generation (ABAP and Java) Context objects can be assigned
© SAP AG 2004, TBIT40 03 Integration Repository 17
Message Interfaces based on RFC/IDoc Imports must be allowed as part of the configuration of the SWCV.
A wizard interface walks you through the process of importing RFC’s/IDOC’s
© SAP AG 2004, TBIT40 03 Integration Repository 18
Connection information for the target system is maintained as part of the SWCV.
Interface Objects And WSDL
Integration Repository Data Type FlightBookingID
Message Type FlightBooking_Confirm_Out_Req
Data Type: FlightBookingID
XML Schema (XSD)
Message Interface FlightBooking_Confirm_Out
Output Message Type: FlightBooking_Confirm_Out_Req
© SAP AG 2004, TBIT40 03 Integration Repository 19
Interface Objects: Context Objects Context Object Pointer to a specific element (field) within the message, for future reference Encapsulate access to data that is contained in the payload or in the header (technical context objects) of a message Example: in CREMAS03 (Vendor master) IDoc: zipcode = CREMAS03/IDOC/E1LFA1M/PSTLZ 1. Create Context Object
© SAP AG 2004, TBIT40 03 Integration Repository 20
2. Use Context Object in Message Interface
Integration Repository
Agenda XI 3.0 Integration Repository Overview and concepts Software components and namespaces Interface objects Proxy generation Mapping objects Business Process objects Miscellaneous
© SAP AG 2004, TBIT40 03 Integration Repository 21
Proxy Generation – Overview Separation of Business Application logic from XI connectivity
Outside-in development approach Adapter-less, out-of-the-box integration For applications based on SAP Web AS 6.20 or above (ABAP and Java)
The Proxy Framework hides technical details from application developer Transform language-specific data structures into XML and vice-versa Ensure technical connectivity with the Integration Engine, guaranteed delivery
© SAP AG 2004, TBIT40 03 Integration Repository 22
Integration Engine
Proxy
Business Function Application Application System System
Proxy Generation Message interfaces are the basis for proxy generation Proxy will have the same attributes as the message interface: Inbound,
outbound
Synchronous,
asynchronous
Same concept for ABAP and Java, but different procedure J2EE
proxies are generated from the IR as .JAR files
ABAP
proxies are generated from the application client, based on the WSDL representation of the message interface
Some rules and restrictions are in effect for the conversion of XSD Data types into Java or ABAP types, respectively See
the documentation for more details
© SAP AG 2004, TBIT40 03 Integration Repository 23
Create ABAP Proxies (Transaction SPROXY)
3
1 2
© SAP AG 2004, TBIT40 03 Integration Repository 24
Generated ABAP Objects Message interfaces can have the mode synchronous or asynchronous. Furthermore, the type of the message interface determines what type of proxy is generated. The counterparts to outbound message interfaces in application systems are client proxies. They are called to send a message to an inbound interface. An outbound message interface is mapped to an ABAP object class (prefix CO_). The counterparts to inbound message interfaces in application systems are server proxies. The proxy generation functions generate an ABAP object interface (prefix II_) for an inbound message interface; you must implement this interface using an ABAP object class to make this service available.
Example: Client proxy (class) generated from Outbound Message Interface
© SAP AG 2004, TBIT40 03 Integration Repository 25
Java Proxy Wizard
© SAP AG 2004, TBIT40 03 Integration Repository 26
Integration Repository
Agenda XI 3.0 Integration Repository Overview and concepts Software components and namespaces Interface objects Proxy generation Mapping objects Business Process objects Miscellaneous
© SAP AG 2004, TBIT40 03 Integration Repository 27
Mapping Concepts Mapping Transformation From One Message Structure To Another Transformation Rules Defined By Mapping Program
Micheal Moore Airline Kingdom AK087 2001-11-22 business
© SAP AG 2004, TBIT40 03 Integration Repository 28
Value Mapping
Structure Mapping
22.11.2001 087 Micheal Moore 2 Happy Holiday
Mapping Techniques In XI Message mapping Graphical design and test environment Queue-based model allows handling of very large documents Extensible via Java user-defined functions
XSLT Open standard Portable Extensible via Java user-defined functions Memory overhead for very large documents
Java Flexibility of Java programming language Java mapping program is responsible for parsing/rendering XML
ABAP Leverage existing ABAP base ABAP mapping program is responsible for parsing/rendering XML
© SAP AG 2004, TBIT40 03 Integration Repository 29
Mapping Objects: Message Mapping
Graphical mapping tool Graphically define mapping rules between source and target message types Queue-based model allows for handling of extremely large documents Drag-and-drop Generates internal Java code Built-in and user-defined functions (in Java) Integrated testing tool N:M mapping possible – for use with BPM only!
© SAP AG 2004, TBIT40 03 Integration Repository 30
Message Mapping: Mapping Editor
Structure Overview
Source SourceStructure Structure
Data-Flow Editor
© SAP AG 2004, TBIT40 03 Integration Repository 31
Target TargetStructure Structure
Target Field Mapping
Mapping Objects: Interface Mapping Representation of the mapping at the interface level Assign mapping program(s) between source and target message types: Message XSLT
mapping
Custom ABAP
mapping
Java mapping
mapping
Mapping programs can be combined in a sequence N:M interface mapping possible (for use with BPM only!) For synchronous interfaces, a request and response mapping can be provided
© SAP AG 2004, TBIT40 03 Integration Repository 32
Mapping Objects: Imported Archives The object type ‘imported archive’ is for importing externally defined programs into the Integration Repository: XSLT stylesheets Java mappings Java extensions to XSLT mappings Java classes to be imported in a user-defined function for message mapping
All files to be imported must be archived (JAR format) The archive is uploaded from user workstation. Integration Repository can serve as central maintenance location for imported objects XSLT and text files can be edited directly from IR. Java CLASS files must be edited and recompiled locally, then reimported. © SAP AG 2004, TBIT40 03 Integration Repository 33
Integration Repository
Agenda XI 3.0 Integration Repository Overview and concepts Software components and namespaces Interface objects Proxy generation Mapping objects Business Process objects Miscellaneous
© SAP AG 2004, TBIT40 03 Integration Repository 34
Business Scenario Objects A Business Scenario describes a complete collaborative process from the XI point of view
Travel Agency Airline Web AS 6.20
Web AS 6.20
main
focus on the complete message exchange
describes
only the public part of the
process
Check Seat Availability
Determine Seat Availability
An Action describes a function (a process) within one component that is involved in the message exchange
Send Flight Booking Order
refers to the interfaces that can be used to perform that function may be used by one or more business scenarios
© SAP AG 2004, TBIT40 03 Integration Repository 35
Book Flight
What Are XI Business Scenarios Used For? Business
Scenario = Plan of Integration
Business Scenario driven modelling and visualization of integrated business processes
Collects all XI objects of an integration scenario
Enables single entry point and access to all objects
Provides structured documentation
Input
for XI configuration
Business Scenario guided configuration
Generation of configuration objects
Products, Functions
Connections (Interfaces, Mapping)
Input
for implementation
Involved functions and services
Products and system requirements
© SAP AG 2004, TBIT40 03 Integration Repository 36
Business Process Objects You can design new objects for executable business processes by using the graphical Process Editor. You can use different modeling elements and patterns to design a stateful, cross-component business process. The following modeling patterns and elements are supported: Receive messages and trigger process Send, transform (merge or split) messages Collect messages Multicast Serialization Process control elements such as switch, assign, fork, wait, block, loop, control Deadlines, exception handling, conditions
© SAP AG 2004, TBIT40 03 Integration Repository 37
Business Processes & Business Scenarios Business Process can be incorporated in a Business Scenario Representation in a swim lane Treated as a Business System Navigation from Scenario to Process
© SAP AG 2004, TBIT40 03 Integration Repository 38
Concept: Integration Of Scenario And Process Visualisation In XI Integration Builder Scenario – Component View Product A
Product A
Product B
Process - Flow Product Template
Process
IFabs1 IFabs2
Send Receive
W ait for Negative Acknowledgem ent
IFabs1 IFabs2
[tim eout] W ait for response
Alert
Alert
Send response back to initiator
Send
IFabs
IFabs
Scenario: integration view of an abstract collaborative business process
[continue]
[one out of three]
BPM process: executable collaborative business process
Process is assigned to a swimlane – visualization of the public parts of the process - process is part of a software component of the product - navigation from swimlane in scenario to process object One action and connection per abstract interface* of the process - checked consistency between process interface and connections in scenario
Executable process (behind the swimlane) for Business Process Engine
*the process interface requires XI interfaces of type abstract in integration repository © SAP AG 2004, TBIT40 03 Integration Repository 39
Integration Repository
Agenda XI 3.0 Integration Repository Overview and concepts Software components and namespaces Interface objects Proxy generation Mapping objects Business Process objects Miscellaneous
© SAP AG 2004, TBIT40 03 Integration Repository 40
Import / Export Functions Objects in the Integration Repository are based on open standards
Integration Repository
BPEL
Business Processes
XSLT Java
Mappings
WSDL XSD DTD
Interfaces
IDocs, RFCs
SAP System
© SAP AG 2004, TBIT40 03 Integration Repository 41
The import function for WSDL, BPEL XSD and DTD files enables you to upload message definitions from external sources. After conversion to WSDL they can be used to define message mappings and message WSDL interfaces. XSD
The object type External Definition is a container which is used to make external message definitions available in the Integration Repository.
Import Of RFC / IDoc Interfaces Import of RFC / IDoc metadata from existing SAP system Based on connection parameters specified in the SW Component RFC and IDoc metadata cannot be modified within XI Namespaces are preset: urn:sap-com:document:sap:idoc:messages urn:sap-com:document:sap:rfc:functions
XSD and WSDL representation available for export Procedure: right-click on ‘imported objects’ and follow the wizard © SAP AG 2004, TBIT40 03 Integration Repository 42
Miscellaneous The Integration Repository supports versioning of all repository objects at software component level. Support Packages of a software component version are also supported. Message interfaces can be marked as “abstract“ (instead of “inbound“ or “outbound“). This applies to interfaces which are used in BPM or which are handled by adapters. Advantage: There is no need to define two interfaces (inbound and outbound) if their structure is identical. It is possible to enhance data types shipped by SAP with customer-specific fields. These enhancements will not be lost in the event of a release upgrade. The information modeled in business scenarios can be used to describe product release combinations. A separate “component view“ can be defined for each release.
© SAP AG 2004, TBIT40 03 Integration Repository 43
Integration Repository: Unit Summary You should now be able to: z Describe the Integration Repository and the objects that are created in it. z Understand various Interface Objects and their roles in integration scenarios. z Detail the use of web standards in the descriptions of interface objects in the Integration Repository. z Explain the Proxy functionality in XI. z Describe message mappings and list the different types of mappings available in XI. z Explain Business Processes and their role in integration scenarios. z Describe how to import various objects into the Integration Repository. © SAP AG 2004, TBIT40 03 Integration Repository 44
SAP Exchange Infrastructure
Integration Directory
Lecture topics
Topics XI Overview System Landscape Directory Integration Repository Integration Directory Runtime Runtime Workbench Adapter Framework Business Process Management Server Administration Security B2B and Industry Standards © SAP AG 2004, TBIT40 04 Integration Directory 2
Integration Directory: Unit Objectives
After completing this unit, you will be able to: z Describe the Configuration Time Activities of the Exchange Infrastructure z Detail the task areas and configuration objects of the Integration Directory z Create and work with Collaboration Profiles z Design Logical Routings z Work with Collaboration Agreements z Completely and correctly configure Integration Scenarios within the Integration Directory
© SAP AG 2004, TBIT40 04 Integration Directory 3
Integration Directory: Business Scenario
z The Development Consultants on your project have designed and developed Integration Scenarios and the related objects to enable A2A and B2B communication. z You are tasked with configuring these scenarios in the Integration Directory so they can be successfully executed at runtime.
© SAP AG 2004, TBIT40 04 Integration Directory 4
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
© SAP AG 2004, TBIT40 04 Integration Directory 5
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
© SAP AG 2004, TBIT40 04 Integration Directory 6
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
© SAP AG 2004, TBIT40 04 Integration Directory 7
Service B
XI 3.0 Integration Directory: Overview Integration Builder Integration Directory Business Scenarios Configuration Wizards
Business Processes Collaboration Profiles Parties , Services & Channels
Configuration Editors
Adapt integration content to specific configuration Delivered empty, without predefined content all content is customer-specific
Integration content derived from Integration Repository
Receiver Determination Rules
Open for Customer to add collaboration knowledge relevant to non-SAP components
Interface Determination Rules (including Mapping Assignment)
Home for centralized adapter configuration
Routing Rules
Collaboration Agreements Sender & Receiver Agreements
© SAP AG 2004, TBIT40 04 Integration Directory 8
Integration Directory
Data provider for IS runtime
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)
© SAP AG 2004, TBIT40 04 Integration Directory 9
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.
A communication party represents a larger unit which is involved in a cross-system process (for example a company).
• 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
© SAP AG 2004, TBIT40 04 Integration Directory 10
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 © SAP AG 2004, TBIT40 04 Integration Directory 11
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
© SAP AG 2004, TBIT40 04 Integration Directory 12
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..*
Party Party
Service Service
PartyName ... AlternativeIdentifiers
... ServiceName
AlternativeIdentifiers 1 Collaboration Profile Interfaces
Service may be: • a B2B service • a Business System • a Process
0..*
Channel Channel ... ChannelName
Receiver Determination Receiver Determination ...
SenderParty SenderService SenderInterfaceNamespace SenderInterfaceName ReceiverParty ReceiverService Conditions
Interface Determination Interface Determination ...
SenderParty SenderService SenderInterfaceNamespace SenderInterfaceName ReceiverParty ReceiverService ReceiverInterfaceNamespace ReceiverInterfaceName MappingProgramName
Logical Routing
© SAP AG 2004, TBIT40 04 Integration Directory 13
AdapterEngine TransportProtocol BusinessProtocol BusinessProtocolVersion SenderAgreement Agreement URL Sender LogonData ...
SenderParty SenderService SenderInterfaceNamespace SenderInterfaceName ReceiverParty InboundChannel Certificates
Receiver Agreement Receiver Agreement ...
SenderParty ReceiverParty ReceiverService ReceiverInterfaceNamespace ReceiverInterfaceName OutboundCannel Certificates
Collaboration Agreement
Configuration Model: Terminology What must XI do, so that FordSender is able to Sender send a Sender POCreate
XI Channels Ford Interfaces Agreements
CP
JBLReceiver Receiver Receiver
What must XI do, so XI is Channels that able to Interfaces forward a POCreate to Agreements JBL
XI must decrypt
SenderAgreement
CA
Ford
XI must encrypt
ReceiverAgreement JBL
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 2004, TBIT40 04 Integration Directory 14
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
© SAP AG 2004, TBIT40 04 Integration Directory 15
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).
© SAP AG 2004, TBIT40 04 Integration Directory 16
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.
© SAP AG 2004, TBIT40 04 Integration Directory 17
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
© SAP AG 2004, TBIT40 04 Integration Directory 18
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
© SAP AG 2004, TBIT40 04 Integration Directory 19
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
© SAP AG 2004, TBIT40 04 Integration Directory 20
XI 3.0 Service Object : Business Service
© SAP AG 2004, TBIT40 04 Integration Directory 21
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
© SAP AG 2004, TBIT40 04 Integration Directory 22
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
© SAP AG 2004, TBIT40 04 Integration Directory 23
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
© SAP AG 2004, TBIT40 04 Integration Directory 24
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
RNIF
For connecting to the RNIF protocol (RosettaNet Implementation Framework) by using the RNIF adapter
© SAP AG 2004, TBIT40 04 Integration Directory 25
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
© SAP AG 2004, TBIT40 04 Integration Directory 26
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).
© SAP AG 2004, TBIT40 04 Integration Directory 27
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
© SAP AG 2004, TBIT40 04 Integration Directory 28
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
© SAP AG 2004, TBIT40 04 Integration Directory 29
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
© SAP AG 2004, TBIT40 04 Integration Directory 30
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
© SAP AG 2004, TBIT40 04 Integration Directory 31
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
© SAP AG 2004, TBIT40 04 Integration Directory 32
Facilities: Configuration Assistant
© SAP AG 2004, TBIT40 04 Integration Directory 33
Configuration Assistant: Internal Communication
Configuration Steps: • Specify Inbound Message • Specify Outbound Message • Define Message Processing • Confirm Configuration Data
© SAP AG 2004, TBIT40 04 Integration Directory 34
Configuration Assistant: Communication with Partners
© SAP AG 2004, TBIT40 04 Integration Directory 35
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…
© SAP AG 2004, TBIT40 04 Integration Directory 36
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)
© SAP AG 2004, TBIT40 04 Integration Directory 37
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
© SAP AG 2004, TBIT40 04 Integration Directory 38
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
© SAP AG 2004, TBIT40 04 Integration Directory 39
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
© SAP AG 2004, TBIT40 04 Integration Directory 40
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.
© SAP AG 2004, TBIT40 04 Integration Directory 41
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.
© SAP AG 2004, TBIT40 04 Integration Directory 42
Value Mapping
Integration Directory Value Mapping Tool
Integration Server Mapping Runtime Mapping Program Value Mapping API
Value Mapping API
ValueMapping Server
Integration Directory Integration Directory 3rd party component Value Mapping Value ToolMapping Tool Value Mapping Value Mapping Tool Tool
© SAP AG 2004, TBIT40 04 Integration Directory 43
Value Mapping Cache
Display UI
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
© SAP AG 2004, TBIT40 04 Integration Directory 44
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
© SAP AG 2004, TBIT40 04 Integration Directory 45
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 © SAP AG 2004, TBIT40 04 Integration Directory 46
Decentral Adapter Engine
Cache Notifications
© SAP AG 2004, TBIT40 04 Integration Directory 47
IS Runtime cache
Goto Æ AE Cache to list the connections from the IS to the adapter engines
© SAP AG 2004, TBIT40 04 Integration Directory 48
Integration Directory: Unit Summary
You should now be able to: z Describe the Configuration Time Activities of the Exchange Infrastructure z Detail the task areas and configuration objects of the Integration Directory z Create and work with Collaboration Profiles z Design Logical Routings z Work with Collaboration Agreements z Completely and correctly configure Integration Scenarios within the Integration Directory
© SAP AG 2004, TBIT40 04 Integration Directory 49
SAP Exchange Infrastructure
Runtime
Lecture topics
Topics XI Overview System Landscape Directory Integration Repository Integration Directory Runtime Runtime Workbench Adapter Framework Business Process Management Server Administration Security B2B and Industry Standards © SAP AG 2004 TBIT40 05 Runtime
Runtime Overview : Unit Objectives
After completing this unit, you will be able to: z Explain basic concepts of XI message processing. z Describe the concept of the Integration Engine and the Pipeline, and detail the difference. z Use the message monitoring capability of the XI. z Explain the XI-SOAP message format. z Describe the caching capabilities of the Integration Server
© SAP AG 2004 TBIT40 05 Runtime
XI 3.0 Runtime
Agenda XI 3.0 Runtime Overview and Concepts Pipeline steps IS Runtime Cache
© SAP AG 2004 TBIT40 05 Runtime
XI Message Processing Integration Server Application System A
SOAP-XML
SOAP-XML
Application System B
XI connects various application systems via XML messaging. XI uses an SAP-specific implementation of the SOAP protocol. Messages received at the Integration Server are processed through a defined series of steps called Pipeline Services. When a message is received at the Integration Server, the message is examined and all valid configurations (as maintained in the Integration Directory) for that message are executed.
© SAP AG 2004 TBIT40 05 Runtime
Example of basic SOAP document over HTTP
© SAP AG 2004 TBIT40 05 Runtime
XI Message format: SOAP with attachments
© SAP AG 2004 TBIT40 05 Runtime
Sample XI Message
© SAP AG 2004 TBIT40 05 Runtime
Technical Structure of an XI Message
© SAP AG 2004 TBIT40 05 Runtime
The XI Pipeline
Source Source Message Message
Receiver Receiver Identification Identification
© SAP AG 2004 TBIT40 05 Runtime
Interface Interface Determination Determination
Message Message Split Split
Message Message Mapping Mapping
Technical Technical Routing Routing
Call Call Adapter Adapter
Target Target Message Message
Pipeline Entry Point
transaction SICF © SAP AG 2004 TBIT40 05 Runtime
Important Pipeline Steps Receiver Identification Determine which system(s) should participate in an exchange with the incoming message.
Interface Determination For each receiver system determine which interface(s) should receive a message.
Message Branch If multiple receivers are found, XI will instantiate a new message for each receiver.
Request Message Mapping Call the mapping program to transform the message structure to the receiver format.
Outbound Binding Bind a specific destination and protocol to the message.
Call Adapter Send the transformed message to the adapter or proxy.
© SAP AG 2004 TBIT40 05 Runtime
Adapter Engine http://
IS Runtime
System Landscape Directory • Holds component description including address data
Config. cache
Adapter Framework
XI Message OK / Error
Adapter Engine in SAP J2EE Integration Integration Repository Repository •• Holds Adapter Holds Adaptermetadata metadata
Adapter Sender
Module Processor
http:// Channel
Q Integration Builder / Directory:
Adapter Receiver
´Messaging
... Receiver determination • Party->Service->Action
Configuration cache
... Channel Definition: • Adapter Engine • Adapter Type • Message Protocol • Transport Protocol • Security • Channel Configuration
Tracing Logging Security
Monitoring
Administration
Configuration Master
End-to-End Monitoring (Sender / Receiver Agreement: • Party/Service/Action Channel © SAP AG 2004 TBIT40 05 Runtime
AdapterSpecific Component Services
Message flow over all XI components / applications
Runtime Workbench • Uis for adminstration, monitoring
E I S
XI 3.0 Runtime
Agenda XI 3.0 Runtime Overview and Concepts Pipeline steps IS Runtime Cache
© SAP AG 2004 TBIT40 05 Runtime
Pipeline Definition
Sender Central Receiver © SAP AG 2004 TBIT40 05 Runtime
Pipeline Services
© SAP AG 2004 TBIT40 05 Runtime
Pipeline Processing
Message Received in the Pipeline
Message After Receiver Identification
© SAP AG 2004 TBIT40 05 Runtime
Transaction SXI_Monitor
Two selection screens (Standard/Advanced) Selection on: z Status Group z Status z Execution From z Execution To z Party/Scheme/Agency/Service (S/R) z Interface Name/Namespace (S/R) z Pipeline z Technical Inbound Channel z Outbound Status z Error z Client
© SAP AG 2004 TBIT40 05 Runtime
XML Message List
Flexible ALV Views
© SAP AG 2004 TBIT40 05 Runtime
Legend
Changing the Layout tecview
Messages are displayed in an ALV Grid Control. Different layouts are possible: •Default: All attributes of a message are displayed •Technical View: Only the technical attributes are displayed •Business View: Business-oriented attributes are displayed •Acknowledgment View: Attributes important for acknowledgments are displayed
bizview © SAP AG 2004 TBIT40 05 Runtime
Display Message Contents
Steps in Pipeline
Display and download of the content
© SAP AG 2004 TBIT40 05 Runtime
Compare versions
Message Handling: Synchronous Processing
Synchronous Processing (QoS = BestEffort) Sending System
XI Integration Server
Receiving System
Sending Application
Receiving Application
Outbound Proxy
Inbound Proxy
Sender
Receiver
Central Central Integration Engine
Local Integration Engine
HTTP
Local Integration Engine
HTTP
Blocking call of sending application (incl. DB commit) No message persistance (logging needs to be swiched on)
© SAP AG 2004 TBIT40 05 Runtime
Message Handling: Asynchronous Processing
Asynchronous Processing (QoS = Exactly Once/Exactly Once In Order) Sending System
XI Integration Server
Receiving System
Sending Application
Receiving Application
Outbound Proxy
XI
qRFC
Inbound Proxy
XI
Sender
XI
qRFC
Receiver
Central
Local Integration Engine
Central Integration Engine HTTP
qRFC Local Integration Engine
HTTP
•XI processing is asynchronously decoupled (scheduled in qRFC) •Hop-to-Hop exactly once protocol -> messages are persisted in database •EOIO serialization by qRFC queues (no serialization number!) © SAP AG 2004 TBIT40 05 Runtime
XI 3.0 Runtime
Agenda XI 3.0 Runtime Overview and Concepts Pipeline steps IS Runtime Cache
© SAP AG 2004 TBIT40 05 Runtime
XI Runtime Cache
Configuration Settings are cached at the Integration Server to improve performance. Cached objects include: Parties Services Receiver Determination Interface Determination Sender/Receiver Agreement Communication Channel Mappings Software Components Business Process
© SAP AG 2004 TBIT40 05 Runtime
Transaction SXI_Cache
© SAP AG 2004 TBIT40 05 Runtime
Manual Cache Refresh
© SAP AG 2004 TBIT40 05 Runtime
Adapter Engine Cache
To view the cached addresses of all Adapter Engines that are registered at the Integration Server, choose Goto Æ AE Cache from the main menu in transaction SXI_CACHE.
© SAP AG 2004 TBIT40 05 Runtime
IDOC Adapter Cache
Transaction IDX2
© SAP AG 2004 TBIT40 05 Runtime
XI Runtime 3.0: Unit Summary
You should now be able to: z Explain basic concepts of XI message processing. z Describe the concept of the Integration Engine and the Pipeline, and detail the difference. z Use the message monitoring capability of the XI. z Explain the XI-SOAP message format. z Describe the caching capabilities of the Integration Server
© SAP AG 2004 TBIT40 05 Runtime
SAP Exchange Infrastructure
Runtime Workbench
Lecture topics
Topics XI Overview System Landscape Directory Integration Repository Integration Directory Runtime Runtime Workbench Adapter Framework Business Process Management Server Administration Security B2B and Industry Standards © SAP AG 2004, TBIT40 06 Runtime Workbench 2
Runtime Workbench: Unit Objectives
After completing this unit, you will be able to: Explain the purpose of the Runtime Workbench. Describe the capabilities of the Runtime Workbench. Monitor messages, performance, and components in the Runtime Workbench. Describe the capabilities of End-to-End monitoring. Detail the alert capabilities of the Runtime Workbench.
© SAP AG 2004, TBIT40 06 Runtime Workbench 3
Runtime Workbench overview
Central point of access: XI Runtime Workbench Smooth integration with CCMS Easy Configuration Exploiting System Landscape Directory Consistent look-and-feel in UI
Improved Error Handling Errors classified by error cause
© SAP AG 2004, TBIT40 06 Runtime Workbench 4
Central Monitoring Message Monitoring
PMI
Component
CCMS
Runtime Monitoring Workbench Performance (RWB) Analysis
Message Alerting
Integration Server (SAP Web AS ≥ 6.40) Business Process Engine Integration Engine
Adapter Engine
© SAP AG 2004, TBIT40 06 Runtime Workbench 5
Alerting Framework
SAP Application SAP Web AS ≥ 6.40, using XI proxies
System Landscape Directory
Monitoring – Message Monitoring
(decentral) J2SE Adapter Adapter Engine Engine
Based on SAP standard monitoring solutions Used by End-to-End monitoring to construct instance view Available for XI component with persistence
Central Monitoring Message Monitoring
PMI
Component
CCMS
Runtime Monitoring Workbench Performance (RWB) Analysis
Message Alerting
Integration Server (SAP Web AS ≥ 6.40) Business Process Engine Integration Engine
Adapter Engine
© SAP AG 2004, TBIT40 06 Runtime Workbench 6
Alerting Framework
SAP Application SAP Web AS ≥ 6.40, using XI proxies
System Landscape Directory
Monitoring – Component Monitoring
Smooth integration with CCMS (easier, leaner) Monitoring of ABAP and Java components
(decentral) J2SE Adapter Adapter Engine Engine
Improved error handling
Central Monitoring Message Monitoring
PMI
Component
CCMS
Runtime Monitoring Workbench Performance (RWB) Analysis
Message Alerting
Integration Server (SAP Web AS ≥ 6.40) Business Process Engine Integration Engine
Adapter Engine
© SAP AG 2004, TBIT40 06 Runtime Workbench 7
Alerting Framework
SAP Application SAP Web AS ≥ 6.40, using XI proxies
System Landscape Directory
Monitoring – Performance Analysis
(decentral) J2SE Adapter Adapter Engine Engine
Enhanced performance statistics Measuring of throughput and latency (‘processing time’) Selection and aggregation of performance data by -
XI component Time range Message attributes
Central Monitoring Message Monitoring
PMI
Component
CCMS
Runtime Monitoring Workbench Performance (RWB) Analysis
Message Alerting
Integration Server (SAP Web AS ≥ 6.40) Business Process Engine Integration Engine
Adapter Engine
© SAP AG 2004, TBIT40 06 Runtime Workbench 8
Alerting Framework
SAP Application SAP Web AS ≥ 6.40, using XI proxies
System Landscape Directory
Monitoring - Alerting
(decentral) J2SE Adapter Adapter Engine Engine
Based on Central Alerting Framework Active Monitoring (alerts being sent by e-Mail, SMS,…)
XI 3.0 RWB – Component Monitoring Component Monitoring: Monitoring of ABAP and Java components
Central viewing of component‘s connection status in a specific domain.
Ping of system and sending of messages to components via a self-test area. © SAP AG 2004, TBIT40 06 Runtime Workbench 9
Component Monitoring features Two different views: XI components can be displayed either in Table or Tree format.
Selecting associated information: For ABAP components, specific configuration parameters are displayed as defined in TC SXMB_ADM. For Java components, system settings as well as Aii-Properties are displayed as defined in the exchange profile © SAP AG 2004, TBIT40 06 Runtime Workbench 10
Sending Test Messages
© SAP AG 2004, TBIT40 06 Runtime Workbench 11
XI 3.0 RWB – Message Monitoring Message Monitoring Harmonization of different message monitors Integration Engine Adapter Framework (J2EE)
All message monitoring centrally accessible through RWB Monitoring locally available as well at least for partner connectivity kit
© SAP AG 2004, TBIT40 06 Runtime Workbench 12
Message Monitoring – Message Details
•To see the detailed information about a message, select the radio button for the message and choose Details. •To view the individual versions of the message (as in transaction SXI_MONITOR), choose Message Content. •You can also view referencing and referenced messages.
© SAP AG 2004, TBIT40 06 Runtime Workbench 13
XI 3.0 RWB – End-to-End Monitoring/Configuration
Configure
Monitor © SAP AG 2004, TBIT40 06 Runtime Workbench 14
End-To-End Monitoring at a glance
Overall process status
Statistics
Status of monitoring tool itself
© SAP AG 2004, TBIT40 06 Runtime Workbench 15
Graphical representation of process or instance flow
End-To-End Monitoring – Prerequisites Activate the Process Monitoring Infrastructure Monitoring by setting respective configuration parameter in TC SXMB_ADM
© SAP AG 2004, TBIT40 06 Runtime Workbench 16
End-To-End Monitoring - Configuration After configuration, choose button “Save Configuration” to activate the End-To-End Monitoring
Select business system to be involved
© SAP AG 2004, TBIT40 06 Runtime Workbench 17
Select level of monitoring
Configure as sending or receiving system
End-To-End Monitoring – Monitoring Status
Displays internal error messages derived from self-monitoring in CCMS
Frequency of updating process monitoring data
Deletes error messages; corresponding alerts in CCMS are completed
Starts update immediately © SAP AG 2004, TBIT40 06 Runtime Workbench 18
End-To-End Monitoring – Process Overview Choose status symbol or attributes (e.g. warning, error, success) to display corresponding process instances
© SAP AG 2004, TBIT40 06 Runtime Workbench 19
End-To-End Monitoring – Instance View Choose message to switch to instance view providing tracking information
Duration of message
Components involved
© SAP AG 2004, TBIT40 06 Runtime Workbench 20
XI 3.0 Performance Monitoring
Performance Monitoring Performance measurement during operation
Measured data: Throughput Latency (“processing time”) Selection and Aggregation by: XI component (Integration Server, Adapter Engine) Time range Message attributes: Sender, receiver, message type © SAP AG 2004, TBIT40 06 Runtime Workbench 21
Performance Statistics --- Example
© SAP AG 2004, TBIT40 06 Runtime Workbench 22
XI 3.0 Alert Configuration | Alert-Configuration
Alert-Configuration Objective: Active Monitoring CCMS Alerts + message-oriented alerts Based on SAP’s Basis Alert Framework Alerts propagated through E-Mail, SMS, …
© SAP AG 2004, TBIT40 06 Runtime Workbench 23
Creating A New Alert Rule (2)
© SAP AG 2004, TBIT40 06 Runtime Workbench 24
XI 3.0 RWB – Cache Monitoring
© SAP AG 2004, TBIT40 06 Runtime Workbench 25
XI 3.0 RWB - Summary Central access to monitoring Component Monitoring End-to-end Message Monitoring Performance Measurement across distributed XI landscape Integration with Basis Monitoring solutions: •CCMS •PMI •Alert Framework Unified User Interface (UI) Easy monitor configuration
© SAP AG 2004, TBIT40 06 Runtime Workbench 26
Runtime Workbench: Unit Summary
You should now be able to: Explain the purpose of the Runtime Workbench. Describe the capabilities of the Runtime Workbench. Monitor messages, performance, and components in the Runtime Workbench. Describe the capabilities of End-to-End monitoring. Detail the alert capabilities of the Runtime Workbench.
© SAP AG 2004, TBIT40 06 Runtime Workbench 27
SAP Exchange Infrastructure Adapter Framework
Lecture topics
Topics XI Overview System Landscape Directory Integration Repository Integration Directory Runtime Runtime Workbench Adapter Framework Business Process Management Server Administration Security B2B and Industry Standards © SAP AG 2004, TBIT40 07 Adapter Framework 2
XI 3.0 Adapter Framework : Unit Objectives
After completing this unit, you will be able to: Describe the Architecture of the SAP XI Adapter Framework. Detail the functionality of the Adapter Engine. Explain central and local Adapter Installations. Distinguish between the various adapter types. Describe the Partner Connectivity Kit. Configure different adapters to send messages to and receive messages from the Integration Server.
© SAP AG 2004, TBIT40 07 Adapter Framework 3
XI 3.0 Adapter Framework Agenda
SAP XI 3.0 Adapter Framework Overview SAP XI 3.0 Adapter Strategy Technical adapters in detail Summary
© SAP AG 2004, TBIT40 07 Adapter Framework 4
SAP XI 3.0 Architecture Integration Integration Repository Repository // Integration Integration Directory Directory // System System Landscape Landscape Directory Directory Content (e. g. Mapping, Adapter Metadata)
Integration Integration Server Server Business Process Engine Integration Engine Central Adapter Engine
© SAP AG 2004, TBIT40 07 Adapter Framework 5
File/DB/JMS File/DB/JMS Marketplace Marketplace rd Party 33rd Party Sys. Sys.
File/DB/JMS File/DB/JMS Marketplace Marketplace rd Party 33rd Party Sys. Sys.
Adapter FW Messaging Queuing Security Handling
Resource Adapter
SAP SAP System System
Adapter FW Messaging Queuing Security Handling
and Monitoring Resource Adapter
File File DB DB JMS JMS
Adapter Framework Messaging Queuing Security Handling
Optional local Adapter Engine Resource Adapter
Adapter
IDoc Adapter
Plain J2SE Adapter Engine
Partner Connectivity Kit PCK Configuration
File/DB/JMS File/DB/JMS SAP SAP System System
Adapter Framework based on SAP J2EE Engine The Adapter Framework provides common functionality for both the Adapter Engine and SAP Partner Connectivity Kit Adapter Framework is based on SAP J2EE Engine as part of SAP Web AS Adapter Framework inherits properties and features such as scalability, clustering, high availability, thread management, etc.
Adapter Framework provides its own queuing and logging services Temporary stand-alone operation without connection to an Integration Server is possible, while still providing e. g. guaranteed exactly once messaging to and from connected application system © SAP AG 2004, TBIT40 07 Adapter Framework 6
JCA enabled Adapter Framework
Adapter Framework supports J2EE Connector Architecture (JCA) JCA is standard architecture for connecting the J2EE platform to Enterprise Information Systems (EIS) - e. g. ERP, DBMS, etc. A Resource Adapter plugs into an application server, providing connectivity between the EIS and a Java application JCA enabled Adapter Framework provides defined interfaces to which both our adapters and 3rd party adapters can conform JCA is a widely accepted standard that 3rd party adapter providers are already familiar with © SAP AG 2004, TBIT40 07 Adapter Framework 7
Central configuration, administration, monitoring
Additionally Adapter Framework provides comprehensive integration for central configuration, administration, monitoring of deployed adapters One single point of access, only one common UI, enhanced transparency Capability to move or copy configuration from one Adapter Framework to another (transportable configuration): To transport configuration from test landscape to productive landscape For high availability/failover Avoid redundant maintenance, ensure consistency End-to-end monitoring of the message flow over all SAP XI components and processes
© SAP AG 2004, TBIT40 07 Adapter Framework 8
SAP XI 3.0 Architecture Integration Integration Repository Repository // Integration Integration Directory Directory // System System Landscape Landscape Directory Directory Content (e. g. Mapping, Adapter Metadata)
Integration Integration Server Server Business Process Engine Integration Engine Central Adapter Engine
© SAP AG 2004, TBIT40 07 Adapter Framework 9
File/DB/JMS File/DB/JMS Marketplace Marketplace rd Party 33rd Party Sys. Sys.
File/DB/JMS File/DB/JMS Marketplace Marketplace rd Party 33rd Party Sys. Sys.
Adapter FW Messaging Queuing Security Handling
Resource Adapter
SAP SAP System System
Adapter FW Messaging Queuing Security Handling
and Monitoring Resource Adapter
File File DB DB JMS JMS
Adapter Framework Messaging Queuing Security Handling
Optional local Adapter Engine Resource Adapter
Adapter
IDoc Adapter
Plain J2SE Adapter Engine
Partner Connectivity Kit PCK Configuration
File/DB/JMS File/DB/JMS SAP SAP System System
Adapter Engine http://
IS Runtime
System Landscape Directory • Holds component description including address data
Config. cache
Adapter Framework
XI Message OK / Error
Adapter Engine in SAP J2EE Integration Integration Repository Repository •• Holds Adapter Holds Adaptermetadata metadata
Adapter Sender
Module Processor
http:// Channel
Q Integration Builder / Directory:
Adapter Receiver
´Messaging
... Receiver determination • Party->Service->Action
Configuration cache
... Channel Definition: • Adapter Engine • Adapter Type • Message Protocol • Transport Protocol • Security • Channel Configuration
Tracing Logging Security
Monitoring
Administration
Configuration Master
End-to-End Monitoring (Sender / Receiver Agreement: • Party/Service/Action Channel © SAP AG 2004, TBIT40 07 Adapter Framework 10
AdapterSpecific Component Services
Message flow over all XI components / applications
Runtime Workbench • UIs for administration, monitoring
E I S
Full integration of Adapter Engine in SAP XI landscape Adapter Engine is based on Adapter Framework
Adapter Engine fully integrated with the SAP XI landscape Central configuration of connections to application systems (through appropriate adapters) in Integration Directory Reuse of Integration Directory’s existing versioning and transport capabilities Central administration and monitoring over adapters, Integration Server, Integration Engine through Runtime Workbench
© SAP AG 2004, TBIT40 07 Adapter Framework 11
Central and Local Adapter Engine Adapter Engine is open for adapter development by partners and customers JCA based adapter development as ‘state-of-the-art’ Java technology Additional services for configuration, monitoring, security etc. SAP XI Adapter Framework (as PCK), Adapter Framework Interface Specification, JCA sample adapter (incl. source code) available via SAP Integration and Certification Center
The Adapter Engine can be deployed centrally as part of Integration Server, or as optional local Adapter Engine on its own SAP J2EE Server Use of local Adapter Engine e. g. to be close to business system
© SAP AG 2004, TBIT40 07 Adapter Framework 12
Adapters hosted in Adapter Engine In addition to Adapter Framework, the Adapter Engine hosts a set of adapters: SAP Adapters File / FTP JDBC (Database) JMS (MQSeries, SonicMQ, …) RFC SOAP SMTP SAP BC (header extension for support of Quality of Service) SAP Marketplace Adapter RosettaNet (RNIF 2.0) Adapter CDIX (RNIF 1.1) Adapter
3rd Party Adapters iWay: UCCnet, more to come … Optional: Adapters developed by partners, certificated by SAP
© SAP AG 2004, TBIT40 07 Adapter Framework 13
SAP XI Adapter Partner System SAP relies on a system of partners to provide adapters for other applications and certain industry standards Adapter Reseller Agreement iWay Software UCCnet Adapter Oracle, Siebel, PeopleSoft
SEEBURGER AG EDI Adapters
WebMethods Applications (Oracle, Siebel, PeopleSoft, Baan, …) Industry Standards (RosettaNet, CDIX) SAP XI 3.0
Partner adapters are sold and delivered through SAP Technical Support SAP provides 1st level support via CSN, 24x7 Partners provide 2nd and 3rd level support via CSN, 24x7 © SAP AG 2004, TBIT40 07 Adapter Framework 14
Adapter Info on SAP Service Marketplace
SAP Service Marketplace: http://service.sap.com/xi SAP XI in Detail
© SAP AG 2004, TBIT40 07 Adapter Framework 15
Connectivity
Adapter Configuration
Adapter independent parameters
Adapter specific parameters
© SAP AG 2004, TBIT40 07 Adapter Framework 16
Remark: Future of SAP XI 2.0 Adapter Engine SAP XI 2.0 Adapter Engine is available in SAP XI 3.0 as “Plain J2SE Adapter Engine” Functional scope as in SAP XI 2.0: Adopted to the SAP XI 3.0 message protocol Minor maintenance issues, bug fixes
Recommendation: Use where platform requirements or limitations (hardware, operating system, JVM support) demand it
SAP XI 2.0 Adapter Engine works with SAP XI 3.0 landscapes, too
© SAP AG 2004, TBIT40 07 Adapter Framework 17
SAP XI 3.0 Architecture Integration Integration Repository Repository // Integration Integration Directory Directory // System System Landscape Landscape Directory Directory Content (e. g. Mapping, Adapter Metadata)
Integration Integration Server Server Business Process Engine Integration Engine Central Adapter Engine
© SAP AG 2004, TBIT40 07 Adapter Framework 18
File/DB/JMS File/DB/JMS Marketplace Marketplace rd Party 33rd Party Sys. Sys.
File/DB/JMS File/DB/JMS Marketplace Marketplace rd Party 33rd Party Sys. Sys.
Adapter FW Messaging Queuing Security Handling
Resource Adapter
SAP SAP System System
Adapter FW Messaging Queuing Security Handling
and Monitoring Resource Adapter
File File DB DB JMS JMS
Adapter Framework Messaging Queuing Security Handling
Optional local Adapter Engine Resource Adapter
Adapter
IDoc Adapter
Plain J2SE Adapter Engine
Partner Connectivity Kit PCK Configuration
File/DB/JMS File/DB/JMS SAP SAP System System
SAP Partner Connectivity Kit (PCK) Overview (1) SAP Partner Connectivity Kit is based on the Adapter Framework The PCK enables XML document exchange between SAP XI and business partners not using SAP XI PCK provides connectivity options to access SAP Adapters: File/FTP JDBC (Database) JMS SOAP SAP Web AS (J2EE only)
RFC
Integration Server
Partner Connectivity Kit PCK Configuration and Monitoring
XI PIPELINE
Resource Adapter
Adapter FW Messaging Queuing Security Handling
XI-SOAP/HTTP(S)
Communication between SAP XI and PCK is via SAP XI messaging protocol © SAP AG 2004, TBIT40 07 Adapter Framework 19
SAP Partner Connectivity Kit Overview (2)
The PCK is deployed on a standalone SAP J2EE Engine (part of SAP Web AS) within business partner’s landscape SAP Web AS (J2EE only) Partner Connectivity Kit PCK Configuration and Monitoring
© SAP AG 2004, TBIT40 07 Adapter Framework 20
Resource Adapter
Adapter FW Messaging Queuing Security Handling
Configuration, administration, and monitoring are done locally on the PCK itself without the need for an Integration Directory Configuration UI provides same “look and feel” as configuration UI of Adapter Engine
XI 3.0 Adapter Framework Agenda
SAP XI 3.0 Adapter Framework Overview SAP XI 3.0 Adapter Strategy Technical adapters in detail Summary
© SAP AG 2004, TBIT40 07 Adapter Framework 21
SAP Exchange Infrastructure - Openness Integration of SAP and non-SAP applications Adapter Framework for comprehensive integration of adapters Adapters are used for technical connectivity Adapter metadata and mappings are stored in Integration Repository
© SAP AG 2004, TBIT40 07 Adapter Framework 22
Dual Strategy Dual connectivity strategy Adapter Framework for comprehensive integration of adapters to provide technical connectivity, including central configuration, administration, monitoring of adapters Interoperability based on open standards (SOAP, JMS, HTTP(S)) to interoperate with EAI providers
Value proposition Standardized interfaces allow easy integration of adapters from different partners Minimum knowledge of SAP XI required Comprehensive integration avoids redundant maintenance, ensures consistency, enhances transparancy Openness to integrate non-SAP applications, 3rd party systems, etc. Reduced TCO
© SAP AG 2004, TBIT40 07 Adapter Framework 23
Certification
Certification SAP NetWeaver Certification of 3rd party adapters based on the adapter framework
Value proposition Certification helps customers to find right solution Faster implementation time and lower integration costs through the use of tested 3rd party integration Quality (stability, HA aspects, performance, etc.) of adapters is controlled Quick and convenient search for a variety of certified products with the online partner and product directory (http://www.sap.com/partners/icc) Reduced TCO
© SAP AG 2004, TBIT40 07 Adapter Framework 24
Adapter Mappings, Metadata in Integration Repository Adapter mappings and adapter metadata are stored in the Integration Repository Centralized Integration Repository contains all relevant information for collaborative and integrative processes All content adheres to open standards Adapters provide technical connectivity
Value proposition Use largest content catalog Reduce costs in integration projects Reduce maintenance costs Reduced TCO
© SAP AG 2004, TBIT40 07 Adapter Framework 25
XI 3.0 Adapter Framework Agenda
SAP XI 3.0 Adapter Framework Overview SAP XI 3.0 Adapter Strategy Technical adapters in detail Summary
© SAP AG 2004, TBIT40 07 Adapter Framework 26
Technical Adapters in Detail This section will give an overview of the functionality and usage of each technical adapter delivered with XI 3.0 RFC IDoc File JDBC JMS Plain HTTP Mail SOAP
Other adapters are covered in advanced or specialized workshops: RosettaNet CIDX SAP BC Marketplace Partner adapters (SEEBURGER, iWay, etc.) © SAP AG 2004, TBIT40 07 Adapter Framework 27
RFC Adapter Channel cache Integration Server
RFCClient/Server
J2EE AF (AE/PCK) Messaging System
Module Processor
XI RFC Adapter
XI-SOAP/http
RFC M1
JRFC/ JCo-lib
M... XI-SOAP/http
Mn
Adapter module: Localeejbs/RFCAFBean © SAP AG 2004, TBIT40 07 Adapter Framework 28
RFC
IDOC Adapter
Subsystem IDoc tRFC
Inbound IDoc Adapter
XI-Pipeline IDoc XML
SAP System
Integration Server
RFC dest Port FM
IDX1
EDI_OUTPUT_NEW
IDX2 FM IDocTYPE_READ_COMPLETE ...
RFC RFC dest Metadata Metadata
© SAP AG 2004, TBIT40 07 Adapter Framework 29
File Adapter
© SAP AG 2004, TBIT40 07 Adapter Framework 30
JDBC/JMS Adapter
ADAPTER ENGINE JDBC Driver XI-SOAP/HTTP QXTJ10005 MSG0000001 MSG0000002 MSG0000003 MSG0000004 MSG0000005 …
© SAP AG 2004, TBIT40 07 Adapter Framework 31
JMS Driver
Plain HTTP Adapter
The Plain HTTP Adapter is used to receive (send) arbitrary XML in the body of an HTTP-Post request... The Sender HTTP-adapter is an ICF service on the Integration Server (path /sap/xi/adapter_plain). The Receiver HTTP adapter is configured as a communication channel in the Integration Directory. Supports QoS BE, EO, and EOIO (specified in the query string of the URL). The HTTP adapter uses HTTP version 1.0, and does not support returning fault messages to the sender.
© SAP AG 2004, TBIT40 07 Adapter Framework 32
Plain SOAP Adapter
Sender
Receiver © SAP AG 2004, TBIT40 07 Adapter Framework 33
Example: Configure the JDBC Receiver Adapter
© SAP AG 2004, TBIT40 07 Adapter Framework 34
XI 3.0 Adapter Framework : Unit Summary
You should now be able to: Describe the Architecture of the SAP XI Adapter Framework. Detail the functionality of the Adapter Engine. Explain central and local Adapter Installations. Distinguish between the various adapter types. Describe the Partner Connectivity Kit. Configuration different adapters to send messages to and receive messages from the Integration Server.
© SAP AG 2004, TBIT40 07 Adapter Framework 35
SAP Exchange Infrastructure
Integration Process (Business Process) Management
Lecture topics
Topics XI Overview System Landscape Directory Integration Repository Integration Directory Runtime Runtime Workbench Adapter Framework Business Process Management Server Administration Security B2B and Industry Standards © SAP AG 2004, TBIT40 08 BPM 2
Business Process Management : Unit Objectives
After completing this unit, you will be able to: z Understand the need for Business Process Management in the Integration Scenario z Create an Integration Process (Business Process) in the Integration Repository. z Use a Integration Process (Business Process) in configuring a scenario. z Describe runtime aspects of Integration Processes (Business Processes).
© SAP AG 2004, TBIT40 08 BPM 3
Today’s Home-Grown Integration Landscapes … Business Partners SAP SAP SAP
SAP
other Integration Solution
B2B B2B Tool Tool
SAP
hard hard coded coded
SAP
3rd party
EAI EAI Tool Tool
mainframe application
3rd Party
© SAP AG 2004, TBIT40 08 BPM 4
B2B Tool
Business Partner Application
Adapter 3rd Party 3rd Party
Marketplace
Process Driven Integration Solution … Business Partners SAP
other Integration SAP XI Solution
SAP
SAP
SAP
SAP Business Workflow
3rd party
SAP
3rd party BPMS Message Oriented Middleware
SAP
3rd party WfMS
RosettaNet Middleware
Business Partner Application
mainframe application
3rd Party
3rd Party 3rd Party
Marketplace Programmed Workflow
BPMS: Business Process Management System WfMS: Workflow Management System © SAP AG 2004, TBIT40 08 BPM 5
Integration with SAP Exchange Infrastructure (SAP XI) SAP NetWeaver SAP
Business Partners
SAP
SAP
SAP
SAP Business Workflow
ccBPM SAP XI 3rd party
SAP
other Integration Solution
ccBPM SAP
RosettaNet Middleware
Business Partner Application
mainframe application other Integration Solution
3rd Party
3rd Party 3rd Party
Marketplace Programmed Workflow
© SAP AG 2004, TBIT40 08 BPM 6
Business Process Management (BPM) Ad-hoc Workflow Team-driven processes Spontaneous events Collaboration
Cross-Component BPM Design, execute and monitor automated processes across applications and systems Stateful interaction model Cross application execution
Business Workflow Design, execute and monitor processes within applications Apply standard business rules Business events Human interaction
© SAP AG 2004, TBIT40 08 BPM 7
Cross-Component BPM in a Nutshell Design, execute and monitor automated processes across applications Provides process control in the central technology layer Contains a Graphical Process Editor Contains a Business Process Engine Integral part of XI
Integration Repository (Design) Integration Directory (Configuration) Integration Server (Runtime)
Adheres to open modeling standards
BPEL4WS 1.1
Industry standard support
Business System 1
Business System 2
Business System 3
1
2
3
Messages
Integration Server Business Process Engine Integration Engine
RosettaNet (RNIF adapter, PIP, …)
Technical Process Monitoring
Integrated with technical Monitoring of XI Graphical Process Monitoring
4 Message
Business System 4 © SAP AG 2004, TBIT40 08 BPM 8
Cross-Component BPM Architecture – Overview Integration Server
Integration Builder
Business Process Engine
Integration Directory
Process Execution
Correlation Handling
Business Process (Configuration) Routing Rules Process / Message Store
Business Process (Definition) Abstract
2 3 Routing
Mapping
1
Integration Engine
Interfaces Adapter Engine
© SAP AG 2004, TBIT40 08 BPM 9
Channel Det.
4
Message
Integration Repository Message
Process Editor
(References)
Business Processes at Design Time Business Process as a Repository Object Integration Repository Business Process (Definition) Abstract
Interfaces
Graphical Process Editor “Native” access to all process relevant XI design objects: interfaces, mappings Adheres to standards
Open standards support (BPEL4WS) Import/ export of process definitions
Abstract Interfaces
Bi-directional (inbound & outbound) Used by BPM & RNIF adapter
Business Process Modeling Message relevant process elements
Trigger and receive, send, receiver determination, transformation (merge & split)
Process flow elements
Switch, container operation, control (terminate, throw exception, throw alert), block (exceptions & deadlines), fork (parallel sections), loop, wait, “undefined” (empty)
Process data (for data declaration) Conditions © SAP AG 2004, TBIT40 08 BPM 10
Architecture – Definition Repository Business Scenario Business Scenario
SWCV
*
Process Process Business Process Business Process Flow Flow If If * * * *
MessageType MessageType AbstractInterfaces AbstractInterfaces
Idoc Idoc
Context objects Context objects
RFC RFC
Interf. Mappings Interf. Mappings
MessageMappings MessageMappings
*
Directory Scenario Scenario
Party
Process Process Process Process
Routing Relation Routing Relation Mapping Relation Mapping Relation
Cache/Runtime Process Process Flow
XML-objects XML-objects
If *
© SAP AG 2004, TBIT40 08 BPM 11
*
Correlations Correlations
Big Picture – Components Client
IS
J2EE
Repository Design Design Flow
*
XI XIobjects objects
1
If
ProcessEngine ProcessEngine
*
Monitoring 6
Business Process
2
Runtime
Import
5 Definition XML-Objects Correlations
Directory Configuration Configuration
XI XIobjects objects Process definition
Routings Routings Mappings Mappings ......
* 3
Change list
4 Cache-Refresh Deployment Rules
© SAP AG 2004, TBIT40 08 BPM 12
* *
*
Business Processes & Business Scenarios Business Process can be incorporated in a Business Scenario Representation in a swim lane Treated as a Business System Navigation from Scenario to Process
© SAP AG 2004, TBIT40 08 BPM 13
Business Process Editor
Header
Process overview Edit area
Property area
Output area © SAP AG 2004, TBIT40 08 BPM 14
Object area
Edit area in detail Message related step types
Process control related step types
Other commands
Drag and drop
Horizontal and vertical modelling
Printing capabilities Process overview as navigation help for large process definitions © SAP AG 2004, TBIT40 08 BPM 15
Object area in detail
The correlation list holds all correlations used by this process
The container holds the data declaration of the process
© SAP AG 2004, TBIT40 08 BPM 16
The process signature shows all the abstract interfaces received and sent by the process
Property area in detail
Container-operation step
Receive step
Property sheet as unified medium for step setting Transformation step
© SAP AG 2004, TBIT40 08 BPM 17
Output area in detail
Search Result shows all objects that match the search ciriteria.
Tasks show the result of the syntax check (filtering on severity level possible)
© SAP AG 2004, TBIT40 08 BPM 18
Messages show immediate consequences of userinteractions (filtering on severity level possible)
Process Step-Types MESSAGING RELEVANT RECEIVE
Block
SEND TRANSFORMATION RECEIVER DETERMINATION PROCESS FLOW CONTROL RELEVANT CONTAINER-OPERATION CONTROL (deadlines, exceptions, alerts) WHILE LOOP
EMPTY
FORK
WAIT
BLOCK
SWITCH
© SAP AG 2004, TBIT40 08 BPM 19
CK BLO LE MP EXA
Message Relevant Steps RECEIVE
You use a receive step to receive a message. SEND
You use a send step to send either an asynchronous or synchronous message or an acknowledgment. TRANSFORMATION
You use a transformation step to change a message inside the process. RECEIVER DETERMINATION
You use a receiver determination step to get a list of receivers for a subsequent send step. © SAP AG 2004, TBIT40 08 BPM 20
Flow Control Steps (1) SWITCH
You use a switch to define different processing branches for a process. CONTAINER-OPERATION
You use a container operation to set a value for a target container element at runtime. CONTROL (deadlines, exceptions, alerts)
You use a control step to do the following to execute process controls (e.g, terminate a process). BLOCK
You use a block to combine steps that you want to execute one after the other and which are to access the same local data. © SAP AG 2004, TBIT40 08 BPM 21
Flow Control Steps (2) FORK
You use a fork when you want to continue a process in branches that are independent of each other. WHILE LOOP
You use a while loop to repeat the execution of steps within the loop. WAIT
You use a wait step to incorporate a delay in a process.
EMPTY
You use an empty (undefined) step as a placeholder. © SAP AG 2004, TBIT40 08 BPM 22
Process Data Messaging Relevant Process Data Variables typed by abstract interfaces Variables typed as receiver Read access to message-payload via
XPath
Context objects
Process Flow Relevant Data Variables typed by XSD simple types (e.g. used for loop-counter, ...)
Process Trigger Via messages (trigger receive) Scheduling (batch jobs)
© SAP AG 2004, TBIT40 08 BPM 23
Correlations
Correlation Handling Routing of messages (Business Documents) to process instances Dependencies rely on business data (e.g. Message ID, Order ID, Business Partner ID, Company Code) Correlations define these dependencies
© SAP AG 2004, TBIT40 08 BPM 24
SAP NetWeaver: Business Process Content
Process Editor
Integration Builder
SAP Business Process Content
Integration Directory
XI scenario & process pattern templates (XI 3.0)
Business Process (Configuration)
SAP solution process content (delivered with SAP solutions)
References
Integration Repository Business Process (Definition)
SAP Solutions
Industry standard content (as e.g. RosettaNet)
Industry Standards XI Process Patterns Workflow Templates Patterns
© SAP AG 2004, TBIT40 08 BPM 25
Business Process Patterns Process Process Container
Serialization Loop
A type AIF1 AT type AIF1* B type AIF2 C type int
S_FL1: single message trigger S_FL2: multi message trigger Receive message on A
Correlations MyCorrelation ID type int
Add 1 to C
(N:1) (1:N)
Collect (same IF type/ different IF type) Append A to AT
C_FL1.1: payload-triggered end C_FL1.2: time-triggered end
Process Interface AIF1 in AIF2 out
Transformations/Merge/Split
C_FL1.3: message triggered end While C A.number Transformation Merge AT into B
C_FL2.1: collect all C_FL2.2: collect some (condition based)
Multicast Send message on B
© SAP AG 2004, TBIT40 08 BPM 26
M_FL1: send in a sequence M_FL2: send in parallel
Configuration Time: Integration Directory A Business Process Integration Directory Business Process (Configuration) Routing Rules
Is identified by a name and belongs to a Party analogous to a Business Systems Contains a reference (link) to its originating repository process
Can only be deployed not created in the directory
Business Process Wizard to import Process reference from the Integration Repository Routing and Mapping Relations Business processes can act as source or target (sender/receiver) as Business Systems Process Wizard
© SAP AG 2004, TBIT40 08 BPM 27
Runtime
Runtime Processes participate in the common cache-mechanism Executable process-definition and depending objects are created Business Process Engine
Enhancement of SAP WebAS Workflow Engine
Stable, proven and robust technology
Monitoring = Technical Monitoring Entry from message view (XI runtime) Entry from process view (Process runtime) Seamless navigation between the monitoring tools
© SAP AG 2004, TBIT40 08 BPM 28
Runtime cache in detail (SXI_CACHE) Runtime cache viewer knows Business Processes
Workflow Builder uses same look and feel as the Process Builder in IB (tiles and other concepts)
Business Workflow tools in a special profile
© SAP AG 2004, TBIT40 08 BPM 29
Business Process Monitoring
BPE Monitoring Process Instances Processes with missed deadline Error Diagnosis Restart processes RFC Monitor
© SAP AG 2004, TBIT40 08 BPM 30
Technical Monitoring of Business Processes Technical monitoring Entry from message view (Integration Engine) Entry from process view (Business Process Engine) Navigation between the monitoring tools
Integration in Monitoring Infrastructure Process Engine Component Test (Runtime Workbench) Technical Process Monitoring (end-to-end) SAP Alert Framework
Business Alerts
SAP CCMS integration
© SAP AG 2004, TBIT40 08 BPM 31
System failures
Current Process Modeling Approaches Value Potential
Business View
Management/ Business Analyst
Business blueprinting Project planning High-level executive model
Static Implementation View
Business Analyst/ Developer
Implementation information Component view Process configuration model
Dynamic Implementation View
IT Specialist/ Developer
© SAP AG 2004, TBIT40 08 BPM 32
Executable processes State engine Process execution model
Business Benefits
Up to 50% 2 months - 2 weeks*
Reduced delivery times
$ 250 per vehicle**
Cost advantage via online sales
Up to 14%**
Reduction in Supply Chain Costs
OEM
Importer
Dealer
Business Benefits Cost advantage via online sales
$ 800 per vehicle**
Reduced days supply inventory
From 75 to 35 days**
Customer SelfInformation
5.1%***
Interactive configuration
27.2%***
Vehicle Specification/ Search Request via Internet
Vehicle Locating and Allocation Reservation Planning
Value Potential
Scenario Maps/ Solution Maps
Reduced inventories
Collect information about customer requirements and preferences
Order Processing
Production Production
Order Tracking Order Tracking
Speed up buying
Consistent Dealer Database
Online information to customer reduces time of communication
Pooled data on cars available
Visibility of tracking status
Speed up handing over of vehicle
Increased customer satisfaction
Shipment
Improved market intelligence
Tracking
Faster reaction to market trends
Transport Control
Increased customer satisfaction
Increased planning security and quality
Goods Receipt Processing
Business Scenarios
Business Processes
7.5%*** 12.6%***
5.5%***
Unified Business Process Management Unified Modeling Environment
One Architecture for workflow and automated processes Modeling Design
Model driven Implementation as far as possible One common Repository SAP Execution Applications & Composites,
Business Activity Monitoring
BPM
Process Monitoring
Process logic decoupled from applications Process Configuration
Flexible process design & configuration Process Execution
Integrated in SAP NetWeaver
SAP XI & Workflow Business Objects Monitoring Technical Process Monitoring
Unified approach for A2A and B2B Integration Business Activities Business Events
Business Activity Monitoring © SAP AG 2004, TBIT40 08 BPM 33
Enterprise Services Business Objects
Open Standards Support
Unified BPM: High Level Architecture Co-Development with IDS Scheer AG based on:
MODELING Unified Modeling UI
ARIS Modeling UI
Unified Look & Feel
Modeling Views & Roles
SAP NetWeaver Repository
Versioning
Software Logistics
SAP Execution
SAP Applications & Composites
ccBPM (SAP XI)
Workflow
Business Objects & Services
Complementary Monitoring Technology
Technical Monitoring
Service Infrastructure
Business Activity Monitoring (BAM) z Process Efficiency Monitoring z Event Resolution
© SAP AG 2004, TBIT40 08 BPM 34
UI Framework
REPOSITORY Process Models & Abstractions
EXECUTION Composite Application Application
Process Engine
Workflow
Monitoring Data Collection
MONITORING Technical
BAM
Business Process Management : Unit Summary
You should now be able to: z Understand the need for Business Process Management in the Integration Scenario z Create an Integration Process (Business Process) in the Integration Repository. z Use a Integration Process (Business Process) in configuring a scenario. z Describe runtime aspects of Integration Processes (Business Processes).
© SAP AG 2004, TBIT40 08 BPM 35
SAP Exchange Infrastructure Server Administration
Lecture topics
Topics XI Overview System Landscape Directory Integration Repository Integration Directory Runtime Runtime Workbench Adapter Framework Business Process Management Server Administration Security B2B and Industry Standards © SAP AG 2004, TBIT40 09 Server Administration 2
Server Administration: Unit Objectives
After completing this unit, you will be able to: Explain which XI components reside in the Java and ABAP parts of the Web Application Server Manage Logs in the J2EE stack. Use Tracing and Logging of the XI ABAP components. Define conditions and actions for troubleshooting.
© SAP AG 2004, TBIT40 09 Server Administration 3
XI 3.0 components in SAP Web AS 6.40 HTTP(s) ICM
HTTP(s)
Central Monitoring
J2EE
ABAP
XI Tools Business Process Engine
Integration Builder (IR, ID) Runtime workbench
JRFC
Mapping runtime Integration Engine Adapter Engine SLD
OpenSQL for Java © SAP AG 2004, TBIT40 09 Server Administration 4
OpenSQL for ABAP
Web AS 6.40 - key architecture points
J2EE stack SQLJ layer for database connectivity All objects stored in database SLD is delivered with the J2EE Engine UME for user management
Middleware JRFC replaces JCo for J2EE to ABAP connectivity
ABAP stack Integration Engine is part of BASIS (and corresponding support packages)
© SAP AG 2004, TBIT40 09 Server Administration 5
Integration Engine Administration
SXMB_ADM
Administration: •Tuning capabilities for queues: • Special queue for large messages • Balancing between parallel queues •Schedule Jobs
Configuration: •Time-controlled message processing •“Switch procedure“ for message deletion •Pipeline Definition/Settings
© SAP AG 2004, TBIT40 09 Server Administration 6
J2EE Engine – Administration overview J2EE Engine Administrator Configuration tool
Offline configuration editor © SAP AG 2004, TBIT40 09 Server Administration 7
Tracing and Logging J2EE-based components of XI use standard logging of J2EE Engine Setup via Log Configurator Service in Visual Administrator tool
© SAP AG 2004, TBIT40 09 Server Administration 8
Standalone Log Viewer UI Connect to any number of WebAS servers (ABAP/J2EE)
© SAP AG 2004, TBIT40 09 Server Administration 9
Integrated Log Viewer UI Accessible via J2EE Visual Administrator tool
© SAP AG 2004, TBIT40 09 Server Administration 10
Trace and Log Files for the XI J2EE components Under /cluster/server0/log/applications/com.sap.xi
repository.log
repository.trc
directory.log
directory.trc
mapruntime.log
mapruntime.trc
rwb.log
rwb.trc
xi.log
xi.trc
Default trace file for entire J2EE Engine: /cluster/server0/log/defaultTrace.trc
© SAP AG 2004, TBIT40 09 Server Administration 11
Trace and Log Files in the ABAP Part
Usage of logging parameter: You set this parameter when you want to analyze message processing as it enables you to document either individual steps, or all steps in a pipeline. © SAP AG 2004, TBIT40 09 Server Administration 12
Trace and Log Files in the ABAP Part
The parameter TRACE_LEVEL enables you to locally set the trace level for all pipelines in an Integration Engine.
© SAP AG 2004, TBIT40 09 Server Administration 13
Defining Conditions and Actions for Troubleshooting In the Integration Engine, you can specify conditions for troubleshooting in inbound messages that trigger particular actions (Example: Writing trace and log information to a file). The procedure for creating a conditioned action is divided into the creation of one or more conditions and one or more actions.
© SAP AG 2004, TBIT40 09 Server Administration 14
Integration Builder – Administration page
System information Administration of locks Migration tool
© SAP AG 2004, TBIT40 09 Server Administration 15
BPE trace In case of any problems or error situations it is recommended to turn on tracing by using transaction SWELS
© SAP AG 2004, TBIT40 09 Server Administration 16
Summary SAP introduced significant changes in the SAP Web AS architecture for version 6.40. In particular, improved J2EE Engine architecture allows better performance, system administration, and monitoring There are also better performance tuning capabilities for Integration Engine
© SAP AG 2004, TBIT40 09 Server Administration 17
Server Administration: Unit Summary
You should now be able to: Explain which XI components reside in the Java and ABAP parts of the Web Application Server Manage Logs in the J2EE stack. Use Tracing and Logging of the XI ABAP components. Define conditions and actions for troubleshooting.
© SAP AG 2004, TBIT40 09 Server Administration 18
SAP Exchange Infrastructure
Security
Lecture topics
Topics XI Overview System Landscape Directory Integration Repository Integration Directory Runtime Runtime Workbench Adapter Framework Business Process Management Server Administration Security B2B and Industry Standards © SAP AG 2004, TBIT40 10 Security 2
Security : Unit Objectives
After completing this unit, you will be able to: z Understand User Management and security for the Exchange Infrastructure. z Describe the built-in users and roles in XI. z Implement message-level security. z Implement channel-level security. z Place the Exchange Infrastructure in the network landscape securely. z Manage the J2EE key store.
© SAP AG 2004, TBIT40 10 Security 3
Why Is Security Necessary?
Business processes executed using XI have to be done in a secure manner. XML messages which contain confidential business data need to be transported over a secure connection Security requirements also apply to communicating XI components- securing information like user names and passwords The messaging system has to be sited securely in the network environment.
© SAP AG 2004, TBIT40 10 Security 4
Security Topics
User Management, Authentication & Authorization
Message level security
Network and Communication Security
Recommended setup for interenterprise connectivity
Certificate management in the J2EE key store
© SAP AG 2004, TBIT40 10 Security 5
User Administration And Authentication
All components of XI 3.0 that run on the SAP Web AS use the underlying infrastructure provided by the Web AS for the following: User management Administration Authorizations Authentication (The only exception is for the J2SE adapters)
© SAP AG 2004, TBIT40 10 Security 6
User Administration And Authentication
User Store Standard: Users are maintained in the ABAP user store Can also be integrated with LDAP based user administration
Certificate Store XI and RNIF protocols support message level security based on digital signature RNIF protocol also supports encryption The required certificates to be used need to be entered into the key store of the J2EE engine In the Integration Directory these certificates are referred by the name of the key store view and the certificate name Recommended to store CA certificates in the TrustedCAs view
© SAP AG 2004, TBIT40 10 Security 7
Users With respect to authentication and authorization, we distinguish two major scenarios: z During design and configuration, dialog users communicate through the Integration Builder with XI. zAt runtime the actors are computer systems rather than humans! 1. At design and configuration time (Integration Repository/Directory)
Real User
© SAP AG 2004, TBIT40 10 Security 8
2. At runtime
Computer systems
Dialog Users
Dialog users represent human users that log on through the various UIs of the Integration Builder Dialog users are generally maintained in the ABAP part of the SAP Web AS The roles for the different dialog users are predefined and shipped with the installation
© SAP AG 2004, TBIT40 10 Security 9
Service Users Service users provide dialog free access to XI components Service users have the SAP user roles on the ABAP part of the Web Application Server They are made available on the J2EE part as user groups Service users have the required authorizations to access the required services on the addressed XI components Service users are created during installation Names and passwords can be assigned during installation
© SAP AG 2004, TBIT40 10 Security 10
Service Users During Design And Configuration XIREPUSER – Access the XI Repository for Design XIDIRUSER – Access the XI Directory for Configuration XIISUSER - Get Cache-updates from XI Directory to RuntimeCache XILDUSER - Get Business System Name from System Landscape Directory Integration Builder
Central Monitoring
Integration Repository (IR)
XIREPUSER
XIISUSER Integration Directory (ID)
SAP Systems
Integration Server (IS)
XIDIRUSER System Landscape Directory (SLD)
© SAP AG 2004, TBIT40 10 Security 11
3rd Party Systems 3rd Party Middleware Component Marketplace/ Business Partner
XI Service Users In Use During Runtime XILDUSER – Get Business System Name from System Landscape Directory XIRWBUSER – Get monitoring information to Runtime Workbench XIISUSER – Get Cache-updates from XI Directory to Runtime Cache XIAPPLUSER – Access XI Engines for message processing (SAP template) XIAFUSER – Access Adapter Framework Central Monitoring
XIRWBUSER Business Process Engine
Integration Server
IntegrationXIISUSER Directory
Integration Engine
SystemXILDUSER Landscape Directory
Adapter Engine customer specific copy of XIAPPLUSER
XILDUSER
Local Integration Engine Proxy Runtime Proxy
SAP Web AS ≥ 6.20 © SAP AG 2004, TBIT40 10 Security 12
XIAFUSER
IDocs RFCs
SAP System
File DB JMS
3rd Party Apps
Apps of Business Partner
Partner Connectivity Kit Apps/Systems of (small) Business Partner
Default Service Users In XI Systems And Their Roles Created automatically at installation time. Referenced in the Exchange Profile. In the future it will be possible to create custom UserIDs at installation time must have the role: SAP_XI_IR_SERV_USER must have the role: SAP_XI_ID_SERV_USER must have the role: SAP_XI_APPL_SERV_USER must have the role: SAP_XI_IS_SERV_USER must have the role: SAP_XI_RWB_SERV_USER must have the role: SAP_XI_AF_SERV_USER_MAIN must have the role: SAP_BC_AI_LANDSCAPE_DB_RFC © SAP AG 2004, TBIT40 10 Security 13
User Maintenance
Users and roles are maintained via the standard Web AS ABAP user management (SU01) After a short delay, the updated users are automatically replicated to the J2EE engine
J2EE User maintenance in Visual Administrator tool Æ Security provider service UME (User Management Engine) available as part of J2EE engine
© SAP AG 2004, TBIT40 10 Security 14
J2EE User Maintenance Å Visual Admin tool
UME frontend Æ
© SAP AG 2004, TBIT40 10 Security 15
Security Topics
User Management, Authentication & Authorization
Message level security
Network and Communication Security
Recommended setup for interenterprise connectivity
Certificate management in the J2EE key store
© SAP AG 2004, TBIT40 10 Security 16
Security – Availability With XI 3.0 Availability Levels of Security Connection Level Security (HTTPS)
XI 1.0 /
XI 3.0
XI 3.0
XI 2.0
XI protocol
RNIF
3
3
3
3 3 3
3 3 3
Message Level Security (for B2B) Signature Data Integrity Non-Repudiation of origin
3
Non-Repudiation of receipt
3
Encryption Technology
© SAP AG 2004, TBIT40 10 Security 17
WS-Security (XML-Signature)
S/MIME
Security – Outlook Availability Levels of Security Connection Level Security
XI 1.0 /
XI 3.0
XI 3.0
XI 2.0
XI protocol
RNIF
3
3
3
3 3 3
3 3 3
Message Level Security (for B2B) Signature Data Integrity Non-Repudiation of origin Non-Repudiation of receipt
3
Encryption Focus of future security enhancements for XI © SAP AG 2004, TBIT40 10 Security 18
3
Message Exchange
In general, the message exchange between business systems can be separated into two communication segments that are treated differently from an authentication and authorization point of view:
1. Sending System to Integration Server Business System
2. Integration Server to Receiving System XI 3.0
Business System
HTTP(S)
HTTP(S)
Technical communication configured only once
Configuration done in the Integration Directory
© SAP AG 2004, TBIT40 10 Security 19
Message Level Security Message level security enabled through the use of digital signatures in XI 3.0 Digital signatures authenticate sending partner and ensure data integrity Adds security qualities to communication level security that are required for B2B communication Message level security for XI 3.0 protocol is based on the Web Service security standard RosettaNet employs the S/MIME standard Encryption ensures that the message content is confidential Only supported by the RNIF protocol
© SAP AG 2004, TBIT40 10 Security 20
Archiving Secured Messages
For non-repudiation, secured messages are archived in the non-repudiation store For each secured message the following data is stored: The raw message Security policy as configured in the directory References to certificates in the key store Identification of the certification used
The archive can be monitored using the Runtime Workbench The non-repudiation archive is only available for the RNIF protocol © SAP AG 2004, TBIT40 10 Security 21
Security Topics
User Management, Authentication & Authorization
Message level security
Network and Communication Security
Recommended setup for interenterprise connectivity
Certificate management in the J2EE key store
© SAP AG 2004, TBIT40 10 Security 22
Network And Communication Security
HTTP and SSL XI runtime components support encryption of the HTTP data stream using SSL A certificate must be installed on the server component based on X.509 to enable HTTPs
Configuring SSL for message exchange for ABAP and Java are different SSL can also be configured for technical communication like cache updates and respository access in the directory
RFC and SNC Connections between SAP components can be secured by SNC SNC supports three levels of security protection •Authentication only •Integrity protection •Confidentiality protection WebAS security guide explains how to set up SNC © SAP AG 2004, TBIT40 10 Security 23
SSL And SNC For Secure Connections
Secure connection possible between the following Between adapters and Integration Server Between business systems and Integration Server Between PCK and Integration Server Between business systems and adapters Cache updates
© SAP AG 2004, TBIT40 10 Security 24
Security Topics
User Management, Authentication & Authorization
Message level security
Network and Communication Security
Recommended setup for interenterprise connectivity
Certificate management in the J2EE key store
© SAP AG 2004, TBIT40 10 Security 25
B2B Communication – Recommended Setup Server LAN Firewall
Inner DMZ Firewall
Firewall
Firewall
Outer DMZ
Application Gateway External Partners
IS
Business Systems
Internet
Proxy
Proxies and application gateways are placed in the outer DMZ providing access control between Internet and internal networks © SAP AG 2004, TBIT40 10 Security 26
Security Topics
User Management, Authentication & Authorization
Message level security
Network and Communication Security
Recommended setup for interenterprise connectivity
Certificate management in the J2EE key store
© SAP AG 2004, TBIT40 10 Security 27
The J2EE Key Store Trusted certification authorities on J2EE key store
© SAP AG 2004, TBIT40 10 Security 28
Requesting A Server Certificate Creation of server certificate
© SAP AG 2004, TBIT40 10 Security 29
Importing the Server Certificate Import the certificate signing response file into your key store
© SAP AG 2004, TBIT40 10 Security 30
Import The Partner Public Key Import the public key of your partner
© SAP AG 2004, TBIT40 10 Security 31
Viewing The Public Key Partners public key in the J2EE key store
© SAP AG 2004, TBIT40 10 Security 32
User Autentication User authentication for the different views created
© SAP AG 2004, TBIT40 10 Security 33
Further Documentation
XI 3.0 Security Guide
SAP Web As Network and Communication Security: This section describes the network and communication security for the SAP Web AS.
SAP Web AS Security Guide for ABAP Technology: This section describes the security aspects involved with the SAP WebAS when using ABAP technology.
SAP Web AS Security Guide for J2EE Technology: This section describes the security aspects involved with the SAP WebAS when using Java or J2EE technology.
© SAP AG 2004, TBIT40 10 Security 34
Security : Unit Summary
You should now be able to: z Understand User Management and security for the Exchange Infrastructure. z Describe the built-in users and roles in XI. z Implement message-level security. z Implement channel-level security. z Place the Exchange Infrastructure in the network landscape securely. z Manage the J2EE key store.
© SAP AG 2004, TBIT40 10 Security 35
SAP Exchange Infrastructure
B2B and Industry Standards
Lecture topics
Topics XI Overview System Landscape Directory Integration Repository Integration Directory Runtime Runtime Workbench Adapter Framework Business Process Management Server Administration Security B2B and Industry Standards © SAP AG 2004, TBIT40 11 B2B Industry standards / 2
B2B and Industry Standards : Unit Objectives
After completing this unit, you will be able to: z Explain the XI Infrastructure for supporting B2B scenarios and Industry Standards. z Describe the configuration objects to use for implementing B2B scenarios. z Describe SAP Business Packages for Industry.
© SAP AG 2004, TBIT40 11 B2B Industry standards / 3
B2B And Industry Standards Support – Challenges Business Partners
Mainframe Application
Hard-coded Integration
SAP Application EAI Tool
Industry Standard Protocols
SAP Application
Other Integration Solution Marketplaces
B2B Tool
Industry standard Adapter
Security
Workflow Tool
3rd Party Application
B2B Tool
Business Partner Application
• Different solutions for A2A and B2B scenarios • Custom solutions to connect to Industry Standards compliant business partners • Substantial effort to develop and support mappings to standard interfaces • Small business partners have to invest heavily to be industry standards compliant • Different solutions used to connect to Marketplaces • Use of proprietary technologies for security handling in B2B scenarios © SAP AG 2004, TBIT40 11 B2B Industry standards / 4
B2B In XI 3.0 Overview
Industry Standard Protocols Business Partners Any Application
SAPApplication
B2B Messaging Business Partners
Partner Connectivity Kit
SAP XI
Security
Small Trading Partners
© SAP AG 2004, TBIT40 11 B2B Industry standards / 5
Market places
B2B In XI 3.0
SAPApplication Any Application
Industry Standard Protocols Integration Server Integration Directory
Business Partners
BPE
Collaboration Agreements Collaboration Profiles
B2B Messaging
Integration Engine
Business Partners
Integration Repository Adapter Engine Business Scenarios
Mappings Message Interfaces
© SAP AG 2004, TBIT40 11 B2B Industry standards / 6
Adapter Framework Messaging Queuing Security Handling
Security
Business Processes
Partner Connectivity Kit Small Trading Partners
B2B Related Configuration In The Directory Creation of Party The new object party facilitates the B2B functions of SAP Exchange Infrastructure and contains the following information: Name, description, and additional identifiers (DUNS, GLN or SCAC) of the party
© SAP AG 2004, TBIT40 11 B2B Industry standards / 7
B2B Related Configuration In The Directory Creation of Service
The new object service generalizes business systems. A service can represent: A business system (in A2A scenarios) Semantical units (grouping of interfaces), which are used mainly for routing purposes in the communication between multiple B2B parties. An example would be a specific PIP® (RosettaNet). A business process
© SAP AG 2004, TBIT40 11 B2B Industry standards / 8
B2B Related Configuration In The Directory
Creation of a Channel Communication channels can be used in two directions Sender communication channel -Receiver communication channel
For configuring specific adapters you can use the predelivered communication channels called channel templates Channel templates also contain the security policies Contains specific information for the message protocol, transport protocol, URL, logon data and adapter specific configuration This also helps in the central configuration of adapters in the Integration directory © SAP AG 2004, TBIT40 11 B2B Industry standards / 9
B2B Related Configuration In The Directory Creation of Sender and Receiver Agreements
The new objects sender agreement and receiver agreement describe which channel to use and specify the party related security settings like certificates The sender agreement is used on the Integration Server for inbound processing, the receiver agreement for outbound processing. Sender agreement and receiver agreement can be subsumed under the term „collaboration agreement“.
© SAP AG 2004, TBIT40 11 B2B Industry standards / 10
B2B Security Details Availability Levels of Security Connection Level Security (HTTPS)
XI 1.0 /
XI 3.0
XI 3.0
XI 2.0
XI protocol
RNIF
3
3
3
3 3 3
3 3 3
Message Level Security (for B2B) Signature Data Integrity Non-Repudiation of origin
3
Non-Repudiation of receipt
3
Encryption Technology
© SAP AG 2004, TBIT40 11 B2B Industry standards / 11
WS-Security (XML-Signature)
S/MIME
B2B In XI 3.0 Collaboration Partner Data in the Integration Directory Manages technical characteristics of partners to facilitate document exchange such as ¾Party identification ¾Message formats and versions supported ¾Security requirements ¾Collaboration Agreements
Partner Connectivity Kit ¾For small business partners ¾Enable business partners of XI customers to conduct XML document exchange with XI ¾Small scale easy to use client
B2B security (Signature/Encryption) XI as marketplace messaging infrastructure © SAP AG 2004, TBIT40 11 B2B Industry standards / 12
SAP XI Provides Industry Standards Technology
Any Application
SAPApplication
Industry Standard Protocols Integration Server Integration Repository & Integration Directory
Business Partners
BPE
B2B Messaging
Integration Engine
Business Partners
Security
Adapter Engine
© SAP AG 2004, TBIT40 11 B2B Industry standards / 13
Partner Connectivity Kit Small Trading Partners
Industry Standards Support
SAP Industry Solution IDOC/Proxy
Integration Server
SAP CRM
BPE
Integration Directory Business Partner Collaboration Agreements
Integration Engine
Collaboration Profiles Adapter Engine
Integration Repository Adapter Framework
Business Scenarios Business Processes
Application↔Standard
Mappings
Business Doc Schema
Message Interfaces
© SAP AG 2004, TBIT40 11 B2B Industry standards / 14
Industry Standard Protocol
SAP Business Packages For Industry Standards Provides Solution Kits for specific industries and delivers mappings for RosettaNet and CIDX
Application adoption Enhance business applications like mySAP CRM or mySAP SCM to support SAP Business Packages for high priority processes
Mapping Including message sets for the industries according their priority Support mappings: versions, upgrade, maintenance
Process Integration SAP Business Packages’ message protocol implementation (such as RNIF 2.0 and RNIF 1.1 for CIDX) Provision of Collaboration Agreements Business Process Management support
© SAP AG 2004, TBIT40 11 B2B Industry standards / 15
B2B and Industry Standards : Unit Summary
You should now be able to: z Explain the XI Infrastructure for supporting B2B scenarios and Industry Standards. z Describe the configuration objects to use for implementing B2B scenarios. z Describe SAP Business Packages for Industry.
© SAP AG 2004, TBIT40 11 B2B Industry standards / 16
View more...
Comments