Borland® StarTeam® 2006 Release Notes

Last updated: December 14, 2006

Welcome to Borland® StarTeam 2006! This file contains important information that might not appear in the documentation and covers the StarTeam Server for Windows, Cross-Platform client (including File Compare/Merge and View Compare/Merge), StarTeam Workflow Extensions, StarTeamMPX, and StarTeam Layout Designer. Read this file in its entirety.

For an overview of the new features in the current release, see the What's New topic in StarTeam Help or Administering and Using StarTeam (AdministeringAndUsingStarTeam.pdf).

Note: The information in this readme represents the known issues at the time of this release. For late-breaking information that may become available after the release, check the Borland web site for the most recent version of this readme: http://info.borland.com/techpubs/starteam.

StarTeam Server for Windows

System Requirements/Prerequisites

In addition to the following system requirements, StarTeam Server uses Sun Microsystems Java Virtual Machine 1.5.0_09, which is automatically installed.

Note: You can access the StarTeam Cross-Platform client with this release of StarTeam Server and StarTeam Server 2005 Release 2. This makes it easier to roll out your upgrades of the client after installing the server.

Top

Installation Instructions

Important: If you are upgrading from a previous version of StarTeam Server, you MUST review the upgrade instructions in the StarTeam Installation Guide (Install_en.pdf). There are some steps that you must complete in order for the upgrade to complete successfully. Failure to complete these steps can cause the upgrade to fail.

Top

Known Issues

Installation Issues

• The installer does not work on some Windows 2003 machines due to Data Execution Prevention (DEP). DEP is software that Microsoft has integrated with Windows to prevent viruses from installing. The workaround is to add the installer to the DEP exclusion list.
  1. Right click on My Computer, and select Properties.
  2. Click the Advanced tab, and click Settings to adjust performance settings. The Performance Options dialog box opens.
  3. Click the Data Execution Prevention tab.
  4. Select the option to add programs to the DEP list.
  5. Click OK to close the dialog box when finished.
• Canceling an Installation
  If you cancel the installation of the StarTeam client after you have already installed the StarTeam Runtime, and then install the StarTeam client again, letting it finish, at the end of the installation you will not be prompted to reboot the computer, even though you need to.
• Seeing PATH Warning during Installation
  As you install the product on Windows, the StarTeam SDK runtime may also be installed. If an error indicates that you must manually edit the PATH system variable and refers you to the readme file, the length of the PATH variable on the target computer has exceeded the Windows maximum.
  
  You must shorten the text and either include the new path for the StarTeam SDK runtime or run the StarTeam installer a second time. The PATH system variable cannot exceed 1024 characters. The 1024 characters must include the StarTeam SDK runtime paths which, by default, are "C:\Program Files\Borland\StarTeam SDK 2006\bin" and "C:\Program Files\Borland\StarTeam SDK 2006\lib". CAUTION - removing text from the Windows path may cause undesired application failure.
  
  It is very important to be certain that a path is obsolete before manually deleting it from the PATH system variable. If you are uncertain, please use the obsolete application's uninstaller and/or consult your system administrator before taking any action.
• Although Windows XP is not an officially supported platform for StarTeam Server, you can still install StarTeam Server on Windows XP systems if you have installed the latest Windows XP Service Packs.
• Uninstalling from Windows Systems
  StarTeam Server, StarTeam Cross-Platform client, and StarTeamMPX use InstallAnywhere for installation. If you encounter one of the following error messages when uninstalling this product from a Windows system (such as 2003 or XP Pro):

  "Can't launch executable. Could not find a suitable Java Virtual Machine on your system."

  or

  "Windows error 3 occurred while loading the Java VM."

  you may need to install JRE 1.5.0_09 or earlier from http://java.sun.com/javase/downloads/index.jsp. A copy of it is also on the StarTeam CD in the Utility folder.

Purge Issues

• Purging data takes longer than in previous releases as additional database queries are required to run to resolve MD5 sharing.
• Before purging data, Borland recommends running either starteam_oracle_compute_stats.sql (for Oracle) or starteam_sqlserver_update_statistics.sql (for Microsoft SQL Server). By default, these scripts install in the C:\Program Files\Borland\StarTeam Server 2006\DBScripts\Oracle_Scripts or C:\Program Files\Borland\StarTeam Server 2006\DBScripts\Sqlserver_Scripts folders.

