After you complete installation of 7pace Timetracker (for more information, read 7pace Timetracker for DevOps Server Installation Guide), the configuration tool wizard that is bundled with the installer kicks off automatically. It allows you to configure Timetracker installed locally with DevOps Server or installed locally but integrated with the remote DevOps Server. You can re-start this tool any time you want, if you need to make changes, by running the TimetrackerOnline.ConfigTool application from the "Tools" folder in your 7pace Timetracker installation location.
IMPORTANT MIGRATION INFORMATION: If you are upgrading from 7pace Timetracker 3 to 7pace Timetracker 4, since the same database is used for both, you won't have to migrate your data; the database is changed silently. If you are upgrading from 7pace Timetracker 2.8 to 7pace Timetracker 4, after your settings are applied during the configuration process, you will need to then go to %programfiles(x86)%\7pace\Timetracker\Tools\TimetrackerOnline.MigrationTool.exe to manually migrate your data.
Please note that in 7pace Timetracker 4, the Service Account is required for server side tracking to work. Additionally, there is a new page to assist you in setting up email notifications in the 7pace Timetracker 4 configuration wizard.
Below, we will guide you through the configuration process for both 7pace Timetracker 3 and 7pace Timetracker 4.
7pace Timetracker 4 | Configuration Guide
1. After installation is complete, the "Welcome!" page of the 7pace Timetracker Configuration wizard displays.
2. Click the Next button to continue.
The wizard detects the local Team Foundation Server on which you have installed 7pace Timetracker and displays your TFS URL.
3. Choose one of the required options from the following selections:
Install on local machine along with Team Foundation Server: 7pace Timetracker is installed on the local system where Team Foundation Server is also installed.
Install locally and integrate with remote Team Foundation Server: 7pace Timetracker is installed on the local system but integrated with the remote Team Foundation Server.
4. Click the Next button.
The system displays the "Database Settings (Microsoft SQL Server)" page.
Note: On the "Database Settings (Microsoft SQL Server)" page, the option to select the same Microsoft SQL Server as TFS is disabled if you are configuring your 7pace Timetracker with remote TFS. In that case, you will need to specify the SQL Server details.
5. Check that the database server name and authentication details are correct and click the Next button.
The system displays the "Internet Information Server (IIS) Settings" page.
Note: 7pace Timetracker is using the same technology as TFS and we put a security cookie into every request. This cookie can, in some cases, interfere with the TFS cookie. Having Timetracker on the same domain as TFS can cause cookies to be overridden. The solution is to the change address of Timetracker to something distinct/different from the TFS address.
6. Check that the "Host Name" and "Network Host Port" are correct.
Note: The HTTPS Certificate drop-down list only appears if you are using secured http (that is, 'https'). The configuration tool only looks for certificates in the Web Hosting store. If the certificate is stored in a personal or alternative store, it will not be listed.
7. Click the HTTPS Certificate drop-down list and select the certificate that you want to use.
8. Click the Build-in-Account drop-down list, and select the application pool account or click the Custom Account and specify the custom account details.
9. Click the Next button.
The system displays the "Service Account" page.
Here, you can configure the "Service Account" (found in the "Configuration" tab of 7pace Timetracker, under "Settings") to display data that is usually not visible to all users. You can either enter the details for a "Custom Service Account" (we recommend that you use a team member who belongs to the Project Collection "Administrators" user group, since this has the highest permission level), or use the same account that you configured as the Application Pool Account. Important: In Timetracker 4, the Service Account is required in order for server side tracking to work.
10. Enter a valid username, including the domain name, if necessary.
11. Enter a valid password for the specified username.
12. Click the Next button to continue.
The Email Settings page displays.
If you "Enable Email Alerts", the users will receive an email notification when tracking was stopped by the system due to no response from the user during activity checks. Under "Authentication", most mail servers require authorization in order to send emails. Please enter your credentials here.
13. Click Next.
The tool starts applying the settings.
14. Click Next.
After a "Kudos! 7pace Timetracker is configured and ready to go" message, you will see the following screen:
15. Click the Finish button to close the wizard.
Timetracker 3 | Configuration Guide
Since the 7pace Timetracker for TFS 3.0 release is built on a different framework than versions before it, the way the data is stored in the database and represented on the user interface has changed. If you are upgrading from Timetracker 3 to Timetracker 4, since the same database is used for both, you won't have to migrate your data; the database is changed silently. If you are upgrading from Timetracker 2.8 to Timetracker 4, after your settings are applied during the configuration process, you will need to then go to %programfiles(x86)%\7pace\Timetracker\Tools\TimetrackerOnline.MigrationTool.exe to manually migrate your data. (For more information, as well as how to migrate your data at a later time, see 7pace Timetracker for TFS Configuration Tool: Making Configuration Changes.)
Following installation of 7pace Timetracker, the configuration tool wizard will then guide you through the migration process using default settings (the "same Microsoft SQL as Team Foundation Server" selection is the default). However, if you require a custom configuration, you would select "Use Custom SQL server configuration" during the wizard selection process, which would then provide options for you to choose the TFS server from which to migrate your data.
1. After you kick off the manual process, the "Welcome!" page of the 7pace Timetracker Configuration wizard displays.
2. Click the Next button to continue.
The wizard detects the local Team Foundation Server on which you have installed 7pace Timetracker and displays your TFS URL.
3. Choose one of the required options from the following selections:
Install on local machine along with Team Foundation Server: 7pace Timetracker is installed on the local system where Team Foundation Server is also installed.
Install locally and integrate with remote Team Foundation Server: 7pace Timetracker is installed on the local system but integrated with the remote Team Foundation Server.
4. Click the Next button.
The system displays the "Database Settings (Microsoft SQL Server)" page.
Note: On the "Database Settings (Microsoft SQL Server)" page, the option to select the same Microsoft SQL Server as TFS is disabled if you are configuring your 7pace Timetracker with remote TFS. In that case, you will need to specify the SQL Server details.
5. Check that the database server name and authentication details are correct and click the Next button.
The system displays the "Internet Information Server (IIS) Settings" page.
Note: 7pace Timetracker is using the same technology as TFS and we put a security cookie into every request. This cookie can, in some cases, interfere with the TFS cookie. Having Timetracker on the same domain as TFS can cause cookies to be overridden. The solution is to the change address of Timetracker to something distinct/different from the TFS address.
6. Check that the "Host Name" and "Network Host Port" are correct.
Note: The HTTPS Certificate drop-down list only appears if you are using secured http (that is, 'https'). The configuration tool only looks for certificates in the Web Hosting store. If the certificate is stored in a personal or alternative store, it will not be listed.
7. Click the HTTPS Certificate drop-down list and select the certificate that you want to use.
8. Click the Build-in-Account drop-down list, and select the application pool account or click the Custom Account and specify the custom account details.
9. Click the Next button.
The system displays the "Service Account" page.
Here, you can configure the "Service Account" (found in the "Configuration" tab of 7pace Timetracker, under "Settings") to display data that is usually not visible to all users. You can either enter the details for a "Custom Service Account" (we recommend that you use a team member who belongs to the Project Collection "Administrators" user group, since this has the highest permission level), or use the same account that you configured as the Application Pool Account. Alternatively, you can also opt not to configure the "Service Account".
10. Enter a valid username, including the domain name, if necessary.
11. Enter a valid password for the specified username.
12. Click the Next button to continue.
The tool starts applying the settings.
IMPORTANT: If you are upgrading from 7pace Timetracker 3 to 7pace Timetracker 4, since the same database is used for both, you won't have to migrate your data; the database is changed silently. If you are upgrading from 7pace Timetracker 2.8 to 7pace Timetracker 4, after your settings are applied during the configuration process, you will need to then go to %programfiles(x86)%\7pace\Timetracker\Tools\TimetrackerOnline.MigrationTool.exe to manually migrate your data.
Related Articles:
Comments
0 comments
Please sign in to leave a comment.