Sun N1 Service Provisioning System 5.2 Installation Guide

Chapter 4 Installing the Sun N1 Service Provisioning System 5.2 on Linux and UNIX Systems

This chapter describes the steps to install the Sun N1 Service Provisioning System 5.2 on Linux and UNIX systems. This chapter discusses the following topics:

Installing the Sun N1 Service Provisioning System 5.2

You will install each of the applications separately by using the appropriate installation script on the product media. The installation scripts for each of the Sun N1 Service Provisioning System 5.2 applications begin by performing the same set of preparatory tasks and asking the same questions about directories, files, and installing the Java^TM runtime environment (JRE). Each script then asks specific configuration questions about the application that it will install.

How to Install the Sun N1 Service Provisioning System 5.2 on Linux and UNIX Systems

Before You Begin

Review the installation process overview in Installing the Sun N1 Service Provisioning System 5.2 – Process Overview. Complete any necessary tasks prior to installing the applications.

Steps

Log in as the user that you want to own the application.

You can log in as root and install the software as the root user. If necessary, the installation program prompts you for information about which user should own the software.

Note –
If you are installing the Master Server or the CLI Client on a Solaris server, you must login as root.

Access the installation scripts.
- If you are installing from the DVD, insert the DVD: :
- If you are installing from the image that you downloaded, change to the directory where you saved the downloaded image.

Change to the directory on the software DVD or within the downloaded image where the installation script is located.
# cd /script-directory
script-directory is one of the following values:
- solaris_sparc
- solaris_x86
- aix
- linux
- hpux

Start the installation script for the application that you want to install.
# cr_app_opsystem_5.2.sh [-allowForwardVersion]
app is one of the following values:
- ms – installs the Master Server
- ra – installs the Remote Agent
- ld – installs the Local Distributor
- cli – installs the CLI Client
opsystem is one of the following values:
- solaris_sparc – installs the application on SPARC based hardware that is running the Solaris OS. To install the Master Server or CLI client, use solaris_sparc_pkg.
- solaris_x86 – installs the application on x86 based hardware that is running the Solaris OS. To install the Master Server or CLI client, use solaris_x86_pkg.
- aix – installs the application on IBM AIX
- linux_i386 – installs the application on Red Hat Linux and SUSE Linux Enterprise Server (32–bit)
- linux_x86_64 – installs the application on Red Hat Linux and SUSE Linux Enterprise Server (64–bit)
- hpux – installs the application on PA-RISC based systems that are running HP-UX
The -allowForwardVersion option enables you to install an Sun N1 Service Provisioning System 5.2 application on a version of an operating system that is numerically higher than the highest version the Sun N1 Service Provisioning System 5.2 supports for that operating system. If you use the -allowForwardVersion option, the installation program does not verify that the operating system on which you are installing the application is supported. There is no standard Sun Services support for use of the Sun N1 Service Provisioning System 5.2 on unsupported operating systems.

Caution –
Installing the Sun N1 Service Provisioning System 5.2 on unsupported operating systems might result in undefined and unexpected behavior. Install the Sun N1 Service Provisioning System 5.2 on unsupported operating systems only for testing purposes. Do not use the Sun N1 Service Provisioning System 5.2 on unsupported operating systems in a production environment.

Answer the configuration questions when prompted by the installation program.

A worksheet is available at Worksheet for the Master Server outlining the sequence of questions, example values, and options to be gathered prior to installation.

Note –
- The Master Server installation path (BASEDIR) is limited to 37 characters on Solaris.
- The Master Server installation path (BASEDIR) is limited to 35 characters on Linux.
The installation program completes the installation and asks if you want to start the application.

The installation program saves a log of events in the /tmp/N1SPSInstaller.log.pid file.

pid is the process ID of the installer.

At this point, the following packages have been installed:
- Master Server
  - SUNWspsms
  - SUNWspsc1
  - SUNWspsj1
