Bookshelf Home | Contents | Index | Search | PDF | ![]() ![]() ![]() ![]() |
Siebel Tools Reference > Siebel Tools Installation > Postinstallation Tasks >
Setting Up the Development Environment
This section:
- Explains how to set up and work in the Siebel Tools development environment
- Describes how to establish the development environment
- Lists the names of important directories
- Explains how to set up developers as mobile users
For an example of setting up the developer environment, see Developing and Deploying Siebel eBusiness Applications.
Creating the Development Environment
As a developer, you need to know which repository is being used for the test environment, for the system test environment, and for the production environment. Operating effectively with multiple environments requires the ability to work with local databases, and a familiarity with checking projects into and out of repositories.
First, create a complete development environment that includes both a Siebel Database Server and a Siebel Server. These can reside on the same physical machine. This environment should be completely separate from your production environment—no development work should be performed in the production environment.
Create a separate test environment into which your configuration can be migrated for system testing prior to installation in the production environment. As with the development environment, the test environment should include both a Siebel Database Server and a Siebel Server.
The development database will store the working copies of all repositories being configured by all developers. Configuration work should take place only on the development database. After you have finished configuring a repository, you will use the Siebel repimexp utility to transfer that repository to the test (and, later, production) environment. For information about this utility, see Backing Up and Restoring Repositories in Repositories.
Setting Up Developers as Mobile Users
Because all developers need Siebel Tools and a local repository, they should install the Siebel Mobile Client on their computers.
For more information on setting up local databases, see Siebel Remote and Replication Manager Administration Guide.
To set up developers as mobile users
- Install Siebel Tools on all developers' PCs, in a directory separate from the standard Siebel applications.
For example, if you have installed your Siebel applications in C:\siebel, install the development tools in C:\siebdev. This ensures that the development and run-time environments are distinct. You may be using Siebel Remote in both environments, so you need to make sure that the two installations do not conflict.
- Verify that each developer has a valid user name and password for the Siebel development database server.
In most cases, their employee logins and passwords will also be their database server user names and passwords.
- Using a Siebel application client connected to the development server database, create an Employee record and a Mobile User record for each developer.
Use the developer's first and last names for the employee first and last names. Use a standard naming convention, such as first initial and last name, for the logon name. This makes it easy to identify who has locked a project.
NOTE: Password encryption interferes with project check-in and checkout. You must disable password encryption in the client or configuration file when running Siebel Tools if you will be checking projects in and out.
- Grant each developer a position and a responsibility.
Grant each developer the Developer and Siebel administrator responsibilities. You may also create a responsibility with access to all views except the System, Service, and Marketing Administration views to prevent unintended changes to important system preferences. 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.
NOTE: If you do not grant the user the Developer responsibility, drilldowns will not be activated in the Tools client.
- On the Siebel Server, generate a database template.
- On the Siebel server, extract each developer's local database using the Database Extract component.
Database Extract creates a template for the developer's local database that is populated only with business data, not repository data. All enterprise-visible data is extracted into this template, together with any limited-visibility data (contacts, accounts, opportunities, and so on) to which this user has access.
- Initialize the Developer's Mobile Client Database.
Begin by double-clicking the Siebel Tools icon and connect to the local database.
- Enter the Siebel developer logon created in Step 3 and an appropriate password.
The initialization program creates the sse_data.dbf
local database in the \local directory of your Siebel Tools installation, for example c:\siebdev.
- Do an initial get of all projects on each local database, as described in Getting Projects.
- Check Out selected projects you want to work on, as described in Checking Out Projects.
Bookshelf Home | Contents | Index | Search | PDF | ![]() ![]() ![]() ![]() |
Siebel Tools Reference, Version 7.5, Rev. A Published: 18 April 2003 |