Enterprise SOA: Designing IT for Business Innovation

ISBN: 0596102380
EAN: 2147483647

Year: 2004
Pages: 265

Authors: Dan Woods, Thomas Mattern

BUY ON AMAZON

Enterprise SOA: Designing IT for Business Innovation
Table of Contents
Enterprise SOA: Designing IT for Business Innovation
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
Section 1.1. Who is this book for?
Section 1.2. Why so many questions?
Section 1.3. What forces created ESA?
Section 1.4. What is ESA?
Section 1.5. How will ESA change how applications are designed and built?
Section 1.6. What supporting infrastructure does ESA require?
Section 1.7. Is ESA compatible with event-driven architecture?
Section 1.8. What is the promise of ESA?
Section 1.9. How will the transition to ESA occur?
Section 1.10. How can ESA be addressed at a tactical level?
Section 1.11. Why does ESA matter?
Section 1.12. What are the core values of ESA?
Section 1.13. Where can we go for more answers?
Section 1.14. ESA in action: Mitsui
Chapter TWO. The Business Case for ESA
Section 2.1. What attributes must ESA embody?
Section 2.2. What principles should be driving my IT decisions?
Section 2.3. What happens when core eventually becomes context?
Section 2.4. How does ESA enable consolidation and reuse?
Section 2.5. What kind of innovation should companies pursue, and how will ESA help them?
Section 2.6. What are ESA s practical implementation issues?
Section 2.7. What s the long-term adoption path of ESA? How quickly will I see ROI, and what form will it take?
Section 2.8. What is ESA s long-range impact on corporations?
Section 2.9. ESA in action: Nordzucker AG
Chapter THREE. Evolving Toward ESA
Section 3.1. Conceiving
Section 3.2. Consuming
Section 3.3. Composing
Section 3.4. Creating
Section 3.5. Controlling
Section 3.6. Just how much and what kind of change will ESA involve?
Section 3.7. What is IT s role within ESA?
Section 3.8. What do you mean by
Section 3.9. That s a good point, but how do you bring the two sides together in the first place?
Section 3.10. What is IT s role if all of this comes to pass? What does my company look like then?
Section 3.11. What stages will we go through on the way there? What skills will we have to develop?
Section 3.12. What kind of architecture skills does ESA call for?
Section 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?
Section 3.14. How will IT change in an ESA world?
Section 3.15. What will the shift to a model-driven world mean for IT, and where will these business analysts come from?
Section 3.16. How will governance function within ESA?
Section 3.17. How and where should I begin evolving toward ESA?
Section 3.18. How will modeling translate between enterprises with different architectures? Will a standards body evolve to resolve potential conflicts?
Section 3.19. What do the analysts think, and what trouble do they foresee?
Section 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
Section 4.1. What is architecture and why is it important?
Section 4.2. What is enterprise architecture and how will ESA change it?
Section 4.3. What motivated the creation of ESA?
Section 4.4. What are the architectural challenges of ESA?
Section 4.5. How does ESA meet those challenges?
Section 4.6. Does ESA make all my existing systems worthless?
Section 4.7. What are systems of record?
Section 4.8. What are transactional systems?
Section 4.9. What are web services?
Section 4.10. What is the difference between a web service and an enterprise service?
Section 4.11. What is service-oriented architecture?
Section 4.12. What is the difference between ESA and other approaches to SOA?
Section 4.13. What are composite applications?
Section 4.14. What are service consumers?
Section 4.15. What are service providers?
Section 4.16. What are xApps?
Section 4.17. What role does the mySAP Business Suite play in ESA?
Section 4.18. What role does SAP NetWeaver play in ESA?
Section 4.19. What are IT practices and IT scenarios?
Section 4.20. What is event-driven architecture?
Section 4.21. Why are analytics so important to ESA?
Section 4.22. How does ESA provide for easier adaptation and a better requirements fit?
Section 4.23. What is the basic structure of an enterprise service?
Section 4.24. What are global data types?
Section 4.25. Why is XML messaging so important to ESA?
Section 4.26. What is the difference between a frontend and a backend application?
Section 4.27. What is service composition?
Section 4.28. What is the role of business objects in ESA?
Section 4.29. How does persistence change in ESA?
Section 4.30. Why does modeling matter? Isn t it just another form of coding?
Section 4.31. Will modeling replace coding?
Section 4.32. How are patterns used in ESA and what value do they provide?
Section 4.33. What is process orchestration?
Section 4.34. What is process integration?
Section 4.35. How will ESA change the way applications are packaged and delivered?
Section 4.36. What are the special needs of composite applications?
Section 4.37. What is the relationship between ESA, standards, and commoditization?
Section 4.38. Is buy versus build a false tradeoff in ESA?
Section 4.39. Why is an ecosystem of companies and standards so important to ESA?
Chapter FIVE. The Structure of ESA
Section 5.1. Basics of ESA applications
Section 5.2. The ESA stack, layer by layer
Section 5.3. The enterprise services layer
Section 5.4. The business objects layer
Section 5.5. The process orchestration layer
Section 5.6. The UI layer
Section 5.7. The persistence layer
Chapter SIX. The Enterprise Services Community
Section 6.1. What is the ES-Community?
Section 6.2. What is the value of the ES-Community?
Section 6.3. What is a Definition Group? Who can join?
Section 6.4. What does the ES-Community contribute?
Section 6.5. Will the ES-Community create new standards?
Section 6.6. How are enterprise service definitions created within the ES-Community?
Section 6.7. What is the organizational structure of a Definition Group?
Section 6.8. What is certification? Is it mandatory?
Section 6.9. What is ES-Ready? How can partners use this brand?
Section 6.10. How does the ES-Community balance efficiency with open participation?
Section 6.11. What is required to participate in the ES-Community?
Section 6.12. How is intellectual property (IP) treated in the ES-Community?
Section 6.13. How will the ES-Community differ from SAP s other partner and customer efforts?
Section 6.14. How does participation in the ES-Community benefit customers?
Section 6.15. What should a company do to get involved in the community process?
Chapter SEVEN. Creating a Roadmap with the ESA Adoption Program
Section 7.1. Why the roadmap approach?
Section 7.2. What challenges do companies face in adopting ESA?
Section 7.3. How does SAP help customers adopt ESA?
Section 7.4. Is there more to success with ESA than just analyzing technologies and preparing roadmaps?
Section 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
Section 8.1. What is the Enterprise Services Repository?
Section 8.2. What is the Enterprise Services Inventory?
Section 8.3. ESA in action: Elsag
Section 8.4. ESA in action: Kimberly-Clark
Section 8.5. ESA in action: CSA International
Chapter NINE. Project Mendocino: A Product Based on Consuming Enterprise Services
Section 9.1. What is the goal of Project Mendocino?
Section 9.2. How does Project Mendocino use ESA?
Section 9.3. Project Mendocino applications
Section 9.4. The Project Mendocino architecture
Section 9.5. ESA in action: Agile Solutions Ltda
Chapter TEN. ESA at Work: Examples from the Field
Section 10.1. ESA in consumer products
Section 10.2. Store-specific pricing
Section 10.3. ESA in CRM: service request processing
Section 10.4. ESA in the chemical industry: e-VMI at Solvay
Section 10.5. ESA for logistic service providers
Section 10.6. ESA for professional service providers
Section 10.7. ESA in manufacturing
Section 10.8. ESA in the chemicals industry
Part IV: COMPOSING SERVICES
Chapter ELEVEN. SAP xApps Composite Applications for Analytics
Section 11.1. How do SAP xApp Analytics help business users?
Section 11.2. How hard is it to deploy SAP xApp Analytics?
Section 11.3. What are the different parts of an analytic composite application?
Section 11.4. In which application and process areas are analytic composites being created?
Section 11.5. How do ESA and SAP NetWeaver help create analytic composites?
Section 11.6. What are the benefits of SAP analytics?
Chapter TWELVE. The Architecture and Development Tools of Composite Applications
Section 12.1. The architecture of composite applications
Section 12.2. Development tools for composite applications
Section 12.3. ESA in action: Asian Paints
Section 12.4. ESA in action: Zuger Kantonalbank
Chapter THIRTEEN. Supporting Composite Applications
Section 13.1. How are composite applications different from the previous generation of applications?
Section 13.2. SAP NetWeaver MDM
Section 13.3. SAP NetWeaver Business intelligence
Section 13.4. SAP NetWeaver Knowledge Management and Collaboration
Section 13.5. SAP NetWeaver Mobile
Section 13.6. ESA in action: Arla Foods
Part V: CREATING SERVICES
Chapter FOURTEEN. Web Services Basics
Section 14.1. What are web services and why do we care?
Section 14.2. What are some examples of web services?
Section 14.3. What are services?
Section 14.4. What is service-oriented architecture?
Section 14.5. Why is service orientation better than object orientation?
Section 14.6. What are the main components of web services?
Section 14.7. What is XML?
Section 14.8. What is XML schema?
Section 14.9. What are XML namespaces?
Section 14.10. What is SOAP?
Section 14.11. What is WSDL?
Section 14.12. What is UDDI and how does it relate to SAP?
Section 14.13. How can we ensure that web services will interoperate?
Section 14.14. What about web services security?
Chapter FIFTEEN. Creating Enterprise Services in ABAP
Section 15.1. Can I start creating enterprise services today, or should I wait?
Section 15.2. How do web services and enterprise services compare?
Section 15.3. What are two ways to create services in ABAP?
Section 15.4. What is SAP NetWeaver s role in creating enterprise services?
Section 15.5. What is the role of the SAP NetWeaver Application Server?
Section 15.6. What is SAP NetWeaver XI s role as an integration broker?
Section 15.7. What steps are involved with web services brokering using SAP NetWeaver XI?
Section 15.8. How can services be adapted to reflect changing customer needs?
Section 15.9. What does the future hold for creating enterprise services?
Chapter SIXTEEN. Creating and Consuming Services in Java
Section 16.1. What development tools are available for Java developers?
Section 16.2. How do you create a service provider in Java?
Section 16.3. How do you create a service consumer using Web Dynpro for Java?
Section 16.4. ESA in action: Arcelor
Section 16.5. ESA in action: TRW
Part VI: CONTROLLING SERVICES
Chapter SEVENTEEN. ESA and IT Governance
Section 17.1. What are typical models for IT governance?
Section 17.2. What are the challenges and problems with existing models?
Section 17.3. How does ESA decrease the need for IT governance?
Section 17.4. How does ESA improve the relationship between business and IT?
Section 17.5. Who owns enterprise services? Who makes a decision about creating new services?
Section 17.6. What processes make sense for approving new enterprise services?
Section 17.7. ESA in action: Whirlpool Corporation
Chapter EIGHTEEN. ESA Life Cycle Management and Operations
Section 18.1. Which operations and management problems will ESA actually solve?
Section 18.2. What is life cycle management?
Section 18.3. What is life cycle management in the context of ESA?
Section 18.4. What are the challenges for life cycle management in the context of ESA?
Section 18.5. How will services be monitored in an ESA landscape? Where will the necessary metadata come from?
Section 18.6. How does ESA affect implementation issues?
Section 18.7. How are operations affected by ESA?
Section 18.8. How will ESA affect change management and software logistics?
Section 18.9. What is adaptive computing and how does it relate to ESA?
Section 18.10. What does the introduction of ESA and its impact on life cycle management mean for IT departments?
Section 18.11. Will life cycle management capabilities be available to ISVs?
Section 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
Section 19.1. What security challenges face enterprise architects?
Section 19.2. What are identity management and authentication?
Section 19.3. How does identity management change within ESA?
Section 19.4. What is access management?
Section 19.5. How does access management change within ESA?
Section 19.6. How are messages that are sent from enterprise services secured? What standards have been developed?
Section 19.7. How do you develop secure composite applications without weaknesses?
Section 19.8. How will security between companies function and evolve in an ESA environment?
Chapter TWENTY. Standards and ESA
Section 20.1. How do standards relate to ESA?
Section 20.2. What are semantic standards, and how do they help build IT solutions?
Section 20.3. Which technology standards does SAP support, and how do they help build IT solutions?
Section 20.4. Which technology standards does SAP NetWeaver support?
About the Author
Colophon
Index
A
B
C
D
E
F
G
H
I
J
K
L
M
N
O
P
R
S
T
U
V
W
X
Y
Z