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:
• In Server Setup | General | Runtime Info, take note of the Server Directory value. This is where the application is located. This includes the software, plug-in and server level settings and icons.
• In Server Setup | General | Current Journal, take note of the Path directory value. 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,
• Shut down Traction TeamPage. You can do this from the Server Setup | General tab where you can click the Shut Down TeamPage button. You may alternately Stop the service if you're on Windows. 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.
• 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).
Now, you can start TeamPage. Some customers prefer to first run TeamPage in the foreground by running TractionApplication which allows you to watch it load and see it go through re-index / re-build processes if required, see any errors (which are captured in the Traction.Out file anyways), and see it finally get to a point where it says "Server ready."
If you see the startup text complain 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 (Server Setup | General - Shut Down TeamPage) to shut it down and then run the service or Unix daemon.
Integration with your directory, mail and Traction TeamPage Premium search server should all work fine after you've moved your TeamPage server unless moving TeamPage creates a situation where these resources are no longer visible.
For example, if your Premium SOLR Search software was installed on the same server as Traction TeamPage, then you may have configured a relative reference and you will need to install the Search software on the new server as well.