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

Summary

In this chapter, we used the Oracle Database both from local and global transactions. You also experienced that mixing services using both local and global transactions does not work as you might imagine at first. Global transactions worked without any effort in application code and you might wonder why you would ever need to use local transactions. That feeling is shared by many users of Tuxedo. The most common reason for not using global transactions is squeezing out the last bits of performance. The performance overhead of transactions is small but they are not free. But even in those cases, it pays to have two implementations of the service as we did with the COUNT and COUNTXA services, one for each transaction type. After all, the code is the same and the only difference is in the server initialization.

Now you know how to develop servers for global and local transactions and how to configure the Tuxedo application in each case. You also know how to access the database...