December 3, 2008
Novell® Teaming is an enterprise collaboration tool that integrates with GroupWise®. Novell Teaming can increase individual productivity, team effectiveness, and organizational success by providing the right set of tools. Key teaming features include:
Team workspaces, calendars, task lists, and milestone tracking
Easy document management and document sharing
Discussion threads, wikis, blogs, and RSS feeds
Workflow automation with customized forms
System requirements and installation instructions are available in the Teaming 1.0 Installation and Configuration Guide on the Novell Teaming 1.0 Documentation Web site.
Novell Teaming is designed to be installed on a different server from the Conferencing component of the Teaming + Conferencing product. However, it is possible, though somewhat more difficult, to install both components on the same server. Production deployment typically uses two or more separate servers.
If you purchased a number of Novell Teaming licenses in such a way that you received multiple license key files, or if you purchased licenses to enable additional Teaming features, you must consolidate the license information.
Use any one of the license key files when you install Novell Teaming.
After Novell Teaming is installed and running, copy all your license key files to the following directory:
Log in to Novell Teaming as the Teaming Site Manager.
In the Teaming Administration portlet, click.
Your current license information is displayed.
Scroll to the bottom of the license information, then click.
The Teaming server reads all the license key files in the license subdirectory and displays your total license information.
Restart the server to put the new licenses into effect.
If you are updating an existing Teaming system to Support Pack 3, you must completely reindex the search index in order to resolve existing index problems that are now fixed.
After installing Support Pack 3:
In the Teaming Administration portlet, click.
Select the top workspace, then click.
Depending on the size of your Novell Teaming site, the reindexing process might be lengthy. If you have a large site, you might want to perform this process when the site is not busy. The reindexing process might prevent users from accessing workspaces and folders on the site.
On an upgrade, the installer now creates a backup directory called icecore-backup in the install directory that contains copies of many configuration files. Each time you upgrade, previous icecore-backup folders are renamed with the date and time appended:
The icecore-backup directory with no date appended is always the most recent backup. The reason for creating the icecore-backup directory is to preserve any manual changes you might make to configuration files (such as the server.xml and cluster config files). The upgrade process needs to overwrite these files, because some Teaming Service Packs ship with updated versions of the server.xml (or similar files) to enable bug fixes, etc. Because there is no reliable way to automatically merge the Teaming software changes with any manual changes you have made, you need to manually re-apply the changes after the upgrade is finished by copying your changes from the backup files in the icecore-backup directory into the new files that Teaming installs as part of the upgrade.
If all of the custom changes (such as changing port number, adding iChain® proxy address, etc.) were previously made through the installer (or installer.xml file) without subsequent manual tweaking of any other configuration files, then the upgrade should preserve all the settings if you answer the installer questions and provide exactly the same configuration settings as before.
To review the known issues for Support Pack 1 or Support Pack 2, see the Teaming 1.0 Support Pack 1 or Support Pack 2 Readme.
When using Firefox as a browser, if you copy from GroupWise and paste into Teaming, Firefox crashes. This is a Firefox problem, and occurs only when using later versions of Firefox 2 (2.0.5 and later). This problem does not exist when using Firefox 3.
Microsoft* Windows Vista* has numerous problems with WebDAV access that affect all WebDAV interactions. There is also a Vista-specific issue with applets that can prevent the Edit-in-Place feature from working properly. Be sure you are running the latest version of Vista.
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 Edit-in-Place:
Click thetab, select , then click .
In thefield, specify the URL of your Teaming server, then click .
Select or deselectas appropriate for your Teaming server.
Click, then click to save the security settings.
To get Edit-in-Place to work in Novell Teaming with Office 2003, Office 2007, and Vista, complete Step 1 through Step 3 in any order:
If you are using Internet Explorer, set your Internet security options as described above.
Firefox users do not need to change their Internet security settings.
Install the latest Microsoft Web Folder update.
This is available from the Microsoft Knowledgebase article 907306.
Add new keys to the registry for each MS Office application:
In Windows Explorer, navigate to Program Files/Microsoft Office/Office12.
Scroll down to each MS Office .exe in turn:
excel.exe powerpnt.exe winword.exe ...
Right-click each executable, then click.
Select, then select from the drop-down list.
Reboot the computer.
You should now be able to use Edit-in-Place for MS Office files.
NOTE:Although these steps enable Edit-in-Place for Novell Teaming, they do not fix Vista’s inability to attach via WebDAV in Novell Teaming.
For additional information on applets, view the following Sun* bulletins:
At release time, the current version of SUSE® Linux Enterprise Desktop (SLED) ships with an older 1.4.x version of the Java Runtime Environment. That version has a bug that prevents drag-and-drop from operating properly with the Novell Teaming file upload applet. However, copy-and-paste still works. Updating the JRE* to 1.5.x on the SLED client system removes this restriction.
The Liferay* portal allows authentication by IDs other than screen name (for example, e-mail address). Enabling this feature requires a number of prerequisites and has some side effects that might not be desirable:
All e-mail addresses must be unique.
The Liferay LDAP search filter must be changed from cn=@screen_name@ to mail=@email_address@
Unique screen names must still be defined for each user.
WebDAV and Web Services only support authentication by username (screen name), not by e-mail address.
Alternatively, you can use the e-mail address as the screen name (so that the screen name and the e-mail address fields are identical). However, this is a decision that cannot be changed; it must be part of the initial population of the database from LDAP.
If you modify a task in place, the summary page underneath does not update to reflect the change. You must refresh the page. A similar behavior can be seen in calendars.
A directory tree named jackrabbit is created in the FileRepository root directory. This is the result of initialization of software components that are not yet supported in the current release.
If you try to download the Novell Teaming system error log by using the Teaming Administration portletmenu with Internet Explorer, you must have set to or less for the download to work. Firefox works in all cases.
If your Teaming session times out while you are viewing a folder with a table view, the Liferay pop-up box is obscured. This will be fixed in a future update.
Five warnings appear in the Liferay startup log file (catalina.out). They are benign and can safely be ignored:
service.impl.PortletLocalServiceImpl - "Portal with name EXT_1..."
org.hibernate.imple.SessionFactoryObjectFactory - "Initial context...
No appenders for log4j
net.sf.ehcache.config.Configurator - "No configuration found..."
When you shut down the product, the log file contains a message about a NullPointerException. This error is benign.
If you change your password through the portal or by other means, you might need to log out and log in again in order for WebDAV access to work properly.
When a report.csv file for an activity report is opened in 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.
As a workaround:
Import the report.csv file into Excel using .
Select the report.csv file, then click .
Select, select , then click .
Selectas the delimiter, click , then click .
Excel should now display the Chinese characters correctly.
To review the bug fixes in Support Pack 1 or Support Pack 2, see the Teaming 1.0 Support Pack 1 or Support Pack 2 Readme.
Database flushes during index operation have been minimized.
ACL changes in the search index are much faster.
Brackets are used in a folder tree if there are more than 25 subfolders in a folder or workspace.
Display problems when showing a deleted user account no longer occur.
The team member list is properly sorted.
When a folder name includes the “&” symbol, tree buckets work correctly.
Users can now right-click and save attached JPG, TXT and PDF files.
The name of the Conferencing product has changed from “Zon” to “Conferencing.”
Users can specify that date elements in entry definitions should not be initialized to today’s date.
If you delete an attached file from a file entry, the title is left unchanged.
The “bleed through” problem of select box elements has been fixed on IE6.
iFRAMEs works better in IE6 (eliminated an error message if the site is running through https).
An improved error message displays if a document cannot be shown in HTML.
Filenames display correctly when the file name has UTF-8 characters.
Text elements are allowed to be columns in the discussion table view.
Searching within a folder and all of its subfolders includes the starting folder.
IMPORTANT:To take advantage of these fixes, make sure you follow the instructions in Section 3.3, Reindexing the Search Index after you install Support Pack 3.
Logout/login is no longer required for a language change.
A configuration option for using different hostnames for all generated WebDAV URLs has been added. This allows iChain to work better with WebDAV.
When a user changes language or time zone settings from the Liferay My Account form, propagate immediately those changes to Teaming. This eliminates the need for the user to log out and log in to see the changes.
When creating new user accounts via LDAP Synchronization, you can use the system’s locale as the default locale for the new accounts.
Hungarian is now a supported language.
Fhe tree widget now works in Italian.
The new Installer process has been added to the Installation Guide.
Post-installation configuration information has been moved to the Administration Guide.
Attached files are handled better when you mail entries into a folder.
Mail notifications are no longer sent if there is nothing new.
Empty alternate content is not sent in e-mail notification messages.
You can now get all principals and add a name to principals.
A workflow can be started on an entry (including specifying the desired starting state).
A comment can be added to an entry.
There are now Web services for setDefinitions, setTeamMembers, and getDefinitionListAsXML.
There is now a Web service to perform a synchronize operation on a mirrored folder.
There are Web Service calls to support the migration from SiteScape Forum to Teaming.
The workflow timer starts properly when a workflow specifies a timer in the first state of the workflow process.
Binder attributes are copied correctly when building templates.
In hibernate mode, if a user double-clicks on an entry that has never been viewed, the program no longer crashes.
Nested HTML elements are allowed in the definition builder.
Height can be set for an IFRAME accessory.
The Move operation works when the saved location is changed.
Applets (file upload, edit in place, and workflow) work when iChain is being used.
Conferencing names now work in Teaming even when there are spaces in the name or there are uppercase characters in the name.
SXI as an extension that can be viewed as HTML.
The following sources provide information about Novell Teaming 1.0:
Online product documentation: Novell Teaming 1.0 Documentation Web site
Product documentation included in Novell Teaming:
To access the Teaming Help system, log in to Novell Teaming, then click thelink.
To access the Teaming guides from within Novell Teaming, click thelink on the Teaming Home page.
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 © 2008 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.