Borland® StarTeam® 2008 Release 2 Release Notes

Last updated: August 18, 2008

Welcome to Borland® StarTeam 2008 Release 2! This file contains important information that might not appear in the documentation and covers the StarTeam Server for Windows, Cross-Platform Client, 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://techpubs.borland.com/starteam/ .

StarTeam Server for Windows

Important Announcement

• The next version of the StarTeam SDK will not work with Server versions older than StarTeam Server 2005 R2. Correspondingly, the next version of the Server will not work with SDK versions older than StarTeam SDK 2005 R2.

• The Com APIs will not be supported begining with the next release of StarTeam.

System Requirements/Prerequisites

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

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

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

• Because StarTeam Server’s database revision number has been incremented, all existing 10.4 configurations, such as previous field test server installations, must be upgraded before they can start.
• 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. Navigate to the installer in the Add dialog box. 6. 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 rebooting is required.
• When installing or uninstalling on a non-Windows platform, you must specify which installed Java VM to use as a parameter when running the installer. This is because Java VMs for non-Windows operating systems are not bundled with the installers. Add the LAX_VM parameter to the install command and specify the path to your VM. For example:
  ./server.bin LAX_VM/usr/java/latest/jre/bin/java
  
  Note: This also applies to StarTeam CPC, EventTransmitter, StarTeamMPX and Cache Agent (for example, ./StarTeamCP.bin, ./ca.bin, ./mpxserver.bin, and ./mpxservices.bin)
• 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 10.4\bin" and "C:\Program Files\Borland\StarTeam SDK 10.4\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.
• If you wan to install the StarTeam Server on Windows XP, you must install the latest Windows XP Service Packs.
  Note: Windows XP is not an officially supported platform for the StarTeam server.
• 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.6.0_02 or earlier from http://java.sun.com/products/archive/j2se/6u2/index.html. A copy of it is also on the StarTeam DVD in the Utility folder.

• 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. To find the setup.ini file on your machine, search 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

Database Issues

Microsoft SQL Server/SSE

• 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

Server 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.

Purge Issues

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 2008 R2\DBScripts\Oracle_Scripts or C:\Program Files\Borland\StarTeam Server 2008 R2\DBScripts\Sqlserver_Scripts folders.

Evaluations

Borland allows you to extend the evaluation period for StarTeam Server by contacting http://www.borland.com/us/company/how-to-buy.html and obtaining an evaluation extender key.

Server Configuration File Option

The option ItemCacheMemoryLoadMaxPct is obsolete and does not have any effect in StarTeam 2008 and 2008 R2. A new server configuration file option ItemCacheMemoryLimit defines the maximum amount of memory that can be used for caching item data, in MB. The default value is -1, which means no limit is set, and the server will use up to the maximum amount of memory available to the server process for caching the data. For example, adding <option name="ItemCacheMemoryLimit" value="100"/> to the configuration file will set the cache limit to 100 MB.

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.

You may receive an error message when entering data in APEs.

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

For more details, see http://technet.microsoft.com/en-us/library/cc758478.aspx.

Opening Ports on Windows XP

If you are using a firewall, you have to open the port number on Windows XP SP2. This is 49201 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 Cross-Platform 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 the following technique.

Warning: Create a backup of the registry before making any registry changes. If you have disastrous results, the only way to recover is to restore from a registry backup or to reinstall the entire operating system.

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).

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.
  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. Click on OK to terminate the program.
  To avoid this situation, be sure to stop the server application before shutting down Windows, or run the server as a service. This issue was present in prior releases of StarTeam Server on Windows XP, and Windows 2003 Server Release 2.
