ITPE 114
Integrative Programming
& Technologies 2
Integration Models
Integration model defines how applications will be integrated by defining
the nature of and mechanisms for integration. Some of the methods used
for application integration are discussed in the following section. These
models include;
Presentation integration model
Data integration model
Function integration model
Presentation Integration Model
Presentation integration model allows the integration of new software
through the existing presentations of the legacy software. This is
typically used to create a new user interface but may be used to
integrate with other applications.
Data Integration Model
Data integration model allows integration of software through access
to the data that is created, managed and stored by the software
typically for the purposes of reusing or synchronizing data across
applications.
Functional Integration Model
Functional integration model allows the integration of software for
the purpose of invoking existing functionality from other new or
existing applications. The integration is done through interfaces to
the software.
Fundamental Challenges
of Integration
Application integration is needed to allow different systems to share data
and support common business processes. However, integration is difficult
because many applications were built independently, use different
programming languages, run on different platforms, and operate in
different locations. Although integration tools exist, they only solve part of
the problem. The real challenges involve both technical and business
issues.
Key challenges include;
Network unreliability
Distributed systems
Slow networks; and;
Heterogeneity
Modification complexity
Network is unreliable
Integration solutions have to transport data from one computer to another
across networks. Compared to process running on a single computer,
distributed computing has to be prepared to deal with a much larger set
of possible problems.
Often times, two systems to be integrated are separated by continents
and data between them has to travel through phone lines, LAN segments,
routers, switches, public networks, and satellite. Each of these steps can
cause delays or interruptions.
Distributed systems
In the worst case, every application runs on a completely separate
environment, e.g., database storage is not shared among applications.
Message-based communication is the only possibility to exchange
information.
Networks are slow
Sending data across the network is multiple orders of magnitude slower
than making a local method call. Designing a widely distributed solution
the same way you would approach a single application could have
disastrous performance implications.
Any two applications are
different
Integration solutions need to transmit information between systems that
use different programming languages, operating platforms, and data
formats. An integration solution needs to be able to interface with all these
different technologies.
Heterogeneous
Each application implements its own data model. Concepts may be
shared, but representation mismatches are to be expected. Mappings and
transformations are required.
Change is inevitable
Applications change over time. An integration solution has to keep pace with changes
in the applications it connects. Integration solutions can easily get caught in an
avalanche effect of changes - if one system changes, all other systems may be
affected.
An integration solution needs to minimize the dependencies from one system to
another by using loose coupling between applications.
Autonomous applications update their state independently without coordinating with
each other. The systems to be integrated are maintained independently and upgraded
at different times.