Installing the SDX Software

The SDX software is provided as several standard Solaris packages, Java Web Archives, and Java Enterprise Archives. The SDX GUI installer is a wrapper around the Solaris packages. You can install the SDX software by using either the SDX GUI installer or the UNIX package tools. This section illustrates the installation process with the SDX GUI installer.

You must have administrator root permissions on each host to install SDX software.

See Installing SDX Components as Solaris Packages for information about installing the Solaris packages with the pkgadd utility.

Installation Modes

The SDX GUI installer has two modes: graphical and silent. We use the graphical mode to illustrate the installation procedures.

Graphical Mode

Graphical mode employs an installer GUI (Figure 30) to determine what SDX components you want to install and where you want to install them. Buttons at the bottom enable you to cancel the installation, move to a previous step, and move to the next step. You can move, minimize, or close the installer window.

Figure 30: Installer GUI

When you have made all your selections or accepted the defaults, the installer presents a summary of your choices. The installer then opens a UNIX window as it uses the pkgadd command to install each component. The window requests confirmation or other input for installation of the package.

Silent Mode

The silent mode does not display the installation GUI. Instead, the system prompts you for your input in a UNIX window as the various components of the SDX software are installed. Provide input as requested by the installer to proceed with the installation.

To start the installation process in silent mode, enter the following command at the UNIX command line:

./UMCsdx.bin -D[argument]="[value]" -i silent

The following table shows the possible inputs to this command.

[argument]	default [value]	Notes
USER_INSTALL_DIR	/opt/UMC	Installation destination directory
USER_INPUT_RESULT_1	sdxuser	User
USER_INPUT-RESULT_2	staff	Group
MEDIAFOLDER	cdrom/cdrom0/SDX	Installation source directory

You may want nonroot users to configure and administer the SDX software after it is installed. If so, you can define users with nonroot privileges with the USER_INPUT_RESULT_1 and USER_INPUT_RESULT_2 arguments to the command. For example:

./UMCsdx.bin -DUSER_INPUT_RESULT_1="sdxuser" 
-DUSER_INSTALL_DIR="/opt/UMC" -DMEDIA_FOLDER="/cdrom/cdrom0" -i silent

Launching the Installer

To launch the installer:

1. On the UNIX host where you will install the SDX software, log in as root.
2. Ensure that the display variable is set.

echo $DISPLAY

3. (Optional) Create nonroot users and groups using the UNIX admintool to enable nonroot users and groups to administer the SDX software.
4. Load the SDX software CD, and launch the SDX installer.

/cdrom/cdrom0/UMCsdx.bin

5. Follow the instructions displayed in the installer windows to select software components and destination directories (folders) for installation.
6. The installer opens a UNIX window and prompts you for input as it installs each package in the installation set. Follow the instructions at each prompt.
7. Click Done when the installer indicates that the installation has finished.

Notes on Using the Installer

The following information may assist you in making choices during the installation process.

Default Installation Directory

The installer fills out the field in the Choose SDX Install Folder window with the default installation directory, /opt/UMC. All examples in this book presume you have accepted the default directory. Although you can specify a different installation directory, you cannot change the location where SDX components are installed within that directory.

NOTE: The SDX software does not support the use of spaces in filenames or directories. If you create files or directories inside the installation directory structure, you must do the following: Ensure that the names do not include spaces. Manage the files and directories outside the context of SDX software. If a filename or directory name includes a space, the removal of various SDX packages will fail.

SDX Component Installation Sets

In the Choose Product Features window, you select a desired set of SDX components from the menu. An installation set includes one or more feature sets, in part or whole. A feature set includes one or more components. For each installation set, various recommended or required components are selected by default for installation. Click on a package or component to display a brief description.

NOTE: If you install SDX software over an existing installation, the installer displays a message stating that the existing software will be overwritten.

Table 12 lists components for each available feature set, their Solaris package names, and the directories where each component is installed.In Table 12, the directories listed are all installed in /opt/UMC, except for ipf, which is installed in /opt/ipf. The home directory for DirX is DirX_HOME.

Table 12: Solaris packages and installation directories for all available installation components 

Feature Set	Components	Package	Installation Directory
Env	Java Runtime Environment Python Runtime Environment (includes Python additional libraries)	UMCjre SMCpython and UMCpyadd	jre python
License Server	License Server	UMClicsvr	licsvr
Application and Web Server	JBoss	UMCjboss	jboss
SAE System	SAE (for JUNOS routers) Agent	UMCsae UMCagent	sae agent
Captive Portal System	IP Filter (Solaris 8 or 9) Web Redirect	ipfx, ipf UMCredir	ipf redir
Configuration Editor	Configuration Editor	UMCecl	sysconf
NIC System	NIC System	UMCnic	nic
Redundancy Monitor System	Redundancy Monitor System	UMCredmon	redmon
Admin Workstation	Policy Editor SDX Admin omniORB	UMCpom UMCsmg omniORB	pom smg omni
Directory Server	OpenLDAP OpenLDAP Add-on Sun ONE (iPlanet) Directory Server Add-on DirX Add-on Migration	UMColdap UMColdapa UMCiDSa UMCdirxa UMCmig	openldap openldap conf $DIRX_HOME$ migration
Merit RADIUS	Merit RADIUS	UMCradius	radius

Table 13 lists the components and feature sets that are included by default for each installation set. In general, an installation set corresponds to a group of software components that provide a specific functionality. For example, if you want a particular host to act as an SAE and directory server, you could deploy the SAE and Directory Server installation set on that host.

