Collabnet Teamforge 5.3

CollabNet TeamForge 5.3

System Administrator Guide

CollabNet TeamForge 5.3 | TOC | 3

Contents

Chapter 1: Set up a CollabNet TeamForge site ...... 9 Install a CollabNet TeamForge site on dedicated hardware...... 10 Set up hardware for CollabNet TeamForge ...... 10 Get CollabNet TeamForge 5.3 ...... 11 Specify your CollabNet TeamForge site©s host and domain names...... 11 Do some basic configuration on your CollabNet TeamForge site...... 12 Install the CollabNet TeamForge application...... 13 Supply your TeamForge license key...... 15 Install an advanced CollabNet TeamForge site ...... 15 Set up hardware for an advanced CollabNet TeamForge installation ...... 15 Get CollabNet TeamForge 5.3 ...... 16 Configure your CollabNet TeamForge site...... 17 Install the CollabNet TeamForge application...... 19 Set up the database for your CollabNet TeamForge site...... 20 Start your new CollabNet TeamForge site...... 22 Supply your TeamForge license key...... 23 Install CollabNet TeamForge on a virtual machine...... 24 Get CollabNet TeamForge 5.3 ...... 24 Configure CollabNet TeamForge ...... 25 Supply your TeamForge license key...... 26 Upgrade to CollabNet TeamForge 5.3 ...... 27 Upgrade to CollabNet TeamForge 5.3 on the same hardware...... 27 Upgrade to CollabNet TeamForge 5.3 on new hardware...... 31 Upgrade to CollabNet TeamForge 5.3 on a virtual machine...... 36 Install a different build of the same release...... 38

Chapter 2: Support CollabNet TeamForge users...... 39 Authenticate users with LDAP...... 40 Set up LDAP integration for the CollabNet TeamForge server...... 40 Set up LDAP for a CVS integration server...... 41 Modify the application policy...... 44 Let users see what©s in a project template...... 44 Permit big file uploads...... 45 Run CollabNet TeamForge in a local language...... 45 Specify where your TeamForge site©s online help comes from...... 46

Chapter 3: Grow your CollabNet TeamForge installation...... 47 Set up source control on its own server...... 48 4 | CollabNet TeamForge 5.3 | TOC

Set up the database for your CollabNet TeamForge site on a separate server...... 48 Set up a PostgreSQL database on its own server...... 49 Set up an Oracle database on its own server...... 50 Set up a PostgreSQL database...... 51

Chapter 4: Protect your CollabNet TeamForge site...... 53 Set up SELinux...... 54 Protect Apache with SSL...... 54 Set up Apache for SSL encryption...... 54 Generate Apache SSL certificates...... 55 Prevent HTTPS cracking...... 56 Protect integrations with SSL...... 56

Chapter 5: Maintain your CollabNet TeamForge installation...... 59 Monitor services on your site...... 60 Get information about a CollabNet TeamForge site...... 60 Patch CollabNet TeamForge ...... 61 Apply a patch...... 61 Apply a patch without a network connection...... 62 Revert a patch upgrade...... 63 Troubleshoot patches...... 65 Specify DNS servers...... 65 Optimize PostgreSQL with vacuum...... 66 Change the location of a log file...... 66 Back up and restore CollabNet TeamForge data...... 66 Restore backed-up CollabNet TeamForge data...... 67 Back up a PostgreSQL database...... 67 Restore a PostgreSQL database...... 67

Appendix A: General questions about using TeamForge...... 69 What does it take to install CollabNet TeamForge ?...... 70 What is the recommended installation method for SourceForge? ...... 70 Do I need an advanced TeamForge install?...... 71 How many servers do I need to run a CollabNet TeamForge site?...... 71 Which application runs on which server?...... 72 How does SourceForge Enterprise Edition (SFEE) handle third-party applications?..73 Which ports should I keep open?...... 73 How does SourceForge Enterprise Edition (SFEE) manage security?...... 74 How does CollabNet TeamForge help protect data access?...... 74 What user activities are tracked?...... 75 How does CollabNet TeamForge help protect my data?...... 75 Does TeamForge work with LDAP?...... 75 J2EE Architecture and security...... 76 CollabNet TeamForge 5.3 | TOC | 5

What security tools come with CollabNet TeamForge ?...... 76 What is a CERT advisory?...... 77 Should I move my TeamForge database to its own server?...... 77 Should I move my source control application to its own server?...... 78 Is it possible to change artifact prefixes in TeamForge? ...... 78 What is the suggested log configuration for a production system? ...... 78 Can I run other java applications in the same JBoss instance as CollabNet Team Forge?....78 How does TeamForge handle multiple redundant LDAP servers? ...... 79 Does SourceForge licensing have any dependencies on IP address of server?...... 79 What is the recommended installation method for SourceForge? ...... 79 Who is responsible for applying OS updates to the underlying VMware image? ...... 80

Appendix B: Concepts and terms in TeamForge...... 81 What does it mean to run CollabNet TeamForge on a virtual machine?...... 82 What is a patch?...... 82 What is the look project?...... 82 What wiki engine does SFEE use? ...... 83 Does CollabNet TeamForge support merge tracking?...... 83 What is a private IP address and what are the private IP ranges? ...... 83 What is the vamessages.log used for?...... 83 How do I use the SourceForge updater to manage backups of old versions of SourceForge?.84

Appendix C: Common errors in TeamForge...... 85 Why won©t my CollabNet TeamForge virtual machine installation start?...... 87 Why does my CollabNet TeamForge site show a different time than the host machine it is running on?.87 Why does my CollabNet SourceForge Enterprise site show a different time than the host machine it is running on?.87 Why won©t my CollabNet SourceForge Enterprise virtual machine installation start?...... 88 Why don©t the branding repo changes get rendered into UI? ...... 88 After switching to ADS authentification, why did the Create button disappear from the user admin section? ...... 89 How can I solve the PSQLException when starting the app server after changing my DB server IP address? ...... 89 Why do search and email server show "Could not connect"? ...... 89 Why does the server lock up when SVN commits are performed in VM edition? ...... 89 Why is the password and login shell changed for users on my cvs/svn server? ...... 89 JBoss crashed with out of memory error, how do I prevent this? ...... 90 Why don©t help links in TeamForge work after upgrade from SourceForge Enterprise 4.4?....90 Why am I getting "Could not connect" status for email and search server? ...... 90 Why is my email taking a long time to arrive? ...... 90 Due to firewall restrictions I cannot send email from James. How can I resolve this? ...... 91 Why do we have errors creating or altering repositories and adding or removing users?...... 91 Why does the SOAP service show "could not connect" on the Server Status page when everything else appears to work?.91 6 | CollabNet TeamForge 5.3 | TOC

