18.04.2013 Views

B2B Integration : A Practical Guide to Collaborative E-commerce

B2B Integration : A Practical Guide to Collaborative E-commerce

B2B Integration : A Practical Guide to Collaborative E-commerce

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Middleware Technologies 235<br />

Each framework is a book in itself. Some aspects of these frameworks,<br />

such as MOM (MSMQ and JMS), have been previously <strong>to</strong>uched upon<br />

in this chapter due <strong>to</strong> their ever-increasing importance in distributed<br />

systems. For the purpose of brevity, this section will focus on the<br />

distributed object/component element of each framework.<br />

8.4.3. OMA — CORBA 3<br />

The common object request broker architecture, or CORBA, was the<br />

first successful distributed architecture pro<strong>to</strong>col <strong>to</strong> be developed. CORBA<br />

is a distributed object/component technology that is platform and<br />

language independent and allows remote object creation and remote<br />

object method invocation.<br />

OMA architecture<br />

CORBA is a pro<strong>to</strong>col based on the object management architecture<br />

(OMA) developed by the OMG. The OMG is a consortium formed in<br />

1989 <strong>to</strong> define the standards and pro<strong>to</strong>cols required for distributed<br />

object systems in heterogeneous environments. OMG's objective is the<br />

definition of the OMA, which includes four sets of standards: the<br />

Common Object Request Broker Architecture (CORBA), Common Object<br />

Services Specification (COSS), Common Facilities and Application<br />

Objects. Unlike the COM and EJB pro<strong>to</strong>cols, the CORBA and OMA<br />

pro<strong>to</strong>cols are developed by a consortium which helps ensure that the<br />

final specification is product or technology independent.<br />

In 1992, OMG first approved the CORBA pro<strong>to</strong>col that defined the<br />

services <strong>to</strong> be provided by an Object Request Broker (ORB). The ORB is<br />

at the heart of CORBA and ORB provides a mechanism for transparently<br />

communicating between client requests, target objects and other ORBs.<br />

The ORB simplifies distributed programming by decoupling the<br />

client from the details of the method invocations. This makes client's<br />

requests appear <strong>to</strong> be local procedure calls, when in fact the ORB is<br />

operating on a remote server (see Figure 8.7). When a client invokes an<br />

operation, the ORB is responsible for finding the object implementation,<br />

transparently activating it if necessary, delivering the request <strong>to</strong> the<br />

object and returning any response <strong>to</strong> the caller.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!