IBM Support

Example of ITM-TEPS and ITM-HUB Migration to a new hardware server

Question & Answer


Question

Is there a summary of links and documentation useful for migrating ITM-TEPS and ITM-HUB sever to a new  hardware server?

Cause

It is often time consuming to find links and documentation that are useful for migrating from ITM-TEPS and ITM-HUB sever to a new  hardware server

Answer

TEPS Server
============================================================
1) Install a TEPS at the existing maintenance and with all application support on the new system.
2) Do a migrate-export from the old TEPS
3) Do a migrate-import into the new TEPS
4) Upgrade the TEPS to the target maintenance level.
5) configure TEPS to connect to the hub TEMS
Reference:
Migrate-export and backing up your TEPS database.
https://www.ibm.com/support/pages/migrate-export-and-backing-your-teps-database
Migrate-import and restoring the TEPS database.
https://www.ibm.com/support/pages/migrate-import-and-restoring-teps-database
============================================================

HUB TEMS Server
============================================================
I) HUB move from one server to a other server
-----------------------------------------------------------
1) Custom Situations:

a) ./tacmd login -s sourceservername/ip address -u root -p password -t 1440
b) tacmd listSit | grep filter(for custom situations)
c) copy all the custom situations name to a text file and copy the text file to the TEMS/TEPS server , from
where you want to export the situations.
d) tacmd bulkExportSit -l /tmp/custom_situations/custom_situations_list.txt
e) the above command will export all the custom situation to $CANDLEHOME/bin/Bulk/SITUATION
f) copy the Bulk folder as it is to the destination server.
g) ./tacmd login -s destinationservername/ip address -u root -p password -t1440
h) ./tacmd bulkImportSit
i) all custom situations will be imported , restart the TEMS/TEPS services.

2) For Exporting Custom Navigator Views and Associated situations:
a) ./tacmd login -s sourceservername/ip address -u root -p password -t 1440
b) It is assumed that you know all the navigator views name, as tacmd exportNavigator works for specific navigator/view name
c) ./tacmd exportNavigator -s sourceservername/ip -n NavigatorViewName -x /migration/views/NavigatorViewName.xml -f -u sysadmin -p password
d) some times a navigator view is too long and command ends up in memory error, so for that use export TACMD_JVM_MAX_MEMORY=1024;
e) copy all the views directory to the destination server
f) ./tacmd login -s destinationservername/ip address -u root -p password -t1440
g) ./tacmd importNavigator -sdestinationservername -n NavigatorViewName -x /migration/views/NavigatorViewName.xml -f -u sysadmin -p password
h) Repeat the above steps for all the navigator views.
Additional Information:
Multiple Situations
•    tacmd bulkImportSit ==>> in special the force setting ==>> [-f|--force]

•    tacmd bulkExportSit
Single Situations
•    tacmd createSit ==>> tacmd createSit {-i|--import} filename

•    tacmd viewSit ==>> -e|--export FILENAME

Reference:
IBM Tivoli Monitoring mix and match migration
https://www.ibm.com/support/pages/node/1083525
IBM Tivoli Monitoring mix and match migration
https://www.ibm.com/support/pages/ibm-tivoli-monitoring-mix-and-match-migration
tacmd bulkImportSit
https://www.ibm.com/support/knowledgecenter/SSDKXQ_6.3.0/com.ibm.itm.doc_6.2.2fp2/bulkimpsit.htm
tacmd bulkExportSit
https://www.ibm.com/support/knowledgecenter/SS3JRN_7.2.0/com.ibm.itm.doc/itm_cmdref10.htm
tacmd createSit
https://www.ibm.com/support/knowledgecenter/SS3JRN_7.2.0/com.ibm.itm.doc/itm_cmdref18.htm#createsit
tacmd viewSit
https://www.ibm.com/support/knowledgecenter/SS3JRN_7.2.0/com.ibm.itm.doc/itm_cmdref48.htm#viewsit
------------------------------------------------------------------------------------------------------------------------

II) FTO Hot Standby
------------------------------------------------------------------------------------------------------------------------
a) Setup/install a standby hub on the new linux server.
b) Stop the old standby server --> Use the new standbyserver as second FTO server
c) Wait until the primary server has sync with the standby server
d) Stop the primary server --> the standby will take over the primary role
Optional if you want use a fto install a new standby server ( was the old primary) start the server as fto and wait until it is sync

References:
Configuring failover support
https://www.ibm.com/support/knowledgecenter/en/SSTFXA_6.3.0/com.ibm.itm.doc_6.3/hag/topics/hotstandby_failingover_config.htm
Configuring the hot standby feature for hub monitoring servers
https://www.ibm.com/support/knowledgecenter/SS3JRN_7.2.1/com.ibm.itm.doc_6.3/hag/topics/hotstandby_failover_hub.htm
============================================================

Additional Information/Comments:
============================================================
a) Check all conditions like operating system , disk, database version ... fit the ITM 6.3 version
b) Check and install the latest version of the required agents/TEPS/TEMS into a new server/ directory
c) Check the agent configurations like instances or similar settings
d) check and install the hub tems and rtems If you want use both itms on the same server you need different ports
e) Install the application support and seed the application support that matches the agent
f) check the database version. If the version is not supported you have to update the database. Please ask your DB admin or the database support
g) now install the TEPS server and install the application support ( !!! there can only one teps available on one server)
h) in the next step you can check if the agents are displayed successfully in the tep
i) If all this works properly you can be sure the installation worked and you have a stable env
j) next step is to bring the situations poicies ... from the old itm to the new one ( export import)
k)

You can use different os of both sites of FTO but please don't use different versions or fixpacks
!!! Please don't copy any files from one server to a other
For example the tems installation copy to the new server
======================================================================

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSCTLMK","label":"ITM Tivoli Enterprise Portal V6"},"Component":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
14 July 2020

UID

ibm16132663

Page Feedback