CORBA 2.6 Getting Started Guide for Java
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
Moving Applications from NonStop CORBA 2.3 Update 3 or Later to NonStop CORBA 2.6
Product Level Migration Information
Overview
NonStop CORBA 2.6 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 can be managed with the same management tools used in previous versions.●
NonStop CORBA 2.6 should perform as well or better than earlier versions.●
Upgrading From NonStop CORBA 2.3 to NonStop CORBA 2.6
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 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,