Pathway/iTS Web Client Programming Manual (H06.03+, J06.03+)
Table Of Contents
- HP NonStop Pathway/iTS Web Client Programming Manual
- Legal Notices
- Contents
- What's New in This Manual
- About This Manual
- 1 Introduction to Pathway/iTS Web Clients
- 2 How to Compile, Build, and Maintain a Pathway/iTS Web Client
- 1. Prepare the SCREEN COBOL Object File
- 2. Create a Configuration File
- 3. Run the Converter
- 4. Modify Java or SCREEN COBOL Code as Needed
- 5. Run PROFDBM to Set Up the User Profile Database
- 6. Build the Converted Client
- 7. Deploy the Web Client
- 8. Customize the Screens
- 9. Specify the Port Number of the Router Process
- 10. Configure Pathway Servers for User Profiles and User Conversion Routines
- 11. Tune the Application for Performance by Changing the Session-Length Parameter
- 12. Maintain the Client
- 3 Logon Security and User Profiles
- 4 User-Written User Conversion Procedures for Web Clients
- 5 SCREEN COBOL-to-Web Conversion Mappings
- 6 Java Import Package Reference
- 7 Introduction to Pathway/iTS 1.1
- A Client Error Messages
- B SCREEN COBOL Features Not Supported for Web Conversion
- Index
- Content Feedback
Introduction to Pathway/iTS Web Clients
HP NonStop Pathway/iTS Web Client Programming Manual—520270-003
1-5
Gateway Threads
that handles a web client is configured with its FILE attribute pointing to a router
process. Each such TERM object sends a message to the router process indicating
that it is available to service a connection. When a client requests a connection, the
request is sent to the router and the router passes the client information to the TCP.
The TCP then establishes a socket connection to the client, verifies access rights, and
passes control to the gateway thread.
The combination of the router and TCP processes provides general load balancing for
gateway threads. TERM objects within multiple TCP processes are associated with a
given router process. This enables the router process to identify the gateway thread
that will process the connection request. Multiple routers can thus be used to support
more than one gateway application.
Gateway Threads
The run-time web gateway is implemented as a Pathway/iTS intelligent device support
(IDS) requester running on the NonStop system under control of the TCP. This
requester program is provided as part of Pathway/iTS. It handles requests from the
browser-based web client, treating the client as an intelligent device.
The gateway validates user access and performs certain functions on behalf of the
client including beginning and ending transactions, user conversion routines, and send
operations to Pathway server processes.
Client communications with the Pathway/iTS web gateway can use the standard HTTP
protocol to allow optional use of Internet proxy servers. Alternatively, for intranet
applications, a client can use the raw sockets protocol. The protocol is specified by the
system manager when starting the router process.
Pathway/iTS 1.1
PATHTCP4, the TCP component uses SERVERCLASS_SEND_* APIs to process the
existing SEND verb for SCOBOL requesters and converted Java clients. The features
are:
•
PATHTCP4 does not communicate with either owner or external PATHMON
process for link management activities. Instead of performing Guardian
WRITEREAD on Pathway server processes to communicate with them,
PATHTCP4 becomes a Pathsend requester and uses Pathsend APIs to
communicate with Pathway servers. Therefore, any existing Pathway/iTS 1.0
application can be used with Pathway/iTS 1.1 with minimal changes to the
applications.
•
PATHTCP4 provides four SCOBOL verbs, DIALOG-ABORT, DIALOG-BEGIN,
DIALOG-END, and DIALOG-SEND to enable SCOBOL requesters and converted
Java clients to establish context-sensitive communication with Pathway servers.
The context-sensitive communication allows SCOBOL requesters and converted
Java clients to send more than 32,000 bytes of data to the same Pathway server
process.