CORBA 2.6.1 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.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. Java source files must be recompiled using NonStop Server for Java version 3.1.1.
3. Be aware that the default port for the ILSD has changed. It is now set to
$portnumber3 at installation.
Some applications may need to be changed, depending on whether they use the constructs discussed in the following paragraphs.
The value of the property org.omg.CORBA.ORBSingletonClass is com.tandem.nsdom.ORB.ORB_ORB_Singleton. (In the past, the value was
com.tandem.nsdom.ORB.ORB_ORB.) If an application has been setting this property explicitly, modify the application.
org.omg.CORBA.ORB.init() returns a singleton ORB, whose functionality is limited (according to OMG specifications). (In the past,
org.omg.CORBA.ORB.init() [singleton ORB] and org.omg.CORBA.ORB.init(String[], Properties) both returned an ORB.) If an
application has been using a singleton ORB where a non-singleton ORB should have been used, modify the application.
For the ORB to process incoming GIOP requests, the server application must specifically call org.omg.CORBA.ORB.run() or a similar
method. (In the past, an application did not have to call
org.omg.CORBA.ORB.run() or a similar method in a server-specific application.)
The default GIOP version is 1.2 (previously, it was 1.0). If an application requires GIOP 1.0, modify the application's profile to add the
key/value giop_version 1.0.
For corbaloc and corbaname the proper syntax is ::host, according to OMG specifications. (In the past, the corbaloc and corbaname
syntax was ://host.)