Editing a UBBCONFIG File

Each BEA TUXEDO application has a configuration file, commonly called the UBBCONFIG file, which specifies the application parameters that are installation dependent. Typically, the configuration file has a name that begins with ubb and ends with something mnemonic, such as ubbsimple. If you are not using the Web-based GUI, you will probably have to edit this file before you can boot the application.

As an example, we show the configuration file from the Simple Application, found in $TUXDIR/apps/simpapp. The configuration file is called ubbsimple.

Figure 1 shows ubbsimple the way it is delivered.

Fig. 1: The ubbsimple configuration file

#ident	"@(#)apps:simpapp/ubbsimple	60.3"
#Skeleton UBBCONFIG file for the TUXEDO Simple Application.
#Replace the  items with the appropriate values.
*RESOURCES
IPCKEY		
#Example:
#IPCKEY		123456
MASTER		simple
MAXACCESSERS	5
MAXSERVERS	5
MAXSERVICES	10
MODEL		SHM
LDBAL		N
*MACHINES
DEFAULT:
		APPDIR=<"replace with the current directory pathname>"
		TUXCONFIG=""
		TUXDIR=""
#Example:
#		APPDIR="/home/me/simpapp"
#		TUXCONFIG="/home/me/simpapp/tuxconfig"
#		TUXDIR="/usr/tuxedo"
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

IPCKEY

carries 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

is the node name of the machine. To obtain the node name on a UNIX system, run the uname -n command. If you are using an NT platform and you do not know the node name of your machine, see your system administrator.

APPDIR = string_value

APPDIR refers to directories in which application and administrative servers will be booted. string_value is the absolute pathname of that directory, optionally followed by a colon-separated list of other directory pathnames, on the machine being defined.

TUXCONFIG = string_value

TUXCONFIG is the binary version of the UBBCONFIG file, produced by tmloadcf(1). string_value is the absolute pathname of the file or device of the TUXCONFIG file.

TUXDIR = string_value

names the base directory of the BEA TUXEDO System software. It must be an absolute pathname.

If you need to look up other values when editing your configuration file, the complete syntax can be found on the ubbconfig(5) man page.

Note: The configuration file must be edited before you use tmloadcf(1) to verify the IPC requirements (see the next section), or tmloadcf will fail with syntax errors.

Verifying IPC Requirements

The BEA TUXEDO System uses UNIX system Interprocess Communications (IPC) resources heavily. On many UNIX system platforms the default values for the parameters that control the size and quantity of the various IPC resources are below the minimums needed to run even a modest BEA TUXEDO System application, so it becomes necessary to reset some of the parameters. After editing your configuration file, the next step in determining how things stand with your application is to determine if the IPC resources suffice for the application.

To do this, invoke the tmloadcf(1) command, specifying your edited configuration file as input:

tmloadcf -c ubbconfig

An example of the output is shown in Figure 2, which is based on the values in ubbsimple.

Fig. 2: Output produced by tmloadcf -c

Ipc sizing (minimum /T values only) ...

		Fixed Minimums Per Processor

SHMMIN:	1
SHMALL:	1
SEMMAP:	SEMMNI

		Variable Minimums Per Processor

	SEMUME,		  A				SHMMAX
	SEMMNU,		  *				  *
Node	SEMMNS	SEMMSL	SEMMSL	SEMMNI	MSGMNI	MSGMAP	SHMSEG
------	------	------	------	------	------	------	------
sftuxe      17	     5	    12	 A + 1	    13	    26	   75K

where 1 = A = 8.

The number of expected application clients per processor should
be added to each MSGMNI value.

This output indicates that to run the Simple Application, your UNIX system must have SEMUME, SEMMNU, and SEMMNS set to no less than 17. SEMMSL must be at least 5, and SEMMNI and SEMMAP at least 4 (assuming A is 3). MSGMNI must be at least 13, and MSGMAP at least 26. Finally, the product of SHMMAX and SHMSEG must be at least 75K bytes.

Of course, the IPC values are application dependent, and the numbers in this example reflect a very small configuration. If other applications that use IPC resources are running on the same system with a BEA TUXEDO application, then the requirements of both applications must be satisfied. Keep in mind also that every node participating in an application must have sufficient IPC resources available.

If the current IPC resources are inadequate, you must increase the values of the associated IPC parameters. For instructions on determining and changing the current IPC values for your platform, see the data sheet for your platform in Appendix A.

Creating the Universal Device List and TLOG

The Universal Device List (UDL) is like a map of the BEA TUXEDO System file system. It gets loaded into shared memory when the application is booted. The TLOG refers to a log in which information on transactions is kept until the transaction is completed.

Creating the UDL

To create the UDL, execute the following command before the application has been booted:

tmadmin -c
crdl -z config -b blocks

TUXDIR=tuxdir; export TUXDIR
LD_LIBRARY_PATH=libpath:$LD_LIBRARY_PATH; export LD_LIBRARY_PATH
$TUXDIR/bin/tlisten -d devname -l nlsaddr -u appuid