Managing the networked world with Java

JMAPI provides universal framework for network management tools

By Rawn Shah, JavaWorld.com, 11/01/96

Network management has always seemed an arcane and mystical job of the few and the brave. Even with important standards such as SNMP (simple network management protocol) and the RMON (remote monitoring) specification, it still takes a lot of training and even more practical experience to become even the least bit proficient. And expertise with one network management and monitoring package may not easily transfer to other packages.

The future is bright, however. If I said "Java to the Rescue" one more time, would you save slapping your forehead in exasperation until after you have read this issue? Although it does seem that the marketing spin doctors of the Java industry are heralding it as the pill for all ailments, this time they may be correct.

In continuation of our coverage of the Java APIs, we now bring on the noise about the Java Management API, or as some call it, JMAPI. Unlike the actual protocol standards SNMP and RMON, which deal directly with communicating with network hardware and software in a uniform way, JMAPI is concerned only with creating a common interface for accessing network information through these and other network protocols.

Components

JMAPI provides programming support for the following features and services:

User Interface Style
Administrative View Module (AVM)
Base Object Interfaces
Managed Container Interfaces
Managed Notification Interfaces
Managed Data Interfaces
Managed Protocol Interfaces
SNMP Interfaces
Applet Integration Interfaces

These components provide the overall structure for creating managed network environment of heterogeneous computer systems. They do not include specific objects, or protocol and system services specific to each type of device to be managed. This is, of course, going to be the responsibility of network equipment vendors.

Although the APIs do not impose a specific graphical view on the Java applet or application developed with JMAPI, there are style guidelines that can help. The User Interface Style guide addresses the issue of how to develop Web-based software using Java, something not all programmers are familiar with.

The AVM is a set of classes that help rapid development of a user interface for the JMAPI software. It is an extension of the current Abstract Window Toolkit (AWT) used by all Java applets. It provides support for making toolbars, multicolumn lists, tables, a help system, buttons, graphs, charts, property charts, etc. Some of these features may appear in future versions of AWT as well.

The Base Object Interface is a description of a distributed network object or service that spans the entire enterprise environment. It can be used to create a very basic object description of a router or Ethernet switch, for example. These can be further sub-classed to create more specific objects like a Cisco 1005 router object.

The Managed Container Interface allows objects to act as a group across the network. This allows you to classify groups of similar or disparate objects as distinct parts of your network. For example, you can use this to classify all types of routers irrespective of whether it's a small 3Com OfficeConnect Remote or a massive Cisco 7500.

1 | 2 | 3 | 4 | Next >