install 370

8/2/2019 Install 370

1/66

8/2/2019 Install 370

2/66

8/2/2019 Install 370

3/66

iii

Track+ Installation Guide, Version 3.7

This manual and the accompanying software and other documentation is protected by internationalcopyright laws, and maybe only used in accordance with the accompanying license agreement.

Trackplus and the Track+ logo are trademarks of Trackplus, and may be registered in certain juris-dicions. The absence of a trademark from this list does not constitute a waiver of Trackpluss intel-

lectual property rights concerning the trademark.

All other company, brand and product names may be trademarks or registered trademarks of theirrespective holders. Trackplus disclaims any responsibility for specifying which marks are owned by

which companies or which organizations.

Trackplus provides links to external third-party Web sites to help you find supplemental informa-

tion. Site content and availability may change without notice. Trackplus makes no warranties no rep-resentations whatsoever as to site content or availability.

TrackplusEugen-Ruoff-Str. 30D-71404 KorbGermany

Tel.: +49 7151 994 89-60

Fax: +49 7151 994 89-61Support: [email protected]

Copyright 2001-2010 Trackplus, All rights reservedFebruary 2010

If you have any comments or suggestions regarding this document, please send them by e-mail to

[email protected].

8/2/2019 Install 370

4/66

iv

8/2/2019 Install 370

5/66

Contents

Welcome to This GuideHow This Guide is Organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Documentation Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Additional Online Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

n Documentation Updates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Before You Install1.1 About Track+ Technology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.2 Track+ Installation Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.3 The Installation Process with Windows Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.4 The Installation Process without Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.5 System Configurations for Track+ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.6 Attachment Data Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.7 Text Search Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.8 Installer Directory Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Installing Track+

2.1 Obtaining the Track+ Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.2 Step 1: Verifying System Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2.2.1 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.2.2 Access to SMTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.2.3 File System Configuration in Clustered Environment . . . . . . . . . . . . . . . . . . . . 16

2.3 Step 2: Installing the Java SDK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.4 Steps 3 to 6: Installation using the Windows Installer . . . . . . . . . . . . . . . . . . . . . . . . 182.5 Step 3: Installing a Database Management System. . . . . . . . . . . . . . . . . . . . . . . . . . . 19

2.5.1 MySQL Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.5.2 Firebird Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.5.3 MS SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232.5.4 Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252.5.5 IBM DB2 Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262.5.6 PostgreSQL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272.5.7 SAP DB Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

2.6 Step 4: Installing an Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282.6.1 Apache Tomcat. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292.6.2 Integrating Apache Tomcat with IIS6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

8/2/2019 Install 370

6/66

2.6.3 Oracle WebLogic (Former BEA). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322.6.4 JBoss. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

2.6.5 Sun ONE Webserver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342.7 Step 5: Configuring the Database Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

2.7.1 Modifying Torque.properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352.7.2 Example for Non-Western Character Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

2.8 Step 6: Installing Graphviz . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382.9 Step 7: Installing Subversion Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382.10 Remaining Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392.11 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Configuring Track+3.1 First Login and Access to Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413.2 Entering License Key Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423.3 Setting up E-mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

3.3.1 Basic E-mail Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433.3.2 Enabling Issue Submissions by E-mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463.3.3 Authorizing E-mail Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

3.4 Setting up Full Text Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

3.5 Setting up Attachment Handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493.5.1 Setting up the Attachment Root Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493.5.2 Configuring the Attachment Size Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

3.6 Configuring for Operation in a Proxied Environment . . . . . . . . . . . . . . . . . . . . . . . . 503.7 Configuring Graphviz . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513.8 Configuring Session Time Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Uninstalling Track+4.1 Uninstalling Track+ from Windows (Installer) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

4.2 Uninstalling Track+ from Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544.3 Uninstalling Track+ from Unix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Index

8/2/2019 Install 370

7/66

1

Welcome to This GuideWelcome to Track+, the enterprise-wide issue tracking and project management application thatsupports tracking and managing all critical activities throughout a projects lifecycle. Track+ bringstransparency into project status, team members responsibilities, and time and cost budgets. It is high-ly configurable and easily adapts and extends to meet your specific project control needs.

How This Guide is Organized

The Track+ Installation Guide describes the system requirements and installation process forTrack+. It contains the following chapters:

Chapter 1 Before You Install

Provides an overview of the product, and specifies the server and client configura-tions for installing Track+.

Chapter 2 Installing Track+

Describes how to install Track+ with different database servers and servlet containers.

Chapter 3 Configuring Track+

Describes how to configure Track+ e-mail access, directories for attachments, index-ing, how to start and stop the server, and how to set up the first project.

Chapter 4 Uninstalling Track+

Describes how to uninstall Track+ from your server.
http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/

8/2/2019 Install 370

8/66

2 Welcome to This Guide

Documentation Library

The documentation library consists of the following documents:

Track+ Installation Guide

This document, describes the Track+ installation process.

Track+ Administrators Guide

Describes procedures to administer a Track+ installation, add, modify and deleteprojects, manage users, manage workflows, manage security, and customize attributesand screens.

Track+ Users Guide

Describes how to use Track+ for regular users, project managers, and process manag-ers.

Release Notes

Describes the history of changes for the latest Track+ release. This should help todecide if its worthwhile to upgrade from a previous release.

The most up to date versions of the documentation library can be accessed on http://www.trackplus.com.

Additional Online Resources

There are additional online resources available on the Trackplus homepage at http://www.track-plus.com. In particular, there are

white papers

forum at http://www.trackplus.com/forum demo installation at http://www.trackplus.com/track-demo

The forum provides patches and answers to frequently asked questions.

Documentation Updates

Trackplus is continuously updating its product documentation with new information. You candownload the latest version of this document from the Trackplus Web site (http://

www.trackplus.com).
http://www.trackplus.com/http://www.trackplus.com/http://www.trackplus.com/forumhttp://www.trackplus.com/track-demohttp://www.trackplus.com/http://www.trackplus.com/http://www.trackplus.com/track-demohttp://www.trackplus.com/forum

8/2/2019 Install 370

9/66

5

1Before You InstallThis chapter provides an overview over the installation process, and specifies system requirements forTrack+. It describes

About Track+ Technology

Track+ Installation Files

The Installation Process with Windows Installer

The Installation Process without Windows Installer System Configurations For Track+

Attachment Data Configuration

Text Search Configuration

1.1 About Track+ Technology

Track+ is an enterprise-wide application that is based on Java technology. This technology enablesTrack+ to run on a wide variety of server hardware and operating systems. Track+ is a web basedapplication and does not require any software installation on the client side; a simple web browsersuffices.

Track+ Enterprise Edition supports clustering. A clusteris a group of application servers that runTrack+ as if they were a single entity. Each application server in a clusteris referred to as a nodeor acluster node.

Clusters provide mission-critical services to ensure maximum scalability and high availability. The

load balancing technique within the cluster is used to distribute client requests across multiple appli-

8/2/2019 Install 370

10/66

6 Chapter 1: Before You Install

cation servers, making it easy to scale to an infinite number of users. The cluster of servers can runon Windows, Linux, and Solaris based platforms, or any other platform that supports Java.

The following diagram illustrates how Track+ client requests are transmitted within a cluster.

Track+ Web Clients:

Track+ requires a standard browser like Internet Explorer, Firefox, Opera, or Safarion each client. There is no need to install any additional software on the client. Thebrowser needs to have JavaScript enabled.

Figure 1-1: Track+ installation in clustered environment

tenartnI/tenretnI

recnalaBdaoL

revreSnoitacilppA

revreSeliFrevreSesabataD

beW+kcarT

stneilC

retsulC+kcarT

noitallatsnI

8/2/2019 Install 370

11/66

Track+ Installation Files 7

Internet/Intranet:

Track+ client requests are transmitted via HTTP protocol to the server. It is possible

to configure a secured link between the clients and the server, using SSL (https).

Load Balancer:

When working with a load balancer, client requests are transmitted to the load bal-ancer and distributed according to server availability within the cluster. The load bal-ancer is optional, it is common to operate Track+ with a single application server.

Application Server:

Client requests are dispatched by servlets to the Track+ application software on theapplication server. Track+ does not require a fully J2EE application server, a simpleservlet container suffices. Track+ officially supports Apache Tomcat, JBoss, Web-Logic, WebSphere, Sun Webserver, Jetty, and JRun.

The deployed application is packaged into a single Web Application Archive (WAR)file. The Java Database Connectivity (JDBC) interface is used to communicatebetween the application server and the database server.

