Manual peer recovery processing is not the default setting; you must enable it through configuration. Administrator intervention is then required to trigger any peer recovery processing.
Why and when to perform this task
Perform this task if you want to use manual peer recovery for the transaction service. A scenario where you might want to use manual peer recovery is when your file system does not provide the required level of file locking support, and no constraints are in place to ensure that overloading or network partitioning does not occur. For more information see How to choose between automated and manual transaction peer recovery.
After you have configured manual peer recovery, your intervention is required only when a server fails and cannot be restarted; in this case, use the administrative console to specify which peer server should perform recovery processing for the failed server.
Manual peer recovery configuration is provided by a group of policies known as static policies, where one policy definition is provided per application server. Individual definitions are required to define server-specific configuration within the policy which, in this case, is the identity of the server that will initiate a peer recovery process.
Steps for this task
Related tasks
Managing manual peer recovery of the transaction service
Configuring transaction properties for peer recovery