About Opentopia
Opentopia Directory Encyclopedia Tools

Common Object Request Broker Architecture

Encyclopedia : C : CO : COM : Common Object Request Broker Architecture

In computing, Common Object Request Broker Architecture (CORBA) is a standard for software componentry, created and controlled by the Object Management Group (OMG). It defines APIs, communication protocol, and object/service information models to enable heterogeneous applications written in various languages running on various platforms to interoperate. CORBA therefore provides platform and location transparency for sharing well-defined objects across a distributed computing platform.

In a general sense CORBA “wraps” code written in some language into a bundle containing additional information on the capabilities of the code inside, and how to call it. The resulting wrapped objects can then be called from other programs (or CORBA objects) over the network. In this sense, CORBA can be considered as a machine-readable documentation format, similar to a header file but with considerably more information.

CORBA uses an interface definition language (IDL) to specify the interfaces that objects will present to the world. CORBA then specifies a “mapping” from IDL to a specific implementation language like C++ or Java. This mapping precisely describes how the CORBA data types are to be used in both client and server implementations. Standard mappings exist for Ada, C, C++, Lisp, Smalltalk, Java, and Python. There are also non-standard mappings for Perl, Visual Basic, and Tcl implemented by ORBs written for those languages.

The CORBA IDL is only one example of an IDL.

This diagram illustrates how the generated code is used within the CORBA infrastructure:

This picture does not reflect all typically used possibilities. Normally the server side has the Portable Object Adapter that redirects calls either to the local servants or (to balance the load) to the other servers. Also, both server and client parts frequently have interceptors that are described below.

In addition to providing users with a language and a platform-neutral remote procedure call specification, CORBA defines commonly needed services such as transactions and security.

