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 set to All.

   You cannot use the Form Applet Wizard, List Applet Wizard, View Wizard, or set the HTML Sequence if the value of 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 the object types that 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.

NOTE:  For Siebel Innovation Pack 2015, the local database for Siebel Tools can use either SAP SQL Anywhere or Oracle Database XE. 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 My Oracle Support for Innovation Pack 2015 (Doc ID 1996273.1).

Options for the local database for a developer using Siebel Tools are as follows:

• Set up the developer as a remote user for Siebel Tools, with a local database that uses Oracle Database XE. This option requires that you install Siebel Innovation Pack 2015, Patchset 5 or later, and that, during patchset installation for Siebel Tools, you select the option to install a local database using Oracle Database XE. This local database cannot be used with Siebel Web Client. Additional steps are required to set up this local database for use by the developer.
• Set up the developer as a remote user for Siebel Tools, with a local database that uses SAP SQL Anywhere.

For more information about:

• Installing Siebel CRM software (including Siebel Enterprise Server, Siebel Web Server Extension, Siebel Tools, and Siebel Web Client), see Siebel Installation Guide for the operating system you are using. This guide also provides information about installing Oracle Database XE with Siebel Tools, about requirements such as an existing installation of the 32-bit Oracle database client, and about validating the installation of Siebel Tools and Oracle Database XE.
• Installing Siebel Patchset releases, see Siebel Patchset Installation Guide for Siebel CRM, 1614310.1 (Article ID) on My Oracle Support.
• Checking in and checking out projects, see Using Siebel Tools.
• Setting up a remote user for Siebel Mobile Web Client, see Siebel Remote and Replication Manager Administration Guide.

To set up a developer as a remote user of Siebel Tools

1. Install Siebel Tools on the computer that the developer uses.

   You must install Siebel Tools in a directory that is separate from the Siebel client. For example, if you install the Siebel client in c:\siebel\client, 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, then the two installations do not conflict.

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

     NOTE:  If you want to use Oracle Database XE for the local database, then you must also install Siebel Innovation Pack 2015, Patchset 5 or later. During patchset installation for Siebel Tools, you must select the option to install a local database using Oracle Database XE, specify the location of the 32-bit Oracle database client, and provide valid database credentials for creating the local database.

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 Developer Web 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, that will simplify identifying who locked a project.

   NOTE:  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 in the configuration file if you run Siebel Tools. For more information about password encryption, see Siebel Security Guide.

   For more information on creating an employee record, see Siebel Security Guide.

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 Siebel Tools client.

   For more information on setting up an employee, see Siebel Applications Administration Guide. For more information on setting up responsibilities and positions, see Siebel Security Guide.

5. To initialize a new local database for this developer, perform the applicable steps in the remainder of this procedure. Different steps apply if you are using Oracle Database XE or SAP SQL Anywhere for the local database:
   • For a local database using Oracle Database XE, go to Step 6.
   • For a local database using SAP SQL Anywhere, go to Step 7.
6. (Oracle Database XE only) Run the local database setup script, using a command similar to the following.

   This command reads custom schema and data from the enterprise database and applies it to the existing local database that was created when you installed Oracle Database XE with Siebel Tools.

   SIEBEL_TOOLS_ROOT\bin\LocalDbSetup.exe -s $SiebelTools -o "$ODBCDataSource" -t $TableOwner -u $username -p $password -r "Siebel Repository" -d $ODBCDataSource_XE -x "$OracleXEInstallationPath" -l $logfilename -w $debugmode -y "Runtime Tables"

   where:

   • $SiebelTools is the path of the Siebel Tools installation.
   • $ODBCDataSource is the ODBC entry of the enterprise database.
   • $TableOwner is the tableowner of the enterprise database.
   • $username is a user name for the enterprise database.
   • $password is the password for this user name.
   • $ODBCDataSource_XE is the ODBC entry for Oracle Database XE (should be LOCAL_XE).
   • $OracleXEInstallationPath is the Oracle Database XE Installation path, such as SIEBEL_TOOLS_ROOT\oraclexe.
   • $logfilename is the name of the log file.
   • $debugmode - defaulted to "N". Set it to "Y" in case of any failure. SQL and data files are not deleted after this script runs, and can be used to analyze the issue in case of any error.
   • $Runtime Tables - defaulted to "N". Set it to "Y" if tables related to Siebel Composer are required in the local database.

     After the script finishes running, you have finished setting up the local database for Oracle Database XE for this developer.

7. (SAP SQL Anywhere only) 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. Before you can run Database Extract, you must have already run the Generate New Database component. For more information, see Siebel Remote and Replication Manager Administration Guide.

8. (SAP SQL Anywhere only) To initialize the Mobile Client Database for the developer, open Siebel Tools and connect to the local database.

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

9. (SAP SQL Anywhere only) To start the initialization process, click Yes.
10. (SAP SQL Anywhere only) In the Siebel Remote Parameters dialog box, enter the Siebel developer login that 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, such as c:\siebel\tools.

11. (SAP SQL Anywhere only) Do an initial get operation for all projects on the local database.

    For more information about this task, see Using Siebel Tools. You have finished setting up the local database for SAP SQL Anywhere for this developer.