This action might not be possible to undo. Are you sure you want to continue?
Siebel Admin Tutorials
Fill in the “Gateway Name Server Address” (by default the host name where Gateway Server is installed) and “Enterprise Server Name” (configured during Enterprise installation and configuration).
Hit the Next button to continue.
Enter the full path of the directory where Siebel Server is installed and hit on the Next button to continue.
Enter the full path where DBSRVR is installed and hit on the Next button to continue.
Select the appropriate database and hit on Next button to continue.
Select “Install Database” from the available list and hit on Next button to continue.
Ensure grantusr.sql has been run on the DB instance before going to the next step. Prior running the sql ensure the following configurations are set in the database. 1. Create a DB with tablespace “SIEBEL” and configure a DBF for the same with auto extend setting. 2. Create a connection to the database on the host machine where installation is being done as per the following guidelines: a. Oracle: Either, create a Service entry manually in tnsnames.ora or use the “Net Manager” or “Net Config” utility to configure the connection. b. DB2: Create an entry in the DB catalog for the DB2 connection, either via command line or the DB2 client. c. MSSQL: There is no need for any such connection. 3. Create a new connection in the odbc setting using the following steps: a. Navigate to Start Run. Type odbcad32 and hit enter. b. Navigate to “System DSN” tab. c. Create a new entry using the “Add” button. Select the appropriate driver to create a configuration. For oracle, use the Siebel provided driver. (Ensure not the use the Oracle driver). d. Fill in the appropriate details and test the connection. For server and client installation, Siebel creates DSN’s. Configure the same and test the connection. 4. Navigate to <DBSrvr_Root>/<DB_Type> and pick the grantusr.sql file and run the same on the database using the appropriate tool. Select “Grantusr.sql has been run” option and click on Next button to continue.
Select “Install Siebel Database” option and hit on Next button to continue.
Select either UNICODE or NON-UNICODE option as per the DB settings and hit on Next button to continue.
Siebel fills in the default DSN created during installation. In this case for the server, siebel8_DSN was created by Siebel during installation and the same is populated here. For Oracle database, give the “Service Name” as per tnsnames.ora and hit on Next button to continue. Note: The DSN created by the Siebel installer follows the naming convention: <Enterprise_Server_Name>_DSN. Prior to Siebel 8, the naming convention used to be <Enterprise_Server_Name>_<Siebel_Server_Name>.
Fill in the Siebel database user created by the grantusr.sql and hit on Next button to continue.
Fill in the table owner details as per the grantusr.sql (run previously). Hit on Next button to continue.
Fill in the table space name for Index as well as the tables. In the example shown, a table space name called “Siebel” was created in the database and the same is used here. Note: As per Siebel recommendation, we need to have 2 tablespaces (one for transactional data and the other for indexes) each of 5GB with auto-extend options.
These options are applicable only for Oracle 10G database. These options are configured at the database level and the same should be used here in the configuration. FYI: The implications of the above configurations are explained briefly: Parallel Indexing Option: This option is recommended for an implementation where there would be a large number of users connecting to the database server. In this mode the resources would be shared across users on the database. If the above option is not selected and instead, Dedicated Server mode is selected, resources on the database server won’t shared between users and each user will be assigned a set of resources through out the active session. This option is recommended when there is a limited number of user connections to the database. Based on the above settings / configurations on the database, select the appropriate option and hit on Next button to continue.
The Security Group ID would be the role created during grantusr.sql execution. Log Output Directory would store the log files for this set of operations. By default Siebel fills in “install” as the directory name. However a user can change it to any other value. The above directory is available at the following location: <SiebSrvr_Root>/log (Prior to SiebSrvr bounce / restart) <SiebSrvr_Root>/LOGARCHIVE/Archive_n (After SiebSrvr bounce / restart).
Select “Yes apply configuration changes now” option and hit on Next button to continue.
Review the configuration details and if correct hit on the Next button to continue. Otherwise hit on the “Back” button the make necessary changes and proceed.
Hit on the “Yes” button to start applying the configuration changes. This action will launch the remote utility as shown below.
Hit on “OK” button to start making the changes. The steps listed above in the window are executed in sequence by the DB installer and requires no action from the user unless errors occur. Below shown are some of the screenshots of the processes in sequence.
Hit on the “OK” button to close the install wizard window.
Hit on “OK” button to dismiss the “Information” window.
Siebel Admin Tutorials