You decide to use a database to store WebLogic Server transaction logs for a managed server. Which two steps are required to configure this?

To configure a WebLogic Server managed server to store its transaction logs (TLogs) in a database, you must perform two key steps. First, you need to create a JDBC data source that the transaction manager can use to connect to the database. The official documentation explicitly requires this data source to be of a non-XA type. Second, you must configure the managed server's JTA (Java Transaction API) settings. This is done by navigating to the server's Services > JTA configuration page and changing the transaction log store Type from the default file-based store to JDBC, then selecting the non-XA data source you created.

B: Disabling the default store is the outcome of selecting "JDBC" as the store type; it is not a separate, selectable configuration step in the process. D: The data source used for the JDBC transaction log store must be a non-XA data source. Using an XA data source for this purpose is not supported and will result in server startup failures.

1. Oracle Fusion Middleware

Administering Oracle WebLogic Server 12.2.1.4.0

Part Number E90492-11

Chapter 11 "Configuring Transactions"

Section "Configuring a JDBC TLog Store".

Page/Section Reference: The section explicitly states

"To use a JDBC TLog store

you must first configure a non-XA JDBC data source that the transaction manager will use to connect to the database." This supports option C and refutes option D. The same section provides the console steps: "In the Transaction Log Store section

for Type

select JDBC." This directly supports option A.

2. Oracle Fusion Middleware

Developing JTA Applications for Oracle WebLogic Server 12.2.1.4.0

Part Number E90490-10

Chapter 4 "Transactions in EJB Applications"

Section "Transaction Log Files".

Page/Section Reference: This document reinforces the requirement

stating

"You can also store transaction log files in a database by configuring a JDBC TLog store. To do so

you must first configure a non-XA JDBC data source that the transaction manager will use to connect to the database." This provides further evidence for the correctness of option C and the incorrectness of option D.