Installation

How do I register my  StarTeam products?

I have installed StarTeam, but when I go to open project it looks like I need to select a server, but I cannot locate a server.

During the installation I noticed the install was checking for JavaVM and ODBC, and WinSockets. Can you tell me why?

Setting Up StarTeam VirtualTeam Server to use MS SQL 6.5, 7 or 2000.

Setting StarTeam VirtualTeam Server to use ODBC to connect to DBMS.

StarTeam Server Performance Tuning.

How do I move a StarTeam repository?

I accidentally deleted a server configuration file at on the machine running server. Is there an easy way to recreate this file?

How do I set up a Shadow Directory for StarTeam?

Where do I install the server?

How do I connect to the Server?

Why does StarTeam 3.0 and above require a server?

I can't find several of the IDE's that you say are part of StarTeam !

IBM's VisualAge for Java is not listed as an IDE integration in the client installation of StarTeam .

During installation I get an error message saying "Jet Database drivers in use by another application".

 

Usage Questions

How Do I . . .
How do I safely backup my repository and server configuration files?

How does e-mail work in StarTeam?

How do I set an alternate-working directory?

How do I add a user to more than one group in the User Manager?

How do I run a query or create a filter?

How do I create Build Reports?

Troubleshooting StarTeam 2.x Import process.

How can I import all file versions?

How do I use StarTeam to version control my System Architect encyclopedias?

Will StarTeam work on dial-up connections?

How does the StarTeam promotional model work?

How Do I "recursively" check out files and folders in "one step"?

How Do I migrate RCS archives to StarTeam 4 archives using the Command Line processing?

How Do I branch in PowerBuilder?

Frequently Asked Questions related to Visual SourceSafe (VSS) and StarTeam.

Process to migrate ClearCase archives to StarTeam archives using the Command Line processing.

Process to migrate CVS archives to StarTeam archives using the Command Line processing.

How to use the StarTeam Promotion Stages?

How to use StarTeam's View Labels?

WebConnect

How Do I . . .
How do I setup WebConnect?

How do I get the WebConnect images to show correctly?

More WebConnect questions

Error Messages

I'm getting one of the following system messages............

I'm getting the following system message: "User error: Unable to read/write to registry". How can I get around it?

Installation Section

  I have installed the StarTeam Professional, but when I go to open project it looks like I need to select a server, but I cannot locate a server.

The StarTeam client requires that you also have the StarTeam Virtual Team Server (STVTS) installed, configured and running.  If the STVTS is installed and running, the next step is to create a new server definition at the client.

For the Server description you may enter any expression that will be meaningful to you.

Your team leader or administrator typically provides the Server address to you. If you are working on a LAN, this is usually the system name as you see it in the Explorer or Network Neighborhood.  In a large LAN it can be very time consuming to use the Browse button to locate the target machine.  For Internet connections use the IP address or domain name of the STVTS installation.

The endpoint should match with the endpoint defined at the server for your selected protocol.  For testing or demonstration purposes you may use our demonstration server at  demo.starbase.com (12.13.2.3), TCP/IP (sockets) with endpoint 21.

Were you looking on the custom install integration list?  We don't directly integrate with the indicated but through common integration for the fact that StarTeam is compatible with Microsoft's SCC interface.  When installing the integration components MS DEV and VB, StarTeam will integrate with the following:

• HahtSite 3.1 & 4.0

• MS Visual J++ 6.0

• Rational Rose 98

• NetDynamics Studio 5.0

• Microsoft Developer Studio & Visual Studio

• Borland's DELPHI 3 & 4

• Symantec Visual Cafe New IDE integration with the leading Java development environment. StarTeam is the first solution to integrate using the Visual Cafe API.

• Powersoft PowerBuilder versions 5 & 6

• Oracle Developer/2000 v. 1.5 and 2.1

• Allaire ColdFusion Studio v. 3.1.1 & 4.0.1

• Premia CodeWright v. 5.3

To the top of this page

During the installation I noticed the install was checking for JavaVM and ODBC, and WinSockets.  Can you tell me why?

A number of our processes are dependent on third party software.  All StarTeam components, with the exception of the Windows Professional client, use the JavaVM.  This includes all COM users, command line, Web Connect and integrations.  All of these must use TCP/IP (sockets).

