USAS Web Enabling

1
USAS Web Enabling

• Initial Release Coming Soon

2
Pilot Project Goals

• Short-Term/Immediate Goals
• Provide alternative GUI for Requisition entry
• Post new Requisitions
• Clone existing Requisition and post as new
• Modify Requisitions
• Print Requisitions
• Do not disturb existing application
• Post/update to existing USAS data files
• Use existing OpenVMS/USAS security model
• Focus on casual/infrequent user

3
Pilot Project Goals

• Project Requirements/Longer Term Goals
• Design framework for web-enabling other state
  software functions
• Plan for future for platform migration
• Use standard technologies (XML, SOAP, RPC, etc.)
• Allow for other interfaces e.g. native GUI
  client
• Ancillary Goals
• Keep costs low (hardware, licensing operating)
• Use Open Source or free tools when possible
• Support, but dont limit to, current OSs and
  hardware
• Reduce dependency on proprietary OSs and software

4
Project Status

• HP Consultants
• Designed architecture and framework
• Implemented first (Requisition) webapp and SOAP
  service
• Have delivered final version
• SSDT
• Backend RPC on OpenVMS using existing routines
• Completing webapp and SOAP service
• Clean up UI, fixing remaining problems
• Prepare for configuration/deployment
• Expected Release date May 2003
• (Note There are 31 days in May)

5
New Technologies

• For OpenVMS Server
• USP (Universal Service Provider)
• Free product from HP
• Provides RPC (Remote Procedure Call)
• Permits existing 3GL (e.g. COBOL) to be called by
  remote clients
• Handles VMS process creation and management
• Allows creation of a process similar to an
  interactive user with appropriate security
  context
• Provides native Java classes for remote clients

6
New Technologies

• For Web Server
• Java 2
• J2EE web container (e.g. Tomcat)
• JSP, Servlets, etc
• For SOAP server
• Apache Axis
• Entire application will be native Java

7
Requirements

• OpenVMS/Alpha 7.3-1 server
• USP V6.1
• Web/SOAP server
• Java 1.4.1 (or higher)
• Tomcat 4.0.4 (or higher)
• Any web server with Servlet Connector)
• SSDT intends to support
• OpenVMS with Apache Web Server
• Linux with Apache
• Windows 2000 (IIS or Apache web server)
• SSDT has provided additional details and sources
  for software
• See http//ssdt.oecn.k12.oh.us/rpcweb/

8
Architecture Diagram
9
Focused Diagram
10
Why Java J2EE?

• Advantages of Java and Java 2 Enterprise Edition
• Low cost
• No licensing for development or run-time
  environments
• Open source and commercial alternatives available
• Platform independence
• Runs anywhere
• Provides migration from OpenVMS
• Does not limit hardware or OS choices
• Broad industry and standards support