4. Establishing Communications : How User Access Is Established : Requirements for Accessing Remote Instances
 
Share this page                  
Requirements for Accessing Remote Instances
When the instance includes Ingres Net, users can connect to databases on remote instances as well as those on their local instance. To connect to remote instances, the following requirements must be met:
A virtual node (vnode) name must be defined for each remote instance that is accessed, unless you use the dynamic vnode format (see page Dynamic Vnode Specification—Connect to Remote Node) to connect.
A virtual node (vnode) is a name defined on the local instance that points to the connection data and authorization data necessary to access a particular remote instance. When a user on the local node wants to access a database on a remote instance or run an application that accesses a database on a remote instance, the user must specify the vnode name for the instance in addition to the name of the database.
The vnode name can be the same as the node’s real address or node name. However, because the real names or addresses are often difficult to remember, and because there can be more than one instance on the node, other names are typically chosen for vnode names.
A connection data entry must be defined for each remote instance that is accessed.
A connection data entry contains the information necessary for Ingres Net to locate and connect to an instance on a remote node. A connection data entry is typically associated with a particular, locally defined vnode, but can also be specified dynamically with the dynamic vnode format. It includes the name or address of the node on which the remote instance resides, the listen address of the remote instance, and an Ingres keyword for the network protocol used between the local and remote nodes.
Remote user authorizations (see page Remote User Authorizations) must be defined for each remote instance that is accessed.
A remote user authorization contains the login and password information necessary to gain access to a remote instance. It is typically associated with a particular, locally defined vnode, but can also be specified dynamically with the dynamic vnode format.