|
|
The Core MIB defines the groups through which the fundamental aspects of an application can be configured and managed. These MIB groups contain objects for managing machines, servers, networking, and load balancing.
The Core MIB defines the basic objects that form a BEA Tuxedo application. It is the main information repository for controlling the operation and configuration of the application. When an application is active, the Core MIB contains groups related to the run-time activity of your application. You can use this information to monitor the behavior of your application.
The Core MIB consists of the following groups.
The tuxTBridgeTbl group contains objects that represent run-time characteristics pertaining to connectivity between logical machines that make up an application. The object values represent connection status and statistics.
Objects in this table are accessible either through a Tuxedo SNMP agent installed on the local machine or using the -c option on the master machine. The index into the table consists of tuxTBridgeLmid and tuxTBridgeNetworkGrpNo. In Tuxedo 6.4, SET requests are allowed only for the DEFAULTNET network group, so all SET requests should use 0 for tuxTBridgeNetworkGrpNo in the SNMP index.
DisplayString is of the format: LMID1[,LMID2]
LMID1
LMID2
INTEGER {active(1), inactive(2), suspended(3), pending(4)}
The values for GET and SET operations are as follows:
GET:{active(1)|inactive(2)|suspended(3)|pending(4)}
GET operation retrieves run-time information for the selected tuxTBridgeTbl instance(s). A tuxTBridgeLmid object value with only one logical machine identifier matches all active connections from LMID1 to other machines in the application. In this case, each retrieved record contains an expanded tuxTBridgeLmid object value with the destination LMID filled in. The following states indicate the meaning of a tuxTBridgeState returned in response to a GET request. States not listed are not returned.
active(1)
inactive(2)
tuxTBridgeLmid object and the source logical machine is reachable.
suspended(3)
tuxTBridgeSuspTime object value.
pending(4)
SET: {active(1)|inactive(2)|suspended(3)|pending(4)}
SET operation updates run-time information for the selected tuxTBridgeTbl object. The following states indicate the meaning of a tuxTBridgeState set in a SET request. States not listed cannot be set.
active(1)
tuxTBridgeTbl instance by establishing an asynchronous connection between the indicated logical machines. This operation fails if only one machine is specified, if either of the machines is not active, or if the source machine is not reachable. When in the pending(4) state, the success or failure of the connection has not yet been determined. The BRIDGE can continue to process other events and data while the connection is outstanding. This state change is allowed in the inactive(2) and suspended(3) states. Successful return leaves the instance in the active(1) or pending(4) state.
inactive(2)
tuxTBridgeTbl object by closing the connection between the indicated logical machines. This operation fails if only one logical machine is specified or if the two machines are not connected. State change allowed only when in the active(1) state. Successful return leaves the object in the inactive(2) state.
suspended(3)
tuxTBridgeTbl object by closing the connection between the indicated logical machines and by setting the tuxTBridgeSuspTime parameter as indicated. State change allowed only when in the active(1) state. Successful return leaves the object in the suspended(3) state.
| Note: | Since the statistics reported are from the source logical machine, resetting those statistics causes them to be out of sync with the statistics reported by the destination logical machine for the same connection. |
pending(4)
tuxTBridgeTbl instance by establishing an asynchronous connection between the indicated logical machines. This operation fails if only one logical machine is specified, if either of the two machines is inactive, or if the source logical machine is not reachable. When in the pending(4) state, the success or failure of the connection request has not yet been determined. However, the BRIDGE can continue to process other events and data while the connection request is outstanding. State change allowed in inactive(2) and suspended(3) states. Successful return leaves the instance in the pending(4) state.
Current time, in seconds, since 00:00:00 UTC, January 1, 1970, as returned by the time(2) system call on tuxTBridgeLmid. This object can be used to compute elapsed time from the following "tuxTBridge" object values.
Time, in seconds, that this connection has been active.
Time, in seconds, remaining in the suspension of this connection. After this amount of time, the connection automatically changes to a tuxTBridgeState of inactive(2) and can be activated by normal application traffic.
Number of bytes sent from the destination logical machine to the source logical machine.
Number of bytes sent from the source logical machine to the destination logical machine.
Number of messages sent from the destination logical machine to the source logical machine.
Number of messages sent from the source logical machine to the destination logical machine.
Number of times flow control has been encountered over this connection.
INTEGER {none(1), 40-bit(2), 128-bit(3), not-available(4)}
The current level of encryption for this link. The tuxTBridgeCurEncryptBits value is negotiated between the machines when the link is established. The number specifies the encryption key length (in bits).
Logical network group number. When both the source and destination tuxTBridgeLmid machine identifiers are in the same network group, tuxTBridgeTbl presents all instances of related fields per network group.
The tuxTclientTbl group contains objects that represent run-time characteristics of active clients within an application. The object values identify and track the activity of clients within a running application. Objects in this table are only accessible through a Tuxedo SNMP agent installed on the local machine.
INTEGER { active(1), suspended(2), dead(3) }
The values for GET and SET operations are as follows:
GET: {active(1)|suspended(2)|dead(3)}
GET operation retrieves run-time information for the selected tuxTclientTbl instance(s). Note that client information is kept in local bulletin board tables only. Therefore, for maximum performance, inquiries on client status should be restricted, using key fields as much as possible. The following states indicate the meaning of a tuxTclientState returned in response to a GET request. States not listed are not returned.
active(1)
tuxTclientTbl instance active. The active(1) state is not an indication of whether the client is idle or busy. A non-0 value retrieved for either the tuxTclientCurConv object or the tuxTclientCurReq object indicates a busy client.
suspended(2)
tuxTclientTbl instance active and suspended from making further service requests (tpcall(3) or tpacall(3)) and from initiating further conversations (tpconnect(3)). See SET suspended(2) below for details.
dead(3)
tuxTclientTbl instance identified as active in the bulletin board but currently not running due to an abnormal death. This state exists only until the BBL local to the client notices the death and takes action to clean up the client's bulletin board resources.
SET: {active(1)|suspended(2)|dead(3)}
SET operation updates run-time information for the selected tuxTclientTbl object. The following states indicate the meaning of a tuxTclientState set in a SET request. States not listed cannot be set.
active(1)
suspended(2) tuxTclientTbl instance. State change allowed only when in the suspended(2) state. Successful return leaves the object in the active(1) state.
suspended(2)
tuxTclientTbl instance from making service requests (tpcall(3) or tpacall(3)), initiating conversations (tpconnect(3)), beginning transactions (tpbegin(3)), and enqueuing new requests (tpenqueue(3)). Clients within a transaction are permitted to make these calls until they abort or commit the current transaction, at which time the clients become suspended. Invocations of these routines result in a TPESYSTEM error return and a system log message being generated that indicates the situation. State change is allowed only when the object is in the active(1) state. Successful return leaves the object in the suspended(2) state.
dead(3)
tuxTclientTbl instance. State change is allowed only when the object is in the active(1) or suspended(2) state. The recommended method for deactivating clients is to first suspend them, and then to abortively deactivate them by setting the state to dead(3). Successful return leaves the object in the dead(3) state.
| Note: | Workstation handlers (tuxTclientWsh == yes(1)) cannot be set to a state of dead(3). The system might not be able to kill the client, due to platform or signaling restrictions. In this case, a native client is abortively terminated at its next access to ATMI, and a workstation client's connection to a WSH is preemptively torn down. |
Client identifier. The data in this field should not be interpreted directly by the end user except for equality comparison.
Client identifier. The data in this field should not be interpreted directly by the end user except for equality comparison.
Client identifier. The data in this field should not be interpreted directly by the end user except for equality comparison.
Client name associated with client at tpinit(3) time through the cltname element of the TPINIT structure.
Approximate amount of time, in seconds, since this client last interacted with the system through an ATMI call. This value is accurate to within tuxTdomainScanUnit (see the tuxTdomain group) seconds. When specified as a key field, a positive value indicates that all clients with idle times of at least the indicated value match, a negative value indicates that all clients with no more than the indicated value match, and a 0 value matches all clients.
Process identifier of client. Note that for workstation clients, this identifier indicates the workstation handler through which the workstation client is connected. A negative number can be specified on a GET operation for the purpose of retrieving client information for the calling process. If the calling process is not a client, then an error is returned.
Server group with which the client is associated. This information is set through the grpname element of the TPINIT structure at tpinit(3) time.
User name associated with client at tpinit(3) time through the usrname element of the TPINIT structure.
If this object is set to yes(1), the indicated client is logged in to the application from a remote workstation.
Workstation handler. If this object is set to yes(1), the indicated client is a workstation handler process.
Client identifier for the associated workstation handler (WSH) if this client is a workstation client (tuxTclientWsc == yes(1)); otherwise, the tuxTclientWshClientId value is returned as a 0-length string.
The Tuxedo system major protocol release number for the machine where the client is running. This value can be different from the tuxTmachineSWrelease for the same machine. Note that for /WS clients (tuxTclientWsc == yes(1)), this value can be different from the major release associated with the application administered machine through which the /WS client accesses the application.
The Tuxedo system /WS protocol version number for a workstation client. This value is changed with each update to the /WS protocol. A value of 0 is returned for this object when it is associated with non-/WS clients (tuxTclientWsc == no(2)).
Number of conversations initiated by this client through tpconnect(3).
Number of dequeue operations initiated by this client through tpdequeue(3).
Number of enqueue operations initiated by this client through tpenqueue(3).
Number of postings initiated by this client through tppost(3).
Number of requests made by this client through tpcall(3) or tpacall(3).
Number of subscriptions made by this client through tpsubscribe(3).
Number of transactions begun by this client.
Number of transactions aborted by this client.
Number of transactions committed by this client.
INTEGER { complete(1) | logged(2) }
Setting of the TP_COMMIT_CONTROL characteristic for this client. See the description of the Tuxedo system ATMI function tpscmt(3) for details on this characteristic.
Number of conversations initiated by this client through tpconnect(3) that are still active.
Number of requests initiated by this client through tpcall(3) or tpacall(3) that are still active.
Current time, in seconds, since 00:00:00 UTC, January 1, 1970, as returned by the time(2) system call on the local host. This object can be used to compute elapsed time from the tuxTclientTimeStart object value.
Server group number of the last service request made or conversation initiated from this client.
DisplayString (SIZE(1..256)) (up to 78 bytes for BEA Tuxedo 8.0 or earlier)
For workstation clients, this object indicates the network address of the client. Network addresses with unprintable characters are converted to the "0x..." network address format as described in the tuxTmachineNaddr object. Non-workstation clients have a 0-length string associated with them for the tuxTclientNaddr value.
| Note: | The ability of the system to provide this information is determined by the transport provider in use. In some cases, workstation clients cannot have addresses associated with them if the provider does not make this information available. |
INTEGER { dipin(1) | signal(2) | ignore(3) }
Setting of the notification characteristic for this client. See the tuxTdomain group description of this object for more details.
Number of unsolicited messages queued for this client that are awaiting processing.
UNIX system message queue identifier for the client's reply queue.
| Note: | This object is a UNIX-system-specific object value that might not be returned if the platform on which the application is being run is not UNIX-based. |
Time left, in seconds, for this client to receive the reply for which it is currently waiting before it times out. This timeout can be a transactional timeout or a blocking timeout.
Time, in seconds, since 00:00:00 UTC, January 1, 1970, as returned by the time(2) system call on local host, since the client joined the application.
Current transaction level for this client. 0 indicates that the client is not currently involved in a transaction.
Identifier for this particular application association.
The tuxTconnTable group contains objects that represent run-time characteristics of active conversations within an application. Objects in this table are only accessible through a Tuxedo SNMP agent installed on the local machine. All objects in this MIB group are local objects, that is, values for these objects correspond to the local host only where the Tuxedo agent is running. Thus, the user needs to run an instance of the Tuxedo agent on every node for which these values are of interest. The index into this table is tuxTconnSerNo.
A running number as an index for tuxTconnTable.
The values for GET and SET operations are as follows:
GET:
GET operation retrieves run-time information for the selected tuxTconnTable instance(s). The following state indicates the meaning of a tuxTconnState returned in response to a GET request. States not listed are not returned.
active(1)
active(1) state returned reflects one or both sides of an active conversation within the application.
SET:
Service name of the conversational service invoked by the originator and processed by the subordinate.
Client identifier. The data in this field should not be interpreted directly by the end user except for equality comparison.
Server group number for the originator of the conversation. If the originator is a client, then 30,000 is returned as the value for this object.
Logical machine identifier that indicates where the originator is running, or (in the case of /WS clients) is accessing the application .
Process identifier for the originator of the conversation.
Number of tpsend(3) calls made by the originator.
Server identifier for the originator of the conversation.
Server group number for the subordinate of the conversation. If the originator is a client, then 30,000 is returned as the value for this object.
Logical machine identifier that indicates where the subordinate is running or, (in the case of /WS clients) is accessing the application.
Process identifier for the subordinate in the conversation.
Number of tpsend(3) calls made by the subordinate.
Server identifier for the subordinate in the conversation.
The tuxTdevice group contains the following object and group (table).
DisplayString (SIZE(2..256)) (up to 64 bytes for BEA Tuxedo 8.0 or earlier)
The value of this object determines the device for which tuxTdeviceTbl returns configuration and run-time information.
The default value of this object is the TUXCONFIG file for the current domain.
The tuxTdeviceTbl group contains objects that represent configuration and run-time objects of raw disk slices or UNIX system files being used to store Tuxedo system device lists. This group allows for the creation and deletion of device list entries within a raw disk slice or UNIX system file. Objects in this table are only accessible through a Tuxedo SNMP agent installed on the local machine. To create a new row in this table, the user needs to send a SET request, with at least a value for tuxTdevSize. The index into this table is tuxTdevCfgDev and tuxTdevIndex.
Logical machine identifier where the device is located. Note that this object can be used as a key field in both unbooted and booted applications as long as they are already configured (that is, at least one tuxTmachineTable instance exists). It is required as a key field on SET operations when they are accessing a booted application. If specified when accessing the tuxTdeviceTbl table in an unconfigured application, this object is ignored.
| Note: | This object can be set only during row creation. |
Absolute pathname of the file or device where the Tuxedo system filesystem is stored or is to be stored.
| Note: | This object can be set only during row creation. |
Absolute pathname of the device list entry.
| Note: | This object can be set only during row creation. |
The offset, in blocks, at which space on this tuxTdevice begins for use within the Tuxedo system VTOC specified by tuxTdevCfgDev.
| Note: | This object can be set only during row creation. |
The size in pages of the disk area to be used for the device list entry.
| Note: | This object can be set only in conjunction with row creation. |
| Note: | This object can be set only during row creation. |
Device index for tuxTdevice within the device list addressed by tuxTdevCfgDev. The tuxTdevIndex value is used for identification purposes only in getting and setting object values that relate to particular devices within a Tuxedo system filesystem.
INTEGER { valid(1) | invalid(2) | re-init(3) }
The values for GET and SET operations are as follows:
GET: {valid(1)}
GET operation retrieves run-time information for the selected tuxTdeviceTbl instance(s). The following state indicates the meaning of a tuxTdevState returned in response to a GET request. States not listed are not returned.
valid(1)
tuxTdevCfgDev exists and contains a valid device list. tuxTdevice is a valid device within that filesystem with the device index tuxTdevIndex.
SET: {invalid(2)|re-init(3)}
SET operation updates information for the selected tuxTdeviceTbl instance or adds the indicated object. The following states indicate the meaning of a tuxTdevState set in a SET request. States not listed cannot be set.
invalid(2)
tuxTdeviceTbl instance for application. State change is allowed only when the object is in the valid(1) state. Successful return leaves the object in the invalid(2) state. Note that tuxTdevIndex 0 is special and must be deleted last.
re-init(3)
The tuxTdomain group contains objects that represent global application characteristics for the domain to which the Tuxedo SNMP Agent is currently connected. The object values serve to identify, customize, size, secure, and tune a Tuxedo application. Many of the object values represented here serve as application defaults for other groups represented in this MIB.
There is exactly one instance of the tuxTdomain group for each application.
Numeric key for the well-known address in a Tuxedo system bulletin board. In a single processor environment, this key "names" the bulletin board. In a multiple processor or LAN environment, this key names the message queue of the DBBL. In addition, this key is used as a basis for deriving the names of resources other than the well-known address, such as the names for bulletin boards throughout the application.
DisplayString is in format: LMID1[,LMID2]
LMID1
LMID2
The master identifier (LMID1) must correspond to the local machine for inactive applications. single-machine(1) mode applications (see tuxTdomainModel below) can set only the master logical machine identifier. Modifications to the tuxTdomainMaster value in an active multi-machine(2) application (see tuxTdomainModel below) have the following semantics.
Assuming current active master LMID A, current backup master LMID B, and secondary LMIDs C, D, ...., the following scenarios define the semantics of permitted changes to the tuxTdomainMaster object in a running multi-machine(2) mode application.
A,B -> B,A — Master migration from A to B. A,B -> A,C — Change backup master LMID designation to C.
Note that master migration can be either orderly or partitioned. Orderly migration takes place when the master machine is active and reachable. Otherwise, partitioned migration takes place. All newly established or re-established network connections verify that the two sites connecting share a common view of where the master machine is located. Otherwise, the connection is refused and an appropriate log message is generated.
The master and backup machines in an active application must always have a Tuxedo system release number greater than or equal to all other machines active in the application. The master and backup machines must be of the same release. Modifications to the tuxTdomainMaster object must preserve this relationship.
INTEGER { single-machine(1) | multi-machine(2) }
single-machine(1)
multi-machine(2)
INTEGER { active(1) | inactive(2) | forcible-inactive(3) }
The values for GET and SET operations are as follows:
GET: {active(1)|inactive(2)}
GET operation retrieves configuration and run-time information for the tuxTdomain group. The following states indicate the meaning of a tuxTdomainState returned in response to a GET request. States not listed are not returned.
active(1)
inactive(2)
SET: active(1)|inactive(2)|forcible-inactive(3)
SET operation updates configuration and run-time information for the tuxTdomain group. The following states indicate the meaning of a tuxTdomainState set in a SET request. States not listed cannot be set.
active(1)
inactive(2) state. Successful return leaves the object in the active(1) state.
inactive(2)
active(1) state. Successful return leaves the object in the inactive(2) state. To do a complete shutdown of the application, you must first make all groups inactive. (See tuxTgroupState.) This state transition fails if any application servers or clients are still attached to the domain. To ignore any running clients or application servers, set to forcible-inactive(3) as explained below.
forcible-inactive(3)
active(1) state. Successful return leaves the object in the inactive(2) state. You need to restart any clients before they can be used to process services after this state transition.
Default value for newly configured objects in the tuxTmachineTable group.
| Note: | Changes to this object do not affect active or already configured tuxTmachineTable instances. |
Default value for newly configured objects in the tuxTmachineTable group.
| Note: | Changes to this object do not affect active or already configured tuxTmachineTable instances. |
Default value for newly configured objects in the tuxTmachineTable group.
| Note: | Changes to this object do not affect active or already configured tuxTmachineTable instances. |
Attribute access mask. User type/access mode combinations specified by tuxTdomainMask are no longer allowed for all group/object combinations defined in TM_MIB(5). For example, a setting of 0003 disallows all updates to users other than the administrator or the operator. The value of this object should be provided as an octal number — 0 through 0777.
Default value for newly configured objects in the tuxTmachineTable group.
| Note: | Changes to this object do not affect active or already configured tuxTmachineTable instances. |
Default value for newly configured objects in the tuxTmachineTable group.
| Note: | Changes to this object do not affect active or already configured tuxTmachineTable instances. |
Default value for newly configured objects in the tuxTmachineTable group.
| Note: | Changes to this object do not affect active or already configured tuxTmachineTable instances. |
Maximum number of buffer subtypes that can be accommodated in the bulletin board buffer subtype table.
Maximum number of buffer types that can be accommodated in the bulletin board buffer type table.
Maximum number of routing table entries that can be accommodated in the bulletin board routing table. One entry per tuxTroutingTable group object is required. Additional entries should be allocated to allow for run-time growth.
Maximum number of server groups that can be accommodated in the bulletin board server group table.
Maximum number of machines that can be accommodated in the bulletin board machine table.
Maximum number of queues to be accommodated in the bulletin board queue table.
Maximum number of routing criteria range table entries to be accommodated in the bulletin board range criteria table. One entry per individual range within a tuxTroutingRanges specification is required plus one additional entry per tuxTroutingTable group object. Additional entries should be allocated to allow for run-time growth.
Maximum string pool space to be accommodated in the bulletin board string pool table. Strings and carrays specified within tuxTroutingRanges values are stored in the string pool. Additional space should be allocated to allow for run-time growth.
Maximum number of servers to be accommodated in the bulletin board server table. Allowances should be made in setting this object for system supplied administrative servers. Administration of each Tuxedo system site adds approximately one server. Additionally, if TMSs are specified for any server groups (see tuxTgroupTMSname), they are booted along with their server group and should be accounted for in setting tuxTdomainMaxServers.
Maximum number of services to be accommodated in the bulletin board service table. Allowances should be made in setting this object for system supplied servers that offer services for administrative purposes. Administration of each Tuxedo system site adds approximately five services. Other administrative components such as /WS, /Q, and /DM can also add administrative services that should be accounted for.
Maximum number of group identifiers that can be used for checking ACL permissions. The maximum group identifier that can be defined is tuxTdomainMaxACLgroups - 1.
INTEGER { complete(1) | logged(2) }
Initial setting of the TP_COMMIT_CONTROL characteristic for all client and server processes in a Tuxedo application. logged(2) initializes the TP_COMMIT_CONTROL characteristic to TP_CMT_LOGGED; otherwise, it is initialized to TP_CMT_COMPLETE. See the description of the Tuxedo system ATMI function tpscmt(3) for details on the setting of this characteristic.
| Note: | Run-time modifications to this object do not affect active clients and servers. |
yes(1)
no(2)
| Note: | Run-time modifications to this object do not affect active clients and servers. |
INTEGER { dipin(1) | signal(2) | ignore(3) }
Default notification detection method used by the system for unsolicited messages sent to client processes. This default value can be overridden on a per-client basis using the appropriate tpinit(3) flag value. Note that once unsolicited messages are detected, they are made available to the application through the application defined unsolicited message handling routine identified through the tpsetunsol(3) function.
dipin(1)
dipin(1) specifies that dip-in-based notification detection should be used, which means that the system only detects notification messages on behalf of a client process while within ATMI calls. The point of detection within any particular ATMI call is not defined by the system, and dip-in detection does not interrupt blocking system calls. dipin(1) is the default notification detection method.
signal(2)
signal(2) specifies that signal-based notification detection should be used, which means that the system sends a signal to the target client process after the notification message has been made available. The system installs a signal catching routine on behalf of clients that select this method of notification.
ignore(3)
ignore(3) specifies that by default, notification messages are to be ignored by application clients, which would be appropriate in applications where only clients that request notification at tpinit(3) time should receive unsolicited messages.
| Note: | Run-time modifications to this object do not affect active clients. All signaling of client processes is done by administrative system processes and not by application processes. Therefore, only clients running with the same UNIX system user identifier can be notified by use of the signal(2) method. |
INTEGER { fastpath(1) | protected(2) | fastpath-no-override(3) | protected-no-override(4) }
Default mode used by Tuxedo system libraries within application processes to gain access to Tuxedo system's internal tables.
fastpath(1)
protected(2)
fastpath-no-override(3) or protected-no-override(4)
tpinit(3).
| Note: | Updates to the tuxTdomainSystemAccess value in a running application affect only newly started clients and newly configured tuxTsrvrTbl objects. |
INTEGER { lan(1) | migrate(2) | accstats(3) | lan-migrate(4) | lan-accstats(5) | migrate-accstats(6) | lan-migrate-accstats(7) | none(8) }
Comma separated list of application options in effect. Valid options are defined as follows:
lan(1)
migrate(2)
accstats(3)
| Note: | Only the accstats(3) can be set or reset in an active application. |
INTEGER { sigusr1(1) | sigusr2(2) }
Signal to be used for signal-based notification (see tuxTdomainNotify above).
Type of application security. The format is:
where security_mode can have the following values:
NONE
APP_PW
USER_AUTH
ACL
MANDATORY_ACL
NONE
APP_PW
APP_PW/app_password indicates that application password security is enforced. Clients must provide the application password during initialization.
USER_AUTH
USER_AUTH is similar to APP_PW, but indicates also that per-user authentication is done during client initialization.
ACL
ACL is similar to USER_AUTH, but also indicates that access control checks are done on service names, queue names, and event names. If an associated ACL is not found for a name, it is assumed that permission is granted
MANDATORY_ACL
MANDATORY_ACL is similar to ACL, but permission is denied if an associated ACL is not found for the name.
app_password
security_mode is being set to anything but NONE. To change the value of app_password, SET this object to:
current_security_mode/new_password
On a GET operation, this object only returns the security mode; the password is not returned.
Application authentication service invoked by the system for each client that joins the system. The tuxTdomainAuthsvc value is ignored if the tuxTdomainSecurity object is set to NONE or to APP-PW.
Interval of time (in seconds) between periodic scans by the system. Periodic scans are used to detect old transactions and timed-out blocking calls within service requests. The tuxTdomainBBLQuery, tuxTdomainBlockTime, tuxTdomainDBBLWait, and tuxTdomainSanityScan objects are multipliers of this value. Passing a value of 0 for this object on a SET operation causes the object to be reset to its default value.
Multiplier of the tuxTdomainScanUnit object that indicates time between DBBL status checks on registered BBLs. The DBBL checks to ensure that all BBLs have reported within the tuxTdomainBBLQuery cycle. If a BBL has not been heard from, the DBBL sends a message to that BBL asking for status. If no reply is received, the BBL is partitioned. Passing a value of 0 for this object on a SET operation causes the object to be reset to its default value. The tuxTdomainBBLQuery value should be set to at least twice the value set for tuxTdomainSanityScan.
Multiplier of the tuxTdomainScanUnit object that indicates the minimum amount of time a blocking ATMI call blocks before timing out. Passing a value of 0 for this object on a SET operation causes the object to be reset to its default value.
Multiplier of the tuxTdomainScanUnit object that indicates the maximum amount of time a DBBL should wait for replies from its BBLs before timing out. Passing a value of 0 for this object on a SET operation causes the object to be reset to its default value.
Multiplier of the tuxTdomainScanUnit object that indicates the time interval between basic sanity checks of the system. Sanity checking includes client/server viability checks done by each BBL for clients/servers running on the local machine as well as BBL status check-ins (multi-machine(2) mode only). Passing a value of 0 for this object on a SET operation causes the object to be reset to its default value.
Current number of bulletin board routing table entries in use.
Current number of bulletin board server group table entries that are in use.
Current number of configured machines.
Current number of bulletin board queue table entries that are in use.
Current number of bulletin board routing criteria range table entries that are in use.
Current size of routing table string pool.
Current number of bulletin board server table entries that are in use.
Current number of bulletin board service table entries that are in use.
Current number of bulletin board subtype table entries that are in use.
Current number of bulletin board type table entries that are in use.
High water number of bulletin board routing table entries that are in use.
High water number of bulletin board server group table entries that are in use.
High water number of configured machines.
High water number of bulletin board queue table entries that are in use.
High water number of bulletin board routing criteria range table entries that are in use.
High water size of routing table string pool.
High water number of bulletin board server table entries that are in use.
High water number of bulletin board service table entries that are in use.
The maximum number of groups that can be configured.
The default maximum number of active CORBA objects that can be accommodated in the Active Object Map tables in the Tuxedo bulletin board.
Specifies the maximum number of interfaces that can be accommodated in the interface table of the bulletin board. If not specified, the default is 100.
All instances of an interface occupy and re-use the same slot in the interface table in the bulletin board. For example, if server SVR1 advertises interfaces IF1 and IF2, SVR2 advertises IF2 and IF3, and SVR3 advertises IF3 and IF4, the interface count is 4, not 6, when calculating tuxMaxInterfaces.
Number of seconds a valid signature's timestamp can be ahead of the local machine's clock.
The current number of interface entries used in the bulletin board interface tables.
The high water mark for the number of interface entries used in the bulletin board interface tables.
Number of seconds a valid signature's timestamp can be behind the local machine's clock.
If set to "yes," every application service in this domain requires an encrypted input message buffer.
If set to "yes," every application service in this domain requires a valid digital signature on its input message buffer.
The tuxTgroupTable group contains objects that represent application characteristics pertaining to a particular server group. The object values represent group identification, location, and DTP information.
The index for this table is tuxTgroupNo. To create a new row, it is necessary to issue a SET request for a non-existing instance that at least specifies values for tuxTgroupName and tuxTgroupLMID.
Logical name of the server group. The group name must be unique within all group names in the tuxTgroupTable group and tuxTgroupLMID values in the tuxTmachineTable group. Server group names cannot contain an asterisk (*), comma, or colon.
| Note: | This object can be set only during row creation. |
Group number associated with this server group.
| Note: | This object can be set only during row creation. |
DisplayString is in the format: LMID1[,LMID2]
LMID1
LMID2
The secondary LMID indicates the machine to which the server group can be migrated (if the MIGRATE option is specified in the tuxTdomainOptions object). A single LMID specified on a GET operation matches either the primary or secondary LMID. Note that the location of an active group is available in the tuxTgroupCurLMID object. Logical machine identifiers specified with the tuxTgroupLMID object must already be configured.
| Note: | Modifications to this object for an active object can only change the backup LMID designation for the group. |
INTEGER { active(1) | inactive(2) | migrating(3) | invalid(4) |
re-active(5) | suspend-services(6) | resume-services(7)}
The values for GET and SET operations are as follows:
GET: {active(1)|inactive(2)|migrating(3)}
GET operation retrieves configuration and run-time information for the selected tuxTgroupTable object(s). The following states indicate the meaning of a tuxTgroupState returned in response to a GET request. States not listed are not returned.
active(1)
tuxTgroupTable object defined and active (TMS and/or application servers). Server groups with non-0 length values for the tuxTgroupTMSname object are considered active if the TMSs associated with the group are active. Otherwise, a group is considered active if any server in the group is active.
inactive(2)
migrating(3)
tuxTgroupTable object defined and currently in a state of migration to the secondary logical machine. The secondary logical machine is the one listed in tuxTgroupLMID that does not match tuxTgroupCurLMID.
SET: {active(1)|inactive(2)|migrating(3)|invalid(4)|re-active(5) |suspend-services(6)|resume-services(7)}
SET operation updates configuration and run-time information for the selected tuxTgroupTable object. The following states indicate the meaning of a tuxTgroupState set in a SET request. States not listed cannot be set.
active(1)
tuxTgroupTable object. State change is allowed only when the group is in the inactive(2) or migrating(3) state. If the group is currently in the inactive(2) state and the primary logical machine is active, then TMS and application servers are started on the primary logical machine; otherwise, if the secondary logical machine is active, the TMS and application servers are started on the secondary logical machine. If neither machine is active, then the request fails. If the group is currently in the migrating(3) state, then the active secondary logical machine (identified as the alternate to tuxTgroupCurLMID in the tuxTgroupLMID list), if it is active, is used to start TMS and application servers. Otherwise, the request fails. Successful return leaves the object in the active(1) state.
inactive(2)
tuxTgroupTable instance. TMS and application servers are deactivated. State change is allowed only when the group is in the active(1) or migrating(3) state. Successful return leaves the object in the inactive(2) state.
migrating(3)
tuxTgroupTable object on its active primary logical machine (tuxTgroupCurLMID) and prepare the group to be migrated to the secondary logical machine. State change is allowed only when the group is in the active(1) state. Successful return leaves the object in the migrating(3) state.
invalid(4)
tuxTgroupTable object for application. State change is allowed only when the group is in the inactive(2) state. Successful return leaves the object in the invalid(4) state.
re-active(5)
inactive(2) and migrating(3) states.
suspend-services(6)
SET operation to this state is allowed only when the group is in the active(1) state. The operation leaves the group in active(1) state but with all its application services in a suspended state.
resume-services(7)
active(1) state. The operation leaves the group in the active(1) state.
Current logical machine on which the server group is running. The tuxTgroupCurLMID value is not returned for server groups that are not active.
If a non-0 length value other than TMS is specified for the tuxTgroupTMSname object, then the tuxTgroupCloseInfo value indicates the resource manager-dependent information needed to terminate access to the resource manager. Otherwise, this object value is ignored.
The format for the tuxTgroupCloseInfo value is dependent on the requirements of the vendor providing the underlying resource manager. The information required by the vendor must be prefixed with rm_name:, which is the published name of the vendor's transaction (XA) interface followed immediately by a colon (:).
A 0-length string value for this object means that the resource manager for this group (if specified) does not require any application-specific information to close access to the resource.
| Note: | Run-time modifications to this object do not affect active servers in the group. |
If a non-0 length value other than TMS is specified for the tuxTgroupTMSname object, the tuxTgroupOpenInfo value indicates the resource manager-dependent information needed to initiate access to the resource manager. Otherwise, this object value is ignored.
The format for the tuxTgroupOpenInfo value is dependent on the requirements of the vendor that provides the underlying resource manager. The information required by the vendor must be prefixed with rm_name:, which is the published name of the vendor's transaction (XA) interface followed immediately by a colon (:).
A 0-length string value for tuxTgroupOpenInfo means that the resource manager for this group (if specified) does not require any application-specific information to open access to the resource.
| Note: | Run-time modifications to this object do not affect active servers in the group. |
If a non-0 length value is specified for the tuxTgroupTMSname object, the tuxTgroupTMScount value indicates the number of transaction manager servers to start for the associated group. Otherwise, this object value is ignored.
DisplayString (SIZE(0..256)) (up to 78 bytes for BEA Tuxedo 8.0 or earlier)
Transaction manager server a.out associated with this group. This parameter must be specified for any group entry whose servers participate in distributed transactions (transactions across multiple resource managers and possibly machines that are started with tpbegin(3) and ended with tpcommit(3) or tpabort(3)).
The value TMS is reserved to indicate use of the null XA interface. If a non-empty value other than TMS is specified, a tuxTmachineTlogDevice must be specified for the machine(s) associated with the primary and secondary logical machines for this object
A unique server identifier is selected automatically for each TM server, and the servers are restartable an unlimited number of times.
INTEGER { yes(1) | no(2)}
If set to "yes," every application service in this group requires an encrypted message buffer.
INTEGER { yes(1) | no(2)}
If set to "yes," every application service in this group requires a valid digital signature on its input message buffer.
The tuxTmachineTable group contains objects that represent application characteristics pertaining to a particular machine. The object values represent machine characteristics, per-machine sizing, statistics, customization options, and UNIX system filenames. This group is available for configured-inactive as well as configured-active machines in the application.
The index into this table is tuxTmachinePmid. To create a new row, issue a SET request for a non-existing row that specifies at least the values for tuxTmachineLmid, tuxTmachineTuxDir, tuxTmachineTuxConfig, and tuxTmachineAppDir. For a multi-machine Tuxedo application, tuxTmachineNaddr, tuxTmachineNlsAddr, and tuxTmachineBridge must also be specified.
Physical machine identifier. This identifier should match the UNIX system nodename returned by the uname -n command when run on the identified system. For a Windows NT system, this identifier should match the computer name and the name configured with the name server.
| Note: | This object can be set only during row creation. |
| Note: | This object can be set only during row creation. |
DisplayString (SIZE (2..256)) (up to 78 bytes for BEA Tuxedo 8.0 or earlier)
Absolute pathname of the file or device where the binary Tuxedo system configuration file is found on this machine. The administrator need only maintain one such file, namely the one identified by the tuxTmachineTuxConfig value on the master machine. The information contained in this file is automatically propagated to all other tuxTmachineTable objects as they are activated. See tuxTmachineEnvFile for a discussion of how the tuxTmachineTuxConfig value is used in the environment.
DisplayString (SIZE(2..256)) (up to 78 bytes for BEA Tuxedo 8.0 or earlier)
Absolute pathname of the directory where the Tuxedo system software is found on this machine. See tuxTmachineEnvFile that follows for a discussion about how the tuxTmachineTuxDir value is used in the environment.
DisplayString (SIZE (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 application servers are started. See tuxTmachineEnvFile for a discussion of how the tuxTmachineAppDir value is used in the environment.
INTEGER { active(1) | inactive(2) | partitioned(3) | invalid(4) |
re-activate(5) | cleaning(7) }
The values for GET and SET operations are as follows:
GET: {active(1)|inactive(2)|partitioned(3)}
GET operation retrieves configuration and run-time information for the selected tuxTmachineTable instance(s). The following states indicate the meaning of a tuxTmachineState returned in response to a GET request. States not listed are not returned
active(1)
tuxTmachineTable instance defined and active (administrative servers, that is, DBBL, BBL, and BRIDGE).
inactive(2)
partitioned(3)
tuxTmachineTable instance defined, listed in accessible bulletin boards as active, but currently unreachable.
SET: {active(1)|inactive(2)|invalid(4)|re-activate(5)|cleaning(7)}
SET operation updates configuration and run-time information for the selected tuxTmachineTable instance. The following states indicate the meaning of a tuxTmachineState set in a SET request. States not listed can not be set.
active(1)
tuxTmachineTable instance. Necessary administrative servers such as the DBBL, BBL, and BRIDGE are started on the indicated site as well as application servers configured to run on that site. State change is allowed only when the machine is in the inactive(2) state. Successful return leaves the object in the active(1) state.
inactive(2)
tuxTmachineTable instance. Necessary administrative servers such as the BBL and BRIDGE are stopped on the indicated site as well as application servers running on that site. State change allowed only when the machine is in the active(1) state and when no other application resources are active on the indicated machine. Successful return leaves the object in the inactive(2) state.
invalid(4)
tuxTmachineTable instance for application. State change is allowed only when the machine is in the inactive(2) state. Successful return leaves the object in the invalid(4) state.
re-activate(5)
tuxTmachineTable instance. Necessary administrative servers such as the DBBL, BBL, and BRIDGE are started on the indicated site. State change is allowed only when the machine is in either the active(1) or inactive(2) state. Successful return leaves the object in the active(1) state.
cleaning(7)
tuxTmachineTable instance is in either the active(1) or partitioned(3) state. Successful return for a non-partitioned machine leaves the state unchanged. Successful return for a partitioned machine leaves the object in the inactive(2) state.
| Note: | State change to inactive(2) is allowed only for non-master machines. The master site administrative processes are deactivated through the tuxTdomain group. |
UNIX system user-identifier for the Tuxedo 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 are started as this user.
| Note: | This object is a UNIX-system-specific object that cannot be returned if the platform on which the application is being run is not UNIX-based. |
UNIX system group identifier for the Tuxedo 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 are started as part of this group.
| Note: | This object is a UNIX-system-specific object that cannot be returned if the platform on which the application is being run is not UNIX-based. |
DisplayString (SIZE(2..256)) (up to 78 bytes for BEA Tuxedo 8.0 or earlier)
Environment file for clients and servers running on this machine.
UNIX system permissions associated with the shared memory bulletin board created on this machine. Default UNIX system permissions for system and application message queues.
| Note: | Modifications to this object for an active object do not affect running servers or clients. |
| Note: | This object is a UNIX-system-specific object that cannot be returned if the platform on which the application is being run is not UNIX-based. |
DisplayString (SIZE(0..256)) (up to 78 bytes for BEA Tuxedo 8.0 or earlier)
Absolute pathname prefix of the path for the userlog(3) file on this machine. The userlog(3) file name is formed by appending the string .mmddyy to the tuxTmachineUlogPfx object value .mmddyy represents the month, day, and year that the messages were generated. All application and system userlog(3) messages generated by clients and servers running on this machine are directed to this file.
| Note: | Modifications to this object for an active object do not affect running servers or clients. |
Machine type. The tuxTmachineType value is used to group machines into groups of like data representations. Data encoding is not performed when communicating between machines of identical types. This object can be given any string value; values are used only for comparison. Distinct tuxTmachineType objects should be set when the application spans a heterogeneous network of machines or when compilers generate dissimilar structure representations. The default value for tuxTmachineType, a 0-length string, matches any other machine having a 0-length string as its tuxTmachineType object value.
Maximum number of clients and servers that can have access to the bulletin board on this machine at one time. System administration processes such as the BBL and tmadmin need not be accounted for in this figure, but all application servers and clients and TMS servers should be counted. If the application is booting workstation listeners on this site, then both the listeners and the potential number of workstation handlers that can be booted should be counted.
Maximum number of simultaneous conversations in which clients and servers on this machine can be involved.
Maximum number of simultaneous global transactions in which this machine can be involved.
Number of entries for accessers on this machine to be reserved for workstation clients. The number specified here takes a portion of the total slots for accessers specified with the tuxTmachineMaxAccessers object. The appropriate setting of this parameter helps to conserve IPC resources because workstation client access to the system is multiplexed through a Tuxedo system supplied surrogate, the workstation handler. It is an error to set this number greater than tuxTmachineMaxAccessers.
Number of entries in the cache used for ACL entries when tuxTdomainSecurity is set to acl(4) or mandatory-acl(5). The appropriate setting of this parameter helps to conserve shared memory resources and yet reduce the number of disk access to do ACL checking.
DisplayString (SIZE (0..256)) (up to 64 bytes for BEA Tuxedo 8.0 or earlier)
The device (raw slice) or UNIX system file containing the Tuxedo system filesystem that holds the DTP transaction log for this machine. The DTP transaction log is stored as a Tuxedo system VTOC table on the device. This device or file can be the same as that specified for the tuxTmachineTuxConfig object for this machine.
The name of the DTP transaction log for this machine. If more than one DTP transaction log exists on the same tuxTmachineTlogDevice, they must have unique names. tuxTmachineTlogName must be different from the name of any other table on the tuxTmachineTlogDevice where the DTP transaction log table is created.
The numeric size, in pages, of the DTP transaction log for this machine. The tuxTmachineTlogSize object value is subject to limits based on available space in the Tuxedo system filesystem identified by the tuxTmachineTlogDevice object.
Device name to be used by the BRIDGE process placed on this logical machine to access the network. The tuxTmachineBridge value is a required value for participation in a networked application through a TLI-based Tuxedo system binary. This object value is not needed for sockets-based Tuxedo system binaries.
DisplayString (SIZE (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 object must be set if the logical machine is to participate in a networked application, that is, if the LAN option is set in the tuxTdomainOptions object value.
If DisplayString has the form 0xhex-digits or \\xhex-digits, it must contain an even number of valid hexadecimal digits. These forms are translated internally into a character array that contains the hexadecimal representations of the specified string.
DisplayString (SIZE(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 has the same format as that specified for the tuxTmachineNaddr object.
This object must be set if the logical machine is to participate in a networked application, that is, if the LAN option is set in the tuxTdomainOptions object value.
Threshold message size at which compression occurs for remote traffic and, optionally, local traffic. Remote and local can be either non-negative numeric values or the string MAXLONG that is dynamically translated to the maximum long setting for the machine. Setting only the remote value defaults local to MAXLONG.
Service load added to any remote service evaluated during load balancing on this machine.
Spincount used on this machine for pre-ticket user-level semaphore access. Default values are built into the Tuxedo system binaries on each machine. For tuning purposes, these defaults can be overridden at run-time using tuxTmachineSpinCount. The spincount can be reset to the default built-in value for the site by resetting tuxTmachineSpinCount to 0.
INTEGER { master(1)| backup(2)| other(3) }
The role of this machine in the application.
master(1)
backup(2)
other(3)
The Tuxedo system minor protocol release number for this machine.
The Tuxedo system major protocol release number for this machine. This value can be different from the tuxTmachineSWrelease for the same machine.
Specifies a limit for the amount of space that can be allocated for messages waiting to be transmitted by the BRIDGE process. The minimum value is 100000.
The maximum number of CORBA objects that can be accommodated in the Active Object Map tables in the bulletin board.
If set to "yes," every application service on this machine requires an encrypted input message buffer.
If set to "yes," every application service on this machine requires a valid digital signature on its input message buffer.
The tuxTmachineActive group contains objects that represent run-time statistics on the local machine if the machine is active (that is, some component of the application is active on the machine). Objects in this group are only accessible through a Tuxedo SNMP agent installed on the local machine.
Number of clients and servers that currently access the application either directly on this machine or through a workstation handler on this machine.
Number of clients, both native and workstation, currently logged in to this machine.
Number of active conversations with participants on this machine.
Number of in use transaction table entries on this machine.
Current service load enqueued on this machine.
| Note: | If the tuxTdomainLoadBalance object is no(2) or the tuxTdomainModel object is multi-machine(2), then an FML32 NULL value (0) is returned. |
Number of workstation clients currently logged in to this machine.
High water number of clients and servers accessing the application either directly on this machine or through a workstation handler on this machine.
High water number of clients, both native and workstation, logged in to this machine.
High water number of active conversations with participants on this machine.
High water number of in use transaction table entries on this machine.
High water number of workstation clients currently logged in to this machine.
Number of tpconnect(3) operations performed from this machine.
Number of tpdequeue(3) operations performed from this machine.
Number of tpenqueue(3) operations performed from this machine.
Number of tppost(3) operations performed from this machine.
Number of tpacall(3) or tpcall(3) operations performed from this machine.
Number of tpsubscribe(3) operations performed from this machine.
Number of transactions initiated (tpbegin(3)) from this machine.
Number of transactions aborted (tpabort(3)) from this machine.
Number of transactions committed (tpcommit(3)) from this machine.
Expiration date for the binary on the machine or a 0-length string if binary is not a Tuxedo system master binary.
Maximum number of licensed users on that machine, or -1 if binary is not a Tuxedo system master binary.
Serial number for binary on the machine or a 0-length string if binary is not a Tuxedo system master binary.
Disk pagesize used on this machine.
Software release for binary on that machine or a 0-length string if binary is not a Tuxedo system master binary.
High water number of entries used in the ACL cache.
Number of accesses to the ACL cache that resulted in a "hit" (that is, the entry was already in the cache).
Number of accesses to the ACL cache.
Number of accesses to the ACL cache that resulted in a access control violation.
Total service load dequeued and processed successfully by servers running on this machine. Note that for long running applications this object can wraparound, that is, exceed the maximum value for a long, and start back at 0 again.
Total service load enqueued by clients/servers running on this machine. Note that for long running applications this object can wraparound, that is, exceed the maximum value for a long, and start back at 0 again.
The number of entries in use in the bulletin board object table for this machine.
The high water mark of entries used in the bulletin board object table for this machine.
The tuxTmsgTable group contains objects that represent run-time characteristics of the Tuxedo system managed UNIX system message queues. Objects in this table are only accessible through a Tuxedo SNMP agent installed on the local machine. tuxTmsgId is the index into this table.
UNIX system message queue identifier.
| Note: | This object is a UNIX-system-specific object that cannot be returned if the platform on which the application is being run is not UNIX-based. |
The values for GET and SET operations are as follows:
GET: active(1)
GET operation retrieves run-time information for the selected tuxTmsgTable object(s). The following state indicates the meaning of a tuxTmsgState returned in response to a GET request. States not listed are not returned.
active(1)
tuxTmsgTable object active. This state corresponds exactly to the related tuxTmachineTable object being active.
SET:
Current time, in seconds, since 00:00:00 UTC, January 1, 1970, as returned by the time(2) system call on the local host.
Current number of bytes on the queue.
Time of the last msgctl(2) operation that changed a member of the msqid_ds structure associated with the queue.
Process identifier of the last process that read from the queue.
Process identifier of the last process that wrote to the queue.
Maximum number of bytes allowed on the queue.
Number of messages currently on the queue.
Time since the last read from the queue.
Time since the last write to the queue.
The tuxTqueueTable group contains objects that represent run-time characteristics of queues in an application. The object values identify and characterize allocated Tuxedo system request queues associated with servers in a running application. They also track statistics related to application workloads associated with each queue object. The index into this table is tuxTqueueRqAddr. Objects in this table are only accessible through a Tuxedo SNMP agent installed on the local machine.
Symbolic address of the request queue. Servers with the same tuxTsrvrRqAddr object value are grouped into a Multiple Server Single Queue (MSSQ) set. object values returned with a tuxTqueueTable object apply to all active servers associated with this symbolic queue address.
INTEGER { active(1)| migrating(2)| suspended(3)| partitioned(4) }
The values for GET and SET operations are as follows:
GET: {active(1)|migrating(2)|suspended(3)|partitioned(4)}
GET operation retrieves run-time information for the selected tuxTqueueTable instance(s). The tuxTqueueTable group does not address configuration information directly. Configuration-related objects discussed here must be set as part of the related tuxTsrvrTbl instances. The following states indicate the meaning of a tuxTqueueState returned in response to a GET request. States not listed are not returned.
active(1)
migrating(2)
tuxTqueueTable instance is currently in the migrating(2) state. See the tuxTsrvrTbl group for more details on this state.
suspended(3)
tuxTqueueTable instance is currently in the suspended(3) state. See the tuxTsrvrTbl group for more details on this state.
partitioned(4)
tuxTqueueTable instance is currently in the partitioned(4) state. See the tuxTsrvrTbl group for more details on this state.
SET:
SET operation updates run-time information for the selected tuxTqueueTable object. State changes are not allowed when updating tuxTqueueTable object information. Modification of an existing tuxTqueueTable object is allowed only when the object is in the active(1) state.
UNIX system message queue identifier.
| Note: | This object is a UNIX-system-specific object that cannot be returned if the platform on which the application is being run is not UNIX-based. |
Number of active servers associated with this queue.
The sum of the queue lengths of this queue while it has been active. This sum includes requests enqueued to and processed by servers that are no longer active on the queue. Each time a new request is assigned to the queue, the sum is incremented by the length of the queue immediately before the new request is enqueued.
| Note: | If the tuxTdomainLoadBalance object is no(2) or the tuxTdomainModel object is multi-machine(2), then tuxTqueueTotNqueued is not returned. In the same configuration, updates to this object are ignored. Consequently, when this object is returned tuxTqueueSource has the same value as the local host. |
The sum of the workloads enqueued to this queue while it has been active. This sum includes requests enqueued to and processed by servers that are no longer active on the queue. Each time a new request is assigned to the queue, the sum is incremented by the workload on the queue immediately before the new request is enqueued.
| Note: | If the tuxTdomainLoadBalance object is no(2) or the tuxTdomainModel object is multi-machine(2), then tuxTqueueTotWkQueued is not returned. In the same configuration, updates to this object are ignored. Consequently, when this object is returned tuxTqueueSource has the same value as the local host. |
Logical machine from which local object values are retrieved.
Number of requests currently enqueued to this queue from the tuxTqueueSource logical machine. This value is incremented at enqueue time and decremented when the server dequeues the request.
| Note: | If the tuxTdomainLoadBalance object is no(2) or the tuxTdomainModel object is multi-machine(2), then tuxTqueueNqueued is not returned. Consequently, when this object is returned tuxTqueueSource has the same value as the local host. |
Workload currently enqueued to this queue from the tuxTqueueSource logical machine. If the tuxTdomainModel object is set to single-machine(1) and the tuxTdomainLoadBalance object is set to yes(1), then tuxTqueueWkQueued reflects the application-wide workload enqueued to this queue. However, if tuxTdomainModel is set to multi-machine(2) and tuxTdomainLoadBalance is set to yes(1), then tuxTqueueWkQueued reflects the workload enqueued to this queue from the tuxTqueueSource logical machine during a recent timespan. The tuxTqueueWkQueued value is used for load balancing purposes. In order not discriminate against newly started servers, tuxTqueueWkQueued is zeroed out on each machine periodically by the BBL.
The tuxTroutingTable group contains objects that represent configuration characteristics of routing specifications for an application. The object values identify and characterize application data-dependent routing criteria with respect to field names, buffer types, and routing definitions. This table also represents configuration objects for factory-based routing for Tuxedo 8.0 or later applications. Object tuxRoutingFieldType (Tuxedo 8.0 or later) is valid only for factory-based routing. Object tuxTroutingBufType is valid only for service-based routing.
The index into this table consists of the following objects: tuxTroutingName, tuxRoutingType, and tuxInternalIdx.
Object tuxRoutingFieldType is valid only for factory-based routing and is supported only for Tuxedo 8.0 or later applications.
Object tuxTroutingBufType is valid only for service-based routing.
When specifying the index in SET requests, tuxInternalIdx is used as an index.
For factory-based routing, tuxInternalIdx must always have a value of -.
For service-based routing, tuxInternalIdx should equal the first 30 characters in tuxTroutingBufType.
To create a new row in the table, it is necessary to issue a SET request for a non-existing row specifying the values of all objects applicable to the tuxRoutingType.
| Note: | This object can be set only during row creation. |
List of types and subtypes of data buffers for which this routing entry is valid. A maximum of 32 type/subtype combinations are allowed. The types are restricted to one of FML, VIEW, X_C_TYPE, or X_COMMON. No subtype can be specified for type FML, and subtypes are required for types VIEW, X_C_TYPE, and X_COMMON (* is not allowed). Note that subtype names should not contain semicolon, colon, comma, or asterisk characters. Duplicate type/subtype pairs cannot be specified for the same routing criterion name. More than one routing entry can have the same criterion name as long as the type/subtype pairs are unique. If multiple buffer types are specified for a single routing entry, the data types of the routing field for each buffer type must be the same.
| Note: | This object is applicable only for service-based routing. |
| Note: | This object can be set only during row creation. |
For Service-based Routing: This field is assumed to be an FML buffer or view field name that is identified in an FML field table (using the FLDTBLDIR and FIELDTBLS environment) or an FML view table (using the VIEWDIR and VIEWFILES environment), respectively. This information is used to get the associated field value for data dependent routing during the sending of a message.
For factory-based routing: This is assumed to be a field that is specified in an NVList parameter to:
PortableServer::POA::create_reference_with_criteria
for an interface that has this factory routing criteria associated with it. See the Tuxedo 8.0 or later documentation for more details.
The ranges and associated server groups for a routing criterion are as follows:
criterion:range:grouprange:value|lower-upper| *lower:valueupper:valuevalue: MIN | MAX |numeric|string
group:string| *numeric: [+ | -]digits[.digits][e | E[ | + | - ]digitdigit: 0-9digits:digit[digit]
\ can be used to escape the single-quote character in strings.
lower must be less than upper. A group specified as a string must specify a valid tuxTgroupName.
INTEGER { valid(1) | unknown(2) | invalid(3) }
The values for GET and SET operations are as follows:
GET: valid(1)
GET operation retrieves configuration information for the selected tuxTroutingTable instance(s). The following state indicates the meaning of a tuxTroutingState returned in response to a GET request. States not listed are not returned.
valid(1)
tuxTroutingTable instance is defined. Note that valid(1) is the only valid state for this group. Routing criteria are never active; rather, they are associated through the configuration with service names and are acted upon at run-time to provide data dependent routing.
SET: invalid(3)
SET operation updates configuration information for the selected tuxTroutingTable instance. The following state indicates the meaning of a tuxTroutingState set in a SET request. States not listed cannot be set.
invalid(3)
tuxTroutingTable instance for application. State change allowed only when in the valid(1) state. Successful return leaves the object in the invalid(2) state.
INTEGER { service(1) |factory(2) }
service(1)
factory(2)
| Note: | The routing type affects the validity and possible values for other objects defined for this table. |
| Note: | This object can be set during row creation only. |
INTEGER { short(1) |long(2) |float(3) |double(4) |char(5) |string(6) }
This object specifies the type of tuxTroutingField on which this routing criterion is defined. Its value is valid only for factory-based routing.
| Note: | This object can be set only during row creation. |
This object is used as an index of this table instead of tuxTroutingBufType (for service-based routing) or tuxTroutingField (for factory-based routing) to reduce the size of the index. Its value for service-based routing (tuxRoutingType = service(1)) is equal to the first 30 characters in tuxTroutingBufType.
In case of entries for factory-based routing (tuxRoutingType = factory(2)), the value is always tuxTroutingField.
| Note: | This object can be set only during row creation. |
The tuxTsrvrTbl group contains objects that represent configuration and run-time characteristics of servers within an application. The object values identify and characterize configured servers as well as provide run-time tracking of statistics and resources associated with each server object.
The index into this table is provided by the objects tuxTsrvrGrpNo and tuxTsrvrId. To create a new row in the table, it is necessary to issue a SET request specifying the values of at least tuxTsrvrGrp and tuxTsrvrName.
Logical name of the server group. Server group names cannot contain an asterisk (*), comma, or colon.
| Note: | This object can be set only during row creation. |
Unique (within the server group) server identification number.
| Note: | This object can be set only during row creation. |
Name of the server executable file. The server identified by tuxTsrvrName runs on the machine(s) identified by the tuxTgroupLMID object for this server's server group. If a relative pathname is given, the search for the executable file is done first in tuxTmachineAppDir, then in tuxTmachineTuxDir/bin, then in /bin and /usr/bin, and then in <path>, where <path> is the value of the first PATH= line that appears in the machine environment file, if one exists. Note that the object value returned for an active server is always a full pathname.
Group number associated with this server's group.
INTEGER { active(1) |inactive(2) |migrating(3) |cleaning(4) |
restarting(5) |suspended(6) | partitioned(7) |dead(8) | invalid(10) }
The values for GET and SET operations are as follows:
GET: active(1)|inactive(2)|migrating(3)|cleaning(4)|restarting(5)|
suspended(6)|partitioned(7)|dead(8)
GET operation retrieves configuration and run-time information for the selected tuxTsrvrTbl instance(s). The following states indicate the meaning of a tuxTsrvrState returned in response to a GET request. States not listed are not returned.
active(1)
tuxTsrvrTbl instance is defined and active. The active(1) state is not an indication of whether the server is idle or busy. An active server with a non-0 length tuxTsrvrCurService object should be interpreted as a busy server, that is, one that is processing a service request.
inactive(2)
migrating(3)
tuxTsrvrTbl instance is defined and currently in a state of migration to the server group's secondary logical machine. The secondary logical machine is the one listed in tuxTgroupLMID object that does not match the tuxTgroupCurLMID object.
cleaning(4)
tuxTsrvrTbl instance is defined and currently being cleaned up after by the system due to an abnormal death. Note that restartable servers can enter this state if they exceed tuxTsrvrMaxgen starts/restarts within their tuxTsrvrGrace period.
restarting(5)
tuxTsrvrTbl instance is defined and currently being restarted by the system due to an abnormal death.
suspended(6)
partitioned(7)
tuxTsrvrTbl instance is defined and active; however, the machine where the server is running is currently partitioned from the tuxTdomainMaster site.
dead(8)
tuxTsrvrTbl instance is defined, identified as active in the bulletin board, but currently not running due to an abnormal death. This state exists only until the BBL local to the server notices the death and takes action (restarting(5)|cleaning(4)).
SET: {active(1)|inactive(2)|dead(8)|invalid(10)}
SET operation updates configuration and run-time information for the selected tuxTsrvrTbl instance. The following states indicate the meaning of a tuxTsrvrState set in a SET request. States not listed cannot be set.
active(1)
tuxTsrvrTbl instance. State change is allowed only when the server is in the inactive(2) state. (Servers in the migrating(3) state must be restarted by setting the tuxTgroupState to active(1).) Successful return leaves the object in the active(1) state.
inactive(2)
tuxTsrvrTbl instance. State change is allowed only when the server is in the active(1) state. Successful return leaves the object in the inactive(2) state.
dead(8)
tuxTsrvrTbl instance by sending the server a SIGTERM signal followed by a SIGKILL signal if the server is still running after 20 seconds. Note that by default, a SIGTERM signal causes the server to initiate orderly shutdown and the server becomes inactive even if it is restartable. If a server is processing a long running service or has chosen to disable the SIGTERM signal, then SIGKILL can be used and is treated by the system as an abnormal termination. State change is allowed only when the server is in the active(1) or suspended(6) state. Successful return leaves the object in the inactive(2), cleaning(4), or restarting(5) state.
invalid(10)
tuxTsrvrTbl instance for application. State change is allowed only when the server is in the inactive(2) state. Successful return leaves the object in the invalid(10) state.
Base server identifier. For servers with a tuxTsrvrMax object value of 1, this object is always the same as tuxTsrvrId. However, for servers with a tuxTsrvrMax value of greater than 1, this object indicates the base server identifier for the set of servers configured identically.
Command line options to be passed to server when it is activated. See the servopts(5) manual page for details.
| Note: | Run-time modifications to this object do not affect a running server. |
DisplayString (SIZE(0..256)) (up to 78 bytes for BEA Tuxedo 8.0 or earlier)
Server specific environment file. See tuxTmachineEnvFile for a complete discussion of how this file is used to modify the environment.
| Note: | Run-time modifications to this object do not affect a running server. |
The period of time, in seconds, over which the tuxTsrvrMaxgen object limit applies. The tuxTsrvrGrace value is meaningful only for restartable servers, that is, if the tuxTsrvrRestart object is set to yes(1). When a restarting server would exceed the tuxTsrvrMaxgen limit but the tuxTsrvrGrace period has expired, the system resets the current generation (tuxTsrvrGeneration) to 1 and resets the initial boot time (tuxTsrvrTimeStart) to the current time. A value of 0 for this object indicates that a server should always be restarted.
Note that servers sharing a request queue (that is, equal values for tuxTsrvrRqAddr) should have equal values for this object. If they do not, then the first server activated establishes the run-time value associated with all servers on the queue.
| Note: | Run-time modifications to this object affect a running server and all other active servers with which it is sharing a request queue. However, only the selected server's configuration parameter is modified. Thus, the behavior of the application depends on the order of boot in subsequent activations unless the administrator ensures that all servers sharing a queue have the same value for this object. |
Number of generations allowed for a restartable server (tuxTsrvrRestart == yes(1)) over the specified grace period (tuxTsrvrGrace). The initial activation of the server counts as one generation and each restart also counts as one. Processing after the maximum generations is exceeded is discussed above with respect to tuxTsrvrGrace.
Note that servers sharing a request queue (that is, equal values for tuxTsrvrRqAddr) should have equal values for this object. If they do not, then the first server activated establishes the run-time value associated with all servers on the queue.
| Note: | Run-time modifications to this object affect a running server and all other active servers with which it is sharing a request queue. However, only the selected server's configuration parameter is modified. Thus, the behavior of the application depends on the order of boot in subsequent activations unless the administrator ensures that all servers sharing a queue have the same value for this object. |
Maximum number of occurrences of the server to be booted. Initially, tmboot(1) boots tuxTsrvrMin objects of the server, and additional objects can be started individually (by starting a particular server id) or through automatic spawning (conversational servers only). Run-time modifications to this object affect all running servers in the set of identically configured servers (see tuxTsrvrBaseSrvId above) as well as the configuration definition of the server.
Minimum number of occurrences of the server to be booted by tmboot(1). If a tuxTsrvrRqAddr is specified and tuxTsrvrMin is greater than 1, then the servers form an MSSQ set. The server identifiers for the servers are tuxTsrvrId up to tuxTsrvrId + tuxTsrvrMax - 1. All occurrences of the server have the same sequence number, as well as any other server parameters.
| Note: | Run-time modifications to this object do not affect a running server. |
DisplayString (SIZE(0..256)) (up to 78 bytes for BEA Tuxedo 8.0 or earlier)
Application-specified command to be executed in parallel with the system restart of an application server. This command must be an executable file.
Note that servers sharing a request queue (that is, equal values for tuxTsrvrRqAddr) should have equal values for this object. If they do not, then the first server activated establishes the run-time value associated with all servers on the queue.
| Note: | Run-time modifications to this object affect a running server and all other active servers with which it shares a request queue. However, only the selected server's configuration parameter is modified. Thus, the behavior of the application depends on the order of boot in subsequent activations unless the administrator ensures that all servers sharing a queue have the same value for this object. |
Restartable yes(1) or non-restartable no(2) server. If server migration is specified for this server group (tuxTdomainOptions = migrate(2) and tuxTgroupLMID with alternate site), this object must be set to yes(1).
Note that servers sharing a request queue (that is, equal values for tuxTsrvrRqAddr) should have equal values for this object. If they do not, the first server activated establishes the run-time value associated with all servers on the queue.
| Note: | Run-time modifications to this object affect a running server and all other active servers with which it shares a request queue. However, only the selected server's configuration parameter is modified. Thus, the behavior of the application depends on the order of boot in subsequent activations unless the administrator ensures that all servers sharing a queue have the same value for this object. |
Specifies when this server should be booted (tmboot(1)) or shutdown (tmshutdown(1)) relative to other servers. If two servers are given the same sequence number, it is possible for tmboot(1) to boot them in parallel and for tmshutdown(1) to shut them down in parallel. tuxTsrvrTbl instances added without a tuxTsrvrSequence object specified or with an invalid value have one generated for them that is 10,000 or more and is higher than any other automatically selected default value. Servers are booted by tmboot(1) in increasing order of sequence number and shutdown by tmshutdown(1) in decreasing order. Run-time modifications to this object affect only tmboot(1) and tmshutdown(1) and affect the order in which running servers can be shutdown by a subsequent invocation of tmshutdown(1).
INTEGER { fastpath(1) | protected(2) }
Mode used by Tuxedo system libraries within this server process to gain access to Tuxedo system's internal tables. See tuxTdomainSystemAccess for a complete discussion of this object.
| Note: | Run-time modifications to this object do not affect a running server. |
Conversational server yes(1) or request/response server no(2).
Specifies whether to allocate a separate reply queue for the server
(tuxTsrvrReplyQ == yes(1)). MSSQ servers that expect to receive replies should set this object to yes(1).
UNIX system permissions for the server's reply queue. If a separate reply queue is not allocated (tuxTsrvrReplyQ == no(2)), this object is ignored. The tuxTsrvrRpPerm value is a string representation of octal numbers starting with a leading 0 0001 through 0777.
| Note: | This object is a UNIX-system-specific object that cannot be returned if the platform on which the application is being run is not UNIX-based. |
Symbolic address of the request queue for the server. Specifying the same tuxTsrvrRqAddr object value for more than one server is the way multiple server, single queue (MSSQ) sets are defined. Servers with the same tuxTsrvrRqAddr object value must be in the same server group.
UNIX system permissions for the server's request queue. The tuxTsrvrRqPerm value is a string representation of octal numbers starting with a leading 0 0001 through 0777.
| Note: | This object is a UNIX-system-specific object that cannot be returned if the platform on which the application is being run is not UNIX-based. |
Generation of the server. When a server is initially booted via tmboot(1) or activated through the SNMP agent, its generation is set to 1. Each time the server dies abnormally and is restarted, its generation is incremented. Note that when tuxTsrvrMaxgen is exceeded and tuxTsrvrGrace has expired, the server is restarted with the generation reset to 1.
UNIX system process identifier for the server. Note that this value cannot be a unique value since servers can be located on different machines, allowing for duplication of process identifiers.
| Note: | This object is a UNIX-system-specific object that cannot be returned if the platform on which the application is being run is not UNIX-based. |
UNIX system message queue identifier for the server's reply queue. If a separate reply queue is not allocated (tuxTsrvrReplyQ == no(2)), the tuxTsrvrRqid value is the same as the tuxTsrvrRqId value.
| Note: | This object is a UNIX-system-specific object that cannot be returned if the platform on which the application is being run is not UNIX-based. |
UNIX system message queue identifier for the server's request queue. If a separate reply queue is not allocated (tuxTsrvrReplyQ == no(2)), the tuxTsrvrRpId value is the same as the tuxTsrvrRpid value.
| Note: | This object is a UNIX-system-specific object that cannot be returned if the platform on which the application is being run is not UNIX-based. |
Time, in seconds, since 00:00:00 UTC, January 1, 1970, as returned by the time(2) system call on local host, when the server was last started or restarted.
Time, in seconds, since 00:00:00 UTC, January 1, 1970, as returned by the time(2) system call on local host, when the server was first started. Restarts of the server do not reset this value; however, if tuxTsrvrMaxgen is exceeded and tuxTsrvrGrace is expired, this object is reset to the time of the restart.
Specifies the number of server dispatch threads started on the initial server boot. This object is effective only if the server has been built with the buildserver -t command.
The separate dispatcher thread that is used when the value of tuxTsrvrMaxDispatchThreads is greater than one is not counted as part of the tuxTsrvrMinDispatchThreads value. The value of tuxTsrvrMinDispatchThreads must be less than the value of tuxTsrvrMaxDispatchThreads. If this object is not specified, the default is 0.
Specifies the maximum number of concurrently dispatched threads that each server process can spawn. This object is effective only if the server has been built with the buildserver -t command.
If tuxTsrvrMaxDispatchThreads is greater than one, a separate dispatcher thread is used and does not count against this limit. The value of tuxTsrvrMinDispatchThreads must be less than the value of tuxTsrvrMaxDispatchThreads. If this object is not specified, the default is 1.
If this object is not specified or if the value specified is 0, the operating system default is used. This option affects the server only when a value greater than 1 is specified for tuxTsrvrMaxDispatchThreads.
The tuxTsrvrTblExt group is an extension of tuxTsrvrTbl. Objects in this table are only accessible through a Tuxedo SNMP agent installed on the local machine.
Unique (within the server group) server identification number.
Group number associated with this server's group.
Number of conversations initiated by this server through tpconnect(3).
Number of dequeue operations initiated by this server through tpdequeue(3).
Number of enqueue operations initiated by this server through tpenqueue(3).
Number of postings initiated by this server through tppost(3).
Number of requests made by this server through tpcall(3) or tpacall(3).
Number of subscriptions made by this server through tpsubscribe(3).
Number of transactions begun by this server since its last (re)start.
Number of transactions aborted by this server since its last (re)start.
Number of transactions committed by this server since its last (re)start.
Total number of requests completed by this server. For conversational servers (tuxTsrvrConv == yes(1)), the tuxTsrvrTotReqC value indicates the number of completed incoming conversations. The tuxTsrvrTotReqC value is a run-time value that is kept across server restart but is lost at server shutdown.
Total workload completed by this server. For conversational servers (tuxTsrvrConv == yes(1)), the tuxTsrvrTotWorkL value indicates the workload of completed incoming conversations. The tuxTsrvrTotWorkL value is a run-time value that is kept across server restart but is lost at server shutdown.
Logical machine for the initiating client or server. The initiating client or server is the process that made the service request on which the server is currently working.
UNIX system process identifier for the initiating client or server.
| Note: | This object is a UNIX-system-specific object that cannot be returned if the platform on which the application is being run is not UNIX-based. |
INTEGER { yes(1) | no(2) | null(3) }
yes(1)
no(2)
INTEGER { complete(1) | logged(2) }
The setting of the TP_COMMIT_CONTROL characteristic for this server. For details on this characteristic, see the description of the Tuxedo system ATMI function tpscmt(3).
Number of conversations initiated by this server through tpconnect(3) that are still active.
Number of requests initiated by this server through tpcall(3) or tpacall(3) that are still active.
Service name, if any, on which the server is currently working.
Current time, in seconds, since 00:00:00 UTC, January 1, 1970, as on the local host. This object can be used to compute elapsed time from the tuxTsrvrTimeStart and tuxTsrvrTimeRestart object values.
Server group number (tuxTgroupNo) of the last service request made or conversation initiated from this server outward.
Time left in seconds, if any, for this server to process the current service request. A value of 0 for an active service indicates that no timeout processing is being done. See tuxTsvcTimeOut for more information.
Time left, in seconds, for this server to receive the reply for which it is currently waiting before it times out. This timeout can be a transactional timeout or a blocking timeout.
Current transaction level for this server. 0 indicates that the server is not currently involved in a transaction.
INTEGER { active(1) | inactive(2) | migrating(3) | cleaning(4) | restarting(5) | suspended(6) | partitioned(7) | dead(8) }
Refer to description of tuxTsrvrState for details.
Name of group to which this server belongs. This object is included for readability purposes only.
The number of entries in use in the bulletin board object table for this server.
The interface name of the interface currently active in this server.
Current number of active service dispatch threads for this server.
Highest number of active service dispatch threads created for this server since its last restart. This number can differ from the number of service calls, because an administrator can specify parameters that control the caching of idle service threads.
Total number of active service dispatch threads created for this server since its last restart.
The tuxTsvcTbl group contains objects that represent configuration characteristics of services within an application. The object values identify and characterize configured services. A tuxTsvcTbl object provides activation time configuration objects for services not specifically configured as part of the tuxTsvcGrp group.
The index into this table is tuxTsvcName. Objects in this group are only accessible through a Tuxedo SNMP agent installed on the local machine. To create a new row in the table, it is necessary to issue a SET request for a non-existing row in the table.
| Note: | This object can be set only during row creation. |
INTEGER { app(1) | callable(2) | system(3) | unknown(4) }
app(1)
callable(2)
system(3)
INTEGER { active(1) | inactive(2) | invalid(3) }
The values for GET and SET operations are as follows:
GET: {active(1)|inactive(2)}
GET operation retrieves configuration information for the selected tuxTsvcTbl instance(s). The following states indicate the meaning of a tuxTsvcState returned in response to a GET request. States not listed are not returned.
active(1)
tuxTsvcTbl instance is defined and at least one tuxTsvcGrp object with a matching tuxTsvcName value is active.
inactive(2)
tuxTsvcTbl instance is defined and no tuxTsvcGrp object with a matching tuxTsvcName value is active.
SET: invalid(3)
SET operation updates configuration information for the selected tuxTsvcTbl instance. The following state indicates the meaning of a tuxTsvcState set in a SET request. States not listed cannot be set.
invalid(3)
tuxTsvcTbl instance for application. State change is allowed only when the service is in the inactive(2) state. Successful return leaves the object in the invalid(3) state.
Automatically begin a transaction.
yes(1)
no(2)
| Note: | Run-time updates to this object are not reflected in active tuxTsvcGrp objects. |
This tuxTsvcTbl object imposes the indicated load on the system. Service loads are used for load balancing purposes, that is, queues with higher enqueued workloads are less likely to be chosen for a new request. Service loads have meaning only if the tuxTdomainLoadBalance is set to yes(1).
| Note: | Run-time updates to this object are not reflected in active tuxTsvcGrp objects. |
This tuxTsvcTbl object has the indicated dequeuing priority. If multiple service requests are waiting on a queue for servicing, the higher priority requests are serviced first.
| Note: | Run-time updates to this object are not reflected in active tuxTsvcGrp objects. |
Time limit (in seconds) for processing requests for this service name. Servers processing service requests for this service are abortively terminated (kill -9) if they exceed the specified time limit in processing the request. A value of 0 for this object indicates that the service should not be abortively terminated.
| Note: | Run-time updates to this object are not reflected in active tuxTsvcGrp objects. |
Transaction timeout value (in seconds) for transactions automatically started for this tuxTsvcTbl object. Transactions are started automatically when a request not in transaction mode is received and the tuxTsvcAutoTran object value for the service is yes(1).
| Note: | Run-time updates to this object are not reflected in active tuxTsvcGrp objects. |
type1[:subtype1[,subtype2 . . . ]][;type2[:subtype3[,. . . ]]] . . .
List of types and subtypes of data buffers accepted by this service. A maximum of 32 type/subtype combinations are allowed. Types of data buffers provided with Tuxedo system are FML (for FML buffers), VIEW, X_C_TYPE, or X_COMMON (for FMLviews), STRING (for NULL terminated character arrays), and CARRAY or X_OCTET (for a character array that is neither encoded nor decoded during transmission). Of these types, only VIEW, X_C_TYPE, and X_COMMON have subtypes. A VIEW subtype gives the name of the particular VIEW expected by the service. Application types and subtypes can also be added (see tuxtypes(5)). For a buffer type that has subtypes, "*" can be specified for the subtype to indicate that the service accepts all subtypes for the associated buffer type.
A single service can only interpret a fixed number of buffer types, namely those found in its buffer type switch (see tuxtypes(5)). If the tuxTsvcBufType value is set to ALL, that service accepts all buffer types found in its buffer type switch.
A type name can be 8 characters or less in length and a subtype name can be 16 characters or less in length. Note that type and subtype names should not contain semicolon, colon, comma, or asterisk characters.
| Note: | The tuxTsvcBufType value represents the buffer types that must be supported by each and every instance of an application service with this service name. Since this object value is processed at service activation time, updates to this object are allowed only when there are no active tuxTsvcGrp objects with matching service names. |
This tuxTsvcTbl object has the indicated routing criteria name. Active updates to this object are reflected in all associated tuxTsvcGrp objects.
If set to yes, every application service in this group requires an encrypted input message buffer.
If set to yes, every application service in this group requires a valid digital signature on its input message buffer.
The tuxTsvcGrp group contains objects that represent configuration and run-time characteristics of services/groups within an application. The object values identify and characterize configured services/groups as well as provide run-time tracking of statistics and resources associated with each object.
Both tuxTsvcTbl and tuxTsvcGrp define activation time object values for service names within the application. When a new service is activated (advertised), either due to initial activation of a server or due to a call to tpadvertise(3), the following hierarchy exists for determining the object values to be used at service startup time.
tuxTsvcGrp entry exists (matching service name and server group), the objects defined in that object are used to initially configure the advertised service. tuxTsvcTbl entry exists (matching service name), the objects defined in that object are used to initially configure the advertised service. tuxTsvcGrp entries are found with matching service name value, the first one found is used to initially configure the advertised service. Objects in this group are only accessible through a Tuxedo SNMP agent installed on the local machine.
To create a new row in the table, it is necessary to issue a SET request that specifies at least tuxTsvcGrpName. The combination of values specified for tuxTsvcGrpName and tuxTsvcGrpSvcName in the SET request should not correspond to an existing row. If the value of tuxTsvcSrvrId is zero in the SET request, the service entry is configured but not activated (advertised). If tuxTsvcSrvrId is not set to zero, the service is activated using the value of tuxTsvcSrvrId to identify the server instance.
Server group name. Server group names cannot contain an asterisk.
INTEGER { active(1) | inactive(2) | invalid(3) }
The values for GET and SET operations are as follows:
GET: active(1)|inactive(2)
GET operation retrieves configuration information for the selected tuxTsvcGrpState instance(s). The following states indicate the meaning of a tuxTsvcGrpState returned in response to a GET request. States not listed are not returned.
active(1)
inactive(2)
SET: invalid(3)
SET operation removes the corresponding tuxTsvcGrp instance. When a tuxTsvcGrp instance is deleted it also removes the associated tuxTsvcSrvr instances that correspond to server instances that are a part of the group advertising this service. This transition is permissible only in inactive(2) state.
Automatically begin a transaction (yes(1)) when a service request message is received for this service if the request is not already in transaction mode.
This tuxTsvcGrp instance imposes the indicated load on the system. Service loads are used for load balancing purposes, that is, queues with higher enqueued workloads are less likely to be chosen for a new request.
This tuxTsvcGrp object has the indicated dequeuing priority. If multiple service requests are waiting on a queue for servicing, the higher priority requests are serviced first.
Time limit (in seconds) for processing requests for this service name. Servers processing service requests for this service are abortively terminated (kill -9) if they exceed the specified time limit in processing the request. A value of 0 for this object indicates that the service should not be abortively terminated.
Transaction timeout value (in seconds) for transactions automatically started for this tuxTsvcGrp instance. Transactions are started automatically when a request not in transaction mode is received and the tuxTsvcGrpAutoTran object value for the service is yes(1).
Current logical machine on which an active server that offers this service is running.
Symbolic address of the request queue for an active server that offers this service. See tuxTsrvrRqAddr for more information on this object.
Server ID of which the service is a part. The user can also set the value of this object to activate (advertise) one or more tuxTsvcGrp instances. The value provided to set this object is used to activate another instance of tuxTsvcGrp.
Function name within the associated server assigned to process requests for this service. When this object is specified, the tuxTsvcGrp instance is activated (advertised). The user needs to specify the server ID of the corresponding server instance (tuxTsvcSrvrId) in the SNMP index. This object can be updated only during row creation.
Number of service requests completed with respect to the retrieved active or suspended instance since it was activated (advertised).
| Note: | The tuxTsvcSrvrNcompleted value is returned only when tuxTdomainLoadBalance is equal to yes(1). |
Number of requests currently enqueued to this service. The tuxTsvcSrvrNqueued value is incremented at enqueue time and decremented when the server dequeues the request.
| Note: | The tuxTsvcSrvrNqueued value is returned only when tuxTdomainModel is set to single-machine(1) and tuxTdomainLoadBalance is set to yes(1). |
The tuxTlistenTbl group contains objects that represent run-time characteristics of Tuxedo listener processes for a distributed application.
INTEGER { inactive(2) | active(1) }
The values for GET and SET operations are as follows:
GET: {active(1)|inactive(2)}
GET operation retrieves run-time information for the selected tuxTlistenTbl instance(s). The following states indicate the meaning of a tuxTlistenState returned in response to a GET request. States not listed are not returned.
active(1)
inactive(2)
The tuxTranTbl group contains objects that represent run-time characteristics of active transactions within the application. The following objects comprise the index for rows in this table: tuxTranIndx1, tuxTranIndx2, tuxTranIndx3, tuxTranIndx4, tuxTranIndx5. Objects in this table are accessible only through a Tuxedo SNMP agent running on the local machine.
Logical machine identifier of the server group responsible for coordinating the transaction.
Transaction identifier as returned from tpsuspend(3) mapped to a string representation. The data in this field should not be interpreted directly by the user except for equality comparison.
Transaction identifier as returned from tx_info(3) mapped to a string representation. The data in this field should not be interpreted directly by the user except for equality comparison.
This number is purely for unique indexing of this table.
This number is purely for unique indexing of this table.
This number is purely for unique indexing of this table.
This number is purely for unique indexing of this table.
This number is purely for unique indexing of this table.
INTEGER { active(1) | abort-only(2) | aborted(3) | com-called(4) |ready(5) | decided(6) | suspended(7) }
The values for GET and SET operations are as follows:
GET: active(1)|abort-only(2)|aborted(3)|com-called(4)|ready(5)|
decided(6)|suspended(7)
GET operation retrieves run-time information for the selected tuxTranTbl instance(s). The following states indicate the meaning of a tuxTranState object. States not listed are not returned. Note that distinct objects pertaining to the same global transaction (equivalent transaction identifiers) can indicate differing states. In general, the state indicated on the coordinator's site (tuxTranCoordLmid) indicates the true state of the transaction. The exception is when a noncoordinator site notices a condition that transitions the transaction state to abort-only(2). This transition is eventually propagated to the coordinator site and results in the rollback of the transaction, but this change cannot be immediately reflected on the coordinator site.
active(1)
abort-only(2)
aborted(3)
com-called(4)
tpcommit(3) and the first phase of two-phase commit has begun on the retrieval site.
ready(5)
decided(6)
suspended(7)
SET: aborted(3)
SET operation updates run-time information for the selected tuxTranTbl instance. The following state indicates the meaning of a tuxTranState set in a SET request. States not listed cannot be set.
aborted(3)
tuxTranTbl instance for the application. State change is allowed only when the transaction is in the active(1), abort-only(2), or com-called(4) state. Cannot be accompanied by a change to tuxTranGstate. Successful return leaves the object in the aborted(3) state.
Time left (in seconds) before the transaction times out on the retrieval site. Note that the tuxTranTimeOut value is returned only when the transaction state is active(1).
Number of groups identified as participants in the transaction by the information returned from the retrieval site.
Index of the first group-specific object values (tuxTranGrpNo and tuxTranGstate) corresponding to this object.
Group number of the participating group.
INTEGER { active(1) | aborted(2) | rd-only(3) | ready(4) | hcommit(5) | habort(6) | done(7) | pre-prepare(8) | post-abort(9) | post-commit(10) | unknown(11) )
The values for GET and SET operations are as follows:
GET: active(1)|aborted(2)|rd-only(3)|ready(4)|hcommit(5)|habort(6)
|done(7)
GET operation retrieves run-time information for the selected tuxTranTbl instance(s) pertaining to the indicated group. The following states indicate the meaning of a tuxTranGstate returned in response to a GET request. States not listed are not returned. Note that distinct objects pertaining to the same global transaction (equivalent transaction identifiers) can indicate differing states for individual groups. In general, the state indicated on the group's site indicates the true state of the group's participation in the transaction. The exception is when the coordinator site determines that the transaction should abort and sets each participant group state to aborted(2). This transition is propagated to the group's site and results in the rollback of the group's work in the transaction, but cannot be reflected immediately
active(1)
aborted(2)
rd-only(3)
ready(4)
hcommit(5)
habort(6)
done(7)
pre-prepare(8)
xa_end (TMSUSPEND) during the course of transactional work and that commit processing is beginning. This state exists until either (1) all servers that called xa_end (TMSUSPEND) have caused a call to xa_end (TMSUCCESS), at which point the group state becomes ready, or (2) one of the target servers does a rollback of the transaction, at which point the group state becomes either post-abort(9) or aborted(2).
| Note: | This state is supported only for Tuxedo 8.0 or later applications. |
post-abort(9)
xa_end (TPFAIL) and that the TMS has not yet called xa_rollback(). In this case, other Tuxedo servers that called xa_end (TMSUSPEND) are being notified by the TMS in order to clean up their associated CORBA objects.
| Note: | This state is supported only for Tuxedo 8.0 or later applications. |
post-commit(10)
| Note: | This state is supported only for Tuxedo 8.0 or later applications. |
SET: hcommit(5)| habort(6)
SET operation updates run-time information for the first group in the originating request within the selected tuxTranTbl instance. The following states indicate the meaning of a tuxTranGstate set in a SET request. States not listed cannot be set. State transitions are allowed only when performed within the object representing the group's site.
hcommit(5)
tuxTranGstate is ready, tuxTranState is ready, and the indicated group is not on the coordinator's site. Successful return leaves the object in the hcommit(5) state.
habort(6)
tuxTranGstate is active(1) or ready(4), tuxTranState is ready(4), and the indicated group is not on the coordinator's site. Successful return leaves the object in the habort(6) state.
The tuxTulogTable group contains objects that represent run-time characteristics of userlog (ULOG) files within an application. The index into this table is tuxTulogSerNo. The values returned for objects in this table are controlled by the MIB control group tuxTulogCtrl.
A running serial number for the rows in tuxTulogTable.
Retrieval machine logical machine identifier.
Month, day, and year of the log file.
Time at which the message was generated.
Line number of the message in the log file.
The entire text of the userlog message as it appears in the userlog file.
Transaction identifier as returned from tpsuspend(3). The data in this field should not be interpreted directly by the user except for equality comparison. Messages not associated with transactions retrieve a 0-length string as the value for this object.
Transaction identifier as returned from tx_info(3). The data in this field should not be interpreted directly by the user except for equality comparison. Messages not associated with transactions retrieve a 0-length string as the value for this object.
Process identifier of the client or server that generated the userlog message.
Catalog name from which the message was derived, if any.
Catalog message number, if the message was derived from a catalog.
Process name of the client or server that generated the userlog message.
Identifier for the thread that wrote this userlog message.
Identifier for this particular application association.
The tuxTulogCtrl group contains objects that control the userlog (ULOG) messages returned by the tuxTulogTable.
Logical machine ID to qualify machine from where the userlog file is read for tuxTulogTable. By default, the ULOG files from the local host are returned, in accordance to the ULOGPFX. To revert to the default setting, set this object to null.
Physical machine name to qualify the source machine for userlog messages to be listed in tuxTulogTable. By default, messages from all hosts within ULOG files qualified by tuxTulogLmidCtrl are returned. To revert to the default setting, set this object to null.
Date value to qualify userlog messages listed in tuxTulogTable. Default value is current date. To reset the value of the qualifier to its default, set this object to 0.
Starting time of the time range for which the userlog messages are listed in tuxTulogTable. This number is calculated as under - "hrs*10000 + mins*100 + secs". The default value is 0.
Ending time of the time range for which the userlog messages are listed in tuxTulogTable. This number is calculated as under - "hrs*10000 + mins*100 + secs". By default, the maximum value is considered. To revert to the default setting, set this object to 0.
Beginning line number from which the userlog messages are listed in tuxTulogTable. By default, all messages are returned. To revert to the default setting, set this object to 0.
Regular expression to qualify userlog messages listed in tuxTulogTable on the basis of the message body. By default, all messages are listed. To revert to the default setting, set this object to null.
Value of tuxTpTranId to qualify messages to be displayed in the in tuxTulogTable. By default, all messages are returned. To revert to the default setting, set it to null.
Value of tuxTranXid to qualify messages to be displayed in the in tuxTulogTable. By default, all messages are returned. To revert to the default setting, set it to null.
Value of process Id of the source to qualify messages to be displayed in the tuxTulogTable. By default, messages with any pid are listed. To revert to the default setting, set this object to 0.
Regular expression to qualify userlog messages to be listed in tuxTulogTable on the basis of message severity, if any. By default, messages with any severity are listed. To revert to the default setting, set this object to null.
Regular expression to qualify userlog messages to be listed in tuxTulogTable on the basis of the catalog name, if any. By default, messages from all catalogs are listed. To revert to the default setting, set this object to null.
Message number in catalog to qualify userlog messages to be listed in tuxTulogTable. By default, all message numbers are returned. To revert to the default setting, set this object to 0.
Regular expression to qualify userlog messages to be listed in tuxTulogTable on the basis of the process name that generated the message, if known. By default, all messages are returned. To revert to the default setting, set this object to null.
The tuxTnetGrpTbl group contains objects that represent application characteristics of network groups. Network groups are groups of logical machine IDs that can communicate over the network address defined in the tuxTnetMapNaddr object in the tuxTnetMapTbl table entry. For row creation, a SET request with tuxTnetGrpName, tuxTnetGrpNo, and tuxTnetGrpPrio is required. tuxTnetGrpNo provides the index into this table.
Logical name of the network group. A group name is a string of printable characters and cannot contain a pound sign (#), comma (,), colon (:), or newline character. This object can be updated only during row creation.
Group identifier of the network group. This object can be updated only during row creation.
INTEGER { valid(1) | invalid(2) }
A GET request retrieves configuration information for the selected tuxTnetGrpTbl instance (or instances). The following states indicate the meaning of the value that is returned:
GET: valid(1)
SET: invalid(2)
States not listed are not returned.
The priority band for this network group. All network groups that have an equivalent band priority are used in parallel.
The instances in the tuxTnetMapTbl associate tuxTmachineLmids to an instance in the tuxTnetGrpTbl. The rows in this table identify which logical machines belong to which network groups. For row creation, a SET request with at least tuxTnetMapNaddr is needed. The index into this table is provided by tuxTnetMapGrpNo and tuxTnetMapLmid.
The logical name of the network group. A group name is a string of printable characters and cannot contain a pound sign (#), comma (,), colon (:), or a newline character.
Identifier for this logical network group. This object can be updated only during row creation.
Logical machine name for this network mapping. This object can be updated only during row creation.
INTEGER { valid(1) | invalid(2) }
A GET request retrieves configuration information for the selected tuxTnetMapTbl instance (or instances). The following states indicate the meaning of the value of tuxTnetMapState that is returned:
GET: valid(1)
SET: invalid(2)
tuxTnetMapTbl instance from the application. If any network links are active as a result of the mapping, they are disconnected. This disconnection can cause a state change in tuxTBridgeTbl instances associated with the network links.
States not listed are not returned.
DisplayString (SIZE(1..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 a networked application, that is, if the value of tuxTdomainOptions is lan(1). If the string is of the form 0xhex-digits or \\xhex-digits, it must contain an even number of valid hexadecimal digits. These forms are translated internally into a character array containing the hexadecimal representation of the string specified. For TCP/IP addresses, either the //hostname:port or #.#.#.#:port format is used.
INTEGER { none(1) | 40-bit(2) | 128-bit(3) | unknown(4) }
Specifies the required level of encryption when establishing a network link to this machine.
none(1)
40-bit(2) and 128-bit(3)
The default value is none(1). Modifications to this object do not affect network links that have already been established.
INTEGER {none(1) | 40-bit(2) | 128-bit(3) | unknown(4) }
Encryption can be negotiated up to the specified level when establishing a network link.
none(1)
40-bit(2) and 128-bit(3)
The default value is 128-bit(3). Modifications to this object do not affect network links that are already established.
The tuxTserverCtxtTbl group contains objects that represent configuration and run-time characteristics of individual server dispatch contexts within an application. This group is defined for both single-context and multi-context servers. For single-context servers, the object values in this group are repeated as part of the tuxTsrvrTbl group. The objects in this group are read-only.
These object values provide run-time tracking of statistics and resources associated with each server dispatch context.
Logical name of the server group. Server group names cannot contain an asterisk (*), comma (,), or colon (:).
Unique (within the server group) server identification number.
Identifier of this particular server context.
Logical machine for the initiating client or server. The initiating client or server is the process that made the service request on which the server is currently working.
UNIX system process identifier for the initiating client or server.
Limitation: This object is a UNIX-system-specific object that cannot be returned if the platform on which the application is being run is not UNIX-based.
The initiating client or server is expecting a reply (yes(1)) or is not expecting a reply (no(2)).
INTEGER { complete(1) | logged(2) }
This object value is the setting of the TP_COMMIT_CONTROL characteristic for this server.
See the description of the BEA Tuxedo ATMI function tpscmt(3c) for details on this characteristic.
Number of conversations initiated by this server through tpconnect() that are still active.
Number of requests initiated by this server through tpcall() or tpacall() that are still active.
Service name, if any, on which the server is currently working.
Time left (in seconds), if any, for this server to process the current service request. A value of 0 for an active service indicates that no time out processing is being done.
See tuxTsvcTbl: tuxTsvcTimeOut for more information.
Server group number (tuxTgroupTable: tuxTgroupNo) of the last service request made or conversation initiated from this server outward.
Time left (in seconds) for this server to receive the reply for which it is currently waiting before it will time out. This timeout can be a transactional timeout or a blocking timeout.
Current transaction level for this server. 0 indicates that the server is not currently involved in a transaction.
You can use the Tuxedo event filters to define a subset of Tuxedo event notifications to be generated for each Tuxedo domain being monitored. The beaEventFilters group consists of the following object and group (table).
INTEGER { sync(1) | dirty(2) }
When the agent starts, this object value is always sync(1). If any change is done to beaEvtFilterTable through SET requests, the value of this object becomes dirty(2) and the changes made to beaEvtFilterTable do not take effect. The changes made to the beaEvtFilterTable take effect only when you set the value of this object to sync(1). When you set the value to sync(1), all changes since the last synchronization are applied to the event-processing module.
The beaEvtFilterTable group contains objects that represent all the event filters defined for the SNMP Agent. The object values are used to determine the collection of events to be forwarded as SNMP trap notifications.
The columnar objects in the beaEvtFilterTable correspond to fields in the TMEVENT_FILTER entries in the BEA SNMP Agent configuration file (beamgr.conf). For more detail, see
Configuration Files" in the BEA SNMP Agent Administration Guide.
| Note: | Changes to this table are applied only when beaEvtFilterStatus is set to sync(1). |
A unique identifier for the event filter within the filter table.
| Note: | This object can be SET only during row creation. |
This logical agent name of the agent supporting this filter. This object is provided only for user convenience since the MIB only returns the event filters for the agent that was queried.
An event name expression, which is a regular expression. For the format of regular expressions, see reference page tpsubscribe(3c) in BEA Tuxedo ATMI C Function Reference. For a Tuxedo system event to be forwarded as an SNMP trap, its name should match this expression. For a list of Tuxedo event names, see reference page EVENTS(5) in BEA Tuxedo File Formats, Data Descriptions, MIBs, and System Processes Reference. The default for this object is all system events.
\.Sys.* matches all system events. (This event name expression is the default.)
\.SysServer.*
matches all system events related to servers.
A value of NONE blocks all events from being forwarded by the selected agent and overrides any other filter table entries for the same logical agent name.
An event filter expression. Each Tuxedo event is accompanied by an FML buffer that contains pertinent information about the event. The buffer's contents are evaluated with respect to this filter, if it is present. The filter must evaluate to TRUE or the event is not forwarded.
The SNMP Agent uses this object as an argument to tpsubscribe(). For more information, see reference page tpsubscribe(3c) in BEA Tuxedo ATMI C Function Reference.
TA_EVENT_SEVERITY=='ERROR' || TA_EVENT_SEVERITY=='WARN'
This filter selects events with a severity of either ERROR or WARNING.
INTEGER { active(1) | inactive(2) | invalid(3) }
This object denotes the current state of the event filter instance.
GET {active(1)|inactive(2)}
GET operation retrieves configuration and run-time information for the selected beaEvtFilterTbl instance(s). The following states indicate the meaning of a beaEvtFilterState returned in response to a GET request. States not listed are not returned.
active(1)
inactive(2)
SET {active(1)|inactive(2)|invalid(3)}
SET operation updates configuration and run-time information for the selected beaEvtFilterTbl instance. The following states indicate the meaning of a beaEvtFilterState set in a SET request. States not listed cannot be set.
active(1)
inactive(2)
invalid(3)
|