Siebel Business Rules Administration Guide > Configuring the Business Rules Development Environment >

About Rules Development Environment Topology

HaleyAuthority versions statements, so changes can be tracked. However, HaleyAuthority and Siebel plug-ins do not include a check-out/check-in system to keep changes by multiple developers cumulative.

The recommended development model is to maintain one knowledge base for creating and deploying rules to a single runtime database.

• The production knowledge base must only be used to update the production runtime database, and the production database must be updated by one and only one knowledge base.
• A development knowledge base must only be used to update one and only one development runtime database, and the development database must be updated by one and only one knowledge base.
• Individual developers must replicate all changes to the development knowledge base that is tested in the development runtime database before migrating to production.
• Individual developers can use a local knowledge base for prototyping only. As in the production and primary development environments, the local knowledge base must update one and only one runtime database (likely a local database), and the runtime database must be updated by one and only one knowledge base.
  • All development on local knowledge bases must be replicated on the development knowledge base.