E strat web services2014

352 views
269 views

Published on

Published in: Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
352
On SlideShare
0
From Embeds
0
Number of Embeds
16
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • XML - Allows the delivery of messages and transfer of data through a series of standard tags; the World Wide Web Consortium released the first version in October 1998
    SOAP - Calls and invokes Web services through HTTP; the W3C last month issued a draft for the next version of SOAP
    WSDL - Describes the function and format of a Web service; proposed to the W3C in March by IBM, Microsoft and 23 other companies
    UDDI Lists available Web services and their locations either on a public directory server or one within an organization; started by IBM, Microsoft and Ariba last September; second version released in June
  • XML - Allows the delivery of messages and transfer of data through a series of standard tags; the World Wide Web Consortium released the first version in October 1998
    SOAP - Calls and invokes Web services through HTTP; the W3C last month issued a draft for the next version of SOAP
    WSDL - Describes the function and format of a Web service; proposed to the W3C in March by IBM, Microsoft and 23 other companies
    UDDI Lists available Web services and their locations either on a public directory server or one within an organization; started by IBM, Microsoft and Ariba last September; second version released in June
  • XML - Allows the delivery of messages and transfer of data through a series of standard tags; the World Wide Web Consortium released the first version in October 1998
    SOAP - Calls and invokes Web services through HTTP; the W3C last month issued a draft for the next version of SOAP
    WSDL - Describes the function and format of a Web service; proposed to the W3C in March by IBM, Microsoft and 23 other companies
    UDDI Lists available Web services and their locations either on a public directory server or one within an organization; started by IBM, Microsoft and Ariba last September; second version released in June
  • XML offers standardized approach to data description, ability to create compact documents, and wide availability of software tools for creating and processing documents.

    Langage XML : Décrit les informations

    Protocole SOAP : Exécute les services à distance

    Langage WSDL : Décrit l’ interface des services

    Norme UDDI : Trouve les services dont on a besoin
  • User Services - these are the services that most users would use along with Internet Access. (These may be hosted within a large corporate LAN) (Webhosting is discussed under the online content section) 
    Domain Name Server - BIND, DNS Resources Directory.
    Email Host -,Sendmail ,Microsoft Exchange 
    Usenet Newsgroups (NNTP) - INN,
    Special services such as quake, telnet, FTP
    User Web Hosting - See the online content section for details.
    These servers require fast interfaces and large/fast storage.

    The web is organized around URIs, HTML, and HTTP.
    URIs provide defined ids to refer to elements on the web,
    HTML provides a standardized way to describe document structures (allowing browsers to render information for the human reader), and
    HTTP defines a protocol to retrieve information from the web.

  • XML offers standardized approach to data description, ability to create compact documents, and wide availability of software tools for creating and processing documents.

    Langage XML : Décrit les informations

    Protocole SOAP : Exécute les services à distance

    Langage WSDL : Décrit l’ interface des services

    Norme UDDI : Trouve les services dont on a besoin
  • Structure d'un message SOAP :

    une enveloppe qui définit la structure du message
    Élément racine
    Namespace

    un en-tête (optionnel) qui contient les informations d'en-tête (autorisations et transactions par exemple),

    un corps contenant les informations sur l'appel et la réponse

    une gestion d'erreur qui identifie la condition d'erreur

    des attachements (optionnel)

  • WSDL est un langage qui permet de
    décrire:
    un service Web,
    et comment l’ invoquer

    Objectif :

    Décrire les services comme un ensemble d’opérations et de messages abstraits relié à des protocoles et des serveurs réseaux

    Permet de décharger les utilisateurs des détails techniques de réalisation d’un appel

    WSDL est un langage qui standardise les schémas XML utilisés pour établir une connexion entre émetteurs et récepteurs.
  • Annuaire mondial d'entreprises basé sur le Web

    Il permet d'automatiser les communications entre prestataires, clients, etc..

    Très orienté « affaires » (vente, prestation)

    Accessible grâce à SOAP

    Intégrant toutes sortes d'entrées (nom, carte d'identité des sociétés, description des produits et des services, etc.),
  • E strat web services2014

    1. 1. ©2013 LHST sarl Web Services Prof. Lee SCHLENKER E-Stratégies Nov 5th 2015 How can you use enterprise technologies to improve apprenticeship?
    2. 2. ©2013 LHST sarl Focus Improve Knowledge Leverage Mesure Organization Processes Explicit Transactions Efficiency Services Delivery Implicit Interactions Effectiveness Introduction Context Building Blocks Challenges
    3. 3. ©2013 LHST sarl Introduction Context Building Blocks Challenges
    4. 4. Introduction Context Building Blocks Challenges
    5. 5. ©2013 LHST sarl Introduction Context Building Blocks Challenges
    6. 6. ©2013 LHST sarl Introduction Context Building Blocks Challenges
    7. 7. Traditional Enterprise 1.Normalized Transactions 2.Single-Owner 3.Generalized Interfaces 4.Applications 5.Synchronous 6.Tightly Coupled 1.Multiowned Transactions 2.Single Owner 3.Personalized Interfaces Business Community Matthew J. Dovey Introduction Context Building Blocks Challenges
    8. 8.  The key objective of the organization is to cater to maximal agility: provide anything, anytime, anywhere, anyhow.  Such organizations are using the maximal capabilities of both technology and humans to meet this objective.  Technologies role is the accumulation, sharing and communication of information through out a business community to permit better decision making.  In taking informed decisions a business community can build business value. Introduction Context Building Blocks Challenges
    9. 9. Introduction Context Building Blocks Challenges Concerns
    10. 10.  Pages Web statiques (HTML)  Des applications réelles(Pages Web dynamiques, ASP, JSP, PHP, ...)  Les Web services (basé sur XML) The Web is Reborn Introduction Context Building Blocks Challenges
    11. 11. Web services are a are self-contained, self-describing, modular applications that can be published, located, and invoked across the Web. Un service Web est une « unité logique applicative » accessible en utilisant les protocoles standard d’Internet Introduction Context Building Blocks Challenges ADP, pionnier du Cloud RH
    12. 12. Leading Edge Forum Introduction Context Building Blocks Challenges
    13. 13.  Consumer, device, business, or system oriented Examples http://www.aswinanand.com/2008/07/send-free-sms-web-service/ http://www.webserviceshare.com/Business/Financial/Currency/S ervice/Currency-Converter.htm http://www.ecubicle.net/driving.asmx?op=GetDirections http://www.postalmethods.com/ Introduction Context Building Blocks Challenges
    14. 14. A short history of Web Services Hewlett-Packard's e-Speak in 1999 Microsoft introduced the name "web services" in June 2000 MS "bet the company" on its web services strategy now every major vendor is a player  http://www.w3.org/ Introduction Context Building Blocks Challenges
    15. 15. • A Web service is a remote procedure protocol (RPC) over the Internet that uses a standardized XML messaging system. • A Web service has a public interface, defined in a common XML grammar that describes all the methods available to clients. • Web services possess a simple mechanism for interested parties to locate the service and locate its public interface. Ethan Cerami, Web Services Essentials Introduction Context Building Blocks Challenges
    16. 16.  Orchestration : the ability to map information flows to client needs  Appropriation : the ability to convince the different clients to use the Internet in a business context  Enrichment : the ability to help clients use the services to produce value  Collaboration : the ability of teams to work together to solve client problems Introduction Context Building Blocks Challenges
    17. 17.  Data : information in relation to context  Utilities : computer applications that cover specific business tasks (word processing, spreadsheets, etc.)  Services : business models that meet specific client needs Introduction Context Building Blocks Challenges
    18. 18. • Extend rather than replace your system • Start at the edge rather than in the middle • Focus on process rather than function • Talk business rather than technology Source: Hagel and Brown Introduction Context Building Blocks Challenges
    19. 19.  The only technology a Web Service needs is an Internet connection, preferably broadband, a Web browser and possibly an email account.  A Web Service does not require any local software to be installed to make it function  A Web Service can be accessed manually via a service provider's portal or programmatically via an application programming interface (API)  A Web Service is provided by an WSP who develops the service and delivers it either directly to service consumers or via an intermediary service broker hub over the Internet. Source: Steward McKie 10 Rules of Web ServicesIntroduction Context Building Blocks Challenges
    20. 20. Source: Hagel and Brown Introduction Context Building Blocks Challenges
    21. 21. ©2013 LHST sarl The Next Revolution in Interactions •Comment définir la notion d'interaction ? •Quels arguments les auteurs avancent-ils pour distinguer entre la valeur ajoutée liée à la transformation des matières premières et celle liée aux "transactions" et aux "interactions" ? •Les auteurs font référence aux concepts de la complexité et des interactions tacites ? De quoi s'agit-il exactement ? •L'article suggère que les applications d'entreprise devraient constituer des aides à la prise de décision. Cet objectif est-il réaliste ? •Quelles pistes nous permettront de faire évoluer les applications d'entreprise pour soutenir le travail tacite ? Introduction Context Building Blocks Challenges
    22. 22. Internet: "The Big Picture" URL HTML, HTTP WWW 500 million users more than 3 billion pages Introduction Context Building Blocks Challenges
    23. 23. HTML is the lingua franca for publishing hypertext on the World Wide Web. It is a non-proprietary format that uses tags such as <h1> and </h1> to structure text into headings, paragraphs, lists, hypertext links etc <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HEAD><TITLE>HTML Home Page</TITLE> <META http-equiv=Content-Type content="text/html; charset=utf-8"><LINK href="HTML Home Page_fichiers/markup.css" type=text/css rel=stylesheet> </HEAD> <BODY> <P class=banner><A href="http://www.w3.org/"><IMG height=48 alt=W3C src="HTML Home Page_fichiers/w3c_home" width=72></A> <A href="http://www.w3.org/DF/"><IMG height=48 HyperText Markup Language Home Page Introduction Context Building Blocks Challenges
    24. 24. <m:CalculateMortgageResponse xmlns:m="http://example.org/mortgage"> <MortgagePayments> <MonthlyPI>733.76</MonthlyPI> <MonthlyTax>83.33</MonthlyTax> <MonthlyInsurance>25</MonthlyInsurance> <MonthlyTotal>842.09</MonthlyTotal> </MortgagePayments> </m:CalculateMortgageResponse> XML documents describe the content of a transaction rather than the format of a page. There are six kinds of XML markup : elements, entity references, comments, processing instructions, marked sections, and document type declarations. What is XML? Introduction Context Building Blocks Challenges
    25. 25. The Simple Object Access Protocol permits the exchange of documents written in XML over the Web SOAP is compatible with existing Web servers and can work through Firewalls, SOAP are not persistent, and can be reinitialized easily if the network breaks down The latest version of SOAP Version 1.2, was published in April 2007 The W3C proposes an on-line tutorial on SOAP at http://www.w3schools.com/soap/default.asp Introduction Context Building Blocks Challenges
    26. 26. <soap:Envelope xmlns:soap="..."> <soap:Header> <!-- extensible headers --> </soap:Header> <soap:Body> <!-- payload --> </soap:Body> </soap:Envelope> Ethan Cerami, Web Services Essentials SOAP is platform independent, and therefore enables diverse applications to communicate with one another. Introduction Context Building Blocks Challenges
    27. 27. Web Services Development Language is an XML grammar for specifying a public interface for a Web service. This public interface can include the following: •Information on all publicly available functions. •Binding information about the specific transport protocol to be used. •Address information for locating the specified service. The version 2.0 of WSDL has been submitted to the W3C. See this W3C page for the latest draft. [WebMethod] public MortgagePayments CalculateMortgage( string amount, string years, string interest, string annIns, string annTax) { MortgagePayments p = new MortgagePayments(); ... // calculate mortgage payments here; return p; } Introduction Context Building Blocks Challenges
    28. 28. UDDI The Universal Description Discovery and Integration (UDDI) is an open framework that permits businesses to share information • White Pages: This includes general information about a specific company. For example, business name, business description, and address. • Yellow Pages: This includes general classification data for either the company or the service offered. For example, this data may include industry, product, or geographic codes based on standard taxonomies. • Green Pages: This includes technical information about a Web service. Generally, this includes a pointer to an external specification, and an address for invoking the Web service. http://www.uddi.orgIntroduction Context Building Blocks Challenges
    29. 29. ©2013 LHST sarl • Representational State Transfer- a stateless, client-server, cacheable communications protocol; • REST is an architecture style for designing networked applications; • With SOAP, you're using an envelope; with REST, it's a postcard • RESTful applications use HTTP requests to post data (create and/or update), read data (e.g., make queries), and delete data. • REST requests rarely use XML, REST services might use XML in their responses http://mbaron.developpez.com/soa/rest/ Common HTTP verbs Introduction Context Building Blocks Challenges

    ×