action.skip

G-H-I

GenerateUniqueDeviceName

This parameter is valid for IBM 3270 emulator, IBM 3270 printer, IBM 5250 emulator, and IBM 5250 printer sessions. When the parameter is set to true and no device name is specified in the configuration file or the Session Setup dialog, Reflection generates a unique device name when a connection to the host is initiated. The name is based on the machine name or the user's IP address.

Value

true

false (Default)

Example

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

Height

The required height attribute controls the initial height of the session applet in the browser window. The height is measured in pixels. When the frame parameter is set to true, use the frameheight parameter to set the height of the separate Reflection terminal window.

Example

<applet mayscript name="IBM3270"
        code="com.wrq.rweb.Launcher.class" 
        width="400" height="300">
</applet>

Heartbeat

A periodic “heartbeat” is maintained between the applet that launches the client and the Management and Security Server to prevent the server from timing out due to inactivity. If a heartbeat between the client and server is not maintained, configuration work can be lost when the inactivity timer expires.

To prevent the loss of work when undergoing lengthy configurations, such as keyboard mappings or macros, you can modify the heartbeat services that affect session management and the links list.

Note

If you use SiteMinder (or something similar) to control access to terminal sessions, see Using Crumb Mode (below) to set a heartbeat.

Management and Security Server heartbeat

When you are configuring Reflection for the Web sessions in MSS, a heartbeat is automatically sent to the server every 3 minutes to keep the MSS Administrative Server from timing out. To change this default or to modify other heartbeat behavior, you can add parameters on the Configure Session panel.

  1. Open launchsession.jsp, located here with a default installation:C:\Program Files\Micro Focus\MSS\server\web\webapps\mss\aws\smt\launchsession.jsp

  2. In launchsession.jsp, locate the section that begins with .

  3. Add the parameters you want to set. See the available Heartbeat parameters, described below.

    For example, to change the heartbeat interval from 3 minutes to 5 minutes, add the following parameter:<rweb:param name="HeartbeatInterval" value="5"/>

Note

Edits to launchsession.jsp may be overwritten when you upgrade Reflection for the Web or Management and Security Server.

The list of links does not, by default, maintain a heartbeat with the server. Users are automatically logged out of the Management and Security Server after 60 minutes if they are not actively using the links list.

To enable a heartbeat for the links list, you must modify the source of the login page. It is recommended that you make backup copies of both the original and modified login pages because any modifications will be overwritten by product upgrades.

  1. In your login page, locate the section that begins with <mss:applet userequest="true"/>.

  2. Add the heartbeat parameters you would like to set.

Hearbeat parameters

You can add these parameters to the MSS applet and/or the links list applet to modify the default heartbeat behavior. Use the basic syntax:<mss:param name="name" value="value"/>.

  • enableHeartbeat – Enables the heartbeat. The default for Session Manager is true. The default for the links list is false.

  • adminHeartbeatOnly – Enables the heartbeat only for a user logged in as the administrator. Applies only to the links list and only when “enableHeartbeat” is true. The default is false (links list heartbeat will apply to both users and administrators).

  • heartbeatInterval - Specifies the interval between heartbeats, in minutes. The default is 3 minutes, the minimum is 1 minute, and the maximum is 720 minutes (12 hours).

  • heartbeatMax – Specifies the maximum lifetime of the heartbeat, in minutes. The default is 0, which lets the heartbeat run indefinitely. The maximum is 720 minutes (12 hours).

  • heartbeatRetry – Specifies the maximum number of consecutive failed heartbeats before the heartbeat is stopped permanently. The default is 5, the minimum is 1, and the maximum is 100.

  • heartbeatCrumbMode – Indicates whether to use “servlet request mode” or “crumb mode” for heartbeat operations. The default is false, and the heartbeat operates in “servlet request mode”. If set to true, an additional parameter, “heartbeatCrumbFilename”, can be set to specify the name of the “crumb” file if the default filename of “crumb.txt” is not desired. See Using Crumb Mode.

Using Crumb mode

