Reference | Help | Introduction | Slide Show | Class Hierarchy | InterClient
PREV | NEXT | FRAMES | NO FRAMES |  |

### Gateways and Database URL Syntax

InterServer as a Gateway

You may setup a single InterServer to act as a gateway to any number of remote InterBase servers across heterogenous architectures. The database URL to pass through an InterServer gateway named `pongo` would be:

    jdbc:interbase://pongo/interbase-remote-database-file-specification

Where `interbase-remote-database-file-specification` follows the syntax dictated by InterBase for remote database access. For example, for InterBase server `perdy`, a database URL to the example employee database on `perdy` might be:

    jdbc:interbase://pongo/perdy:/InterBase/examples/employee.gdb

Here, an InterServer gateway is installed on `pongo`, and an InterBase server is installed on `perdy`.

The InterServer host must have the InterBase client software installed. This includes `gds32.dll` for Windows, `libgds.so` for Solaris, etc.... TCP/IP services will be configured automatically on port 3050 for an InterBase install, and port 3060 for an InterServer install.

URL Syntax

A database URL is used by a JDBC driver to establish a connection to a database. The general form of an InterBase database URL is

    jdbc:interbase://interserverHostName:interserverPort/databaseFileSpecification

By default, the InterServer service listens on port 3060. So normally, the :interserverPort is not given and the form of the database URL is

    jdbc:interbase://interserverHostName/databaseFileSpecification

On Unix file systems, the databaseFileSpecification starts from a root "/", so a typical database URL on a Unix host may be

    jdbc:interbase://pongo//databases/employee.gdb

On Windows file systems, the databaseFileSpecification may start with a driver letter, such as "d:", or it may start from a root "/" using the default drive. So a typical database URL on a Windows host may be

    jdbc:interbase://pongo/c:/databases/employee.gdb

InterServer has the ability to reside on a middle tier and proxy service to a remote InterBase server. In this case, the databaseFileSpecification must be recognizable as a remote database by the InterBase client library. So, if InterServer resides on host "pongo", and the InterBase server resides on host "perdy", then a typical database URL may be

    jdbc:interbase://pongo/perdy:/databases/employee.gdb

Or more generally

    jdbc:interbase://interserverHostName/interbaseHostName:databaseFile

for a TCP/IP connection from InterServer to InterBase. Refer to the InterBase documentation for more information about valid databaseFileSpecifications for remote servers.

Reference | Help | Introduction | Slide Show | Class Hierarchy | InterClient
PREV | NEXT | FRAMES | NO FRAMES |  |

Send comments or suggestions to interclient@interbase.com