test

Netra j 3.0 Product Notes

Netra j 3.0 Product Notes

This document contains late-breaking product information for the Netra(TM) j 3.0 software release.

Additional late-breaking information on the Netra j 3.0 software and JavaStation(TM) computers is posted on the Web at:

http//www.sun.com/javastation.

Before Installation or Upgrade

Read this section before installing or upgrading to the Netra j 3.0 software.

Upgrading Printer Administration

If you are upgrading from the Solaris(TM) 2.5.1 to the Solaris 2.6 operating environment, and printer configuration information resides on the system being upgraded, you must convert the Solaris 2.5.1 LP configuration to the format that is used by the Solaris 2.6 LP print services. If you don't, the printers on the Solaris 2.6 system may not be configured correctly.

To Convert the LP Configuration

  1. Upgrade to the Solaris 2.6 operating environment.

  2. As superuser, open a shell window and run the following script: 

    # /usr/lib/print/conv_lp

    This script constructs the /etc/printers.conf file from the contents of the /etc/lp/printers directory.

Downloading Localized Netra j 3.0 Software

The Netra j 3.0 Installation Guide describes which files to download from the e-commerce site for an English locale installation or upgrade. File names for non-English locales are provided in the following paragraphs.

For any non-English locale, you need the following files: 

netraj30file_1lo.bin
netraj30file_2lo.bin
netraj30file_3lo.bin
netraj30file_4lo.bin
netraj30_L10N1.bin
netraj30_L10N2.bin
netraj30_common1.bin
netraj30_common2.bin

If you are using the Solaris 2.5.1 operating environment, you need these files: 

solaris251addonslo.bin
solaris251addonsL10N.bin

If you are using the Solaris 2.6 operating environment, you need these files: 

solaris26addonslo.bin
solaris26addonsL10N.bin

Refer to the Netra j 3.0 Installation Guide for un-archiving, installation, and upgrade instructions. During the installation or upgrade, you are asked which locale to configure the Netra j 3.0 server software, and which locale to configure the Netra j 3.0 client software to. Select the most appropriate locales.

Solaris 2.5.1 Year 2000 Compliance

To ensure year 2000 compliance of the Netra j 3.0 software when installed on a Solaris 2.5.1 system, you must install the Solaris Year 2000 Patch Cluster. This patch cluster is provided with the Netra j 3.0 software in the y2000/2.5.1_y2000 directory of the installation medium.

To Install the Y2000 Patch Cluster

  1. As superuser, open a shell window and change to the y2000/2.5.1_y2000 directory.

    If you downloaded the Netra j 3.0 software from the Web, type: 

    # cd /download_directory/y2000/2.5.1_y2000

    If you are installing the patch cluster from a CD, type: 

    # cd /cdrom/cdrom0/y2000/2.5.1_y2000

  2. Install the patch cluster using the installation script: 

    # ./install_cluster

Additional information regarding the patch cluster is provided in the y2000/2.5.1_y2000.README file.

Installation and Upgrade

Read this section for notes that describe situations which occur when you install or upgrade to the Netra j 3.0 software.

Console Message on Solaris 2.5.1 Systems

During the installation of or upgrade to Netra j 3.0 on a system running the Solaris 2.5.1 operating environment, you may see this message on the system console: 

Installation of <SUNWcache> was successful.
ld.so.1: /opt/SUNWscalr/lib/scalrd: fatal:
relocation error: symbol not found: __do_dyn_cast: referenced
in /opt/SUNWscalr/lib/scalrd scalrd not started, check
configuration

This message is displayed because the proxy cache services attempted to start before the software patches required by the proxy cache service software were installed. To resolve this error, perform the initial configuration and reboot the Netra j 3.0 server.

Upgrading From Netra i Software

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

Netscape Navigator Requirement

Systems upgrading from Netra i versions 3.1 and 3.2 must have the Netscape Navigator(TM) web browser installed to support the Netscape Enterprise Server and FireWall First! software.

File System Backup

When you upgrade from Netra i 3.1 to Netra j 3.0, the file system backup options set for Netra i 3.1 are lost after the upgrade. Have your system administrator restore the options for Netra j 3.0.

Administration Web Server User Password

The port 81 Administration Web Server user password is lost when upgrading to Netra j 3.0 from Netra i because the National Computer Security Association (NCSA) server is no longer used for Netra j administration. The Sun(TM) WebServer(TM) software 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.

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

Upgrade from Netra i 3.2 and 3.2.1

During the upgrade to the Netra j 3.0 software from Netra i 3.2 or Netra i 3.2.1, the following message may appear intermittently on the system console: 

ERROR: information for "SUNWenntr" was not found

This message does not signify any error condition which affects the upgrade to the Netra j 3.0 software and can be ignored.

Netra j 3.0 Administration Interface

Read this section for notes about the Netra j 3.0 configuration modules.

Logging in at the Server Console

The Netra j 3.0 Installation Guide states that the Netra j 3.0 system administrator must exit out of the windowing environment to log in as the setup user. This is incorrect. The administrator may log in as the setup user from a login window or from a web browser.

Proxy Cache Server Feature

The Proxy Cache Services chapter of the Netra j 3.0 Administrator's Guide describes a feature of the Netra j 3.0 software that prevents certain URLs relying upon the FTP protocol from being fetched through the proxy cache server. This feature is not enabled in this release.

Web Proxy

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

Using Java Web Server With a Netra j 3.0 Server

