Configuration Guidelines > Setting Up Developers > Using Local Databases >

Preparing Local Development Environments

When setting up developers to work in a local environment, complete these steps, in this order:

  1. Install Siebel Tools in the desired folder on developer machines. By default, this is the C:\siebdev directory.
  2. Install the Siebel eBusiness application in the appropriate folder on developer machines. By default, this is the C:\Siebel directory.
  3. Set up each developer as an employee and mobile client. Using a Siebel eBusiness Applications client connected to the development server database, create an Employee and a Mobile User record for each developer. Use the developer's first and last names for the employee first and last names and a standardized short name, such as first initial plus last name, for the login name. This makes it easy to identify who has locked a project.
  4. Grant each developer a position and responsibility. You can grant the Siebel Administrator responsibility to all developers; alternatively, you may want to create a responsibility with access to all views except System, Service, and Marketing Administration to prevent unintended changes to important system preferences and data. You can use a common position for all developers, but for testing purposes you should also set up an organization structure that models the business.
  5. Schedule a Generate New Database Component Request to create an extract for the user. This process creates a template for the developer's local database that is populated with business data only, not with repository data. All enterprise visible data is extracted into this template, together with any limited visibility data (such as Contacts, Accounts, or Opportunities) to which this user has access.
  6. Connect to Siebel Tools locally to initialize the developer's mobile client database. Specify the Siebel developer login created in Step 3 with an appropriate password. The initialization program creates the local database (sse_data.dbf) in the C:\SIEBDEV\LOCAL directory.
  7. Do an initial checkout (get) of all projects, which retrieves all projects but does not lock them. Developers can then individually check in or check out their projects.
  8. Use the Check In and Check Out commands to copy projects between the local database and the server. When you check out a project, a copy remains on the server but the project is now locked on the server. Other developers cannot make changes to projects that are locked on the server.

When you check in a project, it is copied from your local database to the server database, and it replaces the existing definition of the project on the server. To check in a project, you must have it locked on the server database (that is, you must have first checked it out).

NOTE:  When you check in or check out, the project on the target database is overwritten with the new project.

 Configuration Guidelines 
 Published: 18 April 2003