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:
Installation Information (this file)
Information on system requirements and important tips on correctly installing Version Manager. Read this before installing Version Manager.
Usage Cautions (usage_cautions.html)
Performance tips and workarounds to help you proactively avoid undesirable outcomes. Read this before using Version Manager or attempting to recover from a critical error.
Known Issues (known_issues.html)
Information on cosmetic defects, non-critical errors, and issues for which there are no preventative measures. Look here when you experience an error or other unexpected behavior not listed in the Usage Cautions file.
Release Notes (release_notesvm.html)
A list of the defects fixed, enhancements made, and behaviors changed in each release of Version Manager. Look here to see what has changed since you last upgraded.
This readme file is organized into distinct parts. Please read the parts that correspond to the Version Manager components that you are using.
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 |
| 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 SP3 | C | - | - | - | - | - | |
| Windows Vista Business/Ultimate/Enterprise SP2 | C | - | - | - | - | - | 5 |
| Windows 7 Enterprise | C | C | - | - | - | - | 2, 4, 5 |
| Windows 2003 Server SP2 | S | S | S | - | - | - | 2, 4 |
| Windows 2003 Server R2 | S | S | - | - | - | - | 2, 4 |
| Windows 2008 Server SP2 | S | - | - | - | - | - | 5 |
| Windows 2008 Server R2 | - | S | - | - | - | - | 2, 4, 5 |
| Red Hat Enterprise Linux 4.0 & 5.0 | C S | C S | - | - | - | - | 1, 2, 4, 6 |
| SuSE Linux 10, 10.1, 11, & 11.1 | C S | C S | - | - | - | - | 1, 2, 4, 6 |
| HP-UX 11.11, 11.23, & 11.31 | - | - | C | C S | - | - | 2, 3, 4, 6 |
| AIX 5.3 & 6.1 | - | - | - | - | C S | - | 2, 4, 6 |
| Solaris 9 & 10 | - | - | - | - | - | C S | 2, 4, 6 |
Notes:
Legend: C = Client; S = Server; - = Not supported |
|||||||
| Web Server | Notes | |||||
|---|---|---|---|---|---|---|
| Microsoft Internet Information Services 5.0 | 5 | |||||
| Microsoft Internet Information Services 6.0 | 1, 5 | |||||
| Microsoft Internet Information Services 7 | 4 | |||||
| Sun ONE Web Server 7.0 | ||||||
| Sun Java System Web Server 6.1 & 7.0 | ||||||
| Apache 1.3 | 2 | |||||
| Apache 2.0.54 - 2.2.x | 2 | |||||
| Tomcat 6.0.21 | 3 | |||||
Notes:
|
||||||
| Browser | O/S | Notes |
|---|---|---|
| Internet Explorer 6, 7, and 8 | Windows | 3, 4 |
| FireFox 2.x, 3.0.x, 3.5, and 3.6.x | Windows & UNIX | 1, 2 |
| Mozilla 1.7 | Windows & UNIX | |
Notes:
|
||
| JRE | Notes |
|---|---|
| Sun 1.6.0 | - |
| Sun 1.5.0 | - |
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 |
| Win 2008 | 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 |
| Win 2008 | 256 MB | P550 | 140 MB |
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.
You must enable Compatibility View in Internet Explorer 8 in order to use it with the Version Manager Web client. To do this:
To use Microsoft Internet Information Services 7.0 with Version Manager, you must configure IIS 7 as follows.
In order to use IIS 7 as your Web server with Version Manager, you MUST select the Role Service ASP.NET and its dependent Role Services while setting up IIS 7. This is a mandatory step to use IIS 7.
For Microsoft Internet Information Services 7.0, the Version Manager Web Server installation does not automatically set the virtual web directories and the ISAPI filter as part of the installation process.
To manually set the virtual web directories and ISAPI filters execute the following steps:
Make Sure that CGI, ISAPI Extensions, and ISAPI Filters are installed from the Application Deployment section while configuring IIS 7.0
From Administrative Tools select Internet Information Services Manager (IIS).
Select the Server Name and click on Sites.
Select the Default Web Site.
Double-click on ISAPI Filters from the Default Web Site/IIS Pane.
From the Actions menu, click Add.
In the Add ISAPI Filters dialog, enter jakarta in the Filter Name field.
Browse to the <VM_Install_Dir>\vm\common\tomcat bin\win32 directory and select the isapi_redirect.dll file from the Executable field and click OK.
Create the vminet_temp virtual web directory:
Right-click Default Web Site and select the Add Virtual Directory option.
In the Add Virtual Directory dialog, enter vminet_temp in the Alias field.
For the physical path browse to <VM_Install_Dir>\vm\inet\temp\html
Click OK.
Create the vminet_images virtual directory:
Right-click Default Web Site and select the Add Virtual Directory option.
In the Add Virtual Directory dialog, enter vminet_images in the Alias field.
For the physical path browse to <VM_Install_Dir>\vm\common\tomcat\webapps\vminet\vminet_images.
Click OK.
Create the vminet_books virtual directory:
Right-click Default Web Site and select the Add Virtual Directory option.
In the Add Virtual Directory dialog, enter vminet_books in the Alias field.
For the physical path browse to <VM_Install_Dir>\books\vm\vmbooks.
Click OK.
Create the jakarta virtual directory:
Right-click Default Web Site and select the Add Virtual Directory option.
In the Add Virtual Directory dialog, enter jakarta in the Alias field.
For the physical path browse to <VM_Install_Dir>\vm\common\tomcat\bin\win32.
Click OK.
Select Jakarta and double click on Handler Mappings.
From the Actions menu click the Edit Features Permissions option.
Select the Execute Option and click OK.
Double click on ISAPI-DLL to open the Edit Module Mapping dialog.
In the Executable field browse to <VM_Install_Dir>\vm\common\tomcat\bin\win32\isapi_redirect.dll.
Click OK.
Click Yes to add this item to ISAPI and CGI Restrictions.
Select the Server and double click on ISAPI and CGI Restrictions.
Make sure that the added item has Allowed under the Restrictions column.
Double-click to edit the description.
Enter Jakarta in the Description field and click OK.
Restart the IIS Server.
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.
Launch the Internet Information Services (IIS) Manager.
Select Web Service Extensions from the left pane.
Select the Extended tab in the right pane.
Click the Add a new Web service extension link in the right pane. The New Web Service Extension dialog box appears.
Enter a name for the extension in the Extension name field.
Click the Add button. The Add file dialog box appears.
Click the Browse button and navigate to the following directory:
Install_Dir\vm\common\tomcat\bin\win32
Select the isapi_redirect.dll and click the Open button.
Click OK on the Add file dialog box.
Select the Set extension status to Allowed checkbox on the New Web Service Extension dialog box.
Click OK. The new extension appears under Web Service Extension with its status set to Allowed.
Open Control Panel | Administrative Tools | Services and Restart IIS Admin Service.
You must log in as an administrator in order to install the Version Manager Web Server to Windows 2008 with Firefox.
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.
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.
Version Manager requires Serena License Manager 2.1.4.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.
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
Version Manager integrates with Serena TeamTrack 6.6.1 and Serena Business Mashups 2009 R1.04, R2, R2.01, and R3.
Version Manager integrates with Serena Tracker 6.6.1. Note, the rich integrations to Eclipse and VisualStudio require TeamTrack or Serena Business Mashups.
Version Manager installs a private copy of Tomcat 6.0.21 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 |
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.
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.
When you install the Version Manager File Server component, you must also select the Web Server Application; otherwise, File Server fails to start properly.
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:
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.
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:
Use /usr/sbin/timeconfig (as root) to set a different time zone. Try one of the GMT time zones with the same offset as that of your time zone. This affects the entire system.
Define the TZ environment variable just in the shell that is used to launch the Version Manager desktop client or the PCLI. For example:
export TZ=GMT-9
To prevent an accidental hang by users who forget to set this variable, you could add the following as the second line in the file VM_Install_Dir/vm/linux/bin/pvcsvmdmn:
TZ=GMT-9; export TZ
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:
Launch the Version Manager Application Server Configuration utility from the Serena submenu of the Start menu.
Click the Remove NT Service button.
Restart the computer.
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.
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
If the project databases were accessed using a Version Manager File Server prior to this upgrade, you must reconfigure the File Server path map definitions BEFORE doing the above step. If you are upgrading from a version prior to 8.0.0.3, then this must be done manually.
If you are upgrading from 8.0.0.3, or above, the server-config.wsdd can be restored to the Install_Dir\vm\common\tomcat\webapps\serenafs\WEB-INF\ directory in the newly installed location. This will preserve the previous file server definitions.
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.
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\serenafs\WEB-INF\server-config.wsdd
In order to use the integration on Windows (except 2000, 2003, & XP), 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.
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.
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.
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.
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.
This is not a supported configuration.
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.
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.
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.
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:
vmreg [server] copies license information from $PVCS_BINDIR/license.ini to .islvrc. If the server argument is present, the script takes the server name from the argument rather than from the value in $PVCS_BINDIR/license.ini. Users execute this command from the command line.
vmreg -t copies license information from $PVCS_BINDIR/license.ini to .islvrc only if no server definition exists in .islvrc. The PCLI and desktop-client launchers execute this command automatically at startup.
vmreg -m <server> updates $PVCS_BINDIR/license.ini with the name of the server and copies that data to .islvrc. The Version Manager installation script and Administrators execute this command.
vmreg -h provides usage information.
vmreg -v provides version information.
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.
Some UNIX platforms require patches before they will run the JRE as used by Version Manager. See http://knowledgebase.serena.com/InfoCenter/index?page=content&id=S137614. Else, see Serena support at http://support.serena.com and use the Advanced Search page to search for S137614.
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 |
The Version Manager IDE client supports the following development environments:
IMPORTANT!
Eclipse/RAD: Before enhancing your installation of Eclipse/RAD with additional Eclipse framework applications, first install Eclipse/RAD and the Version Manager Rich IDE Plug-in and ensure that it works correctly. If you experience a problem after installing additional Eclipse framework applications, you will know it is an issue with the additional software rather than with Eclipse itself or the integration between Version Manager and Eclipse.
COM/Web Integrations: See the Supported Web Servers table for the versions of Microsoft Internet Information Services supported by the IDE COM/Web integration.
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.
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
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.
Using Single Sign On with versions of Eclipse prior to 3.5 may still require that you login to TeamTrack when opening an issue from inside Eclipse RIDE.
The Serena Issues view will incorrectly display Japanese characters unless it is used with TeamTrack 6.3 or newer.
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.
WARNING! Enabling the Server-Side Processing feature in Version Manager 8.4.0.0 RIDE clients can cause instability in Version Manager File Servers and Web Servers (regardless of version). This feature is installed disabled by default. However, it can still be enabled from inside the RIDE client. PLEASE DO NOT ENABLE IT.
This issue was discovered late in our testing process when it was too late to fix without substantially impacting the release date. Rather than impact all customers, we decided to release with this feature disabled by default. We are working on a follow up release/patch that will fix this issue. We apologize for the inconvenience.
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:
Run the Windows Add or Remove Programs utility.
Select and uninstall any Version Manager 8.1.4.x patch you have already installed.
Select the Serena PVCS Version Manager 8.2 installation and click the Change/Remove button.
Select the Modify option and click the Next button.
Clear the checkboxes next to the Eclipse plug-ins and click the Next button.
Click the Finish button.
Back at the Add or Remove Programs utility, select the Serena PVCS Version Manager 8.2 installation and click the Change/Remove button.
Check the checkboxes next to the desired Eclipse plug-ins and click the Next button.
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.
Click the Next button.
Click the Finish button.
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.
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:
Exit any open IDEs.
Select TrackerLink from the Serena Tracker program group in your Start menu. The Serena TrackerLink dialog box appears.
Select Serena PVCS Version Manager from the SCC Provider drop-down list.
Click the Activate button. The change will take effect the next time you start your IDE.
To use the IDE client without TrackerLink:
Exit any open IDEs.
Select Serena | Serena PVCS Version Manager | Version Manager IDE Client | Select Serena Provider from the Windows Start menu. The Select Serena Provider dialog box appears.
Select Serena PVCS Version Manager.
Click OK. The change will take effect the next time you start your IDE.
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.
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.
Workaround: Reboot to update your system's path information.
|
Part 4: Version Manager Web Client |
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.
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\serenafs\WEB-INF\server-config.wsdd
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:
In <Windows Dir>\Downloaded Program Files, right-click the VM I-Net applet, and remove it.
Remove <Windows System Dir>\vmi660.dll.
Remove <Windows Dir>\Java\lib\vmi660.zip.
In the registry editor, remove the following entry:
HKEY_CLASSES_ROOT\CLSID\{CCF028C4-4631-11D3-90BD-00A0C9B727E1}
In <Windows Dir>\Downloaded Program Files, right-click the VM I-Net applet, and remove it.
Remove <Windows System Dir>\vmi660.dll.
Remove <Windows Dir>\Java\lib\vmi660.jar.
In the registry editor, remove the following entry:
HKEY_CLASSES_ROOT\CLSID\{CCF028C4-4631-11D3-90BD-00A0C9B727E1}
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.
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.
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:
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
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
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
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.
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.
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.
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.
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:
Otherwise, you cannot access /vminet.html or (when File Server is installed) /serenafs/Admin.
This is not a supported configuration.
To install the Version Manager Web Client on Windows 2000 Server machines, you must have local Administrator privileges.
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.
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 &
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
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:
If you don't already have it, download and install JDK 1.4.2x or 1.5x.
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.
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:
JDK_Install_Dir equals the location of your 1.4.2x or 1.5x JDK installation.
Certificate_File equals the path and name of your SSL certificate file.
Install_Dir equals the location of your Version Manager web server installation.
When prompted, enter the password for the JRE keystore. The default password is changeit.
Internet Explorer 8 support is provided in single process mode. To enable single process mode, create the following registry entry:
HKCU\Software\Microsoft\Internet Explorer\Main - TabProcGrowth
And set the value of the dword to: 1
Once installation of the Version Manager Web Client is complete, you can delete the Serena PVCS Version Manager MSI file 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.
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.
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.
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 |
Version Manager works with the following WebDAV clients:
NOTE:
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.
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.
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 |
Microsoft PowerPoint is no longer supported by Serena Meritage.
Serena no longer supports Meritage. It is included in Version Manager 8.4, but no defect fixes or enhancements will be made to this feature.
Part 7: Copyright/Disclaimers/Support |
To contact Serena support, please log in at support.serena.com.
Serena recognizes that virtualization technology provides significant utility and value to our customers. As such, Serena conducts functional testing and certifies our products using virtualization technology in addition to native environments. While Serena expects that our products will function properly when running on supported platforms in a virtualized environment as well as a native environment, there may be functional and performance limitations. Serena will not require that customers recreate and troubleshoot every issue in a non-virtualized environment, however there may be circumstances in which such action may be required. Serena will only make this request when there is reason to believe that the virtualized environment is a contributing factor to the issue. If the issue cannot be reproduced in a supported non-virtualized environment, customers will need to refer their issues to their virtualization vendor.
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.
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.
End Readme
Copyright © 2003–2010 Serena Software, Inc. All rights reserved.