Technical Notes

Upgrading to Reflection for the Web 9.x
Technical Note 1853
Last Reviewed 28-Feb-2008
Applies To
Reflection for the Web version 7.0 through 9.6
Summary

This note describes how to upgrade to Reflection for the Web 9.x from Reflection for the Web 7.x, 8.x, or 9.x.

For information about upgrading to Reflection for the Web 9.x from Reflection for the Web version 5.x or 6.x, see Technical Note 1854.

Note: Reflection for the Web 2008 is available beginning in June 2008.

• For a list of new features in Reflection for the Web 2008 R1, see Technical Note 2345.
• For information about upgrading to Reflection for the Web 2008, see Technical Note 2349.
• For information about purchasing Reflection for the Web, please e-mail us at: SalesRecept@attachmate.com.

When you upgrade, it is strongly recommended that you follow the steps in the order they are presented:

Note the following:

• The term "Reflection management server" refers to the Administrative WebStation plus the terminal emulation files.
• If your configuration enables users to save preference files, see the Note about User Preference Files at the end of this technical note.
• If after upgrading, you receive error messages when trying to make a secure connection, see Technical Note 1956 titled, Error Message: "Invalid or missing authorization token."
• If you have server replication enabled in your environment, you must disable replication before you upgrade Reflection for the Web.

1. Configure the master server and each slave server as a standalone server.
2. Upgrade all servers, per the instructions below.
3. Configure the master server to master mode and define the slave servers.
4. Configure the slave servers to slave mode and point each slave server to the master server.

Step I: Uninstall Reflection for the Web 7.x, 8.x, or 9.x Components

Note: For all installation methods, if you used the UDC Mapping tool in the Administrative WebStation to assign custom characters to EBCDIC values and you want to retain those mappings, save a copy of the udc.xml file that is in the <Reflection management server installation>/ReflectionData/ directory.

Remove Reflection for the Web 7.x, 8.x, or 9.x files from your server. To uninstall a previous version:

• If you used an automated installer, follow one of these procedures:
  • Windows: Go to Start > Settings > Control Panel > Add or Remove Programs. Select Reflection for the Web and click Remove.
  • HP, Linux, or Solaris: Run uninstaller.sh from the [installation folder]/utilities/ directory. An X11 window is required to run the graphical interface. Ensure that you have root access, and then enter this command:

• On other platforms, shut down the Reflection servers, save these files and folders, and then uninstall:

• The web.xml file in the <Reflection management server installation>/jakarta-tomcat-[version number]/webapps/rweb/WEB-INF/ directory.
• Any files that you customized in the <Reflection management server installation>/jakarta-tomcat-[version number]/webapps/rweb/ or <Reflection management server installation>/jakarta-tomcat-[version number]/webapps/rweb/gm/ directory.
• Any unprotected, static sessions in the <Reflection management server installation>/jakarta-tomcat-[version number]/webapps/rweb/session/ directory. These sessions may also be saved in other directories within the webapps directory.
• The <Reflection management server installation>/ReflectionData/ directory.
• The cacerts file in the <Reflection management server installation>/_jvm/lib/security/ directory.

• The <security proxy installation>/conf/ directory and the <security proxy installation>/keystores/ directory. This saves your server.properties file and your certificates.

• The web.xml file in the <metering server installation>/jakarta-tomcat-[version number]/rwebmeter/WEB-INF/ directory.

• The Tomcat keystore in the <tomcat installation>/jakarta-tomcat-[version number]/conf/ directory.

Step II: Reboot the Server(s) from Which You Uninstalled Reflection

If you are running in a Windows environment, restart the server(s) from which you uninstalled Reflection for the Web components.

For all other environments, restarting the servers(s) is not necessary; proceed to Step 3.

Step III: Install Reflection for the Web 9.x Components

Install the Reflection for the Web 9.x components now. When you upgrade from a previous version:

• Install Reflection for the Web 9.x in the same directory structure that Reflection for the Web 7.x, 8.x, or 9.x used.
• Select and follow an installation procedure described in the InstallGuide.html file, located at the root of your product CD.

Step IV: Upgrade Outdated Files

The steps to upgrade outdated files vary depending on how you originally installed Reflection for the Web.

If you installed using an automated installer:

This section includes information about retaining settings for the management server, servlet runner, security proxy server, and metering server if you originally installed Reflection for the Web using an automated installer.

Note the following:

• Follow the steps below in the "For all installation types:" section to retain customized settings and imported certificates, and to upgrade JCE policy files and UDC files.
• See the Static Session Migration procedure in the Administrative WebStation to upgrade sessions that were not saved using the Session Manager or that were manually edited.

Reflection management server and servlet runner

Reflection management server and servlet runner settings have been retained. If you did not customize files or add certificates to the management server trusted list, no further upgrade steps are necessary.

Security proxy server

To ensure that you can edit your existing secure sessions or create new secure sessions in the Session Manager, export the security proxy server settings to the Administrative WebStation.

1. Run the Security Proxy Wizard.
2. Go to the Proxies tab and select Export Settings. You are prompted to export your settings to the management server.
3. Ensure that the management server name, port, and context are correct, and then click Export.

Note: In Reflection for the Web 9.x, the Save button will be grayed out if you haven't made any changes.

For detailed configuration information, see the tutorial, Setting Up the Security Proxy, in the Administrative WebStation.

Metering server

Upgrade of the metering server is complete. To ensure that your settings were saved correctly, open the Metering Configuration tool. For detailed configuration information, see the tutorial, Setting Up the Metering Component, in the Administrative WebStation.

If you installed using archive files:

Ensure that these files are copied or edited correctly.

Reflection management server:

