Вы находитесь на странице: 1из 8

Enterprise SOA an Introduction from a Technology Point of View

Applies to:
Enterprise SOA, SAP NetWeaver CE 7.1 and PI 7.1

Summary
This article gives a brief introduction to the key differentiating elements of enterprise SOA in relation to SAPs technology platform SAP NetWeaver. Authors: Volker Haentjes, Hans-Joachim Odlozinski, Volker Stiehl

Company: SAP AG Created on: 13 March 2008

Author Bio
Hans-Joachim Odlozinski is a solution architect in the Co-Innovation Engineering team in the Global Ecosystem and Partners group of SAP AG. He looks back on many years of development and consulting both internally at SAP as well as for customers & partners in the field.

Volker Haentjes is director of partner and customer engagement in Enterprise SOA Delivery Program for the SAP Business Suite in the Verticals and Composites development group of SAP AG in Walldorf. He is responsible for partner and customer communication and education and several other program management activities. Volker has worked for SAP since 1993.

Volker Stiehl is on the product management team for SAP NetWeaver Composition Environment. He is also responsible for methodologies and best practices in composite application development. Before joining SAP, he spent several years as a consultant for distributed J2EE-based business solutions and integration architectures based on various technologies.

SAP DEVELOPER NETWORK | sdn.sap.com 2008 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 1

Enterprise SOA an Introduction from a Technology Point of View

Table of Contents
The Key Elements Differentiating Enterprise SOA from SOA ............................................................................3 The Architectural Building Blocks For Enterprise SOA ......................................................................................5 Related Content..................................................................................................................................................7 Copyright.............................................................................................................................................................8

SAP DEVELOPER NETWORK | sdn.sap.com 2008 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 2

Enterprise SOA an Introduction from a Technology Point of View

The Key Elements Differentiating Enterprise SOA from SOA


As its name suggests, enterprise service-oriented architecture (enterprise SOA) aims at leveraging the established aspects of SOA like its strong link to established standards for the enterprise as a whole. It does not remain in the technology domain but takes SOA to the core of your business. It aims at connecting the business domain with the technology domain in a holistic and consistent manner.

At the heart of enterprise SOA lays the concept of enterprise services. Enterprise services allow you to leverage SAP solutions in conjunction with partner solutions and your home-grown solution landscape to build new, flexible, and innovative solutions based on the consistent integration concept of enterprise SOA. In a nutshell, enterprise services are highly-integrated Web services combined with business logic and semantics that can be accessed and used repeatedly to support your business processes. The following characteristics differentiate enterprise services from regular web services: Business semantics: Enterprise services are structured according to a harmonized enterprise model based on well-defined business objects, process components, and global data types (GDTs). They are defined using an outside-in approach: common business rules and know-how, rather than SAPspecific implementations, are the guideline for defining the business content of SAP applications. The advantage of this is quite clear when you go down to the technical implementation level: Arranging enterprise services in newly developed business processes is simplified as the formats of the participating data structures are harmonized. Quality and stability: Enterprise services safeguard a stable interface for future versions (backward compatibility). Their behaviors, prerequisites, dependencies of usage and configuration possibilities are well documented. Standards: Enterprise services are based on open standards. The interfaces are described according to WSDL. They are created by using global data types which are based on UN/CEFACT

SAP DEVELOPER NETWORK | sdn.sap.com 2008 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 3

Enterprise SOA an Introduction from a Technology Point of View

CCTS (Core Component Technical Specification). B2B enterprise services are defined in compliance with e-business standards, where applicable. There are different application areas for enterprise services, for example application-to-application (A2A) and business-to-business (B2B) integration or user interfaces. By productizing this concept and offering a consistent set of enterprise services through the Enterprise Services Repository (ESR), enterprise SOA helps lowering the total cost of ownership (TCO). It clarifies and thereby simplifies the approach for connecting the business requirements with the underlying implementation. To simplify the process of adopting enterprise SOA and make it as easy as possible, SAP has enabled its SAP Business Suite by exposing its business functionality in the form of enterprise services as ready-toconsume process steps with built-in business semantics. These enterprise services are grouped along business scenarios as so-called enterprise services bundles, and are based on a sophisticated governance model, together with lifecycle management capabilities and an enhancement concept. Delivering applications and business processes on top of the SAP Business Suite is additionally simplified through business-oriented, catalog-like views of the SAP Business Suite services, the Enterprise Services Workplace (ES Workplace) and the Enterprise Services Wiki (ES Wiki), both available through the SAP Community Network (sdn.sap.com). The ES Wiki describes each of the enterprise services bundles and related business-use cases in great detail and shows how to put them to work. The ES Workplace represents SAPs public ESR, which provides detailed technical information on each enterprise service from both a business and technical perspective. Therefore, browsing the ES Workplace to identify available services required by your business scenario should be the first step on a successful path of implementing an enterprise SOA-based solution. Closing remaining functionality gaps that are not covered by the set of SAP Business Suite enterprise services is an intrinsic part of the overall methodology: Custom-built services and partner-built services complete the set of available business functionality in the framework of enterprise SOA. The second cornerstone to make enterprise SOA a reality is the delivery of the essential technology building blocks with SAPs technology platform NetWeaver . This will be explained in more detail in the following chapter.

