Installation and Configuration Guide : B. OpenROAD Command Line Installation (Windows Only) : Sample Propertiesfile
 
Share this page                  
Sample Propertiesfile
The following sample propertiesfile files are distributed with the 32-bit OpenROAD version to show how the ormsiexec.bat script can be used to install or uninstall OpenROAD or Loadnrun.
In the example propertiesfiles the existing 32-bit Ingres instance is called IngresCT and the existing 64-bit Ingres instance is called IngresTC. This is purely arbitrary. The products can be installed into any compatible Ingres instance as long as it is not one reserved by OpenROAD—XA, XB, XC, XD, XE, XU; or Loadnrun—XN, XO, XP, XQ, XR, XT; or Enteprise Accees—EA. If another Ingres instance is identified, ensure that the INSTALLDIR, INGRESGROUP, and INGRESINSTALLATION properties are adjusted accordingly.
The scripts are listed and described in the following table.
Propertiesfile Name
Description
loadnrun_x64_nonet.rsp
Installs the 64-bit Loadnrun 6.2 instance with no S/A Net configured. It has an option to uninstall the product as well.
loadnrun_x64_sanet.rsp
Installs the 64-bit Loadnrun 6.2 client with the S/A Net instance configured. It has an option to uninstall the product as well.
openroad_x64_ingresTC.rsp
Installs 64-bit OpenROAD 6.2 into an existing Ingres instance. The directives assume that the 64-bit IngresTC instance is the target.
If the Ingres target is an instance other than 32-bit IngresTC, the following directives must be modified:
[PROPERTY]INSTALLDIR=NewInstallDirValue
[PROPERTY]INGRESGROUP=NewIngresGroupValue
If the target location is not the default, the same directives must be altered.
The following directives must be set if installing into an existing Ingres instance:
[PROPERTY]FEATNETCLIENT=Hide
[PROPERTY]FEATNETODBC=Hide
If these values are not set, the target Ingres instance could be corrupted.
openroad_x64_sanet.rsp
Installs 64-bit OpenROAD 6.2 into the S/A Net Client. (This is always the IngresXE instance.)
entacc_x86_ingresCT.rsp
Installs 32-bit Enterprise Access into an existing Ingres instance. The directives assume that the 32-bit IngresCT instance is the target.
If the Ingres target is an instance other than IngresCT, the following directives must be modified:
[PROPERTY]INSTALLDIR=NewInstallDirValue
[PROPERTY]INGRESGROUP=NewIngresGroupValue
If the target location is not the default, the same directives must be altered.
The following directives must be set if installing into an existing Ingres instance:
[PROPERTY]FEATNETCLIENT=Hide
[PROPERTY]FEATNETODBC=Hide
If these values are not set, the target Ingres instance could be corrupted.
entacc_x86_sanet.rsp
Installs 32-bit into the S/A Net Client. (This is always the IngresEA instance.)
The following sample propertiesfile files are distributed with the 64-bit OpenROAD version to show how the ormsiexec.bat script can be used to install or uninstall OpenROAD or Loadnrun. The scripts are listed and described in the following table.
Propertiesfile Name
Description
loadnrun_x64_nonet.rsp
Installs the 64-bit Loadnrun 6.2 instance with no S/A Net configured. It has an option to uninstall the product as well.
loadnrun_x64_sanet.rsp
Installs the 64-bit Loadnrun 6.2 client with the S/A Net instance configured. It has an option to uninstall the product as well.
openroad_x64_ingresTC.rsp
Installs 64-bit OpenROAD 6.2 into an existing Ingres instance. The directives assume that the 64-bit IngresTC instance is the target.
If the Ingres target is an instance other than 32-bit IngresTC, the following directives must be modified:
[PROPERTY]INSTALLDIR=NewInstallDirValue
[PROPERTY]INGRESGROUP=NewIngresGroupValue
If the target location is not the default, the same directives must be altered.
The following directives must be set if installing into an existing Ingres instance:
[PROPERTY]FEATNETCLIENT=Hide
[PROPERTY]FEATNETODBC=Hide
If these values are not set, the target Ingres instance could be corrupted.
openroad_x64_sanet.rsp
Installs 64-bit OpenROAD 6.2 into the S/A Net Client. (This is always the IngresXE instance.)
The propertiesfile files must be placed into the same directory as the installer setup.ini file is located. The ormsiexec.bat script can be launched from any location. The propertiesfile file is passed as the first parameter to the ormsiexec.bat; this can be a file name, relative path location, or absolute path location of the file.