Chapte

r Five
Management Issues in
Developing Integration System

1
 Enterprise Application
Integration
 The (EAI)
ultimate goal of EAI is to bind all
enterprise systems together in such a
way that any application can access any
method or any piece of data without
delay.
 is the primary facility for hardware,
software integration, and system level
testing.
 The facility supports software design and
hardware equipment integration used to
integrate and test integrated software
2

with configured systems.

 Advantage of
Enterprise Integration
 Reduces personnel, IT, and business
costs
 Increases revenues
 Increasing customer satisfaction
 Improving overall quality and
efficiency through optimizing
business processes
3
 The Challenges of
Integration
 integration is basically a complex
problem.
 Providingintegration, visibility,
and
database management across: entitie
structures,
hardware platforms,
applications, and operating systems,
s
programming
business languages,
probably one of the is
most complex tasks in IT.
 Integration doesn't come in a
differ
box.
technologies are most appropriate ent for
 different
You can't types
require just install and
of business
4

ments.
configure it.
 Con
t… companies need to avoid is thinking about
 What
only the necessity of integrating the integration
system.
 Enterprise integration is really more of a journey
(process of development) than a solution.
 System Integration provides an effective, efficient
and flexible management system.
•Effective could be interpreted as addressing all
relevant stakeholder that concerns.
•Efficient would mean that it does the job with low
resource use
5
 Integrated System
Development
•There are several Approaches
ways in which
an organization can develop and
implement an integrated system:
[Link] a totally new integrated
system from first principles based
on the structures and processes of the
organization.
•The main benefit of this approach is that the
resulting system will be more manageable
and will be consistent across and at all levels
of the organization.
requirements of the
[Link] an existing system which is
6

other disciplines.
currently usedfor a single discipline
 Integrated System
3. WhereDevelopment
two or more functions already have
individualApproaches…
management systems it may be
possible for these to be merged.
 This will require careful analysis of the
common elements to decide which of these
will be included and then apply to the
management of both disciplines.
 All of the elements need to mutually
harmonize if the management system is to be
truly integrated and effective.

7
 Barriers to
Integration
1. Failure to gain senior
management commitment
2. No stakeholder drivers for
integration
3. Vested interests
4. Lack of a universal integration
methodology /model
5. Lack of understanding and
concerns about competence
6. Unfavourable organizational 8
 Workflow Management
Systems(WFMS)
 What is
Reading
WFMS? Assignment
 Why WFMS?
 Parts of WFMS
 WF
Architecture
 WFMS
Requirements
 WFMS and
Middleware
9
 Application
Integration
 Web Service and its Components
 A WebStandards
Service can be defined by the following ways:
 A web service is any piece of software that
makes itself available over the internet and
uses a standardized XML messaging system.
 is a client-server application or application
component for communication.
 method of communication between two
devices over network.
 is a software system for interoperable
machine to machine communication. 10
Web
Servic
A complete web service is that:
e  Is available over the Internet or private
(intranet) networks
 Uses a standardized XML messaging
system
 Web services are hardware,
programming language, and operating
system independent.
 Is self-describing via a common XML 11

grammar
 Components of
Web services
 The basic web services platform is XML
+ HTTP.
 All the standard webservices
work using the following
components:
1. XML(Extensible Markup Language )
2. SOAP (Simple Object Access Protocol)
12

3. UDDI (Universal Description, Discovery

and Integration)
 How Does Web
Service Work?
 A web service enables communication
among various applications by using
open standards such as HTML, XML,
SOAP, WSDL, and UDDI.
 A web service takes the help of:
 XML to tag the data
 SOAP to transfer a message
 WSDL to describe the availability of service.
 UDDI to publishing and finding web services 13
 Web Service
There are Architecture
three major roles within the web
service architecture:
 Service Provider: This is the provider of the web
service. The service provider implements the
service and makes it available on the Internet.
 Service Requestor: This is any consumer of the
