Uninstall the old Team Server:

1. Stop the old Team Server service by running the stopService.bat file located in the bat folder of the Team Server installation. This is mandatory. It ensures that the Team Server will have flushed all of its data into persistent storage, and ensures this consistent data set is used by the Team Server.
   
   

2. Uninstall the old Team Server service by running the uninstallService.bat file located in the bat folder of the Team Server installation.
   
   

Install the new Team Server:

1. Rename the current TeamServerHome folder to TeamServerHome-old.
   
   

2. Unzip the new Team Server installer file to the location where the Team Server must be installed.
   
   

3. Copy the teamserver.config.json file from the old Team Server location to the new Team Server location. The structure of the new Team Server installation folder should look similar to this:
   
   
   
   

4. If you have previously made changes to the wrapper.conf file, add these changes to the file in the new Team Server installation (located in the TeamServerHome\conf folder). Examples of changes may be the HTTP port, the java.exe location, and JVM memory.
   
   

5. Open the application.conf file (located in the TeamServerHome\conf folder), and do the following:
   
   
   • Copy the secret from your teamserver.config.json file, and in the section "Configure secret key", replace Secret  with your copied secret:
     
     play.http.secret.key = "Secret"

Example: play.http.secret.key = "Ge29UHhW78fK36Nd"
     
     
   • Copy the base URL from the teamserver.config.json file (baseUriServerName+baseUriPort) to the teamservice URL.
     
     teamServiceUrl="http://localhost:9000"

     

   • In the section "Configure database connection", find the database type you are using, remove the # in front of the lines of the complete database connection string, and replace the default values with your data. The following database connections are available:

      SQL Server using SQL Server Authentication

     db {
       default {
         driver = com.microsoft.sqlserver.jdbc.SQLServerDriver
         url = "jdbc:sqlserver://localhost:1433;databaseName=database-name"
         username = "Username"
         password = "StrongPassword" 
         }
     }

     Replace localhost with your database location, and database-name with the name of your database. Replace Username and StrongPassword with the appropriate values. Do not copy the password from the teamserver.config.json file, since the Team Server has encrypted it. If you do not know the password, ask your database manager.

      SQL Server using integrated security (Windows Authentication)

     When using integrated security, the Team Server will try to sign in to the database using the credentials of the user who is starting the Team Server.

     db {
       default {
         driver = com.microsoft.sqlserver.jdbc.SQLServerDriver
         url = "jdbc:sqlserver://localhost:1433;databaseName=database-name;integratedSecurity=true"
         }
     }

     
     Replace localhost with your database location, and database-name with the name of your database.
     
     

      PostgreSQL

     db {
       default {
         driver = org.postgresql.Driver
         url = "jdbc:postgresql://localhost:5432/database-name"
         username = "Username"
         password = "StrongPassword" 
       }
     }

     
     Replace localhost with your database location, and database-name with the name of your database. Replace Username and StrongPassword with the appropriate values. Do not copy the password from the teamserver.config.json file, since the Team Server has encrypted it. If you do not know the password, ask your database manager.

6. If you have previously made changes to the application.conf file in the old Team Server installation, also add these changes to the file in the new installation. Changes made to this file can come from using an official HTTPS certificate for the Team Server and/or local installation of HoriZZon.
   
   

7. Add the new Team Server service to the services by running the installService.bat file located in the bat folder of the Team Server installation. If you have previously added the Team Server using an AD service account, use that account again.
   
   

8. Start the new Team Server service by running the startService.bat file located in the bat folder of the Team Server installation. All data and users should be available again.

Uninstall the old Team Server:

1. Stop the old Team Server service by running the stopService.bat file located in the bat folder of the Team Server installation. This is mandatory. It ensures that the Team Server will have flushed all of its data into persistent storage, and ensures this consistent data set is used by the Team Server.
   
   

2. Uninstall the old Team Server service by running the uninstallService.bat file located in the bat folder of the Team Server installation.
   
   

Install the new Team Server:

1. Rename the current TeamServerHome folder to TeamServerHome-old.
   
   

2. Unzip the new Team Server installer file to the location where the Team Server must be installed.
   
   

3. If you have previously made changes to the wrapper.conf file, add these changes to the file in the new Team Server installation (located in the TeamServerHome\conf folder). Examples of changes may be the HTTP port, the java.exe location, and JVM memory.
   
   

4. If you have previously made changes to the application.conf file, add the same changes to the file in the new Team Server installation (located in the TeamServerHome\conf folder). Examples of changes may be the teamServiceUrl, secret key, and the SQL JDBC.
   
   
5. Add the new Team Server service to the services by running the installService.bat file located in the bat folder of the Team Server installation. If you have previously added the Team Server using an AD service account, use that account again.
   
   

6. Start the new Team Server service by running the startService.bat file located in the bat folder of the Team Server installation. All data and users should be available again.