- CLI
  - SUNWspsc1
  - SUNWspscl
  - SUNWspsj1

Non-Interactive Installation of a Remote Agent on Linux and UNIX Systems

You can install the Remote Agent non-interactively by providing a parameters file to indicate your configuration selections. When you provide a parameters file to the installation program, the installation program does not prompt you for configuration selections during the installation. Instead, the installation program uses the configuration information that is provided in the parameters file.

How to Non-Interactively Install a Remote Agent on Linux and UNIX Systems

Before You Begin

You must install a Master Server before you install a Remote Agent. The Master Server does not need to be installed on the machine on which you want to install the Remote Agent.

Steps

On the machine where you want to install the Remote Agent, log in as the user that you want to own the Remote Agent.

You can log in as root and install the software as the root user. If necessary, the installation program prompts you for information about which user should own the software.

Access the installation scripts.
- If you are installing from a DVD, insert the DVD:
- If you are installing from the image that you downloaded, change to the directory where you saved the downloaded image.

Change to the directory on the software CD or within the downloaded image where the installation script is located.
% cd /script-directory
script-directory is one of the following values:
- solaris_sparc
- solaris_x86
- aix
- linux
- hpux

Copy the installation script to the machine on which you want to install the Remote Agent.
% cp cr_ra_opsystem_5.2.sh RA-machine/
RA-machine is a directory on the machine on which you want to install the Remote Agent. opsystem is one of the following values:
- solaris_sparc – installs the Remote Agent on SPARC based hardware running the Solaris OS
- solaris_x86 – installs the Remote Agent on x86 based hardware running the Solaris OS
- aix – installs the Remote Agent on IBM AIX
- linux_i386 – installs the Remote Agent on Red Hat Linux and SUSE Linux Enterprise Server (32–bit)
- linux_x86_64 – installs the Remote Agent on Red Hat Linux and SUSE Linux Enterprise Server (64–bit)
- hpux – installs the application on PA-RISC based systems that are running HP-UX

Copy a parameters file into the same directory as the installation script.

A sample parameters file is installed on the Master Server in the N1SPS5.2-MasterServer-home/server/bin directory when you install the Master Server. You can use the default values that are provided in this file or edit the file and add your custom values. The contents of the cr_ra_remote_params.sh sample parameters file and descriptions of the variables that you can set are in Sample Remote Agent Parameters File for Linux and UNIX Systems.

You can also create a new parameters file to use. The parameters file must be an executable file.

N1SPS5.2-MasterServer-home is the directory where you installed the Master Server.

Caution –
The values for the CR_RA_SUID and CR_RA_CTYPE variables are not set in the sample parameters file. You must set values for these variables or the installation script will abort. Also, if you choose to use an insecure connection type, such as raw or SSL encryption with no authentication, you must set the CR_RA_CTYPE_CONFIRM variable value to true.

The value of the CR_RA_SUID variable can be y, if and only if the connection type is ssh. If this condition is not met, the installer terminates.

Start the installation script.
% cr_ra_opsystem_5.2.sh -paramfile parameters-file.sh [-allowForwardVersion]
opsystem is one of the following values:
- solaris_sparc – installs the Remote Agent on SPARC based hardware running the Solaris OS
- solaris_x86 – installs the Remote Agent on x86 based hardware running the Solaris OS
- aix – installs the Remote Agent on IBM AIX
- linux_i386 – installs the Remote Agent on Red Hat Linux and SUSE Linux Enterprise Server (32–bit)
- linux_x86_64 – installs the Remote Agent on Red Hat Linux and SUSE Linux Enterprise Server (64–bit)
- hpux – installs the application on PA-RISC based systems that are running HP-UX
parameters-file is the name of the parameters file that you want the installation program to use to obtain the configuration information. The parameters file must be an executable file.

