Change log of site-options.conf tokens.
TeamForge
16.7
- Obsolete tokens
-
- TeamForge 16.7 installer automatically sets
JAVA_HOME during installation or upgrade. Therefore, the
JAVA_HOME site options token, if added to your
site-options.conf file, must be removed while upgrading to TeamForge 16.7 and later.
- The DEDICATED_INSTALL
token is no longer supported. CollabNet recommends removing this token from the
site-options.conf file. However, this token is ignored (has no effect
whatsoever) if you continue to have it in your site-options.conf file
post upgrade to TeamForge 16.7 and later.
- Debug settings can be done via the
JAVA_OPTS tokens (such as JBOSS_JAVA_OPTS and
ETL_JAVA_OPTS). Hence, the following tokens are no longer supported:
- JBOSS_DEBUG
- PHOENIX_DEBUG
- ETL_DEBUG
- INTEGRATION_DEBUG
- ETL_DEBUG_PORT
- JBOSS_DEBUG_PORT
- INTEGRATION_DEBUG_PORT
- PHOENIX_DEBUG_PORT
- The SITE_DIR and
DATA_DIR tokens are no longer supported. Starting from TeamForge 16.7 (and later) SITE_DIR and
DATA_DIR are unconditionally set to
/opt/collabnet/teamforge and
/opt/collabnet/teamforge/var respectively during runtime
creation.
- The
MODPAGESPEED_ENABLED token is no longer supported.
- SSL certificates are validated by
default. Hence, VALIDATE_SSL_CERTS token is no longer supported. If in
use, remove this token from the site-options.conf file post upgrade to
TeamForge 16.7 and
later.
- While the
SSL_CA_CERT_FILE token is still supported, it has been removed from the
site-options-default.conf file as it is only needed for add-ons.
References to this token have been removed from TeamForge documentation as well.
- Newly added tokens
-
TeamForge
8.2
- Obsolete tokens
-
- PERFORCE_CLIENT_DIR
- PERFORCE_GROUP
- PERFORCE_LICENSE_FILE
- PERFORCE_LOG_DIR
- PERFORCE_PORT
- PERFORCE_REPOSITORY_BASE
- PERFORCE_SERVICE_CMD
- PERFORCE_USER
- HELP_AVAILABILITY
- REMOTE_HELP_URL
- EXTERNAL_TOMCAT_INSTALL_DIR
- INTEGRATION_BUILTIN_TOMCAT
- ETL_BUILTIN_TOMCAT
- CEE_COMPATIBLE
- Newly added tokens
-
TeamForge
8.0
- Newly added tokens
-