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
Logon Security and User Profiles
HP NonStop Pathway/iTS Web Client Programming Manual—520270-003
3-2
Actions of the Web Client
Actions of the Web Client
If the logon is successful (that is, if the end user enters a valid user name/password
combination), the client application begins to run. However, before the browser
displays the starting page of the client application, the application communicates with
the host NonStop to retrieve information associated with the profile entered by the end
user. This information resides in a database (with the Guardian file name
USERPROF) on the NonStop.
A Pathway server program supplied as part of Pathway/iTS reads the database and
obtain the profile information on behalf of the application. The applet stores this
information in various special registers for later use. Then the browser displays the
starting page—that is, the HTML page corresponding to the INITIAL program unit in
the SCREEN COBOL source program—and the client application continues to run.
If the end user does not enter a profile (that is, if the entered profile is null), the user ID
and password are validated, but no values are retrieved or set for any of the special
registers.
If the end user enters a valid profile, the profile is sent via the web gateway to the
server. The server retrieves from the database and returns to the application the
values of the seven special registers associated with user profiles (defined in the
following subsection), and also returns values for the PW-TCP-PROCESS-NAME,
PW-TCP-SYSTEM-NAME, and TERMINAL-FILENAME special registers. (All other
SCREEN COBOL special registers have no meaning for web clients; these special
registers always have default values in the converted Java code.)
If the end user enters an invalid profile (one that is not in the user profile database), a
“Profile Not Found” popup message appears. In this case, no values are returned to
the application for the seven special registers associated with user profiles, but values
are returned for the other three special registers.
Contents of the User Profile Database
The USERPROF database is a key-sequenced database with the profile name as the
key. Each record of the user profile database consists of the key and seven fields; the
values of the seven fields are stored in corresponding special registers in the Java
applet. The fields are as:
Field Name Type and Length
Corresponding Special
Register in Applet
TERMINAL-PRINTER PIC X(36) TerminalPrinter
LOGICAL-TERMINAL-NAME PIC X(16) logicalTerminalName
USER-PROFILE-1 PIC X(36) userProfile1
USER-PROFILE-2 PIC X(36) userProfile2
USER-PROFILE-3 PIC X(36) userProfile3
USER-PROFILE-4 PIC X(36) userProfile4
USER-PROFILE-5 PIC X(36) userProfile5