Upgrading from an Earlier Version

Reflection for the Web 5.x or 6.x

If an outdated version of Reflection for the Web is installed or cached on your local computers and servers, use these instructions to upgrade to the current version of Reflection for the Web. When you upgrade, it is strongly recommended that you follow the steps in the order they are presented on this page.

To upgrade from Reflection for the Web 5.x or 6.x:

1. Uninstall Reflection for the Web 5.x or 6.x
2. Install Reflection for the Web 9.0 Components
3. Upgrade Outdated Files

Step 1: Uninstall Reflection for the Web 5.x or 6.x Components

Note: For all installation methods, if you used the UDC Mapping section of the Deployment Director to assign custom characters to EBCDIC values and you want to retain those mappings, copy and save the udc.xml file that is in the [Reflection management server installation]/ReflectionData/ directory.

Note: For all installation methods, if you exported keyboard map files using the Export Keymap command in the Reflection session, upgrade these files before uninstalling version 5.x or 6.x. See Upgrading External Keyboard Map Files for details.

Remove Reflection for the Web 5.x or 6.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 > Programs > WRQ Reflection for the Web > WRQ Reflection for the Web Uninstallation.
    
    
  • Windows: Run uninstaller.exe from the [installation folder]\_uninst\ folder.
    
    
  • Linux or Solaris: Run uninstaller.sh from the [installation folder]/utilities/ directory. Navigate to the directory and enter the command:
    
    ./uninstaller.sh
    
    
  Performing one of these operations will preserve your Reflection management server and security proxy server configurations. You will be prompted to save modified files during the uninstallation process.
  
  
• If you installed using archive files, first retain these files and folders, then uninstall:
  
  
  1. Reflection management server:
     
     Copy and save the web.xml file in the
     [Reflection management server installation]/jakarta-tomcat-[version number]/webapps/rweb/WEB-INF/ directory.
     
     Copy and save 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/WEB-INF/jsp/ directory.
     
     Copy and save 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.
     
     Copy and save the
     [Reflection management server installation]/ReflectionData/ directory.
     
     Copy and save cacerts in the
     [Reflection management server installation]/_jvm/lib/security/ directory.
     
     
  2. Security proxy server:
     
     Copy and save the
     [security proxy installation]/conf/ directory and the
     [security proxy installation]/keystores/ directory.
     This saves your server.properties file and your certificates.
     
     
  3. Metering server:
     
     Copy and save the web.xml file in the
     [metering server installation]/jakarta-tomcat-[version number]/webapps/rwebmeter/WEB-INF/ directory.
     
     
  4. Servlet runner:
     
     Copy and save the Tomcat keystore in the
     [tomcat installation]/jakarta-tomcat-[version number]/conf/ directory.
     
     
  5. Delete the directories in which you installed the Reflection for the Web components.
     
     

Step 2: Install Reflection for the Web 9.0 Components

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

• Install Reflection for the Web 9.0 in a non-web-servable space. This must be a directory that is inaccessible to your web server. Install Reflection for the Web 9.0 in the same directory structure that Reflection for the Web 5.x or 6.x used.
  
  
• Select and follow an installation procedure.

Step 3: Upgrade Outdated Files

If you installed using an automated installer:

Reflection management server and servlet runner settings have been retained. No further upgrade steps are necessary if you did not customize files or add certificates to the management server trusted list. Follow the steps below to retain customized settings or to retain imported certificates. Follow the steps below under For all installation types to upgrade JCE policy files, UDC files, other customized files, or certificates. Follow the steps in Upgrading Static Sessions to upgrade sessions that were not saved using the Session Manager or that were manually edited.

Upgrade of the security proxy server is complete. 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. Run the Security Proxy Wizard. Click Save to save your settings. You are prompted to export your settings to the management server. Ensure that the management server name, port, and context are correct, and then click Export.

