1. Fujitsu Computer Systems 1 Un survol des Technologies e-Business / e-Gouvernement 1. Protocoles pour e-Business / e-Gouvernement 2. Messageries e-Business 3. Transactions e-Business et Processus Business 4. Les Architectures e-Business Jacques Durand Fujitsu Computer Systems

2. Fujitsu Computer Systems 2 1. Protocoles pour e-Business / e- Gouvernement

3. Fujitsu Computer Systems 3 Protocoles de base: HTTP (hypertext transport protocol) SMTP (simple mail transfer protocol) FTP (file transfer protocol) Chacun definit: - un ensemble de commandes de base ( GET, POST … for HTTP) - un format pour envelopper des donnees (document, fichier … ) Au dessus du protocole Internet (TCP / IP): HTTP URL: http://abc.com:80/~smith/home.htmlhttp://abc.com:80/~smith/home.html SMTP: jdurand@us.fujitsu.com TCP / IP HTTP SMTP FTP

4. Fujitsu Computer Systems 4 Protocoles de base: SMTP (simple mail transfer protocol) Pour la reception Finale: IMAP POP3 Status reply

5. Fujitsu Computer Systems 5 Content-Type: multipart/related; boundary=RN-Outer-Boundary; type=application/xml Content-Description: This is the RosettaNet Business Message --RN-Outer-Boundary Content-Type: Application/XML Content-Location: RN-Preamble Content-ID: [PART 1] --RN-Outer-Boundary Content-Type: Application/XML Content-Location: RN-Delivery-Header Content-ID: [PART 2] --RN-Outer-Boundary Content-Type: Application/XML Content-Location: RN-Service-Header Content-Description: RosettaNet-Service-Header Content-ID: [PART 3] …. Part 1 (text) Part 2 (gif) Part 3 (audio) Enveloppe HTTP Ou SMTP ou… MIME (multi-purpose mail extension) Enveloppe MIME

6. Fujitsu Computer Systems 6 MIME-Version: 1.0 Content-Type: Multipart/Related; boundary=MIME_boundary; type=text/xml; start=" " Content-Description: This is the optional message description. --MIME_boundary Content-Type: text/xml; charset=UTF-8 Content-Transfer-Encoding: 8bit Content-ID:.. --MIME_boundary Content-Type: image/tiff Content-Transfer-Encoding: binary Content-ID:...binary TIFF image... --MIME_boundary-- Exemple avec MIME Part 1 = enveloppe SOAP

7. Fujitsu Computer Systems 7 Digital signature Securite du MIME: S/MIME

8. Fujitsu Computer Systems 8 POST http://partnerB.name.com/servlet/RNInBoundServlet HTTP/1.1 Content-Type: multipart/related; type=multipart/signed; boundary=RN-HTTP-Boundary; x-RN-Version: RosettaNet/V02.00 x-RN-Response-Type: async Content-Length: 18899 --RN-HTTP-Boundary Content-Type: multipart/signed; boundary=RN-Signature-Boundary; protocol=application/pkcs7-signature; micalg=sha1 Business Message --RN-Signature-Boundary [The Business Message to be signed goes here] --RN-Signature-Boundary Content-Type: Application/pkcs7-signature; … [The base64-encoded PKCS7 Detached Signature] --RN-Signature-Boundary-- --RN-HTTP-Boundary-- S/MIME over HTTP

9. Fujitsu Computer Systems 9 POST /insuranceClaims HTTP/1.1 Host: www.risky-stuff.com Content-Type: Multipart/Related; boundary=MIME_boundary; type=text/xml; start=" " Content-Length: XXXX SOAPAction: http://schemas.risky-stuff.com/Auto-Claim Content-Description: This is the optional message description. --MIME_boundary Content-Type: text/xml; charset=UTF-8 Content-Transfer-Encoding: 8bit Content-ID: <claim:insurance_claim_auto id="insurance_claim_document_id" xmlns:claim="http://schemas.risky-stuff.com/Auto-Claim"> --MIME_boundary Content-Type: image/tiff Content-Transfer-Encoding: base64 Content-ID:...Base64 encoded TIFF image... --MIME_boundary Content-Type: image/jpeg Content-Transfer-Encoding: binary Content-ID: claim061400a.jpeg@claiming-it.com...Raw JPEG image.. --MIME_boundary-- HTTP payload HTTP header Part 1 Part 2 Part 3 SOAP With Attachments

10. Fujitsu Computer Systems 10 SOAP: Simple Object Access protocol - Structure du message: une envelope XML independante du niveau transport: SOAP header SOAP body TCP / IP HTTP SMTP SOAP SOAP avec Attachements (MIME)

11. Fujitsu Computer Systems 11 SOAP: Une plateforme protocolaire pour des extensions modulaires (ajouts de fonctions de securité, fiabilite, correlation/addressage, etc.) (SOAP extensions header blocks) Les deux facettes de SOAP - mode RPC : message = invocation de procedure - mode document : message = envelope pour doc. SOAP SOAP avec Attachements (MIME) SécuritéFiabilité Corrélation adressage

12. Fujitsu Computer Systems 12 … <claim:insurance_claim_auto id="insurance_claim_document_id" xmlns:claim="http://schemas.risky-stuff.com/Auto-Claim"> SOAP header For ebMS3 SOAP header For WS-Sec Payload of The message SOAP envelope

13. Fujitsu Computer Systems 13 Extensions SOAP Un mecanisme d extensions modulaires: header blocks dans the SOAP Header Toutes les specs Web services de niveau protocole utilisent ce mecanisme WS-Security WS-Reliability / WS-ReliableMessaging WS-Addressing WS-SecureConversation ….

14. Fujitsu Computer Systems 14 Une alternative à SOAP: REST (Representational State Transfer) - HTTP seulement - davantage un style qu un protocole bien defini - pas d enveloppe XML structuree comme SOAP - moins complexe, mais plus limité (sécurité, robustesse) TCP / IP HTTP SMTP SOAP REST