
Technical Notes |
|
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 2011 R1 Service Pack 1 released in February 2011. For more information, see Technical Note 2608.
This note is organized into the following sections:
Reflection for the Web 2011 includes the following new features.
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.
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 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.
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.
A new installation program includes configuration wizards that provide customization for new and existing installations. A new IIS 7 Integration Wizard is available.
In IBM 3270 and IBM 5250 emulations, you can now assign specific replacement characters for characters not included in the selected character set.
A report on LDAP access mapping, support for changing LDAP passwords, and support for LDAP dynamic groups has been added.
There are known issues with Reflection for the Web 2011. Problems and solutions are described in this section.
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 http://support.attachmate.com/manuals/rweb2011.html.
If you use the JBoss servlet runner, deployment requires the following additional steps:
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.
The example below shows a .sh file for the Enterprise version of Reflection for the Web.
rwebenterprise-11.0.<build number>-prod-unix-nojre.shrweb-prod-unix-nojre-manual.tar.gzrwebproxy-prod-unix-nojre-manual.tar.gzThe 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.
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.
C:\Program Files (x86)\ReflectionServer\jakarta-tomcat_001Use 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.
[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.
[MgmtServerInstall]/jakarta-tomcat-[version number]/webapps/rweb/ or
[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 http://support.attachmate.com/manuals/rweb2011.html) before proceeding.
Retain these files and directories (in addition to those listed above for all installation methods):
[MgmtServerInstall]/jakarta-tomcat-[version number]/webapps/rweb/WEB-INF/ 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.
[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.
This saves your server.properties file and your certificates.
[metering server installation]/jakarta-tomcat-[version number]/rwebmeter/WEB-INF/ [tomcat installation]/jakarta-tomcat-[version number]/conf/ Delete the directories in which you installed the previous version of the <prod_rweb> components.
Maintained customers are eligible to download the latest product releases from the Attachmate Download Library web site: https://download.attachmate.com/Upgrades/. For more information about logging into and using the Attachmate Download Library, see Technical Note 0200.
See Technical Note 2559 for an overview of the installation and upgrading options for Reflection for the Web 2011. Detailed instructions are available in the Installation Guide available from the Attachmate Support site: http://support.attachmate.com/manuals/rweb2011.html
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: http://support.attachmate.com/manuals/rweb2011.html.
Note that the documentation for all editions is the same; some of the documented features may not be available in your edition.
For an index of Reflection for the Web 2011 technical notes, see Technical Note 9988.