IBM Tivoli Netcool/OMNIbus, Version 7.4

Joining a node to a load balancing cluster

You can configure a Tivoli Integrated Portal Server to join an existing load balancing cluster.

Before you begin

If you are joining a stand-alone Tivoli Integrated Portal Server instance to a cluster, ensure that you first export all of its data. Once you have joined it to the cluster, you can then import the previously exported data. Other nodes in the cluster should not contain any custom data and should effectively be new installed instances.
Make sure you have successfully enabled load balancing following the steps in Setting up a load balancing cluster.
Tivoli Integrated Portal should be installed to the node using the same cell name that is designated for the cluster.
All console modules deployed to the cluster must be already deployed to the node that you intend to join.
You should deploy any wires or transformations used by the nodes in the cluster.
If the cluster is using any customization changes in consoleProperties.xml you must copy these changes and this file to the same location on the node that you intend to join.
The node must be configured to the same LDAP with the same user and group definitions as all other nodes in the cluster.

Procedure

Check that you have the JDBC driver for DB2 on the computer where Tivoli Integrated Portal is installed. The JDBC driver is in tip_home_dir/universalDriver/lib.

From a command prompt, change to the tip_home_dir/profiles/TIPProfile/bin/ha directory and edit the settings in tipha.properties.

Property name	Description
DBHost	The hostname or IP address of the machine where the DB2 database is installed. Example: `tipdb.cn.ibm.com`
DBPort	Port number of the DB2 server. Example: `50000` (default)
DBName	The name of the database that you created. Example: `tipdb`
DBProviderClass	Class name of the DB2 provider. Example: `com.ibm.db2.jcc.DB2Driver` (default)
DBProviderName	Name of the DB2 provider. Example: `TIP_Universal_JDBC_Driver` (default)
DBDatasource	JNDI name of the datasource. Example: `jdbc/tipds`
DBDatasourceName	Name of the datasource used for load balancing. Example: `tipds`
DBHelperClassName	DB2 Helper class name. Example: `com.ibm.websphere.rsadapter.DB2UniversalDataStoreHelper` (default)
DBDsImplClassName	DB2 datasource implementation class name. Example: `com.ibm.db2.jcc.DB2ConnectionPoolDataSource` (default)
DBDriverVarName	WebSphere environment variable name for DB2 JDBC driver class path. Example: `TIP_JDBC_DRIVER_PATH`
DBJDBCDriverPath	Location of DB2 JDBC driver libraries (for example, db2jcc.jar). Example: `C:/IBM/tivoli/tipv2/universalDriver/lib`
DBDriverType	JDBC driver type. Example: `4` (default)
DBType	Database type. Example: `DB2` (default)
JaasAliaseName	JAAS alias name used to store database username and password. Example: `TIPAlias` (default)
JaasAliasDesc	Description for JAAS alias name. Example: `JAAS Alias used for load balancing`
LocalHost	The hostname or IP address of the machine on which the console is running. LocalHost and LocalPort uniquely identify the node in the cluster. Example: `tip01.cn.ibm.com`
LocalPort	Administrative console secure port. LocalHost and LocalPort uniquely identify the node in the cluster. Example: `16311`
WasRoot	The full system path to where the application server and console images were extracted during installation. Example: `C:/IBM/tivoli/tipv2`
ProfileName	The profile name that was specified on the manageprofiles command after installation. If no profile name was specified, the default is used. Example: `TIPProfile` (default)
CellName	The cell name that was specified on the manageprofiles command after installation. If no cell name was specified, the default is used. Example: `TIPCell` (default) This parameter is optional for a single node console installation. For a load balancing cluster, however, it is required to ensure all nodes use the same cell name.
NodeName	The application server node name. Example: `TIPNode` (default)
ServerName	The WebSphere Application Server instance name. Example: `server1` (default)
IscAppName	The Tivoli Integrated Portal Server enterprise application name. The Tivoli Integrated Portal Server enterprise application is installed in directory the following directory: ${WAS_ROOT}\profiles\${ProfileName}\installedApps\${CellName}\${IscAppName}.ear Example: `isc` (default)
LoggerLevel	The level of logging required. The default is `OFF`. Example: `FINER`
HAEnabled	Indicates if load balancing is enabled. Attention: Do not edit this value manually.

In the tip_home_dir/profiles/TIPProfile/bin directory, depending on your operating system, enter one of the following commands:
- stopServer.bat server1
- stopServer.sh server1
  Note: On UNIX and Linux systems, you are prompted to provide an administrator username and password.
Make sure the Tivoli Integrated Portal Server is not started.
At a command prompt, change to the tip_home_dir/profiles/TIPProfile/bin/ha directory and issue this command
- ..\ws_ant.bat -f install.ant configHA -Dusername=DB2_username -Dpassword=DB2_password
- ../ws_ant.sh -f install.ant configHA -Dusername=DB2_username -Dpassword=DB2_password
The command creates the DB2® schemas required for Load Balancing.
In the tip_home_dir/profiles/TIPProfile/bin directory, depending on your operating system, enter one of the following commands:
- startServer.bat server1
- startServer.sh server1

Results

The console node is joined to the cluster.

What to do next

Add another node to the cluster, or if you have completed adding nodes, enable server to server trust for each node to every other node in the cluster.

Depending on the network dispatcher (for example, IBM HTTP Server) that you use, you might have further updates to get session requests routed to the new node. Refer to the documentation applicable to your network dispatcher for more information.