Mimer SQL System Management Handbook TOC PREV NEXT INDEX

Mimer Developer Site

www.mimer.com/developer


Accessing a Database Remotely


In order to access a database that resides on another network node, the database must be created as a local database on the node it resides on and a remote database definition must be set up on the node from which the database is to be accessed.

The purpose of the remote database definition is to define a link with a database that resides elsewhere on the network. The name used for the remote database definition must be the same as that given to the local database it represents.

The definition for the remote database contains the communication parameters required for accessing the database over the network.

UNIX: The definition of a remote database under UNIX involves creating an entry in the /etc/sqlhosts file, see The SQLHOSTS File on VMS and Unix for information on the parameters involved.
On the database server computer, the mimer service should be defined in /etc/services and a port dispatcher should be defined in
/etc/inetd.conf.
This is usually done automatically by the dbinstall command as follows:
/etc/services:
mimer 1360/tcp
/etc/inetd.conf:
mimer stream tcp nowait root /usr/bin/mimtcp mimtcp -l
The mimtcp program is started when a connection attempt is made to the mimer service. It establishes a connection to the desired database on the node.
-l specifies that a log file is to be used. If -l is not specified, the default log file will be used. The default log file is:
.mimer_log/mimtcp.log
and is located in root's home directory.
For manual re-initiation of the inetd daemon, use the command
"kill -HUP inetd_pid".

VMS: The definition of a remote database under VMS involves creating an entry in the SQLHOSTS file, see The SQLHOSTS File on VMS and Unix for information on the parameters involved.

Win: The definition of a remote database under Windows is set up by running the Mimer Administrator and specifying the required parameters. On-line Windows help is provided with the Mimer Administrator to guide you through the creation of a remote database.

Client/Server Interface

Once the remote database definition has been set up and provided that the Mimer SQL client/server communications have been established correctly, access to a database that resides on a remote machine is performed transparently.

The Mimer SQL client/server communications interface is integrated into the database server. The database server process manages all connections.

All Mimer SQL applications may use the client/server interface without having to make any special provision in the application code. The client/server interface is automatically activated whenever a remote database is targeted.

The Mimer SQL client/server protocol is identical on all Mimer SQL platforms. This means that a Mimer SQL client on any machine type may access a Mimer SQL server for a remote database on any of the platforms on which Mimer SQL is implemented.



Upright Database Technology AB
Voice: +46 18 780 92 00
Fax: +46 18 780 92 40
dbtechnology@upright.se
Mimer SQL System Management Handbook TOC PREV NEXT INDEX