Cisco Cisco Prime Central 1.5.2 开发者指南
MTOSI OSS Integration
SubscribeRequest mtopBody ) throws SubscribeException;
• UnsubscribeResponse unsubscribe
(Holder<Header> mtopHeader,
UnsubscribeRequest mtopBody ) throws UnsubscribeException;
The subscribe request specifies the following:
• Consumer - URI
• Topic - The string indicating the classification of events of interest
• Selector - Notification Filter
The subscribe response contains a subscriptionID. The unsubscribe request requires the
subscriptionID(s) and topic(s) provided at the time of registration.Support for standard JMS
topic subscription for the JMS interface.
On the notification consumer side, each client type (WS-SOAP or JMS) is expected to
support a slightly different flow.
WS-SOAP clients will need to perform the following
• Expose the NotificationConsumer API as defined by the
NotificationConsumerHttp.wsdl and documented in the MTOSI R2.0 Framework
DDP
• Use the Subscribe operation to register for notifications.
JMS clients will be consuming POJOs with the following format.
ArrayList<Object> consisting of following in this order:
1. com.cisco.prime.esb.fmw.api.Header
2. org.tmforum.mtop.fmw.xsd.notmsg.v1.Notify
For Prime 1.0, the supported notification types will include:
• Object Creation Notification
• Object Deletion Notification
• Attribute Value Change Notification
8.10.4.1
VRF related Notifications
Consumers who have subscribed to the “INVENTORY_NOTIFICATIONS” topic will receive
notifications related to VRF under the following circumstances
• Whenever a VRF gets added
• Whenever a VRF gets added
• Whenever a CTP gets associated with a VRF
• Whenever a CTP gets dissociated with a VRF
• Whenever the IP Address of the CTP changes
Cisco Prime OSS Integration Guide for MTOSI and 3GPP
104