Contents
  • 3 CORBA implementations
  • 4 OMG trademarks
  • 5 See also
  • 6 References
  • 7 External links

    • Key Features

    Objects by Value (OBV)

    Apart from remote objects, the CORBA and RMI-IIOP define the concept of the OBV. The code inside the methods of these objects is executed locally by default. If the OBV has been received from the remote side, the needed code must be either a priori known for both sides or dynamically downloaded from the sender. To make this possible, the record, defining OBV, contains the Code Base that is a space separated list of URLs from where this code should be downloaded. The OBV can also have the remote methods.

    The OBV's may have fields that are transferred when the OBV is transferred. These fields can be OBV's themselves, forming lists, trees or arbitrary graphs. The OBV's have a class hierarchy, including multiple inheritance and abstract classes.

    CORBA Component Model (CCM)

    CORBA Component Model (CCM) is an addition to the family of CORBA definitions. It was introduced with CORBA 3, and it describes standard application framework for CORBA components. It is extension of "language independent Enterprise Java Beans (EJB)". It provides abstraction of entities that can provides and accepts services through well defined named interfaces called port.

    The CCM has a component container, where software components can be deployed. The container offers a set of services that the components can use. These services include (but are not limited to) notification, authentication, persistence and transaction management. These are the most used services any distributed system requires, and by moving the implementation of these services from the software components to the component container, the complexity of the components is dramatically reduced.

    External links

    Portable interceptors

    Portable interceptors are the "hooks", used by CORBA and RMI-IIOP to mediate the most important functions of the CORBA system. CORBA standard defines the following types of interceptors:
    1. IOR interceptors mediate the creation of the new references to the remote objects, presented by the current server.
    2. Client interceptors usually mediate the remote method calls on the client (caller) side. If the object Servant (CORBA) exists on the same server where the method is invoked, they also mediate the local calls.
    3. Server interceptors mediate the handling of the remote method calls on the server (handler) side.
    The interceptors can attach the specific information to the messages being sent and IORs being created. This information can be later read by the corresponding interceptor on the remote side. Interceptors can also throw forwarding exceptions, redirecting request to another target.

    General InterORB Protocol (GIOP)

    The GIOP is an abstract protocol by which Object request brokers (ORBs) communicate. Standards associated with the protocol are maintained by the Object Management Group (OMG.).

    Internet InterORB Protocol (IIOP)

    The Internet Inter-Orb Protocol, is a protocol for communication between CORBA ORBs that has been published by the Object Management Group. IIOP is an implementation of the GIOP for use over an internet, and provides a mapping between GIOP messages and the TCP/IP layer.

    SSLIOP is IIOP over SSL, providing encryption and authentication.

    Network Data Delivery Service (NDDS)

    The Network Data Delivery Service, NDDS emerged from Object Management Group (OMG) Data Distribution Service (DDS) standard, and provides a network middleware between the application and the operating system. Using the Publisher to relay the topic to all subscribers simplifies the underlying low-level network with RTI standards-based API.

    For Real-time applications, the traditional publish-subscribe model has some limitations. The Real-time applications need more deterministic timing control, reliability control, fault tolerance and thread awareness. Object Management Group (OMG) developed the CORBA and the DDS standards. DDS addresses publish-subscribe data distribution and extends publish-subscribe model for real-time systems. Based on the DDS standard, Real-Time Innovations (RTI), headquartered in the heart of Silicon Valley since 1991, produces NDDS, the Real-Time Publish-Subscribe Network Middleware.

    The Network Data Delivery Service (NDDS) is network messaging middleware that allows programmers to set up host-independent communication for distributed real-time applications. It implements the Publish-Subscribe communications model and runs on top of a standard internet UDP/IP protocol stack. NDDS has support for many architectures, Multi-OS, like Windows NT, 2000, XP / Linux / Solaris / VxWorks / Integrity / LynxOS and languages include C / C++ / Java.

    Besides NDDS there are multiple other products that emerged from the DDS standard. For example for The ACE ORB there is a TAO-DDS that emerged from the DDS standard.

    Corba Location

    CorbaLoc means Corba Location refers to a stringified object reference for a Corba object that looks similar to a URL.

    All CORBA products must support two OMG-defined URLs: "corbaloc:" and "corbaname:". The purpose of these is to provide a human readable/editable way to specify a location where an IOR can be obtained.

    An example of corbaloc is shown below:

    corbaloc::160.45.110.41:38693/StandardNS/NameServer-POA/_root
    A CORBA product may optionally support the "http:", "ftp:" and "file:" formats. The semantics of these is that they provide details of how to download a stringified IOR (or, recursively, download another URL that will eventually provide a stringified IOR).

    External links

    CORBA implementations

    - A CORBA 2.5–compliant commercial ORB for Java and C++ from BEA_Systems
  • [Borland Enterprise Server, VisiBroker Ed.] -
    • - A CORBA 2.6–compliant commercial ORB for Java and C++ from Borland.
  • [Combat] - A Tcl ORB, and a Tcl layer for C++ ORBs.
  • [e*ORB] -
    • - A commercial ORB for Ada, C and C++ from PrismTech.
  • ILU - An open software object interface system from Xerox PARC.
  • GNU Classpath - Contains the Free Software (GPL+linking exception, including newly written org.omg packages) implementation for Java.
  • [IIOP.NET] -
    • - A Free Software (LGPL) ORB for Microsoft .NET.
  • [JacORB] -
    • - A Free Software (LGPL) ORB implemented in Java.
  • [J-Integra Espresso] - commercial Microsoft .NET ORB by Intrinsyc J-Integra
  • [MICO] -
    • - A Free Software (LGPL) ORB implemented in C++.
  • [omniORB] -
    • - A Free Software (LGPL) ORB for C++ and Python.
  • [OpenORB] -
    • - A Free Software (BSD) ORB for Java.
  • [Orbacus] - commercial C++ ORB by IONA Technologies
  • [ORBexpress] - standard and real-time commercial Ada, C++, and Java ORBs by Objective Interface Systems
  • [ORBit2] -
    • - A Free Software (LGPL) ORB for C, C++ and Python.
  • [Orbix] - commercial ORB by IONA Technologies
  • [OrbRIVER] -
    • - A commercial ORB for Ada, C++ and Java from Topgraphx.
  • [Perl ORB] -
    • - An open-source (Artistic License) ORB implemented in Perl.
  • PolyORB -
    • - A Free Software (MGPL) ORB implemented in Ada.
  • Python ORB -
    • - A Free Software (Python license) ORB implemented in Python.
  • [SANKHYA Varadhi] -
    • - A commercial ORB for C++
  • [TAO] -
    • - The ACE ORB, an open-source ORB for C++
  • [VBOrb] -
    • - A Free Software (LGPL) ORB for Visual Basic
  • [Xtradyne I-DBC] -
    • - A commercial CORBA Security implementation from Xtradyne.
  • [ORBLink] - A commercial ORB for Allegro Common LISP

    • OMG trademarks

    CORBA, IIOP and OMG are the registered marks of the Object Management Group and should be used with care. Differently, the GIOP is not the registered OMG trademark. Hence in some cases may be more appropriate just to say that the application uses or implements the GIOP-based architecture. The text inside the CORBA specification itself ensures that no person shall be deemed just for using or implementing this specification.

    See also

    has more about this subject:

    References

    External links

     

    From Wikipedia, the Free Encyclopedia. Original article here. Support Wikipedia by contributing or donating.
    All text is available under the terms of the GNU Free Documentation License See Wikipedia Copyrights for details.

    Search Titles
    0123456789
    ABCDEFGHIJ
    KLMNOPQRST
    UVWXYZ?

    E-mail this article to:

    Personal Message: