Companies should base their storage architecture decisions on the amount of XML they are producing and the extensibility of that data. Relational and XML data differ in many, significant ways. The implication is that these two, very different data types may require two, very different storage solutions. Table of Contents: I. Report Scope II. XML Data Storage: A Market Overview 2. 1 XML Data Storage 2. 2 Structured, Semi-Structured, and Relational Content in the Enterprise III. Drivers for XML Storage 3. 1 Content Management, Reuse, and Single-Source Publishing 3. 2 Web Services and Service-Oriented Integration 3. 3 e-Business Messaging and Business Process Auditing 3. 4 Effective Content Searching 3. 5 XML-driven Web Sties 3. 6 Device Communications and Data Storage IV. Support for XML in RDBMS Systems 4. 1 Strategies for Storing XML Data in Relational Databases 4. 2 Advantages of XML Extensions to RDBMS systems 4. 3 Disadvantages of XML-Enabled RDBMS systems 4. 4 Current Support of XML features in RDBMS Products 4. 5. XML-Enabled RDBMS Market Growth V. "Native" XML Data Stores (NXDs) 5. 1 The Native XML Data Store Defined 5. 2 NXD Storage Architectures 5. 3 Advantages of NXDs 5. 4 Disadvantages of NXDs 5. 5 NXD Market Size and Growth 5. 6 WS Support in NXD 5. 7 Schema-dependent vs. Schema-Independent Approaches 5. 8 Eliminating the Need for Data Modeling? VI. Barriers to XML Data Store Adoption and Alternatives 6. 1 XML-based Data Integration 6. 2 Content Management as an Alternative to NXDs? 6. 3 Architectures and Performance Challenges 6. 4 Uncertain Direction of XML Standards 6. 5 When Does the 800-pound Gorilla Enter? 6. 6 Web Services Support in NXDs 6. 7 Value-Adding XML Storage VII. Key XML Storage and Retrieval Standards 7. 1 XPath 7. 2 XQuery 7. 3 XLink 7. 4 The Document Object Model (DOM) 7. 5 Z39. 50 Search and Retrieval Protocol 7. 6 WebDAV 7. 7 XUpdate VIII. ROI for XML Storage 8. 1 Taking advantage of the "X" in XML 8. 2 Enabling Integration 8. 3 Enabling Content Reuse 8. 4 XML Data Storage Evaluation Criteria IX. Market Size and Future Trends 9. 1 Market Adoption of XML Data Stores 9. 2 Trend: Embedding of XML Data Stores 9. 3 NXD Vendor Positioning 9. 4 NXDs as UDDI repositories 9. 5 XML Metadata Mining X. Conclusions 10. 1 Key Notes 10. 2 Decision Points 10. 3 Figures 10. 4 Tables XI. Profiled Vendors 11. 1 RDBMS Vendors with XML Extensions 11. 2 Native XML Data Store Vendors A. Related Research B. Supporting Resource C. Trademark Notice and Statement of Opinion About ZapThink, LLC.

3. Will Applications Deliver their own UI in the future? 9 2. 4. Understanding the Presentation Layer Requirements of SOAs 10 III. Implementing Rich User Interactivity on SOAs 11 3. 1. The Evolving Desktop Operating System 11 3. 2. Rich Client-focused Technologies 13 3. 3. The Emerging Smart Client 21 3. 4. Building More Robust Presentation Layers 22 3. 5. Emerging Standards for Rich Clients 24 IV. Market Trends 27 4. 1. Growth of the Rich Clients for SOAs Opportunity 27 4. 2. Growth Drivers for Market Adoption of Rich Clients for SOAs 32 4. 3. Potential Barriers to Adoption of Rich Clients for SOAs 33 V. Conclusions 33 5. 1. Key Notes 34 5. 2. Decision Points 35 5. 3. Figures 35 5. 4. Tables 35.