Why do I get a server status error when I perform a search?...... 92 Why would some users not get email?...... 92 What does the "psql: could not connect to the server: No such file or directory" error message mean? ...... 92 Why do I get a proxy timeout when I try to view certain SCM pages?...... 92 When using SourceForge Explorer version 4.4 SP1 to connect to SourceForge 4.4 SP1, Ireceive the following error message: "Error - wrong number of arguments"...... 93 Why do I get a URL "not found" or "moved permanently" error after applying a patch/upgrade?.93 Why can©t SourceForge send my outbound mail?...... 93

Appendix D: TeamForge roles and permissions...... 95 How do I add users to user membership after upgrading from 5.0 to CTF 5.2?...... 96 Can I set permissions so that users can move documents but not delete them? ...... 96 Can I grant users permissions to create their own accounts? ...... 96 Why can©t Oracle connect to my SourceForge installation?...... 96 Why does SearchReindex.sh fail on SourceForge 4.4?...... 96

Appendix E: Tasks in TeamForge...... 99 How do I post a site wide broadcast?...... 100 How do I enable post-commit logging? ...... 100 How do I authenticate multiple LDAP via Apache? ...... 100 How do I make the monitoring messages be sent from Forge Administrator? ...... 101 How can I remove the RHEL test page after CSFE installation?...... 101 How can I find the number of files in a repository without checking it out? ...... 101 How do I connect to the Teamforge Postgres database? ...... 101 How do I generate a wiki table of contents? ...... 101 What is the correct procedure for modifying a hosted Lab Manager profile? ...... 101 Can I add custom links to the Quick Links section of the application home page? ...... 102 How do I configure the timeout for Apache in TeamForge? ...... 102 How do I back up SourceForge?...... 102 How do I move an existing CVS repository into SourceForge?...... 103 How do I move an existing SVN repository into SourceForge?...... 104 Where do I configure my client proxy settings?...... 104 How do I make SourceForge work the same when the IP address of the server changes?.104 How do I capture the output of "top" command? ...... 105

Appendix F: Managing email in TeamForge...... 107 How do I configure TeamForge to send mail on a specific network adapter in a multi-NIC configuration? ...... 108 How can I check if port 25 is open? ...... 108 How do I set up a local alias via James? ...... 108 How do I configure email notifications of Subversion commits in SourceForge 4.x?...... 109 Does SourceForge support using /etc/aliases for local mail delivery?...... 109 CollabNet TeamForge 5.3 | TOC | 7

Appendix G: Platform information for TeamForge 5.3...... 111 Minimum hardware requirements for CollabNet TeamForge ...... 112 Supported software for CollabNet TeamForge 5.3 ...... 112 Packages required for Red Hat 5...... 113

Appendix H: Scripts...... 115 bootstrap-data.sh...... 116 The collabnet script...... 117 environment_check.sh...... 118 install.sh...... 118 pbl.py...... 119 snapshot.py...... 120 upgrade-site.sh...... 120

Appendix I: Log files...... 123 JBoss logs...... 124 Oracle logging...... 124 SCM (CVS, Subversion, and Perforce) logs...... 124 Email logs...... 125 Search logs...... 125 Project Build Library audit log ...... 126 Profile audit log...... 126 User Audit Log...... 127 Host audit log...... 127 Project audit log...... 127

Appendix J: Configuration files...... 129 TeamForge configuration variables...... 130 ACTIVITY_LINKS_CUSTOMIZATION...... 130 ADMIN_EMAIL...... 130 APPLICATION_LOG_DIR...... 130 APPROVE_NEW_USER_ACCOUNTS...... 131 ARTIFACT_LIST_LIMIT...... 131 CLEARCASE_INTEGRATION_ENABLED...... 131 DATABASE_HOST...... 131 DATABASE_NAME...... 132 DATABASE_PASSWORD...... 132 DATABASE_TYPE...... 132 DATABASE_USERNAME...... 132 DEDICATED_INSTALL...... 133 DOMAIN_localhost...... 133 8 | CollabNet TeamForge 5.3 | TOC

HOST_localhost...... 134 HTTPD_LOG_DIR...... 134 INCLUDE_ORGANIZATION_USER_FIELD...... 135 INITIAL_PASSWORD_CHANGE_ACTIVATION_CODE_TIMEOUT...... 135 INTEGRATION_JAVA_OPTS...... 135 INTEGRATION_LOG_DIR...... 135 JAMES_GATEWAY_HOST...... 135 JAMES_LOG_DIR...... 136 JAMES_POSTMASTER_EMAIL...... 136 JAVA_HOME...... 136 JBOSS_JAVA_OPTS...... 137 LOG_DIR...... 137 MIGRATION_LOG_DIR...... 137 ORGANIZATION_EDITABLE...... 137 PERFORCE_LOG_DIR...... 137 PGSQL_LOG_DIR...... 138 RUNTIME_LOG_DIR...... 138 SEARCH_LOG_DIR...... 138 SITE_DIR...... 138 SSL...... 139 SSL_CERT_FILE...... 139 SSL_KEY_FILE...... 139 SYSTEM_EMAIL...... 139 The patch manifest file...... 140 login-config.xml...... 140 httpd.conf...... 141 iptables...... 142 Chapter 1

Set up a CollabNet TeamForge site

Topics: Installing TeamForge is not difficult, but it can be complex. To succeed, you should be familiar with essential Linux commands and terminology. Most · Install a CollabNet TeamForge commands are given explicitly, but you will sometimes have to substitute values site on dedicated hardware corresponding to your own specific environment. · Install an advanced CollabNet TeamForge site · Install CollabNet TeamForge on a virtual machine · Upgrade to CollabNet TeamForge 5.3 · Upgrade to CollabNet TeamForge 5.3 on a virtual machine · Install a different build of the same release 10 | CollabNet TeamForge 5.3 | Set up a CollabNet TeamForge site

Install a CollabNet TeamForge site on dedicated hardware Navigation title: Install TeamForge on dedicated hardware A dedicated installation is the easiest way to set up CollabNet TeamForge. Minimal configuration is required. All services run on a single server, which the installer sets up. Your server must run only CollabNet TeamForge. If you need to run other applications on the same system, or if other applications on your network must share the site©s database or source control services, see Install an advanced CollabNet TeamForge site on page 15. Important: If you are installing the VMware version of CollabNet TeamForge, see Install CollabNet TeamForge on a virtual machine on page 24.

Tip: Before you start installing, use the umask command to check that any new files created during installation will get the right file permissions. If necessary, change the umask back to the default setting, 0022.

Set up hardware for CollabNet TeamForge Prepare the computer that your site will run on, install Linux and set up networking.

· For information about the operating systems you can use with CollabNet TeamForge, see Platform information for TeamForge 5.3 on page 111.

You must have root-level access to the machine where you are installing CollabNet TeamForge

