Executing an event trigger
You can set an event trigger as an input or an ouput event trigger in a data service query. Let's look at the usage of the two approaches.
Input event trigger
When an input event trigger is applied to a query, the event trigger is evaluated when the parameters are received by the query. An event-trigger executes an XPath expression against an XML element. This XML element is built from the input parameters that are represented by the element of the parameters wrapped by an element with the name of the query.
For example, take the following query:
Assuming that the values of
value2 respectively, the XML element to be evaluated with the XPath expression is as follows. Also note that this XML element doesn't not have any namespaces associated with it.
Output event trigger
In this case, the event trigger is evaluated when a specific query is returning its result. There isn't a specific creation of an XML element that is used with the XPath expression like in the input event trigger. But the full result XML is used to evaluate it. The result will be namespace qualified. Therefore, you must write the XPath expressions accordingly.
Contents of event notification
In the event notification messages, additional information about the event is added to the SOAP Envelope/Body element. The following code demonstrates this.
- $SERVICE_NAME : Name of the service from which the event originated
- $QUERY_ID : The id of the query that triggered the event
- $TIME : The date/time when the event occurred
- $CONTENT : The XML element generated in case of an input event trigger. It is used when executing the XPath expression. It contains the input parameters wrapped with the query id value. In the case of an output event trigger, it contains the full result XML
For a sample demonstration on how to use eventing, see Eventing Sample.