Information Technology professionals can use this book to move beyond the excitement of web services and service oriented architecture (SOA) and begin the process of finding actionable ideas to innovate and create business value. In Enterprise SOA: Designing IT for Business Innovation, SAP's blueprint for putting SOA to work is analyzed from top to bottom. In addition to design, development, and architecture, vital contextual issues such as governance, security, change management, and culture are also explored. This comprehensive perspective reduces risk as IT departments implement ESA, a sound, flexible architecture for adapting business processes in response to changing market conditions.
This book answers the following questions:
What forces created the need for Enterprise Services Architecture?
How does ESA enable business process innovation?
How is model-driven development used at all levels of design, configuration, and deployment?
How do all the layers of technology that support ESA work together?
How will composite applications extend business process automation?
How does ESA create new models for IT governance?
How can companies manage disruptive change?
How can enterprise services be discovered and designed?
How will the process of adapting applications be simplified?
Based on extensive research with experts from the German software company SAP, this definitive book is ideal for architects, developers, and other IT professionals who want to understand the technology and business relevance of ESA in a detailed way--especially those who want to move on the technology now, rather than in the next year or two.
THE CONTEXT FOR ESA
Chapter ONE ESA in the World of Information Technology
Who is this book for?
Why so many questions?
What forces created ESA?
What is ESA?
How will ESA change how applications are designed and built?
What supporting infrastructure does ESA require?
Is ESA compatible with event-driven architecture?
What is the promise of ESA?
How will the transition to ESA occur?
How can ESA be addressed at a tactical level?
Why does ESA matter?
What are the core values of ESA?
Where can we go for more answers?
ESA in action: Mitsui
Chapter TWO The Business Case for ESA
What attributes must ESA embody?
What principles should be driving my IT decisions?
What happens when core eventually becomes context?
How does ESA enable consolidation and reuse?
What kind of innovation should companies pursue, and how will ESA help them?
What are ESA's practical implementation issues?
What's the long-term adoption path of ESA? How quickly will I see ROI, and what form will it take?
What is ESA's long-range impact on corporations?
ESA in action: Nordzucker AG
Chapter THREE Evolving Toward ESA
Just how much and what kind of change will ESA involve?
What is IT's role within ESA?
What do you mean by "business process?"
That's a good point, but how do you bring the two sides together in the first place?
What is IT's role if all of this comes to pass? What does my company look like then?
What stages will we go through on the way there? What skills will we have to develop?
What kind of architecture skills does ESA call for?
How does a cultural transformation happen in the real world? What can SupplyOn tell us about how to manage the change inherent in ESA?
How will IT change in an ESA world?
What will the shift to a model-driven world mean for IT, and where will these business analysts come from?
How will governance function within ESA?
How and where should I begin evolving toward ESA?
How will modeling translate between enterprises with different architectures? Will a standards body evolve to resolve potential conflicts?
What do the analysts think, and what trouble do they foresee?
What kind of company will we be after ESA?
CONCEIVING A VISION FOR ESA
Chapter FOUR ESA Fundamentals: Learning to Think ESA
What is architecture and why is it important?
What is enterprise architecture and how will ESA change it?
What motivated the creation of ESA?
What are the architectural challenges of ESA?
How does ESA meet those challenges?
Does ESA make all my existing systems worthless?
What are systems of record?
What are transactional systems?
What are web services?
What is the difference between a web service and an enterprise service?
What is service-oriented architecture?
What is the difference between ESA and other approaches to SOA?
What are composite applications?
What are service consumers?
What are service providers?
What are xApps?
What role does the mySAP Business Suite play in ESA?
What role does SAP NetWeaver play in ESA?
What are IT practices and IT scenarios?
What is event-driven architecture?
Why are analytics so important to ESA?
How does ESA provide for easier adaptation and a better requirements fit?
What is the basic structure of an enterprise service?
What are global data types?
Why is XML messaging so important to ESA?
What is the difference between a frontend and a backend application?
What is service composition?
What is the role of business objects in ESA?
How does persistence change in ESA?
Why does modeling matter? Isn't it just another form of coding?
Will modeling replace coding?
How are patterns used in ESA and what value do they provide?
What is process orchestration?
What is process integration?
How will ESA change the way applications are packaged and delivered?
What are the special needs of composite applications?
What is the relationship between ESA, standards, and commoditization?
Is buy versus build a false tradeoff in ESA?
Why is an ecosystem of companies and standards so important to ESA?
Chapter FIVE The Structure of ESA
Basics of ESA applications
The ESA stack, layer by layer
The enterprise services layer
The business objects layer
The process orchestration layer
The UI layer
The persistence layer
Chapter SIX The Enterprise Services Community
What is the ES-Community?
What is the value of the ES-Community?
What is a Definition Group? Who can join?
What does the ES-Community contribute?
Will the ES-Community create new standards?
How are enterprise service definitions created within the ES-Community?
What is the organizational structure of a Definition Group?
What is certification? Is it mandatory?
What is ES-Ready? How can partners use this brand?
How does the ES-Community balance efficiency with open participation?
What is required to participate in the ES-Community?
How is intellectual property (IP) treated in the ES-Community?
How will the ES-Community differ from SAP's other partner and customer efforts?
How does participation in the ES-Community benefit customers?
What should a company do to get involved in the community process?
Chapter SEVEN Creating a Roadmap with the ESA Adoption Program
Why the roadmap approach?
What challenges do companies face in adopting ESA?
How does SAP help customers adopt ESA?
Is there more to success with ESA than just analyzing technologies and preparing roadmaps?
How have companies put SAP's ESA Adoption Program to work?
Chapter EIGHT The Enterprise Services Repository and the Enterprise Services Inventory
What is the Enterprise Services Repository?
What is the Enterprise Services Inventory?
ESA in action: Elsag
ESA in action: Kimberly-Clark
ESA in action: CSA International
Chapter NINE Project Mendocino: A Product Based on Consuming Enterprise Services
What is the goal of Project Mendocino?
How does Project Mendocino use ESA?
Project Mendocino applications
The Project Mendocino architecture
ESA in action: Agile Solutions Ltda
Chapter TEN ESA at Work: Examples from the Field
ESA in consumer products
ESA inCustomer Relationship Management (CRM)ESA in CRM:ESACRM service request processing
ESA in the chemical industry: e-VMI at Solvay
ESA for logistic service providers
ESA for professional service providers
ESA in manufacturing
ESA in the chemicals industry
Chapter ELEVEN SAP xApps Composite Applications for Analytics
How do SAP xApp Analytics help business users?
How hard is it to deploy SAP xApp Analytics?
What are the different parts of an analytic composite application?
In which application and process areas are analytic composites being created?
How do ESA and SAP NetWeaver help create analytic composites?
What are the benefits of SAP analytics?
Chapter TWELVE The Architecture and Development Tools of Composite Applications
Dan Woods, a seasoned CTO, has built technology for companies ranging from Time Inc. New Media to TheStreet.com. He has managed the product development cycle from initial requirements through sales for web sites and software products designed for the publishing and financial services industries. Dan has also navigated all phases of the business cycle: crafting strategy and budgets, building and managing large development teams, writing patent applications, negotiating large vendor agreements, operating data centers, communicating with board members, raising money, and selling and marketing a product. Dan is the author of two books and a frequent contributor to InfoWorld and other publications.
Thomas Mattern, Solution Marketing Manager for Enterprise Services Architecture at SAP, has over 10 years experience in product marketing and management with a focus on distributed software architectures and enterprise application development. Thomas is a frequent speaker who has written numerous articles about the application of technology to business.
This book should be of special interest to SAP users, including developers, architects, business analysts, CEOs, and CIOs. It outlines SAPs roadmap for the future of SOA (Service Oriented Architecture). This is built around ESA (Enterprise Services Architecture), which is SAPs proposed means for building and linking services in a way that promotes maintainability and reuse. It relies heavily on model-driven development
(modeling is the "organizing principle" of ESA).
The authors include fairly extensive discussions of SAPs plans for the future. For
this reason, a better title might be _Enterprise SOA from SAPs Point of View_. However, the strategy outlined, and examples given, should also interest those not using SAP, in that it presents persuasive arguments for an architecture that could be used by organizations faced with extensive complexities in business operations and
therefore, supporting business software. It also brings out issues that such organizations will have to face, such as creating services that are maintainable and reusable. As the authors point out, flexibility in both business operations and
software will be especially necessary to be agile and adaptable in the future--in many
cases, multi-year projects are no longer practical.
Some readers might find the organization of the book a little frustrating if they try to read it from beginning to end without first skimming it, but it is a complex subject, and different ways of organizing the discussion will appeal to different
readers. One nice feature is a brief, high-level introduction to the basics of web services in an FAQ format (pp. 99ff.; pp 321 ff.). The latter reference includes a brief explanation of XML, schemas, and namespaces. Another nice feature is the examples (pp. 184ff., pp228ff., pp372ff., etc.).
A glossary of SAP terms and acronyms might enhance the appeal of the book to non-SAP users, although use of sites such as Google lessens this need somewhat.