Creating a response file

There are two methods of generating a response file for the installation program:

WARNING! If you created a response file using a Custom installation, you need to edit the response file to allow the custom selections to be chosen correctly during installation. The following is a workaround for an installer issue when using a response file.

Use a text editor and delete the “Custom” setup type in this line:

-W setupTypes.selectedSetupTypeId=Custom

The resulting line will look similar to this:

-W setupTypes.selectedSetupTypeId=

Failure to delete the “Custom” setup type results in a Full installation of the product.

Interactive installation using a response file An interactiveinstallation using a response file allows you to accept the default valuesobtained from the response file that you have set up, or to change any of thosevalues for the specific installation. This is useful when you want multiple similar installations but with some minor differences that you want to change at installation time.

At the command line, execute this command (all on one line):

Installing in silent mode A silent mode installation, sometimes referred toas an unattended 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 when you want to automate the installation process.

At the command line, execute this command (all on one line):

where responseFileName is the name of the file containing the installation options you chose. The -W option specifies that you agree with the Sybase License Agreement text.

WARNING! In Windows only, Sybase recommends that you use the setupConsole.exe executable, which runs in the foreground, when running a silent installation. The normal setupwin32.exe executable runs in the background, giving you the impression that the installation has terminated immediately, without a completion status. This could result in duplicate installation attempts.

Except for the absence of the GUI screens, all actions of the installation program are the same, and the result of an installation in silent mode is exactly the same as one done in GUI mode with the same responses.