NonStop Systems Introduction

The Application Server Environment
NonStop Systems Introduction—527825-001
3-19
NonStop CORBA
The Tuxedo API provides distributed transaction-processing capabilities and
transparent access to the fundamental benefits of the SQL/MX database and NonStop
server:
•
Scalability
•
Fault tolerance
•
7X24 availability
•
Easy manageability
NonStop Tuxedo supports clients on many different platforms, including Windows,
HP/UX, and Sun.
NonStop CORBA
The Common Object Request Broker Architecture (CORBA) is an industry-standard
distributed object computing infrastructure for implementing enterprise-class object-
oriented applications. CORBA combines object-oriented programming with distributed
processing. CORBA has been used with great success as an application server and
integration environment in ZLE systems.
Distributed object computing refers to a computing methodology in which applications
are composed of individual modules of software called objects. These objects are
distributed across processors and networks. Objects communicate with one another
without regard for where the individual objects reside. The objects can reside in the
same processor on the same system, in different processors on the same system, or
on a remote systems.
In a distributed object environment, objects communicate using message-based
interfaces. Object technology is well-suited to the N-tiered client/server architecture
introduced earlier in this section.
In the CORBA environment, program components (objects) communicate with objects
in other programs, even if the two programs are written in different programming
languages and are running on different platforms. The CORBA environment manages
the objects and enables them to work together as an application.
Figure 3-13 on page 3-20 shows a typical distributed object computing environment.
Several client applications are sending transaction requests to server processes
(objects) on other systems. In turn, these servers can send database requests to a
server process running on a third system; the transaction server becomes a client
process to the third system.