Add a node to an existing cluster.
Before you begin
You must already have a cluster with at least one member. Ensure
that you installed IBM® WebSphere® Application Server
Network Deployment (Application Server option) on the new node.
Although
the IBM Cognos® Business Intelligence server is managed
by the same Deployment Manager as IBM Connections,
you cannot add that node to the Connections cluster.
About this task
To add a node to a cluster, complete the following steps:
Procedure
- Add a node to the DM cell:
- Log on to the new node.
- Open a command prompt and change to the bin directory
of the local WebSphere Application
Server profile:
app_server_root/profiles/profile_name/bin
where profile_name is
the name of the applicable WebSphere Application
Server profile on this node.
- Run the addNode command to add this
node to the DM cell: .
addnode [dmgr_host]
[dmgr_port] [-username uid]
[-password pwd] [-localusername localuid]
[-localpassword localpwd]
where
- dmgr_host is the host name of the Deployment
Manager
- dmgr_port is the SOAP port of the deployment
manager (the default is 8879)
- uid and pwd are the DM administrator
user name and password
- localuid and localpwd are
the user name and password for the WebSphere Application
Server administrator of the node
- Open the addNode.log file and confirm
that the node was successfully added to the DM cell. The file is stored
in the following location:
app_server_root/profiles/profile_name/log/addNode.log
- Copy the relevant JDBC files from the DM node to this node,
placing them in the same location as the JDBC files on the DM. If,
for example, you copied the db2jcc.jar file from
the C:\IBM\SQLLIB directory on the DM, you must
copy the same file to the C:\IBM\SQLLIB directory
on this node. See the following table to determine which files to
copy. See the following table to determine which files to copy:
Table 1. JDBC filesDatabase type |
JDBC files |
DB2® |
db2jcc.jar
db2jcc_license_cu.jar
sql
|
Oracle |
ojdbc6.jar
|
SQL Server |
sqljdbc4.jar
|
- Ensure that the shared folders that are used for the application
content stores in the cluster are accessible from the new node: from
the new node, try to access the shared directories.
- Add additional members
to an existing IBM Connections
cluster:
- Log on to the Deployment Manager Integration Solutions
Console.
- Click . Specify the following information about the new cluster
member:
- Member name
- The name of the server instance that is created for the cluster.
The DM creates a server instance with this name.
Note: Each member
name in the same cluster must be unique. The Integration Solutions
Console prevents you from reusing the same member name in a cluster.
- Select node
- The node where the server instance is located.
Click Add Member to add this
member to the cluster member list.
- Click Next to go to the summary
page where you can examine detailed information about this cluster
member. Click Finish to complete this step
or click Previous to modify the settings.
- Click Save to save the configuration.
- Click . In the member
list, click the new member that you added in the previous step.
- On the detailed configuration page, click Ports to
expand the port information of the member. Make a note of the WC_defaulthost
and WC_defaulthost_secure port numbers. For example, the WC_defaulthost
port number is typically 9084, while the WC_defaulthost_secure port
number is typically 9447.
- Click . Enter the following information for the host alias
for the WC_defaulthost port:
- Host name
- The IP address or DNS host name of the node where the new member
is located.
- Port:
- The port number for WC_defaulthost. For
example, 9084.
Click OK to complete the
virtual host configuration.
- Click Save to save the configuration.
- Repeat the previous two sub-steps to add the host alias
for the WC_defaulthost_secure port.
- Click .
- In the node list page, select all the nodes where the
target cluster members are located and then click Synchronize.
- Review the configuration of the application server added
to the cluster. JVM settings need to be adapted to equal the other existing application servers in the
cluster. Refer to Reviewing the JVM heap size. Other configuration settings to consider reviewing include
webcontainer threads and session timeouts
settings.
Note: Custom properties set on the existing application servers need to be reapplied to any
new node and server post-installation. Find these properties in .
- Enable the Startup beans service at server startup. Open the WebSphere Integrated Solutions
Console.
- Click .
- In Container Settings, expand Container Services.
Then click Startup beans service.
- In General Properties, check the box next to Enable Service at
server startup.
- Click OK.
- Restart the server.
For more information, see Startup beans service settings.
- Configure IBM HTTP
Server to connect to this node. For more information, see the Configuring IBM HTTP Server and Defining IBM HTTP Server topics.
- Repeat this procedure for each new node that you want to
add to a cluster.
- Configure CCM for newly added nodes to make FileNet work well with IBM Connections Content
Manager.
- Perform these additional steps to add the Search application to a new node.
Results
If you experience interoperability failure, you might be running two servers on the same host
with the same name. This problem can cause the Search and News applications to fail. For more
information, see Application access problems in the WebSphere Application
Server Network Deployment product documentation, and select NameNotFoundException from JNDI
lookup operation.