On the target server:

1. Install the Teaming 2.1 software on the target server, as described in Section II, Basic Installation, paying special attention to these important details:

   • Set up the same Linux user to run the Teaming software that has been used to run the Teaming software in the past.

   • Select the same encryption algorithm for the Teaming database.

     IMPORTANT:If the database encryption algorithms do not match between the source and target Teaming systems, you cannot log in to the new Teaming 2.1 site.

2. Start Teaming on the target server.

3. Verify that the new Teaming site is working as expected.

4. Stop Teaming on the target server.

On the source server:

1. Stop Teaming.

2. Back up your existing database:

   mysqldump -uusername -ppassword sitescape > sitescape.sql
   

   This creates a file named sitescape.sql in the directory where you executed the mysqldump command.

3. Make sure that you have a recent backup of your entire Teaming system.

On the source server:

1. Mount the target server to the source server so that data can be copied from one server to the other.

2. In a terminal window on the source server, become the Linux user that runs the Teaming software.

3. (Conditional) If you are migrating data from Teaming 1.0:

   1. Copy your existing Teaming file repository to the target server:

      From:	/home/icecoredata
      To:	/var/opt/novell/teaming

      IMPORTANT:Do not copy the liferay directory.

   2. Copy the database backup of your existing Teaming database (sitescape.sql file) that you created in Step 2 in Section 23.1.2, Preparing the Source Linux Server to a convenient temporary location on the target server.

   3. Copy your existing Teaming Lucene index to the target server:

      From:	/home/icecoredata/lucene
      To:	/var/opt/novell/teaming/lucene

      In Teaming 2.1, the lucene directory now contains kablink and liferay.com directories.

   4. Delete the empty kablink directory.

   5. Rename the liferay.com directory where your existing Teaming database resides to kablink, which is the Teaming 2.1 zone name.

   6. Copy your existing software extensions to the target server:

      From:	/home/icecoredata/extensions
      To:	/var/opt/novell/teaming/extensions

      In Teaming 2.1, the extensions directory now contains the kablink and liferay.com directories.

   7. Delete the empty kablink directory.

   8. Rename the liferay.com directory where your existing software extensions reside to kablink, which is the Teaming 2.1 zone name.

4. (Conditional) If you are migrating data from Teaming 2.0:

   1. Copy your existing Teaming file repository from /var/opt/novell/teaming on the source server to the same location on the target server.

   2. Copy the database backup of your existing Teaming database (sitescape.sql file) that you created in Step 2 in Section 23.1.2, Preparing the Source Linux Server to a convenient temporary location on the target server.

   3. Copy your existing Teaming database index from /var/opt/novell/teaming/lucene on the source server to the same location on the target server.

   4. Copy your existing software extensions from /var/opt/novell/teaming/extensions on the source server to the same location on the target server.

On the target server:

1. Remove the empty Teaming database that was created when you installed the Teaming 2.1 software:

   mysql>drop sitescape;
   

2. Change to the directory where you copied the sitescape.sql file in Step 3.b or Step 4.b in Section 23.1.3, Transferring Data from the Source Server to the Target Server.

3. Manually re-create the Teaming database with the data that you copied from the source server:

   mysql -uusername -ppassword sitescape < sitescape.sql
   

On the target server:

1. (Conditional) If your are updating from Teaming 1.0 to 2.1, unzip the update-1.0.0-2.0.n.zip file, change to the resulting update-1.0.0-2.0.n directory, then run the update script to update the Teaming database from Teaming 1.0 to 2.0:

   mysql -uusername -ppassword < update-mysql.sql
   

   For more complete database update instructions, refer to Section 20.4.1, Manual Teaming Database Update.

2. To update from Teaming 2.0 to 2.1, unzip the update-2.0.0-2.1.n.zip file, change to the resulting update-2.0.0-2.1.n directory, then run the update script to update the Teaming database from Teaming 2.0 to 2.1:

   mysql -uusername -ppassword < update-mysql.sql
   

   For more complete database update instructions, refer to Section 19.3.1, Manual Teaming Database Update.

On the target server:

1. Change to the following directory:

   /opt/novell/teaming/apache-tomcat-version/webapps/
                                                 ssf/WEB-INF/classes/config
   

2. View the following files to ensure that the current zone name is set to kablink.

   zone.cfg.xml
   zone-ext.cfg.xml
   

3. Use the following commands to update the Teaming database with the new default zone name:

   mysql -uusername -ppassword 
   mysql>use sitescape; 
   mysql>update SS_ZoneInfo set zoneName='kablink' 
                                             where zoneName='liferay.com'; 
   mysql>update SS_Forums set name='kablink' where name='liferay.com';
   

4. Find and rename any liferay.com subdirectories to kablink.

   You might or might not find liferay.com subdirectories in the following locations, so you should check them all:

   /var/opt/novell/teaming/filerepository
   /var/opt/novell/teaming/lucene
   /var/opt/novell/teaming/extensions
   /var/opt/novell/teaming/archivestore
   /var/opt/novell/teaming/cachefilestore
   

1. Start Teaming 2.1, as described in Section 4.1.5, Starting Teaming on Linux.

2. Reindex the Teaming site, as described in Rebuilding the Lucene Index in Site Maintenance in the Kablink Teaming 2.1 Administration Guide.

   Your Teaming site should now function just as it did on the original source server.