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.
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: Copyright/Disclaimers/Support
Part 1: Supported Platforms / System Requirements |
You can download a detailed Supported Platform List from this page.
| O/S | 32-Bit CPU's | 64-Bit CPU's | Notes | ||||
|---|---|---|---|---|---|---|---|
| Pentium Class | AMD64 (x86_64) |
Itanium 2 (McKinley) |
PA-RISC | PPC64 | SPARCv9 | ||
| Windows 7 Ultimate/Enterprise/Professional SP1 | C | C | - | - | - | - | |
| Windows 8 & 8.1 Enterprise/Professional | C | C | - | - | - | - | |
| Windows 10 Enterprise/Professional | C | C | - | - | - | - | |
| Windows 2008 Server R2 SP1 | - | C S | - | - | - | - | |
| Windows 2012 Server | - | C S | - | - | - | - | |
| Windows 2012 R2 Server | - | C S | - | - | - | - | |
| Red Hat Enterprise Linux 6.x & 7.x | - | C S | - | - | - | - | 1, 2 |
| SUSE Linux Enterprise Server 11.x & 12 | - | C S | - | - | - | - | 1, 2 |
| HP-UX 11.31 | - | - | C S | - | - | - | 1, 2 |
| AIX 6.1 & 7.x | - | - | - | - | C S | - | 1, 2 |
| Solaris 10 Update 9+ & 11 | - | - | - | - | - | C S | 1, 2 |
Notes:
Legend: C = Client; S = Server; - = Not supported |
|||||||
Optionally, you may use a supported third-party web server to access the servlets hosted on the Version Manager Web Server. This may be convenient if you have already configured a third-party web server and wish to use the existing front-end and HTTPS certificates with Version Manager.
NOTE
Version Manager does not require a third-party web server. By default, the Tomcat-based Version Manager Web Server will stand on its own.
A third-party web server does NOT take the place of Version Manager’s Tomcat implementation, but rather runs in addition to it.
| Web Server | Notes | |||||
|---|---|---|---|---|---|---|
| Microsoft Internet Information Services (IIS) 7.x | 3 | |||||
| Microsoft Internet Information Services (IIS) 8.x | ||||||
| Apache 2.2.x | 1 | |||||
| Apache 2.4.x | 1 | |||||
| Tomcat 7.0.75 | 2 | |||||
Notes:
|
||||||
| Browser | O/S | Notes |
|---|---|---|
| Mozilla Firefox 10 and above (unless noted otherwise on the SupportLine Site) |
Windows & UNIX/Linux | 1 |
| Internet Explorer 10 & 11 |
Windows | 2, 3 |
Notes:
|
||
| JRE | Notes |
|---|---|
| Oracle Sun 1.8.0 | |
| Oracle Sun 1.7.0 | 1 |
Notes:
|
|
Large projects can exceed the memory allocated for Java in a variety of situations and with a variety of Version Manager interfaces. See "Out of Memory Error" or General Failure Operating on Large Projects in the Usage Cautions readme (usage_cautions.html) for information on setting the Java Heap Size for Version Manager clients.
In addition to Operating System requirements, the minimum system requirements are:
| Client Systems – Minimum | |||
|---|---|---|---|
| Platform | Memory | CPU | Disk Space |
| Windows Client | 128 MB | P400 | 140 MB |
| Windows 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 |
| Windows Client | 256 MB | P550 | 140 MB |
| Windows Server | 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.
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.
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, or use the built-in Tomcat 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/VMverNum_inst directory (where verNum is the version number of the Version Manager release).
The Version Manager Difference/Merge tool requires openmotif libraries. If they are not installed, you will get an error similar to:
mgdiff: error while loading shared libraries: libXm.so.4: cannot open shared object file: No such file or directory.
Ensure that you have the libXm.so.4 library installed to your system along with any dependent libraries. This is typically accomplished by installing the package openmotif.x86_64.
Version Manager 64-bit requires the use of the 64-bit version of ActiveClient. When using the SCC IDE integration, Version Manager runs in 32-bit mode (as SCC itself is 32-bit only), requiring the use of the 32-bit components of ActivClient as well. These typically get installed automatically when installing the 64-bit version of ActivClient.
NOTES
In the file VM_Install_Dir\vm\common\pvcsprop\pvcs\vm\sso\card.config, the directive library64 should point to the 64-bit version of acpkcs211.dll and the directive library32 should point to the 32-bit version of this library (see KB doc S138646). If ActivClient is installed at the time Version Manager is installed, the paths to these libraries will automatically be added to card.config.
ActivClient 7 is supported as of version 7.0.2.408.
On Linux, ActiveClient 3.0 is supported.
Version Manager requires Serena License Manager 2.2.0 or newer.
Version Manager integrates with SBM 10.1.x and SBM 11.x
The Source Bridge integration that is used by the Version Manager Desktop Client GUI and SCC IDE integrations is now parts of the Version Manager installer.
Version Manager installs a private copy of Apache Tomcat in support of the Version Manager File Server, VM I-Net Web Client Server, WebDAV Server, and SSO authentication server. 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, 8443, and 8444).
Version Manager installs Apache Axis2 version 1.5.5.
Part 2: Version Manager CLI, Desktop Client, File Server, and PCLI |
Before attempting to install Version Manager, review the Serena PVCS Version Manager Installation Guide for general information as well as specific scenarios that may apply to you.
This section briefly describes the differences between the release types. Each release type has a different number of digits in its release number:
X.X = Full Release: This is intended to be installed to a clean system (any previous Version Manager install should be uninstalled). In addition to newly developed features, enhancements, and fixes, it contains the enhancements and fixes of all the Patches and Hotfixes released since the previous full release.
TIP You can backup and restore certain configuration settings to ease setup of a full release. See the Serena PVCS Version Manager Installation Guide.
X.X.X = Patch: This must be installed to a system that already has a Full Release installed to it. In addition to newly developed enhancements and fixes, it contains the fixes of all the Hotfixes released since the previous patch.
X.X.X.X = Hotfix: This must be installed to a system that already has a Full Release installed to it. It contains a fix for a specific issue, or small group of closely related issues.
IMPORTANT! Download and review the latest edition of the Readme and the Serena PVCS Version Manager Installation Guide before installing.
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.
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.
This is not a supported configuration.
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.
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 KB doc S124060 for a list of Operating System patches and pre-installed package requirements for UNIX & Linux.
Part 3: Version Manager IDE Client |
The Version Manager IDE client supports the following development environments:
| IDE | SCC | RIDE | Notes | |
|---|---|---|---|---|
| Eclipse 3.7, 4.2, 4.3, 4.4, 4.5, 4.6 | X | X | 1 | |
| IBM Rational Application Developer 8.5, 9.0 | X | X | 1 | |
| Microsoft Visual Studio 2010 (SP1), 2012 (SP4), 2013, 2015 | X | X | ||
| Sybase PowerBuilder 12.5, 12.6 (Classic) | X | 2 | ||
NOTES
|
||||
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.
The Linux version of the rich integration to Eclipse does not work correctly if the SBM 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 SBM/IIS server.
To use the SSO login source, the JDK used by Eclipse RIDE needs to be Java 8-based. Upgrade the JDK as needed.
Before attempting to install Version Manager, review the Serena PVCS Version Manager Installation Guide for general information as well as specific scenarios that may apply to you.
To use a new version of the Version Manager IDE client, you must uninstall any previous version of the IDE client on your system before installing the new version. If you wish to use an older version of the IDE client once the new version is installed, you must uninstall it before installing the older software.
If you currently use TrackerLink with SCC IDEs and wish to use Source Bridge (SBM) instead, change your SCC provider from TrackerLink to Version Manager before installing Source Bridge. Source Bridge 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 Source Bridge while TrackerLink is still set as the SCC provider, Source Bridge 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 Source Bridge dialog box. For details, see the "About Setting Up Source Bridge" 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 |
Before attempting to install Version Manager, review the Serena PVCS Version Manager Installation Guide for general information as well as specific scenarios that may apply to you.
To access the web client, you must disable the Protected Mode option in Internet Explorer on newer versions of Windows. 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.
This is not a supported configuration.
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".
After you delete the file, you can still use Add/Remove Programs to modify or remove Version Manager.
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:
Before attempting to install Version Manager, review the Serena PVCS Version Manager Installation Guide for general information as well as specific scenarios that may apply to you.
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 6: Copyright/Disclaimers/Support |
To obtain product support, please log in at supportline.microfocus.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. All 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.
Portions © Copyright Digia Plc. All Rights Reserved.
End Readme
Copyright © 2003–2017 Serena Software, Inc. All rights reserved.