Where Ingres Net Information Is Stored

Ingres Net configuration values are stored in either of the following:

config.dat file
Stores Ingres Net configuration parameters, which can be changed using Configuration-By-Forms or Configuration Manager.
Name Server database
Stores remote access information, which can be entered using the netutil utility.

config.dat—Store Net Configuration Values

The following Ingres Net configuration parameters, stored in config.dat, can be viewed and changed using the Configuration Manager (vcbf) or Configuration-By-Forms (cbf) utility. The default values are assigned during installation.

Note: The Net Server is the Communications Server.

Parameter	Default	vcbf page	cbf screen
inbound_limit outbound_limit	64 inbound sessions 64 outbound sessions	Parameters Page, Net Server Component	Configure Net Server Definition screen
log_level	Level 4	Parameters Page, Net Server Component	Configure Net Server Definition screen
Protocol	Any protocol present at installation is indicated as active	Protocols Page, Net Server Component	Configure Net Server Protocols screen
Listen Address	A GCC listen address is assigned for any protocol present at installation. (The format depends on the protocol.)	Protocols Page, Net Server Component	Configure Net Server Protocols screen
default_server_ class	INGRES	Parameters Page, Name Server Component	Configure Name Server screen
remote_vnode	No default value	Parameters Page, Name Server Component	Configure Name Server screen
local_vnode	Name of host machine	Parameters Page, Name Server Component	Configure Name Server screen

Name Server Database—Store Remote Access Information

Ingres maintains an internal database called the Name Server database, which is used by the Name Server (iigcn). The Name Server database contains the information required for remote access, such as remote node names, listen addresses, login accounts and passwords, virtual node names, and local and remote Installation Passwords. This information can be entered in the Name Server database using the netutil utility.

In a client/server configuration, this database contains one file called iiname.all and one or more "nodename" files for each client node and for the local node. For example:

iiname.all

IIINGRES_nodename1

IICOMSVR_nodename1

IISTAR_nodename1

IINODE_nodename1

IILOGIN_nodename1

IIIUSVR_nodename1

IIDB2UDB_nodename1

IIORACLE_nodename1

IIRDB_nodename1

IIRMS_nodename1

IILTICKET_nodename1

IIRTICKET_nodename1

IIINGRES_nodename2

IICOMSVR_nodename2

IISTAR_nodename2

IINODE_nodename2

IILOGIN_nodename2

IIIUSVR_nodename2

IIDB2UDB_nodename2

IIORACLE_nodename2

IIRDB_nodename2

IIRMS_nodename2

IILTICKET_nodename2

IIRTICKET_nodename2

A unique set of files is created for each node registered as an Ingres Net client.

In the cluster environment, the Name Server database has only one file of each type. For example:

iiname.all

INGRES

COMSVR

STAR

NODE

IUSVR

DB2 UDB

ORACLE

RDB

RMS

LTICKET

RTICKET

All the nodes in an Ingres Cluster Solution instance share the same files.

The files in the Name Server Database are as follows:

iiname.all
Contains a list of all of the types of servers that the instance is expected to manage. The possibilities are DBMS servers, Communications servers, and Star servers.
IIINGRES_nodename
Contains the GCA listen addresses of all the DBMS servers registered with the Name Server (iigcn) on the specified node.

The file is written when the DBMS Server starts and is cached when the node's (identified by nodename) Name Server starts.
IICOMSVR_nodename
Contains the GCA listen address of the Communications Server (iigcc) on the specified node (identified by nodename). The file is written when the local Communications Server starts and is cached when the local Name Server starts.
IISTAR_nodename
Contains the GCA listen address of the Star Server on the specified node (identified by nodename). The file is written when the Star Server starts and is cached when the nodename's Name Server starts.
IINODE_nodename
Contains the connection data entries established for the specified node (identified by nodename) by running netutil, Network Utility (ingnet) or Visual DBA from that node. The file is written whenever you select the "create" option to add a connection data entry for an existing vnode. The file is cached when the nodename's Name Server starts.
IILOGIN_nodename
Contains the remote user authorizations set up at the specified node (identified by nodename) by running netutil, Network Utility (ingnet) or Visual DBA from that node. The file is written whenever you add a remote user authorization. It is cached when the nodename's Name Server starts.