  Step
8 - Application Development
Omnidex provides easy to use interfaces to several different development
tools and third party applications.
Omnidex ODBC Driver
Omnidex provides an ODBC driver that can interface with most applications
and development tools that support ODBC as well as an ODBC Call Level
Interface (CLI) that can be used for custom ODBC applications.
ODBC Drivers are generally used for:
Generalized On-Line transactions (OLTP) reporting and inquiry.
- Application Development.
- On-Line Analytical Processing (OLAP)/ Data Warehousing reporting and
inquiry.
- Development tools such as Cold Fusion, Microsoft Access, ADO, Visual
Basic, Visual C++, and Powerbuilder can access and update a database
via the Omnidex ODBC driver.
ODBC retrieval applications can quickly and easily access an Omnidex
enhanced database. Some of the retrieval tools tested with the Omnidex
ODBC driver include Microsoft's Access, Excel, Word and Query, Brio's
Brio Query, MicroStrategy tools, Cognos' Impromptu and Powerplay, Business
Objects, and Crystal Reports.
Omnidex JDBC Driver
The Omnidex JDBC Driver can be used for Java applications including JSP,
servlets, applets and standard console applications and is available for
all supported platforms.
See JDBC in the Development
section for more information and a sample
minimum retrieval application.
OmniAccess Application Programming Interface (OAAPI)
The OmniAccess
API is available for server-only and client-server applications.
The OmniAccess API lets programs access data quickly and efficiently
through the Omnidex indexes. Its various routines support keyword searches
and very fast joined retrievals, as well as Boolean, range, comparison
and wildcard searches.
All of the supported SQL language is available for use in the OmniAccess
API via the oaexecsql routine.
The OmniAccess routines are callable from most programming languages.
Each routine uses parameters (buffers created for a specific purpose)
to pass information to the OmniAccess routine, or to return information
to the calling application. With the exception of oaerror, the return
parameter for information about the success of any OmniAccess routine
is status.error (the first field in the status structure). oaerror uses
the address of the message buffer as its return parameter.
OmniAccess programs typically include connecting to a database or environment
catalog, opening one or more search cursors, multiple keyword searches
via the Omnidex indexes, returning the qualifying rows to the program,
updating rows, and closing the cursor(s) and environment.
For single-tiered UNIX, NT and MPEiX applications, Omnidex provides a
callable API that can be accessed from traditional languages such as C
and COBOL. The quickest way to create a simple, singled-tiered test application
against an Omnidex enhanced data base is to use the C language against
the Omnidex Access API (OmniAccess). Use the LDOA command file to properly
link the Omnidex Access API library to the C program.
For multi-tiered Client/Server environments, Omnidex provides a network
aware version of the Omnidex Access API to facilitate access from programming
languages such as C++, Visual Basic, Delphi, Powerbuilder and COBOL.
There are two choices in development with the API:
The first is to use the low-level API calls oaqualify, oajoin, oaselect,
and oafetch to qualify and join tables manually.
The second option is to use the oaexecsql api call in conjunction with
oafetch to process SQL select statement.
Generally, applications should be written using the oaexecsql api and
should only use the lower-level api's if the Omnidex SQL engine does not
handle the particular application need.
Top
|
