Vista Release 5

Vista Plus
Version 5.5.2
Release Notes
April 2, 2012
IMPORTANT: This document describes new features and updates in version 5.5.2 of Vista
Plusthe April 2011 SP (Service Pack). It includes compatibility information, descriptions
of the changes in version 5.5.2, and upgrade instructions. OpenText recommends that you
read this document in conjunction with the other documentation included with the
software. If any conflicts exist, the information in this document supersedes other Vista
Plus documentation.
Check the Vista Plus section of the OpenText Knowledge Center at https://
knowledge.opentext.com for any patches or documentation updates that may have been
posted after the initial release of this version of Vista Plus.
Note
The Vista Plus product suite is now marketed as OpenText Report and Output
Management. It is listed on the Knowledge Center under both the old and
new names.
Table of Contents
General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Supported Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Enhancements in Version 5.5.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Software Fixes and Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Update Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Copyright Open Text Corporation. All rights reserved.

This software product and documentation is licensed subject to the terms of the license agreement shipped with the product.
Vista Plus 5.5.2 Release Notes (April 2, 2012) 60131552.6
Page 1
General Information
General Information
While Vista Plus 5.5.2 is a Service Pack, it does include enhancements in addition to fixes
and performance improvements. It includes changes to the Vista Plus server, Web View,
vadmin, rcapture, the Server Admin Client, and the Windows Client, and new modules
for TransVue Tagging and LDAP user authentication. It includes all patches to Vista Plus
5.5.1 up through April 12, 2011; patches created after that date are not included.
This document contains five sections: supported configurations, descriptions of the
enhancements in version 5.5.2, a list of fixes and changes in the release, a list of known
issues, and installation information. For complete instructions on using Vista Plus, please
see the Vista Plus manuals and the online help.
As with any upgrade, please contact Vista Plus technical support before upgrading to
version 5.5.2.

Page 2
Supported Configurations
Note
Important! All Vista Plus components are supported only with released
versions of underlying software. Using Vista Plus with any beta or pre-release
version of a host operating system, Web browser, or other required software is
not supported.
These software versions were supported when this document was published.
However, we can effectively support Vista Plus only with software versions
that are also supported by their suppliers. Therefore, if a software vendor
drops support for one of the listed versions, we will no longer be able to
support Vista Plus with that version.
Note
Although we use virtual environments when developing and testing Vista

Plus, we do not specifically develop for or test Vista Plus for proper
performance with any server virtual environment, such as VMware, or
desktop virtual environment, such as Citrix. Therefore we do not list specific
virtual environment versions and configurations. We do, however, continue
to provide the same level of support described in the OpenText Maintenance
Handbook for customers who run Vista Plus in a virtual environment.
Note
For complete system requirements for any part of Vista Plus, see the Vista Plus
Server Installation Guide or, for the Windows Client, the Vista Plus Windows
Client Users Guide.
Vista Plus Server

Operating Sys. Version
Notes
HP-UX
11i v1
BUNDLE 11i (B11.11.0306), GOLDAPPS11i (B11.11.0606.446),

GOLDBASE11i (B11.11.0606.446), and PHSS_312211
11i v2
For Itanium and RISC processors; requires 11.23 Standard Patch

Bundle and patches PHSS_32502, PHSS_33349, PHSS_33350,
and PHSS_33352
11i v3
Note
IBM AIX
For Itanium and RISC processors

We strongly suggest you follow HPs recommendation and migrate to
Itanium processors rather than RISC. Although we will still support
customers who use RISC, we have not fully tested 5.5.2 on 11i v3 with a
RISC processor.
5.3
Tested with Technology Level 5, SP 6, and C++ runtime 10.1.0.2

and 8.0.0.7
6.1
Tested with:
Technology Level 6, SP3, with C++ runtime 11.1.0.1
Technology Level 3, with C++ runtime 10.1.0.2 and 9.0.0.1

Page 3
Operating Sys. Version
Notes
Sun Solaris
Requires UltraSPARC architecture; patch #111711-12 and, for 64bit versions, #111712-122
10
Requires UltraSPARC architecture and SUNWlibC patch

#119963-23
Server 2003
Standard or
Enterprise
Service Pack 2 or later
Windows
1.You can install the above patches or any patch listed by HP as superseding one of them. You
can see what patches are installed by entering the command swlist l patch.
2.The patches listed are the minimum revision levels. You can also install a later revision of the
same patch, if available. For example, for Solaris 9, you can install patch #111711-12 or any
higher available version. To see what patches are installed, enter the command showrev -p.
Database Support
Database Software
Oracle
MySQL
Version
10g
Notes
11g
For both: RAC environment and DataDirect 6.0

ODBC drivers; the necessary drivers are shipped
with Vista Plus as the Vista Plus Oracle ODBC
Connector
4.1.13 (UNIX)
4.1.13a (Windows)
With MyODBC 3.51 and ODBC Driver version

3.51.121
1.If you use MySQL, it must be installed on the Vista Plus server host. If you do not already have
MySQL installed, it is installed and configured for Vista Plus as part of a full server installation.
Note
Important! To install more than one Vista Plus database on the same UNIX
server host, you must use Oracle. You can have only one Vista Plus database
using MySQL on a server host. Installing one Vista Plus database using
MySQL and another using Oracle on the same host is not supported.

Page 4
Remote Capture Tools

In addition to the operating system versions listed above for the Vista Plus server, the
Vista Plus remote capture tools are supported on these operating systems.
Host Operating System Version
SUSE Linux Enterprise
Server
SLE 9
RedHat Enterprise
Server
5.x
HP Tru64 UNIX (OSF1)
5.1 B-2
Notes
SLE 10
Legacy Remote Capture Tools

Several operating system versions on which the Vista Plus remote capture tools were
supported in previous versions of Vista Plus are no longer fully supported by their
operating system vendors. Therefore, Vista Plus technical support can offer only limited
support for the remote capture tools on these platforms:
HP-UX
11.0
Sun Solaris
5.8
IBM AIX
5.1
Windows
2000 Server or
Advanced Server
Notes
These are the 5.3 capture tools, and do not have any
features introduced since that version, notably the
ability for vadmin to create text file renditions of
reports.
Service Pack 4
Customers who want to capture reports from a host using one of these operating system
versions can follow one of these procedures to install the remote capture tools on that
host:
To install the remote capture tools on one of the listed UNIX versions, use the
installation files contained in the server\Legacy Capture Tools directory. Do not use the
standard remote capture tools files found in the server\unix directory.
To install the remote capture tools on Windows 2000, perform a custom installation of
the Vista Plus Windows Server and select only the remote capture tools for
installation.
Note
Legacy remote capture tools for older operating system versions may also be
available. Contact technical support for more information.

Page 5
Capture Printer Port

Windows Version
Notes
Server 2003 Standard or Enterprise
Service Pack 1 or 2
Server 2008 R2 Standard or Enterprise
32-bit or 64-bit
LDAP Authentication Module

Product
Versions
Vista Plus Server
5.5.x
LDAP
Supports LDAPv3; tested using OpenLDAP

2.4.16.
Note
The LDAP Authentication module is a new feature of Vista Plus 5.5.2. See
User Authentication Using LDAP Passwords on page 9.
TransVue Tagging
Product
Versions
Vista Plus Server
5.5.2
Operating Systems
For rcapture and vp_load_index, any operating

system which supports the remote capture tools,
as listed in Remote Capture Tools on page 5.
The export connector for Kofax Capture can be
installed on any Windows version which
supports the Kofax Capture version being used.
Note
Export connectors are called release
scripts in earlier versions of Kofax
Capture.
Vista Plus Output Manager
5.4.x.
Kofax Capture
8 and 9
The Vista Plus Output Manager and Kofax Capture versions apply only to the Kofax
Capture export connector portion of TransVue Tagging. They are not required for
vp_load_index and rcapture.
Note
TransVue Tagging is an optional, and separately licensed, new feature of Vista

Plus 5.5.2. See Indexing for TransVue Files on page 9.

Page 6
Client Compatibility
Web View
Web Server Host
Notes
Windows
XP
SP3
Server 2003,
Standard or
Enterprise
SP2
Server 2008 R2, Tomcat only; tested with Tomcat 6 and JDK 1.6.0_26;
Standard or
integration with IIS is not supported.
Enterprise
HP-UX
Supported versions of these operating systems are the same as for the
Vista Plus server software, as listed on page 3.
IBM AIX
Sun Solaris
Web Server/Servlet
Engine
Version
Notes
Microsoft IIS
5.0, 6.0
Needs Cumulative Patch for Internet Information Service

(Q327696). IIS cannot present Java Server Pages (JSPs); to
use Web View with IIS, you must also install a servlet
engine such as Tomcat.
Apache Tomcat
5.5.x
x should be 9 or higher; testing was done on 5.5.27 using

JDK 1.5.0_16-b021
On Windows 2008 R2; testing was done with 6.0.33 using

JDK 1.6.0_261
BEA WebLogic Server
8.1, 10.0
Service Pack 3 for version 8.1
IBM WebSphere
5.1.1, 6.1
Tested on 6.1.0.7
1.Important! If you obtain your copy of Tomcat anywhere other than the www.apache.org Web
site, you may need to make some changes to the installation before you can use Web View.
Please see Customizing Web View for detailed instructions.
Note
Using Web View with the Oracle 10gAS Web server has not been fully tested
by OpenText, but is supported. If you attempt to use this configuration, you
may receive an Internal Server Error 500 (a Java NoClassDefFoundError
message) when starting Web View. If this happens, copy the file commonslogging.jar from the Oracle installation to the j2ee\home\applib directory, then
stop and restart Oracle 10gAS.

