CORBA 2.3.3 Getting Started Guide (NonStop CORBA 2.3.3+)

numbers for the NSDOM processes and the same PREFIX). Leave the "new installation" check
box checked on the installer GUI. The user logged on through the installation GUI must have user
permissions that allow files to be overwritten in the default location. If the contents of NSD_ROOT
are not desired to be retained through the installation process, NSD_ROOT may be renamed or
deleted prior to starting the installation.
Select the option to rebuild the NonStop Server for Java release 2.0 or later JVM.5.
After the installation completes, rename the temporarily saved Guardian NSDCFGDB database
file back to its original name.
6.
Restart the CORBA services from the console.7.
For C++ and Java applications, refer to Moving from NonStop CORBA 2.3 to NonStop CORBA
2.3 Update 3.
8.
Upgrading From NonStop CORBA 2.3 Update 3 to a Later NonStop
CORBA Update
If the default location is desired, the same PREFIX, host name, TCP/IP process, NSDOM process port
numbers, with no customization to the basic installation, and the NAMINGDB and NSDCFGDB will be left
intact.
Stop all CORBA services for the default subsystem from the console.1.
Install the NonStop CORBA 2.3 update with the installer. Leave the "new installation" check box
unchecked on installer GUI, this will leave the etc directory untouched and the previous settings
and the databases will be left intact from the previous installation (for example, NSDCFGDB,
NAMINGDB, nsdom.ir, env.sh). Select the option to rebuild the NonStop Server for Java
release 2.0 or later JVM.
2.
Restart the CORBA services from the console.3.
For C++ and Java applications, refer toMoving from NonStop CORBA 2.3 to NonStop Corba 2.3
Update 3.
4.
Installing Multiple Versions of NonStop DOM, NonStop Jorb, and
NonStop CORBA 2.3 Update 3
Each installation must be in its own directory.●
The PREFIX's and port numbers must be unique.●
Each installation will have its own NSDCFGDB and NAMINGDB.●