Introduction

TMM, the Tmax Manager, manages the overall operations of Tmax. It manages system operation information and CLL, CLH, TMS, and RQS processes as well as various Tmax application processes. TMM is the first component to load when Tmax starts up, and the last to be terminated when Tmax shuts down.

If a Tmax system contains multiple nodes, the TMM on each node maintains session connections with the others to monitor their heartbeats and provide fault tolerance for the server group. TMM is also responsible for logging each process and updating all shared data. TMM ensures normal system operation when a problem occurs that disrupts logging, such as lacking disk space, by temporarily suspending logging until the problem is resolved.

CLL, the Client Listener, forms an initial link between a client and Tmax system. The initial client-Tmax connection is handled by the CLL. When a client issues a service request, all service processing is done through an internal connection with CLH.

CLH, the Client Handler aka the client manager, serves as a mediator between client and server processes. CLH controls data flow by connecting to application server process, gateway, RQ process, and Tmax process. When a service is requested by a client, the CLH forwards the request to the appropriate application server process. Once it receives the results from the application server process, it returns them to the client.

TMS, Transaction Management Server, is responsible for managing database and distributed transactions. While TMM, CLL, and CLH are critical processes that always gets loaded into memory, the TMS is only responsible for database management and distributed transaction processing. It is implemented by using the database libraries.

The RQS, Reliable Queue Server, manages Tmax disk queues. Generally, all data stored within a system is at some level of risk, and the data stored in memory waiting to be processed can be lost in the event of a system failure. The RQS resolves this problem by storing data on the disk before and after service requests to preserve the stored data and resume services when the system is restarted.

The RQS is only loaded when it is specified in the configuration file since an active RQS process can negatively impact the service processing performance.

In a Tmax system that consists of multiple domains, the GW (Gateway) handles inter-domain communications. By using communication methods such as TCP/IP, SNA/LU0, SNA/LU6, and X.25, GW can facilitate communication and integration not only between different Tmax domains, but also between Tmax system and various other systems.

Gateways are only loaded when they are specified in the configuration file. The actual name of a process may vary depending on the setting in the configuration file, and some gateways may require settings to be added to or modified in the configuration file. GW is an optional process that runs only when it is specified in the configuration file.

In Tmax systems that require security, the CAS performs level one and level two security checks for user authentication.

TLM, Transaction Log Manager, monitors pending transactions and performs transaction logging, which was previously performed by TMM (earlier than 4.0).

HMS, Hybrid Messaging System, serves as the communication mediator that enables loose coupling between a sender and a receiver. Even though a sender and a receiver do not know each other, the messaging system enables them to communicate with one another with only virtual channel information of the destination. HMS ensures reliability in message transmission in order to allow delayed data processing by providing the ability to distinguish between the time the message is sent and received.

Tmadmin is a management tool that can be used to dynamically check or modify the Tmax configuration file. It can also be used to monitor the behavior of server processes and to check the statuses of application service processes and queues.

Racd is a daemon process that runs on each node (machine) in the system. When a Tmax system is comprised of multiple nodes in a single domain (group of nodes that share a single configuration file), racd can be used to enable the central monitoring and management of the entire system and nodes from a single node through tmadmin. It can also be used to ensure that changes in the configuration file are applied to all nodes of the domain without having to copy the file each time.

Tmboot is used to start up Tmax using the configuration file. It first loads the system processes, including TMM, CLL, and CLH, and then the RQ, TMS, and GW processes for additional environment configuration, and lastly it loads the application server processes. Tmboot can be used with various options to start Tmax.

Tmdown is used to shutdown Tmax using the configuration file. It first terminates application server processes, and then shuts down the Tmax management processes.