A SOAP listener definition specifies the interface of the user-developed Web service to which the processing results of complex event processing rules are to be sent. This section explains the points to consider in a SOAP listener definition, as follows:
Unit of creation
Create a SOAP listener definition for each user-developed Web service. One SOAP listener definition can be used when a generic application is created, and an application can also be separated by pattern matching.
Development asset ID
Specify a name for the SOAP listener definition that is unique in the CEP engine in which it will be deployed and that suggests the processing content called when rule matching finds a match.
A simple example is where a name such as powerOn is used for a process to notify when the power is on.
Association between a SOAP listener definition and a user-developed Web service
Check that the property value of the corresponding complex event processing rule matches the user-developed Web service to be called, based on the WSDL (interface definition) of the application. Even if an existing Web service is to be used, consider factors such as whether the interface can be used as it is or if it needs to be changed. The aspects that must match are as follows:
Parameter names
The parameter names to be passed to the user-developed Web service must match the property names selected from within the complex event processing rules.
If the property names selected from within the complex event processing rules are to be used as the parameter names to be passed to the user-developed Web service, use them by defining aliases within the rules.
Parameter types
The parameter types must also match the types used from within the complex event processing rules.
Below is an example of the association between a rule definition and a SOAP listener definition. The SOAP messages to be sent to a user-developed Web service are generated from the rule definition and from the SOAP listener definition associated with it.
Figure 5.4 Example of the association between a rule definition and a listener definition, and the SOAP messages to be sent
