TestTrack

Installation Guide
Version 2012

Copyrights
2012 Seapine Software, Inc. All rights reserved.
QA Wizard Pro, Seapine CM, SoloBug, SoloSubmit, Surround SCM, and TestTrack are trademarks or registered trademarks of Seapine Software, Inc. in the United States and other countries. Borland and StarTeam are trademarks or registered trademarks of Borland, Inc. in the United States and other countries. Delphi and JBuilder are trademarks or registered trademarks of Embarcadero Technologies, Inc. in the United States and other countries. Acrobat Reader is a registered trademark of Adobe, Inc. in the United States and other countries. Sun, JVM, Java, JavaScript, and all Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Limited. Apple, Mac, Mac OS, Macintosh, Objective-C, and Safari are registered trademarks of Apple Computer, Inc. Microsoft, Windows, Windows NT, Windows Server, Windows Vista, MS Windows, Active Directory, Internet Explorer, Outlook, SQL Server, Visual SourceSafe, and Visual Studio are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Linux is a trademark of Linus Torvalds. Red Hat, Red Hat Enterprise Linux, and Fedora are the registered trademark of Red Hat, Inc. in the United States and other countries. SUSE is the registered trademark of Novell Inc. in the United States and other countries. Debian is a registered trademark of Software in the Public Interest, Inc. Ubuntu is a registered trademark of Canonical Ltd. IBM, ClearCase, and all other IBM brand and product names are service marks, trademarks or registered trademarks of IBM Corporation or its subsidiaries in the United States and other countries. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. PVCS, Serena PVCS Professional Suite, and Serena PVCS Version Manager are registered trademarks of Serena Software, Inc. All other product names mentioned herein are the trademarks of their respective owners. All other trademarks are the property of their respective owners. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language in any form by any means without the written permission of Seapine Software, Inc. Your license agreement with Seapine Software, Inc., which is included with the product, specifies the permitted and prohibited uses of the product. Any unauthorized duplication or use of this software, in whole or in part, in print, or in any other storage and retrieval system is forbidden. Information in this document is subject to change without notice and does not represent a commitment on the part of Seapine Software, Inc. Unless otherwise noted, all companies, products, street addresses, and persons contained herein are purely fictitious. Mention of third-party companies and products is for informational purposes only and does not constitute an endorsement.

Seapine Software, Inc. 5412 Courseview Drive, Suite 200 Mason, OH 45040 (513) 754-1655 documentation@seapine.com

Contents
TestTrack Installation Overview
About TestTrack databases About upgrade installations About web installations About the 64-bit TestTrack Server About automatic client upgrade installers

1
1 1 2 2 3

Before You Install

System requirements Installation types Installers

5
5 5 6

Installing TestTrack
Running the installer Setting TestTrack configuration options Selecting add-in options Setting CGI configuration options Setting SOAP server configuration options Setting the short date format (Unix only) Setting Seapine License Server configuration options

7
7 7 8 9 10 10 10

After Installing
Starting the Seapine License Server Starting Seapine License Server Admin Utility Configuring a Seapine License Server connection Adding licenses Adding users Starting the TestTrack Server Starting the TestTrack Server Admin Utility Configuring a TestTrack Server connection Starting TestTrack Moving TestTrack projects

13
13 13 14 14 14 15 15 15 16 16

Configuring TestTrack Web Installations

About distributed TestTrack web installations Configuring IIS 7 for TestTrack Web Configuring IIS 6 for TestTrack Web Configuring IIS 5 for TestTrack Web

19
19 20 21 23

Configuring Apache Installing the TestTrack URL Redirector

24 24

Configuring Web Servers for the Seapine License Server Web Admin Utility
Configuring Apache for the license server admin utility Configuring Microsoft IIS 7 for the license server admin utility Configuring Microsoft IIS 5 and 6 for the license server admin utility

25
25 25 27

Troubleshooting Setting Up RDBMSDatabases

Setting up PostgreSQLdatabases Setting up Oracle databases Setting up SQL Server databases Troubleshooting RDBMS connections

29 33
33 33 35 35

Appendix A: Microsoft Windows Security Issues Appendix B: Third-Party Software Licenses Index

39 41 45

ii

TestTrack Installation Overview

In general, there are three steps to install TestTrack: 1. Preparation tasks to complete before running the installer, such as checking system requirements. 2. Installation tasks to perform while running the installer, such as selecting the components to install and setting configuration options. 3. Configuration tasks to complete after running the installer, such as configuring server connections and adding licenses. When you install TestTrack, TestTrack Pro, TestTrack RM, and TestTrack TCM are installed. User access to each product is controlled by licenses. For example, if a user does not have a valid TestTrack Pro license, they cannot access TestTrack Pro functionality. Each TestTrack license also includes a license for the SOAP-based SDK.

About TestTrack databases

By default, TestTrack uses SQLite as the native backend database, which does not require any additional configuration before or after installation. Each TestTrack Server has a server database, which stores configuration information for the TestTrack Server. Each TestTrack project is stored in its own database. Project databases contain all project information, including issues, requirements, requirement documents, test cases, test runs, local customers and users, filters, test configurations, security groups, and reports. After you install TestTrack, you can convert the server database and project databases from TestTrack native format to a different RDBMS format. Oracle, PostgreSQL, and SQL Server are supported. See Setting Up RDBMSDatabases, page 33.

About upgrade installations

You should always create backup copies of the TestTrack Server database, the Seapine License Server database, and TestTrack projects before installation.
n

The TestTrack Server database, the Seapine License Server database, and TestTrack projects are all upgraded. The server databases are automatically upgraded when the servers start. TestTrack can automatically upgrade projects when the server starts or you can manually upgrade them. If you are upgrading the 32-bit TestTrack Server to the 64-bit server application, make sure the server database and legacy TestTrack 2011.1 and earlier native projects are upgraded or converted to RDBMS format first. See About the 64-bit TestTrack Server, page 2. You may be prompted to overwrite existing files, including SOAP or HTML files, during installation. You should always overwrite these files to ensure that TestTrack works correctly after the upgrade is complete.

Automatically upgrading projects

n

When the TestTrack Server starts, you are prompted to automatically upgrade projects. TestTrack native projects are upgraded individually. Other projects in the same database, including inactive projects, are all upgraded at the same time. After projects are upgraded, they are automatically loaded

Ab ou t we b in st al l at ion s

and available to users. Errors are logged if project upgrades fail.

n

Projects are upgraded in the order they are displayed in the Projects list in the TestTrack Server Admin Utility. If you have a large number of projects, you may want to reorder them before upgrading to make sure the most frequently used projects are upgraded first. To reorder projects, in the TestTrack Server Admin Utility, choose View > Projects. Select a project and click Top, Move Up, Move Down, or Bottom to move it. Existing TestTrack users with usernames and valid, non-expired licenses are automatically migrated as global users to the Seapine License Server. Users without usernames are converted as local users.

Manually upgrading projects

You may want to manually upgrade projects using the TestTrack Server Admin Utility if:
n n

