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 (installation_info.html)
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 (this file)
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 in each release of Version Manager. Look here to see what defects have been fixed since you last upgraded.
To view the Master License Agreement, see MasterLicenseAgreement.pdf.
This readme file is organized into distinct parts. Please read the parts that correspond to the Version Manager components you are using.
Part 1: Version Manager CLI, Desktop Client, and PCLI
Part 2: Version Manager IDE Client
Part 3: Version Manager Web Client
Part 4: Version Manager WebDAV Server
Part 5: Serena ChangeMan Meritage
Part 6: Copyright/Disclaimers/Support
|
Part 1: Version Manager CLI, Desktop Client, and PCLI |
In Mover 2, you deploy "packages" rather than "deploy maps". As a result, the deploy command usage statement (output by the -h option) should refer to a "package id" rather than a "deploy map id".
As of Version Manager 6.8, the "Create Archive" privilege has been renamed to "Create Archive and Workfile" because this privilege now allows the user to add workfiles. In previous releases the "Create Archive" privilege had to be combined with the "Add or Remove Versioned Files" privilege in order to allow the same behavior with respect to adding workfiles. This changed behavior makes it possible to allow users to add workfiles without also allowing them to delete files.
Version Manager Administrators should be aware that users who may have had only the "Create Archive" privilege can now add workfiles. The behavior of the "Add or Remove Versioned Files" privilege has not changed.
The output messaging behavior in the Command-line Interface (CLI) has been changed so that all error messages are directed to stderr and all other types of messages are directed to stdout. This change provides for more consistent behavior, but may have an impact on existing scripts.
The default refresh interval is now 30 seconds, which means that changes made in one interface will be visible in another interface (or another instance) after 30 seconds. To refresh immediately from the Version Manager desktop client, choose View | Refresh from the Menu or press CTRL+R.
The Show History Report contains colons to use when you filter for reports on archives. The colons are used to separate the "owner", "author", and "locker" filter criteria. If you use scripts to parse the output of Show History Archive reports, you may need to update the scripts.
The Serena ChangeMan Version Manager Administrator's Guide indicates that multiple setup files can be specified with the runvmcm command. This does not work correctly at this time. If you specify more than one setup file, only the last one will be used.
To workaround this issue, define multiple transfers in a single setup file. See "Creating a Setup File" in the Collage chapter of the Serena ChangeMan Version Manager Administrator's Guide.
The output of the CLI and PCLI vlog commands have been changed to include the Split mode of an archive. You may need to update scripts that parse the output of these commands.
Paths specified in event triggers or custom tool definitions must be accessible by the client operating system. If you migrate an existing Project Database for use with a file server, you may need to change the definitions so that paths remain accessible to the OS.
For security reasons, only Version Manager executables can access paths served by the Version Manager File Server. If the directories mapped by the file server contain files other than archives and Project Database files, and if third-party applications need to access these files (or if the files are third-party applications), you need to provide another form of access for these files (such as a shared directory or a mapped drive).
NOTE: Any Version Manager executable used in your event trigger will work fine without a shared directory or mapped drive, as long as the executable itself--and any script containing it--can be found using regular (OS) file access.
If you issue a CLI command against a file server path map that has security enabled but the user ID that you pass to that command using ‑iduser:password is not authorized, the error message that you receive refers to the HOST user ID as being invalid rather than the incorrect ID that you entered.
The output from the -h option for CLI commands always shows options as all-uppercase; however, many options do not work if you use uppercase letters. To be safe, always use lowercase letters for CLI options.
If a user performs a makedb operation on a path for which the user is not authorized, two messages appear in the log:
Access to writing utility by user userName is granted
Error during authentication.
User userName is not authorized for path path.
The first message should appear only if the second message does not.
If a makedb operation fails because the destination is on a file server that disallows utilities, the user sees the confusing error text, "makedb: cannot create semaphore path."
If a default version label is defined for the Project Database, the Show History report does not work when you perform a Check tips against version/revision operation.
If you run a journal report from a UNIX client against a Version Manager File Server, no results are returned. To work around this issue, run the journal report from a Windows client or use the CLI vjournal command.
Simultaneous use of the desktop client (Version Manager or Tracker) and a web client (Version Manager, Tracker, or TeamTrack) consumes two licenses if access is via a proxy server. The desktop application will license to the client hostname and the web servers will license to the proxy server's hostname, so two licences are consumed.
Problem:
Deploy a promotion model at the root level of a Project Database (PDB).
Create a sub-project with a configuration file.
In the sub-project's configuration file, declare an additional promotion group below the main promotion model's bottom level.
Add a workfile to the sub-project.
Place the desktop client in recursive mode (View | Filter | Recursive).
Select the PDB level. The sub-project and versioned file appear in the right pane.
Select the versioned file directly in the right pane.
Right-click and select Check Out.
Open the drop-down list.
It shows the original bottom-level promotion group as defined by the top-level configuration.
Workaround:
After placing the desktop client in recursive mode (step 5 above), select the PDB level. The sub-project and versioned file appear in the right pane.
This time, select the sub-project.
Select the versioned file in the right pane.
Right-click and select Check Out.
Open the drop-down list.
This time, it displays the new bottom-level promotion group as defined by the sub-project configuration.
To integrate JBuilderX with Version Manager, perform the following steps:
Install JBuilderX.
Copy the merant_jb10_vm8.jar file into the JBuilder_Install_Dir/lib/ext/ directory.
Put the location of JSCC.dll in your PATH environment variable.
Install Version Manager with the SCC/COM component.
Add "Merant Version Manager" to HKLM\Software\SourceCodeControlProvider\InstalledSccProviders. For example:
Merant Version Manager=SOFTWARE\Merant\Integrations\SCC
Restart JBuilderX.
Be default, keyword expansion should be enabled for non-binary Visual Studio .NET files; however, *.cs files have not yet been added to this list. An administrator can configure projects to expand keywords in this file type. For details, see the Serena ChangeMan Version Manager Administrator's Guide.
Administrators see an error message when logging out of the File Server if they log in using the old URL (merantfs rather than serenafs).
The error is harmless.
If you open a project database (PDB) from a File Server and specify a configuration file with a name that doesn't have a ".cfg" extension, Version Manager does not recognize the configuration file.
If you set up TrackerLink to require associations for checkout, you should also require associations for check-in. Otherwise, the revision number of the checked in revision will not appear in the Tracker issue, and the issue information will not be added to the revision description. You should also select the "Clean up associations on undo checkout" check box from the Serena TrackerLink Settings dialog box (Admin | TrackerLink Settings).
If associations are not required on check-in, you can still complete associations during check-in by clicking the Associate Issues button on the Check In dialog box and clicking OK.
Chmod.exe is no longer part of the Version Manager installation. For similar functionality, use the MSDOS Attrib command.
To avoid font problems in the desktop client on UNIX systems, set the following environment variable:
LC_CTYPE=en_US.ISO8859-15
Attempting to change the case of a file name on a case-insensitive File Server fails to rename the archive.
In some situations, the Helper application may not start correctly unless you enter a full path.
Under the View | Options Application tab, you should enter full paths for the following applications:
The editor that Version Manager will use to display and edit your workfiles and to display reports
Adobe Acrobat Reader, used for viewing online manuals
An HTML browser, used for displaying reports and online help
When you select a date range using the Calendar feature, Version Manager may quit unexpectedly. This is because of a known defect in Solaris 8 that is fixed in Solaris 9. Sun has not published a plan to patch Solaris 8 for this known issue. To work around this issue, enter the date ranges directly instead of selecting them from the calendar.
Using Exceed 7.1 in Multiple Window mode causes inconsistent behavior in Version Manager when you click tabs in a dialog box with multiple tabs. The dialog box may move to the upper left corner of the screen. This problem does not happen in Single Window Mode.
Earlier versions of Exceed may cause problems with random shut downs and other unexpected behavior. This is an Exceed issue. Upgrading to Exceed 7.1 should resolve these issues.
When you check out or lock files in a project that has multiple lowest-level promotion groups, the system may hang. This problem occurs sporadically on under-powered or overworked systems. Try closing other open applications to free more memory and CPU resources.
See "Setting Up Your UNIX Environment for Version Manager" in Chapter 4 of the Serena ChangeMan Version Manager Installation Guide.
When referencing a variable's elements in PCLI, do not use leading or trailing spaces. For example:
$FOO[ 3 ] should be changed to $FOO[3]
You cannot use wildcard characters at the top level of workspace paths. For example, if you enter the following, the PCLI does not list the names of any public or private workspaces:
pcli list /@/*
However, this command lists all private workspaces of AdamJ, provided you are logged in to the project database as AdamJ:
pcli list /@/AdamJ/*
The following command lists all the public workspaces:
pcli list /@/Public/*
When you are being prompted to enter a description by the AddFiles or Put command, you cannot use the EndOfFile (EOF) character of the operating system you are running on (UNIX: CTRL+D, Windows: CTRL+Z). When prompted, enter a single period (.) on a line by itself to end the description. Windows users can also press CTRL+D.
Note that this is different from the old-style command-line interface (CLI) that allows you to enter the EOF character to end the description.
On HP-UX systems only, in certain situations, running a complex PCLI script (or many java processes) may result in a message similar to: "You have encountered an out of memory error. Please restart Version Manager and try the operation again. If you continue to have problems, contact your Version Manager administrator for further assistance. java.lang.OutOfMemoryError: unable to create new native thread...". Additional Java errors may appear after this message.
HP has a tool called "HPjconfig" that may remedy this situation. It is designed to tune HP-UX to use Java applications. Go to http://www.hp.com and search for "HPjconfig". Note: Changes made by HPjconfig will require modifications to the kernel.
If you specify a revision number during check-in, you are prompted to confirm the action. Use the run -y put command in your scripts to automatically answer "Yes" to this prompt.
Running Deploy from the command line fails if the Version Manager username or password contains spaces. The problem does not occur when you perform the deploy operation directly from Mover.
The Version Manager Conversion Utility for SourceSafe can convert your existing SourceSafe databases into Version Manager project databases.
Please refer to the Serena ChangeMan Version Manager Administrator's Guide for information about how to use this utility.
The Version Manager help will not launch on Internet Explorer if IE is using Sun's 1.4.0x JRE. Use 1.4.2x or 1.5x instead.
If you resize the Netscape browser window, the TOC pane of the help may not resize correctly. To reload the TOC into the resized pane, click the Hide Navigation link, then click the Show Navigation link.
When you view the online help on Windows XP using Microsoft IE 6.0 with Sun's JVM, the navigation pane in the online help comes up blank. You can work around this by disabling Sun's JVM and using the Microsoft JVM to view the help.
On Solaris systems, invoking the navigation pane of the Version Manager help may crash the Netscape browser. You can work around this by using the Mozilla browser.
|
Part 2: Version Manager IDE Client |
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 ChangeMan Version Manager Administrator's Guide.
If you close one project and open another without restarting ColdFusion, Pulse may display redundant source control activity information.
Pulse may display messages containing the text "pvcs.vm.param.LogInfo". Disregard these messages.
When you perform a get or when you undo checkout of a file or a unit, Rational Rose may display a Version Control Integration message, and the operation may fail. See the sections below for information on successfully performing a get or undoing checkout.
To ensure that you can successfully get a file or unit, do one of the following before getting:
You can now get the file.
If a Version Control Integration message appears during undo checkout, the following has occurred:
To complete undo checkout, you can get the latest revision of the file by write-protecting it and getting it as explained in the section above.
To avoid this error on future undo checkout operations, write-protect the model file or unit before attempting the operation.
In most SCC IDEs, you can submit issues and switch Tracker projects from the TrackerLink Admin dialog box. In most cases, this dialog box appears when you choose to run the external source control application.
Rational Rose, however, does not display the Tracker Admin dialog box. When you select Tools | Version Control | Start Version Control Explorer, the TrackerLink Settings dialog box appears instead.
Although there is currently no way to access the TrackerLink Admin dialog box from within Rational Rose, you can still submit issues and switch projects. See the next two sections for more information.
There are two ways to submit issues with Rational Rose:
Complete the procedure below if you are using TrackerLink with Rational Rose and wish to switch to a different Tracker project:
Select Tools | Version Control | Start Version Control Explorer. The Serena TrackerLink Settings dialog box appears.
Deselect the Auto-login to project check box. Once this option is deselected, you will be prompted to log in to a Tracker project every time you start Rational Rose.
Exit and restart Rational Rose. The Tracker login dialog box appears.
Complete the login process.
You can configure TrackerLink to "clean up" records from files that have been unlocked. Cleaning up removes the association with the file. If you are working with TrackerLink 6.5 and you unlock an unchanged file that you have associated with an issue, the file remains associated with the issue. This does not occur with TrackerLink 6.6 or later.
When you add a new VisualAge for Java project to source control, a series of Login dialog boxes may appear if all of the following are true:
An access control database is associated with the project database, and security is in effect.
You create the new project as a subproject under existing Version Manager projects.
You may be prompted to log in to each level of the project structure twice. This behavior occurs only when you add a project to source control.
Visual Basic may prompt you to confirm the check-in location even though you are checking a file in from the same location to which you checked it out. This occurs when the case in the filename is changed during the check-in process. When prompted to check in anyway, select Yes. The file will be properly checked in to the correct location.
Some IDEs allow you to get an entire project from source control, which copies all files in the Version Manager project to the location of your choice. You can specify any workfile location except a root drive (such as C:\).
The About tab of the Options dialog box lists the Version Manager modules and their version numbers. The IFC_COM.DLL may be listed as "not loaded" since the Options dialog box is part of the SCC interface, which does not use the IFC_COM.DLL.
When you add a C# ASP project to source control, you may receive an error stating that the *.csproj.vcpscc file is not under source control. This may be followed by another error stating that a writable ~sak*.tmp (or similarly named) file already exists.
Click OK to dismiss these dialog boxes. They are a result of the IDE testing the source control connection and do not reflect an actual problem with your project.
FrontPage allows you to view a read-only copy of a file that is currently checked out by another user. When you close the file, it may appear to lose its source control status in the FrontPage project explorer. Double-click the file to refresh its status.
If you try to delete a file that is checked out by another user, you receive an error message stating that the file is checked out. The message should include the ID of the locker, but it does not.
If you receive an error similar to "Ordinal 58 not found at ATL.DLL" when launching an Eclipse-based IDE, you may need to update your ATL.DLL file. Check the ATL.DLL file in the system32 directory of your Windows installation. The ATL.DLL file should be about 60 KB in size. If it is much smaller, the installation of another program has overwritten the file with an outdated version. Obtain the current version from Microsoft or from another computer that has the proper version installed.
For information on Microsoft DLLs, see support.microsoft.com.
On systems that are not set to the en_US locale, "Resource Key" errors occur in the serena_java.log file in your Serena installation directory. These errors do not mean that features are not working correctly; however, to ensure that the log remains readable, you can edit the log to remove these error messages.
In the Compare Revisions dialog box, the "copy all non-conflicting changes from right to left" toolbar button does not work.
Workaround: Click the "three-way compare" toolbar button.
Update your Windows shortcut (target value) to use the heap size of your choosing. For example, if the location of the Eclipse executable is D:\eclipse3.0.1\eclipse\eclipse.exe and you want to specify a heap size of 512m, enter the following command:
D:\eclipse3.0.1\eclipse\eclipse.exe -vmargs -Xmx512m
Choose a value that is suitable for the amount of memory on your machine.
One action that causes this is double-clicking the Name column.
In the Version Manager revision pane, end-of-line characters are removed so that the full comment is visible; however, in the History View in Visual Studio .Net, the comment column shows only the first line of the comment.
This applies to the context menu only; Undo Checkout works properly from the toolbar.
Do not add CAB projects from Version Manager to a solution that is already under source control.
CAB projects in .NET do not support a context menu; however, all operations are available from the main menu.
From the Compare Workspaces view, you cannot commit a CAB project that has not been saved.
If you are unable to operate on a project that has been added through a synchronize operation, close the project and reopen it from source control.
If you move a managed subfolder containing a managed file between two controlled projects and then perform a Compare Workspaces operation, the first project still contains the folder, and the file's status is Local Modify. The second project does not show the moved folder.
Workaround: To recover after performing a move across projects, re-populate the workspace from the repository.
|
Part 3: Version Manager Web Client |
When viewing a file in the revision pane, you can refresh the contents of its parent project by pressing CTRL and clicking the project in the project pane. You can also click the Return to Contents of Project link in the revision pane.
When you click the browse button in the Add Workfiles dialog box, the resulting directory selection dialog box sometimes does not function properly on UNIX.
The workaround is to restart the browser.
One way in which the web client will report communication difficulties with the web server is by displaying IO error messages (such as "java.io.IOException" or "pvcs.io.CommException").
If an Access Control Database does not exist for a project database, you cannot change your Version Manager web client password to log in to that project database. To fix this problem, create a new ACDB for the project database using the Version Manager desktop. Uncheck the "Enable access control database security" box. You can now change your password in the Version Manager web client.
NOTE: Creating the new ACDB does not affect the users' existing permissions, since the ACDB is disabled.
Netscape has a known problem on UNIX of not running an applet until the mouse is moved. If the project pane is not drawing, and there is no error in Netscape's status pane, try moving the mouse. You may also see this when the Results dialog box appears, but remains gray.
The Licenses tab of the Version Manager Web Server Application Configuration utility displays multi-byte and high-ASCII characters as a string of numbers and letters. This behavior will be addressed in a future release.
On HP-UX clients, archive operations (get, checkout, and so forth) may fail resulting in a blank Results dialog box and the following error in the Java console: java.lang.UnsatisfiedLinkError: Netscape_Dir/java/bin/libxfile_jri.sl. To avoid this behavior, run the chmod +x command on the libxfile_jri.sl file, which is located in the java/bin directory of your Netscape browser installation.
Do not use Netscape 7 with Exceed.
This is a display issue only; the archive data is correct. If you perform a lock operation on the file and then refresh the display, the dates appear correctly.
If you get a "Certificate not verified" error when logging in to the web client, do the following:
Close the browser and reopen it.
Bring up the Login page, but do not log in. After a moment or two, a Security Warning dialog box appears.
Click the Always button on the Security Warning dialog box.
Now log in to the web client.
The browse feature may quit working when you switch to a project database on a different server. This can occur with any browser that uses the Sun Java plugin. Netscape and Mozillia use the Sun Java plugin, and Internet Explorer can be configured to use it, also. To switch to a project on another server, exit the browser and restart it.
When you upgrade to Windows XP Service Pack 2, default security settings are changed. These changes can cause messages to appear that prompt you to explicitly allow the Help system to be viewed.
To allow the Help system to be viewed wihout seeing warnings, perform the following steps:
Open Internet Explorer.
Go to Tools | Internet Options.
Click the Advanced tab.
Scroll down to the Security section.
Select the Allow active content to run in files on My Computer check box.
Click OK.
If you resize the Netscape browser window, the TOC pane of the help may not resize correctly. To reload the TOC into the resized pane, click the Hide Navigation link, then click the Show Navigation link.
|
Part 4: Version Manager WebDAV Server |
See the Usage Cautions file.
|
Part 5: Serena ChangeMan Meritage |
Please refer to KnowledgeBase article 5001075.
In Office 2000, the "My Meritage" icon does not appear in the left pane of the Open File dialog box.
If you are using version 8.0.0.0 of WebDAV Server and you check in a file from outside of Meritage using the Keep revision locked option, you will not see the new version of the file from within Meritage until the file is checked in or unlocked.
Please refer to KnowledgeBase article 5001095.
Part 6: Copyright/Disclaimers/Support |
To contact Serena support, please log in at support.serena.com.
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 ChangeMan 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.
End Readme
Copyright © 2003–2005 Serena Software, Inc. All rights reserved.
$Revision: 1.2 $