Attachmate Worldwide  |   Contact Us  |   The Attachmate Group
Extend. Manage. Secure. More than 30 years in the business. Over 65,000 customers.

Technical Notes

Installing Reflection for the Web 2008 on Windows Server 2008 64-bit
Technical Note 2536
Last Reviewed 14-Mar-2011
Applies To
Reflection for the Web 2008 (All Editions)
Summary

This technical note describes how to install, configure, and run Reflection for the Web 2008 on a 64-bit Windows Server 2008.

Reflection for the Web 2008 installs, runs, and is supported on Windows Server 2008 64-bit, but the automated installer is not 64-bit aware, so the product runs in 32-bit mode after the automated installer is complete. While following the steps in this technical note, you will be directed to download several files to use during the installation.

Note: Reflection for the Web 2011 automated installer supports 64-bit.

Topics in this technical note:

Configuring the Management Server

The following steps describe how to install, configure, and run the Reflection for the Web 2008 Management Server in 64-bit mode.

  1. Download and install a 64-bit version of the Sun Java Runtime Environment (JRE).

Note: 6.0 Update 20 (1.6.0_20) is used in the technical note.

  1. Use the automated installer to install Reflection for the Web:
    1. Install to C:\Program Files (x86)\ReflectionServer\
    2. If the Windows server is already running an IIS web server, IIS will be using ports 80 and 443. Tomcat cannot use those ports while IIS is using them. As an alternative, you can specify 8880 and 8443 for the Tomcat HTTP and HTTPS ports when prompted during the product installation. These ports will not conflict with IIS.

Note: During the install, IIS 7.x will not be detected and thus the option to integrate with IIS will not appear. Attachmate provides a utility that integrates the product with IIS 7.x after installation is complete.

Configuring Tomcat for 64-bit Mode

After completing the automated installation, Windows Task Manager will show “tomcat.exe *32” running. The *32 designation after tomcat.exe indicates that the process is running in 32-bit mode using the private 32-bit JVM that was added by the Reflection for the Web 2008 automated installer.

Follow the steps below to switch Tomcat to use the 64-bit JRE, thereby enabling the application to run in 64-bit mode.

  1. Download tomcat64.exe, which is a 64-bit service runner, and save it to the folder C:\Program Files (x86)\ReflectionServer\jakart-tomcat\bin.
  2. Launch the Windows Registry Editor (Start > Run regedit.exe) and navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Reflection Server

Warning: Before you work with the Windows registry, you should back up the registry on your machine.

Use the Windows Registry Editor (Regedit.exe) or another full backup program to back up your Windows registry. For information about the Windows registry, see the Microsoft Knowledge Base Article 256986:

http://support.microsoft.com/default.aspx?scid=KB;en-us;256986

  1. Edit the String entry named “Image Path” by double-clicking it.

In the Edit String box change the filename in the Value data field from tomcat.exe to tomcat64.exe. This entry tells Tomcat to use the 64-bit service runner. For example:

C:\Program Files (x86)\ReflectionServer\jakarta-tomcat\bin\tomcat64.exe
  1. In the Registry Editor, navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Reflection Server\Parameters
  1. Edit the String entry named “JVM Library” by double-clicking it. Change the value to point to the jvm.dll located in the 64-bit JRE installation.

Assuming a default installation location for the 64-bit JRE, the value will be C:\Program Files\Java\jre6\bin\server\jvm.dll. This value tells Tomcat to use the 64 bit JRE that was installed in Step 1.

  1. Edit the String entry named “JVM Option Number 0” by double-clicking it. Change the value to -Xmx1024m.

Note: Attachmate strongly encourages you to export the Reflection Server registry hive as a .reg file at this point. See Exporting or Importing from or to the Windows Registry for instructions. This practice will make upgrading your servers much easier. If the 64-bit JRE and Reflection for the Web are installed on your other servers in the same locations, the .reg file can be run on the other servers to automatically import the registry changes, thereby eliminating the need to edit the registry on your additional servers.