Database Issues

Microsoft SQL Server/MDSE

• When creating a Microsoft SQL Server database for use with StarTeam, the database name should conform to the following guidelines:
• begin with a letter
• contain letters and numbers only
• avoid using spaces in the name
• Not be a SQL reserved word such as create, delete, if, then, else, or goto.
  The Server Tools database options may fail to run for databases with names that do not follow these guidelines.
• If you use a SQL Server database that is case-sensitive, the server might not start your server configuration after an upgrade. This can be fixed, but you will need assistance from technical support.

Oracle

• When creating a schema user for use with a new server configuration and/or before upgrading old server configurations, make sure that the schema user has the following Oracle privileges so that StarTeam Server can create labels and perform other operations successfully:
• create procedure
• create sequence
• create session
• create table
• create trigger
• create type
• create view
• unlimited tablespace
• For 9i installations using Automatic Undo Management, make sure that the undo retention time is defined correctly.

StarTeam Server, Client, and SDK Issues

Native-II Vault

• Disk volumes used for hives by one StarTeam server configuration should not be used by any other process including other StarTeam server configurations.
• Hive threshold limits should never be set to 100%. You should never totally fill a drive anyway, but when a hive is set to 100% and runs out of disk space, the server still checks this hive when it is this hive's turn in the hive rotation. The resulting error is "no space left on device". The workaround is to clear the "Allow new archives" check box in Hive Manager for this hive.

Evaluations

Borland allows you to extend the evaluation period for StarTeam Server by contacting www.borland.com/company/contact/where_to_buy.html and obtaining an evaluation extender key.

StarTeam Sample Server Configuration

If you plan to use the sample server configuration, StarDraw, and want to run it as a service, you may have to start it once as an application, shut it down, and then set it as a service.

4GT RAM Tuning

If your StarTeam Server runs on Windows Server 2003, either Enterprise Edition or Datacenter Edition, you can use Microsoft's 4GT RAM Tuning to give the StarTeam Server process the use of 3 GBs of memory. To enable this feature the /3GB switch needs to be added to the Boot.ini file.

Please see: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/memory/base/4gt_ram_tuning.asp for more information on setting this switch.

For example: "multi(0)disk(0)rdisk(0)partition(2)\WINNT="Microsoft Windows 2000 Advanced Server" /3GB /fastdetect

The use of 4GT on Windows Server 2003, Standard Edition, can give the appearance of a 3 GB range of user-mode memory, but the memory from 0x80000000 through 0xBFFFFFFF is actually not usable.

For more details, see http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/techref/en-us/Default.asp?url=/resources/documentation/windowsserv/2003/all/techref/en-us/w2k3tr_4gt_how.asp.

StarTeam Server and Windows XP

StarTeam Server can run on Windows XP for evaluation or demoing purposes, but there are some complications.

Opening Ports on Windows XP

If you are using a firewall, you have to open the port number on Windows XP SP2. This is 4467 by default. If you don't open this port in the Windows firewall, you cannot connect to the server.

You will run into a similar problem for an MPX-enabled StarTeam Server. You will need to open the ports that are used by MPX. For example, the default port for Message Broker is 5101, and the default port for Multicast Service is 5104. If you are using these ports you need to open them.

To open a port:

1. Start the Control panel and select Windows Firewall.

2. Select the Exceptions tab.

3. Select 'Add Port' and enter in any name and the appropriate port number.

4. Press OK closing all of the dialogs.

Security

If you run StarTeam Server on a Windows XP Professional computer, the person who creates and/or starts the first server configuration becomes the only person who can create and/or start server configurations. We provide the GrantAdmin utility that allows other administrators to create and start server configurations.

The utility is installed in the server installation folder. It must be run by the user who installed/started the server. It does not require any arguments. The GrantAdmin utility grants access rights to the key container to the other administrators. Otherwise, only the administrator who created the key container (that is started the server for the first time) has the rights needed to create and start server configurations.

Blocking

