Finalizing the Siebel Server installation - Siebel - CRM

We have successfully logged on to the Siebel Call Center application as the Siebel Administrator (SADMIN), which is the only valid user account at the time of installation.To finalize the Siebel Enterprise installation and configuration, some small but important tasks are yet to be completed.These tasks include:

  • Setting the system service owner account
  • Copying the Siebel File System seed files
  • Creating an administrative Siebel user
  • Applying additional license keys
  • Synchronizing Server Components

The process flow of finishing the Siebel CRM server software configuration is as follows:


Siebel CRM server software configuration

We will discuss these tasks in the following section.

Setting the System Service owner account

The Siebel Configuration Wizard has created the Siebel Gateway Name Server and Siebel Server system services.These services have the Windows Local System account assigned.In the process of preparing the system for installation of Siebel CRM software, we have created a distinct user account that we now have to assign to the Windows service.

In order to do so, we open the Windows Services console and double-click on the Siebel Gateway Name Server service to open its properties dialog box.In the Log On tab of the properties dialog, we assign the system owner account that we created earlier.The following screenshot shows the local siebsvc account being assigned to the Siebel Gateway Name Server service.Note that the local domain is addressed using a dot.


Setting the System Service owner account

We repeat this procedure for the Siebel Server service. Assigning separate user accounts to the services ensures that we have more control over the user rights assignment for the services and the processes they start. For example, the service account that we assigned to the Siebel Server must have full access to the Siebel File System.

Copying the Siebel File System Seed files

During the installation of the Siebel Database Server Utilities,we chose the feature Sample Database support,which caused the creation of a FILES subdirectory in the installation folder of the Siebel Database Server Utilities (dbsrvr).In order to finalize the Siebel Database installation, we navigate to this directory, select all files that have a .SAF (Siebel Attachment File) or .kb (knowledge base—used for the Smart Answer module) suffix, and copy them to the ATT subdirectory of the Siebel File System using the copy utility of our choice.

In order to verify the correct placement of the attachment files, we log on to the Siebel Web Client as SADMIN and click the Sitemap (globe) icon to access the Sitemap.There we click the Administration - Document link and then click the Correspondence Templates link to navigate to the Correspondence Templates list view.

In the list of correspondence templates (all imported as seed data during the Siebel database installation), we click the hyperlink for the first template. We should see a dialog box allowing us to choose to open or save the document or cancel the operation. When we click Open,the document will be downloaded from the Siebel File System and opened in the associated application.

We must accept the fact that not all seed documents have an associated seed attachment file,but the procedure described above should work for most of the sample correspondence templates and proves that we copied the seed attachment files correctly.

Creating administrative Siebel user accounts

Logging on as the Siebel Administrator (SADMIN) should only be done to verify the installation and to undertake special activities as directed by the Oracle documentation.General administrative tasks should be carried out using our own account, which allows easier tracking and troubleshooting of our activities.In order to create a new administrative user, we use the Siebel application (where we are logged in as SADMIN) and navigate to the Administration - User screen using the Sitemap.

In the Employees list view, we use the Query functionality to find the employee with a User ID of "SADMIN" and use the Copy Record command (Right-click and select Copy Record or press CTRL+B) to copy the SADMIN employee record.In the new record, we modify the First Name, Last Name, and User ID fields to reflect our own account.

The following screenshot shows a new example employee account for Alexander Hansal with the User ID AHANSAL created as a copy of SADMIN.


new example employee account for Alexander Hansal with the User

Copying the Siebel Administrator employee ensures that we have the same user rights assigned and can therefore carry out the same administrative tasks. Before the new user is able to log on, we must register the user ID and password (note that we did not enter a password in the Siebel Client) with the authentication system.As we selected the default authentication via the RDBMS account management in which the Siebel database is located, we have to create a user account in the RDBMS.

We will accomplish this by simply copying the set of commands to create a user account from the grantusr.sql file that we used during the Siebel database installation.It is highly recommended to create files and store them in a central location rather than typing the commands directly into the system console.Storing the scripts we used to alter the system configuration allows for easier tracking of changes, troubleshooting, and reuse of the scripts in other environments.

The following code can be imagined as part of a .sql input file used to create the AHANSAL user account in an Oracle database.

The script creates a user account whose name matches exactly (case is important) the user ID of the new Siebel employee.The user will have the password TZ7yxc99 and has the role and tablespace assignment of a typical Siebel user.Note that this method of creating user accounts in the RDBMS is suitable for small evaluation or development environments. For production environments with thousands of users, companies normally decide to use LDAP or Microsoft Active Directory as the authentication system. User accounts typically already exist in those directories.Setting up authentication via directory services will be discussed in a later.

We can now log off the user SADMIN (by pressing CTRL+SHIFT+X) and log in using our new administrative account. We should use that account rather than SADMIN from now on.

The Siebel Web Client supports keyboard shortcuts.As we strive for professional and efficient use of the tools provided, we should acquaint ourselves with the most important keyboard shortcuts.A list of keyboard shortcuts can be easily found in the Siebel online help, which can be opened using CTRL+H.Click the Contents hyperlink and then click Getting Started: Using Keyboard Shortcuts.

Applying additional license keys

Even if we are prompted for a license key during the Siebel database installation, a typical Siebel CRM license key contains more than a single line of digits. In order to provide access to all licensed functionality, the administrator must enter the additional license keys.

This can be accomplished using the Siebel Web Client that we used to verify the successful installation and to create new administrative users. Another possibility to manage license keys exists within the Siebel Tools development environment, which we have not yet installed. So, the following section shows how to enter additional license keys using the Siebel Web Client.

Using our own administrative account, we log on to the Siebel application and navigate to the Administration - Application screen (using the Sitemap) and then to the License Keys view.

In the list, we can use the New button to create new records and copy and paste each line from our license key file into the Key Value field.This is repeated for each line in the license key file.The following screenshot shows the License Key view in the Administration - Application screen with additional license key strings entered.

Note that the license key values in the following screenshot do not represent real license keys:


Applying additional license keys

Synchronizing server components

Before the Siebel Server can be used to execute components in batch mode, which is also known as "running jobs", the administrator has to synchronize the batch component definitions from the Siebel Gateway Name Server to the Siebel database. One reason for this is that dropdown lists are used when defining jobs via the graphical user interface (GUI) and these dropdown lists are populated from database tables rather than through a (slower) connection to the Gateway Name Server. Server administration tasks such as running jobs will be discussed in a later chapter in detail.

In the Siebel Web Client, we synchronize the server components by navigating to the site map, the Administration - Server Configuration screen, and then the Synchronize view. In the empty list, click the Synchronize button.The component synchronization takes approximately 20 seconds and we can verify successful synchronization by monitoring the automatic refresh of the components list.

The following screenshot shows the Synchronize view after successful synchronization of the server component information from the Siebel Gateway Name server to the Siebel database:


Synchronize view after successful synchronization of the server component

In order to finalize your Siebel demonstration environment, follow the directions in this section to:

  • Set the system service owner account
  • Copy the Siebel File System seed files
  • Create an administrative Siebel user for yourself
  • Apply additional license keys
  • Synchronize server components

All rights reserved © 2020 Wisdom IT Services India Pvt. Ltd Protection Status

Siebel - CRM Topics