Configuring Siebel Business Applications > Configuring a Siebel Application > Using Development Tools >

Setting Up the Development Environment

This task is a step in Roadmap for Configuring a Siebel Application.

This topic describes some of the tasks that you can perform to set up a development environment. For more information, see Using Siebel Tools.

Setting Up the Configuration File for Siebel Tools

This topic describes how to set up the configuration file for Siebel Tools. For more information, see Using Siebel Tools.

To set up the configuration file for Siebel Tools

1. Open the tools.cfg file in a text editor.
2. Set the EnableToolsConstrain parameter to FALSE.

   For more information, see How the EnableToolsConstrain Parameter Affects Text Strings.

3. Make sure the ClientConfigurationMode parameter is not All.

   You cannot use the Form Applet Wizard, List Applet Wizard, View Wizard, or set the HTML Sequence if the ClientConfigurationMode parameter is All.

4. Save the tools.cfg file.
5. If Siebel Tools is open, then exit out of it, and then open it.

How the EnableToolsConstrain Parameter Affects Text Strings

Table 33 describes how the EnableToolsConstrain parameter affects text strings. For more information, see Using Siebel Tools.

You can use one of the following configurations to create a custom text string:

• Use a symbolic string to create a translatable text string.
• Enter a value in a string override field. For an example, see Validating Data That the User Enters in a Business Component Field.
• Add an HTML tag that modifies a text string. For more information, see Modifying the Text Style of a Control or List Column in an Applet.

Displaying Object Types You Use to Configure Siebel CRM

You can display object types in the Object Explorer that you use to configure Siebel CRM.

To display object types you use to configure Siebel CRM

1. Open Siebel Tools.
2. Click the View menu, and then click Options.
3. Click the Object Explorer tab.
4. Scroll down through the Object Explorer Hierarchy window until you locate the Entity Relationship Diagram tree.
5. Make sure the Entity Relationship Diagram tree and all child objects of the Entity Relationship Diagram tree include a check mark.

   If all child objects in the Entity Relationship Diagram tree are displayed, then Siebel Tools displays a black check mark with a white background for the tree.

6. Repeat Step 4 for the following object types:
   • Task Group and all children of the Task Group object type.
   • View and all children of the View object type.
   • Import Object and all children of the Import Object type.
   • Control User Prop and List Column User Prop, which are children the Applet object type.
   • Business Component User Prop, which is a child of the Business Component object type.
   • Class object type.
   • Other object types, as necessary.
7. Click OK.

Setting Up a Developer as a Remote User

After you install Siebel Tools, the Siebel Server, and any other software in the development environment, you must set up each developer as a remote user. This configuration allows you to store a copy of the Siebel database, including the Siebel repository, on the local computer that the developer uses. The developer can check out objects from the Siebel Server repository, configure and test their work on their local computer, and then check objects back into the Siebel Server.

For more information about:

• Installing software, see Siebel Installation Guide for the operating system you are using.
• Check in and check out, see Using Siebel Tools.
• Setting up a remote user, see Siebel Remote and Replication Manager Administration Guide.

To set up a developer as a remote user

1. Install Siebel Tools on the computer that the developer uses. Install Siebel Tools in a directory that is separate from the Siebel client.

   For example, if you install the Siebel client in c:\siebel\clnt, then install Siebel Tools in c:\siebel\tools. This configuration does the following:

   • Makes sure that the development environment and the Siebel client environment are distinct.
   • Makes sure that if you use Siebel Remote in these environments, that the two installations do not conflict.

     For more information, see Siebel Installation Guide for the operating system you are using.

2. Verify that each developer possesses a valid user name and password for the Siebel development database server.

   In most situations, Siebel CRM uses the employee login ID and password for the database server user name and password.

3. Using a Siebel client connected to the development server database, create an Employee record and a Mobile User record for each developer.

   Use the first and last name of the developer for the employee first and last names. For the login ID, use a consistent naming format, such as first initial and last name. This format simplifies identifying who locked a project.

   Password encryption interferes with project check in and check out. If you check projects in and out, then you must disable password encryption in the client or the configuration file if you run Siebel Tools.

4. Grant each developer the Developer and Siebel administrator responsibilities.

   To prevent unintended modifications to important system preferences, you can create a responsibility that contains access to all views except the System, Service, and Marketing Administration views. You can use a common position for all developers. For testing purposes, you can set up an organization structure that models the structure of your business.

   If you do not grant the user the Developer responsibility, then Siebel Tools does not activate drilldowns in the Tools client.

   For more information on setting up an employee, see Siebel Applications Administration Guide. For more information on setting up a responsibility, see Siebel Security Guide.

5. On the Siebel Server, use the Database Extract server component to extract the local database for each developer.

   Database Extract creates a template for the local database that includes only business data, not repository data. The Database Extract server component extracts Enterprise data into this template, together with any data that possesses limited visibility, such as contacts, accounts, opportunities, and so on. For more information, see Siebel Remote and Replication Manager Administration Guide.

6. To initialize the Mobile Client Database for the developer, open Siebel Tools and connect to the local database.

   Siebel CRM displays a message that states the local database is not found.

7. To start the initialization process, click Yes.
8. In the Siebel Remote Parameters dialog box, enter the Siebel developer logon you defined in Step 3 and an appropriate password.

   The initialization program creates the sse_data.dbf local database file in the LOCAL subdirectory of your Siebel Tools installation. For example, c:\siebel\tools.

9. Do an initial get operation for all projects on each local database.

   For more information, see Using Siebel Tools.