HP NonStop CORBA 2.6 Administration Guide HP NonStop CORBA 2.6 Administration Guide Part number: 525935001. Published November 2003. Legal Notice Abstract This manual provides information for administrators on how to configure your system for HP NonStop" CORBA® 2.6. The information provided focuses on the HP-specific implementation of the Object Management Group's CORBA standards. Product Version: HP NonStop" CORBA® 2.
GIOP Over TS/MP Protocol GIOP Over Guardian File System Protocol IIOP over SSL Portable Interceptors Client/Server Process NonStop CORBA Remote Services Client System Configuration Database Comm Server Parallel Library TCP/IP Location Service Daemon (LSD) Interoperable Location Service Daemon (ILSD) Bootstrap Daemon (BSD) Interface Repository Database The Common Object Services Naming Service Event Service Transaction Service Transaction Manager (OTSTM) Two-Phase Commit Process Resource Managers Transaction
Connecting to Host System Managing Business and Security Domains Security Domains Business Domains Monitoring the Servers Server Status Indicators Detailed Server Status Display Status Information for NSDAdminServer and NSDEnvironServer Controlling the Servers Starting the Servers Stopping the Server Stopping Managing the Servers Viewing and Configuring Server Properties General Properties Naming Service Properties Event Service Properties Object Transaction Service (OTS) Properties Object Transaction Servi
Using the Console to Troubleshoot the Servers Load Balancing 4. Configuration and Management Using Commands Configuration Setting Environment Variables (env.sh file) Customizing the env.
NonStop CORBA Configuration Management NonStop CORBA Performance Tuning NonStop CORBA Troubleshooting 5. Managing Application Processes The Application Environment Application Configuration Management Application Performance Tuning 6. Configuring Security Features IIOP/SSL Transport Protocols Configuring and Managing Private Keys and Certificates profile in env.
NSotsTM@transaction_service_settings NSotsXID@ORB profile@ORB ZNCA@comm_server Client and Server Protocol Specifications Client Protocols Server Protocols Protocols Common to both Clients and Servers OpenSSL Cipher List for Use with ssl_ciphers Pathsend Protocol File-System Protocol IIOP/SSL Protocol IIOP Protocol Indirect Server Protocol Keys and Values B.
Detecting and Fixing Problems with Running Applications Cannot Start HP NonStop Console Cannot Start CORBA Server Shared Library ioser12 Could Not Be Found Cannot Stop CORBA Server Cannot Run Client (COMM_FAILURE) Verifying TCP/IP Configuration NonStop CORBA Listening on the Wrong Socket Index List of Figures 1.1. Basic NonStop CORBA Subsystems 1.2. NonStop CORBA Remote Services 1.3. Original TCP/IP 1.4. Parallel Library TCP/IP 1.5. Transaction Service Components List of Examples 4.1.
Copyright 2003 Hewlett-Packard Development Company L.P. Hewlett-Packard, HP, the HP invent logo, 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 Hewlett-Packard Development Company L.P. in the U.S. and/or other countries.
subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause in DFARS 252.227-7013. Hewlett-Packard Development Company L.P. 10600 Ridgeview Court Cupertino, CA 95014 USA Rights for non-DOD U.S. Government Departments and Agencies are as set forth in FAR 52.227-19(c)(1,2). Export of the information contained in this publication may require authorization from the U.S. Department of Commerce. HEWLETT-PACKARD DEVELOPMENT COMPANY L.P.
New and Changed Information New and Changed Information This edition of the HP NonStop CORBA 2.6 Adminstration Guide describes the following new features for HP NonStop CORBA 2.6: ● Support for GIOP/IIOP versions 1.1 and 1.2. ● Support for Portable Interceptors. ● Support for IIOP/SSL. All chapters contain minor technical and editorial corrections. HP NonStop CORBA 2.
About This Guide About This Guide Who Should Read This Guide Organization of this Guide Manuals in the NonStop CORBA Set 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 2.6 Administration Guide describes how to use the HP NonStop Distributed Component Console software to modify the configuration of your system.
Chapter 4, Configuration and Management Using Commands, describes how to configure and manage NonStop CORBA by using a command interface. Chapter 5, Managing Application Processes, describes the application environment, configuration management, and performance tuning. Chapter 6, Configuring Security Features, describes configuring private keys and certificates, and configuring applications.
Notation Conventions Syntax Item Bold text UPPERCASE LETTERS Italic letters [] {} | ... Description Bold text in a paragraph indicates a technical term that is defined within the text and also, in some cases, in the NonStop CORBA 2.6 Glossary. Uppercase letters indicate keywords and reserved words; enter these items exactly as shown. Items not enclosed in brackets are required. For example: MAXATTACH Items in Italicletters indicate variable items that you supply.
"" Other punctuation Long Commands A dash in a command usually indicates a separate flag. When quotation marks surround a defined syntax symbol (such as a bracket or brace), they symbolize an actual character that must be entered as shown. For example: "[" repetition-constant-list "]" Punctuation not previously described (such as parentheses, commas, and semicolons) must be entered as shown. For example: error := NEXTFILENAME ( file-name ) ; LISTOPENS SU $process-name.
Chapter 1. NonStop CORBA Architecture Chapter 1. NonStop CORBA Architecture Distributed Object Computing Infrastructure Services Availability Scalability Data Integrity Tools NonStop CORBA 2.
Distributed Object Computing CORBA is the acronym for Common Object Request Broker" Architecture, an architecture and set of specifications developed by the Object Management Group" (OMG"). The Object Request Broker enables objects to transparently make and receive requests and responses in a distributed environment. It is the foundation for building applications from distributed objects. NonStop CORBA 2.6, which is based on OMG CORBA 2.6.
Scalability Scalability allows a system to grow dynamically as usage increases. NonStop CORBA provides scalability in the following dimensions: ● Network connections ● Object Request Broker (ORB) processes ● Application processes Data Integrity In addition, NonStop CORBA ensures the integrity of its own data stores and offers an object transaction service you can use to maintain a secure environment for your applications.
The NonStop CORBA ORB The NonStop CORBA ORB, although conceptually a single entity, is actually a group of mechanisms. Among these are an SRL (Shared Runtime Library), databases, and the stubs and skeletons representing CORBA objects. The SRL contains mechanisms, which control all events, threads, database I/O, and the interaction the ORB requires to act as the object message bus, to assure delivery and proper system interaction.
GIOP Over TS/MP Protocol HP strongly recommends configuring your production servers with the GIOP over TS/MP protocol, because this protocol leverages the features of process management, process persistence, load balancing, and scalability. (This protocol is also known as GCFIOP, or Guardian Context-Free Protocol.) A server that supports TS/MP can be configured as either a single process or as a group of processes within a server pool.
NonStop CORBA Remote Services The NonStop CORBA remote services are services that enable high-volume, high-performance access from other systems. Figure 16 shows the architecture of the remote services. Figure 1.2.
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 system. 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.
● There is one Comm Server per port, limiting throughput on that port. ● There is a TCP/IP process between the ServerNet adapter and a Comm Server, requiring a message system hop. Figure 1.3. Original TCP/IP Each Fast Ethernet ServerNet Adapter (FESA) corresponds to a TCP/IP port. By comparison, configuring the IIOP connectivity components of your system to use Parallel Library TCP/IP allows publishing a single port for up to 16 Comm Server processes.
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 to modify 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.
large-scale transactional management and services infrastructure, application providers can deliver reliable objects that fully support the ACID properties of a transaction service. NonStop CORBA 2.6 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.
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. Rolling back, or aborting, a transaction means that none of the changes made during the transaction will be made durable and the state of the objects involved in the transaction will remain unchanged from the state they were in before the transaction was started.
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.
Propagating the Transaction Context Transaction propagation refers to the act of associating the transaction context of a client with the operations performed by a transactional object. In the Transaction Service Specification, two types of propagation are defined: implicit and explicit. Currently, only implicit propagation is supported.
Chapter 2. System Management Chapter 2.
The NSDEnvironServer process provides services for a particular security domain. Generally, the NSDEnvironServer processes are created by the NSDAdminServer on demand.
command from the OSS command prompt: 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.
-c file-name 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.
● ❍ NonStop CORBA trace facility ❍ Ptrace utility ❍ Event Management Service (EMS) Format and semantics of the following files: ❍ OSS .profile file ❍ Initialization file (default.
SCF Reference Manual for G-Series Releases TCP/IP Configuration and Management Manual TCP/IP (Parallel Library) Configuration and Management Manual TCP/IP (Parallel Library) Migration Guide Configuring communications subsystems LAN Configuration and Management Manual QIO Configuration and Management Manual X25AM Configuration and Management Manual HP NonStop Transaction Management Facility (TMF) Operations and Recovery Guide Managing TMF databases, TMFCOM HP NonStop Transaction Management Facility (TMF) R
Chapter 3. Configuration and Management Using the Console 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 Using the Console to Troubleshoot the Servers Load Balancing Overview of the Console You can configure and manage NonStop CORBA by using a combination of the following tools: ● HP NonStop Kernel Open System Services (OSS) commands ● Guardian commands (for example, path
● 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 use the command line tools and shell scripts to configure and manage the system if you prefer them (see Configuration and Management Using Commands). Note that it is easier to make mistakes with the tools and scripts than with the Console.
you can define additional security domains for a host system. A security domain is composed of one or more business domains. ● Adding a New Security Domain ● Removing a Security Domain Adding a New Security Domain Add additional security domains if, for example, you want to partition your system. Each security domain corresponds to a Guardian user logon. The processes created under a given security domain have access rights corresponding to the user ID that controls the security domain.
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 NSDAdminServer and NSDEnvironServer You can view the status information for the NSDAdminServer and NSDEnvironServer. You might want to view it to get operational information about the servers. You can also enable and disable tracing. 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.
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.
● 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 ( server. ) should appear on the left-hand side of each Stopping the Server Do one of the following: ● Right-click NonStop Services for CORBA and select Stop from the pull-down menu. ● Select NonStop Services for CORBA and select Control>Stop from the Admin menu.
1. Do one of the following: ● Right-click NonStop Services for CORBA and select Properties from the pull-down menu. ● Select NonStop Services for CORBA and click View properties on the tool bar or select Properties from the View menu. 2. Click the tab for the server properties you want to view. To display properties for a specific server without reviewing General properties: 1. Select NonStop Services for CORBA. 2. Display the list of servers by expanding NonStop Services for CORBA. 3.
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 business domain. Can contain alphabetic, Domain name numeric, and underscore characters.
Primary CPU Backup CPU I/O Size Use default Use Parallel Library TCP/IP for Comm Servers 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. Size, in bytes, of buffers used for sending messages. The default size should accommodate most messages. Large messages are automatically segmented into multiple buffers as needed. You might want to specify a larger I/O size if most messages are large.
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. For better performance, the number of static servers should be close to or equal to the value for Maximum servers. Name of the server process.
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. Name of the TCP process that is managing the selected host address. One TCP process can manage multiple host addresses.
Object Transaction Service (OTS) Properties ● Server Configuration Options ● Troubleshooting Options Server Configuration Options Property Description Maximum number of copies of a server process that can run in a server pool at the Maximum servers 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.
Send timeout Log file name Length of time in microseconds the LINKMON process waits for a server process I/O operation to complete. The maximum time is 18 hours. Name of the file to which server process output is written. Object Transaction Service XID (OTSXID) Properties When transaction context is inherited from one process to another, an imported transaction branch is created. A transaction branch is represented by a new TMF transaction identifier called the XID.
determine if the remote client's host system is mapped to a Comm Server. If the remote client's host system has an entry in the Comm Server Map, the LSD returns the address information for that Comm Server. If the remote client's host system is not registered in the Comm Server Map, the LSD determines whether the request should be handled by a direct TCP server or by a Comm Server. If the request should be handled by a TCP server and one is available, the LSD returns the TCP/IP address of that server.
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 server process. If you do not choose a name, the system assigns one when the process starts.
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 BSD to use Parallel Library TCP/IP.
Comm Server Properties for Original TCP/IP ● Number of Comm Servers ● Basic Configuration ● Server Configuration Options ● Troubleshooting Options Number of Comm Servers 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.
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.
List of CPUs in which server processes can run. Separate the CPU numbers with commas; for example, 1,2,5. You must enter at least as many CPU numbers as the Processors number of servers that have been specified. This field cannot contain duplicate CPU numbers. Priority at which the server process is run. The range of values is 1 through 199, Process priority the highest priority being 199. Number of attempts to restart the server process, in the event of its abnormal Autorestart attempts termination.
List of CPUs in which server processes can run. Separate the CPU numbers with commas; for example, 1,2,5. If you do not specify a list of CPUs, the system runs Processors server processes in any available CPU. Specifying certain CPUs requires the system to use only the CPUs in the list. Priority at which the server process is run. The range of values is 1 through 199, Process priority the highest priority being 199.
IP address of the host system on which the server is listening. The host Host address 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. The port number cannot be used by any other process on the host system. At installation, this port number is set to a value based on the port number you Port number specify for TCP/IP.
Create delay Delete delay Max links Link depth Send timeout Log file name 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. Length of time in microseconds the PATHMON process waits before deleting unused dynamic server processes. The maximum time is 18 hours.
Displaying the Comm Server Map Do either of the following: ● Right-click NonStop Services for CORBA and select Comm Server Map from the pull-down menu. ● Select NonStop Services for CORBA and select Map from the View menu.
6. To exit the Comm Server Map display and save your changes, click OK. To exit without saving changes, click Cancel. Removing a Comm Server Mapping 1. Display the Comm Server Map. 2. Select a map entry to remove, then click Remove. The entry is no longer displayed in the Comm Server Map. 3. To exit the Comm Server Map display and save your changes, click OK. 4. To exit without saving changes, click Cancel.
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.
Properties) ● Adding and removing Comm Server mappings to balance the load of client requests among Comm 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 P
Chapter 4. Configuration and Management Using Commands Chapter 4. Configuration and Management Using Commands Configuration Setting Environment Variables (env.sh file) Customizing the env.
The Distributed Object Environment NonStop CORBA Configuration Management NonStop CORBA Performance Tuning NonStop CORBA Troubleshooting You can configure and manage NonStop CORBA by using a combination of the following tools: ● HP NonStop Kernel Open System Services (OSS) commands ● Guardian commands (for example, pathcom) ● cfgmgt commands ● Shell scripts provided with the product ● The NonStop Distributed Component Console This chapter describes how to configure and manage NonStop CORBA by usin
. /usr/tandem/nsdoms/etc/env.sh Customizing the env.sh file You might want to customize the env.sh file to reflect a special NonStop CORBA setup. For example, if you wanted to move the NonStop CORBA files from one Guardian subvolume to another, you need to make a change to the NSD_DIR and NSD_SUBVOL environment variables in env.sh. Use a text editor to modify env.sh.
MY_SUBVOL $NSD_SUBVOL NSD_SRL_SUBVOL $NSD_SUBVOL 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 Sets a custom NSD_SUBVOL, which allows for multiple installations. By default, the value is the same as NSD_SUBVOL. Specifies in NonStop Kernel format the Guardian volume and subvolume where the NonStop CORBA for Java shared run-time libraries (SRLs) reside. By default, the value is the same as NSD_SUBVOL.
MY_PREFIX Z MY_COLLECTOR '$0' COMP_ROOT JAVA_HOME /usr/tandem/java JREHOME $JAVA_HOME/jre Specifies a unique prefix letter for the NonStop CORBA process names. Use this environment variable prevent process name conflicts if you have multiple NonStop CORBA installations on a single system. You must set this as an uppercase letter. Specifies the EMS collector process used by the NonStop CORBA processes. The name is defined in NonStop Kernel format.
NSD_BOOTCP CLASSPATH PATH Specifies the boot classpath needed by $JREHOME/lib/tandemvm.jar: $JREHOME/lib/rt.jar TS/MP scripts (for NSJ v3.1) Sets up the CLASSPATH=.:$NSD_ROOT/lib/jorb.jar: CLASSPATH for the $NSD_ROOT/lib/jts.jar Java ORB. Adds the NonStop CORBA for Java $PATH:$NSD_ROOT/bin: $NSD_ROOT/bin/unsupported: $COMP_ROOT/usr/lib: bin and lib directories to the $JAVA_HOME/bin current path.
● Displaying All Entities ● Displaying a Particular Entity ● Changing an Entity ● Adding an Entity ● Deleting an Entity ● Exiting cfgmgt Starting cfgmgt Start cfgmgt from the OSS command prompt by using this command: cfgmgt [-r] cfgmgt is command-based. The command prompt identifies the current configuration database. The -r option opens the database for read only. If you have difficulty starting cfgmgt, verify that your environment variable settings are correct.
modify the entity. Each line contains a single key and its associated value. A closing brace terminates data entry. When an input line contains a key that is the same as an existing key, the new value replaces the current value. When an input line contains a new key, the new key and value are made part of the entity.
cfgmgt -x dumpdb myconfig.db 4. Review and edit the myconfig.db script as needed for your specific configuration. 5. Save a copy of the current $NSD_ROOT/etc/default.db script: cd $NSD_ROOT/etc cp default.db default.db.orig 6. Overlay the $NSD_ROOT/etc/default.db script with the myconfig.db script. Be aware that this procedure deletes existing any Naming Service bindings: cp myconfig.db $NSD_ROOT/etc/default.db 7.
Running nsdstart Before running nsdstart, be sure the required environment variable settings are in effect. To run the nsdstart script, enter the following command at the OSS command prompt: nsdstart This command starts the set of processes that comprise the NonStop Services for CORBA.
2. Determines the home terminal (hometerm) on which server output messages are displayed. 3. Starts the PATHMON process that manages the server processes. 4. Creates a new TS/MP configuration file using the server pool settings contained in the script. Some process names are defined using the script variables from Step 1. 5. Starts all the defined server processes. The configuration settings defined by the script are stored in a TS/MP configuration file (PATHCTL).
Differences Between Using Scripts and Using the PATHCOM Interface Scripts enable you to start or stop an entire configuration by executing a single command. Thus, if you need to change the global parameters in your TS/MP configuration, you might edit them in the nsdstart file and then execute the script. (If your NonStop CORBA system is running, you must execute the nsdstop script before restarting the system with the nsdstart script.
1. Locate the section of the script that defines the server you want to change. 2. Change the process priority number in the line that looks like this: set server pri 150 Changing the CPU in Which a Server Runs 1. Locate the section of the script that defines the server you want to change. 2. Add a line similar to the following (which specifies that the servers should run in CPUs 1 and 2): set server cpus (1,2) Enabling Trace Output for a Server 1.
#... 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 #... 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 #... 4.
#... 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 #...
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 ..." The default TCP process name for original TCP/IP is $ZTC0. The default TCP process name for Parallel Library TCP/IP is set when Parallel Library TCP/IP is installed.
set server env NSDOM_CFG_DBM=$NSDOM_CFG_DBM set server env MY_PREFIX=$MY_PREFIX set server define =_SRL_01, class map, file $NSD_SRL_SUBVOL.
+ + * * * set set set set set server server server server server maxservers 3 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.
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: CSNAME = PNCX where P is the installation prefix (the default is Z) and X is a letter that must be in contiguous ascending order. The letters in CSNAME 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.
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. The parameters are the attributes defined through the SET SERVER command when the TS/MP configuration was created by the nsdstart script or through the PATHCOM interface.
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).
You get a display showing the number of server processes running, errors, the number of links, and the weight.
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.
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.
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 THAW SERVER CS START SERVER CS Note that the FREEZE command precedes the STOP and ALTER commands; and also note that the THAW command must precede the START command.
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.
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. You use the Configuration Tool to define the relationships among the LSD, Comm Servers, TCP/IP processes, remote clients, and application servers. 3.
● The NonStop CORBA trace facility lets you follow the flow of control in an application to discover when and where an error occurred. Each component has a variable in the configuration file that controls the tracing for that component. ● SCF lets you verify the configuration of networking resources, validate addressing information, discover recurrent errors, and obtain line traces and protocol traces. ● The Ptrace utility helps you to interpret SCF traces.
Chapter 5. Managing Application Processes Chapter 5. Managing Application Processes The Application Environment Application Configuration Management Application Performance Tuning Managing NonStop CORBA 2.6 applications, like managing the NonStop CORBA system, consists of tasks such as configuring and monitoring the application processes, tuning system performance, and troubleshooting. When you install NonStop CORBA application servers, you have the option to configure them as TS/MP server pools.
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.
● 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. It is in that file that you specify the number of servers in the server pool and several other characteristics important for process management. You should use scripts to configure and run your application servers.
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. Because TS/MP provides all process management for the NonStop CORBA system, you use TS/MP interfaces for either the line-oriented PATHCOM utility or the corresponding programmatic interface (based on the SPI) to configure and manage the NonStop CORBA system processes.
Chapter 6. Configuring Security Features Chapter 6. Configuring Security Features IIOP/SSL Transport Protocols Configuring and Managing Private Keys and Certificates profile in env.sh newca Script newreq Script signreq Script pkcs12 Script Configuring and Managing Security Unaware Applications Modifying the NonStop CORBA Configuration Configuring and Managing Security Aware Applications Operation with Comm Server, LSD, and Naming Service Before you begin to use NonStop CORBA 2.
the process of creating certificates, by using a private CA. The file locations are: $NSD_ROOT/ssliop/etc/env.sh $NSD_ROOT/ssliop/bin/newca $NSD_ROOT/ssliop/bin/newreq $NSD_ROOT/ssliop/bin/signreq $NSD_ROOT/ssliop/bin/pkcs12 $NSD_ROOT/ssliop/bin/newcert The newcert script simply combines the functions of newreq, signreq, and pks12 into one script. profile in env.sh The profile in env.sh is used by all of the CA shell scripts. env.sh provides configuration information for the CA shell scripts.
After running newca, the root CA certificate is created. You can display it by typing: cat toyCA/cacert.pem The result is: Certificate: Data: Version: 3 (0x2) Serial Number: 0 (0x0) Signature Algorithm: md5WithRSAEncryption Issuer: C=US, ST=California, L=Cupertino, O=Hewlett-Packard, OU=NonStop/Email=john.doe@hp.com Validity Not Before: Jan 16 00:03:08 2003 GMT Not After : Feb 15 00:03:08 2003 GMT Subject: C=US, ST=California, L=Cupertino, O=Hewlett-Packard, OU=NonStop/Email=john.doe@hp.
ChMPSGV3bGV0dC1QYWNrYXJkMRAwDgYDVQQLEwdOb25TdG9wMSIwIAYJKoZIhvcN AQkBFhNncmVnLmJvc3Ryb21AaHAuY29tMB4XDTAzMDExNjAwMDMwOFoXDTAzMDIx NTAwMDMwOFowgYYxCzAJBgNVBAYTAlVTMRMwEQYDVQQIEwpDYWxpZm9ybmlhMRIw EAYDVQQHEwlDdXBlcnRpbm8xGDAWBgNVBAoTD0hld2xldHQtUGFja2FyZDEQMA4G A1UECxMHTm9uU3RvcDEiMCAGCSqGSIb3DQEJARYTZ3JlZy5ib3N0cm9tQGhwLmNv bTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA09/mUwiGOV15+/zmkuyDGae9 yb4HSDqUSty+r+2R5QnmTx8lCbTH3GUKdxCf3ts+3iV48Yh4X/x1nDo6msbR/cCW Q09RtzbGXyxDDtenrz/Wj9ZgkrmVIT+QnqNBhIl4UWkvhCbY0gJmz6Q7E
The script creates the following directories and files: Pathname/Filename Purpose The Certificate Signing Request (CSR). name.csr toyCA/private/name.key The newly generated private key for name. signreq Script The signreq script takes a CSR file as input and creates a new certificate. To run the script, type: signreq name.csr where name.csr is the CSR you created previously. Example 6.3. Sample signreq Run Create a certificate from a CSR. Using configuration from toyCA.
Enter PEM pass phrase: Verifying password Enter PEM pass phrase The script creates the following files: File Purpose The output PKCS#12 file, 3DES encrypted using the export password as the key name.p12 name.pem The PKCS#12 file in PEM format After running the pkcs12, the output name.pem file is suitable to use for both the ssl_cert_file and ssl_pkey_file. The PEM pass phrase is to be placed in a file as the ssl_pkey_pswd.
Chapter 5. Managing Application Processes Appendix A.
Appendix A. Configuration Database Entities Appendix A.
Entity bsd1@orb default@ORB default@trace event_service@event_service_settings event_service@ORB ilsd1@ORB ird1@ird_settings ird1@ORB lsd1@ORB NS@name_service_settings NS@ORB NSotsTM@ORB NSotsTM@transaction_service_settings NSotsXID@ORB profile@ORB ZNCA@comm_server Purpose Program profile for Bootstrap Daemon. Default parameters for ORB operation. Global setting for trace flags. Operating information for Event Service. Program profile for Event Service.
keep_alive Used for C++ applications only. Controls whether the TCP/IP keep-alive mechanism is enabled. If enabled, TCP periodically pings the other end of a connection to determine if the connection is still valid. This action will detect if the other end has gone away, even if no data is being transferred. The keep-alive mechanism is useful when one side is waiting for data (the next request for a server, or a reply for a client) and the other side goes away.
EventServiceIORFile If present, specifies the filename to which the Event Service object reference is stored. event_service@ORB tcp_process The TCP process associated with host_name. The default is $ZTC0. The default TCP process name for Parallel Library TCP/IP is set when Parallel Library TCP/IP is installed. You can locate the Parallel Library TCP/IP process for your system by using the SCF command LISTDEV TCPIP and looking for a process with program path ending in TCPSAM.
tcp_server Sets IIOP protocol. lsd1@ORB host_name The address used by the LSD. parallel_ip Specifies whether or not Parallel Library TCP/IP is enabled. port_number Specifies the port number that the LSD listens on. tcp_process The TCP process associated with host_name. The default is $ZTC0. The default TCP process name for Parallel Library TCP/IP is set when Parallel Library TCP/IP is installed.
set when Parallel Library TCP/IP is installed. You can locate the Parallel Library TCP/IP process for your system by using the SCF command LISTDEV TCPIP and looking for a process with program path ending in TCPSAM. use_comm_server Used with IIOP protocol. server_class Name of the TS/MP server class used by NSotsTM. pathmon Name of the PATHMON process. tsmp_server Sets the Pathsend protocol. tcp_server Sets the IIOP protocol.
The port number is the TCP/IP port number on which the Comm Server listens for requests. tcp_process The TCP process associated with host_name, can be omitted if using the default TCP process $ZTC0. The default TCP process name for Parallel Library TCP/IP is set when Parallel Library TCP/IP is installed. You can locate the Parallel Library TCP/IP process for your system by using the SCF command LISTDEV TCPIP and looking for a process with program path ending in TCPSAM.
true or false true tcp_client true or false true fs_client tcp_process Valid TCP process name ssl_client true or false ssl_only true or false $ZTC0 No default for Parallel Library TCP/IP. false false File system protocol: Uses the NonStop File System operations (for example, FILE_OPEN_, WRITEREADX, FILE_CLOSE_). IIOP protocol: Uses socket operations on the target object's host name and port number. Used with the tcp_client protocol. If specified, the given TCP process is used when making requests.
CA_file OSS None path/filename CA_path OSS path TLSv1 or SSLv3 or ssl_version SSLv2 or SSLv23 Cipher list ssl_ciphers follows this table OSS ssl_cert_file path/filename OSS ssl_pkey_file path/filename None SSLv3 DEFAULT The name of a file containing trusted CA certificates in PEM format. More than one certificate may be present in the file. Note that to protect against unauthorized writes, CA_file should be secured with the proper permissions.
RC4-MD5 EXP1024-DHE-DSS-RC4-SHA EXP1024-RC4-SHA EXP1024-DHE-DSS-DES-CBC-SHA EXP1024-DES-CBC-SHA EXP1024-RC2-CBC-MD5 EXP1024-RC4-MD5 ADH-RC4-MD5 EDH-RSA-DES-CBC-SHA EDH-DSS-DES-CBC-SHA DES-CBC-SHA ADH-DES-CBC-SHA EXP-EDH-RSA-DES-CBC-SHA EXP-EDH-DSS-DES-CBC-SHA EXP-DES-CBC-SHA EXP-RC2-CBC-MD5 EXP-RC4-MD5 EXP-ADH-DES-CBC-SHA EXP-ADH-RC4-MD5 NULL-SHA NULL-MD5 NULL-NULL Pathsend Protocol Enable the Pathsend protocol when the object is hosted by a server running in a server pool and you want to use the TS/MP tra
IIOP/SSL Protocol Enable the IIOP/SSL protocol when you want to secure communications between clients and servers. This protocol is appropriate whenever you want to assure confidentiality, authenticate clients, and assure message integrity.
ssl_front_end lsd1 or csname None This key is invalid without a true value for the use_comm_server key. This key identifies the server address to be marshaled into the IOR. csname must be the standard Comm Server entity name form, for example ZNCA, where the first letter is the installation prefix and the last letter must be in contiguous ascending order. If the value lsd1 is specified, the LSD's address is marshaled into the IOR and the LSD is assumed to be configured as an SSL server.
Appendix B. cfgmgt Command Reference Appendix B. cfgmgt Command Reference 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. In the following table, the commands are in alphabetical order.
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.
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. entity Either adds a new entity to the current database or, for an existing entity in the current database, does one of the following: ● Displays all of its keys and their values ● Changes the values of one or more existing keys ● Adds one or more new keys entity entity-name [ "{" {key value}...
entityaddkeyvalue Adds a key and its value to an entity in the current database. entityaddkeyvalue entity-name key 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. key is the name of a key. If key already belongs to entity-name, entityaddkeyvalue sets the value of key to value. If key does not already belongs to entity-name, entityaddkeyvalue adds key to entity-name and sets the value of key to value.
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. entitykeys entity-name entity-name is the name of the entity whose keys are to be displayed. If entity-name does not exist, entitykeys displays an error message. entitykeysvalues Displays the keys of an entity in the current database and their values.
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 The source command reads each command in the script file and processes it as if it had been entered manually. Script File Constructs Construct Comment Line continuation Escaped character Variable Expression Explanation A comment begins with the hash character #. Everything to the right of # is ignored.
Appendix A. Configuration Database Entities Appendix C.
Appendix C. /bin Directory Files 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 Appendix B. cfgmgt Command Reference Appendix D.
Appendix D. Log Files 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. In the following table, the log files are in alphabetical order.
Appendix E. Troubleshooting Appendix E.
NSD_ROOT=/usr/tandem/nsdoms NSD_ROOT_ETC=/usr/tandem/nsdoms/etc NSD_DIR=/G/system/zorbsdk NSDOM_CFG_DBM=$system.zorbsdk.NSDCFGDB NSD_SRL_SUBVOL=$system.zorbsdk NSD_SRL_DIR=/G/system/zorbsdk NSDOM_ADMIN_DB=$SYSTEM.ZORB231.ADMINDB If the command returns without any output, then the NonStop CORBA environment has not been set, and you must run the following command to set it up: . /usr/tandem/nsdoms/etc/env.sh Now you should be able to start the NonStop CORBA server.
Cannot Stop CORBA Server Problem: You want to stop a CORBA server, but pressing Control-C doesnt work. From OutsideView, you click Session->Break to send a Break signal, but the server does not stop, and you get the following message: /home/ecrm/stack: java Server -ORBprofile tcp_server wrote object reference to file stack.ior SIGQUIT Full thread dump Classic VM (T0083V20_30MAR2001_jdk122_V20AAG, posix threads): ...
A valid IOR generates output that looks similar to this: Interoperable Object Reference: type_id=IDL:Stack:1.0 Tagged profile #1: Tag=TAG_INTERNET_IOP (0) Profile data: Major=1, Minor=0 Host=172.17.202.44 Port=1097 110 bytes: (0)[N][S][D][O][M](0)(0)(0)(0)(0)(11)[t][c][p][_][s] [e][r][v][e][r](0)(0)(0)(0)(0)(14)[I][D][L][:][S][t][a][c][k] [:][1][.][0](0)(0)(0)(0)(0)(0)(10)[\][A][R][N][O][L][D][.
[s][e][r][v][e][r](0)(16)(0)(0)(0)(19)[I][D][L][:][A][u][t][h] [o][r][i][z][e][r][:][1][.
TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP UDP ESTAB 172.17.202.44 telnet 155.186.75.21 4251 0 0 ESTAB 172.17.202.44 telnet 155.186.75.21 4533 52 0 ESTAB 172.17.202.44 ftp 155.186.75.77 1246 0 0 ESTAB 172.17.202.44 telnet 155.186.75.21 3639 0 0 ESTAB 172.17.202.44 telnet 155.186.75.77 2339 0 0 LISTEN 172.17.202.44 1033 0.0.0.0 * 0 0 LISTEN 172.17.202.44 4000 0.0.0.0 * 0 0 LISTEN 172.17.202.44 2240 0.0.0.0 * 0 0 LISTEN 172.17.202.44 4001 0.0.0.0 * 0 0 LISTEN 0.0.0.0 telnet 0.0.0.
If the server is running under TS/MP, add the following defines to the TS/MP configuration: SET SERVER DEFINE =TCPIP^PROCESS^NAME, CLASS MAP, FILE $ZTC0 SET SERVER DEFINE =TCPIP^HOST^FILE, CLASS MAP, FILE $SYSTEM.ZTCPIP.HOSTS Explanation: The NonStop CORBA server uses the TCPIP process environment variable to manage the TCP/IP socket connection. If the TCPIP process name is not defined with =TCPIP^PROCESS^NAME, the client cannot establish a connection to the server. Appendix D.
Index Index Symbols .profile script, Setting Environment Variables (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.
TCP/IP bsd.
viewing and configuring, Viewing and Configuring Comm Server Mappings Comm server properties, Comm Server Properties Comm server properties for original TCP/IP, Comm Server Properties for Original TCP/IP Comm server properties for parallel library TCP/IP, Comm Server Properties for Parallel Library 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, Displayi
thaw, Restarting a Previously Defined TS/MP Configuration THAW SERVER, Restarting a Server Pool Common Data Representation (CDR), GIOP and IIOP Common Object Services, The Common Object Services Configuration overview, Configuration setting env.sh file, Setting Environment Variables (env.
Configuration Management Tool (cfgmgt), Configuration Management Tool (cfgmgt) configure script, Customizing the nsdstart Script Console, overview, Overview of the Console, Configuration and Management Using Commands Controlling servers, Controlling the Servers CPU, changing, Changing the CPU in Which a Server Runs cs.
setting, Setting Environment Variables (env.sh file) Environment status, Displaying Environment Status Environment variable file, setting, Setting Environment Variables (env.sh file) Environment variables NSD_DIR, Customizing the env.sh file NSD_SUBVOL, Customizing the env.sh file NSDOM_ADMIN_DB, Configuration Data Used by NSDAdminServer and NSDEnvironServer NSDOM_CFG_DBM, Configuration Database, Starting cfgmgt PATH, Starting cfgmgt Environment variables, table of, Customizing the env.sh file es.
H Host system, connecting to, Connecting to Host System I IIOP, GIOP and IIOP IIOP protocol, IIOP Protocol IIOP/SSL Protocol, IIOP/SSL Protocol ILSD, Interoperable Location Service Daemon (ILSD) ILSD, configuring for Parallel Library TCP/IP, Configuring the BSD, LSD and ILSD for Parallel Library TCP/IP ilsd.
J JTS client stub, Transaction Service L Language bindings, Transaction Service Lifespan policy persistent, File-System Protocol transient, File-System Protocol Load balancing, Load Balancing Location Service Daemon (LSD), Location Service Daemon (LSD) Location Service Daemon (LSD) properties, Location Service Daemon (LSD) Properties Log files admin.log, Log Files bsd.log, Log Files cs.log, Log Files es.log, Log Files ilsd.log, Log Files ird.log, Log Files lsd.log, Log Files ns.log, Log Files ots.
server status indicators, Server Status Indicators status information, Status Information for NSDAdminServer and NSDEnvironServer N Naming Service, Naming Service Naming service data adding naming context, Adding a Naming Context displaying hierarchy, Displaying the Naming Service Hierarchy managing, Managing Naming Service Data refreshing display, Refreshing the Display removing name, Removing a Naming Context or Name removing naming context, Removing a Naming Context or Name renaming name, Renaming a Nam
purpose of, Purpose of NSDAdminServer and NSDEnvironServer stand-alone process, Starting NSDAdminServer as a Stand-Alone Process starting and stopping, Starting and Stopping NSDAdminServer starting as PATHMON process, Starting NSDAdminServer as a PATHMON Process stopping PATHMON process, Stopping the PATHMON Process stopping stand-alone process, Stopping the Stand-Alone Process NSDEnvironServer configuration data, Configuration Data Used by NSDAdminServer and NSDEnvironServer purpose of, Purpose of NSDAdmin
Objection Transaction Service (OTS) properties, Object Transaction Service (OTS) Properties Objects stateful, Application Configuration Management stateless, Application Configuration Management Objects, transactional, Transactional Objects OpenSSL cipher list, OpenSSL Cipher List for Use with ssl_ciphers OTS client stub, Transaction Service ots.
Portability, application, Application Portability Problems, detecting and fixing, Detecting and Fixing Problems with Running Applications Process priority, changing, Changing the Process Priority Profiles, GIOP and IIOP Protocols client, Client Protocols, Protocols Common to both Clients and Servers file-system, File-System Protocol GIOP over Guardian file system, GIOP and IIOP, GIOP Over Guardian File System Protocol GIOP over TS/MP, GIOP Over TS/MP Protocol IIOP, IIOP Protocol IIOP/SSL, IIOP/SSL Protocol
adding, Adding a New Security Domain removing, Removing a Security Domain Server changing CPU, Changing the CPU in Which a Server Runs enabling trace output, Enabling Trace Output for a Server Server pools adding, Adding a Server Pool modifying, Modifying Running Server Pools Server pools status, displaying, Displaying Server Pools Status Server pools, altering, Altering a Server Pool reconfiguring, Reconfiguring Server Pools restarting, Restarting a Server Pool stopping a running server pool, Stopping a Ru
Servers controlling, Controlling the Servers monitoring, Monitoring the Servers starting, Starting the Servers stop managing, Stopping Managing the Servers stopping, Stopping the Server troubleshooting, Using the Console to Troubleshoot the Servers Services, Services SET SERVER, Adding a Server Pool start command, Restarting a Previously Defined TS/MP Configuration START SERVER command, Adding a Server Pool, Restarting a Server Pool Stateful objects, Application Configuration Management Stateless objects, A
Transactional objects, Transactional Objects Transactions, A Look at Transactions Transactions, controlling, Controlling Transactions Transport protocol information, Client and Server Protocol Specifications Transport protocols, GIOP and IIOP Troubleshooting, Troubleshooting NonStop CORBA, NonStop CORBA Troubleshooting Pathctl File in Use, Pathctl File in Use Process Name in Use, Process Name in Use servers, Using the Console to Troubleshoot the Servers starting NonStop Services for CORBA, Troubleshooting:
