Developing and Deploying Siebel Business Applications > Setting Up the Development Environment > Process of Setting Up the Development Environment >

Setting Up Local Databases

This task is a step in Process of Setting Up the Development Environment.

The NREC example requires that each developer use a local database. The process to set up a local database includes tasks that an administrator performs and tasks that the developer performs. For example, to generate a local database, an administrator creates the database user and runs Siebel Remote server tasks. To initialize the local database, each developer downloads repository data from the Siebel Server.

For more information about each step in this task, see Siebel Remote and Replication Manager Administration Guide.

NOTE:  To complete the examples in Configuring the User Interface through Configuring Logos, Banners, and Colors instead of setting up and using a local database you can use the Sample database. For more information, see Prototyping with the Sample Database.

NOTE:  For Siebel Innovation Pack 2015, the local database for the Siebel Mobile Web Client uses SAP SQL Anywhere. SAP SQL Anywhere is not available for new deployments after September 2015. For more detailed information on how this change affects Siebel Tools and Siebel Remote, see Siebel Release Notes on Siebel Support for Innovation Pack 2015 (Doc ID 1996273.1).

To set up local databases

1. Log in to the Partner Manager application as an administrator.

   For more information, see Logging In as the Siebel Administrator.

2. Make sure the Partner Manager application is connected to a Siebel server.
3. Register the developer as a new Siebel Mobile Web Client:
   1. Navigate to the Administration - Siebel Remote screen, and then the Mobile Clients view.
   2. In the Mobile Clients list, click New, and then complete fields using values from the following table.

      Field	Description
      Mobile Client	Enter LCHENG. It is recommended that you enter the Mobile Client name in uppercase letters, with a maximum of eight characters. It is recommended that you use the User ID. CAUTION:  The Mobile Client name and the User ID must contain only Roman characters, alphanumeric characters, the underscore (_) or the dash (-). It cannot include spaces, periods, or other special characters. For more information, see the topic about format of the remote client name, database name, login id, and windows password in Siebel Remote and Replication Manager Administration Guide.
      User ID	Choose the LCHENG user ID that is assigned to Li Cheng. The user uses the User ID to log in to the local database during initialization. Siebel Remote uses the User ID to access the local database during initialization and synchronization.
      Routing Model	Choose MOBILE CLIENT - EXTRACT ONLY. Siebel Remote associates each mobile user with one Routing Model. This model includes a set of routing rules that determines if Siebel CRM routes a record to a Siebel Mobile Web Client. For a developer, it is recommended that you use the MOBILE CLIENT - EXTRACT ONLY routing model. It does not allow synchronization. It provides only a snapshot of data, which is appropriate for a developer.
      Language(s)	Do the following: In the Language(s) field, click the select button. In the Languages dialog box, click New. In the Language field, click the select button. In the Pick Language Name dialog box, Choose a language, and then click OK. For example, choose English-American. Click Save, and then click OK. Siebel CRM uses a language preference for the mobile user to download data in a preferred language for the following dock objects. These objects contain translation tables. This technique helps to optimize the size of the local database: LOV Product Literature Catalog Catalog Category If you leave the Language field empty for a Mobile Client, then Siebel CRM routes all language translations for these dock objects to the local database that resides on the Mobile Client. If you specify a language, then you must add English-American - ENU, and then each of the other languages that your deployment requires.

      Although Siebel CRM does not use Siebel Remote to check in and check out projects, you must register each developer as a Siebel Mobile Web Client. This registration provides Siebel Remote the information it requires to create a local database file for the developer and to enter appropriate data in the file.

4. Make sure the Remote Server component group is enabled:
   • If you enabled Siebel Remote when you installed the Siebel Server, then the Siebel Remote component group is enabled.
   • If you did not enable Siebel Remote when you installed the Siebel Server, then you must enable it. For more information, see Enabling the Siebel Remote Component Group.
5. Generate a new database:
   1. Navigate to the Administration - Server Management screen, and then the Jobs view.
   2. In the Jobs list, click New.
   3. In the Component/Job field, choose Generate New Database.
   4. In the Requested Server field, enter the name of the Siebel Server on which to run the GenNewDb job.
   5. In the Job Parameters list, click New.
   6. In the Name field, click the select button, locate the SQL Anywhere Database job parameter, and then click OK.

      The Siebel Server defaults the Value field to sse_utf8.dbf. To use an encrypted template file, replace this value with sse_encr.dbf.

   7. (Optional) To modify the values of other optional parameters, repeat Step e through Step f for the other parameter.

      For more information, see Parameters for the Generate New Database Server Component.

   8. In the Jobs list, click Submit Job.

      The Siebel Server generates a new database file, which typically requires a few minutes.

