Serena® ChangeMan® DS Version 5.7.2
Readme File
Last updated on March 1, 2006

This file contains information on installing and using the current release of Serena® ChangeMan® DS. This file contains information that may not be included in other Serena documentation. The Fix Log for this release is published in Solution 5002619 on the Serena Support Web site.

To view the Master License Agreement, see MasterLicenseAgreement.

To contact technical support, go to support.serena.com.


Table of Contents

Part 1: ChangeMan DS Main Server, Clients, and Communication Agents
Part 2: Copyrights, Trademarks, and Acknowledgements

 

Part 1: ChangeMan DS Main Server, Clients, and Communication Agents

1.0 Supported Platforms

1.1 Main Server Platforms

1.2 Client Platforms

1.3 Communication Agent Platforms

1.4 Integrations

2.0 Pre-Installation and Database Requirements

2.1 Pre-Installation Requirements

2.2 Metadata Database Requirements

3.0 General Information

4.0 Known Issues

4.1 Installs

4.2 Upgrades

4.3 General

4.4 Product Integrations

5.0 Documentation Updates

5.1 Document Versions

5.2 Corrections and Additions

 

Part 2: Copyrights, Trademarks, and Acknowledgements

6.0 Copyright

7.0 Trademarks

8.0 U.S. Government Rights

9.0 Acknowledgements

 

 

Part 1: ChangeMan DS Main Server, Clients, and Communication Agents

Return to Contents


1.0 Supported Platforms

1.1 Main Server Platforms

1.1.1 Operating Systems Supported

The Main Server for ChangeMan DS is supported on:

1.1.2 Windows System Requirements

In addition to Operating System requirements, the system requirements for a ChangeMan DS Main Server on Windows are:

Windows Main Server Requirements

Pentium III 600 MHz processor

256 MB RAM (512 MB recommended)

400 MB disk space (excluding database requirements). Plan for growth if you have make configurations and have Production areas on this machine.

Temporary space should be at least twice the size of your largest file under control.

TCP/IP connections between all servers and clients involved in software change management

Java™ (Java 2 virtual machine, 100% compatible with Java Runtime Environment version 1.4.1_07 from Sun Microsystems). It is the responsibility of the System Administrator to make sure that Java 2 Runtime 1.4.1_07 is set up as the "primary" version of Java if more than one version is installed.

256 color or higher video display (for install purposes)

Administrator login

System or User Environment variables TEMP and TMP are both defined to point to the temporary directory, for example, C:\Temp.

1.1.3 UNIX System Requirements

In addition to Operating System requirements, the systems requirements for the Main Server on UNIX platforms are:

UNIX Main Server Requirements

400 MB disk space (excluding database requirements). Plan for growth if you have Make configurations and have Production areas on this machine.

200 MB disk space in the temporary directory. (Temporary space should be at least twice the size of your largest file under control.)

Java™ 2 Runtime Environment, version 1.4.1_07. It is the responsibility of the System Administrator to make sure that Java 2 Runtime 1.4.1_07 is set up as the "primary" version of Java if more than one version is installed.

256 color or higher video display (for install purposes)

TCP/IP connections between all servers and clients involved in software change management

Root login to the UNIX server

An active X Terminal Session running for the duration of time the server is running is required to use any Java or Web client access.

1.2 Client Platforms

1.2.1 Windows Client Operating Systems

The Windows client for ChangeMan DS is supported on:

 Note   If you enable the built-in firewall feature of Windows XP SP2, all ChangeMan DS executables should be added to the Exceptions list.

1.2.2 Java Client Operating Systems

The Java client for ChangeMan DS is supported on:

 Note   If you enable the built-in firewall feature of Windows XP SP2, all ChangeMan DS executables should be added to the Exceptions list.

1.2.3 Windows or Java Client System Requirements

In addition to Operating System requirements, the system requirements for a ChangeMan DS Windows client are:

Windows or Java Client Requirements

Pentium processor or higher

64 MB RAM recommended

100 MB disk space

Java 2 Runtime Environment 1.4.1_07 or 1.5 (1.4.2 for the Java client on HP-UX, AIX, or Sun systems)

It is the responsibility of the System Administrator to make sure that Java 2 Runtime 1.4.1_07 is set up as the "primary" version of Java if more than one version is installed.

Microsoft Internet Explorer 6.0 (with Java enabled)