NOTE: For a given installation set, you can select any additional desired components or deselect any undesired components. Be careful if you do this; deselecting required components may have undesired results.

 Table 13:  Default installation set components 

 Installation Set
 Feature Sets and Components

 SDX Demo

 Env

  
 Java Runtime Environment
  
 Python Runtime Environment



 

 Application and Web Server

  
 JBoss



 

 SAE System

  
 SAE 
  
 Agent



 

 Captive Portal System

  
 IP Filter (Solaris 8 or 9); the installer detects the Solaris version on the host and installs the appropriate IP Filter for that OS.
  
 Web Redirect



 

 Configuration Editor

  
 Configuration Editor



 

 Admin Workstation

  
 Policy Editor
  
 SDX Admin
  
 omniORB



 

 Directory Server

  
 OpenLDAP
  
 OpenLDAP Add-on



 

 Merit RADIUS

  
 Merit RADIUS



 SDX License Server

 Env

  
 Java Runtime Environment
  
 Python Runtime Environment



 

 License Server

  
 License Server



 SAE and Directory Server

 Env

  
 Java Runtime Environment
  
 Python Runtime Environment



 

 SAE System

  
 SAE
  
 Agent



 

 Directory Server

  
 OpenLDAP
  
 OpenLDAP Add-on



 SAE Server

 Env

  
 Java Runtime Environment
  
 Python Runtime Environment



 

 SAE System

  
 SAE
  
 Agent



 Application and Web Server

 Application and Web Server

  
 JBoss



 NIC Server

 Env

  
 Java Runtime Environment
  
 Python Runtime Environment



 

 NIC System

  
 NIC System



 Redundancy Monitor Server

 Env

  
 Java Runtime Environment
  
 Python Runtime Environment



 

 Redundancy Monitor System

  
 Redundancy Monitor System



 System Configuration Editor

 Configuration Editor

  
 Configuration Editor



 Captive Portal

 Env

  
 Python Runtime Environment



 

 Captive Portal System

  
 IP Filter (Solaris 8 or 9); the installer detects the Solaris version on the host and installs the appropriate IP Filter for that OS.
  
 Web Redirect



 Administrator WorkStation

 Env

  
 Java Runtime Environment
  
 Python Runtime Environment



 

 Admin Workstation

  
 Policy Editor
  
 SDX Admin
  
 omniORB



 Directory Server

 Directory Server

  
 OpenLDAP
  
 OpenLDAP Add-on



 RADIUS Server

 Merit RADIUS

  
 Merit RADIUS



 Custom

 Env

  
 Java Runtime Environment
  
 Python Runtime Environment



 

 Application and Web Server

  
 JBoss



 

 SAE System

  
 SAE
  
 Agent



 

 Configuration Editor

  
 Configuration Editor



 

 Admin Workstation

  
 Policy Editor
  
 SDX Admin
  
 omniORB



 

 Directory Server

  
 Directory ServerOpenLDAP
  
 OpenLDAP Add-on



 

 Merit RADIUS

  
 Merit RADIUS




 

Installing the SAE for the JUNOSe Routing Platform

The SDX GUI Installer does not currently support installation of the UMCssp package for the JUNOSe routing platform. You must use the pkgadd command to install the SAE component for this platform. See Installing SDX Components as Solaris Packages for information about the pkgadd command.

User Input

You can specify nonroot users or groups in the Get User Input window. The users or groups must already exist (created via the UNIX admintool) or the installer returns an error.

NOTE: Some SDX daemon processes, such as the SAE and the LDAP directory server, use many open files and sockets. You may need to customize the hard and soft limits for the system resources that are used by such SDX processes. Examine your system configuration information and UNIX account holder configuration that runs the SDX processes. See your Solaris system administration documentation for more information about determining the limits of your system configuration and UNIX account holder configuration. The UNIX man pages for limit(1) and sysdef(1M) also provide useful information. For example, if you are installing the SDX software in a nonroot environment in a typical Solaris 8 or Solaris 9 installation, the maximum number of file descriptors is too low for nonroot users. The hard limit is 1024, and the soft limit for nonroot users is 256. You can use the UNIX ulimit command to increase the number.

Installation Defaults

The admin file assigns values to various installation parameters to define default installation actions. The Get Admin Option panel in the GUI installer enables you to select the installation admin options. See the UNIX man page for admin(4).

• Choose SDX Admin file for the same behavior as in SDX 4.0.
• Choose Solaris Admin file to use the Solaris default admin file. This file is located in /var/sadm/install/admin/default.

The selected admin option is used to install all of the packages. You cannot change admin options per package. The admin selection affects only the current SDX GUI installer instance; if you relaunch the installer the selection is neither remembered nor used.

SNMP Agent Installation Notes

Installation of the SNMP agent has the following special considerations.

If you install the SNMP Agent on a host running other SDX components, you must restart the other SDX components after the installation to enable the SNMP Agent to manage them.

You can install the SNMP agent to run under a nonroot user. To do so, select the "under a user identification" option when asked where to install UMCagent during the package installation (see Installing SDX Components as Solaris Packages for information about installing packages). Provide the login name for the nonroot user when prompted. SNMP agent is then installed in the home directory of the named user. If you are using the GUI installer, you can specify authorized nonroot users in the Get User Input window.

If you install SNMP agent to run under a nonroot user and later want to start, stop, or monitor SNMP agent while logged in as the root user, you must use the smagentroot command instead of the smagent command. Failure to do so may cause the agent to create files, such as log files, that are owned by root. If a nonroot user later runs SNMP agent, the agent will not be able to update these files.