Implementing Siebel Business Applications on DB2 for z/OS > Customizing a Development Environment >

Roadmap for Creating Custom Extensions to the Siebel Schema

To extend the Siebel Schema by creating extension columns or tables, you need to perform the following tasks:

1. Plan the new custom object, for example, determine the type of object you need to create, the name of the object, and its size.
2. Add a storage definition for the new object to the storage control file of the Siebel Schema being extended.

   For information on this task, see Amending the Storage Control File for New Schema Objects.

3. Create the new object in Siebel Tools; this adds the object definition to the Siebel Repository thereby updating the logical schema definition in the development environment.

   The process of adding a new object in Siebel Tools is the same on z/OS as on other platforms. However, you need to make sure that you select the check box on the Database tab of the Development Tools Options dialog under the View menu. This option validates the object's compliance with DB2 for z/OS sizing conventions.

4. Apply the physical schema extensions to the development database, specifying the storage control file you updated in Step 2. You can apply the changes directly or generate the DDL into a file which can be applied on the z/OS host later.
   • If you are developing on DB2 for Windows or UNIX, follow the procedures in Applying Schema Extensions to the Local Development Database.
   • If you are developing on DB2 for z/OS, follow the procedures in Migrating Customizations from Development to the Target Database.

     Some organizations do not allow direct database extension. Siebel Tools does not allow the Apply/ DDL button to be disabled but the Apply process fails if developers do not have appropriate database privileges (such as CREATEDBA and DBADM). If you do not want developers to extend tables directly, you can control this using database privileges. In this case, developers follow the procedures in Migrating Customizations from Development to the Target Database to apply schema extensions to their development databases.

5. If you chose to generate the DDL into an output file, review the file, then have your DBA execute the file on the z/OS host.
6. In your development environment, update and test the configuration changes that apply to the extensions you made.
7. Apply the schema extensions on the production database on the z/OS host.

   For information on this task, see Process of Applying Schema Extensions to the Target Database.