256 color or higher video display (for install purposes)

System or User Environment variables TEMP and TMP are both defined to point to the temporary directory, for example, C:\Temp.

1.2.4 Web Browser Client Requirements

The following are the systems requirements to use the Web browser client:

Web Browser Client

Microsoft Internet Explorer 6.0 (with Java enabled)

Java 2 Runtime Environment, version 1.4.1_07 or 1.5 (1.4.2 on HP-UX, AIX, or Sun systems)

It is the responsibility of the System Administrator to make sure that Java 2 Runtime 1.4.1_07 is set up as the "primary" version of Java if more than one version is installed.

256 color or higher video display (for install purposes).

1.3 Communication Agent Platforms

1.3.1 Operating Systems Supported

Communication Agents for ChangeMan DS are supported on:

1.3.2 Windows System Requirements

The following are the systems requirements for the Communication Agent on Windows platforms.

Windows Communication Agent Requirements

TCP/IP connections among all systems involved in software change management

32 MB RAM

5 MB disk space

Note: The Communication Agents generate temporary files that are cleaned up after use. Space reserved for temporary files should be twice the size of the largest file under control.

Administrator login

System or User Environment variables TEMP and TMP are both defined to point to the temporary directory, usually C:\Temp.

1.3.3 UNIX System Requirements

The following are the systems requirements for the Communication Agent on UNIX platforms.

UNIX Communication Agent Requirements

TCP/IP connections among all systems involved in software change management

Root login to the UNIX server

On OS/390 USS, root is not a default user in the same way it is on other UNIX platforms. To use root, make sure it:

  • has a ID of zero (0).

  • has full access to the installation directory structure.

  • is a member of the BPX.DAEMON facility class profile in RACF.

Also, the program VCS_AGENT must be marked as PROGRAM CONTROLLED. The status can be determined by a "p" in the extended attribute.

1.3.4 OS/400 System Requirements

The following are the systems requirements for the Communication Agent on OS/400 platforms.

OS/400 Communication Agent Requirements

Private Address Space Environment system (PASE) must be installed. Depending on the version of your OS, this may be a separate option. Contact IBM for more information.

TCP/IP installed.

QP2Tools should be installed

QP2Shell

Integrated File System

1.4 Integrations

1.4.1 Serena TeamTrack

ChangeMan DS 5.7.2 integrates with TeamTrack versions 6.3 and 6.5.

1.4.2 Borland JBuilder

ChangeMan DS 5.7.2 integrates with JBuilder versions X and 2005

1.4.3 WebSphere Application Developer, Rational Application Developer, and Eclipse

ChangeMan DS 5.7.2 integrates with WebSphere Application Developer 5.1, Rational Application Developer 6.0, and Eclipse versions 3.1 and 3.2.

1.4.4 Microsoft Visual Studio .Net

ChangeMan DS 5.7.2 integrates with Visual Studio .Net versions 2003 and 2005.

1.4.5 Sybase PowerBuilder

ChangeMan DS 5.7.2 integrates with PowerBuilder versions 9 and 10.

Return to Contents


2.0 Pre-Installation and Database Requirements

2.1 Pre-Installation Requirements

The following should be configured before you begin installation:

In Microsoft SQL Server Enterprise Manager, under the Security tab, ensure SQL Server and Windows NT is selected for authentication.

2.2 Metadata Database Requirements

2.2.1 General Database Requirements

The following are configuration requirements that apply to all databases:

General Database Requirements

The database requires 150 MB of disk space for the initial installation. Plan for a growth factor of 100 MB per year.

The database must be case sensitive. When installing Microsoft SQL Server, the Dictionary Sort Order and the server must be installed as case sensitive.

The database must not have a dash in the database name.

If upgrading with Microsoft SQL Server, you must have enough free space for the SQL Transaction Log in addition to other free space requirements. In general, this should be half the size of your existing database.

2.2.2 Database Requirements on Windows

The following are the system requirements for the metadata database options on Windows platforms:

Database Requirements on Windows

Microsoft® SQL Server™ 2000 or 2005; must be installed CASE SENSITIVE

Oracle® database 9i or 10g

IBM DB2 Universal Database™ 8.1, or 8.2.

2.2.3 Database Requirements on UNIX or Linux

The following are the system requirements for the metadata database options on UNIX or Linux platforms:

Database Requirements on UNIX or Linux

