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: 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 S123872 (http://knowledgebase.serena.com/InfoCenter/index?page=content&id=S123872). 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.
NOTE By default, Version Manager checks for illegal characters (such as dash (-)) during label creation and rejects the label if it contains illegal characters. If you must create labels that include illegal characters, you can disable the filter that checks for illegal characters in labels. See the DisableBadLabelFilter directive in the Serena PVCS Version Manager Command-Line Guide.
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.
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, TeamTrack, or SBM 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. See KnowledgeBase article: S134480 (http://knowledgebase.serena.com/InfoCenter/index?page=content&id=S134480)
See also
Using TrackerLink with Secure Sockets Layer (SSL)
SourceBridge must be installed to the clients in order to enforce association on checkin; else the checkin will occur with no association and no prompt or warning that an association is required.
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:
You can create a certificate database with the Mozilla Certutil utility. Certificate databases are platform independent and can be used across multiple operating systems.
To create and populate a certificate database using Mozilla Certutil:
Certutil is a command-line utility installed with Version Manager, so it should already be included in your system's path environment variable. (It is installed to this directory: VM_Install_Dir/vm/common/bin/OS.) For more information, see: http://www.mozilla.org/projects/security/pki/nss/tools/certutil.html.
Create a folder for the certificate database. For example:
C:\pvcs\ldap_cert
Create a certificate database using the command:
certutil -N -d "FolderPath"
For example:
certuil -N -d C:\pvcs\ldap_cert
Do one of the following:
Add the LDAP server certificate to the certificate database using the following command:
certutil -A -n "Nickname" -t "P,," -a -i PathToCertificate -d PathToCertificateDatabase
For example:
certutil -A -n "LDAP" -t "P,," -a -i C:\pvcs\ldap_cert\ldap.cer -d C:\pvcs\ldap_cert
Add a RootCA certificate to the certificate database using the following command (to work with multiple servers all signed by the same RootCA):
certutil -A -n "Nickname" -t "C,," -a -i PathToCertificate -d PathToCertificateDatabase
For example:
certutil -A -n "My RootCA" -t "C,," -a -i C:\pvcs\ldap_cert\My_RootCA.cer -d C:\pvcs\ldap_cert
For each LDAP server you have configured for use with Version Manager, use the Version Manager desktop client to specify the location of the appropriate certificate database. The relevant field is on the LDAP Server dialog off of the Configure Project/Project Database dialog.
NOTE This location must be accessible by all clients, such as a mapped network drive or UNC path.
By default, the Version Manager client will deny access to conflicting path maps and display a message. In the Open Project Database dialog, conflicting path maps will be shown in red. A path map conflict occurs when a user tries to access two, or more, path maps that fully or partially overlap but reside on different servers.
See the Serena PVCS Version Manager Administrator's Guide for information on resolving or working around such conflicts. If improperly handled, overlapping path maps can result in the wrong files being acted upon.
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"
Large projects can exceed the memory allocated for Java in a variety of situations and with a variety of Version Manager interfaces. The following table describes some of the possible error scenarios.
| Component | Symptom | See |
|---|---|---|
| Application Server: -File Server -Web Client -WebDAV Client -RIDE IDE's (if using server-side processing) |
Out of memory error (for example, during recursive view of a large project) | Application Server |
| Desktop Client | Out of memory error Failure of Export/Import |
Desktop Client and PCLI |
| IDEs | Out of memory error | IDEs | PCLI | Out of memory error Failure of Export/Import |
Desktop Client and PCLI |
| NOTE: Export/Import Project May Fail with Large Projects 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. |
Desktop Client and PCLI | |
Java-based Version Manager clients use the following memory heap parameters:
-Xms Minimum heap size JVM parameter for loading JVM.
-Xmx Maximum heap size JVM parameter for loading JVM. If heap value grows above this value application will throw "Out of memory" error.
The following sections describe how to set those values for the various clients.
To increase the amount of memory that the Desktop client and PCLI can allocate, define the environment variable PVCS_MX prior to launching the command or interface. The following examples show how to change the Java Heap Size used by Version Manager to 512MB (your needs may differ):
| Environment | Command |
|---|---|
| Windows | set PVCS_MX=-Xmx512m |
| UNIX Bourne Shell | PVCS_MX=-Xmx512m; export PVCS_MX |
| UNIX Korn Shell/Bash | export PVCS_MX=-Xmx512m |
| UNIX C-Shell | setenv PVCS_MX -Xmx512m |
The Version Manager Application Server hosts the following Version Manager features. Changes made here affect them all.
Version Manager File Server
Version Manager Web Server
Version Manager WebDAV Server
Server-side processing mode for the Rich IDE's
Do one of the following:
If the Application Server is running as a service under Windows:
On the server system, launch the Registry Editor by running RegEdit.
Go to the registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Serena VM Web Application Server\Parameters
Locate the -Xms and/or -Xmx values in the Data column and change the corresponding string value accordingly.
Restart the server.
Else:
On the server system, open the following file in a text editor:
VM_Install\vm\common\bin\pvcsrunner.bat
(pvcsstart.sh on UNIX)
Find the following line:
set JAVA_OPTS=
And set the value of the following parameters as needed:
-Xmsvaluem -Xmxvaluem
Save the file and restart the server.
See the section below specific to your IDE. The memory values shown below are examples; your needs may differ. The changes will take effect when you next launch the IDE.
SCC Clients
In the ISLV.ini file add a section and key value pair in the following format:
[CPCLI]
JAVAARGS=-Xms128m -Xmx512m
Visual Studio RIDE
In the ISLV.ini file add a section and key value pair in the following format:
[SVE]
sve.dotnet.jvmloader.jvm.initialHeapSize=128m
sve.dotnet.jvmloader.jvm.maxHeapSize=256m
Eclipse RIDE and SCC
In the eclipse.ini file located in the eclipse folder, add a section in the following format:
-vmargs
-Xms40m
-Xmx256m
Here 40m and 256m corresponds to 40MB (min Heapsize) and 256MB (max Heapsize).
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.
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.
Version Manager cannot be licensed until the workstation is registered to the network. Register to the network before attempting to use Version Manager.
Allowing PIN caching by ActiveIdentity Client on Linux systems can, in certain circumstances, result in access regardless of the PIN entered. To avoid this possibility, specify a short cache retention period or disable PIN caching in ActiveIdentity Client. For obvious reasons, we are not fully describing the very specific scenario which can bring about this undesired result.
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.
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 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.
It is not enough to configure SourceBridge to require associations, you must also set the SCC provider to the issue management system you are using. Use the Version Manager SCC Admin to select the correct SCC provider from those installed to your client system. Depending on the version you have installed, you will see an SCC provider named for your issue management system. For example, Serena SourceBridge or Tracker TrackerLink.
Server-side processing is enabled by default, so by default all event triggers will be executed on the server. If this is incompatible with your processes, you can revert to the previous behavior of client-side processing. See the Serena PVCS Version Manager IDE Client Implementation Guide for more information (the section on setting default options for your particular IDE).
If you are using the Server-Side Processing feature of the Rich IDEs, then all File Servers containing repositories used by these integrations must be defined on the server(s) through which the RIDE users connect--including the File Server itself (as "localhost" or using its server name). To do so, see the File Server chapter of the Serena PVCS Version Manager Administrator's Guide.
Some third-party tools create folders that fail to function properly for the third-party tool if any outside content is added to them. Since the Serena RIDE integration adds a _serena folder when items are placed under source control, you must exclude sensitive third-party folders from source control. The ibmconfig folder is one folder known to have this issue. See the Serena PVCS IDE Implementation Guide for details on how to exclude files or folders from source control.
There is a dependency upon the library libexpat.0.so. Your SuSE installation probably has a newer version of this file, for example libexpat.1.so. Unfortunately there are several third-party libraries that depend upon the older version of the file. To avoid sporadic crashes, you must download and install a compact pack specific to your operating system in order to acquire the needed version of libexpat0. See http://rpm.pbone.net/index.php3/stat/3/srodzaj/1/search/libexpat.so.0
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.
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.
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/pvcsrunner.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 (&).
If one, or more, servlets are defined for the Version Manager Web Server Application (this provides access for the Version Manager Web Client), and the associated project databases are on a Version Manager File Server, then all File Servers containing repositories used by these components must be defined on the server(s) through which the Web Client users connect--including the File Server itself (as "localhost" or using its server name). To do so, see the File Server chapter of the Serena PVCS Version Manager Administrator's Guide.
|
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: 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–2013 Serena Software, Inc. All rights reserved.