1. Install the operating system according to the instructions from the OS provider. Note: Do not customize your installation. Select only the default packages list.

Important: If you are installing CentOS 5.3, you must uninstall the PostgreSQL support package and the Dovecot mail server to clear the way for TeamForge to install PostgreSQL. These packages are installed as part of the default CentOS install. Use these commands:

rpm -qa | grep dovecot | xargs rpm -e rpm -qa | grep postgresql-libs | xargs rpm -e

2. Verify that the machine name is resolvable on the network. a) Use the hostname command to verify the name of the machine.

hostname bigbox.supervillain.org

b) Use the nslookup command to verify that your hostname maps to the right IP address.

nslookup bigbox.supervillain.org Server: 204.16.107.137 Address: 204.16.107.137#53

Tip: If there is any doubt about what the system©s real IP address is, use the /sbin/ifconfig command.

3. Make sure port 80 is open. Tip: For detailed firewall requirements, see Which ports should I keep open? on page 73 CollabNet TeamForge 5.3 | Set up a CollabNet TeamForge site | 11

4. Disable SELinux.

Your server is ready.You can now set up the software environment in which you will install CollabNet TeamForge.

Get CollabNet TeamForge 5.3 Navigation title:Get TeamForge 5.3 Download the packages you need to install and set up CollabNet TeamForge.

1. Get the TeamForge install package from open.collab.net. Copy it to a temporary location, such as /tmp, on the server where TeamForge will run. 2. If you are installing TeamForge on a server without an Internet connection, get CTF-Disconnected-media-5.3.0.0-308.el5.i386.rpm and save it in /tmp. This is the support package with the software and utilities you would otherwise be downloading during the install process. 3. Deploy the installation package.

rpm -ivh TeamForge-installer-5.3.0.0-308.noarch.rpm

Tip: To specify the directory where you want the installation package deployed, add the --prefix flag to the rpm command.

rpm -ivh TeamForge-installer-5.3.0.0-308.noarch.rpm --prefix /some/other/path

4. If you are installing TeamForge on a server without an Internet connection, deploy the package with the support software.

rpm -ivh CTF-Disconnected-media-5.3.0.0-308.el5.i386.rpm

The installer is now ready to go. If you used the default path, they are located at /opt/collabnet/teamforge-installer/5.3.0.0.

Specify your CollabNet TeamForge site©s host and domain names Navigation title:Specify host and domain names Identify the host where CollabNet TeamForge site will run and the URL where users will find it. CollabNet TeamForge is controlled by settings in the master configuration file, site-options.conf. This page describes some of the most useful modifications you can make. Note: If you don©t need email service or a custom URLthis is a demo or experimental site -- for example, if this is a demo or experimental site -- you can leave these variables at their default values.

1. Open the master site configuration file in a text editor. For example:

vi /opt/collabnet/teamforge-installer/5.3.0.0/conf/site-options.conf

2. Rename the HOST_localhost token, replacing localhost with the name of the machine on which your TeamForge site will run. Note: Make sure the HOST variable is not commented out.

For example, suppose your organization, SuperVillain Inc., has a machine called appbox.supervillain.org available for its site to run on.

HOST_appbox.supervillain.org=app database subversion cvs

You can specify any combination of the app option, the database option, and the source control options (svn, cvs, or perforce), in any order. The default value places all of the services on a single host machine. 12 | CollabNet TeamForge 5.3 | Set up a CollabNet TeamForge site

For example, the Hosts section of your site-options.conf file may end up looking like this:

HOST_appbox.supervillain.org=app database HOST_svn.supervillain.org=subversion cvs HOST_perforce.supervillain.org=perforce For instructions on distributing your site©s services across multiple hosts, see Set up source control on its own server on page 48 and Set up a PostgreSQL database on its own server on page 49. Note: The host name is case-sensitive, and must exactly match the hostname that appears when you run the hostname command.

3. If you have an outward-facing hostname that is different from the internal hostname (for example, if your site is running on a virtual box or in a cloud), edit the DOMAIN variable to point the site©s domain name to the server where the site is running. Note: If you are assigning a value to the DOMAIN variable, check that the variable is not commented out.

Use this format:

DOMAIN_=

For example, suppose SuperVillain Inc. wants the domain name worlddomination.supervillain.org for its development site, which will be hosted on a machine called appbox.

DOMAIN_appbox.supervillain.org=worlddomination.supervillain.org

Your CollabNet TeamForge site will be visible at the URL you selected.

Do some basic configuration on your CollabNet TeamForge site Navigation title:Configure your site Specify settings to enable your site to work at its best under your individual conditions. CollabNet TeamForge is controlled by settings in the master configuration file, site-options.conf. This page describes the minimal modifications you must make to set up a usable TeamForge site.

Set your basic TeamForge database options Navigation title:Set basic database options Set up your site©s database to manage the work products that your site members produce.

1. Open the master site configuration file in a text editor. For example:

vi /opt/collabnet/teamforge-installer/5.3.0.0/conf/site-options.conf

2. Under "Database tokens," configure the site to use the database application. · If you are using a PostgreSQL database, keep the value of the DATABASE_TYPE variable at the default value, postgresql. · If you are using an Oracle database: · Set the value of the DATABASE_TYPE variable to oracle. · Set the value of the DATABASE_PORT variable to 1521.

3. Set values for the other key database variables. (Replace the terms in angle brackets with any string you want.)

DATABASE_NAME= DATABASE_USERNAME= DATABASE_PASSWORD= CollabNet TeamForge 5.3 | Set up a CollabNet TeamForge site | 13

Note: The database password must not contain any special characters. Only alphanumerics will work.

4. Review the rest of the variables in the site-options.conf file to make sure their values are right for your installation, then save the file.

You have now configured TeamForge to work with your database, but you have not yet set up the database itself. We will get to that in Set up a PostgreSQL database on page 51 or Set up an Oracle database on page 22, later in this process.

Set up email delivery from your CollabNet TeamForge site Navigation title:Set up email To enable your site to send automatic notifications to users by email, set up a mail server.

1. Open the master site configuration file in a text editor. For example:

vi /opt/collabnet/teamforge-installer/5.3.0.0/conf/site-options.conf

2. Specify how you want site-related emails handled by giving values for these variables: · SYSTEM_EMAIL: A valid email address for the system administrator responsible for this site. · ADMIN_EMAIL: A valid email address for the site administrator. · JAMES_POSTMASTER_EMAIL: A valid email address for the person or machine that handles email for the domain, such as [email protected]. Tip: The email accounts specified in the SYSTEM_EMAIL, ADMIN_EMAIL, and JAMES_POSTMASTER_EMAIL variables must be hosted on a separate server from the TeamForge site server. They do not necessarily have to be different from each other.

