When a user requests a Reflection URL, Reflection for the Web dynamically generates a web page containing a launcher applet that loads the module named by the launcher.sessions parameter. The launcher.sessions module determines which tools or sessions to run and presents the appropriate page.
When a user selects the Reflection base URL, the launcher applet loads the request manager client module. The module checks with the server to determine if a login is required and if so, presents the login form. After the user logs in, the module presents the customized list of links. When the user clicks a link for a session that appears in its own window, the same module creates a child window in which the emulator session appears. When the user clicks a link for an embedded session, on the other hand, Reflection generates a new browser window with a new launcher applet and a different module—the terminal session itself.
You can change emulator session behavior by using Manage Sessions to add parameters to the session applet tag. These session-specific parameters are added to embedded sessions when they are launched in new browser windows, and to sessions that appear in their own window ("framed" sessions) when they're launched from the links list.
Launcher parameters (such as launcher.keepalive and launcher.sessions) apply to the module-launching applet and not to the module itself. Because these parameters are applied only when the launcher applet first loads and framed sessions are children of the initial launcher module, launcher parameters cannot be set for specific framed sessions.
Define the contents of the session web page using Manage Sessions.
Customizing applet page presentation
See the HTML Samples for instructions on how to customize an applet page and examples of HTML code to run Reflection applets.
Applet security
A Java applet is required to follow security rules, which limit the applet's access to a user's computer.
Related Topics