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
HP NonStop Pathway/iTS Web Client Programming Manual—520270-003
7-1
7 Introduction to Pathway/iTS 1.1
Pathway/iTS 1.1 provides large message (more than 32,000 bytes) communication
support between SCOBOL requesters (and converted Java clients) and Pathway
servers. Today, support for large message communication is available to TS/MP
Pathsend requesters in the form of context-sensitive APIs
(SERVERCLASS_DIALOG_* APIs). Pathway/iTS 1.1 intends to support large
message communication by introducing a new TCP process called PATHTCP4. The
new TCP component of Pathway/iTS 1.1 is a Pathsend requester and uses Pathsend
APIs to forward the application message to Pathway servers. Four new SCOBOL
verbs (DIALOG-ABORT, DIALOG-BEGIN, DIALOG-END, and DIALOG-SEND) are
introduced in Pathway/iTS 1.1 to support large message communication.
To process the SEND verb in SCOBOL program (and in converted Java clients),
PATHTCP4 makes SERVERCLASS_SEND_ API call, and to process the DIALOG-*
verbs, PATHTCP4 makes SERVERCLASS_DIALOG_* API calls. PATHTCP4 never
communicates to any PATHMON process directly for link management activities. The
SCUP and Web Client components of Pathway/iTS 1.1 are also changed to support
the new functionalities. Any existing Pathway/iTS 1.0 application can be used along
with PATHTCP4 component of Pathway/iTS 1.1 with minimal changes or no changes
to the applications. However, for compatibility reasons, Pathway/iTS 1.1 package also
includes PATHTCP3, the legacy TCP component.