AckEvents

After a GetEvents call, the polling client is responsible for calling AckEvents to notify the BMC Impact Integration Web Services server that it has received the events. The server removes the forwarded events from its local cache. The AckEvents call is required for both reliable and non-reliable subscriptions.

Warning

The value of the num_of_events input parameter must equal the number of events received from the GetEvents call. If not, lost events or duplicate events could occur.

WSDL for AckEvents operation

<wsdl:operation name="AckEvents" parameterOrder="inargs">
	<wsdl:input message="tns:AckEvents_Request"/>
	<wsdl:output message="tns:AckEvents_Response"/>
	<wsdl:fault message="tns:Execution_Fault" name="Execution_Fault"/>
</wsdl:operation>

WSDL messages for AckEvents

<wsdl:message name="AckEvents_Request">
        <wsdl:part element="elems:AckEvents" name="inargs"/>
    </wsdl:message>
    <wsdl:message name="AckEvents_Response">	
        <wsdl:part element="elems:NoValue_output" name="outargs"/>
    </wsdl:message>

XSD schema for request and response for AckEvents

<xsd:element name="AckEvents">
<xsd:complexType>
<xsd:sequence>
		<xsd:element name="filterName" nillable="true" type="xsd:string" />
	<xsd:element name="context_nio" nillable="true" type="xsd:string" />
		<xsd:element name="num_of_events" type="xsd:int" />
	</xsd:sequence>
	</xsd:complexType>
</xsd:element>

Parameters for AckEvents

Name

Direction

Element name

Description

filterName

In

tns:filterName

String type that identifies the name of the event filter that the client has selected. The client is acknowledging the events that have been received.

context_nio

In

tns:context_nio

String type that identifies the name of the web service client that is making the request

num_of_events

In

tns:num_of_events

As the input argument, this is the integer that specifies the number of events the client seeks to receive per polling call.

Was this page helpful? Yes No Submitting... Thank you

Comments