Kablink Vibe 3.2 Readme

5.1 Updating a Vibe 3.1 System

You can update from Vibe 3.1 to Vibe 3.2. For more information, see Updating From Kablink Vibe 3.1 to Kablink Vibe 3.2 in Update in the Kablink Vibe 3.2 Installation Guide.

5.2 Updating a Vibe 3 System

To update a Vibe 3 system to Vibe 3.2, you must first update to Vibe 3.1 before you can update to Vibe 3.2. For information on how to update to Vibe 3.1, see “Update” in the Novell Vibe 3.1 Installation Guide.

5.3 Updating a Teaming 2.1 System

If you are upgrading from Teaming 2.1 or earlier, you must first update to Kablink Vibe 3 before you can update to Vibe 3.1 and then 3.2. For information on how to update to Novell Vibe 3, see “Update” in the Kablink Vibe 3 Installation Guide.

5.4 Caching Issues When Updating from Teaming 2.x to Vibe 3.x

If you have done performance tuning for your Vibe cache, you might experience caching issues after you update from a previous release to Vibe 3 or later, if you have modified either of the following configuration files:

You encounter issues only if you have modified either of the above files, because these files are overwritten during the Vibe update.

The issues you experience differ depending on whether you have a single-server Vibe environment, or whether you have a clustered Vibe environment.

If you have modified the ehcache-hibernate.xml file in order to optimize the caching performance for your single Vibe server, you might notice a decrease in caching performance after you update Vibe.

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 Vibe site are not always visible, or other erratic behavior. This is because information is not being cached and synchronized correctly across the various Vibe servers.

To resolve caching issues after an update:

5.5 Issues When Updating from a Previous Vibe Release to Vibe 3.2

5.6 Performance Issues after Updating to a New Version

After updating your Vibe system to a new version, you experience performance issues when you first navigate the Vibe system. This is because Vibe needs to compile the JSPs after an update.

These performance issues do not persist on subsequent visits to the Vibe site.

5.7 Cannot Reset Factory Workflow Definitions When Workflow Is in a Custom State

When resetting the workflow definitions to the factory default as described in Resetting Your Definitions in Update in the Kablink Vibe 3.2 Installation Guide, you encounter a general error informing you to contact your system administrator if you have added a custom state to a factory workflow (such as the Task workflow) and there is currently an entry in the custom state.

If you are trying to reset multiple definitions simultaneously and the factory workflow fails to reset due to this issue, all definitions will fail to reset.

5.8 Manual Ehcache Configuration Settings Are Not Preserved on Update

If you manually edited the ehcache configuration settings by modifying the ehcache-hibernate-clustered.xml file on your Vibe server, the settings are not preserved when you update Vibe.

If you manually edited the ehcache-hibernate-clustered.xml file, you must complete the following after updating Vibe in order to preserve your settings:

6.1 The Vibe Server and the Lucene Server Must Use the Same JDK

If Vibe 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.

6.2 Character Restrictions in Usernames and Passwords

Do not use extended characters or double-byte characters in Kablink Vibe usernames and passwords. This includes usernames and passwords that are synchronized from an LDAP directory into Vibe.

This limitation is caused by the open source Spring Security that Vibe uses for authentication, in combination with the various authentication methods (both basic authentication and form-based authentication) used by single sign-on products such as Novell Authentication Manager, by Web services, and by WebDAV. Only ASCII characters are properly interpreted in all combinations.

6.3 Username Character Restrictions for LDAP Synchronization and Login

