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)

Tuning the application


Planning the architecture of a Tuxedo system is a very important and critical task, as there are a number of components that have various parameters that can impact performance, scalability, reliability, and security. There are basically two major areas we need to look at: modularity (which makes applications more manageable), and agile and resource management (which means sharing common resources to reduce maintenance, that is, time and cost). As an administrator, you need to keep these two in mind, and you don't need to predefine the application configuration all at once. The initial/default values for parameters in UBBCONFIG usually provide acceptable/standard performance in most cases. If the performance, measured by response time, is not as high as required, the administrator should monitor the system to determine the bottleneck and change parameters as necessary. I am sharing some practical experiences with you, which are very common, but critical for a Tuxedo...