This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
admin:basics:overview:updates [2012/01/24 21:20] doc created |
admin:basics:overview:updates [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 7: | Line 7: | ||
| ===== Introduction to Omnidex Fundamentals ===== | ===== Introduction to Omnidex Fundamentals ===== | ||
| - | **[[admin:basics:home | Environments ]]** | | + | [[admin:basics:home | Environments ]] | |
| [[admin:basics:overview:sqlengine | SQL Engine]] | | [[admin:basics:overview:sqlengine | SQL Engine]] | | ||
| - | [[admin:basics:overview:updates | Updates]] | | + | **[[admin:basics:overview:updates | Updates]]** | |
| [[admin:basics:overview:network | Network Services]] | [[admin:basics:overview:network | Network Services]] | ||
| ---- | ---- | ||
| \\ | \\ | ||
| - | The Omnidex indexing technology is built upon four building blocks that provide the foundation of the product. It is valuable to understand these building blocks before learning how to index your data and tune your application. | ||
| - | |||
| - | === Omnidex Environments === | ||
| - | |||
| - | An Omnidex Environment is a term that describes all the aspects an Omnidex database. This includes: | ||
| - | |||
| - | * The Omnidex Environment File, an XML file containing selective metadata about the database and the Omnidex indexing. | ||
| - | * The database, consisting of a relational database, a series of raw datafiles, a series of delimited files, or all three. | ||
| - | * The Omnidex indexes and support files for the database. | ||
| - | |||
| - | Typically, an Omnidex Environment is a directory with subdirectories that contain all of these elements. This is often the most convenient approach since whole directories are easy to move and back up. In many cases, however, the database and indexes are large enough that they must span multiple disk drives or even machines. In that case, the Omnidex Environment refers to the entire collection, even though it is disbursed. | ||
| - | |||
| - | [[admin:basics:environments:home | More >]] | ||
| - | |||
| - | ===== ===== | ||
| - | ---- | ||
| - | **[[admin:basics:overview:sqlengine | Next]] ** | ||
| - | |||
| - | === Omnidex SQL Engine === | ||
| - | |||
| - | The Omnidex product is built around a powerful SQL engine that can process statements and take advantage of the Omnidex indexing technology. This SQL engine can process traditional SQL statements, such as SELECT, INSERT, DELETE and UPDATE, and can also process a wide variety of statements to maintain the database and directly access the Omnidex indexes. The Omnidex SQL Engine is based around Omnidex SQL, a language that is based on ANSI-standard SQL and includes a number of Omnidex-specific extensions. | ||
| - | |||
| - | The Omnidex SQL Engine automatically optimizes statements so that they use the Omnidex indexes as fully as possible. As is true with most relational databases, developers do not need to refer to the indexing strategy in their statements. They simply submit standard SQL statements that reference the tables and columns in the database. This makes it easy to write new applications, and it also means existing applications that call ANSI-standard SQL will quickly receive the benefit of optimization. | ||
| - | |||
| - | [[admin:basics:sqlengine:home | More >]] | ||
| === Omnidex Updates === | === Omnidex Updates === | ||
| Line 48: | Line 23: | ||
| [[admin:basics:updates:home | More >]] | [[admin:basics:updates:home | More >]] | ||
| - | === Network Services === | + | ===== ===== |
| - | + | ---- | |
| - | Omnidex Network Services provide the core communication interface between the components of Omnidex. Based upon the TCP/IP standard, Omnidex Network Services provides the communication services for Omnidex's ODBC and JDBC drivers, as well as the internal communication used in Omnidex Grids. | + | \\ |
| - | + | ||
| - | Omnidex Network Services normally runs as a service in Microsoft Windows, or as a background daemon on Linux. The main process will listen for network requests and spawn additional processes to service each request. It is common to see many Omnidex processes running on an Omnidex server, each one handling a request from a user. Note that Omnidex favors a separate process for each request to help improve control and stability of the application. | + | |
| - | [[admin:basics:network:home | More >]] | + | ** [[admin:basics:overview:sqlengine | Prev]] | [[admin:basics:overview:network | Next]] ** |
| ====== Additional Resources ====== | ====== Additional Resources ====== | ||