Page 7
Workstation
Web Browser
Version
Notes
Internet Explorer
7.0
Tested with 7.0.5730.13
8.0
Tested with 8.0.7600.16385
3.5.x or 3.6.x
Tested with 3.5.16
5.0
Tested with 5.0.1
Firefox
All browsers are supported on Windows only and must have JavaScript enabled. For all
features to work, cookies should also be enabled. For best performance with Internet
Explorer, we recommend you set the browser to check for new page content
Automatically, especially if you are using a low-bandwidth connection.
To download and view files in PDF format, you must have Adobe Acrobat or Reader 9.x.
Note
Pop-up blocker software, including the integrated pop-up blockers in Internet

Explorer and Firefox, can interfere with Web Views ability to open report
generations and display certain other windows. For more information, please
see Web Browser Requirements and Settings in the Web View online help.
Server Administration
Windows Version
Notes
Windows 2008
Both 32- and 64-bit versions
Windows 7 Professional
32- and 64-bit
Windows Vista Business
Service Pack 2, 32- and 64-bit
2003 Server Standard
2003 Server Enterprise
XP Professional
The Server Administration client requires a version of Microsoft Management Console

(MMC) that is supported on your Windows version.
Windows Client
Windows Version
Notes
Windows 2008
Both 32- and 64-bit versions
Windows 7 Professional
32- and 64-bit
Windows Vista Business
Windows Vista Enterprise
2003 Server Standard
XP Professional
Service Pack 3, or Service Pack 2 with KB935448, 32- and 64-bit

Page 8
Enhancements in Version 5.5.2

In addition to the problem fixes and minor enhancements in the next section, Vista Plus
5.5.2 includes these new features and improvements.
User Authentication Using LDAP Passwords

LDAP Authentication is an external module which you can use for password
authentication for some or all Vista Plus users. It functions as a user supplied
authentication module which verifies users signing in to any Vista Plus client against the
user names and passwords in one or more LDAP databases.
The LDAP Authentication module works only with Vista Plus servers on UNIX hosts. If
you have a Vista Plus Windows server host and want to authenticate users against an
Active Directory LDAP database, you can do so by selecting Windows authentication
when creating the users in Vista Plus.
Installing LDAP Authentication is described in the Vista Plus Server Installation Guide.
Configuring and using it is covered in the Vista Plus Server Administration Guide.
Indexing for TransVue Files

The optional TransVue Tagging feature allows you to create indexes for TransVue report
generations. You can add any number of values to each index for any generation; the
values do not need to appear in the TransVue file. This allows you to associate metadata
values with scanned images, Microsoft Word documents, or other types of TransVue files.
TransVue Tagging index values are always stored in the Vista Plus database, whether
other index values are or not. You can search them using Web Views global index search
or Find in Report feature (the Content tab of the Find pane). When you find and open a
TransVue generation through an index search, it always opens to the first page. The
tagging index values are not associated with any particular page of the file.
Note
To search TransVue Tagging values, the server.cfg property

IndexSearchMethod must be set to either auto or db. Make sure this setting
is compatible with the StoreIndexValuesInDB setting, which controls how
other index values are stored. See Appendix B of the Vista Plus Server
Administration Guide.
You can add index values either when capturing the TransVue file using rcapture or after
capture by using the new vp_load_index command. There is also a Kofax Capture export
connector (export connectors were called release scripts in earlier versions of Kofax
Capture) for Vista Plus Output Manager to automate scanning and capture of image files
and their associated index values to Vista Plus through Vista Plus Output Manager.
TransVue Tagging is an optional module. It is sold and licensed separately from the Vista
Plus server. Contact your OpenText representative if you are interested in using it.
Installing TransVue Tagging is described in the Vista Plus Server Installation Guide.
Configuring and using it is covered in the Vista Plus Server Administration Guide.

Page 9
Support for Additional Oracle Database Versions

The Vista Plus Server is now supported with the Oracle 11g and 11gR2 database.
Ability to Remove Index Entries from the Database

Vista Plus 5.5.0 added the ability to store index entries in the Vista Plus database as well as
in the report warehouse. This speeds up certain types of searches and makes it possible to
search offline report generations. However, it also increases the size of the Vista Plus
database. The new revert_gens command removes index entries from the database for
some or all generations and sets the database flag for those generations indicating that
index entries are in the report warehouse.
Tip
Use revert_gens only after consulting with Vista Plus technical support. To
maintain proper index and search performance, including page security, you
must make sure server.cfg parameters relating to index storage and searching
are set correctly. See the Vista Plus Technical Addendum for more information.

Page 10
Software Fixes and Changes

The following sections list the software problems fixed and issues addressed since the
release of Vista Plus 5.5.0. There are separate tables listing the changes in version 5.5.2 and
those in version 5.5.1.
Fixes and Changes in Version 5.5.2

JIRA
Description
884
The Help button did not work in any of the PC Capture tools.
917
Adds the revert_gens command. See Ability to Remove Index Entries from the
Database on page 10. Also tracked by issue 1543.
993
Changes the wording of certain server.debug.log errors generated during searches to be

more informative.
1049
The convert_gens command caused a core dump if generation files were missing from
the Vista Plus report warehouse. It now notes the error in server.debug.log and continues.
1066
Updates the ODBC drivers used with Vista Plus and an Oracle database.
1134
Corrects the version number displayed in the Server Admin Client.
1184
Changes the match pane for Web View searches to remove previous results when a search
is started and to show more accurate messages while a search is in progress.
1190
Adds support for the Oracle 11g database.
1289
Adds LDAP Authentication module. See User Authentication Using LDAP Passwords
on page 9.
1303
Output from the rcapture command was limited to 4000 characters.
1323
Changes the vadmin ModifyWarehouseConfig command vadminSecurity parameter to

accept y/n as values, as documented.
1328
Adds support for newer C++ Runtime packages on UNIX hosts. See Vista Plus Server
on page 3 for tested versions.
1336
With certain combinations of user and group permissions on reports, Web View could not
always properly filter out the reports the user did not have permission for. This did not
allow any user to see prohibited reports, but did cause Web View to display blank pages
in the Browse view report list, making it difficult for users to find the reports they were
allowed to open.
1337
Enhances server.debug.log messages when re-indexing encounters a problem with a page

security.
1341
Downloading a generation as a text file from Web View removed blank lines from the file,
even if Include blank lines was selected.
1345
Attempting to use the Windows Client to open some TIFF images captured as TransVue
generations failed with the message Unable to successfully download file.
1347
When using short-lived connections, the Vista Plus server was not properly closing user
sessions for clients other than the Server Admin client. This resulted in various processes,
such as VMIdentify, failing with messages indicating there were no processes available.

Page 11
JIRA
Description
1356
Allows Web View to display the correct original file name when opening TransVue
generations. This was done by changing the Content-Disposition type in the HTTP
header. Files are now opened in a new window, not within the browser window.
1366
Closing the Windows Client caused an application error message on Windows XP SP3.
1386
Improves VMIdentify performance.
1388
See issue 1356.
1393
The patch installer would fail if the Vista Plus service had been stopped manually before
running the installer.
1403
After opening a generation from a SmartAlarm e-mail message, closing the report viewer
window did not close the user session. This could cause Vista Plus to run out of user
licenses and prevent other users from logging in. The fix adds a Logout button to the
report viewer window.
1406
Fixes two problems in Web View: In some cases, users were disconnected from Web View
if several users were performing large searches at the same time, and opening several
TransVue generations at once could cause a too many reports opened error
message.
1416
Changes Web View so users with View or Distribute permission for a report can save
their own download columns. However, see Known Issues on page 18.
1417
Corrects errors that sometimes occurred during the del_gens command.
1419
Corrects a memory leak that could occur under certain conditions during report capture
and could eventually cause a core dump.
1421
Improves Web View performance when opening reports.
1423
Adds Microsoft Office 2007 file extensions to the default TransVue file extension list in
special.cfg.
1429
When setting generation list options in Web View, the option to list generations for the
Last xxx days did not list the correct generations.
1436
After upgrading to 5.5.1, attempting to open the latest generation of a report by doubleclicking the report in Web View failed with an Access denied error even though the
user had pages to view in the report. Opening the generation from the generation list
worked correctly.
1441
In some cases, users were not able to create or update indexes in Web View.
1472
Corrects problems viewing generations with page security after upgrading to 5.5.1.
1483
In the Server Admin client on newer versions of Windows, users were unable to view
page security conditions if the page security was selected via the user or group.
1484
Corrects the version number display in the Server Admin client About box.
1486
File handles used by Vista Plus worker threads were not always being recovered when
the worker process terminated.
1494
Users were unable to log in to Web View if they belonged to more than five groups. This
occurred only if users were required to select a group when logging in and the server.cfg
ALLGROUPS parameter was set to 1.
1543
See issue 917.

