WebservicesWebservices Henrik Westergaard Hansen

Kort introduktion til Web Services

SOAP - Simple object access Protocol

WSDL – Web service description language WSDL rodelement WSDL rodelement Datatyper der transmitteres Datatyper der transmitteres Beskeder der transmitteres Beskeder der transmitteres Hvilke metoder er understøttet Hvilke metoder er understøttet Hvordan vil beskederne blive transmitteret på linien Hvordan vil beskederne blive transmitteret på linien Hvor er servicen placeret Hvor er servicen placeret

Webservices demo En kort demo af Webservices i Visual Studio 2005

Web Services Architecture ASP.NET Web Services Foundation Applications & Application Infrastructure Transports Connected Applications Management Business Process … SecurityReliabilityTransactions Messaging XML Metadata HTTPTCPSMTP …

Web Services Architecture Web Services Enhancements 2.0 Foundation Applications & Application Infrastructure Transports Connected Applications Management Business Process … SecurityReliabilityTransactions Messaging XML Metadata HTTPTCPSMTP …

Windows Communication Foundation Foundation Applications & Application Infrastructure Transports Connected Applications Management Business Process … SecurityReliabilityTransactions Messaging XML Metadata HTTPTCPSMTP …

Vejen foran os - SOA

Hvilke IT-problemer står virksomheder med i dag Meget store og komplekse arkitekturer Har måske udviklet sig over 30 år Mange forskellige teknologier Meget svært at skifte teknologi (modernisering) Kompetencer & investeringer Systemer er meget dyre at vedligeholde Kompleksitet Forretningen har svært ved at vokse hurtigt og fleksibelt nok For svært at følge nye muligheder

PolymorphismIndkapslingNedarvning Statisk genbrug Besked-baseretSkemaer+Kontrakter Binding gennem politikker Deployed service og data genbrug Interface-baseret Dynamisk loading Runtime Metadata Dynamisk genbrug Objektorientering Serviceorientering Komponentorientering 1980erne erne Serviceorientering Lidt baggrund

Service – An endpoint that reacts to messages Service Orientation – An architectural paradigm that employs the following four tenets: Boundaries are explicit Services are autonomous Services share schema and contract, not class Service compatibility is determined based on policy Service Oriented Architecture (SOA) – Any architecture the adheres to the Four Tenets of Service Orientation Services, SO, and SOA

4 principper for SOA Grænser er eksplicitte Messages sendes over eksplicitte grænser. Serviceinteraktioner er en grænse Det har omkostninger at krydse en grænse Services er autonome Der er ikke nogen kontrollerende autoritet Services er deployed, styret og versioneret individuelt En service må ikke fejle når en afhængig service fejler Services deler skema og kontrakt Services bruger skemaer for data og kontrakter for opførsel Kontrakter og skemaer burde være stabile over tid Kompatibilitet er beskrevet i policies Kompatibilitet er beskrevet i policies Egenskaber og krav er beskrevet i policies

Services interact by exchanging messages Each message exchange traverses boundaries and may have costs SO formalizes intentional, and explicit interaction Tenet 1 – Boundaries are Explicit

Services expose schemas defining data structures and contracts defining available operations Contracts and schema may be independently versioned over time Tenet 2 – Share Schema and Contract, Not Types

Policy is the statement of communication requirements necessary for service interaction Service capabilities and requirements are expressed in terms of a policy expression A policy can contain multiple assertions Tenet 3 – Policy defines Service Compatibility

Autonomy ≠ Independence Topology of a system evolves over time Unlike OO, services do not share behavior Services gracefully handle failure Tenet 4 – Services Are Autonomous

Benefits of Service Orientation Architecture & Development Reflects the new application model Loose coupling, enabling composition of new capabilities Standards-based interoperability IT Operations Topology independent Leverage heterogeneous resources Independent deployment, versioning, management Business Business agility and reduced time to market Efficiency through reuse

Services Beskedudvekslings- format beskriver Operationelle krav gennemtvinger Systemer består af Beskeder udveksler er et set af Kontrakter bundet af indeholder Skemaer definerer struktur af beskyttet af Politikker har Serviceorientering Koncepter Tilstand vedligeholder

Service CBA CBA Klient Adresse, Binding, Kontrakt A BC Adresse Hvor? Kontrakt Hvad? Binding Hvordan? Endpoint CBA

Spørgsmål ? Skriv til

Kom godt igang Software Web services – Visual Studio 2005 Windows communication Foundation, VS 2005 Beta 2 og WinFx beta 1Artikler WS-ReliableMessaging us/dnwse/html/wseandws-rm.asp A Guide to Developing and Running Connected Systems with Indigo: aspx Introducing Indigo: An Early Look us/dnlong/html/introindigov1-0.asp

Projektforslag Lav en P2P klient i WinForms eller WPF Brug WCF (Mesh), så der kan distribueres software. Systemet skal være sikkert og login skal verificeres gennem passports, måske med delegated management Link: