JTC Monitoring (JEUS7)
This chapter describes how to monitor JTC using the JEUS console tool and WebAdmin.
1. Overview
While JTC operates, it is required to manage JTC by checking the JTC local domain and remote domain configurations and the numbers of calls and responses through a domain. For this, the JTC module provides JTC information through the JEUS console tool and WebAdmin.
|
2. Configuration
To manage JTC, relevant configurations are required.
To use the JEUS console tool to use JTC Admin, locate the jwebt-jeus7-webadmin-plugin.jar file deployed in the lib/system directory under the JEUS installation directory.
For more information about how to configure each file and setting, refer to Configuration in Tmax WebT User Guide.
3. JTC Monitoring
This section describes how to monitor JTC using the JEUS console tool and WebAmin.
3.1. Using the JEUS Console Tool
JEUS provides the jeusadmin command, which checks the container status. This newly added command shows the most detailed information.
To use the management tool, execute the following in a console. After executing the command, the user is moved to the jeusadmin command prompt screen.
jeusadmin -host addr:portno -u <user name> -p <user passwd>
To view the current status of JTC, run jtcadmin as follows:
jtcadmin [[-f log|ejb|service] | [-d domainName] [-l] [-s Server Name]
The execution results, which depend on the options inputted, are as follows. Configuration items and their values in the result are identical to the items and values set in webt.properties.
-
Execution without an option
Displays all configured JTC information.
-
[-d domainName]
Displays information about the specified remote domain.
DOMAIN INFORMATION [adminServer] [TDOM2] +----------------------------------------------+--------------+ | remote domainName : | TDOM2 | | ip : | 192.168.1.43 | | port : | 5000 | | status : | CONNECTING | | interval : | 20 | | backup domain : | | | not transaction : | false | | buffer size : | 4096 | | timeout : | -1 | | tx timeout : | -1 | | read timeout : | -1 | | min thread : | 1 | | max thread : | 1 | | call count : | 0 | | reply count : | 0 | | prepare count : | 0 | | commit count : | 0 | | rollback count : | 0 | | service list : | | +----------------------------------------------+--------------+
-
[-l]
Displays local domain information, the number of local service calls, and logging information.
LOCAL INFORMATION [adminServer] +-----------------------------------------------------+----------+ | local domain name : | TDOM1 | | log directory : | c:/temp | | log file : | webt.log | | prepare count : | 0 | | commit count : | 0 | | rollback count : | 0 | | remote domain list : | TDOM2 | | cluster domain list : | | +-----------------------------------------------------+----------+ ================================================================== ======================================================== EJB CALL LIST [adminServer] +-----------------------------------------+------------+ | SERVICE NAME | CALL COUNT | +-----------------------------------------+------------+ (No data available) ========================================================
-
[-f log | ejb | service]
Allows dynamic changes to the jtc.properties file while JEUS and JTC are running.
Item Description log
Modifies logging information.
The following settings are available for dynamic update:
-
log.level
-
log.dir
-
log.bufsize
-
log.file.date.format
-
log.valid.days
ejb
Modifies information about EJBs and Beans to run in JEUS.
The following settings are available for dynamic update:
-
tux.ejbs.service.list
-
tux.ejbs.ServiceName.export
-
tux.ejbs.ServiceName.method
-
tux.beans.service.list= ServiceName
-
tux.beans.ServiceName.class = ClassName
service
Modifies information about services to call from Tuxedo.
The following settings are available for dynamic update:
-
tux.domainName.svc
-
tux.clusterName.svc = string
-
tux.default.remote
-
The following example modifies logging information:
[DAS]jeus_domain.adminServer>jtcadmin -f log ==================================================================== adminServer +----------------------------------------------------------+-------+ | success to reconfig | log | +----------------------------------------------------------+-------+ ====================================================================
-
The following example modifies information about EJBs and Beans.
[DAS]jeus_domain.adminServer>jtcadmin -f ejb ==================================================================== adminServer +----------------------------------------------------------+-------+ | success to reconfig | ejb | +----------------------------------------------------------+-------+ ====================================================================
-
The following example modifies information about services to call by Tuxedo.
[DAS]jeus_domain.adminServer>jtcadmin -f service ================================================================== adminServer +------------------------------------------------------+---------+ | success to reconfig | service | +------------------------------------------------------+---------+ ==================================================================
-
How to apply changes
-
Modify the configuration file.
-
Run the jtcadmin command in jeusadmin to complete the reconfiguration.
The following example applies changes to logging configuration.
jtcadmin -f log
-
-
3.2. Using JEUS WebAdmin
JEUS provides WebAdmin, a web browser based management tool, to check the container status. To access WebAdmin, start JEUS and then enter the following address in a web browser.
http://<ip address>:9736/webadmin
The following screen is displayed after logging in. The WebT, JTmax, and JTC monitoring menus are found in [JEUS Monitoring] under the JEUS Node Tree of the left navigation window.
|
In JEUS WebAdmin, select [JEUS Monitoring] > [JTC Monitoring] under the JEUS Node Tree to display the following JTC Monitoring screen.
The JTC Monitoring screen displays information about monitoring, logging, and connection groups. The items displayed and their values are identical to the items and values set in webt.properties.
The following describes each item displayed in the screen.
| Item | Description |
|---|---|
local domain name |
Configured local domain. |
log directory name |
Directory in which log files are stored. |
log file name |
Log file name. |
prepare count |
Number of xa_prepare operations handled. |
commit count |
Number of xa_commit operations handled. |
rollback count |
Number of xa_rollback operations handled. |
ejb call count |
Number of configured EJB calls. |
remote domain list |
List of remote domains. See the table below for information about each item displayed. |
cluster info list |
List of domains clustered. |
Domain Name |
Remote domain name. |
IP |
IP address of the remote domain. |
PORT |
Port of the remote domain. |
STATUS |
Current status of the remote domain.
|
Each item displays configured information. The fields 'callcount', 'replycount', 'preparecount', 'commitcount', and 'rollbackcount' each indicate the total number of calls, replies, prepares, commits, and rollbacks handled.