Sukumar Natarajan SAP NetWeaver RIG - XI

Transcription

1 SAP XI Framework Sukumar Natarajan SAP NetWeaver RIG - XI

2 Learning Objectives As a result of this workshop, you will be able to: Understand the architecture of SAP XI Framework To explain why central configuration and decentral execution is not a contradiction Get the picture about extending the adapter framework for partner and customer solutions based on open standards

3 Framework Overview Engine Openness and Extensibility

4 The SAP XI Framework Based on SAP J2EE Engine Uniform Handling of Deployment, Configuration, Administration (User, SLD-Registration), Monitoring, Security, Extensions and -Development Technical Basis for Engine (central and decentral) and SAP Partner Connectivity Kit The individual s run as Services within the SAP J2EE Engine while using the J2EE-Services of the Framework (e.g. Queuing/Logging) and of the SAP J2EE Engine Usage of open standards: SOAP, XML, J2EE, JCA, JMS, JDBC..

5 SAP XI Framework Building Blocks XI Integration Server R XI Framework on SAP J2EE Server 6.40 XI Messaging Service R AF Module Processor R 3 R 2 R 3rd Party JCA 1.0 Connected System Integration Directory R Configuration Services Generic AF modules 4 R specific modules R external protocol System Landscape Directory R Cache JCA 1.0 Framework 1 R Runtime Workbench R Administratio nal Services Utilities (Threads, Transactions) 5 R 6 R 7 Logging API Log File & Audit DB Integration Repository 4 R R 8 (configuration) meta data (xsd) Message Definition (WSDL, xsd, dtd)

6 Engine of SAP XI 3.0 IS Runtime XI Message System Landscape Directory Components / Addresses Config. Cache OK / Error Engine in SAP J2EE Framework Integration Builder / Directory:... Receiver Determination Party->Service->Interface... Channel Definition: Engine Type Message Protocol Transport Protocol Security Channel Configuration Configuration Master Sender / Receiver Agreement: Party/Service/Interface <-> Channel Q Messaging Configuration Cache Monitoring Channel End-to-End Monitoring Message Flow over all XI Components/Applications Module Processor Tracing Logging Security Administration J C A - Specific Component Services Sender Receiver Runtime Workbench UIs for Administration, Monitoring B a c k e n d

7 The SAP Partner Connectivity Kit (PCK) For Business Partners without SAP XI, that need to communicate with SAP XI End-to-End Monitoring IS Runtime Integration Builder / Directory: Receiver Determination Conf. Cache Party->Service->Interface... Runtime Workbench UIs for Administration, Monitoring Configuration Master Firewall XI Message Conf UI System Landscape Dir. Components, Systems, Addresses PCK in SAP Engine J2EE in SAP J2EE Q Config. Master Channel Messaging Monitoring Module Processor Tracing Logging Security Administration Mon. UI Adm. UI Sender Recv. - Specific Component Services Framework B a c k e n d

8 SAP Partner Connectivity Kit Overview Supports Smaller Companies / Subsidiaries to exchange XML documents with their business partner s / headquarter s SAP XI Smaller Company / Subsidiary SAP / 3rd Party Appl. SAP PCK Internet Large Business Partner / Headquarter SAP XI SAP Application 3rd Party Application Provides a Platform for Development of own JCA Resource s SAP PCK

9 J2EE Engine central or decentral? Use Central Engine if possible Use Central User- and Role Management (synchronized with ABAP-Stack of the Integration Server => UME with ABAP) Reasons for Decentral SAP J2EE-based AE: u Protocol of Sender-/Receiver system (e.g. ftp not allowed) u Driver OS - dependent u Sender-System has to send independent from IS u Performance u Organizational Aspects

10 SAP XI-s vs. SAP XI-Proxies s Connect existing (legacy) systems to XI Specific wire protocol Interface semantics externally pre-defined Outside-in development approach Proxies Connect new SAP applications to XI Native connectivity to Application system (adapter-less) Interfaces designed centrally in Integration Repository Inside-out development approach

11 Framework Overview Engine Openness and Extensibility

12 SAP XI 3.0 s Logical View Integration Repository / Integration Directory / System Landscape Directory Integration Server Business Process Engine Integration Engine J2SE Engine http/idoc Central Engine Framework Messaging Queuing Security Handling Resource Optional local Engine FW Messaging Queuing Security Handling Resource Partner Connectivity Kit PCK Configuration and Monitoring FW Messaging Queuing Security Handling Resource File DB JMS SAP & Non- System SAP System 3rd Party Appl. File/DB/JMS Marketplaces SAP System 3rd Party Appl. File/DB/JMS Marketplaces SAP System 3rd Party Appl. File/DB/JMS Marketplaces

