The following components of the Novell Teaming operating environment were supported for Teaming 1.0 but are not supported for Teaming 2.1:
Red Hat* Enterprise Linux 3 and 4
Oracle 9g
Microsoft SQL Server 2000
If the operating environment for your Teaming system includes any of these components, you must update the components before your update to Teaming 2.1. For currently supported versions, see Section 2.0, Teaming System Requirements.
For assistance with updating your operating system, see Section 23.0, Migrating Existing Novell Teaming Data into a New Teaming 2.1 System.
Novell Teaming data is stored in the Teaming file repository and in the Teaming database. Make sure that you back up both kinds of Teaming data. In addition, you might want to back up your log files.
The default file location for the Novell Teaming 1.0 file repository varies by platform:
The default locations for Teaming 2.1 are different, as listed in Section 3.2.4, Teaming Installation Locations, but the Teaming 2.1 Installation program does not move the data as part of the update process. If you have performed an Advanced installation and have distributed different types of Teaming data to different locations, check the installer.xml file located in the same directory with the Teaming 1.0 Installation program to make sure that you have backed up all different types of Teaming data.
The default database locations have remained the same from Novell Teaming 1.0 to Novell Teaming 2.1, as listed in Section 3.5.3, Database Location. However, if your database administrator created the Teaming database in a different location, either on the Teaming server or on a remote server, you need to know where it is and make sure that it is backed up before you perform the Teaming update. Check the installer.xml file for the location, if necessary.
The update process eliminates all existing Teaming and Tomcat log files. If you want to retain these log files, copy them to a location outside of the Teaming software directory structure.
The Teaming 1.0 log file (ssf.log) is located here:
|
Linux: |
/opt/icecore/liferay-portal-tomcat-version-jdk5-version/ webapps/ssf/WEB-INF/logs |
|
Windows: |
c:\icecore\liferay-portal-tomcat-version-jdk5-version\ webapps\ssf\WEB-INF\logs |
The Tomcat log file (catalina.out on Linux and stdout_*.log on Windows) is located here:
After confirming that you have backed up your Novell Teaming data, the Teaming 2.1 Installation program performs either a Basic installation or an Advanced installation of Teaming 2.1. As defaults, it uses the configuration information stored in the Teaming 1.0 installer.xml file.
In preparation for the update, review Section 3.0, Planning a Basic Teaming Installation and fill out the Basic Teaming Installation Summary Sheet. If you performed an Advanced installation for Teaming 1.0, review Section 9.0, Planning an Advanced Teaming Installation and fill out the Advanced Teaming Installation Summary Sheet.
To update your Teaming site, follow the instructions in Section 4.0, Setting Up a Basic Teaming Site or Section 10.0, Performing an Advanced Teaming Installation.
In Novell Teaming 1.0, if you used the Add Files to Folder feature to drag and drop a directory full of files into a Teaming folder, the files were automatically given the Discussion entry type, even if the Teaming folder was not a Discussion folder. In addition, if the directory contained subdirectories of files, the subdirectories were created as Teaming Discussion folders.
If you want to change the entry type and folder type to match the top-level Teaming folder type in Teaming 2.1, you can enable the Recursive Apply feature on the Configure Default Settings page of the top-level Teaming folder by editing the Teaming ssf-ext.properties file.
On the Teaming server, change to the directory where the ssf-ext.properties file is located.
The default location of this file varies by platform:
Make a backup copy of the ssf-ext.properties file.
Open the ssf-ext.properties file in a text editor, then scroll to the bottom of the file.
Add the following line:
ssf.allowFolderDefinitionFixups=true
Save the ssf-ext.properties file, then exit the text editor.
Restart Teaming to put the change into effect.
To change the entry types and folder types for imported files, follow the instructions in Recursively Applying Folder Entry Types
in Managing Folders
in the Novell Teaming 2.1 Advanced User Guide.