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 (this file)
Performance tips and workarounds to help you proactively avoid undesirable outcomes. Read this before using Version Manager or attempting to recover from a critical error.
Known Issues (known_issues.html)
Information on cosmetic defects, non-critical errors, and issues for which there are no preventative measures. Look here when you experience an error or other unexpected behavior not listed in the Usage Cautions file.
Release Notes (release_notesvm.html)
A list of the defects fixed, enhancements made, and behaviors changed in each release of Version Manager. Look here to see what has changed since you last upgraded.
This readme file is organized into distinct parts. Please read the parts that correspond to the Version Manager components you are using.
Part 1: Version Manager CLI, Desktop Client, File Server, and PCLI
Part 2: Version Manager IDE Client
Part 3: Version Manager Web Client
Part 4: Version Manager WebDAV Server
Part 5: Serena Meritage
Part 6: Copyright/Disclaimers/Support
|
Part 1: Version Manager CLI, Desktop Client, File Server, and PCLI |
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 PVCS 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.
Version Manager 8.1.1 or later (and Version Manager 8.0.2.6) includes a feature that automatically cleans up old files in the File Server client cache directory whenever a Version Manager session first contacts the File Server.
You can exert some control over this feature by adding entries to your islv.ini file.
NOTE: Time values are in seconds by default, but you can specify minutes or hours using the <n>m or <n>h syntax.
New settings of interest are as follows (shown with the default values that will be used if the entry is absent):
[PVCSGUI_6.5]
pvcs.fileserver.cache.cleanup.frequency=12h
Wait at least 12 hours following a cleanup operation before attempting to clean up the cache directory again.
pvcs.fileserver.cache.cleanup.age=24h
Clean up all files that are at least 24 hours old.
pvcs.fileserver.cache.cleanup.mode=m
Determine the age of the file based on its modification time ('m'). Can also be set to 'a' (file access time) or 'c' (file creation time). The default is highly recommended as some file systems could exhibit bad behavior with the other options.
NOTE: The location of the File Server client cache directory is determined by the environment variable FS_TMP or, if FS_TMP is not defined, FS_TEMP. If neither is defined, the directory defaults to %TMP%\pvcsfs or, if TMP is not defined, %TEMP%\pvcsfs.
Most users should be unaffected by the new dates for Daylight Savings Time. However, if you have a Windows system that uses the TZ environment variable, then Version Manager will default to built-in, hard coded, USA-centric start and end dates for Daylight Savings Time.
To avoid this issue, you can use the PVCSTZ environment variable to override both the TZ variable and the time zone information that is provided by the operating system, should that be desired.
NOTE As of 8.1.4.0 (spring 2007), DST dates have been updated to reflect the current law. Also, an update with the new dates is available for Version Manager 8.1.3.2. It is attached to the KnowledgeBase article mentioned below.
See the Serena KnowledgeBase article, Is Version Manager affected by the changes to the U.S. Daylight Saving Time (DST) for 2007?, ID 5004791, for more information.
If the content of a keyword contains a "$" character, you must use the new syntax:
$Keyword::$123456::$
Where:
Keyword is the keyword.
123456 is the length delimiter. The length is determined by the number of characters. Any characters can be used as the length delimiter.
::$ marks the beginning and the end of the length delimiter character string.
If the content of a fixed length keyword does not contain a "$" character, you may use either the new syntax or the original syntax, which follows:
$Keyword::123456$
From the command line, a dash (-) in a version label can be interpreted as a math operation upon the revision number. This can result in the incorrect revision being acted upon.
This can happen only in the circumstances described below:
A series of labels are the same save for a numeral that follows a dash. For example: Beta; Beta-1; Beta-2; Beta-3. NOTE There must be a label of the same name with no dash and no numeral (Beta, in this case).
A command is issued against a label in the series, but that label does not yet exist in the archive or it has been deleted. For example, Beta-4.
The revision acted upon in that case will be based upon the revision number of the revision with the non-numerical, non-dash label (Beta, in the example above), minus the numerical portion of the requested, but nonexistent, label.
Here is a specific example:
Revision 1.6 has the Version Label: Beta
The nonexistent label used in the command is: Beta-4
The unintended revision math performed is: 1.6 - 4 = 1.2
The revision acted upon by the command is thus: 1.2
Recommendation: If you must use such a label numbering scheme, be sure never to specify a nonexistent label in a command. Better yet, avoid the possibility of encountering this behavior by ensuring that there is not a label like "Beta" that otherwise matches the sequence of labels.
If a file has over 32,000 lines, the scroll bar in the Diff/Merge tool will not work correctly. Use the Next, Previous, and Go to line features to navigate large files. Using the scroll bar alone, you may be unable to reach the desired location.
Under some circumstances, a copy project database operation may fail with a privileges error. This may occur when all of the following are true:
Sub projects are configured with access control databases.
Copy existing Configuration Files is selected.
Create a new Access Control Database is selected.
The name used to log into the operating system (the so called HOSTID) does not exist in the Access Control Database(s) of the subproject, and the copy is performed by a different username.
To work around this issue do one of the following:
Ensure that the HOST login ID exists in all access control databases of the project database. Perform the copy operation as that user.
Select the Copy Access Control Database to new location option.
Configuration Builder does not support the Version Manager File Server.
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.
When you create a new admin user from the Version Manager File Server Administration Utility, do not use a semicolon (;) in the ID or password. Doing so will cause the next login to the administration utility to fail; nobody will be able to log in until the user has been removed.
If you remove all privilege sets from a user (via Admin | Security in the Version Manager desktop client), the user actually receives 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.
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.4.2x or 1.5x.
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:
NOTE Certificate database generated through Netscape 4.7x or Certutil supports multiple platforms and can be used across Microsoft Windows or other platforms.
To create and populate a certificate database using Netscape 4.7x:
Open the following URL using Netscape 4.7x:
https://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.
NOTE As of August 2006, Netscape 4.7x was available from:
http://browser.netscape.com/ns8/download/archive47x.jsp
If that specific URL is no longer active, try starting from the main Netscape page:
http://www.netscape.com/
To create and populate a certificate database using Certutil:
Certutil is a command line utility in the Security NSS package provided by Mozilla. Use this to generate the cert7.db and cert8.db.
Create a folder for the certificate data base.
Example c:\certificate
Create a new certificate using the command Certutil -N -d "Cetificate storage folder".
Example certuil -N -d c:\certificate
The following files are generated:
Cert8.db
Key3.db
Secmod.db
Add the server certificate. You have to manually add this from the directory server to the certificate data base using the following command:
Certutil -A -n "Nickname" -t "P,," -a -i certfile -d Certificate directory
Example certutil -A -n "SerenaDirectoryserver" -t "P,," -a -i :\servernaDirectoryServer.cer -d c:\certificate
Connect the VM LDAP configuration to the Certificate Storage folder.
If LDAP authentication is enabled for a given file server path map, you must disable LDAP authentication before creating a new project database on that path map. Else an error dialog will appear, and the project database will not be functional. You may re-enable LDAP authentication once the project database has been created.
You must enable Access control database security if security is enabled on a file server path map.
File server path map security is set up through the Version Manager File Server Administration utility. From the Path Map page, open the Add Path Map or Edit Path Map dialog box. If you enable either the Access control database field or the LDAP authentication checkbox, you must also enable the Access control database security checkbox (see below).
The Access control database security checkbox is on the General tab of the Configure Project Database dialog (from the desktop client: Admin | Configure Project). Select Security | Access Control Database from the Options tree.
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 |
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.
Restart the Version Manager Desktop Client after making changes to the Make Secure dialog box. If you reopen the dialog box during the same Version Manager session, it will not reflect the previous changes, and they could be lost when you close the dialog box.
To start the Version Manager Application Server, you must be an administrative user in Vista.
See the VS 2005: Windows Requires Administrative User topic for more information.
Every time you launch the Version Manager Application Server Admin, you must right-click on the Application Server Admin shortcut and select Run as administrator from the resulting pop-up menu, or you can configure the shortcut to always run as administrator.
To access the vconfig.exe and to modify the vmwfvc.dll file, you must log into Windows as an administrative user or use the Run as administrator option in Vista.
See the VS 2005: Windows Requires Administrative User topic for more information.
If you encounter a conflict with a third-party DLL, try adding the name of the DLL to the ISLV.INI file. If there is not already a [THIRDPARTY] section in the ISLV.INI file, create one and list the conflicting DLL's under it as follows:
[THIRDPARTY]
PVCS.VM.THIRDPARTYDLLS=libeay32.dll:ssleay32.dll
Any DLL names should:
Be separated by the delimiter colon ( : )
Contain only the filename, not the full file path.
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.
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 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.
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.
|
Part 2: Version Manager IDE Client |
Version Manager file and revision information is not saved in Tracker or TeamTrack when you are using TrackerLink or SourceBridge with VS.NET and ASP.NET Web applications. To work around this problem, you can unregister the Version Manager COM interface if you are not using this interface for other projects. To unregister the COM interface, run the regsvr32 utility from the Windows command line:
regsvr32 /u "C:\Program Files\Serena\vm\devint\bin\IFC_COM.dll"
NOTE The above example reflects the default Version Manager installation location.
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 PVCS Version Manager Administrator's Guide for more information.
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.
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 create a project with empty folders in Eclipse, you must perform an immediate synchronize operation; otherwise, you cannot perform a successful Get on the project.
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.
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.
Using the rich integration to Visual Studio .NET, opening a solution with the following conditions will fail:
The solution includes multiple projects.
One of the project files resides within the root solution folder, and has subfolders beneath the root solution folder.
The solution includes a Web project.
Specifically, the subfolders belonging to the project located in the root solution folder fail to load. To successfully open multi-project solutions from source control, make sure that each project is stored in its own folder.
The rich integration uses the default version (label) to determine which files are visible in a given Version Manager workspace. To avoid confusion, it is important that you understand how this works.
If you use the desktop client to apply a default version or change the existing one for a project database or for a workspace, only files that have the version label will appear in Visual Studio. If the project and solution files do not have these labels, you will see no files.
To avoid the potential for confusion:
Create a Version Manager workspace for any user or group of users who may need their own default version (label).
Define default versions on a workspace-by-workspace basis (File | Properties | Workspace Settings tab), rather than for the entire project database.
Remember that when you open a project from source control that you must specify the Version Manager workspace to use. If you wish to see the files and revisions defined by a different default version, then you must do an open from source control and specify the workspace that is associated with the desired label.
See the Serena Version Manager IDE Client Implementation Guide for more information.
In order to use the integration on Windows (except Windows 2000, 2003, & XP), you must be an administrative user or you must invoke Visual Studio with the Run as administrator option enabled.
You can right-click on the Visual Studio shortcut and select Run as administrator from the resulting pop-up menu, or you can configure the shortcut to always run as administrator.
|
Part 3: Version Manager Web Client |
If you use the Serena PVCS 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.
Version Manager 8.1.1 or later (and Version Manager 8.0.2.6) includes a feature that automatically cleans up old files in the File Server client cache directory whenever a Version Manager session first contacts the File Server.
You can exert some control over this feature by adding entries to your islv.ini file.
NOTE: Time values are in seconds by default, but you can specify minutes or hours using the <n>m or <n>h syntax.
New settings of interest are as follows (shown with the default values that will be used if the entry is absent):
[PVCSGUI_6.5]
pvcs.fileserver.cache.cleanup.frequency=12h
Wait at least 12 hours following a cleanup operation before attempting to clean up the cache directory again.
pvcs.fileserver.cache.cleanup.age=24h
Clean up all files that are at least 24 hours old.
pvcs.fileserver.cache.cleanup.mode=m
Determine the age of the file based on its modification time ('m'). Can also be set to 'a' (file access time) or 'c' (file creation time). The default is highly recommended as some file systems could exhibit bad behavior with the other options.
NOTE: The location of the File Server client cache directory is determined by the environment variable FS_TMP or, if FS_TMP is not defined, FS_TEMP. If neither is defined, the directory defaults to %TMP%\pvcsfs or, if TMP is not defined, %TEMP%\pvcsfs.
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 applet may not install on FireFox and Mozilla browsers if the server is running IIS 6 on Windows 2003. You can avoid this issue by defining a MIME type for .xpi files. See the following topic in the installation_info.html file:
Using FireFox and Mozilla Web Browsers with IIS 6 on Windows 2003 Server
This error occurs when you click on the link to see the revision information for a file with a file name that is over 28 double-byte characters in length.
Workaround: Create the following DWORD value under the following registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters
"UrlSegmentMaxLength"
Set the value to 500.
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 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 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'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 or 1.5.x of the Sun plug-in, they will not have this authentication problem.
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.
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 display pop-up windows.
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 PVCS Version Manager Application Server console window, and remove the DaemonServer.exe process in the Windows Task Manager.
If you are using the Itanium processor, edit vm/common/bin/pvcsstart.bat, replacing -server with -Xint. (This disables the HotSpot compiler.)
Errors occur on the Version Manager Web Server if there is a literal ampersand or an upper-ASCII character in any field of a servlet definition.
If you need to use an ampersand character (&) in the servlet description, use the entity form (&) rather than the literal form (&).
|
Part 4: Version Manager WebDAV Server |
If you are able to connect to WebDAV Server but 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.
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.
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 PVCS 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.
|
Part 5: Serena Meritage |
See the Known Issues file.
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 PVCS Version Manager documentation for acknowledgements, and individual LICENSE files for additional information, regarding any third party components.
THE JAVA RUNTIME ENGINE, TOMCAT AND XERCES JAVA PARSER (THIS SOFTWARE) IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL SUN MICROSYSTEMS, OR THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS, BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
DocuComp® comparison technology licensed from ASI Software.
Portions of the software, DocuComp® comparison © 2004 ASI Software, Inc. All rights reserved.
This product includes software developed by
The Apache Software Foundation (http://www.apache.org/).
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)
Portions © Copyright 2006 Microsoft Corporation. Al Rights Reserved.
Portions © Copyright 1996, 1999 International Business Machines Corporation and others. All Rights Reserved.
Portions © Copyright Intalio Inc. and others. All Rights Reserved.
Portions © Copyright eHelp Corporation. All Rights Reserved.
End Readme
Copyright © 2003–2010 Serena Software, Inc. All rights reserved.