Creating a Response File

By saving installation configuration information into a response file during the initial GUI installation, you can perform subsequent installations of SAP ASE using a silent—or unattended—method.

Note: SAP ASE version 16.0 uses a rearchitected installation program that is incompatible with response files generated for versions 15.0.3 and earlier. Do not use response files from these earlier versions; instead, create a new one from a 16.0 installation.

To create a response file when installing in GUI or console mode, specify the -r command line argument. The -r argument records your responses to the installation wizard prompts and creates a response file when the InstallAnywhere wizard exits. The response file is a text file that you can edit to change any responses before you use it in any subsequent installations. You can find a sample response file in installer image/sample_response.txt.

Create a response file during GUI installation:
```
setupConsole.exe -r [response_file_name]
```
Where:
- -r – specifies the command line argument.
- response_file_name – (Optional) is the absolute path of the file into which the installation information is stored, such as \tmp\responsefile.txt.
Note: The directory path you specify must already exist.
Verify that the response file includes the passwords for the SAP ASE sa login, SAP Control Center admin, and SCC agent admin by including these lines in the file:
```
SY_CFG_ASE_PASSWORD=<ASE sa password>
CONFIG_SCC_CSI_SCCADMIN_PWD=<SCC admin password>
CONFIG_SCC_CSI_UAFADMIN_PWD=<SCC agent admin password>
CONFIG_SCC_REPOSITORY_PWD=<SCC repository password>
```
Each password must be at least six characters long. The sccadmin and uafadmin logins need not be the same as the sa password.
You can also set these passwords using these environment variables:
- SY_CFG_ASE_PASSWORD
- CONFIG_SCC_CSI_SCCADMIN_PWD
- CONFIG_SCC_CSI_UAFADMIN_PWD
- CONFIG_SCC_REPOSITORY_PWD
Note: Secure these response files appropriately if they contain passwords.
To enable a different user for the SAP ASE you are installing, define these properties:
```
SY_CFG_SERVICE_ACCOUNT_CHANGE=<yes | no>
SY_CFG_SERVICE_ACCOUNT_NAME=<account name>
SY_CFG_SERVICE_ACCOUNT_PASSWORD=<account password>
SY_CFG_SERVICE_DATA_DIRECTORY=<data directory>
```
You need not configure SY_CFG_USER_ACCOUNT_NAME or SY_CFG_USER_ACCOUNT_PASSWORD unless you set SY_CFG_USER_ACCOUNT_CHANGE to yes.
For the SY_CFG_SERVICE_DATA_DIRECTORY property, enter a directory other than the installed directory to which SAP ASE can create all the data files during configuration
SAP ASE creates these files during installation to place in the data directory:
- The interfaces file.
- RUN_server file.
- Configuration utilities log files.
- SAP ASE configuration file (.cfg) – under the ASE-16_0 subdirectory.
- SAP ASE shared memory file (.krg) – under the ASE-16_0 subdirectory.
- SAP ASE SySAM properties file – under the ASE-16_0\sysam subdirectory.
- Job Scheduler template .ini files – under the ASE-16_0\jobscheduler\Templates subdirectory
Database device files and server error log files are created in the data directory, but you can move them after the installation is finished.
Note: Make sure that the user you specify in this property setting has read/write/modify permissions to access the data directory.
To support earlier versions of SAP ASE on your system, you can specify these properties for a different Windows Service Account for each server for which you have not defined SY_CFG_SERVICE_ACCOUNT_*:
- For SAP ASE Windows Service:
  SY_CFG_ASE_SERVICE_ACCOUNT_CHANGE=<yes | no> SY_CFG_ASE_SERVICE_ACCOUNT_NAME=<account name> SY_CFG_ASE_SERVICE_ACCOUNT_PASSWORD=<account password>
- For Backup Server Windows Service:
  SY_CFG_BS_SERVICE_ACCOUNT_CHANGE=<yes | no> SY_CFG_BS_SERVICE_ACCOUNT_NAME=<account name> SY_CFG_BS_SERVICE_ACCOUNT_PASSWORD=<account password>
- For XP Windows Service:
  SY_CFG_XP_SERVICE_ACCOUNT_CHANGE=<yes | no> SY_CFG_XP_SERVICE_ACCOUNT_NAME=<account name> SY_CFG_XP_SERVICE_ACCOUNT_PASSWORD=<account password>