|
•
|
WS_MIB—used to manage Workstation groups and processes associated with them
|
|
•
|
ACL_MIB—used to administer access control lists (ACLs)
|
|
•
|
APPQ_MIB—used to administer application stable-storage queues
|
|
•
|
EVENT_MIB—used to control event notification and the subscription request database
|
|
•
|
DM_MIB—used to administer an Oracle Tuxedo Domains (multiple-domain) configuration
|
The MIB reference pages (TM_MIB(5), generic reference page
MIB(5), ...) are defined in
BEA Tuxedo File Formats, Data Descriptions, MIBs, and System Processes Reference.
|
•
|
Command-line utilities—a set of commands used to activate, deactivate, configure, and manage an Oracle Tuxedo application.
|
|
•
|
EventBroker—a Oracle Tuxedo component that provides asynchronous routing of application events among the client and server processes running in an Oracle Tuxedo application, and distributes system events—typically faults or exceptional happenings—to whichever application processes want to receive them.
|
|
•
|
TUXCONFIG file—binary version of an Oracle Tuxedo application’s configuration ( UBBCONFIG) file. Every server machine in an Oracle Tuxedo application stores a copy of the TUXCONFIG file. The MIB updates the TUXCONFIG file and reads information from the TUXCONFIG file.
|
|
•
|
Bulletin board—a memory segment in which all the configuration and dynamic processing information for an Oracle Tuxedo application is held at run time. Every server machine in an Oracle Tuxedo application has a bulletin board. The MIB updates the bulletin board and reads information from the bulletin board.
|
|
•
|
TLOG—a transaction log file in which records of committed global transactions are stored. Every server machine in an Oracle Tuxedo application should have a TLOG. The MIB gathers information from the TLOG.
|
|
•
|
tmloadcf(1)—a command, run on the master machine, that allows you to compile your application’s UBBCONFIG file into the binary TUXCONFIG file. The tmloadcf command loads the binary file to the location defined by the TUXCONFIG environment variable.
|
|
•
|
tmunloadcf(1)—a command, run on the master machine, that allows you to translate the binary TUXCONFIG file back to a text version, so that the UBBCONFIG and TUXCONFIG files can be synchronized. The tmunloadcf command prints the text version to standard output.
|
|
•
|
tpusradd(1), tpusrdel(1), tpusrmod(1)—a set of commands that allow you to create and manage a user database for authorization purposes.
|
|
•
|
tpgrpadd(1), tpgrpdel(1), tpgrpmod(1)—a set of commands that allow you to create and manage user groups by using access control lists to authorize access to services, queues, and events.
|
|
•
|
tpacladd(1), tpaclcvt(1), tpacldel(1), and tpaclmod(1)—a set of commands that allow you to create or manage access control lists for applications. These commands enable the use of security-related authorization features.
|
|
•
|
tmboot(1)—a command, run on the master machine, that allows you to centrally start up your application servers. The tmboot command reads the TUXCONFIG environment variable to locate your application’s TUXCONFIG file. The tmboot command loads TUXCONFIG into shared memory to establish the bulletin board, propagating the changes to the remote server machines in a multiple-machine domain.
|
|
•
|
tmadmin(1)—an interactive meta-command, typically run on the master machine, that enables you to run subcommands to configure, monitor, and tune your application. You can use the tmadmin command before your application is booted (in configuration mode) or when your application is running .
|
|
•
|
tmconfig(1)—another interactive meta-command, typically run on the master machine, that enables you to run subcommands to configure, monitor, and tune your application. You can use the tmconfig command only when your application is running . The tmconfig command is more powerful but less user friendly than the tmadmin command.
|
|
•
|
tmshutdown(1)—a command, run on the master machine, that allows you to centrally shut down your application servers. The tmshutdown command reads the TUXCONFIG environment variable to locate your application’s TUXCONFIG file.
|
You use the command-line utility qmadmin(1) to perform all administration functions for the application queues in your application. Like the
tmadmin and
tmconfig commands,
qmadmin is an interactive meta-command that enables you to run many subcommands.
|
Note:
|
The DMADM server may run on any machine ( master machine, non-master machine) in an Oracle Tuxedo domain.
|
|
•
|
dmloadcf(1)—a command, run on the same machine as the DMADM server, that allows you to compile an application’s DMCONFIG file into the binary BDMCONFIG file. The dmloadcf command loads the binary file to the location defined by the BDMCONFIG environment variable.
|
|
•
|
dmunloadcf(1)—a command, run on the same machine as the DMADM server, that allows you to translate the binary BDMCONFIG file back to a text version, so that the DMCONFIG and BDMCONFIG files can be synchronized. The dmunloadcf command prints the text version to standard output.
|
|
•
|
dmadmin(1)—an interactive meta-command, typically run on the same machine as the DMADM server, that enables you to run subcommands to configure, monitor, and tune domain gateway groups. You can use the dmadmin command before your application is booted (in configuration mode) or when your application is running .
|
|
•
|
DMADM(5), DMCONFIG(5), GWADM(5), GWTDOMAIN(5), and UBBCONFIG(5)in BEA Tuxedo File Formats, Data Descriptions, MIBs, and System Processes Reference
|
The Oracle Tuxedo MIB is used to administer an Oracle Tuxedo application. It defines the parts of an application that are required in every Oracle Tuxedo domain. MIB defines an Oracle Tuxedo application as a set of classes (for example, servers, groups, machines, domains), each of which is made up of objects that are characterized by various attributes (for example, identity and state).
Classes are the types of entities such as servers and machines that make up a Oracle Tuxedo application.
Attributes are characteristics of the objects in a class: identity, state, configuration parameters, run-time statistics, and so on. There are a number of attributes that are common to MIB operations and replies and common to individual classes. Every class has a
state attribute that indicates the state of the object.
|
•
|
tppost(3c), tpsubscribe(3c), and tpunsubscribe(3c)in BEA Tuxedo ATMI C Function Reference
|
|
•
|
EVENTS(5), EVENT_MIB(5), TMSYSEVT(5), TMUSREVT(5), and UBBCONFIG(5) in BEA Tuxedo File Formats, Data Descriptions, MIBs, and System Processes Reference
|
