Together installation is designed to be easy and straightforward. All installers for all products provide a "wizard" to guide you through the process. This topic covers installation issues applicable to all supported OS platforms and virtual machines.
For current information about system requirements, supported operating systems, and recommended Java Virtual Machines (JVM), visit www.togethersoft.com/together/sysrequire.htm.
Detailed installation information and start-up steps for all supported platforms are provided at the TogetherSoft website at www.togethersoft.com/together/readme/.
If you are upgrading from Together 2.x you should first:
Make sure all users working on the same project upgrade at the same time.
Back up your existing config.properties file if you modified it. You may wish to refer to it when setting configuration options in Together.
Back up any "scripts" that you developed for your 2.x installation. For information on how this feature has changed, see User's Guide: Working with Modules.
If you think you or others in your organization might install version 2.x again, back up your license.tg file in the 2.x ./bin directory.
Un-install Together 2.x.
Note: Installing Version 3.x or higher over Version 2.x without uninstalling 2.x is not recommended.
If you are upgrading from Together 3.x :
If you want to preserve your 3.x installation, install Together version 4 to a different location (the installer suggests this by default).
If you want to replace your 3.x installation with Together 4, uninstall version 3.x, then install version 4 to the same location.
Always back up your existing license file (./bin/*.tg or *.license)
If you have modified your configuration, back up your ./config and your ./lib/i18n directories.
The Together installer first looks for a valid license file in the setup directory. If none is present, it checks the destination directory and preserves any existing license file found there. If no currently valid license file is present in either location, the product installs to the specified destination directory and generates a Together Whiteboard license file. If identically named license files are found in both setup and destination locations, the installer asks if you want to overwrite the old one (in destination) with the new one (from setup).
If you are overwriting an existing installation with a new build having a "higher" license (i.e. more features) than your present license, you should overwrite the existing license file.
If you are just installing a new build and not upgrading your license, preserve your existing license file.
License files have a .tg or .license extension.
Together's installer provides an option to preserve existing configuration properties and license files. If you are installing over a previous version 3.0 or higher, you can simplify installation by choosing the same destination directory as your existing installation.
The Together installer installs the full product and generates a license file that enables the feature set for a specific product. Installation performed from distribution media purchased from TogetherSoft or authorized Together distributors will generate the license file and enable the features for the product license you purchased.
If you are upgrading a Together Whiteboard installation with a higher license purchased on-line or through an authorized distributor or reseller, you will need to copy the upgraded license file to your ./bin directory overwriting any existing license file of the same name. If you are not updating your current installation with a new build, copying the license file is all you need to do to "turn on" the features enabled by your license.
You can optionally install Together on a server for shared use. The installation process in the same as for local installs, and the installed file set is identical. You must obtain a license for each user of a shared installation.
Unless the default configuration options are adequate for all users of a shared installation, an administrator will need to create a shared configuration for all users and customize those options that are applicable to all users. See User's Guide: Advanced Customization: Creating a shared multi-user configuration.
SCC version control support requires installation of Coroutine classes and dll libraries. The Together installation program for Windows automatically installs these files and updates the environment's classpath to include them.
Make sure you log on to your
Windows computer with Administrator rights before installing.
After Together installation, you can check to confirm that Coroutine classes have been installed. Look for them in the directory: $TOGETHER_HOME$/lib/coroutine/com/neva/. Also check to be sure your classpath includes this path.
If, when using SCC version control feature, you get an error message that Coroutine can't be initialized, it means that Coroutine classes were not found where expected. If for some reason Coroutine is not installed you can install it separately by running: $TOGETHER_HOME$/bin/win32/jcinst.exe. If Coroutine is installed and the error message persists, check that your classpath points to the Coroutine directory.