The first time you start a new server configuration,
Atlas Hub creates all tables in the database you specify. This section explains how to create
an
Atlas Hub configuration and start it for the first time. It assumes that you want
Atlas Hub to automatically create a
Microsoft SQL Server or
Microsoft SQL Server Express database. If that is not the case, see
Creating a Database Manually.
Database names should:
- Begin with a letter.
- Contain letters and numbers only.
- Not contain spaces.
- Not be a SQL reserved word such as
create,
delete,
if,
then,
else, or
goto.
Important: The
Server Administration database options may fail to run for databases with names that do not follow these guidelines.
To create a server configuration using an existing database:
-
Start the
Server Administration tool.
Click
.
The
Server Administration tool opens.
-
Click
.
The
New Configuration dialog box opens.
-
Enter the new configuration data:
-
Type the name of the configuration in the
Configuration Name field.
If you want the server configuration to have the same name as the database (a nice convention, especially if you have several
server configurations), you must follow the database naming conventions explained at the beginning of this section.
-
Type or click
Browse to specify the
Repository Path location to be used to store log files and other information. If the repository path that you enter does not exist, the application
creates it for you. The
Repository Path is also the location for the default hive.
-
Select
Microsoft SQL Server/SSE (the default) from the
Database Type list.
-
Check the option to
Create new
StarTeam database, so that
Atlas Hub automatically creates the database.
-
Create an initial hive for the Native-II vault by doing one of the following:
- Accept the default settings
-
Leave the
Default option selected and proceed to the next step. With the default settings,
Atlas Hub:
- Creates an initial hive named
DefaultHive.
- Creates subfolders on the repository path named
Archives and
Cache to be used by the
DefaultHive.
- Stipulates that the maximum cache size is 20% of the space currently available on the drive on which the cache is located.
- Uses the default setting of 600 seconds (10 minutes) between cache cleanups.
- Uses the default setting of 95% for the storage threshold, the point at which this drive is considered full.
- Specify custom values
- Select the
Custom option and change any of the hive settings.
-
Click
Next.
-
Enter the server and database information:
-
Enter the information for creating the data files and transaction logs, and click
Finish.
Note: We recommend keeping the data files and transaction log files on different physical drives under their own disk controllers.
The default settings are appropriate for your use if you have fewer than 15 users and expect to store 1GB or less data.
If you are very familiar with
Microsoft SQL Server and
Microsoft SQL Server Express databases, you may choose to make some changes by first clearing the
Use Default Configuration check box and then altering sizes and locations for data files and log files.
Use at least 3 data files and at least 3 transaction log files when creating a database, because
Microsoft SQL Server and
Microsoft SQL Server Express databases use a proportional fill strategy. This way all the files tend to become full at about the same time.
To avoid fragmentation, make the data files as large as possible, based on the maximum amount of data expected in the database.
The
Server Administration tool displays your new server configuration as a child of the
Local node.
Note: In addition to creating the server configuration,
Atlas Hub adds information about the new server configuration to your
starteam-server-configs.xml file. For more information about this file, see the
Server Administration Tool Help.
-
By default, all server configurations are set to use the TCP/IP endpoint (port) 49201. However, each server configuration
on a given computer must have a unique endpoint so it is recommended that you edit the default endpoint. To change the endpoint:
-
Select the server configuration.
-
Click the
Start with Override button (or click
from the main menu). The
Start with Override dialog box opens.
-
Enter the endpoint that you want to use in the
TCP/IP Endpoint field, and click
OK.
-
Be sure to configure your new server configuration (for information, see the
Server Administration Tool Help) and plan a backup schedule for it.