Transcript
StarTeam 14.0 StarTeam Release Notes Micro Focus 575 Anton Blvd., Suite 510 Costa Mesa, CA Copyright Micro Focus All rights reserved. Portions Copyright Borland Software Corporation (a Micro Focus company). MICRO FOCUS, the Micro Focus logo, and Micro Focus product names are trademarks or registered trademarks of Micro Focus IP Development Limited or its subsidiaries or affiliated companies in the United States, United Kingdom, and other countries. BORLAND, the Borland logo, and Borland product names are trademarks or registered trademarks of Borland Software Corporation or its subsidiaries or affiliated companies in the United States, United Kingdom, and other countries. All other marks are the property of their respective owners ii Contents StarTeam Release Notes Version What's New StarTeam Server...6 StarTeam Server System Requirements... 6 Operating Systems...6 Databases... 6 Web Browsers... 7 Third Party Software...7 StarTeam Server and Microsoft SQL Server Express on the Same Computer... 7 StarTeam Server and Database on Different Computers... 8 Database Server System Requirements... 8 Large Memory Support...8 Unicode Character Sets... 9 StarTeam Server Known Issues... 9 StarTeam Cross-Platform Client StarTeam Cross-Platform Client System Requirements...13 StarTeam Cross-Platform Client Known Issues...13 StarTeamMPX StarTeamMPX System Requirements StarTeamMPX Known Issues StarTeam Web Client StarTeam Web Client System Requirements StarTeam Web Client Known Issues StarTeam Web Server StarTeam Web Server System Requirements StarTeam Web Server Known Issues Command Line Known Issues Documentation Known Issues Updates and SupportLine...22 Contacting Micro Focus Information Needed by Micro Focus SupportLine...22 Additional Information Needed by Micro Focus SupportLine Creating Debug Files Licensing Information Contents 3 StarTeam Release Notes Version 14.0 These release notes contain information that might not appear in the Help. Read them in their entirety before you install the product. Note: This document contains a number of links to external web sites. Micro Focus cannot be responsible for the contents of the website or for the contents of any site to which it might link. Web sites by their nature can change very rapidly and although we try to keep our links up-to-date, we cannot guarantee that they will always work as expected. 4 StarTeam Release Notes Version 14.0 What's New This section contain information about new product features Describes the new features for release 14.0: Support for the new StarTeam Agile 2.0 features. Support for Borland Connect 1.0. The StarDraw sample project can now be added to any configuration from the Server Administration tool. Significant performance optimizations have been added for migrations between Microsoft SQL Server and Oracle. What's New 5 StarTeam Server This section details system requirements and know issues for the StarTeam Server. StarTeam Server System Requirements We recommend installing the StarTeam Server on a dedicated application server, and installing the database on a separate server unless you are using a supported version of Microsoft SQL Server Express as your database. There should be a dedicated connection between the computers running the StarTeam Server and the database management system. For optimal performance, both machines should be on the same physical switch. The following shows the minimum and recommended hardware for the computer on which you deploy the Server application and database. Although specific processor speeds are listed, you should always use the fastest available CPU to maximum performance. Note: The StarTeam Cross-Platform Client only supports StarTeam Server versions greater than Important: If you are upgrading from a previous version of StarTeam Server, you MUST review the upgrade instructions in the StarTeam Installation Guide (ST_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. Operating Systems The following operating systems are supported for this release: Microsoft Windows Server 2008 (32- and 64-bit). Microsoft Windows Server 2008 R2 (64-bit). Microsoft Windows Server 2012 (64-bit). Note: You cannot install a 64-bit Microsoft Windows StarTeam component on a 32-bit Microsoft Windows system. The installer will return an error upon attempting to install the Java VM. Databases StarTeam Server supports both 32-bit and 64-bit databases. The following databases have been tested and are supported for the StarTeam Server: Microsoft SQL Server 2008 SP3. Microsoft SQL Server 2008 R2 SP2. Microsoft SQL Server 2008 Express. Microsoft SQL Server 2008 Express R2. Microsoft SQL Server 2012 SP1. Microsoft SQL Server 2012 Express. Oracle Database 10g R2 version (32-bit). Oracle Database 11g version (32-bit). Oracle Database 11g R2. 6 StarTeam Server Note: You can install Microsoft SSE as part of the StarTeam Server installation. You must purchase the other database products from the appropriate vendor. Refer to the StarTeam Installation Guide for more information about recommended system configurations for running StarTeam and SSE on the same computer and for running StarTeam Server and its associated database on separate computers. Important: Never modify database contents or vault files other than through a Client or Server Administration tool. Direct database manipulation is unsupported. Password By default, the installer uses the following password: sa: StarTeam123. Web Browsers Internet Explorer 8 or later. Firefox 4 or later. Third Party Software Please ensure these other software requirements are met JRE The StarTeam Server uses the Java Runtime Environment (JRE) 1.7.0_17 which is automatically installed at C:\Program Files\Borland\Java\Oracle1.7.0_17. Adobe Acrobat Required for viewing the documentation in PDF format. Virus Scanning Utilities Every StarTeam Server 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 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 before restarting the StarTeam Server. Some viruses can be immediately destructive to the repository and in rare cases data loss will be inevitable. Micro Focus 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. StarTeam Server and Microsoft SQL Server Express on the Same Computer When Microsoft SQL Server Express is used, the database typically resides on the same computer as the corresponding StarTeam Server application. The following hardware recommendations for a joint StarTeam Server 7 StarTeam Server/Microsoft SQL Server Express computer are based on the number of seats (registered users) although your situation might vary depending on the size of your StarTeam projects and the number of projects managed by the server configuration. The following lists suggested system configuration requirements if you are using Microsoft SQL Server Express and the StarTeam Server on the same computer. Less than 50 Seats 32-bit dual core machine with 4GB of RAM Seats 32-bit quad core machine with 4-8GB of RAM Note: Microsoft SQL Server Express is not recommended for configurations serving more than 100 registered users. StarTeam Server and Database on Different Computers The following hardware recommendations apply when the StarTeam Server application is executing on a different computer than the database server. They are based on the number of peak users (maximum concurrent users during peak periods) although your situation might vary depending on the size of your StarTeam projects and the number of projects managed by the server configuration. Number of Peak Users Less than bit, dual-core systems with 4GB of memory bit, quad-core systems with 4-8GB of memory. More than bit, quad-core systems with 8-16GB of memory. Database Server System Requirements The following recommendations apply to the database server when it is not on the same computer as the StarTeam Server. The number of peak users is the maximum number of concurrent users during peak usage periods. Number of Peak Users Less than 100 Computer with a dual core processor and 4GB of RAM Minimum: Computer with quad processors and 4 GB of RAM. Recommended: Minimum configuration plus RAID system. More than 200 Minimum: Any high-performance Enterprise Server with quad processors and 4-8 GB of RAM. Recommended: Minimum configuration plus RAID system. Large Memory Support On 32-bit Microsoft Windows systems, you can use 4GB RAM tuning to enable the StarTeam Server application to utilize 3 GBs of memory. To enable this feature, you must add the /3GB switch to the Boot.ini file. For information about setting this switch, see: aa aspx. On 32-bit Microsoft Windows, you should also be aware of the maximum page file size, which can affect memory allocation when multiple applications are run on the same computer. See: support.microsoft.com/kb/ StarTeam Server You should also be aware of Page Table Entry (PTE) limitations when the /3GB switch is used. See: Unicode Character Sets While StarTeam Server supports data in all languages that can be encoded in UTF-8, it uses only ASCII characters (0-127) as it expands keywords. Keyword expansion and EOL conversion should work for all ASCII-based encodings, which include UTF-8, Cp1252, and so on. For the various UTF-16 encodings, StarTeam Server currently performs EOL conversion, but does not expand keywords. The internal names of custom fields must be ASCII, but the display names can be in non-english character sets. StarTeam Server Known Issues ODBC/DSN Decommission Process and the workaround During the database upgrade process for existing pre-13.0 configurations, the ODBC DSN information in the configuration file is replaced with entries for direct database connectivity. During this time, we are able to detect the database server and instance name and update the configuration accordingly. Connecting to a database (SQL Server or Oracle) running on a non-default port is now supported directlyduring the creation of a new configuration, there is an option to select the port, if desired. However for SQL Server configurations upgraded to 12.0 from previous versions of StarTeam, the default port will always be assumed. This is because the workaround to connect to a SQL Server on a non-default port using ODBC does not return the port information when queried. If attempting to upgrade an existing configuration to 13.0, where the SQL Server ODBC DSN used by the existing configuration references a non-default port, it may be necessary to edit the starteam server configuration file to enter the correct port. Installation Issues If you select only the StarTeam Server option with the Custom setup during the first installation of StarTeam Server, and later run the installer again with Typical setup, then you could run into this sseinstall-error warning, followed by a Yes or No button: Warning! Failed to install Microsoft SQL Server 2005 Express Edition which is mandatory for the Sample. Do you still wish to continue without the Sample: Note: Click No. Then, uninstall Microsoft SQL Server Native Client from Control Panel/Add or Remove Programs and run the server installer again. If you install multiple SDKs on a 64-bit OS (one 32-bit and one 64-bit) the shortcuts for the first SDK will be overwritten with the shortcuts to the last SDK installed. This means that you can only uninstall the 'last' SDK using the shortcuts in the program group. On Linux, selecting the Embed Preedit String into client window option is preventing input into the Password text field in the Japanese language (like it was in previous releases), and also in the English language in this release. French and German are fine. We recommend you uncheck the Embed Preedit String into client window option in both English and Japanese languages. Data Execution Prevention (DEP): 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. StarTeam Server 9 2. In the System Dialog, click Advanced System Settings (Windows 2008 only) 3. Click the Advanced tab, and click Settings to adjust performance settings. The Performance Options dialog box opens. 4. Click the Data Execution Prevention tab. 5. Select the option to add programs to the DEP list. 6. Navigate to the installer in the Add dialog box. 7. Click OK to close the dialog box when finished. Canceling an Installation - If you cancel the installation of the StarTeam Server after you have already installed the StarTeam Runtime, and then install the StarTeam Server again, letting it finish, at the end of the installation you will not be prompted to reboot the computer, even though rebooting is required. Seeing PATH Warning during Installation - As you install the product on Windows, the StarTeam SDK runtime may also be installed. If your PATH length is too long and exceeds 1024 characters, an error indicates that you must manually edit the PATH system variable. This might be due to an InstallShield restriction on a string size longer than To fix this, you can uninstall any StarTeam SDKs that are no longer being used, then manually shorten the PATH text by removing the entries to the uninstalled SDKs. Then, you can either manually add the new PATH environment variables for the StarTeam SDK runtime C:\Program Files\Borland\StarTeam SDK 13.0\bin and C:\Program Files\Borland\StarTeam SDK 13.0\lib, or re-install the StarTeam product again and let it automatically modify the PATH variables to the SDK runtime locations. Note: Removing text from the Windows path may cause undesired application failure if done incorrectly. 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 want to install the StarTeam Server on Windows XP, you must install the latest Windows XP Service Packs. Note: Note: Windows XP is not an officially supported platform for the StarTeam Server. Server Issues Native-II Vault StarTeam Sample Server Configuration Opening Ports on Windows XP 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. 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. If you are using a firewall, you have to open the port number on Windows XP SP2. This is by default. If you don't open this port in the Windows firewall, you cannot connect to the Server. Windows Server 2008 also requires an Exception to the Windows Firewall Settings. However, it may be a better practice to grant all access to the StarTeam Server as follows: 1. Start the Control Panel and select Windows Firewall 2. Select Change Settings in the Windows Firewall dialog box. 10 StarTeam Server 3. Select the Exceptions tab. 4. Select Add program 5. In the Add a Program dialog box, select Browse 6. Browse to \Borland\StarTeam Server 1 3.0\ and select the StarTeam Server Application. 7. Click OK. Note: This will grant access to any port to the StarTeam Server. The above procedure could be followed to grant an Exception for MPX, Cache Agent and Web 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 If you are using this port you need to open it. 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. Click OK Security Blocking MDAC Running the Server as a Service 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. Note: Windows XP is not officially supported for StarTeam 13.0 Server. 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. 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 from the Windows Firewall. This is not a problem. Click Unblock. 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. 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 must start before the StarTeam Server service. Usually it does. If StarTeam Server f
