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)

The Tuxedo domain


The Tuxedo domain can be used for large-federated or distributed-application architecture across cities, countries, or different parts of the world. The Tuxedo domain facilitates interoperate or extend the scope of various applications to include access to other Tuxedo and non-Tuxedo-based applications. The Tuxedo domain provides transparency between applications to ensure that any client can get services from another domain (remote service) by maintaining the security norms. The Tuxedo administrator can define/design different domains based on the geographical location of the data center or to enforce inter-organizational boundaries. The Tuxedo domains are autonomous, which means they are administered independently of each other. Domains are defined by the administrator; he/she defines how the services in one domain are made available to another. There are basically three components for the Tuxedo domain architecture: DoMain Administrative server (DMADM), GateWay Administrative...