Page 12
JIRA
Description
1560
Updates the Data Direct driver managers used with the Vista Plus server.
1561
Improves Web View security.
1570
Adds support for Oracle 11gR2 database.
1586
Capturing TransVue files failed if there were bounding box capture rules in the capture
configuration file.
1609
Adds support for C++ Runtime 11.1 on IBM AIX 6.1.
1610
Adds support for latest C++ Runtime on HP-UX 11iv3.
1611
Adds support for latest C++ Runtime on Sun Solaris 10.
1612
Adds the optional TransVue Tagging module. See TransVue Tagging on page 6.
1624
Attempting to capture certain Postscript reports with rcapture failed.
1625
An error when unloading certain tables using the unload_all command could later cause
problems when attempting to read index values.
1633
The Vista Plus server produced core files and, eventually, exhausted all user licenses,
requiring the Vista Plus server to be restarted. This was seen only on a Windows server
host using MySQL.
1635
Vista Plus occasionally lost its connection to the database. It had to be restarted to reestablish the connection. This was seen only on a Windows server host using MySQL.
1656
If you switched the value of the server.cfg flag StoreIndexValuesInDB from 1 to 0, then
re-indexed one or more generations, and the IndexSearchMethod was set to auto in
server.cfg, a global index or generation search would not find any values in those
generations. See Correcting Possible Index Search Problems on page 37 for more
information.
Fixes and Changes in Version 5.5.1

SAR
Description
4930
Places all page securities in a single .p file in the generation directory instead of using
individual .p### files for each one. Also adds a .pidx file, which is an index to the .p file.
This change can greatly reduce the number of files in the report warehouse. The new file
structure is used only for page securities created (or re-created through re-indexing) with
5.5.1 or later. Page securities created in 5.5.0 or earlier remain in .p### files.
5337
Adds support for the Vista Plus Capture Printer Port on Windows 2003,.
5514
Adds the option to limit the number of generations searched for global index searches
and report or generation information searches (the Global Index and Name tabs of the
Web View Find pane).
5881
In version 5.5.0, for Windows Vista compatibility the Windows Client was changed to use
a CHM-format help file instead of a HLP file. This makes the same change for the PC
Capture client.
5882
The new CHM-format help file for the Windows Client was not being installed to the
proper location and had to be manually copied from the installation CD.

Page 13
SAR
Description
5908
Adds support for using migration to move generations from one online volume to
another online volume. The generations are not compressed when this is done.
6120
Trying to capture certain PostScript files using the capture printer port failed and caused
a core dump.
6305
Adds the ability to turn on or off logging of user-group membership changes through the
Server Admin client.
6331
Certain combinations of searches using the Find in Report feature (selecting Find from
the menu bar, then the Content tab), caused Web View to stop working. At times, Web
View crashed with errors in server.debug.log; at other times, it went into an infinite loop.
6350
Adds the ability to search for report generations by generation description or generation
file name, and to limit the number of matching generations listed.
6351
In Web View generation list, the Select All icon appeared inactive after switching from an
offline to online generation list, even though it was active and available.
6363
Under certain conditions, global index search results were inconsistentthe same search
would sometimes find results and sometimes not. This was the result of an error in
accessing shared memory, which was reported in server.debug.log.
6408
Adds the ability to search offline generations when searching for generations by report or
generation info (selecting Find from the menu bar, then the Name tab).
6412
In some cases, it was possible to create an illegal combination of search parameters (some
using an index name, others not) through the Content tab of the Find pane. These
searches found matches in some cases and not in others, but always caused errors in the
server.debug.log file. Weve changed the user interface behavior to prevent this from
happening.
Even after this fix, it is possible to type an illegal search stringmixing text and index
criteriadirectly into the search expression box. This is not supported, will cause an error
in server.debug.log, and may or may not find matches.
6421
If a user cancels a convert_gens operation by typing x, convert_gens now displays a

message saying how many generations had been converted before the cancellation.
6427
In some cases, convert_gens required you to press Enter after p (pause), r (resume), or x
(cancel). With 5.5.2, you do not need to press Enter after typing one of these options.
6446
The Server Admin Client is now supported on Windows Vista.
6468
You can now use the convert_gens command to add index values to the Vista Plus
database even if the server.cfg file contains the statement StoreIndexValuesInDB=0.
6472
The generation list created in the GensToConvert.txt file by the convert_gens -l command
now includes the report name, file name, and generation description for each generation.
6480
On UNIX, after upgrading a 5.4 Vista Plus server owned by root to 5.5 and changing the
owner to a non-root user, the vadmin c=v l=y command incorrectly showed that many
components had not been upgraded. This was because the upgrade was not properly
setting the ownership and permissions for the .version.long file.
6487
On IBM AIX only, upgrading a Vista Plus server owned by a user other than root failed
because it could not load required third-party libraries.

Page 14
SAR
Description
6491
When viewing a TransVue file in the Windows Client, the original file name is now
included as part of the downloaded file name. This makes it possible to see the original
file name in the title bar.
6495
The convert_gens command caused a core dump if it could not find the files for a
generation listed for conversion. It now skips the missing generation and writes an error
to server.debug.log.
6526
When viewing a TransVue file in Web View, the original file name is now included as part
of the downloaded file name. This makes it possible to see the original file name in the
title bar.
6540
After a Web View session expired, performing certain actions on an open reportsuch as
downloadingresulted in HTTP 500 errors. These actions are still not possible after the
session times out, but Web View now displays a more informative session time-out
message.
6564
Running check_gens -p generated an error for each TransVue report generation it found.
6578
Adds three new options to report logging to log password changes and adding users to
or removing them from groups.
6605
When running Vista Plus under a non-root user name on UNIX, adding page securities
using the Server Admin client sometimes caused the client to hang. The problem was
sometimes also seen when attempting to capture a report which had page securities.
6631
Users were sometimes unable to open a generation which had been archived, then
restored.
6654
Adds the ability to run Web View on a Web server using some versions of Oracle 10gAS.
6719
Certain graphics in captured PostScript reports were not displaying properly.
6722
Users with the option set to force a password change at their next login set could not log
in using Web View.
6725
When performing a whole-text generation search with the Show Match List option
selected, not all matches were being found.
6781
You can now change a user name by using the newname parameter with the vadmin
ModifyUser command.
6814
The IndexSearchReportGens() API did not work with Vista Plus 5.5.0.
6827
Using vadmin ModifyWarehouseConfig to change the high watermark setting for online
volumes reset the client connection type to persistent instead of short-lived.
6877
Received APIStatus(451) error when trying to create an index using the Windows
Client with short-lived connections and a short time-out setting (one or two seconds).
6886
Upgrading from Vista Plus 5.3 to Vista Plus 5.5.0 caused some bounding box capture
rules to stop working.
6887
On an HP-UX server, the unload_all utility failed to unload the vp_report table.
6913
When running the Vista Plus server as a non-root user on UNIX, remote printing, or
SmartAlarms which included print actions, could cause an error code 16 in
server.debug.log, even though the print was successful.
6940
On IBM AIX, some customers were unable to open some report generations because Vista
Plus was unable to extract the generation files from the compressed tar file.

Page 15
SAR
Description
6995
Using autocapture to capture multiple reports failed with database-related errors when
using an Oracle database and dedicated ODBC connections.
7042
rcapture failed with a String too long (truncated) message after changing locale
setting.
7072
After opening a generation from a bundle instance, users could not open any other
generations without logging out of and back into Vista Plus. Page security information
from the bundled generation was incorrectly being applied to any other generation the
user tried to open.
7076
Page breaks in text reports were not being interpreted properly when captured using the
text-only parser. One symptom of this was that the last page of a captured report could
not be printed.
7085
After upgrading the Oracle database to 10.2.0.3, the connection between Vista Plus and
Oracle was being dropped frequently. This resulted in users being unable to log in.
7096
On IBM AIX servers, remote print requests caused error messages in server.debug.log and
in the client (Web View or Windows Client), even though the print job completed
successfully.
7102
Adds path information to a verbose server.debug.log message if a generation file cannot be

opened.
7111
Deleting generations created unneeded PAGE_ACCESS tables in the Vista Plus database.
7141
Adds an option to draw pattern objects before other objects when displaying in normal
mode in Web View. This improves the display accuracy of some reports.
7155
Adds the %T parameter to be used to include the generation description in remote print
commands
7156
Upgrading from Vista Plus 5.1.2 to Vista Plus 5.4 or 5.5 caused some bounding box
capture rules to stop working
7171
Default on-demand migration rule set was not being properly cleared from warehouse
configuration after VMIdentify was run.
7180
Vista Plus could not connect to an Oracle 10g database after installation on an HP-UX 11i
server.
7204
Fixes small problems remote printing entire reports in certain situations.
7213
In certain situations, running VMIdentify caused a core file.
7267
rcapture sometimes indicated a capture was successful (there was no error code) even
though it failed.
7271
Updates Vista Plus to use a newer Data Direct ODBC driver which supports Oracle 10gR2
(10.2.03 and 10.2.04).
7280
Adds support for using Web View in Internet Explorer 7.0.
7307
Adds the generation ID to the message displayed after a successful rcapture command.
7383
Adds a web.xml setting to include empty reports by default in Web View report lists.
7384
In Web View, users with Distribute permission for a report were being allowed to modify
their column settings and save the new settings. Only users with Modify or Delete
permissions for a report are supposed to be able to save column settings.

