CORBA 2.3.7 Programmer's Guide for C++

Chapter 10. Porting CORBA Applications to NonStop CORBA
Prev Next
Chapter 10. Porting CORBA Applications to
NonStop CORBA
Table of Contents
Global State Information
Database Access
Applications Using Proprietary Features
This section describes general considerations for porting CORBA applications from other ORBs to
NonStop CORBA 2.3.
For specific details about the NonStop CORBA implementation that may be useful in porting
applications, refer to the NonStop CORBA 2.3.7 Programmer's Reference.
Global State Information
CORBA applications that use global state information may require changes. In general, global state
information limits an application's portability, as well as its ability to take advantage of the scalability
features of NonStop CORBA and the NonStop systems.
Database Access
CORBA applications using multithreaded servers for database access will need to be modified, because
SQL/MP and SQL/MX database accesses are process-blocking operations.
The best design in a NonStop CORBA application is to isolate database access functions from business
logic. Independent data access objects (DAOs) allow database accesses to be isolated from other
functions that can be implemented using multithreading.
For further design recommendations, see Object Distribution.
Applications Using Proprietary Features
Applications using proprietary features or APIs from other CORBA implementations will not run on
NonStop CORBA without modification.
For example, many older applications still use the Basic Object Adapter (BOA). BOA-based applications
must be reworked into POA-based applications, and any use of proprietary extensions will require
additional rework.