Installation

Due to the fact that the DbtuTools framework becomes more and more integrated, it is recommended you install the entire framework [more]. Nevertheless it will still be possible to install a single tool only [more].

Entire framework

One of the basic qualities of the DbtuTools framework is the ability to handle environments with multiple DB2 instances. This, and the use of dbtuswitch.bat [more], configuration-, temporary- and log files, makes it necessary to apply the /opt/dbtutools tree [more] prior to the installation of the tools. In future versions there will be an installation script for automating these steps:

1. Ensure that you are logged in as the user with Administrator authorizations.
2. Create the /opt/dbtutools tree [more] including subtree per DB2 instance and apply the proper permissions and ownerships as well.
3. Copy dbtuswitch.bat [more] and its configuration files dbtuswitch.cfg [more] from your build directory to C:\Program Files\DbtuTools\ and ensure that the defaults within the configuration file meets your environment.
4. Copy the binaries, (wrapper) batch files and JAR files (named in the following list) from your build directory to C:\Program Files\DbtuTools\INSTANCE\tools\bin\ (where INSTANCE stands for the instance name):
   
   • Binaries:
     • dbtuapiwrapper.exe
     • dbtulsts.exe
     • dbtuwho.exe
   • (Wrapper) batch files:
     • dbtuff2code.bat
     • dbtugetss.bat
     • dbtupreptime.bat
     • dbtutraffic.bat
     • dbtuxconnect.bat
   • JAR files:
     • dbtutools.jar
5. Optional: Copy the entire doc subdirectory content from your build directory to C:\Program Files\DbtuTools\INSTANCE\tools\doc\ (where INSTANCE stands for the instance name).
6. Optional: It might be a good idea to add a dbtuswitch.bat call to the C:\Program Files\SQLLIB\bin\db2clp.bat file:
   

   "C:\Program Files\DbtuTools\dbtuswitch.bat" default

   Sample entry for the C:\Program Files\SQLLIB\bin\db2clp.bat file.

Single tool only

As discussed above, it is not recommended to install a single tool only. Nevertheless it is possible for most of the tools. The effort differs based on the needed resources:

1. Copy the tool of your choice from the build directory into your preferred target directory.
2. Optional: If the selected tool is based on Java, you have to copy the JAR files for the build directory into your preferred target directory. Ensure the CLASSPATH environment variable contains the entries for the JAR files as well.
3. Optional: If the selected tool works with configuration-, log- or temporary files, you have to create the related parts of the /opt/dbtutools subtree within your preferred target directory (for example C:\Any\db2inst1\tools\temp\ if C:\Any\ represents the target directory). Ensure the DBTUTOOLSHOME environment variable points to the chosen target directory.