Using a Local Communications Server for Remote Connections
By default, remote connections are established directly between the application and the remote Communications Server (without needing a local Communications Server nor, in some cases, a local Name Server). There is no need to configure Ingres Net or run ingstart on the client. This feature is especially useful in environments where hundreds or thousands of Ingres clients are installed because it simplifies the management of the client installation and improves performance.
Note: Such connections do not apply to JDBC and .NET applications, which connect directly to the Data Access Server. In some cases, however, client-side servers are required.
A client instance requires a local Name Server in the following cases:
• When specifying a static (predefined) vnode rather than a dynamic vnode.
Note: Installation passwords can only be specified in a static vnode and therefore require a local Name Server.
• When specifying the connection_type attribute with a value other than "default," such as: connection_type=direct.
• When another server, such as the Communications Server, is running in the installation.
A client instance requires a local Communications Server in the following cases:
• When using an encrypted connection in which a new process is started that uses the same connection. This applies to the character-based tools that execute other tools. For example, when using the Tables utility to query tables (calls QBF), or when ABF calls the Report-Writer.
• When using a protocol that is supported only through the Communications Server.
VMS: Using the DECnet protocol requires running a Name Server and Communications Server in the client instance.
If a Communications Server is required for a connection, a Name Server is also required.
If a connection requires a local Communications Server, you must enable its use.
To enable the use of a local Communications Server for remote connections
For an individual connection:
Set the connection attribute connection_type to comsvr. The connection attribute can be defined as part of a vnode or in the connection string:
vnode;connection_type=comsvr::dbname
For the installation:
Set the environment variable II_GCA_REMOTE to FALSE or OFF.
Last modified date: 08/28/2024