Reflection for the Web 2011 New Features and Release Notes

  • 7022044
  • 02-Jun-2011
  • 25-Mar-2018


Reflection for the Web 2011 (All Editions)


This technical note lists the product enhancements in Reflection for the Web 2011, and includes release notes about known issues and additional resource information.

Note: Reflection for the Web 2014 released in October 2013. For more information, see KB 7022047.


This note is organized into the following sections:

New Features in Reflection for the Web 2011
Known Issues
Obtaining Reflection for the Web 2011
Installing or Upgrading to Reflection for the Web 2011
Additional Resources

New Features in Reflection for the Web 2011

Reflection for the Web 2011 includes the following new features.

  • File Transfer Requests

You can now create a file transfer request for transfers that you execute repeatedly. File transfer requests are available for FTP, including the FTP support within most emulation types, IND$FILE, and IBM AS/400 Data Transfer.

  • Customizable toolbar

You can change the layout of toolbars, including removing or adding toolbar buttons. You can associate a button with an action, such as running a file transfer request or running a script.

  • ID Management

ID Manager provides IDs to client applications at runtime. Run the ID Manager server to set up ID management. Additional settings for ID management are in the Administrative WebStation and in individual client sessions.

  • Editable macros, built in Script Editor

There are additional macro and scripting capabilities in Reflection for the Web 2011. Recorded scripts are now saved as JavaScript, and can be edited using the built-in Script Editor. In addition, an attachment class developed with the Reflection for the Web Java Emulator Class Library (ECL) API can be assigned as the automated sign-on macro for the session, allowing administrators to automate much more complex sign-on tasks than was previously possible.

  • New Setup Program

A new installation program includes configuration wizards that provide customization for new and existing installations. A new IIS 7 Integration Wizard is available.

  • Customized copy/paste replacement characters

In IBM 3270 and IBM 5250 emulations, you can now assign specific replacement characters for characters not included in the selected character set.

  • LDAP enhancements

A report on LDAP access mapping, support for changing LDAP passwords, and support for LDAP dynamic groups has been added.

Known Issues

There are known issues with Reflection for the Web 2011. Problems and solutions are described in this section.

When Deploying Reflection for the Web to a JBoss Servlet Runner, Reflection Fails to Deploy

Reflection for the Web installs Tomcat as the default servlet runner. Other servlet runners are supported and installation using other servlet runners is described in the Reflection for the Web Installation Guide, available from

If you use the JBoss servlet runner, deployment requires the following additional steps:

  1. Extract the contents of the WAR file using a tool such as WinZip.
  2. Remove the following JAR files from WEB-INF/lib:
  1. Zip the remaining contents back into a WAR file. The new WAR file can now be deployed and will run with the JBoss servlet runner.

Installing on Other UNIX Platforms

The following installation files are available with Reflection for the Web to support platforms that require a version of a Java runtime environment other than the one provided by the installer. Platforms that may use these files include z/OS, Mac, and other UNIX/Linux systems.

Automated Installer

The example below shows a .sh file for the Enterprise version of Reflection for the Web.

rwebenterprise-11.0.<build number>

Manual installer


Manual Installer for Security Proxy only


Installation Procedure

  1. To use any of these packages, confirm that a Java runtime environment appropriate for your platform is already installed.
  2. Expand the package you want to use as described in the Installation Guide.

The only difference in these packages from those documented in the guide is the absence of a JRE. This allows the Java version installed on your platform to be used during installation.

“Unable to rename folder” Message Displays When Running Configuration Upgrade Utility

You may see a warning message such as the following when running the Configuration Upgrade Utility:

 WARNING: Unable to rename C:\Program Files (x86)\ReflectionServer\jakarta-tomcat to C:\Program Files (x86)\ReflectionServer\jakarta-tomcat_001. The most likely causes are a permissions problem, or that the file or path is in use by another process.

This warning message occurs if you use a different user account to upgrade Reflection for the Web than the one used to install the previous version, and Windows UAC (user account control) is being used to elevate installer privileges.