· JAMES_GATEWAY_HOST: A mail server with Internet access. This assures delivery of site email to users if your TeamForge server cannot connect to a DNS server or cannot get outside connections over port 25. Note: Specify the gateway host by its fully qualified domain name, not a host name.

3. Review the rest of the variables in the site-options.conf file to make sure their values are right for your installation, then save the file.

Install the CollabNet TeamForge application The installer sets up the site according to your configuration settings. Tip: For a direct view of everything the installer is doing, tail the yum log in another terminal before executing these steps.

tail -f /var/log/yum.log

1. If any mail service is running on port 25, stop it and make sure it won©t restart. For example:

/sbin/service sendmail stop /sbin/chkconfig sendmail off

If the DEDICATED_INSTALL variable is set to true, the installer will take care of your package versions automatically, and you can skip this whole step. b) If the DEDICATED_INSTALL variable is not set to true (or is not there), then run the automatic environment checking utility and fix any issues it reports.

cd /opt/collabnet/teamforge-installer/5.3.0.0 ./environment_check.sh

The environment checking utility compares your system environment with the list of packages required by the CollabNet TeamForge installer, and reports on which required packages are installed, missing, or out of version tolerance. Any package that is not the right version triggers a WARNING message. In this case, you have three choices: 1. Remove the package and its dependencies. 2. Have the versions fixed automatically by running the prepare-environment tool.

./prepare-environment.sh

The TeamForge installer automatically installs the versions that TeamForge needs. 3. If you can©t have packages changed automatically (for example, if some other application depends on the same Subversion or PostgreSQL installation on your application server, or the prepare-environment tool finds a package conflict it cannot resolve automatically), you can do the upgrade yourself.

c) Run environment_check.sh again until no WARNING messages appear. Important: Do not move on to the next step until all WARNING messages are resolved.

3. If you are using SElinux, make sure your SElinux settings are in order. See Set up SELinux on page 54 for the recommended settings. 4. Run the installer.

cd /opt/collabnet/teamforge-installer/5.3.0.0 ./install.sh -a -b -V

5. Start the application services.

/etc/init.d/collabnet start all

Note: You can use the start command in two ways: · /etc/init.d/collabnet start starts the application server and integration servers. This is the default startup command. · /etc/init.d/collabnet start all also starts the database and the Apache server.

6. Install a project template. TeamForge comes with a sample project template that showcases some of the platform©s most interesting features. Site administrators and project managers can use this template to jump-start projects without a lot of manual setup steps. Note: This procedure is recommended, but not required.

cd /opt/collabnet/teamforge-installer/5.3.0.0 ./install-project-templates.py -V

Use a site administrator user name and password. For a new site, these are admin and admin. Tip: On some servers, it may take a few seconds for the SOAP server to be ready after installation. If install-project-templates.py returns an error, try waiting briefly and then running it again. CollabNet TeamForge 5.3 | Set up a CollabNet TeamForge site | 15

Your new TeamForge site is now up and running.

· By default, the URL to log into is the hostname of the server on which your site is installed. If you provided a value for the DOMAIN variable in the site-options.conf file, then go to that domain. · It©s a good idea to stop TeamForge and reboot the machine to make sure all services come up at startup. Note: On CentOS, Apache may not automatically start up after a reboot. To ensure that it does, run this command now:

/sbin/chkconfig --level 2345 httpd on

· On the site toolbar, click Admin > Users > TeamForge Administrator . Click Edit and make sure the email address is right. This is the address that appears in the From field of messages automatically sent to users from your site.

Important: Do not delete the teamforge-install directory.You will need it for future maintenance or upgrades.

Supply your TeamForge license key Your license key enables you to use CollabNet TeamForge for the period of your contract. Your license key will only work for the IP address of the machine that your CollabNet TeamForge is running on, as specified in your order form.

1. Locate the confirmation email you received from your CollabNet representative when you purchased your contract. 2. Log into your site as the site administrator. Note: The site administrator is different from the root user on the machine where the site is running.

3. Click Admin > License Key . If you have entered a license before, the IP address and current licensed number of users on your site are listed on the License Key page. Verify that the IP address is the same as the one you entered in your order form. 4. Click Enter License Key. 5. Copy your new license key from the confirmation email and paste it into the Enter License Key field. A license key string looks like this: 25:supervillaininc:144.16.116.25.:302D02150080D7853DB3E5C6F67EABC65BD3AC17D4D35CB3Z00214141D70455B18583BF0A5000CA56B34817ADF8DBFI32353A6E657492617369633A38372E3139342E3136102E31322E Tip: save this license key in case you need to reinstall CollabNet TeamForge.

6. Click Save. 7. Verify that the new value for Licensed Number of Users matches the total number of licensed users in your contract.

Install an advanced CollabNet TeamForge site Advanced configuration provides the most flexibility and performance for your CollabNet TeamForge site.You can spread the load across multiple servers, use different source control tools, and otherwise customize your site. You can configure each CollabNet TeamForge service to fit your site©s particular needs. Each TeamForge service can run on its own server or share a server with one or more other services.

Set up hardware for an advanced CollabNet TeamForge installation Navigation title:Set up hardware 16 | CollabNet TeamForge 5.3 | Set up a CollabNet TeamForge site

Set up and install the hardware that your site will run on.

· For information about the operating systems you can use with CollabNet TeamForge, see Platform information for TeamForge 5.3 on page 111.

You must have root-level access to the machine where you are installing CollabNet TeamForge If you anticipate heavy use of your site, you may want to consider installing the database or the source control service on a separate server. See Set up the database for your CollabNet TeamForge site on a separate server on page 48 or Set up source control on its own server on page 48.

1. Install the operating system according to the instructions from the OS provider. Note: Do not customize your installation. Select only the default packages list.

rpm -qa | grep dovecot | xargs rpm -e rpm -qa | grep postgresql-libs | xargs rpm -e

2. Make sure port 80 is open. Tip: For detailed firewall requirements, see Which ports should I keep open? on page 73

3. Verify that the machine name is resolvable on the network. a) Use the hostname command to verify the name of the machine.

hostname bigbox.supervillain.org

b) Use the nslookup command to verify that your hostname maps to the right IP address.

nslookup bigbox.supervillain.org Server: 204.16.107.137 Address: 204.16.107.137#53

Tip: If there is any doubt about what the system©s real IP address is, use the /sbin/ifconfig command.

4. If you are installing TeamForge on CentOS without an Internet connection, move the Web-connected install repositories out of the way.

mv CentOS-Base.repo CentOS-Base.repo.backup mv CentOS-Media.repo CentOS-Media.repo.backup

This will prevent CentOS from going to the Web for files, which could cause an error.

Your server is ready.You can now set up the software environment in which you will install CollabNet TeamForge.

