Direct Connect
Direct Connect are connections to a remote instance that do not pass through an Ingres GCC server. All data is sent natively and does not go through Ingres Net translation (that is, character set translation, numeric translation, etc.). Performance is improved because data goes directly from the application process on the client machine to the Gateway server process on the server machine. Although traffic does not pass through the Ingres GCC server, a GCC server is required to establish the connection. Direct connects are configured with a vnode just like regular Ingres Net connections.
For direct access to occur, the following conditions must be met:
• The client and server machines must be the same platform type (that is, both Windows, both Solaris, and so on) and the environment variable II_CHARSETxx must be identical on both the client and server machines.
• On any platform which uses the same IPC protocol for local and network connections, the environment variable, II_GC_REMOTE must be set on the Server to 'ON' or 'ENABLE' to allow direct connections. See the section on II_GC_REMOTE for more information.
Note: The default character set setting for Ingres and Enterprise Access varies between releases. Always check the character set on both the client and server machines to ensure the character sets are configured identically. Failure to have the same character set defined will result in the default Ingres Net behavior.
It is suggested that the same version of Ingres Net be used on both the server and client machine.
Windows:
The client and server machines must be logged into the same Windows network domain. 
Last modified date: 08/22/2022