Page 16
SAR
Description
7388
Improves support for the Windows Admin Client on Windows Vista.
7420
Improves performance when capturing generations of reports with a very large number
of generations (30,000 or more).
7451
Improves the performance of the load_index utility when doing bulk migration of
indexes and there are blank lines in the source data.
7452
When using auto-recognition of file types, the PC Capture tools were looking for the
special.cfg file in the wrong location, and therefore were not recognizing file extensions
that should be captured as TransVue files.
7507
Remote printing was failing in some instances when used with certain security
configurations on a UNIX server.
7521
Certain graphics in captured PostScript reports were not displaying properly.
7546
VMIdentify was creating a core file when run on IBM AIX 5.3.
7587
Improves generation search performance when the report has a large number of
generations. This fix adds two new parameters to the server.cfg file, DelayGenFilter and
MatchIndexValueFirst.
7596
When performing a text search in Web View, the Show Match List option did not always
show a list of matches.

Page 17
Known Issues
Known Issues
The issues described below are in addition to the known issues listed in the Vista Plus 5.5
Release Notes.
Multiple concurrent captures: Vista Plus supports concurrent capturing of multiple

files. However, capturing more than four files at once can cause the captures to fail
with database errors. If you encounter this problem, we recommend you limit the
number of concurrent file captures. If you use Vista Plus Output Manager to send files
to Vista Plus, you can use Output Managers MaxJobSetting parameter to limit the
number of concurrent jobs.
Web View download columns: There are two issues when creating and editing
download columns in Web View:
After the change for issue 1416 (see page 12), all users should be able to save
download columns for their own use. However, while the columns created by
clicking Create Columns are saved, any edits made to the column definitions are
saved only for users with Modify or Delete permission.
If you change columns while the column editing pane is shown (by
SHIFT+clicking a different column heading), the column editing pane correctly
switches to show information for the newly selected column, but the old column
remains highlighted in the generation window. Any changes you make are
applied to the newly selected column.
Correction to the Documentation
Web View help file: The Web View help file has not been updated for the change in
issue 1416 (see page 12). It still says that only users with Modify or Delete permission
for a report can save column definitions for their own use.

Page 18
Update Instructions
Update Instructions
Vista Plus 5.5.2 is a Service Pack (SP). It does not include all server and client files. You can
install version 5.5.2 only as an upgrade to an existing Vista Plus 5.5.0 or 5.5.1 installation.
The procedures for updating the Vista Plus server host are slightly different depending on
whether you are updating from version 5.5.0 or 5.5.1. In addition, there are special
instructions if you are installing 5.5.2 as a new installation on a server host which uses
software that is not supported by Vista Plus 5.5.0. As you follow the procedures below, be
sure to perform only those steps which apply to your upgrade path and configuration.
Warning
Before upgrading, contact Vista Plus Technical Support to discuss your

upgrade plan. Do not attempt to upgrade your Vista Plus server software
without contacting technical support! If you have downloaded, installed, or
received any patches or updates to the Vista Plus software after April 12,
2011, be sure to ask technical support if your patches are included in this
release. Patches created after April 12, 2011, are not included in Vista Plus
5.5.2.
Warning
Open Text Corporation assumes no responsibility for data loss resulting from
failure to contact technical support before upgrading or from failure to follow
their upgrade instructions, including failure to perform a full backup of all
Vista Plus information before the upgrade.
Before the Upgrade: Online to Online Migration

Note
Follow this procedure only if you are upgrading from an existing Vista Plus
5.5.0 host. Skip this section if you are upgrading from version 5.5.1 to 5.5.2, or
if you installed 5.5.0 on a new host only as a step toward installing 5.5.2.
Even though it was not supported in any version before 5.5.1, some users migrated report
generations from one online volume to another online volume. This appeared to work,
but actually wrote the generation to the online volume as if it was offline. (The file
structure of an offline volume is different than an online one.)
If you have migrated generations from one online volume to another, and you are
upgrading from 5.5.0 to 5.5.2, you must restore all of these migrated generations back to
their original capture volume before you upgrade. If you do not, you will have problems
accessing those generations, and possibly other generations of the same report.
To find the affected generations, look in the root directory of any online volume you used
as a destination. Any generation migrated to that volume will have a compressed file (a
.zip file on Windows or a .tar.Z file on UNIX) in that directory. The name of the file is the
ID of the migrated generation.
When you restore the generations, you must use a permanent restore. A temporary restore
will not avert the problem. You set the restore method on the Restore page of the
warehouse parameters dialog box, as described in the Vista Plus Server Administration
Guide. After restoring the affected generations, you can return this parameter to your
preferred setting.

Page 19
Update Instructions
Update Overview
Updating to Vista Plus 5.5.2 involves a combination of the following procedures. You will
not need to perform all of these procedures; there is no upgrade path that requires them
all. Perform only the procedures which apply to your Vista Plus installation.
1.
If you are installing Vista Plus 5.5.2 on a server host with no previous version of Vista
Plus, download and install Vista Plus 5.5.0. If the server host uses software which is
not supported with Vista Plus 5.5.0, this requires an updated installation program, as
described below, and, if you are using an Oracle database, updated ODBC drivers.
2.
Download the Vista Plus 5.5.2 files from the Knowledge Center.
3.
Install the updated Vista Plus 5.5.2 server files.
4.
If Vista Plus uses an Oracle database, install the updated ODBC drivers.
5.
If you are updating from Vista Plus 5.5.0, run a script to update the Vista Plus
database schema.
6.
If desired, run one or more of the optional post-installation procedures. These

procedures can improve Vista Plus performance and avoid errors in some situations.
7.
Upgrade any Vista Plus remote hosts.
8.
Upgrade the Vista Plus clients: the Server Admin Client, Web View, and the Windows
Client.
The following sections describe each of these procedures in detail. Again, be sure to
perform only those procedure which apply to your Vista Plus installation.
Note
Important! Vista Plus 5.5.2 is supported with operating system and database
versions that are not supported with Vista Plus 5.5.0 or 5.5.1: the IBM AIX 6.1
and HP-UX 11iv3 operating systems and the Oracle 11g and 11gR2 databases.
If you want to upgrade your operating system or database to one of these
versions, we strongly recommend you upgrade Vista Plus to 5.5.2 first
following the procedures in this document, then perform the operating
system or database upgrade.
Installing Version 5.5.0 on a New Vista Plus Host

Vista Plus 5.5.2 is a Service Pack (SP) release. It can only be installed on a host which
already has Vista Plus 5.5.0 or 5.5.1 installed and working. Therefore, to install version
5.5.2 on a new server host, you must first install Vista Plus 5.5.0, then update to 5.5.2.
In most cases, you simply follow the installation instructions for version 5.5.0 in the latest
version of the Vista Plus Server Installation Guide, then update to version 5.5.2 following the
instructions for upgrading from version 5.5.0. However, Vista Plus 5.5.2 is supported with

Page 20
Update Instructions
some operating system and database versions that are not supported with Vista Plus 5.5.0.
If you want to install 5.5.2 in either of these conditions:
On a server host running the IBM AIX 6.1 or HP-UX 11iv3 operating system
On any UNIX server host and using an Oracle 11g or 11gR2 database, either on the
server host or a separate database host
Then you must follow the instructions below to install version 5.5.0 before upgrading to
5.5.2.
Note
If you want to use an Oracle 11g or 11gR2 database with a Vista Plus
Windows server host, there are no special procedures to follow. Install Vista
Plus 5.5.0 following the procedures in the Vista Plus Server Installation Guide,
then perform all the procedures to update to version 5.5.2 from version 5.5.0.
Installing Vista Plus 5.5.0 with IBM AIX 6.1, HP-UX 11iv3, or Oracle 11g
To install Vista Plus 5.5.2 on a host which does not already have Vista Plus installed, you
must first install version 5.5.0, then update it to 5.5.2. The original installation script for
Vista Plus 5.5.0 will not work on a computer running IBM AIX 6.1 or HP-UX 11iv3, or on
any UNIX host using an Oracle 11g or 11gR2 database, because these software versions are
not supported with version 5.5.0. There is an updated installation script for version 5.5.0
which enables you to install it with these software versions. Follow these steps to install
Vista Plus 5.5.0 in these conditions:
1.
Download the Vista Plus 5.5.0 release files for your operating system from the
OpenText Knowledge Center. Create the Vista Plus installation directory and unpack
the installation files into it, as described in the Installation Guide, but do not perform
the installation yet.
2.
From the Knowledge Center 5.5.2 Server/UNIX/Install folder, download the files
install and setup_IPD (they dont have an extension). Copy them to the Vista Plus 5.5.0
release directory, replacing the existing installation script.
3.
If you will be using an Oracle database (11g or another supported version) with Vista
Plus, download the updated ODBC driver file for your operating system from the
5.5.2 Third Party Software/ODBC Drivers/Unix folder of the Knowledge Center. Copy it
to the ThirdPartySoftware/DataDirect/unix directory of the Vista Plus 5.5.0 release
directory.
4.
Install version 5.5.0 as described in the Vista Plus Server Installation Guide.
5.
Check the ddc_odbc/odbc.ini file to make sure it has all the necessary entries. The
statements to check for are described in step 6 on page 26. Make any needed changes
and save the file. Be sure to make the proper changes for your host operating system.
While this procedure allows you to install Vista Plus 5.5.0, using it in these conditions is
not supported. You should immediately follow the procedures in the rest of this document
to upgrade to Vista Plus 5.5.2. Perform only those procedures which apply to a new
installation of 5.5.2.