Get CollabNet TeamForge 5.3 Download the packages you need to install and set up CollabNet TeamForge. Tip: If your TeamForge site is expected to attract heavy user traffic, you may want to consider spreading the load by moving some services to separate servers after you have finished the basic installation. See Grow your CollabNet TeamForge installation on page 47 for how to handle source control and site data on separate machines. CollabNet TeamForge 5.3 | Set up a CollabNet TeamForge site | 17

rpm -ivh TeamForge-installer-5.3.0.0-308.noarch.rpm

Tip: To specify the directory where you want the installation package deployed, add the --prefix flag to the rpm command.

rpm -ivh TeamForge-installer-5.3.0.0-308.noarch.rpm --prefix /some/other/path

4. If you are installing TeamForge on a server without an Internet connection, deploy the package with the support software.

rpm -ivh CTF-Disconnected-media-5.3.0.0-308.el5.i386.rpm

The installer is now ready to go. If you used the default location, it is on your server at /opt/collabnet/teamforge-installer/, and you are ready to configure your site.

Configure your CollabNet TeamForge site Navigation title:Configure your site Specify settings to enable your site to work at its best under your individual conditions. CollabNet TeamForge is controlled by settings in the master configuration file, site-options.conf. This page describes some of the most useful modifications you can make. In pursuit of even greater efficiency and performance under your site©s particular circumstances, you may want to experiment with other variables not described here.

Before you do any configuration on your site, set up the master site configuration file by copying the sample configuration file from the installation package.

cd /opt/collabnet/teamforge-installer/5.3.0.0/conf cp site-options-advanced.conf site-options.conf

1. Open the master site configuration file in a text editor. For example:

vi /opt/collabnet/teamforge-installer/5.3.0.0/conf/site-options.conf

2. Rename the HOST_localhost token, replacing localhost with the name of the machine on which your TeamForge site will run. Note: Make sure the HOST variable is not commented out. 18 | CollabNet TeamForge 5.3 | Set up a CollabNet TeamForge site

For example, suppose your organization, SuperVillain Inc., has a machine called appbox.supervillain.org available for its site to run on.

HOST_appbox.supervillain.org=app database subversion cvs

You can specify any combination of the app option, the database option, and the source control options (svn, cvs, or perforce), in any order. The default value places all of the services on a single host machine. For example, the Hosts section of your site-options.conf file may end up looking like this:

Use this format:

DOMAIN_=

For example, suppose SuperVillain Inc. wants the domain name worlddomination.supervillain.org for its development site, which will be hosted on a machine called appbox.

DOMAIN_appbox.supervillain.org=worlddomination.supervillain.org

Your CollabNet TeamForge site will be visible at the URL you selected.

Set your basic TeamForge database options Navigation title:Set basic database options Set up your site©s database to manage the work products that your site members produce.

1. Open the master site configuration file in a text editor. For example:

vi /opt/collabnet/teamforge-installer/5.3.0.0/conf/site-options.conf

3. Set values for the other key database variables. (Replace the terms in angle brackets with any string you want.)

DATABASE_NAME= DATABASE_USERNAME= DATABASE_PASSWORD= CollabNet TeamForge 5.3 | Set up a CollabNet TeamForge site | 19

Note: The database password must not contain any special characters. Only alphanumerics will work.

4. Review the rest of the variables in the site-options.conf file to make sure their values are right for your installation, then save the file.

Set up email delivery from your CollabNet TeamForge site Navigation title:Set up email To enable your site to send automatic notifications to users by email, set up a mail server.

1. Open the master site configuration file in a text editor. For example:

vi /opt/collabnet/teamforge-installer/5.3.0.0/conf/site-options.conf

3. Review the rest of the variables in the site-options.conf file to make sure their values are right for your installation, then save the file.

Install the CollabNet TeamForge application Run the installer, then update some components and start your site. Tip: For a direct view of everything the installer is doing, tail the yum log in another terminal before executing these steps.

tail -f /var/log/yum.log

1. If any mail service is running on port 25, stop it and make sure it won©t restart. For example:

/sbin/service sendmail stop /sbin/chkconfig sendmail off

cd /opt/collabnet/teamforge-installer/5.3.0.0 ./environment_check.sh

./prepare-environment.sh

c) Run environment_check.sh again until no WARNING messages appear. Important: Do not move on to the next step until all WARNING messages are resolved.

3. If you are using SElinux, make sure your SElinux settings are in order. See Set up SELinux on page 54 for the recommended settings. 4. Run the installer.

cd /opt/collabnet/teamforge-installer/5.3.0.0 ./install.sh -a -V

Important: Do not delete the teamforge-install directory.You will need it for future maintenance or upgrades.

Set up the database for your CollabNet TeamForge site Install the database and configure TeamForge to work with it. The site database contains the work products (other than source code) that users will create on your site.

Set up a PostgreSQL database When you install TeamForge, the PostgreSQL database that handles your CollabNet TeamForge data is set up automatically by default. However, you can configure PostgreSQL further to work with your site©s specific conditions. Note: These are the minimal steps required for a site running on a single server. Settings may vary if your environment features multiple boxes or special networking characteristics. See Set up a PostgreSQL database on its own server on page 49.

1. Check that the basic configuration settings for PostgreSQL are correct in the master configuration file. See Set your basic TeamForge database options on page 12. 2. Log onto the server as the PostgreSQL user.

su-postgres CollabNet TeamForge 5.3 | Set up a CollabNet TeamForge site | 21

Note: Replace postgres with the value you selected for DATABASE_USERNAME in the site-options.conf file, if you changed it from the default.Your password is the value of the DATABASE_PASSWORD in the site-options.conf file.

3. In the /var/lib/pgsql/data/pg_hba.conf file, make sure the host entry points to your CollabNet TeamForge server. The table should look like this:

#TYPE DATABASE USER CIDR-ADDRESS METHOD # "local" is for Unix domain socket connections only local all all trust # IPv4 local connections: host all all 127.0.0.1/32 trust # IPv6 local connections: host /32 md5 where: · is the value of the DATABASE_NAME variable in the site-options.conf file. · is the value of the DATABASE_USERNAME variable in the site-options.conf file. · is the IP address of the main TeamForge application server (that is, the server to which the app parameter is assigned in the site-options.conf file).

4. In the /var/lib/pgsql/data/postgresql.conf file, under CONNECTIONS AND AUTHENTICATION, make sure the listen_addresses variable points to your database server.

listen_addresses = ©127.0.0.1,©

where is the IP address of the the server to which the database parameter is assigned in the site-options.conf file. Note: If your database is running on the same machine as the main TeamForge application, point the variable to your application server.

5. Log out of PostgreSQL and restart it.

exit

/etc/init.d/postgresql start

6. Log back into the PostgreSQL server and create the PostgreSQL user.

su-postgres createuser -P -S --createdb --no-createrole

7. Create the database.

createdb -E UTF8 -O

