|
|
|
Before you install Net, do the following:
|
|
|
Before you install Ingres Net, the network administrator must make sure the network is properly installed and operating.
|
|
|
To install Ingres Net for Windows with TCP/IP as its network protocol, you must first install the TCP/IP network software for Windows. From the Network applet in the Control Panel, choose Add Software. From the list of choices, choose TCP/IP Protocol and Related Components and follow the installation instructions.
To use symbolic node names (host names) of a remote host instead of its numeric IP address, you must either configure a Domain Name Server in the DNS section of the TCP/IP configuration or add a list of IP addresses and corresponding symbolic names in a file called %windir%\system32\drivers\etc\hosts. For information on the format of this file, see Windows documentation.
|
|
|
To install Ingres Net for Windows with SPX/IPX as its network protocol, you must first install the SPX/IPX network software for Windows.
From the Network applet in the Control Panel, choose Add Software. From the list of choices, choose NWLink IPX/SPX Compatible Transport and follow the installation instructions.
For information on installing the SPX/IPX protocol, see Windows documentation.
|
|
|
To install Ingres Net for UNIX with TCP/IP as its network protocol, you must first configure TCP/IP for UNIX.
To use symbolic node names (host names) of a remote host instead of its numeric IP address, you must either configure TCP/IP to use a Domain Name Server configuration or add a list of IP addresses and corresponding symbolic node names host names) of all remote hosts that are referred to by host name in a file called the /etc/hosts file (or other list of network host addresses).
Establish aliases for node names in the /etc/hosts file. This is useful if the node name contains characters that are not accepted by Ingres Net. For information about how to establish aliases, see UNIX documentation for your machine.
Fully test TCP/IP before installing Ingres Net. You must be able to connect to other nodes on the network using telnet and ftp commands.
|
|
|
To install Ingres Net for VMS with TCP/IP as its network protocol, you must first install TCP/IP Services on VMS. To use symbolic node names (host names) of a remote host instead of its numeric IP address, you must either configure TCP/IP to utilize a Domain Name Server configuration or add a list of IP addresses and corresponding symbolic node names host names) of all remote hosts that are referred to by host name in the TCP$HOST file.
Establish aliases for node names in the TCP$HOST file. This is useful if the node name contains characters that are not accepted by Ingres Net. For information about how to establish aliases, see VMS documentation.
Test TCP/IP fully before installing Ingres Net. You must be able to connect to other nodes on the network using telnet and ftp commands. The connection can be tested with a TCPIP PING command, or use the telnet utility to connect to the node. If the connection succeeds, you are ready to add the nodes to the Ingres installation using netutil.
For more information, see the chapter Establishing Communications and the VMS documentation on TCP/IP services.
Note: TCP/IP Services for OpenVMS, formerly UCX, is often still referred to as UCX.
|
|
|
Installing Ingres Net using DECnet as a network protocol requires no additional procedures in the DECnet installation. Simply install DECnet and test it fully before installing Ingres Net. Be sure that all nodes that use Ingres Net are defined and accessible through DECnet. You must be able to use the set host command to connect to any node on the network that uses Ingres Net. For details, see DECnet-Plus for OpenVMS Installation and Basic Configuration or DECnet-Plus Introduction and User's Guide.
|
|
|
When installing MultiNet TCP/IP on a network that uses Ingres Net, you must make it emulate either Wollongong TCP/IP or TCP/IP Services for OpenVMS. For details on enabling TCP/IP Services emulation (using the MultiNet SET LOAD-UC_DRIVER command) or WIN/TCP emulation (using the SET WINS-COMPATIBILITY command), see the MultiNet for OpenVMS System Administrator's Guide.
Depending on the selected emulation mode, you must follow the guide's instructions for Wollongong TCP/IP or TCP/IP Services for OpenVMS.
|
|
|
When using SunLink SNA Peer-to-Peer (LU 62) as the network protocol, you must set up the appc Gateway configuration files to define the SNA Logical Unit (LU) and Physical Unit (PU) resources associated with Ingres Net connections. For information on setting up this configuration file, see the SunLink SNA Peer-to-Peer Administrator's Guide.
The "SunLink Gateway Configuration Files" appendix contains sample excerpts from configuration files. An experienced SNA communications specialist must perform the configuration.
If using independent LUs, make sure (in SunLink SNA Peer-to-Peer Release 7.x) that you start the cnos_local and cnos_remote processes in addition to starting and configuring the appc Gateway process.
Test SunLink SNA Peer-to-Peer fully before installing Ingres Net. Use the SunLink SNA test_p2p program to perform testing.
Ingres Net does not currently support the Physical Unit Management Services (PUMS) that SunLink SNA provides.
|
|
|
When using HP-UX SNAplus (LU6.2) as the network protocol, you must configure the links, connections, Modes, Remote APPC LUs, Local APPC LUs, and Invocable TPs associated with Ingres Net connections. For information on the configuration procedure, see the HP SNA Products Remote System Configuration Guide, the HP-UX SNAplusLink Administrator's Guide, and the HP-UX SNAplusAPI Administrator's Guide.
For more detailed information on configuration, see the appendix "Netu Procedures" in this guide. An experienced SNA communications specialist must perform the configuration.
You must test HP-UX SNAplus fully before installing Ingres Net. For guidance, see the sample programs in /usr/lib/sna/samples.
If the SNAplus control daemon is restarted, any Communications Servers that are using the protocol must also be restarted.
|
|
|
When using AIX SNA Services/6000 as the network protocol, you must create a set of configuration profiles that describe the hardware and software that are used for communications. For information on defining these profiles, see Using AIX SNA Services/6000 and AIX SNA Services/6000 Reference. An experienced SNA communications specialist must perform the configuration.
Ensure that SNA Services/6000 is fully functional before installing Ingres Net. In particular, make sure that the SNA subsystem and the network attachment that is to be used can be started using the startsrc console command. Using AIX SNA Services/6000 contains details on the use of this command.
The appendix "AIX SNA Services/6000 Configuration Profiles" contains sample excerpts from configuration profiles showing examples of those profiles that must be specifically tailored for Ingres Net. Once these profiles are defined and Ingres Net is installed on both the local and remote machines, use the startsrc command to start up the connection that you have configured. This is not necessary for Ingres Net operations, but it helps to verify that the configuration profiles are correct before attempting to actually run Ingres Net.
|
|
|
The parameters that must be specified when installing and setting up Ingres Net depend on whether it is a server or client installation. They also depend on whether you choose to use an Installation Password to authorize access to a server installation from a remote client installation.
|
|
|
Installation Passwords and their corresponding remote user authorizations can be wholly or partially set up during the Ingres Net installation procedure.
You can set up Installation Passwords and remote user authorizations at any time after the installation procedure using Network Utility, Visual DBA, or netutil. For more information about these procedures, see the chapter "Establishing Communications."
|
|
|
If Ingres Net is part of a server installation, you are asked to supply the following information:
Is an alphanumeric string that can be used to authorize remote users to access the DBMS Server on this installation.
The first eight characters of the string must be unique on the installation.
Default: None
VMS: If you are installing Ingres Net on a VMS system, you are not prompted to define an Installation Password. To define one, use netutil after completing the installation procedure.
|
|
|
If you are installing Ingres Net on a non-NFS client installation, you are asked for the following information.
An installer-defined, two-character code that identifies this installation.
Default: II
Windows and UNIX: The first character must be a letter; the second character can be a letter or numeral. If there is more than one installation on the same node, each installation must have a unique installation code.
VMS: This parameter applies only to group-level installations. System level installations are assigned an internal code of "aa".
Make sure that the first letter of your group-level installation code is not "a" and not in use by another group-level installation in the node.
The region of the world and the time zone in which this client installation is located. You must enter these values even if they are the same as for this client's DBMS Server (host) node.
Default on some systems: NA-PACIFIC.
NFS clients are prompted only for the Installation Password. For detailed information on running Setup for NFS clients, see the Installation Guide.
Note: If you are setting up NFS clients from the server installation, you are not prompted to set up a remote user authorization entry. You must set up your remote user authorization entries using netutil after you have completed the installation procedure. For instructions on setting up a remote user authorization using netutil, see the chapter "Establishing Communications."
|
|
|
When Ingres Net is added to an existing installation, the procedures differ slightly but the fundamentals remain the same. You must rerun the Ingres Setup program to install and configure Ingres Net. The prompts that you must answer remain the same, regardless of whether Ingres Net is being installed as part of an initial installation or as an addition to an existing installation.
|
|
|
A server and client are able to communicate through Ingres Net as soon as the installation procedure is complete if an Installation Password and corresponding remote user authorization entry are set up on that server and client, respectively.
Otherwise, before Ingres Net can be used to connect installations, the necessary remote user authorizations, connection data, and Installation Passwords or Login Account Passwords must be defined.