Bookshelf Home | Contents | Index | Search | PDF

Implementing Siebel eBusiness Applications on DB2 UDB for OS/390 and z/OS > 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

Launch the Database Server Configuration Utility using any method described in the Siebel Server Installation Guide for Microsoft Windows.

The Gateway Server Address screen appears.

Enter the values for the Gateway Server Address and Enterprise Server name as you recorded them in your copy of Deployment Planning Worksheet.
Gateway Server Address. The alias of the host on which you installed the Siebel Gateway.
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 Server Address and Enterprise Server Name fields blank.

In 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, D:\sea7xx\siebsrvr.)
Use the browse button to select an alternate directory path.

To continue, click Next.

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.

In the Database Platform screen, select the database platform you use, in this case, DB2 UDB for OS/390 and z/OS.

To continue, click Next.

In the Siebel Database Operation screen, select Install Database.

To continue, click Next.

In 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.

In the ODBC Data Source Name screen, 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.

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 datasource within DB2 Connect.

NOTE:  There can only be one database server in a Siebel Enterprise Server.

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

To continue, click Next.

In 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.

In the Siebel Schema Qualifier screen, 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.

In the Security Group ID screen, 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.

To continue, click Next.

In 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.
Custom Install. The custom installation option allows you to install the database using your customized storage layout. 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.

In 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 FTP or a similar file transfer program to transport the DDL (schema.sql and ddlview.sql) to DB2, where the DBA executes it, using customary methods, for example, SPUFI or DSNTEP2.

To continue, click Next and proceed to Step 14.

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 16.

In the DDL Output Directory screen, select the directory in which you want to store the generated DDL.
Accept the default directory or use the Browse button, if needed, to locate and map to the directory you have already created for this purpose. The default directory is in the format:

DBSRVR_ROOT \db2390\dboutput\install

If the directory does not already exist, a message box appears, prompting you that a directory does not exist, click OK. You must now create one.
In the Encoding Scheme 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.
In the Siebel Schema Layout screen, select one of the following layout options.
Multiple Tables per Table Space. Choose this option if you want to allow multiple tables within a segmented table space.
One Table per Table Space. Choose this option if you want only one table per segmented table space.
Multiple Tables per Table Space with Partitioning. This layout includes a set of tables that is recommended for partitioning. The remaining nonpartitioned tables are arranged in groups within segmented table spaces. For more information on this template, see About Configuring Siebel Templates for Partitioning.
One Table per Table Space with Partitioning. Choose this option if you want a single table per segmented table space. This layout includes a set of tables that is recommended for partitioning. For more information on this template, see About Configuring Siebel Templates for Partitioning.

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

To continue, click Next.

In 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.

In the 4-KB Buffer Pool Name screen, indicate the values for the following parameters.
4-KB 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.
16-KB 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.

To continue, click Next.

In the 32-KB Buffer Pool Name screen, indicate the values for the following parameters.
32-KB 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.

In the Database Name Prefix screen, type the prefix for your database name. The default is SIEBDB.

This prefix consists of up to six of the first characters in the names of your 18-22 logical Siebel Databases. This prefix must start with a letter and cannot contain any special characters. All database names end in numbers except for TM, which is used as a temporary database during an upgrade.

To continue, click Next.

In the Log Output Directory screen, indicate the directory where you want the log files to be generated.
In 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.

The following message appears:

To apply the configuration now, press "OK".
To apply the configuration later, press "Cancel".
The command line to apply the configuration later is C:\sea704\siebsrvr\bin\siebupg \m master_install_mf.ucf

NOTE:  The last line in the prompt is generated dynamically and can vary based on the location of your Siebel Server installation.

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 \m master_install_mf.ucf

Click OK.

When the Database Server Configuration Utility displays the items it will execute or import, click OK to start generating DDL.

This step completes the installation option Run DDL Automatically.

If in Step 13 you chose the installation option Generate DDL Into Files, the utility displays the following message after it generates the schema.sql file that contains the DDL to create the Siebel Schema:

Please create Siebel Schema using schema.sql and ddlview.sql located in the DDL Output Directory. Once the views are created, please select Yes. To stop now and continue installation later please select No. (To resume at a later time, please start the Upgrade Wizard from the command line using option /m master_install_mf.ucf).

Indicate the following:
To discontinue Siebel Schema (schema.sql) and view (ddlview.sql) generation, click No.

When you click No, the Database Server Configuration Utility quits. To resume operation of the Upgrade Wizard from the command line, go to siebsrvr\bin and enter siebupg /m master_install_mf.ucf.

To continue, click Yes.

When you click Yes, the utility generates schema.sql and ddlview.sql, which contains the DDL for views. Proceed to Step 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.

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 Validating Siebel Schema Creation.
Indicate which action you want to take:
Only if your DBA has already created the Siebel Schema, click Yes to apply DML (insert statements) to populate it. (The execution of the DML does not require DBA authority.)

CAUTION:  When you click Yes, it means you proceed to populate the schema with seed data and perform other manipulations on Siebel tables. The operation will fail if the Siebel Schema has not yet been created, because there is no schema to populate.

If you want to quit the DB Server Configuration Utility to give your DBA an opportunity to create the Siebel Schema, click No. You can relaunch the wizard at any time to continue this step by submitting the following command from the siebsrvr\bin subdirectory:

siebupg /m master_install_mf.ucf

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 14.

schema.sql. Contains DDL for all Siebel DB2 objects. You will transfer this file to the mainframe.
ddlsplit.txt. Contains a REXX routine that can be used to split the DDL into more manageable pieces. This file must be moved to a PDS with RECFM=80 and a LRECL of 80. You will transfer this file to the mainframe.
ddlview.sql. Contains DDL for all Siebel views. You will transfer this file to the mainframe.
instddl.txt. You will transfer this file to the mainframe. Contains sample JCL to execute the DDL using DSNTEP2. This file must be moved to a PDS with RECFM=80 and a LRECL of 80. You will transfer this file to the mainframe.
instftp.txt. Use this file to transfer files to the mainframe.
schmvld.sql. Schema validation file
seedvld.sql. Seed validation file containing update statements that gather actual row counts for seed tables.

Bookshelf Home | Contents | Index | Search | PDF