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-14
10. Configure Pathway Servers for User Profiles and
User Conversion Routines
10. Configure Pathway Servers for User Profiles and
User Conversion Routines
Whether an end user is required to enter a password or a user profile is controlled by the
userAuthenticate and getProfile parameters in the control file that is generated by the
CONVERT command.
To use the user profile feature, set the getProfile parameter to true, as described in User
Profile Options in the Control File on page 3-3, and configure the Pathway server class
for the user profile server as detailed in Configure the User Profile Server Class on
page 3-6.
If your application uses user-written conversion routines running on the NonStop
Himalaya host, you must configure the Pathway server class for USER-LIB-SERVER as
described in Configure the User Conversion Server Class
on page 4-2.
11. Tune the Application for Performance by
Changing the Session-Length Parameter
The Java applet portion of the converted SCREEN COBOL application communicates
with the TCP so that the required tasks can be performed on the NonStop Himalaya host
system. Such tasks include:
•
Send operations to server classes
•
Beginning, ending, and aborting transactions
•
Accept day/date/time operations
•
User conversion routines
These tasks are delegated to the Pathway/iTS web gateway requester threads under the
control of the TCP. Each task involves one complete socket communication cycle
(a write and a read) or one I/O operation in a session.
A session begins when the applet opens the communication channel with the host
NonStop Himalaya by establishing a socket connection with the TCP. The session ends
when the connection is closed by the applet after the task delegated to the gateway
thread is completed.
While opening a session, the applet sends a connection request to the router process on
the NonStop Himalaya. The router process assigns the connection request to a waiting
gateway thread associated with a TERM object. The gateway thread then establishes a
socket connection with the applet. The router distributes client connection requests to
the waiting gateway threads while balancing the load optimally among the TCP
processes in the Pathway environment.
The number of I/O operations in a session affects the performance of the application
environment. For example, if this number is specified as 5, then the session with the
client will be kept alive until 5 socket communication cycles are done. In other words,
one gateway thread, with which the connection was established at the beginning of the