Significance of JMAPI

JMAPI is a set of extensible objects and methods for the development of seamless system, network, and service management solutions for heterogeneous networks. This core set of application programming interfaces (API) can be used across a diverse array of computing environments involving numerous operating systems, architectures, and network protocols, enabling the development of low maintenance, heterogeneous software from a single source. JMAPI provides the user interface guidelines, Java classes, and specifications for developing seamlessly integrated system, network, and service management applications.

JMAPI provides a universal framework for network management tools that can be accessed over the World Wide Web. 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. JMAPI provides programming support for the following features and services:

User Interface Style Guide. 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 Java/Web-based user interfaces that conform to the JMAPI standard for integrated management applications—something not all programmers are familiar with.

Administrative View Module. Administrative View Module (AVM) is an extension of the Java Abstract Window Toolkit (AWT) for rapidly developing user interfaces (UI) for distributed management applications. It provides a set of components for building sophisticated graphical user interfaces, including image buttons, multicolumn lists, scrolling windows and panels, state button, toolbar, image canvas, convenience dialogs, and busy tool. There are also power components that enable developers to quickly build complex applications. These components include tables; hierarchy browser; and charts, graphs, and meters.

Base Object Interfaces. Base Object Interfaces support the construction of objects that represent distributed resources and services that comprise the enterprise environment. These interfaces can be used to create a very basic object description of a router, hub, or switch, for example. These can be further subclassed to create more specific objects such as a Bay Networks BayStack Access Node router, a 3Com SuperStack II Entry Hub, or a GDC APEX ATM switch.

Managed Container Interfaces. Managed Container Interfaces allow management applications to perform actions on a single group of managed objects, instead of each instance of an object separately. This permits management applications to scale upwards by allowing for multiple instances to be treated as one. For example, all types of routers—from a small 3Com OfficeConnect remote access router to the high-end Cisco 7500 multiprotocol router—can be classified as "routers" for the purpose of performing the same action on all of the devices simultaneously.

Managed Notification Interfaces. Managed Notification Interfaces provide the basic foundation from which more complex event management services can be built more easily. The model provides asynchronous event notification between managed objects or management applications. Event messages can be sent to a specified database or management station.

Managed Data Interfaces. Managed Data Interfaces support mapping classes and instances of the Base Objects to a relational database. These interfaces are implemented on the appropriate subset of the Java Database Connectivity (JDBC) specification. This allows the management system to store all state information about each of the objects across the network in a standardized database format for interaction with other applications. These interfaces also support a number of commercially available relational database engines.

Managed Protocol Interfaces. By itself, SNMP version 1 offers no security. JMAPI's Managed Protocol Interfaces implement classes that provide the infrastructure to perform distributed operations securely. These interfaces are built on existing Java interfaces for both security and distribution, providing methods for the secure transmission of management information across the enterprise network. The security system is based upon the Java Security API.

SNMP Interfaces. SNMP Interfaces extend the Managed Protocol Interfaces to allow extensions of the Base Objects to contain information obtained from existing SNMP agents. SNMP is the most prevalent management protocol—JMAPI is immediately useful for supporting SNMP agents, including those for RMON.

Applet Integration Interfaces. Applet Integration Interfaces allow application developers to seamlessly integrate their Java applets into the Java Management API. Developers can also choose an appropriate level of integration for their applets. These levels include: registered applets, registered management pages, and registered links.

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

SNMP and Java

Although not a protocol, the Java Management API (JMAPI) includes a mapping to SNMP, enabling SNMP-enabled devices to be managed by JMAPI-compliant applications. JMAPI itself is only a framework for management systems. The protocol or standard supported can actually be anything, even RMON, as long as JMAPI includes the appropriate mappings. Sun has indicated that future mappings could include Common Object Request Broker Architecture (CORBA) and Common Management Information Protocol (CMIP).

One vendor offering an implementation of Java classes for SNMP Version 1 is Advent Network Management, Inc. The company's Advent Java SNMP Package helps programmers develop SNMP applets and applications. With the package, developers can focus on using the Web and Java with the Advent Web NMS framework, and produce the best applications and solutions, instead of dealing with multiple proprietary platform vendor APIs and multiple operating system versions.

