connecting cold fusion to.net using web services geoff snowman developer community champion...

26
Connecting Cold Fusion to .NET Using Web Services Geoff Snowman Developer Community Champion [email protected]

Upload: annis-wade

Post on 12-Jan-2016

214 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Connecting Cold Fusion to.NET Using Web Services Geoff Snowman Developer Community Champion gsnowman@microsoft.com

Connecting Cold Fusion to .NET Using Web Services

Geoff Snowman

Developer Community Champion

[email protected]

Page 2: Connecting Cold Fusion to.NET Using Web Services Geoff Snowman Developer Community Champion gsnowman@microsoft.com

Connecting Cold Fusion to .NET Using Web Services

• What is .NET?– ASP.NET Demo

• Web Services– Cold Fusion/.NET Interop Demo

• UDDI– Dynamic UDDI Demo

• Q & A

Page 3: Connecting Cold Fusion to.NET Using Web Services Geoff Snowman Developer Community Champion gsnowman@microsoft.com

The Customer Perspective

“To remain ahead in this industry, you have to constantly deliver new solutions that continue to add value…

We needed a platform that not only enabled rapid time-to-market… but one that would increase our ability to continually add new products and services.

We chose the Microsoft platform…”

Bella LoykhlerBella LoykhlerCIOCIO

Page 4: Connecting Cold Fusion to.NET Using Web Services Geoff Snowman Developer Community Champion gsnowman@microsoft.com

.NET – Microsoft’s Vision of a New Generation for Application

Development

Page 5: Connecting Cold Fusion to.NET Using Web Services Geoff Snowman Developer Community Champion gsnowman@microsoft.com

.NET Architecture

Operating SystemOperating System

Common Language RuntimeCommon Language Runtime

Base Class LibraryBase Class Library

ADO .NET and XMLADO .NET and XML

ASP .NETASP .NETWeb Forms Web ServicesWeb Forms Web ServicesMobile Web ApplicationsMobile Web Applications

WindowsWindowsFormsForms

Common Language SpecificationCommon Language Specification

VBVB C++C++ C#C# J#J# ……V

isua

l Stu

dio

.NE

TV

isua

l Stu

dio

.NE

T

Page 6: Connecting Cold Fusion to.NET Using Web Services Geoff Snowman Developer Community Champion gsnowman@microsoft.com

Class Library Namespaces

System System

System.DataSystem.Data System.XmlSystem.Xml

System.WebSystem.Web

GlobalizationGlobalization

DiagnosticsDiagnostics

ConfigurationConfiguration

CollectionsCollections

ResourcesResources

ReflectionReflection

NetNet

IOIO

ThreadingThreading

TextText

ServiceProcessServiceProcess

SecuritySecurity

CommonCommon

OleDbOleDb

SQLTypesSQLTypes

SqlClientSqlClient

XPathXPath

XSLTXSLT

RuntimeRuntimeInteropServicesInteropServices

RemotingRemoting

SerializationSerialization

SerializationSerialization

ConfigurationConfiguration SessionStateSessionState

CachingCaching SecuritySecurity

ServicesServicesDescriptionDescription

DiscoveryDiscovery

ProtocolsProtocols

UIUIHtmlControlsHtmlControls

WebControlsWebControls

System.DrawingSystem.Drawing

ImagingImaging

Drawing2DDrawing2D

TextText

PrintingPrinting

System.Windows.FormsSystem.Windows.Forms

DesignDesign ComponentModelComponentModel

Page 7: Connecting Cold Fusion to.NET Using Web Services Geoff Snowman Developer Community Champion gsnowman@microsoft.com

.NET Languages (Microsoft)

• Microsoft: Visual Basic.NET• Microsoft: C#• Microsoft: C++ (Managed/Unmanaged)• Microsoft: J#

Page 8: Connecting Cold Fusion to.NET Using Web Services Geoff Snowman Developer Community Champion gsnowman@microsoft.com

.NET Languages (Others)

• APL• Fujitsu COBOL• Micro Focus COBOL• Eiffel• Forth• FORTRAN 95• Haskell• Mercury• Mondrian

• Oberon• Pascal• Perl• Python• RPG• S#• Scheme• Standard Meta Language

Page 9: Connecting Cold Fusion to.NET Using Web Services Geoff Snowman Developer Community Champion gsnowman@microsoft.com

Server Controls• Programmable, server-side objects

– Properties, methods and events

• Encapsulate both behavior and rendering– HTML, XML, WML, script, etc.

• You can create server controls– Custom controls– User controls– Or derive from existing controls

Page 10: Connecting Cold Fusion to.NET Using Web Services Geoff Snowman Developer Community Champion gsnowman@microsoft.com

Demo:

ASP.NET

Page 11: Connecting Cold Fusion to.NET Using Web Services Geoff Snowman Developer Community Champion gsnowman@microsoft.com

XML Web Services Explained

• Internet connects entities together

• Email and WWW inherently cross boundaries

• XML Web Services applies the same platform neutral approach to system integration– Platform Neutral– Leverage Existing

Standards– No Rip and Replace

E-mail

ConnectsPeople

WWW

ConnectsPeople to

Information

Web Services

ConnectsApplications

Page 12: Connecting Cold Fusion to.NET Using Web Services Geoff Snowman Developer Community Champion gsnowman@microsoft.com

XML Web ServicesFoundation for Programmable Internet

• Based on public standards

– XML, XSD, WSDL, SOAP, UDDI

• Not bound to any single platform

• Protocol and format-based contract

• Loosely coupled programming

• Preserve and connect existing systems

• Broad industry support

Page 13: Connecting Cold Fusion to.NET Using Web Services Geoff Snowman Developer Community Champion gsnowman@microsoft.com

