NonStop CORBA 2.3 Administration Guide Next NonStop CORBA 2.3 Administration Guide Part number: 520550001 Published May 2002 Legal Notice Abstract This manual provides information for administrators on how to configure your system for Compaq NonStop" CORBA® 2.3. The information provided focuses on the Compaq-specific implementation of the Object Management Group's CORBA standards. Product Version: Compaq NonStop" CORBA® 2.
Remote Invocations NonStop CORBA 2.
Starting NSDEnvironServer Configuration Data Used by NSDAdminServer and NSDEnvironServer 3.
Removing a Naming Context or Name Viewing an Object Reference Saving an Object Reference Refreshing the Display Troubleshooting the Servers Load Balancing 4. Configuration and Management Using Commands Configuration Setting Environment Variable (env.sh file) Customizing the env.
Modifying Running Server Pools Altering a Server Pool Managing the Distributed Object Environment The Distributed Object Environment NonStop CORBA Configuration Management NonStop CORBA Performance Tuning NonStop CORBA Troubleshooting What You Need to Know 5. Managing Application Processes The Application Environment Application Configuration Management Application Server Protocols File-System Protocol TS/MP Protocol Application Performance Tuning What You Need to Know A.
B. Additional cfgmgt Commands bye, exit, quit cfgmgt dbcreate dbname dbremove dumpdb entities entity entityaddkeyvalue entitydelete entitydeletekey entitykeys entitykeysvalues profile source C. /bin Directory Files D. Log Files E.
Copyright 2002 Compaq Information Technologies Group, L.P. Compaq, the Compaq logo, Alpha, Atalla, CLX, Deskpro, Enform, Expand, Guardian, Himalaya, Inspect, Integrity, NonStop, OpenVMS, PayMaster, ProLiant, ServerNet, SignMaster, SNAX, Tandem, VAX, VMS, and WebSafe are trademarks of Compaq Information Technologies Group, L.P. in the U.S. and/or other countries.
information in this document is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for Compaq products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty.
About This Guide Prev Next About This Guide Table of Contents Who Should Read This Guide Organization of this Guide Manuals in the NonStop CORBA Set Your Comments Invited Reader Comments Notation Conventions As originally installed, your NonStop" CORBA system is fully functional, but you may wish to alter the configuration at some later time. The NonStop" CORBA® Administration Guide describes how to use the Compaq NonStop" Distributed Component Console software to modify the configuration of your system.
entities in a NonStop CORBA configuration database. Appendix B, Additional cfgmgt Commands, describes additional commands that you might occasionally use. Appendix C, /bin Directory, describes files that in the /bin directory of the product installation. Appendix D, Log Files, names the processes that generated log files Appendix E, Troubleshooting,.provides links to parts of the NonStop CORBA that discuss troubleshooting. Manuals in the NonStop CORBA Set The NonStop CORBA 2.
You will receive immediate acknowledgement of your message only when you use e-mail Reader Comments In your message, please include the following information: Your name Your company name Your company address Daytime telephone number FAX number Your e-mail address Also, please include the document title associated with your comments: To help us improve our software documentation, please answer the following questions in your comments: ● Are the documents technically accurate? ● Do they provide the inform
[] | ... "" Other punctuation Long Commands Brackets enclose optional syntax items. For example: TERM [\system-name.]$terminal-name INT[ERRUPTS] A group of items enclosed in brackets is a list from which you can choose one item or none. The items in the list may be arranged either vertically, with aligned brackets on each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines.
Chapter 1. NonStop CORBA Architecture Prev Next Chapter 1. NonStop CORBA Architecture Table of Contents Distributed Object Computing Infrastructure Services Availability Scalability Data Integrity Tools What is CORBA? What Does It Do? Server Side Remote Invocations NonStop CORBA 2.
Resource Managers Transaction Context Controlling Transactions Application Portability Distributed Object Computing CORBA is the acronym for Common Object Request Broker" Architecture, the Object Management Group" (OMG")'s open, vendor-independent architecture and infrastructure that computer applications use to work together over networks. Compaq NonStop CORBA 2.
subsystems. The ORB supports fault tolerance by using TS/MP as a process manager for ORB processes. TS/MP provides automatic restart when a server process fails. Automatic restart is also available to application components that use TS/MP server pools. Scalability Scalability allows a system to grow dynamically as usage increases.
For each object type, such as your shopping cart, you define its interface in OMG IDL. The interface definition fixes the operations that can be performed on objects of that type, and the input and output parameters for each. This interface definition is independent of your programming language, but maps to all of the popular programming languages through a set of OMG standards: OMG has standardized mappings for C, C++, Java, COBOL, Smalltalk, Ada, Lisp, Python, and IDLscript. This is the essence of CORBA.
interface corresponds to a class. A property is defined as an attribute, which is mapped by the IDL compiler to get and set methods; a read-only attribute maps to a get method only. An operation corresponds to a method; parameters must be specified as in, out, or in/out The following example illustrates an IDL interface description.
Remote Invocations Figure 13 diagrams a remote invocation. In order to invoke the remote object instance, the client first obtains its object reference. (How clients obtain object references is not discussed in this section.) To make the remote invocation, the client uses the object reference along with the name of the method and any method arguments.
Although the ORB can tell from the object reference that the target object is remote, the client cannot. Nothing in the code that the user writes identifies the location of the target object. That information is contained in the object reference. This design ensures location transparency, the CORBA principle that simplifies the design of distributed object computing applications. Figure 14 describes a distributed object computing development process. Figure 1.4. Distributed Object Development Process 1.
If the client program uses the dynamic invocation interface instead of the static approach, the compiled IDL must be written to the interface repository, and the DII access library is linked to the client instead of the stub generated by the IDL compiler. Using the DII, the client can obtain a method description and then create an argument list and request. NonStop CORBA 2.3 Architecture The NonStop CORBA 2.
protocol called GIOP. GIOP messages can be sent over virtually any data transport protocol, such as TCP/IP, the TS/MP Pathsend interface, the NonStop Himalaya file system, and many others. To ensure out-of-the-box interoperability between ORB products, the IIOP specification requires that ORBs send GIOP messages over TCP/IP connections because TCP/IP is the standard connection-oriented transport protocol for the Internet. To put it very simply, GIOP + TCP/IP = IIOP.
Client/Server Process A NonStop Himalaya CORBA server is any process that resides on the same NonStop Himalaya system or Expand network. An object contained by a NonStop Himalaya CORBA server can act as a client, a server, or both. CORBA objects execute from within a server process. Two types of CORBA servers are available on the NonStop Himalaya system, stand-alone CORBA servers or CORBA servers within the TS/MP environment.
Client System Remote clients, or network clients, are application processes that reside on other systems and other vendors ORBs. They act as CORBA clients to CORBA application objects or any of the COS services that reside on the NonStop Himalaya. They normally interact with those services through the Location Service Daemon (LSD) and the Comm servers. The interaction between the remote clients and the remote services is always done through the standard IIOP protocol.
multiple Comm servers can be configured. Using multiple Comm Servers allows larger volumes of traffic to be handled because the load is spread across multiple processors. Parallel Library TCP/IP Another way to increase capacity and fault tolerance is to configure the IIOP connectivity components of your system (Comm Server, LSD, ILSD, and BSD processes) to use Parallel Library TCP/IP. With this configuration, multiple Comm Server processes running in a pool can share the same port.
With this configuration the single port can be serviced by up to 16 actual processes with only one Comm Server pool and only one configuration database entry. Similarly, up to 16 Location Service Daemon (LSD) processes can be configured to avoid a potential LSD bottleneck. The GIOP over TS/MP protocol can be used in combination with Parallel Library TCP/IP to provide two different dimensions of scalability.
Interoperable Location Service Daemon (ILSD) The Interoperable Location Service Daemon (ILSD) is a component of the Interoperable Naming Service. The ILSD services requests for name resolution for names in the Uniform Resource Locator (URL) format. When the ILSD receives such a request, it returns a forwarding reply containing the object reference of the named object.
Test %1 %2 %3 172.26.27.80 is the host IP address, 4506 is the BSD port number. NonStop CORBA does not use the BSD default port of 900, but uses a port dynamically assigned during installation. The port number can be altered using the Console or the cfgmgt utility modifying the bsd1@ORB entity. Interface Repository Database The Interface Repository (IR) is a set of files that contain definitions of object interfaces hosted on your NonStop CORBA application servers.
transactional management and services infrastructure, application providers can deliver reliable objects that fully support the ACID properties of a transaction service. NonStop CORBA 2.3 provides two language bindings: OTS (which is used when developing in C++) and JTS (Java Transaction Service). JTS is the Java API used when developing objects with Java.
A Look at Transactions The word transaction connotes a unit of work in which a client can modify one or more objects. At the end of the transaction process, a decision is made whether to commit or rollback the changes made in effect of the transaction. This is a group decision based on the outcome of each individual piece of work associated with the transaction. Committing a transaction means that all of the changes made during the transaction will be made durable.
Two-Phase Commit Process The OTSTM uses a two-phase commit process to ensure that each transaction maintains the ACID characteristics associated with transaction processing. To understand the workings of a two-phase commit, it is helpful to first understand the processing of a rollback operation. When a transaction terminates, all participants associated with the transaction must either commit or roll back.
When a client initially begins the transaction, a transaction context is generated that is associated with the client thread. The transaction context is the transaction information associated with a specific thread. The objects participating in the transaction use the transaction thread throughout the lifespan of the transaction.
Chapter 2. System Structure Prev Next Chapter 2.
The NSDEnvironServer process provides services for a particular security domain. Generally, the NSDEnvironServer processes are created by the NSDAdminServer on demand.
gtacl -c 'stop $ZDAS' Starting NSDAdminServer as a PATHMON Process To run the NSDAdminServer under PATHMON control: 1. Set the required environment variables (see The env.sh Source File). 2. At the OSS command prompt, give the command adminstart, with or without one or more of these options: -a admin-db specifies an administration database other than that defined by the NSDOM_ADMIN_DB environment variable. -t causes the NSDAdminServer to generate additional output.
specifies a file containing configurations to manage. -d domain-name specifies the name of the domain managed by the server. A corresponding profile ES_domain must exist in the administration configuration database. By default the logon name is used as the domain name. -n directs the server not to scan for configurations to manage. -t causes the NSDAdminServer to generate additional output. This output is typically used for troubleshooting.
Chapter 3. Configuration and Management Using the Console Prev Next Chapter 3.
Managing Naming Service Data Displaying the Naming Service Hierarchy Adding a Naming Context Renaming a Naming Context or Name Removing a Naming Context or Name Viewing an Object Reference Saving an Object Reference Refreshing the Display Troubleshooting the Servers Load Balancing Overview of the Console In previous releases, you configured and managed Compaq NonStop" Services for CORBA® by using a combination of the following: ● Compaq NonStop" Kernel Open System Services (OSS) commands ● Guardian comm
● Control (start and stop) the servers ● View and configure server properties ● View and configure Comm Server mappings ● Manage Naming Service data using the Naming Administrator ● Troubleshoot the servers The Console is recommended for configuring and managing the NonStop Services for CORBA. However, you can still use the command line tools and shell scripts to configure and manage the system if you prefer them (see Configuration and Management Using Commands).
Security Domains A security domain contains the process and configuration data that are manageable under a user name and password. An initial security domain is created when you install the product. If you choose to do so, you can define additional security domains for a host system. A security domain is composed of one or more business domains.
them if desired. Business Domains A business domain contains a collection of related business application processes and configuration data. Multiple business domains can be defined for one security domain. An initial business domain is created when you install the product. ● Adding a New Business Domain ● Removing a Business Domain ● Renaming a Business Domain Adding a New Business Domain Add additional business domains if, for example, you want to partition your security domain.
Renaming a Business Domain To rename a business domain: 1. Select the NonStop Services for CORBA item in the tree that corresponds to the business domain you want to rename. 2. View the properties for the business domain. 3. Alter the domain name field as desired, then click OK. Monitoring the Servers After connecting to the host system, the Console retrieves information about the configuration and status of each server.
Indicator Meaning Server is running. At least one server component is not running normally. Server is stopped. In the following display, all of the servers are running: Detailed Server Status Display To display detailed server status information, do one of the following: ● Right-click NonStop Services for CORBA and select Server Status from the pull-down menu. ● Select NonStop Services for CORBA and select Server Status from the View menu.
Type of server pool.
Status Information for Back-End Servers You can view the status information for the back-end servers. You might want to view it to get operational information about the servers. You can also enable and disable tracing for the back-end servers. To view the status information: 1. Highlight the name of a security domain in the tree (a security domain name appears along with the name of the system at the highest level in the tree). 2. Select Server Status from the View Menu.
Here is an example: Controlling the Servers After connecting to a host system and selecting security and business domains, you can: ● Start the servers ● Stop the servers ● Stop managing the servers Start or stop the servers in the following situations: ● You have connected to a host system and selected security and business domains, and the server status indicators show that one or more servers is either stopped or is not running normally. Stop all of the servers and restart them.
Starting the Servers Do one of the following: ● Right-click NonStop Services for CORBA and select Start from the pull-down menu. ● Select NonStop Services for CORBA and select Control>Start from the Admin menu. ● Select NonStop Services for CORBA and click Start running on the tool bar. The status indicator showing that the server is running ( ) should appear on the left-hand side of each server.
Viewing and Configuring Server Properties The servers have default values defined for their properties. You do not have to change these values; however, server configuration properties determine how well the client request load is balanced, so you might want to tailor server configuration properties to meet your needs. Note Any changes to the server properties require you to stop and restart the servers. To display General properties and then view properties for a specific server: 1.
The following tabs are available: ● General Properties ● Naming Service Properties ● Event Service Properties ● Object Transaction Service (OTS) Properties ● Object Transaction Service XID (OTSXID) Properties ● Location Service Daemon (LSD) Properties
● Bootstrap Daemon (BSD) Properties ● Comm Server Properties ● Interface Repository Database (IRD) Properties ● Interoperable Location Service Daemon (ILSD) Properties General Properties ● Required Configuration ● Advanced Configuration Required Configuration Property Description Meaningful name for the security domain. Can contain alphabetic, Domain name numeric, and underscore characters.
Name Primary CPU Backup CPU I/O Size Use default Use Parallel Library TCP/IP for Comm Servers The PATHMON process for the NonStop Services for CORBA for a particular business domain. The default name consists of "$" and the environment prefix character, followed by NDM. The process name can be altered when the business domain is initially defined. Number of the CPU designated as the primary CPU for the PATHMON process. Number of the CPU designated as the backup CPU for the PATHMON process.
Server Configuration Options Property Description Maximum number of copies of a server process that can run in a server pool at the Maximum Server same time. The range of values is 0 through 4095. Number of static servers, which are processes that are started automatically when the TS/MP environment starts. (Dynamic servers are started as needed by the PATHMON process.) The range of values is 0 through 4095. The value must not Static Servers exceed the value of the Maximum servers field.
Event Service Properties ● Basic Configuration ● Server Configuration Options ● Troubleshooting Options Basic Configuration Property Description IP address of the host system on which the server is listening. Host address The host systems available in the drop-down list are those managed by the selected TCP process. Port number on the host system to which the server is listening. Port number The port number cannot be used by any other process on the host system.
Priority at which the server process is run. The range of values is 1 through 199, the highest priority being 199. Number of attempts to restart the server process, in the event of its abnormal Autorestart attempts termination. The maximum number is 32767. Log file name Name of the file to which server process output is written.
Max links Link depth Send timeout Log file name Maximum number of links that a server process in a server pool can have to all LINKMON processes on the host system. For example, if the Link depth field is set to 10 and there are 3 CPUs in the host system, set the Max links field to 30 to avoid queueing requests at the server process. While a server process is processing a request, the maximum number of queued requests is the value of the Max links field minus 1.
Priority at which the server process is run. The range of values is 1 through 199, the highest priority being 199. Number of attempts to restart the server process, in the event of its abnormal Autorestart attempts termination. The maximum number is 32767. Log file name Name of the file to which server process output is written. Process priority Location Service Daemon (LSD) Properties The Location Service Daemon (LSD) acts as a well-known entry point for initial external client connections.
Property Description If the check box for Use Parallel Library TCP/IP is not checked, this field is set to Maximum servers one. If it is checked, you may specify the number of servers. If the check box for Use Parallel Library TCP/IP is not checked, this field is set to one. If it is checked, this field is set to match the number of Maximum Servers you Static servers specify. Or if you enter a number of Static Servers, the Maximum Servers field will be set to match what you enter here.
Name of the TCP process that is managing the selected host address. One TCP process can manage multiple host addresses. TCP processes can be TCP process spread across CPUs for load balancing. If the "Use Parallel Library TCP/IP" check box is checked you must specify a TCP process that is enabled for Parallel Library TCP/IP. Use Parallel Library TCP/IP If checked, enables the LSD to use Parallel Library TCP/IP.
Comm Server Properties for Original TCP/IP ● Number of Comm Servers ● Basic Configuration ● Server Configuration Options ● Troubleshooting Options Property Description As the client requests increase, you can increase the number of Comm Number of Comm Servers Servers to handle the additional load. Basic Server Configuration Property Comm server Description Number of the Comm Server for which you want to view or configure properties.
Log file name Name of the file to which server process output is written. Comm Server Properties for Parallel Library TCP/IP ● Configuration for Group ● Basic Server Configuration ● Server Configuration Options ● Troubleshooting Options Property Description If more than one group is specified, this drop-down menu allows you to Configuration for Group choose which group to view. Number of Groups The number of groups specified. The usual number is one.
Autorestart attempts Log file name Number of attempts to restart the server process, in the event of its abnormal termination. The maximum number is 32767. Name of the file to which server process output is written. Interface Repository Database (IRD) Properties The Interface Repository Database is a set of files that contain definitions of object interfaces hosted on the application servers.
Autorestart attempts Create delay Delete delay Max links Link depth Send timeout Log file name Number of attempts to restart the server process, in the event of its abnormal termination. The maximum number is 32767. Length of time in microseconds requests are queued while a LINKMON process waits for a server (static or dynamic) to become available. When this time period is exceeded, the PATHMON process creates a dynamic server to process requests. The maximum time is 18 hours.
Name of the TCP process that is managing the selected host address. One TCP process can manage multiple host addresses. TCP processes can be TCP process spread across CPUs for load balancing. If the check box for Use Parallel Library TCP/IP is checked you must specify a TCP process that is enabled for Parallel Library TCP/IP. Location where the Interoperable Location Service Daemon expects to URL directory find object reference files.
Max links Link depth Send timeout Log file name Maximum number of links that a server process in a server pool can have to all LINKMON processes on the host system. For example, if the Link depth field is set to 10 and there are 3 CPUs in the host system, set the Max links field to 30 to avoid queueing requests at the server process. While a server process is processing a request, the maximum number of queued requests is the value of the Max links field minus 1.
Source address IP address of the remote client host system sending a request through a Comm Server Process name of the Comm Server that handles requests from the remote client host Comm Server system Last accessed Date and time the Comm Server was last accessed For example: Adding a Comm Server Mapping 1. Display the Comm Server Map. 2. Click Add. The Add Comm Server Map Entry dialog appears. 3.
3. To exit the Comm Server Map display and save your changes, click OK. 4. To exit without saving changes, click Cancel. Managing Naming Service Data The Naming Service Administrator allows you to manage the data in the Naming Service ● Displaying the Naming Service Hierarchy ● Adding a Naming Context ● Renaming a Naming Context or Name ● Removing a Naming Context or Name ● Viewing an Object Reference ● Saving an Object Reference ● Refreshing the Display .
Left Pane The Naming Service hierarchy is displayed in a tree structure. Initially, the Root Naming context is expanded to show the naming contexts and names at the root level of the hierarchy. Naming contexts are indicated by a folder icon and can be expanded to show the names contained in them. Naming contexts and names consist of two attributes separated by a period: id.kind. For example, NSDOMES.EventChannelFactory.
information. Adding a Naming Context 1. Display the Naming Service hierarchy. 2. Do one of the following: ● Right-click an existing naming context and select New Context from the pull-down menu. ● Select an existing naming context and select New Context from the Action menu. 3. When the Input dialog appears, type the new naming context in id.kind format. The identifier attribute (id) is required.
Viewing an Object Reference View an object reference for a name to verify or examine its properties, such as its name binding, type ID, or available protocols for containing the object. 1. Display the Naming Service hierarchy. 2. Do one of the following: ● Double-click the name in the hierarchy. ● Right-click the name in the hierarchy and select View IOR from the pull-down menu. ● Select the name in the hierarchy and select View IOR from the Action menu.
2. If the status display does not reveal the cause of the problem, stop and restart the servers. 3. If one or more servers are still not started, review the log files. If a server is not functioning as expected: 1. Review the log file. 2. If the log file does not reveal the cause of the problem, enable the Tracing option on the server properties dialog. 3. If tracing does not reveal the cause of the problem, enable Debug for the server on the server properties dialog.
Servers (see Viewing and Configuring Comm Server Mappings) ● Selecting a TCP process from a list of those available when you define a security domain (see Adding a New Security Domain) or when you configure server properties (see Viewing and Configuring Server Properties) ● If Parallel Library TCP/IP is configured, Comm Servers are chosen on a round-robin basis rather than on load (see Comm Server Properties and Parallel Library TCP/IP. Prev Chapter 2. System Structure Up Home Next Chapter 4.
Chapter 4. Configuration and Management Using Commands Prev Next Chapter 4. Configuration and Management Using Commands Table of Contents Configuration Setting Environment Variable (env.sh file) Customizing the env.
The Distributed Object Environment NonStop CORBA Configuration Management NonStop CORBA Performance Tuning NonStop CORBA Troubleshooting What You Need to Know Configuration This section assumes that you have successfully completed installing your Compaq NonStop CORBA system as described in Installing NonStop CORBA. The installation process gives you a fully configured system. Later you may wish to make modifications to your configuration.
also shows the default script settings. Variable Default Setting* NSD_ROOT /usr/tandem/nsdoms MY_ROOT $NSD_ROOT NSD_DIR /G/SYSTEM/ZORBSDK or /G/SYSTEM/ZORBRTK NSD_SUBVOL "\$SYSTEM.ZORBSDK" or "\$SYSTEM.ZORBRTK" MY_SUBVOL $NSD_SUBVOL NSD_SRL_SUBVOL $NSD_SUBVOL Description Sets the root OSS directory for your NonStop CORBA installation. Sets up a custom NSD_ROOT variable to allow for multiple custom installations. By default, the value is the same as NSD_ROOT.
NSD_SRL_DIR $NSD_DIR _SRL_01 File NSDSRL in the NSD_SRL_SUBVOL NSDOM_CFG_DBM $MY_SUBVOL.NSDCFGDB NSDOM_ADMIN_DB Set by installer MY_PREFIX Z MY_COLLECTOR '$0' COMP_ROOT Specifies in OSS format the Guardian volume and subvolume where the NonStop CORBA for Java SRL resides. By default, the value is the same as NSD_DIR. A DEFINE that specifies the location of the NonStop CORBA SRL. Specifies the NonStop Kernel filename for the configuration database.
JAVA_HOME /usr/tandem/java JREHOME $JAVA_HOME JREHOME $JAVA_HOME/jre NSD_BOOTCP $JAVA_HOME/lib/tandemvm. zip:$JAVA_HOME/lib/tsmp. jar:$JAVA_HOME/lib/ classes.zip NSD_BOOTCP $JREHOME/lib/tandemvm. jar:$JREHOME/lib/rt. jar CLASSPATH $CLASSPATH:$NSD_ROOT/idl/ nsdidl.jar:$NSD_ROOT/idl/ jorb/jar:$NSD_ROOT/idl/ jts.jar:$NSD_ROOT/idl/ ejb.jar PATH $PATH:$NSD_ROOT /bin:$NSD_ROOT/ bin/unsupported: $COMP_ROOT/usr/lib: $JAVA_HOME/bin Sets path for NSJ.
particular entity each key must be unique. While there are some standard entities in the configuration database, the specific entities in a particular database is installation-dependent. Appendix A lists some standard entities and their contents.
Displaying a Particular Entity To display the entity whose name is entity-name, use this command: entity entity-name This command displays the entity's keys and their values. For example, the command entity NS@ORB could result in the output: use_comm_server true tcp_server true fs_server true tsmp_server true server_class NS Changing an Entity To change an entity, type the entity name followed by an open brace. This command causes subsequent lines to modify the entity.
● exit ● quit Managing NonStop CORBA Processes The nsdstart script configures and starts the various processes that comprise the NonStop Services for CORBA. These processes run under the Pathway environment that provides them with capabilities such as auto-restart and scalability. After being started, the NonStop Services for CORBA are ready to receive and process requests. The nsdstop script shuts down the processes that comprise the NonStop Services for CORBA.
Before running nsdstop, be sure the required environment variable settings are in effect. To execute the nsdstop script, enter the following command at the OSS command prompt: nsdstop This command stops the set of processes that comprise the NonStop Services for CORBA. How the nsdstart Script Works Each time it is executed, the nsdstart script does the following: 1. Sets the script variables that specify the NonStop CORBA process names, such as the process names for the Comm Server and Naming Server. 2.
Pathctl File in Use If the Pathway control file is in use, you see an error similar to this: $Z1XY: ERROR - *1017* PATHCTL FILE (012) To remedy this error, define an alternate location for the pathway control file by entering the following command at the OSS command prompt: add_define =_DEFAULTS class=DEFAULTS volume=\$VOL.SUBVOL Substitute the desired volume name for VOL and the desired subvolume name for SUBVOL.
● Remove a Comm Server process ● Manage a NSots transaction manager in a process pool To change the script: 1. Give write permission to the script file nsdstart by using the chmod command. 2. Edit the script, making the desired changes. You can use the vi editor under OSS. 3. Save the changes. Changing the Process Priority 1. Locate the section of the script that defines the server you want to change. 2.
#... COM_SERVER1="$MY_PREFIX"NCA COM_SERVER2="$MY_PREFIX"NCB #... set server maxservers 1 set server numstatic 1 set server process \$$COM_SERVER1 set server AUTORESTART 10 add server CS start server CS #... 3. Edit this section to add another server. Note that new Comm Servers names must have the last letter incremented, giving Comm Servers $ZNCA through $ZNCZ. There is a limit of 26 Comm Servers. Adding a Comm Server to the nsdstart Script #... COM_SERVER1="$MY_PREFIX"NCA COM_SERVER2="$MY_PREFIX"NCB #...
Configuring Two Comm Servers #... COM_SERVER1="$MY_PREFIX"NCA COM_SERVER2="$MY_PREFIX"NCB #... set server set server set server set server maxservers numstatic process process 2 2 \$$COM_SERVER1 \$$COM_SERVER2 set server AUTORESTART 10 add server CS start server CS #... 3. Edit the section to remove the $ZNCB server process, as follows: Removing a Comm Server From nsdstart #... COM_SERVER1="$MY_PREFIX"NCA #...
Configuring NonStop CORBA to Use Parallel Library TCP/IP When NonStop CORBA is initially installed the default configuration is for the original TCP/IP. To configure Parallel Library TCP/IP, perform the following steps: 1. During installation, provide a Parallel Library TCP process name to the prompt beginning: "ENTER the TCP process name here ..." 2. Before starting the subsystem, configure the BSD, LSD, ILSD, and Comm Server(s) to take advantage of Parallel Library TCP/IP.
set server env MY_PREFIX=$MY_PREFIX set server define =_SRL_01, class map, file $NSD_SRL_SUBVOL.
+ * * * set set set set server server server server numstatic 3 process \$bsd1 (CPUs 1) process \$bsd2 (CPUs 2) process \$bsd3 (CPUs 3) set server AUTORESTART 10 set server arglist "-ORBprofile", "bsd1" add server BSD start server BSD Configuring a Comm Server for Parallel Library TCP/IP Use this procedure to change the default Comm Server configuration into a Parallel Library TCP/IP Comm Server. 1. Use the cfgmgt tool to add the key/value pair parallel_ip/true to the default@ORB entity.
set server env NSDOM_CFG_DBM=$NSDOM_CFG_DBM set server define =_SRL_01, class map, file $NSD_SRL_SUBVOL.
1. The Comm Server name must be passed as an argument to the processes in a Parallel Library TCP/IP Comm Server SERVERCLASS. The line in the example above that does this is: * set server arglist "$COM_SERVER1" This Comm Server name must conform to the following convention: = NC<1> where
is the installation prefix (default is 'Z') and <1> is a letter that must be in contiguous ascending order. The letters in must be all upper case.
● Adding, removing, or modifying server pools and processes based on performance queues or changing requirements. ● Making changes based on performance considerations, including load-balancing issues. Using the PATHCOM Interface The OSS scripts supplied with NonStop CORBA enable you to issue a single command to start (or stop) a TS/MP configuration.
Monitoring Status The PATHMON process maintains information about process configurations, process status, and operations statistics.
=info pathway PATHWAY MAXASSIGNS 8 MAXDEFINES 27 MAXEXTERNALTCPS 0 MAXLINKMONS 16 MAXPARAMS 4 MAXPATHCOMS 8 MAXPROGRAMS 4 MAXSERVERCLASSES 4 MAXSERVERPROCESSES 40 MAXSPI 8 MAXSTARTUPS 4 MAXTCPS 0 MAXTELLQUEUE 4 MAXTELLS 32 MAXTERMS 0 MAXTMFRESTARTS 5 OWNER \OSS2.
This sample display shows the PATHMON backup process running in CPU 4. If the PATHMON process encounters an internal error, it writes data-stack information to \SYS.$VOL1.TESTING.MONDUMP. INFO SERVER Command The following example shows the command you would type to display the configuration parameters for a single server pool: = INFO SERVER CS In this command, CS is the logical name defined for the server class in the TS/MP configuration. In this example, the command displays parameters for the Comm Server.
Displaying Status Information Use the STATUS command to display status information about your TS/MP environment, the PATHMON process itself, and server objects. Displaying Environment Status To display status for the overall TS/MP environment, issue the following PATHCOM command: = STATUS PATHWAY The following command gives you a display showing the state of the environment (for example, RUNNING).
= status pathmon PATHMON \OSS2.$YNSD2 -- STATE=RUNNING PATHCTL (OPEN) $DATA07.DEREK.PATHCTL LOG1 S (CLOSED) \OSS2.$Z6GR.#INTER LOG2 (CLOSED) REQNUM 1 FILE PATHCOM PID $Z7YJ PAID 190,0 CPUs 1:0 ERROR=201 WAIT = Displaying Server Pools Status To display status information, type the following: = STATUS SERVER *, DETAIL You get a display showing the number of server processes running, errors, the number of links, and the weight.
$Z02Y SERVER NS PROCESS $AND0 SERVER OTSTM PROCESS $ANO0 RUNNING #RUNNING 1 STATE RUNNING #RUNNING 1 STATE RUNNING 0 ERROR 0 ERROR INFO ERROR 1034 INFO #LINKS 5 WEIGHT 15 ERROR #LINKS 9 WEIGHT 17 INFO INFO = Using the STATUS SERVER command can help you determine whether links are evenly allocated and balanced among server processes in your NonStop CORBA application environment. The #LINKS field shows the total number of current links to a given server process.
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 respecify all parameters, be sure to use the COLD start option of the SET PATHWAY command to restart the TS/MP environment.
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.
NonStop CORBA Configuration Management The NonStop CORBA system is implemented as an application using TS/MP, which provides for scalability and load balancing by allowing multiple processes to work in parallel to perform the same task. TS/MP also provides for availability: its monitor process, called PATHMON, automatically restarts a process that fails.
information about the status and use of communication lines, processes, and related resources. NonStop CORBA Performance Tuning Performance tuning of the runtime environment of the NonStop CORBA system is primarily a matter of deciding on the number and relationships among Location Service Daemon (LSD), Comm Server, and TCP/IP processes: 1. You use PATHCOM to define the number of Comm Servers. 2.
● PATHCOM lets you verify the current configurations of NonStop CORBA runtime processes. ● The NonStop CORBA error log is the primary source of information about NonStop CORBA execution errors. A variable in the NonStop CORBA configuration file controls the error logging. ● The NonStop CORBA trace facility lets you follow the flow of control in an application to discover when and where an error occurred.
NonStop TS/MP Pathsend and Server Programming Manual NonStop TS/MP Management Programming Manual TS/MP server pools, PATHCOM interface NonStop TS/MP and Pathway System Management Guide NonStop TS/MP System Management Manual NonStop DCE Application Programming Guide TACL Reference Manual Introduction to NonStop SQL/MP OSS Programmer's Guide DCE threads TACL command reference Compaq database products Open System Service Management and Operation Guide Open System Services shell and utilities, libraries and
Chapter 5. Managing Application Processes Prev Next Chapter 5. Managing Application Processes Table of Contents The Application Environment Application Configuration Management Application Server Protocols File-System Protocol TS/MP Protocol Application Performance Tuning What You Need to Know Managing Compaq NonStop CORBA 2.
Note Although the figure shows a NonStop SQL/MP database, your application can access other types of databases. Not all CORBA servers access databases. This topic describes the issues involved in configuration management and performance tuning for NonStop CORBA application components.
Application Configuration Management NonStop CORBA lets you use any of the following types of processes as application servers: ● Stateless server pool ● Stateful server pool ● Single process Whether a server runs as a server pool or as a single process depends on two configuration steps: ● For a server to run as a server pool, you must define the server in a PATHCOM configuration file.
rather than one line per bank teller). This factor makes it attractive to design classes to be stateless to maximize throughput. However, in some cases, it would be inconvenient or costly for an object to be stateless. For example, if an object returns the results of a large SQL query to a client using a cursor, the client must make multiple method invocations on the server.
If you want a NonStop CORBA client to communicate with a NonStop CORBA for C++ or NonStop CORBA for Java application server through the file-system protocol, you must specify the following setting in the client profile: fs_client true You can add this setting to the client profile using the Configuration Management Tool.
NonStop CORBA for Java application server through the file-system protocol, you must specify the following setting in the client profile: fs_client true You can add this setting to the client profile using the Configuration Management Tool Further, suppose the profile of a NonStop CORBA for Java application server specifies the following settings: fs_server true tcp_server true use_comm_server true In this case, a remote client can use TCP/IP over IIOP to communicate with the NonStop CORBA for Java applicat
Application Performance Tuning Application performance tuning for NonStop CORBA application servers includes: ● Determining the best relative locations of clients, servers, and data ● Managing application server pools Server-pool management includes deciding how many server processes each pool requires and detecting when a performance problem results from a factor other than an insufficient number of server processes. In general, performance tuning of stateless server pools is straightforward.
● ● NonStop CORBA error-logging and trace facilities Procedures and considerations for managing databases protected by NonStop TM/MP Prev Chapter 4. Configuration and Management Using Commands Up Home Next Appendix A.
Appendix A. Configuration Database Entities Prev Next Appendix A.
Standard Entities Entity bsd1@orb default@ORB default@trace Purpose Program profile for Bootstrap Daemon Default parameters for ORB operation Global setting for trace flags Operating information for NonStop CORBA event_service@event_service_settings Event Service Program profile for NonStop CORBA Event event_service@ORB Service Program profile for Interoperable Location ilsd1@ORB Sercie Daemon ird1@ird_settings Operating information for Interface Repository Program profile for Interface Repository ird1@ORB
default@ORB comm_server_groups The number of Comm Server groups when Parallel Library TCP/IP is enabled. Not used when Parallel Library is not enabled. comm_serverx@server_config If Parallel Library TCP/IP is enabled, stores configuration information for the second and subsequent server groups. The character x is replaced by b for the second group, by c for the third group, and so on. data_dir_oss The OSS directory in which the volatile data for this configuration are stored.
product_dir_oss The OSS directory in which the product files were installed. stack_size Defines how many bytes are allocated for new thread stacks. Default is 65536, minimum is 16384, maximum is 32768000. tcp_process The default TCP process (used when none is explicitly specified). trace_file The location to which trace output is written. Use to cause trace messages to appear on the terminal (standard output). Use a file name to cause trace messages to be written to the file.
IRIORFILE Specifies the filename to which the Interface Repository (IR) object references are stored. NSName Specifies the name under which the Interface Repository Daemon (IRD) is registered in the Naming Service. lsd1@ORB parallel_ip Specifies whether or not Parallel Library TCP/IP is enabled. NS@name_service_settings DatabaseName Specifies the location of the naming-service database file. RootNamingContextIOR The root naming context object reference.
tcp_process The TCP process associated with host_name, can be omitted if using the default TCP process $ZTC0. Client and Server Protocol Specifications To make and receive object requests, NonStop CORBA programs need transport-protocol information. This information is used by the ORB component of a client or server program. An entity of the form name@ORB defines a NonStop CORBA program profile with the given name. This profile is used with the CORBA program command-line argument -ORBprofile name.
1. Pathsend 2. File system 3. IIOP By default, the three transport protocols are enabled for a NonStop CORBA program. When you want to limit a client so that it uses only some of the protocols, you can do so by explicitly disabling a protocol in the program profile. For example, to use only the IIOP protocol, specify a program profile in which Fs_client and tsmp_client are set to false.
of the POA policies depend on the particular transport protocol. Details about these relationships are explained in: ● Pathsend Protocol ● File System Protocol ● IIOP Protocol The following table shows the server protocol keys and values that can appear in a NonStop CORBA program profile. Server Protocol Keys and Values Key Possible Values Default Value Operational Characteristics Pathsend protocol; Uses the TS/MP context-sensitive tsmp_server true or false false protocol.
● The server is running in a TS/MP server pool and your object is associated with a POA that has a stateful policy. When your server produces object references that specify the file-system protocol, the process name is included as part of the object references. Later, clients using the object reference make requests and those requests are directed to the identically named process. For this reason, the server process must run as a named process.
Valid TCP process name tcp_process use_comm_server true or false Dot decimal IP address or host name that can be resolved to an host_name IP address Integer port_number Prev Chapter 5. Managing Application Processes Up Home $ZTC0 false None None Next Appendix B.
Appendix B. Additional cfgmgt Commands Prev Next Appendix B. Additional cfgmgt Commands Table of Contents bye, exit, quit cfgmgt dbcreate dbname dbremove dumpdb entities entity entityaddkeyvalue entitydelete entitydeletekey entitykeys entitykeysvalues profile source The most frequently used cfgmgt commands are covered in Configuration and Management Using Command Tools. This appendix describes additional commands that you might occasionally use.
Either adds a new entity to the current database or, for an existing entity in the current database, does one of the following: entity ● Displays all of its keys and their values ● Changes the values of one or more existing keys Adds one or more new keys entityaddkeyvalue Adds a key and its value to an entity in the current database. entitydelete Deletes an entity from the current database. entitydeletekey Deletes a key from an entity in the current database.
Note dbName must be a fully or partially qualified Guardian file name. If the volume or subvolume name is not specified, it is the default volume or subvolume of the currently logged-on user. Note that, in a Guardian file name, the dollar sign character $ must be preceded by a backslash character \. dbname Returns or sets the name of the current database. dbname [dbName] dbName is the name to which the current database is to be set.
● To transport the database configuration to another system entities Lists all the entities in the current database. entities cfgmgt traverses the entire database in hash order. The entities are not listed in alphabetical order.
Note Each key-value pair must be on a separate line. (If necessary, you can continue a long line by ending it with a backslash (\) and continuing on the next physical line), for example: entity Entity1 { key1 value1 key2 value2 key3 value3 } entityaddkeyvalue Adds a key and its value to an entity in the current database. entityaddkeyvalueentity-namekey value entity-name is the name of an entity. If entity-name does not exist, entityaddkeyvalue adds it to the current database, along with the key value pair.
entitydeletekey Deletes a key from an entity in the current database. entitydeletekeyentity-namekey entity-name is the name of an entity. If entity-name does not exist, entitydeletekey displays an error message. key is the name of the key to be deleted from entity-name. If key does not belong to entity-name, entitydeletekey displays an error message. entitykeys Displays all the keys of an entity in the current database.
is the application name to which the profile is to be set. If application-name does not exist, profile displays an error message. source Reads and processes a script file. sourcescript-filename script-filename is the name of a script file. A script file can contain: ● Any of the cfgmgt commands that this appendix describes ● Any of the constructs that the following table describes source reads each command in the script file and processes it as if it had been entered manually.
$env(variable) substitutes the value of the environment variable for the expression. For example, this code associates the value of the environment variable NSD_ROOT with Environment the key product_dir_oss in the entity default@ORB: variable entityaddkeyvalue default@ORB product_dir_oss $env(NSD_ROOT) Note that $env(variable) is not allowed inside the braces of the entity command. Instead you must use another command such as entityaddkeyvalue.
Appendix C. /bin Directory Files Prev Next Appendix C. /bin Directory Files The files that the following table describes are in the /bin directory of the product installation. In the table, the files are in alphabetical order. File adminstart adminstop bsd cfgmgt config-ems configure cs EventService ilsd init.tcl instcfg.tcl ird irjvm lsd name_servant NSDAdminServer NSDEnvironServer nsdidl nsdstart nsdstop NSotsTM NSotsXID ns_init parray.tcl qa.tcl runadmin runenviron showir skel.
srlfixup tclIndex unconfigure Shell script used to update fixup information for Shared Runtime Libraries (SRLs) One of six support files for cfgmgt program Shell script that can be used to delete configuration and naming service database Prev Appendix B. Additional cfgmgt Commands Up Home Next Appendix D.
Appendix D. Log Files Prev Next Appendix D. Log Files The directory log under the OSS product directory or OSS data directory contains log files for the various NonStop Services for CORBA processes. Normally, the log file contains little or no information perhaps only some startup messages; however, it sometimes contains information about unusual operating conditions. When tracing is enabled for a process, the output goes to the log file by default.
Appendix E. Troubleshooting Prev Next Appendix E.
CORBA, to be running. NonStop CORBA programs are located in the nsdoms directory. Therefore, if the ps e command shows that processes in nsdoms are running, NonStop CORBA is running. Cannot Start CORBA Server Problem: You try to start a Java CORBA server and get the following error message: /home/ecrm/stack: java Server -ORBprofile tcp_server Exception in thread "main" java.lang.
First, set the following environment variables: ● JDK13_HOME contains Suns JDK1.3 home directory ● JORBLITE_HOME contains JorbLite 2.3 home directory ● CLASSPATH contains the third party JAR files Then the following command line will work: %JDK13_HOME%\bin\java -Xbootclasspath:%JORBLITE_HOME%\lib\jorblite.jar;% JDK13_HOME%\jre\lib\rt.jar;.\Authorizer.jar;%classpath% AuthorizerServer %* -ORBlitedbm %JORBLITE_HOME%\lib\lite.
Cannot Run Client (COMM_FAILURE) Problem: When you try to run the client, you get the COMM_FAILURE error message: /home/ecrm/stack: java Client read stack.ior Unexpected system exception during full operation. org.omg.CORBA.COMM_FAILURE: Broken connection minor code: 1314063336 completed: No Solution: Verify that the server is still running. If the server is stopped for any reason, the client displays this error message. Restart the server, and then run the client again.
IP address. If any parameters in the configuration are incorrect, a client might not be able to connect to the server, even if the server is running and the CORBA code in both client and server is 100% correct. For more information about verifying the TCP/IP configuration, see the following problem description and also Verifying TCP/IP Configuration. Problem: When you run the client, you get the COMM_FAILURE error message.
#LOOP0 \NOSYS.$NOIOP 127.0.0.1 LOOP-BACK %HFF000000 OFF N #SN1 \ARNOLD.LAN01 172.17.202.44 ETHERNET %HFFFFFF00 N N ... Total Errors = 0 Total Warnings = 0 Look for the subnet with the device whose IP address matches the IP address for the system you are using. For that device, find out the IP process name, which is the last entry on the line beginning with TCPIP Info SUBNET." In the example above, the process name is \ARNOLD.$ZTC0.
configuration. That is because the second server will use the same IP address and port number as the first server; therefore, all the clients will connect only to the second server, and the first servers object reference will become invalid. That is, if a client will try to use the object reference of the first server, it will fail with the org.omg.CORBA.COMM_FAILURE error message.
Index Prev Index Symbols .profile script, Setting Environment Variable (env.sh file) /bin directory files, table of, /bin Directory Files A ACID properties, The ACID Properties of a Transaction ADD SERVER command, Adding a Server Pool add_define command, Pathctl File in Use admin.
bsd.
Comm server properties, Comm Server Properties Comm server properties for parallel library TCP/IP, Comm Server Properties for Parallel Library TCP/IP Comm server properties for original TCP/IP, Comm Server Properties for Original TCP/IP Commands ADD SERVER, Adding a Server Pool add_define, Pathctl File in Use ALTER SERVER, Altering a Server Pool bye, Exiting cfgmgt cfgmgt, Starting cfgmgt entities, Displaying All Entities entity, Displaying a Particular Entity, Changing an Entity, Adding an Entity entitydel
THAW SERVER, Restarting a Server Pool Commands START SERVER, Adding a Server Pool Common Data Representation (CDR), IIOP Common Object Services, The Common Object Services Configuration overview, Configuration setting env.sh file, Setting Environment Variable (env.
deleting an entity, Deleting an Entity exiting, Exiting cfgmgt starting, Starting cfgmgt Configuration Management Tool (cfgmgt), Configuration Management Tool (cfgmgt) configure script, Customizing the nsdstart Script Console, overview, Overview of the Console Controlling servers, Controlling the Servers CORBA architecture, What is CORBA? What Does It Do? definition of, What is CORBA? What Does It Do? IDL, Server Side objects, What is CORBA? What Does It Do? server side, Server Side CPU, changing, Changing
changing, Changing an Entity deleting, Deleting an Entity display a particular one, Displaying a Particular Entity displaying all, Displaying All Entities entity command, Displaying a Particular Entity entity command, Changing an Entity, Adding an Entity entitydelete command, Deleting an Entity entitydeletekey command, Changing an Entity env.sh file setting, Setting Environment Variable (env.sh file) env.sh file customizing, Customizing the env.sh file Enviroment variables, table of, Customizing the env.
F Fault tolerance, Availability File-system protocol, File-System Protocol, File-System Protocol Fixing problems, Detecting and Fixing Problems Flat transaction model, Application Portability freeze command, Restarting a Previously Defined Pathway Configuration FREEZE SERVER command, Stopping a Runnng Server Pool fs_client@ORB, Standard Entities FS_server@ORB, Standard Entities G General properties, General Properties GIOP, IIOP GIOP over Guardian file system protocol, GIOP Over Guardian File System Protoc
Infrastructure, Infrastructure availability, Availability data integrity, Data Integrity scalability, Scalability services, Services tools, Tools Inter-ORB communication, IIOP Interface Repository Database (IRD) properties, Interface Repository Database (IRD) Properties Interface Repository Database (IR), Interface Repository Database Interoperable Location Service Daemon (ILSD), Interoperable Location Service Daemon (ILSD) Interoperable Location Service Daemon (ILSD) properties, Interoperable Location Serv
ird.log, Log Files lsd.log, Log Files ns.log, Log Files ots.log, Log Files pathcom.log, Log Files Log files, table of, Log Files LSD, Location Service Daemon (LSD) LSD, configuring for Parallel Library TCP/IP, Configuring the BSD, LSD and ILSD for Parallel Library TCP/IP lsd.
architecture, NonStop CORBA 2.3 Architecture NonStop CORBA configuring to use Parallel Library TCP/IP, Configuring NonStop CORBA to Use Parallel Library TCP/IP ORB, The NonStop CORBA ORB NonStop CORBA processes managing, Managing NonStop CORBA Processes NonStop Distributed Component Console, overview, Overview of the Console NonStop SQL/MP, Resource Managers ns.log, Log Files NS@name_service_settings, NS@name_service_settings NS@ORB, Standard Entities NSD_DIR environment variable, Customizing the env.
nsdstop, Differences Between Using Scripts and Using the PATHCOM Interface nsdstop command, Executing nsdstop nsdstop, executing, Executing nsdstop NSotsTM, Transaction Service NSotsTM@transaction_service_settings, NSotsTM@transaction_service_settings NSotsXID, Transaction Service NSotsXID@ORB, Standard Entities O Object Transaction Service XID (OTSXID) properties, Object Transaction Service XID (OTSXID) Properties Object Management Architecture (OMA), Services Object reference saving, Saving an Object Ref
configuring LSD for, Configuring the BSD, LSD and ILSD for Parallel Library TCP/IP Parallel library TCP/IP, Parallel Library TCP/IP Parameters, modifying global, Modifying Global Parameters Based on Changing Requirements PATHCOM, NonStop CORBA Configuration Management PATHCOM commands, Monitoring Status PATHCOM command, Starting a PATHMON Process PATHCOM interface, Using the PATHCOM Interface to Maintain TS/MP Processes pathcom.
Q quit command, Exiting cfgmgt R Reconfiguring server pools, Reconfiguring Server Pools Remote invocation, Remote Invocations Remote services, NonStop CORBA Remote Services Resource managers, Resource Managers runadmin, Starting and Stopping NSDAdminServer S Scalability, Scalability Scripts, Differences Between Using Scripts and Using the PATHCOM Interface Security domain, Security Domains adding, Adding a New Security Domain removing, Removing a Security Domain Server changing CPU, Changing the CPU in Wh
Server properties Bootstrap Daemon (BSD) properties, Bootstrap Daemon (BSD) Properties Comm server properties, Comm Server Properties general properties, General Properties Interface Repository Database (IRD) properties, Interface Repository Database (IRD) Properties Interoperable Location Service Daemon (ILSD)) properties, Interoperable Location Service Daemon (ILSD) Properties Location Service Daemon (LSD) properties, Location Service Daemon (LSD) Properties naming service properties, Naming Service Prope
Status information, back-end servers, Status Information for Back-End Servers STATUS PATHMON command, Displaying PATHMON Status STATUS SERVER command, Displaying Server Pools Status STOP SERVER command, Stopping a Runnng Server Pool stop command, Restarting a Previously Defined Pathway Configuration Subsystem Control Facility (SCF), NonStop CORBA Configuration Management T tcp_client@ORB, Standard Entities thaw command, Restarting a Previously Defined Pathway Configuration THAW SERVER command, Restarting a
tsmp_client@ORB, Standard Entities Two phase commit process, Two-Phase Commit Process Z ZNCA@comm_server, ZNCA@comm_server Prev Appendix E.
