January 15, 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
Global searches
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.
When the Teaming Installer prompts you for the type of installation:
If you are updating an existing Teaming installation with Support Pack 2, enter 2 for .
This option preserves your existing databases and offers customized values for prompts that match the configuration of your existing system.
or
If you are installing Novell Teaming Support Pack 2 as your initial Teaming installation, enter 1 for .
This option creates new databases and offers default values for prompts.
Continue with the installation as prompted.
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:
/opt/icecore/liferay-portal-tomcat-5.5-jdk5-4.3.0/webapps/ ssf/WEB-INF/license
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 2, you must completely reindex the search index in order to resolve existing index problems that are now fixed.
After installing Support Pack 2:
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.
To review the known issues for Support Pack 1, see the Teaming 1.0 Support Pack 1 Readme.
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 .
Click the tab, 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 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 .
Click the tab.
Select , then select from the pull-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.
Liferay’s 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 the 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 portlet menu 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). These are benign and can safely be ignored:
service.impl.PortletLocalServiceImpl - "Portal with name EXT_1..."
deploy.hot.PluginPackageHotDeployListener
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.
If you change your interface language, the change is immediate in the portal but requires logging out and logging in again before the Novell Teaming portlets see the change.
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 .
Select as the delimiter, click , then click .
Excel should now display the Chinese characters correctly.
To review the bug fixes in Support Pack 1, see the Teaming 1.0 Support Pack 1 Readme.
Fixed editing of group membership .
Fixed License Manager to make incremental additions of premium options easier.
Fixed search failures when searching for tags.
Fixed the search results display when the selected display style is .
Fixed the search index corruption when adding or changing an ACLs.
Removed the JavaScript* error in Internet Explorer when using the date widget on the form.
IMPORTANT:To take advantage of these fixes, make sure you follow the instructions in Section 2.3, Reindexing the Search Index after you install Support Pack 2.
Fixed the list in advanced workflow.
Fixed importing of workflow definitions to get the correct user IDs.
Fixed the workflow viewer applet so it does not crash if the state name is empty.
Show correct entry owner in e-mail notifications. (It was showing the last person who modified the entry.)
Disabled subscriptions to entry comments.
E-mail sent from the option now has a valid URL.
Provided better user help on search accessories and surveys.
Added more documentation on how the blog facility works when filtering by tags.
Added the Web Services Guide (Web Services Guide.pdf).
Fixed the Community Accessories list so that it expands and collapses correctly from one login to the next.
Fixed the wiki to handle the situation where an invalid title link is entered (for example, [[ ]] ).
Fixed the invalid HTML on the Date element form.
Fixed the HTML of the Project Management view to be well formed.
Fixed the Date element to show the proper date. (It was off by one day.)
Retrieved the proper owner of binders. (The owner value comes from the createdBy field.)
Fixed the display of dates on file attachments to be consistent with the entry creation date.
Wrote build information to the Tomcat log to indicate which product version is running.
Filenames are no longer modified when doing a download operation. (Spaces were being turned into a plus sign (+).)
Fixed the display of select box, radio button and check box columns in the Folder table view to show the caption instead of the data name.
Fixed an error when showing or hiding a community accessory.
Fixed the clause limit for Oracle* databases.
Fixed the display of the About page in Chinese.
Fixed the resport.csv file for activity reports so that Chinese characters are handled correctly.
The following sources provide information about Novell Teaming 1.0:
Installation: The following files are available after you extract the software from the .exe file and before you install the software:
readmeen.html
TeamingInstallationGuide.pdf (the Novell Teaming 1.0 Installation and Configuration Guide)
Product documentation included in Novell Teaming:
To access the Teaming Help system, log in to Novell Teaming, then click the link.
To access the Teaming guides from within Novell Teaming, click the link on the Teaming Home page.
Online product documentation: Novell Teaming 1.0 Documentation Web site
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.