The StarTeam database requires the use of the 32bit ODBC component.

To the top of this page

Setting Up StarTeam VirtualTeam Server to use MS SQL 6.5, 7 or 2000.

If you chose to configure your StarTeam database as SQL, you will want to make sure that your setup meets these prerequisites.

• You need a copy of MS SQL 6.5 (with Service Pack 3) or SQL Server 7 or later.

• The SQL 6.5 database for StarBase should be set for 300 Mb.

• The SQL 7 or 2000 database for StarBase should be set to 10MB and be allowed to grow automatically.

• For best performance plan to install StarTeam Virtual Team Server (STVTS) and the MS SQL server on separate boxes. This is especially important if you will be supporting 50 or more users.

• You will need two user licenses for MS SQL 6.5, 7 or 2000 (One to support the administration of STVTS and the second to support the connection to the SQL database).

• StarTeam needs administrator controls over the database.

• Each repository you create will require a SQL database.

Use the following steps to help configure your database to SQL.

1. Create a database device named StarBaseSQL.

2. Create a database named StarBaseSQL.

3. Setup the database size to 300 MB (6.5) or 10 MB (7 or 2000).

Note: StarTeam VirtualTeam Server will create the data tables and catalog information for the database.

Setting up the ODBC connection:

1. Access the ODBC-32 icon in the Control panel.

2. Create a System DSN to access your StarBaseSQL database:

1. Click on the System DSN tab then click on the Add button.

2. Select SQL Server.

3. Enter StarbaseSQL in the Data Source Name box.

4. Enter the description for the System DSN.

5. Select the SQL Server where you created the StarBaseSQL database.

6. Leave the Network Address and Library box as (Default).

7. Click on the Option button.

8. In the Database name box enter StarBaseSQL and Click on the OK button.

9. Make certain the following items are checked:

• "Use ANSI quoted Identifiers"

• "Use ANSI nulls, padding, and warnings"

• Note: If your ODBC MS SQL driver does not support "Use ANSI quoted Identifiers" or "Use ANSI nulls, padding, and warning" please update the MS SQL ODBC drivers.

To the top of this page

Setting Up StarTeam VirtualTeam Server to use SQL.

:

1. Start the StarTeam VirtualTeam Server and select New and enter the name of the repository and directory path for the repository. Click on the Next button.

2. Select the MS SQL in the Database Type box.

3. Enter DSN name for the Database: StarbaseSQL.

4. Enter the SQL Administrator User Name.

5. Enter the SQL Administrator password and click on Next button.

6. Enter cipher phrase and click on Finish button.

StarTeam Server Performance Tuning.

Improving performance can be a difficult task due to the high number of variables affecting the server during runtime. Here is a list of pointers that you may try in your environment:

• First, make sure you have the latest version of StarTeam client/server. With each release of StarTeam, the product has become more efficient and honed for speed and stability. If you have StarTeam, make sure you have the latest Service Pack.  If you are up to date with your maintenance contract you are entitled for free upgrades.

• When running the server, try closing down all other programs and see if you notice a speed increase. Sometimes other programs can tax the system or the server itself and cause performance issues. If StarTeam's performance increases dramatically, you may want to consider a dedicated server for StarTeam.

• You might try increasing the maximum cache size. With the server running, go into configure, Vault tab. Change the maximum cache size from 100 MB to 200 MB (make sure your machine actually has 200 MB for the cache, as well).

• For the best performance, the file repository should be on the same machine as the server.

• Starting the server and some operations can be improved by modifying the tracing in the ODBC module. Go into control panel and double click on OBDC. Click on the tracing tab, then select "Don't Trace".

• If you are using a Microsoft SQL Server, Oracle or dB2 run the DMBS Server and the StarTeam Virtual TeamServer on a machine with dual processors (or use the next best solution - install StarTeam and the DBMS on two separate systems).

• Tuning StarTeam 4.2 Databases (build 4.2.685 or later):
  StarTeam 4.2 contains SQL tuning scripts that are designed to improve the performance of StarTeam databases that run under Oracle, Microsoft Access, or Microsoft SQL Server 7.0. These scripts drop and recreate most of the indexes on a StarTeam database and improve database throughput. You will find the complete instruction on how to run the scripts in the manual titled "Installation Guide".