Upgrade of the metering server is not supported by this installation process. To transfer the settings for your previous installation into your new installation, open the web.xml file in a text editor. Use this information as a reference when you configure the version 9.0 metering server using the metering configuration interface. For detailed configuration information, see Setting Up the Metering Component.

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. A new web.xml file has been created in the
     [Reflection management server installation]/jakarta-tomcat-[version number]/webapps/rweb/WEB-INF/.
     Open that new file in a text editor.
     
     
  3. In the new web.xml file, enter values for
     rwebdata_location_placeholder and
     https_port_placeholder from the web.xml file that you saved in step 1. You can cut and paste from your saved file, or enter values directly.
     
     
  4. Save the new web.xml file.
     
     
  5. 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 1 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. Run the Security Proxy Wizard. Click Save to save your settings. You are prompted to export your settings to the management server. Ensure that the management server name, port, and context are correct, and then click Export.
  
  
• 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 or HTTPS port.

For all 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 1, copy the udc.xml file into the new ReflectionData directory in version 9.0.
  
  
• JNLP sessions:
  
  If you created JNLP sessions in version 5.x, you will need to modify those sessions so they will work in Reflection for the Web version 9.0. For more information about running and modifying JNLP sessions, see Technical Note 1729.
  
  
• Servlet runner:
  
  If you installed tomcat.zip, upgrade your JDK to Java 2 (version 5.0 is recommended).
  
  
• Metering server:
  
  Use the settings recorded in the web.xml file to configure the new metering server. Open the web.xml file in a text editor and use these settings for reference when you configure the version 9.0 metering server. For detailed configuration information, see the tutorial Setting Up the Metering Server.
  
  
• 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.
  
  
• Customized files:
  
  To retain any unprotected static sessions, see Upgrading Static Sessions.
  
  To retain your settings if you saved the LauncherHTML.jsp file from your version 6.x installation:
  
  
  1. In a text editor, open your original LauncherHTML.jsp, which in version 6.x is in
     [Reflection management server installation]/jakarta-tomcat-[version number]/webapps/rweb/WEB-INF/jsp/.
     
     
  2. Replace the first two lines of the old file with these two lines:
     
         <%@ page import="com.wrq.java13plus.management.core.GmAsset" %>
    <%@ page import="com.wrq.java13plus.management.gm.LauncherStartAction" %>
     
     
  3. Save LauncherHTML.jsp in your new Reflection for the Web installation at [Reflection management server installation]/jakarta-tomcat-[version number]/webapps/rweb/gm/.
     
     
  To retain your settings if you saved the ReflectionClient.html file from your version 5.1 installation:
  
  
  1. In a text editor, open your original ReflectionClient.html, which in version 5.1 is in
     [Reflection management server installation]/ReflectionData/.
     
     
  2. In a text editor, open the new LauncherHTML.jsp, which is in
     [Reflection management server installation]/jakarta-tomcat-[version number]/webapps/rweb/gm/.
     
     
  3. Copy your color, margin, and font settings from ReflectionClient.html into LauncherHTML.jsp.
     
     
  4. Save the JSP file.
     
     
  To retain your settings if you saved the LoginPage.jsp file from your version 5.0 installation:
  
  
  1. In a text editor, open your original LoginPage.jsp, which in version 5.0 is in
     [Reflection management server installation]/jakarta-tomcat-4.0.1/webapps/rweb/.
     
     
  2. In a text editor, open the new LauncherHTML.jsp, which is in
     [Reflection management server installation]/jakarta-tomcat-[version number]/webapps/rweb/gm/.
     
     
  3. Copy your color, margin, and font settings from LoginPage.jsp into LauncherHTML.jsp.
     
     
  4. Save the JSP file.
     
     
• IIS Integration:
  
  If your previous installation of Reflection for the Web was integrated with IIS, the automated installer detected the integration and retained your settings. If you want to change those settings or if you installed using the archive files, open the IIS Wizard (Start > Programs > Attachmate Reflection for the Web > Utilities > IIS Wizard). For more information, see Running the IIS Wizard.) Enter the HTTPS port number, click Next, and then Finish.
  
  
• BEA portal integration:
  
  If you integrated Reflection for the Web version 6.x with your BEA portal, modify the existing code in your portlet JSP. The code to display a session is now:
  
  

  .....
<%= new com.wrq.java13plus.management.portal.RWebBrokerWLP().getContent(request, "<RWeb URL>/RWebSession.do?link=<Session name>&portal=true&appletOnly=true") %>
.....

  
  To display the end user links list:
  
  .....
<%= new com.wrq.java13plus.management.portal.RWebBrokerWLP().getContent(request, "<RWeb URL>/LoginPage.do&appletOnly=true") %>
.....