The 2003 timeframe won't see many multiple-company B2B Web Services, because companies will choose to implement B2B Web Services on a point-to-point basis. Existing 3A security vendors will incorporate XML and Web Services into their product lines, so by 2006, most 3A security products will support or provide XML and/or Web Services security. This report must be placed into the context of an overall security strategy. Simply securing all of a company's Web Services alone can only provide a false sense of security. Enterprises must institute policies that apply to their entire enterprise network (including participants invited from outside), and administer that security in a hierarchical fashion. Next-generation firewalls must be capable of looking at the content of XML streams, and the security mechanisms for such data must be part of that content. Companies planning on using Web Services across the firewall will necessarily have to resolve the resulting security issues first. Table of Contents: I. Report Scope II. Context for Security in the Web Services Model 2. 1 The ZapThink Web Services Roadmap 2. 2 Security: The Key Enabler for Web Services 2. 3 Context: Security Products & Services 2. 4 Context: Web Services Management and Infrastructure Products 2. 5 Context: Global Identity Services 2. 6 Context: Digital Rights Management Technologies 2. 7 Context: Directory Servers III. Technology Landscape 3. 1 XML security and the shift to Service-oriented computing 3. 2 Principles of Application Security 3. 2. 1 Application level security requirements 3. 2. 2 Authentication 3. 2. 3 Authorization and Access Control 3. 2. 4 Confidentiality 3. 2. 5 Data Integrity 3. 2. 6 Non-Repudiation 3. 3 IT Security Precursors 3. 3. 1 Encryption and Decryption 3. 3. 2 Symmetric-Key Encryption 3. 3. 3 Public-Key Encryption 3. 3. 4 Digital Signatures 3. 3. 5 Digital certificates 3. 3. 6 Authentication with certificates 3. 3. 7 How CA Certificates Establish Trust 3. 3. 8 Managing Certificates 3. 3. 9 Kerberos 3. 3. 10 Using HTTP 3. 3. 11 Secure Sockets Layer (SSL) 3. 4 XML Security Efforts 3. 4. 1 XML Signature 3. 4. 2 XML Encryption 3. 5 Web Services Security Efforts 3. 5. 1 SAML 3. 5. 2 XACML 3. 5. 3 XKMS 3. 5. 4 X-KRSS 3. 5. 5 X-KISS 3. 5. 6 WS-Security IV. Market Segmentation 4. 1 Web Services Security Platforms 4. 2 Web Services Infrastructure Management Vendors 4. 3 Secure Integration/EAI Vendors 4. 4 Global Trust Services 4. 5 Identity Management/Authorization/Single Sign-On Vendors 4. 6 Access & Policy Management Vendors 4. 7 PKI Vendors 4. 8 Web Services Security Toolkit Vendors 4. 9 Software XML Firewalls 4. 10 Private Web Services Network Providers 4. 11 Enterprise Security Services 4. 12 Security Service Providers V. Current State of the Market 5. 1 Approaches to the Market 5. 1. 1 Focused technology startups 5. 1. 2 Established Web Services vendors 5. 1. 3 Larger public vendors 5. 2 Customer perspective VI. Business & Technology Trends 6. 1 Long Term Trends: Relationship to the 3A Security Market 6. 2 Long term trends: relationship to Web Services market 6. 3 Inhibitors to the Growth of the XML and Web Services Security Market VII. Conclusions 7. 1 Key Notes 7. 2 Decision Points 7. 3 Figures 7. 4 Tables VIII. Vendor Profiles 8. 1 Web Services Security Platforms 8. 2 Secure Integration Vendors 8. 3 Global Trust Services 8. 4 Identity Management/Authorization/Single Sign-On Vendors 8. 5 Access & Policy Management Vendors 8. 6 Software XML Firewalls 8. 7 PKI Vendors 8. 8 Enterprise Security Services A. Related Research B. Supporting Resources C. Trademark Notice and Statement of Opinion About ZapThink, LLC.

