In order to compile Java programs you will need the Java development Kit (JDK 1.0.2), or it's equivalent. As of this writing the JDK is available on a number of platforms, including Solaris, Windows 95, Windows NT, MacOS, HP-UX, Linux, AIX, and OS/2 from different sources. You could also use one of a number of Java development tools e.g. Symantec Cafe, MS Visual J++, etc. which provide the functionality of the JDK.
In order to run Java programs, you will require a Java runtime environment (virtual machine). This is available in the JDK and equivalents, as well as in many web browsers like Netscape and Internet Explorer 3.0.
If you run your program in a web browser, you will have to make it an applet, as opposed to an application. That in effect defines the difference betwen an applet and an application. To run Java applications, you need a Java virtual machine outside the browser. Applets run in the browser, and are also more suitable for loading from the network via web servers.
The best performance is got with having all your Java classes on the system you're running the applet on. If you have a fast network to your web server, it may not matter too much for performance. When loading from the net, however, you'll have to deal with security restrictions on applets in the web browser due to the Java security model.
The applet loaded from the web server is not allowed to talk to any other system but the web server. This creates a problem when you want to talk to SNMP agents on other systems.
The Advent Network Management SNMP Applet Server (SAS) is a Java application that runs on your Web server and acts as a passthrough for applets using the SNMP package that are loaded from the Web server. To invoke this program you will need a Java runtime at a minimum. The SAS page describes how to invoke this server.
If you plan to load applets via the network from a Web Server (applet host), you will likely need the JDK on your Web server. Or, at least you will need a Java runtime on your Web server to run SAS and communicate with SNMP peers. The exceptions are if you have security on your browser or appletviewer disabled, or you have the classes local.
There are some situations where you will need to load classes over the network for an applet using the SNMP Package. You may find yourself in situations where you cannot or will not support keeping Java class files on all the systems that will use a particular applet. For example, you may want to access the applets from your home PC that does not have the applet classes.
One possibility is to use appletviewer or a browser that allows you to turn off security, so you can network load classes, as well as use SNMP communication without restriction. However, that may be a security risk in your environment, and may not be desirable. In such cases you can use the SNMP Applet Server (SAS) to provide a passthrough for your SNMP packets.
If you have the need to load classes over the network for an SNMP application, and use SAS, you would first need to invoke SAS on your Web Server. Since SAS is a Java application, you will need the JDK on your Web Server to run it.
The following steps list what needs to be done.
The FAQ and mailing list are potential sources for solutions to any problems your run into with installing and using the package or MIB browser. Write to us or use this bug-report form if you still have a problem.