You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 11
Next »
Overview
eyJleHRTcnZJbnRlZ1R5cGUiOiIiLCJnQ2xpZW50SWQiOiIiLCJjcmVhdG9yTmFtZSI6IkhlcmJlcnQgRWlzZWx0Iiwib3V0cHV0VHlwZSI6ImJsb2NrIiwibGFzdE1vZGlmaWVyTmFtZSI6IkhlcmJlcnQgRWlzZWx0IiwibGFuZ3VhZ2UiOiJlbiIsImRpYWdyYW1EaXNwbGF5TmFtZSI6IiIsInNGaWxlSWQiOiIiLCJhdHRJZCI6IjcxODI4ODY3IiwiZGlhZ3JhbU5hbWUiOiJzZG5yLWNvbnRyb2xsZXItYnVuZGxlcyIsImFzcGVjdCI6IiIsImxpbmtzIjoiYXV0byIsImNlb05hbWUiOiJEZXZpY2VtYW5hZ2VyIGNsdXN0ZXIgYnVuZGxlcyIsInRic3R5bGUiOiJ0b3AiLCJjYW5Db21tZW50IjpmYWxzZSwiZGlhZ3JhbVVybCI6IiIsImNzdkZpbGVVcmwiOiIiLCJib3JkZXIiOnRydWUsIm1heFNjYWxlIjoiMSIsIm93bmluZ1BhZ2VJZCI6NzE4Mjg4NjYsImVkaXRhYmxlIjpmYWxzZSwiY2VvSWQiOjcxODMxNDU4LCJwYWdlSWQiOiIiLCJsYm94Ijp0cnVlLCJzZXJ2ZXJDb25maWciOnsiZW1haWxwcmV2aWV3IjoiMSJ9LCJvZHJpdmVJZCI6IiIsInJldmlzaW9uIjo3LCJtYWNyb0lkIjoiMzJhMTYwNGEtOGJmYS00ZDRkLWEyY2ItMTk4NGI4N2NlZjE0IiwicHJldmlld05hbWUiOiJzZG5yLWNvbnRyb2xsZXItYnVuZGxlcy5wbmciLCJsaWNlbnNlU3RhdHVzIjoiT0siLCJzZXJ2aWNlIjoiIiwiaXNUZW1wbGF0ZSI6IiIsIndpZHRoIjoiMTA2MSIsInNpbXBsZVZpZXdlciI6ZmFsc2UsImxhc3RNb2RpZmllZCI6MTU4OTIxMzkwMzAwMCwiZXhjZWVkUGFnZVdpZHRoIjpmYWxzZSwib0NsaWVudElkIjoiIn0=
Netconfnode-state-API
- the base is a Service which provides a Netconfnode-state-API by using a netconf-change-listener
- on top of this service several devicemanagers which can register a callback function for a connected netconfnode
- the devicemanager can then decide if it wants to keep the netconfsession (based on capabilities) and register a notification listener on this or it wants to ignore it
- Listener for
- NetconfNodeConnectListener (Monitored states: connected/not connected and hello response available)
- NetconfNodeStateListener (Create, delete, change .. gets all related indications)
- DeviceMonitor
- ConnectionLog
eyJleHRTcnZJbnRlZ1R5cGUiOiIiLCJnQ2xpZW50SWQiOiIiLCJjcmVhdG9yTmFtZSI6IkhlcmJlcnQgRWlzZWx0Iiwib3V0cHV0VHlwZSI6ImJsb2NrIiwibGFzdE1vZGlmaWVyTmFtZSI6IkhlcmJlcnQgRWlzZWx0IiwibGFuZ3VhZ2UiOiJlbiIsImRpYWdyYW1EaXNwbGF5TmFtZSI6IiIsInNGaWxlSWQiOiIiLCJhdHRJZCI6IjcxODMxNDQ5IiwiZGlhZ3JhbU5hbWUiOiJOZXRjb25mTm9kZVN0YXRlcyIsImFzcGVjdCI6IiIsImxpbmtzIjoiYXV0byIsImNlb05hbWUiOiJEZXZpY2VtYW5hZ2VyIGNsdXN0ZXIgYnVuZGxlcyIsInRic3R5bGUiOiJ0b3AiLCJjYW5Db21tZW50IjpmYWxzZSwiZGlhZ3JhbVVybCI6IiIsImNzdkZpbGVVcmwiOiIiLCJib3JkZXIiOnRydWUsIm1heFNjYWxlIjoiMSIsIm93bmluZ1BhZ2VJZCI6NzE4Mjg4NjYsImVkaXRhYmxlIjpmYWxzZSwiY2VvSWQiOjcxODMxNDU4LCJwYWdlSWQiOiIiLCJsYm94Ijp0cnVlLCJzZXJ2ZXJDb25maWciOnsiZW1haWxwcmV2aWV3IjoiMSJ9LCJvZHJpdmVJZCI6IiIsInJldmlzaW9uIjoyLCJtYWNyb0lkIjoiMGY1YzMyYTItNmNlMy00YWVkLWEzYTQtNGZjZTE5YWQzMDVkIiwicHJldmlld05hbWUiOiJOZXRjb25mTm9kZVN0YXRlcy5wbmciLCJsaWNlbnNlU3RhdHVzIjoiT0siLCJzZXJ2aWNlIjoiIiwiaXNUZW1wbGF0ZSI6IiIsIndpZHRoIjoiOTkxIiwic2ltcGxlVmlld2VyIjpmYWxzZSwibGFzdE1vZGlmaWVkIjoxNTcxMTMzMTcwMDAwLCJleGNlZWRQYWdlV2lkdGgiOmZhbHNlLCJvQ2xpZW50SWQiOiIifQ==
Notification-service
- the notification-service provides the messages for the websevice cluster, so that GUI clients can be informed about changes
- Netconfnode-state-API originated message:
- ObjectCreationNotification (mountpoint created)
- ObjectDeletionNotification (mountpoint deleted)
- AttributeValueChangedNotification (mountpoint connection status change)
- devicemanager originated messages:
- ProblemNotification (Microwave model ProblemNotification)
data-provider
- data-provider has to register on netconfnode-state-API for filling tables