Table of Contents

Search

  1. Preface
  2. RulePoint
  3. RulePoint Concepts
  4. Using RulePoint
  5. RulePoint Objects
  6. Working with Topics
  7. Working with Connections
  8. Working with Sources
  9. Working with Responders
  10. Working with Responses
  11. Working with Watchlists
  12. Working with Analytics
  13. DRQL
  14. Working with Rules
  15. Working with Alerts
  16. Setting Access Controls
  17. Troubleshooting RulePoint Issues
  18. Connecting to an Ultra Messaging Application
  19. Creating an Ultra Messaging JMS Source

User Guide

User Guide

Web Services Analytics

Web Services Analytics

The Web Service analytic sends a formatted SOAP message to run a remote Web Services (WSDL) operation and returns the result.
Running a Web Service as an analytic is useful for enriching the data to provide additional information during rule processing that is not available in the event data. To use the Web Service analytic in a rule, you must create a Web Service and then reference that service in the rule.
The following table defines the properties of a Web Services analytic:
Property
Description
Name
The name of the Web Services analytic. This must be a unique name.
Description
Optional. The description of the analytic.
Type
Select
Webservice Analytic
.
Connection
Select the connection name that you want to associate the responder to. You must create a web service connection before you create a web service analytic.
Service
Select the service to list the operations from the list of available services.
Operation to Execute
Select the Web Services operation to run.
Parameter List
Optional. List of parameters for the selected Web Services operation.
XPath Expression
If you specify an XPath expression in the analytic, you get either a single value or a list of many text values in return. If you do not specify any XPath expression, you get the entire XML document in return. For the output xml to change, you must clear the XPath expression and enter it again.
Condition Evaluation Required
Specifies whether the result of the analytic is part of conditional evaluation within a rule. Set to 'false' if the result of the analytic can be used only for enrichment. The default value is True.
Cache Duration
Time period, in seconds, for which the result of the analytic is to be cached.

Example

Consider a subscription-based Web Service that you can use to convert temperature from one unit (degree Celsius) to another unit (degree Fahrenheit). Here, the required values are the temperature value, the source unit, and the target unit . You can define the order of the values in the
Parameter List
field. To use this analytic in a rule, the rule passes the value of temperature to convert, the source unit, and the target unit, and then retrieves the converted temperature in the target unit as the result.
To use the Web Service analytic, complete the following tasks:
  1. Create the Web Service connection. The following URL is an example: http://www.webservicex.net/ConvertTemperature.asmx?WSDL
    Openly available webservice URL might not work.
  2. Create a Web Service with an appropriate name.
  3. Choose the type as Web Service analytic and select the connection. Selecting the connection will provide the operation to execute.
  4. Provide the following parameter list:
    ConvertTemp.Temperature,ConvertTemp.FromUnit,ConvertTemp.ToUnit
  5. Following is the XPath expression:
    /*/soap:Body/ConvertTempResponse/ConvertTempResult
  6. Condition Evaluation Required: Select True and False.
  7. Cache Duration: Total number of milliseconds for which this analytic result is to be cached.
The following rule uses the web service analytic:
when 1 tempConvert1 tc with tempwsanalytic1(temperature, degreeCelsius, degreeFahrenheit) as result != "" then response with body = "${result}"

0 COMMENTS

We’d like to hear from you!