10.07.2015 Views

Borland StarTeam 2009 - Borland Technical Publications

Borland StarTeam 2009 - Borland Technical Publications

Borland StarTeam 2009 - Borland Technical Publications

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

3. Install the Root Cache Agent. You need to install it only once per machine, even when that machine hasmore than one server configuration. You run multiple instances to support multiple <strong>StarTeam</strong> Serverconfigurations. Each server configuration must have its own root cache agent instance.4. Install the Remote Cache Agent. This is the same installer as the Root Cache Agent. You typically installand run a single Message Broker on remote machines.The Remote Cache Agents can use the same Message Broker as the Root Cache Agent, but multipleMessage Brokers are suggested for distributed teams, especially over distances. In practice, Remote CacheAgents usually use remote Message Brokers.Before you start a Root Cache Agent:1. Start each server configuration that you will use with Cache Agent. Doing this causes the File Transmitterto generate or upgrade a CacheJournal.dat file for each configuration.2. (Optional) Modify the MaxJournalAge parameter’s value in the FileTransmitter.xml file to representthe maximum number of days for which records will be kept within the Journal file. The pre-configuredvalue is 180 days. Note that the Journal file is “trimmed” of expired records (those whose age exceedsthe MaxJournalAge value) only when the Server application is started for the associated configuration.Installing a Cache AgentWhether a Cache Agent operates as a Root Cache Agent or a Remote Cache Agent is determined solely byits configuration. The installation of the Cache Agent is similar in both cases except for consideration of thecomputer on which to install it:• The Root Cache Agent requires access to the vault for the server configuration that it services. Consequently,it can be installed on the same computer as the <strong>StarTeam</strong> Server. Alternatively, if it can be installed on aseparate computer to prevent the Root Cache Agent from competing for CPU or network I/O with thecorresponding server configuration. However, this requires it to access the vault files and theCacheJournal.dat file by way of a shared network drive, so use this option only when a high-speed networkis in place.• Remote Cache Agents should be installed in each geographic location that can benefit from improved filecheck-out performance. One approach is to install a Cache Agent in each network environment that localusers can access over a highspeed LAN. (For example: Install two Remote Cache Agents at headquarters,one each for engineering and QA, a third Remote Cache Agent at the Chicago office, and a fourth at theLondon office.) Another beneficial use of the Cache Agent is to install an instance on a computer dedicatedto a check-out intensive application such as a build utility. There is no limit on the number of Cache Agentsthat can be installed throughout an enterprise. However, keep in mind that each Cache Agent requiresaccess to a Message Broker. For more information about clouds, see “Understanding Clouds” in the<strong>StarTeam</strong>MPX Administrator’s Guide.To install a Root Cache Agent or Remote Cache Agent:1. On the computer where you wish to install the Cache Agent, log on as the administrator or as a user withadministrative privileges.2. Run the downloaded installer, or if using replacement DVDs, insert the <strong>StarTeam</strong> <strong>2009</strong> Installation Disk 1(32 bit) or 2 (64 bit) DVD into your DVD drive.The <strong>StarTeam</strong> Launcher window should appear automatically.If the installation menu does not appear automatically from inserting the DVD, display it by performing thefollowing steps:1. From the Windows Start menu, select Start ➤ Run2. At the command prompt, type:x:\setup.exeInstalling <strong>StarTeam</strong>MPX on Windows | 59

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!