Quick reference to upgrading
Use this information as a quick reference to upgrading the server-side components of Tivoli Netcool/OMNIbus.
The steps are as follows:
| Action | More information |
|---|---|
| 1. Review compatibility issues with earlier versions of the product. | |
| 2. Prepare for the upgrade by checking the prerequisites and obtaining the installation package. | IBM Prerequisite Scanner |
| 3. If your existing installation is running
in non-FIPS 140–2 mode and you intend to upgrade the product to operate
in FIPS 140–2 mode, use the FIPS 140–2 configuration checklist to
help you upgrade. Based on your existing setup, some configuration
steps might be required before you upgrade. Configuration steps will
also be required after you upgrade. Pre-upgrade steps are generally required if the user passwords in your system are currently encrypted by using the DES algorithm, or if you are using property value encryption to encrypt string values in properties files. |
|
| 4. Back up your existing system and then use IBM Installation Manager to
install Tivoli Netcool/OMNIbus into
a new directory.
|
|
5. Review the list of files migrated and perform any manual configuration required. |
|
6. On UNIX operating systems, set the following
environment variables if necessary:
See the guidance for setting these environment variables. |
|
7. Upgrade your ObjectServer schema to the V8.1 schema. |
|
| 8. If you upgraded from an earlier version that
used SSL for client and server communications, and want to continue
to use your old certificates, migrate your certificate files and private
keys into the key database that is used for certificate management. Certificate migration is supported only in non-FIPS 140–2 mode. If you intend to operate in FIPS 140–2 mode, you must use iKeyman to re-create all the old certificates that you want to reuse. |
This gives you
the option to have