To define the enumeration of all the supported topic types. Note that topic types are logical categories of events. The following MTOSI events are not bound to any topic types; Heartbeat, EventLossOccured, EventLossCleared Refer to the Event_T definition. The topic type for these events; ObjectCreation, ObjectDeletion, AttributeValueChange, StateChange, ObjectDiscovery. The topic type for these events; Alarm. The topic type for these events; ProtectionSwitch, EProtectionSwitch. The topic type for these events; FileTransferStatus. the unique service end point address on the CCV. the identifier to uniquely identify a valid subscription. the unique name of topic instance published on the CCV. the enumeration of all the supported query dialect types. the notification filter the dialect of the given query expression the query expression in the language specified by the dialect attribute This operation provides the notification message from the server OS to Client OSs via a Broker (service provider). . it is the unique name of the topic on which the notification "message" was published. The topic is based on a TopicExpression, which is associated as a unique JNDI entry. In MTOSI Release 1, it represents the address of a JMS topic instance created at deployment. the notification payload which can be one of the supported MTOSI events This operation allows the client OS to subscribe with the NotificationBroker for a given topic using the given selector. Raises ProcessingFailureException EXCPT_NOT_IMPLEMENTED - Raised when the OS does not support this operation EXCPT_INVALID_FILTER_DEFINITION ¬ Raised when the filter is invalid EXCPT_INVALID_TOPIC ¬ Raised when the topic is not supported EXCPT_INVALID_INPUT - Raised when another input parameter is invalid EXCPT_NOTIFICATION_SERVICE_PROBLEM ¬ Raised when there is a failure with the Broker the notification consumer endpoint (callback handler) that the broker will call to send the notification the unique name of the topic object of the subscription it is the optional "filter" expression to restrict the flow of messages sent to the notification consumer. By default, an empty selector defines the desire to be notified of all events for the given topic. This is the response of the Subscribe operation. See also Subscribe_T. A unique subscription identifier is returned to the Subscriber Client OS to be used when invoking the unsubscribe() for the given topic. Note that it must uniquely identify the request signature by its three elements; consumerEPR , topic, and selector. This operation allows the client OS to unsubscribe the given consumer with the NotificationBroker for a subscription based on the given topic. Raises ProcessingFailureException EXCPT_NOT_IMPLEMENTED - Raised when the OS does not support this operation EXCPT_INVALID_INPUT - Raised when another input parameter is invalid EXCPT_NOTIFICATION_SERVICE_PROBLEM ¬ Raised when there is a failure with the Broker It is the same subscription identifier that was returned on successful subscription of the Subscriber Client OS with the NotificationBroker. it is the unique name of the topic object of the unsubscription. This is the response of the Unsubscribe operation. See also Unsubscribe_T. Note that it is an empty payload. Failure should be handled as an exception.