This section describes the concept and the structure of the server for the Natural SQL Gateway.
This server is necessary if the Natural SQL Gateway runs within a TP environment. For additional information, see Product Structure in the section Introduction to Natural SQL Gateway.
A Natural SQL Gateway server is a multi-user, multi-tasking application.
The server is responsible for maintaining the persistent connection to the JDBC
server for each client, because a client running in a TP environment cannot
cope with persistent JDBC connections. The client opens a so called SQL session
at the Natural SQL Gateway server. This is done implicitly with the SQL
CONNECT statement. This session represents the client from the
JDBC server point of view and keeps the persistent connection. The client is
loosely coupled to this session just by maintaining a session identifier. The
session remains until the client disconnects with the SQL
DISCONNECT statement.
The Natural SQL Gateway server can host SQL sessions for multiple users and execute their requests concurrently.
To enable the administrator to monitor the status of the Natural SQL Gateway server, a monitor task is provided which is initialized automatically at server startup. Using the monitor commands, the administrator is able to control the server activities, cancel particular user sessions, terminate the entire server, etc. For further information, see Monitoring the Natural SQL Gateway Server in the section Operating the SQL Gateway Server.
