IBM

12.3.1 Installing the Deployment Manager

To install the Deployment Manager follow the steps provided in 9.3, Deployment Manager high availability. This section covers the various options for how to install the Deployment Manager so that the configuration information is available to each node in the cluster.

Installing IBM WAS ND V6 with an IP failover based cluster software requires that your host name is bound to your IP Alias (Virtual IP Address). When creating the Deployment Manager profile, the host name associated with the virtual IP address is used in the configuration. Whenever the Deployment Manager is accessed, the host name associated with the VIP is used. For example, when specifying the URL for the Administrative Console, use 

http://viphostname:9060/ibm/console/

The benefit of using the host name that is associated with the VIP is that it isolates the client from the specific system that is currently hosting the Deployment Manager. If System A is hosting the Deployment Manager and it fails over to System B, then the clustering software switches the virtual IP address to be associated with System B. However, the DNS name (and thus the URL for the Administrative Console) does not need to change and will continue to work.

Figure 12-1 shows our lab setup, which is as follows: - We have two systems that have access to a Network Attached Storage (NAS) device. The systems utilize iSCSI to attach to the NAS which provides simultaneous and concurrent access to the directories that contain the WebSphere configuration data.

- We configured VCS to have an Active/Passive configuration which means that the Deployment Manager is running only on one of the systems at a time. One system is deemed the primary system and when the Deployment Manager process fails on that system, the secondary system becomes active and all requests of the Deployment Manager occur on the secondary system.

- We installed the WebSphere V6 binaries locally on both systems.

- We created the Deployment Manager profile on the shared file system located on the NAS. This makes the configuration data available to both the primary and secondary system.

Figure 12-1 Lab example showing two systems connected to NAS

Redbooks ibm.com/redbooks

Next