How to move a StarTeam 2005 Rel 2 Server Configuration

0 Likes

Problem:

How to move a StarTeam 2005 Rel 2 Server Configuration

Resolution:

  • Product Name: Starteam
  • Product Version: 2005 Rel 2
  • Product Component: N/A
  • Platform/OS Version: Windows-specific, but can be used with any supported OS

    Question:


    How to move a Starteam 2005 Rel 2 Server configuration to a new server? May also be used to replicate a server to test an upgrade before performing on production server.


    Answer:

    Overview:

    The StarTeam server configuration is comprised of three things:

    • The starteam-server-configs.xml file.
    • The entire repository.
    • A supporting database, Oracle, SQL, or MSDE.

    To move a StarTeam 2005 Rel 2 server from one physical system to another follow the process below.

    1. Install StarTeam 2005 Rel 2 on the target system. Make sure your StarTeam Server installation is at least Build 8.0.172, then download and install server patch 28, available here:

    • ftp://ftpd.borland.com/devsupport/starteam/8.0/2005R2Server28.zip

    If you do not have build 8.0.172, then you can download the most recent StarTeam Server build from

    2. Copy the entire repository and starteam-server-configs.xml to the target system. If the database is also being moved and will be run on the same physical system copy the database backup to the target system as well.

  • An easy way to determine the repository path is to highlight the server configuration and click on Configure Server in the Administration pane. Look on the General tab for "Attachments path:". The repository will, by default, be in the parent folder of the one listed there.

    3. Rename the starteam-server-configs.xml in the new StarTeam 2005 Rel 2 server installation and replace it with the starteam-server-configs.xml from the source system. To verify if this step was followed correctly the name of the server configuration that appeared in the Server Administration on the source system should now appear in the Server Administration menu on the target system. To find Server Administration on the same physical system where the StarTeam server is installed click "Start"->"Programs"->"StarTeam"->"StarTeam Server 2005 R2"-> "StarTeam Server". This will open a window titled "Server Administration". Edit the starteam-server-configs.xml file in it"s new location using notepad so that the line that reads "Repository Path" lines and "LogPath" reflect their new locations on the target server.

    4. Restore the database. This process will vary depending on database type, for SQL server there is a create backup/restore backup process, for Oracle EXP/IMP, and for MSDE the MSDE Admin Tool will need to be used.

    5. Within Server Administration on the target system highlight the server configuration and click menu item "Server" --> "Configuration Properties". Verify that the log file path has been changed to reflect your edit to the starteam-server-configs.xml file. Select the Database Connection Information tab and use the ODBC database name to create a new ODBC connection. This process will differ again depending on database type, for SQL or MSDE create a system DSN specifying the target database. For Oracle a new ODBC driver will need to be installed as described in Chapter 4 of the StarTeam 2005 Installation Guide: "Using StarTeam with Oracle". Regardless of the database type specified click "Verify" when the process is completed to confirm that the ODBC configuration has been created successfully. Click "OK" to close.

    6. From within Server Administration, highlight the server configuration and verify that the "Execution mode" is set to "Application". To do this click on menu item Actions, and check to see if Run as Service is unchecked. If not, click "Run as Service one time and the service will be removed from Windows Services.

    7. Start with overrride - With the StarTeam server configuration still highlighted click "Start with Override", either on the toolbar or using the menu (Actions --> Start with Override...". There will be fields for the TCP/IP protocol endpoint and attachments path. The default endpoint is 49201, and the attachments folder is stored within the repository. You can use any TCP/IP endpoint that you have available. StarTeam will NOT start if there is a conflict with this port.

    Note: If the Starteam server starts successfully verify that client connections allow files to be checked out. If the StarTeam server fails to start there should be an error onscreen and an entry in the server.en-us.log. Any mention of the Event Viewer can be safely disregarded.

    8. After the server starts correctly, you can add it to Windows Services. Shutdown the server Configuration, click the pruple Run as Service icon on the toolbar, enter the log on information, and then start the server. It will start as a service the next time the system is restarted using the TCP/IP endpoint you entered in the ocerride step.


    Author: Donnie Nix


    Last Update By: Daniel Rice
Old KB# 27982
Comment List
Related
Recommended