WAS v8.5 > Administer applications and their environment > Welcome to administering Transactions > Administer the transaction service > Manage transaction logging for optimum server availabilityRestart an application server on a different host
As part of restarting an application server on a different host, you move all the transaction logs to the new host. Moving transactions logs to a different host is similar to moving logs from one server to another, as described in Moving a transaction log from one server to another.
This involves moving an original application server on one host to an alternative server, which has access to the same resource managers, on another host. For a network-deployed server configuration, the alternative server must have the same name and host IP address as the original server.
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).
To restart an application server on a different host...
- Ensure the alternative application server is stopped.
- Move all the transaction logs for the original server to the alternative application server, as described in Moving a transaction log from one server to another.
- Restart the alternative application server.
Related
Moving a transaction log from one server to another