1. What is the "tranlog"?
The tranlogs are used by the Java™ Transaction Service (JTS).
2. What is stored in the "tranlog"?
Node specific transactions are stored in "tranlog".
3.Where is log file located?
Default values can be found in <was_root>/bin/admin.config
com.ibm.ejs.sm.adminServer.logFile=<was_root>/tranlog/<nodename>_tranlog1
$WAS_HOME/tranlog/<nodename>_tranlog2
If this property is blank, the server will use in-memory logging. In a
production environment, be sure to set a value because transaction
rollback capability requires transaction logging.
4.How does WebSphere Application Server use the "tranlog"?
This information is used to cleanup any unfinished transactions.
WebSphere Application Server will take care of cleaning up any
unfinished transactions in the event that Administrative Server dies.The
information in the tranlog file is then read when WebSphere Application
Server starts back up, it can rollback any processes it had started, but
did not complete in regards to those transactions.
5.What is the impact of "tranlog" in multinode Workload Management
(WLM) environment?
There is no WLM information stored in the "tranlog" (The "State" of the
transaction is not Workload Managed)
These are "Node" specific and not shared across the Nodes. WebSphere
Application Server does not automatically deal with failed
transactions.
During a transaction, if that particular Node goes down then WLM sends
the requestor client back and it is the client's responsibility to handle
the unfinished transaction.
If the server where the client has a transaction affinity goes down, the
client should receive some sort of transaction exception, recover/deal
with the transaction, and try it again.
6.How to configure all releases of WebSphere Application Server V4.0
to act as a "Transaction Coordinator" with MQSeries?
http://www-3.ibm.com/software/webservers/appserv/doc/v40/ae/infocenter/
See the following sections in chapters 4 and 6 as listed:
4.6.3:
Java Message Service (JMS) Overview
4.6.3.1:
Using the JMS point-to-point messaging approach
4.6.3.3:
Support of Java Message Service resources
4.6.3.4:
Support for the use of MQSeries Java Message Service resources
6.6.20:
Administering transactions (overview)
6.6.20.0:
Transaction properties
|