Installing the Siebel Database schema and seed data

If we observe the configuration process for the Siebel Gateway Name Server and the Siebel Enterprise correctly, we find that the Siebel Gateway Name Server authenticates each connection attempt using the account management of the RDBMS that hosts the Siebel Database. This is the default setting. Other authentication techniques such as LDAP or Microsoft Active Directory are also supported.

The only unauthenticated Gateway Name Server session is the first connection that we used to register a new Enterprise with the Siebel Gateway Name Server. Any other connection attempt, such as when we want to register the first Siebel Server, needs to be authenticated.

However, the Siebel Database, which is the default medium for authentication, has not yet been configured. So, the next logical step is to engage the Siebel Configuration Wizard and install the Siebel Database schema.

The Siebel Database configuration process differs from the previous processes in the sense that we first have to prepare and run an SQL script (in a file named grantusr.sql) against the database and that the configuration wizard invokes the Siebel Upgrade Wizard, which itself invokes other utilities and programs to run specific commands against the database.

So, before we launch the Siebel Configuration Wizard, we will discuss both the grantusr.sql script and the Siebel Upgrade Wizard.