Bookshelf Home | Contents | Index | PDF     

Implementing Siebel eBusiness Applications on DB2 UDB for z/OS and OS/390 > Customizing a Development Environment > Applying Schema Extensions to the Target Database >

Migrating Customizations from Development to the Target Database

CAUTION:  Before you migrate your customizations from your development database to your target database, you must validate your storage control file. See Validating the Storage Control File.

When migrating customizations from your development source to your target database on the DB2 host, you can use one of two modes of execution:

  • Run DDL Automatically. Select this to apply the DDL and DML required to create the Siebel Schema directly against the database, using an ODBC connection.
  • Generate DDL Into Files. Select this to generate the DDL required to create the Siebel Schema.

    You must later use Siebel-provided scripts, your own FTP, or a similar file transfer program to transport the DDL to the zSeries machine, where the DBA executes it using customary methods, for example SPUFI.

This section describes the DDL-generation mode of execution that is generally used under a change-management system.

If your development environment is on DB2 UDB for z/OS and OS/390, your DBA can also clone it to the target database. For more information, see Cloning an z/OS and OS/390 Database.

NOTE:  Siebel 7 does not support customized database triggers. If you have created customized triggers on your Siebel base tables, you must disable them before migrating the database schema. You must re-create the triggers after the migration is finished.

To migrate the schema under Windows

  1. Launch the Database Server configuration wizard:

    Choose Start > Programs > Siebel Enterprise Server 7.x.x > Configure DB Server.

    or

    1. Open a command prompt.
    2. Go to the SIEBSRVR_ROOT\BIN directory.
    3. Enter the following command:

    ssincfgw -l ENU -v Y

    1. In the screen that appears, select dbsrvr.scm.
  2. In the Gateway Name Server Address screen, type the following values as you recorded them in your copy of Deployment Planning Worksheet.
    • Gateway Name Server Address. The alias of the host on which you installed the Siebel Gateway Name Server.
    • Enterprise Server Name. The name you gave to your Enterprise Server, for example, siebel.

      To continue, click Next.

  3. In the Siebel Server Directory screen, perform either of the following tasks:
    • Accept the default value displayed in the Siebel Server Directory field. (This is the SIEBSRVR_ROOT directory, for example, D:\sea7xx\siebsrvr.)
    • Use the browse button to select an alternate directory path.

      To continue, click Next.

  4. In the Siebel Database Server Directory screen, perform either of the following tasks:
    • Accept the default path displayed in the Siebel Database Server Directory field. (This is the DBSRVR_ROOT directory, for example, D:\sea7xx\dbsrvr.)
    • Use the Browse button to select an alternate directory.

      To continue, click Next.

  5. In the RDBMS Platform screen, select the database platform you use, for example, IBM DB2 UDB for z/OS and OS/390.

    To continue, click Next.

  6. In the Siebel Database Operation screen, select Migrate Repository, and then click Next.
  7. In the OBDC Data Source Name screen, type your source ODBC connection name, and then click Next.
  8. In the Database User Name screen, enter your source database username and password, confirm the password by typing it again, and then click Next.
  9. In the Schema Qualifier screen, enter the schema qualifier in uppercase and security group ID from your copy of Deployment Planning Worksheet and then click Next.
  10. In the Source Database Repository Name screen, type the source and target database repository names—typically Siebel Repository for both, and then click Next.
  11. In the Target RDBMS Platform screen, select IBM DB2 UDB for z/OS and OS/390, and then click Next.
  12. In the Target Database ODBC Datasource screen, type your target ODBC connection name, and then click Next.
  13. In the Target Database User Name screen, enter your target database username and password, confirm the password by typing it again, and then click Next.
  14. In the Target Schema Qualifier screen, type the target schema qualifier in uppercase and the target group authorization ID, then click Next.
  15. In the Migrate Repository Mechanism screen, select the Generate DDL Into Files option, and then click Next.
  16. In the DDL Output Directory screen, type the DDL output directory and storage control file, and then click Next.

    For example, use DBSRVR_ROOT\db2390\dboutput\dev2prod and DBSRVR_ROOT\db2390\my_storage_file.ctl, respectively.

    The Configuration Parameter Review screen appears.

  17. Review the parameters, and then click Finish.

    The runnow screen appears, giving you the choice of applying the configuration now or applying it later (and specifying the command line to apply it later).

  18. Click OK to apply the configuration now.

    The Siebel Upgrade Wizard launches.

  19. Click OK to perform the migration.

    The Siebel Upgrade Wizard runs, creating the following files:

    • ftpsync.txt. FTPs the files that are migrating from development to production on the DB2 Host.
    • jobsync.txt. Sets up the migration from development to production process on the DB2 Host. The job is sent to the mainframe using ftpsync.txt.
    • unload.ldc. Unloads control cards used to unload tables during the migration from development to production process on the DB2 Host.
    • load.ldc. Loads control cards used to load tables during the migration from development to production process on the DB2 Host.
    • schema.sql. Applies schema changes from the schema ddl data set during the migration from development to production process on the DB2 Host.
    • bumpver.sql. Bumps up the Siebel Schema version during the migration from development to production process on the DB2 Host.

