|
|
|
|
|
TM_MIB(5)
Name
TM_MIB—Management Information Base for core BEA Tuxedo system
Synopsis
#include <fml32.h>
#include <tpadm.h>
Description
The BEA Tuxedo System MIB defines the set of classes through which the fundamental aspects of an application can be configured and managed. This includes management of machines, servers, networking.
TM_MIB(5) should be used in combination with the generic MIB reference page MIB(5) to format administrative requests and interpret administrative replies. Requests formatted as described in MIB(5) using classes and attributes described in this reference page may be used to request an administrative service using any one of a number of existing ATMI interfaces in an active application. Inactive applications may also be administered using the tpadmcall() function interface. For additional information pertaining to all TM_MIB(5) class definitions, see TM_MIB(5) Additional Information.
TM_MIB(5) consists of the following classes.
Each class description consists of four sections:
Attribute Table Format
Each class that is a part of this MIB is defined in four parts in sections that follow. One of the four parts is the attribute table. The attribute table is a reference guide to the attributes within a class and how they may used by administrators, operators, and general users to interface with an application.
There are five columns for each attribute described in an attribute table: name, type, permissions, values, and default. Each of these components is discussed in MIB(5).
TA_FLAGS Values
MIB(5) defines the generic TA_FLAGS attribute, which is a long containing both generic and component MIB specific flag values. The following are the TM_MIB(5) specific flag values supported. These flag values should be or'd with any generic MIB flags.
FML32 Field Tables
The field table for the attributes described in this reference page is found in the file udataobj/tpadm relative to the root directory of the BEA Tuxedo system software installed on the system. The directory ${TUXDIR}/udataobj should be included by the application in the colon-separated list specified by the FLDTBLDIR environment variable, and the field table name tpadm should be included in the comma-separated list specified by the FIELDTBLS environment variable.
Limitations
Access to the header files and field tables for this MIB is being provided only on BEA Tuxedo release 6.1 sites and later, both native and Workstation.
Workstation access to this MIB is limited to runtime only access; the function tpadmcall(3c) is not supported on workstations.
For the purpose of preimage processing (MIB_PREIMAGE flag bit set), local attributes for classes that have global attributes are not considered. Additionally, indexed fields and the indexes that go with them are not considered, for example, T_TLOG class, TA_TLOGCOUNT, TA_TLOGINDEX, TA_GRPNO, TA_TLOGDATA attributes.
T_BRIDGE Class Definition
Overview
The T_BRIDGE class represents run-time attributes pertaining to connectivity between logical machines making up an application. These attribute values represent connection status and statistics.
Attribute Table
1All attributes in Class T_BRIDGE are local attributes.
2The TA_LMID attribute must be fully specified for SET operations, that is, LMID1,LMID2.
3SET operation may only use TA_NETGROUP DEFAULTNET in BEA Tuxedo release 6.4. GET operation may use any TA_NETGROUP defined for both LMID values.
4TA_SUSPTIME may be SET only if the TA_STATE is currently SUSPENDED or is being SET to SUSPENDED.
5The link-level encryption value of 40 bits is provided for backward compatibility.
Attribute Semantics
Note: The link-level encryption value of 40 bits is provided for backward compatibility.
Limitations
None.
T_CLIENT Class Definition
Overview
The T_CLIENT class represents run-time attributes of active clients within an application. These attribute values identify and track the activity of clients within a running application.
Attribute Table
1All attributes in Class T_CLIENT are local attributes.
2The link-level encryption value of 40 bits is provided for backward compatibility.
Attribute Semantics
Note: The link-level encryption value of 40 bits is provided for backward compatibility.
Note: Some port numbers may be reserved for the underlying transport protocols (such as TCP/IP) used by your system. Check the documentation for your transport protocols to find out which numbers, if any, are reserved on your system.
Limitations
None.
T_CONN Class Definition
Overview
The T_CONN class represents run-time attributes of active conversations within an application.
Attribute Table
1All attributes in Class T_CONN are local attributes.
Attribute Semantics
|
ACTive |
The object returned reflects one or both sides of an active conversation within the application. |
Limitations
None.
T_DEVICE Class Definition
Overview
The T_DEVICE class represents configuration and run-time attributes of raw disk slices or UNIX system files being used to store BEA Tuxedo system device lists. This class allows for the creation and deletion of device list entries within a raw disk slice or UNIX system file.
Attribute Table
1All attributes in Class T_DEVICE are local attributes.
2TA_DEVINDEX is required for SET operations to identify the particular device list entry except when setting the state to NEW for the purpose of creating a new device list entry. In the latter case, TA_DEVINDEX must not be set; a value will be assigned by the system and returned after a successful creation.
3TA_DEVSIZE may only be SET on object creation.
Attribute Semantics
|
VALid |
The BEA Tuxedo filesystem indicated by TA_CFGDEVICE exists and contains a valid device list. TA_DEVICE is a valid device within that filesystem with the device index telnet lchome3. |
Limitations
None.
T_DOMAIN Class Definition
Overview
The T_DOMAIN class represents global application attributes. These attribute values serve to identify, customize, size, secure, and tune a BEA Tuxedo system application. Many of the attribute values represented here serve as application defaults for other classes represented in this MIB.
There is exactly one object of the T_DOMAIN class for each application. Because of this, there are no key fields defined for this class. A GET operation on this class will always return information representing this single object. Likewise, a SET operation will update it. GETNEXT is not permitted with this class.
Attribute Table
1UID and GID as known to the UNIX system
2num must be a multiple of 5
3Specify num so that num times TA_SCANUNIT is approximately "Default"
Attribute Semantics
|
ACTive |
T_DOMAIN object defined and the master machine is active. |
|
INActive |
T_DOMAIN object defined and application is inactive. |
Note: The SIGNAL notification method is not available for MS-DOS clients.
(2) Setting TA_SYSTEM_ACCESS to PROTECTED may not be effective for multithreaded servers because it is possible that while one thread is executing BEA Tuxedo code, which means it is attached to the bulletin board, another thread might be executing user code. The BEA Tuxedo system cannot prevent such situations.
Note: If the NO_AA value is enabled in the TA_OPTIONS parameter, the security parameters NONE, APP_PW, and USER_AUTH will continue to work properly—except that no authorization or auditing will take place. The remaining modes of security, ACL and MANDATORY_ACL will continue to work properly—but will only use the default BEA security mechanism.
Limitations
Many attributes of this class are tunable only when the application is inactive. Therefore, use of the ATMI interface routines to administer the application is not possible. The function tpadmcall() is being provided as a means of configuring or reconfiguring an unbooted application. This interface may only be used for configuration (SET operations) in an inactive application and only on the site being configured as the master site for the application. Once an initial configuration is created and activated, administration is available through the standard ATMI interfaces as described in MIB(5).
T_FACTORY MIB
Overview
The T_FACTORY MIB class represents occurrences of factories registered with the FactoryFinder. The available factories for the application are reflected in this MIB and can be shown to the administrator via the Administration Console or command-line tools. The scope is global.
Attribute Table
The following state indicates the meaning of a TA_STATE returned in response to a GET request:
|
ACTive |
The T_FACTORY object is registered with the FactoryFinder. |
T_GROUP Class Definition
Overview
The T_GROUP class represents application attributes pertaining to a particular server group. These attribute values represent group identification, location, and DTP information.
Attribute Table
Attribute Semantics
OPENINFO = "TUXEDO/QM:qmconfig:qspace"
OPENINFO = "TUXEDO/QM:qmconfig;qspace"
OPENINFO = "TUXEDO/QM:qmconfig;qspace"
OPENINFO = "TUXEDO/QM,[a.b.c]qmconfig,qspace"
Limitations
None.
T_IFQUEUE Class
Overview
The T_IFQUEUE MIB class represents run-time attributes of an interface as it pertains to a particular server queue (T_QUEUE) in a CORBA environment. This is primarily a read-only class providing access to the inherited configuration attributes of an interface as well as statistics relating to the interface on the queue. Additionally, this class gives administrators finer granularity in suspending and activating interfaces. This class provides the link between an interface name and the server processes capable of processing method invocations on the interface, that is, TA_RQADDR can be used as a key search field on the T_SERVER class.
Attribute Table
T_INTERFACE Class
Overview
The T_INTERFACE MIB class represents configuration and runtime attributes of CORBA interfaces at both the domain and server group levels.
A domain-level T_INTERFACE object is one that is not associated with a Server Group. Its TA_SRVGRP attribute contains a NULL string (string of length 0, "").
A server group level T_INTERFACE object is one that has an associated server group (i.e., its TA_SRVGRP attribute contains a valid server group name for the domain). This Server Group level representation of an interface also provides a container for managing interface state (TA_STATE) and for collecting accumulated statistics.
An associated server group level T_INTERFACE object must exist for any CORBA Interfaces that are activated in a server. The activation of interfaces in a server is controlled by the state of a T_IFQUEUE object for the interface. Activation of a T_IFQUEUE object causes its attributes to be initialized with the values specified for the associated server group level T_INTERFACE object. If such an object does not exist, then one will be dynamically created. This dynamically-created server group level T_INTERFACE object will be initialized with the attributes of the domain level T_INTERFACE object for the interface if one exists. If an associated domain level T_INTERFACE object does not exist, system specified default configuration values will be applied. Once activated, interfaces are always associated with a server group level T_INTERFACE object.
The specification of configuration attributes for interfaces at any level is completely optional, system defined defaults will be provided and run-time server group level T_INTERFACE objects will be created. Interfaces to be offered by a server are identified via the ICF file used to generate server skeletons and advertised automatically by the system at server activation time.
Attribute Table
Implementation Hint
The T_INTERFACE MIB is a mapping from an interface to a BEA Tuxedo service. The MIB server can implement some of the get/set operations for an interface by calling the existing logic for the associated T_SERVICE object.
T_MACHINE Class Definition
Overview
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.
Attribute Table
1TA_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, then they must match the same object.
2Default is same as value set for this attribute in Class T_DOMAIN.
3Default is TA_APPDIR for this machine followed by /ULOG.
4The link-level encryption value of 40 bits is provided for backward compatibility.
Attribute Semantics
Note: The link-level encryption value of 40 bits is provided for backward compatibility.
Note: The link-level encryption value of 40 bits is provided for backward compatibility.
Limitations
SHM mode (see T_DOMAIN:TA_MODEL) applications can have only one T_MACHINE object. MP mode (see T_DOMAIN:TA_MODEL) applications with the LAN option set (see T_DOMAIN:TA_OPTIONS) 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 at least must be active in a minimumly 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.
T_MSG Class Definition
Overview
The T_MSG class represents run-time attributes of the BEA Tuxedo system managed UNIX system message queues.
Attribute Table
1All attributes in Class T_MSG are local attributes.
Attribute Semantics
|
ACTive |
T_MSG object active. This corresponds exactly to the related T_MACHINE object being active. |
Limitations
This class is UNIX system-specific and may not be supported in non-UNIX implementations of BEA Tuxedo system.
T_NETGROUP Class Definition
Overview
The T_NETGROUP class represents application attributes of network groups. Network groups are groups of LMIDs which can communicate over the TA_NADDR network addresses defined in the T_NETMAP class.
Attribute Table
Attribute Semantics
|
VALid |
T_NETGROUP object is defined and inactive. Note that this is the only valid state for this class. NETGROUPs are never ACTive. |
Limitations
None.
T_NETMAP Class Definition
Overview
The T_NETMAP class associates TA_LMIDs from the T_MACHINE class in the TM_MIB to a TA_NETGROUP object from the T_NETGROUP class. In other words, this class contains assignments of logical machines to network groups. A TA_LMID may be included in many TA_NETGROUP groups. When one LMID connects to another LMID, the BRIDGE process determines the subset of network groups to which the two LMIDs belong. When the pair of LMIDs are in several common groups, they are sorted in descending TA_NETPRIO order (TA_NETGRPNO is the secondary sort key). The Network groups with the same TA_NETPRIO will flow network data in parallel. Should a networking error prevent data from flowing through all the highest priority group(s), only then the next lower priority network group(s) are used for network traffic (failover). All network groups with a higher priority than the ones flowing data are retried periodically. Once a network connection is established with a higher TA_NETPRIO value, no further data is scheduled for the lower priority one. Once the lower priority connection is drained, it is disconnected in an orderly fashion (failback).
Attribute Table
1 The link-level encryption value of 40 bits is provided for backward compatibility.
Attribute Semantics