HP NonStop CORBA 2.6.1 Getting Started Guide for Java HP NonStop CORBA 2.6.1 Getting Started Guide for Java Part number: 525934–005. Published July 2011. Legal Notice Abstract This manual provides information about getting HP NonStop™ CORBA® 2.6.1 for Java 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 Install JORB Lite on th
Index New and Changed Information
New and Changed Information New and Changed Information The updates in this edition (525934–005) are: Updated subsection Host name of machine in Chapter 2. Updated subsection Current settings in Chapter 2. The updates in this edition (525934–004) are: Updated the Event Service sub-section in the Introduction chapter. The updates in previous edition (525934–002) were: Added the following new features for HP NonStop CORBA 2.6.1: Support for IIOP/SSL for JORB. Support for NonStop Server for Java 4.0.
© 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 The NonStop CORBA Getting Started Guide for Java covers the material you need to know to get NonStop CORBA up and running.
Syntax Item Description 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.
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.
Decide how you want to install EMS templates. There are two ways to install the templates: 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.
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.
8. 9. 10. 11. of your choice. Click Next when you are satisfied with the locations. 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. 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.
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.
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 OSS root dir files. If 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 .
Install JORB Lite on the PC If you write applications in Java you may find JORB Lite useful. If you write applications only in C++ you do not need to install JORB Lite on the PC. See Installing JORB Lite and Running JORB Lite for more information. 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.
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.
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. For second or subsequent copies of NonStop CORBA installed on the same system, Each installation should be considered a new installation.
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.
If JTS is not being used and jts.jar is included in the application's classpath, application performance can be impacted. Remove jts.jar from the application's classpath if JTS is not being used. (In the past, including jts.jar in the application's classpath when JTS was not being used had little impact on application performance.) The adapter activator must extend org.omg.PortableServer._AdapterActivatorLocalBase . (In the past, an application adapter activator extended org.omg.PortableServer.
Chapter 4. Running the Java Stack Example Chapter 4. Running the Java Stack Example 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. The Stack example is a simple but fully functional CORBA program that has both a client and a server implemented in C++ and Java.
StackPackage/STACK_OVERFLOWHelper.java StackPackage/STACK_OVERFLOWHolder.java StackPackage/STACK_UNDERFLOW.java StackPackage/STACK_UNDERFLOWHelper.java StackPackage/STACK_UNDERFLOWHolder.java 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.
Chapter 5. Installing JORB Lite Chapter 5. Installing JORB Lite 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 percent pure Java, the JORB Lite SDK is a CORBA 2.6.
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. From the product CD, run the WORKSTATION\JORBLITE.EXE file. You will be prompted for a directory where you want to place the files. The default directory is c:\jorblite. If you want to enter a different directory name do so and continue.
The PATH and CLASSPATH Environment Variables The installer makes the following environment variable changes: The absolute path of the \bin directory is added to the PATH environment variable for your environment. A CLASSPATH environment variable is added and the absolute paths of \lib\jorblite.jar is added to this environment variable. The env.bat files provided with JORB Lite set the PATH and CLASSPATH environment variables.
Chapter 6. Running JORB Lite Chapter 6. Running JORB Lite 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. Building and Running the Stack Example To build and run the JORB Lite Stack example, open two DOS command-prompt windows.
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. Calling NonStop CORBA Applications from JORB Lite The Java language allows you to "Write once, Run anywhere," which means that you can generate JORB Lite clients and servers and move their generated .class bytecode files to the NonStop Kernel for execution in the NonStop CORBA environment.
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.
JORB Lite, Installing JORB Lite JORB Lite on PC, Install JORB Lite on the PC NonStop CORBA on host system, Install NonStop CORBA on the Host System NonStop Distributed Component Console on PC, Install the NonStop Distributed Component Console on the PC overview, Installation Overview performing, Overview of Installation Steps running the Install script, Run the Install Script subsystem resource cleanup, Perform Subsystem Resource Cleanup test JORB Lite install, Running JORB Lite Installer Setup Program, Run
scalability, Scalability of the Object Request Broker (ORB) Object Transaction Service (OTS), Transaction Protection and Data Integrity P 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 Subsystem resource cleanup, Perform Subsystem Resource Cleanup System architecture, Why No
