Developing and Deploying Siebel Business Applications > Setting Up the Test Environment > Process of Moving Data to the Test Environment >

Moving Repository Data

This task is a step in Process of Moving Data to the Test Environment.

This topic describes how to move repository data, such as applets, views, and business components. The tool you use to move data depends on the type of configuration changes you must move:

• If you must move a database schema change, then use the Repository Migration Configuration Utility. For example, if you add columns to a base table, which you did do in Configuring the House and Opportunity Entities.
• If you must move only user interface and business object definitions, then you can use the Export and Import Repository Utilities.

For more information about managing repositories, see Going Live with Siebel Business Applications.

To move repository data

1. Prepare to move repository data:
   1. Make sure each developer checks in their projects from their local database to the server database.
   2. Instruct your developers not to make any more changes after you begin to move repository data. These changes might be lost.
   3. Stop all server tasks on the target environment.
   4. Disconnect database access until the move is complete.
2. To start the Database Server Configuration Utility, in Microsoft Windows, choose the Start menu, Programs, Siebel Enterprise Server version_number, and then the Configure DB Server menu item.
3. In the Gateway Server Address dialog box, specify your Siebel Gateway Name Server Address and Enterprise Server Name, and then click Next.
4. In the Siebel Server Directory dialog box, accept the default value or click Browse, and then click Next.
5. In the Siebel Database Server Directory dialog box, accept the default value or click Browse, and then click Next.
6. In the RDBMS Platform dialog box, choose the platform for your environment, and then click Next.
7. In the Siebel Database Operations dialog box, choose Migrate Repository from the list of operations, and then click Next.

   For more information, see About the Repository Migration Configuration Utility.

8. Proceed through each dialog box using values from the following table, and then clicking Next.

   Dialog Box	Description
   ODBC Data Source Name	Enter the name of the ODBC data source.
   Database User Name	Enter the source database user name and source database password.
   Database Table Owner	Enter the source database table owner and source table owner password.
   Source Database Repository Name	Enter the database repository name and the target database repository name.
   Target RDBMS Platform	Choose the target RDBMS platform.
   Target Database Encoding	Choose whether the target database is Unicode.
   Target Database ODBC Datasource	Enter the target database ODBC datasource.
   Target Database User Name	Enter the target database user name and password.
   Target Database Table Owner	Enter the target database table owner and table owner password.
   Index Table Space Name	Enter a value only if you indicated that the target database is IBM DB2. Enter the index table space name and 4 KB Table Space Name.
   16-KB Table Space Name	Enter a value only if you indicated that the target database is IBM DB2. Enter the 16 KB table space name and 32 KB table space name.
   Index Table Space Name	Enter a value only if you indicated that the target database is Oracle. There are no 4 KB, 16 KB, or 32 KB table spaces in Oracle. For Microsoft SQL server, there are no dialog boxes for table spaces.
   Configuration Parameter Review	Summary screen that displays a list of your choices. To accept this configuration, click Finish.

About the Repository Migration Configuration Utility

The Repository Migration Configuration Utility is a wizard that prompts you for the required information as you proceed through a succession of dialog boxes. You start the Repository Migration Configuration Utility from the Siebel Database Configuration Utility. When you complete the configuration session, you can use the command line to perform the move immediately or at a later time. The Repository Migration Configuration Utility does the following work:

1. Exports repository data from the source environment
2. Imports the object definitions
3. Updates the physical database schema of the target database.

As a result of this work, the database schema and object definitions in the target environment matches the database schema and object definitions in the source environment.