where is the value you selected for DATABASE_NAME in the site-options.conf file. 8. Exit the PostgreSQL shell.

exit

Your database is now ready to manage the work products your users produce. Tip:

· Before proceeding, make sure you can manually connect to PostgreSQL using the settings you have specified for the application. It is easier to troubleshoot the connection now than in later steps. · For recommendations on optimizing your PostgreSQL database to fit the particular requirements of your CollabNet TeamForge site, see this wiki page. 22 | CollabNet TeamForge 5.3 | Set up a CollabNet TeamForge site

Set up an Oracle database To use an Oracle database for your CollabNet TeamForge data, set up the Oracle database and tell the installer how to handle it.

1. Make sure your database uses UTF8 or AL32UTF8 encoding. This is needed to support users in Asian languages. For information about discovering and changing the database encoding, see this Oracle knowledge base article. 2. Connect to your Oracle database.

SQL> connect @/ as sysdba

3. Create the database user and password you will use to connect from CollabNet TeamForge to Oracle. SQL> create user identified by default tablespace temporary tablespace ; User created. 4. Grant permissions to the user that you just created.

SQL> grant unlimited tablespace to ; SQL> grant create snapshot to ; SQL> grant create cluster to ; SQL> grant create database link to ; SQL> grant create procedure to ; SQL> grant create sequence to ; SQL> grant create synonym to ; SQL> grant create trigger to ; SQL> grant create type to ; SQL> grant create view to ; SQL> grant query rewrite to ; SQL> grant alter session to ; SQL> grant create table to ; SQL> grant create session to ; SQL> exit

Note: The CollabNet TeamForge installer creates the tables and default values for you.

Start your new CollabNet TeamForge site Launch CollabNet TeamForge along with all the associated services.

1. Set up the initial, or "bootstrap," data.

./bootstrap-data.sh

2. Update your Apache configuration, keeping the existing settings around in case you need to roll back any changes. a) Back up your existing Apache configuration file.

cd /etc/httpd/conf cd httpd.conf httpd.conf.backup

b) Review the new httpd.conf.cn_new file that was created by the install process. The httpd.conf.cn_new file is an Apache server configuration file that combines your existing Apache configuration with directives specific to CollabNet TeamForge. c) When you are satisfied that httpd.conf.cn_new meets all your networking requirements, rename it to httpd.conf. CollabNet TeamForge 5.3 | Set up a CollabNet TeamForge site | 23

mv httpd.conf.cn_new httpd.conf

3. If you are using SElinux, make sure your SElinux settings are in order. See Set up SELinux on page 54 for the recommended settings. 4. Start the application services.

/etc/init.d/httpd start /etc/init.d/postgresql start /etc/init.d/collabnet start

5. Install a project template. TeamForge comes with a sample project template that showcases some of the platform©s most interesting features. Site administrators and project managers can use this template to jump-start projects without a lot of manual setup steps. Note: This procedure is recommended, but not required.

cd /opt/collabnet/teamforge-installer/5.3.0.0 ./install-project-templates.py -V

6. Log into the site and verify that things are working. · By default, the URL to log into is the machine name of the server on which your site is installed. If you provided a value for the DOMAIN variable in the site-options.conf file, then go to that domain to log in. · The initial administrator username is admin and the password is admin.You are required to change the password the first time you log in. · It©s a good idea to stop CollabNet TeamForge and reboot the machine to make sure all services come up at startup.

Your CollabNet TeamForge site is now up and running. Important: Do not delete the teamforge-install directory that you created to contain the installer.You may need it for future maintenance or upgrades.

A license key string looks like this: 25:supervillaininc:144.16.116.25.:302D02150080D7853DB3E5C6F67EABC65BD3AC17D4D35CB3Z00214141D70455B18583BF0A5000CA56B34817ADF8DBFI32353A6E657492617369633A38372E3139342E3136102E31322E Tip: save this license key in case you need to reinstall CollabNet TeamForge.

6. Click Save. 7. Verify that the new value for Licensed Number of Users matches the total number of licensed users in your contract.

Install CollabNet TeamForge on a virtual machine Navigation title:Install TeamForge on VMware To get the functionality of CollabNet TeamForge with the ease of installation and maintenance that comes with VMware, run CollabNet TeamForge in a VMware player. Note: For the hardware and software required to run TeamForge on a virtual machine, see #unique_35.

Get CollabNet TeamForge 5.3 Download the CollabNet TeamForge installer from CollabNet and unzip it on on the machine that will host your TeamForge site. Note: The machine on which you are running the VMware player must have at least 2 GB RAM and a 2 GHz processor.

1. Download the installer from http://www.collab.net/products/ctf/tryit.html. 2. Unzip the TeamForge5.3.zip file. 3. Install the VMware player. · On Windows, double-click the VMware-player-3.0.0-203739.exe file. · On Linux, run this command:

rpm -ivh VMware-Player-2.5.1-126130.i386.rpm

Tip: For detailed information about installing VMware on Linux, see the VMware Player Manual.

4. Start the VMware player. · On Windows, click Start > Programs > VMware > VMware Player . · On Linux, run the vmplayer executable. Note: You don©t have to update the VMware player, but you can.

5. In the Commands section, click Open. 6. In the file window, browse to \TeamForge5.3\Image\TeamForge.vmx Note: Starting the VMware image may take a few minutes, depending on the speed of your system. CollabNet TeamForge 5.3 | Set up a CollabNet TeamForge site | 25

Configure CollabNet TeamForge After you have installed VMware Player, configure the CollabNet TeamForge VMware image. Only one user needs to configure CollabNet TeamForge.This instance acts as the application server.To access CollabNet TeamForge , the CollabNet TeamForge application server must be running in VMware Player. Then other users can access it via a Web browser without running VMware Player.

1. Start the VMware player. · On Windows, click Start > Programs > VMware > VMware Player . · On Linux, run the vmplayer executable. Note: You don©t have to update the VMware player, but you can.

2. In the Commands section, click Open. 3. In the file window, browse to \TeamForge5.3\Image\TeamForge.vmx Note: Starting the VMware image may take a few minutes, depending on the speed of your system.

4. Log in with the username root and the password changeme. 5. Enter and confirm a new Linux password. Tip: The system may warn that your password does not meet security standards. For example, it may be too short. This does not mean the password is rejected. If you confirm the same password, it will work.

6. When prompted to run the configuration tool, type y. 7. Read the product license agreement. Type q to close it. Tip: You can use the space bar to advance a screen at a time.

8. If you accept the license terms, type y. 9. In the CollabNet TeamForge configuration tool, choose Dynamic Networking (DHCP) or Static Networking (Static IP) · Dynamic networking is useful for a one-person trial installation. It is quick and easy, but email integration with TeamForge will not work correctly. Note: If your IP address changes, you may also have to reconfigure source control.

