---

Server --> Logging --> JTA

Tasks     Related Topics     Attributes

 

Overview

The Server - >Logging - >JTA tab determines the location of the transaction log files and specifies a policy for writing transaction log records to disk.

BEA recommends that you locate transaction log files on a highly available file system, for example, on a RAID device. To take advantage of the migration capability of the Transaction Recovery Service for servers in a cluster, store the transaction log in a location that is available to a server and its backup servers, preferably on a dual-ported SCSI disk or on a Storage Area Network (SAN).

Warning: On Windows, the Direct-Write transaction log file write policy may leave transaction data in the on-disk cache without immediately writing it to disk. This is not transactionally safe because a power failure can cause loss of on-disk cache data. To prevent cache data loss when using the Direct-Write transaction log file write policy on Windows, disable all write caching for the disk (enabled by default) or use a battery backup for the storage system. See Disabling the On-Disk Cache For a Disk Drive on Windows 2000 for instructions

 

Tasks

Setting the Transaction Log File Location (Prefix)

Setting the Transaction Log File Write Policy

 

Related Topics

(May require an Internet connection.)

Transaction Log Files

Introducing Transactions in Programming WebLogic JTA

Configuring and Managing Transactions in Programming WebLogic JTA

 

Attributes

Attribute Label	Description	Value Constraints
Transaction Log File Prefix	The path prefix for the server's JTA transaction log files. If the pathname is not absolute, the path is assumed to be relative to the server's root directory.MBean: weblogic.management. configuration.ServerMBeanAttribute: TransactionLogFilePrefix	Default: "./"
Transaction Log File Write Policy	The policy used for writing transaction log records to disk: Cache-Flush - Flushes operating system and on-disk caches after each entry to the transaction log. Transactions cannot commit until the commit record is written to stable storage. Direct-Write - Forces the operating system to write transaction log entries directly to disk with each write. To be transactionally safe, this option may require additional OS parameter settings. Direct-Write performs as well or better than Cache-Flush, depending on operating system and OS parameter settings, and is available on Windows, HP-UX, and Solaris.	Default: Cache-Flush