Programming a Tuxedo ATMI Application Using C
This topic includes the following sections:
The application administrator initially defines the configuration settings for an application in the UBBCONFIG
configuration file. To customize your programming environment, you may need to create or update a configuration file.
If you need to create or update a configuration file, refer to the following guidelines:
ubbshm
that comes with the bankapp
sample application can provide a good starting point.IPCKEY
parameter in the configuration file does not conflict with any other parameters being used at your installation. Check with your BEA Tuxedo application administrator, and refer to Setting Up a BEA Tuxedo Application for more information.UID
and GID
parameters so that you are the owner of the configuration.The following table summarizes the UBBCONFIG
configuration file parameters that affect the programming environment. Parameters are listed by functional category.
Specifies the maximum number of servers in the configuration. When setting this value, you need to consider the |
|||
Specifies the maximum total number of services in the configuration. |
|||
List of types and subtypes of data buffers for which the specified routing entry is valid. |
|||
Flag for specifying whether or not load balancing is enabled. If enabled, the BEA Tuxedo system attempts to balance requests across the network. |
|||
Numeric value that is added to the load factor of services that are remote from the invoking client, providing a bias for choosing a local server over a remote server. Load balancing must be enabled (that is, |
|||
Relative load factor associated with a service instance. The default is 50. |
|||
Specifies the name of an application authentication service that is invoked by the system for each client joining the system. |
|||
Sets the maximum number of simultaneous conversations for a single machine. You can specify a value between 0 and 32,767. The default is 64 if any conversational servers are defined in the |
|||
Specifies whether or not conversational communication is supported. If this parameter is set to |
|||
Specifies the minimum and maximum number of occurrences of the server to be started by tmboot(1). If not specified, |
|||
Controls whether a service routine is placed in transaction mode. If you set this parameter to |
|||
Specifies in seconds the maximum timeout allowed for transactions started in or received by this BEA Tuxedo application. |
|||
Specifies the maximum number of concurrently dispatched threads that each server process may spawn. |
|||
Specifies the number of server dispatch threads started on initial server boot. |
The configuration file is an operating system text file. To make it usable by the system, you must execute the tmloadcf(1) command to convert the file to a binary file.
Initially, the application administrator sets the variables that define the environment in which your application runs. These environment variables are set by assigning values to the ENVFILE
parameter in the MACHINES
section of the UBBCONFIG
file. (Refer to Setting Up a BEA Tuxedo Application for more information.)
For the client and server routines in your application, you can update existing environment variables or create new ones. The following table summarizes the most commonly used environment variables. The variables are listed by functional category.
buildclient(1) and buildserver(1) commands. |
|||
Link edit flags to be passed to the C compiler. Link edit flags are optional. |
buildclient(1) and buildserver(1) commands. |
||
BEA Tuxedo application programs that perform data compression. |
|||
Numeric value that is added to the load value for remote queues, making the remote queues appear to have more work than they actually do. As a result, even if load balancing is enabled, local requests are sent to local queues more often than to remote queues. |
BEA Tuxedo application programs that perform load balancing. |
||
Comma-separated list of field table filenames for FML and FML32 typed buffers, respectively. Required only for FML and VIEW types. |
|||
Colon-separated list of directories to be searched for the field table files for FML and FML32, respectively. For Windows 2003, a semicolon-separated list is used. |
|||
Comma-separated list of allowable filenames for VIEW and VIEW32 typed buffers, respectively. |
|||
Colon-separated list of directories to be searched for VIEW and VIEW32 files, respectively. For Windows 2003, a semicolon-separated list is used. |
|||
Code-set encoding name to be included in an MBSTRING typed buffer or in an |
|||
Non-Null or Null value that determines whether the encoding of the MBSTRING data or the |
|||
Flag to turn caching on/off for externally referenced files (DTD, Schemas, and entity reference.) |
|||
Absolute path of the directory to store the cached files. If the |
|||
Absolute path to a file containing pairs of XercesDOMParser class attributes and settings. |
BEA Tuxedo application programs that automatically parse XML data to and from FML/FML32 data. |
If operating in a UNIX environment, add $TUXDIR/bin
to your environment PATH
to ensure that your application can locate the executables for the BEA Tuxedo system commands. For more information on setting up the environment, see Setting Up a BEA Tuxedo Application.
The following table summarizes the header files that may need to be specified within the application programs, using the #include
statement, in order to interface properly with the BEA Tuxedo system.
Table 2-3 Required Header Files
To start the application, execute the tmboot(1) command. The command gets the IPC resources required by the application, and starts administrative processes and application servers.
To stop the application, execute the tmshutdown(1) command. The command stops the servers and releases the IPC resources used by the application, except any that might be used by the resource manager, such as a database.