Installation Prerequisites
This section includes the following topics:
Introduction
In order to successfully install the Oracle Utilities Network Management System (and underlying environment), you must have a thorough understanding of the following:
• Unix system administration.
• Oracle RDBMS installation and configuration.
• WebLogic installation and EJB deployment.
In addition, you should have at least a cursory knowledge of the Oracle Utilities Network Management System architecture and applications functionality.
The Oracle Utilities Network Management System Quick Install Guide provides an overview of the Oracle Utilities Network Management System architecture and lists the supported hardware and software configurations. Verify that your system meets system requirements prior to attempting the Oracle Utilities Network Management System installation.
Requirements for Oracle Utilities Network Management System Database
The Oracle RDBMS must be installed and configured before beginning the Oracle Utilities Network Management System. It must be installed on a server that is accessible from the Oracle Utilities Network Management System services applications. Time zone settings for the Oracle RDBMS and Oracle Utilities Network Management System services application must both be UTC. That is, on both the services machine and the database server, the TZ environment variable must be "UTC", and the database TIMEZONE value must be '+00:00'. These database and WebLogic instances should not be shared with any NMS installations running earlier versions of the code that did not yet support the UTC time zone.
Oracle recommends that any new installations should use the AL32UTF8 character set.
Refer to the “Database Configuration” chapter of the Oracle Utilities Network Management System Configuration Guide for more details regarding the installation and configuration of the Oracle RDBMS for use with the Oracle Utilities Network Management System applications.
Note: Oracle Locator, a standard component of all editions of Oracle RDBMS, is required for the Oracle Utilities Network Management System installation.
To verify that Oracle Locator has not been removed from your Oracle RDBMS, run the following SQL command:
select count(1) "Rows" from mdsys.cs_srs;
If this query returns zero or very few rows (1000+ are expected), consult your DBA to (re)install the Oracle Locator package.
Requirements for Oracle Database Client Installation
The Oracle Utilities Network Management System requires that an installation of the Oracle Database Client software be made available in order to facilitate connections between the NMS services and the database. The installation must be the full installation of the Oracle Database Client software. The Instant Client package will not work, as it does not have all of the required libraries and binaries required by the NMS services.
Requirements for Java Application Server
The Oracle Utilities Network Management System requires the installation of a WebLogic Application Server. This installation should be done before installing the Oracle Utilities Network Management System software. Refer to Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server for instructions.
Requirements for Spatial Landbase
The Oracle Utilities Network Management System recommends installation of the Oracle Map Builder to simplify the process of creating and managing map, theme, and symbology metadata in the spatial database used to render spatial landbase maps. Oracle Map Builder is part of the Oracle Fusion Middleware MapViewer family of products, which is available for download from the Oracle Technology Network website (www.oracle.com/technetwork/).
Requirements for Web Maps Landbase
The Oracle Utilities Network Management System supports the use of commercial web map servers for Viewer background landbases. It is up to each NMS customer to license with a web map provider for access to a web map service. NMS currently supports the following web map services:
• Google Static Maps Basic or Trial - To configure, you will need to agree to a license agreement with Google and they will provide you with an API key. This option is not recommended for production.
• Google Static Maps for Work/Business - To configure, you will need to agree to a license agreement with Google and they will provide you with a process to define Client IDs and Google generated Crypto Keys.
• Bing Maps - To configure, you will need to agree to a license agreement with Bing/Microsoft and they will provide you with a key.
Software Requirements for Unzipping Files
The Oracle Utilities Network Management System and third party software files are compressed in the ZIP format. Most Linux/Unix-based platforms already have the binaries needed to unzip the distribution archives. An unzip utility is also included in the Oracle client under $ORACLE_HOME/bin.
Security Considerations
Please refer to the Oracle Utilities Network Management System Security Guide for security overview, recommendations, and guidelines when installing Oracle Utilities Network Management System software.
OpenSSL
Oracle Utilities Network Management System now uses OpenSSL to encrypt traffic between SwService (used in CVR and FLISR) and WebLogic server by default. As such, OpenSSL is now required to be installed with the operating system if you will be running SwService. The openssl binary as well as libssl and libcrypto are required.
To make them available, you will need to install the appropriate OS packages on your system:
• Linux: openssl and openssl-devel RPM’s
• Solaris: library/security/openssl package
Isis Directory and NTP Daemon
Isis is the backbone of the Oracle Utilities Network Management System. It is the messaging bus through which all back-end NMS service components communicate.
On any computer using Isis it is important to have an accurate clock, which moves monotonically forward. Many approaches, such as rdate, can cause the clock to jump unpredictably, possibly backwards. This jumping is especially deleterious to Isis timing and timer queues, but can easily be avoided by using the Network Time Protocol (NTP) daemon, which is designed to gracefully synchronize the system clock with any reliable time source.
NTP is available for free on all operating systems and is simple to configure. Even if all of your services and applications run on a single computer, it is important to run NTP there. If you have several computers on the same LAN, you may want to consider running an NTP server (pointing to an external time source) on one of them and pointing all of the other NTP clients on the LAN to it. All NMS servers should be configured to be in the same timezone, and have their time synchronized with ntp, including all WebLogic servers.
Refer to the “Isis Configuration” chapter of the Oracle Utilities Network Management System Configuration Guide for more details regarding the configuration of the Isis message bus for use with the Oracle Utilities Network Management System applications.
Client Authentication
Authorization and roles are stored in the database, but the authentication must come from an external source. No matter what the authentication source, each login name must be granted access to the system by using the Configuration Assistant. Active Directory and LDAP are supported authentication sources.