Novell® Teaming 2.1 offers many enhancements over Teaming 2.0 for both Teaming users and administrators:
Landing Page Editor Improvements: The friendly new Landing Page Editor presents containers (a list for a single-column layout or a table for a multi-column layout) into which you can drag and drop folders, folder entries, graphics, and so on. After creating the initial version of a landing page, you can easily modify its appearance.
Teaming Feed: The new Teaming Feed displays in a compact window and lists postings as they occur on the Teaming site. You can display four types of new postings: site wide, your teams, your tracked places, or micro-blogs.
YouTube Video Support: Teaming enables you to display YouTube* videos in any entry, folder, or workspace throughout the Teaming site.
Teaming Site Access from Mobile Devices: Users can access the Teaming site from their mobile devices. From a mobile device, users can perform basic searches to find people and places. They can use saved searches (although new saved searches cannot be defined on mobile devices). My Teams, My Favorites, What’s New, blogs, wikis, discussions, calendars, and tasks can all be viewed from a mobile device, and workflow states can be modified.
Undelete for Workspaces and Folders: Users can undelete workspaces, folders, and folder entries. The main sidebar and menu bars provide a Trash icon that displays all deleted items within the selected workspace or folder, so users can select what they want to undelete. Users see only items that they have rights to see and can undelete only items that they have rights to undelete. Deleted items count against data quotas until they are purged. Users can use an Advanced Search to find and review their deleted items when they need to eliminate content in order to stay within their data quotas.
Calendar Improvements: In a Calendar folder, you can display all events that pertain to the Calendar folder owner, regardless of the workspace on the Teaming site where the event is actually posted.
Task Improvements: In a Task folder, you can display all tasks that are assigned to the Task folder owner, regardless of the workspace on the Teaming site where the task is actually posted.
User/Entry Data Quota: The Teaming administrator can set a maximum size limit for each Teaming user’s accumulated attached files and versions in any single folder entry. Users receive a warning when they reach a “high-water mark” (a percentage of their data quota for the folder entry). When they finally reach the data quota for the folder entry, users cannot create additional file attachments or versions in that folder entry until they make space available by deleting file attachments and versions in that folder entry. Administrators can assign data quotas on an individual user basis, or use groups to easily assign the same data quota to multiple users.
Administrative Purge for Workspaces and Folders: Because deleted items count against users’ data quotas, the Teaming administrator can choose to purge deleted items anywhere on the Teaming site to make storage space available.
Workspace/Folder Export/Import: The Teaming administrator can export workspaces, folders, and folder entries, then import them into a different Teaming system. The export process includes all content associated with the exported workspace, folder, or folder entry, such as users, groups, team members, roles, custom forms, landing pages, workflows, custom JSPs, and simple URLs. The import process attempts to reconcile imported data with data already existing in the target Teaming site.
Software Extension Management: The Teaming administrator can deploy extensions to the Teaming software while logged in to the Teaming site, without manually editing the Teaming properties file (ssf-ext.properties). Existing Teaming software extensions can also be viewed and deleted from the new Manage Extensions page on the Teaming site.
System requirements are available in the Teaming 2.1 Installation Guide on the Novell Teaming 2.1 Documentation Web site.
Make sure that the Linux* server where you plan to install Novell Teaming meets the system requirements.
If a Web server is currently running on the Teaming server, stop it, and preferably disable it.
Create or select a non-root Linux user and group that you want to own the Teaming directories and files and to run the Teaming software.
In a terminal window, become root by entering su - and the root password.
In the directory where you downloaded and extracted the Teaming software, enter the following command to start the Teaming Installation program:
./installer-teaming.linux
Complete installation instructions are available in the Teaming 2.1 Installation Guide on the Novell Teaming 2.1 Documentation Web site.
Make sure that the Windows* server where you plan to install Novell Teaming meets the system requirements.
Log in to the Windows server as a user with Administrator rights.
If a Web server is currently running on the Teaming server, stop it, and preferably disable it.
In Windows Explorer, browse to the directory where you downloaded and extracted the Teaming software, then double-click the installer-teaming.exe file to start the Teaming Installation program.
Complete installation instructions are available in the Teaming 2.1 Installation Guide on the Novell Teaming 2.1 Documentation Web site.
Section 5.1, Character Restrictions in Usernames and Passwords
Section 5.2, Username Character Restrictions for LDAP Synchronization and Login
Section 5.3, Character Restrictions in the Software Installation Directory Name
Section 5.4, Character Restrictions in the File Repository Directory Name
Section 5.10, JDK Dependency for SSL Connections to WebDAV Servers
Section 5.11, Updated Visual C++ Redistributable Package on Windows
Section 5.12, Installation on a Double-Byte Linux Operating System
Do not use extended characters or double-byte characters in Novell Teaming usernames and passwords. This includes usernames and passwords that are synchronized from an LDAP directory into Teaming.
This limitation is caused by the open source Spring Security that Teaming uses for authentication, in combination with the various authentication methods (both basic authentication and form-based authentication) used by single sign-on products such as Novell Authentication Manager, by Web services, and by WebDAV. Only ASCII characters are properly interpreted in all combinations.
LDAP usernames that contain special characters ( / \ * ? " < > : | ) cannot be used as Novell Teaming usernames. If your LDAP directory includes usernames with these characters, they do synchronize to the Teaming site, but the associated users cannot log in.
These characters cannot be used in a Teaming username because a Teaming username becomes the user’s workspace title, and the workspace title becomes an element of the hierarchical path that leads to the workspace. These characters are not legal characters in Linux and Windows pathnames.
Do not use extended characters or double-byte characters in the installation directory name for Novell Teaming file. The default location for the Teaming software is:
Do not use extended characters or double-byte characters in directory names in the path to the Novell Teaming file repository. The default location for the file repository root directory is:
The Oracle Outside In viewers that are used to render various file types into HTML for viewing in the Teaming site and for indexing do not handle directory names that include extended characters and double-byte characters.
When you have the Novell Teaming Installation program create the Teaming database for you, the database is given the name of sitescape. This database name is currently hard-coded into the database creation scripts used by the Installation program. The name dates back to the name of the company that previously owned the Teaming software.
If you want the Teaming database to have a different name, you can edit the database creation script, then run the database creation script manually before you start the Teaming Installation program. If you do this, you must also update the JDBC* URL when you run the Teaming Installation program.
IMPORTANT:Changing the Teaming database name is not recommended.
Applets are not supported in the following environments:
Safari on Mac*
64-bit Firefox on a system with a Java* Runtime Environment (JRE*) earlier than 1.6.0_12
On a 64-bit operating system, updating to JRE 1.6.0.12 or later enables the applets to work.
For example, multi-file drag-and-drop from the desktop, file paste from the desktop, Edit in Place, and the graphical display in the workflow editor do not work where applets are not supported.
For Mac users, Teaming looks for OpenOffice.org* in the following directory on users’ Mac workstations:
/Applications/OpenOffice.org.app
If your organization’s standard location for OpenOffice.org is in a different location on users’ workstations, you can reconfigure Teaming to look for OpenOffice.org in your preferred location.
Change to the following directory:
Open the ssf.properties file in a text editor.
Locate the block of lines that start with:
edit.in.place.mac.editor
Copy that set of lines to the clipboard of your text editor.
Open the ssf-ext.properties file, which is located in the same directory as the ssf.properties file.
Paste the block of lines you copied at the end of the ssf-ext.properties file.
Edit the location of the OpenOffice.org software to reflect its location in your organization.
Save and close the ssf-ext.properties file.
Close the ssf.properties file without saving it.
Stop and restart Teaming to put the new software location into effect on your Teaming site.
NFS* file system mounts are supported for placing the Teaming file repository on a remote server from where Teaming is running. However, NFS file system mounts are not supported for placing the Lucene* index on a remote server from where the Lucene Index Server is running.
On Windows Server* 2008 R2, the firewall is enabled by default and ports 80 and 443 are blocked. Teaming needs to use these ports, so Teaming needs to be an allowed program on your Windows server.
To prepare your Windows Server 2008 machine for use with Teaming:
In the Control Panel, double-click .
Click .
Open the ports that Teaming needs to use through the firewall:
After defining the two ports, click in the Windows Firewall Settings dialog box to allow Teaming to communicate through the firewall on these ports.
If you want to use an SSL connection between your Novell Teaming site and a WebDAV server, and if the WebDAV server has a self-signed certificate rather than a certificate provided by a Certificate Authority, you must use the Sun* JDK*. The existing Teaming functionality for handling self-signed certificates is not compatible with the way the IBM* JDK handles self-signed certificates.
Novell Teaming uses Oracle Outside In 8.3.0 viewer technology for displaying documents and images on the Teaming site and for indexing documents. This viewer technology relies on Support Pack 1 of the Microsoft* Visual C++ 2005 Redistributable Package. If the Windows server where you install Teaming does not already have the latest version of the Visual C++ Redistributable Package installed, you must install it before your Teaming site can function properly. The required version of the Visual C++ Redistributable Package is available from:
For more information, see New Dependency for Outside In 8.2.0 and Newer Versions, Windows Products Only (Doc ID 468895.1) on the Oracle Support Web site. Oracle Support site login is required in order to access the support document.
On Linux, the Novell Teaming Installation program does not currently accept double-byte input in any input fields.
To work around this limitation:
Copy the sample-installer.xml file to create an installer.xml file.
Open the installer.xml file in a text editor.
For a Basic installation:
In the Network section, specify your settings for the following fields:
name= port= listenPort= securePort= secureListinPort= shutdownPort= ajpPort= keystoreFile=
In the Database section, specify your settings for the following fields for the type of database that you plan to use:
username= password=
In the InternalInboundSMTP section, specify your settings for the following fields in the subsection for either SMTP or secure SMTPS:
mail.smtp.host= mail.smtp.user= mail.smtp.password= mail.smtp.port=
In the Inbound section, specify your settings for the following fields in the subsection for POP3 or secure POP3S, or IMAP or secure IMAPS:
mail.pop3.host= mail.pop3.user= mail.pop3.password= mail.pop3.port= mail.imap.host= mail.imap.user= mail.imap.password= mail.imap.port=
For an Advanced installation, specify additional settings as needed.
Save the installer.xml file, then exit the text editor.
Run the Teaming Installation program.
The settings you specified in the installer.xml file display as defaults as you proceed through the installation.
To successfully use Novell Teaming 2.1 with Novell Access Manager, Access Manager 3.1 SP1 IR1 is required. This version is available on the Novell Downloads Web site.
When you update from Teaming 2.0 to 2.1, customized themes are not automatically retained. However, the previous version of your Teaming software is backed up in /opt/novell/teaming/teaming-backup during the update process, so that you can restore any files that you have customized.
Zones are a new feature of Novell Teaming 2.x. However, groundwork for zones was laid in Teaming 1.0. The original default zone name was set to liferay.com in Teaming 1.0, although it was not visible in the Teaming 1.0 interface. With the removal of Liferay for Teaming 1.0, the default zone name provided for new Teaming 2.1 installations is kablink.
If you have a Teaming 1.0 site or if you participated in the Teaming 2.0 beta releases, your existing site displays liferay.com as the default zone name when you install Teaming 2.1. You cannot change the original zone name for a Teaming site.
Novell Teaming 1.0 could be configured to allow users to log in using their e-mail addresses. After updating to Teaming 2.0, users must use their usernames, rather than their full e-mail addresses, to log into the Teaming site.
When you update a Novell Teaming site from version 1.0 to version 2.1, Teaming users might encounter some Teaming pages that do not display as expected. For example, they might have trouble displaying the Calendar folder. To resolve display problems, Teaming users should clear the browser cache.
If you have a Novell Teaming 1.0 site or if you participated in the Teaming 2.0 beta releases, and if you have 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, 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.
To enable the Recursive Apply feature:
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 Definition Settings” in “Managing Folders” in the Novell Teaming 2.1 Advanced User Guide.
On Linux, if you ran Novell Teaming 1.0 as root and you want to run Novell Teaming 2.1 as a non-root user (recommended), you must change the owner and group of the Teaming 1.0 file repository directory structure before you perform the update. You can create a new Linux user specifically to run Teaming (for example, a teamingadmin user and a teamingadmin group) or you can use an existing Linux user (for example, the Apache wwwrun user and www group).
Stop Teaming 1.0.
Change to the Teaming 1.0 data directory.
The default location is:
/icecore/teamingdata
As root, execute the following commands:
chown -R username * chgrp -R group_name *
As root, run the Teaming 2.1 Installation program to perform the update from Teaming 1.0 to Teaming 2.1.
On the User ID for Novell Teaming page, specify the username and group name that you used in Step 3.
The Teaming 2.1 Installation program updates the /etc/init.d/teaming script to start Teaming as the specified Teaming administrator user.
After the installation is complete, run the /etc/init.d/teaming script to start Teaming as the Teaming administrator user.
In Novell Teaming 1.0, the Teaming Installation program enabled you to create mirrored folders of type SharePoint. Internally, SharePoint* mirrored folder functionality was the same as WebDAV mirrored folders. SharePoint mirrored folders did not support Windows NT* LAN Manager (NTLM) authentication.
In Teaming 2.1, the Installation program no longer offers the SharePoint option for mirrored folders. Existing SharePoint mirrored folders continue to work as usual in Teaming 2.1.
If you create Novell Teaming users by importing users from an LDAP directory, and if all users in the LDAP directory do not appear in Teaming, you might be experiencing one of the following issues:
Your LDAP directory might not be using a consistent user attribute (exclusively uid or exclusively cn). Repeat the LDAP synchronization process and use the other user attribute. The remaining users should then appear in Teaming.
If you selected cn, if you configured multiple contexts to search for users, and if you have multiple users with the same username, only the first instance of the duplicate username is synchronized into Teaming.
By default, all Teaming users can create new Teaming accounts for other users by clicking on the Personal Workspaces page. If you want to reserve account creation for the Teaming administrator, follow the instructions in “Preventing Users from Creating User Accounts” in “Basic Installation” in the Teaming 2.1 Installation Guide on the Novell Teaming 2.1 Documentation Web site
When you copy a workspace, the custom form and workflow definitions in that workspace are not transferred to the copy of the workspace. You can work around this limitation by moving the definitions to a higher level in the workspace tree.
Navigate to the folder in the original workspace where the definitions are located.
On the Workspace toolbar, click .
Expand the Form and View Designers tree, then click the definition that you want to move.
In the Definition Properties box, click to display the workspace and folder tree for your Teaming site, then expand the tree as needed to display an appropriate destination for the definition.
To make the definition available in the copy of the original workspace, move the definition to a location in the tree that is above both the original workspace and the copy of the workspace.
To make the definition available globally on your Teaming site, move it to the root of the workspace and folder tree.
To move the definition, select the destination, then click .
Click twice to return to the main Teaming page.
Verify that the definition is now available in the copy of the workspace.
Repeat this procedure for each definition that needs to be available in the copied workspace.
When you export a workspace or folder that includes links to external workspaces, folders, or entries, the target data pointed to by the external links is not exported along with the workspace or folder. The reference to the external target is exported, but external data is not exported because the hierarchy at the import location would probably not accommodate data that is not part of the exported workspace or folder.
If you are using MySQL, you might see the following error when you upload files and then delete them:
class org.hibernate.exception.GenericJDBCException Cannot release connection
This is related to a MySQL defect. To resolve the problem, update MySQL to version 5.1.40.
Files that have been password-protected in the application where they were created cannot be viewed on the Novell Teaming site. This is working as designed.
You cannot use the Novell Teaming Move This Folder feature to move one Mirrored File folder inside of another Mirrored File folder.
If you edit a file in a mirrored folder and then check the version history, you see only the latest version of the file and only the latest version of the file is available for editing from the mirrored location. This is working as designed. Document versioning is not currently available in mirrored folders.
A mirrored file cannot include a plus sign (+) in the filename if the following are true in your environment:
The mirrored file is mirroring a file on another Teaming server
The Teaming mirrored folder is a WebDAV file type
Renaming a Teaming file through a WebDAV client renames the attachment file only. It does not rename the title of the Teaming folder entry that the file is associated with.
This behavior is due to the capability recently added to Teaming that allows you to specify any title of your choosing when creating a File entry, regardless of the filename of the associated file. Historically, the title for all File entries was the same as the filename of the associated file.
Current Novell Teaming license usage is viewed by clicking . The License Report currently counts three internal, local users (_emailPostingAgent, _jobProcessingAgent, and _synchronizationAgent) as LDAP users. These internal users do not count against your Teaming license usage. The report also includes LDAP users with local users.
If you use the Date attribute in a custom entry or view, users in different time zones might see a different date compared to what you see.
Novell Teaming stores the date as midnight on the selected date in the Teaming user’s time zone in GMT. So, for example, January 13, 2010 in the Mountain time zone is stored as GMT-7:00 (20100113T0700). No problem appears for people in the same time zone. However, for people in a different time zone, Mountain time zone midnight could be a different day for them in their time zone. This discrepancy will be resolved in an upcoming release.
In the GroupWise® client, you cannot drag a file that is attached to a GroupWise message and drop it successfully into the Novell Teaming drag-and-drop window that opens when you click on the Folder Entry toolbar. Save the attachment first, then drag and drop the saved file into the drag-and-drop window.
In order to access a Novell Teaming site from the GroupWise Windows client, the time setting on the GroupWise user’s workstation must match the time setting on the Teaming server within five minutes. If there is a discrepancy of more than five minutes, the GroupWise client’s attempt to contact the Teaming site times out. If possible, reset the time of the server or the workstation to the correct and matching time.
If the time difference is a necessary part of your system configuration, you can change the timeout setting for Web services such as GroupWise that authenticate to the Teaming site through WS-Security.
Make a backup copy of the following file:
teaming_directory/webapps/ssf/WEB-INF/server-config.wsdd
Open the server-config.wsdd file in a text editor.
Search for the following section:
<handler type="java:org.apache.ws.axis.security.WSDoAllReceiver"> <parameter name="passwordCallbackClass" value="org.kablink.teaming.remoting.ws.security.PWCallback"/> <parameter name="action" value="UsernameToken Timestamp"/> </handler>
Insert a timeToLive parameter with large timeout value (for example, 86400 for 24 hours).
<handler type="java:org.apache.ws.axis.security.WSDoAllReceiver"> <parameter name="passwordCallbackClass" value="org.kablink.teaming.remoting.ws.security.PWCallback"/> <parameter name="action" value="UsernameToken Timestamp"/> <parameter name="timeToLive" value="86400"/> </handler>
Repeat Step 3 and Step 4 for the second instance of the section in the server-config.wsdd file.
Save the server-config.wsdd file, then restart the server.
This configuration change affects all client applications that authenticate to the server using WS-Security, not just GroupWise.
If you send an e-mail message from the Novell Teaming site, and you have a typographical error or invalid recipient in the field, an error displays, along with a button. In Firefox, you return to the Send E-Mail page, but the message content is lost. In Internet Explorer, the message content is retained.
When you use Firefox to send e-mail from the Teaming site, select Teaming users as recipients whenever possible, or copy recipient e-mail addresses to avoid typographical errors in the field.
In order to use the Novell Teaming Edit in Place feature in your browser on Windows, you must install the following Windows WebDAV update:
Software Update for Web Folders (KB907306).
This Windows update enables OpenOffice.org and Microsoft Office to interact correctly with the Teaming Edit in Place feature.
Microsoft Windows Vista* has some issues with WebDAV access that affect all WebDAV interactions. In addition, a Vista-specific issue with applets can prevent the Novell Teaming Edit in Place feature from working properly. Be sure you are running the latest version of Vista. Be sure you have installed the Windows WebDAV update described in Section 8.16, Windows Update for WebDAV Functionality.
Windows Vista users who are using Internet Explorer might see a Java warning when they try to use Edit in Place. (Firefox users do not see this error.)
To configure Internet Explorer to support the Teaming Edit in Place feature:
In Internet Explorer, click .
Click , select , then click .
In the field, specify the URL of your Teaming server, then click .
Select or deselect as appropriate for your Teaming server.
Click , then click to save the security settings.
To configure Windows Vista to support the Teaming Edit in Place feature in Microsoft Office, you must add new keys to the Windows registry for each Microsoft Office application.
In Windows Explorer, navigate to Program Files/Microsoft Office/Office12.
Scroll down to each Microsoft Office .exe in turn:
excel.exe powerpnt.exe winword.exe ...
Right-click each executable, then click .
Click .
Select , then select from the drop-down list.
Reboot the computer.
You should now be able to use the Teaming Edit in Place feature with Microsoft Office files.
NOTE:Although these steps enable Edit in Place for Teaming, they do not fix Vista’s inability to attach via WebDAV in Teaming.
For additional information on applets, view the following Sun bulletins:
If you use the Novell Teaming Edit in Place feature to edit a Word document using Office 2007 on a Windows 7 workstation, Word requests a location to save the edited file rather than saving it back to the Teaming site. The file can be saved to the Teaming site using Office 2003 on a Windows 7 workstation. It can also be saved to the Teaming site using Office 2007 on a Windows XP workstation.
For more information, see WebDAV Problems on Windows 7
If you copy the WebDAV URL associated with a Novell Teaming folder and try to use it to map a Windows network drive to the location, Windows Vista and Windows 7 might not be able to map the drive. When you install the Windows WebDAV update described in Section 8.16, Windows Update for WebDAV Functionality, some Teaming WebDAV URLs work successfully on Windows Vista and Windows 7.
WebDAV URLs work reliably on Windows XP.
On Windows XP, when viewing a Teaming folder through Windows Explorer, an additional sub-folder with the same name as the parent folder might be displayed.
To resolve this problem:
Launch a Web browser.
Navigate to the Microsoft Download Center and install the Software Update for Web Folders (KB907306) http://www.microsoft.com/downloads/details.aspx?FamilyId=17C36612-632E-4C04-9382-987622ED1D64&displaylang=en
Follow the on-screen instructions to install the software update.
When you use the Access Attachments Using WebDAV feature, authentication to the WebDAV server might fail. To resolve the problem, you need to clear your browser cache and possibly remove other types of stored data.
In Internet Explorer 8:
Clear the cache:
Click .
In the section on the tab, click .
In the list of data types to delete, select only , then click .
Restart your browser, access the Teaming site, then attempt to access the attachment again.
If clearing the cache does not resolve the authentication problem, remove additional stored data such as your browsing history and cookies:
Click .
In the section on the tab, click .
Select additional types of data, then click .
Restart your browser, access the Teaming site, then attempt to access the attachment again.
The Access Attachments Using WebDAV feature is not available in Firefox. Firefox does not have a mechanism for opening a WebDAV URL.
OpenOffice.org creates a new document version each time you click , instead of creating one new version when you exit the edited document. This behavior can cause you to quickly meet your data quota.
To avoid creating unnecessary versions of the same document, do either of the following:
Do not click multiple times when editing a document. Instead, click only once, before closing the document in OpenOffice.org.
When editing documents in Teaming, use a document editor other than OpenOffice.org, such as Microsoft Word.
If you see an HTML Conversion Error when you try to view a file, your Teaming server might not be configured correctly. Check the following:
The Installation program prompts you for the TrueType* font path. Typical locations are:
/usr/X11R6/lib/X11/fonts/truetype /usr/share/fonts/truetype
If Teaming cannot find the TrueType fonts, it cannot display HTML files correctly. To resolve the problem, you can:
Rerun the Teaming Installation program, use the installation option, and supply the correct path.
Modify the setting for the DGFONTPATH environment variable in the following file:
/opt/novell/teaming/apache-tomcat-version/bin/catalina.sh
Change to the following directory:
/opt/novell/teaming/stellent-converter/linux/x86
Run the exporter program.
The errors about missing input and output files are to be expected.
Look for errors about missing libraries.
If there are library errors, install any libraries that are missing.
The five Video Tutorials displayed on each user’s main Novell Teaming home page are defined in the tutorial_support_js.jsp file. The standard Video Tutorials are available in English only.
By changing the URLs in this file, you can make different content available to your Teaming users.
On your Web server, organize the tutorial material that you want to present so that you know the URL of each of your customized tutorial videos.
On the Teaming server, change to the directory where the tutorial_support_js.jsp file is located.
The default location of this file varies by platform:
Make a backup copy of the tutorial_support_js.jsp file.
Open the tutorial_support_js.jsp file in a text editor.
Find the following line:
function startTutorial( tutorialName )
In the url = line, specify the base URL where you custom content is located.
In each of the url += lines, provide the part of the URL that uniquely identifies each of your custom video tutorials.
Save the tutorial_support_js.jsp file, then exit the text editor.
Make a backup copy of your customized tutorial_support_js.jsp file.
If you do not back up the file, your changes are overwritten when you update the Teaming software. When you do update the Teaming software, your customizations must be transferred to the updated tutorial_support_js.jsp file.
Restart Teaming to put the changes into effect.
By default, Novell Teaming SOAP payloads do not generate multi-reference values. You can change the server-config.wsdd files so that multi-reference values are generated.
Change to the directory where a server-config.wsdd file is located.
A Teaming installation includes two server-config.wsdd files. The default locations of this file varies by platform:
In the following line:
<parameter name="sendMultiRefs" value="false"/>
change false to true.
Save the server-config.wsdd file, then exit the text editor.
Create a backup copy of the modified server-config.wsdd file.
If you update the Teaming software, the server-config.wsdd file is overwritten by the Teaming Installation program. You must either restore the updated file after the update or repeat the modification.
Repeat the procedure for the second server-config.wsdd file in the Teaming software.
On the Configure Default Settings page of your workspace, the field does not accept extended characters. Use only alphabetic characters and numbers in simple URLs.
If Outlook* users send postings to the Novell Teaming site and if the messages have attachments with extended or double-byte characters in the filenames, the attachment does not arrive on the Teaming site unless the Exchange server is properly configured. To configure the Exchange server to pass the filenames correctly, follow the instructions in Foreign Characters Appear as Question Marks When Sent from OWA.
When a report.csv file for an activity report is opened in Microsoft Excel*, Chinese characters do not display correctly, even though the report.csv file has been created correctly by default, because Excel always reads the file using the ISO Latin character set.
One workaround is to use the OpenOffice.org Calc spreadsheet program instead of Excel. It displays Chinese characters correctly.
As a workaround in Excel:
Import the report.csv file into Excel by using .
Select the report.csv file, then click .
Select , select , then click .
Select as the delimiter, click , then click .
Excel should now display the Chinese characters correctly.
The HTML editor included with Novell Teaming is the open source TinyMCE JavaScript WYSIWYG Editor. Its interface has been translated into Simplified Chinese, but not into Traditional Chinese. Therefore, if you set your Teaming locale to Traditional Chinese, the TinyMCE editor still displays its interface in Simplified Chinese. However, TinyMCE still accepts and properly displays Traditional Chinese input in the text fields.
In Internet Explorer 6, if you upload a file whose filename includes international characters into a File folder, and if you edit that file and create a new version, the link to the original version of the file no longer works, because Internet Explorer 6 double-encoded the filename. To resolve this issue, update to Internet Explorer 7.
To ensure that your Novell Teaming site is adequately secure, keep your system updated with all patches and security fixes.
For a list of the bugs that have been fixed since Novell Teaming 2.0, see the Novell Teaming 2.1 Bug List. You can look up the bug numbers in Bugzilla for more information about each bug.
The following sources provide information about Novell Teaming 2.1:
Online product documentation: Novell Teaming 2.1 Documentation Web site
Product documentation included within Novell Teaming:
Video Tutorials: Click any of the five Video Tutorial icons on the Teaming Home page to view explanations and demonstrations of common Teaming tasks. (The Video Tutorials are available in English only.)
Help System: Click the icon (question mark) in the upper right corner of the Teaming Home page, then click a yellow Help spot for context-sensitive help.
Guides: Click the icon, then click .
In addition to the Novell Teaming product documentation, the following resources provide additional information about Teaming 2.1:
In this documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path.
A trademark symbol (®, ™, etc.) denotes a Novell trademark; an asterisk (*) denotes a third-party trademark
Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.
Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export, or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. Please refer to the Novell International Trade Services Web page for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals.
Copyright © 2010 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.
Novell, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed on the Novell Legal Patents Web page and one or more additional patents or pending patent applications in the U.S. and in other countries.
For Novell trademarks, see the Novell Trademark and Service Mark list.
All third-party trademarks are the property of their respective owners.