The following set of procedures outline what you need to do to run SCM in a HotJava browser.
You may need to determine if you have the correct version of the following:
If you choose to use the HotJava browser shipped with your Solaris 2.6 or 2.7 Operating System, there may be problem when using the menus, for example: after making your menu selection, the menu selection can remain visible on the browser. Refer to the Sun Cluster 2.2 Release Notes for complete information based on your software requirement needs.
JDK on the machine running the HotJava browser.
HotJava.
Refer to the Sun Cluster 2.2 Release Notes for complete information on software requirements.
You will need to determine whether you want to:
Run the HotJava browser on a cluster node.
If you choose this option, you will have to restart HotJava on a different node, when the node running HotJava crashes.
Install a web server on each node in the cluster for running SCM.
If you choose this option, you will need to type an appropriate URL for another node into the HotJava browser when you see the Lost Connection dialog.
Depending on what you decide, refer to the appropriate procedure.
Type the following from the console prompt on the server in your cluster:
java -version |
Refer to the Sun Cluster 2.2 Release Notes for complete information on software requirements.
From the machine running the HotJava browser, select About HotJava from the Help menu.
Refer to the Sun Cluster 2.2 Release Notes for complete information on software requirements.
Run your HotJava browser on a node in the cluster.
Remotely display it on an X windows workstation.
Set the applet security preferences in the HotJava browser:
Choose Applet Security from Preferences on the Edit menu.
Click Medium Security as the Default setting for Unsigned applets
When you are ready to begin monitoring the cluster with SCM, type the appropriate URL.
file:/opt/SUNWcluster/scmgr/index.html |
Click OK to dialog boxes that ask for permission to access certain files, ports, and so forth from the remote display workstation to the cluster node where the browser is started.
It may take HotJava some time to download and run the applet. No status information will appear during this time.
Refer to the online help for complete information on menu navigation, tasks, and reference.
If you choose, you can install a web server on the cluster nodes to run with SCM.
Install a web server that supports HTML 2.0 or later on all nodes in the cluster.
One option is Sun Web Server, which is available to download at http://www.sun.com/solaris/webserver.
If you are running the HA-HTTP service and an HTTP server on SCM, you need to configure the HTTP servers to listen on different ports. Otherwise there will be a port conflict between the two.
Follow the web server's configuration procedure to make sure that SCM's index.html file is accessible to the clients.
The client applet for SCM is in the index.html file in the /opt/SUNWcluster/scmgr directory.
For example, go to your HTTP server's document root and create a link to the /opt/SUNWcluster/scmgr directory.
Run your HotJava browser from your workstation.
Set the applet security preferences in the HotJava browser:
When you are ready to begin monitoring the cluster with SCM, type the appropriate URL.
http://cluster node/scmgr/index.html |
Click OK to dialog boxes that ask for permission to access certain files, ports, and so forth to the cluster node where the browser is started.
It may take HotJava some time to download and run the applet. No status information will appear during this time
Refer to the online help for complete information on menu navigation, tasks, and reference.