Page 21
Update Instructions
Downloading the 5.5.2 Files

Download the installation files for the 5.5.2 SP from the Vista Plus section of the OpenText
Knowledge Center. You must do this in all upgrade situations. To download the files:
1.
Log in to the OpenText Knowledge Center: https://knowledge.opentext.com.
2.
Go to the Vista Plus product section and navigate to the 5.5.2 Service Pack.
3.
Download the files needed for your environment, as shown in the section below for
your host operating system.
UNIX Host
Database
Files
Either
Server >UNIX > vista-patch552-nnn-yyyymmdd-OS.tar.Z

Server > UNIX > Install > patchinstall.ksh
Clients > WebView > vp_web.war
Clients > WinAdmin > setup.exe
Clients > WinClient > setup.exe
Note
Download this to a different location than the Server Admin setup.exe file.
Documentation > *.pdf
Oracle
Server > SQL_Scripts > Oracle_Upgrade_5.5.20.sql

Server > SQL_Scripts > Oracle_Upgrade_5.5.10.sql1
Third Party Software > ODBC Drivers > Unix > ddc_odbc-6.x-OS.tar.Z2
MySQL

Server > UNIX > post_install_script > check_db.ksh
1.Download only if you are upgrading directly from Vista Plus 5.5.0.
2.If you just installed Vista Plus 5.5.0 as part of a new Vista Plus 5.5.2 installation with IBM AIX
6.1, HP-UX 11iV3, or Oracle 11g, as described in Installing Vista Plus 5.5.0 with IBM AIX 6.1,
HP-UX 11iv3, or Oracle 11g on page 21, you installed the updated drivers as part of that process, and do not need to download them again.
After downloading the files, copy the patch installation utility and any SQL script file or
files to the Vista Plus home directory.
Copy the Web View file to a temporary location on the Web server.

Page 22
Update Instructions
Windows Host
Database
Either
Files
Server >Windows > vista-patch552n-yyyymmdd-NT.zip
Server > Windows > Install > patchinstall.exe
Clients > WebView > vp_web.war
Clients > WinAdmin > setup.exe
Clients > WinClient > setup.exe
Note
Download this to a different location than the Server Admin setup.exe file.
Documentation > *.pdf
Oracle
Server > SQL_Scripts > Oracle_Upgrade_5.5.20.sql

Third Party Software > ODBC Drivers > Windows > *.zip
MySQL

Server > Windows > post_install_script > check_db.ksh
1.Download only if you are upgrading directly from Vista Plus 5.5.0.
After downloading the files, copy the patch installation utility and any SQL script file or
files to the Vista Plus bin directory.
Copy the Web View file to a temporary location on the Web server.
Updating the Vista Plus Server Files

To install the 5.5.2 SP after downloading the files from the Knowledge Center, follow the
directions below for your operating system. There are separate procedures for installing
the service pack on UNIX and Windows. You must perform the procedure for your
operating system in all upgrade situations.
To Install the Service Pack on a UNIX Server Host

Warning
Installing the SP stops the Vista Plus server. This disconnects all Vista Plus
clients and stops any capture or migration processes that are running. Before
running the SP installation, make sure VMTransport is not running. If it is, do
not stop it; let it complete before installing the SP.
1.
Log on to the server host as root. Vista Plus does not support pseudo-root users
created by the sudo, su, or pseudo UNIX commands. You must log on as root even if
Vista Plus is being run as a non-root user.
2.
Change to the Vista Plus home directory.
3.
Make sure the installation script is executable by entering this command:

chmod +x patchinstall.ksh

Page 23
Update Instructions
4.
If the Vista Plus home directory does not have a patches subdirectory, run the patch
installation utility, with no options, to create it:
./patchinstall.ksh
5.
Copy the tar.Z file for the SP to the Vista Plus patches subdirectory.
6.
Run the patch installation utility:

./patchinstall.ksh
7.
The utility asks if you want to install an SP or a specific patch. Type P for SP and press
Enter.
8.
It then asks if you are sure you want to shut down the Vista Plus server and proceed
with the installation. To continue, type y and press Enter.
9.
This displays a list of all the patch files found in the patches subdirectory. Type the
number for the SP file and press Enter.
You now see various messages as the patch installation utility backs up the files it will
be replacing, then installs the new files.
10. When the SP installation finishes, a prompt asks if you want to install any specific
patches. Type n and press Enter.
You are now asked if you want to restart the Vista Plus server:
If Vista Plus uses an Oracle database and you are updating from a previous
5.5.0 or 5.5.1 installation, type n and press Enter.
If Vista Plus uses a MySQL database, or you are updating a fresh installation of
Vista Plus 5.5.0 on an HP-UX 11iv3 or AIX 6.1 server host, as described in
Installing Version 5.5.0 on a New Vista Plus Host on page 20, type y and press
Enter.
There is a log of the service pack installation in the patches/logs directory.
To Install the Service Pack on a Windows Server Host

Warning
Installing the SP stops the Vista Plus server. This disconnects all Vista Plus
clients and stops any capture or migration processes that are running. Before
running the SP installation, make sure VMTransport is not running. If it is, do
not stop it; let it complete before installing the SP.
1.
Log on to the server host as an Administrative user. You must be able to move and
copy files in the Vista Plus folder tree and stop and start the Vista Plus server.
2.
Open a DOS command window and change to the Vista Plus bin directory.
3.
If the Vista Plus home directory does not have a patches subdirectory, run the patch
installation utility, with no options, to create it:
patchinstall.exe
4.
Copy the zip file for the SP to the Vista Plus patches subdirectory.

Page 24
Update Instructions
5.
Run the patch installation utility:

patchinstall.exe
6.
The utility asks if you want to install an SP or a specific patch. Type P for SP and press
Enter.
7.
It then asks if you are sure you want to shut down the Vista Plus server and proceed
with the installation. To continue, type y and press Enter.
8.
This displays a list of all the patch files found in the patches subdirectory. Type the
number for the SP file and press Enter.
You now see various messages as the patch installation utility backs up the files it will
be replacing, then installs the new files.
9.
When the SP installation finishes, a prompt asks if you want to install any specific
patches. Type n and press Enter.
10. You are now asked if you want to restart the Vista Plus server:
If Vista Plus uses an Oracle database, type n and press Enter. Continue by
updating the ODBC drivers.
If Vista Plus uses a MySQL database, type y and press Enter. After making sure
that the Vista Plus server is up and running properly, continue by updating the
database schema.
There is a log of the service pack installation in the patches/logs directory.
Updating the ODBC Drivers for Oracle

Note
Follow this procedure only if you are upgrading from an existing Vista Plus
host using an Oracle database. Skip this section if Vista Plus uses MySQL, or if
you just installed Vista Plus 5.5.0 as part of a new Vista Plus 5.5.2 installation
with IBM AIX 6.1, HP-UX 11iV3, or Oracle 11g, as described page 21.
If your Vista Plus server uses an Oracle database, you need to update the ODBC drivers
Vista Plus uses to communicate with the database. Follow the procedure below for your
operating system.
Updating the ODBC Drivers on a UNIX Host

Tip
These instructions assume you are performing this procedure immediately

after installing the service pack. You must be logged into the Vista Plus home
directory as root and the Vista Plus server must be stopped.
1.
Rename the ddc_odbc subdirectory to ddc_odbc.bk.
2.
Recreate the ddc_odbc subdirectory.
3.
Copy the ODBC tar file you downloaded from the Knowledge Center into the new
ddc_odbc directory.

Page 25
Update Instructions
4.
Change directory to ddc_odbc, then uncompress and untar the ODBC tar file:
cd ddc_odbc
uncompress ddc_odbc-6.x-UnixOS.tar.Z
tar xvf ddc_odbc-6.x-UnixOS.tar
UnixOS varies depending on your operating system. x may be different for different
operating systems.
5.
Copy the odbc.ini file from ddc_odbc.bk to ddc_odbc.
6.
Using vi or another editor, open odbc.ini. The changes you need to make depend on
the operating system you are upgrading on. For Solaris and HP-UX, make these
change to the data source section:
In the Driver statement, change the file name at the end from VPora21.so or
VPora23 to VPora.so. For example:
Driver=/VistaPlus/ddc_odbc/lib/VPora.so
Tip
If your operating system is HP-UX RISC, the file extension is .sl, not .so.
Change the OracleWireProtocol statement to read:
OracleWireProtocol=DataDirect 6.0 Oracle Wire Protocol
In the Description statement, change the version number to 6.0. For

example:
If they are not already there, add these statements to the end of the section (if
you are upgrading from 5.5.1, they should already be present):
Description=DataDirect 6.0 Oracle Wire Protocol
AuthenticationMethod=1
ConnectionRetryCount=0
ConnectionRetryDelay=3
EncryptionMethod=0
GSSClient=native
HostNameInCertificate=
KeyPassword=
KeyStore=
KeyStorePassword
LoadBalancing=0
LocalTimeZoneOffset=xx:xx
LockTimeOut=-1
ValidateServerCertificate=1
WireProtocolMode=1
In LocalTimeZoneOffset, xx:xx is the correct entry for your time zone. For
example, for Eastern Standard Time, it would be -05:00.
Add these statements after the ones in the preceding step:

BulkBinaryThreshold=32
BulkCharacterThreshold=-1
BulkLoadBatchSize=1024
ConnectionReset=0

Page 26
Update Instructions
EnableBulkLoad=0
FailoverGranularity=0
FailoverMode=0
FailoverPreconnect=0
FetchTSWTZasTimestamp=0
InitializationString=
LoadBalanceTimeout=0
LoginTimeout=15
MaxPoolSize=100
MinPoolSize=0
Pooling=0
QueryTimeout=0
For IBM-AIX, make these change to the data source section:
In the Driver statement, change the file name at the end from VPora21.so or
VPora23 to VPora25.so. For example:
Driver=/VistaPlus/ddc_odbc/lib/VPora25.so
Change the OracleWireProtocol statement to read:

OracleWireProtocol=DataDirect 6.1.1 Oracle Wire Protocol
In the Description statement, change the version number to 6.1.1. For

example:
Description=DataDirect 6.1.1 Oracle Wire Protocol
7.
Save your changes and close the file.
8.
Change to the lib subdirectory and make sure all files in that directory are executable:
cd lib
chmod +x *.*

Page 27
Update Instructions
9.
Change to the Vista Plus home directory, source the ddc_odbc.cfg file, and run the
command vpsql -v to test the new driver:
cd ../..
. ./ddc_odbc.cfg
./vpsql -v
On Sun Solaris and HP-UX, the information returned should look like this:
VPSQL version 5.5.0.129
This software product and documentation is licensed subject to the
terms of the license agreement shipped with the product.
WARNING: This utility is for Open Text Corporation installation
use only
Current ODBC connection info is as follows:
ODBC Connection: DBMS is Oracle
ODBC Connection: DBMS version is 10.02.0000 Oracle 10.2.0.3.0
ODBC Connection: DSN is MyVista
ODBC Connection: ODBC Driver name is VPora24.so
ODBC Connection: ODBC Driver ver is 06.00.0196 (B0141, U0059)
ODBC Connection: ODBC version is 03.52
On IBM-AIX, the information returned should look like this:

terms of the
license agreement shipped with the product.
use only
The highlighted sections should match exactly if the driver update was successful.
Other values, including the last four digits of the ODBC driver version, will vary at
different installations.
10. If vpsql -v was successful, the upgrade is complete. You can now use vista_service to
restart the Vista Plus server.

Page 28
Update Instructions
After making sure that the Vista Plus server is up and running properly, if you are
updating from version 5.5.0, continue by updating the database schema. If you are
updating from version 5.5.1, continue with the post-installation procedures.
To Update the ODBC Drivers on a Windows Host

You need to perform this procedure only if your Vista Plus server uses an Oracle database.
If it uses a MySQL database, skip this section.
Tip
These instructions assume you are performing this procedure immediately

after installing the service pack. The Vista Plus server must be stopped.
1.
In the DataDirect subfolder of the Vista Plus server home folder, create the folder
ODBC60.
2.
Unzip the Drivers.zip and DriverReg.zip files to the new ODBC60 folder. Drivers.zip will
create a Drivers subfolder and place its files there. Make sure you know the complete
path to this folder. By default, it would be c:\Program Files\Open Text\Vista Plus\Vista
Plus Server\DataDirect\ODBC60\Drivers.
3.
Make sure you know the name of the data source used by Vista Plus. You can find it
in the db.cfg file in the Vista Plus home folder.
4.
Unzipping DriverReg.zip creates four registry files in the ODBC60 folder. You may
need to make changes to three of these files. Check the highlighted text in each file
and correct it as needed:
In DataSources.reg, make sure the data source name is correct:
[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources]
"MyOracle"="DataDirect 6.0 Oracle Wire Protocol"
In DDC60.reg, make sure the paths to the Drivers directory are correct:
[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\DataDirect 6.0
Oracle Wire Protocol]
"ConnectFunctions"="YYY"
"APILevel"="1"
"CPTimeout"="60"
"Driver"="E:\\Program Files\\Open Text\\Vista Plus\\Vista Plus
Server\\DataDirect\\ODBC60\\Drivers\\vpora24.dll"
"DriverODBCVer"="3.52"
"FileUsage"="0"
"Setup"="E:\\Program Files\\Open Text\\Vista Plus\\Vista Plus
"SQLLevel"="1"
"UsageCount"="1"
In MyOracle.reg, check the path to the Drivers directory:

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\MyOracle]
"Driver"="E:\\Program Files\\Open Text\\Vista Plus\\Vista Plus

Page 29
Update Instructions
"Description"="Data Direct Oracle Wire Protocol 6.0 ODBC Driver"
The Drivers.reg file does not need any changes.

5.
Execute each registration filefor example, by double-clicking it in Windows

Explorer. You can execute the files in any order, but be sure to execute all four.
6.
Check the connection through Data Sources control.
7.
Make sure the time zone setting for the data source is set. This value must be present
or Vista Plus will be unable to connect to the database at certain times of the day. To
check the time zone setting:
8.
Open the Windows Control Panel and select Administrative Tools, Data
Sources (ODBC).
On the ODBC Data Source Administrator, select the data source and click
Configure.
On the Advanced tab page, set the time zone offset to the correct value for your
location. For example, for Eastern Standard Time, set it to -05:00.
Save your change.
Open a DOS command window and change to the Vista Plus home directory. Then,
execute the command vpsql -v to test the new driver:
bin\vpsql -v
The information returned should look like this:

terms of the license agreement shipped with the product.
use only
The highlighted sections should match exactly if the driver update was successful.
Other values will vary at different installations.
9.
If vpsql -v was successful, the upgrade is complete. Restart the Vista Plus server using
vista_service.
After making sure that the Vista Plus server is up and running properly, if you are
updating from version 5.5.0, continue by updating the database schema. If you are
updating from version 5.5.1, continue with the post-installation procedures.

Page 30
Update Instructions
To Update the Database Schema

Note
Follow this procedure if you are upgrading from Vista Plus 5.5.0, including
fresh installations of Vista Plus 5.5.0 with IBM AIX 6.1, HP-UX 11iV3, or
Oracle 11g. Skip this section if you are upgrading from version 5.5.1.
If you are upgrading from version 5.5.0, after installing the 5.5.2 software and, if you use
an Oracle database, updating the ODBC drivers, you need to run the provided SQL script
to update the Vista Plus database schema. Follow the instructions below for your
operating system and database.
You can perform this procedure while the Vista Plus server is running, as all it does is add
indexes to existing tables.
To update the schema on UNIX

Type the appropriate command for your database:
For MySQL:
/opt/mysql/bin/mysql --user=root --password=password database <
VPHome/MySQL_Upgrade_5.5.10.sql
Root and password are the MySQL root user name and password. Database is the
name of the Vista Plus database. VPHome is the path to the Vista Plus home directory.
For Oracle:
su - oracle -c "sqlplus User/Pass @VPHome/Oracle_Upgrade_5.5.10.sql"
User is the name of the Oracle user set up for Vista Plus and pass is the password for
that user. VPHome is the path to the Vista Plus home directory.
Continue with any desired post-upgrade procedures, as described below, then updating
any remote hosts, the Server Admin Client, and Web View.
To update the schema on Windows

Type the appropriate command for your database:
Note
Important! If any of the paths in either command below contain spaces,

enclose the entire path, including the file name, in quotes.
For MySQL:
MySQLHome\mysql.exe --user=root --password=password database <
VistaHome\bin\MySQL_Upgrade_5.5.10.sql
MySQLHome is the path to the MySQL home directory. Root is the MySQL root user
name and password is the password for that user. Database is the name of the Vista
Plus database. VistaHome is the path to the Vista Plus home directory.

Page 31
Update Instructions
For Oracle:
OracleHome\bin\sqlplus.exe User/Pass @VistaHome/
Oracle_Upgrade_5.5.10.sql
OracleHome is the path to the Oracle home directory. User is the name of the Oracle
user set up for Vista Plus and pass is the password for that user. VistaHome is the
path to the Vista Plus home directory.
Continue with any desired post-upgrade procedures, as described below, then updating
any remote hosts, the Server Admin Client, and Web View.
Optional Post-Upgrade Procedures

The procedures below are optional. Most of them make small changes to the Vista Plus
database. As Vista Plus has matured, we have changed some of the recommended
database configuration settings and structures. Most Vista Plus installations have made
these modifications during earlier upgrades. However, as they are not required, only
recommended for better performance, some Vista Plus servers may still be using the old
options and structures. After upgrading the server software to 5.5.2, you may want to
perform the database procedures below to make sure your database is using the optimum
settings and table structure in these areas.
The final procedure, Correcting Possible Index Search Problems on page 37, does not
make any changes to the database structure. It corrects a possible inconsistency between
where index entries for a generation are stored and where the generation record indicates
they are stored. You will need to run it only if you followed a particular sequence of steps,
as described in the section.
Note
You can perform these procedures at any time. However, because the
database-related procedures involve stopping the Vista Plus server, it is
frequently most convenient to do them immediately after upgrading the
server, before users start using the new version.
Setting the MySQL vp_rep_gens Table to Use InnoDB

Note
Important! This procedure applies only to Vista Plus installations using a

