WebSphere Application Server Network Deployment, Version 6.0.x     Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Configuring automated peer recovery for the transaction service

Automated peer recovery processing is the default setting when high availability is enabled, however follow the steps in this topic to ensure that your system is configured correctly. If you have configured manual peer recovery and want to return to automated peer recovery, you must reconfigure the system back to the default settings.

Before you begin

Make sure that you understand the infrastructure requirements for automatic peer recovery. For more information, see How to choose between automated and manual transaction peer recovery and Disabling file locking.

Steps for this task

  1. Ensure that high availability is enabled, and that the location of the transaction recovery log is specified, as described in Configuring transaction properties for peer recovery.
  2. Remove any Static HA policies that you might have previously created by configuring the system for manual peer recovery.
    1. In the administrative console click Servers > Core groups > Core group settings . All the members of a cluster reside in a single core group, which by default is the DefaultCoreGroup. Click the core group that contains your cluster. The Core groups configuration panel is displayed.
    2. Under Additional Properties, click Policies . The current set of policies is displayed.
    3. Select any policies with a Policy type of Static, and a Match criteria that includes type = WAS_TRANSACTIONS. Click Delete.
  3. Check to see if the required One-of-N transaction HA policy already exists. This policy will have a Policy type of One-of-N, and a Match criteria that includes type = WAS_TRANSACTIONS. If this policy already exists, you do not need to take any further action. If the policy does not already exist, create it according to the following sub-steps.
    1. Click New to create a new policy.
    2. Select One of N policy and click Next.
    3. Provide a name for the policy. This value is a free-form text string that is used only as a label in the administrative console, however to assist readability in the administrative console, use a name that associates the policy with the required behavior, for example, Clustered TM policy.
    4. Enter a description if required.
    5. Select the Fail back check box to ensure that a failed server reclaims its recovery log when it restarts, and click OK.
    6. Set values for Is alive timer, Quorum and Preferred servers only, if required. (See the contextual help for more information.)
    7. Under Additional Properties, click Match criteria to open an empty match criteria panel.
    8. Click New to create a new match criterion.
    9. Enter 'type' (without quotation marks) in the Name field and WAS_TRANSACTIONS in the Value field. Click OK.
    10. Save your changes to the master configuration, ensuring that you select the Synchronize changes with Nodes check box.
    11. Stop and restart the cluster members for the changes to take effect.



Sub-topics
Disabling file locking

Related tasks
Configuring transaction properties for peer recovery

Related information
How to choose between automated and manual transaction peer recovery
Core group collection

Task topic    

Terms of Use | Feedback

Last updated: Dec 11, 2005 4:07:15 PM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/tjta_cfgpeer_auto.html

© Copyright IBM Corporation 2002, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)