Database Reference
In-Depth Information
◾
Message-Oriented Middleware (MOM)
: Achieves integration by providing for the
communication of messages between applications by means of the messages placed in
MOM, which itself is implemented in a variety of configurations, including message queu-
ing and message passing. The MOM is then responsible for delivering to the target system.
Microsoft's MSMQ, BizTalk, IBM's MQSeries, and Talarian's Smart Sockets are examples
of MOM.
◾
Distributed Object Technology (DOT)
: Achieves integration by providing object interfaces
that make applications look like objects; the application can then be accessed by other
applications across a network through the object interfaces. OMG's CORBA, Microsoft's
COM+, and Sun's Java 2 Enterprise Edition (J2EE) are examples of DOT.
◾
Transaction Processing Monitors (TPMs)
: Achieves integration by providing critical support
for integrity of distributed resources such as databases, files, and message queues across
distributed architectures by allowing various types of transactions to be managed using a
variety of concepts including two-phase commit. BEA's Tuxedo is an example of TPM.
Functional integration, which is more flexible than the other two integration models, can be
applied in three different forms described below.
10.2.2.2.1 Synchronization
This corresponds to the coordination of data updates from multiple sources across integrated
applications that may have been developed and enhanced across a long period of time. It pro-
vides integration that is loosely coupled and predominantly asynchronous. These applications
may represent various relationships that a customer may have had with the enterprise or manage
employees or products related information. When an update is made into anyone of the systems,
the update needs to be propagated across all of these systems. Typically, synchronization is imple-
mented by propagating a request that describes the intended action and the corresponding data
to each of the relevant systems.
10.2.2.2.2 Component Integration
Component integration is the integration of applications where a well-defined interface exists that
allows a component to be accessed via requests from other components without modifications. The
interfaces for each component must identify the specific functions that the component supports. It
provides integration that is tightly coupled and predominantly synchronous.
10.2.2.2.3 Straight-Through Processing (STP)
This corresponds to a coordinated set of automated actions executed across all relevant applica-
tions in the correct order of precedence automatically, that is, without human intervention. It
provides integration that is tightly coupled and can be both synchronous and asynchronous. This
kind of process is commonly associated with workflow though it does not involve decision mak-
ing or complicated scheduling. For instance, if an order for a product is placed on a website, the
order processing system (OPS) creates the order and notifies the logistics and shipping system to
ship the product. When the order is completed, the OPS is notified of the change of status and
the billing system triggers a bill for payment. Once the payment is received, the OPS is notified
to close the order.
