N1 Service Provisioning System 4.1 Installation Guide

Configuration Decisions

The installation program prompts you for configuration information for the N1 Service Provisioning System 4.1. Use the sections below to make configuration decisions before you begin the installation.

The Java Runtime Environment

When installing on Solaris OS, Red Hat Linux, or IBM AIX systems, the installation program prompts you to install the JRE or to provide a valid path to a JRE. When installing on Windows, the installation program automatically installs the JRE without prompting you.

If you are installing on a Red Hat Linux system, the installation script searches your machine for an instance of the JRE in the default location. If the JRE is not installed in the default location, you must install the JRE. If the installation program finds the JRE in the default location, you can choose whether or not to reinstall the JRE.

If you are installing on Solaris OS or IBM AIX systems, if you chose not to install the JRE, the installation script prompts you to provide a path to a valid JRE. Then the installation script verifies that the JRE is supported. If the JRE is not supported but has a higher version number than the versions that are supported, the installer warns you that the JRE is not supported and asks if you want to continue. If you specified a version of the JRE that is supported by the N1 Service Provisioning System 4.1, the installation script sets the JRE_HOME variable to the JRE that you specified. The installation script also creates a symbolic link, N1SPS4.1-home/common/jre, which points to the JRE directory. By creating a symbolic link, the N1 Service Provisioning System 4.1 applications use the JRE without changing its location, which other applications might depend upon.


Note –

You should install the bundled JRE only once per machine. For example, if you are installing the Master Server, a Local Distributor, and the CLI Client on the same machine, you should install the JRE with the Master Server, but not with the Local Distributor or the CLI Client.


User Ownership of Applications

The installation program prompts you to select a user and group to own the application that you are installing. If you want to configure the applications to communicate using SSH, install the Master Server, Local Distributors, and Remote Agents as the same user.

The root user cannot own the Master Server. You can install the Master Server as the user that owns the Master Server or you can install the application as root and, when you are prompted, specify which user owns root.

If you want the Remote Agent to have root privileges on the machine where it is running, then you must run the installation program as the root user. Even though you may specify a user other than root to own the Remote Agent, if you want the Remote Agent to have root privileges on the machine where it is running, start the installation program as the root user.

Network Protocol

The installation program prompts you to choose a network protocol for communication among the software applications. Before you install the software, decide which encryption method to use, TCP/IP, SSH, or SSL. If you select SSL, you must also specify which cipher suite to use, encryption with no authentication or encryption with authentication.

For more information about network protocols, see Network Protocols.

Jython

When you install the CLI Client, the installation program prompts you to specify whether or not Jython is installed on the machine. The CLI Client uses the Jython programming language to run in interactive mode. However, Jython is not required to use the CLI Client. For more information about Jython and the CLI Client, see Command Line Interface Client.