| Bookshelf Home | Contents | Index | Search | PDF | |
Configuration Guidelines > Setting Up Developers >
Using Local Databases
Although Siebel Tools lets developers operate in a client/server mode with the development database server, developers should never make configuration changes directly in the server database, for the following reasons:
- When working directly in the server database, you cannot undo or back out undesired changes to a specific project. The only option is to recover the entire repository.
- Your changes are immediately available to other developers when they check out projects or compile an SRF in the database server. If you have not completed work on the project, these incomplete changes can cause problems for other developers.
To prevent these problems and promote efficient team-based development, each developer should be configured as a mobile user, with a local SQL Anywhere or MS SQL database. Initially, each developer should populate the local database with a read-only copy of all projects on the server. When developers need to modify a specific project, they can check out that project from the server database. This locks the project on the server database to prevent other developers from making changes to it, and transfers a modifiable copy of the project to the local database. The developer can then modify and unit-test the project against the local database. After the work is complete, the developer can check the project back into the server database. If a developer wants to discard the local configuration work, the developer can revert the local database copy of the project to the server version, which is kept as an archive file each time a project is checked out.
| Bookshelf Home | Contents | Index | Search | PDF | |
Configuration Guidelines Published: 18 April 2003 |