Cisco Cisco Configuration Engine 3.5 Entwickleranleitung
8-10
Cisco Configuration Engine Software Development Kit API Reference and Programmer Guide 3.5
OL-17661-02
Chapter 8 Creating Provisioning Solution
Creating Provisioning Solutions
Creating Provisioning Application for Non-Agent Enabled Devices
Using the DID API, create device objects and add hop information for the devices.
If using NSM, create device, group, application and event objects using the UI.
Write an application using the Event API to publish and subscribe events on the Event Bus. The devices
can be configured either using pull mode or push mode. The status of the configuration operation will
also be published on the event bus and can be processed by the application. The XML DTDs for the
configuration and status messages are documented in Chapter 7.
can be configured either using pull mode or push mode. The status of the configuration operation will
also be published on the event bus and can be processed by the application. The XML DTDs for the
configuration and status messages are documented in Chapter 7.
Figure 8-4
IMGW works in concert with the Event Gateway to reach legacy devices without a
built-in event agent
built-in event agent
The following sections describe the sequence of operations for initial and partial configuration using
Cisco Configuration Engine for agent-enabled devices. For the complete list of features offered by Cisco
Configuration Engine and their usage, please refer to the official Cisco Configuration Engine
documentation.
Cisco Configuration Engine for agent-enabled devices. For the complete list of features offered by Cisco
Configuration Engine and their usage, please refer to the official Cisco Configuration Engine
documentation.
75502
CNS
event API
Event
interface
Device
interface
SSH/
Telnet
Telnet
IMGW
Event
interface
Protocol
engine
Event
gateway
Event Bus (RVD/RVRD)
Provisioning App (runtime)
Legacy
devices
without
agents
Proprietary protocol/
TCP
TCP
Event
Agent
config
Agent
Devices with
agents