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.
You can change emulator session behavior. Use Manage Sessions to add session-specific parameters to the session applet tag.
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.
Applet security
A Java applet is required to follow security rules, which limit the applet's access to a user's computer.
Related Topics