1. Copy the old ReflectionData directory into your new Reflection management server directory structure.
2. Edit the web.xml file. Copy the path to the ReflectionData folder and the sslport value from the web.xml file that you saved into the new web.xml file in <Reflection management server installation>/jakarta-tomcat-[version number]/rweb/WEB-INF/.
3. If you customized the login and links list pages, copy the LauncherHTML.jsp file from the <Reflection management server installation>/jakarta-tomcat-[version number]/rweb/gm_nnn/ backup directory into the /gm/ directory.
4. Copy the old cacerts into the <Reflection management server installation>/_jvm/lib/security/ directory.

Security proxy server:

Copy the /conf/ and /keystores/ directories that you saved in Step I into the new security proxy installation.

To ensure that you can edit your existing secure sessions or create new secure sessions in the Session Manager, export the security proxy server settings to the Administrative WebStation.

1. Run the Security Proxy Wizard.
2. Go to the Proxies tab and select Export Settings. You are prompted to export your settings to the management server.
3. Ensure that the management server name, port, and context are correct, and then click Export.

Note: In Reflection for the Web 9.x, the Save button will be grayed out if you haven't made any changes.

For detailed configuration information, see the tutorial, Setting Up the Security Proxy, in the Administrative WebStation.

Metering server:

Edit the web.xml file. Copy the path to the ReflectionData folder from the web.xml file you saved into the new web.xml file in the <metering server installation path>/jakarta-tomcat-[version number]/webapps/rwebmeter/WEB-INF/ directory.

Servlet runner:

Copy the Tomcat keystore you saved into <installation path>/jakarta-tomcat-[version number]/conf/.

In a text editor, open <installation path>/jakarta-tomcat-[version number]/conf/server.xml. Make necessary modifications to the HTTP port and HTTPS port.

For all installation types:

The following procedures to upgrade outdated files apply to all Reflection for the Web installation types.

JCE policy files

If you installed the JCE unlimited strength policy files from the Sun web site to support 192-bit and 256-bit AES encryption in your previous version of Reflection, the downloaded files are uninstalled from the management server without notification during an automated uninstallation.

If you installed using an automated installation, the JRE version 5.0 was installed. To continue supporting 192-bit and 256-bit AES encryption, download and install the most recent version of the JCE unlimited strength policy files from the Sun web site. For more details, see the Security Proxy Wizard help (Security Proxy Wizard > Proxies > Add or Modify > Add or Modify > Help).

UDC mapping

If you saved your UDC Mapping settings by saving the udc.xml file in Step I, copy the udc.xml file into the new ReflectionData directory in version 9.x.

Servlet runner

If you installed tomcat.zip, upgrade your JDK to Java 2 (version 5.0 is recommended).

Trusted certificates

Automatic installation: If you added certificates to the management server trusted list, the imported certificates are stored in the cacerts file. This file was automatically saved during uninstallation of your previous version in the root of the Reflection management server installation, and renamed. The new name is created by appending an underscore and a three-digit number to the original file name, for example, cacerts_000. Copy this file into the new <Reflection management server installation>/_jvm/lib/security/ directory, and then rename the file to cacerts.

SSL client certificates or SSH user keys

If you enabled client authentication in version 7.x or 8.x, each client computer had a client certificate client.pfx file in its user.home folder. In the latest version of Reflection, the expected location is user.home\reflectionweb\. Move these files from the original location to the new location. For example, on a Windows 2000 or XP platform, the new location is C:\Documents and Settings\[username]\reflectionweb\.

If you used the Secure Shell transport in HP or VT sessions and you authenticated using user keys, the public/private key pairs were installed in the clients' user.home\.ssh\ directories. In the latest version of Reflection, the expected location is user.home\reflectionweb\.ssh\. Move these files on the client computers from the original location to the new location. For example, on a Windows 2000 or XP platform, the new location is C:\Documents and Settings\[username]\reflectionweb\.ssh\.

Customized files

To retain any unprotected static sessions, see the Static Session Migration procedure in the Administrative WebStation.

To retain your settings if you saved the LauncherHTML.jsp file from your version 7.x or 8.x installation, save LauncherHTML.jsp in your new Reflection for the Web installation at [Reflection management server installation]/jakarta-tomcat-[version number]/webapps/rweb/gm/.

IIS Integration

If you installed using an automated installer, the installer prompted you to configure IIS during installation. You will need to stop and restart IIS and the Reflection Management server service for integration to take effect.

If you installed using an archive file, re-run the IIS Wizard. (For more information see Technical Note 2195.) Enter the HTTPS port number, click Next, and then Finish.

Note: If you are using Windows Server 2003 or if the server has multiple web sites, see Technical Note 2195 for more information about integrating Reflection for the Web with IIS.

Step V: Update Printing Sessions

When upgrading from Reflection for the web 7.x or 8.x to Reflection 9.x, your printer sessions, print setup, and the test print feature may no longer function.

If you experience this problem, follow the steps below.

1. Open the Reflection for the Web Administrative WebStation and click Session Manager.
2. Click the printer session link and then click Save Settings.
3. Repeat steps 1 and 2 for each printer session.

Note about User Preference Files

Each user's preference files are stored locally on the user's machine and are not upgradeable with the Reflection for the Web upgrade on the server. End users will need to create new preference files.

Advise the end users to rename the existing preference (.pref) files, launch a session, configure the settings as needed, and then save a new preference file. (In Reflection, click File > Save Preferences.)

Related Technical Notes

1854	Upgrading to Reflection for the Web 9.x from Reflection for the Web version 5.x or 6.x
1943	Features Introduced in Reflection for the Web 9.0 and 9.01
1956	Error Message: "Invalid or missing authorization token"
2345	New Features in Reflection for the Web 2008
2349	Upgrading to Reflection for the Web 2008