6. Make sure the Generate New Database task finishes:
   1. Click Tasks.
   2. In the Tasks list, click Query, enter Generate New Database in the Component field, and then click Go.
   3. Make sure the value in the State field is Completed.
   4. If the value in the State field is not Completed, then wait a few minutes, and then repeat Step b.

      If necessary, repeat Step d until the value in the State field is Completed.

7. Extract the local database:
   1. Click Jobs.
   2. In the Jobs list, click New.
   3. In the Component/Job field, choose Database Extract.
   4. In the Job Parameters list, add a new parameter for each row in the following table.

      Parameter	Value
      Client Name	Enter LCHENG. This is the name of the Mobile Client you entered in Step b.
      Encrypt client Db password	Enter False.
      Client Database encryption method	Enter none.

      The Job Parameters list is located below the Jobs list and below the Job Detail form. The encryption parameters allow you to extract a local database without encryption. For more information, see 475398.1 (Article ID) on My Oracle Support.

   5. In the Jobs list, click Start.

      Siebel CRM extracts the database for the Siebel Mobile Web Client. This might take a few minutes

8. Verify that the database extraction created the required files:
   1. On the Siebel Server computer, open Windows Explorer, and then navigate to the following directory:

   siebel\docking\lcheng

   2. Verify that the following items exist in the siebel\docking\lcheng directory:
      • The dobjinst.dbf file
      • Inbox and outbox directories
   3. Open the outbox directory, and then verify that at least one file exists for each of the following file extensions:
      • .uaf
      • .dat
      • .toc

        For more information, see How the Database Extract Server Component Extracts Data.

9. Log out of the Siebel client.

Enabling the Siebel Remote Component Group

You must make sure the Siebel Remote component group is enabled. For more information, see Siebel System Administration Guide.

To enable the Siebel Remote component group

1. Enable the Siebel Remote component group:
   1. Navigate to the Administration - Server Configuration screen, Enterprises, and then the Component Groups view.
   2. In the Component Groups list, click Query, enter Siebel Remote in the Component Group field, and then click Go.
   3. If the value in the Enable state field is not Enabled, then click Enable.
   4. In the Component Group Assignments list, make sure the Enabled on Server option contains a check mark.
   5. If you clicked Enable in Step c, or if you added a check mark in Step d, then log out of the Siebel application, restart the Siebel Server, and then log back in.

      For more information, see Enabling the Siebel Remote Component Group.

2. Make sure the Siebel Remote server components are online:
   1. Navigate to the Administration - Server Management screen, and then the Components view.
   2. In the Components list, click Query, enter Database Extract in the Component field, and then click Go.
   3. Make sure the value in the State field is Online.
   4. If the server component is not online, then use the buttons in the Components list to restart the server component.

      For example, click Startup, or Resume.

   5. Repeat Step b for the Generate New Database server component.
   6. Repeat Step b for the Synchronization Manager server component.
3. Synchronize the server components:
   1. Navigate to Administration - Server Configuration screen, and then the Enterprises view.
   2. Click the Synchronize tab.
   3. In the Synchronize list, click Synchronize.
   4. Wait for Siebel CRM to complete the synchronization.

      This might require a few minutes.

Parameters for the Generate New Database Server Component

Table 8 lists the parameters and default values for the Generate New Database server component.

NOTE:  For Siebel Innovation Pack 2015, the local database for the Siebel Mobile Web Client uses SAP SQL Anywhere. SAP SQL Anywhere is not available for new deployments after September 2015. For more detailed information on how this change affects Siebel Tools and Siebel Remote, see Siebel Release Notes on Siebel Support for Innovation Pack 2015 (Doc ID 1996273.1).

How the Database Extract Server Component Extracts Data

The database extract process retrieves data that is visible to the Remote user from the server database. It retrieves data according to routing rules that define the level of access for the user. It creates compressed files that contain data that Siebel CRM loads in the local database when the user initializes the laptop. Note that, for the database extract to be successful, the mobile user must be associated with a valid position. For more, see Siebel Applications Administration Guide.

Each registered Siebel Mobile Web Client requires a separate directory on the Siebel Remote server. The Database Extract job creates these directories for each Siebel Mobile Web Client. It also places a directory named txnproc in the docking directory in the Siebel server root directory. Do not modify the contents of this directory under any circumstances.

The following example displays a portion of the server directory tree after you run Database Extract for Siebel Mobile Web Clients and developers named LCHENG and SSCOTT.

siebel
   docking
      lcheng
         inbox
         outbox
      sscott
         inbox
         outbox
      txnproc

Running the Database Extract job creates a database snapshot for a given user, which includes multiple files. These files contain the data the Siebel CRM requires to initialize the local database for the user. Siebel CRM places them in the following directory on the development server:

siebsrvr_root\docking\user\outbox

To create a local database and local file system, each mobile user downloads these files.