How to Propagate the BEA Tuxedo System Software


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

Administering a BEA Tuxedo Application at Run Time

TUXCONFIG is propagated automatically to all machines in your configuration by the BEA Tuxedo system when you run tmboot(1). There are, however, other files that you need to propagate manually. Following is a list of the files and directories that you need to create for a networked application. First, install the BEA Tuxedo system on the machine.

Directories and Files to Propagate

Directory/File
Description

APPDIR

You must create the directory named in the APPDIR variable must be created on each node. It is easier if this directory has the same path name on all nodes.

Executables

You must build one set of application servers for each platform, and manually propagate the appropriate set to all machines running on each platform (that is, the BEA Tuxedo system does not do this automatically). Store the executables in APPDIR, or in a directory specified in a PATH variable in ENVFILES in the MACHINES section of your configuration file.

Field tables
VIEW tables

If FML or VIEWS buffer types are used, field tables and VIEW description files must be manually propagated to the machines where they are used, and then recompiled. Use mkfldhdr, mkfldhdr32(1) to make a header file out of a field table file; use viewc, viewc32(1) to compile a VIEW file. The FML field tables and VIEW description files should be available through the environment variables FLDTBLDIR, FIELDTBLS, VIEWDIR, and VIEWFILES, or their 32-bit equivalents.

tlisten

The tlisten process must be started on each machine of a networked BEA Tuxedo application before the application is booted. Refer to the tlisten(1) reference page.

You must define TUXDIR, TUXCONFIG, APPDIR, and other relevant environment variables before starting tlisten.

Directory/File	Description
APPDIR	You must create the directory named in the APPDIR variable must be created on each node. It is easier if this directory has the same path name on all nodes.
Executables	You must build one set of application servers for each platform, and manually propagate the appropriate set to all machines running on each platform (that is, the BEA Tuxedo system does not do this automatically). Store the executables in APPDIR, or in a directory specified in a PATH variable in ENVFILES in the MACHINES section of your configuration file.
Field tables VIEW tables	If FML or VIEWS buffer types are used, field tables and VIEW description files must be manually propagated to the machines where they are used, and then recompiled. Use mkfldhdr, mkfldhdr32(1) to make a header file out of a field table file; use viewc, viewc32(1) to compile a VIEW file. The FML field tables and VIEW description files should be available through the environment variables FLDTBLDIR, FIELDTBLS, VIEWDIR, and VIEWFILES, or their 32-bit equivalents.
tlisten	The tlisten process must be started on each machine of a networked BEA Tuxedo application before the application is booted. Refer to the tlisten(1) reference page. You must define TUXDIR, TUXCONFIG, APPDIR, and other relevant environment variables before starting tlisten.