Perform silent installation (sometimes referred to as an “unattended installation”) by running InstallShield and providing a response file that contains answers to all InstallShield questions.
There are two ways of creating a response file for InstallShield; using record mode or template mode.
In this mode, InstallShield performs an installation of the product and records all your responses and selections in the specified response file. You must complete the installation to generate a response file. To create a response file, enter:
On Windows:
setup.exe -options-record responseFileName
On Solaris:
./setup -options-record responseFileName
where responseFileName is the absolute path of the file name you choose for the response file.
You can also use the console mode to generate a response file without using the graphical interface.
On Windows, enter the following at the command line:
setupConsole.exe -options-record responseFileName
On Solaris, enter:
./setup -is:javaconsole -console -options-record responseFileName
The following are the results:
An installation of DI Suite components on your computer
A response file containing all of your responses from the installation
If you use this response file for a silent installation, the resulting installation is identical to the one from which the response file was created; the same installation location, same feature selection, and all the same remaining information. The response file is a text file that you can edit to change any responses before using it in any subsequent installations.
In this mode, InstallShield creates a response file containing commented-out values for all required responses and selections. However, you need not install the product, and you can cancel the installation after the response file has been created. To create this template file, enter:
On Windows:
setupConsole.exe -options-template responseFileName
On Solaris:
./setup -is:javaconsole -options-template responseFileName
where responseFileName is the file name you choose for the response file. When specifying the response file name, include the full directory path of its location.
If run in console mode, as shown in the previous example, InstallShield provides a message indicating that the template creation was successful. If run in GUI mode, no such message is provided.
If you use this response file for a silent installation, the default values for all responses are used. Edit the template with the values you want to use during installation.
An interactive installation using a response file allows you to accept the default values from the response file, or to change any of those values for the specific installation. This is useful when you have multiple similar installations that have minor differences that you want to change at installation time.
On Windows, enter the following at the command line:
setup.exe -options responseFileName
On Solaris, enter:
./setup -options responseFileName
where responseFileName is the file name containing the installation options you chose. When specifying the response file name, include the full directory path of its location.
A silent-mode installation allows you to install the product with all responses being taken from the response file that you have set up. There is no user interaction. This is useful when you want multiple identical installations, or you want to automate the installation process.
On Windows, enter the following at the command line:
setupConsole.exe -silent -options responseFileName -W SybaseLicense.agreeToLicense=true
On Solaris, enter:
./setup -is:javaconsole -silent -options responseFileName -W SybaseLicense.agreeToLicense=true
where responseFileName is the absolute path of the file name containing the installation options you chose. The -W option specifies that you agree with the Sybase License Agreement text.
WARNING! On Windows, Sybase recommends that you use setupConsole.exe rather than setup.exe. setupConsole.exe runs in the foreground when you are running a silent installation, while setup.exe runs in the background, giving the impression that the installation has terminated, and resulting in additional installation attempts using the silent installation. Multiple simultaneous installations may corrupt the Windows Registry and lead to a failure to restart the operating system.
Except for the absence of the GUI screens, all actions of InstallShield are the same, and the result of an installation in silent mode is exactly the same as one performed in GUI mode with the same responses.
