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   |   Installation   |   Topic List   |   Previous   |   Next   |   Contents

   Installing the BEA Tuxedo System

Each BEA Tuxedo application is controlled by a configuration file in which installation-dependent parameters are defined. The configuration file for an application usually requires editing before the application can be booted.

In the BEA Tuxedo documentation this file is referred to as UBBCONFIG(5), but you can give your configuration file any name you like. 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 configuration file for a rudimentary sample application called simpapp, that is delivered with the BEA Tuxedo System. On UNIX platforms, this application is found in $TUXDIR/samples/atmi/simpapp; on Windows platforms, it is found in %TUXDIR%\samples\atmi\simpapp.

The following sample listing shows ubbsimple as delivered on a UNIX platform.

 #ident "@(#)apps:simpapp/ubbsimple   $Revision: 1.1 $
 
 #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>"
 #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

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.

This 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 a UNIX system, run the uname -n command. If you are using a Windows NT platform and you do not know the node name of your machine, see your system administrator.
APPDIR = string	A list of one or more directories in which application and administrative servers will be booted. The value of string is the absolute path name of one directory, optionally followed by a colon-separated list of path names for other directories on the machine being defined.
TUXCONFIG = string	The binary version of UBBCONFIG(5) (the text-format configuration file). TUXCONFIG is produced by running the tmloadcf(1) command on UBBCONFIG. The value of string is the absolute path name of the TUXCONFIG file.
TUXDIR = string	The base directory of the BEA Tuxedo system software. It must be an absolute path name.

If you need to look up other parameters when editing your configuration file, see the UBBCONFIG(5) reference page in the BEA Tuxedo File Formats and Data Descriptions Reference.

Note: You must edit the configuration file before running tmloadcf(1) to verify the IPC requirements (see Verifying IPC Requirements on a UNIX System). If you run tmloadcf without first editing the configuration file, the command will fail with syntax errors.