CORBA 2.6.1 Programmer's Guide for Java

The OSS run command lets you run a process with specific attributes. For example, you could use the following syntax to run a named process:
run -name=Guardian-process-name program-name
For example,
run -name=/G/svr Test_DII_SVR -ORBprofile tcp_sample_svr
In this example, svr is an arbitrary process name. tcp_sample_svr is passed when org.omg.CORBA.ORB.init() is called.
OSS Environment Variables and the env.sh File
A shell implements environment variables that you can set and display. Processes started from the OSS shell can access exported environment
variables. For example, NonStop CORBA processes and utilities use environment variables when you configure the system, develop a
component, or run an application. The $NSD_ROOT/etc/env.sh file stores shell commands that set the environment variables. Run the env.sh
shell script during the shell initialization by using the .profile, or run the env.sh shell script in the current shell using the dot (.) command. If you
log on only for NonStop CORBA work, it is often easier to set the environment variables using
.profile. However, when you use many
application environments, it may be easier to run the
env.sh script.
A subset of the environment variables set in the
env.sh file are relevant for compiling and building NonStop CORBA applications:
> export NSD_ROOT=/usr/tandem/nsdoms
> export JAVA_HOME=/usr/tandem/java
> export JREHOME=$JAVA_HOME/jre
> export CLASSPATH=.:$NSD_ROOT/lib/jorb.jar:$NSD_ROOT/lib/jts.jar:$NSD_ROOT/lib/ejb.jar
> export CLASSPATH=.:NSD_ROOT/lib/jorb.jar:$NSD_ROOT/lib/jts.jar
> export PATH=”$PATH:$NSD_ROOT/bin:$COMP_ROOT/usr/lib:$JAVA_HOME/bin”
$NSD_ROOT designates the root directory where NonStop CORBA files reside. This guide sometimes refers to directory names relative to
$NSD_ROOT; in these cases, the notation $NSD_ROOT means your setting of the NSD_ROOT variable.
JAVA_HOME designates the root directory where NonStop Server for Java files reside. The jorb.jar and JTS.jar files reside in the $NSD_ROOT/lib
directory.
CLASSPATH contains fully qualified names of all the jar files used by applications.
PATH specifies the order in which to search directories for a command typed at the osh prompt.
OSS Development and Debugging Tools
You use the following OSS commands and utilities to develop your application:
javac
You use javac to run the Java compiler. You can invoke javac from within the Makefile.
java
You use java to run Java programs. All Java programs are executed within the JVM
make
This utility helps you to build and maintain an application that consists of multiple, interdependent modules. You use a file, called
Makefile by default, to describe the dependencies among program modules. Thereafter, when you modify a module on which other
modules depend, the make utility automatically initiates recompilation of the dependent modules. The NonStop CORBA sample programs
use a Makefile to perform all the steps for building and configuring applications: running the IDL compiler, compiling and linking
application programs.
nm
The nm command writes the name list of each specified object file to the standard output file. The nm command displays symbolic
information appearing in an object file, executable file, or object-file library.
nm can be used to find symbols that show up in unresolved
external error messages.
vi
This utility is the OSS editor used to create and update OSS files.
jdb
You must use the jdb tool to debug your NonStop CORBA application programs. The implementation of jdb and extensions to the Sun
Microsystems tool are described in the NonStop Server for Java (NSJ) Tools Reference Pages.
Working in the NonStop CORBA Administrative Environment
Applications that you write use services provided by the NonStop CORBA administrative environment. This section gives a brief overview of the
administrative environment. For more information on the NonStop CORBA administrative environment, see the NonStop CORBA 2.6.1
Administration Guide.
Components of the NonStop CORBA Environment
The NonStop CORBA administrative environment has the following components:
The NonStop Distributed Component Console is a GUI-based interface used to manage the administrative environment.
Security domains are the processes that are managed under a single user ID.