|
|
The CORBA Interface MIB defines the Common Object Request Broker Architecture (CORBA) interface groups and objects specific to BEA Tuxedo 8.0 or later applications. The CORBA Interface MIB consists of the following groups:
In addition to the objects in these groups, the Core MIB contains the following CORBA interface specific objects:
For more information on these objects, see Core MIB.
The tuxFactoryTable group contains objects that represent occurrences of factories registered with the FactoryFinder.
This object is the running number used as the index to instances in this table.
The registered ID for the factory.
The fully qualified interface name used as the interface repository ID for the factory. The format of this name depends on the options specified in the Interface Definition Language (IDL) that generates the interface implementation. For details, consult the CORBA 2.1 specification, section 7.6.
A GET operation retrieves run-time information for the selected tuxFactoryTable instance or instances. The returned value is 1 (active) if the instance is registered with the FactoryFinder.
The tuxInterfaceTable group contains objects that represent configuration and run-time characteristics of CORBA interfaces at both the domain and server group levels. There are certain semantic differences in the objects of this group between domain level and server group level instances, as explained in the following discussions for tuxInterfaceTable.
A domain level tuxInterfaceTable instance is not associated with a Server group. In this case, its tuxIfSrvGrp object has the invalid value *.
A server group level instance has an associated Server group. In this case, its tuxIfSrvGrp object has a valid server group name for the domain. This server group level representation of an interface also provides a container for managing the interface state (the tuxIfState object) and for collecting accumulated statistics.
Every CORBA interface that is activated in a server must have a server group level tuxInterfaceTable instance. The activation of interfaces in a server is controlled by the state of a tuxIfQueue instance for the interface. Activation of a tuxIfQueue instance causes its objects to be initialized with values specified for the associated server group level tuxInterfaceTable instance. If such an instance does not already exist, then one is dynamically created. This dynamically created server group level tuxInterfaceTable instance is initialized with the objects of the domain level tuxInterfaceTable instance for the interface, if one exists. If an associated domain level instance does not exist, system-specified default configuration values are used. After they are activated, interfaces are always associated with a server group level tuxInterfaceTable instance.
The specification of configuration objects for interfaces at any level is optional. Interfaces offered by a server are identified through the ICF file used for generating skeletons. The interfaces are advertised automatically by the system when the server is activated.
The following table lists the objects within the tuxInterfaceTable.
This object value is the running number used as an index to instances in this table.
The fully qualified interface name used as the interface ID. The format of this name is one of the options specified in the IDL that generates the interface implementation. For details, consult the CORBA 2.1 specification, Section 7.6.
The server group name. Server group names cannot contain an asterisk, comma, or colon. An asterisk (*) specified as a value for this object specifies a domain level instance.
| Note: | This object can be SET only during creation of a new row. |
INTEGER { active(1), inactive(2), suspended(3), partitioned(4), invalid(5), reactivate(6) }
The semantics for GET and SET requests differ between server group and domain level instances as noted in the following list.
GET:{active(1)|inactive(2)|suspended(3)|partitioned(4)}
GET request retrieves configuration information for the selected tuxInterfaceTable instance or instances. The only states that can be returned are: active, inactive, suspended, partitioned.
active(1)
tuxInterfaceTable instance is defined and at least one corresponding tuxIfQueueTable instance is in the active state. For a server group level tuxInterfaceTable instance, corresponding tuxIfQueueTable instances are those with matching tuxIfName and tuxIfSrvGrp objects. For a domain level tuxInterfaceTable instance, corresponding tuxIfQueueTable instances are those with matching tuxIfName value regardless of their tuxIfSrvGrp value.
inactive(2)
tuxInterfaceTable instance is defined and there are no corresponding tuxIfQueueTable instances in any active state.
suspended(3)
tuxInterfaceTable instance is defined and among all corresponding tuxIfQueueTable instances, there are none in the active state and at least one in the suspended state.
partitioned(4)
tuxInterfaceTable instance is defined and among all the corresponding tuxIfQueueTable instances, there are none in the active state, none in the suspended state, and at least one in the partitioned state.
SET: {invalid(5)|active(1)|inactive(2)|reactivate(6)|suspended(3)}
SET request updates run-time and configuration information for the selected tuxInterfaceTable instance. Modifications can affect more than one server group when domain level changes are made, and run-time modifications can affect more than one server if multiple servers are currently offering an interface. Only the following values can be used in a SET request: invalid, active, reactivate, or suspended.
invalid(5)
tuxInterfaceTable instance for the application. This state change is allowed only when the instance is in the inactive state.
active(1)
tuxInterfaceTable instance for the application. Setting this state on a domain level instance has the effect of activating all corresponding tuxIfQueueTable instances that are currently suspended throughout the domain. Setting this state on a server group level instance affects only servers within the group offering the interface. This state change is allowed only when the instance is in the suspended state. A successful return leaves the object in the active(1) state.
reactivate(6)
tuxInterfaceTable instance. Setting this state on a domain level instance has the effect of activating all corresponding tuxIfQueueTable instances that are currently suspended throughout the domain. Setting this state on a server group level instance affects only servers within the group offering the interface. This state change is allowed only when the instance is in the active(1) or suspended(3) state. Successful return leaves the instance in the active(1) state. Setting this state permits global activation of tuxIfQueueTable instances suspended at the server group level without having to individually activate each server group level tuxInterfaceTable instance.
suspended(3)
tuxInterfaceTable instance. Setting this state on the domain level object has the effect of suspending all corresponding tuxIfQueueTable instances that are currently active throughout the domain. Setting this state on a server group level instance affects only servers within the group offering the interface. This state change is permitted only in the active(1) state. Successful return leaves the object in the suspended(3) state.
| Note: | Dynamic advertisement of interfaces (that is, state change from inactive(2) or invalid(5) to active(1)) is not supported, nor is removal of advertisement (that is, state change from active(1) to inactive(2)). |
Signifies whether a transaction is automatically started for invocations made outside a transaction context.
This object has the following limitations:
tuxInterfaceTable instances.tuxIfTxPolicy object can override the value specified for this object in the UBBCONFIG file. If tuxIfTxPolicy is always(1), a tuxIfAutoTran value of no(2) has no effect at run-time. Behavior is as though the setting were yes(1). If tuxIfTxPolicy is never(2), an tuxIfAutoTran value of yes(1) has no effect. The interface is never involved in a transaction. If tuxIfTxPolicy is ignore(4), an tuxIfAutoTran value of yes(1) has no effect. The interface is never involved in a transaction.
This object imposes the indicated load on the system. Interface loads are used for load-balancing. That is, queues with higher enqueued workloads are less likely to be chosen for a new request.
| Note: | Run-time updates to this object for domain level instances do not affect corresponding server group level instances for the same interface. |
Dequeueing priority. If multiple interface requests are waiting on a queue for servicing, the higher priority requests are handled first.
| Note: | Run-time updates to this object for domain level instances do not affect corresponding server group level instances for the same interface. |
The time limit (in seconds) for processing individual method invocations for this interface. Servers that process method invocations for this interface are terminated abortively if they exceed the specified time limit in processing the request. A value of 0 for this object indicates that the server should not be terminated abortively.
| Note: | Run-time updates to this object for domain level instances do not affect corresponding server group level instances for the same interface. |
Transaction timeout value in seconds for transactions automatically started for this tuxInterfaceTable instance. Transactions are started automatically when a request not in transaction mode is received and the tuxIfAutoTran object value for the interface is yes(1).
| Note: | Run-time updates to this object for domain level instances do not affect corresponding server group level instances for the same interface. |
The factory-based routing criteria associated with this interface.
| Note: | This object can be set only for a domain level tuxInterfaceTable instance, that is, only if tuxIfSrvGrp is *. |
Current logical machine with which the active equivalent server group level tuxInterfaceTable instance, is associated. This object value is NULL for domain level instances.
The number of corresponding servers that offer this interface.
INTEGER { method(1), transaction(2), process(3) }
The TP framework deactivation policy. This object value reflects the policy registered with the framework at server startup. The first server to register with the interface sets the value in tuxInterfaceTable. This value cannot be changed.
INTEGER { always(1), never(2), optional(3), ignore(4) }
The transaction policy for the interface. This object value affects the tuxIfAutoTran object. This policy is set by the application developer and is registered when the server starts.
The tuxLclInterfaceTable group returns values for the local host on which BEA SNMP Agent is running. The following table lists the columnar objects that comprise each row (instance) in the group.
This object value is the running number, which is used as an index into the table.
The fully qualified interface name used as the interface repository ID for the interface. The format of this name depends on the options specified in the IDL that generates the interface implementation. For details, see the CORBA 2.1 Specification Section 7.6 [CORBA].
The server group name. Server group names cannot contain an asterisk, comma, or colon. A value of * for this object indicates a domain level interface.
The number of method invocations completed for the corresponding tuxIfQueueTable instances since they were initially offered. The values returned are for the indicated interface on the local host where BEA SNMP Agent is running.
| Note: | This object value is returned only when tuxTdomainLoadBalance is yes(1). |
The number of requests currently enqueued for this interface. The values returned are for the indicated interface on the local host where BEA SNMP Agent is running.
| Note: | This object value is returned only when tuxTdomainLoadBalance is yes(1). |
The tuxIfQueueTable group contains objects that represent the run-time characteristics of an interface for a particular server queue. The objects provide access to the inherited configuration characteristics of an interface as well as statistics relating to the interface on the queue. This group gives administrators finer granularity in suspending and activating interfaces. This group provides the link between the interface name and the server processes capable of processing method invocations on the interface. For example, tuxIfQRqAddr can be used to identify the corresponding server in the tuxTsrvrTbl and tuxTsrvrTblExt groups.
The running number used as an index into this table.
The fully qualified interface name used as the interface repository ID for the interface. The format of this name is dependent on the options specified in the IDL that generates the interface implementation. See the CORBA 2.1 specification Section 7.6 for details.
The server group name. Server group names cannot contain an asterisk, comma, or colon.
The symbolic address of the request queue for an active server offering this interface. See tuxTsrvrRqAddr for more information about this object.
INTEGER { active(1), suspended(2), partitioned(3), unknown(4) }
The values for GET and SET operations are as follows:
GET:{active(1)|suspended(2)|partitioned(3)}
GET request retrieves configuration information for the selected tuxIfQueueTable instances. The meaning of the possible return values are as follows:
active(1)
suspended(2)
partitioned(3)
SET:{active(1)|suspended(2)}
active(1)
tuxIfQueueTable instance. This state change is allowed only in the suspended(2) state. A successful return leaves instances in the active(1) state.
suspended(2)
tuxIfQueueTable instance. This state change is allowed only in the active(1) state. A successful return leaves the object in the suspended(2) state.
| Note: | Dynamic advertisement of interfaces (that is, a state change from inactive or invalid to active) is not supported, nor is unadvertisement (that is, a state change from active to inactive). |
Signifies whether a transaction is automatically started for invocations made outside a transaction context.
This object has the following limitations:
tuxInterfaceTable instances.tuxIfTxPolicy object can override the value specified for this object in the UBBCONFIG file. If tuxIfTxPolicy is always(1), an tuxIfQueueAutoTran value of no(2) has no effect at run-time. Behavior is as though the setting were yes(1). If tuxIfTxPolicy is never(2), an tuxIfQueueAutoTran value of yes(1) has no effect. The interface is never involved in a transaction. If tuxIfTxPolicy is ignore(4), an tuxIfQueueAutoTran value of yes(1) has no effect. The interface is never involved in a transaction.
Load imposed on the system by this instance. Interface loads are used for load-balancing. Queues with higher enqueued workloads are less likely to be chosen for a new request.
Dequeueing priority. If multiple interface requests are waiting on a queue for servicing, the higher priority requests are handled first.
The time limit (in seconds) for processing individual method invocations for this interface. Servers processing method invocations for this interface are abortively terminated if they exceed the specified time limit in processing the request. A value of 0 for this object indicates that the server should not be abortively terminated.
The transaction timeout value in seconds for transactions automatically started for this instance. Transactions are started automatically when a request not in transaction mode is received and the tuxIfAutoTran object value for the interface is yes(1).
The factory-based routing criterion associated with this interface.
The current logical machine on which this queue is offering this interface.
The number of corresponding servers that offer this interface on this queue.
INTEGER { method(1), transaction(2), process(3) }
The TP framework deactivation policy. This value reflects the policy registered with the framework at the server startup. The first server to register the interface sets the value. This value cannot be changed.
INTEGER { always(1), never(2), optional(3), ignore(4)}
The transaction policy for the interface. This object value affects the effect of the tuxIfQueueAutoTran object; see tuxIfQueueAutoTran for further explanation. This object value is always read-only, and is set by the developer when the server is built and registered at server startup.
The tuxLclIfQueueTable group contains objects that represent the local characteristics of the tuxIfQueueTable. The object values are specific to the host on which BEA SNMP Agent is running.
The running number used as an index into this table.
The fully qualified interface name used as the interface repository ID for this interface. The format of this name is dependent on the options specified in the IDL that generates the interface implementation. For details, see the CORBA 2.1 specification Section 7.6.
The server group name. Server group names cannot contain an asterisk, comma, or colon.
The symbolic address of the request queue for an active server that offers this interface. See tuxTsrvrRqAddr for more information about this object.
The number of interface method invocations completed since the interface was initially offered.
| Note: | This object value is returned only when tuxTdomainLoadBalance is equal to yes(1). |
The number of requests currently enqueued for this interface.
| Note: | This object value is returned only when tuxTdomainLoadBalance is equal to yes(1). |
The number of active objects for this interface for the associated queue. This number represents the number of entries in the active object table for this queue on the associated machine. This number includes objects that are not in memory but were invoked within an active transaction.
The number of active global transactions associated with this interface for its associated queue.
|