Corba Fundamentals  «Prev 

Third party CORBA/COM Integration Products

Some of the third-party vendors for Corba that existed during the dot.com period are no longer in existence. The OMG is defining the standard for CORBA, which in turn is implemented by companies, also known as ORB vendors. Since the OMG is a vendor consortium that is open to everyone, you can participate in the process continue of what is defined by the OMG. A specification adopted by the OMG must be implemented by the submitters.

Introduction to the BEA Tuxedo CORBA Environment

The CORBA environment in the BEA Tuxedo product is based on the CORBA standard as a programming model for developing enterprise applications with high performance, scalability, and reliability. BEA Tuxedo CORBA extends the Object Request Broker (ORB) model with online transaction processing (OLTP) functions. The BEA Tuxedo CORBA deployment infrastructure delivers secure, transactional, distributed applications in a managed environment. CORBA objects built with the BEA Tuxedo product are accessible from Web-based applications that communicate using the CORBA Object Management Group (OMG) Internet Inter-ORB Protocol (IIOP). IIOP is the standard protocol for communications running on the Internet or on an intranet within an enterprise. BEA Tuxedo CORBA has a native implementation of IIOP, ensuring high-performance, interoperable, distributed-object applications for the Internet, intranets, and enterprise computing environments. You can build integrated enterprise applications using multiple programming models. CORBA and Application-to- Transaction-Monitor-Interface (ATMI) applications can be developed with fully integrated transaction management, security, administration, and reliability capabilities.
The interoperability technology incorporated into BEA Tuxedo CORBA provides for scalable connectivity between the CORBA and WebLogic Server environments. For information on interoperability see BEA Tuxedo Interoperability in the BEA Tuxedo online documentation.