• Enhanced Process Links
  The use of enhanced process links can now be turned on and off for all projects in the server configuration from the Server Administration tool.
  The use of enhanced process links for a specific project can be turned on and off from that project's Project Properties dialog box using the "Enable enhanced process links" check box on the Process Rules tab.
  Previously, using the "Enable enhanced process links by default for all projects on this server" check box in the Project Properties dialog box controlled enhanced process links for all projects. That check box has been removed from StarTeam Cross-Platform Client 2008 Release 2.
  We recommend checking both Process check boxes on the General page of the Server Configuration dialog box, and leaving them checked, or unchecking them both and leaving them unchecked. These check boxes are named "Enable enhanced process links by default for all projects" and "Enable enhanced process links by default for new projects". Then, to control specific projects, if those projects need different settings, use the "Enable enhanced process links" check box on the Process Rules page of the Project Properties dialog box.
  Be aware that by turning off the "Enable enhanced process links" check box for a project, you automatically turn off the "Enable enhanced process links by default for all projects" in the Server Administration tool.

 

Top

Limitations

The following are limitations in StarTeam Server for Windows.

• You cannot upgrade to this release of StarTeam Server until you have converted all Native-I archives to Native-II archive format. For more information, refer to the StarTeam 2008 R2 Installation Guide  (Install_en.pdf).
• PVCS and VSS archive files that were wrapped by a StarTeam client must be converted to the StarTeam Native-II format before using this release of StarTeam Server and its clients.
• Database support for Oracle 9g, SQL 2000, and MSDE were removed in the StarTeam 2008 Server release. You must upgrade your database to a currently supported version before upgrading StarTeam Server. For more information, refer to the StarTeam 2008 R2 Installation Guide  (Install_en.pdf).
• To help diagnose problems, StarTeam Server supports server statistics monitoring to track memory usage, currently executed commands, locking statistics, and so on. You should use this tool only with the assistance of Borland Technical Support.

Top

StarTeam Cross-Platform Client

Contents
System Requirements/Prerequisites	Limitations
Getting Help
Known Issues

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.6.0_02. However, only the following Java-enabled platforms have been tested for compatibility with this product by Borland:

System Area	Requirement
Platforms (32-bit)	Windows XP Professional SP3 Windows Vista SP1 Solaris Sparc 9, 10 Red Hat Enterprise Linux (WS) 5.1
Processor	600-MHz Pentium III-class processor or greater 600-MHz Sun SPARC/UltraSPARC
RAM	512 MB minimum 1 GB recommended
Hard disk space	200 MB to install the application Note: Sufficient disk space is required for your working files. The amount will vary depending on your use of the product.
Display	SVGA, high color mode, 1024x768 or greater Recommended resolution: 1280x1024 or more
Other	Adobe Acrobat Reader 4.0 or higher for viewing the StarTeam Installation Guide (Install_en.pdf)
Web browser (for online help)	Microsoft IE6 SP1+ Opera 8.5.2+ Netscape 7.2+ Firefox 0.9+
Virus Scanning Utilities	Every StarTeam client computer should be equipped with a virus protection utility that has up-to-date virus definition files. All StarTeam servers should also be equipped with up-to-date virus protection and the settings should be set to alert only the administrator. The StarTeam administrator should halt the StarTeam Server immediately upon virus detection, perform a full StarTeam backup, and then follow the instructions provided by the virus protection vendor for cleaning the virus from the infected file. If the infected file cannot be cleaned or if problems exist, contact http://support.borland.com before restarting the server. Some viruses can be immediately destructive to the repository and in rare cases data loss will be inevitable. Borland strongly recommends that regular backups be performed. A virus that might be a nuisance to a file system can be far more destructive when checked into the repository. For example, many virus protection utilities are set by default or can be set to delete infected files. If an archive file is deleted by the virus protection utility, data may be lost. Another example is that a virus may not be detected in the archive and may sit dormant waiting to infect the computers of all project users. Your network will rapidly spread the virus and a data loss could occur. Note: If any process or program such as anti-virus software alters files under StarTeam control the system could behave erratically. It is highly recommended that these processes not be allowed to modify system or data files under StarTeam control. Since StarTeam only acts as a conduit between users and the storage mechanism, it is highly improbable that any contamination/bad behavior will be propagated.

