bea.com | products | dev2dev | support | askBEA

Download Docs | Site Map | Glossary
Search

Administration Console Online Help

JTA

On the Domain Configuration JTA tab in the Administration Console, you can configure Java Transaction API (JTA) attributes to suit your environment. The Administration Console provides default values for all JTA configuration attributes.

Configuration settings for JTA are applicable at the domain level. This means that configuration attribute settings apply to all servers within a domain. Monitoring and logging tasks for JTA are performed at the server level.

Once you configure WebLogic JTA and any transaction participants, the system can perform transactions using the JTA API and the WebLogic JTA extensions.

Tasks

Configuring JTA

1. Click the Domain node. A dialog displays in the right pane showing the tabs associated with configuration for the domain.

2. Click the JTA tab.

3. Enter values in the Timeout Seconds, Abandon Timeout Seconds, Before Completion Iteration Limit, Max Transactions, Max Unique Name Statistics, and Checkpoint Interval Seconds attribute fields or accept the default values as assigned. For details about JTA attributes, see Attributes.

4. Enable or disable the Forget Heuristics attribute as desired.

5. Click Apply to save any changes you made.

Migrating the Transaction Recovery Service to a Server in the Same Cluster

To migrate the Transaction Recovery Service from a failed server in a cluster, follow these steps:

1. Make sure the failed or failing server is not running:

   1. Click the Servers node in the left pane in the Administration Console to expand it.

   2. Right-click the failed server and select Start/Stop this server.

   3. In the right pane of the Administration Console, click Shutdown this server. If that action fails, retry these steps and select Force shutdown of this server.

2. In the left pane in the Administration Console, select the failed server from which you want to migrate the Transaction Recovery Service. A dialog displays in the right pane with tabs for configuring the server.

3. Select the Control tab, then select the JTA Migrate tab. The Migrate JTA tab includes the following:

   - Cluster—The name of the cluster to which the server belongs.

   - Current Server—The server that currently owns the Transaction Recovery Service for the selected server. (The selected server name is displayed at the top of the page.)

   - Destination Server—A list of servers in the cluster. This list shows all servers in the cluster or a list of servers that you specify. See Constraining the Servers to Which the Transaction Recovery Service can Migrate.

4. In Destination Server, select the server that you want to recover transactions for the failed server.

5. Click Migrate and follow any additional instructions in the right pane.

Note: The Transaction Recovery Service is designed to gracefully handle transaction recovery after a crash. BEA recommends that you attempt to restart a crashed server and allow the Transaction Recovery Service to handle incomplete transactions, rather than migrate the Transaction Recovery Service to another server.

Constraining the Servers to Which the Transaction Recovery Service can Migrate

You may want to limit the choices of the servers to use as a Transaction Recovery Service backup for a server in a cluster. For example, all servers in your cluster may not have access to the transaction log files for a server. You can limit the list of destination servers available on the Server—>Control—>Migrate JTA tab in the Administration Console by following these instructions:

1. In the Administration Console, click the Servers node in the left pane to expand it.

2. Select the server for which you want to specify Transaction Recovery Service backup servers. A dialog displays in the right pane with tabs for configuring the server.

3. Select the Control tab, then select the JTA Migration Config tab.

4. In the Available list of Constrained Candidate Servers, select the servers you want to use as a Transaction Recovery Service backup and click the right arrow to move the servers to the Chosen list.

Note: You must include the original server in the list of chosen servers so that you can manually migrate the Transaction Recovery Service back to the original server, if need be. The Administration Console enforces this rule.

1. Click Apply to save your changes.

Viewing Current Owner of the Transaction Recovery Service

When you migrate the Transaction Recovery Service to another server in the cluster, the backup server takes ownership of the Transaction Recovery Service until it completes all incomplete transactions. After which, it releases ownership of the Transaction Recovery Service and the original server can reclaim it. You can see the current owner on the Server—>Control—>Migrate JTA tab in the Administration Console. Follow these instructions:

1. In the Administration Console, click the Servers node in the left pane to expand it.

2. Select the server for which you want to see the owner of the Transaction Recovery Service. A dialog displays in the right pane with tabs for configuring the server.

3. Select the Control tab. If necessary, select the Migrate JTA tab. On the Migrate JTA tab, the Current Server indicates the current owner of the Transaction Recovery Service.

Manually Migrating the Transaction Recovery Service Back to the Original Server

After completing transaction recovery for a failed server, a backup server releases ownership of the Transaction Recovery Service so that the original server can reclaim it when the server is restarted. If the backup server stops (crashes) for any reason before it completes transaction recovery, the original server cannot reclaim ownership of the Transaction Recovery Service and will not start. You can manually migrate the Transaction Recovery Service back to the original server by selecting the original server as the Destination Server. The backup server must not be running when you migrate the service back to the original server. Follow the instructions below.

Note: Please note the following:

- A backup server will continue to recover incomplete transactions after you restart it. You will not need to manually migrate the Transaction Recovery Service back to the original server if the backup server completes the transaction recovery.

- If you restart the original server while the backup server is recovering transactions, the backup server will gracefully release ownership of the Transaction Recovery Service. You do not need to stop the backup server. See Recovering Transactions for a Failed Clustered Server in the WebLogic Server Administration Guide.

1. Make sure the backup server is not running. To do this, click the Servers node in the left pane in the Administration Console to expand it, then right-click the backup server and select Stop this server. Follow any additional instructions.

2. In the Administration Console, click the Servers node in the left pane to expand it.

3. Select the failed server that you want to migrate the Transaction Recovery Service back to. A dialog displays in the right pane with tabs for configuring the server.

4. Select the Control tab. If necessary, select the Migrate JTA tab.

5. In Destination Server, select the original server.

6. Click Migrate and follow any additional instructions in the right pane.