Upgrading to Netra j 2.0 Software

This section describes Netra j 2.0 software upgrade considerations.

Upgrading From Netra i to Netra j

Upgrading from a Netra i system to a Netra j system means a shift of emphasis in the capabilities of the server.

• Netra i systems provide only NIS client capabilities, whereas Netra j servers provide NIS server capabilities. For example, a Netra i site with local user accounts must become NIS user accounts for login through JavaStation systems.

• ISDN Internet access, considered central to a Netra i server, is no longer available to the Netra j server.

Netscape Navigator Requirement

Netscape Navigator is required for systems upgrading from Netra i versions 3.1 and 3.2 that support Netscape Enterprise Server(TM) and FireWall First!.

Local Name Service

The following information affects systems upgrading from Netra i 3.1 and Netra j 1.1.

Before completing the initial configuration steps on the Netra j 2.0 software, check the Netra j host name from the Local Name Service module, under Name Services.

If the Netra j host name is mapped to the loopback IP address (127.0.0.1), you must delete this reference to the host name machine. In such cases, you must add a separate host-to-IP address mapping that maps the host name of the Netra j server to the IP address of the network interface that is used to provide boot services to the JavaStation client or network computer.

Upgrading to Netra j 2.0 Software (OS Installation Required)

If you are upgrading Netra i 3.1 and Netra i 3.2 systems to Netra j 2.0 and you must load the operating system, make a tape backup of the entire file system. In particular, back up the Netscape Enterprise Server web documents and subsequently restore once the upgrade process is complete and the SUNWnse package reinstalled.

If you are upgrading from Netra i 3.1 or 3.2 to Netra j 2.0, you should make a tape backup of their Netscape Web Server port 80 htdocs directory (for Netscape Enterprise Server 2.0 this is /usr/local/netscape/nse-home/docs; for Netscape Enterprise Server 3.0 it is /opt/netscape/suitespot/docs). This especially pertains to upgrades requiring an OS install.

File System Backup

When you upgrade from Netra i 3.1 to Netra j 2.0, the file system backup options set for Netra i 3.1 are lost after the upgrade. The system administrator should restore the options for Netra j 2.0.

Upgrading From Netra j 1.1 Software

Administration Web Server User Password

The port 81 Administration Web Server user password is lost on upgrading to Netra j 2.0 from Netra j 1.1 because the National Computer Security Association (NCSA) server is no longer used for Netra j administration. Sun WebServer now performs this task, and the Administration Web Server user password is stored differently. This is why you are always prompted for a new Administration Web Server password when logging in immediately after an upgrade.

Access control lists associated with the NCSA server is also lost. You must apply similar access rights to the server through Sun WebServer after upgrading to Netra j 2.0.

Local Name Service

The following information affects systems upgrading from Netra i 3.1 and Netra j 1.1.

Before completing the initial configuration steps on the Netra j 2.0 software, check the Netra j host name from the Local Name Service module, under Name Services.

If the Netra j host name is mapped to the loopback IP address (127.0.0.1), you must delete this reference to the host name machine. In such cases, you must add a separate host-to-IP address mapping that maps the host name of the Netra j server to the IP address of the network interface that is used to provide boot services to the JavaStation client or network computer.

Web Proxy

On networks with both a Netra j server and a separate Web proxy server, you must modify JavaStation HotJava Views and HotJava Browser preferences to allow no proxy for the Netra j server. Otherwise, the JavaStation client always contacts the Web proxy for all its services, which could lead to potential connectivity problems.