HP NonStop CORBA 2.6.1 Getting Started Guide for C++ HP NonStop CORBA 2.6.1 Getting Started Guide for C++ Part number: 525933–004. Published October 2014. Legal Notice Abstract This manual provides information about getting HP NonStop™ CORBA® 2.6.1 for C++ installed and running. The information provided focuses on the HP-specific implementation of the Object Management Group's CORBA standards. Product Version: HP NonStop™ CORBA® 2.6.
Hardware and Software Requirements Check for Previously Installed Products HP NonStop Server Toolkit for BEA WebLogic Server NonStop Enterprise Java Beans (EJB) Perform Subsystem Resource Cleanup Install NonStop CORBA on the Host System Run the IPSetup Program Run the DSM/SCM Planner Interface Change Ownership of OSS Files (if Using DSM/SCM) Run the NonStop CORBA OSS Installer Setup Program Host Installation Installer Wizard Install the NonStop Distributed Component Console on the PC Start NonStop CORBA Ser
New and Changed Information New and Changed Information This edition of 525933-004 is updated for the following: Note: The following updates are applicable only from T2817H14, T2818H14, and T2820H14 release onwards. This version of NS CORBA must be used on H06.26/J0.15 and later RVU’s. Also, it requires NSJ7 (32-bit) application for further configurations. Current SPT library is replaced by PUT library. Softlink (/usr/tandem/java) is not created automatically in NSJ7 (32-bit) application.
© Copyright 2007, 2014 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 The NonStop CORBA Getting Started Guide for C++ covers the material you need to know to get NonStop CORBA up and running.
NonStop CORBA 2.6.1 Glossary. UPPERCASE Uppercase letters indicate keywords and reserved words; enter these items exactly as shown. Items not enclosed in LETTERS brackets are required. For example: Italic letters MAXATTACH Items in Italicletters indicate variable items that you supply. Items not enclosed in brackets are required. In the following example, UserDir is a variable directory name, while /projectX must be entered exactly as shown: UserDir/projectX [] Brackets enclose optional syntax items.
Chapter 1. Introduction to NonStop CORBA Chapter 1. Introduction to NonStop CORBA Why NonStop CORBA CORBA 2.6.
Optimized for use in transaction processing, NonStop CORBA allows the mapping of a large number of clients to a smaller number of servers, effectively sharing resources. Because the NonStop CORBA system processes run in an HP NonStop TS/MP environment, you get the strength of HP transaction services (for process management, availability, and load balancing) in a CORBA-compliant-based environment. CORBA 2.6.1 Base New features of NonStop CORBA are based on the CORBA 2.6.
Within the HP system, the NonStop CORBA system uses TS/MP for communication between application processes, Comm Servers, and application servers. This design improves throughput while minimizing the IPC resources needed by the ORB. You can increase the number of remote clients connected to the NonStop CORBA ORB without requiring configuration changes on either the client workstation or the NonStop CORBA system.
Language bindings Portable Object Adapter (POA) Object Method Invocation Naming Service and Interoperable Naming Service Bootstrap Daemon (BSD) OTS/JTS NSots XID Broker Object by Value Event Service Error Logging and Tracing Portable Interceptors Legacy Wrapper Interface IIOP and GIOP Protocol Support Internet Inter-ORB Protocol (IIOP) is the standard protocol that different ORBs must use to communicate across the Internet. This protocol is standardized by the OMG.
NonStop CORBA also implements the interoperable extension of the Naming Service, allowing users to access an object through a humanreadable URL name. This format makes handling objects simpler for the user. In addition, the client no longer must import an IOR URL from the server to invoke methods on that server.
Legacy wrapping is never an easy task because the legacy application code itself may require modification. However, HP's supplied set of generic legacy wrappers act as an integration framework for your legacy application. You do not need to modify your legacy application, and your legacy application can interoperate transparently with existing CORBA objects and components. About This Guide Chapter 2.
Chapter 2. Installing NonStop CORBA Chapter 2.
Method 1: Use the NonStop CORBA OSS Installer or the installation script to install the templates during the NonStop CORBA installation. Method 2: Use the INSTALL^TEMPLATES TACL macro to install the templates after you complete the NonStop CORBA installation. Decide if you want to use the NonStop CORBA PC installer or if you will install directly in the OSS environment by using the installation script. Consider the security implications of the user ID that you use to perform your installation.
NonStop Enterprise Java Beans (EJB) NonStop CORBA 2.6.1 should not be installed on the same system as NonStop Enterprise Java Beans (EJB). You should uninstall EJB before installing NonStop CORBA 2.6.1. Perform Subsystem Resource Cleanup A subsystem cleanup does not have to be done in all cases, but you may want to do a cleanup if NonStop CORBA is already installed. If you have a system you want to install over or a system to clean up, then performing a subsystem resource cleanup is advisable.
7. On the Host Target Settings screen you may either accept the default locations for Work and Backup subvolumes or browse to locations of your choice. Click Next when you are satisfied with the locations. 8. On the Host File Placement screen you may either accept the default disk locations or browse to locations of your choice. Click Next when you are satisfied with the locations. 9. On the Installation Manifest screen review the file locations. You may click Back to go back and change them.
directories. 3. Type values for the OSS host name, OSS user ID, and OSS password fields. Click Next to continue. Note: If you used the DSM/SCM planner interface to move your files onto the NonStop system and unpax them, the host name, user ID, and password are provided as part of the Operator Instructions in DSM/SCM. Field Name Description OSS host name Name or IP address of the host system.
OSS directory for pax files /G/SYSTEM/ZOSSUTL Must be unique across all installed products. The location where the pax and other installation files are copied. Make a note of this value: it is used when bringing up the NonStop CORBA services. OSS directory for ISV G/SYSTEM/ZORBC11 The installation subvolume NEW checked installation Uncheck this box only if you are updating an existing NonStop CORBA 2.6.1 installation. When updating a previous CORBA 2.
new values. Click Next to continue. Field Name Default Value Description Java OSS root directory /usr/tandem/java Must be unique across all installed products. The location of NonStop Server for Java. If you use DSM/SCM, you may not change this value. NonStop CORBA usr/tandem/nsdoms Must be unique across all installed products. The location of NonStop CORBA files. If OSS root dir you use DSM/SCM, you may not change this value.
8. If you indicated in Step 4 that this installation is an update to a previous installation, go to Step 9. If you indicated this is a new installation, fill in the next group of fields. Supply values for the Environment prefix, EMS collector, EMS template directory, EMS object template directory, TCP process name, TCP/IP base port number, Security domain, and Business domain fields by accepting the defaults or typing new values. Click Next to continue.
9. The NonStop CORBA OSS Installer wizard indicates that the installation is complete. Click Finish. 10. If you did not choose to install the EMS template files using the GUI installer, then you should install them now by using the INSTALL^TEMPLATES TACL macro. The INSTALL^TEMPLATES TACL macro is distributed on the SUT and can be found in volume.ZINSAIDS.TACLMACS.
Start NonStop CORBA Server Processes on the Host System Use the NonStop Distributed Component Console to start the NonStop CORBA server processes and to verify their status. Alternatively you can log on to the OSS environment and use the nsdstart script. That method is discussed under Alternative Installation Method. 1. Launch the Console on the PC by double-clicking on the NonStop Console icon placed on the desktop by the installer. The main Console window appears. 2.
The Business Domain Selection dialog appears. Note: You can define additional security and business domains at a later time. See the Console online help for instructions. 6. Select the business domain you defined during the installation, then click OK. The business domain appears on the main Console window. 7. Click on the plus sign (+) next to the business domain to show the NonStop Services for CORBA node under the business domain.
Modifying an Existing NonStop CORBA 2.6.1 Installation to Add the IIOP/SSL features If you previously installed NonStop CORBA 2.6.1, but did not install the optional IIOP/SSL features, you can add those features. To check whether IIOP/SSL is already installed, run the stack sample program configured for IIOP/SSL as described in Using the Stack Example with IIOP/SSL Installing IIOP/SSL on an Existing NonStop CORBA 2.6.1 System 1. If CORBA is running, stop it by using the Console or the nsdstop script. 2.
Run the Install Script Start the OSS shell by typing: >osh Move to the directory where you transferred the OSSPAX file: >cd /G/SYSTEM/ZORBC11 Start the script by typing >install Follow the script prompts to completion. If the script encounters an error, it will back up to the closest logical starting place and allow you to reenter information. When the script prompts you to unpack the pax files, answer N if you have used DSM/SCM to place the files on your system and unpax them.
Specifies a unique prefix letter for the subsystem process names. Use this environment variable to prevent process-name conflicts if you have multiple NonStop CORBA installations on a single system. ENTER prefix letter here or leave blank to use the current value Z : === CHECKING for existing process $ZNDM === Collector Process Specifies the EMS collector process used by the subsystem. The name is defined in NonStop Kernel format (for example, $ZNSD0).
building config dB initializing LSD initializing Name Service building EMS templates (in background) check /usr/tandem/nsdoms/log/bldems.out for details updating JVM starting Admin server Where, change_me is a dot-separated IPv4 address like 172.31.41.151 or colon-separated IPv6 address like fe80::a00:8eff:fe06:d093. ================================================== NonStop(TM) CORBA INSTALLATION COMPLETE ================================================== Installing Multiple Copies of NonStop CORBA 2.6.
Chapter 3. Considerations for Migrating from Previous Releases Chapter 3. Considerations for Migrating from Previous Releases Product Level Migration Information Overview Upgrading From NonStop CORBA 2.3 to NonStop CORBA 2.6.1 Moving Applications from NonStop CORBA 2.3 Update 3 or Later to NonStop CORBA 2.6.1 Product Level Migration Information Overview NonStop CORBA 2.6.1 is compatible with prior versions of NonStop CORBA. New features have been added, but no features have been removed.
POAManager_ptr a_POAManager, const CORBA::PolicyList& policies); in the past, the signature was: POA_ptr create_POA(const char* adapter_name, POAManager_ptr a_POAManager, CORBA::PolicyList_ptr policies); Local POA objects are implemented. Applications do not need to be changed to work properly in CORBA 2.6; recompiling takes care of any needed changes. The new pseudo hierarchy is: class class class class class class class CORBA::LocalObject : public virtual CORBA::Object { ...
Chapter 4. Running the C++ Stack Example Chapter 4. Running the C++ Stack Example The Stack Example Overview Building the Stack Example Configuring NonStop CORBA for the Stack Example Running the Stack Example on OSS Using the Stack Example With IIOP/SSL Once you have installed your NonStop CORBA software and configured your system, you can test the operation of your system by running a simple CORBA program.
Configuring NonStop CORBA for the Stack Example Before you can run the stack example, you must configure the stack server for your particular system by editing, then sourcing, the stack server configuration script config.src: 1. Edit the config.src file, changing the CHANGE_ME value to a valid TCP host name or IP address. 2. Use the cfgmgt tool to source the stack-server configuration script by issuing these commands: > cfgmgt > source config.src > exit These commands load the sample_stack@ORB entity.
Where, change_me is a dot-separated IPv4 address like 172.31.41.151 or colon-separated IPv6 address like fe80::a00:8eff:fe06:d093. Change the client configuration by entering: catch {entitydelete sample_stack_client@ORB} entity sample_stack_client@ORB { ssl_client true Then run the example.
Index Index A Application, migrating NonStop CORBA 2.3 Update 3 to NonStop CORBA 2.6.1, Moving Applications from NonStop CORBA 2.3 Update 3 or Later to NonStop CORBA 2.6.
alternative method, Alternative Installation Method before you begin, Before You Begin the Installation Installer Setup Program, Run the NonStop CORBA OSS Installer Setup Program installer wizard, Host Installation Installer Wizard installing multiple versions of software, Installing Multiple Copies of NonStop CORBA 2.6.
System architecture, Why NonStop CORBA T Tracing, Error Logging and Tracing Transaction protection, Transaction Protection and Data Integrity TS/MP environment, advantages of, Advantages of the TS/MP Environment U unconfigure script, Perform Subsystem Resource Cleanup Upgrading from NonStop CORBA 2.3 Update 3 or later to NonStop CORBA 2.6.1, Upgrading From NonStop CORBA 2.3 to NonStop CORBA 2.6.1 W Wrapping, Legacy Wrapper Interface Chapter 4.
