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
SCREEN COBOL-to-Web Conversion Mappings
HP NonStop Pathway/iTS Web Client Programming Manual—520270-003
5-2
Components of the Web Client
Components of the Web Client
For each SCREEN COBOL application, the converter generates these Java classes
and HTML files:
•
Main Java applet
•
Starting page
•
Initial page
•
Control page
•
Java classes for the program units
•
User HTML pages for the Screen Sections
Main Java Applet
The main applet is contained in a file named
initprog
_MAINAPP.java, where
initprog
is the Program Unit name specified in the INITPROG parameter of the
CONVERT command. If the APPNAME parameter is specified in the CONVERT
command, then the file name has the format appname.java. The main applet
contains the generic applet code, which acts as a container for individual program unit
classes. It starts an execution thread for the program units and retains the context
across program units during CALL processing. It also provides methods to be called
from HTML pages on completion of HTML events.
Starting Page
The starting page is an HTML page. This is the first application component to be
loaded by the client’s browser. This page defines a START button. When the user
clicks the START button, a new browser window is created and the Initial page is
loaded .
The name of the HTML file is derived from the user-specified INITPROG or
APPPNAME parameter followed by _START; hyphens in the user-specified parameter
are replaced with underscores (_) in the generated name. For example, if the name of
the INITIAL program unit is MY-SCOBOL-APP, the name of the generated starting
page is MY_SCOBOL_APP_START.html.
Initial Page
The initial page is an HTML page. This is the second application component to be
loaded by the client's browser. This page defines the frames on the browser window.
The name of the HTML file is derived from the user-specified INITPROG or APPNAME
parameter followed by _PAGE1; hyphens in the user-specified parameter are replaced
with underscores (_) in the generated name. For example, if the name of the INITIAL
program unit is MY-SCOBOL-APP, the name of the generated initial page is
MY_SCOBOL_APP_PAGE1.html.