The Connectivity Guide describes how to establish and maintain communications between Ingres® installations. The connectivity information presented in this guide for accessing Ingres databases also applies to Enterprise Access and EDBC products and the databases they support.
This guide includes the following information:
This chapter briefly describes networking concepts, Ingres components and tools, and conventions used in this guide.
|
|
Ingres provides a variety of connectivity drivers, data adapters, and dialects, including the following:
For a list of latest solutions and details on each, see the downloads page of the Ingres web site.
|
|
To use this guide effectively, you should be familiar with the following basic networking terms and concepts.
A network is a collection of connected computers, software, and communication links.
A heterogeneous environment is a computing environment that includes a variety of machines, operating systems, software, and protocols.
A homogeneous environment is a computing environment in which all machines are the same, and use the same operating system, software, and protocols.
A protocol is a standard that defines a set of rules for the transference of data between computers. A protocol specifies how the data is represented, how the transfer occurs, and how errors are detected and transmissions are acknowledged.
A node is a computer that is connected to a network. Each network node has a unique address within the network.
The term local refers to the instance or node on which you are working.
The term remote refers to all non-local instances or nodes on the network. For example, assume that your network has three instances, "napoleon," "eugenie," and "josephine," and that you are working on "napoleon." From your perspective, "napoleon" is the local instance and "eugenie" and "josephine" are the remote instances. If a co-worker is working on "josephine," for that person, "josephine" is the local instance and "napoleon" and "eugenie" are remote instances.
JDBC (Java Database Connectivity) is a standardized API (Application Programming Interface) that allows database connectivity. It defines a set of function calls, error codes and data types that can be used to develop database independent applications using Java.
ODBC (Open Database Connectivity) is a standardized API (Application Programming Interface) that allows database connectivity. It defines a set of function calls, error codes and data types that can be used to develop database independent applications using Structured Query Language (SQL).
ODBC permits maximum interoperability—a single application can access many different database management systems. This enables an ODBC developer to develop, compile, and deploy an application without targeting a specific type of data source. Users can add the database drivers that link the application to the database management systems of their choice.
|
|
To use this guide effectively, you should be familiar with the basic components of Ingres, client/server concepts, and the Ingres tools required to configure, maintain, and view data.
The basic components of Ingres are as follows:
The Ingres database management system is the server that process requests from clients. The Ingres tools and database applications are the clients.
The following figure illustrates the relationships among Ingres components and tools:
The Ingres tools used to configure, maintain, and view data include the following (commands to invoke these tools are shown in parentheses):
For a description of each tool, see the System Administrator Guide.
The application development tools used to write customized applications include:
For instructions on using these tools, see the Forms-based Application Development Tools User Guide.
|
|
An Ingres instance consists of a set of installed products that share a unique system-file location, ownership, and installation code, together with any data files created by these products. An instance is classified as either a server installation or a client installation.
|
|
An Ingres server installation consists of a DBMS server process (iidbms), a Name Server process (iigcn), a set of Ingres tools, and the files and logs necessary to run the DBMS Server. For a detailed description of DBMS servers, see the System Administrator Guide.
If the server installation allows remote clients to access its DBMS servers, the server installation also includes the Ingres Net Communications Server process (iigcc).
|
|
An Ingres client installation contains a Name server process (iigcn), a Communications server process (iigcc), a DAS process (iigcd), the API components that support client applications (Ingres JDBC Driver, ODBC Driver and .NET Data Provider) and the Ingres tools. A client installation does not run a DBMS server or store any data.
|
|
This guide provides information that is specific to your operating system, as in these examples:
Windows: This information is specific to the Windows operation system.
UNIX: This information is specific to the UNIX operation system.
VMS: This information is specific to VMS operating system.
When necessary for clarity, the symbol 
is used to indicate the end of the system-specific text.
For sections that pertain to one system only, the system is indicated in the section title.
|
|
This guide uses the following terminology:
Note: A statement can be written in Ingres 4GL, a host programming language (such as C), or a database query language (SQL or QUEL).
|
|
This guide uses the following conventions to describe syntax:
Convention |
Usage |
|---|---|
Monospace |
Indicates key words, symbols, or punctuation that you must enter as shown |
Italics |
Represent a variable name for which you must supply an actual value |
[ ] (brackets) |
Indicate an optional item |
{ } (braces) |
Indicate an optional item that you can repeat as many times as appropriate |
| (vertical bar) |
Separates items in a list and indicates that you must choose one item |