Novell Vibe OnPrem 3.1 Beta Readme

June 9, 2011

This Readme discusses issues that are unique to the Novell Vibe OnPrem 3.1 beta. For a list of issues in the released product, see the Novell Vibe OnPrem 3 Readme.

The Vibe 3.1 Beta 6 release should be installed in a testing environment.

1.0 Product Overview

2.0 Vibe System Requirements

3.0 Linux Installation Instructions

4.0 Windows Installation Instructions

5.0 Update Issues

6.0 Database Issues

7.0 Vibe Documentation

8.0 Documentation Conventions

9.0 Legal Notices

1.0 Product Overview

Novell Vibe OnPrem 3.1 offers many enhancements over prior Vibe versions for both Vibe users and administrators:

For Users

Task Improvements: Users can create and manage sub-tasks, create linked tasks, and more. For more information, see Working with Tasks Folders in the Novell 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 Novell 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 Newin the Novell 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 Novell 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 Novell 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 Novell 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 Novell Vibe OnPrem 3.1 Advanced User Guide.

For Administrators

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 Novell 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 Novell 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 Novell Vibe OnPrem 3.1 Administration Guide.

2.0 Vibe System Requirements

Novell 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 Novell Vibe OnPrem 3.1 Installation Guide.

3.0 Linux Installation Instructions

Make sure that the Linux server where you plan to install Novell 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 3.1 Authorized Beta tar file (novell-vibe-3.1.0-beta3.linux.tar) to a temporary directory on the 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 Authorized Beta tar file, then use the following command to untar the file:

tar xvf novell-vibe-3.1.0-beta3.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 Novell Vibe OnPrem 3.1 Installation Guide.

4.0 Windows Installation Instructions

Make sure that the Windows server where you plan to install Novell 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 3.1 Authorized Beta compressed executable file (novell-vibe-3.1.0-beta3.windows.zip) to a temporary directory on the Windows server, then extract the contents.
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 Novell Vibe OnPrem 3.1 Installation Guide.

5.0 Update Issues

Section 5.1, Updating a Teaming 2.1 System
Section 5.2, Updating a Vibe 3 System
Section 5.3, Updating to Beta 6 from a Previous Vibe 3.1 Beta
Section 5.4, Updating to Vibe OnPrem 3.1 Beta 3 and Later
Section 5.5, Updating to Vibe OnPrem 3.1 Beta 4 and Later
Section 5.6, Issues When Updating an Oracle Database
Section 5.7, Workflow Issues When Updating to Vibe 3.1

5.1 Updating a Teaming 2.1 System

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

5.2 Updating a Vibe 3 System

You can upgrade from Vibe 3 to Vibe 3.1 Beta 2 or later. For information about Updating from Novell Vibe 3 to Novell Vibe 3.1 in Update in the Novell Vibe OnPrem 3.1 Installation Guide.

5.3 Updating to Beta 6 from a Previous Vibe 3.1 Beta

You must complete the following procedure to successfully upgrade from a previous Vibe 3.1 beta release to Vibe 3.1 Beta 6:

Run the Vibe installation program by running the installer-teaming.exe file.
On the Installation Options page, select Update software and settings, then click Next.
On the Database Selection page, in the Setup section, select, The database already has been updated, then click Next.
Finish going through the installation program, then click Install to complete the installation.

Download to a temporary directory the SQL script that corresponds with your database type that you want to update to Beta 6.

These scripts are provided on the download page with the Vibe OnPrem 3.1 Beta 6 release.

MySQL	update-3.1.0.beta-3.1.0.beta6-mysql.sql
Microsoft SQL	update-3.1.0.beta-3.1.0.beta6-sqlserver.sql
Oracle	update-3.1.0.beta-3.1.0.beta6-oracle.sql

From a command prompt, run the following command to execute the SQL script that is appropriate for your database:

MySQL

mysql -uusername -ppassword< update-3.1.0.beta-3.1.0.beta6-mysql.sql

Microsoft SQL

osql -Uusername -Ppassword -i update-3.1.0.beta-3.1.0.beta6-sqlserver.sql

Oracle

sqlplus "/ as sysdba"

SQL> @update-3.1.0.beta-3.1.0.beta6-oracle.sql;

SQL> quit

Start the Vibe server.

For more detailed information about how to install Vibe, as well as how to start the Vibe server, see Linux: Installing and Setting Up a Basic Vibe Site in Basic Installation in the Novell Vibe OnPrem 3.1 Installation Guide.

5.4 Updating to Vibe OnPrem 3.1 Beta 3 and Later

When you are upgrading to Vibe 3.1 Beta 3 or later, you need to reset the search index on the Vibe site in order to see the new search functionality that is described in Understanding and Configuring Search Functionality in the Novell Vibe OnPrem 3.1 Administration Guide.

For information on how to reset the Vibe search index, see Resetting the Search Index in the Novell Vibe OnPrem 3.1 Installation Guide.

5.5 Updating to Vibe OnPrem 3.1 Beta 4 and Later

When you upgrade to Vibe 3.1 Beta 4 and later, a dialog box appears, informing you that you need to use the “Access Control for Zone Administration Functions” to define the initial access controls for all applications. This step is not necessary. However, if you do not complete the step, you see this dialog box each time you log in to Vibe as the Vibe administrator.

To accomplish this step and prevent the dialog from being displayed each time you log in:

Click the Administration icon in the upper right corner of the page.
Under System, click Access Control for Zone Administration.

The Configure Access Control page is displayed.
Click Save Changes > Close.

For information on how to accomplish the other tasks that are described in this dialog box, see Performing Post-Update Tasks in the Novell Vibe OnPrem 3.1 Installation Guide.

5.6 Issues When Updating an Oracle Database

Only new installations of Vibe 3.1 Beta 5 and later are supported with an Oracle database. Updating from a previous version of Vibe or from a previous beta release is not supported with an Oracle database.

5.7 Workflow Issues When Updating to Vibe 3.1

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 upgrading 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 Novell 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 Novell Vibe OnPrem 3.1 Advanced User Guide.
If workflows contain the Transition on Response transition, you must designate specific users as responders to the workflow question.

For more information on how to designate specific users as responders, see Designating Specific Users to Respond to a Workflow Question in the Novell Vibe OnPrem 3.1 Advanced User Guide.

6.0 Database Issues

Section 6.1, Error Occurs When Installing Vibe OnPrem 3.1 Beta with a MySQL 5.1.x Database

6.1 Error Occurs When Installing Vibe OnPrem 3.1 Beta with a MySQL 5.1.x Database

When installing Vibe OnPrem 3.1 beta wtih a MySQL 5.1.x database, an error occurs and the databse is not created.

To fix this problem, install Vibe 3.1 beta with a MySQL 5.5.x database.

7.0 Vibe Documentation

The following sources provide information about Novell Vibe 3.1:

Online product documentation: Novell Vibe 3.1 Documentation Web site
Product documentation included within Novell Vibe:
- Help System: Click the Help icon (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.1:

8.0 Documentation Conventions

In this documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path.

9.0 Legal Notices

Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.

Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.

Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export, or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. Please refer to the Novell International Trade Services Web page for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals.

Copyright © 2010-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.

For Novell trademarks, see the Novell Trademark and Service Mark list.

All third-party trademarks are the property of their respective owners.