The potential ROI realized by adopting Service-Oriented Architectures (SOA) far outweighs the slight benefits an organization gets from using Web Services as simply a "better API" for accessing application functionality. Integrating systems between two businesses is not only a technological problem; it requires pre-existing business relationships between the companies. Table of Contents: I. Report Scope II. Integration: The Challenges to be Solved 2. 1 The N-Squared Integration Challenge 2. 2 Classes of Integration Problem 2. 3 Traditional EAI and B2Bi Solutions 2. 4 Why Current EAI and B2Bi Solutions are Not Sufficient 2. 5 The Integration "Zipper" III. Service-Oriented Integration Approaches 3. 1 Using Web Services for Integration: Service-Oriented Integration (SOI) 3. 2 Methods for Implementing SOI 3. 3 SOI-enabled EAI and B2Bi Solutions 3. 4 Emerging SOI Solutions 3. 5 Data-focused SOI Solutions IV. Drivers for SOI Adoption 4. 1 Reduce the cost and complexity of managing IT infrastructures 4. 2 Provide a uniform platform for B2B exchange and marketplaces 4. 3 Move away from proprietary technologies and solutions 4. 4 Enable application and data reuse 4. 5 Simplify business modeling 4. 6 Provide fine-grained access to data, functionality, and logic V. ROI for Service-Oriented Integration 5. 1 TCO and ROI of Traditional EAI and B2Bi Solutions 5. 2 Improving the ROI Outlook with SOI 5. 3 The Movement to the "Agile Enterprise" Offers Greatest ROI 5. 4 Realize Integration ROI Internally First, Externally with Trusted Parties Second VI. Barriers and Challenges to SOI Adoption 6. 1 Interoperability of SOI implementations 6. 2 SOI specifications are far from complete 6. 3 SOI can require the re-architecting of systems 6. 4 Lack of Semantic Integration 6. 5 Web Services introduces its own level of complexity and inefficiency VII. Market Size and Future Trends 7. 1 The Convergence of EAI, B2Bi, and Data Integration Markets 7. 2 Market Opportunity and Sizing 7. 3 Current Vendor Positioning and Market Share 7. 4 Future Directions for Service-Oriented Integration VIII. Conclusions 8. 1 Key Notes 8. 2 Decision Points 8. 3 Figures 8. 4 Tables IX. Profiled Vendors 9. 1 SOI-enabled Web Services Platforms 9. 2 SOI-enabled EAI and B2Bi Solutions 9. 3 Emerging SOI Solutions 9. 4 Data-Focused SOI Solutions A. Related Research Reports Briefing Notes B. Supporting Resources C. Trademark Notice and Statement of Opinion About ZapThink, LLC.

What is a Service-Oriented Architecture? 2. 1. 1. Evolution of Distributed Computing 2. 2. Business Motivations for SOAs 2. 2. 1. The Economics of Business Agility III. Foundations of SOA 3. 1. SOA Foundation: Model-Driven Architecture 3. 2. SOA Foundation: Agile Methodologies 3. 3. The SOA Metamodel 3. 4. The 4+1 View Model of SOA IV. Best Practices of SOA 4. 1. Develop a top-down, extended enterprise SOA 4. 2. Build & maintain a platform independent Service model 4. 3. Maintain feedback at all points of the architecture 4. 4. Follow Agile Methodology principles & techniques within the context of the Service model 4. 5. Encapsulate existing/legacy functionality 4. 6. Embrace heterogeneity/follow a federation model of software 4. 7. Compose atomic Services into coarse-grained business Services 4. 8. Build for consumability/broad applicability 4. 9. Perform ad hoc upgrades 4. 10. Prioritize SOA transition activities on the fly V. Market Segmentation 5. 1. Current State of the Market VI. Business and Technology Trends 6. 1. Long Term Trends: A Shift in the Favored Approach to Distributed Computing 6. 2. Long-Term Trends: Grid/Utility Computing 6. 3. Inhibitors to Growth of Service Orientation and SOAs VII. Conclusions 7. 1. Key Notes 7. 2. Decision Points 7. 3. Best Practices 7. 4. Figures 7. 5. Tables VIII. Profiled Vendors.

1. Sources and Growth of Content in the Enterprise 2. 2. The Content Management Challenge 2. 3. The Evolution of the Content Management System (CMS) 2. 4. Markup Languages and Content III. The Content Lifecycle 3. 1. Content Creation 3. 2. The Content Repository 3. 3. Content Management 3. 4. Content Publishing and Distribution 3. 5. Content Syndication 3. 6. Content Protection IV. XML-Enabling the Content Lifecycle 4. 1. Is XML Necessary for Improving the Content Lifecycle? 4. 2. Content Creation: XML-based Authoring and Conversion 4. 3. Content Repository: Native XML Storage and Search 4. 4. Content Management: XML-based Content Componentization 4. 5. Content Publishing and Distribution 4. 6. Content Syndication: XML Standards and Products 4. 7. Content Protection: XML-powered DRM V. The ROI of XML-enabling the Content Lifecycle 5. 1. Cost Savings: Content Reuse 5. 2. Cost Savings: Efficient Content Search 5. 3. Revenue Enhancing: Enabling Content Syndication 5. 4. Cost Savings: Integrating Islands of Content VI. Challenges in Implementing an XML-enabled Content Lifecycle 6. 1. Metadata-encoding Content is Difficult 6. 2. XML May Not be Suitable as a Long-term Archival Format VII. The Service-Oriented Vision of Content 7. 1. Shifting away from a Publish-oriented Mentality 7. 2. Content as Services: Service-Oriented Content 7. 3. Content Lifecycle Functionality as Services VIII. Market for XML-enabled Content Lifecycle Products 8. 1. Market Sizing and Growth 8. 2. Vendor Market Segmentation and Positioning 8. 3. The Future of Content Management Systems IX. Conclusions 9. 1. Key Notes 9. 2. Decision Points 9. 3. Figures 9. 4. Tables X. Profiled Vendors 10. 1. Content Creation 10. 2. Content Repository 10. 3. Content Management 10. 4. Content Publishing / Distribution 10. 5. Content Syndication 10. 6. Content Protection Related Research Trademark Notice and Statement of Opinion About ZapThink, LLC.