If you run StarTeam Server and the StarTeam Windows client on Windows XP SP2 with all updates, running the StarTeam Server or the StarTeam Toolbar for the first time can result in a Server_Blocked or Toolbar_Blocked error message. This is not a problem. Click Unblock.

MDAC

StarTeam Server needs MDAC 2.8 and Windows XP SP2 comes with that version of MDAC. During the installation of StarTeam Server, you may see a message about MDAC 2.8 being incompatible with this version of Windows. This is not a problem. Click Cancel.

Running the Server as a Service

If you are running StarTeam Server as a service, you may see the Windows error 2186 indicating that the service is not responding to the Start Control function. Windows 2003 displays this message when a service takes longer to start than expected. Depending on the size of your database, StarTeam Server may take longer to complete the startup process than Windows expects. Usually StarTeam Server starts without a problem (despite this error message). However, to be sure, run the Event Viewer (Start\Programs\Administration Tools (Common)\Event Viewer. Check the most recent events for StarTeam Server. You will probably see: StarTeam Server Service started. If not, you will find the reason why it did not start or start properly and take appropriate action.

If an MPX-enabled StarTeam Server runs as a service, the Message Broker or Multicast Services must start before the StarTeam Server service. Usually it does. If StarTeam Server fails to enable MPX and the Message Broker or Multicast Service are on the same computer, you may want to make the StarTeam Server service dependent on the Message Broker or Multicast Service service. Check with your system administrator before using one of the following techniques:

To set up a service dependency for Windows 2003:

1. Click Start>Run from the Start menu.

2. Type Regedt32.

3. Click OK.

4. Select HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\StarTeamServer-configName

5. Select Edit>New>Multi-String Value.

6. Set the Value Name to DependOnService.

7. Double-click the DependOnService Value to open the Data window.

8. Enter your StarTeam Message Broker or StarTeam Multicast Service service name into the Data window. (Example: StarTeam Message Broker 6.7).

StarTeam SDK Path

Uninstalling the SDK runtime does not reset the installation path-unless all the versions of the runtime have been uninstalled. A user can manually change the path in the setup.ini file if desired. The setup.ini file for StarTeam will always be under "Documents and Settings". However, it may be under All Users or the specific user. Also, depending on when that user started using StarTeam, the setup.ini may be in the Application Data\Starbase or Application Data\Borland\StarTeam folder. It may be easier to search all Documents and Settings for a setup.ini file that contains "StarTeam SDK". The following is an example of setup.ini:

[StarTeam SDK Folders]

Programs=C:\Program Files\Borland

Java=C:\Program Files\Borland\Java

Time Issues

StarTeam Server stores time stamps in UTC (also known as Universal Coordinated Time, Greenwich time, or Zulu time) format and adjusts the time stamp for the time zone that the computer specifies. For example, if a file is saved and checked in at 5 P.M. in California, its time stamp in California is 5 P.M. However, its time stamp on a computer in New York would be 8 P.M., the time it was in New York when the file was checked in. When a file is modified, the time stamp reflects that of the operating system. This means that if a file is checked in by a user in one time zone and modified by a user in another, the file's time stamp may appear to be earlier than the most recently checked-in revision. This does not affect file statuses within StarTeam because the UTC times are used to calculate statuses.

If you are in an area that observes Daylight Savings Time (DST), the StarTeam status bar may display the incorrect time when rolling back a view (View\Select Configuration\Configuration As Of). For example, if you are currently in DST and rollback the view to a point in time prior to DST, the time display in the status bar (lower left corner of the StarTeam window) will be ahead by one hour. If you are not currently in DST and rollback the view to a point in time during DST, the time in the status bar will be behind one hour.

Miscellaneous Issues

• Opening Web Help
  On Windows XP SP2, opening Web Help (Help > Help Topics) requires you to change your IE security setting to view the Web Help. Refer to http://www.psychpage.com/tech/damnbar.html
  Workaround:
  1. Open Internet Explorer.
  2. Select Tools >Internet Options.
  3. Select the Advanced tab.
  4. Scroll down to the Security options.
  5. Select the option to Allow active content to run in files on My Computer.
• Microsoft Project Tasks
  MSP tasks imported into a StarTeam Server should not have work records that occur before the start date. If they do, the work hours will not be subtracted from the remaining work.
• Disk-imaging Software
  Using Disk-imaging Software In StarTeam: Disk-imaging software, such as Norton Ghost, does not work well with StarTeam. StarTeam needs to be installed on each workstation. StarTeam creates a unique connectionmanager.ini file for each workstation. The connectionmanager.ini is used to identify one workstation from another. If you use disk-imaging software, this .ini file is copied, and when the image is installed to another computer, there are now two or more workstations with the same .ini file. This can lead to unusual status problems.
• Logging in using previously logged on user
  When working in the Server Administration tool and logging in using a previously logged on user, an error displays indicating that "A user has already been logged on for this session." As a workaround, close and reopen the Server Administration tool and log on again.
  

Top

Known Documentation Issues

The following are known documentation issues related to the StarTeam Server for Windows.

• The documentation incorrectly states that the Security Administrators group receives email notifications about locked out users. The server does not send email to the Security Administrators on account lockout.
  This is stated incorrectly in the following help topics: Configuring the Number of Logon Attempts, Setting the Number of Log-on Attempts, and User and Group Configuration Overview.
• The help reference topic, Report Archives Command-line Options erroneously lists a -type parameter and does not list the -ForceNative2 option. Refer to the StarTeam 2006 Installation Guide (Install_en.pdf) for complete details about working with the Report Archives utility.
• The What's New help topic, Discontinued Features in StarTeam inaccurately advises users to upgrade to Oracle 9.2.0.4. The supported Oracle version is 9.2.0.5.

Top

Limitations

The following are limitations in StarTeam Server for Windows.

• You cannot upgrade to this release of StarTeam Server unless you have converted all Native-I archives to Native-II archive format. For more information, refer to the StarTeam 2006 Installation Guide (Install_en.pdf).
• You can still use the StarTeam 2005 R2 Windows client to wrap PVCS 6.8 and VSS 6c project files; however, you must convert those files to the StarTeam Native-II format before using this release of StarTeam Server and its clients.
• Database support for IBM DB2, Oracle 9.1, and MS SQL Server 7.0 has been removed in this release. You must upgrade your database to a currently supported version (MSDE 2000 SP2, MS SQL Server 2000 SP4, or Oracle versions 9.2.0.5 or 10.1.0.4.0) before upgrading StarTeam Server.
• The License Usage Report was removed for this release. It was a vestigial report that was used in older versions of the product to report usages with client licensing, and it was removed since StarTeam no longer supports client-side licenses. The license is registered with StarTeam server.

Top

StarTeam Cross-Platform Client (including File Compare/Merge and View Compare/Merge)

This release brings an end-of-life to the StarTeam Windows, Web Edition CR-only, and StarDisk clients. The Cross-Platform client has been updated to support many of the the Windows client features.

File Compare/Merge is a graphical compare/merge tool installed with the Cross-Platform client. It enables you to compare a file dynamically with the file in the repository, and manually or automatically merge the content of the two files.

Also installed with the Cross-Platform client, View Compare/Merge is the tool you use to compare two views or subsets of two views. As part of the process, you can merge corresponding items and make new revisions of those items in the target.

System Requirements/Prerequisites

The StarTeam Cross-Platform client is implemented in Java and can be installed on Microsoft Windows systems and any system that supports Sun Microsystems Java Virtual Machine 1.5.0_09. However, only the following Java-enabled platforms have been tested for compatibility with this product by Borland:

Top

Installation Instructions

Please see the PDF file, StarTeam 2006 Installation Guide (Install_en.pdf). StarTeam documentation can be found on the product CD. If the product CD is not available, you can find documentation on the Borland web site at this URL: http://info.borland.com/techpubs/starteam/.

Top

Known Issues

The following are known issues found in the Cross-Platform client and View Compare/Merge.

Cross-Platform Client Issues

• On Windows XP SP2, opening Web Help (Help > Help Topics) requires you to change your IE security setting to view the Web Help. Refer to http://www.psychpage.com/tech/damnbar.html
  Workaround:
  1. Open Internet Explorer.
  2. Select Tools >Internet Options.
  3. Select the Advanced tab.
  4. Scroll down to the Security options.
  5. Select the option to Allow active content to run in files on My Computer.
• When setting the component order (Tools > Personal Options > Workspace), the Audit tab should not be used as the first tab in the component order list since loading it first can take a very long time.
• Uninstalling from Windows Systems:
  StarTeam Server, StarTeam Cross-Platform client, and StarTeamMPX use InstallAnywhere for installation. If you encounter one of the following error messages when uninstalling this product from a Windows system (such as 2003 or XP Pro):

  "Can't launch executable. Could not find a suitable Java Virtual Machine on your system."

  or

  "Windows error 3 occurred while loading the Java VM."

  you may need to install JRE 1.5.0_09 or earlier from http://java.sun.com/javase/downloads/index.jsp. A copy of it is also on the StarTeam CD in the Utility folder.

• Take care when selecting items in groups as selected items are highly sensitive to mouse movement.
• On some Windows XP systems, the display font may appear distorted on the Pre-Installation Summary page of Cross-Platform client's Installer. Also, the text "InstallAnywhere by Macrovision" is chopped off on the bottom of the installation screens. There is no known workaround for this issue.
• Use the Folder tab to selectively include or exclude folders from a project. Using the New Folder Wizard to selectively include or exclude folders from the project may generate errors.
• When using the embedded file compare feature (Tools > File Compare) to display and compare text files at the bottom of the window in the Cross-Platform client, the first time that you use these panes, the progress bar may update continuously. Closing and reopening the Cross-Platform client solves this problem.
• As you install the product on Windows, the StarTeam SDK runtime will also be installed if necessary. If an error indicates that you must manually edit the PATH system variable and refers you to the readme file, the length of the PATH variable on the target computer has exceeded the Windows maximum. You must shorten the text and either include the new path for the StarTeam SDK runtime or run the StarTeam installer a second time. The PATH system variable cannot exceed 1024 characters. The 1024 characters must include the StarTeam SDK runtime paths which, by default, are "C:\Program Files\Borland\StarTeam SDK 2005 R2\bin" and "C:\Program Files\Borland\StarTeam SDK 2005 R2\lib". CAUTION - removing text from the Windows path may cause undesired application failure. It is very important to be certain that a path is obsolete before manually deleting it from the PATH system variable. If you are uncertain, please use the obsolete application's uninstaller and/or consult your system administrator before taking any action.
• Known issues with Look and Feel settings:
• The StarTeam Cross-Platform client uses the system default "look and feel" setting when installed. If the setting is changed to "Borland" it is necessary to end the current StarTeam Cross-Platform client session and open a new session for the changes to properly take effect.
• Data does not display correctly when the GTK look and feel is selected (available on Linux and Solaris). The GTK or GTK+ look and feel should never be used with StarTeam Cross-Platform client.
• Japanese characters do not display properly when the Japanese localized version of the product is installed on the English version of the Windows operating system and the Windows look and feel is used (default setting). The workaround is to select a different look and feel.
• In some cases when performing a local file status repository purge operation to remove abandoned status records the preview detail is not displayed. A workaround is not available. Options are to either cancel and not to perform the operation or to purge all abandoned records without previewing.
• If the name of a folder in a view is 248 characters or greater the New Folder Wizard dialog will truncate causing the OK and Cancel buttons to be beyond the visible window. The workaround is to use the tab key to focus on the buttons.
• On all operating systems other than MS Windows, the command-line arguments are not properly understood when starting StarTeam Cross-Platform client via the symbolic link. The script changes its working directory to the scripts location before processing the arguments, thus if you use a relative path for the shortcut file it cannot find the shortcut file.
• See History access right is required to checkout tip revisions of files. The version of the file must be specified and this requires see history access rights.
• When performing a move operation it is necessary to select data and to 'grab' the data using two click actions. First select an item or multi-select several items, release the mouse button and then click and drag to move data.
• Please be sure that the paths to your working folders do not exceed the limits set by your operating system. If the path to a working folder contains more characters than the operating system allows, Java attempts to create the folder but may not. When there is an error, Java may not provide an error message for the Cross-Platform client. In this case, nothing can be logged or displayed to the user. When there is an error, the effects are dependent on the operating system.
  

View Compare/Merge Issues

• A View Compare/Merge session saved by the Cross-Platform client cannot be resumed and committed by the View Compare/Merge Utility when the target view requires a process item.
• Double byte characters are not displayed properly in View Compare/Merge summary or difference reports. However, when reports are opened in a browser, such as Internet Explorer the characters are displayed correctly.
• Whenever you have two shares of the same folder at the same branch and revision level, View Compare/Merge loses track of one of the folders. As a result, one of the source folders that should be matched looks like it is new. View Compare/Merge recommends to "Share" the items in that folder, when in fact, View Compare/Merge should not have detected any differences. If you do not catch this and commit the session, View Compare/Merge creates new shares of items that should not be there. It is recommended that you carefully review the Test perspective as there will be several folders with two copies of each file.
• A double renamed-and-moved folder causes an uncommitable View Compare/Merge session. This is caused by an unresolved difference being moved from one folder to another causing View Compare/Merge to indicate that the state for the previous parent folder contains unresolved differences. If you find yourself in this situation, you can still commit the View Compare/Merge session by switching to the Compare perspective in View Compare/Merge where the Commit button is enabled.
• If you run into a Java out-of-memory error when comparing very large projects with View Compare/Merge, edit the StarTeamCP.stjava file and increase the heap size for the JVM by changing the line -Xmx512m to -Xmx768m.

Top

Known Documentation Issues

The following are known documentation issues related to the StarTeam Cross-Platform client.

• Detail pane sample templates are installed with the Cross-Platform client under the samples/details-templates folder. This was not noted in the procedural help topic, Customizing the Detail Panes in the Cross-Platform Client.
• Although it exists, the sample Folder detail template is not mentioned in the procedural help topic, Customizing the Detail Panes in the Cross-Platform Client or in the Detail Pane Customization Reference topics.
• The Internal Identifier for the change request field is incorrect in the Change Request Fields help reference topic. It should be PathRevision instead of ParentRevision.
• The reference help topic, Table of Common Operations is missing some text. In rows one and two, each of the blank fields should reflect a value of No. In row 3, you can create shortcuts to requirements.
• The client command-line options described in the Reference section of StarTeam Help (Reference > Client Command-line Operations) are not completely synchronized with the options that display when you run help for these commands at the command line. While most options are listed in the help topics, to get a complete list, run the help command for a desired option at the command line. For example, you can enter stcmd label -? at a command prompt to obtain a list of help options for the label command.
• The documentation for the stcmd label option (Reference > Client Command-line Operations > Create Labels: stcmd label) should indicate that you can create a view label based on a promotion state only when the promotion state is set to a label and not set to Current.

Top

Limitations

The following are limitations in the Cross-Platform client.

• When editing a change request, you can move from New to Fixed states in the properties dialog. To move to subsequent states, you must click Apply.
• Imported tasks from Microsoft Project should not have work records that occur before the start date. If they do, the work hours will not be subtracted from the remaining work.
• You can still use the StarTeam 2005 R2 Windows client to wrap PVCS 6.8 and VSS 6c project files; however, you must convert those files to the native format before using this release of StarTeam Server and its clients.
• Although the file is being checked in, progress reporting when checking in a large file does not work. The progress bar does not increment.
• On non-Windows systems, jsafe.jar automatically installs with the Cross-Platform and Universal Edition (stcmd) clients and is used for encryption. jsafe.jar is required if you are running standalone scripts on non-Windows platforms, and you need to establish an encrypted connection to a StarTeam Server. Without jsafe.jar installed, you will receive a meaningful "encryption algorithm not supported" message. If you receive this error, you should install the Cross-Platform client as a workaround.

Top

StarTeamMPX

StarTeamMPX provides a publish/subscribe messaging architecture for StarTeam Server. StarTeamMPX accelerates the velocity of information exchanged between clients and the server by extending the client/server framework. Events are published to the clients on a real-time basis through the use of  advanced client caching. This enables faster access to data by facilitating automatic delivery of new and updated information to the user. Many round trip server communications are eliminated because data is already available in the local computer's cache.

StarTeamMPX 2006 consists of several components:

• Event Transmitter
• File Transmitter
• Message Broker
• Multicast Service
• Root and Remote Cache Agents

New in StarTeam 2006, StarTeam Enterprise licenses support the following StarTeamMPX components:

• Message Broker
• Multicast Service
• Event Transmitter

Same as in past releases, StarTeam Enterprise Advantage licenses support all of the StarTeamMPX components:

• Message Broker
• Multicast Service
• Event Transmitter
• File Transmitter
• Cache Agent

System Requirements/Prerequisites

StarTeamMPX transmitters have the same system requirements as the StarTeam Server because they are part of that system. For details, see the StarTeam Server for Windows System Requirements/Prerequisites in this file.

The Message Broker is required. The Message Broker is a publish/subscribe messaging engine that broadcasts messages to subscriber components on a topic basis. It is a stand-alone process that can run on a separate computer to offload network processing overhead in high-volume environments.

The Multicast Service is an optional process that gives the Message Broker additional broadcast capabilities. However, only the Remote Cache Agents can use Multicast Service at this time. The Multicast Service delivers the same information as the Message Broker, but it uses IP multicast messaging instead of TCP/IP unicast communication.

You can also set up Cache Agents in tiers at a variety of locations so that file contents, transmitted by the file transmitter, can be network near any StarTeam user.

Cache Agents work with the StarTeam Cross-Platform client to check out files faster. They also work with the Bulk Check Out (BCO) utility, making it even faster than when it is used alone. Using BCO, even without Cache Agent, can speed up builds and is often substituted for the stcmd co command. Files checked out with Cache Agent can now use keyword expansion.

Message Brokers and Multicast Service

Cache Agent

These requirements should be sufficient for teams that have 50 to 100 members.

On a Windows system, a smaller computer can be used for smaller teams. For example, fewer than 50 developers on a Windows system can get by with 128 MB memory and a slower CPU. A faster CPU (maybe even dual CPUs) should be used for larger teams (more than 200 users).

On a Solaris system, a smaller computer can be used for smaller teams. For example, fewer than 50 developers on a Solaris system can get by with 256 MB memory and a slower CPU. A faster CPU (maybe even quad CPUs) should be used for larger teams (more than 200 users).

Top

Installation Instructions

Prior to installing, please read the StarTeamMPX Administrator's Guide (adminMPX.pdf) and the StarTeam Installation Guide (Install_en.pdf). Proper planning is required in order to achieve best results from StarTeamMPX. StarTeam documentation can be found on the product CD. If the product CD is not available documentation is found on the Borland web site at this URL http://info.borland.com/techpubs/starteam/.

Top

Known Issues

• Most network routers and switches are not multicast enabled by default. In order to use the multicast protocol it is necessary for the network administrator to verify that the network hardware is properly configured to allow the use of multicast protocol.
• Uninstalling from Windows Systems:
  StarTeam Server, StarTeam Cross-Platform client, and StarTeamMPX use InstallAnywhere for installation. If you encounter one of the following error messages when uninstalling this product from a Windows system (such as 2003 or XP Pro):

  "Can't launch executable. Could not find a suitable Java Virtual Machine on your system."

  or

  "Windows error 3 occurred while loading the Java VM."

  you may need to install JRE 1.5.0_09 or earlier from http://java.sun.com/javase/downloads/index.jsp. A copy of it is also on the StarTeam CD in the Utility folder.

• With StarTeam security, you can control detailed access rights for a file: the ability to see the file, see history, check-out, check-in, etc. In StarTeam, you can give someone the "see item and its properties" right but deny the "check-out" right. However, with the Cache Agent, granting someone the "see item and its properties" right implicitly grants them a "Cache Agent check-out" right. This is because the client can get a file's MD5, which is all it is needed to request a check-out. For environments in which this difference in security "interpretation" matters, you should not deploy Cache Agent or deny the "see item and its properties" right for users who should not check-out the corresponding files.
• If Cache Agent is installed as an auto start service and uses a Message Broker on the same machine, Cache Agent may start more quickly than the Message Broker. In this case, the Cache Agent start fails. The fix is simply to make the Cache Agent service depend on the Message Broker service.
• If you receive either of the following errors when installing StarTeamMPX Cache Agent:
  • Error 1723. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor.
  • WARNING! Failed to install Visual C++ Runtime Libraries. Please make sure to run vcredist_x86.exe before running StarTeamMPX Cache Agent.
  This happens when you have an old version (2.0) of Windows Installer. Windows Installer 3.0 or later is recommended.
  For more information, see http://www.microsoft.com/downloads/details.aspx?FamilyId=32BC1BEE-A3F9-4C13-9C99-220B62A191EE&displaylang=en.
  

Top

StarTeam Workflow Extensions

Available with Enterprise Advantage licenses. StarTeam Extensions enable you to create custom workflows for StarTeam components, such as change requests and tasks.

StarTeam Workflow Extensions consist of the following:

• StarTeam Extensions
• StarTeam Workflow Designer
• StarTeam Notification Agent

System Requirements/Prerequisites

StarTeam Extensions and StarTeam Workflow Designer have the same system requirements as StarTeam Server. It is good practice to install StarTeam Server 2006 prior to installing StarTeam Notification Agent.

The following are prerequisites for installing StarTeam Workflow Extensions:

• You must install StarTeam Server prior to installing StarTeam Workflow Extensions.
• You should install StarTeam Notification Agent on the same machine as StarTeam Server.
• Files from StarTeam Extensions need to be installed and checked in to the 2006 server configurations.
• Adobe Acrobat Reader 4.0 or higher is required for viewing the StarTeam Workflow Extensions User's Guide (extensions.pdf).

Top

Installation Instructions

Please see the PDF file, StarTeam Installation Guide (Install_en.pdf). StarTeam documentation can be found on the product CD. If the product CD is not available documentation is found on the Borland web site at this URL http://info.borland.com/techpubs/starteam/.

Top

Known Issues

• Running Notification Agent as a Service: If you run Notification Agent as a service, shutting down the service sometimes adds a harmless error message (javax.xml.parsers.FactoryConfigurationError) to the Notification Agent's log file.
• Seeing PATH Warning during Installation: As you install a product, you may also install the StarTeam SDK runtime. If you see this error, you must manually edit the PATH system variable to include the path statements necessary for the StarTeam SDK runtime. By default the paths are "C:\Program Files\Borland\StarTeam SDK 2006\bin" and "C:\Program Files\Borland\StarTeam SDK 2006\Lib".

Top

StarTeam Layout Designer

StarTeam Layout Designer is available with the StarTeam Cross-Platform and Web Edition clients.

 

Contents
System Requirements/Prerequisites	Limitations
Installation Instructions	Getting Help
Known Issues

System Requirements/Prerequisites

StarTeam Layout Designer can be installed on Microsoft Windows systems that support Sun Microsystems Java Virtual Machine 1.5.0_09. The system requirements are listed below:

Top

Installation Instructions

Please see the PDF file, StarTeam Installation Guide (Install_en.pdf). StarTeam documentation can be found on the product CD. If the product CD is not available documentation is found on the Borland web site at this URL http://info.borland.com/techpubs/starteam/.

Top

Known Issues

• Uninstalling from Windows Systems:
  StarTeam Layout Designer uses InstallAnywhere for installation. If you encounter one of the following error messages when uninstalling this product from a Windows system (such as 2003 or XP Pro):

  "Can't launch executable. Could not find a suitable Java Virtual Machine on your system."

  or

  "Windows error 3 occurred while loading the Java VM."

  you may need to install JRE 1.5.0_09 or earlier from http://java.sun.com/javase/downloads/index.jsp. A copy of it is also on the StarTeam CD in the Utility folder.

Top

Limitations

The following are limitations in Layout Designer.

• The Item Reference control is not available in the Web Edition client.
• The Attach, Userlist, History, Link and Label controls must each be used on a separate tab.
• Two or more controls having identical properties cannot be used on the same tab.

Top

StarTeam Integrations

StarTeam integrations are not included on the StarTeam Installation CD, but are posted for download on the Borland web site as they become available.

Check for them at: http://www.borland.com/downloads/download_starteam.html.

Getting Help

Borland Technical Support

Top