File Formats, Data Descriptions, MIBs, and System Processes Reference
The T_MACHINE
class represents application attributes pertaining to a particular machine. These attribute values represent machine characteristics, per-machine sizing, statistics, customization options, and UNIX system filenames.
(k)— |
TA_LMID
and TA_PMID
must each be unique within this class. Only one of these fields is required as a key field for a SET
operation. If both are specified, they must match the same object.T_DOMAIN
class.TA_APPDIR
for this machine followed by /ULOG
.Logical machine identifier. This identifier is used within the rest of the TM_MIB
definition as the sole means of mapping application resources to T_MACHINE
objects.
Physical machine identifier. This identifier should match the UNIX system nodename as returned by the "uname -n
" command when run on the identified system.
TA_TUXCONFIG
: string
[2..256] (up to 64 bytes for BEA Tuxedo 8.0 or earlier)
Absolute pathname of the file or device where the binary BEA Tuxedo system configuration file is found on this machine. The administrator need only maintain one such file, namely the one identified by the TA_TUXCONFIG
attribute value on the master machine. The information contained in this file is automatically propagated to all other T_MACHINE
objects as they are activated. See TA_ENVFILE
in this class for a discussion of how this attribute value is used in the environment.
TA_TUXDIR
: string
[2..256] (up to 78 bytes for BEA Tuxedo 8.0 or earlier)
Absolute pathname of the directory where the BEA Tuxedo system software is found on this machine. See TA_ENVFILE
in this class for a discussion of how this attribute value is used in the environment.
TA_APPDIR
: string
[2..256] (up to 78 bytes for BEA Tuxedo 8.0 or earlier)
colon-separated list of application directory absolute pathnames. The first directory serves as the current directory for all application and administrative servers booted on this machine. All directories in the list are searched when starting application servers. See TA_ENVFILE
in this class for a discussion of how this attribute value is used in the environment.
A GET
operation will retrieve configuration and run-time information for the selected T_MACHINE
object(s). The following states indicate the meaning of a TA_STATE
returned in response to a GET
request.
SET
: "
{NEW
| INValid
| ACTive
| ReACtivate
| INActive
| ForceINactive
| CLEaning
}"
A SET
operation will update configuration and run-time information for the selected T_MACHINE
object. The following states indicate the meaning of a TA_STATE
set in a SET
request. States not listed may not be set.
Limitation: State change to ForceINactive
or INActive
allowed only for non-master machines. The master site administrative processes are deactivated via the T_DOMAIN
class.
UNIX system user identifier for the BEA Tuxedo system application administrator on this machine. Administrative commands such as tmboot(1), tmshutdown(1), and tmadmin(1) must run as the indicated user on this machine. Application and administrative servers on this machine will be started as this user.
Limitation: This is a UNIX system-specific attribute that may not be returned if the platform on which the application is being run is not UNIX-based.
UNIX system group identifier for the BEA Tuxedo system application administrator on this machine. Administrative commands such as tmboot(1), tmshutdown(1), and tmadmin(1) must run as part of the indicated group on this machine. Application and administrative servers on this machine will be started as part of this group.
Limitation: This is a UNIX system-specific attribute that may not be returned if the platform on which the application is being run is not UNIX-based.
TA_ENVFILE
: string
[0..256] (up to 78 bytes for BEA Tuxedo 8.0 or earlier)
Environment file for clients and servers running on this machine. If the value specifies an invalid filename, no values are added to the environment. the value of string
is placed into the environment.
When booting servers, local servers inherit the environment of tmboot(1) and remote servers (not on the MASTER
) inherit the environment of tlisten(1). TUXCONFIG
, TUXDIR
, and APPDIR
are also put into the environment when a server is booted based on the information in the associated T_MACHINE
object. PATH
will be set in the environment to:
where path
is the value of the first PATH
= line appearing in the machine environment file, if one exists (subsequent PATH
= lines will be ignored). This PATH
will be used as a search path for servers that are specified with a simple or relative pathname (that is, that doesn't begin with slash). LD_LIBRARY_PATH
will be set in the environment to:
where lib
is the value of the first LD_LIBRARY_PATH
= line appearing in the machine environment file, if one exists (subsequent LD_LIBRARY_PATH
= lines will be ignored).
As part of server initialization (before tpsvrinit()
is called), a server will read and export variables from both the machine and server ENVFILE
files. If a variable is set in both the machine and server ENVFILE
, the value in the server ENVFILE
will override the value in the machine ENVFILE
with the exception of PATH
which is appended. A client will process only the machine ENVFILE
file. When the machine and server ENVFILE
files are processed, lines that are not of the form ident
=
will be ignored, where ident
begins with an underscore or alphabetic character, and contains only underscore or alphanumeric characters. If a PATH=
line is encountered, PATH
will be set to:
where path
is the value of the first PATH
= line appearing in the environment file (subsequent PATH
= lines are ignored). If PATH
appears in both the machine and server files, path
is path1:path2
, where path1
is from the machine ENVFILE
, and path2
is from the server ENVFILE
. If a LD_LIBRARY_PATH
= line is encountered, LD_LIBRARY_PATH
will be set to:
where lib
is the value of the first LD_LIBRARY_PATH
= line appearing in the environment file (subsequent LD_LIBRARY_PATH
= lines are ignored). Attempts to reset TUXDIR
, APPDIR
, or TUXCONFIG
will be ignored and a warning will be printed if the value does not match the corresponding T_MACHINE
attribute value. Limitation: Modifications to this attribute for an active object will not affect running servers or clients.
UNIX system permissions associated with the shared memory bulletin board created on this machine. Default UNIX system permissions for system and application message queues.
Limitations: Modifications to this attribute for an active object will not affect running servers or clients.
This is a UNIX system-specific attribute that may not be returned if the platform on which the application is being run is not UNIX-based.
TA_ULOGPFX
: string
[0..256] (up to 78 bytes for BEA Tuxedo 8.0 or earlier)
Absolute pathname prefix of the path for the userlog()
file on this machine. The userlog()
filename is formed by appending the string .
mmddyy
to the TA_ULOGPFX
attribute value. mmddyy
represents the month, day, and year that the messages were generated. All application and system userlog()
messages generated by clients and servers running on this machine are directed to this file.
Limitation: Modifications to this attribute for an active object will not affect running servers or clients.
Machine type. Used to group machines into classes of like data representations. Data encoding is not performed when communicating between machines of identical types. This attribute can be given any string value; values are used only for comparison. Distinct TA_TYPE
attributes should be set when the application spans a heterogeneous network of machines or when compilers generate dissimilar structure representations. The default for this attribute, a 0-length string, matches any other machine with a 0-length string as its TA_TYPE
attribute value.
Maximum number of clients and servers that can be simultaneously connected to the bulletin board on this machine. If not specified, the default is the TA_MAXACCESSERS
value specified in the T_DOMAIN
class.
System administration processes, such as the BBL, restartsrv
, cleanupsrv
, tmshutdown()
, and tmadmin()
, need not be accounted for in this value, but the DBBL, all bridge processes, all system-supplied and application server processes, and all potential client processes at this site need to be counted. (Examples of system-supplied servers are AUTHSVR
, TMQUEUE
, TMQFORWARD
, TMUSREVT
, TMSYSEVT
, TMS
—see T_GROUP
TA_TMSNAME
attribute, TMS_QM
, GWTDOMAIN
, and WSL
.) If the application is booting workstation listeners (WSLs) on this site, both the WSLs and the number of potential workstation handlers (WSHs) that may be booted need to be counted.
Note that for BEA Tuxedo pre-release 7.1 (6.5 or earlier), both the TA_MAXACCESSERS
and TA_MAXSERVERS
(see T_DOMAIN
:TA_MAXSERVERS
attribute) attributes for an application play a part in the user license checking scheme. Specifically, a machine is not allowed to boot if the number of TA_MAXACCESSERS
for that machine + the number of TA_MAXACCESSERS
for the machine (or machines) already running in the application is greater than the number of TA_MAXSERVERS
+ user licenses for the application. Thus, the total number of TA_MAXACCESSERS
for an application must be less than or equal to the number of TA_MAXSERVERS
+ user licenses for the application.
Note also that the user license checking scheme in BEA Tuxedo release 7.1 or later considers only the following two factors when performing its checks: the number of user licenses for an application and the number of licenses currently in use for the application. When all user licenses are in use, no new clients are allowed to join the application.
Maximum number of simultaneous conversations in which clients and servers on this machine can be involved. If not specified, the default is the TA_MAXCONV
value specified in the T_DOMAIN
class. The maximum number of simultaneous conversations per server is 64.
Maximum number of simultaneous global transactions in which this machine can be involved. If not specified, the default is the value specified in the T_DOMAIN
class.
Number of accesser entries on this machine to be reserved for Workstation clients (as opposed to native clients). If TA_MAXWSCLIENTS
is not specified, the default is 0.
The number specified here takes a portion of the total accesser slots specified with TA_MAXACCESSERS
, meaning that the accesser slots reserved for TA_MAXWSCLIENTS
are unavailable for use by other clients and servers on this machine. It is an error to set this number greater than TA_MAXACCESSERS
.
The TA_MAXWSCLIENTS
attribute is only used when the BEA Tuxedo system Workstation feature is used. The appropriate setting of this attribute helps to conserve interprocess communication (IPC) resources since Workstation client access to the system is multiplexed through a BEA Tuxedo system-supplied surrogate, the workstation handler (WSH).
Number of entries in the cache used for ACL entries when TA_SECURITY
is set to ACL
or MANDATORY_ACL
. The appropriate setting of this attribute helps to conserve on shared memory resources and yet reduce the number of disk access to do ACL checking.
TA_TLOGDEVICE
: string
[0..256] (up to 64 bytes for BEA Tuxedo 8.0 or earlier)
The device (raw slice) or UNIX system file containing the BEA Tuxedo filesystem that holds the DTP transaction log for this machine. The DTP transaction log is stored as a BEA Tuxedo system VTOC table on the device. This device or file may be the same as that specified for the TA_TUXCONFIG
attribute for this machine.
The name of the DTP transaction log for this machine. If more than one DTP transaction log exists on the same TA_TLOGDEVICE
, they must have unique names. TA_TLOGNAME
must be different from the name of any other table on the TA_TLOGDEVICE
where the DTP transaction log table is created.
The numeric size, in pages, of the DTP transaction log for this machine. The TA_TLOGSIZE
attribute value is subject to limits based on available space in the BEA Tuxedo filesystem identified by the TA_TLOGDEVICE
attribute.
Device name to be used by the Bridge process for this logical machine to access the network. This value is required for participation in a networked application via a TLI-based BEA Tuxedo system binary. This attribute is not needed for sockets-based BEA Tuxedo system binaries.
The Bridge process for this logical machine is configured for multithreaded execution ("Y"
) or single-threaded execution ("N"
). The default is "N"
. This attribute applies only to applications running BEA Tuxedo 8.1 or later software.
Setting TA_BRTHREADS
to "Y"
makes sense only if a machine has multiple CPUs. However, having multiple CPUs is not a prerequisite for setting TA_BRTHREADS
to "Y"
.
Configurations with TA_BRTHREADS
set to "Y"
on the local machine and TA_BRTHREADS
set (or defaulted) to "N"
on the remote machine are allowed, but the throughput between the machines will not be greater than that for the single-threaded Bridge process.
A Bridge process configured for single-threaded or multithreaded execution can interoperate with a Bridge process running in an earlier release of BEA Tuxedo or WebLogic Enterprise: BEA Tuxedo release 8.0 or earlier, WebLogic Enterprise release 5.1 or earlier. In general, a threaded Bridge can interoperate with an unthreaded Bridge because there are no external functional or behavioral changes due to the threading.
TA_NADDR
: string
[0..256] (up to 78 bytes for BEA Tuxedo 8.0 or earlier)
Specifies the complete network address to be used by the Bridge process placed on the logical machine as its listening address. The listening address for a Bridge is the means by which it is contacted by other Bridge processes participating in the application. This attribute must be set if the logical machine is to participate in a networked application, that is, if the LAN
option is set in the T_DOMAIN
:TA_OPTIONS
attribute value.
If string
has the form "0x
hex-digits
"
or "\\x
hex-digits
"
, it must contain an even number of valid hex digits. These forms are translated internally into a character array containing the hexadecimal representations of the string specified. For TCP/IP addresses either the
TA_NLSADDR
: string
[0..256] (up to 78 bytes for BEA Tuxedo 8.0 or earlier)
Network address used by the tlisten(1) process servicing the network on the node identified by this logical machine. This network address is of the same format as that specified for the TA_NADDR
attribute above.
This attribute must be set if the logical machine is to participate in a networked application, that is, if the LAN
option is set in the T_DOMAIN
:TA_OPTIONS
attribute value.
TA_FADDR:
string
[0..256] (up to 78 bytes for BEA Tuxedo 8.0 or earlier)
Specifies the complete network address to which local processes such as tmboot
, tmloadcf
, and Bridge can bind before making an outbound connection. This address must be a TCP/IP address. This attribute, along with the TA_FRANGE
attribute, determines the range of TCP/IP ports to which a process attempts to bind before making an outbound connection. If this attribute is set to the NULL or empty string, the operating system randomly chooses a local port with which to bind.
If string
has the form "0x
hex-digits
"
, it must contain an even number of valid hex digits. These forms are translated internally into a character array containing the hexadecimal representations of the string specified.
Specifies the range of TCP/IP ports to which local processes attempt to bind before making an outbound connection. The TA_FADDR
attribute specifies the base address of the range.
Threshold message size at which compression will occur for remote
traffic and optionally local
traffic. remote
and local
may be either non-negative numeric values or the string MAXLONG
, which is dynamically translated to the maximum long setting for the machine. Setting only the remote
value will default local
to MAXLONG
.
Limitation: This attribute value is not part of the T_MACHINE
object for active sites running BEA Tuxedo system release 4.2.2 or earlier. However, site release identification is not determined until run time, so this attribute may be set and accessed for any inactive object. When a BEA Tuxedo release 4.2.2 or earlier site is activated, the configured value is not used.
Service load added to any remote service evaluated during load balancing on this machine.
Limitation: This attribute value is not part of the T_MACHINE
object for active sites running BEA Tuxedo release 4.2.2 or earlier. However, site release identification is not determined until run time, so this attribute may be set and accessed for any inactive object. When a BEA Tuxedo release 4.2.2 or earlier site is activated, the configured value is not used.
Spincount used on this machine for pre-ticket user level semaphore access. Defaults are built into the BEA Tuxedo system binaries on each machine. These defaults may be overridden at run time for tuning purposes using this attribute. The spincount may be reset to the default built-in value for the site by resetting this attribute value to 0. There is also a TMSPINCOUNT
environment variable, which the system uses if the value is not set here or in the UBBCONFIG
file.
Limitation: This attribute value is not part of the T_MACHINE
object for active sites running BEA Tuxedo release 4.2.2 or earlier. However, site release identification is not determined until run time, so this attribute may be set and accessed for any inactive object. When a BEA Tuxedo release 4.2.2 or earlier site is activated, the configured value is not used.
The role of this machine in the application. "MASTER"
indicates that this machine is the master machine, "BACKUP"
indicates that it is the backup master machine, and "OTHER"
indicates that the machine is neither the master nor backup master machine.
The BEA Tuxedo system major protocol release number for this machine. This may be different from the TA_SWRELEASE
for the same machine.
Specifies the minimum level of encryption required when establishing a network link to this machine. 0
means no encryption, while 40
, 56
, and 128
specify the encryption key length (in bits). If this minimum level of encryption cannot be met, link establishment will fail. The default is 0
.
Note: The link-level encryption value of 40 bits is provided for backward compatibility.
Limitation: Modifications to this attribute will not effect established network links.
Specifies the maximum level of encryption that can be negotiated when establishing a network link. 0
means no encryption, while 40
, 56
, and 128
specify the encryption length (in bits). The default is 128
.
Note: The link-level encryption value of 40 bits is provided for backward compatibility.
Limitation: Modifications to this attribute will not effect established network links.
Specifies a limit for the amount of space that can be allocated for messages waiting to be transmitted by the Bridge process.
The number of service and interface cache entries kept on this machine. If not specified, the value will be set to "500". A value of "0" implies that service caching is not used on this machine.
Security principal name identification string to be used for authentication purposes by an application running BEA Tuxedo 7.1 or later software. This attribute may contain a maximum of 511 characters (excluding the terminating NULL character). The principal name specified for this attribute becomes the identity of one or more system processes running on this machine.
TA_SEC_PRINCIPAL_NAME
can be specified at any of the following four levels in the configuration hierarchy: T_DOMAIN
class, T_MACHINE
class, T_GROUP
class, and T_SERVER
class. A principal name at a particular configuration level can be overridden at a lower level. If TA_SEC_PRINCIPAL_NAME
is not specified at any of these levels, the principal name for the application defaults to the TA_DOMAINID
string for this domain.
Note that TA_SEC_PRINCIPAL_NAME
is one of a trio of attributes, the other two being TA_SEC_PRINCIPAL_LOCATION
and TA_SEC_PRINCIPAL_PASSVAR
. The latter two attributes pertain to opening decryption keys during application booting for the system processes running in a BEA Tuxedo 7.1 or later application. When only TA_SEC_PRINCIPAL_NAME
is specified at a particular level, the system sets each of the other two attributes to a NULL
(zero length) string.
Location of the file or device where the decryption (private) key for the principal specified in TA_SEC_PRINCIPAL_NAME
resides. This attribute may contain a maximum of 511 characters (excluding the terminating NULL character).
TA_SEC_PRINCIPAL_LOCATION
can be specified at any of the following four levels in the configuration hierarchy: T_DOMAIN
class, T_MACHINE
class, T_GROUP
class, and T_SERVER
class. When specified at any of these levels, this attribute must be paired with the TA_SEC_PRINCIPAL_NAME
attribute; otherwise, its value is ignored. (TA_SEC_PRINCIPAL_PASSVAR
is optional; if not specified, the system sets it to a NULL
—zero length—string.)
Variable in which the password for the principal specified in TA_SEC_PRINCIPAL_NAME
is stored. This attribute may contain a maximum of 511 characters (excluding the terminating NULL character).
TA_SEC_PRINCIPAL_PASSVAR
can be specified at any of the following four levels in the configuration hierarchy: T_DOMAIN
class, T_MACHINE
class, T_GROUP
class, and T_SERVER
class. When specified at any of these levels, this attribute must be paired with the TA_SEC_PRINCIPAL_NAME
attribute; otherwise, its value is ignored. (TA_SEC_PRINCIPAL_LOCATION
is optional; if not specified, the system sets it to a NULL
—zero length—string.)
During initialization, the administrator must provide the password for each of the decryption keys configured with TA_SEC_PRINCIPAL_PASSVAR
. The system automatically encrypts the password entered by the administrator and assigns each encrypted password to the associated password variable.
If set to "Y"
, every process running on this machine requires a digital signature on its input message buffer. If not specified, the default is "N"
. This attribute applies only to applications running BEA Tuxedo 7.1 or later software.
TA_SIGNATURE_REQUIRED
can be specified at any of the following four levels in the configuration hierarchy: T_DOMAIN
class, T_MACHINE
class, T_GROUP
class, and T_SERVICE
class. Setting SIGNATURE_REQUIRED
to Y
at a particular level means that signatures are required for all processes running at that level or below.
If set to "Y"
, every process running on this machine requires an encrypted input message buffer. If not specified, the default is "N"
. This attribute applies only to applications running BEA Tuxedo 7.1 or later software.
TA_ENCRYPTION_REQUIRED
can be specified at any of the following four levels in the configuration hierarchy: T_DOMAIN
class, T_MACHINE
class, T_GROUP
class, and T_SERVICE
class. Setting TA_ENCRYPTION_REQUIRED
to "Y"
at a particular level means that encryption is required for all processes running at that level or below.
Number of clients and servers currently accessing the application either directly on this machine or through a workstation handler on this machine.
Current service load enqueued on this machine. Limitation: If the T_DOMAIN
:TA_LDBAL
attribute is "N"
or the T_DOMAIN
:TA_MODEL
attribute is "MP
", an FML32 NULL
value is returned (0).
High water number of clients and servers accessing the application either directly on this machine or through a workstation handler on this machine.
Software release for binary on that machine or a 0-length string if binary is not a BEA Tuxedo system master binary.
Number of accesses to the ACL cache that resulted in a "hit" (that is, the entry was already in the cache).
Total service load dequeued and processed successfully by servers running on this machine. Note that for long running applications this attribute may wraparound, that is, exceed the maximum value for a long, and start back at 0 again.
SHM
mode (see T_DOMAIN
:TA_MODEL
attribute) applications can have only one T_MACHINE
object. MP
mode (see T_DOMAIN
:TA_MODEL
attribute) applications with the LAN
option set (see T_DOMAIN
:TA_OPTIONS
attribute) may have up to the maximum number of configurable T_MACHINE
objects as defined by the T_DOMAIN
:TA_MAXMACHINES
attribute. Many attributes of this class are tunable only when the application is inactive on the site. Since the master machine must at least be active in a minimally active application, the use of the ATMI interface routines to administer the application is not possible with respect to the master machine object. The function tpadmcall()
is being provided as a means configuring an unbooted application and may be used to set these attributes for the master machine.