Silent installations and upgrades

Applies to NAM 2018

Upgrade response files

This help topic is for NAM 2018. If you are creating a silent installation for DC RUM 2017, start with Silent installations and upgrades in DC RUM 2017.

Any installation response files created for previous releases are invalid for upgrading to this release. Generate a new response file using the newest installation wizard.

You can use a standard installer to record your settings in a properties file, and then use that properties file to automate subsequent installations:

  • Use a properties file interactively when you want to step through each page of an installer and use most or all of the same settings you recorded earlier, but perhaps change one or two settings per installation.
  • Use a properties file silently when you want to run multiple installations on a number of other machines using exactly the same settings you used to make one interactive installation.

For more information, please also refer to the InstallAnywhere documentation on its Replay feature.

To generate a properties file for a NAM installation

Regardless of how you intend to use it, you need to start by generating a response file.

Download an installer from the Dynatrace site and save it to a convenient directory on your Windows machine.

Open a Windows command prompt.

Select Start ► Run

Type cmd in In the Open box and then click OK

Change to the directory in which you saved the installer.

Start the installer with the -r option and with a profile file name specified.
For example, type or paste the following command and press Enter.
Console_setupAMD64.exe -r installer.properties
where

  • Console_setupAMD64.exe is the installer
  • -r specifies that you want to generate a response file
  • installer.properties is the name under which you want to save the response file

The installer runs interactively as usual, but after installation it writes an installer.properties file in which it records all of the settings you specify during this installation session.

Important

Passwords are an exception. Your passwords are not recorded. You must use a text editor to add your passwords to the properties file before you use the file to install a NAM component.

After installation is complete, use a text editor to open the installer.properties file and verify that your settings have been recorded.

To use a properties file during an interactive installation

Use a properties file in an interactive installation when you want to reuse most but not all of the settings you recorded.

Install the product manually using the -r option as described earlier to create a properties file for that type of installation.

Save the installer and the properties file in the same directory, and switch to that directory.

Use a text editor to edit the properties file as needed.

Important

Remember that passwords are not recorded. Before you can use a properties file to install a NAM component, you must open the properties file in a text editor, scan it for password names such as (from the example above)

SQL_ADMIN_PWD=
SQL_DB_USER_PWD=
SQL_DB_USER_PWD_2=

which have no corresponding passwords. Add the passwords after the equal signs and save the file.

Start the installer with the -f option this time (not -r) but with the same profile file name specified.
For example, type or paste the following command
Console_setupAMD64.exe -f installer.properties where

  • Console_setupAMD64.exe is the installer
  • -f specifies that you want to use a previously generated properties file
  • installer.properties is the name of the properties file you previously created and now want to use

The installer runs interactively as usual, but it reads the installer.properties file and uses the recorded values as defaults, so you can just step through the installation and make changes only as needed.

To use a properties file during a silent installation

Use a properties file in a silent installation when you want to reuse all of the settings you recorded.

Install the product manually using the -r option as described earlier to create a properties file for that type of installation.

Save the installer and the properties file in the same directory, and switch to that directory.

Use a text editor to edit the properties file as needed.

Important

Remember that passwords are not recorded. Before you can use a properties file to install a NAM component, you must open the properties file in a text editor, scan it for password names such as (from the example above)

SQL_ADMIN_PWD=
SQL_DB_USER_PWD=
SQL_DB_USER_PWD_2=

which have no corresponding passwords. Add the passwords after the equal signs and save the file.

Start the installer with the -i option and the -f option to run the installer silently using a properties file.
For example, type or paste the following command Console_setupAMD64.exe -i silent -f installer.properties

where

  • Console_setupAMD64.exe is the installer
  • -i silent sets the installation mode to silent
  • -f specifies that you want to use a previously generated properties file
  • installer.properties is the name of the properties file you previously created and now want to use

The installer runs silently and reads the installer.properties file for all recorded values.

To upgrade product software without changing property settings

Use a properties file during an upgrade when you want to leave all settings unchanged but you want to upgrade the software.

As described earlier, install the product manually once using the -r option as described earlier to create a properties file for that type of installation.

Save the installer and the properties file in the same directory, and switch to that directory.

Use a text editor to insert this line anywhere in the properties file.

PRODUCT_UPGRADE=true

This flag instructs the installer to ignore all properties in the properties file and to simply upgrade the product software.

Run the installer interactively or silently (depending on your needs).

The installer runs, reads the installer.properties file, and (because of the PRODUCT_UPGRADE=true flag) upgrades the product software without changing the settings.