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

HTTP Response Example

HTTP Response Example

After you define an HTTP Responder service, you can create a response that performs an HTTP GET from or POST to an URL.
You can run the response with its default values using the following syntax:
WHEN 1 stock s WITH s.symbol="XYZ" THEN HTTPStockResponse
In this DRQL,
HTTPStockResponse
is the name of the response.
If you want to override any of the default values in your response within your rule text, you can specify those changes in individual parameters. The following rule provides the syntax for all of the parameters for this service:
WHEN 1 stock s WITH s.symbol="XYZ" THEN HTTPStockResponse WITH symbol="${s.symbol}", price="${s.price}", url="http://localhost/submitStockData.html", method="POST", userName="username", password="password", contentType="text/plain; charset=ISO-8859-1", body="Hello World"
The following keywords are restricted to use as response property name and the named properties for this response type:
  • Response property names: target, topic, icon
  • Named properties for this service: URL, method, user name, password, content type, body

0 COMMENTS

We’d like to hear from you!