This file contains information on installing and using the current release of Version Manager. This file contains information not included in the Version Manager manuals and online help. Additional information is available in KnowledgeBase articles available via your browser.
For a list of the defects fixed since an earlier release of Version Manager, see release_notesvm.html.
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 1: Version Manager CLI, Desktop Client, and PCLI |
Version Manager for Windows is supported on:
Version Manager for UNIX is supported on:
Version Manager for Windows supports TrackerLink in Serena Tracker versions 6.5.00 (Build 506) or newer. However, Tracker 6.6.00 or newer is required for the "Clean up associations on undo checkout" feature.
If you plan to install Version Manager 8.1 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
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
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 ChangeMan 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 ChangeMan Version Manager Administrator's Guide.
This error 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 you use the Version Manager Web Server, File Server, or WebDAV Server, you must stop the server before upgrading. See the Serena ChangeMan 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.
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 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.
See the topic with this name in Part 2: Version Manager IDE Client, below.
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 2003 Server | 128 MB | P400 | 140 MB |
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 2003 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.
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.
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.
In addition to Operating System requirements, the minimum system requirements are:
| Client Systems – Minimum | ||
|---|---|---|
| Platform | Memory | Disk Space |
| Solaris | 64 MB | 112 MB |
| HP-UX | 64 MB | 141 MB |
| AIX | 64 MB | 65 MB |
| Red Hat Linux | 64 MB | 117 MB |
| SuSE | 64 MB | 117 MB |
The recommended system requirements are:
| Client Systems – Recommended | ||
|---|---|---|
| Platform | Memory | Disk Space |
| Solaris | 128 MB | 112 MB |
| HP-UX | 128 MB | 141 MB |
| AIX | 128 MB | 65 MB |
| Red Hat Linux | 128 MB | 117 MB |
| SuSE | 128 MB | 117 MB |
NOTE: Memory requirements are per session of Version Manager.
Memory requirements for the server depend upon how many users access the server at the same time and how many daemon processes are running (by default, 5 to 20 daemons will be 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.
Some UNIX platforms require patches before they will run the JRE (version 1.4) as used by Version Manager. See Serena support at support.serena.com for more information (KnowledgeBase Document 70396).
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.
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.
The Serena ChangeMan Builder integration to Version Manager may fail. To avoid this issue, make sure you have the latest Serena ChangeMan Builder patch. You can obtain the patch from support.serena.com. If your Serena ChangeMan Builder CD is labeled MB 8010, it already contains the fix. CDs labeled Merant Build 8010 require the patch.
If you use symbolic links to specify paths in Version Manager commands, the command will take longer to complete. To speed execution, specify full paths rather than symbolic links, or add the fully qualified paths of Version Manager commands to your environment.
If you use the Serena ChangeMan Version Manager File Server and you run real-time antivirus software on your clients, you may experience degraded performance. This is because the antivirus software scans the Version Manager file cache every time the cache is updated. To avoid this performance penalty, exclude the cache directory from real-time virus scans.
By default, the file cache is in a directory named pvcsfs under your system's temporary directory (as specified by the TMP or TEMP environment variable). You can set a different location for the cache by defining a path in either the FS_TMP or FS_TEMP environment variable.
For more information on antivirus-related performance improvements, see Serena KnowldegeBase article 70042. This article applies to both clients and file servers.
If you assign a version label that matches a revision number to a different revision, you cannot access the revision with the matching number using the desktop client, the web client, or the PCLI.
You can avoid this problem in two ways:
Do not use version labels that look like revision numbers.
—or—
Use the CLI when working with archives that use such version labels.
Configuration Builder does not support the Version Manager File Server.
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 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.
User names that contain double-byte characters and are longer than 20 characters get truncated when you close the Project Security dialog box. In some cases, they also can prevent repeated use of the dialog box.
If you remove all privilege sets from a user (via Admin | Security in the Version Manager desktop client) and then click OK after applying your changes, the user actually recieves the Unlimited privilege set.
If you do not want a user to have Unlimited privileges, make sure that the user has at least one privilege set.
When performing "Open from Team Provider" to bring projects from Version Manager into a local workspace, you must enter your correct login information twice.
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".
If the Tracker web client is running on an SSL-enabled server, associations may fail. You can resolve this issue by adding an SSL certificate to the JRE keystore, as follows:
Download and install JDK 1.3.x or 1.4.x.
Run the following command:
JDK_Home\bin\keytool.exe -import -file Certificate_File -keystore Serena_Home\vm\common\jre\win32\lib\security\cacerts
You will be prompted for a password to the keystore; the default password is changeit.
See also
Using TrackerLink with Secure Sockets Layer (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:
To create and populate a certificate database:
Open the following URL using the Netscape browser:
http://YourServer:SSLport
Where:
YourServer is the IP address or host name of your LDAP server.
SSLport is the TCP/IP port number used by your LDAP server for SSL connections (usually 636).
Follow the instructions on the Netscape Certificate Name Check window, and accept the server certificate for future sessions.
Close Netscape.
Copy the key3.db and cert7.db files from the Netscape user profile directory to the VM_Install_Dir/vm/common/bin/OS directory.
Restart your Version Manager interface (desktop client, IDE, web client, or WebDAV).
Log in.
If you use the INCLUDE directive in a configuration file and there are blank spaces in the path of the configuration file being included, you must use quotation marks around the path. For example, if the sample project database is installed to the default location, define the INCLUDE directive to its configuration file as:
INCLUDE "c:\program files\serena\vm\common\sampledb\archives\basecfg.cfg"
Version Manager may run out of memory when exporting or importing large projects. To avoid loss of data, retain the source project after exporting it. You can then return to it if the project is too large to import.
To increase the amount of memory PCLI (and the desktop client) can allocate, define the environment variable PVCS_MX prior to launching that command. The following examples show how this can be done, changing Java's Heap Size used by Version Manager to 500MB:
| Environment | Command |
| Windows | set PVCS_MX=-Xmx500m |
| UNIX Bourne Shell | PVCS_MX=-mx500m; export PVCS_MX |
| UNIX Korn Shell/Bash | export PVCS_MX=-mx500m |
| UNIX C-Shell | setenv PVCS_MX mx500m |
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.
Page 388 of 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 page 385 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.
The DTK call PvcsSetProjectSemaphore() is not supported by file servers. If you previously used this call to lock down the archives in preparation for builds or backups, you can achieve the same effect with archives on a file server by deselecting the Enable write access option in the Version Manager Administration Utility.
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.
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
If the fully qualified path for the current working directory contains a space, attempts to run PCLI commands or launch the desktop client may fail with an error. For example, if the current directory is /home/pvcs/my dir/test, PCLI may return some version of the following message:
/usr/serena/vm/solaris/bin/pvcsvmdmn: /home/pvcs/my: does not exist
To fix this problem, modify the pvcsvmdmn script identified in the error message by changing the following line:
cd ${EXEDIR}
To this:
cd "${EXEDIR}"
This will resolve the problem.
If you want to make sure that Version Manager gets project information (such as configuration file locations) from the Version Manager File Server, make sure that the location is not also mapped by an entry in the nfsmap file.
Attempting to change the case of a file name on a case-insensitive File Server fails to rename the archive.
To prevent inconsistent time-stamping on Version Manager archives and workfiles, Solaris users in the United Kingdom and Ireland must download and install a patch from Sun Microsystems. The patch, 105210-10 or later, is available from the Sun Microsystems customer support web site, http://sunsolve.Sun.com.
The default kill character on HP-UX (Bourne and Korn shells) is @. This character conflicts with the PCLI listfile command (@listfile) and specifying a workspace at the command line. For example:
pcli listversionedfiles -prd:\productb -pp/newprj @listfile
—or—
pcli getworklocation -sp/@/mariec/myworkspace...
To avoid this conflict, set the kill character to a value other than @. For example:
stty kill ^U (sets the kill character to CTRL+U)
Some PCLI operations, such as ListVersionedFiles, can open many files at a time. On some UNIX systems, the default open file descriptor limit may be set too low. We recommend that you set your file descriptor limit to 128 or higher. For very large databases, we recommend setting the limit as high as allowed by the operating system. For C shell users, use the "limit" command to set the limit. For Bourne and Korn shell users, use the "ulimit" command. The default file descriptor limit varies on each operating system and by system configuration. The default limit may or may not already be set higher than 128.
A lack of file descriptors can manifest itself in various ways. Typical problems include a failure to open or locate files in response to file-intensive commands such as AddFiles, ListVersionedFiles, and ImportArchives.
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.
Attempting to merge revisions (in either the desktop or web client)—or to show differences between revisions using the web client—using version labels comprising only numeric characters generates an error.
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.
Fields, such as the File name field of the Select Workfiles dialog box, may display corrupted Japanese characters.
To fix this issue:
Navigate to the following directory:
VM_Install_Dir/vm/common/java/linux/jre/lib
Rename the font.properties.ja file to font.properties.ja.old.
Rename the font.properties.ja.Redhat8.0 file to font.properties.ja.
You may need to install certain fonts described in this properties file. Execute the following command to determine whether you have a particular font installed:
xlsfonts | grep fontName
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]
When you export a project database on Windows, you can import it only on Windows; you cannot import it on UNIX without manually converting all the pathnames in the exported file and in the configuration file(s) it references. The same is true when you import a file on Windows that was exported on UNIX.
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.
Workspace or user names that contain slashes (/ \), square brackets ([ ]), or colons (:) can cause PCLI commands and the import/export of project databases to fail. Change any such preexisting names before importing/exporting or using other PCLI commands.
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.
Adobe Acrobat may remember the last index that was used for a full-text search. This can cause Acrobat to search the index of the current document and of a previous document, resulting in duplication of search results. To avoid this, make sure that only the index for the current document is selected (see the installation guide for details on selecting a search index).
The Version Manager help will not launch on Internet Explorer if IE is using Sun's 1.4.0x JRE. Use 1.3x or 1.4.1x 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 |
The Version Manager IDE client is supported on:
The following web server configurations are supported for use with Microsoft FrontPage and Visual InterDev web projects:
| Web Server | Operating System |
|---|---|
| IIS 5.0 | Windows 2000 Server |
| IIS 6.0 | Windows 2003 Server |
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 Microsoft Knowledge Base Article 328419.
The Version Manager IDE client supports the following development environments:
NOTE: For integration with IBM VisualAge for Java, you must install the appropriate IBM patch as noted above.
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 ChangeMan Version Manager IDE Client Implementation Guide for more information.
The Version Manager IDE client is certified for use with Serena TrackerLink 6.5 and above.
To use version 8 of the Version Manager IDE client, you must uninstall any previous version of the IDE client on your system before installing Version Manager 8. If you wish to use an older verson of the IDE clinet once Version Manager 8 is installed, you must uninstall Version Manager 8 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 ChangeMan 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 ChangeMan Version Manager | Version Manager IDE Client | Select Serena Provider from the Windows Start menu. The Select Serena Provider dialog box appears.
Select Serena ChangeMan Version Manager.
Click OK. The change will take effect the next time you start your IDE.
If you use a UNC path to install Version Manager to the network in preparation for a workstation installation of the Eclipse 2 plugin, you must edit the setup.ini file before installing to workstations or the Eclipse integration will not work correctly.
To modify a UNC workstation installation for use with Eclipse 2:
Install Version Manager to a network location as outlined in the Serena ChangeMan Version Manager Installation Guide.
Open the \workinst\setup.ini file with a text editor.
Locate the [Workstation] section of the file. The text will be similar to the following:
[Workstation]
InstallDir=\\server\shared\serena\
vmdevint=\\server\shared\serena\vm\common\vmdevint
Change the UNC path on the InstallDir= line to a drive mapping available to all workstations. For example:
[Workstation]
InstallDir=g:\serena\
vmdevint=\\server\shared\serena\vm\common\vmdevint
Save the file.
You can now install to each workstation.
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 Microsoft Knowledge Base Article 328419.
If you wish to use a previous version of the Version Manager IDE client (Development Interface), you must uninstall the current version of Version Manager and then reinstall the older version. To switch back to the current version, you must uninstall the older version and then reinstall the current version.
In the help (Help | About), the interface libraries are listed incorrectly as version 8,0,0,1; however, the build numbers are correct.
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.
Version Manager allows you to configure a project database or project to always remove locks on unchanged files. If you are working with Version Manager projects within PowerBuilder, be sure to set this option. If you do not, objects in your PowerBuilder application may become out of sync with their associated versioned files when you undo a checkout or when you check in an unchanged revision. Objects may appear to be unlocked in PowerBuilder when in fact their associated Version Manager archives are still locked.
See the Serena ChangeMan Version Manager Administrator's Guide for more 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.
Due to a limitation of the Microsoft FrontPage server extensions, other users may be able to delete files that you have checked out. To prevent accidental deletion, use Windows security to protect your files, or be sure to notify other users when you check out files.
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 use square brackets [ ] in folder, project, or file names, source control operations may fail. Avoid using square brackets in folder, project, and file names.
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.
Workaround: Reboot to update your system's path information.
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, the following errors may occur in the Eclipse Rich Integration:
"null.output.blank2" appears in dialog boxes. To eliminate these error messages, see KnowledgeBase article 71502, available from Serena Support.
"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.
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.
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.
The "About" pages and the about.mappings file say: "Serena ChangeMan Version Manager offering includes Eclipse plug-ins that can be installed and used with other Eclipse (3.1)-based offerings." This should be: "Serena ChangeMan Version Manager offering includes Eclipse plug-ins that can be installed and used with other Eclipse (3.0)-based offerings."
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.
If you click Cancel (rather than OK) after changing settings in the Set User Options dialog box, the changes are not implemented; however, they still appear in the dialog box when you open it again. Be careful to note the settings in that dialog box before you click OK.
This applies to the context menu only; Undo Checkout works properly from the toolbar.
When you force an update from the Compare Workspaces view in order to add a new project to your local workspace, the Compare Workspaces view may continue to display the new project even after you have successfully updated your local workspace. Choosing to force an update a second time may then cause an error.
In the case of a failure during a move operation, .NET tries to recover; however, if it fails to do so, the IDE may remain unstable. In this case, return your assets to their original state and perform the move operation again.
In the .NET IDE, if you add a project from Version Manager and specify the local workspace used by the current solution, files with names similar to those in the current project may fail to open. You must then reopen the project from source control to another location so that you can clean things up.
For best results, do not overwrite a local workspace.
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 TeamTrack data includes upper-ASCII characters and the character set is not consistent among the TeamTrack database, server operating system, and Administrator settings, the Rich Integration interfaces may not display the characters correctly.
|
Part 3: Version Manager Web Client |
Version Manager Server is supported on the platforms shown below.
Supported Operating Systems:
Supported Web Servers:
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 Microsoft Knowledge Base Article 328419.
Requirements:
Memory requirements for the server depend upon how many users access the server at the same time and how many daemon processes are running (by default, 5 to 20 daemons will be 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.
Supported Operating Systems:
Supported Web Servers:
Requirements:
Memory requirements for the server depend upon how many users access the server at the same time and how many daemon processes are running (by default, 5 to 20 daemons will be 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.
The Version Manager web client is supported on the platforms shown below.
Operating Systems:
Web Browsers:
Operating Systems:
Web Browsers:
If you're using IE 5.5 and don't have SP2 installed, go to http://windowsupdate.microsoft.com and click the Product Updates link.
Once you have IE 5.5 SP2 installed, perform the following steps:
Select Tools | Internet Options.
On the General tab, click the Settings button.
Set Check for newer versions of stored pages to Every visit to the page.
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 use with TrackerLink in the Version Manager web client. Use JRE 1.3x or 1.4.1x.
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.
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.
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.
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.3.x or 1.4.x.
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.3.x or 1.4.x 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.
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 in version 8.0.
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.
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 Microsoft Knowledge Base Article 328419.
If you plan to install Version Manager 8.1 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
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
If the PVCS Version Manager Application Server is installed as an NT Service, you must remove the service before upgrading. To do so, launch the Version Manager I-Net Configuration utility. By default, you run the Version Manager I-Net Configuration utility by selecting Start | Programs | PVCS Version Manager | PVCS VM I-Net | PVCS VM I-Net Configuration Utility. 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 like any other PDB in the configuration files noted above; you do not have to do anything differently to access a File Server PDB.
Do not use any of the following characters in the name of a project:
* : | / \ ? < > " tab ~ % & ' ,
Also: Do not use ".." as a two-character name, and do not use "." or "@" as a one-character name.
Do not use any of the following characters in the name of a file:
* : | / \ ? < > " tab
Do not use any of the following characters in the name of a label:
: + - * \
Do not use any of the following characters in the name of a promotion group:
< = " ,
Do not use any of the following characters in the name of an archive:
; ,
The functionality of event triggers differs significantly in the Version Manager web client compared to the Version Manager desktop client. The difference is caused by how archives are modified. When you use the Version Manager web client to perform a task, the archives are modified by the Version Manager web server--not by the Version Manager web client. Therefore, the data and operations available to event triggers through the Version Manager web client differ from the data and operations available to event triggers through the Version Manager desktop client.
When working with event triggers, note the following:
EventWorkfile and EventFQPWorkfile contain the temporary file name that the Version Manager web server is working with instead of the workfile name as seen in the Version Manager web client.
If a check-in operation prompts the user for additional information, such as whether or not to continue checking in an unchanged workfile, then the Unconditional PrePut Event Trigger fires twice if the user allows Version Manager to complete the operation. Event Trigger programs affected by these characteristics may require modification.
If the event trigger puts up a dialog box, it is actually displayed on the server, not the client. If the dialog box is modal, it stops the Version Manager web server from processing any further requests from all users until the dialog box is closed.
The Version Manager web server generates log files and temporary files on the server machine. These files do not cause problems, but do use up hard drive space until deleted. We recommend that you purge these files periodically.
You can periodically delete the log files generated in the following directories:
UNIX: VM_Install_Dir/vm/common/tomcat/logs
Windows: VM_Install_Dir\vm\common\tomcat\logs
Temporary files are generated on the server if the connection between the client and server is lost in the middle of a file transfer. Delete these files from the directory VM_Install_Dir\vm\inet\temp on Windows, and in the system temp directory on UNIX. Additionally, temporary files are generated from history and difference reports when users close the browser without logging out of the project. Delete these files from the VM_Install_Dir\vm\inet\temp\html directory.
The Version Manager web client does not automatically update the expanded keyword values in your workfiles after you add them or check them in. To update the keyword values, get or check out the files to your workfile location.
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 attempting to start the Version Manager web server or WebDAV Server, you may get a Java exception error that includes the text JVM_Bind:8080 or JVM_Bind:8090. This may occur for one of the following reasons:
Version Manager web or WebDAV Server is already running. If one feature is started, the other feature is started automatically, since both features share the same installation of Tomcat. The error occurs when you try to start two instances of Tomcat. Close the Tomcat window and proceed to use Version Manager web or WebDAV Server.
Port 8080 (or 8090) is already in use by another application. By default, Version Manager web and WebDAV Server use port 8080. Change the port number if necessary and restart Version Manager web or WebDAV Server.
To change the port number, go to VM_Install_Dir/vm/common/tomcat/conf/server.xml, and change the value of Http10Connector port=.
You may also need to change the following ports if another application is using them:
If you change one or both of these entries to a different port number, make sure that the same ports are specified in the worker.apj12.port= and worker.apj13.port= statements of the VM_Install_Dir/vm/common/tomcat/conf/jk/workers.properties file.
NOTE: If you already have another Tomcat installation, you should change the shutdown port from 8005 to an unused value. Otherwise, both applications will stop when either application's shutdown routine is called.
If you use the Serena ChangeMan Version Manager File Server and you run real-time antivirus software on the system running the Version Manager web server, you may experience degraded performance. This is because the antivirus software scans the Version Manager file cache every time the cache is updated. To avoid this performance penalty, exclude the cache directory from real-time virus scans.
By default, the file cache is in a directory named pvcsfs under your system's temporary directory (as specified by the TMP or TEMP environment variable). You can set a different location for the cache by defining a path in either the FS_TMP or FS_TEMP environment variable.
For more information on antivirus-related performance improvements, see Serena KnowldegeBase article 70042.
If you are using the Version Manager Web server with an Apache 1.3.x server that is configured to use EAPI, you receive an error message when trying to start the Apache server.
WORKAROUND: Contact Support for a copy of the correct mod_jk_eapi.a file.
For the Version Manager applet to load properly, you must add the browser location to your path:
export PATH=/apps/mozilla:$PATH
ALSO: You must launch the browser using the PATH statement:
mozilla &
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.
On 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 you're using NT authentication and your web client users are using the Sun Java plug-in v1.4.1x, they will have authentication problems. If they are able to use the native JVM or version 1.4.2x of the Sun plug-in, they will not have this authentication problem.
When you resize certain dialog boxes on Netscape, Netscape may crash or cancel your operation. Do not resize dialog boxes on Netscape.
Occasionally, you may get a Bad Magic Number exception when you try to perform an action. To fix this problem, delete the contents of the following directory on the server: VM_Install_Dir/vm/common/tomcat/temp/html
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.
At this time, the Version Manager Web Client does not support multi-byte characters when used with the iPlanet Web server. For multi-byte support, please use the Microsoft IIS Web server.
To make sure fonts appear legibly on your UNIX machine, set Netscape to override document-specified fonts:
In Netscape, go to Edit | Preferences; then select Appearance | Fonts in the Category list.
Select Use my default fonts, overriding document-specified fonts.
Make sure your font size is set to something you can read, such as 10 or 12 pt.
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.
If your browser is configured to prevent pop-up ads, the Version Manager web client may not work correctly. Either turn off the pop-up blocking feature, or add the Version Manager server to the list of sites that are allowed to disply pop-up windows.
In Netscape 7, for example, you can configure pop-up blocking options using the Popup Window Controls dialog box under Edit | Preferences | Privacy & Security.
Do not use Netscape 7 with Exceed.
On Windows, if you start the Version Manager Application Server and then stop it before it has been used to access any archives, the daemons do not shut down cleanly. If this happens, close the Serena ChangeMan Version Manager Application Server console window, and remove the DaemonServer.exe process in the Windows Task Manager.
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}
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 are using the Itanium processor, edit vm/common/bin/pvcsstart.bat, replacing -server with -Xint. (This disables the HotSpot compiler.)
Some confirmation windows fail to appear in Netscape 7.02 for Windows, causing some operations to fail. Upgrade your browser to Netscape 7.1 or later.
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.
On both Windows and UNIX platforms, Mozilla 1.6 is unable to display the project directory tree.
Workaround: Use Mozilla 1.7.
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 |
Supported Operating Systems:
Supported Web Servers:
Supported Operating Systems:
NOTE: Read-only support for WebDAV is available for the Windows XP DAV File System and Mac OS DAV File System.
Supported WebDAV Clients:
Other WebDAV-enabled clients may work but are unsupported at this time.
If the PVCS Version Manager Application Server is installed as an NT Service, you must remove the service before upgrading. To do so, launch the Version Manager I-Net Configuration utility. By default, you run the Version Manager I-Net Configuration utility by selecting Start | Programs | PVCS Version Manager | PVCS VM I-Net | PVCS VM I-Net Configuration Utility. Click the Remove NT Service button.
To troubleshoot connection problems with WebDAV Server, first check the Tomcat server console for any errors or exceptions.
If you do not see any errors, do the following:
Check that you can access the Version Manager project database by logging in to Version Manager. Note that you should verify the project database specified in vm.properties.
Check that the web server is up and running by entering the web server URL in your web browser. For example: http://Test1:10070/
Check that the Tomcat web server is running by entering the Tomcat URL in your web browser. For example: http://Test1:8080
Check that the DAV servlet can be accessed from a supported client, such as web folders, by connecting to Tomcat directly from the client. For example: http://Test1:8080/SampleDB.dav.
If you can't access the servlet, check the Tomcat server console for any exceptions.
If the DAV servlet can be accessed by a client directly through Tomcat, try adding a web folder using the web server (e.g., Apache or IIS) port number. For example: http://Test1:10070/SampleDB.dav
If this does not work, then the problem is with the web server configuration. Check the Tomcat and web server logs to identify the errors.
Check that the web server is using the right port setting to communicate with Tomcat. Open the following two files:
VM_Install_Dir/vm/common/tomcat/conf/jk/workers.properties
VM_Install_Dir/vm/common/tomcat/conf/server.xml
Verify that the port setting for worker.ajp13.port in workers.properties matches the port specified in server.xml under "Apache AJP13 support."
If the port settings do not match, change them so they are the same.
The workspace setting for default version (a label) determines which files are visible through WebDAV Server. Unlike the Version Manager desktop client, WebDAV Server only shows the files that match the default version setting. If a default version is not set, then the default is the tip revision of the trunk. In this case, only these tip revisions will be visible through WebDAV Server.
After successfully connecting to WebDAV Server, most failures on common operations (e.g., check out or add workfiles) occur due to lack of privileges.
NOTE: To be able to create new archives through WebDAV, users must be assigned the Add Version Label privilege in addition to the Create Archive privilege.
Log in to Version Manager as that user to verify that you can perform the operations allowed with the specified privileges. If you can perform the correct operations in Version Manager, you should be able to perform them using WebDAV Server.
If you change a user's privileges, those changes are not visible to the user until you restart Tomcat or the user's current session times out.
When attempting to start the Version Manager web server or WebDAV Server, you may get a Java exception error that includes the text JVM_Bind:8080 or JVM_Bind:8090. This may occur for one of the following reasons:
Version Manager web or WebDAV Server is already running. If one feature is started, the other feature is started automatically, since both features share the same installation of Tomcat. The error occurs when you try to start two instances of Tomcat. Close the Tomcat window and proceed to use Version Manager web or WebDAV Server.
Port 8080 (or 8090) is already in use by another application. By default, Version Manager web and WebDAV Server use port 8080. Change the port number if necessary and restart Version Manager web or WebDAV Server.
To change the port number, go to VM_Install_Dir/vm/common/tomcat/conf/server.xml, and change the value of Http10Connector port=.
You may also need to change the following ports if another application is using them:
If you change one or both of these entries to a different port number, make sure that the same ports are specified in the worker.apj12.port= and worker.apj13.port= statements of the VM_Install_Dir/vm/common/tomcat/conf/jk/workers.properties file.
NOTE: If you already have another Tomcat installation, you should change the shutdown port from 8005 to an unused value. Otherwise, both applications will stop when either application's shutdown routine is called.
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 Web Client section.
Version Manager WebDAV Server is configured to work with the Serena ChangeMan 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.
If you are able to connect to WebDAV Server and still encounter problems working in a WebDAV client, the client may have WebDAV issues.
We recommend that you:
Go to the client support web site and install any recommended service packs. Search the client KnowledgeBase or support documents for reported WebDAV problems and fixes.
Check Serena support for KnowledgeBase articles about specific client problems and fixes.
Some WebDAV clients (e.g., Dreamweaver) may require you to enter a password for authentication. We recommend that you have a Version Manager password so that the WebDAV clients will work properly. If you do not have a Version Manager password, define one using the Version Manager desktop client.
Microsoft Web Folders auto-detects if Microsoft FrontPage Server Extensions are running on an IIS web server. If detected, the Web Folders client does not use a WebDAV protocol and therefore does not interact with the WebDAV server. If you configure Serena ChangeMan Version Manager WebDAV Server redirected through an IIS webserver server with MS FrontPage Server Extensions, Web Folder clients will only interact with the FrontPage Server Extensions, and not the WebDAV server.
To ensure that the Euro character works properly on Solaris, do the following:
Install the latest OS patches for Solaris.
In the Solaris Login dialog box (console), click Options and then select Language | en_ISO8859-15.
Log in; then start WebDAV Server by running ./pvcsstart.sh from VM_Install_Dir/vm/common/bin.
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.
|
Part 5: Serena ChangeMan Meritage |
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.
End Readme
Copyright © 2003–2005 Serena Software, Inc. All rights reserved.
$Revision: 1.198 $