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-11
Deploy the Web Client on a Windows Environment
Additional options available in the make file are as:
•
Publish only the HTML files from /usr/test/inventory/build
-f invymk.mk DEPLOY=testapp html
•
Publish only the class files from /usr/test/inventory/bin
-f invymk.mk DEPLOY=testapp class
•
Delete all the class files from /usr/test/inventory/bin
-f invymk.mk clean
•
Compile all the Java source files and create the class files in /usr/test/inventory/bin
-f invymk.mk all
•
Publish all the gif files (which must be in /usr/tandem/webserver/root)
-f invymk.mk DEPLOY=testapp gif
Deploy the Web Client on a Windows Environment
To deploy the compiled Java class files and the HTML files from a Windows
environment to an OSS directory under the webroot directory, run the JPUTFILE from
the Windows environment.
To get the JPUTFILE onto a Windows environment, use these steps:
1. From the Windows DOS prompt, execute the command:
ftp
host-address
where
host-address
is the IP address of the NonStop Server where the Java
and HTML files are generated
2. At the FTP prompt:
•
Logon to the system.
•
Set the remote directory to the location where JGETFILE is located; this the
same directorywhere all the class files are generated and the HTML files are
located
•
Set the transfer mode to ASCII .
3. Transfer JGETFILE then exit the FTP session using the commands
ftp> ASCII
ftp> get JPUTFILE JPUTFILE.BAT
ftp> bye
Once JPUTFILE.BAT is copied to a Windows environment, deploy the compiled Java
files and HTML files using this command:
JPUTFILE
hostname
user-ID
password
application-home