web service. The requestor utilizes an existing
web service by opening a network connection and
sending an XML request.
 Service Registry(Broker): This is a logically
their 14
Web Service
Architecture

15
 Extensible Markup
Language
 XML: (XML)Language
Extensible Markup
 Defined by the WWW Consortium (W3C)
 Derived from SGML (Standard
Generalized Markup Language), but
simpler to use than SGML
 Documents have tags giving extra
information about sections of the
document
–E.g. <title> XML </title> <slide> Introduction …
</slide>
 Extensible, unlike HTML
16


 XM
L…
XML was directed to describe data and to
focus on what data is. It can be used to
store, carry and exchange data between
systems.
 XML tags are not predefined, instead that
they are created by the author.
 There can be only one element as root
element.
 All XML elements should have a closing tag.
 XML tags are case sensitive.
 XML elements are strictly nested and
cannot overlap. 17
 XML…
 Bridge for data exchange on the Web
 An XML element is made up of a start
tag, an end tag, and data in between.
 Example:
<student> Abebe Kebede</student>
 XML tags are
case-sensitive:
<CITY>
<City>
<city>
 XML can
abbreviate
18
 XM
L… ability to specify new tags, and to
 The
create nested tag structures make XML a
great way to exchange data, not just
documents.
 Much of the use of XML has been in data
exchange applications, not as a replacement
for HTML
<account_number>
 Tags make data A-101
(relatively) self-documenting
<branch_name>
–E.g. </account_number>
<balance> 500
Downtown
<bank>
</balance>
</account>
</branch_name>
<account>
<account_number> A-101
<depositor>
<customer_name>
</
Abebe</customer_name>
</account_number>
deposit
or> 19
 XM
L…
There are three important
characteristics of XML
 XML is extensible: XML allows you to
create your own self-descriptive tags, or
language, that suits your application.
 XML carries the data, does not present it:
XML allows you to store the data
irrespective of how it will be presented.
 XML is a public standard: XML was
developed by an organization called the
World Wide Web Consortium (W3C) and is20
 Contents of
XMLdeclaration:
 XML file must be at beginning of a
file
<? xml version="1.0" encoding="UTF-
8"?>
 Element(tag): must have a valid name,
begin with underscore (_) or letter,
periods, digits, hyphens or underscores.
But can’t use string “xml” in any case of
combination and each element have
starting and closing tag.
Valid: <_Element1> </_Element1>
<[Link]> </[Link]>
Invalid: <1Elemet> 21
 Contents of
XML file…
 Empty tags i.e. tags that do not contain any
content themselves, must be closed
with />
Instead of <elm><elm/> use <elm/>
 Attribute values must always be inside
quotes, either single or double
<elm attr=val> is wrong use <elm
attr=“val”>
 Tags must be properly nested inside each
other
<elm1> <elm2> <elm1> <elm2> is wrong,
use <elm1> <elm2> <elm2> <elm1> 22
 Contents of
XML file…
 Attribute: Is specified on the start tag of
an element.
<element atrri=”atrri_val”>
</elemenet> And can only
appear one time on a given element.
<element atrri=”a” atrri=”b”> is wrong
 Comment: begins with <!-- and end with
-->
<!-- Type your comment -->
 Character data section: used to the
character data that you want to be the 23
 XML
Usage
 XML can be used to store and arrange the
data, which can customize your data
handling needs.
 XML can easily be merged with style sheets
to create almost any desired output.
 Virtually, any type of data can be expressed
as an XML document.
 XML can work behind the scene to
simplify the creationof HTML documents
for large web sites.
 XML can be used to exchange the
information between organizations and
24
 The Building Blocks of
XML Documents
 All XML documents are made up by the
following building blocks:
 PCDATA
 CDATA
 Elements
 Entities
 Attributes

25
 The Building Blocks of
XML Documents…
 PCDATA
 means Parsed Character Data.
 PCDATA is text that WILL be parsed by a