• If you are using the internet for remote connections, use the Project=>Shortcut Properties, Data Transfer tab, check for Compress transferred data.

• Within Tools=>Workstation options, go to the Files tab and select "Optimize for slow connections". This will send the deltas only.

• If you are using an Access database, performance may be increased by using the repair and compact utilities in the ODBC manager or in Access. This will compress the database and should make the server a little more responsive.

• The minimum requirement for the StarTeam Server is a 400 MHz processor with 256 MB of RAM.

To the top of this page

How do I move a StarTeam repository? (Separate Document)

Moving a repository requires precision. Here are a few steps that you can follow to help you move your repository to a new location. Be aware of the following:

1. You need to know the Cipher key for the Repository.

2. You need to install StarTeam VirtualTeam Server on new Computer where the repository will be located.

3. Be sure which database you are using with the repository.

4. Be aware of any foreign archives that the repository is using.

5. Carefully test the new configuration before deleting the old.

Moving Repository using an Access Database:

1. Copy the repository directory to the new computer or hard driver.

2. Copy the configuration file and cipher file in the StarTeam Virtual Team Server Config Files directory to the new StarTeam Virtual Team Server Config Files directory.

   Ex:

   C:\Program Files\StarTeam VirtualTeam Server 4.0\Config Files\DEMO.SCG

   C:\Program Files\StarTeam VirtualTeam Server 4.0\Config Files\DEMO.CPH

3. Start the StarTeam Virtual Team Server.

4. Select the repository you wish to start.

5. Click on the Properties button.

6. To the right of the Cipher name box click on the Verify Button.

7. Enter the cipher key that was used to create the repository.

8. Click on the Database tab.

9. Highlight the entry in the DSN box.

10. Hold the Ctrl key and hit the C key on the keyboard. This will copy the name entry to the clipboard.

11. Click on the Ok button.

Updating the ODBC

1. From the Start button at the bottom lower left of the desktop, go to Setting and select the Control Panel.

2. From the Control panel select the select the ODBC icon

3. Select the System DSN tab

4. With the System DSN tab active, click on the Add button.

5. Scroll the list of Create New Database source and select MS Access driver.

6. Click on the Finish button.

7. In the ODBC Microsoft Access 97 Setup dialog box move your pointer to Data Source Name box and click. Hold the Ctrl key down and depress the V key on the keyboard, this should paste the DSN name from steps 9 and 10.

8. You can enter any useful information in the description box if you wish.

9. Click on the Select button in the Database box.

10. In the Select Database dialog box find the repository directory that you have moved.

11. Select the Database folder under the repository folder.

12. Select the Database file *.mdb

13. Click on the OK button.

14. In the ODBC Microsoft Access 97 Setup dialog box click on the OK button.

15. In the ODBC Data Source Administrator click on the OK button.

Begin the testing of your new configuration:

1. Move your pointer on the Red box in the System Tray, select server configuration Menu appears.

2. In the Select Server Configuration Dialog Box click on the Start Server

If you plan to move the repository to a different directory or hard driver letter other than the original creation setting, please use the following steps:

1. Do a right mouse click on the StarTeam VirtualTeam Server Icon in the system tray.

2. Select Configure on the menu.

3. Enter user logon and password

4. In the StarTeam VirtualTeam Server Configuration dialog box on the General Tab in the Attachments Box make sure that the path is pointing to the new locations.

5. In the StarTeam VirtualTeam Server Configuration dialog box on the Vault Tab make the sure that the following item are pointing to the correct directory:

Vault Path

Disk Cache Path

Archive Path

To the top of this page

I accidentally deleted a server configuration file at on the machine running server. Is there an easy way to recreate this file?

There is no easy solution. First, the configuration files are like a FAT table on the disk. Hence, you have to backup these files and keep in a safe place. These files are the keys to the database and are not easily recreated.

However, is a suggested workaround:

1. Suppose the orphaned repository is rooted at d:\repository. Rename the original root directory, e.g., to d:\repository.old.

2. Create a fresh repository, making sure that the same cipher phrase is used.

3. Run the server once on it so it gets initialized.

4. Shut down the server.

5. Delete the root directory and rename the original directory to its correct name, e.g., d:\repository.old to d:\repository

6. At this step we have recreated the configuration files and they point to the old database.

