Hewlett Packard Enterprise NonStop Software Essentials Installation and Quick Start Guide
Reklama
Reklama
NonStop Software Essentials
Installation and Quick Start Guide
Part Number: 575074-009
Published: September 2016
Edition: L15.02, J06.03, H06.09, and all subsequent RVUs.
© Copyright 2016, 2015, 2016 Hewlett Packard Enterprise Development LP
The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.
Confidential computer software. Valid license from Hewlett Packard Enterprise 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.
Export of the information contained in this publication may require authorization from the U.S. Department of Commerce.
Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise website.
Acknowledgments
Intel ®, Itanium®, Pentium®, Intel Inside®, and the Intel Inside logo are trademarks of Intel Corporation in the United States and other countries.
Microsoft ® and Windows® are trademarks of the Microsoft group of companies.
Java and Oracle are registered trademarks of Oracle and/or its affiliates.
UNIX ® is a registered trademark of The Open Group.
Motif, OSF/1, UNIX, X/Open, and the "X" device are registered trademarks, and IT DialTone and The Open Group are trademarks of The Open
Group in the U.S. and other countries.
Open Software Foundation, OSF, the OSF logo, OSF/1, OSF/Motif, and Motif are trademarks of the Open Software Foundation, Inc. OSF MAKES
NO WARRANTY OF ANY KIND WITH REGARD TO THE OSF MATERIAL PROVIDED HEREIN, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. OSF shall not be liable for errors contained herein or for incidental consequential damages in connection with the furnishing, performance, or use of this material.
© 1990, 1991, 1992, 1993 Open Software Foundation, Inc. The OSF documentation and the OSF software to which it relates are derived in part from materials supplied by the following:© 1987, 1988, 1989 Carnegie-Mellon University. © 1989, 1990, 1991 Digital Equipment Corporation. ©
1985, 1988, 1989, 1990 Encore Computer Corporation. © 1988 Free Software Foundation, Inc. © 1987, 1988, 1989, 1990, 1991 Hewlett-Packard
Company. © 1985, 1987, 1988, 1989, 1990, 1991, 1992 International Business Machines Corporation. © 1988, 1989 Massachusetts Institute of
Technology. © 1988, 1989, 1990 Mentat Inc. © 1988 Microsoft Corporation. © 1987, 1988, 1989, 1990, 1991, 1992 SecureWare, Inc. © 1990,
1991 Siemens Nixdorf Informationssysteme AG. © 1986, 1989, 1996, 1997 Sun Microsystems, Inc. © 1989, 1990, 1991 Transarc Corporation.
OSF software and documentation are based in part on the Fourth Berkeley Software Distribution under license from The Regents of the University of California. OSF acknowledges the following individuals and institutions for their role in its development: Kenneth C.R.C. Arnold, Gregory S.
Couch, Conrad C. Huang, Ed James, Symmetric Computer Systems, Robert Elz. © 1980, 1981, 1982, 1983, 1985, 1986, 1987, 1988, 1989
Regents of the University of California.
Contents
1 Introduction to NonStop Software Essentials......................................................8
3 NonStop Software Essentials Prerequisites......................................................10
8 Installing NonStop Software Essentials to a non-default location.....................24
9 Configuring and Starting NonStop Software Essentials....................................25
Contents 3
10 Using NonStop Software Essentials as a Replacement for the Planner
Overview of the Similarities and Differences between NonStop Software Essentials and the
4 Contents
Figures
Tables
Examples
Example of addresses allowed to the local host and IP addresses 1.2.3.4 and 5.6.7.8.............20
6
About this Document
This guide provides the following information for getting started with the HPE NonStop Software
Essentials product:
•
“Introduction to NonStop Software Essentials” (page 8)
•
“Upgrade and migration prerequisites” (page 9)
•
“NonStop Software Essentials Prerequisites” (page 10)
•
“Quick Start Installation Guide” (page 13)
•
“Installing NonStop Software Essentials” (page 14)
•
“Creating a NonStop Software Essentials client certificate (using Oracle Java tools)” (page 21)
•
“Creating a NonStop Software Essentials client certificate (using OpenSSL tools)” (page 23)
•
“Installing NonStop Software Essentials to a non-default location” (page 24)
•
“Configuring and Starting NonStop Software Essentials” (page 25)
•
“Using NonStop Software Essentials as a Replacement for the Planner Interface” (page 30)
Supported Release Version Updates (RVUs)
This guide supports L15.02, J06.03, H06.09, and all subsequent RVUs unless otherwise indicated in a replacement publication.
New and Changed Information in the 575074-009 Edition
New product features allow you to:
•
Install NonStop Software Essentials in a system location other than C:\Program Files.
•
Create SH256 certificates for the NonStop Software Essentials client.
•
Create certificates for NonStop Software Essentials servers.
•
Use NonStop Software Essentials with Microsoft Internet Explorer without being required to be in Compatibility mode.
New and Changed Information in the 575074-008R Edition
Updated Hewlett Packard Enterprise references.
New and Changed Information in the 575074-008 Edition
The following sections of this guide version have been updated:
•
“New features for NonStop Software Essentials 5.1” (page 8)
•
“NonStop Software Essentials Prerequisites” (page 10)
•
“NonStop Server Software Requirements” (page 11)
For a complete list of fixes and enhancements for the NonStop Software Essentials product, see the NonStop Software Essentials Server softdoc (T0894) and the NonStop Software Essentials
Client softdoc (T0895).
This guide, the NonStop Software Essentials Installation and Quick Start Guide, is on the web at:
http://www.hpe.com/info/nonstop-docs
Under NonStop Technical Library, select the desired HPE Integrity NonStop Series: L-Series,
J-Series, or H-Series.
Related Information
Document
NonStop System Console Installer Guide
Web Location http://www.hpe.com/info/nonstop-docs
Under NonStop Technical Library, select the desired Integrity
NonStop Series: L-Series, J-Series, and H-Series.
Publishing History
Part Number
575074-009
575074-008R
575074-008
575074-007
575074-006
575074-005
Product Version
NonStop Software Essentials 5.1
NonStop Software Essentials 5.0
NonStop Software Essentials 5.0
NonStop Software Essentials 4.0
NonStop Software Essentials 2.1.0
NonStop Software Essentials 2.0
Publication Date
September 2016
November 2015
August 2015
February 2015
February 2013
May 2012
Related Information 7
1 Introduction to NonStop Software Essentials
NonStop Software Essentials is a software installation and management tool for all NonStop servers. NonStop Software Essentials uses DSM/SCM server software and provides a replacement for DSM/SCM Planner and CNFGINFO Interface functions, as well as certain Host Maintenance
Interface functions. The software coexists with DSM/SCM; you can use either NonStop Software
Essentials or the DSM/SCM Planner Interface for tasks with overlapping functionality (see
NonStop Software Essentials as a Replacement for the Planner Interface” (page 30)
).
NOTE:
The DSM/SCM Planner Interface is not supported on 64-bit system consoles. This support limitation includes NonStop system consoles running Windows 2008 Server, or using it with J06.19 and later or L15.02 and later. In these cases, the NonStop Software Essentials interface must be used in place of the DSM/SCM Planner Interface.
The NonStop Software Essentials user interface is a stand-alone application and provides:
•
A user-friendly interface (see
“Overview of the Similarities and Differences between NonStop
Software Essentials and the DSM/SCM Planner Interface” (page 30) ).
•
Enhanced security that provides encryption for all data passed to NonStop servers.
•
Enhanced software audit.
•
Unified request status where NonStop Software Essentials provides a consolidated request status, allowing you to view status from multiple Expand-connected systems. DSM/SCM interfaces do not show complete status of requests that span several NonStop servers. For example, a build/apply request has four sequential activities, starting on the host system, then on the target system, and ending back on the host system. The host and target system interface does not show the complete status of activities, even when the host and target are the same system.
For more information on using NonStop Software Essentials, see the online help available from any NonStop Software Essentials home page.
New features for NonStop Software Essentials 5.1
New NonStop Software Essential 5.1 features include the following:
•
NonStop Software Essential no longer requires you run Internet Explorer in Compatibility mode.
•
NonStop Software Essentials can now be installed in other directories besides the
C:\Program Files directory.
•
Certificates can be created for NonStop Software Essentials servers.
•
Certificates can be created for NonStop Software Essentials clients.
8 Introduction to NonStop Software Essentials
2 Upgrade and migration prerequisites
Upgrading from NonStop Software Essentials 1.0
If you are upgrading from NonStop Software Essentials 1.0, you must install NonStop server components on all host systems before installing the 2.0 (or later) client component.
More information
•
“Starting the NonStop Software Essentials Server Process” (page 26)
•
“Installing the NonStop Server Component” (page 14)
Migrating from the DSM/SCM Planner Interface
Migrate from the DSM/SCM Planner Interface after you have met all NonStop Software Essentials prerequisites and have installed NonStop Software Essentials.
More information
•
“Installing NonStop Software Essentials” (page 14)
.
•
“NonStop Software Essentials Prerequisites” (page 10)
DSM/SCM Upgrade Sequence prerequisites
If you are upgrading DSM/SCM SPRs to T6031 ACS (or later) for H/J-series, upgrade all target systems before the host system. Upgrading target systems first prevents problems due to a change in the snapshot file format on earlier versions of DSM/SCM.
Upgrading from NonStop Software Essentials 1.0
9
3 NonStop Software Essentials Prerequisites
Prerequisites for installing and using NonStop Software Essentials include:
•
Verifying that the correct T-number is installed on your specific system.
•
Ensuring that your Windows system meets the minimum requirements.
•
Ensuring that your NonStop server meets the minimum requirements.
More information
•
“T-number Compatibility” (page 10)
•
“Windows System Requirements” (page 10)
•
“NonStop Server Software Requirements” (page 11)
T-number Compatibility
Before installing NonStop Software Essentials, be sure to install the correct T-number version for your system.
NonStop Software
Essentials Server
L-series
H-series and J-series
G-series
T-number
T0894—L-series SPR (H02 AAH, for NonStop Software Essentials 5.0) is included on the
L15.08 SUT. Subsequent updates, including H02 AAI for NonStop Software Essentials 5.0, are downloadable from Scout.
T0894—Minimum supported H-series and J-series SPRs are included on H06.25 and J06.14
SUTs; subsequent updates, including H02 AAI for NonStop Software Essentials 5.0, are downloadable from Scout.
Not supported.
NonStop Software
Essentials Client
Windows
T-number
T0895—Minimum supported versions can be installed from the HPE Insight Control for
NonStop DVD that ships with the HPE NonStop System Console Installer DVD, Update 17 and later. Version T0895 V02 AAH, for NonStop Software Essentials 5.0, can be installed from HPE Insight Control for NonStop DVD, Update 25. SPRs are also downloadable from
Scout.
Windows System Requirements
The NonStop Software Essentials client component (T0895) can be installed on any 64-bit system running Microsoft Windows that has:
•
At least 4 GB of available memory (8 GB is recommended).
•
Internet Explorer 11.0.32 or later.
NOTE:
With Internet Explorer, you must add about:blank as a trusted sites. To do so:
1.
From any Internet Explorer window, click Tools→Internet Options→Security.
2.
From the Security tab, click either Local Intranet→Sites→Advanced or Trusted
Sites→Sites.
3.
In the Add this website to the zone: field, enter About.blank, and click
Add→Close→OK.
10 NonStop Software Essentials Prerequisites
•
Connectivity to a secure operations LAN (for access to the OSM Event Viewer).
•
Secure sockets layer (SSL) enabled in OSM (see
“Configuring OSM (Conditional)” (page
NOTE:
The Windows system can be either be a:
•
Physical system running Windows directly on the physical computer
•
Virtual system running Windows on a VM with the hypervisor being VMWare ESX 3.5 (and later) or ESXi 4.1 (and later)
NonStop Server Software Requirements
The NonStop Software Essentials Server component is T0894. Before installing the NonStop
Server Component (see
“Installing the NonStop Server Component” (page 14)
), the NonStop server must have the following minimum RVU and SPRs, as appropriate, for the type of NonStop servers to be managed with NonStop Software Essentials.
Minimum OSM SPR
1
Minimum RVU
L15.02
T0682 L02 ADM—already on L15.02 SUT
J06.03
T0682 H02 ABI—available on J06.03 (and later)
H06.09
T0682 H02 ABI—available on H06.14 (and later)
1
Required for OSM Event Viewer
NOTE:
Specified RVUs and SPRs are minimum required versions; you can always download later versions from Scout or these packages, if available.
DSM/SCM Requirements
The minimum required DSM/SCM SPRs for use with NonStop Software Essentials are listed in
“DSM/SCM SPRs required for use with NonStop Software Essentials” (page 11) .
Table 1 DSM/SCM SPRs required for use with NonStop Software Essentials
Minimum RVU
L15.02
J06.03
H06.09
Minimum DSM/SCM SPR
T6031 H03 ADG—already on L15.02 SUT
T6031 H02 ACW
T6031 H02 ACW
Other software products required or recommended for use with DSM/SCM in the NonStop
Software Essentials environment include Expand, SQL/MP, TMF, Pathway, and SWID.
Expand
Expand is required on both the target and host systems. If you have a host or target system that uses only tape for communication, Expand is optional and must be licensed.
SQL/MP
DSM/SCM uses an SQL database to manage software. If SQL/MP is present on the system, it is included as a limited version that is sufficient for DSM/SCM but not other usage. SQL/MP is included in the base NonStop OS installation.
NonStop Server Software Requirements 11
TMF
Because the TMF audits the DSM/SCM database, it must be installed on your host system (as part of the base NonStop OS installation).
Pathway
Many DSM/SCM functions are based on the Pathway environment and must be installed on all host and target systems. If Pathway is present on the system, it is included as a limited version.
This version is sufficient for DSM/SCM but not other usage. It is included in the base NonStop
OS installation.
Software Identification (SWID)
SWID provides unique identification of all NonStop system files distributed to customers. This unique identifier is known as the fingerprint of the file. The file is used to perform software inventory, version analysis, and delivery. Each product version of DSM/SCM requires a specific product version of SWID.
12 NonStop Software Essentials Prerequisites
4 Quick Start Installation Guide
To begin the NonStop Software Essentials installation process:
1.
Verify that all NonStop Server Software prerequisites are met (see “NonStop Server Software
).
2.
Install the NonStop Software Essentials server product on the host system by using either the Software Essentials interface or the DSM/SCM Planner Interface (see
NonStop Server Component” (page 14) ).
3.
After ensuring that you have met all of the Windows requirements (see
), install the NonStop Software Essentials client software on your
Windows system (see
“Installing the Client Component on Windows-based System”
4.
If the TCP/IP stack to be used for communication with the Windows-based console running
NonStop Software Essentials is not one of the default stacks, configure additional TCP/IP stacks (see
“Configuring TCP/IP Stacks Outside of the Dedicated Maintenance LAN
).
5.
Start the NonStop Software Essentials server process (see
“Starting the NonStop Software
Essentials Server Process” (page 26)
).
6.
To enable SSL (secure sockets layer), if it is not already enabled, or to configure additional
TCP/IP stacks in OSM, see
“Configuring OSM (Conditional)” (page 27) .
7.
Launch NonStop Software Essentials. For more information, see
Software Essentials” (page 28)
.
13
5 Installing NonStop Software Essentials
Installing the NonStop Software Essentials product components, as needed, involves server and
Windows-based system components.
Installing the NonStop Server Component
NOTE:
NonStop Software Essentials 2.0 (or later) components are not compatible with NonStop
Software Essentials 1.0 components. Be sure to install the 2.0 (or later) NonStop Server component (T0894 H02 or later) on all hosts before installing the 2.0 (or later) client component.
You can use the NonStop Software Essentials 1.0 interface to install the 2.0 (or later) NonStop
Server component, as described in
“Installing the NonStop Server Component”
. After the revision containing the NonStop Software Essential 2.0 (or later) server product has been activated, you must install the 2.0 (or later) client component on the CMS before using NonStop Software
Essentials on those upgraded host systems (see
“Installing the Client Component”
).
Two methods exist for installing the NonStop Software Essentials server component, depending on whether you already have an earlier version installed:
•
Method 1—If the T0894 H02 (or later) version of NonStop Software Essentials server component is installed on your system and you have a NonStop Software Essentials client version later than 2.0, use the installation procedure detailed in
Component from SUT or SPR” (page 14) .
•
Method 2—If the NonStop Software Essentials server, T0894 H02 (or later), is not already installed on the system and you do not have NonStop Software Essentials 2.0 or earlier on the system or the ability to use the DSM/SCM Planner Interface to install T0894 H02 (or later), use the installation procedure detailed in
“Installing the Server Component Manually”
NOTE:
T0894 H02 was included on J06.14/H06.25 and later SUTs, so the manual process for installing NonStop Software Essentials server is not necessary.
NOTE:
The SPR for the NonStop Software Essentials 5.0 server component (T0894 H02^AAH) is included on the L15.08 SUT, so it is not necessary to install the NonStop server at all unless the subsequent SPR is available.
Installing the Server Component from SUT or SPR
This primary method of installing or upgrading the NonStop Software Essentials server component involves using NonStop Software Essentials, since the DSM/SCM Planner Interface is not supported on 64-bit consoles. Use this procedure unless your scenario necessitates using the manual installation process, as described in
“Installing the NonStop Server Component” (page 14) .
To install the NonStop Software Essentials server component on a NonStop server to be used as a host:
1.
Having acquired the NonStop Software Essentials SPR (T0894), either on a SUT or from
Scout, launch either NonStop Software Essentials (see
Essentials” (page 28) ) or the DSM/SCM Planner Interface (if available), and then perform
steps
through
. Use NonStop Software Essentials if you already have both the client component installed on the console and an existing server component version running on the NonStop system.
2.
Receive T0894 into the software archive.
3.
Create a new software revision for your target system. Cloning can be used to install the software to multiple similar target systems simultaneously, provided they have identical hardware and volume names.
14 Installing NonStop Software Essentials
4.
Copy T0894 into the new revision.
5.
Perform a build/apply.
6.
If a new version of T6031 (DSM/SCM) is being installed with NonStop Software Essentials, run STOPSCM in the Target SubVolume (TSV) where DSM/SCM is installed.
7.
To activate the new revision, run ZPHIRNM, which includes the NonStop Software Essentials files in $SYSTEM.ZNSE.
8.
If you ran STOPSCM (because of a T6031 SPR upgrade), run STARTSCM to migrate to the newer version of T6031.
NOTE:
If you used the NonStop Software Essentials 1.0 interface to install the NonStop server component, the 1.0 interface no longer works on that host system after the new revision containing
NonStop Software Essentials 2.0 (or later) is activated. (If you used the DSM/SCM Planner
Interface, you can continue to use that on the host system.) Repeat the server installation process for all host systems. After all host systems have been upgraded to the NonStop Software
Essentials 2.0 (or later) server product, you must install the 2.0 (or later) client component (see
“Installing the Client Component” (page 16)
) on each CMS. If host systems continue to use
NonStop Software Essentials server version 1.0, at least one CMS must have the 1.0 client version installed for use with that host, since mixed client and server versions are not compatible.
If a system load is not done after installing the NonStop server component, you must start the
NonStop Software Essentials process, as described in
“Starting the NonStop Software Essentials
.
For more information, see the NonStop Software Essentials Server softdoc (T0894).
Installing the Server Component Manually
Use the manual server component installation method to install the NonStop Software Essentials server component on a NonStop system. Do so only if NonStop Software Essentials server,
T0894 H02 (or later), is not already installed on the system and you do not have NonStop Software
Essentials 1.0 or the ability to use the DSM/SCM Planner Interface to install or upgrade the
NonStop Software Essentials server component on the system to T0894 H02 (or later). Otherwise, install or upgrade the NonStop Software Essentials server component using the DSM/SCM
Planner Interface from an available NonStop System Console, or even from a PC outside of the dedicated service LAN, if possible (see
“Installing the Server Component from SUT or SPR”
for more information). Install the server component only if the DSM/SCM Planner
Interface is not supported on 64-bit consoles (which includes NonStop system consoles running
Windows 2008 Server) or with J06.19 or later, or on L15.02 or later.
To install the NonStop Software Essentials server component manually on a NonStop system:
1.
If you are installing the NonStop Software Essentials server SPR from the SUT, enter the following commands from a TACL prompt, and then proceed to Step
RESTORE {sut-tape-drive}, $*.E0894*.*, volume $SYSTEM.ZNSE, LISTALL
(where nn is the product version)
VOLUME $SYSTEM.ZNSE
2.
If you are installing the NonStop Software Essentials server SPR from Scout: a.
Download the appropriate T0894 SPR from Scout, and place the DSV in
$SYSTEM.E0894ipm
(where ipm is the IPM identifier).
b.
From a TACL prompt, enter:
VOLUME $SYSTEM.ZNSE
c.
Enter:
FUP DUP $SYSTEM.E0894ipm.*, *, SOURCEDATE
(where ipm is the IPM identifier) d.
Proceed to Step
.
Installing the NonStop Server Component 15
3.
Enter:
FUP PURGE (A0CINFO, T0894xxx)
(where xxx is the product version or IPM identifier)
4.
Enter:
FUP RENAME ZNSEGP, ZCNFDEFS.ZNSEGP
5.
Enter:
ZMODGP ZCNFDEFS.ZNSEGP
6.
Enter:
SCF START PROCESS $ZZKRN.NSE-HTTP
7.
After the NonStop Software Essentials client component has been installed on NonStop system consoles that are running Windows 2008 Server, use the NonStop Software Essentials interface to perform software management tasks, such as installing a new RVU
Installing the Client Component
The NonStop Software Essentials client component for Windows is delivered on the HPE Insight
Control for NonStop DVD that ships along with HPE NonStop System Console Installer DVD
(Product ID: 7X-SWV2/HNSC-SWV2/QNSC-SWV2), Update 17 and later. Version T0895 V02
AAH, for NonStop Software Essentials 5.0, can be installed from the HPE Insight Control for
NonStop DVD, Update 26. SPRs are also downloadable from Scout.
Installing the Client Component on Windows-based System
Pre-Installation Notes:
Make sure that the:
•
Windows-based system meets all Windows system requirements (see
).
•
NonStop Software Essentials 5.1 stand-alone client does not interfere with prior NonStop
Software Essentials client versions that are a plug-in to HPE SIM (4.0 and earlier).
To install the Windows client component:
1.
If you are using Scout to acquire the Windows Component Installer: a.
Extract the contents of the Y0895xxx.EXE file (xxx being the product version or IPM identifier) to a temporary directory.
b.
Run setup.exe from that directory.
The installer proceeds from
through
.
2.
If you are using the HPE Insight Control for NonStop DVD to acquire the Windows Component
Installer, run the installer at \NonStop Essentials\Windows\Software Essentials\
Setup.exe
.
The installer proceeds from
through
3.
Wait for NonStop Software Essentials to verify that a 64-bit system is being used. If a 64-bit system is not used, an error is displayed, and the installer aborts after the user acknowledges the error.
4.
Copy the previously installed NonStop Software Essentials 5.0 files to a backup location, if possible. (This action may fail with no error other than in the log file mentioned later.)
5.
To preserve previous changes, if any, locate the NonStop Software Essentials 4.0 (or earlier) site properties file, and copy it into the NonStop Software Essentials 5.1 installation folders.
6.
After Ready to Install appears and indicates the product and version being installed, click Install to continue with the installation.
16 Installing NonStop Software Essentials
7.
Note that Installing appears, and a progress bar is displayed as the system copies all required files to the appropriate locations.
NonStop Software Essentials services are started. This action is briefly noted in the installer window.
8.
Note that Finish appears. If the C:\ZSUPPORT\install folder exists, log of install tasks and errors is placed in C:\ZSUPPORT\install\nse.inno.log.
Installing the Client Component 17
NOTE:
•
NonStop Software Essentials 5.0 (and later) is referred to as NonStop Software Essentials+ on the Start menu and in other GUI locations. These references are delineated as such to differentiate between NonStop Software Essentials 5.0 (and later) and previous HPE SIM plug-in versions of NonStop Software Essentials which are referred to as NonStop Software
Essentials, since they can co-exist.
•
NonStop Software Essentials installs to the C:/Program Files/HP/NonStop Software
Essentials folder. To install NonStop Software Essentials onto a non-default location, see
“Installing NonStop Software Essentials to a non-default location” (page 24)
for information.
•
Previously installed versions of NonStop Software Essentials stand-alone (5.0 and later) are replaced.
•
Previously installed versions of NonStop Software Essentials stand-alone (5.0 and later) do not need to be uninstalled before a new version of NonStop Software Essentials stand-alone
(5.1 and later) is installed.
•
If NonStop Software Essentials 5.1 and later is installed, NonStop Software Essentials 5.1
and later must be uninstalled before installing NonStop Software Essentials 5.0.
•
Any custom configuration done within the files in C:\Program Files\HP\NonStop
Software Essentials files are saved to C:\Program Files\HP\NonStop Software
Essentials (old)
, replacing any prior files in this folder.
•
Configuration changes in the site properties file in C:\ProgramData\HP\NonStop
Software Essentials\config\nonstop_software_essentials.properties
are preserved.
•
If C:\ProgramData\HP\NonStop Software Essentials\config\ nonstop_software_essentials_site.properties
does not exist, and C:\
ProgramData\HP\Systems Insight Manager\config\nse\ nonstop_software_essentials_site.properties
does, C:\ProgramData\HP\
Systems Insight Manager\config\nse\ nonstop_software_essentials_site.properties
is copied to C:\ProgramData\
HP\NonStop Software Essentials\config\ nonstop_software_essentials_site.properties
to preserve site customizations from a previous SIM-based NonStop Software Essentials installation.
•
NonStop Software Essentials stand-alone (5.0 and later) can run alongside NonStop Software
Essentials HPE SIM plug-in versions.
•
NonStop Software Essentials installs its own Jetty app server that is used exclusively by
NonStop Software Essentials. It also installs a Java version used exclusively by NonStop
Software Essentials.
•
By default, NonStop Software Essentials uses port 9987 for HTTP and 9988 for HTTPS.
Note that 9988 is the same port number used for the connection to the NonStop Software
Essentials server on NonStop server, which is a different connection:
◦
9988—Connection between Browser and NonStop Software Essentials client
◦
9988—Connection between NonStop Software Essentials client and server
Note that Port 9991 is also used on Windows systems by the NonStop Software Essentials server for shutdown requests or whenever you stop services. The use of this port number on Windows is different than its use on NonStop Software Essentials by the OSM event viewer.
18 Installing NonStop Software Essentials
More information
For more related installation information, see the NonStop Software Essentials Client softdoc
(T0895) or the readme file on the HPE Insight Control for NonStop DVD.
Securing NonStop Software Essentials (and Jetty App Server)
NonStop Software Essentials intentionally installs its own private Jetty app server used exclusively for NonStop Software Essentials. This provision allows for tighter security. Since NonStop Software
Essentials is often only used for software upgrades (which usually occur a limited number of times a year), the NonStop Software Essentials Jetty app server can be stopped if it is not in use. By default, the NonStop Software Essentials Jetty server is configured only to allow local access so that no threat of internet access to the NonStop Software Essentials client computer exists. The NonStop Software Essentials Jetty server can be configured only to allow local access and remote access from specific IP addresses to run the NonStop Software Essentials client application.
Starting and Stopping the NonStop Software Essentials Jetty App Server
To start and stop NonStop Software Essentials, run Control Panel\System and Security\
Administrative Tools\Services
. If the computer is rebooted or manually started (default), you can change the service configuration to be automatically started .
TIP:
In most cases, it is better to use the Automatic (Delayed Start) setting rather than the Automatic setting.
Allowing Remote Access
By default, the NonStop Software Essentials Jetty app server is secured for local access only.
To allow remote access, remove (or comment out) the following line in the C:/Program Files/
HP/NonStop Software Essentials/jetty/start.ini
file: jetty.host=localhost
Restricting Access
To restrict the NonStop Software Essentials Jetty app server to specific IP addresses, add allowed or disallowed IP addresses to the C:/Program Files/HP/NonStop Software Essentials/ jetty/etc/jetty-ipaccess.xml
file. (Refer to the documentation at http://eclipse.org/
jetty/documentation/current/ipaccess-handler.html for more information.) Also, un-comment the –-module=ipaccess line in C:/Program Files/HP/NonStop Software Essentials/ jetty/start.ini
.
Installing the Client Component 19
Example 1 Example of addresses allowed to the local host and IP addresses 1.2.3.4 and
5.6.7.8
• start.ini
:
### SSL Keystore Configuration
# define the port to use for secure redirection jetty.secure.port=9988
# ---------------------------------------
# Module: ipaccess
# Uncomment the --module=ipaccess line to enable restricting access to specific
# IP addresses via the jetty/etc/jetty-ipaccess.xml file.
# See http://www.eclipse.org/jetty/documentation/9.2.10.v20150310/ipaccess-handler.html
--module=ipaccess
## Setup a demonstration keystore and truststore jetty.keystore=etc/keystore jetty.truststore=etc/keystore
• jetty-ipaccess.xml
:
<Configure id="Server" class="org.eclipse.jetty.server.Server">
<Get id="oldhandler" name="handler"/>
<Set name="handler">
<New id="IPAccessHandler" class="org.eclipse.jetty.server.handler.IPAccessHandler">
<Set name="handler"><Ref refid="oldhandler"/></Set>
<Set name="white">
<Array type="String">
<Item>127.0.0.1</Item>
<Item>1.2.3.4</Item>
<Item>5.6.7.8</Item>
</Array>
</Set>
<Set name="black">
<Array type="String">
</Array>
</Set>
<Set name="whiteListByPath">false</Set>
</New>
</Set>
</Configure>
NOTE:
If jetty-ipaccess.xml is used with 127.0.0.1 added, it may appear that does not work. However, note that http://127.0.0.1:9987/nse works.
Configuring Client SSL/TSL
To configure SSL/TSL, see related Jetty documentation at http://www.eclipse.org/jetty/
documentation/current/configuring-ssl.html. Note that OpenJDK, which is installed at C:\
Program Files\HP\NonStop Software Essentials\j2re
, contains tools that can be used for configuring SSL/TSL.
20 Installing NonStop Software Essentials
6 Creating a NonStop Software Essentials client certificate
(using Oracle Java tools)
Creating a client certificate may be necessary when using NonStop Software Essentials, and
TLS 1.0 is disabled and TLS 1.1 and/or TLS 1.2 is enabled. To create a NonStop Software
Essentials client certificate:
1.
Go to C:\Program Files\HP\NonStop Software Essentials\jetty\etc, create a backup of the file keystore, and then delete the keystore file.
2.
To generate an SHA256 certificate, from the Windows command shell (cmd.exe), enter: keytool -genkey -keyalg RSA -alias jetty -keystore keystore -validity
1826 -keysize 2048
NOTE:
The Keytool utility is in the C:\Program Files\HP\NonStop Software
Essentials\j2re\jre\bin directory.
3.
When prompted to enter the keystore password, enter and take note of the password.
4.
When prompted to enter your name, organization, and other information, enter, as a minimum, the fully qualified host name of the server at the first and last name prompt, which is localhost
.
5.
When the system prompts you for the jetty key password, press enter to apply the same password as the keystore password.
This command creates a file, called keystore in C:\Program Files\HP\NonStop
Software Essentials\jetty\etc with all the information entered by the user.
6.
Generate an obfuscated password for the password: a.
Change to the C:\Program Files\HP\NonStop Software
Essentials\jetty\lib folder in a command shell.
b.
Enter: java -cp jetty-util-9.2.8.v20150217.jar
org.eclipse.jetty.util.security.Password <yourpassword>
Where <yourpassword> is the one provided in Step
c.
Copy the Line which starts with OBF:xxxx.
7.
Go to C:\Program Files\HP\NonStop Software Essentials\jetty and edit file start.ini
to change the value for the jetty.keymanager.password, jetty.keystore.password
and jetty.truststore.password keys to the OBF password generated in Step
NOTE:
In start.ini, ensure that the jetty.keymanager.password, jetty.keystore.password
, and jetty.truststore.password properties do not include the hash (#) symbol in front of them.
8.
Restart NonStop Software Essentials service.
9.
In Internet Explorer, go to the NonStop Software Essentials URL by reconfiguring IE to restrict TLS/SSL use to TLS 1.2 and, if desired, TLS 1.1..
Example:
C:\Users\Admin>cd :\Program Files\HP\NonStop Software Essentials\jetty\etc
C:\Program Files\HP\NonStop Software Essentials\jetty\etc>copy keystore keystore-old
1 file(s) copied.
C:\Program Files\HP\NonStop Software Essentials\jetty\etc>del keystore
21
C:\Program Files\HP\NonStop Software Essentials\jetty\etc>..\..\j2re\bin\keytool
-genkey -keyalg RSA -alias jetty -keystore keystore -validity 1826 -keysize 20
48
Enter keystore password:
Re-enter new password:
What is your first and last name?
[Unknown]: localhost
What is the name of your organizational unit?
[Unknown]:
What is the name of your organization?
[Unknown]:
What is the name of your City or Locality?
[Unknown]:
What is the name of your State or Province?
[Unknown]:
What is the two-letter country code for this unit?
[Unknown]:
Is CN=localhost, OU=Unknown, O=Unknown, L=Unknown, ST=Unknown, C=Unknown correct
?
[no]: yes
Enter key password for <jetty>
(RETURN if same as keystore password):
C:\Program Files\HP\NonStop Software Essentials\jetty\etc>cd ..\lib
C:\Program Files\HP\NonStop Software Essentials\jetty\lib>..\..\j2re\bin\java -c p jetty-util-9.2.8.v20150217.jar org.eclipse.jetty.util.security.Password <password>
2016-05-05 12:24:12.668:INFO::main: Logging initialized @255ms
<password>
OBF:1ci91lmn1jue1j8z1m0x1vn61vnw1lx91j631jrc1lj31ch9
MD5:64506f9dd1e18c60c0c5ef81f6d97f77
C:\Program Files\HP\NonStop Software Essentials\jetty\lib>
22 Creating a NonStop Software Essentials client certificate (using Oracle Java tools)
7 Creating a NonStop Software Essentials client certificate
(using OpenSSL tools)
To configure an HTTPS client certificate:
1.
Export the key/certificate pair in pkcs12 format.
For example, set your directory to the OpenSSL sslshare directory, and then run the following command to create a key and certificate pair to be imported into a Java Key Store: openssl pkcs12 -inkey file.pem -in cert.pem -export -out jetty.pkcs12
openSSL asks for a non-empty password for creating a pkcs12 format key-store
(Remember this information, as it is required later.)
2.
Create a keystore that can be used by NonStop Software Essentials, and then run the keytool command to import the above pkcs12 keystore into the keystore.
CD to the folder where the jetty.pkcs12 file is generated, from the Step
command: keytool -importkeystore -srckeystore jetty.pkcs12 -srcstoretype
PKCS12 –destkeystore keystore
Provide the password for the new keystore as storepwd when prompted for the storepwd password, and provide the source (pkcs12) keystore password designated in Step
when requested.
This action creates a keystore file.
3.
Stop the service NonStop Software Essentials from services.msc.
4.
Backup the keystore file in the C:\Program Files\HP\NonStop Software
Essentials\jetty\etc folder.
5.
Edit the start.ini file in the C:\Program Files\HP\NonStop Software
Essentials\jetty\ folder as follows: a.
If the jetty.keymanager.password, jetty.keystore.password or jetty.truststore.password
property has a # sign in front of it, remove it.
b.
Change the values of these three properties to
OBF:1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4
.
6.
Start NonStop Software Essentials service from services.msc.
7.
Access NonStop Software Essentials.
23
8 Installing NonStop Software Essentials to a non-default location
To install NonStop Software Essentials to another locations other than C:\Program Files:
1.
Install NonStop Software Essentials.
2.
Copy the NonStop Software Essentials folder from the C:\Program Files\HP directory to another directory of your choice (for example, C:\Temp).
3.
Uninstall NonStop Software Essentials from the Control Panel.
4.
Open the install-nse-service.bat file located, for example, in the C:\Temp\NonStop
Software Essentials\bin\ directory in a Text editor of your choice (for example,
Notepad
).
Replace all six occurrences of the text, C:\Program Files\HP\NonStop Software
Essentials with C:\Temp\NonStop Software Essentials.
5.
Save the file.
6.
Right-click install-nse-service.bat, which is located in C:\Temp\NonStop
Software Essentials\bin\
, and then select Run as Administrator.
7.
Open the services.msc program. The NonStop Software Essentials service is listed in the file.
8.
Right-click on the services.msc program, and select Properties.
9.
Change the Startup type to Automatic, and then click Apply.
10. Right-click on the service again, and then click Start to start the service. After approximately
15-20 minutes, you can access the NonStop Software Essentials link.
24 Installing NonStop Software Essentials to a non-default location
9 Configuring and Starting NonStop Software Essentials
Changing the Default Port to Something Other than Port 9988
The NonStop Software Essentials server and client components are initially configured to use port 9988 to communicate with each other. To change the default port, both the client and server component can be configured to use a different port number. In doing so, you must change the default port number in the NonStop Software Essentials server.
Change the Default Port Number in the NonStop Software Essentials Server
To create and edit an NSECONF file and change the default port:
1.
To create a new file (if it does not exist), copy the $SYSTEM.ZNSE.NSEEXMPL file NSECONF file.
2.
Edit the $SYSTEM.ZNSE.NSECONF file, and add the Port=<new-port-number> entry.
If needed, the NSECONF file should be created and/or edited before starting the NonStop Software
Essentials process (NSE-HTTP). If the process is already running, it must be stopped and restarted in order for the changes specified in the NSECONF file to take effect (see
NonStop Software Essentials Server Process” (page 26)
).
Change the Default Port Number in the NonStop Software Essentials Client
To change the default port, create and edit a C:\ProgramData\HP\NonStop Software
Essentials\config\nonstop_software_essentials_site.properties
file:
1.
If the nonstop_software_essentials_site.properties file does not exist, create it by copying the nonstop_software_essentials_site.example.properties file to the C:\ProgramData\HP\NonStop Software Essentials\config\ directory.
2.
Edit the nonstop_software_essentials_site.properties file, and add or change it to include the following statement, and then change the port number to match the port specified in the NSECONF server file.
For example: nonStop.session.port = 9988
3.
Restart the NonStop Software Essentials Windows service using the program, Control
Panel\All Control Panel Items\Administrative Tools\Services
.
Configuring TCP/IP for FAMILY and INET Settings
If you are configuring TCP/IP and using the FAMILY, note that you must also set it to INET. To check or change this setting:
•
Check FAMILY setting. For example:
SCF INFO PROVIDER $ZZCIP.ZTC0,DETAIL
•
Change FAMILY setting. For example:
SCF ALTER PROVIDER $ZZCIP.ZTC0, FAMILY INET
SCF START PROVIDER $ZZCIP.ZTC0
Configuring TCP/IP Stacks Outside of the Dedicated Maintenance LAN
(Conditional)
The NonStop Software Essentials server component is shipped out of the box so that it can be used with the NonStop Software Essentials client component that is running on the NonStop
System Console. The NonStop Software Essentials server component listens on the default maintenance LAN TCP/IP stacks ($ZTCP0 and $ZTCP1). If you want to use a CMS to run the
Changing the Default Port to Something Other than Port 9988 25
NonStop Software Essentials client component, you must create and edit an NSECONF file to have the NonStop Software Essentials server component listen on a different TCP/IP stack.
To create and edit an NSECONF file, and change the default stack:
1.
Copy the $SYSTEM.ZNSE.NSEEXMPL file in the NSECONF file.
2.
Edit the $SYSTEM.ZNSE.NSECONF file, and add the Stack=<Stack> entry. The Stack parameter should point to the TCP/IP process name associated with the IP address that is used for discovery in HPE SIM.
For example:
Stack=$ZTC0
Multiple stacks can be registered by specifying multiple entries for Stack, as follows:
Stack=$ZTC0
Stack=$ZTC1
3.
Add the following in the $SYSTEM.ZNSE.NSECONF file if you do not want the NonStop
Software Essentials client running on the NonStop System Console to communicate with the NonStop Software Essentials server component:
Ignore_Default_Stacks=On
When needed, the NSECONF file should be created and/or edited before starting the NonStop
Software Essentials process (NSE-HTTP). If the process is already running, it must be stopped and restarted for the changes specified in the NSECONF file to take effect (see
NonStop Software Essentials Server Process” (page 26)
).
NOTE:
When configuring an additional TCP/IP stack, you must also add that stack to the
OSMCONF file for the NonStop system (see
“Configuring OSM (Conditional)” (page 27) ).
Using a Different Protocol File than $SYSTEM.ZTCPIP.PROTOCOL
NonStop Software Essentials uses the $SYSTEM.ZTCPIP.PROCOTOL file internally. If you are using a different protocol file or if the protocol file is in a different location, follow these steps to ensure that NonStop Software Essentials uses your specific protocol file:
1.
Abort the NonStop Software Essentials process:
SCF ABORT PROCESS $ZZKRN.NSE-HTTP
2.
Define the protocol file that you want the NonStop Software Essentials generic process to use:
SCF ADD PROCESS $ZZKRN.#NSE-HTTP , &
( DEFINE =TCPIP^PROTOCOL^FILE, CLASS MAP, FILE &
<location of the PROTOCOL file>)
For example:
SCF ADD PROCESS $ZZKRN.#NSE-HTTP , &
( DEFINE =TCPIP^PROTOCOL^FILE, CLASS MAP, FILE &
$SYSTEM.MYSUBVOL.PROTOCOL)
3.
Start the NonStop Software Essentials process:
SCF START PROCESS $ZZKRN.NSE-HTTP
Starting the NonStop Software Essentials Server Process
If a system load was not done after the initial NonStop Software Essentials installation, start the
NonStop Software Essentials process on the NonStop server that is to be used as host, by entering:
SCF START PROCESS $ZZKRN.NSE-HTTP
26 Configuring and Starting NonStop Software Essentials
NOTE:
If a prior version of NonStop Software Essentials was already installed or if you must restart the NonStop Software Essentials process in order for changes made to the NSECONF file to take effect, you must abort and then start the process by entering:
SCF ABORT PROCESS $ZZKRN.NSE-HTTP
SCF START PROCESS $ZZKRN.NSE-HTTP
Adding the NonStop Software Essentials-HTTP Server Process
(Conditional)
If the NonStop Software Essentials-HTTP server process was not added during installation or was somehow deleted, configure it:
ADD PROCESS $ZZKRN.#NSE-HTTP, &
AUTORESTART 10, &
CPU FIRSTOF (2,3,4,5,6,7,8,9,10,11,12,13,14,15,0,1),&
DEFAULTVOL $SYSTEM.ZNSE,
HIGHPIN ON,
HOMETERM $ZHOME,
NAME $ZZNSE,
&
&
&
&
PRIORITY 150,
PROGRAM $SYSTEM.ZNSE.HTTPSRVR,
INFILE $ZHOME,
OUTFILE $ZHOME,
STARTMODE APPLICATION,
STARTUPMSG “cpu-list < cpu-list>”,
USERID SUPER.SUPER
&
&
&
&
&
&
START PROCESS $ZZKRN.#NSE-HTTP
Configuring OSM (Conditional)
Depending on the NonStop Software Essentials hardware and LAN configuration, you may need to add one or both of the following parameters to your OSMCONF file for the host NonStop server:
•
SSL (secure sockets layer) must be enabled for OSM. It is enabled by default for NonStop
BladeSystems, NonStop X systems, and any NS-series systems that use OSM T0682 H02
ADD and later. For other NonStop servers, enable SSL by adding the following parameter to your OSMCONF file:
UseSSL = On
•
If the TCP/IP stack to be used for communication with the Windows-based running NonStop
Software Essentials is outside of the dedicated maintenance LAN, you must specify stack parameters in your OSMCONF file by entering: stack = <TCPIP process name>
For example: stack = $ZTC00 stack = $ZTC01
For information on creating an OSMCONF file, see the OSM Migration and Configuration Guide.
After changing your OSMCONF file, you must restart the OSM server ($ZCMOM), if it is running, for the changes to take effect.
Adding the NonStop Software Essentials-HTTP Server Process (Conditional) 27
Launching NonStop Software Essentials
The following list of URLs shows many examples of how NonStop Software Essentials may be started from an Internet Explorer window on the system where NonStop Software Essentials is installed:
•
http://localhost:9987/nse
•
https://localhost:9988/nse
•
http://localhost:9987/nse?address=nonStop.server.dns.name&name=\SCUBA
•
http://localhost:9987/nse?address=11.22.33.44&name=\SCUBA
•
http://localhost:9987/nse?address=nonStop.server.dns.name&name=\SCUBA& port=9988
•
http://localhost:9987/nse?address=nonStop.server.dns.name&n=\SCUBA& user=JOHN.DOE
•
http://localhost:9987/nse?address=nonStop.server.dns.name&n=\SCUBA& user=JOHN.DOES
In the simplest form with no parameters, the NonStop Software Essentials Launch Page is displayed. If one or more parameters are specified, the Logon screen is displayed. The following lists and describes some of these parameters.
Example 2 Description of parameters that can be used in the URL
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
/*
* NSE Decouple: Now that NSE has been decoupled from HP SIM, customers will
* be able to enter the NSE URL directly into the browser to launch NSE.
So,
* we want the arguments to be simple, optional, and even have abbreviations.
* Abbreviations will be the minimum number of characters to uniquely identify
* the parameter from all other parameters.
*
* The parameters are: (names and abbreviation are not case sensitive)
* Abbr
Name evia Requ tion ired Value Description
------- ------------------------------------------------------------------------address a no 11.22.33.44
This is the network address (IP or DNS) of the NonStop nonStop.
server.dns.
name system NSE is to connect with. If this value is not specified and none of the other parameters are specified then the Select NonStop Server page is displayed.
If this parameter is not specified and any of the other parameters are specified then an IllegalArgumentException is thrown with the message "address parameter is missing and required.
Value is the IP or DNS name of the NonStop system to connect to.", which will be displayed in the browser.
If both "address" and "a" parameters exist,
"address" is used.
port name user p n u no no no
9571
\SCUBA
GROUP.MIKE
SUPER.SUPER
This is the port to connect to the "address" on.
used.
The name of the nonstop system.
The user ID to place in the User ID field on the NSE logon page.
If this value is not present the User ID field on the NSE logon page will be empty.
If both "user" and "u" parameters exist, "user" is used.
If this value is not present the address will be used as the name.
If both
"name" and "n" parameters exist, "name" is used.
If this value is not specified the default port of 9988 will be
If both "port" and "p" are specified, "port" is used.
type t no manage package p
Session type.
value is not present, "manage" is the default.
If both
"type" and "t" parameters exist, "type" is used.
If the value is not "manage", "package" or "p" an error is displayed.
This is "manage" for NSE Manage Software and "package" or "p" for NSE Package Software.
If this
Each time NonStop Software Essentials is launched, the customer must log on with a valid user
ID (Guardian user name or Safeguard alias) and password for the chosen NonStop server.
Whenever a NonStop Software Essentials window is closed, the user is logged out of NonStop
Software Essentials. Multiple NonStop Software Essentials windows can be opened (for the
28 Configuring and Starting NonStop Software Essentials
same or different NonStop servers) and used independently. Thus, if a user opens another
NonStop Software Essentials window for the same NonStop server, they must log on again in that window.
For Information on Using NonStop Software Essentials
After logging on to NonStop Software Essentials, you can access the online help that is specific to NonStop Software Essentials from the Help menu or by clicking Help from any NonStop
Software Essentials page.
Launching NonStop Software Essentials 29
10 Using NonStop Software Essentials as a Replacement for the Planner Interface
NonStop Software Essentials and the DSM/SCM Planner Interface have several similarities and differences (see
“Overview of the Similarities and Differences between NonStop Software
Essentials and the DSM/SCM Planner Interface” (page 30) ). It also presents a side-by-side
comparison of how to use NonStop Software Essentials instead of the Planner Interface for the typical progression of activities involved in:
•
“Establishing or Reinitializing a New Host System” (page 34)
•
“Establishing or Reinitializing a New Target System” (page 35)
NOTE:
The DSM/SCM Planner Interface is not supported on 64-bit system consoles (which includes NonStop system consoles running Windows 2008 Server), with J06.19 or later, or on
L15.02 or later. The NonStop Software Essentials interface must be used in place of the DSM/SCM
Planner Interface in those cases.
Overview of the Similarities and Differences between NonStop Software
Essentials and the DSM/SCM Planner Interface
NonStop Software Essentials provides the same, or in many cases, more user-friendly functionality than the DSM/SCM Planner Interface.
30 Using NonStop Software Essentials as a Replacement for the Planner Interface
Figure 1 NonStop Software Essentials Home page
•
Graphical user interface:
◦
The Planner Interface displays fixed views of the Software Archive and Configuration
Revisions (they are always present whether used or not), and some menu items are dependent on the window or row selected.
The Planner Interface features many pop-up dialogs for inputting information, launched by buttons in the main windows.
◦
The Planner Interface shows non-grouped Software Inputs below the Groups in the pane Software in Archive.
In NonStop Software Essentials, this functionality is provided by the Ungrouped Packages node in the Navigation Tree in the left pane and the Ungrouped Packages page. The node is a child of the Software in Archive node in the tree.
◦
NonStop Software Essentials (see
) allows you to select what is displayed in the . The Host Tree is always displayed in the left-hand pane for easy access to the Configuration Revisions pages and Software in Archive views, which are available by expanding those headings in the Host Tree. Likewise, the NonStop
Software Essentials menu bar always appears above the , for easy access to all NonStop
Software Essentials menu options.
shows the NonStop Software
Essentials Home page. Selecting a menu option or clicking a link on the Host Tree or on the of the Home page causes the selected page to be displayed in the . You can always get back to the Home page by clicking Home on the right side of the NonStop
Software Essentials Banner.
To avoid excessive pop-up windows, NonStop Software Essentials often presents multiple tabs within a single window instead.
To make finding and organizing data easier, many of the data tables displayed within
NonStop Software Essentials pages can be sorted by clicking the column headings.
•
Functionality mapping –
maps Planner Interface menu options (or buttons) to the functional equivalent in NonStop Software Essentials.
Overview of the Similarities and Differences between NonStop Software Essentials and the DSM/SCM Planner Interface 31
Table 2 Planner Interface and NonStop Software Essentials menu options (or buttons)
Planner Interface Menu Option (or button)
Maintain > Configuration Manager
Maintain > Security Maintenance > Planner List
Maintain > Security Maintenance > DB administrator list
Maintain > Volume Maintenance
Requests > Requests List
Requests > Receive Snapshot
Requests > Receive Software
Requests > Prepare Report
File > View Prepared Documents
Tandem > Support Info > Server Trace
Show Products by Group (button)
File > Show Revision History
Maintain > System Maintenance menu item
Maintain > Target Maintenance menu items
NonStop Software Essentials Menu Option or
Equivalent
Maintenance > Host Configuration
Maintenance > Manage Planners
Maintenance > Manage Host Administrators
Maintenance > Manage Volume Usage
Requests > Show Requests
Requests > Receive Snapshot
Requests > Software Installation > Receive Software
Reports > Manage Reports
Reports > View Prepared Reports
Options > Server Tracing
Options > Show Products in Groups
Comparable to loading the work panel with the Target page
Target Maintenance buttons on the Configuration
Revisions page
Target Maintenance buttons on the Configuration
Revisions page
•
Other miscellaneous changes/improvements in NonStop Software Essentials:
◦
Users with roles, other than planners, can log on to NonStop Software Essentials, and view DSM/SCM information through NonStop Software Essentials.
◦
Request names are more descriptive.
◦
The Request Status functionality monitors requests across both host and target activities, and cancel and restart actions are easier.
◦
The Planner Interface uses less useful Private Product Groups as default; NonStop
Software Essentials supports only Shared Product Groups.
◦
Mixed (upper/lower) case support for Package, Package Group, Planner Group, and
Product Group names (names are not allowed to differ only in case).
◦
Receive Software has better pattern matching support for searches, and also differs in that only selected DSVs are received into the archive.
◦
Difference in how a composite product is displayed:
The DSM/SCM Planner Interface shows a composite product version on a single row in a table, showing update SPRs in the T6031H02 ()+AAA+AAB+AAC format.
NonStop Software Essentials shows the same composite product version on a single row that can be expanded to show the individual Update SPRs in their own rows. The main benefit of this NonStop Software Essentials feature is that an individual SPR, such as AAC, can be deleted from the new revision directly. To delete just AAC in the
DSM/SCM Planner Interface, the entire product would have to be removed, then
T6031H02 (), AAA, and AAB added back.
32 Using NonStop Software Essentials as a Replacement for the Planner Interface
◦
Difference in copying a SUT to create a new Revision:
In the DSM/SCM Planner Interface, to copy a SUT/Revision and establish it as the new base, you must perform the copy without opening/displaying the individual product versions within that SUT/Revision. After you open a SUT/Revision to display the product versions, select all the individual products and perform a copy, that copy does not establish the SUT/Revision as a new base. Copying in that manner copies the individual product versions in an additive manner and does not set the revision RVU level.
Likewise, NonStop Software Essentials provides both copy options, additive as well as copying an entire SUT, to establish a new base revision. The added benefit in NonStop
Software Essentials is that you can open a SUT to view all product versions and still select and copy the entire SUT to create a new base revision. If you select only a subset of the products in a SUT, that constitutes an additive copy and does not establish a new base revision.
◦
NonStop Software Essentials saves the revision notes along with the revision after Save is pressed from the New Revision page.
◦
Differences in how new revisions are identified:
The DSM/SCM Planner Interface indicates that a new revision exists in the left column of the Configuration Revisions window (see
the new revision with which the current user is a member. An asterisk (*) indicates that the current user owns revision, and the revision is new. An ampersand (@) symbol indicates that the revision is new and not owned by the current user but by another member of the same planner group. If the planner group (in which the current user is a member) does not own the new revision, the left column is blank. The user cannot tell that a new revision exists until they try to create one and get an error message.
Figure 2 The DSM/SCM Planner Interface indicating that a new revision exists
The Configuration Revisions page of NonStop Software Essentials (see
) always displays a new revision—identified as “New” in the
Applied column—regardless of ownership, as well as an incremented revision number for the new revision in the Revision column. The Applied column also displays an icon to indicate when someone other than the current user owns a revision. The icon in the top row (for the RGJ Logical Target on system \BAKER) indicates that someone not in the same planner group as the current user owns the new revision. The icon in the next row (for the “DEFAULT” Logical Target on system \SCUBA) indicates that someone in the same planner group as the current user owns the new revision. The absence of an icon in the row below indicates that the current user owns the new revision for the
DEFAULT2 Logical Target on system \SCUBA).
Overview of the Similarities and Differences between NonStop Software Essentials and the DSM/SCM Planner Interface 33
Figure 3 Configuration Revisions page
◦
Difference in how an uninitialized state is displayed—The uninitialized state of a target is confusing as multiple new revisions can all be assigned a revision number of 1. Only after the targets are initialized can the new revisions assigned incremental revision numbers. The DSM/SCM Planner Interface does not show all the individual revision 1 revisions in the revision history table. With NonStop Software Essentials, you can see complete revision history.
◦
Differences in the build/apply process—NonStop Software Essentials provides more status and control of the build/apply activities by monitoring both the host and target sides; the Planner Interface only has access to information on the host side.
NOTE:
Whether using NonStop Software Essentials or the DSM/SCM Planner
Interface, the Target Interface is required for manual build/apply operations when the target is not Expand-connected to the host.
◦
Differences in report functionality—NonStop Software Essentials provides enhanced software audit. Auditors require reports to verify that the software installed on the servers is what was intended to be installed. The Software Audit Report feature provides a simpler method of gathering such data.
◦
Softdocs cannot be viewed from within NonStop Software Essentials; they can be viewed through Scout.
Establishing or Reinitializing a New Host System
The process flow between NonStop Software Essentials and the DSM/SCM Planner Interface for establishing or reinitializing a new host system vary.
Using DSM/SCM Planner Interface
1.
After running INITENV on the system, in either order:
•
Use the Target Maintenance Interface (ZPHITMI) to define an operator and provide values for System Maintenance and Volume Maintenance.
•
Use the Host Maintenance Interface (ZPHIHMI) to define a planner and provide values for System Maintenance and Volume Maintenance. The Planner Interface cannot be run until a planner is added.
34 Using NonStop Software Essentials as a Replacement for the Planner Interface
2.
Use the Planner Interface to:
•
Define the values for the Configuration Manager Profile.
•
Define the values for the archive and scratch volumes under Volume Maintenance.
•
Modify the Logical Target values under Target Maintenance.
•
Receive Software into the archive to be installed on the target.
•
Create new revision 1 for the target.
•
Build/Apply the revision and initialize the target. After files are placed, activate the new revision.
Using NonStop Software Essentials
1.
After running INITENV on the system, use the Target Maintenance Interface (ZPHITMI) to define an Operator and provide values for System Maintenance and Volume Maintenance.
When defining an Operator, decide if the Request an Audit permission should be enabled; you must submit a Software Audit request in NonStop Software Essentials.
2.
Log on to NonStop Software Essentials as the Host Administrator and owner of the DSM/SCM database (as defined during INITENV). Add the same user as a planner using the Manage
Planners link on the NonStop Software Essentials Home page (planner permissions are updated immediately without logging in again); then:
•
Define the values for the Host Configuration (same as defining values for the
Configuration Manager Profile in the DSM/SCM PI).
•
Define the values for the archive and scratch volumes using the Manage Volume Usage link on the NonStop Software Essentials Home page.
•
Modify both the Physical and Logical Target values under the Target Maintenance heading on the Configuration Revisions page. A single pop-up dialog is used to define both Physical and Logical Target values.
•
Receive Software into the archive to be installed on the target.
•
Create new Revision 1 for the target.
•
Build/Apply the revision and initialize the target. After files are placed, activate the new revision.
Establishing or Reinitializing a New Target System
The process flow between using NonStop Software Essentials and the DSM/SCM Planner
Interface to establish or reinitialize a new target system are different.
Using DSM/SCM Planner Interface
1.
After running INITENV on the target system, use the Target Maintenance Interface (ZPHITMI) to configure system attributes on the target side of DSM/SCM, define an Operator, and specify a scratch volume.
2.
Use the Planner Interface to add a new Physical and Logical Target on the host side. This action requires two separate operations, first using the System Maintenance menu, and then the Target Maintenance menu.
3.
Use the Planner Interface to:
•
Receive Software into the archive to be installed on the target.
•
Create new Revision 1 for the target.
•
Build/Apply the revision and initialize the target. After files are placed, activate the new revision.
Establishing or Reinitializing a New Target System 35
Using NonStop Software Essentials
1.
After running INITENV on the target system, use the Target Maintenance Interface (ZPHITMI) to configure system attributes on the target side of DSM/SCM, define an Operator, and specify a scratch volume.
When defining an Operator, decide if the Request an Audit permission should be enabled; you must submit a Software Audit request in NonStop Software Essentials.
2.
Use NonStop Software Essentials to add a new Physical and Logical Target in a single operation, using the Configuration Revisions link on the NonStop Software Essentials
Home page.
From the Configuration Revisions page, modify both the Physical and Logical Target values by clicking Modify under the Target Maintenance heading. A single pop-up dialog is used to define both Physical and Logical Target values.
3.
Use NonStop Software Essentials to:
•
Receive Software into the archive to be installed on the target.
•
Create new Revision 1 for the target.
•
Build/Apply the revision and initialize the target. After files are placed, activate the new revision.
36 Using NonStop Software Essentials as a Replacement for the Planner Interface
11 Support and other resources
Accessing Hewlett Packard Enterprise Support
•
For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website:
www.hpe.com/assistance
•
To access documentation and support services, go to the HP Support Center – Hewlett
Packard Enterprise website:
www.hpe.com/support/hpesc
Information to collect
•
Technical support registration number (if applicable)
•
Product name, model or version, and serial number
•
Operating system name and version
•
Firmware version
•
Error messages
•
Product-specific reports and logs
•
Add-on products or components
•
Third-party products or components
Accessing updates
•
Some software products provide a mechanism for accessing software updates through the product interface. Review your product documentation to identify the recommended software update method.
•
To download product updates, go to either of the following:
◦
HP Support Center – Hewlett Packard Enterprise Get connected with updates from
HP page:
www.hpe.com/support/e-updates
◦
Software Depot website:
www.hpe.com/support/softwaredepot
•
To view and update your entitlements, and to link your contracts, Care Packs, and warranties with your profile, go to the HP Support Center – Hewlett Packard Enterprise More Information
on Access to HP Support Materials page:
www.hpe.com/support/AccessToSupportMaterials
IMPORTANT:
Access to some updates might require product entitlement when accessed through the HP Support Center – Hewlett Packard Enterprise. You must have a Hewlett
Packard Enterprise Passport set up with relevant entitlements.
Accessing Hewlett Packard Enterprise Support 37
Websites
Website
Hewlett Packard Enterprise Information Library
HP Support Center – Hewlett Packard Enterprise
Contact Hewlett Packard Enterprise Worldwide
Subscription Service/Support Alerts
Software Depot
Customer Self Repair
Link www.hpe.com/info/enterprise/docs www.hpe.com/support/hpesc www.hpe.com/assistance www.hpe.com/support/e-updates www.hpe.com/support/softwaredepot www.hpe.com/support/selfrepair
Insight Remote Support
Serviceguard Solutions for HP-UX
www.hpe.com/info/insightremotesupport/docs www.hpe.com/info/hpux-serviceguard-docs
Single Point of Connectivity Knowledge (SPOCK) Storage compatibility matrix
www.hpe.com/storage/spock
Storage white papers and analyst reports
www.hpe.com/storage/whitepapers
Customer self repair
Hewlett Packard Enterprise customer self repair (CSR) programs allow you to repair your product.
If a CSR part needs to be replaced, it will be shipped directly to you so that you can install it at your convenience. Some parts do not qualify for CSR. Your Hewlett Packard Enterprise authorized service provider will determine whether a repair can be accomplished by CSR.
For more information about CSR, contact your local service provider or go to the CSR website:
www.hpe.com/support/selfrepair
Remote support
Remote support is available with supported devices as part of your warranty, Care Pack Service, or contractual support agreement. It provides intelligent event diagnosis, and automatic, secure submission of hardware event notifications to Hewlett Packard Enterprise, which will initiate a fast and accurate resolution based on your product’s service level. Hewlett Packard Enterprise strongly recommends that you register your device for remote support.
For more information and device support details, go to the following website:
www.hpe.com/info/insightremotesupport/docs
Documentation feedback
Hewlett Packard Enterprise is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation
Feedback ([email protected]). When submitting your feedback, include the document title, part number, edition, and publication date located on the front cover of the document. For online help content, include the product name, product version, help edition, and publication date located on the legal notices page.
38 Support and other resources
Index
Symbols
A
accessing
B
C
contacting Hewlett Packard Enterprise, 37
D
documentation
DSM/SCM
DSM/SCM Planner Interface, comparison to, 30
E
Expand, required for DSM/SCM, 11
H
host system, establishing or reinitializing, 34
I
installing client and server components, 14
installing client component
M
migrating from DSM/SCM Planner Interface, 9
N
NonStop Software Essentials
comparison to Planner Interface, 30
O
online help for NonStop Software Essentials, 29
P
Pathway, required for DSM/SCM, 12
Q
R
requirements
S
server component, installing, 14
SQL/MP, required for DSM/SCM, 11
SSL, enabling, 27 stack parameters for OSM, 27
starting NonStop Software Essentials process, 26
support
Hewlett Packard Enterprise, 37
SWID, required for DSM/SCM, 12
T
target system, establishing or reinitializing, 35
TCP/IP stacks
U
updates
upgrading from NonStop Software Essentials 1.0, 9
using NonStop Software Essentials, 29
V
VMWare, supported versions, 11
W
websites, 38 customer self repair, 38
39
Pobierz
Publiczny link zaktualizowany
Publiczny link do Twojego czatu został zaktualizowany. You may view and manage your chat links after registration here.
Publiczny link do dokumentu
Reklama