The -allowForwardVersion option enables you to install an Sun N1 Service Provisioning System 5.2 Remote Agent on a version of an operating system that is numerically higher than the highest version the Sun N1 Service Provisioning System 5.2 supports for that operating system. If you use the -allowForwardVersion option, the installation program does not verify that the operating system on which you are installing the Remote Agent is supported. There is no standard Sun Services support for use of the Sun N1 Service Provisioning System 5.2 on unsupported operating systems.

Caution –
Installing the Sun N1 Service Provisioning System 5.2 on unsupported operating systems might result in undefined and unexpected behavior. Install the Sun N1 Service Provisioning System 5.2 on unsupported operating systems only for testing purposes. Do not use the Sun N1 Service Provisioning System 5.2 on unsupported operating systems in a production environment.

Remote Installation of Remote Agents on Linux and UNIX Systems

You can install a Remote Agent remotely from another machine across the network. When you install the Master Server, the scripts needed to remotely install a Remote Agent are installed in the N1SPS5.2-MasterServer-home/server/bin directory. The installation is a non-interactive installation and uses environment variables to manage the installation and configuration of the Remote Agents. You can set the environment variables in a parameters file, at the command line, or use the default values provided by the installation script.

How to Remotely Install Remote Agents on Linux and UNIX Systems

The installation scripts for the Remote Agent are specific to the operating system of the target machine. You need to complete these steps for each operating system running on your target machines.

Before You Begin

The target machine must meet the following requirements:

The UNIX utility sshd must be running and have direct IP connectivity to the source machine.
Support for the UNIX hostname command must exist, so that the remote installation script can call this command. The Remote Agent must be configured to listen on the IP address of the host name returned by the hostname command.

The Master Server machine must have the UNIX utilities ssh and scp installed and in the path at the time of execution.

The remote installation program uses environment variables to manage the installation and configuration of the Remote Agent. You can set the environment variables in a parameters file or at the command line. You must declare a value for the following environment variables:

CR_RA_CTYPE=raw – The Remote Agent connects to the Master Server or Local Distributor using no encryption. Valid values are raw, ssh, and ssl.
CR_RA_SUID – Installs the Remote Agent with setuid root privilege. To specify a value of yes, you must run the installation script as the root user. Valid values are y and n.

The value of the CR_RA_SUID variable can be y, if and only if the connection type is ssh. If this condition is not met, the installer terminates.
CR_RA_INSTALLER_HOSTS – If you do not supply host names on the command line or as an environment variable, the installation script exits with an error. An example of a valid value is: CR_RA_INSTALLER_HOSTS=host1,host3.enterprise.com,10.10.0.207.

Steps

On the Master Server machine, access the installation scripts.
- If you are installing from a DVD, insert the DVD:
- If you are installing from the image that you downloaded, change to the directory where you saved the downloaded image.

Change to the directory on the software DVD or within the downloaded image where the installation script is located.
% cd /script-directory
script-directory is one of the following values:
- solaris_sparc
- solaris_x86
- aix
- linux
- hpux

Copy the installation script to the Master Server.
% cp cr_ra_opsystem_5.2.sh N1SPS5.2-MasterServer-home/server/bin
N1SPS5.2-MasterServer-home is the directory where you installed the Master Server and opsystem is one of the following values:
- solaris_sparc – installs the Remote Agent on SPARC based hardware running the Solaris OS
- solaris_x86 – installs the Remote Agent on x86 based hardware running the Solaris OS
- aix – installs the Remote Agent on IBM AIX
- linux_i386 – installs the Remote Agent on Red Hat Linux and SUSE Linux Enterprise Server (32–bit)
- linux_x86_64 – installs the Remote Agent on Red Hat Linux and SUSE Linux Enterprise Server (64–bit)
- hpux – installs the application on PA-RISC based systems that are running HP-UX

Change directories to where the scripts are located.
% cd N1SPS5.2-MasterServer-home/server/bin
N1SPS5.2-MasterServer-home is the directory where you installed the Master Server.

