Kablink Teaming 3 Beta Readme
This Readme discusses issues that are unique to the Teaming 3 beta. For a list of issues in the released Teaming product, see the Novell Teaming 2.1 Readme.
1.0 Product Overview
Kablink Teaming 3 offers many enhancements over prior Teaming versions for both Teaming users and administrators:
For Users
-
New User Interface: The user interface for Teaming 3 has been significantly redesigned to facilitate maximum productivity.
-
Basic Search Improvements: Basic search now allows you to refine your search by field name, AND/OR statements, date range, and more. For more information, see
Using Basic Search
in the Kablink Teaming 3 User Guide. -
Advanced Search Improvements: When you perform an advanced search, you can now specify whether you want to search by relevance or date. For more information, see
Using Advanced Search
in the Kablink Teaming 3 User Guide. -
Expanded User Profile: The User Profile section in Teaming 3 has been expanded to rival other professional knowledgebases such as LinkedIn. Now you can include more information to share with your colleagues, such as your education, qualifications, and competencies. For more information, see
Modifying Your Profile
in the Kablink Teaming 3 User Guide.If you have modified the User Profile definition for your Teaming site, these changes are not displayed when you upgrade to Teaming 3. To display these changes, complete the steps in
Resetting Your Definitions
in the Kablink Teaming 3 Installation Guide. -
Quick View Profile Dialog Box: The Quick View Profile dialog box is displayed when you click on a user’s Presence icon
. It enables you to see information about that user, view the user’s micro-blog or workspace, follow the user, and more.
If you have modified the User Profile definition for your Teaming site, this dialog box is not displayed when you upgrade to Teaming 3. To display these changes, complete the steps in
Resetting Your Definitions
in the Kablink Teaming 3 Installation Guide. -
Entry-Level Access Controls: You can now set access controls on individual entries that differ from those set on the parent folder. For more information, see
Controlling Access to Entries
in the Kablink Teaming 3 Advanced User Guide. -
Delete Past Versions of Documents: You can now delete past versions of a document.
-
Minor Versioning: You can now track documents on a more granular level. For example, instead of versions of a document being 1, 2, 3, Teaming documents can now be versioned as 1, 1.2, 2, 2.2, 2.3, and so forth.
-
Version Notes: You can now add personal notes to specific versions of a document.
For Administrators
-
Site-wide brand: Create a site-wide brand and manage users’ ability to create individual brands on lower-level workspaces. For more information, see
Creating a Site-Wide Brand
in the Kablink Teaming 3 Administration Guide. -
Default home page: Set a default home page where all users are first taken when they access the Teaming site. You can create a separate default home page for visitors. For more information, see
Setting a Default Home Page
in the Kablink Teaming 3 Administration Guide. -
User and group management: When you move or rename users and groups that are being synchronized via LDAP, Teaming now recognizes the change and maintains the association between the user or group that was moved or renamed and the LDAP server. For more information, see
LDAP Attribute to Identify User
in the Kablink Teaming 3 Installation Guide. -
User Visibility: Hide one set of users from another set of users. For example, you might want to do this if your Teaming site has users from more than one company and you want users to see only the users who belong to their same company. For more information, see
Restricting Groups of Users from Seeing One Another
in the Kablink Teaming 3 Administration Guide. -
Integrations with Novell Conferencing: Teaming 3 provides tight integrations with Novell Conferencing, which allows you to start an instant meeting with other Teaming users, directly from the Teaming interface.
Teaming administrators must configure Novell Messenger to work with Novell Conferencing.
-
Ability to Send Teaming Mail Messages from a Custom Address: Configure Teaming to send e-mail messages and notifications from a zone-specific or site-wide address. In previous versions of Teaming, when a user sends an e-mail message from Teaming, the message can be shown only as being from that specific user.
For more information, see
Configuring Teaming to Send E-Mail Messages and Notifications from a Custom Address
in the Kablink Teaming 3 Administration Guide.
2.0 Teaming System Requirements
Kablink Teaming 3 system requirements (including requirements for mobile devices that access the Teaming mobile interface) are listed in Teaming System Requirements
in the Kablink Teaming 3 Installation Guide.
3.0 Linux Installation Instructions
-
Make sure that the Linux server where you plan to install Kablink 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 Kablink Teaming 3 Installation Guide.
4.0 Windows Installation Instructions
-
Make sure that the Windows server where you plan to install Kablink 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 Novell Teaming 3 Installation Guide.
5.0 Update Issues
5.1 Caching Issues When Upgrading from a Previous Teaming Release to Teaming 3 Beta 5 and Later
If you have done performance tuning for your Teaming cache, you might experience caching issues after you upgrade from a previous Teaming release to Teaming 3 Beta 5 or later, if you have modified either of the following configuration files:
-
ehcache-hibernate.xml (single-server Teaming environment)
-
ehcache-hibernate-clustered.xml (clustered Teaming environment)
You encounter issues only if you have modified either of the above files, because these files are overwritten during the Teaming upgrade. For a description of issues that you might encounter, see Visible Issues.
To resolve caching issues after an upgrade:
-
Modify the ehcache-hibernate.xml file or the ehcache-hibernate-clustered.xml file to reflect the file’s state before the Teaming upgrade.
The files are located in the following directory:
Linux:
/opt/novell/teaming/apache-tomcat/ webapps/ssf/WEB-INF/classes/config
Windows:
c:\Program Files\Novell\Teaming\apache-tomcat\ webapps\ssf\WEB-INF\classes\config
To see what these files looked like before the Teaming upgrade, you can look in the backup directory, in the following location:
Linux:
/opt/novell/teaming/teaming-backup/ ssf/WEB-INF/classes/config
Windows:
c:\Program Files\Novell\Teaming\teaming-backup\ ssf\WEB-INF\classes\config
IMPORTANT:Use these backup files only as a reference. Do not replace the entire ehcache-hibernate.xml file or ehcache-hibernate-clustered.xml file with the files in the backup directory. The new files contain important new settings that must be retained. You must manually add to the new files any customizations that existed in your old files.
-
(Conditional) If you have a clustered Teaming environment and you need to modify the ehcache-hibernate-clustered.xml file, ensure that the values for the hostName, multicastGroupAddress, and multicastGroupPort properties are correct in the new ehcache-hibernate-clustered.xml file.
-
Save any modifications that you made to the configuration files, then restart Teaming.
5.1.1 Visible Issues
The issues you experience differ depending on whether you have a single-server Teaming environment, or whether you have a clustered Teaming environment.
5.1.1.1 Issues When Running a Single Server Teaming Environment
If you have modified the ehcache-hibernate.xml file in order to optimize the caching performance for your single Teaming server, you might notice a decrease in caching performance after you upgrade Teaming.
5.1.1.2 Issues When Running a Clustered Teaming Environment
If you have modified the ehcache-hibernate-clustered.xml file in order to configure your clustered environment, you might notice that items that are added to the Teaming site are not always visible, or other erratic behavior. This is because information is not being cached and synchronized correctly across the various Teaming servers.
5.2 LDAP Issue When Updating from a Previous Beta to Beta 4 or Later
After you upgrade from a previous Teaming 3 beta to Beta 4 or later, Teaming users who are being synchronized through LDAP might be automatically deleted and re-created the first time your LDAP connection is manually or automatically synchronized. For information about synchronizing with an LDAP directory, see Synchronizing Users and Groups from an LDAP Directory
in the Novell Teaming 3 Administration Guide.
You can work around this issue by completing the following procedure before the LDAP synchronization occurs after your upgrade to Beta 4 or later:
-
Log in to the Teaming site as the Teaming administrator.
-
Click the icon
in the upper right corner of the Teaming page.
-
Under , click .
The Configure LDAP Synchronization page is displayed.
-
In the field, delete the current setting.
The field should now be blank.
-
Select , then click to synchronize your LDAP connection.
-
After the LDAP synchronization is complete, close the LDAP Synchronization Results dialog box.
-
In the field, specify either GUID or objectGUID, depending on whether you are using eDirectory or Active Directory.
-
Synchronize the LDAP connection again by clicking .
5.3 Issues Updating from Teaming 2.1 to Teaming 3
5.3.1 Clearing Your Browser Cache
When upgrading to Teaming 3, each user who has used a previous version of Teaming must clear his or her browser’s cache, regardless of which browser he or she is using. Not clearing the browser cache results in Teaming not being displayed correctly.
Ensure that you communicate this to each Teaming user in your system.
5.3.2 Resetting Your Definitions
Various aspects of the Teaming interface have been redesigned and enhanced in Teaming 3. Some of these enhancements affect entries, folders, user profiles, and user workspaces. If you have made customizations to these areas of Teaming, you must reset these definitions in order to see the Teaming 3 enhancements. For more information, see Resetting Your Definitions
in Updating from Kablink Teaming 2.1 to Kablink Teaming 3
in the Novell Teaming 3 Installation Guide.
5.3.3 Calendar Entries Are Not Displayed After You Upgrade a Distributed System
After upgrading your distributed Teaming system to Teaming 3, your calendar entries are not displayed. This is a known issue and will be resolved soon.
5.4 Performance Issues after Updating to a New Version
After upgrading your Teaming system to a new version, you experience performance issues when first navigating the Teaming system. This is because Teaming has to compile the JavaScript after an upgrade.
These performance issues do not persist on subsequent visits to the Teaming site.
6.0 Browser Issues
6.1 You Cannot View the User Profile Page
When using the Internet Explorer 8 browser you cannot view the user profile page. This includes your own user profile as well as user profiles of other Teaming users. This is a known issue and will be resolved soon.
This issue is present only in Internet Explorer 8. If you want to view user profiles in Teaming, use a different browser, such as Internet Explorer 7 or Firefox.
6.2 Adding a Micro-Blog Entry When Using Safari Crashes the Browser
When using the Safari browser, when you attempt to add a micro-blog entry as discussed in Posting a Micro-Blog
in the Kablink Teaming 3 User Guide, the browser crashes and you are unable to add the micro-blog entry.
7.0 Teaming Issues
7.1 File Names That Contain Double-Byte Characters Are Changed When Creating a ZIP File
When Teaming 3 is used to create a ZIP file with files that contain double-byte characters in the file name, the file names for the downloaded files are displayed as _file1, _file2, _file3, etc. This is because the Java ZIP file facility is not capable of creating file names that contain double-byte characters.
The files within Teaming remain unchanged.
For information on how to download files in Teaming, see Downloading Files
in the Kablink Teaming 3 User Guide.
7.2 The User Profile Does Not Support the Use of Custom JSP Files
When creating or modifying attributes for the User Profile form and view in the Form and View Designers tool, you cannot reference custom JSP files.
This ability still exists for modifying attributes for workspaces, folders, and entries, as described in Enabling Teaming Forms and Views to Reference JSP Files
in the Kablink Teaming 3 Advanced User Guide.
7.3 Profile Pictures Display as Distorted
When you view your profile picture, the dimensions of the picture are distorted and the image is stretched. This is a known issue and will be resolved soon.
7.4 The Quick View Profile Dialog Box Is Not Perfectly Aligned
The Quick View Profile dialog box is not always displayed next to the Presence icon that you click. This is a known issue and will be resolved soon.
8.0 Installation Issues
8.1 The Teaming Server and the Lucene Server Must Use the Same JDK
If Teaming and the Lucene Index are running on separate servers, you must use the same JDK for both servers. Using different JDKs results in undesired behavior, such as not being able to create calendar entries.
8.2 Server Crashes with an ‘Out of Memory’ or ‘Stack Overflow’ Error
The JVM settings specified during installation are not being written to the service.bat file, which causes the server to crash with an Out of Memory or Stack Overflow exception. This is a known issue and will be resolved soon.
9.0 Security Issue
To ensure that your Kablink Teaming site is adequately secure, keep your system updated with all patches and security fixes.
10.0 Teaming Documentation
The following sources provide information about Kablink Teaming 3:
-
Online product documentation: Kablink Teaming 3 Documentation Web site
-
Product documentation included within Kablink Teaming:
-
Help System: Click the icon (question mark) in the upper right corner of the Teaming Home page.
-
11.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.
12.0 Open Source Code
Novell, hereby, offers to give any third party a complete machine-readable copy of the source code of Kablink Teaming, under the terms of Sections 1 and 2 of version 2 of the GNU General Public License as published by the Free Software Foundation, on a medium customarily used for software interchange. Please contact Novell Developer Services or visit Kablnik.org if you require a copy of the same.
13.0 Legal Notices
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.
THIS DOCUMENT AND MODIFIED VERSIONS OF THIS DOCUMENT ARE PROVIDED UNDER THE TERMS OF THE GNU FREE DOCUMENTATION LICENSE WITH THE FURTHER UNDERSTANDING THAT:
1. THE DOCUMENT IS PROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT THE DOCUMENT OR MODIFIED VERSION OF THE DOCUMENT IS FREE OF DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE, OR NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY, ACCURACY, AND PERFORMANCE OF THE DOCUMENT OR MODIFIED VERSION OF THE DOCUMENT IS WITH YOU. SHOULD ANY DOCUMENT OR MODIFIED VERSION PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL WRITER, AUTHOR OR ANY CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY DOCUMENT OR MODIFIED VERSION OF THE DOCUMENT IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER; AND
2. UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER IN TORT (INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL THE AUTHOR, INITIAL WRITER, ANY CONTRIBUTOR, OR ANY DISTRIBUTOR OF THE DOCUMENT OR MODIFIED VERSION OF THE DOCUMENT, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER DAMAGES OR LOSSES ARISING OUT OF OR RELATING TO USE OF THE DOCUMENT AND MODIFIED VERSIONS OF THE DOCUMENT, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGES.
For Novell trademarks, see the Novell Trademark and Service Mark list.
All third-party trademarks are the property of their respective owners.