Post-Installation Configuration (Windows)
The following steps apply to both existing and new installations.
1. If the gateways are to be run as a Windows Service, use the Windows Services applet to configure the Startup parameters.
Note: For existing Ingres installations, the gateway will run under the existing Ingres service. For standalone Ingres Net, the service is called Net <installation id>. Instructions for your Windows system may vary from those provided here.
To configure the startup parameters for a gateway service
a. From the Start menu, select Control Panel, Administrative Tools, and then the Services option.
b. Select the Ingres Intelligent Database xx service corresponding to the gateway instance for which you want to set startup parameters.
c. Select the General tab of the Properties dialog and configure the desired parameters. For help on a particular field, click the help button on the dialog's title b, drag it to the field, and click.
d. Select the Log On tab.
You can configure the gateway service to log on to a user account or to the local system account. (By default, the gateway service is created as Local System and no password is required.) To configure or change a user account, enter the user id and password corresponding to the account the gateway service will use to log on. Re-enter the password and click OK.
2. Use the Ingres Service Manager to start the installation. (Click Start, Programs, Ingres, Ingres <installation id>, Ingres Service Manager.) Alternatively, you can use the Windows Service Manager to start the installation as a service.
The Start as a service check box can be used to indicate whether the installation should run as a service or under the current login.
If the installation is started successfully, Ingres Service Manager eventually displays a message stating that installation started successfully.
Once the installation is started successfully, the following processes appear in Windows Task Manager:
Process Name | Description |
|---|---|
iigcc.exe | The Ingres Net process, which is needed if the gateway is accessed from a remote Ingres client. This is distributed with the gateway installation. |
iigcn.exe | The Ingres Name Server process, which is required by the gateway installation. |
iigcd.exe | The Ingres Data Access Server (DAS) process, which is distributed with the gateway installation. |
iigwmssd.exe | The Microsoft SQL Server gateway listener process, which handles connection requests to the Microsoft SQL Server gateway. |
iigworad.exe | The Oracle gateway listener process, which handles connection requests to the Oracle gateway. |
iigwodbd.exe | The ODBC gateway listener process, which handles connection requests to the ODBC gateway. |
Note: Only the processes associated with the components you installed appear in Task Manager.
3. Create the gateway alias used to access the host DBMS. See the chapter "Gateway Alias Configuration" in the Administrator Guide for more information on configuring the gateway alias.
4. Set up the gateway catalogs using the appropriate gateway catalog build utility. Each host DBMS has its own gateway catalog build utility, which is run from the command line. The following table provides the name of the catalog build program for each gateway:
Gateway | Catalog Build Utility |
|---|---|
Microsoft SQL Server | iigwcatmss |
Oracle RDBMS | iigwcatora |
ODBC | iigwcatodb |
Windows only: The GUI-based Gateway Catalog Utility (iigwcat) can be used instead of the command line catalog utilities to build the gateway catalogs for Oracle and MSSQL. 
You must provide a gateway alias entry when setting up the gateway catalogs. The gateway catalog build utility connects as the ingres user ID. If the gateway alias entry does not contain the password for the ingres user, you are prompted to enter it. The gateway DBA/DBO must be provided to the gateway catalog build utility. See the chapter "Gateway Catalog Setup" in the Administrator Guide for more information about building the gateway catalogs.
Oracle only: During the Enterprise Access installation, you were prompted to select the Oracle version that will be used with Enterprise Access. If you want to select a different Oracle version, or if Oracle is upgraded at a later time, you must run the command-line iigwuseora utility, or the GUI-based gwuseoraw utility (Windows only) to make the Oracle version change before running the gateway catalog build utility.
5. After you have created a gateway alias and built the gateway catalogs, you are ready to use the Enterprise Access gateways. See the chapter "Gateway Configuration Variables" in the Administrator Guide for more information about configuring the gateway parameters.
6. Use the Ingres Terminal Monitor to access each gateway:
sql dbname/server_class
where server_class is mssql, odbc, or oracle
Example: Access an Oracle database through the Oracle gateway
sql oracledb/oracle
Last modified date: 08/22/2022