Novell Teaming 1.0 SP1 for Windows
This document (5007121) is provided subject to the disclaimer at the end of this document.
patches this patch supersedes
patches that supersede this patch
| Product | Status | Next Superceded By | Last Superceded By |
|---|---|---|---|
| Novell Teaming 1.0 | Obsolete | Novell Teaming 1.0 SP2 for Windows | Novell Teaming 1.0 SP2 for Windows |
| Novell Teaming + Conferencing 1.0 | Obsolete | Novell Teaming 1.0 SP2 for Windows | Novell Teaming 1.0 SP2 for Windows |
Warning: The patch associated with this readme is obsolete; it is no longer available for download.
patch attributes
document
abstract
This is an update to Novell Teaming 1.0. This can be applied to Novell Teaming or Novell Teaming + Conferencing products.
details
Overview:
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 automaton with customized forms
Global searches
System Requirements:
See Product Documentation
Documentation
The following files are available after you extract the software from the .zip file
and before you install the software:
readme_en.pdf
installation-guide.pdf (the Novell Teaming 1.0 Installation and Configuration
Guide)
To access the Novell Teaming Help system, log in to Novell Teaming, then click the Help
link.
To access the Novell Teaming guides from within Novell Teaming, click the Getting
Started link on the Novell Teaming Home page.
Online product documentation: Novell Teaming 1.0 Documentation Web site (http://
www.novell.com/documentation/team_plus_conf)
Installation:
1. If you are updating an existing Teaming installation, enter 2 for Update. This option preserves your existing databases and offers values for prompts that match the configuration of your existing system.
or
If you are installing Teaming Support Pack 1 as your initial Teaming installation, enter 1 for Full Install.
This option creates new databases and offers default values to prompts.
2. Continue with the installation as prompted.
Known Problems and Limitations:
Teaming Known Issues
Section 3.1, WebDAV / Edit-in-place Issues with Microsoft Vista,
Section 3.2, Drag-and-Drop Issue on SLED,
Section 3.3, Update Failure in Folder Summary View of Tasks,
Section 3.4, Log Out / Log In Required to Change Interface Language,
Section 3.5, Log Out / Log In Required for WebDAV Access after Password Change,
Section 3.6, E-Mail Authentication Not Supported by Default,
Section 3.7, Novell Teaming Error Log and Internet Explorer,
Section 3.8, Liferay Timeout Box Obscured,
Section 3.9, Benign Warnings in Liferay Log File,
Section 3.10, NullPointerException at Shutdown,
Section 3.11, Extra Directory Created in FileRepository Tree,
3.1 WebDAV / Edit-in-place Issues with Microsoft Vista
Microsoft Vista has numerous problems with WebDAV access affecting all WebDAV interactions.
There is also a Vista-specific issue with applets that prevents the edit-in-place feature from working
properly. Monitor Microsoft support bulletins for updates on these issues. For the applets, refer to
the following Sun bulletins:
Bug 6440902 (http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6440902)
Bug 6432317 (http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6432317)
3.2 Drag-and-Drop Issue on SLED
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 (JRE). This version has a bug which prevents dragand-
drop from operating properly with the Novell Teaming file upload applet, However, copy-andpaste
still works. Updating the JRE to 1.5.x on the SLED client machine resolves the problem.
3.3 Update Failure in Folder Summary View of Tasks
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.
3.4 Log Out / Log In Required to Change Interface Language
If you change your interface language, the change is immediate in the Liferay portal, but requires
logging out and logging in again before Novell Teaming responds to the change.
3.5 Log Out / Log In Required for WebDAV Access after Password Change
If you change your password through the Liferay portal or by other means, you might need to log
out and log in again for WebDAV access to work properly.
3.6 E-Mail Authentication Not Supported by Default
The Liferay portal allows authentication by IDs other than screen name (e.g., 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
Liferays 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 e-mail
address.
Alternatively, it is possible to use the e-mail address as the screen name (i.e., screen name and e-mail
address fields are identical). This, however, is a decision that cannot be changed and must be part of
the initial population of the database from LDAP.
3.7 Novell Teaming Error Log and Internet Explorer
In Internet Explorer, if you try to download the Novell Teaming system error log using the Reports
menu item in the Teaming Administration portlet, you must have the Security setting set to Medium
or less for the download to work. Firefox works in all cases.
3.8 Liferay Timeout Box Obscured
If your session times out while viewing a folder with a table view, the Liferay pop-up box will be
obscured. We hope to fix this in a future update.
3.9 Benign Warnings in Liferay Log File
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...
3.10 NullPointerException at Shutdown
When you shut down Novell Teaming, the log file contains a message about a
"NullPointerException". This error is benign.
3.11 Extra Directory Created in FileRepository Tree
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.
change log
Teaming Bug Fixes
1. Unlimited User License
The unlimited user license now works correctly.
2. Workflow Assignments
workflow assignments can now be configured on the Folder Configuration form.
3. Workflow State Deletion
When you delete a workflow state, an unnecessary Transitions item no longer appears.[336944]
4. Permalink Initialization
Permalink initialization has been improved for first-time users.
5. Form Designer
The fieldset element in the Form Designer now works correctly.
6. Profile Synchronization
The users name in Liferay profiles and Teaming profiles is now synchronized during login.
7. File Synchronization
Modified files are correctly synchronized in mirror folders.
8. HTML Conversion Error
If a file fails to convert into HTML for display, the error message more clearly describes the
problem.
9. Extra Space in the Description Field
An extra space character no longer appears in the Description field of forms.
10. Translation Issues
Missing translations have been provided in the TinyMCE HTML editor form. Translation issues
regarding Simplified Chinese vs. Traditional Chinese have been resolved.[335656]
11 French Entry Definitions
Entry definitions in the View Designed can now be added in French.[336931]
12 Chinese Characters
Chinese characters in uploaded filenames are now handled correctly. However, if you added a tags
to Chinese files using the original Teaming release, the tags are still broken after installing SP1.
You must use the Tag Search feature to find the broken tags, delete them, then re-enter the correct
tag.[335654]
file contents
| Files Included | Size | Date |
|---|---|---|
| teaming-1.0.1-win.zip | 149.6 MB (156963468) | 2007-11-19 10:45:44 |
| readme_en.pdf | 218.8 KB (224078) | 2007-11-19 10:45:44 |
| readme_5007121.html | N/A | 2008-05-14 16:52:18 |
disclaimer
The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information. Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.
Novell is a registered trademark of Novell, Inc. in the United States and other countries. SUSE is a registered trademark of SUSE Linux AG, a Novell business. *All third-party trademarks are the property of their respective owners.
© 2007 Novell, Inc. All Rights Reserved.