|
|
|
|
|
|
Running BEA Tuxedo System Clients on a Workstation
After the client programs have been developed and tested, they can be moved to the workstations where they will be available to users.
Verifying the Directory Structure on Workstation Clients
The following table describes the directory structure on a Workstation client after you have installed the Workstation component of the BEA Tuxedo system.
Workstation clients make use of several environment variables. The following table shows the environment variables that are checked by tpinit(3c) or TPINITIALIZE(3cbl) when the workstation client attempts to join the application. See Defining Workstation Clients in Setting Up a BEA Tuxedo Application for details on setting these environment variables.
Other environment variables may be needed by Workstation clients on a UNIX workstation depending on the BEA Tuxedo system features being used. The compilation(5) reference page in BEA Tuxedo File Formats and Data Descriptions Reference explains which variables are needed under what circumstances.
Creating an Environment File
If you have created an environment file, it is read when tpinit(3c) or TPINITIALIZE(3cbl) is called. The following listing shows a sample file that could be used for two different applications.
Environment File
TUXDIR=/opt/tuxedo
[application1]
;this is a comment
/* this is a comment */
#this is a comment
//this is a comment
set FIELDTBLS=app1_flds
set FLDTBLDIR=/opt/app1/udataobj
[application2]
FIELDTBLS=app2_flds
FLDTBLDIR=/opt/app2/udataobj
The format of the file is as follows:
variable=value where variable must begin with an alphabetic or underscore character and contain only alphanumeric or underscore characters, and value may contain any character except newline. where label is the name of the section and follows the same rules for variable above. The label is silently truncated if longer than 31 characters.
or
set variable=value[label]
When you call the tuxreadenv(3c) function, it reads the environment file and adds the environment variables to the environment for the entire process, independent of platform. These variables are available using tuxgetenv(3c) and can be reset using tuxputenv(3c).
void tuxreadenv(char *file, char *label)
If file is NULL, then a default file name is used. The default file names for various platforms are as follows:
If the value of label is NULL, then only variables in the global section are put into the environment. For other values of label, the global section variables plus any variables in a section matching the label are put into the environment.
An error message is printed to the userlog under the following conditions:
Each time tpinit(3c)is called (either explicitly or implicitly by calling another ATMI function), tuxreadenv(3c) is called automatically in Workstation clients. If WSENVFILE is set in the environment, then it designates the environment file; otherwise, NULL is passed to tuxreadenv() for the file name so that the default file is used. If WSAPP is set in the environment, then it is to be used as the section label in the environment file; otherwise, NULL is passed to tuxreadenv() for the label name. Application clients may also call tuxreadenv() explicitly.
The environment is implemented and available in different ways on different platforms. A uniform interface to the environment is provided via the existing tuxgetenv(3c) and tuxputenv(3c) functions. These functions provide access to the following:
|
|
|
|
|
|
Copyright © 2000 BEA Systems, Inc. All rights reserved.
|