25 Configuring Transactions

This chapter describes how to configure transactions in Oracle WebLogic Server Multitenant (MT). The chapter refers to the Oracle Fusion Middleware and WebLogic Server documentation sets and online help for additional information as appropriate.

This chapter includes the following sections:

Configuring Transactions in a Domain Partition: Overview

WebLogic Server MT supports transaction processing in a multiple partition environment. The scope of the transactions can be either at the domain level or at the partition level. For more information, see "About Scope".

Most of the attributes that define a transaction environment are defined at the global (domain) level. However, the Timeout Seconds for JTA need to be configured at the partition level. For more information, see the Oracle WebLogic Server Administration Console Online Help.

Configuring LLR Data Source, JDBC TLog Data Source, and a Determiner Resource in a Domain Partition: Limitations

A Logging Last Resource (LLR) data source, JDBC TLog data source, or a Determiner Resource cannot be registered in a partition. In this release of WebLogic Server, any attempt to register these resources at the partition level will result in a SystemException.

This restriction is because a WebLogic Server instance cannot start if any of these resources are not available. Therefore, in a multitenant environment, an inaccessible resource owned by one partition prevents the startup of a server that is shared by other partitions. If a server is allowed to start despite the inaccessibility of a resource (and hence its commit records), the recovery of resources enlisted in transactions that also enlisted those resources may be non-atomic as the lack of a commit record would result in a rollback of those resources.

If you still want to use LLR for the resource commit ordering it inherently provides, use the "first resource commit” functionality provided in the WebLogic Server 12.2.1 release. As this feature entails using a true XA resource rather than the local-transaction based LLR resource, it does not provide the performance benefits that LLR offers and it does not require an LLR table. LLR datasources are pinned to the server they are deployed on but XA datasources are not. Therefore, in the case where multiple servers are enlisted in a transaction, the two-phase commit flow may be slightly different. For more information, see "First Resource Commit Ordering" in Developing JTA Applications for Oracle WebLogic Server.