You have a large number of projects and do not want to upgrade all of them at once. You are going to upgrade legacy TestTrack 2011.1 or earlier native projects or convert them to a different RDBMS format. You can upgrade and convert projects in one step. See 'Converting projects' in the TestTrack Server Admin Guide (http://downloads.seapine.com/pub/docs/ttserveradminguide.pdf) for information. You want to manually resolve user conflicts. If you use TestTrack and Surround SCM, and users are set up differently, there may be conflicts caused by data differences on the servers. Manually upgrading projects gives you more control over conflict resolution. For example, users were configured using full names (e.g., Deborah) in Surround SCM and using nicknames (e.g., Debbie) in TestTrack. When you manually upgrade, you can select the name you want to use.

Note: You must manually upgrade projects if you use the Linux command line (Perl) installer.

About web installations

TestTrack Pro Web, TestTrack TCM Test Runner, and the TestTrack Web Server Admin Utility use a set of HTML files and CGI scripts. A web server is required to host the HTMLfiles and execute the scripts. The scripts connect to the TestTrack Server using a TCP/IP connection. TestTrack web components are installed when you perform server or custom installations. After installation, you need to perform additional configuration on the web server before users can log in using the web clients. See Configuring TestTrack Web Installations, page 19.

About the 64-bit TestTrack Server

The 64-bit version of the TestTrack Server lets the server computer access more RAM, which increases the size and number of projects you can store on a server.
n

Only the TestTrack Server and TestTrack Registry Utility are supported on 64-bit systems. A 64-bit TestTrack Client application is not available. 32-bit clients can communicate with the 64-bit TestTrack Server and vice versa.

Ab ou t au t omat ic cl ie n t u p gr ad e in st al l e r s

The 64-bit TestTrack Server is packaged in separate installers for Windows and Linux. See Installers, page 6. The 64-bit installers also include the 64-bit Seapine License Server. See the Seapine License Server Admin Guide (http://downloads.seapine.com/pub/docs/licenseserveradmin.pdf) for information about installing the 64-bit license server. The 64-bit TestTrack Server has different system requirements than the 32-bit server. Make sure the server computer meets the recommended system requirements. See the TestTrack Server System Requirements knowledgebase article (www.seapine.com/kb/questions/1306).

New installations
If you are performing a new 64-bit TestTrack Server installation, a TestTrack native server database is created automatically the first time you start the server. Refer to the TestTrack Server Admin Guide for information about configuring the server database. See the Installing the 64-bit TestTrack Server knowledgebase article (www.seapine.com/kb/questions/1492) for additional installation information. Note: The 64-bit TestTrack Server and the 32-bit server are installed in the same directory on Linux. Separate application directories are created on Windows. Do not install the 64-bit server application in the same directory as the 32-bit server on Windows.

Upgrade installations
If you are upgrading from a 32-bit TestTrack Server, you must perform the following steps before you install the 64-bit server. See the Migrating from the 32-bit Server to the 64-bit Server on the Same Computer knowledgebase article (www.seapine.com/kb/questions/1482). 1. Create backup copies of the TestTrack Server database and projects. 2. The 64-bit server supports TestTrack Server databases and projects stored in TestTrack native (SQLite) or RDBMS format. Information about supported platforms and databases is available in the TestTrack RDBMS Support knowledgebase article (www.seapine.com/kb/questions/1527). If the TestTrack Server database is a legacy 2011.1 or earlier native database, upgrade it using the TestTrack Server Admin Utility. 3. Upgrade or convert all legacy TestTrack2011.1 or earlier native projects that will be stored on the 64bit server using the TestTrack Server Admin Utility. Refer to the TestTrack Server Admin Guide for information about converting server databases and projects. Note: After upgrading in Windows, you need to move the TTServDb directory from the 32-bit TestTrack application directory to the 64-bit directory. By default, the 32-bit TestTrack application directory is in C:\Program Files (x86)\Seapine\TestTrack and the 64-bit directory is stored in C:\Program Files\Seapine\TestTrack.

About automatic client upgrade installers

TestTrack includes client installer packages that are used for automatic client upgrades. These packages are installed with the TestTrack Server to make cross-platform client deployment easier after server upgrades. When users try to connect to the TestTrack Server with an older client version, they are notified to upgrade the client to the newer version.

Ab ou t au t omat ic cl ie n t u p gr ad e in st al l e r s

The Windows, Mac, and Linux automatic client upgrade installer packages are installed in the installers folders in the default TestTrack directory. Note: You can enable and disable automatic TestTrack Client upgrade using the TestTrack Server Admin Utility. Refer to the TestTrack Server Admin Guide for information about setting server options.

Before You Install

Before installing TestTrack, take the time to determine the options you need to select during installation. Keep the following in mind:
n

Make sure all TestTrack and Seapine License Server client and server applications are shut down on the computer you are installing on. If you use Surround SCM, the Seapine License Server and Seapine License Server Admin Utility may already be installed on your network. Check with the Surround SCM administrator.

System requirements
Review the following knowledgebase articles to check system requirements for the TestTrack Client and TestTrack Server.
n n

TestTrack Client System Requirements (www.seapine.com/kb/questions/1408) TestTrack Server System Requirements (www.seapine.com/kb/questions/1306)

Installation types
Installation type TestTrack Client installation TestTrack Server installation Installs TestTrack Client and SoloBug Notes Most users only need to install the client.

TestTrack Server, TestTrack Client, TestTrack Server Admin Utility, Seapine License Server, Seapine License Server Admin Utility, SoloBug, and a sample project TestTrack Server, TestTrack Client, TestTrack Server Admin Utility, TestTrack web clients, TestTrack Web Server Admin Utility, TestTrack Published Data Server, Seapine License Server, Seapine License Server Admin Utility, SoloSubmit, and a sample project TestTrack Server, TestTrack Client, TestTrack Server Admin Utility, TestTrack web clients, TestTrack Web Server Admin Utility, TestTrack Published Data Server, TestTrack SOAP Server, Seapine License Server, Seapine License Server Admin Utility, SoloSubmit, and a sample project

The server application is generally installed on a networked computer.

TestTrack Server installation with web components

A web server must be installed on the computer before installation. See Configuring TestTrack Web Installations, page 19.

TestTrack Server installation with web and SOAP components

A web server must be installed on the computer before installation. See Configuring TestTrack Web Installations, page 19.

In st al l e r s

Installation type Seapine License Server

Installs Seapine License Server, Seapine License Server Admin Utility, Seapine License Server Web Admin Utility

Notes A web server must be installed on the computer before installation if you are also installing the web admin utility. See Configuring TestTrack Web Installations, page 19. A web server must be installed on the computer before installation. See Configuring Web Servers for the Seapine License Server Web Admin Utility, page 25.

Seapine License Server Web Admin Utility

Seapine License Server Web Admin Utility

Custom installation

Components you select

Installers
Platform Windows Installation program Complete Client-only 64-bit TestTrack Server and Seapine License Server Mac OS X Complete Client-only Linux Complete (Java) Complete (Perl) Client-only 64-bit TestTrack Server and Seapine License Server (Java) 64-bit TestTrack Server and Seapine License Server (Perl) File name ttwininstall.exe ttwinclientinstall.exe ttwininstall64.exe ttmacosxinstall.dmg.gz ttmacclientinstall.dmg.gz ttlinuxjavainstall.tar.gz ttlinuxinstall.tar.gz ttlinuxclientinstall.tar.gz ttlinuxjavainstall64.tar.gz ttlinuxinstall64.tar.gz

Note: Java 1.4 is required to use the Linux Java installers. Use the Perl command line installer if you do not have Java 1.4.

Installing TestTrack
The TestTrack installation program installs TestTrack Pro, TestTrack RM, and TestTrack TCM. User access to each product is controlled by licenses. You must select settings for the TestTrack components you decide to install. The following steps apply to the TestTrack Server installation with web and SOAP components. You may be prompted for different information depending on the type of installation you perform.

Running the installer

n n

WindowsDouble-click the installation file. MacGunzip the installation file to extract the installer and then double-click ttmacosxinstall.dmg to mount the image on the desktop. Double-click the TestTrack disk image and then double-click the Install TestTrack icon. Linux graphical installerUntar and gunzip the installation file and then log in as root and doubleclick the installer file in the Window Manager. Linux command line installerUntar and gunzip the installation file, change (cd) to the TestTrack directory, and then enter .install.pl to run the install script. Press Enter to accept the default options. Press Ctrl+C to cancel the installation.

Setting TestTrack configuration options

You must select a TestTrack application directory. The Mac and Linux installers also require you to select a directory for creating the Startup.log file, which contains errors that are logged when the TestTrack Server starts. You can use the default directory or select a different directory. Additional configuration options include setting the server port number and choosing a server execution mode (Windows only).

S e l e ct in g ad d -in op t ion s

Default installation directories

Installer Windows Files All files Default directory C:\Program Files\Seapine\TestTrack /Applications/TestTrack

Mac

Client executable programs, server database, documentation, stylesheets, lexicons, stylesheets, and other supporting files Startup.log file Other executable Unix programs, shell scripts, and TestTrack Server daemon

/var/log /usr/bin

Linux

Client executable programs, server database, documentation, stylesheets, lexicons, stylesheets, and other supporting files Startup.log file Other executable Unix programs, shell scripts, and TestTrack Server daemon

/var/lib/TestTrack

/var/log /usr/bin

Server execution mode (Windows only)

You can choose to run the TestTrack Server as a service if you want the server to automatically start when the computer starts. You must configure the TestTrack service to log in as the Local System Account. If you run the server as an application, you must manually start the TestTrack Server application.

Server port
The TestTrack Server communicates with TestTrack clients on this port. Use the default port number or enter another number. Platform Windows Unix Default port 99 1566

Selecting add-in options

If Visual Studio is installed on your computer, you can install an add-in to integrate it with TestTrack. Select the versions you want to integrate with TestTrack. If Microsoft Outlook is installed, you can install an add-in to create new TestTrack issues, requirements, or test cases from emails or add emails to existing items. Close Outlook before installing TestTrack.

S e t t in g CGI con figu r at ion op t ion s

Setting CGI configuration options

If you are installing the TestTrack CGIs, you must select a location to install the CGI scripts and HTML files and set the TestTrack Server address and port number. When TestTrack Pro Web, TestTrack TCM Test Runner, or TestTrack Web Server Admin Utility users log in, the web server calls the appropriate CGI, which communicates with the TestTrack Server. Note: If you are installing the Seapine License Server Web Admin Utility, you must set a location to install the CGI scripts and HTML files. See Setting Seapine License Server configuration options, page 10.

Web server types

Microsoft IIS and Apache web servers are supported. See TestTrack Supported Web Servers (www.seapine.com/kb/questions/1333) for supported versions.

Default HTML file installation directories

Select the directory where you want to install the HTML files used by TestTrack web clients. Note: If you are upgrading, you may be prompted to overwrite existing HTML files during installation. You should always overwrite these files to ensure that TestTrack works correctly after the upgrade is complete. Web server Platform IIS Apache Windows Windows Mac Linux Default HTML files directory C:\inetpub\wwwroot C:\Program Files\Apache Software Foundation\Apache <version>\htdocs /Library/WebServer/Documents /var/www/html

TestTrack Server address and port

Enter a static IP address or domain name and port number of the TestTrack Server computer. The TestTrack CGIs use this information to communicate with the TestTrack Server. You are only prompted to enter this information the first time you install TestTrack. Platform Windows Unix Default server port 99 1566

S e t t in g S OAP se r ve r con figu r at ion op t ion s

Default CGI installation directories

Select the directory where you want to install the CGI scripts. The web server must have access to this directory. Web server IIS Apache Platform Windows Windows Default logical CGI directory name scripts cgi-bin Default CGI scripts directory C:\inetpub\scripts C:\Program Files\Apache Software Foundation\Apache <version>\cgi-bin /Library/WebServer/CGI-Executables /var/www/cgi-bin

Mac Linux

cgi-bin cgi-bin

Setting SOAP server configuration options

Enter the IP address or domain name of the computer that is hosting the SOAP CGI and the port number. The default port is 80.

Setting the short date format (Unix only)

On Linux and Mac OS X, you can set the short date format used for reports, email notifications, and the startup log file, and any other date string created by the TestTrack Server. Valid date formats include: %m/%d/%y, %d/%m/%y, %b/%d/%y, or %d/%b/%y. You can substitute %b with %B or %y with %Y in these formats. The year parameter must be last in the date format. Valid delimiters include a period, dash, forward slash, backward slash, comma, or a space. Character Description %b %B %d %m %y %Y Abbreviated month name Full month name Day of the month, 01-31 Month of the year, 01-12 Two-digit year Four-digit year Example Mar March 22 03 99 1999

Setting Seapine License Server configuration options

You must select a Seapine License Server application directory. The Mac and Linux installers also require you to select a directory for creating the LSStartup.log file, which contains errors that are logged when the server starts. You can use the default directory for these options or select a different directory.

10

S e t t in g S e ap in e Lice n se S e r ve r con figu r at ion op t ion s

Additional configuration options include setting the server port number, choosing a server execution mode (Windows only), and setting the web server admin utility CGI and HTML file locations.

Default installation directories

Platform Windows Files installed All files Default directory C:\Program Files\Seapine\License Server /Applications/Seapine License Server /var/log /usr/bin

Mac

Seapine License Server Admin Utility executable, server database, documentation, and other supporting files LSStartup.log file Other executable Unix programs, shell scripts, and the Seapine License Server daemon

Linux

Application LSStartup/log file Other executable Unix programs, shell scripts, and the Seapine License Server daemon

/var/lib/splicsvr /var/log /usr/bin

Web server admin utility CGI and HTML file installation directories
If you are installing the Seapine License Server Web Admin Utility, you must set a location to install the CGI scripts and HTML files. Microsoft IIS and Apache web servers are supported. See Seapine License Server Supported Web Servers (www.seapine.com/kb/questions/1658) for supported versions. Web server IIS Apache Platform Windows Windows Default CGI directory C:\inetpub\scripts C:\Program Files\Apache Software Foundation\Apache <version>\cgi-bin /Library/WebServer/CGI-Executables /var/www/cgi-bin Default HTML files directory C:\inetpub\wwwroot C:\Program Files\Apache Software Foundation\Apache <version>\htdocs /Library/WebServer/Documents /var/www/html

Mac Linux

Server execution mode (Windows only)

You can choose to run the Seapine License Server as a service if you want the server to automatically start when the computer starts. If you run the server as an application, you must manually start the Seapine License Server application.

11

S e t t in g S e ap in e Lice n se S e r ve r con figu r at ion op t ion s

Server port
The Seapine License Server communicates with TestTrack clients on this port. Use the default port number (5100) or enter another number.

12

After Installing
After TestTrack is installed, an administrator or another high-level user needs to perform the following tasks:
n n n n n

Configure a Seapine License Server connection Add licenses and users to the Seapine License Server Configure a TestTrack Server connection Create a project Retrieve global users from the Seapine License Server and create security groups

After an upgrade installation, existing projects must be upgraded to the current format. See About upgrade installations, page 1. After a web installation, the web server needs to be configured before users can access TestTrack using web clients. See Configuring TestTrack Web Installations, page 19. Note: During installation, an administrative user with full admin security rights is created. To log in as this user, enter Administrator as the username. A password is not required. If you want to create a different admin user, you can delete this user. If you do not want to delete this user, you should add a password to prevent unauthorized users from logging in to the admin account.

Starting the Seapine License Server

The Seapine License Server must be running before the TestTrack Server is started.
n

WindowsIf you chose to run the license server as a service, it starts automatically. If you chose to run the license server as an application, you have to start it yourself. Choose Programs > Seapine Software > Seapine License Server > Seapine License Server from the Start menu. MacClick Seapine License Server in the System Preferences. If you want to set the server to start automatically, click the lock button and select Start Seapine License Server when this computer starts up. LinuxEnter /usr/bin/spls start

Starting Seapine License Server Admin Utility

The Seapine License Server Admin Utility provides a convenient way to manage global users and customers. Managing users and customers from one central location reduces the time spent on administrative tasks and allows you to quickly assign licenses.
n

WindowsChoose Programs > Seapine Software > Seapine License Server > Seapine License Server Admin on the Start menu. MacDouble-click the Seapine License Server Admin Utility icon in the Applications/Seapine License Server folder. LinuxEnter /usr/bin/lsadmin

13

Con figu r in g a S e ap in e Lice n se S e r ve r con n e ct ion

WebIn a web browser, enter the server admin utility URL. The URL uses the static or IP address of the web server hosting the admin utility and the path to the admin utility files. For example, http://www.yourserver.com/lsweb/admin.

Configuring a Seapine License Server connection

Before you can access a server, you need to add the server connection information. Note: Steps 1-6 may not be necessary if you installed the TestTrack Server and the Seapine License Server on the same computer using the default port configurations. 1. Start the Seapine License Server and the Seapine License Server Admin Utility. 2. Click Setup on the login dialog box if the Setup Server Connections dialog box does not open automatically. 3. Click Add to add a server connection. 4. Enter a Server Name, Server Address, and Port. 5. Click OK to add the server connection. 6. Click Close in the Setup Server Connections dialog box to return to the Seapine License Server Login dialog box. 7. Log in as the default administrative user and click Connect. The username is Administrator and there is no password. By default, the Administrator user has full admin security rights and uses a TestTrack floating license. We strongly recommend setting a password for this user to prevent unauthorized user access.

Adding licenses
1. Click Licenses in the License Server Admin Utility dialog box. 2. Click Add and enter the license serial number or click Browse to select a license file. This field is case sensitive. Licenses can be entered with or without dashes. 3. Click OK to add the license.

Adding users
1. Click the Global Users in the License Server Admin Utility dialog box. 2. Click Add. 3. Enter the user's contact information, username and password, security rights, and licenses. 4. Click Add to add the user to the Global Users list. Note: Global users can be shared by TestTrack and Surround SCM. 5. Close the Seapine License Server Admin Utility.

14

S t ar t in g t h e Te st Tr ack S e r ve r

You are prompted to change the communications and Administrator passwords. We strongly recommend changing these passwords to prevent unauthorized user access.

Starting the TestTrack Server

n

WindowsIf you chose to run the TestTrack Server as a service, it starts automatically. If you chose to run the server as an application, you have to start it yourself. Choose Programs > Seapine Software > TestTrack > TestTrack Server from the Start menu. MacClick TestTrack in the System Preferences. If you want to set the server to start automatically, click the lock button and select Start TestTrack Server when this computer starts up. LinuxEnter /usr/bin/ttstudio start

Starting the TestTrack Server Admin Utility

The TestTrack Server Admin Utility is used to manage projects, the server log, server users, the mail queue, and server options.
n

WindowsChoose Programs > Seapine Software > TestTrack > TestTrack Server Admin on the Start menu. MacDouble-click the TestTrack Server Admin Utility icon in the Applications/TestTrack folder. LinuxEnter /usr/bin/ttadmin WebIn a web browser, enter the server admin utility URL. The URL uses the static or IP address of the web server you want to connect to and the path to the admin utility login page. For example, http://www.yourserver.com/ttweb/ttadmin/adminlogin.htm. If the login dialog box does not open automatically, click Go To Login on the Welcome page.

n n n

Configuring a TestTrack Server connection

You need to configure a TestTrack Server connection and create at least one project before users can log in to TestTrack. 1. Start the TestTrack Server and TestTrack Server Admin Utility. 2. Click Setup on the login dialog box if the Setup Server Connections dialog box does not open automatically. 3. Click Add to add a server connection. 4. Enter a Server Name, Server Address, and Port Number. 5. Click OK to add the server connection. 6. Click Close in the Setup Server Connections dialog box to return to the TestTrack Admin Utility Login dialog box. 7. Log in as the default administrative user and click Connect. The username is Administrator and there is no password. 8. Click Projects and create at least one project. See the TestTrack Server Admin Utility Guide for information. 9. Close the TestTrack Server Admin Utility when you finish adding projects.

15

S t ar t in g Te st Tr ack

Note: Before users can access a TestTrack project, you must retrieve the users from the license server to the project and add them to at least one security group using the TestTrack Client. See the TestTrack User Guide for information.

Starting TestTrack
n

WindowsChoose Programs > Seapine Software > TestTrack > TestTrack Client on the Start menu. MacDouble-click the TestTrack Client icon in the Applications/TestTrack folder. LinuxEnter /usr/bin/ttclient TestTrack Pro WebIn a web browser, enter the TestTrack Pro Web URL. The URL uses the server name or IP address of the web server hosting the project and the path to the login page. For example, http://www.yourserver.com/ttweb/login.htm. If the login dialog box does not open automatically, click Go To Login on the Welcome page. If the dialog box still does not open, disable any pop-up blocker software you are running and try again. TestTrack TCM Test RunnerIn a web browser, enter the Test Runner URL. The URL uses the server name or IP address of the web server hosting the project and the path to the login page. For example, http://www.yourserver.com/ttweb/tcmlogin.htm.

n n n

When the application starts, select the Server you want to connect to, enter a Username and Password, and click Connect. Select a Project and click OK.

Moving TestTrack projects

After installation, you may want to move existing TestTrack projects. You can move projects to another computer using a network connection, a ZIP drive, or an FTP connection. Keep the following in mind:
n

If you are upgrading TestTrack, you can upgrade projects in the existing location or in the new location. If you upgrade projects in the existing location, you should wait to move the projects to the new location until you are sure the upgrade is successful. The TestTrack project database file structure is the same on all operating systems. No special conversion is necessary. On Linux, data files in the /var/lib/testtrack directory must be owned by root. These files have a .TTT, .TTI, or .FPT extension. The TestTrack data file naming convention is case sensitive and requires all upper case (e.g., ISSUES.TTT). These files need read-write permissions to save data.

Note: The following information only applies to TestTrack 6.0 and later, and the TestTrack native database format. 1. Install TestTrack and the Seapine License Server in the new location. 2. In both locations, stop the TestTrack Server and the Seapine License Server. It is important to stop the servers in the old location to make sure the projects are not being written to when they are moved. 3. In the old location, make a backup copy of the LicenseServDb directory and all subdirectories in the Seapine License Server application directory.

16

M ovin g Te st Tr ack p r oje ct s

4. In the old location, make a backup copy of the TTDbs directory and all subdirectories in the TestTrack application directory. 5. Copy the LicenseServDb directory and all subdirectories in the old location to the Seapine License Server application directory in the new location. 6. Copy the TTDbs directory and all subdirectories in the old location to the TestTrack application directory in the new location. 7. Start the Seapine License Server in the new location. 8. Start the TestTrack Server in the new location. Note: If you have trouble connecting to the projects in the new location, see the Moving TestTrack Databases and Projects knowledgebase article (www.seapine.com/kb/questions/1232).

17

Configuring TestTrack Web Installations

TestTrack Pro Web, TestTrack TCM Test Runner, and the TestTrack Web Server Admin Utility require a web server to host the HTML files and execute the CGI scripts. The CGI scripts connect to the TestTrack Server using a TCP/IP connection. The TestTrack web components are installed during server or custom installations. After installation, you need to configure the web server before users can log in using the web clients. See the TestTrack Supported Web Servers knowledgebase article (www.seapine.com/kb/questions/1333) for a list of supported web servers. Note: TestTrack web users may need to install the TestTrack URL Redirector to access ttstudio hyperlinks. See Installing the TestTrack URL Redirector, page 24.

About distributed TestTrack web installations

You can install the TestTrack Server on the same computer as the web server or another computer as long as they are located in the same network. If you have a large TestTrack installation, you may want to host multiple TestTrack Servers on multiple computers running against one or more web servers. Regardless of the configuration, when a user accesses the TestTrack CGIs, the CGIs safely and securely communicate with the TestTrack Server behind your firewall. Distributed installations provide the following benefits:
n

Enhanced securityHosting the TestTrack web components on one computer and data on another computer provides more security. A hacker who accesses your web server will not have access to any TestTrack data. Better performanceSeparating the web server and the TestTrack Server lets you split up the workload, increasing the performance of both server computers. Using multiple TestTrack Servers on different computers can improve performance even more. In addition, SoloSubmit can be installed on up to 10 additional web servers, which allows customers to access separate SoloSubmit URLs while submitting issues and requests to the same server or project. Greater flexibilityTestTrack web users can log in to all TestTrack Servers hosted by the web server simultaneously. All projects the user has access to are displayed in the Projects list.

Perform the following steps to configure a distributed TestTrack web installation: 1. Install the TestTrack Server, Client, and Server Admin Utility on the computer that will host the TestTrack Server and projects. 2. Install the TestTrack web and CGI components on the computer that will host the web components. 3. Configure the web server for TestTrack. 4. To provide access to multiple TestTrack Servers from a single web server, configure the CGIs to connect to the TestTrack Servers. See the TestTrack Registry Utility Guide (http://downloads.seapine.com/pub/docs/ttregistryutilityguide.pdf) for information.

19

Con figu r in g IIS 7 for Te st Tr ack We b

Configuring IIS 7 for TestTrack Web

After you install the TestTrack web components, you need to configure the web server before users can log in to TestTrack web clients. Refer the IIS documentation for information about enabling CGI execution and authentication.

Enabling support for CGI executables

Windows Vista and Windows 7
1. Choose Start > Control Panel > Programs and Features. 2. Click Turn Windows features on or off in the Tasks pane. 3. Expand the Internet Information Services, World Wide Web Services, and Application Development Features nodes. 4. Select CGIand Server-Side Includes. 5. Click OK.

Windows Server 2008

1. Choose Start > Control Panel > Programs and Features. 2. Click Turn Windows features on or off in the Tasks pane. 3. Click Roles in the left pane. 4. Click Add Role Services in the right pane. 5. Expand the Web Server and Application Development Features nodes. 6. Select CGI and Server-Side Includes. 7. Click OK.

Creating a CGI directory alias

1. Open IIS Manager. 2. In the Connections pane, expand the Web Sites node. 3. Right-click the default web site or the site used for TestTrack and choose Add Virtual Directory. 4. Enter 'scripts' as the Alias. 5. Enter the path to the ttcgi.exe as the Physical Path. This is the path entered during the TestTrack installation. The default path is C:\inetpub\scripts. 6. Click OK.

Enabling the .exe CGI extension

1. Click the scripts virtual directory in the Connections pane. 2. Double-click Handler Mappings. 3. Click Add Module Mapping in the Actions pane.

20

Con figu r in g IIS 6 for Te st Tr ack We b

4. Enter '*.exe' as the Request path. 5. Select CgiModule as the Module. 6. Enter 'ttcgi' as the Name. 7. Click OK. 8. Select the server computer in the Connections pane. 9. Double-click ISAPI and CGI Restrictions. 10. Click Add in the Actions pane. 11. Enter the path to the ttcgi.exe program as the ISAPI or CGI path. This is the path entered for the ttcgi.exe program during the TestTrack installation. The default path is C:\inetpub\ttcgi.exe. 12. Enter 'ttcgi' as the Description. 13. Select Allow extension path to execute. 14. Click OK. 15. Repeat steps 8 through 14 for ttadmcgi.exe.
n n

If you use SOAP, repeat the steps to add ttsoapcgi.exe. If you use TestTrack TCM Test Runner, repeat the steps to add tttcmcgi.exe.

Enabling the .ttp CGI extension

Note: The following steps are only required if you use TestTrack TCM TestRunner. 1. Click the server computer in the Connections pane. 2. Double-click Handler Mappings. 3. Click Add Module Mapping in the Actions pane. 4. Enter '*.ttp' as the Request path. 5. Select ServerSideIncludeModule as the Module. 6. Enter the path to the tttcmcgi.exe program as the Executable. The default path is C:\inetpub\scripts. 7. Enter 'ttp files' as the Name. 8. Click Request Restrictions and select Invoke handler only if request is mapped to and the File option. 9. Click OK. Note: If you cannot log in to TestTrack web clients, see the TestTrack Web Returns a 404 - Page Not Found Error knowledgebase article (www.seapine.com/kb/questions/1257).

Configuring IIS 6 for TestTrack Web

After you install the TestTrack web components, you need to configure the web server before users can log in to TestTrack web clients. Refer the IIS documentation for information about enabling CGI execution and authentication.

21

Con figu r in g IIS 6 for Te st Tr ack We b

Creating a CGI directory alias

1. Open IIS Manager. 2. Right-click the default web site or the site used for TestTrack and choose New > Virtual Directory. 3. Follow the on-screen instructions. Enter the following information when prompted:
n n

Enter scripts as the Alias. Set the Directory to the path that was entered during the TestTrack installation for the ttcgi.exe program. The default path is C:\inetpub\scripts. Select the following Access Permissions: Read, Run scripts, Execute.

Enabling the .exe CGI extension

1. In IIS Manager, expand Web Sites and click Web Service Extensions. 2. Click Add a new Web service extension in the Web Service Extensions pane. 3. Enter 'TestTrack' as the Extension name. 4. Click Add. 5. Enter the path to the ttcgi.exe program and click OK. The default location is C:\inetpub\scripts\ttcgi.exe. 6. Select Set extension status to Allowed. 7. Click OK. 8. Repeat steps 4 through 7 for ttadmcgi.exe.
n n

If you use SOAP, repeat the steps to add ttsoapcgi.exe. If you use TestTrack TCM Test Runner, repeat the steps to add tttcmcgi.exe.

9. Click OK to save the changes.

Enabling the .ttp CGI extension and Active Server pages

Note: The following steps are only required if you use TestTrack TCM TestRunner. 1. In IIS Manager, right-click the default web site or the site used for TestTrack and choose Properties. 2. Click the Home Directory tab. 3. Click Configuration. The Application Configuration dialog box opens. 4. Click Add to create a new mapping. 5. Enter a file processor Executable path. You can use the ASP library located in C:\WINDOWS\system32\inetsrv\asp.dll or another file processor application. 6. Enter '.ttp' as the Extension. 7. Select Limit to and enter 'GET,POST' as the Verbs.

22

Con figu r in g IIS 5 for Te st Tr ack We b

8. Select Script engine and Check that file exists if they are not already selected. 9. Click OK. The .ttp extension is enabled. 10. Expand Web Sites and then click Web Service Extensions. 11. In the Web Service Extensions pane, click Active Server Pages and then click Allow. 12. Restart IIS. Note: If you cannot log in to TestTrack web clients, see the TestTrack Web Returns a 404 - Page Not Found Error knowledgebase article (www.seapine.com/kb/questions/1257/).

Configuring IIS 5 for TestTrack Web

After you install the TestTrack web components, you need to configure the web server before users can log in to TestTrack web clients. Refer the IIS documentation for information about enabling CGI execution and authentication.

Creating a CGI directory alias

1. Open IIS Manager. 2. Right-click the default web site or the site used for TestTrack and choose New > Virtual Directory. 3. Follow the on-screen instructions. Enter the following information when prompted:
n n

Enter scripts as the Alias. Set the Directory to the path that was entered during the TestTrack installation for the ttcgi.exe program. The default path is C:\inetpub\scripts. Select the following Access Permissions: Read, Run scripts, Execute.

Enabling the .ttp CGI extension

Note: The following steps are only required if you use TestTrack TCM TestRunner. 1. In IIS Manager, right-click the default web site or the site used for TestTrack and choose Properties. 2. Click the Home Directory tab. 3. Click Configuration. The Application Configuration dialog box opens. 4. Click Add to create a new mapping. 5. Enter a file processor Executable path. You can use the ASP library located in C:\WINDOWS\system32\inetsrv\asp.dll or another file processor application. 6. Enter '.ttp' as the Extension. 7. Select Limit to and enter 'GET,POST' as the Verbs. 8. Select Script engine and Check that file exists if they are not already selected.

23

Con figu r in g Ap ach e

9. Click OK. The .ttp extension is enabled. Note: If you cannot log in to TestTrack web clients, see the TestTrack Web Returns a 404 - Page Not Found Error knowledgebase article (www.seapine.com/kb/questions/1257/).

Configuring Apache
You must create a CGI directory alias on the Apache web server before users can log in to TestTrack web clients. 1. Open the httpd.conf file. 2. Search the file for ScriptAlias/cgi-bin. If the directory does not exist, add the following to the file: ScriptAlias/cgi-bin/C:\Program Files/Apache Group/cgi-bin/ Note: If you cannot log in to TestTrack web clients, see the TestTrack Returns a 404 - Page Not Found Error knowledgebase article (www.seapine.com/kb/questions/1257).

Installing the TestTrack URL Redirector

TestTrack supports ttstudio and http protocols in hyperlinks used to open items, such as issues. The TestTrack URL Redirector handles routing of ttstudio hyperlinks and determines if they are opened in the TestTrack Client or TestTrack web clients. Http hyperlinks are always opened in TestTrack web clients. By default, ttstudio hyperlinks are opened in the TestTrack Client. If the TestTrack Client is not found, the link is converted to use the http protocol and opened in TestTrack web clients. The redirector is automatically installed during TestTrack Client installations. TestTrack web users must install the redirector to open ttstudio hyperlinks. The installer can be downloaded from Seapines web site (www.seapine.com/ttresources.php).

24

Configuring Web Servers for the Seapine License Server Web Admin Utility
The Seapine License Server Web Admin Utility requires a web server to host the HTML files and execute the CGI scripts. The CGI scripts connect to the Seapine License Server using a TCP/IP connection. The Seapine License Server web components can be installed during TestTrack installation. After installation, you need to configure the web server before administrators can log in using the web admin utility. See the Seapine License Server Supported Web Servers knowledgebase article (www.seapine.com/kb/questions/1658) for a list of supported web servers.

Configuring Apache for the license server admin utility

You must create a CGI directory alias on the Apache web server before administrators can log in to the Seapine License Server Web Server Admin Utility. 1. Open the httpd.conf file. 2. Search the file for ScriptAlias/cgi-bin. If the directory does not exist, add the following to the file: ScriptAlias/cgi-bin/C:\Program Files/Apache Group/cgi-bin/

Configuring Microsoft IIS 7 for the license server admin utility

After you install the Seapine License Server Web Admin Utility files, you need to configure the web server before administrators can log in to the admin utility. Refer to the IIS documentation for information about enabling CGI execution and authentication.

Enabling support for CGI executables

Windows Vista and Windows 7
1. Choose Start > Control Panel > Programs and Features. 2. Click Turn Windows features on or off in the Tasks pane. 3. Expand the Internet Information Services, World Wide Web Services, and Application Development Features nodes. 4. Select CGI. 5. Click OK.

Windows Server 2008

1. Choose Start > Control Panel > Programs and Features. 2. Click Turn Windows features on or off in the Tasks pane.

25

Con figu r in g M icr osoft IIS 7 for t h e l ice n se se r ve r ad min u t il it y

3. Click Roles in the left pane. 4. Click Add Role Services in the right pane. 5. Expand the Web Server and Application Development Features nodes. 6. Select CGI. 7. Click OK.

Creating a CGI directory alias

1. Open IIS Manager. 2. In the Connections pane, expand the Web Sites node. 3. Right-click the default web site or the site used for the Seapine License Server Web Admin Utility and choose Add Virtual Directory. 4. Enter 'scripts' as the Alias. 5. Enter the path to the lscgi.exe as the Physical Path. This is the path entered during the admin utility installation. The default path is C:\inetpub\scripts. 6. Click OK.

Enabling the .exe CGI extension

1. Click the scripts virtual directory in the Connections pane. 2. Double-click Handler Mappings. 3. Click Add Module Mapping in the Actions pane. 4. Enter '*.exe' as the Request path. 5. Select CgiModule as the Module. 6. Enter 'lscgi' as the Name. 7. Click OK. 8. Select the server computer in the Connections pane. 9. Double-click ISAPI and CGI Restrictions. 10. Click Add in the Actions pane. 11. Enter the path to the lscgi.exe program as the ISAPI or CGI path. This is the path entered for the lscgi.exe program during the admin utility installation. The default path is C:\inetpub\scripts\lscgi.exe. 12. Enter 'lscgi' as the Description. 13. Select Allow extension path to execute. 14. Click OK.

26

Con figu r in g M icr osoft IIS 5 an d 6 for t h e l ice n se se r ve r ad min u t il it y

Configuring Microsoft IIS 5 and 6 for the license server admin utility
After you install the Seapine License Server Web Admin Utility files, you need to configure the web server before administrators can log in to the admin utility. Refer to the IIS documentation for information about enabling CGI execution and authentication.

Creating a CGI directory alias

1. Open IIS Manager. 2. Right-click the default web site or the site used for the Seapine License Server Web Server Admin Utility and choose New > Virtual Directory. 3. Follow the on-screen instructions. Enter the following information when prompted:
n n

Enter scripts as the Alias. Set the Directory to the path that was entered during the admin utility installation for the lscgi.exe program. The default path is C:\inetpub\scripts. Select the following Access Permissions: Read, Run scripts, Execute.

Enabling the .exe CGI extension

The following steps are only required for IIS 6. 1. In IIS Manager, expand Web Sites and click Web Service Extensions. 2. Click Add a new Web service extension in the Web Service Extensions pane. 3. Enter 'LSAdmin' as the Extension name. 4. Click Add. 5. Enter the path to the lscgi.exe program and click OK. The default location is C:\inetpub\scripts\lscgi.exe. 6. Select Set extension status to Allowed. 7. Click OK. 8. Click OK to save the changes.

27

Troubleshooting
If there is a problem connecting to the TestTrack Server or Seapine License Server, first check the following and try reconnecting:
n n n

Make sure the server computer is running. Check the IP address and port number. Make sure you are connected to the network, intranet, or Internet.

The Seapine License Server and TestTrack Server are not communicating
If the servers are not communicating, make sure the connections are configured correctly. 1. Start the Seapine License Server and the TestTrack Server. 2. Start the TestTrack Server Admin Utility and log in. Use the local admin password to log in if your username and password are not recognized. Leave the username blank and enter admin as the password. This password only provides access to the Seapine License Server configuration. 3. Click Server Options and select the License Server category. 4. Make sure the server address and port number are correct and click Test Connection. 5. If the connection is successful, stop and restart the TestTrack Server for the changes to take effect. 6. If the connection is not successful, check the following:
n

If the TestTrack Server and the Seapine License Server are installed on different computers, check your network and firewall configurations to open the necessary ports. Check the communications password on the TestTrack Server and Seapine License Server. The same communications password must be set on both servers. To check the password in the TestTrack Server Admin Utility, click Server Options, and then click the License Server category. To check the password in the Seapine License Server Admin Utility, click Server Options, and then click the Server category.

Users cannot access TestTrack Pro, TestTrack RM, or TestTrack TCM

Users may be able to log in to TestTrack, but may not be able to access TestTrack Pro, TestTrack RM, or TestTrack TCM functionality. Verify that the project options allow users to log in and check user licenses.

Check project options

1. Choose Tools > Administration > Project Options and select the General category. 2. Select any Login Options to allow users to log in to the project. 3. Click OK to save the changes.

29

Tr ou b l e sh oot in g

Users must restart the TestTrack Client if any changes were made. If users still cannot access functionality, make sure the correct product license is assigned.

Check licenses
1. Choose View > Users. 2. Select a user and click Edit. 3. Click the License tab. 4. Verify that user has a license for the product they cannot access. Assign a license if necessary. 5. Click OK to save the changes. Users must restart the TestTrack Client if any changes were made.

Users cannot log in to TestTrack Pro Web or TestTrack TCM Test Runner
If users cannot log into TestTrack Pro Web or TestTrack TCM Test Runner, make sure they have the security permissions to log in using the web client. 1. Choose View > Security Groups. 2. Select the user's security group and click Edit. 3. Select General in the Command Security category. 4. Verify that the Allow Login Via TestTrack Web command is selected. 5. Click OK to save the changes. 6. Retry the login.

TestTrack Pro Web or TestTrack TCM Test Runner returns a '404 Page Not Found' error
TestTrack web clients need access to the CGI directory and the CGI executables. This error usually occurs for one of the following reasons:
n n n n

The directory and executable do not exist or cannot be accessed The directory and executable location has changed The .exe extension is prohibited (IIS 6.0 only) URLScan is running (IIS only)

See the TestTrack Web Returns a 404 - Page Not Found Error knowledgebase article (www.seapine.com/kb/questions/1257) for information about resolving the error.

Server is not available in the login dialog box

To access a project, the TestTrack Client must connect to a TestTrack Server. Users need to set up a server connection if the TestTrack Server that contains the project is not available in the Server list in the login dialog box. 1. Click Setup in the TestTrack login dialog box.

30

Tr ou b l e sh oot in g

2. Click Add in the Setup Server Connections dialog box. 3. Enter a Server Name, Server Address, and Port number. Tip: If the TestTrack Server is installed on the same computer as the TestTrack Client, enter localhost or 127.0.0.1 for the server address. 4. Click OK to add the server connection.

Project is not available in the Projects list

The Projects list in the TestTrack Project Selection dialog box only contains the projects that users have access to. If users do not have access, the TestTrack administrator must add them to the project. 1. Log in to the project. 2. Choose View > Users. 3. Click Add to add a new user or click Retrieve Global User to add global users from the Seapine License Server.

31

Setting Up RDBMSDatabases
TestTrack projects and the server database are stored in a Relational Database Management System (RDBMS). The TestTrack database is stored in SQLite, which is the default, native database type. ODBC (Microsoft SQL Server), Oracle, and PostgreSQL are also supported. Information about supported platforms and databases is available in the TestTrack RDBMS Support knowledgebase article (www.seapine.com/kb/questions/1527). TestTrack native databases do not require any setup or configuration before or after installation. PostgreSQL is also supported out of the box. If you use Oracle or SQL Server, review the following information for help setting up databases. Note: By default, the Seapine License Server database is also stored in SQLite, but other RDBMS types are also supported. See the Seapine License Server Admin Guide (http://downloads.seapine.com/pub/docs/licenseserveradmin.pdf) for information about setting up license server databases.

Setting up PostgreSQLdatabases
Seapine does not provide support for installing, configuring, or maintaining PostgreSQL. A qualified PostgreSQL database administrator should install and configure the database. Keep the following in mind:
n n n n

Do not add, delete, or modify any fields in the TestTrack tables. Do not directly add, edit, or delete any data in the tables. Do not create different primary keys. This will adversely affect application performance. Do not create complex triggers on any of the tables. Triggers may cause severe database issues and correcting these issues is not covered by Seapine Software. Create a process to back up database tables on a regular schedule. Running PostgreSQL and the TestTrack Server on the same computer can result in slow performance if not configured properly. Make sure PostgreSQL is properly configured to avoid using all the system memory.

n n

Creating server database tables

The TestTrack Server automatically creates tables in PostgreSQL when you start the server or convert the server database. The TTServerDB.sql script file, which is located in the PostgreSQL directory in the TestTrack application directory, is used to create the tables.

Setting up Oracle databases

Seapine does not provide support for installing, configuring, or maintaining Oracle. A qualified Oracle database administrator should install and configure the database and create the necessary schemas and tablespaces. Keep the following in mind:

33

S e t t in g u p Or acl e d at ab ase s

n n n n

Do not add, delete, or modify any fields in the TestTrack tables. Do not directly add, edit, or delete any data in the tables. Do not create different primary keys. This will adversely affect application performance. Do not create complex triggers on any of the tables. Triggers may cause severe database issues and correcting these issues is not covered by Seapine Software. Create a process to back up database tables on a regular schedule. Running Oracle and the TestTrack Server on the same computer can result in slow performance if not configured properly. Make sure Oracle is properly configured to avoid using all the system memory.

n n

Connecting to Oracle
The recommended method for using Oracle is via Oracle Call Interface (OCI). A separate installer that includes the required Oracle Instant Client libraries can be downloaded from Seapines web site.
n n n

Windowshttp://downloads.seapine.com/pub/software/OracleInstantClientInstaller.exe Mac OS Xhttp://downloads.seapine.com/pub/software/oraclemacosxjavainstall.zip Linuxhttp://downloads.seapine.com/pub/software/oraclelinuxjavainstall.tar.gz

Creating database tables

The TestTrack Server automatically creates tables when you start the server or convert the server database. The TTServerDB.sql script file, which is located in the Oracle directory in the TestTrack application directory, is used to create the tables.

Creating Oracle users

You must create an Oracle user for the TestTrack Server. The user only requires default connection privileges and should not have any Oracle DBA privileges. Use your preferred tablespace management for the users. An easy method is to set up the user to share the USERS tablespace and to enable an unlimited quota.

Database character set

Oracle only converts characters when the Oracle clients character set, specified by NLS_LANG, does not match the character set stored in the database. If the character set is not UTF-8, VARCHAR2 fields may not be able to correctly store data. If this happens, the following misnomer of an error is returned: ORA-01461: can bind a LONG value only for insert into a LONG column. The Oracle database character set should be AL32UTF8 or UTF8.

Sizing, memory, and tuning

Oracle sizing and tuning settings should be consistent with your corporate standards. Review the SQL scripts for schema creation installed with TestTrack Server to determine the appropriate settings.

34

S e t t in g u p S QL S e r ve r d at ab ase s

Setting up SQL Server databases

Seapine does not provide support for installing, configuring, or maintaining SQL Server. A qualified SQL Server database administrator should install and configure the database. Keep the following in mind:
n n n n

Do not add, delete, or modify any fields in the TestTrack tables. Do not directly add, edit, or delete any data in the tables. Do not create different primary keys. This will adversely affect application performance. Do not create complex triggers on any of the tables. Triggers may cause severe database issues and correcting these issues is not covered by Seapine Software. Create a process to back up database tables on a regular schedule. Running SQL Server and the TestTrack Server on the same computer can result in slow performance if not configured properly. Make sure SQL Server is properly configured to avoid using all the system memory.

n n

Note: You must be a member of the db_ddladmin role and have the CREATE TABLE, CREATE PROCEDURE, and CREATE VIEW permissions to create the TestTrack tables.

Connecting to SQL Server

The only supported method for using SQL Server is via an ODBC connection. Use the ODBC Data Source Administrator to add a SQL Server data source name (DSN) on the TestTrack computer.
n n n

SQL Server must contain a TestTrack database before you create the DSN. You must use a system DSN. Make sure you change the default database to the TestTrack database. Do not use the master database. Make sure the Use ANSI quoted identifiers, ANSI nulls, padding, and warnings, and Perform translation for character data options are selected.

Creating server database tables

The TestTrack Server automatically creates tables when you start the server or convert the server database. The TTServerDB.sql script file, which is located in the SQLServer directory in the TestTrack application directory, is used to create the tables.

Troubleshooting RDBMS connections

The following information can help you troubleshoot common RDBMS issues. Refer to the database vendor documentation for additional help. Note: If the TestTrack Server cannot connect to the server database, errors are added to the Startup.log file in the TestTrack application directory.

35

Tr ou b l e sh oot in g RDB M S con n e ct ion s

Server database cannot be shared

The Seapine License Server, Surround SCM Server, and TestTrack Server store server configuration information in a server database. The server databases cannot be located in the same RDBMS database.

Dropped tables or change database configuration

You must stop and restart the TestTrack Server if you drop server or tables from an RDBMS and need to re-create them. You must also stop and restart the server if you reconfigure the destination database in the ODBC Data Source Administrator. The TestTrack Server caches data from the database. If the underlying database is modified, the cached data no longer matches the data in the database. The connection fails if the server identifies that the backend database is different and the following error is logged: 'The server failed to initialize a connection for XYZ. The destination RDBMS database was changed'.

Mismatched UUID affects server database lock

This error occurs when the database is in use by a different TestTrack Server. You are prompted to reconfigure the database. Do not reconfigure the database if it is used on a different computer. You must manually modify the TestTrack Server connection information to point to a different database and restart the server. If the database is no longer in use by a different server, reconfigure the database connection information to allow the current TestTrack Server access to the database.

ODBC connection issues

Try the following if you are experiencing ODBC connection problems. 1. Test the ODBC connection in the ODBC Data Source Administrator. If you cannot connect to the RDBMS, click the Test Connection button in the ODBC Data Source Administrator to test the connection. 2. Make sure the DSN is a system DSN. The data source you are trying to connect to must be configured as a system DSN in the ODBC Data Source Administrator. The TestTrack Server Admin Utility only displays system DSNs.

ODBC connection errors

Error [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified QODBC3: Unable to connect Cause An ODBC data source with the specified DSN was not set up in the ODBC Data Source Administrator. The DSN must be a system DSN.

36

Tr ou b l e sh oot in g RDB M S con n e ct ion s

SQL Server connection errors

Error [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection. QODBC3: Unable to connect [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'xxxx'. QODBC3: Unable to connect Cause Occurs on Windows. A username is not specified for the RDBMS connection and the ODBC data source was not configured to run With Windows NT authentication using the network login ID in the ODBC Data Source Administrator. The username or password entered in the RDBMS connection information is not valid.

Oracle connection errors

Error ORA-06401: NETCMN: invalid driver designator QOCI: Unable to logon ORA-12705: invalid or unknown NLS parameter value specified QOCI: Unable to logon Cause The Oracle Instant client drivers are not installed. See Setting up Oracle databases, page 33 for information about downloading the installers.

The full Oracle client is installed on the same computer with a language setting other than UTF8. To resolve this issue, set the following environment variable:
n n

WindowsNLS_LANG=AMERICAN_AMERICA.WE8MSWIN1252 Linux and Mac OS XNLS_LANG=American_America.UTF8

You can also remove the following registry entry to help resolve the issue: HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\NLS_LANG Note: Refer to Oracle Metalink article 179133.1, The Correct NLS_LANG in a Windows Environment, for information about the correct setting, which varies based on the Windows version. ORA-12514: TNS:listener does not currently know of service requested in connect descriptor QOCI: Unable to logon The service name specified in the RDBMS connection information does not exist. Make sure that an Oracle listener was created with the specified service name on the host computer. This error can also occur if a version of the full Oracle client older than 10g is installed. If the full client appears in the PATH environment variable, the older oci.dll may be loaded. To resolve this issue, search for all instances of the oci.dll file. If multiple copies are found, remove the other copies or remove their directory reference from the PATH environment variable.

37

Tr ou b l e sh oot in g RDB M S con n e ct ion s

Error ORA-12154: TNS:could not resolve the connect identifier specified QOCI: Unable to logon ORA-12541: TNS:no listener QOCI: Unable to logon ORA-01017: invalid username/password; logon denied QOCI: Unable to logon

Cause The computer specified in the RDBMS connection host name cannot be found. Make sure the host name is correct and the host computer is running.

The port number specified in the RDBMS connection information is not a valid TNS listener port on the specified host computer. Check the host port number. The username or password specified in the RDBMS connection information is not valid. Check the username and password.

PostgreSQL connection errors

Error Opening the database connection failed because the TestTrack Server could not connect to the server or translate the host name Cause The TestTrack Server cannot connect to the PostgreSQL service. Check the following and then restart the server:
n n

The PostgreSQL service is running. The host name and port number are correct. A firewall is not blocking the port. If connecting to a remote PostgreSQL server, the server is configured to accept remote connections.

n n

38

Appendix A: Microsoft Windows Security Issues

File level security issues
TestTrack can only restrict security access through the application. This does not replace the need for file and directory security at the operating system level. Use Windows NT/2000 with NTFS to provide increased security. You can restrict access to the TestTrack directory through NTFS security settings. You can also restrict access for most users to readonly permission. TestTrack users do not need write access because the server application does the actual writing to the project files. The following example illustrates what could happen if users have full access: A drive is accessible through the network and there is no file-level security on the drive. Any user can open and look at data/files using a program such as Notepad. Data is stored in both binary format and plain text. Usernames and passwords are encrypted so the user cannot access that information. In addition to viewing the data/files, it is possible for a user to vandalize your system by deleting files or even deleting an entire TestTrack project. Note: Windows 2000 with FAT provides some security restrictions. However, Windows NT/2000 with NTFS is recommended if security is a concern.

Directory sharing issues

n

The TestTrack ODBC driver requires projects to be accessible via a shared network drive. You only need to share the TestTrack directory if you are planning to use the TestTrack ODBC driver. If you grant ODBC access to a project, users can view all TestTrack data with the exception of encrypted usernames and passwords. The need for file-level security is increased if you place the TestTrack project on a shared network drive.

Note: Windows XP does not provide file-level security because it uses the FAT file system. Windows NT security is only available if you are using the NTFS file system; it is not available with the FAT file system. You can convert to NTFS. Refer to the Microsoft Windows documentation for additional information.

39

Appendix B: Third-Party Software Licenses

Diff Match and Patch license
The following license information pertains specifically to the Diff Match and Patch software. Copyright 2008 Google Inc. All Rights Reserved. Author: fraser@google.com (Neil Fraser) Author: mikeslemmer@gmail.com (Mike Slemmer) Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. Diff Match and Patch http://code.google.com/p/google-diff-match-patch/

gSOAP software license

The following license information pertains specifically to the gSOAP software. Part of the software embedded in this product is gSOAP software. Portions created by gSOAP are Copyright (C) 2001-2002 Robert A. van Engelen, Florida State University. All Rights Reserved. THE SOFTWARE IN THIS PRODUCT WAS IN PART PROVIDED BY GSOAP SOFTWARE AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

OpenSSL license
The following license information pertains specifically to the OpenSSL toolkit. The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit. See below for the actual license texts. Actually both licenses are BSD-style Open Source licenses. In case of any license issues related to OpenSSL please contact openssl-core@openssl.org.

41

Ap p e n d ix B : Th ir d -P ar t y S oft war e Lice n se s

OpenSSL license
Copyright (c) 1998-2008 The OpenSSL Project. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. All advertising materials mentioning features or use of this software must display the following acknowledgment: "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)" 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact openssl-core@openssl.org. 5. Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their names without prior written permission of the OpenSSL Project. 6. Redistributions of any form whatsoever must retain the following acknowledgment: "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)" THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ==================================================================== This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com).

Original SSLeay license

Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com) All rights reserved. This package is an SSL implementation written by Eric Young (eay@cryptsoft.com). The implementation was written so as to conform with Netscape's SSL. This library is free for commercial and non-commercial use as long as the following conditions are adhered to. The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson (tjh@cryptsoft.com). Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed.

42

Ap p e n d ix B : Th ir d -P ar t y S oft war e Lice n se s

If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. All advertising materials mentioning features or use of this software must display the following acknowledgement: "This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)" The word 'cryptographic' can be left out if the routines from the library being used are not cryptographic related :-). 4. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement: "This product includes software written by Tim Hudson (tjh@cryptsoft.com)" THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. The license and distribution terms for any publicly available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution licence [including the GNU Public Licence.]

Qt LGPL license
TestTrack uses the Qt library covered by version 2.1 of the GNU Lesser General Public License (LGPL). A copy of the Qt LGPL license is available in the Qt License.txt file in the TestTrack application directory.

Xerces license
The following license information pertains specifically to the Xerces software. Copyright 1999-2004 The Apache Software Foundation. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0

43

Ap p e n d ix B : Th ir d -P ar t y S oft war e Lice n se s

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. ====================================================== == NOTICE file corresponding to section 4(d) of the Apache License, == Version 2.0, in this case for the Apache Xerces distribution. ====================================================== This product includes software developed by The Apache Software Foundation (http://www.apache.org/). Portions of this software were originally based on the following: - software copyright (c) 1999, IBM Corporation., http://www.ibm.com

44

In d e x:404 - P age N ot Fou n d P r oje ct s

Index
4
404 - Page Not Found 30

types Installers

5 6

L
Licenses adding 2 3 3 Login default 13 14

6
64-bit TestTrack Server new installations upgrade installations

M
Moving projects 16

A
Add-in options After installation Apache configuration Automatic client upgrades 8 13 24 3

O
ODBC connection errors connection issues Oracle 36 36

C
Configuration options 7

connecting to connection errors

34 37 34 34 34 34 33 34 8

D
Databases Oracle PostgreSQL SQL Server Date format Directories default installation Distributed web installations 8 19 1 33 33 35 10

creating server database tables creating users database character set instant client libraries (OCI) setting up sizing, memory, and tuning Outlook add-in

P
Ports

H
HTML file default directories 9

Seapine License Server SOAP server TestTrack Server PostgreSQL 23 21 20 connection errors creating server database tables setting up Projects 13 5 8 7 moving upgrading automatically upgrading manually

12 10 8

I
IIS configuration IIS 5 IIS 6 IIS 7 Installation after before default directories running

38 33 33

16 1 2

45

In d e x:RDB M S con n e ct ion s Te st Tr ack S e r ve r Ad min U t il it y

RDBMS connections changed database configuration dropped tables exclusive lock mismatched UUID server database cannot be shared troubleshooting RDBMS databases 36 36 36 36 36 35 33

SOAP server SQL Server connecting to connection errors creating server database tables setting up Starting Seapine License Server Seapine License Server Admin Utility TestTrack Client 11 10 14 11 11 12 13 13 TestTrack Pro Web TestTrack Server TestTrack Server Admin Utility TestTrack TCM Test Runner System requirements

10

35 37 35 35

13 13 16 16 15 15 16 5

S
Seapine License Server CGI and HTML file directories configuration options configuring connections default installation directories execution mode port starting starting admin utility Seapine License Server Admin Utility configuring web servers Apache IIS 5 and 6 IIS 7 URL Security issues (Windows) directory sharing file-level Serial numbers adding Server connections Seapine License Server TestTrack Server Server database tables Oracle PostgreSQL SQL Server Server execution mode Short date format 34 33 35 8 10 14 15 14 39 39 25 27 25 14

T
TestTrack CGIs configuration options default HTML file directories default installation directories server address and port TestTrack Client starting upgrading automatically TestTrack Pro Web configuring IIS 5 configuring IIS 6 configuring IIS 7 starting TestTrack Server 64-bit application configuring connections execution mode port starting TestTrack Server Admin Utility starting 15 2 15 8 8 15 23 21 20 16 16 3 9 9 10 9

46

In d e x:Te st Tr ack TCM Te st Ru n n e r Win d ows se cu r it y issu e s

TestTrack TCM Test Runner configuring Apache configuring IIS 5 configuring IIS 6 configuring IIS 7 starting TestTrack URL Redirector TestTrack Web configuration options configuring Apache distributed installations installation Troubleshooting RDBMS connections TestTrack issues 35 29 9 24 19 2 24 23 21 20 16 24

file-level

39

U
Unix short date format Upgrading clients automatically projects automatically projects manually URL for license server admin utility URL Redirector Users adding retrieving global 14 16 10 1 3 1 2 14 24

V
Visual Studio add-in 8

W
Web server configuring Apache supported Web server configuration IIS 5 IIS 6 IIS 7 Windows security issues directory sharing 39 23 21 20 24 9

47