This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
admin:basics:environments:types [2011/01/13 16:21] els |
admin:basics:environments:types [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ~~NOTOC~~ | ||
| + | |||
| {{page>:top_add&nofooter&noeditbtn}} | {{page>:top_add&nofooter&noeditbtn}} | ||
| - | ====== Administration: Omnidex Basics ====== | + | ====== Administration: Omnidex Fundamentals ====== |
| ===== Omnidex Environments ===== | ===== Omnidex Environments ===== | ||
| [[admin:basics:environments:home|Overview]] | | [[admin:basics:environments:home|Overview]] | | ||
| - | **[[admin:basics:environments:types|Types of Environments]]** | | + | **[[admin:basics:environments:types|Types]]** | |
| [[admin:basics:environments:create|Creating]] | | [[admin:basics:environments:create|Creating]] | | ||
| [[admin:basics:environments:maintain|Maintaining]] | | [[admin:basics:environments:maintain|Maintaining]] | | ||
| Line 24: | Line 26: | ||
| Omnidex Environments can be comprised of multiple databases. These databases can be of different types as well. For example, an environment can contain a database pointing to Oracle tables, and also contain a database pointing to raw data files or delimited files. All databases can have Omnidex indexes, and queries against this environment can reference tables from both databases. This capability is of great benefit to those who have transient log files or transaction files that they want to query in conjunction with a primary relational database. | Omnidex Environments can be comprised of multiple databases. These databases can be of different types as well. For example, an environment can contain a database pointing to Oracle tables, and also contain a database pointing to raw data files or delimited files. All databases can have Omnidex indexes, and queries against this environment can reference tables from both databases. This capability is of great benefit to those who have transient log files or transaction files that they want to query in conjunction with a primary relational database. | ||
| + | |||
| + | For applications that require accessing multiple sources of data, it is also possible to temporarily [[admin:features:attach:home|attach a database or table]] to the current environment. This is useful for incorporating tables with search criteria from customers, or incorporating the results of previous orders. | ||
| === Omnidex Grid Environments === | === Omnidex Grid Environments === | ||
| Line 31: | Line 35: | ||
| === Document Catalog Environment === | === Document Catalog Environment === | ||
| - | Omnidex provide powerful features for performing [[admin:features:text:home|textual searches]], including searches on external textual files. An Omnidex database acts as a catalog of the textual documents and allows the indexing of both the catalog and the documents themselves. | + | Omnidex provide powerful features for performing [[admin:indexing:text:home|textual searches]], including searches on external textual files. An Omnidex database acts as a catalog of the textual documents and allows the indexing of both the catalog and the documents themselves. |
| === The "OMNIDEX" Environment === | === The "OMNIDEX" Environment === | ||
| - | Omnidex provides a special environment that gives access to features within the product itself, such as connection and query logs, synonym tables, error messages and configuration information. This reserved environment is simply called "omnidex", and is universally available in the product. | + | Omnidex provides a special environment that gives access to features within the product itself, such as connection and statement logs, synonym tables, error messages and configuration information. This reserved environment is simply called "omnidex", and is universally available in the product. |
| ===== ===== | ===== ===== | ||