The original development targeted the creation and administration of operations support systems for the US telephone company that required online transaction processing (OLTP) capabilities.
[2] In 1993 Novell acquired the Unix System Laboratories (USL) division of AT&T which was responsible for the development of Tuxedo at the time.
In September 1993 it was called the "best known" distributed transaction processing monitor, running on 25 different platforms.
In essence, Tuxedo provided the elements of service-oriented architecture (SOA) decades before the phrase was coined.
Tuxedo can use the content of the message to determine what servers should be utilized to receive the request by means of data-dependent routing.
Servers, services, transactions, and clients are all registered in the BB providing a global view of their state across the machines within a domain.
A master machine runs a process called the "Distinguished Bulletin Board Liaison" that coordinates the updates to the BB.
On Oracle Exalogic Tuxedo leverages the RDMA capabilities of InfiniBand to bypass the bridge.
Tuxedo applications can utilize a variety of message formats depending upon the type of data that is to be passed.
As it is a self-describing binary format, the processing of fields incurs very little overhead in comparison to the parsing necessary to support something like XML.
A VIEW buffer has an external description which allows Tuxedo to access the fields within it if necessary for things like data dependent routing.
This is in contrast to most Java EE application servers where load balancing is done by the client making requests to different machines with the cluster.
Besides connecting Tuxedo domains together, domain gateways exist for mainframe systems using TCP/IP, IBM's Systems Network Architecture (SNA), or the OSI protocols, and Java Platform, Enterprise Edition application servers.
The BRIDGE process in a clustered environment monitors to BBL, so there are no single points of failure.
Any transactions that are affected by a server or machine failure and that have not completed the prepare phase are rolled back.
Unsolicited events allow Tuxedo applications to send out-of-band notifications to clients that aren't necessarily waiting for a response.
By providing automated conversion tools, CICS equivalent API pre-processor macro expansion, and a JES-2 like Batch execution environment, the migration of mainframe applications is greatly simplified.
This product provides a set of gateway processes that run on Tuxedo that communicate with a mainframe using its native protocols.
Provides enterprise messaging capabilities that combines the features of Oracle MessageQ with Tuxedo.