Kablink Vibe OnPrem 3.1 offers many enhancements over prior Vibe versions for both Vibe users and administrators:
Task Improvements:
Users can create and manage sub-tasks, create linked tasks, and more. For more information, see Working with Tasks Folders
in the Kablink Vibe OnPrem 3.1 User Guide.
Landing Page Improvements:
Users can modify the location of elements in the landing page editor by dragging and dropping, they can input HTML via an HTML editor, and more. For more information, see Setting Up Your Landing Page
in the Kablink Vibe OnPrem 3.1 Advanced User Guide.
What’s New Improvements:
The What’s New page now allows users to comment on entries, share entries, subscribe to entries, tag entries, and more, all directly from the What’s New page. For more information, see Finding What’s New
in the Kablink Vibe OnPrem 3.1 User Guide.
Workspace and Folder Quotas:
Workspace and folder owners can set data quotas on workspaces and folders. For more information, see Setting a Data Quota for Workspaces and Folders
in the Kablink Vibe OnPrem 3.1 Advanced User Guide.
Folder View Improvements:
Folder owners can modify folder columns by changing the column titles and the order in which columns appear. For more information, see Configuring Folder Columns
in the Kablink Vibe OnPrem 3.1 User Guide.
Workflow Improvements:
Workflow creators can specify who can do manual transitions, whether to transition the workflow after everyone has responded, and can specify individual e-mail addresses where notifications are to be sent. For more information, see Setting Access Controls on a Manual Transition,
Designating Specific Users to Respond to a Workflow Question,
and Sending E-Mail Notifications
in the Kablink Vibe OnPrem 3.1 Advanced User Guide.
Individual Folder Notifications:
Folder owners can set their own digest notification schedules for their folders. For more information, see Configuring Folders to Send E-Mail Notifications to Other Users
in the Kablink Vibe OnPrem 3.1 Advanced User Guide.
Tracking All Sent E-Mails:
Like a personal e-mail Outbox for the Vibe site, you can configure a folder or any e-mail address to receive all e-mail messages that you personally send from the Vibe site. For more information, see Setting Up a Folder or External E-Mail Address to Receive All Sent E-Mail Messages
in the Kablink Vibe OnPrem 3.1 Advanced User Guide.
Search Improvements:
The Search feature in Vibe 3.1 has been improved and is more accurate and efficient than in past versions of Vibe. By default, the Search automatically removes words that have no inherent meaning, searches for the root of a word instead of exactly what the user specifies, and returns words regardless of whether they contain accents. Furthermore, Vibe administrators can configure or disable these features. For more information, see Understanding and Configuring Search Functionality
in the Kablink Vibe OnPrem 3.1 Administration Guide.
Disable Users:
Administrators can disable Vibe user accounts instead of deleting them. For more information, see Disabling Vibe User Accounts
in the Kablink Vibe OnPrem 3.1 Administration Guide.
Restrict Access Rights of Users by Domain:
Administrators can restrict the access rights of users, depending on the domain they are using to access the Vibe system. For more information, see Restricting Access Rights of Users Outside the Firewall
in the Kablink Vibe OnPrem 3.1 Administration Guide.
Kablink Vibe 3.1 system requirements (including requirements for mobile devices that access the Vibe mobile interface) are listed in Vibe OnPrem System Requirements
in the Kablink Vibe OnPrem 3.1 Installation Guide.
Make sure that the Linux server where you plan to install Kablink Vibe meets the system requirements.
If a Web server is currently running on the Vibe server, stop it, and preferably disable it.
Create or select a non-root Linux user and group that you want to own the Vibe directories and files and to run the Vibe software.
Download the Vibe software to a temporary directory on your Linux server.
In a terminal window, become root by entering su - and the root password.
Change to the temporary directory where you downloaded the Vibe 3.1 tar file, then use the following command to untar the file:
tar xvf kablink-vibe-3.1.0.linux.tar
In the directory where you downloaded and extracted the Vibe software, enter the following command to start the Vibe Installation program:
./installer-teaming.linux
Complete installation instructions are available in the Kablink Vibe OnPrem 3.1 Installation Guide.
Make sure that the Windows server where you plan to install Kablink Vibe 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 Vibe server, stop it, and preferably disable it.
Download the Vibe software to a temporary directory on your Windows server.
In Windows Explorer, browse to the directory where you downloaded and extracted the Vibe software, then double-click the installer-teaming.exe file to start the Vibe Installation program.
Complete installation instructions are available in the Kablink Vibe OnPrem 3.1 Installation Guide.
You can upgrade from Vibe 3 to Vibe 3.1. For information about Updating from Kablink Vibe 3 to Kablink Vibe 3.1
in Update
in the Kablink Vibe OnPrem 3.1 Installation Guide.
If you are upgrading from Teaming 2.1 or earlier, you must first update to Kablink Vibe 3 before you can upgrade to Kablink Vibe 3.1. For information on how to update to Novell Vibe 3, see “Update” in the Kablink Vibe OnPrem 3 Installation Guide.
Because of enhancements made to workflow functionality in Vibe 3.1, you might see issues with access control functionality in workflows throughout your Vibe site when you upgrade from 2.1 or later to Vibe 3.1. After upgrading, you or other advanced Vibe users who create workflows should test all workflows that contain access controls to ensure the workflows are functioning correctly. If you find that access controls in the workflow are not functioning as expected, investigate the following causes:
If workflows contain the Transition Into This State or Transition Out of This State access controls and the users who have been granted access to transition entries in the workflow do not have access to the folder or workspace where the entry is contained as it transitions through the workflow, users who have been granted access to transition entries in the workflow must also be granted Read rights and Modify rights in the workflow.
For more information on how to grant users access within a workflow, see Adding Access Controls to a Workflow
in the Kablink Vibe OnPrem 3.1 Advanced User Guide.
If users have been granted Modify access in a workflow and the users do not have access to the folder or workspace where the entry is contained as it transitions through the workflow, users must also be granted Read access to the workflow.
For information on how to grant users with Read access to a workflow, see Adding Access Controls to a Workflow
in the Kablink Vibe OnPrem 3.1 Advanced User Guide.
If you have done performance tuning for your Vibe cache, you might experience caching issues after you upgrade from a previous release to Vibe 3, 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 upgrade.
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 upgrade 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 upgrade:
Modify the ehcache-hibernate.xml file or the ehcache-hibernate-clustered.xml file to reflect the file’s state before the Vibe upgrade.
The files are located in the following directories:
|
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 Vibe upgrade, you can look in the backup directories in the following locations:
|
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 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.
When upgrading to Vibe 3.1, each user who has used a previous version of Vibe must clear his or her browser’s cache, regardless of the browser he or she is using. Not clearing the browser cache results in an incorrect Vibe display.
Ensure that you communicate this to each Vibe user in your system.
Various aspects of the Vibe interface have been redesigned and enhanced in Vibe 3.1. Some of these enhancements affect entries, folders, user profiles, and user workspaces. If you have made customizations to these areas of Vibe, you must reset these definitions in order to see the Vibe 3.1 enhancements. For more information, see Resetting Your Definitions
in Updating from Kablink Vibe 3 to Kablink Vibe 3.1
in the Kablink Vibe OnPrem 3.1 Installation Guide.
Search functionality has been improved in Vibe 3.1. For optimal search performance, you need to re-index the search index after you upgrade to Vibe 3.1. For more information, see Resetting the Search Index
in Updating from Kablink Vibe 3 to Kablink Vibe 3.1
in the Kablink Vibe OnPrem 3.1 Installation Guide.
After upgrading 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 upgrade.
These performance issues do not persist on subsequent visits to the Vibe site.
Section 6.1, The Vibe Server and the Lucene Server Must Use the Same JDK
Section 6.2, Character Restrictions in Usernames and Passwords
Section 6.3, Username Character Restrictions for LDAP Synchronization and Login
Section 6.4, Character Restrictions in the Software Installation Directory Name
Section 6.6, File Conversion and Indexing Fails for Kablink Vibe
Section 6.11, JDK Dependency for SSL Connections to WebDAV Servers
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.
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.
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 file. The default location for the Vibe software is:
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 upgrade 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.
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.
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.
Change to the following directory:
Open the ssf.properties file in a text editor.
Locate the block of lines that start with:
edit.in.place.mac.editor
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.
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.
To prepare your Windows Server 2008 R2 machine for use with Vibe:
In the Control Panel, double-click .
Click .
Open the ports that Vibe needs to use through the firewall:
After defining the two ports, click in the Windows Firewall Settings dialog box to allow Vibe to communicate through the firewall on these ports.
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.
Section 7.4, Filenames That Contain Double-Byte Characters Are Changed When Creating a ZIP File
Section 7.10, Windows Update for WebDAV Functionality for Windows Vista and Windows XP
Section 7.11, WebDAV/Edit in Place Issues with Microsoft Windows Vista and Microsoft Office
Section 7.13, WebDAV URL Issue on Windows Vista and Windows 7
Section 7.18, The User Profile Does Not Support Custom JSP Files
If you create Kablink Vibe OnPrem users by importing users from an LDAP directory, all users in the LDAP directory might not appear in Vibe if the value of the LDAP attribute that you are using to synchronize users is not unique. For example, if you are using the cn attribute to identify users and if you have multiple users with the same cn value, only the first instance of the duplicate username is synchronized into Vibe.
To resolve this issue, use an attribute whose value is always unique across all containers, such as emailAddress.
Renaming or moving users in your LDAP directory might result in new users being created in Vibe. This is because when you rename or move a user in the LDAP directory, Vibe assumes that the new name (or the new location of the same name) represents a new user, not a modified user, and creates a new Vibe user.
To resolve this issue, you should specify an LDAP attribute that uniquely identifies the user. For more information, see LDAP Attribute to Identify a User or Group
in LDAP Connections
in the Kablink Vibe OnPrem 3.1 Installation Guide.
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, click to 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 .
Click twice 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 won’t work correctly when it is imported to a different Vibe system.
When Vibe 3 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.
For information on how to download files in Vibe, see Downloading Files
in the Kablink Vibe OnPrem 3.1 User Guide.
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.
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 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 for them in their time zone. This discrepancy will be resolved in an upcoming release.
If you send an e-mail message from the Kablink Vibe site, and you have a typographical error or invalid recipient in the field, an error displays, along with a 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 field.
IMPORTANT:Install this update only on Windows Vista and Windows XP. Do not install this update on Windows 7.
In order to use the Kablink Vibe Edit in Place feature in your browser on Windows Vista and Windows XP, you must install the following Windows WebDAV update:
Software Update for Web Folders (KB907306).
This Windows update enables OpenOffice.org and Microsoft Office to interact correctly with the Vibe Edit in Place feature.
Microsoft Windows Vista has some issues with WebDAV access that affect all WebDAV interactions. In addition, a Vista-specific issue with applets can prevent the Kablink Vibe Edit in Place feature from working properly. Be sure you are running the latest version of Vista. Be sure you have installed the Windows WebDAV update described in Section 7.10, Windows Update for WebDAV Functionality for Windows Vista and Windows XP.
Windows Vista users who are using Internet Explorer might see a Java warning when they try to use Edit in Place. (Firefox users do not see this error.)
To configure Internet Explorer to support the Vibe Edit in Place feature:
In Internet Explorer, click .
Click , select , then click .
In the field, specify the URL of your Vibe server, then click .
Select or deselect as appropriate for your Vibe server.
Click , then click to save the security settings.
To configure Windows Vista to support the Vibe Edit in Place feature in Microsoft Office, you must add new keys to the Windows registry for each Microsoft Office application.
In Windows Explorer, navigate to Program Files/Microsoft Office/Office12.
Scroll down to each Microsoft Office .exe in turn:
excel.exe powerpnt.exe winword.exe ...
Right-click each executable, then click .
Click .
Select , then select from the drop-down list.
Reboot the computer.
You should now be able to use the Vibe Edit in Place feature with Microsoft Office files.
NOTE:Although these steps enable Edit in Place for Vibe, they do not fix Vista’s inability to attach via WebDAV in Vibe.
For additional information on applets, view the following Sun bulletins:
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 Editing Files with Edit-in-Place Functionality
in Configuring Vibe to Support WebDAV on Windows 7
in the Kablink Vibe OnPrem 3.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 Vista and 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 Vista and Windows 7.
When using 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 as your document editor.
For more information, see Using WebDAV to Edit Individual Files
in the Kablink Vibe OnPrem 3.1 Advanced User Guide.
Because of limitations with WebDAV on Mac, you cannot use WebDAV to view a Vibe folder in a Mac environment.
For more information, see Using WebDAV on a Vibe Folder
in the Kablink Vibe OnPrem 3.1 Advanced User Guide.
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:
Launch a Web browser.
Navigate to the Microsoft Download Center and install the Software Update for Web Folders (KB907306) http://www.microsoft.com/downloads/details.aspx?FamilyId=17C36612-632E-4C04-9382-987622ED1D64&displaylang=en
Follow the on-screen instructions to install the software update.
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 click multiple 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.
You can delete specific versions of a file, as described in Deleting Existing Versions of a File
in the Kablink Vibe OnPrem 3.1 User Guide.
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:
/opt/novell/teaming/stellent-converter/linux/x86
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 Enabling Vibe Forms and Views to Reference JSP Files
in the Kablink Vibe OnPrem 3.1 Advanced User Guide.
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:
In the following line:
<parameter name="sendMultiRefs" value="false"/>
change false to true.
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.
User names that contain extended characters are not displayed in the area of e-mail messages that are sent from Vibe and are viewed in GroupWise.
To resolve this issue, you need to modify the startup scripts for your Vibe server. The startup scripts and their locations differ slightly depending on whether your Vibe installation is running on a Linux or a Windows server.
Open the catalina.sh file in a text editor. This file is located in the following directory:
opt/novell/teaming/apache-tomcat/bin
Search for UTF8 in the file, then change this to UTF-8.
Stop and restart the Vibe server.
Open the service.bat file in a text editor. This file is located in the following directory:
c:\Program Files\Novell\Teaming\apache-tomcat\bin
Search for UTF8 in the file, then change this to UTF-8.
Open the catalina.bat file in a text editor. This file is located in the following directory:
c:\Program Files\Novell\Teaming\apache-tomcat\bin
Search for UTF8 in the file, then change this to UTF-8.
Stop and restart the Vibe server.
On the Configure Default Settings page of your workspace, the field 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.
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.
As a workaround in Excel:
Import the report.csv file into Excel by using .
Select the report.csv file, then click .
Select , select , then click .
Select as the delimiter, click , then click .
Excel should now display the Chinese characters correctly.
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.
To ensure that your Kablink Vibe site is adequately secure, keep your operating system updated with all patches and security fixes.
For a list of the bugs that have been fixed since Vibe OnPrem 3, see the Kablink Vibe OnPrem 3.1 Bug List. You can look up the bug numbers in Bugzilla for more information about each bug.
The following sources provide information about Kablink Vibe 3.1:
Online product documentation: Kablink Vibe 3.1 Documentation Web site
Product documentation included within Kablink Vibe:
Help System: Click the icon (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.
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 © 2011 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.