CORBA 2.6.1 Getting Started Guide for C++
installing NonStop CORBA 2.6.1.
Perform Subsystem Resource Cleanup
A subsystem cleanup does not have to be done in all cases, but you may want to do a cleanup if NonStop CORBA is already installed. If you
have a system you want to install over or a system to clean up, then performing a subsystem resource cleanup is advisable. A NonStop CORBA
subsystem creates resources during installation and setup. It is necessary to run the
unconfigure script to remove these resources.
The script is divided into two phases. The first phase removes files created during installation. The second phase removes TMF Resource
Manager entities created by OTS Transaction Managers during subsystem startup.
Phase 1
To execute this phase of the script, you must have the subsystem's
env.sh file sourced into your environment. You either must use the same
logon id as you used during the original installation of the subsystem, or you must be logged on as a super user. For example, assuming the
subsystem's prefix is "M", a successful first phase looks like this:
oss>>
unconfigure
nsdstop must be run prior to running this script and
NSDCFGDB and NAMINGDB database files cannot be opened.
This will PERMANENTLY purge the NSDCFGDB and NAMINGDB databases.
Do you want to proceed (y/n):
y
$DATA01.MMD0406.NSDCFGDB PURGED.
1 FILE PURGED
$DATA01.MMD0404.NAMINGDB PURGED.
1 FILE PURGED
Phase 2
To execute this phase of the script, you must be logged on as a super user. For example, assuming the subsystem's prefix is "M" and five
processes were configured in the subsystem's otstm serverclass, a successful second phase looks like this:
oss>>
unconfigure
This will PERMANENTLY purge the NSDCFGDB and NAMINGDB databases.
Do you want to proceed (y/n):
n
This will PERMANENTLY delete the TMF Resource Managers.
Do you want to proceed (y/n):
y
gtacl[9]: unable to propagate all environment variables
deleted RM NSOTSRMTX_MNO0
gtacl[9]: unable to propagate all environment variables
deleted RM NSOTSRMTX_MNO1
gtacl[9]: unable to propagate all environment variables
deleted RM NSOTSRMTX_MNO2
gtacl[9]: unable to propagate all environment variables
deleted RM NSOTSRMTX_MNO3
gtacl[9]: unable to propagate all environment variables
deleted RM NSOTSRMTX_MNO4
gtacl[9]: unable to propagate all environment variables
Install NonStop CORBA on the Host System
The host system is a NonStop S-Series server. The installers run on your workstation.
Run the IPSetup Program
This section discusses only automated software placement using the IPSetup Windows application. See the IPSetup User's Guide for
information about manual software placement using FTP and SETUPRUN.
Exit all other Windows applications before starting to place NonStop CORBA software on the host.
1. Open the product CD by double clicking on the CD drive.
2. Click the View Readme file button. Setup opens the readme file in Notepad. Be sure to review the entire readme file before
proceeding.
3. Click the Run IPSetup button to launch IPSetup. The program displays a Welcome screen and a License Agreement screen. To
continue the installation, click Next on each of these screens.
4. On the Installation Options screen click the NonStop Kernel RISC radio button. You may optionally check the box for Use
DSM/SCM. Click Next.
5. On the Product Selection screen, highlight the NonStop CORBA products you want to install. The software developers kit (SDK), the
runtime environment kit (RTK), and IIOP/SSL are separate products. Click the Add button, then click Next.
6. Log on to the host that you wish to install on by following the instructions on the Host Information screen. You may use either the system
name or the system IP address to log on. Click Next.
7. On the Host Target Settings screen you may either accept the default locations for Work and Backup subvolumes or browse to locations
of your choice. Click Next when you are satisfied with the locations.
8. On the Host File Placement screen you may either accept the default disk locations or browse to locations of your choice. Click Next
when you are satisfied with the locations.