Creating and Starting a Server Configuration with an Oracle Schema User

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 the Oracle tablespace and a schema user named StarTeam. If that is not the case, see Overview of Creating the Oracle Schema User Manually.

For new configurations, you must know the Oracle Database Server name and either the Oracle Service name or SID.

Start the Server Administration tool. Click Start > Programs > Micro Focus > Hub > Server Administration. The Server Administration tool opens.
Click Server > New Configuration. The New Configuration dialog box opens.
Enter the new configuration data:
1. Type the name of the configuration in the Configuration Name field.
2. 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.
3. Select Oracle from the Database Type list.
4. Check the option to Create new StarTeam database, so that Atlas Hub automatically creates the tablespace and schema user for the schema user.
5. 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.
6. Click Next. The Create an Oracle Schema User page of the wizard opens.
7. Type the Oracle Server name or SID in the appropriate field.
8. Optionally, if you are using a port other than the default, check Edit Database Port and type the port number in the text field.
9. Enter the database system password in the System password field.
10. Click Verify Connection to test the connection. If the connection fails, review and change your settings.
11. To keep the name of the server configuration and the schema user the same, both the New schema user name field default to the name you provided earlier for the server configuration. Change these names if you prefer to use different values.
12. Enter and confirm a password for the schema user name.
13. Click Next. The Create a Tablespace for StarTeam Schema page of the wizard opens.
14. The tablespace name defaults to the name of your server configuration. Change this name if you prefer to use a different value.
15. If you have fewer than 15 users and expect to store 1 GB or less of data, the default settings are appropriate for your use. If you are very familiar with Oracle schema users, you may choose to alter the names, sizes, and locations of the data files. For more information, see Guidelines for Data Files. To avoid fragmentation, make the data files as large as possible, based on the maximum amount of data expected in the database. Use at least three data files when creating a tablespace because:
  - There is a size limit of 2 GB per data file.
  - Fewer files can result in slow response times when insert activity is heavy.
16. Click Finish.
  This action re-displays the Server Administration tool, which shows 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:
1. Select the server configuration.
2. Click the Start with Override button (or click Actions > Start with Override from the main menu). The Start with Override dialog box opens.
3. 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.