This document contains the following topics:
Platform | Hardware and Software Minimum Requirements |
---|---|
Red Hat Linux Advanced Server 2.1 |
|
You can refer to the Install Guide for information on prerequisites and installation requirements. The installation process does not enforce all the prerequisites. One of the prerequisites which is not enforced is the disk space requirement.
The following browsers are supported with NNM 7.0. For an updated list of browser support, visit http://ovweb.external.hp.com/nnm/NNM7.0/relNoteUpd/relNoteUpdate.htm.
For additional limitations on browsers running in non-English locales, see Supported Non-English Locale Configurations.
Client Operating System | Supported Browsers | Where to Download |
---|---|---|
HP-UX 11.11 HP-UX 11.0 |
Netscape Navigator 7.0 Mozilla 1.4 note: Mozilla 1.4 incorrectly reports userAgent as Windows instead of HP-UX, so if you have no JPI, you'll get redirected to the wrong site to download the plug-in. Instead, follow the link below to get the HP-UX plug-in |
http://www.hp.com/workstations/risc/standard/software/netscape/netscape.html http://www.hp.com/products1/unix/java/mozilla/index.html |
Solaris 9 Solaris 8 |
Netscape Navigator 7.0 Mozilla 1.2.1 |
http://www.sun.com/solaris/netscape/ http://wwws.sun.com/software/solaris/browser/index.html |
Windows XP Windows 2000 |
Internet Explorer 6.0 Netscape Navigator 7.0 Mozilla 1.4 |
http://www.microsoft.com/windows/ie/default.htm http://home.netscape.com/download/ http://www.mozilla.org |
Red Hat Linux Advanced Server 2.1 | Mozilla 1.4 and Netscape 7.1 | http://www.mozilla.org http://home.netscape.com/download/ |
The gcc3-3.0.4-1 package must be installed as part of the operating system.
For information about the Java Plug-in, browse to http://java.sun.com/products/plugin/index.html.
Server Operating System | Supported Java Plug-in | Where to Download |
---|---|---|
HP-UX 11.11 HP-UX 11.0 |
JPI 1.4.1.03 | http://www.hp.com/go/java |
Solaris 9 Solaris 8 |
The JPI is automatically installed with supported browsers. Netscape 7.0 automatically installs JPI 1.4.1. Mozilla automatically installs JPI 1.4.2 |
http://java.sun.com/j2se/1.4.2/download.html |
Windows XP Windows 2000 |
JPI 1.4.2_01 | http://java.sun.com/j2se/1.4.2/download.html |
Red Hat Linux Advanced Server 2.1 | JPI 1.4.2_01 | http://java.sun.com/j2se/1.4.2/download.html |
Dynamic Views require the Java Plug-in (JPI). When you view one of the Dynamic Views, you will be prompted with a dialog such as
This page contains information of a type (application/x-java-applet;jpi-version=1.4) that can only be viewed with the appropriate Plug-in.
Click OK to download Plugin.
Installing the Java Plug-in
You must have installed gcc3-3.0.4-1 on your machine.
Source: http://plugindoc.mozdev.org/linux.html#Java [Then press HOWTO: Installing Java Plug-in(linux)].
Note: If you copy the file instead of making the symlink, Java will crash.
If you are not familiar with symbolic linking and permissions, complete one of the following steps:
Note: To check which compiler was used to build Mozilla, see about:buildconfig (Mozilla 1.4a or later).
For the Netscape Installation with Java Plug-ins, follow the same procedure mentioned above but replace the mozilla directory with netscape in all the cases.
Signed Applet:Non-English Users Note:
When you first download the JPI, at the "Select Java(TM) Plugin
Installation..." dialog, be sure to set your Locale to
"International". Otherwise, your Internet Explorer browser will
disappear every time you load a Dynamic View.
NNM currently only supports Apache on Linux
If you are using the embedded database that is installed with Network Node Manager, you have no additional requirements. If you want to run an enterprise database, the following external databases are supported:
Operating System | Supported Databases |
---|---|
Red Hat Linux Advanced Server 2.1 |
Oracle 9.2.0.3 Oracle 8.1.7 |
The listener.ora and tnsnames.ora files can be located at $ORACLE_HOME/network/admin.
For Oracle, the following products are required to run together with NNM.
HP only supports 32-bit Oracle on HP-UX and Solaris.
A single installation of Network Node Manager can support multiple locales. NNM 7.0 is internationalized. Follow your system's instructions to set the locale appropriately. Other languages can be set to get locale specific values such as dates, sorting/collation, character handling, and currency. Various parts of Network Node Manager force LC_NUMERIC to be C to enforce consistent use of ',' instead of '.' for numbers.
Use ovchange_locale_mapping on the NNM server to ensure that the NNM and browser codesets match.
(Unix only) Be sure that the ovspmd process (started upon bootup via /etc/init) has the correct locale set, or the web-based alarm browser will not have localized categories. This happens if ovalarmsrv is running with LANG=C in its environment. The environment is set at the time ovstart is first run, usually at the operating system startup, and is passed to its child processes, such as ovalarmsrv. Running 'ovstop ovalarmsrv; ovstart ovalarmsrv' will not change the parent's environment. Often the operating system has the default language of "C" when it first starts, so this environment is passed indirectly to ovalarmsrv. To work around this problem, set the correct language variable (such as 'export LANG=ja_JP.eucjp') into the /sbin/init.d/ov500 file. Or after every re-boot, run ovstop;ovstart with the correct $LANG in the environment.
To set locale for Mozilla, complete the following steps:
NNM supports web browsers configured for various different languages. The following is an example of how to configure these languages.
A Japanese web browser pointed at a system which supports multi-locales will display Japanese characters, while an English web browser will display English when pointed at the same system. This requires that the Japanese locale be installed on the server for Unix systems. With Internet Explorer browser you can adjust your locale by selecting Tools:Internet Options and clicking the Languages... button. To view Japanese, select Add... and make "Japanese [ja]" the first item in the list. Note that an input method must also be selected, and it must be configured via the Regional Settings of the Windows Control Panel.
If you get a message like:
Cannot set locale LC_ALL to [system default]. Be sure the locale is set on the machine (check the "Language settings for the system" in Control Panel's Regional Options)
it is likely that you need to set the Control Panel's Regional Options "Your locale (location):" field to Japanese. Windows 2000: If this field is not available, you need to check it in the "Language settings for the system" section.
Be sure to set the Fonts correctly, so you can display Japanese fonts. Do this from Internet Explorer by picking "Tools:Internet Options", General tab, pick "Fonts...", and change "Language script:" to "Japanese". For English systems this should be set to "Latin based".
On Windows, if the English version of the Java Plug-in (JPI) is installed instead of the International version, the Dynamic Views will cause Internet Explorer to immediately disappear without a message.
This is currently not tested.
NNM is currently tested against Gnome and KDE desktop environments.