To migrate the schema under UNIX

  1. Source environment variables from $SIEBEL_ROOT.

    SIEBEL_ROOT should be the path of your Siebel installation directory.

    LANGUAGE should be set to the language in which the Configuration Wizard prompts appear, for example, enu for U.S. English.

    NOTE:  LANGUAGE is not the same as LANG; the former is the language in which the Configuration Wizard runs, while the latter is the code for the Language Pack you installed.

    If either of these values is incorrect or empty, reset them using one of the following commands, as appropriate to the shell you use:

    csh

    setenv SIEBEL_ROOT New Value

    setenv LANGUAGE New Value

    ksh

    SIEBEL_ROOT=New Value ; export SIEBEL_ROOT

    LANGUAGE=New Value; export LANGUAGE

  2. Go to $SIEBEL_ROOT /bin and enter:

    dbsrvr_config.ksh

    This launches the Database Server configuration wizard.

  3. Review the values of the following environment variables and confirm whether the settings are correct by entering either Y or N.

    NOTE:  If either the SIEBEL_ROOT or LANGUAGE value is not set or is incorrect, you must correct it before proceeding.

  4. Specify the path of your Siebel Server root directory, or accept the default by pressing ENTER.
  5. Specify the path of your database server root directory, or accept the default by pressing ENTER.
  6. Enter the number that corresponds to your database platform.
  7. From the Select Database Operation menu, choose Migrate Repository (4).
  8. Enter the number that corresponds to the language you are using, typically 1 for English.
  9. Enter your source ODBC connection name.
  10. Enter your source database username and password.
  11. Enter the schema qualifier in uppercase from your copy of Deployment Planning Worksheet.
  12. Specify the source database repository name, or accept the default by pressing ENTER.
  13. Specify the target database repository name, or accept the default by pressing ENTER.
  14. Select the target database platform by entering the number that corresponds to IBM DB2 UDB for z/OS and OS/390.
  15. Enter your target ODBC connection name.
  16. Enter your target database username and password.
  17. Enter the target schema qualifier in uppercase.
  18. Enter the target group authorization ID, or accept the default ID, SSEROLE by simply pressing ENTER.
  19. In the Select Installation Mechanism screen, select Generate DDL Into Files (1).
  20. Specify the DDL output directory, for example
    DBSRVR_ROOT/db2390/dboutput/dev2prod.
  21. Specify the storage control file, for example
    DBSRVR_ROOT/db2390/my_storage_file.ctl.

    The configuration parameters are listed and you are asked if you want to run srvrupgwiz.

  22. Enter Y for yes.

    The Siebel Upgrade Wizard launches.

  23. You will receive a message that states that the files with the Siebel Schema modifications have been generated in the DDL Output Directory. Select Yes to exit now and apply the files.

    The following files are created:

    • ftpsync.txt. FTPs the files that are migrating from development to production on the DB2 Host.
    • jobsync.txt. Sets up the migration from development to production process on the DB2Host. The job is FTPd to the mainframe using ftpsync.txt.
    • unload.ldc. Unloads control cards used to unload tables during the migration from development to production process on the DB2 Host.
    • load.ldc. Loads control cards used to load tables during the migration from development to production process on the DB2 Host.
    • schema.sql. Applies schema changes from the schema ddl data set during the migration from development to production process on the DB2 Host.
    • bumpver.sql. Bumps up the Siebel Schema version during the migration from development to production process on the DB2 Host.
    
Implementing Siebel eBusiness Applications on DB2 UDB for z/OS and OS/390