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
How to Compile, Build, and Maintain a Pathway/iTS
Web Client
HP NonStop Pathway/iTS Web Client Programming Manual—520270-003
2-6
Set Up the Build Environment in a Windows
Environment
application-home
is the full path name of the OSS directory from which the application will be run.
makefile-name
is the name of the make file to be created that is used when building and running
the application int he OSS environment.
JMAKENV does these:
•
Creates a directory named
application-home
/build.
•
Creates a directory named
application-home
/bin where the built objects will
be stored.
•
Copies all the appropriate files from the Java and HTML location (specified at the
time of the conversion) to the
application-home
/build directory. The files are
copied with the appropriate .java and .html extensions.
•
Creates a make file for building the application. The name of the make file is
specified in the JMAKENV command and is copied to the
application-
home
/build directory as
make-file.mk
.
•
Sets up the environment variables used by the make file.
For example, you would run the JMAKENV file for the sample application as:
TACL> JMAKENV invy /usr/test/inventory invymk
JMAKENV in the sample application does these:
•
Creates the directory /usr/test/inventory/build.
•
Creates the directory /usr/test/inventory/bin where the built objects will be
stored.
•
Copies all the necessary files from the specified Java and HTML location (in this
example, the volumes default to the same volume and subvolume as mycfg) to
the NonStop Kernel OSS directory /usr/test/inventory/build.
•
Creates a make file named invymk for building the application.
•
Sets up the environment variables used by invymk.
•
Copies invymk to the directory /usr/test/inventory/build as invymk.mk.
Set Up the Build Environment in a Windows Environment
Pathway/iTS provides a TACL MACRO utility named JMAKENV, which is used to set
up the build environment for the converted web client.
Note. The user running JMAKENV must have permission to create and copy files to the
application-home
directory in the OSS environment.