To create a response file, first run the installer for a record installation. A response file generated by the installer takes advantage of the installer’s real-time dependency checking and error reporting.
The format of response files resembles that of an .ini file, but response files have the .iss extension. A response file is a plain text file that consists of sections containing data entries. By default, the response file is called Setup.iss and is created in the Windows System directory.
If you are an experienced user of the installer, you might be accustomed to building response files manually. However, this method can cause problems at installation time, configuration time, or server startup time.
At the command prompt, navigate to the directory where the installer is located.
cd JavaES-install-dir
Use the Setup.bat /r command to create the response file, either in the default location or in the system's Windows folder or in a location you specify.
Use the /f1 option to specify where the response file is to be created and to provide a name. To avoid unpredictable results. specify an absolute path for the file that has the .iss extension. For example, type:
Setup.bat /r /f1"C:\Temp\example.iss".
Run \Setup.bat and not \Windows\setup.exe to start the installation.
Proceed with the installation providing the information that you want the silent installer to provide.
All the data typed and options selected are recorded in the .iss file.
At the end of the installation, the response file is generated.
The response file is ready for use with the options selected during the record installation. The response file can be edited manually to modify the options recorded. For information about how to edit a response file, see Editing the Response File.
After you have generated a response file, you can edit the response file to modify local parameters. These parameters include Administrator User ID, Administrator Password and Retype Password.
When editing the response file, follow these guidelines:
Do not modify parameters except to edit their values.
Do not remove a parameter even if the parameter does not have a value.
Do not add a parameter.
Do not change the order in which parameters appear.
Notice original types and formats and maintain them as you type new values.
Replace any value that you delete. If the parameter is required, installation or configuration could fail if the parameter has been deleted.
To add a component, change both the SunJavaES-count= (total) and SunJavaES-(count number)=SunJavaES\.... For example,
Original:
SunJavaES-count=2 SunJavaES-0=SunJavaES\MessageQueue SunJavaES-1=SunJavaES\DirectoryServer
Modified:
SunJavaES-count=3 SunJavaES-0=SunJavaES\MessageQueue SunJavaES-1=SunJavaES\DirectoryServer SunJavaES-2=SunJavaES\WebServer
For more information on response file, see Appendix C, Example Response File: Silent Installation
To add a subcomponent, change both total count and count number. The subcomponent is added after the main component. For example:
SunJavaES-3=SunJavaES\AccessManager\AMAdministrationConsole
The response file contains sections corresponding to the SdWelcome dialog box. For example:
[{311E6252-893E-4445-B865-94DAFF5C500C}-SdWelcome-0] Result=1
The section header [{311E6252-893E-4445-B865-94DAFF5C500C}-SdWelcome-0] indicates that the data pertains to the SdWelcome dialog box for a component with ProductCode (and PRODUCT_GUID) value {311E6252-893E-4445-B865-94DAFF5C500C }.
The -0 at the end of the header indicates that this is the first call to SdWelcome. If the installation displayed a second SdWelcome dialog box, its header would end with -1.
The Result=1 indicates the return value from the SdWelcome function. The return value 1 indicates that you clicked the Next button.
In the SdSetupType dialog box, the Quick_Configure specifies Configure Automatically During Installation and Configure_Later specifies Configure Manually After Installation.