Prerequisites

TeamInspector runs in an existing build environment:

The SCM systems you are using with your builds must be installed, set up, and available.
The build tools you are using for your builds must be installed on your build servers and configured for your build executions.
Any test and analyzer tools you intend to use must be installed and configured for your builds.

You can use an Apache Derby database to store the TeamInspector data. Oracle 10g and SQL Server 2005 are also supported. The database you intend to use for the TeamInspector data repository must be set up and ready for use before you start the installation. You can download Derby from the Apache DB Project download site if you do not have a database application already installed to use for TeamInspector. Instructions for installing Apache Derby are provided in the next section. If you are upgrading TeamInspector and using Derby for the new version, you must run the migration script before starting the TeamInspector installation. See the section Upgrading a TeamInspector Installation for details about migrating data from your existing installation to the current installation. If you are installing TeamInspector on a remote job server, the database connection information is required by the job service on every system on which TeamInspector is installed.

The installer allows you to install the TeamInspector Master Services and the Job Service separately. If you intend to run builds on a different server than the TeamInspector master server, you must first install the TeamInspector Master Services on the machine you intend to use as the master server before installing the Job Service on remote build servers.

TeamInspector uses the Apache FTP services and automatically sets a default port of 21 to use for this service. If you anticipate a conflict with this port setting, you can change it on the Configuration page when you log on to TeamInspector after setup is complete.

You must satisfy the following requirements for the software configuration management (SCM) systems that you intend to use with TeamInspector:

If you are using Subversion, the SVNKit toolkit must be installed on the TeamInspector servers and the SVNKit JAR files must be extracted and accessible to TeamInspector. To access the SVNKit JAR files, use the settings in the TeamInspector env-settings.conf file. For more information about configuring these requirements, see Configuring Subversion Settings in the online help.
If you are using a Perforce SCM system with your builds, the Perforce Command Line Client (P4 client) must be installed on all the servers (master server and job servers) on which TeamInspector is installed in your build environment. The P4 client must be available to TeamInspector through the system path. The path can be specified in the env-settings.conf file, located in the conf directory. For more information about configuring these settings, see Configuring Perforce Settings in the online help. See the Release Notes for more information about this requirement.
If you are using an IBM Rational ClearCase SCM system with your builds, the ClearCase Remote Client must be installed on all systems on which you install TeamInspector, and you must make the TeamAPI jar files available to TeamInspector. For more information about configuring the settings for a ClearCase SCM system, see Configuring ClearCase Settings in the online help.
If you are using a StarTeam SCM system, the StarTeam SDK must be installed on all systems on which you install TeamInspector and the SDK JAR files must be accessible to TeamInspector. You can configure the location of the JAR files by using the settings in the env-settings.conf file in TeamInspector to interact with your StarTeam SCM system. For more information about configuring these requirements, see Configuring StarTeam Settings. See the Release Notes for more information about this requirement.