Top

Known Issues

The following are known issues found in the Cross-Platform client.

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.
  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 installing StarTeam applications on Microsoft Vista, a warning message displays from Vista indicating that a program has performed an action that requires Windows to temporarily change the color scheme to Windows Vista Basic. This happens whenever an application using an older version of the JRE tries to lock the primary display to apply its own display settings. The Desktop Window Manager is disabled which then disables the Aero desktop theme effects.
• On Windows Vista, in the StarTeam Toolbar tool, the 'Add Tool' wizard will not add a shortcut.
  Workaround - Try one of the following:
  • Right-click on the Toolbar and choose 'Open. In Windows Explorer, right-click and choose New > Shortcut. Browse to the application file to select it. In the StarTeam Toolbar, right-click on the menu bar and choose 'Refresh Tools'. The new shortcut should be displayed.
  • Open Windows Explorer and navigate to C:\Users\<username>\AppData\Local\Borland\StarTeam Toolbar\Tools. Right-click and choose New > Shortcut. Browse to the application file to select it. In the StarTeam Toolbar, right-click on the main menu bar and choose 'Refresh Tools'. The new shortcut should be displayed.  
• 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. 
• When installing or uninstalling on a non-Windows platform, you must specify which installed Java VM to use as a parameter when running the installer. This is because Java VMs for non-Windows operating systems are not bundled with the installers. Add the LAX_VM parameter to the install command and specify the path to your VM. For example:
  ./StarTeamCP.bin LAX_VM/usr/java/latest/jre/bin/java
  
  Note: This also applies to StarTeam Server, EventTransmitter, StarTeamMPX and Cache Agent (for example, ./server.bin, ./ca.bin, ./mpxserver.bin, and ./mpxservices.bin)
• 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.6.0_02 or earlier from http://java.sun.com/products/archive/j2se/6u2/index.html. 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 10.0\bin and C:\Program Files\Borland\StarTeam SDK 10.0\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.
• The 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 items and to 'grab' the items using two click actions. First select an item or multi-select several items, release the mouse button and then click and drag to move items.
• 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

• When a custom VCM merge type is specified in the View Compare/Merge wizard, the default Items Types for that merge type will only be applied in the wizard if the VCM Session was initiated as a full View scope."
• When a list of merge types have been specified for the Server node in the 'Available Merge Types' tree of the Customize VCM tool, the merge types can display within the list of Projects. The order of the merge types will be the same order in which they were added as will the visibility of the merge types within the StarTeam Client
• View Compare/Merge has no way of automatically deleting files it creates or checks out in the VCM working folder, or any VCM sessions you have saved there. You should periodically clean up your VCM working folder. For Windows XP, the working folder is C:\Documents and Settings\<user>\Applicsation Data\Borland\StarTeam\vcm, and for Windows Vista it is C:\Users\<user>\AppData\Roaming\Borland\StarTeam\vcm.
• When performing a View Compare/Merge, if you get a "Parent Folder Failed" condition, you will have to run two separate VCM sessions: The first session to resolve the folder-related issues, and a second session to merge the files.
• When committing changes and entering a label to be attached to the items, only the first 64 characters are saved in the label name. The text field accepts more than 64 characters, but it ignores any entries after the first 64 characters.
• Double-byte characters do not display properly in Summary or Differences reports. However, when reports are opened in a browser, such as Internet Explorer, the characters are displayed properly.
  
• When a shared item that has been pinned is manually shared once more, its configuration becomes floating by default.
  This is a known issue and can be identified visually because the Configuration tab of the Behavior dialog box becomes disabled (grayed). Select the item, then Advanced>Behavior to see this dialog box.
  The workaround for items that can branch is to branch the parent share. For example, you can do a force checkin of a file or change a field in a CR or folder. Then the child share can be pinned.
