The Multi-Dimensional-Keyword (MDK) indexes and the Aggregation-Sorted-Key (ASK) indexes have been merged into a single index which will decrease greatly the time to re-index on Omnidex Environment containing ASK indexes.
The ASK and MDK terminology is no longer being used although Omnidex error messages and the Explain Plans still use the terminology. These will be removed in future releases.
Omnidex no longer has installation options for Client and Server installations. Any Omnidex installation can be used as either a server or a client or both.
Note that Omnidex Client and Omnidex Server versions must have the same major version number (ie 5.1 to 5.1) to communicate to each other.
As of 5.0, Omnidex provided some limited support for connection strings in both ODBC and JDBC to eliminate the need to create File Data Sources or System or User Data Sources. Note that connection strings were further enhanced in 5.1 and changed slightly in 5.2.
In OdxSQL, the following would work:
os> odxsql -odbc odxsql> connect [localhost:7555]c:\odx\myenv.env
In Omnidex 5.0, DISC introduced a new XML format for maintaining Omnidex metadata information that also included Omnidex index specifications. However, the Omnidex Data Definition Language (DDL) syntax was not fully completed in the 5.0 release. Customers on 5.0 should continue to maintain their Omnidex Environments using a text editor and dbinstal index and build scripts. As of Omnidex 5.1, customers can use OdxSQL and the Omnidex DDL statements that create Omnidex Enviroments containing both metadata information and Omnidex index information.
For Omnidex 5.0 customers that want to take a looks at the new 5.0 XML file layout, use OACOMP to translate a Legacy Environment Source into an Environment XML file.
os> oacomp myenv.src myenv.xml
DISC recommends that all existing Omnidex Environments be maintained using an editor and compiled with OACOMP should continue to do so under Omnidex 5.0.
NsAdmin is no longer supported as of the 5.0 release. The NsAdmin functionality has been moved to a new monitoring environment that is available through the Omnidex SQL interface so it is easy to access via OdxSQL.
This functionality is not available in versions 5.0 and 5.1 but will be available in Omnidex version 5.2.
Customers that rely on NsAdmin to monitor existing Omnidex production environments may want to want until the Omnidex 5.2 release is available.
DsEdit is no longer supported as of Omnidex version 5.0 as part of DISC's effort to make the Microsoft Windows and Unix/Linux versions more consistent. However all of the features provided by DsEdit are available in other ways as follows:
| DsEdit Current Feature | 5.x Approach |
|---|---|
| Create ODBC File data sources | copy from documentation and edit with editor |
| Create ODBC System and User data sources | use Control Panel, Data Source Adminstrator |
| Create JDBC data sources | use connection strings and test with OdxSql -JDBC option |
| Test connections | use OdxSQL with -odbc and -jdbc option to test connections |
| Perform simple test queries | use OdxSql with -odbc and -jdbc option to test queries |
DISC is developing a Windows based front end to administer Omnidex in a multi-server environment. However, due to other customer driven priorities, the Omnidex Administrator is not available in either 5.0 or 5.1.
OdxAdmin will incorporate the NsAdmin and DsEdit functionality once it is released.
And any references in the documentation to OdxAdmin should be ignored at this time.
The Oracle and SQLServer Stored Procedure interface is not currently being moved to the current documentation as DISC undergoes a planned refresh of the Store Procedure Interface.
Contact support@disc.com if you need documentation on the Stored Procedure Interface.
cmd> odbcreg -i "program files\omnidex 5.1\bin"
cmd> odbcreg -i "program files\omnidex 4.4\bin"