CORBA 2.6.1 Getting Started Guide for C++

Chapter 3. Considerations for Migrating from Previous Releases
Chapter 3. Considerations for Migrating from Previous Releases
Product Level Migration Information
Overview
Upgrading From NonStop CORBA 2.3 to NonStop CORBA 2.6.1
Moving Applications from NonStop CORBA 2.3 Update 3 or Later to NonStop CORBA 2.6.1
Product Level Migration Information
Overview
NonStop CORBA 2.6.1 is compatible with prior versions of NonStop CORBA. New features have been added, but no features have been
removed. Some general considerations follow:
The GUI installer scripts for the SDK and RTK have been combined into one script, with choices for installation of the SDK and of SSL
as options.
The installation script has been enhanced to allow installation of SSL as an option.
DSM/SCM support has been added to help manage installation of files in the OSS environment.
The Console has been altered. Console installations from previous versions should be uninstalled, and the new Console should be
installed.
NonStop CORBA 2.6.1 can be managed with the same management tools used in previous versions.
NonStop CORBA 2.6.1 should perform as well or better than earlier versions.
Upgrading From NonStop CORBA 2.3 to NonStop CORBA 2.6.1
You should always install NonStop CORBA as a new installation, even if you have a previous installation of NonStop CORBA 2.3. If you use the
GUI installer, follow the procedures in
Installing NonStop CORBA, and leave the NEW installation check box checked. If you use the
installation script as described in
Alternative Installation Method, leave the default for the question “Is this a new installation.”
Installing NonStop CORBA 2.6.1 as a new installation causes the previous settings and databases to be overwritten with new CORBA 2.6
settings and databases (for example,
NSDCFGDB, NAMINGDB, nsdom.ir, env.sh).
Moving Applications from NonStop CORBA 2.3 Update 3 or Later to
NonStop CORBA 2.6.1
For all applications,
1. IDL files must be recompiled by the CORBA 2.6 IDL compiler.
2. C++ source must be recompiled.
Some applications may need to be changed, depending on whether they use the constructs discussed in the following paragraphs.
When NonStop CORBA 2.6.1 is installed, the default port for the ILSD is set to $portnumber3, where $portnumber3 represents the fourth
port number in sequence, starting with the number entered in the installation GUI or script. The installation default number is 4000, so the
default for $portnumber3 would be 4003. (In the past, the ILSD port number was set to a well-known fixed value, 2809.) If your
applications relied on a fixed ILSD port number, such as 2809, you must change your application's
corbaname or corbaloc URL to
append the ILSD port number to the host IP address. For example,
corbaloc://host ip address must be changed to corbaloc://host
ip address:ilsd port number.
Identifiers of the form CORBAname reside in the CORBA namespace. (In the past, these names were available to applications.) For
example,
CORBAObject_ptr has been changed to CORBA::Object_ptr.
Some names have been removed since some CORBAname identifiers did not directly map into proper names. For example,
CORBATransactionRequired is represented CORBA::TRANSACTION_REQUIRED.
Callers are responsible for releasing the object reference returned by TypeCode::content_type().
The POA::create_POA signature is: