Serena PVCS Version Manager
Version 8.2
Readme File: Installation Information
Last updated on 15 November 2008
Build 784

The readme contains information, not included in the manuals or online help, on installing and using the current release of Version Manager. Additional information is available in KnowledgeBase articles available via your browser.

The Version Manager readme consists of the following files:

This readme file is organized into distinct parts. Please read the parts that correspond to the Version Manager components that you are using.


Table of Contents

Part 1: Supported Platforms / System Requirements
Part 2: Version Manager CLI, Desktop Client, File Server, and PCLI
Part 3: Version Manager IDE Client
Part 4: Version Manager Web Client
Part 5: Version Manager WebDAV Server
Part 6: Serena Meritage
Part 7: Copyright/Disclaimers/Support

 

Part 1: Supported Platforms / System Requirements

1.0 Supported Platforms

1.1 Supported Operating Systems

1.2 Supported Web Servers

1.3 Supported Web Browsers

1.4 Supported Java Run Time Environments for Web Browsers

2.0 System Requirements

2.1 Client Requirements

2.2 Server Requirements

3.0 Windows Notes

3.1 IIS 6 on Windows 2003 Server Requires Extra Setup

3.2 Using FireFox and Mozilla Web Browsers with IIS 6 on Windows 2003 Server

4.0 UNIX/Linux Notes

4.1 Apache Web Servers and Dynamic Shared Object (DSO) Support

4.2 Additional Space Requirements During Installation

5.0 Serena License Manager

6.0 Serena Builder

6.1 Obtaining Serena Builder 6.41.1

6.2 IMPORTANT! You Must Download and Install the Integration Library Files Before Installing Serena Builder

7.0 Serena TeamTrack & Business Mashups

8.0 Tomcat

 

Part 2: Version Manager CLI, Desktop Client, File Server, and PCLI

9.0 Installation

9.1 Clean Up References to Obsolete File Servers

9.2 Disable Anti Virus Software

9.3 File Server and Web Server Application Must Be Installed Together

9.4 Installing a Patch on a Non-English System

9.5 LDAP & SSL

9.6 Linux Error: "Illegal end day of week in month"; PCLI and Desktop Lockup

9.7 Remove the NT Service Before Upgrading (Version Manager File Server, Web Server, or WebDAV Server) [REQUIRED]

9.8 Stop the Server and Upgrade Both Client and Server [REQUIRED]

9.9 Uninstall Before Upgrading from Earlier Versions

9.10 Windows Vista Requires Administrative User Rights

9.11 Workstation Installation

9.12 Windows Installation

9.13 UNIX Installation

 

Part 3: Version Manager IDE Client

10.0 Supported Software

10.1 Supported IDEs

10.2 Use Only Windows Security for Web Projects

10.3 Supported Serena TrackerLink Versions

10.4 Eclipse Rich Integration: TeamTrack Integration Requires Java Runtime Environment (JRE) 1.4.2_06 or Later

10.5 Eclipse Rich Integration on Linux: Active Issues and IDE Folder View Does Not Work with NT Authentication

10.6 Eclipse and Visual Studio Rich Integrations: Requires TeamTrack 6.3 to Display Japanese Characters

10.7 Visual Studio: Crashes with Rational XDE Developer Plus

11.0 Installation

11.1 Integrating with IBM Rational Application Developer 7

11.2 You Must Uninstall the Previous IDE Client Before You Upgrade

11.3 TrackerLink Users Must Select a Source Control Provider

11.4 Run Visual Studio at Least Once Before Installing the Integration

11.5 Set the SCC Provider to Version Manager Before Installing SourceBridge

11.6 Eclipse: Plug-In Sometimes Fails to Initialize After Version Manager Installation

 

Part 4: Version Manager Web Client

12.0 Upgrade Considerations

12.1 Uninstall Before Upgrading from Earlier Versions

12.2 Windows: No Apparent Way for Non-Admin to Uninstall the Web Client

12.3 Microsoft Vista: Disable Protected Mode to Access the Web Client [REQUIRED]

12.4 Remove the NT Service Before Upgrading (I-Net or WebDAV Server) [REQUIRED]

12.5 Migrating a Large List of Version Manager Servlets

13.0 Installation

13.1 Problem Installing Applet When an Older Applet Is Loaded

13.2 Do Not Use Sun JRE 1.4.0x with Internet Explorer

13.3 Login Problems Resulting from Disabling Cookies

13.4 Installing the Web Server Application Separately Requires Additional Steps

13.5 Do Not Use a UNC Path to Install the Version Manager Application Server, File Server, or Web Server on Windows 2003

13.6 Installing the Version Manager Web Client on Windows 2000

13.7 iPlanet Web Server on Pentium IV Servers

13.8 UNIX: Browser Location Must Be Added to Path

13.9 Running configure_inet to Configure a Different Web Server

13.10 Using TrackerLink with Secure Sockets Layer (SSL)

13.11 Large Temporary Web Server Installation File on the Client Machine Resulting from Web Client Installation

13.12 Using the Web Client with a Version Manager File Server

13.13 IIS 6 on Windows 2003 Server Requires Extra Setup

13.14 Apache Web Servers and Dynamic Shared Object (DSO) Support

 

Part 5: Version Manager WebDAV Server

14.0 Supported WebDAV Clients

15.0 Installation

15.1 Remove the NT Service Before Upgrading (I-Net or WebDAV Server) [REQUIRED]

15.2 Apache Web Servers and Dynamic Shared Object (DSO) Support

15.3 Using Microsoft Office with Version Manager WebDAV Server

 

Part 6: Serena Meritage

16.0 Support Notes

16.1 PowerPoint Is No Longer Supported

 

Part 7: Copyright/Disclaimers/Support

17.0 Support

17.1 Support Information

18.0 Notice Regarding Third Party Software

18.1 Third Party Software Disclaimers

18.2 Third Party Software Rights

 

To Top

Part 1: Supported Platforms / System Requirements

Return to Contents


1.0 Supported Platforms

1.1 Supported Operating Systems

O/S 32-Bit CPU's 64-Bit CPU's Notes
Pentium Class AMD64
(x86_64)
Itanium 2
(McKinley)
PA-RISC PowerPC SPARC
Windows 2000 Server SP4 S - - - - -  
Windows XP Pro SP2 C - - - - -  
Windows Vista Business C - - - - -  
Windows Vista Ultimate C - - - - -  
Windows Vista Enterprise C - - - - -  
Windows 2003 Server SP2 S - S - - - 2, 4
Red Hat Enterprise Linux 4.0 C S C S - - - - 1, 2, 4
Red Hat Enterprise Linux 5.0 C S C S - - - - 1, 2, 4
SuSE Linux 9 and 10 C S C S - - - - 1, 2, 4
HP-UX 11.11 and 11.23 - - C C S - - 2, 3, 4
AIX 5.3 and 6.1 - - - - C S - 2, 4
Solaris 9 and 10 - - - - - C S 2, 4
Notes:
  1. Linux 2.6 kernels require the compat-libstdc++ libraries in order to host the Version Manager Application
    Server (File Server, Web Server, WebDAV).
  2. Runs as a 32-bit application on 64-bit systems.
  3. Supported on Itanium using the HP-UX Aries PA-RISC emulator.
  4. Version Manager library files are 32-bit. Use 32-bit programs to load the Version Manager libraries. Examples of affected programs are web browsers used to run the VM web client, and custom built applications using the Version Manager Developer's Toolkit (DTK).

Legend: C = Client; S = Server; - = Not supported

1.2 Supported Web Servers

Web Server Notes
Microsoft Internet Information Services 5.0  
Microsoft Internet Information Services 6.0 1, 2
Sun ONE Web Server 7.0  
Sun Java System Web Server 6.1  
Apache 1.3 3
Apache 2.0.54 - 2.0.x 3
Tomcat 5.5 4
Notes:
  1. See IIS 6 on Windows 2003 Server Requires Extra Setup.
  2. See Using FireFox and Mozilla Web Browsers with IIS 6 on Windows
    2003 Server
    .
  3. Your Apache server must include DSO support.
  4. Supported for use with WebDAV only.

1.3 Supported Web Browsers

Browser O/S Notes
Internet Explorer 6 and 7 Windows  
FireFox 1.5 and 2.x All 1, 2
Mozilla 1.7 All 2
Notes:
  1. If using with the IE Tab extension, use the Options button
    on the IE Tab extension to specify that content from the VM
    server URL should always be rendered with the embedded IE.
  2. UNIX: If your browser quits working after installing Version
    Manager, edit the LD_LIBRARY_PATH variable to point to
    /usr/lib before /serena/vm/common/lib.

1.4 Supported Java Run Time Environments for Web Browsers

JRE Notes
Sun 1.6.0 -
Sun 1.5.0 -

Return to Contents


2.0 System Requirements

2.1 Client Requirements

In addition to Operating System requirements, the minimum system requirements are:

Client Systems – Minimum
Platform Memory CPU Disk Space
Win 2000 Pro 128 MB P200 140 MB
Win 2000 Server 128 MB P200 140 MB
Win XP Pro 128 MB P400 140 MB
Win Vista Biz 128 MB P400 140 MB
Win Vista Ult 128 MB P400 140 MB
Win Vista Ent 128 MB P400 140 MB
Win 2003 Server 128 MB P400 140 MB

In addition to Operating System requirements, the recommended system requirements are:

Client Systems – Recommended
Platform Memory CPU Disk Space
Win 2000 Pro 256 MB P550 140 MB
Win 2000 Server 256 MB P550 140 MB
Win XP Pro 256 MB P550 140 MB
Win Vista Biz 128 MB P550 140 MB
Win Vista Ult 128 MB P550 140 MB
Win Vista Ent 128 MB P550 140 MB
Win 2003 Server 256 MB P550 140 MB

2.2 Server Requirements

Memory requirements for the server depend on how many users access the server at the same time and how many daemon processes are running (by default, 5 to 20 daemons are running). Use the formula in the table below to calculate your memory needs.

Server Systems
  Base Concurrent Users Daemons Total
Formula 256 MB + 6 MB per user + 8 MB per daemon = ?
Example 256 MB 6 x 100 = 600 MB 8 x 20 = 160 MB = 1016 MB

NOTE: The example is for the case of 100 concurrent users and 20 daemon processes. It is included only to illustrate the use of the formula and is not intended as a recommendation.

Return to Contents


3.0 Windows Notes

3.1 IIS 6 on Windows 2003 Server Requires Extra Setup

If you are using IIS 6 on Windows 2003 Server, there is a little extra work you need to do to set up isapi-redirect.dll as a Web Service Extension File.

  1. Launch the Internet Information Services (IIS) Manager.

  2. Select Web Service Extensions from the left pane.

  3. Select the Extended tab in the right pane.

  4. Click the Add a new Web service extension link in the right pane. The New Web Service Extension dialog box appears.

  5. Enter a name for the extension in the Extension name field.

  6. Click the Add button. The Add file dialog box appears.

  7. Click the Browse button and navigate to the following directory:

    Install_Dir\vm\common\tomcat\bin\win32

  8. Select the isapi_redirect.dll and click the Open button.

  9. Click OK on the Add file dialog box.

  10. Select the Set extension status to Allowed checkbox on the New Web Service Extension dialog box.

  11. Click OK. The new extension appears under Web Service Extension with its status set to Allowed.

  12. Open Control Panel | Administrative Tools | Services and Restart IIS Admin Service.

3.2 Using FireFox and Mozilla Web Browsers with IIS 6 on Windows 2003 Server

The Version Manager Web client applet may not install on FireFox and Mozilla browsers if the server is running IIS 6 on Windows 2003. You can avoid this issue by defining a MIME type for .xpi files. See the following procedure.

To define a MIME type for .xpi files:

  1. Launch the IIS Microsoft Management Console.

  2. Right-click the Internet Information Services node and select Properties from the resulting menu.

  3. Click the MIME Types button.

  4. Click the New button.

  5. Enter .xpi in the Extension field.

  6. Enter application/octet-stream in the MIME Type field.

  7. Click OK on the various dialogs to apply the new settings.

For more information on setting MIME types, see:
http://support.microsoft.com/default.aspx?scid=kb;en-us;326965

Return to Contents


4.0 UNIX/Linux Notes

4.1 Apache Web Servers and Dynamic Shared Object (DSO) Support

To run the Version Manager web server or Version Manager WebDAV Server, your Apache web server must include Dynamic Shared Object (DSO) support. To see if your web server includes DSO support, run the following command from Apache's bin directory:

./httpd -l

If mod_so.c is listed in the command's output, your Apache install includes DSO.

If your installation of Apache does not include DSO support, you must obtain one that does, compile your own Apache server to include DSO support (as detailed in the Apache 1.3 README.configure file or the Apache 2.0 INSTALL file, as found in Apache's source distribution), or use a different web server.

4.2 Additional Space Requirements During Installation

Installation of Version Manager on Linux, Solaris, HP-UX, and AIX uses a significant amount of space in the directory specified by $TMP (this data sticks around until you delete it), and temporarily places a significant amount of data in the VM_Install_Dir/VM8.2_inst directory. The following table gives the approximate amounts of temporary space required during installation (sizes are in bytes):

Platform $TMP directory VM8.2_inst Total
Linux 108236 208612 316848
Solaris 108388 205232 313620
HP-UX 203568 404326 607894
AIX 98756 186334 285090

NOTE: About 170 MB of additional space is required to expand vm811unixpatch.tar so that it can be used; however, this data can be written anywhere on the network—or even to a CD-ROM.

Return to Contents


5.0 Serena License Manager

Version Manager requires Serena License Manager 2.1.4.

Return to Contents


6.0 Serena Builder

6.1 Obtaining Serena Builder 6.41.1

Serena Builder users can download the installer from the Serena Builder 6.41.1 page of the Serena Support site. Serena Builder is no longer included on the Pro DVD.

6.2 IMPORTANT! You Must Download and Install the Integration Library Files Before Installing Serena Builder

You must download and install the library files for the Version Manager integration to Serena Builder. You must do this before installing Serena Builder.

The library file installer is available as a zip file, VM_Builder_Int.zip. Unzip the file to extract the VM_Builder_Integration directory. This directory contains the installer for both Windows (setup.exe) and UNIX (vm_builderinst and vm_builder.zip) platforms.

The Serena Builder Integration library files will be installed in the Version Manager library path:Install_Dir\vm\common\lib

Return to Contents


7.0 Serena TeamTrack & Business Mashups

Version Manager integrates with Serena TeamTrack 6.6.1 and Serena Business Mashup 2008.

You may be unable to submit issues to TeamTrack 6.5 from the Version Manager integration when using Internet Explorer. This is due to a modified template in TeamTrack. See the TeamTrack readme for the work-around.

Return to Contents


8.0 Tomcat

Version Manager installs a private copy of Tomcat 5.5 in support of the Version Manager File Server, Web Server, and Meritage (WebDAV). This installation of Tomcat is designed to work with Version Manager. Version Manager will not work with a generic Tomcat installation. If you have other Tomcat installations, you should ensure that they are not using the same ports (8005, 8009, 8080, 8090).

 

Part 2: Version Manager CLI, Desktop Client, File Server, and PCLI

Return to Contents


9.0 Installation

9.1 Clean Up References to Obsolete File Servers

If a Version Manager client is configured to access a Version Manager file server that is unavailable, the client will hang. To avoid this, be sure to remove any obsolete file server definitions from your servers.ini file. See the Version Manager Administrator's Guide for information on configuring clients for use with file servers.

9.2 Disable Anti Virus Software

Before installing, disable any anti virus software. In particular, disable any anti virus software that scans files in real-time as you access them. Such real-time scanning software may hang the installer during the creation of the sample database.

9.3 File Server and Web Server Application Must Be Installed Together

When you install the Version Manager File Server component, you must also select the Web Server Application; otherwise, File Server fails to start properly.

9.4 Installing a Patch on a Non-English System

If English Version Manager has been installed on a non-English system, installing a Version Manager patch may change the Version Manager interface to match the language of the operating system.

To restore the English interface, delete the following files:

9.5 LDAP & SSL

If your LDAP server is configured to use Secure Sockets Layer (SSL) but there is not a certificate database in the VM_Install_Dir/vm/common/bin/OS directory or the database is missing the required SSL certificates, you will receive errors, such as:

"Failed to connect to LDAP server."
"You cannot access this project because your login account, UserName, is invalid ..."

See LDAP Connection/Authentication Fails in the Usage_Cautions.html readme file.

9.6 Linux Error: "Illegal end day of week in month"; PCLI and Desktop Lockup

This error message may appear during installation if you chose to install the sample database. The error may also occur when you attempt to run a PCLI command; the desktop client and the PCLI may hang. This occurs if the local time zone is set to "Australia/Melbourne". It may also occur with other time zones.

You can work around this issue by specifying an equivalent time zone (different name, same time). Here are two methods of changing your time zone:

9.7 Remove the NT Service Before Upgrading (Version Manager File Server, Web Server, or WebDAV Server) [REQUIRED]

If the Version Manager Application Server is installed as an NT Service, you must remove the service before upgrading.

To remove the service, perform the following steps:

  1. Launch the Version Manager Application Server Configuration utility from the Serena submenu of the Start menu.

  2. Click the Remove NT Service button.

  3. Restart the computer.

9.8 Stop the Server and Upgrade Both Client and Server [REQUIRED]

If you use the Version Manager Web Server, File Server, or WebDAV Server, you must stop the server before upgrading. See the Serena PVCS Version Manager Installation Guide for details.

If you use the Version Manager File Server, you must install the latest version of both the Version Manager client and the server.

NOTE If circumstances prevent you from completing both the server and client upgrades before work must resume, complete the server upgrades before resuming work. You are less likely to encounter problems when running old clients against new servers than when running new clients against old servers. Neither is recommended practice, but running old clients against new servers is less likely to present problems.

9.9 Uninstall Before Upgrading from Earlier Versions

NOTE This applies to full releases only, not to patches.

If you plan to install Version Manager in the same location as a previous version, you must uninstall it before upgrading. The Sample Database may remain, but all other files should be removed. Failure to perform these uninstall tasks may cause conflicts when you upgrade.

To preserve your Servlet definitions on Windows, back up the PVCSServlets.properties file and restore it to VM_Install_Dir\vm\inet\props\PVCSServlets.properties after installing the new version. Next, launch the Version Manager Web Server Application Configuration utility and make sure the "Location of Netscape Configuration Files" and/or "Location of Microsoft IIS Scripts Directory" matches the desired location for the new server installation (as they too will be inherited from PVCSServlets.properties). Finally, go to the Servlets tab, select the first servlet from the list, click Modify and then click Apply. Repeat this for all remaining servlets.

Users of Version Manager Server 6.8.00 on UNIX should preserve the file VM6800_Install_Dir/vminet/tomcat/webapps/vminet/WEB-INF/web.xml, and users of Version Manager I-Net 6.8.1x or later should preserve the file VM681x_Install_Dir/vm/common/tomcat/webapps/vminet/WEB-INF/web.xml. After installing the new version, copy the sections from <servlet> up to and including </servlet> for every servlet referring to a project database that was added to the old web.xml file, and paste them into the new web.xml file (which can be found at VM_Install_Dir/vm/common/tomcat/webapps/vminet/WEB-INF/web.xml). The two <servlet-mapping> ... </servlet-mapping> sections that exist for every one of these servlets should also be copied into the new web.xml file.

NOTE

9.9.1 Back Up Configuration Files

It is a good idea to save a backup copy of the following files:

Install_Dir\vm\common\bin\pvcsstart.bat (pvcsstart.sh on UNIX)
Install_Dir\vm\common\tomcat\conf\jk\uriworkermap.properties
(Windows only)
Install_Dir\vm\inet\props\PVCSServlets.properties (web servers only)
Install_Dir\vm\common\tomcat\webapps\vminet\WEB-INF\web.xml
(file servers only)
Install_Dir\vm\common\tomcat\webapps\webdav\WEB-INF\web.xml
(WebDAV servers only)
Install_Dir\vm\common\tomcat\webapps\merantfs\WEB-INF\server-config.wsdd

NOTE If upgrading from Version Manager 8.1.x, then the last line in the above list should be:
Install_Dir\vm\common\tomcat\webapps\serenafs\WEB-INF\server-config.wsdd

9.10 Windows Vista Requires Administrative User Rights

In order to use the integration on Windows Vista, you must be an administrative user in Vista or you must invoke Visual Studio with the Run as administrator option enabled.

You can right-click on the Visual Studio shortcut and select Run as administrator from the resulting pop-up menu, or you can configure the shortcut to always run as administrator.

9.11 Workstation Installation

9.11.1 Installation Using a UNC Path Name with Directory Names Longer Than Eight Characters

If you want to install to a server using a path name that contains any directory names longer than eight characters, you may first need to map a network drive to that location and use the drive mapping to install Version Manager. If you do not use a drive mapping, an error message may appear stating that the path to the setup executable is invalid.

To prevent errors when installing or working from a network installation of Version Manager, make sure network path names do not contain directory names longer than eight characters.

9.11.2 Workstation Installation May Fail with Microsoft Novell Client Drivers

Workstation installations of Version Manager may behave unpredictably if you are using Microsoft Novell Client drivers to access a Netware server. We recommend using Novell Netware Client drivers.

9.11.3 Windows XP: Custom Settings File islv.ini Storage Location Changes Between Upgrade VS New Installation of Version Manager 8.2

If you upgrade from Version Manager 8.1 to 8.2, islv.ini, the userwise custom setting information file, will be stored at \Windows.

If you install Version Manager 8.2 for the first time, islv.ini will be stored at \Documents and Settings\All Users\Application Data\Serena\VM.

See the Serena PVCS Version Manager 8.2 Installation Guide for more information.

9.12 Windows Installation

9.12.1 Administrator's Privileges Required for Windows 2000 Installation

Installing without Administrator's privileges results in an InstallShield error that requires you to remove the winnt/IsUnist.exe file. Removing this file also requires Administrator's privileges.

If you attempt to install Version Manager without Administrator's privileges and the winnt/IsUnist.exe file is deleted, an error box is displayed with an X in a red background and an OK button. Clicking OK terminates the installation process; ignoring the error box allows installation to complete successfully.

9.12.2 Do Not Use a UNC Path to Install the Version Manager Application Server, File Server, or Web Server on Windows 2003

This is not a supported configuration.

9.12.3 IDE Client Upgrade May Be Required

If your existing installation of the IDE client is older than 6.7.11 SP2, you must upgrade it when you upgrade Version Manager. Builds of the Version Manager IDE client prior to 6.7.11 SP2 will not work with newer builds of Version Manager.

9.12.4 Installation to Root of a UNC Share Shows Space Required as Zero

When you install to the root of a UNC share, the installer indicates that zero space is required. The installer shows the required space correctly if you select a directory on the share. In either case, Version Manager will be correctly installed--provided you actually have enough disk space on the share.

9.12.5 Version Manager Installation Fails Without Adequate Disk Space on Root Drive

To successfully install Version Manager, you need 450 MB of hard disk space on the drive containing Windows (150 MB for the CD-ROM installation) and 600 MB on your destination drive. If you delete temporary files created during installation, you will not need this amount of space once Version Manager is installed.

9.13 UNIX Installation

9.13.1 End-User Licensing on UNIX

To set up licensing for end-user workstations on UNIX, a shell script named vmreg updates the license.ini file in the $PVCS_BINDIR directory and/or the .islvrc file in an end user's home directory. The Version Manager installation script and launch scripts run vmreg automatically, but Administrators and users can run it as well. For example, the Administrator can save the current configuration-file information in $PVCS_BINDIR/license.ini, and then users can move the information into their personal .islvrc files by running vmreg. End users who use the command line, but not PCLI or the desktop client, need to run vmreg once before using the command line.

The script can be called in the following ways:

9.13.2 HP-UX: Recommended Kernel Parameter Settings

Set the following kernel parameters to allow the Version Manager web and file servers to work properly on HP-UX:

max_thread_proc 1000
maxfiles 2000

IMPORTANT: After setting the kernel parameters, you must rebuild the kernel.

9.13.3 Required Operating System Patches for UNIX Platforms

Some UNIX platforms require patches before they will run the JRE as used by Version Manager. See Serena support at support.serena.com for more information (Use the Advanced Search page to search for KB70396).

9.13.4 Users Must Install New Web Client Applet After Version Manager Is Upgraded [REQUIRED]

After you install Version Manager, web client users on Linux, Solaris, HP-UX, and AIX must install the new web client applet before logging in to the new server. Failure to do so may result in unpredictable behavior, such as users seeing error messages after successful check-out operations.

 

Part 3: Version Manager IDE Client

Return to Contents


10.0 Supported Software

10.1 Supported IDEs

The Version Manager IDE client supports the following development environments:

IMPORTANT!

10.2 Use Only Windows Security for Web Projects

Version Manager projects associated with Visual InterDev/FrontPage web projects rely on Windows security. For your web projects, do not configure access control databases.

See the Serena PVCS Version Manager IDE Client Implementation Guide for more information.

10.3 Supported Serena TrackerLink Versions

The Version Manager IDE client is certified for use with Serena TrackerLink 6.5 and above. However, Tracker 6.6 or later is required for the "Clean up associations on undo checkout" feature.

10.4 Eclipse Rich Integration: TeamTrack Integration Requires Java Runtime Environment (JRE) 1.4.2_06 or Later

If you are using an old version of the Java Runtime Environment (JRE), the Eclipse Issue view may not display reports and issues due to a TeamTrack authentication problem exhibited with versions of the JRE prior to 1.4.2_06

10.5 Eclipse Rich Integration on Linux: Active Issues and IDE Folder View Does Not Work with NT Authentication

The Linux version of the rich integration to Eclipse does not work correctly if the TeamTrack server is using NTLM authentication. One can still submit issues, but no issues are visible via the Active Issues or IDE Folder view.

To avoid this issue, do not to use NTLM authentication when the integration clients are on a non-windows platform. If you must use NTLM, set up an external virtual directory on the TeamTrack/IIS server.

10.6 Eclipse and Visual Studio Rich Integrations: Requires TeamTrack 6.3 to Display Japanese Characters

The Serena Issues view will incorrectly display Japanese characters unless it is used with TeamTrack 6.3 or newer.

10.7 Visual Studio: Crashes with Rational XDE Developer Plus

Visual Studio may crash when you open a solution that is under source control and contains an XDE model. This appears to be related to XDE loading an older version of the JRE.

Return to Contents


11.0 Installation

11.1 Integrating with IBM Rational Application Developer 7

The Version Manager plug-in does not work with Rational Application Developer 7.0.0.0. During the RAD install, you can choose to update the install. Please ensure that you install Rational Application Developer 7.0.0.2 or newer.

NOTE The Version Manager Patch Installer does not include the Eclipse Plug-In Installation dialogs. To upgrade an existing Rational Application Developer 6 and Version Manager 8.2 integration to RAD 7 and VM 8.2, use the following procedure:

  1. Run the Windows Add or Remove Programs utility.

  2. Select and uninstall any Version Manager 8.1.4.x patch you have already installed.

  3. Select the Serena ChangeMan Version Manager 8.2 installation and click the Change/Remove button.

  4. Select the Modify option and click the Next button.

  5. Clear the checkboxes next to the Eclipse plug-ins and click the Next button.

  6. Click the Finish button.

  7. Back at the Add or Remove Programs utility, select the Serena ChangeMan Version Manager 8.2 installation and click the Change/Remove button.

  8. Check the checkboxes next to the desired Eclipse plug-ins and click the Next button.

  9. If you are integrating with RAD 7 or generic Eclipse, you must click the Add button and enter the path when prompted for the path to the Eclipse installation. By default, RAD 7 is installed to:

    C:\Program Files\IBM\SDP70

    NOTE Any WSAD 5 or RAD 6 installations are automatically included in the dialog; To remove them from the list, select them and click the Remove button.

  10. Click the Next button.

  11. Click the Finish button.

11.2 You Must Uninstall the Previous IDE Client Before You Upgrade

To use version 8.2 of the Version Manager IDE client, you must uninstall any previous version of the IDE client on your system before installing Version Manager 8.2. If you wish to use an older verson of the IDE client once Version Manager 8.2 is installed, you must uninstall Version Manager 8.2 before installing the older software.

11.3 TrackerLink Users Must Select a Source Control Provider

If Serena TrackerLink is installed to your system, it remains the active source control provider after you install the IDE client.

To use the IDE client with TrackerLink:

  1. Exit any open IDEs.

  2. Select TrackerLink from the Serena Tracker program group in your Start menu. The Serena TrackerLink dialog box appears.

  3. Select Serena ChangeMan Version Manager from the SCC Provider drop-down list.

  4. Click the Activate button. The change will take effect the next time you start your IDE.

To use the IDE client without TrackerLink:

  1. Exit any open IDEs.

  2. Select Serena | Serena ChangeMan Version Manager | Version Manager IDE Client | Select Serena Provider from the Windows Start menu. The Select Serena Provider dialog box appears.

  3. Select Serena ChangeMan Version Manager.

  4. Click OK. The change will take effect the next time you start your IDE.

11.4 Run Visual Studio at Least Once Before Installing the Integration

Before installing the Version Manager integration to Visual Studio, ensure that the IDE has been run at least one time. Else a package load error may appear the next time Visual Studio is started. This in itself does no harm, but it prompts you as to whether you want to load this package in the future (you DO!). Choosing incorrectly at this point will disable the integration and require an uninstall and reinstall to fix the integration. It will load properly the next time you open Visual Studio.

11.5 Set the SCC Provider to Version Manager Before Installing SourceBridge

If you currently use TrackerLink with SCC IDEs and wish to use SourceBridge (TeamTrack) instead, change your SCC provider from TrackerLink to Version Manager before installing SourceBridge. SourceBridge will then set itself as the SCC provider and pass SCC information on to Version Manager.

To set the SCC provider, launch the Version Manager SCC Admin. For details, see the Serena PVCS Version Manager IDE Client Implementation Guide.

If you install SourceBridge while TrackerLink is still set as the SCC provider, SourceBridge will try to use TrackerLink as the SCC provider. Source control will not work.

To correct this, set the SCC provider in the System Settings tab of the SourceBridge dialog box. For details, see the "About Setting Up SourceBridge" section of the Serena PVCS Version Manager Administrator's Guide.

11.6 Eclipse: Plug-In Sometimes Fails to Initialize After Version Manager Installation

Workaround: Reboot to update your system's path information.

 

Part 4: Version Manager Web Client

Return to Contents


12.0 Upgrade Considerations

12.1 Uninstall Before Upgrading from Earlier Versions

If you plan to install Version Manager in the same location as a previous version, you must uninstall it before upgrading. The Sample Database may remain, but all other files should be removed. Failure to perform these uninstall tasks may cause conflicts when you upgrade.

To preserve your Servlet definitions on Windows, back up the PVCSServlets.properties file and restore it to VM_Install_Dir\vm\inet\props\PVCSServlets.properties after installing the new version. Next, launch the Version Manager Web Server Application Configuration utility and make sure the "Location of Netscape Configuration Files" and/or "Location of Microsoft IIS Scripts Directory" matches the desired location for the new server installation (as they too will be inherited from PVCSServlets.properties). Finally, go to the Servlets tab, select the first servlet from the list, click Modify and then click Apply. Repeat this for all remaining servlets.

Users of Version Manager Server 6.8.00 on UNIX should preserve the file VM6800_Install_Dir/vminet/tomcat/webapps/vminet/WEB-INF/web.xml, and users of Version Manager I-Net 6.8.1x or later should preserve the file VM681x_Install_Dir/vm/common/tomcat/webapps/vminet/WEB-INF/web.xml. After installing the new version, copy the sections from <servlet> up to and including </servlet> for every servlet referring to a project database that was added to the old web.xml file, and paste them into the new web.xml file (which can be found at VM_Install_Dir/vm/common/tomcat/webapps/vminet/WEB-INF/web.xml). The two <servlet-mapping> ... </servlet-mapping> sections that exist for every one of these servlets should also be copied into the new web.xml file.

Servlets defined in UNIX Version Manager Server releases prior to 6.8.00 (using the servlets.properties file) cannot be preserved.

Before uninstalling, ensure that the Version Manager Web Server and your web server (IIS, iPlanet, Java System Web Server, or Apache) are NOT running.

12.1.1 Back Up Configuration Files

It is a good idea to save a backup copy of the following files:

Install_Dir\vm\common\bin\pvcsstart.bat (pvcsstart.sh on UNIX)
Install_Dir\vm\common\tomcat\conf\jk\uriworkermap.properties
(Windows only)
Install_Dir\vm\inet\props\PVCSServlets.properties (web servers only)
Install_Dir\vm\common\tomcat\webapps\vminet\WEB-INF\web.xml
(file servers only)
Install_Dir\vm\common\tomcat\webapps\webdav\WEB-INF\web.xml
(WebDAV servers only)
Install_Dir\vm\common\tomcat\webapps\merantfs\WEB-INF\server-config.wsdd

12.2 Windows: No Apparent Way for Non-Admin to Uninstall the Web Client

If the applet is not completely removed, there may be unusual behavior after you install a different version. Follow these steps to remove the applet:

12.2.1 Version 7.5 or Earlier

  1. In <Windows Dir>\Downloaded Program Files, right-click the VM I-Net applet, and remove it.

  2. Remove <Windows System Dir>\vmi660.dll.

  3. Remove <Windows Dir>\Java\lib\vmi660.zip.

  4. In the registry editor, remove the following entry:

    HKEY_CLASSES_ROOT\CLSID\{CCF028C4-4631-11D3-90BD-00A0C9B727E1}

12.2.2 Version 8.0 or Later

  1. In <Windows Dir>\Downloaded Program Files, right-click the VM I-Net applet, and remove it.

  2. Remove <Windows System Dir>\vmi660.dll.

  3. Remove <Windows Dir>\Java\lib\vmi660.jar.

  4. In the registry editor, remove the following entry:

    HKEY_CLASSES_ROOT\CLSID\{CCF028C4-4631-11D3-90BD-00A0C9B727E1}

12.3 Microsoft Vista: Disable Protected Mode to Access the Web Client [REQUIRED]

To access the web client, you must disable the Protected Mode option in Internet Explorer for Vista. To do so, you can either double click on the Protected Mode On status message from the Internet Explorer status bar or select Tools | Internet Options | Security and clear the Enable Protected Mode checkbox.

12.4 Remove the NT Service Before Upgrading (I-Net or WebDAV Server) [REQUIRED]

If the PVCS Version Manager Application Server is installed as an NT Service, you must remove the service before upgrading. To do so, select Start | All Programs | Serena | PVCS Version Manager 8.2 | Version Manager Application Server | Version Manager Application Server Admin dialog. Click the Remove NT Service button.

12.5 Migrating a Large List of Version Manager Servlets

NOTE: This procedure applies to all platforms.

It is not realistic to try to manually reconfigure your Version Manager web server for more than five servlets. You can "migrate" key configuration files over to the new server to help automate the process; however, if you are migrating a large number of servlets, there are some things to know:

  1. If the installation directory is the same, paths internal to these files should still be valid. However, you should double-check the following file:

    ...\Serena\vm\common\tomcat\webapps\vminet\WEB-INF\web.xml

  2. If the server name is the same, this parameter should still be valid; however, if you migrate to a new server, you should modify the following files:

    ...\Serena\vm\common\tomcat\webapps\vminet\WEB-INF\web.xml
    ...\Serena\vm\inet\props\PVCSServlets.properties

  3. With Version Manager 8.0, we use a different AJP worker (AJP13 instead of AJP12). We recommend that you make the change as well. Check the following file:

    ...\Serena\vm\common\tomcat\conf\jk\uriworkermap.properties

  4. Version Manager 7.5 has a now obsolete parameter. It should be removed. It will not be written in the new files.

    Edit the following file:

    ...\Serena\vm\common\tomcat\webapps\vminet\WEB-INF\web.xml

    Remove the servlet mapping for "ProjectServletAlias". This is a delicate edit. You must comment out or remove the entire exact section. As long as you are careful, the format is easy to discern. It looks like this:

    <servlet-mapping>
      <servlet-name> ProjectServletAlias </servlet-name>
      <url-pattern> /ProjectRootName </url-pattern>
    </servlet-mapping>

CAUTION: We recommend that you back up your existing files before modifying them.

Additional note: A project database (PDB) served by File Server appears the same as any other PDB in the configuration files noted above; you do not have to do anything differently to access a File Server PDB.

To TOC


13.0 Installation

13.1 Problem Installing Applet When an Older Applet Is Loaded

If you try to install the Version Manager web client while another instance is running, an error occurs. Close other browser windows before installing the Version Manager web client.

NOTE: In some circumstances, you may need to remove the old applet. See Uninstall the Web Client.

13.2 Do Not Use Sun JRE 1.4.0x with Internet Explorer

Using Sun's JRE 1.4.0x may cause instabilities in Internet Explorer and is not recommended. For example, the browser may crash when used with auto-logon. To avoid these issues, use JRE 1.5x.

13.3 Login Problems Resulting from Disabling Cookies

If you disable cookies in your browser, you will not be able to log in to the Version Manager web client. The Version Manager web client uses cookies to store login information.

13.4 Installing the Web Server Application Separately Requires Additional Steps

If you add the Version Manager Web Server Application after installing Version Manager, you must run the Version Manager Application Server Admin tool and perform the following steps:

  1. Go to the Servlets tab.
  2. Select a servlet (SampleDB will suffice).
  3. Click Modify.
  4. Click Apply.

Otherwise, you cannot access /vminet.html or (when File Server is installed) /serenafs/Admin.

13.5 Do Not Use a UNC Path to Install the Version Manager Application Server, File Server, or Web Server on Windows 2003

This is not a supported configuration.

13.6 Installing the Version Manager Web Client on Windows 2000

To install the Version Manager Web Client on Windows 2000 Server machines, you must have local Administrator privileges.

13.7 iPlanet Web Server on Pentium IV Servers

To start iPlanet Web Server on Pentium IV servers, you must disable internal servlet support. From the iPlanet Web Server Administration page, select a server to manage. Select the Servlets tab, and then select the No option under Activate the Servlet Engine.

13.8 UNIX: Browser Location Must Be Added to Path

For the Version Manager applet to load properly, you must add the browser location to your path. For example:

PATH=/apps/mozilla:$PATH; export PATH

ALSO: Do not launch the browser by using a fully qualified path to its executable. Instead, let it be found using the PATH variable:

mozilla &

13.9 Running configure_inet to Configure a Different Web Server

You can configure a different Web Server to work with Version Manager after the installation has completed. To do so, run the command:
VM_Install_Dir/vm/OS/bin/configure_inet VM_Install_Dir.

For example:
/usr/serena/vm/linux/bin/configure_inet /usr/serena

13.10 Using TrackerLink with Secure Sockets Layer (SSL)

To use TrackerLink with the Version Manager web client and the Tracker web client on an SSL-enabled server, you must add an SSL certificate to the JRE keystore. Otherwise, TrackerLink issue associations will fail.

After installing and configuring the Tracker web server and the Version Manager web server, do the following:

  1. If you don't already have it, download and install JDK 1.4.2x or 1.5x.

  2. Determine the location of the certificate file that enables SSL on your web server. Certificate files are issued by signing authorities, such as VeriSign, and have a .CER file extension.

  3. Run the following command:

    JDK_Install_Dir\bin\keytool.exe -import -file Certificate_File -keystore Install_Dir\vm\common\jre\win32\lib\security\cacerts

    Where:

  4. When prompted, enter the password for the JRE keystore. The default password is changeit.

13.11 Large Temporary Web Server Installation File on the Client Machine Resulting from Web Client Installation

Once installation of the Version Manager Web Client is complete, you can delete the file named "Serena ChangeMan Version Manager.msi" if disk space is a consideration. The file is typically located in a folder named "C:\Windows\Downloaded Installations" and is around 110 MB.

After you delete the file, you can still use Add/Remove Programs to modify or remove Version Manager.

13.12 Using the Web Client with a Version Manager File Server

To enable web-client users to access a project database located on a Version Manager File Server, you must configure the web server to access the file server. You do this by running the desktop client on the system running the Version Manager Web Server and entering the File Server specification in the Admin | File Server menu. Following that, be sure to specify a file server path map Client Name–based location for the project database when you set up the servlet. No setup is required on the web client itself.

13.13 IIS 6 on Windows 2003 Server Requires Extra Setup

NOTE: If you are using IIS 6 on Windows 2003 Server, there is a little extra work you need to do to set up isapi-redirect.dll as a Web Service Extension File. See IIS 6 on Windows 2003 Server Requires Extra Setup.

13.14 Apache Web Servers and Dynamic Shared Object (DSO) Support

To run Version Manager web or Version Manager WebDAV Server, your Apache web server must include Dynamic Shared Object (DSO) support. To see if your web server includes DSO support, see the topic in the Supported Platforms / System Requirements section.

 

Part 5: Version Manager WebDAV Server

Return to Contents


14.0 Supported WebDAV Clients

Version Manager works with the following WebDAV clients:

NOTE:

To TOC


15.0 Installation

15.1 Remove the NT Service Before Upgrading (I-Net or WebDAV Server) [REQUIRED]

If the PVCS Version Manager Application Server is installed as an NT Service, you must remove the service before upgrading. To do so, select Start | All Programs | Serena | PVCS Version Manager 8.2 | Version Manager Application Server | Version Manager Application Server Admin dialog. Click the Remove NT Service button.

15.2 Apache Web Servers and Dynamic Shared Object (DSO) Support

To run Version Manager web or Version Manager WebDAV Server, your Apache web server must include Dynamic Shared Object (DSO) support. To see if your web server includes DSO support, see the topic in the Supported Platforms / System Requirements section.

15.3 Using Microsoft Office with Version Manager WebDAV Server

Version Manager WebDAV Server is configured to work with the Serena Meritage client by default. Meritage is an extension to Office that enables you to use Version Manager features like Check-In and Checkout from within Word, Excel, or PowerPoint. If you do not want to use Meritage but you want to use Office as a WebDAV client, you need to configure the WebDAV server by commenting out the following line in VM_Install_Dir/mv/common/tomcat/webapps/SampleDB.dav/WEB-INF/classes/webdav.properites:

Dav.NoLockAgent.Microsoft-Office=Microsoft Data Access Internet Publishing Provider DAV

Important: You must restart Tomcat and any configured web server for this change to take effect.

For more information on Meritage and Version Manager WebDAV Server, refer to the user and installation guides.

 

Part 6: Serena Meritage

Return to Contents


16.0 Support Notes

16.1 PowerPoint Is No Longer Supported

Microsoft PowerPoint is no longer supported by Serena Meritage.

 

Part 7: Copyright/Disclaimers/Support

Return to Contents


17.0 Support

17.1 Support Information

To contact Serena support, please log in at support.serena.com.

Return to Contents


18.0 Notice Regarding Third Party Software

18.1 Third Party Software Disclaimers

The following disclaimers are provided on behalf of third party components used by and distributed with the Version Manager web server, Version Manager File Server, and WebDAV Server. Please see the Serena PVCS Version Manager documentation for acknowledgements, and individual LICENSE files for additional information, regarding any third party components.

THE JAVA RUNTIME ENGINE, TOMCAT AND XERCES JAVA PARSER (THIS SOFTWARE) IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL SUN MICROSYSTEMS, OR THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS, BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

18.2 Third Party Software Rights

DocuComp® comparison technology licensed from ASI Software.
Portions of the software, DocuComp® comparison © 2004 ASI Software, Inc. All rights reserved.

This product includes software developed by
The Apache Software Foundation (http://www.apache.org/).

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)

Portions © Copyright 2006 Microsoft Corporation. Al Rights Reserved.

Portions © Copyright 1996, 1999 International Business Machines Corporation and others. All Rights Reserved.

Portions © Copyright Intalio Inc. and others. All Rights Reserved.

Portions © Copyright eHelp Corporation. All Rights Reserved.

 

Return to Contents


End Readme
Copyright © 2003–2008 Serena Software, Inc. All rights reserved.

$Revision: 1.47 $