Enterprise SOA : Designing IT for Business Innovation
Dan. Woods
Bok Engelsk 2008 · Electronic books.
| Utgitt | Sebastopol : : O'Reilly Media, , 2008.
|
|---|---|
| Omfang | 1 online resource (456 p.)
|
| Opplysninger | Description based upon print version of record.. - Enterprise SOA; Preface; How can I comment on this book?; Acknowledgments; I. THE CONTEXT FOR ESA; 1.2. Why so many questions?; 1.3. What forces created ESA?; 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.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.2. Enterprise Services Infrastructure. - 1.14. ESA in action: MitsuiTWO. The Business Case for ESA; 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.2. Consuming. - 1.6.3. Enterprise Services Repository1.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.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?. - 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.3. Composing3.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?. - 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 imple
|
| Emner | |
| Sjanger | |
| Dewey | |
| ISBN | 0596102380
|