MySQL database. If Vista Plus uses an Oracle database, skip this section.
When using MySQL, most of the tables in the Vista Plus database are set to use the
InnoDB database engine, not MyISAM, which is the default database engine for MySQL.
However, in Vista Plus 5.2.1, the script used to add the vp_rep_gens table to the database
did not set the report engine type, so the table was added as a MyISAM table. While Vista
Plus will work with the MyISAM engine, InnoDB is preferred because it supports
transactions and individual row locking. This allows better performance than MyISAM.
Vista Plus 5.5.2 includes a script which checks to see if the vp_rep_gen table uses the
MyISAM engine. If so, it changes the table engine type to InnoDB. There are separate
scripts for Windows and UNIX server hosts.

Page 32
Update Instructions
To check the vp_rep_gens table on a Windows host

1.
Copy the downloaded check_db.bat file to the VistaPlus\bin directory.
2.
If it is running, stop the Vista Plus server.
3.
Open a DOS command windows and change to the VistaPlus\bin directory.
4.
Enter this command:

check_db mysql_root_pwd db_name
Mysql_root_pwd is the password for the MySQL root user and db_name is the name
of the Vista Plus database.
To check the vp_rep_gens table on a UNIX host

1.
Copy the downloaded check_db.ksh file to the VistaPlus directory.
2.
If it is running, stop the Vista Plus server.
3.
Change to the VistaPlus installation directory.
4.
Enter this command:

check_db mysql_root_pwd db_name
Mysql_root_pwd is the password for the MySQL root user and db_name is the name
of the Vista Plus database.
Setting MySQL to Use Individual Files for Each Table

Note
Important! This procedure applies only to Vista Plus installations using a

MySQL database. If Vista Plus uses an Oracle database, skip this section.
Warning
This procedure affects all InnoDB tables in the MySQL tablespace. If you have
any MySQL databases other than Vista Plus, this will change the setting for
those tables as well.
MySQL can either store data for all InnoDB tables in a database in a single file, or create
separate files for each table. Using a separate file for each InnoDB table makes it easier to
reclaim space freed when data is deleted from a table, and is the recommended method
for use with Vista Plus.
1.
If it is running, stop the Vista Plus server. Make sure the MySQL server is running.
2.
Dump all of the Vista Plus database tables using mysqldump:
On Windows, open a DOS command window. On UNIX, display the system

prompt.
Change to the MySQL directory.
Enter this command:

mysqldump -u root -p -A > dump.sql
Dump.sql is the file to hold the dumped information. It can be a full file path.
When prompted, enter the MySQL root user password.

Page 33
Update Instructions
3.
Stop the MySQL server.
4.
Back up all the files from the MySQL tablespace.
5.
Delete all files from the MySQL tablespace, including the ibdata and ib_log files.
6.
Delete any .frm files for InnoDB tables. These files are in the Vista Plus directory.
7.
Edit the my.ini file (on Windows) or the my.cnf file (on UNIX) in the MySQL
installation directory. Change the innodb_file_per_table setting to 1.
8.
Restart the MySQL server.
9.
Import the Vista Plus data from the file you dumped it to in step 2:
On Windows, open a DOS command window. On UNIX, display the system

prompt.
Change to the MySQL directory.
Enter this command:

mysql -u root -p < dump.sql
Dump.sql is the path to the file holding the dumped information.
When prompted, enter the MySQL root user password.
10. Restart the Vista Plus server.
Adding the obj_id index to the vp_permissions Table

Certain queries that Vista Plus performs on the vp_permissions table are much more
efficient (completing up to 90% faster) if there is an index on the permission ID (the
obj_id field). This index should have been created when upgrading to Vista Plus 5.4
from an earlier version, or during new installations of Vista Plus 5.4 and later. However, it
appears that in some cases the index was not created when it should have been. If you are
not certain that this index exists, we recommend you follow the procedure below to check
for it and create it if needed.
There are separate procedures for MySQL and Oracle.
Adding the obj_id Index in MySQL

You need to stop the Vista Plus server and run a SQL command against the Vista Plus
database. Follow these steps:
1.
Stop all Vista Plus services. Do not stop the MySQL service.
2.
Login to MySQL.
3.
Run this command to see if the index already exists:

show index from VP_PERMISSIONS;
If there is an index defined on the obj_id field, stop. If not, continue.

4.
Back up the database using mysqldump. See the backup and restore appendix of the
Vista Plus Server Administration Guide for details.

Page 34
Update Instructions
5.
Run this command to create the index:

ALTER TABLE `vp_permissions` ADD INDEX `VP_PERM_OBJ_ID_IDX`
(`OBJ_ID`);
6.
Verify the new index exists with this command:

show index from VP_PERMISSIONS;
7.
Restart Vista Plus.
Adding the obj_id Index in Oracle

Vista Plus 5.5.2 includes a SQL script file to add the index to an Oracle database if it
doesnt already exist. You can run the script while the Vista Plus service is running. Enter
the command shown for your operating system:
On UNIX:
su - oracle -c "sqlplus User/Pass @VPHome/Oracle_Upgrade_5.5.20.sql"
User is the name of the Oracle user set up for Vista Plus and pass is the password for
that user. VPHome is the path to the Vista Plus home directory.
On Windows:
Oracle\bin\sqlplus.exe User/Pass @VPHome/Oracle_Upgrade_5.5.20.sql
Oracle is the path to the Oracle home directory. User is the name of the Oracle user set
up for Vista Plus and pass is the password for that user. VPHome is the path to the
Vista Plus home directory.
Increasing the Maximum Oracle CLOB Size

Note
Important! This procedure applies only to Vista Plus installations using an

Oracle database. If Vista Plus uses a MySQL database, skip this section.
The Oracle connector that Vista Plus uses to connect to its Oracle database has a known
bug when retrieving large CLOB (Character Large Object) columns. If a single CLOB is
longer than 12,000 characters, it is truncated and the rest of the data is not retrieved. Many
Vista Plus installations will not have a problem, as it is unusual for a CLOB to be that
large. However, some page security set definitions, especially those generated by the Vista
Plus Interface for PeopleSoft, can have thousands of conditions and may exceed this limit.
If this happens, only part of the security set is returned, causing errors in Vista Plus. It is
also possible, but rare, for other types of data to exceed the limit.
If you think you may have page security expressions or other data, such as a saved search
expression, that exceed the CLOB size limit, you can modify an Oracle configuration
setting to change the CLOB size limit to be larger than the largest piece of data in your
Vista Plus database. The procedure below checks each Vista Plus column which may have
data that exceeds the default CLOB limit to find the largest piece of data, then tells you
how to change the limit to be as large as needed.

Page 35
Update Instructions
1.
Using SQLPlus or another Oracle SQL client, enter the following command:
select dbms_lob.getlength(EXPR) from VP_PAGE_SEC_SET order by
dbms_lob.getlength(EXPR) desc ;
This returns the lengths of each entry in the EXPR column of the VP_PAGE_SEC_SET
table, which holds the page security expressions. The lengths are listed in descending
order, so the largest one is first.
2.
To make sure none of the other likely table columns contain data longer than the
longest page security expression, repeat the command for each column:
select dbms_lob.getlength(P4) from VP_ACTION order by
dbms_lob.getlength(P4) desc ;
select dbms_lob.getlength(P5) from VP_ACTION order by
dbms_lob.getlength(P5) desc ;
select dbms_lob.getlength(MESSAGE_TEXT) from VP_ALARM order by
dbms_lob.getlength(MESSAGE_TEXT) desc ;
select dbms_lob.getlength(QUERY_EXPR) from VP_SEARCHES order by
dbms_lob.getlength(QUERY_EXPR) desc ;
select dbms_lob.getlength(DATA1) from VP_REPORT_ELEMENT order by
dbms_lob.getlength(DATA1) desc ;
select dbms_lob.getlength(DATA2) from VP_REPORT_ELEMENT order by
dbms_lob.getlength(DATA2) desc ;
3.
How to change the maximum CLOB size is different on UNIX and Windows.
On UNIX:
Use a text editor to edit the odbc.ini file in the ddc_odbc directory.
Add a StaticCursorLongCollBuffLen=x parameter to the driver

definition section of odbc.ini. Set x to the largest CLOB length returned for any
table in step 2, plus 5120 as a padding for safekeeping. For example, if the
largest size found in step 2 was 14495, set
StaticCursorLongColBuffLen=19615. (19615 = 14495+5120)
Save your change and close the odbc.ini file.
On Windows:
Uncompress the downloaded DDODBC.zip file to get the DDODBC.reg file.
Use a text editor to open DDODBC.reg. The file contains the following text:
[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\DDC60]
"StaticCursorLongColBuffLen"="20000"
Change DDC60 to the data source name (DSN) of your Vista Plus database.
Change 20000 to the desired maximum CLOB size
Save your changes and close the file.
Execute the file using any Windows method, such as double-clicking it in

Windows Explorer.

Page 36
Update Instructions
4.
Restart the Vista Plus server.
Correcting Possible Index Search Problems

