Serena® Mover™
Version 2.3 Readme File

This file contains important information on installing and using the current release of Serena Mover. For a list of the defects fixed since the last release of Mover, see release_notes.enUS.html.

Table of Contents

1.0 Important Information

1.1 Server OS and Requirements

1.2 Client and Browser OS and Requirements

1.3 Mover Agent Requirements

1.4 Java Runtime Environment Requirements

1.5 Version Manager and Dimensions Requirements

1.6 Supported FTP Servers

1.7 Source Dimensions or VM Profile on UNIX

1.8 Flattening Directory Structures at Deployment

1.9 1.9 UNIX: Set Timezone Environment Variable for Tomcat

1.10 Support for Public Keys with SSH

2.0 Known Issues

2.1 Dimensions/Version Manager Browser Connection Error

2.2 Netscape: Login Fails on Ports Other than 80

2.3 Tomcat Errors When Mover and VM Web Server are on Same System

2.4 Licensing Error When VM Configuration File Is Not Found

2.5 Upgrade: Two Entries in Windows Add/Remove Programs

2.6 Netscape: Help Index Does Not Open the Correct Topic

2.7 Supported Characters for User and Group Names

2.8 Supported Characters for Server Commands

2.9 UNIX: rundmcm.sh and rundmcli.sh Script Errors When Deploying Dimensions Files

To Top

1.0 Important Information

1.1 Server OS and Requirements

The information in this section represents minimum requirements only.

IMPORTANT! If you will use Mover with Serena Dimensions or Serena Version Manager, you must install Mover and the correct version of the Dimensions server or Version Manager to the same machine. See Version Manager and Dimensions Requirements, below.

Supported Server Operating Systems

Server Hardware Requirements

IMPORTANT! In addition to the following requirements, we recommend that the servers to which you install Mover use static IP addresses only. Systems that dynamically generate IP addresses, for example using DHCP, can cause licensing problems.

1.2 Client and Browser OS and Requirements

Supported Client Operating Systems

Supported Browsers

You can use these combinations of operating systems and browsers, with the Sun Java Virtual Machine plug-in for each:

Minimum Client Hardware Requirements

1.3 Mover Agent Requirements

Supported Agent Operating Systems

Minimum Hardware Requirements

1.4 Java Runtime Environment Requirements

Mover requires one of the following versions of the Java Runtime Environment (JRE):

The Java Runtime Environment is available at http://java.sun.com

1.5 Version Manager and Dimensions Requirements

To use Mover to manage deployment of Version Manager or Dimensions files, you must upgrade Version Manager or the Dimensions server to the versions that support integration to Mover. You can upgrade before or after you install Mover.

Upgrade to one of the following:

1.6 Supported FTP Servers

You can use the following FTP servers with Serena Mover:

1.7 Source Dimensions or VM Profile on UNIX

If you will use Mover with UNIX installations of Version Manager or Dimensions, you must source the Version Manager or Dimensions profile before you start Mover. If you do not source the upgraded Version Manager or Dimensions profile, the Mover integration will fail to connect to Dimensions or VM and you will receive a "Login Failed" error message. Do one of the following to complete this requirement:

1.8 Flattening Directory Structures at Deployment

A Flatten Tree Structure option has been added that allows you to flatten the directory structure when you deploy files that are stored in Version Manager and Dimensions.

If you choose this option, all files from either Version Manager or Dimensions will be deployed to the same level in the same directory.

1.9 1.9 UNIX: Set Timezone Environment Variable for Tomcat

The Timezone environment variable for the Tomcat server is set to a null value, by default, in UNIX installations of Mover. This may result in incorrect timestamps resulting from shifts in time that the server is unaware of, such as Daylight Savings.

To set the timezone:

  1. Open the following file in a text editor:

    Mover install directory/changemanmover/options.sh

  2. Locate the following line:

    JAVA_OPTS="-Xmx$CATALINA_MEMORY"

    And change it to the following:

    JAVA_OPTS="-Xmx$CATALINA_MEMORY -Duser.timezone=[yourtimezone]"

    Replace [yourtimezone] with the appropriate value.

    For example: JAVA_OPTS="-Xmx$CATALINA_MEMORY -Duser.timezone=America/Los_Angeles"

For a complete list of possible timezone values, see KnowledgeBase document KB70631 on Serena Support.

To TOC

1.10 Support for Public Keys with SSH

Starting with version 2.3, Serena Mover more fully supports the Secure Sockets Handling (SSH) protocol. You can now store a public key in the keystore on the Mover server, and direct the Mover SFTP / SSH client to use that public key. You can use public key authorization for keys protected with passphrases.

To set up public keys for Mover:

  1. Set up both a Mover server and a target server running SFTP.
  2. Set up a key. For example, for RSA authentication, you would complete steps like the following:
    1. On the Mover server, run a command like the following:
      ssh-keygen -f <location>/id_rsa -t rsa
      In this example the key pair includes id_rsa and id_rsa.pub.
    2. Copy the id_rsa.pub file to the target server, under the ~/.ssh folder, where ~ is the home for the FTP user that Mover will use to deploy. If there is no .ssh folder on the SFTP server, you must create it.
    3. Add the id_rsa.pub file to the authorized_keys file, for example with the following command:
      cat id_rsa.pub>>authorized_keys
      This will create the authorized_keys file in the FTP user's .ssh file.
  3. From the Mover client, display the Deploy | Setup | Target view.
  4. Define a server, and on the New Server dialog box set the Type list to Secure FTP Server (SSH/Secure Copy).
  5. Under FTP Server on the New Server dialog box, complete all fields and enter the passphrase in the Password field. If you are not using passphrases, leave this field blank.
  6. Under Options, select the Public key authentication check-box.
  7. Ask your administrator for the path where the appropriate private key resides.
  8. Also under Options, enter the full path on the Mover server to the private key file in the Private key field. This must include the key name. For example, this may be something like the following: '.ssh/id_rsa'

