S1: Adding subsequent node to the cluster  |
|
|
You need to install Lotus Connections only once, on the first node of the cluster. Subsequent nodes/servers are configured by installing WebSphere Application Server, federating the node into the cell and, using the Deployment Manager to create the new server and add it to the cluster for the service in question.
The Deployment Manager automatically synchronizes all the required configuration artifacts to the new server. This makes Lotus Connections easy to configure in a network environment and allows scalability easy and quick scalability of the product. As the new node is already configured with WebSphere Application Server the next step is federate the node into the cell and then to add these new servers. The following steps describe this process:
- On the second node (node2.example.com), open a command prompt and change to the bin directory of the local WebSphere® Application Profile, C:\IBM\WebSphere\AppServer\Profiles\AppSrv01\bin.
- Run the addNode command to add this node to the DM cell. Command syntax is as follows:
addnode [dmgr_host] [dmgr_port] [-username uid] [-password pwd] [-localusername localuid] [-localpassword localpwd]
- After the command completes, review the addNode.log, located in the following directory: C:\IBM\WebSphere\AppServer\profiles\AppSrv01\log\addNode.log
- If you have not already done so, copy the JDBC file, sqljdbc.jar, to the same location on node 2 as on node 1. Also verify that the data store is accessible from this node.
- Copy the Stellant binary from node 1 to node 2. The same file paths and folder structure should be replicated on node 2. The binary is located in the following directory: C:\IBM\LotusConnections\search\search\search\dcs
Ensure that the entire dcs folder is copied to the exact same location on node 2. You can now complete the remainder of the second node configuration from the deployment manager.
- Open the deployment manager console and follow these steps to create new servers and add them to a cluster. The following example applies to the activitiesCluster only. It is important that you repeat these steps for each cluster in the configuration.
a. Click Servers > Clusters > activitiesCluster> Cluster members > New.
b. Enter the server name and select the node on which to create the server – node 2. Click Add Member.
c. Click Next to display a summary window. Click Finish to add the server and save the configuration.
d. Select Servers > Clusters > activitiesCluster > Cluster members. Notice that the server you just added is in the cluster. Select the newly added server to open a detailed configuration page.
e. In the section named Communications, locate the ports menu. Expand this option and locate the drop-down list containing port numbers. Make a note of the values for WC_defaulthost and WC_defaulthost_secure.
f. Add these values to the list of host aliases. To do so, click Environment > Virtual Hosts > default_host > Host Aliases and click New.
g. After you have completed this process for the 11 clusters in the configuration, save the configuration. Next, select System Administration > Nodes. In the node list, select Node 1 and Node 2 and then click Synchronize to perform a synchronization between the nodes.
At this point, the cluster is created with two nodes, a deployment manager to centrally administer the application, a common data store, and mail integration. However, there is one key component missing before we can start the application. This Web server setup task is discussed in the Post installation tasks topic that follows.
|
|
|
|
|
|
| Version 3 |
January 26, 2010 |
11:36:14 PM |
by Dana Liburdi  |
|
|