If you use SiteMinder (or something similar) to control access to terminal sessions, you can set the heartbeat to operate in “crumb mode” instead of the default “servlet request mode”. In servlet request mode, the emulator client makes a request to the servlet to maintain activity. In crumb mode, heartbeat requests are sent to fetch a crumb of data from the codebase directory on the Management and Security Server.

The crumb of data is simply a text file called crumb.txt, and the file contents must be only the string ok. You must create the crumb file manually and place it in the applet codebase directory. In a default installation, locate the directory here: C:\Program Files\Micro Focus\MSS\server\web\webapps\mss\ex

Access management products, such as SiteMinder, record the heartbeat crumb request as activity to prevent session timeouts, whereas they may not record activity generated by heartbeats in servlet request mode. Crumb mode does not maintain Management and Security Server activity.

Two parameters control crumb mode: heartbeatCrumbMode and heartbeatCrumbFilename, described above. The following example shows how crumb mode may be enabled in the links list and configured to use an alternate crumb file:

<mss:applet userequest="true">
   <mss:param name="heartbeatCrumbMode"value="true"/>
   <mss:param name="heartbeatCrumbFilename"value="mycrumb.txt"/>
</mss:applet>

helpbase

This parameter specifies the path to the starting folder of the Reflection online help for the terminal session. The value should be formatted as a URL. If this parameter is not specified, Reflection uses the URL specified in the Codebase applet attribute to find the starting folder

If a relative URL is specified, Reflection starts searching for the page from the Ex folder in the terminal emulation component. By default, Reflection looks in the Help folder (considered the starting folder), installed at the same level as the Ex folder.

Value

http://<terminal emulation component installation>/ (Default) <any valid URL>

Example

<param name="helpbase"
       value="http://Reflection.example.com/RWebHelp/">

hostURL

This parameter can be used to specify three values: transport, host, and port. These values are named using the following syntax: transport://host:port.

You can define all or part of the hostURL. If you omit the host name, a dialog box prompts for a host when the session starts; if you omit the port or transport, Reflection automatically includes default values. The default value for the transport is determined by the transport parameter if one is specified. Otherwise, the transport and the port are both selected from Reflection program defaults. If you know which transport or port you need, however, it is recommended that you specify them in this parameter instead of depending on the defaults.

Note

The recommended method for configuring most settings is to use the dialog box equivalents where available. In these cases, parameters should be restricted to scripted sessions. The equivalent setting for the hostURL parameter is Host.

Values

  • IBM 3270

    : tn3270 and tn3270e :// tn3270 or tn3270e:// tn3270 or tn3270e://: tn3270 or tn3270e://: demo://ibm3270

  • IBM 3270 Printer - The default port number for the tn3270e transport is 23. The port may be different for your organization. To change the default, specify the port number in this parameter.

    : tn3270e:// tn3270e:// tn3270e://: tn3270e://:

  • IBM 5250 / IBM AS/400 Printer

    : tn5250:// tn5250:// tn5250://: tn5250://: demo://ibm5250

  • IBM AS/400 Data Transfer - The transport and port values are not used for IBM AS/400 data transfer; only the host name or IP address is used. <host name or IP address>

  • HP

    : nsvt or telnet:// nsvt or telnet:// nsvt or telnet://: nsvt or telnet://: demo://HP3000 demo://UNIX

  • VT

    : telnet:// telnet:// telnet://: telnet://: demo://digital demo://UNIX

  • UTS

    : int1, airgate, matip, pepgate:// :

  • T27 and T27 Printer

    : tcpa:// tcpa:// tcpa:// tcpa://:

  • ALC

    : lantern airgate, matip, atscp, sabre,tcpfrad, udpfrad :// :

Example

The transport, host, and port are all specified: <param name="hostURL" value="tn3270://jupiter:23">

Only the host is specified, and the default transport and port are used: <param name="hostURL" value="jupiter">

The transport and host are specified, and the default port is used: <param name="hostURL" value="tn3270://jupiter">

The host and port are specified, and the default transport is used. <param name="hostURL" value="jupiter:23">

hphelptoc

This parameter redirects the Help Topics command in the Help menu for HP terminal sessions to the specified URL.

Value

http://<terminal emulation component installation>/help/hphelp.html (Default)<any valid URL>

Example

