Bookshelf v8.0: Best Practices for Configuring and Maintaining Your Rules Development Environment

Table 2 provides best practices to follow when you configure and maintain your rules development environment.

Table 2. Best Practices for Configuring and Maintaining Your Rules Development Environment
Guideline	Explanation
Do not use a knowledge base to update more than one runtime database.	Your edited or added relations may not be consistent with the Siebel object model.
Do not delete a knowledge base.	Deleting a knowledge base deletes the knowledge base tables in the runtime database to which the knowledge base points.
Run only one knowledge base against a runtime database. That is, do not create a new knowledge base against a runtime database to which another knowledge base points.	When you import objects for the new knowledge base, the runtime data created for the original knowledge base is deleted, making the original knowledge base useless.
Backup runtime tables nightly using an SQL tool.	This is an extra precaution to protect against data corruption.
Never modify or delete any HaleyAuthority concepts, relations, or phrasing manually, especially objects created by the Object Importer.	A knowledge base is not supported if imported Siebel objects' concepts, relations, or phrasing are modified or deleted. See About Technical Support for Rules.