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)

Developing a Tuxedo client


A client is an application program that initiates requests in the Tuxedo application. This can be built in different platforms (for example, in both terminal and graphical interfaces). A client has to join the application before it can make any request to a server/service and must leave the application before exiting.

There are basically two types of clients:

  • Native client: This runs on the same platform as the Tuxedo domain, meaning it is attached locally

  • Workstation (WS) client: This runs on a different machine and joins over the network to a Tuxedo application running on a different machine

The design, coding, and operation of these two types of clients are the same—the ATMI for both are identical. There are some differences in the way these clients are compiled using the buildclient command, which will be described later.

Your client application uses tpinit() to attach to a Tuxedo application and tpterm() to detach from it. When a client joins an application, a...