Now the tricky part:

• Start the server and view properties of the recreated configuration. From the first page copy the Database Guid field (for pasting into the database).

• Open the database file with Access and locate the table ServerSettings, and then ServerID field (column). Paste the guid value into that field and close the database.

7. Run the server configuration.

To the top of this page

How do I set up a Shadow Directory for StarTeam?

1. Create a View in the StarTeam project. This view should be created at the top of the project tree. This should be a derived view. The name of the view could be Shadow Directory. In the shadow view, the working directory should be set to a network drive or directory. Please use UNC names ie. \\smartsys\shadow\shadow1.

2. You should set the security on the Shadow View to allow Administrators and the ghost shadow administrator access to this view. The ghost shadow administrator user is a user id created by you to allow command line function to check out files to the Shadow directory.

3. You will need to create a batch command that will store the follow command line function:

• This command line function will update the shadow directory with only missing or out of date files in the shadow directory:

I.E. STCMD30 co /p "ghostshadow:password@STProject3:1024/StprojectName/Shadow

Directory" /is /q /x /f NCO *.*

/p Indicates what project is to be used.

The full syntax is:

"username:password@hostname:port/ProjectName/ViewName/Folder/".

• If the username is omitted then the current user’s login name is used.

• If password is omitted then the user is prompted to enter the password.

• If hostname is omitted then hostname defaults to localhost.

• If port is omitted then it defaults to 1024.

• ProjectName is always required.

• If View Name is omitted then the default view is used.

/is Applies the command to all child folders. Without this option, the command applies only to the specified folder.

/q Suppresses progress reporting. Without this option, messages about each action appear on the screen as the action is performed.

/x Bypasses error messages. Without this option, you will have to confirm error messages.

/f NCO Specifies the checkout of all files that need to be checked out. These are the files whose status is Missing or Out of Date.

4. Once you have ascertained that bat file is working as desired, start the NT Scheduler Service in the control panel.

5. At the Command Prompt using the AT command to setup the scheduled process, the batch file that contains the STCMD30 CO command should be scheduled to execute at what you think is appropriate intervals:

• AT command sample:

• C:\>AT \\ComputerName 00:00 /Every:M,T,W,Th,F C:\Starteam\Shawdow.bat

. To the top of this page

Where do I install the server?

You can install a StarTeam VirtualTeam Server (STVTS) on any Windows 95, Windows NT 4.0 (SP3), or Windows 98 (for StarTeam service pack 2) Intel computer with 32 MB RAM or greater and a 486 processor or better. The target system should support protocols that will permit your team members to connect to the server. You will have better performance when you install the STVTS on a Windows NT Server box. Systems with faster CPU’s and more RAM also offer improved performance (Example: 200Mhz CPU and 96 MB of RAM).

. To the top of this page

How do I connect to the Server?

You can connect to a StarTeam Virtual Team Server (STVTS) over a LAN, WAN, Internet, or RAS connection. The STVTS support the most popular network protocols in use today, including:

• LightWeight RPC: You may use this protocol when connecting the StarTeam Client to a Server on the same computer.

• NetBIOS over NetBEUI: You may use this protocol for a small LAN. This is the default protocol installed by Microsoft network systems.

• IPX/SPX: This protocol is better suited to support networks using Novell file servers but can be used on large LAN’s and WAN’s.

• Named Pipes are used for supporting large LAN’s and WAN’s. This allows better performance than NetBIOS over NetBEUI protocols.

• TCP/IP RPC: You can use this protocol for improved performance for non IPX/SPX networks.

• TCP/IP Sockets: This protocol must be used for certain StarTeam functionality. If you plan to use any item beyond the StarTeam Professional, this protocol is required. For example: to import 2.x StarTeam projects into 3.0 or later, the integrations, and the Web Connect Server all need this protocol. This protocol may also be used when your users are connecting by a remote dial up Internet connection. This is fastest protocol supported by StarTeam VTS.

. To the top of this page

Why does 3.0 or later require a server?

The StarTeam Virtual Team Server (STVTS) is required to support new features in StarTeam 3.0 or later. It was designed to support low bandwidth and broad as well. STVTS enhances performance over the Internet through data compression, encryption, and, for native archives, delta based check-out. It provides an additional level of security and control over the projects in a repository.