Determine how to provide configuration information to the installation script.

Create a new parameters file or edit the sample parameters file that was installed by the Sun N1 Service Provisioning System 5.2. When you install the Master Server, a parameters file is installed. The file is named N1SPS5.2-MasterServer-home/server/bin/cr_ra_remote_params.sh. You can use the default values that are provided in this file or edit the file and add your custom values. You can also create a new parameters file to use. The contents of the sample parameters file and descriptions of the variables that you can set are in Sample Remote Agent Parameters File for Linux and UNIX Systems. The parameters file must be an executable file.

Caution –
The values for the CR_RA_SUID and CR_RA_CTYPE variables are not set in the sample parameters file. You must set values for these variables or the installation script will abort. Also, if you choose to use an insecure connection type, such as raw or SSL encryption with no authentication, you must set the CR_RA_CTYPE_CONFIRM variable value to true.

The value of the CR_RA_SUID variable can be y, if and only if the connection type is ssh. If this condition is not met, the installer terminates.

Set the environment variables.

% export CR_RA_INSTALLER_USER=username
% export CR_RA_INSTALLER_WORKDIR=/working_directory
% export CR_RA_INSTALLER_LEAVEFILES=yes, no
% export CR_RA_CTYPE=raw, ssh, ssl
% export CR_RA_SUID=y, n
% export CR_RA_INSTALLER_HOSTS=hostnames.enterprise.com,10.10.0.207

Start the remote installation.
% cr_ra_remote.sh -paramfile path-to-file/parameters-file.sh –f cr_ra_opsystem_5.2.sh hostnames
- cr_ra_opsystem_5.2.sh is the installation script that you copied from the Sun N1 Service Provisioning System 5.2 CD or downloaded image.
- path-to-file/parameters-file is the path to the parameters file and the name of the parameters file that you want the installation program to use to obtain the configuration information. If you set the environment variables or you want the installation script to use the default values, you do not need to specify a parameters file.
- hostnames are the host names of the machines on which to perform the installation. Separate the hostnames by a space. If you specified the host names in the CR_RA_INSTALLER_HOSTS parameter, either in the parameters file or as an environment variable, you do not need to specify the hos tnames on the command line. If you specify host names on the command line, those hosts are installed and any hosts specified in the CR_RA_INSTALLER_HOSTS parameter are not be installed.

Make a note of the location of the log file.

The installation program notifies you that it is creating a log file and displays the location of the log file. Note the location of the file so that you can view it later.

If prompted by the installation program, provide passwords for the remote machine.

The installation script generates log files on the remote machine.

Starting Applications on Linux and UNIX Systems

The following table lists the commands to start the Sun N1 Service Provisioning System 5.2 applications on Linux and UNIX systems. N1SPS5.2-home is the home directory of the application.

Caution –

Do not use the Bourne shell to start the Master Server or other Sun N1 Service Provisioning System 5.2 applications. If you start the Master Server process using the cr_server start command in a Bourne shell, and if a ^C command is issued to any subsequent command in the same shell that started the Master Server, then the database and Master Server processes stop.

In the N1SPS5.2-home/server/bin/roxdb.out file, the following messages appear as the most recent entries:

DEBUG:  fast shutdown request
DEBUG:  aborting any active transactions

Table 4–1 Start Commands for Linux and UNIX System Applications


Application	Path to Command	Command to Start
Master Server	`N1SPS5.2-home/server/bin/`	`cr_server start`
Local Distributor	`N1SPS5.2-home/ld/bin/`	`cr_ld start`
Remote Agent	`N1SPS5.2-home/agent/bin/`	`cr_agent start`
CLI Client	`N1SPS5.2-home/cli/bin/`	`cr_cli CLI-command`
Jython version of CLI Client	`N1SPS5.2-home/cli/bin/`	`cr_clij CLI-command`