To add additional nodes to the cluster, follow these steps. Note that these steps must be repeated for node 2 and node 3 individually.
1. From the node that you want to add to the cluster, open a command prompt and change to the bin directory of the local WebSphere Application Profile. For example, change to the /opt/IBM/WebSphere/AppServer/Profiles/AppSrv01/bin directory.
2. Run the
addNode command from the AppSrv01 bin directory (/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin/addnode.sh) on each node to be added to the deployment manager cell. Command syntax is as follows:
./addnode.sh [dmgr_host] [dmgr_port] [-username uid] [-password pwd] [-localusername localuid] [-localpassword localpwd]</pre>
3. After the command completes, check the addNode.log file, located in the following directory:
/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/log/addNode.log.
4. If you have not already done so, copy the JDBC file, ojdbc14.jar, to the same location on this node as on node 1. Also verify that the data store is accessible from this node (mounted on /mnt/LotusConnections/Data).
5. Copy the Stellant binary from node 1 to each node being added. The same file paths and folder structure should be replicated on each node as node1. The binary is located in the following directory:
/opt/IBM/LotusConnections/search/search/search/dcs
Copy the entire dcs folder to the exact location on the node being added. Then add the following text to the end of the /etc/profile file on the subsequent node:
export PATH=$PATH:/opt/IBM/LotusConnections/search/search/search
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/IBM/LotusConnections/search/search/search/dcs/oiexport
At this point, it is highly recommended to add a task to ensure that the file share (/mnt/LotusConnections/Data) is always configured when the node machines are restarted. To do so, add the following line to the '/etc/fstab' file:
'/mnt/LotusConnections/Data //nfs_fileshare.example.com/LotusConnections smbfs auto,rw,username=<administrator>,password=<password> 0 0'
You can now complete the remainder of the subsequent node configuration from the deployment manager.
6. Open the deployment manager console.
The following process needs to be followed for each of the clusters in the configuration. This example shows the activitiesCluster only. Repeat this step for each cluster and then again for each node.
a. Click Servers > Clusters > activitiesCluster > Cluster members > New.
b. Enter the server name and select the node on which to create the server. Ensure to select the correct node. Click Add Member.
c. Click Next to be presented with a summary window. Click Finish to add the server and then save the configuration.
d. Click Servers > Clusters > activitiesCluster > Cluster members. The server that you just added to the cluster is displayed. Select the new server that you added to open a detailed configuration page.
e. Within the Communications section, there is a Ports menu. Expand this option to view a drop-down list of port numbers. Write down the value 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 then select New as shown:
g. Add the host name of node 2 and the value for WC_defaulthost. Click OK. Repeat the process of adding the host aliases for both WC_defaulthost and WC_defaulthost_secure for all of the features as you add them to the cluster.
After you complete this process for all of the 11 clusters in the configuration, make sure to save the configuration. Next select
System Administration > Nodes. In the node list, select Node 1 and the subsequent nodes that you added. Then click
Synchronize to perform a synchronization between the nodes.
After you complete this process for both Node 2 and Node 3, the cluster configuration is complete. Now the deployment manager can centrally administer the application. A common data store has been set up and is available to all nodes and mail integration is also configured by the installer.
At this stage, you can start Lotus Connections 2.5. However there is one key component missing before we can start the application. You must set up the Web server, as discussed in the post installation tasks that follow.
Go to the next topic:
S2: Scenario environment
S2: Prerequisites
S2: Configuration diagrams
S2: Machine details
S2: Installing Lotus Connections in an Enterprise level deployment
S2: Preinstallation tasks
S2: Installing Lotus Connections on node 1
S2: Adding nodes 2 and 3 to the cluster
S2: Post installation tasks
S2: Starting Lotus Connections
S2: Configuring an administrative user for Blogs
S2: Integrating Lotus Connections with Lotus Quickr for WebSphere Portal
S2: Enabling Sametime awareness on Lotus Connections
S2: Troubleshooting
Table of Contents:
Lotus Connections 2.5 Enterprise level deployment scenario