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-3
Control Page
Control Page
Each converted SCREEN COBOL application is managed through a control page.
This HTML page is loaded into a control frame that is created by the starting page.
The control page contains a MainApp applet. This page is not visible to the end user.
It remains active throughout the execution of the application.
The name of the control page is derived from the user-specified INITIAL program unit
followed by _CONTROL. For example, if the name of the INITIAL program unit is MY-
SCOBOL-APP, the name of the generated control page will be called
MY_SCOBOL_APP_CONTROL.html.
Java Classes for the Program Units
For each program unit, the converter creates a Java class. The name of the Java file
for the class is derived from the name of the program unit. The conversion mappings
are described under Mappings to Java Classes later in this section.
User HTML Pages for the Screen Sections
The Screen Section of the SCREEN COBOL program is converted into a set of HTML
pages. The conversion mappings are described under Mappings to User HTML Pages
later in this section.
Conversion Mappings
This section describes how the various elements of a SCREEN COBOL program are
converted to elements of Java classes or user HTML pages.
Mappings to Java Classes
For each program unit in the SCREEN COBOL program, the converter creates a Java
class. The name of the Java file is derived from the name of the corresponding
program unit. The conversion mapping is as:
•
The Working-Storage section is converted to Java classes.
•
Each paragraph in the program unit is converted to methods within the Java class.
•
Input-output elements in the Screen Section are converted to ScreenField objects
in the Java class.
The Java code files are generated at the location specified by the JAVAVOL parameter
in the CONVERT command or at the Java location specified in the configuration file.
Conversion of Working-Storage Section
Each group-level item in the SCREEN COBOL program unit is represented as a
nested class within the Java class. Each such nested class implements the necessary