• Where items exist in two views with the same name but no common ancestry, VCM can only make the connection between these items while they remain in the same folder location.
  Most files are shared from one view to another and share the same Root Object ID. That is, they have a common ancestor. However, if a user checks in a file first in one view and then another, both receive different Root Object IDs and have no common ancestry. VCM uses Root Object IDs when matching items. When two files have no common ancestry, VCM can match them only by name and only while they have the same StarTeam paths.
  
  • Whenever the two files have identical contents and properties, VCM indicates that they are "Unchanged".
  • Whenever they have different contents and/or different properties, VCM always returns the difference type "Modified in source, modified in target" because VCM does not know which was modified. There is no common ancestor to indicate that only one of them has changed.
  • When files have no common ancestry, selecting the merge action "Mark Resolved" does nothing because files with no common ancestry cannot be given merge points. In this case "Mark Resolved" and "Ignore" are equivalent merge actions.
  A workaround for this problem is to delete one of the items from its view and then share or reverse share the item from the other view. This gives the two items a common ancestor. However, you cannot see the history, links, and labels of the deleted file unless you roll back the view's configuration to a time before the deletion.

Top

 

Documentation Issues

The following are known documentation issues.

• The View Compare/Merge Action Decision Table had a last-minute change to row 2000. The action Move and Overwrite was added as a possible action. This change was not made in the German, French, and Japanese documentation.
  
• The Com API docs cannot be viewed on Vista. To view the Com API docs, open them on an operating system other than Vista

 

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.
• When checking in a large file, the check in progress bar reporting may take some time to update as it completes the check-in process.
• 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 re-install the Cross-Platform Client as a workaround.

Top

StarTeamMPX

Contents
System Requirements/Prerequisites	Getting Help
Known Issues

StarTeamMPX provides a publish/subscribe messaging architecture for StarTeam Server. StarTeamMPX reduces server demand and improves client responsiveness by pushing update events to clients, reducing their need to poll for new information. 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 consists of several components:

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

StarTeam Enterprise licenses support the following StarTeamMPX components:

• Message Broker
• Multicast Service
• Event Transmitter

StarTeam Enterprise Advantage licenses support all of the StarTeamMPX components:

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

Important: Prior to installing, please read the StarTeamMPX Administrator's Guide (adminMPX.pdf) and the StarTeam 2008 R2 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 DVD or on the Borland web site at this URL http://techpubs.borland.com/starteam/.

System Requirements/Prerequisites

StarTeamMPX transmitters have the same system requirements as the StarTeam Server because they are part of that system:

• 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.

For details, see the StarTeam Server for Windows System Requirements/Prerequisites in this file.

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

Cache Agents work with the StarTeam client to check out files and fetch objects faster.

Message Brokers and Multicast Service

Note: Advanced platform storage, virtualization, and high availability features (Red Hat Global File System Cluster Suite) are not supported.

Note: The Message Broker and Multicast Service should be installed on the same type of platform.

System Area	Requirement
Platforms	Microsoft Windows 2003 Server and 2003 Server Release 2 (32-bit versions) Red Hat Enterprise Linux 5 Solaris platforms: Sun Ultra-250 (Sun Ultra-4 recommended)
Processor	Red Hat Enterprise Linux 5 Windows platforms: 400-MHz Pentium Pro-class processor or greater Solaris platforms: Sun Ultra-250 (Sun Ultra-4 recommended)
RAM	Windows platforms: 128 MB minimum
Hard disk space	5 MB to install the MPX Services
Display	SVGA, high color mode, 1024x768 or greater Recommended resolution: 1280x1024 or more
Other	Adobe Acrobat Reader 4.0 or higher for viewing the StarTeamMPX Administrator's Guide (adminMPX.pdf)

Cache Agent

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