· Static networking is best if you are evaluating CollabNet TeamForge with a team, or if you already have a license and intend to use TeamForge to support your team. To configure static networking, you will need to get a static IP address and hostname from your network administrator, and specify your network settings when prompted. Tip: In this case, it©s also a good idea to run TeamForge in VMware Player on a dedicated machine.

The networking for TeamForge is restarted. 10. Specify your outgoing email (SMTP) server. · For a one-person evaluation, accept the default value. 26 | CollabNet TeamForge 5.3 | Set up a CollabNet TeamForge site

· If you have a CollabNet TeamForge license and intend to send email outside of your firewall, use the SMTP server settings provided by your network administrator. Note: Depending on your corporate email configuration, your system administrator may need to permit TeamForge to send mail to the corporate mail server.

11. Choose whether to run CollabNet TeamForge at startup. · Choose ªYesº to start CollabNet TeamForge automatically whenever you start the TeamForge VMware image. · Choose ªNoº to require a manual CollabNet TeamForge startup whenever you start the TeamForge VMware image.

12. At the prompt, click Enter to start your CollabNet TeamForge site. Note: Startup can take several minutes, depending on the speed of the host system. On some slower systems, you may get a false failure message from JBoss, like this: jboss (app) (localhost:8080) ...... failed to start in 600 seconds, giving up now. Please check the log: /opt/collabnet/teamforge/log/apps/service.log FAILED This can safely be ignored.

Tip: From now on, you can stop and restart TeamForge using these commands:

/etc/init.d/httpd stop /etc/init.d/postgresql stop /etc/init.d/collabnet stop

/etc/init.d/httpd start /etc/init.d/postgresql start /etc/init.d/collabnet start

13. Log into your new site with the user name admin and the password admin. The URL for your site is the IP address or domain name provided in the Linux console at the end of the installation process. Note: You will have to change your administrator password when you first log in.

Any user with access to the network where the host system is running can now get to your site via a Web browser.

Supply your TeamForge license key Your license key enables you to use the VMware edition of CollabNet TeamForge for the period of your contract. Your license key will only work for the IP address of the machine that your CollabNet TeamForge is running on, as specified in your order form.

3. Click Admin > License Key . If you have entered a license before, the IP address and current licensed number of users on your site are listed on the License Key page. Verify that the IP address is the same as the one you entered in your order form. 4. Click Enter License Key. 5. Copy your new license key from the confirmation email and paste it into the Enter License Key field. A license key string looks like this: 25:supervillaininc:144.16.116.25.:302D02150080D7853DB3E5C6F67EABC65BD3AC17D4D35CB3Z00214141D70455B18583BF0A5000CA56B34817ADF8DBFI32353A6E657492617369633A38372E3139342E3136102E31322E CollabNet TeamForge 5.3 | Set up a CollabNet TeamForge site | 27

Tip: save this license key in case you need to reinstall CollabNet TeamForge.

6. Click Save. 7. Verify that the new value for Licensed Number of Users matches the total number of licensed users in your contract.

Upgrade to CollabNet TeamForge 5.3 You can upgrade to CollabNet TeamForge from CollabNet TeamForge 5.2, with any patch installed. To upgrade from CollabNet SourceForge Enterprise 5.1 or 5.0, or from any version of SourceForge Enterprise Edition, first upgrade your site to CollabNet TeamForge 5.2 and start it up. Then follow the steps for upgrading to CollabNet TeamForge 5.3.

Before you get started, choose whether your upgraded site will run on the same machine that your 5.2 site has run on, or on a new machine. Options Description You can choose whether to upgrade on the same box or on a new box if: · You were running TeamForge 5.2 on 32-bit Linux and you plan to run TeamForge 5.3 on 32-bit Linux. · You were running TeamForge 5.2 on 64-bit Linux and you plan to run TeamForge 5.3 on 64-bit Linux.

You must upgrade to a new box if: · You were running 5.2 on 32-bit RHEL and you plan to run 5.3 on 64-bit RHEL. · You want to move your site to bigger or faster hardware to handle increased traffic. · You want to test TeamForge 5.3 on a stage site before installing it.

Upgrade to CollabNet TeamForge 5.3 on the same hardware Navigation title:Upgrade on the same box If you plan to run TeamForge 5.3 on the same architecture as TeamForge 5.2, you can upgrade to TeamForge 5.3 without switching servers.

Back up CollabNet TeamForge 5.2 data Save a copy of your TeamForge 5.2 site data to a location where you can quickly retrieve it to your TeamForge 5.3 site. Note: This backup method requires shutting down your site briefly. If you cannot tolerate a shutdown, you might consider another backup/restore method, such as the NetApp Snapshot utility.

1. Stop the TeamForge application server and the Apache server.

/etc/init.d/collabnet stop /etc/init.d/httpd stop

2. Back up your database. · If your site uses a PostgreSQL database, create a dump of the database contents. (The data will be loaded back in later, after PostgreSQL has been upgraded.)

su - postgres -c /usr/bin/pg_dumpall > /tmp/backup_dir/ctf52.dmp 28 | CollabNet TeamForge 5.3 | Set up a CollabNet TeamForge site

Note: If your database is running on a separate machine from your application server, run this command on the database machine.

· If your site uses an Oracle database, follow the normal backup procedure.

3. Copy the following data directories to a safe location: Directory Contents /opt/collabnet/teamforge/var User-created data, such as artifact attachments /svnroot Subversion source code repositories /sf-svnroot Subversion repository for branding data e/cvsroot CVS source code repositories (not present on all sites)

Note: If your current site was upgraded from version 5.1 or earlier, replace /opt/collabnet/teamforge with /usr/local/sourceforge now. TeamForge 5.1 and earlier versions kept their data under /usr/local/sourceforge and not /opt/collabnet/teamforge.

Remove CollabNet TeamForge 5.2 To upgrade to CollabNet TeamForge 5.3, you must uninstall your current version of TeamForge. The uninstall process removes the CollabNet TeamForge application, but leaves your site data and configuration in place.

1. Stop your CollabNet TeamForge site.

/etc/init.d/postgresql stop

2. In the TeamForge 5.2 installer directory, run the uninstall command.

cd /opt/collabnet/teamforge-installer/5.2.0.0 ./install.sh -n -u -V -d /opt/collabnet/teamforge

The CollabNet TeamForge installer removes the rpm packages that make up the TeamForge application.

Get CollabNet TeamForge 5.3 Navigation title:Get TeamForge Find and deploy the packages you need to install and set up CollabNet TeamForge.

1. Get the TeamForge install package from open.collab.net. Copy it to a temporary location, such as /tmp, on the server where TeamForge will run. 2. Get the TeamForge update package from collab.net and copy it to /tmp. If you don©t already have credentials to download the package from the collab.net site, contact your CollabNet representative. 3. If you are installing TeamForge on a server without an Internet connection, get CTF-Disconnected-media-5.3.0.0-308.el5.i386.rpm and save it in /tmp. This is the support package with the software and utilities you would otherwise be downloading during the install process. 4. Deploy the installation package.