2.0 Known Issues

2.1 Dimensions/Version Manager Browser Connection Error

When you use Mover with the Dimensions web client or Version Manager web client, you can invoke a dialog box when you define a custom root that allows you to browse for the specific baseline (for Dimensions) or revision (for Version Manager) that you will include in a deployment activity. If the session for this browser dialog box times out, it will lose its connection to the Dimensions or Version Manager server. In order to reconnect, you must log out of Mover, close all instances of your browser application, and then log back into Mover.

2.2 Netscape: Login Fails on Ports Other than 80

Logging in to the Mover server from a Netscape browser may fail if the Mover server uses a port number other than 80 (which is the default port). When this happens, Netscape displays the following error message:

Access to the port number given has been disabled for security reasons.

If this happens, you must add the port number to a list of acceptable ports that Netscape stores in a preferences file, all.js.

To do this:

  1. Locate and open the following file in a text editor:

    Netscape install directory\defaults\pref\all.js
  2. Add the following line to this file:

    pref("network.security.ports.banned.override", "port number 1" , "port number 2");

    For example, to enable Netscape to log into Mover servers on ports 1080 and 8080:

    pref("network.security.ports.banned.override", "1080" , "8080");
  3. Save all.js and restart Netscape.

2.3 Tomcat Errors When Mover and VM Web Server are on Same System

If you have installed Mover and the VM Web Server to the same system, the following Tomcat error may occur when you try to run both of them:

java.net.BindException: Address in use

This occurs when the AJP connectors for both Tomcat installations are set to use the same port number (8009 by default). To correct this, you can change the port number for the AJP connector in the Mover Tomcat installation. To do this:

  1. Open the following file in a text editor, such as Windows Notepad:

    Mover install directory/Tomcat/conf/server.xml
  2. Locate the following lines:

    <!-- Define an AJP 1.3 Connector on port 8009 -->
        <Connector className="org.apache.ajp.tomcat4.Ajp13Connector"
                   port="8009" minProcessors="5" maxProcessors="75"
                   acceptCount="10" debug="0"/>
  3. Change the port attribute to another value, such as 8019.
  4. Save the server.xml file and restart the Mover server.

2.4 Licensing Error When VM Configuration File Is Not Found

Version Manager uses a configuration file, ISLV.INI, which typically resides in the Windows root directory (for example, c:\Windows). During deployment, Mover checks this file to make sure that the user has a valid Version Manager license. If the ISLV.INI file resides in a location other than the Windows root directory, the following error appears:

Access to this project has been denied because your login account was unable to obtain a license.

To fix this problem, you must identify the location of the ISLV.INI file to Mover.

  1. Locate and open the following file in a text editor:

    Mover install directory\vm\runvmcm.bat
  2. Uncomment the following line in the file, and enter the location of the ISLV.INI file:

    set ISLVINI=directory


    3. For example, set ISLVINI=C:\configuration
  3. Save the file.

2.5 Upgrade: Two Entries in Windows Add/Remove Programs

After you upgrade Mover 1.x on Windows, two entries for the program appear in the Add or Remove Programs list (Serena Mover and Merant Mover). Do not attempt to remove Merant Mover; the new version of Mover will not work if you attempt to uninstall the previous version.

2.6 Netscape: Help Index Does Not Open the Correct Topic

On Netscape, when you click an entry in the help index, the topic above the correct topic in the current section of the help opens. To open the correct topic, click the index entry again.

2.7 Supported Characters for User and Group Names

The characters listed below cannot be used in group or user names.

2.8 Supported Characters for Server Commands

On UNIX, the characters listed below cannot be used in combination with any server commands:

We recommend that you place all complex server commands in a script file and reference the script from the Mover command fields.

2.9 UNIX: rundmcm.sh and rundmcli.sh Script Errors When Deploying Dimensions Files

When deploying files that are stored in Dimensions, deployments may fail with errors indicating that the sed and dirname commands could not be found. For example, the activity log may display an error such as the following:

/Mover_inst/changemanmover/dim/rundmcli.sh: sed: not found
/Mover_inst/changemanmover/dim/rundmcli.sh: dirname: not found

If you encounter this error, you must manually edit the script files to include their correct location in the PATH environment variable. These files typically reside in the /usr/bin directory. To correct this issue:

  1. Locate the rundmcli.sh and rundmcm.sh files. They are typically located in the <Mover install directory>dim directory.
  2. Open the files in a text editor.
  3. Add the location of the files to the PATH environment variable, near the top of the file. For example:
    PATH=${PATH}:/usr/bin
    DIM_ROOT=${INSTALL_ROOT}
  4. Save the files.

To TOC

 

Copyright © 2001-2007 Serena Software, Inc. All rights reserved.