1. 1 “Indigo” & Web Services Roadmap David Gristwood

2. 2 Web Services Roadmap Indigo will supersede existing connected systems technologies Other technologies continue to co-exist, interoperate and be supported via support policy Indigo ASMX Enterprise Services.NET Remoting Com(+) MSMQ ASMX WSE1 WSE2 WSE-n

3. 3 Indigo Indigo And Unification ASMX and WSE.NET Remoting Enterprise Services Simple Config Interoperable Service-Oriented Attributes Transactions Components Broad Vision Extensibility Object-Oriented System.Messaging Indigo is a superset of the capabilities of our existing stacks Queuing Reliable Msg Durable Msg

4. 4 Don Box’s 5 Minute Challenge Today someone challenged me to explain Indigo in five minutes. Here goes:. Indigo connects software together using structural contracts (a.k.a. schemas) and behavioural contracts (a.k.a. message exchange patterns). We integrate with the CLR and COM and eviscerate your local types into either data contracts or service contracts, but never both. An especially cool feature of Indigo is that the sender and receiver don't need to share the same CLR types (nor do both sides even need to be Indigo or CLR or COM). The messages we use in Indigo are based on the SOAP processing/data model but don't use angle brackets unless we are forced to, and when forced to, we do it happily and pretty damn fast. We support a variety of message transports and support both transport-level and SOAP-level security and reliability. Oh yeah, and we integrate tightly with System.Transactions and a queuing system. There. That took me less than five minutes and I type much slower than I speak. Maybe I'm jaded, but I'm sceptical of technologies whose core concepts can't be explained crisply in five minutes or less.

5. 5 Service Orientation Required Capabilities - provided by BizTalk - provided by Windows - provided by Indigo SOA Tenets SecurityReliabilityTransactionsDiscovery Transport Independence InteroperabilityManagement Process Orchestration

6. 6 Indigo Architecture Detail Messaging Services Application Queuing Routing Eventing Discovery Service Model Instance Manager Context Manager Type Integration Data Contract Data Contract Declarative Behaviors Transacted Methods Messaging Transport Channels (IPC, HTTP, TCP…) Channels (Datagram, Reliable, Peer, …) Policy Engine Policy Engine Message Encoder Message Encoder Channel Security Channel Security Hosting Environments ASP.NET Avalon.exe NT Service COM+

7. 7 Indigo Capabilities Interoperability Transports HTTP XML XML, XSD, XPath Messaging SOAP, WS-Addressing, WS-Eventing Security WS-Security WS-Trust WS-Federation Reliability WS-Reliable Messaging Transactions WS-Transactions WS-Coordination Metadata WSDL, WS-Policy, WS-Discovery

8. 8 Call to Action Start Web service pilot projects on.NET Get smart about the technologies and standards Influence the future - Participate in the Workshop process Recognize the risks associated with overlooking the benefits of this technology are far greater than the early adoption risks Evaluate the impact of Web services on your company and develop a roadmap

9. 9 (Call to Action) XML schematize your world Plan on a Web services backbone Design for reuse and change: create reusable corporate IT assets Build Web services skills Join and participate in WS-I

10. 10 Resources Download WSE from: http://msdn.microsoft.com/webservices Read case studies at: http://www.microsoft.com/casestudies Learn more about Web Services at: http://msdn.microsoft.com/webservices Participate in the Workshop Process: http://msdn.microsoft.com/webservices/community/workshops Search for each specification by name at: http://msdn.microsoft.com/webservices/understanding/specs WS-I http://www.ws-i.org

11. 11 Questions?

12. 12 © 2004 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS SUMMARY.