rpm -Uvh TeamForge-installer-5.3.0.0-308.noarch.rpm

5. Copy the update package to the installer directory.

cp migratorator_5.3.0.0.308.zip /opt/collabnet/teamforge-installer/5.3.0.0/migration

6. Unzip the update package. CollabNet TeamForge 5.3 | Set up a CollabNet TeamForge site | 29

cd /opt/collabnet/teamforge-installer/5.3.0.0/migration unzip migratorator_5.3.0.0.308.zip

7. If you are installing TeamForge on a server without an Internet connection, deploy the package with the support software.

rpm -ivh CTF-Disconnected-media-5.3.0.0-308.el5.i386.rpm

8. Check if the 5.2 Collabnet repo file still exists in /etc/yum.repos.d. If it does, move it out of the way.

mv /etc/yum.repos.d/collabnet.repo /etc/yum.repos.d/collabnet.repo_5.2backup

The installer and updater are now ready to go. If you used the default path, they are located at /opt/collabnet/teamforge-installer/5.3.0.0.

Install the CollabNet TeamForge 5.3 application Install CollabNet TeamForge and bring over the data from your old site.

1. For some sites, it©s a good idea to stop here and reconcile any software on the box that won©t work with CollabNet TeamForge 5.3. a) To determine whether you need to do this, check your site©s master configuration file: /opt/collabnet/teamforge-installer/5.3.0.0/conf/site-options.conf. If the DEDICATED_INSTALL variable is set to true, the installer will take care of your package versions automatically, and you can skip this whole step. b) If the DEDICATED_INSTALL variable is not set to true (or is not there), then run the automatic environment checking utility and fix any issues it reports.

cd /opt/collabnet/teamforge-installer/5.3.0.0 ./environment_check.sh

./prepare-environment.sh

c) Run environment_check.sh again until no WARNING messages appear. Important: Do not move on to the next step until all WARNING messages are resolved.

2. If you did not use the prepare-environment tool, or if you ran it but did not tell it to upgrade PostgreSQL to version 8.3.8, then run the PostgreSQL upgrade command now.

/etc/init.d/postgresql start cd /opt/collabnet/teamforge-installer/5.3.0.0 sh hooks/upgradepostgresql.sh 30 | CollabNet TeamForge 5.3 | Set up a CollabNet TeamForge site

Note: This is a good time to revisit any custom PostgreSQL configuration you may have done in pg_hba.conf and postgresql.conf .Your site©s database has now been upgraded from PostgreSQL 8.2 to PostgreSQL 8.3, and some configuration options have changed. · For the specific configuration options, see Set your basic TeamForge database options on page 12. · For detailed information about database setup, see Set up the database for your CollabNet TeamForge site on page 20. · For background information about the new version of PostgreSQL, see the PostgreSQL 8.3 documentation.

3. Run the installer.

cd /opt/collabnet/teamforge-installer/5.3.0.0 ./install.sh -a -V

4. Convert your old site©s data.

/opt/collabnet/teamforge/runtime/scripts/migrate.py

The migrate.py script locates the existing site data and modifies it to work with the new CollabNet TeamForge version. This includes configuration data for LDAP and the James mail server. Any modifications that you have applied to these components on your old site are reproduced on your upgraded CollabNet TeamForge site. 5. Update your Apache configuration, keeping the existing settings around in case you need to roll back any changes. a) Back up your existing Apache configuration file.

cd /etc/httpd/conf cd httpd.conf httpd.conf.backup

mv httpd.conf.cn_new httpd.conf

6. Start the application services.

/etc/init.d/httpd start /etc/init.d/postgresql start /etc/init.d/collabnet start

Your CollabNet TeamForge site is now up and running.

Finish your upgrade Here©s how to make sure everything is running smoothly after upgrading to CollabNet TeamForge. Tip: It©s a good idea to stop TeamForge and reboot the machine to make sure all services come up at startup.

Note: On CentOS, Apache may not automatically start up after a reboot.To ensure that it does, run this command now:

/sbin/chkconfig --level 2345 httpd on CollabNet TeamForge 5.3 | Set up a CollabNet TeamForge site | 31

1. Install a project template. TeamForge comes with a sample project template that showcases some of the platform©s most interesting features. Site administrators and project managers can use this template to jump-start projects without a lot of manual setup steps. Note: This procedure is recommended, but not required.

cd /opt/collabnet/teamforge-installer/5.3.0.0 ./install-project-templates.py -V

2. Log into your site as the administrator. The value you assigned to the DOMAIN variable in the site-options.conf file is the URL to log into. 3. Ensure that your users can access their source code normally. a) Click Admin in the CollabNet TeamForge navigation bar. b) On the site administration navigation bar, click Integrations. c) For each source control service you are supporting, verify that the right paths are specified. · SOAP service host should be localhost or the host name of the server on which you just installed TeamForge. · Repository base URL should be the URL for the top level of your source code server (which may be the same as your application server). For example, http:///svn/repos · SCM Viewer URL should be the URL for the ViewVC application on your source control server. For example, http:///integration/viewvc/viewvc.cgi

d) Select all your source code integrations and click Synchronize Permissions. This updates the permissions on your code repositories so that users can access them from the new site.

4. Verify that your site administrator email is still correct. This is the address that appears in the From field of messages automatically sent to users from your site. a) On the site toolbar, click Admin > Users > TeamForge Administrator . b) If your site©s URL has changed, click Edit and provide a valid email address. 5. If your site has custom branding, inspect the CSS, Javascript and Velocity files that have been committed to the branding repository and verify that they still work as intended. Tip: Commonly customized files include such files as button_bar.vm, menu_bar.vm, and sf_functions.js.

For more detailed information about branding, see #unique_46.

Upgrade to CollabNet TeamForge 5.3 on new hardware Navigation title:Upgrade on a new box If you plan to run TeamForge 5.3 on 64-bit Linux, and your TeamForge 5.2 site runs on 32-bit Linux, you must move your site to a new server.

Set up hardware for CollabNet TeamForge 5.3 Navigation title:Set up hardware Set up and install the hardware that your CollabNet TeamForge site will run on.

· For information about the operating systems you can use with CollabNet TeamForge, see Platform information for TeamForge 5.3 on page 111.

You must have root-level access to the machine where you are installing CollabNet TeamForge 32 | CollabNet TeamForge 5.3 | Set up a CollabNet TeamForge site

If you anticipate heavy use of your site, you may want to consider installing the database or the source control service on a separate server. See Set up the database for your CollabNet TeamForge site on a separate server on page 48 or Set up source control on its own server on page 48.