M-N-O

macroTimeout

This parameter specifies the number of seconds that a macro waits for the next screen during playback. If the timeout elapses without the screen being received, the macro stops and an error message displays. You can also set this value in the Macro Playback dialog box. You may need to increase the timeout if your host is slow to respond.

Value

10 Default, in seconds 1-9999

Example

<param name="macroTimeout" value="20">

mayscript

This attribute allows a Java applet to access JavaScript. If an applet attempts to access JavaScript when the mayscript attribute is not specified, the browser generates an exception.

The mayscript attribute does not take a value such as true or false.

Example

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

meteringContext

This parameter specifies the web application context for the metering server. This is used in the URL that accesses the metering server, and is specified when the metering component is installed. The default, rwebmeter, is the correct value if you used the automated installer and have only one metering server.

The usage metering component monitors and logs connection information and queries.

Value

rwebmeter (Default)

<descriptive string>

Example

<param name="meteringContext" value="rwebmeter">

meteringEnabled

This parameter determines whether usage metering is enabled for Reflection sessions. The usage metering component monitors and logs connection information and queries.

When this parameter is set to true, you must specify the host on which the metering servlet resides, using the meteringHost parameter.

Value

true

false (default)

Example

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

meteringFTPenabled

This parameter determines whether usage metering is enabled for FTP connections. The usage metering component monitors and logs connection information and queries.

When this parameter is set to true, the FTP connection is monitored. (However the meteringFTPenabled parameter is always ignored when meteringEnabled is set to false.)

Note that a metered FTP session does not use a second license in addition to the terminal session--licensing is based upon the number of computers connecting, not the number of connections made. However, when meteringFTPenabled is set to true, the FTP connection counts as an additional session, which is monitored when the perUserLimit parameter is enabled in the metering servlet.

Value

true (default)

false

Example

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

meteringHost

This parameter identifies the host on which the metering servlet resides. You can use a full host name or its full Internet Protocol (IP) address. The usage metering functionality monitors and logs connection information and queries.

Value

<host name>

<IP address>

Example

<param name="meteringHost" value="myServer.example.com">

meteringHostRequired

This parameter specifies whether host connections can be made when the metering servlet is unresponsive for any reason. Setting this parameter to true prevents all host connections when the metering servlet is unavailable.

When this parameter is set to true, you must specify the host on which the metering servlet resides, using the meteringHost parameter. The usage metering functionality monitors and logs connection information and queries.

Value

true

false (default)

Example

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

meteringPort

This parameter specifies the port on which the metering servlet resides. The default is 80. The usage metering functionality monitors and logs connection information and queries.

Value

80 (Default)

<any valid port number>

Example

<param name="meteringPort" value="80">

meteringProtocol

This parameter specifies whether the metering server uses the HTTP or HTTPS protocol for connections to the client. The usage metering component monitors and logs connection information and queries.

When the parameter is set to true, the HTTPS protocol is used; when it is set to false, HTTP is used. The HTTPS protocol provides SSL/TLS encryption and is consequently more secure, but requires that the servlet runner be SSL/TLS-enabled. If you used an automated installer and installed the default servlet runner, SSL/TLS is enabled with a self-signed certificate.

Value

true (use HTTPS)

false (use HTTPS, default)

Example

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

model

This parameter specifies the terminal model for the session. To use this parameter, enter only values that are compatible with the type of applet specified in the applet tag. If you do not use this parameter to specify a model, the default model for the applet is used.

• IBM3270

  2E, default (Enhanced), 3E-5E, 2-5

• IBM3270 printer

  3287

• IBM5250

  3179-2 (Default), 3180-2, 3196-A1, 3477-FC, 3477-FG, 3486-BA, 3487-HA, 3487-HC, 5251-11, 5291-2

• IBM AS/400 printer

  3812-1

• IBM AS/400 data transfer

  The model parameter is not used for AS/400 data transfer.

• HP

  2392A, 70092 (Default--includes 70096), 70094 (Includes 70098)

• VT

  VT52, VT102, VT400-7 (Default), VT400-8

• UTS

  UTS20, UTS40, UTS60 (Default)

• T27

  UNISYS-TD830, UNISYS-TD830-ASCII, UNISYS-TD830-INTL, UNISYS-TD830-NDL (Default)

-T27 printer - The model parameter is not used for T27 printer

-ALC - The model parameter is not used for ALC

Example

<param name="model" value="2E">

name

This optional attribute specifies the name of the applet. The applet name is used by other programs and applets to reference and communicate with the applet. It is important that you assign each applet a unique name if you are running multiple applets on a page, enabling user preferences, or using the Reflection API.

Also, the value for the name attribute is displayed in the title bar of the session when the applet session is running in a separate window (the frame parameter is set to true) and the title parameter is not specified.

Example

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

onExitJavaClass

This parameter specifies a Java "attachment class" to run when you select the Exit command in the File menu, you click the session's close box, or you invoke the API exit() method. iThe attachment class can then perform any "clean-up" tasks it needs to before the session is exited.

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="onExitJavaClass" value="com.mycorp.reflection.MyCleanUpClass">

<param name="onExitJavaClass" value="com.wrq.eNetwork.ECL.modules.PreventSessionClose">

onStartupJavaClass parameter

This parameter specifies a Java "attachment class" to load immediately after the Reflection terminal session is done loading.

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="onStartupJavaClass" value="com.mycorp.reflection.MyAttachmentClass">