Your new version of Reflection for the Web 2011 will be appropriately configured and will run without problems even if you see this message. However, we recommend that you rename this directory to ensure that any subsequent operations with the Configuration Upgrade utility will operate as expected.

  1. Locate C:\Program Files (x86)\ReflectionServer\jakarta-tomcat or the equivalent on your machine.
  2. Change the folder’s name to the target value seen in the WARNING message, for example:
C:\Program Files (x86)\ReflectionServer\jakarta-tomcat_001

Upgrading from Manually Installed Versions Reflection for the Web 9.x or Reflection for the Web 2008:

Use the information below to upgrade from a manually installed version of Reflection for the Web. This information replaces the text in Upgrading from Manually Installed Versions in the Installation Guide.

Step 1: Back up customized files

  • Copy and save cacerts in the
[MgmtServerInstall]/_jvm/lib/security/ directory.

You may have the cacerts in a location associated with a JDK install. Other locations may be the /_jvm/lib/security or /jre/lib/security directory of the JDK installation used by Reflection for the Web. In any case, locate this file and make a separate copy of it.

  • Copy and save any files that you customized in these directories:
[MgmtServerInstall]/jakarta-tomcat-[version number]/webapps/rweb/


[MgmtServerInstall]/jakarta-tomcat-[version number]/webapps/rweb/gm/

If you have replicated servers in your environment, see the information in Additional Upgrade Modifications in the Installation Guide (available from before proceeding.

Step 2: Uninstall Reflection for the Web 9.x or Reflection for the Web 2008 Components

Retain these files and directories (in addition to those listed above for all installation methods):

Reflection Management Server

  • Copy and save the earlier version of the web.xml file located here:
[MgmtServerInstall]/jakarta-tomcat-[version number]/webapps/rweb/WEB-INF/
  • Copy and save the earlier version of the ReflectionData directory.

The default location of ReflectionData in Reflection for the Web 2008 is as follows:

On Windows XP and Windows 2003: C:\Documents and Settings\All Users\Application Data\ReflectionServer\ReflectionData

On other supported Windows systems: C:\ProgramData\Attachmate\ReflectionServer\ReflectionData

On UNIX and Linux: /var/opt/attachmate/reflectionserver/reflectiondata

Note: These defaults are not directly specified in the web.xml file; instead, a value of rwebdata_location_placeholder for the ReflectionData parameter in web.xml generates the appropriate defaults for the platforms listed above.

If you specified a custom location for ReflectionData or are upgrading from a version previous to Reflection for the Web 2008, open web.xml and locate the ReflectionData parameter to identify the path.

This folder must be backed up in a location that is not referenced by any upgrade or configuration procedure. This will assure that you have an independent validation of these settings.

  • Copy and save the earlier version of any unprotected, static sessions located here:
[MgmtServerInstall]/jakarta-tomcat-[version number]/webapps/rweb/session/

These sessions may also be saved in other directories within the webapps directory. See Upgrading Static Sessions in the Installation Guide for more information.

Security Proxy Server

  • Copy and save the earlier version of these directories:
[security proxy installation]/conf/
[security proxy installation]/keystores/

This saves your file and your certificates.

Metering Server

  • Copy and save the earlier version of the web.xml file located here:
[metering server installation]/jakarta-tomcat-[version number]/rwebmeter/WEB-INF/

Servlet Runner

  • Copy and save the earlier version of the Tomcat keystore located here:
[tomcat installation]/jakarta-tomcat-[version number]/conf/

Delete the directories in which you installed the previous version of the <prod_rweb> components.

Obtaining Reflection for the Web 2011

Maintained customers are eligible to download the latest product releases from the Attachmate Download Library web site: For more information about logging into and using the Attachmate Download Library, see KB 7021965.

Installing or Upgrading to Reflection for the Web 2011

Information about the installation and upgrading options for Reflection for the Web 2011 is provided in the Installation Guide available from the Attachmate Support site:

Additional Information

For more information about Reflection for the Web 2011, see the following resources:


Reflection for the Web 2011 Installation Guide is available on the Attachmate Support site:

Note that the documentation for all editions is the same; some of the documented features may not be available in your edition.

Technical Notes

For an index of Reflection for the Web technical notes, see

Legacy KB ID

This document was originally published as Attachmate Technical Note 2557.