Oracle® database 9i or 10g

IBM DB2 Universal Database™ 8.1, or 8.2.

Return to Contents


3.0 General Information

Review the following information before you begin:

See the Serena® ChangeMan® DS Command Line Interface Guide for detailed documentation on the command line utilities

Return to Contents


4.0 Known Issues

4.1 Installs

Occasionally on Linux, when you execute the setup.sh script, you receive an error message regarding the available space even though there is enough space on the system to install ChangeMan DS. If this happens, run setup.jar instead using the following command:



 
java -jar setup.jar 

If you experience problems with the user interface of the installer using Linux (particularly the RedHat ES and AS distrubutions), these problems can typically be resolved by using Java Runtime Environment version 1.3.1 to run the java-based installer for ChangeMan DS. This is freely available from Sun Microsystems at http://java.sun.com/products/archive/.

4.2 Upgrades

You should save your configuration files to a temporary location before running the upgrade.

Upgrades are supported from ChangeMan DS 5.6.1, 5.7.0, and 5.7.1.

4.3 General

To maintain consistency in license administration, Serena recommends that all ChangeMan DS areas on a particular host be configured using either IP address or host name, but not a mixture of both.

Right-click menu options in the Java and Web browser clients may be enabled regardless of whether the option is eligible to be performed.

If you edit or compare a Microsoft Word document in the Java or Web browser client, errors may occur due to the binary nature of the files. For editing or comparing Word documents, use the Windows client.

(DEF74031) If a different version of the Oracle JDBC driver than is supplied with ChangeMan DS is installed on machine hosting your database, the default install time for all packages is 12:00AM.

If you have a Java runtime version earlier than 1.4.1 installed on a Windows Main Server, you may receive the following message during an installation when the installer tries to install Java 1.4.1:

An installation support file 'C:\Program Files\Common Files\Installs\engine\6\Intel32\objectps.dll' could not be installed.

Cancel from the Java installation and continue with the ChangeMan DS installation. After the ChangeMan DS installation is complete, install Java 1.4.1 from the ChangeMan DS Installation CD by running j2re-1_4_1_07-windows-i586.exe.

4.4 Product Integrations

When you upgrade your ChangeMan DS client, the source control provider setting is not retained. If you are using ChangeMan DS as your source control provider through SCC integration, you must execute IDEReg.exe located in the ChangeMan DS Client subdirectory to set ChangeMan DS as your source control provider.

(DEF90023)If you are using WebSphere Application Developer 6, the ChangeMan DS preferences are not added to the Team node of the wrokbench's Preferences dialog. To enable the Team node in the Preferences dialog:

  1. Select the Workbench, Capabilities node

  1. Dnable "Core Team Support" under the "Team" node and click OK.

Return to the Preferences dialog and the "Team" node should now appear.

Return to Contents


5.0 Documentation Updates

5.1 Document Versions

Documentation for ChangeMan DS 5.7 is provided on your product installation CD and is posted on Serena's Support site.

 Note   Some documents have not been updated since the 5.7 or 5.7.1 releases of ChangeMan DS. The appropriate versions of the documents shipping with 5.7.2 are:

Document

Product Version

Serena® ChangeMan® DS Administrator's Guide

5.7.1

Serena® ChangeMan® DS Command Line Interface Guide

5.7.1

Serena® ChangeMan® DS Conversion Guide

5.7.1

Serena® ChangeMan® DS Installation Guide

5.7.1

Serena® ChangeMan® DS Integration Guide for Borland® JBuilder®

5.7

Serena® ChangeMan® DS Integration Guide for Eclipse Workbench and IBM® WebSphere® Studio

5.7.1

Serena® ChangeMan® DS Integration Guide for Microsoft® Visual Studio® .NET™

5.7

Serena® ChangeMan® DS Integration Guide for Sybase® PowerBuilder®

5.7

Serena® ChangeMan® DS User's Guide

5.7.1

Serena® TeamTrack® VersionBridge for Serena® ChangeMan® DS

5.7

5.2 Corrections and Additions

Updates to the documentation that are not in the published documents for this release are listed in this section. Updates to the published documentation are maintained between product releases in Documentation Solutions in the Serena Knowledgebase.

5.2.1 ChangeMan DS Integration Guide for Microsoft Visual Studio .NET™

