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:

• On the server settings > General page, take note of the Server Directory under Runtime Info. This is where the application is located. This includes the software, plug-ins and server level settings and icons.

• Also on the server settings > General page, under Current Journal, take note of the Path directory. This is where your "Journal" is located. This is your data and all the journal level settings. By default, the Journal path is within the Server directory path, but could be located anywhere depending on where you chose to store it when you created it.

• Shut down Traction TeamPage. You can do this from the server settings > General page, under Manage Server by clicking the "Shut Down TeamPage" button. You can also stop the service or daemon if that's how you're running TeamPage. Either approach 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 from the Server Directory value (e.g. C:\Program Files\Traction) to the same location on 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 and should also be placed in the same location on the target system as it was on the originating system. We strongly recommend that the journal folder be located on a volume local to the host machine.

From here, you are about to "upgrade" the software.

• Download the proper installer from the Traction TeamPage Server Installers Page

• 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.

Find the Traction.properties server / bootstrap configuration file. Traction.properties is located in the traction/server subdirectory of your TeamPage installation.

• If the system previously specified a network bind address via the bindaddress= property, you should modify that address. If the address or host name you are using is not a canonical name for the new host computer, you should also ensure that the enablebind= property is set to false: otherwise, if TeamPage is unable to bind to the specified address, it will not be able to start up.

• Assuming the host name of the new computer is different, you will also need change the value of the serverbase= property, which specifies the address TeamPage uses to identify itself, including when generating fully qualified URLs. If you are using SSL / TLS with TeamPage, and the new server address is different, you will also need to obtain and install a new certificate. See Customer5583.

After you have made those modifications as necessary, you can start TeamPage normally. You may find it useful to first run TeamPage in the foreground by running the TractionApplication program so that you can monitor the startup process, including any metadata index rebuild that may be necessary. Errors you see on the console should also be captured in the traction.out.txt service console output file in your installation's server directory, or TeamPage's log file. When the console or log indicates that the server is ready -- e.g., Server ready on https://teampage.example.com -- TeamPage is ready to use.

If you see error messages pertaining to a failure to start TeamPage's web server -- e.g., due to a port conflict, or an incorrect bind address -- you shut down TeamPage and either a) edit Traction.properties to make the appropriate changes -- e.g., change the port= property or the bindaddress= property -- or b) shut down the conflicting service. Then try starting TeamPage again.

If you ran TeamPage in the foreground, after you are able to open it in your browser, you can use the web interface (server settings > General > "Shut Down TeamPage") to shut it down and then run the service or Unix daemon.

If your TeamPage server is configured to read and send email messages, and/or to use an Apache Solr service for TeamPage's advanced search module, those should continue to work from the new computer as long as the required remote services are still reachable. If you intend to use a different Apache Solr service, or different IMAP, POP3 or SMTP services, you can make the necessary changes from TeamPage's setup UI after TeamPage is up and running normally.

If you are using TeamPage with an external directory service and you can't log in, or TeamPage can't retrieve the required security group or user account information, and you need to make configuration changes to address those issues, you can do so by temporarily running TeamPage with no journal. See Customer5580.



Related Articles
referenced by (2)
Doc191: OverviewDoc19: How do I Back Up and Restore Traction TeamPage?
Article: Customer267 (permalink)
Categories: :Doc:FAQ
Date: July 16, 2002; 4:36:39 PM Eastern Daylight Time

Author Name: Greg Lloyd
Author ID: grl