Web services2014

on

  • 267 views

 

Statistics

Views

Total Views
267
Slideshare-icon Views on SlideShare
243
Embed Views
24

Actions

Likes
0
Downloads
1
Comments
0

2 Embeds 24

http://e-thinking.org 21
http://appescp.com 3

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Web services2014 Web services2014 Presentation Transcript

    • Web Services E-Stratégies How can you use enterprise technologies to improve organizational performance? ©2013 LHST sarl
    • Do enterprise applications make sense? Focus Improve Knowledge Leverage Mesure Organization Processes Explicit Transactions Efficiency Services Delivery Implicit Interactions Effectiveness Introduction Challenges Context Building Blocks ©2013 LHST sarl
    • The Web of Things Introduction Challenges Context Building Blocks ©2013 LHST sarl
    • The objectives of an IS Actionnaires  Actifs  Demandes en temps réel Employées  Mobilité  ...  Valorisation des tâches  ... L’organisation Clients  Fidélité ?  Vrai coûts  ... Introduction Société  Compétition  “made in” “made by”  ... Partenaires  Peu de barrières d’entrée  Acquisitions, OPA  ... Challenges Context Building Blocks ©2013 LHST sarl
    • Coengineering a vision Introduction Challenges Context Building Blocks
    • No one best way Introduction Challenges Context Building Blocks
    • Cost of current investments Introduction Challenges Context Building Blocks
    • From internal to embedded processes Traditional Enterprise 1.Multiowned Transactions 2.Single Owner 3.Personalized Interfaces 1.Normalized Transactions 2.Single-Owner 3.Generalized Interfaces 4.Applications 5.Synchronous 6.Tightly Coupled Introduction Challenges Matthew J. Dovey Business Community Context Building Blocks
    • Anything, anytime, anywhere • 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 Challenges Context Building Blocks
    • The Problem with batch operations Introduction Challenges Context Building Blocks Concerns
    • Programming the Web I. II. Des applications réelles(Pages Web dynamiques, ASP, JSP, PHP, ...) III. Les Web services (basé sur XML) The Web is Reborn Introduction Pages Web statiques (HTML) Challenges Context Building Blocks
    • Web Services Un service Web est une « unité logique applicative » accessible en utilisant les protocoles standard d’Internet ADP, pionnier du Cloud RH Web services are a are self-contained, self-describing, modular applications that can be published, located, and invoked across the Web. Introduction Challenges Context Building Blocks
    • WEB SERVICE PROVIDERS Leading Edge Forum Introduction Challenges Context Building Blocks
    • Typical Applications  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 Challenges Context Building Blocks
    • Origins 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 Challenges Context Building Blocks
    • CHARACTERISTICS • 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 Challenges Context Building Blocks
    • A DIFFERENCE IN SCOPE  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 Challenges Context Building Blocks
    • A DIFFERENCE IN CONTENT  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 Challenges Context Building Blocks
    • A DIFFERENCE IN APPROACH • 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 Challenges Context Building Blocks
    • A DIFFERENCE IN KIND  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 Source: Steward McKie Internet. 10 Rules of Web Services  Web Services are consumed and pricing is based on either a per-use basis or a periodic subscription (monthly, quarterly, annually) and not on a "number-of-users" basis. Introduction Challenges Context Building Blocks
    • A DIFFERENCE IN STRATEGY Source: Hagel and Brown Introduction Challenges Context Building Blocks
    • 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 Challenges Context Building Blocks ©2013 LHST sarl
    • The Building Blocks - THE INTERNET 500 million users more than 3 billion pages WWW URL HTML, HTTP Internet: "The Big Picture" Introduction Challenges Context Building Blocks
    • HTML <!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 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 HyperText Markup Language Home Page Introduction Challenges Context Building Blocks
    • XML <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 Challenges Context Building Blocks
    • SOAP 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 Challenges Context Building Blocks
    • SOAP EXAMPLE <soap:Envelope xmlns:soap="..."> <soap:Header> <!-- extensible headers --> </soap:Header> <soap:Body> <!-- payload --> </soap:Body> </soap:Envelope> SOAP is platform independent, and therefore enables diverse applications to communicate with one another. Ethan Cerami, Web Services Essentials Introduction Challenges Context Building Blocks
    • WSDL [WebMethod] public MortgagePayments CalculateMortgage( string amount, string years, string interest, string annIns, string annTax) { MortgagePayments p = new MortgagePayments(); ... // calculate mortgage payments here; return p; } 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. Introduction Challenges Context Building Blocks
    • UDDI The Universal Description Discovery and Integration (UDDI) is an open framework that permits businesses to share information • • • Introduction 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. Challenges Context Building Blocks
    • REST • • • • • Common HTTP verbs 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/ Introduction Challenges Context Building Blocks ©2013 LHST sarl