HP NonStop CORBA 2.6.1 Administration Guide HP NonStop CORBA 2.6.1 Administration Guide Part number: 525935–005. Published July 2011. Legal Notice Abstract This manual provides information for administrators on how to configure your system for HP NonStop™ CORBA® 2.6.1. The information provided focuses on the HP-specific implementation of the Object Management Group's CORBA standards. Product Version: HP NonStop™ CORBA® 2.6.
Two-Phase Commit Process Resource Managers Transaction Context Controlling Transactions Application Portability 2. System Management NSDAdminServer and NSDEnvironServer Purpose of NSDAdminServer and NSDEnvironServer Starting and Stopping NSDAdminServer Starting NSDEnvironServer Configuration Data Used by NSDAdminServer and NSDEnvironServer What You Need to Know 3.
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.
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 A.
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. 1.2. 1.3. 1.4. 1.5. Basic NonStop CORBA Subsystems NonStop CORBA Remote Services Original TCP/IP Parallel Library TCP/IP Transaction Service Components List of Examples 4.1. 4.2. 4.3. 6.1. 6.2. 6.3. 6.4.
New and Changed Information New and Changed Information The updates in this edition (525935–005) are: Updated the description of Configuring and Managing Private Keys and Certificates. Updated the description of Activating the BSD Bootstrap Protocol. The updates in this edition (525935–004) are: Updated the description of Server Configuration Options. Updated the Note in the INFO PATHWAY Command section.
© Copyright 2009 and 2011 Hewlett-Packard Development Company L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
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.1 Administration Guide describes how to use the HP NonStop Distributed Component Console software to modify the configuration of your system.
the NonStop CORBA 2.6.1 Programmer’s Guide for C++. For Java programmers, it provides IDL to Java mapping. (Reference information for Java interfaces and classes is provided in Javadoc format on the product CD.) The NonStop CORBA 2.6.1 Glossary provides definitions of CORBA terminology, with special emphasis on the NonStop CORBA implementation. In addition, the NonStop Distributed Component Console includes online help.
New and Changed Information Chapter 1.
Chapter 1. NonStop CORBA Architecture Chapter 1. NonStop CORBA Architecture Distributed Object Computing Infrastructure Services Availability Scalability Data Integrity Tools NonStop CORBA 2.6.
Wide area network (WAN) and local area network (LAN) connectivity based on international networking standards Ability to wrap legacy applications with a distributed object architecture (an advantage of NonStop CORBA) Infrastructure The NonStop CORBA infrastructure provides the services and tools to help software developers and system administrators build object-oriented components and distributed object systems.
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 Guardian file system inter-ORB protocol Implementation). This protocol is used when client objects wish to communicate with objects whose server is either running as a stand-alone process or as stateful objects managed by TS/MP. The tools for configuring these protocols are described later in this manual.
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.
configuration database identifies the transport protocols used by the server. Some CORBA servers place information into the configuration database. For example, the naming service stores the root naming context object reference into the configuration database. The configuration database enables NonStop CORBA 2.6.1 to use implementation-specific data. Since these data are obtained from a database instead of appearing in the server code, the servers can be portable.
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.
module CORBA{ interface InitialReferences { Object get(in ObjectID id); ObjectIdList list(); }; }; Any client ORB must obtain the initial root naming context on an arbitrary host in an interoperable fashion. Using a file system relies on the presence of a shared file system and an agreed location. These specific and often platform dependent mechanisms prevent all clients from obtaining the root naming context in a portable and interoperable way.
The NonStop CORBA Event Service is implemented based on the OMG CORBA Event Service specification version 1.1. The Event Service provides asynchronous communication among CORBA objects. The Event Service allows supplier objects to communicate through an event channel, notifying any number of consumer objects when events they subscribe to take place. The Event Service consists of the Event Service executable, which is also deployed as a server pool.
A transaction is a unit of work that behaves in accordance with the ACID properties that have become synonymous with transaction processing. In transactions that are distributed across one or more systems, a Transaction Manager is normally relied upon to carry out the low-level details involved in orchestrating a transaction.
Resource Managers The Transaction Service Specification describes a Resource Manager, which is the database(s) involved with a transaction. NonStop CORBA supports two resource managers, NonStop SQL/MP and Enscribe. These resource managers are responsible for making durable any changes required by a transaction commit. In addition to these resource managers, the OTSTM uses NonStop TM/MP to interface with these resource managers.
Chapter 2. System Management Chapter 2.
-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. This output is typically used for troubleshooting. An NSDAdminServer process named $ZDAS starts running.
cfgmgt Command Reference).
Chapter 1. NonStop CORBA Architecture Chapter 3.
Chapter 3. Configuration and Management Using the Console Chapter 3.
commands Shell scripts provided with the product The NonStop Distributed Component Console This chapter describes how to configure and manage NonStop CORBA by using the Console.
You can add a security domain either while you are selecting a host system to manage or when you are already managing a host system (for step-by-step instructions, see the Console's online help). In either case, you must provide the following information: Field Information Required Security domain name Meaningful name for the security domain. Can contain alphabetic, numeric, and underscore characters. Logon name User ID for the security domain. This is the Guardian logon name for the host system.
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.
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. The following information is displayed about each server: Information Description Class 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. You have changed any of the server properties.
window. If you want to resume managing the servers you removed: 1. Exit the Console 2. Restart the Console 3. Reconnect to the host system 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.
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
OSS Data Directory Directory under which configuration and log files are stored for a business domain. Each business domain requires a separate location for its data files. For one business domain, this location can be the same as the OSS Product Directory. A browse button is available for navigating to the directory. Guardian Product Directory Name of the Guardian Database Directory Name of the Guardian $volume.
Server is 0 through 4095. Static Servers 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 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. Process Name Name of the server process.
Write object reference to a file Recommended: Leave this box checked. Applications without access to object references in the Naming Service might need to get the object reference from a file. File name Name of the object reference file. Server Configuration Options Property Description Process name Name of the server process. If you do not choose a name, the system assigns one when the process starts. Processors List of CPUs in which server processes can run.
range of values is 1 through 255. Set the value of Link depth to be less than or equal to the value of Max links. If Max links is 0, use the default value of 1 for Link depth. Send timeout Length of time in microseconds the LINKMON process waits for a server process I/O operation to complete. The maximum time is 18 hours. Log file name Name of the file to which server process output is written.
address those managed by the selected TCP process. Port number 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 specify for TCP/IP. If you have more than one copy of NonStop CORBA installed on a NonStop server, each copy must have a different port number. TCP process Name of the TCP process that is managing the selected host address.
Parallel Library TCP/IP Server Configuration Options Property Description Maximum servers If the check box for Use Parallel Library TCP/IP is not checked, this field is set to one. If it is checked, you may specify the number of servers. Static 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 specify.
Port number 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, the user is prompted to select a value for this port number. TCP process Name of the TCP process that is managing the selected host address. One TCP process can manage multiple host addresses. TCP processes can be spread across CPUs for load balancing. Process name Name of the Comm Server process.
priority Autorestart Number of attempts to restart the server process, in the event of its abnormal termination. The maximum number is attempts 32767. Log file name 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.
name Interoperable Location Service Daemon (ILSD) Properties The Interoperable Location Service Daemon (ILSD) is an interoperable Naming Service forwarding agent. The ILSD receives requests targeted at corbaloc and corbaname URLs. The ILSD uses the object key to determine how to forward requests. Basic Configuration Server Configuration Options Troubleshooting Options Basic Configuration Property Description Host address IP address of the host system on which the server is listening.
maximum number of queued requests is the value of the Max links field minus 1. The range of Max links values is 0 through 4095. Link depth Number of concurrent links allowed from a LINKMON process to a particular server process in a server pool. The range of values is 1 through 255. Set the value of Link depth to be less than or equal to the value of Max links. If Max links is 0, use the default value of 1 for Link depth.
3. Type the IP address of the remote host system sending the request through a Comm Server in the Source Address field. 4. Select a Comm Server to service client requests from the drop-down list. 5. Click OK. The new Comm Server mapping is shown in the Comm Server Map. 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.
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 .
3. When the Input dialog appears, type the new naming context in id.kind format. The identifier attribute (id ) is required. The kind attribute, a descriptive string for the type of naming context, is optional and, if present, is separated from the id by a period. Example: NSDOMES.EventChannelFactory . 4. Click OK. The new name appears in the Naming Service hierarchy Removing a Naming Context or Name 1. Display the Naming Service hierarchy. 2.
Property Description Tracing Enable tracing when you are troubleshooting a problem with the server. When enabled, the tracing option writes information to the log file. The recommended procedure for tracing is to enable Basic tracing first, which might give you enough information to solve the problem. If you need more information, enable Detailed tracing for additional detail. (The NonStop CORBA 2.6.1 Programmer's Guide for C++ and the NonStop CORBA 2.6.
Chapter 4. Configuration and Management Using Commands Chapter 4. Configuration and Management Using Commands Configuration Setting Environment Variables (env.sh file) Customizing the env.
This section assumes that you have successfully completed installing your 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. The information in this section shows you how to perform these configuration tasks. Most of the commands described in this section are used in the Open System Services (OSS) environment.
MY_COLLECTOR '$0' COMP_ROOT Specifies the EMS collector process used by the NonStop CORBA processes. The name is defined in NonStop Kernel format. Modify this line if you want to use a different collector other than the system default of $0. Specifies the root location where your tools, such as c89, are located. Modify this line if the tools you want to use are in a location other than the system default. JAVA_HOME /usr/tandem/java Sets path for NSJ.
entities Each entity has a name of the form profile@attribute , where profile and attribute are any strings. When you have the list of available entities, you can use other commands to manipulate them. 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.
Starting and Stopping NonStop Services for CORBA Running nsdstart Running nsdstop 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.
If you try to execute nsdstart when the target TS/MP environment is already running, you get an error message. The following example shows the result of executing the nsdstart file when the TS/MP environment for NonStop CORBA is already running. Issuing the nsdstart Command: Error Condition /usr/tandem/nsdoms> nsdstart -v gtacl[5]: unable to run $SYSTEM.SYSTEM.
Changing the Process Priority 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.
remove the $ZNCB process. 1. If NonStop CORBA system processes are running, stop them by executing the nsdstop script from OSS: > nsdstop 2. Locate the Comm Server specification section in nsdstart . The following example shows the section of nsdstart that configures the Comm Server, including two processes: Configuring Two Comm Servers #... COM_SERVER1="$MY_PREFIX"NCA COM_SERVER2="$MY_PREFIX"NCB #...
This profile change tells the TCP/IP component of the NonStop CORBA application to tell the Parallel Library TCP/IP components to enable socket sharing and round-robin connection filtering. 2. Alter the application's SERVERCLASS configuration in the nsdstart script to run multiple processes. This involves changing the maxservers and numstatic entries, and creating the appropriate process entries. Note: Each process in a Parallel Library TCP/IP server class must run in a separate CPU. Example 4.1.
2. Alter the default Comm Server SERVERCLASS configuration in the nsdstart script to pass the Comm Server's key as an argument. This involves adding a statement to set the server's arglist. Alter the default Comm Server SERVERCLASS configuration to run multiple processes. This involves changing the maxservers and numstatic entries, and creating the appropriate process entries. Note: Each process in a Parallel Library TCP/IP server class must run in a separate CPU. Example 4.3.
If the default Comm Server's name is ZNCA, a second Comm Server's name must be ZNCB. There are two handy predefined Comm Server name variables available in the nsdstart script, COM_SERVER1 and COM_SERVER2. 2. The Comm Server entity name must have the following form: csname@comm_server where csname is the argument passed to processes in the associated Parallel Library TCP/IP Comm Server SERVERCLASS. 3.
commands cause PATHMON to stop the processes. The thaw and start commands restart the processes. Monitoring Status The PATHMON process maintains information about process configurations, process status, and operations statistics.
= INFO PATHMON The following example shows information displayed after the INFO PATHMON command was issued: INFO PATHMON Display PATHMON BACKUPCPU 4 DUMP ON (FILE \SYS.$VOL1.TESTING.MONDUMP) 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 .
STATUS PATHMON Display = status pathmon PATHMON \OSS2.$YNSD2 -- STATE=RUNNING PATHCTL (OPEN) $DATA07.DEREK.PATHCTL LOG1 S (CLOSED) \OSS2.$Z6GR.#INTER LOG2 (CLOSED) REQNUM FILE 1 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.
Because a system shutdown can result in considerable downtime if your application is complex, when you first configure your environment you should specify global limits that are high enough to allow for growth. If you discover that you must reconfigure the global parameters, thereby forcing a shutdown, you must re-specify all limits, not just the ones you are changing.
= 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. Managing the Distributed Object Environment This subsection provides an overview of the tasks involved with managing the NonStop CORBA distributed object environment. The NonStop CORBA system implements the ORB on the NonStop Kernel operating system.
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. You can use PATHCOM to locate and resolve a NonStop CORBA system performance problem. 4. You can use the cfgmgt tool and the nsdstart script to configure Parallel Library TCP/IP to increase capacity.
Chapter 5. Managing Application Processes Chapter 5. Managing Application Processes The Application Environment Application Configuration Management Application Performance Tuning Managing NonStop CORBA 2.6.1 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.
You can use PATHCOM to detect problems in tuning stateful server pools, but solving the problem often involves changing the application design. You can, for example, redefine object classes so more accept stateless requests. You also might redesign your application so that the same transaction is accomplished by making smaller requests to the application object. Chapter 4. Configuration and Management Using Commands Chapter 6.
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.6.
newreq stack /*Answer the questions*/ signreq stack.csr /*Answer the questions*/ pkcs13 stack.cert.pem /*Answer the questions*/ Note: Ensure to use a unique name or common name. Add a profile for Stack SSL: catch {entitydelete sample_stackSSL@ORB} entity sample_stackSSL@ORB { tcp_server true ssl_only true ssl_port 0 port_number 0 host_name texas.txn.cpqcorp.net ssl_cert_file /h13/samples/stack/cert/stack.pem ssl_pkey_file /h13/samples/stack/cert/stack.pem ssl_pkey_pswd /h13/ssliop/toyCA/password.
2. csname(commserver name) If you want to extend this to include ILSD or LSD you should modify the client profile to: catch {entitydelete sample_stack_clientSSL@ORB} entity sample_stack_clientSSL@ORB { ssl_client true tcp_client true fs_client false CA_file /h13/ssliop/toyCA/CAcert.pem } which would allow the ILSD and LSD traffic to pass in the clear but keep the user data encrypted.
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.
a1:d7:75:82:99:a6:e2:40:23 Exponent: 65537 (0x10001) X509v3 extensions: X509v3 Basic Constraints: CA:TRUE X509v3 Key Usage: Certificate Sign, CRL Sign X509v3 Subject Key Identifier: 87:CA:7A:F7:6D:A1:0E:FB:12:E4:B7:3E:68:CB:C7:5E:72:CD:73:53 X509v3 Authority Key Identifier: keyid:87:CA:7A:F7:6D:A1:0E:FB:12:E4:B7:3E:68:CB:C7:5E:72:CD:73:53 DirName:/C=US/ST=California/L=Cupertino/O=Hewlett-Packard/OU=NonStop/Email=john.doe@hp.com serial:00 Netscape Comment: Warning! This is a learning toy certificate.
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.
catch {entitydelete sample_stack@ORB} entity sample_stack@ORB { tcp_server true ssl_only true ssl_port 0 host_name 127.0.0.1 ssl_cert_file $NSD_ROOT/testCA/GServer.pem ssl_pkey_file $NSD_ROOT/testCA/GServer.pem ssl_pkey_pswd $NSD_ROOT/testCA/yo.
Appendix A. Configuration Database Entities Appendix A.
ilsd1@ORB Program profile for Interoperable Location Service Daemon. ird1@ird_settings Operating information for Interface Repository. ird1@ORB Program profile for Interface Repository Daemon. lsd1@ORB Program profile for Location Service Daemon. NS@name_service_settings Operating information for Naming Service. NS@ORB Program profile for Naming Service. NSotsTM@ORB Program profile for the NonStop Object Transaction Service.
Specifies whether or not Parallel Library TCP/IP is enabled for Comm Servers. pathmon The name of the PATHMON process used for the NonStop Services for CORBA processes. product_dir_guardian The Guardian directory in which the product files were installed. product_dir_oss The OSS directory in which the product files were installed. ssliop_default The location for the default certificates. The default at installation is $NSD_ROOT/ssliop/default .
ird1@ird_settings IRFiles A search path for IR databases. Multiple IR databases can be used if separated by semicolons. The rightmost database listed receives updates for new IR entries. When you modify an IR, the search begins on the left, then proceeds until the correct IR is found. Any updated IR replaces the existing IR in the same database. IRIORFILE Specifies the filename to which the Interface Repository (IR) object references are stored.
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. NSotsTM@transaction_service_settings XID_file Specifies the location of the file used to hold transaction identifiers. NSotsXID@ORB fs_server Sets the file system protocol. profile@ORB Application programmers can use profile@ORB to define applicaton profiles in many ways.
is specified, the program will listen on a TCP socket and accept CORBA requests on it. NonStop CORBA provides four transport protocols: Transport Protocol Uses... Appropriate When... Pathsend TS/MP communication mechanism Servers are running in a TS/MP server pool. File system NonStop File System Client and server reside in the same Expand network. IIOP/SSL SSL over TCP/IP Data protection is required for the communication.
database records. If you use the same program profile for different server programs, incorrect server behavior is likely. When an object in a server program creates an object reference, the ORB component uses information from a number of sources. The transport protocols specified in the program profile determine the protocols that appear in the generated object references.
or SSLv2 SSLv23 or are recommended. SSLv2 and SSLv23 are not recommended, but are provided for completeness. ssl_ciphers Cipher list follows this table DEFAULT ALL:!ADH:RC4+RSA:+SSLv2:@STRENGTH ssl_cert_file OSS path/filename $NSD_ROOT/ssliop/default/cert.pem Certificate file. (The certificate file may also contain the private key.) ssl_pkey_file OSS path/filename $NSD_ROOT/ssliop/default/cert.pem Private key file. (The private key file may also contain the certificate.
example: ssl.TrustManagerFactory.algorithm=SunX509 . The configuration of the truststore is done in the following order: 1. The -ORBprofile values for the entity keys truststore and truststore_pswd . 2. The system properties that may be set on the program command line: javax.net.ssl.trustStore javax.net.ssl.trustStorePassword javax.net.ssl.trustStoreType (optional) 3. $JAVA_HOME/lib/security/jssecerts . 4. $JAVA_HOME/lib/security/cacerts .
PATHMON process name and server class name in the program profile. The following table shows the keys and values that are associated with the Pathsend protocol (tsmp_server ): Pathsend Protocol Keys and Values Key Possible Values Default Value pathmon Valid process name None server_class Valid server class name None File-System Protocol Enable the file-system protocol when you want the NonStop Kernel file system to be used as the transport mechanism for requests and responses.
ssl_pkey_pswd OSS None. If ssl_sert_file is not set, then Password to unlock the private key file. path/filename ssl_pkey_pswd will be set to $NSD_ROOT/ssliop/default/certpswd.txt 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. 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.
Normal Comm Server (using traditional TCP/IP) Dedicated Comm Server Parallel Library TCP/IP Comm Server Chapter 6. Configuring Security Features Appendix B.
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.
bye, exit, quit Exits cfgmgt and returns to the OSS shell prompt. { bye | exit | quit } cfgmgt Starts cfgmgt , the configuration management tool. The -r option opens the configuration database for read only. cfgmgt [-r] dbcreate Creates a database. dbcreate [dbName] dbName is the name of the database to be created. The default is the name that the NSDOM_CFG_DBM environment variable specifies. Note: must be a fully or partially qualified Guardian file name.
Changes the values of one or more existing keys Adds one or more new keys entity entity-name [ "{" {key value }... "}" ] entity-name is the name of an entity. If entity-name does not exist, entity adds it to the current database, along with any key-value pairs. If entity-name does exist, but no key-value pairs are specified, entity displays all of the keys of entity-name and their values. key is the name of a key. The list of key-value pairs must be enclosed in braces.
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. entitykeysvalues entity-name entity-name is the name of the entity whose keys and values are to be displayed. If entity-name does not exist, entitykeysvalues displays an error message. profile Returns or sets the application name profiled in the current database.
For example, to delete the entity such as: default@ORB if it exists but ignore the error if it does not exist, use a command catch { entitydelete default@ORB } 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.
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.
following error: ERROR! Shared library ioser12 could not be found. Exception in thread "main" java.lang.UnsatisfiedLinkError: specialLoadClass at com.sun.corba.se.internal.util.JDKClassLoader.loadClass (JDKClassLoader.java) at ... com.blazesoft.engines.rules.NdRuleAgent.initialize(:3877) at AuthorizerRuleAgent.instantiate(AuthorizerRuleAgent.java, at AuthorizerServer.(AuthorizerServer.java, Compiled Code) at AuthorizerServer.main(AuthorizerServer.java, Compiled Code) Compiled Code) JorbLite 2.
server is still running: /home/ecrm/stack: java Server -ORBprofile tcp_server wrote object reference to file stack.ior Solution: Verify that the CORBA server generated a valid object reference (IOR). If the server wrote an IOR file, display the contents of that file with the following command (using the appropriate file name in place of stack.ior): showior stack.ior A valid IOR generates output that looks similar to this: Interoperable Object Reference: type_id=IDL:Stack:1.
SCF - T9082G02 - (26JUN00) (20MAR00) - 07/11/0000 10:30:20 System \ARNOLD Copyright Compaq Computer Corporation 1986 - 1999 TCPIP Info SUBNET \ARNOLD.$ZTC0.* Name Devicename *IPADDRESS TYPE *SUBNETMASK SuName QIO *R #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.
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.
Client protocols, Client Protocols, Protocols Common to both Clients and Servers Client system, Client System Client/server process, Client/Server Process Clients, transactional, Transactional Clients Comm server, Comm Server adding a process, Adding a Comm Server Process configuring for Parallel Library TCP/IP, Configuring a Comm Server for Parallel Library TCP/IP removing a process, Removing a Comm Server Process Comm server mappings adding, Adding a Comm Server Mapping displaying, Displaying the Comm Ser
bsd1@ORB, Standard Entities, bsd1@ORB default@ORB, Standard Entities, default@ORB default@trace, Standard Entities, default@trace event_service@event_service_settings, Standard Entities, event_service@event_service_settings event_service@ORB, Standard Entities ilsd1@ORB, Standard Entities, ilsd1@ORB ird1@ird_settings, Standard Entities ird1@ORB, Standard Entities, ird1@ird_settings lsd1@ORB, Standard Entities, lsd1@ORB NS@name_service_settings, Standard Entities, NS@name_service_settings NS@ORB, Standard En
entitydeletekey command, Changing an Entity env.sh file customizing, Customizing the env.sh file 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.
availability, Availability data integrity, Data Integrity scalability, Scalability services, Services tools, Tools Inter-ORB communication, GIOP and IIOP Interface Repository Database (IR), Interface Repository Database Interface Repository Database (IRD) properties, Interface Repository Database (IRD) Properties Interoperable Location Service Daemon (ILSD), Interoperable Location Service Daemon (ILSD) Interoperable Location Service Daemon (ILSD) properties, Interoperable Location Service Daemon (ILSD) Prop
server status display, Detailed Server Status Display 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
nsdstop, Differences Between Using Scripts and Using the PATHCOM Interface nsdstop command, Running nsdstop nsdstop, executing, Running nsdstop NSotsTM, Transaction Service NSotsTM@ORB, Standard Entities NSotsTM@transaction_service_settings, Standard Entities, NSotsTM@transaction_service_settings NSotsXID, Transaction Service NSotsXID@ORB, Standard Entities O Object Management Architecture (OMA), Services Object reference saving, Saving an Object Reference viewing, Viewing an Object Reference Object Transa
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 Pathsend, Pathsend Protocol server, Server Protocols, Protocols Common to both Clients and Servers table of client protocol keys and values, Client Protocols table of common protocol keys and valu
event service properties, Event Service 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 Properties Object Transaction Service (OTS) properties, Object Transaction Service (OTS)
Truststore, JSSE Truststore algorithm, JSSE Truststore TS/MP processes, maintaining, Using the PATHCOM Interface to Maintain TS/MP Processes Two phase commit process, Two-Phase Commit Process Z ZNCA@comm_server, Standard Entities, ZNCA@comm_server Appendix E.
