Moving TADDM from one operating system to another
To move TADDM from one operating system to another, complete the following steps.
- Make an offline backup of your current production database.
- Restore the backup to the new database server.
- Stop TADDM.
- Copy the taddm directories recursively
from your current primary storage server to a new primary storage
server. Change all
com.collation.db.*properties in the collation.properties file to match the new database (primary and secondary schema).
When you copy the taddm directories, the following limitations apply:
- TADDM is not started automatically, unless you set it up.
- BIRT reports might still point to the production database. You can find the database server name hardcoded in the dist/deploy-tomcat/birt-viewer/WEB-INF/report files (TADDM 7.3.0) or in the dist/apps/birt-viewer/WEB-INF/report (TADDM 220.127.116.11, and later) . Delete the *rptdesigncompiled files so that TADDM recompiles them correctly with the new collation.properties file settings.
- The SSL certificate has the old server name, which might generate warnings if you use SSL on the UI.
- After you copy the taddm directories, before you start TADDM, update the collation.properties file to point to the new database. Search for any IP addresses or FQDNs from your TADDM server environment, by default they are not added to the collation.properties file, but it is possible that a customization was made.
- When you copy TADDM from the Windows operating system to the UNIX operating systems, run the dos2unix command for all *properties files.
- If you have any additional servers (discovery servers
and secondary storage servers), copy their taddm directories
to the new servers, which are a part of the same setup as the primary
storage server that you copied in step 3. Change the database
com.collation.db.*parameters in the collation.properties file to point to the new database. Also, change the
com.collation.PrimaryStorageServer.hostproperty to point to the new primary storage server.Note: When you copy TADDM from the Windows operating system to the UNIX operating systems, run the dos2unix command for all *properties files.
- Go to the external/ directory, and extract the jdk archive that corresponds to your operating system.
- Start TADDM and make sure that all user interfaces are displayed correctly, that you can run discoveries, and that any other function that is critical works.