For a server configuration where there are no distributed transactions,
move the transaction logs to any server that has access to the same resource
managers. For a single server or network-deployed server configuration
where it is known there are no distributed transactions present in the logs,
the transaction logs can be moved to any server (on any node) that has access
to the same resource managers as the original server. For example, the server
needs communication and valid security access to databases or message queues.If the server is in a different cell from the original server, you need to
ensure that there is a JAAS alias available to the server that was used by
the original server for accessing XA resources. In this case you should use
wsadmin to construct the aliases, because if you use the administrative console
to create the alias, then the node name gets prefixed to the alias.
All
the transaction log files for the original server need to be moved to a directory
accessible by the new server. This can be accomplished by either renaming
the transaction log directory or copying all the contents to the new server's
transaction log directory before starting the new server.
Note: To
complete transaction recovery, the application server uses the resource manager
configuration information in the transaction logs. However, for the application
server to continue to do new work with the same resource managers, the server
must have an appropriate resource manager configuration (as for the original
server).