Implementing Siebel eBusiness Applications on DB2 UDB for z/OS and OS/390 > Siebel Schema Installation on the DB2 Host > Performing a Standard Installation >

Performing a Standard Installation Under Windows


Perform the following steps for a standard installation under Windows.

To perform a standard installation under Windows

  1. From the Start menu, navigate to Programs > Siebel Enterprise Server Configuration 7.x.x > Database Server configuration.

    The Siebel Gateway Name Server Address screen appears.

  2. Enter the values for the Siebel Gateway Name Server Address and Enterprise Server Name 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.

      CAUTION:  If you subsequently add a new language (after you complete your initial installation with your initial set of languages), leave the Gateway Name Server Address and Enterprise Server Name fields blank.

  3. On the Siebel Server Directory screen, perform one of the following tasks:
    • Accept the default value displayed in the Siebel Server Directory field. (This is the SIEBSRVR_ROOT directory, for example, C:\sea7xx\siebsrvr.)
    • Click Browse to select an alternate directory path.

      To continue, click Next.

  4. On 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, C:\sea7xx\dbsrvr.)
    • Click Browse to select an alternate directory.

      To continue, click Next.

  5. On the RDBMS Platform screen, select the RDBMS platform you use, in this case, DB2 UDB for z/OS and OS/390.

    To continue, click Next.

  6. On the Siebel Database Operation screen, select Install Database.

    To continue, click Next.

  7. On the Select Installation Operation screen:
    • If you are configuring Siebel Database Server software for the first time, click Install Siebel Database.
    • If you have already installed your Siebel Database Server software in its base or primary language, and want to install a new language, proceed to Installing Multilingual Seed Data.
    • Install Siebel Data Warehouse Database. For information on this installation option, see Siebel Data Warehouse Installation and Administration Guide.

      To continue, click Next.

  8. On the ODBC Data Source Name screen, indicate the following values for your ODBC data source:
    • Accept the default name of the ODBC data source, SiebSrvr_Siebel, or enter the database alias you prefer to use for the data source.

      The database alias must have been previously registered within DB2 Connect, either by using the DB2 Client Configuration assistant or by natively registering to the DB2 Connect catalog, the Database, Node, and DCS entries.

      NOTE:  If you define database aliases, you must add the TXNISOLATION parameter to the database alias entry in the db2cli.ini file and set it to have a value of 1. For information on setting values in the db2cli.ini file, refer to the relevant IBM documentation.

      If you want to work with information on a different database server than the one currently pointed to, you can type in the ODBC name of that database server, as long as you previously registered it as an ODBC data source within DB2 Connect.

      The Siebel Server installation process automatically creates the data source, using the format SiebSrvr_EnterpriseServerName.

      NOTE:  There can only be one database server in a Siebel Enterprise Server, but another ODBC data source name could be used in generating a new Siebel Schema DDL.

    • Enter the name of the source database DB2 subsystem.

      To continue, click Next.

  9. On the Database User Name screen, indicate the following values for your database:
    • Database User Name. Type the ID (for example, SADMIN) used to log into the Siebel Database Server. This user ID should be part of the security group (secondary authorization group) with authorization to set the current SQLID to the schema name.
    • Database Password. Type the password for the ID used to log into the Siebel Database Server.
    • Database Password (confirm). Retype the password to confirm it.

      To continue, click Next.

  10. On the Siebel Schema Qualifier screen, indicate the following values for your Siebel Schema:
    • Siebel Schema Qualifier. Type the up to eight-character ID that identifies the Siebel Schema owner, for example, SIEBTO.

      NOTE:  This ID must be in uppercase, must start with a letter, and cannot include any special characters. This is the SQL Authorization ID stored in the CURRENT SQLID special register.

    • Security Group ID / Grantee. Type the group ID to which schema access is being granted, for example, SSEROLE.

      For more information about the group authorization ID privileges, see Security Concepts for z/OS and OS/390.

      To continue, click Next.

  11. On the Select Installation Type screen, select the appropriate type of installation; for example, to perform a standard installation, select Standard Install.
    • Standard Install. The standard installation option installs the database, using one of the Siebel-recommended default storage layouts.
    • Customized Install. For a customized installation, you will need to provide a storage control file, which you created and validated prior to performing this installation. This will allow you to create a custom database layout, best suited to your Siebel deployment. See Performing a Custom Installation for a description of the custom installation process.

      To continue, click Next.

      NOTE:  The following steps appear after you select Standard Install.

  12. On the Database Encoding screen, indicate whether your DB2 subsystem is ASCII or EBCDIC. For more information about choosing the code page for your subsystem, see Preparing for Implementation on the DB2 Host.
  13. In the Siebel Schema Layout screen, select one of the following layout options:
    • Siebel Schema without Partitioning. Choose this option if you want all tables only in segmented table spaces.
    • Siebel Schema with Partitioning. This layout includes a set of tables that is recommended for partitioning. The remaining nonpartitioned tables are in segmented table spaces. For more information on this option, see About Configuring Siebel Templates for Partitioning.

      For details about layout considerations, see Configuring the Database Layout.

      To continue, click Next.

  14. On the Storage Group for Table Spaces screen, indicate the values for the following parameters:
    • Storage Group for Table Spaces. Type the name for the table storage group.
    • Storage Group for Indexes. Type the name for the index storage group.

      To continue, click Next.

  15. On the 4KB Buffer Pool Name screen, indicate the values for the following parameters:
    • 4KB Buffer Pool Name. Type the 4-KB buffer pool name for your table spaces or accept the default, BP1. This buffer pool should already be activated and have access to it granted by the DBA.
    • 16KB Buffer Pool Name. Type the 16-KB buffer pool name for your table spaces or accept the default, BP16K1. This buffer pool should already be activated and have access to it granted by the DBA.

      For more information about layout considerations, see Configuring the Database Layout.

      To continue, click Next.

  16. On the 32KB Buffer Pool Name screen, indicate the values for the following parameters:
    • 32KB Buffer Pool Name. Type the 32-KB buffer pool name for your table spaces, or accept the default, BP32K1. This buffer pool should already be activated and have access to it granted by the DBA.
    • Index Buffer Pool Name. Type the buffer pool name for the indexes, or accept the default, BP2. This buffer pool should already be activated and have access to it granted by the DBA.

      To continue, click Next.

  17. On the Database Name Prefix screen, type the prefix for your database name. The default is SIDB.

    This prefix consists of up to four of the first characters in the names of your logical Siebel Databases. This prefix must start with a letter and cannot contain any special characters. All database names end in numbers.

    To continue, click Next.

  18. On the Select Installation Mechanism screen, indicate which installation mechanism you want to use:
    • Generate DDL Into Files. Select this to generate the DDL required to create the Siebel Schema.

      Use Siebel-provided scripts, your own FTP, or a similar file transfer program to transport the DDL (schema.sql and ddlview.sql) to the DB2 host, where the DBA executes it, using customary methods, for example, SPUFI or DSNTEP2.T

      To continue, click Next and proceed to Step 19.

    • Run DDL Automatically. Select this to apply the DDL and DML required to create the Siebel Schema directly against the database, using ODBC to connect.

      To continue, click Next and proceed to Step 21.

  19. On the DDL Commit Frequency screen, choose the number of DDL statements between issuing COMMITs and click Next.
  20. On the Output Directory screen, indicate the output directory.

    Accept the default value, DBSRVR_ROOT\DB2390\DBOUTPUT\INSTALL, or enter your new value.

    This is the directory that contains schema.sql, ddlview.sql, and the new files to apply DDL on the mainframe.

  21. On the Log Output Directory screen, indicate the directory where you want the log files to be generated.

    Accept the default value, install_mf, or enter your new value.

  22. On the runnow message box, choose from one of the following options:
    • To apply the configuration now, press OK.
    • To apply the configuration later, press Cancel.

      The command line command to apply the configuration later is
      C:\sea7x\siebsrvr\bin\siebupg.exe /m master_install_mf.ucf

      NOTE:  This command is generated dynamically and can vary based on the location of your Siebel Server installation.

  23. On the Configuration Parameter Review screen, review the configuration values you entered on the previous Configuration Utility screens:
    • To go back and make changes, click Previous to back out until you reach the screen with the parameter you need to change.
    • To accept the values you input with no changes, click Finish.

      This step completes the installation option to Run DDL Automatically.

      If a program or system error occurs and you need to rerun the Siebel Upgrade Wizard, you can do so, starting from the command line at the point at which the wizard failed, by navigating to \siebsrvr\bin and entering:

    siebupg.exe /m master_install_mf.ucf

  24. The resulting message box states that the configuration was applied successfully.

    To continue click OK.

  25. Transfer schema.sql and ddlview.sql to OS/390 and have your DBA apply them to create the Siebel Schema.

    For information on how the DBA applies the DDL on the DB2 host, see Applying DDL on the DB2 Host.

  26. If you performed a manual install, validate that all tables and indexes are present in the logical schema. For information, refer to the information in Preparing the Database Layout.

When you have successfully completed the step of populating the seed data, you are ready to import the Siebel Repository.

TIP:   To preserve a record of the values you entered, locate and print the file named master_install_mf.ucf in the binary subdirectory of your Siebel Server installation directory.

The following files are generated by the installation into the default output directory (DBSRVR_ROOT\DB2390\DBOUTPUT\INSTALL) or into the output directory that you designated in Step 20:

  • instftp.bat. Use this batch file to run the Siebel-provided scripts, your own FTP, or a similar file transfer program to transport the DDL (schema.sql and ddlview.sql) to DB2.
  • instftp.txt. Use this file to transfer files to the mainframe.
  • jobinstl.txt. Contains JCL and REXX execs to execute the DDL.
Implementing Siebel eBusiness Applications on DB2 UDB for z/OS and OS/390