snmpc thumb1

  • SNMPc Programming Interface

    • AGNEKO SNMPc architecture uses a simple DLL based API that provides complete distributed management capabilities to any application. This API has a small number of common functions that operate on instances of object classes. Each object has a set of attributes that you can read and modify.

      Object classes map onto functional groups, including Session, Map, Log, SNMP, MIB, Event Filter, Custom Menus, and others. Classes also exist for creating high level objects such as map views, log views, MIB tables, and MIB graphs.

      You can easily create programs that run as Polling Agent, Server, or Console components.

  • Custom Scripting Support

    • AGNEKO SNMPc includes a number of utilities that can be used from any scripting language to develop script based applications. The use of scripting instead of a full programming language can greatly simplify development of custom application suites and integration with existing management environments. Custom scripts can be executed on trap reception, when you double-click a map icon, from custom menus, and as custom polling applications. Scripting commands perform a variety of common functions such as device SNMP operations, and the query and configuration of SNMPc Enterprise map data. The source files for all custom scripting commands are included with SNMPc.
  • WinSNMP Programming Interface

    • AGNEKO SNMPc supports the WinSNMP de-facto standard API for SNMP based programming under Windows. SNMPc Enterprise includes a runtime DLL and trap receiving program, as well as the include files, libraries and documentation required to develop WinSNMP applications.
  • DDE Programming Interface

    • AGNEKO SNMPc also supports a DDE based API. You can use this API from Visual Basic programs and from many standard Windows programs such as Microsoft Excel. Commands can query the Map and Mib databases, perform low-level MIB operations, download MIB tables, and execute SNMPc Enterprise commands. HubView and BitView were both developed using the DDE API.