Silent installations and upgrades in DC RUM 2017

Applies to DC RUM 2017

Upgrade response files

This help applies to DC RUM 2017 deployments. If you are creating a silent installation for a more recent release, see Silent installations and upgrades.

Upgrade response files

DC RUM release 2017 uses a single point of access for user management and security for DC RUM
The RUM Console, the CAS and the ADS installation and upgrade wizards have changed to allow for the import of users from an existing CSS for RUM Console and to provide the authentication token for CAS or ADS. As a result, any installation response files created for previous DC RUM releases are invalid for upgrading to DC RUM 2017 release.

Generate a new response file using the newest installation wizard for the RUM Console.

You can use a standard DC RUM 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 DC RUM 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 DC RUM component.

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

Importing users to RUM Console from existing Central Security Server (CSS)

This response file example imports users from an existing CSS located at 192.168.1.66.
Properties indicating the import option:

MIGRATE_CSS_DB_VAR=1 (set 1 for user import)
NEW_CSS_DB_VAR=0

Properties providing details for the import CSS:

CSS_IP_MIGRATE=192.168.1.66 (IP address or host name of the existing CSS - user import source.)
CSS_PORT_MIGRATE=4182
CSS_USER_MIGRATE=adminuser (existing CSS administrator account)
CSS_PWD_MIGRATE=

This response file does not import users from an existing CSS. Instead, it creates a new admin user (adminuser).

Properties indicating the import option:

MIGRATE_CSS_DB_VAR=0
NEW_CSS_DB_VAR=1 (set 1 for create new user in the database)

Properties providing details for the new user to be created:

CSS_ADMIN_USER=adminuser (new RUM Console administrator account)
CSS_ADMIN_PWD= CSS_ADMIN_PWD2=

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 DC RUM 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 DC RUM 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.