Manualshelf

CORBA 2.3.3 Getting Started Guide (NonStop CORBA 2.3.3+)

ManualsBrandsHP ManualsServerHP NonStop G-Series
41424344454647484950
Upgrading From NonStop DOM, NonStop JORB, and NonStop
OTS/JTS to NonStop CORBA Update 2.3 and Later
NonStop DOM, NonStop JORB and NonStop OTS/JTS previously used NonStop Server for Java release
1.6. NonStop CORBA 2.3, Update 3 and later, requires NonStop Server for Java release 2.0 or later.
It is best to install NonStop CORBA 2.3 in a unique location from NonStop DOM, NonStop JORB and
NonStop OTS/JTS. If the default location is desired, perform the following steps:
Run NSDSTOP for the subsystem in the default location.1.
Run UNCONFIGURE to purge the old NAMINGDB and NSDCFGDB databases.2.
Rename or delete the contents of the old NSD_ROOT directory.3.
Install NonStop CORBA 2.3 in the same locations (with the same ip address, TCP/IP process, port
numbers for the NSDOM processes and the same PREFIX). Select the option to rebuild the
NonStop Server for Java release 2.0 or later JVM.
4.
Run NSDSTART.5.
For C++ applications, refer to Moving from NonStop DOM to NonStop Corba 2.3 Update 3 (C++
Applications).
6.
For Java applications, refer toMoving from NonStop JORB to NonStop Corba 2.3 Update 3 (Java
Applications).
7.
Restart the applications to reinitialize the ORB for NSDOM.8.
Upgrading From NonStop CORBA 2.3 Update 1 to NonStop CORBA
2.3 Update 3
NonStop CORBA 2.3 Update 1 could be configured to use NonStop Server for Java release 1.6 or 2.0.
NonStop CORBA 2.3, Update 3 and later, requires NonStop Server for Java release 2.0 or later.
If Update 1 was configured to use NonStop Server for Java release 1.6, it is best to install NonStop
CORBA 2.3 in a unique location. Install NonStop Server for Java release 2.0 or later and continue with
the NonStop CORBA 2.3 Update 3 installation.
If the default NonStop CORBA 2.3 location is desired, perform the following step:
Stop all CORBA services for the default subsystem from the console.1.
The NSDCFGDB database may be saved between Update 1 and Update 3 of NonStop CORBA 2.3.
If the NSDCFGDB database is to be saved, rename the Guardian NSDCFGDB database file to a
temporary name.
2.
Run UNCONFIGURE to purge the Guardian NAMINGDB database.3.
Install NonStop CORBA 2.3 in the same locations (with the same ip address, TCP/IP process, port4.