Maintain your CollabNet TeamForge 6.1.1 site on Red Hat

Supply your TeamForge license key
Your license key enables you to use CollabNet TeamForge for the period of your contract.

Supply your CollabNet TeamForge license key as a text file
Your license key enables you to use CollabNet TeamForge for the period of your contract.

Support CollabNet TeamForge users
As a system administrator, you can do these things to help maximize the effectiveness and productivity of your site's users.

Protect your CollabNet TeamForge site
You can take various measures to maximize the security of your CollabNet TeamForge users.

Set up external applications for a TeamForge site
When you integrate an external application into your TeamForge site, the site administrator can make that application available to users as if it were a native TeamForge component.

Get information about a CollabNet TeamForge site
Use the snapshot.py utility to determine what processes are running on your CollabNet TeamForge site, how much free memory is available, and other information.

Rebuild runtime without the install directory
You should keep your teamforge-installer directory around after installing TeamForge in case you need it later. However, if you delete or lose the directory you can still rebuild the application runtime.

Turn on site-wide reporting
To use the site-wide reporting functionality, you have to configure a collection of variables in the site-options.conf file.

Synchronize TeamForge source control integrations
Any time you upgrade your TeamForge site or a source control application, you must ensure that your users can still access their source code.

Provide more than one source control server
To run more than one source control server of the same type on your site, each integration must have its own unique name and data directory.

Upgrade Subversion
Use the yum package manager to upgrade to the latest supported Subversion release.

Change your site's domain name
To change the domain name of your site, you must change the name in the file system, the database, and any integrated applications. TeamForge provides a script for each of these.

Specify DNS servers
Define the DNS servers with which you want CollabNet TeamForge to resolve URLs by listing them in the resolv.conf file.

Optimize PostgreSQL with vacuum
To optimize your PostgreSQL database, run a built-in utility called "vacuum."

Change the location of a log file
To change where log files are written to, edit the site-options.conf file and restart the runtime environment.

Change the logging level on your site
To support troubleshooting, you may need to set the logging level appropriately. Here's how to do that.

Raise the logging visibility of selected database requests
For easier troubleshooting, you can dictate that certain database requests get logged in a handy central log file.

Schedule data extraction for reporting
Set the interval at which you want yourTeamForge site's data extracted to the datamart from which reports are generated.

Move datamart to a separate instance
Datamart can be run in same instance or in a separate instance.

Back up and restore CollabNet TeamForge data
CollabNet TeamForge stores data in the database and on the file system. Back up all data comprehensively so that it can be restored in the event of unrecoverable failures.