The T_DOMAIN class represents global application attributes. These attribute values serve to identify, customize, size, secure, and tune a BEA TUXEDO system application. Many of the attribute values represented here serve as application defaults for other classes represented in this MIB.
There is exactly one object of the T_DOMAIN class for each application. Because of this, there are no key fields defined for this class. A GET operation on this class will always return information representing this single object. Likewise, a SET operation will update it. GETNEXT is not permitted with this class.
1 2num must be a multiple of 5
3Specify num so that num times UID and GID as known to the UNIX System
TA_SCANUNIT is approximately "Default"
Attribute Semantics
TA_IPCKEY: 32K+1 <= num < 262,144
TA_MASTER: LMID1[,LMID2]
INActive applications. SHM mode applications (see TA_MODEL below) may set only the master logical machine identifier. Modifications to this attribute value in an ACTive MP application (see TA_MODEL below) have the following semantics:
A, current backup master LMID B, and secondary LMIDs C, D, . . ., the following scenarios define the semantics of permitted changes to the TA_MASTER attribute in a running MP 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 may 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 reestablished network connections will verify that the two sites connecting share a common view of where the master machine is. Otherwise, the connection will be refused and an appropriate log message generated. The master and backup machines in an ACTive application must always have a BEA 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 TA_MASTER attribute must preserve this relationship.
TA_MODEL: {SHM|MP}
SHM specifies a single machine configuration; only one T_MACHINE object may be specified. MP specifies a multi-machine or network configuration; MP must be specified if a networked application is being defined.
TA_STATE:
GET: {ACTive|INActive}
GET operation will retrieve configuration and run-time information for the T_DOMAIN object. The following states indicate the meaning of a TA_STATE returned in response to a GET request. States not listed will not be returned.
|
|
|
|
|
|
SET: {NEW|INValid|ACTive|INActive|FINactive}
SET operation will update configuration and run-time information for the T_DOMAIN object. The following states indicate the meaning of a TA_STATE set in a SET request. States not listed may not be set.
TA_DOMAINID: string[0...30]
TA_PREFERENCES: string[0...1023]
TA_UID: 0 <= num
T_MACHINE class. Limitation: Changes to this attribute do not affect active or already configured T_MACHINE objects.
TA_GID: 0 <= num
T_MACHINE class. Limitation: Changes to this attribute do not affect active or already configured T_MACHINE objects.
TA_PERM: 0001 <= num <= 0777
T_MACHINE class. Limitation: Changes to this attribute do not affect active or already configured T_MACHINE objects.
TA_LICEXPIRE: string[0 . . . 78]
TA_LICMAXUSERS: 0 <= num < 32K
TA_LICSERIAL: string [0 . . . 78]
TA_MIBMASK: 0 <= num <= 0777
0003 disallows all updates to users other than the administrator or the operator.
TA_MAXACCESSERS: 1 <= num < 32K
T_MACHINE class.
T_MACHINE objects.
TA_MAXCONV: 0 <= num < 32K
T_MACHINE class. Limitation: Changes to this attribute do not affect active or already configured T_MACHINE objects.
TA_MAXGTT: 0 <= num < 32K
T_MACHINE class. Limitation: Changes to this attribute do not affect active or already configured T_MACHINE objects.
TA_MAXBUFSTYPE: 1 <= num < 32K
TA_MAXBUFTYPE: 1 <= num < 32K
TA_MAXDRT: 0 <= num < 32K
T_ROUTING class object is required. Additional entries should be allocated to allow for run-time growth.
TA_MAXGROUPS: 100 <= num < 32,766
TA_MAXNETGROUPS: 1 <= num < 8192
NETWORK section of the TUXCONFIG file. This value must be greater than or equal to 1 and less than 8192. If not specified, the default is 8.
TA_MAXMACHINES: 256 = num 8K-1
TA_MAXQUEUES: 1 <= num 8K
TA_MAXQUEUES is equal to the setting for TA_MAXSERVERS.
TA_MAXRFT: 0 <= num < 32K
TA_RANGES specification is required plus one additional entry per T_ROUTING class object. Additional entries should be allocated to allow for run-time growth.
TA_MAXRTDATA: 0 <= num < 32,761
TA_RANGES values are stored in the string pool. Additional space should be allocated to allow for run-time growth.
TA_MAXSERVERS: 1 <= num< 8K
T_GROUP TA_TMSNAME attribute), then they will be booted along with their server group and should be accounted for in setting TA_MAXSERVERS.
TA_MAXSERVICES: 1 <= num < 32766
TA_MAXACLGROUPS: 1 <= num < 16K
TA_MAXACLGROUPS - 1.
TA_CMTRET: {COMPLETE|LOGGED}
TP_COMMIT_CONTROL characteristic for all client and server processes in a BEA TUXEDO system application. LOGGED initializes the TP_COMMIT_CONTROL characteristic to TP_CMT_LOGGED; otherwise, it is initialized to TP_CMT_COMPLETE. See the description of the BEA TUXEDO system ATMI function tpscmt (3c) for details on the setting of this characteristic.
Limitation: Run-time modifications to this attribute do not affect active clients and servers.
TA_LDBAL: {Y|N}
Y") or off ("N").
TA_NOTIFY: {DIPIN|SIGNAL|IGNORE}
tpinit (3c) 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 via the tpsetunsol (3c) function.
The value DIPIN specifies that dip-in-based notification detection should be used. This means that the system will only detect 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 will not interrupt blocking system calls. DIPIN is the default notification detection method.
The value SIGNAL specifies that signal-based notification detection should be used. This 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 selecting this method of notification.
The value IGNORE specifies that by default, notification messages are to be ignored by application clients. This would be appropriate in applications where only clients that request notification at tpinit (3c) time should receive unsolicited messages.
Limitations: Run-time modifications to this attribute 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 using the SIGNAL method.
TA_SYSTEM_ACCESS: {FASTPATH|PROTECTED}[,NO_OVERRIDE]
FASTPATH specifies that BEA TUXEDO system's internal tables are accessible by BEA TUXEDO system libraries via unprotected shared memory for fast access. PROTECTED specifies that BEA TUXEDO system's internal tables are accessible by BEA TUXEDO system libraries via protected shared memory for safety against corruption by application code. NO_OVERRIDE can be specified to indicate that the mode selected cannot be overridden by an application process using flags available for use with tpinit (3c).
Limitations: Updates to this attribute value in a running application affect only newly started clients and newly configured T_SERVER objects.
TA_OPTIONS: {LAN|MIGRATE|ACCSTATS],*}
LAN - Networked application.
MIGRATE - Allow server group migration.
ACCSTATS - Exact statistics (SHM mode only).
Limitation: Only the ACCSTATS may be set or reset in an active application.
TA_USIGNAL: {SIGUSR1|SIGUSR2}
TA_NOTIFY above).
TA_SECURITY: {NONE|APP_PW|USER_AUTH|ACL|MANDATORY_ACL}
NONE for this attribute indicates that security is/will be turned off. The identifier APP_PW indicates that application password security is to be enforced (clients must provide the application password during initialization). Setting this attribute requires a non-0 length TA_PASSWORD attribute. The identifier USER_AUTH is similar to APP_PW but, in addition, indicates that per-user authentication will be done during client initialization. The identifier ACL is similar to USER_AUTH but, in addition, indicates that access control checks will be 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 identifier MANDATORY_ACL is similar to ACL but permission is denied if an associated ACL is not found for the name.
TA_PASSWORD: string[0 . . . 30]
TA_SECURITY attribute is set to nothing. The system automatically encrypts this information on behalf of the administrator.
TA_AUTHSVC: string[0...15]
TA_SECURITY attribute is set to nothing or to APP_PW.
TA_SCANUNIT: 0 <= num <= 60 (multiple of 5)
TA_BBLQUERY, TA_BLOCKTIME, TA_DBBLWAIT, and TA_SANITYSCAN attributes are multipliers of this value. Passing a value of 0 for this attribute on a SET operation will cause the attribute to be reset to its default.
TA_BBLQUERY: 0 <= num < 32K
TA_SCANUNIT attribute indicating time between DBBL status checks on registered BBLs. The DBBL checks to ensure that all BBLs have reported in within the TA_BBLQUERY 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 attribute on a SET operation will cause the attribute to be reset to its default. This attribute value should be set to at least twice the value set for the TA_SANITYSCAN attribute value (see below).
TA_BLOCKTIME: 0 <= num < 32K
TA_SCANUNIT attribute indicating the minimum amount of time a blocking ATMI call will block before timing out. Passing a value of 0 for this attribute on a SET operation will cause the attribute to be reset to its default.
TA_DBBLWAIT: 0 <= num < 32K
TA_SCANUNIT attribute indicating maximum amount of time a DBBL should wait for replies from its BBLs before timing out. Passing a value of 0 for this attribute on a SET operation will cause the attribute to be reset to its default.
TA_SANITYSCAN: 0 <= num < 32K
TA_SCANUNIT attribute indicating time 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 (MP mode only). Passing a value of 0 for this attribute on a SET operation will cause the attribute to be reset to its default.
TA_CURDRT: 0 <= num < 32K
TA_CURGROUPS: 0 <= num < 32K
TA_CURMACHINES: 0 <= num < 32K
TA_CURQUEUES: 0 <= num < 32K
TA_CURRFT: 0 <= num < 32K
TA_CURRTDATA: 0 <= num < 32K
TA_CURSERVERS: 0 <= num < 32K
TA_CURSERVICES: 0 <= num < 32K
TA_CURSTYPE: 0 <= num < 32K
TA_CURTYPE: 0 <= num < 32K
TA_HWDRT: 0 <= num < 32K
TA_HWGROUPS: 0 <= num < 32K
TA_HWMACHINES: 0 <= num < 32K
TA_HWQUEUES: 0 <= num < 32K
TA_HWRFT: 0 <= num < 32K
TA_HWRTDATA: 0 <= num < 32K
TA_HWSERVERS: 0 <= num < 32K
TA_HWSERVICES: 0 <= num < 32K
Many attributes of this class are tunable only when the application is inactive. Therefore, use of the ATMI interface routines to administer the application is not possible. The function tpadmcall (3c) is being provided as a means of configuring or reconfiguring an unbooted application. This interface may only be used for configuration (SET operations) in an inactive application and only on the site being configured as the master site for the application. Once an initial configuration is created and activated, administration is available through the standard ATMI interfaces as described in MIB(5).