Directory Structure
The Oracle Utilities Network Management System has three directory areas involved with product installation, project configuration, and runtime. This section describes how these directories are created and interact.
Directory Overview
The Oracle Utilities Network Management System Directory structure is comprised of three major areas:
• The Oracle Utilities Network Management System Installation directory
• The Oracle Utilities Network Management System Project Configuration directory
• The Oracle Utilities Network Management System Runtime directory
Installation Directory
The Oracle Utilities Network Management System Installation directory is created as part of the installation process. There are two environment variables involved with this directory:
• $NMS_ROOT: Points to the top-level of the Oracle Utilities Network Management System installation directory. $NMS_ROOT is typically set to be the nmsadmin user home directory (for example, users/nmsadmin).
The installation process will create a directory structure under $NMS_ROOT; the top level is named nms, and it has a sub-directory named product. The product directory contains directories for each installed Oracle Utilities Network Management System version, which will include the major release or service pack and any applied patches.
For example:
• NMS 2.5.0.0.0 (Major Release)
$NMS_ROOT
nms
product
2.5.0.0
2.5.0.0.0 As patches are applied, they are added to the product directory:
$NMS_ROOT
nms
product
2.5.0.0
2.5.0.0.0
2.5.0.0.1
2.5.0.0.x• NMS 2.5.0 Service Pack 2
$NMS_ROOT
nms
product
2.5.0.2
2.5.0.2.0 As in the case of the major release example above, as patches are applied to the Service Pack, their directories are added to the product directory.
• $NMS_BASE: Points to the current major release or service pack version without the patch level number. For example, 2.5.0.0 (major release) or 2.5.0.1 (service pack).
The installation directory will contain all content from the Oracle E-Delivery and should not be changed by the runtime system or user.
Project Configuration Directory
The Oracle Utilities Network Management System Project directory will contain all project-specific configurations, scripts, and programs required to run the Oracle Utilities Network Management System. This directory is identified by the $NMS_CONFIG environment variable and is typically set to $NMS_HOME/project_name; the Oracle Utilities Network Management System demonstration environment’s project name is OPAL so $NMS_CONFIG is set to $NMS_HOME/OPAL.
Note: Configuration files in the configuration directory need to be prefixed by the project name. For example, OPAL_devices.sql. For more information on creating custom configuration files, see the Oracle Utilities Network Management System Configuration Guide.
The top level directory structure for the project configuration directory is as follows.
$NMS_CONFIG
bin
data
jconfig
migration
sql
workbooksOther files and directories can exist in the $NMS_CONFIG directory, but only those documented above will be utilized by the install script: nms-install-config.
Runtime Directory
The Oracle Utilities Network Management System runtime directory will contain all runtime specific configurations, scripts, and programs required to run the Oracle Utilities Network Management System. This directory is identified by the environment variable: $NMS_HOME and, for Oracle Utilities Network Management System Release 2.5.0.2.0, this must be set to $HOME (/users/nmsadmin).
$NMS_HOME
bin
data ($OPERATIONS_MODELS)
etc
java
lib
logs (based on $NMS_LOG_DIR)
migration
data
manual
scripts
sql
nms
sql
xmlThe NMS executables and shared libraries are in the $NMS_BASE/bin (for example, /users/nmsadmin/product/2.5.0.0/lib) and $NMS_BASE/lib (for example, /users/nmsadmin/product/2.5.0.0/lib) directories.
Directory Administration
The install process establishes the Oracle Utilities Network Management System Installation Directory. The project implementation team creates the contents of the Oracle Utilities Network Management System Project Directory. The nms-install-config script installs the product and project configurations into the runtime directories. Project files will either be appended to or override the product configurations based on type.