Configuration Guidelines > Database Extensibility >

Dynamic and Advanced Database Extensions

As with all configuration work, first perform any database extensibility in a local database. This provides the ability to recover if there are any unexpected issues and allows the thorough testing of changes before they are made available to other developers. The following steps illustrate this process:

  1. Check out the project.
  2. With Siebel Tools running in a local database, check out the project containing the table that you want to modify. Typically, this is the Newtable project.

  3. Update the logical schema definition in the local environment.
  4. Make your changes to the requisite tables, columns, indexes, and mappings in the project. For more information, see Siebel Tools Reference.

  5. Apply the physical schema extensions to the local database.
  6. When you are finished making changes, complete the following tasks to update your local environment:

    1. In the Table List window, click Apply.
    2. This applies your changes to the local database. You may get a warning message that database extensibility is not supported from the client.

    3. Specify Current Query, All or Current Row. Enter your local database password (which must be in uppercase), and then click Apply.
    4. In the Table List window, click Activate.
    5. Thoroughly test any changes. Typically, you expose data model changes in screens or views, so you must test any of them that may have been affected by your changes. You must also check out any updated copies that have been modified by other developers, and test them in your local database.

  7. Apply the changes to the server database.
  8. Check in the Newtable project in order to update the repository schema definition on the server. At this point, the logical database schema of the server database has been updated, but the changes have not been applied to the physical server database.

  9. Repeat Step 3 while connected to the server using Siebel Tools.
  10. To minimize the impact of your changes on other developers, make any bulk changes to the schema at the beginning of each project phase. If you make changes during a project phase, then these need to be distributed to all mobile users. You can use Siebel Anywhere to distribute a schema change; otherwise, you generate new database extracts for all of your mobile users before you can progress to the next phase. For more information, see Siebel Tools Reference.

 Configuration Guidelines 
 Published: 18 April 2003