Scott Lowden SAP America Technical Solution Architect

Size: px

Start display at page:

Download "Scott Lowden SAP America Technical Solution Architect"

Nickolas Rice
6 years ago
Views:

1 SAP NetWeaver Training Overview - SAP Exchange Infrastructure Scott Lowden SAP America Technical Solution Architect

2 NetWeaver Components Detail Exchange Infrastructure SAP AG 2003, Title of Presentation, Speaker Name / 2

3 Today s Integration Challenge Call Center Document Mgmt Market Analysis Integration costs are high Lots of heterogeneous systems Long integration projects SCM IT environments become increasingly rigid Pressure on IT increases ERP Must leverage existing investments Must show quick results Trading e-sales Must reduce total cost of ownership (TCO) Technical systems PLM E-Procurement SAP AG 2003, Title of Presentation, Speaker Name / 3

4 How to Lower TCO Call Center Document Mgmt Market Analysis Reduce complexity Minimize the number of connections - using hubs SCM Use only 1 platform to integrate all people, information, and systems ERP Reduce custom integration Deliver.NET and J2EE interoperability Trading e-sales Deliver adaptors for ISV products Deliver products, not projects! Technical systems PLM E-Procurement Increase company performance Increase ease of use, scalability and adaptability Increase business process flexibility by using an Enterprise Services Architecture SAP AG 2003, Title of Presentation, Speaker Name / 4

5 Enterprise Services Architecture (ESA) Make Web Services work for your business Objective Add new levels of flexibility while leveraging existing investments ESA is the blueprint for complete and services-based business solutions Empowers all participating people (internal and external, all relevant roles) Manages all information (structured and unstructured) Encompasses all systems (SAP and non-sap) SAP delivers its business solutions using an Enterprise Services Architecture SAP NetWeaver implements an ESA SAP xapps, mysap Business Suite, custom solutions are powered by SAP NetWeaver Open, Web Services Environment Snap on business process People Integration Information Integration Process Integration Enterpr. Services Existing Systems SAP AG 2003, Title of Presentation, Speaker Name / 5

6 SAP Solutions Powered by SAP NetWeaver Open integration on all levels for the mysap Business Suite SAP NetWeaver SAP R/3 Enterprise mysap SRM mysap SCM People Integration Multi-Channel Access Portal Collaboration Strategic Sourcing Information Integration Knowledge Mgmt Business Intelligence Master Data Mgmt Process Integration Integration Broker, Business Process Mgmt Application Platform Supplier Evaluation Demand/ Source of Supply J2EE ABAP, DB and OS Abstraction R/3 SRM Backbone SCM Backbone 3 rd party Solution SAP AG 2003, Title of Presentation, Speaker Name / 6

7 SAP Solutions Powered by SAP NetWeaver Orchestrating new, cross-functional business processes SAP NetWeaver People Integration Multi-Channel Access Portal Collaboration SAP xapps SAP xapp Resource and Program Mgmt Information Integration Knowledge Mgmt Business Intelligence Master Data Mgmt Project Portfolio Mgmt Project Execution Staffing Resource Assignmt Advanced Skills Mgmt Process Integration Integration Broker, Business Process Mgmt Application Platform J2EE ABAP, DB and OS Abstraction PLM 3 rd party HR Project System Microsoft Office 3 rd party FI SAP AG 2003, Title of Presentation, Speaker Name / 7

8 The Solution Key Design Elements Web services Application functions become Web services Self-contained, modularized functionality that can be described, published, discovered, and accessed through open internet standards In addition, all kinds of services that are relevant for classical EAI and remote communication (via adapters) Open syndication of Web services Regardless of location Web-centric Architecture XML and message based infrastructure for open collaboration supporting open standards and leveraging Java, ABAP and.net Central Integration Repository and Directory capturing shared Collaboration knowledge Open for mysap.com e-business solutions and 3 rd party components All customer touchpoints based on open XML and Java technology SAP AG 2003, Title of Presentation, Speaker Name / 8

9 The Solution Shared Business Semantics Shared Integration Knowledge Business scenarios, business processes, Web services, interfaces, mappings, routing rules,... For a common understanding of 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 2003, Title of Presentation, Speaker Name / 9

10 Overview Exchange Infrastructure 2.0 Shared Collaboration Knowledge Execute Collaborative Business Processes Design Configuration Runtime 3 rd Party and Messaging Systems SAP Systems Integration Server Integration Repository Integration Directory Integration Engine Business Process Engine Additional Integration Services Marketplaces SOAP Plain HTTP System Landscape Directory Runtime Workbench Partner Eco-System (additional 3rd Party Adapters and Industry Standards) SAP AG 2003, Title of Presentation, Speaker Name / 10

11 Integration Repository Integration Content provided at Design Time Already contains Integration knowledge for mysap solutions Open for Partner and Customer to add collaboration knowledge of non-sap systems Content can be filled from different sources using open standard descriptions (e.g. WSDL) XML and Java based tools Business Scenarios Business Processes Mapping Objects Interface Objects Imported Objects Components (SLD) Integration Repository SAP AG 2003, Title of Presentation, Speaker Name / 11

