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.
A 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.
A 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.
Activate the 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.
Deactivate the 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.
Suspend the 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.
Activate the 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.
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.
A 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.
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.
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.
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.
A 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.
Activate a suspended(2) tuxTclientTbl instance. State change allowed only when in the
suspended(2) state. Successful return leaves the object in the
active(1) state.
Suspend the 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.
Abortively deactivate the 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.
|
DisplayString (
SIZE(
1..256)) (up to 78 bytes for Oracle Tuxedo 8.0 or earlier)
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 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.
The active(1) state returned reflects one or both sides of an active conversation within the application.
SET operations are not permitted for this group.
Number of tpsend(3) calls made by the originator.
Number of tpsend(3) calls made by the subordinate.
The tuxTdevice group contains the following object and group (table).
DisplayString (
SIZE(
2..256)) (up to 64 bytes for Oracle Tuxedo 8.0 or earlier)
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.
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.
A 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.
A 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.
Delete 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.
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.
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.
A 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.
tuxTdomain group is defined and the master machine is active.
tuxTdomain group is defined and application is inactive.
A 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.
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.
The value 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.
The value 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.
The value 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:
|
Updates to the tuxTdomainSystemAccess value in a running application affect only newly started clients and newly configured tuxTsrvrTbl objects.
|
|
Note:
|
Only the accstats(3) can be set or reset in an active application.
|
where security_mode can have the following values:
The value APP_PW/app_password indicates that application password security is enforced. Clients must provide the application password during initialization.
The value USER_AUTH is similar to
APP_PW, but indicates also that per-user authentication is done during client initialization.
The value 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
The value MANDATORY_ACL is similar to
ACL, but permission is denied if an associated ACL is not found for the name.
On a GET operation, this object only returns the security mode; the password is not returned.
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.
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.
A 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.
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.
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.
A 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.
Activate the 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.
Deactivate the 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.
Deactivate the 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.
Delete 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.
Identical to a transition to the active(1) state except that this state change is also allowed in the
active(1) state as well as the
inactive(2) and
migrating(3) states.
Suspend the application services in the group. A 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.
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 (:).
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.
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 Oracle 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
If set to “yes,” every application service in this group requires an encrypted message buffer.
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.
DisplayString (
SIZE (
2..256)) (up to 78 bytes for Oracle Tuxedo 8.0 or earlier)
DisplayString (
SIZE(
2..256)) (up to 78 bytes for Oracle Tuxedo 8.0 or earlier)
DisplayString (
SIZE (
2..256)) (up to 78 bytes for Oracle Tuxedo 8.0 or earlier)
A 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
tuxTmachineTable instance defined and active (administrative servers, that is, DBBL, BBL, and BRIDGE).
tuxTmachineTable instance defined, listed in accessible bulletin boards as active, but currently unreachable.
A 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.
Activate the 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.
Deactivate the 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.
Delete 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.
Activate the 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.
|
Note:
|
State change to inactive(2) is allowed only for non-master machines. The master site administrative processes are deactivated through the tuxTdomain group.
|
DisplayString (
SIZE(
2..256)) (up to 78 bytes for Oracle Tuxedo 8.0 or earlier)
DisplayString (
SIZE(
0..256)) (up to 78 bytes for Oracle 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.
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.
DisplayString (
SIZE (
0..256)) (up to 64 bytes for Oracle Tuxedo 8.0 or earlier)
DisplayString (
SIZE (
0..256)) (up to 78 bytes for Oracle Tuxedo 8.0 or earlier)
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 Oracle 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.
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.
|
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 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.
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.
A 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.
tuxTmsgTable object active. This state corresponds exactly to the related
tuxTmachineTable object being active.
SET operations are not permitted on this group.
Time of the last msgctl(2) operation that changed a member of the
msqid_ds structure associated with 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.
A 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.
A 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.
|
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.
|
|
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.
|
|
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.
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.
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.
criterion:
range:
group
range:
value |
lower -
upper | *
lower:
value upper:
value value: MIN | MAX | numeric | string
group: string | *
numeric: [+ | -]digits[.digits][e | E[ | + | - ] digit
digit: 0-9
digits: 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.
A 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.
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.
A 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.
Delete tuxTroutingTable instance for application. State change allowed only when in the
valid(1) state. Successful return leaves the object in the
invalid(2) state.
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.
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.
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.
A 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.
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.
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.
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.
tuxTsrvrTbl instance is defined and currently being restarted by the system due to an abnormal death.
tuxTsrvrTbl instance is defined and currently suspended, pending shutdown.
tuxTsrvrTbl instance is defined and active; however, the machine where the server is running is currently partitioned from the
tuxTdomainMaster site.
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)).
A 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.
Activate the 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.
Deactivate the 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.
Deactivate the 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.
Delete 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.
DisplayString (
SIZE(
0..256)) (up to 78 bytes for Oracle Tuxedo 8.0 or earlier)
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.
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.
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.
DisplayString (
SIZE(
0..256)) (up to 78 bytes for Oracle Tuxedo 8.0 or earlier)
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).
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).
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.
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.
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.
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.
Server group number (tuxTgroupNo) of the last service request made or conversation initiated from this server outward.
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.
A 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.
tuxTsvcTbl instance is defined and at least one
tuxTsvcGrp object with a matching
tuxTsvcName value is active.
tuxTsvcTbl instance is defined and no
tuxTsvcGrp object with a matching
tuxTsvcName value is active.
A 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.
Delete 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.
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).
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:
|
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.
|
1.
|
If a matching configured tuxTsvcGrp entry exists (matching service name and server group), the objects defined in that object are used to initially configure the advertised service.
|
|
2.
|
Otherwise, if a matching configured tuxTsvcTbl entry exists (matching service name), the objects defined in that object are used to initially configure the advertised service.
|
|
3.
|
Otherwise, if any configured tuxTsvcGrp entries are found with matching service name value, the first one found is used to initially configure the advertised service.
|
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.
A 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.
A 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.
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.
|
Note:
|
The tuxTsvcSrvrNcompleted value is returned only when tuxTdomainLoadBalance is equal to yes(1).
|
|
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.
A 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.
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.
A 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.
A 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.
Abort the 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.
A 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
Indicates that the transaction group contains Tuxedo servers that have called 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).
Indicates that a Tuxedo server called 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.
A 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.
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.
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.
The tuxTulogCtrl group contains objects that control the userlog (
ULOG) messages returned by the
tuxTulogTable.
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.
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.
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:
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.
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:
Delete the selected 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.
DisplayString (
SIZE(
1..256)) (up to 78 bytes for Oracle Tuxedo 8.0 or earlier)
The default value is none(1). Modifications to this object do not affect network links that have already been established.
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.
See tuxTsvcTbl: tuxTsvcTimeOut for more information.
Server group number (tuxTgroupTable: tuxTgroupNo) of the last service request made or conversation initiated from this server outward.
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 Oracle SNMP Agent configuration file (
beamgr.conf). For more detail, see
“Configuration Files” in the
Oracle SNMP Agent Administration Guide.
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.
A 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.
A 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.
