Configuring Enhydra to use InterBase

InterBase™ is an efficient and powerful RDBMS engine. Its vendor Inprise Corp. has announced a policy to release the upcoming version of InterBase as an open source product. See www.interbase.com for more information and product downloads.

Understanding the InterClient, InterServer, InterBase relationship

With most databases, the JDBC™ driver talks directly with the database server. In the case of Interbase, the JDBC driver talks to an intermediary server that talks to the database server. The InterBase JDBC driver is called InterClient™. The InterClient system includes an all-Java thin client, and a server-side daemon (also known as a service on Windows™ NT) called InterServer. This daemon accepts JDBC connection requests and in turn connects to the InterBase RDBMS daemon. Each of the three processes (JDBC client, InterServer daemon, InterBase daemon) can run on separate hosts, or they can all run on the same host, or any other combination. InterClient is a class 3 JDBC driver in that it has a separate daemon on the server to serve JDBC connections, but it also matches the definition of a class 4 driver in that the client component can connect only to one DBMS back-end, InterBase.

InterClient is installed separately from InterBase. On Windows, it is commonly installed in the JAR file C:\Program Files\Borland\InterClient\interclient.jar. Depending on the version of InterClient, it might instead be in C:\Program Files\InterBase Corp\InterClient\interclient.jar.

Find the jar file and append its location to your system CLASSPATH environment variable on the client host where you run Java applications. Different versions of InterClient are available. Version 1.50x works only with JDK 1.1x. InterClient Version 1.51x works only with JDK 1.2.x. Whichever version of InterClient you use, you must use the matching version of InterServer.

Enhydra Configuration

Below is an example of the database configuration settings for connecting an Enhydra application to InterBase. Add the following settings to the configuration file <appName>.conf where appName is the name of your application. To use this example, change values shown in bold.
#--------------------------------------------------------------------
#                   Database Manager Configuration
#--------------------------------------------------------------------
DatabaseManager.Databases[] = "database_id"
DatabaseManager.DefaultDatabase = " database_id "
DatabaseManager.Debug = "false"
DatabaseManager.DB.database_id.ClassType = "Standard"
DatabaseManager.DB.database_id.JdbcDriver = 
  "interbase.interclient.Driver"
DatabaseManager.DB.database_id.Connection.Url = 
  "jdbc:interbase://loopback/C:/directory/subdirectory/database.gdb"
DatabaseManager.DB.database_id.Connection.User = "sysdba"
DatabaseManager.DB.database_id.Connection.Password = "masterkey"
DatabaseManager.DB.database_id.Connection.MaxPoolSize = 30
DatabaseManager.DB.database_id.Connection.AllocationTimeout = 10000
DatabaseManager.DB.database_id.Connection.Logging = false
DatabaseManager.DB.database_id.ObjectId.CacheSize = 20
DatabaseManager.DB.database_id.ObjectId.MinValue = 1

Configuration notes: