Install Enterprise Access using a Response File
After you create the Enterprise Access response file, you need to invoke the EA installer. The installer performs a silent installation and configuration of the components as specified in the response file.
To install Enterprise Access using a response file
Issue the following command from the root directory of the EA install image:
setup /r <path><response_file_name>
<path>
Specifies the full storage location path for the response file.
<response_file_name>
Specifies the name of the response file.
Example setup /r command
C:\EA3_0\cdimage\setup /r C:\EA3_0\myresponsefile.rsp
Response File Parameters
The currently supported response file parameter options are as follows:
II_COMPONENT_MSSQLGATEWAY
Determines whether MS SQL Server gateway is to be installed. Valid values are "YES" and "NO". Default is "YES".
II_COMPONENT_ORACLEGATEWAY
Determines whether Oracle gateway is to be installed. Valid values are "YES" and "NO". Default is "YES".
II_COMPONENT_ODBCGATEWAY
Determines whether the ODBC gateway is to be installed. Valid values are "YES" and "NO". Default is "YES".
II_COMPONENT_NET
Determines whether Ingres Net is to be installed. Valid values are "YES" and "NO". Default is "YES".
II_COMPONENT_EMBEDDEDPROGRAMMING
Determines whether the tools and supporting files for Embedded SQL programming with C/C++, COBOL and Fortran is to be installed. Valid values are "YES" and "NO". Default is "YES".
II_COMPONENT_DOCUMENTATION
Determines whether gateway documentation in Portable Document Format (PDF) is to be installed. Valid values are "YES" and "NO". Default is "YES".
II_SYSTEM
Defines the location of the Enterprise Access system (executable) files. The default directory path is "C:\Program Files\Ingres\IngresRR".
II_INSTALLATION
Defines the EA installation code. The installation code is a two-character code that identifies a specific installation on a node, and allows all EA processes and images to be installed and shared successfully. In an upgrade scenario, the existing value is kept. Valid values are [A-Z], [A-Z] [0-9]. Default is "II".
The first character of the installation code must be a letter; the second character can be a letter or numeral.
II_CHARSET
Specifies the value to be used for the Ingres environment variable II_CHARSETxx. In an upgrade scenario, the existing value is kept and should not be changed. Any valid value for II_CHARSETxx may be used. Default is "WIN1252" or "IBMPC850" depending on the code page selected for the operating system.
II_DICTIONARY_OK
If II_DICTIONARY_OK variable is set to anything, the usual frontend dictionary check when connecting to a DBMS is omitted.
Note: Some OpenROAD runtime methods will require existing frontend dictionary tables (for example, ii_stored_strings, ii_stored_bitmaps, ii_sequence_values), so they would fail if these tables are missing.
II_TIMEZONE_NAME
Specifies the value to be used for the time zone. In an upgrade scenario, the existing value is kept. Any valid Ingres II_TIMEZONE_NAME value may be used. Default is the time zone that most closely approximates the OS time zone, for example, "NA-EASTERN".
II_TERMINAL
Specifies the value to be used for the terminal type. In an upgrade scenario, the existing value is kept. Any valid value for II_TERMINAL enclosed in double quotes may be used. Default is "IBMPC".
II_ADD_TO_PATH
Defines whether to add EA to the Windows PATH. Valid values are "YES" and "NO". Default is "YES".
II_INSTALL_ALL_ICONS
Defines whether to create the EA program group and associated icons during the EA installation. Valid values are "YES" and "NO". Default is "YES".
II_START_INGRES_ON_COMPLETE
Defines whether to start Ingres after the EA installation completes. Valid values are "YES" and "NO". Default is "YES".
II_START_IVM_ON_COMPLETE
Defines whether to start the Ingres Visual Manager utility after the EA installation completes. Valid values are "YES" and "NO". Default is "YES".
II_SERVICE_START_AUTO
Specifies whether to start the Ingres service automatically at system startup. Valid values are "YES" and "NO". Default is "NO".
II_SERVICE_START_USER
Defines the user who can start Ingres as a service. Default is “LocalSystem”.
II_SERVICE_START_USERPASSWORD
Defines the password required to start Ingres as a service. Default is "". (No password if LocalSystem is used as II_SERVICE_START_USER value.)
II_ENABLE_TCP
Specifies whether to use TCP/IP networking protocol for Ingres Net. Valid values are "YES" and "NO". Default is "YES".
II_ORACLE_VERSION
Defines the Oracle gateway version used with Enterprise Access. To obtain valid options for this parameter, run iigwuseora or iigwuseora list.
Sample Response File
Here is an example of an Enterprise Access response file:
; Enterprise Access Response File
; Generated by the Enterprise Access Response File API
; Created: Tue, October 1, 12:20:07 2013
[Ingres Components]
II_COMPONENT_MSSQLGATEWAY="YES"
II_COMPONENT_ORACLEGATEWAY="YES"
II_COMPONENT_ODBCGATEWAY="YES"
II_COMPONENT_NET="YES"
II_COMPONENT_EMBEDDEDPROGRAMMING="YES"
II_COMPONENT_DOCUMENTATION="YES"
[Ingres Locations]
II_SYSTEM="C:\Program Files\Ingres\IngresEA"
[Ingres Configuration]
II_INSTALLATION="EA"
II_CHARSET="WIN1252"
II_TIMEZONE_NAME="NA-EASTERN"
II_TERMINAL="IBMPC"
II_ADD_TO_PATH="YES"
II_INSTALL_ALL_ICONS="YES"
II_START_INGRES_ON_COMPLETE="YES"
II_START_IVM_ON_COMPLETE="NO"
II_SERVICE_START_AUTO="NO"
II_SERVICE_START_USER="LocalSystem"
II_SERVICE_START_USERPASSWORD=""
II_ENABLE_TCP="YES"
II_ORACLE_VERSION="12"