By using this approach, you can skip steps 2-6 on each additional server.

  1. Restart the Windows service for Reflection for the Web (named “Reflection Server”). Notice that Windows Task Manager now shows tomcat.exe running in 64-bit mode (the *32 is not designated after tomcat64.exe).

Launching the Administrative WebStation

You should now be able to access the Reflection for the Web 2008 Administrative WebStation by browsing to http://<host>[:port]/rweb/AdminStart.html, where <host> is the fully qualified domain name or the IP address of your Windows Server 2008 64-bit machine running Reflection for the Web. For example:

http://myserver.mycompany.com:8880/rweb/AdminStart.html

Note: If you are using Internet Explorer on a workstation or server that has a 64-bit Java browser plug-in, but does not have a 32-bit Java browser plug-in, then be sure to use “Internet Explorer (64-bit)”. You can launch “Internet Explorer (64-bit)” using the Start menu.

By default, all html shortcuts on Windows Server 2008 launch the 32-bit version of Internet Explorer, including the Administrative WebStation shortcut. If a 32-bit version of the Java browser plug-in is not installed on the system, you will not be able to access the Reflection for the Web login page, Administrative WebStation, or other Java content using the 32-bit version of Internet Explorer.

Note: To launch Reflection or INFOConnect thick client sessions from Reflection for the Web, you must use the 32-bit version of Internet Explorer along with a 32-bit version of the Java plug-in.

Configuring the Security Proxy Server

The following steps describe how to configure and run the Reflection Security Proxy Server in 64-bit mode.

Note: If you are installing the Reflection Security Proxy Server to the same server as the Reflection Management Server, skip this section and proceed to Configuring Security Proxy to Use 64-bit JRE.

  1. Download and install a 64-bit version of the Sun Java Runtime Environment (JRE). 6.0 Update 20 (1.6.0_20) is used in the technical note.
  2. Use the Reflection for the Web 2008 automated installer to install Reflection for the Web. Install the product to C:\Program Files (x86)\ReflectionServer\

Configuring Security Proxy to Use 64-bit JRE

After completing the automated installation, Windows Task Manager will display “secproxy_svc.exe *32”. Notice that Windows Task Manager shows a *32 designation after secproxy_svc.exe indicating that the process is running in 32-bit mode using the private 32-bit JVM that was added by the Reflection for the Web 2008 automated installer. Follow the steps below to configure the Security Proxy to use the 64-bit JRE, thereby enabling the application to run in 64-bit mode.

  1. Download secproxy_svc_64.exe, which is a 64-bit service runner, and save it to the following folder:
C:\Program Files (x86)\ReflectionServer\securityproxy\bin
  1. Launch the Windows Registry Editor (Start > Run regedit.exe) and navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Reflection Security Proxy

Warning: Before you work with the Windows registry, you should back up the registry on your machine.

Use the Windows Registry Editor (Regedit.exe) or another full backup program to back up your Windows registry. For information about the Windows registry, see the Microsoft Knowledge Base Article 256986:

http://support.microsoft.com/default.aspx?scid=KB;en-us;256986

  1. Edit the String entry named “Image Path” by double-clicking it. In the Edit String box change the filename in the Value data field from secproxy_svc.exe to secproxy_svc_64.exe. The path remains the same. This entry tells the Security Proxy to use the 64-bit service runner. For example: C:\Program Files (x86)\ReflectionServer\securityproxy\bin\secproxy_svc_64.exe
  2. In the Registry Editor, navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Reflection Security Proxy\Parameters
  1. Edit the String entry named “JVM Library” by double-clicking it. Change the value to point to the jvm.dll located in the 64-bit JRE installation.