LDAP usernames that contain special characters ( / \ * ? " < > : | ) cannot be used as Kablink Vibe usernames. If your LDAP directory includes usernames with these characters, they synchronize to the Vibe site, but the associated users cannot log in.

These characters cannot be used in a Vibe username because a Vibe username becomes the user’s workspace title, and the workspace title becomes an element of the hierarchical path that leads to the workspace. These characters are not legal characters in Linux and Windows pathnames.

6.4 Character Restrictions in the Software Installation Directory Name

Do not use extended characters or double-byte characters in the installation directory name for Kablink Vibe file. The default location for the Vibe software is:

6.5 Default Database Name

When you have the Kablink Vibe installation program create the Vibe database for you, the database is given the name of sitescape. This database name is currently hard-coded into the database creation scripts used by the installation program. The name dates back to the name of the company that previously owned the Vibe software.

If you want the Vibe database to have a different name, you can edit the database creation script, then run the database creation script manually before you start the Vibe installation program. If you do this, you must also update the JDBC URL when you run the Vibe installation program. Prior to upgrading to a new version, the database update scripts also need to be modified.

6.6 File Conversion and Indexing Fails for Kablink Vibe

Kablink Vibe uses OpenOffice.org converters to prepare documents for indexing by the Lucene Index Server. The OpenOffice.org converters are also used on the Vibe site for viewing documents (by converting them to HTML). OpenOffice.org must be continuously running as a daemon in order for it to perform its document conversion function. Before running OpenOffice.org as a daemon, you must first run it with a user interface and respond to the Welcome prompts. Otherwise, OpenOffice.org fails to perform the file conversions. Run OpenOffice.org as the same user that runs Vibe.

6.7 Restrictions on Applet Support

Applets are not supported on 64-bit Firefox on a system with a Java Runtime Environment (JRE) earlier than 1.6.0_12.

On a 64-bit operating system, updating to JRE 1.6.0.12 or later enables the applets to work.

For example, multi-file drag-and-drop from the desktop, file paste from the desktop, Edit in Place, and the graphical display in the workflow editor do not work where applets are not supported.

6.8 Edit in Place Support for Mac Users

For Mac users, Vibe looks for OpenOffice.org in the following directory on users’ Mac workstations:

/Applications/OpenOffice.org.app

If your organization’s standard location for OpenOffice.org is in a different location on users’ workstations, you can reconfigure Vibe to look for OpenOffice.org in your preferred location.

6.9 NFS Support

NFS file system mounts are supported for placing the Vibe file repository on a remote server from where Vibe is running. However, NFS file system mounts are not supported for placing the Lucene index on a remote server from where the Lucene Index Server is running.

6.10 Firewall Issue on Windows Server 2008 R2

On Windows Server 2008 R2, the firewall is enabled by default and ports 80 and 443 are blocked. Vibe needs to use these ports, so Vibe needs to be an allowed program on your Windows server.

6.11 JDK Dependency for SSL Connections to WebDAV Servers

If you want to use an SSL connection between your Kablink Vibe site and a WebDAV server, and if the WebDAV server has a self-signed certificate rather than a certificate provided by a certificate authority, you must use the Sun JDK. The existing Vibe functionality for handling self-signed certificates is not compatible with the way the IBM JDK handles self-signed certificates.

6.12 MySQL Version on openSUSE 11.2

OpenSUSE 11.2 includes MySQL 5.1.36. This version of MySQL can cause problems with the Vibe database connection. To resolve database problems, update to MySQL 5.1.40 or later.

7.1 Cannot Perform Actions on Multiple Tasks Simultaneously

When you perform the following actions on multiple tasks in the task list, your changes are reverted when you refresh the page:

You can reorder tasks, make tasks sub-tasks, and make sub-tasks main tasks when you perform these actions one task at a time, as described in Reordering Tasks One Number at a Time, Making a Main Task a Sub-Task, and Making a Sub-Task a Main Task in the Kablink Vibe 3.2 User Guide.

7.2 Saving a Vibe Document with OpenOffice on Linux Creates Two File Versions

When you edit a file in Vibe with OpenOffice on Linux, two new file versions are generated each time you save the file.

This issue is due to a bug in the way that OpenOffice communicates with WebDAV.

For more information about editing files in Vibe, see Viewing and Editing Files in Working with Folder Entries in the Novell Vibe 3.2 User Guide.

7.3 Link (URL) Element on a Landing Page Does Not Work With Internet Explorer

When you create a link from a landing page with the Link (URL) element, the link is not activated on the landing page unless you select the Open the URL in a new window option when configuring the element.

For more information about how to add this element to your landing page, see Adding Content to Your Landing Page in the Kablink Vibe 3.2 Advanced User Guide.

7.4 Safari on Mac Does Not Allow RSS Feed Creation with the Add Bookmark Option

The Add Bookmark option that is available after you paste the RSS URL into the browser does not work when you use Safari on a Mac. Instead, you must use the Bookmark menu to create an RSS feed.

This is an issue with the way Safari deals with RSS feeds; it is not an issue with Vibe itself.

7.5 Adding Files with Drag and Drop Does Not Work on Mac

Because of Java limitations on the Mac, you cannot drag and drop files to add files to a folder or to attach files to an entry as described in Dragging and Dropping Files in Working with Folder Entries in the Kablink Vibe 3.2 User Guide.

You can use the Vibe applet that is used for drag and drop if you copy the file that you want to add and paste it into the applet. However, dragging the file onto the applet does not work.

7.6 LDAP Synchronization Issues

7.7 Workspace Copy Limitation

When you copy a workspace, the custom form and workflow definitions in that workspace are not transferred to the copy of the workspace. You can work around this limitation by moving the definitions to a higher level in the workspace tree.

7.8 Export/Import Limitation

When an exported workspace, folder, or entry has a link to something that isn’t included in the export file, the link won’t work correctly when it is imported to a different Vibe system.

7.9 File Deletion Issue with MySQL

If you are using MySQL, you might see the following error when you upload files and then delete them:

class org.hibernate.exception.GenericJDBCException
Cannot release connection

This is related to a MySQL defect. To resolve the problem, update MySQL to version 5.1.40 or later.

7.10 Password-Protected Files

Files that have been password-protected in the application where they were created cannot be viewed on the Kablink Vibe site. This is working as designed.

7.11 Folder and Workspace Nesting Issue

Because of database restrictions, the maximum number of nested folders and workspaces that Vibe allows is 45. For example, you can create a folder within a folder, then create a folder within that folder, and so forth, until the folder structure is 45 levels deep. You cannot exceed 45 levels in the folder structure.

7.12 Date Attribute in Custom Entries and Views

If you use the Date attribute in a custom entry or view, users in different time zones might see a different date compared to what you see.

Kablink Vibe stores the date as midnight on the selected date in the Vibe user’s time zone in GMT. So, for example, January 13, 2010 in the Mountain time zone is stored as GMT-7:00 (20100113T0700). No problem appears for people in the same time zone. However, for people in a different time zone, Mountain time zone midnight could be a different day in their time zone. This discrepancy will be resolved in an upcoming release.

7.13 Firefox Limitation When Sending E-Mail

If you send an e-mail message from the Kablink Vibe site, and you have a typographical error or invalid recipient in the Add E-Mail Addresses field, an error displays, along with a Return to Previous Page button. In Firefox, you return to the Send E-Mail page, but the message content is lost. In Internet Explorer, the message content is retained.

When you use Firefox to send e-mail from the Vibe site, select Vibe users as recipients whenever possible, or copy recipient e-mail addresses to avoid typographical errors in the Add E-Mail Addresses field.

7.14 WebDAV Issues

7.15 Viewing a Vibe Folder through Windows Explorer Displays an Additional Folder on Windows XP

On Windows XP, when you view a Vibe folder through Windows Explorer, an additional sub-folder with the same name as the parent folder might be displayed.

To resolve this problem:

7.16 Data Quota Issue with OpenOffice.org

OpenOffice.org creates a new document version each time you click Save, instead of creating one new version when you exit the edited document. This behavior can cause you to quickly meet your data quota. You can avoid creating unnecessary versions of the same document, and if you do create them, you can delete them.

7.17 Cannot Perform Document Conversions with Latest Releases of LibreOffice

LibreOffice 3.4.x cannot be used as the document converter for Vibe due to a bug in LibreOffice. If you want LibreOffice to perform document conversions for Vibe, uninstall LibreOffice 3.4.x and install either LibreOffice 3.3.4 or the latest version of OpenOffice.

For more information about document conversions with LibreOffice and OpenOffice in Vibe, see Configuring the Document Converter on Linux in the Kablink Vibe 3.2 Installation Guide.

For more detailed information regarding this LibreOffice defect, see Bug 43433

7.18 HTML Conversion Error on a Linux Server

If you see an HTML Conversion Error when you try to view a file, your Vibe Linux server might be missing necessary libraries.

To install the missing libraries:

7.19 The User Profile Does Not Support Custom JSP Files

When you create or modify 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 Vibe Forms and Views to Reference JSP Files in the Kablink Vibe 3.2 Advanced User Guide.

7.20 Cannot Read the Latest File Version if Filenames Are Not the Same Case

With previous versions of Vibe that are installed on Linux, when you add a new version of an existing file, and the filenames for the current version and the new version do not have the same case (for example, test.odp and test.ODP), Vibe recognizes these as two different files in the database, and you cannot access the latest version of the file.

To fix this problem, simply rename the filename to match the case of the original filename.

In Vibe 3 and later, this issue does not exist if the original file was uploaded after the upgrade to Vibe 3. Filenames can be uploaded to the Vibe site with mismatching case (for example, test.odp and test.ODP) and the Vibe database recognizes them as the same file.

8.1 Log File Does Not Accurately Report Database Creation

The installer.log file sometimes reports that the Vibe database was created successfully when it actually wasn’t. Ensure that your database was created successfully.

The Vibe database is called sitescape.

For more information about the Vibe database, see Planning the Vibe Database in the Kablink Vibe 3.2 Installation Guide.

9.1 Multi-Reference Values in SOAP Payloads

By default, Kablink Vibe SOAP payloads do not generate multi-reference values. You can change the server-config.wsdd files so that multi-reference values are generated.

10.1 Extended Characters Are Not Allowed in Simple URLs

On the Configure Default Settings page of your workspace, the Define URL field does not accept extended characters. Use only alphabetic characters and numbers in simple URLs.

10.2 Extended and Double-Byte Characters in Attachment Filenames

If Outlook users send postings to the Kablink Vibe site and if the messages have attachments with extended or double-byte characters in the filenames, the attachment does not arrive on the Vibe site unless the Exchange server is properly configured. To configure the Exchange server to pass the filenames correctly, follow the instructions in Foreign Characters Appear as Question Marks When Sent from OWA.

10.3 Filenames That Contain Extended and Double-Byte Characters Are Changed When Creating a ZIP File

When Vibe 3 or later is used to create a ZIP file with files that contain double-byte characters in the filename, the filenames for the downloaded files are displayed as _file1, _file2, _file3, etc. This is because the Java ZIP file facility is not capable of creating filenames that contain double-byte characters.

The files within Vibe remain unchanged.

This is due to a problem in the way Java handles non-ASCII characters. For information on how you can modify the way Vibe deals with .zip files that are downloaded that contain extended or double-byte characters in the filename, see Enabling ZIP Files That Contain Extended or Double-Byte Characters in the Filename to Be Downloaded in the Kablink Vibe 3.2 Administration Guide.

For information on how to download files in Vibe, see Downloading Files in the Kablink Vibe 3.2 User Guide.

10.4 Chinese Characters in Activity Logs

When a report.csv file for an activity report is opened in Microsoft Excel, Chinese characters do not display correctly, even though the report.csv file has been created correctly, because Excel always reads the file using the ISO Latin character set.

One workaround is to use the OpenOffice.org Calc spreadsheet program instead of Excel. It displays Chinese characters correctly.

Excel should now display the Chinese characters correctly.

10.5 Internet Explorer 6 Limitation with International Characters in Filenames

In Internet Explorer 6, if you upload a file whose filename includes international characters into a File folder, and if you edit that file and create a new version, the link to the original version of the file no longer works, because Internet Explorer 6 double-encoded the filename. To resolve this issue, update to Internet Explorer 7 or later.