Restarting an application server on a different host

This topic describes some considerations and actions that you can take with transaction logs to restart an application server on a different host.

Why and when to perform this task

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.

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).

To restart an application server on a different host, complete the following steps:

Steps for this task

  1. Ensure that the alternative application server is stopped.
  2. Move all the transaction logs for the original server to the alternative application server, according to the considerations described in Moving a transaction log from one server to another.
  3. Restart the alternative application server.

Related tasks
Managing transaction logging for optimum server availability



Searchable topic ID:   tjta_mvesrv
Last updated: Jun 21, 2007 8:07:48 PM CDT    WebSphere Business Integration Server Foundation, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/ae/tjta_mvesrv.html

Library | Support | Terms of Use | Feedback