Enterprise SOA. Designing IT for Business Innovation (ebook)(audiobook)(audiobook)

Spis treści

• Enterprise SOA
  • SPECIAL OFFER: Upgrade this ebook with OReilly
  • Foreword
  • Preface
    • Safari Enabled
    • How can I comment on this book?
    • Acknowledgments
  • I. THE CONTEXT FOR ESA
    • 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.3.1. Application proliferation: systems of record are built out
        • 1.3.2. Bridging the gap among systems of record
        • 1.3.3. Consolidation: mySAP? Business Suite and SAP NetWeaver
        • 1.3.4. The web services era
      • 1.4. What is ESA?
        • 1.4.1. User interface
        • 1.4.2. Process orchestration
        • 1.4.3. Enterprise services
        • 1.4.4. Business objects
        • 1.4.5. Distributed persistence
      • 1.5. How will ESA change how applications are designed and built?
      • 1.6. What supporting infrastructure does ESA require?
        • 1.6.1. Model-driven, pattern-based development tools
        • 1.6.2. Enterprise Services Infrastructure
        • 1.6.3. Enterprise Services Repository
        • 1.6.4. Enterprise Services Inventory
        • 1.6.5. Life cycle management, operations, and security
        • 1.6.6. Industry and technology standards
        • 1.6.7. ESA ecosystem
      • 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.9.1. ESAs areas of focus for applications
        • 1.9.2. ESA today: SAP R/3
        • 1.9.3. ESA in mySAP ERP 2004 and mySAP ERP 2005
        • 1.9.4. ESA in the future
      • 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
    • 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
    • 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?
  • II. CONCEIVING A VISION FOR ESA
    • 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?
    • FIVE. The Structure of ESA
      • 5.1. Basics of ESA applications
        • 5.1.1. How are applications in ESA different from previous generations?
        • 5.1.2. How are services combined into applications in ESA?
        • 5.1.3. Can an application be both a consumer and a provider of services?
        • 5.1.4. How does ESA work with event-driven architectures?
          • 5.1.4.1. Core events and business events
      • 5.2. The ESA stack, layer by layer
        • 5.2.1. What challenges face the ESA stack?
          • 5.2.1.1. User interface
          • 5.2.1.2. Process orchestration
          • 5.2.1.3. Enterprise services
          • 5.2.1.4. Business objects
          • 5.2.1.5. Persistence
      • 5.3. The enterprise services layer
        • 5.3.1. What is the basic structure of enterprise services?
        • 5.3.2. What are global data types and how are they related to enterprise services?
        • 5.3.3. Does ESA have an Enterprise Service Bus or the equivalent?
        • 5.3.4. How are database transactions handled in ESA?
        • 5.3.5. This is all rather technical; how do enterprise services get the business meaning they are supposed to have?
        • 5.3.6. How do enterprise services fit into business process modeling?
        • 5.3.7. What is service composition? How can you build enterprise services from other enterprise services?
        • 5.3.8. What are the main categories of enterprise services?
        • 5.3.9. What kinds of enterprise services support the special needs of composite applications?
          • 5.3.9.1. Master data management
          • 5.3.9.2. Business Intelligence (BI) Consumer Services
          • 5.3.9.3. Analytics
          • 5.3.9.4. Knowledge management
          • 5.3.9.5. Collaboration
          • 5.3.9.6. Mobile
        • 5.3.10. What development tools are used to create enterprise services?
      • 5.4. The business objects layer
      • 5.5. The process orchestration layer
        • 5.5.1. What is process orchestration?
        • 5.5.2. Why is process orchestration important in ESA?
        • 5.5.3. What forms of process orchestration will be used in ESA?
        • 5.5.4. What are the limits of process orchestration?
        • 5.5.5. How does process component modeling work?
      • 5.6. The UI layer
        • 5.6.1. How will the UI layer change in ESA?
        • 5.6.2. How will modeling be used to create the UI layer?
        • 5.6.3. What are patterns and UI building blocks?
        • 5.6.4. How will UI building blocks and patterns change the nature of applications?
        • 5.6.5. How will the UI be implemented under ESA?
      • 5.7. The persistence layer
        • 5.7.1. How will this discussion be continued?
    • 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.7.1. How do Request Definition Groups operate?
        • 6.7.2. How do Review Definition Groups operate?
      • 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?
    • 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.3.1. What happens in the Discover phase?
          • 7.3.1.1. What do the workshops reveal?
          • 7.3.1.2. How about a concrete example?
          • 7.3.1.3. Are there different types of enterprise services to look for?
          • 7.3.1.4. How can companies avoid disruptive change?
        • 7.3.2. What happens in the Evaluate phase?
          • 7.3.2.1. What will the customer be able to see with the roadmap in hand?
        • 7.3.3. What about the Implement phase?
        • 7.3.4. What happens in the Operate phase?
      • 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?
        • 7.5.1. ESA in action: Manchette Publicité
        • 7.5.2. ESA in action: Wacker Chemie AG
        • 7.5.3. ESA in action: LHI Leasing
  • III. CONSUMING SERVICES
    • EIGHT. The Enterprise Services Repository and the Enterprise Services Inventory
      • 8.1. What is the Enterprise Services Repository?
        • 8.1.1. What are the Enterprise Services Repository's roots?
        • 8.1.2. What are the advantages of the Enterprise Services Repository?
          • 8.1.2.1. Orderly development
          • 8.1.2.2. Reuse
          • 8.1.2.3. Ease of development
          • 8.1.2.4. Model-driven development
          • 8.1.2.5. Service orchestration
        • 8.1.3. What tools do you use to access the Enterprise Services Repository?
        • 8.1.4. If the Enterprise Services Repository is at the heart of ESA, don't less technical people use it, too?
        • 8.1.5. What is in the Enterprise Services Repository?
          • 8.1.5.1. Data types
          • 8.1.5.2. Message types
          • 8.1.5.3. Operations
          • 8.1.5.4. Service interfaces
          • 8.1.5.5. Integration objects
          • 8.1.5.6. Process models
          • 8.1.5.7. Business objects
        • 8.1.6. What is the role of namespaces in the Enterprise Services Repository?
      • 8.2. What is the Enterprise Services Inventory?
        • 8.2.1. What does the Enterprise Services Inventory provide for each service?
        • 8.2.2. What kinds of services are part of the Enterprise Services Inventory?
        • 8.2.3. What methodology has SAP created for service enablement?
        • 8.2.4. How do the indicators and the procedural model work in practice?
          • 8.2.4.1. Scenario for purchasing a new component
          • 8.2.4.2. Process flow
          • 8.2.4.3. Deployment
          • 8.2.4.4. Service identification by applying the indicators
          • 8.2.4.5. Applying general indicators
          • 8.2.4.6. Applying user productivity and centricity indicators
          • 8.2.4.7. Applying best practices and process innovation indicators
          • 8.2.4.8. Applying business automation and process efficiency indicators
          • 8.2.4.9. Applying flexible deployment indicators
        • 8.2.5. For each service, what does the Enterprise Services Inventory provide?
        • 8.2.6. What is the Enterprise Services Preview?
      • 8.3. ESA in action: Elsag
      • 8.4. ESA in action: Kimberly-Clark
      • 8.5. ESA in action: CSA International
    • 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.3.1. What is the goal of the Time Management application?
        • 9.3.2. What is the goal of the Leave Management application?
        • 9.3.3. What is the goal of the Budget Monitoring application?
        • 9.3.4. What is the goal of the Team Management application?
      • 9.4. The Project Mendocino architecture
        • 9.4.1. What makes up the Mendocino extensions?
        • 9.4.2. What is the Office Add-On?
        • 9.4.3. How is data routed through the Project Mendocino architecture?
        • 9.4.4. What are the system requirements for using the Project Mendocino architecture?
        • 9.4.5. What is the primary function of the Office Add-On?
        • 9.4.6. What are the functions of the Mendocino extensions components?
        • 9.4.7. How is security handled in the Project Mendocino environment?
        • 9.4.8. How will Project Mendocino change in the future?
      • 9.5. ESA in action: Agile Solutions Ltda
    • TEN. ESA at Work: Examples from the Field
      • 10.1. ESA in consumer products
      • 10.2. Store-specific pricing
      • 10.3. ESA in CRM: 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
  • IV. COMPOSING SERVICES
    • ELEVEN. SAP xApps Composite Applications for Analytics
      • 11.1. How do SAP xApp Analytics help business users?
        • 11.1.1. SAP xApp Analytics for credit management
        • 11.1.2. SAP xApp Analytics composite application for campaign management
        • 11.1.3. SAP xApp Analytics composite application for corporate governance
      • 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?
    • TWELVE. The Architecture and Development Tools of Composite Applications
      • 12.1. The architecture of composite applications
        • 12.1.1. What is the purpose of composite applications in ESA?
        • 12.1.2. What is the architecture of composite applications?
          • 12.1.2.1. Roles and work centers
          • 12.1.2.2. Composite processes and business activities
          • 12.1.2.3. Actions
          • 12.1.2.4. Composite application business logic and abstraction layer
          • 12.1.2.5. Service providers
        • 12.1.3. What are the main categories of composite applications?
        • 12.1.4. How are processes modeled in composite applications?
        • 12.1.5. How do composite applications use patterns?
      • 12.2. Development tools for composite applications
        • 12.2.1. What development tools are used to create composites?
        • 12.2.2. Can every development challenge be met through modeling?
        • 12.2.3. What role does SAP NetWeaver Visual Composer play in creating composites?
        • 12.2.4. What role does the Guided Procedures design time play in creating composites?
        • 12.2.5. What role does the SAP CAF play in creating composites?
        • 12.2.6. What roles do the ABAP Development Workbench and SAP NetWeaver Developer Studio play in creating composites?
      • 12.3. ESA in action: Asian Paints
      • 12.4. ESA in action: Zuger Kantonalbank
    • THIRTEEN. Supporting Composite Applications
      • 13.1. How are composite applications different from the previous generation of applications?
        • 13.1.1. What are the challenges facing composite application developers and architects?
        • 13.1.2. What is information management and how will it help?
      • 13.2. SAP NetWeaver MDM
        • 13.2.1. What is master data?
        • 13.2.2. What is SAP NetWeaver MDM?
        • 13.2.3. What are the key capabilities of SAP NetWeaver MDM for information quality?
        • 13.2.4. What are the key capabilities of SAP NetWeaver MDM for information synchronization?
        • 13.2.5. How does SAP NetWeaver MDM help development of composite applications?
      • 13.3. SAP NetWeaver Business intelligence
        • 13.3.1. What are the core functions of SAP NetWeaver BI?
          • 13.3.1.1. Enterprise data warehousing
          • 13.3.1.2. Enterprise reporting, querying, and analysis
          • 13.3.1.3. Business planning and analytical services
          • 13.3.1.4. Data quality
        • 13.3.2. How is business intelligence becoming service enabled?
        • 13.3.3. What is the SAP NetWeaver BI Accelerator?
        • 13.3.4. How will SAP NetWeaver BI help embed analytics into composites?
      • 13.4. SAP NetWeaver Knowledge Management and Collaboration
        • 13.4.1. What is Knowledge Management and Collaboration?
        • 13.4.2. What Knowledge Management capabilities can help composite applications?
        • 13.4.3. What collaboration capabilities can help composite applications?
        • 13.4.4. How can KMC help composite applications?
      • 13.5. SAP NetWeaver Mobile
      • 13.6. ESA in action: Arla Foods
  • V. CREATING SERVICES
    • 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?
    • 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.3.1. What does it mean to create services from the inside out?
        • 15.3.2. How do you create a service from the inside out using ABAP?
        • 15.3.3. What does it mean to create services from the outside in?
        • 15.3.4. How do you create a service from the outside in using 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?
        • 15.9.1. What are business objects?
        • 15.9.2. What are the steps one takes to develop enterprise services?
    • 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
  • VI. CONTROLLING SERVICES
    • 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
    • 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.7.1. What is capacity planning in the world of ESA?
        • 18.7.2. How do you size composite applications?
        • 18.7.3. How does performance monitoring work in an ESA environment?
        • 18.7.4. How does virtualization affect capacity planning?
      • 18.8. How will ESA affect change management and software logistics?
        • 18.8.1. What is the SAP NetWeaver Administrator? How will it adapt to the demands of an ESA environment?
      • 18.9. What is adaptive computing and how does it relate to ESA?
        • 18.9.1. What's behind adaptive computing?
        • 18.9.2. The Adaptive Computing Controller
        • 18.9.3. How do conventional infrastructure approaches compare to adaptive computing?
        • 18.9.4. What will adaptive computing mean for SAP's partners?
      • 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?
    • 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?
    • TWENTY. Standards and ESA
      • 20.1. How do standards relate to ESA?
        • 20.1.1. Isn't standardization between disparate brands of systems and between independent companies easier said than done?
        • 20.1.2. What kinds of standards does ESA rely on?
        • 20.1.3. What is SAP's general approach to standards?
        • 20.1.4. Does ESA provide support for every major IT standard?
      • 20.2. What are semantic standards, and how do they help build IT solutions?
        • 20.2.1. Are semantic standards simply sets of XML tags?
        • 20.2.2. What are core components and how do they relate to SAP's concept of semantic standards?
      • 20.3. Which technology standards does SAP support, and how do they help build IT solutions?
        • 20.3.1. What's an example of a critical technology standard?
      • 20.4. Which technology standards does SAP NetWeaver support?
        • 20.4.1. How do portability standards help customers to build IT solutions?
        • 20.4.2. What is SAP's relationship to industry-specific standards groups?
        • 20.4.3. Are standards tested to ensure they provide interoperability?
        • 20.4.4. Which additional standards will ESA support in the future?
  • Index
  • About the Authors
  • Colophon
  • SPECIAL OFFER: Upgrade this ebook with OReilly

pokaż cały spis treści

ukryj recenzje