If you intend to use the Java(TM) Web Server(TM) 1.1 application as your default web server, it may not successfully establish itself as the default web server on port 80 when you boot the Netra j 3.0 server. Instead, the Sun WebServer (bundled with the Netra j 3.0 software) substitutes itself as the primary web server running on port 80. As a workaround, you must add a delay to the /etc/rc3.d/S95http script.

In the following example, the sleep instruction is added to the /etc/rc3.d/s95http script: 

case "$1" in
`start')
	sleep 5 
	if netstat -na | grep LISTEN | grep -w 80 >/dev/null
	then
			echo "$SCRIPT_NAME: httpd not started, port in use"
			exit 
			...
			...

This adjustment provides an adequate interval for the Java Web Server to initialize itself during the boot sequence and prevent the Sun WebServer from monopolizing port 80.

Router Address

The Netra j 3.0 Modify Global Parameters page lists "Router Address" as an optional field. However, in an environment where router discovery is not operational, this field is required. JavaStation computers do not use the routing daemon, routed, as a fallback, so the router entry is necessary if router discovery is not used.

File System Backup and Restore

Backing up user home directories with the Filesystem Backup and Restore module of the Netra j 3.0 administration interface works only for user home directories that reside under /export/home. To back up home directories residing elsewhere, you must specify their directory path in the blank field of the Directories section of the File System Backup Options or Immediate File System Backup pages.

Save and Restore Configuration

Restoring the Network Computer Server module also restores the Custom Client Application configurations of the Network Computer Application Management module. If there was no previous configuration, the present configuration is deleted. It is not possible to restore the custom client configurations separately. Before restoring the Network Computer Server module, record the configurations of the custom client applications. This is so that they can be properly re-configured after the restoration.

Software Management

The following notes are for installation and removal of software using the Software Management module of the Netra j 3.0 administration interface.

Software Installation

When the Software Management module of the Netra j 3.0 administration interface is used to install software patches, packages, or clusters, it notifies the web browser to reload the status page every 30 seconds during the process. If your browser does not appear to be reloading the page automatically, clicking on the reload button of the web browser achieves the same effect.

Software Removal

When the Netra j 3.0 Software Management module is used to remove software from the system, the Sun WebServer may time out. This results in one of the following error message from the browser.

For HotJava Browser: 

Exception: java.net.SocketException

For Netscape Navigator: 

500 server error

If this error occurs, make sure that the software component (package, patch, or cluster) was fully removed. The removal process may continue to run in the background after the browser returns with an error.

Make sure you remove software components one at a time, or use other utilities to remove these components.

Configuring Users' Home Directories

The home directories of user accounts set up for JavaStation users must be NFS(TM) shared. This requirement is handled automatically when users are added or modified using the Netra j 3.0 User Accounts module. Some user accounts may not be NFS shared if they existed prior to the Netra j 3.0 software installation or upgrade. To activate NFS sharing of such user accounts, follow these instructions:

To Activate NFS Sharing of Existing User Accounts

  1. As superuser, open the /etc/dfs/dfstab file in a text editor.

  2. For each user, add the following line to the /etc/dfs/dfstab file.

    share -F nfs -o rw -d "directory_description" /export/home/username

    Where directory_description is a description of the directory and /export/home/username is the user's home directory.

    If existing users all have a common home directory base, for example, /export/home, you can edit the /etc/dfs/dfstab file as follows:

    share -F nfs -o rw -d "directory_description" /export/home

Known Problems

Be aware of the following problems with the server software:

JavaStation Client Software

Read this section for notes pertaining to the software that runs on the JavaStation network computers.

Unsupported Features

The following features are described in the JavaStation Client Software Guide (PN 805-5890-10) but are not supported in the client software:

Updating the javaos Binary

After updating a new javaos binary to flash memory, the server automatically reboots the JavaStation, and the JavaStation may display the following error message: 

Can't open device.
Keyboard not present. Using ttya for input and output.

This error message may be displayed when the JavaOS software is first installed or after reboot when the user updates the operating system. This error message is from the OpenBoot(TM) PROM (OBP) and has no impact on how theJavaOS software functions.

European Union Currency Symbol

The JavaOS operating system that is provided with the Netra j 3.0 software has the symbol for the European Union Currency (Euro) already built in. To generate the Euro symbol, press the "Alt Graph" (AG) key and while holding this key down, press a second key according to your keyboard language. The following table lists the keyboard languages and their respective key combinations to generate the Euro symbol.

Table 1-1 Key Combinations to Generate the Euro Symbol

Language 

Key Combination 

Language 

Key Combination 

Czech 

Danish 

Estonian 

French 

German 

Greek 

Hungarian 

Italian 

Latvian 

Lithuanian 

Netherlands 

AG + e 

AG + 5 or AG + e 

AG + 5 

AG + e 

AG + e 

AG + Epsilon or AG + 5 

AG + u 

AG + 5 

AG + 4 

AG + e 

AG + e 

Norwegian 

Polish 

Portuguese 

Slovakian 

Spanish 

Swedish 

Swiss-French 

Swiss-German 

Turkish 

UK 

USIntl 

AG + 5 or AG + e 

AG + u 

AG + 5 or AG + e 

AG + e 

AG + 5 or AG + e 

AG + 5 or AG + e 

AG + e 

AG + e 

AG + e 

AG + 4 

AG + 5 

Developer Documentation

Information on Application Programming Interfaces (APIs) for developers building applications to run on JavaOS are posted at:

http://www.sun.com/javastation

Known Problems

Be aware of the following problems with the client software: