Sun N1 Service Provisioning System 5.2 Installation Guide

General System Requirements

This section lists general system requirements for installing and using the Sun N1 Service Provisioning System 5.2.

Supported Web Browsers

The following table lists the web browser requirements for the Sun N1 Service Provisioning System 5.2 browser interface.

Table 2–9 Web Browser Requirements for the Browser Interface


Platform	Browser
Solaris, Red Hat, SUSE, HP-UX	Netscape Navigator^TM 7.1, Mozilla^TM 1.4
Windows	Netscape Navigator 7.1, Mozilla 1.4, Internet Explorer 5.5, Internet Explorer 6.0
AIX	Mozilla 1.4

Note –

Some web proxy servers are configured to block popup windows. The Sun N1 Service Provisioning System 5.2 relies on the ability to present popup windows to run properly. Do not run web proxy servers that block popup windows or set your browser to block popup windows.

To run properly, the Sun N1 Service Provisioning System 5.2 relies on the ability to use cookies. Set your browser to allow the use of cookies.

Requirements for SSH

If you want to use SSH for secure connections on Linux and UNIX systems, you must have SSH protocol version 2 installed on each server that you want to use SSH.

Requirements for Jython

If you want to use Jython with the CLI Client, install Jython version 2.0 or higher. For more information about Jython, see http://www.jython.org.

Requirements for Locales

The Sun N1 Service Provisioning System 5.2 has been internationalized to install and run in localized environment. Also, the Sun N1 Service Provisioning System 5.2 accepts non–ASCII characters. You will need to adhere to the following requirements if you require that the software support non-ASCII characters:

All applications must be run in the same locale or in locales that are equivalent. The Remote Agent, Local Distributors, and CLI Client must run a locale that is compatible with the locale in which the Master Server is running.
You must use Internet Explorer 5.5 or 6.0, or Netscape 7.0.
Set the web browser Character Interface to use UTF-8, which is also known as Unicode or Universal Alphabet.
In the configuration files, such as the config.properties file, all non-ASCII characters must be Unicode-encoded. You can create configuration files in any encoding. Then, use the native2ascii command that is available in the Java^TM Development Kit (JDK) package to convert the file to Unicode-encoded ASCII characters.