To help you maximize your Vibe investment, Novell Vibe 3.4 includes licensing changes related to external users.
External users can now be added to the Vibe system at no additional cost.
Guest user access is now included without the need to purchase a separate license.
These licensing changes are important not only because they allow you to expose your Vibe site to users outside of your organization at no additional cost, but because future versions of the Vibe software will provide enhanced tools for sharing information with external users.
There are some restrictions, so refer to the EULA for more information.
Novell Vibe 3.4 also includes enhanced mobile device support for the Vibe mobile app, as well as various bug fixes.
Complete installation instructions are available in the Novell Vibe 3.4 Installation Guide.
You can update from Vibe 3, Vibe 3.1, or Vibe 3.2 to Vibe 3.3. To update to Vibe 3.4, you must first update to Vibe 3.3. You need to update the database separately from the software. For more information, see Novell Vibe 3.4 Installation Guide.
If you are upgrading from Teaming 2.1 or earlier, you must first update to Novell Vibe 3 before you can update to Vibe 3.3, and then to Vibe 3.4. For information on how to update to Novell Vibe 3, see “Update” in the Novell Vibe 3 Installation Guide.
Because of an issue that was addressed regarding attachment file sizes, you should re-index the search index after you update to Vibe 3.3 in order for attachment sizes to be displayed correctly. For more information on how to re-index the search index, see Novell Vibe 3.4 Installation Guide.
When you update your high availability Vibe system to Vibe 3 or later from an earlier version, any deferred log records that currently exist become incompatible with each other.
To ensure that no incompatibility issues arise with deferred update logs during the update to Vibe 3 or later, you must clear all deferred update logs prior to upgrading.
For information on how to clear deferred update logs, see Novell Vibe 3.4 Administration Guide.
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.
When you update to Vibe 3.3 from a previous version, you should reset the definitions for your Vibe site if you want your folder and workspace definitions to no longer include the Branding element. This element is no longer useful and could be potentially confusing to users. Branding a folder or workspace is now done as described in Novell Vibe 3.4 Advanced User Guide.
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 Novell Vibe 3.4 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.
After applying the Security Update 1 (POODLE fix) for Vibe 3.4, you must update the advanced settings in your reverse proxy provider (such as NetIQ Access Manager or Apache).
For systems fronted by Apache:
Add the following setting to the /etc/httpd/conf.d/ssl.conf file:
SSLProxyProtocol ALL -SSLv2 -SSLv3
For systems fronted by NetIQ Access Manager:
Add the following advanced option (You can access thefrom the tab):
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 Novell 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 Novell 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 Novell Vibe. The default location for the Vibe software is:
Do not use extended characters or double-byte characters in directory names in the path to the Novell Vibe file repository. The default location for the file repository root directory is:
The Oracle Outside In viewers that are used to render various file types into HTML for viewing in the Vibe site and for indexing do not handle directory names that include extended characters and double-byte characters.
When you have the Novell 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.
IMPORTANT:Changing the Vibe database name is not recommended.
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 22.214.171.124 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:
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.
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.
Open the ports that Vibe needs to use through the firewall:
After defining the two ports, clickin 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 Novell 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.
Novell Vibe uses Oracle Outside In 8.3.5 viewer technology for displaying documents and images on the Vibe site and for indexing documents. This viewer technology relies on Support Pack 1 of the Microsoft Visual C++ 2005 Redistributable Package. If the Windows server where you install Vibe does not already have the latest version of the Visual C++ Redistributable Package installed, you must install it before your Vibe site can function properly. The required version of the Visual C++ Redistributable Package is available from:
For more information, see New Dependency for Outside In 8.2.0 and Newer Versions, Windows Products Only (Doc ID 468895.1) on the Oracle Support Web site. Oracle Support site login is required in order to access the support document.
To successfully use Novell Vibe with Novell Access Manager, Access Manager 3.1 SP1 IR1 is required. This version is available on the Novell Downloads Web site.
There are four system user accounts in Vibe. You should not delete any of these accounts, because doing so can cause issues with your Vibe system. The system accounts are: Admin, E-mail Posting Agent, Synchronization Agent, and Guest.
If you do need to delete any of these user accounts, first consult with Novell Support.
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.
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 Novell Vibe 3.4 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.
When a file contains multiple versions and a user attempts to add a note about the oldest version (Novell Vibe 3.4 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 Novell Vibe 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.
In order to rename or move users in your LDAP directory, ensure that you have specified a value for the setting Novell Vibe 3.4 Installation 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 create a link from a landing page with the Link (URL) element, the link is not activated on the landing page unless you select theoption when configuring the element.
In Vibe 3.3, theoption for the Enhanced View element was modified. If you added this option to a landing page in a previous release and you upgrade to Vibe 3.3, the option is automatically removed when you edit your landing page and then click . If you edit the landing page and then click , the element becomes unusable on the landing page.
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 Novell Vibe site. This is working as designed.
You cannot use the Novell Vibe Move This Folder feature to move one Mirrored File folder inside of another Mirrored File folder.
If you edit a file in a mirrored folder and then check the version history, you see only the latest version of the file and only the latest version of the file is available for editing from the mirrored location. This is working as designed. Document versioning is not currently available in mirrored folders.
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.
You can view current Novell Vibe license usage by clicking the _emailPostingAgent, _jobProcessingAgent, and _synchronizationAgent) as local users. The Administrator counts as an active user, but the other four local users do not count against your Vibe license usage.icon, then under , clicking . The License Report currently counts Administrator, Guest, and three internal users (
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.
Novell Vibe stores the date as midnight on the selected date in the Vibe user’s time zone in GMT. 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.
In the GroupWise client, you cannot drag a file that is attached to a GroupWise message and drop it successfully into the Novell Vibe drag-and-drop window that opens when you clickon the Folder Entry toolbar. Save the attachment first, then drag and drop the saved file into the drag-and-drop window.
In order to access a Novell Vibe site from the GroupWise Windows client, the time setting on the GroupWise user’s workstation must match the time setting on the Vibe server within five minutes. If there is a discrepancy of more than five minutes, the GroupWise client’s attempt to contact the Vibe site times out. If possible, reset the time of the server or the workstation to the correct and matching time.
If the time difference is a necessary part of your system configuration, you can change the timeout setting for Web services such as GroupWise that authenticate to the Vibe site through WS-Security.
Make a backup copy of the following file:
Open the server-config.wsdd file in a text editor.
Search for the following section:
<handler type="java:org.apache.ws.axis.security.WSDoAllReceiver"> <parameter name="passwordCallbackClass" value="org.kablink.teaming.remoting.ws.security.PWCallback"/> <parameter name="action" value="UsernameToken Timestamp"/> </handler>
Insert a timeToLive parameter with large timeout value (for example, 86400 for 24 hours).
<handler type="java:org.apache.ws.axis.security.WSDoAllReceiver"> <parameter name="passwordCallbackClass" value="org.kablink.teaming.remoting.ws.security.PWCallback"/> <parameter name="action" value="UsernameToken Timestamp"/> <parameter name="timeToLive" value="86400"/> </handler>
Save the server-config.wsdd file, then restart the server.
This configuration change affects all client applications that authenticate to the server through WS-Security, not just GroupWise.
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 Novell Vibe 3.4 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 Novell Vibe 3.4 Advanced User Guide.
If you send an e-mail message from the Novell Vibe site, and you have a typographical error or invalid recipient in thefield, 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 thefield.
When accessing Vibe with Safari 7.x and OS X 10.9.x, using the Edit-in-Place applet to edit a file (as described in Novell Vibe 3.4 User Guide) and the File Upload applet (as described in Novell Vibe 3.4 User Guide) results in an error and you are not able to edit or upload the file.
To configure Safari 7.x and OS X 10.9.x 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 .
Other Vibe applets include the workflow graphical designer, and the dragging and dropping of files in the following circumstances:
When clicking Add Files in older browsers that do not support HTML 5
When pressing the Ctrl key when clicking Add Files in any browser (this invokes the file upload applet rather than leveraging HTML 5 to do the upload)
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 Novell Vibe 3.4 Advanced User Guide.
Renaming a Vibe file through a WebDAV client renames the attachment file only. It does not rename the title of the Vibe folder entry that the file is associated with.
This is because of the capability recently added to Vibe that allows you to specify any title of your choosing when creating a File entry, regardless of the filename of the associated file. Historically, the title for all File entries was the same as the filename of the associated file.
IMPORTANT:Install this update only on Windows Vista and Windows XP. Do not install this update on Windows 7.
In order to use the Novell Vibe Edit-in-Place feature in your browser on Windows Vista and Windows XP, you must install the following Windows WebDAV update:
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 Novell 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.22.5, 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 thefield, specify the URL of your Vibe server, then click .
Select or deselectas 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.
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 Novell 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 Novell Vibe 3.4 Administration Guide.
If you copy the WebDAV URL associated with a Novell 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 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.
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 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 Novell Vibe 3.4 Advanced User Guide.
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, Novell 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 Novell 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 .
Selectas 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 Novell Vibe site is adequately secure, keep your operating system updated with all patches and security fixes.
The following sources provide information about Novell Vibe 3.4:
Online product documentation: Novell Vibe 3.4 Documentation Web site
Product documentation included within Novell Vibe. Click theicon (question mark) in the upper right corner of the Vibe Home page.
In addition to the Novell Vibe product documentation, the following resources provide additional information about Vibe 3.4:
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-2015 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.
For Novell trademarks, see the Novell Trademark and Service Mark list.
All third-party trademarks are the property of their respective owners.