test

Netra j 2.0 Administrator's Guide

HotJava Views

This section lists some of the known problems with the HotJava Views software.

General

CalendarView

CalendarView works best with the CDE calendar server. The feature of storing mail messages with appointments is available only for data version 4 format calendars. This format is supported by the CDE calendar server. The OpenWindows calendar server does not support data version 4 format.

MailView

HotJava Views Administration

Use of the HotJava Views Administration facility requires a fully JDK 1.1-compliant browser. Both HotJava Views 1.1 WebView and HotJava Browser 1.1 (currently in beta) are JDK 1.1-compliant. Other browsers may not yet be fully JDK 1.1-compliant. For example, Netscape Navigator Version 3.x supports only JDK 1.0.2 and Netscape Navigator Version 4.x supports only a subset of JDK 1.1.

The administration facility is applicable only when configuring HotJava Views installed on the HTTP server that is used to deliver Views applets and configuration files.

Tips

General

CalendarView

You can use the /usr/dt/bin/sdtcm_convert calendar conversion utility to convert data version 3 calendars to data version 4 format. Refer to the sdtcm_convert man page for details.

NameView

And uncomment the line: 

# $JAVA_HOME/bin/java sunw.jdt.dex.server.Namesvc [boxv  ] tee /tmp dex.last

If you perform a search and this file doesn't get created or updated, then chances are your httpd server is having problems launching the cgi-bin script. If the output in the file indicates some type of error: 

Content-type: text/plain
<DBError>:6

then the database probably couldn't be found or the permissions on the file are not set correctly. Make sure the database files have read access for world.

Enabling Error Message Logging

This release of HotJava Views has an error message logging capability that is used most extensively by NameView. If you want to enable this capability, use the following procedure on the system running your web server.

  1. Assuming you have installed HotJava Views in /opt/SUNWjdt, make a symbolic link called jdt from within your httpd server's cgi-bin directory (this location will vary among servers) to /opt/SUNWjdt/cgi-bin.

    For example, if you are running the Apache server, you can use the following commands: 

    # pwd
# /opt/WWW/Apache/httpd/cgi-bin Your
httpd server's cgi-bin dir
# ln -s /opt/SUNWjdt/cgi-bin ./jdt
# ls jdt
# getidsvc.2.0   jdtlogsvc  namesvc.2.0

  2. Some web servers require that you explicitly turn on cgi-bin support before cgi-bin scripts can be executed. Refer to your httpd server's documentation to determine your server's requirements.

  3. Edit the /etc/syslog.conf file and add the following line: 

    # local0.info		/var/opt/SUNWjdt/jdt.log

    Make sure that you use tabs, not the spaces between the values.

  4. Create /var/opt/SUNWjdt/jdt.log and modify its permissions: 

    # mkdir /var/opt/SUNWjdt
# touch /var/opt/SUNWjdt/jdt.log
# chmod 666 /var/opt/SUNWjdt/jdt.log

  5. Restart the syslog daemon: 

    # kill -HUP `cat /etc/syslog.pid

    HotJava Views uses CGI to send error messages to the jdtlogsvc script on your web server. The jdtlogsvc script uses syslog to log the errors.

Troubleshooting

Table D-4 HotJava Views Error Messagesand Suggested Actions

Message/ Problem 

Action 

JavaOS 1.1 boots OK, but upon login, the heap viewer applet displays instead of Views. 

The alternate main parameters are not getting passed to JavaOS. Make sure you have specified the correct URL in the -i option in /var/dhcp/dhcptab. Use a web browser to verify the URL.

Make sure the javaos.mainProgram, javaos.mainZip and javaos.mainHomeprop parameters are correctly specified in the javaosopt.txt file. Use the -i URL indirection.

Make sure you have sent a SIGHUP to in.dhcpd if you have changed the /var/dhcp/dhcptab file.

JavaOS 1.1 boots OK, but upon login, a blue screen displays instead of Views. 

JavaOS has received the alternate main parameters, but they are incorrect. Make sure javaos.mainProgram and javaos.mainZip are specified correctly in the javaosopt.txt file. Verify the URLs are correct by using a web browser.

class not found/defined error

This error is common if you are using the JavaServer(TM) server. Servers may fail to handle HTTP requests. If this happens when Views is trying to load a class file, you get a class not found/defined error.

Try using the Apache or Netscape server to correct this problem.  

Tables do not parse well in WebView. 

The .jdt/props/selector.props files may contain invalid entries for class names that handle HTML tags.

Check your selector.props file for entries that specify classes that start with sun.hotjava . If you find such entries, move your .jdt/props/selector.props file aside (don't forget to reset your proxies).

After modifying Appointment Reminder properties within the 

Properties dialog, the appointment reminder types (Post Notice and /or Ring Bell) do not match the property value settings. 

Restart Selector for the new property setting to take effect. 

Several (or many) reminders are posted for a single appointment. 

Chances are your calendar file is in an older format, and/or your workstation has a different time than your calendar server. Update your calendar file and sync your workstation clock with the server's clock. 

No reminders are displayed for appointments inserted through Month view. 

After inserting appointments in Month view, perform an action that reloads your calendar, such as changing the month you're viewing or switching to Day view or Week view. 

Closing the Mail Login dialog in Calendarview can cause HotJava Views to lock up. 

Don't close the Mail Login dialog using the window menu. Use the Login and Cancel buttons to close the dialog. 

HotJava Views complains about not being able to mount my home directory. 

JavaOS mounts your home directory when you log in. It gets the location of your home directory from the passwd and auto.home NIS maps. Make sure these maps are correct and that your home directory is properly exported so the JavaStation can mount it.

You can run snoop(1M) and watch for the MOUNT request that happens after you log into JavaOS.

snoop(1M) doesn't show all the packets from the JavaStation.

You may be on a switched network. In this case, packets from the JavaStation may not be visible to the system on which you are running snoop.

The best way to make sure you see all packets is to plug the JavaStation and your Solaris system into a mini-hub and run snoop etherid for javastation.

Table D-5 describes HotJava Views error messages and known problems.

nown problems.