action.skip

J-K-L

jceprovider

This parameter specifies an alternative JCE provider for an SSH session. Use this parameter if you have a VT session that runs over a FIPS certified SSH connection. In this case, use the value "JsafeJCE" to invoke the RSA Jsafe crypto module. This value is case sensitive. If the JsafeJCE provider is successfully loaded, information in the Java console will indicate whether the module was loaded and if it is in FIPS-140 mode. If you do not use the correct case, the module will still load, but the client won't be able to connect, and you'll see this exception in the java console: kSecurityFactoryNoSuchProvider?com.wrq.fipsmodule.resources.Resources

Value

A valid JCE provider name. The default, "", uses JCRYPTO.

Example

<param name="jceProvider" value="JsafeJCE">

launcher.keepalive

This parameter determines the behavior of the session applet when the user browses away from the page that launched the applet.

Note

The browse-away behavior of sessions accessed from the Reflection links list and that launch in their own window is controlled by the launcher.keepalive parameter for the links list applet itself, so changing the value of this parameter in the Administrative Console session management panel will not have any effect on these sessions.

If the value of launcher.keepalive is framed (the default when you are not using a portal for authentication), sessions remain open when the user browses away from applet page.

If the value is all, sessions remain active when the user browses away from the applet page or closes the browser window containing the applet (unless the window closed is the only browser window remaining, in which case the session is closed). Users can navigate back to the session and resume work.

A value of portal (the default when you are using a portal for authentication) results in the same behavior as all, with additional optimizations for a portal environment.

To close sessions when the user browses away from the applet page, set the launcher.keepalive parameter to none, and also set the parameter legacy_lifecycle to false. The legacy_lifecycle parameter is processed by both Reflection and the Java plug-in itself, and a value of false will allow the plug-in to terminate the applet upon browse-away

Value

framed (default for non-portal sessions)

none

all

portal (default for portal sessions)

Example

<param name="launcher.keepalive" value="none">

launcher.sessions

This parameter launches a session of the type specified. This parameter is case-sensitive.

  • HP
  • IBM3270
  • IBM3287 (for IBM 3270 printer sessions)
  • IBM5250
  • IBM3812 (for IBM 5250 printer sessions)
  • IBM5250Xfer (for AS/400 data transfer sessions)
  • VT
  • UTS
  • T27
  • T27 Printer (for T27 printer sessions)
  • ALC
  • ePrint

Example

<param name="launcher.sessions" value="IBM3270">

launcher.splash

This parameter determines whether the Reflection splash screen is displayed while Reflection is loading. The splash screen includes a progress indicator, so the loading progress is not displayed when the splash screen is suppressed.

Value

true (default)

false

Example

<param name="launcher.splash" value="true">

loadJavaClassName

This parameter specifies the name of a Java "attachment class" to insert into the Load Java Class dialog box when it first opens. This lets you provide a default Java attachment class, without requiring users to remember the class name.

Java attachment classes are a feature of the Reflection Emulator Class Library (ECL) that allow Java code to attach to the currently running terminal session and perform automated tasks. If you write your own Java attachment class, it must be packaged into a user archive file, and the userArchive parameter must be used to specify the name of the archive file. If you use an attachment class built into Reflection, you do not need to add the userArchive parameter when specifying a startup Java class. Java attachment classes must implement the interface ECLAppletInterface.

Value

<a fully qualified Java class name>

Example

<param name="loadJavaClassName" value="com.mycorp.reflection.MyAutomatedTask">

loadUserPrefs

This parameter determines whether user preferences are loaded when a user starts a Reflection session and a preferences file exists for that session. There is more information about user preferences in the Management and Security Server documentation, Configuring Reflection: User Preferences.

Value

true (default)

false

Example

<param name="loadUserPrefs" value="true">