parser.
 The text will be examined by the parser for
entities and markup.
 Tags inside the text will be
treated as markup and entities will
be expanded.
 CDATA
 means Character Data.
 CDATA is text that will NOT be parsed by a
parser. 26
 CDATA
Syntax characters with
 <![CDATA[
markup ]]>
 The above syntax is composed of
three sections:
1. CDATA Start section - CDATA begins
with the nine-character delimiter <!
[CDATA[
2. CDATA End section - CDATA section
ends with ]]> delimiter.
3. CDATA section - Characters between
these two enclosures are interpreted
as characters, and not as markup.
This section may contain markup
characters (<, >, and &), but they are
27
 Difference Between
XML and HTML
 XML document does not DO anything,
was designed to be self- descriptive of
about data
 XML was designed to carry data - with
focus on what data is
 HTML was designed to format and
display data - with focus on how data
looks
 XML tags are not predefined like HTML
tags are 28
XML

 <?xml version="1.0"
encoding="UTF-8"?> XML prolog
 All XML Elements Must Have a
Closing Tag
 XML Tags are Case Sensitive
 XML Elements Must be Properly
Nested
 XML Attribute Values Must be
Quoted
29
Entity
Reference
 Some characters have a special
s
meaning in XML.
 If you place a character like "<" inside
an XML element, it will generate an
error because the parser interprets it
as the start of a new element.
 This will generate an XML error:
 <message>salary <
1000</message> 30
 Entity
References
 There are 5 pre-defined
…&lt <references
entity less than in XML:
;
 &g > greater than
t;
 &am & ampersa
p; nd
 &apo we
When ‘ want
apostrop
to use the XML entity
s;
references he a data we use CDATA or
as
 &quo “ quotation
we must write like(&lt;, &gt;, &amp;,
t; mark
&apos;, and &quot;). 31
XML
Naming
 The syntax for writing comments in
Rules
XML is similar to that of HTML.
 <!-- This is a comment -->
 Two dashes in the middle of a comment
are not allowed.
 Not allowed: <!-- This is a -- comment --
>
 White-space is Preserved in XML
 XML does not truncate
multiple white-spaces (HTML
truncates multiple white-spaces to one
single white-space):
 XML: Hello Everybody 32
 XML Naming
Rules…
 XML elements must follow these naming
rules:
 Element names are case-sensitive
 Element names must start with a letter or
underscore
 Element names cannot start with the
letters xml (or XML, or Xml, etc)
 Element names can contain letters, digits,
underscores, and periods
 Element names cannot contain spaces
 Avoid using -, . , : 33
 Avoid XML
Attributes?
 Some things to consider when using
attributes are:
 attributes cannot contain multiple
values (elements can)
 attributes cannot contain tree
structures (elements can)
 attributes are not easily expandable
(for future changes)
 Attributes provide extra information
about elements. Attributes are
always placed inside the opening tag
34
 XML
 Namespac
XML Namespaces provide a method to avoid
element
es name conflicts.
 XML table contains information about fruit
<table>
<tr>
<td>Apples</td>
<td>Bananas</td>
</tr>
</table>
 XML table contains information about house
<table>
<name>Ethiopian house</name>
<width>80</width>
<length>120</length>
</table
 Solving the Name Conflict Using a Prefix like
<f:table> and <h:table>
 Declare
 xmlns:h="[Link]
the name space inside root element or35
 XML
 Namespace
XML data has to be exchanged between
organizations
s…
 Same tag name may have different
meaning in different organizations, causing
confusion on exchanged documents
 Specifying a unique string as an element
name avoids confusion
 Better solution: use unique-name:element-
name
 Avoid using long unique names allover
document by using XML Namespaces
<FB:bran Brooklyn </
<bank Xmlns:FB=‘[Link]
chcity>
… FB:branchcity>
</
<FB:branch>
FB:branch>
<FB:branchname>Downtown</
36
 XML
DTDgives a way to check the validity of
 DTD
