©2013 LHST sarl

Web Services

E-StratégiesHow 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 Context Building Blocks

Challenges

©2013 LHST sarl

The Web of Things

Introduction Context Building Blocks

Challenges

©2013 LHST sarl

The objectives of an IS

Actifs Demandes en temps

réel ...

Actionnaires

Compétition “made in” “made by” ...

Société

Peu de barrières d’entrée Acquisitions, OPA ...

Partenaires Fidélité ? Vrai coûts ...

Clients

L’organisationL’organisation

Mobilité Valorisation des tâches ...

Employées

Introduction Context Building Blocks

Challenges

Coengineering a vision

Introduction Context Building Blocks

Challenges

No one best way

Introduction Context Building Blocks

Challenges

Cost of current investments

Introduction Context Building Blocks

Challenges

From internal to embedded processes

Traditional EnterpriseTraditional Enterprise

1. Normalized Transactions2. Single-Owner3. Generalized Interfaces4. Applications5. Synchronous6. Tightly Coupled

1. Multiowned Transactions

2. Single Owner3. Personalized

Interfaces

Business CommunityBusiness

Community

Matthew J. Dovey

Introduction Context Building Blocks

Challenges

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 Context Building Blocks

Challenges

The Problem with batch operations

Introduction Context Building Blocks

Challenges Concerns

Programming the Web

I. Pages Web statiques (HTML)

II. Des applications réelles(Pages Web dynamiques, ASP, JSP, PHP, ...)

III. Les Web services (basé sur XML)

The Web is Reborn

Introduction Context Building Blocks

Challenges

Web Services

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

WEB SERVICE PROVIDERS

Leading Edge Forum

Introduction Context Building Blocks

Challenges

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/Service/Currency-Converter.htm http://www.ecubicle.net/driving.asmx?op=GetDirections http://www.postalmethods.com/

Introduction Context Building Blocks

Challenges

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 Context Building Blocks

Challenges

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 Context Building Blocks

Challenges

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 Context Building Blocks

Challenges

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 Context Building Blocks

Challenges

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 Context Building Blocks

Challenges

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

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.

Source: Steward McKie10 Rules of Web Services

Introduction Context Building Blocks

Challenges

A DIFFERENCE IN STRATEGY

Source: Hagel and Brown

Introduction Context Building Blocks

Challenges

©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

The Building Blocks - THE INTERNET

Internet: "The Big Picture"  URL HTML, HTTP

WWW

500 million usersmore than 3 billion pages

Introduction Context Building Blocks

Challenges

HTML

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

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 Context Building Blocks

Challenges

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 Context Building Blocks

Challenges

SOAP EXAMPLE

<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

WSDL

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

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

Introduction Context Building Blocks

Challenges

©2013 LHST sarl

REST

•  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