Reflection for the Web Reference Guide

Reflection for the Web is a standalone client that requires the Host Access Management and Security Server (MSS).

NOTE: In versions 13.2 and higher, Reflection for the Web no longer supports the use of Oracle’s JRE or the Java browser plug-in. Sessions are launched via the Reflection for the Web Launcher, which uses OpenJDK 8 JRE with Web Start (JNLP).

Given these changes, the Java/JavaScript bridge (LiveConnect) feature is no longer supported. For information about using an older version, see Reflection for the Web Documentation.

This Reference Guide includes introductory and advanced topics for use with Reflection for the Web 13.2.

In this guide:

How Reflection for the Web Works

Using Reflection for the Web and MSS, you can configure secure web-based terminal emulations sessions that connect to host applications located inside or outside the firewall.

Applets are downloaded to each user’s workstation as needed and are cached locally for faster performance. Sessions are centrally managed and secured using the MSS Administrative Console.

Briefly, here’s how Reflection for the Web works:

  1. An administrator installs Reflection for the Web on a web server and either installs or uses an existing installation of MSS

  2. The administrator uses the MSS Administrative Console to create, configure, and secure terminal emulation sessions. Optional security settings can be configured on a per-session basis.

  3. A user clicks a link to start a terminal session

  4. The Reflection for the Web emulation applet is downloaded to the user's workstation and is cached locally.

  5. The user connects to and communicates with the host system using the downloaded emulation applet.

  6. When the session is closed (Save/Exit), settings are sent to the Management and Security Server.