Feedback
Did this article resolve your question/issue?

   

Article

How to use Windows or Linux scripting to adjust hostname in response.ini file for silent install on different computers.

Information

 
TitleHow to use Windows or Linux scripting to adjust hostname in response.ini file for silent install on different computers.
URL Namehow-to-use-windows-or-linux-scripting-to-adjust-hostname-in-response-ini-file-for-silent-install-on-different-computers
Article Number000133733
EnvironmentProduct: OpenEdge
Version: All supported versions
OS: All supported platforms
Question/Problem Description
How to use Windows or Linux scripting to adjust hostname in response.ini file for silent install on different computers.

 
Steps to Reproduce
Clarifying Information
Error Message
Defect/Enhancement Number
Cause
Resolution
On Windows the following script will edit  an existing response.ini file, where a hostname from the original system is already embedded in the file, and will replace the the original hostname in the file with the hostname of the system the script is running.
Microsoft Powershell (which is installed on most Windows 7 / Windows 2008r2 or later systems) is used to replace the text in the file.
Example of Windows script:
hostname > tmpFile 
set /p myvar= < tmpFile 
del tmpFile 
set ffile='<path to response.ini file directory>\oe_response.ini'
set fold='<original hostname embedded in response.ini file here>'
set fnew='%myvar%'
powershell -Command "(gc %ffile%) -replace %fold%, %fnew% | Out-File %ffile% -encoding utf8"
start /wait ""<path to Progress installation files here>\setup.exe -psc_s -psc_f1="<path to oe_response.ini dir>"\oe_response.ini

On Unix same can be done on with a script similar to the following:
set fnew=`hostname`
set ffile='<path to response.ini file directory>\oe_response.ini'
set fold='<original hostname embedded in oe_response.ini file here>'
sed -i "s/$fold/$fnew/g" oe_response.ini
<path to Progress installation files here>/proinst -psc_s -psc_f1=<path to response.ini dir>/oe_response.ini
Workaround
Notes
Last Modified Date8/7/2018 1:52 PM
Attachment 
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.