CORBA 2.6 Administration Guide

among server processes in your NonStop CORBA application environment.
The #LINKS field shows the total number of current links to a given server process. The WEIGHT field indicates
how heavily the server process is used relative to how heavily other processes in the server pool are used. In the
example above, process $ANO0 has nine links and a weight of 17; thus it is the hardest working process in the
server pool at the moment.
Displaying Statistical Information
To display statistical information about a PATHMON process, type the following PATHCOM command:
= STATS SERVER PROCESS-SERVER
Refer to the TS/MP System Management Manual for details about interpreting the output from this command.
Modifying Global Parameters Based on Changing Requirements
As your application needs change, requirements for your TS/MP configuration will change. If your application
grows, adjustments might be necessary to satisfy your transaction throughput and response-time requirements and
to update or expand the system to provide needed resources.
For example, you might need to increase the maximum number of application-server processes to satisfy a
growing demand for links to servers. In response to your changing requirements, you might need to specify not
just new attributes for your server pools but also new global limits and parameters for the TS/MP environment.
Caution: You cannot specify new global parameters while the PATHMON environment is running. You
must first shut down the entire configuration before you can install the new parameters.
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.