Managing Your Configuration Dynamically


	Corporate Info \| News \| Solutions \| Products \| Partners \| Services \| Events \| Download \| How To Buy
	http://www.oracle.com/technology/documentation/index.html \| Site Map \| Search \| PDF Files \| Contact \| Glossary

Tuxedo Doc Home \| Getting Started \| Topic List \| Previous \| Next \| Contents

Introducing the BEA Tuxedo System

Administrators can use the BEA Administration Console or the BEA Tuxedo system command-line utilities to reconfigure applications dynamically, adjusting parameters to respond to varying system loads while the system is running. A revised TUXCONFIG file is propagated automatically to all machines in the system as it is updated. However, many RESOURCES parameters cannot be changed while the system is running.

Examples of tasks you can do dynamically include: adding servers or machines, deleting machines, and so forth. To ensure that the text and binary versions of your configuration file (UBBCONFIG and TUXCONFIG, respectively) always match, you need to back them up and synchronize them by using tmunloadcf. This command translates the binary file to a text version.

You can change most elements of the system dynamically. You can, for example, spawn new servers, add new machines, or change time-out parameters. There are, however, a few things you cannot change while a system is running:

Any parameter in the configuration file that affects the size and shape of the bulletin board cannot be changed. Many such parameters are named with the prefix "MAX," such as the MAXGTT parameter, which specifies the maximum number of in-flight transactions allowed within the BEA Tuxedo system at any time.
The processor name of a machine within a particular application cannot be changed. (You can add new machines with different names but you cannot change the name of an existing machine.)
The values of server executables, assigned to run on MASTER and BACKUP machines, cannot be changed.