HP NonStop Release 3.1 NSM/web Installation Guide Abstract This guide describes how to install NSM/web software on an HP NonStop™ server and also includes troubleshooting information for NSM/web. Product Version NSM/web H31 Supported Release Version Updates (RVUs) This publication supports J06.12 and all subsequent J-series RVUs and H06.23 and all subsequent H-series RVUs until otherwise indicated by its replacement publications.
Document History Part Number Product Version Published 529994-001 NSM/web G10 and G21 June 2005 529994-002 NSM/web H30 February 2011 663861-001 NSM/web H31 October 2011
Legal Notices Copyright 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.
HP NonStop Release 3.1 NSM/web Installation Guide Index Figures Legal Notices What’s New in This Manual v Manual Information v New and Changed Information v About This Manual vii Audience vii Related Documentation vii Notation Conventions xi 1. Installation (T2806H31 and Superseding SPRs) Planning for Installation 1-2 Installing NSM/web 1-7 1. Log On to the NonStop System 1-7 2. Extract Files 1-7 3. Start the Install Script 1-8 4. Enter the OSS Root Directory 1-9 5.
2. Installation (Pre-T2806H31 SPRs) Contents Uninstalling NSM/web Manually 1-20 2. Installation (Pre-T2806H31 SPRs) Software and Installation Requirements 2-2 Installing NSM/web 2-3 1. Extract Files 2-3 2. Start the Install Script 2-4 3. Enter the OSS Root Directory 2-4 4. Enter the Location for Web Pages 2-4 5. Enter the Location for Guardian Files 2-5 6. Enter the PATHMON Process Name 2-5 7. Enter the CPU Number for Servers 2-5 8. Enter the Server Priority 2-5 9. Enter the Home Terminal 2-6 10.
Contents Figure 1-1. Figure 2-1. Catalogs Tree Node Visible in NSM/web Logon Display Catalogs Tree Node Visible in NSM/web Logon Display HP NonStop Release 3.
Contents HP NonStop Release 3.
What’s New in This Manual Manual Information HP NonStop Release 3.1 NSM/web Installation Guide Abstract This guide describes how to install NSM/web software on an HP NonStop™ server and also includes troubleshooting information for NSM/web. Product Version NSM/web H31 Supported Release Version Updates (RVUs) This publication supports J06.12 and all subsequent J-series RVUs and H06.23 and all subsequent H-series RVUs until otherwise indicated by its replacement publications.
What’s New in This Manual Changes to the 529994-002 manual: 14. Verify Your Entries Added the following information in the Installing NSM/web section: 12. Enter the Base TCP/IP Port Number 13. Enter the Base Process Prefix Updated the output in section 3. Start the Install Script on page 1-8. Added a note on page 1-13. Updated a filepath in section, Installing and Configuring iTP WebServer on page 1-16. Added a note on page 1-19.
About This Manual This guide describes how to install NSM/web software on an HP NonStop server and includes troubleshooting information for NSM/web. Audience This guide is intended for system administrators or operators who need to install or use the NSM/web product. Related Documentation This manual is part of the HP NonStop SQL/MX library of manuals, which includes: Introductory Guides SQL/MX Comparison Guide for SQL/MP Users Describes SQL differences between SQL/MP and SQL/MX.
Related Documentation About This Manual Specialized Guides SQL/MX Installation and Management Guide Describes how to plan for, install, create, and manage an SQL/MX database. Explains how to use installation and management commands and utilities. SQL/MX Query Guide Describes how to understand query execution plans and write optimal queries for an SQL/MX database. SQL/MX Data Mining Guide Describes the SQL/MX data structures and operations to carry out the knowledge-discovery process.
Related Documentation About This Manual document can be accessed from the following documentation links available at the HP Business Support Center (BSC), http://www.hp.com/go/nonstop-docs: HP Integrity NonStop H-Series HP Integrity NonStop J-Series For more information about downloading online help, see the SQL/MX Installation and Management Guide.
Related Documentation About This Manual Programming Manuals Introductory Guides SQL/MX Comparison Guide for SQL/MP Users SQL/MX Quick Start SQL/MX Programming Manual for C and COBOL SQL/MX Programming Manual for Java Reference Manuals SQL/MX Reference Manual SQL/MX Messages Manual SQL/MX Glossary SQL/MX Connectivity Service Administrative Command Reference DataLoader/MX Reference Manual Specialized Guides SQL/MX Installation and Management Guide NSM/web Installation Guide SQL/MX Guide to Sto
Notation Conventions About This Manual Notation Conventions Hypertext Links Blue underline is used to indicate a hypertext link within text. By clicking a passage of text with a blue underline, you are taken to the location described. For example: This requirement is described under Backup DAM Volumes and Physical Disk Drives on page 3-2. General Syntax Notation This list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS.
General Syntax Notation About This Manual { } Braces. A group of items enclosed in braces is a list from which you are required to choose one item. The items in the list can be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: LISTOPENS PROCESS { $appl-mgr-name } { $process-name } ALLOWSU { ON | OFF } | Vertical Line.
Change Bar Notation About This Manual a blank line. This spacing distinguishes items in a continuation line from items in a vertical list of selections. For example: ALTER [ / OUT file-spec / ] LINE [ , attribute-spec ]… !i and !o. In procedure calls, the !i notation follows an input parameter (one that passes data to the called procedure); the !o notation follows an output parameter (one that returns data to the calling program).
Change Bar Notation About This Manual HP NonStop Release 3.
1 Installation (T2806H31 and Superseding SPRs) You install NSM/web by installing software on the HP NonStop system. Except for the browser and Java plug-in, no software needs to be installed on client workstations.
Installation (T2806H31 and Superseding SPRs) Planning for Installation Planning for Installation 1. Before installing NSM/web, review these software and installation notes: Pathway NSM/web runs as a small, independent, HP NonStop Pathway/iTS environment. OSS Many NSM/web files are stored in the HP NonStop Open System Services (OSS) directory hierarchy, and all NSM/web executables run as OSS processes. NSM/web executables NSMwebNSKServer performs utility commands.
Installation (T2806H31 and Superseding SPRs) Planning for Installation Firewalls T2806H31 NSM/web uses both HTTP connections and direct TCP/IP socket connections. The latter uses a set of pre-defined port numbers during NSM/web installation. To use NSM/web through a firewall, you must unblock the dedicated TCP/IP port that is configured during installation in the firewall settings. You must review the firewall settings before installing NSM/web.
Installation (T2806H31 and Superseding SPRs) Planning for Installation 2. Gather information about your NonStop system and Web server, and record the information on this worksheet. You will need this information to answer the prompts displayed by the NSM/web installation script: OSS root directory Description: The OSS directory in which you plan to install NSM/web files. Also referred to as the OSS Installation Directory.
Installation (T2806H31 and Superseding SPRs) Planning for Installation Home terminal Description: The home terminal for the NSM/web server and PATHMON processes. The home terminal is not used, but it must exist and be available for output. Example*: $ZHOME Your Value: _________________________________ TCP/IP processes Description: The Guardian process names for the running NonStop TCP/IP processes.
Installation (T2806H31 and Superseding SPRs) Planning for Installation Base TCP/IP port Description: To access NSM/web through the firewall, two consecutive ports must be open. Base TCP/IP port is the port that has the lesser value between the two consecutive port numbers. NSM/web client-server communication occurs on these two consecutive ports. For example, if you specify 45900 as the TCP/IP port number, NSM/web uses the TCP/IP ports 45900 and 45901.
Installation (T2806H31 and Superseding SPRs) Installing NSM/web Installing NSM/web 1. Log On to the NonStop System on page 1-7 2. Extract Files on page 1-7 3. Start the Install Script on page 1-8 4. Enter the OSS Root Directory on page 1-9 5. Enter the Location for Web Pages on page 1-9 6. Enter the Location for Guardian Files on page 1-9 7. Enter the PATHMON Process Name on page 1-9 8. Enter the CPU Number for Servers on page 1-10 9. Enter the Server Priority on page 1-10 10.
Installation (T2806H31 and Superseding SPRs) 3. Start the Install Script The NSM/web installation files are extracted and automatically placed in the /usr/tandem/NSMweb directory. You can copy the directory and its contents to any other location. 3. Start the Install Script At the OSS prompt, change the working directory to the OSS directory from which the NSM/web files were extracted in Step 2.
Installation (T2806H31 and Superseding SPRs) 4. Enter the OSS Root Directory 4. Enter the OSS Root Directory In the OSS installation directory section of the script, enter the full path name of the root OSS directory for your installation, or leave it blank to use the default: OSS Installation directory ========================== The root OSS directory for your installation. ENTER the directory here or leave blank to use the current value /usr/tandem/NSMwebServers : /usr/tandem/lobsterServers 5.
Installation (T2806H31 and Superseding SPRs) 8. Enter the CPU Number for Servers name must be of the form $ANNN where A is any letter and N is any letter or digit. ENTER the process name here or leave blank to use the current value $ZNSM: $ZLOB Checking for unused process name $ZLOB ... Process $ZLOB is available. 8. Enter the CPU Number for Servers Enter the CPU number to be used by the NSM/web servers, or leave it blank to use the default.
11. Enter the TCP/IP Configuration Installation (T2806H31 and Superseding SPRs) 11. Enter the TCP/IP Configuration Select the IP addresses on which NSM/web is to be available. You must specify all the IP addresses serviced by the Web server you instruct your users to use for NSM/web. The installer finds all available IP addresses and enables you to enter additional IP addresses that are not currently running. After all these addresses are gathered, you can select which ones you want NSM/web to service.
Installation (T2806H31 and Superseding SPRs) 12. Enter the Base TCP/IP Port Number Do you wish to enter another IP address manually (y/n) [default Y] ? :n Please select the IP addresses on which you want NSM/web to be installed: 192.168.101.221 on $ZTCP0 (y/n) [default N] ? :y 192.168.109.220 on $ZTC0 (y/n) [default N] ? :y 192.168.109.222 on $ZTC0 (y/n) [default N] ? :y 192.168.109.223 on $ZTC0 (y/n) [default N] ? :y 192.168.109.224 on $ZTC0 (y/n) [default N] ? :y 192.168.101.
Installation (T2806H31 and Superseding SPRs) 13. Enter the Base Process Prefix Base TCP/IP port ================ NSM/web requires exclusive use of two consecutive TCP/IP ports. These same ports will be used on all IP addresses on which NSM/web is installed. ENTER the lowest of the two consecutive port numbers here or leave blank to use the current value 9500: Checking 9500 on $ZTC0... Checking 9501 on $ZTC0... 13.
Installation (T2806H31 and Superseding SPRs) IP addresses: 192.168.101.221 192.168.109.220 192.168.101.223 192.168.109.221 192.168.108.200 on on on on on 15.
Installation (T2806H31 and Superseding SPRs) 16. Starting NSM/web and Verifying Installation 16.
Installation (T2806H31 and Superseding SPRs) 16. Starting NSM/web and Verifying Installation Installing and Configuring iTP WebServer The iTP WebServer product must be installed before you can access the NSM/web home page: 1. Install and configure iTP WebServer. For instructions, see the iTP Secure WebServer System Administrator’s Guide. 2. To access the NSM/web application, make these changes to the Web server’s configuration file (httpd.config): a. Make a backup of the httpd.config file.
Installation (T2806H31 and Superseding SPRs) 16. Starting NSM/web and Verifying Installation 5. Enter the following OSS commands: chown SUPER.SUPER:SUPER NSMwebServerFactory chmod u+s NSMwebServerFactory 6. Purge the PATHOUT file in the Guardian environment. You might get the following error message: "ERROR- $VOL.SUBVOL.PATHOUT: CREATE ERR 10" Starting the Browser and Navigating to the NSM/web Page Note. NSM/web provides a single-logon infrastructure across all its supported products (SQL/MX and MXCS).
Installation (T2806H31 and Superseding SPRs) Stopping NSM/web Security Considerations When logged on, the user has access privileges to all objects under the user ID that was specified at logon time, based on SQL/MX and MXCS rules. When performing SQL/MX tasks, the user who creates a catalog or schema is the owner of the catalog or schema and of objects created under them. To create objects, users must have appropriate SQL/MX permissions.
Installation (T2806H31 and Superseding SPRs) Uninstalling NSM/web by Using the unstall Script Uninstalling NSM/web Manually on page 1-20 Uninstalling NSM/web by Using the unstall Script If T2806H31 or a superseding product is installed on a NonStop system, you can use the unstall shell script to uninstall NSM/web. Note. If T2806H31 is not installed on your NonStop system, see Uninstalling NSM/web (T2806H31 is not Installed) on page 2-9.
Installation (T2806H31 and Superseding SPRs) Uninstalling NSM/web Manually 2. From OSS, issue a cd command to one of the three directories and run the unstall script. If, for example, CORBA executable files were installed in the directory /usr/tandem/lobsterServers, issue: cd /usr/tandem/lobsterServers Then issue: ./unstall 3. unstall prompts you for permission to uninstall NSM/web. Enter Y for yes and N for no. 4.
Installation (T2806H31 and Superseding SPRs) Uninstalling NSM/web Manually NSDCFGDB NSDSRL PATHCTL PATHOUT 4. Remove the NSM/web files installed in the OSS files directory: a. Change the directory to /usr/tandem/NSMweb: cd /usr/tandem/NSMweb b. Remove NSM/web files in the /usr/tandem/NSMweb/bin directory: /usr/tandem/NSMweb> rm -R ./bin/* /usr/tandem/NSMweb>rmdir bin c. Remove the NSM/web files in the /usr/tandem/NSMweb/log directory: /usr/tandem/NSMweb> rm -R .
Installation (T2806H31 and Superseding SPRs) Uninstalling NSM/web Manually HP NonStop Release 3.
2 Installation (Pre-T2806H31 SPRs) You install NSM/web by installing software on the NonStop system. Except for the browser and Java plug-in, no software needs to be installed on client workstations.
Installation (Pre-T2806H31 SPRs) Software and Installation Requirements Software and Installation Requirements Pathway NSM/web runs as a small, independent, HP NonStop Pathway/iTS environment. OSS Many NSM/web files are stored in the OSS directory hierarchy, and all of its executables run as OSS processes. NSM/web executables NSMwebNSKServer performs utility commands. One instance runs for each NSM/web client.
Installation (Pre-T2806H31 SPRs) Installing NSM/web User identification An NSM/web user must have a valid Guardian user name and password for the system on which the user wants to use NSM/web. Firewalls NSM/web uses both HTTP and direct dynamic TCP/IP socket connections. Because of the latter, you cannot use it through a firewall. CORBA NSM/web uses CORBA for applet communication to the NonStop system. There is no impact on your client machine or your NonStop system.
Installation (Pre-T2806H31 SPRs) 2. Start the Install Script 2. Start the Install Script Start the install script install from the directory that contains the installation files: /usr/tandem/NSMweb: .
Installation (Pre-T2806H31 SPRs) 5. Enter the Location for Guardian Files ENTER the directory here or leave blank to use the current value /usr/tandem/webserver/root/NSMweb: /usr/tandem/webserver/root/NSMweb/lobster 5. Enter the Location for Guardian Files In the Guardian installation section of the script, enter the location for Guardian files, or leave it blank to use the default: Guardian Installation directory =============================== The Guardian directory for your installation.
Installation (Pre-T2806H31 SPRs) 9. Enter the Home Terminal 9. Enter the Home Terminal Enter the server home terminal for the NSM/web servers and PATHMON process, or leave it blank to use the default: Home terminal ==================== The home terminal for NSM/web servers and PATHMON process. It will not be used but must exist and be available for output. ENTER the home terminal here or leave blank to use the current value $ZHOME: Checking for existing $ZHOME ... Process $ZHOME exists. 10.
Installation (Pre-T2806H31 SPRs) 12. Wait for the Completion Message Server priority : 160 Hometerm : $ZHOME TCPIP process : $ZTC0 IP address : 192.168.109.225 Do you want to change anything (y/n) [default Y] ?: n 12. Wait for the Completion Message The installation is complete when this message is displayed: ================================================== NSM/web INSTALLATION COMPLETE ================================================== /usr/tandem/NSMweb: 13.
Installation (Pre-T2806H31 SPRs) Stopping NSM/web Starting NSM/web Run the start NSM/web script from the NSM/web directory. This script starts the NSM/web Pathway environment: Note. To start the script the first time, you must be the super ID (255,255). cd /usr/tandem/NSMweb/lobster/bin ./startNSMweb After the initial installation is complete, you can allow other users to start NSM/web by using these steps: 1. Log on as the super ID (255,255). 2. Start an OSS prompt by using the osh command. 3.
Installation (Pre-T2806H31 SPRs) Security Considerations A server encounters an error. The user attempts to switch to a different subsystem (for example to SQL/MX, MXCS, or Tools). Security Considerations When logged on, the user has access privileges to all objects under the user ID that was specified at logon time, based on SQL/MX and MXCS rules. When performing SQL/MX tasks, the user who creates a catalog or schema is the owner of the catalog or schema and of objects created under them.
Installation (Pre-T2806H31 SPRs) Uninstalling NSM/web by Using the unstall Script Directory that contains Guardian file types for CORBA (for example, /G/system/lobster) To uninstall NSM/web from any one of these three directories, run the unstall script. The directories also contain these text files, which are used by the unstall script: instinfo, which contains the names of all the installation directories and the date of the installation.
Installation (Pre-T2806H31 SPRs) Uninstalling NSM/web Manually The uninstallation process is finished when this message appears: NSM/web has been uninstalled Uninstalling NSM/web Manually If, for any reason, the unstall script is unable to uninstall NSM/web, or if you have an older version of NSM/web that does not include the unstall file, use these steps to manually remove the software: Note.
Installation (Pre-T2806H31 SPRs) Uninstalling NSM/web Manually e. Remove the unfiles file, if present: /usr/tandem/NSMweb> rm unfiles f. Remove the instinfo file, if present: /usr/tandem/NSMweb> rm instinfo 5. Remove the NSM/web pages. Assuming that the Web server HTML content root directory is /usr/tandem/webserver/root/NSMweb, enter: /usr/tandem/webserver/root/NSMweb> rm -R * /usr/tandem/webserver/root> rmdir NSMweb 6. Remove NSM/web Guardian files.
3 Troubleshooting This section provides troubleshooting information for NSM/web and covers these topics: Java Runtime Versions on page 3-1 Diagnostic Tips on page 3-1 Performance Notes on page 3-2 Choosing the Correct IP Addresses for Installation on page 3-3 Problems Contacting the NSM/web Server Factory on page 3-3 NonStop DOM and CORBA on page 3-5 Security on page 3-5 Browser Considerations on page 3-5 Displaying Process Names Used by the MXCS Subsystem on page 3-7 Java Runtime Ver
Performance Notes Troubleshooting Section 2, Installation (Pre-T2806H31 SPRs) of this guide, which describe the directories and file locations for NSM/web software components. Client side Open your browser’s Java console to see runtime error messages. For example, if your browser is Internet Explorer, select Tools > Sun Java Console. Server side View the textual log files in NSM/web’s log directory: NSMwebStderr.txt Text written to standard error by NSM/web processes. NSMwebStdout.
Choosing the Correct IP Addresses for Installation Troubleshooting Choosing the Correct IP Addresses for Installation Suppose that the iTP WebServer is properly configured. Look in the Web server's configuration file. For example: /usr/tandem/webserver/conf/httpd.
Problems Contacting the NSM/web's Comm Server Process Troubleshooting The WebServer has cached a stale version of the factory's IOR (Interoperable Object Reference) file. To fix this problem, you can flush the WebServer's cache (/usr/tandem/webserver/conf/vcache script). Note. If the WebServer was installed by the super user ID (255, 255), you must have super-user privileges to flush the WebServer’s cache. You can also add the following to the WebServer's /usr/tandem/webserver/conf/ local.
NonStop DOM and CORBA Troubleshooting The Comm Server process name of the form $NC is already in use by another process on the system. To fix this problem, reinstall NSM/web using the same or a different prefix letter for the process name. NonStop DOM and CORBA NSM/web uses CORBA as the communication transport between the applets in the browser and the NSM/web servers on NonStop systems. The CORBA client side is included in the Java run time.
Browser Considerations Troubleshooting One way to grant access to these jar files is to create a Java user policy file named .java.policy in your user directory: {user.home}/.java.policy (Solaris) {user.home}\.java.policy (Win32) Note. user.home refers to the value of the system property named user.home. This property specifies the user’s home directory. On Win32 systems, given the user name uName, the user.
Displaying Process Names Used by the MXCS Subsystem Troubleshooting Displaying Process Names Used by the MXCS Subsystem The processes used by MXCS in NSM/web are not initially shown. To display the process names: 1. With MXCS in the active window, click anywhere within the left-hand or right-hand panes in the applet. 2. Press Ctrl-s. A panel showing the process names used by the applet appears below the tree panel. 3. Press Ctrl-s again to close the panel. HP NonStop Release 3.
Troubleshooting Displaying Process Names Used by the MXCS Subsystem HP NonStop Release 3.
Index B I Browsers 1-2, 2-2, 3-5 Install script 1-7 Installation directories 1-17 files, removing 1-16 planning 1-2/1-5, 2-2 verifying 2-7 instinfo file 1-17, 1-20 inst* files 1-16 IOR file 3-4 IP addresses, choosing 2-6, 3-2, 3-4 iTP WebServer 1-14 C Catalog and schema owner 1-16 Completion message 1-12, 2-7 CORBA 1-3, 2-3, 3-5 CPU for NSM/web server processes 1-4, 2-5 D Diagnostic tips 3-2 Directories, installation 1-17 Disk space 1-3, 2-3 DNS names 1-5 DSM/SCM 1-1, 2-1 J Java runtime versions 3-1 J
O Index NSM/web installation directories 1-17 installing 1-1/1-16, 2-1/2-9 license 1-7 logging on 1-15, 2-8 reinstalling 1-5 security 1-16, 2-9 software requirements 2-2 starting 1-14, 2-8 stopping 1-16, 2-8 uninstalling 1-17, 1-18, 2-9 O Online help 1-16, 2-9 OSS installation directory 1-4 processes 1-2, 2-2 root directory 1-4, 1-8, 2-4 T T2806H31 1-1, 2-1 T2806OSS 1-16 T2806PAX 1-16, 2-3 T2806PAX file 1-6 T2806VOL 1-16 T2806WEB 1-16 Troubleshooting 3-1/3-7 U unfiles file 1-17, 1-20 unstall file 1-17,
