IBM Support

TBSM 6.2 Failover Configuration Guide - step by step example

Technical Blog Post


Abstract

TBSM 6.2 Failover Configuration Guide - step by step example

Body

This guide has the purpose to illustrate a complete step by step example for setting up a failover configuration for TBSM 6.2. It can be downloaded from here:

https://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=cdd16df5-7bb8-4ef1-bcb9-cefb1dd40581#fullpageWidgetId=W05de62601548_4e85_8940_81bb58657a85&file=9eff7a1a-fc00-4730-b8ee-f5319050cdfc

 

Also during tests an issue has been observed causing RADServices to be restarted on the primary server while the secondary TBSM Data server is being restarted. A case could be opened at IBM to ask for a test fix for APAR IJ15391 to avoid such problems. Details here: https://www-01.ibm.com/support/entdocview.wss?uid=swg1IJ15391

 

Within this new TBSM 6.2 guide the following versions were used:


1. Installation Manager 1.8.9
2. IBM DB2 Workgroup Server Edition 11.1.2.2
3. IBM Tivoli Netcool/Omnibus 8.1 - Fix Pack 18
4. IBM WebSphere Application Server Version 8.5.5 - Fix Pack 13
5. Jazz for Service Management 1.1.3 - Fix Pack 2
6. IBM JAVA 8.0.5.6
7. IBM Tivoli Netcool/Omnibus 8.1.0.4-webgui Fix Pack 15
8. IBM Tivoli Netcool/Impact 7.1 Fix Pack 15

 

All the TBSM prerequisites and components were installed using 3 servers as follows, but this is not a mandatory configuration:

- On server 1: Installation Manager, Omnibus, Netcool/Impact Primary, TBSM Primary Data Server
- On server 2: Installation Manager, Netcool/Impact Secondary, TBSM Secondary Data Server
- On server 3: Installation Manager, DB2, TBSM Database Configuration Utility, WAS, JazzSM/DASH, WebGUI, TBSM Dashboard Server

 

The guide contains screenshots and details for each installation and configuration needed to be followed. The most important aspects needed to be taken into consideration to avoid unwanted failures would be the following:

- Netcool/Impact servers should be configured from the beginning as an Impact cluster, prior to any TBSM component installation process to begin.
- While installing TBSM Primary data server, the secondary impact instance should be stopped.
- While installing TBSM Secondary data server, the primary impact instance should be up and running.
- During the TBSM Secondary installation process the Designated Backup option should be checked.
- During the TBSM Dash installation process the HA/FO option should be checked.

 

Previous guides created for TBSM installation with everything installed on the same servers, with the components distributed on several servers as well as SSO configuration could be found as follows:

 

Installation example with everything installed and configured on one server:
/support/pages/node/1080063


Installation example with everything installed and configured on two servers:
/support/pages/node/1081869


Installation example with everything installed and configured on two servers including SSO configuration between DASH and Impact:
/support/pages/node/1082421

 

Others are planned as well and hopefully you will find them useful!

 

Mihaela Gheorghe

mihaela.gheorghe1@ibm.com

[{"Business Unit":{"code":"BU004","label":"Hybrid Cloud"},"Product":{"code":"","label":""},"Component":"","Platform":[{"code":"","label":""}],"Version":"","Edition":""}]

UID

ibm11081911