Last updated: September 10, 2012
Welcome to Borland StarTeam 13.0! These release notes contain important information that might not appear in the documentation and cover the StarTeam Server, Cross-Platform Client, StarTeamMPX, Web Client, Web Server, and Command Lines.
The StarTeam Installation Guide for each release is available online at http://supportline.microfocus.com/productdoc.aspx
Note: These release notes represent the known issues at the time of this release. For late-breaking information that may become available after the release, check the Micro Focus Web site for the most recent version of the Release Notes at http://supportline.microfocus.com/productdoc.aspx.
|What's New in 13.0|
|StarTeam Server||StarTeam Cross-Platform Client|
|StarTeamMPX||StarTeam Web Client|
|StarTeam Web Server||Command Lines|
|StarTeam Documentation||Getting Help|
This section provides an overview of the new features found in StarTeam 13.0.
This section provides an overview of the new features found in the StarTeam Server 13.0.
Support has been added for StarTeam Agile 1.0.
StarTeam Server 13.0 is now available on Red Hat Enterprise Linux 5.5 (32-bit).
The new component types Sprint and Story have been added to support the new 1.0 StarTeam Agile Web application. Sprints and Stories can be created in StarTeam Agile and viewed in the Cross-Platform Client. See the StarTeam Agile 1.0 documentation for a complete list of supported features.
Two new session options have been added to the starteam-server-configs.xml file.
This section provides an overview of the new features found in StarTeam Command-lines 13.0.
CustomDifferenceTypes (CDT) has been added as a supported option of VCMUtility. Using Custom Difference Types provides an alternative mechanism to specifying either Match States or Session Option Properties such as Lock Source for Difference, Ignore Merge Points, and so on. Specifically, the values of the difference type actions and session properties from Custom Difference Types override anything equivalent specified through the vcmutility command-line utility. Besides supporting tracking all configuration options through the Server Administration Tool, this also has the added advantage of simplifying and minimizing the vcmutility parameter set. See the Command-line Tools Help documentation for VCMUtility example commands.
This section provides an overview of the new features found in the StarTeam Cross-Platform Client 13.0.
You now have a quick and easy way to launch StarTeam Agile from within the Cross-Platform Client. Your server administrator must first specify the StarTeamAgileWebAddress option information in the starteam-server-confs.xml file. Once defined you can then choose Project > Open StarTeam Agile from the main menu to launch StarTeam Agile in your default browser.
A new Show Advanced Menus option allows you to control whether standard or advanced menu items display in the Main Menu for the component selected. Choose Tools > Show Advanced Menus from the Main Menu to turn the feature on or off. This feature is turned on by default and a check box displays when the option is turned on. When enabled, you will see advanced menu items displayed in the menu of the component selected. The component Main Menu options include: View, Folder Tree, File, Folder, Change Request, Requirement, Task, and Topic.
The new component types Sprint and Story have been added to support StarTeam Agile. Sprints and Stories can be created in StarTeam Agile and viewed in the Cross-Platform Client. Personal options tabs have been added where you can define system tray notifications to indicate how often the application should search for new sprints and stories and define URL options for displaying templates.
The following status values are now available in the CPC. You can only view these statuses in the File Items pane and they are not value options in a query if you choose Status as a Field condition. However, when you generate a report these statuses do display on the report.
|Known Issues and Notes about StarTeam Server|
|Server System Requirements/Prerequisites|
Microsoft Windows Server 2003 R2 SP2 (32-bit)
Microsoft Windows Server 2008 (32- and 64-bit)
Microsoft Windows Server 2008 R2 (64-bit)
Red Hat Enterprise Linux 5.5 Server (32-bit)
|Databases and ODBC versions||
Microsoft SQL Server 2005 Express SP3 (Windows Server only)
Microsoft SQL Server 2008 Express (Windows Server only)
Microsoft SQL Server 2008 Express R2 (Windows Server only)
Microsoft SQL Server 2005 SP3 (Windows Server only)
Microsoft SQL Server 2008 (Windows Server only)
Microsoft SQL Server 2008 R2 (Windows Server only)
Oracle Client 10g R2 version 10.2.0.4 (32-bit)
Oracle Client 11g version 18.104.22.168 (32-bit)
Oracle Client 11g R2
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
Important: Never modify database contents or vault files other than through a Client or Server Administration tool. Direct database manipulation is unsupported.
Microsoft Internet Explorer 8 or later
Firefox 4 or later
Adobe Acrobat Reader for viewing the StarTeam 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 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://supportline.microfocus.com before restarting the 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.
Note: The StarTeam 13.0 Cross-Platform Client can only access the following StarTeam Servers: 13.0, 12.5, 12.0, 2009 R2, and 2009. All Servers prior to 2009 will not support the 13.0 Client.
Important: If you are upgrading from a
previous version of StarTeam Server, you MUST review the upgrade
instructions in the StarTeam 13.0 Installation
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.
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 directly—during 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.
sse-install-error60206406827924122...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:
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.
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.
Right click on My Computer, and select Properties.
In the System Dialog, click Advanced System Settings (Windows 2008 only)
Click the Advanced tab, and click Settings to adjust performance settings. The Performance Options dialog box opens.
Click the Data Execution Prevention tab.
Select the option to add programs to the DEP list.
Navigate to the installer in the Add dialog box.
Click OK to close the dialog box when finished.
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.
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 1024.
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.
Caution: 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: Windows XP is not an officially supported platform for the StarTeam Server.
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.
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.
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.
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:
Start the Control Panel and select Windows Firewall.
Select Change Settings in the Windows Firewall dialog box.
Select the Exceptions tab.
Select Add program…
In the Add a Program dialog box, select Browse…
\Borland\StarTeam Server 13.0\ and select the StarTeam Server Application.
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 5101. 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.
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.
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 must start before the StarTeam Server service. Usually it does. If StarTeam Server fails to enable MPX and the Message Brokers on the same computer, you may want to make the StarTeam Server service dependent on the Message Broker 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 32-bit or 64-bit:
1. Click Start > Run from the Start menu.
2. Type Regedit32 or Regedit64, depending on your operating system.
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 internal service name into the Data window. (Example: StarTeam Message Broker 6.8).
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.
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.
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.
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 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.
|Known Issues and Notes about Cross-Platform Client||Cross-Platform Client Limitations|
|System Requirements/Prerequisites for the Cross-Platform Client|
The StarTeam Cross-Platform Client is implemented in Java and can be installed on Microsoft Windows systems and any system that supports the Java Runtime Environment (JRE) 1.6.0_29 . However, only the following Java-enabled platforms have been tested for compatibility with this product:
(32-bit and 64-bit)
Windows XP Professional SP3
Windows Vista SP1
Solaris Sparc 10
Red Hat Enterprise Linux (WS) 5.1
Adobe Acrobat Reader for viewing
the StarTeam Installation Guide (
|Web browser (for online help)||
Microsoft Internet Explorer 8 or later (Windows only)
Firefox 4 or later
The following are known issues found in the Cross-Platform Client (CPC).
Micro Focus recommends that you shut down all other applications when installing StarTeam components because other applications can cause the installer to hang. Shutting down all applications resolves such issues during installation.
On a Windows 7 platform, the Help is only available from the pdf versions. Access the pdf help from the Start menu or from the pdf subfolder in the client installation folder. For example, C:\Program Files\Borland\StarTeam Cross-Platform Client <version>\PDF.
On Windows XP SP2 and later, opening Help (Help > Help Topics) requires you to change your IE security setting to view the Help. As a workaround, follow the steps below:
Open Internet Explorer.
Select Tools > Internet Options.
Select the Advanced tab.
Scroll down to the Security options.
Select the option to Allow active content to run in files on My Computer.
When running the CPC with 'User Account Control' turned on, you may experience some security warnings regarding local files that are not accessible. Launching the CPC for the first time, and initializing the log with help launched are two examples where you will experience the security issue. Note: If a security warnings does appear, it will not prevent you from working normally in StarTeam.
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 and Windows Server 2008, in the StarTeam Toolbar tool, the Add Tool wizard will not add a shortcut. As a workaround, try one of the following options:
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.
On Windows Server 2008 64-bit, Toolbar shortcuts to 64-bit applications may not work. This occurs because Windows sometimes interprets the "Target" path using the 32-bit Program Files path (C:\Program Files (x86)\...) instead of the 64-bit Program Files path (C:\Program Files\...). To correct this, try the following steps:
Right-click on the tool in the Toolbar and select Modify Tool.
In the corresponding dialog box, remove the x86 part from the "Target" path and click OK.
Then exit the Toolbar and start it again.
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,
C:\Program Files\Borland\StarTeam SDK
Files\Borland\StarTeam SDK 13.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.
On non-Windows systems, jsafe.jar automatically installs with the Cross-Platform and Universal Edition (stcmd) Clients and is used for encryption. The jsafe.jar file 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.
Prior to installing, please read the StarTeamMPX
Administrator's Guide (
ST_MPX_Help.pdf) and the StarTeam Installation Guide (
ST_Install_en.pdf) on the Product Documentation page of
the Micro Focus web site at http://supportline.microfocus.com/productdoc.aspx. Proper
planning is required in order to achieve best results from StarTeamMPX.
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. For details, see the StarTeam Server for Windows Server System Requirements 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.
Note: For Cache Agent, these requirements should be sufficient for teams that have 50 to 100 members.
Microsoft Windows Server 2003 R2 SP2 (32-bit)
Microsoft Windows Server 2008 (32- and 64-bit)
Microsoft Windows Server 2008 R2 (64-bit)
Disk appropriate for size of cache; fast disk preferable but not mandatory
100 Megabit NIC or better
1 CPU P4 1Ghz or better
256 MB memory or better.
Note: 13.0 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.
SVGA, high color mode, 1024x768 or greater
Recommended resolution: 1280x1024 or more
Adobe Acrobat Reader for viewing
the StarTeamMPX Administrator's Guide
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.
Note: 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.
Checkout data will not be included in the
.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.
|Web browser||Microsoft Internet Explorer 8 or later (Windows
Firefox 4 or later
StarTeam Web Client has the following limitations and known issues:
Custom Components are not visible in the 13.0 Web Client.
Access Rights changes on the StarTeam Server that affect a user's ability to view and browse Items in the Items Table of the Web Client require a restart of the Web Server to pickup the changes. However, Access Rights changes on the StarTeam Server that affect a user's ability to modify or view the details of an Item will be picked up automatically by the Web Server.
On the first attempt to view Item Properties for a specific type of Item, if multiple Items are selected then the Web Client will display a warning that the editor file could not be found. After closing this warning, the editors display correctly and further attempts to open editors of this type will not display the warning. This issue is not present if only a single Item is selected for editing the first time.
|Platforms||Microsoft Windows Server 2008 R2 SP1 (64-bit)|
When administering the Web Server for multiple combined StarTeam repositories that add up to more than 1000 projects, you must use Firefox 10.0.2 or greater. All other browsers fail or lock-up when trying to load the Web Server Administration user interface.
The first person to log into a project that contains over 100 views will experience a load delay that could last several minutes depending on the quantity of views. This is a one-time cost for the project. No other user will experience the delay unless the Web server is restarted.
On some Windows 2008 Server operating systems, the Web Server installation will fail to copy the required libraries from the StarTeam install location to the Web Server install location. If this occurs, the files must be manually copied from the SDK to the Web Server. Copy the following files to YOUR_PATH\StarTeam 13.0 Web Server\apache-tomcat-5.5.33\shared\lib:
YOUR_PATH\StarTeam SDK 13.0\lib\ss.jar
YOUR_PATH\StarTeam SDK 13.0\lib\starteam120.jar
YOUR_PATH\StarTeam SDK 13.0\lib\starteam120-resources.jar
YOUR_PATH\StarTeam SDK 13.0\lib\StarTeam.Encryption.dll
YOUR_PATH\StarTeam SDK 13.0\lib\StarTeam.Environment.dll
YOUR_PATH\StarTeam SDK 13.0\lib\StarTeam.FileAccess.dll
YOUR_PATH\StarTeam SDK 13.0\lib\StarTeam.Profile.dll
The Web Server, installed as a service, can fail to stop. This can happen when the Web Server is configured to support over 1000 projects. The process will exit, but Windows will show a failed error message.
Default memory settings may be insufficient for very large data-sets, such as more than 1000 projects. There are two files that may need to be modified before the Web Server can be started, depending on the action you perform: running as a service or running from the Start menu.
Edit either the file: YOUR_PATH\StarTeam 13.0 Web Server\StarTeamService32.bat or YOUR_PATH\StarTeam 13.0 Web Server\StarTeamService64.bat depending on your operating system. Change the value of JVM_MAX_MEMORY to an MB value of your choice. For 32-bit operating systems, a maximum of approximately 1.8 GB is generally the limit. The JAVA_HOME and PRODUCT_JVM variables should be validated for accuracy; they are set according to typical path locations.
Edit the file: YOUR_PATH\StarTeam 13.0 Web Server\ apache-tomcat-5.5.33\bin\setenv.bat. Change the value of -Xmx4096M to an MB value of your choice. For 32-bit operating systems, a maximum of approximately 1.8 GB is generally the limit. The JRE_HOME variable should be validated for accuracy; it is set according to typical path locations.
In the StarTeam Install Guide documentation for the Web Server installation, the section "Setting up the Web Server as a Windows Service" states the incorrect location of the StarTeamService32.bat and StarTeamService64.bat files. The correct location of the files is: C:\Program Files\Borland\StarTeam 13.0 Web Server.
Access Rights changes on the StarTeam Server that affect a user's ability to view and browse Items in the Items Table of the Web Client require a restart of the Web Server to pick up the changes. However, Access Rights changes on the StarTeam Server that affect a user's ability to modify or view the details of an Item will be picked up automatically by the Web Server.
Properties whose values are Deleted Users will display as “Deleted User” in the Web Client.
|Known Issues with the Command Lines|
When specifying a quoted argument that contains a space, the beginning quote must be preceeded by a space. The following are examples of both incorrect and correct syntax for arguments with spaces:
Incorrect: stcmd set project=”StarFlow Extensions”
Correct: stcmd set project = “StarFlow Extensions”
Incorrect: stcmd select name from File where query=”Flagged Items”
Correct: stcmd select name from File where query = “Flagged Items”
When you open the first instance of a StarTeam
application, such as the Cross-Platform Client, and click on the Help Topics menu,
the Eclipse Info Center opens and displays the correct help contents for
that application. However, when you close the application, and/or open
another StarTeam Application, such as the Server Administrator Tool, when
you click on the Help menu, the Eclipse Info Center displays the help from
the previous application, in this case, the Cross-Platform Client.
The workaround for this is to go into the installation directory of the first application in which you clicked Help (Cross-Platform Client in this example), and in the
\borland-help subfolder, double-click
shutdown.bat. This releases the previous
applications Help contents from memory so the correct help will display when
you open it in the second application.
To obtain help for StarTeam, see Micro Focus SupportLine.