Configuring Siebel Business Applications > Configuring Tables >

Applying a Data Layer Customization to the Server Database

You must apply your customization to the physical server database. Until you do this, Siebel CRM only updates the logical database schema, as stored in the repository tables of the Siebel database. You can use Siebel Tools or the Database Configuration Utility to apply a customization to the data objects layer.

CAUTION:  If a table is marked as Inactive in the Siebel Repository, and if you click Apply/DDL, then Siebel Tools removes the underlying table from the Siebel database.

To apply a data layer customization to the server database

1. Test your customization in the local environment.
2. Prepare the server database:
   1. Make sure all remote users synchronize.
   2. Make sure all connected clients are disconnected from the database server.
   3. After Siebel CRM merges and routes all transactions for remote users, stop all Siebel Servers.
   4. Do a full backup of the server database.
3. Connect to the Siebel Server.
4. Check your projects into to the server database.
5. In the Object Explorer, click Table.
6. In the Tables list, locate the table where you must apply a modification to the Siebel database.
7. In the Tables list, click Apply/DDL.

   Siebel Tools disables the Apply/DDL button for tables that contain External in the Type property. For more information, see Overview: Siebel Enterprise Application Integration.

8. In the Choose option dialog box, choose the Apply option, and then click OK.
9. In the Apply Schema dialog box, perform Step 7.

   If you receive an error message and cannot apply your customization on the server database, then you must use the Database Server Configuration Utility. For more information, see Downloading a Data Layer Customization to Remote Users.

10. In the Apply Schema dialog box, click Apply.
11. In the Tables list, click Activate.

    Siebel Tools increases the version of the custom database schema and prepares the upgrade of the remote client. The customization now exists physically on the server database.

12. Restart the Siebel Server.

    Your customization tables and columns are now available to use in your configuration.

Downloading a Data Layer Customization to Remote Users

After you check in extensions to your server database and apply the physical database, you can download the schema modifications to remote users.

NOTE:  For Siebel Innovation Pack 2016, the local database for Siebel Tools or for Siebel Mobile Web Client uses Oracle Database XE. SAP SQL Anywhere is no longer available or supported.

To download a data layer customization to remote users

1. Make sure all remote users perform a full synchronization.
2. If you use Siebel Anywhere, then do the following:
   1. Create an Upgrade Kit on your Server database that includes the Siebel Database Schema as the upgrade kit component.

      For more information, see Siebel Anywhere Administration Guide.

   2. Click Activate on the Upgrade Kits View to make the upgrade kit available.
3. If you do not use Siebel Anywhere, then do the following:
   1. Log in to Siebel Tools while connected to the server database.
   2. In the Object Explorer, click Table.
   3. In the Tables list, locate the table that includes your customization.
   4. In the Tables list, click Activate.

      Siebel Tools increases the version of the custom database schema and prepares the upgrade of the remote client.

4. To recreate the template local database, run gennewdb.

   For more information, see Siebel Remote and Replication Manager Administration Guide.

5. Reextract remote clients.

   Each remote client must reinitialize the local database with the extracted data. This procedure differs depending on if you use Siebel Anywhere.

6. If you use Siebel Anywhere, then click Distribute in the Upgrade Configurations View.

   This step makes the new custom schema version available for a schema upgrade. You must manually set the Required flag. For more information, see Siebel Anywhere Administration Guide.

If you do not use Siebel Anywhere, then manually reextract and reinitialize all remote user databases.