This guide is intended for software developers and system administrators who are using OpenBase on MacOS X, Windows and Linux. Each of these sections describe ways of connecting to OpenBase.
The Hypertext Transfer Protocol (HTTP) is the most ubiquitous of the Internet protocols. Although seen primarily as a means to fetch pages of Hypertext Markup Language (HTML) content for display in a web browser, HTTP is really a general-purpose transport for any type of data. The OpenBase.cgi process makes use of HTTP to communicate with clients requesting data using XML or JSON.
The REALbasic Connectivity Module for OpenBase allows clients written in REALbasic to connect with OpenBase databases. Since the connectivity module is written in 100% REALbasic, applications that use the module are instantly compatible with other platforms. This section will help you get started with the connectivity module.
In addition to accessing database data, the RealBasic Module for OpenBase provides administration classes for creating and controlling OpenBase databases. This section provides an overview of the administrative classes.
Reading/Writing Java Objects From/To OpenBase
• Object Relational Mapping (ORM)
• Cayenne Architecture
• Cayenne In Practice
• Code Examples
OpenBase comes with a standard JDBC driver which will work for most applications. For examples on how to use JDBC we recommend visiting the sun.com website. We also have the following instructional video from our developers conference:
The PHP archive contains the files necessary to add OpenBase support to PHP. The module source has been recently modified in January 2009 to support MacOS X leopard, 64 bit architechtures and OpenBase.
The OpenBase DAMs provide connectivity between Omnis Studio 3.2 (or later) or Omnis 126.96.36.199 (or later) and OpenBase SQL. This section describes the requirements, installation procedures, and basic usage of the OpenBase DAMs.
WebObjects is a powerful rapid application development environment for building powerful web sites and web services. Built on a three-tier architechure, WebObjects allows you to insulate applications from your database architecture by mapping attributes in a data model. Database access is accomplished by a component called Enterprise Objects Framework (EOF) which maps database records to Java objects using the data model.
These instructions allow access to up-to-date DBI functionality through the extremely well supported JDBC driver for OpenBase. This set of instructions shows you how to connect to an OpenBase server using the OpenBase JDBC Drivers on MacOS X.
Many common desktop applications allow you to directly access data in your database by using ODBC technology. Whether you want to create a report using FileMakerPro, perform numerical analysis using Microsoft Excel pivot tables, or create client/server applications using Microsoft Access, ODBC drivers let you include data from your database in your documents.
The Espresso API offers a superset of the OpenBase API to insulate developers from having to always construct SQL. The Espresso API layer takes care of all the SQL, record locking, data encoding and all database access. It is an abstraction layer. At the same time, the Espresso API does not prevent you from writing your own SQL.
The Espresso API offers a superset of objects which can be combined with the OpenBase API to offer a higher level of access which insulates program logic from SQL. The Espresso API layer takes care of all the SQL, record locking, data encoding and all database access. It is an abstraction layer. At the same time, the Espresso API does not prevent you from writing your own SQL.
This section focuses on the low-level OpenBase Objective-C interface through the OpenBase object. The OpenBase object provides the basis for all communication to OpenBase databases and is complementary to the Espresso interface which is built on top of it.
OpenBase offers a C and Objective-C API for communicating with databases and retrieving results. This section describes the API calls that are common to both versions of the communications APIs.