Book Image

Modernizing Oracle Tuxedo Applications with Python

By : Aivars Kalvans
Book Image

Modernizing Oracle Tuxedo Applications with Python

By: Aivars Kalvans

Overview of this book

Despite being developed in the 1980s, Oracle Tuxedo still runs a significant part of critical infrastructure and is not going away any time soon. Modernizing Oracle Tuxedo Applications with Python will help you get to grips with the most important Tuxedo concepts by writing Python code. The book starts with an introduction to Oracle Tuxedo and guides you in installing its latest version and Python bindings for Tuxedo on Linux. You'll then learn how to build your first server and client, configure Tuxedo, and start running an application. As you advance, you'll understand load balancing and work with the BBL server, which is at the heart of a Tuxedo application. This Tuxedo book will also cover Boolean expressions and different ways to export Tuxedo buffers for storage and transmission, before showing you how to implement servers and clients and use the management information base to change the configuration dynamically. Once you've learned how to configure Tuxedo for transactions and control them in application code, you'll discover how to use the store-and-forward functionality to reach destinations and use an Oracle database from a Tuxedo application. By the end of this Oracle Tuxedo book, you'll be able to perform common Tuxedo programming tasks with Python and integrate Tuxedo applications with other parts of modern infrastructure.
Table of Contents (18 chapters)
1
Section 1: The Basics
6
Section 2: The Good Bits
12
Section 3: Integrations

Configuring Tuxedo for transactions

A transaction is a unit of work that has ACID properties—Atomic, Consistent, Isolated, and Durable. But Tuxedo takes transactions a step further and supports distributed transactions that provide ACID properties for two or more databases from different vendors, queueing systems, and filesystems. Tuxedo was also the basis for the X/Open XA specification, which is the de facto standard for distributed transactions.

Transactions are infectious in Tuxedo. Once a transaction is started in Tuxedo, all the following service calls become a part of the transaction unless otherwise specified. If any of the services participating in the transaction fails, the whole transaction is marked as bad and must be aborted.

Although distributed transactions and two-phase commit do have problems and limitations, they work well in Tuxedo. Distributed transactions are not as trendy as Basically Available, Soft state, Eventual consistency (BASE) properties...