Q: Do I need to run both the Client and the Server?
A:No. The client is the only application needed to join a session. However, if you wish to host or create a session you will need to invoke the server.
Q: Is there a limit to the number of users that can effectively collaborate?
A:Yes and no. We have not imposed a limit but we're sure there is an upper limit that is dependent on system hardware and network connectivity. We have successfully tested Habanero in a lab of 22 systems running Windows NT.
Q: Which operating systems are supported?
A: NCSA Habanero was written in Java and is theoretically platform independent. However, Habanero is dependent on a Java Virtual Machine (VM) and thus it is restricted to systems that support the Java VM.
We've been using the Sun JDK for development and testing and we are confident in its performance under Solaris and Windows. We have tested the Macintosh MRJ v1.5 and despite a couple of window sizing and repainting bugs, Habanero works. We have also tested Habanero on SGI and HP systems with their respective VMs and everything seems to run fine. For more information about obtaining a Java VM see our release page.
Another consideration when running Habanero is the fact that some applications are dependent on the use of native libraries. This adds another limit to platform independence because the native libraries must be compiled for each platform. Native libraries are required for the Audio Chat and the HDF tools and to date we do not have a Macintosh implementation of these libraries. If a native library exists for your platform you can find it in the \rsc\lib directory. In general, we compile and test native libraries for Solaris and Windows systems.
Q: I've installed Habanero and it doesn't work. What should I do?
A: The habanero.home property in the users.props file of your habanero.rsc directory is mis-defined or it needs to be defined. Using an ASCII editor, define the directory path to the Habanero files. For example:
UNIX habanero.home=/java/habanero/ristra Windows habanero.home=c:\\habanero\\ristra Macintosh no editing required 8^)NOTE: Windows uses a backslash to define directory paths and Java uses a backslash to define an escape character. Thus, two backslashes are required when defining a Windows path to Java.
Q: Why do applets no longer work in Netscape after I installed Habanero on my UNIX system.
A: The Netscape client defines an internal CLASSPATH and if a CLASSPATH is defined in the .cshrc, it will override the Netscape default. As a result, applets do not run in Netscape. The easiest solution is to use a script to set the environment variables and invoke either Netscape or Habanero. For example, create a script for Netscape:
ns, with the following two lines:
setenv CLASSPATH
netscape
ns to invoke Netscape.
This script overwrites the current CLASSPATH setting it to NULL. Now when Netscape is invoked, it uses it's internally defined CLASSPATH.
Q: Why can't I join session or replay a session from a web page through Netscape on Windows?
A: Netscape references it's own internally defined helper application list before it uses the system's list. Chances are the reference in Netscape are out-of-date. Solution: Delete the Habanero references in the Netscape helper application list and restart Netscape. The next time you click on a session link or replay link, Netscape will use the system's list of applications which will point to current version of Habanero.
Q: What should I do when Windows 95 gives me system out of memory errors?
A: Windows 95 Users ONLY Due to a problem with the way Windows 95 allocates the initial environment memory, you will have to edit the properties file for the Habanero Client, Server and Replay Editor. The "Initial Environment" memory property needs to be changed from 'Auto' to '4096'. Changing this property involves:
|
Q: Are there limitations while running Habanero under Windows 95?
A:Unfortunately, Windows 95 has a 64 socket limit and your system may run out of sockets if you host a server and client on one system. The solutions include:
Q: How do I configure Habanero to run with the JRE?
A: It is possible to run Habanero using the JRE under UNIX and Windows. Macintosh users are not affected by the differences between the JDK and JRE. Using the JRE requires you to create a script or a batch file defining the PATH to the jre, invoking the jre using the "-cp" switch including the required paths and the calling the proper class name. The format is:
PATH=<the_path_to_jre> jre -cp <required_class_paths> <required_properties> <class_name>
required class paths include:
Habanero2.0
Habanero2.0\apps
Habanero2.0\rsc\jars\voyager.jar
Habanero2.0\rsc\jars\jgl3.1.0.jar
Habanero2.0\rsc\jars\swingall.jar
Habanero2.0\rsc\jars\x509v1.jar
required properties affect Windows. Under Windows you will need to define the location of your habanero.rsc directory using the user.home property. For Example: -Duser.home="c:\Program Files\NCSA\Habanero2.0
class name are either Habanero for the client or HabaneroServer for the server.
NOTE: Libraries normally defined in the LD_LIBRARY_PATH get added to the path statement under Windows.
SET PATH=C:\Program Files\NCSA\Habanero2.0\jre\bin;C:\Program Files\NCSA\Habanero2.0\rsc\lib\w95;
jre -cp "C:\Program Files\NCSA\Habanero2.0";"C:\Program Files\NCSA\Habanero2.0\apps";"C:\Program Files\NCSA\Habanero2.0\rsc\jars\voyager.jar";"C:\Program Files\NCSA\Habanero2.0\rsc\jars\jgl3.1.0.jar";"C:\Program Files\NCSA\Habanero2.0\rsc\jars\swingall.jar";"C:\Program Files\NCSA\Habanero2.0\rsc\jars\x509v1.jar" -Duser.home="c:\Program Files\NCSA\Habanero2.0" Habanero
An Example of UNIX ksh Script
#!/bin/ksh
PATH=$PATH:/java/sun/jdk1.1.6/jre/bin
LD_LIBRARY_PATH=/java/habanero/2.0/rsc/lib/Solaris:$LD_LIBRARY_PATH
jre -cp /java/habanero/Habanero2.0:/java/habanero/Habanero2.0/apps:/java/habanero/Habanero2.0/rsc/jars/voyager.jar:/java/habanero/Habanero2.0/rsc/jars/jgl3.1.0.jar:/java/habanero/Habanero2.0/rsc/jars/swingall.jar:/java/habanero/Habanero2.0/rsc/jars/x509v1.jar Habanero
Habanero® is a registered trademark owned by The Board of Trustees of the University of Illinois. Copyright 1996-1998. All rights reserved. Java(TM) is a proprietary trademark owned by Sun Microsystems, Inc.
The National Center for Supercomputing Applications
University of Illinois at Urbana-Champaign
Last modified: February 12, 1998