Transcript Microsoft`s Commitment to Integrate

Microsoft’s Commitment to
Integrate
Curtis Koppang
Managing Partner
Pharos Software
Agenda
•
•
•
•
•
Open Applications
Open Standards
Open Platform
Products Supporting Integration
Wrap-up
Open Applications
• There are three basic platforms out there
– CICS/MVS, Unix variations and Windows
• Bias’ aside there is a lot of data on each
• Guarding that data is code
• No one will agree on a single platform
– Nor should we have to, each has its strengths
• Business’ want to leverage their data, but
their data is often “locked up” in an
application
Interoperability
• The ability to share data across
heterogeneous application domains
• Relatively mature approach
• Bridging or gateway technologies
– COM -> CORBA bridges
– COMTI (SNA Gateway)
– Message Oriented Middleware (MQSeries)
– “Proprietary” interfaces (SAP et al)
– EDI variations
Integration
• The combining of different activities or
components into a functional unit
• We are talking about a rich interaction
• We need cross platform protocols
– Wire protocols
– Application protocols
• We also need new architectures
– Without changing all the existing applications
Service Oriented Architectures
• Hooking together autonomous systems
• Sending data is the easy part
• Building robust applications is harder
– Security
– Application domain differences (mapping)
– Transactions
• We are not talking about re-writing
• Expose objects/methods as loosely
coupled services/messages
Open Standards
• The Microsoft Way
• Past Microsoft Standards
– XDR and SOAP
• Future Microsoft Standards
– XLANG and GXA
Microsoft Specification Process
• The open standards process is slow
– But effective
• Microsoft’s goal is to jumpstart the process
• Develop specifications internally
– With other “interested” parties
• Turn specifications over to standards
bodies
Upside
• Small team of “plumbers”
• Focused on delivering
• Allows for earlier product releases
– Standards drive products
– Products make money
• Standards bodies do what they do best
– Let more people participate
– Work out competing interests
Downside
• Competing standards
– Seems like it’s a race - very competitive
• Initially specification group is closed
– Who’s to say who an “interested party” is?
– May contribute to some animosity
• Is early product release actually better?
– Not interoperable with anyone else
– Need a subsequent rev to adhere to final
specification
Examples
• XML Data Reduced (XDR)
– Pre-cursor to XML Schema
• Simple Object Access Protocol (SOAP)
– Web Service wire format
• XLANG
– Describes business processes and
implementation
• Global XML Architecture (GXA)
– Web Service specifications (WS-xx)
XML Data Reduced
• DTD is not valid XML
• Need something which could be
embedded in an XML document
• Microsoft introduced XDR
• Once released to W3C became XML
Schema
• XML Schema is what makes XML
interesting
Simple Object Access Protocol
• Timeframe was 1998
• No good way to remote over Internet
• Small group working on an XML remoting
protocol
– A person from each: Microsoft,
Developmentor and IBM
• W3C has already published two revisions
XLANG
• Will be deprecated by IBM on Business
Process Execution Language for Web
Services (BPEL4WS)
• Major investment in XLANG
– BizTalk Orchestration is entirely based on
XLANG
• Shows Microsoft has a major commitment
to creating standards
Global XML Architecture
• Higher level protocols for Integration
between different platforms
• Federated
• Definitions based on existing abstractions
– Infoset and SOAP
• Application Domain neutral
– Implies extensibility
Global XML Architecture
Global XML Architecture
• Security
– WS-Security, WS-Trust, WS-Privacy
Policy and WS-Authorization
• Virtual Network
– WS-Routing and WS-Referral
• Discovery
– WS-Inspection
• Transactions
– WS-Transaction and WS-Coordination
WS-
Other Standards
• In 1996, Microsoft co-authored the first draft of
Extensible Markup Language (XML).
• In March 2001, IBM and Microsoft submitted
Web Services Description Language (WSDL) to
the World Wide Web Consortium (W3C).
• Microsoft is a member of the industry initiative
developing the Universal Description, Discovery
& Integration (UDDI) specification.
Web Services
• Notice that these technologies are all
converging on Web Services
• It’s not by mistake, if we are going to share
data this is a logical place
• A great way of hooking up autonomous,
loosely coupled applications
• Today Web Services offer Interoperability
• Future standards will give us Integration
– We are building the foundation now
Demo
• Interoperability through Web Services
• Java Service
– Apache Axis
• .NET Consumer
– Microsoft .NET Framework
Open Platform
• Shared Source Common Language
Infrastructure (SSCLI)
• Windows
SSCLI
• Codenamed Rotor
• Source code for Common Language
Runtime (CLR) and much of the
Framework
• CLR minus some algorithms
– Cryptography, garbage collection, etc
• Ratified by ECMA as a standard 12/31/01
– C# - ECMA TC39/TG2
– CLI - ECMA TC39/TG3
SSCLI
• Portable architecture
– Platform Abstraction Layer (500+ functions)
– C# compiler emits x86 or ANSI C
• Statistics
– 1.9 million lines of code
– 9,700 files
– 1,300 public classes
• Useful resource for .NET Developers
SSCLI License
You may use this Software for any non-commercial
purpose, subject to the restrictions in this license. Some
purposes which can be non-commercial are teaching,
academic research, and personal experimentation. You
may also distribute this Software with books or other
teaching materials, or publish the Software on websites,
that are intended to teach the use of the Software.
You may not use or distribute this Software or any
derivative works in any form for commercial purposes.
Examples of commercial purposes would be running
business operations, licensing, leasing, or selling the
Software, or distributing the Software for use with
commercial products.
Demo
• Quick tour of the SSCLI
Windows
• Did you know that as an enterprise
customer it is possible to get the source
code to most of the Windows platforms?
– http://www.microsoft.com/licensing/sharedsource/
• Active Directory is already based on
Kerberos and DNS
• .NET Server will have a UDDI service
Products Supporting Openness
• .NET Framework
• BizTalk
• Web Services Development Kit (WSDK)
.NET Framework
• The support for Web Services in the
Framework is worth mentioning
• My experience is that - at the moment - it
is much easier to use than the Java based
frameworks
• Don’t forget this is free for download
– Get the entire Framework, C# compiler and
GUI debugger
BizTalk
• Published the architecture for BizTalk at
least a year before shipping the product
• You need infrastructure to really make
Service Oriented Architectures work
• BizTalk can provide that Framework
– Provides a compensating model for doing
long running transactions
– Provides an infrastructure for transforming
messages into a single vocabulary
Service Oriented Architecture
Backend
System
Transactions
Mapping
Validation
Security
Transport
Consumers
Service Oriented Architecture
BizTalk
Backend
System
Transactions
Mapping
Validation
Security
Transport
Consumers
Web Services Development Kit
• Initial implementation of GXA
– Just a new namespace (bunch of classes)
– WS-Security, WS-Routing, WS-Attachments
and DIME
• Currently a Microsoft “technology preview”
– It will change!
• Not broadly supported by other toolkits
– Don’t use unless own both sides of the pipe
• Gives you a definite sense of direction
Summary
• Some may say it’s the same ‘ol MS
• Maybe, but the world has changed so the
MS model has had to change as well
• Not everyone can agree on a platform
• The glue is where we need open
standards and a different architecture
• Currently we are in a grey area between
Interop and Integration
– We still need things like transactions
Links
• http://www.microsoft.com/licensing/sharedsource
• http://msdn.microsoft.com/library/default.asp?url=/library/
en-us/Dndotnet/html/mssharsourcecli.asp
• http://www.ws-i.org
• http://www.microsoft.com/biztalk