In previous releases of Ingres, the JDBC driver required a user ID and password that was valid in the context of the DBMS platform, even for local connections where the local user ID is sufficient. The JDBC driver also failed to use virtual node (vnode) login information when making remote connections, and was not able to access private vnode definitions.

In Ingres 2006, the JDBC driver no longer requires a user ID and password when the Data Access Server is running on the same platform as the Java client. Instead, for local connections, the local user ID is sufficient to establish the DBMS Server connection.

When the Data Access Server and DBMS Server are on separate platforms, a vnode is required in the target database specification that defines how the connection between the Data Access Server and DBMS Server is to be established. The vnode provides the connection information while the JDBC user ID and password are used to access the remote DBMS Server.

A new driver connection property/URL attribute allows the JDBC application to control the context (Data Access Server (local) or DBMS Server (remote)) in which the user ID is used.

When used in the Data Access Server context, the user ID and password allow access to the private vnode information for the user ID provided, and both the login and connection information from the vnode is used to access the remote DBMS Server.

When used in the DBMS Server context, global vnode definitions are used for (nonsensitive) connection information and the provided user ID and password are used to access the remote DBMS Server.

For more information, see the Connectivity Guide.