1 / 41

The Dawning of Enterprise Service Architecture

The Dawning of Enterprise Service Architecture. Hype or Vision? By Axel Angeli (Germany) and Lynton Grice (South Africa) Blue Elephant League http://logosworld.com. 42 (Source: Douglas Adams, The Hitchhiker‘s Guide to Galaxy). The Answer. ESA and 42. ESA is the answer that SAP gave us

latimer
Download Presentation

The Dawning of Enterprise Service Architecture

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Dawning of Enterprise Service Architecture Hype or Vision?By Axel Angeli (Germany) and Lynton Grice (South Africa)Blue Elephant Leaguehttp://logosworld.com

  2. 42 (Source: Douglas Adams, The Hitchhiker‘s Guide to Galaxy) The Answer ....

  3. ESA and 42 • ESA is the answer that SAP gave us • But what .... • What did we actually ask for? • (Who needs ESA anyway?)

  4. The Future of IT is • The Service Oriented Enterprise

  5. Many Names for ESA • ESA – Enterprise Service Architecture (SAP) • SOA – Service Oriented Architecture • EDA – Event Driven Architecture • MBA – Message Based Architecture • Hologramming – Holistice Programming

  6. Service Oriented Enterprise • It will completely change • the way how you do business! Why? Why? Why?

  7. Why the SOE Will Change Everything • It will bring ... • The real-time enterprise • Modularization of IT processes! • Above all: a common language to describe business • Enforce collaboration! Isn‘t collaboration what we all want?

  8. Do we need ESA? • Yes! • ESA will bring to ERP the degree of inter-operability that we are used from Office applications • .... Finally, after 10 years

  9. Is ESA a Hype, Myth or Vision • ESA is a vision • When you strip the mystical elements from the hype • ESA will allow the degree of EAI that is already overdue • Highly specialized business will benefit most • From collaboration SAP and non-SAP tech • SAP ESA will be front-runner as ESB framework • Outperforming many others .... • Why? Due to the unique ABAP runtime!

  10. Benefits of ESA and ESB • Reduces complexity • Easier maintenance • Choice from Best of Breed • No need for complete suites! Cool! Let‘s throw out old IT and run ESA? Indeed! IT hadn‘t had much fun recently...

  11. Wait:Evolution Not Revolution Builds for Generations! • Transformation step-by-step How? • ESB replaces interfaces • Applications will eventually be rewritten as web services

  12. Where Is Netweaver?

  13. Here is Netweaver: Just Departed! • In Boston, Massachusetts • Kagermann commited to ESA • Boston, Lincolnshire • „The Original Boston“ • This is where Netweaver still is! • Ergo: • A long, long way to sail!

  14. The ESA Ingredients

  15. That is how marketing sees it ... Modern Integration Stack • People Integration • Portals, collaboration tools • Information Integration • Business intelligence, Business Activity Monitoring, Warehouse, SEM, LIS • Process Integration • Workflow • Integrated Application Runtime • Virtual machines

  16. As it looks from the machine room... The Ingredients of ESA • Powerful Business Applications • The goal of all these activities • They fill a portal with life! • Object Database • Real time data discovery and consolidation • Immediate spidering of data and many-to-many relationships • Message Queues and Message Consolidators • A prerequisite for distributed computing • The public space of cooperation and communications • Virtual Machine • Allowing managed processes • The power horses and engines of the corporate IT

  17. ESA is still at its Beginnings As transformation will make progress • New aspects will be added to ESA • Big ERP suites will become more and more modularized • ESA will become the heart beat of ERP • B2B business will rely on it shortly

  18. What happens to a company without ESA? • It will suffer a darvinistic destiny!

  19. Inside ESA: From Business To Service... All aboard! The bus is leaving... - Adapted from “Re-Imagine” by Tom Peters

  20. The Enterprise Service Bus (ESB) • The world spanning highway of communication

  21. ESB is the Highway of IT Communication • All communication is routed passively through ESB • Subscribers can act as listeners and/or collectors • ESB extends seemlessly into WWW

  22. Enterprise Service Bus Component Hive • All components are pluggable • Every component replacable • Special Application Services • Process Automation • Application Adapters • App Data Consolidation • Business App Monitoring • Traffic Monitoring cockpit • Special message Services • Web Services • Protocol conversion • Message Consolidation • Message Routing • Message Services

  23. How Communication Looks Like on ESB

  24. Can ESA Really Work? • It works like public traffic works • Individual responsibility • Minimal standards • Very few rules • More rules may be counter productive

  25. ESA allows safe transformation • First the ESB framework will be installed • No impact on current installations • Legacy apps will be wrapped for ESA • Only dirty architrecture needs revamping • Legacy apps will deliver results to the ESB • Results can be viewed by other apps • No „hard“ dependencies will be set • New applications will add as they appear • And eventually replace old applications with components

  26. Project Management Needs to Change! ... the human side • A Most Crucial Area • Project managers need to change their thinking • End of waterfall strategies • Waterfall will end up in disaster • Just like police wanted to control movement of every car • Chaotical methods necessary („Chaos“ ≠ „Anarchy“  ) • Also known as: Agile, Extreme, Hologramming, SCRUM • Don‘t believe in pure virtual worlds • You need to sit face to face!!!

  27. Outlook: The New Netweaver • SAP will soon be the leader in the SOA market • How an ugly duckling becomes a handsome swan!

  28. The Layers of the Netweaver 04 • WebAS Application Server • Classic ABAP engine plus Java Personality • Application Integration Framework • That is XI • People Integration Components • Mainly Enterprise Portal • Business Applications • E.g. mySAP ERP (R/3), BW and CRM

  29. The New Netweaver

  30. Netweaver ESA • Netweaver AS Application Server • implements an Enterprise Service Bus • Monitored Execution Runtime „Virtual Machine“ based on ABAP Engine • With integrated MQ services • Java personality: minor importance • An abundance of event driven components • Business Service Directory • Front-end technology • Portal, WebDynpro, more 3rd party

  31. The Elements of ESB

  32. ESB Compliance of ESA • Netweaver AS Application Server • Monitored process execution runtime • Powerful Message Queue Engine • integrated MQ services in the core • Business Service Directory • A habitat for plugable components • Universal Adapter Framework • Prerequisites for disparate computing

  33. Exchange Infrastructure • Will be part of the core • Will disappear as stand-alone product • One can also say • XI will be ESA • ESA will be XI

  34. Importance of MQ Services • Component based software needs asynchronous execution service • Many scattered MQ technology in ABAP now: • IDocs, NAST messaging, Workflow, batch service • None of them are universal • Asynchronous processes • need orchestration • implement many typical Patterns • Power of ESA depends on Power of MQ

  35. BSR: Business Service Repository • A central storage for interface descriptions • Similar to UDDI but incompatible • Based on WSDL with additional information • All applications register with BSR • A ancestor exists at ifr.sap.com • Lists all BAPIs, IDocs, and many RFC • But IFR is global, not dynamic

  36. BSR: Business Service Repository • A central storage for interface descriptions • Similar to UDDI but incompatible • Based on WSDL with additional information • All applications register with BSR • A ancestor exists at ifr.sap.com • Lists all BAPIs, IDocs, and many RFC • But IFR is global, not dynamic

  37. What Is the Value of the BSR? • Software will be delivered in components • Components will have a common interface standard, a touch of COM or CORBA • Components will be pluggable • SAP and non-SAP applications will co-exists with equal rights • As we are used from Windows etc. • BSR => Netweaver as Operating Framework

  38. What Happens to Old Applications • They become „wrapped components“ • Automatically transferred • BAPI compliant apps • IDoc interfaces • Only works when BAPIs implement full functionality • Many BAPIs still only call online transactions!

  39. Blue Elephant League Says Thank You! • Email us at westin@logosworld.de for the whitepapers for the presentation by SAPTIPS.COM. Blue Elephant Lynton Grice Axel Angeli www.logosworld.com • blue.elephant@logosworld.com

  40. The Blue Elephant Stampede • Networking computers means networking people! • Blue Elephants are individual researchers or a small enterprise • Blue Elephants League is their network • Blue Elephants Know That the World is a Village • Blue Elephants evangelize the vision of collaboration of computer software across organisations • Blue Elephants Mentor EAI Projects • Blue Elephants Give Independent Expertize • Contact: blueelephants@logosworld.com

  41. You Are Not Alone on Your Journey!

More Related