Novell Teaming 1.0 Support Pack 1

November 16, 2007

1.0 Product 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

2.0 Teaming Installation Instructions

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:

  1. If you are updating an existing Teaming installation with Support Pack 1, enter 2 for Update.

    This option preserves your existing databases and offers customized values for prompts that match the configuration of your existing system.


    If you are installing Novell Teaming Support Pack 1 as your initial Teaming installation, enter 1 for Full Install.

    This option creates new databases and offers default values for prompts.

  2. Continue with the installation as prompted.

2.1 Multiple License Key Files

If you purchased a number of licenses in such a way that you received multiple license key files, you need to consolidate the license information.

  1. Use any one of the license key files when you install Novell Teaming.

  2. After Novell Teaming is installed and running, copy all your license key files to the following directory:

  3. Log in to Novell Teaming as the Teaming Site Manager.

  4. In the Teaming Administration portlet, click Manage License.

    Your current license information is displayed.

  5. Scroll to the bottom of the license information, then click Reload License File.

    The Teaming server reads all the license key files in the license subdirectory and displays your total license information.

3.0 Teaming Known Issues

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:

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 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 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 in Novell Teaming, 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 (for example, by 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 e-mail address.

Alternatively, it is possible to use the e-mail address as the screen name (i.e., the 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 Teaming session times out while viewing a folder with a table view, the Liferay pop-up box is obscured. This will be fixed 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..."


  • 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.

4.0 Teaming Bug Fixes

4.1 Unlimited User License

The unlimited user license now works correctly.

4.2 Workflow Assignments

Workflow assignments can now be configured on the Folder Configuration form.

4.3 Workflow State Deletion

When you delete a workflow state, an unnecessary Transitions item no longer appears.

4.4 Permalink Initialization

Permalink initialization has been improved for first-time users.

4.5 Form Designer

The fieldset element in the Form Designer now works correctly.

4.6 Profile Synchronization

The user’s name in Liferay profiles and Teaming profiles is now synchronized during login.

4.7 File Synchronization

Modified files are correctly synchronized in mirror folders.

4.8 HTML Conversion Error

If a file fails to convert into HTML for display, the error message more clearly describes the problem.

4.9 Extra Space in the Description Field

An extra space character no longer appears in the Description field of forms.

4.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.

4.11 French Entry Definitions

Entry definitions in the View Designer can now be added in French.

4.12 Chinese Characters

Chinese characters in uploaded filenames are now handled correctly. However, if you added 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.

5.0 Teaming Documentation

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:

    • readme.txt

    • installation-guide.pdf (the Novell Teaming 1.0 Installation and Configuration Guide)

  • Product documentation included in Novell Teaming:

    • 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

6.0 Documentation Conventions

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