Upgrading to Reflection for the Web 12.3 from versions earlier than 12.2

  • 7022345
  • 21-Jun-2016
  • 25-Mar-2018

Environment

Reflection for the Web (All Editions) version 12.3

Situation

This technical note describes how to upgrade to Reflection for the Web 12.2 before upgrading to version 12.3.

To upgrade to Reflection for the Web version 12.3 from a version earlier than 12.2, it is recommended that you first upgrade to Reflection for the Web 12.2 which includes Management and Security Server 12.2. Then you can directly upgrade to version 12.3.

Why upgrade to Reflection for the Web 12.2 first?

Beginning in version 12.3, Reflection for the Web is a separate web application that requires Management and Security Server to create, configure, and deploy terminal emulation sessions. In earlier versions, Reflection for the Web included the Management and Security Server functionality.

Because the products are separate and need to be compatible, an initial upgrade to Reflection for the Web 12.2 provides the compatible versions that can then be directly upgraded to 12.3.

Resolution

Upgrading to Reflection for the Web version 12.2

Check your version of Reflection for the Web to determine which upgrade path to follow.

Reflection for the Web 2014 R2 = version 12.1
Reflection for the Web 2014 R1 = version 12.0
Reflection for the Web 2011 = version 11.0

Note: Earlier versions have been Discontinued. To upgrade from a version earlier than Reflection for the Web 2011, contact Technical Support.

Upgrade paths:

Upgrading from Reflection for the Web 2014

Follow these guidelines when upgrading using either an automated or manual installation.

Note: Remember to make a backup before proceeding with the upgrade.

Automated installation

  • When upgrading from Reflection for the Web 2014 to Reflection for the Web 12.2, the automated setup program will install the latest software and retain your current settings. You do not need to run a configuration upgrade utility as a separate step.
  • Although new installations of Reflection for the Web will install to a different directory (such as C:\Program Files\Micro Focus\MSS), an upgrade will install to your current installation directory.

Manual installation

  • If you installed the product using a multi-component installer, you can use the same approach again.

If you can use the default (Tomcat) servlet runner included with the product, extract the multi-component archive file appropriate for your platform, and then run the Configuration Upgrade Utility to handle the upgrade of your settings.

  • To avoid potential port conflicts, make sure the earlier version of the software is not running when you run the configuration utility. Then you will be able to accept the default port assignments.
  • If you are upgrading a Linux or UNIX system, make sure no startup scripts are running.

When the upgrade to version 12.2 is complete, you can upgrade directly to version 12.3. For instructions, see the Reflection for the Web 12.3 Installation Guide, https://www.attachmate.com/documentation/rweb-12-3/rweb-installguide/.

Upgrading from Reflection for the Web 2011

When upgrading from Reflection for the Web 2011 to Reflection for the Web version 12.2, the setup program will install the latest software and will retain your current settings. You do not need to run a configuration upgrade utility as a separate step.

Although new installations of Reflection for the Web will install to a different directory (such as C:\Program Files\Micro Focus\MSS), an upgrade will install to your current installation directory.

Note: Remember to make a backup before proceeding with the upgrade.

Automatic installation

  • Upgrades for versions of Reflection for the Web 2011 that were installed with the automated installer require no additional steps.
  • If you use SiteMinder for Access Control and you are upgrading from a version of Reflection for the Web 2011 Hot Fix 5 or earlier, you must copy the SiteMinder Java Agent JAR file from your SiteMinder distribution media to the Administrative Server's lib directory and restart the Tomcat servlet runner after the upgrade is complete. See KB 7021600 for details.

Manual installation

  • If you installed using a multi-component installer, you can use the same approach again.

If you can use the default (Tomcat) servlet runner included with the product, extract the multi-component archive file appropriate for your platform, and then run the Configuration Upgrade Utility to handle the upgrade of your settings.

  • To avoid potential port conflicts, make sure the earlier version of the software is not running when you run the configuration utility. Then you will be able to accept the default port assignments.
  • If you are upgrading a Linux or UNIX system, make sure no startup scripts are running.

When the upgrade to version 12.2 is complete, you can upgrade directly to version 12.3. For instructions, see the Reflection for the Web 12.3 Installation Guide, https://www.attachmate.com/documentation/rweb-12-3/rweb-installguide/.

Additional Considerations

These upgrade modifications may be necessary after any upgrade method.

Customized static session files

To retain any unprotected static sessions, see Upgrading Static Sessions in the Reflection for the Web 12.2 Installation Guide, https://www.attachmate.com/documentation/rweb/rweb-installguide/.

IIS Integration

The automated installation program detects IIS and allows you to integrate Reflection for the Web as part of the installation process.

If you need to make modifications later, see Running the IIS Integration Utility in the Reflection for the Web 12.2 Installation Guide, https://www.attachmate.com/documentation/rweb/rweb-installguide/

Upgrading replicated servers

If server replication is enabled, you must disable it on every server with replication before you upgrade. Follow these steps:

  1. In the Administrative WebStation, under Activities > Settings, click the Replication tab and select the Standalone option. Click Save Settings.
  2. Repeat this step for the Master server and all the Slave servers.
  3. Upgrade all the servers.
  4. Configure the Master server from Standalone back to Master role and define the Slave servers.
  5. Configure the Slave servers from Standalone back to Slave role and point them to the Master server.

Importing an activation file

After installing Reflection for the Web, you can add modules for other terminal types or for expanded functionality, which require activation files to be imported.

The automated installation procedure provides a warning when this step is required after you finish installing. For details, see Importing Activation Files in the Reflection for the Web 12.2 Installation Guide, https://www.attachmate.com/documentation/rweb/rweb-installguide/.

Resources

Reflection for the Web 12.2 Installation Guide, https://www.attachmate.com/documentation/rweb/rweb-installguide/

Reflection for the Web 12.3 Installation Guide, https://www.attachmate.com/documentation/rweb-12-3/rweb-installguide/

Additional Information

Legacy KB ID

This document was originally published as Attachmate Technical Note 2875.

Feedback service temporarily unavailable. For content questions or problems, please contact Support.