JavaStation Software Environment 1.0.1 for Developers Download Software Now Products
JavaStation |
Installing and Running the JavaStation Software Environment 1.0.1 for Developers3/31/97ContentsPrerequisitesPlease read this section before downloading and installing the JavaStation(TM) Software Environment 1.0.1 for Developers (JSE 1.0.1). DependenciesThe JavaStation Software Environment 1.0.1 for Developers (JSE 1.0.1) is bundled into a Solaris package called SUNWjdse, which is installed on a host system that "serves" JavaStation clients. SUNWjdse is dependent upon the following packages. Use the command pkginfo to determine if these packages are already installed on the host system. If you need one of these packages, click to download the package and add it before you install the SUNWjdse package (available below). SUNWdhcsr.tar - BOOTP/DHCP Server Services, (Root) SUNWdhcsu.tar - BOOTP/DHCP Server Services, (Usr) SUNWfns.tar - Federated Naming System Note: SUNWfns is part of the the standard Solaris 2.5/2.5.1 distribution and may already be installed on the host system. To download and extract a package:1. Click on the package name to download it. /tmp is a convenient directory to specifiy for downloading software from a browser. Once the package is installed, you will not need to keep a copy of the tar file. 2. Extract the package: # tar xf package_name.tar 3. Install the package using the pkgadd command: # pkgadd -d <directory where package is> <package name> You must be super-user to install a package. Note: When installing releases of JSE in the future, you will only need to upgrade the SUNWjdse package, since the SUNWdhcs* packages will not change.
A Note about DHCPThe JavaStation Software Environment for Developers (JSE 1.0.1) uses the DHCP (Dynamic Host Configuration Protocol) daemon to boot JavaStation clients. The use of this protocol should be transparent to most system administrators, unless the host machine on which SUNWjdse will be installed uses BOOTP to support hosts other than JavaStation clients.
If the host machine uses BOOTP to support hosts other
than JavaStation clients, the system administrator will need to add
the non-JavaStation client hosts to the DHCP databases. To do
so, consult the following man pages:
dhtadm(1m)
System administrators may also want to consult the following man pages
to become more familiar with DHCP:
in.dhcpd(1m) See the section below if you'd like to install these man pages on your system.
Note: If the host system uses a bootp server that was not installed from an early-access release of the SUNWjdse package and that server is started by an init script at the system's boot time, you need to disable that script since it will interfere with the DHCP services. To install the DHCP-related man pages on your system:1. Click on the tarfile Patches.tar to download it./tmp is a convenient directory to specifiy for downloading software from a browser. 2. Extract the tarfile: # tar xf Patches.tar 3. Change directories into the Patches directory: # cd Patches/iss_man_dhcp_sparc-01 and read the instructions in the file "Install.info" to install the man pages. 4. You'll probably want to install the Patches using the installpatch command: # ./installpatch .
Installing and Running the SoftwareThe JavaStation Software Environment 1.0.1 for Developers (JSE 1.0.1) is bundled into a Solaris package called SUNWjdse, which is installed on a host system that "serves" JavaStation clients. 1. Click to download SUNWjdse.tar.
Note: /tmp is a convenient directory to specifiy for downloading software from a browser. Once the package is installed, you will not need to keep a copy of the tar file. 2. Extract the SUNWjdse package:
# tar xf SUNWjdse.tar
Note: JSE 1.0.1 can only be installed on servers running the Solaris 2.5 or 2.5.1 operating environment. 3. Install the package: # pkgadd -d <directory where SUNWjdse is> SUNWjdse You must be super-user to install a package. By default, SUNWjdse is installed in the /opt directory. 4. Start the host manager:
# /opt/SUNWjdse/bin/jdhostmgr
Note: If an error message appears similar to: AUDIT: date: 478 X: client 23 rejected from local host in the console window, you may not be running the windowing system as root. One way to correct the problem is to exit super-user and type: % xhost +hostnamewhere hostname is the name of the host you're using. Then type the command to start the host manager again. Alternatively, you can use the xauth(1) command to permanently change the authorization information so root clients can attach to the X server. Or, run the windowing system as root to correct the problem.
The host manager interface is similar to the Solstice(TM) Launcher
host manager.
This dialog box only appears at startup if at least one of the fields has not been initialized. 5. Enter the default data. The Set Defaults dialog box appears the first time host manager is invoked. All fields must be filled in before you click OK or Apply:
DNS DOMAIN NAME - type the name of the DNS domain. For example, "eng.sun.com" DNS SERVER IP ADDRESS - type the IP address of the DNS server SUBNET MASK - type the IP address for the subnet mask. For example, "255.255.255.0"
ROUTER IP ADDRESS(*) - type the IP address of the router ("gateway"). To determine the router IP address, use the command netstat -nr. The "default" value is the router address. 6. Click OK. After applying changes, a "Defaults Update Pending" message is displayed in the lower right corner of the window. 7. Add the names, Ethernet addresses, and IP addresses of each JavaStation client. Select Edit -> Add... to add clients. You must specify a name, an IP address, and a corresponding hexadecimal Ethernet address for each JavaStation client.
Click Apply to add each client entry to the list of hosts.
Note: JavaStation clients are network-dependent devices; they require NIS and DNS naming and file services. Do not install a Java Desktop client on a network that does not provide support for NIS and DNS. For example, each JavaStation client needs an entry in the network host and map tables. Note: The Ethernet address is on a label on the bottom of the JavaStation system, or on a configuration sheet that was shipped with the system. Alternatively, you can power-on the JavaStation client (before configuring on the host system) and read the Ethernet address from the BootPROM banner. Although leading zeros appear in the screen display, they are not required when you enter Ethernet addresses for single-digit values (for example, typing "3" is equivalent to typing "03." When you add a client, a plus sign ("+") appears next to the client's host name to indicate that client is to be added, and the Total Changes Pending number is incremented. (Double-clicking on a pending addition (a hostname with a "+") displays the Add window.) For example:
8. After adding all names and addresses for each JavaStation client, select File -> Save Changes to save and write the changes to a file. Note that the plus signs are erased and the "Total Changes Pending" message resets to a "Configuration in Progress..." message. When the changes are saved, the message changes to "Configuration Succeeded." 9. Reboot (or power-on) the JavaStation client. To reboot the JavaStation client, turn the power off and then turn the power on again. Note: The JavaStation client may take up to 1 minute to boot. When booting is complete, a Login window is displayed. 10. Log into the JavaStation client machine. Because the JavaStation client uses NIS naming services, use your regular NIS username and password. After logging in, the HotJava browser is displayed.
Modifying or Deleting ClientsTo Change a Client's Ethernet Address:1. Select the client name from the list of available hosts.
2. Select Edit -> Modify to change the client's Ethernet address. 3. Type the new Ethernet address in the Ethernet Address field and click OK. A change bar ("|") appears next to the client's host name to indicate that a change was made, and the "Total Changes Pending" message is displayed. Note: To undo a modification, select the client and select Edit -> Revert. A warning pop-up window is displayed; click Revert to undo the modification. 4. Select File -> Save Changes to apply the change. The change bar is erased and the "Configuration Succeeded" message is displayed. 5. Reboot the modified JavaStation client. To Delete a Client:1. Select the client name from the list of available hosts. 2. Select Edit -> Delete. When you delete a client, a warning pop-up asks you to confirm the deletion. When you click Delete, a minus sign ("-") appears next to the client's host name to indicate the client will be deleted. The Total Changes Pending number is incremented. Note: To undo a deletion, select the client and select Edit -> Revert. A warning pop-up window is displayed; click Revert to undo the modification. 3. Select File -> Save Changes to delete the client. The client is removed from the list, and the "Configuration Succeeded" message is displayed. Note: You can delete more than one client at a time by clicking each additional client name.
Configuring PrintersConfigure printers for JavaStation clients in the following two ways:
Note: If your printer model is a Hewlett Packard J255xA JetDirect, the required version of firmware is A.04.09 or higher. The firmware can be obtained from http://www.hp.com/cposupport/indexes1/firmwars.html.
TroubleshootingIf a JavaStation client "hangs" or does not respond, rebooting the JavaStation client usually solves the problem. Capturing Log FilesTo retrieve log files of operating system activity from JavaStation clients that fail, type the following command on the server machine: # /opt/SUNWjdse/bin/snmptrapd -x /opt/SUNWjdse/bin/logdumper & If failures do occur, they will be saved in the /tmp directory of the server machine with the following unique file name: /tmp/javaos.log.<IP address of failed client>@<time in seconds since January 1, 1970> You can browse the log file to determine errors that may have caused a failure. Note: Not all JavaStation client failures will result in a log file creation on the server machine.
Error Messages
Where to Go For More InformationFor more information on getting started with the HotJava browser, frequently asked questions, and known bugs, see http://java.sun.com/HotJava/. |
Copyright 1996-1997 Sun Microsystems, Inc., 2550 Garcia Ave., Mtn. View, CA 94043-1100 USA. All rights reserved.