HP NonStop CORBA 2.3 Getting Started Guide Next HP NonStop CORBA 2.3 Getting Started Guide Part number: 520549002. Published October 2002. Legal Notice Abstract This manual provides information about getting HP NonStop" CORBA® 2.3 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.
Scalability of the Object Request Broker (ORB) Scalability of Application Server Processes Compatibility of NonStop CORBA Components Availability and Fault Tolerance Transaction Protection and Data Integrity Network Session Concentration Advantages of the Pathway Environment IIOP Protocol Support IDL Compiler Language Bindings Portable Object Adapter Object Method Invocation Naming Service and Interoperable Naming Service Bootstrap Daemon (BSD) Object Transaction Service (OTS)/Java TransactionService (JTS)
Ensure the ORB.properties Include CORBA and EJB Properties Create a Superset of ORB.properties Install NonStop CORBA over NonStop EJB Install the NonStop Distributed Component Console on the PC Install JORB Lite on the PC Start NonStop CORBA Server Processes on the Host System Alternative Installation Method Run the Install Script Sample Script Run 4.
JORB Lite Overview The JORB Lite Package Installing JORB Lite The JORB Lite Directory Structure The PATH and CLASSPATH Environment Variables Running the IDL Compiler 8.
Copyright 2002 Compaq Information Technologies Group, L.P. Compaq, the Compaq logo, Alpha, Atalla, CLX, Deskpro, Enform, Expand, Guardian, Himalaya, Inspect, Integrity, NonStop, OpenVMS, PayMaster, ProLiant, ServerNet, SignMaster, SNAX, Tandem, VAX, VMS, and WebSafe are trademarks of Compaq Information Technologies Group, L.P. in the U.S. and/or other countries.
information in this document is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for Compaq products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty.
New and Changed Information Prev Next New and Changed Information This publication has been updated to reflect new product names: ● Since product names are changing over time, this publication might contain both HP and Compaq product names. ● Product names in graphic representations are consistent with the current product interface. Installation prerequisites and migration information has been updated.
About This Guide Prev Next About This Guide Table of Contents Who Should Read This Guide Organization of this Guide Manuals in the NonStop CORBA Set Your Comments Invited Notation Conventions The NonStop CORBA Getting Started Guide covers the material you need to know to get NonStop CORBA up and running.
Section 7, Installing JORB Lite, describes how to install JORB Lite. Section 8, Running JORB Lite, describes how you can test your JORB Lite system setup by running one of the examples supplied with the JORB Lite package. Manuals in the NonStop CORBA Set The NonStop CORBA 2.3 Getting Started Guide describes how to install the product and verify installation. It also includes an introduction to the product. The NonStop CORBA 2.
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 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 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.#su-name If the syntax of a command is too long to be shown on a single line, each continuation line is indented three spaces, the first of which is separated from the preceding line by a blank line.
Chapter 1. Overview of Distributed Object Computing and CORBA Prev Next Chapter 1.
An application model that separates the user-interface functions, transaction processing functions, and database functions is called a three-tiered architecture. Object technology is suited to many different types of application models, varying in both the types and the number of tiers. Client/Server Computing with NonStop CORBA NonStop CORBA applications are client/server applications that run on Common Object Request Broker Architecture (CORBA) 2.3-based computer systems and networks.
Inheritance is the feature of object technology that provides for evolution and specialization of services. Inheritance allows you to define a new class to have the characteristics of another class, with specific additions or the replacement of features (overriding) in the base or parent class. Object inheritance lets you define an "isa" relationship between an object and its parent object. For example, suppose you have a "mammal" class.
● Most platforms do not ensure the availability, scalability, and transaction protection required for OLTP applications and electronic commerce. Addressing the Challenges Although these are formidable challenges, the distributed object architecture defined by the Object Management Group® (OMG") in CORBA 2.3 goes a long way toward addressing the problems unsolved in older object-oriented systems.
CORBA Common Object Services (COS), also called CORBAservices" include: ● Naming Service, for storing the bindings of object names ● Event Service, for asynchronous communication among objects ● Object Transaction Service (OTS), for ensuring the consistency of a database when a request involves multiple updates to databases or state repositories Client applications and object servers that comply with the standards of the CORBAservices can seamlessly interoperate with each other; that is, clients can r
Chapter 2. Introduction to NonStop CORBA Prev Next Chapter 2. Introduction to NonStop CORBA Table of Contents Why NonStop CORBA CORBA 2.
software. NonStop CORBA Release 2.3 is an implementation of the Common Object Request Broker Architecture (CORBA) defined and promoted by the Object Management Group (OMG). Because NonStop CORBA Release 2.3 is based on CORBA 2.3 as defined by the OMG, application clients and components you develop using NonStop CORBA can interoperate with other CORBA-compliant servers running on different platforms.
Also noteworthy, NonStop CORBA is language-compliant and object-adapter compliant with the OMG's CORBA ORB portability specification, which enhances the interoperability of the components you write using NonStop CORBA. Writing client and server objects compliant with CORBA 2.
number of Comm Servers. ● To provide additional external port connections, the administrator can add multiple instances of HP NonStop TCP/IP to the NonStop CORBA system. Each instance of NonStop TCP/IP increases the number of available TCP/IP ports and, therefore, the number of clients the ORB can support. Multiple instances of NonStop TCP/IP allow Comm Servers to listen on the same IP address or different IP addresses (port numbers must be unique within the scope of the TCP/IP process).
Availability and Fault Tolerance To support continuous availability, an object-oriented runtime environment must provide fault tolerance on the following three levels: ● The system platform ● The ORB ● The application components The NonStop CORBA system provides the first level of fault tolerance by running on the NonStop Kernel operating system, which offers such features as NonStop process pairs, mirrored disk controllers, and fault-tolerant communications subsystems.
Advantages of the Pathway Environment When you use the NonStop CORBA software you can gain all of the advantages of the Pathway environment, including ease of development, manageability, data integrity, and fault tolerance.
Language Bindings NSDIDL supports OMG standard C++ and Java language bindings, as defined in the OMG binding specifications. Portable Object Adapter The NonStop CORBA Portable Object Adapter (POA) supports the function defined in the CORBA portability specification. An Object Adapter is the primary way that an object implementation accesses the services an ORB provides.
● Defines the name syntax and parsing interface ● Standardizes bootstrapping to a common name context ● Requires id and kind attribute matching ● Adds support for URL (Uniform Resource Locator) names The Naming Service installs automatically when you install NonStop CORBA. Bootstrap Daemon (BSD) The Bootstrap Daemon (BSD) is a component of the Interoperable Naming Service. The BSD is needed for interoperability with other ORBs using the Bootstrap protocol.
requests for imported transactions within the pool of NSotsTMs by routing secondary import requests back to the NSotsTM that originally imported the transaction. In previous versions of NSOTS and NSJTS, the broker function was provided through a shared file. The current version of NSOTS and NSJTS replaces the file implementation with a singleton process called NSotsXID.
Chapter 3. Installing NonStop CORBA Prev Next Chapter 3.
● Check whether previous installations of NonStop Enterprise Java Beans (EJB) products are already installed on the system where you intend to install NonStop CORBA, as indicated in Check for Previously Installed Products. ● If you have not used the IPSetup program before, you may want to refer to the IPSetup User's Guide on the product CD for information about this installation utility. The file is USRGUIDE.PDF on the CD.
If NonStop EJB is installed, make a note of the values you have already defined for this product before proceeding with the NonStop CORBA installation. Perform Subsystem Resource Cleanup A subsystem cleanup does not have to be done in all cases. 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.
deleted RM NSOTSRMTX_MNO3 gtacl[9]: unable to propagate all environment variables deleted RM NSOTSRMTX_MNO4 gtacl[9]: unable to propagate all environment variables Install NonStop CORBA on the Host System The host system is a NonStop S-Series server. The installers run on your workstation. Run the IPSetup Program Exit all other Windows applications before starting to place NonStop CORBA software on the host. 1. Open the product CD by double clicking on the CD drive. 2. Click the View Readme file button.
3. On the Select a Program Manager Group screen, select a Program Manager Group to contain the NonStop CORBA SDK or RTK OSS Installer icon or accept the default group of NonStop CORBA. Click Next to continue. 4. If the installer cannot find the javaw.exe file (usually located in the JRE), the Java Runtime Environment (JRE) installation dialog box appears. In this dialog, you can specify where the JRE installation that contains javaw.exe is located.
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 checkboxes. Click Next to continue. Note You should leave the boxes checked for unpacking the pax files and rebuilding the JVM. Field Name Local pax file Local runtime pax file Default Value T0539PAX T0546PAX Description Cannot be changed. Cannot be changed. Must be unique across all installed products.
Uncheck this box if you are updating an existing NonStop CORBA installation. When updating a previous 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. The NonStop CORBA native library contains Guardian information and is linked into the JVM. Uncheck this box only if the native library has not changed since the last NonStop CORBA installation.
Must be unique across all installed products. Location of NonStop Server for Java. Must be unique across all installed products. NonStop CORBA OSS root dir usr/tandem/nsdoms Location of NonStop CORBA files. Location where the pax and other installation OSS directory for pax file Displays value entered previously. files are copied. Java OSS root directory /usr/tandem/java 6. Specify an admin DB directory.
Field Name Environment prefix EMS collector EMS template directory EMS object template directory OSS host name TCP process name TCP/IP base port number Security domain Business domain Default Value Description Must be unique across all installed products. One letter attached to the front of some NonStop CORBA Z process names and some NonStop Services for CORBA process names. $0 Name of the EMS collector. /G/SYSTEM/SYS00 Location of the EMS Templates.
8. The NonStop CORBA OSS Installer wizard indicates that the installation is complete. Click Finish. 9. Install the EMS template files. DSM/SCM option: During the IPSetup program operations, check the Use DSM/SCM box. Then IPSetup installs the EMS templates. Install templates with the INSTALL^TEMPLATES TACL macro option: Perform this installation after IPSetup has placed the NonStop CORBA installation files on the NonStop Kernel system.
Before You Begin Installing NonStop CORBA Over NonStop EJB Ensure that you have matched versions of NonStop EJB and NonStop CORBA 2.3. For example, NonStop EJB version 1.1 (A11)and NonStop CORBA 2.3 version B12 is a matched set. For matches, check the NonStop EJB Readme.txt file on the Distribution CD for the version of NonStop CORBA required for that NonStop EJB release. Ensure the ORB.properties Include CORBA and EJB Properties The orb.
These files are in your NonStop EJB installation subvol and root installation directory. The defaults are $SYSTEM.NSEJB and /usr/tandem/nsejb, respectively. 3. Stop the NonStop CORBA processes and the NonStop EJB applications from the Console. 4. Stop NSDAdminServer, NSDEnvironServer, and the PATHMON process (default name is $MY_PREFIX DAPM ), if it exists. This will free NSDSRL, which is required to run the NonStop CORBA installation. 5. Install the NonStop CORBA 2.
5. On the System Modifications screen, leave the Modify Java installation check box checked unless you wish to manually modify your Java installation. Click Next to continue. 6. On the Start Installation screen, click Next to proceed with the installation. 7. If you have chosen to install the JRE in Step 3, the Java Runtime Environment Setup program will take over and you will be asked to agree to the Java licensing agreement. Click Yes to continue.
If you enter a name, it must be one that can be found by a host name lookup (usually performed by the Domain Name Service). The Security Domain Selection dialog appears. 4. Select the security domain you defined during the installation, then click OK The Security Domain Authentication dialog appears. 5. Log onto the security domain by typing the user name and password for the security domain, then click OK.
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 "+" by the business domain to show the NonStop Services for CORBA node under the business domain. Click on the "+" by the node to expand the list to see the services. 8.
9. Verify the status of the server processes by doing the following: ● Right-click NonStop Services for CORBA. ● Select Server Status from the pull-down menu. A detailed status of each server is displayed. Alternative Installation Method You may choose to install NonStop CORBA on the NonStop system by using the Open System Services (OSS) shell prompt.
Start the script by typing >install Follow the script prompts to completion. After you have completed the installation, you can start the NonStop Services for CORBA by running the NonStop Distributed Console as described in Start NonStop CORBA Server Processes on the Host System. Alternatively, you may start by logging on to the OSS environment and running the nsdstart shell script. See the Administration Guide for more information about using scripts to start and configure your system.
ENTER the directory here (NEW or /G//): /G/system/master Prefix letter Specifies a unique prefix letter for the subsystem process names. Use this environment variable to prevent process-name conflicts if you have multiple JORB/DOM/CORBA/EJB 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.
ENTER base port number or leave blank to use the current value 4000 : Security domain Specifies the security domain name. ENTER security domain value USER.NSDOMS: Business domain Specifies the business domain name.
starting Admin server ================================================== NonStop(TM) CORBA SDK INSTALLATION COMPLETE ================================================== Prev Chapter 2. Introduction to NonStop CORBA Up Home Next Chapter 4.
Chapter 4. Considerations for Migrating from Previous Releases Prev Next Chapter 4. Considerations for Migrating from Previous Releases Table of Contents Product Level Migration Information Upgrading From NonStop DOM, NonStop JORB, and NonStop OTS/JTS to NonStop CORBA Update 2.3 Update 3 and Later Upgrading From NonStop CORBA 2.3 Update 1 to NonStop CORBA 2.3 Update 3 Upgrading From NonStop CORBA 2.
Product Version B11 B11 B12 B12 B12 B12 B13 IPM Identifier CD Update Number Update 1 AAB Update 2 Update 3 AAC Update 4 AAE Update 5 AAF Update 6 Update 7 Upgrading From NonStop DOM, NonStop JORB, and NonStop OTS/JTS to NonStop CORBA Update 2.3 Update 3 and Later NonStop DOM, NonStop JORB and NonStop OTS/JTS previously used NonStop Server for Java release 1.6. NonStop CORBA 2.3 Updates 3 through 6 require NonStop Server for Java release 2.0 or 2.1. Update 7 requires NonStop Server for Java 3.0.
If Update 1 was configured to use NonStop Server for Java release 1.6, it is best to install NonStop CORBA 2.3 in a unique location. Install NonStop Server for Java release 2.0 or later and continue with the NonStop CORBA 2.3 Update 3 installation. If the default NonStop CORBA 2.3 location is desired, perform the following step: 1. Stop all CORBA services for the default subsystem from the console. 2. The NSDCFGDB database may be saved between Update 1 and Update 3 of NonStop CORBA 2.3.
release 2.0 or later JVM. 5. Restart the CORBA services from the console. 6. For C++ and Java applications, refer to Moving from NonStop CORBA 2.3 Update 1 to NonStop Corba 2.3 Update 3 or Later. Installing Multiple Versions of NonStop DOM, NonStop JORB, and NonStop CORBA 2.3 Update 3 ● Each installation must be in its own directory. ● The PREFIX's and port numbers must be unique. ● Each installation will have its own NSDCFGDB and NAMINGDB.
Moving from NonStop CORBA 2.3 Update 1 to NonStop CORBA 2.3 Update 3 or Later For Updates 3 through 6, 1. C++ applications must be recompiled. 2. C++ IDL files must be recompiled by the new IDL compiler. 3. For Java applications, nothing needs to be done. For Update 7, 1. C++ applications must be recompiled. 2. C++ IDL files must be recompiled by the new IDL compiler. 3. Java IDL files must be recompiled by the new IDL compiler 4. Java source files must be recompiled using NonStop Server for Java version 3.
2. NonStop CORBA Service IDL-generated files are incorporated into the C++ ORB SRL (nsdsrl). Previously, applications were required to link with the service's archive file to use the service components. This link is no longer required. For example, if your C++ ORB application uses the Naming Service, the make step to build the executable was required to include the clause: -l$(NSD_ROOT)/lib/libnaming.a and/or -l$(NSD_ROOT)/lib/libeventservice.a These clauses must be removed because libnaming.
POA _default_POA() needs to be moved into the object implementation. 7. If an IDL contained a "const" declaration located within an "interface," then the generated constant identifier and its value have moved from: Package..value to . An application needs to change its references to the constant. If the following IDL example were followed: interface Stack { const long StackSize = 10; }; an old reference would be: int size = StackPackage.StackSize.
Chapter 5. Running the C++ Stack Example Prev Next Chapter 5. Running the C++ Stack Example Table of Contents The Stack Example Overview Building the Stack Example The Makefile Script Running the Stack Example 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.
The Makefile Script The Makefile script does the following: ● Uses the NonStop CORBA IDL compiler to process the interface contained in stack.idl. ● Builds the server executable by using the C++ compiler to compile the server components. ● Builds the client executable by using the C++ compiler to build the server components. The NonStop CORBA IDL compiler (NSDIDL), takes stack.idl file as input and produces the following four files: ● stack_client.h ● stack_client.cpp ● stack_server.
obtained by sourcing the env.sh script, as described in Configuration and Management Using Commands in the NonStop CORBA Administration Guide.
Chapter 6. Running the Java Stack Example Prev Next Chapter 6. Running the Java Stack Example Table of Contents The Stack Example Overview Building the Stack Sample Configuring NonStop CORBA for the Stack Example Running the Stack Example on OSS Once you have installed and configured your NonStop CORBA software, you can test the operation of your system by running a simple CORBA program.
Building the Stack Sample The Stack example comes complete with a "make" script which builds both the client and the server applications. The script, named "Makefile," performs the required steps to construct the executable components. To build the sample: 1. Log on to the system containing your NonStop JORB setup and go to the directory javasamples/stack. 2. Verify that the NonStop DOM etc/env.
These files contain the CORBA-specified "Java language mapping" translation of the interface definition provided in the stack.idl file. The compilation steps use the NonStop Server for Java tools to compile the programs. During the compilation, the Java compiler uses the NonStop JORB implementation files, which are located in the $JAVA_HOME/lib/jorb.jar file.
Got STACK_OVERFLOW exception as expected. Pop: 1000 Pop: 900 Pop: 800 Pop: 700 Pop: 600 Pop: 500 Pop: 400 Pop: 300 Pop: 200 Pop: 100 Got STACK_UNDERFLOW exception as expected. Once you are satisfied with the output, you can stop the server program (in the server OSS window) by pressing . If you see the output as described above, you have successfully built and run the Stack example on your NonStop CORBA system.
Chapter 7. Installing JORB Lite Prev Next Chapter 7. Installing JORB Lite Table of Contents JORB Lite Overview The JORB Lite Package Installing JORB Lite The JORB Lite Directory Structure The PATH and CLASSPATH Environment Variables Running the IDL Compiler JORB Lite Overview JORB Lite is a software development kit (SDK) and runtime environment that lets you develop CORBA applications in the Java programming language. Implemented in 100% pure Java, the JORB Lite SDK is a CORBA 2.
Stock Quote example Stock Dynamic example Located in the javasamples/stock directory Located in the javasamples/stock_dynamic example Documentation Name Comments Product documentation Located in the docs\javapubs\javadocs\javadoc directory Installing JORB Lite JORB Lite resides in a self-extracting executable file on your NonStop CORBA compact disc. This installation procedure assumes you have the Java SDK (version 1.1.2 or newer) installed. To install JORB Lite: 1.
Variable Default Setting Description JORBLITE_HOME c:\jorblite Root directory of your JORB Lite installation. JAVA_HOME c:\jdk 1.1.4 Root directory of your JDK installation. Assumes that you have the 1.1.4 JDK installed. For example, if you install JORB Lite into a directory other than c:\jorblite, you will have to modify the file etc\env.bat so that the JORBLITE_HOME environment variables reference the correct JORB Lite root directory.
idl2java In this command, is the name of the IDL file you want to compile. Prev Chapter 6. Running the Java Stack Example Up Home Next Chapter 8.
Chapter 8. Running JORB Lite Prev Next Chapter 8. Running JORB Lite Table of Contents Building and Running the Stack Example Building the Stack Example Running the Stack Example Calling NonStop CORBA Applications from JORB Lite Running Clients and Servers on Remote Machines After you have installed JORB Lite, you can test your system setup by running one of the examples supplied with the JORB Lite package.
Running the Stack Example You have now built the Stack client and server applications and are ready to test your JORB Lite system: 1. Open a second DOS command-prompt window. In this window, navigate to the Stack example directory. 2. In the first command-prompt window, execute the Stack server program by running the runserver.bat file. (Note that you can also run the runserverpoa.bat file to run the POA implementation.) 3.
Lite clients and servers and move their generated .class bytecode files to the NonStop Kernel for execution in the NonStop CORBA environment. You can also move only the client or server .class and their associated IOR files and allow JORB Lite applications to interoperate with NonStop CORBA applications. You can use JORB Lite as a build environment and NonStop CORBA as an execution environment. To test this technique, follow the steps above to build the Stack example on your PC.
Prev Chapter 7.
Index Prev Index A Application migration, considerations, Application Migration Considerations Application, migrating applications from NonStop DOM or NonStop JORB to NonStop CORBA 2.3 Update 3, Moving Any Application from NonStop DOM or NonStop JORB to NonStop CORBA 2.3 Update 3 NonStop Corba 2.3 Update 1 to NonStop CORBA 2.3 Update 3, Moving from NonStop CORBA 2.3 Update 1 to NonStop CORBA 2.3 Update 3 or Later NonStop JORB to NonStop CORBA 2.
Common Object Services (COS), CORBA Defines Standard Interfaces and Services Component reuse, Reuse of Existing Components CORBA compliance, CORBA 2.
installer wizard, Host Installation Installer Wizard installing multiple versions of software, Installing Multiple Versions of NonStop DOM, NonStop JORB, and NonStop CORBA 2.
installing, Installing JORB Lite interoperability, Running Clients and Servers on Remote Machines overview, JORB Lite Overview package, The JORB Lite Package running IDL compiler, Running the IDL Compiler running stack example, Running the Stack Example stack example, Building and Running the Stack Example test installation, Running JORB Lite L Language bindings, Language Bindings Legacy Wrapper Interface, Legacy Wrapper Interface Legacy applications, Migration and Integration of Legacy Applications M Mak
P Pathway environment, advantages of, Advantages of the Pathway Environment Polymorphism, Insulation of Clients From Server Implementation Details Portable Object Adapter (POA), Portable Object Adapter S Scalability application server process, Scalability of Application Server Processes Object Request Broker, Scalability of the Object Request Broker (ORB) Software and hardware requirements, Hardware and Software Requirements Static Invocation Interface (SII), CORBA Defines Standard Interfaces and Services