XML files by checking whether
the elements appear in the right
order, mandatory elements and
attributes are in place, the
elements and attributes have not
been inserted in an incorrect way, and so
on.
 An XML document with correctwith
syntax is
defines the structure a
called
An XML"Well Formed".
document which conforms
 list
“valid”. of legal
there elements.
An
to XMLrules
the ofare two
document types of
validated
DTD DTDisfile:
against acalled
DTD
 is both "Well
External
external DTD Formed"
Declaration
and internal and "Valid".
DTD
 
The purpose
If the DTD is ofdeclared
a DTD isintoan
define the file,
external
the <! DOCTYPE>
structure of an XML definition
[Link] contain
a reference to the DTD file:
37
 External DTD
•Declaration
<?xml version="1.0"?>
<!DOCTYPE note SYSTEM
"[Link]">
<note>
<to>IT 4th</to>
<from>Tadesse</from>
<body>Don't forget
today’s class</body>
</note>
•<!DOCTYPE note [
<!ELEMENT note
(to,from,body)>
<!ELEMENT to (#PCDATA)>
<!ELEMENT from
(#PCDATA)> 38
 Internal DTD
•IfDeclaration
the DTD is declared inside the XML file, it
must be wrapped inside the <! DOCTYPE>
definition:
•<?xml version="1.0"?>
<!DOCTYPE note [
<!ELEMENT note (to,from,body)>
<!ELEMENT to (#PCDATA)>
<!ELEMENT from (#PCDATA)>
<!ELEMENT body (#PCDATA)>
]>
<note>
<to>IT 4th</to>
<from>Tadesse</from>
<body>Don't forget today’s class</body> 39
Publish/Find/
Bind Model 1. The service provider
publishes its
service(s) to a service
registry such as UDDI
in the form of a WSDL
document.
2. The service requestor
finds services
for consumption via
service registries and
this process is also
called “service
discovery.”
3. Once the service
requestor has 40
 Publish/
Find/Bind
 Web Services are published and located via
the UDDI, they are described using WSDL
and are invoked using SOAP over HTTP
 SOAP Also known as “e-mail for
XML documents” SOAP is like the
computer version using the postal service.
A message (like a letter) is placed in an
envelope and sent off to the person it is
intended for.
 Specifically, it standardizes what we refer to
as:
 "an envelope" (actually called a SOAP
envelope) 41
 SOAP (Simple Object
Access
SOAP wasProtocol)
created to accomplish this.
 SOAP provides a way to communicate
between applications running on different
operating systems, with different
technologies and programming languages.
 SOAP is for communication protocol
between applications.
 SOAP is a format for sending messages.
 SOAP is designed to communicate via
Internet.
 SOAP is platform and language
independent.
 SOAP is simple and extensible. 42
 WSDL(Web Service
Description
 WSDL Language)
is an XML-based language for
describing, locate web services and how to
access them.
 WSDL was developed jointly by Microsoft and
IBM.
 WSDL is an XML based protocol for
information exchange in decentralized and
distributed environments.
 WSDL is the standard format for describing a
web service.
 WSDL definition describes how to access a
web service and what operations it will
perform.
 WSDL is a language for describing how to
interface with XML-based services. 43
UDDI(Universal Description,
Discovery,
 UDDI is an and Integration)
XML-based standard for
describing services, publishing, and
finding web services by using the Internet.
 UDDI is a specification for a distributed
registry of web services.
 UDDI is platform independent, open
framework.
 UDDI can communicate via SOAP, CORBA,
and Java RMI Protocol.
 UDDI uses WSDL to describe interfaces to
web services.
 UDDI specification defines a framework for
registering, deregistering and discovering
44
SOA
Technologi
es UD Points to
description WS
DI
Regi DL
stry Fin Descr
ibes
ds
Serv
Ser
ice
vice
Servi We
SO
ce b
AP
Consu Communica Ser
mer tes with vice 45