BEA Tuxedo Application Administration DEPL
DEPL-4
Copyright © BEA Systems, Inc.
All Rights Reserved. Unauthorized Duplication Prohibited.
© BEA Systems, Inc.
DEPL-4
BEA Tuxedo Application Administration
The Tuxedo Configuration File
Referred to as the UBBCONFIG file but can
be any file name;it defines the parameters
for Tuxedo to boot (start-up) an application
The UBBCONFIG file is typically created by
application developers and modified by the
application administrator
The configuration file exists in two formats
¾ UBBCONFIG: text version
¾ TUXCONFIG: binary version, compiled from the
UBBCONFIG file; this is the file that is used to
actually boot the Tuxedo application domain
UBBCONFIG
The UBBCONFIG file is an ASCII version of the configuration file. You can create and
edit this version with any editor. Sample configuration files are provided with each of the
Tuxedo sample applications, including the simple sample–simpapp. You must create a
UBBCONFIG file for each new application. You can use any of the sample UBBCONFIG
files as a starting point and edit it to meet the requirements of your particular application.
The syntax used for entries in the file is described in detail in the ubbconfig(5) reference
pages in the BEA TUXEDO Reference Manual.
TUXCONFIG
The TUXCONFIG file is a binary version of the configuration file that you generate from
the ASCII version using the tmloadcf command. You cannot create this file directly; a
UBBCONFIG file must be created first. You can, however, dynamically modify many (but
not all) configuration parameters while the application is running.
The TUXCONFIG file contains information used by tmboot to start the Tuxedo
administrative server and initialize the bulletin board of a BEA TUXEDO system. The
tmadmin command line utility uses the configuration file (or a copy of it) in its monitoring
activity. The tmshutdown command references the configuration file for information
needed to shut the application down.
