Synopses & Reviews
Is there room for improvement in the way your network SOA enables applications to communicate and perform services for one another? Then you'll want to take a serious look at Enterprise Services Architecture (ESA), which is fast becoming the leading SOA technology. With ESA, monolithic enterprise applications are broken apart into layers and offered as components that make extensive use of web services. With these components, companies gain the flexibility to craft the optimal IT infrastructure, eliminating bottlenecks and reducing the cost of implementation.
Our new guide, Enterprise Services Architecture: Designing IT for Business Innovation, demonstrates how your enterprise can transform current solutions into technology that will better serve the needs of your customers. Commissioned by the German software development company SAP, this definitive book is ideal for architects, developers and other IT professionals who want to understand ESA in a detailed way-especially those of you who want to move on the technology now, rather than in the next year or two.
Each chapter in the book is organized as a set of theoretical and practical questions with answers and examples that offer a clear story. To partition ESA into digestible portions, the authors boiled everything down into five concepts:
Conceiving a Vision for ESA - This section delves deep into the technical aspects of ESA.
Consuming Services-Using services to solve IT problems within the organization: This business-focused material shows you how services can be consumed immediately to configure standard software to solve a much larger set of problems.
Composing with Services-Assembling newapplications and services from existing services: This section demonstrates how services can extend standard software by building on existing functionality as much as possible.
Creating Services-Creating new web services from scratch: How new services are created is described to provide technologists a deeper understanding of the tools and processes involved.
Controlling Services -discusses new forms of governance based on services as well as lifecycle management, operations, security, and standards.
ESA is already changing the way vendors build applications and the way companies use them. Enterprise Services Architecture: Designing IT for Business Innovation presents a forward-looking approach that you can use to meet future development challenges with ease and agility.
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.
About the Author
Dan Woods is a seasoned CTO, author, speaker, and entrepreneur with experience in business, computer science, journalism, and publishing. He is CTO and Editor of CITO Research, a firm dedicated to creating content to improve the performance of CIO and CTOs. As an author, Dan has written or coauthored more than 20 books about business and technology, ranging from books about service-oriented architecture, open source, manufacturing, RFID, and wikis to the ideas driving the latest generation of enterprise applications, particularly in the face of Web 2.0's impact on the enterprise. Dan has written hundreds of white papers and conducted more than 1,000 interviews with experts in a variety of fields. He is also an invited speaker and moderator at international conferences.
As a CTO, Dan 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 websites and software products designed for the publishing and financial services industries. At TheStreet.com, his systems supported the company's successful IPO and handled millions of daily page views while the number of subscribers tripled and new lines of business were launched. At CapitalThinking, Dan's software was purchased by the IT departments of large financial institutions including General Electric, JPMorgan Chase, and Citigroup.
Dan holds an M.S. from Columbia University's Graduate School of Journalism and a B.A. in Computer Science from the University of Michigan. Since July 2008, Dan has been writing a column for Forbes.com.
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.
Table of Contents
Foreword; Preface; Safari® Enabled; How can I comment on this book?; Acknowledgments; Part I: THE CONTEXT FOR ESA; Chapter ONE: ESA in the World of Information Technology; 1.1 Who is this book for?; 1.2 Why so many questions?; 1.3 What forces created ESA?; 1.4 What is ESA?; 1.5 How will ESA change how applications are designed and built?; 1.6 What supporting infrastructure does ESA require?; 1.7 Is ESA compatible with event-driven architecture?; 1.8 What is the promise of ESA?; 1.9 How will the transition to ESA occur?; 1.10 How can ESA be addressed at a tactical level?; 1.11 Why does ESA matter?; 1.12 What are the core values of ESA?; 1.13 Where can we go for more answers?; 1.14 ESA in action: Mitsui; Chapter TWO: The Business Case for ESA; 2.1 What attributes must ESA embody?; 2.2 What principles should be driving my IT decisions?; 2.3 What happens when core eventually becomes context?; 2.4 How does ESA enable consolidation and reuse?; 2.5 What kind of innovation should companies pursue, and how will ESA help them?; 2.6 What are ESA's practical implementation issues?; 2.7 What's the long-term adoption path of ESA? How quickly will I see ROI, and what form will it take?; 2.8 What is ESA's long-range impact on corporations?; 2.9 ESA in action: Nordzucker AG; Chapter THREE: Evolving Toward ESA; 3.1 Conceiving; 3.2 Consuming; 3.3 Composing; 3.4 Creating; 3.5 Controlling; 3.6 Just how much and what kind of change will ESA involve?; 3.7 What is IT's role within ESA?; 3.8 What do you mean by "business process?"; 3.9 That's a good point, but how do you bring the two sides together in the first place?; 3.10 What is IT's role if all of this comes to pass? What does my company look like then?; 3.11 What stages will we go through on the way there? What skills will we have to develop?; 3.12 What kind of architecture skills does ESA call for?; 3.13 How does a cultural transformation happen in the real world? What can SupplyOn tell us about how to manage the change inherent in ESA?; 3.14 How will IT change in an ESA world?; 3.15 What will the shift to a model-driven world mean for IT, and where will these business analysts come from?; 3.16 How will governance function within ESA?; 3.17 How and where should I begin evolving toward ESA?; 3.18 How will modeling translate between enterprises with different architectures? Will a standards body evolve to resolve potential conflicts?; 3.19 What do the analysts think, and what trouble do they foresee?; 3.20 What kind of company will we be after ESA?; Part II: CONCEIVING A VISION FOR ESA; Chapter FOUR: ESA Fundamentals: Learning to Think ESA; 4.1 What is architecture and why is it important?; 4.2 What is enterprise architecture and how will ESA change it?; 4.3 What motivated the creation of ESA?; 4.4 What are the architectural challenges of ESA?; 4.5 How does ESA meet those challenges?; 4.6 Does ESA make all my existing systems worthless?; 4.7 What are systems of record?; 4.8 What are transactional systems?; 4.9 What are web services?; 4.10 What is the difference between a web service and an enterprise service?; 4.11 What is service-oriented architecture?; 4.12 What is the difference between ESA and other approaches to SOA?; 4.13 What are composite applications?; 4.14 What are service consumers?; 4.15 What are service providers?; 4.16 What are xApps?; 4.17 What role does the mySAP Business Suite play in ESA?; 4.18 What role does SAP NetWeaver play in ESA?; 4.19 What are IT practices and IT scenarios?; 4.20 What is event-driven architecture?; 4.21 Why are analytics so important to ESA?; 4.22 How does ESA provide for easier adaptation and a better requirements fit?; 4.23 What is the basic structure of an enterprise service?; 4.24 What are global data types?; 4.25 Why is XML messaging so important to ESA?; 4.26 What is the difference between a frontend and a backend application?; 4.27 What is service composition?; 4.28 What is the role of business objects in ESA?; 4.29 How does persistence change in ESA?; 4.30 Why does modeling matter? Isn't it just another form of coding?; 4.31 Will modeling replace coding?; 4.32 How are patterns used in ESA and what value do they provide?; 4.33 What is process orchestration?; 4.34 What is process integration?; 4.35 How will ESA change the way applications are packaged and delivered?; 4.36 What are the special needs of composite applications?; 4.37 What is the relationship between ESA, standards, and commoditization?; 4.38 Is buy versus build a false tradeoff in ESA?; 4.39 Why is an ecosystem of companies and standards so important to ESA?; Chapter FIVE: The Structure of ESA; 5.1 Basics of ESA applications; 5.2 The ESA stack, layer by layer; 5.3 The enterprise services layer; 5.4 The business objects layer; 5.5 The process orchestration layer; 5.6 The UI layer; 5.7 The persistence layer; Chapter SIX: The Enterprise Services Community; 6.1 What is the ES-Community?; 6.2 What is the value of the ES-Community?; 6.3 What is a Definition Group? Who can join?; 6.4 What does the ES-Community contribute?; 6.5 Will the ES-Community create new standards?; 6.6 How are enterprise service definitions created within the ES-Community?; 6.7 What is the organizational structure of a Definition Group?; 6.8 What is certification? Is it mandatory?; 6.9 What is ES-Ready? How can partners use this brand?; 6.10 How does the ES-Community balance efficiency with open participation?; 6.11 What is required to participate in the ES-Community?; 6.12 How is intellectual property (IP) treated in the ES-Community?; 6.13 How will the ES-Community differ from SAP's other partner and customer efforts?; 6.14 How does participation in the ES-Community benefit customers?; 6.15 What should a company do to get involved in the community process?; Chapter SEVEN: Creating a Roadmap with the ESA Adoption Program; 7.1 Why the roadmap approach?; 7.2 What challenges do companies face in adopting ESA?; 7.3 How does SAP help customers adopt ESA?; 7.4 Is there more to success with ESA than just analyzing technologies and preparing roadmaps?; 7.5 How have companies put SAP's ESA Adoption Program to work?; Part III: CONSUMING SERVICES; Chapter EIGHT: The Enterprise Services Repository and the Enterprise Services Inventory; 8.1 What is the Enterprise Services Repository?; 8.2 What is the Enterprise Services Inventory?; 8.3 ESA in action: Elsag; 8.4 ESA in action: Kimberly-Clark; 8.5 ESA in action: CSA International; Chapter NINE: Project Mendocino: A Product Based on Consuming Enterprise Services; 9.1 What is the goal of Project Mendocino?; 9.2 How does Project Mendocino use ESA?; 9.3 Project Mendocino applications; 9.4 The Project Mendocino architecture; 9.5 ESA in action: Agile Solutions Ltda; Chapter TEN: ESA at Work: Examples from the Field; 10.1 ESA in consumer products; 10.2 Store-specific pricing; 10.3 ESA inCustomer Relationship Management (CRM)ESA in CRM:ESACRM service request processing; 10.4 ESA in the chemical industry: e-VMI at Solvay; 10.5 ESA for logistic service providers; 10.6 ESA for professional service providers; 10.7 ESA in manufacturing; 10.8 ESA in the chemicals industry; Part IV: COMPOSING SERVICES; Chapter ELEVEN: SAP xApps Composite Applications for Analytics; 11.1 How do SAP xApp Analytics help business users?; 11.2 How hard is it to deploy SAP xApp Analytics?; 11.3 What are the different parts of an analytic composite application?; 11.4 In which application and process areas are analytic composites being created?; 11.5 How do ESA and SAP NetWeaver help create analytic composites?; 11.6 What are the benefits of SAP analytics?; Chapter TWELVE: The Architecture and Development Tools of Composite Applications; 12.1 The architecture of composite applications; 12.2 Development tools for composite applications; 12.3 ESA in action: Asian Paints; 12.4 ESA in action: Zuger Kantonalbank; Chapter THIRTEEN: Supporting Composite Applications; 13.1 How are composite applications different from the previous generation of applications?; 13.2 SAP NetWeaver MDM; 13.3 SAP NetWeaver Business intelligence; 13.4 SAP NetWeaver Knowledge Management and Collaboration; 13.5 SAP NetWeaver Mobile; 13.6 ESA in action: Arla Foods; Part V: CREATING SERVICES; Chapter FOURTEEN: Web Services Basics; 14.1 What are web services and why do we care?; 14.2 What are some examples of web services?; 14.3 What are services?; 14.4 What is service-oriented architecture?; 14.5 Why is service orientation better than object orientation?; 14.6 What are the main components of web services?; 14.7 What is XML?; 14.8 What is XML schema?; 14.9 What are XML namespaces?; 14.10 What is SOAP?; 14.11 What is WSDL?; 14.12 What is UDDI and how does it relate to SAP?; 14.13 How can we ensure that web services will interoperate?; 14.14 What about web services security?; Chapter FIFTEEN: Creating Enterprise Services in ABAP; 15.1 Can I start creating enterprise services today, or should I wait?; 15.2 How do web services and enterprise services compare?; 15.3 What are two ways to create services in ABAP?; 15.4 What is SAP NetWeaver's role in creating enterprise services?; 15.5 What is the role of the SAP NetWeaver Application Server?; 15.6 What is SAP NetWeaver XI's role as an integration broker?; 15.7 What steps are involved with web services brokering using SAP NetWeaver XI?; 15.8 How can services be adapted to reflect changing customer needs?; 15.9 What does the future hold for creating enterprise services?; Chapter SIXTEEN: Creating and Consuming Services in Java; 16.1 What development tools are available for Java developers?; 16.2 How do you create a service provider in Java?; 16.3 How do you create a service consumer using Web Dynpro for Java?; 16.4 ESA in action: Arcelor; 16.5 ESA in action: TRW; Part VI: CONTROLLING SERVICES; Chapter SEVENTEEN: ESA and IT Governance; 17.1 What are typical models for IT governance?; 17.2 What are the challenges and problems with existing models?; 17.3 How does ESA decrease the need for IT governance?; 17.4 How does ESA improve the relationship between business and IT?; 17.5 Who owns enterprise services? Who makes a decision about creating new services?; 17.6 What processes make sense for approving new enterprise services?; 17.7 ESA in action: Whirlpool Corporation; Chapter EIGHTEEN: ESA Life Cycle Management and Operations; 18.1 Which operations and management problems will ESA actually solve?; 18.2 What is life cycle management?; 18.3 What is life cycle management in the context of ESA?; 18.4 What are the challenges for life cycle management in the context of ESA?; 18.5 How will services be monitored in an ESA landscape? Where will the necessary metadata come from?; 18.6 How does ESA affect implementation issues?; 18.7 How are operations affected by ESA?; 18.8 How will ESA affect change management and software logistics?; 18.9 What is adaptive computing and how does it relate to ESA?; 18.10 What does the introduction of ESA and its impact on life cycle management mean for IT departments?; 18.11 Will life cycle management capabilities be available to ISVs?; 18.12 What additional capabilities does ESA offer in terms of allowing business analysts to determine which revenue-generating services should receive additional resources?; Chapter NINETEEN: ESA Security; 19.1 What security challenges face enterprise architects?; 19.2 What are identity management and authentication?; 19.3 How does identity management change within ESA?; 19.4 What is access management?; 19.5 How does access management change within ESA?; 19.6 How are messages that are sent from enterprise services secured? What standards have been developed?; 19.7 How do you develop secure composite applications without weaknesses?; 19.8 How will security between companies function and evolve in an ESA environment?; Chapter TWENTY: Standards and ESA; 20.1 How do standards relate to ESA?; 20.2 What are semantic standards, and how do they help build IT solutions?; 20.3 Which technology standards does SAP support, and how do they help build IT solutions?; 20.4 Which technology standards does SAP NetWeaver support?; Colophon;