. To the top of this page

I can't find several of the IDE's that you say are part of StarTeam !

Were you looking on the custom install integration list?  We don't directly integrate with the indicated but through common integration for the fact that StarTeam is compatible with Microsoft's SCC interface.  When installing the integration components MS DEV and VB, StarTeam will integrate with the following:

• HahtSite 3.1 & 4.0

• MS Visual J++ 6.0

• Rational Rose 98

• NetDynamics Studio 5.0

• Microsoft Developer Studio & Visual Studio

• Borland's DELPHI 3 & 4

• Symantec Visual Cafe New IDE integration with the leading Java development environment. StarTeam is the first solution to integrate using the Visual Cafe API.

• Powersoft PowerBuilder versions 5 & 6

• Oracle Developer/2000 v. 1.5 and 2.1

• Allaire ColdFusion Studio v. 3.1.1 & 4.0.1

• Premia CodeWright v. 5.3

To the top of this page

Usage Questions Section

How do I safely backup my repository and server configuration files?

As you create server configurations the server creates files and directories for you to hold your configuration and project information.  These files are specific to your specifications and should be backed up.

These files and directories include:

The Configuration and cipher files:
Configuration\server.scg
Configuration\server.cph

Database files:
Database\StarTeamDB.mdb    (if you are using Access)

Vault:
Archive dir: *.*
Attachments dir: *.*

The following instructions are designed for teams using Access as their database.  If you are using other database, the corresponding database utility should be used.

The StarTeamDB.mdb, if you are using access, and vault directories should be backed up at the same time.  A mismatch between the database and repository may cause data to be lost and/or unusable.  For your backups to be most reliable it would be best to close down the STVTS when creating your backups. If the STVTS is not closed down, you have the risk of the database and vault being mismatched as a check-in may be in progress at the time of the backup.

If you are running the STVTS manually, the Shut Down option will close it gracefully.

If you are running STVTS as an NT Service you may go to the Services applet and stop the service there.  After the backup is completed, you may restart the service.

If you are running STVTS as an NT Service and prefer an automated backup which utilizes the NET Stop and NET Start commands.  See the example below for more details.

You should also be aware that your cipher phrase should be carefully documented and stored for safe keeping.  If you forget and loose your cipher phrase you can loose the access to your StarTeam projects.

Example:
1.Create a batch file to Stop the appropriate services, backup and Start the services. If you are also running Web Connect you will want to stop and start Web Connect as well.
Commands for batch file to stop services:

NET Stop StarTeamService

NET Stop "Web Connect"

Commands for batch file to start services:

NET Start StarTeamService

NET Start "Web Connect"

2.Start the NT Scheduler Service in the control panel.

3.At the Command prompt use the AT command to setup the scheduled process.

To the top of this page

How does e-mail work in StarTeam? (Separate document)

StarTeam Server is not an e-mail server; it is a limited, e-mail client. It does not track, route or receive e-mail. StarTeam sends e-mail to a MAPI compliant e-mail server. StarTeam assumes the email server is up and running and has an account StarTeam can use.

Here are some simple steps you can use:

4.1.1. Make sure that the system where you install the StarTeam Virtual Team Server (STVTS) can connect to your e-mail server. To check if e-mail is enabled for the computer:

A. Go to Control Panel and click on the Mail and Fax or Mail applet icon.
B. Make sure that the Mail and FAX Services dialog is not empty.

4.1.2. The STVTS will use the Mail and FAX user profile stored on the computer to connect to Mail Server. This profile must be named StarTeam.
4.1.3. The user records created through the User Manager need to have valid e-mail addresses.

Creating the StarTeam profile in the Mail and FAX Icon.

4.2.1. Go to Control Panel and click on the Mail and Fax or Mail applet icon.
4.2.2. Click on the Show Profiles.
4.2.3. Either copy the existing Profile and change the profile name to StarTeam or add a new Profile with the name of StarTeam.

To add a new profile in the Mail and FAX Icon:

4.3.1. Click on the Show Profiles.
4.3.2. Click on the Add button.
4.3.3. Select the Service that is your e-mail Server.
43.4. Enter the Profile Name.
4.3.5. Fill-in information about e-mail and server add connect.

Enable E-mail Support for Exchange Servers