Integration Repository Business Scenarios Business scenarios Provide overview of business semantics of an integration scenario Show involved communication partners and their roles Outline

12 Integration Repository Business Scenarios Business scenarios Provide overview of business semantics of an integration scenario Show involved communication partners and their roles Outline choreography of message exchange Provide central access to all involved design time objects (like interfaces, mappings) Provide input for configuration Support top-down and bottom-up modeling SAP standard business scenario Supplier Managed Inventory SAP AG 2003, Title of Presentation, Speaker Name / 12

Integration Repository - Interfaces Central place to define and catalog global and component-specific interfaces Interfaces assigned to components Tracks different interface versions Descriptions of

13 Integration Repository - Interfaces Central place to define and catalog global and component-specific interfaces Interfaces assigned to components Tracks different interface versions Descriptions of all existing BAPI, IDOCs and RFCs Global interfaces and types populate Includes message types and data types for high reusability Based on WSDL (Web Service Description Language, W3C) Outbound and inbound interfaces Synchronous and asynchronous interfaces XML Schema to describe data types Basis for Proxy generation populate Application developer designs a new interface SAP AG 2003, Title of Presentation, Speaker Name / 13

14 Proxy Generation Key Benefits Separation of Business Application from technical Exchange Infrastructure Platform and programming language independent principles Generation of proxies in Java, ABAP and.net platform Using interface description (WSDL) of Interfaces in the Integration Repository Design time activity Proxy connects to (local) Integration Engine Executes shared integration knowledge (Integration Directory) Proxy Integration Engine Business Function Application System SAP AG 2003, Title of Presentation, Speaker Name / 14

Integration Repository - Mappings Contains preconfigured information for Structural transformation Value mapping Interface Mappings register mappings for interface pairs Message Mappings are used to

15 Integration Repository - Mappings Contains preconfigured information for Structural transformation Value mapping Interface Mappings register mappings for interface pairs Message Mappings are used to implement mappings Message Mapping definition in the Integration Repository Graphical Mapping Editor Import schema (XSD, XML) Import IR message types Import archives (zip or jar) Import RFC, IDoc Write own Java functions Mappings are stored in the Integration Repository, selected for business processes in Configuration Time, executed by the Integration Engine at runtime SAP AG 2003, Title of Presentation, Speaker Name / 15

16 Integration Directory Integration Content provided at Configuration Time Contains productive integration knowledge at customer site Can be derived from Integration Repository during installation and configuration Open for Customer to add collaboration knowledge relevant to non-sap components XML and Java based tools Business Scenarios Business Processes Receiver Determinations Interface Determinations Web Services System Landscape (SLD) Business Partners Integration Directory SAP AG 2003, Title of Presentation, Speaker Name / 16

resolution from the Integration Directory SAP 4.

17 Message Flow within the Integration Server SAP 3.x The Integration Server retrieves required Collaboration Knowledge on Routing, Mapping and Address resolution from the Integration Directory SAP 4.x Third Party System SAP Adapter Logical Routing 3rd Party Adapter Mapping Technical Routing mysap.com Solution* Marketplace Firewall Business Partner Business Partner Business Partner SAP AG 2003, Title of Presentation, Speaker Name / 17

18 Features of the Integration Engine Different quality of service for message delivery or Web service invocation Synchronous: always best effort Asynchronous: exactly-once exactly-once-in-order support of acknowledgement Different messaging models Request/Response Publish/Subscribe Error handling Return or storage of fault messages Automatic retry Monitoring Configurable monitoring and tracing of all messages Application related monitoring functionality Deployment as local Integration Engine or stand alone Integration Server SAP AG 2003, Title of Presentation, Speaker Name / 18

19 Adapters Overview Connection to existing SAP systems RFC adapter IDoc adapter Connection to 3 rd party and messaging systems File adapter Database (JDBC) adapter Java Messaging Service (JMS) adapter SOAP adapter Plain HTTP adapter Connection to marketplaces MarketSet adapter Adapter framework for selected partners Adapters provided by partners For application systems like Siebel, JDE, Oracle, For industry standard protocols like RosettaNet, CIDX, SAP AG 2003, Title of Presentation, Speaker Name / 19 Runtime Integration Server Integration Repository 3 rd Party and Messaging Systems SAP Systems Marketplaces SOAP Plain HTTP Adapter Framework - Partner Content (additional 3rd Party Adapters and Industry Standards)

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

20 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 Integration Engine SAP AG 2003, Title of Presentation, Speaker Name / 20

21 Copyright 2003 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, NT, EXCEL, Word, PowerPoint and SQL Server 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, Informix and Informix Dynamic ServerTM are trademarks of IBM Corporation in USA 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, the Citrix logo, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, MultiWin and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc. HTML, DHTML, XML, XHTML 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. MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One. SAP, SAP Logo, R/2, R/3, mysap, mysap.com 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 trademarks of their respective companies. SAP AG 2003, Title of Presentation, Speaker Name / 21

Interaction Center for Automotive

Interaction Center for Automotive Release 2005 ADDON.SECGUIDE_AUM Copyright Copyright 2004 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any