This shows you the differences between two versions of the page.
|
dev:home [2009/12/07 02:58] tdo |
dev:home [2016/06/28 22:38] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | {{page>:top_add&nofooter&noeditbtn}} | ||
| - | <html><div align="center"><span style="color:red">DRAFT</span></div></html> | ||
| - | ====== Omnidex Development ====== | ||
| - | ===== Main Development Components ===== | ||
| - | Omnidex Development uses the following main components of the Omnidex Software. | ||
| - | |||
| - | * [[ programs:odxadmin:home | Omnidex Administrator ]] | ||
| - | * [[ programs:odxsql:home | OdxSQL ]] | ||
| - | * [[ programs:odxnet:home | OdxNet ]] | ||
| - | * [[ programs:odxaim:home | OdxAim ]] | ||
| - | * [[ dev:odbc:home | Omnidex ODBC Driver ]] | ||
| - | * [[ dev:jdbc:home | Omnidex JDBC Driver ]] | ||
| - | * [[ dev:dbprocs:home | RDBMS Stored Procedure Interface ]] | ||
| - | |||
| - | ===== Java Snapshot Application Steps ===== | ||
| - | * Install Omnidex on Snapshot data store. | ||
| - | * Set up OdxNet Network Services. | ||
| - | * Use OdxSQL to test set up, prototype and optimize queries. | ||
| - | * Write Java Application. | ||
| - | |||
| - | ===== Windows Snapshot Applications ===== | ||
| - | * Install Omnidex on Snapshot data store. | ||
| - | * Set up OdxNet Network Services. | ||
| - | * Use OdxSQL to test set up, prototype and optimize queries. | ||
| - | * Write Java Application. | ||
| - | ===== RDBMS Integration ===== | ||
| - | |||
| - | * Install Omnidex on RDBMS. | ||
| - | * Use OdxSQL to test set up, prototype and optimize queries. | ||
| - | * Write Stored Procedures using the RDBMS Stored Procedure Interface. | ||
| - | * Run OdxAIM to generate Automatic Update Triggers. | ||
| - | * Install Triggers. | ||
| - | * Run OdxAim to monitor and process the triggered updates. | ||
| - | |||
| - | Omnidex Development primarily takes the form of developing either an ODBC or JDBC based application or using either SQL Server or Oracle Stored Procedures. | ||
| - | |||
| - | Applications have also been previously developed using the OmniAccess API (OA) and Client OmniAccess (CLOA) api. DISC recommends that all future Omnidex development use ODBC, JDBC or the Stored Procedure Interface. | ||
| - | |||
| - | * [[dev:odbc:home | ODBC ]] | ||
| - | * [[dev:jdbc:home | JDBC ]] | ||
| - | * [[dev:dbprocs:home | RDBMS Stored Procedure Interface ]] | ||
| - | |||
| - | Applications using Omnidex have been developed using: | ||
| - | |||
| - | * C | ||
| - | * C++ [[dev:odbc:examples:simpleselect | Windows C++ Simple Connection and Select ]] | ||
| - | * C# [[dev:odbc:examples:csharp_simple_select | Windows C# Connection and Select ]] | ||
| - | * Visual Basic | ||
| - | * PHP [[dev:odbc:examples:php_select | PHP Simple Connection and Select ]] | ||
| - | * Java | ||
| - | * Cold Fusion | ||
| - | * Microsoft Access | ||
| - | * Microsoft Excel | ||
| - | * MicroStrategy | ||
| - | * Oracle Business Intelligence | ||
| - | * SAP Business Objects | ||
| - | * Activant Speedware 4th GL | ||
| - | | ||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | {{page>:bottom_add&nofooter&noeditbtn}} | ||