4.4.1. Where StarTeam Server is installed, please check the Mail and FAX icon in the Control Panel and make sure that MS Exchange Server item is in the Services tab. Use the following steps to add the MS Exchange Server to the computer if the Exchange Server Services isn't installed.

A. Click on the Add button this will bring up a list of Mail Service select the MS Exchange Server Service to install the MS Exchange Server.

B. Enter the Name of the Exchange Server and a mailbox of a user in the Exchange Server then click on OK button.

4.4.2. Click on the Delivery tab and make sure that the system is sending mail to a mailbox on the MS Exchange Server.

StarTeam Team requirements

4.5.1. When you are using the Exchange Server the users in the StarTeam User Manager needs either the X400 or SMTP mail address in the user's e-mail address box.

4.5.2. You may want to create a mailbox that StarTeam can use named StarTeam Project Administrator.

To the top of this page

How do I set an alternate-working directory?

Version 3.0 (Build 3.00.254.1) does not offer an alternate directory feature. However, you may use the View feature to achieve this goal. Create your own view or a view to share with others for a particular drive, deriving the view from the main or other parent. To maintain integrity and conformance with the parent view, you will want to make sure that you select "Do not permit branching". This will allow all changes in directory structure, files, and labels made in one view to "float" to the other, almost as if they were the same view.

The current version,  4.2 includes an alternate directory feature. New views will not be required for each different working directory.

To the top of this page

How do I add a user to more than one group in the User Manager?

Use the copy feature to assign a user to more than one group in the User Manager dialog window. Select the user with the mouse. Using the combination of the left mouse button and the control key, drag and drop the user to the new group. This will then add the user to the new group, without deleting him from the old one.

To the top of this page

How do I run a query or create a filter?

Creating a filter can help you view your data more efficiently. While in the StarTeam client, move the mouse cursor to the column header bar of the right upper pane of the project window. Right click on the information bar that contains the field headings such as name, status, locked by, etc. Select Filters from the small menu that appears. You can now create a new filter. If you currently are viewing the data in a manner you would like to reuse, you can use the menu item: "Save current settings as". You may also associate a query with your filter. To do this, select query and then new, so select query, and then new. For further information on queries and filters, please see Chapter 5, Managing Data of the StarTeam User's Guide.

To the top of this page

Troubleshooting StarTeam 2.x Import process

First, make sure you have Service Pack 1, which addresses some of the import problems and makes import feature more robust. In addition, you might want to do try these other things as well, to make sure things go smoothly.

You will want to make sure that you have administrator access in both StarTeam server user group and StarTeam 2.1 project. Lack of proper access can cause various problems.

Each 2.x project need to be imported in its own session.

If the import utility dialog box does not list any protocols, this means there is an incompatibility in the JavaVM information. Call or write support and we will give you more information on this. We are currently working to improve this item.

In some situations, the import is using the tmp or temp directory. Make certain that the location of this directory exists and has much space free.

In your project's directory, there is a directory with your project' name and the extension .vlt

Eg. myproject.vlt

You will want to go through this directory and delete all files of 0 length. Make sure you delete all files that meet the following conditions:

*.tmp

_*.*

*.*_

To the top of this page

How can I import all file versions?

First, make certain you have unchecked the default check box for Tip revisions only. You also need to have administrator access in both the StarTeam server user group and the StarTeam 2.1 project.

To the top of this page

How do I use StarTeam to version control my System Architect encyclopedias?

Never ever try to do any work on individual files in an encyclopedia from the StarTeam Client interface! This will result in a corrupt encyclopedia!

Creating a new project from an existing SA Encyclopedia:

1. Start your StarTeam GUI client but do not open any projects.

2. Create a new project for the encyclopedia that you want to version control by dragging the SA Encyclopedia folder from the Windows Explorer onto the empty StarTeam GUI window.

3. From the "Create Project Wizard", select the server where you want to store your new project and click on the "Next" button.

4. Log on to the server with your User Name and Password. You must have the proper Access Rights to create a new project. If you don't, please see you StarTeam Server Administrator.

5. Enter a name for your new project and a description and click on the "Next" button.

6. In the next dialog LEAVE THE DEFAULT WORKING FOLDER as it is! In a multi-user environment, your work in SA will only exist in your local copy if you try to create your own local working folder of the encyclopedia.