Database Server:

Persistent data is stored in the Track+ database. Track+ supports schemas on Oracle,DB2, Microsoft SQL Server, MySQL, Firebird, Postgres, Sybase, and Derby.

File Server:

Track+ stores attachments to issues and indices for the text search facility directly infiles and not in the database. In a clustered environment these data should be storedon a single server.

The standard configuration is to operate Track+ with a single machine running application server,file service, and database server. A standard workstation with 1 GByte of main memory and 1 GByteof disk space should be sufficient to serve several hundred users and accommodate up to 100.000issues.

1.2 Track+ Installation Files

Track+ offers three types of installation files:

8/2/2019 Install 370

12/66


Track+ Windows Installer

This packages permits to install Track+ basically without any user intervention on

machines with Windows operating systems. This package is well suited for non-clus-tered production environments and for local test installations. It bundles with a Fire-bird open source database server and an open source Apache Tomcat servletcontainer.

Track+ Binary (WAR-file)

The Track+ WAR file can be copied to a servlet containers webapps directory andwill usually be expanded there by the servlet container. Using this package requires

more manual configuration, but any choice of database servers, servlet containers,and operating systems can be used.

The WAR file package should be used if the database server and servlet containercoming with the Windows installer do not fit, or if Track+ shall be installed on anon-Windows system like Linux, Solaris, HP-UX, etc.

Track+ Binary (EAR-file)

This file is very similar to the WAR file and can be loaded into application servers

using their application management facilities. Using the EAR file it is possible to use

tenartnI/tenretnI

revreSnoitacilppA

beW+kcarT

stneilC

elpmiS+kcarT

noitallatsnI

Figure 1-2: Track+ simple installation

8/2/2019 Install 370

13/66

The Installation Process with Windows Installer 9

a variety of operating systems, servlet containers, and database servers. It requires thesame amount of manual configuration as the WAR file.

1.3 The Installation Process with Windows Installer

Installing Track+ using the Windows installer consists of the following steps:

Step 1 Verify System Configuration

Before you install Track+, verify that your server and client machines meet hardwareand software specifications. For more information, see "System Configurations forTrack+" on page 12.

Step 2 Install Java JDK

Track+ uses Java technology. In this installation step a Java Development Kit (JDK)needs to be installed on the server machine, unless it is already there.

Step 3 Run Windows Installer

Track+ uses Java technology. In this installation step a Java Development Kit (JDK)needs to be installed on the server machine, unless it is already there.

Step 4 Configure Track+

This step involves some basic setup like changing the administrator password, estab-lishing SMTP server connection parameters, and defining directories for attachmentsand indexes.

1.4 The Installation Process without Installer

Installing Track+ without an installer consists of the following steps:

Step 1 Verify System Configuration

Before you install Track+, verify that your server and client machines meet hardwareand software specifications. For more information, see "System Configurations forTrack+" on page 12.

Step 2 Install Java JDK or JRE

Track+ uses Java technology. In this installation step a Java Development Kit (JDK)

or Java Runtime Environment (JRE) needs to be installed on the server machine.

8/2/2019 Install 370

14/66


Step 3 Install Database Management System

Track+ runs on a variety of database servers (for more information, see "System Con-figurations for Track+" on page 12). Before Track+ can be installed, a database server

must be running on a database server machine. The database server machine can bedifferent from the Track+ server. In a clustered environment there is usually a singledatabase server, and several cluster nodes running the Track+ application.

Step 4 Install Application Server

Track+ is a J2EE application and requires a servlet container like Apache Tomcat orapplication server like JBoss, Websphere or Bea Weblogic to run. This servlet con-tainer needs to be installed before Track+ itself can be installed. The deployment ofthe Track+ application depends on the application server used. Basically it means to

unpack or upload a file on the application server.

Install Track+

Install Database Server

Verify System Configuration1. Verify System Configuration

3. Run Windows Installer

4. Configure Track+

Figure 1-3: Track+ installation process with installer, overview

Install Database Server2. Install Java JDK or JRE

8/2/2019 Install 370

15/66

The Installation Process without Installer 11

Install Track+

Install Graphviz

Install Application Server

Install Database Server

Verify System Configuration1. Verify System Configuration

3. Install Database Server

4. Install Application Server

6. Install Graphviz

7. Configure Track+

Figure 1-4: Track+ installation process without installer, overview

Install Database Server2. Install Java JDK or JRE

Install Application Server5. Configure DB Connection

8/2/2019 Install 370

16/66


Step 5 Configure Database Connection

After Track+ has been deployed to the application server, you need to modify a single

configuration file to establish connection to the database.

Step 6 Install Graphviz

Track+ uses the Graphviz package from AT&T to render its workflow graphs.Graphviz is a native application and needs to be obtained for the specific servermachine. If graphical display of workflow graphs is not required this package can beomitted.

Step 7 Configure Track+

This step involves some basic setup like changing the administrator password, estab-lishing SMTP server connection parameters, and defining directories for attachmentsand indexes.

If the Track+ Windows Installer is used, steps 1 to 6 are executed automatically by the installationsoftware. There is no need for user intervention.

1.5 System Configurations for Track+

This section describes the server system and client (browser) configurations for Track+.

Since Track+ system uses Java technology, it runs on any platform with the requirements shown inTable 1-1. Not all possible configurations are officially supported. Table 1-2 shows the operating sys-tem configurations supported by Trackplus.

Table 1-1: System requirements for the Track+ system

Object Requirement

Main memory min. 512 MByte

Disc space min. 1 GByte available

Java Virtual Machine Java SDK or JRE version 1.5.x or 1.6.x
http://-/?-http://-/?-

8/2/2019 Install 370

17/66

System Configurations for Track+ 13

There are more operating systems known to work with Track+, but they are not directly supported

Database System MySQL 5.x

Firebird 2.x

Oracle9i, Oracle 10g, Oracle 11gMS SQL Server 2000, 2005, 2008

PostgreSQL 8.x

IBM DB2 9.x

Application Server Oracle WebLogic 10

JBoss 4.x

Jetty 5.x and 6.xSun ONE Web Server 6 and 7

Apache Tomcat 5.5 or higher

Websphere Application Server

SMTP E-Mail Server any standard SMTP server

Browser Internet Explorer 6.x, 7.x

Opera 9.x

Firefox 3.x

Safari

Table 1-2: Supported operating systems

Operating System Remarks

Windows 2000 no support any more

Windows XP

Windows Server 2003, 2008

Windows Vista

Linux 2.4 (Ubuntu, SuSE, RedHat)

Table 1-1: System requirements for the Track+ system

Object Requirement

8/2/2019 Install 370

18/66


by Trackplus. They are shown in Table 1-3.

1.6 Attachment Data Configuration

In Track+ an arbitrary number of files can be attached to an issue. For performance reasons, theseattachments are not stored inside the Track+ database but on the file system. Sufficient disk spaceshould be provided to be able to accommodate all attachments. As an example for a worst case cal-culation we assume 2 attachments of 1 MByte each for each 10 issues. If the plan is to keep 100.000issues active there would have to be provided 20.000 MByte or 20 Gbyte of disk space for attach-

ments.There is a single attachment directory. In a clustered environment this directory needs to be read andwrite accessible from all cluster nodes.

1.7 Text Search Configuration

Track+ provides full text search facilities for all issue fields and attached files. The indices for the textsearch facility are kept outside of the database in a separate directory. This directory should provide

enough disk space for about half the size of the attachment directory. In a clustered environment itneeds to be read and write accessible from all cluster nodes.

1.8 Installer Directory Layout

When Track+ is installed via the installer, the resulting directory layout is as illustrated in Fig. 1-5.File Torque.properties contains the information on how Track+ connects to the Track+ data-base. The database files, attachments and indices are stored in a separated folder under C:\Program

Files\Track+.

Table 1-3: Unsupported operating systems known to work

Operating System Remarks

Windows NT SP6

Sun Solaris

HP-UX 11

MacOS X

8/2/2019 Install 370

19/66

Installer Directory Layout 15

The web container structure is predetermined by the Java Server Pages specification and the servletcontainer being used. If a different database shall be used, it can be placed anywhere else, even on a

separate server. The directory for attachments and index data can also be placed anywhere else whereit can be read and written to from the servlet container. This directory is configured inside the Track+application and stored in the database.

Local Disk (C:)

...

Program Files

Apache Software FoundationTomcat 5.5

bin

conf

logs

webapps

track

...WEB-INF

Torque.properties

track.war

