Technical Notes |
|
This technical note provides a step-by-step guide to evaluating Reflection for the Web 2008. Use this note along with the Reflection for the Web Installation Guide.
Reflection for the Web is terminal emulation software that connects browser users to host applications located inside or outside the firewall. Briefly, here’s how it works:
For a list of the new features in Reflection for the Web 2008, see Technical Note 2345.
For an overview of what components are included in each of the five Reflection for the Web 2008 editions, see Technical Note 2321.
This technical note provides a recommended path for installing and evaluating Reflection for the Web 2008, but you can select other features along the way.
Here’s the suggested path:
Depending on your environment, the steps to install Reflection vary. Before you install Reflection for the Web 2008, we recommend that you check the system requirements and read the guidelines in this section.
The 60-day time-limited evaluation copy of Reflection for the Web 2008 is available from the Attachmate web site. To request a copy, follow the instructions on the Evaluation web page: http://www.attachmate.com/Evals/rweb/eval-form.htm.
Before installation, identify the computer you will use to evaluate Reflection for the Web 2008 and check the system requirements. Then, browse through the Installation Guide, which you will use along with this technical note.
The Reflection for the Web Installation Guide is available from these locations:
Attachmate Support site: On http://support.attachmate.com/manuals/rweb2008.html, click Reflection for the Web 2008 Installation Guide.
Reflection for the Web product: After installing, at the root of the Reflection for the Web installation (typically \ReflectionServer), click installguide.html.
To avoid file conflicts, install the evaluation copy of Reflection for the Web 2008 to a machine that does not have Reflection for the Web installed.
(To check your current version of Reflection for the Web, open the Administrative WebStation and click Resources > About Reflection for the Web.)
For initial testing, you can install Reflection for the Web 2008 on a workstation; however, Attachmate recommends installing Reflection for the Web 2008 on a server operating system for production. The installation process is the same whether you install to a workstation or a server. This technical note refers to installing on a server.
For evaluation purposes, install all of the Reflection components onto the same computer using the automated installer. That computer should meet the following minimum hardware and software requirements:
| Server |
256 MB RAM 230 MB disk space TCP/IP connection (for the end user) |
| Operating system |
Reflection for the Web is platform independent, and automated installers are available for Windows, Solaris, HP-UX, Red Hat, SUSE, and Mandriva (Mandrake) Linux. Note: A graphical interface is needed for the non-Windows automated installers. |
| Java Virtual Machine (JVM) |
Java 2 Virtual Machine (JVM) 1.4 or higher capable of running Java applications; Java 1.1 with the Microsoft VM is also supported. For more information, see Technical Note 1674. |
| Servlet runner |
Use the Tomcat servlet runner that auto-installs with Reflection for the Web 2008. |
| Web browser |
Any Java 2 (JVM) 1.4 (or higher) compliant web browser that can run trusted applets and supports JavaScript, cookies, and cascading style sheets. For detailed browser requirements, see Technical Note 1383. |
| Other Reflection software |
No previous version of Reflection for the Web installed. To avoid file conflicts, install the evaluation copy of Reflection for the Web 2008 to a machine that does not have Reflection for the Web already installed. |
For an itemized list of the system requirements for each Reflection component and for the end users’ computers, see the Installation Guide: Preparing to Install > System Requirements.
After you check for compatible system requirements, read through these general guidelines:
For details about configuring Reflection in these environments, see Technical Note 2195.
Use the Automatic Installation Checklist in the Installation Guide to identify the system-specific information that you must enter (or accept) during installation.
In the Installation Guide, click Installing Reflection > Automatic Installation Checklist. Print the page to record your choices as you install Reflection for the Web.
For evaluation purposes, run the automated installer once to install all of the components onto the same computer at the same time. For screen-by-screen instructions on running the installation wizard, see the Installation Guide: Installing Reflection for the Web > Automatic Installation Procedure.
Note: Running the auto-installer on Linux requires "execute" permission.
Note: You will see an explanation about the temporary self-signed certificate that was created during installation. The temporary certificate enables you to access the Reflection for the Web server securely until you are able to obtain a certificate signed by a recognized certificate authority.
During the automated installation, the following components are installed onto the designated computer:
When you purchase Reflection for the Web 2008, you may decide to install some components onto different machines. To install components on different computers, run the installer more than once to select the appropriate components.
Although the automated installation is recommended for evaluation purposes, you can use the manual installation procedures if either of these conditions applies:
For detailed procedures, see the Installation Guide: Installing Reflection > Manual Installation Procedures. For more information about installing Reflection for the Web on UNIX or Linux, see Technical Note 1699. On Mac OS X, see Technical Note 2343.
If you would like technical assistance while installing or configuring your evaluation copy of Reflection for the Web 2008, please contact Attachmate Technical Support. See http://support.attachmate.com/contact/ for contact information.
Once Reflection for the Web 2008 is installed, begin with the Administrative WebStation to evaluate the product features.
The Administrative WebStation is a centralized web site that contains administrative tools and documentation. You can configure, secure, deploy, and monitor terminal sessions from this central location. The WebStation is password-protected to allow for remote administration and access by multiple administrators.
Follow these steps to start the Administrative WebStation.
If Tomcat was installed as a Windows service, Windows starts it automatically. Continue with step 2.
If Tomcat was not installed as a Windows service, then in Windows, click Start > Programs > Attachmate Reflection for the Web > Start Servlet Runner.
If a non-Windows (UNIX, Linux, Solaris, or HP-UX) auto-installer was used, then start Tomcat by running
<Reflection Server Installation>/Jakarta-Tomcat/bin/startup.shNote: The machine from which you are accessing the Administrative WebStation must have a Java Virtual Machine (JVM) installed for the browser. To determine if the machine has a JVM, see Technical Note 1674.
If you are using Windows, click Start > Programs > Attachmate Reflection for the Web > Administrative WebStation.
If you are accessing the Administrative WebStation from a machine other than the web server, or if you are using UNIX, Linux, or Mac OS X to access the Administrative WebStation, open your web browser and in the Address field, enter the appropriate URL for your configuration. Replace the <server name> and <port#> entries with your site-specific information:
For HTTPS:
https://<server name>:<SSL port#>/rweb/AdminStart.htmlFor HTTP:
http://<server name>:<http port#>/rweb/AdminStart.htmlNote: You may see a security alert about the temporary self-signed security certificate created during installation. Click Yes to proceed.
Depending on the specific message, select "Run" or "Grant this session." If you do not want to see this alert again, select "Always trust content from this publisher."
Click Administrative WebStation.
Note: To navigate through the Administrative WebStation, use the Reflection navigation buttons and links rather than using your browser’s Back button.
From the home page, you have access to the tools to create, configure, and manage terminal sessions. The WebStation also provides a wealth of introductory information, tutorials, and other references.
Reflection for the Web 2008 connects users to IBM 3270, IBM 5250, VT, HP, UTS, T27, and ALC host applications using a series of Java-based applets. Applets are downloaded to the user’s PC as needed and cached locally for faster performance.
For an at-a-glance look, try one of the preconfigured Reflection sessions.
Reflection for the Web automatically detects your browser type and downloads the files you need to initiate a connection.
The end-user menu level for the preconfigured session is Administrator, and all of the menu options are enabled. When you create your own terminal sessions for end users, you can control the menu access.
Look for details about configuring Reflection settings in a later section.
Note: The preconfigured sessions are embedded in a browser page, and the menu options are available by using the right mouse button. When a session is configured to display in a separate window, the menu options appear in a menu bar.
For details about opening the WebStation remotely on a different operating system, starting the servlet runner, or using passwords, see the Installation Guide: Starting the Administrative WebStation.
Now, continue evaluating Reflection for the Web 2008 by creating and configuring at least one terminal session.
Use the Session Manager in the Administrative WebStation to create and configure the Reflection terminal sessions you want to deploy to end users.
Follow these steps to create terminal sessions.
Note: If you are using both web- and Windows-based Reflection, you can manage all of your sessions from the Administrative WebStation. However, this technical note explains only the web-based sessions.
Click Continue.
If you want to test the connection to the host, enter the name of your host computer and click OK. Or, click Cancel when prompted for the host name.
Now you are ready to configure the emulation settings for the end-users’ Reflection terminal session.
Test the emulation features in a launched Reflection session. (You do not need to be connected to the host to configure settings.)
Note: When you, as an administrator, launch a session from the WebStation, all of the menu options are visible and enabled. The end users, however, are able to access only the menu options filtered by the End user menu level selected in the Profiler, which is described below. (The default is Basic.)
Try some of these commonly used features:
The Reflection for the Web profiler can be used the to restrict access to entire menus, dialog boxes, toolbars, or to specific items within them. To experiment with these access levels, go to the Profiler, which is accessed from the session menu:
For more information about configuring user menu levels, see Technical Note 2186.
In the terminal session, click the Setup menu to modify display features. Then follow the logical navigation, which varies among session types.
For example, to change foreground and background screen colors, you might click Setup > Color.
To create a custom keyboard mapping, click Setup > Keyboard > Add. Follow the directions in the dialog box to create a custom keyboard mapping, or click Help for more details.
To select which settings the end users can (and cannot) change and save locally:
Note: End users save their local setting changes by clicking File > Save Preferences. The settings are stored on the user workstations in a preference file.
Several printing options are available in any Reflection terminal session from the File menu:
Specific printer setups:
Reflection for the Web can perform the following data transfers:
To launch the FTP session you just configured, click File > FTP. (In 3270 sessions, click File > Transfer > FTP.)
Note: FTP needs to be enabled in this session. If you did not enable FTP when you configured this session, you need to return to the Session Manager. Follow these steps:
To launch the IND$FILE session you just configured, click File > Transfer > IND$FILE or File > IND$FILE.
For information about using the IBM AS/400 Data Transfer session, click Help in the launched Data Transfer session window.
When you are finished configuring the emulation features in Reflection, save the session by clicking File > Save and Exit. This session is then added to the Session Manager list in the Administrative WebStation but not to the end user's list of available sessions.
The Session Saved page provides the URL for the session and links to the Access Mapper and the Session Manager pages.
At this point, you have several options:
Now that you have created and configured at least one terminal session, you are ready to deploy the session(s) to end users. Use the Access Mapper to specify the sessions you want to appear on the end users' links list.
Note: If the Session Saved page is still open (from the previous step), you can click the "Map session access" link to open the Access Mapper.
Reflection also enables you to deploy specified sessions to a subset of end users. To assign sessions to a specific user or group, use the advanced options, described next, for controlling authentication and access control.
Reflection for the Web provides tools for using optional and advanced features. This section provides a brief description of the following features:
Reflection for the Web supports a variety of access control models. For instance, if your environment uses an LDAP-compatible directory service, you can use your existing LDAP database to map terminal sessions to users, groups, or folders.
For information about the authentication options, see these resources:
By default, Reflection for the Web enables web browsers to use the HTTP protocol to communicate between the client computer and the management server. Although HTTP is universally available to web browsers, it is not a secure protocol.
To secure the communication between the client and the web server, you should require web browsers to use the HTTPS protocol (which provides SSL encryption) when connecting to the Reflection for the Web management server. HTTP is enabled by default. For more information, read the Security overview in the Administrative WebStation: Overviews > Overview > Security.
Security is increased by using the Reflection security proxy to encrypt the data between the client and the security proxy. You can install the security proxy when you run the automated installer. For more information about using the security proxy, see these resources:
Usage metering can be used to audit and control access to both Windows- and Web-based Reflection sessions. You may want to install Reflection for the Web's usage metering component if your site needs to carefully balance network and server loads. For more information, see these resources:
Earlier, when you created and configured your terminal sessions, you were able to make some preliminary customization choices. Reflection for the Web also includes a well-documented API and some advanced tools that make it easy to customize terminal sessionseven if you don't have Java or HTML programming experience.
For instance, see Technical Note 1807 to learn how to use the personalization feature. See Technical Note 9988 for links to more information about customizing Reflection for the Web.
In the Administrative WebStation under Reference, click Advanced in the left-navigation bar. Then, click the links to find out how to use scripts, HTML code, and applet parameters with Reflection.
The following example demonstrates how you can customize the behavior of a terminal session by changing the parameters for a specific attribute.
Edit an applet tag to disable the Reflection for the Web start-up (splash) screen that normally appears when a terminal session is starting.
For information about applet attributes and parameters used in Reflection, see Administrative WebStation: Advanced > Applet Parameters.
There are many resources available to help you install, configure, and troubleshoot Reflection for the Web 2008.
Click Resources for links to a Glossary, Troubleshooting topics, System Requirements, and version information (in About Reflection).
The technical notes for Reflection for the Web are listed in Technical Note 9988.
Reflection for the Web 2008 documentation is included in the product and online at http://support.attachmate.com/manuals/rweb2008.html.
To request technical support, see http://support.attachmate.com/contact/ for contact information.
To purchase Reflection for the Web 2008 or to request a Proof of Concept, contact Attachmate Sales at 1.800.872.2829 or e-mail us at SalesRecept@attachmate.com.
Before you install the fully-licensed version of Reflection for the Web 2008, you must uninstall the evaluation copy.
Your sessions and settings will be retained. But, if you wish to remove all the sessions and settings, delete the ReflectionServer folder and its sub-folders on the designated machine.
For Windows platform: Follow the steps below.
For UNIX/Linux: Run the following shell script.
<installation directory>/utilities/uninstaller.sh