NonStop Systems Introduction

The Application Server Environment
NonStop Systems Introduction— 527825-001
3-18
The HP Application Servers
The HP Application Servers
HP provides several application servers that are well-suited for use in ZLE systems.
They are presented in the order in which they were introduced by HP. Each of these
application servers represents an advance in features and capabilities over the
previous offering.
•
NonStop Tuxedo
•
NonStop CORBA
•
WebLogic Server and the J2EE Platform
NonStop Tuxedo
NonStop Tuxedo was the first HP offering of an industry-standard transaction monitor.
NonStop Tuxedo is a highly clustered version of the BEA Systems Tuxedo product.
Tuxedo was a leading open transaction monitor that provided a framework for
client/server applications in enterprise transaction processing. It has been used to
provide an application integration environment for many ZLE systems.
Tuxedo is easy to code and is widely used throughout business and industry. At the
time of its implementation at HP, it was the most “open” of the HP transaction
processing environments. Most Tuxedo servers are written in the C or C++ language
and are easily ported from one host platform to another.
Client applications use the Tuxedo Application-Transaction Monitor Interface (ATMI)
API to access the Tuxedo servers. This interface is familiar to developers throughout
the industry, so programming skills are transferable as well.
In the NonStop implementation of Tuxedo, HP proprietary components handle process
management (TS/MP) and transaction management (TMF). As a result, NonStop
Tuxedo can offer the high levels of scalability and availability that the NonStop server
platform is noted for.
In the NonStop Tuxedo environment, Tuxedo components handle initial communication
with clients. TS/MP components automatically take care of communication paths
between the Tuxedo components and the Tuxedo servers.
The TS/MP components set up communication paths between client and server
processes and distribute client requests to server processes to optimize system
throughput and response time. TS/MP components also start additional copies of
server processes as needed, restart failed processes, and delete server processes
when they are no longer needed.