During the Tuxedo development process, it is difficult to find an article about monitoring. The following is translated from http://e-docs.bea.com/tuxedo/tux71/html/admon15.htm, I hope someone will continue to complete these documents. Use MIB to monitor your application basically you can use MIB to complete two operations: get information from MIB (GET Actions) and update information in MIB (SET operation), you can always pass a set of ATMI functions (for example: tpalloc, TpRealloc, TpCall, TPACALL, TPGETRPLY, TPENQUE, TPDEQUEUE are completed. When you query from the MIB via GET, MIB responds to your criticism information and indicates how much object satisfies your request. MIB returns a handle (ie, the cursor), and you can get the remaining objects through this handle. The operation of the next result set is called getNext. A third operation occurs when the query spans multiple buffers. Limit MIB Query When you query MIB's virtual database, you are selecting a recordset from the database table. You can control the size of the database table by two ways: control the number of objects in the query results, or control the amount of information for each object. By key fields and filters, the range of data that meets the requirements can be restricted. The more strict conditions you specified, the fewer the application of the request, the faster the data is returned. Query the overall and local data MIB data saved in several different places. Some data in distributed applications are copied to not only one machine. Other data is not copied, but stored on a local specific machine like nature or objects. What is the global data? Global data is the information copied to each machine to the application component (or server) on each machine. Most of the information of the server, such as configuring status information, all of which are globally replicated in applications, especially in bulletins. BEA Tuxedo's application can be from every place. For example, from each machine called "customer order", the administrator can find 1 group of B6 services on the CustOrda machine, in the activation state. What is local data? Other information like a service and is copied globally, but is limited to an entity. An example of the local attribute TA_TOTREQC defines the number of times the service executed in a particular Server. This statistic is saved on the slave machine with Server. When the Sverver accepts and handles a service request, the counter grows. Because this information is managed locally, copy the performance of the constraint system. There are also some exclusive local data like the client. When a client online, the BEA Tuxedo system creates an instance on the bulletin board, and records all tracking information of the client in the instance. The MIB can confirm the status of the client by checking the entity. Accessing the information through TmadMCall to the BEA Tuxedo system provides direct access to the MIB programming interface (even if your app is not running). This interface, TPADMCALL function, provides data on directly over MIB like applications. TPADMCALL allows you to access information subsets for those processed locally. When the system is not in a run state, you need to query the system or use TPADMCALL when making management changes, and it queries the TuxConfig file that represents your request. Submit and receive data buffers (including queries and replies) are precise.
