Deploying large StarTeam configurations

over 8 years ago

Deploying large StarTeam configurations


Large configurations are the ones that support 400 concurrent users or more during peak periods. For these configurations, you should place the StarTeam Server process on its own system. The database process should also execute on its own machine. Though not strictly necessary, the root MPX Message Broker and Cache Agent processes can also benefit by executing on yet another “MPX” machine. This strategy is very beneficial when concurrent users rise to 300, or more and moving the MPX processes to their own machine can remove network traffic and other resource contention from the StarTeam Server machine.

A typical deployment of multiple large configurations is shown in Figure 1.

The key points of this multiple, large configuration deployment are summarized below:

  • The StarTeam Server process for each configuration executes on its own machine. This is typically a high-end machine with four, eight core CPUs with 64 GB of RAM.


  • The Database process for each configuration executes on its own machine. This is typically a high-end machine with very similar specs to the StarTeam Server machine. It is highly recommended to have a very fast connection between the database server and the Application Server due to the heavy amount of data that is transmitted from the Database to the ST Server.


  • Borland strongly recommends having the database and the StarTeam Server on the same physical switch. For example, a TraceRt between StarTeam Server and Database Server should be one hop. Every additional hop would add lag time to the packets being streamed across the network.  This would be more noticeable whenever Server is running a lot of bulk database commands and a very large amount of data is streamed in a very short duration causing sluggishness in StarTeam. Every effort is made in the Server Architecture to minimize database round trips and get data in bulk and a slow network can potentially cause major performance issues.


  • The MPX root Message Broker and root Cache Agents can all execute on a single “MPX machine”. Each root Cache Agent requires access to the appropriate vault, but a high-speed dedicated connection is not necessary. File access over the network (e.g., using UNC paths) is sufficient. Note that if you utilize the workflow Notification Agent, you can put it on the MPX machine also.


  • A shared storage server such as a SAN server can be used for all StarTeam vaults and database partitions. Depending on the hardware, an interface (e.g., “host” card) may be needed for each StarTeam server machine in order to access the SAN.


Further configuration recommendations can be advised by contacting StarTeam Support.


How To-Best Practice
Comment List
Related Discussions