<param name="hphelptoc"
        value="http://ReflectionWeb.example.com
                    /customHelp/hphelp.html">

httpsProxy

Use this parameter to specify the port and name or IP address of a secure HTTP proxy to use while running encrypted Reflection sessions. The secure HTTP proxy specified in this parameter overrides any secure HTTP proxies that are set in the browser's properties.

You can use the httpsProxy parameter in combination with the proxyExcept parameter to bypass authentication schemes on HTTP proxies that are not supported in Reflection. The httpsProxy parameter overrides the browser settings and then the proxyExcept parameter overrides the setting for Reflection sessions. The Reflection session--encrypted using the Reflection security proxy server--can then pass directly through the firewall (an opening must be made in the firewall).

When the httpsProxy parameter is used without the proxyExcept parameter, it can be used to direct all incoming Reflection sessions to one specific secure HTTP server.

Hint

In general, this parameter is unnecessary. It should be used only when Reflection for the Web cannot automatically detect the secure HTTP proxy.

Values

Any valid secure HTTP proxy address in the following format:address:port

Example

<param name="httpsProxy" value="myHTTPSProxy:443">

ibm3270helptoc

This parameter redirects the Help Topics command in the Help menu for IBM 3270 terminal sessions to the specified URL.

Value

http://<terminal emulation component installation>/help/ibm3270help.html (Default)<any valid URL>

Example

<param name="ibm3270helptoc"
        value="http://ReflectionWeb.example.com
                    /customHelp/ibm3270help.html">

ibm3287helptoc

This parameter redirects the Help Topics command in the Help menu for IBM 3287 printer sessions to the specified URL.

Value

http://<terminal emulation component installation>/help/ibm3287help.html (Default)<any valid URL>

Example

<param name="ibm3270helptoc"
        value="http://ReflectionWeb.example.com
                    /customHelp/ibm3287help.html">

ibm3812helptoc

This parameter redirects the Help Topics command in the Help menu for IBM AS/400 printer sessions to the specified URL.

Value

http://<terminal emulation component installation>/help/ibm3812help.html (Default)<any valid URL>

Example

<param name="ibm3270helptoc"
        value="http://ReflectionWeb.example.com
                    /customHelp/ibm3812help.html">

ibm5250helptoc

This parameter redirects the Help Topics command in the Help menu for IBM 5250 termianl sessions to the specified URL.

Value

http://<terminal emulation component installation>/help/ibm5250help.html (Default)<any valid URL>

Example

<param name="ibm3270helptoc"
        value="http://ReflectionWeb.example.com
                    /customHelp/ibm5250help.html">

ibmxfrhelptoc parameter

This parameter redirects the Help Topics command in the Help menu for IBM AS/400 data transfer sessions to the specified URL.

Value

http://<terminal emulation component installation>/help/ibmxfrhelp.html (Default)<any valid URL>

Example

<param name="ibmxfrhelptoc"
        value="http://ReflectionWeb.example.com
                    /customHelp/ibmxfrhelp.html">

ignoreASCIIData

This parameter is used in IBM 5250 emulation and IBM AS/400 printer emulation. The parameter directs the emulator to ignore any ASCII data records that may precede the first valid block-mode data (5250 data stream commands) received after connecting. By default, when the parameter is set to false, such ASCII data will result in an error message. When set to true, such ASCII data will not result in an error.

Value

true

false (Default)

Example

<param name="ignoreASCIIData" value="false">

ignoreHostPrintRequest

This parameter specifies whether host-initiated print requests in a 3270 terminal session are ignored. The default is true. This parameter applies to 3270 sessions only.

Value

true (Default)

false

Example

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

indAutoPositionCursor

This parameter controls whether Reflection enters IND$FILE commands into the last unprotected field on the screen. If true (the default), Reflection sends a HOME and a BACKTAB key to move the cursor to the last unprotected field before issuing the IND$FILE command.

Value

true (Default)

false

Example

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

int1InsertPads parameter

This parameter is used with UTS emulation sessions only. If Insert Pads is set to true, a Pad code is inserted into the INT1 transmit buffer before sending if the buffer is not completely filled. The value of the Pad code is 0x9F.

Value

false (Default)

true

Example

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