11.1.4 Add the new Web server to the cell configuration

Perform the following steps to add the new Web server to your Network Deployment Manager cell configuration:

1.xxxx

Log on to your Network Deployment Manager as non-root_user.

2.xxxx

Change to the WebSphere Application Server installation directory (ND_Install_Dir, the default is /usr/IBM/WebSphere/AppServer on AIX, /opt/IBM/WebSphere/AppServer on Linux).

3.xxxx

Execute the following command on one line:

./wsadmin.sh -profileName DmgrProfileName -f 
configureWebServerDefinition.jacl WebServerName IHS 
'IHS_Install_Dir' 
'WC_Install_Dir/instances/Instance_Name/httpconf/httpd.conf' 80 
MAP_ALL 'WC_Install_Dir/instances/Instance_Name/httpconf/' unmanaged 
WebServerNodeName WebServerHostName WebServerOS

For example, our Web server node 2 (srvb504.torolab.ibm.com, running on AIX) is added as webserver2 by the command shown in Example 11-1.

Example 11-1 Adding a Web server definition to the cell configuration

./wsadmin.sh -profileName Dmgr01 -f configureWebserverDefinition.jacl webserver2 IHS 
'/usr/IBMIHS' 
'/usr/IBM/WebSphere/CommerceServer60/instances/demo/httpconf/httpd.conf' 80 MAP_ALL 
'/usr/IBM/WebSphere/CommerceServer60/instances/demo/httpconf/' unmanaged 
srvb504.torolab.ibm.com srvb504.torolab.ibm.com aix

In the Network Deployment Manager administrative console, you should now see two Web servers when navigating to Servers Æ Web servers, as shown in Figure 11-2.

Figure 11-2 Web servers page

4.xxxx

For the new Web server, verify and change the configuration, and activate remote Web server management as described for the first Web server in Update the Web server configuration and Activate remote Web server management (optional). Do not propagate the plug-in configuration at this point.

5.xxxx

Verify the application mapping by navigating to Applications Æ Enterprise Applications Æ WC_<Instance_Name> > Map modules to servers. The modules of the WebSphere Commerce instance application (WC_demo in our case) should be mapped to all Web servers and to the application server cluster. This is shown for each module in the Server column, as shown in Figure 11-3.

Figure 11-3 Map modules to server panel - Server column

If this is not the case, perform the following steps:

a.xxxx Select the cluster and all Web servers in the Clusters and Servers combo box, as shown in Figure 11-4. Figure 11-4 Selecting the servers for mapping b.xxxx Then click the Select all icon, as shown in Figure 11-5. Figure 11-5 Selecting all application modules c.xxxx Click Apply (Figure 11-4) and verify the mappings in the Server column. 6.xxxx To add virtual host aliases for the new Web server, navigate to Environments Æ Virtual Hosts. 7.xxxx For each WebSphere Commerce virtual host (VH_<Instance_Name>...), click the virtual host name, then click Host Aliases. Add host aliases for the new Web server for each port of the virtual host by clicking New and adding the Web server and port information, as shown in Figure 11-6. Figure 11-6 Adding a host alias to the VH_<Instance_Name> virtual host Click OK and repeat this for each port of the virtual host. Also, add host aliases for the short name of the Web servers. Figure 11-7 shows the complete host alias list for the VH_<Instance_Name> virtual host for our two Web servers (our instance name is demo). Figure 11-7 Complete host alias list for VH_<Instance_Name> Add host aliases for the Web server's short and full qualified host names to all VH_<Instance_Name>... virtual hosts for the relevant ports. For example, for the VH_<Instance_Name>_tools virtual host, add aliases for port 8000. For VH_<Instance_Name>_admin, add aliases for port 8002, and so on. 8.xxxx To save the configuration changes, click Save, as shown in Figure 11-8. Figure 11-8 Saving the configuration - step 1 9.xxxx On the save page, check Synchronize changes with Nodes and click the Save button, as shown in Figure 11-9. Figure 11-9 Virtual Hosts The new Web server configuration is now complete and saved. 10.xxxx Propagate the IBM HTTP Server Plug-in configuration to the new Web server as explained for Web server node 1 in "Propagate IBM HTTP Server Plug-in configuration. 11.xxxx Start (or restart) the new Web server as explained for Web server node 1 in Restart the Web server. The store and administration pages of your WebSphere Commerce application should now be accessible through the new Web server node. Refer to the following sections for instructions on how to configure load balancing for all your Web servers using IBM WebSphere Edge Components Load Balancer. d.xxxx Click OK below the list of application modules. xxxx