|
Other manuals for this model:
manual abstract
Optimized for use in transaction processing, NonStop CORBA allows the mapping of a large number of clients to a smaller number of servers,
effectively sharing resources. Because the NonStop CORBA system processes run in an HP NonStop TS/MP environment, you get the strength
of HP transaction services (for process management, availability, and load balancing) in a CORBA-compliant-based environment.
CORBA 2.6.1 Base
New features of NonStop CORBA are based on the CORBA 2.6.1 specification of the Object Management Group (OMG) and other OMG
specifications, except as noted in the NonStop CORBA 2.6.1 Programmer's Reference. Being CORBA-based means that NonStop CORBA
interoperates with other CORBA Object Request Brokers (ORBs). By using the Internet Inter-ORB Protocol (IIOP™) defined by CORBA,
NonStop CORBA can interoperate with other heterogeneous OMA-based environments that use the CORBA IIOP protocol.
Writing client and server objects compliant with CORBA 2.6 offers the following benefits:
Interoperation with other CORBA-compliant ORBs
Wide area network (WAN) and local area (LAN) network connectivity based on international networking standards
Ability to wrap legacy applications with a distributed object architecture (an advantage of NonStop CORBA)
Client/Server Computing with NonStop CORBA
NonStop CORBA applications are client/server applications that run on Common Object Request Broker Architecture (CORBA) 2.6-based
computer systems and networks. While clients and servers can be running on the same system, NonStop CORBA servers can also handle
remote client requests. Also, NonStop CORBA clients can make requests that are fulfilled by remote NonStop CORBA servers and servers on
other ORBs™.
NonStop CORBA application servers are CORBA-based server processes that run on the HP NonStop Kernel operating system. The application
server acts as a server process for clients both local and remote to the NonStop CORBA system.
NonStop CORBA clients are CORBA client processes that also run on the NonStop Kernel operating system. As CORBA clients, they can either
reside on the same system as the NonStop CORBA application server that processes their requests, or they can act as a "network" or "remote"
clients by interoperating across a network to an application server located on another computer that may use another vendor's CORBA-
compliant ORB.
With NonStop CORBA, a network client need not be aware of where the application server is located; when a network client makes a request of
an object, the NonStop CORBA software transparently establishes a link with the server to handle the client's request.
Features of NonStop CORBA
By implementing certain system-specific processes using TS/MP server classes or server pools (the preferred terminology), the ORB provided
with NonStop CORBA offers availability and scalability advantages over other CORBA-based ORBs. TS/MP runtime code resides in every ORB
running NonStop CORBA and can also be included in your NonStop CORBA application servers.
The NonStop CORBA ORB runs on HP NonStop systems. The NonStop CORBA application servers that you write in C++ or Java use this ORB
for communication to and from remote clients. The major features differentiating the ORB supplied with NonStop CORBA from other ORBs are:
Scalability of the ORB to support higher throughput
Scalability of application server processes across CPUs
Compatibility of NonStop CORBA components
Availability and fault tolerance
Transaction protection for data stores managed by the NonStop TM/MP and database software
Network session concentration to reduce the number of IP ports needed in the host
Advantages of the TS/MP environment
Scalability of the Object Request Broker (ORB)
With NonStop CORBA, you can increase the ORB capacity without disturbing running applications. NonStop CORBA provides several ways of
scaling the ORB itself:
Scalability of the ORB to support higher throughput New clients can connect to the NonStop CORBA ORB with no configuration changes
required on the client workstation or on the HP server.
To support increased request traffic, the NonStop CORBA system administrator can increase the number of Comm Servers.
To provide additional external port connections, the administrator can add multiple instances of HP NonStop TCP/IP to the NonStop
CORBA system. Each instance of NonStop TCP/IP increases the number of available TCP/IP ports and, therefore, the number of clients
the ORB can support. Multiple instances of NonStop TCP/IP allow Comm Servers to listen on the same IP address or different IP
addresses (port numbers must be unique within the scope of the TCP/IP process).
The administrator can configure NonStop CORBA to use the Parallel Library TCP/IP product. This product allows a single TCP/IP port to
be shared by multiple processes, with each connection being established in round-robin fashion. Using Parallel Library TCP/IP increases
capacity (there are more processes available to share the load) and improves fault tolerance (a software or processor failure does not
render the address unusable).
Network session concentration to reduce the number of IP ports needed in the host
...Other models in this manual:
Desktops - HP Integrity NonStop J-Series (195.75 kb)
Desktops - HP NonStop L-Series (195.75 kb)