Enhancing the HP e3000 User Interface

3
Web Access
Most implementations of the user interface enhancement methods are being expanded to
include Web access. Additional security and data encryption must be addressed when adding
Web access. These methods can be desktop- or session-based, depending on their specific
implementations. They also can have Web-based deployment capabilities.
For more information on this topic, see the HP white paper, “Web Enabling Your HP e3000
Applications and Data Access.”
Enhanced User Interface Methodologies
There are many ways to evolve the simple terminal user interface of the HP e3000 application.
The following are different available approaches. Please note that some implementations use a
combination of these methodologies.
VPlus Conversions
With so many HP e3000 programs using VPlus, which is part of the MPE/iX operating system, it
is a natural starting point for user interface evolution. The VPlus forms file is used as source
and is converted into a graphical interface. Since the calling program is not changed, the VPlus
API is used as the client/server protocol. (Please Appendix A for third-party VPlus conversion
tools for the HP e3000.)
Enhanced Terminal Emulators
Some vendors are enhancing the capabilities of terminal emulators that run on a PC to provide
HP e3000 programs with access to additional terminal emulator features. These features range
from pull-down menus and radio buttons to display of graphics files and sound files. (Please
see Appendix B for available enhancement products.)
Client/Server Conversions
A more radical approach is to change the program to use a heterogeneous client/server
computing environment. Although other methodologies use a client/server environment as an
implementation technique, doing so is hidden from the developer. The client/server approach
exposes the developer to network calls or to middleware that resides on top of the network.
The program is modified to use network/middleware solutions to communicate with a client
running on a desktop. (Appendix C lists client/server and middleware solutions.)