The Advent Java SNMP Package is a group of Java class files that provide Java programmers a simple API for developing network management applets and applications that use SNMP version 1. Many different architectures are supported, such that SNMP can be used in the Web browser, on the server, or even on managed elements that have a Java Virtual Machine. Applets developed using this package can be loaded from the network or from local disks and run in any Java-enabled browser.

Java applets that are loaded from the network are usually restricted by browsers from connecting to any system other than the applet host. The Advent Java SNMP Package provides special support for applets loaded remotely via the network that run in browsers that have socket and file access restrictions. Via a Java program called the SNMP Applet Server (SAS) on the applet host (Web Server), applets can communicate with SNMP managed devices, and save and retrieve files on the applet host.

Developers can also use the Advent NetMonitor SNMP Applet Builder, which uses the SNMP Package libraries to communicate with SNMP agents. Advent NetMonitor lets developers visually build these applets without writing code. They can then use Java to add their own event handling code and components.

The company also offers a Management Information Base (MIB) Browser Applet (Figure 1). MIB Browsers allow the user to view and operate on data available through an SNMP agent on a managed device, such as a router. To get a better view of the data available on the SNMP agent, a MIB file is usually provided with the managed device. This MIB file contains a description of the object hierarchy on the managed device, as well as the syntax and access privileges for each variable in the MIB.

Figure 1: Shown here is the primary window of the MIB browser applet. (Although the screen is taken from Windows 95, it looks similar in Netscape and on other Java-enabled browsers.) The applet includes fields for community, SNMP agent name or address (Host), value used for a set request, the current Node OID that is being operated upon, a chooser for the current MIB module, a list of children of the current node, and a text area to view query results. The operations allowed with the MIB browser are available through the series of buttons at the bottom of the applet's main window.

Figure 1: Shown here is the primary window of the MIB browser applet. (Although the screen is taken from Windows 95, it looks similar in Netscape and on other Java-enabled browsers.) The applet includes fields for community, SNMP agent name or address (Host), value used for a set request, the current Node OID that is being operated upon, a chooser for the current MIB module, a list of children of the current node, and a text area to view query results. The operations allowed with the MIB browser are available through the series of buttons at the bottom of the applet's main window.

The Advent MIB Browser applet provides the capability to load and view multiple MIB modules, and traverse the MIB tree to look at the definitions for each node in the MIB tree. It allows the use of SNMP's get, getnext, and set requests to a particular variable in the MIB of an SNMP managed device. It also enables multiple real-time graphs of data on the managed device to be viewed as it changes over time. It also allows the user to view SNMP tables.

The major NMS platform providers are planning to support Java. IBM subsidiary, Tivoli Systems, for example, plans to evolve its TME 10 framework into a Java-based architecture by mid-1998. The architecture will support JMAPI for enabling Java management applications to take advantage of the platform's back-end functions, such as event and alarm correlation and data management. Computer Associates plans to add the ability to control its Unicenter TNG management functions from a Web browser as well as the ability for Java applications to invoke its functions. Unicenter TNG is the company's object-oriented enterprise management framework.

Components of WBM | Web-Based Management

Components for WBM can be written in any language, including HyperText Markup Language (HTML), Common Gateway Interface (CGI) scripts, and Java.

HTML provides a standardized way to create pages of Web-based information and embed hyperlinks that lead the user to other pages. While HTML pages are usually static and textual, they can be made interactive by embedding graphics and active elements, such as Java applets and CGI applications, within the page. HTML is the ideal tool for displaying tables, such as network inventory details and IP address listings.

CGI is not a language: it is a protocol used to access database information. For example, a WBM application may need to display the current number of incomplete work orders. This data could be stored in the database of a proxy workstation. A CGI application written in Java or Perl can be used to query the database and format an HTML page to display the information.

Java is rapidly emerging as an important tool for managing an intranet through a WBM system. Java is an interpretive programming language. Java code is not compiled before run time but is interpreted by a Java Virtual Machine (JVM) at run time. JVMs are available for many processor environments and are included with some Web browsers, such as Netscape Navigator and Microsoft Internet Explorer, enabling these browsers to execute Java code.

