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-5
6. Build the Converted Client
6. Build the Converted Client
You can build (compile) the converted client either on the NonStop system under the
Open System Services (OSS) environment of the NonStop Kernel operating system or
on another machine running the Windows NT operating system. Doing this involves
three steps:
1. Set up the build environment
2. Transfer files to the build environment (if the build environment is Windows NT)
3. Build (compile) the application
Set Up the Build Environment in an OSS Environment
Pathway/iTS provides a TACL MACRO utility named JMAKENV, which is used to set
up the build environment for the converted web client.
This utility uses the MAP file that is created at the time of conversion to generate the
build environment. The MAP file is created at the same location
($
volume
.
subvolume
) from which the CONVERT command was run. The MAP file
name is composed of the first four or five SCOBOL object file characters plus the
characters MAP. For example, if the SCOBOL objects are named MYAPPCOD,
MYAPPDIR, and MYAPPSYM, then the MAP file name is MYAPPMAP.
If the build environment is on a NonStop system under the OSS environment,
JMAKENV creates the application home directory under OSS, copies the converted
files to this directory and creates a make file for building and deploying the application.
You must set the CLASSPATH variable to point to the itsjlib.jar file (the Java import
package) and to the current directory.
export CLASSPATH=/usr/tandem/Pathway-iTS/itsjlib.jar:$CLASSPATH
The itsjlib.jar file must be available on the local machine. If it is not available, copy the
file from the installation CD.
Set other environment variables for Java compilation: for example:
•
Add /usr/tandem/java/bin to $PATH
•
Add /usr/tandem/java/lib/classes.zip to $CLASSPATH
•
Add /usr/tandem/java/lib/tandemvm.zip to $CLASSPATH
From the TACL prompt on a NonStop system, run JMAKENV as:
file-name
is the name of the SCREEN COBOL object-file (the POBJ file).
RUN JMAKENV
file-name
application-home makefile-name