| Prev | Next | Start of Chapter | End of Chapter | Contents | Glossary | Index | Comments | (2 out of 14)

A KB contains knowledge in the form of items and, in some cases, additional real-time data. The items in a KB represent a set of application knowledge. Chapter 10, G2 Items describes the purposes and features of items.

A running G2 process provides an interactive environment that a developer uses to work with knowledge bases. Chapter 2, The Developer's Environment describes the features provided by the G2 developer's environment.

You use G2 to work with a KB as follows:

• A running G2 process reserves part of its memory to contain one KB, called the current KB. A G2 process always works with one and only one current KB.

• You can direct G2 to save the KB into one or more files called KB files.

You use the G2 developer's environment to operate a KB. To operate a KB means to start, pause, resume, reset, and restart the KB. You can operate your KB programmatically, for example, within rules and procedures.

You work with the current KB and with KB files in these ways:

• You can load a previously saved KB file, so that it replaces the contents of the current KB.

• You can merge the contents of a saved KB file into the current KB.

• You can clear the current KB by removing all application knowledge from it.

• You can save the current KB to a KB file that G2 stores on a storage device.

• You can capture the current KB, along with all its run-time information, to a snapshot file.

• You can warmboot a KB from a KB snapshot file to run a captured KB as if resumed at the time its snapshot file was written.

Finally, each KB includes a set of system tables. These tables store preferences that affect how G2 uses the KB's application knowledge when the KB is loaded.

| Prev | Next | Start of Chapter | End of Chapter | Contents | Glossary | Index | Comments | (2 out of 14)