- X/Open XA /D - Clustering - Domains /WS - Remote Clients WTC - Weblogic Tuxedo Connector Java clients - Jolt Java EE (J2EE) Integration - Tuxedo JCA Adapter Bidirectional SOAP and REST Web Services - SALT /Q - Transient (in memory) and Persistent Queues (also called Reliable Queues) Data Dependent Routing (DDR) Event Broker (also called publish and subscribe messaging) Security - Authentication, Authorization, Auditing, and Public key infrastructure based message signing and encryption Programmed Administration and SNMP support System and application performance monitoring - TSAM Plus Load balancing, server spawning and decay Mainframe connectivity - TMA Supports C, C++, COBOL, Python, Ruby, PHP, and Java applications on most Unix platforms, Linux, Microsoft Windows, and other proprietary platforms such as OpenVMS and IBM i. Messaging core Tuxedo is at its core a message routing and queuing system. Requests are sent to named services and Tuxedo uses memory-based inter-process communication facilities to queue the requests to servers. The requester is unaware of where the server that actually processes the request is located or how it is implemented. 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. Clustering The heart of the Tuxedo system is the Bulletin Board (BB). This is a shared memory segment that contains the configuration and state of a Tuxedo domain. Servers, services, transactions, and clients are all registered in the BB providing a global view of their state across the machines within a domain. To coordinate updates to the BB a process called the Bulletin Board Liaison (BBL) runs on each machine to keep the local copy of the BB up-to-date. A master machine runs a process called the "Distinguished Bulletin Board Liaison" that coordinates the updates to the BB. This allows each machine to have a view of what servers, services, transactions, and clients are on each machine within the domain. Another process on each machine called the Bridge is responsible for passing requests from one machine to another. This allows Tuxedo to spread load across the various machines within a domain and allows servers and services to be running on multiple machines. In addition, the BBL and Bridge monitor each other and restart the other should one fail. In the advent of a