System Area	Requirement
Platforms	Microsoft Windows 2003 Server or 2003 Server Release 2 (32-bit)
Processor/Hardware	Disk appropriate for size of cache; fast disk preferable but not mandatory 100 Megabit NIC or better 1 CPU P4 1Ghz or better
RAM	256 MB memory or better. Note: 2008 and 2008 R2 Cache Agents support memory caching, which is important if object caching is enabled. Therefore, additional memory should be available to support the desired amount of memory caching. The default memory cache size is 100MB.
Hard disk space	12 MB to install the application plus sufficient disk space for the desired size of each Cache Agent's cache.
Display	SVGA, high color mode, 1024x768 or greater Recommended resolution: 1280x1024 or more
Other	Adobe Acrobat Reader 4.0 or higher for viewing the StarTeamMPX Administrator's Guide (adminMPX.pdf)

 

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.
• When installing or uninstalling on a non-Windows platform, you must specify which installed Java VM to use as a parameter when running the installer. This is because Java VMs for non-Windows operating systems are not bundled with the installers. Add the LAX_VM parameter to the install command and specify the path to your VM. For example:
  ./mpxserver.bin LAX_VM/usr/java/latest/jre/bin/java
  
  Note: This applies to StarTeam CPC, StarTeam Server, EventTransmitter, StarTeamMPX and Cache Agent (for example, ./server.bin, ./ca.bin, ./mpxserver.bin, and ./mpxservices.bin)
• 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.6.0_02 or earlier from http://java.sun.com/products/archive/j2se/6u2/index.html. A copy of it is also on the StarTeam DVD 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 files, check in files, etc. In StarTeam, you can give someone the right to see an item and its properties, but deny them the right to check out the item. However, with the Cache Agent, granting someone the right to see an item and its properties implicitly grants them a the right to do a check-out. 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.
  • Checkout data will not be included in the generated .cotrc file if a Cache Agent performed the checkout. Data will only be included in the .cotrc file if the check-out operation was performed by the Server.
  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 Extensions Complete

Contents
System Requirements/Prerequisites	Known Issues
Getting Help

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 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 server configurations.
• Adobe Acrobat Reader 4.0 or higher is required for viewing the StarTeam Workflow Extensions User's Guide (extensions.pdf).

Top

Known Issues

• Dynamic Defaults: If a workflow is used in a different locale than the one in which it was created, dynamic defaults will be displayed in the language of the locale in which the workflow originated.
• 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 10.4\bin" and "C:\Program Files\Borland\StarTeam SDK 10.4\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.

 

Top

StarTeam Layout Designer

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

Contents
System Requirements/Prerequisites	Limitations
Known Issues	Getting Help

System Requirements/Prerequisites

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

System Area	Requirement
Platforms (32-bit)	Windows XP Professional SP2 Windows Vista
Processor	600-MHz Pentium III-class processor or greater
RAM	512 MB minimum 1 GB recommended
Hard disk space	200 MB to install the application Note: Sufficient disk space is required for your working files. The amount will vary depending on your use of the product.
Display	SVGA, high color mode, 1024x768 or greater Recommended resolution: 1280x1024 or more
Other	Adobe Acrobat Reader 4.0 or higher for viewing the StarTeam Installation Guide (Install_en.pdf)
Web browser (for online help)	Microsoft IE6 SP1+ Opera 8.5.2+ Netscape 7.2+ Firefox 0.9+

 

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.6.0_02 or earlier from http://java.sun.com/products/archive/j2se/6u2/index.html. A copy of it is also on the StarTeam DVD 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.
• all of the new Workflow Designer features introduced in StarTeam 2008 Release 2 will not be available in Web Edition Layout Forms. These features included User Context Limits, Dynamic Enumerated Field Limits and Default Text Field Values.

 

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_integrations.html.

Getting Help

To optain help for StarTeam, see Borland Technical Support.

 

Top

Installation Instructions

These installation instructions are a high-level overview of the installation process. For detailed installation instructions on installing the StarTeam products, see the Installation Guide install_en.pdf.

Important: If you are upgrading from a previous version of StarTeam Server, you MUST review the upgrade instructions in the StarTeam Installation Guide. 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.

