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–003. Published July 2011. 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 the HP NonStop CORBA 2.6.1 Getting Started Guide for C++ is updated for the following: Updated subsection Host Name of a Machine in Chapter 2. Updated subsection Current Settings in Chapter 2. Updated subsection Using the Stack Example with IIOP/SSL in Chapter 4. This edition of the HP NonStop CORBA 2.6.1 Getting Started Guide for C++ describes the following new features for HP NonStop CORBA 2.6.
(C) Copyright 2004 and 2011 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.
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.
Bold text 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.1 Glossary. UPPERCASE Uppercase letters indicate keywords and reserved words; enter these items exactly as shown. Items not enclosed LETTERS in brackets are required. For example: MAXATTACH Italic letters Items in Italic letters indicate variable items that you supply. Items not enclosed in brackets are required.
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.
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.
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. A NonStop CORBA subsystem creates resources during installation and setup. It is necessary to run the unconfigure script to remove these resources.
9. On the Installation Manifest screen review the file locations. You may click Back to go back and change them. When you are satisfied with them click Next. This step may take a few minutes to complete. 10. On the Installation Complete screen you may choose the check boxes to view the release documentation and to launch the DSM/SCM planner interface. It is recommended that you review the release documentation before proceeding to install NonStop CORBA. 11. Click Finish to complete running IPSetup.
Field Name Description OSS host name Name or IP address of the host system. OSS user ID User ID having write permission on the OSS directory for pax file (Guardian space) and Java OSS root directory. OSS password Password for the OSS user ID. 4. Supply a value for the OSS directory for pax file field. This value should be the installation subvolume (ISV) where IPSetup placed the software. You may type a new value as needed. Review the check boxes. Click Next to continue.
files 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.6 installation, program files are copied to the system but existing configuration files are untouched. Leaving this box checked means both program and configuration files (if they exist) are overwritten. Unpack Runtime pax file checked Leave this box checked to unpax the Runtime.
directory 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 OSS root dir files. If you use DSM/SCM, you may not change this value. OSS directory for Displays value The location where the pax and other installation files are copied. pax files entered previously. OSS directory for Displays value The location of the installation subvolume. ISV entered previously. 6.
values. Click Next to continue. Field Name Default Value Description Environment Z prefix Must be unique across all installed products. One letter attached to the front of some NonStop CORBA process names and some NonStop Services for CORBA process names. EMS collector $0 Name of the EMS collector. EMS template directory /G/SYSTEM/SYS00 Location of the EMS Templates. EMS object /G/SYSTEM/ZTEMPL template directory Location of the EMS template object files.
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.
Collector Process Specifies the EMS collector process used by the subsystem. The name is defined in NonStop Kernel format (for example, $ZNSD0). ENTER the Collector process you want to use or leave blank to use the current value $0: EMS template directory The location of the system file TEMPLATE is required for configuring and creating the template files. If you have multiple copies of this file you should use the one that is open.
================================================== Installing Multiple Copies of NonStop CORBA 2.6.1 on the Same Server Note: DSM/SCM allows only one location for each Independent Product installation. If you want to install a second copy of NonStop CORBA, you must do the installation directly, without using DSM/SCM. The DSM/SCM database will be unaware of any such subsequent installations.
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.
POA_ptr create_POA(const char* adapter_name, 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.
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.
catch {entitydelete sample_stack_client@ORB} entity sample_stack_client@ORB { ssl_client true Then run the example. Start the server program in one window by using the following command: server -ORBprofile sample_stack In the other window, start the client program by using the following command: client -ORBprofile sample_stack_client You should see the same output as before. Chapter 3.
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.
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.