Enterprise Application Integration – Web Collaboration and Standardisation Enterprise Application Integration – Web Collaboration and Standardisation

Trends of Web collaborations‘ technologies Evolution of Web tech. Various markup languages Distributed network and API

Evolution of Web technology DOM (object Oriented) MarkUp Script JavaScript JSP PHP SGML (Cost & Diff.) HTML DHTML HTML4.0 XML XHTML HTML5 BOM (object Oriented) CSS Data Modeling Design

Cascading Style Sheet (CSS) Support from Style Sheet function There are three ways of inserting a style sheet: –External style sheet –Internal style sheet –Inline style To handle massive and a number of images for e-business web site.

CSS Image sprite.home { width:46px; height:44px; background:url(img_navsprite s.gif) 0 0; }.next { width:43px; height:44px; background:url(img_navsprites.gif) -91px 0; }

CSS Image Sprite

More Extensions for Visual Library Open source for visualisation –provide various types of business charts –Free libraries, Various dynamic graphs

Markup Languages SGML (Standard Generalized ML) HTML (Hyper Text ML) SHTML (Secured HTML) XML (Extensible ML) XHTML (Extensible HTML) MathML CML (Chemical ML) BSML (Bioinformatic Sequence ML) ebXMl (Electronic Business ML) …etc

9 –Mid -1990s : Network –Late 1990s: XML Standardization Changing Trends A Unix B 200x Network D Linux DB HTTP CGI WWW HTTP XML Standards A (Unix) MS-SQL C (Linux) Informix B (MS200x) Oracle D (AIX) IBM-DB2

XML DOM The XML DOM is: A standard object model for XML A standard programming interface for XML Platform- and language-independent A W3C standard

XML DOM "The W3C Document Object Model (DOM) is a platform and language-neutral interface that allows programs and scripts to dynamically access and update the content, structure, and style of a document." The DOM is separated into 3 different parts / levels: Core DOM - standard model for any structured document XML DOM - standard model for XML documents HTML DOM - standard model for HTML documents

XML DOM Structure

Methods for XML DOM methoddescription String getNodeName()Return node name String getNodeValue()Return node value getElementsByTagName() Return tag name short getNodeType()Return node type NamedNodeMap getAttributes()Return node attribute Document getOwnerDocument()Return owner document of the current node

XML DOM

XML DOM with JavaScript function loadXMLDoc(dname) { if (window.XMLHttpRequest) { xhttp=new XMLHttpRequest(); } else { xhttp=new ActiveXObject("Microsoft.XMLHTT P"); } xhttp.open("GET",dname,false); xhttp.send(); return xhttp.responseXML; } xmlDoc=loadXMLDoc("books.xml"); document.write(xmlDoc.getElementsByTagNa me("title")[1].childNodes[0].nodeValue + " "); document.write(xmlDoc.getElementsByTagNa me("author")[0].childNodes[0].nodeValue + " "); document.write(xmlDoc.getElementsByTagNa me("year")[0].childNodes[0].nodeValue);

Simple Object Access Protocol(SOAP) XML based communication tool(protocol) –A way for a program running in one kind of OS to communicate with a progamme in the same or another kind of an OS Designed as an object-access protocol in 1998 by MS engineers but currently maintained by the XML Protocol Working Group. After SOAP was first introduced, it became the underlying layer of Web Services Description Language (WSDL) Cf. SOA:Service-oriented architecture

Service Broker SOAP Message Exchange with WSDL and Service Consumer Service Provider http transport SOAP message WSDL describing service SOAP message http transport client service registry find publish DESCRIBE INVOKE SOAP SenderSOAP Receiver SOAP Sender SOAP Receiver

SOAP Body SOAP Message SOAP header SOAP envelope Header block Header data Header data Header data Body child element

SOAP Building Blocks A SOAP message is an XML document with the following elements –A required envelope Identifies XML document as a SOAP message –An optional header Contains header information –A required body element with call and response information –An optional fault element Information about errors that could occur

SOAP -example POST /InStock HTTP/1.1 Host: Content-Type: application/soap+xml; charset=utf-8 Content-Length: 299 SOAPAction: " IBM

Web Services Description Language Provides a model and an XML format for the “contract” of a web service Separates abstract service description from both concrete network protocol and message format Describes data types used in messages Messages are defined as aggregation of typed parts Operations are message exchange patterns supported by the web service PortTypes are named collections of operations

WSDL Specification types message operation porttype operation binding service port

WSDL: More Basics Define services as collections of network endpoints or ports Messages are abstract descriptions of data being exchanged Port types are abstraction collection of operations Concrete protocol and data format specification for a particular porttype constitutes a binding