Upgrading Your Installation Using the Derby Migration Utility

To upgrade an existing installation on a Microsoft Windows host, use the migration utility to move the existing tidb database to your Derby installation and preserve your existing data:

Make sure you have the Derby database application installed and the database you intend to use for TeamInspector created. If you need installation instructions, see steps 1-4 in Installing and Creating a Derby Database to use with TeamInspector above.
Make a backup copy of the tidb database located in the TeamInspector installation directory by copying the entire tidb folder in TEAMINSPECTOR_HOME\data to a location outside of the TeamInspector installation path. TeamInspector removes the database previously installed for the TeamInspector data-store repository and requires an external database to store TeamInspector data.
Run the migration script provided in the top level directory of your extracted installation files using the following example syntax:
```
migrate-derby.bat  [<new Team Inspector database drive>:<new Team Inspector database  path and name>]
```
For example:
```
migrate-derby.bat c:\Derby\data
```
The new directory path specified in the script argument must exist before running the script. TeamInspector does not create the directory.
Note: If you want to move the database to a remote server (other than the TeamInspector server), you must first map the drive of the remote server you intend to specify in the migration script argument and make sure that the mapped drive has write privileges.
Run the setup script from your Derby bin directory to enable remote hosts to connect to your TeamInspector database.
```
setNetworkServerCP
```
Start the Derby Network Server for your Derby installation, if not already started:
```
startNetworkServer -p <port number> -h <Derby server>
```
Where port number is the connection port for your Derby server. Derby uses 1527 as the default port assignment. Derby server is the server address or server hostname where Derby resides.
Note: If you specify localhost for the Derby hostname, only TeamInspector on the local server can connect to the database, restricting any other TeamInspector server from using the database.
If you start the Derby server from the command-line, the command-line window must remain active. Alternatively, you can start it as a service. The following link describes several methods for creating a DerbyWindowsService and provides an example for using the Java Service Wrapper (jsw) to create the service: http://wiki.apache.org/db-derby/DerbyWindowsService
Start the TeamInspector installation by going to the directory in which you downloaded and extracted the product files and run the executable: TeamInspector.exe. When the installation program starts, follow the prompts in the installation wizard. When the prompt for the Database Connection information is presented, update the values to point to your Derby database installation and the database that you have created to use with TeamInspector.
After the installation program has completed, locate the env-settings.conf file in the conf directory of your installation and update the file to specify your SCM settings. TeamInspector does not change your settings in the env-settings.conf file on an upgrade, and instead provides the settings required in this version in a default file, env-settings.conf.default. To configure your SCM systems for use with TeamInspector, update your env-settings.conf file by copying the appropriate SCM sections from the env-settings.conf.default file and following the instructions in that file to uncomment and update the settings for your environment.
TeamInspector preserves your existing configuration settings on an upgrade; no further configuration is needed. You can launch TeamInspector and view the online help if you need additional information about getting started or using TeamInspector.