CORBA 2.6.1 Programmer's Guide for C++

Chapter 4. Deploying a NonStop CORBA Application
Chapter 4. Deploying a NonStop CORBA Application
The general steps in deploying a NonStop CORBA application after you have compiled your files are:
Check that you have set up your application profile as described in Application Profiles: Configuring and Managing an Application.
Use the Console to make sure that any other subsystem configuration profile settings are correct.
Decide if you want to enable tracing.
Make sure messages will go to the location you want (either $0 or another place you designate).
Move your application files to the directories where you want to run them.
Ensure that environment variables are set correctly in $NSD_ROOT/etc/env.sh, and then execute env.sh.
If the application uses a database, ensure that database files are ready and the database is available.
Now you are ready to run your application. For bring-up you should run clients and servers from separate OSS sessions on the NonStop
system. Beyond that you take different steps depending upon the complexity and design of your application. The variations are listed in the
matrix below:
Client Server
Single Process Start the server, then run the client. Run the server.
Server Pool
(TS/MP Server
Class)
Start the server, then configure and run the
client processes using NonStop TS/MP.
Set up the server pool environment in a NonStop TS/MP
configuration, then run the NonStop TS/MP server.
These four variants are discussed in detail in the following paragraphs:
Single-process client
No profile@ORB entity is needed unless you wish to override the system settings in the configuration database. A common case where
you might want to override these settings is to control the TCP/IP process to be used (the default TCP/IP process is
$ztc0).
Single-process server
A unique profile must exist for each logical server. If the profile uses the TCP/IP transport protocol only, you can simply run the server
process. If the server uses the file-system transport protocol, the server must be run as a named process (for example,
run -
name=/G/process-name). If your server uses a POA configured with the STATELESS state policy, the TS/MP transport protocol is
required to deliver requests. Such servers must be configured as a NonStop TS/MP server pool.
Server-pool client
Clients can run as server pools. You need to set up the environment in a NonStop TS/MP configuration.
Server-pool server
Servers running as server pools require you to set up the environment in a NonStop TS/MP configuration. The sample script shown
below illustrates how the environment is configured (this example is from the Bank sample program supplied with NonStop CORBA).
For server-pool environments, HP recommends using a script. If you are not familiar with configuring NonStop TS/MP environments, see the
NonStop TS/MP System Management Manual (note that in TS/MP documentation, server pools are called server classes). The following sample
OSS script illustrates how the environment might be configured:
In the following script, the trace settings have been disabled by placing the comment character open bracket
[ in front of the line. For more
information about tracing see
Tracing and Debugging Applications.
#
#
# Bank server PATHMON start -up and configuration script.
#
# Usage: start_server [-v] [-d]
#
# The -v option displays the input used to configure the server class.
# The -d option causes extra application output to be displayed.
# This output is directed to the file "server.log".
#
export PATHMON=smon
export SERVER_CLASS=BANK-SERVER
# Get options if supplied
while getopts ":vd" opt; do
case $opt in
v ) VERBOSE="-v" ;;
d ) APPL_TRACE_ENABLED="set server env BANK_CFG_LOG=TRUE" ;;
\? ) print "usage: start_server [-v] [-d]"
return 1