Track+

Database

TRACK.GDB

trackdataattachments

Figure 1-5: Track+ directory structure as created by the installer

8/2/2019 Install 370

20/66


8/2/2019 Install 370

21/66

15

2

Installing Track+This chapter provides a step by step description of the installation process with either the Windowsinstaller, or without the windows installer, for example for Unix systems. In particular it describes

Obtaining the Track+ Package

Verifying System Configuration

Installing the Java SDK

Installation using the Windows Installer Installing a Database Management System

Installing an Application Server

Configuring the Database Connection

Installing Graphviz

Remaining Steps

2.1 Obtaining the Track+ PackageDownload the required files of the Track+ package from http://www.trackplus.com/prod-ucts/download.html and save it under e.g. c:\tracktmp or any other place. At the end of theinstallation procedure you may remove these files and directories.

If you want to use the Windows installer, download it from the web site. It contains everything re-quired to install a complete Track+ system on an MS Windows based computer. You can skip therest of this section if you follow this route.

If you cannot use the Windows installer, you need at least the following two files (where v stands for

8/2/2019 Install 370

22/66

16 Chapter 2: Installing Track+

the version):

track-v-db.zip (the database setup files)

track-v.war (Everything else)

The source code package track-v-src.zip will be supplied upon request to customers. You onlyneed it if you want to recompile the application. The client package track-client-v.jar youonly need if you want to use the client functionality.

Please be aware that some browsers add a .zip extension to the .war-file when downloading andsaving it since they recognize it as a compressed file. You may have to manually rename it back totrack-v.war if your browser has mangled the file name.

2.2 Step 1: Verifying System Configuration

2.2.1 System Requirements

Before you start make sure that your system meets Track+ requirements. Be aware that the Track+installer installs a Tomcat application server on the default Windows drive where your ProgramFiles directory is located. Make sure there is at least 50 Mbyte of disk space there.

Make sure that you have sufficient disk space for the system itself, the database, the indexes, and theattachments (see section 1.5).

2.2.2 Access to SMTP Server

You should have access to an SMTP server before setting up Track+. For test purposes you could useyour own e-mail account, but this is not recommended if your SMTP server requires authentication.It is definitely best to get a dedicated e-mail account for your Track+ installation.

2.2.3 File System Configuration in Clustered EnvironmentWhen working in a clustered environment in Solaris or Linux, you must mount the file system re-pository before you start the Track+ installation process. Note that the mount to the file system re-pository should not use any cache mechanisms.

To mount a file system repository in Linux:

NFS mounts:

When using NFS mounts, modify the /etc/fstab file as follows:
http://install.pdf/http://install.pdf/

8/2/2019 Install 370

23/66

Step 2: Installing the Java SDK 17

nfs sync,noac 0 0

SMBFS mounts:

When using SMBFS (mounted from a Windows machine), modify the /etc/fstab file as follows:

smbfs

credentials=/root/.smbpasswd,rw,gid=,uid=,

fmask=0777,dmask=0777 0 0

For example://tpserver/TPrepository /mnt/TPrepository smbfs

credentials=/root/.smbpasswd,rw,gid=10,uid=qcadmin,fmask=0777,dmask=0777 0 0

Where:

//qcserver/QCrepositoryis the UNC of the source path

uid=qcadmin is a domain user. Note that qcadmin must be a user on the Win-dows server and must belong to Administrators group.

/mnt/TPrepository

is the local folder

The tpadminin this example must be defined in the credential file (/root/.smb-passwd) as follows:

username = tpadmin

password =

You must also edit the /etc/samba/smb.conf file and change the workgroupvalue to a domain name (for example: TRACKPLUS).

To mount a file system repository in Solaris:

NFS mounts: When using NFS mounts, modify the /etc/vfstab file as follows:

- nfs - yes sync,noac

2.3 Step 2: Installing the Java SDK

Many systems already come with a Java runtime environment (JRE) installed. For running a Track+

server the JRE is not sufficient. You need to obtain the Java Software Development Kit (Java SDK)

8/2/2019 Install 370

24/66


version 1.5 or later as the servlet engine needs the Java compiler to compile the servlets. You can getit from http://java.sun.com.

The Windows version comes with an installer. You have to remember the root directory where youinstall the package ($JAVA_HOME). This you need later on to configure your application server.Many Linux and Unix distributions come with a Java SDK already installed. Here you have to findout where the root directory of the SDK is located to be able to configure your application serverlater on.

2.4 Steps 3 to 6: Installation using the Windows Installer

The installer installs the application in about five minutes with basically no user interaction. It comeswith a servlet container (Tomcat), a complete SQL database system suitable even for large installa-tions of several hundred users (Firebird), the workflow graph visualization software (GraphViz), andthe Track+ application itself.

Possible Conflicts with Competing Web Servers

If on first startup you do not get the login screen, there may be another web server already runningon port 80 and 8080 of your system.

Competing web servers could have been installed for example as part of Windows XP, Microsoft Of-fice Frontpage, Visual.NET or some other development software. Also known to cause problems areservers that have Oracle installed on them. Oracle might install its own webserver on port 80 and8080. To get Track+ running in such a case, you should either shut it down, or deploy Track+ withit. Alternatively you could change the default port in file server.xml of the Tomcat server (by de-fault installed under C:\Program Files\Apache Software Foundation\Tomcat5.5\conf) from 8080 to some other number. In this case you have to enter the port number as partof the URL where you access Track+, like http://localhost:7001/track instead ofhttp://localhost/track.

Possible Problem on Windows 2003 Server Systems

The Track+ installer runs itself an installer for the Firebird database management system. There is aknown problem with this installer on Windows 2003 Server Systems. To solve this problem down-load the Firebird installer yourself and run it manually. Then have a look at the Track+ forum for anup to date work around to get the database server up an running.

Thereafter run the Track+ installer again.

8/2/2019 Install 370

25/66

Step 3: Installing a Database Management System 19

2.5 Step 3: Installing a Database Management System

Before you proceed to the instructions for your specific RDBMS please unzip the Track+ databasepackage track-db-v.zip. The directory where you save the extracted files we call from now onUNZIP_DBASE_DIR. It has several database specific subdirectories like MySQL, Oracle, Fire-bird, MS SQL Server, Postgres, hypersonic, sapdb, and so on.

2.5.1 MySQL Database

MySQL is one of the primary supported database systems of Track+. Most Linux systems come witha mysql server instance already installed. Please be aware of the license of MySQL. In general,MySQL is only free for non-commercial usage, similar to Track+. If you want to deploy Track+ com-mercially with MySQL, you need to obtain a MySQL license.

Figure 2-1: Track+ Windows Installer

8/2/2019 Install 370

26/66


If you need to get the software, you can obtain it from http://www.mysql.com/downloads/index.html.

Get the latest stable release and install it on your computer. In the following the procedure is outlinedto get the required Track+ database up and running. In a production environment, it is recommend-ed to set up MySQL with transaction support and take care with regard to access privileges. Partic-ularly, there should be no general GRANT to user trackp for all hosts(trackp@%), but only tothe one the application is running on.

1. Change directory to the place where you unzipped the Track+ database packagetrack-db-v.zip to. This directory we call UNZIP_DBASE_DIR. It has a subdirectory called''MySQL''. Change to this directory, e.g. on Windows

cd c:\tracktmp\dbase\MySQL

2. Add a new user ''trackp'' with some password with theMySQL administration tool c:\mysql\bin\winmysqladmin.exe supplied with theMySQL distribution, or some other tool of the many that you may have found useful.

3. Call the mysql command line tool. There should be no space between the p and the pass-word. You are now inside the mysql command line tool, showing the prompt mysql>.Don't type this prompt in the following commands!

mysql --user=root -p

mysql> GRANT ALL PRIVILEGES ON track.* to trackp@"%"

IDENTIFIED by ''

WITH GRANT OPTION;

mysql> GRANT ALL PRIVILEGES ON track.* TO trackp@localhost

IDENTIFIED by ''

WITH GRANT OPTION;

mysql> FLUSH PRIVILEGES;

mysql> quit;

mysql -utrackp -p

mysql> create database track;

mysql> use track;

mysql> source /MySQL/id-table-schema.sql;

mysql> source /MySQL/track-schema.sql;

mysql> source /MySQL/quartz.sql;

mysql> source /populate.sql;

mysql> quit;

St 3 I t lli D t b M t S t 21

8/2/2019 Install 370

27/66


