Book Image

Getting Started with Oracle Tuxedo

Book Image

Getting Started with Oracle Tuxedo

Overview of this book

The client server or Tuxedo has existed for the past few decades and it is expanding every day! Today, Service Oriented Architecture (SOA) or Service Component Architecture (SCA) are considered to be the new approaches to build client server architecture, Tuxedo adopts this concept and can be extended very easily. "Getting Started with Oracle Tuxedo" shows how to develop distributed systems using Tuxedo and extend that to SOA or even a Cloud environment. The primary objective of this book is to show how to develop distributed systems using Tuxedo and extend that to a SOA environment. It also gives fundamentals of Exalogic machines and how Tuxedo application can leverage these new high end machines for enterprise needs. This book introduces you to the client server technology and how it has evolved in past decades. The book also covers various Tuxedo installation procedures, hardware and software requirements, and then how to configure Tuxedo application, all parameters with their syntax and relevant values. You will be introduced to various Tuxedo administrative tools, which are very important for a Tuxedo Administrator to perform his daily work, and with tuning suggestions and best practices. Next comes, Tuxedo APIs to build your applications, combining client and server modules. The book then covers the SALT component, which allows external web service applications to invoke Tuxedo services, and similarly Tuxedo applications can invoke external web services. At the end we discuss briefly the Exalogic machine and its architecture and how to configure and deploy Tuxedo application in this environment.
Table of Contents (12 chapters)

Transaction in Tuxedo


This is one of the most important sections in client/server architecture. The foundation of Tuxedo ATMI is a proven, reliable transaction processor, also known as a Transaction Processing (TP) monitor. This transaction processing has very unique characteristics consisting Atomicity, Consistency, Isolation, and Durability, also known as ACID.

  • Atomicity: All changes to data are committed in a single operation, which means all the changes are done at once, otherwise they are rolled back

  • Consistency: This means that the data has to be in a consistent state before and after the transaction

  • Isolation: This means that transactions run concurrently and appear to be serialized; the intermediate state of a transaction is unseen to other transactions

  • Durability: Once a transaction is committed, the changes to data should be saved and cannot be lost, even in the event of a system failure

The XA interface and two-phase commit

In a real-life scenario, we need to have a single function...