Kablink Vibe is an enterprise collaboration tool designed to increase individual productivity, team effectiveness, and organizational success by providing the right set of tools to the right people.
Kablink Vibe 4 includes many enhancements over the previous version, as well as significant bug fixes. For a complete list of enhancements, see Kablink Vibe 4.0.1 Installation Guide.
Complete installation instructions are available in the Kablink Vibe 4.0.1 Installation Guide.
In order for an upgraded search index to be compatible with Vibe 4, you must re-index the search index after you upgrade to Vibe 4. For more information on how to re-index the search index, see Kablink Vibe 4.0.1 Installation Guide.
When creating a simple URL for a workspace or folder (as described in Kablink Vibe 4.0.1 User Guide), versions of Vibe prior to Vibe 4 allowed you to shorten the URL when referencing it. For example, if the simple URL was http://vibe_url:8080/vibe/admin/personal, you could shorten the URL by omitting the vibe. For example, http://vibe_url:8080/admin/personal. Short forms of URLs are not honored in Vibe 4, and therefore will have to be fixed after upgrading to Vibe 4.
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:
ehcache-hibernate.xml (single-server Vibe environment)
ehcache-hibernate-clustered.xml (clustered Vibe environment)
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:
Modify the ehcache-hibernate.xml file or the ehcache-hibernate-clustered.xml file to reflect the file’s state before the Vibe update.
The files are located in the following directories:
c:\Program Files\Novell\Teaming\apache-tomcat\ webapps\ssf\WEB-INF\classes\config
To see what these files looked like before the Vibe update, you can look in the backup directories in the following locations:
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 any customizations that existed in your old files.
(Conditional) If you have a clustered Vibe 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 Vibe.
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.
When you reset the workflow definitions to the factory default as described in Kablink Vibe 4.0.1 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 because of this issue, all definitions fail to reset.
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.
When using the Oracle JDK (both 7 and 8), the catalina.out file displays warning messages regarding the SAXParser.
These warning messages can safely be ignored; they are due to the following upstream Xerces libraries:
These libraries have been deprecated in Vibe 4, and will be removed in future releases of Vibe.
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.
Do not use extended characters or double-byte characters in the installation directory name for Kablink Vibe. The default location for the Vibe software is:
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.
IMPORTANT:Changing the Vibe database name is not recommended.
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.
For Mac users, Vibe looks for OpenOffice.org in the following directory on users’ Mac workstations:
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.
Change to the following directory:
c:\Program Files\Novell\Teaming\apache-tomcat-version\ webapps\ssf\WEB-INF\classes\config
Open the ssf.properties file in a text editor.
Locate the block of lines that start with:
Copy that set of lines to the clipboard of your text editor.
Open the ssf-ext.properties file, which is located in the same directory as the ssf.properties file.
Paste the block of lines you copied at the end of the ssf-ext.properties file.
Edit the location of the OpenOffice.org software to reflect its location in your organization.
Save and close the ssf-ext.properties file.
Close the ssf.properties file without saving it.
Stop and restart Vibe to put the new software location into effect on your Vibe site.
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.
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.
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.
If you have a Vibe zone that you no longer need, you should not delete it. Deleting zones in Vibe can cause significant issues with your Vibe site.
If you do need to delete a Vibe zone, first consult with Novell Support.
If you move a main (parent) task to another location on the Vibe site, all sub-tasks beneath that main task--even sub-tasks of sub-tasks (nested tasks)--all become main tasks within the original Tasks folder.
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 because of a bug in the way that OpenOffice communicates with WebDAV.
To resolve this issue, use the latest version of LibreOffice.
Theoption 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 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.
After downloading a single file or multiple files as a .zip file (as described in Kablink Vibe 4.0.1 User Guide), the file can be extracted only when using third-party tools such as iZip Unarchiver.
This issue is due to the fact that OS X does not currently handle ZIP64, the technology that is used to create the .zip file.
If you are experiencing issues when downloading multiple files (as described in Kablink Vibe 4.0.1 User Guide) when using Safari on Mac, ensure that the option is not selected.
On the General tab, ensure thatis not selected.
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 Kablink Vibe 4.0.1 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.
Because Photoshop files do not support editing via a WebDAV URL, photoshop files cannot be editing by using Edit-in-Place functionality in Vibe, as described in Kablink Vibe 4.0.1 Advanced User Guide.
When accessing Vibe with Safari 7.x with OS X 10.9.x and OS X 10.10, using the Edit-in-Place applet to edit a file (as described in Kablink Vibe 4.0.1 User Guide) and the File Upload applet (as described in Kablink Vibe 4.0.1 User Guide) results in an error and you are not able to edit or upload the file.
To configure Safari 7.x with OS X 10.9.x and OS X 10.10 to support the Vibe Edit-in-Place feature and to support adding files to folders when using a browser that does not support HTML 5:
With the Vibe site open, in Safari, click> .
Click thetab, then click .
Select, then in the click the drop-down arrow next to the Vibe site URL and select .
When a file contains multiple versions and a user attempts to add a note about the oldest version (Kablink Vibe 4.0.1 User Guide), the note is not always displayed.
Novell recommends that you never select the optionwhen configuring your LDAP synchronization. This feature will either be enhanced or removed in future Vibe releases. User accounts that are deleted cannot be recovered. As a best practice, leave this LDAP option unchecked. Doing so disables users rather than deleting them.
If you create Kablink Vibe users by importing users from an LDAP directory, all users in the LDAP directory might not appear in Vibe if the LDAP attribute that you are using for the cn attribute for the value of the attribute, and if you have multiple users with the same cn value, only the first instance of the duplicate user name is synchronized to Vibe.attribute is not unique. For example, if you are using the
To resolve this issue, use an attribute whose value is always unique across all containers, such as emailAddress.
In order to rename or move users in your LDAP directory, ensure that you have specified a value for the setting Kablink Vibe 4.0.1 Administration Guide. If a value is not specified for this setting, renaming or moving users in your LDAP directory might result in new users being created in Vibe., as described in
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.
Navigate to the folder in the original workspace where the definitions are located.
On the Workspace toolbar, click.
Expand the Form and View Designers tree, then click the definition that you want to move.
In the Definition Properties box, clickto display the workspace and folder tree for your Vibe site, then expand the tree as needed to display an appropriate destination for the definition.
To make the definition available in the copy of the original workspace, move the definition to a location in the tree that is above both the original workspace and the copy of the workspace.
To make the definition available globally on your Vibe site, move it to the root of the workspace and folder tree.
To move the definition, select the destination, then click.
Clicktwice to return to the main Vibe page.
Verify that the definition is now available in the copy of the workspace.
Repeat this procedure for each definition that needs to be available in the copied workspace.
When an exported workspace, folder, or entry has a link to something that isn’t included in the export file, the link doesn’t work correctly when it is imported to a different Vibe system.
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
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.
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.
If you use the Date attribute in a custom entry or view, users in different time zones might see a different date than you see.
Kablink Vibe stores the date as midnight on the selected date in the Vibe user’s time zone in GMT. For example, January 13, 2015 in the Mountain time zone is stored as GMT-7:00 (20150113T0700). 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.
If you cannot get your Vibe site to communicate with an external outbound mail system (such as Novell GroupWise), you might need to configure the Vibe outbound e-mail server with TLS over SMTP. If your e-mail application requires this type of configuration, you can configure Vibe with TLS over SMTP by using STARTTLS, as described in Kablink Vibe 4.0.1 Administration Guide.
When Vibe sends tasks to Outlook via an iCal attachment, the tasks appear as calendar events rather than as task items.
This is because of an issue with the way Outlook handles iCal events.
For more information about how Vibe uses iCal attachments to send calendar events and task items, see Kablink Vibe 4.0.1 User Guide.
If you have created a mapped drive to a Vibe folder via WebDAV (as described in Kablink Vibe 4.0.1 Advanced User Guide.), the WebDAV URL is no longer valid after upgrading the Vibe 4, and the mapped drives are no longer functional.
You must re-create any mapped drives that were previously created via WebDAV after upgrading the Vibe 4.
If you use the Kablink Vibe Edit in Place feature to edit a Word document using Office 2007 or Office 2010 on a Windows 7 workstation, Word requests a location to save the edited file rather than saving it back to the Vibe site. Depending on whether you want to run Vibe with a secure (HTTPS) or non-secure (HTTP) connection, this affects how you need to configure Vibe. For more information, see Kablink Vibe 4.0.1 Administration Guide.
If you copy the WebDAV URL associated with a Kablink Vibe folder and try to use the Add Network Location feature, Windows 7 might not be able to map the drive. Instead, you should always use the Map Network Drive feature when using Vibe on Windows 7.
When you use WebDAV functionality in a Mac environment, you encounter various limitations.
Edit-in-Place functionality is not supported on Mac when you use Microsoft Office as your document editor. To use Edit-in-Place functionality on Mac, you must use OpenOffice or LibreOffice as your document editor.
OpenOffice.org creates a new document version each time you click, 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.
To avoid creating unnecessary versions of the same document, do either of the following:
Do not clickmultiple times when editing a document. Instead, click only once, before closing the document in OpenOffice.org.
When you edit documents in Vibe, use a document editor other than OpenOffice.org, such as Microsoft Word.
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:
Change to the following directory:
Run the exporter program.
The errors about missing input and output files are to be expected.
Look for errors about missing libraries.
If there are library errors, install any libraries that are missing.
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 Kablink Vibe 4.0.1 Advanced User Guide.
Do not adjust theor entries indicated in the screen shot below. Doing so causes much more to be deleted than intended due to a logic flaw in the Vibe 4 code.
If you have any concerns regarding this issue, contact Novell Support for assistance.
Microsoft SQL 2012 is not a supported database for Vibe 4. Vibe 4 supports the same databases as were supported in Vibe 3.4. For more information about supported databases, see Kablink Vibe 4.0.1 Installation Guide.
You might receive database errors referring to Lock wait timeout exceeded. To resolve these errors:
Open the MySQL configuration file in a text editor.
The MySQL configuration file is at the following location, depending on your operating system:
c:\Program Files\MySQL\MySQL Server version\my.ini
Add the following section to the MySQL configuration file:
[mysqld] transaction-isolation = READ-COMMITTED
Save your changes and close the editor.
When viewing a Vibe calendar within the mobile app, only the first instance of a repeating calendar entry is displayed. All subsequent entries are missing from the mobile app.
If you have re-compiled or re-built Vibe in a Development environment, your Vibe installation is not supported by Novell. Alternatively, please seek support for custom Vibe deployments in the Kablink Community or the Novell Vibe discussion forum.
This excludes JSP-based changes made to facilitate the development of custom Forms and Views.
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.
Change to the directory where a server-config.wsdd file is located.
A Vibe installation includes two server-config.wsdd files. The default locations of these files vary by platform:
c:\Program Files\Novell\Teaming\apache-tomcat-version\webapps\ ssf\WEB-INF c:\Program Files\Novell\Teaming\apache-tomcat-version\webapps\ ssr\WEB-INF
In the following line, change false to true:
<parameter name="sendMultiRefs" value="false"/>
Save the server-config.wsdd file, then exit the text editor.
Create a backup copy of the modified server-config.wsdd file.
If you update the Vibe software, the server-config.wsdd file is overwritten by the Vibe Installation program. You must either restore the updated file after the update or repeat the modification.
Repeat the procedure for the second server-config.wsdd file in the Vibe software.
On the Configure Default Settings page of your workspace, thefield does not accept extended characters. Use only alphabetic characters and numbers in simple URLs.
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.
To ensure that your Kablink Vibe site is adequately secure, keep your operating system updated with all patches and security fixes.
The following sources provide information about Kablink Vibe 4:
Online product documentation: Kablink Vibe 4 Documentation Web site
Product documentation included within Kablink Vibe. Click theicon (question mark) in the upper right corner of the Vibe Home page.
Novell, hereby, offers to give any third party a complete machine-readable copy of the source code of Kablink Vibe, 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.
For information about legal notices, trademarks, disclaimers, warranties, export and other use restrictions, U.S. Government rights, patent policy, and FIPS compliance, see https://www.novell.com/company/legal/.
Copyright © 2016 Novell, Inc. All Rights Reserved.