13 Categories Application s Siebel, Oracle, PeopleSoft applications Technical s File Systems (File/FTP) RDBMS systems (JDBC) Messaging systems (JMS) Web Services (SOAP) Mail Servers (SMTP) SAP Business Connector (SAPBC) Marketplaces Industry Standard s RosettaNet CIDX Engine SAP System 3rd Party Appl. File/DB/JMS Marketplaces

14 Technical s Provided with initial shipment by SAP ( Engine and SAP Partner Connectivity Kit) Engine (central and decentral): File, JMS, JDBC, SOAP, RFC, Mail, Business Connector, MarketPlace SAP Partner Connectivity Kit: File, JMS, JDBC, SOAP, RFC, Mail, Business Connector Technical s in ABAP-Stack: IDoc-, http- Additionally: Application specific s, Industry Speak, B2B

15 Role of adapters in SAP Busines Packages Standard scenarios Application standard Business Document Schema Integration Repository Business Scenarios Business Processes Mappings Message Interfaces Integration Directory Routing Rules Collaboration Agreements Collaboration Profiles Business Partner SAP Industry Solution (e.g. High Tech) Integration Server Business Process Engine IDoc/ Proxy Integration Engine 3rd Party Application Resource Engine Messaging Queuing Security Handling Industry Standard to Business Partner

16 Central Configuration Integration Directory Selection of Type specific Settings

17 Central Monitoring from RWB

18 The Framework Monitor Single point of entry for error analysis (instead logviewer etc.) Monitor only (no start/stop, control) Information per communication channel J2EE-User needs monitoring rights/permissions Part of RWB Component Monitoring for Framework (Link on start page for PCK Monitoring)

19 Send a Test Message from RWB In Component Monitoring of RWB select All => Display Tree Select Integration Server Integration Engine Choose Test Message

20 Archiving In Component Monitoring of RWB select All => Display Tree Select Integration Server => Engine Choose Message Archiving

21 AE with J2EE Cluster Assumption: Several server-instances, i.e. several server (processes)/vm One Engine in SLD and Directory Port in SLD points to the central J2EE-dispatcher Load Balancing Is done via central J2EE-mechanisms, i.e. not specific to AF CPA-Cache: AF handles consistent content distribution after a refresh to the individual server cache nodes Services: Running on all individual server processes/instances (CPA, Messaging System, s) EOIO-Handling: EOIO-messages are distributed among the nodes/instances. A Sequence-ID and the receiving node per message is stored in the messaging system. A redistribution to different nodes for handling does not take place, i.e. always the node which receives the message has to handle/process it further. Exception: if a node is down an event is triggered to the messaging system and then the messages is scheduled for process on another node by the messaging system.

22 Framework Overview Engine Openness and Extensibility

23 Development Kit and Module Processor Development Kit for development of additional adapters (partner and customer solutions) based on SAP J2EE und JCA Any additional Engine not imperative SAP NetWeaver Certification of Third-Party s Modulprocessor as extension concept (corresponds to dispatcher functionality within the J2SE-AE of SAP XI); Default- Modules per

24 Module Processor Concept For every adapter it is possible to define generic modules in the module processor: possibility to extend the functionality of the specific adapter Equivalent to the dispatcher classes in the J2SE adapter engine; migration and examples The default module configuration for the certain adapter is displayed in the channel configuration Module configuration is defined as message-protocol and adapter type specific Stateless Sequence matters! Modules are EJB s

25 Module Processor Example

26 Metadata in Repository XML file defines all configuration parameters for each adapter type Uploaded into SAP XI Integration Repository or SAP PCK Configuration parameters rendered into graphical configuration front-end Channel Templates Objects

27 Integration and Certification Center New ICC portal for one-stop-shopping ICC Palo Alto, California US Phone SDN iview Screenshot Get started

28 Summary The Framework provides uniform SAP J2EEbased services for technical, application- specific and B2B-s of the Engine or/and SAP PCK Decentral installed adapters can be configured, administered and monitored centrally Open standards and an extension concept serve as the foundation for a multitude of partner and customer solutions, by making full use of the services provided by the Framework

29 Further Information Ł Public Web: SAP Developer Network: Ł Exchange Infrastructure SAP Customer Services Network: Ł Related SAP Education Training Opportunities

30 Questions? Q&A

31 Copyright 2004 SAP AG. All Rights Reserved No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iseries, pseries, xseries, zseries, z/os, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mysap, mysap.com, xapps, xapp, SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.