Table of Contents Previous Next PDF

Programming Environment

Programming Environment
This topic includes the following sections:
Updating the UBBCONFIG Configuration File
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:
Copy and edit a file that already exists. For example, the file ubbshm that comes with the bankapp sample application can provide a good starting point.
Make sure the IPCKEY parameter in the configuration file does not conflict with any other parameters being used at your installation. Check with your Oracle Tuxedo application administrator, and refer to Setting Up an Oracle Tuxedo Application for more information.
Set the UID and GID parameters so that you are the owner of the configuration.
Review the documentation. The configuration file is described in UBBCONFIG(5) in the File Formats, Data Descriptions, MIBs, and System Processes Reference.
Table 3‑1 summarizes the UBBCONFIG configuration file parameters that affect the programming environment. Parameters are listed by functional category.
Specifies the minimum and maximum number of occurrences of the server to be started by tmboot(1). If not specified, MIN defaults to 1 and MAX defaults to MIN. The same parameters are available for use with request/response servers. However, conversational servers are automatically spawned as needed. So if you set MIN=1 and MAX=10, for example, tmboot starts one server initially. When a tpconnect() call is made to a service offered by that server, the system starts a second copy of a server. As each copy is called, a new one is spawned, up to a limit of 10.
Controls whether a service routine is placed in transaction mode. If you set this parameter to Y, a transaction in the service subroutine is automatically started whenever a request message is received from another process.
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.
See Also
UBBCONFIG(5) in the File Formats, Data Descriptions, MIBs, and System Processes Reference
Setting Environment Variables
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 an Oracle Tuxedo Application for more information.)
For the client and server routines in your application, you can update existing environment variables or create new ones. Table 3‑2 summarizes the most commonly used environment variables. The variables are listed by functional category.
Non-Null or Null value that determines whether the encoding of the MBSTRING data or the FLD_MBSTRING field data in an FML32 typed buffer is converted when received by the destination process.
Absolute path of the directory to store the cached files. If the URLENTITYCACHING flag is turned on and no path is specified, the current working directory is used to store the cached files (provided appropriate permissions are set.).
If operating in a UNIX environment, add $TUXDIR/bin to your environment PATH to ensure that your application can locate the executables for the Oracle Tuxedo system commands. For more information on setting up the environment, see Setting Up an Oracle Tuxedo Application.
See Also
“Setting Up Your Environment for FML and VIEWS” in Programming Oracle Tuxedo ATMI Applications Using FML
Including the Required Header Files
Table 3‑3 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 Oracle Tuxedo system.
atmi.h header file supplied by the Oracle Tuxedo system
fml.h header file supplied by the Oracle Tuxedo system
Starting and Stopping the Application
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.
See Also
tmboot(1) and tmshutdown(1) in the Oracle Tuxedo Command Reference

Copyright © 1994, 2017, Oracle and/or its affiliates. All rights reserved.