Connecting Cold Fusion to .NET Using Web Services - PowerPoint PPT Presentation

About This Presentation
Title:

Connecting Cold Fusion to .NET Using Web Services

Description:

Connecting Cold Fusion to .NET Using Web Services Geoff Snowman Developer Community Champion gsnowman_at_microsoft.com Connecting Cold Fusion to .NET Using Web Services ... – PowerPoint PPT presentation

Number of Views:90
Avg rating:3.0/5.0
Slides: 32
Provided by: GeoffS86
Category:

less

Transcript and Presenter's Notes

Title: Connecting Cold Fusion to .NET Using Web Services


1
Connecting Cold Fusion to .NET Using Web Services
  • Geoff Snowman
  • Developer Community Champion
  • gsnowman_at_microsoft.com

2
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

3
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 Loykhler CIO
4
.NET Microsofts Vision of a New Generation for
Application Development
5
.NET Architecture
Visual Studio .NET
Common Language Runtime
Operating System
6
Class Library Namespaces
System.Web
System.Windows.Forms
Services
UI
Design
ComponentModel
Description
HtmlControls
Discovery
WebControls
Protocols
System.Drawing
Caching
Security
Drawing2D
Printing
Configuration
SessionState
Imaging
Text
System.Data
System.Xml
OleDb
SqlClient
XSLT
Serialization
Common
SQLTypes
XPath
System
Collections
IO
Security
Runtime
InteropServices
Configuration
Net
ServiceProcess
Remoting
Diagnostics
Reflection
Text
Serialization
Globalization
Resources
Threading
7
.NET Languages (Microsoft)
  • Microsoft Visual Basic.NET
  • Microsoft C
  • Microsoft C (Managed/Unmanaged)
  • Microsoft J

8
.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

9
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

10
Demo ASP.NET
11
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

12
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

13
XML Web Services
Language Independent Platform Independent Device
Independent
  • LOB J2EE App
  • BEA Weblogic
  • Oracle 8i
  • Sun UE 10000
  • SAP R/3
  • DB2
  • Solaris
  • IBM RS/6000
  • Motorola i85s
  • J2ME

XML Web Services
  • Compaq iPAQ
  • Windows CE
  • StrongARM
  • PeopleSoft 7.0
  • SQL 2000
  • Windows 2000/.NET
  • Compaq Proliant
  • PERL
  • Apache 2.0
  • MySQL
  • Linux

14
  • 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

15
Microsoft .NET
Web services support across the Microsoft
platform
16
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
17
Cold Fusion calls .NET
18
Demo Cold Fusion calls .NET
19
.NET calls Cold Fusion
20
Demo .NET calls Cold Fusion
21
Dollar Rent A Car
22
Case Study Integrating Business Partners
  • Organization
  • One of the worlds 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

23
Solution Web Services
Network
XML/SOAP
Partner
Dollar.com Request
ASP
Web Services(SOAP Listener)(XML Parser)
XML/SOAP
MIT
ANY Internet Device
Results
Dollar.com
Dollar Reservations
  • 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!

24
Customer Feedback
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
25
The Future - GXA
  • WS-ReliableMessaging
  • WS-Addressing
  • WS-Security
  • WS-Policy
  • WS-Attachments
  • WS-Coordination
  • DIME
  • WS-Inspection
  • WS-Referral
  • WS-Routing
  • WS-Transaction
  • BPEL4WS

26
Example
lt?xml version"1.0" encoding"utf-8"?gt ltSEnvelope
xmlnsS"http//schemas.xmlsoap.org/soap/envelope
/" xmlnsxsd"http//www.w3.org/2001/XMLSche
ma" xmlnsxsi"http//www.w3.org/2001/XMLSch
ema-instance"gt ltSHeadergt ltmpath
xmlnsm"http//schemas.xmlsoap.org/rp"gt
ltmactiongthttp//tickers-r-us.org/getQuotelt/macti
ongt ltmtogtsoap//tickers-r-us.org/stockslt/m
togt ltmfromgtmailtojohnsmith_at_isps-r-us.comlt
/mfromgt ltmidgtuuid84b9f5d0-33fb-4a81-b02b
-5b760641c1d6lt/midgt lt/mpathgt
ltwssecSecurity xmlnswssec"http//schema
s.xmlsoap.org/ws/2002/04/secext"gt
ltwssecBinarySecurityToken
ValueType"wssecX509v3"
EncodingTypewssecBase64Binary"gt     
dWJzY3JpYmVyLVBlc..eFw0wMTEwMTAwMD
lt/wssecBinarySecurityTokengt
lt/wssecSecuritygt lt/SHeadergt ltSBodygt
ltappTrafficStatus xmlnsapp"http//hig
hwaymon.org/payloads"gt ltroadgt520Wlt/roadgtltsp
eedgt3MPHlt/speedgt lt/appTrafficStatusgt
lt/SBodygt lt/SEnvelopegt
Routing
Security
27
InfoPath is a Smart Client for XML Web Services
BizTalk
SQL
InfoPath
IIS
STS
ASP.NET
Oracle, DB2, SAP, PeopleSoft, Siebel,
ADO
28
What is UDDI?
  • Universal Description Discovery and Integration
    is an industry-wide project to standardize the
    discovery of web services.
  • Major vendors including Microsoft, IBM, Sun,
    Oracle and HP
  • Interoperable, cross-platform specifications
  • Publish and search
  • Based on Internet standards
  • Specs will be transitioned to a standards body.
  • Collaborate on standards, compete on
    implementations.
  • Public and Enterprise Implementations
  • UDDI Business Registry (UBR)
  • Public Internet registry operated by Microsoft
    and IBM, SAP and HP
  • Fully replicated, entirely interoperable
  • Enterprise UDDI Services in Windows Server 2003

29
Scenario Dynamic Application Configuration
Enterprise UDDI Services allows dynamic
configuration
1. Each sub registers financials web services in
enterprise UDDI
2. Financial reporting system at HQ reads UDDI to
discover each subs web service
3. Financial reporting system uses web service to
read financials
4. Financial reporting system presents
consolidated financial statement
Financial Reporting System
5. Adding a new sub requires UDDI registration
but no change in report app
30
Demo UDDI
31
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
Write a Comment
User Comments (0)
About PowerShow.com