SIEBEL CRM

Siebel Local Setup

Author:
 OMS Setup Local DB

26 April 2010

Setting up a mobile user/developer database

Prerequisites

1. Siebel Remote server component must be enabled on the Siebel server.

2. Siebel Mobile Web Client must be installed on the mobile user’s local machines.
3. Both Siebel Developer Client and Siebel Tools must be installed on the developer’s
local machines.
4. A live connection to the server is required during local database initialisation and for
subsequent synchronizations with the server.
5. Oracle Client installed on the local developers machines and OLTP database
connection string added in the tnsnames.ora file under
$ORACLE_HOME\NETWORK\ADMIN folder.
Please refer to the detailed installation steps section for further information on
installing Siebel Web Client, Siebel Tools and Oracle Client.

Steps

1. Setup the Siebel user

This implies to create the user in the Siebel database with SSE_ROLE, if database
authentication is used, and to setup the user as an employee in Siebel under
Administration-User screen > Employees view. Before initiating the extraction the
user’s position and responsibility must be well defined as the position controls the
data and responsibility the screens and views that will be available to the user in the
local database. Also the employee’s status have to be Active for a successful
extraction/synchronization.
Since developers need access to all views for testing purposes the responsibility for
these users is usually set to Siebel Administrator.

2. Registering the user as a Mobile Web Client

This action informs Siebel Remote on the need to extract the local database for this
specific user and is done from Administration – Siebel Remote screen > Mobile
Clients view. Along with user’s position, the extraction routing model, defined on this
screen, determines the data the user will be able to access.
The following are the most used extraction routing models:
- MOBILE CLIENT – EXTRACT ONLY - This model does not allows synchronization, it
is simple a snapshot of data, which is appropriate in the case of a developer.
- MOBILE CLIENT – STANDARD – This model is used to get a full set of data related
to the user, the same set of data that is visible when the user is connected to the
server database using a web client, with some exceptions. It also allows data

2
 OMS Setup Local DB

26 April 2010

synchronization and can be appropriate for both a developer or a mobile

(remote) user.
There are some other predefined routing models like Executive Management, Field
Sales Representative, Field Sales Manager and so on, that restrict the data extaction
based on the job requirements.
To register a mobile Web client
1. Navigate to Administration - Siebel Remote screen> Mobile Clients view.
2. In the Parent Server form, choose the appropriate parent node.
3. In the Mobile Clients list, click New and fill in the required parameters: user login
for Mobile Client/User ID parameters, select a Routing Model.

3. Generate the database template

A database template is a cached representation of Siebel tables and indexes that will
be used to recreate the database for each mobile user/developer. The database
template is created only once and reused for all local database extraction requests,
therefore this step will be omitted for subsequent mobile users/developers
extractions. However if major schema changes are applied on the server database
(such as changes to private dock objects that have influence on how the data routed
to the mobile users) it is recommended to generate a new database template to be
used by both new and existing mobile clients. This step consists in creating a server
task that needs to complete successfully before proceeding further.

To generate a new database template (GenNewDb)

1. Navigate to Site Map > Administration – Server Management screen > Jobs view.
2. In the Jobs list, click New.
3. In the Component/Job field, select Generate New Database.
4. In the Requested Server field, enter the name of the server on which to run the
GenNewDb job.
5. In the Job Parameters list, click New.
6. In the Name field fill in SQL Anywhere Database. The Value field typically defaults
to sse_utf8.dbf and appears automatically. To use an encrypted template file, replace
this value with sse_encr.dbf.
7. Modify the values of optional parameters if necessary. Set the UseDdlFile
parameter to FALSE only when you run the Generate New Database component after
a schema change.
8. In the Jobs list, with the Database Extract record still selected, click Start. This may
take a few minutes.

4. Extracting the local database

The database extract process retrieves data visible to this specific mobile user from
the server database. It retrieves data according to routing rules that define the level
of access to information for each Mobile Web Client. It creates compressed files on
the Siebel server that contain data to be loaded into a local database when a Mobile
Web Client initializes the database. If a mobile user’s position or routing model
changes we need to reextract the mobile user’s database in order to delete the

3
 OMS Setup Local DB

26 April 2010

records that should no longer be visible to the user based on the user’s new position.
Additionally this improves extraction performance. This step consists in creating a
server task that needs to complete successfully before proceeding further.

To run a database extract for a Mobile Web Client

1. Navigate to Site Map > Administration – Server Management screen > Jobs view.
2. In the Jobs list, click New.
3. In the Component/Job field, select Database Extract from the picklist.
4. In the Requested Server field, enter the name of the server on which you want the
Database Extract job to run.
5. Please be careful to also include the following parameters:
§ Client Database encryption method=None
§ Client Name= $USERNAME
§ Encrypt client Db password=False
§ Extract all Repository Tables=True

6. In the Jobs list, with the Database Extract record still selected, click Start. This may
take a few minutes.

5. Initializing the local database

Unlike the tasks defined in the previous steps that are performed by a Siebel
administrator, this is initiated by the mobile users/developers themself when they
login to the local database using one of the following applications installed on their
local machines: Siebel Mobile Client in the case of a mobile (remote) user, Siebel
Developer Client/Siebel Tools in the case of a developer.

To initialize the local database for Siebel Tools

1. Start Siebel Tools, choosing Local in the Connect field.
The following message appears.
“The local Siebel database was not found. Would you like to connect to the Siebel
Remote server to initialize the local database?”
2. Click Yes.
Siebel Tools connects to the Siebel Remote server and initializes the developer’s local
database.

To initialize the local database for Siebel Web Client

1. Start Siebel Web Client, choosing Local in the Connect field.
The following message appears.
“The local Siebel database was not found. Would you like to connect to the Siebel
Remote server to initialize the local database?”
2. Click Yes. Siebel Remote parameters dialog window appears.
3. Fill in Client Name, User Name, Password, Confirm Password.

4
 OMS Setup Local DB

26 April 2010

For the local database you can choose a different password then the one used to
access the Siebel server. For simplicity purposes in the development environment we
have disabled password lockout for failed login attempts and password syntax check.
4. Siebel Web Client connects to the Siebel Remote server and initializes the
developer’s local database.

6. Extract repository data

This is done only by developer users from Siebel Tools in order to get a full repository
containing a read-only copy of the projects and object definitions stored on the
server database. After performing this action the local repository will have the same
contents as the server repository.

To perform the initial full extract of the repository data

1. Start Siebel Tools, choosing Local in the Connect field.
2. Choose Tools > Check Out. The Check Out dialog box appears.
3. Choose the name of your development repository from the Repository pick list.
4. Click the All projects option button.
5. Click Options. In the Development Tools Options window, make sure that your
Server Data Source points to the server development database and your Client Data
Source points to the local database previously initialized. These data sources must
match those shown in the Control Panel, under ODBC Data Sources.
6. In the Check Out dialog box, click Get to have all objects from the server repository
are copied to the local repository.