Title: How do I move a Traction TeamPage Installation to a different computer?
For the smoothest possible transition when moving your TeamPage installation to a different host machine (even if the new host uses a different operating system), please follow these steps:
• Shut down your TeamPage service. This will remove the lock file in the journal directory, close all open files, and ensure that all data are committed to disk.
• Copy the entire Traction directory (e.g. C:\Program Files\Traction) to the target system. This will ensure that certain customizations and configuration (server bootstrap configuration file, plug-ins, logo images, Java keystores, etc.) are all present and accounted for on the new host machine.
• If your journal directory is not contained in your TeamPage installation directory, it must of course be copied separately. We strongly recommend that the journal folder be located on a volume local to the host machine.
• Run the Traction TeamPage installer on the target system (e.g. if you moved from Solaris to Windows, you will run the Windows installer). When asked for the target location, please be sure to specify the location of the Traction directory that you copied from the old system. (If you do not specify the same Traction location, the installation process would create a separate TeamPage installation.) This will set up the scripts needed to run the TeamPage service on the new system. If you are installing on Windows, this will let you install the Windows services.
• If the system previously specified a network bind address, you must either edit the bind address or set enablebind=false in the Traction.properties server bootstrap configuration file before starting the TeamPage service. If TeamPage is unable to bind to a bind address, it will shut down. (Traction.properties is located in the traction/server subdirectory of your TeamPage installation).
You can then try running TeamPage in the foreground by running TractionApplication. If it complains of a port conflict (e.g. port 80 is already in use, or can't bind to the bind address), you can either edit the Traction.properties file to change the port or bind address, or shut down the conflicting service.
Once you get TractionApplication running and are able to contact the server's web interface on the new machine, you can use the web interface to shut it down and then run the service or Unix daemon.