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
BOM
(object
(object
Oriented) Oriented)
1986
SGML
MarkUp
(Cost &
Diff.)
1991
1994
1998
Data Modeling
XML
Script
JavaScript
JSP
PHP
Design
HTML
2000
DHTML
HTML4.0
CSS
XHTML
HTML5
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
<html>
<head>
<style type="text/css">
.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;
}
</style>
</head>
<body>
<div class="home"></div>
<br /><br />
<div class="next"></div>
</body>
</html>
CSS Image Sprite
More Extensions for Visual Library
• Open source for visualisation
• http://dojotoolkit.org
– provide various types of business charts
• http://d3js.org
– 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
Changing Trends
– Mid -1990s : Network
A Unix
WWW
HTTP
B 200x
CGI
Network
DB
D Linux
– Late 1990s: XML Standardization
A (Unix)
B (MS200x)
MS-SQL
C (Linux)
Informix
Oracle
XML
Standards
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
method
description
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
http://www.w3schools.com/dom/tryit.asp?filename=try_dom_parsertest
XML DOM with JavaScript
<html>
<head>
<script type="text/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;
}
</script>
</head>
<body>
<script type="text/javascript">
xmlDoc=loadXMLDoc("books.xml");
document.write(xmlDoc.getElementsByTagNa
me("title")[1].childNodes[0].nodeValue +
"<br />");
document.write(xmlDoc.getElementsByTagNa
me("author")[0].childNodes[0].nodeValue
+ "<br />");
document.write(xmlDoc.getElementsByTagNa
me("year")[0].childNodes[0].nodeValue);
</script>
</body>
</html>
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
SOAP Message Exchange with
WSDL and
Service
Consumer
SOAP Sender
client
SOAP Receiver
find
WSDL
describing
service
Service
Provider
DESCRIBE
SOAP
http
transport message
INVOKE
SOAP
message
SOAP Receiver
http
transport
registry
Service Broker
service
SOAP Sender
publish
SOAP Message
SOAP envelope
Header
block
Header
data
SOAP
header
Header
data
SOAP Body
Body child element
Header
data
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: www.example.org
Content-Type: application/soap+xml; charset=utf-8
Content-Length: 299
SOAPAction: "http://www.w3.org/2003/05/soap-envelope"
<?xml version="1.0"?>
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
<soap:Header>
</soap:Header>
<soap:Body>
<m:GetStockPrice xmlns:m="http://www.example.org/stock">
<m:StockName>IBM</m:StockName>
</m:GetStockPrice>
</soap:Body>
</soap:Envelope>
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
message
message
porttype
operation operation operation
binding
port
service
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
Descargar

Slide 1