CORBA 2.6 Programmer's Guide for C++

Chapter 4. Deploying a NonStop CORBA Application
Chapter 4. Deploying a NonStop CORBA
Application
The general steps to consider 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 more 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