-
Where is everything?
TeamForge consists of five interrelated services that can run on separate
hardware or share one or more boxes in various configurations. If you aren't
the person who first installed your current TeamForge site (or maybe even if
you are), it's essential to catalog the hosts where your services are
running and to know what configuration has been applied to them.
-
Provide site-wide reporting?
TeamForge 6.1.x enables site
administrators to track user logins for their site. More reporting options
are coming.
If your users want this feature, you'll have to turn on a
service known as extract-transform-load (ETL), during the upgrade process.
You'll also have to configure a new database called the datamart. (These
elements are off by default.)
After your site is upgraded, you can
also choose to move these new services off to one or more separate servers,
the same as you can do with the existing TeamForge services.
-
"Dedicated" or "advanced?"
The type of TeamForge
installation you have makes a difference for how you upgrade and patch the
site. If your site is a dedicated site, you'll be able to skip some of the
steps outlined here. If you don't know whether your site was originally
installed as dedicated or advanced, here's how you can find out: Is my TeamForge site "dedicated" or "advanced?"
-
Branding changes?
Every release of TeamForge can
bring changes to the look and feel of the product. TeamForge
6.1.1 is no
exception. If you have edited files in your site's branding repository
(that's how you customize the look and feel of the product), you must
download the new branding package and check into your branding repository
the new versions of any files you have edited. See Customize anything on your site for instructions.
-
Special database settings?
The efficiency of your database can have an impact on your users' perception
of the site's usability. If your site uses a PostgreSQL database (which is
the default), you may want to consider tuning it to fit your specific
circumstances. The default settings are intended for a small-to-medium site
running on a single server. See What are the right PostgreSQL settings for my site? for
recommendations from CollabNet's performance team on optimizing PostgreSQL
for different conditions.
-
Upgraded JDK
TeamForge
6.1.1 uses JDK
1.6.0_26. If you are upgrading on the same box, and that box has a JDK at an
earlier version, the upgrade utility upgrades the JDK. However, you'll still
need to edit the JAVA_HOME variable in your
site-options.conf file to reflect the new JDK
version. See Upgrade a TeamForge site to 6.1.1 on the same hardware.