The database should now be up and running. The MySQL JDBC driver closes idle connections after8 hours. To have the driver automatically reconnected you need to set the option autoRecon-nect=true.

2.5.2 Firebird Database

Firebird Database on Linux

1. The software can be obtained via http://sourceforge.net/project/show-files.php?group_id=9028. Select the required server binary depending on your oper-ating system. The instructions for Unix below assume you are using the Linux rpm. For

other Unix operating systems, the procedure should be similar. Wherever possible, select theSuper Server architecture.

2. For easy setup and administration of the Firebird Database some administrative tool supportmay be helpful. You find a bunch of tools at http://www.ibphoenix.com.

3. Check if the database server is listening:

netstat -an | grep 3050

should result in a line including LISTEN in it.

4. Go and change the default SYSDBA password from MASTERKEY to your own. Don't for-get this password!

/opt/interbase/bin/gsec -modify sysdba -user sysdba

-password MASTERKEY -pw

5. Add a new user with name ''trackp'' and some password:

/opt/interbase/bin/gsec -add trackp -user sysdba

-password

-pw

6. The database is created from scratch using the isql command line utility (don't type theisql prompts) from where you extracted your Track+ database package:

/opt/interbase/bin/isql -u trackp -p tissi

isql> create database "/opt/interbase/db/track.gdb";

isql> input "dbase/Firebird/id-table-schema.sql";

isql> input "dbase/Firebird/track-schema.sql";


8/2/2019 Install 370

28/66


isql> input "dbase/Firebird/quartz.sql";

isql> input "dbase/populate.sql";

isql> quit;

Make sure the owner and permissions are set right:

chown -R firebird /opt/interbase/db

chmod 700 /opt/interbase/db

To access the database via IBConsole, you have to register it in this tool (Menu DatabaseRegister).The file path that needs to be entered is as seen from the server (e.g. /opt/interbase/db/track.gdb). The alias is of no importance.

Firebird Database on WindowsIf you intend to use this software on Windows, you should use the Track+ Windows installer. If forany reason you cant do this, the following instructions might be helpful.

The software can be obtained via http://sourceforge.net/project/show-files.php?group_id=9028. Select the required server binary depending on your operating sys-tem. The installation of the RDBMS is straightforward using the installation package. Please notethat there are some problems with the installer on Windows 2003 Server systems. Please have a lookat the Track+ forum for hints to resolve this kind of problem.

The following procedures assume that the database was installed in directory c:\ProgramFiles\Firebird. However, it can be placed anywhere else.

1. After installation, set the SYSDBA password from ''masterkey'' to something more secure:

c:\Program Files\Firebird\bin\gsec -modify sysdba -user sysdba

-password masterkey -pw

Alternatively, use the IBConsole utility if you did download it from the Borland site.

2. Add a new user with name ''trackp'' and some password:

c:\Program Files\Firebird\bin\gsec -add trackp -user sysdba

-password -pw

The user name does not matter, but it has to be consistent across the entire configuration.

3. Now you can install the Track+ database itself. Assuming that you had downloaded theTrack+ database package to c:\tracktmp, change to this directory and unpack the zip file.

You could use a utility program like WinZip for this instead of the unzip command:


8/2/2019 Install 370

29/66


cd c:\tracktmp

unzip track-v-db.zip

You should now have a directoryc:\tracktmp\dbase.4. Change to the Firebird directory ofdbase and create the Track+ database (don't type the

sql> prompts):

cd c:\tracktmp\dbase\Firebird

mkdir c:\data

c:\Program Files\Firebird\bin\isql -u trackp -p

sql> create database "c:\data\track.gdb";

sql> input "id-table-schema.sql";sql> input "track-schema.sql";

sql> input "quartz.sql";

sql> input "..\populate.sql";

sql> quit;

Of course, you can use any other name instead ofc:\data\track.gdb for the databasefile as long as you enter the same name and path into the ...\WEB-INF\Torque.prop-erties file in the application serves webapps directory.

2.5.3 MS SQL Server

Track+ works well with MS SQL Server Version 2000 , 2005, and 2008. Track+ uses the jTDSJDBC driver to connect to the database server. The most important point to consider is the correctsetting of the character set and collation, so that non-ANSI characters are properly stored and re-trieved. This setting should be explicitly set when creating the database. It is not recommended touse the standard settings of the database server. Create the database with the Enterprise Manager tool.

Table 2-1: Some code page settings for the jTDS JDBC driver

Region Collation jTDS Charset

Chinese tradit ional (Taiwan) Chinese_Taiwan_Stroke CP950

Chinese simplified (PRC) Chinese_PRC CP936

Danish Danish_Norwegian CP1252

English Latin1_General CP1252


8/2/2019 Install 370

30/66


Make sure you are using the right collation set when creating the database (see Table 2-1). It mightbe best to add a new user which will be used as owner of the database.

Use the SQl Query Analyzer to run these scripts located in the dbase directory of the database pack-age for completely new databases:

1. MSSQL\id-table-schema.sql

2. MSSQL\track-schema.sql

3. MSSQL\quartz.sql

4. populate.sql

The database should now be up and running. The MS SQL Server JDBC driver needs to be enabledin the Torque.properties file located in the webapps directory of your servlet container or ap-

Farsi Arabian CP1256

Finnish Finnish_Swedish CP1252

French French CP1252

German Latin1_General CP1252

Hebrew Hebrew CP1255

Italian Italian CP1252

Japanese Japanese CP932

Netherland Latin1_General CP1252

Norwegian Danish_Norwegian CP1252

Russian Cyrillic_General CP1251

Spanish Modern_Spanish CP1252

Swedish Finnish_Swedish CP1252

UTF-8 UTF8

UTF-16 UNICODE

Table 2-1: Some code page settings for the jTDS JDBC driver

Region Collation jTDS Charset


8/2/2019 Install 370

31/66


plication server as described below. Don't forget to choose the right character set.

2.5.4 Oracle DatabaseTrack+ has been tested to run with Oracle 9i, Oracle 10g, and Oracle 11gdatabases. This documentwill not cover how to setup a database in Oracle. Once your database administrator has set up a da-tabase and granted you the privileges to create and modify objects in your schema you can use thescripts from the Track+ database package that you have already extracted to UNZIP_DBASE_DIR tocreate the Track+ tables and indices in your database. We will assume that the database is namedtrack and that it is your default database. Your database user name we assume to be trackp, pass-word tissi. If you are later on running the Track+ application as a different database user you would

have to provide synonyms for each table, which is something you should try to avoid.sqlplus trackp/tissi

SQL> @/Oracle/id-table-schema.sql;

SQL> @/Oracle/track-schema.sql;

SQL> @/Oracle/quartz.sql;

SQL> @/populate.sql;

SQL> quit;

If you use Track+ with Oracle you need to download the appropriate JDBC driver. Unfortunately,

Oracle has a difficult history with their JDBC driver database data type to Java data type mapping.As far as Track+ is concerned, this pertains particularly to the date, time, and timestamp data type.Here are some hints:

If you are using Oracle 9.0 you may be best off with the latest version of the JDBC driver inclasses12.zip. You have to drop classes12.zip into the Track+ lib directory. Rename thisfile to classes12.jar to have it included into the class path. This is required on some applicationservers that do not search zip archives for classes (e.g. Tomcat).

If you are using Oracle 9.2 or Oracle 10g and the JDK 1.4, use the JDBC driver provided inojdbc14.jar. You have to drop this file into the Track+ lib directory.

Some application servers add their own class libraries to the path; with Oracle OC4J there could bea problem that it might give you a different JDK and JDBC driver than what you think. Make sureyou have the right JDK and onlythe Oracle driver in the classpath mentioned here.

For more information on possible Oracle related problems you may want to have a look at the Oracletechnology support site, particularly at http://www.oracle.com/technology/tech/java/sqlj_jdbc/htdocs/jdbc_faq.htm#08_01 or at the Track+ forum, searching for Oracle. If

you are upgrading from a previous release make sure that all date related fields for which you like to


8/2/2019 Install 370

32/66

p g

see the time as well are defined as TIMESTAMP in the database.

Earlier Oracle JDBC drivers hat a limit of 4000 characters on the size of VARCHAR2 fields, which

in Track+ are used for description and storing preferences. It has been reported that these restrictionshave been removed with the drivers for Oracle 10g. If you feel restricted by the size limitation youshould get the new JDBC driver, which also works for Oracle 9.2, and resize the description and pref-erence fields in the database. These are:

TBASELINE.REASONFORCHANGE

TPERSON.PREFERENCES

TSTATECHANGE.CHANGEDESCRIPTION

TTRAIL.CHANGEDESCRIPTION

TWORKITEM.PACKAGEDESCRIPTION

TPRIVATEREPORTREPOSITORY.QUERY

TPROJECTREPORTREPOSITORY.QUERY

TATTACHMENT.FILENAME

TATTACHMENT.DESCRIPTION

TATTACHMENT.CRYPTKEY

TSITE.ALLOWEDEMAILPATTERN TSITE.ATTACHMENTROOTDIR

TSITE.PREFERENCES

TGROUP.PREFERENCES

Of course, you can only change those that restrict you in your application scenario.

2.5.5 IBM DB2 Database

Track+ supports IBMs DB2 database. Here are some hints how to proceed.

1. Install DB2 and create a new database (for example named TRACK). The schema nameshould be the same as the database user name you will be using later on to connect theTrack+ software with the database. You should have enough table spaces. The default is 4k,and you should choose 32K. If the table space is not sufficient the scripts will not run.

2. You have to change the date strings in file .../dbase/populate.sql to have the rightformat, which is YYYY-MM-DD hh:mm:ss.nnnnn, and set the dates in the two INSERT


8/2/2019 Install 370

33/66

INTO TPERSON statements to the time pattern above. Alternatively, delete the two datefields (TOKENEXPDATE and EMAILLASTREMINDED) from these insert statements.

3. Make sure the current schema matches the database user name. Run the scripts:.../dbase/DB2/id-table-schema.sql.../dbase/DB2/track-schema.sql.../dbase/DB2/quartz.sql.../dbase/populate.sql

in this order.

4. Obtain a suitable JDBC driver for DB2 from the IBM download area (for exampledb2java.jar). Place it into your Track+ installation, directory ...webapps/track/WEB-INF/lib.

5. Change the Torque.properties to map to db2. Comment out all other similar entries andenable the following entries:

torque.dsfactory.track.connection.user = yourDB2Username

torque.dsfactory.track.connection.password = yourDB2Password

#DB2

torque.database.track.adapter=db2app

torque.dsfactory.track.connection.driver =COM.ibm.db2.jdbc.app.DB2Driver

torque.dsfactory.track.connection.url =jdbc:db2:TRACK

2.5.6 PostgreSQL

Track+ supports PostgreSQL 8.x databases. Be aware that there have been reports of slow perfor-

mance on PostgreSQL version 8.x. Here are some hints to get a Track+ database on a PostgreSQLserver. The following assumes that you are currently on the Postgres directory of the databasepackage, and that the PostgreSQL utilities are in your path.

$createuser --username=postgres --password -d -P -A --sysid=501 trackp

>Enter password for new user:

>Enter it again:

>Password:

>CREATE USER


8/2/2019 Install 370

34/66

$createdb --owner=trackp --username=trackp --password track "Track+ Database"

>Password:

>CREATE DATABASE

>Password:

>COMMENT

$ psql.exe -f id-table-schema.sql track2 trackp

>Password:

...

$ psql.exe -f track-schema.sql track2 trackp

>Password:

...

$ psql.exe -f quartz.sql track2 trackp

>Password: ...

You have to insert a BEGIN in the first line of the populate.sql script before you can run it inorder to start a transaction. Then execute

$ psql.exe -f ../populate.sql track2 trackp

>Password:

...

2.5.7 SAP DB Database

There are several users reporting that they have Track+ running successfully with SAP DB. However,this RDBMS is not in the rollout test plans and therefore not officially supported.

2.6 Step 4: Installing an Application Server

To run Track+, you have to have an application server or at least a servlet container according to serv-

let specification 2.2 and Java Server Pages specification 1.1 running.Track+ offers the option to render charts and diagrams to get a quick project overview. The chartingcode uses the JFreeChart library. JFreeChart requires a running windowing system on the server, e.g.the X11 windowing system on Unix systems, to work correctly. If on your server a windowing systemis not enabled, you would for example get the following error:

java.lang.InternalError: Can't connect to X11 window server

using ':0.0' as the value of the DISPLAY variable.

The best workaround is to set the headless property to true. For Tomcat, the catalina.sh

Step 4: Installing an Application Server 29

8/2/2019 Install 370

35/66

script can use an environment setting:

setenv CATALINA_OPTS -Djava.awt.headless=true

After you have installed your servlet container or application server as described below, and after youhave configured the database connection settings Track+ should be ready to use. For your first logon,there is the system administrator admin with password tissi already predefined in the database.

After this prologue, we now describe the installation for some of the more popular application serv-ers.

2.6.1 Apache Tomcat

Some Linux distributions already include a Tomcat version; it is recommended to work with a pro-duction version 5.5.x or later.

Install the Tomcat package under /opt/jakarta/tomcat. Make sure that the shell files under /opt/jakarta/tomcat/bin are executable. You may want to consult the Tomcat installation in-structions to help you with the details. As $JAVA_HOME set the path where you installed the JavaSDK. Execute command (possibly as user root):

/etc/init.d/tomcat start

Check, if you get the Tomcat default start page under http://localhost:8080. Thereafter, shutdown the server again:

/etc/init.d/tomcat stop

You should now have a running Tomcat servlet container. If you have not been successful there areusually two main reasons:

1. port 8080 is already used by another HTTP server

2. you have not set $JAVA_HOME to the right pathIf you want to have a more professional installation with all security issues considered you shouldintegrate the Tomcat servlet container with an Apache HTTP server. How to do this is well describedin the documentation that comes with Tomcat. Depending on how you configured your distributionyou may have to disable Zope and the JServ module to avoid conflicts on port 8080.

Installation of the Windows version of Tomcat is straightforward and doesn't require any specialskills as long as Tomcat is run stand alone. You may have to set the $JAVA_HOME environment vari-able to the location where you installed the Java SDK, either in the Tomcat startup scripts or in the


8/2/2019 Install 370

36/66

Windows System Control panel. Sometimes port 8080 is already used by some other server on yourcomputer. Select a different port then for Tomcat, such as 80. You can configure this in the serv-er.xml file in the Tomcat conf directory.

In the following it is assumed that Tomcat has been installed under $TOMCAT_HOME, e.g. /opt/jakarta/tomcat for Linux based systems, and c:\Program Files\Apache Software Foun-dation\Tomcat for Windows based systems. To install the Track+ application:

1. Change to the $TOMCAT_HOME/webapps directory:

cd $TOMCAT_HOME/webapps

2. Create a new directory there named track and change into this directory. You can name

it differently, but it determines under which address (URL) your Track+ installation will befound later on. In this case it will be found under http://:8080/track:

mkdir track

cd track

3. Copy the track-v.war file of this distribution into the $TOMCAT_HOME/webapps/track directory.

4. Unpack the file like this:$JAVA_HOME/bin/jar -xvf track-v.war

or (Windows):

%JAVA_HOME%\bin\jar -xvf track-v.war

5. Start the Tomcat servlet container

/etc/init.d/tomcat start (on Linux)

or use the Windows Tomcat startup batch file or the Configure Tomcat utility.

If you get out of memory errors try to configure your JVM different from the default options. Forexample, on a Linux Server with Sun JDK 1.5 and 512 MByte of main memory we have configuredthe following JAVA_OPTS in catalina.sh:

JAVA_OPTS=-XXPermSize=128M -XX:MaxPermSize=196M -Xms196M -Xmx384M


8/2/2019 Install 370

37/66

2.6.2 Integrating Apache Tomcat with IIS6

Prerequisites

Make sure you have a running instance of a Microsoft Windows 2003 Server with IIS6 installed

Java 2 Standard Edition Developer Kit JDK 1.5.0 or later

Jakarta Tomcat 5.5 or later

Jakarta Tomcat Web Server Connector JK2 for IIS6 (from http://archive.apache.org/dist/jakarta/tomcat-connectors/jk2/binaries/

win32/jakarta-tomcat-connectors-jk2.0.4-win32-IIS.zip)

Make sure you have the JDK and Tomcat installed before you proceed, using the installers provided.

Configure the Track+ Context

Follow the instructions of installing Track+ under Tomcat. Make sure you can reach Track+ directlyunder Tomcat like this:

http://www.yoursite.com:8080/track

Make sure that Tomcat does not use port 80. For this you may have to edit the proper section in the

conf/server.xml file of the Tomcat directory.

Run the IIS-Tomcat-Connector Installer

Setting up IIS to run with the Tomcat connector is very tedious. To simplify the procedure, there isan installer available at the download site.

2.6.3 Oracle WebLogic (Former BEA)

Oracle WebLogic is a powerful commercial application server. Track+ runs on Oracle WebLogic

with no restrictions. You can deploy Track+ in either exploded or unexploded mode using thetrack-v.ear file.

To install Track+ on Oracle WebLogic you have to first extract the track.war file contained intrack-v.ear:

jar -xvf track-v.ear track.war

You now have a track.war file in the same directory as the track.ear file. Extract file WEB-INF/Torque.properties from the track.ear file:


8/2/2019 Install 370

38/66

jar -xvf track.war WEB-INF/Torque.properties

Change to directoryWEB-INF and modify the Torque.properties file as described further downin section 2.10. Basically, this configures your database connection. Thereafter you jar everythingback together:

jar -uvf track.war WEB-INF/Torque.properties

jar -uvf track-v.ear track.war

You can now deploy the application using the standard BEA WebLogic deployment procedure. Youhave to set the attachment directory on the server configuration page (see section 3.5.1) when usingOracle WebLogic. Otherwise attachments may not work properly or you will loose all attachmentsonce the server goes down.

Figure 2-2: The IIS-Tomcat connector installer


8/2/2019 Install 370

39/66

2.6.4 JBoss

JBoss is a very popular Java applications server. You can obtain it from http://www.jboss.org

(about 75 MByte).Track+ does run successfully with JBoss 4.x, while there are classpath loader problems on JBoss 5.x.Follow the instructions of installing JBoss. In particular, adapt the $JAVA_HOME variable in theJBoss startup scripts to the path where you had installed your Java SDK. Make sure that the portsyou want to serve on aren't being used by another (web) server on your machine.

To install Track+ you have to unjar the track-v.war file and modify the Torque.propertiesconfiguration files as described further down in section 2.10. Thereafter you jar it again to a filetrack.war and copy it to the JBoss deployment directory. If you have properly installed your RD-

BMS (see section 2.5) Track+ should be ready to use.Alternatively, you could use the track-v.ear file for deployment. Look at the description for theBEA WebLogic server for instructions on how to do this.

You have to set the attachment directory on the server configuration page (see section 3.5.1) whenusing JBoss. Otherwise you will loose all attachments once JBoss goes down.

2.6.5 Sun ONE Webserver

Sun One is a professional and performant web server and servlet container. We assume you have gotyour package from the Sun website and installed the server software itself, and that you have createda virtual server (see Fig. 2-3).

The Sun ONE server comes with a default upload limit of application file sizes of 10 MByte. Sincethe Track+ application is much larger, this limit has to be changed for upload installation. To changethe limit, go to $SERVER_ROOT/bin/https/webapps/admin-app/WEB-INF/web.xml fileand make a backup copy. Edit this file and in the servlet webappdeploy, insert an ini-paramnamed maxUploadSize with a value in bytes specifying the maximum upload size. Example(Track+ requires about 100 MByte, so this gives us some room for growth):

webappdeploy

com.sun.web.admin.servlets.DeployServlet

maxUploadSize

80000000

To apply these changes restart the server, for example via the Windows services manager.


8/2/2019 Install 370

40/66

Once you have made these changes, and have added a virtual server, hit the manage button thatshows right to the selected virtual server in Fig. 2-4, and then the Virtual Server Class tab selectoron the next screen. Select the proper virtual server in the selection box, and hit the manage buttonnext to it.

On the screen than comes up then select the Web Applications tab, and deploy the WAR file thatyou downloaded from the Track+ site.

Before you can operate Track+, you will have to properly configure the database connection (see sec-

tion 2.10). The Torque.properties file can be found in $SERVER_ROOT//we-bapps//track, in case you have deployed the application under the URI /track.

Once you are done with all this, hit the Apply changes link in the upper right corner, and youshould be ready to go.

Figure 2-3:Adding and managing a server

Step 5: Configuring the Database Connection 35

8/2/2019 Install 370

41/66

2.7 Step 5: Configuring the Database Connection

2.7.1 Modifying Torque.propertiesThe Track+ application ships with a default user and password for the database. This default userand password is contained in the file under $YOUR_SERVLET_CONTAINER_HOME/webapps/track-v/WEB-INF/Torque.properties. The following is an excerpt and the respective areasare shown.

...

# !!! THIS USER WITH THIS PASSWORD HAS TO BE KNOWN BY YOUR

# DATABASE SYSTEM !!!

Figure 2-4: Managing a virtual server and virtual server class


8/2/2019 Install 370

42/66

torque.dsfactory.track.connection.user = friedjtorque.dsfactory.track.connection.password = tissi

#

#-------------------------------------------------------------

#

# In this section the driver for your database management

# system needs to be enabled. This depends on what kind of

# RDBMS (Interbase, MySQL, etc.) you have and possibly on

# what kind of operating system the database server is running.

# Of course, ONLY ONE DRIVER CAN BE BE ENABLED AT A TIME!!

##

# 1) Firebird on Windows 32. Use for Firebird version > 1.0

torque.database.track.adapter=firebird

torque.dsfactory.track.connection.driver = org.firebirdsql.jdbc.FBDriver

torque.dsfactory.track.connection.url = jdbc:firebirdsql://localhost/D:

/Daten/trackdata/track.gdb

# 2) Firebird on Unix

...

Figure 2-5: Deploying the Track+ application

Step 6: Installing Graphviz 37

8/2/2019 Install 370

43/66

If the password is changed in this file it has also to be changed for the database and vice versa. ForFirebird and Interbase, the IBConsole utility can be conveniently used for this task. If the user nameshould be changed as well, it has to be made sure that the new user has complete SELECT, DELETE,

INSERT, UPDATE, AND REFERENCE permissions for all tables, functions, and generators of theTrack+ application. The database user acts as a proxy only and doesn't appear anywhere in the userspace.

The second item that needs to be configured is the URL of the database and the database driver. Ex-amples are given for various database systems in the Torque.properties file. For non-standardcharacter sets have a look at section 2.7.2.

After changing any of the settings in Torque.properties the servlet container Tomcat has to berestarted for the changes to take effect.

2.7.2 Example for Non-Western Character Sets

The configuration of the database character encoding very much depends on the database system be-ing used, so no general instructions can be given here. For Track+ running with MySQL, here arestep by step instructions for a Hebrew localization:

1. Find the file my.ini (in case of Windows) or my.cnf (in case of Linux) for the MySQLinstallation. In section [mysqld] add or modify a line to

default-character-set=hebrew

Restart the MySQL server after the change.

2. In file Torque.properties change connection URL for MySQL to

torque.dsfactory.track.connection.url =

jdbc:mysql://localhost:3306/mytrackplus?

useUnicode=true&characterEncoding=Cp1255

You have of course to use the correct database name and server name of your installation.

3. In the site configuration menu change the e-mail character encoding to ISO-8859-8.

After these changes restart your application server.

2.8 Step 6: Installing Graphviz

In order to have a graphical display of workflows the Graphviz software, a third party product, needs

to be installed on the server running Track+. You can obtain it free of charge from http://


8/2/2019 Install 370

44/66

www.graphviz.org. You will have to tell Track+ where you have installed this package later onwhen you configure the system for the first time.

2.9 Step 7: Installing Subversion Support

If you like to connect Track+ to your Subversion repository you need an additional library, whichyou can freely download from http://www.trackplus.com/subversion.html.

Place the file into the lib directory (under webapps/track/WEB-INF/lib) of your Track+ ap-plication and restart your server.

2.10 Remaining StepsAt this point you should have completed the basic installation procedure and after you have restartedyour application server or reloaded the Track+ application you should be able to log into the systemby pointing your browser to the URL under which you have installed the system.

Some configuration steps remain to be done to get the Track+ configured and ready to serve projects.This mostly concerns e-mail connection setup, and configuration of directories for attachments andindexes. These steps are outlined in Fig. 2-6.

These configuration steps are carried out using the regular Track+ web browser user interface so thereis no need to directly work on the server any more from this point on.

The details of the remaining configuration steps are described in the next chapter.

2.11 Troubleshooting

Most problems that will occur with a Track+ installation are related to the database system softwareand your application server.

It is beyond the scope of this document to deal with these issues in detail. Please have a look at theTrack+ forum in case you should run into any trouble.

As owner of the commercial version, you will get e-mail and telephone support. Otherwise you willbe supported by the public forums.

If you have trouble installing Track+, do the following:

1. describe your problem and all error messages you get

2. tell us what application server, database server, Java environment and operating system you

are using

Troubleshooting 39
http://-/?-http://-/?-http://-/?-

8/2/2019 Install 370

45/66

3. post or e-mail your Torque.properties file

Sometimes it is helpful to enable Track+ logging messages. These messages usually go to the appli-cation servers console or redirected console output file. Logging is configured via a dedicated admin-istrative function when you login as admin user.

Install Track+

Install Graphviz

Install Application Server

Install Database Server2. Authorizing E-Mail Domains

3. Configuring E-Mail Submission

4. Configuring LDAP Connection

5. Configuring Attachment Directory

Figure 2-6: Track+ configuration process overview

Install Database Server1. Configuring E-Mail Server

Connection

Install Track+6. Configuring Text Search Index


8/2/2019 Install 370

46/66

3

8/2/2019 Install 370

47/66

41

3

Configuring Track+This chapter describes the minimum configuration steps you need to do after a first installation, andbefore you can use your Track+ system productively. In particular, the following topics are consid-ered:

First login and access to server configuration

Entering license key information (optional)

Setting up E-mail

Setting up full text search Setting up attachment handling

Configuring for operation in proxied environments (optional)

Configuring Graphviz

Configuring session time out

3.1 First Login and Access to Server Configuration

To carry out the configuration steps in this chapter you have to login as system administrator. Thesystem administrator account is created during database installation, using a predefined, default pass-word.

To login as the system administrator use:

user name: admin

password: tissi

42 Chapter 3: Configuring Track+

8/2/2019 Install 370

48/66

There is a second account created during initial setup, the guest account.

To login as a regular guest user with but a few access rights:

user name: guest

password: trackplus

You should change the administrator password before you expose your server to the public. How thisis done is described in the Track+ User Manual.

The admin user has access to all project administration access management pages. It should be herprivilege to add new projects. Each project itself may have several project specific administrators outof the regular user base. These project specific administrators have the same rights as the admin user,except that these rights are limited to specific projects.

You can configure later on any user to have system administrator privileges.

All server configuration steps described below will be managed via menu entry Administration -Manage server - Server configuration....

3.2 Entering License Key Information

The Track+ Community Edition can be operated without any license key. If you use a different li-cense model you have to enter the license key information in the field provided. Just cut and pastethe license key from the key file you received into the text area and save.

Figure 3-1:Accessing server configuration

Setting up E-mail 43

8/2/2019 Install 370

49/66

You should see the number of active users covered and the expiration date of the license.

3.3 Setting up E-mail

3.3.1 Basic E-mail Setup

Track+ will send notification messages to involved users for example if certain state changes occur,new issues are created, or responsible persons are being modified. Track+ also sends initial passwordsafter registration or lost passwords via e-mail.

For this feature to work, Track+ has to be able to connect to an SMTP server. You have to configure

your SMTP server name on the server configuration page as shown in Fig. 3-3.

There are several other options when configuring your e-mail notification service.

Track+ system e-mail:

here you should define an e-mail account which is being inserted as "sent from" byTrack+ in any e-mail the systems sends out. You can further down select however ifthe sent from address of outgoing e-mails is the one of the user initiating the cau-sing action.

Figure 3-2: Entering a license key

http://-/?-http://-/?-

8/2/2019 Install 370

50/66

Use Track+ from address in e-mails:

This switch determines if e-mails coming from the Track+ system carry as their sentfrom address the value given in the previous field Track+ system email, or if it car-ries the address of the person causing the email.

For example, if an issue was changed, the issues manager will be informed of thechange by e-mail (Automail). If the check box mentioned above is checked, the e-mail will have as its sent from address [email protected], and the sent

from name will be Trackplus.If the check box was not checked, the sent from address will appear as Smith, Diana[Track+]. Some SMTP servers do not like to sent messages with a from addressdifferent than the account which has been used to gaining access. In the exampleabove, the SMTP server might not like to use an account [email protected] sending messages from [email protected].

Mail encoding:

You need to define an e-mail encoding that is being used by Track+ when sendingout e-mails. You can select one of the list provided, such as "UTF-8", "koi8-r", or"ISO-8859-1". For Western languages, "ISO-8859-1" usually works fine.

SMTP server name:

For Track+ to be able to send notifications you need to give it the name of yourSMTP server. Some company internal installations do not require authenticationbefore using the server, some do. If authentication is being used, it can be eitherSMTP authentication or POP before SMTP. In the first case you also have to set the

Figure 3-3: Site configuration page, first part


d d d b d b l h d h

8/2/2019 Install 370

51/66

SMTP user name and SMTP password described below. In the second case you haveto configure the POP parameters.

SMTP Port:

Default is 25. Usually, you don't have to change this.

SMTP user name:

In case your SMTP server requires SMTP authentication, supply the user name here.

SMTP authentication mode:

Company internal SMTP servers sometimes do not require special authentication. Ifyour SMTP server does, you need to click the check box and select an authenticationmode. You can use either use a special user/password for the SMTP server, or use thesame user/password as for the incoming mail, or use the POP3 before SMTP authen-tication mode, where you will first be logged in into the POP3 incoming mail server,

and this will authenticate you for the outgoing SMTP mail server.SMTP password:

In case your SMTP server requires SMTP authentication, supply the password here.

Mailserver protocol:

Track+ supports two incoming mail protocols: POP3 and IMAP. Here you canchoose which one your server uses.

Mailserver name:

Figure 3-4: Setting mail encoding and SMTP connection parameters


8/2/2019 Install 370

52/66

In case of POP before SMTP authentication, supply your POP server here. You willalso have to configure this if you want to be able to submit issues by e-mail to eithera POP3 mailbox or an IMAP mailbox.

Mailserver port:

Default is 110 for POP3 and 143 for IMAP. You usually do not have to change this.

Mailbox user:

In case of POP before SMTP authentication, supply your POP user account here.Also supply this if you want to access incoming e-mails by an IMAP inbox.

Mailbox password:

In case of POP before SMTP authentication, supply your POP password here. Also-supply this if you want to access incoming e-mails by an IMAP inbox.

3.3.2 Enabling Issue Submissions by E-mail

Track+ can be configured to accept issue submissions and additions to existing issues via e-mail. Thiscan be quite useful if customers shall not get access to the Track+ database itself, but they shouldchannel their requests via e-mails to a specific account.

Keep messages on server:

If this is checked, reading the e-mails does not delete the messages on the server. Thiscan be helpful if you also want to manually scan the Track+ mailbox.

E-mail submissions:

If this is turned on, it is possible to submit issues by sending e-mails to the Track+

Figure 3-5: Configuring the incoming e-mail connection parameters


8/2/2019 Install 370

53/66

mailbox. The subject of the e-mail is copied into the title field of the issue, the text of

the e-mail is copied into the description field. Attachments are added as attachments.The issue is created in the project declared as e-mail default project (see below). If thesubject of the e-mail starts with a positive integer, Track+ will try to find an appropri-ate issue number. If successful it will add the e-mail as comment to the issues. If theissue number could not be found, a new issue will be created.

Accept unknown sender:

If this is checked, e-mails from users not registered with the Track+ system are accep-ted and can create new issues. Nonetheless, the e-mail domain has to match the allo-wed e-mail domain pattern (see below). E-mails from senders whose domain doesnot match the pattern are silently disregarded.

E-mail default project:

Issues submitted by e-mail are created in this project (catch all project). Be aware thatit is also possible to create a separate mailbox for each project. This can be done inthe project configuration area.

3.3.3 Authorizing E-mail DomainsTo prevent users from unverified domains (e.g. hotmail.com, gmx.com) to register, a Perl5 regularexpression can be defined so that only e-mail domains matching that expression are allowed to reg-ister. The default pattern is to allow all domains to register.

Track+ can be configured such that users may register themselves. However, you can restrict registra-tion to specific domains and even user email accounts, for example such that only your customers areallowed to register with the system. The pattern that is allowed to register is a Perl pattern. F

Example pattern:

Figure 3-6: Configuring e-mail issue submission


8/2/2019 Install 370

54/66

[^@ \t]@bosch\.com

This example permits just users from domain bosch.com to register. Some more examples:

[^@ \t]@t-online\.de|[^@ \t]@computer\.org

matches all users from domains t-online.de and computer.org. The pattern

\w[-.\w]+\@[-.\w]+\.\w{2,3}

matches all e-mail domains with no restrictions. This is the default pattern.

3.4 Setting up Full Text Search

Track+ uses the Lucene indexing system to search for issues based on keywords. The index systemcan be configured using several parameters.

Figure 3-7:Authorizing domains for registration and issue submission by e-mail

Figure 3-8: Full text search configuration parameters

Setting up Attachment Handling 49

Enable full text search:

8/2/2019 Install 370

55/66

Enable full text search:

Here you can enable TQLplus. If this is not set, TQLplus syntax is not recognized.You can disable this if you have only little disk space left.

Index attachments:

This enables indexing of attachments. Since attachments can be quite large, settingthis option will increase disk usage by Track+ considerably.

Reindex on startup:

If you want to start a complete reindex after server startup set this switch. This ensu-res that your index is complete. It also purges index entries that may not be neededany more. Take into consideration that it may take some time until the index is com-

plete again.Lucene analyzer:

Choose the preferred analyzer for your index. A good analyzer gets rid of small wordsof little importance like "a" or "the" and so on. This is of course language dependent,so if you have an analyzer that matches the primary language of the installation enterit here. New analyzers can be added if you pack them into a file "lucene-analy-zers.jar" and drop this file into the lib directory of the Track+ application. The safebet is to use the Standard Analyzer.

Lucene index root directory:

This is where Track+ will place the index file. Depending on the size of your docu-ments disk space requirements can become quite large. Make sure there is enoughspace at this location.

3.5 Setting up Attachment Handling

3.5.1 Setting up the Attachment Root Directory

Attachments are stored on the file system and not in the database. You should configure a directoryon a volume with sufficient space for your attachments. If you do not configure this parameter, at-tachments will be stored inside the application directory. This could result in complete loss of all at-tachment data on some application servers!


8/2/2019 Install 370

56/66

3.5.2 Configuring the Attachment Size Limit

It is possible to limit the size of attachments to prevent people from loading Gigabytes on the Track+

server. The limit can be set to any amount of MBytes. The default size limit is 4.0 MByte.

3.6 Configuring for Operation in a Proxied Environment

Track+ has been designed to operate in a proxy environment. Usually, Track+ can extract the URLsthat are included in notification e-mails automatically. This automatic detection works fine if thereare no proxy servers between the application server and the user clients. If there is a proxy server hid-ing the application server, the correct server URL has to be configured via parameter Track+ Server

URL on the site configuration page, for example:http://gandalf

In non-proxied environments, you can leave this field empty, which will enable the automatic detec-tion feature for the server URL.

Figure 3-9: Configuring attachment root directory and maximum attachment size

Configuring Graphviz 51

3.7 Configuring Graphviz

8/2/2019 Install 370

57/66

3.7 Configuring Graphviz

In order to have a graphical display of workflows the Graphviz software, a third party product, needsto be installed on the server running Track+. Inside of Track+ you have to enter the complete pathto the Graphviz executable, like

C:\Program Files\ATT\Graphviz\bin\dot.exe

on a Windows machine or something like

/opt/att/graphviz/dot

on a Unix machine. Temporary files are stored in a subdirectory of the attachment folder.

3.8 Configuring Session Time Out

In file web.xml a cookie time out can be set, to allow a user to directly access an issue without havingto log on. Usually you would not change the default value.

In the same file you can define the session time out. If there are no requests sent during this timefrom a client to the server, the server terminates that session and the user would have to log in againto access the system.

Figure 3-10: Setting the path to the graphviz executable


8/2/2019 Install 370

58/66

4

8/2/2019 Install 370

59/66

53

4

Uninstalling Track+

4.1 Uninstalling Track+ from Windows (Installer)

When Track+ was installed using the Windows installer, several packages have been installed andneed to be removed for a complete uninstall:

Track+ itself

Firebird database server

Apache Tomcat servlet container

Graphviz package

The following describes the procedure how to uninstall Track+ when it was installed using the Win-dows installer.

1. Go to the Windows System Control page.

2. Select the Software icon and select Track+: remove.

3. The remove will not remove the data that you have accumulated with Track. If you want toremove all data, go to which is typically C:\ProgramFiles\Track+ and remove the Database and trackdata directories, or the entireTrack+ installation directory.

4. If you are not using the Firebird database server for anything else, remove it using the Soft-ware icon as described above for Track+.

5. If you are not using Apache Tomcat for anything else, remove it using the Software icon asdescribed above for Track+.

54 Chapter 4: Uninstalling Track+

6. If you are not using the Graphviz package for anything else, remove it using the Softwared b d b f T k

8/2/2019 Install 370

60/66

icon as described above for Track+

This will remove all registration entries and files that have been placed on your computer by Track+.

4.2 Uninstalling Track+ from Windows

If you have not used the installer for a Track+ installation on Windows, the procedure to removeTrack+ depends on the type of application server and database server you have been using. The fol-lowing items have to be removed, unless you are using them for anything else as well:

Track+ itself

Database server Servlet container or application server

Graphviz

Track+ itself consists of

the applications WAR or EAR file in the webapps directory of your servlet container

the expanded directory for Track+ in the webapps directory of your servlet container

the attachment and indexing files

The attachment and indexing files can reside anywhere on the disk, you would have to check on theAdministration-Server Admin. dialog for the paths of these directories.

4.3 Uninstalling Track+ from Unix

The uninstall procedure for Track+ from a Unix system depends the database server and servlet con-tainer you have been using for Track+. The following items have to be removed, unless you are still

using them for something else: Track+ itself

Database server

Servlet container or application server

Graphviz

Track+ itself consists of

Uninstalling Track+ from Unix 55

the applications WAR or EAR file in the webapps directory of your servlet container

8/2/2019 Install 370

61/66

the expanded directory for Track+ in the webapps directory of your servlet container

the attachment and indexing files

The attachment and indexing files can reside anywhere on the disk, you would have to check on theAdministration-Server Admin. dialog for the paths of these directories.

56 Chapter 4: Uninstalling Track+

8/2/2019 Install 370

62/66

57

Index

8/2/2019 Install 370

63/66

Aadmin user . . . . . . . . . . . . . . . . . . . . . . 42administrator password . . . . . . . . . . . . . 42Apache Tomcat . . . . . . . . . . . . . . . 29, 31application server

installation . . . . . . . . . . . . . . . . . . 28attachment

configuration root directory . . . . . 50

BBEA Weblogic . . . . . . . . . . . . . . . . . . . 31

Ccharacter sets

non-western . . . . . . . . . . . . . . . . . 37configuration . . . . . . . . . . . . . . . . . . . . 38

attachment root directory . . . . . . . 50

Graphviz path . . . . . . . . . . 37, 38, 51Track+ . . . . . . . . . . . . . . . . . . . . . . 38

DDB2 database . . . . . . . . . . . . . . . . . . . . 26

Ee-mail

authorizing domains . . . . . . . . . . . 47Example . . . . . . . . . . . . . . . . . . . . . . . . 37

FFirebird RDBMS

installation in Linux . . . . . . . . . . . 21installation on Unix . . . . . . . . . . . . 21installation on Windows . . . . . . . . 22

Ggraphdoesnt show . . . . . . . . . . . . . . . . . 28

Graphviz . . . . . . . . . . . . . . . . . . . . . . . 37installation . . . . . . . . . . . . . . . 37, 51

II18N . . . . . . . . . . . . . . . . . . . . . . . . . . 37IIS6 . . . . . . . . . . . . . . . . . . . . . . . . . . . 31installation

application server . . . . . . . . . . . . . 28SDK . . . . . . . . . . . . . . . . . . . . . . . 17Tomcat . . . . . . . . . . . . . . . . . . 29, 31

Installer . . . . . . . . . . . . . . . . . . . . . . . . 18

JJava SDK . . . . . . . . . . . . . . . . . . . . . . . 17

JBoss . . . . . . . . . . . . . . . . . . . . . . . . . . 33JRE . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

LLinux

installation of Firebird RDBMS . . 21Logging . . . . . . . . . . . . . . . . . . . . . . . . 39

MMS SQL Server . . . . . . . . . . . . . . . . . . 23MS SQL Server RDBMS

installation . . . . . . . . . . . . . . . . . . 23MySQL . . . . . . . . . . . . . . . . . . . . . . . . 19

OOracle

database installation . . . . . . . . . . . 25

58

Oracle Weblogic . . . . . . . . . . . . . . . . . .31

P

installation of MS SQL . . . . . . . . . .23Windows installer . . . . . . . . . . . . . . . . .18
http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://install.pdf/http://insta

install 370

Documents