What Is the Configuration File?


	BEA Home \| Events \| Solutions \| Partners \| Products \| Services \| Download \| Developer Center \| WebSUPPORT
	http://www.oracle.com/technology/documentation/index.html \| Site Map \| Search \| PDF Files \| Contact \| Glossary

Tuxedo Documentation \| Setting Up a BEA Tuxedo Application \| Local Topics \| Previous Topic \| Next Topic \| Contents

Configuring each BEA Tuxedo application is a central task of the administrator. By configuring a file, you are describing your application using a set of parameters that the software interprets to create a viable application. The configuration file is a repository that contains all the information necessary to boot and run an application, such as specifications for application resources, machines, machine groups, servers, available services, interfaces, and so on.

Text and Binary Versions of the Configuration File

The configuration file exists in two versions:

The UBBCONFIG file is a text version of the configuration file, created and edited with any text editor. Except for sample configuration files distributed with BEA Tuxedo sample applications, no UBBCONFIG file is provided. You must create a UBBCONFIG file for each new application. The syntax used for entries in the file is described in UBBCONFIG(5) in the File Formats, Data Descriptions, MIBs, and System Processes Reference.
Note: The BEA Tuxedo software provides three sample UBBCONFIG files—ubbshm, ubbmp, and ubbsimple—as part of the bankapp and simpapp applications. (See Tutorials for Developing BEA Tuxedo ATMI Applications.)
The TUXCONFIG file is a binary version of the configuration file, created from the text version by the tmloadcf(1) command. Before tmloadcf is executed, the environment variable TUXCONFIG must be set to the full pathname of the device or system file where TUXCONFIG is to be loaded. If necessary, many parameters in TUXCONFIG can be changed while the application is running by using tmconfig, wtmconfig(1) or the MIB.