This section provides notes on the Netra j 2.0.1 software.
The Netra j software packages are not relocatable. Be sure that you have enough space in /opt, /usr, or /var file systems. Table 1-1 lists the approximate disk space requirements.
Table 1-1 Netra j Software Disk Space Requirements
File System |
Space in Mbytes |
---|---|
/ |
21 |
/opt |
83 |
/usr |
5 |
/var |
3 |
You must reboot the server after installing the Netra j 2.0.1 software and before you begin setup.
On page 18 of the Netra j 2.0 Installation Guide, under Initial Configuration, you are no longer required to complete steps 3 through 9. The Netra j 2.0.1 software will not display these configuration pages.
HotJava Views administration requires HotJava Browser for the Solaris operating environment. HotJava Browser 1.1 is included with the Netra j 2.0.1 software. For all other Netra j 2.0.1 administration tasks, any industry-standard browser can be used.
The HotJava Views administration applets use JDK(TM) 1.1 application program interfaces (APIs), including AWT 1.1 (abstract windowing toolkit) and the New Event Model. Therefore, HotJava Views administration requires a fully JDK 1.1-capable browser. As of this writing, HotJava Browser 1.1 for the Solaris operating environment is the only browser that supports AWT 1.1 and New Event Model features in JDK 1.1. Netscape Navigator(TM) 4.03 supports only a subset of JDK 1.1. If you prefer a Netscape browser, check the Netscape web site at http://devedge.netscape.com/software/index.html for the latest information about AWT 1.1 and New Event Model support.
Before configuring HotJava Views Client Administration, you must set preferences for applet security to Medium.
At the top of HotJava Browser, select Edit Preferences Applet Security.
Set signed applet security to Low, and set unsigned applet security to Medium.
Table 1-2 lists the Netra j software package additions to accommodate the high encryption and low encryption software.
Table 1-2 Netra j Software Additions
Current Package ID |
High-Encryption Package ID |
Low-Encryption Package ID |
---|---|---|
SUNWjsos |
SUNWjsosh |
SUNWjsosl |
The following documents for Netra j 2.0 support the Netra j 2.0.1 software.
Netra j 2.0 Installation Guide (805-3080-10)
Netra j 2.0 Administrtor's Guide (805-3076-10)
For updates to the Netra j 2.0 documentation, see "Netra j 2.0 Documentation Updates".
When the Netra j Software Management module is used to make additions to or removals from the system, the Sun(TM) WebServer(TM) may time out. This results in an error message from the browser.
Exception: java.net.SocketException
500 server error
If this error occurs, make sure that the software component (package, patch, or cluster) was fully installed or removed. The install or remove process may continue to run in the background after the browser returns with an error.
Make sure you either add or remove software components one at a time or use the admintool or pkgadd utility to add or remove these components.
When Lotus eSuite is installed on the Netra j server, the following error messages are reported:
Connection error Something went wrong while reading the document http://localhost:81/cgi-bin/uncgi/misc/sw-admin/cgi-bin/process_install.cgi?type=package Either the connection was closed prematurely or some other exception occurred Exception: java.net.SocketException Socket closed
However, observing the console window shows that the installation finishes successfully.
Some of the administration information that is entered using the Network Computer Administration forms is not automatically saved as part of the Netra j Save and Restore feature. The relevant system files must be saved manually if you intend to restore these settings after a system crash. The entire directory /var/dhcp should be saved to an off-line storage medium such as magnetic tape or diskette. It is recommended that the contents of this directory be backed up at regular intervals, particularly when new NC's have been added, deleted or modified using the Netra j user interface. These files must be restored separately in addition to the default restore procedures required during a crash recovery of a Netra j server.
The home directories of user accounts set up for JavaStation users must be NFS-shared. This requirement is handled automatically when users are added or modified using the Netra j User Accounts module. Some user accounts may not be NFS-shared if they existed prior to Netra j installation/upgrade. To activate NFS-sharing of such user accounts, follow the instructions below.
Become root.
Add the following line to the /etc/dfs/dfstab file for each user:
share -F nfs -o rw -d "Home Directory" /export/home/username
where /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 "Home Directory" /export/home
If you intend to use Java Web Server 1.1 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 server. Instead, the Sun WebServer (bundled with the Netra j 2.0.1 software) substitutes itself as the primary web server running on port 80. As a workaround, you must add sleep 5 to the script /etc/rc3.d/S95http.
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 WebServer to initialize itself during bootup and prevents Sun WebServer from monopolizing port 80.
Sending a SIGHUP to the DHCP server daemon causes the in.dhcpd file to reread its data during the idle interval, anywhere from 0-60 seconds. The moment the in.dhcpd file actually rereads its data during the idle interval depends on where the DHCP server is in its polling cycle. For busy servers, you should run /etc/init.d/dhcp stop then /etc/init.d/dhcp start to force the data to be reread.
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.