OpenEdge can be configured to use a text file to govern the installation process.
For all Silent Installs the basic concepts are the same.
- An interactive installation is performed to record the basic installation options. In versions 10.2B and later a file named response.ini is automatically generated in the %DLC%\installation directory.
- The file recorded (typically response.ini) is used to perform a non-interactive installation
To make the process more usable for a larger variety of installation scenarios improvements were made.
In
OpenEdge 10.1C and later, a license addendum can be downloaded from the
License Tab in
.htm format from the Progress ESD site (see the first article in the notes section below for more details).
This file can be used during an OpenEdge install to provide the installation codes withou having to manually enter license codes.
In
OpenEdge 11.4, and later the Silent Installation functionality was further enhanced to include an option to define the
License Addendum file path and
Company Name in the response file (silent answer file) which makes it simpler to use one
When deploying multiple installations of the same licenses at different customer sites, the same recorded
response.ini file can be used by simply using the license addendum file path and assuring that Customer Site's unique License Addendum's used when license information are read.
While this feature has been available since OpenEdge 11.4, it is advisable to upgrade to OpenEdge 11.7.3, 12.0 or later, where the validity of this information is checked assuring all intended licenses are installed. For further information refer to Article:
Using the License Addendum file path and Company Name for Silent InstallsOne common scenario performed by many customers is when multiple sites install the same set of OpenEdge products with unique installation codes.
For the following example it will be understood that three licenses will be installed at multiple sites. Each site will have its own unique serial numbers and control codes
- Progress Production AppServer for OE
- OE Enterprise RDBMS
- OpenEdge Replication Plus
1. Use the first customer's license addendum file to record the
response.ini file using either:
a. The full install media provided from the Progress ESD download or
b. Since OpenEdge 11.6, use a smaller custom installation bundle (refer to the article in the notes section below on creating a custom installation bundle)
2. Edit the response.ini (answer file):
a. Delete the control codes added with each product line generated automatically during the record mode of a manual installation.
In this example the following lines are deleted from the response.ini file because they will be supplied by the site specific license addendum files downloaded by the scenario implementer:
ProductName-0=Progress ProdAS for OE
SerialNumber-0=[001234567]
ControlNumber_1-0=[-----]
ControlNumber_2-0=[-----]
ControlNumber_3-0=[-----]
ProductName-40=
ProductName-1=OE Enterprise RDBMS
SerialNumber-1=[001234567]
ControlNumber_1-1=[-----]
ControlNumber_2-1=[-----]
ControlNumber_3-1=[-----]
ProductName-2=OpenEdge Repl Plus
SerialNumber-2=[001234567]
ControlNumber_1-2=[-----]
ControlNumber_2-2=[-----]
ControlNumber_3-2=[-----]
b. Add the license addendum file path and registered company response.ini options to the response.ini file:
Linux:
[Configuration Count]:
LicenseAddendumFile=<path to site specific license addendum file>
CompanyName=<site specific company name>
Windows:
[Serial Number And Control Codes Dialog]
LicenseAddendumFile=<path to site specific license addendum file>
CompanyName=<site specific company name>
- Or add additional product control codes to the response.ini file of those to be silently installed as additional products.
The Downloadable License Configuration File utility available since OpenEdge 10.2B, can be used to create a tailored license file to use when installing new licenses. For further information refer to Article:
3. Run the silent install
The Install routine will first check the existence of “
LicenseAddendumFile” in the response file to use the addendum file during silent installation, otherwise it will still support the previous functionality and read the Control Codes for each product line from this section.