SAP DEVELOPER NETWORK | sdn.sap.com 2008 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 4

Enterprise SOA an Introduction from a Technology Point of View

The Architectural Building Blocks for Enterprise SOA


SAP provides a comprehensive blueprint that delivers key building blocks of the enterprise serviceoriented architecture (enterprise SOA). The enterprise SOA blueprint below shows how these building blocks facilitate innovation, enable business network transformation, and achieve operational excellence in an cost efficient way. Any given enterprise-level scenario does not need to use all of the capabilities that reside in these building blocks; different scenarios will use different capabilities and the facilitating platform will enable the incremental adoption of more capabilities to ensure flexibility and innovation.

Building blocks are organized in the following SOA principles which define ground rules for SOA capabilities: User Interface: Provide a high performance and rich UI experience Enterprise SOA Consumption: Composition of service based applications by consuming business entities delivered through the platform. Business Process Composition & Management: Modeling, configuration, execution and monitoring of business processes UI Composition: Build, code, compose, and adapt UI interaction, logic, and bestpractice UI patterns Service & Event Composition: Composition and adaptation of services and events Information Composition: Collaborative composition (in business user runtime) of structured and unstructured information within a business context (aka situational composites)

SAP DEVELOPER NETWORK | sdn.sap.com 2008 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 5

Enterprise SOA an Introduction from a Technology Point of View

SOA Middleware: Communication and service management layer to ensure optimized interoperability between consumption, provisioning and external entities. Service Bus: Allows efficient and scalable messaging, routing, mediation, federation, and event processing. Seamless integration with Enterprise Services Repository (ESR), Services Registry (SR), and SOA management capabilities SOA Design Governance: SOA metadata repository; design, configuration, and management of services prior to deployment; supported by the ESR SOA Management: Safe-guard deployment and operations of SOA applications. Runtime governance solutions and security; monitoring and measurement Enterprise SOA Provisioning: Provide services and events; manage connectivity integration to other platforms and external entities. Service & Event Enablement: Capabilities to create services and events; local event processing Connectivity & Integration: Enterprise application integration (EAI) and legacy connectivity capabilities; B2B integration with external business partners Service-enabled Applications: Service enablement of SAP applications and technology. Integration touch points with partners and legacy systems Process Components: Service enabled application functionality covering all main domains of enterprise applications (e.g. ERP, SCM, SRM, CRM) Platform Services: Service enabled integration platform capabilities (e.g. BI, MDM, KM) Customer & Partner Applications: Service enabled or integrated partner or customer applications Non SAP & Legacy: Available connectivity capabilities with non-SAP and legacy systems SAP NetWeaver delivers SAPs enterprise SOA technology foundation with two product shipments. While SAP NetWeaver Process Integration (PI) 7.1 provides enterprise SOA provisioning and SOA middleware capabilities, SAP NetWeaver Composition Environment (CE) 7.1 enables enterprise SOA consumption, development and composition of SOA applications. The implementation of a concrete business scenario might require the usage of both or just one of them: E.g. a portfolio of composite applications with lightweight point-to-point enterprise service integration would simply be implemented on SAP NetWeaver Composition Environment (CE) 7.1. A complex B2B data exchange scenario with complex interface mappings and routing rules instead would be implemented on SAP NetWeaver Process Integration (PI) 7.1. If you join these two scenarios and imagine a composite application scenario that essentially resides upon a complex B2B data exchange scenario you will reach the point where you will have to deploy both product shipments, CE and PI. Both product shipments contain the Enterprise Services Repository (ESR) which can be used as a common repository for enterprise SOA assets, namely the enterprise service definitions shipped with SAP Business Suite mentioned in the previous chapter.

SAP DEVELOPER NETWORK | sdn.sap.com 2008 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 6

Enterprise SOA an Introduction from a Technology Point of View

Related Content
SAP NetWeaver Application Development: SAP Application Categories overview (ABAP, Java, Composition)

Java development and composition: SAP NetWeaver Composition Environment 7.1 SAP NetWeaver Developers Guide 7.1

ABAP development SAP NetWeaver Process Integration: Introduction SAP NetWeaver SOA Middleware SAP NetWeaver Process Integration 7.1 Education

SAP DEVELOPER NETWORK | sdn.sap.com 2008 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 7

Enterprise SOA an Introduction from a Technology Point of View

Copyright
2008 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, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated 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. These materials are provided as is without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these materials. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third party web pages nor provide any warranty whatsoever relating to third party web pages. Any software coding and/or code lines/strings (Code) included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or grossly negligent.

SAP DEVELOPER NETWORK | sdn.sap.com 2008 SAP AG

BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com 8

Вам также может понравиться