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-10
Deploy the Web Client on an OSS Environment
makefile-name
is the name of the make file generated by JMAKENV
path-name
is the relative pathname (under web-root) from which the web pages are served.
To deploy the sample application, execute the make file with this command:
make -f invymk.mk DEPLOY=testapp publish
Executing this make file does these:
•
Copies all the HTML files from the /usr/test/inventory/bin directory to the
usr/webserver/root/testapp directory, where /usr/webserver/root is
obtained from the WEBROOT variable in the make file .
•
Copies all the compiled Java files from the /usr/test/inventory/bin
directory to the /usr/webserver/root/testapp directory, where
/usr/webserver/root is obtained from the WEBROOT variable in the make
file.
Move installation files to the web server
Before running the application, you must move these files to the application directory
on the web server (these files were created when Pathway/iTS was installed):
ITSJLIB.jar, BPathwayiTS.js, OVPathwayiTS.js, and blank.html.
Copy these files to the application directory in the root using these commands:
cp /usr/tandem/Pathway-iTS/itsjlib.jar
/usr/tandem/webserver/root/
application-dir
/itsjlib.jar
cp /usr/tandem/Pathway-iTS/BPathwayiTS.js
/usr/tandem/webserver/root/
application-dir
/BPathwayiTS.js
cp /usr/tandem/Pathway-iTS/OVPathwayiTS.js
/usr/tandem/webserver/root/
application-dir
/OVPathwayiTS.js
cp /usr/tandem/Pathway-iTS/blank.html
/usr/tandem/webserver/root/
application-dir
/blank.html
In addition, HP recommends you also move the file end.html to the application
directory on the server. This file is displayed when the application terminates and can
be modified. Copy the file using this command:
cp /usr/tandem/Pathway-iTS/end.html
/usr/tandem/webserver/root/
application-dir
/end.html
Test the converted application
If the URL for the default page on the web server is http://intraweb.mycompany.com,
you can now test the converted application by using this URL:
http://intraweb.mycompany.com/testapp/INVENTORY_START.html