7. In the next dialog, click Finish and your new project is created.

When StarTeam has created the new project in it's database, the 3 pane window will open. In the upper pane all files will have the status Missing. You now need to add all the files in the Encyclopedia to the the project:

1. Click on Name in the header bar to show all files.

2. Right click in the files pane and select "Select | Select All" from the pop-up menu.

3. With all files highlighted, right click in the files pane and select "Add Files" from the pop-up menu.

4. In the Add Files dialog, enter a label in the "Revision Label" field  such as "Initial Revision" and click on the OK button.

Checking in the Encyclopedia.

1. Click on Name in the header bar to show all files.

2. Right click in the files pane and select "Select | Select All" from the pop-up menu.

3. With all files highlighted, right click in the files pane and select "Add Files" from the pop-up menu.

4. In the Add Files dialog, enter a label in the "Revision Label" field and click on the OK button.

Checking out an older version of the Encyclopedia.

Checking out an older version of the Encyclopedia from the StarTeam version control system is done entirely from the StarTeam  GUI client. The reason for this is that the standard StarTeam client interface gives the user full control in order not to overwrite the current version being worked on.

Do not use Time Travel when checking-out a System Architect encyclopedia!

Do not use the same working folder as your current version as that will overwrite all your work in progress!

Follow these steps to checked-out a previously check-in version:

1. With the correct System Architect encyclopedia project open in the StarTeam GUI client, select “View | New View� from the menu.

2.  Select the “Permit items to branch within this viewâ€Â� check-box.

3. Select the “Branch none� radio button.

4. Select “Next�

5. Name the view with the version name that you are going to check out.

6. In the default working folders dialog, make sure that you create a new folder for this version.

7. In the “Specify Base Configuration� dialog click on “Labeled configuration� and select the version that you want to check out.

8. Select all files.

9. Check out all.

10. Start System Architect and open the encyclopedia that you just created.

To the top of this page

Will StarTeam work on dial-up connections?

The entire product is Internet enabled. Every interface - GUI, CLI, IDE integration, browser was designed for distributed development teams. ST is optimized for low bandwidth (modem connections) and public networks (the Internet and telephone lines). The feature that makes the product optimized for low bandwidth is the ability to send only the file differences of only the modified files from either the client or the server in a compressed format. The features that make ST optimal on public networks is the ability to use four different types of encryption and the administrators ability to set the encryption level based on the client's IP address.

To the top of this page

How does the StarTeam promotional model work?

Using Views you can setup your own promotional model. Here is a generic example based on promotion from some body of code, to a development area to quality assurance/testing area, and finally to a production area, which illustrates what can be done presently in StarTeam.

1. Create the project (add files and folders).

2. Create a Development View:

• Derive the view from the current view, branch none. (To change the working directory is the option of the project administrator).

3. Go to Development View

• Select all Files.

• Check Out all files.

• This is the development area. When files are ready for testing developer will do a Force Check In on all files with a Revision Label "Testing".

4. Create a Testing View.

• Derive from the current view (Development), no branching, change the working directory.

• Set Filter to "Files in Project".

• Select All Files.

• Check out all files with label "Testing".

5. Files are tested, if files fail a Change Request is completed.

6. If files pass testing, check In all files with Revision Label "Production"

7. From the Testing View Create a new view:

• Derive view from current configuration and select a new working directory for the production view.

8. Select the Production View Select all Files:

• Check out files based on label "Production".

• This is the view a code ready for Production.

The promotional model as a formal feature is targeted for StarTeam Enterprise Edition.

To the top of this page

How Do I "recursively" check out files and folders in "one step"?

Checking files in/out as a group is best accomplished by using the sorting and grouping feature in StarTeam. This feature can be combined with a filter to make the job easier. Here is a step by step example...

1. In the StarTeam GUI select the "File" tab and right click on the column headings of the list view (where it says Names, Status, Locked by, etc.).

2. From the context menu select "Filters" then from the filters dialog select "New"

3. In the new dialog enter a name for the filter such as "Grouped Status". You have the option here of making this a private filter or making it public for all users.

4. Once created, the new filter must be defined. Select "fields" and add the desired data fields to the filter (Name, Status, Folder, etc.).

5. The next step is to set the sorting and grouping. In the Sort and Group dialog select "Status" as your first criteria and set the group by checkbox on.

