Pathway/iTS Web Client Programming Manual (G06.24+)

How to Compile, Build, and Maintain a Pathway/iTS

Web Client

Compaq NonStop Pathway/iTS Web Client Programming Manual—520270-001

2-15

12. Maintain the Client

session, will be dedicated to that client (applet) until it has performed 5 delegated tasks.

After the 5 tasks are completed, the socket connection is broken, the session is closed,

and the gateway thread is freed to service another connection request from an applet.

There is one case where the specified number of I/O operations is ignored: the BT-ET

block. After a begin-transaction operation, the session is kept alive, regardless of the

specified number of I/O operations, until the end-transaction operation is done. After

the end-transaction operation, the session is closed.

The length of the session is important in view of the response times when several

hundreds of applets are running. One gateway thread should not be tied to one client for

a long duration. Neither should the length be too small, as each beginning of a session

incurs a fixed overhead of time and resources.

Pathway/iTS provides a default value for the number of I/O operations in a session. You

can modify this value to tune the application for optimal performance.

The value is specified in the sessionlength parameter in the file named

app-name_CONTROL.html generated during the conversion process. The contents

of this file are shown in Example. In this example, the INITPROG of the application is

named LOGON, and the name of the control file is LOGON_CONTROL.html.

To modify the number of I/O operations in a session, replace the param sessionlength

default value (within the double quotes; 20 in the example) with the desired integer

value.

12. Maintain the Client

You can maintain the client by modifying either the SCREEN COBOL source files or

the Java source files. If both terminal clients and web clients access the converted

application, you might want to make future modifications in the SCREEN COBOL files

to avoid maintaining two sets of source-code files. On the other hand, if all the clients

accessing the application are web clients, modifying the Java source might be a better

option.

Example 2-2. Sample CONTROL.html File

<META HTTP-EQUIV="Content-Type" content="text/html; charset=iso-

8859-1">

<TITLE> Control Frame </TITLE>

</SCRIPT> </HEAD>

<BODY>

<applet code="LOGON_MAINAPP.class", name="PathwayiTS",

archive="itsjlib.jar" width=10, height=10, MAYSCRIPT>

</applet>

</BODY> </HTML>