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
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.sh
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:
- Ensure that you are logged in as the user root (using the
- Create a group named "dbtuadm" within the
operating system and add all users to this group, which
will be using the DbtuTools framework later on.
- Create the /opt/dbtutools tree
including subtree per DB2 instance and apply the
proper permissions and ownerships as well.
- Copy dbtuswitch.sh
and its configuration files dbtuswitch.cfg
from your build directory to /opt/dbtutools
and ensure that the defaults within the configuration
file meets your environment.
- Copy the binaries, (wrapper) scripts and JAR files
(named in the following list) from your build directory
(where INSTANCE stands for the instance name):
- (Wrapper) scripts:
- JAR files:
- Optional: Copy the entire doc subdirectory
content from your build directory to
(where INSTANCE stands for the instance name).
- Optional: It's a good idea to add a
dbtuswitch.sh call to the ~/.profile file
of the users you added to the "dbtuadm" group above
. /opt/dbtutools/dbtuswitch.sh default
Sample entry for the ~/.profile 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:
- Copy the tool of your choice from the build directory into
your preferred target directory.
- 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.
- 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
~/db2inst1/tools/temp if ~/ represents
the target directory). Ensure the $DBTUTOOLSHOME
environment variable points to the chosen target directory.