Offline changes are now supported by the ChangeMan DS integration for Microsoft Visual Studio .NET. When you cannot access the ChangeMan DS server to perform a checkout, you may disable the Read-Only attribute on the file and change it locally on the client. Then, when access to the server becomes available, you may perform an "offline check out" against the server version of the file retroactively, without overwriting your local changes. Check in the modified file as usual to upload your changes to the host and increment the file version number.

5.2.2 Serena® ChangeMan® DS Administrator's Guide

(TSK06255)In "Restoring Files Removed from Control," -log is no longer valid for the actions -ala and -alf when restoring files using the command line interface.

The following information should be added to the "Advanced Configurations" chapter under "Other Configurations":

If TeamTrack is setup up to work with NT Challenged Response, enable TTNTChallenge in the vcs_serv.ins file.

5.2.3 VersionBridge for Serena® ChangeMan® DS

See Serena TeamTrack for the TeamTrack versions supported for integration with this release.

The following information should be added to this document:

If TeamTrack is setup up to work with NT Challenged Response, enable TTNTChallenge in the vcs_serv.ins file.

5.2.4 Serena® ChangeMan® DS Integration Guide for Eclipse Workbench and IBM® WebSphere® Studio

Page 91 under Project Merge Operations states: "This entry is optiona" for the Common Ancestor. This is now required and not optional.

 

Part 2: Copyrights, Trademarks, and Acknowledgements

Return to Contents


6.0 Copyright

Copyright © 1998-2006 SERENA Software Inc. All rights reserved.

This document, as well as the software described in it, is furnished under license and may be used or copied only in accordance with the terms of such license. Except as permitted by such license, no part of this publication may be reproduced, photocopied, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, recording, or otherwise, without the prior written permission of Serena. Any reproduction of such software product user documentation, regardless of whether the documentation is reproduced in whole or in part, must be accompanied by this copyright statement in its entirety, without modification.

This document contains proprietary and confidential information, and no reproduction or dissemination of any information contained herein is allowed without the express permission of Serena Software.

The content of this document is furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by Serena. Serena assumes no responsibility or liability for any errors or inaccuracies that may appear in this document.

Return to Contents


7.0 Trademarks

Serena, TeamTrack, and ChangeMan are registered trademarks of Serena Software, Inc. The Serena logo is a trademark of Serena Software, Inc.

All other products or company names are used for identification purposes only, and may be trademarks of their respective owners.

Return to Contents


8.0 U.S. Government Rights

Any Software product acquired by Licensee under this Agreement for or on behalf of the U.S. Government, its agencies and instrumentalities is "commercial software" as defined by the FAR. Use, duplication, and disclosure by the U.S. Government is subject to the restrictions set forth in the license under which the Software was acquired. The manufacturer is Serena Software, Inc., 2755 Campus Drive, San Mateo, CA 94403.

Return to Contents


9.0 Acknowledgements

Portions of this product are redistributed unmodified in binary form from the Eclipse Organization. Source and binary code is available from http://www.eclipse.org/.

Portions of this product are copyrights of other corporations or individuals, as follows:

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code and documentation must retain the above copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. All advertising materials mentioning features or use of this software must display the following acknowledgement:

This product includes software developed or owned by Caldera International, Inc.

4. Neither the name of Caldera International, Inc. nor the names of other contributors may be used to endorse or promote products derived from this software without specific prior written permission.

USE OF THE SOFTWARE PROVIDED FOR UNDER THIS LICENSE BY CALDERA INTERNATIONAL, INC. AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS 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 CALDERA INTERNATIONAL, INC. 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.

Permission to use, copy, modify, and distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.

THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

Sponsored in part by the Defense Advanced Research Projects Agency (DARPA) and Air Force Research Laboratory, Air Force Materiel Command, USAF, under agreement number F39502-99-1-0512.

The Regents of the University of California. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. Neither the name of the University nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS 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 THE REGENTS OR 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.

Copyright (c) 1998-2005 The OpenSSL Project. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. All advertising materials mentioning features or use of this software must display the following acknowledgment:

"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)"

4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact openssl-core@openssl.org.

5. Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their names without prior written permission of the OpenSSL Project.

6. Redistributions of any form whatsoever must retain the following acknowledgment:

"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)"

THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``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 THE OpenSSL PROJECT 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.

This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com).

Return to Contents


End Readme
Copyright © 2005 Serena Software, Inc. All rights reserved.