CORBA 2.6.1 Administration Guide

Because a system shutdown can result in considerable downtime if your application is complex, when you first
configure your environment you should specify global limits that are high enough to allow for growth.
If you discover that you must reconfigure the global parameters, thereby forcing a shutdown, you must re-specify all limits, not just the ones you
are changing. For this reason, you might find it more efficient to change global parameters by editing the
nsdstart script rather than specifying
each specific parameter through PATHCOM.
If you change global parameters by editing the relevant parameters in the nsdstart script, execute the script to cold-start the TS/MP
environment with the new parameters.
If you use PATHCOM to respective all parameters, be sure to use the COLD start option of the SET PATHWAY command to restart the TS/MP
environment.
Reconfiguring Server Pools
Changing application requirements or performance queues can necessitate a reconfiguration of your server resources. For example, you may
find that one application server pool is handling many more requests than expected while another does not receive the expected number of
requests. One way to address this situation would be to increase the maximum number of processes that can be started for the first server pool.
A more complex approach might be to review link access to the first server pool and modify link-related server attributes such as LINKDEPTH
and MAXLINKS.
For a discussion of these attributes and ways to use them to achieve successful load balancing across server processes, refer to
Load
Balancing for Application Server Processes.
You do not need to shut down the environment to reconfigure server pools. Because editing and running the nsdstart script requires a complete
environment shutdown, reconfiguring server pools by using the appropriate PATHCOM commands may be more efficient.
Adding a Server Pool
To add a server pool, use the SET SERVER and ADD SERVER commands. Then use the START SERVER command to start the pool. For details about
how to do this, refer to the
nsdstart script.
Modifying Running Server Pools
To remove or alter a running server pool, you must:
1. Freeze the server pool
2. Stop the server pool
3. Delete or modify the server pool
4. Thaw the modified server pool
5. Start the modified server pool
Stopping a Running Server Pool
Before you can modify a running server pool, you must stop it. First, use the FREEZE SERVER command to disable server communications
with other processes in the environment. After a server pool is frozen, you can stop it by issuing a STOP SERVER command.
For example, the following commands stop all server processes in server pool NS:
= FREEZE SERVER NS
= STOP SERVER NS
To stop all server pools in your TS/MP configuration, use the following two commands:
= FREEZE SERVER *
= STOP SERVER *
To confirm that server pools are frozen or stopped, use the STATUS SERVER command.
Once the server pool is stopped, you can use PATHCOM commands to either delete the server pool or to modify the server attributes.
Restarting a Server Pool
To restart server pool NS, you must first thaw the server, then start it, as shown:
= THAW SERVER NS
= START SERVER NS
The following commands restart all server processes:
= THAW SERVER *
= START SERVER *
Altering a Server Pool
Alter a server pool by using the ALTER SERVER command. For example, the following series of commands changes the priority at which the
server CS runs:
ALTER SERVER Command
= FREEZE SERVER CS
= STOP SERVER CS
= ALTER SERVER CS, PRI 50