While Java can be used to build standalone applications and does not have to be scripted for Web-accessible applications, the importance of Java for Web-based management systems is its built-in Web-enabled capabilities. Applets, self-contained Java programs, are sent from the server to a browser-equipped client where they are run locally (Figure 1). Other CGI scripting languages such as Perl, another popular language used for Web-based applications development, run on the server. The back and forth nature of Perl has the drawback of consuming processing resources and network bandwidth, which can inhibit the application's performance.

Figure 1: Java applets work in one direction: server to client.

Applets have browser-imposed security restraints that limit access to network resources and prevent access to local system resources, such as memory and disk. Thus, applets can be run on the receiving machine with minimal risk while ensuring network security.

Java applets, which can be served from both proxy and embedded Web-server WBM implementations, can be used for:

§  Displaying dynamic graphs that interpret network operations

§  Illustrating complex situations, such as interactive views of chassis hubs or modules of a stackable hub

§  Displaying real-time data that are updated from polling and traps

§  Adding graphics, including animation

Because Java can produce applications that are portable across Unix, Windows, and other environments, a JVM can be embedded in an end device and the device agent can then execute Java code. This capability enables code to be ported across other devices with JVMs. A key facet of this capability is that the code can be distributed dynamically, ported from a management proxy to devices, and ported between devices or components within a device (Figure 2).

Figure 2: An embedded agent with a Java Virtual Machine.

The use of Java within an embedded agent can increase management capabilities by enforcing policy-based management or security rules. For example, assume that an administrator wants to enable remote network access between 6:00 a.m. and 6:00 p.m. Traditional methods, such as SNMP sets, have been used to enforce such restrictions but at the cost of increasing network traffic and with the difficulty of scaling to handle thousands of devices. While a device-resident agent could perform this function, agent releases are typically infrequent. An embedded agent with a JVM could independently create the scheduling routine and dynamically distribute the policy to restricted devices, bypassing the need for an agent release.

Applications | Web-Based Management

There are three fundamental applications where Web-based tools can provide a significant benefit: individual device configuration and management, browser access to sophisticated management applications, and corporate IS access to network status data.

Device configuration

The capability of configurating and managing individual devices via a Web browser is aimed at managers of small networks who may not have their own network management system. These users want to configure and monitor the devices on their networks as easily as possible, and perhaps even gain some remote device management capabilities as well.

This can be accomplished by providing the equipment to be configured with an agent that includes a native HTML interface. The manager then enters basic configuration parameters for each device by completing a simple online electronic form. Remote monitoring of simple device statistics is also possible via the browser, using tabular and graphical displays of basic device information and performance.

Advanced NMS capabilities

Web-based access to advanced, network-wide management functions is an application targeted at enterprise network support staffs who already use network management systems. Their goal is to monitor the network, understand potential faults and alarms, and provide their users with continuous network availability. Network management solutions working in conjunction with popular platforms like Hewlett-Packard's OpenView, provide the foundation for these networks. Building on this foundation, Web browsers provide several low-cost options for easily accessing important information. For example, a staff member out on the manufacturing floor troubleshooting a network segment may need to access a particular management application. Through a Web browser running on any PC or laptop in the organization, the user could access the necessary functionality and continue the troubleshooting process, regardless of their location—saving time and effort.

Network status data

Web reporting of network status information for access by IS management and others via the organization's intranet is aimed at those who do not necessarily operate the network nor get involved in extremely technical detail. Instead, their goal is to quickly obtain information about the state of the network, review trends over time, and receive notification of any potential trouble spots.

Various people within an organization have different needs for different types of information. The Web can be used for distributing this type of information to people who do not have ready access to traditional management systems. Members of the finance group, for instance, may need usage accounting information, while database users may need to determine system status or submit an online trouble ticket and follow it through to resolution.

The convenience of Web management is very appealing. A Web-based management tool is easier to use than the command-line interfaces of Unix systems. It is geographically independent and can be used from any notebook, desktop PC, or workstation with a browser to access network information. This also means network planners, designers, and managers do not have to load specialized client software on their portable computers. With a Web browser, they can access the network at any time—in any building, while traveling, or even at home.

Web-based management offers several other benefits. In being able to access performance data and implement routine management tasks over the Web, companies with global networks do not have to distribute management platforms to every remote site. The Web's ubiquity also has the potential to reduce the cost of managing transmission facilities and services by eliminating the need for proprietary, high-priced equipment offered by carriers.