These acronyms are used throughout this document for the SNMP Agent Plug-in.
Java Management Extension. Supplies tools for managing and monitoring applications, system objects, devices, and service-oriented networks. This API allows Java classes to be dynamically constructed and changed. UAF is implemented using JMX.
Management Information Base. A formal description of a set of objects that can be managed using SNMP. MIB-I refers to the initial MIB definition, and MIB-II refers to the current definition. There are MIB extensions for each set of related management entities, such as the RDBMS-MIB, which defines SNMP tables that provide information about managed database servers and their databases, and APPLICATION-MIBs, which provide general purpose attributes for each database server. Standard MIBs can be extended to include proprietary objects.
Tabular Data Stream™. Open Clients and Open Servers exchange information using this application protocol. All applications built using the Sybase Open Client libraries are also TDS applications, because the Open Client libraries handle the TDS interface. However, some applications, such as jConnect, are TDS applications even though they do not use the Open Client libraries—they communicate directly using TDS protocol.
Unified Agent Framework™. A JMX-based, service-oriented agent framework. It reduces the cost of developing a distributed agent by providing common services and interfaces for SNMP Agent Plug-in development and deployment. UAF includes the agent server, an agent framework library (both server and client APIs) and sample SNMP Agent Plug-ins.
User-based Security Model. The Simple Network Management Protocol (SNMPv3) that defines the process for providing SNMP message-level security. USM includes an MIB to remotely monitor and manage the configuration parameters for this Security Model. The USM provides authentication for an SNMPv3 protocol.
View-based Access Control Model. The SNMPv3 that defines the process for controlling access to management information. It includes an MIB to remotely manage the configuration parameters for the VACM. While the USM provides authentication, the VACM provides authorization for an SNMPv3 protocol.
