http://www.ibm.com/wsdl/twss/nm/reg/v1_0/interface
A Notification Management-enabled service must use
the NotificationRegistration interface to register and remove
notifications at the beginning and end of their lifetimes,
respectively.
A notification is uniquely identified by its requester,
service, and operation. To remove a previously registered
request, a service must maintain these three pieces of state
between the register and remove invocations.
Operations |
The registerNotification operation allows a
service to register a newly created notification with
the Notification Management common component. Once a
notification has been registered, an administrator may
examine its properties and runtime characteristics using
the NotificationAdministration interface.
The registerNotification operation requires a
sizeable number of details. This provides administrators
with significant flexibility when querying in-flight or
live notifications during problem determination.
Fault:
NotificationDuplicateFault
:
This fault occurs if the request specifies
a requester, service, and correlator already used by
an existing notification.
|
The removeNotification operation allows a
service to remove or deregister a previously created
notification. Removing a notification is generally done
when the notification terminates due to either reaching
its completion criteria or due to a service error.
After removal, a notification can no longer be examined
administratively through the NotificationAdministration
interface.
The removeNotificationRequest requires the same
requester, service, and correlator previously provided to
the registerNotification operation.
Fault:
NotificationNotFoundFault
:
This fault occurs if the requester, service,
and correlator identify a currently unknown notification.
|
|
XML |
-<wsdl:portType name="NotificationRegistration">
<xhtml:p> A Notification Management-enabled service must use
the NotificationRegistration interface to register and remove
notifications at the beginning and end of their lifetimes,
respectively. </xhtml:p>
<xhtml:p> A notification is uniquely identified by its requester,
service, and operation. To remove a previously registered
request, a service must maintain these three pieces of state
between the register and remove invocations. </xhtml:p>
</wsdl:documentation>
-<wsdl:operation name="registerNotification">
<xhtml:p> The registerNotification operation allows a
service to register a newly created notification with
the Notification Management common component. Once a
notification has been registered, an administrator may
examine its properties and runtime characteristics using
the NotificationAdministration interface. </xhtml:p>
<xhtml:p> The registerNotification operation requires a
sizeable number of details. This provides administrators
with significant flexibility when querying in-flight or
live notifications during problem determination. </xhtml:p>
</wsdl:documentation>
<xhtml:p> This fault occurs if the request contains
invalid structure or semantic content. </xhtml:p>
</wsdl:documentation>
</wsdl:fault>
<xhtml:p> This fault occurs if the request specifies
a requester, service, and correlator already used by
an existing notification. </xhtml:p>
</wsdl:documentation>
</wsdl:fault>
<xhtml:p> This fault occurs if an unrecoverable error
occurs while processing the request. </xhtml:p>
</wsdl:documentation>
</wsdl:fault>
</wsdl:operation>
-<wsdl:operation name="removeNotification">
<xhtml:p> The removeNotification operation allows a
service to remove or deregister a previously created
notification. Removing a notification is generally done
when the notification terminates due to either reaching
its completion criteria or due to a service error.
After removal, a notification can no longer be examined
administratively through the NotificationAdministration
interface. </xhtml:p>
<xhtml:p> The removeNotificationRequest requires the same
requester, service, and correlator previously provided to
the registerNotification operation. </xhtml:p>
</wsdl:documentation>
<xhtml:p> This fault occurs if the request contains
invalid structure or semantic content. </xhtml:p>
</wsdl:documentation>
</wsdl:fault>
<xhtml:p> This fault occurs if the requester, service,
and correlator identify a currently unknown notification.
</xhtml:p>
</wsdl:documentation>
</wsdl:fault>
<xhtml:p> This fault occurs if an unrecoverable error
occurs while processing the request. </xhtml:p>
</wsdl:documentation>
</wsdl:fault>
</wsdl:operation>
</wsdl:portType>
|
Used-By |
|