Using this new filter you will see that all files needing check in/out are represented as a collapsed header. Selecting the header only and setting the scope button to scope all you may check in/out in a single operation from the toolbar or the menu selections. Additionally, the user may place focus on any folder or subfolder in the project tree to limit the criteria.

Filters and sorting/grouping may be set for the other components such as change requests. This is a valuable tool for reporting purposes as well. Reports are generated based on the data displayed in the GUI. This method allows for easy display of data in a format that is custom for each user.

To the top of this page

WebConnect

How Do I install WebConnect:

Setting up Web Connect and getting images to load correctly can sometimes be difficult. First, and foremost, you must make sure you have added your images to your repository. The images are in a Sub-directory in Web Connect (probably under your installation directory for StarTeam) The images sub-directory is called Images. You will want to add this folder, and all its files, to a project. Create a new project for this purpose and call it Web Resources. (Make sure all the files get added!)

Under the HTTP tab in the Web Connect Administrator, select the check box "Permit direct HTTP access to Web Connect".

The Web Resources project would have a single folder off the root called images, and in it all the images for your Web Connect Server. Once this is setup, you will need to venture into the Web Connect Administrator and tell the Administrator where to find these files. Click on the HTTP tab. Then pick your project with the images (in our example Web Resources) and then select browse, find the Images folder, then press OK.

When a user logs on with his browser, he needs to see images right away, even before he technically "logs on" to a project. Because the Web Connect Server needs to grab a few image files even before a user logs on, another special user account is created to reach out to the StarTeam Virtual Team Server and get those images. This account is a guest account, and is set up in the Web Connect Administrator itself. Select the project tab again, then select the project alias that has the web images (Web Resources) and then click on properties. Select the Users Tab, then select "allow Guest Account log on". Set the user name to Guest. Leave the password blank. In the StarTeam VirtualTeam Server, you will also need to create a user called Guest. Check blank password. This will enable special access to the files stored in the Web Resources project, regardless of the user, so that the user will always get graphics and other items.

When In Web Connect Administrator, select the "Server" button in the "Projects" tab. Select a server and press "Modify" and change the user down at the bottom of this dialog to user name Administrator, password Administrator (make sure these values are consistent with the Administrator account in StarTeam VirtualTeam server.

Error Messages

I'm getting one of the following system messages:

VC++ runtime error: r6025 Pure Virtual Function call.
MFC runtime error: r6025 Pure Virtual Function call.
Invalid signature
Internal Application error
These first three errors are related to the RSABASE encryption dll not being appropriate or compatible. The last error may also be related to problems in the RSABASE.DLL or other problems as well.

Verify that your team is currently using the StarTeam, service pack 1.

If you have Microsoft Internet Explorer 4.0 on your system, verify the build. If it is less that 4.27xxx, install the IE4 that is on our product CD. This browser includes the RASBASE.DLL and JavaVM and may conflict with the StarTeam installation. A matching version of Microsoft Internet Explorer 4.01 is available on the StarTeam installation CD.

If you are running Windows NT:

10.1.1. Go to regedit: H_Key_local machine\Software\Microsoft\Cryptograpy\Defaults\Provider\: You must see three keys for the next steps to work.

10.1.2. Check version of RSABASE.DLL. This file should be in winnt/sys32 dir and 98K, version 5.00.1651.1

10.1.3. If it is the correct version: at DOS prompt type the command: REGSVR32 RSABASE and press .

If you are running Windows 95:

10.2.1. Execute MSJAVX86.EXE on the SP1 CD: Utilities/JavaVM dir.

10.2.1Next verify that RSABASE.DLLl is on the path and at a DOS prompt: REGSVR32 RSABASE

To the top of this page

I'm getting the following system message: "User error: Unable to read/write to registry". How can I get around it?

This problem occurs when a user logs onto the computer and does not have permission to write to the "HKEY_LOCAL_MACHINE\Software\StarBase" reg key. An easy workaround is for an administrator to log onto the computer and change the security settings (use regedt32.exe) for the StarBase specific key to allow domain users or other trusted accounts to write to the StarBase key and subkeys. This will pose a very minimal security risk in that only a very specific key will have been granted additional rights to only trusted user accounts.

To the top of this page