When using Vista Plus 5.5.0 or 5.5.1, a very specific combination of settings and events, in
a specific order, could cause Web View global index searches and generation searches to
miss matches in some generations. The problem which led to this has been fixed (see issue
1656 in Fixes and Changes in Version 5.5.2 on page 11). However, there could be
installations where some report generations are in the error condition and need to be
corrected.
Note
Important! The problem described in this section affected only global index
searches and generation searches, and only in the conditions described. All
index values were always stored correctly in the report warehouse. Any
search which looked at the report warehouse, such as an index search in an
open generation, correctly found all matches.
The problem is related to the ability to store index values in the Vista Plus database, a
feature introduced in version 5.5.0. This series of actions caused the issue:
1.
Store index entries in the database, either by setting the server.cfg parameter
StoreIndexValuesInDB to 1 or by not having the parameter in server.cfg. This is the
default condition in Vista Plus 5.5.x.
2.
Store index values for one or more generations in both the database and in the
generation directory in the report warehouse. You could do this by capturing one or
more generations to reports with indexes defined, by reindexing existing generations,
or by using the convert_gens command.
When Vista Plus stores the index values for a generation in the database, it sets a flag
in the generation record, indicating it has done so.
3.
Set StoreIndexValuesInDB to 0, so that future index values will be stored only in the
report warehouse, not in the database. This does not affect generations which already
have values in the databasethose values stay there.
4.
Reindex one or more generations that have index values in the database. The
reindexing removes the old values from the database and report warehouse, and,
because the StoreIndexValuesInDB setting has been changed, writes the new values
only to the report warehouse.
This is where the error occurred. While the index values are no longer in the database,
reindexing the generation did not reset the flag in the generation record to indicate
this change. The flag still indicated that the values were in the database.
Note
Vista Plus lets you reindex either an individual index or all indexes in a
generation. This problem occurred with either type of reindexing. If you
reindexed an individual index, the problem affected only that index. The
values for the other indexes in that generation remained in the database.

Page 37
Update Instructions
After this series of actions, if the IndexSearchMethod parameter in server.cfg is set to auto
or db, global index searches and generation searches will not find any matches in the
generations where the flag incorrectly indicates that index values are in the database.
The fastest way to ensure that these types of searches are not missing any matches is to
change the IndexSearchMethod setting to file. Searches will then always look in the
report warehouse for index values, and will find all matches. (It may make searches take
longer, and it you will not be able to search offline generations.) However, it leaves the
flag in the generation record in the incorrect stateindicating that index values are in the
database when they are not.
To reset the index location flag for a generation you think is in this condition, reindex it
after installing Vista Plus 5.5.2. This will write the new index values to the report
warehouse and reset the flag to indicate that they no longer exist in the database. All
searches will be able to find matches in this generation, even if you return the
IndexSearchMethod setting to auto.
Note
Even if you reindex only one index for a generation, Vista Plus will set the
flag to indicate that index values are not in the database for that generation,
and will search only in the report warehouse for all indexes for that
generation. This is necessary to make sure that no matches are missed.
Installing LDAP Authentication or TransVue Tagging

The files for the new LDAP authentication module and the optional TransVue Tagging
feature are in their own folders in the Vista Plus section of the OpenText Knowledge
Center. Follow the directions in the Vista Plus Server Installation Guide to download and
install either of these features.
Note
TransVue Tagging is an optional feature, and must be purchased and licensed

separately. Contact your OpenText representative for more information.
Updating Remote Hosts

The 5.5.2 SP includes a fix to the vadmin command. If you have vadmin and the remote
capture tools installed on any remote hosts, you should also upgrade those hosts. To do
so:
1.
Download the SP file from the Knowledge Center to each remote host, following the
instructions in Downloading the 5.5.2 Files on page 22. Be sure to download the
correct file for the remote hosts operating system. You do not need to download the
patch installation utility or any other files.
2.
Extract the vadmin and remote capture tools files from the SP file.
On UNIX:
Be sure you are logged in as root.
Change to the directory where the remote capture tools are installed. For your
convenience, you may want to copy the SP file to this location.

Page 38
Update Instructions
Use the uncompress and tar commands to extract the vadmin, rcapture, and
dircapture files to the current directory:
uncompress SPfile.tar.Z
tar xvf SPfile.tar ./vadmin ./rcapture ./dircapture
SPfile is the name of the SP file you downloaded from the Knowledge Center. If
you did not copy the file to the current directory, it is the entire path to the file.
On Windows:
Using Winzip or another file unzipping utility, extract the files vadmin.exe and
rcapture.exe to the directory where those files are installed, replacing the
previous versions.
Installing the Capture Printer Port

The Vista Plus Capture Printer Port is supported on either Windows 2003 or Windows
2008 R2. Installation instructions for the capture printer port on Windows 2003 are in
chapter 3 of the Vista Plus Server Installation Guide. However, because support for the
capture printer port on Windows 2008 R2 was added after the initial release of Vista Plus
5.5.2, installation instructions for Windows 2008 R2 are not in the Installation Guide. They
are in a separate document, Vista Plus Capture Printer Port for Microsoft Windows 2008
Release Notes.
The installation procedures for both Windows 2003 and Windows 2008 R2 are different
than the procedure was for earlier versions of Windows.
Updating the Server Admin Client

If you install the Vista Plus 5.5.2 Server Administration client on a computer which has a
5.5.x client installed, it automatically upgrades the existing installation. Follow the
procedure below.
You can also install the 5.5.2 Server Admin client on a computer which does not have a
previous client installed. In that case, follow the procedure found in the Vista Plus Server
Installation Guide.
To upgrade Server Admin

Tip
Important! During the upgrade, all the connections defined in Server Admin
will be lost. Before the upgrade, you may want to write down the name, host,
port, and user for all of your server connections. After the upgrade, youll
need to re-enter all server connections and redo any other customizations you
had added to the console file.
1.
Extract the setup.exe file from the setup_adm.zip file and run it.
2.
When asked if you want to upgrade Server Admin, click Yes.
3.
When asked if you want to continue and complete the installation, click Next.
4.
Click Finish when done.

Page 39
Update Instructions
5.
Start Server Admin and re-enter your connection information.
Updating Web View

We recommend you upgrade Web View after testing the server upgrade so any potential
problems found during Web View testing are not incorrectly thought to be due to the
server upgrade. In general, you need to remove the old Web View installation following
the procedure for your servlet engine, then install the new version. For example, for
Apache Tomcat, you would:
Warning
Before removing the existing Web View, be sure to back up any files you have
modified. This will help you in making equivalent modifications to the new
files if needed.
1.
Shut down Tomcat.
2.
In the Tomcat webapps subdirectory, delete the vp_web.war file and the vp_web
subdirectory.
3.
Delete the Tomcat work/Standalone/localhost/vp_web directory. This is where Tomcat

caches working copies of the Web View jsp files.
4.
Copy the new vp_web.war file to the webapps subdirectory.
5.
Restart Tomcat. This deploys the Web View application automatically.
Other servlet engines will have their own procedures for removing the existing Web View
and installing the new one.
Updating the Windows Client

To update the Windows Client, execute the setup.exe file. Then, continue from step 3 of the
installation procedure in Chapter 2 of the Vista Plus Windows Client Users Guide.

Page 40

Vista Release 5

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Vista Release 5

Uploaded by

Copyright:

Available Formats

Vista Plus

Copyright Open Text Corporation. All rights reserved.

Copyright Open Text Corporation. All rights reserved.

Although we use virtual environments when developing and testing Vista

Vista Plus Server

BUNDLE 11i (B11.11.0306), GOLDAPPS11i (B11.11.0606.446),

For Itanium and RISC processors; requires 11.23 Standard Patch

For Itanium and RISC processors

Tested with Technology Level 5, SP 6, and C++ runtime 10.1.0.2

Copyright Open Text Corporation. All rights reserved.

Operating Sys. Version

Requires UltraSPARC architecture and SUNWlibC patch

Service Pack 2 or later

For both: RAC environment and DataDirect 6.0

With MyODBC 3.51 and ODBC Driver version

Copyright Open Text Corporation. All rights reserved.

Remote Capture Tools

HP Tru64 UNIX (OSF1)

Legacy Remote Capture Tools

Copyright Open Text Corporation. All rights reserved.

Capture Printer Port

Server 2003 Standard or Enterprise

Server 2008 R2 Standard or Enterprise

LDAP Authentication Module

Vista Plus Server

Supports LDAPv3; tested using OpenLDAP

Vista Plus Server

For rcapture and vp_load_index, any operating

Vista Plus Output Manager

TransVue Tagging is an optional, and separately licensed, new feature of Vista

Copyright Open Text Corporation. All rights reserved.

Needs Cumulative Patch for Internet Information Service

x should be 9 or higher; testing was done on 5.5.27 using

On Windows 2008 R2; testing was done with 6.0.33 using

BEA WebLogic Server

Service Pack 3 for version 8.1

Copyright Open Text Corporation. All rights reserved.

Tested with 7.0.5730.13

Tested with 8.0.7600.16385

Tested with 3.5.16

Tested with 5.0.1

Pop-up blocker software, including the integrated pop-up blockers in Internet

Both 32- and 64-bit versions

32- and 64-bit

Windows Vista Business

Service Pack 2, 32- and 64-bit

2003 Server Standard

Service Pack 1, 32- and 64-bit

2003 Server Enterprise

Service Pack 2, 32- and 64-bit

Service Pack 3, 32- and 64-bit

The Server Administration client requires a version of Microsoft Management Console

Both 32- and 64-bit versions

32- and 64-bit

Windows Vista Business

Service Pack 2, 32- and 64-bit

Windows Vista Enterprise

Service Pack 2, 32- and 64-bit

2003 Server Standard

Service Pack 1, 32- and 64-bit

Service Pack 3, or Service Pack 2 with KB935448, 32- and 64-bit

Copyright Open Text Corporation. All rights reserved.

Enhancements in Version 5.5.2