XML Web Services

XML Web Services

LOB J2EE AppLOB J2EE App BEA WeblogicBEA Weblogic Oracle 8iOracle 8i Sun UE 10000Sun UE 10000

SAP R/3SAP R/3 DB2DB2 SolarisSolaris IBM RS/6000IBM RS/6000

PERLPERL Apache 2.0Apache 2.0 MySQLMySQL LinuxLinux

Language IndependentPlatform Independent

Device Independent

Motorola i85sMotorola i85s J2MEJ2ME

Compaq iPAQCompaq iPAQ Windows CEWindows CE StrongARMStrongARM PeopleSoft 7.0PeopleSoft 7.0

SQL 2000SQL 2000 Windows 2000/.NETWindows 2000/.NET Compaq ProliantCompaq Proliant

Page 14: Connecting Cold Fusion to.NET Using Web Services Geoff Snowman Developer Community Champion gsnowman@microsoft.com

• Promoters group for Web services– Facilitate customer adoption– Ensure interoperability – Not a standards body

• Industry alignment around Web services– First testing tools this year

• More info: http://www.ws-i.org

Page 15: Connecting Cold Fusion to.NET Using Web Services Geoff Snowman Developer Community Champion gsnowman@microsoft.com

Microsoft .NETWeb services support across the Microsoft platform Web services support across the Microsoft platform

To

ols

To

ols

ClientsClients

ServicesServices

ServersServers

Ex

pe

rien

ces

E

xp

erie

nce

s

& S

olu

tion

s&

So

lutio

ns

Page 16: Connecting Cold Fusion to.NET Using Web Services Geoff Snowman Developer Community Champion gsnowman@microsoft.com

Analyst Perspective On .NET“.NET is a brilliant strategy that enables Microsoft to define the next shift in the software business.” Gartner Group

“Everyone should build on the XML/SOAP foundation.”

Meta Group

“Gartner believes Microsoft is now providing more vision and influence regarding this shift than any other vendor.”

Gartner Group

“.NET is a leading example of what we believe will be the dominant architectural model for the third generation of Internet applications.”

Patricia Seybold Group

Completeness of VisionCompleteness of Vision

HPHPOracleOracle

*Source: Gartner Research, 9/13/2001*Source: Gartner Research, 9/13/2001

Gartner Web Services Gartner Web Services Magic QuadrantMagic Quadrant

Ab

i li t

y t

o E

xecu

t eA

bi l

i ty

to

Exe

cut e

IBMIBM

SunSun

Page 17: Connecting Cold Fusion to.NET Using Web Services Geoff Snowman Developer Community Champion gsnowman@microsoft.com

Demo:

A Simple Web Service

Page 18: Connecting Cold Fusion to.NET Using Web Services Geoff Snowman Developer Community Champion gsnowman@microsoft.com

Cold Fusion calls .NET

Page 19: Connecting Cold Fusion to.NET Using Web Services Geoff Snowman Developer Community Champion gsnowman@microsoft.com

Demo:

Cold Fusion calls .NET

Page 20: Connecting Cold Fusion to.NET Using Web Services Geoff Snowman Developer Community Champion gsnowman@microsoft.com

.NET calls Cold Fusion

Page 21: Connecting Cold Fusion to.NET Using Web Services Geoff Snowman Developer Community Champion gsnowman@microsoft.com

Demo:

.NET calls Cold Fusion

Page 22: Connecting Cold Fusion to.NET Using Web Services Geoff Snowman Developer Community Champion gsnowman@microsoft.com

Dollar Rent A CarDollar Rent A Car

Page 23: Connecting Cold Fusion to.NET Using Web Services Geoff Snowman Developer Community Champion gsnowman@microsoft.com

Case Study: Integrating Business Partners

Organization• One of the world’s largest car rental agencies

• More than 400 locations in 26 countries

Business challenges• Cost of acquiring new customers too high

• Needed to connect with diverse set of business partners to grow business– Online travel sites, airlines, hotels, travel agents, Web site

Page 24: Connecting Cold Fusion to.NET Using Web Services Geoff Snowman Developer Community Champion gsnowman@microsoft.com

Solution – Web Services

Dollar cost-effectively opened up another sales channel that has provided thousands of new reservations per year, equating to millions of dollars in additional revenue

Partner connection richer, deeper and more dynamic – live with 25 partners in 2 months!

Results

PartnerPartner

Dollar.com Dollar.com RequestRequest

ANY ANY Internet Internet DeviceDevice

NetworkNetwork XML/SOAP

ASPASP

MMIITT

XML/SOAP

Web ServicesWeb Services(SOAP Listener)(SOAP Listener)

++(XML Parser)(XML Parser)

Dollar.comDollar.com Dollar Dollar ReservationsReservations

Page 25: Connecting Cold Fusion to.NET Using Web Services Geoff Snowman Developer Community Champion gsnowman@microsoft.com

“We knew exposing our reservation system as a Web service would provide a standard interface that could be used by a wide range of other applications, both internal and external. However, at the time, we had no idea just how often we would use it, or the magnitude of the benefits it would deliver.”

– Peter Osbourne, Group Manager, Advanced Technology Group

Customer Feedback

Page 26: Connecting Cold Fusion to.NET Using Web Services Geoff Snowman Developer Community Champion gsnowman@microsoft.com

Summary: Enterprise Application Integration

• Yesterday: Hardwired endpoints built with proprietary messaging frameworks

– Point to Point

– Difficult, Expensive

– Not business context driven

• Today: Loosely coupled endpoints built on standard messaging framework

– End to End

– Easier, Lower Cost

– Business context driven