To install StarTeam 2008 R2 for CPC, SDK, Notification Agent, or StarTeam Extensions:

1. Go to the Borland StarTeam trial downloads site at http://www.borland.com/downloads/download_starteam.html.
2. Scroll down the page and find the download link for the product you wish to install.
   For CPC, locate the product and the language version to install.
   For Notification Agent and StarTeam Extensions, locate the StarTeam Extensions Complete area.
   Note: The runtime SDK is automatically installed with each of the other products.
3. If downloading the StarTeam Server, click the StarTeam 2008 R2 Server link, fill out the form to register for the trial download, and then click Submit.
   The StarTeam Server 2008 R2 page is displayed.
4. Click the link for the download method (HTTP or FTP ). HTTP is faster.
5. Start the installation.
   
   1. Run the executable file:
      • For CPC Windows platforms, double-click the executable file (see table).
      • For CPC on Linux and Solaris platforms, you may need to unzip and run the StarTeamCP.bin file. After installation, run the StarTeamCP executable file in the StarTeamCP/bin directory, or use the shortcut with the same name located in the directory selected during installation.
        Note: You must specifiy which installed Java VM to use as a parameter when running the installer. This is because Java VMs for non-Windows operating systems are not bundled with the installers. Add the LAX_VM parameter to the install command and specify the path to your VM. For example:
        ./StarTeamCP.bin LAX_VM/usr/java/latest/jre/bin/java
      • For CPC Universal Edition, run the setup script in the installation's ./bin folder in order to create more executable scripts in that directory. To start CPC, run the starteam script.
      • For StarTeam Extensions and the Notification Agent, double-click the executable file and then choose a product from the menu of WorkFlow Extensions products.
        

   Installation Filenames

   Product	Platform	Language	Filename
   CPC	Windows	English	CPClient-2008R2-WIN-EN.exe
   		Japanese	CPClient-2008R2-WIN-JA.exe
   		German	CPClient-2008R2-WIN-DE.exe
   		French	CPClient-2008R2-WIN-FR.exe
   	Solaris	English	CPClient-2008R2-SOLARIS-EN.tar.gz
   		Japanese	CPClient-2008R2-SOLARIS-JA.tar.gz
   		German	CPClient-2008R2-SOLARIS-DE.tar.gz
   		French	CPClient-2008R2-SOLARIS-FR.tar.gz
   	Linux	English	CPClient-2008R2-LINUX-EN.tar.gz
   		Japanese	CPClient-2008R2-LINUX-JA.tar.gz
   		German	CPClient-2008R2-LINUX-DE.tar.gz
   		French	CPClient-2008R2-LINUX-FR.tar.gz
   Universal Client	All	English	CPClient-Universal-2008R2-UNIX.tar.gz
   StarTeam Extensions	Windows	English	Extensions-2008R2-WIN.exe
   	Linux	English	Extensions-2008R2-LINUX.tar.gz
   	Unix	English	Extensions-2008R2-UNIX.tar.gz
   Notification Agent	Windows	English	NotificationAgent-2008-WIN.exe

   1. Follow the onscreen instructions.
      
6. Repeat these steps for each product you want to install.

Default Windows Installation Folders

The default location for StarTeam Client is C:\Program Files\Borland\StarTeam Cross-Platform Client 2008 R2

The default location for StarTeam Notification Agent is C:\Program Files\Borland\StarTeam Notification Agent

The default installation folder for StarTeam Extensions is C:\Program Files\Borland\StarFlow Extensions, but Borland recommends copying the runtime files to a different folder for each server configuration. You must check the files in the Client, Projects, and Utilities subfolders into the StarFlow Extensions project for each StarTeam server configuration.

 

Top

Copyright © 2008 Borland Software Corporation. All Borland brand and product names are trademarks or registered trademarks of Borland Software Corporation in the United States and other countries. All other marks are the property of their respective owners.