Upgrading TADDM

Before upgrading the IBM® Tivoli Application Dependency Discovery Manager (TADDM), ensure that your environment meets the requirements for each TADDM component, including the hardware, operating system, and software prerequisites.

For more information about hardware, operating system, and software prerequisites, see Planning for installation.

Note:
  1. If the TADDM user upgrades the DB2 version in a TADDM installation, then compatible version of the driver should also be updated. You can ask your DBA for db2jcc.jar from the TADDM DB2 server, or you can download the one appropriate for your version of DB2 here:http://www-01.ibm.com/support/docview.wss?uid=swg21363866 Once you have it, stop TADDM, copy it to the following paths, and confirm permissions are correct so that the TADDM user can read the file and then start TADDM. Repeat this step on all TADDM servers in your environment.
  2. Fix Pack 8If the TADDM user upgrades the Oracle DB version in a TADDM installation, then compatible version of the driver must also be updated. Obtain the supported ojdbc jar and the related jars (as mentioned in Upgrading the TADDM server) from Oracle website or the oracle server and once you have it, stop TADDM, remove old jars and copy the obtained jars to the dist/lib/jdbc/ and other locations where older jars are present as mentioned in above link, confirm permissions are correct so that the TADDM user can read the file and then start TADDM. Repeat this step on all TADDM servers in your environment.
  1. /dist/lib/jdbc/db2jcc
  2. /dist/apps/dap/WEB-INF/lib/
  3. /dist/apps/birt-viewer/WEB-INF/plugins/org.eclipse.birt.report.data.oda.jdbc_2.2.1.r22x_v20070919/drivers/
  4. /dist/apps/birt-viewer/WEB-INF/platform/plugins/org.eclipse.birt.report.data.oda.jdbc_2.2.1.r22x_v20070919/drivers/
Note: If you do not update the db2jcc.jar at above path, then the SSL function gsk_secure_soc_init might fail with the return code 402 in sqlccSSLSocketSetup.
Important: When you want to upgrade to TADDM 7.3.0, you must have TADDM 7.2.2 installed. You cannot upgrade from TADDM 7.2.1, or earlier, to TADDM 7.3.0.

During the upgrade new objects are created that results in the creation of new database tables. The size of the database can slightly increase, typically by up to 10%. The increase varies depending on the number and type of objects in the database. So, you might need to increase the size of database table spaces to ensure that there is enough free space available for a successful upgrade. Work with your database administrator to make any necessary changes during the upgrade.

Table 1 indicates the type of deployment that you have after you upgrade, depending on your original TADDM installation.

Table 1. Resulting deployment type after upgrade
TADDM installation before upgrade TADDM deployment type after upgrade
one domain server domain server deployment
Enterprise Domain Server and two or more domain servers synchronization server deployment
Notes:
  1. After the upgrade, any Enterprise Domain Server is a synchronization server, and domain servers are still domain servers.
  2. After the upgrade, if you have a synchronization server deployment but you want to use a streaming server deployment, you can manually convert the servers. For information about how to do this, see Converting from a synchronization server deployment to a streaming server deployment in the TADDM Wiki at https://github.com/TADDM/taddm-wiki/wiki.