Chapter 8: Using Tuxedo Message Queue

As you know by now, Tuxedo uses System V IPC message queues for inter-process communication. Not only are those queues not persistent but their content can also be lost during a system restart. Tuxedo also uses at-most-once delivery semantics. So then, how can one build a reliable system with these tools? The answer to this is to use persistence for some of the messages and application parts.

Tuxedo comes with a queueing component called /Q included. Among other features, it supports queues persisted to the file system. Oracle also offers a paid add-on called Oracle Tuxedo Message Queue (OTMQ) with even more features. However, in this book, we will cover only /Q because every Tuxedo application has this component and it is sufficient for most tasks. For more advanced features and better integration, we will be using a open source messaging framework in Chapter 12, Modernizing the Tuxedo Application.

In this chapter, we will cover the following...