6.14 Editing a UBBCONFIG File

Each Oracle Tuxedo application is controlled by a configuration file in which installation-dependent parameters are defined. In the Oracle Tuxedo documentation, this file is referred to as UBBCONFIG, but you can give your configuration file any name you like as long as the content of the file conforms to the format described in reference page UBBCONFIG(5) in OracleTuxedo File Formats, Data Descriptions, MIBs, and System Processes Reference. Typical configuration filenames begin with the string ubb, followed by a mnemonic string, such as simple in the filename ubbsimple.

As an example, consider ubbsimple, the UBBCONFIG file for the rudimentary ATMI-based simpapp application delivered with the Oracle Tuxedo installation. On a Windows system, this application is found in the directory %TUXDIR%\samples\atmi\simpapp; on a UNIX system, it is found in the directory $TUXDIR/samples/atmi/simpapp.

The following example ubbsimple file has been modified from the ubbsimple file delivered on a UNIX system to include example pathname values for both Windows and UNIX systems.

#ident “@(#)apps:simpapp/ubbsimple $Revision: 1.3 $ 
#Skeleton UBBCONFIG file for the Tuxedo Simple Application. 
#Replace the <bracketed> items with the appropriate values. 
*RESOURCES IPCKEY <Replace with a valid IPC Key> 
#Example: 
#IPCKEY 123456 
DOMAINID simpapp 
MASTER simple 
MAXACCESSERS 10 
MAXSERVERS 5 
MAXSERVICES 10 
MODEL SHM 
LDBAL N 
*MACHINES 
DEFAULT: 
APPDIR=“<Replace with the current directory pathname>” 
TUXCONFIG=“<Replace with your TUXCONFIG Pathname>” 
TUXDIR=“<Directory where Tuxedo is installed>”  
#UNIX 
  #Example: 
  # APPDIR=“/home/me/simpapp” 
  # TUXCONFIG=“/home/me/simpapp/tuxconfig” 
  # TUXDIR=“/home/oracle/tuxedo12cR1” 
<Machine-name> LMID=simple 
#Example:
  #beatux LMID=simple 
*GROUPS 
GROUP1 LMID=simple GRPNO=1 OPENINFO=NONE 
*SERVERS 
DEFAULT: 
CLOPT=“-A” 
simpserv SRVGRP=GROUP1 SRVID=1 
*SERVICES 
TOUPPER

In the configuration file for your application, you must replace the strings enclosed in angle brackets with values specific to your application. The following table provides a sample of the parameters that must be defined in every configuration file.

Table 6-9 Parameter Sample

Parameter	Specifies
IPCKEY	A numeric key that identifies the shared memory segment where the structures used by your application are located. The value must be greater than 32,768 and less than 262,143.
machine_name	The node name of the machine. To obtain the node name on aWindows 2003 Server system, see your system administrator. To obtain the node name on a UNIX system, run the uname-n command.
APPDIR = string	A list of one or more directories in which application and administrative servers are booted on this machine. For Windows, the value of a string is the absolute pathname of one directory, optionally followed by a semicolon-separated list of pathnames for other directories on the machine being defined. For UNIX, the value of string is the absolute pathname of one directory, optionally followed by a colon-separated list of pathnames for other directories on the machine being defined.
TUXCONFIG = string	The absolute pathname of the device or system file where the binary TUXCONFIG file is to be created on this machine. The TUXCONFIG file is created by running the tmloadcf(1) command on the UBBCONFIG file.
TUXDIR = string	The absolute pathname of the product directory of the Oracle Tuxedo software on this machine.

You must define APPDIR, TUXCONFIG, and TUXDIR for every machine in your Oracle Tuxedo application. If you need to look up other parameters when editing your UBBCONFIG file, see reference page UBBCONFIG(5) in OracleTuxedo File Formats, Data Descriptions, MIBs, and System Processes Reference.

You must edit your UBBCONFIG file before running tmloadcf(1) to verify the IPC requirements in the section that follows. If you run tmloadcf without first editing the UBBCONFIG file, the command fails with syntax errors.