Glossary

A complete unit of work. A single transaction includes multiple tasks.

All or nothing. All work in a transaction is performed, or nothing is performed.

The successful result of a transaction is updated to shared resources. If the transaction fails, shared resources are kept in their original states.

Changes in shared resources affected by a transaction do not affect other transactions until the transaction is committed.

The result of a transaction is always maintained after it is committed.

Multiple RMs (Resource Managers) handle a single transaction.

One or more RMs are treated as a single unit of work. Any work generated by the system must be automatically committed.

As part of handling transactions, makes tentative changes permanent.

An operation that recovers the result of a transaction to a previous state due to a transaction failure or a user request.

Transaction management middleware, which monitors transactions and maintains their consistency.

The process of changing a centralized mainframe environment to an open distributed system environment.

The system software that provides a single user environment in a distributed computing environment. It connects a network of heterogeneous systems, supports communication between clients and servers, and connects between computers.

A service that handles transactions in the web and provides the mutual communication (J2EE) feature between heterogeneous systems.

A service that handles messages by putting them into a queue and provides an asynchronous message management feature.

A service that enables multiple database servers to be used with a single consistent method in a distributed environment.

A service that synchronously runs a program located in another computer through a network.

A service that provides the feature that enables a client object to call a method of a remote server using a software bus called ORB.

A core process that operates and manages the Tmax system. It manages all shared information of the Tmax system and the following server processes: CLL (Client Listener), CLH (Client Handler), TMS (Transaction Management Server), and AP (Application Program).

A process for connections between clients and Tmax. CLL receives requests from clients by setting the PORT Listener to manage client connections.

A process that relays between clients and servers, requests a service from a server that handles businesses, connects to a server, and manages the connection.

A process that changes databases and handles transactions while operating in a database-related system. It delivers commit/rollback requests from XA services to RM (Resource Manager).

Saves transaction logs in tlog before CLH executes commit when a transaction occurs.

As a process that manages the disk queue of the Tmax system, it reads/writes from/to a file.

Handles inter-domain communication when multiple domains exist.

Monitors Tmax-related information and manages changes in the configuration file.

Remotely controls all domains in which Tmax is installed.

A server process that handles business logic passively at the request of CLH and returns the results.

A server process that actively handles business logic without a caller request and returns the results. It is a unique feature of Tmax.

Checks system environment information and statistics information, and operates and manages the system.

Core information required to operate the Tmax system. It is created by the TMM service and located in the shared memory managed by Tmax.

A method that uses the socket API without any changes and uses a file to enable communication between processes.

A method that distributes loads by using a defined load ratio.

A method that distributes loads with data values. If multiple nodes provide the same service, routing is possible for the nodes within the data range.

A method that dynamically selects a handling group according to the load ratio. If loads are concentrated at a certain node, Tmax distributes the loads with this method, which dynamically adjusts the loads for each node.

A server process that starts and handles business logic only when there is a client request.

An agent that supports multiple ports that efficiently handle processes with the multi-threading method.

An agent that supports multiple ports that can handle both non-Tmax clients and Tmax clients.

A two step protocol used to guarantee transaction properties for global transactions related to more than one homogeneous or heterogeneous database. The first step is the prepare phase. The second step is the commit phase.

Enables data to be maintained and reliably handled by preventing a request from disappearing due to a failure.

A Tmax feature that is the communication medium for loosely coupled senders and receivers. It supports the Queue and Topic methods.

A program that supports the transaction service for Tmax and Java application programs.

A buffer used to save a string that ends with NULL. The length of the buffer does not need to be specified.

A buffer used to save binary type data that has a specified number of bytes. The length of a buffer must be specified to exchange data.

A buffer used to save a C language struct.

A buffer used to save a C language struct. Only the char, int, and long types can be used as members of the struct.

A buffer used to save field key and data value pairs. All primitive data types can be saved in this buffer.