J2EE for Enterprise Integration - Guide to Cloud Computing for Business and Technology Managers - page 135

6
J2EE for En terprise Integration
6.1 Choosing an Enterprise Application Integration Platform
To implement the integration architecture requires an enterprise software
platform that gathers together all of the necessary technologies and mid-
dleware solutions needed for building enterprise information systems. The
prime choices are the J2EE platform, COBRA (Common Object Request
Broker Architecture), and the Microsoft.NET architecture.
6.1.1 CORBA
CORBA is a standardized open architecture managed by OMG (Object
Management Group). CORBA technology can be considered a generalization
of Remote Procedure Call (RPC) technology and includes several improve-
ments on the data objects and on the data primitives. The purpose of this
technology and architecture was to enable the development of distributed
applications and services that can interoperably communicate with other dis-
parate applications over the network. The CORBA was essentially developed
to bring about a discipline to implement portability and interoperability of
applications across different hardware platforms, operating environments,
and disparate hardware implementations. CORBA technology uses a binary
protocol called Internet Inter-ORB Protocol (IIOP) for communicating with
remote objects.
6.1.2 DCOM
In the mid-1990s, Microsoft Corporation introduced a technology called
COM that enabled the development of software modules called components
for integrating applications over the client-server architecture. To build
these components, developers adhered to the COM specification so that the
components could operate interoperably within the network. The DCOM
technology, introduced sometime in the late 1990s, enabled interaction
among network-based components to bring in the Distributed Computing
Environment (DCE). DCOM technology is essentially built on an object
135