Assuming a default installation location for the 64-bit JRE, the value will be C:\Program Files\Java\jre6\bin\server\jvm.dll.This value tells the Security Proxy to use the 64-bit JRE that was installed in the first step of Configuring the Security Proxy Server.

  1. Edit the String entry named “JVM Option Number 1” by double-clicking it. Change the value to -Xmx2048m.

Note: Attachmate strongly encourages you to export the Reflection Server registry hive as a .reg file at this point. See Exporting or Importing from or to the Windows Registry for instructions. This practice will make upgrading your servers much easier. If the 64-bit JRE and Reflection for the Web are installed on your other servers in the same locations, the .reg file can be run on the other servers to automatically import the registry changes, thereby eliminating the need to edit the registry on your additional servers.

By using this approach, you can skip steps 2-6 on each additional server.

  1. Restart the Windows service for the proxy (named “Reflection Security Proxy”). Notice that Windows Task Manager now displays tomcat.exe running in 64-bit mode (the *32 is not designated after secproxy_svc_64.exe).

You will now be able to run the Reflection Security Proxy Wizard using the Windows Start Menu. Note: To do this, you must right-click the shortcut and choose to run the application as Administrator.

Integrating Reflection for the Web 2008 with IIS 7.x (optional)

To integrate Reflection for the Web 2008 with IIS 7.x, on Windows Server 2008, see Technical Note 2543.

Exporting or Importing from or to the Windows Registry

Warning: Before you work with the Windows registry, you should back up the registry on your machine.

Use the Windows Registry Editor (Regedit.exe) or another full backup program to back up your Windows registry. For information about the Windows registry, see the Microsoft Knowledge Base Article 256986:

To export: Follow these steps to export a registry hive from the Windows Registry as a .reg file:

  1. Run the Windows Registry editor (regedit) and navigate to the location of the hive to be exported.
  2. Right-click the registry hive and then click “Export” on the context menu. The same technique can be applied to the Reflection Security Proxy registry hive.
  3. Select the location that you want to save to, a file name for the .reg file, and click the Save button.

To import: Follow these steps to import (merge) settings from a .reg file to the Windows Registry:

  1. To Import a .reg file into the Windows Registry, right-click the file and click Merge on the context menu (or simply double-click the .reg file).
  2. When prompted, click Yes to merge the information from the .reg file to the Windows Registry.
  3. Click OK on the prompt indicating that the keys and values were successfully merged.
  4. Open the Windows Registry (regedit) to confirm that that the values from the .reg file were merged.
  5. Restart the Reflection Server or Reflection Security Proxy for the imported registry values to take effect.

Installing Reflection for the Web 2008 Hotfixes

Follow these steps to install or upgrade a Reflection for the Web 2008 hotfix.

  1. Make sure that you export the appropriate registry hive of the product you are uninstalling. If you did this during the installation, then you can skip this step, proceed to step 2, and then later use the .reg file for step 4.

Warning: Before you work with the Windows registry, you should back up the registry on your machine.

Use the Windows Registry Editor (Regedit.exe) or another full backup program to back up your Windows registry. For information about the Windows registry, see the Microsoft Knowledge Base Article 256986:

http://support.microsoft.com/default.aspx?scid=KB;en-us;256986

  1. Uninstall Reflection for the Web using the Windows Control Panel – Programs and Features.

If prompted to remove isapi_redirect.dll or any other existing file(s) click “No to All.”

  1. Install the hotfix following the installation procedure described in the appropriate section above: Configuring the Management Server or Configuring the Security Proxy Server.

If prompted to replace isapi_redirect.dll or any other files click “No to All.”

  1. Use your saved .reg file to merge the necessary registry changes for the product into the Windows Registry. See Exporting or Importing from or to the Windows Registry for information on importing registry settings.
  2. Restart the appropriate service (Reflection Management Server or Reflection Security Proxy) for the application to which you just applied the hotfix.
Related Technical Notes
9988 Reflection for the Web Technical Notes

horizontal line

Did this technical note answer your question?

           


Need further help? For technical support, please contact Support.