Table of Contents: I. Report Scope II. The Role of the XML Proxy 2. 1 The Evolution of Networking Devices and Applications 2. 2 Why Current Network Protocol-based Solutions Are Not Adequate to handle XML Traffic 2. 3 XML Proxies 2. 4 Use and Context of XML Proxies III. XML Proxy Functionality 3. 1 Security 3. 2 Performance: Compression and Caching 3. 3 Monitoring and Management 3. 4 Routing 3. 5 Transformation IV. XML Proxy Solutions 4. 1 Hardware XML Network Appliances 4. 2 Software XML Proxies 4. 3 "Cross-over" Software and Hardware Solutions V Drivers for XML Proxy Adoption 5. 1 Managing increased volume of XML traffic on the network 5. 2 Enforcing corporate XML policies and normalizing XML implementations 5. 3 Simplifying external XML integration 5. 4 Providing Value-Added Services for XML VI. Barriers to Adoption of XML Proxies 6. 1 XML and Web Services Standards and Markets in Flux 6. 2 Increased Competition through Product "Scope Creep" 6. 3 The Rack "Stack" 6. 4 Processing Overhead VII. Future Trends 7. 1 Convergence on a set of functionality: the one-stop box 7. 2 Rapid growth of XML traffic on the network 7. 3 Entrance of the "Established" Network Appliance Vendors 7. 4 Further clarification of the role of SOAP Intermediaries VIII. Conclusions 8. 1 Key Notes 8. 2 Decision Points 8. 3 Figures 8. 4 Tables IX. Profiled Vendors 9. 1 XML-aware Network Appliances 9. 2 Software XML Firewalls and Proxies A. Related Research Reports Briefing Notes B. Copyright, Trademark Notice, and Statement of Opinion About ZapThink, LLC.

What are Business Processes? 2. 2. Why is Process Important to the Enterprise? 2. 3. Connecting Business Requirements to IT Capabilities Through Process 2. 4. Organizational Roles and Business Process III. Fundamentals of Business Process 3. 1. Business Process Terms and Concepts 3. 2. Business Process Definition 3. 3. Process Execution 3. 4. Transactions and Exception Handling 3. 5. Process Monitoring and Management 3. 6. A History of Business Process Management and Workflow Solutions IV. Applying SOA to Business Process: Service-Oriented Process 4. 1. Web Services and SOA Approaches for Process Definition and Execution 4. 2. Workflow 4. 3. Transactions 4. 4. Reliability 4. 5. Guidance on the Specifications V. Connecting the Dots: Process, Management, and Integration 5. 1. Proper Mindset for SOA: Process-Orientation 5. 2. Asynchrony and Coarse-Granularity: Enabled by Process 5. 3. Fulfilling the Requirements for Loose Coupling with Service-Oriented Management VI. Market Opportunity for Service-Oriented Process VII. Future Trends for Service-Oriented Process 7. 1. Smarter Invocation of Services 7. 2. Portals and Processes 7. 3. Enterprise Applications and Processes 7. 4. Processes and Peer-to-Peer Implementations VIII. Conclusions 8. 1. Key Notes 8. 2. Decision Points 8. 3. Figures 8. 4. Tables IX. Glossary X. Profiled Vendors.

The shift to Service Orientation affects all distributed computing 2. 2. Shifts in market segments 2. 3. The SOA Implementation Framework 2. 4. The march toward the SOAIF 2. 5. Integration: the key transitional market III. Vendor Landscape 3. 1. Core Service Orientation segments 3. 2. The role of the incumbents 3. 3. The role of On Demand IV. Market Trends 4. 1. Methodology 4. 2. Core market numbers 4. 3. SOAIF market numbers 4. 4. Who will win the SOAIF battle? V. Conclusions 5. 1. Key notes 5. 2. Decision points 5. 3. Figures 5. 4. Tables.