Add Deployment Manager to OS daemon service

As a first step in making HA provisions for the Deployment Manager, make use of the platform specific mechanisms for providing operating system process monitoring and restart.

When installing WebSphere Network Deployment on the Windows platform, it is recommended that you select the option of adding the Deployment Manager as a Windows service. If you did not select this option during installation, then you can do so afterwards by using the WASService command (located in the <install_root>\WebSphere\Deployment Manager\bin directory).

For Unix you can add an entry in the inittab file, as an example on AIX, you can do so by adding the following entry in the inittab file:

was:2:once:/usr/WebSphere/DeploymentManager/bin/rc.was >dev/console 2>&1

For Linux, you can use the chkconfig command.

Once you have added the Deployment Manager server as an operating system monitored process, the operating system will restart it automatically when the process terminates abnormally. This will minimize the impact of an outage due to a process failure.

Doing so will not prevent the failure of the Deployment Manager due to any network, disk, operating system, JVM, and host machine failures.

  Prev | Home | Next

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.