Step 6: How to Edit 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 \| Tutorials for Developing BEA Tuxedo ATMI Applications \| Local Topics \| Previous Topic \| Next Topic \| Contents

A configuration file defines how an application runs. bankapp is delivered with two configuration files in the text format described in UBBCONFIG(5): ubbshm, which defines an application on a single computer, and ubbmp, which defines a networked application.

Initialization scripts are provided in the sample applications. In addition, you can generate completed configuration files by .sh for any number up to 10 for your configuration and machines.

In a text editor, familiarize yourself with the ubbshm and ubbmp configuration files for bankapp.

ubbmp Configuration File

         #Copyright (c) 1999 BEA Systems, Inc.
         #All rights reserved

         *RESOURCES  
         IPCKEY                80952
    001  UID                   <user id from id(1)>
    002  GID                   <group id from id(1)>
         PERM                  0660
         MAXACCESSERS          40
         MAXSERVERS            35
         MAXSERVICES           75
         MAXCONV               10
         MAXGTT                20
         MASTER                SITE1,SITE2
         SCANUNIT              10
         SANITYSCAN            12
         BBLQUERY              180
         BLOCKTIME             30
         DBBLWAIT          6
         OPTIONS           LAN,MIGRATE
         MODEL             MP
         LDBAL             Y
         ##SECURITY        ACL
         #
         *MACHINES
    003  <SITE1's uname>  LMID=SITE1
    004                   TUXDIR="<TUXDIR>"
    005                   APPDIR="<APPDIR>"
                          ENVFILE="<APPDIR>/ENVFILE"
                          TLOGDEVICE="<APPDIR>/TLOG"
                          TLOGNAME=TLOG
                          TUXCONFIG="<APPDIR>/tuxconfig"
    006                   TYPE="<machine type>"
                          ULOGPFX="<APPDIR>/ULOG"
    007  <SITE2's uname>  LMID=SITE2
                          TUXDIR="<TUXDIR>"
                          APPDIR="<APPDIR>"
                          ENVFILE="<APPDIR>/ENVFILE"
                          TLOGDEVICE="<APPDIR>/TLOG"
                          TLOGNAME=TLOG
                          TUXCONFIG="<APPDIR>/tuxconfig"
                          TYPE="<machine type>"
                          ULOGPFX="<APPDIR>/ULOG"
         #
         *GROUPS
         #
         # Group for Authentication Servers
         #
         Group for Application Queue (/Q) Servers
         #
         ##QGRP1      LMID=SITE1    GRP=102
         ##       TMSNAME=TMS_QM    TMSCOUNT=2
         ##       OPENINFO="TUXEDO/QM:<APPDIR>/qdevice:QSP_BANKAPP"
         #
         # Group for Event Broker Servers
         #
         ##EVBGRP1     LMID=SITE1    GRPNO=104

         DEFAULT: TMSNAME=TMS_SQL   TMSCOUNT=2
         BANKB1   LMID=SITE1        GRPNO=1

    008  OPENINFO="TUXEDO/SQL:<APPDIR>/bankdl1:bankdb:readwrite"
         BANKB2   LMID=SITE2         GRPNO=2
         OPENINFO="TUXEDO/SQL:<APPDIR>/bankdl2:bankdb:readwrite"
         *NETWORK
    009  SITE1     NADDR="<network address of SITE1>"
    010            NLSADDR="<network listener address of SITE1>"
    011  SITE2     NADDR="<network address of SITE2>"
    012            NLSADDR="<network listener address of SITE2>"

To enable the application password feature, add the following line to the RESOURCES section of ubbshm or ubbmp:
```
    SECURITY       APP_PW
```

In both configuration files, you may notice that the values of some parameters are enclosed in angle brackets (< >). Values shown in angle brackets are generic; you need to replace them with values that pertain to your installation. All of these fields occur within the RESOURCES, MACHINES, and GROUPS sections in both files. In ubbmp, the NETWORK section also has values you must replace. The following table shows the ubbmp through the NETWORK section and illustrates all the changes you need to make in the RESOURCES, MACHINES, and GROUPS sections if you are bringing up a single-machine application.

Explanation of Values

Line	String to Be Replaced	Description
001	UID	The effective user ID (UID) for the owner of the bulletin board IPC structures. In a multiprocessor configuration, the value must be the same on all machines. To avoid problems, use the same UID as that of the owner of the BEA Tuxedo system software.
002	GID	The effective group ID (GID) for the owner of the bulletin board IPC structures. In a multiprocessor configuration, the value must be the same on all machines. Users of the application should share this group ID.
003	SITE1 name	The name of the machine. (For UNIX platforms, use the value produced by the UNIX command: uname -n)
004	TUXDIR	The absolute path name of the root directory for the BEA Tuxedo software. Replace all occurrences of <TUXDIR> in the file with the specified path name.
005	APPDIR	The absolute path name of the directory in which the application runs. Make this a global change so that all occurrences of <APPDIR> in the file are replaced by the specified path name.
006	machine type	An identifying string used in networked applications that include machines of different types. The BEA Tuxedo system checks the value of machine type for each machine communicating with another. If the system identifies two machines with different machine types trying to communicate, it invokes the message encode and decode routines to convert the data being transmitted to a form recognizable by both machines.
007	SITE2 name	The name of the second machine. (For UNIX platforms, use the value produced by the UNIX command: uname -n)
008	OPENINFO	The statement here and in the following entry are in a format understood by BEA Tuxedo system resource managers. They need to be changed (or removed) to meet the requirements of other resource managers.
009	Network address of SITE1	The full address of the network listener for the BRIDGE process on this machine.
010	Network listener address of SITE1	The address of the network listener for the tlisten process on this machine.
011	Network address of SITE2	The full address of the network listener for the BRIDGE process on this machine. This value must be different on each machine.
012	Network listener address of SITE2	The address of the network listener for the tlisten process on this machine.