Cisco Cisco Prime Central 1.0 Developer's Guide
© 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 124 of 124
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
These notifications will be supported across the following objects:
Managed Element
Equipment Holder
Equipment
Physical Termination Point
The primary consumer of notifications within the Prime suite will be the Common Inventory for the purposes of
maintaining synchronization with the state of the live devices. It is anticipated that Common Inventory will consume
notifications from the JMS interface. Other consumers are expected to be Fulfillment (JMS) and the Prime Suite
NBI users (SOAP).